Sia-UI: siad on OSX crashes while unlocking wallet

I am using "v1.2.1 (Blue Moon)" on OS X and I am unable to unlock my wallet. The blockchain is synchronized and the passphrase accepted, but for a long time a message about the wallet in the process of being unlocked ("may take several minutes") is displayed and then:
Siad has exited unexpectedly. Please submit a bug report including the error log here.
Loading...
(0/6) Loading siad...
(1/6) Loading gateway...
(2/6) Loading consensus...
(3/6) Loading transaction pool...
(4/6) Loading wallet...
(5/6) Loading host...
(6/6) Loading renter...
Finished loading in 0.819651164 seconds
Wallet: scanned to height 67308...
Wallet: scanned to height 67318...
Wallet: scanned to height 67319...
Wallet: scanned to height 67322...
Wallet: scanned to height 67326...
Wallet: scanned to height 67329...
Wallet: scanned to height 67332...
Wallet: scanned to height 67333...
Wallet: scanned to height 67336...
Wallet: scanned to height 67339...
Wallet: scanned to height 67340...
Wallet: scanned to height 67344...
Wallet: scanned to height 67346...
Wallet: scanned to height 67351...
Wallet: scanned to height 67352...
Wallet: scanned to height 67359...
Wallet: scanned to height 67362...
Wallet: scanned to height 67364...
Wallet: scanned to height 67367...
Wallet: scanned to height 67369...
Wallet: scanned to height 67374...
Wallet: scanned to height 67377...
Wallet: scanned to height 67379...
Wallet: scanned to height 67382...
Wallet: scanned to height 67383...
Wallet: scanned to height 67386...
Wallet: scanned to height 67387...
Wallet: scanned to height 67392...
Wallet: scanned to height 67393...
Wallet: scanned to height 67399...
Wallet: scanned to height 67403...
Wallet: scanned to height 67404...
Wallet: scanned to height 67408...
Wallet: scanned to height 67411...
Wallet: scanned to height 67412...
Wallet: scanned to height 67417...
Wallet: scanned to height 67421...
Wallet: scanned to height 67425...
Wallet: scanned to height 67429...
Wallet: scanned to height 67434...
Wallet: scanned to height 67439...
Wallet: scanned to height 67441...
Wallet: scanned to height 67443...
Wallet: scanned to height 67448...
Wallet: scanned to height 67451...
Wallet: scanned to height 67456...
Wallet: scanned to height 67457...
Wallet: scanned to height 67461...
Wallet: scanned to height 67463...
Wallet: scanned to height 67464...
Wallet: scanned to height 67468...
Wallet: scanned to height 67474...
Wallet: scanned to height 67476...
Wallet: scanned to height 67483...
Wallet: scanned to height 67485...
Wallet: scanned to height 67489...
Wallet: scanned to height 67491...
Wallet: scanned to height 67492...
Wallet: scanned to height 67498...
Wallet: scanned to height 67499...
Wallet: scanned to height 67503...
Wallet: scanned to height 67506...
Wallet: scanned to height 67508...
Wallet: scanned to height 67513...
Wallet: scanned to height 67516...
Wallet: scanned to height 67519...
Wallet: scanned to height 67520...
Wallet: scanned to height 67525...
Wallet: scanned to height 67530...
Wallet: scanned to height 67533...
Wallet: scanned to height 67536...
Wallet: scanned to height 67537...
Wallet: scanned to height 67543...
Wallet: scanned to height 67546...
Wallet: scanned to height 67547...
Wallet: scanned to height 67552...
Wallet: scanned to height 67553...
Wallet: scanned to height 67558...
Wallet: scanned to height 67560...
Wallet: scanned to height 67566...
Wallet: scanned to height 67568...
Wallet: scanned to height 67574...
Wallet: scanned to height 67575...
Wallet: scanned to height 67578...
Wallet: scanned to height 67580...
Wallet: scanned to height 67585...
Wallet: scanned to height 67588...
Wallet: scanned to height 67590...
Wallet: scanned to height 67596...
Wallet: scanned to height 67600...
Wallet: scanned to height 67601...
Wallet: scanned to height 67606...
Wallet: scanned to height 67608...
Wallet: scanned to height 67612...
Wallet: scanned to height 67613...
Wallet: scanned to height 67619...
Wallet: scanned to height 67624...
Wallet: scanned to height 67630...
Wallet: scanned to height 67632...
Wallet: scanned to height 67636...
Wallet: scanned to height 67639...
Wallet: scanned to height 67640...
Wallet: scanned to height 67641...
Wallet: scanned to height 67646...
Wallet: scanned to height 67649...
Wallet: scanned to height 67654...
Wallet: scanned to height 67657...
Wallet: scanned to height 67662...
Wallet: scanned to height 67663...
Wallet: scanned to height 67669...
Wallet: scanned to height 67671...
Wallet: scanned to height 67674...
Wallet: scanned to height 67679...
Wallet: scanned to height 67681...
Wallet: scanned to height 67690...
Wallet: scanned to height 67691...
Wallet: scanned to height 67696...
Wallet: scanned to height 67699...
Wallet: scanned to height 67700...
Wallet: scanned to height 67703...
Wallet: scanned to height 67705...
Wallet: scanned to height 67708...
Wallet: scanned to height 67713...
Wallet: scanned to height 67715...
Wallet: scanned to height 67719...
Wallet: scanned to height 67725...
Wallet: scanned to height 67729...
Wallet: scanned to height 67730...
Wallet: scanned to height 67733...
Wallet: scanned to height 67735...
Wallet: scanned to height 67737...
Wallet: scanned to height 67739...
Wallet: scanned to height 67741...
Wallet: scanned to height 67745...
Wallet: scanned to height 67748...
Wallet: scanned to height 67754...
Wallet: scanned to height 67759...
Wallet: scanned to height 67764...
Wallet: scanned to height 67769...
Wallet: scanned to height 67772...
Wallet: scanned to height 67773...
Wallet: scanned to height 67777...
Wallet: scanned to height 67779...
Wallet: scanned to height 67784...
Wallet: scanned to height 67786...
Wallet: scanned to height 67792...
Wallet: scanned to height 67801...
Wallet: scanned to height 67808...
Wallet: scanned to height 67813...
Wallet: scanned to height 67818...
Wallet: scanned to height 67824...
Wallet: scanned to height 67826...
Wallet: scanned to height 67829...
Wallet: scanned to height 67836...
Wallet: scanned to height 67838...
Wallet: scanned to height 67842...
Wallet: scanned to height 67844...
Wallet: scanned to height 67846...
Wallet: scanned to height 67852...
Wallet: scanned to height 67855...
Wallet: scanned to height 67861...
Wallet: scanned to height 67864...
Wallet: scanned to height 67867...
Wallet: scanned to height 67875...
Wallet: scanned to height 67878...
Wallet: scanned to height 67880...
Wallet: scanned to height 67885...
Wallet: scanned to height 67889...
Wallet: scanned to height 67895...
Wallet: scanned to height 67900...
Wallet: scanned to height 67902...
Wallet: scanned to height 67904...
Wallet: scanned to height 67912...
Wallet: scanned to height 67913...
Wallet: scanned to height 67916...
Wallet: scanned to height 67921...
Wallet: scanned to height 67930...
Wallet: scanned to height 67933...
Wallet: scanned to height 67939...
Wallet: scanned to height 67945...
Wallet: scanned to height 67948...
Wallet: scanned to height 67953...
Wallet: scanned to height 67958...
Wallet: scanned to height 67961...
Wallet: scanned to height 67966...
Wallet: scanned to height 67972...
Wallet: scanned to height 67976...
Wallet: scanned to height 67980...
Wallet: scanned to height 67989...
Wallet: scanned to height 67996...
Wallet: scanned to height 67999...
Wallet: scanned to height 68002...
Wallet: scanned to height 68005...
Wallet: scanned to height 68008...
Wallet: scanned to height 68010...
Wallet: scanned to height 68020...
Wallet: scanned to height 68028...
Wallet: scanned to height 68034...
Wallet: scanned to height 68041...
Wallet: scanned to height 68044...
Wallet: scanned to height 68046...
Wallet: scanned to height 68050...
Wallet: scanned to height 68052...
Wallet: scanned to height 68057...
Wallet: scanned to height 68060...
Wallet: scanned to height 68065...
Wallet: scanned to height 68072...
Wallet: scanned to height 68073...
Wallet: scanned to height 68075...
Wallet: scanned to height 68077...
Wallet: scanned to height 68080...
Wallet: scanned to height 68089...
Wallet: scanned to height 68091...
Wallet: scanned to height 68097...
Wallet: scanned to height 68103...
Wallet: scanned to height 68110...
Wallet: scanned to height 68114...
Wallet: scanned to height 68124...
Wallet: scanned to height 68129...
Wallet: scanned to height 68135...
Wallet: scanned to height 68137...
Wallet: scanned to height 68144...
Wallet: scanned to height 68147...
Wallet: scanned to height 68149...
Wallet: scanned to height 68151...
Wallet: scanned to height 68160...
Wallet: scanned to height 68165...
Wallet: scanned to height 68171...
Wallet: scanned to height 68180...
Wallet: scanned to height 68185...
Wallet: scanned to height 68192...
Wallet: scanned to height 68196...
Wallet: scanned to height 68206...
Wallet: scanned to height 68217...
Wallet: scanned to height 68219...
Wallet: scanned to height 68221...
Wallet: scanned to height 68227...
Wallet: scanned to height 68228...
Wallet: scanned to height 68234...
Wallet: scanned to height 68238...
Wallet: scanned to height 68239...
Wallet: scanned to height 68246...
Wallet: scanned to height 68252...
Wallet: scanned to height 68258...
Wallet: scanned to height 68270...
Wallet: scanned to height 68272...
Wallet: scanned to height 68281...
Wallet: scanned to height 68282...
Wallet: scanned to height 68291...
Wallet: scanned to height 68297...
Wallet: scanned to height 68301...
Wallet: scanned to height 68307...
Wallet: scanned to height 68310...
Wallet: scanned to height 68318...
Wallet: scanned to height 68326...
Wallet: scanned to height 68334...
Wallet: scanned to height 68340...
Wallet: scanned to height 68345...
Wallet: scanned to height 68352...
Wallet: scanned to height 68357...
Wallet: scanned to height 68365...
Wallet: scanned to height 68371...
Wallet: scanned to height 68374...
Wallet: scanned to height 68379...
Wallet: scanned to height 68384...
Wallet: scanned to height 68395...
Wallet: scanned to height 68398...
Wallet: scanned to height 68400...
Wallet: scanned to height 68407...
Wallet: scanned to height 68414...
Wallet: scanned to height 68418...
Wallet: scanned to height 68430...
Wallet: scanned to height 68435...
Wallet: scanned to height 68446...
Wallet: scanned to height 68450...
Wallet: scanned to height 68459...
Wallet: scanned to height 68467...
Wallet: scanned to height 68477...
Wallet: scanned to height 68478...
Wallet: scanned to height 68487...
Wallet: scanned to height 68490...
Wallet: scanned to height 68493...
Wallet: scanned to height 68498...
Wallet: scanned to height 68505...
Wallet: scanned to height 68510...
Wallet: scanned to height 68515...
Wallet: scanned to height 68521...
Wallet: scanned to height 68527...
Wallet: scanned to height 68531...
Wallet: scanned to height 68549...
Wallet: scanned to height 68550...
Wallet: scanned to height 68557...
Wallet: scanned to height 68563...
Wallet: scanned to height 68570...
Wallet: scanned to height 68581...
Wallet: scanned to height 68587...
Wallet: scanned to height 68592...
Wallet: scanned to height 68601...
Wallet: scanned to height 68608...
Wallet: scanned to height 68609...
Wallet: scanned to height 68622...
Wallet: scanned to height 68638...
Wallet: scanned to height 68646...
Wallet: scanned to height 68653...
Wallet: scanned to height 68665...
Wallet: scanned to height 68672...
Wallet: scanned to height 68679...
Wallet: scanned to height 68686...
Wallet: scanned to height 68696...
Wallet: scanned to height 68705...
Wallet: scanned to height 68707...
Wallet: scanned to height 68714...
Wallet: scanned to height 68722...
Wallet: scanned to height 68735...
Wallet: scanned to height 68741...
Wallet: scanned to height 68751...
Wallet: scanned to height 68756...
Wallet: scanned to height 68761...
Wallet: scanned to height 68769...
Wallet: scanned to height 68782...
Wallet: scanned to height 68789...
Wallet: scanned to height 68800...
Wallet: scanned to height 68813...
Wallet: scanned to height 68814...
Wallet: scanned to height 68830...
Wallet: scanned to height 68834...
Wallet: scanned to height 68841...
Wallet: scanned to height 68859...
Wallet: scanned to height 68874...
Wallet: scanned to height 68879...
Wallet: scanned to height 68889...
Wallet: scanned to height 68890...
Wallet: scanned to height 68902...
Wallet: scanned to height 68910...
Wallet: scanned to height 68922...
Wallet: scanned to height 68930...
Wallet: scanned to height 68936...
Wallet: scanned to height 68950...
Wallet: scanned to height 68954...
Wallet: scanned to height 68959...
Wallet: scanned to height 68973...
Wallet: scanned to height 68980...
Wallet: scanned to height 68986...
Wallet: scanned to height 68988...
Wallet: scanned to height 69005...
Wallet: scanned to height 69012...
Wallet: scanned to height 69026...
Wallet: scanned to height 69031...
Wallet: scanned to height 69043...
Wallet: scanned to height 69056...
Wallet: scanned to height 69065...
Wallet: scanned to height 69070...
Wallet: scanned to height 69080...
Wallet: scanned to height 69085...
Wallet: scanned to height 69103...
Wallet: scanned to height 69118...
Wallet: scanned to height 69121...
Wallet: scanned to height 69127...
Wallet: scanned to height 69130...
Wallet: scanned to height 69147...
Wallet: scanned to height 69167...
Wallet: scanned to height 69168...
Wallet: scanned to height 69173...
Wallet: scanned to height 69190...
Wallet: scanned to height 69206...
Wallet: scanned to height 69213...
Wallet: scanned to height 69226...
Wallet: scanned to height 69254...
Wallet: scanned to height 69255...
Wallet: scanned to height 69273...
Wallet: scanned to height 69278...
Wallet: scanned to height 69289...
Wallet: scanned to height 69299...
Wallet: scanned to height 69312...
Wallet: scanned to height 69325...
Wallet: scanned to height 69331...
Wallet: scanned to height 69352...
Wallet: scanned to height 69359...
Wallet: scanned to height 69367...
Wallet: scanned to height 69376...
Wallet: scanned to height 69381...
Wallet: scanned to height 69401...
Wallet: scanned to height 69420...
Wallet: scanned to height 69429...
Wallet: scanned to height 69450...
Wallet: scanned to height 69470...
Wallet: scanned to height 69484...
Wallet: scanned to height 69496...
Wallet: scanned to height 69506...
Wallet: scanned to height 69546...
Wallet: scanned to height 69567...
Wallet: scanned to height 69607...
Wallet: scanned to height 69610...
Wallet: scanned to height 69635...
Wallet: scanned to height 69650...
Wallet: scanned to height 69667...
Wallet: scanned to height 69675...
Wallet: scanned to height 69705...
Wallet: scanned to height 69717...
Wallet: scanned to height 69741...
Wallet: scanned to height 69756...
Wallet: scanned to height 69764...
Wallet: scanned to height 69779...
Wallet: scanned to height 69797...
Wallet: scanned to height 69817...
Wallet: scanned to height 69826...
Wallet: scanned to height 69837...
Wallet: scanned to height 69849...
Wallet: scanned to height 69856...
Wallet: scanned to height 69867...
Wallet: scanned to height 69888...
Wallet: scanned to height 69895...
Wallet: scanned to height 69901...
Wallet: scanned to height 69920...
Wallet: scanned to height 69933...
Wallet: scanned to height 69964...
Wallet: scanned to height 69976...
Wallet: scanned to height 69990...
Wallet: scanned to height 70031...
Wallet: scanned to height 70057...
Wallet: scanned to height 70062...
Wallet: scanned to height 70072...
Wallet: scanned to height 70081...
Wallet: scanned to height 70082...
Wallet: scanned to height 70096...
Wallet: scanned to height 70121...
Wallet: scanned to height 70123...
Wallet: scanned to height 70143...
Wallet: scanned to height 70145...
Wallet: scanned to height 70166...
Wallet: scanned to height 70178...
Wallet: scanned to height 70180...
Wallet: scanned to height 70191...
Wallet: scanned to height 70206...
Wallet: scanned to height 70227...
Wallet: scanned to height 70234...
Wallet: scanned to height 70271...
Wallet: scanned to height 70278...
Wallet: scanned to height 70304...
Wallet: scanned to height 70310...
Wallet: scanned to height 70342...
Wallet: scanned to height 70383...
Wallet: scanned to height 70392...
Wallet: scanned to height 70399...
Wallet: scanned to height 70406...
Wallet: scanned to height 70429...
Wallet: scanned to height 70434...
Wallet: scanned to height 70465...
Wallet: scanned to height 70482...
Wallet: scanned to height 70487...
Wallet: scanned to height 70511...
Wallet: scanned to height 70532...
Wallet: scanned to height 70541...
Wallet: scanned to height 70546...
Wallet: scanned to height 70549...
Wallet: scanned to height 70550...
Wallet: scanned to height 70582...
Wallet: scanned to height 70601...
Wallet: scanned to height 70614...
Wallet: scanned to height 70622...
Wallet: scanned to height 70629...
Wallet: scanned to height 70630...
Wallet: scanned to height 70656...
Wallet: scanned to height 70686...
Wallet: scanned to height 70704...
Wallet: scanned to height 70723...
Wallet: scanned to height 70756...
Wallet: scanned to height 70776...
Wallet: scanned to height 70802...
Wallet: scanned to height 70843...
Wallet: scanned to height 70851...
Wallet: scanned to height 70864...
Wallet: scanned to height 70892...
Wallet: scanned to height 70904...
Wallet: scanned to height 70915...
Wallet: scanned to height 70955...
Wallet: scanned to height 70965...
Wallet: scanned to height 70977...
Wallet: scanned to height 70982...
Wallet: scanned to height 70987...
Wallet: scanned to height 71004...
Wallet: scanned to height 71034...
Wallet: scanned to height 71044...
Wallet: scanned to height 71080...
Wallet: scanned to height 71101...
Wallet: scanned to height 71112...
Wallet: scanned to height 71117...
Wallet: scanned to height 71146...
Wallet: scanned to height 71175...
Wallet: scanned to height 71223...
Wallet: scanned to height 71251...
Wallet: scanned to height 71258...
Wallet: scanned to height 71303...
Wallet: scanned to height 71308...
Wallet: scanned to height 71358...
Wallet: scanned to height 71376...
Wallet: scanned to height 71407...
Wallet: scanned to height 71419...
Wallet: scanned to height 71432...
Wallet: scanned to height 71438...
Wallet: scanned to height 71444...
Wallet: scanned to height 71483...
Wallet: scanned to height 71500...
Wallet: scanned to height 71508...
Wallet: scanned to height 71515...
Wallet: scanned to height 71534...
Wallet: scanned to height 71555...
Wallet: scanned to height 71604...
Wallet: scanned to height 71617...
Wallet: scanned to height 71649...
Wallet: scanned to height 71678...
Wallet: scanned to height 71723...
Wallet: scanned to height 71771...
Wallet: scanned to height 71781...
Wallet: scanned to height 71830...
Wallet: scanned to height 71851...
Wallet: scanned to height 71861...
Wallet: scanned to height 71882...
Wallet: scanned to height 71918...
Wallet: scanned to height 71942...
Wallet: scanned to height 71952...
Wallet: scanned to height 71972...
Wallet: scanned to height 71996...
Wallet: scanned to height 71999...
Wallet: scanned to height 72012...
Wallet: scanned to height 72018...
Wallet: scanned to height 72033...
Wallet: scanned to height 72075...
Wallet: scanned to height 72107...
Wallet: scanned to height 72130...
Wallet: scanned to height 72135...
Wallet: scanned to height 72190...
Wallet: scanned to height 72207...
Wallet: scanned to height 72218...
Wallet: scanned to height 72232...
Wallet: scanned to height 72279...
Wallet: scanned to height 72307...
Wallet: scanned to height 72316...
Wallet: scanned to height 72327...
Wallet: scanned to height 72339...
Wallet: scanned to height 72352...
Wallet: scanned to height 72366...
Wallet: scanned to height 72381...
Wallet: scanned to height 72387...
Wallet: scanned to height 72412...
Wallet: scanned to height 72422...
Wallet: scanned to height 72457...
Wallet: scanned to height 72515...
Wallet: scanned to height 72526...
Wallet: scanned to height 72560...
Wallet: scanned to height 72569...
Wallet: scanned to height 72580...
Wallet: scanned to height 72606...
Wallet: scanned to height 72633...
Wallet: scanned to height 72643...
Wallet: scanned to height 72650...
Wallet: scanned to height 72668...
Wallet: scanned to height 72688...
Wallet: scanned to height 72726...
Wallet: scanned to height 72736...
Wallet: scanned to height 72785...
Wallet: scanned to height 72804...
Wallet: scanned to height 72821...
Wallet: scanned to height 72831...
Wallet: scanned to height 72877...
Wallet: scanned to height 72889...
Wallet: scanned to height 72911...
Wallet: scanned to height 72936...
Wallet: scanned to height 72946...
Wallet: scanned to height 72995...
Wallet: scanned to height 73012...
Wallet: scanned to height 73040...
Wallet: scanned to height 73072...
Wallet: scanned to height 73086...
Wallet: scanned to height 73090...
Wallet: scanned to height 73142...
Wallet: scanned to height 73176...
Wallet: scanned to height 73182...
Wallet: scanned to height 73211...
Wallet: scanned to height 73237...
Wallet: scanned to height 73289...
Wallet: scanned to height 73341...
Wallet: scanned to height 73349...
Wallet: scanned to height 73379...
Wallet: scanned to height 73391...
Wallet: scanned to height 73395...
Wallet: scanned to height 73433...
Wallet: scanned to height 73437...
Wallet: scanned to height 73469...
Wallet: scanned to height 73507...
Wallet: scanned to height 73543...
Wallet: scanned to height 73566...
Wallet: scanned to height 73595...
Wallet: scanned to height 73608...
Wallet: scanned to height 73637...
Wallet: scanned to height 73665...
Wallet: scanned to height 73707...
Wallet: scanned to height 73708...
Wallet: scanned to height 73722...
Wallet: scanned to height 73750...
Wallet: scanned to height 73781...
Wallet: scanned to height 73803...
Wallet: scanned to height 73810...
Wallet: scanned to height 73819...
Wallet: scanned to height 73863...
Wallet: scanned to height 73869...
Wallet: scanned to height 73888...
Wallet: scanned to height 73913...
Wallet: scanned to height 73929...
Wallet: scanned to height 73946...
Wallet: scanned to height 73948...
Wallet: scanned to height 73957...
Wallet: scanned to height 73988...
Wallet: scanned to height 73994...
Wallet: scanned to height 74011...
Wallet: scanned to height 74033...
Wallet: scanned to height 74087...
Wallet: scanned to height 74117...
Wallet: scanned to height 74121...
Wallet: scanned to height 74150...
Wallet: scanned to height 74186...
Wallet: scanned to height 74204...
Wallet: scanned to height 74212...
Wallet: scanned to height 74219...
Wallet: scanned to height 74228...
Wallet: scanned to height 74248...
Wallet: scanned to height 74270...
Wallet: scanned to height 74288...
Wallet: scanned to height 74312...
Wallet: scanned to height 74327...
Wallet: scanned to height 74341...
Wallet: scanned to height 74366...
Wallet: scanned to height 74368...
Wallet: scanned to height 74410...
Wallet: scanned to height 74421...
Wallet: scanned to height 74451...
Wallet: scanned to height 74496...
Wallet: scanned to height 74525...
Wallet: scanned to height 74526...
Wallet: scanned to height 74576...
Wallet: scanned to height 74601...
Wallet: scanned to height 74614...
Wallet: scanned to height 74671...
Wallet: scanned to height 74681...
Wallet: scanned to height 74705...
Wallet: scanned to height 74736...
Wallet: scanned to height 74803...
Wallet: scanned to height 74809...
Wallet: scanned to height 74837...
Wallet: scanned to height 74861...
Wallet: scanned to height 74867...
Wallet: scanned to height 74896...
Wallet: scanned to height 74910...
Wallet: scanned to height 74913...
Wallet: scanned to height 74924...
Wallet: scanned to height 74962...
Wallet: scanned to height 74984...
Wallet: scanned to height 74985...
Wallet: scanned to height 75006...
Wallet: scanned to height 75042...
Wallet: scanned to height 75079...
Wallet: scanned to height 75097...
Wallet: scanned to height 75108...
Wallet: scanned to height 75108...
Wallet: scanned to height 75118...
Wallet: scanned to height 75162...
Wallet: scanned to height 75180...
Wallet: scanned to height 75235...
Wallet: scanned to height 75258...
Wallet: scanned to height 75306...
Wallet: scanned to height 75322...
Wallet: scanned to height 75327...
Wallet: scanned to height 75377...
Wallet: scanned to height 75390...
Wallet: scanned to height 75445...
Wallet: scanned to height 75448...
Wallet: scanned to height 75462...
Wallet: scanned to height 75494...
Wallet: scanned to height 75552...
Wallet: scanned to height 75574...
Wallet: scanned to height 75591...
Wallet: scanned to height 75594...
Wallet: scanned to height 75634...
Wallet: scanned to height 75642...
Wallet: scanned to height 75671...
Wallet: scanned to height 75679...
Wallet: scanned to height 75720...
Wallet: scanned to height 75731...
Wallet: scanned to height 75752...
Wallet: scanned to height 75801...
Wallet: scanned to height 75835...
Wallet: scanned to height 75863...
Wallet: scanned to height 75891...
Wallet: scanned to height 75933...
Wallet: scanned to height 75982...
Wallet: scanned to height 75993...
Wallet: scanned to height 76004...
Wallet: scanned to height 76052...
Wallet: scanned to height 76066...
Wallet: scanned to height 76109...
Wallet: scanned to height 76121...
Wallet: scanned to height 76143...
Wallet: scanned to height 76175...
Wallet: scanned to height 76199...
Wallet: scanned to height 76208...
Wallet: scanned to height 76213...
Wallet: scanned to height 76216...
Wallet: scanned to height 76219...
Wallet: scanned to height 76232...
Wallet: scanned to height 76254...
Wallet: scanned to height 76258...
Wallet: scanned to height 76290...
Wallet: scanned to height 76305...
Wallet: scanned to height 76308...
Wallet: scanned to height 76319...
Wallet: scanned to height 76355...
Wallet: scanned to height 76383...
Wallet: scanned to height 76403...
Wallet: scanned to height 76405...
Wallet: scanned to height 76408...
Wallet: scanned to height 76415...
Wallet: scanned to height 76422...
Wallet: scanned to height 76424...
Wallet: scanned to height 76432...
Wallet: scanned to height 76434...
Wallet: scanned to height 76459...
Wallet: scanned to height 76475...
Wallet: scanned to height 76482...
Wallet: scanned to height 76486...
Wallet: scanned to height 76489...
Wallet: scanned to height 76516...
Wallet: scanned to height 76538...
Wallet: scanned to height 76571...
Wallet: scanned to height 76583...
Wallet: scanned to height 76609...
Wallet: scanned to height 76654...
Wallet: scanned to height 76677...
Wallet: scanned to height 76706...
Wallet: scanned to height 76716...
Wallet: scanned to height 76725...
Wallet: scanned to height 76734...
Wallet: scanned to height 76760...
Wallet: scanned to height 76805...
Wallet: scanned to height 76832...
Wallet: scanned to height 76852...
Wallet: scanned to height 76862...
Wallet: scanned to height 76881...
Wallet: scanned to height 76886...
Wallet: scanned to height 76908...
Wallet: scanned to height 76949...
Wallet: scanned to height 76971...
Wallet: scanned to height 76987...
Wallet: scanned to height 76994...
Wallet: scanned to height 77029...
Wallet: scanned to height 77037...
Wallet: scanned to height 77060...
Wallet: scanned to height 77084...
Wallet: scanned to height 77102...
Wallet: scanned to height 77114...
Wallet: scanned to height 77128...
Wallet: scanned to height 77141...
Wallet: scanned to height 77176...
Wallet: scanned to height 77190...
Wallet: scanned to height 77206...
Wallet: scanned to height 77228...
Wallet: scanned to height 77247...
Wallet: scanned to height 77269...
Wallet: scanned to height 77282...
Wallet: scanned to height 77285...
Wallet: scanned to height 77287...
Wallet: scanned to height 77297...
Wallet: scanned to height 77318...
Wallet: scanned to height 77351...
Wallet: scanned to height 77366...
Wallet: scanned to height 77368...
Wallet: scanned to height 77375...
Wallet: scanned to height 77396...
Wallet: scanned to height 77406...
Wallet: scanned to height 77454...
Wallet: scanned to height 77455...
Wallet: scanned to height 77477...
Wallet: scanned to height 77483...
Wallet: scanned to height 77490...
Wallet: scanned to height 77505...
Wallet: scanned to height 77518...
Wallet: scanned to height 77545...
Wallet: scanned to height 77562...
Wallet: scanned to height 77586...
Wallet: scanned to height 77601...
Wallet: scanned to height 77639...
Wallet: scanned to height 77661...
Wallet: scanned to height 77665...
Wallet: scanned to height 77702...
Wallet: scanned to height 77725...
Wallet: scanned to height 77726...
Wallet: scanned to height 77747...
Wallet: scanned to height 77772...
Wallet: scanned to height 77774...
Wallet: scanned to height 77785...
Wallet: scanned to height 77819...
Wallet: scanned to height 77830...
Wallet: scanned to height 77846...
Wallet: scanned to height 77869...
Wallet: scanned to height 77887...
Wallet: scanned to height 77917...
Wallet: scanned to height 77934...
Wallet: scanned to height 77943...
Wallet: scanned to height 77986...
Wallet: scanned to height 78009...
Wallet: scanned to height 78018...
Wallet: scanned to height 78057...
Wallet: scanned to height 78068...
Wallet: scanned to height 78110...
Wallet: scanned to height 78120...
Wallet: scanned to height 78137...
Wallet: scanned to height 78139...
Wallet: scanned to height 78175...
Wallet: scanned to height 78192...
Wallet: scanned to height 78196...
Wallet: scanned to height 78211...
Wallet: scanned to height 78227...
Wallet: scanned to height 78242...
Wallet: scanned to height 78257...
Wallet: scanned to height 78272...
Wallet: scanned to height 78275...
Wallet: scanned to height 78319...
Wallet: scanned to height 78325...
Wallet: scanned to height 78371...
Wallet: scanned to height 78402...
Wallet: scanned to height 78423...
Wallet: scanned to height 78469...
Wallet: scanned to height 78502...
Wallet: scanned to height 78517...
Wallet: scanned to height 78544...
Wallet: scanned to height 78583...
Wallet: scanned to height 78610...
Wallet: scanned to height 78625...
Wallet: scanned to height 78654...
Wallet: scanned to height 78686...
Wallet: scanned to height 78707...
Wallet: scanned to height 78748...
Wallet: scanned to height 78763...
Wallet: scanned to height 78794...
Wallet: scanned to height 78819...
Wallet: scanned to height 78831...
Wallet: scanned to height 78840...
Wallet: scanned to height 78845...
Wallet: scanned to height 78891...
Wallet: scanned to height 78913...
Wallet: scanned to height 78934...
Wallet: scanned to height 78986...
Wallet: scanned to height 79015...
Wallet: scanned to height 79045...
Wallet: scanned to height 79054...
Wallet: scanned to height 79104...
Wallet: scanned to height 79106...
Wallet: scanned to height 79112...
Wallet: scanned to height 79125...
Wallet: scanned to height 79164...
Wallet: scanned to height 79167...
Wallet: scanned to height 79175...
Wallet: scanned to height 79203...
Wallet: scanned to height 79213...
Wallet: scanned to height 79221...
Wallet: scanned to height 79241...
Wallet: scanned to height 79292...
Wallet: scanned to height 79308...goroutine 1 [running]:
runtime/debug.Stack(0x1043857, 0x0, 0xc4204b35f8)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Critical(0xc4204b3948, 0x1, 0x1)
/home/luke/go/src/github.com/NebulousLabs/Sia/build/critical.go:15 +0xa7
main.startDaemon(0x0, 0x0, 0x7fff5fbffccc, 0xe, 0x7fff5fbffcf8, 0x5, 0x7fff5fbffce7, 0x5, 0x0, 0x7fff5fbffd08, ...)
/home/luke/go/src/github.com/NebulousLabs/Sia/siad/daemon.go:295 +0xaa9
main.startDaemonCmd(0xc420081200, 0xc4200194a0, 0x0, 0x5)
/home/luke/go/src/github.com/NebulousLabs/Sia/siad/daemon.go:309 +0x6d
github.com/spf13/cobra.(*Command).execute(0xc420081200, 0xc42000e0d0, 0x5, 0x5, 0xc420081200, 0xc42000e0d0)
/home/luke/go/src/github.com/spf13/cobra/command.go:648 +0x234
github.com/spf13/cobra.(*Command).ExecuteC(0xc420081200, 0x16c6004, 0x3b, 0xc4201548c0)
/home/luke/go/src/github.com/spf13/cobra/command.go:734 +0x339
github.com/spf13/cobra.(*Command).Execute(0xc420081200, 0x1aa4520, 0x16af49d)
/home/luke/go/src/github.com/spf13/cobra/command.go:693 +0x2b
main.main()
/home/luke/go/src/github.com/NebulousLabs/Sia/siad/main.go:174 +0x7ac
Critical error: accept tcp <IP_ADDRESS>:9980: accept: too many open files in system
Please submit a bug report here: https://github.com/NebulousLabs/Sia/issues
Closing renter...

