Added logging for client & work server

When looking at the logs, using docker-compose -t, for a client or the work server there was no clear indication of what action was being performed. I added a few statements that would make following and understanding the logs easier
@pereze03 can you please review and check to see if there are any other log messages that could be added

What does the output look like now?  Run the system locally and let it run for a minute or so.  The do docker-compose logs client1 and cut-and-paste the logs into a comment on this PR.

client1_1         | 2023-02-06T16:37:08.081638812Z Your ID is:  135
client1_1         | 2023-02-06T16:37:08.081709486Z performing job
client1_1         | 2023-02-06T16:37:08.081717650Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081722459Z performing job
client1_1         | 2023-02-06T16:37:08.081726841Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081731126Z performing job
client1_1         | 2023-02-06T16:37:08.081735444Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081739633Z performing job
client1_1         | 2023-02-06T16:37:08.081743757Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081748451Z performing job
client1_1         | 2023-02-06T16:37:08.081752694Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081756975Z performing job
client1_1         | 2023-02-06T16:37:08.081761161Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081765394Z performing job
client1_1         | 2023-02-06T16:37:08.081769590Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081773761Z performing job
client1_1         | 2023-02-06T16:37:08.081777933Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081782118Z performing job
client1_1         | 2023-02-06T16:37:08.081786279Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081790453Z performing job
client1_1         | 2023-02-06T16:37:08.081794583Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081798835Z performing job
client1_1         | 2023-02-06T16:37:08.081802980Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081807180Z performing job
client1_1         | 2023-02-06T16:37:08.081811350Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081815573Z performing job
client1_1         | 2023-02-06T16:37:08.081819760Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081823944Z performing job
client1_1         | 2023-02-06T16:37:08.081828048Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081832212Z performing job
client1_1         | 2023-02-06T16:37:08.081836350Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081840557Z performing job
client1_1         | 2023-02-06T16:37:08.081844737Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081848942Z performing job
client1_1         | 2023-02-06T16:37:08.081853052Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081857224Z performing job
client1_1         | 2023-02-06T16:37:08.081861346Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081865616Z performing job
client1_1         | 2023-02-06T16:37:08.081869759Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081873916Z performing job
client1_1         | 2023-02-06T16:37:08.081878051Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081882236Z performing job
client1_1         | 2023-02-06T16:37:08.081895458Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081900515Z performing job
client1_1         | 2023-02-06T16:37:08.081904829Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081909075Z performing job
client1_1         | 2023-02-06T16:37:08.081913273Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081917459Z performing job
client1_1         | 2023-02-06T16:37:08.081921613Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081925831Z performing job
client1_1         | 2023-02-06T16:37:08.081930017Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081934202Z performing job
client1_1         | 2023-02-06T16:37:08.081938403Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081942576Z performing job
client1_1         | 2023-02-06T16:37:08.081946723Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081950921Z performing job
client1_1         | 2023-02-06T16:37:08.081955083Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081959264Z performing job
client1_1         | 2023-02-06T16:37:08.081963473Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081967747Z performing job
client1_1         | 2023-02-06T16:37:08.081971912Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081976099Z performing job
client1_1         | 2023-02-06T16:37:08.081980259Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081984452Z performing job
client1_1         | 2023-02-06T16:37:08.081988640Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.081992835Z performing job
client1_1         | 2023-02-06T16:37:08.081996997Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082001185Z performing job
client1_1         | 2023-02-06T16:37:08.082005363Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082009532Z performing job
client1_1         | 2023-02-06T16:37:08.082013711Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082019346Z performing job
client1_1         | 2023-02-06T16:37:08.082023842Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082028256Z performing job
client1_1         | 2023-02-06T16:37:08.082032418Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082036609Z performing job
client1_1         | 2023-02-06T16:37:08.082040726Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082044903Z performing job
client1_1         | 2023-02-06T16:37:08.082049074Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082053269Z performing job
client1_1         | 2023-02-06T16:37:08.082057399Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082061605Z performing job
client1_1         | 2023-02-06T16:37:08.082065740Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082151314Z performing job
client1_1         | 2023-02-06T16:37:08.082172255Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082175616Z performing job
client1_1         | 2023-02-06T16:37:08.082178803Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082181967Z performing job
client1_1         | 2023-02-06T16:37:08.082185073Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082188225Z performing job
client1_1         | 2023-02-06T16:37:08.082191343Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082194500Z performing job
client1_1         | 2023-02-06T16:37:08.082197679Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082200788Z performing job
client1_1         | 2023-02-06T16:37:08.082203893Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082207074Z performing job
client1_1         | 2023-02-06T16:37:08.082210138Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082213325Z performing job
client1_1         | 2023-02-06T16:37:08.082216409Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082219524Z performing job
client1_1         | 2023-02-06T16:37:08.082222610Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082225787Z performing job
client1_1         | 2023-02-06T16:37:08.082228883Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082231990Z performing job
client1_1         | 2023-02-06T16:37:08.082235124Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082238245Z performing job
client1_1         | 2023-02-06T16:37:08.082241315Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082244457Z performing job
client1_1         | 2023-02-06T16:37:08.082247548Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082250675Z performing job
client1_1         | 2023-02-06T16:37:08.082253763Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082256916Z performing job
client1_1         | 2023-02-06T16:37:08.082260010Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082263220Z performing job
client1_1         | 2023-02-06T16:37:08.082266320Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082269472Z performing job
client1_1         | 2023-02-06T16:37:08.082272571Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082275679Z performing job
client1_1         | 2023-02-06T16:37:08.082278771Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082281912Z performing job
client1_1         | 2023-02-06T16:37:08.082285000Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082288210Z performing job
client1_1         | 2023-02-06T16:37:08.082291328Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082294463Z performing job
client1_1         | 2023-02-06T16:37:08.082297560Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082304899Z performing job
client1_1         | 2023-02-06T16:37:08.082308407Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082311561Z performing job
client1_1         | 2023-02-06T16:37:08.082314650Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082317779Z performing job
client1_1         | 2023-02-06T16:37:08.082320994Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082324124Z performing job
client1_1         | 2023-02-06T16:37:08.082327214Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082330407Z performing job
client1_1         | 2023-02-06T16:37:08.082339718Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082343059Z performing job
client1_1         | 2023-02-06T16:37:08.082346210Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082349357Z performing job
client1_1         | 2023-02-06T16:37:08.082352520Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082355669Z performing job
client1_1         | 2023-02-06T16:37:08.082358789Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082361994Z performing job
client1_1         | 2023-02-06T16:37:08.082365865Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082369143Z performing job
client1_1         | 2023-02-06T16:37:08.082372229Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082375411Z performing job
client1_1         | 2023-02-06T16:37:08.082378527Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082381675Z performing job
client1_1         | 2023-02-06T16:37:08.082384808Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082387925Z performing job
client1_1         | 2023-02-06T16:37:08.082391029Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082394175Z performing job
client1_1         | 2023-02-06T16:37:08.082397260Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082400395Z performing job
client1_1         | 2023-02-06T16:37:08.082403498Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082406616Z performing job
client1_1         | 2023-02-06T16:37:08.082409720Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082412887Z performing job
client1_1         | 2023-02-06T16:37:08.082415988Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082419125Z performing job
client1_1         | 2023-02-06T16:37:08.082422247Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082425348Z performing job
client1_1         | 2023-02-06T16:37:08.082428449Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082431594Z performing job
client1_1         | 2023-02-06T16:37:08.082434696Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082437832Z performing job
client1_1         | 2023-02-06T16:37:08.082440940Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082448409Z performing job
client1_1         | 2023-02-06T16:37:08.082451829Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082455009Z performing job
client1_1         | 2023-02-06T16:37:08.082458131Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082461262Z performing job
client1_1         | 2023-02-06T16:37:08.082464456Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082467576Z performing job
client1_1         | 2023-02-06T16:37:08.082470695Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082487065Z performing job
client1_1         | 2023-02-06T16:37:08.082490392Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082493538Z performing job
client1_1         | 2023-02-06T16:37:08.082496623Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082499792Z performing job
client1_1         | 2023-02-06T16:37:08.082502906Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082506043Z performing job
client1_1         | 2023-02-06T16:37:08.082509173Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082512406Z performing job
client1_1         | 2023-02-06T16:37:08.082515549Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082518664Z performing job
client1_1         | 2023-02-06T16:37:08.082521792Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082524989Z performing job
client1_1         | 2023-02-06T16:37:08.082528107Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082531305Z performing job
client1_1         | 2023-02-06T16:37:08.082534401Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082537604Z performing job
client1_1         | 2023-02-06T16:37:08.082540697Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082543866Z performing job
client1_1         | 2023-02-06T16:37:08.082546978Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082550111Z performing job
client1_1         | 2023-02-06T16:37:08.082553218Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082556454Z performing job
client1_1         | 2023-02-06T16:37:08.082559595Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082562747Z performing job
client1_1         | 2023-02-06T16:37:08.082565839Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082568985Z performing job
client1_1         | 2023-02-06T16:37:08.082572132Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082575312Z performing job
client1_1         | 2023-02-06T16:37:08.082578407Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082581550Z performing job
client1_1         | 2023-02-06T16:37:08.082584652Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082587824Z performing job
client1_1         | 2023-02-06T16:37:08.082595082Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082598623Z performing job
client1_1         | 2023-02-06T16:37:08.082601861Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082605035Z performing job
client1_1         | 2023-02-06T16:37:08.082609060Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082612419Z performing job
client1_1         | 2023-02-06T16:37:08.082615617Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082618798Z performing job
client1_1         | 2023-02-06T16:37:08.082621941Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082625119Z performing job
client1_1         | 2023-02-06T16:37:08.082628274Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082631405Z performing job
client1_1         | 2023-02-06T16:37:08.082634581Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082637779Z performing job
client1_1         | 2023-02-06T16:37:08.082640919Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082644084Z performing job
client1_1         | 2023-02-06T16:37:08.082647258Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082650454Z performing job
client1_1         | 2023-02-06T16:37:08.082653604Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082656745Z performing job
client1_1         | 2023-02-06T16:37:08.082659865Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082663030Z performing job
client1_1         | 2023-02-06T16:37:08.082666172Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082669318Z performing job
client1_1         | 2023-02-06T16:37:08.082672449Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082675629Z performing job
client1_1         | 2023-02-06T16:37:08.082678790Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082681961Z performing job
client1_1         | 2023-02-06T16:37:08.082685067Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082688242Z performing job
client1_1         | 2023-02-06T16:37:08.082691443Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082694603Z performing job
client1_1         | 2023-02-06T16:37:08.082697730Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082700924Z performing job
client1_1         | 2023-02-06T16:37:08.082704077Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082707240Z performing job
client1_1         | 2023-02-06T16:37:08.082710380Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082713510Z performing job
client1_1         | 2023-02-06T16:37:08.082716681Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082719799Z performing job
client1_1         | 2023-02-06T16:37:08.082722889Z performing job
client1_1         | 2023-02-06T16:37:08.082726041Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082732084Z performing job
client1_1         | 2023-02-06T16:37:08.082735593Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082738751Z performing job
client1_1         | 2023-02-06T16:37:08.082741847Z performing job
client1_1         | 2023-02-06T16:37:08.082744997Z performing job
client1_1         | 2023-02-06T16:37:08.082748146Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082751290Z performing job
client1_1         | 2023-02-06T16:37:08.082754429Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082757548Z performing job
client1_1         | 2023-02-06T16:37:08.082760713Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082763875Z performing job
client1_1         | 2023-02-06T16:37:08.082767067Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082770188Z performing job
client1_1         | 2023-02-06T16:37:08.082773295Z performing job
client1_1         | 2023-02-06T16:37:08.082767067Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082770188Z performing job
client1_1         | 2023-02-06T16:37:08.082773295Z performing job
client1_1         | 2023-02-06T16:37:08.082776449Z There was an error handling this response.
client1_1         | 2023-02-06T16:37:08.082779595Z performing job
client1_1         | 2023-02-06T16:37:08.082782708Z performing job
client1_1         | 2023-02-06T16:37:08.082785835Z performing job
client1_1         | 2023-02-06T16:37:08.082788942Z performing job
client1_1         | 2023-02-06T16:37:08.082792056Z performing job
client1_1         | 2023-02-06T16:37:08.082795161Z performing job
client1_1         | 2023-02-06T16:37:08.082798266Z performing job
client1_1         | 2023-02-06T16:37:08.082801403Z performing job
client1_1         | 2023-02-06T16:37:08.082804538Z performing job
client1_1         | 2023-02-06T16:37:08.082807655Z performing job
client1_1         | 2023-02-06T16:37:08.082810789Z performing job
client1_1         | 2023-02-06T16:37:08.082813900Z performing job
client1_1         | 2023-02-06T16:37:08.082817036Z performing job
client1_1         | 2023-02-06T16:37:08.082820159Z performing job
client1_1         | 2023-02-06T16:37:08.082823268Z performing job
client1_1         | 2023-02-06T16:37:08.082826380Z performing job
client1_1         | 2023-02-06T16:37:08.082829502Z performing job
client1_1         | 2023-02-06T16:37:08.082832664Z performing job
client1_1         | 2023-02-06T16:37:08.082835783Z performing job
client1_1         | 2023-02-06T16:37:08.082838952Z performing job
client1_1         | 2023-02-06T16:37:08.082842041Z performing job
client1_1         | 2023-02-06T16:37:08.082845130Z performing job
client1_1         | 2023-02-06T16:37:08.082848229Z performing job
client1_1         | 2023-02-06T16:37:08.082851346Z performing job
client1_1         | 2023-02-06T16:37:08.082854439Z performing job
client1_1         | 2023-02-06T16:37:08.082857549Z performing job
client1_1         | 2023-02-06T16:37:08.082860697Z performing job
client1_1         | 2023-02-06T16:37:08.082863811Z performing job
client1_1         | 2023-02-06T16:37:08.082866907Z performing job

