expr: 1.16.5 -> 1.16.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/antonmedv/expr/releases.
meta.description for expr is: Expression language and expression evaluation for Go
meta.homepage for expr is: https://github.com/antonmedv/expr
meta.changelog for expr is: https://github.com/antonmedv/expr/releases/tag/v1.16.6
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.16.6 in filename of file in /nix/store/hxbgxgykmawmq32gr24zmhpjlg6p1yqc-expr-1.16.6

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

expr

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hxbgxgykmawmq32gr24zmhpjlg6p1yqc-expr-1.16.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A expr https://github.com/r-ryantm/nixpkgs/archive/7cc866a36b26107002ee86c422728e18390cebd9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7cc866a36b26107002ee86c422728e18390cebd9#expr

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hxbgxgykmawmq32gr24zmhpjlg6p1yqc-expr-1.16.6
ls -la /nix/store/hxbgxgykmawmq32gr24zmhpjlg6p1yqc-expr-1.16.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

expr

Maintainer pings
cc @figsoda for testing.

Looks like the github repo has moved to expr-lang/expr.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/antonmedv/expr/releases.
meta.description for expr is: Expression language and expression evaluation for Go
meta.homepage for expr is: https://github.com/antonmedv/expr
meta.changelog for expr is: https://github.com/antonmedv/expr/releases/tag/v1.16.7
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.16.7 in filename of file in /nix/store/lphlr7pjk459aymj39ny2rm7pj8fava5-expr-1.16.7

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

expr

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lphlr7pjk459aymj39ny2rm7pj8fava5-expr-1.16.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A expr https://github.com/r-ryantm/nixpkgs/archive/91b3f43e844b05793358891637aac8d71784eedd.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/91b3f43e844b05793358891637aac8d71784eedd#expr

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lphlr7pjk459aymj39ny2rm7pj8fava5-expr-1.16.7
ls -la /nix/store/lphlr7pjk459aymj39ny2rm7pj8fava5-expr-1.16.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

expr

Maintainer pings
cc @figsoda for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/antonmedv/expr/releases.
meta.description for expr is: Expression language and expression evaluation for Go
meta.homepage for expr is: https://github.com/antonmedv/expr
meta.changelog for expr is: https://github.com/antonmedv/expr/releases/tag/v1.16.8
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.16.8 in filename of file in /nix/store/j401i2xf4d6f7kwk87yn80yrg1nxliqn-expr-1.16.8

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

expr

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j401i2xf4d6f7kwk87yn80yrg1nxliqn-expr-1.16.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A expr https://github.com/r-ryantm/nixpkgs/archive/9e4a8b5a917ffb5bcd951244fcf9e994578f126a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9e4a8b5a917ffb5bcd951244fcf9e994578f126a#expr

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j401i2xf4d6f7kwk87yn80yrg1nxliqn-expr-1.16.8
ls -la /nix/store/j401i2xf4d6f7kwk87yn80yrg1nxliqn-expr-1.16.8/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

expr

Maintainer pings
cc @figsoda for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/antonmedv/expr/releases.
meta.description for expr is: Expression language and expression evaluation for Go
meta.homepage for expr is: https://github.com/antonmedv/expr
meta.changelog for expr is: https://github.com/antonmedv/expr/releases/tag/v1.16.9
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.16.9 in filename of file in /nix/store/bx8vzkibaiaz09qbcql1v011vypymkqn-expr-1.16.9

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

expr

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bx8vzkibaiaz09qbcql1v011vypymkqn-expr-1.16.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A expr https://github.com/r-ryantm/nixpkgs/archive/1c5ac31f513e27294ba57a9391e2e4e2aa201f6c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1c5ac31f513e27294ba57a9391e2e4e2aa201f6c#expr

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bx8vzkibaiaz09qbcql1v011vypymkqn-expr-1.16.9
ls -la /nix/store/bx8vzkibaiaz09qbcql1v011vypymkqn-expr-1.16.9/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

expr

Maintainer pings
cc @figsoda for testing.


[WIP][SPARK-36034][SQL] Rebase datetime in pushed down filters to parquet

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Test build #141025 has started for PR 33347 at commit 96a7ca4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45540/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45540/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45540/

Test build #141029 has started for PR 33347 at commit fffc22e.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45544/

Test build #141025 has finished for PR 33347 at commit 96a7ca4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45544/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45544/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141025/

Test build #141029 has finished for PR 33347 at commit fffc22e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141029/

Test build #141085 has started for PR 33347 at commit 37d7ffa.

Kubernetes integration test unable to build dist.
exiting with code: 141
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45599/

The failed GA is not related to changes:
starting mypy test...
mypy checks failed:
python/pyspark/mllib/tree.pyi:29: error: Overloaded function signatures 1 and 2 overlap with incompatible return types
python/pyspark/mllib/tree.pyi:38: error: Overloaded function signatures 1 and 2 overlap with incompatible return types

I am merging this to master/3.2.

Here is the backport to 3.0: https://github.com/apache/spark/pull/33387


Apply severity filter to diagnostics panel and navigation, not underline/hover

Closes #795
Next/previous diagnostic was hardwired to Errors and Warnings, but as we have a setting controlling what the user thinks is relevant (show_diagnostics_severity_level), we should read that instead.
Also drops the severity filter for in-view diagnostic regions. This is because as a developer I want quick access to errors and warnings, but still want to see server suggestions somewhere.

[x] Should the default for show_diagnostics_severity_level change from 3 (info) to 2 (warning) ?

For those offended by info and hint squigglies in their code, should we expose diagnostic_severity_scopes as a setting? (We could drop some of the fallback scopes and give the user the chance to not set any scopes at all for some diagnostics) Can do this later.

Coverage increased (+0.05%) to 38.112% when pulling 3c267eab898cf43778a1d05e6b582045b8812b4b on apply-severity-level-to-diag-panel-and-navigation into 790d5f4382c550df6e77ae142a68adc09035f3eb on master.

issue fixed thanks @tomv564


Increment version number and add prerelease feed to README.

This PR updates the version number used to build the Q# runtime in CI and updates the README file to point to the public prerelease feed.

Sounds good, I'll get on that now, then.


styling {injector} is broken in Safari

Renderer
v3
Browser
Safari
Operating System
MacOS
What happened?
Loading any page causes Safari to fail incomplete.
An error in the console leads to this:

