-
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
[RELEASE] 0.6.0 #356
base: master
Are you sure you want to change the base?
[RELEASE] 0.6.0 #356
Commits on Jul 23, 2024
-
OCT-1516: Improve processing in an asynchronous way (#353)
…sing ## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for f218eed - Browse repository at this point
Copy the full SHA f218eedView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4af8d30 - Browse repository at this point
Copy the full SHA 4af8d30View commit details -
Configuration menu - View commit details
-
Copy full SHA for 77fb77f - Browse repository at this point
Copy the full SHA 77fb77fView commit details
Commits on Jul 24, 2024
-
OCT-1768 & OCT-1767: Change the verifier logic for E4 (#344)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc). --------- Co-authored-by: adam-gf <adam@golem.foundation>
Configuration menu - View commit details
-
Copy full SHA for 77741ec - Browse repository at this point
Copy the full SHA 77741ecView commit details -
Configuration menu - View commit details
-
Copy full SHA for e53d34e - Browse repository at this point
Copy the full SHA e53d34eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9068957 - Browse repository at this point
Copy the full SHA 9068957View commit details
Commits on Jul 26, 2024
-
sanity tests for info endpoints
Signed-off-by: Mateusz Stolecki <mateusz@golem.foundation>
Configuration menu - View commit details
-
Copy full SHA for 917c6da - Browse repository at this point
Copy the full SHA 917c6daView commit details -
fix readme command to run one api test
Signed-off-by: Mateusz Stolecki <mateusz@golem.foundation>
Configuration menu - View commit details
-
Copy full SHA for 21e6d93 - Browse repository at this point
Copy the full SHA 21e6d93View commit details -
one left out method not updated for sync status changes
Signed-off-by: Mateusz Stolecki <mateusz@golem.foundation>
Configuration menu - View commit details
-
Copy full SHA for ec62975 - Browse repository at this point
Copy the full SHA ec62975View commit details -
Signed-off-by: Mateusz Stolecki <mateusz@golem.foundation>
Configuration menu - View commit details
-
Copy full SHA for bef3608 - Browse repository at this point
Copy the full SHA bef3608View commit details -
Configuration menu - View commit details
-
Copy full SHA for d8cb45e - Browse repository at this point
Copy the full SHA d8cb45eView commit details
Commits on Jul 28, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4f60b14 - Browse repository at this point
Copy the full SHA 4f60b14View commit details
Commits on Jul 29, 2024
-
multideployer: better handling of errors
multideployer: * non-zero exit on subcommand => http 500 * print stdout and stderr in logs * return stdout and stderr as a text accompanying the http 500 conftest: * if multideployer crashes, log the details
Configuration menu - View commit details
-
Copy full SHA for 23823b0 - Browse repository at this point
Copy the full SHA 23823b0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 48c02ea - Browse repository at this point
Copy the full SHA 48c02eaView commit details -
Configuration menu - View commit details
-
Copy full SHA for dcbb945 - Browse repository at this point
Copy the full SHA dcbb945View commit details -
OCT-1596 Implement automated sanity tests for Info API section (#345)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 5219678 - Browse repository at this point
Copy the full SHA 5219678View commit details
Commits on Jul 30, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 69aad73 - Browse repository at this point
Copy the full SHA 69aad73View commit details
Commits on Jul 31, 2024
-
OCT-1750: introduce redis cache (#355)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 306859e - Browse repository at this point
Copy the full SHA 306859eView commit details
Commits on Aug 1, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 0c40459 - Browse repository at this point
Copy the full SHA 0c40459View commit details -
Use local IPFS gateway for test envs (#347)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 44e57fa - Browse repository at this point
Copy the full SHA 44e57faView commit details
Commits on Aug 6, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 0dd53fc - Browse repository at this point
Copy the full SHA 0dd53fcView commit details
Commits on Aug 7, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 00d8957 - Browse repository at this point
Copy the full SHA 00d8957View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3ecfda0 - Browse repository at this point
Copy the full SHA 3ecfda0View commit details -
Revert "OCT-1842: Reduce sentry events flood"
This reverts commit 6bf0225.
Configuration menu - View commit details
-
Copy full SHA for 9fcf0a4 - Browse repository at this point
Copy the full SHA 9fcf0a4View commit details -
Configuration menu - View commit details
-
Copy full SHA for c2bfade - Browse repository at this point
Copy the full SHA c2bfadeView commit details -
Use local IPFS gateway for test envs (#381)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for e583504 - Browse repository at this point
Copy the full SHA e583504View commit details -
OCT-1730: Improvements for the epoch verifier (#368)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc). --------- Co-authored-by: Andrzej Ziółek <a.j.ziolek@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 43ac141 - Browse repository at this point
Copy the full SHA 43ac141View commit details -
basic api tests for history endpoint
Signed-off-by: Mateusz Stolecki <mateusz@golem.foundation> Signed-off-by: Mateusz Stolecki <mateusz@golem.foundation>
Configuration menu - View commit details
-
Copy full SHA for 329d8d1 - Browse repository at this point
Copy the full SHA 329d8d1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0c207ba - Browse repository at this point
Copy the full SHA 0c207baView commit details
Commits on Aug 8, 2024
-
OCT-1597 Implement automated sanity tests for History endpoint (#369)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 381c857 - Browse repository at this point
Copy the full SHA 381c857View commit details -
Reapply "OCT-1842: Reduce sentry events flood"
This reverts commit 9fcf0a4.
Configuration menu - View commit details
-
Copy full SHA for e77fb43 - Browse repository at this point
Copy the full SHA e77fb43View commit details
Commits on Aug 9, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 2ee40ee - Browse repository at this point
Copy the full SHA 2ee40eeView commit details -
FIX-OCT-1839: Set created_at field (#376)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 6ba54d3 - Browse repository at this point
Copy the full SHA 6ba54d3View commit details
Commits on Aug 14, 2024
-
[SYNC] Master to develop (#387)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc). --------- Co-authored-by: Jakub Mikołajczyk <j.mikolajczyk96@gmail.com> Co-authored-by: Housekeeper Bot <birnam@wildland.io> Co-authored-by: Andrzej Ziółek <a.j.ziolek@gmail.com> Co-authored-by: Jakub Mikołajczyk <38243788+jmikolajczyk@users.noreply.github.com> Co-authored-by: Pawel Peregud <paulperegud@protonmail.ch>
Configuration menu - View commit details
-
Copy full SHA for 778f0f0 - Browse repository at this point
Copy the full SHA 778f0f0View commit details
Commits on Aug 19, 2024
-
OCT-1842: Reduce sentry events flood (#375)
## Description Since our app is structured in a way that exceptions are expected, then caught and displayed as valid http responses, sentry must not report those exceptions as issues. It should thus not report "handled" exceptions. ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 00de2a1 - Browse repository at this point
Copy the full SHA 00de2a1View commit details
Commits on Aug 21, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 112763e - Browse repository at this point
Copy the full SHA 112763eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 656645f - Browse repository at this point
Copy the full SHA 656645fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 430d028 - Browse repository at this point
Copy the full SHA 430d028View commit details
Commits on Aug 22, 2024
-
Configuration menu - View commit details
-
Copy full SHA for f30d798 - Browse repository at this point
Copy the full SHA f30d798View commit details
Commits on Aug 23, 2024
-
Configuration menu - View commit details
-
Copy full SHA for a38af09 - Browse repository at this point
Copy the full SHA a38af09View commit details
Commits on Aug 24, 2024
-
OCT-1860: Cover /delegate with API Tests (#391)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for adb9c3a - Browse repository at this point
Copy the full SHA adb9c3aView commit details
Commits on Aug 25, 2024
-
OCT-1863: Cover UQ with API Tests (#390)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for d28c587 - Browse repository at this point
Copy the full SHA d28c587View commit details -
Configuration menu - View commit details
-
Copy full SHA for 66314fa - Browse repository at this point
Copy the full SHA 66314faView commit details -
Configuration menu - View commit details
-
Copy full SHA for dba3c31 - Browse repository at this point
Copy the full SHA dba3c31View commit details
Commits on Aug 27, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 9cf28d9 - Browse repository at this point
Copy the full SHA 9cf28d9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 25d0207 - Browse repository at this point
Copy the full SHA 25d0207View commit details -
Configuration menu - View commit details
-
Copy full SHA for d4bc66d - Browse repository at this point
Copy the full SHA d4bc66dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 063818f - Browse repository at this point
Copy the full SHA 063818fView commit details -
OCT-1864: Add an exception for invalid user address (#389)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for e649fd9 - Browse repository at this point
Copy the full SHA e649fd9View commit details
Commits on Aug 28, 2024
-
OCT-1862: Cover /check in delegation with API Tests (#392)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 66f5304 - Browse repository at this point
Copy the full SHA 66f5304View commit details -
Configuration menu - View commit details
-
Copy full SHA for cbe3583 - Browse repository at this point
Copy the full SHA cbe3583View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2b0fa2a - Browse repository at this point
Copy the full SHA 2b0fa2aView commit details -
Configuration menu - View commit details
-
Copy full SHA for cb11a15 - Browse repository at this point
Copy the full SHA cb11a15View commit details -
Configuration menu - View commit details
-
Copy full SHA for a12b50e - Browse repository at this point
Copy the full SHA a12b50eView commit details -
Configuration menu - View commit details
-
Copy full SHA for a65a0f3 - Browse repository at this point
Copy the full SHA a65a0f3View commit details
Commits on Aug 29, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 077ed90 - Browse repository at this point
Copy the full SHA 077ed90View commit details
Commits on Aug 30, 2024
-
Configuration menu - View commit details
-
Copy full SHA for ce20c51 - Browse repository at this point
Copy the full SHA ce20c51View commit details
Commits on Sep 2, 2024
-
OCT-1837 & OCT-1838: Upgrade metrics pie chart for unused MR (#383)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc). --------- Co-authored-by: Andrzej Ziółek <a.j.ziolek@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 44a889f - Browse repository at this point
Copy the full SHA 44a889fView commit details -
OCT-1861: Cover /recalculate with API Tests (#394)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 143eabd - Browse repository at this point
Copy the full SHA 143eabdView commit details -
OCT-1714 API Tests: Implement tests for epoch4 with capped QF (alloca…
…tions) (#395) ## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc). --------- Co-authored-by: Michał Kluczek <michal@wildland.io>
Configuration menu - View commit details
-
Copy full SHA for bceb433 - Browse repository at this point
Copy the full SHA bceb433View commit details
Commits on Sep 4, 2024
-
Configuration menu - View commit details
-
Copy full SHA for c3354b6 - Browse repository at this point
Copy the full SHA c3354b6View commit details
Commits on Sep 9, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 5eeab89 - Browse repository at this point
Copy the full SHA 5eeab89View commit details -
Configuration menu - View commit details
-
Copy full SHA for ac5bf51 - Browse repository at this point
Copy the full SHA ac5bf51View commit details
Commits on Sep 10, 2024
-
Configuration menu - View commit details
-
Copy full SHA for ba0958a - Browse repository at this point
Copy the full SHA ba0958aView commit details
Commits on Sep 16, 2024
-
OCT-1598 rewards api sanity test (#407)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 277d02a - Browse repository at this point
Copy the full SHA 277d02aView commit details
Commits on Sep 18, 2024
-
OCT-1938: Propose a changelog (#414)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 785368a - Browse repository at this point
Copy the full SHA 785368aView commit details -
OCT-1843: Refetch when getting 404 error (#411)
## Description ## Definition of Done 1. [ ] Acceptance criteria are met. 2. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 3. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 4. [ ] Unit tests are added unless there is a reason to omit them. 5. [ ] Automated tests are added when required. 6. [ ] The code is merged. 7. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 8. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 16ac5ae - Browse repository at this point
Copy the full SHA 16ac5aeView commit details
Commits on Sep 24, 2024
-
OCT-1943: Add project searching on the server side (#419)
## Description ## Definition of Done 1. [ ] If required, the desciption of your change is added to the [QA changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281) 2. [ ] Acceptance criteria are met. 3. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 4. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 5. [ ] Unit tests are added unless there is a reason to omit them. 6. [ ] Automated tests are added when required. 7. [ ] The code is merged. 8. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 9. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 67ee7b8 - Browse repository at this point
Copy the full SHA 67ee7b8View commit details
Commits on Sep 26, 2024
-
OCT-1930: Change the UQ leverage (#425)
## Description ## Definition of Done 1. [ ] If required, the desciption of your change is added to the [QA changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281) 2. [ ] Acceptance criteria are met. 3. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 4. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 5. [ ] Unit tests are added unless there is a reason to omit them. 6. [ ] Automated tests are added when required. 7. [ ] The code is merged. 8. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 9. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for cfb3ce4 - Browse repository at this point
Copy the full SHA cfb3ce4View commit details -
OCT-1939: Implement a timeout list (#422)
## Description ## Definition of Done 1. [ ] If required, the desciption of your change is added to the [QA changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281) 2. [ ] Acceptance criteria are met. 3. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 4. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 5. [ ] Unit tests are added unless there is a reason to omit them. 6. [ ] Automated tests are added when required. 7. [ ] The code is merged. 8. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 9. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 452e25d - Browse repository at this point
Copy the full SHA 452e25dView commit details -
OCT-1867: Add a rewards rate value for the server (#421)
## Description ## Definition of Done 1. [ ] If required, the desciption of your change is added to the [QA changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281) 2. [ ] Acceptance criteria are met. 3. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 4. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 5. [ ] Unit tests are added unless there is a reason to omit them. 6. [ ] Automated tests are added when required. 7. [ ] The code is merged. 8. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 9. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for db20a2a - Browse repository at this point
Copy the full SHA db20a2aView commit details
Commits on Sep 27, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 6293397 - Browse repository at this point
Copy the full SHA 6293397View commit details -
Gitcoin Passport: for GTC staking stamps use weight of zero
Provider strings fetched from here: https://github.com/passportxyz/passport/blob/main/types/src/index.d.ts#L374 Weights taken from https://passport.gitcoin.co/#/octant/dashboard page.
Configuration menu - View commit details
-
Copy full SHA for 2dbab5d - Browse repository at this point
Copy the full SHA 2dbab5dView commit details -
OCT-1992: Extend searching functionality for multiple params (#439)
## Description ## Definition of Done 1. [ ] If required, the desciption of your change is added to the [QA changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281) 2. [ ] Acceptance criteria are met. 3. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 4. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 5. [ ] Unit tests are added unless there is a reason to omit them. 6. [ ] Automated tests are added when required. 7. [ ] The code is merged. 8. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 9. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for ab945c3 - Browse repository at this point
Copy the full SHA ab945c3View commit details -
OCT-1944 Lower GP score giving the UQ score multiplier 1: server (#437)
## Description ## Definition of Done 1. [ ] If required, the desciption of your change is added to the [QA changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281) 2. [ ] Acceptance criteria are met. 3. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 4. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 5. [ ] Unit tests are added unless there is a reason to omit them. 6. [ ] Automated tests are added when required. 7. [ ] The code is merged. 8. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 9. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for bb0acd2 - Browse repository at this point
Copy the full SHA bb0acd2View commit details
Commits on Sep 30, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 4b825b5 - Browse repository at this point
Copy the full SHA 4b825b5View commit details -
OCT-1923 Assign zero score to GTC staking stamps (#443)
## Description ## Definition of Done 1. [ ] If required, the desciption of your change is added to the [QA changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281) 2. [x] Acceptance criteria are met. 3. [x] PR is manually tested before the merge by developer(s). - [x] Happy path is manually checked. 4. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 5. [x] Unit tests are added unless there is a reason to omit them. 6. [x] Automated tests are added when required. 7. [ ] The code is merged. 8. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 9. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 7cb4cbe - Browse repository at this point
Copy the full SHA 7cb4cbeView commit details
Commits on Oct 1, 2024
-
OCT-1939: Fix improper way of handling an antisybil_status field (#452)
## Description ## Definition of Done 1. [ ] If required, the desciption of your change is added to the [QA changelog](https://www.notion.so/octantapp/Changelog-for-the-QA-d96fa3b411cf488bb1d8d9a598d88281) 2. [ ] Acceptance criteria are met. 3. [ ] PR is manually tested before the merge by developer(s). - [ ] Happy path is manually checked. 4. [ ] PR is manually tested by QA when their assistance is required (1). - [ ] Octant Areas & Test Cases are checked for impact and updated if required (2). 5. [ ] Unit tests are added unless there is a reason to omit them. 6. [ ] Automated tests are added when required. 7. [ ] The code is merged. 8. [ ] Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files). - [ ] BE: Swagger documentation is updated. 9. [ ] When required by QA: - [ ] Deployed to the relevant environment. - [ ] Passed system tests. --- (1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required. (2) [Octant Areas & Test Cases](https://docs.google.com/spreadsheets/d/1cRe6dxuKJV3a4ZskAwWEPvrFkQm6rEfyUCYwLTYw_Cc).
Configuration menu - View commit details
-
Copy full SHA for 6c440cf - Browse repository at this point
Copy the full SHA 6c440cfView commit details