text:
UI config recommendations

It appears that in config files you can move the armor ui overlay for the space suit, you seamed to make this possible since issue 379. With the ui lock set to false in the config I cannot move the ui while having chat open with middle click, I don't know if another mod I'm running is preventing me from doing this.
Having a button that opens a configuration screen in the suit workstation to change the location and scale of the ui's would make a lot of sense to me, since one needs the workstation to get any real use out of the suit, additionally an option to disable the armor ui overlay would be nice since it only tells you what's in your suit, which can be checked through a mouse over of the items, and jet pack state, which could be separate.

Is this still a issue? Please comment if it is and i will reopen if if you are unable? We are closing old issues to see what is still relevant and needs to be fixed.

authors: Rightfuldeathray dmodoomsirius


text:
Missing license and copyright information

I am unable to find any licensing and copyright information for this package.
Are you able to provide this?

Bump. @zodern any chance you could make this happen?

source: gharchive/issue

repo: zodern/meteor-package-versions

license: MIT

license_type: permissive

license_source: github-api


text:
Subjects retiring with too few classifications!

@camallen @edpaget I have a bunch of subjects in Season Spotter Questions that are all marked "retired", but have fewer than 5 classifications. (5 is the set retirement limit.)
For example, check out subject 595581, which has 10 classifications according to the subject export, but only 2 classifications show up in the classifications export.

duplicate of #1363 (really not sure what's going on)

@mkosmala We'll make sure to unretire any falsely retired subjects when we fix this.

@mkosmala the solution we ended up with calculates by counting classifications made since a given date. I have Season Spotter Questions down as 2015-07-21, is that the date you'd want to start the counters (essentially that's then the date they would have all been zero). If so, I'll trigger a recount.

@marten Yep, 2015-07-21 is perfect. For both Season Spotter Questions (project id 347) and Season Spotter Image Marking (id 348).

@mkosmala In that case, everything should be fixed up now. Here's the number of subjects that were dragged out of retirement as a result:
Questions:

"1-4_SimpleSingleCrops" => 200
"1-3_SimpleSingleGrass" => 163
"1-1-5_SimpleSingleShrubs" => 211
"1-2_SimpleSingleNeedleleafTrees" => 167
"1-1_SimpleSingleBroadleafTrees" => 179
"2-2_SimpleDoubleDeciduousFall" => 152
"2-1_SimpleDoubleDeciduousSpring" =>156

Image Marking:

"3-2_ComplexTrees" => 0
"5_ComplexShifts" => 3
"4_ComplexAMOS" => 2

authors: ggdhines marten mkosmala

repo: zooniverse/Panoptes

license_source: bigquery


text:
Data completed message not showing on Supernova Hunters

I was checking around on other projects for some inspiration for my own and encountered that Supernova Hunters is out of data and says finished for the subject  I see non-logged in but the automessage saying the site is out of data isn't showing. I thought I'd mention it.

@mschwamb this is a know issue, the fininshed banner is derived from the subjects vs retired counts matching. In this case the set counts include data that was used pre-launch and the retired counts only count from the launch date. Solutions are to unlink the pre-launch data set / modify the launch date to include the retired counts.

authors: camallen mschwamb


text:
Use build number rather than commit ID for migration jobs

Commit ID seems to be too long.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

👍 Good idea

source: gharchive/pull-request

repo: zooniverse/panoptes


text:
Ability to reuse text for more than one tag

Currently if you've already tagged a piece of text in an issue it doesn't let you use it within in another tag. However, depending on the context, it's sometimes appropriate to use the same piece of text for more than one tag. Can we make it possible to do this?

Seems reasonable. I need to rewrite the classification code anyway, to address #23 and #21.
Deleting a note, by clicking the [X], removes it from the document completely, so I suspect that might remove it from all linked health issues in this case.

authors: axgreen eatyourgreens

repo: zooniverse/wellcome


text:
Repeating overline syntax with Clearspeak

I am not sure if this is expected behaviour or not, but logging here just in case. Given the following MathML:
<math xmlns="http://www.w3.org/1998/Math/MathML" display="block">
  <mn>5.178</mn>
  <mover>
    <mn>6</mn>
    <mo accent="false">¯<!-- ¯ --></mo>
  </mover>
</math>

The Mathspeak rules output:
./bin/sre -i input.xml -d mathspeak -t default -c en
-> 5.178 ModifyingAbove 6 With bar

However with Clearspeak enabled, the output is this:
./bin/sre -i input.xml -d clearspeak -t default -c en
-> the repeating decimal 5 point 1 7 8 followed by repeating digit 6

Is the repeating decimal 5 supposed to be there as an indicator that there are going to be repeating digits in the number? Or should it be simply read as: 5 point 1 7 8 followed by repeating digit 6?

Hi Ryan, sorry it took me a while to get back to this.
The reading is indeed correct. Have look at the Rules and Preferences guide page 61. The rule there states:
the repeating decimal [number] with repeating digit [digit under bar]
The examples however (e.g. in document ClearSpeakExamples_Part 3_Adornments.docx) all use
followed by
For example,
The repeating decimal 2 point followed by repeating digits 1 3 4
I have chosen to implement the latter. But in hindsight the original rule might actually make it a bit shorter.

Perfect, thanks for clearing that up Volker!

authors: ryan-codingintrigue zorkow

repo: zorkow/speech-rule-engine


text:
stopwords compared with contain and not exact match

Describe the bug
When ignoring some secrets using stopwords, other secrets are ignore as they contain stopwords
To Reproduce
stop word "123" ignore also secret "qwerty123"
Expected behavior
stopword ignore exact match (may be ignore case)
Basic Info (please complete the following information):

OS: ubuntu 22.04
Gitleaks Version: 8.9.0

cc @zricethezav

123 is not part of the default stopwords. What you are describing is what is intended; if 123 is part of the secret, then the secret should be ignored if that is what is configured.

Hello,
we have a custom gitleaks who extend from default config, thanks for this new feature, and for customization we have a small stopwords who can have a risk to hide a real secrets

authors: anasoid zricethezav

repo: zricethezav/gitleaks


text:
Static classes within a class

I'm having an issue with the log() method at the tag() call crashing inside a child static class, in general I like what you've done here!

Can you please give some more details? Like what is the exception that crashes things?
I think I've coverted the logging of the static inner classes (see src/test/java/trikita/log/LogFormatTest.java, there are many static classes like LogWithTag, LogWithoutTag etc) and they seemed to work just fine.

