- 22 Jun, 2022 2 commits
-
- 10 Jun, 2022 1 commit
-
-
meskio authored
This commit adds two metrics: * gettor_request_total the total number of requests done to gettor, with the command, platform and locale of the original request. * gettor_link_response_total the total number of responses with links sent with platform and locale that was used. Closes: #51
-
- 08 Jun, 2022 1 commit
-
- 07 Jun, 2022 1 commit
-
-
meskio authored
To avoid sharing *requestHashKeys* between different goroutines let's use a worker to write to metrics so a single goroutine has access to it. This solves a crash on the telegram distributor.
-
- 16 May, 2022 4 commits
-
-
meskio authored
Is a function only used by the backend and not useful for distributors.
- 03 May, 2022 1 commit
-
-
meskio authored
Old telegram accounts have smaller IDs and new ones have bigger IDs. The logic was inversed here.
-
- 29 Apr, 2022 2 commits
-
-
meskio authored
The prometheus metrics can't be initalized multiple times. To make the tests work they are now a global variable.
-
meskio authored
After the transition from bridgedb to rdsys many 'telegram' bridges (old bridges) are comming from 'moat' or other distributors that could be blocked in certain locations. For old telegram accounts let's distribute bridges from both pools the dynamic 'new' bridges and the bridge authority 'old' bridges. Closes: #101
-
- 25 Apr, 2022 1 commit
-
- 20 Apr, 2022 1 commit
-
-
meskio authored
Closes: bridgedb#40043
-
- 04 Apr, 2022 1 commit
-
-
meskio authored
Oid is used to detect if a resource has changed, they don't get updated unless the oid has changed. Let's include any information that can change, like the distributio request, flags or oraddresses in the oid. Before that change rdsys was missing some bridge changes and not updating bridges until rdsys was restarted. Closes: #104
-
- 31 Mar, 2022 1 commit
-
- 25 Mar, 2022 2 commits
-
-
meskio authored
-
- 18 Mar, 2022 5 commits
-
-
meskio authored
-
meskio authored
-
meskio authored
The only consumer (for now) of Hashring.GetMany is the moat distributor, the distributors doesn't have the test status of the resources. Let's get bridges independently of their test status. AFAIK current rdsys implementation doesn't use the bridgestrap test status to decide wich bridges to distribute. I just created an issue to investigate that (#96).
-
meskio authored
The new version of go vet considers that an error.
-
- 17 Mar, 2022 2 commits
- 15 Mar, 2022 1 commit
-
-
meskio authored
It is used by moat distributor now.
-
- 08 Mar, 2022 4 commits
- 04 Mar, 2022 3 commits
- 23 Feb, 2022 4 commits
- 14 Feb, 2022 2 commits
-
-
meskio authored
Transport bridges include the IP address in the hash index, together with the fingerprint and the type. We can not address them directly just knowing the fingerprint. For now let's do a sequential search over the fingerprint, in the future this might become a problem and we might need to make it more efficient. Closes: #88
-
meskio authored
Not all the users of the Hashkey need to know how is it hashed and what is the polynomial being used.
-
- 31 Jan, 2022 1 commit
-
-
meskio authored
For it let's derivate resources.BridgeBase from core.ResourceBase so we have access to the BlockedIn function.
-