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

fix(signal): trim down tested endpoints #1421

Merged
merged 1 commit into from
Dec 1, 2023
Merged

fix(signal): trim down tested endpoints #1421

merged 1 commit into from
Dec 1, 2023

Conversation

bassosimone
Copy link
Contributor

@bassosimone bassosimone commented Dec 1, 2023

Checklist

Description

This diff trims down the endpoints tested by signal to avoid the possibility of future churn.

@bassosimone bassosimone requested a review from hellais as a code owner December 1, 2023 10:21
bassosimone added a commit to ooni/spec that referenced this pull request Dec 1, 2023
## Checklist

- [x] I have read the [contribution
guidelines](https://github.com/ooni/spec/blob/master/CONTRIBUTING.md)
- [x] reference issue for this pull request:
ooni/probe#2636
- [x] related ooni/probe-cli pull request:
ooni/probe-cli#1421
- [x] If I changed a spec, I also bumped its version number and/or date

<!-- Location of the issue tracker: https://github.com/ooni/probe -->

## Description

We trim down signal endpoints to increase robustness against endpoints
churn.
@bassosimone bassosimone merged commit a0d4b5c into master Dec 1, 2023
10 checks passed
@bassosimone bassosimone deleted the issue/2636 branch December 1, 2023 10:31
bassosimone added a commit that referenced this pull request Dec 1, 2023
## Checklist

- [x] I have read the [contribution
guidelines](https://github.com/ooni/probe-cli/blob/master/CONTRIBUTING.md)
- [x] reference issue for this pull request:
ooni/probe#2636
- [x] if you changed anything related to how experiments work and you
need to reflect these changes in the ooni/spec repository, please link
to the related ooni/spec pull request:
ooni/spec#282
- [x] if you changed code inside an experiment, make sure you bump its
version number

<!-- Reminder: Location of the issue tracker:
https://github.com/ooni/probe -->

## Description

This diff trims down the endpoints tested by signal to avoid the
possibility of future churn.
Murphy-OrangeMud pushed a commit to Murphy-OrangeMud/probe-cli that referenced this pull request Feb 13, 2024
## Checklist

- [x] I have read the [contribution
guidelines](https://github.com/ooni/probe-cli/blob/master/CONTRIBUTING.md)
- [x] reference issue for this pull request:
ooni/probe#2636
- [x] if you changed anything related to how experiments work and you
need to reflect these changes in the ooni/spec repository, please link
to the related ooni/spec pull request:
ooni/spec#282
- [x] if you changed code inside an experiment, make sure you bump its
version number

<!-- Reminder: Location of the issue tracker:
https://github.com/ooni/probe -->

## Description

This diff trims down the endpoints tested by signal to avoid the
possibility of future churn.
bassosimone added a commit to ooni/backend that referenced this pull request Mar 22, 2024
The ooni/probe-cli#1421 PR trimmed the endpoints and bumped signal's version to v0.2.5.

So we need to ignore versions of signal lower than v0.2.5.

I am wondering whether we should also use a time window because otherwise what happens when we reprocess measurements. If my analysis is correct, then we have an additional issue that there's another check in this codepath that seems to mark signal measurements as failed without any temporal constraints. This would also cause reprocessing to cause downstream issues.

Part of ooni/probe#2636
hellais added a commit to ooni/backend that referenced this pull request Mar 25, 2024
* fix: mark signal v0.2.4 as failed

The ooni/probe-cli#1421 PR trimmed the endpoints and bumped signal's version to v0.2.5.

So we need to ignore versions of signal lower than v0.2.5.

I am wondering whether we should also use a time window because otherwise what happens when we reprocess measurements. If my analysis is correct, then we have an additional issue that there's another check in this codepath that seems to mark signal measurements as failed without any temporal constraints. This would also cause reprocessing to cause downstream issues.

Part of ooni/probe#2636

* Add more specific constraints to the signal scoring logic

* Bump changelog entry

Fix changelog entry to avoid conflict with: https://github.com/ooni/backend/pull/793/files

---------

Co-authored-by: Arturo Filastò <arturo@filasto.net>
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.

1 participant