GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Own block rules lost after update to v. 1.0.0.3 · Issue #381 · gorhill/httpswitchboard

This repository was archived by the owner on Nov 15, 2017. It is now read-only.
This repository was archived by the owner on Nov 15, 2017. It is now read-only.

Own block rules lost after update to v. 1.0.0.3 #381

Copy link
Copy link
Closed
Closed
Own block rules lost after update to v. 1.0.0.3#381
Copy link

Description

@ghost
ghost
opened on Jul 23, 2014

Unfortunately, the "Your block rules" window is empty now. I assume that this problem might be related to the FileSystem API change?

Activity

  1. gorhill commented on Jul 23, 2014

    @gorhill
    gorhill
    on Jul 23, 2014
    Owner
    More actions

    Crap.

    I just reviewed the code and I can't see why it wouldn't work. Will keep looking but it's kind of too late at this point, there is no way back.

    If you have a back up, restoring should work fine though.

  2. gorhill commented on Jul 23, 2014

    @gorhill
    gorhill
    on Jul 23, 2014
    Owner
    More actions

    Ok so if I understand, before the restore, the block rules were gone, while the allow rules were properly converted to the new storage?

  3. gorhill commented on Jul 23, 2014

    @gorhill
    gorhill
    on Jul 23, 2014
    Owner
    More actions

    Ok. I see potential for a race condition, where there is an attempt to load data before it has been saved. If so, this means that your data was properly converted, but somehow the actual writing of bytes to the storage did not occur before the data was requested.

    I need to fix this.

    The workaround meanwhile in case other users end up with the same problem is a simple restart of the extension (disabling/enabling).

  4. gorhill
    closed this as completedin 9502679on Jul 23, 2014
  5. gorhill commented on Jul 23, 2014

    @gorhill
    gorhill
    on Jul 23, 2014
    Owner
    More actions

    Actually, correction:

    The data was irremediably lost. Whichever "block" or "allow" rules was saved first was clobbered if both fields had rules.

    I can still save Opera users I think.

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

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.