Sonarr not fully accepting SABnzbd develop version

[Snuser]

Sonarr version (exact version): 3.0.6.1342
OS: Windows 10
Debug logs:

2022-01-07 22:21:32.1|Trace|HttpClient|Res: [GET] http://localhost:9999/api?mode=version&apikey=(removed)&output=json: 200.OK (2006 ms)
2022-01-07 22:21:32.1|Trace|HttpClient|Response content (22 bytes): {“version”: “develop”}
2022-01-07 22:21:32.2|Trace|SonarrErrorPipeline|Handling Exception
2022-01-07 22:21:32.2|Warn|SonarrErrorPipeline|Invalid request Validation failed:
– Version: Sabnzbd develop version, assuming version 1.1.0 or higher.
2022-01-07 22:21:32.2|Trace|Http|Res: 112 [POST] /api/v3/downloadclient/test: 400.BadRequest (2124 ms)
2022-01-07 22:21:32.2|Debug|Api|[POST] /api/v3/downloadclient/test: 400.BadRequest (2124 ms)

Description of issue:
I’m running the SABnzbd develop version from Git. Sonarr does not seem to fully accept “develop” as version. When it is using it normally it will not complain but if SABnzbd has been down for a while and put on a timeout then I can’t use the test to make it work. It will not accept that it’s up again and it will wait for the timeout before it starts using it again.

[bakerboy448]

This is not a Sonarr issue.

SAB’s beta had a breaking API change

also you should not be running beta download clients with stable versions of Sonarr…that typically is never a good combination.

Show estimated time left on par2 repair and unrar unpack

[Snuser]

The SABnzbd API issue was only related to the problem with Sonarr not accepting debug in the sense that it makes it annoying to have to wait to see if the patched version works. It’s SABnzbd I want to test for new issues, not Sonarr. Using a frequently updated develop version of both would make it harder to figure out what’s broken.