| 12:13 |
awt |
$ticker btc usd |
| 12:13 |
busybot |
Current BTC price in USD: $21677.29 |
| |
~ 2 hours 29 minutes ~ |
| 14:42 |
awt |
9972 sig: includes address cast support and a fix for the bug in which long messages are truncated instead of broken up into smaller messages. |
| |
↖ |
| |
~ 40 minutes ~ |
| 15:22 |
asciilifeform |
oh hey neato awt |
| 15:23 |
* |
asciilifeform will test as soon as hands free |
| 15:24 |
awt |
aweso |
| 15:24 |
awt |
me, thanks |
| 15:26 |
awt |
Last message types to implement (for blatta) are key offer and key slice. Honestly would wrather implement some kind of file storage/retrieval message types first. |
| 15:27 |
asciilifeform |
'# if the signature checks out for a peer with no AT entry, decrypt' << is this comment accurate, i.e. only worx if there is no at entry at all? (or worx per spec on any 'cold' peer?) |
| 15:30 |
awt |
No that comment isn't accurate. It checks all peers with keys. |
| 15:35 |
awt |
Actually doens't exclude warm peers though |
| |
~ 27 minutes ~ |
| 16:03 |
asciilifeform |
aok |
| 16:03 |
asciilifeform |
(oughta exclude warm peers tho) |
| 16:03 |
asciilifeform |
decoding against warm peers only wastes cpu |
| 16:06 |
asciilifeform |
( a warm peer, logically, at that moment knows yer addr/port and won't be firing off addrcast ) |
| 16:18 |
asciilifeform |
awt: does your latest blatta answer prod's correctly ? ( wasn't obv. to asciilifeform from reading the patch . the specful behaviour is that if receiving a prod where flag==0, one answers with anuther prod where flag==1. otherwise not answers) |
| 16:19 |
asciilifeform |
( pertinent spec ref ) |
| |
~ 22 minutes ~ |
| 16:42 |
awt |
asciilifeform: it does |
| 16:42 |
asciilifeform |
awt: a++ |
| |
~ 47 minutes ~ |
| 17:29 |
signpost |
awt: fired it up, getting a spray of error log messages regarding a peer with duplicate address or handle id. |
| |
↖ |
| 17:30 |
signpost |
it's complaining about deedbot and crawlerbot |
| 17:31 |
signpost |
which have neither the same address in AT nor same handle |
| 17:39 |
awt |
signpost: I left that message in there as more of a warning. I believe the duplicate check was needed due to an earlier error in the way at entries were created, where handle ids would be almost randomly assigned |
| 17:39 |
awt |
If there are no dupe values in your AT, I'm not sure why tha warning is firing off |
| 17:39 |
signpost |
filling up my logs atm with multiple per second |
| 17:40 |
signpost |
there are not. gotta be a bug in the is_duplicate thing |
| 17:40 |
signpost |
firing for deedbot still even though I unpeered crawlerbot |
| 17:40 |
awt |
feel free to comment it out, won't harm anything, but would be interesting to know specifically how it's borked |
| 17:41 |
signpost |
dropping some print statements in |
| 17:41 |
awt |
I am seeing ac messages from you btw |
| 17:44 |
signpost |
gird thine autisms for some noise while I debug plz |
| 17:48 |
signpost |
k the message originates from State.get_keyed_peers |
| 17:50 |
signpost |
and indeed deedbot has two keys in the keys table. |
| 17:52 |
awt |
Ah hmmm ok |
| 17:53 |
signpost |
deleting the unused key solved the warning message |
| 17:53 |
signpost |
not sure how I ended up in that state. I see that deedbot's sqlite db also has a duplicate key for bitbot |
| 17:54 |
signpost |
cool, going to update deedbot's station onw |
| 17:54 |
signpost |
*now |
| 17:55 |
awt |
It should be ok two have more than one key for a peer, but having duplicate keys is a little weird |
| 17:56 |
awt |
So get_keyed_peers still needs some work. |
| |
~ 24 minutes ~ |
| 18:20 |
signpost |
!!help |
| 18:20 |
deedbot |
http://deedbot.org/help.html |
| 18:22 |
signpost |
cool, those are on latest now. |
| 18:22 |
* |
signpost back to painting a room, bbl |
| 18:37 |
awt |
sweet |
| |
~ 3 hours 49 minutes ~ |
| 22:27 |
asciilifeform |
awt: ideally thing oughta check for duplicate keys on startup (or prohibit'em entirely in sql schema, better) |
| |
↖ |