Can you try unlocking using just siad and siac to determine if this is a Sia-UI problem?

It seems that it was a problem with the wallet files. I re-inited the
wallet from seed and now it works correctly even in the Sia-UI.
--
Adam Nohejl
On 28 Apr 2017, at 20:34, Johnathan Howell wrote:

Can you try unlocking using just siad and siac to determine if
this is a Sia-UI problem?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/NebulousLabs/Sia/issues/1750#issuecomment-298074090

Sorry for being dumb, I'm having the same on 1.2.2.  I've increased the ulimit, waited for the blockchain to sync but the wallet keeps crashing with the same error mentioned.
Any tips or commands to resolve this?  Being relatively new "I re-inited the wallet from seed" hasn't turned much up for me yet.
Thanks
Dave


Pycosat Statistics

Hey guys,
great binding. I was wondering if it would be possible to include the statistics that are available in the pure C version?
/------------------------------------------------------------------------/
/* Statistics.
/
int picosat_variables (PicoSAT *);                      / p cnf  n /
int picosat_added_original_clauses (PicoSAT *);         / p cnf m  /
size_t picosat_max_bytes_allocated (PicoSAT *);
double picosat_time_stamp (void);                       / ... in process /
void picosat_stats (PicoSAT *);                         / > output file /
unsigned long long picosat_propagations (PicoSAT *);    / #propagations /
unsigned long long picosat_decisions (PicoSAT *);   / #decisions /
unsigned long long picosat_visits (PicoSAT *); / #visits */
Thanks!

