Can we have a PHP 7.2/PHP 7.3 security release ? (CVE-2023-30536)

  Problem 1
    - slim/psr7 1.5 requires php ^7.3 || ^8.0 -> your php version (7.2.34) does not satisfy that requirement.
    - slim/psr7[1.6, ..., 1.6.1] require php ^7.4 || ^8.0 -> your php version (7.2.34) does not satisfy that requirement.
    - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest].
    - roave/security-advisories dev-latest conflicts with slim/psr7 <1.6.1.
    - Root composer.json requires slim/psr7 ^1.4 -> satisfiable by slim/psr7[1.4, 1.5, 1.6, 1.6.1].

    - slim/psr7 1.5 requires php ^7.3 || ^8.0 -> your php version (7.2.34) does not satisfy that requirement.
    - slim/psr7[1.6, ..., 1.6.1] require php ^7.4 || ^8.0 -> your php version (7.2.34) does not satisfy that requirement.
    - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest].
    - roave/security-advisories dev-latest conflicts with slim/psr7 <1.6.1.
    - Root composer.json requires slim/psr7 ^1.4 -> satisfiable by slim/psr7[1.4, 1.5, 1.6, 1.6.1].

See: https://github.com/phpmyadmin/phpmyadmin/actions/runs/4772858589/jobs/8485603736
Is failing because of https://github.com/Roave/SecurityAdvisories/commit/39006a790754a68b3a476069297b0cb83abb17d2
Ref: CVE-2023-30536
At phpMyAdmin we have to support PHP 7.2 on the 5.2 series. I would be most grateful if you would allow a security release to be done for PHP 7.2 versions. It looks like PHP 7.3 versions would be un-covered since 1.6 dropped them.
That would mean:

1.4.1 for PHP 7.2
1.5.1 for PHP 7.3

@williamdes  we cannot do security releases for PHP versions we do not support anymore unfortunately.
We are using typed properties in the codebase which are not supported by either PHP 7.2 or PHP 7.3.
This would be an insane amount of work.
If someone wants to raise the PR for it, I will gladly release it. Otherwise it's not going to happen.

@williamdes we cannot do security releases for PHP versions we do not support anymore unfortunately.
We are using typed properties in the codebase which are not supported by either PHP 7.2 or PHP 7.3.
This would be an insane amount of work.
If someone wants to raise the PR for it, I will gladly release it. Otherwise it's not going to happen.

We could "easily" make a branch from the last releases I mentioned, pick the security fix and release it
It's only a regex change
Seems possible, don't you think?
I can do the PRs if you validate that

@l0gicgate What can be done is to create a branch from the tag, and then git cherry-pick the commit 4fea29e910391b1883de5bf6e84b50f6900355fb, which is the security fix.
I wasn't able to do that because there are no 1.4.x and 1.5.x branches to open PRs to.

@l0gicgate What can be done is to create a branch from the tag, and then git cherry-pick the commit 4fea29e, which is the security fix.
I wasn't able to do that because there are no 1.4.x and 1.5.x branches to open PRs to.

Maybe you can create them on a fork and @l0gicgate can push the tags from them
Not needing to have a branch on the main repo as a result

Here are the branches @MauricioFauth @williamdes
https://github.com/slimphp/Slim-Psr7/tree/1.4.x
https://github.com/slimphp/Slim-Psr7/tree/1.5.x

A simple cherry-pick and it worked, tests did run perfectly (for the HeadersTest, others where failing before the PR)

https://github.com/slimphp/Slim-Psr7/pull/286 (1.4.x)
https://github.com/slimphp/Slim-Psr7/pull/287 (1.5.x)

Should I open another PR on 1.4 and 1.5 to fix the currently failing tests ?

Here are the releases:

https://github.com/slimphp/Slim-Psr7/releases/tag/1.4.1
https://github.com/slimphp/Slim-Psr7/releases/tag/1.5.1

Thank you @MauricioFauth @williamdes  for these contributions!
cc: @akrabat
I am closing as resolved now feel free to re-open if there's anything

Thanks @l0gicgate ! 🎉 🚀
PS: The bot says (https://github.com/github/advisory-database/pull/2233#issuecomment-1541563033) that the advisory needs a manual update here: https://github.com/slimphp/Slim-Psr7/security/advisories/GHSA-q2qj-628g-vhfw

Thanks for the update. I was used version 0.6 due to I would like to widely support many PHP versions in many places.
However, I have to bump up to minimum PHP 7.4 and Slim\PSr7 version 1.6.1 due to this security reason.
The update looks great because it seems to have nothing break since 0.6. So that I can continuous use my code without a lot of fix.
Thank you.

Only 7.2 is required https://github.com/slimphp/Slim-Psr7/blob/d3cea6539bdd0910a1e3ea2cc2a96c363c2403c3/composer.json#L31
Since 1.4 was fixed


[US] - Make text in Dark Mode more readable

As a
LiRA Map user
I want
Text to be more readable (The dark blue text on the signup/login links or on the selected page on the navigation bar)
so that
I can read all text easily.
Examples:

I intend to also fix some of the darkmode bugs that are present, like the trip data in darkmode.

I'm having difficulties changing the button themes using overrides as shown in the following:
https://mui.com/material-ui/customization/theme-components/#global-style-overrides
Dark theme plain texts now fixed to be more visible and the meta data window is also fixed.


CAMEL-19866 - Camel-Pulsar: Support HashingScheme as uri parameter fo…

…r producers
Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

/component-tests camel-pulsar


Translucent tiles change colors on mouse move when picking

Sandcastle example: link
Browser: Firefox
Operating System: Linux

Found by @lilleyse in #9399. From a comment in that PR:

Some notes -
@lilleyse Suggested that this was due to a frame buffer not being cleared, and after testing I'm pretty confident this is true. When translucency in the above Sandcastle is set to 0.01 instead of 0.5, the ghosting effect of old frame buffers loading back in is much more noticeable and gradual.
This also seems to happen when an old frame buffer is present and the camera moves, and results in a ghosting artifact like this -

I found something that might be of note -

Scene.executeCommands calls TranslucentTileClassification.executeTranslucentCommands and TranslucentTileClassification.executeClassificationCommands, in that order.
The translucent commands function increments TranslucentTileClassification._frustumsDrawn by +=1 if hasTranslucentDepth is true. All the other places where frustumsDrawn is changed set it to 0.
In TranslucentTileClassification.executeClassificationCommands, the drawClassificationFBO only gets cleared if frustumsDrawn is greater than 1. Setting the check to >= instead of > appears to fix this bug, and does not seem to impact correctness of Scene.pick's return value in the above Sandcastle.

Is it possible for frustumsDrawn to become greater than 1? In Scene.executeCommandsInViewport, it is set to 0 in updateAndClearFramebuffers before the call to executeCommands, so at first glance it looks like it it isn't. @lilleyse @likangning93 Any thoughts, maybe I'm missing something?

I don't remember all the details but I believe frustumsDrawn is there in case the scene renders multiple frustums like when log depth is disabled (scene.logarithmicDepthBuffer = false)

Update - I believe this bug happens because Picking.pick might call TranslucentTileClassification's execute commands before the classification's clear function has a chance to run during the last render.

TranslucentTileClassification stores an accumulationFBO if there are more than one frustums using the classification. In the clear function, this is handled by always clearing the drawClassificationFBO and only clearing the accumulationFBO if frustumsDrawn > 1.
The check if (this._frustumsDrawn > 1) in executeClassificationCommands before clearing the looks like an optimization to avoid clearing the classification FBO both in the execute function and in the clear function.
It is possible for the picking function to call the two execute functions in TranslucentTileClassifications in between the time that the render executes the translucent classification commands and clears the buffer for the next frame. This is because Scene calls updateAndClearFrameBuffers before it calls executeCommands in executeCommandsInViewport.

I wasn't sure what the best way to test this was but I figured that with the above thinking, the bug could be replicated outside of picking by only clearing the classification FBO in clear if frustumsDrawn > 1. This would simulate the behavior of not clearing the FBO in between consecutive calls to executeClassificationCommands. With this change, the same ghosting artifacts can be seen because the uncleared FBO stacks on itself without picking -

A better solution might be to force the pick function to clear the classification FBO if the commands are being executed as part of a pick rather than a render. I'm not sure how easy of a change that'd be, so for now I opened a PR with the simpler change - https://github.com/CesiumGS/cesium/pull/9440.


Despite missing variable file test is executed

By mistake I provided a variable file that could not be found under this path:
--variablefile "./variables/testvariables.py"
But the test is executed - and PASSED.
How this?

 JsonPreprocessor

 [robotframework] Despite missing variable file test is executed


Expand game board size to 11x11; Add letters in initial tiles

@BrendanOswego it’s most likely my fault Travis is failing, I was doing a quick fix and miss d punting the file. There seems to be a formatting error which is making all the builds fail/error. I will fix it right away.

@BrendanOswego How do these changes look? You're the better expert here.

Hi @BrendanOswego ,
In JavaScript, I don’t think it’s a serious issue that needed to be revised at this stage because unlike Java, JavaScript is weekly typed and the var is function scope which is an simple and early introduced feature.
If you trace the source code of Vue.js written by the Vue inventor, you’ll find that he use var instead of const to declare a constant. I understand it’s good to use let and const which are block scope, but this should be a low priority refactoring issue comparing to a logic error.
This is only my shallow opinion. Please feel free to correct me if I got anything wrong.


Inconsistent spacing between amount and tick mark

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Send a money request from account A to account B
Settle the requested amount from account B
Look at the "settled up [amount]" and tick mark

Expected Result:
There should be a spacing between the amount and the tick mark
Actual Result:
There is no space between the amount and the tick mark
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.14-10
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://github.com/Expensify/App/assets/43996225/17cd4b13-77f4-4ae0-93a0-f307db896f4f

Expensify/Expensify Issue URL:
Issue reported by: @nathan-mulugeta
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684143189663259
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
Inconsistent spacing between amount and tick mark
What is the root cause of that problem?
no margin between icon and text
What changes do you think we should make in order to solve the problem?
surround icon with
<View style={styles.iouPreviewBoxCheckmark}>
    <Icon/>
</View>

What alternative solutions did you explore? (Optional)
N/A

Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
We are passing style to the Icon component in here:
https://github.com/Expensify/App/blob/f013fe2d26930bffb90e23620f8360743a0d2ea8/src/components/ReportActionItem/ReportPreview.js#L124
But inside Icon component we don't have style props, so we don't see any margin here.
What changes do you think we should make in order to solve the problem?
In stead of using style props we should use additionalStyles props for Icon component, we also need to make sure the margin is consistent with the Checkmark in IOUPreview.
              <Icon
// we should use additionalStyles instead of style here
                     additionalStyles={[styles.ml1]}
                     src={Expensicons.Checkmark}
                     fill={themeColors.iconSuccessFill}
                />

What alternative solutions did you explore? (Optional)

I think if you change code like this, the bug will disappear
App/tree/main/src/styles line 2486:
current :
iouPreviewBoxCheckmark: {
marginLeft: 4,
alignSelf: 'center',
}
Change it:
iouPreviewBoxCheckmark: {
marginLeft: 5,
alignSelf: 'center',
}
Is it easy, right ?

Hey @ahmedGaber93 Please make sure to wait until the job is in Upwork before adding a proposal to the GH.

Thanks @Christinadobrzyn.
But guideline here recently changed to allow proposal at any time

You can propose solutions on any issue at at any time, but if you propose solutions to jobs before the Help Wanted label is applied, you do so at your own risk. Proposals will not be reviewed until the label is added and there is always a chance that we might not add the label or hire an external contributor for the job.

I think if you change code like this, the bug will disappear App/tree/main/src/styles line 2486:
current : iouPreviewBoxCheckmark: { marginLeft: 4, alignSelf: 'center', } Change it: iouPreviewBoxCheckmark: { marginLeft: 5, alignSelf: 'center', }
Is it easy, right ?

Hey @lobcare, please follow the proposal template: https://github.com/Expensify/App/blob/main/contributingGuides/PROPOSAL_TEMPLATE.md

Thanks @jasperhuangg for the Review!
@ahmedGaber93 Let us know when is PR is ready for Review!

@Santhosh-Sellavel PR is ready for review.

I like finding bugs
So I made PR yesterday
But you need my upwork account
I don't have it
In this case, what should I do?
Thanks.
On Thu, May 18, 2023 at 5:08 PM ahmedGaber93 @.***>
wrote:

@Santhosh-Sellavel https://github.com/Santhosh-Sellavel PR
https://github.com/Expensify/App/pull/19222 is ready for review.
—
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/issues/19049#issuecomment-1553724523,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6N2ACDMIG7XGFPIO32R36LXG2MWJANCNFSM6AAAAAAYD7EEKY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@lobcare
If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!
Post your questions on the channel, so people will address your queries.
For now, Upwork is mandatory for getting paid.

Hired in Upwork - https://www.upwork.com/jobs/~0172355caaa1314f42

@Nathan-Mulugeta as reporter
@Santhosh-Sellavel as C+
@ahmedGaber93 as contributor

@Santhosh-Sellavel what do you think of a regression test for this?

@Santhosh-Sellavel what do you think of a regression test for this?

Not needed here as it's a small UI polish cc: @jasperhuangg

Hi, Santhosh
It's me Jack and a new member of Expensify Slack Channel.
Actually I have some problems contributing to Expensify.
I don't have my upwork account now because it is blocked.
I know once it is blocked I can't recover it.
And then I don't know exactly how to work for Expensify as a guest.
If possible, kindly teach me.
If possible, I wanna collaborate with you.
I think I would be helpful to you.
I am waiting for your reply.
Thanks a lot for taking your time.
Best regards.
Jack
On Fri, May 19, 2023 at 5:41 AM Santhosh Sellavel @.***>
wrote:

Thanks @jasperhuangg https://github.com/jasperhuangg for the Review!
@ahmedGaber93 https://github.com/ahmedGaber93 Let us know when is PR is
ready for Review!
—
Reply to this email directly, view it on GitHub
https://github.com/Expensify/App/issues/19049#issuecomment-1553618760,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6N2ACFLVNZ6ASQYG6AU6T3XG2CPLANCNFSM6AAAAAAYD7EEKY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@lobcare I've already replied here. Further queries post your questions on channel

Ready for payment but there are some additional convos on the PR - @Santhosh-Sellavel @luacmartins can you confirm if this can be paid or if we're working on something else first?
Do we need a regression test for this?

@Christinadobrzyn yes, we can pay that one. We're addressing those in a separate issue.

Awesome! Thanks for confirming @luacmartins
Looks like this isn't eligible for a speed bonus (PR created May 18th - merged May 23rd)
Paid in Upwork based on this - https://github.com/Expensify/App/issues/19049#issuecomment-1564949792
Let me know about any regression tests!

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@Santhosh-Sellavel] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/18486
[x]  [@Santhosh-Sellavel] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/18486/files#r1215085067
[x]  [@Santhosh-Sellavel] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A Should be caught based on the check list
[x]  [@Santhosh-Sellavel] Determine if we should create a regression test for this bug. N/A
[x]  [@Santhosh-Sellavel] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. N/A
[x]  [@Christinadobrzyn] Link the GH issue for creating/updating the regression test once above steps have been agreed upon: N/A


