Failing test case from the web version

Feel free to close immediately, I didn't search if the bug was already submitted.
I just played with the web version of CavalierContours and found a failing test:
(80.0, 90.0, 0.374794619217547),
(231.5, -278.0, 0.0),
(230.0, 0.0, 1.0),
(320.0, 0.0, -0.5),
(280.0, 0.0, 0.5),
(390.0, 210.0, 0.0),
(280.0, 120.0, 0.5)], 3.0) =>
                    [PlineProperties::new(11, 0.0, 1563.689560505266, 66.99239238371496, -273.0909692941639,<PHONE_NUMBER>8912127,<PHONE_NUMBER>5960901)]

with mode Offset , Offset 3, Offset count 50, Handle Self Intersects activated.
Thanks for offering this project!

You closed this issue already, I haven't looked at it, is this an actual bug?

I think that my path was then self-intersecting and I guess that the offset would have been in one of the loop if the loop were large enough.


Spacing on News article template needs addressing

Looking at the news article the spacing between components and components within the text module seems to be duplicated or even trebled. The spacing needs to reflect the spacing reference on TOPIC page template between components.
Reference page link below:

Double space between Ingress and text module.
Seems to be triple spacing Text module and Iframe and iframe to Links.
Seems to be double spacing within the text module between text and factbox. The correct spacing is shown between text and image.

https://web-global-development-equinor-web-sites-dev.c2.radix.equinor.com/api/preview?type=news&locale=en&slug=%2Fnews%2Fnick-testing-the-layout&secret=jlskdjfkj4323lk4jlkjlksdf

@NickHaggerty1 @meols This is ready for a second review.

@NickHaggerty1 - can you please check this one?

@padms Looks better. thanks


Handles inexistent npm module exception properly

Hey @natecavanaugh, this should fix the issues when trying to locate themes or themelets from npm registry. As far as I can tell, some dependencies needed to be updated and some APIs changed.
All tests are passing locally, we can use this to try to figure out the CI issues as well.
Finally, as yoy can see, I'm sending this to the develop branch. This is the git flow we're following here:

master contains the code of the latest published version on npm
develop contains the current work in progress
We use a merge commit to merge into develop.
When we want to release, we send a PR to master from develop and if all tests pass, then we merge and release from master

@jbalsas Thanks for the heads up on the git flow process. We used it on the old Lexicon repo, but since it's the default, it will let me update locally so I make sure I'm on the right version :)
About the CI changes, I think things should be working (at least the latest build went through after some updates to eliminate the failing test and prettier formatting.
Re: the changes here, they look good to me, though just one quick question:
Since this uses features that will break in the maintenance LTS of node (async/await), should be specify a minimum node version in package.json? Mainly, I'd rather people get the hint that the version of node required needs to be higher when they go to install rather than it installing and reporting errors later on.
Just a thought though :)
Everything else, LGTM!

Hey @natecavanaugh, that's a good point!
We ran the frontend training last week, and it turns out that this already won't run in node<6, I think, so it's definitely worth updating it.
Can you think of a way to use it so we can limit how high a node version we might need? I tried simple promises but didn't seem to work. 🤔

@jbalsas Wierd... I was under the impression that await (implicitly) relied on Promises already.
Can you go into detail as to why it didn't work with just plain promises?
Either way, I think node < 6 shouldn't even be a concern (though I think the package.json should at least error it quickly).
Thanks again for all of this help!

Nothing, really, I guess I was just tired... I tried promises, but used callback style instead of promise catch 😂
I've updated it and added node>=8.0.0 to the engines property. I think we might be able to relax it to 6.0, but based on how long it's going to stay around and being 8.x.x the current active LTS version, I think it should be fine.

Hey @natecavanaugh, CI looks good, so I'm going to shamelessly auto-merge since you okey'd it before... but please, review it if you have a chance so we can fix anything that I might've done wrong here :)
Thanks for the help!


preclick fires on dragend

debug/map/markers.html

click on marker (got popup)
drag map
popup closed when drag ended (wrong)

Before new event model popup is still opened after drag.
It's happed because preclick fired on drag end. preclick fired because we have click event from browser.
_fireDOMEvent checked current state in https://github.com/Leaflet/Leaflet/blob/cdb9ce0beb70705fb31b79fdc9376f72c42dc596/src/map/Map.js#L683
May be same check must be in _handleDOMEvent or move preclick firing to _fireDOMEvent?

Confirmed. I'll have a look if nobody else is on it.


bug: recreating a wagmi client with a different connectors list breaks the connection flow

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.12.10
Current Behavior
If you recreate a Wagmi client by using createClient with a different set of connectors, it disrupts the connection flow, requiring a page refresh to display the connected wallet address after connecting to it.
https://user-images.githubusercontent.com/8983736/236782094-eb9814e2-40e5-4a07-8363-8631c54eff20.mov
Expected Behavior
The wallet address should be visible immediately after connecting to it.
Steps To Reproduce
Attached a repository with a reproducible code below.
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
https://github.com/bulgakovk/connect-button-PoC
Anything else?
For an explanation as to why it's necessary to recreate a Wagmi client, please refer to the Wallet Standard connector request. Essentially, Standard Wallets possess an asynchronous registration (injection) API, which allows for the wallets list to be updated dynamically, and as a result, the Wagmi client should be recreated.

Thanks for reporting. This issue is temporarily closed due to lack of information. Please provide a minimal reproducible example that only uses wagmi without RainbowKit and reopen this issue.


TST: fix ultra-slow ttest permutations test

This test was taking 24 seconds and was also consistently crashing an Azure worker on the scipy-wheels repo.
There is no good reason to run that many iterations; reduce it to something more sensible. That should also make it runnable on 32-bit.
Closes gh-13540

This misses the point of the test, which was to show agreement between the permutation and asymptotic tests. A better solution might be to make it XSLOW. But merging to avoid those failures.

A better solution might be to make it XSLOW. But merging to avoid those failures.

I don't think so, a single test running for half an hour is (almost) never the right answer. And a 4x tolerance bump doesn't all of a sudden change what the test does completely.


How Can I Run IOS app, I did not find .xcodeproj file in sample projects

Hello,
Thanks a lot for this amazing project.
How Can I Run IOS app, I did not find .xcodeproj file in sample projects.
I investigated this repo, "compose-multiplatform-ios-android-template"
Is it different approach from urs?

PreCompose sample still using "old" Compose iOS project structure, so you'll need to run ./gradlew :sample:todo:ios:iosDeploySimulatorDebug in order to run sample iOS project.
I do have a plan on upgrading to new Compose iOS project structure, but currently I do not have the time to do that, but PreCompose's setup should be not that different for iOS.

Thank you so much, I am trying to implement with new IOS project structure.
I just faced " java.lang.IllegalStateException: No StateHolder provided" exception running on Android

Sorry my fault, I replaced setContent with "moe.tlaster.precompose.lifecycle.setContent".


Hybrid FxRapidHasher variant

Combining the best of fxhash and rapidhash into the ultimate memory-safe high-performance platform-independent hash function.

I'm wondering if you've considered using a parallelized variation on fxhash for fast hashing even on somewhat longer data?


Use ahash for IndexMap and IndexSet hasher

Summary
The ahash hasher offers better performace as a drop in replacement for the stdlib hash algorithm. This is a large reason we use the hashbrown crate for our HashMap type in Qiskit (along with rayon support). The indexmap crate doesn't use ahash by default however, so we typically switch to it anywhere we use IndexMap or IndexSet to match the lookup performance of hashbrown in places where we need to preserve insertion order. However, there were a couple of spots where we missed this in the rust code, this commit corrects these oversights.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
21 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.01%) to 89.725%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
94.02%

crates/qasm2/src/lex.rs
2
91.48%

crates/qasm2/src/parse.rs
18
96.69%

Totals

Change from base Build<PHONE_NUMBER>6:
-0.01%

Covered Lines:
67363

Relevant Lines:
75077

💛  - Coveralls


Remove usage of ajaxDie

Questions
Answers

Description?
ajaxDie is deprecated and ajaxRender should be used instead. Related to https://github.com/PrestaShop/PrestaShop/pull/35283.

Type?
refactor

BC breaks?
no

Deprecations?
no

Fixed ticket?

Sponsor company

How to test?

Does not need any QA, the methods are the same.

Hello @Hlavtox,
Some checks were not successful, can you look at this?
Thanks!

@paulnoelcholot It's ready, just a random fail. :-)

@PrestaShop/qa-functional Guys can I get a QA on this pls?


Incorrect links to project landing page

Hi!
Links to project landing page are incorrect; both missing www subdomain.
Current links in README.me and  About point to https://sunlit.io as opposed to https://www.sunlit.io.

Thanks! The DNS was out of date, so I fixed that and it should fix the URLs too so both versions work.


ERROR: Download failed: 'YoutubeDL' object has no attribute '_allow_colors'

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
I'm using yt-dlp as a plugin for Gpodder, and since the 2023.06.21 update getting the error mentioned on the title when I try to download a media.
I have tracked down the cause of the error to following line:
self.report_warning('Overwriting params from "color" with "no_color"')
It appears down the call chain of report_warning function it is using self._allow_colors before it is initialized.
Note: initialization of self._allow_colors happens on the line 630.
I was able to solved the my issues by changing the report_warning to write_debug, but didn't want to send a patch for this since I am not sure if that was the correct way to solve this issue.
P.S.
I acknowledge to have checked some options on the issue template to get it to go through, but the results provided is not exactly by following the steps mentioned.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
1688712184.665647 [gpodder.download] ERROR: Download failed: 'YoutubeDL' object has no attribute '_allow_colors'
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/gpodder/download.py", line 910, in run
    headers, real_url = downloader.retrieve_resume(self.tempname, self.status_updated)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/gpodder/extensions/youtube-dl.py", line 116, in retrieve_resume
    res = self._ytdl.fetch_video(info, opts)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/gpodder/extensions/youtube-dl.py", line 355, in fetch_video
    with youtube_dl.YoutubeDL(opts) as ydl:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/yt_dlp/YoutubeDL.py", line 618, in __init__
    self.report_warning('Overwriting params from "color" with "no_color"')
  File "/usr/lib/python3.11/site-packages/yt_dlp/YoutubeDL.py", line 1027, in report_warning
    self.to_stderr(f'{self._format_err("WARNING:", self.Styles.WARNING)} {message}', only_once)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/yt_dlp/YoutubeDL.py", line 1015, in _format_err
    return self._format_text(self._out_files.error, self._allow_colors.error, *args, **kwargs)
                                                    ^^^^^^^^^^^^^^^^^^