@trdavidson did you figure out how to get these statistics?

Has there been any progress on this?


Add ability to check if a certain Skill-Tree-node is active or Add activation logic

Activation logic as in: When the skill-tree-node is learnt, the logic behind it is activated or at least broadcasts its activation. Including an id, so you could have effects/traits etc. that get activated as soon as a skill-node is learnt/active

I can do the "broadcast" via a global-event to which the developer could connect to or having to add a parent skill-tree or something similar to that.


feat: user api token - [merged]

Merges 63-feat-user-api-token -> development
:books: Summary

:link: Links / References

#63

:construction_worker: Tasks

[ ] ~"breaking-change" Any Breaking change(s)
Breaking Change must also be notated in the commit that introduces it and in Conventional Commit Format.

[x] ~Documentation Documentation written
All features to be documented within the correct section(s). Administration, Development and/or User

[x] Milestone assigned

[x] Unit Test(s) Written
ensure test coverage delta is not less than zero

mentioned in commit e655f22fac4d7de2ef42f16f33c8427528b63481

added 2 commits
37d277e1 - refactor(settings): use form for user settings66b8d936 - refactor(settings): use seperate change/view views
Compare with previous version

mentioned in commit 37d277e1493ab708b8861fa8d0de3191da24d2f2

added 5h of time spent

