mlck crashes if it receives data it cannot decode

We don't handle exceptions yet, it's all a proof of concept, but this one is major so I'm noting it before I forget.
Triggered by a port scanner; thanks, random attacker.
2020-11-30 07:12:47,966 : INFO : accept: Accepting connection from ('<IP_ADDRESS>', 65144)
Traceback (most recent call last):
  File "./mlck", line 1847, in <module>
    main()
  File "./mlck", line 1844, in main
    handle(k, m)
  File "./mlck", line 1742, in handle
    data.client.handle(cmd)
  File "./mlck", line 282, in handle
    msg = msg.decode(config['encoding'])
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe0 in position 5: invalid continuation byte

Should be handled now.


added py to Clone a  DAG.

given a DAG, we create another graph that has copy of its vertices and edges connecting them.

Programming languages other than cpp are not entertained.


Add back -no-toolchain-stdlib-rpath when installing sourcekit-lsp

Pull #597 incorrectly removed this, as it's still needed on ELF platforms.
That pull noted some SPM changes invalidate the need for this flag, but that's irrelevant since this flag is passed directly to the Swift compiler.
As a result of this flag's removal last year, the 5.8 snapshots for linux have this extraneous /home/build-user/ rpath:
> readelf -d swift-5.8-DEVELOPMENT-SNAPSHOT-2022-12-20-a-ubuntu20.04/usr/bin/* | ag "File:|runpath" | ag sourcekit -A1
File: swift-5.8-DEVELOPMENT-SNAPSHOT-2022-12-20-a-ubuntu20.04/usr/bin/sourcekit-lsp
 0x000000000000001d (RUNPATH)            Library runpath: [/home/build-user/swift-nightly-install/usr/lib/swift/linux:$ORIGIN:$ORIGIN/../lib/swift/linux]

@ahoppen, please review.

Hey @buttaface,
We can’t simply add this flag back because in CI we are building all SwiftPM packages in a unified build, meaning that we don’t need to e.g. rebuild SwiftSyntax multiple times because the SourceKit-LSP, swift-format and the SourceKit stress tester import it. If one of the build invocation uses different compiler arguments than the others, that invalidates the entire unified build.
That being said, I think what we should be able to do is set this compiler flag inside SourceKit-LSP’s Package.swift using unsafeFlags. Do you think you could try that? I don’t have a Linux container at hand right now.
Also: Just so I understand the problem correctly: This is just about removing the rpath that references a directory on the Swift CI build machines. IIUC (and I might be completely wrong) that rpath shouldn’t be causing any harm because it most likely doesn’t exist on your machine, it’s just not clean. Is this correct?

I think what we should be able to do is set this compiler flag inside SourceKit-LSP’s Package.swift using unsafeFlags. Do you think you could try that?

I don't think that's the right place, because it's okay for local builds of sourcekit-lsp to have this rpath. The issue is that this build script determines the rpath for the executable shipping in the official toolchain, where this is wrong.

that rpath shouldn’t be causing any harm because it most likely doesn’t exist on your machine, it’s just not clean. Is this correct?

I believe it's a security hole on multi-user machines, as an attacker could create that account and then inject their own libraries' into others' use of sourcekit-lsp. Perhaps uncommon these days, but still worth closing up.

If one of the build invocation uses different compiler arguments than the others, that invalidates the entire unified build.

I did notice that. If there's some way to avoid that, let me know: maybe we can only apply it to executable targets at installation somehow?

Thanks for the explanation. That makes sense. I see two options here:
Option 1: Add the flag in Package.swift behind an environment variable like SWIFT_BUILD_SCRIPT_ENVIRONMENT similar to what we do in swift-syntax (https://github.com/apple/swift-syntax/blob/324166c2b2d6c2a06b078ff769b2e876ac933da2/Package.swift#L9)
Option 2: Pass -no-toolchain-stdlib-rpath in every build in the SwiftPM unified build. I believe this is the better option. The project that need updating should be: indexstore-db, SourceKitStressTester, SwiftEvolve, docc, swift-format and swift-syntax.

While the first option may be a way out, having to work around this seems wrong in the first place. Correct me if I'm wrong but I presume the reason SPM kicks off a rebuild is to make sure the same compiler flags are applied to all Swift source. However, this is a linker flag, so it should only apply to shared library and executable targets and shouldn't trigger a rebuild of all source files.
Is there currently no way to tell SPM or the compiler that?

I don’t think SwiftPM really knows anything about that compiler flag so it just assumes the worst and rebuilds all source files, which is a reasonable behavior IMO. Teaching SwiftPM about every Swift compiler flag doesn’t seem reasonable to me.
CC @neonichu

I think if the flag gets passed as an unsafe flags in linkerSettings, that may only result link steps being redone, but not 100% confident in that behavior.

it just assumes the worst and rebuilds all source files, which is a reasonable behavior IMO. Teaching SwiftPM about every Swift compiler flag doesn’t seem reasonable to me.

Not every flag, but couldn't we give it a list of Swift compiler flags that shouldn't trigger a full rebuild?

I think if the flag gets passed as an unsafe flag in linkerSettings, that may only result in the link steps being redone, but not 100% confident in that behavior.

To be clear, this is a Swift compiler flag that only affects a linker flag set by the Swift compiler, so it wouldn't be passed to linkerSettings, which I believe are passed directly to the linker.

To be clear, this is a Swift compiler flag that only affects a linker flag set by the Swift compiler

Ah I see. I don't think we have a great way to give special treatment to something like that at the moment. Rebuilding is happening at the llbuild layer and it works by basically comparing hashes of the full commandlines.

Huh, that is unfortunate that SPM doesn't control that. I will try Alex's workaround and submit that if it works.

Circled back around to this and updated this pull with a combination of Alex's Option 1 and Boris's suggestion of using linkerSettings, which works to not trigger a full unified rebuild in my local testing.
@neonichu, I was wrong to assume linkerSettings are passed directly to the linker like -Xlinker on the SPM command line, so I'm able to pass this through to the Swift compiler for the final executable product build, since only targets' linkerSettings are passed on to their associated SPM products and not their swiftSettings, which is what I originally tried as in Alex's swift-syntax link above.
@ahoppen, if you would kick off the CI for this, I'd like to get this in and into 5.8 next.

Note to self: Check that SourceKit-LSP build times aren’t increasing with this change.
@swift-ci Please test

Ready to go in? I will submit for 5.8 next.

Ah, actually, I’d like to measure toolchain build times as well. I triggered a toolchain build in https://github.com/apple/swift/pull/37710. If that doesn’t show us rebuilding SourceKit-LSP during the install phase, I’ll merge.

Good thing you tested building the toolchain too: it appears there's a bug with macOS SPM alone where linkerSettings are wrongly passed to clang instead? I can work around that for now by only enabling this flag for ELF platforms, which are the only ones where it does anything anyway, as this rpath flag does nothing on macOS and Windows.
@neonichu, is this a known issue with mac SPM? Should I file a bug?
The good news is that this did not trigger a full unified rebuild on the linux toolchain, according to the build log, as the first iteration of this pull was doing.

Updated this to only add back the flag on linux, should be good to go now.

Oh, good thing we watched that. Let’s run CI on this PR + build a toolchain to be sure this doesn’t break anything.
@swift-ci Please test

Tests passed, toolchain build passed and installing SourceKit-LSP took <20s so it doesn’t seem to trigger a full rebuild. Let’s merge it.


Add documentation on the current breaking changes policy.

As a team we've had a policy around breaking changes, though we haven't really written this down until now. This is a summarization of the current state of our stance on breaking changes (tl;dr it's impossible to avoid in all cases, in many cases it's possible to avoid, in the cases where it's not possible to avoid we have to see if the value the change bring is greater than the pain of adoption)

/azp run mrtk_docs


python310Packages.trimesh: 3.13.0 -> 3.13.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.trimesh is: "Python library for loading and using triangular meshes"
meta.homepage for python310Packages.trimesh is: "https://trimsh.org/"
meta.changelog for python310Packages.trimesh is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 3.13.4 with grep in /nix/store/gql5zi8rv88j2yvsmmimwadk6kmm5wrz-python3.10-trimesh-3.13.4
found 3.13.4 in filename of file in /nix/store/gql5zi8rv88j2yvsmmimwadk6kmm5wrz-python3.10-trimesh-3.13.4

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cura
python310Packages.trimesh
python39Packages.trimesh

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gql5zi8rv88j2yvsmmimwadk6kmm5wrz-python3.10-trimesh-3.13.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 python310Packages.trimesh https://github.com/r-ryantm/nixpkgs/archive/b6c148e9b00605251726fa277883522f19acdb0f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gql5zi8rv88j2yvsmmimwadk6kmm5wrz-python3.10-trimesh-3.13.4
ls -la /nix/store/gql5zi8rv88j2yvsmmimwadk6kmm5wrz-python3.10-trimesh-3.13.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 run on x86_64-linux 1

3 packages built:

cura
python310Packages.trimesh
python39Packages.trimesh

Maintainer pings
cc @gebner for testing.

Result of nixpkgs-review pr 186213 run on x86_64-darwin 1

2 packages built:

python310Packages.trimesh
python39Packages.trimesh


Add blueprint to Signed Distance Fields example

What
Also replace the somewhat broken screenshot it had (thumbnail was alright)

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using newly built examples: app.rerun.io
Using examples from latest main build: app.rerun.io
Using full set of examples from nightly build: app.rerun.io

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

Looks like you inadvertently added a submodule though

urgh, thought I removed that again, wasn't thorough. The requirements.txt in this one does a clone which an innocent git add . will trip over then


Unhandled KeyboardInterrupt in battery node

Steps:

run luxonis/rae-ros-robot:humble docker image
run bringup.launch.py
press ctrl+c when all the nodes are up and running

Expected: battery node is correctly stopped
Actual: unhandled KeyboardInterrupt exception occurs:
[battery_status.py-6] Traceback (most recent call last):
[battery_status.py-6]   File "/ws/install/rae_bringup/lib/rae_bringup/battery_status.py", line 122, in <module>
[battery_status.py-6]     main()
[battery_status.py-6]   File "/ws/install/rae_bringup/lib/rae_bringup/battery_status.py", line 114, in main
[battery_status.py-6]     rclpy.spin(battery_status_node)
[battery_status.py-6]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/__init__.py", line 222, in spin
[battery_status.py-6]     executor.spin_once()
[battery_status.py-6]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 705, in spin_once
[battery_status.py-6]     handler, entity, node = self.wait_for_ready_callbacks(timeout_sec=timeout_sec)
[battery_status.py-6]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 691, in wait_for_ready_callbacks
[battery_status.py-6]     return next(self._cb_iter)
[battery_status.py-6]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 588, in _wait_for_ready_callbacks
[battery_status.py-6]     wait_set.wait(timeout_nsec)
[battery_status.py-6] KeyboardInterrupt

I will close this issue and we can continue this conversation at the #50 so we are not talking about same thing at 2 places.

Ok, but, you know, that's a good practice to create issues for changes you're working on for better planning, progress tracking and clearer history.
Moreover, there might be a big epic-like issue that would likely be covered by several PRs.
In case of regression, the first thing people usually do, is searching among existing issues. And it's quite easy to track the related PRs when you use GH id in corresponding commit messages or PR description.
BTW, as I used a special keyword "fixes #N" in PR description, this issue would be automatically closed on merge. So it's not required to explicitly close it.
Anyway, of course, it's just a recommendation, but issue tracking would help a lot the others who would face similar issues in the future. Otherwise, there's a high probability of duplicates.


CVE-2007-4559 Patch

Patching CVE-2007-4559
Hi, we are security researchers from the Advanced Research Center at Trellix. We have began a campaign to patch a widespread bug named CVE-2007-4559. CVE-2007-4559 is a 15 year old bug in the Python tarfile package. By using extract() or extractall() on a tarfile object without sanitizing input, a maliciously crafted .tar file could perform a directory path traversal attack. We found at least one unsantized extractall() in your codebase and are providing a patch for you via pull request. The patch essentially checks to see if all tarfile members will be extracted safely and throws an exception otherwise. We encourage you to use this patch or your own solution to secure against CVE-2007-4559. Further technical information about the vulnerability can be found in this blog.
If you have further questions you may contact us through this projects lead researcher Kasimir Schulz.

consider using https://github.com/beatsbears/tarsafe instead

closing, superseded by PR #379


Upgrade to 2.0.0+ Breaks Current Instances

I'm unsure if this will be an issue, but thought it may help someone else in any case.
It looks like our instance needs to be set to "Multiuser Normal Operator" with ID set to 0 for things to work properly. We upgraded from 1.3.6 to the latest 2 release in a recent Beta. It looks like in the code if the multiuser isn't set it falls back to a single user else block.
I'm not familiar enough with EM to know if this should be added to the upgrade scripts or not, but think that as more users upgrade this could break their configurations as well. In any case, the multi-user setting should probably be added to the upgrade script so that it doesn't show ?? in the dropdown. Maybe there could be a notice added to the connection page that multi-user support was added and may need to be changed to operator if single doesn't work?
We only have one location with EM in use, so we may just be an edge case and, FWIW, it looks like we're on 3.0.0 OS version and 8.2.4374 SW version.

Thanks for the heads up


refactor: changing getState to improve code readability

Changing Object.keys to Object.entries as it gives to Object package the responsability to desconsruct the object as oposite to direct access the object.

As proposed by @kentcdodds on https://youtu.be/ubXtOROjILU?list=PLV5CVI1eNcJgNqzNwcs4UKrlJdhfDjshf&t=7823 it would be more clear to use Object.entries in getState method.

This makes the code more readable and gives the responsibility to better access the object to the Object module.

Change the Object.keys to Object.entries, making a small change inside the interaction.

Checklist:

[ ] Documentation
[X] Tests
[X] Ready to be merged

[X] Added myself to contributors table

@alexandernanberg  I would love to help on making sure that Babel transforms/polyfills it, could you give me some hints on how to test it?

Thanks for this! But I'm not sure this change is worth the polyfill. There's not a Babel transform for this.

I really do appreciate it @tyagow, but I don't think that this particular case is worth the extra effort to make sure we have polyfills in place. Thanks anyway!


Sum url content using Sentence Transformers before making prediction

This PR implements a new tool that uses the openAI API to extract the most relevant information from the html content of a browsed url. This can be seen as a preprocessing of each url's content, which is stored inside the additional information variable. This additional information leads to more accurate predictions by the tool.
Work in progress:

currently the get_website_summary() function feeds the gpt-3.5-turbo model the whole html content. As the model can only process 4K tokens, it throws an exception and skips the url if the html content exceeds the limit.

CI failures are unrelated to the changes here.

The workflow failed because i use code licensed by NVIDIA: "nvidia-cublas-cu11 (<IP_ADDRESS>): ['Other/Proprietary']"
The tox.ini does not list this licence under unauthorized. How should I proceed here?

I'm struggling to get it running. Here what I'm trying to archieve:
For gathering the most relevant information on the internet for predicting the question from the prediction market I want to use a sentence embedding model. These models map each sentence into a vector space. By calculating the dot product between each sentence embedding and the question embedding, it is possible to get some kind of semantic similarity between the question and each sentence. The sentences with the most similarity to the prediction market question, tend to be most relevant for making a prediction estimation. I tested different models locally and they perform very good, while being cost efficient. Only the preselected relevant content will be passed to GPT-4 which will make the prediction. The frameworks that are best suited for that are Sentence Transformer (BERT) and Universal Sentence Encoder (TensorFlow). With either model the code does not pass the PR workflow.
Sentence Transformers (BERT)
Sentence Transformers has pytorch as a dependency. PyTorch is a deep learning tensor library and comes with the CUDA API that enables the use of NVIDIA GPUs for computation. The CUDA library is licensed by NVIDIA, which is the reason why the workflow fails (https://github.com/NVIDIA/nccl/blob/master/LICENSE.txt). However it is possible to install PyTorch without CUDA, but only by providing the source url of the specific version in the pyproject.toml file. When I tried this I got an error in the "license compatibility check"-job:
_"File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/tox/config/init.py", line 1965, in replace_match
raise tox.exception.ConfigError(
tox.exception.ConfigError: ConfigError: No support for the 'url' substitution type"
Universal Sentence Transformer
This is a model library from the TensorFlow Hub. The problem here is that the installed TensorFlow version must match >2.14.0,<3.0.0 and Tensorflow requires protobuf (>=3.20.3,<4.21.0 || >4.21.0,<4.21.1 || >4.21.1,<4.21.2 || >4.21.2,<4.21.3 || >4.21.3,<4.21.4 || >4.21.4,<4.21.5 || >4.21.5,<5.0.0dev). But, as the mech depends on protobuf (<=3.20.1,>=3.19) version solving failed.
Is it possible to add support for the url substitution type to enable the use of PyTorch without CUDA in the code? Or alternatively is it possible to extend the authorized licenses with NVIDIA?
Or is there a chance to update protobuf to a version >=3.20.3 to make use of TensorFlow?

CI failures are unrelated to the changes here.

@0xArdi The licence related to NVIDIA can be whitelisted, as it is released under Apache 2.0 https://github.com/NVIDIA/NVTX/blob/release-v3/LICENSE.txt

CI failures are unrelated to the changes here.

@0xArdi The licence related to NVIDIA can be whitelisted, as it is released under Apache 2.0 https://github.com/NVIDIA/NVTX/blob/release-v3/LICENSE.txt

There are 12 components licensed by NVIDIA that do not pass the workflow:

nvidia-cublas-cu12 (<IP_ADDRESS>)
nvidia-cuda-cupti-cu12 (12.1.105)
nvidia-cuda-nvrtc-cu12 (12.1.105)
nvidia-cuda-runtime-cu12 (12.1.105)
nvidia-cudnn-cu12 (<IP_ADDRESS>)
nvidia-cufft-cu12 (<IP_ADDRESS>)
nvidia-curand-cu12 (<IP_ADDRESS>)
nvidia-cusolver-cu12 (<IP_ADDRESS>)
nvidia-cusparse-cu12 (<IP_ADDRESS>)
nvidia-nccl-cu12 (2.18.1)
nvidia-nvjitlink-cu12 (12.2.140)
nvidia-nvtx-cu12 (12.1.105)

Hello this is Armagan from Gnosis
Congratulations on winning a prize for the Best Mech Mech Tool in the Prediction Agent Hackathon! Your innovative contribution stood out, and we're excited to award your work.
Please reply to this comment with your Gnosis Chain wallet address so we can proceed with transferring your prize in xDAI.
Thank you for your fantastic work and looking forward to your continued contributions!

Hello this is Armagan from Gnosis
Congratulations on winning a prize for the Best Mech Mech Tool in the Prediction Agent Hackathon! Your innovative contribution stood out, and we're excited to award your work.
Please reply to this comment with your Gnosis Chain wallet address so we can proceed with transferring your prize in xDAI.
Thank you for your fantastic work and looking forward to your continued contributions!

Hi @0xarmagan, thank you for the great news! I'm honored and looking forward to future collaborations and contributions. My wallet address is 0x4a143CdC6B9A8AFb4D54E01A95A66c29ce8591DF.


allow to force-set black background of httpstream output

On white or bright-grey terminal, it's very difficult to read the color of httpstream ouput. I added an optional query param backgroud=black which will force-set the terminal background of the httpstream output text to black.

wouldn't you prefer just turning colors off?

I know it's poss to turn the colors off, but I think the colors are really useful to distinguish output of different containers. I don't want to lose the readability just because I prefer white-background terminal.
I was thinking how to implement it least-invasively and this was what I came up with. I am happy to rewrite it if you have another idea how to keep the colors in bright terminal.


Feature: support for new XML format (per SonarQube)

Feature addition: XML schema support as per new SonarQube

adds a corresponding flag support in karma.conf.js for the new XML mode

proposing "xmlVersion" field into karma.conf.js

0 or omitted: old legacy behavior (such won't break happy users)
1: uses new XML version output (makes SonarQube 6.2 and newer users happy)
in the future, even newer XML versions can be numbered 2,3,4, and so on

related switch added to karma.conf.js: xmlVersion (if omitted => works in legacy mode, if defined -> works in new XML mode)

so, commit code keeps the current functioning of karma-junit-reporter as-is,
nothing changed. Unless user changes the karma.conf.js configuration file

Validation of new XML report
The XSD schema ("specs") used for testing is also included in the commit
(file sonar-unit-tests.xsd)
New XML output report was validated against the specs with 'xmllint' tool.

If someone wants to test this, would be great. Don't test in production, necessarily.
To test:
drop this new index.js into your project-local karma-junit-reporter. For example, I have now:
./node_modules/karma-junit-reporter/index.js
So 'cp' (copy) this new index.js over that old mentioned above.
Further:

To test that nothing was broken in old code:
just run your karma -related testing as you used to

To test the new thing, ie. XML format, edit your karma.conf.js file and insert xmlVersion: 1
into the junitReporter -section

Thanks,
J

thank you! it would be really cool if junit support on sonar is back :) +1

All go from this side. If you care to review this PR further, would be great.

Thank you :octocat:


Enable socket.reuse_address in MDNS::Server so it plays nicely with other multicast clients

I had to enable @socket.reuse_address = true. Otherwise I would get:
Unhandled exception: Could not bind to '<IP_ADDRESS>:5353': Address in use (Socket::BindError)

presumably because I have other programs listening to port 5353, including avahi-daemon on my computer.
Per this document, "[with SO_REUSEADDR] every incoming multicast or broadcast UDP datagram destined to the shared port is delivered to all sockets bound to the port."
Works now! :smile:

Thanks!

pushed a new version: v1.0.2


⚠ Bofrost.fr has degraded performance

In a1c15c2, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 949 ms

Resolved: Bofrost.fr performance has improved in 4404e26 after 13 minutes.


escaped characters in the mapping rules are not honoured

Escaped characters (such as %20) in the mapping rules are not honoured.
In porta, when a % is used in a mapping rule, it has to be part of an escape sequence to be accepted. Otherwise, porta refuses to save the settings.
And APIcast treats the percent signs as litteral.
This means it is not possible to use a percent in a mapping rules:

/foo/100%/bar is not accepted by porta because %/b is not a valid escape sequence
/foo/100%25/bar is accepted by porta but APIcast does not correctly matches it

Version
I'm using the hosted APIcast (SaaS).
Steps To Reproduce

Define the mapping rule /foo/100%25/bar$

Try to query the API with:

curl https://blablabla/foo/100%25/bar
curl https://blablabla/foo/100%2525/bar

Current Result

curl https://blablabla/foo/100%25/bar => KO
curl https://blablabla/foo/100%2525/bar => OK

Expected Result

curl https://blablabla/foo/100%25/bar => OK
curl https://blablabla/foo/100%2525/bar => KO

Hi @nmasse-itix
I tested this and it's working correctly:
bash-4.2$ curl http://localhost:8080/20/?user_key=12312 -v
* About to connect() to localhost port 8080 (#0)
*   Trying <IP_ADDRESS>...
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> GET /20/?user_key=12312 HTTP/1.1
> User-Agent: curl/7.29.0
> Host: localhost:8080
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: openresty
< Date: Tue, 20 Aug 2019 16:54:57 GMT
< Content-Type: application/json
< Content-Length: 585
< Connection: keep-alive
< Cache-control: private
< Set-Cookie: d8c1dd0e39ac4456ed39ce5889b9a5a5=abe93c04c357bfdab7978dd760ca80c0; path=/; HttpOnly
< Vary: Origin
< X-Content-Type-Options: nosniff
<
{
  "method": "GET",
  "path": "/20/",
  "args": "user_key=12312",
  "body": "",
  "headers": {
    "HTTP_VERSION": "HTTP/1.1",
    "HTTP_HOST": "echo-api.3scale.net",
    "HTTP_ACCEPT": "*/*",
    "HTTP_USER_AGENT": "curl/7.29.0",
    "HTTP_X_REAL_IP": "<IP_ADDRESS>",
    "HTTP_X_FORWARDED_FOR": "<IP_ADDRESS>, <IP_ADDRESS>",
    "HTTP_X_FORWARDED_HOST": "echo-api.3scale.net",
    "HTTP_X_FORWARDED_PORT": "443",
    "HTTP_X_FORWARDED_PROTO": "https",
    "HTTP_FORWARDED": "for=<IP_ADDRESS>;host=echo-api.3scale.net;proto=https"
  },
  "uuid": "d745b402-2852-4f3e-b239-71cbcffbc937"
