status-im
/
status-go
mirror of https://github.com/status-im/status-go.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
5,190 Commits 587 Branches 904 Tags 247 MiB
Commit Graph

20 Commits

Author SHA1 Message Date
osmaczko 2ced83abb7
chore_: replace geth logger with zap logger (#5962) 
closes: #6002
 2024-10-28 20:54:17 +00:00
frank 38308d48f2
feat_: log on panic (#5849) 
* feat_: log error and stacktrace when panic in goroutine

* test_: add test TestSafeGo

* chore_: rename logAndCall to call

* chore_: rename SafeGo to Go

* chore_: make lint-fix

* chore_: use t.Cleanup

* chore_: Revert "chore_: use t.Cleanup"

This reverts commit 4eb420d179cc0e208e84c13cb941e6b3d1ed9819.

* chore_: Revert "chore_: make lint-fix"

This reverts commit fcc995f157e671a4229b47419c3a0e4004b5fdab.

* chore_: Revert "chore_: rename SafeGo to Go"

This reverts commit a6d73d6df583f313032d79aac62f66328039cb55.

* chore_: Revert "chore_: rename logAndCall to call"

This reverts commit 8fbe993bedb9fbba67349a44f151e2dd5e3bc4cc.

* chore_: Revert "test_: add test TestSafeGo"

This reverts commit a1fa91839f3960398980c6bf456e6462ec944819.

* chore_: Revert "feat_: log error and stacktrace when panic in goroutine"

This reverts commit f612dd828fa2ce410d0e806fe773ecbe3e86a68a.

* feat_: log error and stacktrace when panic in goroutine

* chore_: make lint-fix

* chore_: rename logAndCall to call

* chore_: renaming LogOnPanic

* chore_: update rest goroutine function calls

* chore_: make lint-fix
 2024-09-27 06:37:32 +08:00
Igor Sirotin e0eb737c51
fix_: enable tests to run with `-count` more than 1 (#5757) 
* fix(TestProfilingCPU)_: enable run with -count=2

* fix(TestProfilingMem)_: enable run with -count=2

* fix(zaputil)_: register encoder only once

* fix(timesource)_: global variables override in tests

* fix(TestClosingsqlDB)_: delete database from cache

* fix(postgres/helpers)_: drop connections before dropping database

* fix_: linter

* chore_: remove redundant condition
 2024-08-23 19:30:58 +00:00
osmaczko a584ab086a
Fix/timesource offline (#4309) 
* fix: add missing callback cleanup in timesource

fixes: "panic: sync: negative WaitGroup counter"

part of: status-im/status-desktop#12691

* fix: ensure timesource.GetCurrentTime is non-blocking

closes: status-im/status-desktop#12691
 2023-11-13 14:06:32 -05:00
frank 7ad5800a9a
use timesource(synced) to generate/validate server cert time (#4228) 
* use timesource(synced) to generate/validate server cert time

* add debug log

* bump version
 2023-11-07 09:51:15 +08:00
frank 864b0686d2
add more ntp servers (#3890) 
* add more ntp servers to improve stability

* bump version
 2023-08-16 10:06:03 +08:00
frank b81ad3fcac
Fix/stuck on keys saved (#3823) 
* fixed: getting stuck on the "Keys saved" randomly

* bump version
 2023-08-01 17:09:23 +08:00
frank 71ca35bf34
Feat/sync customization color (#3702) 
* sync customization color

* addressed feedback from @cammellos

* add param customizationColorClock to function generateOrImportAccount
 2023-07-18 21:35:06 +08:00
Andrea Maria Piana 4b0daeb47b Move services to status-node 
Move all the services to status-node, as some of them were there, some
of them were in the geth backend and scattered around.
 2021-07-20 10:57:38 +02:00
Pedro Pombeiro 6537cae606 Nimbus node support 2020-01-20 13:15:17 +01:00
Pedro Pombeiro c8a911ebd1 Use goimports instead of gofmt 2020-01-06 10:17:23 +01:00
Dmitry ae7faece88 Sanity validate ntp response 2018-06-08 19:10:29 +03:00
Dmitry Shulyak bc14e6faee Tolerate only one error during ntp sync 
Previously we were doing 5 concurrent requests, thus it was
safe to tolerate 2 errors. With 4 it doesn't make sense to use
only 2 responses, because even if 1 of them is skewed - we will set
incorrect time.
 2018-05-24 13:14:02 +03:00
Adrià Cidre 888ad10b26
[#969] Decrease NTP sync period after first success (#977) 2018-05-22 17:38:38 +02:00
Adam Babik 4dfbef3867
Fix p2p/Peers metric (#975) 
Do not use server.PeerCount() when getting peers right after receiving add/remove peer event as it does not contain updated info.
 2018-05-22 12:26:03 +02:00
Dmitry Shulyak ee60b7e727 Fix mid computation in timesource 
Additionally improved test suite
 2018-05-15 19:34:37 +03:00
Ivan Daniluk bd68fa15c9 Use different pool hostnames for NTP timesource (#939) (#952) 
* Use different pool hostnames for NTP timesource

* Make govet happy

* Add check for empty servers list
 2018-05-15 17:10:51 +03:00
Dmitry Shulyak 6c2a8ef1f9
Define shorter timeout for ntp calls (2s) and tolerate failures (#911) 
* Define shorter timeout for ntp calls (2s) and tolerate failures

* Use allowed failures instead of tolerated errorss
 2018-05-09 08:10:48 +03:00
Dmitry Shulyak 7aa508765e Set timesource from config (#915) 2018-05-08 13:38:54 +03:00
Dmitry Shulyak 707221954f
Make whisper tolerant to local time skews (#864) 
This change adds adds an ability to use different source of time for whisper:

when envelope is created it is used to set expiry
to track when envelope needs to be expired
This time is then used to check validity of the envelope when it is received. Currently If we receive an envelope that is sent from future - peer will get disconnected. If envelope that was received has an expiry less then now it will be simply dropped, if expiry is less than now + 10*2 seconds peer will get dropped.

So, it is clear that whisper depends on time. And any time we get a skew with peers that is > 20s reliability will be grealy reduced.

In this change another source of time for whisper will be used. This time source will use ntp servers from pool.ntp.org to compute offset. When whisper queries time - this offset will be added/substracted from current time.

Query is executed every 2 mins, queries 5 different servers, cut offs min and max and the computes mean value. pool.ntp.org is resolved to different servers and according to documentation you will rarely hit the same.

Closes: #687
 2018-05-04 11:23:38 +03:00