Log for CHANGELOG.md

• Prepare for v1.0.0 💬 by Caio 6 months ago

  Experience tells me that as soon as I release this something will pop up
  so here I am, goading the Fates.
  
  The API hasn't changed in a long while, so it isn't much of a concern.
  Not every dependency is stable, but they rarely change. A paced major
  version bump simply to update deps is perfectly fine
  

• Ensure wrapped errors are Sync by Caio 8 months ago
• Prepare for v0.19.0 release by Caio a year ago
• Prepare for v0.18.0 release by Caio 2 years ago
• Add parameter to skip broadcasts on apply_many by Caio 2 years ago
• Add new, experimental, feture gated notifications 💬 by Caio 2 years ago

  This patch introduces Notification::{DataSent,DataReceived} which
  allows peeking into the interaction between peers without having
  to deal with traces
  

• Notification enum now holds references 💬 by Caio 2 years ago

  I want to extend notifications without worrying too much about causing
  allocs for (potentially) unused data
  
  Not particularly nice, but I think this is still a better dev experience
  than slapping a bunch of "on_$something" methods in the Runtime trait
  with a default no-op impl
  

• Update docs wrt std feature / core::error::Error by Caio 2 years ago
• Prepare for v0.17.2 release by Caio 2 years ago
• Don't add custom broadcasts to TurnUndead messages by Caio 2 years ago
• Prepare for v0.17.1 release by Caio 2 years ago
• Ignore messages from known old identities 💬 by Caio 2 years ago

  In a scenario where traffic is buffered and/or replayed this could
  lead to noisy cluster behaviour
  

• Don't request indirect ping to same addr 💬 by Caio 2 years ago

  If a member changed its identity while being probed there was
  a chance foca would try to ask the new identity to ping
  the old one on its behalf
  

• Prepare for v0.17.0 release by Caio 2 years ago
• Introduces Config::periodic_announce_to_down_members 💬 by Caio 2 years ago

  New feature to (try to) recorver from network partitions
  

• More notes to the Changelog. It's a big release by Caio 2 years ago
• Update BroadcastHandler docs by Caio 2 years ago
• Update changelog by Caio 2 years ago
• Prepare for v0.16.0 release by Caio 2 years ago
• Prepare for v0.15.0 release by Caio 2 years ago
• Prepare for v0.14.0 release by Caio 2 years ago
• Only emit DEBUG and TRACE traces 💬 by Caio 2 years ago

  I'll stick to a simple methodology here:
  
  - this is a library, so never emit traces higher than DEBUG
  - DEBUG is used for high-level protocol visibility
  - TRACE is used for exposing the guts
  

• Prepare for v0.13.0 release by Caio 2 years ago
• Prepare for v0.12.0 release 💬 by Caio 2 years ago

  Resolves #25
  

• Prepare for v0.11.0 release by Caio 3 years ago
• Prepare for v0.10.1 release by Caio 3 years ago
• Prepare for v0.10.0 release by Caio 3 years ago
• higher level traces now include useful information 💬 by Caio 3 years ago

  previously, running with RUST_LOG=info or higher would lead to unhelpful
  traces with just a message and no clue on what actually caused it
  
  this patch ensures useful spans are created wherever necessary and
  removes a bunch of instrumentation code that became redundant after the
  fact
  

• don't choose an identity with same prefix for indirect probe 💬 by Caio 3 years ago

  there was a small chance that foca would pick a target for the
  indirect probe cycle that had the same prefix as the identity
  being probed
  
  when that happened in the right order (the newest being chosen
  for the indirect probe while the old was still considered alive),
  the target would end up crafting packets destined to itself,
  leading to a head-scrathing error in the logs
  
  very unlikely to happen when the network is decent; even less
  likely for large clusters
  

• Prepare for v0.9.0 release 💬 by Caio 3 years ago

  Resolves #19