Quote from: rnglab on October 15, 2015, 02:38:57 am

witness "1.6.33" is back, sorry for the delay

Update: failover script based on update_witness didn't work because witness_node process died on both servers after the fork. Checking logs now

My newest version of failover script should restart witness_node and cli_wallet in case of crash, or witness production falling below 50%.  Unlock the wallet, and switch signing keys if blocks are missed.  The first 3 times it restarts it will attempt a --replay-blockchain to get back on a majority fork.  If that doesn't work it will try a --resync-blockchain.

At least thats what I expect it to do.  I still need to test it a bit more.

Quote from: rnglab on October 09, 2015, 06:29:03 am

Quote from: bitsacer on October 08, 2015, 10:00:19 am

I started on the light wallet's translation , but I I need to be able to see the words in the context . Some of them might sound ridiculous when translated out of context.   Is there any way to see the results - like a preview mode. thanks

Hi @bitsacer you mean the web wallet?  graphene-ui project on transifex? If thats you, great work : )
I've reviewed Turkish translation and created a pull request on github, we should see Turkish languate on graphene.bitshares.org on next update (you might have to clear your browser cache to see it)

As for being able to see the words in context, I could fork graphene-ui with transifex translations included, and deploy it on a vps running a local testnet. But I think I can use those resources and time on other tasks because graphene-ui development is going pretty fast and we will see Turkish language on graphene.bitshares.org pretty soon. Then you check your translation in context and modify whatever you want on transifex to be applied on the  next update. That's how I'm doing the Spanish translation.

Let me know if I can help you.

Hi , yes that's me . An update would be really great, then I can go over it and check it once more to make sure everything sounds right. Thanks

Quote from: rnglab on October 10, 2015, 10:27:08 am

just removed InBTC and works great : )

Wonderful!

Regarding the yunbi error, have you tried contacting them to request for an unban of your ip?  Their contact - https://yunbi.com/documents/contact

Quote from: xeroc on October 10, 2015, 10:11:22 am

Quote from: cube on October 10, 2015, 09:58:28 am

There is another error on 'config.minValidAssetPrice'.  It should not be because this variable should be in config.py.  There may be a syntax error in your config.py Have you checked it?  Can you post it here?

I renamed that variable to make clear its in BTC .. please update your config file

thank you both. this is my config.py

Code: [Select]

################################################################################
## RPC-client connection information (required)
################################################################################
host   = "localhost"
port   = 8092
user   = ""
passwd = ""
unlock = ""

################################################################################
## Delegate Feed Publish Parameters
################################################################################
delegate_list            = ["bitshares-argentina"]
maxAgeFeedInSeconds      = 60*60 # 1hour

################################################################################
## Fine tuning
################################################################################
discount                 = 0.995
core_exchange_factor     = 1.05 # 5% surplus if paying fees in bitassets

minValidAssetPriceInBTC  = 0.00001
change_min               = 0.5
## trust level for exchanges (if an exception happens and level is 0.8 script
##                            will quit with a failure)
btc38_trust_level        = 0.9
bter_trust_level         = 0.5
poloniex_trust_level     = 1.0
bittrex_trust_level      = 0.5
yunbi_trust_level        = 0.8

Quote from: rnglab on October 10, 2015, 09:39:06 am

Quote from: cube on October 10, 2015, 09:11:16 am

Quote from: Bhuz on October 10, 2015, 08:57:17 am

@cube

I modified the scrupt, and i get this output

Code: [Select]

[Starting Threads]: (poloniex)(yunbi)..Error in asset USD: no median for empty data
Error in asset BTC: no median for empty data
Update required! Forcing now!
publishing feeds for delegate: bhuz

But on the cli_wallet side there are no asset_publish_feed_operation in the account history, and the balance is always the same

The changes are not working.  I reverted to the original script and made the following changes instead.  This time it gets through.

You will need to revert to original script and apply the changes below.

Code: [Select]


Only disable bter

 mythreads["yahoo"]    = threading.Thread(target = fetch_from_yahoo)
 mythreads["yunbi"]    = threading.Thread(target = fetch_from_yunbi)
#mythreads["btc38"]    = threading.Thread(target = fetch_from_btc38)
 #mythreads["bter"]     = threading.Thread(target = fetch_from_bter)
 mythreads["poloniex"] = threading.Thread(target = fetch_from_poloniex)
 mythreads["bittrex"]  = threading.Thread(target = fetch_from_bittrex)
 mythreads["btcavg"]   = threading.Thread(target = fetch_bitcoinaverage)


under price feed, swap the lines involving the asset ids

                      "core_exchange_rate": {
                        "quote": {
                          "asset_id": "1.3.0",
                          "amount": int(denominator * 1.05) # 5% extra
                        },
                        "base": {
                          "asset_id": assets[asset]["id"],
                          "amount": numerator
                        }
                      }


I put up the modified copy here - http://pastebin.com/E9d60Htp

had to change delegate_name to delegate_list on config and add brackets.

throws an exception but seems to publish:

Code: [Select]

[Starting Threads]: (yahoo)USDUSD=X,EURUSD=X,CNYUSD=X
(bittrex)(yunbi)(btcavg)(poloniex)USD
1.0
EUR
1.1358
CNY
0.1576
USDEUR=X,EUREUR=X,CNYEUR=X
USD
0.8804
EUR
1.0
CNY
0.1387
USDCNY=X,EURCNY=X,CNYCNY=X
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.4/threading.py", line 920, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.4/threading.py", line 868, in run
    self._target(*self._args, **self._kwargs)
  File "pricefeeds.py", line 144, in fetch_from_poloniex
    if float(result["BTC_"+coin]["last"]) > config.minValidAssetPrice:
AttributeError: 'module' object has no attribute 'minValidAssetPrice'

USD
6.3467
EUR
7.2088
CNY
1.0
indices:

..
Error fetching results from yunbi! (HTTPSConnectionPool(host='yunbi.com', port=443): Max retries exceeded with url: /api/v2/tickers.json (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fe7479a8898>: Failed to establish a new connection: [Errno -2] Name or service not known',)))

...Error in this asset CNY: no median for empty data
Error in this asset BTC: no median for empty data
Error in this asset EUR: no median for empty data
Error in this asset USD: no median for empty data
Update required! Forcing now!
publishing feeds for delegate: bitshares-argentina

Your output error:

Code: [Select]

"Error fetching results from yunbi! (HTTPSConnectionPool(host='yunbi.com', port=443): Max retries exceeded with url: /api/v2/tickers.json (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fe7479a8898>: Failed to establish a new connection: [Errno -2] Name or service not known',)))"

It seems to be due to yunbi not accepting your IP due to too many retries (ie exceeded the number of connection attempts allowed by yunbi for any IP address).  Please try it after an hour or two so that yunbi allows for connection from your machine's IP.