[BUG] ICheckpointMananger is misspelled in Service Fabric Processor
See original GitHub issueDescribe the bug
I genuinely am not sure whether or not this is actually a bug per se, but it did just cause me several minutes of confusion and frustration. I’m also not sure if it’s fixable without breaking changes.
The ICheckpointMananger
interface is misspelled. There is an extra n
: ICheckpointMananger
Environment:
- Name and version of the Library package used: Microsoft.Azure.EventHubs.ServiceFabricProcessor, v0.5.4.0
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
c# - Service fabric error
Service fabric has a hook ( The commslistener) which tells it the service is ready , if this is not set ( or...
Read more >[BUG] -Service Fabric SDK dont install in MAC M1 ...
Describe the bug. The SDK doesn't install with vs studio or chocolatey when I use a virtual machine in mac book with an...
Read more >Service Fabric Worker Application does not get updated ...
Service Fabric Worker Application does not get updated even when version is incremented and deployed through Visual Studio - Developer Community.
Read more >Troubleshoot with system health reports - Azure Service ...
Describes the health reports sent by Azure Service Fabric components and their usage for troubleshooting cluster or application problems.
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 FreeTop 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
Top GitHub Comments
Argh. At least it’s still preview, so we can fix that.
The Microsoft.Azure.EventHubs.ServiceFabricProcessor package is in preview and there are no plans for a stable release. This package will soon be deprecated and therefore we won’t be taking any changes.