The source is https://github.com/naturalcrit/homebrewery/blob/ee05392d27ce76999b95bfb8f990d17a1e6d2b1a/client/homebrew/editor/editor.jsx#L142
The regex for styling {injectors} begins with a negative look-behind, but that is not supported in Safari per https://caniuse.com/js-regexp-lookbehind
Suggestion: this (?<!{) be changed to a non-capturing group (?:[^{]?) — that is, the {injector} pattern should be preceded with zero-or-one character which is not a {.
Code
# heading
{injector}

I suspect this needs to be "start-of-line or one non { character", rather than zero or one non { character.

See https://regex101.com/r/eRt9me/1
It's matching even though there are two {. This is because we are essentially matching "{, and then zero {, and then the rest of the tag"
You can do "start of line" with ^

We probably need something more like https://regex101.com/r/H674QD/1

d'oh, of course.

/(?:^|[^{]){(?=((?::(?:"[\w,-()#%. ]"|[\w-()#%.])|[^"':{}\s])))\1}/gm

this captures the character before the injector as well.  For example, Cat's eat Mice{sometimes}....the style is applied to e{sometimes}.

I think this does it:
const regex = /(?:^|[^{|\n])({(?=((?::(?:"[\w,\-()#%. ]*"|[\w\-()#%.]*)|[^"':{}\s]*)*))\2})/gm;
let match;
while ((match = regex.exec(line)) != null) {
    codeMirror.markText({ line: lineNumber, ch: line.indexOf(match[1]) }, { line: lineNumber, ch: line.indexOf(match[1]) + match[1].length }, { className: 'injection' });
}

regex101 link
I'll put a PR up in a minute.


Fixing Issue 278

I've added the elements for the View Project page, but the GET API doesn't seem to be working (or maybe I'm just using it wrong) so I had to just leave some placeholder data for now.
Also, I need help with getting the label css to match the css of the other labels, because it looks kind of strange right now.

after accessing http://localhost:3000/project/list and selecting a project, i get this error in the console

Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'project/1'

i think you need to update the routes, i.e. app-routing.module.ts

When I access http://localhost:3000/project/list I get this error in the console:

Failed to load resource: net::ERR_CONNECTION_REFUSED http://localhost:8080/api/projects/all

Do I need to do something first in order to make the API work?

@Ryan-Thomas i am curious how you tested the code that you wrote if you didn't have the backend running? that was the only way i could get the project list to display.

Could you also resolve the conflicts?


Enhancement Request: Categorize Blocks

The submenu for new blocks gets really long if you have quite a few blocks.  Wondering if it is possible to categorize blocks so that in the JS frontend when you create a new block, you see the main category and then the blocks that fall under that specific category.

So, to understand you better. When you want to add a new block, on the context menu (when you right click) the list is long. So, you'd like to categorise them and provide sub-menus so it is easy to access them. Right?

@krish-adi you understand perfectly.  I’m really enjoying this package you’ve built it’s very interesting and a perfect fit for my project.

Hey @zabrewer,
I've put it on the development roadmap.
Great to hear you're enjoying barfi. I would be very interested to know your use-case. If you don't mind, could you write to me at<EMAIL_ADDRESS>?

Thanks!!!!


how to count up instead of count down?

Hi,
Is there a simple way of modifying the code to count up instead of count down?

I don't think so. Because its name is count down; not count up :)
If you want to use some other libraries to do that, I suggest you to use FlipClock.
It can count up and count down both.

Hi Bilal,
Actually, Hilios did explain it in another reply, as it was possible to
countUp:
"..Just set a config object {elapse: true} as the plugin functions second
argument."
$('#clock').countdown('YYYY/MM/DD', {elapse:
true}).on('update.countdown', function(event) {
var $this = $(this);
if (event.elapsed) {
$this.html(event.strftime('After end: %H:%M:%S'));
} else {
$this.html(event.strftime('To end: %H:%M:%S'));
}
});
On Sun, Oct 1, 2017 at 7:42 AM, Bilal AFŞAR<EMAIL_ADDRESS>wrote:

I don't think so. Because its name is count down; not count up :)
If you want to use some other libraries to do that, I suggest you to use
FlipClock http://flipclockjs.com/.
It can count up and count down both.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hilios/jQuery.countdown/issues/279#issuecomment-333334707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV30urw3hxogajhMUdCI4C41kO8dNmyEks5snqergaJpZM4PoV5g
.

https://github.com/hilios/jQuery.countdown/issues/134
On Sun, Oct 1, 2017 at 12:25 PM, Krystyna<EMAIL_ADDRESS>wrote:

Hi Bilal,
Actually, Hilios did explain it in another reply, as it was possible to
countUp:
"..Just set a config object {elapse: true} as the plugin functions second
argument."
$('#clock').countdown('YYYY/MM/DD', {elapse: true}).on('update.countdown', function(event) {
var $this = $(this);
if (event.elapsed) {
$this.html(event.strftime('After end: %H:%M:%S'));
} else {
$this.html(event.strftime('To end: %H:%M:%S'));
}
});
On Sun, Oct 1, 2017 at 7:42 AM, Bilal AFŞAR<EMAIL_ADDRESS>wrote:

I don't think so. Because its name is count down; not count up :)
If you want to use some other libraries to do that, I suggest you to use
FlipClock http://flipclockjs.com/.
It can count up and count down both.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hilios/jQuery.countdown/issues/279#issuecomment-333334707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV30urw3hxogajhMUdCI4C41kO8dNmyEks5snqergaJpZM4PoV5g
.

https://gist.github.com/onskyD/cc7547b8c536f58ea3e1d61ce6dadc2c#file-scripts-js


merge package template from arlac77/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template

doc/README.hbs

docs(README): update from template

Coverage remained the same at 48.936% when pulling 6fedd46e34b8cdbeae24334fe93ac1d87a2a472e on template-sync-1 into 43cd0986e350b312b6cd55600d874b80148348ea on master.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #139   +/-   ##
=======================================
  Coverage   48.83%   48.83%
=======================================
  Files           2        2
  Lines          43       43
=======================================
  Hits           21       21
  Misses         22       22

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 43cd098...6fedd46. Read the comment docs.


Make the usage of newlines in Cargo.toml consistent

Hi,
It seems that people generally prefer not having newlines after section headers in their Cargo.tomls. However, when one creates a new package via cargo new, a newline gets automatically inserted after [package]. Then a typical Cargo.toml ends up being some what inconsistent: there is a newline after [package], and there are no newlines after other headers.
On top of that, the examples given on crates.io do not seem to be consistent: sometimes there is a newline after [package], and sometimes there is none. The same applies to other section names.
I am wondering if there should be some style conventions in this regard.
Regards,
Ivan

r? @wycats
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+ dc2d54c
I agree that this seems to be the more idiomatic style, and that a more official convention would be nice :). For now I think it's best to keep up with general consensus instead of waiting for an official decision, however.

:hourglass: Testing commit dc2d54c with merge 6f232c9...

:broken_heart: Test failed - cargo-win-32

@bors: retry
On Wed, Mar 18, 2015 at 9:55 AM, bors<EMAIL_ADDRESS>wrote:

[image: :broken_heart:] Test failed - cargo-win-32
http://buildbot.rust-lang.org/builders/cargo-win-32/builds/891
—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/cargo/pull/1431#issuecomment-83056471.

:hourglass: Testing commit dc2d54c with merge 8c4b728...

:broken_heart: Test failed - cargo-win-32

@bors: retry
On Wed, Mar 18, 2015 at 10:20 AM, bors<EMAIL_ADDRESS>wrote:

[image: :broken_heart:] Test failed - cargo-win-32
http://buildbot.rust-lang.org/builders/cargo-win-32/builds/893
—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/cargo/pull/1431#issuecomment-83065817.

:zap: Previous build results for cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64 are reusable. Rebuilding only cargo-win-32, cargo-win-64...

I wonder what the normal ini style is.

@bors: retry clean force

:hourglass: Testing commit dc2d54c with merge 3e6607c...

:broken_heart: Test failed - cargo-win-64

@bors: retry

:hourglass: Testing commit dc2d54c with merge 8399dca...

:broken_heart: Test failed - cargo-win-32

@bors: retry
On Wed, Mar 18, 2015 at 11:18 AM, bors<EMAIL_ADDRESS>wrote:

[image: :broken_heart:] Test failed - cargo-win-32
http://buildbot.rust-lang.org/builders/cargo-win-32/builds/899
—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/cargo/pull/1431#issuecomment-83108076.

:zap: Previous build results for cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-64 are reusable. Rebuilding only cargo-win-32...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64


Ubuntu single build image (devel)

Scope & Purpose
Ubuntu single build image for devel based on clang-16 and modified static glibc usage.

[ ] :hankey: Bugfix
[x] :pizza: New feature
[x] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[x] Tests

[x] Regression tests
[x] C++ Unit tests
[x] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[ ] Backport for 3.11: (Please link PR)
[ ] Backport for 3.10: (Please link PR)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket:
[ ] Design document:

[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-matrix/110/
[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-packages/98/

[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-packages/102/
[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-matrix/111/
[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-components-and-drivers/49/


Support OAS 3.1.0

I'd like to use this library to detect breaking changes in a OAS v3.1.0 schema. Currently, it fails to parse the schema due to the breaking change of "exclusiveMinimum" being a number instead of a boolean in v3.1.0.
I'm not sure if "exclusiveMinimum" is the only thing unsupported for v3.1.0 (ex. type can be an array instead of a single value, but that seems to pass parsing already), but in my particular case its the only thing blocking parsing.
Curious generally if there's plans to support v3.1.0, or if we can start with a small patch around this particular breaking change (since it seems fairly easy to support both versions of this particular field at least)

Please see https://github.com/Tufin/oasdiff/issues/52


[Android] [0.57.6] [BUG] PanResponder is not working on Android after upgrade from 0.54.2 to 0.57.6

Issue report from previously closed/unresolved/incomplete issue:  #22434

I have created a Circular Slider, using PanResponder, based on existing GitHub project and it was working beautifully in both Android and iOS (react-native version ^0.54.2).

PanResponder was responding to touch events for both Android and iOS when in RN 0.54.2, after upgrading to 0.57.6 it doesn't trigger any events to Android anymore but it still works fine in iOS.
I've worked around the issues with scrollviews using a toggle to switch scroll on/off while in version 0.54.2, it was affecting only iOS and this workaround resolved it.
There is a debug (console.log) in the code (slider.page.js -> enableScroll()) which writes "true" or "false" as my scroll toggles, it can be seen in console when running in iOS but not in Android.
this._panResponder = PanResponder.create({
      onStartShouldSetPanResponder: (e, gs) => {return true;},
      onStartShouldSetPanResponderCapture: (e, gs) => {return true;},
      onMoveShouldSetPanResponder: (e, gs) => {return true;},
      onMoveShouldSetPanResponderCapture: (e, gs) => {return true;},
      onPanResponderStart: e => {
        this.props.enableScroll(false);
        return true;
      },
      onPanResponderMove: (e, gs) => {
        this.layoutData();
        let xOrigin = this.state.initialX;
        let yOrigin = this.state.initialY;
        let a = this.cartesianToPolar(gs.moveX - xOrigin, gs.moveY - yOrigin);
        this.setState({ angle: a });
        this.props.changeDuration(a);
        return true;
      },
      onPanResponderRelease: (e, gestureState) => {
        this.props.enableScroll(true);
        return true;
      }
    });
  }

render() {
    let width = (this.props.dialRadius + this.props.btnRadius) * 2;
    let bR = this.props.btnRadius;
    let dR = this.props.dialRadius;
    let startCoord = this.polarToCartesian(0);
    let endCoord = this.polarToCartesian(this.state.angle);

    return (
      <View style={styles.container} onLayout={this.layoutData}>
        <Svg
          ref={ref => (this.svg = ref)}
          width={width}
          height={width}
          fill="#f2f8fb"
        >
          <Circle
            r={dR}
            cx={width / 2}
            cy={width / 2}
            stroke="#cccccc"
            strokeWidth={1.5}
            fill="#f2f8fb"
          />

          <Path
            stroke={this.props.meterColor}
            strokeWidth={this.props.dialWidth}
            fill="#f2f8fb"
            d={`M${startCoord.x} ${startCoord.y} A ${dR} ${dR} 0 ${
              this.state.angle > 180 ? 1 : 0
            } 1 ${endCoord.x} ${endCoord.y}`}
          />

          <Text
            fontSize={20}
          >
            {this.state.duration}
          </Text>

          <G x={endCoord.x - bR} y={endCoord.y - bR} >
            <Circle
              r={bR}
              cx={bR}
              cy={bR}
              fill="#005b7f"
              {...this._panResponder.panHandlers}
            />
          </G>

        </Svg>
      </View>
    );
  }
}

I've tried:
going back to expo version (0.57.1)
tried the suggestion on issue #21749 (set collapseable=false)
Reproducible Demo
https://snack.expo.io/@wazzupex/circularslider
React Native Environment Info:
System:
  OS: macOS 10.14.1
  CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
  Memory: 2.63 GB / 16.00 GB
  Shell: 3.2.57 - /bin/bash
Binaries:
  Node: 10.11.0 - /usr/local/bin/node
  Yarn: 1.12.3 - /usr/local/bin/yarn
  npm: 6.4.1 - /usr/local/bin/npm
SDKs:
  iOS SDK:
    Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
IDEs:
  Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
  react: ^16.6.3 => 16.6.3
  react-native: https://github.com/expo/react-native/archive/sdk-31.0.0.tar.gz => 0.57.1
npmGlobalPackages:
  create-react-native-app: 2.0.2
  eslint-plugin-react-native: 3.4.0
  react-native-cli: 2.0.1
  react-native-git-upgrade: 0.2.7

Up!
Will I have to downgrade React-Native and dependency tree?

To make it work, I have downgraded react-native and dependencies tree while awaiting for a solution for this issue.
I'm making myself available to help in any way even though I'm not a very skilled developer.
Find me dependencies below:
"dependencies": {
    "@babel/core": "^7.1.5",
    "@babel/plugin-check-constants": "^7.0.0-beta.38",
    "cli-engine-command": "^12.0.0",
    "cli-engine-config": "^3.5.0",
    "d3-interpolate": "^1.3.2",
    "expo": "^26.1.1",
    "fetch-intercept": "^2.3.1",
    "lodash.range": "^3.2.0",
    "moment": "^2.22.2",
    "native-base": "^2.8.1",
    "prop-types": "^15.6.1",
    "react": "^16.6.1",
    "react-native": "^0.54.2",
    "react-native-svg": "^6.3.1",
    "react-navigation": "^1.6.1",
    "react-redux": "^5.1.0",
    "redux": "^3.7.2",
  },

Does anyone acknowledge it as React-Native issue/Bug or it is something too dumb I did that no one even comment on this topic?

Up!

I am having the same issue, any news on that ?
downgrading the version is not something I want.

Something changed, I'm not too sure what because I can't run any of these snacks in some of the latest version - any chance someone can give this a fresh look on the latest releases?

Still having the problems of not able to trigger touches on TouchableHighlight. TouchableOpacity able to trigger touches but cannot execute the function within (for example, an alert message).
`    this._panResponder = PanResponder.create({
onStartShouldSetPanResponder: () => {this.resetTimer(); return true},
onStartShouldSetPanResponderCapture: () => {this.resetTimer(); return false},
onMoveShouldSetPanResponder: () => true,
onMoveShouldSetPanResponderCapture: () => false,
onPanResponderTerminationRequest: () => true,
onShouldBlockNativeResponder: () => false,
});
this.timer = setTimeout(() => this.setState({ show: true }), 3000)
resetTimer(){
clearTimeout(this.timer);
if(this.state.show){
this.setState({ show: false })
}
this.timer = setTimeout(() => this.setState({ show: true }), 3000)
}
`

The issue is no longer happening since I upgraded to 0.59+


Fix structure comparison in road layout planning

The existing program incorrectly uses integers when comparing structure types, rather than the structure names themselves. This has made it so road planning does not take into account any of the planned structures.
This PR fixes that issue and uses the OBSTACLE_OBJECT_TYPES constant for future proofing.

This Pull Request has been merged by GitConsensus.
Vote Totals

Yes
No
Abstain
Voters

3
0
0
3

Vote Breakdown

User
Yes
No
Abstain

tedivm
✔

dragoonreas
✔

ags131
✔

Vote Results

Criteria
Result

Has Quorum
True

Has Votes
True


improved search bar ui on mobile responses

Description
This PR addresses the issue of the search bar's usability on mobile devices by modifying the CSS to ensure the search bar appears above the text and is fully responsive. The changes include adjustments to the layout using Flexbox and media queries.
Related Issues

Fixes #226

Changes Made

Modified .body-search CSS to stack elements vertically by default.
Added media queries to switch the layout to horizontal alignment on screens larger than 600px.
Ensured the input field and search button take full width on smaller screens for better usability.
Centered the heading text for a polished look on mobile devices.

Screenshots
Before

After

Testing

Fork the repository:

Log into GitHub.
Go to the Creative Commons Search Portal repository.
Click the Fork button at the top of the screen.
Choose your GitHub ID.

Clone the forked repository:
git clone https://github.com/<YourUserName>/search.git
cd search

Set up the upstream repository:
git remote add upstream https://github.com/creativecommons/search.git
git pull upstream main
git push origin main

Switch to the branch for this feature:
git checkout -b feature/search-bar-mobile-responsiveness

Checklist

[x] Code compiles correctly.
[x] All tests passing.
[x] Extended the README / documentation, if necessary.
[x] Lint and formatting check passed.
[x] Updated relevant screenshots for UI changes.

Additional Comments
Please review the changes and let me know if there are any adjustments needed. The new layout should significantly improve the usability of the search bar on mobile devices.

Hey, @possumbilities or @Shafiya-Heena ...Can you please review the pr?


Wrong label for Web App Firewall

Within the Visio image. The Web App Firewall is mislabeled as "Well Architected Framework".

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d4978cb6-4e7a-5d67-2e45-ab2f9a292ee6
Version Independent ID: d4978cb6-4e7a-5d67-2e45-ab2f9a292ee6
Content: Recommendations for designing for redundancy - Microsoft Azure Well-Architected Framework
Content Source: well-architected/reliability/redundancy.md
Service: waf
Sub-service: waf-pillar-reliability
GitHub Login: @claytonsiemens77
Microsoft Alias: csiemens

Fixed under PR https://github.com/MicrosoftDocs/well-architected-pr/pull/1469

Closing.


[Bug] --watch is no longer effective

Describe the bug
When running npx test-storybook --watch the test runner runs in normal mode, rather than watching for changes and exists on completion
Steps to reproduce the behavior
Bug encountered in a private repo, is there a good starter project I can test deps on?
Expected behavior
I'd expect --watch to watch for file changes and rerun test-storybook accordingly
Screenshots and/or logs
If applicable, add screenshots and/or logs to help explain your problem.
Environment

OS: macOS
Node.js version: v16.16.0
NPM version: v8.15.0

 "@storybook/test-runner": "^0.6.0-next.1",
 "@storybook/testing-library": "^0.0.13",
 "@storybook/testing-react": "^1.3.0",
 "jest": "^28.1.3",

Additional context
Add any other context about the problem here.
associated discord thread: https://discord.com/channels/486522875931656193/1006156600022667345/1006157098318577714
I think I may have discovered it being due to upgrading to jest 28 in our repo?

yay https://github.com/storybookjs/test-runner/releases/tag/v0.6.0-next.3

Fix was released in v0.6.0! Thanks once again @jasikpark


[1p cp] revert split display list

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Should we wait for the cut off date?

Should we wait for the cut off date?

Umm like when this branch is promoted to the new beta?

Should we wait for the cut off date?

Umm like when this branch is promoted to the new beta?

I thought this was from this week release

umm this one is 3.14.- 13. I am also trying to roll engine into 3.14-14 in https://github.com/flutter/flutter/pull/134495
umm just to clarify, what would be the concern?


Make Indiekit a Progressive Web App (PWA)

To reduce the friction between getting an idea for a post and actually posting it, I'd like to have Indiekit installed on my iPhone and Mac as a Progressive Web App, launchable like any other app on the device and with the ability to remain logged in.
Right now I can bookmark Indiekit, but whenever I open it I have to put in my IndieAuth password again, and that gets a bit tedious.

This is definitely something I want to get to, but need to sit down and actually work out how to make this work properly (been a while since I’ve played with service workers, and lots has changed.)
Meanwhile, in 91a08c74 I’ve added a maxAge of 7 days to the session cookie which should mean, as long as your server doesn’t restart, needing to enter a password on fewer occasions. This will ship with Beta 10.


feat(create): add 'Mithril' templates

Description
Add Mithril templates (standard -> m functions and jsx)
Additional context
Actually No Mithrill templates for Vite

What is the purpose of this pull request?

[ ] Bug fix
[X] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the PR Title Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[-] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks for the PR. We usually don't add new templates unless the framework has a large enough usage (e.g. npm downloads). It seems like the CLI added here is rather new. If there's more traction for this Vite template, we can reconsider this but at the moment we won't be adding this.


Superset issue #4512: fixing histogram

This is an attempt to address issue #4512.

ticks: setting the max number of ticks to 20, using scientific notation
colors: using the same color for all bars
annotations: getting rid of text on bars - another option could be to add a setting to toggle them
adding an x-axis label option
adding a normalization option

🚢  @mistercrunch

@hughhhh @mistercrunch I have another commit in store that I want to push. Should I

update this PR with it?
wait for this PR to be merged and create a new one?
create a new PR right now in parallel to this one?

@ArielStv Merged!

thanks a lot!


Block exploded event

I wanna create a bomb gadget for my hub server which destroys blocks (drops primed_tnt) and then it should replace the blocks with a nice pop sound back after a few seconds. What event do I have to use for the exploded blocks?

on entity explodes
primed_tnt is an entity, not a block.

@Talamar1 :smile_cat: I knew that this is an entity (otherwise I would be a bit stupid), but I thougt the event I searched for would trigger when a block gets broken by an explosion, something like on block burns. But with this event I can use the <context.blocks> to get the destroyed blocks. Thanks! :cake:

My script currently looks like that:
bomb:
  type: world
  events:
    on entity explodes:
    - define blocks <context.blocks>
    - wait <util.random.decimal[1].to[3]>
    - foreach %blocks% {
        - modifyblock <%value%> <%value%.material>
        - wait <util.random.decimal[0.1].to[0.5]>
        }

But in the %blocks% list only the location are saved and the materials are read out at runtime. How can I save the materials? I first thougt about cycling throug the %blocks% list at the start of the event and writing the blocks in a second list. But that would be a bit too complicated I think. Is there any easier solution?

you could try the entity changes block event, I have no clue if it would work or not, but it may be worth a shot.

I think, I do this now with displayfake.

Your wait statement allows the blocks to change, which is why you are losing the material value.

@Talamar1 I know, that's why I use showfake now.

@brainscript the showfake won't fix the problem.. the problem for you is that <context.blocks> only stores locations, not materials. you need a list of the old materials aswell.
This, accounts for materials and regenerates the area progressively. I sped it up a bit, as the wait was very slow
bomb:
  type: world
  events:
    on entity explodes:
    - define blocks <context.blocks>
    - define materials <def[Blocks].parse[material]>
    - wait <util.random.decimal[1].to[3]>
    - foreach %blocks% {
        - modifyblock <%value%> <def[materials].get[<def[loop_index]>]>
        - wait <util.random.decimal[3].to[5]>t
        }

@Fortifier42 The script is already done and replaces the blocks with colored wool blocks. But thanks for your solution, I didn't know of the parse tag before.


Trying to follow quickstart but stuck on docker ps and sending funds

Hello there !
Merry -X-Mass and HPNY  :-)
I following the quick-start guide, everything looks good with providing APIs and it seems like half working.
At some point it asking to  have #.## ETH in main wallet, but then it checks some different to main wallet address I think it sent some ETH to that address but next line it  writing something like make sure the 0xnew-address has at least ## USDC.
I am not sure I am supposed to have to send it there since I do not know what the address is it?
Another thing    docker ps -a  gives zero images running.

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WB240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

Hello there !
Merry -X-Mass and HPNY :-)
I following the quick-start guide, everything looks good with providing APIs and it seems like half working. At some point it asking to have #.## ETH in main wallet, but then it checks some different to main wallet address I think it sent some ETH to that address but next line it writing something like make sure the 0xnew-address has at least ## USDC. I am not sure I am supposed to have to send it there since I do not know what the address is it? Another thing docker ps -a gives zero images running.

Hello @MikhailKlemin
We sincerely apologize for the delay and any inconvenience this may have caused.
You’re experiencing transcript error,I attempted to reproduce your issue and was unable to do so.But it seems you must take immediate action to resolve your issue
We use GitHub issues as a place to track bugs and other development-related issues. If your issue persists, I’ll have to refer you to the official support live chat with the ticket ID MOD093739
Please see the link below to our dedicated support line:
Modius Network DApps Support Ticket Requests.
Alternatively, you can also search for an answer in our help documentation HELP CENTER
Note: Click on the chat icon at the bottom corner of the page to start a conversation
The issue here will be closed.
Thanks!


Incorrect rows count when using GROUP BY with multiple columns - Nette\Database\Table

Hi,
I found the bug in Nette\Database\Table data source when using GROUP BY with multiple columns.
Here is example of SQL queries.
Query for the datagrid with 703 total rows.
SELECT `id`, `title`, `variant`, CONCAT_WS(" - ", `title`, `variant`, `course_city`, `course_date`) AS `full_name`
FROM `orders_products`
GROUP BY `title`, `variant`, `course_city`, `course_date`;

Datagrid generated this SQL query from the getCount() function which gets 0 rows.
SELECT COUNT(DISTINCT `title`, `variant`, `course_city`, `course_date`)
FROM `orders_products`;

I think right SQL query with multiple GROUP BY columns should be:
SELECT COUNT(*)
FROM (
SELECT COUNT(id)
FROM `orders_products`
GROUP BY `title`, `variant`, `course_city`, `course_date`
) AS x;

Best regards

Maybe related with https://github.com/contributte/datagrid-nette-database-data-source/pull/12.


implement exec closures

High level points:

Fn/FnMut/FnOnce can now be called in exec mode.
Closures that capture mutable references are not supported yet.
Every Fn/FnMut/FnOnce object now implements a trait FnWithSpecification which gives it requires and ensures spec functions.
Fn/FnMut/FnOnce can no longer be called in spec mode; only FnSpec can be called in spec mode. This breaks some existing code.

More details:

This makes the following changes to VIR AST:

Adds Typ::AnonymousClosure. The old Lambda type now only applies to FnSpec (and should probably be renamed). Similar to tuple types, these are translated into datatypes by ast_simplify.
Adds CallTarget::FnExec for any non-static function calls that are exec. The determination of whether something is FnSpec or FnExec is type-based (depending on whether the type is FnSpec).
Adds CallTarget::BuiltinSpecFun. This is for the builtin requires and ensures functions. Currently requires has type (Params) -> bool, while ensures has type (Params, Ret) -> bool.
Adds ExprX::ExecClosure.
Removes the old GenericBoundX::FnSpec. This was previously used to turn the Fn/FnMut/FnOnce traits into Lambda types.

Lowering to SST and then AIR has several components:

The builtin requires/ensures functions get translated to special AIR functions. These have a hardcoded name, similar to height.
When calling into a closure, we have to generate preconditions and postconditions. Instead of calling statically determined requires and ensures, we call the requires and ensures builtins using the callee as an argument.
Everything inside the closure gets translated into an SST ClosureInner, which behaves like a DeadEnd.
When creating a closure, we have to create an object that has the appropriate specifications via the requires and ensures builtins.

 I'm thinking of moving this part into ast_simplify. This is now done in ast_simplify.

TODO:

[ ] add special syntax to the macro
[ ] add a check that the user doesn't reference any non-captured mutable variable in ghost code. (This would not lead to unsoundness, but in one of our discussions, we decided it might be confusing if it were allowed.) Right now I'm not really sure what the easiest way to do this check is.
[x] potentially move some of the lowering code into ast_simplify

Since the main thing left to do is add an additional check, which shouldn't interfere with any of the existing code, I'm going to go ahead and mark this as ready-for-review.
I'm still not sure what's the best way to implement that check, so I'm looking for pointers here. What I want to check for is any variables which is (i) marked mut (ii) NOT captured in the closure by exec/proof code but (iii) IS captured by spec code. But I'm not actually sure how to get the variable modes since the mode-checker currently has this delayed choice stuff. So I'm not sure what's the easiest way to get the mode of a variable usage?

If you want to just get variable modes, you can use ErasureModes::var_modes.  You can ignore inferred_modes; that's for BinaryOp::Arith.  Is this check intended to generate warnings or errors?

I think this makes sense.  My main comment (discussed a little offline) is that, in the implementation, we could look for ways to consolidate  exec closure call code with trait call code (e.g. StmX::DynCall with StmX::Call).

I'll look into the possibility of consolidating some of the new code with traits code.

I removed the SST DynCall and the AST FnExec. I replaced them both with a fake static call to this, now defined in pervasive:
#[verifier(custom_req_err("Call to non-static function fails to satisfy `callee.requires(args)`"))]
#[doc(hidden)]
#[verifier(external_body)]
fn exec_nonstatic_call<Args, Output, F>(f: F, args: Args) -> Output
    where F: FnOnce<Args, Output=Output>
{
    requires(f.requires(args));
    ensures(|output: Output| f.ensures(args, output));
    unimplemented!();
}


Implement Gain scheduling for ZMP/CoM controller

In order to reduce oscillation during the stance phase, the gain scheduling strategy is implemented for the ZMP/CoM controller
This is on top of #7
Simulation

TODO

[x] Implement the gain scheduling
[x] Test on simulation
[x] Test on iCub

Last week we test the on iCubGenova04. This reduces a lot the oscillation during the stance phase.

Since the last merge point is always at the end of the trajectory the idea is to use this information to understand if the trajectory is finished or not.

So m_stancePhase has a misleading name, since it does not refer to the stance phase of a step, but rather determines if the robot is standing still. I think I have not understood when this mechanism takes place. In which cases that variable is supposed to be true?

In which cases that variable is supposed to be true?

Only when the trajectory is finished. In other words, using the joypad, the gains on the ZMP are reduced only when iCub stops. The default gains are restored when a new trajectory is attached.

I would say that I am not completely convinced. By using the merge points you are using directly (and modifying, https://github.com/GiulioRomualdi/capture-point-walking/blob/5fd623f8dbaf4b16f974a820bad332eb15244807/modules/Walking_module/src/WalkingModule.cpp#L1671-L1672), a mechanism which was meant for the generation of new trajectories only. Somehow it seems an abuse to me. The risk is that, if , for some reasons, the mechanism of attaching new trajectories changes, this is going to be broken.

Are there any other conditions to be checked which are more directly related to the stopping of the robot (like some velocity going to zero)?

Maybe I can check the norm of the velocity of the DCM, if it is lower than a threshold the gain are updated. What do you think?

Much better!


WARNING: Wrapping Vararg directly in UnionAll is deprecated (wrap the tuple instead)

See also: https://github.com/chriselrod/LoopVectorization.jl/issues/175
cc: @chriselrod

@chriselrod I'm closing this as fixed by https://github.com/SciML/ArrayInterface.jl/commit/57b03b300433c2bce2ffdc8ade97682b096bef89, correct?

Should be fixed, yes.


VueJS Props Hyphenation

The VueJS Standard is to hyphenate properties like isVisible -> is-visible
What is the Standard for StencilJS?
Would the code break if we enforce hyphenated properties (from what we can see it works for most but for example pd-table iconConfig.prop -> icon-config.prop does not work)

I think normally that should be possible as they document it: https://stenciljs.com/docs/properties#prop-decorator

In HTML, you must set attributes using dash-case, in JSX you set an attribute using camelCase

We could enforce it over the Prop attribute to set the name we want to enforce.
@thomasschneiter wdyt?

I would like to keep the Stencil default: html -> dash-case, jsx -> camelCase.
Since we provide the library to multiple frameworks and most of them use camelCase in 'code-behind'.
E.g. for simple JS we'd have table.icon-config = { ... }; if we hyphenate the properties.


Correctly implement Viewer Matrix vs Model Matrix

Fixed in https://github.com/vimaec/vim-webgl-viewer/pull/138


Add ability to change local exec interpreter from variable.

Background
We ran into issue where terraform local-exec was failing in travis CI as default interpreter was /bin/sh which was exiting with non zero status code. We had to change the interpreter to /bin/bash to successfully run the local-exec to apply configmap-auth via travis CI.
Hence, I have created a PR that will inject the interpreter type as a variable to this module.

/codefresh run test


i18n(es): Fix typo in api-reference.mdx

Description (required)
Remove untranslated text

Lunaria Status Overview
🌑 This pull request will not trigger status changes.

Learn more
Lunaria automatically ignores changes on specific PRs by adding a ignored keyword in its title. Found: typo.
You can change this by either removing the keyword above from the PR's title, or modifying the ignoreKeywords property in your Lunaria configuration file.

Tracked Files

Locale
File
Note

es
reference/api-reference.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Prepare for GitHub API versions

See also https://docs.github.com/en/rest/overview/api-versions
@yanyongyu it can be a thing that GitHub versions its API endpoints :)

The versioning of rest-api can be hard to support until the github/rest-api-description support it. Changing the rest api version will cause model definitions and client methods to change.

https://github.com/github/rest-api-description/ has added versioned schema.

githubkit currently does not specify a rest api version and github will use the default version. But githubkit now generates the model using the latest model instead of 2022-11-28. We may change this behavior first.

Due to #11, the core logic of codegen may change. For now, i would like to add the version tag to codegen and output the version header in client request.


fix FocusDialogContainerTestCase on Edge (after reducing waitFor delay)

This commit adds some pauses in the test because of the following strange behavior in Edge: clicking on another field just after focusing a field with the keyboard has no effect to change the focus, it is necessary to wait a bit after focusing the field before the click on another field has some effect.

The issue seems to be due to a touchpad setting which can be disabled in Windows 10:
Settings -> Devices -> Mouse & touchpad -> Touchpad section

To help prevent the cursor from accidentally moving while you type, change the delay before clicks work

The setting can be set to: No delay (always on)

I am closing this issue as it can be better solved by changing the setting in Windows 10.


Update README.md

Fix formatting of Implied Volatility Formulas lists

Thanks, good spot. It has been merged :+1:


car not stopping

The car does not always stop when there is a stop sign or red light.

that seems like a potentially dangerous issue.

@jmo366 what changes in the software do you think would help the vehicle be more responsive in situations where a full stop is required?


incorrect parentage: "cell migration" not a type of "cell motility"

While curating Wang et al. 2020 that indicates that Pdilt is involved in the same process as Lypd4 to mature Adam3, a sperm cell surface protein involved in the process of fertilization:

Wang D, et al. LYPD4, mouse homolog of a human acrosome protein, is essential for sperm fertilizing ability and male fertility. Biol Reprod. 2020 Apr 24;102(5):1033-1044. PMID: 32040177.

I noticed that Tokuhiro et al. 2012 is cited as the source of an annotation of Pdilt to "sperm motility" though both of these two papers indicate that mutations in either Lypd4 or Pdilt do NOT cause defects in sperm motility, but instead in "migration of sperm from uterus to oviduct":

Tokuhiro K, et al. Protein disulfide isomerase homolog PDILT is required for quality control of sperm membrane protein ADAM3 and male fertility [corrected]. Proc Natl Acad Sci U S A. 2012 Mar 6;109(10):3850-5. PMID: 22357757

Looking in Noctua, I see that the curator actually chose the term "cell migration", but that the logic over the GO term, extensions, and relationships has come up with the term "sperm motility":

I think it is INCORRECT to say that "cell migration" is a "cell motility". The definition of "cell migration" includes the fact that the movement of the cell is guided by molecular cues.
It seems that the CORRECT relationship is that "cell migration" has_part "cell motility"
where "cell motility" refers to methods of cell motility, e.g.:

actin polymerization-dependent cell motility (GO:0070358)
cell gliding (GO:0071976)
cilium or flagellum-dependent cell motility (GO:0001539)
ameoidal-type cell motility
** this term does not exist, but we do have "ameboidal-type cell migration" (GO:0001667) & "amoeboid sperm motility" (GO:0097723)
cytoskeleton-mediated cell swimming (GO:0071979)
substrate-dependent cell motility
** this term does not exist, but we do have  "substrate-dependent cell migration" (GO:0006929)
type IV pilus-dependent motility (GO:0043107)

These direct child terms of "cell motility" might actually be intended to be migration terms and probably merit a closer look:

cell motility in response to calcium ion (GO:0097231)
cell motility in response to potassium ion (GO:0097230)
cell motility involved in camera-type eye morphogenesis (GO:0003411)
cell motility involved in cerebral cortex radial glia guided migration (GO:0021814)
cell movement involved in somal translocation (GO:0021805)

For reference, here are portions of the stanzas for each of these two terms:

id: GO:0048870
name: cell motility
namespace: biological_process
def: "Any process involved in the controlled self-propelled movement of a cell that results in translocation of the cell from one place to another." [GOC:dgh, GOC:dph, GOC:isa_complete, GOC:mlg]
synonym: "cell locomotion" EXACT []
synonym: "cell movement" RELATED []
synonym: "movement of a cell" EXACT []
is_a: GO:0009987 ! cellular process

id: GO:0016477
name: cell migration
namespace: biological_process
def: "The controlled self-propelled movement of a cell from one site to a destination guided by molecular cues." [GOC:cjm, GOC:dph, GOC:ems, GOC:pf, Wikipedia:Cell_migration]
is_a: GO:0048870 ! cell motility

@ukemi - your thoughts on this issue would be greatly appreciated

It seems that the CORRECT relationship is that "cell migration" has_part "cell motility"

Actually, I think it might NOT be correct to code any absolute relationship between "cell migration" and "cell motility", at least not between these two terms, though it may be appropriate to code relationships between specific types of cell motility and specific cell migrations.
Quotes from: Barton LJ, LeBlanc MG, Lehmann R. Finding their way: themes in germ cell migration. Curr Opin Cell Biol. 2016 Oct;42:128-137.  PMID: 27484857

The translocation of germ cells from the place of origin to the developing somatic gonad involves several processes including passive movements with underlying tissues, transepithelial migration, cell adhesion dynamics, the establishment of environmental guidance cues and the ability to sustain directed migration.

and regarding one phase of embryonic germ cell migration in some organisms:

In Drosophila and Xenopus, the translocation with endodermal tissue is a passive process and known to require germ cell adhesion to underlying endodermal epithelium

@krchristie 'passive' processes do not apply to GO, since no genes mediate them. All protein-mediate migration likely involves motililty.

@krchristie 'passive' processes do not apply to GO, since no genes mediate them. All protein-mediate migration likely involves motililty.

@pgaudet - Why did you close this?
This comment about whether or not it is true to say that "cell migration" always has some "cell motililty" or not (depending on whether you want to talk about whether or not the migrating cells are motile cells, or are "riding" on other cells that do have cell motility) has no impact on the fact that it is not true to say that "cell migration" is_a "cell motility.
"cell migration" is a process that includes additional signalling processes in addition to cell motility.
This incorrect relationship is causing some incorrect inferred annotations.
"cell migration" needs to become a direct child of "cellular process" so that it will be a sibling of "cell motility", not a child of it.


The $IsLinux variable is set to true on non-Linux platforms

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
I am running PowerShell as a native FreeBSD build using RID "freebsd-x64" and "freebsd-arm64".
Expected behavior
I would expect when on FreeBSD for $IsLinux to be false

I would expect $IsLinux to have the same value as [System.OperatingSystem]::IsLinux()

Actual behavior
PS> @{ IsWindows=$IsWindows;IsLinux=$IsLinux;IsMacOS=$IsMacOS }

Name                           Value
----                           -----
IsLinux                        True
IsMacOS                        False
IsWindows                      False

PS> [System.OperatingSystem]::IsLinux()
False
PS> [System.OperatingSystem]::IsFreeBSD()
True

Error details
no actual error

Environment data
Name                           Value
----                           -----
PSVersion                      7.4.5
PSEdition                      Core
GitCommitId                    7.4.5
OS                             FreeBSD 13.3-RELEASE FreeBSD 13.3-RELEASE releng/13.3-n257428-80d2b634ddf0 GENERIC
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0â€}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

good，It is time to new an automatic variable for freebsd:  $IsFreeBsd
for next：
After conducting a period of testing, find a way to let the compile into freebsd ports

I would expect $IsLinux to have the same value as [System.OperatingSystem]::IsLinux()

It is exactly so in pwsh code.

It is time to new an automatic variable for freebsd: $IsFreeBsd

Will be in https://github.com/PowerShell/PowerShell/pull/20041

That is excellent news!


Basic auth  in get frame requests does not work

Hi!
I try to use BasicAuth in OHIF with my local dicomweb server. I have:
  servers: {
    dicomWeb: [
      {
        name: 'My local dev',
        qidoRoot: 'https://<IP_ADDRESS>:8080',
        wadoRoot: 'https://<IP_ADDRESS>:8080',
        qidoSupportsIncludeField: true,
        imageRendering: 'wadors',
        thumbnailRendering: 'wadors',
        enableStudyLazyLoad: true,
        supportsFuzzyMatching: true,
        requestOptions: {
          auth: 'username:password',
	},
      },
    ],
  },

QIDO requests like get studies, get series works fine. Request for get metadata works fine too.
But in the get frame requests like:
https://<IP_ADDRESS>:8080/studies/1.2.8<IP_ADDRESS>80043.8.1055.1.20111102150758591.92402465.76095170/series/1.2.8<IP_ADDRESS>80043.8.1055.1.20111102150758591.96842950.07877442/instances/1.2.8<IP_ADDRESS>80043.8.1055.1.20111102150831466.74318282.34203447/frames/1
there is no Authorization headers.
Is there any way to add Authorization headers for all requests?

I'm facing exactly the same issue. In wado request while fetching the instances somewhere we need to include the authorization header i.e. headers: DICOMWeb.getAuthorizationHeader(server) but can't figure out exactly where.

Please review the latest code in the master branch. This issue might have been resolved. If it persists, kindly reopen the issue with updated details.
Try viewer-dev.ohif.org instead of viewer.ohif.org
Our viewer.ohif.org is deployed from release branch while viewer-dev.ohif.org is our master  branch
Read more about branch explanations here https://docs.ohif.org/development/getting-started#developing


IndexError: tuple index out of range on spec_augment_pytorch

Any idea on how to resolve this problem?
from SpecAugment import spec_augment_pytorch as spec_augment_l
import librosa

y, sr = librosa.load(dataset_audio_path.joinpath(audio_path), sr=16000)
y, _ = librosa.effects.trim(y, top_db=15)
S = librosa.feature.melspectrogram(y, sr=sr, n_fft=2048, hop_length=512, n_mels=128)
S = librosa.power_to_db(S, ref=np.max)
S = spec_augment_l.spec_augment(mel_spectrogram=S)

---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-10-9e6d8eca1293> in <module>
     14     plt.pause(0.001)  # pause a bit so that plots are updated
     15
---> 16 inputs, classes = next(iter(train_dataloader))
     17 out = make_grid(inputs)
     18 class_names = train_dataset.classes

~\anaconda3\envs\torch\lib\site-packages\torch\utils\data\dataloader.py in __next__(self)
    343
    344     def __next__(self):
--> 345         data = self._next_data()
    346         self._num_yielded += 1
    347         if self._dataset_kind == _DatasetKind.Iterable and \

~\anaconda3\envs\torch\lib\site-packages\torch\utils\data\dataloader.py in _next_data(self)
    383     def _next_data(self):
    384         index = self._next_index()  # may raise StopIteration
--> 385         data = self._dataset_fetcher.fetch(index)  # may raise StopIteration
    386         if self._pin_memory:
    387             data = _utils.pin_memory.pin_memory(data)

~\anaconda3\envs\torch\lib\site-packages\torch\utils\data\_utils\fetch.py in fetch(self, possibly_batched_index)
     42     def fetch(self, possibly_batched_index):
     43         if self.auto_collation:
---> 44             data = [self.dataset[idx] for idx in possibly_batched_index]
     45         else:
     46             data = self.dataset[possibly_batched_index]

~\anaconda3\envs\torch\lib\site-packages\torch\utils\data\_utils\fetch.py in <listcomp>(.0)
     42     def fetch(self, possibly_batched_index):
     43         if self.auto_collation:
---> 44             data = [self.dataset[idx] for idx in possibly_batched_index]
     45         else:
     46             data = self.dataset[possibly_batched_index]

~\anaconda3\envs\torch\lib\site-packages\torchvision\datasets\folder.py in __getitem__(self, index)
    133         """
    134         path, target = self.samples[index]
--> 135         sample = self.loader(path)
    136         if self.transform is not None:
    137             sample = self.transform(sample)

<ipython-input-9-9aca4872e8ea> in spec_augment_loader(audio_path)
     40     S = librosa.feature.melspectrogram(y, sr=sr, n_fft=2048, hop_length=512, n_mels=128)
     41     S = librosa.power_to_db(S, ref=np.max)
---> 42     S = spec_augment_l.spec_augment(mel_spectrogram=S)
     43     fig = plt.Figure(figsize=figsize, dpi=dpi, frameon=False)
     44     fig.patch.set_visible(False)

~\anaconda3\envs\torch\lib\site-packages\SpecAugment\spec_augment_pytorch.py in spec_augment(mel_spectrogram, time_warping_para, frequency_masking_para, time_masking_para, frequency_mask_num, time_mask_num)
     87     """
     88     v = mel_spectrogram.shape[1]
---> 89     tau = mel_spectrogram.shape[2]
     90
     91     # Step 1 : Time warping

IndexError: tuple index out of range

Encountered the same issue myself. It's expecting a 3d input [Batch x H x W], so if you input a single data point [H x W], then you will get out of range errors. The solution is to use a batch of inputs, or modify the code to expect a single data point as input

Hi any one solve this issue ? I have encountered the same.

@Aditya3107 yes - see my comment above

@Aditya3107 yes - see my comment above

@DWhettam Hi, yes I applied your solution but still no success. I faced below problem.
`(venv) mds-student@mdsstudent-HP-Compaq-Elite-8300-CMT:~/Documents/SpecAugment-master$ python3
Python 3.8.5 (default, Aug  5 2020, 08:36:46)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.

import librosa
from SpecAugment import spec_augment_pytorch
audio, sampling_rate = librosa.load('data/61-70968-0002.wav')
mel_spectrogram = librosa.feature.melspectrogram(y = audio, sr = sampling_rate, n_mels = 256, hop_length = 128, fmax = 8000)
warped_masked_spectrogram = spec_augment_tensorflow.spec_augment(mel_spectrogram = mel_spectrogram)
Traceback (most recent call last):
File "", line 1, in
NameError: name 'spec_augment_tensorflow' is not defined
warped_masked_spectrogram = spec_augment_pytorch.spec_augment(mel_spectrogram = mel_spectrogram)
Traceback (most recent call last):
File "", line 1, in
File "/home/mds-student/Documents/SpecAugment-master/SpecAugment/spec_augment_pytorch.py", line 97, in spec_augment
warped_mel_spectrogram = time_warp(mel_spectrogram, W=time_warping_para)
File "/home/mds-student/Documents/SpecAugment-master/SpecAugment/spec_augment_pytorch.py", line 63, in time_warp
warped_spectro, dense_flows = sparse_image_warp(spec, src_pts, dest_pts)
File "/home/mds-student/.local/lib/python3.8/site-packages/specAugment/sparse_image_warp_pytorch.py", line 138, in sparse_image_warp
image = ops.convert_to_tensor(image)
NameError: name 'ops' is not defined`

If you can suggest some solution it would be helpful.

you are importing spec_augment_pytorch, but calling spec_augment_tensorflow. That's why you are getting the error:
NameError: name 'spec_augment_tensorflow' is not defined
if you are using pytorch you need to use spec_augment_pytorch

@DWhettam  thank you for the response. But I have taken pytorch only. For the particular code snippet shown above first I took tensorflow mistakenly then I corrected it with pytorch.
warped_masked_spectrogram = spec_augment_pytorch.spec_augment(mel_spectrogram = mel_spectrogram) Traceback (most recent call last): File "", line 1, in File "/home/mds-student/Documents/SpecAugment-master/SpecAugment/spec_augment_pytorch.py", line 97, in spec_augment warped_mel_spectrogram = time_warp(mel_spectrogram, W=time_warping_para) File "/home/mds-student/Documents/SpecAugment-master/SpecAugment/spec_augment_pytorch.py", line 63, in time_warp warped_spectro, dense_flows = sparse_image_warp(spec, src_pts, dest_pts) File "/home/mds-student/.local/lib/python3.8/site-packages/specAugment/sparse_image_warp_pytorch.py", line 138, in sparse_image_warp image = ops.convert_to_tensor(image) NameError: name 'ops' is not defined

It looks like you are still using the incorrect files. Read through your error message and you can see the error occurs here:
line 138, in sparse_image_warp image = ops.convert_to_tensor(image)
however, image = ops.convert_to_tensor(image) is not in the original sparse_image_warp_pytorch.py file. Have you modified the files in some way, or changed their names? I would re-download the repo and start fresh.

Hi, you can use the example in the tests/ folder, there it converts the spectrogram to [batch_size, time, frequency, 1]

Hi, thanks for reply. It is working for me.


fix: prevent exceptions for unparse-able anon ops

you'll see now that the graphql parser still fails on multiple anonymous operations in one query, however we're at least able to parse the query and not break the application with keys or undefined paths, and the dropdown still works
Fixes #1308

ended up bringing this into the typescript migration to fix a bug, so consider this fix merged :D


All wallets should check against blacklist before transfer to save users from losing funds

@brianoflondon just lost funds sending to bloctrades instead of blocktrades using keychain. It's really important that wallets use the blacklist of phishing account names to avoid such losses. Please add this on a priority basis to avoid further fund losses (I just realized I should create a similar isssue for the hive cli wallet).

Yup, not looking for anybody's sympathy, but just to help other's avoid this kind of thing and make the whole system safer.

@dnotestein where can I find this list? I ll implement it asap

https://gitlab.syncad.com/hive/condenser/-/blob/develop/src/app/utils/BadActorList.js


auroracoind core dumps on start

This issue is with the latest commit dd875f52677839ae234703726cdec3986367f4d2.
After a successful build, starting auroracoind causes a core dump with the following error:
auroracoind: chainparams.cpp:149: CMainParams::CMainParams(): Assertion `hashGenesisBlock == uint256("0x2a8e100939494904af825b488596ddd536b3a96226ad02e0f7ab7ae472b27a8e")' failed.
Aborted (core dumped)

The commit you're referencing is on a development branch that hasn't been anywhere near finished yet.  When it is completed, tested, and verified working, it will be merged into a master branch and made the main repo.  That's a little ways off though.
If you're trying to build AUR, you need to build from the master-0.8 branch, which is the main branch at this time.


Centered Text Function

With this you can center the text on the motd easy without adding additional spaces, just adding something like %newline%%centered%
that should be good

Posting here for future reference: https://www.spigotmc.org/threads/centering-a-motd.49945/

Added with 5.2.0 https://github.com/AlexProgrammerDE/PistonMOTD/releases/tag/5.2.0


Feature Request: Filter by ArtifactType after calling oci Store.Predecessors()

I'd like to filter manifests by ArtifactType after calling oci Store.Predecessors(), for example, only keeping notary signatures ("application/vnd.cncf.notary.signature").
Currently, the ArtifactType field is cut after calling Predecessors(), which is blocking my filtering.
Is it feasible to keep the ArtifactType information for Predecessors()?

Extracting ArtifactType is not the purpose of the Predecessors() and it requires additional I/Os.
@patrickzheng200 If you are interested, you can take a look at the related oras implementation.

Extracting ArtifactType is not the purpose of the Predecessors() and it requires additional I/Os.
@patrickzheng200 If you are interested, you can take a look at the related oras implementation.

@shizhMSFT hmm, to my understanding, Predecessors() serves as the OCI layout substitution of the OCI v1.1 Referrers API in oras-go. Please correct me if I'm wrong. Since Referrers API has the ability to filter by ArtifactType, should we also support this feature in Predecessors()?

Predecessors() is a method to find all predecessors of the current node in terms of the graph. It cares about the nodes themself (i.e. media type, digest, size) but not their metadata (e.g. artifact type). Predecessors() applies to all GraphStorage where registries are instances of GraphStorage.
On the other hand, Referrers API works similar to Predecessors() but only finds certain types of predecessors (i.e. manifest types.) iff the current node is of manifest types. Besides, Referrers API also returns ArtifactType and Annotations of the found predecessors per spec.

Therefore, Predecessors() and Referrers() are not interchangeable.
Nonetheless, Referrers() can be used as a degraded Predecessors. For example, remote repositories:
https://github.com/oras-project/oras-go/blob/96a37c2b359ac1305f70dc31b28c789688d77d0f/registry/remote/repository.go#L365-L378
Meanwhile, Referrers() can be implemented using Predecessors() with degraded performance.

@shizhMSFT thanks for the detailed explanation! So by design, we are not simply substituting Referrers API with Predecessors() in OCI layout. I get the differences now.

Closing as a duplicate of #392


Permission denied when creating keys

If you run into [Errno 13] Permission denied: '/home/$USER/.commune/key'
when creating or manipulating your keys.
Make sure to run the following:
sudo chown -R $USER:$USER ~/.commune

Do you know what causes this folder to be created with the wrong owner?
Perhaps it's when the user runs the a docker image that mounts a volume on ~/.commune before any other operation that uses the folder then the Docker daemon creates all parent folders with root:root owner?
Do commune have any other operations that usually run as root/sudo and write to ~/.commune?


Run Script on Startup?

I use your container and need to run a simple .sh script on startup. Does it support launching scripts on startup?
On all LinuxServer.io containers you're able to achieve this by placing a script /config/custom-cont-init.d/onstart.sh and mounting it appropriately.
Can someone with the ability please add a similar method to this project? It'll be greatly appreciated.

The image has a script for geoip in /etc/periodic/monthly. This called from root's crontab in /etc/crontabs/root. I think this means we have cron available to us, so you could make use of that.
Although, if you run rtorrent in kubernetes or a variation thereof, an init container doing the job is probably a better idea.

Custom scripting will not be added to this image. Feel free to fork or build on top of this image if you want.

You can do basically the same thing just add the script to
/etc/cont-init.d/
Depending on where you want to do, you have to be careful about where you name the script


Disable in a per-syntax basis?

Hi,
personally I find indentation guides only necessary/helpful for indentation-based syntaxes such as haml,  coffee, python and sass. But for most programming languages, guides are a quite noisy thing to have imo.
Can one apply intent-guide-improved using a syntax whitelist/blacklist?
I'm guessing that the packages doesn't include this feature, would it be easy to implement? Maybe Atom provides a generic enabling/disabling mechanism which could be applied here?
Cheers - Victor

I see the fix can be easy to implement https://github.com/Glavin001/atom-beautify/pull/141/files


Entrypoint's 'if our command is a valid Docker subcommand, let's invoke it through Docker instead' doesn't work anymore with 1.13

If you run docker run docker:1.12 docker foo --help it will exit with
docker: 'foo' is not a docker command.
See 'docker --help'.

and status code 1. The entrypoint script expects this behavior.
But if you do the same with 1.13 RC, docker run docker:1.13-rc docker foo --help will print the regular help text and exit with status code 0. This will cause the entrypoint script's check to believe that everything is a valid docker subcommand, and it will try to pass everything to docker.
This makes regular usage a bit difficult, for instance docker run docker:1.13-rc true fails, saying docker: 'true' is not a docker command.. Also, notably, this breaks usage with GitLab CI (and probably other CI systems that would use Docker). GitLab CI tries to run some shell commands to set up the container, but they fail with 1.13-rc cause of this.

Never mind, fixed by https://github.com/docker/docker/pull/28773


Support including charset in Content-Type

Content-Type not only includes the mime, but may include other information in it like Charset.
The server may response with a Content-Type set to application/scim+json; charset=utf-8 for instance, it is still valid.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type

Thank you for your contribution. There was already a fix for that in #18. It has been merged and released in 0.1.11!


Error while creating build definition: TF401019: The Git repository with name or identifier 779D8E0C-355F-46A8-B232-ABB2CC07ACB0 does not exist or you do not have permissions for the operation you are attempting.

Created custom template to create DevOps project.
The project gets created fine but I get this error and a service connection to an unknown GitHub repo is added to the project.

Error while creating build definition: TF401019: The Git repository with name or identifier 779D8E0C-355F-46A8-B232-ABB2CC07ACB0 does not exist or you do not have permissions for the operation you are attempting.

Hello @pascalbillot, thank you for reaching us.
This might occur when the repository that you want to use is private.
Can you unzip the template file and check /serviceendpoints/*.json files. If you see any repository that is private and trying to authenticate, make it public and try once.
Let us know your updates.

@pascalbillot we are closing the issue, you can reopen the same if the issue persists


Other SCRAM passwords

Hello @tv42,
Thanks for your work on SCRAM!
Why do you not rename your repository:

scram-sha-256-password

And create others like:

scram-sha-1-password
scram-sha-512-password
scram-sha3-512-password

Or have one for all?
Some people uses other hashes too.

SCRAM-SHA-512 and SCRAM-SHA3-512 are not specified: https://www.iana.org/assignments/sasl-mechanisms/sasl-mechanisms.xhtml#scram
SCRAM-SHA-512 etc also have no reason to exist; SHA256 is plenty strong for the use, and if it isn't then you need a real passphrase storage solution, with memory-hardness etc.
Nobody should be using SHA-1 for anything new, and I haven't encountered any software that uses SCRAM-SHA-1 so I haven't programmed it.
This repository is just a little command-line wrapper over https://github.com/xdg-go/scram


[master] sync the master branch with upstream stable

This sync includes:
https://github.com/opendatahub-io/kubeflow/pull/320
https://github.com/opendatahub-io/kubeflow/pull/328
Related-JIRA: https://issues.redhat.com/browse/RHOAIENG-6410

Merging this PR.


Position of the 'toggle sidebar' button

Use case
Match the native positioning of the 'toggle sidebar' button
Proposal
Have the button for toggling the sidebar in the same position as native macos apps.
When toggling, in native apps, the position stays the same.
[Current Flutter macos_ui version]

[Native version]

You’re right. It appears that the native ‘toggle sidebar’ button remains stationary when the sidebar is clicked. I’ll try to investigate this issue.


Unclear Approve and Transfer

Describe the bug
The site checks for token spending approval after clicking transfer, and then prompts 2 transactions to the user (approval and transfer). We should make it clear to the user that they are doing 2 separate transactions and show what they are before clicking on "Transfer".
To Reproduce
Steps to reproduce the behavior:
Have approval limit set to 0 before starting.

Go to https://amarok-testnet.coinhippo.io/
Select an amount
Click Transfer
See problem

Expected behavior
The site should check for token approval and show an approve button before clicking on transfer.
We received this feedback from a few users but I still think this is up for debate. I believe some platforms do it the way I described and some others do it like we're doing right now.

Based on the above feedback, UX improvements already happened.


add truncated_normal to initializers

Codecov Report

Merging #3401 (9521cf9) into main (d059ba8) will decrease coverage by 0.02%.
Report is 4 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #3401      +/-   ##
==========================================
- Coverage   83.60%   83.59%   -0.02%
==========================================
  Files          56       56
  Lines        6746     6747       +1
==========================================
  Hits         5640     5640
- Misses       1106     1107       +1

Files
Coverage Δ

flax/linen/initializers.py
100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes


Handling of Multiple Words

Seems like concise concepts, while great, isn't able to assign entities to "multiple words". For instance, it might pick up:
Mashed -> ENT
Potato -> ENT
But not "Mashed Potato" -> ENT
Is there any way that we can solve for this?

I agree. @nv78 I need to look into compound chains to handle this properly. Have been playing around with this but will probably be covered during my vacation in April:)

Perfect, reach out at<EMAIL_ADDRESS>if you need someone to test!

This would be a killer feature! 🔥🔥🔥

Agreed - we've had this issue for a while! If there is a solution for multi word entity recognizers, let me know.

It seems to be possible when using Prodigy (from Explosion AI).
Check the video below:
https://m.youtube.com/watch?time_continue=324&v=59BKHO_xBPA&embeds_euri=https%3A%2F%2Fprodi.gy%2F&feature=emb_title
The seed entities are single words (like broccoli) but the suggested entities include feta cheese and tomato soup


cubemap-renderer.js - Trying to bind current color buffer as a texture

Using the default script cubemap-renderer.js in the editor results in an error: Trying to bind current color buffer as a texture
https://playcanvas.com/editor/scene/1088850
And how to use prefiltered data whit a rendered cubemap? A simple change to the glossiness does not work.

please see here
https://forum.playcanvas.com/t/dynamic-cubemaps-reflection-probes-render-to-texture-in-2020/15959


Configurable voting-degree in council elections pallet

This makes the number of votes per voter in the council election pallet configurable.
Configure This Pallet Responsibly.
This allows parachain teams to configure the pallet with parameters that are safe in parachain context.
Use MaxVoters, MaxCandidates and MaxVotesPerVoter to make sure the weight of the election does not exceed the full block weight. See fn integrity_test for more detail.

As a follow-up, In #12588, we should provide a new naive solver that just calculates approval stakes, and announces the top candidates as winners. This should be much cheaper to compute compared to phragmen.
polkadot companion: https://github.com/paritytech/polkadot/pull/6680
related https://github.com/paritytech/srlabs_findings/issues/263

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2347596

/cmd queue -c bench $ pallet polkadot-dev pallet_elections_phragmen

/cmd queue -c bench $ pallet dev pallet_elections_phragmen

/cmd cancel 72-ca982630-9326-4b29-896c-7ad5f468c2de

/cmd queue -c bench $ pallet dev pallet_elections_phragmen

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2360440

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2360789

bot merge


Enable customizable registration.

Allows plugins to override the registration process, but still fallback to a good basic registration strategy (the same as used prior to this PR).
To add its own registration, a plugin need only have the following:

ember-service-worker-plugin keyword
service-worker-registration/index.js file

See #31 for some additional background / motivation on this.
Closes #31

@martndemus - Updated to use registration technique.

LGTM :+1:


libc++abi.dylib: terminating with uncaught exception of type NSException

I followed all the steps on iOS incl. deep linking etc. However when the redirect happens (back to the app), I get the following exception:
<DCTOAuth2Account: 0x600000526ae0; type = appname; identifier = 0DF59F02-57C9-4CB8-B163-677976E75502; credential = (null)>
2017-06-22 22:20:12.715 appname[60610:4056225] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'

Any ideas?

So it looks like there is a even deeper underlying issue. I traced it down to the fact that the app says that my URL is not supported. Yet everything is registered properly:
Error Domain=NSURLErrorDomain
Code=-1002 "unsupported URL"
UserInfo={NSUnderlyingError=0x600000845610
{Error Domain=kCFErrorDomainCFNetwork
Code=-1002 "unsupported URL"
UserInfo=
{NSErrorFailingURLStringKey=myapp://oauth2/authorize,
 NSLocalizedDescription=unsupported URL,
  NSErrorFailingURLKey=myapp://oauth2/authorize}},
   NSErrorFailingURLStringKey=myapp://oauth2/authorize,
   NSErrorFailingURLKey=myapp://oauth2/authorize,
   NSLocalizedDescription=unsupported URL}

any ideas?


Browsing for files to add to resources

When browsing to add multiple files to a resource, the file names selected should be listed when there is more than one file.

List files selected rather than just indicating 2 files selected.
If a user browses again the files they select should be added to the list, rather than the list being replaced.
A user should be able to delete files from the files selected.

@hyi @dtarb @mauriel133 Where are we at on this one?

@aphelionz This is an enhancement low priority issue, I don't think it has been worked at yet.

@hyi thank you

Nice work!
I suggest adding a small bit of help text near the Create Resource button such as "When you click Create Resource, the files will be uploaded to the HydroShare server. Click here to learn more about next steps to share and formally publish your data.

Also, add a Create Resource button on the upper right was mentioned in the call. Two buttons? Or one?

Work on this issue has generated changes to the Create Resource page.  On the new create resource page (deployed on beta) I find the following aspects non intuitive

Below where it says "Select a resource type" there is a single button "Composite".  Nothing about that button indicates that if I click on it I will get a drop down list.  Can there be some sort of drop down indicator (inverted triangle is common) to encourage clicking this drop down.
In the "add your files" box it says "or click to upload".  But it is not clear to me "where" I should click.  I find that clicking on the grey area gives me the dialog to upload, but it would be better if there was an indication in the grey area that I should click there.

@mauriel133

tested on beta.  OK


Salinity - Refractometer or cheaper alternative?

Hydrometers (i.e. specific gravity) might be cheap alternative.

From today's lab meeting: Refractometers possibly in the "biology" kits (yeast bubbling kit).


feat: Add additional auto advance time controls

Purpose (TL;DR)
This adds a new mode for automatically advancing time that moves more quickly than the existing shouldAdvanceTime, which uses real time. It also adds the ability to modify the initial values that were used for shouldAdvanceTime and advanceTimeDelta. shouldAdvanceTime is useful in some situations, but is not useful for solving the problem that testers usually install mock clocks for (to speed up time).
Background
Testing with mock clocks can often turn into a real struggle when dealing with situations where some work in the test is truly async and other work is captured by the mock clock.
In addition, when using mock clocks, testers are always forced to write tests with intimate knowledge of when the mock clock needs to be ticked. Oftentimes, the purpose of using a mock clock is to speed up the execution time of the test when there are timeouts involved. It is not often a goal to test the exact timeout values. This can cause tests to be riddled with manual advancements of fake time. It ideal for test code to be written in a way that is independent of whether a mock clock is installed or which mock clock library is used. For example:
document.getElementById('submit');
// https://testing-library.com/docs/dom-testing-library/api-async/#waitfor
await waitFor(() => expect(mockAPI).toHaveBeenCalledTimes(1))

When mock clocks are involved, the above may not be possible if there is some delay involved between the click and the request to the API. Instead, developers would need to manually tick the clock beyond the delay to trigger the API call.
This is different from the existing shouldAdvanceTime in the following ways:
shouldAdvanceTime is essentially setInterval(() => clock.tick(ms), ms) while this feature is const loop = () => setTimeout(() => clock.nextAsync().then(() => loop()), 0);
There are two key differences between these two:

shouldAdvanceTime uses clock.tick(ms) so it synchronously runs all timers inside the "ms" of the clock queue. This doesn't allow the microtask queue to empty between the macrotask timers in the clock whereas something like tickAsync(ms) (or a loop around nextAsync) would. This could arguably be considered a fixable bug in its implementation
shouldAdvanceTime uses real time to advance the same amount of real time in the mock clock. The way I understand it, this feels somewhat like "real time with the opportunity to advance more quickly by manually advancing time". This would be quite different: It advances time as quickly possible and as far as necessary. Without manual ticks, shouldAdvanceTime would only be capabale of automatically advancing as far as the timeout of the test and take the whole real time of the test timeout. In contrast, setTickMode({mode: "nextAsync"}) can theoretically advance infinitely far, limited only by processing speed. Somewhat similar to the --virtual-time-budget feature of headless chrome.

In addition to the "quick mode" of shouldAdvanceTime, this also adds the ability to modify the initially configured values for shouldAdvanceTime and advanceTimeDelta.

Thanks for this, I will have to check out the code at a later time.

testers are always forced to write tests with intimate knowledge of when the mock clock needs to be ticke

just to check ... You are aware of await clock.runAllAsync() and await clock.runToLastAsync(), right? They often solve the issues of needing intimate knowledge about when timers are being fired and when Promises are needing to be resolved.

just to check ... You are aware of await clock.runAllAsync() and await clock.runToLastAsync(), right? They often solve the issues of needing intimate knowledge about when timers are being fired and when Promises are needing to be resolved.

Yes, these are quite useful! Here are some of my thoughts where these still cause some test friction that this feature would help resolve:
When mock clocks are installed, it's not "safe" to await just anything
When writing tests, you have to know that whatever you're awaiting will not wait for any timers to complete. Either that, or you need to make sure that you flush timers before awaiting any promises. It's especially difficult if the function causes a timer to be queued and then waits for it. The way around this would be to save the promise instead of awaiting it, then flush timers, then await the promise (pretty awkward).
When mock clocks are installed, test utilities need to know about it
Today, test utilities that perform async actions need to be written to account for mock clocks. In the above situation, if the function we're talking about was some test harness or test utility, we could tell it how to tick the clock so it can advance time internally rather than us having to do it in the test body.
Concrete example: Testing Gmail's "undo" send button
Consider testing the "undo" send button feature in Gmail. Conceptually, what you want to do in the test is "click send, wait for the toast to appear, then click the 'undo' button". The undo button doesn't appear synchronously and would require running some timers to make it appear. Using runAllAsync would advance time to the point where the email is fully sent and the toast disappears. You'd have to write the test to tick some amount of time for it to appear, but not long enough for it to disappear.
await sendButton.click();
await clock.tickAsync(100);
const undoButton = await page.undoButton();
await undoButton.click();
// follow-up expectations

With the auto-clicking mock clock, this test could instead look much more like it would in an e2e environment (and in fact, could even use the same test body, with the page harnesses swapped out underneath which uses WebDriver or the framework testing library depending on environment):
await sendButton.click();
// Maybe undoButton getter polls for the button with a timeout
const undoButton = await page.undoButton();
await undoButton.click();

In each of the above situations, an automatically advancing mock clock would make testing much more reasonable. It's certainly not always the answer and it may also still be useful to manually flush timers (i.e. in the "undo" button example, flushing timers after clicking undo and then asserting that the RPC to send the message never happened). While runAllAsync and runToLastAsync are absolutely useful, they still require the test author to actually call them to advance time. It's less intimate knowledge of the timer, but it is still needing to know that the promise doesn't resolve in the event loop.


<EMAIL_ADDRESS>not available

Summary
<EMAIL_ADDRESS>not available
Expected behaviour
I can send Emails to<EMAIL_ADDRESS>and somebody can have a look at them.
Actual behaviour
I receive a "Undelivered Mail Returned to Sender" Email:
'''
<EMAIL_ADDRESS>host aspmx.l.google.com[<IP_ADDRESS>] said:
550-5.1.1 The email account that you tried to reach does not exist. Please
try 550-5.1.1 double-checking the recipient's email address for typos or
550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1
https://support.google.com/mail/?p=NoSuchUser k18si1587585wrl.351 - gsmtp
(in reply to RCPT TO command)
'''
Remarks
Same goes for<EMAIL_ADDRESS>I have not checked other default addresses

Strange.. @moellering if you have an issue to disclose, can you send it to:
Me -<EMAIL_ADDRESS>and Daniele -<EMAIL_ADDRESS>

Taking a look

closing as the email is working again


Need to rename the kernel filename to "kernel"

I followed the youtube video and felt I need to rename the kernel file name to its original name "kernel" instead of keeping the name "kernel-x86_64" (which is not required in the video). However, I didn't rename it, and when I installed WSA and tried to open files, it crashed. I uninstalled WSA and renamed the kernel file to "kernel" as it was originally, installed, and files opened.

You should replace the original. Initially, it had no suffix and only supported x86_64 arch.


Bump opentelemetry-proto to 1.4.0-alpha

Fixes https://github.com/advisories/GHSA-735f-pc8j-v9w8.
This PR also removes the explicit definition of protobuf-java.
protobuf-java is actually derived from opentelemetry-proto. This update also transitively updates protobuf-java 3 -> 4.

Thanks @codefromthecrypt !


crash in SAMSUNG s4

@i5ting Can you please provide more details for instance logs (we can't reproduce this crash )?


Update Composer dependencies (2022-03-31-00-02)

Visual regression test passed!
View the visual regression test report