Skip to content
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

dearb patching #1

Closed
wants to merge 200 commits into from
Closed

dearb patching #1

wants to merge 200 commits into from

Conversation

qdrs
Copy link

@qdrs qdrs commented Jun 20, 2023

JoshLind and others added 30 commits May 31, 2023 09:27
Reported by community member @urkesaptos-labs#1518

Test plan: Click this link it works
* added default custom header

* fixes on comments

* moved the client_builder to new file

* fixes from comment
[Executor]  moving block gas limit to state computer, refactoring and fixing tests
…-labs#8342)

* added fetching and update get public key method

* fixes from comment

* update method comment, and change fetch range limit from 20 to 10
…s#8442)

* Update clients to include custom headers

* bump version

* created metadata util class for get_version()
* Change directory and add item sidebar

* Change title

* Fix image link

* Text review

* Update aptos-db-restore.md

* Update aptos-db-restore.md

* Fix headings

* Fix tip

* Restructure and rephrase text. Add text to describe required options

* Update aptos-db-restore.md

* Update developer-docs-site/docs/nodes/full-node/aptos-db-restore.md

---------

Co-authored-by: David Wolinsky <isaac.wolinsky@gmail.com>
* Rebase per @banool

aptos-labs#8416 (comment)

Squashed commit 1:
Bump CLI version to 1.0.15

Squashed commit 2:
Update current release date, Cargo.lock

Squashed commit 3:
Modify for v2.0.0 release

Squashed commit 4:
Re-insert v1.0.14 changelog section per @banool

aptos-labs#8416 (comment)

* Remove erroneous double cash sign
### Description

This makes it easier to inspect node logs after running a successful smoke test.

Example usage:
```
LOCAL_SWARM_SAVE_LOGS=1 cargo test --package smoke-test test_full_node_basic_flow -- --nocapture
```

The last logged line will have the location, e.g.,
```
Logs located at /var/folders/7h/r8yg843j0tl24vsc33ddl9s40000gn/T/.tmpHbbwHX
```
* add newline to fix linting error

* remove newline

* poetry run isort, poetry run black
rustielin and others added 26 commits June 15, 2023 06:01
…s-labs#8599)

* Revert "Revert "[gha][docker] only push to GAR on PR; push to ECR on postcommit" (aptos-labs#8514)"

This reverts commit c32e918.

* [forge] find latest images based on cloud

* [gha] make GCP the default target registry for docker build

Co-authored-by: Balaji Arun <balaji@aptoslabs.com>

* [gha/docker] make remote TARGET_REGISTRY backwards compatible

* [testsuite] find docker images on GCP using crane

---------

Co-authored-by: Balaji Arun <balaji@aptoslabs.com>
* [aptos-vm] Skip converting storage error

* fixup! [aptos-vm] Skip converting storage error
… days of ownership

Moved the unit tests to a different file

Added the token_lockup unit tests to move_unit_tests.rs
Co-authored-by: rustielin <rustielin@users.noreply.github.com>
* init

* fix lint

* fix linter

* fix trimspace

* fix comment

* fix md
[BlockSTM] Better naming for execution task
* init

* new schema

* fix comment and lint

* fix comment and schema

* add md

---------

Co-authored-by: chan-bing <zzywullr@gmail.com>
…example (aptos-labs#8682)

* Remove --bytecode-version requirement

* Remove the "view functions aren't supported" statement

* Add an example of a view function request via CLI
* [GHA] Use spot VM for executor-performance

* test

* duplicate spot runner

* point workflow to main
) (aptos-labs#8636)

* Fix aptos-labs#7932

Docgen should output attributes (aptos-labs#7932).

Output attributes (e.g., #[view] or #[resource_group(scope = global)])
from docgen for move code.  Currently only handles attibutes on
Function, Script/Module, and Struct/Resource.

Note that attributes are allowed on some other syntactic objects
(address scope, use statement, const definition, spec), but how to
format these usefully in docgen is unclear.  for these in docgen is
unclear.

Also fix an unrelated bug discovered when adapting
attribute_placement.move as a test of docgen: previously, only a
single Module/Script per input file would be output in docgen.

* Update move library docs with new docgen.

---------

Co-authored-by: Brian R. Murphy <brianrmurphy@gmail.com>
aptos-labs#8697)

We have a few odd cases, and need to figure out if emitter is causing issues, or nodes.
@qdrs qdrs closed this Jun 20, 2023
khokho pushed a commit that referenced this pull request May 14, 2024
* jwk types update

* update

* update

* jwk txn and execution

* update

* fix dummy

* update

* update

* update

* update

* update

* update

* remove dummy txns

* check voting power than verify signature

* fix warnings

* update

* update QuorumCertifiedUpdate struct
khokho pushed a commit that referenced this pull request May 14, 2024
* types update from randomnet

* update

* lint

* lint
khokho pushed a commit that referenced this pull request May 14, 2024
…#12462)

* [compiler-v2] Making v2 the basis of the prover (step #1)

This adds the missing parts to let compiler v2 fully support the specification language, and switches the prover to use v2 as the basis for verification of v1 bytecode. There is one further step needed to run the prover also on the code generated by v2 but that one is smaller than here. Notice that with this, we are dogfooding the v2 compiler frontend in production with the Move prover. There is no switching back and forth, code for the v1 prover integration has been removed. In more detail this does the following:

- There are two new env processors, the spec_checker and the spec_rewriter:
    - `spec_checker` checks the correct use of Move functions in the specification language. Those functions must be 'pure' and not depend on state or use certain other constructs. The checker is to be run as part of the regular compiler chain.
    - `spec_rewriter` rewrites specification expressions by converting used Move functions into specification functions, and doing other transformations to lift a Move expression into the specification language. This is only run by the prover itself.
- Inlining has been extended to deal with specification constructs.
- To support the inlining refactoring and the new processors, a new module `rewrite_target` is introduced which allows to collect functions and specification elements in a program in a unified fashion, rewriting them, and writing back to the environment. This new data structure has been inspired by the current design of the inliner and naturally extends it.
- A lot of ugliness has been ripped out of the model builder infrastructure (e.g. `TryImplAsSpec` mode is gone, as this is now handled by the `spec_rewriter`). More should come in step #2.
- Multiple test cases have been added.
- The prover driver has been adapted to use the new components.

* Fixing some unit tests

* Making hopefully all tests pass:

- Adding tuple support to the specification language as they are created by the inliner.
- Fixing an issue in memory usage calculation
- Adding a flag `--aptos` to the prover command line for easier debugging, avoiding the CLI.

* Disabling a condition for CI because of timeout.

* Rebasing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.