Error in OSX 10.11.2

The app starts up, but when I click on start I get these messages.
I am running version 0.4.2.

I get the same message when running version 0.4.2 also. I tried running Driveshare a few weeks ago, and it was unable to tell me the amount of free space I had. Now I get a specific figure - which is an improvement.

@ShaunHoyes @kstarev Fixed. Will go out in the next release.

Perfect! Thanks.
On Wed, Dec 23, 2015 at 6:20 PM, Shawn Wilkinson<EMAIL_ADDRESS>wrote:

Closed #127 https://github.com/Storj/driveshare-gui/issues/127.
—
Reply to this email directly or view it on GitHub
https://github.com/Storj/driveshare-gui/issues/127#event-499835237.


MNT: Create dependabot.yml for workflow auto updates

As recommended by https://scientific-python.org/specs/spec-0008/#pin-github-actions-release-workflows-to-their-full-release-commit-shas , this PR changes adds a dependabot.yml file to enable future automatic updates of GitHub Actions workflow(s) in this repository.
This is an automated update made by the batchpr tool :robot: - feel free to close if it doesn't look good! You can report issues to @pllim.
:ghost:

The CI failure is unrelated.


Sync master to upstream

It will incorporate those four commits, in addition to our local changes:
$ git log -4 --pretty=oneline
2cd295d1a74e56a2f1cbe9d2fcb25dd26280f620 (HEAD -> upstream, upstream/master, origin/upstream) redis_sentinel.conf.j2: Support sentinel rename-command option (#245)
0c327bbbb89ebb6fe830ec27acc32172c2290bb7 Set additional config through a variable (#244)
b0be6be4cb3a9cfd75e31845992abe23248ca4d6 Add protected-mode option to template config files (#209)
6362fc1859253b3ac852baeed8ec29272aaa3201 (tag: 1.2.8) Add redis 6.0.* checksums. (#240)

We need the latest change, redis_sentinel.conf.j2 change, but bringing all shouldn't cause any harm.  Regarding the protected-mode, we'll explicitly sets protected-mode yes with the new redis replicas.  And also, I'll add protected-mode: false to the exiting redis, just in case.

Pushed a new branch for ansible-onesignal.
https://github.com/OneSignal/ansible-redis/tree/do-not-flush-rebase-20200707

@jwilm, let me know if there is any issue with this merge.  We need, at least, the last commit for redis-sentinel deployment.


Fix Extension model paths

This PR:

fixes paths used by the Extension class.
Adds logging in ProtoToJavaMapperPlugin

Spine version advanced to 0.10.29-SNAPSHOT

@armiol, PTAL.


TGI not working with AMD gpus

System Info
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:  jammy
GPU: RX 6900
Information

[X] Docker
[X] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
conda create -n text-generation-inference python=3.9
conda activate text-generation-inference
PROTOC_ZIP=protoc-21.12-linux-x86_64.zip
curl -OL https://github.com/protocolbuffers/protobuf/releases/download/v21.12/$PROTOC_ZIP
sudo unzip -o $PROTOC_ZIP -d /usr/local bin/protoc
sudo unzip -o $PROTOC_ZIP -d /usr/local 'include/*'
rm -f $PROTOC_ZIP
BUILD_EXTENSIONS=True make install # Install repository and HF/transformer fork with CUDA kernels
make run-falcon-7b-instruct
Expected behavior
Hello,
Cant run TGI with my gpu

We are currently working on AMD support.


Unable to convert argument to type java.lang.Class

Version:  The WebLogic Deploy Tooling createDomain version is 0.12:master
I see this attribute is defined in SecurityConfiguration.json
If anyone can point me direction what might be the issue , i would be happy to fix it and do a pull request
I am trying to create domain with ActiveDirectoryAuthenticator.
when i add certain attributes i get this exception
In my model file i have provided UseRetrievedUserNameAsPrincipal: false
Caused by: oracle.weblogic.deploy.util.PyWLSTException: WLSDPLY-00008: wlst.set(UseRetrievedUserNameAsPrincipal, false) in offline mode failed : Unable to convert argument to type java.lang.Class
@com.oracle.cie.domain.script.jython.WLScriptContext.set(WLScriptContext.java:2544)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.python.core.PyReflectedConstructor.call(Unknown Source)
at org.python.core.PyJavaInstance.init(Unknown Source)
at org.python.core.PyJavaClass.call(PyJavaClass.java:891)
at org.python.core.PyObject.call(Unknown Source)
at wlsdeploy.exception.exception_helper$py.create_pywlst_exception$8(/app/local/oracle/fmw12.2.1/installer/weblogic-deploy/lib/python/wlsdeploy/exception/exception_helper.py:212)
at wlsdeploy.exception.exception_helper$py.call_function(/app/local/oracle/fmw12.2.1/installer/weblogic-deploy/lib/python/wlsdeploy/exception/exception_helper.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.call(Unknown Source)
at wlsdeploy.util.wlst_helper$py.set$3(/app/local/oracle/fmw12.2.1/installer/weblogic-deploy/lib/python/wlsdeploy/util/wlst_helper.py:70)
at wlsdeploy.util.wlst_helper$py.call_function(/app/local/oracle/fmw12.2.1/installer/weblogic-deploy/lib/python/wlsdeploy/util/wlst_helper.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.call(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at wlsdeploy.tool.util.wlst_helper$py.set$5(/app/local/oracle/fmw12.2.1/installer/weblogic-deploy/lib/python/wlsdeploy/tool/util/wlst_helper.py:72)
... 129 more
Caused by: com.oracle.cie.domain.script.jython.WLSTException: Unable to convert argument to type java.lang.Class
@com.oracle.cie.domain.script.jython.WLScriptContext.set(WLScriptContext.java:2544)

Looking at this issue. Would you attach the model file to this issue please? If you do not wish to attach the full model because of clear text values, then swipe the ActiveDirectoryAuthenticator section please.

@CarolynRountree thanks for the help
model.yml.txt

Thank you. Able to recreate. This issue will need to be fixed internally.

Closed by pull request #159

Hi @CarolynRountree
Same error occurs in ActiveDirectoryAuthenticator when I set:
UseTokenGroupsForGroupMembershipLookup: true


Question about applyPtSlOnT1

In the method [3.2] applyPtSlOnT1, there is:
       df0=(df0/close[loc]-1)*events_.at[loc,'side'] # path returns
This line is the same as in the book, however what is the point of multiplying the returns by the predicted side: *events_.at[loc,'side']? Wouldn't this change the sign of the returns and thus create an error when the barriers are computed on the next line? I know this is not a bug, so I'm sorry about asking here.

what is the column "side" about ?
Does it represent long as 1, short as -1 ????

Yes, this is my understanding. Side represents long as 1 and short as -1. The side parameter is the prediction of the first step of the algorithm. It is used in the meta-labeling part (second step). However, I don't understand why it's necessary to multiply by it.

@ivan-vasilev a positive return is only beneficial if you're long. If you're short it's a negative outcome. The reverse is also true, a negative return is only beneficial if you're short. If you're long it's a negative outcome. The side is a binary variable indicating whether you are long or short.
Example:
Long positions:
+1% * 1 (side) = +1% (good)
-1% * 1 (side) = -1% (bad)

Short positions:
+1% * -1 (side) = -1% (bad)
-1% * -1 (side) = +1% (good)


Change from 1.5.6 to 2.0.0 and appears a "Completed 401 Unauthorized"

I just "bundle update", and the this error starts appearing while invoking: before_action :authenticate_user!
Im' using device 4.3.0 and jwt gems for authentication.
My code is:
class UsersController < ApplicationController
  before_action :authenticate_user!

  (...)
end

# Helper module for you to use on your app and in your Strategy
# Don't add "Helper" to its name and rails won't load it has a view helper module.
# "app/helpers/jwt_wrapper.rb"

module JWTWrapper
  extend self

  def encode(payload, expiration = nil)
    expiration ||= Rails.application.secrets.jwt_expiration_minutes

    payload = payload.dup
    payload['exp'] = expiration.to_i.minutes.from_now.to_i

    JWT.encode payload, Rails.application.secrets.secret_key_base
  end

  def decode(token)
    begin
      decoded_token = JWT.decode token, Rails.application.secrets.secret_key_base

      decoded_token.first
    rescue
      nil
    end
  end
end

# Use this hook to configure devise mailer, warden hooks and so forth.
# Many of these configuration options can be set straight in your model.
Devise.setup do |config|
  (...)

  config.warden do |manager|
    # Registering your new Strategy
    manager.strategies.add(:jwt, Devise::Strategies::JsonWebToken)

    # Adding the new JWT Strategy to the top of Warden's list,
    # Scoped by what Devise would scope (typically :user)
    manager.default_strategies(scope: :user).unshift :jwt
  end

  (...)
end

# Your actual JWT Strategy
# "config/initializers/core_extensions/devise/strategies/json_web_token.rb"

module Devise
  module Strategies
    class JsonWebToken < Base
      def valid?
        request.headers['Authorization'].present?
      end

      def authenticate!
        return fail! unless claims
        return fail! unless claims.has_key?('user_id')

        success! User.find_by_id claims['user_id']
      end

      protected ######################## PROTECTED #############################

      def claims
        strategy, token = request.headers['Authorization'].split(' ')

        return nil if (strategy || '').downcase != 'bearer'

        JWTWrapper.decode(token) rescue nil
      end
    end
  end
end

Any idea?, thanks!

Hi @glarrai1,
thanks for the detailed report. Please make sure your exp claim is an unix timestamp and the decode method no longer provides a default algorithm. Please make sure to set a algorithm when decoding the token.
For further debugging help I recommend to open a ticket on the devise repository.
Sorry to hear that you run into troubles.

Thanks @excpt , including the algorithm explicit (using the default one anyway; 'HS256'); now the last 2.0.0 version works ;)


New version: AWSS3 v0.7.0

Registering package: AWSS3
Repository: https://github.com/JuliaCloud/AWSS3.jl
Created by: @rofinn
Version: v0.7.0
Commit: c881edf4318dd0e78de93b0b78f3baa440e0e0cb
Reviewed by: @rofinn
Reference: https://github.com/JuliaCloud/AWSS3.jl/commit/c881edf4318dd0e78de93b0b78f3baa440e0e0cb#commitcomment-38884980

NOTE: This is a breaking change to match some corresponding breaking changes in FilePathsBase.jl.


"TypeError: Not bool" on the initial insert

Hi,
Please find the traceback for the crash on the very first insert into AnnaDB:
https://gist.github.com/taurus-forever/56492ae09c13b94e1a4788241d432a34
The command was copied from the documentation:
https://annadb.dev/documentation/insert/#example

Hi @taurus-forever
Thank you for the issue!
There is a typo in the query. Please, use b|true| instead of b|True|. Python syntax sneaked in :)
I'll fix the doc soon

The doc is fixed.

The fix is confirmed. Resolved. Tnx!


Fresh new app cannot link to webserver

So today it's been the apocalypse 💣 🔥
I made the following:
react-native init mobile-apps
cd mobile-apps
See the gif for the ending (I don't know how to explain it with words):

Note that:

App never opens.
run-ios ignores the running webserver and throws a new terminal to open it.
If I let the popped terminal to be the webserver it fails in the exactly same way.
I downgraded and failed again.
Same versions with fresh new baby works like a charm in another mac.

Versions:

react-native 0.40.0
node 7.4.0

Note: There's only one difference. The mac with the working project is a 10.11 the one failing a 10.12. Tho, a fella has the project working on a 10.12. Well, for God's sake I have this project working this morning under 10.12.

I found this error which message makes sense due to the issue behaviour:
PhaseScriptExecution Start\ Packager /Users/rigel/labs/mobile-apps/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Script-006B79A01A781F38006873D1.sh
    cd /Users/rigel/labs/mobile-apps/node_modules/react-native/React
    /bin/sh -c /Users/rigel/labs/mobile-apps/ios/build/Build/Intermediates/React.build/Debug-iphonesimulator/React.build/Script-006B79A01A781F38006873D1.sh

Error: Couldn't resolve host "localhost"

Problem solved. For some reason this essential line went missing in /etc/hosts:
<IP_ADDRESS> localhost
Which raises 2 questions?

Shouldn't React Native be addressing to <IP_ADDRESS> instead of localhost? At the end, localhost it's just an alias.
Can be place a more clear error message?


Added direction and file_system arguments to cisco_file_transfer

Hi, I amended the cisco_file_transfer module to allow 'get' operations. Actually the secret (i.e. enable password) is not used yet but relates to issue https://github.com/ktbyers/netmiko/issues/647.
Markus

@mjuenema I am not actively maintaining this. I will look at the NAPALM project if you are doing config operations (including napalm-ansible).
There also are network device file transfer mechanisms in ntc-ansible.


指定模型本地路径后仍然需要下载模型

您好，我在指定本地路径后，仍然需要到 HuggingFace 下载，结果报错。我希望知道哪里设置错了。我想训练 llava-llama3-8b。

命令：NPROC_PER_NODE=1 xtuner train llava_llama3_8b_instruct_quant_clip_vit_large_p14_336_e1_gpu1_pretrain --deepspeed deepspeed_zero3_offload
配置文件：

# Model
llm_name_or_path = '/root/autodl-tmp/Models/Meta-Llama-3-8B-Instruct'
visual_encoder_name_or_path = '/root/autodl-tmp/Models/clip-vit-large-patch14-336'

报错：

Traceback (most recent call last):
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/utils/_errors.py", line 304, in hf_raise_for_status
    response.raise_for_status()
  File "/root/miniconda3/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct/resolve/main/config.json

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/root/miniconda3/lib/python3.10/site-packages/transformers/utils/hub.py", line 399, in cached_file
    resolved_file = hf_hub_download(
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
    return fn(*args, **kwargs)
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1221, in hf_hub_download
    return _hf_hub_download_to_cache_dir(
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1325, in _hf_hub_download_to_cache_dir
    _raise_on_head_call_error(head_call_error, force_download, local_files_only)
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1823, in _raise_on_head_call_error
    raise head_call_error
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1722, in _get_metadata_or_catch_error
    metadata = get_hf_file_metadata(url=url, proxies=proxies, timeout=etag_timeout, headers=headers)
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
    return fn(*args, **kwargs)
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 1645, in get_hf_file_metadata
    r = _request_wrapper(
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 372, in _request_wrapper
    response = _request_wrapper(
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/file_download.py", line 396, in _request_wrapper
    hf_raise_for_status(response)
  File "/root/miniconda3/lib/python3.10/site-packages/huggingface_hub/utils/_errors.py", line 321, in hf_raise_for_status
    raise GatedRepoError(message, response) from e
huggingface_hub.utils._errors.GatedRepoError: 401 Client Error. (Request ID: Root=1-66546098-2a77795a4fb2e26d341a2147;99e64d9b-c281-4e7a-a289-d953b8deeb90)

Cannot access gated repo for url https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct/resolve/main/config.json.
Access to model meta-llama/Meta-Llama-3-8B-Instruct is restricted. You must be authenticated to access it.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/root/miniconda3/lib/python3.10/site-packages/xtuner/tools/train.py", line 360, in <module>
    main()
  File "/root/miniconda3/lib/python3.10/site-packages/xtuner/tools/train.py", line 353, in main
    runner = RUNNERS.build(cfg)
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/registry/registry.py", line 570, in build
    return self.build_func(cfg, *args, **kwargs, registry=self)
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/registry/build_functions.py", line 196, in build_runner_from_cfg
    runner = runner_cls.from_cfg(args)  # type: ignore
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/runner/_flexible_runner.py", line 423, in from_cfg
    runner = cls(
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/runner/_flexible_runner.py", line 403, in __init__
    self.register_hooks(default_hooks, custom_hooks)
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/runner/_flexible_runner.py", line 1430, in register_hooks
    self.register_custom_hooks(custom_hooks)
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/runner/_flexible_runner.py", line 1410, in register_custom_hooks
    self.register_hook(hook)
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/runner/_flexible_runner.py", line 1310, in register_hook
    hook_obj = HOOKS.build(hook)
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/registry/registry.py", line 570, in build
    return self.build_func(cfg, *args, **kwargs, registry=self)
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/registry/build_functions.py", line 121, in build_from_cfg
    obj = obj_cls(**args)  # type: ignore
  File "/root/miniconda3/lib/python3.10/site-packages/xtuner/engine/hooks/dataset_info_hook.py", line 24, in __init__
    self.tokenizer = BUILDER.build(tokenizer)
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/registry/registry.py", line 570, in build
    return self.build_func(cfg, *args, **kwargs, registry=self)
  File "/root/miniconda3/lib/python3.10/site-packages/mmengine/registry/build_functions.py", line 121, in build_from_cfg
    obj = obj_cls(**args)  # type: ignore
  File "/root/miniconda3/lib/python3.10/site-packages/transformers/models/auto/tokenization_auto.py", line 837, in from_pretrained
    config = AutoConfig.from_pretrained(
  File "/root/miniconda3/lib/python3.10/site-packages/transformers/models/auto/configuration_auto.py", line 934, in from_pretrained
    config_dict, unused_kwargs = PretrainedConfig.get_config_dict(pretrained_model_name_or_path, **kwargs)
  File "/root/miniconda3/lib/python3.10/site-packages/transformers/configuration_utils.py", line 632, in get_config_dict
    config_dict, kwargs = cls._get_config_dict(pretrained_model_name_or_path, **kwargs)
  File "/root/miniconda3/lib/python3.10/site-packages/transformers/configuration_utils.py", line 689, in _get_config_dict
    resolved_config_file = cached_file(
  File "/root/miniconda3/lib/python3.10/site-packages/transformers/utils/hub.py", line 417, in cached_file
    raise EnvironmentError(
OSError: You are trying to access a gated repo.
Make sure to have access to it at https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct.
401 Client Error. (Request ID: Root=1-66546098-2a77795a4fb2e26d341a2147;99e64d9b-c281-4e7a-a289-d953b8deeb90)

Cannot access gated repo for url https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct/resolve/main/config.json.
Access to model meta-llama/Meta-Llama-3-8B-Instruct is restricted. You must be authenticated to access it.
[2024-05-27 18:29:49,767] torch.distributed.elastic.multiprocessing.api: [ERROR] failed (exitcode: 1) local_rank: 0 (pid: 19592) of binary: /root/miniconda3/bin/python
Traceback (most recent call last):
  File "/root/miniconda3/bin/torchrun", line 8, in <module>
    sys.exit(main())
  File "/root/miniconda3/lib/python3.10/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 346, in wrapper
    return f(*args, **kwargs)
  File "/root/miniconda3/lib/python3.10/site-packages/torch/distributed/run.py", line 806, in main
    run(args)
  File "/root/miniconda3/lib/python3.10/site-packages/torch/distributed/run.py", line 797, in run
    elastic_launch(
  File "/root/miniconda3/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 134, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/root/miniconda3/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 264, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
/root/miniconda3/lib/python3.10/site-packages/xtuner/tools/train.py FAILED
------------------------------------------------------------
Failures:
  <NO_OTHER_FAILURES>
------------------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2024-05-27_18:29:49
  host      : autodl-container-514f11b352-ce13d0dd
  rank      : 0 (local_rank: 0)
  exitcode  : 1 (pid: 19592)
  error_file: <N/A>
  traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
============================================================

谢谢帮助！

您好，我好像也遇到了和您一样的问题，请问您解决了吗？


Color tolerance doesn't work properly

There are images that are perceived by MC as colored, but in appearance they are black and white.
E.g.
https://mangadex.org/chapter/4927a00e-8748-4435-bc8c-0d71694759e0/5

When I use the minimum value of the "Color Tolerance" parameter of 250, at which such images begin to be processed by MC, there are color images that also begin to be processed.
https://mangadex.org/chapter/4927a00e-8748-4435-bc8c-0d71694759e0/21

At the same time, if I use inference.py from https://github.com/xiaogdgenuine/Manga-Colorization-FJ to colorize the same images, but downloaded locally, such thing doesn't occur.

It's getting colorized for me. Mangadex preloads some panels left and right, so even if you open a single page, it may colorize the other pages first, and if any of the pages like https://mangadex.org/chapter/4927a00e-8748-4435-bc8c-0d71694759e0/1 are already colored, it may print out a log as such.
If this is not the case, please provide me with more example links.

After seeing your screenshot I noticed that I didn't update the addon, my first post was made with addon version 0.3.1. After I updated it to 0.4.0, MC started working fine.
My apologies and extend my deepest gratitude for your patience.

The Chapter 15 Crisis example has some bright yellow lettering in the original. That shows how difficult it can be to decide whether to leave the image alone or go ahead and recolor it. I have thought that adding some way to show the original or force coloring on a particular image might be valuable, maybe in a right-click context menu so it is not always visible.

Injecting small buttons on every such image should be easy. Visibility may be controlled by the extension globally.

It would be great if such a feature would be implemented. It makes no difference whether it's via right mouse click or button, although I'm leaning more towards the button as, IMHO, a more convenient option.

I am adding the show original idea as a new issue since this one is already closed. I'm reluctant to jump in and work on it right now while BinitDOX is in the middle of so many big exciting changes.


encoding: Add graphql schemas support

Is your feature request related to a problem? Please describe.
Missing capability for converting CUE programs to valid graphql schemas
Describe the solution you'd like
Add a package to encode graphql, update CLI capabilities to be able to export; cue export *.cue graphql:namefile.graphqls
Describe alternatives you've considered
Additional context
I will work on this feature so please assign it to me :+1:

glad this is being thought about. I was thinking about this aspect a few days ago.

I suspect you will have to create a proposal for this. Here are some things to think about while devising what this would look like and help others to know the scope of this feature.

Are you trying to only generate the types, or also queries and mutations? How would they be differentiated?
How will optional vs required be handled?
How will references be handled? structs vs definitions comes to mind here?
Default values / disjunctions?
How would query / mutation args be defined?

A good place to start is by creating input / output pairs to show what the codec would produce

How would you handle the ID type, given CUE does not have this natively? (This is generally the problem of target basic types which have no representation in CUE)
Conversely, there are valid CUE expressions which are hard to translate

foo: int | *42
bar: #CustomType1 | #CustomType2

What should happen in the above cases?
A couple of suggestions:

It could be easier to start with a stand alone tool, which uses the Go API. This should make it easier to frame out the problem and inform a proposal
https://github.com/cue-lang/cue/issues/822 is a relevant issue to be aware of

I would argue, that a solution to codegen GraphQL queries/mutations ought to be similar to generating routes / paths in OpenAPI, and perhaps even member functions for generating types in programming languages?
It is unclear to me if cue should take on this much domain specific knowledge, given its wide applicability... and the wide variety of concepts in potential codegen targets.

Where would the line be drawn for export target support? Which languages, technologies, and platforms should be built into the core tool?
Should tools like this be written as 3rd party? There is a rich GoAPI to do so
How can the trade off between tool bloat vs ecosystem fragmentation guide this?
Can a set of guidelines be created such that the tools can be developed independently yet have consistent patterns / concepts?

Thanks for raising the issue, @qequ.
I don't really have anything to add to the excellent comments above from @verdverm and @timbunce. So I'll just quote some of their points and add a couple of comments.

A good place to start is by creating input / output pairs to show what the codec would produce

👍. This also helps others to understand the scope of what's being planned, how someone would hold and use such a feature.

It could be easier to start with a stand alone tool, which uses the Go API. This should make it easier to frame out the problem and inform a proposal

👍. It should be possible to experiment with support for different encodings outside of the core repo. If you are running into problems in this respect, please raise an issue.

It is unclear to me if cue should take on this much domain specific knowledge, given its wide applicability... and the wide variety of concepts in potential codegen targets.

I think answers to this sort of question (and those that followed it) will become clearer the more closely we look at what an actual design for GraphQL support would look like. So, yet another reason to experiment and iterate.

Should tools like this be written as 3rd party?

Our current thinking is that there should probably be some ground in between "core" and "3rd party". Much like the x repos in the Go world, but with more clearly defined ownership and delegation.

Does putting tools like this into the cue cli push long-term support on the core devs?

Possibly, and thank you for raising this concern ❤. Alternatively, it forces us to think about better models of ownership and delegation within the CUE project, which is to my mind a better long term goal for everyone involved, and the project itself. This applies to whether something is core, and x project/feature, or third party.

Perhaps graphql could serve as an example by being developed in a separate repo but with input from the cue team to help establish those patterns / concepts which could act as a model for other integrations.

We would be delighted to participate in any such design exploration. Furthermore, to ensure that the Go API, tools etc fully support people in doing that. Indeed as both @verdverm and @timbunce have suggested, providing an example to people of how a decision/design/proposal was reached after collaborative discussion etc would be a valuable contribution in and of itself, regardless of the outcome.

how would be treated as an x

It's a reference to how we determine the best home for the resulting code.

I've read the Go wiki and it states that an x library is a sub repo of Go but outside of the main tree

I was making reference to the fact we might have such a concept in the CUE world. But it's not something we need to worry about now.
As @verdverm suggested, I would start by writing out some GraphQL and CUE, and showing the mapping between the two.


Site not loading on iPad

https://noagendasocial.com/@Hewy/105586437276151516

I suspect #21 will fix this.

This was fixed in v2


Takes forever to delete a single file

Type: Performance Issue
Create a file in the explorer view, then delete that file. Sometimes it simply never happens, sometimes it happens after 30+ seconds
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:20:33.924Z)
OS version: Darwin x64 19.2.0
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz (4 x 2300)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
9, 6, 4

Memory (System)
8.00GB (1.23GB free)

Process Argv
. --crash-reporter-id 4afd74ac-9e8b-48ca-a322-8ac2c5a855c3

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
   20	   123	 36052	code main
    0	    57	 36055	   gpu-process
    0	    33	 36056	   utility-network-service
    0	   279	 36057	window [1] (Welcome — elixir)
    0	   254	 36058	window [2] (,)
    0	   164	 36060	shared-process
    0	     0	 36102	     /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	    49	 36061	fileWatcher [1]
    0	    90	 36062	extensionHost [1]
    0	    98	 36063	extensionHost [2]
    0	    49	 36064	fileWatcher [2]
    0	    74	 36100	window [3] (Issue Reporter)

Workspace Info
|  Window (Welcome — elixir)
|    Folder (elixir): 0 files
|      File types:
|      Conf files:;

Extensions (13)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.4.2

prettier-vscode
esb
10.1.0

go
gol
0.39.1

gc-excelviewer
Gra
4.2.58

elixir-ls
Jak
0.16.0

vscode-docker
ms-
1.26.0

black-formatter
ms-
2023.4.1

python
ms-
2023.14.0

vscode-pylance
ms-
2023.8.30

makefile-tools
ms-
0.7.0

material-icon-theme
PKi
4.29.0

markdown-preview-enhanced
shd
0.6.8

pdf
tom
1.2.2

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30803844
2e4cg342:30602488
f6dab269:30613381
showlangstatbar:30737416
03d35959:30757346
pythonfmttext:30731395
pythoncmvfstrcf:30756944
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30804715
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30812749

Do you have any more detailed repro steps? I've tried deleting like 100 different files on my machine and have been unable to reproduce this

Thank you for your response - I don't have any further repro steps, but I have a clip.
https://github.com/microsoft/vscode/assets/54866289/537d2d96-6318-4e3e-a6ac-08088121f479

Thank you for your response - I don't have any further repro steps, but I have a clip.
Screen.Recording.2023-08-21.at.1.13.40.PM.mov

And you see this occur every time?
Here's another test

Create a file in VS Code
Leave VS Code open
Delete file from OS explorer

Is this fast?

Yes, every time.
And yes, it is immediate from OS Explorer (and also from terminal)

Can you try to install insiders and see if that will repro
https://code.visualstudio.com/insiders/

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


msc project renamed to operation

This will be the last in the row. The incoming changed need also resolving merge problems.


Srk table

Hi Patrick,
this is a lightweight PR, adding some more SRK documentation. The first commit just adds the table of all SDE solvers into docs/api/solvers/sde_solver.md. The second commit adds a Jupyter notebook to examples/, wherein I gave a walkthrough of the basics SDE simulation in Diffrax. Feel free to get rid of the second commit if you do not find it necessary :)

I removed some things from sde_example.ipynb and moved it to devdocs. I removed the table from sde_solvers.md, but I added a link pointing to the table at the bottom of sde_example.ipynb.
I feel like it is important to at least somewhere in the docs show users the canonical way of batch-solving SDEs, because Monte Carlo is the primary use case of SDE simulation. This is why I think we should really keep that part of the notebook.

Should ralston and EulerHeun also be in the table?

Should ralston and EulerHeun also be in the table?

Good point, I'll add them.

I added Ralston and EulerHeun to the table.

Okay, I like this!
I should have clearer in my past message by the way, I think only the table of SDE information needs to be in the devdocs (and it should be included in mkdocs.yml). I think the notebook you have here is really useful, so I'd actually like to include that in the main example docs!
I don't think GitHub lets me comment on notebook files so I'll leave review feedback here instead:

can you tidy up the Diffrax imports, so that it doesn't appear twice?
Can you standardise the notation to the same used throughout the rest of the Diffrax documentation, e.g. see here: https://docs.kidger.site/diffrax/usage/how-to-choose-a-solver/#stochastic-differential-equations (Note how I use y instead of Y, w instead of W etc -- the style and characters I use are chosen to allow using equivalent notation for ODEs/SDEs/CDEs interchangably.)
I'd like to title this 'Advanced SDE example' since it includes topics like Levy area, Monte Carlo etc.
Let's have just print(f"Minimal levy area for SPaRK: {solver.minimal_levy_area}.") (no __name__) -- I prefer simplicity of code over simplicity of printout in these examples.
It is very important to have h > bm_tol -- can you briefly add a sentence explaining why?
I'd really prefer for examples to not rely on private functionality, or functions defined in tests. Let's rewrite the 'optimizing wrt SDE parameters' section to be a bit simpler, focusing on just the optimization?
For the ito-vs-stratonovich, different noise types, etc., then I'd like to avoid duplicating the information already in https://docs.kidger.site/diffrax/usage/how-to-choose-a-solver/#stochastic-differential-equations -- can you just link to that instead? (And add any extra information there if you think something is missing.)

Hi Patrick!
I agree with all of your comments and I made the appropriate modifications. Two notes however:

In the definition of commutative noise you originally used \mu and \sigma. Because I instead use f and g everywhere else, including in AbstractSRK documentation, I opted to just convert everything to f and g. I assume you don't mind the change too much as long as the notation is consistent everywhere. LMK
I agree I shouldn't use a private method such as _batch_sde_solve in the example, so I just wrote an equivalent in the notebook. However, several people (including two of James's new students and another person at the Edinburgh conference) were asking me about canonical ways to do Monte Carlo with Diffrax, so we could consider writing an equivalent of _batch_sde_solve in Diffrax proper and making it public. I don't feel very strongly about this though.

Please let me know if I missed anything or if you notice anything else I should change.


Bump Minor Versions

Sorry @reznord 😆 Similar to what you did, I think, but includes minor version increases.

lol...it's fine ☺


Proposal - revise public API

I'd like to propose reworking the public API of the package to make it easier to use in upstream packages. This would be a breaking change:

Migrate public API types from classes to structs for better local reasoning. (e.g struct {Recipe,Ingredient,Step})

Upstream packages can wrap structs in a class where needed and add Idenitifiable conformance.

Improve some of the names (e.g ParsedEquipment -> Equipment, SemanticRecipe -> Recipe)
Remove parsing types from the public API (e.g IngredientAmount.value could be a Decimal rather than a ValueNode)
Provide some convenience methods like let recipe = try Recipe.from(text: String)

IMO, this would improve the consumption of the API, but would require changes in the CLI as well. What do you think, is this something you'd be open to changing in the short term, or would you prefer to keep the current API for now?

Hi @iainsmith I certainly agree with all your points and I welcome this change.
This last layer didn't get much attention. Some other things which should be rethought: IngredientTable and IngredientAmount. I was considering an option to have them as a type alias for dictionary and have some helpers to merge ingredients from outside (instead of having this inside classes). But struct will work too.

Changes merged to main, thanks @iainsmith for review.


frontend/exchange: refactor exchange deals logic

Exchange logic was largely implemented in the frontend. With this, all the logic is moved to the backend, and the whole code is simplified.
Main changes:

getExchangeDeals now has three params: coin, region and action (buy/sell) and returns already filtered exchange deals, with best deal flag already set
mv sell.tsx buysell.tsx: this component now has an action param, that allows to display different deals on the base of the enabled buy/sell tab.
all the /buy/ path has been moved to /exchange/
a lot of frontend logic (e.g. to find the best deal) is not necessary anymore and has been removed.
pocket sell mockup button removed, as it is not necessary anymore

Still todo: we should check if the bb02 firmware supports silent payments and can sell through Pocket using a backend endpoint instead of just checking the version in the frontend. This will be done in a future commit.

ping @benma for BE review :) :pray:

@benma @shonsirsha updated the code and answered the comments, PTAL :pray:


Incorporate 2017 04

This PR incorporates upstream changes between v2016.11 and v2017.04 into the lwaftr branch.  Let's see what CI does with it :)

I ran a loadtest on snabb2 and reached the normal 2MPPS 500BPP FDX bump-in-the-wire (20Gbps) target, so I think we should merge.

@wingo the CI tests used to fail in Snabb2 due to an environment problem, I think that was the cause. I'd need to look into that again. I agree with merging.


Use double quotes in installation instructions

Usage like:
pip intsall "tiled[client]"

works in the Linux default shell (bash), Mac default shell (zsh), and Windows command prompt. Using no quotes breaks in zsh and using single quotes breaks on Windows.

@jmaruland Can you confirm again that double quotes works on Windows? Just double checking.

@danielballan Quotes work on Windows, too. I tried it on a clean new environment, just in case.


ci: Build aarch64 releases on ubuntu-20.04

This matches our amd64 build and improves binary compatibility with systems using older glibc.

@lann is it okay if I merge this or are you still working on it?

Oh I forgot I was hoping @endocrimes could test the release binary to verify.


Update developing instructions in README

This probably isn't the best way to word these instructions but something like this is needed for people to be able to build and run Riot for iOS on their own machines.

Thanks @aaronraimist for the update of the doc.
I need 2 more things before accepting the PR. It is relative about contributing on matrix:

the PR must be against the develop branch
a sign-off in the PR (even as a comment)

Signed-off-by: Aaron Raimist<EMAIL_ADDRESS>


Decide on lazy log formatting in the new pylint config

Description of issue or feature request:
Using f-strings (and all types of string formatting except %-syle) in logging messages is not lazy evaluated so linters "recommend" %-style formatting.
Should we disable the related pylint warnings and use f-strings:
logging-not-lazy
logging-format-interpolation
logging-fstring-interpolation

or adhere to the recommendation.
Current behavior:
Top-level pylintrc disables logging that recommend lazy formatting globally.
New api/pylintrc does not.
Expected behavior:
Decide on a common approach.

An example approach to avoid the warnings while using f-strings which feels more like a workaround: 438c0a0

It's annoying to use a different formatting method for logging than anything else but the reasoning is solid... Most of our logging is not in a "hot loop" but some debug logs really might be used quite a lot (and the workaround only hides the warning, not the potential performance issue in those cases).
I think using %-style is fine for logging: logger.debug("processing, a=%s", a) but it's not a strong opinion -- in the opposite case we may want to do a quick review to identify hottest logging calls though.

And then there is this issue when trying to use %-style formatting but you've set up pylint to logging-format-style=new.

I had understood that using %-style implies means we would need to use logging-format-style=old anyway? Pylint docs really could have more examples.

I'm proposing we use the default logging style, meaning:

use logging-format-style=old (which is default value)
stop disabling logging-not-lazy

It looks a bit uglier (other string formatting is f-strings but logging is then based on %-formatting) but:

it's a common style
it's suggested by the google style guide
it means we don't have to think about performance when writing logging code


Removed references to question is_behavioristic in templates, reviews…

Fixes #100. This commit includes database migrations. I don't know if that's policy or if migrations should be made in develop later.

Looks good!
The policy for migrations is to make them and add them as soon as possible to the develop branch. This avoides migration conflicts from different branches.


Update sbt to 1.3.4

Updates org.scala-sbt:sbt from 1.3.3 to 1.3.4.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: semver-patch

Codecov Report

Merging #184 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #184   +/-   ##
=======================================
  Coverage   61.13%   61.13%
=======================================
  Files          36       36
  Lines        1194     1194
  Branches        7        8    +1
=======================================
  Hits          730      730
  Misses        464      464

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 7f2a694...626b7b0. Read the comment docs.


Task error on bot startup

Seen on dev.
Task exception was never retrieved
future: <Task finished coro=<background_task_spoiler_season() done, defined at /Users/bakert/pd/discordbot/bot.py:169> exception=TooFewItemsException("Expected `1` and got `0` with `{'Lost Vale'}`.  missing=`{'Lost Vale'}`",)>
Traceback (most recent call last):
  File "/Users/bakert/pd/magic/oracle.py", line 37, in valid_name
    return cards[0].name
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/bakert/pd/discordbot/bot.py", line 175, in background_task_spoiler_season
    oracle.valid_name(c['name'])
  File "/Users/bakert/pd/magic/oracle.py", line 39, in valid_name
    raise InvalidDataException('Did not find any cards looking for `{name}`'.format(name=name))
shared.pd_exception.InvalidDataException: Did not find any cards looking for `Dowsing Dagger // Lost Vale`

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/tasks.py", line 240, in _step
    result = coro.send(None)
  File "/Users/bakert/pd/discordbot/bot.py", line 177, in background_task_spoiler_season
    oracle.insert_scryfall_card(c)
  File "/Users/bakert/pd/magic/oracle.py", line 203, in insert_scryfall_card
    CARDS_BY_NAME[name] = load_card(name)
  File "/Users/bakert/pd/magic/oracle.py", line 42, in load_card
    return load_cards([name])[0]
  File "/Users/bakert/pd/magic/oracle.py", line 58, in load_cards
    raise TooFewItemsException('Expected `{namelen}` and got `{rslen}` with `{names}`.  missing=`{missing}`'.format(namelen=len(names), rslen=len(rs), names=names, missing=missing))
shared.pd_exception.TooFewItemsException: Expected `1` and got `0` with `{'Lost Vale'}`.  missing=`{'Lost Vale'}`

lost vale
arlinn, embraced by the moon
lord of lineage
...
something going on with the reverse side of double-faced cards. and we end up with them in the database twice as the end of this.
mysql> SELECT COUNT(*), name FROM face GROUP BY name HAVING COUNT(*) > 1;
+----------+--------------------------------+
| COUNT(*) | name                           |
+----------+--------------------------------+
|        2 | Adanto, the First Fort         |
|        2 | Archangel Avacyn               |
|        2 | Arguel's Blood Fast            |
|        2 | Arlinn Kord                    |
|        2 | Arlinn, Embraced by the Moon   |
|        2 | Avacyn, the Purifier           |
|        2 | Azcanta, the Sunken Ruin       |
|        2 | Bloodline Keeper               |
|        2 | Brisela, Voice of Nightmares   |
|        2 | Chittering Host                |
|        2 | Conqueror's Foothold           |
|        2 | Conqueror's Galleon            |
|        2 | Dowsing Dagger                 |
|        2 | Growing Rites of Itlimoc       |
|        2 | Hanweir, the Writhing Township |
|        2 | Itlimoc, Cradle of the Sun     |
|        2 | Legion's Landing               |
|        2 | Lord of Lineage                |
|        2 | Lost Vale                      |
|        2 | Primal Amulet                  |
|        2 | Primal Wellspring              |
|        2 | Search for Azcanta             |
|        2 | Spires of Orazca               |
|        2 | Spitfire Bastion               |
|        2 | Temple of Aclazotz             |
|        2 | Thaumatic Compass              |
|        2 | Treasure Cove                  |
|        2 | Treasure Map                   |
|        2 | Vance's Blasting Cannons       |
+----------+--------------------------------+
29 rows in set (0.06 sec)

This is just straight up BS so first thing I"m going to do is delete the dupes and add a UNIQUE constraint on face.name

The reason we don't have UNIQUE on face.name is because of meld cards. The meld side is two faces but they both have the same name (kinda). It's ugly but it's probably necessary.

This still seems mostly terrible to me but I've stopped the errors and hopefully sane-ified the database so that we don't get dupes when fixing up insert_scryfall_card to work with the new _card_cache.


nixos/octoprint: improve example

Motivation for this change
noticed in https://www.reddit.com/r/NixOS/comments/ifmg55/octoprint_plugins/ that the example will actually cause an error. Fixed the example.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

also changed it to show m33-fio as m3d-fio i guess is deprecated


Readme not clear

I consider about installing on the local environment. Should I need to run the command: composer create-project ....?

Roger, I'm updating it. Hopefully, we could work on this project since this afternoon.

Resolved with https://github.com/gsmartsolutions/gss-website/commit/9eda5fb1789f437f5956903b8f26630318d77725


Estute/install global tools

In order to use Groovy outside of the script console or specific use cases (i.e. DSL, build flow) which contain their own Groovy tooling, this script will install multiple versions of Groovy in the Global Tool Configuration. It also can be used in the future for other tools, such as JDKs, Python environments and various build tools.

Is that failing test a legitimate problem?  Looks good otherwise.

@jmbowman no, it's a flaky test. The trouble is that a lot of these tests are validating things on $JENKINS_URL/configure, which can be quite large and causes some scrolling issues. I will put in a separate PR to remove it.


Delay configuration of buf binary configuration until after the tool version is resolvable from the extension

See the (formerly) failing test - configureBufDependency grabs the toolVersion from the extension at plugin application time today, but this needs to be done after project evaluation in order to get the configured version.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


PathString implicit string converters are asymmetric

In PathString.cs
public static implicit operator PathString(string s)
        {
            return new PathString(s);
        }

Will create the unescaped new PathString while
        public static implicit operator string(PathString path)
        {
            return path.ToString();
        }

Will create the escaped ToString.

That's not great...

I thought that was the whole point of PathString? Make it easier to do "the right thing" by expecting an unescaped and outputting an escaped string. This prevents someone accidentally ToString'ing a path in its unescaped form.

@khellang We didn't specify which was wrong, just that it's asymmetric. If anything I think it's the string -> PathString converter that's wrong, it should use FromUriComponent to maintain symmetry. Unfortunately that's not how we normally to use it either.

This would be a breaking change. We'll reconsider in 2.0

@muratg we should re-triage this if we're ever going to fix it.

12f89f66a687bdb1c1b683b0d7abd2732c05eb1a


Large project builds break memory limits on vercel/netlify

Describe the bug
When building large projects on vercel/netlify sveltekit builds fails due to exceeding build memory allocations.
I believe this issue is related to vite/esbuild - kit maintainers if you feel I should post the issue elsewhere please let me know but I thought it would be best to make the issue known here first.
Context
We have migrated our codebase to sveltekit a long time ago and have been loving it. In the last few months I created a branch to upgrade our core svelte packages to the latest versions. Everything worked locally but I kept running into vague esbuild errors with every deploy to Vercel. After experimenting with many different sveltekit, esbuild and vite configs I could not get our project to build successfully on Vercel. I deployed the same code to Netlify and got a memory heap allocation error which narrowed down the cause of the issue.
Problem
I believe the issue is that during the building/bundling esbuild is transforming too many files in parallel and holding too much in memory which results in a javascript heap allocation error.
This error is easily reproducible and I have provided an example repo below which is a fork of sveltejs/realworld. I have simply cloned the src/routes/article folder 2000 times to inflate the build. This causes a build heap error on my local machine and in Vercel. If you lower the number of cloned folders 1000 builds it will build successfully on Vercel.
In our production codebase we are at a point where this error occurs only on Vercel and is blocking us from upgrading. Obviously it is not an option for us to remove routes / components from our project so if we wish to upgrade sveltekit we are forced to consider other bespoke deployment options.
For reference I know Vercel provides 8GB of memory per build.
Solution
Not sure if its possible to implement some kind of progressive build strategy to combat these large builds or perhaps this issue is originating from some internal bug within esbuild package.
Reproduction
https://github.com/Axeldeblen/realworld-big-build
run npm run build locally and deploy to vercl/netlify using default configs
remove 1000 folders and commit to trigger another deploy, it should build successfully on those platforms I have done this in this PR - https://github.com/Axeldeblen/realworld-big-build/pull/1
Logs
local build failure

<--- Last few GCs --->

[60557:0x104905000]   199087 ms: Scavenge (reduce) 4058.9 (4101.9) -> 4058.4 (4101.9) MB, 5.8 / 0.0 ms  (average mu = 0.167, current mu = 0.052) allocation failure
[60557:0x104905000]   199106 ms: Scavenge (reduce) 4060.0 (4099.6) -> 4059.4 (4100.6) MB, 5.1 / 0.0 ms  (average mu = 0.167, current mu = 0.052) allocation failure
[60557:0x104905000]   199127 ms: Scavenge (reduce) 4061.0 (4100.6) -> 4060.5 (4101.6) MB, 7.3 / 0.0 ms  (average mu = 0.167, current mu = 0.052) allocation failure

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

vercel build failure
vite v2.9.6 building SSR bundle for production...
> The service was stopped
    at /vercel/path0/node_modules/esbuild/lib/main.js:1335:25
    at /vercel/path0/node_modules/esbuild/lib/main.js:666:9
    at Socket.afterClose (/vercel/path0/node_modules/esbuild/lib/main.js:644:7)
    at Socket.emit (events.js:412:35)
    at endReadableNT (internal/streams/readable.js:1334:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
Error: Command "npm run build" exited with 1

netlify
<--- Last few GCs --->
2:48:31 PM: [1460:0x4632bd0]   194829 ms: Scavenge (reduce) 2042.0 (2050.5) -> 2041.2 (2051.5) MB, 13.5 / 0.0 ms  (average mu = 0.258, current mu = 0.264) allocation failure
2:48:31 PM: [1460:0x4632bd0]   194841 ms: Scavenge (reduce) 2042.1 (2050.5) -> 2041.2 (2051.5) MB, 6.8 / 0.0 ms  (average mu = 0.258, current mu = 0.264) allocation failure
2:48:31 PM: [1460:0x4632bd0]   194855 ms: Scavenge (reduce) 2042.1 (2050.5) -> 2041.2 (2051.7) MB, 4.9 / 0.0 ms  (average mu = 0.258, current mu = 0.264) allocation failure
2:48:31 PM: <--- JS stacktrace --->
2:48:31 PM: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
2:48:31 PM:  1: 0xa3aaf0 node::Abort() [node]
2:48:31 PM:  2: 0x970199 node::FatalError(char const*, char const*) [node]
2:48:31 PM:  3: 0xbba45e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
2:48:31 PM:  4: 0xbba7d7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
2:48:31 PM:  5: 0xd769e5  [node]
2:48:31 PM:  6: 0xd7756f  [node]
2:48:31 PM:  7: 0xd853ab v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
2:48:31 PM:  8: 0xd88f6c v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
2:48:31 PM:  9: 0xd4e73d v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
2:48:31 PM: 10: 0xd4a999 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawArray(int, v8::internal::AllocationType) [node]
2:48:31 PM: 11: 0xd4aa54 v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArrayWithFiller(v8::internal::Handle<v8::internal::Map>, int, v8::internal::Handle<v8::internal::Oddball>, v8::internal::AllocationType) [node]
2:48:31 PM: 12: 0xf914fb v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Allocate(v8::internal::Isolate*, int, v8::internal::AllocationType) [node]
2:48:31 PM: 13: 0xf9168f v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, 1>::Rehash(v8::internal::Isolate*, v8::internal::Handle<v8::internal::OrderedHashSet>, int) [node]
2:48:31 PM: 14: 0x1083568 v8::internal::Runtime_SetGrow(int, unsigned long*, v8::internal::Isolate*) [node]
2:48:31 PM: 15: 0x1448e19  [node]
2:48:32 PM: Aborted (core dumped)
2:48:32 PM: npm ERR! code ELIFECYCLE
2:48:32 PM: npm ERR! errno 134
2:48:32 PM: npm ERR<EMAIL_ADDRESS>build: `svelte-kit build --verbose`
2:48:32 PM: npm ERR! Exit status 134
2:48:32 PM: npm ERR!
2:48:32 PM: npm ERR! Failed at the<EMAIL_ADDRESS>build script.
2:48:32 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging outpu

System Info
System:
    OS: macOS 11.5.2
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 367.55 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.17.3 - ~/.nvm/versions/node/v14.17.3/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.1.3 - ~/.nvm/versions/node/v14.17.3/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 100.0.4896.127
    Firefox: 99.0.1
    Safari: 14.1.2
  npmPackages:
    @sveltejs/adapter-netlify: next => 1.0.0-next.56
    @sveltejs/adapter-vercel: next => 1.0.0-next.50
    @sveltejs/kit: 1.0.0-next.216 => 1.0.0-next.324
    svelte: ^3.42.1 => 3.47.0

Severity
blocking an upgrade

According to the logs, it's failing on the SSR build phase so it's likely a Vite issue, or specifically https://github.com/vitejs/vite/issues/2433. It's great that you have a repro up (though sveltekit specific), as no one really provided one in that issue. I'll close this in favor of the issue, thanks for the report!

Cheers @bluwy I had seen that issue before, unfortunately it doesn't look like it has been getting much attention though. Hopefully the vite team can fix it soon

@benmccann Personally I think this issue should be added to a section of #2086. The workaround in the https://github.com/vitejs/vite/issues/2433. thread is not an option on these deployment services

Changing the max_old_space_size to 16GB at build command fixed the issue
"build": "NODE_OPTIONS=--max_old_space_size=16384 svelte-kit build"

@itswadesh
For reference I know Vercel provides 8GB of memory per build.
This will exceed the build memory limits on these platforms so will not fix the issue even though it may work locally


Cycles with a duration of zero still show misleading information on the upcoming cycle tab.

What does this PR do and why?
Closes JB-738 : Upcoming cycle redesign + fix
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #4031

PR #4032   👈

This comment was auto-generated by Graphite.

Merge Activity

Aug 29, 5:26 PM: @wraeth-eth started a stack merge that includes this pull request via Graphite.


fix: remove reauth from update user info

:tada: This PR is included in version 0.66.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add support for inner shadows

Issue #, if available: #160
Description of changes:  Adds a new InnerShadow class and updates Style and SharedStyle to use these along side outer/regular shadows.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Ugh, apparently I am bad at git. This includes commits I don’t want in here. I’ll make another PR. Sorry!


Different result compared to sklearn.metric.auc calculated

in main.py, function, voc_ap();
I tried to add the following lines of codes there
auc_ap = metrics.auc(rec, prec)     print(ap, auc_ap)
However, I found the result is hugely different.

In python, I found that
  iw = bi[2] - bi[0] + 1                     ih = bi[3] - bi[1] + 1                     if iw > 0 and ih > 0:                         # compute overlap (IoU) = area of intersection / area of union                         ua = (bb[2] - bb[0] + 1) * (bb[3] - bb[1] + 1) + (bbgt[2] - bbgt[0]                                         + 1) * (bbgt[3] - bbgt[1] + 1) - iw * ih                         ov = iw * ih / ua                         if ov > ovmax:                             ovmax = ov                             gt_match = obj
I wonder why the +1 in the end is necessary?

In python, I found that
 iw = bi[2] - bi[0] + 1 ih = bi[3] - bi[1] + 1 if iw > 0 and ih > 0: # compute overlap (IoU) = area of intersection / area of union ua = (bb[2] - bb[0] + 1) * (bb[3] - bb[1] + 1) + (bbgt[2] - bbgt[0] + 1) * (bbgt[3] - bbgt[1] + 1) - iw * ih ov = iw * ih / ua if ov > ovmax: ovmax = ov gt_match = obj
I wonder why the +1 in the end is necessary?

because the index begin with 0. for example, w is 5, so it list as
xmin = 0
xmax= 4
w = xmax - xmin + 1

in main.py, function, voc_ap();
I tried to add the following lines of codes there
auc_ap = metrics.auc(rec, prec) print(ap, auc_ap)
However, I found the result is hugely different.

same question

in main.py, function, voc_ap();
I tried to add the following lines of codes there
auc_ap = metrics.auc(rec, prec) print(ap, auc_ap)
However, I found the result is hugely different.

same question

sklearn.metric.auc works for ROC-curve
import numpy as np
from sklearn import metrics
y = np.array([1, 1, 2, 2])
pred = np.array([0.1, 0.4, 0.35, 0.8])
fpr, tpr, thresholds = metrics.roc_curve(y, pred, pos_label=2)
metrics.auc(fpr, tpr)

refer to sklearn.metrics.auc


doc: remove a badge from README

It’s super long now and it takes two lines on the homepage (https://cj.rs/rusqlite_migration/).

Coverage: 94.083%. Remained the same when pulling 4821ec2eaad5d0c387135d44c69237d203c51fa8 on remove-badge into bea8848b00d1bef873ce1fc8af5f10f667c0333e on master.


Implement signMessage

As a user I want to be able to use the signMessage functionality of the signer object provided by Koilib.

implemented in https://github.com/joticajulian/kondor/releases/tag/v0.7.0


DNU doesn't like semi-colons anymore.  It uses multiple args for the same flag.

Same as https://github.com/cake-build/cake/pull/834
Rebased on develop for release with 0.11.0
Thanks!

@adamhathcock could you squash into one commit and ping me when done and I'll review for merging.

@devlead I think this is good to go now.  Thanks!

@adamhathcock thanks, I'll review and merge if all's ok.

Relates to #839

@adamhathcock merged :+1: Thanks for your contribution!


How do I use hnswlib for ColBERT's set of vectors?

How do I use hnswlib for ColBERT's set of vectors?
Thanks

Yes, one can use hnswlib with set distances, but it requires a specialized distance calculation in C++.


Default version if no tags

Hi, thanks for your work on versioningit. Would it be possible to have a default version, say 0.0.0 if there are no tags found in the repository? The reason is that for testing, a shallow copy is often taken which doesn't have a tag, and so the install fails.

versioningit already has this as a feature, as mentioned in the docs.  Assuming you're using git, setting default-tag like so:
[tool.versioningit.vcs]
method = "git"
default-tag = "0.0.0"

will cause versioningit to act as though the initial commit is tagged with "0.0.0" if there are no tags in the repository.

Thanks, sorry, I missed that.


examples css & some js syntax

Minor changes to the js syntax to make it more understandable.
The main changes are to the function "code_arr_text", if you want to tweak the html/css refer to the "const example_html" and to the css classes: snippet-input and snippet-output

LGTM


RSA ssh keys

Does it support RSA keys? I tried, but got  debug1: send_pubkey_test: no mutual signature algorithm. Then I generate ed25519 key and he works fine.

Hey @iwex,
Yes, sish supports RSA keys. I generated a new RSA key using ssh-keygen and sish was able to load it just fine. I was also able to force connecting using just an RSA cipher. Can you share some reproduction steps for this?
Gonna close this issue while we confirm it's a problem with sish.


Unable to use kerberos plaintext auth

Description
Tried to connect to the broker using Kerberos authentication. But I get an error:
[sarama] 2024/01/31 08:31:43 Kerberos client error: [Root cause: KDC_Error] KDC_Error: AS Exchange Error: kerberos error response from KDC: KRB Error: (6) KDC_ERR_C_PRINCIPAL_UNKNOWN Client not found in Kerberos database

Here is simple code to reproduce this behaviour:
package main

import (
	"fmt"
	"log"
	"os"

	"github.com/IBM/sarama"
)

var brokers = []string{"kfk-server.com:6667"}

func main() {
	sarama.Logger = log.New(os.Stdout, "[sarama] ", log.LstdFlags)

	config := sarama.NewConfig()
	config.ClientID = "sarama_test"
	config.Net.SASL.Enable = true
	config.Net.SASL.Mechanism = sarama.SASLTypeGSSAPI
	config.Net.SASL.GSSAPI.ServiceName = "kafka"
	config.Net.SASL.GSSAPI.AuthType = sarama.KRB5_KEYTAB_AUTH
	config.Net.SASL.GSSAPI.KeyTabPath = "/home/user/dev/krb5/some_principal.keytab"
	config.Net.SASL.GSSAPI.KerberosConfigPath = "/home/user/dev/krb5/krb5.conf"
	config.Net.SASL.GSSAPI.Username = "some_principal"
	config.Net.SASL.GSSAPI.Realm = "some_realm"
	config.Net.TLS.Enable = false

	config.Producer.Return.Successes = true

	producer, err := sarama.NewSyncProducer(brokers, config)
	if err != nil {
		panic("Failed to create Kafka producer: " + err.Error())
	}
	defer func() {
		if err := producer.Close(); err != nil {
			fmt.Println("Failed to close Kafka producer:", err)
		}
	}()
}

It is worth noting that with the same configuration data (principal, realm, keytab, etc) another library (confluent-kafka-go) is successfully connected to the broker.
Versions

Sarama
Kafka
Go

1.42.1
2.1.0
go1.21.5 linux/amd64

Logs

logs: CLICK ME

$ ./sarama_producer
[sarama] 2024/01/31 08:31:33 Initializing new client
[sarama] 2024/01/31 08:31:33 client/metadata fetching metadata for all topics from broker kfk-server.com:6667
[sarama] 2024/01/31 08:31:43 Kerberos client error: [Root cause: KDC_Error] KDC_Error: AS Exchange Error: kerberos error response from KDC: KRB Error: (6) KDC_ERR_C_PRINCIPAL_UNKNOWN Client not found in Kerberos database
[sarama] 2024/01/31 08:31:43 Closed connection to broker kfk-server.com:6667
[sarama] 2024/01/31 08:31:43 client/metadata got error from broker -1 while fetching metadata: [Root cause: KDC_Error] KDC_Error: AS Exchange Error: kerberos error response from KDC: KRB Error: (6) KDC_ERR_C_PRINCIPAL_UNKNOWN Client not found in Kerberos database
[sarama] 2024/01/31 08:31:43 client/metadata no available broker to send metadata request to
[sarama] 2024/01/31 08:31:43 client/brokers resurrecting 1 dead seed brokers
[sarama] 2024/01/31 08:31:43 client/metadata retrying after 250ms... (2 attempts remaining)
[sarama] 2024/01/31 08:31:43 client/metadata fetching metadata for all topics from broker kfk-server.com:6667
^C

Additional Context

@kamelusz can you detail what your kerberos server setup is? MIT KDC or AD or something else? There are some limitations in terms of what encryption and checksum types are supported [1], but it should otherwise be working
[1] https://github.com/jcmturner/gokrb5#implemented-encryption--checksum-types

Thanks for the reply. It looks like there really is a problem with our server settings. Sorry to bother and thanks.

No worries, glad you got it working 👍🏻


Entity Object schema nesting is not supported

why not use reflect-metadata?

Thanks

This was fixed with the release of Redis OM 0.4.0 Beta. Install it with npm install redis-om@beta.


make rocm compile

3e3b9156 changed CHECK_ERR() to PCHECK().

Oops, it's fixed by  https://github.com/tensorflow/tensorflow/pull/30030 already.
Close this.


ARIA-290 Update Makefile for binary dist creation

Updated the Makefile to push required files for release
(LICENSE, NOTICE, DISCLAIMER) into the binary distribution
archive (wheel) automatically.

Can one of the admins verify this patch?


Function to not update to MAL if your watchcount on MAL is higher than the episode you're on

Select your issue type: (check at least one)

[ ] Bug
[ ] Question
[x] Suggestion
[ ] Other (please describe):

Describe your issue:
A helpful feature I think would be if you could toggle wether or nor it should automatically update episodes to MyAnimeList or not if the episode you are on is lower than the episode you have on MyAnimeList.
So let's say I'm on episode 5 and MAL has that I'm on episode 10, then it wouldnt update until I'm at episode 11.
Sometimes I like to go back to older episodes for certains scenes but have to reupdate back again.
Thanks

Shipped in version 1.2.0.


ci: add support for /retest command

Commenting /retest on a PR will re-run failed jobs in its GitHub Actions workflows.

Copied from https://github.com/containernetworking/plugins.

The /retest command will only work once this PR is merged, so I can't test it here yet.

Right now, this will re-run all CI jobs, including ones that are already succeeding. I might look into making it just re-run failing jobs at a later time.

In my testing, it takes 20 to 30 seconds for the command to take effect: https://github.com/jpsim/ZenTuner/actions/workflows/commands.yml

there is some custom stuff on envoy that we could reuse here probably

there is some custom stuff on envoy that we could reuse here probably

i looked at that but Envoy’s CI is all Azure Pipelines so it doesn’t really carry over.

cc @itayd who helps us with RepoKitteh in the main repo and is working on "something better" which we can hopefully use here also when it is ready.

don't we already have retest working here for azp?

Envoy Mobile uses GitHub Actions for all of its CI, there are no azp jobs. There's also one CircleCI job that deploys docs when new versions are pushed.

Speaking from the perspective of a person who did a few contributions in EM repo without being a maintainer I think that having a /retest command is a quality of life improvement - especially if we find a way to eventually make it smarter so that it does not rerun green jobs (that would've been pretty awesome).
Pretty often I found myself pushing multiple empty commits to a branch just to get rid jobs that decided to go red randomly. Having /retest would've allowed me to have to do less of a git work.

Now that GitHub Actions directly supports rerunning failed jobs only, I think that's almost always preferable to rerunning all of CI. We have finite resources, and CI jobs do get backed up. If this could be improved to rerun failed jobs only, I feel it would be a lot more compelling. That said, for the occasions where rerunning everything really is what you want (post-CI outage?), I don't see the harm in having this.

Thanks for the feedback everyone. After spending some time looking at the API responses, and looking at GitHub's REST API documentation, I found an endpoint to rerun failed jobs from a workflow run.
Unlike rerun_url, this endpoint isn't in the run API response, but we can construct it manually easily.
Documentation for it is here: https://docs.github.com/en/rest/actions/workflow-runs#re-run-failed-jobs-from-a-workflow-run
I've tested it on a separate repo and it worked as expected: https://github.com/jpsim/ZenTuner/pull/47

@goaway @Augustyniak did my latest updates address your concerns about only re-running failing jobs?

Thanks @jpsim! This is fantastic, and should be a huge improvement over needing to navigate the UI to restart each failing individually - in addition to solving the permissions issue for external contributors.


CASSANDRA-16450 MigrationCoordinatorTest#testWeKeepSendingRequests() Failing Sporadically

ensure that MigrationCoordinatorTest.testWeKeepSendingRequests waits for callback failure to complete before asserting that a new request has been sent

https://app.circleci.com/pipelines/github/maedhroz/cassandra/237/workflows/641cd945-f194-4a4f-bc0b-5cbed0c2061f


SQL error

I'm getting the error on launch.
Could not initialize driver: connection("library routine called out of sequence")
I've created the example table in the Database folder. Any ideas why this might be happening?

Doesn't seem like a Fluent issue. Seems like an issue with the driver.

@Joannis Yes, putting a breakpoint revealed that the error is actually being generated in the driver. The error message is coming from sqlite3 itself.

@kaandedeoglu I think this error is coming from Fluent not being able to find your database. Are you using Xcode? If so, make sure to set the correct working directory.

I just fixed a bug that I think is causing that misleading error message
https://github.com/qutheory/fluent-sqlite/commit/bd4e248664a1240ced109f1c383d751f5ee46f5b
Try cleaning your project and building again @kaandedeoglu

Thanks for the quick reply, i'm no longer getting the same error message 👍 💯


Test Python client against latest MR

As the majority of Python client tests depend on the current implementation of MR, build it in favor of using the last pushed version.
This also creates a new (e2e) test mode for the Python client to highlight the dependencies.
Description

How Has This Been Tested?
Updated on GHA, ran make test-e2e locally. Also tested with nox.
Merge criteria:

All the commits have been signed-off  (To pass the DCO check)

[ ] The commits have meaningful messages; the author will squash them after approval or in case of manual merges will ask to merge with squash.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work.
[ ] Code changes follow the kubeflow contribution guidelines.

If you have UI changes

[ ] The developer has added tests or explained why testing cannot be added.
[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Verify that UI/UX changes conform the UX guidelines for Kubeflow.

cc: @tarilabs


Remove ObserverController/SiteStats#server_status

The server_status method is unused and throws an error if you try to use it.
See discussion at https://www.pivotaltracker.com/story/show/137757411.
Therefore, remove the method and the corresponding view template.

Coverage increased (+0.04%) to 87.843% when pulling 2b8ba869230426fa8989ad9adfeb7afb97194fa8 on JoeCohen:remove-server_status into 2901f663adde549ae0567bafc5715146ce153490 on MushroomObserver:master.


CSS not displaying

Hi!
First of all, thanks for this AWESOME library. This is huge and so cool! I'm really new to React and this has made my life easier. I'd like to thanks all of the contributors and, obviously, the creator and main maintainer.
I just got a "simple" problem: The CSS loaded from MyComponent.css into MyComponent.js is not applied. But When I use this CSS in the main CSS file (App.css), it works just fine.

components: Navbar
reactstrap version 6.4.0
import method es
react version 16.4.2
bootstrap version 4.1.3

What is happening?
There is a Code Sandbox where you can see the problem : Code Sandbox
I create a simple navigation component called Navigation in the components folder. There is a Navigation.css file which describes my component stylesheet. This is curently a simple background-color.
In the Navigation.js file : I import the css using import './Navigation.css'
In the browser : The component doesn't get colored in red as it should. The CSS is accessible through F12 but its not used and overrides by the Boostrap's one.
When I set the exact same CSS in the App.css file, it works.
It is a bug or something I just misunderstood?
What should be happening?
The component should be colored from its own CSS file
Steps to reproduce issue

Open the Code Sandbox
Open Components/Navigation.css
Edit it to see there is no effect
Set the exact same value in the App.css file  : It should work there

Error message in console
No error message
Code
Code Sandbox link : Code Sandbox
Thanks for any kind of help <3

Sorry... I searched for hours and the solution just appeared after writing this...
For anyone facing this problem in the future the solution is just moving the bootstrap import in index.js to the top...
After this, it works fine.
Closing this :)


[PE-D][Tester B] add_applicant UG mismatch with expected command format on App

Expected Example for add_applicant:

Actual Example for add_applicant:

Perhaps, the team can update the UG to make the given examples coherent with the ones in the application for better user understandability.
Regards!

Labels: severity.VeryLow type.DocumentationBug
original: YuvBindal/ped#11

duplicate


added getters for parsed image and parsed MRZ, fixed render view usage without xib

Hi,
i've added some getters for

parsed image (useful for legal issues)
parsed MRZ fullstring

Also, I've fixed the render view init when the view controller is used programmatically, without a xib
Enjoy, :)

Thanks! It's merged and published to cocoapods as version 4.2.0


[BUG] Weird Visual Glitch in bloxstrap menu??

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[ ] My answer given in the checkbox above is a lie.

What problem did you encounter?
I have installed Bloxstrap today, and for some reason the menu is having visual glitches, It's hard to control
Provided video:
https://github.com/user-attachments/assets/c544dde1-4c4e-4a04-86f7-dce0ba71f701
My pc is W11, RTX 2070 Super, Intel i7-9700k

My pc is W11, RTX 2070 Super, Intel i7-9700k

Sonic Suite turns out to be the cause of this issue.

if i had a nickel every time some shitty oem audio software caused this issue id have two which isnt a lot but is weird i have that much in the first place