Maybe I was wrong about the static part, in the class it was crashing it
also has a local class variable "tag". I'll dig a bit more.
On Sat, Jun 27, 2015 at 10:03 AM zserge notifications@github.com wrote:

Can you please give some more details? Like what is the exception that
crashes things?
I think I've coverted the logging of the static inner classes (see
src/test/java/trikita/log/LogFormatTest.java, there are many static
classes like LogWithTag, LogWithoutTag etc) and they seemed to work just
fine.
—
Reply to this email directly or view it on GitHub
https://github.com/zserge/log/issues/3#issuecomment-116083575.

That was it, if a static class has a member "tag" (I was logging instances of a class with the tag) once I removed the local variable it worked fine. If you can't find the bit of code that caused the problem, I will change back and get you a proper stack trace...

Yeah.. A stack trace (of a simple code snippet to reproduce) would be helpful.
I tried adding local method variables called "tag" (String type), added/removed static class members called "tag", and tests still pass and it doesn't crash.

I'll see what I can do, I just removed the tag member variable and it
worked after that...
On Sun, Jun 28, 2015 at 9:01 PM zserge notifications@github.com wrote:

Yeah.. A stack trace (of a simple code snippet to reproduce) would be
helpful.
I tried adding local method variables called "tag" (String type),
added/removed static class members called "tag", and tests still pass and
it doesn't crash.
—
Reply to this email directly or view it on GitHub
https://github.com/zserge/log/issues/3#issuecomment-116374694.

Ok, one might get a NullPointerException if the tag class member is not static, e.g. if you have private final String tag = "MyClass" instead of private static final String tag = "MyClass". Can you please tell if this is your case?
I think I can catch the NPE in my Log.tag() method as well and ignore it. Which means that a non-static field "tag" won't work as the log tag actually, unless I figure out how to get the caller's "this" object, and hope that the caller's method is not static.

Added a catch for NPE in 1.1.5. Now classes may have a non-static tag attribute and no crash will happen (but it won't be used as log tag though). If you still have problems - please reopen this issue.

authors: KennyGoers zserge

repo: zserge/log

license: mit


text:
Async suggestions search

Hi, very nice package.
But as it comes to fetching suggestions I think it would be very useful if the findSuggestions callback would have return type FutureOr<Iterable<T>> because now this package is not usable when it comes to fetching data asynchronousely which is the most usual case, let's say from an API.
Suggestion is to just change the return type of findSuggestions callback or allow custom builder for suggestions.

This has been implemented just a week ago:
https://github.com/zsoerenm/chips_input/pull/17

authors: salihagic zsoerenm


text:
This model's maximum context length is 4097 token

This is the error message
  "error": {
    "message": "This model's maximum context length is 4097 tokens. However, your messages resulted in 4290 tokens. Please reduce the length of the messages.",
    "type": "invalid_request_error",
    "param": "messages",
    "code": "context_length_exceeded"
  }
}

Rate limited! Please try again later.

I have selected GPT-4-32k with Max Token: 32768.
On the same chat, It works fine in the first 2 questions, but on the third question is throws the error above.
Please let me know how to bypass this, specifically how to make it continue to use the max token during the same chat without going back to the 4092 token.
Big fan of this!

May I know whether the 3 questions are in the same chat or different chats?

Hi, they are in the same chat

Have you clicked on confirm after configuring the model parameters?

Upon further investigation, I went to https://platform.openai.com/ and then checked "Usage" and although I had GPT 4 on the frontend of your app and I clicked save, it sent GPT3.5-turbo to the API calls.
I pulled your latest release and that fixed the issue!
Thank you.

repo: ztjhz/BetterChatGPT


text:
RFC: Ensure key network requests always succeed

refactor timeout code
refactor initial requests code
add a function tryUntilSucceed that retries a failed request
add tests

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!

Added initial comments. Also changed the title to 'RFC: ' (for 'request for comments') to reflect the fact that this is a work in progress

@borisyankov let me know when this is ready for a final review and merge!

Ready for final review and merge.

We shouldn't retry on non-network errors
I will merge this, and add this as issue and work on it next.

authors: borisyankov neerajwahi smarx

repo: zulip/zulip-mobile


text:
tools/deps: Fix hashbang

/usr/bin/env bash is more portable than /bin/bash.

Merged, thanks!

authors: WesleyAC gnprice


text:
ComposeBox conversion: some followups

For review after #5312 settles. Done! 🙂

#5355

authors: chrisbobbe gnprice


text:
Zulip tray icon gone (on Manjaro Linux using XFCE)

Since a few days back, Zulip no longer displays any tray icon when running. This makes it hard to remember that it's still running when minimized and easy to miss important notifications.
I'm using package zulip-desktop 5.0.0-1 on Manjaro Linux with XFCE.
I tried clicking "View -> Toggle Tray Icon" in the menu, toggling "Desktop Settings -> General -> Show app icon in system tray", and also manually changing the "trayIcon" flag in .config/Zulip/config/settings.json, but none of this made any difference either immediately or after a restart (both of Zulip or of my whole machine). I've also tried starting zulip with dbus-lunch but that didn't make a difference either. I looked in the Dev Tools console, but didn't find anything that seems related to this problem.
So what can I do to bring back the Zulip tray icon?

@catalin-hritcu This is occuring due an upstream electron issue which occurs in some Linux distros.
The fix for Manjaro XFCE is given here . Please try that out and if it works for you please let us know.

@abhigyank Thanks a lot, this worked like a charm for me.

Good to know.
This issue can be closed.

This comment has some more fixes for other distros (such as Mint, which solved the issue for me). Just leaving it here for people who look for a fix.

authors: NiklasMM abhigyank catalin-hritcu

repo: zulip/zulip


text:
Make it easier to make the compose box big for composing something large

I've gotten feedback that some users compose messages in emacs because composing a long message in Zulip didn't feel great to them.  There are 3 parts of the problem:

Compose is at the very bottom of the screen, so you're looking down.
It's nice to feel like there's a lot of space if you're composing e.g. an announcement.
The user didn't know how to expand the compose box (hitting enter works, but is kinda hacky).

At the very least, we should have a more obvious mechanism than holding down enter for supporting the use case of writing a longer message.  Possibly supporting a popover in the center of the screen would be a good idea; the quick approach would be to have UI for dragging it taller.

@timabbott I like the idea of making the compose box big. It would be really nice to do that for longer messages. Having a popover may be a good idea, but I am not sure if it is suitable for opening a popover just to write a longer message. Currently the composing texarea is not resizable. What if we make the textarea resizable (which will be visible to the user) and the user can simply drag it to make it bigger. What do you think?

