@Protovist snooping in db?
Special is the table used for single object entries
@Fireduck, you around?
[snowblossomcoin/snowblossom] #78 add vote tally page
Yes
I am seeing this insane behavior in my local shackleton
where it drops every other request
I'm guessing the connection is getting lost
and the browser has to kill it
I did the voting work last night
lol
The explorer has it right now
indeed
just for the record the first vote was block height 4936
anyways, have you seen anything like that with the explorer?
I'm guessing it's something stupid with the WebServer class
Nope
Would look but have screaming child
I mean, if you haven't seen it you aren't going to start getting it now
it's probably something weird on my machine
alright, ttyl
Wouldn't rule out anything
@Clueless you could add the block remarks to the block announcer bots
@Rotonen Is there a method to query for it? Right now I just have that parse logoutput
So I've gone so far as to convert to msdos style line endings in the deployment build
Should we make windows users figure out something like notepad++, or should I be bothering making thier configs notepad configurable? -_-;
i recommend to use dos2unix for that sort of stuff, it can do very many things
`for i in configs/*; do awk 'sub("$", "\r")' "$i" > "$1/$i"; done`
@Clueless dunno, but the block explorer does that, @Fireduck maybe shackleton should provide an atom feed?
they're working on it
and I can query node's for latest block, but I just didn't want to deploy any pythons stuff yet
@Fireduck Found a case where someone deleted their node database. They suggest it got stuck at starting peerage because it "tests all the peers" and there were simply too many that it'd be faster just to resync again lol
@Fireduck Also, I got up early and got tested my deployment stuff. I'd like your opinions. Changes. 1. Deploy.zip works for Windows AND Linux 2. Everyone starts with the same config files. https://github.com/cluelessperson/snowblossom/tree/master/example/deployment Results in: https://github.com/cluelessperson/snowblossom/releases/tag/1.0.8
NEXT is wiki changes
as you saw, same layout, minor changes
Finding a working peer time fixed in 1.0.7
sweet
I just want confirmation before pushing these changes to master.
I'll take a look in about an hour
it changes flow slightly and just prefer you guys be familiar instead of confused. take your time. :)
I dig it
but don't make a new release yet
I want to put in a few more things and then call that 1.1.0
@Fireduck That `1.0.8` is just a test of my fork. Several things to specifically note: 1. `auto_snow=false` by default (thoughts?) 2. Windows and Linux use the same confs/layout/directories/names 3. The file tree looks like this: ``` snowblossom-1.0.7-5-g09d3727 ├── client.bat ├── client.sh ├── cmd_here.bat ├── configs │ ├── client.conf │ ├── miner.conf │ ├── node.conf │ └── pool-miner.conf ├── miner.bat ├── miner-mem.bat ├── miner.sh ├── node.bat ├── node_db │ └── mainnet ├── node.sh ├── pool-miner.bat ├── PoolMiner_deploy.jar ├── pool-miner.sh ├── snow ├── SnowBlossomClient_deploy.jar ├── SnowBlossomMiner_deploy.jar ├── SnowBlossomNode_deploy.jar ├── systemd │ ├── snowblossom-miner.service │ └── snowblossom-node.service └── wallets ```
client.sh, client.bat, node.sh, node.bat, miner.sh, miner.bat, miner-mem.bat, pool-miner.sh, pool-miner.bat You can do `client.sh send` `client.bat send` from respective consoles.
auto_snow is the tool of satan
do those bat files with forward slashes work?
I clicked and started each of them, yes.
on windows?
yes
ok, cool
Helps miners generally. They don't have to go looking for an explorer to figure out what field we're on.
@Fireduck I think it's good to simplify the *Quickstart* into a global "1. 2. 3." (which my deployment changes do) but hitting a wall in determining what the *User Guide* should look like. * Tell them to always run a node * Examples of sending payments. * I imagine it should inform of the basic topology. (my earlier picture or similar)