You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
ArchiveNotWritableError means you're not the owner of the archive, because
you don't have the private keys available. If you created the archives with
`bkr dev` then you should be the owner. This may be a bug.
Are you 100% sure you got the URLs right? If so, file an issue in beaker's
repo
(Self-writing archives might be too dangerous; haven't yet decided whether
to allow that.)
On Tue, Feb 7, 2017 at 11:38 AM, Ahmed Fasih ***@***.***> wrote:
Should I be able to test this in Beaker’s DevTools window?
I create two bkr dev archives (two because maybe an archive can’t edit
itself?).
In one of them, I open DevTools (Vew->Toggle DevTools), and type in:
dat.writeFile('dat://6fd40d077132bc0d23ba36bbcf5573
7a8ed87ea187abddb6461bc216351ea6e8/fromcode.txt', 'hi',
'utf8').then(x=>console.log('written!', x))
where that Dat URL is that of the other dev archive I made.
But I get ArchiveNotWritableError {name: "ArchiveNotWritableError",
message: ""}. No request in either tab asking for permission.
I will try putting this in JS instead of DevTools.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABNhU5CEssqplgE-7OjXMiIxQ3qThwVYks5raKwogaJpZM4L5AD->
.
It currently says that only the creating site can write to a dat. That's not true-- other sites can ask permission to write.
The text was updated successfully, but these errors were encountered: