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