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.
Suggestion for retry
See original GitHub issueI suggest to resync the heading position every x tries (to be passed as parameter).
I suspect that the disks presenting bad sectors are not read because of the heading position rather than the floppy itself.
BTW the default PC implementation does this: move back the head to zero, than back to the position and retries.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Enhancement suggestions for "Retries"
Here are a few enhancement suggestions for "Retries": (1) Allow the ability to configure retries directly on a step without having to add...
Read more >Good suggestion to implement a retry logic of a single step in ...
If you only want to retry on a specific call, then you should wrap only that specific call in retry logic. I will...
Read more >Suggest retry mechanism in Typescript - CodeChef Discuss
I am implementing a retry mechanism in a node.js application as follows: async addComments(id: string, comments: string[]): Promise<any> ...
Read more >Naming/Javadoc suggestions for Retry.java #2553 - GitHub
Documentation Issue I think that both the naming and the javadoc regarding number of retries in Retry.java could use some changes for ...
Read more >Suggestion: Retry Quiz Questions (Example) - Treehouse
Often times when I am taking quizzes I will get a question wrong, but will be able still pass a quiz by hitting...
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
You can use the latest successful CI build under the repository’s Actions tab on its Github page. Click Actions, then click top build, then artifact link is at the bottom of the page.
What’s a good default? Perhaps three reads then reseek, three times total?