* update copyright for new files only if not matching existing patterns
* scripts too
* scripts all use Besu copyright
Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
---------
Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
* extra test for host and port leak
Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
---------
Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
* Move EOF to the Osaka Fork
* Ensure Osaka activations are working
* Remove CancunEOF and PragueEOF forks
* Move EOF tools to default to Osaka
Signed-off-by: Danno Ferrin <danno@numisight.com>
* remove eof tests that fail only because of fork
Signed-off-by: Danno Ferrin <danno@numisight.com>
* Restore CancunEOF
* Update unit tests to use "Cancun" as pre-eof fork
* Make PC in trace zeroed to start of code section 0
* Update extcall to consider precompiles warm
* Add stack checking to CALLF operation
Signed-off-by: Danno Ferrin <danno@numisight.com>
---------
Signed-off-by: Danno Ferrin <danno@numisight.com>
Co-authored-by: Sally MacFarlane <macfarla.github@gmail.com>
* keep track of blobs that are part of multiple transactions
Signed-off-by: stefan.pingel@consensys.net <stefan.pingel@consensys.net>
Signed-off-by: Stefan Pingel <16143240+pinges@users.noreply.github.com>
* don't try to import to an existing db
* deprecated task
* testutil subproject hit a sonar bug
---------
Signed-off-by: Justin Florentine <justin+github@florentine.us>
* Add support to sync to head instead of safe block during snapsync
Signed-off-by: Kevin King <kevin.king@consensys.net>
Signed-off-by: kingnhcomcast <114761064+kingnhcomcast@users.noreply.github.com>
Updates MetricsOptions to implement CLIOptions, and to contain its unstable options.
---------
Signed-off-by: Justin Florentine <justin+github@florentine.us>
* Changes to release workflow
- Workflow environment variable changed to RELEASE_VERSION instead of RELEASE_NAME to make it more meaningful
- Workflows draft-release and docker-promote previously trigger workflow container-verify. This can result in trigger is successful but actual verification workflow fails. This will not be reflected in the draft-release and docker-promote workflows. Container verify code is embedded in the draft-release and docker-promote workflows to avoid this confusion
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
* PR comment improvements
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
* Match the only tags starting with word latest for latest check
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
---------
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
Co-authored-by: Simon Dudley <simon.dudley@consensys.net>
Previously GitHub release will be created which triggers building and publishing the artifacts. Release engineers found workflow could fail after the GitHub release created. Community may subscribed to GitHub releases but if the workflow failed, artifacts for the release would not available.
Proposed solution requires release engineer to run a GitHub workflow manually by providing the Git tag which creates a draft GitHub release. During this workflow, release artifacts binary distribution, docker images (not latest), Artifactory jars created and published. Release engineer can update the release notes in draft release and publish the release. At the time when the release is published, release engineer is confident all the artifacts are ready. Upon publishing the release, another workflow is triggered to promote the release version of docker images to latest
Signed-off-by: Chaminda Divitotawela <cdivitotawela@gmail.com>
Co-authored-by: Simon Dudley <simon.dudley@consensys.net>
Sally MacFarlane
Simon Dudley
Justin Florentine
garyschulte
Fabio Di Fabio
Bhanu Pulluri
Stefan Pingel
Danno Ferrin
Preeti
Matt Whitehead
kingnhcomcast
Glory Agatevure
Suyash Nayan
Chaminda Divitotawela
Karim Taam
Gabriel-Trintinalia
Usman Saleem
daniellehrner
Wolmin
Jason Frame