Fix re-running admindb migration failures

What does this PR change?
Make all admindb migration queries re-entrance so re-running migration would not fail.
Does the PR depend on any other PRs or Issues? If yes, please list them.
None
Checklist
I confirm, that I have...

[ ] Read and followed the contributing guide in CONTRIBUTING.md
[ ] Added tests for this PR
[ ] Formatted the code using go fmt (if applicable)
[ ] Updated documentation on the Paralus docs site (if applicable)
[ ] Updated CHANGELOG.md

Codecov Report

Merging #205 (567685a) into main (da418fd) will increase coverage by 0.20%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #205      +/-   ##
==========================================
+ Coverage   34.41%   34.62%   +0.20%
==========================================
  Files          74       74
  Lines       11692    11692
==========================================
+ Hits         4024     4048      +24
+ Misses       7123     7094      -29
- Partials      545      550       +5

see 1 file with indirect coverage changes


add zhCN.

Hello, thank you so much for providing a translation.
I'll assign it to the 0.9 milestone.
0.8 will see updates in translation strings, I'll notify you in the PR for the appropriate updates.

thanks.
0.8 done.

raid soul drop at heroic and mythic, not in normal.

Hello, there are a few translation key changes upcoming today for the 0.9 version, I'll start integrating translations after you have a chance to update the PR.

done.

relly done.


recipes-robot: add module connection and communicatin

We use ainotify to wrap inotify watch fds in python asyncio interfaces to detect modules. Add it and set it as an rdepend of robot server.
We'll also need udev rules to properly make symlinks for the module serial links.

Tested on a machine; connecting a module correctly ends up with it detected and frequently polled for its status.


Improve logging when an invalid variable is provided

Is your feature request related to a problem? Please describe.
HC0016: Variable `eventTypes` got an invalid value.
      HotChocolate.Types.SerializationException: AppEventType cannot parse the given literal of type `StringValueNode`.
         at HotChocolate.Types.EnumType.ParseLiteral(IValueNode valueSyntax, Boolean withDefaults)
         at HotChocolate.Types.NonNullType.ParseLiteral(IValueNode literal, Boolean withDefaults)
         at HotChocolate.Types.NonNamedType.HotChocolate.Types.IParsableType.ParseLiteral(IValueNode literal, Boolean withDefaults)
         at HotChocolate.Types.ListType.CreateList(ListValueNode listLiteral, Boolean withDefaults)
         at HotChocolate.Types.ListType.ParseLiteral(IValueNode valueSyntax, Boolean withDefaults)
         at HotChocolate.Types.NonNamedType.HotChocolate.Types.IParsableType.ParseLiteral(IValueNode literal, Boolean withDefaults)
         at HotChocolate.Execution.Processing.VariableCoercionHelper.CoerceVariableValue(VariableDefinitionNode variableDefinition, IInputType variableType, Object value)

Describe the solution you'd like
It would help greatly if the error could tell me exactly which value has failed.

@michaelstaib is working on improving the error handling of variables this very minute: #4037
Look forward to it in v12 🚀

We will need at least two more days to get that merged. The errors now exactly specify what is wrong and where:
{
  "errors": [
    {
      "message": "The required input field \u0060name\u0060 is missing.",
      "path": [
        "user",
        "name"
      ],
      "extensions": {
        "field": "UserInput.name"
      }
    }
  ]
}

{
  "errors": [
    {
      "message": "The required input field \u0060name\u0060 is missing.",
      "path": [
        "user",
        "name"
      ],
      "extensions": {
        "field": "UserInput.name"
      }
    }
  ]
}


feat(spartan): run ethereum with beacon node in cluster w/ kurtosis

A second attempt at running eth with a beacon node in the kind cluster eth's kurtosis tooling
PROS: we can deploy some what complex ethereum environments underneath pretty easily, with multiple different types of CL + EL combinations, which is useful for us to test that everything is working ok, we can query blobs from different types of clients
We can also run a testnet with blobscan + mev boost builders underneath if we want to, which could be very useful if we want to test using private send transaction flows
CONS: dis thing takes a good while to boot up when using kind as a backend (like minutes vs seconds on the docker backend)
fixes: #10055

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#10275  👈 (View in Graphite)
#10248
#10079
master

This stack of pull requests is managed by Graphite. Learn more about stacking.


Enforce nested dependency installation through a multi-fronted strategy.

t2 run/push checks for .npmrc and isntructs to the author to run to t2 init to prepare the directory for deployment.
t2 init now produces an .npmrc file which sets global-style=true
t2 init will reinstall everything with newly created npmrc config in place

This is a wacky fix to a truly unfortunate problem. For projects that are started with t2 init, the .npmrc file will enforce mostly nested package installation (see the resource file itself for complete explanation of "mostly"). Since projects started with npm init will not have that .npmrc file provided for them, the deployment operation will check for that file and if it's not available, the deployment will be stopped and the author will be instructed to run t2 init first; that will create the .npmrc file and reinstall all the dependencies for the author.
Smoke Test 1

mkdir project && cd project && t2 init && ls
Observe and confirm the following output:INFO Initializing new Tessel project for JavaScript...
INFO Created ".npmrc".
INFO Created "package.json".
INFO Created ".tesselinclude".
INFO Wrote "Hello World" to index.js
.
├── [-rw-r--r-- rwaldron staff     940 Jun 30 13:14]  .npmrc
├── [-rw-r--r-- rwaldron staff     390 Jun 30 13:14]  .tesselinclude
├── [-rw-r--r-- rwaldron staff     298 Jun 30 13:14]  index.js
└── [-rw-r--r-- rwaldron staff     334 Jun 30 13:14]  package.json

0 directories, 4 files

npm install serialport > /dev/null 2>&1 && tree -aL 2
Observe and confirm the following output:.
├── .npmrc
├── .tesselinclude
├── index.js
├── node_modules
│   ├── .bin
│   └── serialport
└── package.json