added 31h of time spent

added 1h of time spent

mentioned in commit ce2c6f3b135ec9110682db3b77c80d6dde26a3c2

added 1h of time spent

added 1 commit
ce2c6f3b - feat(api): abilty for user to create/delete api token
Compare with previous version

mentioned in commit 111791438a45a8eb0cf4c175e4a1439cd56c84da

mentioned in commit e6c47b6a7cbd17cb503565a45bacdc2ac934ae2f

mentioned in commit 47d6a3beffa7bb3d5b822c54440fe8b31ad18e02

added 1 commit
0f9bab2e - feat(api): API token authentication
Compare with previous version

mentioned in commit 0f9bab2e01a867ad8efd7fa59293781486751d22

added 1 commit
11179143 - feat(api): API token authentication
Compare with previous version

added 2h 40m of time spent

added 2 commits
47d6a3be - docs(api): API Token authenticatione6c47b6a - docs: Add user settings documentation
Compare with previous version

mentioned in commit 6cfcf1580c669c046e4dd6d547b99c8b9814a078

added 2 commits
6cfcf158 - fix(user_token): conduct user check on token view access792d2eed - test(token_auth): test authentication method token
Compare with previous version

mentioned in commit 792d2eed0d7fedd10c851788c7cbd7733d8684b8

added 47m of time spent

added 41m of time spent

added 1 commit
4d3a2385 - docs: Add user settings documentation
Compare with previous version

mentioned in commit 4d3a2385831c4db99bb9f3e70411b3d2d4d624f0

added 50m of time spent

added 2h of time spent

marked the checklist item ~Documentation Documentation written as completed

marked the checklist item Unit Test(s) Written as completed

marked the checklist item Milestone assigned as completed

added 1 commit
53284d45 - test(token_auth): test authentication method token
Compare with previous version

mentioned in commit 53284d456f21012da4b2800a173141a1a8b292e0

mentioned in commit 05c46df0a9078afa2307d2fb0aaec755b3503c92


Parse Server Limitations

This isn't an issue as much as it's a question:
With hosting your own instance of Parse Server, are the limitations here still in effect?

Some of them are (due to being limitations of the underlying MongoDB) and some of them aren't. We don't have a complete guide on limitations yet, but in general you can expect that object size and query related limitations are still there, and Cloud Code related limits are not. Also, by having full access to the DB, you can build your own indexes, which means you can change some of these limits if you put in some effort.

How parse-server manages ParseUser object? e.g. I store a ParseUser around 400 bytes. Let's say I have 40k (hitting 16mb - mongo limit) users signup. On 40001 signup, what happen?


Complex shapes

Added a 'Complex' shape type, constructor, and extended transformations to handle it. This allows for grouping multiple shapes into a single compound shape which can then have the libraries' various transformations applied to it.

Thanks for the contribution! @FayCarsons
LGTM! 👍


Investigate why tests fail locally and pass on CI

I wanted to release patch 2.3.2 (arbitrum hotfix) but got slowed down, because tests were failing locally (and they pass on CI).
I've temporarily modified the release script locally not-to-run the unit tests.

They are passing now - not sure what was the issue.


Version 39.0.2171.95 m of Chrome not showing close button

Lighter works like charm on all platforms and browsers I've tested it on. Except when I'm using Version 39.0.2171.95 m of Chrome on w8.1 the popup/overlay it too big and expands off screen so the close buttons is inaccessible/does no show.
Cheers
Rickard

@CarolusW Hey, sorry for the delay but would you mind re-verifying now? I added a few animation fixes and think this might be fixed in v1.2.4 but had a tough time reproducing as I don't run Windows 8.1.

closing due to no response.


chore: more byAsSorry backports

Thanks @mattrobball, I've resolved your helpful suggestions.

bors merge


Custom serialization example with namespace

Enhanced custom serialization example to use namespace for the object.

Test PASSed.


Added Cosine Annealing Warmup Restarts With Decay optimiser

This is an optimiser that is a variant of the Cosine Annealing Restart scheduler or the OneCycleLR optimiser. The added optimiser can decrease over time the maximum learning rate it warms up to and can increase the length of the decay cycle over time. If we set T_warmup=0, gamma=1.0 we recover the base  CosineAnnealingWarmRestarts.
This was based on the observation that CREStereo generally reacts better to a constantly changing learning rate as opposed to the default scheduler proposed in the paper. Bellow is an example of a schedule generated with a value of gamma < 1.0 and a value of T_warmup > 0

This was based on the observation that CREStereo generally reacts better to a constantly changing learning rate as opposed to the default scheduler proposed in the paper.

To avoid adding unnecessary complexity on the references, it's worth starting from the paper's proposal first. If you can't reproduce the results and you need an extra boost, we could consider adding new optimizers. wdyt?

There are multiple people stating on the original repo that they have trouble reproducing the performance claimed by the authors with the training code provided by them.
This is something I have noticed as well during my training runs. It can however be ameliorated with much simpler scheduling. We can skip this PR all-together, I do not have any strong opinions on it.

@TeodorPoncu Thanks for the references! It's great that you tried reproducing it already.
From what I understand the nan value appears on the early epochs much before any restart. If that's the case, then the modified optimizer might have less effect on nans and it might be beneficial to do warmup at the beginning using one of the standard schedulers such as LinearLR or ConstantLR. If that doesn't work out then we should consider merging this PR.
In general it's not a big problem adding primitives in references, as long as they are necessary. For tasks such as Classification, we are more forgiving because some techniques are popular across multiple models and because we constantly do work on them. For Depth Perception that is still prototype, it would be great if we could keep things simple as long as we can reproduce the accuracies and we don't have a good reason to complicate things. So if you really need it, we can definitely add it. If you manage to work around it, that's a plus. :)

@datumbox I have already managed to work around both the NaN and some of the performance drop by simply adjusting the point at which the learning rate starts decaying, and by replacing the linear decay with a cosine. Therefor, the scheduler is just a minor nice-to-have / bonus.
The benefit of this schedule is in fine-tuning scenarios, solely for convergence time and a very minor performance boost.

@TeodorPoncu shall we close the PR given you managed to train the models and deploy the weights?

Yes, this could be closed.


Tracking issue for PubSub high-perf client integration

This issue tracks items we need to do to go from "the code works" to "we're happy with it"

[ ] Document explaining migration to HP client
[ ] Figure out the proper configuration for Publisher and Subscriber

Can executors be shared with the rest of the program?
Does each connection have its own channel?
See https://github.com/GoogleCloudPlatform/google-cloud-java/pull/1487 for context

Sample code

[ ] Publisher
[ ] Subscriber

Code snippets

[ ] Publisher
[ ] Subscriber

I prefer if we keep separate executors for publisher and subscriber (but also give the alternative for the user to provide his own executor). The reason being that it is easier to debug thread starvation problems and thread dumps when the executors are separate (i.e. you don't want the subscriber executor to starve the publisher if having problems to pull, renew-deadlines, etc)

In regards to the multiple channels, we need many channels in order to achieve the desired throughput

@pongad we may have taken care of enough of this tracking issue - maybe close it out, and if there are any tail-end tasks, create separate issues for them. I would like to avoid zombie issues.

This was a tracking issue for bundling implementation integration. That work is much more long term than I thought previously. Let's close it out.


Wallet balance is incorrect

The total wallet balance doesn't match the individual totals of each asset.

I've spent some time looking at this. There are no issues with the code (i.e. the values are what we would expect from the calculation) so I think we've made a mistake with the implementation, and the way in which the total/lent/borrow amount affect one another. Should be an easy fix—I'll talk it through with Dom and/or Sander, and update the requirements as necessary.


#1685 Add support for multiple results in salesforce batch jobs

Addresses #1685 by adding support to fetch multiple results from a single Salesforce batch job.
Open Items

[x] Merge downloaded files

Description

New get_batch_result_ids method that is more accurately documented
Backwards compatible get_batch_results method, including warning message
Small set of tests for the changes

Motivation and Context
Fixes #1685
Have you tested this? If so, how?
Included unit tests as well as verified locally.

Based on TravisCI results, looks like you just need to fix the few flake8 errors and then run the tests again. All the others look to be errors when creating the environment (stuff you didn't cause).
I haven't run this myself, but the logic looks good. Thanks!

D'oh. Of course I forget to run the flake8 test after I add the unit test. ;)
Addressing shortly.

Looks like you need to get @Tarrasch 's updates to Tox (that'll fix these tests).
git fetch upstream
git checkout master
git merge upstream/master
git checkout <this branch>
git rebase master

git push origin <this branch> --force

@dlstadther Thanks for the note re: Tox updates. Just pulled that in and pushed up an update that merges batch results (from CSV).

Looks like I have to some work to do re: python 3 compat.

[Current coverage][cc-pull] is 74.74%

Merging [#1686][cc-pull] into [master][cc-base-branch] will decrease coverage by 3.88%

@@             master      #1686   diff @@
==========================================
  Files            94         94
  Lines         10256      10287    +31
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           8063       7688   -375
- Misses         2193       2599   +406
  Partials          0          0

Powered by Codecov. Last updated by [187517b...ee7a5d4][cc-compare]
[cc-base-branch]: https://codecov.io/gh/spotify/luigi/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/spotify/luigi/compare/187517b0cecbdef2381ca6d02db926dbeccf477b...ee7a5d4d45f6ff8bbdee900502cfb41eb0679685
[cc-pull]: https://codecov.io/gh/spotify/luigi/pull/1686?src=pr

Good job. Thanks guys :)


missing_param

Hi @BayrakMustafa i tested the new RegisterCode method i got this response:
({"status":"fail","reason":"missing_param","param":"token"})

@eaba What is your country code?

Hi @BayrakMustafa please check, you where calling the wrong endpoint


Improve way of showing repositories

I slowly started to add Dependabot into all my open source repositories. They are less than 6, and I have to scroll in order to see the last one. I would love if the application can use more efficiently the available space in the screen.
Example

In case the client project is open source, I would gladly contribute to the project! 😄

Closing this as we're not investing more in the dashboard, which is being replaced by UI built into GitHub.


error in code

Hi,
My name is Sam and I was having a little trouble with Coding the MeArm. In the IDE I tried to verify the Wii classic controller code, and  I keep getting this error: "ClassicController dose not name a type." If anyone can help, I would really appreciate it.
Thanks,
Sam B.

Hi, the comments in the file say "Uses ClassicController library from https://github.com/wayneandlayne/Video-Game-Shield" - can you get that library and put it in your libraries folder?  That ought to do the trick.


Add support for indexing Audio setAttribute command

Description
As a part of #2, we should be able to index the audio:setAttribute transactions and list the Audio NFTs.
Acceptance Criteria

Index transactions of audio:setAttribute
Display updated audio NFTs attributes in the audios list
The above functionality must be tested (automated).

Resolved by #25


HTTP request failed after ISTIO_META_DNS_AUTO_ALLOCATE enabled

Bug Description
There is a ServiceEntry for example.com, port 9444 as TCP protocol.
HTTP requests to example.com:80 will also succeed.
apiVersion: networking.istio.io/v1beta1
kind: ServiceEntry
metadata:
  name: external-auto
spec:
  hosts:
  - example.com
  ports:
  - name: tcp
    number: 9444
    protocol: TCP
  resolution: DNS

After I enable ISTIO_META_DNS_AUTO_ALLOCATE, HTTP requests to example.com:80 always failed. Got 503 connection failure
Istio allocs a new IP for example.com. Destination of connections to this host will be changed to this IP and passthrough cluster will use ORIGIN DST to connect and fail.
Version
client version: 1.12.6
control plane version: 1.12.6
data plane version: 1.12.6

Additional Information
No response

same as https://github.com/istio/istio/issues/29224

@hzxuzhonghu Hi，there maybe a little different with #29224.
apiVersion: networking.istio.io/v1beta1
kind: ServiceEntry
metadata:
  name: external-auto
spec:
  hosts:
  - example.com
  ports:
  - name: tcp
    number: 9444
    protocol: TCP
  resolution: DNS

I define a TCP port in this ServiceEntry. Resolve example.com to an IP auto alloced by istio is expected since I will add VirtualService to this host and port. It needs to dstinguish the different host by IP.
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: auto-tls
spec:
  hosts:
  - "example.com"
  gateways:
  - mesh
  tcp:
  - match:
    - port: 9444
    route:
    - destination:
        host: sni-proxy
        subset: example-com-9444
        port:
          number: 443

It works well.
But curl example.com:80 failed. I'm not sure if we can route traffics to the alloced IP and ports except 9444 to a STRICT_DNS type cluster.

This is expected IMO. Original_dst will not work with this mode, as noted. When you define your svc entry for 9444, you are saying its ONLY on port 9444 (not 80). So you hit passthrough which ends up breaking.
Its not possible for us to somehow only return the fake IP for port 9444 since DNS is not port-aware.
ISTIO_META_DNS_AUTO_ALLOCATE is not something that can ever be 100% reliable

This is expected IMO. Original_dst will not work with this mode, as noted. When you define your svc entry for 9444, you are saying its ONLY on port 9444 (not 80). So you hit passthrough which ends up breaking.
Its not possible for us to somehow only return the fake IP for port 9444 since DNS is not port-aware.
ISTIO_META_DNS_AUTO_ALLOCATE is not something that can ever be 100% reliable

@howardjohn  Alright.
Another question. ISTIO_META_DNS_AUTO_ALLOCATE is global. Can I only enable it for specified serviceentries? So it will not affect existing serviceentries.

There is no such way now

If you want the opposite (opt-in to allocate) you can basically DIY it by just setting a random IP in the ServiceEntry.address YAML. That is basically what the feature does.

@howardjohn Great. Thank you for your reminding.


add CopyActiveFilepathToClipboard action

I'm currently using atom and this is one of my most used commands. Whenever I work on a test and I want to run that test only I use that command to the the path of the file I'm currently editing. Or basically if I want to do anything on the terminal with the file I use this.
I hope this is useful for other's as well.

@despairblue - looks great!
Really appreciate that you added the integration test as well (gives a lot of confidence that it works cross-platform too 👍 )
Thank you for the contribution!


FirebaseUiLogin

Hi, I have followed all the steps and yet I keep getting a runtime error, a nullPointerException error. Here
Where I have the onStart method. What am I missing?

If you implement the getFirebaseReference() method, that NPE will
disappear:
@Override
protected Firebase getFirebaseRef() {
return null;
}
On Tue, Mar 1, 2016 at 2:14 PM Martin Mwangi<EMAIL_ADDRESS>wrote:

Hi, I have followed all the steps and yet I keep getting a runtime error,
a nullPointerException error. Here
https://github.com/martmwangi/Logintest/blob/master/app/src/main/java/com/example/hulk/logintest/MainActivity.java
Where I have the onStart method. What am I missing?
—
Reply to this email directly or view it on GitHub
https://github.com/firebase/FirebaseUI-Android/issues/87.

Duplicate of https://github.com/firebase/FirebaseUI-Android/issues/85

Actually, I have and still am getting the same

The project you linked returns null from getFirebaseReference(). That
will raise an NPE. If your code doesn't do that, what is the linked code
for?
I'll need to either see the actual code or the full stack trace (and
preferably both) to be able to help here.
On Tue, Mar 1, 2016 at 7:06 PM Martin Mwangi<EMAIL_ADDRESS>wrote:

Actually, I have and still am getting the same
—
Reply to this email directly or view it on GitHub
https://github.com/firebase/FirebaseUI-Android/issues/87#issuecomment-190836152
.


Calling setData raises 'Cannot read property '$options' of undefined'

Version
1.0.0-beta.16
Reproduction link
https://codesandbox.io/s/6lm4248qjr
Steps to reproduce
In reproduction link, 1.0.0-beta.12 version is selected on which test is passing. Upgrading to any version after 1.0.0-beta.12 causes test to fail with error Cannot read property '$options' of undefined when setData is invoked.
What is expected?
Test should pass on later/latest versions as well.
What is actually happening?
Test is failing on vue-test-utils latest versions(after 1.0.0-beta.12 )

Since this worked fine on version 1.0.0-beta.12, i assume this bug could be side effect of PR https://github.com/vuejs/vue-test-utils/pull/438 merged in version 1.0.0-beta.13, as all ElementUI components used in the sample reproduction link are not functional components, so it should work ok on latest version as well. Links to component's used in this sample are below for reference:
https://github.com/ElemeFE/element/blob/v2.3.8/packages/form/src/form.vue
https://github.com/ElemeFE/element/blob/v2.3.8/packages/form/src/form-item.vue
https://github.com/ElemeFE/element/blob/v2.3.8/packages/input/src/input.vue

Thank you providing the update on this and suggesting workaround. 👍

I was facing this issue and when i realized a fix was provided, I updated from 1.0.0-beta.16 to 1.0.0-beta.18 and all my tests are breaking.

There is a bug where stubs and mocks aren't applied correctly to extended components, including the class component. The fix will be released soon.
The issue here is still unresolved.

I have a very similar case, I don't know, if it  should be a separate issue:
When upgrading from 1.0.0-beta.17 (up to 1.0.0-beta.20 I tried), all my components that use vuelidate are unable to reach data(). If I try and test if the initial values are correctly set, I get an error message: Cannot read property 'validations' of undefined.
If I use it like this:
const data = vm.$options.data
expect(data().someValue).toEqual('value')

then I get Cannot read property '$options' of undefined.
If I change to
expect(vm.$options.data().someValue).toEqual('value')

then the error message changes to the one above.
Both worked under 1.0.0-beta.17, and vuelidate didn't change since.
Any ideas?

Sorry about this. Can you post a minimal reproduction?

Steps to reproduce
package.json
{
  "name": "vue-test-utils-jest-example",
  "version": "1.0.0",
  "description": "A Vue.js project",
  "author": "Edd Yerburgh<EMAIL_ADDRESS>  "scripts": {
    "dev": "node build/dev-server.js",
    "start": "node build/dev-server.js",
    "build": "node build/build.js",
    "lint": "eslint --ext .js,.vue src test",
    "lint:fix": "npm run lint --fix",
    "unit": "jest"
  },
  "dependencies": {
    "@vue/test-utils": "^1.0.0-beta.20",
    "element-ui": "^2.4.2",
    "vue": "^2.5.16",
    "vue-router": "^2.6.0"
  },
  "devDependencies": {
    "autoprefixer": "^7.1.2",
    "babel-core": "^6.22.1",
    "babel-eslint": "^7.1.1",
    "babel-jest": "^23.2.0",
    "babel-loader": "^7.1.1",
    "babel-plugin-module-resolver": "^2.7.1",
    "babel-plugin-transform-runtime": "^6.22.0",
    "babel-preset-env": "^1.3.2",
    "babel-preset-stage-2": "^6.22.0",
    "babel-register": "^6.22.0",
    "chalk": "^2.0.1",
    "connect-history-api-fallback": "^1.3.0",
    "css-loader": "^0.28.0",
    "cssnano": "^3.10.0",
    "eslint": "^3.19.0",
    "eslint-config-standard": "^6.2.1",
    "eslint-friendly-formatter": "^3.0.0",
    "eslint-loader": "^1.7.1",
    "eslint-plugin-html": "^3.0.0",
    "eslint-plugin-promise": "^3.4.0",
    "eslint-plugin-standard": "^2.0.1",
    "eventsource-polyfill": "^0.9.6",
    "express": "^4.14.1",
    "extract-text-webpack-plugin": "^2.0.0",
    "file-loader": "^0.11.1",
    "friendly-errors-webpack-plugin": "^1.1.3",
    "html-webpack-plugin": "^2.28.0",
    "http-proxy-middleware": "^0.17.3",
    "jest": "^23.2.0",
    "jest-serializer-vue": "^2.0.2",
    "opn": "^5.1.0",
    "optimize-css-assets-webpack-plugin": "^2.0.0",
    "ora": "^1.2.0",
    "rimraf": "^2.6.0",
    "semver": "^5.3.0",
    "shelljs": "^0.7.6",
    "url-loader": "^0.5.8",
    "vue-jest": "^2.6.0",
    "vue-loader": "^12.1.0",
    "vue-server-renderer": "^2.5.16",
    "vue-style-loader": "^3.0.1",
    "vue-template-compiler": "^2.5.16",
    "webpack": "^2.6.1",
    "webpack-bundle-analyzer": "^2.2.1",
    "webpack-dev-middleware": "^1.10.0",
    "webpack-hot-middleware": "^2.18.0",
    "webpack-merge": "^4.1.0"
  },
  "engines": {
    "node": ">= 4.0.0",
    "npm": ">= 3.0.0"
  },
  "browserslist": [
    "> 1%",
    "last 2 versions",
    "not ie <= 8"
  ],
  "jest": {
    "moduleFileExtensions": [
      "js",
      "json",
      "vue"
    ],
    "transform": {
      "^.+\\.js$": "<rootDir>/node_modules/babel-jest",
      ".*\\.(vue)$": "<rootDir>/node_modules/vue-jest"
    },
    "snapshotSerializers": [
      "<rootDir>/node_modules/jest-serializer-vue"
    ]
  }
}

Component with ElementUI dropdown and table
<template>

  <el-select v-model="value" placeholder="Select">
    <el-option
      v-for="item in options"
      :key="item.value"
      :label="item.label"
      :value="item.value">
    </el-option>
  </el-select>

  <el-table
      :data="tableData"
      style="width: 100%">
      <el-table-column
        prop="date"
        label="Date"
        width="180">
      </el-table-column>
      <el-table-column
        prop="name"
        label="Name"
        width="180">
      </el-table-column>
      <el-table-column
        prop="address"
        label="Address">
      </el-table-column>
    </el-table>

</template>