@pereze03 That appears to be the old logs that you pasted, make sure you are using the right branch when running locally.

@KyleSmilon I know it looks that way but this was actually while in the logging branch. Can you check your own logs? Do you see the other prints?

Logging for 'work_server.py' now shows this as output:
work_server_1     | Job received: documents for client:  599
work_server_1     | Work_server received job for client:  599
work_server_1     | Writing results to disk
work_server_1     | Job success for client:599, job:  458611
It does so for each client.

Updated output for client.py
client1_1         | Staring New Job
client1_1         | Job ID: 74367
client1_1         | Sending Job to Work Server
client1_1         | Job output path: FAA/FAA-2016-8787/FAA-2016-8787.json
client1_1         | Processing job
client1_1         | Staring New Job
client1_1         | Job ID: 74449
client1_1         | Sending Job to Work Server
client1_1         | Job output path: FDA/FDA-2016-V-2480/FDA-2016-V-2480.json
client1_1         | Processing job

Updated output for client.py
client1_1         | Processing job from work server
client1_1         | Staring New Job
client1_1         | Job ID: 175598
client1_1         | Performing job https://api.regulations.gov/v4/dockets/FDA-1999-F-0077
client1_1         | Sending Job 175598 to Work Server
client1_1         | Job output path: FDA/FDA-1999-F-0077/FDA-1999-F-0077.json


Make failed on macOS

Describe the bug
Following the Dev Guide, make failed with the following details
2018-08-28T06:18:08.827058Z	info	skipping cluster registries, no kube-client created
2018-08-28T06:18:08.827134Z	info	Adding Config registry adapter
2018-08-28T06:18:08.827370Z	info	ads	Starting ADS server with rateLimiter=10 burst=100
2018-08-28T06:18:08.827649Z	info	Discovery service started at http=[::]:57075 grpc=[::]:57076
Listening HTTP/1.1 on 57079
Listening HTTP/1.1 on 57080
Listening HTTP/1.1 on 57081
Listening HTTP/1.1 on 57082
Listening GRPC on 57083
Listening GRPC on 57084
PARSE ERROR: Argument: --log-format
             Couldn't find match for argument

Brief USAGE:
   GOPATH/out/darwin_amd64/release/envoy
                                        [--disable-hot-restart]
                                        [--max-obj-name-len <uint64_t>]
                                        [--max-stats <uint64_t>] [--mode
                                        <string>] [--parent-shutdown-time-s
                                        <uint32_t>] [--drain-time-s
                                        <uint32_t>]
                                        [--file-flush-interval-msec
                                        <uint32_t>] [--service-zone
                                        <string>] [--service-node <string>]
                                        [--service-cluster <string>]
                                        [--hot-restart-version]
                                        [--restart-epoch <uint32_t>]
                                        [--log-path <string>] [-l <string>]
                                        [--local-address-ip-version
                                        <string>] [--admin-address-path
                                        <string>] [--v2-config-only] [-c
                                        <string>] [--concurrency
                                        <uint32_t>] [--base-id <uint32_t>]
                                        [--] [--version] [-h]

For complete USAGE and HELP type:
   GOPATH/out/darwin_amd64/release/envoy --help

--- FAIL: TestAgent (10.05s)
	agent_test.go:90: failed to start envoy after 10s. Error: Get http://<IP_ADDRESS>:57086/server_info: dial tcp <IP_ADDRESS>:57086: connect: connection refused
FAIL
FAIL	istio.io/istio/pkg/test/framework/components/apps/local/envoy/agent/pilot	10.095s

I'm doing it on macOS.
Branch:
$ git branch
* (HEAD detached at origin/master)
  collab-gcp-identity
  master

Most recent git commitId: 7904b4d58844582f4e87189020938b840bc0f378

Unfortunately the MacOS Envoy build is not at the same level as the Linux one. I believe the current binary which is being downloaded for the local test is missing that flag.
@rshriram what's the process of updating the Darwin build of Envoy? I mean, I can build it but who can update the online binary?

Hi @rshriram , can you help take a look at this?

@dunjut I have the current proxy built for MacOS available here: https://github.com/ymesika/istio-proxy-darwin/raw/master/envoy.tgz
This is temporary until I find out how to update the one downloaded by the scripts.

The one used by the scripts is out of date afaik. And it is only pushed manually.


Can't Open Settings

Since i don't have a numpad, i can't open the settings page. Perhaps something in settings to change menu keybind?

Same problem here

Fixed in https://github.com/rvazarkar/NGUInjector/commit/d66207fa299c07e3c300fbfae1e69130e6f8c359.
New version will use F1-F4 instead of numpad, hopefully theres no conflicts


account-sys: add whitelist to account creation

[ ] Add contract that stores whitelist for testnet of which accounts are allowed to add new accounts.

Fractally accounts are hardcoded to be able to add and remove items from the whitelist.


how can i convert h5 to kmodel

Thank you for good repo.
I want to convert h5 to kmodel. but it doesn't work on tf2.1
How did you convert h5 file to kmodel?

I made kmodel. Thank you

@acabadw22 could you share it? Thanks.


Does not seem to work at all.

I am adept at powewscript scripts on Windows 10 and ran the script repeatedly but it seems not to remove anything.
Either Microsoft is on to this and prevents it from running or something on the OS is preventing it from completing successfully.
I have tried disabling SVM (Virtualization) in the bios as some system protection relies on virtualising parts of the OS to prevent tampering.
As well, most of the threads here seem to be complaining about how the script hosed their systems. All I can say is the author of the script warned you when you downloaded it, that he is not responsible for what occurs.
Any suggestions as to why the script seems to do nothing for me, while it seems to do undesirable things for everyone else.
And Yes, I did run as administrator in powershell.

Same, the powershell lines all seem to working without errors, but nothing actually changes. tried multiple times. after completely updating windows, several restarts but nothing

for me it has always worked fine, I just tried for you to revert all the changed, and of course re-DEBLOATED and everything is working as it should!

Can confirm for some reason its not working at all. Nothing gets removed I still have store and all store apps on Windows.

It appears that windows is rapidly reinstalling all the bloat ware after using the tool.  I caught it doing it.  I am using the latest build of windows 10 using a media creation tool.  I followed ever step saw them being removed and then it all got redownloaded in a flash.  I wonder if there is a way to prevent that?  Somethings are still disabled like the one drive.  Anyways somethings gone are better than nothing but it seems windows is fighting back.

It appears that windows is rapidly reinstalling all the bloat ware after using the tool. I caught it doing it. I am using the latest build of windows 10 using a media creation tool. I followed ever step saw them being removed and then it all got redownloaded in a flash. I wonder if there is a way to prevent that? Somethings are still disabled like the one drive. Anyways somethings gone are better than nothing but it seems windows is fighting back.

I know what I am doing and have been building computers running dos and linux for 30 years.  I doubt i did something wrong.  I know how to use the powershell in admin mode.  I use the media creation tool because its easy and I pay for my windows.  I was able to remove most of the bloatware manually.  So I will worry about this when I need to install windows again but just a heads up it does reinstall things with the august 8th iso image.

No need to get on your high hills... if you write a comments it means you wanted help, and since you have 30 years of backgrounds....
And what August 8th iso are you talking about?? last Win10 ISO is May 2004.....

How is you did it wrong help?  Second Its what downloaded with the tool.  I didn't use an iso image dude.  If you don't want to help just don't respond.

Apparently when selecting nvidia in custom it doesn't delete anything you must unselect nvidia in customs then it will work.

Apparently when selecting nvidia in custom it doesn't delete anything you must unselect nvidia in customs then it will work.

Are you referring to the GUI script? As I have had this issue with both the normal script and the SysPrep script (run in sysprep of course) and, albeit rare, it does sometimes just NOT do anything, no errors, no negative feedback. This has happened across various machines and on multiple versions of Windows 10.
I don't see why this caused beef in a GitHub issue though..?
It does seem inconsistent and non-reproducible from my experience.
This has not happened in a long time to me, though to note - I now install Windows with no internet connection to the machine, do everything I need to do, run this script etc. before I reconnect.
My guess is Windows is updating the apps as they are being removed and so appears like they are being reinstalled as soon as they are removed. This is not Windows "fighting back", just a matter of timing.
Even on the most up-to-date ISOs, the apps will rarely be the current version.

@grydian - my apologies for not responding for a very long time. I will look into a way to see if the apps can be prevented from being reinstalled.


groovy: 2.5.3 -> 2.5.4

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/groovy/versions.
meta.description for groovy is: '"An agile dynamic language for the Java Platform"'.

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovy.ico had a zero exit code or showed the expected version
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/grape passed the binary check.
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/java2groovy passed the binary check.
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovy passed the binary check.
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovydoc passed the binary check.
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovyc passed the binary check.
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovysh passed the binary check.
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovyConsole passed the binary check.
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/grape_completion had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovyConsole_completion had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovyc_completion had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovydoc_completion had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovysh_completion had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovy_completion had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/startGroovy had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.grape-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.java2groovy-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.groovy-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.groovydoc-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.groovyc-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.groovysh-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.groovyConsole-wrapped had a zero exit code or showed the expected version
7 of 22 passed binary check by having a zero exit code.
3 of 22 passed binary check by having the new version present in output.
found 2.5.4 with grep in /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4
directory tree listing: https://gist.github.com/d219e4c24fe4666ff8a322c899edc1c7
du listing: https://gist.github.com/ceeebb2a31bc85297e0969194aa0bd27

Rebuild report (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
groovy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A groovy https://github.com/r-ryantm/nixpkgs/archive/c630d8c69737a2743b70ea66553ffc481ce395b2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4
ls -la /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin

cc @pSub for testing.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: groovy
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: groovy
Partial log (click to expand)
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovy_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/bash"
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovydoc_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/bash"
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.groovysh-wrapped: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovysh_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/bash"
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.grape-wrapped: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/startGroovy: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/.java2groovy-wrapped: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4/bin/groovyConsole_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4...
/nix/store/hq9c8hyrm5xy44px363xj2p7rik69w4b-groovy-2.5.4

Success on x86_64-darwin (full log)
Attempted: groovy
Partial log (click to expand)
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4/bin/.groovysh-wrapped: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/n9hba031gjky8hpjgx9fnlaxhidyzxbz-bash-4.4-p23/bin/sh"
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4/bin/.java2groovy-wrapped: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/n9hba031gjky8hpjgx9fnlaxhidyzxbz-bash-4.4-p23/bin/sh"
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4/bin/grape_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/n9hba031gjky8hpjgx9fnlaxhidyzxbz-bash-4.4-p23/bin/bash"
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4/bin/groovy_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/n9hba031gjky8hpjgx9fnlaxhidyzxbz-bash-4.4-p23/bin/bash"
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4/bin/groovyc_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/n9hba031gjky8hpjgx9fnlaxhidyzxbz-bash-4.4-p23/bin/bash"
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4/bin/groovyConsole_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/n9hba031gjky8hpjgx9fnlaxhidyzxbz-bash-4.4-p23/bin/bash"
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4/bin/groovydoc_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/n9hba031gjky8hpjgx9fnlaxhidyzxbz-bash-4.4-p23/bin/bash"
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4/bin/groovysh_completion: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/n9hba031gjky8hpjgx9fnlaxhidyzxbz-bash-4.4-p23/bin/bash"
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4/bin/startGroovy: interpreter directive changed from "/usr/bin/env sh" to "/nix/store/n9hba031gjky8hpjgx9fnlaxhidyzxbz-bash-4.4-p23/bin/sh"
/nix/store/117nib25ckq4yixw54w6l5b6x20p2n4i-groovy-2.5.4


Fix AnimationTrackEditor doesn't open when selecting AnimationPlayer node while another Editor is open

Fixed #72811. Follow up #72420.
It seems unnecessary to update flag for the editor closing.

I uploaded the video as #72811.

Thanks!


SharePoint Search is not persistent and not working!

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[X] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[X] 💥 FireFox
[X] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version
Node.js version
etc

Describe the bug / error
We are having a strange issue since today morning. We have couple of Search webparts in our Home page which is an Hub site. The webparts are not loading results even with out of box handlebar templates. We tested the standard sharepoint search, the results are not persistent. Sometimes, results are empty. If we look into Network tab, we are receiving 500 error for /_api/search/postquery endpoint. Please refer the screenshot here:

Steps to reproduce

We can reproduce this via PnP Modern search webpart immediately. If you add the webpart to a page, it fails immediately.
If you search in standard SharePoint, resutls are empty sometime and sometimes we get results.

Expected behavior
Search work normally without failing

@arunakshi - is it still happening? Or maybe it was a temporary glitch?

@AJIXuMuK This issue was persisted for some regions of users until end of day. I don't see anymore the incident related to SharePoint Search in message center also. Hope this was a temporary glitch.

Search simply stopped working at all for me in my dev tenant. I create a brand new team, add a document to the default documents library, force crawl on site, force crawl on list, nothing gets crawled,  no result at all.
I also get a system error when trying to add a mapping in a RefinableString managed property through the search schema UI, looks like the search in general is broken?

@AJIXuMuK I was checking today morning. The same error occured again for me and it didn't occur for my colleague. We both are accessing the site from different regions. Is it fixed perminantely? Could you please verify.

Looks like this is resolved for us now.

Can confirm this is resolved.


Some SVG icons are not rendered

Some SVG icons are not loading on my local and in the console I get 404. This happens for example on the category page for: arrow_up.svg, arrow_down.svg and chevron_up.svg:

I don't know if it's the same bug but probably (something linked to webpack build-assets)
It also happens on the dashboard.
saleor/static/dashboard/components/_breadcrumbs.scss:17
        content: url('/static/dashboard/images/chevron_right.svg');
This works in local but not in production env.

It may be related, we'll check that. Thanks for reporting @mperesson.

Closed by #1355

Is this issue resolved? Because in production it is still not displaying svg images

@saqibkhan2523 what is the developer console showing (console and network tab)? Can be a CORS issue or other.
I don't have issues on production here.

There is no error it is just picking up pass-invisible.svg from assets in place of the other.svg images like search.svg I tried replacing these with png and images gets displayed, but the images are getting distorted that way.

There was no changes done to the javascript source code? Or is there no Rockerloader or whatever it's called from Cloudflare to bundle javascript?
And the SVG files are fully loaded? (if you look into the network tab and you look at the response data). What does the inspector show when you inspect a part with a SVG file not showing?

I havent done any change in js. and when I inspect the svg image it is displaying the link to the image https://mybucket.s3.amazonaws.com/images/google-logo.svg

@saqibkhan2523 sent you a message about the PR over Gitter.

Hi,
Still facing this issue.
"pass-invisible.svg" not rendering as STATIC_URL doesn't get replaced by the S3 Url/Custom Domain Url.
As STATIC_URL environment variable is not changed for Webpack to find, we will need to change it to the new URL.
Possible fix would be:
S3_URL = 'https://%s.s3.amazonaws.com/' % AWS_STORAGE_BUCKET_NAME
STATIC_URL = S3_URL + 'assets/'

Your url is not right.
it should be like this S3_URL = https://**mybucke**t.s3.amazonaws.com


bump rubocop to enforce what our style dictates

@moolitayer @simon3z

@grosser please elaborate why are all those style changes needed and why rubocop needs to be bumped for that. thanks

style changes are needed because they are "what our style dictates" according to @moolitayer in https://github.com/abonas/kubeclient/pull/195 ... and we need a newer rubocop version to enforce that

style changes are needed because they are "what our style dictates" according to @moolitayer in #195 ... and we need a newer rubocop version to enforce that

I can't find in that issue the discussion regarding rubocop. do you have the exact link? cc @moolitayer

@abonas me and @simon3z have been enforcing this for a while on incoming PRs. Where do you stand on this?

@abonas me and @simon3z have been enforcing this for a while on incoming PRs. Where do you stand on this?

@moolitayer
I'm OK with it as long as:

indeed all past code is aligned to the style - which looks like what this PR should achieve
there is a clear pointer for the required style in the readme so it is crystal clear to whoever makes code changes what is required
openshift client is aligned and enforced to it as well

I'm not clear why rubocop version bump is needed (not objecting to it, just want to understand) - are those new rules that you are interested to enforce?

newer rubocop version has this check
all styles got adjusted ... rubocop will alert new contributors.
On Wed, Mar 29, 2017 at 1:54 AM, abonas<EMAIL_ADDRESS>wrote:

@abonas https://github.com/abonas me and @simon3z
https://github.com/simon3z have been enforcing this for a while on
incoming PRs. Where do you stand on this?
@moolitayer https://github.com/moolitayer
I'm OK with it as long as:

indeed all past code is aligned to the style - which looks like
what this PR should achieve
there is a clear pointer for the required style in the readme so it
is crystal clear to whoever makes code changes what is required
openshift client is aligned and enforced to it as well

I'm not clear why rubocop version bump is needed (not objecting to it,
just want to understand) - are those new rules that you are interested to
enforce?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/abonas/kubeclient/pull/236#issuecomment-290026498,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAsZ_Wg66YuFpJ6w7tmSQ_oy5nWrbBjks5rqhxAgaJpZM4MdewM
.

let's start here and then I can make the same PR for openshift client
On Wed, Mar 29, 2017 at 7:43 AM, Michael Grosser<EMAIL_ADDRESS>wrote:

newer rubocop version has this check
all styles got adjusted ... rubocop will alert new contributors.
On Wed, Mar 29, 2017 at 1:54 AM, abonas<EMAIL_ADDRESS>wrote:

@abonas https://github.com/abonas me and @simon3z
https://github.com/simon3z have been enforcing this for a while on
incoming PRs. Where do you stand on this?
@moolitayer https://github.com/moolitayer
I'm OK with it as long as:

indeed all past code is aligned to the style - which looks like
what this PR should achieve
there is a clear pointer for the required style in the readme so
it is crystal clear to whoever makes code changes what is required
openshift client is aligned and enforced to it as well

I'm not clear why rubocop version bump is needed (not objecting to it,
just want to understand) - are those new rules that you are interested to
enforce?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/abonas/kubeclient/pull/236#issuecomment-290026498,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAsZ_Wg66YuFpJ6w7tmSQ_oy5nWrbBjks5rqhxAgaJpZM4MdewM
.

let's start here and then I can make the same PR for openshift client

it was brought to my attention that openshift client has much lower priority than I thought, so it probably won't be needed there.

The only issue I have with this change is that the Readme file code examples should also have parenthesis on method calls.
Thanks for doing this @grosser

looked at the readme, tons of calls and not part of this codebase ... also this PR is big enough.
can we please get this merged now ?

I'm find with leaving the README for next iteration. @abonas has the final call

The readme is definitely part of this codebase (unless I misunderstood what that comment meant), but I am OK with updating it in a separate PR as long as it happens ASAP

Endless PR discussions and waiting around is demotivating for me, merge if
it's better then before.
I'd not consider the Readme part of the codebase since it is not 'our' code
/ not examples on how to write this gem, but examples for other people to
copy-paste.
I'll still do the conversion since it's nice to be in sync.
On Mon, Apr 3, 2017 at 5:04 AM, abonas<EMAIL_ADDRESS>wrote:

The readme is definitely part of this codebase (unless I misunderstood
what that comment meant), but I am OK with updating it in a separate PR as
long as it happens ASAP
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/abonas/kubeclient/pull/236#issuecomment-291123556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAsZ6K_-mVO51STa_ndIZmkcUrl1TR_ks5rsOA8gaJpZM4MdewM
.


Rocketpool Mainnet QA

Review Info

Description
Info

Subgraph Reviewed
https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/name/benreilly19/rocketpool&tab=protocol

Schema Version
1.3.0

Subgraph Version
1.0.1

Methodology Version
1.0.0

Evidence Spreadsheet
https://docs.google.com/spreadsheets/d/1G_N0W8q1UaOt0YqgZVTrOyKeObEM9S7o/edit?usp=sharing&ouid=104027705798814439445&rtpof=true&sd=true

Metric to Review
TVL

Subgraph's TVL data shows a seven-day average discrepancy of 9.30% with Defi Llama data. Furthermore, we have computed the implied TVL using the official website data and the results are in line with Defi Llama data. This implies that Defi Llama data is more accurate than the TVL data of the subgraph.
See 'Protocol' and 'Support-Implied-TVL' sheets for more information.

Subgraph TVL 7-day average
Defi Llama 7-day average
Absolute Difference
% Difference

349,138,759
385,051,231
-35,912,472
-9.30%

Recent Subgraph TVL
Implied TVL
Absolute Difference
% Difference

351,798,821
392,741,941
-40,943,120.11
-10.42%

Revenue

Daily revenue data must not be zero. Our computations for the implied revenue show that the total revenue for the recent data must be around $17.7 million. The protocol side revenue should also be larger than the supply side revenue as the node operators take commissions from LPs by reducing their staking rewards.
Refer to 'Protocol' and 'Support-Implied-Revenue' sheets

Subgraph Daily Supply Side Revenue
Implied Revenue
Absolute Difference
% Difference

0
6,209,738.96
-6,209,738.96
-100%

Subgraph Daily Protocol Side Revenue
Implied Revenue
Absolute Difference
% Difference

0
11,532,372.35
-11,532,372.35
-100%

Subgraph Total Daily Revenue
Implied Revenue
Absolute Difference
% Difference

0
17,742,111.31
-17,742,111.31
-100%

Pool Overview

TVL has a discrepancy of about 10% against Defi Llama and implied TVL data. See the analysis under TVL section.
Input tokens must only be in ETH.
Base Yield should not be zero as there is supply side revenue. See 'Support-Implied-Revenue' sheet for more information.

Please refer to the attached worksheet for more details.

@zdql - Bumping this QA for Rocket Pool

@bye43 Daily revenue being 0 is due to my methodology of only tracking revenue when beacon chain rewards are updated. This is flawed, but I'm not sure of a better methodology. Any suggestions for other ways to track this more regularly?

@bye43 tagging you to get a review of the the QA changes on this? https://okgraph.xyz/?q=benreilly19%2Frocketpool
If there are things to change @zdql will address in a separate PR, but we will merge #1427 this week

All good now @bye43 ?

@dmelotik Can you close this whenever it gets backfilled?

Yes I will @bye43

all done @bye43


Add poligrain as dependency and remove overlapping code

This should resolve OpenSenseAction/poligrain#60.
I added poligrain as a dependency and removed the grid intersection code. In the validation part and in the related example notebook, poligrain is now being imported.
Alternatively, the related code in validator.py could be removed or shifted to poligrain I assume.

Thanks for cleaning up pycomlink 👍
Please note that you also need to adjust dependencies in requirements.txt, see #152 (you do not have to remove tensorflow there, though, because Erlend will do that in his next PR)

I am trying to find out why readthedocs does not build. But, since the docs of pycomlink are a mess, that is not super important now...

Changing Python version to 3.10 for readthedocs build results in different error, already earlier in the build...

okay, here is the issue that points to our problem https://github.com/CrossNox/m2r2/issues/68
Solution there

Adding docutils>=0.18.1,<0.21 to my requirements.txt fixed it.

But maybe we can completely get rid of m2r2.

Let's track the readthedocs problem in #154 and merge this. Thanks @nblettner


Android 10 support

Hi,
I'm trying to get the serial of a device with Android 10 and it returns "unknown". With older versions of Android, works fine.
I found this link about the new Android version:
https://developer.android.com/about/versions/10/privacy/changes
Has someone the same problem?
Many thanks.

Hi,
This is my little contribution.
As I see, in this class https://github.com/Paldom/UniqueDeviceID/blob/master/src/android/UniqueDeviceID.java the deviceId is calculated by this formula (line 77):
uuid = androidID + deviceID + simID;

Since deviceID and simID is not longer supported in Android 10, you only have the androidID to identify the device (as i know, the Android ID is generated by the OS and is unique) and the device ID returned by the plugin will have this structure:
00000000-0000-0000-XXXX-XXXXXXXXXXXX
where XXXX-XXXXXXXXXXXX is the Android ID
In our app we need to mantain compatibity with Android 9 devices and older who are being updated to android 10, so, from the older "complete" device id (containing androidID + deviceID + simID) we take only the first part (androidID) and compare it against the deviceID generated in android 10 for example:
o4ca5327-cd5c-3a0f-3345-181008441738 (old uniqueDeviceID, containing simID and deviceID)
00000000-0000-0000-o4ca-5327cd5c3a0f ("new" Android 10 uniqueDeviceID, containing only Android ID)
We just compare the o4ca-5327cd5c3a0f part to identify the device
I hope it help


Hide review2

Trying this again - Local build working fine, but it continues to get hung up on Netlify automated build.

OK - this build made it through the automated build process.  Needs review before completing.


White screen when Brackets opens

Whenever I open Brackets, about 8/10 times to be more specific, I get a white screen with the title "index.html". I get it if I'm just opening Brackets via the shortcut or opening a file associated with it. I opened the DevTools by right clicking and see the following:
Uncaught Error: Load timeout for modules: main
http://requirejs.org/docs/errors.html#timeout

@nsyrax Can you please share the Brackets version and OS that you are using.

I'm on Windows 7 SP1, I can't tell you what version of Brackets I'm running because it won't open at all. But I can tell you I have updated in the last month.

I uninstalled/reinstalled Brackets and it seems to have fixed the issue. Corrupt preferences?

@nsyrax Good to see that you have Brackets working now..
Corrupt preferences? Well may be, but can't say for sure as we don't have the setup to verify.
Closing the issue.

@rroshan1  Problem is back  :0(

@nsyrax Do you see that issue with the latest release?
Do you see the issue if you don't use that shortcut to open Brackets?
Still, I think the error message that  you shared would help. Thanks.

@nsyrax Can you please delete Brackets cache folder
If problem still persists, please collect crash logs and share the result.

@rroshan1  OK, I am running the newest update, which I believe was from yesterday, still had the issue. I used procdump to create dumps for each Brackets process. My question is this, what exactly is included in the dump file and is there a way I can read it? And each one is over 100mb, is that right? And thanks for all your help so far. It appears the Brackets team is every bit as awesome as the program they created!

AFAICT, we usually saw this issue with very slow Windows machines or when opening Brackets right after starting Windows up.
Is your setup particularly slow?

@MarcelGerber  It's installed on C, I have 8GB of RAM and an Intel i5 @ 3.2GHz, that should be more than enough to run it. I run Photoshop and Illustrator with no issues.

@nsyrax Can you try the following:-
Backup and delete the contents in the folder *C:\Users\username\AppData\Roaming\Brackets*.
See if the issue still exists. If NOT, we can confirm that it is caused by some corrupt preference OR faulty extension. Otherwise, we can look more into the issue.

@nsyrax Were you able to resolve the issue and proceed with using Brackets?

Since the 1.3 upgrade I am experiencing random freeze where the main screen goes white with only the menu and header shown (same as #10988). The  menu interface works (dropdown) but not the menu items. The window can't be closed and requires the task manager to be killed. Further information:
The crash occurs

after 1-10 minutes of use
when working on a relatively small JS file (~100 Lines)
on no specific triggers (keystroke, mouse move...)
even with all extensions disabled
even after clearing the cache
How to downgrade? Even after uninstalling 1.3 the 1.2 installer complains that a new version is available.

@hurelu can you please collect crash logs and share result.

@prafulVaishnav followed the instructions on the link to get the freeze log. I could only locate one Brackets.exe process and just sent you by email a zip of the dmp file.
Hope this helps. Cheers.

@prafulVaishnav was the freeze log of any use? Any insights on what is happening?

i had the same problem, so i deleted the "Brackets" folder in the "C:/Users/username/AppData/Roaming/" and then i opened Brackets again and the problem was solved.

But wont the datas be deleted? Also when the problem occurs again what can be done? Always deleting the brackets folder in C wont help right


Use dynamic response channels to avoid responses going to every client

Resolves #407
Dynamic response channels are subscribed to, by the request-originator, just before the request is dispatched. This ensures that responses are consumed only by the originator, avoiding unnecessary noise for the other clients.

I haven't tested it but, if this works as described, would be a great performance boost!
@doodlesbykumbi are the dynamic response automatic or do you need to modify server code to keep track of subscribed channels?

@y4my4my4m The dynamic response is automatic. The idea is

Client creates request and subscribes to response channel (prefix + "-response#" + this.nsp.name + "#" + requestId)
Client sends request
Clients either times out or gets all the responses it needs
Client unsubscribes from response channel

It's a mostly transparent change for consumers of the adapter. It could be made entirely transparent by having it be backwards compatible, but I think it's better to just go all in.

@doodlesbykumbi thanks for the pull request! If I understand correctly, this change is not backward compatible and will require a synchronized cluster update, isn't it?

I think to maintain backwards compatibility just before dispatching requests we would also have to listen on the original response channel. When we publish a response it would also have to be published on the original response channel.
An edge case (for when dispatching requests) I have to figure out is what happens when by some luck multiple requests take place at the same time. I suppose we'll have to keep a count, and only clean up when the count goes back to 0

Superseded by https://github.com/socketio/socket.io-redis-adapter/commit/f66de114a4581b692da759015def0373c619aab7.


Evaluate Neocities as recommend hosting option

https://neocities.org/ is a reliable host and very easy to use (without CLI knowledge, though there is a nice CLI helper).
There are evidently some limitations for hosting Unity WebVR-exported games (with file size, I believe). @delapuente: can you tell me what you encountered? We'll try to reach out to Kyle at Neocities

Relevant to documentation written by @delapuente in PR #109

Great! Limits for free hosting are not bad (1GiB store / 200GiB bandwidth) but it rejects uploading *.webmanifest and *.asm.* and *.wasm.* files.

@kyledrake: howdy! hope all is well! would there be any chance you can have Neocities whitelist those above file extensions as well as *.unityweb files (for WebAssembly modules)?


Removed old branch alias

Are you able to merge this 1.1->2.0->master?

Or shall i send a pull to 2.0 too?

Ping @vlucas. :)

We need branch alises removing and the master re-aliased as 2.1 before laravel can upgrade to this.

And the old branches deleted as the "v2" branch can mess with packagist.

PING - THIS IS URGENT - YOU HAVE BROKEN ALL 1.X CODE BY ALIASING THE MASTER TO 1.1

Sorry - will fix

Thank you. :)


Initial Changes

As suggested, doing the changes.
Please review the changes and let me know whether I am on the right path or not.
Fixes #7

Changes are done, as suggested.

I will continue to change other sections as well

Yep, now it looks like I wanted it to :)

Requesting for review


Penguinmod website down for 20+ days

looks like penguinmod is too lazy to fix their website, altrough the editor works fine, witch is OK For me.


Updates from ADS - Powershell

Updates to the powershell log data source.

Thinking this one might focus on logging not captured from the context of a process (ex: module/script block logging + transcription -- https://www.fireeye.com/blog/threat-research/2016/02/greater_visibilityt.html). Might not need the .NET specific level of detail vice a component pointing to these logs

Need to update to remove what is covered in Command + Process


Support holidays in "inject" node

To enable trigger in inject nodes not only on Saturday and Sunday, but on holidays too.
Used, for example, in home automation applications.

Just to wave the flag again that not all countries work a Mon-Fri working week.
Also there is already the Google Calendar node that is easy to modify to trigger if an all day event covers that day which I'm using for HomeAutomation and a colour of bin to put-out reminder

But home automation calendar have to work even when your internet connection isn't working. So google calendar should be integrated into build-in scheduler/calendar rather than set as a main one.
In my case I am using https://github.com/rschmukler/agenda

@ukmoose
forgot I have been sitting on this change for the day selector for a while ... any good ?

Looks good!   Having lived in a country with a Friday - Saturday weekend, its amazing how many things break.
rgds
ukmoose
On 2 Feb 2015, at 20:00, Dave Conway-Jones<EMAIL_ADDRESS>wrote:
@ukmoose https://github.com/ukmoose
forgot I have been sitting on this change for the day selector for a while ... any good ?
https://cloud.githubusercontent.com/assets/5375409/6007954/e2f41026-ab15-11e4-8770-b8456e963297.png
—
Reply to this email directly or view it on GitHub https://github.com/node-red/node-red/pull/504#issuecomment-72526357.

Replaced day selector with checkboxes in inject node - Commit 84e64178770e8ed7821049cda628d1cb0b010a54

There has been a lot of discussion on this topic on the mailing list over recent weeks.
The consensus is to create a Scheduler node that has the more complicated options than really fit in the simple inject node. Any consideration of holiday schedules would belong in that node.


SSRProvider creates issues with conditionally-rendered OverlayContainers

🐛 Bug Report
When wrapping an app with SSRProvider, conditionally-rendered overlays don't display correctly on the first display. If you show one based on state.isOpen from a trigger, the rendering is odd the first go. In my app's case, the tooltip that should be rendered stays offscreen until mousing away, then the overlay flashes on and off in a second. Hovering over the same element again, the overlay displays correctly.
I created a sandbox that shows a similar problem. In the sandbox, the overlay shows, but the offset is being ignored.
These issues only show up when the app is wrapped in an SSRProvider. If the provider is removed, the overlays display as expected, but then the app complains about SSR and IDs.
I can side-step the issue by conditionally rendering the content inside the OverlayContainers, but this results in hundreds of portals sitting at the bottom of body.
🤔 Expected Behavior
I expect overlays to display correctly even when the app is wrapped in an SSRProvider.
😯 Current Behavior
Overlays exhibit odd behavior, sometimes not showing at all, or having odd positionProps.style values when wrapped with SSRProvider.
🔦 Context
I'm building a Remix app that would seemingly require SSRProvider and I have lots of menus and tooltips that need to be in OverlayContainers because of overflowing/scrolling parents.
💻 Code Sample
https://codesandbox.io/s/react-spectrum-template-forked-9io4uj?file=/src/index.js
🌍 Your Environment

Software
Version(s)

react-aria
3.19.0

react-stately
3.17.0

Chrome
103

macOS
12.5.1

👍

We have the same problem, and i found this issue which i think is directly related to the problem.
https://github.com/adobe/react-spectrum/issues/3293

Update: 2022-09-09. After playing around today a bit more, I was able to get an OverlayContainer to conditionally render when triggered off of useMenuTrigger by moving the OverlayContainer inside the Popover component and then conditionally rendering the Popover. Works as expected.
Tried the same with my Tooltip, but no matter what I do, the Tooltip (using OverlayContainer) won't position itself when conditionally rendered and the OverlayContainer is inside the conditionally rendered component. If I conditionally render inside the OverlayContainer, things look fine, but there are a hundred OverlayContainers in the body. Also, if I remove the SSRProvider, everything works as expected, but React Aria yells at me about IDs not matching.

I've made it work but manually handling the ref in a callback.
    const popoverRefCallback = useCallback(
      (ref: HTMLDivElement) => {
        popoverRef.current = ref;
        updatePosition();
      },
      [popoverRef, updatePosition]
    );

Update: 2022-09-09. After playing around today a bit more, I was able to get an OverlayContainer to conditionally render when triggered off of useMenuTrigger by moving the OverlayContainer inside the Popover component and then conditionally rendering the Popover. Works as expected.
Tried the same with my Tooltip, but no matter what I do, the Tooltip (using OverlayContainer) won't position itself when conditionally rendered and the OverlayContainer is inside the conditionally rendered component. If I conditionally render inside the OverlayContainer, things look fine, but there are a hundred OverlayContainers in the body. Also, if I remove the SSRProvider, everything works as expected, but React Aria yells at me about IDs not matching.

I've made it work by manually handling the ref in a callback.
    const popoverRefCallback = useCallback(
      (ref: HTMLDivElement) => {
        popoverRef.current = ref;
        updatePosition();
      },
      [popoverRef, updatePosition]
    );

Update: 2022-09-09. After playing around today a bit more, I was able to get an OverlayContainer to conditionally render when triggered off of useMenuTrigger by moving the OverlayContainer inside the Popover component and then conditionally rendering the Popover. Works as expected.
Tried the same with my Tooltip, but no matter what I do, the Tooltip (using OverlayContainer) won't position itself when conditionally rendered and the OverlayContainer is inside the conditionally rendered component. If I conditionally render inside the OverlayContainer, things look fine, but there are a hundred OverlayContainers in the body. Also, if I remove the SSRProvider, everything works as expected, but React Aria yells at me about IDs not matching.

I've made it work by manually handling the ref in a callback, and then calling updatePostion which is returned from the useOverlayPosition hook.
    const popoverRefCallback = useCallback(
      (ref: HTMLDivElement) => {
        popoverRef.current = ref;
        updatePosition();
      },
      [popoverRef, updatePosition]
    );

@rk-lunar
Ah, that took care of it! Thank you very much for the workaround.
I don't know if the above workaround is the solution to this problem or if it should work without the callbackRef. Will leave this open for now.

Did anyone figure out a workaround when using useMenu? I'm running into the same issue when trying to incorporate the styled example inside a Next.JS project and SSRProvider breaks it 😅

@brandonpittman sorry if I'm missing context but why did you close the issue?

https://github.com/adobe/react-spectrum/issues/3490#issuecomment-1241670866

@eramdam I expect that our workaround should work there as well, but passing the menu trigger state instead of the overlay trigger state.
@brandonpittman I don't think that the existence of a workaround means that the bug is no longer present? Ideally, that (or our) workaround wouldn't be necessary.

@eramdam I expect that our workaround should work there as well, but passing the menu trigger state instead of the overlay trigger state.
@brandonpittman I don't think that the existence of a workaround means that the bug is no longer present? Ideally, that (or our) workaround wouldn't be necessary.

Yep, your work around works!

I've made it work by manually handling the ref in a callback, and then calling updatePostion which is returned from the useOverlayPosition hook.

I'm using usePopover() which doesn't return an updatePosition() method... how would I work around the issue when using usePopover()?
I don't understand why this issue was closed. This is still a bug... :/

Mine was broken with the examples for useSelect, but this workaround from #3787 fixed it fine:
<Overlay portalContainer={document.body}>
     ...
</Overlay>

This is in a Remix app where we hydrate the entire <html> element; I think it was getting confused about where to send the portal perhaps?


Your source code is incomplete, missing source file under common , compile error!

Missing MyArray.h , MyString.h and so on.  would you please add these files?

would you please add these files?
No problem, I'll share them soon(a few days). Currently, they're in another repository(and it's private).

But note that the project is still in a VERY EARLY STATE, and I'm stilling find algorithms to implement the functions.
But welcome to contribute if you want.

The common C++ types are shared at https://github.com/VFSSOFT/common.


Cargo 1.78+ incorrectly drops FeatureValues that match the implicit feature

Problem
Cargo 1.78 and 1.79 drops FeatureValues that match the default feature, resulting in an invalid feature map that later causes Cargo to ignore the version when parsing the index in the slow path of Summaries::parse() due to build_feature_map() returning an error.
Example error message:
   0.378811004s TRACE cargo::sources::registry::index: json parsed registry hs-clarity-resource-locator-rust/4.2.4
   0.381279937s  INFO cargo::sources::registry::index: failed to parse "hs/-c/hs-clarity-resource-locator-rust" registry package: optional dependency `tonic_010` is not included in any feature
Make sure that `dep:tonic_010` is included in one of features in the [features] table.

The corresponding Cargo.toml looks like this:
[package]
name = "hs-clarity-resource-locator-rust"
version = "0.1.0"
edition = "2021"

[features]
tonic_010 = ["dep:tonic_010"]

[dependencies]
tonic_010 = { package = "tonic", version = "0.10", optional = true }

❌ The error occurs because when this crate is published by Cargo 1.78 or 1.79, the feature map is broken:
{
  // ...
  "features": {
    "tonic_010": []
  }
}

✅ When published with Cargo 1.76 or 1.77 instead, you get:
{
  // ...
  "features": {
    "tonic_010": [
      "dep:tonic_010"
    ]
  }
}

✅ When removing the [features] table from the Cargo.toml, you get:
{
  // ...
  "features": {}
  }
}

My hypothesis is that Cargo does some "cleaning" of the features map, maybe attempting to remove features that would be implied anyway, but it results in a broken map.
Steps

Create a new crate with a Cargo.toml akin to the one shown above
Publish it to a registry
Inspect the published version's feature map

More elaborate local testing:

Step (1) from above
Run the sparsereg.py from below to record a newcrate.json when publishing
Publish the crate to sparse+http://localhost:8000/cargo/foorepo/index/
Apply 0001-Add-cargo-build-feature-map.rs.patch
cargo run --bin cargo-build-feature-map -- newcrate.json

Result
❯ cargo run --bin cargo-build-feature-map -- ~/Desktop/newcrate.json
   Compiling cargo v0.83.0 (/home/coder/git/rust-lang/cargo)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 11.43s
     Running `target/debug/cargo-build-feature-map /home/coder/git/niklas/Desktop/newcrate.json`
{"name":"hs-clarity-resource-locator-rust","vers":"0.1.0","deps":[{"name":"tonic_010","optional":true,"explicit_name_in_toml":null}],"features":{"tonic_010":[]}}
Error: optional dependency `tonic_010` is not included in any feature
Make sure that `dep:tonic_010` is included in one of features in the [features] table.

Additional files
sparsereg.py
"""
Implements the basic API endpoints for a Cargo sparse registry to perform a `cargo publish`.
Records the received crate's metadata in a `newcrate.json` file in the CWD.

Dependencies:

- fastapi

Run:

    $ fastapi run sparsereg.py
"""

import struct
from typing import Any
from fastapi import FastAPI, Request

app = FastAPI()

@app.get("/cargo/{repository}/index/config.json")
def config_json(repository: str) -> dict[str, str]:
    return {
        "dl": "http://localhost:8000/cargo/v1/crates",
        "api": f"http://localhost:8000/cargo/{repository}",
    }

@app.put("/cargo/{repository}/api/v1/crates/new")
async def new_crate(repository: str, request: Request) -> dict[str, Any]:
    body = await request.body()
    length = struct.unpack("I", body[:4])[0]
    with open("newcrate.json", "wb") as fp:
        fp.write(body[4 : length + 4])
    return {}

0001-Add-cargo-build-feature-map.rs.patch
From 1169b45dcb59e503f980b926bda9a89b3fad51e2 Mon Sep 17 00:00:00 2001
From: Niklas Rosenstein<EMAIL_ADDRESS>Date: Tue, 30 Jul 2024 07:04:27 +0000
Subject: [PATCH 1/1] Add cargo-build-feature-map.rs

---
 Cargo.toml                         |  5 ++
 src/bin/cargo-build-feature-map.rs | 77 ++++++++++++++++++++++++++++++
 src/cargo/core/summary.rs          |  2 +-
 3 files changed, 83 insertions(+), 1 deletion(-)
 create mode 100644 src/bin/cargo-build-feature-map.rs

diff --git a/Cargo.toml b/Cargo.toml
index 77e7f9092..c9cf20eb4 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -251,6 +251,11 @@ name = "cargo"
 test = false
 doc = false

+[[bin]]
+name = "cargo-build-feature-map"
+test = false
+doc = false
+
 [features]
 vendored-openssl = ["openssl/vendored"]
 vendored-libgit2 = ["libgit2-sys/vendored"]
diff --git a/src/bin/cargo-build-feature-map.rs b/src/bin/cargo-build-feature-map.rs
new file mode 100644
index 000000000..48e9506a4
--- /dev/null
+++ b/src/bin/cargo-build-feature-map.rs
@@ -0,0 +1,77 @@
+use std::collections::BTreeMap;
+use std::error::Error;
+
+use cargo::core::summary::build_feature_map;
+use cargo::util::interning::InternedString;
+use itertools::Itertools;
+use serde::{Deserialize, Serialize};
+
+#[derive(Clone, Deserialize, Serialize)]
+struct PackageDep {
+    name: String,
+    optional: Option<bool>,
+
+    // For metadata from the Publish API, this contains the actual name in the TOML file (the alias).
+    // In the Sparse Registry Index API, the `name` field is already the actual name in the TOML.
+    explicit_name_in_toml: Option<String>,
+}
+
+impl PackageDep {
+    fn normalize(self) -> PackageDep {
+        if let Some(ref toml_name) = self.explicit_name_in_toml {
+            PackageDep {
+                name: toml_name.clone(),
+                optional: self.optional,
+                explicit_name_in_toml: None,
+            }
+        } else {
+            self.clone()
+        }
+    }
+}
+
+impl Into<cargo::core::Dependency> for PackageDep {
+    fn into(self) -> cargo::core::Dependency {
+        // Fake source ID, irrelevant.
+        let source_id = cargo::core::SourceId::from_url("git+https://foobar").unwrap();
+        let mut result =
+            cargo::core::Dependency::new_override(InternedString::new(&self.name), source_id);
+        result.set_optional(self.optional.unwrap_or(false));
+        result
+    }
+}
+
+#[derive(Deserialize, Serialize)]
+struct Package {
+    name: String,
+    vers: String,
+    deps: Vec<PackageDep>,
+    features: BTreeMap<InternedString, Vec<InternedString>>,
+}
+
+pub fn main() -> Result<(), Box<dyn Error>> {
+    let cmd = clap::Command::new("cargo-build-feature-map").args([clap::Arg::new("file")]);
+    let args = cmd.get_matches();
+
+    let file = args.get_one::<String>("file").unwrap();
+    let mut pkg: Package = serde_json::from_str(&std::fs::read_to_string(&file)?)?;
+
+    // Adjust for asymmetry between Registry API and Sparse registry API.
+    pkg.deps = pkg
+        .deps
+        .into_iter()
+        .map(PackageDep::normalize)
+        .collect_vec();
+
+    // Re-serialize the content. Makes it easier to compare one file with the other later.
+    println!("{}", serde_json::to_string(&pkg)?);
+
+    // Validates the feature map.
+    let feature_map = build_feature_map(
+        &pkg.features,
+        &pkg.deps.into_iter().map(Into::into).collect_vec(),
+    )?;
+    println!("{:?}", feature_map);
+
+    Ok(())
+}
diff --git a/src/cargo/core/summary.rs b/src/cargo/core/summary.rs
index 424328fa6..05ff9f33c 100644
--- a/src/cargo/core/summary.rs
+++ b/src/cargo/core/summary.rs
@@ -186,7 +186,7 @@ const _: fn() = || {

 /// Checks features for errors, bailing out a CargoResult:Err if invalid,
 /// and creates FeatureValues for each feature.
-fn build_feature_map(
+pub fn build_feature_map(
     features: &BTreeMap<InternedString, Vec<InternedString>>,
     dependencies: &[Dependency],
 ) -> CargoResult<FeatureMap> {
--
2.45.2

Possible Solution(s)
No response
Notes
No response
Version
cargo 1.79.0 (ffa9cf99a 2024-06-03)
release: 1.79.0
commit-hash: ffa9cf99a594e59032757403d4c780b46dc2c43a
commit-date: 2024-06-03
host: x86_64-unknown-linux-gnu
libgit2: 1.7.2 (sys:0.18.3 vendored)
libcurl: 8.6.0-DEV (sys:0.4.72+curl-8.6.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Ubuntu 22.4.0 (jammy) [64-bit]

I found this related issue after all: https://github.com/rust-lang/cargo/issues/10125
However it is described as a "entirely reasonable human error" when I would classify this as a Cargo bug / breaking change, given that the Cargo.toml is semantically correct (even if not normalized given that one could rely on implied default features).

On master,
cargo package Cargo.toml is good:
# THIS FILE IS AUTOMATICALLY GENERATED BY CARGO
#
# When uploading crates to the registry Cargo will automatically
# "normalize" Cargo.toml files for maximal compatibility
# with all versions of Cargo and also rewrite `path` dependencies
# to registry (e.g., crates.io) dependencies.
#
# If you are reading this file be aware that the original Cargo.toml
# will likely look very different (and much more reasonable).
# See Cargo.toml.orig for the original contents.

[package]
edition = "2021"
name = "hs-clarity-resource-locator-rust"
version = "0.1.0"
build = false
autobins = false
autoexamples = false
autotests = false
autobenches = false
readme = false

[[bin]]
name = "hs-clarity-resource-locator-rust"
path = "src/main.rs"

[dependencies.tonic_010]
version = "0.10"
optional = true
package = "tonic"

[features]
tonic_010 = ["dep:tonic_010"]

The Summary generated for the above is good:
        features: {
            "tonic_010": [
                Dep {
                    dep_name: "tonic_010",
                },
            ],
        },

But what we send to the registry is bad:
[src/cargo/ops/registry/publish.rs:473:5] &new_crate = NewCrate {
    name: "hs-clarity-resource-locator-rust",
    vers: "0.1.0",
    deps: [
        NewCrateDependency {
            optional: true,
            default_features: true,
            name: "tonic",
            features: [],
            version_req: "^0.10",
            target: None,
            kind: "normal",
            registry: None,
            explicit_name_in_toml: Some(
                "tonic_010",
            ),
            artifact: None,
            bindep_target: None,
            lib: false,
        },
    ],
    features: {
        "tonic_010": [],
    },
    authors: [],
    description: None,
    documentation: None,
    homepage: None,
    readme: None,
    readme_file: None,
    keywords: [],
    categories: [],
    license: None,
    license_file: None,
    repository: None,
    badges: {},
    links: None,
    rust_version: None,
}

@NiklasRosenstein are you using a custom registry?  crates.io re-generates the summary, ignoring NewCrate.  If this only happens for third-party registries, that might explain why this wasn't noticed before.

@epage Yep, can confirm this is happening for a third-party registry!

@NiklasRosenstein May be a good idea to try a git bisect here that looks at the log output of what gets sent in NewCrate when running cargo publish against a simple HTTP receiver.

atm I am updating the tests to cover this and will then cherry pick to just before #13518.

Confirmed that it is that PR.  It is also specific to renaming.

Posted a fix at #14325.

Hey @epage, thank you for fixing this. 🚀 It's going to land in Cargo 1.81, yes?
Speaking to how Cargo handles caches for crate indexes in general, I wonder if there is something that should be done with regards to error reporting and the caching behaviour.
As it stands today,

When you are on an older Cargo version that doesn't support a particular version, the actual error is hidden in a very specific log message and it is not clear to the user why version resolution fails when clearly the registry indicates that the version you are looking to resolve exists.
When you upgrade Cargo to a version that supports additional versions from the index that the previous version did not, you still can't resolve the respective versions until you either clear your local registry cache or the remote index is updated.

If I may suggest (maybe naively); Cargo could

Maintain the original state of the index file in the cache and only validate versions on loading them back from disk
Propagate information about versions that can't be considered because they are incompatible with the current Cargo version to the resolver or the error reporting

What do you think?

It's going to land in Cargo 1.81, yes?

We haven't done a beta-backport yet. Will do that in this week.

This PR was against 1.82 but i have a cherry-pick to 1.81 ready to go when i get onto better internet.
I believe your first case is being tracked in #10623.
The second case shouldn't be a problem and I'd need reproduction steps.


Can't connect from android

Hello, I'm trying to run on android and I can't connect. The server definitely works, the connection from Linux is normal. I use 3.1 version
D/WSTUN: WAIT for datagrames on <IP_ADDRESS>:51821
D/WSTUN: DEBUG :: Oppening tcp connection to <IP_ADDRESS>:31118
D/WSTUN: DEBUG :: TIMEOUT connection

Start command libwstunnel.so -v --udp --udpTimeoutSec -1 -L <IP_ADDRESS>:51821:<IP_ADDRESS>:51821 wss://<IP_ADDRESS>:31118

Hello,
Like that I can't tell you. Can you take a tcpdum/pcap of the network traffic on server and client ?
tcpdump -i <interface> -s 65535 -w dump.pcap

Hello, I'm trying to run on android and I can't connect. The server definitely works, the connection from Linux is normal. I use 3.1 version
D/WSTUN: WAIT for datagrames on <IP_ADDRESS>:51821
D/WSTUN: DEBUG :: Oppening tcp connection to <IP_ADDRESS>:31118
D/WSTUN: DEBUG :: TIMEOUT connection

Start command libwstunnel.so -v --udp --udpTimeoutSec -1 -L <IP_ADDRESS>:51821:<IP_ADDRESS>:51821 wss://<IP_ADDRESS>:31118

LOL，How to run wstunnel on Android? Can you give me some instructions?

I think it will be very difficult to run tcpdump on android, there are certain security restrictions.
I have an assumption that the problem may be related to how the TCP connection is opened. How tcp connections are opened? I know for sure that it will not work in RAW format in android

I was still able to run tcpdump and, as I understand it, there are no packets from the application to connect to the tunnel. Perhaps now TCP is used to connect RAW or some other form not allowed by android.

The client use normal sockets, no RAW or anything else. So I don't think this is the issue.
Can you try starting the client with
--udp --udpTimeoutSec -1 -L <IP_ADDRESS>:51821:<IP_ADDRESS>:51821 wss://<IP_ADDRESS>:31118

and also without UDP at all.
 -L <IP_ADDRESS>:51821:<IP_ADDRESS>:51821 wss://<IP_ADDRESS>:31118

I don't know what software you have installed on your android, but if you can try first with some dns request (dig) for udp and netcat (nc) for tcp to try it will be perfect.
Also send me the pcap please, so I can take a look at it

dump.pcap.zip
for udp

TCP connection
D/WSTUN: WAIT for tcp connection on <IP_ADDRESS>:51821
D/WSTUN: DEBUG :: Oppening tcp connection to <IP_ADDRESS>:31118

I stop process after some minute.
dump.pcap.zip

dump-nc.pcap.zip
I also made an attempt to connect to the wstunnel server through nc

I tried running the program as root and it worked. It remains to understand why it does not work in normal mode, it seems that the problem is still with an attempt to work with a socket at a low level
(base) MacBook-Pro:lzo asdasdsdsadsada$ ~/Library/Android/sdk/platform-tools/adb shell /data/local/tmp/libwstunnel.so -v -L <IP_ADDRESS>:51821:<IP_ADDRESS>:51821 wss://<IP_ADDRESS>:31118
WAIT for tcp connection on <IP_ADDRESS>:51821
DEBUG :: Oppening tcp connection to <IP_ADDRESS>:31118
DEBUG :: Doing tls Handshake
DEBUG :: Oppening Websocket stream
CLOSE tunnel :: <IP_ADDRESS>:51821 <==WSS==> <IP_ADDRESS>:31118 <==TCP==> <IP_ADDRESS>:51821
DEBUG :: Closing Websocket stream
DEBUG :: Closing TLS
DEBUG :: Closing tcp connection to <IP_ADDRESS>:31118
DEBUG :: ====
<IP_ADDRESS>:31118: Network.Connection.connectionGetChunk: end of file
====
^C
(base) MacBook-Pro:lzo asdasdsdsadsada$ ~/Library/Android/sdk/platform-tools/adb shell /data/local/tmp/libwstunnel.so --udp --udpTimeoutSec -1 -v -L <IP_ADDRESS>:51821:<IP_ADDRESS>:51821 wss://<IP_ADDRESS>:31118
WAIT for datagrames on <IP_ADDRESS>:51821
DEBUG :: Oppening tcp connection to <IP_ADDRESS>:31118
DEBUG :: Doing tls Handshake
DEBUG :: Oppening Websocket stream

Thank you for the dumps,  will take a look at it later in the week-end m,  but if in root it works,  i guess it will only confirm your asssumptions.
Can you run strace on android ? if yes please do
strace -fff comand_line_wstunnel_cliebnt

for both the root and normal user,  i would like to see which syscall get refused

I found the problem and everything turned out to be much easier. I launched the wstunnel and run vpn into the tunnel, without excluding it so that it would bypass the VPN, as a result we got a loop.
Many thanks for the help.

Haha no, such a déception. I was hopping for a more challenging issue :0
Well anyway, have fun with wstunnel 👍


Write proper error messages for Get-Command ' '

PR Summary
Fix #13342. Checks if _commandName is empty or null in the DoPowerShellRelativePathLookup() method. Removes a Dbg.Assert() that checks if the name is empty or null. The assertion fails because _commandName is trimmed in setupPathSearcher().

PR Context
After this change Get-Command ' ' will return a CommandNotFoundException instead of a IndexOutOfRangeException. The Dbg.Assert was removed because according to Issue #10165 whitespace should be a valid argument for Get-Command.

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

I see now that an alternate and maybe cleaner solution would involve changing only this line _commandName = _commandName.TrimEnd(Utils.Separators.PathSearchTrimEnd); to create a new variable which is only used for the setupPathSearcher() routine. Creating a new variable for path searching may be more desirable than altering the existing _commandName string. If _commandName doesn't get trimmed we don't ever have to worry about the IndexOutOfRangeException being thrown.

Creating a new variable for path searching may be more desirable than altering the existing _commandName string.

I think it makes no sense to create new variable - this complicates code and don't protect underlying internal methods.

@SteveL-MSFT what do you think of the added test cases? Thanks.

@adityapatwardhan I don't mean to bother you but I just wanted to know if there's anything else I can do to help get this PR approved? Thanks.

Currently working on some high priority items. I will be reviewing this after. Thank you for your patience.

@SteveL-MSFT can you update your review

@jakekerr Thanks for your contribution!

@jakekerr Thanks for your contribution!


Rocket.Chat webhook: slack failed with: {"success":true}

Gogs version:  <IP_ADDRESS>7
Git version: 2.7.4
Operating system: Ubuntu 16.04
Database:

[ ] PostgreSQL
[x] MySQL
[ ] SQLite

Can you reproduce the bug at http://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log:

"[...rc/runtime/asm_arm.s:990 goexit()] [E] slack failed with: {"success":true}
[T] Hook delivery failed: 1053b9b9-2c6f-48c6-8c40-cba5c420ace2"
Hello,
I am using Rocket.Chat and have configured a webhook in "slack" format in Gogs (since Rocket.Chat does support this without much configuration).
Even though the webhook works fine, Gogs thinks it failed, because the body response is "{"success":true}", instead of the "ok" that Gogs seems to expect.
I've been looking at Slack's webhook documentation, and it does not specify what response Slack will return. Instead it only says: "[..] in most cases you'll receive a "HTTP 200 OK" response with a JSON body indicating that your message posted successfully, [...]".
So I feel Gogs should just look at HTTP 200 OK (like it does on the custom format code path), since assuming the response is always going to be the text "ok" seems problematic if Slack changes this.
(As they have not defined the response format, they probably don't expect people to rely on this exact format either).
Anyway, still works, just thought it might confuse people.

Got a link to the docs for that quote? :smiley:
If it's true then we have a bug that should be fixed :laughing:

Sure, here you go:
https://api.slack.com/incoming-webhooks
(Scroll down to "Handling errors")

May be #3254

This is claimed to be fixed by merging #3256, please help test on develop branch or https://try.gogs.io.

Seems to work fine now, with the latest compiled version from the repo.
Thanks!

Kept open until merged into master :)

Already in.

Hah! Working hard :thumbup:


log temperature output to pc over usb / serial

A live logging feature / output to pb would be helpful, to check that the profile is progressing as expected. It seems like a good idea, if the MCU is not getting too busy in it's main loop to print that data out every so often.

Good news!  Controleo3 already does that.  It dumps temperature and PID information out over the USB port every second.  The data can be collected then pasted into Excel (or another spreadsheet program) for charting.


Fix Trainer arg name in docs

What does this PR do?
Fixes a Trainer arg name in its docs.
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

thanks! if you do a full text search for the whole project, you will find one more occurence in pytorch_lightning/trainer/__init__.py

Good catch! :+1:


env variables pre-filled example

Feature Request
Is your feature request related to a problem? Please describe.
.env.example to be pre-filled with example ports etc, remove the pain of manually entering every variable for first time setup.

Example being missing:
AUTH_POSTGRES_USERNAME
AUTH_POSTGRES_PASSWORD
etc

@Baroshem do you have these? makes it hard to start up the project without a correct .env.example thanks in advance.

Hi @uncodable
Yes I will push the variables so that it will be easier to develop.

@uncodable
Because Otasoft is built using microservices it may be easier to run each project separately with their own .env. I also added .env to Otasoft API which is a gateway used for handling all trafic and distributing it to the correct microservice. Let me know if you need more help.

Thanks @Baroshem it was more for running docker-compose locally it needs the base .env i believe


Consider tagging a release

Hi!  I am reviewing on gittuf and they use commit da429971be5a5cf611bad18e03bbc006b80eacdb from this project which is later than v0.8.0.  Would you consider making a new release with this commit in it?  The last tag was made almost a year ago, so maybe it is time :)
Thanks,
Simon

Hi @jas4711, thanks for filing this! I just created a new tag. :)

Wow that was really fast, thank you!