2018-10-23 01:56:41
@Clueless Arktika 1.4.0 said INFO: Error talking to mining pool: io.grpc.StatusRuntimeException: UNAVAILABLE: Channel shutdownNow invoked, but 1.2.0 is okay to mining
alistar
2018-10-23 02:01:37
1.4.0 arktika works fine for me
Fireduck
2018-10-23 02:02:32
So I dont know why it is happened. I must use 1.2.0 again.
alistar
2018-10-23 02:04:00
Sure nothing else is different?
Fireduck
2018-10-23 02:04:12
None of that network code has changed
Fireduck
2018-10-23 02:05:09
nothing different, same configure files? is configure files different between 1.20 and 1.4.0?
alistar
2018-10-23 02:07:57
Same config file?
Fireduck
2018-10-23 02:09:27
find error.
alistar
2018-10-23 02:09:45
I need update my Pool application.lol
alistar
2018-10-23 02:22:51
@alistar what pool are you connected to?
Clueless
2018-10-23 02:23:05
my own pool
alistar
2018-10-23 03:54:35
well, glad it is nothing I need to fix. :wink:
Fireduck
2018-10-23 15:27:01
@Joko I still like you but was just cleaning up perms
Fireduck
2018-10-23 15:30:24
Haha I like you too mate :smile:
Joko
2018-10-23 15:32:04
yeah, you had github commit access
Fireduck
2018-10-23 16:12:40
Damn, I should have abused my powers when I had my chance!
Joko
2018-10-23 16:20:19
So, nicely, you can use `cpulimit` to throttle your miner if you want, or perhaps an iolimit
Clueless
2018-10-23 17:06:32
@Rotonen I'm able to get 750+K mining in a VM, really not bad.
Clueless
2018-10-23 17:07:01
using `cpulimit` to throttle to `15%` for testnet nets me `Oct 23 10:06:30 vmsnow1 cpulimit[27821]: INFO: Mining rate: 19456.636/sec - at this rate 0.487 hours per block`
Clueless
2018-10-23 17:45:53
Anyone want to make a testnet faucet so I don't have to?
Fireduck
2018-10-23 17:46:12
My plan is to encourage people to use testnet to play with things (like the upcoming Android client)
Fireduck
2018-10-23 17:57:49
@Fireduck I´ll take the job
mjay
2018-10-23 17:58:56
@mjay awesome
Fireduck
2018-10-23 19:49:15
First step: Testnet explorer online.
http://testnet.snowblossom-explorer.org/
mjay
2018-10-23 19:49:54
awesome. Let me know when you want some testnet coin
Fireduck
2018-10-23 19:51:11
You can send me some: snowtest:varv2n46rmmf79n5etad2lw8flx758axx0gd4pum
mjay
2018-10-23 19:54:05
done
Fireduck
2018-10-23 19:56:12
thank you
mjay
2018-10-23 20:14:24
@Clueless rather use chrt if you want it to stay out of the way
Rotonen
2018-10-23 21:15:46
Is there a minimal length for snow addresses?
mjay
2018-10-23 21:16:10
not really
Fireduck
2018-10-23 21:16:29
if they end up with a bunch of zeros on the front the base32 form will be smaller
Fireduck
2018-10-23 21:16:45
What language are you working with? We can probably come up with a validator.
Fireduck
2018-10-23 21:16:51
C++
mjay
2018-10-23 21:17:09
I´ll just do some basic validation, should be fine
mjay
2018-10-23 21:17:20
cool
Fireduck
2018-10-23 21:17:27
the send will reject it if it is nonsense
Fireduck
2018-10-23 21:17:30
so whatever
Fireduck
2018-10-23 21:18:05
contains only base32, is 40 chars or shorter, it should be fine
mjay
2018-10-23 21:18:20
snowtest: removed before test
mjay
2018-10-23 21:18:50
the address can be valid with snowtest: on the front or not
Fireduck
2018-10-23 21:19:07
when presenting anything to a user, you should always have snowtest: on
Fireduck
2018-10-23 21:19:09
for clarity
Fireduck
2018-10-23 21:19:37
I remove it before the check if its present, and always send it without to the node
mjay
2018-10-23 21:20:14
cool. I'm just saying you can send to the node either way.
Fireduck
2018-10-23 21:42:31
here we go, faucet is running. http://testnet.snowblossom-explorer.org/
mjay
2018-10-23 21:43:07
5 testsnow each time
mjay
2018-10-23 21:49:40
1) awesome
Fireduck
2018-10-23 21:49:44
2) I've filled it up more
Fireduck
2018-10-23 21:50:03
thanks
mjay
2018-10-23 21:50:22
once it drops below 1k snow a miner will start
mjay
2018-10-23 21:51:17
that is fancy
Fireduck
2018-10-23 21:54:16
cronjobs are
Rotonen
2018-10-23 21:56:13
hey, that is like an if statement and something to not spawn a new one each time the job runs (presumably)
Fireduck
2018-10-23 21:56:23
and maybe even some mechanism to turn it off when not needed
Fireduck
2018-10-23 21:56:25
so fancy
Fireduck
2018-10-23 21:58:12
its a simple cronjob. Every 15 minutes: kill the miner (nothing happens if none is running), and start a new one if balance < 1000
mjay
2018-10-23 21:59:49
still untested, so I expect it to be broken
mjay
2018-10-23 21:59:58
not even doing a sigterm timeout dance?
Rotonen
2018-10-23 22:00:34
I like it, it has a certain brutal efficency
Fireduck
2018-10-23 22:01:08
walk into room. Shoot one foot above guard desk. If a guard is required, call temp agency for a new one.
Fireduck
2018-10-23 22:01:45
efficient shooting using SIGTERM
mjay
2018-10-23 22:02:11
SIGKILL sounded a little harsh
mjay
2018-10-23 22:40:20
@mjay no i mean handling the fact signal sending is blocking
Rotonen
2018-10-23 22:46:07
you mean, waiting until the process stops?
mjay
2018-10-23 22:54:41
in general handling an indefinite stall upon SIGTERM
Rotonen
2018-10-23 22:55:32
I just added another SIGKILL 5 seconds after the SIGTERM
mjay
2018-10-23 22:56:47
how does the script get there if the kill is blocking
Rotonen
2018-10-23 22:57:13
It never happened to me that a kill blocks
mjay
2018-10-23 22:58:23
seems you mostly deal with well behaving well written software
Rotonen
2018-10-23 22:58:53
how can you get it to block?
mjay
2018-10-23 23:00:05
I had processes that catch sigterm and ignore it, zombies, cuda-processes with gpu crashed (ignoring even sigkill)
mjay
2018-10-23 23:00:19
but kill never blocked (so far)
mjay
2018-10-23 23:00:36
i'm sorta paranoid on that sorta unixy stuff, so i use fancy bells and whistles the kernel gives me to decide my course of action, like
https://lwn.net/Articles/288056/ Like most versions of Unix, Linux has two fundamental ways in which a process can be put to sleep. A process which is placed in the TASK_INTERRUPTIBLE state will sleep until either (1) something explicitly wakes it up, or (2) a non-masked signal is received. The TASK_UNINTERRUPTIBLE state, instead, ignores signals; processes in that state will require an explicit wakeup before they can run again.
Rotonen
2018-10-23 23:02:07
i think you can also get a file descriptor on the signal you've sent these days, but that's too new for me
Rotonen
2018-10-23 23:04:59
@mjay if you want to implement a test program for yourself, see this
https://cr.yp.to/docs/selfpipe.html
seek out the classic book, and misimplement the example
Rotonen
2018-10-23 23:06:16
From Mr. Bernstein, nice
mjay
2018-10-23 23:24:51
Those old unix books are fun to read and experiment with
mjay
2018-10-23 23:28:01
yeah, funny how that parallels with dusty magic tomes for wizardry
Rotonen
2018-10-23 23:30:21
I like that djb posts on the post quantum mailing list I'm on
Fireduck
2018-10-23 23:30:41
I just watch, no real clue what those guys are on about
Fireduck
2018-10-23 23:32:17
what mailing list is this?
mjay
2018-10-23 23:32:53
i'm assuming https://csrc.nist.gov/projects/post-quantum-cryptography/email-list
Rotonen
2018-10-23 23:33:34
Yep
Fireduck
2018-10-23 23:35:00
Watching with an eye towards adding winners to snowblossom
Fireduck
2018-10-23 23:35:29
Nice, joined
mjay
2018-10-23 23:35:53
but yeah, people with a lifetime of experience in this stuff debating how to deal with unknown unknowns is probably... dense
Rotonen
2018-10-23 23:41:28
hehe
Fireduck
2018-10-23 23:41:29
it is
Fireduck
2018-10-23 23:49:01
There was some brilliant shade last week
Fireduck
2018-10-23 23:49:18
Someone announced an attack on one of the candidates
Fireduck
2018-10-23 23:49:43
DJB came back a few days later saying the attack had no merit.
Fireduck
2018-10-23 23:49:56
:fire:
Fireduck
2018-10-23 23:54:51
Its really impressive to read through these papers, barely understanding it, and to know someone came up with this stuff
mjay
2018-10-23 23:55:42
Specialization is great
Fireduck
2018-10-23 23:56:07
Those folks are specialist in that area
Fireduck
2018-10-23 23:58:27
I specialize in doing dumb things with hashed tries
Fireduck