Error while creating summary: Error: Trades not found

Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the getting help page for details.
I'm submitting a ...
[ ] bug report
[ ] question about the decisions made in the repository
Action taken (what you did)
Running live trader on development branch
Expected result (what you hoped would happen)
summary in log
Actual result (unexpected outcome)
2018-09-10 16:53:21 (DEBUG):    [ORDER] statusChange: OPEN
2018-09-10 16:53:23 (INFO):     [ORDER] partial buy fill, total filled: 39.7
2018-09-10 16:53:23 (DEBUG):    [ORDER] statusChange: FILLED
2018-09-10 16:53:25 (ERROR):    Error while creating summary: Error: Trades not found
at get (/home/username/gekko/exchange/wrappers/binance.js:366:23)
at checkFn (/home/username/gekko/exchange/exchangeUtils.js:23:16)
at /home/username/gekko/exchange/wrappers/binance.js:130:12
at Request.request [as _callback] (/home/username/gekko/exchange/node_modules/binance/lib/rest.js:100:21)
at Request.self.callback (/home/username/gekko/exchange/node_modules/request/request.js:185:22)
at Request.emit (events.js:182:13)
at Request. (/home/username/gekko/exchange/node_modules/request/request.js:1157:10)
at Request.emit (events.js:182:13)
at IncomingMessage. (/home/username/gekko/exchange/node_modules/request/request.js:1079:12)
at Object.onceWrapper (events.js:273:13)
at IncomingMessage.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1081:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
2018-09-10 16:54:56 (DEBUG):    Buy - Predicted variation:  0.8433171137867231
2018-09-10 17:03:05 (DEBUG):    syncing private data
2018-09-10 17:13:05 (DEBUG):    syncing private data
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

2018-09-14 10:56:09 (DEBUG):    Requested EOS/USDT trade data from Binance ...
2018-09-14 10:56:09 (DEBUG):    Processing 124 new trades. From 2018-09-14 08:55:49 UTC to 2018-09-14 08:56:09 UTC. (a few seconds)
2018-09-14 10:56:09 (INFO):     Trader Received advice to go long. Buying  EOS
isValidLot 10 true
2018-09-14 10:56:09 (DEBUG):    Creating order to buy 22.51082142515631 EOS
2018-09-14 10:56:16 (DEBUG):    [ORDER] statusChange: SUBMITTED
isValidLot 10 true
2018-09-14 10:56:16 (DEBUG):    [ORDER] statusChange: OPEN
2018-09-14 10:56:18 (INFO):     [ORDER] partial buy fill, total filled: 22.51
2018-09-14 10:56:18 (DEBUG):    [ORDER] statusChange: FILLED
2018-09-14 10:56:19 (ERROR):    Error while creating summary: Error: Trades not found
    at get (/home/gekko/gekko/exchange/wrappers/binance.js:366:23)
    at checkFn (/home/gekko/gekko/exchange/exchangeUtils.js:23:16)
    at /home/gekko/gekko/exchange/wrappers/binance.js:130:12
    at Request.request [as _callback] (/home/gekko/gekko/exchange/node_modules/binance/lib/rest.js:100:21)
    at Request.self.callback (/home/gekko/gekko/exchange/node_modules/request/request.js:185:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)
    at Request.<anonymous> (/home/gekko/gekko/exchange/node_modules/request/request.js:1157:10)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at IncomingMessage.<anonymous> (/home/gekko/gekko/exchange/node_modules/request/request.js:1079:12)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
2018-09-14 10:56:29 (DEBUG):    Requested EOS/USDT trade data from Binance ...
2018-09-14 10:56:29 (DEBUG):    Processing 166 new trades. From 2018-09-14 08:56:09 UTC to 2018-09-14 08:56:29 UTC. (a few seconds)
2018-09-14 10:56:49 (DEBUG):    Requested EOS/USDT trade data from Binance ...

And again.
@xbromy, did you find a solution?

This is all on binance, it seems. The same error message is also effecting gdax users (happens to me there about once every 200 trades).
This error comes from Gekko not being able to find the trade it just did. Some context:
Gekko trades by doing limit orders, it tells Binance please buy 10 BTC at X and Binance replies we accept you order and you can refer to it by this ID. After Gekko figures out the order is completed and 10 bitcoin is bought Gekko needs to figure out things like execution price (since it might have done multiple limit orders) and fees. However the only way to get this is to ask for all trades you did and match them with the limit orders we requested previously.
This error means that matching didn't work, there are 2 reasons for this:

Binance only provides your previous 1000 trades to you, so if you trade a lot (or big size) by the time Gekko gets around to asking about these trades they are not recent enough anymore. So not part of that list
Gekko thought the limit order was completed, but in reality it wasn't (as such there are no trades).

I am in the process of creating one big debug branch that everyone who has any problems on binance, gdax or kraken should run.

I pushed more logging around this situation: 7344410cb5a9c431cbe795b2c42a6e49f6bdc31e please run the latest develop and post more logs. I am running this non stop as well to see if I can reproduce it..

I'm now on 2271428aae6f568b8ce13f40dda38cc11172c833

@PhunkyBob
Thanks for those logs! This is a tough one to fix...
The list in the log is cut off but it's clear that the order Gekko was searching for was not in that list. This most likely means that the order was never filled (even though Gekko thought it was).
Just to make sure: Do you have any other trading things (or multiple gekkos) running on that binance account? This might be caused because someone cancelled an order that Gekko created and as such Gekko thought it was filled.
I pushed another commit that should give us even more debug information: 22fca69 because I am still not sure what the problem is..

When Gekko says

2018-09-19 20:58:19 (ERROR):    Error while creating summary: Error: Trades not found

the trade was however made and filled in my Binance account (and at the first attempt).
Here is my Binance order log:
https://i.imgur.com/fd5Pi8x.png
The latest order (21:16:16) was made by me (because à saw Gekko failed to make it), all the others were made by Gekko.
We can see that the long advice was made correctly.

@PhunkyBob thanks a lot for all the details. Do please run the latest develop as it might show more debug output when the situation is happening.
I'm not sure whether this is a problem with Gekko or binance, as such I asked in their API support chat:

I'm now on 22fca6928a85ca407438338dbfb83ec94dff5bc1

2018-09-20 22:31:09 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-20 22:31:09 (DEBUG):    Processing 187 new trades. From 2018-09-20 20:30:49 UTC to 2018-09-20 20:31:08 UTC. (a few seconds)
2018-09-20 22:31:09 (INFO):     Trader Received advice to go long. Buying  XRP
isValidLot 10 true
2018-09-20 22:31:09 (DEBUG):    Creating order to buy<PHONE_NUMBER>944301 XRP
2018-09-20T20:31:14.852Z 'sticky create' 'buy'
2018-09-20 22:31:14 (DEBUG):    [ORDER] statusChange: SUBMITTED
isValidLot 10 true
2018-09-20 22:31:15 (DEBUG):    [ORDER] statusChange: OPEN
2018-09-20 22:31:17 (INFO):     [ORDER] partial buy fill, total filled: 304.8
2018-09-20 22:31:17 (DEBUG):    [ORDER] statusChange: FILLED
cannot find trades! { order: '21040740',
  list:
   [ 21019478,
     21010462,
     20859904,
     20859904,
     20855636,
     20638354,
     20626447,
     20626447,
     20509106,
     20492314,
     20492314,
     20462192,
     20425584,
     20408332,
     20408269,
     20398710,
     20388622,
     20352261,
     20341643,
     20339775,
     20209144,
     20209144,
     19976305,
     19066903,
     19047973,
     16327174,
     16209927,
     16209927,
     16209927,
     15908193,
     15908083,
     15891130,
     15891130,
     15694017,
     15693493,
     15687248,
     15687248,
     15640172,
     15640172,
     15602650,
     15600338,
     15591280,
     15590273,
     15590235,
     15590235,
     15590089,
     15553296,
     15516879,
     15308756,
     15308756,
     15290039,
     15290039,
     15281705,
     15281081,
     15278861,
     15272568,
     15270400,
     15270400,
     15254821,
     15236591,
     15235188,
     15068068,
     15012292,
     14932112,
     14932112,
     14857005,
     14658271,
     14656647,
     14654033,
     14654033,
     14646295,
     14641657,
     14641630,
     14640644,
     14504037,
     14504037,
     14503304,
     14413157,
     14407172,
     14197569,
     14160562,
     14160479,
     14160479,
     14160479,
     14139236,
     14136087,
     14136087,
     14117288,
     14079516,
     14079516,
     14053783,
     14002131,
     14002131,
     14002131,
     14002131,
     13963651,
     13610498,
     13578328,
     12881046,
     12872316,
     ... 9 more items ] }
couldnt find any trade for order, here is order: { err: null,
  resp:
   { symbol: 'XRPUSDT',
     orderId: 21040740,
     clientOrderId: '2TyFpfxjvK3tQDwVy7Mu90',
     price: '0.40651000',
     origQty: '304.80000000',
     executedQty: '0.00000000',
     cummulativeQuoteQty: '0.00000000',
     status: 'NEW',
     timeInForce: 'GTC',
     type: 'LIMIT',
     side: 'BUY',
     stopPrice: '0.00000000',
     icebergQty: '0.00000000',
     time:<PHONE_NUMBER>034,
     updateTime:<PHONE_NUMBER>034,
     isWorking: true } }
2018-09-20 22:31:19 (ERROR):    Error while creating summary: Error: Trades not found
    at binance.queryOrder (/home/gekko/gekko/exchange/wrappers/binance.js:356:19)
    at Request.request [as _callback] (/home/gekko/gekko/exchange/node_modules/binance/lib/rest.js:100:21)
    at Request.self.callback (/home/gekko/gekko/exchange/node_modules/request/request.js:185:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)
    at Request.<anonymous> (/home/gekko/gekko/exchange/node_modules/request/request.js:1157:10)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at IncomingMessage.<anonymous> (/home/gekko/gekko/exchange/node_modules/request/request.js:1079:12)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
2018-09-20 22:31:29 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-20 22:31:30 (DEBUG):    Processing 188 new trades. From 2018-09-20 20:31:09 UTC to 2018-09-20 20:31:29 UTC. (a few seconds)
2018-09-20 22:31:49 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-20 22:31:49 (DEBUG):    Processing 95 new trades. From 2018-09-20 20:31:30 UTC to 2018-09-20 20:31:48 UTC. (a few seconds)
2018-09-20 22:32:09 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-20 22:32:09 (DEBUG):    Processing 60 new trades. From 2018-09-20 20:31:50 UTC to 2018-09-20 20:32:08 UTC. (a few seconds)
2018-09-20 22:32:29 (DEBUG):    Requested XRP/USDT trade data from Binance ...
.
.
.
2018-09-20 23:30:50 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-20 23:30:50 (DEBUG):    Processing 51 new trades. From 2018-09-20 21:30:30 UTC to 2018-09-20 21:30:50 UTC. (a few seconds)
2018-09-20 23:31:10 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-20 23:31:10 (DEBUG):    Processing 58 new trades. From 2018-09-20 21:30:51 UTC to 2018-09-20 21:31:08 UTC. (a few seconds)
2018-09-20 23:31:10 (INFO):     Received advice to sell however Gekko is already in the process to buy
2018-09-20 23:31:10 (INFO):     Canceling buy order first
(node:18409) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated.
2018-09-20 23:31:30 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-20 23:31:30 (DEBUG):    Processing 108 new trades. From 2018-09-20 21:31:10 UTC to 2018-09-20 21:31:29 UTC. (a few seconds)
2018-09-20 23:31:50 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-20 23:31:50 (DEBUG):    Processing 55 new trades. From 2018-09-20 21:31:31 UTC to 2018-09-20 21:31:49 UTC. (a few seconds)
2018-09-20 23:32:10 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-20 23:32:10 (DEBUG):    Processing 111 new trades. From 2018-09-20 21:31:50 UTC to 2018-09-20 21:32:09 UTC. (a few seconds)

