Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BeyondHD Error - Value was either too large or too small for an Int64 #960

Closed
1 task done
nipuna-perera opened this issue Apr 16, 2022 · 2 comments
Closed
1 task done
Labels
Type: Bug Issue is a bug

Comments

@nipuna-perera
Copy link

nipuna-perera commented Apr 16, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

BeyondHD tracker isn't working

Expected Behavior

BeyondHD tracker works

Steps To Reproduce

  • Normal BeyondHD setup with API Key (Not one url)
  • click on settings
  • test
  • Check logs to see error - Value was either too large or too small for an Int64

Environment

- OS: 
- Prowlarr: 0.2.0.1678
- Docker Install: Yes
- Using Reverse Proxy: No
- Browser:

What branch are you running?

Master

Trace Logs?

2022-04-16 09:30:50.1|Warn|BeyondHD|Unable to connect to indexer

[v0.2.0.1678] System.OverflowException: Value was either too large or too small for an Int64.
at System.Number.ThrowOverflowOrFormatException(ParsingStatus status, TypeCode type)
at NzbDrone.Core.Parser.ParseUtil.CoerceLong(String str) in D:\a\1\s\src\NzbDrone.Core\Parser\ParseUtil.cs:line 56
at NzbDrone.Core.Indexers.Definitions.BeyondHDParser.ParseResponse(IndexerResponse indexerResponse) in D:\a\1\s\src\NzbDrone.Core\Indexers\Definitions\BeyondHD.cs:line 208
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in D:\a\1\s\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 320 at NzbDrone.Core.Indexers.HttpIndexerBase1.TestConnection() in D:\a\1\s\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 456
prowlarr.txt

AB#2999

@nipuna-perera nipuna-perera added Status: Needs Triage New Issue needing triage Type: Bug Issue is a bug labels Apr 16, 2022
@bakerboy448
Copy link
Contributor

bakerboy448 commented Apr 16, 2022

  • there is no master branch; how are you running a branch that doesn't exist?
  • Info logs of just the error are invalid for bug reports. The bug report template is clear on this.
  • Need the trace logs and ideally with the indexer response on so we know the bad value as well

@Qstick
Copy link
Contributor

Qstick commented Apr 16, 2022

The info is in discord @bakerboy448

@Qstick Qstick closed this as completed in 1b83459 Apr 16, 2022
bakerboy448 pushed a commit that referenced this issue May 2, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Bug Issue is a bug
Projects
None yet
Development

No branches or pull requests

3 participants