gitmewai

The fallback to `3.3.3` for this mainnet node has been running for almost 6 days and the connections get stabilized. We have not switched back to `3.3.4` yet, so I...

We have just upgraded to `3.3.5` but the same behavior is observed as in `3.3.4`. We found that the node keeps syncing instead of import when running at `3.3.3`. ```...

We also encounter similar `runtime error` on `Staged Sync`: ``` Staged Sync err="runtime error: invalid memory address or nil pointer dereference, trace: [stageloop.go:129 panic.go:844 panic.go:220 signal_unix.go:818 fork_validator.go:279 fork_validator.go:216 stage_headers.go:673 collector.go:276...

Our issue is no longer observed under the latest version of erigon

@2opremio yes we are using `history-retention-count` with the value `483840` for roughly 28 days. It looks like the CPU/memory/IO are not constrained. Can we customize `stellar-horizon` process for the timeout...

Could we have the dependencies that are common in both debian and ubuntu (e.g. `libc++1-11`)? Or is there any specific requirement on `stellar-core` that should depend on `libc++1-10` only? On...

@MonsieurNicolas the version `19.3.0` still depends on `libc++1-10`. Is there any plan to fix this dependency on `libc++1-11` instead? Thanks

How about keeping the dependency on `libc++1-8`? Why has stellar-core changed to `libc++1-10` starting at `19.2.0`?

And when is the deadline on upgrading to `stellar-core` `19.2.0` or later release? @MonsieurNicolas Thanks