Again, the order is however made in Binance.

Hi Guys,
I got the same issue last night too... caused me to miss out on a couple of good trades as all future trades get the "ignoring advice, already in process to Buy" which is kinda frustrating..
I'm going to launch my own investigation.. but below is my log output. Hopefully helpful to someone?
I'm running latest Develop branch at commit "[GB] add more debug information on binance trade match fail, see #2518"
`2018-09-21 15:42:02 (INFO):        --- BUY --- 0.08391 2018-09-21T15:36:00Z
2018-09-21 15:42:02 (INFO):                 MEH
2018-09-21 15:42:02 (INFO):         Biggest Drop was.. 1.2952469064415517
2018-09-21 15:42:02 (INFO):        bbLongDegs 35.26301172960844
2018-09-21 15:42:02 (INFO):        ma1000Degs 15.692328522818876
2018-09-21 15:42:02 (INFO):                 BBUpper0.0911 BBMiddle0.0879 BBLow0.0846
2018-09-21 15:42:02 (INFO):        Trader Received advice to go long. Buying  ADA
isValidLot 10 true
2018-09-21 15:42:02 (DEBUG):        Creating order to buy 37999.21509270051 ADA
{"status":1,"request":"4168b3c2-777c-40f4-bed9-fc4be3bf5a4c"}
2018-09-21 15:42:05 (INFO):        Send advice via email.
2018-09-21T15:42:07.204Z 'sticky create' 'buy'
2018-09-21 15:42:07 (DEBUG):        [ORDER] statusChange: SUBMITTED
isValidLot 10 true
2018-09-21 15:42:07 (DEBUG):        [ORDER] statusChange: OPEN
2018-09-21 15:42:08 (INFO):        [ORDER] partial buy fill, total filled: 37999.2
2018-09-21 15:42:08 (DEBUG):        [ORDER] statusChange: FILLED
cannot find trades! { order: '25861199',
list:
[ 25822337,
25822322,
25794791,
25794791,
25794763,
25794763,
25794763,
25794763,
25794763,
25636962,
25622818,
25622818,
25622818,
25585628,
25585486,
25585439,
25585439,
25585439,
25585439,
25585439,
25585439,
25501167,
25501167,
25501167,
25501110,
25501110,
25501110,
25428663,
....
....
23802117,
23802117,
23767173,
... 405 more items ] }
couldnt find any trade for order, here is order: { err: null,
resp:
{ symbol: 'ADAUSDT',
orderId: 25861199,
clientOrderId: 'g27VyOPTF8GGatZlfx7D4v',
price: '0.08379000',
origQty: '37999.20000000',
executedQty: '0.00000000',
cummulativeQuoteQty: '0.00000000',
status: 'NEW',
timeInForce: 'GTC',
type: 'LIMIT',
side: 'BUY',
stopPrice: '0.00000000',
icebergQty: '0.00000000',
time:<PHONE_NUMBER>269,
updateTime:<PHONE_NUMBER>269,
isWorking: true } }
2018-09-21 15:42:11 (ERROR):        Error while creating summary: Error: Trades not found
at binance.queryOrder (/home/richard/bitbucket/gekko-0-6/exchange/wrappers/binance.js:356:19)
at Request.request [as _callback] (/home/richard/bitbucket/gekko-0-6/exchange/node_modules/binance/lib/rest.js:100:21)
at Request.self.callback (/home/richard/bitbucket/gekko-0-6/exchange/node_modules/request/request.js:185:22)
at emitTwo (events.js:126:13)
at Request.emit (events.js:214:7)
at Request. (/home/richard/bitbucket/gekko-0-6/exchange/node_modules/request/request.js:1157:10)
at emitOne (events.js:116:13)
at Request.emit (events.js:211:7)
at IncomingMessage. (/home/richard/bitbucket/gekko-0-6/exchange/node_modules/request/request.js:1079:12)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:111:20)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
2018-09-21 15:42:22 (DEBUG):        Requested ADA/USDT trade data from Binance ...
2018-09-21 15:42:22 (DEBUG):        Processing 43 new trades. From 2018-09-21 15:42:02 UTC to 2018-09-21 15:42:21 UTC. (a few seconds)
.... a long time later....
2018-09-21 15:48:02 (INFO):        --- SELL --- 0.08205 2018-09-21T15:42:00Z
2018-09-21 15:48:02 (INFO):                 Meh going wrong way
2018-09-21 15:48:02 (DEBUG):                 Sale INFO -2.2669104204753205%
2018-09-21 15:48:02 (DEBUG):                 C0.08205
2018-09-21 15:48:02 (INFO):        Received advice to sell however Gekko is already in the process to buy
2018-09-21 15:48:02 (INFO):        Canceling buy order first
{"status":1,"request":"d5fe8759-9de0-4288-9003-6bef3f0ab040"}
..................
2018-09-21 15:54:02 (INFO):        --- BUY --- 0.08277 2018-09-21T15:48:00Z
2018-09-21 15:54:02 (INFO):                 MEH
2018-09-21 15:54:02 (INFO):         Biggest Drop was.. 0
2018-09-21 15:54:02 (INFO):        bbLongDegs 22.496471500212326
2018-09-21 15:54:02 (INFO):        ma1000Degs 14.369066254838387
2018-09-21 15:54:02 (INFO):                 BBUpper0.0918 BBMiddle0.0873 BBLow0.0828
2018-09-21 15:54:02 (INFO):        ignoring advice: already in the process to buy
{"status":1,"request":"91b560d8-c661-4bf1-b769-33f189825a00"}
2018-09-21 15:54:04 (INFO):        Send advice via email.
2018-09-21 15:54:22 (DEBUG):        Requested ADA/USDT trade data from Binance ...
........................
2018-09-21 16:36:22 (INFO):        --- SELL --- 0.0839 2018-09-21T16:30:00Z
2018-09-21 16:36:22 (INFO):                 End of Big Trend, its now going down!
2018-09-21 16:36:22 (DEBUG):                 Sale INFO 1.3468414779499476%
2018-09-21 16:36:22 (DEBUG):                 C0.0839
2018-09-21 16:36:22 (INFO):        ignoring advice: already cancelling previous buy order
{"status":1,"request":"2ded6a04-ec0b-44c8-b533-510fa105a167"}
2018-09-21 16:36:25 (INFO):        Send advice via email.
2018-09-21 16:36:34 (DEBUG):        syncing private data
2018-09-21 16:36:42 (DEBUG):        Requested ADA/USDT trade data from Binance ...
2018-09-21 16:36:42 (DEBUG):        Processing 4 new trades. From 2018-09-21 16:36:22 UTC to 2018-09-21 16:36:42 UTC. (a few seconds)
2018-09-21 16:37:02 (DEBUG):        Requested ADA/USDT trade data from Binance ...
`

@askmike  Perhaps this is a rounding issue?
Creating order to buy 37999.21509270051
...
[ORDER] partial buy fill, total filled: 37999.2

