Skip to content

Bug: index out of range at L178 #1

Description

@0x27

Hey,
Was testing this out, and ran into a crash at line 178. I'm not a golang person, but it seems that it tries read in the list of proxies from a file, instead of retrieving them from the API in this version? Is this "Left to the user to implement" or an artefact from testing?

I'll have a go myself at getting it to work by trying to implement the API call to retrieve the list of proxies myself, but figured it was worth flagging up in case it was an accidental omission.

https://github.com/dis2/operator/blob/master/operator.go#L178

Also, related: When I test using the client ID you supplied, it gets flagged as "invalid", apparently...

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions