You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+20-1Lines changed: 20 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,25 @@ All notable changes to this project will be documented in this file.
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
and this project adheres to the versioning scheme outlined in the [README.md](README.md).
7
7
8
+
## [3.1.0.0.9]
9
+
10
+
### Added
11
+
12
+
- Added field `vm_error` to EventObserver transaction outputs
13
+
- Added new `ValidateRejectCode` values to the `/v3/block_proposal` endpoint
14
+
- Added `StateMachineUpdateContent::V1` to support a vector of `StacksTransaction` expected to be replayed in subsequent Stacks blocks
15
+
- Include a reason string in the transaction receipt when a transaction is rolled back due to a post-condition. This should help users in understanding what went wrong.
16
+
17
+
### Changed
18
+
19
+
- Reduce the default `block_rejection_timeout_steps` configuration so that miners will retry faster when blocks fail to reach 70% approved or 30% rejected.
20
+
- Added index for `next_ready_nakamoto_block()` which improves block processing performance.
21
+
- Added a new field, `parent_burn_block_hash`, to the payload that is included in the `/new_burn_block` event observer payload.
22
+
23
+
### Fixed
24
+
25
+
- Fix regression in mock-mining, allowing the mock miner to continue mining blocks throughout a tenure instead of failing after mining the tenure change block.
26
+
8
27
## [3.1.0.0.8]
9
28
10
29
### Added
@@ -19,7 +38,7 @@ and this project adheres to the versioning scheme outlined in the [README.md](RE
19
38
20
39
- When a miner times out waiting for signatures, it will re-propose the same block instead of building a new block ([#5877](https://github.com/stacks-network/stacks-core/pull/5877))
21
40
- Improve tenure downloader trace verbosity applying proper logging level depending on the tenure state ("debug" if unconfirmed, "info" otherwise) ([#5871](https://github.com/stacks-network/stacks-core/issues/5871))
22
-
- Remove warning log about missing UTXOs when a node is configured as `miner` with `mock_mining` mode enabled ([#5841](https://github.com/stacks-network/stacks-core/issues/5841))
41
+
- Remove warning log about missing UTXOs when a node is configured as `miner` with `mock_mining` mode enabled ([#5841](https://github.com/stacks-network/stacks-core/issues/5841))
23
42
- Deprecated the `wait_on_interim_blocks` option in the miner config file. This option is no longer needed, as the miner will always wait for interim blocks to be processed before mining a new block. To wait extra time in between blocks, use the `min_time_between_blocks_ms` option instead. ([#5979](https://github.com/stacks-network/stacks-core/pull/5979))
24
43
- Added `empty_mempool_sleep_ms` to the miner config file to control the time to wait in between mining attempts when the mempool is empty. If not set, the default sleep time is 2.5s. ([#5997](https://github.com/stacks-network/stacks-core/pull/5997))
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+18-4Lines changed: 18 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -361,17 +361,31 @@ A non-exhaustive list of examples of consensus-critical changes include:
361
361
362
362
- Every consensus-critical change needs an integration test to verify that the feature activates only when the hard fork activates.
363
363
364
-
PRs must include test coverage. However, if your PR includes large tests or tests which cannot run in parallel
364
+
-PRs must include test coverage. However, if your PR includes large tests or tests which cannot run in parallel
365
365
(which is the default operation of the `cargo test` command), these tests should be decorated with `#[ignore]`.
366
-
367
366
A test should be marked `#[ignore]` if:
368
367
369
-
1. It does not _always_ pass `cargo test` in a vanilla environment
368
+
1. It does not _always_ pass `cargo test` in a vanilla environment
370
369
(i.e., it does not need to run with `--test-threads 1`).
371
370
372
-
2. Or, it runs for over a minute via a normal `cargo test` execution
371
+
2. Or, it runs for over a minute via a normal `cargo test` execution
373
372
(the `cargo test` command will warn if this is not the case).
374
373
374
+
-**Integration tests need to be properly tagged** using [pinny-rs](https://github.com/BitcoinL2-Labs/pinny-rs/) crate. Tagging requires two fundamental steps:
375
+
1. Define allowed tags in the package `Cargo.toml` file (if needed).
376
+
2. Apply relevant tags to the tests, picking from the allowed set.
377
+
378
+
Then it will be possible to run tests with filtering based on the tags using `cargo test` and `cargo nextest` runner.
379
+
> For more information and examples on how tagging works, refer to the [pinny-rs](https://github.com/BitcoinL2-Labs/pinny-rs/) readme.
380
+
381
+
Below the tag set currently defined with related purpose:
0 commit comments