-
-
Notifications
You must be signed in to change notification settings - Fork 449
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
dat not sharing files other than dat.json #1191
Comments
I have the same problem with |
Did you try the executable, available in the Releases section? I think the npm install -g dat is broken last I heard |
Yes, I noticed the other issues (e.g. #1186) and indeed the executable works, but I did want to try the new version... |
sorry dat is currently unmaintained by a particular person but we're trying to fix that actively by spending some open collective money on a person |
I'm facing the same issue on both of my machines after installing dat using Specs:
++++++++++++++++++
|
@okdistribute I'm willing to help in anything you guys need. I just really like dat and I'll be glad to help |
@iankressin If you're interested in contributing time to get the Dat CLI working again, I'd be down to help coordinate that effort by giving pointers as to what needs to be done and reviewing PRs. It's a non-trivial amount of effort, however. 😅 |
@iankressin thanks ian! that would be super helpful. I think @RangerMauve is right, there is a non-trivial amount of 'potential' work, but I think getting it working with the latest Node is not that difficult, mostly updating dependencies and testing that it works. Since dat-node and dat are using package-lock.json, it falls behind easily when new Node versions come out. If you have time, we'd definitely merge a PR! |
@RangerMauve @okdistribute I'll definitely start taking a look at it in the next couple of days. @RangerMauve probably, I'll need a little bit of guidance at the beginning, so thanks for offering it. |
@RangerMauve I'm starting to take a look at the code and as the first action to try to solve this problem I upgraded the hypercore dependency from
The only difference between them being the node:x, where x varies in each error. The error message is not that helpful for debugging. I tried to search for What I'm looking for is better context for the error messages so I can debug faster. Am I in the right path? Below, are all the 5 errors with a little bit of prior context:
|
@iankressin sorry I wasn't clear, some dependencies can't be updated without significant work, but others can -- hypercore & hyperdrive can't be updated without updating dat-storage which would require some deep understanding of hyperdrive 10 |
@okdistribute No problem!! I'll get into hyperdrive as soon as possible. Is there a specific part of the code where you suggest to begin with the refactor? |
@RangerMauve Got a better understanding on hyperdrive now. Are you still available to give some guidance on the refactoring? |
@iankressin Yeah sure, would you be down for a 1 hour call some time this week? Tuesday is good for me between 11:00 ET and 22:00 ET, but I can do another day if you prefer. 😁 |
@RangerMauve yepp, I'm down. Tuesday is good for me. 20:00 ET?? |
20:00 ET works for me. I'll follow up via DMs. 😁 |
We had a call today to talk about what would need to be done to get the CLI working again, specifically around dat-store. The notes from the call can be found here: https://hackmd.io/XDxGGosQTvuCpeQwl5vahg?view |
Thank you guys, this is wonderful news. |
hello ,
I am using linux and node version 12,
I installed dat cli globally , with npm i -g dat , on my linux
Then i went to my Desktop and made a folder share_it with one text file in it,
as given in the documentation, i did
"dat share share_it"
it showed me sharing dat: (empty archive),
No files are being shared, as i did a dat clone onto my other computer with other network connection, but no luck,
Can some please help me
The text was updated successfully, but these errors were encountered: