feat: 🎸 release elimination of transaction queues

triggers release of latest alpha as the previous merge had older commits
skipped be semver bot
Feat/da 148 eliminate transaction queues (#785)

feat: remove Transaction Queues

The TransactionQueue class has been removed. Most of its methods have been moved over to
PolymeshTransaction and PolymeshTransactionBatch. Methods that returned a TransactionQueue
(all endpoints that write to the blockchain, such as sdk.assets.registerTicker) now return
either a PolymeshTransaction or PolymeshTransactionBatch. This means that all operations
in the SDK are now atomic and not prone to race conditions or half-states

The onProcessedByMiddleware method has been moved to PolymeshTransaction and
PolymeshTransactionBase
The Fees interface now contains a total property which is the sum of free
and locked
The PayingAccountType enum now includes a Caller member, to represent cases
where the calling Account has to pay for a transaction’s fees

perf: ⚡ use a single call to fetch latest finalized block

chore: 🤖 implement a way of discriminating batch events

feat: 🎸 Allow passing of nonce as part of ProcedureOptions

refactor: 💡 Remove unnecessary nonce value from txSpec

feat: 🎸 Add currentNonce method to Account

chore: 🤖 Allow async values for nonce

Update src/types/index.ts

feat: support merging transactions into batches

feat: 🎸 expose the MapTxWithData type

docs: ✏ improve rendered documentation to handle code snippets

test: 💍 use proper type in assertion

feat: 🎸 support splitting batches

fix: 🐛 carry manual fees over when simplifying a batch

Add a splitTransactions method to the PolymeshTransactionBatch class
that returns all individual transactions in the batch. This method is
useful when the caller is being subsidized, since batches do not support
subsidies
When a procedure that normally produces batches produced a single
transaction, we weren't passing manual fee data over

Add an sdk.createTransactionBatch endpoint that takes an array of SDK transactions and returns
them all batched in a single transaction. The result of running this batch is an array of the
results of each transaction in the same order
Fix documentation to reflect the fact that transaction queues no longer exist
Improve transaction fee calculation algorithm to avoid edge cases where estimated fees were
different than the actual fees
Expose getProtocolFees from PolymeshTransaction and PolymeshTransactionBatch
Expose the GenericPolymeshTransaction type
(returned by most endpoints that create transactions)

BREAKING CHANGES:

Remove the inputArgs property from PolymeshTransaction. Replaced by the args
property. Arguments for PolymeshTransaction and PolymeshTransactionBatch are now
available at any point in time (previously they could depend on the result of a previous
transaction in the queue)
Remove the isCritical property from both PolymeshTransaction and PolymeshTransactionBatch.
It no longer makes sense without Transaction Queues
Change the run method in PolymeshTransaction and PolymeshTransactionBatch to work similarly
to the run method in TransactionQueue. The method will check if the caller account has
enough balance for fees, the transaction will be run and its status updated. The method returns
a Promise that resolves to the result of running the transaction. For example, calling run on
the transaction returned by asset.registerTicker will return a Promise that resolves to a
TickerReservation entity
Change the argument received by the callback passed to onStatusChange to
PolymeshTransactionBase. If type refinement is required, the isPolymeshTransaction
and isPolymeshTransactionBatch typeguards can be used (they can be imported from types)
Change the return type of getFees in PolymeshTransaction and PolymeshTransactionBatch
to PayingAccountFees, which contains details about the Account that will pay for the fees,
its remaining balance (before paying), and the fees themselves
Remove the getPayingAccount method from PolymeshTransaction and PolymeshTransactionBatch.
Its result is now contained in getFees
Change the PayingAccount type to now only contain allowance: BigNumber when type is
Subsidy. For Caller and Other, there is no allowance
Rename getFees to getTotalFees in PolymeshTransaction and PolymeshTransactionBatch

:tada: This PR is included in version 15.0.0-alpha.17 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 15.1.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 17.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


IE11 and rowsPerPage update

IE11 updates which refactor includes to be indexOf (more info on difference here), and wraps an IF statement around the Object.value call. (https://github.com/gregnb/mui-datatables/issues/1451)
rowsPerPage now allows updates on re-renders. (https://github.com/gregnb/mui-datatables/issues/1445)

Coverage increased (+0.01%) to 83.788% when pulling e3f18dbd11c51d5347188a906ac427a7ba66c81f on ie11_fixes into db5ec061d7678e9cdc247f110116277c9a49447c on master.


Update with fixes for Windows and new features for a newer Atom

Removed the launch.cmd requirement, instead putting everything into one file (makes it much simpler)
If not in terminal mode and a filename command has quotes around it, remove those quotes (necessary in terminal mode, breaks otherwise in normal mode)
If not in terminal mode, allow command to be relative path to an executable in any project directory, or an absolute path
Make ProjectDir always point to the main project directory, as it would be an empty string if no file was opened
Add ability for commands to be run only in certain contexts, using a set of flags
Use whatever data is available in the current 'context', instead of refusing to run the command if no file or editor is open

I added another commit to allow the console to show in-progress input, instead of waiting for a full line of text. This became annoying when I was running a program with a progress bar, because the console wouldn't display my progress until it was all done. I will note that I haven't quite done sufficient testing yet, although I think it should work, feel free to criticize and fix my work.

thanks, I will take a look at the differ.

I realized I made quite a few mistakes, and am working on fixes, sorry. Also, I noticed that you use a different 'tabbing' scheme, would you like me to fix all of my changes to that scheme?


chore: add additional BN native converter

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant and/or add your own.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project (You can use the linters)
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas and hacks
[ ] I have made corresponding changes to the documentation
[ ] I have added tests to verify my fix or my feature
[ ] New and existing unit tests pass locally with my changes
[ ] I have added the relevant labels to my PR in so that relevant reviewers are notified

CI is likely unrelated to this change - it seems to be a mismatch between the Torch version used to build Torch-TensorRT and the version of Torch in the environment.


Admins can delete pages

This should resolve Issue #32,
Admins have the ability to delete pages.

Awesome, thanks for the PR!


Snippets do not really get exportet

Currently, the snippets just get appended to a <span> at JSFiddle.
However that span is not the real editor text area. Which is why it can't be edited and there is no syntax highliting.
This renders the extension useless at the moment.

Fixed in:

https://github.com/NLDev/Snippeter/commit/686285b2d52e54b01900e0b35bff389045bd525c
https://github.com/NLDev/Snippeter/commit/cbde280ec913ccc9c47249ce53422b3375fd0ce7
https://github.com/NLDev/Snippeter/commit/96ef8f3840bada61c88d4012b9ee39e9b17484a2
https://github.com/NLDev/Snippeter/commit/242776c73ea1fa834d970fd645aea5de024192fe


tests: smp_suspend: Tweak duration and timeouts

Reduces the number of seconds that the test runs to 15 seconds (down from 30 seconds). This should still be sufficient time to determine if there is anything amiss with the synchonous thread suspend/resume. Furthermore, the test itself has been tagged as being slow and its timeout increased to 10 minutes (600 seconds) as some simulators are rather slow.

There is another one like this in posix (semaphores) I should tweak

See #67873


⚠ Mobitopup has degraded performance

In 6e0fbd5, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 8024 ms

Resolved: Mobitopup performance has improved in 0b55bee.


注销问题

Reproduction link
https://github.com/hbyunzai/ng-yunzai.git
Steps to reproduce
直接点击注销，跳转路径有问题
What is expected?
正常退出注销后 重新返回至登录页面
What is actually happening?
无法返回登录页面

Environment
Info

ng-yunzai
12.0.6

Browser
Google Chrome

还有拦截器的ToLogin也需要修改逻辑，保证 server cookie 正常删除

Closed https://github.com/hbyunzai/yelon/commit/86b440a2af3b89018bc0f92efe42b8c7dc2b9710


BugFix - Issue with the nitro server socket

An error appears randomly when mounting the container.
As seen here :
https://github.com/nuxt/nuxt/issues/13587

Has been merged #7  to dev


[WIP] Mapping for docker-compose to k8s and openshift conversion

WIP for #82
cc @kadel

@procrypt Should we close this for now or are you still working on it?

@cdrage Yes we can close this.


yuzuPackages.compat-list: unstable-2024-02-14 -> unstable-2024-02-22

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-02 in filename of file in /nix/store/61k5311k570l4j0c5qf29zc6w0awdd4d-yuzu-compatibility-list-unstable-2024-02-02

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/61k5311k570l4j0c5qf29zc6w0awdd4d-yuzu-compatibility-list-unstable-2024-02-02 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/ddfe522ab88d8f9450a8f18f0aca4034aa719d22#yuzuPackages.compat-list

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/61k5311k570l4j0c5qf29zc6w0awdd4d-yuzu-compatibility-list-unstable-2024-02-02
ls -la /nix/store/61k5311k570l4j0c5qf29zc6w0awdd4d-yuzu-compatibility-list-unstable-2024-02-02/bin

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

3 packages built:

yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-08 in filename of file in /nix/store/d79ldxz0dlp5nr299b71d8668ja3420x-yuzu-compatibility-list-unstable-2024-02-08

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d79ldxz0dlp5nr299b71d8668ja3420x-yuzu-compatibility-list-unstable-2024-02-08 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/5d1e28a32f1c02738872d79e1b5d41e727ea5cb1#yuzuPackages.compat-list

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d79ldxz0dlp5nr299b71d8668ja3420x-yuzu-compatibility-list-unstable-2024-02-08
ls -la /nix/store/d79ldxz0dlp5nr299b71d8668ja3420x-yuzu-compatibility-list-unstable-2024-02-08/bin

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

3 packages built:

yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-12 in filename of file in /nix/store/6kzb1h14hdjx61jvqypxaji7iy90bkkz-yuzu-compatibility-list-unstable-2024-02-12

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6kzb1h14hdjx61jvqypxaji7iy90bkkz-yuzu-compatibility-list-unstable-2024-02-12 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/77fd3e220ce54d13b5a83132f1b5ac67d38ccdee#yuzuPackages.compat-list

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6kzb1h14hdjx61jvqypxaji7iy90bkkz-yuzu-compatibility-list-unstable-2024-02-12
ls -la /nix/store/6kzb1h14hdjx61jvqypxaji7iy90bkkz-yuzu-compatibility-list-unstable-2024-02-12/bin

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

3 packages built:

yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-19 in filename of file in /nix/store/s80shwd9vmrchwggnwak3h2yb2rd17d1-yuzu-compatibility-list-unstable-2024-02-19

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s80shwd9vmrchwggnwak3h2yb2rd17d1-yuzu-compatibility-list-unstable-2024-02-19 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/2df763f3fef0571fbfad3225b3f46adb12002917#yuzuPackages.compat-list

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s80shwd9vmrchwggnwak3h2yb2rd17d1-yuzu-compatibility-list-unstable-2024-02-19
ls -la /nix/store/s80shwd9vmrchwggnwak3h2yb2rd17d1-yuzu-compatibility-list-unstable-2024-02-19/bin

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

3 packages built:

yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-22 in filename of file in /nix/store/0bk7la1y5azs4pzypygzhvy5kwphrqk8-yuzu-compatibility-list-unstable-2024-02-22

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0bk7la1y5azs4pzypygzhvy5kwphrqk8-yuzu-compatibility-list-unstable-2024-02-22 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/fa4e3cf9ea13e12a42676e2d6cb6b28ac32a2b6c#yuzuPackages.compat-list

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0bk7la1y5azs4pzypygzhvy5kwphrqk8-yuzu-compatibility-list-unstable-2024-02-22
ls -la /nix/store/0bk7la1y5azs4pzypygzhvy5kwphrqk8-yuzu-compatibility-list-unstable-2024-02-22/bin

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

3 packages built:

yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-26 in filename of file in /nix/store/6shd7bzn2d8r1nx2lz84wjy2d4hk0hfs-yuzu-compatibility-list-unstable-2024-02-26

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6shd7bzn2d8r1nx2lz84wjy2d4hk0hfs-yuzu-compatibility-list-unstable-2024-02-26 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/5e15dae0e7c742b33e03ac54c3318bfb57aa7f07#yuzuPackages.compat-list

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6shd7bzn2d8r1nx2lz84wjy2d4hk0hfs-yuzu-compatibility-list-unstable-2024-02-26
ls -la /nix/store/6shd7bzn2d8r1nx2lz84wjy2d4hk0hfs-yuzu-compatibility-list-unstable-2024-02-26/bin

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

3 packages built:

yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-03-04 in filename of file in /nix/store/41xg7dj84mk0cjcq9h1i5y6sdby6bchy-yuzu-compatibility-list-unstable-2024-03-04

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/41xg7dj84mk0cjcq9h1i5y6sdby6bchy-yuzu-compatibility-list-unstable-2024-03-04 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/57c96a521abd7de22af9b5f9c8053265ecf80783#yuzuPackages.compat-list

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/41xg7dj84mk0cjcq9h1i5y6sdby6bchy-yuzu-compatibility-list-unstable-2024-03-04
ls -la /nix/store/41xg7dj84mk0cjcq9h1i5y6sdby6bchy-yuzu-compatibility-list-unstable-2024-03-04/bin

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

3 packages built:

yuzuPackages.compat-list
yuzuPackages.early-access
yuzuPackages.mainline

Maintainer pings


Add Gateway service

Added initial support for an embedded IPFS daemon

Adds an AAR for the agregore-ipfs-daemon to the dependency tree (and links to it's .so file
Adds a new IPFSService class which can start the gateway as well as bind a MulticastLock
Adds an IPFSStarter class which can bind to the IPFSService
Invokes IPFStarter inside the main chrome activity in order to start the gateway if it isn't already running.

This also adds some more scripts for automating the dev process. These will likely get updated as we go.
Limitations:

Only works on Android 9 or lower because Android 10 added security features which break MDNS support in libp2p

We'll be fixing the MDNS issue in the gateway while the protocol handlers get integrated wit the app in #2

I'm contemplating whether we should split the patch into two, one which adds the AAR for the gateway, and on that sets up the rest of the code for it.
This would make the diffs small enough to actually see. Alternately we could pull the third_party/agregore-ipfs-daemon folder off into it's own repo and have it pulled in at runtime via CIPD in the DEPS file.


How to preserve form field values when capturing a page?

I'm working on a script that captures a page with a sign up form on it. I need to later be able to see what the visitor entered into the form. This is done for compliance.
html-screen-capture-js works great when capturing the page, but it captures the page in its original state, meaning if you enter something into a form on the page and then capture the screen, you won't see what was entered. Is there a way to also capture the form field values entered in real time?

Sorry for the late response...
If we're talking about simple input tags, the current value can be added as a value attribute to the html node (or replace the default value which is already there), so it looks like an easy thing to support. Would that be ok?

This is precisely what I did. Essentially I had to set the value attribute to what has just been entered:
$j(this).focusout(function(){
     $j(this).attr("value", $j(this).val());
});

or for a select:
$j(this).focusout(function(){
    $j(this).children().each(function(){
	$j(this).attr('selected', false);
     });
     $j(this).children('[value="'+$j(this).val()+'"]').attr('selected', true);
});

What characters would you escape though? I'm not escaping anything.

cool, seems like the problematic chars (e.g. < > " ' &) are already taken care of by the attr function

I've added support for 2 types of fields: input-text, and select-options.

Hey Uri, do you see a problem if I extended the functionality of the feature you added for input-text to textarea?
if (domElm.tagName.toLowerCase() === 'input' && domElm.getAttribute('type') === 'text') {
	newElm.setAttribute('value', domElm.value);
} else if(domElm.tagName.toLowerCase() === 'textarea') {
        newElm.innerText = domElm.value;
} else if (domElm.tagName.toLowerCase() === 'select' && domElm.children) {...
...

Hi,
Looks cool to me!
Thanks,
Uri Kalish
בתאריך יום ד׳, 15 באפר׳ 2020, 03:12, מאת alimovz<EMAIL_ADDRESS>
:

Hey Uri, do you see a problem if I extended the functionality of the
feature you added for input-text to textarea?
if (domElm.tagName.toLowerCase() === 'input' && domElm.getAttribute('type') === 'text') {
newElm.setAttribute('value', domElm.value);
} else if(domElm.tagName.toLowerCase() === 'textarea') {
newElm.innerText = domElm.value;
} else if (domElm.tagName.toLowerCase() === 'select' && domElm.children) {...
...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/html-screen-capture-js/html-screen-capture-js/issues/4#issuecomment-613743239,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPUPD45UFWQYB5YS32ES53RMT3XRANCNFSM4G65W4UQ
.


2023 06 06

Agenda - 2023 06 06
Time 1630pm (BST) - See the time in your timezone

Chair – Tammy McClellan @tmcclell (Microsoft)
Vice-Chair – Chris Lloyd-Jones @Sealjay (Avanade)
Convener – Sean Mcilroy @seanmcilroy29  (GSF)

Antitrust Policy
Joint Development Foundation meetings may involve participation by industry competitors, and it is the intention of the Joint Development Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
If you have questions about these matters, please contact your company counsel or counsel to the Joint Development Foundation, DLA Piper.
Roll Call
Please add 'Attended' to this issue during the meeting to denote attendance.
Any untracked attendees will be added by the GSF team below:
Agenda

[ ] Review/Approve agenda

Proposed new projects

[ ] https://github.com/Green-Software-Foundation/oc/discussions/17 - Sarah @greenhsu123:

Project Update

[ ] Add details here

Agenda submissions

[ ] #33
[ ] #32
[ ] #35

Governance

[ ] https://github.com/Green-Software-Foundation/oc/issues/23
[ ] https://github.com/Green-Software-Foundation/oc/issues/26
[ ] https://github.com/Green-Software-Foundation/oc/issues/36

Process Improvement

[ ] https://github.com/Green-Software-Foundation/oc/discussions/11 - @Sealjay
[ ] Review the GSF Contributing Writers' Guidelines
[ ] #36
[ ] #37

Regular updates

[ ] https://github.com/Green-Software-Foundation/oc/issues/29

Rhythm of business

[ ] OKR Tracking - Asim

Actions

@jawache to revert back on https://github.com/Green-Software-Foundation/oc/discussions/17

Deferred

https://github.com/Green-Software-Foundation/oc/discussions/18
[ ] https://github.com/Green-Software-Foundation/oc/discussions/16 - Sarah

AOB

[ ] Any questions or other business

Adjourn

FYI, added a PR to support #17 https://github.com/Green-Software-Foundation/oc/pull/38

Attended

Attended

attended

attended


CorsairLightingProtocol/examples/MultipleFans/MultipleFans.ino Error

CorsairLightingProtocol/examples/MultipleFans/MultipleFans.ino
This Code only control 8 leds on Corsair LL, How to setup it for all 16 leds ?

i dont know if it works the same but you can edit the number of leds in the
ino file directly then upload it too your arduino
On Mon, 8 Mar 2021 at 06:01, MinadaLakmira<EMAIL_ADDRESS>wrote:

CorsairLightingProtocol/examples/MultipleFans/MultipleFans.ino
This Code only control 8 leds on Corsair LL, How to setup it for all 16
leds ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Legion2/CorsairLightingProtocol/issues/218, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJCVOYBO4UQCKD3NRNY3ZULTCRR4LANCNFSM4YYYMAYA
.

@MinadaLakmira you have to change the line #define NUMBER_OF_LEDS_PER_FAN 8 to 16

No problem, I found the answer 👍👍-------- Original message --------From: Robbo247<EMAIL_ADDRESS>Mon, 8 Mar 2021, 11:59To: Legion2/CorsairLightingProtocol<EMAIL_ADDRESS>MinadaLakmira<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Re: [Legion2/CorsairLightingProtocol] CorsairLightingProtocol/examples/MultipleFans/MultipleFans.ino Error  (#218)
i dont know if it works the same but you can edit the number of leds in the
ino file directly then upload it too your arduino
On Mon, 8 Mar 2021 at 06:01, MinadaLakmira<EMAIL_ADDRESS>wrote:

CorsairLightingProtocol/examples/MultipleFans/MultipleFans.ino

This Code only control 8 leds on Corsair LL, How to setup it for all 16

leds ?

—

You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub

https://github.com/Legion2/CorsairLightingProtocol/issues/218, or

unsubscribe

https://github.com/notifications/unsubscribe-auth/AJCVOYBO4UQCKD3NRNY3ZULTCRR4LANCNFSM4YYYMAYA

.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Are people actually using corsairs fans etc on this project just too bypass
a genuine node etc ,i thought this project was aimed more as a custom non
brand lighting workaround
On Mon, 8 Mar 2021 at 07:57, Leon Kiefer<EMAIL_ADDRESS>wrote:

Closed #218
https://github.com/Legion2/CorsairLightingProtocol/issues/218.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Legion2/CorsairLightingProtocol/issues/218#event-4419769171,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJCVOYBFHPVVRXTH5YPGDBDTCR7N7ANCNFSM4YYYMAYA
.


Squiz.Arrays.ArrayDeclaration.ValueNoNewline false positive with static fn

Describe the bug
Squiz.Arrays.ArrayDeclaration.ValueNoNewline triggers false positive at static fn.
Code sample
return [
    static fn (string $value): AAA => new AAA($value),
    BBB::fromString(...),
];

To reproduce
Steps to reproduce the behavior:

Create a file called test.php with the code sample above...
Run phpcs test.php ...
See error message displayed

PHPCS output here

Expected behavior
No error
Versions (please complete the following information)

Operating System
macos 14

PHP version
8.3

PHP_CodeSniffer version
3.10.1

Standard
Squiz

Install type
composer

Additional context
Add any other context about the problem here.
Please confirm

[x] I have searched the issue list and am not opening a duplicate issue.
[x] I have read the Contribution Guidelines and this is not a support question.
[x] I confirm that this bug is a bug in PHP_CodeSniffer and not in one of the external standards.
[ ] I have verified the issue still exists in the master branch of PHP_CodeSniffer.

Confirmed. Thanks for reporting this @simPod.
This looks like a similar issue to #368 which was fixed by #369 and #379, which were included in the 3.9.1 release.
I've checked and the fixes in the 3.9.1 release are not directly related to this issue. This issue can be reproduced both with PHPCS 3.9.0 as well as master.
The Squiz.Arrays.ArrayDeclaration sniff is known to be problematic and has been for years.
The problem is largely that as soon as something is excluded from that sniff, the sniff is broken. This is a design flaw in the sniff.
I've been building up a (highly configurable) NormalizedArrays standard in PHPCSExtra to replace it, but that's not complete yet. Would be lovely if I could find some time to finish that at some point.
With that in mind, I will not be working on this issue.
If someone would submit a PR with a small/simple fix for this issue, I will accept it, but other than that, this sniff is out of bounds for large fixes/rewrites as it is just not worth the time.

Seems also related to this issue?
<?php declare(strict_types = 1);

class Bug {
    public static function bug(): mixed {
        return [
            'paginator' => [
                new class() {
                    public function toArray(): mixed {
                        return [];
                    }
                },
            ],
        ];
    }
}

 9 | ERROR | [x] The first value in a multi-value array must be on a new line
 9 | ERROR | [x] Each value in a multi-line array must be on a new line

@LastDragon-ru To be honest, that looks like a completely different issue to me.


Dependencies to unknown classes

Expected Behavior
Code should rely 100% on specified APIs.
Actual Behavior
Ugly dependency to internal com.sun classes. I cannot build with the provided JDK installed by Bazel.

Version: 2ce7768f42d2aee2cee8c9cfe82db96deca99387
Platform: Ubuntu 20.04

@lbovet thanks for reporting this! I'm unfortunately not sure what exactly you mean by this... may I request more details?
Which dependency to what unknown class in which source? Can you copy/paste some error message? )Or even Screenshot?)

com.sun.net.httpserver
But I just searched and it seems to be a standard API. For some reason this package is not found in my install
Investigating further...

Looks like it would require to include the module jdk.httpserver but I have no idea how to do that with bazel.

Oh, god! Why are dependencies always such a mess! 😵💫

Looks like it would require to include the module jdk.httpserver but I have no idea how to do that with bazel.

I don't think that's possible or what would help. What's likely going on here is that I've configured Bazel to use "the host's Java environment". And for SOME reason, your local Java OS package (?) doesn't have this module... does Debian package individual JDK (21) modules as separate DEB packages?! But Bazel CAN also have a dependency to a fixed "remote" JDK and download and build with that. It actually originally used to be like that here, and then I changed it. I think seeing this makes me change my mind (again) - let me do something (right now) to just make Bazel download and use a "good" JDK that we know works to build this project - that seems easier, after all.

make Bazel download and use a "good" JDK that we know works to build this project

Wait, I'm confused - the project IS ALREADY configured to do this like so, as-is right now!
Except... I am so stupid, and set --java_runtime_version= as well as --tool_java_runtime_version TWICE, once as 21 (which means "your local JDK" - I think) and before that as remotejdk_21 (which means "use one that Bazel will DL") - that's probably not very smart... 🤣 I wonder if #549 will fix this problem, for you? (Was it build javac failures, or test execution failures?)
@lbovet would you be willing to post an exact error message? Like some output you get e.g. from ./test.bash with Bazel failures.

Bazel installs a JDK 21. I have put it in the PATH so that we have only one JDK used for the project:
Thus, the java command used buy the IDE build is /home/<username>/.cache/bazel/_bazel_<username>/install/<hash>/embedded_tools/jdk/bin/java
Apparently, this JDK does not have the jdk.httpserver module built-in, hence the problem.
We I run  java --list-modules, I don't see it. Can you see it?
I am very far from having any skills in this area...

The fix does not help.

So you git pull and have #549 now? OK.
Hm. Sorry but just to clarify what exactly we are actually chasing down here:

Is ./test.bash working for you? Fully - does it complete successfully? Just to understand if the Bazel build works on CLI, for you. If that doesn't work, we should perhaps make sure that works, first.

When that works, are you reporting here that you have red in VSC? "Just" in that web/sun/src/main/java/dev/enola/web/sun/SunServer.java due to the import com.sun.net.httpserver - or also elsewhere? Is that the only problem left?

/home//.cache/bazel/bazel/install//embedded_tools/jdk/bin/java
I have put it in the PATH so that we have only one JDK used for the project:

Nice idea! (Although that "hash" may change, of course.)

Apparently, this JDK does not have the jdk.httpserver module built-in, hence the problem.

That's interesting! And surprising me (because I interpret this documentation as meaning that this line is causing the test to run under the JDK 21 which Bazel downloads).
Assuming (see above) that CLI works for you, and you "just" have an in-VSC-IDE problem, could you please try to see what happens if you run (just) this on the CLI, to see if web/sun/src/test/java/dev/enola/web/sun/test/SunServerTest.java passes:
bazelisk test //web/sun:src/test/java/dev/enola/web/sun/test/SunServerTest

When I run java --list-modules, I don't see it. Can you see it?

Here is some of my output - first using the JDK that I have installed via OS package in my Fedora workstation:
$ which java
/usr/bin/java

$ java -version
openjdk version "21.0.2" 2024-01-16
OpenJDK Runtime Environment (Red_Hat-<IP_ADDRESS>.13-1) (build 21.0.2+13)
OpenJDK 64-Bit Server VM (Red_Hat-<IP_ADDRESS>.13-1) (build 21.0.2+13, mixed mode, sharing)

$ java --list-modules | wc --lines
69

$ java --list-modules | grep jdk.httpserver
<EMAIL_ADDRESS>
and now similarly using the one that Bazel DL'd, like you:
$  ~/.cache/bazel/_bazel_vorburger/install/14fb027596f626f2526df4873ea20b8b/embedded_tools/jdk/bin/java -version
openjdk 21 2023-09-19
OpenJDK Runtime Environment Zulu21.28+85-CA (build 21+35)
OpenJDK 64-Bit Server VM Zulu21.28+85-CA (build 21+35, mixed mode)

$ ~/.cache/bazel/_bazel_vorburger/install/14fb027596f626f2526df4873ea20b8b/embedded_tools/jdk/bin/java --list-modules | wc --lines
13

$ ~/.cache/bazel/_bazel_vorburger/install/14fb027596f626f2526df4873ea20b8b/embedded_tools/jdk/bin/java --list-modules
NADA | grep jdk.httpserver

Looks like you're right... 🍭  That SunServerTest must be running using my /usr/bin/java?! I'll uninstall it, and see if I can make Bazel run tests with the JDK it DL.

Looks like you're right... 🍭 That SunServerTest must be running using my /usr/bin/java?!
I'll uninstall it, and see if I can make Bazel run tests with the JDK it DL.

$ killall java
$ sudo dnf remove "java-*"
$ bazelisk test //web/sun:src/test/java/dev/enola/web/sun/test/SunServerTest

WARNING: Ignoring JAVA_HOME, because it must point to a JDK, not a JRE.
Starting local Bazel server and connecting to it...
INFO: Analyzed target //web/sun:src/test/java/dev/enola/web/sun/test/SunServerTest (117 packages loaded, 4072 targets configured).
INFO: Found 1 test target...
Target //web/sun:src/test/java/dev/enola/web/sun/test/SunServerTest up-to-date:
  bazel-bin/web/sun/src/test/java/dev/enola/web/sun/test/SunServerTest
  bazel-bin/web/sun/src/test/java/dev/enola/web/sun/test/SunServerTest.jar
INFO: Elapsed time: 9.070s, Critical Path: 4.88s
INFO: 42 processes: 3 internal, 32 linux-sandbox, 7 worker.
INFO: Build completed successfully, 42 total actions
//web/sun:src/test/java/dev/enola/web/sun/test/SunServerTest             PASSED in 0.8s

Executed 1 out of 1 test: 1 test passes.

Now this is curious...

JUST to be extra sure and careful with this wonderful { Fast, Correct } — Choose two Build tool:
$ killall java
$ sudo rm -rf ~/.cache/bazel/
$ bazelisk test //web/sun:src/test/java/dev/enola/web/sun/test/SunServerTest

but it STILL does work for me, as-is. Very weird!
But this seems wrong... I'll try to remove it. Without being able to reproduce it, I've no idea if that will help.

Hm. Sorry but just to clarify what exactly we are actually chasing down here:

@lbovet has clarified by DM that bazelisk test //web/sun:src/test/java/dev/enola/web/sun/test/SunServerTest also does work for him.
So this not a "Bazel CLI build issue", but a "Bazel in/or VSC integration" issue. I've update the issue title accordingly.

We have now figured out the root cause of the problem:
If one uses the ~/.cache/bazel/_bazel_$USER/install/<hash>/embedded_tools/jdk/bin/java, then the problem described in this issue (with some confusion...) occurs: VSC cannot find the jdk.httpserver Java Module where com.sun.net.httpserver.
If however one uses ~/.cache/bazel/_bazel_$USER/<hash>/external/remotejdk21_linux/, then everything works just fine.
In a perfect world, everything should "just work out of the box". For this, ideally ./enola should run java from that remotejdk21_linux. And we could (should) have some start-up (say ... ./env ?) which sets PATH (and JAVA_HOME perhaps?) to that, so that when one starts (VSC) code, it just works. (Although that probably won't work for/in GitHub Codespaces - but one step at a time.)
I'll post a SO question to learn how to query Bazel for the path to the configured Java Toolchain...

I'll post a SO question to learn how to query Bazel for the path to the configured Java Toolchain...

https://stackoverflow.com/q/78057833/421602 - @guw do you happen to know how to do this?

https://github.com/salesforce/bazel-eclipse/blob/888bcd333ac7bd4166fdb411562b74c2b54514d5/bundles/com.salesforce.bazel.eclipse.core/src/com/salesforce/bazel/eclipse/core/model/discovery/BaseProvisioningStrategy.java#L945-L960
It uses a query file because extracting the information requires a bit more Starlark code.

@guw Thank You! I've tried that (after also looking at this) in (draft) PR #558, but running the tools/bazel-java-tool-chain/bazel-java-tool-chain.bash from that PR does not quite work yet, as-is that just outputs this (which isn't the "path" I was hoping to get), I don't suppose you happen to immediately see why?
java_toolchain_info_source_version=21\njava_toolchain_info_target_version=21\njava_toolchain_info_java_home=external/remotejdk21_linux
java_runtime_info_java_home=external/remotejdk21_linux

You need to tweak the output to suite your needs. :)

PR #558 is now simplified (I've found this, yay!), but what I'm struggling with is that it returns (literally) external/remotejdk21_linux - but I would need (e.g.) /home/vorburger/.cache/bazel/_bazel_vorburger/a3cf8df34f0c7a76e9926daaad9ffbf4/external/remotejdk21_linux - how does one get that? (I'm imaging you must have solved this somewhere in https://github.com/salesforce/bazel-vscode-java, to obtain the JDK to set on JDT to build the project.)

bazel info output_base

Should give you the needed info and can be used in shell scripts.

@guw thanks so much, that helped a lot, and was what I was missing! It allowed me to finish and merge PR #558.
@lbovet this is fixed! 💯


changed the callback param for getPerformance method

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


avenida background fix

Added new Avenida background PNG with better sizing. Cloud movement to come soon, background cut off bug being worked on.
Issue Link: https://github.com/nighthawkcoders/game_levels_mp/issues/74


require is not defined in the ESM version of Sosse

Hello, while making a simple dev server I noticed that Sosse still uses require, even in the ESM generated code

Node disallows using require in the ESM module. So it should be imported in the top so it properly builds to import chokidar from 'chokidar'
The full stacktrace is this:
> node main.js
(node:240789) UnhandledPromiseRejectionWarning: ReferenceError: require is not defined
    at _temp2 (file:///home/v1rtl/Coding/tinyhttp/node_modules/.pnpm/sosse@0.6.0/node_modules/sosse/dist/main.mjs:862:26)
    at _temp4 (file:///home/v1rtl/Coding/tinyhttp/node_modules/.pnpm/sosse@0.6.0/node_modules/sosse/dist/main.mjs:885:57)
    at hsr (file:///home/v1rtl/Coding/tinyhttp/node_modules/.pnpm/sosse@0.6.0/node_modules/sosse/dist/main.mjs:907:74)
    at file:///home/v1rtl/Coding/tinyhttp/examples/dev-server/main.js:4:1
    at ModuleJob.run (internal/modules/esm/module_job.js:140:23)
    at async Loader.import (internal/modules/esm/loader.js:162:24)

Sosse version: 0.6.0
Node version: 14.5.0

@talentlessguy Tbh. those requires cannot be moved to the top of sosse. They have to be called dynamically after file changes - thats the essential part for the hot server reload ;).
Maybe there is a chance to switch to dynamic imports, but this is not something I can quickly change, I have to test this in the very detail of each require ^^.

@katywings oh ok, no worries. I could maybe try to find the way to load CJS version of Sosse :thinking:

@talentlessguy I investigated this and in the end got stuck in an upstream blocker :facepalm:
Hot module replace currently is only possible with require, the import cache cannot be invalidated.
This is the corresponding upstream issue: nodejs/modules#307

I gonna watch that upstream issue but ESM support has to unfortunately wait for now :see_no_evil:

Also something that should be watched going forward nodejs/modules#339.


Add files via upload

Also, you can use these graphics to say that your ERC20 token fully compatible with Trust Wallet (https://trustwalletapp.com/logo-assets)

Thanks!


WIP: WORKING ON MAKING THESE CHANGES

Closing pull request because "all the jenkins jobs are configured to ignore branches that are included in pull requests & by you creating pull requests where oracle-build-from-source is the source branch it will basically ignore that branch in every jenkins job"


Added support for configurable Filepond table name

Reopening PR as requested

The discussion for this PR can be found in here #12 Thanks @dmalta for the PR.


InDatabaseCache : ICache

Hi !
Thank you very much for this great package !
I'm trying to create an InDatabaseCache instead of InMemoryCache. We have 3 servers with LoadBalancing. So sometimes data was updated on Server1 but not invalidated on Server2. All these servers are on the same domain.
My idea is to implement an ICache that stores data on a database, so servers can share data between them without problem.
What do you think about that ? Is it a good idea ? Is this efficient ? And would you have any other solution ?
If you want, I can contribute to the project with this InDatabaseCache.
Thank you very much and have a nice day !

There are non-memory based implementations of ICache

https://www.nuget.org/packages/DacheCache.Provider.EF/1.0.1-beta1
https://www.nuget.org/packages/EFCache.RedisCache/
I don't know anything about your environment to answer any of your questions but I have doubts about using a database to avoid using database. Also, (relational) databases are better at storing and allowing to query data that has more structure rather than blobs.

The provider model should allow providing alternative implementations without coupling the implementation with this project. InMemoryCache is just a very simple and a bit crude implementation that could be used as a reference.


fix: Move down offline indicator to bottom on Chose Card type page

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/45272
PROPOSAL: https://github.com/Expensify/App/issues/45272#issuecomment-2222918196
Tests

Precondition:

User should add bank account to their workspace

Launch New Expensify app
Go to workspace settings > Expensify Card (enable in More features)
Go offline
Tap Issue new card
Select the added bank account
Proceed to Step 2 - Choose a card type

[x] Verify that offline indicator is at the bottom of the screen
[x] Verify that no errors appear in the JS console

Note: this applies for only mobile devices where Choose a card type page takes the whole page
Offline tests

Same as test stpes
QA Steps

Same as test stpes

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/f20e0510-eedb-4c5d-8f2e-072d8b28fe99

Android: mWeb Chrome

https://github.com/user-attachments/assets/a8a77c43-a2bf-4650-8863-a92dec3bbe59

iOS: Native

https://github.com/user-attachments/assets/482da707-8e60-41d1-9e48-552222ff2006

iOS: mWeb Safari

https://github.com/user-attachments/assets/0f06b434-2e8e-4bcb-8d41-50f82e9a18cb

MacOS: Chrome / Safari

N/A

MacOS: Desktop

N/A

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome
https://github.com/user-attachments/assets/ec5f018f-6536-4dcb-b07b-d4165752ada7

iOS: Native

iOS: mWeb Safari

https://github.com/user-attachments/assets/0473533d-5612-48c3-aaa6-67526ec593c3

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/a44da05c-592e-46e6-a936-cd18d2d73ac0

MacOS: Desktop
https://github.com/user-attachments/assets/7ad439bd-fafb-4bff-b919-e330dc0dc876

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/Gonals in version: 9.0.13-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/luacmartins in version: 9.0.13-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
failure ❌


net, backend: add more error types to disconnection error

What problem does this PR solve?

Issue Number: close #489
Problem Summary:

A client network error connection timed out was mistakenly reported as a proxy error. The error was syscall.ETIMEDOUT.
I found there were redundant stacks that made stacks too long.

What is changed and how it works:

Add syscall.ETIMEDOUT to IsDisconnectError() and move IsDisconnectError() to error.go.
Refined errors.WithStack() to remove redundant stacks.

Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Notable changes

[ ] Has configuration change
[ ] Has HTTP API interfaces change
[ ] Has tiproxyctl change
[ ] Other user behavior changes

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Codecov Report
Attention: Patch coverage is 58.33333% with 5 lines in your changes are missing coverage. Please review.

:exclamation: No coverage uploaded for pull request base (main@233f456). Click here to learn what that means.

Files
Patch %
Lines

pkg/proxy/net/packetio.go
40.00%
3 Missing :warning:

pkg/proxy/net/tls.go
0.00%
2 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #490   +/-   ##
=======================================
  Coverage        ?   64.48%
=======================================
  Files           ?       61
  Lines           ?     5809
  Branches        ?        0
=======================================
  Hits            ?     3746
  Misses          ?     1777
  Partials        ?      286

Flag
Coverage Δ

unit
64.48% <58.33%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

/test mysql-test


Arduino compiler makes half-baked optimization

it seems the arduino compiler (and maybe C too) makes some smart optimization, trying to remove some messages and ports that are not used. So far, so good. The problem is that the associated declarations are removed, but those declarations are still called at some point in the code, causing compilation errors (xxx not declared).

I guess this is fixed, isn't it @Lyadis ? If so, close the issue

I hope so!


Test: Add Twitter unit test - it closes #123

Add unit tests for Twitter components. Closes #123

Codecov Report

Merging #176 into main will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #176   +/-   ##
=======================================
  Coverage   74.46%   74.46%
=======================================
  Files          76       76
  Lines         607      607
  Branches      109      109
=======================================
  Hits          452      452
  Misses        132      132
  Partials       23       23

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 47cce8c...85ac4a0. Read the comment docs.

Oh no, still fails. But there seemed to be more errors last night, while now we only get one single error.
https://app.circleci.com/pipelines/github/PaulieScanlon/mdx-embed/269/workflows/7722e777-deec-4dde-9850-b97b215efb70/jobs/926
FAIL  src/components/wikipedia/wikipedia.test.tsx
  ● Test suite failed to run

    ENOMEM: not enough memory, read

      at Object.<anonymous> (../../node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js:65:28)

Again, yarn test locally passes fine.

@ekafyi oh blast!
Ok, i think i might see the problem.
It's with the Circle config but everything i try seems to pass so i think what'll i do, is make a quick change to your branch and skip the tests... just temporarily, merge it in and then work off a new branch to try and resolve the Circle config but i'll be able to use your tests and as a proving ground...
also we can then merge this PR in case it's holding up your Hacktoberfest contributions.

@PaulieScanlon Just fetched and made a new branch and I noticed you fixed it in https://github.com/PaulieScanlon/mdx-embed/pull/178 . Bookmarking your fix in case I ever come across something like this in the future. :)


feat: add renderEnhance function

Provide rendering enhancement capability for data. When you are not satisfied with the current rendering situation and want to expand by yourself, renderenhance provides you with all possible attributes and data, which will be executed every time you get rendering, so you need to pay attention to the execution time and performance of renderenhance to avoid jamming.

为数据提供渲染增强能力，当你不满足于当前的渲染情况，想要自己动手进行扩展时，renderEnhance给你提供所有可能用到的属性和数据，在每次获取渲染的时候都会执行，所以需要注意renderEnhance的执行时间和性能，以免造成卡顿。

:tada: This PR is included in version 1.0.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Wrapping Aws-xray with gorilla mux

Hi,
We have used gorilla mux (https://github.com/gorilla/mux) in our codebase as following:
router := mux.NewRouter().StrictSlash(true)
api := router.PathPrefix("/routes").Subrouter()
api.Handle("/version", WrapMethodHandler(http.MethodGet, rest.HandlerVersion))
type MethodHandler map[string]http.Handler
func WrapMethodHandler(method string, fn func(w http.ResponseWriter, _ *http.Request)) MethodHandler {
return MethodHandler{
method: http.HandlerFunc(fn),
}
}
Please help us, to wrap this handler inside xray as https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-go-handler.html

Hi @continuum-ajay-sahani ,
You should be able to trace upstream HTTP call using something like this.
router := mux.NewRouter()
router.Handle("/", xray.Handler(xray.NewFixedSegmentNamer("newsegment"), HelloServer()))

In above example HelloServer() method is a function handler. So add any function handler method in place of
HelloServer() method.
Let me know if you have more questions.

In this code snippet, how to mention HTTP method type (GET, POST,etc) for the handler ?

I believe you should be able to mention it in the http handler code. In the above example HelloServer() is the http handler. Whenever this path ('/') is being hit it will call the http handler and perform operations like GET, POST etc. I believe you can review the example in this thread (https://github.com/aws/aws-xray-sdk-go/issues/238) to get more clear idea.


Some distributed .dylib files are damaged preventing program use.

Describe the bug
I downloaded the latest release of ASP (3.2.0) onto my mac (12.6.3 Monterey, but still an Intel mac), unpacked the tarball, and tried to run pc_align.  The OS threw up a series of dialogue boxes that indicated that libtbb.dylib and libGL.1.dylib were "damaged" and could not be opened.  I tried with the 2023-02-01 daily and got the same behavior.  While the dialogue boxes aren't helpful, the text sent to STDOUT has a little more info:
$> cd opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/bin/
$> ./pc_align -h
dyld[55738]: Library not loaded<EMAIL_ADDRESS>  Referenced from: '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libembree.2.dylib'
  Reason: tried: '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/oalexan1/miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/oalexan1/miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/oalexan1/miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/oalexan1/miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/3rdParty/lib/libtbb.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' (code signature in <3837B61A-C21F-3524-864E-1DDAD65CA501> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libtbb.dylib' not valid for use in process: library load disallowed by system policy)
Library not loaded<EMAIL_ADDRESS>  Referenced from: '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libisis7.1.0.dylib'
  Reason: tried: '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/oalexan1/miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/oalexan1/miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/oalexan1/miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/oalexan1/miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/3rdParty/lib/libGL.1.dylib' (no such file), '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' (code signature in <C6005C01-EEFD-397A-8635-F8F580E1D80C> '/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/libGL.1.dylib' not valid for use in process: library load disallowed by system policy)

Unfortunately, both of these libraries look like dependencies that are related to ISIS, which always makes me nervous.  Maybe we need to update our macOS build system?
Sadly, these errors means that I can't run ASP programs on my mac (good thing I also have access to a Linux system).
Looking at this huge block of text, the messages at first seem to indicate that maybe this is some mac gatekeeper nonsense ("not valid for use in process: library load disallowed by system policy"), but that's at odds with the "damaged" message.
However, farther down, there is this (carriage returns added):
'/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/libexec/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file),
'/Users/rbeyer/opt/StereoPipeline-3.2.1-alpha-2023-02-01-x86_64-OSX/lib/../../../../../miniconda3/envs/isis7/lib/libtbb.dylib' (no such file),
'/Users/oalexan1/miniconda3/envs/isis7/lib/libtbb.dylib' (no such file),

The rpath stuff has always mystified me in general, but does this mean that it is trying to find files way back up the directory chain in a very specific ISIS 7 miniconda3 directory, and that's the problem?  And also Oleg's home directory path there looks weird.  So is that something that didn't get cleansed properly in the build?
I suspect that there is something goofy with those two .dylib files in the distribution and that really is the problem, but when the system can't use those, it tries a variety of strategies to find alternate versions of those .dylib files which are functional.
If we can fix these libraries, great.  Otherwise, we should (sadly) stop offering the macOS tarball and force people to install via conda I guess?
Your Environment (please complete the following information):

OS: macOS 12.6.3 Monterey, but still an Intel mac
ASP Version: 3.2.0 but also 2023-01-02 daily build

Additional context
Add any other context about the problem here.

The 3.1.0 conda install (that I still have on my mac does), I haven't had the time to check the latest, but I'll get around to it.

Nope, conda install of 3.2.0 does not appear to work:
$> conda install stereo-pipeline==3.2.0
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: \
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

ResolvePackageNotFound:
  - llvm-openmp[version='15.0.6.*,>=15.0.6']

And it isn't clear what the remedy is.

That is odd. This package exists. See here: https://anaconda.org/conda-forge/llvm-openmp/15.0.6/download/osx-64/llvm-openmp-15.0.6-h61d9ccf_0.conda.
You can try to create a standalone env having this package only, to see if it really fails to get it. The command is:
conda create -n tmp_openmp llvm-openmp=15.0.6 -c conda-forge -y
Here's what I see:
The following NEW packages will be INSTALLED:
llvm-openmp        conda-forge/osx-64::llvm-openmp-15.0.6-h61d9ccf_0
If that works, you can try installing ASP using the precise env published at https://raw.githubusercontent.com/NeoGeographyToolkit/StereoPipeline/master/conda/asp_3.2.0_osx_env.yaml
You would need to fetch that, then, per the installation instructions in our doc, do:
conda env create -f asp_3.2.0_osx_env.yaml
As an alternative, this also worked for me:
conda create -n tmp_asp  stereo-pipeline==3.2.0 -c nasa-ames-stereo-pipeline -c usgs-astrogeology -c conda-forge -y
In the meantime I reinstalled ISIS and will force the nightly to rebuild from a clean slate, and see how it goes.

The latest build is up as well, after being given a dependency refresh and a wholesale rebuild. You can also try to fetch isis 7.1.0 in a stand-alone environment, to see if the problem stems from them.


Selection (soExpandRealNumbers option)

Highlighting similar terms bug when soExpandRealNumbers option is True.

Fix GetWordAtTextPosition.

Fixed.


Semantic info: Empty constraint list

Is your feature request related to a problem?
An empty constraint list can be removed.
Desired solution
Show an appropriate info.
Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
No response

:tada: This issue has been resolved in version 0.2.0 :tada:
The release is available on:

Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Constrain surface mask area calculation for Float32

Problem:

and eps(Float32) is 1.1920929f-7
Heisenbug, not always reproducible locally.

for now implemented a more explicit enforcement of max(x,0) in #272


check man pages

Some of the manpages are incomplete (synopsis) and many mention -r incorrectly.

Fixed as of 517973d


Snapshot restore throws UPnP error 402

Hi,
multi_zone_snap.py consistently fails if any of the Sonos devices is playing music - upon the restore, it gives a 402 error as follows:
Traceback (most recent call last):   File "./test2.py", line 84, in <module>     play_alert(   File "./test2.py", line 74, in play_alert     zone.snap.restore(fade=fade_back)   File "/usr/local/lib/python3.8/dist-packages/soco/snapshot.py", line 214, in restore     self.device.play_uri(   File "/usr/local/lib/python3.8/dist-packages/soco/core.py", line 121, in inner_function     return function(self, *args, **kwargs)   File "/usr/local/lib/python3.8/dist-packages/soco/core.py", line 642, in play_uri     self.avTransport.SetAVTransportURI(   File "/usr/local/lib/python3.8/dist-packages/soco/services.py", line 217, in _dispatcher     return self.send_command(action, *args, **kwargs)   File "/usr/local/lib/python3.8/dist-packages/soco/services.py", line 507, in send_command     self.handle_upnp_error(response.text)   File "/usr/local/lib/python3.8/dist-packages/soco/services.py", line 560, in handle_upnp_error     raise SoCoUPnPException( soco.exceptions.SoCoUPnPException: UPnP Error 402 received: Invalid Args from <IP_ADDRESS>
(with <IP_ADDRESS> being the Sonos devices that was playing at the time)
thanks!
Dan

Hi @Dan1001
I have tested out the example program in the SoCo release with Python 3.8 my system is S1 Sonos.
I can't make it fail whatever is playing or not!
Looking at the error you get it implies you are playing a stream / radio station - can you let me know what you are playing please. Also are you on S1 or S2 sonos? Assume you are using SoCo 0.20 ?
Maybe you could try the example in the SoCo release https://github.com/SoCo/SoCo/blob/master/examples/snapshot/multi_zone_snap.py
and see if that still fails for you.
Let us know how you get on and we can investigate further,
Cheers David

Many thanks. I'm guessing the difference is that my system is S2 Sonos.
My SoCo release is 0.20. Python 3.8.5, and I was playing a stream on Spotify, then testing using an unedited version of multi_zone_snap.py.
Thanks for the pointers to the other issues around 702. I tried the suggestion of amending "pause" to "stop" in line 178 of snapshot.py - that doesn't help.
Dan

Interesting. How many zones are you snapshotting, how many are grouped and how many are playing music?
Which zone is it failing on - the device - maybe its something special on that device.
Assume your alert is as in the example.
Can anyone else try the example on an S2 set up please?
Cheers David

I've tested, and get the error whether I run the alert (per the example) on all zones, or on individual zones one at a time (ungrouped). All the devices are One SLs, and all respond in the same way.
Some more testing: the error appears consistently when streaming from Spotify on either my iphone or macbook. However there is no error if streaming from youtube on iphone/macbook. And no error if Sonos itself is streaming from Spotify (i.e. using the Sonos app not the Spotify app).
Dan

Some more testing: the error appears consistently when streaming from Spotify on either my iphone or macbook. However there is no error if streaming from youtube on iphone/macbook. And no error if Sonos itself is streaming from Spotify (i.e. using the Sonos app not the Spotify app).

It sounds like you're streaming to the Sonos speakers using AirPlay?

Can anyone else try the example on an S2 set up please?
Cheers David

Working fine for me on S2, playing Spotify directly from Sonos.

It's Spotify Connect

@pwt, could you please try if you play Spotify from the Spotify app?

@pwt, could you please try if you play Spotify from the Spotify app?

I get the same error as you, if using Spotify Connect. However, I think that's what I'd expect when Sonos is being controlled by something external to the system. I'd expect the same limitation with AirPlay playback.

oh - perhaps this is inevitable, then!

Playing this way erros on S1 also.  Like queues started from Alexa or Google Home (cloud queues) they can't currently be restarted from SoCo. You can pause  them and play them, but once you stop or play an alert sound you loose connection with the original stream.
There are some options:

we can trap this stream and not raise an error -  but it will just not restart - as with other cloud queues. if you want to try it insert the following at line 121 in (indented same level as previous if)

        if self.media_uri.split(":")[0] == "x-sonos-vli":
            # playing from an external service (eg via Spotify connect)
            self.is_playing_cloud_queue = True

in you code you could pause this stream leave one player with it - alert on the others players then rejoin the other players to the preserved player and play. We could make this an addition to snapshot to have a "preserve cloud queue player" which would work for this and other cloud queues.

Welcome your thoughts or other ideas
Cheers David

I'm hitting this same issue now with Spotify Connect. I've tried the the line 121 addition suggestion above, but it still disconnects Spotify and fails to reconnect on restore. Any more progress since this time last year please?

@DPH, I'm hitting this same issue now with Spotify Connect. I've tried the the line 121 addition suggestion above, but it still disconnects Spotify and fails to reconnect on restore. Any more progress since this time last year please?

I'm not sure there is an acceptably clean solution to this use case.

Hi @peterwallhead, I think the only way you will resume Spotify Connect is if you use a lib that controls Spotify and that casts to Sonos. As said before if a queue is created outside of Sonos (Alexa, Spotify etc.) then Sonos has no knowledge of it and no ability to restart it. Please post any options you find as I think a lot of us are interested in making this work. Good luck, Cheers David

Ah, thanks @DPH! That's definitely helped my understanding of what's going on. I was focussing on controlling the Sonos device, but I now understand that I should be controlling Spotify instead in this instance.
Basically I'll just need to do the following, right?

Snapshot the current Spotify Connect state (and then stop the music), all via Spotify
Take control of the device using SoCo (and play the required alert/message)
Restore the Spotify state by reconnecting/recasting to the device via Spotify

Will post here if/when I find a workable solution.

Sounds right to me. Will be great if you can get that combination working.
Happy to test things or help if you find some options.
Cheers David
On Fri, 10 Dec 2021 at 08:03, Peter Wallhead @.***>
wrote:

Ah, thanks @DPH https://github.com/DPH! That's definitely helped my
understanding of what's going on. I was focussing on controlling the Sonos
device, but I now understand that I should be controlling Spotify instead
in this instance.
Basically I'll just need to do the following, right?

Snapshot the current Spotify Connect state (and then stop the
music), all via Spotify
Take control of the device using SoCo (and play the required
alert/message)
Restore the Spotify state by reconnecting/recasting to the device
via Spotify

Will post here if/when I find a workable solution.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SoCo/SoCo/issues/761#issuecomment-990715484, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACIDKNJRJHCOK43LTROITLUQGX3ZANCNFSM4T5I66KQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

This thread got locked, so I'll reference it from this end: https://github.com/home-assistant/core/issues/45050
Tl;dr: Home Assistant is also affected by this issue when restoring a snapshot taken while a Spotify stream was playing.


SubscriptionClient.subscriptions.list doesn't return any tags

My basic use is as follows:
client = SubscriptionClient(creds)
subs = c.subscriptions.list()
for sub in subs:
    print(sub)

For each subscription returned, all have
'tags': None
I'm using azure-mgmt-resource and the model version (2019-11_01). If it helps, the method subscriptions.get(sub_id) does return tags successfully.

Thank you for reporting @HarryBrooks , we will investigate ASAP!

Done some digging our end and have discovered it appears to be an issue with permissions across the API as a whole rather than the python sdk. I'll close this and open an issue in the correct area. Thanks!