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

Fixes channel going back in time due to incomplete change. #22

Merged
merged 1 commit into from Aug 30, 2018

Conversation

samueldr
Copy link
Member

The change in d3d33d5 changed how the
locally saved channel information was saved on the local machine.

The changeset did not change the guard clause, which now made it act
like this:

  1. Try readlink on the file
  2. (bail as it's undefined)

The new behaviour is as more or less expected:

  1. Reads the file if available
  2. Split the URL components
  3. Keep the last bit

This can give us an empty string, which will compare to -1 thus
fulfilling the need.


I'd like to add these big disclaimers:

  1. The change as it is has not been tested fully integrated, due to the lack of a sandbox to play around replicating how the server works.
  2. I am not a perl developer, thus my implementation may lack the fine polish of a well-versed perl developer.

The code was as thoroughly tested as possible through this naïve script, which mostly replicates whatever is required.

This file is a giant hack :).

The change in d3d33d5 changed how the
locally saved channel information was saved on the local machine.

 * NixOS@d3d33d5#diff-682bf482f6dd273f1c3c49afd99b4660R192

The changeset did *not* change the guard clause, which now made it act
like this:

 1. Try readlink on the file
 2. (bail as it's undefined)

The new behaviour is as more or less expected:

 1. Reads the file if available
 2. Split the URL components
 3. Keep the last bit

This can give us an empty string, which will compare to `-1` thus
fulfilling the need.
@edolstra edolstra merged commit 8dfa9f3 into NixOS:master Aug 30, 2018
@samueldr samueldr deleted the fix/bttf-guard branch August 30, 2018 14:48
@vcunat
Copy link
Member

vcunat commented Oct 7, 2018

Hmm, right now we offer 18.09-beta-740-g6cbd1ec4b04 – commit pushed on Oct 3. That's suspicious to me.

@vcunat
Copy link
Member

vcunat commented Oct 7, 2018

By kicking Hydra I managed 18.09.783.299814b385d now. From a quick thought I suspect if changing the name (-beta) could've broken the ordering or something.

@andir
Copy link
Member

andir commented Oct 7, 2018

Same is happening with 18.03. It bounced back to 20th of September. No renaming was done there as far as I can tell.

@domenkozar
Copy link
Member

Could be this change wasn't deployed yet :)

@vcunat
Copy link
Member

vcunat commented Oct 29, 2018

@edolstra: is it easy to check whether this has been deployed? (Or at least try re-deploy blindly, but it would be nice to know if this PR didn't help.)

@edolstra
Copy link
Member

Looks like it's not deployed...

@edolstra
Copy link
Member

Now it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants