profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/sdondley/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Steve Dondley sdondley Prometheus Labor Communications https://steve.dondley.com

pqrs-org/KE-complex_modifications 803

Karabiner-Elements complex_modifications rules

sdondley/Anki-Import 15

Efficiently generate Anki notes with your text editor for easy import into Anki.

sdondley/JSON-Karabiner 9

JSON::Karabiner - easy JSON code generation for Karabiner-Elements

sdondley/cheat 1

cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind *nix system administrators of options for commands that they use frequently, but not frequently enough to remember.

sdondley/Dist-Zilla-for-Beginners 1

Dist::Zilla tutorial for new developers and Dist::Zilla beginners

prometheuslabor/prometheus_wordpress 0

Prometheus Wordpress Base

sdondley/alacritty 0

A cross-platform, GPU-accelerated terminal emulator

sdondley/apachebuddy.pl 0

Not written by me, maintained by me : Apachebuddy.pl

sdondley/App-sayhi 0

toy dist zilla demo

sdondley/Arduino_avrusb_firmware 0

firmwares for Arduino boards based on LUFA151115

issue openedcosminadrianpopescu/muttcube

Switching away from browser and back to browser causes blur event and field loses focus

To reproduce:

  1. compose a new message
  2. start entering text in body
  3. move cursor to another part of the body message
  4. switch away from browser to another open application
  5. switch back to browser

You can no longer type into the compose field after switching back. Ideally, the body field would be refocused automatically and cursor would remain in the same location. This is how it works without muttcube installed.

Workaround: hit the escape key and then click in the field or double click somewhere in the body field and start typing again. While this works, it causes causes you to lose your previous cursor position, which is annoying.

created time in 2 days

issue commentroundcube/roundcubemail

$_SESSION['search_scope'] getting masked by code in app.js

OK, thanks.

I guess I'll just leave my one-line hack in place. Unfortunately, I do not have the spare hours required to write a proper patch that is non-trivial.

Thanks for all your work on roundcube.

sdondley

comment created time in 5 days

issue openedroundcube/roundcubemail

$_SESSION['search_scope'] getting masked by code in app.js

