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

Merge master into amm branch #3941

Merged
merged 20 commits into from
Sep 20, 2021
Merged

Merge master into amm branch #3941

merged 20 commits into from
Sep 20, 2021

Conversation

2opremio
Copy link
Contributor

@2opremio 2opremio commented Sep 20, 2021

I need this for #3931

bartekn and others added 19 commits September 9, 2021 21:19
The commit message of e011c91 was long enough to make `git log -1` command
enable scrolling. This was causing `test_verify_range_docker_image` job failures
because it got stuck at `git log -1` command waiting for user action.

I also noticed that the Golang version in the image does not match the one we
use in other places. I changed it to Go 1.17.
Golang time parser is not compatible with format rendered by the GNU date,
even though both claim to be RFC3339. This change replaces space separator
betwen date and time with "T" which will allow golang to parse it.
It also switches from `--utc` to `-u` that's supported by both GNU and BSD
date commands.
Format the VSCode tasks file.

When I open the stellar/go repo locally in the latest version of VSCode it displays a warning saying the file is "dirty". It appears the file is not formatted to how VSCode prefers it to be formatted. I don't really know what this file does or is for, but supposedly it was added because somebody uses it. This change resolves the warning.
…tellar#3912)

Using a generic `docker-compose down` command for stopping the Horizon
integration test containers causes every docker-compose container to
be brought down (including other containers, like the Horizon database
container which can be started using docker-compose).

This change makes sure we only destroy the containers brought up
during integration testing.
Update docker image build timestamp format
This commit adds a new `UpsertOffers` method (and generic `upsertRows`) and
modifies `OffersProcessor` to use it.

The performance of `OffersProcessor` degraded recently due to number of offers
in the network and batching updates should improve the performance of the
processor and ingestion overall.
…iod-to-challenge-reader

txnbuild: adds a 5 minute grace period to ReadChallengeTx MinTime constraint
* Run `apt-get` commands separately. Commands were previously joined by `&&`
operator which returned 0 code in case any of the commands failure.
* Hide hashes if they match.
* Add unstable repo.
Add test coverage for the Hint functions of the keypair.FromAddress and keypair.Full types.

Those functions aren't tested, and I'm iterating on the keypair code in stellar#3914 that involves changing the Hint functions, so I'd like test coverage present before hand.
Add tests to the crc16 package.

We don't have any. I was digging around in the code for some thing else and wanted to make a change to the crc logic and make sure I don't break it.
Move the `crc16` package to `strkey/internal/crc16`.

The `crc16` package implements a single form of crc16, the form specifically used by [strkeys](https://stellar.org/protocol/sep-23). It is only used by the `strkey` package and it is not really something that needs to be exported for others to use in other contexts.

The `crc16` package is not officially released in any particular package.
…nter to summary (stellar#3940)

Add a new metric `ProcessorsRunDurationSummary`/`processor_run_duration_seconds`
to replace existing `ProcessorsRunDuration`(`processor_run_duration_seconds_total`.
The old metric is now deprecated. The `ProcessorsRunDuration` is a counter.
While it allows estimating and comparing actual duration of processors it's
impossible to calculate average per ledger run duration because number of events
are not counted.
@2opremio 2opremio merged commit 588ce03 into stellar:amm Sep 20, 2021
@2opremio 2opremio deleted the merge-master branch September 20, 2021 14:31
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.

6 participants