archive snowblossom slack dev
prev 2018-06-16 next
2018-06-16 10:37:11
Rotonen
addresses do not drop out of the pool stats until the pool restarts?
2018-06-16 13:32:54
Fireduck
not even then
2018-06-16 13:33:55
Fireduck
they drop out after 5 blocks of shares
2018-06-16 13:45:55
Rotonen
kk, thank you
2018-06-16 14:42:42
Fireduck
PPLNS is the name of the scheme
2018-06-16 14:48:31
GitHub
minor adjustments cleanup prepare for master repo
2018-06-16 14:51:02
GitHub
[snowblossomcoin/snowblossom] #80 deployment reorg, common configs, new systemd impl
2018-06-16 14:53:19
Fireduck
@Clueless does that new config move the wallet or db location?
2018-06-16 14:53:55
Clueless
verifying
2018-06-16 14:55:46
Clueless
windows deployment had `wallet` linux (example configs had `wallets/mainnet/` new config is now `wallets`
2018-06-16 14:56:33
Clueless
-
2018-06-16 14:58:21
Clueless
windows: `db_path=snowdb` linux: `node_db/mainnet` new config is now `node_db/mainnet`
2018-06-16 14:58:58
Clueless
- linux: `pool_db/mainnet` new config: `pool_db/mainnet`
2018-06-16 15:00:28
Clueless
@Fireduck It means users might have to move things around a bit to get on the same schema. I'm not sure how to prevent that when cleaning up.
2018-06-16 15:01:28
Fireduck
Not worried about node db
2018-06-16 15:01:33
Fireduck
It can resync
2018-06-16 15:01:52
Fireduck
The wallet has the potential to be nightmare
2018-06-16 15:02:14
Fireduck
Can you make it just wallet?
2018-06-16 15:02:40
Fireduck
And that should allow our windows users to not freak out or accidentally lose funds
2018-06-16 15:02:51
Clueless
sure, sounds like a good idea.
2018-06-16 15:07:53
Clueless
@Fireduck The other thing to be aware of. `/example/deployment/build.sh` is what outputs the linux/windows release. The linux install scripts treat the **latest** github release attachment as the thing to install.
2018-06-16 15:53:22
Tyler Boone
@Fireduck, what is causing output like this: Jun 16, 2018 8:22:50 AM snowblossom.node.MemPool rebuildPriorityMap
2018-06-16 15:53:50
Tyler Boone
It's got to be some kind of reflection going on somewhere because there is no log or print statement like that
2018-06-16 15:56:02
Fireduck
Pretty sure you are wrong
2018-06-16 15:56:13
Fireduck
I recall writing that log line
2018-06-16 15:57:26
Tyler Boone
you know what
2018-06-16 15:57:37
Tyler Boone
I just realized I might be running a node that is like a month old...
2018-06-16 15:57:42
Tyler Boone
but looking at code that is current
2018-06-16 16:00:16
Fireduck
I could be wrong too
2018-06-16 16:03:43
Tyler Boone
same thing with this: Jun 16, 2018 9:01:56 AM snowblossom.lib.PowUtil calcNextTarget
2018-06-16 16:04:36
Tyler Boone
you know what... could be something in the logger...
2018-06-16 16:04:45
Fireduck
Ah, that is the context for the subsequent line
2018-06-16 16:05:15
Fireduck
If you want to fix logging that would be great
2018-06-16 16:05:30
Fireduck
The logging properties file does notging
2018-06-16 16:06:09
Tyler Boone
do you have an idea for how you want to manage "log this string" vs. "show this string to the user"?
2018-06-16 16:10:02
Fireduck
I'd be happy to have any log level control at all
2018-06-16 16:11:23
Fireduck
Here is what I want: All output is via logging api
2018-06-16 16:11:40
Fireduck
we have a config file that says snowblossom.* = info level
2018-06-16 16:12:00
Tyler Boone
OK. so maybe output to console INFO and above?
2018-06-16 16:12:10
Fireduck
and if someone things they might have a peering problem they could set snowblossom.peering to level finest
2018-06-16 16:12:22
Fireduck
assume info and above is usually output to console
2018-06-16 16:12:26
Fireduck
and that should be the default config
2018-06-16 16:13:22
Fireduck
in theory, the log config allows this but I can't get it to fing work
2018-06-16 16:13:51
Fireduck
LogSetup loads the config if set
2018-06-16 16:13:59
Fireduck
but I can't get it to actually change any behavior
2018-06-16 16:16:00
Tyler Boone
lol
2018-06-16 16:17:31
Fireduck
and we are somewhat tied to java.util.logging beccause that is what grpc and friends are outputting to
2018-06-16 16:17:36
Fireduck
and we want to silence that shit
2018-06-16 16:17:53
Fireduck
I guess we could silence java.util.logging and then use something else for our stuff
2018-06-16 16:18:01
Tyler Boone
I'm rather dissapointed with intellij to be honest
2018-06-16 16:18:19
Tyler Boone
ReSharper is so f-ing good. I was expecting similar
2018-06-16 16:39:59
Tyler Boone
I thought Microsoft's MSDN documentation was bad
2018-06-16 16:40:24
Tyler Boone
Oracle blows it out of the water (badness wise)
2018-06-16 16:40:37
Tyler Boone
it's like they want developers to hate Java
2018-06-16 17:04:41
Fireduck
The logging is a particular fucjstorn
2018-06-16 17:04:55
Fireduck
I am good with java and that shit still makes no sense
2018-06-16 17:11:06
Tyler Boone
I have it generating a log file with the lower log levels
2018-06-16 17:11:26
Tyler Boone
but I don't understand this FileHandler.count bullshit
2018-06-16 17:12:10
Fireduck
Is it my bullshit?
2018-06-16 17:12:22
Tyler Boone
no
2018-06-16 17:17:06
Tyler Boone
weird.. every time I start Node it generates 2 log files...
2018-06-16 17:23:16
Tyler Boone
OK, figured it out. had file size limit set too small
2018-06-16 17:48:16
GitHub
1. adding logging to file 2. improving log lines
2018-06-16 17:49:05
Tyler Boone
If one of you gets a chance, will you build a Windows release with that and send it to me
2018-06-16 17:49:43
Fireduck
I am at nordstroms
2018-06-16 17:49:54
Tyler Boone
no rush
2018-06-16 17:49:58
Tyler Boone
just whenever you get a change
2018-06-16 17:50:00
Tyler Boone
chance
2018-06-16 21:29:16
Clueless
@Tyler Boone Sure, I'll add it
2018-06-16 21:29:42
Clueless
the config and properties configs just need to be added to the example/deployment/snowblossom/ folder, and make sure the configs are modified to use it
2018-06-16 21:29:50
Clueless
and make sure it works on linux AND windows. :)
2018-06-16 22:04:36
Tyler Boone
I don't think you created that from my branch
2018-06-16 22:11:24
Clueless
@Tyler Boone Does the file logging interrupt console logging?
2018-06-16 22:11:37
Tyler Boone
no
2018-06-16 22:11:45
Fireduck
I only know about one branch and that is called master
2018-06-16 22:11:52
Tyler Boone
git pull
2018-06-16 22:12:22
Tyler Boone
git checkout tster/add-file-logging
2018-06-16 22:12:38
Tyler Boone
git pull
2018-06-16 22:13:17
Fireduck
fine
2018-06-16 22:16:26
Fireduck
it is one of those
2018-06-16 22:19:48
Tyler Boone
hmmm, it's missing logging.properties
2018-06-16 22:22:18
Tyler Boone
I thought this line would copy all the files in configs/: for i in configs/*; do awk 'sub("$", "\r")' "$i" > "$1/$i"; done
2018-06-16 22:23:45
Fireduck
awkward
2018-06-16 22:24:14
Tyler Boone
I don't know what example/configs vs example/deployment/configs is...
2018-06-16 22:24:58
Tyler Boone
example/depoyment/configs is some insanity
2018-06-16 22:25:02
Tyler Boone
pointer files?
2018-06-16 22:25:26
Tyler Boone
C:\Users\thboo\source\repos\snowblossom\snowblossom>type example\deployment\configs\client.conf ../../configs/client.conf
2018-06-16 22:25:36
Fireduck
yeah, symlinks
2018-06-16 22:26:11
Tyler Boone
they are text files
2018-06-16 22:26:28
Fireduck
on linux, they are symlinks
2018-06-16 22:32:53
Tyler Boone
OK, well I guess you'll have to add a symlink to logging.properties
2018-06-16 22:34:37
Tyler Boone
also, pull the latest commit
2018-06-16 22:34:50
Tyler Boone
and add a symlink and it should work
2018-06-16 22:44:37
Tyler Boone
we should probably change the release to include lib and all the lib requirements in a single jar, and then have each component in a separate jar and just add the big jar to the jarpath
2018-06-16 22:45:09
Tyler Boone
kind of silly that every jar is 29mb...
2018-06-16 22:45:30
Clueless
that's probably a nice idea.
2018-06-16 22:45:44
Fireduck
heh
2018-06-16 22:49:47
Tyler Boone
OK cools good
2018-06-16 22:50:41
Tyler Boone
wtf
2018-06-16 22:50:52
Tyler Boone
why is it using node_db instead of snowdb...
2018-06-16 22:51:12
Tyler Boone
bah
2018-06-16 22:53:04
Clueless
@Tyler Boone because before it was "snowdb" which isn't very clear or informative, especially when new db folders may show up.
2018-06-16 22:53:11
Clueless
In my case, `pool_db`
2018-06-16 22:53:23
Clueless
What's more. `node_db/mainnet`
2018-06-16 22:53:26
Tyler Boone
OK, this is by design then
2018-06-16 22:53:39
Clueless
ah, I didn't know. :)
2018-06-16 22:53:39
Fireduck
yeah, people might end up resyncing but it is fine
2018-06-16 22:53:47
Tyler Boone
might==>will
2018-06-16 22:53:55
Tyler Boone
that's fine
2018-06-16 22:54:00
Tyler Boone
just was unexpected
2018-06-16 22:54:08
Fireduck
sure
2018-06-16 22:54:44
Clueless
@Tyler Boone yeah What's worse is that my linux examples did `node_db/mainnet` and windows `snowdb` And the database doesn't differentiate between mainnet and testnet
2018-06-16 22:54:54
Tyler Boone
we should have a release notes or something I guess
2018-06-16 22:55:04
Clueless
great idea!
2018-06-16 22:55:15
Tyler Boone
otherwise there will be mass confusion
2018-06-16 22:55:16
Fireduck
especially if it just said "welcome to your doom"
2018-06-16 22:55:21
Tyler Boone
troof
2018-06-16 22:55:46
Fireduck
Other coins have fancy web sites and marketing budgets
2018-06-16 22:55:55
Clueless
@Tyler Boone also, I linked this earlier, but not sure you saw it. https://github.com/cluelessperson/snowblossom/wiki Want your opinions.
2018-06-16 22:55:57
Fireduck
We have torrent seeds hidden above microwaves
2018-06-16 22:56:03
Clueless
not everything is fully there yet, but it's taking shape.
2018-06-16 23:00:51
Tyler Boone
looks pretty good
2018-06-16 23:01:04
Tyler Boone
later we should add a page on tips to get the best hashrate
2018-06-16 23:01:54
Clueless
That will definitely go under "Further"
2018-06-16 23:02:11
Clueless
eh, maybe not. It is a FAQ thing too
2018-06-16 23:02:16
Clueless
we'll see
2018-06-16 23:02:31
Clueless
Any Release Note information?
2018-06-16 23:02:38
Clueless
runs to `git log`
2018-06-16 23:02:44
Tyler Boone
a FAQ can contain a link to a page for more details
2018-06-16 23:03:07
Clueless
that sounds sane
2018-06-16 23:04:38
Fireduck
lots of hate for issue 4
2018-06-16 23:04:39
Fireduck
Issue 4: Yes: 0, No: 91, Both: 0
2018-06-16 23:05:52
Clueless
might have to skip that or modify the config. Problem is I ran into trouble with people not understanding voting
2018-06-16 23:06:11
Clueless
```vote_yes=1,2,3 vote_no=4``` works very well
2018-06-16 23:06:22
Clueless
except now people are voting against 4
2018-06-16 23:06:54
Clueless
``` vote_yes=a,b,c vote_no=d ```
2018-06-16 23:06:56
Clueless
might work
2018-06-16 23:07:24
Fireduck
I like it
2018-06-16 23:07:38
Fireduck
SIP4 - save the kittens from drowning
2018-06-16 23:08:00
Clueless
like which option, skipping or example using letters instead
2018-06-16 23:08:05
Clueless
then it'll error if they don't read it
2018-06-16 23:08:08
Tyler Boone
in the quickstart
2018-06-16 23:08:25
Tyler Boone
you need to tell users how to figure out which is the current snowfield
2018-06-16 23:08:51
Clueless
I created an issue to **loudly** report the current snowfield in node.
2018-06-16 23:09:04
Clueless
but I can add to check the explorer for the `activated_field`
2018-06-16 23:09:19
Tyler Boone
actually, that's another good FAQ. "When will we be on snowfield x"
2018-06-16 23:09:27
Clueless
with each block too, not just end of sync
2018-06-16 23:09:43
Clueless
@Tyler Boone nice! I was linking people to the code map describing difficulty earlier. Will add
2018-06-16 23:10:19
Clueless
What else is going into 1.0.8 ?
2018-06-16 23:10:38
Fireduck
We should make 1.1.0 soon
2018-06-16 23:10:42
Fireduck
to include sip1
2018-06-16 23:12:33
Clueless
what block did sip1 pass?
2018-06-16 23:14:12
Fireduck
5250 or so
2018-06-16 23:14:17
Fireduck
not really sure
2018-06-16 23:18:46
GitHub
[snowblossomcoin/snowblossom] #81 logging improvements
2018-06-16 23:41:10
Clueless
here's what I got so far
2018-06-16 23:59:04
Fireduck
Fuck yeah, release notes