* Connection #0 to host localhost left intact
}bash-4.2$ curl http://localhost:8080/%2520/?user_key=12312 -v
* About to connect() to localhost port 8080 (#0)
*   Trying <IP_ADDRESS>...
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> GET /%2520/?user_key=12312 HTTP/1.1
> User-Agent: curl/7.29.0
> Host: localhost:8080
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: openresty
< Date: Tue, 20 Aug 2019 16:55:04 GMT
< Content-Type: application/json
< Content-Length: 588
< Connection: keep-alive
< Cache-control: private
< Set-Cookie: d8c1dd0e39ac4456ed39ce5889b9a5a5=1f3ae150fd257186107c0631ee0eaaa3; path=/; HttpOnly
< Vary: Origin
< X-Content-Type-Options: nosniff
<
{
  "method": "GET",
  "path": "/%2520/",
  "args": "user_key=12312",
  "body": "",
  "headers": {
    "HTTP_VERSION": "HTTP/1.1",
    "HTTP_HOST": "echo-api.3scale.net",
    "HTTP_ACCEPT": "*/*",
    "HTTP_USER_AGENT": "curl/7.29.0",
    "HTTP_X_REAL_IP": "<IP_ADDRESS>",
    "HTTP_X_FORWARDED_FOR": "<IP_ADDRESS>, <IP_ADDRESS>",
    "HTTP_X_FORWARDED_HOST": "echo-api.3scale.net",
    "HTTP_X_FORWARDED_PORT": "443",
    "HTTP_X_FORWARDED_PROTO": "https",
    "HTTP_FORWARDED": "for=<IP_ADDRESS>;host=echo-api.3scale.net;proto=https"
  },
  "uuid": "97ac637a-a8fe-4526-8627-53c6b2c98156"
* Connection #0 to host localhost left intact
}bash-4.2$
bash-4.2$ curl http://localhost:8080/%252020/?user_key=12312 -v
* About to connect() to localhost port 8080 (#0)
*   Trying <IP_ADDRESS>...
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> GET /%252020/?user_key=12312 HTTP/1.1
> User-Agent: curl/7.29.0
> Host: localhost:8080
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Server: openresty
< Date: Tue, 20 Aug 2019 16:55:09 GMT
< Content-Type: text/plain; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
<
* Connection #0 to host localhost left intact
bash-4.2$

And the config:
{
  "services": [
    {
      "id": 42,
      "backend_version":  1,
      "backend_authentication_type": "service_token",
      "backend_authentication_value": "token-value",
      "proxy": {
        "api_backend": "https://echo-api.3scale.net",
        "proxy_rules": [
          { "pattern": "/20/$", "http_method": "GET", "metric_system_name": "hits", "delta": 1 },
          { "pattern": "/%20/$", "http_method": "GET", "metric_system_name": "hits", "delta": 1 }
        ],
        "policy_chain": [
          { "name": "apicast.policy.apicast" }
        ]
      }
    }
  ]
}


implement FilterFn for ChunkedArray

Heh, turns out the naive implementation is 3x slower than develop, pretty much entirely due to find_chunk_idx slowness

Alright so currently what I'm seeing is for Q15 vortex-compressed-file:

develop: ~112ms
This PR, using ChunkedArray::find_chunk_idx: ~700ms, most of that in find_chunk_idx
The latest commit that uses a binary search on pre-materialized chunk indices: ~106ms

The new flame graph is showing ~6% less time spent in filter, which is what we'd expect roughly just going off the numbers

Right, this can go lower if all the children also implement filter. Good to know that we need to unpack values

Most of the children do implement FilterFn, the exception is extension array

FoR has it. Notable omission is Bitpacked which could repack itself and it likely would be faster. Also sparse is missing which likely leads to some extra allocation

fwiw we should make them in separate prs

@a10y you have a bug somewhere
Failed to get min_index from SparseArray: index 0 out of bounds from 0 to 0
Backtrace:
disabled backtrace

Alright benchmark comment is updated. Most queries stayed roughly same, the following got slower, some by a considerable margin:

Q1
Q3
Q4
Q7
Q10
Q15
Q16
Q21
Q22

Will do some profiling investigation in the AM

Alright, the issue was with filter_slices, it was creating so many slices that the overhead of slicing was just eating everything else up, especially when it came time to re-canonicalize before passing the RecordBatches back to DF.
Now, filter_slices will instead look at all of the slices and determine which chunks must be sliced, passed through, or dropped completely. I'll kick off a full bench run but for Q15 this saves us ~20% VS what we had on develop.

Ok benchmark run just completed, looks like the 20ms speed up i was seeing locally for Q16 was maybe just test jitter, in the PR run it's roughly same as develop. Most queries are 0-10% faster. A number are considerably slower, this time due to slow take implementation. May try and implement the accelerated search_sorted here as well

@a10y we should just merge this and make follow up prs. There's a lot of noise in the runs so comparing to latest develop runs is a bit difficult. Anyway I will review this and we can make another pr?

Alright I'm ok with that if you are. We have the issues for tracking already. I just hate to see graphs go up :P

I think I meant something else, you can avoid the scalar/array overhead but still use the search sorted logic, i.e. keep find_chunk_idx in chunked array but you can create a mirror of that function over &[u64]. In the current variant you end up with scalar overhead

like that?


Start-up stops at 99% - IP: <IP_ADDRESS> is not in the cert's list: <IP_ADDRESS>

This guaranteed to happen if I reboot and run Kitematic again. Dropping dev and recreating it works; however, I would like to avoid the productivity loss of reinstalling containers every time I reboot.
Cannot connect to the Docker Engine. Either the
VM is not responding or the connection may be
blocked (VPN or Proxy): Hostname/IP doesn't
match certificate's altnames: "IP: <IP_ADDRESS> is
not in the cert's list: <IP_ADDRESS>"

@dev-guy We are testing out a pre-release that should fix this problem! Do you mind giving it a try?
https://github.com/kitematic/kitematic/releases/download/v0.5.27-intel-nic/Kitematic-0.5.27-intel-nic.zip
Let me know if you are still running into the issue after.

Also consolidating this issue to: https://github.com/kitematic/kitematic/issues/483

I have the same problem how ever if I reinstall everything seems to be fine ..But again I will face the issue
Waste of time
Please fix the the issue

@ynagarjuna1995 It looks like you had multiple machines setup at some point - Whenever the certs above appears, you can always regenerate the certs via: docker-machine regenerate-certs default

i have the same error
IP: <IP_ADDRESS> is not in the cert's list: <IP_ADDRESS>

Thanks

@peter-mw Thank you for that command.  Saved me from blowing away my VM and starting from scratch.  You rock!

@peter-mw Thank you for the command, also saved my work

hi, i'm glad it worked, but credit for the command goes to @FrenchBen

It saved my day! Cheers..

Really really thanks +1

Thanks! It really helped.


Validation error silently swallowed when used within publish function

Given a publish function:
Meteor.publish('hello', function(name) {
  new SimpleSchema({name: {type: String, min: 5}}).validate({name})
  return Names.find({name});
});

Subscribing with:
Meteor.subscribe('hello', 'x');

I would expect to see an error on the server console just like I do with check but I see nothing. The function simply does not publish anything and that's it, making it hard to debug publications.
PS: I cross posted this over at the validated-method tracker on issue 15

The Meteor SimpleSchema package is no longer maintained other than critical fixes to keep it running with each latest Meteor release. Closing non-critical issues in this repo. Anyone who cares about this may do one or more of the following:

Switch to the NPM package. Be sure to adjust for the breaking changes. There can be a lot of work involved in switching, but it is worth the effort.
If this issue still occurs in the NPM package, submit an issue there. Be sure to include a link to a reproduction repo or a PR that adds a failing test for the issue.
If you have more time than money, submit a pull request to resolve any issue labeled "help wanted" in the NPM package repo.
If you have more money than time, donate to help support development if you are able


💥 Breaking(helm): Remove default oci-max-parallelism num-cpu

This may result in a surprising behaviour, as captured in:

https://github.com/dagger/dagger/pull/7395

You can still set this if needed, we are just removing it as the default option.

Follow-up to:

https://github.com/dagger/dagger/pull/8348#discussion_r1750138175

Thanks @jedevc 💪
Will merge as soon as the Helm / test passes.


Optimize the leadeboards screen

The Leaderboards screen recalls the API every time the screen is opened. Optimizing it would be nice :)
Suggestion:

Use Riverpod StateManagement

assign to me


💄 update example data

Codecov Report

Merging #57 (7005dc7) into main (6a9bcd1) will decrease coverage by 1.21%.
Report is 3 commits behind head on main.
The diff coverage is 56.25%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main      #57      +/-   ##
==========================================
- Coverage   80.66%   79.45%   -1.21%
==========================================
  Files          10       10
  Lines         393      404      +11
==========================================
+ Hits          317      321       +4
- Misses         76       83       +7

Files
Coverage Δ

pytometry/plotting/_histogram.py
71.42% <100.00%> (+1.86%)
:arrow_up:

pytometry/tools/_normalization.py
83.25% <30.00%> (-3.32%)
:arrow_down:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Bug 1802638: Allow support for creating an S3 bucket on an IPV6 cluster.

This is needed as the s3_bucket Ansible module does not support dual-stack endpoints, which is problematic is metering is run in an ipv6 single-stack configuration. In order to use the aws_s3 module which exposes a dualstack option, but has a dependency on the botocore python package. This commit would install that package so we can utilize this module to support both single-stack ipv4 and single-stack ipv6 configurations.

/bugzilla refresh

/lgtm


V7 doc updates

Update v7 integration docs per current state

There may be small tweaks if there is feedback from v7 but I don't expect anything significant


Update generate command to use the targetRootUrl

Not passing the targetRootUrl causes the command to match a lot more graphql files than it should which is confusing when one already update the targetRootUrl var to the proper path.

@alexisbronchart: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/


pull is not downloading everything or fixing all clashes

Hi, thanks for this great tool!
I'm trying to pull (drive <IP_ADDRESS>) a large set of files (55+GB), with hundreds of folders, thousands of files and up to 8 folder levels. I'm using my own api keys. First pull lasted hours, as expected, but when it finished without errors, about 8GB of files where missing.
Now, every time I do a pull, it lasts about 10 to 20 minutes and it downloads 100 or a few more new files.
The progress gets to 100% and no error is printed.
After 10 pulls, I'm questioning what I'm doing wrong or if I missed something from the readme.
It only should need 1 pull to download everything.
When trying to fix clashes, something similar happens (either with drive clashes -fix or with drive pull -fix-clashes).
Finally, a drive pull -fix-clashes -no-prompt returns to the prompt without errors, after fixing some clashes and without downloading anything.
I tried:
drive clashes -fix -no-prompt
drive pull -ignore-conflict -fix-clashes -no-prompt -verbose
drive pull -ignore-conflict -fix-clashes -no-prompt -recursive -verbose
drive pull -ignore-conflict -ignore-name-clashes -verbose
drive pull -ignore-conflict -ignore-name-clashes -recursive -verbose

my .driverc:
export=docx,xlsx,pptx,svg
same-exports-dir=true
hidden=true
no-prompt=true
verbose=true
desktop-links=false

[list]
depth=1
long=false

[push]
depth=-1
recursive=true

[pull]
depth=-1
recursive=true

uname -a:
Linux nas 4.9.0-0.bpo.2-amd64 #1 SMP Debian 4.9.18-1~bpo8+1 (2017-04-10) x86_64 GNU/Linux

Hello there @syp1975, thank you for the report and welcome to drive!
Wow, that's weird, I don't know how to proceed on this one except that that shows me that
there is something buggy with drive. I'll leave it open and as more work is done and more tests
are added, perhaps we'll flush out these bugs.

Hey, thanks!
If you need me to run some tests, I can arrange a golang setup.
For now, I use a crontab job to keep pulling files until the download completes.

I have the same issue...

Same thing here. Let me know if you need logs for debugging the issue.


ROI_number

Hi,
thank you for this tool.
I have some difficulties when adding a new ROI into an existing RTstructure.
In fact, I looked at the code and when adding a new ROI, the ROI_number is set to ds.StructureSetROISequence +1. However, in the RT file I have downloaded from my PACS, ROI_number are not consecutive. For example they are foing from 2 to 17, then 19 and 63. So I have for example 17 initial ROIs, and if I add 2 more ROIs, numbers 18 and 19 are automatically attributed, and this generates a error message when I reimport the RT structure in my PACS because there are two "numbers 19".
I will try to get around the problem but one of my suggestion would be to propose to the user to add (or not) the ROI_number when calling the add_ROI function and at least to specify this problem in your readme file as it was very difficult to understand where was the problem.
Best
Fabien

Hi Fabien,
Thanks for the suggestion. I agree that, that should be an option (and that we should update our documentation in that regard).
We should additionally test what existing roi_numbers are present and use one that isn't already taken, but that would be a separate initiative.
I can get a fix in for you sometime this week. If you'd like, feel free to try and tackle this in a PR :)

HI Asim,
thank you for your answer.
I managed to do it by modifying the rtstruct.py but my solution seems to be a little precarious as I removed the automatic roi_number affectation (which is not necessary for my ongoing study).
Yes I would like to provide something "well done" by proposing the two options (automatic and manual). It will take some time (I am new in Python and even more in Github :) )

