RepairnatorConfig specialized for each module?

RepairnatorConfig is highly related to the pipeline, but we use it for all modules now. What about creating one config for each module? Then we init the config for a given module with all args in that module, thus we don't need to retrieve specific args in any other location in the code?

The main purpose of RepairnatorConfig was actually to be used in every module... So I'm not sure about your proposal here.

Ok, let me try to elaborate...
Each module receives args. Some args are shared among modules, and some args are specific to single modules. For instance, in the realtime module, we have the arg whitelist. Observe that we use RepairnatorConfig field in that module, but we don't use it to store the value of the arg whitelist. Then, when we need this arg, we do like this: this.arguments.contains("whitelist"). As this example, it happens with a lot of args because in RepairnatorConfig we don't keep them. A simple approach would be to include all args of all modules in RepairnatorConfig, but I think it will be quite messy as things will be mixture. So what I was proposing would be to have in RepairnatorConfig only args that are shared among more than one or all modules, and to extend this RepairnatorConfig for each module to keep args specific to each module.

In a short and practical version, what I want is to be able to call the method initConfig() in each module and after that not to do things like this.arguments.contains("whitelist") ever again, because everything would be in config, so config would be intensively used.

Hmmmm. Actually I like the idea, but I maintain we should only keep one RepairnatorConfig:

but I think it will be quite messy as things will be mixture

Not necessarily. Have a look on https://github.com/Spirals-Team/repairnator/blob/master/repairnator/scripts/set_env_variable.sh actually it should contain almost the same parameters.

Deal.


Hey Team,

It seems I cannot get this test alert to work.
Followed the Manual 1 by 1.
Azure Monitoring Agent is connected to my Azure Windows 11 VM.
Log Analytics and AMA are standard configured.
Defender for Cloud is enabled.
Thanks for any help.
Cheers
Chris

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

ID: cadad05f-dc23-7906-6679-8421a7b32b38
Version Independent ID: 81549581-e362-20c8-1516-ca8aa2101c39
Content: Alert validation in Microsoft Defender for Cloud
Content Source: articles/defender-for-cloud/alert-validation.md
Service: defender-for-cloud
GitHub Login: @bmansheim
Microsoft Alias: benmansheim

@schrauf187
Thank you for bringing this to our attention.
I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request).

@schrauf187
We are going to close this thread if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


System.Memory Error

Upgraded to 0.31 and I am getting reference errors. VS 2022 with .net 4.7.2. Downloaded from NuGet and VS references says 4.1.1. Was working with no issues.
Location: ..\packages\System.Memory.4.5.4\lib\net461
Could not load file or assembly 'System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)    at SharpCompress.Archives.GZip.GZipArchive.IsGZipFile(Stream stream)
at SharpCompress.Archives.ArchiveFactory.Open(FileInfo fileInfo, ReaderOptions options)

Code analysis shows possible MySQL Conflict?
Severity	Code	Description	Project	File	Line	Suppression State
Warning		Found conflicts between different versions of "System.Memory" that could not be resolved.
There was a conflict between "System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" and "System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51".
"System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" was chosen because it was primary and "System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" was not.
References which depend on "System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" [C:\Users\Administrator\source\repos\ImageProcessor\packages\System.Memory.4.5.4\lib\net461\System.Memory.dll].
C:\Users\Administrator\source\repos\ImageProcessor\packages\System.Memory.4.5.4\lib\net461\System.Memory.dll
Project file item includes which caused reference "C:\Users\Administrator\source\repos\ImageProcessor\packages\System.Memory.4.5.4\lib\net461\System.Memory.dll".
System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51, processorArchitecture=MSIL
References which depend on "System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" [].
C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\MySql.Data.dll
Project file item includes which caused reference "C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\MySql.Data.dll".
MySql.Data, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=c5687fc88969c44d, processorArchitecture=MSIL
C:\Users\Administrator\source\repos\ImageProcessor\packages\SharpCompress.0.31.0\lib\net461\SharpCompress.dll
Project file item includes which caused reference "C:\Users\Administrator\source\repos\ImageProcessor\packages\SharpCompress.0.31.0\lib\net461\SharpCompress.dll".
SharpCompress, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=afb0a02973931d96, processorArchitecture=MSIL
C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\Google.Protobuf.dll
Project file item includes which caused reference "C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\Google.Protobuf.dll".
MySql.Data, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=c5687fc88969c44d, processorArchitecture=MSIL
C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\ZstdNet.dll
Project file item includes which caused reference "C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\ZstdNet.dll".
MySql.Data, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=c5687fc88969c44d, processorArchitecture=MSIL
C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\K4os.Compression.LZ4.Streams.dll
Project file item includes which caused reference "C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\K4os.Compression.LZ4.Streams.dll".
MySql.Data, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=c5687fc88969c44d, processorArchitecture=MSIL
C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\K4os.Compression.LZ4.dll
Project file item includes which caused reference "C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\K4os.Compression.LZ4.dll".
MySql.Data, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=c5687fc88969c44d, processorArchitecture=MSIL
C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\K4os.Hash.xxHash.dll
Project file item includes which caused reference "C:\Program Files (x86)\MySQL\Connector NET 8.0\Assemblies\v4.5.2\K4os.Hash.xxHash.dll".
MySql.Data, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=c5687fc88969c44d, processorArchitecture=MSIL	ImageProcessor

Hopefully this helps someone else. I was able to modify the *.exe.config file to point to the older dll. (below) MySQL seems to be working still. Not sure if this is the best fix but it works.
  <dependentAssembly>
    <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>


Composer support

Very useful for quickly grabbing the latest development copy, I know connect20/strategery_infinitescroll2 is on Firegento but I feel this is a must for a modern library.

+1

@damian-pastorini could you test & merge this one and also incorporate some of the changes from PR #111 into the composer.json file?

@jzahedieh , could you update this branch so I could merge it please? Thanks!

Hi @damian-pastorini I updated the branch and resolved the conflict, I used your composer.json as it will work.
FYI it is still called Magento Cron Scheduler also the project license conflicts should be AFL not GPL?