Note: This is not a debian package manager bug as I thought. Some stupidity on my end while trying to debug this issue led me to believe that. (See closed issue #8198). I'm reopening this issue in a new thread to minimize confusion.

As best I can tell from looking at the code, roundcube is supposed to remember the search_scope stored in $_SESSION so that when switching between folders, the same scope is kept.

However, when switching between folders, the search_scope is not remembered and it defaults to "base." The user is forced to refresh the page manually to get the "Seach scope" setting to the value stored in the session.

A simple hack to the code gives me the behavior I desire (always default to search all folders because I'm using solr to perform searches which is fast):

2696c2696
<       this.env.search_scope = 'base';
---
>       this.env.search_scope = 'all';

Obviously this is not the proper fix. This code is to just illustrate the problem.

created time in 6 days

issue commentroundcube/roundcubemail

Javascript overriding $config['search_scope'] setting?

I've made an attempt to report this issue to the debian package manager: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068

sdondley

comment created time in 7 days

issue commentroundcube/roundcubemail

Javascript overriding $config['search_scope'] setting?

After minifying app.js manually and replacing app.min.js, everything still works. So yeah, looks like a stale copy of app.min.js was shipped with the debian package I'm using.

sdondley

comment created time in 8 days

issue commentroundcube/roundcubemail

Javascript overriding $config['search_scope'] setting?

Alright, I think the problem is that app.min.js is a stale minimized copy of a older version of app.js.

If I simply overwrite app.min.js with app.js, things work as expected.

Don't know if this is a debian package manager's issue or what. At any rate, things are woking perfectly using the non-minimized version of app.js.

sdondley

comment created time in 8 days

issue commentroundcube/roundcubemail

Javascript overriding $config['search_scope'] setting?

Based on some tinkering I did, I suspect there is some kind of caching of app.min.js that is the cause of the problem. I think this line:

scope = this.env.search_scope || 'base',

it's loading very old, stale values. But I'm not sure because I have no idea how js caching might be set up with roundcube.

But by tinkering with this line in app.min.js and forcing it to all lke so:

scope = this.env.search_scope || 'all',

I got things to work properly. I'm just not sure how to flush the cache to get the changes to take consisently.

sdondley

comment created time in 8 days

issue openedroundcube/roundcubemail

Javascript overriding $config['search_scope'] setting?

Using 1.4.11.

I have the $config['search_scope'] = 'all' in my config file.

However, when I click in new folder and open the search menu, the search setting defaults to 'current folder'. I have to manually refresh the page to get the 'all folders' setting to kick in. It seems like some javascript might be overriding the initial setting of the search scope. Not sure, though.

Please advise.

created time in 8 days

issue commentzakkor/shortcut

How to get woking on a mac

I have brew's coreutils package installed on my mac. That package may have installed realpath on my machine for me. So coreutils from brew may need to be installed if that's the case.

sdondley

comment created time in 10 days

push eventsdondley/shortcut

Steve Dondley

commit sha 5929bd802404f36b390f77067e7191bd763bbe5c

add test for macos

view details

push time in 10 days

pull request commentzakkor/shortcut

fixes for macos

ah, crap, I just realized I screwed this up. forgot to test for darwin before changing command name.

sdondley

comment created time in 10 days

pull request commentzakkor/shortcut

fixes for macos

This is totally untested outside of macos.

sdondley

comment created time in 10 days

PR opened zakkor/shortcut

fixes for macos

For #3

+6 -3

0 comment

2 changed files

pr created time in 10 days

push eventsdondley/shortcut

Steve Dondley

commit sha 6c52bbe7fbce6533404a550444710bb2784bb206

fixes for macos

view details

push time in 10 days

issue commentzakkor/shortcut

How to get woking on a mac

I'll submit a proper patch when I have a little more time if there is interest. Let me know.

sdondley

comment created time in 10 days

fork sdondley/shortcut

Quickly make and use shortcuts in your shell for easy navigation

fork in 10 days

startedzakkor/shortcut

started time in 10 days

issue openedzakkor/shortcut

How to get woking on a mac

If you are reading this, it probably means you are trying to install on a mac. It won't work. But you can get it to work with a few relatively simple steps.

First, if you are trying to install with install.sh and getting an error about a directory not existing, do this:

sudo mkdir /usr/local/bin

Now run the install script and it should work.

Now you will get more errors. The first error is because you may be running the ancient version of bash that is installed on your mac. East fix:

  1. install homebrew if not already installed (google it)
  2. brew install bash

Ok, done.

But you will still get errors because the shortcut script is set up to use the old version of bash. Easy fix:

  1. Edit the first line of /usr/local/bin/shortcut to this:

#!/usr/bin/env bash

Ok, fixed.

But wait, don't close out the file yet. Change line 17 (or thereabouts) of the same file from:

path=$(readlink -m $2)

to:

path=$(realpath -m $2)

Everything should now work.

created time in 10 days

issue closedjunegunn/fzf.vim

Looking for a quick hand on hacking ripgrepFzf example function

<!-- ISSUES NOT FOLLOWING THIS TEMPLATE WILL BE CLOSED AND DELETED -->

<!-- Check all that apply [x] -->

  • [x] I have fzf 0.23.0 or above
  • [x] I have read through https://github.com/junegunn/fzf.vim/blob/master/README.md
  • [x] I have read through https://github.com/junegunn/fzf/blob/master/README-VIM.md
  • [x] I have read through the manual page of fzf (man fzf)
  • [x] I have searched through the existing issues

I've hacked the RipgrepFzf() example function to accept a directory argument. I'm now trying to hack it so it does not show the full path to the file. I've tried adding --delimiter / --with-nth -1 per another issue I found on here but I can't figure out where to put it. Here's what I have right now:

function! RipgrepFzf(query, fullscreen, dir)
  let command_fmt = 'rg -L --column --line-number --no-heading --color=always --smart-case %s %s || true'
  let initial_command = printf(command_fmt, shellescape(a:query), a:dir)
  let reload_command = printf(command_fmt, '{q}', a:dir)
  let spec = {'--delimiter / --with-nth -1 options': ['--phony', '--query', a:query, '--bind', 'change:reload:'.reload_command]}
  call fzf#vim#grep(initial_command, 1, fzf#vim#with_preview(spec), a:fullscreen)
endfunction

I'm also tried stuffing the --delimiter options into the options array but no luck with that either. I just get errors.

closed time in 11 days

sdondley

issue commentjunegunn/fzf.vim

Looking for a quick hand on hacking ripgrepFzf example function

Ok, I must have had a typo earlier. Just plain old '-1' is working now.

Looks like I'm good. Again, awesome plugin.

sdondley

comment created time in 11 days

issue commentjunegunn/fzf.vim

Looking for a quick hand on hacking ripgrepFzf example function

So this works:

let spec = {'options': ['--delimiter', '/', '--with-nth', '1', '--phony', '--query', a:query, '--bind', 'change:reload:'.reload_command]}

However, the '1' is not what I want. When I try with '-1', I get an error. I tried escaping the - but no luck. Hmm...maybe shellescape() is the solution.

sdondley

comment created time in 11 days

issue openedjunegunn/fzf.vim

Looking for a quick hand on hacking ripgrepFzf example function

<!-- ISSUES NOT FOLLOWING THIS TEMPLATE WILL BE CLOSED AND DELETED -->

<!-- Check all that apply [x] -->

  • [x] I have fzf 0.23.0 or above
  • [x] I have read through https://github.com/junegunn/fzf.vim/blob/master/README.md
  • [x] I have read through https://github.com/junegunn/fzf/blob/master/README-VIM.md
  • [x] I have read through the manual page of fzf (man fzf)
  • [x] I have searched through the existing issues

I've hacked the RipgrepFzf() example function to accept a directory argument. I'm now trying to hack it so it does not show the full path to the file. I've tried adding --delimiter / --with-nth -1 per another issue I found on here but I can't figure out where to put it. Here's what I have right now:

function! RipgrepFzf(query, fullscreen, dir)
  let command_fmt = 'rg -L --column --line-number --no-heading --color=always --smart-case %s %s || true'
  let initial_command = printf(command_fmt, shellescape(a:query), a:dir)
  let reload_command = printf(command_fmt, '{q}', a:dir)
  let spec = {'--delimiter / --with-nth -1 options': ['--phony', '--query', a:query, '--bind', 'change:reload:'.reload_command]}
  call fzf#vim#grep(initial_command, 1, fzf#vim#with_preview(spec), a:fullscreen)
endfunction

I'm also tried stuffing the --delimiter options into the options array but no luck with that either. I just get errors.

created time in 11 days

startedsedm0784/vim-you-autocorrect

started time in 12 days

issue openedcheat/cheat

No fzf integration with zsh completion

Thanks for submitting a bug report. Please provide the following information:

A description of the problem fzf not implemented with zsh. The zsh script does not include a function for implementing zsh.

cheat version info 4.2.2

created time in 12 days

issue commentcheat/cheat

Enable fuzzy search

I don't understand how this works. I have fzf installed and added the export line to my .zshrc. It doesn't seem to do anything different.

chongchonghe

comment created time in 12 days

created repositorysdondley/cheatsheets

created time in 12 days

issue commentcheat/cheat

zsh autocompletion working, but not for cheat file names

OK, I just made the default value for state to be 'full'. Seems to work.

_cheat() {
  local state
  state='full'

...snip...

Then it get overridden by the _arguments portion of the code. If this is the correct way of fixing this, just let me know and I'll submit a patch.

sdondley

comment created time in 13 days

issue commentcheat/cheat

zsh autocompletion working, but not for cheat file names

OK, so looking at the completion script, there is a $state variable on or about line 45 that never gets set. When I change that $state variable and replace it with 'full', completions for cheat file names start working.

I'm not much of a shell scripter so I'm not quire sure how get the $state variable to reflect the correct context. Maybe the bash script will offer some clues. I'll take a look.

sdondley

comment created time in 13 days

issue openedcheat/cheat

zsh autocompletion working, but not for cheat file names

Thanks for submitting a bug report. Please provide the following information:

A description of the problem I have zsh (with ohmyzh). Completions are working for cheat arguments but they are not working for the names of the cheatsheet files.

Example: cheat tm<tab> does nothing even though a tmux cheat sheet exists in my ~/.config/cheat/cheatsheets/personal directory cheat -<tab> generates a list of acceptable arguments for the cheat command

cheat version info 4.2.2

created time in 13 days

issue closedtmux/tmux

Spurious control-click events occurring with both terminal and iterm when switching between panes using tmux navigator with "focus-events" on

Issue description

Out of the blue, a left click event is somehow getting triggered when using tmux navigator to switch between panes. This is happening in both iterm and the stock terminal app on my mac. As a side effect of the control-click, it can cause neovim to throw spurious errors when switching between panes or iterm to pop open a context menu.

Here's the weird part: it only happens if I hold the ctrl key down for an extended length of time. If I quickly release the ctrl key, I can't trigger the problem. Also, the problem is intermittent. It only happens maybe half the time. It doesn't appear to happen on all panes. On a freshly opened pane it may not happen immediately but after a while, it can start occurring.

I didn't change any settings that I'm aware of that might have changed the behavior of tmux.

The fix is simple: set "focus-events" setting to "off".

Required information

Please provide the following information:

  • tmux version (tmux -V).

tmux 3.2a

  • Platform (uname -sp).

Darwin i386

  • $TERM inside and outside of tmux (echo $TERM).

"screen-256color" for both in an out

  • Logs from tmux (tmux kill-server; tmux -vv new).

1630778692.596425 client started (19665): version 3.2a, socket /private/tmp/tmux-501/default, protocol 8 1630778692.596495 on Darwin 20.6.0 Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 1630778692.596512 using libevent 2.1.12-stable (select); utf8proc 2.6.1; ncurses 6.2 1630778692.596548 flags are 0x18010000 1630778692.596559 socket is /private/tmp/tmux-501/default 1630778692.596577 trying connect 1630778692.596602 connect failed: Connection refused 1630778692.596814 lock file is /private/tmp/tmux-501/default.lock 1630778692.596907 flock succeeded 1630778692.596916 got lock (6) 1630778692.596942 trying connect 1630778692.596955 connect failed: Connection refused 1630778692.597564 add peer 0x7f8d30008000: 7 (0x0) 1630778692.599351 sending message 100 to peer 0x7f8d30008000 (4 bytes) 1630778692.599374 sending message 111 to peer 0x7f8d30008000 (8 bytes) 1630778692.599385 sending message 101 to peer 0x7f8d30008000 (15 bytes) 1630778692.599393 sending message 109 to peer 0x7f8d30008000 (4 bytes) 1630778692.599426 sending message 102 to peer 0x7f8d30008000 (13 bytes) 1630778692.599434 sending message 108 to peer 0x7f8d30008000 (20 bytes) 1630778692.599443 sending message 112 to peer 0x7f8d30008000 (58 bytes) 1630778692.599450 sending message 112 to peer 0x7f8d30008000 (5 bytes) 1630778692.599458 sending message 112 to peer 0x7f8d30008000 (5 bytes) 1630778692.599466 sending message 112 to peer 0x7f8d30008000 (6 bytes) 1630778692.599474 sending message 112 to peer 0x7f8d30008000 (6 bytes) 1630778692.599481 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.599489 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.599497 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599505 sending message 112 to peer 0x7f8d30008000 (14 bytes) 1630778692.599513 sending message 112 to peer 0x7f8d30008000 (19 bytes) 1630778692.599520 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.599528 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.599537 sending message 112 to peer 0x7f8d30008000 (15 bytes) 1630778692.599544 sending message 112 to peer 0x7f8d30008000 (21 bytes) 1630778692.599551 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599559 sending message 112 to peer 0x7f8d30008000 (7 bytes) 1630778692.599566 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599574 sending message 112 to peer 0x7f8d30008000 (7 bytes) 1630778692.599582 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599589 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.599596 sending message 112 to peer 0x7f8d30008000 (21 bytes) 1630778692.599604 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599611 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.599620 sending message 112 to peer 0x7f8d30008000 (16 bytes) 1630778692.599629 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599636 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.599644 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.599651 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599659 sending message 112 to peer 0x7f8d30008000 (8 bytes) 1630778692.599666 sending message 112 to peer 0x7f8d30008000 (8 bytes) 1630778692.599674 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599682 sending message 112 to peer 0x7f8d30008000 (7 bytes) 1630778692.599689 sending message 112 to peer 0x7f8d30008000 (7 bytes) 1630778692.599698 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.599705 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.599713 sending message 112 to peer 0x7f8d30008000 (15 bytes) 1630778692.599720 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599728 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599736 sending message 112 to peer 0x7f8d30008000 (8 bytes) 1630778692.599743 sending message 112 to peer 0x7f8d30008000 (14 bytes) 1630778692.599752 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.599773 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.599779 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.599785 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.599791 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.599796 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.599820 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.599825 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599830 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599835 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599841 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599845 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599850 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.599854 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.599858 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599863 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599867 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599872 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599878 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599883 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.599889 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599893 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599898 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599903 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599907 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599912 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599916 sending message 112 to peer 0x7f8d30008000 (8 bytes) 1630778692.599921 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.599926 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.599931 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.599935 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599940 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599945 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599949 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.599954 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599959 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599964 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599969 sending message 112 to peer 0x7f8d30008000 (8 bytes) 1630778692.599974 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599979 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599983 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599988 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.599994 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600000 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600005 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600011 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600016 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600031 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600038 sending message 112 to peer 0x7f8d30008000 (8 bytes) 1630778692.600042 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600048 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600053 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600057 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600060 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600064 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600068 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600073 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600079 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600123 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600133 sending message 112 to peer 0x7f8d30008000 (8 bytes) 1630778692.600139 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600145 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600151 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600157 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600162 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600167 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600172 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600176 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600180 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600184 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600189 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600193 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600197 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600203 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600206 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600211 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600216 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600220 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600225 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600230 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600234 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600238 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600243 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600247 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600253 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600258 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600263 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600268 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600274 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600279 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600285 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600289 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600293 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600298 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600302 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600307 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600312 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.600316 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600321 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600327 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600334 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600339 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600344 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.600348 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600353 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600358 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600362 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600367 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600371 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600376 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600381 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600386 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.600390 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600395 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600399 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600418 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600424 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600428 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600434 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.600440 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600445 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600450 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600455 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600460 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600464 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600469 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.600473 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600478 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600482 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600486 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600491 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600496 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600501 sending message 112 to peer 0x7f8d30008000 (11 bytes) 1630778692.600506 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600511 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600516 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600521 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600527 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600530 sending message 112 to peer 0x7f8d30008000 (21 bytes) 1630778692.600535 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600540 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.600545 sending message 112 to peer 0x7f8d30008000 (6 bytes) 1630778692.600552 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600557 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600562 sending message 112 to peer 0x7f8d30008000 (24 bytes) 1630778692.600567 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600572 sending message 112 to peer 0x7f8d30008000 (9 bytes) 1630778692.600577 sending message 112 to peer 0x7f8d30008000 (70 bytes) 1630778692.600582 sending message 112 to peer 0x7f8d30008000 (69 bytes) 1630778692.600587 sending message 112 to peer 0x7f8d30008000 (12 bytes) 1630778692.600591 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600595 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600600 sending message 112 to peer 0x7f8d30008000 (24 bytes) 1630778692.600604 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600609 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600613 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600618 sending message 112 to peer 0x7f8d30008000 (10 bytes) 1630778692.600622 sending message 112 to peer 0x7f8d30008000 (13 bytes) 1630778692.600628 sending message 112 to peer 0x7f8d30008000 (15 bytes) 1630778692.600632 sending message 112 to peer 0x7f8d30008000 (5 bytes) 1630778692.600647 sending message 104 to peer 0x7f8d30008000 (0 bytes) 1630778692.600654 sending message 110 to peer 0x7f8d30008000 (0 bytes) 1630778692.600659 sending message 107 to peer 0x7f8d30008000 (4 bytes) 1630778692.600664 sending message 105 to peer 0x7f8d30008000 (60 bytes) 1630778692.600668 sending message 105 to peer 0x7f8d30008000 (66 bytes) 1630778692.600673 sending message 105 to peer 0x7f8d30008000 (26 bytes) 1630778692.600677 sending message 105 to peer 0x7f8d30008000 (15 bytes) 1630778692.600682 sending message 105 to peer 0x7f8d30008000 (26 bytes) 1630778692.600687 sending message 105 to peer 0x7f8d30008000 (14 bytes) 1630778692.600691 sending message 105 to peer 0x7f8d30008000 (17 bytes) 1630778692.600695 sending message 105 to peer 0x7f8d30008000 (24 bytes) 1630778692.600700 sending message 105 to peer 0x7f8d30008000 (15 bytes) 1630778692.600718 sending message 105 to peer 0x7f8d30008000 (43 bytes) 1630778692.600724 sending message 105 to peer 0x7f8d30008000 (27 bytes) 1630778692.600729 sending message 105 to peer 0x7f8d30008000 (23 bytes) 1630778692.600734 sending message 105 to peer 0x7f8d30008000 (419 bytes) 1630778692.600741 sending message 105 to peer 0x7f8d30008000 (64 bytes) 1630778692.600746 sending message 105 to peer 0x7f8d30008000 (19 bytes) 1630778692.600751 sending message 105 to peer 0x7f8d30008000 (20 bytes) 1630778692.600755 sending message 105 to peer 0x7f8d30008000 (22 bytes) 1630778692.600760 sending message 105 to peer 0x7f8d30008000 (20 bytes) 1630778692.600764 sending message 105 to peer 0x7f8d30008000 (25 bytes) 1630778692.600769 sending message 105 to peer 0x7f8d30008000 (57 bytes) 1630778692.600794 sending message 105 to peer 0x7f8d30008000 (18 bytes) 1630778692.600799 sending message 105 to peer 0x7f8d30008000 (19 bytes) 1630778692.600804 sending message 105 to peer 0x7f8d30008000 (21 bytes) 1630778692.600808 sending message 105 to peer 0x7f8d30008000 (61 bytes) 1630778692.600812 sending message 105 to peer 0x7f8d30008000 (32 bytes) 1630778692.600817 sending message 105 to peer 0x7f8d30008000 (8 bytes) 1630778692.600822 sending message 105 to peer 0x7f8d30008000 (27 bytes) 1630778692.600827 sending message 105 to peer 0x7f8d30008000 (35 bytes) 1630778692.600832 sending message 105 to peer 0x7f8d30008000 (11 bytes) 1630778692.600855 sending message 105 to peer 0x7f8d30008000 (8 bytes) 1630778692.600859 sending message 105 to peer 0x7f8d30008000 (32 bytes) 1630778692.600863 sending message 105 to peer 0x7f8d30008000 (31 bytes) 1630778692.600867 sending message 105 to peer 0x7f8d30008000 (34 bytes) 1630778692.600870 sending message 105 to peer 0x7f8d30008000 (16 bytes) 1630778692.600874 sending message 105 to peer 0x7f8d30008000 (42 bytes) 1630778692.600877 sending message 105 to peer 0x7f8d30008000 (14 bytes) 1630778692.600881 sending message 105 to peer 0x7f8d30008000 (9 bytes) 1630778692.600885 sending message 105 to peer 0x7f8d30008000 (10 bytes) 1630778692.600890 sending message 105 to peer 0x7f8d30008000 (28 bytes) 1630778692.600894 sending message 105 to peer 0x7f8d30008000 (31 bytes) 1630778692.600899 sending message 105 to peer 0x7f8d30008000 (32 bytes) 1630778692.600903 sending message 105 to peer 0x7f8d30008000 (29 bytes) 1630778692.600908 sending message 105 to peer 0x7f8d30008000 (55 bytes) 1630778692.600912 sending message 105 to peer 0x7f8d30008000 (108 bytes) 1630778692.600918 sending message 105 to peer 0x7f8d30008000 (61 bytes) 1630778692.600922 sending message 105 to peer 0x7f8d30008000 (61 bytes) 1630778692.600926 sending message 105 to peer 0x7f8d30008000 (57 bytes) 1630778692.600936 sending message 105 to peer 0x7f8d30008000 (30 bytes) 1630778692.600941 sending message 105 to peer 0x7f8d30008000 (49 bytes) 1630778692.600945 sending message 105 to peer 0x7f8d30008000 (44 bytes) 1630778692.600950 sending message 105 to peer 0x7f8d30008000 (74 bytes) 1630778692.600954 sending message 105 to peer 0x7f8d30008000 (110 bytes) 1630778692.600959 sending message 105 to peer 0x7f8d30008000 (26 bytes) 1630778692.600963 sending message 105 to peer 0x7f8d30008000 (22 bytes) 1630778692.600968 sending message 105 to peer 0x7f8d30008000 (519 bytes) 1630778692.600973 sending message 105 to peer 0x7f8d30008000 (22 bytes) 1630778692.600980 sending message 106 to peer 0x7f8d30008000 (0 bytes) 1630778692.600998 cmd_pack_argv: argv[0]=new 1630778692.601008 sending message 200 to peer 0x7f8d30008000 (8 bytes) 1630778692.601013 client loop enter 1630778692.601120 client_signal: Child exited: 20 1630778692.673021 peer 0x7f8d30008000 message 207 1630778692.673035 sending message 208 to peer 0x7f8d30008000 (0 bytes)

closed time in 14 days

sdondley