| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
First tried lts-14.7, but the version of cabal-install currently in debian
unstable (2.2.0.0) is not able to parse its cabal files.
Small fix for MonadFail changes.
This commit was sponsored by Jochen Bartl on Patreon.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't fully understand the need for the MonoLocalBinds language extension,
which was not needed before but now ghc complains if it's not included,
but I've tested it and it does work.
All the rest of the changes are straightforward AMP changes and dep
updates.
Removed fgl from stack.yaml because it seems that indirect dep no longer
needs to be specified for stack to build.
Added custom-setup stanza since stack now warns without one.
This commit was sponsored by Trenton Cronholm on Patreon.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is distinct from the wire protocol version used in the websocket
framing of messages. Versioning the high level protocol will let later
features be added.
The user controls the protocol version, since they send the first
several messages. Developers that connect need to avoid using features
from newer protocol versions.
So, developers and servers will need to support the most recent version,
while the user can have an old version of debug-me and it will continue
to work.
This commit changes the protocol buffer encoding, and is the last such
free change. All changes past this point will need to be versioned.
This commit was sponsored by Jochen Bartl on Patreon.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This makes debug-me not rely on the gpg keyservers at all.
Before, it was only working when the user had the developer's public key
already. I thought that --verify would download from --keyserver, but
seems not.
This is a protocol breaking change! Luckily done before any release, so
ok. ProtocolBuffers renumbered.
This commit was sponsored by Denis Dzyubenko on Patreon.
|
| | |
|
| |
|
|
| |
This commit was sponsored by Jake Vosloo on Patreon.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Client requires this always point to the previous Entered it accepted,
so a hash chain of Entered is built up, and there is no possibility for
ambiguity about which order a client received two Entered activies in.
So restoreHashes now has to try every possible combination of
known hashes for both prevEntered and prevActivity. That could be
significantly more work, but it would be unusual for there to be a lot
of known hashes, so it should be ok.
--graphviz shows this additional hash chain with grey edges
(and leaves out edges identical to the other hash chain)
While testing this with an artifical network lag, it turned out that
signature verification was failing for Reject messages sent by the
user. Didn't quite figure out what was at the bottom of that,
but the Activity Entered that was sent back in a Reject message was
clearly not useful, because it probably had both its prevEntered and
prevActivity hashes set to Nothing (because restoreHashes didn't restore
them, because the original Activity Entered was out of the expected
chain). So, switched Rejected to use a Hash.
(And renamed Rejected to EnteredRejected to make it more clear what
it's rejecting.)
Also, added a lastAccepted hash to EnteredRejected. This lets
the developer find its way back to the accepted chain when some
of its input gets rejected.
This commit was sponsored by Trenton Cronholm on Patreon.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Last commit allows this simplification
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
I think there was a race where a SessionKey message had been drained
from the TChan, but not yet added to the developer state, which was
resonsible for recent instability at startup.
It manifested as protocol errors where the prevActivity hash was wrongly
Nothing.
Fixed by adding a MissingHashes type to tag things whose hashes have
been stripped, and adding back the hashes when needed, which always
happens inside atomically blocks, so won't have such a race.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
And improve some messages.
|
| | |
|
| |
|
|
|
| |
The control window doesn't know it's running for a developer, so it
would prompt to allow these, which was pointless.
|
| |
|
|
| |
This fixes chat message echoing consistency too.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
start
|
| | |
|
| |
|
|
| |
Works!
|
| |
|
|
|
|
|
|
|
| |
Make watcher also log and display the name of the logfile at start and
end of session.
--download still downloads to current directory because that seems less
surprising than downloading to elsewhere. Also, the user might want to
keep a copy of the local log while downloading the server log.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do include it in the data that gets signed, so it can be recovered
by trying each likely (recently seen) Activity as the prevMessage, and
checking the signature.
The UserState and DeveloperState already had the necessary state about
recently seen hashes, so this does not impact data use.
One tricky bit is that relayFromSocket needs to wait for the TMChan
to be empty before calling restorePrevActivityHash. Otherwise, the
hashes of items in the channel that have not been processed yet won't be
tried. The TMChan is not really being used as a channel since only 1
item can be in it. It could be converted to a TMVar, but closeTMChan is
used so I left it as a channel.
Note that the server does not restore hashes of messages that pass
through it; it's just a dumb relay.
Sending a single key press now only needs 94 bytes of data to be sent,
down from 169!
---
Also switched to SHA512, since hashes are no longer being sent over
the wire and so the larger size does not matter. SHA512 is slightly
faster and more secure.
This commit was sponsored by Ewen McNeill.
|
| |
|
|
| |
Make it a monoid and use mempty = 0
|
| |
|
|
| |
Not related to the Log anymore.
|
| |
|
|
|
|
| |
And part of what we need to have users verify them.
This commit was sponsored by andrea rota.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Time is relative, so the debug-me proof chain doesn't prove when things
happened, but it's still useful to have some idea of how long things
took to happen. This makes --replay work with logs gotten by --download.
Log still includes loggedTimestamp. This is a bit redundant, and is
unused now, but it's useful for log files to record when messages were
received.
This commit was sponsored by Riku Voipio.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
messages
This makes --download always work, which was the real motivation.
It's probably a good ways to having multiple connected developers able
to simulantaneously interact. I tested that breifly, and it seems to
work ok! It may however, not handle it perfectly when both developers
are trying to type at the same time. Still, nice that's basically
working for free!
This commit was sponsored by Jeff Goeke-Smith on Patreon.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Including the process exit status.
And cleaner Role.User shutdown sequence.
|
| | |
|
| |
|
|
| |
Now when the user quits, the developer also exits.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Multi-user client-server debug-me is working, almost perfectly.
All that was missing was replaying the log when the developer connected.
A number of race conditions had to be avoided to do that sanely.
This commit was sponsored by Ignacio on Patreon.
|
| | |
|
| |
|
|
|
|
| |
For some reason, runClient throws ConnectionClosed on apparently clean
shutdown. This happens even though clientApp uses sendClose, and the
server receives it and shuts down entirely cleanly.
|
| | |
|
| |
|
|
| |
This commit was sponsored by Ewen McNeill.
|
| |
|
|
|
|
|
| |
Nice, was able to reuse all the protocol stuff from Role.Developer for
this.
This commit was sponsored by Fernando Jimenez on Patreon.
|