Yes, license should be AFL and @damian-pastorini  make sure the name is correct in the composer.json file and any other files (not sure where "Magento Cron Scheduler" came from but it shouldn't be there).


Data management

:brain: the module narps_open.utils.results allows to easily download the results form NARPS teams:

# In a python script
from narps_open.utils.results import download_all_result_collections, download_result_collection

# Either download all collections
download_all_result_collections()

# Or select the ones you need
teams = ['2T6S', 'C88N', 'L1A8']
for team in teams:
    download_result_collection(team)

# From the command line

# Either download all collections
python narps_open/utils/results -a

# Or select the ones you need
python narps_open/utils/results -t 2T6S C88N L1A8

The git submodule that contains the results form NARPS teams was moved from data/neurovault/ to data/results/ for readability reasons. Its address was changed, using https instead of ssh, after a bug was identified while using ssh.
:blue_book: Documentation updates concern the results module, as well as instructions about data and software environment managment.
:microscope: tests of the results module have been added in tests/utils/test_results.py

Thanks @bclenet!  This looks good to me. My only comment is to keep in mind (maybe as an issue?) that we might want to illustrate how to use this in the contribution handbook (as discussed). (I'll let you merge once the other PRs are merged and conflicts are solved).


Dart does not work in Android x86 simulator

This issue was originally filed by<EMAIL_ADDRESS>
Dart does not work in Android x86 simulator
I'm building mojo/sky for Android Android x86 (simulator)
signal_handler_android.cc is just missing the x86 mappings, or presumably we should build the x86 file instead of the _android file in this environment.

Failure:
https://gist.github.com/eseidelGoogle/c4e7abc1dcf203197f90
This is becoming more important to us as folks are starting to use flutter more.  @johnmccutchan @zanderso

https://codereview.chromium.org/1761713002

This should be fixed by https://github.com/dart-lang/sdk/commit/7c2c02d6a6e299124946672eeaf52b71fbd74d3e. @eseidelGoogle can you verify? Thanks!

Tried to verify by doing:
$ ./sky/tools/gn --android --simulator --release
$ ninja -C out/android_sim_Release

The build no longer fails in the Dart VM, but appears to be failing in //sky/engine in various places.

I have a patch in progress.  It's mostly dart:jni fixes.  @jason-simmons.
On Thu, Mar 3, 2016 at 1:52 PM, Zachary Anderson<EMAIL_ADDRESS>wrote:

Tried to verify by doing:
$ ./sky/tools/gn --android --simulator --release
$ ninja -C out/android_sim_Release
The build no longer fails in the Dart VM, but appears to be failing in
//sky/engine in various places.
—
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/sdk/issues/23478#issuecomment-191981431.

Flutter fix in https://github.com/flutter/engine/pull/2455

I've not verified that it runs yet, only that it builds. :)


Wayland: Implement window_get_native_handle

Related to a discussion regarding OpenXR done in https://github.com/Riteo/godot/pull/4#discussion_r1467363946
This will be the most useful for stuff like OpenXR, although we'd need a way to eventually also expose the EGL handles.

Thanks!


fix(webhooks): remove 'events' API, accept payload in 'update'

Proposed changes

For body parameters expected by the PUT /webhooks/{id} API, accept the necessary payload as a parameter in the client and pass it to the HTTP request.
In addition, the unit tests as well as the mock are adjusted to return the exact status codes as given in the server's API handler, and the unhandled events API has been removed from the client and test suite.
Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
events API has been removed
[x] Test (adding missing tests or fixing existing tests)

Checklist

[x] I have read the CONTRIBUTING documentation
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works

Codecov Report

Merging #2 into develop will decrease coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop       #2      +/-   ##
===========================================
- Coverage    99.51%   99.51%   -0.01%
===========================================
  Files           23       23
  Lines          207      206       -1
  Branches        15       15
===========================================
- Hits           206      205       -1
  Misses           1        1

Impacted Files
Coverage Δ

lib/resources/v2/webhooks.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[BUG/ISSUE] (App not opening)

App is not opening correctly, showing a line instead of app window.
I don't know what causing this issue. Maybe lack of depenencies or it's bug from itself windows (windows 11 22000.9)
Please help me with this issue.
Preview: https://drive.google.com/file/d/1Nv_UWa1T21SKZIy0tp0XSB3e6eipiNIb/view?usp=sharing

Please try running the latest beta: https://github.com/marticliment/WingetUI/releases/tag/2.0.0-beta3

Tried 2.0.0-beta, same issue. I think it's a bug from windows, not from your apps. Some other uwp apps open like this. Thanks for your time.
Another preview: https://drive.google.com/file/d/1W24mZi3gd22EpTacqt_zpll3gYPvtozB/view?usp=sharing

The best I can say is to run a Health Check (https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image) on your pc; but if other UWP apps also fail, the issue is most likely to be your system


WIP: upgrade to GHC-8.10.7, drop pandoc-citeproc

Fixes #649 (CI).
CI currently looks very sad.  It basically never ran successfully.
This PR gets CI into a working state by:

Upgrading from GHC 8.10.5 to 8.10.7 and the latest stack LTS 18.28 for GHC 8.10
Dropping deprecated pandoc-citeproc, allowing newer pandoc
Skipping the processCites step in page building until solution independent of pandoc-citeproc is available
Pre-building the Agda standard library, fixing races in the site building process (locked .agdai files)
Not fixing the CI branch to dev, allowing it to run on PRs like this one.
(So, you may not see CI running on this PR before it has been merged into dev.)

In the current state (2022-05-21), CI succeeds (see https://github.com/andreasabel/plfa.github.io/actions/runs/2364301888), but there are the following loose ends / TODOs left:

[ ] Clean up, comment on the decisions
[ ] Extend CI to other platforms (Windows(?), add back macOS)
[ ] Cache cabal directory
[ ] Maybe cache Agda standard-library
[ ] Build Agda faster by turning off aggressive optimization (this would be obsolete by switching to Agda-2.6.2 which has it off by default)
[ ] Migrate the processing of citations
[ ] Fix races in site building (ADDED after CI run)
These might be fixed in the newer builders (shake/shoggoth)!?

Ad "migrating processCites":

Atm, there are only two references for self-citations, thus, I decided skipping these would not be terrible: https://github.com/plfa/plfa.github.io/blob/a798dc6a76ced81fc3fbb869861d010423e30ccb/bib/plfa.bib
I asked for migration help upstream:

https://github.com/jgm/pandoc/issues/8081

Ad "races" (ADDED):
CI still experiences races (https://github.com/plfa/plfa.github.io/runs/6543439794?check_suite_focus=true#step:19:443) which I tried to circumvent by pre-building the Agda standard library:
/home/runner/work/plfa.github.io/plfa.github.io/src/plfa/part3/Soundness.lagda.md:50,1-63
/home/runner/work/plfa.github.io/plfa.github.io/_build/<IP_ADDRESS>/agda/src/plfa/part2/Substitution.agdai:
openBinaryFile: resource busy (file is locked)

Let me know what you think / how to proceed from here.
I suggest to finally squash the commits.

Thank you! New committers need approval to run, and I've granted that. Best if Wen can approve the pull request itself. I've alerted her.

[ ]  Cache cabal directory

https://github.com/wenkokke/wenkokke.github.io/blob/dev/.github/workflows/ci.yml#L50-L67

In general, dev doesn’t include any of the fixes I implemented prior to my injury.
Switching to the latest version of Agda is trivial from the perspective of the Agda code, but required a complete overhaul of the code that calls Agda due to breaking changes in the in the library API.
I have implemented most of these changes either on a branch here or for my personal blog, though ideally they would eventually end up in the Agda codebase.
For an idea of what is generally needed, have a look at the following file:
https://github.com/wenkokke/shoggoth/blob/dev/shoggoth-agda/Shoggoth/Agda.hs
Most of the code is there to solve one of two problems:

When running the HTML or LaTeX backends, there is no option to choose the output  file name, and the output file name is not predictable from the input file name without parsing the code. (The htmlOutputPath and latexOutputPath functions.)
Agda hardcodes the links to definitions two locally generated files, which doesn’t work for the links in PLFA. The linked module allows you to redirect links on a per library basis given a canonical URL (e.g., builtins & the standard library) or arbitrarily, using a routing table (e.g., for PLFA).

The branches that I have been working on already have both of these problems fixed; dev doesn’t include any of the fixes I implemented prior to my injury.

Yes, I suspected that solutions already exist on other branches.
I was looking for the minimal work to get the current CI to function.
I agree that Agda should be better suited for applications like the PLFA book, i.e., give the user more configuration options where products should go.  There does not seem a systematic approach to configuring output directories yet.  If you have concrete suggestions, welcome to raise them on the Agda bug tracker.  Such configuration options should not be too hard to implement.
To deal with the races, my naive take would be to generate the .agdai files for PLFA prior to running hakyll.

The PLFA modules reside in src/ and have names like plfa.part1.Naturals.
The compiled interface files are located in _build/<IP_ADDRESS>/agda/src/, e.g. _build/<IP_ADDRESS>/agda/src/plfa/part1/Naturals.agdai.
Agda's native build directory layout would be _build/<IP_ADDRESS>/plfa/**/*.agdai residing in a directory which has a .agda-lib file that includes src/.

So maybe a simple minded fix would be to place a Everything.agda files in src/ with a suitable .agda-lib file. Running Agda on Everything would then produce the .agdai files which could be copied over to _build/<IP_ADDRESS>/agda/src/.
Of course, one would like Everything.agda be generated automatically, but this could be done with standard tooling (find agda files, then awk or similar).
What do you think?
I anyway wonder where the races are coming from, is hakyll running jobs in parallel?

I’m unsure; I’ve abandoned hakyll, as it doesn’t seem to be very maintained anymore.
There’s a table-of-contents file somewhere—unless that’s only in the newer branches?—which contains the filename of every linked-to Agda file. That could presumably be used.

Everything has gone quiet here. I was hopeful of getting CI working for the book. It is rather urgent, as currently changes to github are not being reflected in the available book. Please tell me what I can do to help move things along!

So I got a bit unsure about how to continue, more so as @wenkokke has been in the process of reworking the build process.
I can try to pick up the work and see if I get something working quickly, even if Wen then replaces it by something better once her injury is better.  Wen, if typing is a problem, I am happy to get a call to discuss this further (my work phone is +46 31 772 1731).

Thanks, Andreas. I think that would be fantastic. We should not let the perfect be the enemy of the good!

@wadler @wenkokke : Now I added a little script (src/typecheck-plfa.sh) that builds PLFA in Agda before the site building runs.  Locally and on my fork (https://github.com/andreasabel/plfa.github.io/runs/6661244225?check_suite_focus=true), this solves the race/locking problem with the .agdai files.
Would you please run the workflow here again so we can see if it works here as well?
If it succeeds, I can do some final polishing...

@wadler @wenkokke : Now I added a little script (src/typecheck-plfa.sh) that builds PLFA in Agda before the site building runs. Locally and on my fork (https://github.com/andreasabel/plfa.github.io/runs/6661244225?check_suite_focus=true), this solves the race/locking problem with the .agdai files.
Would you please run the workflow here again so we can see if it works here as well?
If it succeeds, I can do some final polishing...

I’m in the process of deprecating rewriting this entire build pipeline, so polishing is probably not necessary. However, could you explain the race/locking problem? I don’t think I have encountered it before.

However, could you explain the race/locking problem?

The phenomenon witnessed in the OP (see the workflow run I point to there).  I also experienced it locally when running the site builder.  I have not investigated why it arises, but creating all the .agdai files before running the site builder fixed it for me.

This is probably because the caching behavior of the current ci is completely broken. Once I have the build system working again locally I will simply copy in an entirely new ci script.

This is due to a wrong module header:

I fixed this in:

#656


Local testing documentation added to contributing.md

Signed-off-by: Ritikaa96<EMAIL_ADDRESS>This PR adds documentation for local testing HTTP Addon in the CONTRIBUTING.md including build and deploy instruction on local setup as well as load testing using k9s.
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)
[x] Any necessary documentation is added, such as:

README.md
The docs/ directory
The docs repo

Fixes #160

@arschles @tomkerkhove @asw101 PTAL


Page does not display from code

Describe the bug
I have run the code twice requesting the display and have used tokens to do so and still there is no display of a simple regsitration page for a download.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-je43qe
Steps to reproduce
Display the landing page
Expected behavior
Display the landing page to register for the download
Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 611582157,
  "usedJSHeapSize": 590611701,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = kismetaz
Chat ID = e8072ea770a8

Additional context
No response

Appreciate the feedback! This is known issue and is being tracked here: #1791.


fix: typo css property for #page-description

hmmm, thanks for the fix, but I think this is a false positive... I prefer the not bold version and we should remove this line completely.

sure!


Expected Performance with Ideal Pose

Hi,
Firstly thanks for providing this package, especially in ROS2.
My question is about usage of ideal odometry data (and the corresponding tf) for mapping purposes.
The odometry data I'm using is "ideal" in the sense that its from an RTK system with centimeter accuracy. I'm not using IMU data. However when the pose from the SLAM algorithm is updated with the pose from pointcloud matching, I can see a visible drift at the point of loop closure. So the modified_map that's generated at the end has a visible mismatch at the loop closure point (but the input odometry data is continous, without any jump)
Is there some way to increase the weight of the pose information from the odometry, or some constraint parameter?
Thanks and regards

I could provide you with a ROSBAG with RTK-GNSS ( /fix /heading) and the PointCloud of a Livox MID 70. Would that help you to program a combined function.


Error: Failed deserializing tests from specs.yaml

Example: https://github.com/paritytech/cumulus/actions/runs/3428224512/jobs/5712214909
specs.yaml:
---
name: paritytech/cumulus
description: Import from paritytech/cumulus
version: 0.0.1
labels:
  - name: A0-please_review
    description: Pull request needs code review.
    color: "666666"
  - name: A1-needs_burnin
    description: Pull request needs to be tested on a live validator node before merge. DevOps is notified via matrix
    color: c7def8
  - name: A2-insubstantial
    description: "Pull request requires no code review (e.g., a sub-repository hash update)."
    color: C6C7F8
  - name: A3-in_progress
    description: Pull request is in progress. No review needed at this stage.
    color: DBC6F8
  - name: A4-companion
    description: A PR that should be considered alongside another (usually more comprehensive and detailed) PR.
    color: F8C5E7
  - name: A5-stale
    description: Pull request did not receive any updates in a long time. No review needed at this stage. Close it.
    color: F2C5F8
  - name: A6-backport
    description: Pull request is already reviewed well in another branch.
    color: F8C5E7
  - name: B0-silent
    description: Changes should not be mentioned in any release notes
    color: F8C4D0
  - name: B1-note_worthy
    description: Changes should be noted in the release notes
    color: f9d0c4
  - name: C1-low
    description: "PR touches the given topic and has a low impact on builders."
    color: EBF7B3
  - name: C3-medium
    description: "PR touches the given topic and has a medium impact on builders.."
    color: FEF2C0
  - name: C5-high
    description: "PR touches the given topic and has a high impact on builders."
    color: D4C5F9
  - name: C7-critical
    description: "PR touches the given topic and has a critical impact on builders."
    color: E99695
  - name: D1-audited 👍
    description: PR contains changes to fund-managing logic that has been properly reviewed and externally audited.
    color: C0E7CC
  - name: D2-notlive 💤
    description: PR contains changes in a runtime directory that is not deployed to a chain that requires an audit.
    color: C209B4
  - name: D3-trivial 🧸
    description: PR contains trivial changes in a runtime directory that do not require an audit
    color: 5EDFEE
  - name: D5-nicetohaveaudit ⚠
    description: PR contains trivial changes to logic that should be properly reviewed.
    color: c5def5
  - name: D9-needsaudit 👮
    description: PR contains changes to fund-managing logic that should be properly reviewed and externally audited
    color: C3EDC0
  - name: E0-runtime_migration
    description: PR introduces code that might require downstream chains to run a runtime upgrade.
    color: c2e0c6
  - name: E1-database_migration
    description: PR introduces code that does a one-way migration of the database.
    color: f4f5f9
  - name: E2-dependencies
    description: Pull requests that update a dependency file.
    color: f2f9f2
  - name: E3-host_functions
    description: PR adds new host functions which requires a node release before a runtime upgrade.
    color: f9f2f2
  - name: E4-node_first_update
    description: This is a runtime change that will require all nodes to be update BEFORE the runtime upgrade.
    color: e8d7d7
  - name: F0-breaks_everything
    description: "This change breaks the underlying networking, sync or related and thus will cause a fork."
    color: bdadad
  - name: F1-breaks_authoring
    description: This change breaks authorities or authoring code.
    color: e99695
  - name: F2-breaks_consensus
    description: This change breaks consensus or consensus code.
    color: "5319e7"
  - name: F3-breaks_API
    description: This PR changes public API; next release should be major.
    color: cdadad
  - name: I0-consensus
    description: Issue can lead to a consensus failure.
    color: f6d9e9
  - name: I1-panic
    description: The node panics and exits without proper error handling.
    color: 17b25d
  - name: I2-security
    description: "The node fails to follow expected, security-sensitive, behaviour."
    color: d93f0b
  - name: I3-bug
    description: The node fails to follow expected behavior.
    color: "249899"
  - name: I4-annoyance
    description: "The node behaves within expectations, however this “expected behaviour” itself is at issue."
    color: D6075D
  - name: I5-tests
    description: "Tests need fixing, improving or augmenting."
    color: 6C9C98
  - name: I6-documentation
    description: "Documentation needs fixing, improving or augmenting."
    color: f48a75
  - name: I7-refactor
    description: Code needs refactoring.
    color: 0075ca
  - name: I8-footprint
    description: "An enhancement to provide a smaller (system load, memory, network or disk) footprint."
    color: "000000"
  - name: I9-optimisation
    description: An enhancement to provide better overall performance in terms of time-to-completion for a task.
    color: c5def5
  - name: J0-enhancement
    description: An additional feature request.
    color: c2e0c6
  - name: J1-meta
    description: A specific issue for grouping tasks or bugs of a specific category.
    color: a2eeef
  - name: J2-unconfirmed
    description: "Issue might be valid, but it's not yet known."
    color: "000000"
  - name: J3-intended
    description: Issue describes a behavior which turns out to work as intended. Closer should explain why.
    color: b10d11
  - name: J4-duplicate
    description: Issue is a duplicate. Closer should comment with a link to the duplicate.
    color: D62209
  - name: J5-wont_fix
    description: "Issue is in principle valid, but this project will not address it. Closer should explain why."
    color: FB3701
  - name: J6-invalid
    description: Issue is invalid. Closer should comment why.
    color: F76E02
  - name: S0-design
    description: Issue is in the design stage.
    color: f3a603
  - name: S1-implement
    description: Issue is in the implementation stage.
    color: fbca04
  - name: S2-test/monitor
    description: Issue is in the testing stage.
    color: dbea04
  - name: S3-deploy
    description: Issue is in the deployment stage
    color: 34C302
  - name: S4-blocked
    description: "Issue is blocked, see comments for further information."
    color: "122381"
  - name: T3-relay_chain
    description: This PR/Issue is related to the relay chain.
    color: ffeeee
  - name: T4-smart_contracts
    description: This PR/Issue is related to smart contracts.
    color: 0C7BAD
  - name: T5-parachains
    description: This PR/Issue is related to Parachains.
    color: 0052cc
  - name: T10-release
    description: This PR/Issue is related to topics touching the release notes.
    color: 0052cc
  - name: T7-statemint
    description: This PR/Issue is related to Statemint
    color: 86e62a
  - name: T8-CGP
    description: This PR/Issue is related to Common Good Parachains.
    color: BFDADC
  - name: T6-XCM
    description: This PR/Issue is related to XCM.
    color: d4c5f9
  - name: T9-substrate
    description: This is an issue that needs to be implemented upstream in Substrate.
    color: 1d76db
  - name: U0-drop_everything
    description: Everyone should address the issue now.
    color: "5319e7"
  - name: U1-asap
    description: "No need to stop dead in your tracks, however issue should be addressed as soon as possible."
    color: fff4ed
  - name: U2-some_time_soon
    description: Issue is worth doing soon.
    color: b60205
  - name: U3-nice_to_have
    description: Issue is worth doing eventually.
    color: FFF7ED
  - name: U4-some_day_maybe
    description: Issue might be worth doing eventually.
    color: fffbed
  - name: T0-node
    description: This PR/Issue is related to the topic “node”.
    color: fbffe0
  - name: T1-runtime
    description: This PR/Issue is related to the topic “runtime”.
    color: F5FCE6
  - name: T2-API
    description: This PR/Issue is related to APIs.
    color: 009B40

rules:
  - name: Require a single Release (B) label
    id: single_b
    tags: [PR]
    spec:
      require: !one_of [B*]

  - name: Release mentions need criticality (C)
    id: require_one_c_when_b1
    tags: [PR]
    spec:
      when: !one_of [B1]
      require: !one_of [C*]

  - name: Release mentions need a topic (T)
    id: require_one_t_when_b1
    tags: [PR]
    spec:
      when: !one_of [B1]
      require: !one_of [T*]

  - name: One single issue status (S) label allowed
    id: single_s
    tags:
    spec:
      when: !some_of [S*]
      require: !one_of [S*]

  - name: One single urgency status (U) label allowed
    id: single_u
    tags:
    spec:
      when: !some_of [U*]
      require: !one_of [U*]

  - name: One single criticality (C) label allowed
    id: single_c
    tags:
    spec:
      when: !some_of [C*]
      require: !one_of [C*]

  - name: One single audit (D) label allowed
    id: single_d
    tags: [PR]
    spec:
      when: !some_of [D*]
      require: !one_of [D*]

Command:
ruled-labels test specs.yaml

There is no issue here, you are mixing up 2 different specs.
The specs.yaml you provide as example is a spec file and can be used with the check command and a set of labels.
If you want to use the test command, you need to pass a file that has a slightly different schema and contains the tests to run against the specs.
You cannot swap one for the other.
You can find examples for both schemas in https://github.com/chevdor/ruled_labels/tree/master/tests


i2pd-2.52.0 report

mobile phone ：piexel 6 pro
By using the debug package, it can run normally
i2pd-2.52.0-arm64-v8a-debug.apk
Unable to run using release package
i2pd-2.52.0-arm64-v8a-release.apk

Check 2.53.0 at first.

2.53.0
perfect


BLD: Require numpy 2.0 for building now

This will still work with older versions of numpy, but builds wheels that can be used in either version.

Had to remove the c99 from the recent macos SDK with gcc on the new runners due to this issue when including headers from the SDK: https://github.com/orgs/Homebrew/discussions/5223


deployment broken (smtp relay option)

After a completed deployment in Azure with no completion errors i am getting a forbidden error, i have looked to initialize the database with the steps provided in the readme, but the fires were not under /home, they were under /home/site/repository and none of them could execute becuase some files were amiss (failed to open /home/install.sql)
I can find most of the installation artefacts under the site/repository, and i am using the latest build of RedCap (13.,1.35 LTS)

automation wouldnt pull the zip file, had to manually download it into container and extract


Delete settings.js

#5
Removed Empty/Unused settings.js from server source code configuration.

Sorry -- someone beat you :)


Bootstrap v5.3.2

Bootstrap has been updated to v5.3.2:
https://github.com/twbs/bootstrap/releases/tag/v5.3.2
However, since Strapdown.js also uses Bootswatch, I also need to update to Bootwatch v5.3.2. I'll wait for this.
https://github.com/thomaspark/bootswatch

https://github.com/fu-sen/strapdown/commit/e8b15726e14d043d778eccc98bc40eb0e29fdf67


valigrind shows that parseJSON() generates errors relating to uninitialised values

alex.braunegg reported this on 2020-05-10T01:15:19Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=20817
CC List

b2.temp

Description
Created attachment 1784
reproducer

Background:
===========
* Trying to determine if a memory leak exists in trying to diagnose https://github.com/abraunegg/onedrive/issues/893
* Valgrind is showing some interesting data re uninitialised values and possibly lost blocks

Valgrind errors:
================
* Use of uninitialised value of size X
* Conditional jump or move depends on uninitialised value(s)
* Uninitialised value was created by a stack allocation

Files Attached:
===============
* main.d (reproducer)
* valgrind-out-202005101049.txt (valgrind output)
* make_with_dmd.sh (compile & test with valgrind)

Questions:
==========
Is this a valid bug? I have looked through json.d and to me, everything looks like it gets initialised correctly.

!!!There are attachements in the bugzilla issue that have not been copied over!!!

alex.braunegg commented on 2020-05-10T01:16:25Z
Created attachment 1786
compile & run valgrind

b2.temp commented on 2020-05-24T07:01:01Z
The report is valid. I also see the same report (+ a 112 bytes leak) on x86_64. But this is either a druntime bug (GC) or phobos (std.json)

alex.braunegg commented on 2020-05-10T01:15:55Z
Created attachment 1785
valgrind output


MLPAB-2378: Add voucher-acted event

Enables MLPAB-2378.

Closing until we define if Sirius needs this.


Change the stored seed to a seed based on a hash to improve build resiliance

Thought that I will just put on the table. Changing the stored seed to a seed generator to make each test class to have its own seed, but still make it deterministic. Have a number of builds which seem to fail randomly, so this might help in making the builds more predictable. But we don't wan't all tests to use one seed, because that might hide a lot of bugs. So generate a seed per test class, but still use the same seed for the tests.

Pulling this one back untill its more clear what keeps failing in the build.

See if I can include #66 in this set.

Adding same kind seed generation to QuantumSimulatorTestTargets.cs. Don't want to make a dependency between these two or add a utility library yet (bit overkill for one method).


Landsat 8 SPARCS Cloud (1.4GB)

Landsat 7: https://www.usgs.gov/core-science-systems/nli/landsat/spatial-procedures-automated-removal-cloud-and-shadow-sparcs

@juannat7 @ryzary added to board


How do i read data in batches from kafka-node?

How do i read data in batches from kafka let's say an array of 10 messages from Kafka, Perform some opertions on those 10 messages, then get another 10, and process goes on.
I have tried few approaches but nothing is helping me
Approach 1: Just a basic logic by putting records in an array and pausing the consumer until that activity is performed and then resuming the consumer
	import kafka from "kafka-node"

	const client = new kafka.Client("localhost:2181");

	const topics = [
	    {
	        topic: "webevents4"
	    }
	];
	const options = {
	    autoCommit: false,
	    fetchMaxWaitMs: 1000,
	    fetchMaxBytes: 100,
	    encoding: "utf-8",
	    //offset:true
	    fromOffset: false,
	};

	// console.log("here");

	const consumer = new kafka.Consumer(client, topics, options);

	let notification_batch_max_size=5;
	let notification_batch = [];

	consumer.on("message", function(message) {

		if(notification_batch.length<notification_batch_max_size){
	 			notification_batch.push(message);
	 		}
	 	else{

	 		function someHeavyActivity(time, callback) {
	 			consumer.close(function(err,data) {});
	 			consumer.commit(function(err,data) {

	 			})
			    var stop = new Date().getTime();
			    while(new Date().getTime() < stop + time) {
			        ;
			    }
			    notification_batch = [];
                                consumer.resume();
			}
			someHeavyActivity(20000);
	});

	consumer.on("error", function(err) {
	    console.log("error", err);
	});

	process.on("SIGINT", function() {
	    consumer.close(true, function() {
	        process.exit();
	    });
	});

Approach 2: Using the Consumer Stream
            import kafka from "kafka-node"

	const client = new kafka.Client("localhost:2181");

	const topics = [
	    {
	        topic: "webevents4",
	        highWaterMark:2,
	        offset: 0, //default 0
	        partition: 0 // default 0
	    }
	];
	const options = {
	    autoCommit: true,
	    fetchMaxWaitMs: 1000,
	    fetchMaxBytes: 1024 * 1024,
	    encoding: "utf8",

	    fromOffset: true,
	};

	const consumer = new kafka.ConsumerStream(client, topics, options);
        consumer.setEncoding('UTF8');

	let data ="";
	consumer.on('data', function(chunk) {

	   if (chunk !== null && typeof chunk === 'object') {
	    try { chunk = JSON.stringify(chunk) } catch (e) { next(e) }
	  }
	  console.log(chunk.toString());
	   data += chunk;

	});

Approach 3: Transform Stream with ConsumerStream
	import kafka from "kafka-node"

	const client = new kafka.Client("localhost:2181");

	const topics = [
	    {
	        topic: "webevents4",
	        highWaterMark:2,
	        offset: 0, //default 0
	        partition: 0 // default 0
	    }
	];
	const options = {
	    autoCommit: true,
	    fetchMaxWaitMs: 1000,
	    fetchMaxBytes: 1024 * 1024,
	    encoding: "utf8",
	    //offset:true
	    fromOffset: true,
	};

	const consumer = new kafka.ConsumerStream(client, topics, options);

	const Transform = require('stream').Transform;
	const messageTransform = new Transform({
	  objectMode: true,
	  decodeStrings: true,
	  transform (message, encoding, callback) {

	    console.log(`Received message ${message.value} transforming input`);

	  }
	});

	consumer.on("error", function(err) {
	    console.log("error", err);
	});

	process.on("SIGINT", function() {
	    consumer.close(true, function() {
	        process.exit();
	    });
	});

	consumer.pipe(messageTransform);

Any help and guidance will be much appreciated.
Thanks

I have an additional scenario in this , what if while processing those 10 messages something goes wrong in the system. But I have processed 5 of them and I want to commit those 5. So that next time when consuming starts is reads from 6th message.
How this can be achieved through autocommit set to false and using consumer.commit() function.
Please help with this .

While using consumer group stream on autocommit true . This is not working

From: Xiaoxin Lu<EMAIL_ADDRESS>Sent: Tuesday, April 24, 2018 12:41:13 AM
To: SOHU-Co/kafka-node
Cc: Khushboo Katta; Manual
Subject: Re: [SOHU-Co/kafka-node] How do i read data in batches from kafka-node? (#943)
Try using a ConsumerGroupStream.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/SOHU-Co/kafka-node/issues/943#issuecomment-383689190, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATIWejGWPJNbkS7ZuVbyAjvu_vav80Mmks5tridRgaJpZM4Tekgu.

@hyperlink  is that the solution to my problem, basically batches of 10.

@sunil-lulla that is what I would recommend. You can read the stream in paused mode.

@hyperlink Do I need to use Streams at Producer as well, or using only at Consumer will work?

It's up to you @sunil-lulla. The reason I recommend the ConsumerGroupStream for consumer is because of the feature that it will only commit what you have read from the stream.

@sunil-lulla could you suggest what was your final approach? I am also in the same situation where I want to read a batch and then pause, once those are processed, then take next batch. Also, if you can share sample code for the same.

I followed the first approach by @sunil-lulla  and I have the following code:
`
consumer.resume();
const events = [];
consumer.on('message', msg => {
events.push(msg.value);
});
    setTimeout(() => {
        consumer.pause();
        console.log(`${events.length} messages found`);
        let count = 0;
        for (let i = 0; i < events.length; i += 10) {
            const subEvents = events.slice(i, i + 10);
            for (const event of subEvents) {
                const userEvent = JSON.parse(event);
                new UserEventsModel(userEvent).save().then(() => {
                    count++;
                    console.log(`${((count / events.length) * 100).toFixed(2)}% events saved`);
                });
            }
        }
    }, 3 * 1000);

`
This code runs inside of a cron job. The issue here is that the onMessage callback is still executing once the consumer pauses. Also it doesn't catch up with messages that were there in the topic partition already but were not processed by the consumer yet. Any suggestions on this?

@hyperlink is that the solution to my problem, basically batches of 10.

is this problem resolved? please suggest me.

You can use ConsumerGroupStream with async.queue  , pushing items to the queue.


Match UI

@szhan @hyanwong this adds the ability to run a the HMM matching for a given set of strains and parameters against an ARG. Run it like:
python3 -m sc2ts run-match [alignments DB path] [ts/tsz path] --direction=reverse ERR4206593

The output is one line of JSON per strain. I think we'll probably use this later for updating the ARG, so we can split up the part of doing the matching and updating for the large bulk updates we'll want to do later on.
For now, this should help explore things like the origins of Alpha, and to think about what would happen if we added in specific samples after the fact.


Rounding error above a threshold

Description
Dear Jax team,
I am working with large floats using jax.numpy and noticed this:
a = 30303020.99
print(jnp.round(a))
print(np.round(a))

OUT
30303020.0
30303021.0

Numpy has the correct value while Jax's Numpy is wrong. It seems to be related to float representation in Jax since:
a = jnp.float64(30303020.99) (or float32)
print(jnp.round(a))
print(np.round(a))

OUT
30303020.0
30303020.0

The above example is an arbitrary number, but the threshold above which this error appears seems to be 16777216 as:
a = jnp.float32(15040300.99)

print(jnp.round(a))
print(np.round(a))

OUT
15040301.0
15040301.0

These rounding error passing above the threshold led to very tricky bugs to find in my code, thanks in advance for your help!
What jax/jaxlib version are you using?
jax 0.3.21, jaxlib 0.3.20
Which accelerator(s) are you using?
CPU/GPU/TPU
Additional system info
Python 3.9.12 but also tested on other versions like 3.8.xx
NVIDIA GPU info
My issue has been tested on CPU/GPU/TPU

Just found the solution to my problem, I should have:
from jax.config import config
config.update("jax_enable_x64", True)

Because jax opertaes in float32 anyway if you don't do this. While it is clearly stated in the doc, I find it a little bit difficult to know as it can lead to sneaky bugs in your code.


[IOTDB-3083] DataNode AuthorInfo cache

DataNode AuthorInfo cache

Is this PR also used to implement the ShowChildNode and ShowChildPath ?
From the description, it seems that this PR is only used to implement the AuthCache part.
It is better to separate them as two PRs. By the way, the implementation of ShowChildNode seems not complete and the DistributionPlanner part is lost.

Is this PR also used to implement the ShowChildNode and ShowChildPath ?
From the description, it seems that this PR is only used to implement the AuthCache part.
It is better to separate them as two PRs. By the way, the implementation of ShowChildNode seems not complete and the DistributionPlanner part is lost.

The feature ShowChildNode and ShowChildPath is in another pr, not this. The DistributionPlanner part will be completed in next pr along with CountNodes.


Consider exposing calculateSpecificityOfSelectorObject

As per request by @bartveneman on Twitter:

Would be nice to expose calculateSpecificityOfSelectorObject so we can avoid convertToAST -> typeof source -> source instanceof Object -> source.type == 'Selector'
https://github.com/bramus/specificity/blob/12557b78948bb4cb6438ac51e4c81c850cde5a4e/src/core/calculate.js#L5
This adds up quickly on several thousands of selectors like on our website.

Considered this in the past but hadn’t done set yet because I’m not too happy with the name of the function. Open to suggestions for a shorter - yet also clear - name. If no alternative can be found, then I’m fine with exposing as is.

Maybe calculateFromAstNode or calculateSelectorNode, calculateNode? The return type is Specificity, so no real need to include that in the function name.

1 more way to improve this function is to allow our own csstree walker. Project Wallace is powered by CSSTree too, so we already have a walker function available, next to the full AST. If we could expose a function that would accept a walk function and a Selector Node, that'd be 💯 , because there will not be conflict issues when our versions of CSSTree are different. function getSpeficiticity({ walker, node }) {}

Ah, sorry, misread the code: it doesn't use an AST walker, it just loops over some of the nodes 😬. So that already makes it pretty lightweight. The only dependency it seems to have is the max function and it returns a new Specificity at the end, which we maybe can skip?


Unity Runtime node editor added

Thank you for your suggestion, but it was already added into Node Graph section, not sure you want to change its title or description or category or not.

Ah, it's added already :) Well, I'm surprised that someone added before me. Thanks!


remove strange assignment

There is no need in this line documentRef = document;

You're right. I think that was a botched copy/paste job. Thanks!


add module for NanoPlot

Add NanoPlot to the gpu-basecalling workflow to run after basecalling finishes below this line: https://github.com/lskatz/nanoporeWorkflow/blob/228abfd6a790c67a5d4a468fafca64b8896876fe/workflows/run_01_basecall-w-gpu.sh#L122
# np_basecall-w-gpu.sh sets the job ID to always be set as 'guppy-gpu'
# therefore, hold this job on that jobID before running NanoPlot
qsub -hold_jid guppy-gpu -o log/nanoplot.log -j y ${thisDir}/../scripts/np_runsummary_nanoplot.sh

Need to make a new script, np_runsummary_nanoplot.sh which includes something like this:
# standard command
NanoPlot --summary sequencing_summary.txt --loglength -o nanoplot/ -t 24 --N50 -p N20169-20-003
# broken down by barcode
NanoPlot --summary sequencing_summary.txt --loglength --barcoded -o nanoplot-barcoded/ -t 24 --N50 -p N20169-20-003

Might be good to experiment with this flag with NanoPlot:
--drop_outliers       Drop outlier reads with extreme long length.
Either that, or drop the --loglength flag

After some experimentation, my preferred nanoplot cmd and params is this:
runID=N20169-20-004
NanoPlot -t $NSLOTS --summary sequencing_summary.txt --loglength --N50 --prefix $runID -o nanoplot --maxlength 100000

--drop_outliers removes too much of the longer reads. It cut out everything above 25kb (different depending on the run, of course)

Done in https://github.com/lskatz/nanoporeWorkflow/commit/28cf476c0e18dbadf5cc65ad724bb68aa1e690cb


Build Revery is presenting failure in shell.c

RHEL 8.3 - 4.18.0-240.15.1.el8_3.x86_64:

Revery Version: Trying to build commit 26e8b73

OCaml version: esy 0.6.8 built-in

Native, Bytecode, or JS build: Native

Steps to reproduce:

Install all required dependencies: (OK)
cmake
ragel
nasm
libpng-devel
bzip2-devel
libX11-devel
mesa-libGLU-devel
harfbuzz-devel
libXext-devel
fontconfig-devel
nasm
m4
libXrandr-devel
libXi-devel
libXcursor-devel
libXinerama-devel
libXxf86vm-devel
Clone Revery repo (OK)
cd into it (OK)
Run esy install (OK)
Run esy build (BAD)

Actual Result:
Exit error log (after run esy build in / of Revery):
issue-log.txt

Expected Result:
Some Warnings and Build Successful.

Search terms used: Red Hat, RHEL 8, RHEL, Fedora, shell.c.

In the revery directory do grep -r Werror and replace all results with Wno-error

Can you add #include "utilities.h"in shell.c


Blocked at "loading" screen - how to reset the app / cache ?

After playing a bit with the app, it now stays in "Loading" state at startup (see screenshot)
I tried to remove the cache in ~/Library/Application Support/hf-diffusion-models but it just cause a re-download.
How can I reset the app, delete all files created and start like on a fresh machine again ?
Alternatively, how can I pass the "Loading" screen ?

Hello, it may take some time to load a model. I have IPhone 15 Pro and sometimes it takes about 250 seconds


Fixes some 'Attempted to free invalid ID' warnings in mobile renderer

Fix _free_render_buffer_data freeing half_texture and half_fb the mipmap array of both blur structs when switching scenes. During assignment, half_texture and half_fb in each of the mipmaps of both arrays are assigned the same texture and framebuffer, and since _free_render_buffer_data attempts to free both, the engine throws up a warning since they have already been erased in the first blur struct.
Fixes #51752

Thanks!


Add qTox 1.16.3

Closes lukesampson/scoop#2959

Just a question, should we change the qtox.ini when installing to make qtox be portable? I want to know what the rule is, thanks.


Add JsonExtract udf

What this PR does / why we need it:
JsonExtract computation function is added which can be used to extract values using two different JsonPath.
For example, given this JSON:
{
   "details": "{\"merchant_id\": 9001}",
}

The method JsonExtract("$.details", "$.merchant_id") can be used to extract 9001.
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

Checklist

[X] Added unit test, integration, and/or e2e tests
[X] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduce API changes

Please add documentation for supported entity extractions (JSON Path and UDF (Geohash, JsonExtract)) here: https://github.com/gojek/merlin/blob/main/docs/user-guide/transformer.md

Please add some test cases on Test_buildEntitiesRequest as well:
https://github.com/gojek/merlin/blob/main/api/pkg/transformer/feast/transformer_test.go#L556

@ariefrahmansyah @pradithya Addressed review comments.

Created a PR to allow PRs to trigger GH action from forked repository: https://github.com/gojek/merlin/pull/85

Workflow was not working: https://www.githubstatus.com/incidents/xn0sd2x4nd7f


Add HTTP Logging Explanation

Description
Adds documentation explaining how to enable HTTP request and response logging and high-level configurations available.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Update pkgs and add missing

Update oc to stable-4.14
openshift-tests are missing some tools
such as diff and git. The tests
image also has python3-six

this needs testing

Hi @jcpowermac , reviewing this change, looks like the most recent plugin refact, changing the plugin architecture by running openshift-tests inside it's own container provided by payload may resolve this issue by removing the needed to install diff and git.
I can't see anymore the failures in kubernetes/conformance running the v0.5+. Do you think we can close this one?


Master branch failed with : 'Config' object has no attribute 'get_disks_id_exclude'

@wefixit-AT could you please revert PR #83  from master and merge it to ovirt4.3?
because PR #83 depends on PR #70 which merged to branch ovirt4.3.
now in master branch, I got the following error:
!!! Got unexpected exception: 'Config' object has no attribute 'get_disks_id_exclude'

@wefixit-AT could you please revert PR #83 from master and merge it to ovirt4.3?
because PR #83 depends on PR #70 which merged to branch ovirt4.3.
now in master branch, I got the following error: !!! Got unexpected exception: 'Config' object has no attribute 'get_disks_id_exclude'

You need to add a parameter to config, an example is in config_example.cfg
# an array of exclude disks id,exampel ["6d811aa25-52a1-45c3-9f40-1c7c868182c9","6e78d7c2-5786-4dz2-a966-fd308c23f08e"]
disks_id_exclude: []

Hi, I add disks_id_exclude: [] to config file. But it doesn't fix.  Got unexpected exception: 'Config' object has no attribute 'get_disks_id_exclude'.

A little update. Your master branch does not contain info in config.py about disks_id_exclude: [], also there is no mention about it in config_example.cfg.  But they exist in 4.3 branch.

Hi @Dankhatskevich
This issue should be fixed in:
https://github.com/wefixit-AT/oVirtBackup/pull/87
Please try to use it

Hello everyone, I can't get the script to work on version 4.5.4 gives the same error 'Config' object has no attribute 'get_disks_id_exclude'


Design Brief

@todo
Getting to know more about dat-ecosystem (WK1)

[ ] Videos to watch (3 hours)
Watch All in a day and relate questions to Sarapath and his team in video format if neccesary
@input :factory: old conference videos from #issue 3
@input :package: dat-ecosystem project screencast
@input :package: example project screencast "datdot-ui"
@input :package: example project screencast "wizardamigos"
@input :package: github issue management system
[ ]  Materials to read (1 hour)
@input :factory: current dat-ecosystem website: https://dat-ecosystem.org
@input :factory: dat-ecosystem as a garden Vision/Mission
@input :factory: Inspiration1
@input :factory: dat-ecosystem twitter account
@input :factory: list of historic dat ecosystem projects
@input :factory: more dat ecosystem projects
@input :factory: website section for organizing structure and processes
@input :package: initial dat whitepaper
@input :package: dat design
@input :package: dat colors
[ ]  Make a design brief document about the dat ecosystem (3 days)
@output :question: Design brief document

Next #39

@info
Note: Information gathered above will help us create a design brief document which is very important for us not to get clouded.

feedback 2022.04.28
looks good to me

but you have a todo Videos to watch (3 hours) whith an input that has a check box, but the input should have no check box and if you want it, then make multiple todos each with an input and mark the todos as done

same for the next list of inputs which should not have checkboxes and if you want that then make an additional todo for each input and mark that instead of the todo.

there is a next label that is not a sub bullet point of an @output and in general this issue does not create any outputs, which means it should not have next and if an issue or todos create no outputs at all we have no reasons to do any of the todos in the first place, so you need to add at least one output :-)

merged into #49


fix usage of saveMode via the clean flag

Tweaked description of clean flag to make its usage clearer.
Made sure to do a not on the flag since $saveMode = false is what will clean out the database of unneeded assets. So, not providing the --clean flag will mean that we only update the tables that have changed and leave everything else as is.
Make sure the clean flag is used when actually updating the schema and not just used to get the SQL.

I wanted to do the same but I found this p-r. Please Merge it as it is very helpful when migrating app from Eloquent to Doctrine. Lost my DB twice before found this bug.


Support to view AP for each class

Hi all,
It seems that current coco_error_analysis.py does not support to view class-wise mAP, so I just add some code in the coco_error_analysis.py to support it.
I add an option named --with_ap, it will behave as before and calculate class-wise mAP if --with_ap command is used when running the script.

I ran your program to evaluate mAP of each class of faster r50, and compare it with the result of codalab. However, the result of two are not the same. For example, this is the result of person category of two:
Your program:
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.522
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.835
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.554
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.366
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.598
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.667
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.180
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.523
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.598
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.451
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.663
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.740

Codalab:
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.512
 Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.816
 Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.545
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.347
 Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.590
 Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.663
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.180
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.523
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.598
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.451
 Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.663
 Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.740

Please have a check about that to ensure the evaluation program is logic correct.


Information missing in the AST due to string concatenation

The AST is relatively faithful to the input file and contains a lot of information (locations, raw data). One notable exception is due to an optimization in the parser: "a" + "b" is replaced with "ab".
Is there a way to preserve this information?
Maybe optimizations on the AST could be done in a separate pass (in case we want to do other things like this)?

Currently there is not, but I agree optimizations should be done as an optional separate pass, perhaps by the resolver (or by the bytecode compiler if I ever decide to commit it).

I've committed the compiler (https://github.com/google/skylark/pull/95) and sent a PR to move the string-concatenation optimization out of the parser (https://github.com/google/skylark/pull/97).

Fixed now.

Thanks!


Add option to force increasing permissions on dry-run

Is your feature request related to a problem?
When running the dry-run, I noticed it got an output of ~10GB(forgot to screenshot) and after running, it reported cleaning 99GB.

Additional Context
What I noticed is that the only difference on the runs is that the actual run asked for my password, so I got investigating the code a bit and this bit of code seems to be the "problem"/masking the difference:
                except (PermissionError, FileNotFoundError):
                    continue

What do you think of adding a option to force it to get all the permissions for dry-run too?
Also great work on this project! Simple and effective ❤

Hey 👋🏻
I'll try to improve it, but on the first look it doesn't seems to be possible.
If you have a solution tho, you are welcome to fix this 😉

@athossampayo
I looked a bit into the issue, there is no way to increase privileges of python script mid run.
But you can always run it with sudo and problem will go away.
I'll close the issue for now but you are welcome to reopen it if problem persists with sudo


[build] Make raylib available in package managers

This issue is a follow up of #401 . Just moved to a new issue flor clearness.
Currently supported package managers:

[x] macOS - Homebrew
[ ] Windows - Chocolatey
[x] Windows - vcpkg
[x] Linux - openSUSE
[x] Linux - Arch User Repositories (AUR)
[x] Linux - Linuxbrew
[ ] Linux - Gentoo
[ ] Linux - Debian
[x] BSD - FreeBSD

If you are able and willing to help, you're welcome!

Just noticed that openSUSE (@jubalh) and Arch (@nounoursheureux) are not updated to raylib 2.0, still 1.8.

@raysan5 thats wrong. openSUSE Tumbleweed is updated to 2.0 on 24th July in the devel project https://build.opensuse.org/package/show/devel:libraries:c_c++/raylib.  From then it goes through test rounds and landed on 28 July on Factory project. And from there will be shipped in the next snapshot.

@jubalh oh, sorry! just look for it on the net and found that version... Thanks for the update! 👍 😄

I have experience doing debian packaging; I can offer my assistance for this.  Though, I do want you to know that there are MANY different options to do this.  Though this library is open source, I'd recommend creating a binary package (as they are a tad simplier to work with).
What's the status though on the CMake stuff?  I know I helped with it a while back, but I'm really out of the loop on it.  There does exist a command in CMake to generate the debian stuffs: https://cmake.org/cmake/help/v3.0/module/CPackDeb.html

There does exist a command in CMake to generate the debian stuffs

CI is configured to push a binary package (tarball) to the Github releases page whenever a new release is tagged, so we could use that. Anyone interested in trying to get it into the official repositories?

I'll work on the Debian package even though I'm new to it, but if someone more experience would like to help feel free to chime in.

There are a couple issues making packaging a bit bothersome:

The binary tarball is small, but it cannot be used to create a package; everything must be built from source.
Using the snapshot tarball from GitHub will work but it has a lot of extra pre-built stuff in the release directory that we don't want. It seems like this sort of stuff should be on a separate branch or repo, or just left to the GitHub releases page.
Would be nice to have a release with #608 since it fixes not only CMake issues, but building against the latest glfw release.

Now that we have CI and automatic release generation, maybe we can avoid release folder?
Probably build system needs to be updated to output to some default system folder?

A 2.1 or 2.1-dev release would be good from my PoV.  It'd get the extra keyboard keys added today out "into circulation" faster. :smile:

releases directory removed in commit https://github.com/raysan5/raylib/commit/d6241d18abdfa723563d62cede22795d6548bd6a
Makefile outputs to RAYLIB_RELEASE_PATH automatically on building.

No worries at all. :smile:

One more: https://github.com/Microsoft/vcpkg/pull/5946

Nice one! Already wanted to do the vcpkg myself :)

The Arch Linux package has been moved from the AUR to the official repository ! I am no longer the maintainer.

@wbrbr oh! nice! is someone going to update it to latest release?

Yes the new maintainer should do it soon since it has been flagged as out of date. I can't give you more details because I don't know them haha

I am wondering if we should start incrementing SOVERSION every 2.x release to prevent applications dynamically linked against one raylib version from having a later, backwards incompatible, raylib loaded. Thoughts?

I am wondering if we should start incrementing SOVERSION every 2.x release to prevent applications dynamically linked against one raylib version from having a later, backwards incompatible, raylib loaded. Thoughts?

I am saying this since years  (on various issues here and on the chat) :-)

I was thinking in a way to increment API version consistently with library version.
Considering API and ABI are very prone to changes, maybe we can just use RAYLIB_API_VERSION = 250 and increase that number aligned with 2.5.0. What do you think?

@raysan5 incrementing API version directly after a release would allow the git version to be installed alongside the released version and binaries linked against an old version or explicitly requesting the released version would continue to work.
If we increment before the release, this wouldn't work.

What we could do is set to 251 now, 260 on release and 261 directly after... ? (granted that 2.6.0 is the next version)

How often should we increase the revision number? I mean, 252-253-254...

@raysan5 What we absolutely want is for every release to have a different API version. A different API version for the git trunk is nice to have because issue reporters are often told to try the newest git snapshot, so we shouldn't accidentally break their already linked applications if they install from git.
Breakage will still happen, if you install an unreleased git snapshot, dynamically link, and come back later to install a newer version from git. But if you do that, we'll assume you're experienced enough to expect breakage and to deal with it.
To sum up:

Just before tagging the release:

set software version to new version
set API version to software version / 100

Directly after tagging the release:

increment API version by one

Both commits can be done together.

@a3f ok, I understand, it looks ok this way.

AppGet for Windows is missing from the list.

@elitepleb oh! looks nice! :D

Might look at some of the opensuse packaging to make a fedora copr repo, no promises though.

raylib is already available in some package managers. I think this issue is not the best way to track those packages... Closing the issue.

is a Raylib package available on Debian?

is a Raylib package available on Debian?
No it is not.
Here you can see where it is available: https://repology.org/project/raylib/versions

I know this issues is closed, but it would be really awesome if a Debian package could be created, given that apt is one the most common and widely used package managers.

@ranguli Sure! Feel free to add it!

Hello there,
I've developed an ebuild for Portage in Gentoo, and I'm considering making it available to the community. While it's not public yet, I'm keen to gauge interest. If there's interest, I'll be happy to maintain it and potentially work on getting it included in the official upstream repository.
Please let me know if you'd be interested in this ebuild, and if you have any advice on the process of contributing to the official upstream, I'd greatly appreciate your guidance.
Thank you for your time and consideration!

Please let me know if you'd be interested in this ebuild

You don't need to ask it raylib upstream. Just push it there.

if you have any advice on the process of contributing to the official upstream, I'd greatly appreciate your guidance

It's pretty well documented:
https://wiki.gentoo.org/wiki/Proxied_Maintainer_FAQ
https://wiki.gentoo.org/wiki/GitHub_Pull_Requests
Let me know if you need more help.

Would it be a good idea to link the the Arch official repo instead?
Current link to the AUR does not exist. I can see how this might create an issue here and there.

In the readme we have a repology badge that links to:
https://repology.org/project/raylib/versions
Where people can see all repos.

@jubalh That badge is actually amazing! It would be nice if more packages were updated to 5.0.

Yes, FreeBSD and Guix seem out of date for example
But some of the outdated ones are also older/released distros, like openSUSE Leap 15.1 or nixpkgs stable 21.11. So those are normal :)

In the readme we have a repology badge that links to: https://repology.org/project/raylib/versions
Where people can see all repos.

I'm not sure how to get to that link from the README. All I found was this thread. But, if the information is there and I'm just too dumb to find it, that's ok.

I'm not sure how to get to that link from the README

You go to the README. You look at the badges on top. You click on in repositories

Got it. Well, if it won't cause any trouble. then it should be fine. Sorry for the inconveniences.


Move to jupyter_sphinx for executing code snippets

Summary
Move to jupyter_sphinx for executing code snippets in getting_started and install.
Details and comments

can you show a screen shot

Here is a sub-section.  The code in the docs is now executed at build via Jupyter.  This gets around some issues with the other IPython version that was making figures not display correctly.

@jaygambetta we good?


Integer support for the basic Math nodes.

It would be good to take a pass at improving the integer support in MaterialX's math nodes. Having these low-level building-blocks would improve the types of nodegraphs that can be expressed.

Node
Input
Output

Add
integer, integer
integer

Add
integer, float
integer

Subtract
integer, integer
integer

Subtract
integer, float
integer

Multiply
integer, integer
integer

Multiply
Integer, float
integer

Divide
integer, integer
integer

Divide
integer, float
integer

Min
integer, integer
integer

Max
integer, integer
integer

I'm not sure if there are other options necessary. Or if we need to do things like Vector (I) signatures...

I would disagree with having e.g. an "Add" with integer and float inputs, and certainly with having that combination produce an integer output.  Instead, I would suggest we only have same-type inputs and outputs for the nodes themselves, and refine the "auto convert" logic to insert conversion nodes (int to float "convert", or "floor(float) with int output") when someone wants to connect a different type to an input, similar in concept to what we do with swizzle/extract or colorspace-convert on input.
Not sure about how useful integer vector types would be- do you have any use cases in mind?

Thanks @dbsmythe - that all makes sense. The integer-vector types was more about vec3 * int cases - and only for the sake of completeness. If the math nodes only supported integer inputs and outputs, that's perfectly fine by me. As you pointed out, (in the future) integer-aware floor and ceil, along with future round can take care of float-to-int cases.

Linking this issue to the recent work from @ld-kerley on #1777 and #1786.

Thanks for this original proposal, @crydalch, and I think that we can close this out, as a good fraction of this work has been implemented in MaterialX 1.39.  Feel free to post additional ideas for integer math improvements in new GitHub Issues.


fix: Circular import caused by invite class.

What type of pull request is this?

[x] Non-breaking code change
[ ] Breaking code change
[ ] Documentation change/addition

Description

Changes

Checklist

[x] I've formatted my code with Black
[x] I've ensured my code works on Python 3.10.x
[ ] I've tested my code

What about line 77?

✅Works


GCD-Euclid's Algorithm

Compute HCF(GCD) & LCM
Before making PR check this...
Please add your image in image folder nd update readme.md file this is for all contributorsdo this then only i will be able to merge PR Check this
#90 (comment)
File format:-
EuclidsAlgorithm/CPP/HCF_And_LCM.c++

I will do this in C++. Can you please assign it to me?

@zahinekbal PR is ready here: https://github.com/zahinekbal/codeWith-hacktoberfest/pull/141 :pray:


Module level noop

I really think the approach I have in the code is the right one.    The wandb objects should be backed by regular dicts, and return useful information so the codepath still works as expected.

Running a final test on this PR:
WANDB_MODE=offline ./do-main-regression.sh --spec :~base: --cli_branch fr_noop | tee regression-offline.txt

🤞


Fix customization instructions

Summary
Fix sample code in customization instructions on website for these two sections:

Initializing gql.tada manually
Customizing scalar types

This seems out-of-date to me, as @0no-co/graphqlsp now outputs a different format. Basically it adds an export type there, so the d.ts output outputs a type, while the .ts output outpus a value.
Did you make sure to try this out with the latest version's output? ✌
(You can now also output it with the CLI)

Hey @kitten! Yes, this is against the latest version of @0no-co/graphqlsp and gql.tada
Good point about the .d.ts vs .ts files. These instructions are for customizing, so the examples should be using a .ts file
Instructions/comment from a .d.ts file:
/** An IntrospectionQuery representation of your schema.
 *
 * @remarks
 * This is an introspection of your schema saved as a file by GraphQLSP.
 * It will automatically be used by `gql.tada` to infer the types of your GraphQL documents.
 * If you need to reuse this data or update your `scalars`, update `tadaOutputLocation` to
 * instead save to a .ts instead of a .d.ts file.
 */

I updated the examples in this PR to import from a .ts file as well

That doesn't seem quite right though, sorry 😅 ❤
The important detail here is that the docs explicitly recommend saving the introspection to a .d.ts file, which outputs the introspection as a type. So, your change explicitly only works if a user was to switch to a .ts output, which isn't mentioned in the docs at that point yet.
Instead, the intention is that this is only mentioned once you get to this file: https://gql-tada.0no.co/reference/graphqlsp-config/#tadaoutputlocation
That's a change we had to make because:

the .d.ts format is a lot more efficient for TS to parse and process, and export type simply makes more sense there
the .ts format was already used by some folks at that point and the intention there is that it's usable by value (however, the original instructions did show typeof)
the .d.ts format is likely going to diverge further so less work is done by the type inference in introspection.ts, but that's a little besides the point

Hope that makes sense ❤

Hmm.. two questions:
One of the two sections I updated is titled Customizing scalar types
How would someone go about customizing scalars etc. with the .d.ts file?
I'm also working with a multi-schema monorepo (3 applications interacting with 3 different GraphQL APIs)
This type of setup is mentioned in the other section I updated here titled Initializing gql.tada manually
How would someone achieve this with a .d.ts file?

I'm also working with a multi-schema monorepo

This isn't supported yet 🥲 It's unfortunately a little tricky. That's because GraphQLSP cannot differentiate between schemas and doesn't know which schema to check against for any given document.
We have an idea for addressing this, but that may take us a bit of time.
The way to address this for now is to instantiate gql.tada multiple times, i.e. passing different schemas to initGraphQLTada<>(). It doesn't matter where the schema lives, so that means you can write multiple graphql-env.d.ts files, e.g. schema-1.d.ts, and so on.
However, currently, there's no mechanism to generate these separately, unless you were to isolate the instances of gql.tada in faux-packages/monorepo packages with their own tsconfig.jsons and used either GraphQLSP just in that package or by using the CLI there.
In short, multi-schema use-cases aren't supported yet.
I'm very eager to make these happen though. While we can talk a lot about how ideally an organisation shouldn't have multiple schemas they're consuming, since those often cross boundaries and this opens you up to having apps that also consume multiple schemas (which starts defeating the point of GraphQL pretty hard),
I ran into this myself in a simple case too with a monorepo that both had a GraphQL schema but also consumed a third-party GraphQL schema.
Anyway, that's a little off topic ❤ Maybe better suited for Discord (where this question was also asked, I believe)
Closing for now

This isn't supported yet 🥲 It's unfortunately a little tricky. That's because GraphQLSP cannot differentiate between schemas and doesn't know which schema to check against for any given document.
We have an idea for addressing this, but that may take us a bit of time.
The way to address this for now is to instantiate gql.tada multiple times, i.e. passing different schemas to initGraphQLTada<>(). It doesn't matter where the schema lives, so that means you can write multiple graphql-env.d.ts files, e.g. schema-1.d.ts, and so on.
However, currently, there's no mechanism to generate these separately, unless you were to isolate the instances of gql.tada in faux-packages/monorepo packages with their own tsconfig.jsons and used either GraphQLSP just in that package or by using the CLI there.
In short, multi-schema use-cases aren't supported yet. I'm very eager to make these happen though.

It's working just fine for me.. but again, not with .d.ts file(s) since they'd compete with one another for the only introspection value:
tsconfig.json
{
  "compilerOptions": {
    "plugins": [
        {
          "name": "@0no-co/graphqlsp",
          "schema": "./src/app1/schema.graphql",
          "tadaOutputLocation": "./src/app1/tada.ts"
        },
        {
          "name": "@0no-co/graphqlsp",
          "schema": "./src/app2/schema.graphql",
          "tadaOutputLocation": "./src/app2/tada.ts"
        },
        {
          "name": "@0no-co/graphqlsp",
          "schema": "./src/app3/schema.graphql",
          "tadaOutputLocation": "./src/app3/tada.ts"
        }
      ],
  }
}

example tada.ts (e.g. app1, but all 3 would look identical)
import { initGraphQLTada } from 'gql.tada'
import { introspection } from './tada'
import { type Scalars } from 'src/shared/scalars'

export const graphql = initGraphQLTada<{
  introspection: typeof introspection
  scalars: Scalars
}>()

export type { FragmentOf, ResultOf, VariablesOf } from 'gql.tada'
export { readFragment } from 'gql.tada'

While we can talk a lot about how ideally an organisation shouldn't have multiple schemas they're consuming, since those often cross boundaries and this opens you up to having apps that also consume multiple schemas (which starts defeating the point of GraphQL pretty hard),
I ran into this myself in a simple case too with a monorepo that both had a GraphQL schema but also consumed a third-party GraphQL schema.

It's fairly standard to have distinct GraphQL APIs for distinct applications (even when they're all "first party"). They have different use cases, capabilities, auth patterns, etc.
My point in opening up this PR was to help other people get their setups working. We kinda glossed over the fact that "monorepo" was mentioned in section I was trying to update the documentation for and that .d.ts definitely isn't working with a multi-schema monorepo setup at the moment, but using .ts files does in fact work as expected