No worries! Please reach out if you have any questions :)


86 Improve documentation MotionCheck

Changes
Improve documentation of MotionCheck Behaviour #86.
Related issues
Resolves #86
Checklist

[x] Tests are included for relevant behavior changes.
[x] Documentation is added in the docs folder for relevant behavior changes. If you made important user-facing
changes, describe them under the [Unreleased] tag in CHANGELOG.md.
[x] New package dependencies are declared in the pyproject.toml file.
Requirement files have been updated by running tox -e requirements.
[x] Code works with all supported Python versions (3.10, 3.11 and 3.12).
[x] Code is formatted according to PEP 8 (an IDE like PyCharm can do this for you).
[x] Technical guidelines listed in CONTRIBUTING.md are followed.

The documentation i can understand is looks good. but the detailed questions i can not answer - > please @hagrid67


Review import code to make sure a lock is acquired on additional data imports

Upload more data button as not disabled while a dataset was importing? Maybe?

I can't replicate this bug. Will wait for it to show up again.


Proposal: Use "describe" in place of "fixture"

Forgive me if this is thoroughly discussed already -- I couldn't find it, and just wanted to propose it. My understanding of the word "fixture" is more akin to sample data used to ensure consistent unit or integration tests (as described here). I normally have a fixtures directory of JSON files that I stub XHR requests with, for example. Testcafe uses it to describe the test file, which other testing libraries like mocha and jest use the word describe for. I just wanted to propose either changing it, or allowing an alias so as not to confuse fixture with the other meaning.