Ok been doing some further investigation... (it's probably not a rounding issue..)
For my example the orderId 25861199 definitely exists and was filled quickly without any cancels and retries on the exchange.
I'm not much of a Node.js developer but from what I can see we were trying to check the order exists in a list of order ids but the response from Binance didn't contain this orderID in the array of responses. My guess is that Binance was under load (trade volumes are quite high right now) and the response from binance was cached or hadn't updated yet. (Just a guess.. this is hard to prove!).
Looking at exchange/wrappers/binance.js Lines 404-405
  const handler = cb => this.binance.myTrades(reqData, this.handleResponse('getOrder', cb));
  retry(undefined, handler, get);

We have a retry function, but the checkFn "handler" we pass through doesn't have any checking that the order ID we are wanting actually exists? Can we somehow add this check into the handler? So if the order Id we are looking for doesn't return we retry the request to the exchange X number of times before we just fail?
Also as this causes all future trades to fail. I think we need to email an alert in this situation so we can come and investigate / restart gekko. Gekko shouldn't just continue like nothing is wrong.

@PhunkyBob @rkingy I know why the error is happening now:

Gekko creates an order
Gekko checks the order and thinks it's filled
Gekko tried to get fill information

However 2. is wrong in your cases! The extra logs show that the order wasn't filled at all when Gekko tripped. So while it might be that your binance account shows the order was filled, it wasn't when Gekko tried to get fill information yet!

We have a retry function, but the checkFn "handler" we pass through doesn't have any checking that the order ID we are wanting actually exists? Can we somehow add this check into the handler? So if the order Id we are looking for doesn't return we retry the request to the exchange X number of times before we just fail?

Thanks Mike.! I'll pull that update down and give it a whirl...

Thank you @askmike !
Updating 22fca69..d676a6e
I hope one day it would be possible to make market orders (they are filled faster).

It's weird.
This night the bot took a trade with amount not even near the expected value.
At 2018-09-22 22:39:13, the close was at 0.57303 and the strategy advised a long.
But the bot created the order at 0.57604.
At 2018-09-23 01:36:16, the close was at 0.57975 and the strategy advised a short.
But the bot created the order at 0.57355.
I expected from 0.57303 to 0.57975 (+1%) I had 0.57604 to 0.57355 (-0.5%).
Usually, when the strategy advised at a price, the order was created at this price. I don't say it's always filled, but at least it's created.
This time it was not even created at the correct price.
2018-09-22 22:38:13 (DEBUG):    Processing 98 new trades. From 2018-09-22 20:37:53 UTC to 2018-09-22 20:38:13 UTC. (a few seconds)
2018-09-22 22:38:33 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-22 22:38:34 (DEBUG):    Processing 40 new trades. From 2018-09-22 20:38:14 UTC to 2018-09-22 20:38:33 UTC. (a few seconds)
2018-09-22 22:38:53 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-22 22:38:54 (DEBUG):    Processing 87 new trades. From 2018-09-22 20:38:34 UTC to 2018-09-22 20:38:53 UTC. (a few seconds)
2018-09-22 22:39:13 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-22 22:39:13 (DEBUG):    Processing 68 new trades. From 2018-09-22 20:38:53 UTC to 2018-09-22 20:39:13 UTC. (a few seconds)
2018-09-22 22:39:13 (DEBUG):    -->long @ 0.57303
2018-09-22 22:39:13 (INFO):     Trader Received advice to go long. Buying  XRP
2018-09-22 22:39:13 (DEBUG):    Creating order to buy<PHONE_NUMBER>6671723 XRP
2018-09-22T20:39:18.922Z 'sticky create' 'buy'
2018-09-22 22:39:18 (DEBUG):    [ORDER] statusChange: SUBMITTED
2018-09-22 22:39:19 (DEBUG):    [ORDER] statusChange: OPEN
2018-09-22 22:39:22 (DEBUG):    [ORDER] statusChange: MOVING
2018-09-22 22:39:22 (DEBUG):    [ORDER] statusChange: OPEN
2018-09-22 22:39:24 (DEBUG):    [ORDER] statusChange: MOVING
2018-09-22 22:39:25 (INFO):     [ORDER] partial buy fill, total filled: 193.3
2018-09-22 22:39:25 (DEBUG):    [ORDER] statusChange: FILLED
2018-09-22 22:39:26 (INFO):     [ORDER] summary: { price: 0.57604,
  amount: 193.3,
  date: moment("2018-09-22T22:39:25.007"),
  side: 'buy',
  orders: 1,
  fees: { XRP: 0.1933 },
  feePercent: 0.1 }
2018-09-22 22:39:26 (DEBUG):    syncing private data
2018-09-22 22:39:33 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-22 22:39:33 (DEBUG):    Processing 56 new trades. From 2018-09-22 20:39:13 UTC to 2018-09-22 20:39:32 UTC. (a few seconds)
2018-09-22 22:39:53 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-22 22:39:54 (DEBUG):    Processing 22 new trades. From 2018-09-22 20:39:34 UTC to 2018-09-22 20:39:49 UTC. (a few seconds)
2018-09-22 22:40:13 (DEBUG):    Requested XRP/USDT trade data from Binance ...
.
.
.
2018-09-23 01:34:56 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-23 01:34:56 (DEBUG):    Processing 65 new trades. From 2018-09-22 23:34:36 UTC to 2018-09-22 23:34:56 UTC. (a few seconds)
2018-09-23 01:35:16 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-23 01:35:16 (DEBUG):    Processing 61 new trades. From 2018-09-22 23:34:56 UTC to 2018-09-22 23:35:16 UTC. (a few seconds)
2018-09-23 01:35:36 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-23 01:35:36 (DEBUG):    Processing 110 new trades. From 2018-09-22 23:35:17 UTC to 2018-09-22 23:35:36 UTC. (a few seconds)
2018-09-23 01:35:56 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-23 01:35:56 (DEBUG):    Processing 221 new trades. From 2018-09-22 23:35:36 UTC to 2018-09-22 23:35:56 UTC. (a few seconds)
2018-09-23 01:36:16 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-23 01:36:16 (DEBUG):    Processing 269 new trades. From 2018-09-22 23:35:56 UTC to 2018-09-22 23:36:16 UTC. (a few seconds)
2018-09-23 01:36:16 (DEBUG):    -->short @ 0.57975
2018-09-23 01:36:16 (INFO):     Trader Received advice to go short. Selling  XRP
2018-09-23 01:36:16 (DEBUG):    Creating order to sell 193.16716 XRP
(node:20767) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated.
2018-09-22T23:36:22.051Z 'sticky create' 'sell'
2018-09-23 01:36:22 (DEBUG):    [ORDER] statusChange: SUBMITTED
2018-09-23 01:36:22 (DEBUG):    [ORDER] statusChange: OPEN
2018-09-23 01:36:24 (INFO):     [ORDER] partial sell fill, total filled: 193.1
2018-09-23 01:36:24 (DEBUG):    [ORDER] statusChange: FILLED
2018-09-23 01:36:26 (INFO):     [ORDER] summary: { price: 0.57355,
  amount: 193.1,
  date: moment("2018-09-23T01:36:22.661"),
  side: 'sell',
  orders: 1,
  fees: { USDT: 0.11075251 },
  feePercent: 0.10000000000000002 }
2018-09-23 01:36:26 (DEBUG):    syncing private data
2018-09-23 01:36:36 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-23 01:36:37 (DEBUG):    Processing 156 new trades. From 2018-09-22 23:36:16 UTC to 2018-09-22 23:36:36 UTC. (a few seconds)
2018-09-23 01:36:56 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-23 01:36:56 (DEBUG):    Processing 100 new trades. From 2018-09-22 23:36:37 UTC to 2018-09-22 23:36:55 UTC. (a few seconds)
2018-09-23 01:37:16 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-23 01:37:16 (DEBUG):    Processing 71 new trades. From 2018-09-22 23:36:57 UTC to 2018-09-22 23:37:16 UTC. (a few seconds)
2018-09-23 01:37:36 (DEBUG):    Requested XRP/USDT trade data from Binance ...

Since the update, I have another problem:
https://github.com/askmike/gekko/issues/2556

@PhunkyBob i answered that new issue. Thanks for putting your questions there instead of here so we can keep this on topic.
Regarding that, thanks for the logs. Would you be able to watch them and let me know once you either see the "No trades found" error or a message like Binance doesnt know this order, retrying up to 10 times.. (which is the new updated handling).

Would you be able to watch them and let me know once you either see the "No trades found" error or a message like Binance doesnt know this order, retrying up to 10 times.. (which is the new updated handling).

No problem.
Thank you for your work.

@PhunkyBob @xbromy @rkingy is anyone still experiencing this on latest develop?

On my side: 30 trades without any problem, since.

Yes it's same on my end. Having two instances trading on binance different pairs. No problem so far..

2018-09-24 08:41:51 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-24 08:41:51 (DEBUG):    Processing 165 new trades. From 2018-09-24 06:41:31 UTC to 2018-09-24 06:41:51 UTC. (a few seconds)
2018-09-24 08:42:11 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-24 08:42:11 (DEBUG):    Processing 229 new trades. From 2018-09-24 06:41:51 UTC to 2018-09-24 06:42:11 UTC. (a few seconds)
2018-09-24 08:42:11 (INFO):     Trader Received advice to go long. Buying  XRP
2018-09-24 08:42:11 (DEBUG):    Creating order to buy<PHONE_NUMBER>2043007 XRP
2018-09-24T06:42:17.002Z 'sticky create' 'buy'
2018-09-24 08:42:17 (DEBUG):    [ORDER] statusChange: SUBMITTED
2018-09-24 08:42:17 (DEBUG):    [ORDER] statusChange: OPEN
2018-09-24T06:42:19.040Z 'Binance doesnt know this order, retrying up to 10 times..'
2018-09-24T06:42:19.040Z 'Error -2013: Order does not exist.'
2018-09-24T06:42:20.306Z 'Binance doesnt know this order, retrying up to 10 times..'
2018-09-24T06:42:20.306Z 'Error -2013: Order does not exist.'
2018-09-24T06:42:21.775Z 'Binance doesnt know this order, retrying up to 10 times..'
2018-09-24T06:42:21.775Z 'Error -2013: Order does not exist.'
2018-09-24T06:42:23.484Z 'Binance doesnt know this order, retrying up to 10 times..'
2018-09-24T06:42:23.484Z 'Error -2013: Order does not exist.'
2018-09-24T06:42:25.994Z 'Binance doesnt know this order, retrying up to 10 times..'
2018-09-24T06:42:25.994Z 'Error -2013: Order does not exist.'
2018-09-24 08:42:28 (INFO):     [ORDER] partial buy fill, total filled: 201.3
2018-09-24 08:42:28 (DEBUG):    [ORDER] statusChange: FILLED
2018-09-24 08:42:30 (INFO):     [ORDER] summary: { price: 0.55706,
  amount: 201.3,
  date: moment("2018-09-24T08:42:17.182"),
  side: 'buy',
  orders: 1,
  fees: { XRP: 0.2013 },
  feePercent: 0.1 }
2018-09-24 08:42:30 (DEBUG):    syncing private data
2018-09-24 08:42:31 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-24 08:42:31 (DEBUG):    Processing 325 new trades. From 2018-09-24 06:42:11 UTC to 2018-09-24 06:42:31 UTC. (a few seconds)
2018-09-24 08:42:51 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-24 08:42:51 (DEBUG):    Processing 161 new trades. From 2018-09-24 06:42:31 UTC to 2018-09-24 06:42:51 UTC. (a few seconds)
.
.
.
2018-09-25 20:09:44 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-25 20:09:44 (DEBUG):    Processing 65 new trades. From 2018-09-25 18:09:25 UTC to 2018-09-25 18:09:44 UTC. (a few seconds)
2018-09-25 20:10:04 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-25 20:10:04 (DEBUG):    Processing 139 new trades. From 2018-09-25 18:09:44 UTC to 2018-09-25 18:10:04 UTC. (a few seconds)
2018-09-25 20:10:04 (INFO):     Trader Received advice to go long. Buying  XRP
2018-09-25 20:10:04 (DEBUG):    Creating order to buy<PHONE_NUMBER>6142976 XRP
2018-09-25T18:10:09.980Z 'sticky create' 'buy'
2018-09-25 20:10:09 (DEBUG):    [ORDER] statusChange: SUBMITTED
2018-09-25 20:10:10 (DEBUG):    [ORDER] statusChange: OPEN
2018-09-25T18:10:12.076Z 'Binance doesnt know this order, retrying up to 10 times..'
2018-09-25T18:10:12.076Z 'Error -2013: Order does not exist.'
2018-09-25T18:10:13.452Z 'Binance doesnt know this order, retrying up to 10 times..'
2018-09-25T18:10:13.452Z 'Error -2013: Order does not exist.'
2018-09-25 20:10:14 (INFO):     [ORDER] partial buy fill, total filled: 222.9
2018-09-25 20:10:14 (DEBUG):    [ORDER] statusChange: FILLED
2018-09-25 20:10:17 (INFO):     [ORDER] summary: { price: 0.44517799910273664,
  amount: 222.9,
  date: moment("2018-09-25T20:10:10.178"),
  side: 'buy',
  orders: 1,
  fees: { XRP: 0.2229 },
  feePercent: 0.1 }
2018-09-25 20:10:17 (DEBUG):    syncing private data
2018-09-25 20:10:24 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-25 20:10:25 (DEBUG):    Processing 149 new trades. From 2018-09-25 18:10:05 UTC to 2018-09-25 18:10:24 UTC. (a few seconds)
2018-09-25 20:10:44 (DEBUG):    Requested XRP/USDT trade data from Binance ...
2018-09-25 20:10:45 (DEBUG):    Processing 108 new trades. From 2018-09-25 18:10:24 UTC to 2018-09-25 18:10:45 UTC. (a few seconds)
2018-09-25 20:11:04 (DEBUG):    Requested XRP/USDT trade data from Binance ...

If it's up to the strategy and you design the strategy to be run over bfx
USD/BTC that works great. But if you share that strat and someone else runs
it over MCO/BNB on binance he is probably going to lose all his money
within a week.
Since this is off topic in this issue I will start a forum thread about
this. I'll ping you the link when I do.
On Sun, 30 Sep 2018, 20:25 PhunkyBob<EMAIL_ADDRESS>wrote:

I hope one day it would be possible to make market orders (they are filled
faster).
You are right in that they are instant, but market orders in small markets
are super dangerous. I just uploaded a youtube video with examples where I
explain the rational: https://youtu.be/r0yc1sonYvo?t=8m20s
I agree with your analysis.
I don't say "it'ld be nice to replace limit orders by market orders",
but "it'ld be nice to have the choice between limit order and market
orders". It would be a decision made by the owner of the strategy. It's
up to him to know the market he is dealing with.
You say the strategy with Gekko should be to predict price movement and
target 5/10% profit.
I'm using Gekko on 1 minute ticks and I'm targeting lots of trades with 1%
profit. Sometimes it works like a charm ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/issues/2518#issuecomment-425717251, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7MD_ql_ZEfJyGfOxSrNE6Z3qgrN8Ayks5ugLhRgaJpZM4Wh4ev
.

Yip no further issues from my end. Thanks for the fix!


Interrupt a running operation

Using context.WithCancel a call to the cancel func should interrupt the running operation (code snippet below).
ctx, cancel := context.WithCancel(context.Background())

go func () {
	fmt.Println(db.ExecContext(ctx, "begin for i in 1..120 loop dbms_lock.sleep(1); end loop; end;"))
}()

go func() {
	time.Sleep(1 * time.Second)
	cancel()
}()

To get it work i disable Urgent-Data-Transport (OOB) because sendOOB on windows is empty. Furthermore oracle-jdbc-driver and nodejs-thin-driver in my debug cases only (can) send marker packets.
The main challenge is the race conidtion between the running operation (read) and another concurrent read from BreakConnection. That's why i simplify the code with returning an error instead of reading the ORA-01013 packet.

there is 2 point here
1- in connection break function: you discard returned data from the server and return connection break error but this data is important and contain cursor ID required to close the cursor otherwise cursor leak issue will come back
2- you make a go routine for connect context what about exec and query?

your model is good but I need to use it for all context type (cancel and timeout)
timeout is an old problem and passes with many issue until reach this code model
so changing the code need more testing

I use your code make some modification and testing. now available in v 2.8.8


Added whatsapp in sharers

Coverage remained the same at 60.09% when pulling 11839d27f211ed84f0329b02a25e7e1953c0c6bc on vinodnimbalkar:master into d80e38a904491f83c4a17a146d9818def9145750 on MaxArt2501:master.

Coverage remained the same at 60.09% when pulling 11839d27f211ed84f0329b02a25e7e1953c0c6bc on vinodnimbalkar:master into d80e38a904491f83c4a17a146d9818def9145750 on MaxArt2501:master.

Hello, thank you for your contribution!
Why is the source minified as well as why is the test actually the minified version and not actually a test?

Hello! I'm closing this as it's my intention to remove the sharers from the library in order to move them in their own packages (see #39).
You're free to create your own sharer and publish it on npm! (You can actually do that right now.)


Nullable is not a repeatable annotation type in 1.18.4

1.18.4 introduced a bug in handling annotations present both in base class and builder,
for example this code:
@Builder(builderClassName = "Builder")
@Getter
public class Boo {
    @Nullable private final String foo;

    public static class Builder {
        @Nullable private String foo;
    }
}

causing this compilation error:
Boo.java:8: error: Nullable is not a repeatable annotation type
@Builder(builderClassName = "Builder")

Once you remove @Nullable from either base class or builder it compiles fine.
Bug is introduced in 1.18.4, in 1.18.2 everything works without issues

it breaks backward compatibility.
fix could be "don't apply non-repeatable (or the same) annotation if it's already there"


ESP32-HUB75-MatrixPanel-I2S-DMA.cpp:771:11: error: this 'if' clause does not guard...

        if(coloridx && coloridx <= lsbMsbTransitionBit) {
          // divide brightness in half for each bit below lsbMsbTransitionBit
          int lsbBrightness = brt >> (lsbMsbTransitionBit - coloridx + 1);
          if((x_coord) >= lsbBrightness)
            row[x_coord] |= BIT_OE;  // Disable output after this point.
            continue;
        }

Where does the continue; belong to?

if(coloridx && coloridx <= lsbMsbTransitionBit)
if((x_coord) >= lsbBrightness)

I get the following error messages:
../components/arduino/libraries/ESP32-HUB75-MatrixPanel-I2S-DMA/ESP32-HUB75-MatrixPanel-I2S-DMA.cpp: In member function 'void MatrixPanel_I2S_DMA::brtCtrlOE(int, bool)':
../components/arduino/libraries/ESP32-HUB75-MatrixPanel-I2S-DMA/ESP32-HUB75-MatrixPanel-I2S-DMA.cpp:771:11: error: this 'if' clause does not guard... [-Werror=misleading-indentation]
           if((x_coord) >= lsbBrightness)
           ^~
../components/arduino/libraries/ESP32-HUB75-MatrixPanel-I2S-DMA/ESP32-HUB75-MatrixPanel-I2S-DMA.cpp:773:13: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if'
             continue;
             ^~~~~~~~

do {
--x_coord;

751 do { 752 --x_coord;

Maybe I should rephrase the question. Which version is the correct one? (which if statement should the continue belong to?)
A:
if(coloridx && coloridx <= lsbMsbTransitionBit) {
          // divide brightness in half for each bit below lsbMsbTransitionBit
          int lsbBrightness = brt >> (lsbMsbTransitionBit - coloridx + 1);
          if((x_coord) >= lsbBrightness) {
            row[x_coord] |= BIT_OE;  // Disable output after this point.
            continue;
	  }
        }

B:
if(coloridx && coloridx <= lsbMsbTransitionBit) {
          // divide brightness in half for each bit below lsbMsbTransitionBit
          int lsbBrightness = brt >> (lsbMsbTransitionBit - coloridx + 1);
          if((x_coord) >= lsbBrightness) {
            row[x_coord] |= BIT_OE;  // Disable output after this point.
	  }

	  continue;
        }

I've fixed it in the git repo. Should have been A


Post JSON?

I have the code
let mut map = HashMap::new();
    map.insert("lang", "rust");
    map.insert("body", "json");

    let client = reqwest::Client::new();
    let res = client.post("http://httpbin.org/post")
        .json(&map)
        .send()
        .await;

(which is pretty much copied from the docs) and I am getting an error on the .json(&map) part - "no method named json found for struct reqwest::async_impl::request::RequestBuilder in the current scope"
I believe this is a problem because it is literally exactly what the docs provided, but it does not work

I was not using "json" as a feature in cargo.toml


Proper into_num_set() default impl

The default implementation for into_num_set() was erroneously ignoring
the last available value.  In particular it would transform a singleton
set into the empty set.  This makes it so that the last value is
properly accounted for.

bors r=andidr


Move language names to a seperate WL component

https://hosted.weblate.org/projects/weblate/languages/#translations has all the language names, most of which are duplicated in https://hosted.weblate.org/translate/pappl/papp
If not translating the language names, it becomes harder to find more relevant strings, especially as new ones are added .
Setting string-priority would help if they are kept in the same component.
Hopefully things like this could be avoided(?):
https://hosted.weblate.org/translate/pappl/pappl/de/?checksum=bec3cb3a5d69206#history
Can't remember the solution, but https://github.com/ManeraKai/simplytranslate_mobile/issues/171 was fixed.
(Don't agree to the CoC)

@comradekingu I'm not sure what you are asking for? The message catalog doesn't contain language names, but it does contain country names since they are used when generating X.509 certificates/certificate requests.


Bump to ostree-ext 0.14.4

Closes: https://github.com/containers/bootc/issues/679

Now with 100% more DCO


TaskExtractorConfig.save appears to not work (and also be untested and possibly unused).

The appropriate solution may be to just remove it?

I believe it is unused - do you see a use case? Also I am guessing the docstring was for load

It doesn't matter, of it doesn't work now and isn't used now we should
delete it
On Fri, Aug 23, 2024, 10:31 PM Justin Xu @.***> wrote:

I believe it is unused - do you see a use case? Also I am guessing the
docstring was for load
—
Reply to this email directly, view it on GitHub
https://github.com/justin13601/ACES/issues/116#issuecomment-2308001847,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADS5X5SAODHEPJHHVTKZODZS7WBTAVCNFSM6AAAAABNBFA3XSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGAYDCOBUG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Auto doc comment generation and other formatOnType features broken

Environment data

`dotnet --info` output:

.NET SDK:
 Version:           8.0.201
 Commit:            4c2d78f037
 Workload version:  8.0.200-manifests.3097af8b

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22631
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\8.0.201\

VS Code version: 1.89.1
C# Extension version: 2.31.16 (pre-release)
Steps to reproduce

Enable 2.31 Preview (via Switch to Preview Version) and Restart Extensions
Type /// above any method, class, etc.
No further text appears

Expected  behavior
Code snippets and other formatOnType behaviors work as they did in 2.30.28 (via Switch to Release Version).
Actual behavior
Code snippets and other formatOnType behavior, such as automatically inserted spaces and * characters for multiline comments or XML tags for documentation comments, are not functioning.
Additional context
I've changed no other settings or other extensions. The issue appears (that is, stops working) when switching to Preview (2.31) and disappears (that is, works again) when going back to Release (2.30).
If this is a new change (new setting, etc.) rather than a bug, I haven't been able to find any documentation on it.

Hi!
I experience the same issues using the same versions as @CynicalBusiness.

Same here on 2.31.19

Looks like the version went stable and since others are seeing it appear on this version, including myself on v2.31.19, I updated the title.
I can only imagine there must be some special case which triggers/breaks this behavior if it has gone unnoticed thus far?

Can confirm it's broken on v2.31.19 and downgrading to v2.30.28 "fixed" it.

Should be fixed in an upcoming prerelease, will update here when its out.

This is published in the 2.34.10 prerelease (will go to the release channel next week).


Benchmarking alphafold

Hello -
Thank you for such a wonderful algorithm for the community! We have installed the software onto a community server and we want to ensure that we are getting appropriate performance.
Are there benchmark jobs for speed available that could serve as a comparison?
Thank you,
Mike

Hi, I think that it depends on many factor, on various properties of the protein itself. We mention a setup and very basic timings in our preprint: AlphaFold2 transmembrane protein structure prediction shines
https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>7196v1
Tamas

Are there any reference timings for T1050.fasta (which can be obtained from https://www.predictioncenter.org/casp14/target.cgi?target=T1050&view=sequence), which is used in the README (https://github.com/deepmind/alphafold#running-alphafold) as an example?

Sorry for the late answer. I strongly recommend the following talk on benchmarking and optimising AlphaFold speed from HPC-UGent: https://www.youtube.com/watch?v=jP9Qg1yBGcs

@Augustin-Zidek I'm the one who gave that talk, in case that wasn't clear ;)


Add setting to change the URI type in generated clients

I have a C# DTO model for input in my API that takes a string with the DataType annotation for a URL.
[DataType(DataType.Url)]
public string Url { get; set; }

I am using the generated C# client in Razor pages and would have expected the client to use the same sort of annotations but instead I am seeing it come in as a System.Uri.
Is it possible that I missed something in the settings?

Currently there is no setting to change the generated uri type via cli/nswagstudio.
You could use the packages to generate and overload the type resolver method.
But probably it makes sense to add a setting

Just wanted to check if there's been any progress on this - and if not, would you be interested in accepting a PR for this?

No progress AFAIK, but that would add complexity to the template, which is already bloated. Not sure if we should add the option, but you could try to make a PR

I'm fine adding this config similar to the array type configs.

add complexity to the template

It would only be a C# level config, would not need any template changes (no additional complexity there).

Hi,
I made a pull request that should solve this issue in NJsonSchema
https://github.com/RicoSuter/NJsonSchema/pull/1567


How to set a default og:image

Checklist

[X] I have read and accepted the contributing guidelines.

Is your feature request related to a problem? Please describe
When sharing a link to a chirpy-created site, the default "image preview" shown is a chirpy related image. I don't know how or where this is being grabbed from.
Ex. :

For my post here, which does not define image: in the markdown header and thus does not define og:image in the page's html, as confirmed by socialsharepreview.com.
Describe the solution you'd like
I'd like to be able to define a default image: /path/to/image.png that will be used as og:image whenever it is not explicitly described in the markdown header.
Describe alternatives you've considered
This issue states that we can define an image: in index.html for a preview image to be shown when sharing the link to the root of the site. I've confirmed this works. But it only works for the root of the site. And not any other posts or page on the site.
Similar issue here that didn't seem to help me...
Additional context
There's also a chance that I have something stale as I used chirpy-starter about a year ago and might have missed updating something...

The og:image is read from the preview image of each page. So you can set up the default front matter to add a default preview image for each page.

Thanks cotes, that's close to what I was looking for. But I'm not really trying to set a default image for each post, as the image I have in mind isn't for the post specifically, it's really for the whole site in general. I'm really just trying to get a default image to be used for the og:image tag throughout the site. Like if we could take the avatar: from _config.yml to be the default og:image tag, that would be perfect.
Think this is possible? Or point me in the right direction of how I could implement it?

... hide it from displaying prominently at the top of every post.

The current functionality does not support this, it requires customization of og:image to work.

Ok, I think I have largely achieved what I wanted. I could not figure out where the chirpy image of the link preview was being grabbed from. Turns out, there are a few default favicons in jekyll-theme-chirpy. I had generated my favicons so long ago that the conventions for names of the favicon files have changed. I was missing the mstile-150x150.png file. Since I didn't have it, the chirpy default was being used.
I have now generated new favicons in this commit and we now have a small, default preview image used on iOS.
Before (top), and after (below).

Yay!


[PKG-2459] python-kaleido 0.2.1

License: https://github.com/plotly/Kaleido/blob/v0.2.1/LICENSE.txt
Requirements: https://github.com/plotly/Kaleido/blob/v0.2.1/repos/kaleido/py/setup.py
Actions:

Clean up the recipe:

Remove noarch python
Skip py<37
Add flags --no-deps --no-build-isolation to script
Add missing setuptools & wheel to host
Fix python in host and run

Skip s390x and ppc64le as kaleido-core isn't available
Add pip check to run_test.py
Remove test/imports as imports are inside run_test.py

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f6rxs9s8nv/clone/recipe/meta.yaml:30: missing_pip_check: For pypi packages, pip check should be present in the test commands
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_98jpsi6r5w/clone/recipe/meta.yaml:32: missing_pip_check: For pypi packages, pip check should be present in the test commands
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_2cykicv1u6/clone/recipe/meta.yaml:32: missing_pip_check: For pypi packages, pip check should be present in the test commands
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ac7obahndt/clone/recipe/meta.yaml:32: missing_pip_check: For pypi packages, pip check should be present in the test commands
Errors were found


[FIX] No longer use recursivity in ReactiveThrottler::onRequestDone

The ReactiveThrottler can be (subscriber direct) recursive, leading to StackOverflowError that could cause unpredictable failure.
Very rare yet spotted in production twice in a row, effectively killing the IMAP service:
java.lang.StackOverflowError: null
	at java.base/java.text.DecimalFormat.format(Unknown Source)
	at java.base/java.text.DecimalFormat.format(Unknown Source)
	at java.base/java.text.SimpleDateFormat.zeroPaddingNumber(Unknown Source)
	at java.base/java.text.SimpleDateFormat.subFormat(Unknown Source)
	at java.base/java.text.SimpleDateFormat.format(Unknown Source)
	at java.base/java.text.SimpleDateFormat.format(Unknown Source)
	at java.base/java.text.DateFormat.format(Unknown Source)
	at ch.qos.logback.contrib.json.JsonLayoutBase.format(Unknown Source)
	at ch.qos.logback.contrib.json.JsonLayoutBase.formatTimestamp(Unknown Source)
	at ch.qos.logback.contrib.json.JsonLayoutBase.addTimestamp(Unknown Source)
	at ch.qos.logback.contrib.json.classic.JsonLayout.toJsonMap(Unknown Source)
	at ch.qos.logback.contrib.json.classic.JsonLayout.toJsonMap(Unknown Source)
	at ch.qos.logback.contrib.json.JsonLayoutBase.doLayout(Unknown Source)
	at ch.qos.logback.core.encoder.LayoutWrappingEncoder.encode(LayoutWrappingEncoder.java:114)
	at ch.qos.logback.core.OutputStreamAppender.writeOut(OutputStreamAppender.java:192)
	at ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender.java:237)
	at ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.java:102)
	at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:85)
	at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51)
	at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:272)
	at ch.qos.logback.classic.Logger.callAppenders(Logger.java:259)
	at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:426)
	at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:386)
	at ch.qos.logback.classic.Logger.warn(Logger.java:697)
	at reactor.util.Loggers$Slf4JLogger.warn(Loggers.java:304)
	at reactor.core.Exceptions.throwIfFatal(Exceptions.java:513)
	at reactor.core.publisher.Operators.onOperatorError(Operators.java:756)
	at reactor.core.publisher.Operators.onOperatorError(Operators.java:734)
	at reactor.core.publisher.Operators.onOperatorError(Operators.java:716)
	at reactor.core.publisher.Operators.reportThrowInSubscribe(Operators.java:232)
	at reactor.core.publisher.Mono.subscribe(Mono.java:4571)
	at reactor.core.publisher.Mono.subscribeWith(Mono.java:4634)
	at reactor.core.publisher.Mono.subscribe(Mono.java:4395)
	at org.apache.james.imapserver.netty.ReactiveThrottler.onRequestDone(ReactiveThrottler.java:129)
	at org.apache.james.imapserver.netty.ReactiveThrottler.lambda$onRequestDone$5(ReactiveThrottler.java:127)
	at reactor.core.publisher.FluxDoFinally$DoFinallySubscriber.runFinally(FluxDoFinally.java:146)
	at reactor.core.publisher.FluxDoFinally$DoFinallySubscriber.onComplete(FluxDoFinally.java:129)
	at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.onComplete(MonoIgnoreThen.java:210)
	at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.subscribeNext(MonoIgnoreThen.java:239)
	at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.onComplete(MonoIgnoreThen.java:204)
	at reactor.core.publisher.FluxContextWrite$ContextWriteSubscriber.onComplete(FluxContextWrite.java:126)
	at reactor.core.publisher.FluxDoOnEach$DoOnEachSubscriber.onComplete(FluxDoOnEach.java:223)
	at reactor.core.publisher.FluxContextWrite$ContextWriteSubscriber.onComplete(FluxContextWrite.java:126)
	at reactor.core.publisher.MonoUsing$MonoUsingSubscriber.onComplete(MonoUsing.java:283)
	at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.onComplete(Operators.java:2231)
	at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.onComplete(Operators.java:2231)
	at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.onComplete(Operators.java:2231)
	at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.onComplete(MonoIgnoreThen.java:210)
	at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.subscribeNext(MonoIgnoreThen.java:239)
	at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:51)
	at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:76)
	at reactor.core.publisher.MonoUsing.subscribe(MonoUsing.java:109)
	...

