Skip to content

NIO generation support #829

Closed
Closed

Description

@jart

It's very important that we have richer testing for the atomicity of certain storage operations, like creating an object only if doesn't exist. We should also implement NIO OpenOption and CopyOption implementations for generations, which map to the functionality provided by StorageRpc.Option. FakeStorageRpc should have generational awareness for supporting this.

@jean-philippe-martin

Activity

  1. added
    priority: p2Moderately-important priority. Fix may not be included in next release.
    type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.
    on Jul 18, 2017
  2. danoscarmike commented on Aug 9, 2017

    @danoscarmike
    Contributor

    This issue may no longer be relevant due to its age. If you are still experiencing this issue and are reasonably certain that it is a bug, please feel free to re-open this it with enough information to help us reproduce it.

  3. jean-philippe-martin commented on Aug 15, 2017

    @jean-philippe-martin

    Actually this issue was fixed with commit #2232, so closing it was the right thing to do.

  4. added a commit that references this issue on Dec 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority: p2Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions