release/0.7.4-beta based on release/0.7.3-beta #563
Closed
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
This reverts commit 469dff6.
* Upgrade command * Lints * Working on upgrade command * More improvements - testing now * Rebasing on master * Download spinner is working properly * More UX improvements * Small fix * Small fix for Linux * Small change to upgrade, much cleaner now * Fixes for windows --------- Co-authored-by: Boppy <no-reply@boppygames.gg>
* Add OptIn serialization attribute * Run rust fmt
* core: Refactor commit encoding / decoding
Use `sats::{BufReader, BufWriter}` for decoding / encoding of `Commit`
and associated types. This makes `decode` fallible (which is quite
desirable, instead of panicking).
As the `DecodeError` from sats is fairly sparse, also add some context
about where exactly decoding failed.
Lastly, add some documentation and (property) tests.
Allows to remove custom strategies for the commit log types (in core), and may become useful for future property testing efforts.
Fixes #531. Instead of having two distinct metrics for commits and rollbacks, this patch replaces them with a single metric plus a boolean label representing whether the transaction was committed or rolled back.
Added multi column index usage to the rust-wasm-test module This also updates integration test. The number of lines in the output changes as there is 1 additional line corresponding to the new table.
* Added license files for the primitives crate * Fixed version number dependency thing --------- Co-authored-by: Tyler Cloutier <cloutiertyler@aol.com>
Co-authored-by: Noa <coolreader18@gmail.com>
This log line is currently occuring too often. Later changes will investigate the categorization of these "normal" errors, and more holistically evaluate our log levels.
Fixes #553. Before this change, we would use the same plan for both query and incremental eval. This is problematic for index joins. In particular, table sizes are drastically different under incremental eval. After this change, joins are reordered for incremental eval.
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.
Description of Changes
Please describe your change, mention any related tickets, and so on here.
API and ABI breaking changes
If this is an API or ABI breaking change, please apply the
corresponding GitHub label.
Expected complexity level and risk
How complicated do you think these changes are? Grade on a scale from 1 to 5,
where 1 is a trivial change, and 5 is a deep-reaching and complex change.
This complexity rating applies not only to the complexity apparent in the diff,
but also to its interactions with existing and future code.
If you answered more than a 2, explain what is complex about the PR,
and what other components it interacts with in potentially concerning ways.