1. 05 Apr, 2023 1 commit
    • Marius van der Wijden's avatar
      core/txpool: disallow future churn by remote txs (#26907) · 230df98e
      Marius van der Wijden authored
      Prior to this change, it was possible that transactions are erroneously deemed as 'future' although they are in fact 'pending', causing them to be dropped due to 'future' not being allowed to replace 'pending'. 
      
      This change fixes that, by doing a more in-depth inspection of the queue. 
      230df98e
  2. 04 Apr, 2023 7 commits
  3. 03 Apr, 2023 8 commits
  4. 31 Mar, 2023 2 commits
  5. 30 Mar, 2023 7 commits
  6. 28 Mar, 2023 6 commits
  7. 27 Mar, 2023 3 commits
  8. 25 Mar, 2023 1 commit
  9. 24 Mar, 2023 2 commits
  10. 23 Mar, 2023 3 commits
    • aaronbuchwald's avatar
      eth/gasprice: change feehistory input type from int to uint64 (#26922) · b1acaf47
      aaronbuchwald authored
      Change input param type from int to uint64
      b1acaf47
    • Martin Holst Swende's avatar
      metrics/influxdb: use smaller dependency and reuse code between v1 and v2 reporters (#26963) · f6c3a534
      Martin Holst Swende authored
      This change switches to use the smaller influxdata/influxdb1-client package instead of depending on the whole infuxdb package. The new smaller client is very similar to the influxdb-v2 client, which made it possible to refactor the two reporters to reuse code a lot more. 
      f6c3a534
    • turboboost55's avatar
      metrics: add cpu counters (#26796) · 7dc10071
      turboboost55 authored
      This PR adds counter metrics for the CPU system and the Geth process.
      Currently the only metrics available for these items are gauges. Gauges are
      fine when the consumer scrapes metrics data at the same interval as Geth
      produces new values (every 3 seconds), but it is likely that most consumers
      will not scrape that often. Intervals of 10, 15, or maybe even 30 seconds
      are probably more common.
      
      So the problem is, how does the consumer estimate what the CPU was doing in
      between scrapes. With a counter, it's easy ... you just subtract two
      successive values and divide by the time to get a nice, accurate average.
      But with a gauge, you can't do that. A gauge reading is an instantaneous
      picture of what was happening at that moment, but it gives you no idea
      about what was going on between scrapes. Taking an average of values is
      meaningless.
      7dc10071