Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Breaking change: previous autoPingSize
See original GitHub issueOur microservices were connecting with option {autoPingSize:4}. I believe this was the default.
All of our microservices broke with the latest autobahn.
Connection failed: AssertionError:
Changing our options to the new default of 12 fixed it, but it took us awhile to track this down.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
How to Catch Breaking Changes Before They Happen
Preventing breaking changes is important, and it should absolutely be a part of your governance model when it comes to APIs.
Read more >What Are Breaking Changes and How Do You Avoid Them?
As the name might suggest, a breaking change to an API is any change that can break a client's application. Usually, breaking changes...
Read more >Breaking Changes
A breaking change is any change which modifies the public interface to a module in such a way that causes any consuming modules...
Read more >Denote API breaking changes · Issue #41 · olivierlacan/keep-a ...
We have a Changed section but some changes may be breaking and others not. This information can be encoded in the release version...
Read more >A definitive guide to API-breaking changes in .NET
Binary-level break - an API change that results in client assemblies compiled against older version of the API potentially not loading with the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
yes, true. and would have been easy to do as you describe. so yes, will take more care next time
That’s great… but backwards compatibility would have been great too 😃. (If autoPingSize <12, log a message w/ a github issue URL describing why you should update it to get the new feature!)