SkynetLabs/pinner

Issues

• Pinner Endpoint to trigger a manual pin

  #50 opened 2 years ago by ro-tex
  0

• Batch skylinks on /sweep

  #49 opened 2 years ago by ro-tex
  0

• Detailed information in `GET /sweep/status`

  #48 opened 2 years ago by ro-tex
  0

• Potentially change the decision whether to log to disk via a separate env var

  #39 opened 2 years ago by ro-tex
  0

• Dry Run Follow-ups

  #31 opened 2 years ago by ro-tex
  0

• (lord of the nits) f/u You could make this a `<-chan struct{}` to prevent the receiver of the result from closing the channel.

  #25 opened 2 years ago by ro-tex
  0

• Get the list of pinned skylinks directly from skyd

  #3 opened 2 years ago by ro-tex
  0

• I agree with PJ on the naming. I think flipping it to `pinned` would be more readable.

  #10 opened 2 years ago by ro-tex
  0

• Take a look at ResponseRecorder

  #5 opened 2 years ago by ro-tex
  1

• SKY-279 Cluster-wide setting for underpinned threshold

  #8 opened 2 years ago by ro-tex
  1

• you're holding this lock while doing a bunch of I/O, are you sure that's fine?

  #11 opened 2 years ago by ro-tex
  3

• This is saying that there are no skylinks that can be pinned by this server right? Feels like we should just return the `mongo.ErrNoDocuments` in that case.

  #9 opened 2 years ago by ro-tex
  1

• Look at mongo change streams

  #20 opened 2 years ago by ro-tex
  0

• follow up; I would add a `parseSkylink` helper to ensure all endpoints and future endpoint parse the skylink the same way.

  #12 opened 2 years ago by ro-tex
  0

• It is still being used as the default sleep time in case we fail to fetch the size of the skyfile from `skyd`.

  #13 opened 2 years ago by ChrisSchinnerl
  1

• Configuration race conditions

  #6 opened 2 years ago by ro-tex
  0

• Improve Tester Shutdown

  #4 opened 2 years ago by ro-tex
  0