-
Notifications
You must be signed in to change notification settings - Fork 4
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
GitHub ci #2
Open
shichengripple001
wants to merge
76
commits into
develop
Choose a base branch
from
github-ci
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
GitHub ci #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Increase the visibility of each type's API. * No functional changes.
* These are meant to be used by detail::STVar only and are otherwise error-prone to call.
This is a refactor aimed at cleaning up and simplifying the existing job queue. As of now, all jobs are cancelled at the same time and in the same way, so this commit removes the per-job cancellation token. If the need for such support is demonstrated, support can be re-added. * Revise documentation for ClosureCounter and Workers. * Simplify code, removing unnecessary function arguments and deduplicating expressions * Restructure job handlers to no longer need to pass a job's handle to the job.
Orphaned nodestore directories should only be deleted if the proper nodestore directories are confirmed to exist.
If fast loading is enabled but the last persisted ledger is not entirely on disk, the server would fail to start without manual intervention by the server operator. This commit allows the server to detect this scenario and attempt to automatically recover.
respresent -> represent
* Remove Application & Database dependency in PerfLog. Replace it with a callback passed into the constructor. * Fixes the circular dependency between ripple/nodestore and ripple/basics
* Update boost version. * Use latest macOS image. * Credit to @donovanhide in #4025 for starting this ball rolling, and inspiring a boost update.
* Allow clio to ask for object successors and predecessors from rippled * Add lower_bound and last_below to SHAMap
* Include a warning message when a newer version is found
* Split Windows prereq jobs to decrease change of timeout. * Generalize "control" commit message keywords from "travis" to "ci". * Tune time and numbar process params.
* Will save significant space and potentially download time for CI caches, and for building multiple configs in a single repo.
* Split that function into a separate file so it can be used in other contexts.
* telLOCAL_ERROR is not new, but it is not used anywhere in the transaction engine, unlike temINVALID. This will make those types of errors distinct and easier to diagnose.
* This intended to future-proof in two ways. 1) so we don't lose the institutional knowledge why we keep using VS2017. 2) if/when the issue is resolved, we'll know it.
* VS19 debug builds DO NOT RUN TESTS. Known issue with those builds, but if it gets fixed, I want to be able to see those tests succeed.
* Simplifies the validation * Note that it will be backward compatible with the "VS 2017 Win64" generator format
* Dump vc environment if parsing fails
shichengripple001
force-pushed
the
github-ci
branch
11 times, most recently
from
March 28, 2022 01:21
f9d4cb6
to
0b118f6
Compare
docker login with secret
shichengripple001
force-pushed
the
github-ci
branch
from
March 28, 2022 01:22
0b118f6
to
1d7880e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
High Level Overview of Change
Context of Change
Type of Change