-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Sync from noir #5475
feat: Sync from noir #5475
Conversation
fix: Slice coercions (noir-lang/noir#4640) chore(ci): add warning sticky comment (noir-lang/noir#4647) fix(ssa): Fix slice intrinsic handling in the capacity tracker (noir-lang/noir#4643) chore: fix versioning of `bn254_blackbox_solver` crate (noir-lang/noir#4638) chore: fix acvm crates reporting errors as JS packages (noir-lang/noir#4637) chore: Release Noir(0.26.0) (noir-lang/noir#4526) chore: convert `BlockExpression` into a standard struct (noir-lang/noir#4623) chore(github): Improve PR template "document later" checkbox description (noir-lang/noir#4625) chore: Update integers.md to note support for Fields using `from_integer` (noir-lang/noir#4536) chore: update docs with function names to match version 0.25.0 specifications (noir-lang/noir#4466) feat: add specific error for attempting `string[x] = ".."` (noir-lang/noir#4611) fix(ssa): Use accurate type during SSA AsSlice simplficiation (noir-lang/noir#4610)
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. What's wrong with native code?Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs. Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. Values are compared against data from master at commit L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 16 txs.
Circuits statsStats on running time and I/O sizes collected for every circuit run across all benchmarks.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contract classes are registered in the tx.
Transaction size based on fee payment method
Transaction processing duration by data writes.
|
Automated pull of development from the [noir](https://github.com/noir-lang/noir) programming language, a dependency of Aztec. BEGIN_COMMIT_OVERRIDE chore: delete `R1CSTransformer` (#4649) fix: Slice coercions (#4640) chore(ci): add warning sticky comment (#4647) fix(ssa): Fix slice intrinsic handling in the capacity tracker (#4643) chore: fix versioning of `bn254_blackbox_solver` crate (#4638) chore: fix acvm crates reporting errors as JS packages (#4637) chore: Release Noir(0.26.0) (#4526) chore: convert `BlockExpression` into a standard struct (#4623) chore(github): Improve PR template "document later" checkbox description (#4625) chore: Update integers.md to note support for Fields using `from_integer` (#4536) chore: update docs with function names to match version 0.25.0 specifications (#4466) feat: add specific error for attempting `string[x] = ".."` (#4611) fix(ssa): Use accurate type during SSA AsSlice simplficiation (#4610) END_COMMIT_OVERRIDE --------- Co-authored-by: sirasistant <[email protected]>
Automated pull of development from the noir programming language, a dependency of Aztec.
BEGIN_COMMIT_OVERRIDE
chore: delete
R1CSTransformer
(noir-lang/noir#4649)fix: Slice coercions (noir-lang/noir#4640)
chore(ci): add warning sticky comment (noir-lang/noir#4647)
fix(ssa): Fix slice intrinsic handling in the capacity tracker (noir-lang/noir#4643)
chore: fix versioning of
bn254_blackbox_solver
crate (noir-lang/noir#4638)chore: fix acvm crates reporting errors as JS packages (noir-lang/noir#4637)
chore: Release Noir(0.26.0) (noir-lang/noir#4526)
chore: convert
BlockExpression
into a standard struct (noir-lang/noir#4623)chore(github): Improve PR template "document later" checkbox description (noir-lang/noir#4625)
chore: Update integers.md to note support for Fields using
from_integer
(noir-lang/noir#4536)chore: update docs with function names to match version 0.25.0 specifications (noir-lang/noir#4466)
feat: add specific error for attempting
string[x] = ".."
(noir-lang/noir#4611)fix(ssa): Use accurate type during SSA AsSlice simplficiation (noir-lang/noir#4610)
END_COMMIT_OVERRIDE