Test
import { mount, createLocalVue } from '@vue/test-utils'
import { createRenderer } from 'vue-server-renderer'
import ElementUI from 'element-ui'
import DropDownSample from<EMAIL_ADDRESS>
let localVue = createLocalVue()
localVue.use(ElementUI)

describe('DropDownSample.vue', () => {
  it('displays default message', () => {
    const wrapper = mount(DropDownSample, { localVue })
    const renderer = createRenderer()

    renderer.renderToString(wrapper.vm, (err, str) => {
      if (err) throw new Error(err)
      expect(str).toMatchSnapshot()
    })
  })
})

Test Results
 yarn unit
yarn run v1.7.0
warning package.json: No license field
$ jest
 PASS  src/components/__tests__/DropDownSample.spec.js
  DropDownSample.vue
    √ displays default message (140ms)

  console.error node_modules/vue/dist/vue.runtime.common.js:589
    [Vue warn]: Error in callback for watcher "options": "TypeError: Cannot read property 'querySelectorAll' of undefined"

    found in

    ---> <ElSelect>
           <DropdownSample>
             <Root>

  console.error node_modules/vue/dist/vue.runtime.common.js:1739
    TypeError: Cannot read property 'querySelectorAll' of undefined
        at VueComponent.options (C:\Projects\Issues\vue-unit-test-starter\node_modules\element-ui\lib\element-ui.common.js:8567:29)
        at Watcher.run (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:3231:19)
        at flushSchedulerQueue (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:2979:13)
        at Array.<anonymous> (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:1835:12)
        at flushCallbacks (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:1756:14)
        at <anonymous>
        at process._tickCallback (internal/process/next_tick.js:188:7)

  console.error node_modules/vue/dist/vue.runtime.common.js:589
    [Vue warn]: Error in nextTick: "TypeError: Cannot read property 'clientWidth' of undefined"

  console.error node_modules/vue/dist/vue.runtime.common.js:1739
    TypeError: Cannot read property 'clientWidth' of undefined
        at TableLayout.updateColumnsWidth (C:\Projects\Issues\vue-unit-test-starter\node_modules\element-ui\lib\element-ui.common.js:11450:36)
        at VueComponent.updateScrollY (C:\Projects\Issues\vue-unit-test-starter\node_modules\element-ui\lib\element-ui.common.js:10269:19)
        at C:\Projects\Issues\vue-unit-test-starter\node_modules\element-ui\lib\element-ui.common.js:10829:26
        at Array.<anonymous> (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:1835:12)
        at flushCallbacks (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:1756:14)
        at <anonymous>
        at process._tickCallback (internal/process/next_tick.js:188:7)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   1 passed, 1 total
Time:        2.822s, estimated 3s
Ran all test suites.
Done in 3.89s.

Can you try setting sync to false and use Vue.nextTick to await DOM updates:
test('use Vue.nextTick', (done) => {
  const wrapper = mount(TestComponent, { sync: false })
  wrapper.trigger('click')
  Vue.nextTick(() => {
    expect(wrapper.text()).toBe('updated')
    done()
  })
})

I changed the test as below (sync is set to false and Vue.nextTick is used)
But the test results is still the same.
import Vue from "vue"
import { mount, createLocalVue } from "@vue/test-utils"
import { createRenderer } from "vue-server-renderer"
import ElementUI from "element-ui"
import DropDownSample from<EMAIL_ADDRESS>
let localVue = createLocalVue()
localVue.use(ElementUI)

describe("DropDownSample.vue", () => {
  it("displays default message", () => {
    const wrapper = mount(DropDownSample, { sync: false, localVue })
    const renderer = createRenderer()
    Vue.nextTick(() => {
      renderer.renderToString(wrapper.vm, (err, str) => {
        if (err) throw new Error(err)
        expect(str).toMatchSnapshot()
      })
    })
  })
})

Test Results
PS C:\Projects\Issues\vue-unit-test-starter> yarn unit
yarn run v1.7.0
warning package.json: No license field
$ jest
 PASS  src/components/__tests__/DropDownSample.spec.js
  DropDownSample.vue
    √ displays default message (265ms)

  console.error node_modules/vue/dist/vue.runtime.common.js:589
    [Vue warn]: Error in callback for watcher "options": "TypeError: Cannot read property 'querySelectorAll' of undefined"

    found in

    ---> <ElSelect>
           <DropdownSample>
             <Root>

  console.error node_modules/vue/dist/vue.runtime.common.js:1739
    TypeError: Cannot read property 'querySelectorAll' of undefined
        at VueComponent.options (C:\Projects\Issues\vue-unit-test-starter\node_modules\element-ui\lib\element-ui.common.js:8567:29)
        at Watcher.run (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:3231:19)
        at flushSchedulerQueue (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:2979:13)
        at Array.<anonymous> (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:1835:12)
        at flushCallbacks (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:1756:14)
        at <anonymous>

  console.error node_modules/vue/dist/vue.runtime.common.js:589
    [Vue warn]: Error in nextTick: "TypeError: Cannot read property 'clientWidth' of undefined"

  console.error node_modules/vue/dist/vue.runtime.common.js:1739
    TypeError: Cannot read property 'clientWidth' of undefined
        at TableLayout.updateColumnsWidth (C:\Projects\Issues\vue-unit-test-starter\node_modules\element-ui\lib\element-ui.common.js:11450:36)
        at VueComponent.updateScrollY (C:\Projects\Issues\vue-unit-test-starter\node_modules\element-ui\lib\element-ui.common.js:10269:19)
        at C:\Projects\Issues\vue-unit-test-starter\node_modules\element-ui\lib\element-ui.common.js:10829:26
        at Array.<anonymous> (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:1835:12)
        at flushCallbacks (C:\Projects\Issues\vue-unit-test-starter\node_modules\vue\dist\vue.runtime.common.js:1756:14)
        at <anonymous>

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   1 passed, 1 total
Time:        4.575s
Ran all test suites.
Done in 5.87s.

Can you create a full minimal reproduction that I can run (either on code sandbox or GitHub). Please use the least amount of code possible to reproduce the issue. Then open a new issue with the reproduction.

@ChandruCR maybe you should change Vue.nextTick to localVue.nextTick

@BartekZienkiewicz
I get same warnings for localVue and Vue.
@eddyerburgh
These warnings are thrown for Jest Snapshots tests only.
Other tests succeed without any warning.
I will create a new issue for this.

submitted new issue (#795)

The reproduction issue is fixed with the latest version of element-ui—https://codesandbox.io/s/3rvrqrv2vq


Update to latest 0.3.8 of the CopyOnWrite library containing a bug fix

Plus SourceLink added to the CoW library.

For #546


Fix problem where a mixed polarity .raw file can result in an error a…

…bout the number of times not being equal. ("Times xxx and intensities xxx disagree in point count").

Here's a fix for a bug that I introduced a few months ago.
We assume that so long as no scheduling is going on, all MS1 chromatograms will have the same number of points in them.
However, if some of your MS1 scans are positive, and some are negative, then not all chromatograms will have the same number of points (at least, ever since my change back in February to ignore MS1 scans with the same polarity).
I think the easiest way to fix this is to have two different ChromCollector's for positive and negative scans.

Oops. Did not mean to close this pull request. I misunderstood what the "Close and comment" button did.

Looks like a simple enough change - no such polarity concerns in SIM?

SIM is in theory more targeted MS1. Let's wait for someone to show us a data set where they target MS1 to the same range with alternating polarities. Or will positive-negative switching DIA appear before that?


Deprecate old notification block APIs

As best I can tell, this was just missed in #3359 /cc @tgoyne
I think this is compatible with #3419 but not 100% sure just yet. /cc @bdash

I think, we should deprecate these APIs you're removing here first to completely remove them with 1.0 to give our users better assistance migrating through the versions and adopting the changes.

The problem with deprecating these APIs rather than removing them is that the Swift compiler is a real pain to work with when methods have ambiguous overloads, which is how I discovered this in the first place.
For example, the following won't compile if we keep both overloads (even if one is deprecated):
let token = results.addNotificationBlock { changes in }

For it to work, you need to be explicit with the type:
let token = results.addNotificationBlock { (changes: RealmCollectionChange) in }

The old method should certainly be marked as deprecated, but having to explicitly give the type of an argument to a block is not exactly an unusual experience in Swift.

The old method should certainly be marked as deprecated

If we do this, we need to do it consistently for the other notification block APIs that have been changed.

but having to explicitly give the type of an argument to a block is not exactly an unusual experience in Swift.

I'd like to think we've set ourselves to a higher bar of quality than the usual experiences, for example supporting Swift versions long after even Apple doesn't.

As the method has the same name just another type signature, the compiler will do likely do at least an acceptable job at hinting how that has to change. I'm all for completely removing it already now, because it's a breaking change in one way or another, if you haven't specified the types of the expected arguments before. So a :+1: from my side.

It's not a breaking change either way. The one argument version is ambiguous due to that the single arg could be a tuple (which is something that they're killing in Swift 3), but the two-arg version is unambiguously the old one.

If we do this, we need to do it consistently for the other notification block APIs that have been changed.

If there's a path to doing so that doesn't lead to long-term unpleasantness then I'd be all for it, but I don't have any ideas for how to do so other than using a different name, and that just gives us a breaking change later when we decide to rename it back to addNotificationBlock.

I'd like to think we've set ourselves to a higher bar of quality than the usual experiences, for example supporting Swift versions long after even Apple doesn't.

Yes, and I consider doing our best to avoid breaking existing code without a warning period to be an important part of making a library pleasant to use. Trying to update your deps and having compilation fail is unpleasant.

Ok, there's definitely a nice-ish way to keep the old Swift one deprecated. I'm doing that now.

Done.

👍

👍

:+1:


chore(deis-tests): sync command-line e2e options

Closes deis/workflow-e2e#97.
See deis/workflow-e2e#99.

I figured out the last remaining problem on this PR: the standard go test flags needed to be prefixed for the Ginkgo tests.test binary to understand them. So -v becomes -test.v and -timeout=60m becomes -test.timeout=60m. This was all clarified by doing make build and then asking tests.test for its command-line options.
I also removed /bin/sh -c since it was not necessary to run the tests binary.
This could use another reivew as I've made some changes after it got LGTMs.

Good find, @mboersma!


⚠ Bofrost.fr has degraded performance

In f271051, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1440 ms

Resolved: Bofrost.fr performance has improved in 2ff71a2 after 15 minutes.


gfx 7 card with ROCm tensorflow

Hi everyone,
i installed the recent ROCm Tensorflow release 1.11 and had hoped, that i can use my gfx7 card for Deep Learning in Tensorflow. Since it is stating in the ROCm documentation:
"The following list of GPUs are likely to work within ROCm, though full support is not guaranteed:
GFX7 GPUs
“Hawaii” chips, such as the AMD Radeon R9 390X and FirePro W9100"
After setting everything up and starting an Tensorflow example i get the following error:
"Ignoring visible gpu device with AMDGPU ISA gfx 701. The minimum required AMDGPU ISA is gfx803."
Did anyone get a gfx7 card to run with TensorFlow? It would be a pitty when i have to get a new graphics card just because of this software restrictions. Thanks in advance for your advice.

unfortunately gfx7 is not supported in this project.
Base ROCm stack and toolchain supports gfx7 but libraries to enable TensorFlow do not.


Update the database to 2.0

Can you update the SOCSDatabase to SPDX2.0 present in the https://github.com/socs-dev-env/Database-SPDX2.0 repo

Repo has been updated. Thanks for creating that Rohith. Hopefully we can get everything to 2.0 when it comes out and retire 1.2


[Kriging] [Tests] [Experimental] Functional tests of Least Squarest Approximation

Is your feature request related to a problem? Please describe.
The Kriging algorithm allows users to perform Least Squares Approximation if Numpy solver produces LinAlgError. This idea is experimental and not recommended - it would be useful to extensively track cases when the numpy.linalg.solve method fails, and then decide if there are edge cases when the LSA algorithm could be used instead.
Describe the solution you'd like
Design and write functional tests with different types of matrices that are unsolvable by the numpy.linalg.solve method (e.g.: zeros, ones etc). Check if those cases may occur in reality, and if so, make the LSA approximation option more granular.
Describe alternatives you've considered
n/a
Additional context
n/a

https://github.com/DataverseLabs/pyinterpolate/blob/dev/pyinterpolate/test/debug_sandbox/directional_ok.py


Add flag --ignore-cache to plugin install

Similar to #5445 in that I ran into some developer annoyance when developing a plugin, where changes weren't being shown because bundle plugin install decided that the cached version of the plugin took precedence over the updated remote copy. If there were a flag like --ignore-cache that would force a load of the remote version, I could've saved a couple "wait, did I not save the file?" moments.

Maybe bundle plugin update is more inline with what you're looking for?

@kerrizor How exactly are you doing this? I understand you are passing a file:/// URI to install without changing the plugin version, and it is not overwriting the existing installed plugin? Is that correct?

@segiddins I imagine plugin update checking a gem version and updating it if it is older. I don't think that this would solve his problem if my take on what is happening to him is right. I think a --reinstall option would be more likely to solve his problem. What do you think?

@segiddins @fotanus If this is still open I would like to take a crack at it. I can use #5672 as a starting point since it's a good example of how to add new commands. However, I'm not entirely sure how I would go about comparing the version of an installed plugin to a remote version.

I don't think anyone has started a PR, so go ahead!

@ajwann go ahead, ty!

Where does the bundle plugin install access the cache in the code? Is it in rubygems.rb?

@royalharsh as I recall, it is looking at the bundler config/dotfile that is left behind after you do an initial plugin install

@kerrizor could you provide a test case? I've inspected the code, and using your plugin, I can't reproduce the problem.
Specifically, the workflow I've tried is:
# run all from the bundler local repo
# make sure $HOME/.bundle/plugin has not the plugin

# copy locally
git clone git@github.com:kerrizor/bundler-dependency_graph /path/to/bundler-dependency_graph

# install the plugin
bin/bundle plugin install --git=/path/to/bundler-dependency_graph bundler-dependency_graph

# make it fail
bin/bundle plugin install --git=/path/to/bundler-dependency_graph bundler-dependency_graph

# kerry changes the command and commits
perl -i -pe 's/(command) "graph"/$1 "pizza"/' /path/to/bundler-dependency_graph/lib/bundler/dependency_graph/graph_builder.rb
git -C /path/to/bundler-dependency_graph commit -a -m test

# succeeds
bin/bundle plugin install --git=/path/to/bundler-dependency_graph bundler-dependency_graph

Preemptively, I've also though briefly thought about the case where workflow you specify ("did I not save the file") actually means saving without committing (same sequence as above, without the git commit); if this is the case, then this can't work in any case. The git operation, downstream, is a clone:
git_proxy.copy_to(install_path, submodules)
# [...]
git_retry %(clone --no-checkout --quiet "#{path}" "#{destination}")

so if the changes are not committed, from the git perspective, there are no changes.
Regardless of any of the above, there is actually a very neat option (pun not intended :joy:) - downstream there is an option called force (lib/bundler/source/git.rb:175) which could be exposed to the user; if so, it would yield the behavior you've described.


[BUG] Unable to auto train paligemma

Prerequisites

[X] I have read the documentation.
[X] I have checked other issues for similar problems.

Backend
Local
Interface Used
UI
CLI Command
No response
UI Screenshots & Parameters

Error Logs
INFO | 2024-07-27 21:51:50 | autotrain.app.utils:kill_process_by_pid:52 - Sent SIGTERM to process with PID 713
INFO | 2024-07-27 21:51:50 | autotrain.app.utils:get_running_jobs:26 - Killing PID: 713
0%| | 0/3 [00:00<?, ?it/s]
ERROR | 2024-07-27 21:51:49 | autotrain.trainers.common:wrapper:121 - 'autotrain_prompt'
KeyError: 'autotrain_prompt'
prompts = ["answer " + example[config.prompt_text_column] for example in examples]
File "/app/env/lib/python3.10/site-packages/autotrain/trainers/vlm/train_vlm_generic.py", line 13, in
prompts = ["answer " + example[config.prompt_text_column] for example in examples]
File "/app/env/lib/python3.10/site-packages/autotrain/trainers/vlm/train_vlm_generic.py", line 13, in collate_fn
return self.collate_fn(data)
File "/app/env/lib/python3.10/site-packages/torch/utils/data/_utils/fetch.py", line 54, in fetch
data = self._dataset_fetcher.fetch(index) # may raise StopIteration
File "/app/env/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 675, in _next_data
data = self._next_data()
File "/app/env/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 631, in next
current_batch = next(dataloader_iter)
File "/app/env/lib/python3.10/site-packages/accelerate/data_loader.py", line 454, in iter
for step, inputs in enumerate(epoch_iterator):
File "/app/env/lib/python3.10/site-packages/transformers/trainer.py", line 2236, in _inner_training_loop
return inner_training_loop(
File "/app/env/lib/python3.10/site-packages/transformers/trainer.py", line 1938, in train
trainer.train()
File "/app/env/lib/python3.10/site-packages/autotrain/trainers/vlm/train_vlm_generic.py", line 97, in train
train_generic(config)
File "/app/env/lib/python3.10/site-packages/autotrain/trainers/vlm/main.py", line 27, in train
return func(*args, **kwargs)
File "/app/env/lib/python3.10/site-packages/autotrain/trainers/common.py", line 117, in wrapper
0%| | 0/3 [00:00<?, ?it/s]ERROR | 2024-07-27 21:51:49 | autotrain.trainers.common:wrapper:120 - train has failed due to an exception: Traceback (most recent call last):
INFO | 2024-07-27 21:51:48 | autotrain.trainers.common:on_train_begin:230 - Starting to train...
warnings.warn(
/app/env/lib/python3.10/site-packages/transformers/models/paligemma/configuration_paligemma.py:137: FutureWarning: The vocab_size attribute is deprecated and will be removed in v4.44, Please use text_config.vocab_size instead.
 [WARNING]  using untested triton version (2.3.0), only 1.0.0 is known to be compatible
 [WARNING]  sparse_attn requires a torch version >= 1.5 and < 2.0 but detected 2.3
 [WARNING]  NVIDIA Inference is only supported on Ampere and newer architectures
 [WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
[2024-07-27 21:51:48,616] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
INFO | 2024-07-27 21:51:48 | autotrain.trainers.vlm.train_vlm_generic:train:80 - creating trainer
INFO | 2024-07-27 21:51:47 | autotrain.trainers.vlm.utils:get_model:232 - preparing peft model...
INFO | 2024-07-27 21:51:47 | autotrain.trainers.vlm.utils:get_model:229 - model dtype: torch.float16
Additional Information
Tried to train with a test dataset using the UI.
Followed the exact steps mentioned here: https://huggingface.co/blog/abhishek/paligemma-finetuning-autotrain
But ended up getting the error.
The zip file that was used for testing the finetuning  :
train.zip

it seems like your column mappings are incorrect? can you share first few lines from metadata.jsonl?


Feature/libitd 2311

So somehow, the Content-MD5 header is already being added to the request to the file upload process. I was able to confirm this because initially I had written a callback function to add a Content-MD5 header during runtime for each request to AWS, but after some debugging with it erroring, I found that I was adding a second Content-MD5 header. So I removed the verification check in the deposit process, because that seems to be redundant if Content-MD5 is already being added. Here's an example of the header before and after I had added another Content-MD5 header, mine wasn't base 64 encoded so which I hadn't realized needed to be at the time.
x-amz-storage-class: DEEP_ARCHIVE
x-amz-meta-md5: d41d8cd98f00b204e9800998ecf8427e
x-amz-meta-bytes: 0
User-Agent: Boto3/1.26.100 Python/3.11.0 Darwin/22.4.0 Botocore/1.29.100 Resource
Content-MD5: 1B2M2Y8AsgTpgAmY7PhCfg==
Expect: 100-continue
x-amz-storage-class: DEEP_ARCHIVE
x-amz-meta-md5: d41d8cd98f00b204e9800998ecf8427e
x-amz-meta-bytes: 0
User-Agent: Boto3/1.26.100 Python/3.11.0 Darwin/22.4.0 Botocore/1.29.100 Resource
Content-MD5: 1B2M2Y8AsgTpgAmY7PhCfg==
Expect: 100-continue
Content-MD5: d41d8cd98f00b204e9800998ecf8427e

I probably should make the isort thing another issue like I did with preserve


Add Speaker Images

Fixes #571
@mananwason @mariobehling  Please review.

@the-dagger This is already fixed in #570


MRG, BUG: Fix complex vol morph

Closes #8127

thanks @larsoner for the fix and @ualsbombe for the bug report !

No problem, keep up the good work!


Parallel use of Protege

I have tried to copy the data down and use Protege to run the queries. Sometimes they work other times they don't. Is this to be expected or am I doing something wrong

Has this issue been dealt with by the resolution of issues 46 and 45?


Add more sorting options for overdue/lent devices

Right now it's not possible to sort devices in the overdue/lending list for owner or duedate.

Yes, that is super annoying, you are right.
The devices/ view together with all tables will get fully functional datatables once I finished the bootstrap4 branch.

Btw @phillipthelen, do you remember why you implemented paged tables server side instead of using datatables? :)


Unable to start openldap on CentOS 7.5, cannot access '/container/service/slapd/install.sh': No such file or directory.

uname -a
Linux node2 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)

docker version
Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:25:41 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea
  Built:            Wed Nov 13 07:24:18 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

start command
docker run -p 389:389 -p 636:636 --name my-openldap-container --detach osixia/openldap:1.5.0

docker logs my-openldap-containe
*** CONTAINER_LOG_LEVEL = 3 (info)
*** Search service in CONTAINER_SERVICE_DIR = /container/service :
*** link /container/service/:ssl-tools/startup.sh to /container/run/startup/:ssl-tools
*** link /container/service/slapd/startup.sh to /container/run/startup/slapd
*** link /container/service/slapd/process.sh to /container/run/process/slapd/run
*** Set environment for startup files
*** Environment files will be proccessed in this order :
Caution: previously defined variables will not be overriden.
/container/environment/99-default/default.startup.yaml
/container/environment/99-default/default.yaml

To see how this files are processed and environment variables values,
run this container with '--loglevel debug'
*** Running /container/run/startup/:ssl-tools...
*** Running /container/run/startup/slapd...
openldap user and group adjustments
get current openldap uid/gid info inside container
-------------------------------------
openldap GID/UID
-------------------------------------
User uid: 911
User gid: 911
uid/gid changed: false
-------------------------------------
updating file uid/gid ownership
chown: cannot access '/container/service/slapd/install.sh': No such file or directory
*** /container/run/startup/slapd failed with status 1

*** Killing all processes...

But on my CentOS 8.3 VM, it works fine.

Mark


Fix CMEK typo in project module. Part 2 :)

Yet another typo was found

Checklist

I applicable, I acknowledge that I have:

[x] Read the contributing guide
[x] Ran terraform fmt on all modified files
[x] Regenerated the relevant README.md files using tools/tfdoc.py
[x] Made sure all relevant tests pass

@ludoo thank you as well for the new CMEK part in the project module. You saved me a lot of time 😁


Update Composer dependencies (2021-12-02-00-03)

Visual regression test passed!
View the visual regression test report


Amplify App - entire app - unwanted disappearance, and not deleting completely when actually deleting.

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
dyyvoq47s0kba
AWS Region
us-west-1
Amplify Hosting feature
Deployments, Not Applicable
Describe the bug

About 10 days ago we had an entire Amplify app disappear from the "All Apps" Section in Amplify after leaving the Amplify console up for an extended period of time, then logging back in. We shrugged it off thinking it was our mistake. Linked to the "original" GitHub account. We then setup an Amplify App, which worked.
A few days ago, we created a new Amplify app and deleted the old one and linked to a different temporary GitHub account. No issues at all.
Earlier today, we decided get rid of that working Amplify App as we needed to connect back to the "original" GitHub account. After deleting the app, and some navigating around, the Amplify App from a few days ago reappeared in our Amplify Apps. Keep in mind we deleted this one already. We redeleted it, and created a new Amplify app connected to the "original" GitHub Account - the original intention of today. We received the error "CNAMEAlredyExistsException". Waited an hour, not working. It says in the supporting docs to then wait 6 hours. We did so; the issue still persisted.
Just now, after 6 hours of waiting for any previous source to be unlinked and linking domains was still not working, we tried deleting the app that we created earlier today and create a new, fresh one. Did so, opened a new window and moved that window to my other monitor, and after refreshing the Amplify Apps, the App from a few days ago appeared again and the Amplify App I just created - it was in the process of running the build - disappeared. It seems like deleting an app does not work properly, and also leaving sessions open for too long or creating 2 windows for the Amplify App is prone to complete deletion of any previous progress which is very frustrating.

Expected behavior
Amplify Apps should be completely deleted when you delete.
Previously deleted Amplify Apps should not reappear.
Amplify Apps should not delete themselves after extended sessions in the console or after creating a new window and moving to another screen.
Reproduction steps
I'm not sure if this is a guarantee, but try

Create an amplify app like normal. Link to a github repo.
Wait until it auto logs you out due to timeout. See if the app is deleted.
If it's not, delete the app.
Create a new app linked to the same Gihub repo.
Duplicate the window and move to another screen.
On the duplicated screen, refresh the page and login out and back in. Do this a few times.
Go back to the original window and refresh. See if the app you just deleted reappears.

Build Settings
No response
Log output

# Put your logs below this line

Additional information
No response

Hi @Logiq-repos 👋🏽 we have a known bug where sometimes deleting applications directly from the console may be unsuccessful. In these cases, the workaround is to delete the backend environment via the AWS CLI and then delete the frontend application in the console. To delete the backend environment please run this command:
aws amplify delete-backend-environment --app-id <APP_ID> --environment-name <ENV_NAME>
Doc reference: https://docs.aws.amazon.com/cli/latest/reference/amplify/delete-backend-environment.html
To confirm that your app has been successfully deleted, please run the aws amplify list-apps command to make sure the app is no longer listed: https://docs.aws.amazon.com/cli/latest/reference/amplify/list-apps.html.
Please let us know if the above steps help you confirm deletion of the appropriate applications. The application periodically disappearing from the console needs to be further investigated so I will try to reproduce this behavior with the steps you provided.

Just to clarify, the CNAME error we are getting is
The following CloudFront distributions or Amplify Apps are already using one or more of your domains: [Distribution: *******YPBE0FU in AWS Account: ******359175]
We do not have an account with the last digits 359175, and there is no distribution in our account ending with YPBE0FU

I am having a similar issue deleting apps--we did "amplify init" and got an error back stating that we had exceeded our 25 app limit, but we only have 3 apps right how.  We have added/removed some recently, however.  But right now I can't successfully get through the process of adding new ones.

Just to clarify, the CNAME error we are getting is
The following CloudFront distributions or Amplify Apps are already using one or more of your domains: [Distribution: *******YPBE0FU in AWS Account: ******359175]
We do not have an account with the last digits 359175, and there is no distribution in our account ending with YPBE0FU

I'm also facing similar issue where my website root domain was previously hosted on vercel.app and now after deleting the hosting from vercel, I changed my dns provider as route 53 and tried to add custom domain for my amplify app.
I get One or more of the CNAMEs you provided are already associated with a different resource. (Service: AmazonCloudFront; Status Code: 409; Error Code: CNAMEAlreadyExists; Request ID: 0ac55b2f-4821-4ad6-830f-3f6f45840b74; Proxy: null)
After checking the distribution id I found it's still with some other account as below. Although I'm not sure if vercel.app is using this account or not.
"DistributionId": "*******CIDM0F2",
"AccountId": "******164913"

Is there any update on this? We created another app about 12 hours ago, and we just signed to find the whole amplify app deleted from the amplify console. Tried recreating the app, and got the CNAME errors above. The websites are still working which is odd.

facing same issue
amplify app not showing on the amplify console
appId d1x20x5yrvmc5n

Something similar is happening to me.
I deleted the Amplify app. When I try to add a CNAME to CloudFront, I receive the following error:
One or more of the CNAMEs you provided are already associated with a different resource.
I ran the command aws cloudfront list-conflicting-aliases, and the CNAME is attached to an account that is not mine.
{
"ConflictingAliasesList": {
"MaxItems": 100,
"Quantity": 1,
"Items": [
{
"Alias": "www.****.com.br",
"DistributionId": "*******WOOP2BA",
"AccountId": "******171576"
}
]
}
}
Perhaps Amplify is using an internal account to create the resources and not properly deleting it, now the ID does not exist anymore. I can't do anything to fix it.
This is really concerning.


[Image OP] Normalize

@piiswrong I add gradients here but I'm not sure whether we need it.
https://github.com/apache/incubator-mxnet/issues/8556

we don't need gradient for now


Update license to include LLVM license for modified/redistributed code [phab:D1917]

Created by shahms at 2017-08-29 21:54:31:
Update license to include LLVM license for modified/redistributed code

fromberger accepted this revision at 2017-08-29 21:58:53

shahms closed via commit 57223c77bb1fddef14e547f8098ef482c428ea54 at 2017-08-29 22:02:55


"Sign up" page breaks several tabs

If i go to https://www.codewars.com/join, page breaks into "Aw Snap" error message.
It doesn't break immediately, you can actually see website loading for half a second and only then it breaks.
It also breaks several other tabs, not related any way to Codewars.
You can see that on the screenshots 1-2 below.

If i reload broken tabs and try to click "SignUp" again, Codewars breaks the same tabs again.
If i change the websites on these tabs, it will randomly break some of them.
In the screenshot below you can see that it broke my GitHub issue submit page, if though it didn't on the screenshots above

Browser: Google Chrome 62.0.3202.94
Installed extensions: uBlock, Imagus.

Thanks for reporting with details.
Are you on Windows 7 or 8? Some Windows users are having issues, for example #1157

@kazk Windows 8. Seems like issue is the same as #1157

@shakhbulatgaz Thanks for confirming.
Do you think you can help us by enabling logging (--enable-logging --v=1) and posting chrome_debug.log? How to determine what is causing Chrome to show the “Aw, Snap” dialogue.

@kazk sure, here you go
chrome_debug.log
I tried to open just codewars.com ,  since it throws the same error.

@kazk another observation — page works fine on IE 10.0.1
The console there says "Raven is not defined"

@shakhbulatgaz Thanks! I'll look into it and see if I can find anything. I'll also remove the file just in case if it contains any personal information.

@shakhbulatgaz Unfortunately, I couldn't find anything obvious.
Does codewars.com crash without extensions? Extension mjdepdfccjgcndkmemponafgioodelna is writing to console few times.
Other lines that might be related, but I don't have the knowledge to understand are:
[1588:2248:1212/000800.824:VERBOSE1:policy_loader_win.cc(377)] Reading policy from the registry is disabled.

[1588:1736:1212/000800.918:VERBOSE1:dhcp_proxy_script_adapter_fetcher_win.cc(263)] Error fetching PAC URL from DHCP: 2

[4524:3988:1212/000801.012:ERROR:mf_helpers.cc(14)] Error in dxva_video_decode_accelerator_win.cc on line 485

Adding --no-sandbox flag might add more details.

To enable logging from the render processes on Windows you also need the --no-sandbox command line flag.
https://www.chromium.org/for-testers/enable-logging

I'm not sure if I can find anything from it because I'm not familiar with browser internals, but I can try. If you don't mind, can you disable extensions and launch with --enable-logging --v=1 --no-sandbox? Make sure to remove those flags after collecting logs. If not, don't worry, thanks for all the info.

I want to know why only Windows 7 and 8 crashes :/ Windows 10 seems fine.

@kazk later, once i get home.
Interesting - I tried to open codewars.com from my workplace and it works fine, even though my browser here has even more extenstions.
Problem obviously is in local machines.

@kazk here
chrome_debug.log

@shakhbulatgaz Thanks, I'll take a look.

@shakhbulatgaz

I tried to open codewars.com from my workplace (Windows 7) and it works fine

Is your chrome 32 bit version? And maybe 64 bit at your work?
Does it work in Incognito window?

Some other observations:

chrome-extension://pkedcjkdefgpdelpbcmbmeomcjbeemfm is loaded. This seems to be the builtin Chrome Cast

@kazk no and no.
Maybe there is some sort of GPU memory problem taking place?
It could probably explain this:
[4524:3988:1212/000801.012:ERROR:mf_helpers.cc(14)] Error in dxva_video_decode_accelerator_win.cc on line 485
At work we use distributed network, so maybe that's why it doesn't crash here.
Also the tabs that get crashed alongside codewars are heavily loaded with graphics, (it doesnt' crash text-only pages) so...

@shakhbulatgaz sorry, I don't think I can help at this point. Thanks for providing us the logs. I'm going to close this as a duplicate of #1157.


[Bug] 0.51.0-rc2 only: Could not create web worker

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[X] Not reproducible in the monaco editor playground

Monaco Editor Playground Link
No response
Monaco Editor Playground Code
No response
Reproduction Steps
If I update from 0.50.0 to 0.51.0-rc2 I get these errors:
simpleWorker.ts:36
 Could not create web worker(s). Falling back to loading web worker code in main thread, which might cause UI freezes. Please see https://github.com/microsoft/monaco-editor#faq
simpleWorker.ts:38
 Uncaught SyntaxError: Failed to execute 'importScripts' on 'WorkerGlobalScope': The URL './node_modules/monaco-editor/dev/vs/base/worker/workerMain.js#css' is invalid.
simpleWorker.ts:38
 Uncaught SyntaxError: Failed to execute 'importScripts' on 'WorkerGlobalScope': The URL './node_modules/monaco-editor/dev/vs/base/worker/workerMain.js#editorWorkerService' is invalid.
...

Downgrade and it works again.
Using requirejs as loader - everything has worked fine for years.
I know its RC - just a heads up.
Actual (Problematic) Behavior
No response
Expected Behavior
No response
Additional Context
No response

now also in 0.51.0

This is also happening on the monaco editor official website:

try like this
import EditorWorker from  worker-loader?inline=no-fallback!./node_modules/monaco-editor/esm/vs/editor/editor.worker

We're seeing this in the released version too (0.52.0), but only on diffEditors

in v0.52 this has been fixed if you use absolute paths: requirejs.config({ paths: { "vs": window.location.origin + "/scripts/modelyn-editor/vs" .. (I am using requirejs) and @mattgodbolt I also tested the diff and that works fine.

@AndersMad we're using webpack; any advice on that welcomed.


Client library changes for Validate Migration

Client library changes for Validate Migration

Hi @priydes, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;


Emit structured (JSON) logs

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2772
Originally created by @deanmorin on 2021-05-28 21:21:07

All of my meltano logs end up in datadog. If the logs were formatted as json, it would automatically break up each log message into its various components. This is possible to do with a custom regex as well, but not quite as convenient.

View 18 previous comments from the original issue on GitLab


Provide proper PDF rendering for the presentation

The PDF rendering needs to be configured properly, so that we can get readable PDF slides for the trainees.

Done along with the migration to asciidoctor-revealjs, which makes the PDf export easy.