3 directories, 4 files

Smoke Test 2

mkdir project && cd project && t2 init && ls

Observe and confirm the following output:
Wrote to /Users/rwaldron/robotz/project/package.json:

{
  "name": "project",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

.
└── [-rw-r--r-- rwaldron staff     221 Jun 30 13:20]  package.json

0 directories, 1 file

npm install serialport > /dev/null 2>&1 && tree -aL 2

Observe and confirm the following output:
.
├── node_modules
│   ├── .bin
│   ├── bindings
│   ├── commander
│   ├── debug
│   ├── define-properties
│   ├── foreach
│   ├── function-bind
│   ├── graceful-readlink
│   ├── immediate
│   ├── lie
│   ├── ms
│   ├── nan
│   ├── object-keys
│   ├── object.assign
│   └── serialport
└── package.json

16 directories, 1 file

touch index.js

t2 run index.js

Observe and confirm the following output:
INFO Looking for your Tessel...
INFO Connected to sonny.
WARN This project is missing an ".npmrc" file!
WARN To prepare your project for deployment, use the command:
WARN
WARN t2 init
WARN
WARN Once complete, retry:
WARN
WARN t2 run index.js

t2 init

Observe and confirm the following output:
INFO Initializing new Tessel project for JavaScript...
INFO Created ".npmrc".
INFO Created "package.json".
[serialport] Success: "/Users/rwaldron/robotz/project/node_modules/serialport/build/Release/serialport.node" is installed via remote
<EMAIL_ADDRESS>node_modules/foreach -> node_modules/serialport/node_modules/foreach
<EMAIL_ADDRESS>node_modules/function-bind -> node_modules/serialport/node_modules/function-bind
<EMAIL_ADDRESS>node_modules/graceful-readlink -> node_modules/serialport/node_modules/graceful-readlink
<EMAIL_ADDRESS>node_modules/commander -> node_modules/serialport/node_modules/commander
<EMAIL_ADDRESS>node_modules/immediate -> node_modules/serialport/node_modules/immediate
<EMAIL_ADDRESS>node_modules/ms -> node_modules/serialport/node_modules/ms
<EMAIL_ADDRESS>node_modules/object-keys -> node_modules/serialport/node_modules/object-keys
<EMAIL_ADDRESS>node_modules/define-properties -> node_modules/serialport/node_modules/define-properties
<EMAIL_ADDRESS>node_modules/bindings -> node_modules/serialport/node_modules/bindings
<EMAIL_ADDRESS>node_modules/debug -> node_modules/serialport/node_modules/debug
<EMAIL_ADDRESS>node_modules/lie -> node_modules/serialport/node_modules/lie
<EMAIL_ADDRESS>node_modules/nan -> node_modules/serialport/node_modules/nan
<EMAIL_ADDRESS>node_modules/object.assign -> node_modules/serialport/node_modules/object.assign
<EMAIL_ADDRESS>/Users/rwaldron/robotz/project
└──<EMAIL_ADDRESS>
INFO Created ".tesselinclude".
INFO Wrote "Hello World" to index.js

(Don't worry, all of that npm output is just indicating that existing directories are being moved)

tree -aL 2

Observe and confirm the following output:
.
├── .npmrc
├── .tesselinclude
├── index.js
├── node_modules
│   ├── .bin
│   └── serialport
└── package.json

3 directories, 4 files

Signed-off-by: Rick Waldron<EMAIL_ADDRESS>

r? @tcr
(tessel-highfive has picked a reviewer for you, use r? to override)

Coverage increased (+0.06%) to 79.694% when pulling 8918456fc0940e68702b07741b8ccb303b49607a on npmrc-for-nested-deps into 9251b586e4b679a0d37b23f8a39b06c38853d2d2 on master.

Coverage increased (+0.06%) to 79.694% when pulling 8918456fc0940e68702b07741b8ccb303b49607a on npmrc-for-nested-deps into 9251b586e4b679a0d37b23f8a39b06c38853d2d2 on master.

Coverage decreased (-0.2%) to 79.454% when pulling d21c727e0a78f82b097403ab582f69377b4d5f58 on npmrc-for-nested-deps into 9251b586e4b679a0d37b23f8a39b06c38853d2d2 on master.

I'd still like you to step through the smoke tests, if you can, just in case


fix(Pointer): switch off usage on pointer off

If pointerActivatesUseAction is true in VRTK_InteractableObject, after
pointing at the object with the pointer, the object continues to be used
also when the pointer is switched off.
Add a check in VRTK_WordPointer.TogglePointer() to switch off the
object usage if the pointer is switched off (add also a reference to the
object as private class member to keep track of the pointed object).

I think the issue you're describing is actually a feature.
If the Hold Button To Use checkbox is ticked then the pointer needs to be on the object (and active) for the pointer to work.
If Hold Button To Use is unchecked then the pointer will turn it on with the first destination set, and turn it off with the second destination set.
Look at the 019_Controller_InteractingWithPointer example to see this working.

This fix is intended just when the Hold Button To Use is checked (notice
the "&& interactableObject.holdButtonToUse" condition in my change to
the TogglePointer() method), if you switch off the pointer (you stop
holding button) the object continues to be "used". This happens if you
set e.g. both "Pointer Toggle Button" and "Use Toggle Button" to
"Trigger" (sorry for having omitted this detail before).
StoneFox wrote:

I think the issue you're describing is actually a feature.
If the |Hold Button To Use| checkbox is ticked then the pointer needs to
be on the object (and active) for the pointer to work.
If |Hold Button To Use| is unchecked then the pointer will turn it on
with the first destination set, and turn it off with the second
destination set.
Look at the |019_Controller_InteractingWithPointer| example to see this
working.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thestonefox/SteamVR_Unity_Toolkit/pull/288#issuecomment-234323584,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATW1qeNDZJZFcbsTZwH962goxISpKqylks5qX6tTgaJpZM4JRzbi.

Can you provide a video of the issue you believe you're seeing?
I've looked over the example scene and it seems to be working as I would expect.
If I hover my pointer over the cube that has Hold button To Use checked, then the spinner is only active when the pointer is on and touching the cube.
The other cube is correctly having it's using state toggled.

You can test it loading the example 019_Controller_InteractingWithPointer and setting Trigger both as Pointer Toggle and Use Toggle Button:

then point to the active object on the right "Whirlygig (2)", press the controller trigger:

then release it:

The capsule will continue spinning even if the pointer was disabled.

Cool, i'll try that out in a bit.

I wouldn't say this is a bug, I'd say it's a misconfiguration.
Because of the way the code works, if you set the Pointer Toggle button and Use button to the same button (e.g. Trigger). but leave the Pointer Set button as something different then it's going to cause all sorts of problems because it's a bad configuration.
If in your example you change the "Pointer Set" button to "Trigger" as well then it works as expected.
Whilst your PR does seemingly fix the initial issue, it doesn't fix other issues that are caused by this bad configuration. So I'd say rather than sticking plaster one issue, it's better just to not configure the system to work in this way,

This configuration was intended to activate objects with a kind of "laser shot".
Maybe this should be a different type of pointer (or a parameter could be added to enable this feature), but for now, if this is not allowed, probably it is better to point out in the documentation that we cannot set the same button to two different functions.

I changed the button settings, but the problem seems to be the same: if the interactive object has "Pointer Activates Use Action" and "Hold Button To Use" enabled and you just disable the pointer while the object is activated "in use" it won't stop to be "in use".

I'll do a video of my solution in a moment to make sure it's what you're expecting (and to show off the settings)
Maybe worth you doing a video too to show it not working?

These are the changed settings:

The result is the same, I have a small video in this ZIP (made using current version on master):
VRTK 2016-08-02 10-24-08-54.zip

Shouldn't your settings be:
Pointer Toggle Button: Trigger
Pointer Set Button: Trigger
Use Toggle Button: Trigger
Or are you saying with the default settings it doesn't work?

Yeah i agree your new settings shouldn't keep the item going.
Confirmed bug :)

Sorry, I need your help.
After rebasing to master I tried to  push and I got this error:
error: failed to push some refs to 'https://github.com/gpvigano/SteamVR_Unity_Toolkit'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
I Fetched from your repository, what should I Pull?

There were the following issues with your Pull Request

Commit: 7d6e769b977735b5d878c13dd089af68321965ce
Invalid type. Valid types are feat, fix, docs, style, refactor, perf, test, chore, revert

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

Sorry, finally I pushed using the "Force update" option and probably I broke something, could you check again this PR please?
Thanks

Still looks ok to me, let me pull it down and try it locally
No idea what gitcop is moaning about :/


[Enhancement] Support complex type expression push down

Fixes #issue

Support complex type expression push down
Rename ConjunctivePredicatesRewriter to GlobalDictPredicatesRewriter

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 5 / 6 (83.33%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/analysis/SubfieldExpr.java
0
1
00.00%
[97]

:large_blue_circle:
com/starrocks/analysis/CollectionElementExpr.java
5
5
100.00%
[]

@Mergifyio backport branch-3.1


Add lib/controllers/ENGINE to the autoload_paths

Summary
SolidusSupport added lib/decorators/#{engine} to the autoload_paths, but there are no other autoloaded_paths for lib. This is a problem when the decorator tries to decorate an existing class, because it's not loaded yet.
A real example, happened on solidus_social, because it decorates a controller defined on solidus_auth_devise.
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:

[x] I have written a thorough PR description.
[x] I have kept my commits small and atomic.
[x] I have used clear, explanatory commit messages.

The following are not always needed:

📖 I have updated the README to account for my changes.
📑 I have documented new code with YARD.
🛣 I have opened a PR to update the guides.
✅ I have added automated tests to cover my changes.
📸 I have attached screenshots to demo visual changes.

@elia, this is the ticket we have investigated today.

@DanielePalombo I'm not sure to understand the problem: are you decorating a controller that has been defined in the same engine? I'm sure I'm missing something, can you make a rough example?

@kennyadsl as a result of the investigation we discovered that with Rails 5.2 and Solidus 3 the RegistrationController defined by solidus_auth_devise was not autoloaded correctly and another extension (solidus_social) attempting to decorate that controller was not finding it.
The decorator paths were added to the autoload paths here but the same wasn't done for lib/controllers.

Ah, so, so we are talking about decorating controllers defined in other extensions, which are not autoloaded, makes sense now!

Merged, do we need a new version released?

Yes, please!

@kennyadsl @elia done!


[Provider Audit] provider.maintek.ch

Prerequisite Steps:
1. Make sure your provider has community provider attributes and your contact details (email, website):
  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community
  info:
    email: "<your email>"
    website: "<your website>"

Ref documentation:.
2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)
host <anything>.ingress.<yourdomain>

Example:
$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address <IP_ADDRESS>

More info on what DNS records should look like are available in the Akash Documentation here.

3. Please make sure your Akash provider doesn't block any Akash specific ports.

If you are using a firewall, please follow this doc:
https://akash.network/docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/#step-11---firewall-rule-review
If you are behind NAT, then you need to make sure these ports are open between your provider worker nodes and the internet.

Audit Steps:
1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")
2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.
3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.
4. Audit Issue will be closed by core team member.
Leave contact information (optional)

Jakob
Discord / jackserippl
<EMAIL_ADDRESS>

hi @jackserippi ,
Your provider is not answering status endpoint calls on port 8443:
curl -sk https://provider.maintek.ch:8443:status | jq
Which is strange because it is answering the inventory status endpoint call on port 8444. This would indicate that most probably the port forwarding is not done correctly.
Please check and we will continue. If you need assistance please reach out on Discord.
Shimpa

hi @jackserippi ,
The provider attributes are good.
The performance is quite low however. It's not mandatory for a provider to be fast however the user experience will not be great. A simple deployment took 20 minutes to load, something that usually takes 30 seconds. The provider can still get audited and signed.
Another much more serious issue is reliability. The provider is constantly going down and is unreachable. This is a hindrance in the auditing process. The provider needs to be up 24/7 in order to receive an audited status.

@shimpa1
Hi, yes I know It was a little bit to early to apply for the audit. I am reorganizing my storage completly, which caused the cluster to be down and heavly degreaded (Change from Raid to Ceph). Will be up 24/7 with high performance, when done.

OK,
Please sort out the infrastructure and let us know when you're done.
thank you,
Shimpa

Closing as stale. Provider is offline and it's been longer than a month.


Confuse on Retain Count

I am confused by the algorithm of Retain Count.
in HeapInspector,Retain Count = alloc+retain+strong -release, but is not always equals to CFGetRetainCount((__bridge CFTypeRef)object), why?

hard so answer right now...
do you have an example snippet?

Since the new version 0.2.0 now uses CFGetRetainCount, I'd close this issue


Navigation

"From the main menu, click Field Service > Administration, and then choose Resource Pay Types."
This has moved to Resources>Pay Types.

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

ID: e83ef851-7b39-233c-c550-a74adb40b603
Version Independent ID: e0f14b9d-d2a1-7a23-31b8-a42239c81d9c
Content: Set up resource pay types (Dynamics 365 Field Service)
Content Source: ce/field-service/set-up-resource-pay-types.md
Service: dynamics-365-customerservice
Technology: field-service
GitHub Login: @FieldServiceDave
Microsoft Alias: daclar

Thank you for sharing this feedback. I started working on Field Service docs a few days ago and do some housekeeping on open issues.
The listed doc issues are addressed in an upcoming publish that is expected to go live next week.
Closing this issue as solved. Please keep your feedback coming!
Thanks,
Michael


Replace Icons in the app with new ones

As a user ,
I want matching icons for actions ,
so that I know what action by clicking on an icon gets executed.
Hints / Details

Miro UI Concept Board : LINK
See Concept for Icon Design
Action Icons should have tooltip which describe the action
Feedback from Julia: Replace Queued & Requested Investigations (mat-tab on quality incidents page and on dashboard) with this one from Material:

Acceptance Criteria

[ ] Backend provides severity of active investigations
[ ] Icons are used as in concept
[ ] Tooltips describe what the icon does

Out of Scope

...

I copied the ticket as the original tickets were deleted due to a spam account.
Orginal Ticket: https://github.com/eclipse-tractusx/traceability-foss/issues/626


Make ARRAY_LENGTH working with JSON arrays

Signed-off-by: kuba--<EMAIL_ADDRESS>This PR add support to ARRAY_LENGTH for other type of array (e.g. JSON).
If we want to count something what will be extracted from diffs by EXPLODE/JSON_EXTRACT we need ARRAY_LENGTH with support for other arrays, e.g.:
SELECT ARRAY_LENGTH(JSON_EXTRACT('[{"i":0}, {"i":1, "y":"yyy"}, {"i":2, "x":"xxx"}]', '$.i'))

LGTM once tests pass.

rebuild C# helped


[SPARK-32971][K8S][FOLLOWUP] Add .toSeq for Scala 2.13 compilation

What changes were proposed in this pull request?
This is a follow-up to fix Scala 2.13 compilation at Kubernetes module.
Why are the changes needed?
To fix Scala 2.13 compilation.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the GitHub Action Scala 2.13 compilation job.

Could you review this, @viirya ?

Test build #129056 has started for PR 29859 at commit 19d9a2f.

Test build #129056 has finished for PR 29859 at commit 19d9a2f.

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

Merged build finished. Test PASSed.

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

Scala 2.13 GA job passed. Thank you, @viirya and @HyukjinKwon .
Merged to master.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/33677/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/33677/

Merged build finished. Test FAILed.

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


source-map-explorer throws 'Unable to map' error while analyzing CRA app

Describe the bug
source-map-explorer throws 'Unable to map' error while analyzing CRA app
Did you try recovering your dependencies?
Testing with fresh CRA app, so there is no issues with dependencies
Which terms did you search for in User Guide?

create react app source map explorer
the docs can be viewed here https://create-react-app.dev/docs/analyzing-the-bundle-size/

Environment
$ npx create-react-app --info
npx: installed 99 in 3.601s

Environment Info:

  current version of create-react-app: 3.3.1

Steps to reproduce
To set up environment:
$ npx create-react-app cra-source-map-explorer
$ cd cra-source-map-explorer
$ yarn build
yarn run v1.21.1
$ react-scripts build
Creating an optimized production build...
Compiled successfully.

File sizes after gzip:

  39.86 KB  build/static/js/2.6c16d42b.chunk.js
  783 B     build/static/js/runtime-main.e3ebb5d1.js
  623 B     build/static/js/main.25832e22.chunk.js
  556 B     build/static/css/main.d1b05096.chunk.css

The project was built assuming it is hosted at the server root.
You can control this with the homepage field in your package.json.
For example, add this to build it for GitHub Pages:

  "homepage" : "http://myname.github.io/myapp",

The build folder is ready to be deployed.
You may serve it with a static server:

  yarn global add serve
  serve -s build

Find out more about deployment here:

  bit.ly/CRA-deploy

Done in 5.76s.

To reproduce the error:
$ yarn add global source-map-explorer
$ source-map-explorer --version
2.2.2
$ source-map-explorer 'build/static/js/*.js'
build/static/js/2.6c16d42b.chunk.js
  Unable to map 207/129832 bytes (0.16%)
build/static/js/main.25832e22.chunk.js
  Unable to map 124/1167 bytes (10.63%)
build/static/js/runtime-main.e3ebb5d1.js
  Unable to map 13/1593 bytes (0.82%)

Expected behavior
source-map-explorer shows analysis of CRA app as documented in https://www.npmjs.com/package/source-map-explorer#source-map-explorer
Actual behavior
$ source-map-explorer 'build/static/js/*.js'
build/static/js/2.6c16d42b.chunk.js
  Unable to map 207/129832 bytes (0.16%)
build/static/js/main.25832e22.chunk.js
  Unable to map 124/1167 bytes (10.63%)
build/static/js/runtime-main.e3ebb5d1.js
  Unable to map 13/1593 bytes (0.82%)

Reproducible demo
Issue is reproducible on a fresh CRA app build using<EMAIL_ADDRESS>

Temporary fix: pass --only-mapped to source-map-explorer as follows:
source-map-explorer 'build/static/js/*.js' --only-mapped


No HDMI output on boot

After installing on a M1 mini, I get no HDMI output after the boot picker using a Lenovo L27m-28 monitor. Monitor works fine in macOS & Recovery/Boot picker. Install works fine with different screen (Dell UltraSharp 43).
Happy to provide any other details and conduct any testing required.

I had the same issue. In my case, with an M1 mini and a Viewsonic VP2785-4K display. In the install, after going through the boot picker and security stuff and then rebooting, my screen stayed blank. After an hour or so, I used the power button to shut down the system and restart it; now the display worked and the system came up into Asahi Linux.


kicad-testing-small: 7.0-2024-01-07 -> 7.0-2024-01-23

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bp7mdrjlq0rihn2qxk9flwivby0w6cvm-kicad-testing-small-7.0-2024-01-10 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/0a0021e29bc22b75ab2bda45bca4652b2bd8fce8.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0a0021e29bc22b75ab2bda45bca4652b2bd8fce8#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bp7mdrjlq0rihn2qxk9flwivby0w6cvm-kicad-testing-small-7.0-2024-01-10
ls -la /nix/store/bp7mdrjlq0rihn2qxk9flwivby0w6cvm-kicad-testing-small-7.0-2024-01-10/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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3c4l05r4i80gs5n1nb7403w0pary7v6v-kicad-testing-small-7.0-2024-01-17 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/f18f2d7e6aa94bf3c4531e8877a11343c2529481.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/f18f2d7e6aa94bf3c4531e8877a11343c2529481#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3c4l05r4i80gs5n1nb7403w0pary7v6v-kicad-testing-small-7.0-2024-01-17
ls -la /nix/store/3c4l05r4i80gs5n1nb7403w0pary7v6v-kicad-testing-small-7.0-2024-01-17/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

1 package failed to build:

kicad-testing

1 package built:

kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/p6frc2k2bs6rb4n3qknv89bkk5n8mn9b-kicad-testing-small-7.0-2024-01-23 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/3fd5a74004c27314a741ebec0b8a9a8051e08619.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3fd5a74004c27314a741ebec0b8a9a8051e08619#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/p6frc2k2bs6rb4n3qknv89bkk5n8mn9b-kicad-testing-small-7.0-2024-01-23
ls -la /nix/store/p6frc2k2bs6rb4n3qknv89bkk5n8mn9b-kicad-testing-small-7.0-2024-01-23/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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

i don't know why this update was attempted via kicad-testing-small
for the purpose of updating it is equivalent to kicad-testing
and i don't recall why kicad-small and kicad-unstable-small don't get updated / why that exclusion doesn't apply here

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0zs2pf1s9x9hmaq0w1vkmqrggqc2zj5s-kicad-testing-small-7.0-2024-02-06 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/d2e3881cba0c96bd01e655cc1166ce6cfd700f7e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d2e3881cba0c96bd01e655cc1166ce6cfd700f7e#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0zs2pf1s9x9hmaq0w1vkmqrggqc2zj5s-kicad-testing-small-7.0-2024-02-06
ls -la /nix/store/0zs2pf1s9x9hmaq0w1vkmqrggqc2zj5s-kicad-testing-small-7.0-2024-02-06/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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/giliaxl4vj7xdd329iznpqsjjbsxdidk-kicad-testing-small-7.0-2024-02-11 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/dee28a66371016b5e5ad4842066cce7dcc55f9c5.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/dee28a66371016b5e5ad4842066cce7dcc55f9c5#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/giliaxl4vj7xdd329iznpqsjjbsxdidk-kicad-testing-small-7.0-2024-02-11
ls -la /nix/store/giliaxl4vj7xdd329iznpqsjjbsxdidk-kicad-testing-small-7.0-2024-02-11/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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ilv17dy7a9cjsn4ibr4bx8nlw2y7ykka-kicad-testing-small-7.0-2024-02-14 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/23aae8a273b0f1b26edeef76253f02c71eaf5fb6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/23aae8a273b0f1b26edeef76253f02c71eaf5fb6#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ilv17dy7a9cjsn4ibr4bx8nlw2y7ykka-kicad-testing-small-7.0-2024-02-14
ls -la /nix/store/ilv17dy7a9cjsn4ibr4bx8nlw2y7ykka-kicad-testing-small-7.0-2024-02-14/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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1cvshcfpv9rqz3dk7kvplxv1wljx3wbr-kicad-testing-small-7.0-2024-02-21 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/630b121f7070c652bd7118bb5f28695a01d7b206.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/630b121f7070c652bd7118bb5f28695a01d7b206#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1cvshcfpv9rqz3dk7kvplxv1wljx3wbr-kicad-testing-small-7.0-2024-02-21
ls -la /nix/store/1cvshcfpv9rqz3dk7kvplxv1wljx3wbr-kicad-testing-small-7.0-2024-02-21/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

1 package failed to build:

kicad-testing

1 package built:

kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bpn5yqdy7i14a8vwb2740hisw9032lsk-kicad-testing-small-8.0-2024-03-23 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/24ce7accca1ad33e293ceb911ff14d9cd1b7ea6f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/24ce7accca1ad33e293ceb911ff14d9cd1b7ea6f#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bpn5yqdy7i14a8vwb2740hisw9032lsk-kicad-testing-small-8.0-2024-03-23
ls -la /nix/store/bpn5yqdy7i14a8vwb2740hisw9032lsk-kicad-testing-small-8.0-2024-03-23/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4hgfbrffmd2krz5c50878ja9rggmlyz1-kicad-testing-small-8.0-2024-03-30 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/9be2f048201b3f8ddffd6e484ba4c72d5b14ff78.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9be2f048201b3f8ddffd6e484ba4c72d5b14ff78#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4hgfbrffmd2krz5c50878ja9rggmlyz1-kicad-testing-small-8.0-2024-03-30
ls -la /nix/store/4hgfbrffmd2krz5c50878ja9rggmlyz1-kicad-testing-small-8.0-2024-03-30/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/03k91jpq0lsgl8lqi4fanrkac1hgsfcj-kicad-testing-small-8.0-2024-04-06 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/569533b8c2e74700f4ff7b21967bcf36abe1a162.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/569533b8c2e74700f4ff7b21967bcf36abe1a162#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/03k91jpq0lsgl8lqi4fanrkac1hgsfcj-kicad-testing-small-8.0-2024-04-06
ls -la /nix/store/03k91jpq0lsgl8lqi4fanrkac1hgsfcj-kicad-testing-small-8.0-2024-04-06/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/x9w80iab9hxzqyjs1qpbc3a6k8hh6765-kicad-testing-small-8.0-2024-04-24 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/8425fc8e47017cc53fd259f80f5ada604b8d425f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8425fc8e47017cc53fd259f80f5ada604b8d425f#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/x9w80iab9hxzqyjs1qpbc3a6k8hh6765-kicad-testing-small-8.0-2024-04-24
ls -la /nix/store/x9w80iab9hxzqyjs1qpbc3a6k8hh6765-kicad-testing-small-8.0-2024-04-24/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r7ijl1xpcm8mlq7inzm8zfxypy749shv-kicad-testing-small-8.0-2024-04-29 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/7fb0ba787dfc74f34e77808b0019a24cbecd9504.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7fb0ba787dfc74f34e77808b0019a24cbecd9504#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r7ijl1xpcm8mlq7inzm8zfxypy749shv-kicad-testing-small-8.0-2024-04-29
ls -la /nix/store/r7ijl1xpcm8mlq7inzm8zfxypy749shv-kicad-testing-small-8.0-2024-04-29/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kwmxsj6ifp3gc45zadd1a1kbl1wz8a3c-kicad-testing-small-8.0-2024-05-06 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/c4b6b22156a361ed5ba91d02be5a78978b04f897.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c4b6b22156a361ed5ba91d02be5a78978b04f897#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kwmxsj6ifp3gc45zadd1a1kbl1wz8a3c-kicad-testing-small-8.0-2024-05-06
ls -la /nix/store/kwmxsj6ifp3gc45zadd1a1kbl1wz8a3c-kicad-testing-small-8.0-2024-05-06/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hdvhya5h9pw7a5s1r0jnjxsapczpfwk0-kicad-testing-small-8.0-2024-05-19 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/83b0c8339c335bf38be3abf9488668bb8ec371a8#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hdvhya5h9pw7a5s1r0jnjxsapczpfwk0-kicad-testing-small-8.0-2024-05-19
ls -la /nix/store/hdvhya5h9pw7a5s1r0jnjxsapczpfwk0-kicad-testing-small-8.0-2024-05-19/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vri6ks5iczhj2fn78xcxhjx3yjd883sq-kicad-testing-small-8.0-2024-05-25 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/ff3a82d8e1a3019e0f1950d0cf433317326e38a7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ff3a82d8e1a3019e0f1950d0cf433317326e38a7#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vri6ks5iczhj2fn78xcxhjx3yjd883sq-kicad-testing-small-8.0-2024-05-25
ls -la /nix/store/vri6ks5iczhj2fn78xcxhjx3yjd883sq-kicad-testing-small-8.0-2024-05-25/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/scv8fbhn9a6xyyjlcysphr7w097viyc7-kicad-testing-small-8.0-2024-05-30 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/f8e2ecb50c2bb413eda466c07b8e4b2900d9f41c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/f8e2ecb50c2bb413eda466c07b8e4b2900d9f41c#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/scv8fbhn9a6xyyjlcysphr7w097viyc7-kicad-testing-small-8.0-2024-05-30
ls -la /nix/store/scv8fbhn9a6xyyjlcysphr7w097viyc7-kicad-testing-small-8.0-2024-05-30/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6a339d5hg7ax768aas2b1z7sv51lpkv0-kicad-testing-small-8.0-2024-06-07 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/fa7a7c4e824ceb093a79bc52e4fc2618f827f303.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fa7a7c4e824ceb093a79bc52e4fc2618f827f303#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6a339d5hg7ax768aas2b1z7sv51lpkv0-kicad-testing-small-8.0-2024-06-07
ls -la /nix/store/6a339d5hg7ax768aas2b1z7sv51lpkv0-kicad-testing-small-8.0-2024-06-07/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/szpjwhqj5lq9c81l1b5r8ybaimb0qslm-kicad-testing-small-8.0-2024-06-14 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/6bc3429fb4919f49516b599437702c482c8ad2f9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6bc3429fb4919f49516b599437702c482c8ad2f9#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/szpjwhqj5lq9c81l1b5r8ybaimb0qslm-kicad-testing-small-8.0-2024-06-14
ls -la /nix/store/szpjwhqj5lq9c81l1b5r8ybaimb0qslm-kicad-testing-small-8.0-2024-06-14/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2p645jvxfhf9sa780dkcamj60v6m69qm-kicad-testing-small-8.0-2024-06-22 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/75d986aa37b457ff6826fefb006f269165be4ec3#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2p645jvxfhf9sa780dkcamj60v6m69qm-kicad-testing-small-8.0-2024-06-22
ls -la /nix/store/2p645jvxfhf9sa780dkcamj60v6m69qm-kicad-testing-small-8.0-2024-06-22/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gdja6gl6q8y4yin0qvm5qq8yh1vhkajf-kicad-testing-small-8.0-2024-06-27 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/4f284955317fe14b3aeac9a52c403b52bedc2233.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4f284955317fe14b3aeac9a52c403b52bedc2233#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gdja6gl6q8y4yin0qvm5qq8yh1vhkajf-kicad-testing-small-8.0-2024-06-27
ls -la /nix/store/gdja6gl6q8y4yin0qvm5qq8yh1vhkajf-kicad-testing-small-8.0-2024-06-27/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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zia708mfb5kih43dk1k5wkzfwchr717p-kicad-testing-small-8.0-2024-08-14 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/54a797c347dacb841d163a8b869b56811a38a4bc.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/54a797c347dacb841d163a8b869b56811a38a4bc#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zia708mfb5kih43dk1k5wkzfwchr717p-kicad-testing-small-8.0-2024-08-14
ls -la /nix/store/zia708mfb5kih43dk1k5wkzfwchr717p-kicad-testing-small-8.0-2024-08-14/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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qksd451z4ac36vkr1ziv46xpxdzqnr4y-kicad-testing-small-8.0-2024-08-26 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/c98355b46bafda8a530eebb0a6c6770be1cc71ef#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qksd451z4ac36vkr1ziv46xpxdzqnr4y-kicad-testing-small-8.0-2024-08-26
ls -la /nix/store/qksd451z4ac36vkr1ziv46xpxdzqnr4y-kicad-testing-small-8.0-2024-08-26/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2iyqpqp5agiq7ac0zfbzmplwn2cgxw0j-kicad-testing-small-8.0-2024-09-08 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/fcfacea65c07e9bd5c3bb6e28c9970c4e81339a1#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2iyqpqp5agiq7ac0zfbzmplwn2cgxw0j-kicad-testing-small-8.0-2024-09-08
ls -la /nix/store/2iyqpqp5agiq7ac0zfbzmplwn2cgxw0j-kicad-testing-small-8.0-2024-09-08/bin

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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mwdi1brflfy49g96qck698w5avhhw2zr-kicad-testing-small-8.0-2024-09-21 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/09c056f390ba9b828297d49327e57e7cd290110a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/09c056f390ba9b828297d49327e57e7cd290110a#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mwdi1brflfy49g96qck698w5avhhw2zr-kicad-testing-small-8.0-2024-09-21
ls -la /nix/store/mwdi1brflfy49g96qck698w5avhhw2zr-kicad-testing-small-8.0-2024-09-21/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

2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for kicad-testing-small is: Open Source Electronics Design Automation suite, without 3D models
meta.homepage for kicad-testing-small is: https://www.kicad.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
kicad result is not automatically checked because some binaries stick around

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

kicad-testing
kicad-testing-small

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pb631s8q9q0663gakhy483gfs1sjsz3z-kicad-testing-small-8.0-2024-11-28 \
  --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 kicad-testing-small https://github.com/r-ryantm/nixpkgs/archive/eb3a4d41e781f88678f49fc20e8455247cc18c56.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/eb3a4d41e781f88678f49fc20e8455247cc18c56#kicad-testing-small

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pb631s8q9q0663gakhy483gfs1sjsz3z-kicad-testing-small-8.0-2024-11-28
ls -la /nix/store/pb631s8q9q0663gakhy483gfs1sjsz3z-kicad-testing-small-8.0-2024-11-28/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.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 2 packages built:

kicad-testing
kicad-testing-small

Maintainer pings
cc @evils for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


[#1220] Currencies in profile no longer duplicate on update

core.UpdateProfile was causing currency lists in the profile to become duplicated. Manually verified this fix works for the case illustrated in #1220.

lgtm


Buffer api fix

derive endiannes postfix supported by node Buffer api:

8 bit integers methods have no endiannes postfix
for all other numbers, endiannes postfix is mandatory

Hello! I'm not using this library anymore, so I've added you as a collaborator on GitHub and an owner on NPM. Please feel free to make improvements and releases as you see fit, and delegate any work to anyone else you feel is suitable for the job. The only thing I ask is that you follow the semver guidelines. Thanks!


UnicodeEncodeError fixed

Fixed UnicodeEncodeError while saving non-latin1 symbols in extended description or tags.

Hi guys, just reminding you about this pull-request.

@haron Sorry about the multi-year delay. This looks good, thanks for contributing! 👍


[question] How to load hific iamge directly？

Do we need a decoder to parse the hific image?

Yes, images are encoded in .hific format - to decode this back to an image you need to first:

Decode the bitstream to the latent representation using a standard entropy (here we use ANS).
Pass the latent representation through the NN decoder/generator - this is the bottleneck.

Using compress.py will do both for you automatically provided you pass in the right flags. Check the usage guide for more info about this.


Props callback crashes on non-true return

What version of React-Table are you using?
6.5.3
What bug are you experiencing, or what feature are you proposing?
getTrProps and probably all the other get props callbacks will crash the component if returning a falsey value. This is not intuitive or documented. See example below
Example
https://codesandbox.io/s/50lprj46mx
Intuitively you would think to just return nothing here if the row is undefined, but you must return something truthy.
What are the steps to reproduce the issue?
Return void or falsey value from get props callback

On the next refactor I will normalize propCallbacks to not require this. For now, it is newly documented.


Combine semver with GitHub release

We are currently using semantic-release but semver could be the perfect replacement. However there is on scenario that I am struggling with: Besides creating the changelog we also want to publish a GitHub release

The problem is that semver will end the process with creating a tag.
If I now e.g. want to use the gh cli to create a release I would be in trouble because the tag has already been created

Is there a smart way out of that?

Hi @petergrau, I am not sure if the presence of the tag affects gh cli.
As mentioned by @edbzn in #71, we are thinking about the best way to handle publishing/deployment as we are not only aiming monorepos with libs but also monorepos with apps and maybe non-js code.
Meanwhile we provide a generic way for handling publishing & deployment, you could implement github release with something like this for each package
gh release create $(cat package.json | npx json version)

Meanwhile we provide a generic way for handling publishing & deployment, you could implement github release with something like this for each package
gh release create $(cat package.json | npx json version)

@yjaaidi thanks - that seems to work - need to dig in a bit deeper. The only remaining question I then have at this point is if there is a good way to only retrieve the changelog from the latest release from the CHANGELOG.MD that was written by semver.

Closing this issue to regroup the discussions here #167.

😅 Oups! I closed this too quickly.
AFAIK, there is no github release angular/nx builder meaning that after #167 is ready, we'll have to create one or create a schematic that adds an nx custom command running gh release create to workspace.json


Adding lots of examples to the docstrings in core (part two)

Examples, you said? We've got examples.
Note: some of them can/should get updated as other PRs get merged.

This PR fixes some problems in PR #59 by adding the --remote-data astropy test option to the travis runs, and adding the # doctest: +FLOAT_CMP tag on some print statements that would otherwise yield different results in Python 2 and 3.

Using --remote-data and querying Sesame all the time via from_name is a bit risky. If the uptime of Sesame is no good, it'll mean annoying sporadic travis-ci fails that are unrelated to the PRs.
So I still think mocking from_name as suggested in https://github.com/astroplanners/astroplan/pull/59#issuecomment-130194176 is the better approach.
But I realise time is short until the 0.1 release and learning how to implement the mocking takes time, so OK to put this in if others agree. If there are issues we can always do the mocking later.
@adrn @eteq OK to merge?

:+1:
(I'll merge this tomorrow, unless someone else does a review and / or merges it today.)

@bmorris3 -- As I was reading through core.py, I was confused as to where airmass came from, then I came upon the altaz frame in astropy.  Am I correct in assuming that the altaz frame in astroplan is functionally the same?  In that case, we need to point this out to users in our own altaz docstring.

@bmorris3 – I just realised that this PR breaks python setup.py test without the --remote-data option:
https://gist.github.com/cdeil/4b477928d76ec1e537f0#file-gistfile1-txt-L260
I.e. someone without internet connection can't run the astroplan tests.
That's not OK and we have to find another solution.
Like I said in https://github.com/astroplanners/astroplan/pull/59#issuecomment-130194176, I think mocking from_name for the tests and docs is the right approach.
I just now thought about this some more, and this would be my suggestion how to implement it:

Add a function astroplan.remote_data_mock() that assigns mock functions to Target.from_name and Observer.at_site. For a hand-written list of inputs from the docs / tests the outputs are hard-coded. Whether you do this in a JSON file or in the .py file itself doesn't matter... whatever you prefer.
Call this function in docs/conf.py so that it's active when building the docs.
Call this function in astroplan/conftest.py so that it's active when running the tests. (I think, here I'm not sure, but if this is not the right location, we can figure out where it needs to go.)

@cdeil I could use some help with this, I can't figure out if mock can be used that way.

@cdeil I used your mocking suggestion in f36dac0, and it seemed to work fine on my computer, but it failed in travis. Might that urllib error be a travis problem? If so, would you mind restarting the run?

@adrn / @eteq: The current build has an error that looks like weird quantities behavior. In almost all contexts I've been able to compute an inequality for a Quantity that's a time duration (days, minutes) and a TimeDelta, but it's giving an error on some of the builds (but not all), see one here.

The errors in this build are related to those being address in #67.

The unrelated travis-ci issues are gone, so we can try to get this finalised.
@adrn What do you think?

Re @cdeil: Addressed your comments in be46506

Sorry I'm just looking at the most recent commits now.
I'm a bit confused as to why we are "mocking" from_name. I understand we don't want the tests to be pinging the internet all the time (I agree this is bad), but what is the advantage to creating targets using from_name rather than just having a few sets of coordinates manually entered in... I'm :-1: on the mocking stuff that was added and would much prefer to just see the 4 test-case stars hard-coded in somewhere.


feat: update header.js

I updated header. Please check! Thank you:)

I checked it! I'll merge it!

The modal functionality works well, but consider adding accessibility features, like closing the modal with the "Esc" key.
Solid work overall! 👍👍👍


Trade channel: Invalid channel name

Hi! Thanks for this addon, is really great to organize whispers and trade chat for the selling crafting process in DF :)
I just want to let you know that I have an error on the trade window. I've setted WIM to show trade channel on a different WIM window but when I leave the city it gives me an error on the WIM window "Invalid channel name" and re-entering the city won't join Trade channel back again.
I have to logout and login and type "/join Trade" to be able to see trade channel again.
I've found a bug report on prat addon similar to the same issue. maybe it can help? :)
https://github.com/sylvanaar/prat-3-0/issues/114

Thank you, I will look into how this is affecting WIM. WIM only listens to incoming chat events. Not sure why it would be causing an issue.

Can you confirm this is still an issue? WIM doesn't manage joining and leaving channels and really shouldn't be the cause of this problem. WIM only listens for chat message events and delivers them to the UI. Might have been another addon you are using. In this case Prat?

With only WIM on, I enter and leave city and trade leaves and auto rejoins as it should.

Thanks for the feedback! I still have the issue but now I can exclude WIM from the hypothesis :)
I don't use Prat, WIM is enough :D


option to reseed parallel copies of trained ARMA

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
Closes #245.
What are the significant changes in functionality due to this change request?
ARMA now has an optional "reseedCopies" option.  It is True by default.  When enabled, any pickling of the ARMA will result in a reseeding of the random number generation with a random integer.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

The test only tests reseedCopies = False. Should there be an additional test that checks that the ARMA histories are different for reseedCopies = True?

Shouldn't  be mentioned in the manual?

The difficulty with reseedCopies = True is that we can't control the seed to test its consistency.  I'm up for ideas on how to cover that with a test, though.