Hi @timwis,
Thank you for your observation.
When we just started working on TestCafe here at DevExpress, our first users were DevExpress teams that work on ASP.NET projects and run NUnit tests against them. So we borrowed the term fixture from NUnit meaning a set of tests.
I agree that most frameworks use the word fixture with a different meaning. However, the describe keyword is mainly used in BDD frameworks that support nested test sets. Note that we also have a suggestion to support BDD testing: https://github.com/DevExpress/testcafe/issues/792. And that's where we use describe instead of fixture.
As to our current test workflow, I feel like it is too late to make such a fundamental change switching from fixture to describe. This would be a major breaking change for all our users and we already have a number of them. After all, it is a matter of taste to rather prefer one or another keyword, isn't it?

Thanks for that background! Makes sense. I was suggesting perhaps allowing describe as an alias rather than replacing it, so it would be backwards compatible, but if that doesn't appeal to enough of your user base then it wouldn't be worth it I imagine.


Subject mapping doesn't specify rdf:type

See Subject mapping. It doesn't specify rdf:type, so PUAM has used owl:Thing, see eg http://data.americanartcollaborative.org/page/puam/object/17328.
Since you're using CRM, specify E1_Entity

Agreed.


wlr/taskbar crashes on icon missing from GTK theme

The app in Go I'm working on has just been given a .desktop file and an icon, located in /usr/share/nwgocc/nwgocc.svg. On Wayfire I use Waybar with the wlr/taskbar module.
"format": "{icon} {title:.15}",

Unless I remove {icon}, launching my program crashes Waybar with the message like this:

[2021-01-07 04:27:51.301] [error] Icon '/usr/share/nwgocc/nwgocc.svg' not present in theme Papirus-Dark

My other app, written in python, that stores the icon in /usr/share/azote/azote.svg doesn't crash Waybar. I wonder if this is a bug in Waybar, or maybe in my golang code. Could anybody help?
EDIT: Placing the icon in usr/share/pixmaps and using just the nwgocc name  in the .desktop file resolves the issue. I'll leave the issue open for a while, in case the Author wanted to know and catch the possible exception.

I ran into this same issue.
@nwg-piotr could you please re-open?
I don't expect Waybar to crash if an icon is missing when using wlr/taskbar.
Last log line with --log-level=trace:

[2021-02-06 18:58:43.776] [error] Icon 'network.cycles.wdisplays' not present in theme Adwaita

Info: Waybar v0.9.5-ff9f09a2 (branch 'master')

Sure.

@berbiche this should be fixed on master by @jgmdev :)

Thanks, I confirm the issue is resolved.


Can't parse workflows for BillyDM/vitalium-verb