Don't merge it does not work.
    @Test
    void test() {
        Mono<Void> m = Mono.delay(Duration.ofMillis(1)).then();
        for (int i = 0; i < 2000; i++) {
            int j = i;
            m = m.doFinally(any -> System.out.println(j));
        }
        m.block();
    }

    private Sinks.Many<Integer> objectMany;
    private CountDownLatch countDownLatch;

    @Test
    void test() throws Exception {
        countDownLatch = new CountDownLatch(1);
        objectMany = Sinks.many().multicast().onBackpressureBuffer();
        objectMany.asFlux()
            .subscribeOn(Schedulers.parallel())
            .subscribe(i -> Mono.delay(Duration.ofMillis(1))
                .doFinally(any -> betise(i))
                .subscribe());
        objectMany.emitNext(1, Sinks.EmitFailureHandler.FAIL_FAST);
        countDownLatch.await();
    }

    void betise(int i) {
        if (i < 20000) {
            System.out.println(i);
            objectMany.emitNext(i + 1, Sinks.EmitFailureHandler.FAIL_FAST);
        } else {
            countDownLatch.countDown();
        }
    }

Using signaling technics apparently do avoid the effect mentioned in https://github.com/apache/james-project/pull/2486#issuecomment-2457568663

Can we squash the fixups?

Can we squash the fixups?

Nope, let's be sure we fixes some real-world IMAP issue and that this changeset is prod backed.

Running for a week in production, it did solve the stak overflow error without compromising throttling.
Also it ensure all IMAP request processing starts from the eventloop which wasn't the case before.


adding records to table creates scroll bar

The table widget should simply resize, not get a scrollbar.

Worked with @josephtocci , could not reproduce.


add social share wrapper

Adds a component that you can use to automagically create a social share button for twitter, linkedin or facebook.  It's very un-opinionated on what the element should look like because we may want buttons vs icons at various spots throughout the site.  Component takes a url (facebook and linkedin) or content (twitter) to share
usage:
<SocialShare type="twitter" content="A tweet">
  <Icon name="twitter"/>
</SocialShare>

:+1:


PR 2: add support for expense group sync

Codecov Report
Attention: 77 lines in your changes are missing coverage. Please review.

Comparison is base (636a515) 73.47% compared to head (ae3d2f9) 71.33%.

Additional details and impacted files
@@                         Coverage Diff                          @@
##           create-accounting-export-methods      #73      +/-   ##
====================================================================
- Coverage                             73.47%   71.33%   -2.15%
====================================================================
  Files                                    51       53       +2
  Lines                                  2236     2337     +101
====================================================================
+ Hits                                   1643     1667      +24
- Misses                                  593      670      +77

Files
Coverage Δ

apps/fyle/models.py
89.01% <100.00%> (+0.24%)
:arrow_up:

apps/fyle/views.py
92.50% <50.00%> (-7.50%)
:arrow_down:

apps/fyle/queue.py
33.33% <33.33%> (ø)

apps/fyle/tasks.py
17.94% <17.94%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Left/Right transitions are not working properly on Android

So I was testing this on my Android LG G3 and when I clicked on a contact, it didn't slide to the left, or right to go back to the list as shown in the browser version. Is this expected?
What happens is that the content goes away and the new contnet fades in. The blue header and background stay intact though.

@rclai I haven't actually tested on an Android device yet, just simulator. I was under the impression that it would work without a problem. Which Android version is your phone running?

Lollipop.

Ok thanks, I'll try to get my hands on a device to do some testing this week.

@rclai Do you get the same thing on the demo app? http://meteor-ionic.meteor.com/

I can see the left/right swipe more but there's still a fade out of the current content before the new content swipes in.
In the browser, there's a seamless transition that doesn't involve the fading out of the current content.

Closing this and moving it to meteoric/meteor-ionic#17


Animated updating of chart timeScale without recreating the chart.

I am trying to update the timeScale of the chart without recreating it. Currently, it seems like I have to recreate the entire chart to change the timeScale, which isn't optimal for performance.
This feature would be especially helpful in cases where the chart is continuously receiving new data and needs to adjust the timeScale frequently. An animated transition would make these changes less jarring for users.

Hi @sulhadin,
Could you be a bit more specific about what you are trying to change with the timescale? Perhaps if you can share an example of your current implementation?
You shouldn't need to recreate the chart (or the timescale) for any changes to the chart.
The series api includes an update() method for providing new data to an existing series, and the ITimeScaleApi has many methods for adjusting the time scale and it's options.
The library can scroll new updates to the chart into view. scrollToRealTime, or shitVisibleRangeOnNewBar

Hi @SlicedSilver
I am using THIS implementation which uses the useEffect hook. As such, the chart gets recreated each time any of the states data, backgroundColor, lineColor, textColor, areaTopColor, areaBottomColor change. Moreover, I've added timeScale as an option:
   const chart = createChart(
        chartContainerRef.current,
          ....
          timeScale,
        }),

Upon updating timeScale, the useEffect hook is triggered and createChart re-initiates the chart creation. I'm curious if there's a means to animate the transition between different timeScale options? Alternatively, is there a different approach to change the timeScale without recreating the entire chart? Any guidance or suggestions would be greatly appreciated.

You shouldn't need to create a new chart for each option change. It would be better to create the chart once within the React component (and only remove it when the React component is removed). If any of the properties change (options change) then you could apply them to the existing chart instance by using the applyOptions() method. Discussed further in this tutorial: https://tradingview.github.io/lightweight-charts/tutorials/customization/chart-colors#applying-options
Which specific timescale option are you changing that you would like to animate? rightOffset is essentially the same as scrolling left or right. So the scrollToPosition method could help with this. barSpacing is essentially the zoom level which could be set using the setVisibleLogicalRange

