Comments (7)
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:
- "Priority" labels will show how urgent this is for the team.
- "Status" labels will show if this is ready to be worked on, blocked, or in progress.
- "Need" labels will indicate if additional input or analysis is required.
Finally, remember to use https://discuss.ipfs.io if you just need general support.
from go-unixfs.
should FSNode continue to use the protobuf-generated struct implementation, or should we generate an equivalent ipld-prime node representation of that data?
I'd actually rather write custom code. We need to guarantee a somewhat funky encoding order anyways.
enumerate the interfaces (e.g. a quick glance shows public methods like NewShard make use of a dag service) that would ideally transition from reliance on ipld-format/go-merkeldag to prime equivalents (maybe you haves started this, @gammazero ?)
We'll likely have to throw away almost all of the current interfaces.
from go-unixfs.
We'll likely have to throw away almost all of the current interfaces.
I guess the main question is what things do we care about stability on / are problematic to break / should continue to be supported. If we have the top level CLI functionality remain the same are we okay? Would you suggest making a separate implementation for the CLI to use and have a way for consumers to use this implementation with the go-ipld-legacy
shim until they're ready to transition?
from go-unixfs.
The top-level CLI should continue to work. In terms of this library, I'd actually just crate a new one (maybe go-ipfs-fs
?) and merge in everything you need (likely pieces of go-ipfs-chunkers, go-unixfs, go-ipfs-files, and go-merkledag).
If we want to stick with a single repo, also feel free to go with a v2.
from go-unixfs.
@willscott I have stayed away from making changes to unixfs so far, but need to so was hoping to know what we want to do with unixfs very soon.
from go-unixfs.
Things building on UnixFS we're aware of:
from go-unixfs.
This repository is no longer maintained and has been copied over to Boxo. In an effort to avoid noise and crippling in the Boxo repo from the weight of issues of the past, we are closing most issues and PRs in this repo. Please feel free to open a new issue in Boxo (and reference this issue) if resolving this issue is still critical for unblocking or improving your usecase.
You can learn more in the FAQs for the Boxo repo copying/consolidation effort.
IMO redundent after ipfs/boxo#224 ping me if you want to reopen and move this anyway.
from go-unixfs.
Related Issues (20)
- Do not add an internal timeout for "extra" fetches used to compute directory size in the unsharding algorithm HOT 4
- [unsharding] Follow up on some low-priority fixes/renames/refactors HOT 1
- The context in `CtxReadFull` is not propagated to the child nodes being read HOT 4
- Trying to use in project, fails with go-merkledag errors HOT 2
- Avoid use of `pb.Data` HOT 6
- `Sync()`/`modifyDag()`: correctly handle offsets bigger than file size HOT 3
- Use only one kind of variable to refer to data types HOT 1
- Importers: DAGService should not be batched internally by default HOT 5
- Remove the `child` interface from the `hamt` package HOT 6
- Maybe we could use `ResolveLink` HOT 1
- Remove the internal `ProtoNode` from the `Shard` structure HOT 19
- HAMT: evaluate using the DAG walker in `getValue` HOT 3
- HAMT: review `getValue` and `walkTrie` HOT 1
- `go-merkledag` dependency version discrepancy with `go-ipfs` HOT 9
- Can we remove the `expandSparse` call in `WriteAt`? HOT 5
- "Impedance mismatch" between mode as specified in spec/UNIXFS.md and go's os.FileMode HOT 7
- Add created/modified fields to unixfs files HOT 2
- State of UnixFS v2 HOT 3
- Remove `HAMTShard` UnixFS type HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from go-unixfs.