Getting this:
2024-11-29 17:26:40.017 | INFO     | sr_data.steps.workflows:main:46 - Repo BillyDM/vitalium-verb has 1 *.yml|*.yaml workflows inside .github/workflows
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/sr-data/src/sr_data/steps/workflows.py", line 50, in main
    workflow_info(
  File "/sr-data/src/sr_data/steps/workflows.py", line 88, in workflow_info
    for matrixed in jdetails.get("strategy").get("matrix").get(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not iterable
error: Recipe `workflows` failed on line 140 with exit code 1

Full logs are here

@rultor release, tag is 0.0.23

@rultor release, tag is 0.0.23

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


Add support for attachments

Attachments are currently not supported

Support for attachments will be added in the following days, thank you for mentioning @fazpu

Hey @fazpu , version 0.1.3 includes support for attachments (also has breaking changes, please consult README before updating).


parcel doesn't export correctly the functions

Since i started working on this project, i had every time when serving the project had an error like :
Uncaught TypeError: Cannot read property 'create' of undefined
    at Object.parcelRequire.62.aphrodite (style.ts:46)
    at newRequire (speedscope.0c5f66b3.js:48)
    at localRequire (speedscope.0c5f66b3.js:54)
    at Object.parcelRequire.103.aphrodite (flamechart-style.ts:2)
    at newRequire (speedscope.0c5f66b3.js:48)
    at localRequire (speedscope.0c5f66b3.js:54)
    at Object.parcelRequire.35.inline-style-prefixer/static/plugins/calc (index.js:10)
    at newRequire (speedscope.0c5f66b3.js:48)
    at localRequire (speedscope.0c5f66b3.js:54)
    at Object.parcelRequire.51.preact (profile-table-view.tsx:2)

I believe there is a problem with the hot-reloading, at some point when i switch from master to old commit / branch that parcel finally export the function and i'm able to use it.
I never used parcel before so i don't know where to search the problem, if you have any idea i would happily try to debug

Yeah, I think there are some bugs in parcel's cache invalidation scheme. It's really annoying, but what I've done in this circumstance is to just do rm -rf .cache and then restart parcel. Super annoying.

I'm going to close this for now since this is a bug in parcel as far as I can tell, and don't think there's anything actionable to do in speedscope short of switching to a different bundler (all of which have their own unique set of issues).

Yeah, i believe its okay to close it but it would be preferable to add a section in the contributing readme so new developer can know that (and avoid spending hour waiting for parcel to refresh its cache ^^)


Per project opt-in/opt-out

It'd be great if this plugin had some kind of blacklist so you could opt-out certain projects from Copilot (for safety reasons). Or a whitelist if you'd like to block all the projects by default and only use Copilot in certain allowed project.

Hi @krystianpaszek, this is supported via configuration on github.com. See details in Excluding content from GitHub Copilot

Copilot for Xcode is missing from the table there, but it is in fact supported (docs PR in progress 🏃)


fixed->issue:147 search box is missing by replacing easyos-cn/docusau…

Fixes the problem of search bar missing which is added in PR 31

fixes:issue 147
to fix the issue I replaced the easyos-cn/docusaurus-local-search with @cmfcmf/docusaurus-search-local which works perfectly with docusaurus v2.
Live Link for testing
Working Demo Video : Google Drive Link
Screenshot

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

Figured out why previous local search not working will be creating a new pr for that.


Introduce RPP CPU backend, the GPU_SUPPORT flag and a restructure for common files

@rrawther @asalmanp this PR adds the CPU-only build and dependent changes::

Add support for an RPP CPU only build, and change all dependencies in headers and cmake
Cleanup rpp.h header and handle_api.cpp to accommodate CPU build.
Add a new GPU_SUPPORT flag taking inspiration from MIVisionX to turn ON/OFF gpu support in RPP builds.
Remove all unnecessary MIopen references in RPP external header and add RPP styled inline-documentation to rpp.h header.
Introduce backend support for the different flag possibilities in capital or small letters from the user - OPENCL/OpenCL/OCL/hip/HIP/cpu/CPU
Change multiple include statements to follow a pattern of first, a set of angular includes in <> for external includes, and then followed by a set of quotes includes in ”” for local rpp specific internal includes.
Clean up all overlapping code for OCL and HIP builds and ensure CMake builds only the required folders for each build type.
Remove any duplicate code applicable for HIP and OCL backends to be placed under the ‘common/rpp’ directory.
Add the AMD MIT License wherever not found.
Set rpp version in version header.
Restructure all functionality groups’ header and rppi/rppt*.cpp API files to accommodate a separate CPU build by separating GPU_SUPPORT on/off sections of code.
Restructure rpp_validate.hpp to accommodate a separate CPU build.
Add a new handlehost.cpp file to introduce a CPU specific handle, and clean up handlehip and handleocl cpp files.
Code cleanup, tabs to spaces conversions, deletion of unused files.

@asalmanp @r-abishek This PR passes all relevant unit tests.


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In 551cbc3, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 5717 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in 26ee8b8.


centos 7 compile error

centos 7
cmake command : cmake3 -B build -DBUILD_MYSQL_CONNECTOR=ON -DCMAKE_INSTALL_PREFIX=./output
use toolchains devtoolset-8 gcc 8.3.1
Scanning dependencies of target sqlpp11_assert_case
[ 64%] Building CXX object tests/core/static_asserts/CMakeFiles/sqlpp11_assert_case.dir/case.cpp.o
In file included from /root/sqlpp11/include/sqlpp11/type_traits.h:33,
from /root/sqlpp11/include/sqlpp11/data_types/no_value/data_type.h:30,
from /root/sqlpp11/include/sqlpp11/data_types/no_value.h:30,
from /root/sqlpp11/tests/core/usage/MockDb.h:32,
from /root/sqlpp11/tests/core/static_asserts/case.cpp:26:
/root/sqlpp11/include/sqlpp11/case.h: In instantiation of ‘constexpr sqlpp::assert_case_when_boolean_expression_t::assert_case_when_boolean_expression_t(T&& ...) [with T = {}]’:
/root/sqlpp11/include/sqlpp11/case.h:179:63:   required by substitution of ‘template decltype (sqlpp::detail::case_when_impl(sqlpp::check_case_when_t{}, when)) sqlpp::case_when(When) [with When = sqlpp::assignment_t<sqlpp::column_t<test::TabBar, test::TabBar_::Gamma>, sqlpp::boolean_operand>]’
/root/sqlpp11/tests/core/static_asserts/case.cpp:54:49:   required from ‘void {anonymous}::when_check(const When&) [with Assert = sqlpp::assert_case_when_boolean_expression_t; When = sqlpp::assignment_t<sqlpp::column_t<test::TabBar, test::TabBar_::Gamma>, sqlpp::boolean_operand>]’
/root/sqlpp11/tests/core/static_asserts/case.cpp:96:76:   required from here
/root/sqlpp11/include/sqlpp11/portable_static_assert.h:41:21: error: static assertion failed: argument is not a boolean expression in case_when()
static_assert(wrong_t<T...>::value, message);
^~~~~~~~~~~~~
/root/sqlpp11/include/sqlpp11/case.h:54:3: note: in expansion of macro ‘SQLPP_PORTABLE_STATIC_ASSERT’
SQLPP_PORTABLE_STATIC_ASSERT(assert_case_when_boolean_expression_t,

Which compiler version are you using?

gcc 8.3.1

OK, thanks, I will try to install that, but it will probably take some time.
Note that failures to compile these tests are not necessarily a hard problem and you might be able to use the library nonetheless. They test static_assert as described here: https://www.youtube.com/watch?v=zxDzMjfsgjg


Inverted clock polarity does not seem to work?

cc @therealprof, not sure whats going on here
I tested version v3 out on real hardware (ItsyBitsy M4). I was not able to get it working with the end frame polarity inverted - it would twitch blue and pink.
I could only get it working if I reset clock polarity back to all ones (0xff), which is no longer the default configuration.
This doesnt match my expectations.
Any chance you can try out the behaviour in v3 @therealprof ? would be interested to know how it behaves for your setup + if we can track down what its doing.

Yes, I can do in 10 hours or so.

@twitchyliquid64 Works perfectly fine for me.

What phase/polarity or mode do you have your SPI configured with?

polarity: Polarity::IdleHigh,
phase: Phase::CaptureOnSecondTransition,

Can you try with MODE0?
ie:
/// Helper for CPOL = 0, CPHA = 0
pub const MODE_0: Mode = Mode {
    polarity: Polarity::IdleLow,
    phase: Phase::CaptureOnFirstTransition,
};

Every other library I've found online uses MODE0, and my own experiments bitbanging it match mode 0.

Great reference that datasheet, huh? 😂
Anyway, that SPI mode works equally well for me.

Stellar datasheet XD
I think https://github.com/sajattack/bitbang-hal/issues/7 is to blame for why it doesnt work for me. Either way, I'll switch the mode in this crate to mode 0.


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement GPU acceleration for OpenEye docking (?)

Previous docking runs have been using CPUs. I tried to use the GPU queue and got this result:
Not sure if / how accelerating docking with GPUs is possible
Debug: Falling back to CPU as the GPU is currently not available
Debug: !!! GPU READY: FALSE !!!

https://docs.eyesopen.com/toolkits/python/omegatk/omegagpuomega.html?highlight=gpu

In the dock-e2e workflow we use GPUs and in my experience the OMEGA GPU code seems to work fine automatically.

is it actually using the GPUs though? i.e. do you still see that output in your log files or does it say something like "Yay! Found a GPU! Let's use it!"


Broadway

Broadway Font install
[Enter feedback here]

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

ID: 0ddc81be-f3c0-106b-d242-430e04d17184
Version Independent ID: 984d1db4-610b-15ec-48ae-dc4133083e32
Content: Broadway font family - Typography
Content Source: typographydocs/font-list/broadway.md
Service: typography
GitHub Login: @alib-ms
Microsoft Alias: alib

No actionable feedback. Closing.


Add Nice Global

I'll need to check the API, if I remember right then the existing global is pulled then filtered using the nice rank, which is potentially a bit slow.

Seems like I need to use http://api.nice.social/user/nicesummary to filter the list


Intro to state in Compose: Android Basics with Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-using-state?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-2-pathway-3%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-using-state#4
In which task and step of the codelab can this issue be found?
Intro to state in Compose
Describe the problem
Hi! I do not really know if it is a problem, however I was following the step by step of this process and I have found a litlle problem:

In the codelab it says that you can use this code, but I got an error that prevented me to build the app, may be something that changed in the mean time that the codelab was created and I have satarted, anyway if it is not a problem, ok.
I already tried to use .value, still not working
I expect being useful
Steps to reproduce?

it's just use the code on this codelab, it isn't working

Versions
Android Studio version:  sorry, i am new on this, can't say
API version of the emulator:  sorry, i am new on this, can't say
Additional information
Include screenshots if they would be useful in clarifying the problem.

Maybe this is because you're initializing it inside a Composable function.
It'll work with no errors if you initialize it in a not-composable one, otherwise, you'll need to do it with the remember function.
PS: You might want to take a look at Understanding state in Compose from Interacting with UI and State pathway.


Add IBM Backends to the Database

General
Add all important simulators and quantum computers from IBM to our database.
Something like IBMProvider.getBackends() gives us a list of backends. They are also visible here.
Therefore, the devices should be saved in connection with the IBM-Provider.
This should happen, when the database is initialized.
To make automated tests, we need to simulate on our local machine.
Therefor we need the aer_simulator .
And Noise Model ?
Standard should be the airsimulator, so we do not always send requests to IBM
Tasks

[x] Find out which backends/simulators/quantum-computer IBM has and select the important ones
[x] Update devices when user sends request
[x] Provide all devices and information in response of request
[x] Create a method to save all devices in the database (Therefor the database need to be extended)
[x] Implement get-all-device request (to update devices for this specific user)
[x] Extend the Job-Request-Dto with the device_name/id and use this in the code.
[x] Add aer_simulator to simulate on local machine (for local tests)

There are different backends for the aer_simulator, we currently use qasm_simulator. Is it necessary to choose between different backends or is it just fine for tests and local testing to only have one backend?


Converge fails when non-existent user set to lock

Cookbook version
5.3.1
Chef-client version
14.1.12
Platform Details
CentOS 7.5
Scenario:
Bootstrapping new nodes with a user being locked
Steps to Reproduce:
Create a databag with the action "lock" for a user that doesn't exist on a new node
Expected Result:
non-existent user ignored (no reason to lock a user that isn't there)
Actual Result:
Converge fails.
Relevant:

Chef::Exceptions::User:linux_user[XXXXX] (/var/chef/cache/cookbooks/users/resource/manage.rb line 65) had an error: Chef::Exceptions::User: Cannot modify user XXXXX - does not exist!

Closing because this cookbook is unmaintained.

Closing because this cookbook is unmaintained.


[MM-41570] Moving next on dismiss on boarding tour and finished value

Summary
Moving next on dismiss on causing issue with onBoarding Tour
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-41570
Related Pull Requests
NONE
Screenshots

before
after

https://user-images.githubusercontent.com/16203333/152521050-2a5e9cf5-2d1a-4ef4-b62e-8118c74b731a.mov
https://user-images.githubusercontent.com/16203333/152521160-3b7a5347-8a17-4428-8b94-4e21fa744da2.mov

Release Note
UI: Moving next on dismiss on causing issue with onBoarding Tour

@amyblais is it still possible to include this with following https://mattermost.atlassian.net/browse/MM-29622

@AGMETEOR Please help prioritize PR review.

Cherry pick is scheduled.

@AshishDhama This seems to need a manual cherry-pick.


encoding/csv: golang csv also so slow and consumed two much memory

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
go version go1.7 linux/amd64

What operating system and processor architecture are you using (go env)?
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"

What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

Read a several csv file, each one is about 50 m. the speed and memory usage are so huge.

What did you expect to see?

I compared regex with Java yesterday: https://github.com/golang/go/issues/16758
I wish Go can get the speed of Java

What did you see instead?

Go is much slower on CSV reading. I think writing also much slower too. So is there any way to optimize this? I read CSV like:
func (cd *CsvDecoder) readCsv(source []byte) (records [][]string, err error) {
	r := csv.NewReader(bytes.NewReader(source))
	return r.ReadAll()
}

Maybe I can set some options before reading? Seems I can't specify something like buffer size, etc. Why?

Can you provide two small, self contained  Go and Java programs that can be used to assess the problem?
How much slower than Java is "so slow"? How much memory is "huge memory"?

As @ALTree said, we need some more information. Maybe you can also give us some more information about your CSV files, like the number of rows and columns.
There are currently no options that you could specify for better performance.
The internal reader used by encoding/csv uses a bufio.Reader with default buffer size (4096 bytes). You could try to wrap your reader with an bufio.Reader by using bufio.NewReaderSize with a bigger buffer size, but I don't except this to yield any performance gains as the reader only reads from an in-memory byte slice.
I have a CL open that optimizes the encoding/csv a bit by avoiding some allocations (basically reducing allocations from 1*columns*rows to 1*rows in your case). In a simple synthetic test reading ~15 million rows of CSV I got a 17% win with my CL.
If you have multiple files you could also try to parse them with multiple goroutines in parallel.

You can also not use ReadAll if you care about memory. You should use Go's streaming APIs when your data is large.
Let's move this discussion to golang-nuts@ if there's nothing concrete to do here.
Reports on the bug tracker should be more concrete than "Go is slow" and the "the speed and memory usage are so huge". Please provide sample code, numbers, etc.

To be fair the standard library csv reader is notoriously slow out of the box, we could use an Issue tracking the problem. Obviously it'll need some data.

@ALTree, if you'd like to open one, please go ahead.


Tidy up readme titles

Codecov Report
Patch and project coverage have no change.

Comparison is base (237e5c4) 93.33% compared to head (a983df0) 93.33%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   93.33%   93.33%
=======================================
  Files           1        1
  Lines          15       15
=======================================
  Hits           14       14
  Misses          1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Stop using AppCompatActivity in the reference app

with our min sdk version 21, we probably don't need to use AppCompatActivity in the reference app

I would like to work on this @jingtang10 @fredhersch @epicadk

Will it be beneficial if I am removing AppCompactActivity and adding FragmentActivity.

@jingtang10 I would like to work on this issue, can you please assign it to me?

Looking at the documentation here https://developer.android.com/training/appbar/setting-up.html it appears that we should just use app compat activity anyway.
Let's just close this issue.


nextHtml

hi
when use custom nextHtml , yet old nexthtml is show !!!

Maybe removing this line in css file could fix it temporarily
.lSAction > a {
    background-image: url("../img/controls.png");

tnak , but i know this ,
i want you change in the source when nextHtml is not null change class


Build Error : missing .did files

During yarn dfx:install
$ yarn dfx:install
yarn run v1.22.19
$ yarn dfx:identity && sh ./scripts/install.sh
$ dfx deps deploy internet_identity
Installing canister: rdmx6-jaaaa-aaaaa-aaadq-cai (internet_identity)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  526k  100  526k    0     0  1636k      0 --:--:-- --:--:-- --:--:-- 1636k
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  8923  100  8923    0     0  46849      0 --:--:-- --:--:-- --:--:-- 46963
Deploying: ckbtc
All canisters have already been created.
Building canisters...
Executing 'true'
Error: Failed while trying to deploy canisters.
Caused by: Failed while trying to deploy canisters.
  Failed to build all canisters.
    Failed while trying to build all canisters.
      The post-build step failed for canister 'mxzaz-hqaaa-aaaar-qaada-cai' (ckbtc) with an embedded error:
         Failed to copy ~/B3/canisters/ckbtc/ledger.did to ~/B3/.dfx/local/canisters/ckbtc/constructor.did:
             No such file or directory (os error 2)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  275k  100  275k    0     0   832k      0 --:--:-- --:--:-- --:--:--  833k
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1716  100  1716    0     0   9778      0 --:--:-- --:--:-- --:--:--  9750
Deploying: kyt
All canisters have already been created.
Building canisters...

Fixed, Thanks.

Thank you. Ill check.

fixed! thanx!


Migrate to RxJava 3

Based on test/rxjava3 branch with updated imports & dependency updates for rxjava3.
As far as I can tell, all the tests are succeeding.
What's missing:

Some test files still contain "old imports" as function names, e.g. NotificationAndIndicationManagerTest.groovy
Some doc strings still have the old imports, e.g. BleAlreadyConnectedException.java

Fixes #690

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: dariuszseweryn:x: z3ntuYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for helping with the work. Unfortunately I cannot accept this PR until you will sign the CLA.
If you would have time to fix imports, docs and change package name to rxandroidble3 it would be awesome.

@dariuszseweryn I'm struggling at the moment to build the library to my local maven repository. Generally gradle rxandroidble:install mockrxandroidble:install dagger-library-shadow:install seems to work but the resulting pom at ~/.m2/repository/com/polidea/rxandroidble2/rxandroidble/1.11.1-SNAPSHOT/rxandroidble-1.11.1-SNAPSHOT.pom is missing all dependency information for some reason which I haven't figured out why. Any idea?

@dariuszseweryn ping?

Any news here ? because RxJava2 will soon be not supported anymore : https://bioserenity.atlassian.net/browse/MA-3566

I've noticed when using the lib built on jitpack.io (and manually adding back the dependencies, see my comments above) this:

Somehow some desugaring component doesn't translate one static interface
call correctly which makes the app crash at runtime.
Reproducible with deleting the app apk, ./gradlew assemblePreview
and install that apk.
When decompiling it (e.g. with apktool) use this command to view if the
error exists:
grep -r "fromAction(Lio/reactivex/rxjava3/functions/Action;)Lio/reactivex/rxjava3/disposables/Disposable"

The previous comment seems to be caused by https://issuetracker.google.com/issues/183632445 , workaround there is to put android.enableDexingArtifactTransform=false into your gradle.properties

FYI I'll probably only be able to work on this until the end of May, after that somebody else will have to complete the PR.

@z3ntu @dariuszseweryn Any update on this PR? 🙏🏼

@z3ntu I wanted to continue your PR but, I get this:
ERROR: Permission to z3ntu/RxAndroidBle.git denied to Drjacky.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

seems you need to check something  like

Allow edits from maintainers.

@Drjacky You're not maintainer which is why you don't have permission to push. The checkbox was on. I've given you direct access now though.
Feel free to rebase and fix up the rest etc. I've kept the last couple of commits un-squashed on purpose to allow to reproduce them in case upstream changes (which it did again as you can see). When it's getting close to be merged (maybe this will happen at some point..?) then just squash them together but please keep me as author. Good luck :)

@dariuszseweryn Please check Readme file to see if you're happy with ### Gradle and ### Maven sections as they're still pointing to .rxandroidble2.
Also, in gradle.properties:
GROUP=com.polidea.rxandroidble3
VERSION_NAME=1.12.2

Let me know if you want me to change them to something.

@dariuszseweryn @z3ntu Anything else we need to do to have this PR to be merged?

I've resolved the conflicts.
@z3ntu @dariuszseweryn Please check the PR if applicable. 🙏🏼

@dariuszseweryn Is there any plan to update this amazing library with RxJava 3 😃 ? I'm really looking forward to it 🔥

https://twitter.com/DSeweryn/status/1369016230095511554

I have still this in plans. I am currently working on merging #770 which should unlock me a bit but I must keep the ability to release the library

Waiting for this PR merging. Thanks

RxJava 3 based dependency is now on Maven Central under com.polidea.rxandroidble3:rxandroidble:1.15.0. I am sorry for such a long wait and would like to thank you all for the support. RxJava 2 based dependency is still supported for the time being under the usual com.polidea.rxandroidble2:rxandroidble:1.15.0. Cheers!


feat(op-reth): Add Shanghai Hardfork to Optimism ChainSpecs [PLANNED]

Describe the feature
This is a planned change to track addition of the Shanghai hardfork to optimism feature flag chain specs.
Additional context
Overview
Mainnet Ethereum has the Shanghai Hardfork, but Optimism is not. This Hardfork will need to be added to ChainSpecs behind the optimism feature flag once timestamp is set.
Where should this feature live?
In the OP_GOERLI and BASE_GOERLI ChainSpecs inside the primitives crate (and any other chainspecs underneath the optimism feature flag). See the op-reth repository for reference.
Completion Criteria

[ ] Shanghai Hardfork is added to all ChainSpec objects behind the optimism feature flag.

Resources

op-geth diff
op-erigon diff
Optimism Specs

@gakonst Request to add the A-op-reth label to this issue 🙏


Wrong Renew Before default values in cert-manager integrations leads to certificate expired

A clear and concise description of what the bug is.
After running Keda stably for over 2 years with the cert-manager integration we found a subtle but important bug that essentially turns into a exploding bomb after 2 years :bomb:. Our Certificate authority expired before the lead certificate had a chance to be renewed
When enabled, KEDA instanciates 2 certificates as part of a custom PKI infra to be able to communicate with the control plane using tls. In particular it creates the following:

A Root CA:

Duration: 1 year (fixed)
RenewBefore: 1 month (fixed)

A Leaf CA, signed by the Root CA:

Duration: 1 year (configurable)
RenewBefore: 8 months (configurable)

What we saw after 2 years of continual usage is described in the attached picture but I will try to summarize it in words.

Timeline:

17/08/24 => Lead certificate gets renewed as usual procedure

This will be valid for a year and won't get renewed again until 4 months have passed.

21/10/24 => Root certificate gets renewed

The new one is valid for a year while the old one is still valid for another 30 days

21/11/24 => The old CA expires.

That last event is the problematic. Technically both certs are still valid but the leaf certificate has been signed by a cert that is expired. This leads to the communication between the metrics pod and the controller to be broken. This is very dangerous as in our case it prevented our workloads to scale correctly  as the system was unable to detect the metrics correctly.
To make the matter even more complicated cert-manager is 100% unavare. As far as the controller is concerned both certs are generated, valid and signed.  The only solution at this point is to manually renew the leaf cert, either by manually removing the underlying secret or through the cert-manager apis.

[!CAUTION]
CC: @jeffhollan @JorTurFer @zroubalik @wozniakjan
I ask for the keda mantainers to please pay attention to this urgently as I suspect many people use the default config like we do and have a ticking bomb in their systems. All that is needed for this to trigger is the following config.

certificates:
  certManager:
    enabled: true

At my company we are lucky enough to deploy very aggressively and stay up to date with release so we may be one of the first once to notice and diagnose the problem.
Thankfully the scale from 0 to 1 worked fine as it is independent but since that point the work is being picked up by the HPA it wasn't unable to continue.
Expected Behavior
There are many lessons learn for me. In regards to keda, I think the chart should always ensure that, the renewBefore field of the Root CA should always be bigger than the usage duration of the leaf certificate (i.e. duration - renewBefore). This ensures that there will be at least a renewal of the leaf certificate in between a new root ca being issued and the old CA being expired.
Furthermore the Root CA should probably last longer than the leaf certificate. Looking at nginx-ingress, another project with a similar setup their values are 5 years for the root and 1 year for the leaf. Furthermore they allow the default renewBefore value of 2/3 of the duration. This makes them safe and robust with plenty of time to switch to the new CA.
I will also open up a discussion with the cert-manager team if it makes sense to consider a certificate as invalid if the ca is expired and maybe renew it as well.
Actual Behavior
Our Root CA expired faster than our leaf certificate could renew itself-
Steps to Reproduce the Problem

Deploy the chart with

certificates:
  certManager:
    enabled: true

Wait for 2 years... (I know a bit of an obscure scene)
The metrics pod will log thing similar to this

W1120 15:26:04.275111       1 logging.go:55] [core] [Channel #1 SubChannel #2]grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:9666", ServerName: "keda-operator.keda.svc.cluster.local:9666", }. Err: connection error: desc = "transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-11-20T15:26:04Z is after 2024-11-20T03:13:23Z"

Specifications

KEDA Version: 2.16.0
Platform & Version: AKS + cert-manager
Kubernetes Version: 1.30.5
Scaler(s): Rabbitmq, although it really doesn't matter as it is a general problem

I think you are right, the fact that the leaf cert is generated every 2 months but root CA can sign a month before its own expiration seems like a bug. The root CA should probably renew 3 months before its own expiry to be on the safe side.

imho https://github.com/kedacore/charts/pull/711 should fix this but I will wait for someone to verify my logic :)


support for my project

My project https://github.com/henrykironde/deletedret/tree/docbuild build well locally but has failed to build and create the desired docs on your server.

Please provide more information, this doesn't describe an actionable bug.

This is the docs home for the project  http://deletedret.readthedocs.org/en/docbuild/index.html.
If you try to go to the Submodules you should be able to see the code with the documentation,
However in am only getting the Submodules names.  I have attached a sample image. and you could check my local committed HTML files here https://github.com/henrykironde/deletedret/tree/docbuild/docs/_build/html

Your latest build shows failures due to missing dependencies during the html sphinx passes: http://readthedocs.org/projects/deletedret/builds/3637778/
Read more on our docs about mocking dependencies, my guess is you have C dependencies which we do not provide headers for. This requires mocking and removing those dependencies from your requirements.

I am closing this issue because i found the fix.
Since readthedocs doesn't take care of the requirements by default, Use the project's setting in readthedoc( advanced settings) and check
"Install Project:"  Install your project inside a virtualenv using setup.py install
and you may also give the path of the Requirements file:


Prepare Release <IP_ADDRESS>

Checklist:

[x] Create branch
[x] Update CHANGELOG.md
[x] Push this issue branch and create PR for it
[x] Merge PR into dev
[x] Git tag dev with <IP_ADDRESS>-rc.1
[x] Push the <IP_ADDRESS>-rc.1 tag on dev; thus, [.github/workflows/pip.yml] and [.github/workflows/conda.yml] are automatically launched on the <IP_ADDRESS>-rc.1 tag; whence, a GitHub pre-release is created, the Pip packages are pushed to the pre-release, and the Conda packages are pushed to the default khiops-dev channel;
[x] Manually launch the full automatic tests on the CI (by checking the "Long tests" box) on the <IP_ADDRESS>-rc.1 tag
[x] Manually inspect the CI logs on the <IP_ADDRESS>-rc.1 tag for the following workflows [.github/workflows/pip.yml], [.github/workflows/conda.yml] and [.github/workflows/unit-tests.yml] to make sure no warning or error is present therein
[x] Manually test the <IP_ADDRESS>rc.1 Conda packages on all target environments
[ ] If <IP_ADDRESS>-rc.1 tests are successful, then create PR to merge dev into main;
[ ] Merge PR into main;
[ ] Git tag main with <IP_ADDRESS>;
[ ] Push the <IP_ADDRESS> tag on main; thus, [.github/workflows/pip.yml] and [.github/workflows/conda.yml] are automatically launched on the <IP_ADDRESS> tag; whence, a GitHub pre-release is created, the Pip packages are pushed to the pre-release, and the Conda packages are pushed to the default khiops-dev channel;
[ ] Launch [.github/workflows/conda.yml] manually, on the <IP_ADDRESS> tag, selecting the official khiops channel;
[ ] Copy relevant CHANGELOG.md contents to the <IP_ADDRESS> GitHub pre-release;
[ ] (After the Conda package has been pushed to the official khiops channel ~and the API doc has been deployed~) Transform the <IP_ADDRESS> GitHub pre-release into a release.
[ ] Launch [.github/workflows/api-docs.yml] manually on the <IP_ADDRESS> tag and instruct it to deploy the documentation pages;
[ ] Make dev point to the merge commit just created in main. This is necessary to include the merge commit into main to calculate intermediary versions with Versioneer. Steps:

        git switch dev
        git reset --hard main
        git push origin dev # (you need to remove the protections of dev for this step)

Colab : OK
JuPyter : OK
Kaggle : ~ OK, but Conda envs don't seem to be supported in a straightforward way anymore.


🎮 Game Request
Game logic and basic description
A player has to guess the 3 numbers in order to win this game by using 5 simple hints. If player guess it correct than player will win else game restarted.
Point down the features
Game points

Generate 3 number code
Provide hints
Player's guess
Submit guess
Check for correct submission
If true win else loss
Loop continues

Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @pavitrachavda97 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @pavitrachavda97 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Add Github Hooks

Added hooks for BE lint and Markdown lint

added test hook

should add:

linting FE
tests FE
build FE
build BE


Add travis config

If you decide to merge this, you'll still need to add this repo in travis.

Thanks, but no thanks.


add OMIM xrefs

@matentzn I reviewed the Mondo mappings and added new Mondo xrefs to Mondo.
I have a list of mappings I didn't agree with here.
Related to https://github.com/monarch-initiative/mondo/pull/5492
cc @joeflack4 @hrshdhgd

Thank you for alerting me to the issue! Can you make sure your updated tables show up in the respective issues - I don't see it linked here and when the PR is merged, we will lose your notes :)
@hrshdhgd Can you take responsibility to develop a strategy on dealing with the false positive mappings?

According to the file linked above, the only No is for "matching on abbreviation".

that's right @hrshdhgd


FINALLY FIX APPROVER IN CARGO INVOICE!!!

About the PR

title
also a little remade approver for radio message
Why / Balance

bug and FOR BUREAUCRACY REASONS AHHH!!!!
fixes #27065
Technical details

approver was set AFTER the invoice was created, i just moved the code
also use the same thing for radio message instead of creating two new vars
plus read the comment below
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

fix: Fixed permanent absence of the approver string in cargo invoice.

changed some logic because initial commit caused some bugs when order was set approved but it could be denied if there is no room on ATS
Approved bool now sets manually after right before real approving, so the invoice will get approver data but wont be approved

guahhhhh

QUARTERMASTERS REJOICE!!


[BUG] Loss of CTRL+SHIFT+V Functionality and Other Issues After Update to 1.10.0

Description
After manually updating the Big AGI application to version 1.10.0, I've encountered a loss of functionality. Specifically, the CTRL+SHIFT+V shortcut, which I frequently use, no longer works. Additionally, there seem to be other features that are missing or not functioning as expected.
Steps to reproduce:

Pulled the latest changes from the GitHub repository.
Stopped the running Docker containers using docker-compose down.
Removed the old Docker image using docker rmi e65805c73b0a.
Updated the docker-compose.yml file to use the image tagged with 1.10.0.
Attempted to start the application with the new image using docker-compose up.

Expected behavior:
The CTRL+SHIFT+V function should paste the clipboard content as it did before the update, and all other features should operate as before.
Actual behavior:
The CTRL+SHIFT+V function does not respond, and other features appear to be missing or not working correctly.
Device and browser
Device: PC
OS: Debian 12 bookworm
Browser: Chrome (120.0.6099.216)
Screenshots and more

I've also noticed an error in the application logs after starting the updated version. Here's the relevant output:
▲ Next.js 14.0.4

Local:        http://localhost:3000

✓ Ready in 754ms
Error: aborted
at connResetException (node:internal/errors:720:14)
at abortIncoming (node:_http_server:782:17)
at socketOnClose (node:_http_server:776:3)
at Socket.emit (node:events:529:35)
at TCP. (node:net:350:12)
at TCP.callbackTrampoline (node:internal/async_hooks:128:17) {
code: 'ECONNRESET'
}
Willingness to Contribute

[X] 🙋♂ Yes, I would like to contribute a fix.

Hi @Satya12-369 thanks.
First, for the "ctrl + shift + v" issue, this is happening because Firefox did not support clipboard access (the screenshot is of Firefox, not Chrome).

Can you open with Chrome, and test if it works?

The "aborted" issue is by nodejs/nextjs when pressing the "stop" button. This is normal and expected, it just says the stream is interrupted and stop producing tokens. This is expected, for instance the Vercel AI SDK does the same exact behavior.

sorry for the confusion, still does not work on chrome either

Omg youre right!!!
I was browsing it in the Firefox broswer, my b! Now it works! Thank you! Sorry for being stupid! lol
I appreciate it


How to retrieve custom number of docs from parent retriver document , I have 100 docs and i don't want the reteiver to just retrieve only 4 docs

Issue you'd like to raise.
I have 100 docs , from which i am trying to retrieve top 10 docs which are most relevant to my query using parent document retriever. How can this be achieved.
Suggestion:
No response

@dosu-bot
can we choose how many docs are retrieved from the parent document retriever.?

@dosu-bot
I want to limit the number of relevant docs retrieved by parent document retriever. Is there something to do with get_relavant_documents function

@dheekshayogananda if you getting docs after similarity search then you must be getting score with it you can filter these to get the top 10

Hi,
I am having issues with get_relevant_documents function. It appears that the number of retrieved parent documents is set to 4 and I was not able to find any option to provide a parameter to retrieve more documents.

Hi, @dheekshayogananda  I have identified a potential solution to this set the search_kwargs={"k":} in the retriever object.
Example
retriever= ParentDocumentRetriever(
vectorstore=langchain_chroma,
docstore=store,
child_splitter=child_splitter,
parent_splitter=parent_splitter,
)
retriever.search_kwargs={"k":10}

retriever = ParentDocumentRetriever(
vectorstore=vectorstore,
docstore=store,
child_splitter=child_splitter,
search_kwargs={"k": 10}
)


Merge pull request #50 from pkprajapati7402/pr-most

Merge pull request #49 from pkprajapati7402/main

Awsome


Prevent MITM by authenticating Spotify servers

librespot doesn't have any way of authenticating Spotify's server, and will happily send the username and password to a MITM proxy. I don't know what the official client does about it.

The connection does not use TLS at all, so the certificate Spotify uses for their website is irrelevant.
My best guess is https://github.com/plietar/librespot/blob/master/protocol/proto/keyexchange.proto, the gs_signature field in the LoginCryptoDiffieHellmanChallenge struct.
We would need to find the public key and algorithm used to check that signature. Also relevant are the server_keys_known and server_signature_key fields in that same file.

The connection does not use TLS at all, so the certificate Spotify uses for their website is irrelevant.
openssl s_client -connect apresolve.spotify.com:443 presents a valid cert, but that's just *.spotify.com.

Did you eavesdrop on the connection and auth-negotiation of a certified device? Our lab just got an onkyo-avr that has built-in spotify-support - so if need be I could try to set up wireshark to have a look at the connections beeing made during zeroconf auth.

I'm not quite sure which part of the protocol you're referring to. There are basically 3 network connections :

Zeroconf authentication
Resolving the AP through apresolve.spotify.com
Connection to the AP

Zeroconf authentication only runs on your local network, and is encrypted (not authenticated, but there's no way of doing that since you don't know the device anyway). Your password is never sent though, only a token.
Resolving the AP uses http, with optional TLS. librespot currently does not use https for reasons explained in #124. Encryption is pretty pointless, and like I explained there, there's no point authenticating that part if the connection to the AP in not authenticated, and similarily, authenticating it isn't necessary if we authenticate the next part.
Finally authenticating the connection to the AP is what I would like to implement, and is what this issue is about. This is a proprietary protocol, with it's own exotic encryption and authentication. It isn't based on SSL/TLS at all, and makes no use of certificates.
Encryption is already implemented (that was necessary to get it working), but authentication isn't, and I'm not 100% sure how it is done, but my comment just above describes my initial thoughts on it. The next steps would be disassemble the relevant part from Spotify's binaries, figure out the crypto algorithm, where the inputs come from, build a simple MITM and see how the client behaves, and implement it here.

If you're still interested in this:
server_keys_known is a bitmask of all known signature keys (i.e. 1 << server_signature_key for all keys the client knows). So far there's only one key being used (key id 0).
gs_signature is the RSA (RSASSA-PKCS1-v1_5) signature of gs, signed using the key identified by server_signature_key. The public key (e, n) is hardcoded inside the Spotify client.
Here's a simplified version of the code I use to verify the signature:
static const unsigned char server_key_0_n[] = {
  0xac, 0xe0, 0x46, 0x0b, 0xff, 0xc2, 0x30, 0xaf, 0xf4, 0x6b, 0xfe, 0xc3,
  0xbf, 0xbf, 0x86, 0x3d, 0xa1, 0x91, 0xc6, 0xcc, 0x33, 0x6c, 0x93, 0xa1,
  0x4f, 0xb3, 0xb0, 0x16, 0x12, 0xac, 0xac, 0x6a, 0xf1, 0x80, 0xe7, 0xf6,
  0x14, 0xd9, 0x42, 0x9d, 0xbe, 0x2e, 0x34, 0x66, 0x43, 0xe3, 0x62, 0xd2,
  0x32, 0x7a, 0x1a, 0x0d, 0x92, 0x3b, 0xae, 0xdd, 0x14, 0x02, 0xb1, 0x81,
  0x55, 0x05, 0x61, 0x04, 0xd5, 0x2c, 0x96, 0xa4, 0x4c, 0x1e, 0xcc, 0x02,
  0x4a, 0xd4, 0xb2, 0x0c, 0x00, 0x1f, 0x17, 0xed, 0xc2, 0x2f, 0xc4, 0x35,
  0x21, 0xc8, 0xf0, 0xcb, 0xae, 0xd2, 0xad, 0xd7, 0x2b, 0x0f, 0x9d, 0xb3,
  0xc5, 0x32, 0x1a, 0x2a, 0xfe, 0x59, 0xf3, 0x5a, 0x0d, 0xac, 0x68, 0xf1,
  0xfa, 0x62, 0x1e, 0xfb, 0x2c, 0x8d, 0x0c, 0xb7, 0x39, 0x2d, 0x92, 0x47,
  0xe3, 0xd7, 0x35, 0x1a, 0x6d, 0xbd, 0x24, 0xc2, 0xae, 0x25, 0x5b, 0x88,
  0xff, 0xab, 0x73, 0x29, 0x8a, 0x0b, 0xcc, 0xcd, 0x0c, 0x58, 0x67, 0x31,
  0x89, 0xe8, 0xbd, 0x34, 0x80, 0x78, 0x4a, 0x5f, 0xc9, 0x6b, 0x89, 0x9d,
  0x95, 0x6b, 0xfc, 0x86, 0xd7, 0x4f, 0x33, 0xa6, 0x78, 0x17, 0x96, 0xc9,
  0xc3, 0x2d, 0x0d, 0x32, 0xa5, 0xab, 0xcd, 0x05, 0x27, 0xe2, 0xf7, 0x10,
  0xa3, 0x96, 0x13, 0xc4, 0x2f, 0x99, 0xc0, 0x27, 0xbf, 0xed, 0x04, 0x9c,
  0x3c, 0x27, 0x58, 0x04, 0xb6, 0xb2, 0x19, 0xf9, 0xc1, 0x2f, 0x02, 0xe9,
  0x48, 0x63, 0xec, 0xa1, 0xb6, 0x42, 0xa0, 0x9d, 0x48, 0x25, 0xf8, 0xb3,
  0x9d, 0xd0, 0xe8, 0x6a, 0xf9, 0x48, 0x4d, 0xa1, 0xc2, 0xba, 0x86, 0x30,
  0x42, 0xea, 0x9d, 0xb3, 0x08, 0x6c, 0x19, 0x0e, 0x48, 0xb3, 0x9d, 0x66,
  0xeb, 0x00, 0x06, 0xa2, 0x5a, 0xee, 0xa1, 0x1b, 0x13, 0x87, 0x3c, 0xd7,
  0x19, 0xe6, 0x55, 0xbd
};

bssl::UniquePtr<RSA> rsa(RSA_new());
rsa->n = BN_bin2bn(server_key_0_n, sizeof(server_key_0_n), nullptr);
rsa->e = BN_new();
BN_set_word(rsa->e, 65537);

std::uint8_t gs_hash[20];
SHA1(gs.data(), gs.size(), gs_hash);

if (1 != RSA_verify(NID_sha1, gs_hash, sizeof(gs_hash),
                    gs_sig.data(), gs_sig.size(), rsa.get())) {
  // failed
}


NIFI-3356: Initial implementation of writeahead provenance repository

The idea behind NIFI-3356 was to improve the efficiency and throughput of the Provenance Repository, as it is often the bottleneck. While testing the newly designed repository,
a handful of other, fairly minor, changes were made to improve efficiency as well, as these came to light when testing the new repository:

Use a BufferedOutputStream within StandardProcessSession (via a ClaimCache abstraction) in order to avoid continually writing to FileOutputStream when writing many small FlowFiles

Updated threading model of MinimalLockingWriteAheadLog - now performs serialization outside of lock and writes to a 'synchronized' OutputStream

Change minimum scheduling period for components from 30 microseconds to 1 nanosecond. ScheduledExecutor is very inconsistent with timing of task scheduling. With the bored.yield.duration
now present, this value doesn't need to be set to 30 microseconds. This was originally done to avoid processors that had no work from dominating the CPU. However, now that we will yield
when processors have no work, this results in slowing down processors that are able to perform work.

Allow nifi.properties to specify multiple directories for FlowFile Repository

If backpressure is engaged while running a batch of sessions, then stop batch processing earlier. This helps FlowFiles to move through the system much more smoothly instead of the
herky-jerky queuing that we previously saw at very high rates of FlowFiles.

Added NiFi PID to log message when starting nifi. This was simply an update to the log message that provides helpful information.

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Some neat stuff here, @markap14 .  I noticed you changed a couple of the same files as PR #1475.  Since #1475 is almost complete, it would be nice to commit that first.  Merging that into this PR shouldn't be bad at all, and if we're lucky it will still apply cleanly!

am a +1 to mike's point.  @markap14 can you please review/merge if appropriate 1475.  i'd be happy to dive through this once that is in place but agree we should not push this and complicate that one first.

@mosermw good call. We should be able to get #1475 merged pretty easily, I think. Then can rebase my PR.

@markap14 there seem to be some unintended files that made into the commit (i.e., /bin/.., .gitignore etc)


feat: Adding python3.11 support.

Closing because this work was done in https://github.com/openedx/codejail/pull/167


Website examples are currently not working

Hi,
Just in case you are not aware of it, the examples on the website (https://alpine-ajax.js.org/examples/)  are not working currently in Firefox or Chrome. They were working a couple of days ago.
The error as reported in Firefox: Uncaught (in promise) TypeError: t.status is undefined in function statusKey(attributes, response) at module.ems.js line 472, which is: let status = response.redirected ? "3xx" : response.status.toString();
In Chrome: Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'toString') at rn (module.esm.js:472:62)

ooof 🤦 I definitely need to get those pages added to the test suite
They should be good to go now! Thanks for letting me know 🙌

All working again.  Excellent! Thanks for fixing.