Yeah, I think making it resizable via drag (not just holding down enter) is probably a good immediate response to this.  We should think carefully about the semantics here to avoid creating other problems.
The model is currently that the compose box grows/shrinks in size based on how much content you have in it; I guess the new model could be that it keeps the behavior, but if you've dragged it while it's open, then it just stays at the current size until it grows to that size via typing stuff in and then reverts to the resizing-based-on-typing behavior?

Right. The new model you are suggesting sounds great. The vertical dragging system would work fine. So if the user drags the box to a certain height and then types something, and if the typed content's height becomes more than the current height of the box then the box will grow till its max height (provided the max height is not already  reached by dragging the box). And finally if a user starts deleting content, the box will shrink according to the content.

Sounds good!


text:
Create separate booleans on Stream objects for private/invite-only streams and private history

In Zulip, we have 2 concepts that are related but not quite the same:

Stream.invite_only -- the current boolean which controls whether people can join a stream without an invitation
Whether the message history of the stream is visible to subscribers from before they joined.

Historically, these were the same, since we wanted to support discussing whether to invite someone to a stream before adding them without potential embarrassing issues, but it would be good to give users the flexibility to do things differently for streams where they want to (we have several, such as the GCI members stream, in chat.zulip.org that would make sense to be invite-only with full history available to members).
There are a few things that this separation will require:

creating the new boolean and populating it properly in a migration (I think we need to use the logic currently in Stream.is_public() for this, basically)
Moving the get_old_messages code to actually make the old messages available based on the new boolean.
Changing access_message (used for getting raw content, etc.) to
Adding tests for the new behavior

Ideas for what we should call the new field?

