Update dependency lerna to v3

This PR contains the following updates:

Package
Type
Update
Change
References

lerna
devDependencies
major
^2.9.0 -> ^3.0.0
homepage, source

Release Notes

lerna/lerna
v3.4.3
Compare Source
Bug Fixes

publish: Use correct field name when limiting retries (76589d4)

v3.4.2
Compare Source
Bug Fixes

publish: Use correct field name when limiting retries (76589d4)

v3.4.1
Compare Source
Bug Fixes

publish: Prevent retries during access validation so third-party registries are skipped faster (a89ae62)
publish: Use modern auth resolution (7ba41a6)

v3.4.0
Compare Source
Features

publish: Use APIs for validation queries instead of CLI (65fc603)

3.3.2 (2018-09-12)
Bug Fixes

publish: Allow --force-publish in a canary release (b97d9a3), closes #1638
version: Allow --force-publish to work on tagged releases (7971bf3), closes #1667 #1671

3.3.1 (2018-09-11)
Bug Fixes

create: Upgrade whatwg-url to ^7.0.0 (00842d6)
import: Handle filepaths with spaces more robustly (#1655) (b084293)
prompt: Upgrade inquirer to ^6.2.0 (ebb7ee4)
publish: Tell yarn to stop creating git tags (2a6f0a4), closes #1662
run-lifecycle: Remove repetitive error logging (b8915e7)

v3.3.2
Compare Source
Features

publish: Use APIs for validation queries instead of CLI (65fc603)

3.3.2 (2018-09-12)
Bug Fixes

publish: Allow --force-publish in a canary release (b97d9a3), closes #1638
version: Allow --force-publish to work on tagged releases (7971bf3), closes #1667 #1671

3.3.1 (2018-09-11)
Bug Fixes

create: Upgrade whatwg-url to ^7.0.0 (00842d6)
import: Handle filepaths with spaces more robustly (#1655) (b084293)
prompt: Upgrade inquirer to ^6.2.0 (ebb7ee4)
publish: Tell yarn to stop creating git tags (2a6f0a4), closes #1662
run-lifecycle: Remove repetitive error logging (b8915e7)

v3.3.1
Compare Source
Bug Fixes

publish: Allow --force-publish in a canary release (b97d9a3), closes #1638
version: Allow --force-publish to work on tagged releases (7971bf3), closes #1667 #1671

v3.3.0
Compare Source
Bug Fixes

describe-ref: Fallback refCount is the number of commits since beginning of repository (6dfea52)
Propagate exit codes from failed executions (af9c70b), closes #1374 #1653
run-lifecycle: Propagate exit code when execution fails (4763f95), closes #1495

Features

deps: Upgrade execa to ^1.0.0 (748ae4e)
deps: Upgrade fs-extra to ^7.0.0 (042b1a3)
deps: Upgrade get-stream to ^4.0.0 (e280d1d)
deps: Upgrade strong-log-transformer to ^2.0.0 (42b18a1)

3.2.1 (2018-08-28)
Bug Fixes

publish: Use package version as fallback for independent canary bump (989a3b5), closes #1614

v3.2.1
Compare Source
Bug Fixes

describe-ref: Fallback refCount is the number of commits since beginning of repository (6dfea52)
Propagate exit codes from failed executions (af9c70b), closes #1374 #1653
run-lifecycle: Propagate exit code when execution fails (4763f95), closes #1495

Features

deps: Upgrade execa to ^1.0.0 (748ae4e)
deps: Upgrade fs-extra to ^7.0.0 (042b1a3)
deps: Upgrade get-stream to ^4.0.0 (e280d1d)
deps: Upgrade strong-log-transformer to ^2.0.0 (42b18a1)

3.2.1 (2018-08-28)
Bug Fixes

publish: Use package version as fallback for independent canary bump (989a3b5), closes #1614

v3.2.0
Compare Source
Bug Fixes

add: Order short flags first in help output, clarify description (8efb549)
publish: Call synthetic prepublishOnly lifecycle before packing (dda9812), closes #1169
version: Make changes to packages in batched topological order (d799fbf)
version: Skip working tree validation when --no-git-tag-version passed (bd948cc), closes #1613

Features

add: Add examples to --help output (#1612) (2ab62c1), closes #1608
cli: Configure commands in root package, all other bits in cli package (7200fd0), closes #1584
npm-publish: Resolve target package to aid chaining (928a707)
npm-publish: Store entire tarball metadata object on Package instances (063d743)
publish: Support prepack/postpack lifecycle in root manifest (9df88a4)
run-lifecycle: Resolve target package to aid chaining (8e0aa96)

3.1.4 (2018-08-21)
Bug Fixes

symlink-binary: Avoid instanceof across nested module boundaries (26d1b72), closes #1525

3.1.3 (2018-08-21)
Bug Fixes

add: Avoid passing bad scope to pacote (ad649bf), closes #1592
global-options: Move env defaults to command superclass (6d8e405), closes #1449

3.1.2 (2018-08-20)
Bug Fixes

Setup instance.filteredPackages explicitly (32357f8)
Use packageGraph.rawPackageList instead of misleading instance.filteredPackages (2e2abdc)
bootstrap: Remove redundant duplicate name check (c2405a1)
command: Remove redundant filteredPackages calculation (e0a361f)
filter-options: Move filterPackages logic into named export (e863c28)
package-graph: Throw errors when package names are not unique (387df2b)
publish: Allow composed version command to decide when to verify working tree (e61aa67)

3.1.1 (2018-08-17)
Bug Fixes

add: Compose bootstrap to avoid extra logs (3c534eb)
add: Use pacote to resolve third-party registry authentication woes (a0fbf46), closes #1572 #1539

v3.1.4
Compare Source
Bug Fixes

add: Order short flags first in help output, clarify description (8efb549)
publish: Call synthetic prepublishOnly lifecycle before packing (dda9812), closes #1169
version: Make changes to packages in batched topological order (d799fbf)
version: Skip working tree validation when --no-git-tag-version passed (bd948cc), closes #1613

Features

add: Add examples to --help output (#1612) (2ab62c1), closes #1608
cli: Configure commands in root package, all other bits in cli package (7200fd0), closes #1584
npm-publish: Resolve target package to aid chaining (928a707)
npm-publish: Store entire tarball metadata object on Package instances (063d743)
publish: Support prepack/postpack lifecycle in root manifest (9df88a4)
run-lifecycle: Resolve target package to aid chaining (8e0aa96)

3.1.4 (2018-08-21)
Bug Fixes

symlink-binary: Avoid instanceof across nested module boundaries (26d1b72), closes #1525

3.1.3 (2018-08-21)
Bug Fixes

add: Avoid passing bad scope to pacote (ad649bf), closes #1592
global-options: Move env defaults to command superclass (6d8e405), closes #1449

3.1.2 (2018-08-20)
Bug Fixes

Setup instance.filteredPackages explicitly (32357f8)
Use packageGraph.rawPackageList instead of misleading instance.filteredPackages (2e2abdc)
bootstrap: Remove redundant duplicate name check (c2405a1)
command: Remove redundant filteredPackages calculation (e0a361f)
filter-options: Move filterPackages logic into named export (e863c28)
package-graph: Throw errors when package names are not unique (387df2b)
publish: Allow composed version command to decide when to verify working tree (e61aa67)

3.1.1 (2018-08-17)
Bug Fixes

add: Compose bootstrap to avoid extra logs (3c534eb)
add: Use pacote to resolve third-party registry authentication woes (a0fbf46), closes #1572 #1539

v3.1.3
Compare Source
Bug Fixes

symlink-binary: Avoid instanceof across nested module boundaries (26d1b72), closes #1525

v3.1.2
Compare Source
Bug Fixes

add: Avoid passing bad scope to pacote (ad649bf), closes #1592
global-options: Move env defaults to command superclass (6d8e405), closes #1449

v3.1.1
Compare Source
Bug Fixes

Setup instance.filteredPackages explicitly (32357f8)
Use packageGraph.rawPackageList instead of misleading instance.filteredPackages (2e2abdc)
bootstrap: Remove redundant duplicate name check (c2405a1)
command: Remove redundant filteredPackages calculation (e0a361f)
filter-options: Move filterPackages logic into named export (e863c28)
package-graph: Throw errors when package names are not unique (387df2b)
publish: Allow composed version command to decide when to verify working tree (e61aa67)

v3.1.0
Compare Source
Bug Fixes

collect-updates: Report no changes when on a release commit (082d876), closes #1548
command: Detect composed commands more accurately (1e51b39)
command: Log lerna CLI version with less ambiguity (67494e7)
publish: Throw errors if --canary attempted on unclean tree or tagged release (5da0e42)
version: Throw errors if tree is unclean or duplicating tagged release (d8ee1cf)

Features

Create [@lerna](https://renovatebot.com/gh/lerna)/check-working-tree (98cd41f)
Create [@lerna](https://renovatebot.com/gh/lerna)/describe-ref (8c11b75)

3.0.6 (2018-08-16)
Bug Fixes

command: Silence goalpost logging when running a composed command (12b4280)
create: Use whatwg-url instead of node 8.x-dependent URL class (8701b79)
init: Consume lernaVersion from options, not instance property (89e31d2)
npm-publish: Tip-toe around logging when emitting chunk to stdout (c027246)
version: Pass --preid to selection prompt (23a30a0), closes #1214
version: Prioritize --preid over existing prerelease ID (#1568) (f2c470a)

3.0.5 (2018-08-15)
Bug Fixes

collect-updates: Remove period from committish log message (a97262c)
filter-options: Allow --private to be configured from file (21e134c)
global-options: Allow --sort to be configured from file (f4aed75)
help: Insert line break before describing boolean negations (da2f886)
options: Provide -y alias for --yes (3ea460c)
publish: Add confirmation prompt before execution (47766e5), closes #1566
publish: Get tagged packages from merge commit (#1567) (fc771d9)
version: Log skipped publish when composed (89645b7)

3.0.4 (2018-08-14)
Bug Fixes

publish: Do not ping third-party registries (42f4fdd), closes #1560
publish: Only pass --json to npm pack when npm >= 5.10.0 (71babce), closes #1558
publish: Run publish from leaf nodes again (3d348ec), closes #1560

3.0.3 (2018-08-11)
Bug Fixes

publish: Restore deprecated --skip-npm functionality (cb47cb6), closes #1553

3.0.2 (2018-08-11)
Bug Fixes

conventional-commits: Pass --tag-version-prefix to changelog utilities (8ed7d83)
conventional-commits: Provide fallback bump when releaseType is missing (e330f6f), closes #1551
exec: Allow config files to override defaults (2335149)
publish: Add default for --tag-version-prefix (f159442)
publish: Allow disabling of registry and package verification (0bfdff5), closes #1552
run: Allow config files to override defaults (f15b6fb)
version: Allow config files to override defaults (bb1cfb5)
version: Positional bump supersedes --conventional-commits when choosing version (a74c866)

3.0.1 (2018-08-10)
Bug Fixes

publish: Allow unpublished packages to pass access verification (3a7348c)

v3.0.6
Compare Source
Bug Fixes

collect-updates: Report no changes when on a release commit (082d876), closes #1548
command: Detect composed commands more accurately (1e51b39)
command: Log lerna CLI version with less ambiguity (67494e7)
publish: Throw errors if --canary attempted on unclean tree or tagged release (5da0e42)
version: Throw errors if tree is unclean or duplicating tagged release (d8ee1cf)

Features

Create [@lerna](https://renovatebot.com/gh/lerna)/check-working-tree (98cd41f)
Create [@lerna](https://renovatebot.com/gh/lerna)/describe-ref (8c11b75)

3.0.6 (2018-08-16)
Bug Fixes

command: Silence goalpost logging when running a composed command (12b4280)
create: Use whatwg-url instead of node 8.x-dependent URL class (8701b79)
init: Consume lernaVersion from options, not instance property (89e31d2)
npm-publish: Tip-toe around logging when emitting chunk to stdout (c027246)
version: Pass --preid to selection prompt (23a30a0), closes #1214
version: Prioritize --preid over existing prerelease ID (#1568) (f2c470a)

3.0.5 (2018-08-15)
Bug Fixes

collect-updates: Remove period from committish log message (a97262c)
filter-options: Allow --private to be configured from file (21e134c)
global-options: Allow --sort to be configured from file (f4aed75)
help: Insert line break before describing boolean negations (da2f886)
options: Provide -y alias for --yes (3ea460c)
publish: Add confirmation prompt before execution (47766e5), closes #1566
publish: Get tagged packages from merge commit (#1567) (fc771d9)
version: Log skipped publish when composed (89645b7)

3.0.4 (2018-08-14)
Bug Fixes

publish: Do not ping third-party registries (42f4fdd), closes #1560
publish: Only pass --json to npm pack when npm >= 5.10.0 (71babce), closes #1558
publish: Run publish from leaf nodes again (3d348ec), closes #1560

3.0.3 (2018-08-11)
Bug Fixes

publish: Restore deprecated --skip-npm functionality (cb47cb6), closes #1553

3.0.2 (2018-08-11)
Bug Fixes

conventional-commits: Pass --tag-version-prefix to changelog utilities (8ed7d83)
conventional-commits: Provide fallback bump when releaseType is missing (e330f6f), closes #1551
exec: Allow config files to override defaults (2335149)
publish: Add default for --tag-version-prefix (f159442)
publish: Allow disabling of registry and package verification (0bfdff5), closes #1552
run: Allow config files to override defaults (f15b6fb)
version: Allow config files to override defaults (bb1cfb5)
version: Positional bump supersedes --conventional-commits when choosing version (a74c866)

3.0.1 (2018-08-10)
Bug Fixes

publish: Allow unpublished packages to pass access verification (3a7348c)

v3.0.5
Compare Source
Bug Fixes

command: Silence goalpost logging when running a composed command (12b4280)
create: Use whatwg-url instead of node 8.x-dependent URL class (8701b79)
init: Consume lernaVersion from options, not instance property (89e31d2)
npm-publish: Tip-toe around logging when emitting chunk to stdout (c027246)
version: Pass --preid to selection prompt (23a30a0), closes #1214
version: Prioritize --preid over existing prerelease ID (#1568) (f2c470a)

v3.0.4
Compare Source
Bug Fixes

collect-updates: Remove period from committish log message (a97262c)
filter-options: Allow --private to be configured from file (21e134c)
global-options: Allow --sort to be configured from file (f4aed75)
help: Insert line break before describing boolean negations (da2f886)
options: Provide -y alias for --yes (3ea460c)
publish: Add confirmation prompt before execution (47766e5), closes #1566
publish: Get tagged packages from merge commit (#1567) (fc771d9)
version: Log skipped publish when composed (89645b7)

v3.0.3
Compare Source
Bug Fixes

publish: Do not ping third-party registries (42f4fdd), closes #1560
publish: Only pass --json to npm pack when npm >= 5.10.0 (71babce), closes #1558
publish: Run publish from leaf nodes again (3d348ec), closes #1560

v3.0.2
Compare Source
Bug Fixes

publish: Restore deprecated --skip-npm functionality (cb47cb6), closes #1553

v3.0.1
Compare Source
Bug Fixes

conventional-commits: Pass --tag-version-prefix to changelog utilities (8ed7d83)
conventional-commits: Provide fallback bump when releaseType is missing (e330f6f), closes #1551
exec: Allow config files to override defaults (2335149)
publish: Add default for --tag-version-prefix (f159442)
publish: Allow disabling of registry and package verification (0bfdff5), closes #1552
run: Allow config files to override defaults (f15b6fb)
version: Allow config files to override defaults (bb1cfb5)
version: Positional bump supersedes --conventional-commits when choosing version (a74c866)

v3.0.0
Compare Source
Bug Fixes

add: Always use POSIX paths when computing relative file: specifiers (ffe354f)
add: Support explicit & implicit relative file: specifiers (41f231f)
create: Use filename without scope when generating imports from test file (acfd48b)
publish: Improve npm pack experience (627cfc2)

Features

changed: Support list output options (6ecdd83)
list: Extract @lerna/listable utility (bf56018)
list: Improve scriptability with several new options (2e204af)
npm-publish: Add npmPack export (088ea54)
package: Add tarball property (be453cd)
publish: Run npm pack before npm publish (8d80b2c)
publish: Validate npm registry and package access prerequisites (ebc8ba6), closes #55 #1045 #1347
Add @lerna/log-packed module, extracted from npm (9c767ac)
Split lerna version from of lerna publish (#1522) (8b97394), closes #277 #936 #956 #961 #1056 #1118 #1385 #1483 #1494

BREAKING CHANGES

changed: The package names emitted to stdout are no longer prefixed by a "- ", and private packages are no longer displayed by default.

list: The default output of lerna ls no longer shows version strings or private packages.

The new alias lerna la resembles the old output, with the addition of relative path to the package

The new alias lerna ll is a shortcut for the new --long option

A new --parseable option has been added to aid magical piping incantations

--preid now defaults to "alpha" during prereleases:

The previous default for this option was undefined, which led to an awkward "1.0.1-0" result when passed to semver.inc().
The new default "alpha" yields a much more useful "1.0.1-alpha.0" result. Any previous prerelease ID will be preserved, just as it was before.

--no-verify is no longer passed to git commit by default, but controlled by the new --commit-hooks option:
The previous behavior was too overzealous, and the new option operates exactly like the corresponding npm version option of the same name.
As long as your pre-commit hooks are properly scoped to ignore changes in package.json files, this change should not affect you. If that is not the case, you may pass --no-commit-hooks to restore the previous behavior.

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

This PR has been generated by Renovate Bot.

PR has been edited
:construction_worker: This PR has received other commits, so Renovate will stop updating it to avoid conflicts or other problems. If you wish to abandon your changes and have Renovate start over you may click the "rebase" checkbox in the PR body/description.


Use double quotes in .stylelintrc

This rule should also be backported in v4-dev. Shall we do a new PR or cherry-pick https://github.com/twbs/bootstrap/pull/29612 and this PR, @XhmikosR?

We just need to cherry pick the quotes change if it applies on the current v4-dev. Newer stylelint-config-twbs-bootstrap versions don't work with Node.js 6.

AFAICT there's nothing to backport in v4, so we are good.

Newer stylelint-config-twbs-bootstrap versions don't work with Node.js 6.

Ow yeah, I forgot. looks good indeed then


Occasional segmentation fault when non-blocking function is interrupted by end of script

This only happens if a script ends before playback is finished.
This isn't a real problem since you would use a blocking call or at least sd.wait() in a Python script.
But crashing the interpreter isn't really nice ...
This is an example script to reproduce the error:
import sounddevice as sd
import numpy as np

sd.play(np.zeros(100000))

Note that the crash doesn't happen every time, only occasionally.

I was trying to look at this but I quickly realized that sounddevice isn't actually a compiled extension which makes it more difficult to debug C issues like this. Is it much more troublesome to make it into a compiled extension?

I'm not sure if I understand ...
It would be reasonably simple to switch from CFFI's ABI mode to API mode, see http://cffi.readthedocs.io/en/latest/cdef.html.
This would change hardly anything in the implementation, most notably, the callback would still be implemented in Python.
If by "compiled extension" you mean manually writing C code using the Python C API, this would be an insane amount of work. Also, PyAudio already does that: https://people.csail.mit.edu/hubert/pyaudio/.
In this case, the callback would still be written in Python.
If you mean to keep CFFI (in API mode) but implement the callback in C, that's what I'm doing in https://github.com/mgeier/python-rtmixer/.
Finally, if you are talking about using the Python C API and implementing the callback in C, that's what pyo does: https://github.com/belangeo/pyo.

Sorry about the vagueness, I actually just meant using CFFI in API mode. All this would do is produce some debuggable C code.

OK. It should be straightforward, but I haven't actually tried it.
Do you want me to make a branch for API mode?

Nah, I wouldn't put this at a high priority. I will experiment with it in
the near future. I've done it for a previous project and I agree it
should be straightforward.
On Mon, Feb 6, 2017 at 11:43 AM, Matthias Geier<EMAIL_ADDRESS>wrote:

OK. It should be straightforward, but I haven't actually tried it.
Do you want me to make a branch for API mode?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/spatialaudio/python-sounddevice/issues/1#issuecomment-277756712,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAaVHGL9uARHrapPAYB6tAxeWTHk_hmlks5rZ1vPgaJpZM4FIMt0
.

Fixed by #75.


Fix failing linemappings tests

Need to use a consistent newline, since these fail on xplat.

/cc @pranavkm

6c55754823f7180cf0c2738b0d64cbcdf518ec7d


Scroll position doesn't reset after page transitions

Issue
The scroll position doesn't reset after page transitions.
Expectation
After scrolling down on a page and visiting another page, the user begins the new page from the top.
Reproducible Example
Visit the reference page for the DCGAN model and scroll down to the bottom of the page. Next, visit the reference page for another model, such as SketchRNN by selecting it from the left-hand sidebar. Notice that the SketchRNN route is loaded, but you are at the bottom of the page, requiring you to scroll back to the top of the page to see the initial content.

Closing this issue on this repository, as this actually has to do with the Docsify setup. I'll open this issue on ml5-library where that configuration lives.

Hi @bomanimc ! Thanks! I will follow up accordingly. This is great feedback!


Remove nightly tests

Codecov Report

Merging #3 (1649a1e) into master (c4f86ba) will increase coverage by 1.18%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master       #3      +/-   ##
==========================================
+ Coverage   80.39%   81.57%   +1.18%
==========================================
  Files           1        1
  Lines         102      114      +12
==========================================
+ Hits           82       93      +11
- Misses         20       21       +1

Impacted Files
Coverage Δ

src/lib.rs
81.57% <100.00%> (+1.18%)
:arrow_up:

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 c4f86ba...74e30e7. Read the comment docs.


[Enchancement] Plain output format

Hi!
First, thank you for such awesome tools.
I've just started using the gospider and like the way it crawls and lists down the output. I however, miss a plain formatted output to pass the urls to other tools. Is there a possibility to use a -plain format to get the output of just the urls without the preceding information like the source of the url and http code?
One challenge I notice is the way to output information from linkfinder.
Thanks

| grep -e "code-200" | awk '{print $5}'


Please rename directory adapters to adapter

Sorry for this nit: almost all directories in this repo use singular name except adapters. It would be nicer to use singular for all directories. :)

I think this will be handled as part of the reshuffle discussed in #86. Let's continue that discussion there, perhaps?

Tracked by #86


[SPARK-47151][PYTHON][PS][BUILD] Upgrade to pandas 2.2.1

What changes were proposed in this pull request?
Upgrade pandas from 2.2.0 to 2.2.1
Why are the changes needed?
Release notes 2.2.1
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA
Was this patch authored or co-authored using generative AI tooling?
No.

Merged to master for Apache Spark 4.0.0.

Thank you, @bjornjorgensen .


Add filter for deprecated and foregone todo problems.

Add filter for unneeded problems.
Update test fixtures to include deprecated and foregone arrays.
Update test to check that deprecated and foregone problems are not included in todo.

Closes https://github.com/exercism/todo/issues/171.

Sweet, thanks!


Add workflow to automate gpuCI updates

Mirrors the workflow added to Dask; should make RAPIDS release cycles a little easier to manage gpuCI-wise

Codecov Report

Merging #327 (c812ed6) into main (ec328c6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #327   +/-   ##
=======================================
  Coverage   95.80%   95.80%
=======================================
  Files          65       65
  Lines        2834     2834
  Branches      426      426
=======================================
  Hits         2715     2715
  Misses         74       74
  Partials       45       45

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 ec328c6...c812ed6. Read the comment docs.


Update positions of old sparkles instead of creating new ones.

Changed the animation iteration to infinite and update on animationiteration.
Trying to fix #5.

Very cool @yuanchuan. This seems to work perfectly! Thank you! 👏
Let's hope it fixes #5.


Question regarding the mixture in MDN (pi)

I wonder how the mixture is done in MDN at test time (so when we want to dream).
http://blog.otoro.net/2015/11/24/mixture-density-networks-with-tensorflow/ : Here we have an example of a MDN with k Gaussians of parameters (mu_k, sigma_k) that are 1-dimensional. E.g mu_k and sigma_k are scalars. Since we can only mix these K Gaussians by taking one of the K possible pair of parameters (mu_k, sigma_k), the shape of Pi is Pi = (Pi_1, ..., Pi_k) with each Pi_j being the (scalar) probability of selecting the j-th Gaussian.
In the case of the MDN in World Models, the k Gaussians of parameters (mu_k, sigma_k) are n-dimensional (with the same dimension as z, the encoded feature coming from the VAE). Hence given one sample there a choice for mixture, you can:

have the same shape of Pi as before, with Pi = (Pi_1, ..., Pi_k) with each Pi_j being the (scalar) probability of selecting the j-th Gaussian.
Pi is a matrix of size (k, n): Pi = (Pi_1, ..., Pi_n) where n is the dimension of z (encoding from the VAE). For each j, Pi_j = (Pi_j_1, ..., Pi_j_k) where Pi_j_l is the probability of selecting the l-th component of mu_j and sigma_j. So, for each j in 1..n, one can sample according the distribution P_j (this is where you can modify this distribution with temperature to have a more or less stochastic world model if I understand right) to select the j-th component of any of the k gaussians. The result is a new mu and new sigma, both n-dimensional mix of the components of mu_k and sigma_k. Finally, you can sample according to this mixture to obtain the next z.

For 1), there are k Gaussians to choose from, while for 2) there are actually n*k Gaussians to choose from.
Which one is right and why ?
In available implementations, I see that people seem to use 2) (since the shape of Pi is (NB_GAUSSIANS, SIZE_FEATURE_VAE)).
[I also asked my question in the comments on Reddit : https://www.reddit.com/r/MachineLearning/comments/8poc3z/r_blog_post_on_world_models_for_sonic/ . If I get an answer there, I will close the issue and reference the answer there.]

Hi @Caselles
During inference (testing), I first sample 1 of the k possible mixtures (from a categorical distribution defined using the πᵢ's).
After picking one of the mixtures, I then sample a Gaussian z vector using the μ and σ vectors for that mixture.
It might not be the 100% correct thing to do, but it's fairly efficient to implement for practical purposes, and works well. I have also done the same thing in sketch-rnn demo.

I understand, and this raises my concern. Let me explain:
Let NB_GAUSSIAN be the number of Gaussians in the MDN. Let Z_SIZE be the dimension of the latent vector produced by the VAE.
This means that the shape of π, for your implementation is (NB_GAUSSIAN). π is a distribution from which you can sample an integer ranging from 1 to NB_GAUSSIAN. Once you obtain this integer, let's call it j, you sample from the j-th gaussian to obtain the output.
In various implementations, such as this one in PyTorch and this one in Keras, the shape of π is (NB_GAUSSIAN, Z_SIZE). It is composed of a list of Z_SIZE distributions over [1, .. , NB_GAUSSIAN] from which you can sample a component from the NB_GAUSSIAN gaussians.
Here is a simple example :

What are your thoughts on that ? It seems weird to me that there is no fixed answer for this.

I'm not familiar with the implementation details of the Keras and PyTorch versions. Are you saying they may have implemented the sampling method incorrectly?

Hi @Caselles
Thanks for the detailed explanation, I have reread your original message, and your second clear explanation and I understand your question now. Apologies, and please ignore the previous response as that does not properly address your question!
I have followed the approach in (2), and modelled each individual dimension of Z (say of 64 dim) as a mixture of 5 Gaussians in the MDN-RNN. I think this is a reasonable choice if our modelling assumption is that each dimension of Z is independent.
Please refer to the code for DoomRNN, particularly for get_lossfunc, to see that in the loss calculation we optimize for the likelihood of y (which is the pre-processed data given by the VAE),
https://github.com/hardmaru/WorldModelsExperiments/blob/master/doomrnn/doomrnn.py#L352
I would love to hear your thoughts as to whether (1) is more preferable to (2). In my view (2) might be more expressive. If you want to experiment with (1), then the training of the MDN-RNN, and the loss functions, will need to be modified to accompany for that.
Thanks!

Thank you for your clear answer !
I have no prior preference on method (1) or (2). I was just wondering about it because it seems that in the original paper by Bishop about Mixture Density Networks (PDF link), he only considers the case where the predicted output is scalar. Here the output is a vector so we are left with a choice to model each component as a mixture of k gaussians (method (1)) or to model the whole vector a k multivariate gaussians (method (2)).
Indeed, it seems that method (2) is intuitively more expressive. I wonder if method (1) works. It could be that (1) works just as good and is simpler ?
I will be experimenting with (1). Thanks for pointing out that the training and the loss should be modified. I'll let you know if I have any interesting results.
Thanks again for your work and especially for answering questions here, on Reddit, publishing the code. The effort is much appreciated !


Possibly a bug but more likely i'm doing something wrong and it's not working.

Describe the bug
I'm not sure if this is a bug or something I'm doing wrong. I have a Plex folder called Movies-30-Day and I would like it to clear out any Movies after they have been added to Plex after 60 days (just to give family a little extra time to watch rather than 30 days). But it doesn't seem to be doing anything.
To Reproduce
Steps to reproduce the behavior:
Please see the screenshots for the rule I have setup to achieve the above.
Expected behavior
Delete movies from Radarr and Plex after 60 days they have been added to Plex.
Screenshots

Device (please complete the following information):

OS: Synology Docker Containers
Version 2.0.3 Stable

Additional context
Nothing further to add.

Hey,
It won't add anything because your rule checks if  'Plex add date' is later than 'Plex add date'. Which will never result in true, since it's exactly the same date.
Want you want is this:

This will find all items that were added at least 60 days ago.
'The take action after days' configuration value specifies how many days an item stays in the 'Movies 30-Day' collection before the actual removal happens.
So when an item matches the rule, Maintainerr will add the item to the collection. This collection can be shown on the home page to notify your users. Once the item has lived in the collection for longer than the amount of days specified in 'take action after days', it'll remove the item.

ahh this has created another issue now.
I subscribe to lists and radarr has automatically re-downloaded some of the ones removed.
Is it possible to add the removed ones to a radarr blacklist so they don't re-download?
Thanks for the help.

There’s a checkmark in the rule config ‘Add list exclusions’, that does what you want.


[Question] Enable response_type extension

As defined per (RFC6749)[https://tools.ietf.org/html/rfc6749#section-8.4], the response_type should be extensible.
I did not see a way to extend this part, as the Constants.SupportedResponseType is internal.
The goal is to support the none  value and/or other values (like a federation value)

We don't support extending the response types.
If you think that feature is needed please open a feature request and explain the scenarios in detail.


Update group-dance.html

Added Link to main Apratim Website which earlier was not redirecting to main website if we clicked on Apratim2k19.
'../'' was missing in line 32.

Good Work


ex_doc dependency for Erlang users

Hi,
I've been using eredis_cluster for a while now (here). Thanks for making it available!
I noticed that you added ex_doc and removed the , only :dev:
https://github.com/adrienmo/eredis_cluster/commit/4192b3c12c57d60253e1a474853f36e8babb0166#diff-6023be6004fce4718dad3dafb576d258
Since I'm having trouble making this compile with version 0.5.12 on Erlang (using OTP 21 and rebar3 3.9.0), would you consider moving the ex_doc dependency back to a separate profile?
I tried using rebar_mix, got some errors that I am trying to work around but I would still appreciate having one less dependency that is not strictly required :)
Thanks.

Another question based on this, why at all are there mix and rebar files around?
Please choose one over the other (as this is erlang, perhaps choose rebar) and stick to that.
You can push/publish to hex using rebar as well.


Added  window_fullscreen? api

example usage                 if LibRaylib.window_fullscreen?

Thanks I guess I missed this one.


Custom hook: All schools

Using a json or an api endpoint,  return a list of all institutions using from a custom hook
The hook should return the following:

[ ]  The school name. E.g Obafemi Awolowo University
[ ]  The school code E.g OAU
[ ]  The school logo

Here is an api you can use:
https://github.com/favourdev1/Nigerian-University-Api

@stephengade , assign this to me

Any update on this @Akeemkabiru

@stephengade provide the API endpoint please


Expose Instructions

Myself (and probably many others) would like to use the classloader and instruction decoder to do analysis on class files. Any plans to expose the different instruction structs or at least the name?

Thanks for you advice but I am afraid I have no time to do this. This project was coded a half year ago when I quit my job and get some free time at home. After that  the project is almost stopped.

No worries, thanks for the update. I forked it and exposed some stuff myself for classfile parsing. Thanks again for the code.


cannot create roles

Creation Failed
Aha! Link: https://t-mobile1t-mobile.aha.io/features/PM-304

issue fixed


Connect to Electrum (Bitcoin) - node address and port are not display

Bug is not reproduced for now


[Code Addition Request]: Histogram Maximal Rectangle DP Hard

Have you completed your first issue?

[X] I have completed my first issue

Guidelines

[X] I have read the guidelines
[X] I have the link to my latest merged PR

Latest Merged PR Link
#1040
Project Description
Add maximal rectangle in histogram
Full Name
Anneshu Nag
Participant Role
GSSOC

@NK-Works I am closing this issue, raise another issue add add atleast 3-4 slogs not just 1.

@UTSAVS26 got it


Fix loading for nested through associations

Patch to address #55 based on PR #58 by @gbxl

Ah! Looks like you figured what I was missing! Can't wait to see this merged :). Thanks for you work @rschef !

Thanks!


Update version: Bilibili.Livehime version <IP_ADDRESS>95

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/110032&drop=dogfoodAlpha

Automatic Validation ended with:

URI: https://live.bilibili.com, Validation result: Passed
URI: https://link.bilibili.com/p/help, Validation result: Failed, Http status code: NotFound
URI: https://www.bilibili.com/blackboard/live/mobilelink-provacypolicy.html, Validation result: Passed
URI: https://live.bilibili.com/liveHime, Validation result: Passed
URI: https://www.bilibili.com/blackboard/live/activity-dLUnpNZEM1.html, Validation result: Passed
URI: https://dl.hdslb.com/bili/bililive/win/Livehime-Win-beta-<IP_ADDRESS>95-x64.exe, Validation result: Passed

The 2nd link appears to be the issue.


Improve Console Section

I reworked and extended some parts of Section 6.1
Some minor fixes in related sections.

Thanks!


AltC Maybe doesn’t terminate for infinitely productive search spaces

run (runNonDet (asum (map pure [1..]))) :: Maybe Int

won’t terminate despite the fact that it should be able to complete immediately on the first result.
This is probably actually “works as expected,” because of the dual semantics of Alternative—there’s no way for AltC to know that <|> for Maybe means “leftmost wins” whereas for [] it means “all win.”
Therefore, this probably warrants the inclusion of a OnceC which returns in Maybe and knows about the <|>-as-choice-not-union semantics.

This could also be phrased as “AltC is best-case linear in the size of the search space”


Initial jsonschema validator

This is a work in progress. The CIDR regex is known to be wrong, for example.

blocked by schema issue

Blocking issue is https://github.com/samsung-cnct/k2/issues/258

will this cover cluster name validation? wondering if we can not bother with https://github.com/samsung-cnct/k2cli/issues/33

I am in the process of fixing up this PR now so that it will merge cleanly. Other than correcting the new k8s label support, I do not expect any changes.

Validation is failing due to RelativeRef lookup failures [1]. I expected this to be fixed and am looking into the cause now.
[1]

TASK [kraken.config : Validate k2 configuration under schema] ******************
/home/jenkins/workspace/K2_PR-404-JUOHVXPUF4EKW3NMSNFAX35JGVLHPUVW4ZNWD4VJD2LEHFMM3EFQ # exit
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: jsonschema.exceptions.RefResolutionError: No JSON object could be decoded
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File "/tmp/ansible_x4060m/ansible_module_jsonschema.py", line 185, in \n    main()\n  File "/tmp/ansible_x4060m/ansible_module_jsonschema.py", line 176, in main\n    result = validate_document(config, schema, module.params['subschema_dir'])\n  File "/tmp/ansible_x4060m/ansible_module_jsonschema.py", line 131, in validate_document\n    validator.validate(config)\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 122, in validate\n    for error in self.iter_errors(*args, **kwargs):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 98, in iter_errors\n    for error in errors:\n  File "/usr/lib/python2.7/site-packages/jsonschema/_validators.py", line 291, in properties_draft4\n    schema_path=property,\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 114, in descend\n    for error in self.iter_errors(instance, schema):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 98, in iter_errors\n    for error in errors:\n  File "/usr/lib/python2.7/site-packages/jsonschema/_validators.py", line 203, in ref\n    for error in validator.descend(instance, resolved):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 114, in descend\n    for error in self.iter_errors(instance, schema):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 98, in iter_errors\n    for error in errors:\n  File "/usr/lib/python2.7/site-packages/jsonschema/_validators.py", line 291, in properties_draft4\n    schema_path=property,\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 114, in descend\n    for error in self.iter_errors(instance, schema):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 98, in iter_errors\n    for error in errors:\n  File "/usr/lib/python2.7/site-packages/jsonschema/_validators.py", line 42, in items\n    for error in validator.descend(item, items, path=index):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 114, in descend\n    for error in self.iter_errors(instance, schema):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 98, in iter_errors\n    for error in errors:\n  File "/usr/lib/python2.7/site-packages/jsonschema/_validators.py", line 203, in ref\n    for error in validator.descend(instance, resolved):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 114, in descend\n    for error in self.iter_errors(instance, schema):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 98, in iter_errors\n    for error in errors:\n  File "/usr/lib/python2.7/site-packages/jsonschema/_validators.py", line 291, in properties_draft4\n    schema_path=property,\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 114, in descend\n    for error in self.iter_errors(instance, schema):\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 98, in iter_errors\n    for error in errors:\n  File "/usr/lib/python2.7/site-packages/jsonschema/_validators.py", line 199, in ref\n    scope, resolved = validator.resolver.resolve(ref)\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 336, in resolve\n    return url, self._remote_cache(url)\n  File "/usr/lib/python2.7/site-packages/functools32/functools32.py", line 400, in wrapper\n    result = user_function(*args, **kwds)\n  File "/usr/lib/python2.7/site-packages/jsonschema/validators.py", line 346, in resolve_from_url\n    raise RefResolutionError(exc)\njsonschema.exceptions.RefResolutionError: No JSON object could be decoded\n", "module_stdout": "SUBSCHEMA_DIR ../schemas/config/v1/\n", "msg": "MODULE FAILURE", "rc": 0}

Closing in favor of


fix(inspector): subscribe to latent covalues instead of loading them immediately

added a new function subscribeToCoValue() to examples/inspector/src/viewer/use-resolve-covalue.ts
useResolvedCoValue() and useResolvedCoValues() now use subscribeToCoValue() instead of resolveCoValue()
basically using node.subscribe() over node.load()

Looks good to me overall, please can you make it use 4 spaces so the diff is cleaner?

More general comment is that load should behave correctly - but this is a bigger problem we need to address in cojson over the longer term. The nice benefit of subscribing is that we have a live view of the CoValues I guess?

The nice benefit of subscribing is that we have a live view of the CoValues I guess?

Yes, at least we get this benefit for now.

More general comment is that load should behave correctly - but this is a bigger problem we need to address in cojson over the longer term.

Opening a new issue to track this.


Integrate LLVM at 24c2c74bd29d4d550974f8249cbf8fdf1d033bfd

This integrates LLVM as of 24c2c74bd29d4d550974f8249cbf8fdf1d033bfd,
but with two new reverts applied:

8e7633e241e7f842bac99b68eee2830fd879bb7f
Revert "[MLIR][Linalg] Re-land linalg.matmul move to ODS. +
Remove/update failing obsolete OpDSL tests. (#115319)"
This reverts commit 3ad0148020ca91cc288bffd8ad36e25f7555a3bb.

3ef687c9c1d8949a102e02a5b2fb5cae7041867b
Revert "[MLIR][Linalg] Fix unclosed code block which broke generated
docs - NFC (#115763)"
This reverts commit c02b8a01b7caf2e4ffe17a123f1bcf59192e4b39.

This also carries the following revert, which previously had the commit
hash 2ab1021dcf1fd0443e6249ac848f6a0413d939bd:

b86bf2a6746db5f8df0441a847ba80aa7070922b
Revert "[mlir][Vector] Support 0-d vectors natively in
TransferOpReduceRank (#112907)"
This reverts commit 1004865f1ca41a9581da8747f34b29862d3ebc3d.

The following commits previously applied on top of LLVM have been
dropped as they are no longer needed:

889525fa99b251dc962edb516e0108088ba7e44d
[mlir][Tensor] Add discardable attrs back in cast(pack) folder

a07e80ce836faaddf99c474e1646d2b18afa5f7b
[mlir] Fix condition for fusability in consumer fusion API

Thanks to @Groverkss for preparing the submodule part of this btw: https://github.com/iree-org/llvm-project/commits/sm-iree-integrate-llvm-202411120alt


API create project with file

I want to create a new project by using the API. In the documentation I could see how to do that with a path to a file to scan. I want to upload a file which should be scanned. I can do it in the UI by using drag and drop. What do I have to do to enable that by the API?
upload_file here is not working
data='{
"name": "core api",
"upload_file": "/mnt/d/git/wsl/projects/murphy.zip",
"pipeline": "scan_codebase",
"execute_now": false
}'
curl -v --header "Authorization: Basic aabbcc" -X POST "http://mydomain.com/api/projects/" -H "Content-Type: application/json" -d "$data"

Hi @RaphaelHerd , upload_file is a special type of field, it cannot be provided in the data but need to be submitted as a file.
You can use the Form emulation in cURL with the following syntax:
api_url="http://localhost/api/projects/""
upload_file="/path/to/the/archive.zip"

curl -F "name=project_name" \
     -F "pipeline=scan_package" \
     -F "execute_now=True" \
     -F "upload_file=@$upload_file" \
     "$api_url"

Let me know if that works for you and I'll add this to the documentation.

@tdruez thx for the quick response. It works. You can close the issue. But before, you maybe can help me quickly with one other question:
Is it also possible to use scancode CLI for automation purposes (https://scancodeio.readthedocs.io/en/latest/command-line-interface.html)? If so, can you tell me if and how I can build scanpipe individually or simply use it as pip package? I saw that it is available if I build the entire solution in compose but is there an easy way to only build the scanpipe CLI?
Thanks in advance

@RaphaelHerd thanks for reporting, I've added the details about upload_file in the documentation https://scancodeio.readthedocs.io/en/latest/rest-api.html#create-a-project

simply use it as pip package?

ScanCode.io is not a library but a server.
It requires a database, tasks worker, cache backend, and a webserver to work properly.
The "Local development installation" is the lightest setup you can have at the moment.
If you only want to run a scan from the command line, you can use the ScanCode-toolkit https://github.com/nexB/scancode-toolkit as a library.


dominanceComparator function

I am not sure whether the dominanceComparator function will become less efficient or not, I wrote it in the following way.
function dominanceComparator(x::Array{T}, y::Array{T})::Int where {T <: Number}
    @assert length(x) == length(y) "The arrays have a different length"

    x==y && return 0

    all(t->(t[1]≤t[2]), zip(x, y)) && return -1
    all(t->(t[1]≤t[2]), zip(y, x)) && return  1
    return 0
end

It is a very concise, clear and elegant solution. I will adopt it.


Task Builder

Allow tasks to be chained together.
Currently to have an sync run after a sync we must do
async {
   // code
    sync {

    }
}

We can implement a chain builder such as
    async {

    } thenSync {

    }

    asyncDelayed(20) {

    } thenSync {

    }

    asyncRepeat(20) {

    } thenSync {
        // Runs once above is cancelled
    }```

Reason to implement this is because async and sync blocks can cause some ugly indentation

Implement in dev branch. (However i recommend using Skedule to avoid callback hell)


Publish nightly builds

Closes https://github.com/adobe/react-spectrum/issues/723
I've set the time to 09:00 UTC = 02:00 PDT

The current .npmrc files (.npmrc and .circle/.npmrc) contain some internal registries, is that still needed? Not sure how it would behave at the moment
Might want to hold off until the double-build situation is fixed in Parcel (https://github.com/parcel-bundler/parcel/pull/4887)
With Parcel, we have the problem that, according to semver, and 2.0.0-nightly.352 matches<EMAIL_ADDRESS>
📝 Test Instructions:
Can be tested by running a Verdaccio registry locally with this config (verdaccio -c file.yml)
storage: /Users/niklas/.local/share/verdaccio/storage
plugins: ./plugins

web:
  title: Verdaccio

auth:
  htpasswd:
    file: ./htpasswd

uplinks:
  npmjs:
    url: https://registry.npmjs.org/

packages:
  '@adobe/react-spectrum':
    access: $all
    publish: $all
    unpublish: $all

  '@react-spectrum/*':
    access: $all
    publish: $all
    unpublish: $all

  '@react-aria/*':
    access: $all
    publish: $all
    unpublish: $all

  '@react-stately/*':
    access: $all
    publish: $all
    unpublish: $all

  '@react-types/*':
    access: $all
    publish: $all
    unpublish: $all

  '@spectrum-icons/*':
    access: $all
    publish: $all
    unpublish: $all

  '@*/*':
    access: $all
    publish: $authenticated
    unpublish: $authenticated
    proxy: npmjs

  '**':
    access: $all
    publish: $authenticated
    unpublish: $authenticated
    proxy: npmjs

server:
  keepAliveTimeout: 60

logs:
  - { type: stdout, format: pretty, level: http }

and
diff --git package.json package.json
index ebd9898b..8402b9fd 100644
--- package.json
+++ package.json
@@ -29,7 +29,7 @@
     "start:docs": "PARCEL_WORKER_BACKEND=process parcel 'packages/@react-{spectrum,aria,stately}/*/docs/*.mdx' 'packages/dev/docs/pages/**/*.mdx'",
     "build:docs": "PARCEL_WORKER_BACKEND=process parcel build 'packages/@react-{spectrum,aria,stately}/*/docs/*.mdx' 'packages/dev/docs/pages/**/*.mdx' --no-scope-hoist",
     "publish": "lerna publish from-package --yes",
-    "publish:nightly": "lerna publish -y --canary --preid nightly --dist-tag=nightly --exact --force-publish=* --no-push"
+    "publish:nightly": "lerna publish -y --canary --preid nightly --dist-tag=nightly --exact --force-publish=* --no-push --registry http://localhost:4873/"
   },
   "workspaces": [
     "packages/*/*"

After running make publish-nightly, create a new project and installing/using the packages after running npm set registry http://localhost:4873/.
Verdaccio also serves a browser UI at http://localhost:4873/

Would this change also publish private packages in nightlies?

Would this change also publish private packages in nightlies?

No

Tried to upgrade parcel to the latest nightly again and failed miserably. 😆
It builds but I get "Uncaught Error: Cannot find module '1t8mc'" at runtime. Seems to be related to react fast refresh. Didn't have time to look into it more...


arch/xtensa: Add special register allocation generator

Zephyr likes to use the various Xtensa scratch registers for its own purposes in several places.  Unfortunately, owing to the configurability of the architecture, we have to use different registers for different platforms.  This has been done so far with a collection of different tricks, some... less elegant than others.
Put it all in one place.  This is a python script that emites a "zsr.h" header with register assignments for all the existing users.
[This particular PR is mostly a wash in terms of complexity, removing some hacks and adding an equivalent amount of python and cmake.  But I have plans for this: a similar trick could be played to integrate the long-dormant second-level interrupt handler generator (or better: a rewritten replacement) into the build, so we don't have to have a copy of the output for every platform.  Similar tricks could be played in the link to remove all the boilerplate around the vector table sections (those offsets are all in core-isa.h).  Lots of future here, I promise.]

(Tried to pick a representative set of reviewers from across the zephyr/xtensa community.   Please add anyone I missed.)

@andyross
I see some code in the PR that is not dealt with, such as the issue I mentioned.
https://github.com/zephyrproject-rtos/zephyr/issues/40974

@hongshui3000 indeed, this is is just cleanup (though it does get the EPC/EPS usage off of the debug interrupt level, which I know was one of your concerns).  I know you have an app architecture with non-Zephyr interrupt handling mixed with Zephyr interrupts.  It's not that we refuse to support that, you just have to realize that it's "unsupported" architecturally and that none of us are likely to fix it for you.  Please consider addressing the issues in an upstreamable way and submitting the fixes yourself.

Ok, I see

@hongshui3000 indeed, this is is just cleanup (though it does get the EPC/EPS usage off of the debug interrupt level, which I know was one of your concerns). I know you have an app architecture with non-Zephyr interrupt handling mixed with Zephyr interrupts. It's not that we refuse to support that, you just have to realize that it's "unsupported" architecturally and that none of us are likely to fix it for you. Please consider addressing the issues in an upstreamable way and submitting the fixes yourself.

Ok, I see

Ping.  Would be good to get this merged.


Azure authentication with Proxy should not require Windows credentials to be specified

Connection Azure portal or Synapse using Azure Data Studio using Proxy, Customer has to specify username and password in the studio which can be security threat.
Customer requested that they could use the Username password as part of the string while connecting using proxy as temporary solution.
Hence can we consider this as the feature enhancement where without using hardcoded username and password connect using proxy to Azure Portal or Synapse through ADS has helped us to fix the issue.

"http.proxy": http://nbkxxxxx@corp.contso.com:xxxxxxxxxx@proxy.contoso.com:8080,
"https.proxy": http://nbkxxxx@corp.contso.com:xxxxxxxxxxxxxxx@proxy.contoso.com:8080,

Related issue in vscode: https://github.com/microsoft/vscode/issues/167852


strange warnings from trace.simp_lemmas

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Checked that your issue isn't already filed.

Specifically, check out the wishlist, open RFCs,
or feature requests.

Reduced the issue to a self-contained, reproducible test case.

Description
trace.simp_lemmas reports strange error messages. It is not a serious problem, but I am mentioning it in case it indicates something wrong.
Steps to Reproduce
Run this.
set_option trace.simp_lemmas true

example (x : ℕ) : x = x :=
by simp

We get the following information:
[simp_lemmas.invalid] rule derived from 'list.nil_subset' contains argument that is (a) not a Prop, (b) not an instance, and (c) not in the LHS of the rule
[simp_lemmas.invalid] LHS of rule derived from 'list.subset.refl' occurs in RHS
[simp_lemmas.invalid] rule derived from 'list.subset_cons' contains argument that is (a) not a Prop, (b) not an instance, and (c) not in the LHS of the rule
[simp_lemmas.invalid] rule derived from 'list.subset_append_left' contains argument that is (a) not a Prop, (b) not an instance, and (c) not in the LHS of the rule
[simp_lemmas.invalid] rule derived from 'list.subset_append_right' contains argument that is (a) not a Prop, (b) not an instance, and (c) not in the LHS of the rule

But e.g. the simplifier seems to be using list.nil_subset correctly:
set_option trace.simplify true

example (l : list ℕ) : list.nil ⊆ l := by simp

Reproduces how often: 100%
Versions
current lean master.

The error message comes from is_ceqv in simp_lemmas.cpp. But it does not seem to be causing problems, so I will close this.

These warnings make sense, since ⊆ is technically a simp relation over lists (i.e. it is [refl] and [trans]). The rule list.nil_subset : [] ==> l over ⊆ is invalid since l is a new variable on the RHS, and that is what the warning is saying. However, the rule list.nil_subset : [] ⊆ l ==> true over iff is still a valid simp rule, and is still being generated.

@dselsam Thanks, that is helpful.


Some external projects (wycheproof, scala) Dockefile can't be generated correctly.

Some external projects ( wycheproof) Dockefile can't be generated correctly, some contents are missing.
For example: wycheproof need bazel installed however there is no installation step when build the image by dockerfile.
https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder_Tether/73/console
Believe some information are missing in set_test_info()
A quick look shows that we need to add following test info, similar way as ant_version ant_version=$(getProperty "ant_version")
gradle_version
sbt_version
bazel_version
openssl_version

yes, thanks for raising the issue, these were identified as part of https://github.com/adoptium/aqa-tests/issues/3187
also, we should close related / dup reports for those failing tests:
https://github.com/adoptium/aqa-tests/issues/1211
https://github.com/adoptium/aqa-tests/issues/1824
https://github.com/adoptium/aqa-tests/issues/3153
As a note, we should remind everyone to check for dups before raising new issues.
https://github.com/adoptium/aqa-tests/pull/3216 is for bazel update.

i am up for it


Automatic error report

<!---   *** BEFORE SUBMITTING: PASTE CLIPBOARD HERE TO COMPLETE YOUR REPORT ***   ---!>

Closing because this is empty. Please update to our latest version (3.3.0), which has better report facilities.


DBZ-5530 Add support for predicates in debezium embedded engine.

@jpechane Added documentation.

@jeremy-l-ford Applied, thanks!


update fsspec

Is there a reason to limit fsspec to a single version? This is currently keeping us from using img2dataset as a dependency due to dependency conflicts, and requires us to copy in part of the code instead.

The version structure of fsspec (it uses year.month.day and not major.minor.patch) that is not following semver prevents depending on one major and letting the minor change.
That leaves these choices:

Depending on one version and being sure this one works (thanks to CI checking it)
Removing the version requirement completely, so users would get no guarantee on fsspec working well with fsspec
Keeping a minimum fsspec version, hoping new "major versions" will not be breaking
Making a random guess on what the last supported "major" should be (maybe 3 months from now)
Asking fsspec to use semver

We're currently doing 1.
I think 5 is the best solution but if they would agree it would take some time and it's not sure they'd agree to such a bit change.
Maybe 4 is an ok compromise?
Eg we switch to the current last fsspec and allow up to 2024.01.00
Would that work for you ?

Since there's no semantic meaning to the versions, I would argue that 3 is the best option. You indicate a minimum compatible version while keeping options open for the user. The user should pin their versions instead.
Ideally you catch deprecation warnings in your tests to catch breaking changes before they happen, but otherwise you can update the dependency in the release after a breaking change.

The problem with 3 is that maybe the latest version of fsspec does not work with img2dataset and was not tested to work in the CI. This is the version that will be installed by users so users will start reporting things don't work

Yes, but users can fix it on their side. With the current solution, there's no way for us to fix it, since there's a conflict with the pinned version.
Also, when releasing img2dataset, the latest version of fsspec should work. So if users pin their versions from the start, they will not run into issues.
Here's a couple of long reads which discuss the topic:
https://iscinumpy.dev/post/bound-version-constraints/
https://hynek.me/articles/semver-will-not-save-you/ (a bit shorter)
While I don't agree with abandoning SemVer, I do agree with the solution if a dependency abandons it :slightly_smiling_face:

I decided to just remove the version restriction on fsspec. That's done and released now


minMatchCharLength doesnt work

setting minMatchCharLength to greater than 1 for eg "minMatchCharLength: 3" still gives result for single character

I'm having the same problem. I get matches as soon as I type any letter.
const fuse = new Fuse(response, {       keys: ['content'],       shouldSort: true,       threshold: 0.1,       distance: 20000000,       minMatchCharLength: 3     });


Add server path to the outFiles launch config

I'm not sure if just globbing the whole of out/ might be better, but I followed what was there.

ah I think this is dumb I need to connect to the server (idiot me)!


Tower height does not update on Power Tower costs page

Equation missing to assign value of h_tower to ui_tower_height on Tower SolarPilot Capital Costs UI form.

... The tower height value in SAM is not updating. Start with the default values in SAM (create a new CSP MS power tower model) and then use the correlation in the SAM help:
Total Tower Cost = Fixed Tower Costs x e ^ ( Tower Cost Scaling Exponent x ( Tower Height - Receiver Height ÷ 2 + Heliostat Height ÷ 2 ) )
The SAM result matches the correlation output. Change just the receiver height and the SAM output agrees with the correlation. Same is true for heliostat height. Update the tower height and they disagree.

This is an issue as of the original release of SAM 2020.2.29.


Failed to restore backup from deployment slot

I tried several times to restore a backup, but got this error:

Operation name: Slots
Error code: ResourceOperationFailure
Error message: The resource operation completed with terminal provisioning state 'Failed'.
Error properties:

 {
        "statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"message\":\"Sharing violation to C:\\\\Resources\\\\directory\\\\{guid}.ControllerRole.BackupRestore\\\\{guid}\\\\fs\\\\site\\\\wwwroot\\\\path\\\\to\\\\media\\\\abc-xyz.pptx\"}]}}"
}

I resolve temporary by delete deployment slot and re-create then it work fine.

@TatChu,
Thanks for posting the question! It appears that you’re referring to the steps outlined in this document Restore an app in Azure (https://docs.microsoft.com/azure/app-service/web-sites-restore#monitor-a-restore-operation) for the process and this feedback is applicable to Azure App Service doc.
Since this channel is reserved for ‘Azure docs’ questions- For doc related feedback and content improvements, we recommend posting technical questions on the technical forum where one of our specialized engineers in the subject or the Azure community members can provide the best possible answer to your scenario or question.
Having said that, kindly review the log files to see if the issue is due to an exception at the time due to any specific files.
You may checkout the documentation 'Enable diagnostics logging for web apps in Azure App Service' for a detailed steps on finding the logs.
We will now close this issue in GitHub but hope to engage with you via our technical forums shared above.


Fix missing .clone() on username for Linux target

Was trying to compile the latest commit at 5bda8a3c1432ce6fd009ad81e63b71bff1dc0cd7 on Linux and got the following error:
error[E0382]: borrow of moved value: `username`
  --> src/paths.rs:39:17
   |
25 |         let username = whoami::username();
   |             -------- move occurs because `username` has type `std::string::String`, which does not implement the `Copy` trait
...
29 |         let user_dir = PathBuf::from("/home").join(username);
   |                                                    -------- value moved here
...
39 |                 username
   |                 ^^^^^^^^ value borrowed here after move
   |
   = note: this error originates in the macro `$crate::__export::format_args` which comes from the expansion of the macro `format` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider cloning the value if the performance cost is acceptable
   |
29 |         let user_dir = PathBuf::from("/home").join(username.clone());
   |                                                            ++++++++

There was a .clone() used a few lines above for the macOS target, so thought it should be ok to use here too:
https://github.com/MatthiasGrandl/Loungy/blob/5bda8a3c1432ce6fd009ad81e63b71bff1dc0cd7/src/paths.rs#L26-L29

I really need to setup some checks for Linux 😅


reset release 0.10.0 branch to 0.10.0 tag

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
Does this PR require a change in the driver versions?
What this PR does / why we need it:
It reverts a couple of commits on the release/0.10.0 branch; that release branch will be left as-is, while we will be opening a release/0.10.x soon, given the new procedure highlighted in https://github.com/falcosecurity/libs/pull/821 .
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


fix(@schematics/angular): use peerDependency on typescript

This saves 7MB in the initial install of @angular/cli which depends on this package

@clydin points out this is a breaking change to the install instructions


Convert examples back to JS

Hi folks!
I must have missed some context — why were examples converted to TypeScript? It makes sense if you find development in TS more productive, but most users use JavaScript. I think it's important that we keep examples accessible to the majority of developers.
How do you feel about leaving examples in JS?

I think it's nice to have both examples (but selfishly that's because right now I'm playing with Typescript) but I agree it is really confusing right now. The documentation guide code snippets are all in JS and then the documentation examples are in Typescript. It's not that bad because the syntax is very similar but can be jarring for new users who might be going back and forth for reference.
I recall a while back the documentation had a way to toggle and show how to write with or without Decorators/ES7 syntax. Anyway we can have something like that for JS / Typescript snippets and examples? (willing to contribute if someone can point me to how we handled the toggling of docs before)

If Dan Abramov can't get a response from a maintainer I think it's safe to say we're shouting into the void.
And yeah, this is extremely confusing. The fact that dnd developers use TypeScript doesn't change the fact that this is a React library, and React is a JavaScript library.
JS examples ought to come first, not TS. JS is valid TS, not the other way around...

Having examples in TS is incredibly confusing to those of use who have never used it. I'd love to see some JS examples in the docs.

It should be trivial to set up a build where types are stripped from the examples. This could be done with either Babel or the TypeScript compiler.

:wave:
As much as I admire the effort that's been put into this project, the examples are pretty complex.
This doesn't need to be optimized using all the fancy new features Typescript / our new build systems offer, it just needs to be easy to grok.
I'm looking through the simple sorting example wondering what "as" does and whether that's a new es6 / babel feature or typescript.
I can't get the examples working because I've never used typescript.

Without the TypeScript examples, it is difficult to understand how the types are supposed to work. Since the site and tutorials are all written in JavaScript, the TS code examples are the only official guidance for using TS.

@gaearon Sorry about getting to this late. The examples are kind of playing double-duty as a set of integration tests at the moment. Having them in TS has been very helpful in verifying correctness of the types we provide.
I'm not opposed to having some Vanilla JS examples, but I would favor using Markdown for those, or having them as a separate thing from the TS examples.

Also, one thing we've floated from time to time is using the examples as a suite of automated integration tests as well, which is why they are in a separate package now.

@darthtrevino appreciate you responding and understanding the situation :smile:


Upgrade to Hugo 0.100.2 + Docsy patch

In upgrading to Hugo 0.100.2, we were hitting the following issue:

https://github.com/google/docsy/issues/1065

Update: I've patched docsy, fixing 1065 in this PR by providing a file override. (I'll upstream the change as soon as I can.)
Other changes in the generated site files:

Page meta data:

Descriptions are different in whitespaces
Word counts differ (even if the page content hasnt' changed)

No other diffs that I'm aware of:

Note that the diff below is done over normalized pages that ignore the page header content up until the link to main.css (and the generator version number):
$ cd public && git diff -bw --ignore-blank-lines -I "Hugo 0." -- . ':(exclude)*.[^h]*'
$

/cc @nate-double-u ... in case you know of other CNCF project hitting this issue.


Fix copy/paste error. Set provider to AWS.

Pull Request Test Coverage Report for Build 730

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

Totals

Change from base Build 728:
0.0%

Covered Lines:
874

Relevant Lines:
875

💛  - Coveralls


Migrate to AndroidX

@faycelchaoua thank you for doing this!  Could you remove the .idea files and maybe add that folder to .gitignore?

@faycelchaoua sorry I missed this but could we also revert changes in this directory:
https://github.com/googlesamples/google-services/tree/master/android/signin/app-legacy
That one is not meant to be up to date (we should probably just delete it but that's a whole different PR :-) _

@faycelchaoua thank you!


Deprecation/inactivation of run_Fastq_Multx

Making my own copy of the PR for https://github.com/kbaseapps/kb_ea_utils/pull/12 so I can debug the build

For https://kbase-jira.atlassian.net/browse/PTV-1445


Fix styling when theme is change in another device

Summary
Update all the styles when the theme is changed in another device
Ticket Link
https://mattermost.atlassian.net/browse/RN-544

@hmhealey @mkraft have you guys tested this one?

@enahum Oops didn't notice the label. Testing now.

I changed themes from browser while viewing each mobile view on the iPhone 6 emulator 👍

I'm seeing the drawer bleeding through some of the components on Android. There's a screenshot on pre-release

Cool, looks good to me now


N-27 Debugging

Bugs to be cleared
Here we collect things to be soon solved but not absolutely critical
Hero Parallax http://localhost:3000/ausbildung-theaterpaedagogik/einstiege
on Firefox the fixed/sticky does not work correctly (if I scroll back to top empty space shows up - if I release the scrollbar it is ok again)

The rendering bug in Firefox has been fixed.


Add an 'ignore' item to watch objects to pass filenames to be ignored…

… on to nodemon

Please add an explanation to the README.
Otherwise looks fine

Explanation added; thank you, I forgot!

:shipit: then.
:tada: Thank you @stuartlangridge .


Dial support and pxtparts documentation

Boardhost file changed to support new JSON arguments in the simulationBehavior definition
Added basic documentation about pxtparts arguments description
DO NOT merge before checking these changes

@chmora,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Is this still required?

Yeah well have to get to this soon.

From: Peli de Halleux<EMAIL_ADDRESS>Sent: Thursday, April 20, 2017 4:11:21 PM
To: Microsoft/pxt
Cc: Sam El-Husseini; Review requested
Subject: Re: [Microsoft/pxt] Dial support and pxtparts documentation (#1812)
Is this still required?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fpull%2F1812%23issuecomment-295959796&data=02|01|Sam.El-Husseini%40microsoft.com|fa9bc13d734f46d6562e08d488428eff|72f988bf86f141af91ab2d7cd011db47|1|0|636283266826228301&sdata=ixfEezS7c1SN9xgZhd1GmB%2BuGJ5bl0uo%2FJCQrPrx0gE%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP6rzBu7hXNhEVQq0qzbXdrkOkqAVDMgks5rx-YZgaJpZM4MwIPg&data=02|01|Sam.El-Husseini%40microsoft.com|fa9bc13d734f46d6562e08d488428eff|72f988bf86f141af91ab2d7cd011db47|1|0|636283266826228301&sdata=qKLA9dMmmhVCVX3CQAo%2BVRUNtqPcWBodO92VfxAhMC8%3D&reserved=0.

What is the state of this PR?

Need to apply @darzu's feedback and merge.


Publish issue 14

Name change in Architecture and diagrams.  Resolved ambiguity between a more "Broadcast Controller" IPMX Controller and the more limited element "IPMX Device Controller" which handles EDID type functionality.

@rbgodwin, I checked #23 and see that it already has these changes and additional ones. I used IPMX Device Controller, IPMX Device Control API and IPMX Control System there and cleaned the text from any other variants of these names. I think, #23 can be accepted after we finish with IPMX Device Controller definition and replace the obsolete terms in diagrams. Don't you mind moving to #23?

On #23 there are no updates to the diagrams. This pull request has updates to the diagrams to match name changes. However I think there may be a consensus to use EDID Device Control and IPMX Controller so we need one more pass.
Since we are seeing confusion using the current names I would like to get these changes in this week. I can do the changes using EDID Device Control and IPMX Controller and this will be consistent with the BCP https://specs.amwa.tv/nmos-edid-connection-management/branches/publish-bcp-mappins/docs/1.0._EDID-Mapping.html#is-05-ref

@rbgodwin, it seems to me that we need to raise it up during the next call and then vote using a Slack poll.

It was covered within another PR.


mysql-setup is broken in the quickstart command

Describe the bug
When trying to run the datahub docker quickstart command there is an error with the mysql-setup command
To Reproduce
Steps to reproduce the behavior:
https://datahubproject.io/docs/quickstart/
Expected behavior
The init.sh script should run and properly create the tables needed for the metadata store
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Mac

Additional context
Just started happening around noon, which is when the smoke test started breaking as well

Thank you for reporting! We are taking a look.


update release documentation

Can we add that master should be merged back into outstanding release branches after a release? We'll also need to update the default branch in GitHub, right?


Dataloader usage and implementation question

Thank you @sunli829 for this awesome repo!
I have a question about how Dataloader should be implemented in practice.
From all the examples I have seen such as this one (https://github.com/async-graphql/examples/blob/master/tide/dataloader-postgres/src/main.rs), a Dataloader is created and stored as global data and then accessed via the schema's Context.
This is also documented here: https://async-graphql.github.io/async-graphql/en/dataloader.html
Since it is global struct, how does the Dataloader implementation actually ensure that batching and caching of data per graphQL request? By storing a Dataloader in the Context, wouldn't that end up batching and caching calls across multiple graphQL requests since there is only 1 global instance of a Dataloader?
Thanks!

I have the same question, can @sunli829 help please? Thanks in advance :)


Compile Binary for Arm?

Description
I have a raspberry Pi 3b that I carry on me while at school, I have managed to reserve an IP for its MAC address with my school IT department (to run PHP-based web apps), but i cant use the docker image as docker itself kinda just hangs and does absolutely nothing,
Is there a way I can use this on said Raspberry Pi? I run ArchLinux Arm on it, (aarch64)  and want to be able to run this program on it (preferably a binary, can compile if needed)
What would be needed to either
A) Run it
or
B) Compile a Binary for it?
This is what i get when i try to run via yarn start
[alarm@alarm code-server]$ yarn start
yarn run v1.15.2
$ cd ./packages/server && yarn start
warning package.json: No license field
warning ../package.json: No license field
$ node --max-old-space-size=32384 --require ts-node/register --require tsconfig-paths/register src/cli.ts
internal/modules/cjs/loader.js:670
    throw err;
    ^

Error: Cannot find module 'ts-node/register'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:668:15)
    at Function.Module._load (internal/modules/cjs/loader.js:591:27)
    at Module.require (internal/modules/cjs/loader.js:723:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:945:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:363:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:61:3)
    at internal/main/run_main_module.js:11:1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hey @Merith-TK, we are currently working on an ARM-based build for code-server but it's not quite ready yet. We will also need to trim the memory consumption before this would be practical for a Raspberry Pi. See #35

Thanks, let me know on any progress
also the site is saying that they arnt accepting signups?

@Merith-TK That is correct, sign-ups for coder.com are currently disabled at the moment. We are working on a new user-facing product for the website

Are there ways i can force it to compile for arm? I really am a newb to yarn

I tried to cross-build but I was hit by
#18 2921. ERROR BUILD:SERVER:BINARY:PACKAGE Failed: Failed to package binary: ✔ Wrote 1245 files!
#18 2921. ✔ Wrote 1 file!
#18 2921. Error: Forbidden
#18 2921.     at e.Binary. (/src/packages/server/node_modules/@coder/nbin/out/api.js:1:43397)
#18 2921.     at Generator.next ()
#18 2921.     at s (/src/packages/server/node_modules/@coder/nbin/out/api.js:1:40627)
#18 2921.     at process._tickCallback (internal/process/next_tick.js:68:7)
#18 2921. npm ERR! code ELIFECYCLE
#18 2921. npm ERR! errno 1
#18 2921. npm ERR! server@ build:binary: ts-node scripts/nbin.ts
#18 2921. npm ERR! Exit status 1
#18 2921. npm ERR!
#18 2921. npm ERR! Failed at the server@ build:binary script.
#18 2921. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
#18 2921.
#18 2921. npm ERR! A complete log of this run can be found in:
#18 2921. npm ERR!     /root/.npm/_logs/2019-07-20T18_01_23_706Z-debug.log
Giving up for now...

Like we said @crazyquark, it needs to be fixed in our end first before you can self-build it for ARM. The memory usage is also way too high to be considered ready for Raspberry 3B+ (nbin only builds for amd64, not ARM atm).

Xheesuz..
Issue number 18 just got spammed lol
On Sat, Jul 20, 2019, 8:12 PM Kibo Hikari<EMAIL_ADDRESS>wrote:

Like we said @crazyquark https://github.com/crazyquark, it needs to be
fixed in our end first before you can self-build it for ARM. The memory
usage is also way too high to be considered ready for Raspberry 3B+ (nbin
only builds for amd64, not ARM atm).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cdr/code-server/issues/654?email_source=notifications&email_token=ACPQOXRTVMDXV7KURWCIN5DQAPH3TA5CNFSM4HLBGX4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2N2ARQ#issuecomment-513515590,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACPQOXX75ZGFJDQL3BKZXDTQAPH3TANCNFSM4HLBGX4A
.

All right, we'll wait quietly :)

v2 is in the works, and should significantly reduce memory usage. We've merged ARM support into nbin, so we'll tackle ARM builds for code-server once we merge v2.

v2 is in the works, and should significantly reduce memory usage. We've merged ARM support into nbin, so we'll tackle ARM builds for code-server once we merge v2.

(ARM Builds are still broken btw, working on it to fix everything else)

Closing since we have https://github.com/cdr/code-server/issues/35.


Port forwarding not working when docker is active

Hi,
I am not sure this is the right place to ask nor do I know whether this is unexpected for you, but I would like to get your point of view on the following problem I encountered:
I am in the middle of moving Docker container workloads to podman 4.3.1 using netavark as network backend. Some containers are still running in docker, while another one, a postgresql database that for dubious reasons exposes its database to the host port and to another container on its own network, has been moved to podman. When Docker is not running, assigning the database container to the network, while publishing port 5432 on the host using  -p 5432:5432 works exactly as expected (meaning: pointing an external postgresql client to the host works as if the database is running on the host). However, when I start Docker, the port forward on the host to the podman container stops working. Connecting directly to the database container still works. None of the containers still running in Docker publish to the host's port (not to port 5432 nor to any other one).
My guess is that Docker overwrites the port forward in the firewall to the podman container. I do not know how to debug this further or fix this though. Do you have ideas/remarks/workarounds that could support this hybrid situation until all of them have been moved to podman?

Can you share the output of iptables -nvL and iptables -nvL - nat when this happens? I guess there are some conflicting rules in here.

Thank you for following up on this! After a couple more restarts and changes, I do not seem to be able to reproduce it any longer.
Closing the issue, my apologies to have disturbed you with this.

It looks like the issue is back now:
sudo iptables -nvL
Chain INPUT (policy ACCEPT 542 packets, 39542 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy DROP 1 packets, 60 bytes)
 pkts bytes target     prot opt in     out     source               destination
2035K  222M NETAVARK_FORWARD  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            /* netavark firewall plugin rules */
1517K  136M DOCKER-USER  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
1517K  136M DOCKER-ISOLATION-STAGE-1  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
 723K   57M ACCEPT     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ctstate RELATED,ESTABLISHED
    0     0 DOCKER     all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
 723K   69M ACCEPT     all  --  docker0 !docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
    0     0 ACCEPT     all  --  docker0 docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
51548 8889K ACCEPT     all  --  br-af3d99ee7d86 br-af3d99ee7d86  <IP_ADDRESS>/0            <IP_ADDRESS>/0

Chain OUTPUT (policy ACCEPT 521 packets, 48028 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER (1 references)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
 pkts bytes target     prot opt in     out     source               destination
 723K   69M DOCKER-ISOLATION-STAGE-2  all  --  docker0 !docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
    0     0 DROP       all  --  *      br-af3d99ee7d86 !<IP_ADDRESS>/16        <IP_ADDRESS>/0
19897 1174K DROP       all  --  br-af3d99ee7d86 *       <IP_ADDRESS>/0           !<IP_ADDRESS>/16
1497K  135M RETURN     all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0

Chain DOCKER-ISOLATION-STAGE-2 (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DROP       all  --  *      docker0  <IP_ADDRESS>/0            <IP_ADDRESS>/0
 723K   69M RETURN     all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0

Chain DOCKER-USER (1 references)
 pkts bytes target     prot opt in     out     source               destination
1517K  136M RETURN     all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0

Chain NETAVARK_FORWARD (1 references)
 pkts bytes target     prot opt in     out     source               destination
 269K   61M ACCEPT     all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/24         ctstate RELATED,ESTABLISHED
 249K   25M ACCEPT     all  --  *      *       <IP_ADDRESS>/24         <IP_ADDRESS>/0

Chain vl (0 references)
 pkts bytes target     prot opt in     out     source               destination

The nat option does not seem to work:
sudo iptables -nvL - nat
Bad argument `-'
Try `iptables -h' or 'iptables --help' for more information.

sorry the correct command is iptables -nvL -t nat

Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
 2043 87676 DOCKER     all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL
 1993 85736 NETAVARK-HOSTPORT-DNAT  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
    1    60 DOCKER     all  --  *      *       <IP_ADDRESS>/0           !<IP_ADDRESS>/8          ADDRTYPE match dst-type LOCAL
    3   180 NETAVARK-HOSTPORT-DNAT  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
 1100 70444 NETAVARK-HOSTPORT-MASQ  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
    2   123 MASQUERADE  all  --  *      !docker0  <IP_ADDRESS>/16        <IP_ADDRESS>/0
    0     0 NETAVARK-1D8721804F16F  all  --  *      *       <IP_ADDRESS>/16         <IP_ADDRESS>/0

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 RETURN     all  --  docker0 *       <IP_ADDRESS>/0            <IP_ADDRESS>/0

Chain NETAVARK-1D8721804F16F (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/16
    0     0 MASQUERADE  all  --  *      *       <IP_ADDRESS>/0           !<IP_ADDRESS>/4

Chain NETAVARK-DN-1D8721804F16F (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 NETAVARK-HOSTPORT-SETMARK  tcp  --  *      *       <IP_ADDRESS>/16         <IP_ADDRESS>/0            tcp dpt:6984
    0     0 NETAVARK-HOSTPORT-SETMARK  tcp  --  *      *       <IP_ADDRESS>            <IP_ADDRESS>/0            tcp dpt:6984
  131  7900 DNAT       tcp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            tcp dpt:6984 to:<IP_ADDRESS>:5984

Chain NETAVARK-HOSTPORT-DNAT (2 references)
 pkts bytes target     prot opt in     out     source               destination
  131  7900 NETAVARK-DN-1D8721804F16F  tcp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            tcp dpt:6984 /* dnat name: podman id: e27d2262233abc31a6541b83ef841615580caee66ea6ac5d5e0f1be8ee9dc1d0 */

Chain NETAVARK-HOSTPORT-MASQ (1 references)
 pkts bytes target     prot opt in     out     source               destination
    1    60 MASQUERADE  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            /* netavark portfw masq mark */ mark match 0x2000/0x2000

Chain NETAVARK-HOSTPORT-SETMARK (2 references)
 pkts bytes target     prot opt in     out     source               destination
    1    60 MARK       all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            MARK or 0x2000

I try to use podman and docker side by side, progressively migrate to podman.

I switched completely to podman in the meantime, which resolves the issue for me.

@sumpfralle : thanks for your consideration and for providing the real solution! As mentioned, I pushed through and converted everything to podman right away.
I hope it will help others though that do not have this luxury!


Run @azure/blob-storage web worker js sample got error

Package Name: @azure/blob-storage

Package Version: 12.5.0

Operating system: win10

nodejs

version: v16.15.0

browser

name/version:  chrome

Is the bug related to documentation in

README

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
I tried to run the web worker following the README, and got error from broswer: SharedArrayBuffer is not defined
Expected behavior
I know that the pacakage may need dom api to support parsing and stringifying XML, and we need a polyfill before importing the pacakage. I' d like to know is there any successful sample about that? Or is there other way to use the package in web worker?
Screenshots

Hiya @sgszha17 - thanks for reaching out and opening this issue. This is a known issue in older versions of the jsdom library we use in this example. I previously updated the typescript sample, but apparently did not update the javascript sample 😄
See https://github.com/Azure/azure-sdk-for-js/issues/20934
If you update jsdom to ^19.0.0 it will work again; however, I am now also noticing that the example was changed to use SAS URLs as opposed to connection strings. I'll need to go ahead and update the sample to work with SAS URLs again. But, this should give you a starting point!
Stay tuned for a PR that updates both samples and ensures they are working again

Hi, @maorleger , that's helpful. I have upgrade, and it's worked. Thanks for your answer.


Force the nightly version of cargo on web command

Some users (like me) does not default to nightly version.
I install stable and nightly, default to stable. and use cargo +nightly
for projects that requires nightly features.
I always take a look to examples before diving projects, so I guess it is better
for every new users if the build script does not failed if you don't default to nigthly.

bors r+

In beta and nightly channel, there is no +nightly option.


URL

The README.md says that algorithm details can be viewed in https://arxiv.org/abs/2202.06044, but isn't the address https://arxiv.org/pdf/2301.05847.pdf#page=35?

Hi, you are correct. The correct link to view the algorithm details should be https://arxiv.org/pdf/2301.05847.pdf#page=35. We have updated the README.md to reflect this change. Thank you for pointing this out!


Enchanting Extra Reservations

Anyway to expand this to other Disney reservations such as Bibbidi Bobbidi Boutique?

added BETA version here:
https://github.com/jparkerweb/wdw-adr-checker#bibbidi-bobbidi-boutique-beta

@Jchri010 let me know if this works!

@jparkerweb
It appears to be working, thank you for the addition. For this and the ADR checker, do you know how long each session is active for before you need to refresh and log back in?
I'm curious of the code developed on dining alert site such as stakeout/mouse watcher/etc. As an example I had the ADR up and running for a restaurant and did not get a "beep" or any availability but I did get a stakeout alert. I am wondering if the session expires, even though it appears to still be checking.
Do you know if there is any negative impact to having multiple tabs open in using your ADR tool? It seems to work, but the counts of searches go up very slowly.
Thanks!


Bone with "Local Location" unticked is exported incorrectly

Describe the bug
When the "Local Location" checkbox for a bone is unticked, the bone is displayed in a different position in Blender.  However, this change is not reflected in the exported glTF file.  In fact, the checkbox seems to be entirely ignored, as the exported glTF file is identical no matter the state of this checkbox.
To Reproduce
Steps to reproduce the behavior: (or just grab the .zip file below)

Create a bone with some attached geometry and position it somewhere
Untick the Local Location checkbox
Export
Observe that the bone's position in the exported .gltf doesn't match the .blend file

Expected behavior
I expected the exporter to take the setting into account and match Blender's positioning behaviour.
Screenshots

.blend file/ .gltf
local_location.zip
Version

OS: Linux
Blender Version: 2.80

I confirm that this option is not yet implemented in exporter

Will be fixed by #1378

Fixed by 69746b2b31eeee080d5dfd3c74f1e02742795ed2