AttributeError: 'YoutubeDL' object has no attribute '_allow_colors'

I'll fix this, but why are you passing both color and no_color anyway?

Thanks for looking into this.

I'll fix this, but why are you passing both color and no_color anyway?

This happens when I use yt-dlp as extension for Gpodder, not sure what's reason behind it sending the color parameters.


Decimal serialization

This should also fail if Math.round(value) < -999999999999:
https://github.com/Jxck/structured-field-values/blob/master/index.js#L331
Also,<PHONE_NUMBER>99.1 fails to serialize, when it should pass:
If input_decimal has more than 12 significant digits to the left  of the decimal point after rounding,

it's already fixed during update to v3
https://github.com/Jxck/structured-field-values/blob/54cfea375be670cfcb873b6c0c4c4fc57e642bc9/index.js#L423
thanks


Add monitoring for rabbitmq

Need to know about stuck queues etc.

closing this as a duplicate of #130


Prettier to run on local pre-commit

ref #27
As a developer, I want prettier to run on every commit locally with the pre-commit hook, so that I can be sure that I'm submitting properly formatted code.
DoD:

commit formatted code changes by running prettier against the entire codebase (@wenzowski still a bit unclear as to when this step needs to happen, should it be a separate issue?)
prettier runs on the pre-commit hook on every commit

commit formatted code changes by running prettier against the entire codebase
I'd say this CI guardrail is configured.

Combined with https://github.com/button-inc/digital_marketplace/issues/27


Change enum member lint rule to camelCase

I left the enum name at PascalCase but changed the enum member to camelCase. I think this is what we intended.

PR Checklist

[x] Verify if the change requires a changeset. See CONTRIBUTING.md
[x] Link to the respective task if one exists: COM-889

Closed in favor of https://github.com/vivid-planet/comet/pull/2266


Great choice of combinations

https://github.com/user-attachments/assets/6b4a4d6e-cff4-4a9f-adc1-8434e4b26c05

Thank you. This is the wildest issue with perfect video. It says This horse is a multidimensional crazy animal. 🎠🎨

Thank you. This is the wildest issue with perfect video. It says This horse is a multidimensional crazy animal. 🎠🎨

thank you as well. This is the first time I found a fitting place to put the song I wrote.


python311Packages.cyclonedx-python-lib: 7.3.2 -> 7.3.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.cyclonedx-python-lib is: Python library for generating CycloneDX SBOMs
meta.homepage for python311Packages.cyclonedx-python-lib is: https://github.com/CycloneDX/cyclonedx-python-lib
meta.changelog for python311Packages.cyclonedx-python-lib is: https://github.com/CycloneDX/cyclonedx-python-lib/releases/tag/v7.1.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.1.0 with grep in /nix/store/kzicrf708gi8fsx75j2f16ybw07z4vsd-python3.11-cyclonedx-python-lib-7.1.0
found 7.1.0 in filename of file in /nix/store/kzicrf708gi8fsx75j2f16ybw07z4vsd-python3.11-cyclonedx-python-lib-7.1.0

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

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
checkov
pip-audit
python311Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kzicrf708gi8fsx75j2f16ybw07z4vsd-python3.11-cyclonedx-python-lib-7.1.0 \
  --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 python311Packages.cyclonedx-python-lib https://github.com/r-ryantm/nixpkgs/archive/c7400ffdb0b29b94ae2370f9a92c9f0f84fc93ce.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c7400ffdb0b29b94ae2370f9a92c9f0f84fc93ce#python311Packages.cyclonedx-python-lib

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kzicrf708gi8fsx75j2f16ybw07z4vsd-python3.11-cyclonedx-python-lib-7.1.0
ls -la /nix/store/kzicrf708gi8fsx75j2f16ybw07z4vsd-python3.11-cyclonedx-python-lib-7.1.0/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

4 packages failed to build:

checkov
checkov.dist
pip-audit
pip-audit.dist

4 packages built:

python311Packages.cyclonedx-python-lib
python311Packages.cyclonedx-python-lib.dist
python312Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib.dist

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.cyclonedx-python-lib is: Python library for generating CycloneDX SBOMs
meta.homepage for python311Packages.cyclonedx-python-lib is: https://github.com/CycloneDX/cyclonedx-python-lib
meta.changelog for python311Packages.cyclonedx-python-lib is: https://github.com/CycloneDX/cyclonedx-python-lib/releases/tag/v7.3.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.3.1 with grep in /nix/store/40j568v0ana3c2f6fqiilzcfcy2vhscx-python3.11-cyclonedx-python-lib-7.3.1
found 7.3.1 in filename of file in /nix/store/40j568v0ana3c2f6fqiilzcfcy2vhscx-python3.11-cyclonedx-python-lib-7.3.1

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

checkov
pip-audit
python311Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/40j568v0ana3c2f6fqiilzcfcy2vhscx-python3.11-cyclonedx-python-lib-7.3.1 \
  --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 python311Packages.cyclonedx-python-lib https://github.com/r-ryantm/nixpkgs/archive/b04d727cc795d7b83d93decebd27464b2d322350.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b04d727cc795d7b83d93decebd27464b2d322350#python311Packages.cyclonedx-python-lib

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/40j568v0ana3c2f6fqiilzcfcy2vhscx-python3.11-cyclonedx-python-lib-7.3.1
ls -la /nix/store/40j568v0ana3c2f6fqiilzcfcy2vhscx-python3.11-cyclonedx-python-lib-7.3.1/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

4 packages failed to build:

checkov
checkov.dist
pip-audit
pip-audit.dist

4 packages built:

python311Packages.cyclonedx-python-lib
python311Packages.cyclonedx-python-lib.dist
python312Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib.dist

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.cyclonedx-python-lib is: Python library for generating CycloneDX SBOMs
meta.homepage for python311Packages.cyclonedx-python-lib is: https://github.com/CycloneDX/cyclonedx-python-lib
meta.changelog for python311Packages.cyclonedx-python-lib is: https://github.com/CycloneDX/cyclonedx-python-lib/releases/tag/v7.3.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.3.2 with grep in /nix/store/fyf3ab6i25nabkm9rdkin3qfxr43sjxr-python3.11-cyclonedx-python-lib-7.3.2
found 7.3.2 in filename of file in /nix/store/fyf3ab6i25nabkm9rdkin3qfxr43sjxr-python3.11-cyclonedx-python-lib-7.3.2

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

checkov
pip-audit
python311Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fyf3ab6i25nabkm9rdkin3qfxr43sjxr-python3.11-cyclonedx-python-lib-7.3.2 \
  --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 python311Packages.cyclonedx-python-lib https://github.com/r-ryantm/nixpkgs/archive/70491e706314337be91471d240baf4d66b9b9798.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/70491e706314337be91471d240baf4d66b9b9798#python311Packages.cyclonedx-python-lib

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fyf3ab6i25nabkm9rdkin3qfxr43sjxr-python3.11-cyclonedx-python-lib-7.3.2
ls -la /nix/store/fyf3ab6i25nabkm9rdkin3qfxr43sjxr-python3.11-cyclonedx-python-lib-7.3.2/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

4 packages failed to build:

checkov
checkov.dist
pip-audit
pip-audit.dist

4 packages built:

python311Packages.cyclonedx-python-lib
python311Packages.cyclonedx-python-lib.dist
python312Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib.dist

Maintainer pings
cc @fabaff for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.cyclonedx-python-lib is: Python library for generating CycloneDX SBOMs
meta.homepage for python311Packages.cyclonedx-python-lib is: https://github.com/CycloneDX/cyclonedx-python-lib
meta.changelog for python311Packages.cyclonedx-python-lib is: https://github.com/CycloneDX/cyclonedx-python-lib/releases/tag/v7.3.4
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.3.4 with grep in /nix/store/2wr0l8k480mwrgilq53qdq63syjsikzq-python3.11-cyclonedx-python-lib-7.3.4
found 7.3.4 in filename of file in /nix/store/2wr0l8k480mwrgilq53qdq63syjsikzq-python3.11-cyclonedx-python-lib-7.3.4

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

checkov
pip-audit
python311Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2wr0l8k480mwrgilq53qdq63syjsikzq-python3.11-cyclonedx-python-lib-7.3.4 \
  --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 python311Packages.cyclonedx-python-lib https://github.com/r-ryantm/nixpkgs/archive/2f38d589d4a9344d07cf4bc816cb0b99496d461b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2f38d589d4a9344d07cf4bc816cb0b99496d461b#python311Packages.cyclonedx-python-lib

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2wr0l8k480mwrgilq53qdq63syjsikzq-python3.11-cyclonedx-python-lib-7.3.4
ls -la /nix/store/2wr0l8k480mwrgilq53qdq63syjsikzq-python3.11-cyclonedx-python-lib-7.3.4/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

8 packages built:

checkov
checkov.dist
pip-audit
pip-audit.dist
python311Packages.cyclonedx-python-lib
python311Packages.cyclonedx-python-lib.dist
python312Packages.cyclonedx-python-lib
python312Packages.cyclonedx-python-lib.dist

Maintainer pings
cc @fabaff for testing.


melonDS: 0.9.5-unstable-2024-04-18 -> 0.9.5-unstable-2024-05-05

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for melonDS is: Work in progress Nintendo DS emulator
meta.homepage for melonDS is: https://melonds.kuribo64.net/
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 0.9.5-unstable-2024-05-05 in filename of file in /nix/store/i5wwzjfmsh14y8gxnl1blchpsyph5zdy-melonDS-0.9.5-unstable-2024-05-05

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

