| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
New setting, can be used to disable autocommit of changed files by the
assistant, while it still does data syncing and other tasks.
Also wired into webapp UI
|
| |
|
|
|
|
|
| |
wget is used due to having better progress output, but curl is used
in some cases where wget is not appropriate.
|
|
|
|
| |
is available.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to the top of the repository, even when operating inside a subdirectory.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Union merges involving two or more repositories could sometimes result in
data from one repository getting lost. This could result in the location
log data becoming wrong, and fsck being needed to fix it.
NB: I audited for any other occurrences of this problem. There are other
places than union merge where multiple changes are fed into update-index
in a stream, but they all involve working copy files being staged, or their
deletion being staged, and in this case it's fine for the later changes
to override the earlier ones.
|
|
|
|
| |
passphrases rather than using the supplied --passphrase-fd.
|
|
|
|
| |
that is not a git repository.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
It used to not log to daemon.log when a repository was first created, and
when starting the webapp. Now both do. Redirecting stdout and stderr to the
log is tricky when starting the webapp, because the web browser may want to
communicate with the user. (Either a console web browser, or web.browser = echo)
This is handled by restoring the original fds when running the browser.
|
|
|
|
| |
#698184
|
|
|
|
| |
quoting in different versions of shakespeare-js.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
would cause a surprising behavior if modifying one, where the other would also change.
|
| |
|
|
|
|
|
| |
Checks the key's size and checksum. This is sorta expensive, but it avoids
needing to add another round-trip to the protocol.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A while ago I added code to support recent versions of shakespeare-js,
(commit a2e8bda7df7707f84cd551ed16ffaa0bf7c3aac0). But it seems that resulted
in quoting of all strings inserted into javascript files, which means it's
now impossible to do the type of metaprogramming that longpolling.julius
relied on. I have found another way to accomplish the same thing without
needing to generate unique function names. Hopefully it's portable.
Opinion of shakespeare-js now at rock bottom. One of these days, this
needs to be redone to use Fay.
|
|
|
|
|
|
|
|
|
| |
since some systems may have configuration problems or other issues that
prevent web browsers from connecting to the right localhost IP for the
webapp.
Tested on both ipv4 and ipv6 localhost. Url for the latter looks like:
http://[::1]:50676
|
|
|
|
| |
on a drive that's not mounted).
|
| |
|
|
|
|
| |
the transfer, which can happen in direct mode.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also, changed sync to no longer automatically add files in direct mode.
That was only necessary before because add didn't work.
|
| |
|
| |
|
|
|
|
| |
content is not present.
|
|
|
|
| |
environment to prevent git from failing.
|
|
|
|
|
|
|
|
| |
drop, log.
These started working, for free, once lookupFile supported direct mode.
yay!!
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The expensive scan uses lookupFile, but in direct mode, that doesn't work
for files that are present. So the scan was not finding things that are
present that need to be uploaded. (It did find things not present that
needed to be downloaded.)
Now lookupFile also works in direct mode. Note that it still prefers
symlinks on disk to info committed to git, in direct mode. This is
necessary to make things like Assistant.Threads.Watcher.onAddSymlink
work correctly, when given a new symlink not yet checked into git (or
replacing a file checked into git).
|
| |
|
|
|
|
|
| |
Browser behavior is not ideal; a new tab is opened on restart.
Browsers won't let me redirect to a file:// so I cannot use the old tab.
|
|
|
|
|
|
|
| |
Would like to also have restart UI, but that's rather harder to do,
seems it'd need to start another copy of the webapp, and redirect the
browser to its new url, but running two assistants in the same repo at
the same time isn't good.
|
| |
|