Print the reason why vote registrations are rejected

ADP-991
ADP-984

Modify the MetadataRetrievalError to include the transaction id (useful for
debugging) and the MetadataParsingError as an error node, the previous
grouping of them under a larger error type (MetadataError) was unnecessary.
Print how many vote registrations were rejected and how many were good.
For each rejected vote registration, print why that registration was rejected,
along with the txid of the registration.
Print registrations that are rejected for not having enough voting power.
Document the decisions made by the code better.
Refactor the "voteFromTxMetadata" function to provide better error messages.

Example output on testnet (with lots of output omitted):
Found 1017 vote registrations. Of which,
	370 were good vote registrations.
	647 were bad vote registrations.
 Failed transactions:
 - tx: '445406', reason: 'The TxMetadata associated with transaction "445406" was not a valid vote registration. Parsing failed with error: "The rewards address at metadata path: 61284 > 3 failed to parse. Error was: Failed to deserialise."'
 - tx: '443981', reason: 'The TxMetadata associated with transaction "443981" was not a valid vote registration. Parsing failed with error: "The signature could not be found at the metadata path: 61285 > 1"'
 - tx: '506790', reason: 'The TxMetadata associated with transaction "506790" was not a valid vote registration. Parsing failed with error: "Signature validation failed"'
 - tx: '363206', reason: 'The TxMetadata associated with transaction "363206" was not a valid vote registration. Parsing failed with error: "The rewards address could not be found at the metadata path: 61284 > 3"'
 - tx: '441630', reason: 'The TxMetadata associated with transaction "441630" was not a valid vote registration. Parsing failed with error: "The slot number could not be found at the metadata path: 61284 > 4"'
Keys eligible: 80
Processing vote stake 80 of 80
Rejecting 0x0a6c8f9760e68901a615ab675759e77c46b6ab9410318f8c92227a3437720e4c, not enough voting power.
Rejecting 0x0dcb1d822e5b0cfa43d22f21631509780f231c65b2e8eab9ee67d80c2f3a9dea, not enough voting power.

It looks like it does the job, well done.
Extra tasty test cases for CLI.Query would be nice, but I assume you've manually tested it anyway.
All review comments are for informational purposes, and optional.

Yeah, testing isn't great. I think for quick "QA plan" we should compare the output of this tool to the output of the python implementation (if it's still kicking around - the original implementation was in python). The python version did see use so we might be able to use it as a standard.

This project was developed in such a rush, I think it would benefit from some refactoring, which would make testing easier.

Yeah no worries. If you're sure that this works, let's merge.

The reference implementation QA plan didn't work out, so in lieu of proper automated tests:
If I run the rewards tool on master (commit db0748e), the result is:
$ ./master/bin/voting-tools rewards --testnet-magic 3 --db cexplorer --db-user cardano-node --out-file test-master.json --total-rewards 1000

$ cat test-master.json
{
    "stake_test1up0pf960qp4h34z2zn026kv6xmq6364aw4ysvyfy2cleg9qr86u3w": 76,
    "stake_test1up4nxuextye6g4ee0wlacjfr58z59s4zkew9mh54rge7dks4q4c02": 0,
    "stake_test1up4yzhcnz7d9pwtr47un72g60tpf2yad0p9e9rtr0t8gv4quegwls": 0,
    "stake_test1up6n38fujl2ewzyr039t9072f867sv0p0ha76sw9a93ua4qafzk5j": 8,
    "stake_test1upd956c5pc0zyd6z2prcj7q2h8s4lgc760vj90ucu7874gcxu4x2n": 0,
    "stake_test1upnumn34svy2ngfjhpludmgqtvmzvxcgrejlxgf7att7kpc7u7e5t": 0,
    "stake_test1uqgunewqvzxsfn9vzk2ujmqaar0rju4j5ff9kqmyfkgx2yqhfvuau": 76,
    "stake_test1uqh28ls8xhajflwpglw4m8nufrl40en7xj7sa53h42wvpssxxzvwz": 76,
    "stake_test1uqpayp2nyzy66tmcz6yjuth59pym0df83rjpk0758fhqrnc8dx6fl": 8,
    "stake_test1uqvme07m3ptfvlsw9vajwvdfysc5hsv35vua53gtexhz24qkg4z23": 0,
    "stake_test1ur9vqc4arnkmledd7xkjcjws0htxda765j982w69naacnjg7mwq5d": 0,
    "stake_test1urq2qcyfn45qd7qs23lzedn0jt2us9apdte2yrexncjcacq6zv5dc": 756,
    "stake_test1uz9f5netc2w4jw9aqej2h9tr285rzyjcnhk8fht4h269qfsfgafp9": 0,
    "stake_test1uzgg4mwuskxqvxnyhm3htfv8gquwrcyerxyrkh922n2rpgq5y798z": 0,
    "stake_test1uzgqw0aqph3uhsu4r2gzq0f2qyl0qdg0p06ce7cgr7r6xygf3pvjp": 0,
    "stake_test1uzzd48zzkvg4sttpp7rcm8zxxjyf2s4ec4efw9g9d7pd60sq2yk9k": 0
}

Note that if the proportion of the voting power of an address would result in it receiving a fractional amount of Lovelace, that user will receive no rewards (this is a limitation of cardano-node, we can't send fractional amounts of Lovelace). The rewards are distributed such that sum of the rewards matches the "total-rewards" specified.
If I run the same command on this branch, the result is:
$ ./result/bin/voting-tools rewards --testnet-magic 3 --db cexplorer --db-user cardano-node --out-file test-branch.json --total-rewards 1000

$ cat test-branch.json
{
    "stake_test1up0pf960qp4h34z2zn026kv6xmq6364aw4ysvyfy2cleg9qr86u3w": 76,
    "stake_test1up4nxuextye6g4ee0wlacjfr58z59s4zkew9mh54rge7dks4q4c02": 0,
    "stake_test1up4yzhcnz7d9pwtr47un72g60tpf2yad0p9e9rtr0t8gv4quegwls": 0,
    "stake_test1up6n38fujl2ewzyr039t9072f867sv0p0ha76sw9a93ua4qafzk5j": 8,
    "stake_test1upd956c5pc0zyd6z2prcj7q2h8s4lgc760vj90ucu7874gcxu4x2n": 0,
    "stake_test1upnumn34svy2ngfjhpludmgqtvmzvxcgrejlxgf7att7kpc7u7e5t": 0,
    "stake_test1uqgunewqvzxsfn9vzk2ujmqaar0rju4j5ff9kqmyfkgx2yqhfvuau": 76,
    "stake_test1uqh28ls8xhajflwpglw4m8nufrl40en7xj7sa53h42wvpssxxzvwz": 76,
    "stake_test1uqpayp2nyzy66tmcz6yjuth59pym0df83rjpk0758fhqrnc8dx6fl": 8,
    "stake_test1uqvme07m3ptfvlsw9vajwvdfysc5hsv35vua53gtexhz24qkg4z23": 0,
    "stake_test1ur9vqc4arnkmledd7xkjcjws0htxda765j982w69naacnjg7mwq5d": 0,
    "stake_test1urq2qcyfn45qd7qs23lzedn0jt2us9apdte2yrexncjcacq6zv5dc": 756,
    "stake_test1uz9f5netc2w4jw9aqej2h9tr285rzyjcnhk8fht4h269qfsfgafp9": 0,
    "stake_test1uzgg4mwuskxqvxnyhm3htfv8gquwrcyerxyrkh922n2rpgq5y798z": 0,
    "stake_test1uzgqw0aqph3uhsu4r2gzq0f2qyl0qdg0p06ce7cgr7r6xygf3pvjp": 0,
    "stake_test1uzzd48zzkvg4sttpp7rcm8zxxjyf2s4ec4efw9g9d7pd60sq2yk9k": 0
}

Which is an empty diff:
$ diff test-master.json test-branch.json
$ echo $?
0

I'm using this as evidence this branch has not changed the behaviour of voting-tools.


Making modal display just below the components i want to.

Making modal display just below the components i want to. How do I achieve this ? For now, the modal is in the center of the screen.

Hi,
That is not possible with this component. It is however preferred to show on entire screen. Makes it more readable and easy to use.
Thanks


WIP: Build slepc

This PR rebuilds Serac TPLs and adds SLEPc as an additional TPL. Leveraging SLEPc will help Serac solve eigenvalue problems.
Fixes #1099

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 86.97%. Comparing base (dcde5f1) to head (6f7f2f1).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1102   +/-   ##
========================================
  Coverage    86.97%   86.97%
========================================
  Files          159      159
  Lines        15465    15465
========================================
  Hits         13450    13450
  Misses        2015     2015

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


softwarecontainer: move to recipes-containers

Move the softwarecontainer recipe to recipes-containers folder in
order to match the same location in meta-virtualization.
Signed-off-by: Gordan Markuš<EMAIL_ADDRESS>

Issue #98


Global options does not work in CLI mode

https://github.com/gorcon/rcon-cli/commit/22108f3c8bceb5298bbd1d17c883369151d826b8


Add Educhain (full)

Closes L2B-8036
Launches Dec 2nd, EOA admin

project launch postponed to q1 next year (source: telegram)


mariadb: fix typo in values.yaml

What this PR does / why we need it:
Typo fix in values.yaml.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

thanks @cimomo
/ok-to-test
/lgtm


[CI] Send out email in case of meshmodel component generation/updation failure.

Current Behavior

Desired Behavior

Implementation

Acceptance Tests

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

hey @vishalvivekm ,are you still working on this issue ? I will be happy to take up on this.

hey @vishalvivekm ,are you still working on this issue ? I will be happy to take up on this.

@ayushthe1 I didn't start working on it was involved in some other issue, Ashish has said it's not that urgent of a task and asked for some progress over a week, so lemme try and if i m not able to make some quick progress ( by tmrw) I'll happily pass this on to you mate!

What's the status on this issue @vishalvivekm

What's the status on this issue @vishalvivekm

awaiting response from Ashish


Action all the sudden reporting job status using "(merge)" suffix

I have a number of workflow jobs that use cypress-io/github-action which I have tied to branch protection status checks. Here is an example of a job:
- name: Cypress end-to-end tests
  uses: cypress-io/github-action@v4
  with:
    wait-on: 'https://localhost:9000/index.js'
    start: npm run start:local
    config-file: cypress/config/e2e.ts
    record: true
    install: false
    group: 'E2E'
    ci-build-id: ${{ needs.prepare.outputs.uuid }}
    tag: 'pull-request'

The name of the status check that I previously set for this job is "cypress: E2E" which uses the group property of the action.  This has been working fine.  All of the sudden, however, the previous status checks are not reporting.  Instead, I'm seeing status checks being reported that have my expected checks, but with a "(merge)" suffix. eg:

Why is this happening?

I manually re-ran the workflow and this time it reported the status checks without the "(merge)" suffix.

@mellis481
Was this just a one-time occurrence or are you having repeatable issues? You would need to examine the workflow logs for the run which hung in order to see what might have gone wrong. If you find a need to re-run your workflow with debug logging enabled, then you can add:
env:
  DEBUG: '@cypress/github-action, cypress:*'

Your post shows that you are using cypress-io/github-action@v4 which is effectively v4.2.2 published on Nov 28, 2022 and unchanged since then.
To take advantage of on-going improvements and bug-fixes you should consider migrating to cypress-io/github-action@v5 which is the latest version available.
Which version of Cypress are you using?

v4.
This happened multiple times. I pushed an empty commit to the PR after seeing the problem initially and the corresponding workflow run again had the "(merge)" suffix. It wasn't until I manually re-ran the workflow where the statuses were reported without the "(merge)" suffix.

@mellis481
Is your screenshot from the pull request status on GitHub? Are you using a GitHub hosted runner or self-hosted? What do you have in your workflow event trigger section on:? I suspect that merge is a GitHub PR status. In open PRs in this repository I see (pull_request) where you see (merge):

v4.

I was actually asking about the version of Cypress in use, like 9.7.0 or 12.6.0 for instance. That is just for background information.

Is your screenshot from the pull request status on GitHub?

Yes.

Are you using a GitHub hosted runner or self-hosted?

Self-hosted.

What do you have in your workflow event trigger section on:? I suspect that merge is a GitHub PR status. In open PRs in this repository I see (pull_request) where you see (merge):

on:
  pull_request:
    branches:
      - master

I was actually asking about the version of Cypress in use, like 9.7.0 or 12.6.0 for instance. That is just for background information.

10.4.0.

@mellis481
Thanks for the additional information! It doesn't look like this is an issue caused by cypress-io/github-action. Again, I think you would need to dig into your log files to gain more insight.

@mellis481
One more thought: when I hover over the GitHub icon in my screenshot it says "@github-actions generated this status".

In your screenshot I can see only Cypress icons, so there is a difference.
Your issue has now been assigned to a Cypress engineer, so hopefully he will be able to chip in with more expertise than I have!

@MikeMcC399 Thanks! Yes, when I hover over the Cypress icons the popover says "@cypress generated status".
I'm not sure if it was clear from my workflow code, but our workflow job is parallelized and integrated with Cypress Dashboard.

@mellis481 I think I concur with @MikeMcC399 that this isn't related to the GitHub Action, since these status checks come directly from Cypress Cloud itself.
I spoke with @davidr-cy and he showed me that the relevant code paths that generate these status checks haven't changed in almost 2 years. (merge) is added if it's detected that the commit message is generated from a merge commit, and our logic around that hasn't changed.
So now we are wondering if GitHub is sending us different metadata all of a sudden, causing the change in behavior you're seeing. Could you please share your Cloud organization ID so we can debug further? You can find it under "Organization ID" inside of the Cypress Cloud.

c5365dbf-9c5b-4769-a95d-130d46f70241

@mellis481 can you try switching to on: push instead of on: pull_request and seeing if it resolves the issue? It's what the docs recommend, for reasons explained there: https://github.com/cypress-io/github-action#record-test-results-on-cypress-cloud

@flotwig I'm confused with the recommendation in the article you shared. Those triggers are used in different use cases.  on: pull_request should be used for PR gate workflows. on: push should be used for workflows that should be run when a PR is merged.

on push, happens whenever you push changes to a branch, be it the feature branch, master or main
on pull_request happens when 'the workflow runs when a pull request is opened or reopened or when the head branch of the pull request is updated'.
So after you've created a pull request, on push and on pull_request will both happen whenever you update the head branch.
According to the article the information provided by on push is more accurate than on pull_request but I haven't double checked that myself.
It's worth a shot to try though right? 🤷♂

@mjhenkes The example workflow in the article you shared doesn't specify a branch so it will run the Cypress action on any pushed commit to any branch. That's basically the only scenario I can think of wherethe push and pull_request triggers could be used interchangeably.
In my situation (which is exceedingly common I can only assume), I only want to run Cypress tests for 1. PRs 2. against certain branches (in my case, just one: master). This means I have to use the pull_request trigger which will run when there is "activity on a pull request in the workflow's repository occurs" (on the master branch).  If I were to use the push trigger like you recommend, the only way it would run would be is if I changed the branch targeted by the trigger from master to the branch the PR is for.  And then for the next PR, the workflow would need to target that PR branch name. That, of course, isn't how PR gate workflows would ever work.

It looks like this issue is also related to a previous conversation in https://github.com/cypress-io/github-action/issues/124 involving @mellis481

@MikeMcC399 As you can see, I contribute at the end of that thread. I didn't include it in my original post listing code, but I do include COMMIT_MESSAGE which is the solution Gleb gives in that thread.  Here is my whole job FWIW:
- id: cypress-e2e-tests
  name: Cypress end-to-end tests
  uses: cypress-io/github-action@v4
  with:
    wait-on: 'https://localhost:9000/ui/vtx-ui-root-app/index.js'
    start: npm run start:local
    config-file: cypress/config/e2e.ts
    record: true
    install: false
    group: 'E2E'
    ci-build-id: ${{ needs.prepare.outputs.uuid }}
    tag: 'pull-request'
  env:
    NODE_TLS_REJECT_UNAUTHORIZED: 0
    CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }}
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    COMMIT_INFO_MESSAGE: ${{ github.event.pull_request.title }}
    COMMIT_INFO_SHA: ${{ github.event.pull_request.head.sha }}

@mellis481
This issue seems to have gone stale and I'm unsure what the next steps might be.
A new version of the action has been published which automatically pulls in any available PR information when recording. See https://github.com/cypress-io/github-action#automatic-pr-number--url-detection
You would access this functionality using
cypress-io/github-action@v6 or
<EMAIL_ADDRESS>Again, I'm unsure whether that would change your experience, but I thought I would let you know anyway!

@MikeMcC399 I'm still seeing this issue using cypress-io/github-action@v6.

@mellis481
Many thanks for your update to say that you are still experiencing this issue.
It looks like it is not directly an issue with cypress-io/github-action but more with the Cypress Cloud GitHub Integration as described on Cypress Cloud > Integrations > Source Control > GitHub.
We'd need some assistance from the Cypress Cloud team on this, since this part of the solution is not open source. We can't see what it is doing or fix it in this repo.
@emilyrohrbough
This issue is assigned to you. Are you still involved?

@MikeMcC399 Interestingly, when you just said you think this is a Cypress Cloud thing, I thought I'd compare the project settings for the repo I'm having a problem with with another that I am not. The only thing that I found that was different was that the problem repo did not have a "Default branch" set in Cypress Cloud. I created a PR after setting the Default branch in Cypress Cloud (to master) and it appears to have resolved this issue.
I'm finding the symptoms of a missing "Default branch" in Cypress Cloud strange. As I described in the thread, it appended "(merge)" to the status checks, but what I also found is that, if a GitHub user other than the person who created the PR re-ran the workflow, the status checks reported fine.
In any event, I'll close this issue.

@mellis481
Congratulations on solving the issue!  Thanks also for sharing what you did.

@MikeMcC399 Nevermind the issue is back again. :(

@mellis481

Nevermind the issue is back again.

That is rather disappointing 🙁 !
My previous comments still hold though, that this is unlikely to be an issue with github-action and so the Cypress Cloud team would need to assist.
If you don't get any reaction here and you are on a paid Cypress Cloud plan (Team, Business, or Enterprise), then presumably you could also open a Cypress Cloud  support ticket.

(merge) is added if it's detected that the commit message is generated from a merge commit, and our logic around that hasn't changed.

@MikeMcC399 Thanks. I opened a Cypress Cloud support ticket.
@flotwig Can you describe the logic that is used to append (merge) to status checks?


ConfigurableCell T triggers SwiftLint warning

Hey, @maxsokolov!
We have a minor issue with ConfigurableCell. Every time we implement ConfigurableCell and provide a typealias for T it triggers a SwiftLint warning based on type_name rule (which is enabled by default in SwiftLint):
../CustomTableCell.swift:13:15: warning: Type Name Violation: Type name should be between 3 and 60 characters long: 'T' (type_name)

https://github.com/maxsokolov/TableKit/blob/dd8e5d0625b0775e77d7c3464f542e9acb8e16ed/Sources/ConfigurableCell.swift#L25
As a workaround we disable this warning every time we implement ConfigurableCell protocol. It would be nice to rename T into something more meaningful like TableDisplayData or something similar to prevent this warning form being triggered by SwiftLint.

Hey @kean
This is really nice to have a meaningful name for this associatedtype. I have updated master and pushed new version v2.7.0 to Cocoapods.
Thank you for pointing that out.

Thanks!


Favicon Path Fix

Super minor PR
Got a path error in the _config.yml for the favicon.ico path when building a cookbook locally.
Updated images/icons/favicon.ico -> notebooks/images/icons/favicon.ico

Thanks for the fix @norlandrhagen!


Fabric Bot Configuration

The focus of these changes is to add the Fabric Bot rules into the repository.

/check-enforcer override


feat: face mask for kirakira effect #86epjek8p

Description

Currently, the kirakira effects have a high chance of displaying near the eyes and teeth, which are mostly lighter than its nearby area, and it causes the result to look scary for those cases.
Therefore, this PR adds face masks to the kirakira effect to prevent the center of sparkles located on people's faces.

Screenshots

Before
After

https://github.com/cardinalblue/pic-collage-ios/assets/40178645/29eb7ee3-38ad-4c52-bcbc-9f0c3978c28b

https://github.com/cardinalblue/pic-collage-ios/assets/40178645/ed0c7ccf-2382-4622-ad80-1ee440b8bda0

Hi @yyjim, I decided to change the implementation with the way I used for CBAddBlend and CBScreenBlend, and I'll make the PR ready for review again once I push the commit; thanks!

Hi @yyjim I'm going to merge the PR first, please feel free to leave comments, and I'll create another PR for them if needed
Thanks!


kafka adapter example fails

Describe the bug
Running e_08_kafka.py errors out
To Reproduce
Steps to reproduce the behavior:
cd csp/examples
python e_08_kafka.py

Traceback (most recent call last):
  File "/Users/goldbaum/Documents/csp/csp/examples/e_08_kafka.py", line 6, in <module>
    from csp.adapters.kafka import (
ImportError: cannot import name 'ProtoMessageMapper' from 'csp.adapters.kafka' (/Users/goldbaum/Documents/csp/csp/adapters/kafka.py)

Expected behavior
No error

I don't think ProtoMessageMapper is defined anywhere, though it is mentioned here: docs/wiki/api-references/Input-Output-Adapters-API.md


Langchain

Just some initial work
Swapped for my langchain agent and vectorizing the dom to get around size limits
works about the same as upstream though mine cant die overflowing context
but upstream kinda sucks.. so not saying much, were gonna have to dig in

Eh, still happening, seeing stuff like this
      Action Input:
      - https://www.billboard.com/articles/columns/hip-hop/8543645/la-hip-hop-history-timeline
      - \"Key events in LA hip hop history\"
      - https://www.latimes.com/entertainment-arts/music/story/2020-02-20/la-hip-hop-documentary-unsung-heroes
      - \"LA hip hop unsung heroes\"
      - https://www.npr.org/2019/08/08/748305947/la-hip-hop-and-the-rise-of-the-latinx-voice
      - \"Latinx influence on LA hip hop\"

note for future this is bugged, AgentExecutor needs to take domsimplifierFn so it can generate a fresh dom for each action


netcdf: fix darwin and more broadly clang builds

Description of changes
As tracked upstream, later versions of clang produce warning that triggers failure when building netcdf. This PR introduces a tried and true strategy of ignoring those warnings for the time being -- many many projects are not as strict as the latest clang versions would have them be.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

 There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4376

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 330670 run on aarch64-darwin 1

48 packages marked as broken and skipped:

c3d
ezminc
gplates
labplot
nco
netcdfcxx4
python311Packages.bambi
python311Packages.bambi.dist
python311Packages.flowmc
python311Packages.flowmc.dist
python311Packages.intensity-normalization
python311Packages.intensity-normalization.dist
python311Packages.medpy
python311Packages.medpy.dist
python311Packages.pydicom-seg
python311Packages.pydicom-seg.dist
python311Packages.pygmt
python311Packages.pygmt.dist
python311Packages.pymc
python311Packages.pymc.dist
python311Packages.pymedio
python311Packages.pymedio.dist
python311Packages.pyradiomics
python311Packages.pyradiomics.dist
python311Packages.shimmy
python311Packages.shimmy.dist
python311Packages.torchio
python311Packages.torchio.dist
python311Packages.worldengine
python311Packages.worldengine.dist
python312Packages.medpy
python312Packages.medpy.dist
python312Packages.pydicom-seg
python312Packages.pydicom-seg.dist
python312Packages.pygmt
python312Packages.pygmt.dist
python312Packages.pymedio
python312Packages.pymedio.dist
python312Packages.pyradiomics
python312Packages.pyradiomics.dist
python312Packages.shimmy
python312Packages.shimmy.dist
python312Packages.torchio
python312Packages.torchio.dist
python312Packages.worldengine
python312Packages.worldengine.dist
worldengine-cli
worldengine-cli.dist

2 packages failed to build and already failed to build on hydra master:

pymol: plain log
python312Packages.wrf-python: plain log

25 packages failed to build and are new build failures:

grass: plain log
merkaartor: log was empty
mni_autoreg: plain log
pymol.dist: plain log
python311Packages.arviz: log was empty
python311Packages.arviz.dist: log was empty
python311Packages.bsuite: log was empty
python311Packages.bsuite.dist: log was empty
python311Packages.corner: log was empty
python311Packages.corner.dist: log was empty
python311Packages.plotnine: plain log
python311Packages.plotnine.dist: plain log
python311Packages.qcodes: plain log
python311Packages.qcodes-contrib-drivers: log was empty
python311Packages.qcodes-contrib-drivers.dist: log was empty
python311Packages.qcodes.dist: plain log
python312Packages.arviz: log was empty
python312Packages.arviz.dist: log was empty
python312Packages.bsuite: log was empty
python312Packages.bsuite.dist: log was empty
python312Packages.corner: log was empty
python312Packages.corner.dist: log was empty
python312Packages.plotnine: plain log
python312Packages.plotnine.dist: plain log
python312Packages.wrf-python.dist: plain log

145 packages built:

ants
bicgl
bicpl
cdo
conglomerate
ebtks
eccodes
gdal (python312Packages.gdal)
gnudatalanguage
haskellPackages.hgdal
haskellPackages.hgdal.doc
inormalize
libminc
mapcache
mapnik
mapproxy
mapproxy.dist
mapserver
minc_tools
minc_widgets
n3
ncview
netcdf
netcdf-mpi
netcdffortran
oobicpl
openorienteering-mapper
pdal
perl536Packages.Tirex
perl536Packages.Tirex.devdoc
perl538Packages.Tirex
perl538Packages.Tirex.devdoc
python311Packages.boltztrap2
python311Packages.boltztrap2.dist
python311Packages.cartopy
python311Packages.cartopy.dist
python311Packages.datashader
python311Packages.datashader.dist
python311Packages.django-bootstrap4
python311Packages.django-bootstrap4.dist
python311Packages.django-bootstrap5
python311Packages.django-bootstrap5.dist
python311Packages.eccodes
python311Packages.fiona
python311Packages.fiona.dist
python311Packages.folium
python311Packages.folium.dist
python311Packages.gdal
python311Packages.geodatasets
python311Packages.geodatasets.dist
python311Packages.geopandas
python311Packages.geopandas.dist
python311Packages.gstools
python311Packages.gstools.dist
python311Packages.h5netcdf
python311Packages.h5netcdf.dist
python311Packages.inequality
python311Packages.inequality.dist
python311Packages.libpysal
python311Packages.libpysal.dist
python311Packages.mapclassify
python311Packages.mapclassify.dist
python311Packages.meshio
python311Packages.meshio.dist
python311Packages.momepy
python311Packages.momepy.dist
python311Packages.morecantile
python311Packages.morecantile.dist
python311Packages.netcdf4
python311Packages.netcdf4.dist
python311Packages.osmnx
python311Packages.osmnx.dist
python311Packages.pyogrio
python311Packages.pyogrio.dist
python311Packages.python-mapnik
python311Packages.python-mapnik.dist
python311Packages.rasterio
python311Packages.rasterio.dist
python311Packages.rio-tiler
python311Packages.rio-tiler.dist
python311Packages.rioxarray
python311Packages.rioxarray.dist
python311Packages.sfepy
python311Packages.sfepy.dist
python311Packages.wktutils
python311Packages.wktutils.dist
python311Packages.wrf-python
python311Packages.wrf-python.dist
python312Packages.boltztrap2
python312Packages.boltztrap2.dist
python312Packages.cartopy
python312Packages.cartopy.dist
python312Packages.django-bootstrap4
python312Packages.django-bootstrap4.dist
python312Packages.django-bootstrap5
python312Packages.django-bootstrap5.dist
python312Packages.eccodes
python312Packages.fiona
python312Packages.fiona.dist
python312Packages.folium
python312Packages.folium.dist
python312Packages.geodatasets
python312Packages.geodatasets.dist
python312Packages.geopandas
python312Packages.geopandas.dist
python312Packages.gstools
python312Packages.gstools.dist
python312Packages.h5netcdf
python312Packages.h5netcdf.dist
python312Packages.inequality
python312Packages.inequality.dist
python312Packages.libpysal
python312Packages.libpysal.dist
python312Packages.mapclassify
python312Packages.mapclassify.dist
python312Packages.meshio
python312Packages.meshio.dist
python312Packages.momepy
python312Packages.momepy.dist
python312Packages.morecantile
python312Packages.morecantile.dist
python312Packages.netcdf4
python312Packages.netcdf4.dist
python312Packages.osmnx
python312Packages.osmnx.dist
python312Packages.pyogrio
python312Packages.pyogrio.dist
python312Packages.python-mapnik
python312Packages.python-mapnik.dist
python312Packages.qcodes
python312Packages.qcodes-contrib-drivers
python312Packages.qcodes-contrib-drivers.dist
python312Packages.qcodes.dist
python312Packages.rasterio
python312Packages.rasterio.dist
python312Packages.rio-tiler
python312Packages.rio-tiler.dist
python312Packages.rioxarray
python312Packages.rioxarray.dist
python312Packages.sfepy
python312Packages.sfepy.dist
python312Packages.wktutils
python312Packages.wktutils.dist
saga
t-rex

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

gdal:

got build log for '/nix/store/5dsz2dbx2a8w8hqdwphgzynkfjzq3qjm-gdal-3.9.1' from 'daemon'
When evaluating attribute ‘gdal’:
warning: unnecessary-parallel-building
Meson, CMake and qmake already set enableParallelBuilding = true by default so it is not necessary.
Near pkgs/development/libraries/gdal/default.nix:210:3:
    |
210 |   enableParallelBuilding = true;
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unnecessary-parallel-building.md

haskellPackages.hgdal.doc:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

haskellPackages.hgdal:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/6rgl7llw3cag58sf5yr2x73iib4jz1gz-hgdal-<IP_ADDRESS>' from 'daemon'
When evaluating attribute ‘haskellPackages.hgdal’:
warning: build-tools-in-build-inputs
docbook_xml_dtd_43 is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
docbook-xsl-nons is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
getopt is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
gnum4 is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
gtk-doc is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
which is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/haskell-modules/generic-builder.nix:847:3:
    |
847 |   meta = { inherit homepage license platforms; }
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

netcdffortran:

got build log for '/nix/store/1raamzh5l2l52jmviji97g0is3fklpki-netcdf-fortran-4.4.5' from 'daemon'
When evaluating attribute ‘netcdffortran’:
warning: attribute-typo
A likely typo in the FFLAGS argument was found, did you mean CFLAGS or FCFLAGS?
Near pkgs/development/libraries/netcdf-fortran/default.nix:26:3:
   |
26 |   FFLAGS = [ "-std=legacy" ];
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/attribute-typo.md
warning: environment-variables-go-to-env
Environment variable FCFLAGS should be moved to env attribute rather than being passed directly to ‘stdenv.mkDerivation’.
Near pkgs/development/libraries/netcdf-fortran/default.nix:27:3:
   |
27 |   FCFLAGS = [ "-std=legacy" ];
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/environment-variables-go-to-env.md

netcdf:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/lq2622aigvm00q35w74j1psr711id5k7-netcdf-4.9.2' from 'daemon'
When evaluating attribute ‘netcdf’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/netcdf/default.nix:84:3:
   |
84 |   meta = {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

netcdf-mpi:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/56kad08qm6cjp4sg7vwibap7scgi8455-netcdf-mpi-4.9.2' from 'daemon'
When evaluating attribute ‘netcdf-mpi’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/netcdf/default.nix:84:3:
   |
84 |   meta = {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.boltztrap2.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/r6bjdjj60pnq7anymj6x94v1hl5n1r6r-python3.11-boltztrap2-24.1.1-dist' from 'daemon'
When evaluating attribute ‘python311Packages.boltztrap2.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boltztrap2/default.nix:63:5:
   |
63 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.boltztrap2:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/23pprr1pqi5izwhqxrz0f80jhys7dhk4-python3.11-boltztrap2-24.1.1' from 'daemon'
When evaluating attribute ‘python311Packages.boltztrap2’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boltztrap2/default.nix:63:5:
   |
63 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.datashader.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/datashader/default.nix:99:5:
   |
99 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.datashader:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/datashader/default.nix:99:5:
   |
99 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.h5netcdf.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/5kmlncaib4342ph0xzsr36ll9lrh2qm9-python3.11-h5netcdf-1.3.0-dist' from 'daemon'
When evaluating attribute ‘python311Packages.h5netcdf.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/h5netcdf/default.nix:46:5:
   |
46 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.h5netcdf:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/nvrm6p38d9pz8qb77vxxrb749r076gnf-python3.11-h5netcdf-1.3.0' from 'daemon'
When evaluating attribute ‘python311Packages.h5netcdf’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/h5netcdf/default.nix:46:5:
   |
46 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.netcdf4.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/g0dh3aw2698y96dffr76hi7pfjzgg6vi-python3.11-netcdf4-1.6.5-dist' from 'daemon'
When evaluating attribute ‘python311Packages.netcdf4.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/netcdf4/default.nix:73:5:
   |
73 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.netcdf4:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/xdjm1v8fv90i97549b8vvmdphd6b1r4m-python3.11-netcdf4-1.6.5' from 'daemon'
When evaluating attribute ‘python311Packages.netcdf4’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/netcdf4/default.nix:73:5:
   |
73 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.python-mapnik.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/8wrxaah1vbrxh9n6bd8yardc711gcr4m-python3.11-python-mapnik-3.0.16-unstable-2024-02-22-dist' from 'daemon'
When evaluating attribute ‘python311Packages.python-mapnik.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/python-mapnik/default.nix:132:5:
    |
132 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.python-mapnik:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/77lvh5vsny6jbli6m8x3xg4vqsap7q0j-python3.11-python-mapnik-3.0.16-unstable-2024-02-22' from 'daemon'
When evaluating attribute ‘python311Packages.python-mapnik’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/python-mapnik/default.nix:132:5:
    |
132 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.boltztrap2.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/98sg38dk427vzlk2jj33bmil2h558v64-python3.12-boltztrap2-24.1.1-dist' from 'daemon'
When evaluating attribute ‘python312Packages.boltztrap2.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boltztrap2/default.nix:63:5:
   |
63 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.boltztrap2:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/n9jjmb99301slaakvhqbk3jfcff04n2w-python3.12-boltztrap2-24.1.1' from 'daemon'
When evaluating attribute ‘python312Packages.boltztrap2’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boltztrap2/default.nix:63:5:
   |
63 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.h5netcdf.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/ji9vkrc8wjlfsl8vwh7w6xcf40k3a4mq-python3.12-h5netcdf-1.3.0-dist' from 'daemon'
When evaluating attribute ‘python312Packages.h5netcdf.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/h5netcdf/default.nix:46:5:
   |
46 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.h5netcdf:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/irg2a9x8i9rqm8mq48jbg6q8y0i8ciqv-python3.12-h5netcdf-1.3.0' from 'daemon'
When evaluating attribute ‘python312Packages.h5netcdf’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/h5netcdf/default.nix:46:5:
   |
46 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.netcdf4.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/d2mv1hqmy8r9c2ysnl9vrkw1q7ahpfb4-python3.12-netcdf4-1.6.5-dist' from 'daemon'
When evaluating attribute ‘python312Packages.netcdf4.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/netcdf4/default.nix:73:5:
   |
73 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.netcdf4:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/0mv2ba9kvqnzmhycvmlxn9i4hdsn4w1s-python3.12-netcdf4-1.6.5' from 'daemon'
When evaluating attribute ‘python312Packages.netcdf4’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/netcdf4/default.nix:73:5:
   |
73 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.python-mapnik.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/python-mapnik/default.nix:132:5:
    |
132 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.python-mapnik:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/python-mapnik/default.nix:132:5:
    |
132 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

t-rex:

warning: environment-variables-go-to-env
Environment variable PKG_CONFIG_ALLOW_CROSS should be moved to env attribute rather than being passed directly to ‘stdenv.mkDerivation’.
Near pkgs/build-support/rust/build-rust-package/default.nix:135:3:
    |
135 |   PKG_CONFIG_ALLOW_CROSS =
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/environment-variables-go-to-env.md

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 330670 run on x86_64-linux 1

13 packages marked as broken and skipped:

ezminc
python311Packages.bambi
python311Packages.bambi.dist
python311Packages.sunpy
python311Packages.sunpy.dist
python311Packages.worldengine
python311Packages.worldengine.dist
python312Packages.shimmy
python312Packages.shimmy.dist
python312Packages.worldengine
python312Packages.worldengine.dist
worldengine-cli
worldengine-cli.dist

8 packages failed to build and already failed to build on hydra master:

gmt: plain log
labplot: log was empty
pymol: plain log
python311Packages.pydicom-seg: plain log
python311Packages.pygmt: log was empty
python312Packages.pydicom-seg: plain log
python312Packages.pygmt: log was empty
python312Packages.wrf-python: plain log

6 packages failed to build and are new build failures:

pymol.dist: plain log
python311Packages.pydicom-seg.dist: plain log
python311Packages.pygmt.dist: log was empty
python312Packages.pydicom-seg.dist: plain log
python312Packages.pygmt.dist: log was empty
python312Packages.wrf-python.dist: plain log

225 packages built:

ants
apacheHttpdPackages.mod_tile (apacheHttpdPackages_2_4.mod_tile)
bicgl
bicpl
c3d
cdo
cloudcompare
conglomerate
ebtks
eccodes
elastix
entwine
gdal (python312Packages.gdal)
gnudatalanguage
gplates
grass
haskellPackages.hgdal
haskellPackages.hgdal.doc
inormalize
itk (itk_5)
itk_5_2
libminc
mapcache
mapnik
mapproxy
mapproxy.dist
mapserver
merkaartor
minc_tools
minc_widgets
mirtk
mni_autoreg
mrtrix
mysql-workbench
n3
nco
ncview
netcdf
netcdf-mpi
netcdfcxx4
netcdffortran
nixpkgs-manual
octavePackages.mapping
octavePackages.ncarray
octavePackages.netcdf
octopus
oobicpl
openorienteering-mapper
ovito
paraview
pdal
perl536Packages.Tirex
perl536Packages.Tirex.devdoc
perl538Packages.Tirex
perl538Packages.Tirex.devdoc
python311Packages.arviz
python311Packages.arviz.dist
python311Packages.boltztrap2
python311Packages.boltztrap2.dist
python311Packages.bsuite
python311Packages.bsuite.dist
python311Packages.cartopy
python311Packages.cartopy.dist
python311Packages.corner
python311Packages.corner.dist
python311Packages.datashader
python311Packages.datashader.dist
python311Packages.django-bootstrap4
python311Packages.django-bootstrap4.dist
python311Packages.django-bootstrap5
python311Packages.django-bootstrap5.dist
python311Packages.eccodes
python311Packages.fiona
python311Packages.fiona.dist
python311Packages.flowmc
python311Packages.flowmc.dist
python311Packages.folium
python311Packages.folium.dist
python311Packages.gdal
python311Packages.geodatasets
python311Packages.geodatasets.dist
python311Packages.geopandas
python311Packages.geopandas.dist
python311Packages.gstools
python311Packages.gstools.dist
python311Packages.h5netcdf
python311Packages.h5netcdf.dist
python311Packages.inequality
python311Packages.inequality.dist
python311Packages.intensity-normalization
python311Packages.intensity-normalization.dist
python311Packages.libpysal
python311Packages.libpysal.dist
python311Packages.mapclassify
python311Packages.mapclassify.dist
python311Packages.medpy
python311Packages.medpy.dist
python311Packages.meshio
python311Packages.meshio.dist
python311Packages.momepy
python311Packages.momepy.dist
python311Packages.morecantile
python311Packages.morecantile.dist
python311Packages.netcdf4
python311Packages.netcdf4.dist
python311Packages.osmnx
python311Packages.osmnx.dist
python311Packages.plotnine
python311Packages.plotnine.dist
python311Packages.pymc
python311Packages.pymc.dist
python311Packages.pymedio
python311Packages.pymedio.dist
python311Packages.pyogrio
python311Packages.pyogrio.dist
python311Packages.pyradiomics
python311Packages.pyradiomics.dist
python311Packages.python-mapnik
python311Packages.python-mapnik.dist
python311Packages.qcodes
python311Packages.qcodes-contrib-drivers
python311Packages.qcodes-contrib-drivers.dist
python311Packages.qcodes.dist
python311Packages.rasterio
python311Packages.rasterio.dist
python311Packages.rio-tiler
python311Packages.rio-tiler.dist
python311Packages.rioxarray
python311Packages.rioxarray.dist
python311Packages.sfepy
python311Packages.sfepy.dist
python311Packages.shimmy
python311Packages.shimmy.dist
python311Packages.simpleitk
python311Packages.simpleitk.dist
python311Packages.torchio
python311Packages.torchio.dist
python311Packages.wktutils
python311Packages.wktutils.dist
python311Packages.wrf-python
python311Packages.wrf-python.dist
python312Packages.arviz
python312Packages.arviz.dist
python312Packages.boltztrap2
python312Packages.boltztrap2.dist
python312Packages.bsuite
python312Packages.bsuite.dist
python312Packages.cartopy
python312Packages.cartopy.dist
python312Packages.corner
python312Packages.corner.dist
python312Packages.django-bootstrap4
python312Packages.django-bootstrap4.dist
python312Packages.django-bootstrap5
python312Packages.django-bootstrap5.dist
python312Packages.eccodes
python312Packages.fiona
python312Packages.fiona.dist
python312Packages.folium
python312Packages.folium.dist
python312Packages.geodatasets
python312Packages.geodatasets.dist
python312Packages.geopandas
python312Packages.geopandas.dist
python312Packages.gstools
python312Packages.gstools.dist
python312Packages.h5netcdf
python312Packages.h5netcdf.dist
python312Packages.inequality
python312Packages.inequality.dist
python312Packages.libpysal
python312Packages.libpysal.dist
python312Packages.mapclassify
python312Packages.mapclassify.dist
python312Packages.medpy
python312Packages.medpy.dist
python312Packages.meshio
python312Packages.meshio.dist
python312Packages.momepy
python312Packages.momepy.dist
python312Packages.morecantile
python312Packages.morecantile.dist
python312Packages.netcdf4
python312Packages.netcdf4.dist
python312Packages.osmnx
python312Packages.osmnx.dist
python312Packages.plotnine
python312Packages.plotnine.dist
python312Packages.pymedio
python312Packages.pymedio.dist
python312Packages.pyogrio
python312Packages.pyogrio.dist
python312Packages.pyradiomics
python312Packages.pyradiomics.dist
python312Packages.python-mapnik
python312Packages.python-mapnik.dist
python312Packages.qcodes
python312Packages.qcodes-contrib-drivers
python312Packages.qcodes-contrib-drivers.dist
python312Packages.qcodes.dist
python312Packages.rasterio
python312Packages.rasterio.dist
python312Packages.rio-tiler
python312Packages.rio-tiler.dist
python312Packages.rioxarray
python312Packages.rioxarray.dist
python312Packages.sfepy
python312Packages.sfepy.dist
python312Packages.simpleitk
python312Packages.simpleitk.dist
python312Packages.torchio
python312Packages.torchio.dist
python312Packages.wktutils
python312Packages.wktutils.dist
pytrainer
pytrainer.dist
qgis
qgis-ltr
qmapshack
saga
simpleitk
sumo
t-rex
udig
vpv

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

apacheHttpdPackages.mod_tile:

got build log for '/nix/store/4lcwvxl8jd962lf6pwn6aik7gnhmii1d-mod_tile-0.7.1' from 'daemon'
When evaluating attribute ‘apacheHttpdPackages.mod_tile’:
warning: unnecessary-parallel-building
Meson, CMake and qmake already set enableParallelBuilding = true by default so it is not necessary.
Near pkgs/servers/http/apache-modules/mod_tile/default.nix:57:3:
   |
57 |   enableParallelBuilding = true;
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unnecessary-parallel-building.md

c3d:

got build log for '/nix/store/30rl757iicanhdwy1g897s8hsaiawn8i-c3d-unstable-2021-09-14' from 'daemon'
When evaluating attribute ‘c3d’:
warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/graphics/c3d/default.nix:25:5:
   |
25 |     license = licenses.gpl3;
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md

gdal:

got build log for '/nix/store/5dsz2dbx2a8w8hqdwphgzynkfjzq3qjm-gdal-3.9.1' from 'daemon'
When evaluating attribute ‘gdal’:
warning: unnecessary-parallel-building
Meson, CMake and qmake already set enableParallelBuilding = true by default so it is not necessary.
Near pkgs/development/libraries/gdal/default.nix:210:3:
    |
210 |   enableParallelBuilding = true;
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unnecessary-parallel-building.md

gplates:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/lmgafhj0hy9a8rlhdbiz23vd9jwd890d-gplates-2.5' from 'daemon'
When evaluating attribute ‘gplates’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/applications/science/misc/gplates/default.nix:68:3:
   |
68 |   meta = with lib; {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

haskellPackages.hgdal.doc:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

haskellPackages.hgdal:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/6rgl7llw3cag58sf5yr2x73iib4jz1gz-hgdal-<IP_ADDRESS>' from 'daemon'
When evaluating attribute ‘haskellPackages.hgdal’:
warning: build-tools-in-build-inputs
docbook_xml_dtd_43 is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
docbook-xsl-nons is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
getopt is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
gnum4 is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
gtk-doc is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: build-tools-in-build-inputs
which is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/development/haskell-modules/generic-builder.nix:460:3:
    |
460 |   buildInputs = otherBuildInputs ++ optionals (!isLibrary) propagatedBuildInputs
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/build-tools-in-build-inputs.md
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/haskell-modules/generic-builder.nix:847:3:
    |
847 |   meta = { inherit homepage license platforms; }
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

itk_5_2:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/9jphy61mqr5pp3f7r0h5j4w9nwwr4rxz-itk-5.2.1' from 'daemon'
When evaluating attribute ‘itk_5_2’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/itk/generic.nix:115:5:
    |
115 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

itk:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/z13qm50c8dxkylhxj0l90v77w528iq3c-itk-5.4.0' from 'daemon'
When evaluating attribute ‘itk’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/itk/generic.nix:115:5:
    |
115 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

netcdfcxx4:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/2ahp31xz59mp7pbk7n6qv038zja8y88v-netcdf-cxx4-4.3.1' from 'daemon'
When evaluating attribute ‘netcdfcxx4’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/netcdf-cxx4/default.nix:31:3:
   |
31 |   meta = {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

netcdffortran:

got build log for '/nix/store/1raamzh5l2l52jmviji97g0is3fklpki-netcdf-fortran-4.4.5' from 'daemon'
When evaluating attribute ‘netcdffortran’:
warning: attribute-typo
A likely typo in the FFLAGS argument was found, did you mean CFLAGS or FCFLAGS?
Near pkgs/development/libraries/netcdf-fortran/default.nix:26:3:
   |
26 |   FFLAGS = [ "-std=legacy" ];
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/attribute-typo.md
warning: environment-variables-go-to-env
Environment variable FCFLAGS should be moved to env attribute rather than being passed directly to ‘stdenv.mkDerivation’.
Near pkgs/development/libraries/netcdf-fortran/default.nix:27:3:
   |
27 |   FCFLAGS = [ "-std=legacy" ];
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/environment-variables-go-to-env.md

netcdf:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/lq2622aigvm00q35w74j1psr711id5k7-netcdf-4.9.2' from 'daemon'
When evaluating attribute ‘netcdf’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/netcdf/default.nix:84:3:
   |
84 |   meta = {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

netcdf-mpi:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/56kad08qm6cjp4sg7vwibap7scgi8455-netcdf-mpi-4.9.2' from 'daemon'
When evaluating attribute ‘netcdf-mpi’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/libraries/netcdf/default.nix:84:3:
   |
84 |   meta = {
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

nixpkgs-manual:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.

octavePackages.mapping:

got build log for '/nix/store/hw2a50vm1x38rss2z8pfiqv562zgp28y-octave-9.2.0-mapping-1.4.2' from 'daemon'
When evaluating attribute ‘octavePackages.mapping’:
warning: patch-phase
patchPhase should not be overridden, use postPatch instead.
Near pkgs/development/interpreters/octave/build-octave-package.nix:96:10:
   |
96 |   inherit dontPatch patches patchPhase;
   |          ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/patch-phase.md

octavePackages.ncarray:

got build log for '/nix/store/n46jbznf1izv6bpgcbgg9w9nlm0049m6-octave-9.2.0-ncarray-1.0.6' from 'daemon'
When evaluating attribute ‘octavePackages.ncarray’:
warning: patch-phase
patchPhase should not be overridden, use postPatch instead.
Near pkgs/development/interpreters/octave/build-octave-package.nix:96:10:
   |
96 |   inherit dontPatch patches patchPhase;
   |          ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/patch-phase.md

octavePackages.netcdf:

got build log for '/nix/store/rcq1vcip3142904csi1abz7dk04y0ndz-octave-9.2.0-netcdf-1.0.17' from 'daemon'
When evaluating attribute ‘octavePackages.netcdf’:
warning: patch-phase
patchPhase should not be overridden, use postPatch instead.
Near pkgs/development/interpreters/octave/build-octave-package.nix:96:10:
   |
96 |   inherit dontPatch patches patchPhase;
   |          ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/patch-phase.md

octopus:

got build log for '/nix/store/00afix2mwkb1sq2c0s5qiafxrwbfjkb9-octopus-14.1' from 'daemon'
When evaluating attribute ‘octopus’:
warning: unnecessary-parallel-building
Meson, CMake and qmake already set enableParallelBuilding = true by default so it is not necessary.
Near pkgs/applications/science/chemistry/octopus/default.nix:88:3:
   |
88 |   enableParallelBuilding = true;
   |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unnecessary-parallel-building.md

python311Packages.boltztrap2.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/r6bjdjj60pnq7anymj6x94v1hl5n1r6r-python3.11-boltztrap2-24.1.1-dist' from 'daemon'
When evaluating attribute ‘python311Packages.boltztrap2.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boltztrap2/default.nix:63:5:
   |
63 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.boltztrap2:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/23pprr1pqi5izwhqxrz0f80jhys7dhk4-python3.11-boltztrap2-24.1.1' from 'daemon'
When evaluating attribute ‘python311Packages.boltztrap2’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boltztrap2/default.nix:63:5:
   |
63 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.datashader.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/sjaxlrdirvlb71g9c31icw3py1ykm8l4-python3.11-datashader-0.16.2-dist' from 'daemon'
When evaluating attribute ‘python311Packages.datashader.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/datashader/default.nix:99:5:
   |
99 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.datashader:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/9ngvkx4968knpm43g7z91cy6zb0rzywb-python3.11-datashader-0.16.2' from 'daemon'
When evaluating attribute ‘python311Packages.datashader’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/datashader/default.nix:99:5:
   |
99 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.h5netcdf.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/5kmlncaib4342ph0xzsr36ll9lrh2qm9-python3.11-h5netcdf-1.3.0-dist' from 'daemon'
When evaluating attribute ‘python311Packages.h5netcdf.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/h5netcdf/default.nix:46:5:
   |
46 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.h5netcdf:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/nvrm6p38d9pz8qb77vxxrb749r076gnf-python3.11-h5netcdf-1.3.0' from 'daemon'
When evaluating attribute ‘python311Packages.h5netcdf’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/h5netcdf/default.nix:46:5:
   |
46 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.netcdf4.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/g0dh3aw2698y96dffr76hi7pfjzgg6vi-python3.11-netcdf4-1.6.5-dist' from 'daemon'
When evaluating attribute ‘python311Packages.netcdf4.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/netcdf4/default.nix:73:5:
   |
73 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.netcdf4:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/xdjm1v8fv90i97549b8vvmdphd6b1r4m-python3.11-netcdf4-1.6.5' from 'daemon'
When evaluating attribute ‘python311Packages.netcdf4’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/netcdf4/default.nix:73:5:
   |
73 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.python-mapnik.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/8wrxaah1vbrxh9n6bd8yardc711gcr4m-python3.11-python-mapnik-3.0.16-unstable-2024-02-22-dist' from 'daemon'
When evaluating attribute ‘python311Packages.python-mapnik.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/python-mapnik/default.nix:132:5:
    |
132 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python311Packages.python-mapnik:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/77lvh5vsny6jbli6m8x3xg4vqsap7q0j-python3.11-python-mapnik-3.0.16-unstable-2024-02-22' from 'daemon'
When evaluating attribute ‘python311Packages.python-mapnik’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/python-mapnik/default.nix:132:5:
    |
132 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.boltztrap2.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/98sg38dk427vzlk2jj33bmil2h558v64-python3.12-boltztrap2-24.1.1-dist' from 'daemon'
When evaluating attribute ‘python312Packages.boltztrap2.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boltztrap2/default.nix:63:5:
   |
63 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.boltztrap2:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/n9jjmb99301slaakvhqbk3jfcff04n2w-python3.12-boltztrap2-24.1.1' from 'daemon'
When evaluating attribute ‘python312Packages.boltztrap2’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/boltztrap2/default.nix:63:5:
   |
63 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.h5netcdf.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/ji9vkrc8wjlfsl8vwh7w6xcf40k3a4mq-python3.12-h5netcdf-1.3.0-dist' from 'daemon'
When evaluating attribute ‘python312Packages.h5netcdf.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/h5netcdf/default.nix:46:5:
   |
46 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.h5netcdf:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/irg2a9x8i9rqm8mq48jbg6q8y0i8ciqv-python3.12-h5netcdf-1.3.0' from 'daemon'
When evaluating attribute ‘python312Packages.h5netcdf’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/h5netcdf/default.nix:46:5:
   |
46 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.netcdf4.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/d2mv1hqmy8r9c2ysnl9vrkw1q7ahpfb4-python3.12-netcdf4-1.6.5-dist' from 'daemon'
When evaluating attribute ‘python312Packages.netcdf4.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/netcdf4/default.nix:73:5:
   |
73 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.netcdf4:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/0mv2ba9kvqnzmhycvmlxn9i4hdsn4w1s-python3.12-netcdf4-1.6.5' from 'daemon'
When evaluating attribute ‘python312Packages.netcdf4’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/netcdf4/default.nix:73:5:
   |
73 |     maintainers = [ ];
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.python-mapnik.dist:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/1czak465cz4hsr4q8avlipvi1nffzz0p-python3.12-python-mapnik-3.0.16-unstable-2024-02-22-dist' from 'daemon'
When evaluating attribute ‘python312Packages.python-mapnik.dist’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/python-mapnik/default.nix:132:5:
    |
132 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

python312Packages.python-mapnik:

Package is missing maintainers.
If the package is using runCommand please make sure to inherit or list one or more maintainers.
got build log for '/nix/store/nyi30sjszm9l2d7m2w0zwfdjwl4wim4y-python3.12-python-mapnik-3.0.16-unstable-2024-02-22' from 'daemon'
When evaluating attribute ‘python312Packages.python-mapnik’:
warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/python-mapnik/default.nix:132:5:
    |
132 |     maintainers = [ ];
    |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/maintainers-missing.md

t-rex:

got build log for '/nix/store/lmlpsvbzdgcj7sm5l70wn60brkbcvjs3-t-rex-0.15.0-alpha3' from 'daemon'
When evaluating attribute ‘t-rex’:
warning: environment-variables-go-to-env
Environment variable PKG_CONFIG_ALLOW_CROSS should be moved to env attribute rather than being passed directly to ‘stdenv.mkDerivation’.
Near pkgs/build-support/rust/build-rust-package/default.nix:135:3:
    |
135 |   PKG_CONFIG_ALLOW_CROSS =
    |   ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/environment-variables-go-to-env.md

vpv:

got build log for '/nix/store/l9w71cg465jamybpdmnx8lb9niqvr0zq-vpv-0.8.2' from 'daemon'
When evaluating attribute ‘vpv’:
warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/graphics/vpv/default.nix:60:5:
   |
60 |     license = lib.licenses.gpl3;
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md

Thanks for running those reviews; my Linux laptop crashed before it finished with the review script 😅.
I'm a bit surprised to see new failures introduced according to the Linux review pass; I wonder if that's possibly not the correct interpretation of those failures (they are new as of some previous Hydra run but not specifically introduced by this PR).

Ok, I didn't check all of the 6 "new failures" but I did check the first one (pymol.dist) which fails on master as well and lends credence to the theory that these are not truly new failures as-in "caused by this PR."

I can confirm that all packages fail on current master, too.

I can also confirm that all packages marked as "new build failures" on aarch64-darwin are already present on master (mostly due to error: Package ‘pmix-5.0.3’ in [...]/pkgs/development/libraries/pmix/default.nix:82 is not available on the requested hostPlatform)

Although this will cause a few rebuilds, it still isn't enough to warrant a staging cycle, so I am fine merging this to master

I've put up a PR to hopefully address this in the netCDF v4.9.3, https://github.com/Unidata/netcdf-c/pull/2977.


[BUG] Small bug when using big-AGI 2

Description
Decided to try to use big-AGI 2 a bit (hopefully you'll release it soon enough), and there's this small thing. For some reason, big-AGI is sending the system prompt for Anthropic as an array. It works with the official API, but it's undocumented, so I think it would be better to make it align to what the official API says. Other implementations (like proxies for LLMs) rely on the official API docs, so I stumbled upon an issue of a proxy not supporting this way of sending the system prompt.
Basically, big-AGI sends this:
{"max_tokens":4096,"model":"claude-3-5-sonnet-20240620","system":[{"type":"text","text":"You are an AI conversation titles assistant who specializes in creating expressive yet few-words chat titles."}], "messages":REDACTED,"stream":false,"temperature":0.5}

Notice how system is an array of entities. If you check the official docs at https://docs.anthropic.com/en/api/messages, they specify that the system parameter should be just a string. I guess this is also a bug on their end (for not properly verifying the inputs), but I think big-AGI should just stick to the default way :)

Proposed fix: make big-AGI 2 always pass the system prompt as a simple string to Anthropic's Messages API, not as an array.
Device and browser
Arch Linux, Brave version: 1.68.137 Chromium: 127.0.6533.100
Screenshots and more
No response
Willingness to Contribute

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

@hourianto great find. I'm unsure whether to fix or not, as there are reasons for this. Big-AGI ad had the Network stack fully rewritten to enable multimodality, function calling, and more.
It's not an Anthropic bug for not verifying, it's how Anthropic truly works under the scenes. It's the way to enable images in system prompts and multi-part (image, text, audio, text) system prompt. The docs don't document this Yet, but they will soon.
For this specific case I guess I can add a hot fix and downcast the multi-part system message to a single text string, but in the future we'll be back to the current behavior. Again: our new network stack (AIX) is awesome.

@enricoros okay then, fair enough, as long as Anthropic docs update it soon enough. But I've also tested passing image message type to the system prompt in an array, and the API tells me:
{"type":"error","error":{"type":"invalid_request_error","message":"system.0.type: Input should be 'text'"}}

Or do you have some inside knowledge from Anthropic that they will allow this in the future?

@hourianto I'll do the down mix in a bit, it's 5 minutes.
What's important is that I keep the high level representation (multi-part, etc.) before the down mix into a single text.
Here, this is the official Anthropic python SDK:
https://github.com/anthropics/anthropic-sdk-python/blob/main/src%2Fanthropic%2Ftypes%2Fmessage_create_params.py#L146
Valid are "string" and [{type:"text", text:"..."}, ..] for now. But you can see where this is going.

@hourianto you got it. LMK if this works as expected.

@hourianto today Anthropic released a new API, and in the first example they show a system prompt with 2 parts :)
https://docs.anthropic.com/en/docs/build-with-claude/prompt-caching#can-i-use-prompt-caching-at-the-same-time-as-other-betas
Please let em know if you still need this feature, because I may revert it, for the purpose of adding support for caching.

@enricoros yeah, I saw it too, I guess I'll just patch it on the proxy :)


Grammar Fix

Rearranged a sentence for more correct grammar. One line change.

That sentence looks like it's written as intended. It's emphasizing the fact that the data itself won't go on the chain (although a reference to the data will).

:laughing:
Yes, I did. Thanks.


Upgrade to v1.18.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin please rerender

@conda-forge-admin, please rerender

Hi @marcelotrevisani would you able to approve this and the related ones please? Appears @mariusvniekerk is on holidays.
https://github.com/conda-forge/opentelemetry-sdk-feedstock/pull/27 (depends on this)
https://github.com/conda-forge/opentelemetry-exporter-otlp-proto-http-feedstock/pull/10 (depends on above)
https://github.com/conda-forge/opentelemetry-exporter-otlp-proto-grpc-feedstock/pull/13 (depends on above)


@ApiResponse response parameter not used in 3.0.0

Starting with 3.0.0 (in 2.9.2 it worked properly)
@ApiResponse(code = 404, message = "Not Found", response = CustomError::class)
The 404 - Not Found is in the documentation, but the defined response (CustomError in example) not shown in the generated documentation (response sample and model)

Thanks for reporting @varjasz

Same issue here.
After some debugging, root cause should be: https://github.com/springfox/springfox/blob/07a4c86d70b791f21c2d2f656a863920b8c883c7/springfox-swagger2/src/main/java/springfox/documentation/swagger2/mappers/ServiceModelToSwagger2Mapper.java#L117
Springfox 3.0 uses v3 models by default, but source.getResponses() gives wrong type. To workaround it for now, add:
springfox.documentation.swagger.use-model-v3=false in your application.properties.

To workaround it for now, add: springfox.documentation.swagger.use-model-v3=false

The prescribed workaround doesn't seem to work for ResponseEntity<?> return types. I'm not sure if that's a separate issue or if it's part and parcel to this bug.

To workaround it for now, add: springfox.documentation.swagger.use-model-v3=false

The prescribed workaround doesn't seem to work for ResponseEntity<?> return types. I'm not sure if that's a separate issue or if it's part and parcel to this bug.

I can confirm the fix with springfox.documentation.swagger.use-model-v3=false for doc type DocumentationType.SWAGGER_2.
On the other hand, shouldn't it work out of the box with doc type DocumentationType.OAS_30? I tried it both with and without the app.prop setting but it behaves the same as the initial issue by not showing up at all.

Also getting this on springfox 3.0.0 using OAS_30. Specifically, the problem is that my POST requests return a body with 201 responses, which are incorrectly labelled to have no body. Overriding this has no effect. The side-effect of this is that generated api clients behave incorrectly.

I tried with springfox.documentation.swagger.use-model-v3=false, but then the globalRequestParameters I had configured in the Docket didn't work anymore (some custom global headers).
After a few hours I found a way to add my custom errors as a global response. It may not be a suitable solution if your endpoints have different custom errors, but in my case it was good enough and hopefully it will save someone's time, so I'll share it anyway.
Here's an example on how to add the class CustomError as a global response for POST operations that return a status code  400
@Bean
    public Docket api(TypeResolver typeResolver) {

        return new Docket(DocumentationType.SWAGGER_2)
                .useDefaultResponseMessages(false)
                // omitted config...
                .additionalModels(
                        typeResolver.resolve(CustomError.class)
                )
                .globalResponses(
                        HttpMethod.POST,
                        List.of(
                                new ResponseBuilder()
                                        .code("400")
                                        .description("some description..")
                                        .representation(MediaType.APPLICATION_JSON)
                                        .apply(r ->
                                                r.model(m ->
                                                        m.referenceModel(rm ->
                                                                rm.key(k ->
                                                                        k.qualifiedModelName(q ->
                                                                                q.namespace(CustomError.class.getPackageName())
                                                                                .name(CustomError.class.getSimpleName()))))))
                                        .build()
                        ))
    }

Note that you need to register the class with typeResolver, otherwise it won't work.
It doesn't look pretty but hey, it's only temporary

As already pointed out, the bug is tied to an empty set of produces media type(s) for the operation. A simple workaround it is to explicitly set your @XXXXXMapping produces value on your operation (i.e. @GetMapping(produces={"application/json"})).
I would recommend avoid setting ~springfox.documentation.swagger.use-model-v3=false~ since it may have unintended consequences as observed by this issue and other issues.
FYI... root cause of this particular issue is tied to SwaggerResponseMessageReader class. It's v2 counterpart  ResponseMessagesReader does not suffer from this bug because it will default produces to */* if its empty.

@ale-rd 's solution worked, and it's still possible to add custom error responses by specifying @ApiResponse for specific endpoints, but you still have to register your custom error models in .additionalModels.

@fduser1 how we can overcome this by only defining @Produces and @Consumes in class level ?

Is there any update on this issue?

I got the same issue, but it's caused by spring.main.lazy-initialization = true, so don't override this configuration.

set your @XXXXXMapping produces value on your operation (i.e. @GetMapping(produces={"application/json"})).
That would solve your problem ;)


rust-analyzer reports proc-macro panic while rustc doesn't

Cargo.toml:
[package]
name = "proc-macro-test"
version = "0.1.0"
edition = "2018"

[dependencies]
derive_builder = "0.9.0"

src/lib.rs:
#[derive(Default, derive_builder::Builder)]
#[builder(default)]
struct Foo {}

Expected
rust-analyzer reports no errors on src/lib.rs.
Actual
rust-analyzer reports an error with message: proc macro returned error: proc-macro panicked: Couldn't parse default expression `Trait`: "expected curly braces".
cargo check passes.
Meta

Server version: rust-analyzer 60c501f
rustc version: rustc 1.51.0 (2fd73fabe 2021-03-23)

Server version: rust-analyzer 60c501f

Please update rust-analzyer, your version is 2 months ago :)

Oh, my coc-rust-analyzer auto update didn't work then :(

Auto updates by coc-rust-analyzer was failing silently for some reason, it's working on 2021-03-22 now. Thanks!


[mb-4627] Payment request cards for move tab

Description
This PR creates a new component, PaymentRequestCard, to display in a list of all payment requests for a move locator in the TIO tab UI.
It also creates a new page component MovePaymentRequests that adds a react-query hook to call the /moves/{locator}/payment-requests endpoint.
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?
Setup
Add any steps or code to run in this section to help others prepare to run your code:
make db_dev_e2e_populate
make server_run
make office_client_run

Sign in as the TIO office user
Find a payment request from the queue and note the move locator code
Edit the URL to be officelocal:3000/moves/[locator]/payment-requests where you add the locator value
It should navigate you to the payment requests tab of for that move locator and show a list of payment request cards

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
this article explains more about the approach used.

Screenshots
If this PR makes visible UI changes, an image of the finished UI can help reviewers and casual
observers understand the context of the changes. A before image is optional and
can be included at the submitter's discretion.
Consider using an animated image to show an entire workflow instead of using multiple images. You may want to use GIPHY CAPTURE for this! 📸
Please frame screenshots to show enough useful context but also highlight the affected regions.

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against b87542b2044cae1541fbdfa1e172432570ff1036

It looks like we're using the wrong icons on the payment request that has both accepted and rejected amounts. Payment requests should only use the times and check icons.
Sorry for the outdated screenshot in the Jira story - that was my oversight.
Other than that, this PR checks all the design boxes!

@amanda5iu This should be fixed now please take a look at the new Happo diff


chore(scripts): remove resolved ERR_COP style exceptions

This PR removes ERR_COP style exceptions that have been resolved in #11825.

bors merge


Implements opinionated decorator lifecycle

This adds to the set of decorators that can be applied to a node,
and puts them in a uniform setting. The ordering is provided in
function_base.resolve_nodes -- the algorithm is as follows:

If there is a list of function resolvers, apply them one
after the other. Otherwise, apply the default function resolver
which will always return just the function. This determines whether to
proceed -- if any function resolver is none, short circuit and return
an empty list of nodes.

If there is a list of node creators, that list must be of length 1
-- this is determined in the node creator class. Apply that to get
the initial node.

If there is a list of node expanders, apply that. This must be a
list of length one. This gives out a list of nodes.

If there is a node transformer, apply that. Note that the node transformer
gets applied individually to just the sink nodes in the subdag. It subclasses
"DagTransformer" to do so.

Return the final list of nodes.

[Short description explaining the high-level reason for the pull request]
Additions

Removals

Changes

Testing

Screenshots
If applicable
Notes

Todos

Checklist

[x] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the TODO link to standards
[x] Passes all existing automated tests
[ ] Any change in functionality is tested
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist
Python

[ ] python 3.6
[ ] python 3.7

TODO:

[ ] Change to have transform be a superclass (much like config), with to as the method
[ ] Add transform to documentation

So what's net new here? Just the transform decorator? Suggestion on name: augment. Transform is a bit overloaded a term.
Otherwise the decorator lifecycle is largely a refactor of existing behavior, right?

The decorator lifecycle is solidified and expanded -- moved some things around, but yeah, a refactor of existing behavior. Technically this allows models + parametrization together (whereas before it wouldn't), although that could get a little weird and probably won't be used much.

TODO left prior to publishing:

[ ] Fix @skrawcz's requests
[ ] Add instructions for writing your own node lifecycle components
[ ] Add tests to ensure that @config.when decorator works


err instead of air

Fixes #5432

Definitely a critical issue.

LGTM, thanks for the high impact PR 🤣


Version Solving Failed

Because audio_recorder <0.0.5 requires SDK version >=1.8.0 <2.0.0 and audio_recorder >=0.0.5 <1.0.0 depends on path_provider ^0.4.1, audio_recorder <1.0.0 requires path_provider ^0.4.1.
And because google_fonts >=2.0.0 depends on path_provider ^2.0.0, google_fonts >=2.0.0 is incompatible with audio_recorder <1.0.0.
And because audio_recorder >=0.0.6 depends on file ^5.0.4 and shared_preferences_linux >=2.0.0 depends on file ^6.0.0, one of google_fonts >=2.0.0 or audio_recorder any or shared_preferences_linux >=2.0.0 must be false.
And because utool depends on shared_preferences ^2.0.15 which depends on shared_preferences_linux ^2.0.1, google_fonts >=2.0.0 is incompatible with audio_recorder.
So, because utool depends on both google_fonts ^3.0.1 and audio_recorder any, version solving failed.
i am trying to use latest versions of audio_recorder, path_provider , google_fonts ,shared_preferences

This error message is indicating that the version of audio_recorder you are trying to use depends on old versions of common dependencies (path_provider, file), and so isn't compatible with the latest version of other packages. If that's the latest version of audio_recorder, then you'll need to contact the developer about updating, or fork it to update the dependencies yourself.
Closing as this is not a Flutter bug.


Vector2(position) constructor causes an error

Godot 3.1 alpha2
I get an error when I try to construct a Vector2 from another one:
extends Node2D

func _draw():
	var pos = self.position
	var angle = PI
	draw_set_transform(Vector2(pos), angle, Vector2(1,1))

Causes an error at the last line:
SCRIPT ERROR: GDScript::reload: Parse Error: No constructor of 'Vector2' matches the signature 'Vector2(var)'.
          At: built-in:7

This code worked in Godot 3.0.6, although I have to admit it can be fairly simplified :p
The same happens with Vector3.

Are you sure that it worked in 3.0.6? I didn't think that this feature existed before.
I added this (and a few other things) here: https://github.com/godotengine/godot/pull/21348

It worked before because I tested it :) it was part of my codebase for a long time as well

Yeah, I am getting this same error in 3.1 on code that ran fine in 3.0.6; passing a position variable that is created on the fly causes it.  Game won't even run now because of it.

I did some regression testing using git bisect, this is caused by https://github.com/godotengine/godot/pull/19264
@vnen The fix for this seems pretty simple, but the concern that @akien-mga had was that it would be hiding a deeper bug. Would you mind looking into it?

Sorry for the delay on this. It seems the fix wasn't very difficult, I just hadn't the time.


Install cuDF-py against python 3.10 on Databricks

Fix on Databricks runtime for : https://github.com/NVIDIA/spark-rapids/issues/11394
Enable the udf_cudf_test test case for Databricks-13.3
Rapids 24.10+ drops python 3.9 or below conda packages. ref: https://docs.rapids.ai/notices/rsn0040/
Install cuDF-py packages against python 3.10 and above on Databricks runtime to run UDF cuDF tests, because on DB-13.3 Conda is not installed by default.

build

The pre-merge CI can not cover the udf-cudf python tests,
Verified the PR locally, both the init script and udf-cudf tests got PASS:

failed unrelated cases: test_broadcast_join_with_conditionals

build