melonDS

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/i5wwzjfmsh14y8gxnl1blchpsyph5zdy-melonDS-0.9.5-unstable-2024-05-05 \
  --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 melonDS https://github.com/r-ryantm/nixpkgs/archive/9852c83fe37d389f0c07d3ba7539c62cf87c8da8.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9852c83fe37d389f0c07d3ba7539c62cf87c8da8#melonDS

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/i5wwzjfmsh14y8gxnl1blchpsyph5zdy-melonDS-0.9.5-unstable-2024-05-05
ls -la /nix/store/i5wwzjfmsh14y8gxnl1blchpsyph5zdy-melonDS-0.9.5-unstable-2024-05-05/bin

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

1 package built:

melonDS

Maintainer pings
cc @AndersonTorres @artemist @benley @SCOTT-HAMILTON for testing.

@ofborg build pkgsCross.mingwW64.melonDS


Changes property options to support converter

Fixes #264
Changes type to be only a hint to the converter option which has the previous type functionality, an object with toAttribute and fromAttribute or just a function which is fromAttribute. In addition to the value these functions now also get the property's type.
Also provides a default converter that supports Boolean, String, Number, Object, and Array out of the box.
In addition, numbers and strings now become null if their reflected attribute is removed.

In addition, numbers and strings now become null if their reflected attribute is removed.

Shouldn't numbers and strings become undefined if they are removed? Changing them to null means that defaults set by the component will now be bypassed:
function func(foo='bar'){
  console.log(foo);
}

func(null); // null
func(undefined); // 'bar'


Subsequent compilations with compiler debugging flags doesn't work.

Version(s)
0.1.8
Describe the bug
Running scala-cli compile --scalac-option -Yprint-pos-syms -Xprint:typer Test.scala -S 3.2.0-RC1
Multiple times does not print trees in subsequent launches. Probably due to some caching which shouldn't work in that case.
To Reproduce
Prepare any Scala file and run:
scala-cli compile --scalac-option -Yprint-pos-syms -Xprint:typer Test.scala -S 3.2.0-RC1
Expected behaviour
Print trees again especially as I explicitly provide compile command instead of just running the app.

It seems that's somehow expected, and not specific to Scala CLI. On subsequent compile calls, nothing gets recompiled thanks to incremental compilation, so no tree is printed. We get the same thing from sbt for example:
sbt
[info] welcome to sbt 1.6.2 (AdoptOpenJDK Java <IP_ADDRESS>)
[info] loading project definition from ./project
[info] loading settings for project tmp from build.sbt ...
[info] set current project to tmp (in build file:./)
[info] sbt server started at local://~/.sbt/1.0/server/2c03047191bbb9a53e81/sock
[info] started sbt server
sbt:tmp> compile
[info] compiling 1 Scala source to ./target/scala-3.2.0-RC1/classes ...
[info] [[syntax trees at end of                     typer]] // ./src/main/scala/Foo.scala
[info] package <empty> {
[info]   final lazy module val Foo: Foo = new Foo()@@(Foo=
[info]     ./src/main/scala/Foo.scala:<0..0>
[info]   )
[info]   final module class Foo() extends Object() { this: Foo.type =>
[info]     def main(
[info]       args: Array[String]@@(args=
[info]         ./src/main/scala/Foo.scala:<24..24>
[info]       )
[info]     ): Unit = println("Helloz")@@(main=
[info]       ./src/main/scala/Foo.scala:<19..19>
[info]     )
[info]   }@@(Foo$=
[info]     ./src/main/scala/Foo.scala:<7..7>
[info]   )
[info] }
[success] Total time: 6 s, completed 27 juin 2022 à 14:14:16
sbt:tmp> compile
[success] Total time: 0 s, completed 27 juin 2022 à 14:14:18

As a workaround, disabling Bloop use with --server=false disables incremental compilation too, and makes Scala CLI print the tree upon every call.

Or users can run clean command and then re-run scala files:
scala-cli clean .
scala-cli compile --scalac-option -Yprint-pos-syms -Xprint:typer Test.scala -S 3.2.0-RC1


Webpack stucks in Docker Container

I created a project using
npx create-strapi-app my-project --quickstart
created a Dockerfile:
FROM strapi/base

WORKDIR /srv/app

COPY ./package.json ./
COPY ./yarn.lock ./

RUN yarn install

COPY . .

ENV NODE_ENV production

RUN yarn build

EXPOSE 1337

CMD ["yarn", "start"]

Now i'm trying to build the Docker Image, but it stucks always when building the webpack.
When I manually start yarn build in the container, then i can see that it's stuck at 90% processing chunk assets.
My container has 4GB Ram and 2 cpus attached. I can see that its using 100% SSD Read the whole time.
Do you have any suggestions?

Do you have Docker trying run strapi/base image on linux/arm64/v8?

running webpack the first time can take a lot of time - on aws the build process inside the codepipeline took mostly ~2-4min. this would also the reason why your ssd is ~100% all the time... so maybe just wait for a longer time..? how long did you wait?

I created a project using
npx create-strapi-app my-project --quickstart
created a Dockerfile:
FROM strapi/base

WORKDIR /srv/app

COPY ./package.json ./
COPY ./yarn.lock ./

RUN yarn install

COPY . .

ENV NODE_ENV production

RUN yarn build

EXPOSE 1337

CMD ["yarn", "start"]

Now i'm trying to build the Docker Image, but it stucks always when building the webpack.
When I manually start yarn build in the container, then i can see that it's stuck at 90% processing chunk assets.
My container has 4GB Ram and 2 cpus attached. I can see that its using 100% SSD Read the whole time.
Do you have any suggestions?

I had this issue running Docker on a M1 chip. Later I added platform to the Dockerfile and also if it took more than 560 seconds it worked. I also used strapi/base instead of strapi/base:14-alpine
This fix worked for me:
FROM --platform=linux/amd64 strapi/base as base

WORKDIR /usr/src/app
#COPY ["package.json", "yarn.lock", "./"]
EXPOSE 1337

FROM base as builder
COPY ["package.json", "yarn.lock", "./"]
RUN yarn install
COPY . /usr/src/app
RUN yarn build

FROM base as release
ENV NODE_ENV=production
USER node
COPY --chown=node:node --from=builder /usr/src/app/node_modules ./node_modules
COPY --chown=node:node --from=builder /usr/src/app/build ./build
COPY --chown=node:node . /usr/src/app
CMD ["yarn", "start"]


lxcfs mounted cgroup mgr causes docker run failure with user-namespace enabled daemon