I see that the example React component you are using is our example in the documentation. We should update that example to implement better practices. Apologies, that example focused more on simplicity than performance when changing properties. We will improve the example.

Your solution helped me with the performance issue. Thank you for your help.


Save per-modality feature names for MuData models

Current MuData-based models save their var_names as a single list, with no information on which feature came from which modality. This is problematic for certain downstream features (e.g. reference mapping #2393) which require knowledge of features' modalities. This PR thus modifies the base save function to save var_names as a dictionary for MuData models, where each key is a modality and each value is that modality's features. In anticipation of potential backwards compatibility issues, this PR also includes a convert_legacy_mudata_save method to update earlier MuData models saved under the previous scheme.
@martinkim0 @canergen Per our discussion I added convenience functions for converting legacy models saved with the old MuData var names saving scheme (as opposed to just waiting until scvi-tools 2.0 and not worrying about backwards compatibility). I made this a separate PR from the scArches MuData PR (https://github.com/scverse/scvi-tools/pull/2578) to keep each PR more focused/reduce reviewer burden.

Just to add to my comment above, we do some validation checking that the saved var names match with the loaded mudata in load.
In the case where an old model save is loaded with new code, we can just check that the union of per-mod var names in the mudata is equal to the var names in the model save (since I believe the top level var names in mudata corresponds to the union of all mods).

Hi @martinkim0
Your suggested path forward largely makes sense to me. My one question is: what's the logic behind raising a user warning with the new default save scheme (i.e., saving per-mod var names for new mudata models)?

sorry for the delay - I've merged support for this with #2769. thanks for putting in this initial pr! i'll close this now.


Migration Log

This is an auto-generated issue. The migration log is in the following comment(s).

Log Chunk 1
[2024-05-20T07:36:01Z] INFO -- Migration started by shubhajyoti-bagchi-groww from https://github.com/GrowwOld/react-native to Groww-OSS/react-native
[2024-05-20T07:36:01Z] INFO -- Migration ID: 28fa9b9f-e901-448e-b286-3f15bdeec4ca
[2024-05-20T07:36:01Z] INFO -- -----------------------------
[2024-05-20T07:36:01Z] INFO -- Git source migration started
[2024-05-20T07:46:23Z] INFO -- Git source migration completed
[2024-05-20T07:46:23Z] INFO -- -----------------------------
[2024-05-20T07:46:23Z] INFO -- Extraction started
[2024-05-20T07:46:26Z] WARN -- ExtractRepoMetadataArchiveResumableJob: A release with ID 82062793 failed to export from https://github.com/GrowwOld/react-native/releases/tag/untagged-43d23ff307f78c1c25e9 with the following warning: "Model could not be serialized due to validation errors: Target commitish is invalid".
[2024-05-20T07:46:31Z] INFO -- Extraction complete
[2024-05-20T07:46:31Z] INFO -- -----------------------------
[2024-05-20T07:46:31Z] INFO -- Transformation started
[2024-05-20T07:46:33Z] INFO -- Transformation complete
[2024-05-20T07:46:33Z] INFO -- -----------------------------
[2024-05-20T07:46:33Z] INFO -- Import started
[2024-05-20T07:46:33Z] WARN -- 'Allow Forking' setting could not be enabled for the repository because it is not enabled at the organization level.
[2024-05-20T07:46:47Z] INFO -- Import complete
[2024-05-20T07:46:47Z] INFO -- -----------------------------
[2024-05-20T07:46:47Z] INFO -- Migration complete
[2024-05-20T07:46:47Z] INFO -- -----------------------------


wrap data in single quotes

@delirius325 cURL commands fail for me on OS X 10.13 using bash without having the data as json wrapped in single quotes.

Thanks for the contribution 👍 !


Use array and switch for numerify

Codecov Report

Merging #478 (1cac541) into main (2da3a03) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #478      +/-   ##
============================================
- Coverage     93.04%   92.95%   -0.09%
+ Complexity     2139     2136       -3
============================================
  Files           233      233
  Lines          4469     4471       +2
  Branches        468      467       -1
============================================
- Hits           4158     4156       -2
- Misses          192      197       +5
+ Partials        119      118       -1

Impacted Files
Coverage Δ

.../java/net/datafaker/service/FakeValuesService.java
86.72% <100.00%> (-0.59%)
:arrow_down:

.../main/java/net/datafaker/service/FakerContext.java
84.61% <0.00%> (-2.57%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Creating, using and managing multiple child processes

Ideally, we should execute each notebook in a separate child process. This is similar to Kernels in Jupyter notebooks.
This ensures that multiple notebooks can be run simultaneously, and each manages its own state.
I believe this can be achieved by using child processes
Acceptance

[ ] User can run multiple notebooks simultaneously
[ ] User can start and manage new kernels/chilc process
[ ] Notebooks are independent of each other

@risenW wanna assign this issue to me?

@risenW wanna assign this issue to me?

I fixed this already, and didn't use child process. I ended up using a context object. I'll update the issue description


Build : scalingo sometimes deploys the wrong react-sdk version

When specifying a react-sdk version from a github branch or tag, sometimes scalingo deploys the wrong version.
Scalingo support says that it's a problem with yarn : https://github.com/yarnpkg/yarn/issues/4734
Workaround : reset deployment cache of scalingo machine (in Deploy page in scalingo dashboard) and redeploy.
Possible solutions :

look through the yarn issue (linked above) for fixes (clean build, force version, whatever) to add to our build commands.
use npm instead of yarn (but we diverge from element)
use yarn links instead, the way element does in more recent versions. This avoids the problem because you check out the repo for react-sdk, then switch the appropriate branch, then yarn link it (so you don't have to use github links in package.json at all)

Hopefully solved by https://github.com/tchapgouv/tchap-web/pull/214


Does this work in URP 2021.2 ?

Using Variant Collection which I collect using prewarming current scene, and in build I only build that scene, so my guess is those shaders are all I need to include. The build time cut by 7/8 ( 8 hours to 1 hour ) which is nice, but everything is pink.

Also I did write in Strip by name, start with
Hidden/Universal Render Pipeline/Terrain
which I double check many time with no typo, but I still see it's families being compiling on build.

Strip By Variant Collection is the most unpredictable unfortunately - Unity doesn't seem to make a very accurate list of what shaders are actually in use. As such it should only be used for quick builds where you don't care much about shaders.

From my testing i think that UnityShaderStripper doesn't handle the new local macros for variants at all really. So if you have #pragma shader_feature_local / #pragma shader_feature_local_fragment (and others) in your shaders, you're bound to have some pink materials.
@SixWays Did you notice this as well ? Is this something you are likely to fix ?
I've been using your tool for about 2 years and it's been a godsend <3 , builds now only take 3 - 8 minutes whereas they took about an hour before.  Massive improvement to iteration Times! Unity should pay you a million and integrate that thing into their engine.
Also i think shadervariant stripping is pretty useable, you just gotta be careful with your shaders and materials but it works for my case.

I've not used it with those pragmas so can't say! But not too surprising. I can't promise to take a look any time soon - it basically depends on whether I'm using it for a particular thing. Good to hear it's been of use to you though!

It's sad that on user's perspective, the variants that be warmed up while user playing the level should be all the variants the build need for that level. But Unity failed to deliver that, at this point I don't think the variant collection asset have any use.
I warmed up the level, collect the variants to asset, set the asset as preloaded shaders. Notice the Tree LOD Instancing_ON is there in the variant asset, yet in build player log I see Unity complained that the Tree LOD Instancing_ON is missing. Which does not make any sense.
I honestly think this is a bug, for when I'm about to release my game I'll file this as a bug report.


Grouping with Full width Row (Expandable)

@ceolter: I try  to implement the grouping or tree data with full width row (Expandable).  because both having the same set of cellrenderer, expandable not working when grouping available

cellRenderer: 'group',

if its possible, can we have example here please
https://www.ag-grid.com/javascript-grid-full-width-rows/?framework=angular#gsc.tab=0
Thanks you
Anand

Hi
Please raise support requests either in stackoverflow, or our free forum: https://ag-grid.com/forum/forumdisplay.php?fid=4

Has this issue been raised in either SO or official forums so I can check the answer?


[Guide] Add more option in featured post

Hi there, I've found a really good video here: https://www.youtube.com/watch?v=KxdhGAw93QI&feature=emb_logo (by you). Can you add a way to make the title of each featured post direct to the post link when you click on it (or adding a Read More button under the post's excerpt) Thanks

There are some code examples on this page that could be useful: https://reflexjs.org/videos/add-featured-posts-section
You can use post.slug to link to the post page.
import { usePost } from "@reflexjs/gatsby-theme-post"

// highlight-start
export const FeaturedPosts = ({ limit = 5 }) => {
  // highlight-end
  const featuredPosts = usePost({ featured: true })
  return featuredPosts
    ? featuredPosts
        .slice(0, limit) // highlight-line
        .map((post) => {post.title})
    : null
}

Don't know why but when I add like this:
import { usePost } from "@reflexjs/gatsby-theme-post"
export const FeaturedPosts = ({ limit = 5 }) => {
  const featuredPosts = usePost({ featured: true })
  return featuredPosts
    ? featuredPosts
        .slice(0, limit)
        .map((post) => {post.title})
    : null
}

Gatsby report a problem:

Here is my block, how could I add the limit to this, thanks.
import { usePost } from "@reflexjs/gatsby-theme-post"

export const FeaturedPosts = () => {
  const featuredPosts = usePost({ featured: true })
  return (
    <Container>

Present

      {featuredPosts.map((post) => (

          <Grid col="350px 1fr" gap="8">
            <Image src={post.image} aspectRatio={3 / 2}/>

{post.title}

{post.excerpt}

                <ButtonLink to={post.slug} variant="secondary sm">
                Read more <Icon name="arrow-right" ml="2" />
                </ButtonLink>

          </Grid>

    ))}
      <ButtonLink to="/present" variant="secondary lg">
        More present <Icon name="arrow-right" ml="2" />
      </ButtonLink>
    </Container>
  );
};

Can you try the following?
import { usePost } from "@reflexjs/gatsby-theme-post"

export const FeaturedPosts = ({ limit = 5 }) => {
  const featuredPosts = usePost({ featured: true })
  return (
    <Container>

Present

      {featuredPosts.slice(0, limit).map((post) => (

          <Grid col="350px 1fr" gap="8">
            <Image src={post.image} aspectRatio={3 / 2}/>

{post.title}

{post.excerpt}

                <ButtonLink to={post.slug} variant="secondary sm">
                Read more <Icon name="arrow-right" ml="2" />
                </ButtonLink>

          </Grid>

    ))}
      <ButtonLink to="/present" variant="secondary lg">
        More present <Icon name="arrow-right" ml="2" />
      </ButtonLink>
    </Container>
  );
};

Thanks, it works.


update gitlab within the container

How to update an old Gitlab 8.1.3 on the latest version without losing data?
TS-453 Pro

Hi
The latest version of sameersbn/gitlab is 8.12.6.
Please follow the steps to upgrade gitlab manually.
Step 1. SSH into your NAS
$ ssh admin@NAP_IP

Step 2. Change directory to gitlab folder
# cd /share/CACHEDEV1_DATA/.qpkg/container-station/data/application/gitlab

Step 3. Edit docker-compose.yml file
postgresql:
  restart: always
  image: sameersbn/postgresql:9.4-23
  environment:
    - DB_USER=gitlab
    - DB_PASS=password
    - DB_NAME=gitlabhq_production
    - DB_EXTENSION=pg_trgm
gitlab:
  restart: always
  image: sameersbn/gitlab:8.12.6
  links:
    - redis:redisio
    - postgresql:postgresql
  ports:
    - "10080:80"
    - "10022:22"
  environment:
    - DEBUG=false
    - GITLAB_PORT=10080
    - GITLAB_SSH_PORT=10022
    - GITLAB_SECRETS_DB_KEY_BASE=qcs-gitlab-app
    - GITLAB_SECRETS_OTP_KEY_BASE=qcs-gitlab-app
    - GITLAB_SECRETS_SECRET_KEY_BASE=qcs-gitlab-app
redis:
  restart: always
  image: sameersbn/redis:latest
  command:
    - --loglevel warning

Step 4. Use compose to recreate app
# docker-compose up -d

Wait for a moment and check your data on the website.
I hope that helps clarify the issue. Let me know if you need additional information.

thx
works fine


KeyError: 'loss/total'

I have a small doubt regarding line 547 of the train.py file. According to the code, conf.train.best_key will be in numerical format, but why is it set as a string in the config section as best_key = 'loss/total'?

The code here is intended to compare the value of the key named ‘loss/total’ in the results dictionary. However, I am currently encountering a KeyError: 'loss/total' at this point in the code execution. Upon inspection, I have found that the results dictionary is empty. Could you please advise on how to resolve this issue?

This error arises from inaccurately dividing the train, test, and validation from my dataset to supply to the model, resulting in the val_loader being empty. Thus, the solution involves checking whether your val_loader is indeed empty and then properly re-dividing the train_dataset, test_dataset, and val_dataset for the model (ensuring that none of the datasets are left empty).

Thank you for identifying the issue with the empty val_loader. Through my efforts, I have not discovered how to correctly divide the dataset into training, testing, and validation sets.Could you please provide a guide on how to properly divide my dataset into training, testing, and validation sets?

I have resolved my issue. Thank you for your response.

Thank you for identifying the issue with the empty val_loader. Through my efforts, I have not discovered how to correctly divide the dataset into training, testing, and validation sets.Could you please provide a guide on how to properly divide my dataset into training, testing, and validation sets?

请问一下 如何解决empty val_loader的问题，非常感谢

You can set it up in the data section of the.yaml file you use for the training process.

 You can set it up in the data section of the.yaml file you use for the training process.

非常感谢


hatamtehrani

Please fill the following out:

Name: hatamtehrani
Homepage url: https://hatamtehrani.com
Brand Guidelines/Licensing: https://hatamtehrani.com/about-us/
Logo: https://hatamtehrani.com/wp-content/uploads/2016/09/logo-hatam.jpg

Example:
Name: Microsoft
Homepage url: https://microsoft.com
Brand Guidelines/Licensing: https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/logo.aspx
Logo: https://news.microsoft.com/microsoft-news-center-photos/msft_logo_rgb_c-gray/

Hey folks -we're looking at a new website and it's likely that the friends of TypeScript page isn't going to make it to the new site. This is mainly because close to everyone is a friend of TypeScript now and listing folks kinda feels a bit un-inclusive to everyone else.
So I'm going to close this issue - thanks for posting to apply


Feature Request: Dynamic filter

Will it be possible to introduce the concept of dynamic filter, so that we map a column to the logged-in user or logged-in role and apply that filter to the data retrieved.
Consider a table where one of the column represents the user name, if we can define a dynamic filter to that column (attaching the logged-in user), then whoever logs-in will see their own data.
It will be great, if we can have dynamic filters at the cube level and at widget level.
Thanks & Regards
Ranes

It's already done at branch-0.4.


origfn

Hi, I've this error on graceful queue shutdown on version 0.10.5:
origfn is not a function
Apr 27 08:29:59 test-air-alvieromartini app/web.2:  15:29:58 web-app-0 STACK:
Apr 27 08:29:59 test-air-alvieromartini app/web.2:  15:29:58 web-app-0 TypeError: origFn is not a function
Apr 27 08:29:59 test-air-alvieromartini app/web.2:  15:29:58 web-app-0   at Queue.shutdown (/app/node_modules/kue/lib/kue.js:423:5)
Apr 27 08:29:59 test-air-alvieromartini app/web.2:  15:29:58 web-app-0   at process. (/app/workers/queue.js:14:18)
Apr 27 08:29:59 test-air-alvieromartini app/web.2:  15:29:58 web-app-0   at process.g (events.js:260:16)
Apr 27 08:29:59 test-air-alvieromartini app/web.2:  15:29:58 web-app-0   at emitNone (events.js:72:20)
Apr 27 08:29:59 test-air-alvieromartini app/web.2:  15:29:58 web-app-0   at process.emit (events.js:166:7)
Apr 27 08:29:59 test-air-alvieromartini app/web.2:  15:29:58 web-app-0   at Signal.wrap.onsignal (node.js:804:46)
Seems to be a regression to https://github.com/Automattic/kue/issues/606

If you check the code, it looks somehow wired!
Can you dig it more?

Sorry for late response, didn't received the issue update message.
Yes, it seems to manage to "check" if there is something in "fn" length. But my case is managed in row 362, as I only pass timeout:
process.once 'SIGTERM', (sig) -> queue.shutdown 5000

and kue consider the single parameter as callback. I can get along passing a fake callback function, so to go to row 366.
Can be fixed checking if first argument is a number or not, I think. Will fork and push the fix, if you want.
BTW: kue is very kool, it saved my bacon as I was using Parse Background Jobs and, as Parse is closing...

👍 a PR is welcome @giano

Will work on it this weekend. Thanks for Kue.


Starting weave router will take a long time after host reboot

INFO: 2016/08/12 11:32:34.116564 === received SIGINT/SIGTERM ===
*** exiting
INFO: 2016/08/12 11:33:08.687573 Command line options: map[dns-effective-listen-address:<IP_ADDRESS> ipalloc-range: resolv-conf:/var/run/weave/etc/resolv.conf nickname:autumn-darkness-94 port:6783 trusted-subnets: datapath:datapath dns-domain:kontena.local dns-listen-address:<IP_ADDRESS>:53 http-addr:<IP_ADDRESS>:6784 name:de:0d:de:ba:53:32]
FATA: 2016/08/12 11:34:28.834638 netlink error response: device or resource busy
INFO: 2016/08/12 11:34:29.754315 Command line options: map[dns-domain:kontena.local dns-effective-listen-address:<IP_ADDRESS> http-addr:<IP_ADDRESS>:6784 nickname:autumn-darkness-94 port:6783 trusted-subnets: datapath:datapath dns-listen-address:<IP_ADDRESS>:53 ipalloc-range: name:de:0d:de:ba:53:32 resolv-conf:/var/run/weave/etc/resolv.conf]
INFO: 2016/08/12 11:34:29.763312 Communication between peers via untrusted networks is encrypted.
INFO: 2016/08/12 11:34:29.769125 Our name is de:0d:de:ba:53:32(autumn-darkness-94)
INFO: 2016/08/12 11:34:29.769529 Restart/resume detected - using persisted peer list: []
INFO: 2016/08/12 11:34:29.783083 Docker API on unix:///var/run/docker.sock: &[Arch=amd64 KernelVersion=4.6.3-coreos Version=1.10.3 ApiVersion=1.22 GitCommit=3cd164c GoVersion=go1.5.4 Os=linux]
INFO: 2016/08/12 11:34:29.784625 Listening for DNS queries on <IP_ADDRESS>
INFO: 2016/08/12 11:34:29.784723 Sniffing traffic on datapath (via ODP)
INFO: 2016/08/12 11:34:29.825981 Listening for HTTP control messages on <IP_ADDRESS>:6784

Sometimes weave router starts immediately and sometimes it seems to take ~80s.
Tested in DigitalOcean & Vagrant with CoreOS stable (kernel 4.6.3-coreos)

Thanks for the report. I was able to reproduce the issue.

@jakolehm if you are still able to reproduce the issue, could you add and enable the weavedebug.service systemd service? Once you have reproduced the issue, please do cat /sys/kernel/debug/tracing/trace and provide the output. Thanks!
Relevant files:

/etc/systemd/system/weavedebug.service
/home/core/ftrace.sh

It seems that we cannot reproduce this anymore. Maybe it was some weird combination of kernel/docker and moon phase.

Happened again with 1.7.2 (CoreOS stable / DigitalOcean). Also found this in the weave container logs: https://gist.github.com/jakolehm/80e6914ea81d4e7ca98d3b0e6ccb1599

Trace: https://gist.github.com/jakolehm/150802bc6ce3a62df5b43b0f55eb1a91

Thanks! We will look into those.

@jakolehm: is the attached kernel trace for the case when weave fails with netlink error response: device or resource busy or interface conversion: interface is nil, not odp.TunnelFlowKey (as can be seen in the weave container logs you just linked)? Also, was it on the 4.7.0 kernel?

@brb no, it's not from the same boot (although same machine). Kernel is 4.7.0.

@brb my last comment was a bit misleading.. linked ftrace is from the netlink error response: device or resource busy case.

Most likely this device or resource busy error happens because of a bug in the systemd: https://github.com/systemd/systemd/issues/1982
If we disable ipv6 completely from weave interface we cannot reproduce this error, or if we test the same coreos/weave/systemd host in an environment that does not have ipv6 at all. Also if we upgrade coreos to beta (systemd 331) the errors are gone.

On my System Ubuntu 15.04, I unable to start weave after docker daemon is restarted.

Docker daemon is started with /usr/bin/docker daemon -H fd:// --ip=<IP_ADDRESS> (thanks to systemd)
Start docker daemon, start weave with weave launch --password=foobar
Restart docker with systemctl restart docker
Weave sock is not unavailable (see logs below), error got: curl: (7) Failed to connect to <IP_ADDRESS> port 6784: Connection refused

Weave log
INFO: 2016/12/07 03:15:20.982699 Command line options: map[dns-listen-address:<IP_ADDRESS>:53 http-addr:<IP_ADDRESS>:6784 ipalloc-range:<IP_ADDRESS>/12 port:6783 resolv-conf:/var/run/weave/etc/resolv.conf status-addr:<IP_ADDRESS>:6782 datapath:datapath dns-effective-listen-address:<IP_ADDRESS> name:2a:06:a8:e4:34:36 nickname:xxxx]
INFO: 2016/12/07 03:15:21.001349 Communication between peers via untrusted networks is encrypted.
INFO: 2016/12/07 03:15:21.040978 Our name is 2a:06:a8:e4:34:36(hinton)
INFO: 2016/12/07 03:15:21.041031 Launch detected - using supplied peer list: []
INFO: 2016/12/07 03:15:21.042192 Docker API on unix:///var/run/docker.sock: &[Arch=amd64 KernelVersion=3.19.0-22-generic BuildTime=2016-08-18T17:52:38.255390991+00:00 Version=1.12.1 ApiVersion=1.24 GitCommit=23cf638 GoVersion=go1.6.3 Os=linux]
INFO: 2016/12/07 03:15:21.042587 [allocator 2a:06:a8:e4:34:36] No valid persisted data
INFO: 2016/12/07 03:15:21.080622 [allocator 2a:06:a8:e4:34:36] Initialising via deferred consensus
INFO: 2016/12/07 03:15:21.095075 Listening for DNS queries on <IP_ADDRESS>
INFO: 2016/12/07 03:15:21.095147 Sniffing traffic on datapath (via ODP)
INFO: 2016/12/07 03:15:21.107806 Listening for HTTP control messages on <IP_ADDRESS>:6784
INFO: 2016/12/07 03:15:21.108658 Listening for metrics requests on <IP_ADDRESS>:6782
INFO: 2016/12/07 03:15:21.309456 Discovered local MAC d2:79:ce:66:24:74
INFO: 2016/12/07 03:15:21.753424 Discovered local MAC 12:d4:57:4e:bb:d2
INFO: 2016/12/07 03:15:21.817367 Discovered local MAC 2a:06:a8:e4:34:36
INFO: 2016/12/07 03:15:35.853407 ->[<IP_ADDRESS>:64837] connection accepted
INFO: 2016/12/07 03:15:35.940616 ->[<IP_ADDRESS>:64837|0a:fe:80:b0:89:7b(ip-172-31-8-91)]: connection ready; using protocol version 2
INFO: 2016/12/07 03:15:35.940662 Unable to use fastdp for connection to 0a:fe:80:b0:89:7b(ip-172-31-8-91): encryption not supported
INFO: 2016/12/07 03:15:35.940761 overlay_switch ->[0a:fe:80:b0:89:7b(ip-172-31-8-91)] using sleeve
INFO: 2016/12/07 03:15:35.940848 ->[<IP_ADDRESS>:64837|0a:fe:80:b0:89:7b(ip-172-31-8-91)]: connection added (new peer)
INFO: 2016/12/07 03:15:36.100426 ->[<IP_ADDRESS>:64837|0a:fe:80:b0:89:7b(ip-172-31-8-91)]: connection fully established
INFO: 2016/12/07 03:15:36.101295 EMSGSIZE on send, expecting PMTU update (IP packet was 60052 bytes, payload was 60044 bytes)
INFO: 2016/12/07 03:15:36.192771 sleeve ->[<IP_ADDRESS>:15566|0a:fe:80:b0:89:7b(ip-172-31-8-91)]: Effective MTU verified at 1414
INFO: 2016/12/07 03:18:43.610482 ->[<IP_ADDRESS>:37743] connection accepted
INFO: 2016/12/07 03:18:43.698618 ->[<IP_ADDRESS>:37743|3e:f5:d1:78:7a:ac(ip-172-31-8-35)]: connection ready; using protocol version 2
INFO: 2016/12/07 03:18:43.698665 Unable to use fastdp for connection to 3e:f5:d1:78:7a:ac(ip-172-31-8-35): encryption not supported
INFO: 2016/12/07 03:18:43.698811 overlay_switch ->[3e:f5:d1:78:7a:ac(ip-172-31-8-35)] using sleeve
INFO: 2016/12/07 03:18:43.698903 ->[<IP_ADDRESS>:37743|3e:f5:d1:78:7a:ac(ip-172-31-8-35)]: connection added (new peer)
INFO: 2016/12/07 03:18:43.864153 ->[<IP_ADDRESS>:37743|3e:f5:d1:78:7a:ac(ip-172-31-8-35)]: connection fully established
INFO: 2016/12/07 03:18:43.864644 EMSGSIZE on send, expecting PMTU update (IP packet was 60052 bytes, payload was 60044 bytes)
INFO: 2016/12/07 03:18:43.952305 sleeve ->[<IP_ADDRESS>:2037|3e:f5:d1:78:7a:ac(ip-172-31-8-35)]: Effective MTU verified at 1414
INFO: 2016/12/07 03:22:59.473912 === received SIGINT/SIGTERM ===
*** exiting
INFO: 2016/12/07 03:23:18.262400 Command line options: map[port:6783 resolv-conf:/var/run/weave/etc/resolv.conf datapath:datapath dns-effective-listen-address:<IP_ADDRESS> dns-listen-address:<IP_ADDRESS>:53 http-addr:<IP_ADDRESS>:6784 ipalloc-range:<IP_ADDRESS>/12 name:2a:06:a8:e4:34:36 status-addr:<IP_ADDRESS>:6782 nickname:hinton]'
'

Docker info
root@hinton:~# docker info
Containers: 10
 Running: 6
 Paused: 0
 Stopped: 4
Images: 37
Server Version: 1.12.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 181
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local nvidia-docker
 Network: host bridge null weavemesh overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 3.19.0-22-generic
Operating System: Ubuntu 15.04
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 31.33 GiB
Name: hinton
ID: N5MI:J6FJ:32E2:SMDV:WE4Z:3AOZ:H5JB:SH6T:PWXR:3H6F:2L5U:L4RV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

@icy your symptoms are different; please start a new issue. Please include the output of ip link.

Do we think this issue is associated with the systemd-networkd overreach on CoreOS, which they have now developed a way to turn off?  So this could be closed?

I don't think we've seen this anymore after fixing the networkd configuration on CoreOS, so I would consider it closed.

Great, thanks.


boards: arm: Fix conditionalized pinmuxes for shared pin

A change was put in to conditionalize pinmuxes based on
Ethernet configuration but for the IMXRT1050/60/64-EVK
boards the USER_LED and ENET_RST share the same GPIO.
Samples like blinky would not work on these boards.
The change is to not conditionalize the shared pin.
fixes: #27473
Signed-off-by: David Leach<EMAIL_ADDRESS>

@MaureenHelm, are you okay with the way I changed this?


Doc: Remove python 2 vestiges from conf.py, traffic-server.py.

Sphinx 2.x generates warnings about removing Python 2 support. As we have already moved to Python 3 in general, it's best to clean up the documentation files to be fully Python 3.

[approve ci docs]

[approve ci docs]

[approve ci autest]


incoming-transfer, module and multisig endpoints

Closes #841
Needs unit tests

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

301 of 420 (71.67%)  changed or added relevant lines in 13 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.9%) to 34.401%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/transactions/converters/summary.rs
21
22
95.45%

src/routes/transactions/handlers/tests/transfers.rs
47
50
94.0%

src/routes/transactions/filters/tests/mod.rs
66
71
92.96%

src/routes/transactions/handlers/commons.rs
21
27
77.78%

src/routes/transactions/filters/module.rs
9
22
40.91%

src/routes/transactions/filters/transfer.rs
25
43
58.14%

src/routes/transactions/routes.rs
28
47
59.57%

src/routes/transactions/filters/multisig.rs
18
43
41.86%

src/routes/transactions/handlers/transfers.rs
53
82
64.63%

Files with Coverage Reduction
New Missed Lines
%

src/routes/transactions/models/summary.rs
2
2.83%

Totals

Change from base Build<PHONE_NUMBER>:
-0.9%

Covered Lines:
12299

Relevant Lines:
13989

💛  - Coveralls


Change references of OS X to macOS

Signed-off-by: James Hill-Khurana<EMAIL_ADDRESS>

Done, thanks!


[Campaign] Ensure Github workflow runs on docker image used by Production Distribution Build

Hi All,
This is coming from the campaign here:

https://github.com/opensearch-project/opensearch-build/issues/3966

Overview
We would like your CI check (specifically plugin build) in GitHub Repo to run on top of the Build Docker Images from production distribution pipeline.
This is to ensure every plugin repo will use the exact docker images we used in Jenkins build, to check their PRs and run tests before merging the code, so that issues can be detected earlier, and environment can be identical across teams.
Solutions
The Build Team has created a simple script to dynamically retrieve the current docker image name/tag, so everyone can easily pull the images for their CI checks.
We have a trial run of the above with k-NN team. The script retrieves the docker image dynamically, save output, and use it as the docker image to pull for the upcoming run:

https://github.com/opensearch-project/k-NN/pull/1099

Note that GitHub Actions only support LINUX docker container at the time of this writing, so we will add Windows containers later on as well as macOS.
Implementation Notes
We would like you to review above PR and implement similar changes. Note on line 33 of the above k-NN PR, -u and -p parameters needs to assign values accordingly.

OpenSearch Plugin:

          CI_IMAGE_VERSION=`opensearch-build/docker/ci/get-ci-images.sh -p centos7 -u opensearch -t build | head -1`

OpenSearch-Dashboards Plugin:

          CI_IMAGE_VERSION=`opensearch-build/docker/ci/get-ci-images.sh -p rockylinux8 -u opensearch-dashboards -t build | head -1`

Note that in the above k-NN PR, despite it being OpenSearch plugin, it still uses rockylinux8, as we initially plan to upgrade to rockylinux. We have since revert back to centos7 to support older versions of systems running k-NN lib. As a result, all OpenSearch plugins still uses centos7 for the time being, and all OpenSearch-Dashboards plugins can go to rockylinux8.
Completion Date
The above should be implemented by Nov. 1, 2023 (2023-11-01) by Plugin Owners to their repository.
And backport the changes to 2.x branch after merging in main branch.
Contacts
Please contact @peterzhuamazon for any questions on this campaign.
cc: @bbarani
Thanks.

We have a new approach established here.
Please see this sample workflow file from Alerting for example:
https://github.com/opensearch-project/alerting/blob/main/.github/workflows/multi-node-test-workflow.yml
Thanks.

I do not see any related build steps here for testing, only maven upload.
This repo needs to have a CI github actions to start with.
Thanks.


How are these SF-XL   downloaded from Google Earth?

Can you share the method of downloading photos from Google Earth to make SF-XL dataset?

We are not planning to release the code for downloading images from Google StreetView, although you can find some open-source repositories online that allow you to do that.

Thank you for your help. May I ask you another question?
      When I get 360° panoramas from Google Earth, how can I get the metadata of these panoramas at the same time, such as azimuth, latitude and longitude values, etc.?
      Looking forward to your reply, thank you again.


Fix odd issue caused by Adonis parenting Service.lua to Server or…

… Client
This fixes the Adonis failing to load error

Ok not it works


Add yarn.lock and .yarnclean

For those of us who use yarn, these files are nice to have around.  They speed up installs and ensure everyone using yarn is using exactly the same package versions.  NPM users can just ignore them so it works out great for everyone.

@AlexanderOtavka any info on how this changes the installation process?  It seems like adding a lockfile would freeze all child dependencies to a hard version, if it's observed by Yarn during install.  That's quite a firm stance on versioning for a little JavaScript library haha.
Also - I think this means we'd have to require that anyone contributing to this repo then use Yarn?  Otherwise the lockfile will get out of sync with the package.json, right?

The exact behavior is outlined on yarn's website.  Basically, it ensures that unless you explicitly upgrade, everyone stays on the same version.  It's okay if the lockfile gets momentarily out of sync with the package.json since using the yarn CLI will bring it back into sync - package.json is king.

@AlexanderOtavka right. It would seem this means I have to use Yarn to manage this package now.

Oh, ok.  You should probably add yarn.lock to the .gitignore so yarn users don't accidentally commit it then.  I'll make a PR for that.

Makes sense - thanks for switching the PRs!  I'm not against using Yarn, just not quite ready to change workflows.


License Request

Hi Gary,
Working on some open source projects taking this repo as a dependency. For that i need to license which this repo does not have. I was wondering if it was possible to add a license in this repo? Thanks in advance!

@hanyunx Sure, I've added the MIT license https://github.com/garslo/gogen/commit/f497ca02dd4c54af4ab00d61e133da0b4c96ecb8


pkg/{identity,ipcache}: check for nil identity in slice of identities

As the slice of identities can contain identities that were not
previously allocated, set as nil, we need to check if they are nil
while iterating over the slice of identities to be released or
inserted into the kvstore.
Fixes: 6494f0e01364 ("identity: Guarantee 1:1 prefix <-> identity slices")
Signed-off-by: André Martins<EMAIL_ADDRESS>

This change is

test-me-please