would these changes enable also this scenario:
We realised today that in a company you can also really use the option of an open stream with a closed history. We are about to run the company newsletters through a default stream but had to set it to closed because why would new employees need to browse through ancient newsletter with reminders to not let food go moldy in the fridges :-P ? That's just a trivial example...
So the idea would be to limit history for new users but still give all users of the realm the chance to subscribe themselves to the stream (because it's public) or not.
Alternatively another setting would be that the limited factor for chat history is not the point in time when the user joined the stream but the realm instead.
I can see this best worked out if each stream has two main boolean settings.

closed stream (yes/no)
open history (yes/no)
* sub setting limit criteria if the above is false: realm join (yes/no) (no would be stream join)

Does this make sense?

I don't see that open stream with closed history as a compelling use case, and I do see some incentive problems with it (means you want to subscribe to everything with a bot that logs things so you can get the history).

The incentive problems are at least fixed in the second proposal, which is that users would get history up to the point when they joined the realm.
It's possible limiting public stream history in this way is solving problems that should instead be solved with stream-level retention policies?

public stream with closed history: for all employees: announcing birthday or personal forum type of things. New users joining the realm should not be able to see stuff before they joined the realm due to data protection. But still the nature of the stream is public. So @rishig point is the better approach.
For now opening up all history with the server setting is not an option because of the first scenario I described.

Closing this in favor of #2044 (since the work described in this issue is done).

Streams history is not visible to new users that are subscribed to that stream. But after I have done the steps mentioned above. Now the stream history is visible to new users but only for the streams that were created after changing those settings. The history of the streams that are created before changing those settings are still not visible to the new users.

Yeah, that's because we're an intermediate state of migrating this to be controlled in the UI (a few days from completion).  You can adjust manually on the manage.py shell, but this should be no longer messy very soon.

authors: penCsharpener rishig suryateja29 timabbott vbNETonIce


text:
Mentioning autocomplete when editing message

When editing a message to include an @mention on the Zulip web client, the autocompletion feature is not implemented. The way I personally go about getting their handle correct is the use the autocompletion is the standard chat then copy-and-pasting it into my message edit.

As you can see in the picture above, no suggestions are given to complete the mention.

That is already a bug report here.

@tommyip ah, appears it is. Closing issue now.


text:
api-documentation: Document avatar URL endpoints.

Currently, we don't have documentation for the avatar URL endpoints. Those are:

GET https://yourZulipDomain.zulipchat.com/avatar/{email}/
GET https://yourZulipDomain.zulipchat.com/avatar/{email}/medium

Among other things, we want to document and make clear:

the file type: no SVG file type (probably we want all to be PNG)
the different file size: requests to the medium endpoint will return a 500x500 px image avatar, and the default one will return <=100x100px image file

Follow ups:

Adjust a code comment on lib/storage.py/reformat_medium_filename() made on this PR

CZO thread

@zulipbot add "area: documentation (api and integrations)"


text:
user docs: Information on changing organization settings is outdated

Our user docs are very outdated in the fact that most of our organization settings formerly located at #organization/organization-settings have been moved to the #organization/organization-permissions page; most of our docs still point to those pages when they should be pointing to the permissions page instead.
Additionally, several new organization settings have been added and should be documented.
/help/change-your-organization-settings also needs to be updated accordingly.

Yeah, good point.  The "organization permissions" piece we should at least treat as a high priority.

@zulipbot claim

@synicalsyntax with #5750, are there more things we need to do here?

For change-your-organization-settings.md, I was referring to the fact that both that page and the {!admin.md!} macro refer to a "Manage organization" page, which doesn't exist. I think it's been renamed to "Organization"?

#5765 was merged, so we can close this.  Thanks @synicalsyntax and @vaidap!

authors: synicalsyntax timabbott vaidap


text:
User docs: copy-a-block-of-messages

Splitting out the articles from to todo list here: 32f6a76
@zulipbot label "area: documentation (user)"

https://github.com/zulip/zulip/issues/8889


text:
Skipping Oracle java

Although java 1.7 is installed on the system (ubuntu), the installer wants to download Oracle Java 1.7 and it fails due to some connection problems that I am aware of that.

root@ce:~# java -version
java version "1.7.0_121"
OpenJDK Runtime Environment (IcedTea 2.6.8) (7u121-2.6.8-1ubuntu0.14.04.3)
OpenJDK 64-Bit Server VM (build 24.121-b00, mixed mode)
root@ce:~# ./zulip-server-1.8.1/scripts/setup/install --certbot --email=mh.naderan@scu.ac.ir --hostname=ce.scu.ac.ir
+++ dirname ./zulip-server-1.8.1/scripts/lib/install
++ readlink -f ./zulip-server-1.8.1/scripts/lib/../..
+ ZULIP_PATH=/home/mahmood/zulip-server-1.8.1
+ export LC_ALL=en_US.UTF-8
+ LC_ALL=en_US.UTF-8
+ apt-get install -y lsb-release
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 302 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up oracle-java7-installer (7u80+7u60arm-0~webupd8~1) ...
Downloading Oracle Java 7...
--2018-05-10 16:58:22--  http://download.oracle.com/otn-pub/java/jdk/7u80-b15/jdk-7u80-linux-x64.tar.gz
Resolving download.oracle.com (download.oracle.com)... 23.210.248.136
Connecting to download.oracle.com (download.oracle.com)|23.210.248.136|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2018-05-10 16:58:22 ERROR 403: Forbidden.

download failed
Oracle JDK 7 is NOT installed.
dpkg: error processing package oracle-java7-installer (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 oracle-java7-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@ce:~# vim ./zulip-server-1.8.1/scripts/setup/install

How can I skip that step?

This isn't a Zulip problem.  The Zulip installer is just running  apt-get install -y lsb-release, if you read closely, you'll see that you have a half-installed Oracle Java package, and apt is trying to finish installing it.  You should be able to dpkg -r oracle-java7-installer` to get rid of it and then proceed to install Zulip.

authors: mahmoodn timabbott


text:
create stream: Fix bugs in copy-subs-from-stream and announce-stream features.

This PR fixes minor bugs in create stream page.

I merged the first commit, and posted a couple comments.

@timabbott updated.

Rebased.

I think the behavior to uncheck users who were on a stream you uncheck was intentional, though it's hard to say what the correct behavior here should be.  I think probably migrating to this makes sense, since it's hard to come up with a use case for wanting to exclude users from a given stream by double-toggling it.

yeah, make sense. when subscribers are not included in list even the stream is checked, it creates confusion. PR also includes fixes of #9964 for issue #9480

Closing as I'm pretty sure we've fixed these bugs through other PRs.

authors: YJDave timabbott


text:
Ratelimitfilter

EDIT: Oops, I didn't set the PR title properly and now can't edit it :see_no_evil:
Fixes https://github.com/zulip/zulip/issues/12595.
I tried to more-or-less implement the idea for fixing this outlined there. The way I did this is pretty ugly, so I'll be happy to change it up if it can be made nicer. The comments in the code explain what's going on.
Seems to work in the sense of passing the unit test added in commit 1 and with manual testing - I can kill memcached in development environment, do tools/run-dev.py and open the page in my browser - it leads to Fatal Python error: Cannot recover from stack overflow. before the changes, and normal handling with the changes.
I'm not sure how to test whether this works correctly in terms of threading - if the thread-local variable acts like it should and each thread has its own version of it. It should be the case, as long as I didn't misread the documentation, but this seems like something that should get tested somehow before feeling happy with this fix :thinking:
As for the logging.error generated, nothing unusal about them I think and they can be rate limited just fine. Here's an example output (by making _RateLimitFilter print out info about the received logging record at the start of the function). It duplicates the errors printed, because it's printed one time by the _RateLimitFilter and once by Django's logging.error calls, but you can see the generated cache keys for the same error are the same each time:
https://pastebin.com/u783LAbr

This is great!  A few notes:

I extracted a block of hard-to-read code to a function, which I think helped a lot.
I rewrote a lot of the comments, added a docstring, etc., to make this a lot more readable.
I squashed the commits, because while it's great for manual testing to be able to confirm

and merged this as a7ec1a089c2b3c5c531dde698df6c1396fb20437.  Thanks @mateuszmandera!

@Arunhari333 The issue with that would be that another filter() execution within the same thread (so a recursive call) will have  handling_exception.value set to True, so in your block, it would switch the value to False at its end - but the original call (the one who set  handling_exception.value = True) hasn't finished yet, so that would be incorrect.
allowed_to_alter_handling_exception_value is there to know the "original" function - it will be True only for the original, and then only the original will set handling_exception.value to False - just as we want to, because "handling exception" state ends only when the original filter() call stops executing.

Tim refactored it somewhat when merging - https://github.com/zulip/zulip/commit/a7ec1a089c2b3c5c531dde698df6c1396fb20437 - maybe this will look clearer for you.

I understood, thank you

authors: Arunhari333 mateuszmandera timabbott


text:
search: add unittests for pgroonga parts-of-URL search.

Related to #9165 and #22672

In my view, we can only mark #9165 if that bug no longer occurs in any version of Zulip. Right now, PGroonga is a non-default setting experienced by probably <1% of users, and there's substantial work required to change that.

@timabbott sorry my bad, edited the PR comment.

Merged after also editing the commit message, thanks @asah!

authors: asah timabbott


text:
gear_menu_popover: Fix extra space when no invite permission.

This PR fixes the extra space and additional border that was being added to the gear menu popover when the user did not have permission to invite users.

CZO: link

Screenshots and screen captures:

Before
After

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

This probably works though I hate having to write the conditional explicitly there; it would be nice if we could just declare via CSS to not allocate space to an empty region. Not sure there's a good way to do that though; @amanagr @karlstolley ideas?

Ideally we'd be able to use something like :empty in CSS, but the structures here aren't lending themselves to its use (for :empty to work, an element has to have zero child nodes, even if the child nodes themselves are empty).
So I think the solution here is probably the best for now, and possibly longer term. I'm not sure what kind of gymnastics are ultimately worth it to try and clean out the structure, when @sayamsamal's solution--though not the prettiest at the template level--just wholesale prevents those elements from appearing in the DOM to begin with.

Merged, thanks @sayamsamal!

authors: karlstolley sayamsamal timabbott


text:
compose: Make ctrl-enter, meta-enter and alt-enter add newline with enter_sends

(ouch, commit title got cut a bit, hehe).
Closes #2989.

Automated message from Dropbox CLA bot
@bojidar-bg, it looks like you've already signed the Dropbox CLA. Thanks!

Thanks for fixing this @bojidar-bg!  I merged this as 1c044688a41e412f3fd6c22ac324dcbf503c8038, changed just to resize the input area if one hits enter when at the bottom of the text box (compose.autosize()).

authors: bojidar-bg smarx timabbott


text:
left_sidebar: Refactor nav rows for low-resolution screens.

This PR refactors the left sidebar navigation rows in a way that does not disturb high-res presentation of the labels and icons, but makes a big improvement to low-res display of navigation rows in Chrome.
The solution here effectively decouples the row height from the line-height, which was off in Chrome due to likely subpixel rounding errors in its font rendering engine. Instead, CSS Grid auto-generates rows as needed to the same height as would otherwise be specified on the line-height.
CZO discussion

Screenshots and screen captures:

Chrome, low-res before
Chrome, low-res after

Chrome, high-res before
Chrome, high-res after (slight improvement?)

Firefox, high-res before
Firefox, high-res after (no change)

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Looks great, merged, thanks @karlstolley!

authors: karlstolley timabbott


text:
stream_popover: Handle no messages condition for a topic being moved.

Previously, when there were no messages in the topic being moved, the banner in the move topic modal only showed a "Failed" error banner which did not convey the actual error to the user. Also, a server call was being made even when there were no messages in the topic being moved.
This PR explicitly handles the non-existent topic, prevents a call to the server when the message_id is undefined, and displays a more informative error banner to the user.
Fixes: CZO Discussion

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[ ] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Looks great, merged, thanks @sayamsamal!

authors: sayamsamal timabbott


text:
Fix a grammatical error in status change message.

The whole story:

Github: cc0d391 changed it's status to pending
Github: cc0d391 changed it's status to pending
Github: cc0d391 changed it's status to error
KW: Did we write this message ourselves?!? The grammar error is driving me crazy. :-)
SF: No, it's either Github's fault or Zulip's!
+ Sigh. I assume it's part of the Travis-CI integration?
– I checked, and that message is not in the JSON message that comes from Github
– Look what I found! https://github.com/zulip/zulip/blob/7227f488c8f9d77fb30b9276192f1147e30c981b/zerver/webhooks/github_webhook/view.py#L273
+ Time for a pull request!
– My moment has arrived.

Automated message from Dropbox CLA bot
@sadjad, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@sadjad, thanks for signing the CLA!

Merged!  Thanks @sadjad and @lonerz.  Note that I squashed the two commits into one.  We always put test changes into the same commit as the code changes.

Thank you so much, @showell and @lonerz!

authors: sadjad showell smarx


text:
Add custom data to states from front matter

Provide access to add custom data to state objects from front matter.  I needed to add custom data for route authentication, but this could be useful for others and their purposes as well.
Template Front Matter
---
name: main
url: /
animationIn: fadeIn
data: { requiresLogin: true }
---

Added to DynamicRouting
angular.extend(state.data, page.data);

@naneer that feature is already available! :) The front matter works off basic YAML syntax so what you can do is:
data:
    requiresLogin: true

That should work.
I made a video demonstrating some of these features, check it out (make sure to watch it far enough where I demonstrate that it works, I fumble a few times).

Thanks for the response, I switched to YAML syntax!!!  Though the issue I have is that I need the authentication system to be able to access the State data property directly.  The properties in front matter will be placed in data.vars.
I apologize, in the effort to be frank, I missed a few key reasons why I had to do this.  I should have clarified better, the story is that I'm trying to use another third-party system that listens for $stateChangeStart and checks if authentication is needed by looking for to.data.requireLogin.
I'd imagine that there could be other external assets out there that follow this specification to store  custom data in the data property.
But rather than attempting to change the way the other system checks $state.data, I was hoping Foundation-apps could be able to pass in data properties entered in front matter and then add that to the state.data along with the properties that will be placed in state.data.vars.
I expanded my initial workaround to compensate some edge cases, here's my amateur attempt at this:
    var state = {
      data: getData(page),
    }
    function getData(page) {
      var data = { vars: {} };
      if (page.data) {
        if (typeof page.data.vars === "object") {
          data.vars = page.data.vars;
        }
        delete page.data.vars;
        angular.extend(data, page.data);
      }
      delete page.data;
      angular.extend(data.vars, page);
      return data;
    }

It considers that there could be valid data.vars properties from within and merge it with the rest of the properties in the page, but ultimately overwriting same name values in favor of the page properties.
---
name: post
url: /post
animationIn: fadeIn
data:
    requiresLogin: true
    vars:   // not recommended but will support provided properties are unique
        cards:
            -
                name: "Card in data vars"
                description: "I shouldn't be here, but I'll still work {{ vars.cards[0].name }}"
---

---
name: post
url: /post
animationIn: fadeIn
data:
    requiresLogin: true
    vars:  // not recommended but will support provided properties are unique
        cards:
            -
                name: "Card in data vars"
                description: "I won't work now cause I'm not favored"
cards:
    -
         name: "Card in vars"
         description:  "I will work cause I'm favored!"
---

Overlooks any properties with the key name as vars
---
name: post
url: /post
animationIn: fadeIn
data:
    requiresLogin: true
    vars: "will be overwritten cause I'm not an object"
---

I hope this isn't beyond the scope of Foundation-apps, I think being able to integrate with other third-party systems will be vital.

authors: AntJanus naneer

repo: zurb/foundation-apps


text:
Using center elements with anything else seems to break the layout

Using a center element in a panel, text-pad, etc. seems to break the container width.

We've removed the .text-pad class in v2, so this should be fixed. We've also stopped supporting v1, however we're more than happy to pull in v1 PRs into our v1.0.0 branch. Thanks!

authors: jscheel tdhartwick

repo: zurb/foundation-emails


text:
wrong link location in HTML Templates

bit offtopic, but it's a quick one:
on your foundation6 HTML template page both simple blog and simple blog /w sidebar link to "simple-blog.html"
cheers

CC @rafibomb

All good now!

authors: S1SYPHOS gakimball rafibomb

repo: zurb/foundation-sites


text:
Animating Offcanvas with Closable Button

How can we reproduce this bug?
<div class="off-canvas position-right" id="off-canvas"
    data-closable="slide-in-down slide-out-up"
    data-off-canvas data-position="right">

What did you expect to happen?
Take priority for Closable animation.
What happened instead?
Offcanvas will stuck as there is some clashing between Closable and Offcanvas js parts.
Test case:
Will update one soon, posted for a quick review, in case someone have the same experience.

CodePen with Foundation 6 and MotionUI
CodePen with Foundation 6, Flexbox grid and MotionUI

Have you tried closing with custom function?
$('#oc-left a').on('click',function(e) {
                                    $('#offCanvasLeft').foundation('close',function(e) {
                                        console.log("holler back");
                                    });
                                });

cc @brettsmason for your offcanvas work

@kball I'd like to discuss this with you when possible to see how we could handle MotionUI animations

Maybe can be done with the new OffCancas II in Foundation 6.4?

Hi, what is the current status?

I think this is outside the current scope of the off canvas menu - it wasn't really built with this integration in mind, and would require a fair bit of work. I'd suggest we close this and maybe revisit in 7.

I had used twitter/bootstrap since with good luck setting up similarly the project.

authors: DanielRuf brettsmason kball klihelp paxperscientiam


text:
Proposed fix for issue #17

Makes clientside javascript calls to the github API. Retains existing formatting/styling.

Very cool use of the GitHub API. Merged into master and will go live with the next deploy of the documentation site.
7bd876662b7034c07ef357426cfbc6ab6535da6a

repo: zurb/foundation


text:
Get illuminance value (LUX)

Hello,
is there a way to get illuminance value (LUX format) of a picture from the stream?
My goal is to create a camera based light meter.
Thank you

This library only provides luminance values.
It appears that reflectance data is required to convert luminance to illuminance, but I am not familiar with the specifics.

@k4rm3l0 Were you able to find a solution to build a camera based light meter ?

@k4rm3l0 Were you able to find a solution to build a camera based light meter ?

Yes, but my code is heavy dirty. It's just for learning purpose.
I found the formula to calculate the lux value here.

Thanks @k4rm3l0. I will check it out.

authors: ibrahimbroachwala k4rm3l0 zuvola


text:
Multilevel switch currentValue reports level 255 when setting targetLevel to last (255)

Describe the bug
If you turn on a light using the last level (targetValue 255) zwave-js immediately returns the currentValue as 255, which is a "deprecated" value. I assume this is some new behavior from #1522.
Should the application handle the value 255, or should zwave-js not send it? Unfortunately, if nothing is sent, the problem of flickering UIs returns.
As of now, HA only expects values from 1-99 so the 255 results in HA thinking the light is as bright as the sun (or close to it!).
Device information
Which device(s) is/are affected (make/model)? All dimmers (state exists until a new value is reported, that time various by device). If an application prefers to report targetValue for V4+ switches, it will not be observable.
What are the node IDs? 2
Last Known Working Configuration

[ ] New device

[X] Previously working device (node-zwave-js)

Which library version/docker image/adapter version? v6.1.0
Have you made any recent configuration changes to the device? Describe. No

[ ] Previously working device (other platform)

Which platform?
Have you made any recent configuration changes to the device? Describe.

Installation information
How did you install node-zwave-js?

[ ] zwavejs2mqtt (latest) docker image
[ ] zwavejs2mqtt (dev) docker image
[ ] ioBroker.zwave2 adapter
[ ] Pkg
[X] Manual Docker build

node-zwave-js branch:  b1b4f74ef95da72f87e68b474e513867d7e33c68
zwavejs2mqtt branch:  v1.0.1

[ ] Manually built (as described in the docs)
[ ] Other:

To Reproduce
Steps to reproduce the behavior:

Set the multilevel switch targetValue to 255 (turn on to last level)
Watch the currentValue go to 255
Wait a few seconds for a refresh
Watch the currentValue show the actual value

Additional context
Logfile: zwavejs_1.log

I think this is just an issue of the 99 or 255 scale, no? Are you on the most recent? If so, I think @AlCalzone  and @robertsLando need to coordinate which scale they're using for devices as zwavejs2mqtt is defining the 0-99 scale and node-zwave-js is returning 255. https://github.com/zwave-js/zwavejs2mqtt/pull/295

@kpine's analysis is correct. This is due to the immediate response for the currentValue properties. 255 is an edge case I forgot to handle.
Unfortunately, this means that you'll have to handle the missing (or delayed) update somehow in the UI. There's no sound fix for this at the zwave-js side that also avoids flickering.
If we remember the last value somehow, that adds a lot of complexity and there's no guarantee that it is the correct one.
If we don't update currentValue (my preferred solution) you will have flickering for devices that don't send updates on their own.
I believe that in the end, there's some change warranted on the HA side. If the zwave-js API call succeeds, it is at least guaranteed that the command was acknowledged by the device. This doesn't mean it will execute it, but you could use that information to update the UI (or keep it from switching back).

I agree with all that you said. HA should ultimately handle this in some way, after all there must be some other kinds of devices out there (not Z-Wave) that don't report instant states. Assuming an optimistic value as you are doing would work the same way.
Given #1561, it looks like HA can assume it will always receive values of 0-99 then, at least for currentValue? Should it guard against other values?
I also wonder if some HA users will see this for the multilevel switch V4 devices. HA checks the CC version, if it's 4+ it uses targetValue to report the brightness value instead. If HA turns on a V4 switch in this same way, it seems the targetValue will be 255 until the switch reports something, causing the same problem? In that cause, it should guard against 255 anyways (I don't have one of these switches to test).

@kpine we reverted the targetValue check in HA...
https://github.com/home-assistant/core/pull/45884

authors: AlCalzone blhoward2 kpine marcelveldt

repo: zwave-js/node-zwave-js


text:
Missing device config: 0x0086:0x0003:0x006f:1.2

Discovered info:
associationGroups: Lifeline, Retransmit, Control:Key1, Control:Key2
zWavePlusVersion: 1

http://manuals-backend.z-wave.info/make.php?lang=en&sku=AEOEZW111&cert=ZC10-17015388

https://devices.zwave-js.io/?jumpTo=0x0086:0x0003:0x006f:2.3
but we don't have a config for firmware 1.2
@blhoward2 ?

I combined files and I think I just missed changing the definition at the top. I'll fix it.

authors: AlCalzone akennerly blhoward2


text:
chore(docker): add tags for major and minor version to container images

What is the objective of this PR
On release this adds tags ${major} as well as ${major}.${minor} to the container images.
This is quite common practice and allows users to follow minor or major releases instead of only latest (typically not recommended) or specific patch versions, requiring to constantly monitor for new patches releases.
Any feedback is welcome. :)

Pull Request Test Coverage Report for Build 3306422927

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 24.478%

Totals

Change from base Build 3295723139:
0.0%

Covered Lines:
3732

Relevant Lines:
16097

💛  - Coveralls

authors: coveralls esolitos

repo: zwave-js/zwave-js-ui


text:
[bug] Upgrade from 4.0.1 to 4.1.0 or 4.2.0 loses all data on battery powered devices

Version
Checklist:

[x ] I am not using HomeAssistant. Or: a developer has told me to come here.
[x ] I have checked the troubleshooting section and my problem is not described there.
[x ] I have read the changelog problem was not mentioned there.

Build/Run method

[x ] Docker
[ ] PKG
[ ] Snap package
[ ] Manually built (git clone - yarn install - yarn run build )

zwavejs2mqtt version: 4.0.1
zwave-js version: 7.3.0
Describe the bug
Running ZWaveJS2MQTT docker container and have about 50 devices paired to an Aeotec stick. Has been running flawlessly for the last few months. Running with the "latest" tag in my docker compose file so today it pulled in 4.2.0 and started. Noticed right away I was missing a bunch of node data. Looking closer in the web UI, pretty much every battery powered device shows no data like it needs to re-interview the node. I did not check completely to see if it truly is only battery powered devices since I had to get things running again.
Since I've had something similar happen in the past, I stopped the docker container, removed it, manually specified 4.0.1 in my docker compose file, then replaced all the persistent volume data with a backup from last night. Started up and all is working just fine.
Tried again by changing the tag to latest and pulling in 4.2.0. Stopped Home Assistant first just to keep it isolated while testing.
Same problem, a good majority of my devices have no node data again. This is 15 or so minutes later so my network should have "settled down" by then.
Needed a working system so I downgraded to 4.0.1 again with my backup data and am back to a working state again.
I owe some log files when I get to a chance to re-produce this later today.
To Reproduce
Steps to reproduce the behavior:
See above
Expected behavior
Reviewed the changelog and didnt see any breaking changes so I expected the upgrade to be normal.
Additional context
I am using Home Assistance container, but this issue is isolated to the ZwaveJS2MQTT setup. The same thing happens regardless of if Home Assistant is running or not.

Please update to 4.2.1

FIxed. Thank you.


text:
🛑 🇲🇨 SCRIPT is down

In 8c7f328, 🇲🇨 SCRIPT (http://sc.zxbxns.me:81) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 🇲🇨 SCRIPT is back up in 74dd51c.

repo: zxbxns/status-server


text:
Thanks and a question about upstreaming

Hi, thank you for this wonderful library! We're creating a structure editor for ASTs for our pedagogical functional programming language, and have had a hard time finding a layout library that works well for ASTs. We recently discovered Tidy, and it looks very promising.
I have a question about submitting PRs. We've forked this repo in order to add Nix support, and in the process have cleaned up a few build- and packaging-related issues. We would like to upstream those changes, if you're interested. However, before we do that, I see that you're using npmmirror.com in the lockfile, rather than npmjs.org. Does npmmirror.com work better for you based on your location, or something like that? I ask because we've never heard of npmmirror.com and don't know anything about the organization/individuals who run it, and we're therefore uncomfortable using it for production. So for our own purposes, we're going to regenerate the package-lock.json file, which will complicate upstreaming.
Anyway, I'm not suggesting that you change anything on your end, just wondering whether you're committed to using npmmirror.com rather than npmjs.org. If so, we will just work around it if/when we upstream PRs.
Thanks again!

PRs are welcome! Yeah, npmmirror.com works better at my geo location. It's run by Alibaba. But I'm not committed to using it, you're free to change the lockfile to use npmjs.com instead.

Great, thanks! I'll close this now and submit an initial PR.


text:
add the ZAPI request id on RequestError message

Alternative to https://github.com/scrapy-plugins/scrapy-zyte-api/pull/142

Codecov Report

Merging #52 (cd8454e) into main (91b141e) will increase coverage by 15.02%.
The diff coverage is 100.00%.

:exclamation: Current head cd8454e differs from pull request most recent head 0e684a3. Consider uploading reports for the commit 0e684a3 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main      #52       +/-   ##
===========================================
+ Coverage   43.28%   58.31%   +15.02%
===========================================
  Files          10       10
  Lines         365      367        +2
  Branches       53       53
===========================================
+ Hits          158      214       +56
+ Misses        205      145       -60
- Partials        2        8        +6

Files
Coverage Δ

zyte_api/aio/client.py
71.42% <100.00%> (+36.76%)
:arrow_up:

... and 5 files with indirect coverage changes

Tox is failling for 3.7. I suppose removing it would be apt. https://github.com/zytedata/python-zyte-api/pull/53

authors: BurnzZ codecov-commenter

repo: zytedata/python-zyte-api


text:
is recognized as a Text node

Hello!
When parsing html </form> is recognized as a #text node.
Small repro.
var document = new HtmlDocument();
document.LoadHtml("

");
var result = document.DocumentNode.Descendants().Select(dn => new { dn.NodeType, dn.Name, dn.OuterHtml }).ToArray();

Result contains:
new []
{
    new { NodeType = HtmlNodetype.Element, Name = "div", OuterHtml = "

" }
}

Seems reasonable, however changing "

" to "<form></form>" in the repro above yields an unexpected output
new []
{
    new { NodeType = HtmlNodeType.Element, Name = "form", OuterHtml = "<form>" },
    new { NodeType = HtmlNodeType.Text, Name = "#text", OuterHtml = "</form>" }
}

Obviously my real scenario has a full HTML document, with html, head, body, etc, but the error stays the same.

Hello @osjoberg ,
Thank you for reporting,
We will look at this issue.
Best Regards,
Jonathan

Hi @JonathanMagnan, I am a developer of the WebSharper web framework for F#. We are using HtmlAgilityPack for our templating engine, and we are being hit by this and #48. Is there any ETA for a fix on these issues?

Hello @Tarmil ,
My developer provided me a pull request yesterday.
I'm currently checking the side effect of this pull request.
If there is nothing wrong, it should be released probably Wednesday.
Best Regards,
Jonathan

Hello @Tarmil ,
My developer provided me a pull request yesterday.
I'm currently checking the side effect of this pull request.
If there is nothing wrong, it should be released probably Wednesday.
Best Regards,
Jonathan

That's great news, thanks!

Hello @osjoberg , @Tarmil ,
The issue should be fixed, the Form is no longer recognized with an flag Empty
Soon, we will rework the logic to fix all this kind of issue with tag.
Best Regards,
Jonathan

Hello @osjoberg , @Tarmil ,
We will close this issue since it should be fixed.
Feel free to re-open if you still have this issue.
Best Regards,
Jonathan

authors: JonathanMagnan Tarmil emmatb1 osjoberg

repo: zzzprojects/html-agility-pack


text:
docs: add simple deployment guide // add test overview testing

I have corrected the basic structure.
Unfortunately I cannot give any input on the content
@vobu can you please give feedback here

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA

authors: marianfoo osigge vobu


text:
Singly linked list

irregular


text:
DevOps: Research application deployment options

Thanks to @fpindej. We will commit to Azure at least for MVP and we will see how far we can get with the free tier.


text:
咨询一下，会开发对讲功能么，或者能提供一些思路么

我们在开发国标的对讲功能，想找些借鉴

以后会做，暂时没时间。#44


text:
How can I know the css value of an application center?

点击浏览器的Automa，顶部有一个Element Selector
🫱 https://github.com/6r6/vfs-iceland-slot-monitor#usage


text:
Update access-nri-intake to v1.0.0b1

Wait for the test to complete...

repo: ACCESS-NRI/MED-condaenv


text:
Fix website title

Codecov Report

Merging #283 (00f23fd) into master (5f0583d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #283   +/-   ##
=========================================
  Coverage     75.97%   75.97%
  Complexity      683      683
=========================================
  Files            94       94
  Lines          1998     1998
  Branches        223      223
=========================================
  Hits           1518     1518
  Misses          414      414
  Partials         66       66

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5f0583d...00f23fd. Read the comment docs.


text:
Modify glossary table and PPP

Codecov Report

Merging #176 (e9f4ff6) into master (b02c7d0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #176   +/-   ##
=========================================
  Coverage     73.81%   73.81%
  Complexity      536      536
=========================================
  Files            93       93
  Lines          1810     1810
  Branches        213      213
=========================================
  Hits           1336     1336
  Misses          391      391
  Partials         83       83

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: codecov-commenter gabyang


text:
Update PPP

@javinchua amended


text:
Update Non-Functional Requirements in DeveloperGuide.md

Closes #8

Lgtm


text:
How can I use the adapters for BART model in Language generation task?

Do anyone has some ideas in this scenarios? recently I am also doing this.

Thanks @JoPfeiff

authors: dinethnarada lavine-lmu

repo: Adapter-Hub/adapter-transformers


text:
ex4_js-objects-part2

merge

repo: AlinaAprel/external-courses


text:
Use SQL to create a table with GENERATED COLUMN

Won't merge. Asked in Slack but no answers.

repo: AmadeusITGroup/spark-perf-hikes


text:
Create a good PPT taking screenshots from main site, referring what tasks to be done, which tasks to be done serially, then create a issue list in issue md

sir, i would like to resolve this issue

Please assign me and guide regarding this .
Thank you

Hello , can I work on this issue?

Hello , can I work on this issue?

yes go on, remember it's a project so put each and every details with which you need to work on, order which fix after which...

could i work on this issue?

could i work on this issue? @ArchismanKarmakar

go ahead, check out:

@ArchismanKarmakar shall i create the issue list for current issues only? or if u have new issues to be added in future then i could add them as well.

@ArchismanKarmakar shall i create the issue list for current issues only? or if u have new issues to be added in future then i could add them as well.

Yes this project has future issues and you can guess what those are, ig. So you can just give a rough idea of those.


text:
day9

fixed it

thank you for contributing

repo: ArchismwanChatterjee/C


text:
Add Issues section on Github Repo

This was resolved by going to the Settings of the repo and heading to Options -> Features -> Check "Issues"

repo: ArpithaVijayakumar/WolfTrack


text:
Forgot to actually check that the top-level object is of the list type.

Closed by ad65ef8a71a909482f4621f7bfa2e0b7434367d4


text:
Code Quality And CI/CD

Thank you for the work @Abhinav-ark and @Sowrabh0-0!


text:
Fix Recovery Services Vaults pipeline

Tested with diverse different names. Using a new name leads to an 'InternalCloudError'. Using am existing to a 'Conflict with existing resource' error...

As a quick fix identity has been removed from validation tests by PR #2388. Opened a new bug #2391 to monitor going forward.

authors: AlexanderSehr eriqua

repo: Azure/ResourceModules


text:
{Dns} Fix disallowed html tags

reference to https://github.com/Azure/azure-cli/pull/30424

authors: AllyW Jing-song

repo: Azure/aaz


text:
azure-search-documents May 2022 Post Patch Updates

API change check for com.azure:azure-search-documents
API changes are not detected in this pull request for com.azure:azure-search-documents

authors: alzimmermsft azure-sdk

repo: Azure/azure-sdk-for-java


text:
Prototype: Vendor-in OTel HTTP instrumentation

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Monitor.OpenTelemetry.AspNetCore

authors: azure-sdk lmolkova

repo: Azure/azure-sdk-for-net


text:
Submitting a PR from test account only for testing

Test made. Working as expected.

authors: JimSuplizio weshaggard-test

repo: Azure/azure-sdk-tools


text:
Optimizations

As per DMS, this is a breaking change so moving into a 1.20.5-dev branch.

authors: AzureDoom bvanseg

repo: AzureDoom/AzureLib


text:
adding faqs and tech hiring timelines, fixed the submit a pr button

looks like the primary problem was the url: metadata in _config.prod.yml which was leading to bad previews. Also added the faqs to the index page. Also fixed the PR link in the header which was another misconfig in _config.prod.yml

authors: funkyvoong langdon

repo: BU-Spark/bu-spark


text:
基于readthedocs搞文档

This is almost done, check https://babassl.readthedocs.io

repo: BabaSSL/BabaSSL


text:
Center/Extent fix for aggregates

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13602/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13602/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13602/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13602/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13602/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13602/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13602/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13602/merge#BCU1XR#0

authors: CedricGuillemet bjsplat


text:
fix: add token rate

:tada: This PR is included in version 1.15.21 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: Badger-Finance/badger-sdk


text:
Update README.md

Pipelines as Code CI/pipelines-vote has failed.Error retrieving pipeline for pipelinerun pipelines-tutorial/pipelines-vote-8zgbf: failed to get pipeline: error requesting remote resource: error getting "Git" "pipelines-tutorial/git-3f11cf210a69050bc8659e319858ca11": revision error: reference not found

repo: Basavaraju-G/pipelines-vote-ui


text:
Adding mvp files with assets

Adding mvp files with assets


text:
add a crafting mapping interface

Could you elaborate? I'm not quite sure what you're talking about

like projecte.addConversision(ingedent:[],output) or projecte.addConversision(ingedent:[],outputs:[],wheights:[])

Handling the built-in item inputs(like item.of or raw string or tag) of kubejs and common JSON NBT inputs.

@BobVarioa

It would be best to add a function to handle recipes as well,like handle_repices(type,function(recipes)=>(ingedents,outputs,weights))

repo: BobVarioa/kjsprojecte


text:
need to find a way to parse *args

This is the same branch just named differently, delete this branch

repo: BrandonPacewic/TestSamples