There have been several reports of "container command not found" errors when attempting to run containers on a user-namespaces enabled Docker daemon.
Given the lack of clarity in the error message, there could be multiple issues hidden by this generic error, but I was able to reproduce this myself in a newly installed Ubuntu 16.04 VM that happened to install the lxc components by default (which I don't have installed on a physical 16.04 system).
In this particular case, the existence of the cgroup mounts for lxcfs in /proc/self/mountinfo is causing the issue, as the codepath in libcontainer for GetAllPids() will use a parsed version of this information to find cgroup root paths, and in the case where it finds the 'lxcfs' variant, will try an os.Stat of this root path, and get an EPERM given the process is inside a user namespace at this point, and has no read access to that path.  Specifically the code here in libcontainer/cgroups/fs/apply_raw.go performs the syscall which gets permissions failures.
I'm not sure why I don't get this failure when using runc by itself (on the same system) so I'm opening the issue in docker repo first until we resolve why.
I can get the error to disappear by stopping the lxcfs service and unmounting the cgroup mounts under /run/lxcfs. I did find when searching that @hallyn said there is a correct path rooted under /var/lib for the cgroup hierarchy instead of trying to look at /run/lxcfs, but in general I guess I'm curious if we (Docker engine) should be trying to use the non-lxcfs cgroup mounts that already exist and ignore the lxcfs? At this point I'm at the end of my cgroup knowledge, so I'll let others tell me :)

This is also causing an issue for libvirt.  As I've mentioned in
https://github.com/lxc/lxcfs/issues/123 lxcfs could start doing the
cgmanager trick of running in a custom rootfs in a ms_private
namespace to hide those mounts, but that does complicate things.

Should be fixed by https://github.com/lxc/lxcfs/pull/124.

I'm going to close this as there aren't any code changes in Docker necessary if lxc has solved the issue. Of course, until distros get an updated lxc this issue might appear from time to time, but hopefully this issue can be informational to those still hitting the problem until the lxc fix is fully propagated to users.

For posterity and those who may come across this in the future, here's some information on handling the clash until LXC updates are available in your distro or the next release: https://gist.github.com/estesp/e37b06e51384fa0ad6067af42a693925

Removal of lxcfs and other tools is not required.
We have released lxcfs 2.0.3. It's available for Ubuntu 16.04. For other Ubuntu releases the PPA https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxcfs-stable can be used. For other distros the new source is available at https://launchpad.net/ubuntu/+source/lxcfs/2.0.3-0ubuntu2.

Thanks @brauner ; had no idea there would be a new release so soon. It is still not in the 16.04 officially released repos yet (just checked), but as soon as it is, I will update my gist pointing to the update and mention that for other distros/platforms, look for the 2.0.3 release update or get it from the URLs you provided.

Somewhat related but I can't seem to use this feature when it involves another mounted drive.
Using the PPA with lxcfs 2.0.3 and docker service ExecStart=/usr/bin/dockerd -H fd:// --userns-remap=Default works under the default /var/lib/docker directory. However my SSD doesn't have that much space so I tried using the --graph parameter for docker to store the files in another drive.
Using the following:
ExecStart=/usr/bin/dockerd -H fd:// --userns-remap=Default --graph /media/user/somedrive/docker
Gives me the following error when I do a docker run --rm hello-world command.
docker: Error response from daemon: oci runtime error: rootfs_linux.go:42: preparing rootfs caused "permission denied".
docker folder is owned by root, is this permission related or another bug?

@CRTX : that is a permission bug because of more limited permissions/access to an existing directory in the provided path to --graph. Would you mind opening a new issue for that? The question will be do we want to (and will users accept) the Docker daemon changing permissions on an existing path for (root dir) access to work via a user namespaced process?


Branch planner doesn't use changed variables in branch

User stories

[ ] As a Terraform Controller user, I want to be able to receive a comment notifying me of all relevant changes I’ve made to my Terraform variables, so that I receive a complete set of information.
[ ] As a Terraform Controller user, I want to be able to receive a comment notifying me of all relevant changes to my Terraform HCL, so that I receive a complete set of information.

Acceptance Criteria

After a Terraform plan run on all of my clusters, I want to see references in the comment to the changes I made in the branch in the PR.
The produced output enables me to identify which TF generated the plan via a confirmation in the resulting plan, instead of saying “no changes.”
I don’t receive feedback about pods that aren’t affected by my change.
Need to confirm that if I change a variable in main and push the change, that I will see a change in TF if I use TF runner without the branch planner. (QQ: Does this already work?)

According to this issue, the TF-controller branch planner does not support changing a variable to run the plan output in a PR.
There are 2 cases that result in changes to terraform managed objects:

A change to the Terraform HCL
A change to the Terraform variables

Modifying the HCL is supported by the branch planner.
Modifying the variables is not supported by the branch planner.
In order for the branch planner to be a complete feature, then both of these cases need to be supported by the planner.
If this is not the case, then the usefulness of the branch planner is considerably reduced and this feature is not complete.
Original comment from community member
When changing the vars block in a Terraform resource in a branch, those changes are not reflected in ephemeral, PR-specific Terraform resource. This means that I might change some variables only and I get a comment in the PR saying No changes are detected.

Oh you've filed it. Thank you so much @cybercyst

@chanwit thanks for everyone's hard work on it!
One more piece of context, we also use a base Terraform definition and then use Kustomize (from Flux) to change the variables and workspace for each environment

Thank you for sharing that @cybercyst
We unfortunately don't support that use case yet in the Branch Planner v0.16.0-rc.2. Will investigate more on how should we support the TerraformCR change in the Branch Planner. The current architecture doesn't allow that.

@chanwit questions that came up in my chat with @madAndroid about this issue:

Instead of running a change for all the TF resources when I push a change to a branch, can I restrict a run to only the list of files that I’m pushing to Git/individual and related resources affected by the change?
Why would I want to see changes in other areas of my codebase?
Could you not filter by changes by path within the Git repo, and then the changes are set in the PR to only surface the relevant files? Right now the diff surfaces many things that aren’t in the PR/related. Jenkins only includes what you expect.

Talking to @squaremo and we've distilled the request in this way:
Scenario: Person has a Git repo synced by Flux and there's a TF object. Flux applies the object to the cluster. TF-controller takes over and runs the program. User wants TF-controller to note a change to the Terraform definition, say "I see a change," and make a preview of that.
Problem: This isn't what branch planner does now, and Flux doesn't do it, either. Flux doesn't go looking for branches saying, "I wonder if the user wants this to be applied." But if anything, it would be Flux's job to take care of this, not TF-Controller's.
Proposed resolution: Closing this as out of scope.
cc @darrylweaver @madAndroid

Closing based on previous comment.


fix: correct lua autocmd API usage

Current example will match all "User" events.
see also: https://github.com/neovim/neovim/issues/25517

Hi, @llllvvuu
please fix the UT event_spec.lua.
You may need to install these dependencies to testing in local machine (please use ubuntu/macos):

luarocks
https://github.com/notomo/vusted

I think we can use nvim_exec_cmd for higher version nvim, for v0.6 we can use <nomodeline>

hi, @llllvvuu
I temporarily revert this PR, since I want to merge it after I test it.
I think when users upgrade this patch, but their autocmd group still remains:

I am not sure if they can receive the new events?
because I don't want this plugin suddenly break users experience.
I will do some backward-compatible testing on your patch. would you please submit this PR again?
＞ sorry I am still not experienced when working with others, so makes this issue.

I am not sure if they can receive the correct events?

Yes, it will be fine.

would you please submit this PR again?

No problem, will do


Support list of blocks in addition to block ranges

Allow blocks to be passed in as a list in addition to block ranges, perhaps as comma separated list
I'll make a pass at adding this today, just filing issue for visibility

this should already work, as a space separated list
cryo txs --blocks 16000000 16000001 16000002

huh not sure why i was getting parsing error, will check

Found the issue, PR'd here https://github.com/paradigmxyz/cryo/pull/14


drivers: watchdog: Make SOC reset as an option in counter watchdog

When using watchdog which doesn't support callbacks (e.g. STM32 IWDG) it's very useful to have counter based watchdog with shorter timeout. This way we can gather useful information before IWDG resets SOC.
In above case it's usually not desired to reset SOC when counter watchdog is triggerd, because we can lose information about reset cause. For example, STM32 can determine if the reset was caused by watchdog.
Another use case for counter watchdog without SOC reset is to detect slow code paths.
Best regards,
Patryk

Added commit with simple implementation of free counter channels tracking. This allows to install watchdog more than number of counter channels.

Friendly ping


Better file header

I am using <TreatWarningsAsErrors> in my code.
Sadly, using it on your code throws generates a lot of warnings (und thus errors in my case)
Could you add the following Code in your generated file headers:
// <auto-generated />
#pragma warning disable CS1591

as an alternative to the <auto-generated /> comment you could decorate each generated method with the following (replacing Immutype and/or <IP_ADDRESS> with apropriate data:
[global::System.CodeDom.Compiler.GeneratedCodeAttribute("Immutype", "<IP_ADDRESS>")]

You could add XML-Docs to all generated methods as well (actually preferred) to not need to disable CS1591, but that is way more work

You could add XML-Docs to all generated methods as well (actually preferred) to not need to disable CS1591, but that is way more work

This code generator automatically adds comments to methods if there are comments to arguments. For example, this code will contain comments for all methods created by the generator.

I try that, but there are no doc comments for the target attribute though

Oh, it doesn't get the comment from the xml docs? That's a shame

Oh, it doesn't get the comment from the xml docs? That's a shame
No wonder it didn't work for me.

Added task #4

Fixed in 1.0.16


JSX coloring, this not colorized in Dark+ but it is colorized in Monokai

In the following snippet this should be colorized

It is colorized when I use the monokai theme

@aeschli since this is colorized in monokai,this hints that this is an issue with the Dark+ theme?

It's not a problem of the themes, but caused by our flattening of text mate scopes (#3008).
The tokenizer actually returns quite detailed scopes on the source code, but the theme ends up matching against a parent scope.
duplicate of #3008

return
    <View>
        <Text> {JSON.stringify(this.state.connectionInfoHistory)} </Text>
    </View>;


Help : Required prevent submit even if cf-conditional isn't respected

I've several forms merged in a single one.
I want to prevent empty input without using the required tag. Any work-around ?

It'll do the trick, thx. Maybe adding some "cf-required" stuff could be useful tho.

@Vaelrium I see your point, it does go against embracing standards as much as possible. You are also able to use flowStepCallback, like this example

It's okay with the pattern stuff tbh.
Now i'm trying to go a different path depending on the first select value.
I could change the action attribute of the form with jquery, but it seems like the action is stored at the beginning of the chat loading. Problem is I can't find where.


I'm not sure if this is a bug

GORM Playground Link

https://github.com/go-gorm/playground/pull/243
Description

I don't get your issue, could you make it clearly?

I don't get your issue, could you make it clearly?

I don't get your issue, could you make it clearly?

I don't get your issue, could you make it clearly?

I don't get your issue, could you make it clearly?
When not mounting the field name , the SQL contains ‘id = null‘ and Invalid search criteria .

I don't get your issue, could you make it clearly?
When not mounting the field name , the SQL contains ‘id = null‘ and Invalid search criteria .

Can you make a minimal example to explain it?

Can you make a minimal example to explain it?

Can you make a minimal example to explain it?

here for test :
https://github.com/go-gorm/playground/pull/243

https://github.com/airplayx/playground
gorm version : 1.20.9

Can you make a minimal example to explain it?

here for test :
https://github.com/go-gorm/playground/pull/243

https://github.com/airplayx/playground
gorm version : 1.20.9


Avoid floating point arithmetic when calculating time replacement

The current code essentially does this
timeReplacement = (startTime / timescale + ...) * timescale

When timescale is large enough (e.g. 10 MHz in order to support MS Smooth Streaming as well), "startTime / timescale * timescale" may not always be exactly "startTime" because of floating point precision, which could produce incorrect segment URLs.
Keep startTime unchanged in the timeline just to avoid the multiply/divide dance.
@TobbeEdgeware and @PhamCongDuc this is SHIELD-1235. The code is not exactly pretty, but I want to make sure I get the logic right before worrying about where to save "unscaledStart"

I think this looks nice, except that there is a potential issue with floating point accuracy from the presentationTimeOffset as well (we use zero, but for multiperiod, we may need other values).
It would be good to check if that part can be improved as well (an complication is that presentationTimeOffset can be defined on different levels with different timescales).
To get the code accepted, the best is to

create an issue on github describing the problem
make sure that current tests go through, and ideally add another test for this
submit a pull request for it.

I can help out with creating the issue. It might help since I've relationship with the main developer since before.

I looked a bit more at the file lib/dash/mpd_utils.js and the createTimeline function uses integer arithmetic to add presentationTime to the timestamp. However, the parseSegmentInfo sends back a scaled presentationTimeOffset. It might work to add a presentationTimeOffsetUnscaled to the return object and then use that together with the patch.

Thanks @TobbeEdgeware . @PhamCongDuc I'll leave it to you to handle the rest with help from @TobbeEdgeware. You should also make sure that it does fix the problems for TVB or we're just wasting time fixing something else.

I've made a shaka player issue https://github.com/google/shaka-player/issues/690 and we'll wait for response on whether they are open to pull request.
If they are positive, we may need to improve the fix to include presentationTimeOffset and possibly tests. I'll be back to you @duynguyen-ew  in that case.
@PhamCongDuc On the TVB side, it would be good if you use your own patched version for the moment. In any case, it will take some time until this is included in a dhaka-player release.

Thanks @duynguyen-ew , @TobbeEdgeware . I ran Skaka auto tests, nothing failed at the moment.

We got an answer to google#690  that they are positive to a patch.
I think one should check that all of "startTime", "endTime", and "presentationTimeOffset" are handled exactly, and not just "startTime".
Will you make one from Vietnam (with an github account Edgeware email address)?

Yes. I'm doing that (checking presentationTimeOffset) and will check endTime. I sent you a message on Slack.

Closing as #2 covers it too


AspNetCore 3.0 Web API GET yields 415 Unsupported Media type

If I try a GET request with complex type as parameter (from Blazor here), AspNetCore 3.0 Web API yields 415 Unsupported Media type. If I am not mistaken, it did work with 2.2.
For example:
    [HttpGet]
    public List<Customer> Get([FromQuery] Request request)
    {
        List<Customer> customers = _query.Get(request);
        return customers;
    }

Request headers:
    Host: localhost:5004
    User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:64.0) Gecko/20100101 Firefox/64.0
    Accept: */*
    Accept-Language: en-US,en;q=0.5
    Accept-Encoding: gzip, deflate
    Referer: http://localhost:5000/customers
    origin: http://localhost:5000
    DNT: 1
    Connection: keep-alive
    Pragma: no-cache
    Cache-Control: no-cache

Response headers:
    HTTP/1.1 415 Unsupported Media Type
    Date: Tue, 17 Sep 2019 13:25:29 GMT
    Content-Type: application/json; charset=utf-8
    Transfer-Encoding: chunked

Seems Content-Type: application/json is missing in the Get Request.
Is there something I am missing? A setup? Or something wrong with json serialization?

Could you share a minimal repro sample?

Sorry, it was caused by a bad server configuration.


[WIP - 0.3.2] Fix/FSMBehaviourBaseCase.setup

Proposed changes
changes the setup method on FSMBehaviourBaseCase from a class method into a regular method. Matches open-aea PR #300
Only once open-aea changes are introduced and should this be considered for merging. Also, the mypy ignore statements, def setup(self):  # type: ignore, can then be removed from all
Fixes
https://github.com/valory-xyz/open-autonomy/issues/1263
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

CLosing as this adds nothing of value relative to maiin


Computing h (Part II)

The dFFT implementation has been cleaned up. Involves breaking changes to the function inputs.
Added support for both the circom and libsnark versions of computing h. To use the libsnark version a different backend prover will have to be implemented.
Closes #46

Thanks! Committed the changes.


Occurrence not emitted for type tree of self parameters

class C { this: Map[Int, String] =>
}
class D { this: String =>
}
class E { this: E =>
}

-- obtained
++ expected
Occurrences:
[0:6..0:7) <= _empty_/
[0:8..0:8) <= _empty_/C#`<init>`().
+ [0:16..0:19) => scala/collection/immutable/Map#
+ [0:21..0:23) => scala/Int#
+ [0:25..0:31) => java/lang/String#
[2:6..2:7) <= _empty_/D#
[2:8..2:8) <= _empty_/D#`<init>`().
+ [2:16..2:24) => java/lang/String#
[4:6..4:7) <= _empty_/E#
[4:8..4:8) <= _empty_/E#`<init>`().
[4:16..4:17) => _empty_/E#

Observe that this: E produces an occurrence for E, as expected 🤔
Using Scalameta 4.3.0, 2.12.10
Originally reported in https://github.com/scalacenter/scalafix/issues/1000 by @travisbrown

I won't be able to look at this issue until earliest next week.

I was able to reproduce this issue in https://github.com/scalameta/scalameta/compare/master...olafurpg:self-type-occurrence?expand=1
The problem is that the Ident trees for Map, Int and String in this: Map[String, Int] have null types and NoSymbol. We may be able to recover the symbols by poking into the self type of the enclosing class but it will require some creative solution to align the type with the AppliedTypeTree

I took a look at this issue, it is mostly what @olafurpg said, let me add a few details:
Checking with this expression val x: Map[String,Int]
We get that Map[String,Int] is TypeTree which inside holds AppliedTypeTree with structure:
AppliedTypeTree(Select(Select(Ident(scala), Predef), Map), List(TypeTree(), TypeTree()))
We can see that Map here is not Ident and it's path was properly resolved.
In our case class C { this: Map[String, Int] => }
We also get that Map[String,Int] is TypeTree which inside has AppliedTypeTree but with different structure:
AppliedTypeTree(Ident(Map), List(Ident(String), Ident(Int)))
It is completely not resolved and Map String and Int are treated as unknown objects.
Also when you try to see that in scastie:
import scala.reflect.runtime.{universe => u}
import u._

val expr = reify {
 class X { this: Map[String,Int] => }
}

It throws exception with unexpected: bound type that doesn't have a tpe: Ident(TypeName("Map"))
If types should actually be expected in this scenario maybe this issue should be raised in scala-compiler?

@kpbochenek nice investigation! Yes, I believe this issue should be raised in scala/bug

For context, I believe SemanticDB used to handle this case before when we hijacked the typechecker with runtime reflection in order to instrument typechecking and attach information when occurrences like these got lost

We removed this hijacking step because it made it difficult to upgrade to new Scala versions and it didn't play nicely with other integrations like Hydra


RqForm.Smart#single() doesn't return a form parameter

the code below throws org.takes.HttpException: [400] form param "name" is mandatory
MatcherAssert.assertThat(
            new RqForm.Smart(
                new RqForm.Base(new RqFake(
                    "POST",
                    "/b",
                    "name=foo"
                ))
            ).single("name"), Matchers.is("foo"));

the test works fine on Takes  0.31.1, but fails on 0.31.2

@rultor release, tag is 0.31.3

@rultor release, tag is 0.31.3

@rultor release, tag is 0.31.3

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.31.3

@yegor256 Done! FYI, the full log is here (took me 5min)

@dmzaytsev should be fine now, please check

@yegor256 thanks

@dmzaytsev once 620-91883c6a puzzle is resolved (later, in another ticket), this ticket will be fully complete

@dmzaytsev the last puzzle 620-91883c6a/#625 originated from here solved


[ci] Add publish python engine and serving wlm pipeline

Change-Id: Ic3faf71f9af87beb1563bdf13477acd2cf616227
Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report

Merging #1260 (71c0c04) into master (1d8d32f) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1260      +/-   ##
============================================
- Coverage     71.97%   71.94%   -0.03%
  Complexity     5111     5111
============================================
  Files           473      473
  Lines         21909    21909
  Branches       2345     2345
============================================
- Hits          15768    15763       -5
- Misses         4937     4943       +6
+ Partials       1204     1203       -1

Impacted Files
Coverage Δ

...gine/src/main/java/ai/djl/dlr/engine/DlrModel.java
51.61% <0.00%> (-3.23%)
:arrow_down:

api/src/main/java/ai/djl/util/Platform.java
69.81% <0.00%> (-1.89%)
:arrow_down:

api/src/main/java/ai/djl/repository/Artifact.java
87.80% <0.00%> (-1.63%)
:arrow_down:

...ain/java/ai/djl/tensorflow/engine/TfNDManager.java
87.78% <0.00%> (-1.53%)
:arrow_down:

...ngine/src/main/java/ai/djl/mxnet/jna/LibUtils.java
40.00% <0.00%> (-1.18%)
:arrow_down:

.../djl/training/listener/MemoryTrainingListener.java
76.62% <0.00%> (ø)

...rc/main/java/ai/djl/paddlepaddle/jni/LibUtils.java
48.27% <0.00%> (ø)

api/src/main/java/ai/djl/inference/Predictor.java
91.34% <0.00%> (+2.88%)
:arrow_up:

Continue to review full report at Codecov.

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


Simplify address matching by providing a Matcher

A Matcher is constructed from an OSC address pattern and will use a
number of precompiled regular expression to match against a concrete OSC
address.  Regular expression match quite well to the pattern rules given
by the OSC specification and are used by other popular OSC libraries for
this purpose, e.g. python-osc.
I chose nom as a parser combinator library to parse OSC addresses and
OSC address patterns reliably and efficiently.
@DrLuke please do not take this as a criticism of your implementation, I
am very about happy your contribution!  Actually, I would be happy if
you could review this change so we can merge it back into your PR and
eventually release this feature.
My GitHub feed showed me that @D1plo1d is working on a no_std
feature which also adds nom.  I would be happy to receive a review
from @D1plo1d as well, hoping to reduce merge conflicts with their
feature.
Please be kind, I haven't programmed Rust in a long time and never used
nom before.

Hey, awesome PR, at first glance that looks like a way better approach!
I'll try to get a review done on sunday, I don't think I can get it in earlier.

@DrLuke Thank you very much for the review and please excuse my late reply because I was on vacation and started a new job this week.  Besides, I applied all the suggestions.

When thinking about performance I'm not sure if having a seperate Regex instance for each part is the way to go, but maybe this is an optimization for future PRs.

This is a valid point and, as you already said, something one can address in an upcoming PR.

This PR is fine from my side and ready  to merge.  Feel free to do that whenever you're ready.


Update status with one request

Currently for one thermostat there are at least four exactly the same requests.
Below log:
[19.02.2019, 18:29:11] [Thermostat] getTargetHeatingCoolingState from: http://localhost:9010/REST/homekit/status
[19.02.2019, 18:29:11] [Thermostat] getTargetRelativeHumidity: 0.5
[19.02.2019, 18:29:11] [Thermostat] getTemperatureDisplayUnits: 0
[19.02.2019, 18:29:11] [Thermostat] getHeatingThresholdTemperature : 25
[19.02.2019, 18:29:11] [Thermostat] getCurrentTemperature from: http://localhost:9010/REST/homekit/status
[19.02.2019, 18:29:11] [Thermostat] getCurrentHeatingCoolingState from: http://localhost:9010/REST/homekit/status
[19.02.2019, 18:29:11] [Thermostat] getTargetTemperature from: http://localhost:9010/REST/homekit/status
So in above example there are four calls to http://localhost:9010/REST/homekit/statusw which is very inefficient

@mariusz2108 I agree that this is quite inefficient; however, implementing this isn't straight forward due to the way HomeKit requests information.
The way I can see around it is for there to be a central function called something like getStatus which will do the one request; then, when a variable is requested e.g. getTargetTemperature, it asks the getStatus function for this info rather than requesting it directly from the thermostat. However, the central function must ensure that the info is up-to-date.
Like I said, I agree that this would be an improvement and I'm interested in looking into implementing this into my fork of the plugin in the near future.
Best, Tom

I also agree, but according on how you will ask SIRI/Home App information, you will still have 4 Calls. Indeed, we can separate the call to get a lighter payload, but at the time I did the plugin, I didn't saw much difference.
And then I think about all the peoplle the have a working API that could be broken with a new implementation.
Do you think this is really an issue ?
@Tommrodrigues, if you do a PullRequest (what can be nice) I will wrap it into a new version. V1.X.X
Thx

I have made POC with "caching" results and it makes huge difference for me (my home bridge runs on raspberry pi).
First request gets data and save it.
Then I start timer for one minut.
Sice now for one minute every request is taken from "cache".
I am not sure if it's good solution since I don't know well JS. But it works.

Not bad ;) it may be a good in between :) If you want to add a config param if unset that don’t cache it can make a good pull request :)
Sent from my mobile device.

Le 19 févr. 2019 à 21:45, mariusz2108<EMAIL_ADDRESS>a écrit :
I have made POC with "caching" results and it makes huge difference for me (my home bridge runs on raspberry pi).
First request gets data and save it.
Then I start timer for one minut.
Sice now for one minute every request is taken from "cache".
I am not sure if it's good solution since I don't know well JS. But it works.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Update terraform SDKv2 to the latest version

According to terraform docs, SDKv2 is deprecated in favour of framework. Eventually I assume we'll need to update to framework, but for now lets at least get to a recent version of SDKv2.
The changelog for SDKv2 says v2.0.3 was released September 2020, v2.26.1 in March 2023. The list of changes is long, but nothing is called out as breaking.
v2.0.4 does have a change that caused our AgentToken acceptance specs to fail:

Fix a bug that would pass the post-destroy state to
helper/resource.TestCase.CheckDestroy instead of the documented
pre-destroy state (https://github.com/hashicorp/terraform-plugin-sdk/issues/591)

It turns out that our CheckDestroy function was silently failing to confirm our acceptance tests were revoking Agent Registration Tokens when the resource was destroyed. Luckily, the tokens were being revoked correctly so the fix is to confirm that accurately in test code, not to change the code under test.
This is an alternative to #234, because I had to dig into what was causing the acceptance test failures.

Already merged but massively in favour of this and it's a prerequisite to migrate to framework.


Updating/Publishing the docs/ directory

I only realized that the docs/ directory exists recently, when refactoring README.md (#763, #764).
@fnothaft implied on #764 that the docs there get distributed via released artifacts, but I don't see any in adam-distribution_2.10-0.17.0-bin.tar.gz.
It seems like there was a lot of somewhat-duplicated markdown living there, vs. what was in README; now the README is very different.
Are builds of docs/ available on the internet anywhere? How should we keep them updated / consistent with README.md? Is it up to anyone making changes to update the docs in both places?
Should we move towards setting up e.g. readthedocs.org builds of the docs for each version? Should the README point at those? I generally like that approach, though some way to also publish docs for random non-release SHAs/nightly-snapshots or something would also be good and has been lacking in other projects who've done something like this, e.g. Spark.

The docs are published with the releases. I had hoped that by using simple markdown, the barrier to updating them would be low. Unfortunately, we haven't been updating them once created, e.g. git log -- docs.
I'm open to any suggestions about how to do documentation better. I haven't used readthedocs.org so I can't comment from experience. I hope what we choose needs to create standalone docs (e.g. PDF, html, etc) and not be dependent on services.

Ah, thx @massie, I see the PDF and HTML downloads on the releases/ page now. Thanks for the additional context as well; I don't have any great ideas at the moment but I'll leave this here until inspiration strikes someone.

We should push this to our github pages.

Fixed by #1461.


uncaught at check sagaMiddleware.run(saga, ...args): saga argument must be a Generator function!

After adding the new saga in sagas.js and adjusting the store to include the middleware following the tutorial
//sagas.js
export function* helloSaga() {
   console.log('Hello Sagas!')
}

the following error appears:
utils.js:188 uncaught at check sagaMiddleware.run(saga, ...args): saga argument must be a Generator function!

Both in latest Chrome and FF.

Can you provide a Gist ? Cant tell what s wrong only from above

Strangely enough, I cannot reproduce it on my machine at home. Will check tomorrow.
Is is possible that it would not build correctly under node 4.x for some reason ?

Have a similar issue, though not with the tutorial specifically. Trying to run my own redux-saga on react-native. I'm running node v6.2.0, react-native version 0.27.1, if that is relevant.  I include the middleware like so:
const sagaMiddleware = createSagaMiddleware({sagaMonitor});
const store = createStore(
  reducer,
  applyMiddleware(sagaMiddleware)
);
sagaMiddleware.run(rootSaga);

Where rootSaga is defined as:
export default function* rootSaga() {
  yield* takeEvery('CHECK', some_api_function);
}

The error message I get is:

Oh, my bad - the issue was caused by erroneous default import, while the saga was using the named export.

@michalczaplinski I also have this problem.Can you tell me how did you resolve this problem in detail?
Thank you!

@zilan830 Just using default export:
//sagas.js
export default function* helloSaga() {
   console.log('Hello Sagas!')
}

Dear Friends,
please help...
first i want to try it on Register
i am migrating from Thunk to Saga,
i feel frustrated with the handling difference ini this two machine
here is my code 👍
sagas.js
import { call, put, takeLatest, takeEvery } from 'redux-saga/effects'
import { REGISTER_REQUEST, REGISTER_REQUEST_SUCCESS } from '../constants'
import { registerRequest } from '../actions/register'
const headers = {
method: 'POST',
headers: {
'Accept': 'application/json',
'Content-Type': 'application/json'
},body: JSON.stringify(this.item)
};
// Sagas
export default function* watchRegister() {
yield takeEvery('FETCHED_REGISTER', registerAsync);
}
function* registerAsync() {
try {
yield put(registerRequest());
const data = yield call(() => {
return fetch(url, {headers})
.then(response => response.json())
}
);
yield put(registerRequestSuccess(data));
} catch (error) {
yield put(registerRequestError());
}
}
//
// Action Creators
export const registerRequest = () => {
return { type: 'REGISTER_REQUEST' }
};
export const registerRequestSuccess = (data) => {
return { type: 'REGISTER_REQUEST_SUCCEEDED', url: data.message }
};
export const registerRequestError = () => {
return { type: 'REGISTER_REQUEST_FAILED' }
};
export const register = (item) => {
return { type: 'FETCHED_REGISTER' }
};

So the main saga Beginner Tutorial has mistakes in it?

It is easy to miss deleting braces "{}" in this row "import rootSaga from './sagas'" while you work with Beginner Tutoral.

It is easy to miss deleting braces "{}" in this row "import rootSaga from './sagas'" while you work with Beginner Tutoral.

yep - I did this!


Difficulty logging in

Configuration:
Gerrit plugin v1.0.6-146
IntelliJ v2017.2.5
Gerrit v2.13.9
MacBook Pro - OS v10.13.3
I use IntelliJ for my IDE and not able to successfully login the Gerrit plugin. Have tried both HTTP and SSH urls for the project, both return "Login Failure" 401, Unauthorized. From command line can use either url and successfully clone the project.
The login attempts are by clicking the "Test" button in the Login section of the Preferences...->Version Control -> Gerrit dialog.
Any help would be appreciated. Thanks!

@stwwalton: Are you using the URL you are using in the browser for the Gerrit web UI in the address field?

@uwolfer: Yes, I got the URL from the Gerrit Web UI and the password is from Gerrit Web UI user->Settings->HTTP password.

Could you also try the credentials you are using for the web UI login?
Do you know what type of authentication your Gerrit instance is using (htaccess, single sign on, ...)?

Our Gerrit instance uses single sign-on. Web UI login credentials yield same unauthorized.

You could try debugging your connection as described here:
https://gerrit-review.googlesource.com/Documentation/dev-rest-api.html
Please let me know your results.

Results Here

Results Here

@stwwalton: Thanks for your logs (I have removed them because they are not by interst for other people). It looks like a issue with your credentials, not related to the plugin. I know from other people in your company which are using the Gerrit IntelliJ plugin - so I assume that it is related your setup. I suggest your to ask around how others have set it up. I think I cannot help you in this case.

Problem solved, it was a user error. The Web-URL is the url of Gerrit not the url of the project.


[SPARK-17002][CORE]: Document that spark.ssl.protocol. is required for SSL

What changes were proposed in this pull request?
spark.ssl.enabled=true, but failing to set spark.ssl.protocol will fail and throw meaningless exception. spark.ssl.protocol is required when spark.ssl.enabled.
Improvement: require spark.ssl.protocol when initializing SSLContext, otherwise throws an exception to indicate that.
Remove the OrElse("default").
Document this requirement in configure.md
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
Manual tests:
Build document and check document
Configure spark.ssl.enabled only, it throws exception below:
6/08/16 16:04:37 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users  with view permissions: Set(mwang); groups with view permissions: Set(); users  with modify permissions: Set(mwang); groups with modify permissions: Set()
Exception in thread "main" java.lang.IllegalArgumentException: requirement failed: spark.ssl.protocol is required when enabling SSL connections.
at scala.Predef$.require(Predef.scala:224)
at org.apache.spark.SecurityManager.(SecurityManager.scala:285)
at org.apache.spark.deploy.master.Master$.startRpcEnvAndEndpoint(Master.scala:1026)
at org.apache.spark.deploy.master.Master$.main(Master.scala:1011)
at org.apache.spark.deploy.master.Master.main(Master.scala)
Configure spark.ssl.protocol  and spark.ssl.protocol
It works fine.

Test build #63882 has started for PR 14674 at commit 6cc46b9.

Test build #63882 has finished for PR 14674 at commit 6cc46b9.

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

Merged build finished. Test PASSed.

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

Test build #63940 has started for PR 14674 at commit 0f18e94.

Test build #63940 has finished for PR 14674 at commit 0f18e94.

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

Merged build finished. Test PASSed.

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

Test build #63997 has started for PR 14674 at commit a38bd6b.

@srowen Thanks for your explanation. I misunderstood your previous comment. Now, I addressed your comments.

Test build #63997 has finished for PR 14674 at commit a38bd6b.

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

Merged build finished. Test PASSed.

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

Test build #64078 has started for PR 14674 at commit 9017807.

I'm fine with this PR, but I'm wondering if it makes more sense to set the default to one of the values here (probably "TLS"): https://docs.oracle.com/javase/7/docs/technotes/guides/security/StandardNames.html#SSLContext
So that the user doesn't have to specify.

@mgummelt I am fine with setting a default value. I have one concern about it. My motivation is to let the user make sure that they choose a proper protocol to use which meets their security requirement. Otherwise, user might think they are using the proper protocol, say TLS1.2, but it actually use TLS. With an exception, we just remind user that you should configure a protocol for secure communication.

If we document what the default is, I think it's a fair requirement that the user read the docs and verify that it meets their needs.

Test build #64078 has finished for PR 14674 at commit 9017807.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Jenkins, retest this please.

Test build #64101 has started for PR 14674 at commit 9017807.

Test build #64102 has started for PR 14674 at commit 9017807.

Test build #64101 has finished for PR 14674 at commit 9017807.

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

Merged build finished. Test PASSed.

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

Test build #64102 has finished for PR 14674 at commit 9017807.

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

Merged build finished. Test PASSed.

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

@srowen Do you have any suggestions on our discussion above? Thanks!

Merged to master


newline in header

the message header displays like this despite the app being fullscreen. only pluralchum is enabled (version 2.2.1), no themes or anything.

whoops didnt see another issue about the same thing


agent: Small code rework

This PR is all about code rework for cleanness so it is not intended to add new features or do massive reworks, just small ones.

@sixhills please take a look here as well.

Excellent! Comments help to understand the way the code works.


Please add xhamster proxies like xhwide1.com

The program does not recognise xhamster proxies and for some reason the main site does not work in my region and it gets redirected to proxies like the one in the title
PS: changing the site to "xhamster.com" does not download any of the files because this proxy doesn't work in my region as stated before

hi, can I work on this issue?

sur @RAG-KR @brthngnsh you can, here as well: https://github.com/ripmeapp2/ripme/releases .


[Event Request] codeunit 408 "DimensionManagement" - Change IntergrationEvent

Can we change the following event for the "DimensionManagement" Codeunit: OnAfterDefaultDimObjectNoWithoutGlobalDimsList
   ///
    // [IntegrationEvent(false, false)]
    [IntegrationEvent(true, false)] ///NEW
    ///-
    local procedure OnAfterDefaultDimObjectNoWithoutGlobalDimsList(var TempAllObjWithCaption: Record AllObjWithCaption temporary)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


[P1] SPIKE Explore integration with Red Hat Trusted Application Pipeline (RHTAP) and to perform Static Application Security Testing (SAST)

@vaibhavjainwiz please provide short updates here. and could you please add all relevant labels, complexity, priority etc here.


Web page + service crash upon Loading tape for job with multiple TBs

Hi Everyone, I'm trying to use LTFS and YATM into an ULTRIUM-HH8 tape reader for the first time and in my tests everything has been going well.
However, I have this issue where I add directories with multiple TBs of data to be loaded into an LTO-8 tape, upon selecting a tape and adding the barcode. my browser starts to consume all of my RAM and CPU, the page crashes and in the logs, YATM is getting stuck in mounting the tape.
I have to keep restarting the service and trying to delete the job multiple times until I am able to get access to the web gui again. in some of my smaller tests of 50GB single files being sent to tape it works ok.
This is running in an actual Dell PowerEdge 7415 server running CentOS 7.9
1x AMD EPYC 7401P
128GB RAM
256 O.S SSD
So I find it difficult that this would happen due to hardware limitations.
Does anyone have a clue of what can it be? When I issue LTFS commands and send data to the tape via CLI everything works fine.
Any help would be appreciated
Here are some logs:
time="2024-03-04T09:58:45+01:00" level=info msg="walk source all finished, get 251890 sources"
time="2024-03-04T10:06:00+01:00" level=info msg="+ mt -f /dev/nst0 load"
time="2024-03-04T10:06:00+01:00" level=info msg="+ sleep 5"
time="2024-03-04T10:06:05+01:00" level=info msg="+ sleep 3"
time="2024-03-04T10:06:08+01:00" level=info msg="+++ dirname ./scripts/mkfs"
time="2024-03-04T10:06:08+01:00" level=info msg="++ cd ./scripts"
time="2024-03-04T10:06:08+01:00" level=info msg="++ pwd"
time="2024-03-04T10:06:08+01:00" level=info msg="+ CURDIR=/opt/yatm/scripts"
time="2024-03-04T10:06:08+01:00" level=info msg="++ /opt/yatm/scripts/get_device"
time="2024-03-04T10:06:08+01:00" level=info msg="+ SG_DEVICE=/dev/sg8"
time="2024-03-04T10:06:08+01:00" level=info msg="+ /opt/ibm/ltfssde/bin/mkltfs -f -d /dev/sg8 -s 001130 -n GA-1130"
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS9015W Setting the locale to 'en_US.UTF-8'. If this is wrong, please set the LANG environment variable before starting mkltfs."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15000I Starting mkltfs, LTFS version <IP_ADDRESS> (10511), log level 2."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15041I Launched by \"/opt/ibm/ltfssde/bin/mkltfs -f -d /dev/sg8 -s 001130 -n GA-1130\"."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15042I This binary is built for Linux (x86_64)."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15043I GCC version is 4.8.5 20150623 (Red Hat 4.8.5-44)."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS17087I Kernel version: Linux version 3.10.0-1160.102.1.el7.x86_64<EMAIL_ADDRESS>(gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Tue Oct 17 15:42:21 UTC 2023 i386."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core)."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS17089I Distribution: NAME=\"CentOS Linux\"."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core)."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core)."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15003I Formatting device '/dev/sg8'."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15004I LTFS volume blocksize: 524288."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15005I Index partition placement policy: None."
time="2024-03-04T10:06:08+01:00" level=info
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS11337I Update index-dirty flag (1) - 001130 (0x0xcf0220)."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS17085I Plugin: Loading \"sg\" tape backend."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS30209I Opening a device through sg-ibmtape driver (/dev/sg8)."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS30250I Opened the SCSI tape device <IP_ADDRESS> (/dev/sg8)."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS30207I Vendor ID is QUANTUM ."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS30208I Product ID is ULTRIUM-HH8     ."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS30214I Firmware revision is K4K5."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS30215I Drive serial is 10WT060567."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS30285I The reserved buffer size of /dev/sg8 is 524288."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS30294I Setting up timeout values from RSOC."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS17160I Maximum device block size is 1048576."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS11330I Loading cartridge."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS11332I Load successful."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS17157I Changing the drive setting to write-anywhere mode."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15049I Checking the medium (load)."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15010I Creating data partition b on SCSI partition 1."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS15011I Creating index partition a on SCSI partition 0."
time="2024-03-04T10:06:08+01:00" level=info msg="LTFS17165I Resetting the medium's capacity proportion."
time="2024-03-04T10:06:16+01:00" level=info msg="LTFS11097I Partitioning the medium."
time="2024-03-04T10:06:16+01:00" level=info msg="LTFS30263I MODESELECT returns Mode Parameters Rounded (-20101) /dev/sg8."
time="2024-03-04T10:06:37+01:00" level=info msg="LTFS11100I Writing label to partition b."
time="2024-03-04T10:06:44+01:00" level=info msg="LTFS11278I Writing index to partition b."
time="2024-03-04T10:06:44+01:00" level=info msg="LTFS30205I READ_ATTR (0x8c) returns -20501."
time="2024-03-04T10:06:44+01:00" level=info msg="LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg8."
time="2024-03-04T10:06:44+01:00" level=info msg="LTFS30233I Cannot read attribute (-20501)."
time="2024-03-04T10:06:44+01:00" level=info msg="LTFS11336I The attribute does not exist. Ignore the expected error."
time="2024-03-04T10:06:44+01:00" level=info msg="LTFS17235I Writing index of 001130 to b (Reason: Format, 0 files) 10WT060567."
time="2024-03-04T10:06:51+01:00" level=info msg="LTFS17236I Wrote index of 001130 (Gen = 1, Part = b, Pos = 5, 10WT060567)."
time="2024-03-04T10:06:51+01:00" level=info msg="LTFS11337I Update index-dirty flag (0) - 001130 (0x0xcf0220)."
time="2024-03-04T10:06:51+01:00" level=info msg="LTFS11100I Writing label to partition a."
time="2024-03-04T10:06:55+01:00" level=info msg="LTFS11278I Writing index to partition a."
time="2024-03-04T10:06:55+01:00" level=info msg="LTFS30205I READ_ATTR (0x8c) returns -20501."
time="2024-03-04T10:06:55+01:00" level=info msg="LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg8."
time="2024-03-04T10:06:55+01:00" level=info msg="LTFS30233I Cannot read attribute (-20501)."
time="2024-03-04T10:06:55+01:00" level=info msg="LTFS11336I The attribute does not exist. Ignore the expected error."
time="2024-03-04T10:07:00+01:00" level=info msg="LTFS17235I Writing index of 001130 to a (Reason: Format, 0 files) 10WT060567."
time="2024-03-04T10:07:05+01:00" level=info msg="LTFS17236I Wrote index of 001130 (Gen = 1, Part = a, Pos = 5, 10WT060567)."
time="2024-03-04T10:07:05+01:00" level=info msg="LTFS15013I Volume UUID is: ad1ad853-edb4-4e2b-bd74-75172b02ca23."
time="2024-03-04T10:07:05+01:00" level=info
time="2024-03-04T10:07:05+01:00" level=info msg="LTFS15019I Volume capacity is 11712 GB."
time="2024-03-04T10:07:21+01:00" level=info msg="LTFS30252I Logical block protection is disabled."
time="2024-03-04T10:07:21+01:00" level=info msg="LTFS15024I Medium formatted successfully."
time="2024-03-04T10:07:21+01:00" level=info msg="+ sleep 3"
time="2024-03-04T10:07:24+01:00" level=info msg="+++ dirname ./scripts/mount"
time="2024-03-04T10:07:24+01:00" level=info msg="++ cd ./scripts"
time="2024-03-04T10:07:24+01:00" level=info msg="++ pwd"
time="2024-03-04T10:07:24+01:00" level=info msg="+ CURDIR=/opt/yatm/scripts"
time="2024-03-04T10:07:24+01:00" level=info msg="++ /opt/yatm/scripts/get_device"
time="2024-03-04T10:07:24+01:00" level=info msg="+ SG_DEVICE=/dev/sg8"
time="2024-03-04T10:07:24+01:00" level=info msg="+ /opt/ibm/ltfssde/bin/ltfs -o devname=/dev/sg8 -o noatime -o sync_type=unmount -o work_directory=/opt/yatm/captured_indices -o capture_index -o min_pool_size=256 -o max_pool_size=1024 -o eject -s /tmp/3212318303.ltfs"
time="2024-03-04T10:07:24+01:00" level=info msg="LTFS9015W Setting the locale to 'en_US.UTF-8'. If this is wrong, please set the LANG environment variable before starting ltfs."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS14000I LTFS starting, LTFS version <IP_ADDRESS> (10511), log level 2."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS14058I LTFS Format Specification version 2.4.0."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS14104I Launched by \"/opt/ibm/ltfssde/bin/ltfs -o devname=/dev/sg8 -o noatime -o sync_type=unmount -o work_directory=/opt/yatm/captured_indices -o capture_index -o min_pool_size=256 -o max_pool_size=1024 -o eject -s /tmp/3212318303.ltfs\"."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS14105I This binary is built for Linux (x86_64)."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS14106I GCC version is 4.8.5 20150623 (Red Hat 4.8.5-44)."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS17087I Kernel version: Linux version 3.10.0-1160.102.1.el7.x86_64<EMAIL_ADDRESS>(gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Tue Oct 17 15:42:21 UTC 2023 i386."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core)."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS17089I Distribution: NAME=\"CentOS Linux\"."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core)."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core)."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS14064I Sync type is \"unmount\"."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS17085I Plugin: Loading \"sg\" tape backend."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS17085I Plugin: Loading \"unified\" iosched backend."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS30209I Opening a device through sg-ibmtape driver (/dev/sg8)."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS30250I Opened the SCSI tape device <IP_ADDRESS> (/dev/sg8)."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS30207I Vendor ID is QUANTUM ."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS30208I Product ID is ULTRIUM-HH8     ."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS30214I Firmware revision is K4K5."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS30215I Drive serial is 10WT060567."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS30285I The reserved buffer size of /dev/sg8 is 524288."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS30294I Setting up timeout values from RSOC."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS17160I Maximum device block size is 1048576."
time="2024-03-04T10:07:24+01:00" level=info msg="9471 LTFS11330I Loading cartridge."
time="2024-03-04T10:07:27+01:00" level=info msg="9471 LTFS11332I Load successful."
time="2024-03-04T10:07:27+01:00" level=info msg="9471 LTFS17157I Changing the drive setting to append-only mode."
time="2024-03-04T10:07:27+01:00" level=info msg="9471 LTFS11005I Mounting the volume."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS17227I Tape attribute: Vendor = IBM     ."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS17227I Tape attribute: Application Name = LTFS                            ."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS17227I Tape attribute: Application Version = <IP_ADDRESS> ."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS17227I Tape attribute: Medium Label = GA-1130."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS17228I Tape attribute: Text Localization ID = 0x81."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS17227I Tape attribute: Barcode = 001130                          ."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS17227I Tape attribute: Application Format Version = 2.4.0           ."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS17228I Tape attribute: Volume Lock Status = 0x00."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS17227I Tape attribute: Media Pool name = ."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS11031I Volume mounted successfully. 001130 : Gen = 1 / (a, 5) -> (b, 5) / 10WT060567."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS14111I Initial setup completed successfully."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS14112I Invoke 'mount' command to check the result of final setup."
time="2024-03-04T10:07:43+01:00" level=info msg="9471 LTFS14113I Specified mount point is listed if succeeded."
time="2024-03-04T10:07:43+01:00" level=info msg="+ sleep 3"
time="2024-03-04T10:07:46+01:00" level=info msg="++ df /tmp/3212318303.ltfs --output=target"
time="2024-03-04T10:07:46+01:00" level=info msg="++ sed -n '1!p'"
time="2024-03-04T10:07:46+01:00" level=info msg="+ MOUNT_POINT_TARGET=/tmp/3212318303.ltfs"
time="2024-03-04T10:07:46+01:00" level=info msg="+ [[ /tmp/3212318303.ltfs != /tmp/3212318303.ltfs ]]"
time="2024-03-04T10:07:46+01:00" level=info msg="+ echo 'mount '\\''/tmp/3212318303.ltfs'\\'' success'"
time="2024-03-04T10:07:46+01:00" level=info msg="mount '/tmp/3212318303.ltfs' success"
time="2024-03-04T10:14:33+01:00" level=warning msg="update state failed while save job" error="save job fail, err= sql: transaction has already been committed or rolled back"
time="2024-03-04T10:14:33+01:00" level=warning msg="update state failed while save job" error="save job fail, err= context canceled"
time="2024-03-04T10:14:33+01:00" level=warning msg="update state failed while save job" error="save job fail, err= context canceled"
time="2024-03-04T10:14:33+01:00" level=warning msg="update state failed while save job" error="save job fail, err= context canceled"

[root@server ~]# systemctl status yatm-httpd.service -l
● yatm-httpd.service - YATM Service
   Loaded: loaded (/opt/yatm/yatm-httpd.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2024-03-04 09:43:05 CET; 29min ago
     Docs: https://github.com/samuelncui/yatm/
 Main PID: 30645 (yatm-httpd)
   CGroup: /system.slice/yatm-httpd.service
           ├─30645 /opt/yatm/yatm-httpd
           └─38066 /opt/ibm/ltfssde/bin/ltfs -o devname=/dev/sg8 -o noatime -o sync_type=unmount -o work_directory=/opt/yatm/captured_indices -o capture_index -o min_pool_size=256 -o max_pool_size=1024 -o eject -s /tmp/3212318303.ltfs

Mar 04 10:12:59 server yatm-httpd[30645]: 2024/03/04 10:12:59 /home/runner/work/yatm/yatm/executor/job.go:53 SLOW SQL >= 200ms
Mar 04 10:12:59 server yatm-httpd[30645]: [225.397ms] [rows:1] UPDATE `jobs` SET `status`=3,`priority`=1,`state`="<binary>",`create_time`="2024-03-04 09:58:45.972",`update_time`="2024-03-04 10:12:58.964" WHERE `id` = 15
Mar 04 10:12:59 server yatm-httpd[30645]: 2024/03/04 10:12:59 /home/runner/work/yatm/yatm/executor/job.go:53 SLOW SQL >= 200ms
Mar 04 10:12:59 server yatm-httpd[30645]: [249.348ms] [rows:1] UPDATE `jobs` SET `status`=3,`priority`=1,`state`="<binary>",`create_time`="2024-03-04 09:58:45.972",`update_time`="2024-03-04 10:12:59.414" WHERE `id` = 15
Mar 04 10:13:00 server yatm-httpd[30645]: 2024/03/04 10:13:00 /home/runner/work/yatm/yatm/executor/job.go:53 SLOW SQL >= 200ms
Mar 04 10:13:00 server yatm-httpd[30645]: [207.976ms] [rows:1] UPDATE `jobs` SET `status`=3,`priority`=1,`state`="<binary>",`create_time`="2024-03-04 09:58:45.972",`update_time`="2024-03-04 10:12:59.882" WHERE `id` = 15
Mar 04 10:13:00 server yatm-httpd[30645]: 2024/03/04 10:13:00 /home/runner/work/yatm/yatm/executor/job.go:53 SLOW SQL >= 200ms
Mar 04 10:13:00 server yatm-httpd[30645]: [210.772ms] [rows:1] UPDATE `jobs` SET `status`=3,`priority`=1,`state`="<binary>",`create_time`="2024-03-04 09:58:45.972",`update_time`="2024-03-04 10:13:00.292" WHERE `id` = 15
Mar 04 10:13:01 server yatm-httpd[30645]: 2024/03/04 10:13:01 /home/runner/work/yatm/yatm/executor/job.go:53 SLOW SQL >= 200ms
Mar 04 10:13:01 server yatm-httpd[30645]: [258.660ms] [rows:1] UPDATE `jobs` SET `status`=3,`priority`=1,`state`="<binary>",`create_time`="2024-03-04 09:58:45.972",`update_time`="2024-03-04 10:13:00.736" WHERE `id` = 15

How many files are you trying to backup in this job? Could you give me the number of files, so I can reproduce this bug?
It's a known issue that if a job contains too many files, it might get very slow to load the web gui. But I don't know it can be this extreme.

Thx for your Infomation, I will improve this in the future.


refactor: allow users to set global service account namespaces

Resolves https://github.com/akuity/kargo/issues/1186

@devholic it seems some changes might be missing from the PR?


STSE-2610 Aqara presence sensor FP1: fix possible re-onboarding issue

fix possible operation failure issue in case of re-onboarding scenario

@lelandblue Could you help to review this patch? please refer details on STSE-2610.

Hey @greens and @wkhenon Can you please review this PR?

@lelandblue Can you help me get this pull request merged?


How to install this testing model?which file to put in?thanks

I put the file into the"custom-nodes",but when I loaded the workflow, it warning the model is missing!

You need X_Adapter_v1.bin on the folder "models\checkpoints\X-Adapter" get it here.

where can I find this file?I didn't find it in the zip, thanks so much!

ComfyUI\custom_nodes\ComfyUI-Diffusers-X-Adapter\checkpoints\X-Adapter\X_Adapter_v1.bin