Deploy failing on .<IP_ADDRESS> Telescope app on Digital Ocean

I don't want to keep hijacking other threads but I can't get this thing working.
mup setup seems to go fine, but mup deploy fails on the last step every time.
Does anyone see an issue in this error?
Started TaskList: Deploy app 'musichunt' (linux)
[<IP_ADDRESS>] - Uploading bundle
[<IP_ADDRESS>] ✔ Uploading bundle: SUCCESS
[<IP_ADDRESS>] - Setting up Environment Variables
[<IP_ADDRESS>] ✔ Setting up Environment Variables: SUCCESS
[<IP_ADDRESS>] - Invoking deployment process
[<IP_ADDRESS>] ✘ Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
    de_root_dir=/root/.node-gyp/0.10.31',
    gyp info spawn args   '-Dmodule_root_dir=/opt/musichunt/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
    gyp info spawn args   '--depth=.',
    gyp info spawn args   '--no-parallel',
    gyp info spawn args   '--generator-output',
    gyp info spawn args   'build',
    gyp info spawn args   '-Goutput_dir=.' ]
    gyp info spawn make
    gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
    gyp info ok
    npm WARN package.json<EMAIL_ADDRESS>No description
    npm WARN package.json<EMAIL_ADDRESS>No repository field.
    npm WARN package.json<EMAIL_ADDRESS>No README data
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 80: Connection refused
    Latest deployment failed! Reverted back to the previous version.
    -----------------------------------STDOUT-----------------------------------
    ease/obj.target/bcrypt_lib/src/bcrypt.o
      CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
      SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
      SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node: Finished
      COPY Release/bcrypt_lib.node
    make: Leaving directory `/opt/musichunt/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build'

    ><EMAIL_ADDRESS>install /opt/musichunt/tmp/bundle/programs/server/node_modules/fibers
    > node ./build.js

    `linux-x64-v8-3.14` exists; testing
    Binary is fine; exiting
<EMAIL_ADDRESS>node_modules/underscore

<EMAIL_ADDRESS>node_modules/semver

<EMAIL_ADDRESS>node_modules/source-map-support
    └──<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/fibers
    musichunt stop/waiting
    musichunt start/running, process 12589
    Waiting for MongoDB to initialize. (5 minutes)
    connected
    Waiting for 15 seconds while app is booting up
    Checking is app booted or not?
    musichunt stop/waiting
    musichunt start/running, process 12693
    ----------------------------------------------------------------------------
Completed TaskList: Deploy app 'musichunt' (linux)

Logs:
dshan:.deploy derekshanahan$ mup logs -n 400

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------

[<IP_ADDRESS>] Warning: Permanently added '<IP_ADDRESS>' (RSA) to the list of known hosts.
[<IP_ADDRESS>] MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonymous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.js:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #2
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:28:48 GMT-0400 (EDT)
!!! Found incomplete migration "moveVotesFromProfile", removing and running again.
//----------------------------------------------------------------------//
//------------//    Starting moveVotesFromProfile Migration    //-----------//
//----------------------------------------------------------------------//
User: gGW35ozHsGAnGmXJ9
---------------------
User: cGJ2j6wJaZbzoZhR2
---------------------
User: tCaG5YDzQNgJ5YJqC

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonymous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.j[<IP_ADDRESS>] s:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #3
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:28:51 GMT-0400 (EDT)
!!! Found incomplete migration "moveVotesFromProfile", removing and running again.
//----------------------------------------------------------------------//
//------------//    Starting moveVotesFromProfile Migration    //-----------//
//----------------------------------------------------------------------//
User: gGW35ozHsGAnGmXJ9
---------------------
User: cGJ2j6wJaZbzoZhR2
---------------------
User: tCaG5YDzQNgJ5YJqC

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonymous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.js:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #4
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled[<IP_ADDRESS>]  "Schedule newsletter" next run @Tue Sep 09 2014 22:28:53 GMT-0400 (EDT)
!!! Found incomplete migration "moveVotesFromProfile", removing and running again.
//----------------------------------------------------------------------//
//------------//    Starting moveVotesFromProfile Migration    //-----------//
//----------------------------------------------------------------------//
User: gGW35ozHsGAnGmXJ9
---------------------
User: cGJ2j6wJaZbzoZhR2
---------------------
User: tCaG5YDzQNgJ5YJqC

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonymous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.js:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #5

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
Error: ENOENT, open '/opt/musichunt/app/programs/server/assets/packages/oauth/end_of_login_response.html'
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at getAsset (/opt/musichunt/app/programs/server/boot.js:139:20)
    at Object.Assets.getText (/opt/musichunt/app/programs/server/boot.js:144:16)
    at OAuth._pendingCredentials.Meteor.Collection._preventAutopublish (packages/oauth/oauth_server.js:190)
    at /opt/musichunt/app/programs/server/packages/oauth.js:343:4
    at /opt/musichunt/app/programs/server/packages/oauth.js:536:3
    at /opt/musichunt/app/programs/server/boot.js:161:10
    at Array.forEach (native)
    at Function._.each._.forEach (/opt/musichunt/app/programs/server/node_modules/underscore/underscore.js:79:11)
    at /opt/musichunt/app/programs/server/boot.js:82:5
    - - - - -
error: Forever detected script exited with code: 8
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:28:57 GMT-0400 (EDT)
 >> stepping down to gid: meteoruser
 >> stepping d[<IP_ADDRESS>] own to uid: meteoruser
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:39:21 GMT-0400 (EDT)
!!! Found incomplete migration "moveVotesFromProfile", removing and running again.
//----------------------------------------------------------------------//
//------------//    Starting moveVotesFromProfile Migration    //-----------//
//----------------------------------------------------------------------//
User: gGW35ozHsGAnGmXJ9
---------------------
User: cGJ2j6wJaZbzoZhR2
---------------------
User: tCaG5YDzQNgJ5YJqC

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonymous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.js:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #1
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:39:22 GMT-0400 (EDT)
!!! Found incomplete migration "moveVotesFromProfile", removing and running again.
//----------------------------------------------------------------------//
//------------//    Starting moveVotesFromProfile Migration    //-----------//
//----------------------------------------------------------------------//
User: gGW35ozHsGAnGmXJ9
---------------------
User: cGJ2j6wJaZbzoZhR2
---------------------
User: tCaG5YDzQNgJ5YJqC

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonym[<IP_ADDRESS>] ous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.js:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #2
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:39:25 GMT-0400 (EDT)
!!! Found incomplete migration "moveVotesFromProfile", removing and running again.
//----------------------------------------------------------------------//
//------------//    Starting moveVotesFromProfile Migration    //-----------//
//----------------------------------------------------------------------//
User: gGW35ozHsGAnGmXJ9
---------------------
User: cGJ2j6wJaZbzoZhR2
---------------------
User: tCaG5YDzQNgJ5YJqC

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonymous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.js:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server[<IP_ADDRESS>] /npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #3
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:39:28 GMT-0400 (EDT)
!!! Found incomplete migration "moveVotesFromProfile", removing and running again.
//----------------------------------------------------------------------//
//------------//    Starting moveVotesFromProfile Migration    //-----------//
//----------------------------------------------------------------------//
User: gGW35ozHsGAnGmXJ9
---------------------
User: cGJ2j6wJaZbzoZhR2
---------------------
User: tCaG5YDzQNgJ5YJqC

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonymous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.js:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #4
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:39:31 GMT-0400 (EDT)
!!! Found incomplete migration "moveVotesFromProfile", removing and running again.
//----------------------------------------------------------------------//
//------------//    Starting moveVotesFromProfile Migration    //-----------//
//----------------------------------------------------------------------//
User: gGW35ozHsGAnGmXJ9
[<IP_ADDRESS>] ---------------------
User: cGJ2j6wJaZbzoZhR2
---------------------
User: tCaG5YDzQNgJ5YJqC

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonymous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.js:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #5
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:39:34 GMT-0400 (EDT)
!!! Found incomplete migration "moveVotesFromProfile", removing and running again.
//----------------------------------------------------------------------//
//------------//    Starting moveVotesFromProfile Migration    //-----------//
//----------------------------------------------------------------------//
User: gGW35ozHsGAnGmXJ9
---------------------
User: cGJ2j6wJaZbzoZhR2
---------------------
User: tCaG5YDzQNgJ5YJqC

/opt/musichunt/app/programs/server/node_modules/fibers/future.js:206
                        throw(ex);
                              ^
MongoError: cannot create details for $rename mod
    at Object.Future.wait (/opt/musichunt/app/programs/server/node_modules/fibers/future.js:326:15)
    at null.<anonymous> (packages/meteor/helpers.js:111)
    at MongoConnection.(anonymous function) [as update] (packages/mongo-livedata/mongo_driver.js:607)
    at Object.fields (packages/matb33:collection-hooks/update.js:71)
    at Object.collection.(anonymous function) [as update] (packages/matb33:collection-hooks/collection-hooks.js:105)
    at Meteor.Collection.(anonymous function) (packages/mongo-livedata/collection.js:486)
    at Meteor.Collection.(anonymous function) [as update] (packages/aldeed:collection2/collection2.js:294)
    at app/server/migrations.js:334:20
    at _.extend.forEach (packages/mongo-livedata/mongo_driver.js:894)
    at Cursor.(anonymous function) [as forEach] (packages/mongo-livedata/mongo_driver.js:741)
    - - - - -
    at Object.toError (/opt/musichunt/[<IP_ADDRESS>] app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/utils.js:110:11)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/collection/core.js:542:27
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1129:7
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/db.js:1843:9
    at Server.Base._callHandler (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/base.js:445:41)
    at /opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:468:18
    at MongoReply.parseBody (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/server.js:426:20)
    at emit (events.js:95:17)
    at null.<anonymous> (/opt/musichunt/app/programs/server/npm/mongo-livedata/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:201:13)
error: Forever detected script exited with code: 8
error: Script restart attempt #6
[MailChimp] Error: MailChimp Options have not been set in your settings.json file.
SyncedCron: scheduled "Schedule newsletter" next run @Tue Sep 09 2014 22:39:36 GMT-0400 (EDT)
 >> stepping down to gid: meteoruser
 >> stepping down to uid: meteoruser

Hi Gentlemen, I am attempting to deploy Meteor/Telescope (DigitalOcean + Compose.io) but no success. I received the following error message a few seconds ago. Would you have any recommendations? Eric

Pretty sure Meteor requires Node 0.10.3x right now.  Looks like you're using the current stable (0.12.0).  Try changing your mup config and starting over with a fresh server.

How do I revert to Node 0.10.3x?

https://github.com/arunoda/meteor-up#example-file

I think I understand now. It looks like I installed the latest stable build of Node on my DigitalOcean droplet before deployment. I am adding a screenshot. If this is the problem, how do I revert Ubuntu's Node version to 0.10.3x?

Unless you're using that server for something else, the fastest solution is to dump it and fire up a new fresh server and follow the mup instructions from step 1.  Mup will set everything up for you.

I am not using it for anything else but I thought that it might be easiest to run sudo apt-get auto remove --purge node && sudo apt-get auto remove --purge npm. If it doesn't work, I'll fire up a fresh server.

Whatever you prefer, of course.  I only recommended it because a fresh setup guarantees your version conflicts go away.  Assuming you have a properly configured mup.json, it only takes about 60 seconds to be up and running after the new server is done booting.  Quite possibly faster than reconfiguring the existing server.

I just destroyed the existing Droplet. I'll try the latest deployment right
now.
2015-02-26 13:06 GMT-08:00 Jeremy Shimko<EMAIL_ADDRESS>
Whatever you prefer, of course. I only recommended it because a fresh
setup guarantees your version conflicts go away. Assuming you have a
properly configured mup.json, it only takes about 60 seconds to be up and
running after the new server is done booting. Quite possibly faster than
reconfiguring the existing server.
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/381#issuecomment-76273313
.

You have to factor the SSH-key exchange into the milieu...

I use the same key for every server I have in Digital Ocean, so I guess I haven't really run into that.  It just gets taken care of when a new server is booting for the first time.

Do you have email or Jitsi?
2015-02-26 13:23 GMT-08:00 Jeremy Shimko<EMAIL_ADDRESS>
I use the same key for every server I have in Digital Ocean, so I guess I
haven't really run into that. It just gets taken care of when a new server
is booting for the first time.
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/381#issuecomment-76276428
.

I refreshed the server. I received the following errors:
*[<IP_ADDRESS>] *✘ Invoking deployment process: FAILED

-----------------------------------STDERR-----------------------------------*

ibrary=shared_library',*

gyp info spawn args   '-Dvisibility=default',*

gyp info spawn args   '-Dnode_root_dir=/root/.node-gyp/0.10.33',*

gyp info spawn args
'-Dmodule_root_dir=/opt/AnotherUniverse/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',*

gyp info spawn args   '--depth=.',*

gyp info spawn args   '--no-parallel',*

gyp info spawn args   '--generator-output',*

gyp info spawn args   'build',*

gyp info spawn args   '-Goutput_dir=.' ]*

gyp info spawn make*

gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]*

gyp info ok *

npm WARN package.json<EMAIL_ADDRESS>No description*

npm WARN package.json<EMAIL_ADDRESS>No repository field.*

npm WARN package.json<EMAIL_ADDRESS>No README data*

/usr/lib/node_modules/wait-for-mongo/bin/wait-for-mongo:14*

throw err;*

      ^*

Error: TIMEOUTED_WAIT_FOR_MONGO*

at null._onTimeout

(/usr/lib/node_modules/wait-for-mongo/lib/waitForMongo.js:20:14)*

at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)*

-----------------------------------STDOUT-----------------------------------*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

wait-for-mongo: auth fails*

----------------------------------------------------------------------------*
Completed TaskList: Deploy app 'AnotherUniverse' (linux)
2015-02-26 13:28 GMT-08:00 Eric Giannini<EMAIL_ADDRESS>
Do you have email or Jitsi?
2015-02-26 13:23 GMT-08:00 Jeremy Shimko<EMAIL_ADDRESS>
I use the same key for every server I have in Digital Ocean, so I guess I
haven't really run into that. It just gets taken care of when a new server
is booting for the first time.
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/381#issuecomment-76276428
.

I fired up a new instance. Right now I am receiving the following errors.

Your Mongo credentials or URL are likely wrong.

I am updating them right now.
2015-02-26 13:47 GMT-08:00 Jeremy Shimko<EMAIL_ADDRESS>
Your Mongo credentials or URL are likely wrong.
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/381#issuecomment-76281150
.

What about these:
-npm WARN package.json<EMAIL_ADDRESS>No description
-npm WARN package.json<EMAIL_ADDRESS>No repository field.
-npm WARN package.json<EMAIL_ADDRESS>No README data
2015-02-26 13:53 GMT-08:00 Eric Giannini<EMAIL_ADDRESS>
I am updating them right now.
2015-02-26 13:47 GMT-08:00 Jeremy Shimko<EMAIL_ADDRESS>
Your Mongo credentials or URL are likely wrong.
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/381#issuecomment-76281150
.

SUCCESS!!!
2015-02-26 13:56 GMT-08:00 Eric Giannini<EMAIL_ADDRESS>
What about these:
-npm WARN package.json<EMAIL_ADDRESS>No description
-npm WARN package.json<EMAIL_ADDRESS>No repository field.
-npm WARN package.json<EMAIL_ADDRESS>No README data
2015-02-26 13:53 GMT-08:00 Eric Giannini<EMAIL_ADDRESS>:
I am updating them right now.

2015-02-26 13:47 GMT-08:00 Jeremy Shimko<EMAIL_ADDRESS>
Your Mongo credentials or URL are likely wrong.
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/381#issuecomment-76281150
.

Shout out to jshimko! Thanks!

:+1:


Broken pipe on Manjaro with Cinnamon

Hi, I get a broken pipe at start on Manjaro / Cinnamon. Is there a way to get more logs to debug that? I tried both your compiled binary and to compile myself and both CLI and tray.

Hi, I think it is very likely that you are using the older version of HyperX Cloud 2. Apparently, that version does not work very well with my app. Could you please run lsusb and send me the entry of your headset?

Hi, here is the output with the headset on and plugged in:
-> % lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 1bcf:0215 Sunplus Innovation Technology Inc. Aukey-PC-LM1E Camera Bus 001 Device 004: ID 1e71:3008 NZXT NZXT KrakenZ Device Bus 001 Device 005: ID 1462:7c56 Micro Star International MYSTIC LIGHT  Bus 001 Device 006: ID 0951:1718 Kingston Technology HyperX Cloud II Wireless Bus 001 Device 007: ID 0951:1719 Kingston Technology HyperX Cloud II Wireless Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 003 Device 003: ID 045e:02e6 Microsoft Corp. Xbox Wireless Adapter for Windows Bus 003 Device 004: ID 2357:0604 TP-Link TP-Link UB500 Adapter Bus 003 Device 005: ID 046d:c547 Logitech, Inc. USB Receiver Bus 003 Device 006: ID 046d:c547 Logitech, Inc. USB Receiver Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002: ID 05e3:0612 Genesys Logic, Inc. Hub
I bought it in March 2021, if it can help you.

Ah, yes, that is the older version of the Headset Sady. The app has some issues with that version.https://github.com/LennardKittner/HyperXCloudIIWireless/issues/1

I close this issue as a duplicate, thanks for your help.


Refactor discovery consumer

Motivation
Our current usage of discv5 is very sub-optimal

Queries are issued continuously non-stop, finding tons of ENRs
however, the node struggles to find good peers

Description
Moves discv5 into our own PeerManager evicting it from libp2p blackbox. Now we control dials and have access to the ENRs directly.

Check eth2 field and other metrics to connect only to good ENRs
Cache good results to prevent continuous queries
Add many new metrics to have visibility into how optimal this design is. There's a lot to improve still

Metrics
Answer the questions:

How efficiently are we finding relevant ENRs?
How efficient are our dial attempts?
How efficient is the cachedENRs mechanism?
How frequently the app layer is requesting more peers?

dial time metrics already show cases where a failed dial took 16 minutes.

I've tested this PR for 12 hours in Prater nodes (1, 16, and 900 validators) and validator performance has not been changed at all. It seems attestations are propagated properly :+1:

on contabo-0, it shows that we connect to only 1-2 attestation subnet peers a lot of time although we have 7 validators connected to that node. Sometimes the number goes up to 60 and then drop significantly to 1-2.
http://<IP_ADDRESS>:3000/

With this branch the scrape timing has uptick-ed significantly. Seems that some metrics are heavy to compute. Need to investigate more


Add overlay and instructions for using it

The home-manager derivation only includes the script, not the modules. When I set up home-manager using an overlay I had to add a source package so I can point to the modules:
self: super:

{
  home-manager-src = super.fetchFromGitHub {
    owner = "rycee";
    repo = "home-manager";
    rev = "6ecf9e091c53d592edeb202378a5b5c920dfde55";
    sha256 = "0sdmmfk2dvmn0l6k0gp6027jxlv4w4dvwd3yh8lnb5hv503xsmgb";
  };

  home-manager = import self.home-manager-src {
    pkgs = self;
    modulesPath = "${self.home-manager-src}/modules";
  };
}

So I  think we would have to include the modules in the home-manager package or create a home-manager-modules package or so.

Looking good! Happy to merge to master after a squash.

Rebased to master in 34428fc7090744481e2328ddfda466596e875775. Thanks a lot!


'istanbul ignore else' inbetween a 'else' and 'if' is ignored

See also #230.

You can work around it with some extra braces:

I'm having this same issue, it seems like a problem with the branch coverage though because as the coverage shows the 'else if' case is covered by a unit test.  It's very confusing to get the 'else path not taken' marking when the 'else if' is clearly covered as shown by the 11x marking on the right side.

Just found this issue when running into the same problem. I solved it by adding the ignore line above the first if, like so:
/* istanbul ignore else */
if (element) {
	element.addEventListener('animationend', this.handleAnimationEnd)
} else if (this.contentElement) {
	this.contentElement.removeEventListener('animationend', this.handleAnimationEnd)
}

Bump.
This is annoying. I have a list of if..else if.. statements that does not need an else clause, because it's impossible to get anything else other than what's accounted for. Similar problem if I use a switch statement.
I've confirmed that if I put the /* istanbul ignore else */  above the first if, it ignores all the else if clauses, not just the final if.
My annoyingly bad choices are:

use the /* istanbul ignore else */  above the first if, and lose the benefit of Istanbul tracking my coverage of all my else if statements.

live with less than 100% coverage

forcibly pass a wasted piece of bad data into this function to get it to hit that phantom else condition

refactor the if...else if... series like this:
 if (one) { .. }
 else if (two) { .. }
 else if (three) { .. }
 else {
    /* istanbul ignore else */
    if (four) { .. }
 }

I picked option (4), but it's extra annoying because not only do I have to contort the code in that weirder shape, but then my linter complains about the "lonely if", so I have to put another comment to get the linter to hush. :/

Something like /* instanbul ignore-final-else */ would be pretty useful for stuff like this.

So is there any solution to this? I agree @getify that the workaround isn't working for all situations.

this works
if (condition1) {
} else /* istanbul ignore next */
if (condition) {

Can someone explain to me why the solution of @livingston should not be done?. it worked for me.

@arleyyap this "suggested solution" doesn't fit the form of the problem I brought up (which differs from the OP)... consider:
if (condition1) {
  // ..
} /* istanbul ignore next */
else {
  // ..
}

vs
if (condition1) {
  // ..
} else /* istanbul ignore next */
if (whatShouldGoHere) {
  // ..
}

In the first snippet, we're trying to ignore an else... which doesn't work -- that's my complaint. In the second snippet, the ignoring is of an if that's part of an else... but what condition should go there for an else that isn't ever planned to fire?
This hack could "work", but IMO is as janky (or worse) than some other work-arounds discussed earlier in the thread:
if (condition1) {
  // ..
} else /* istanbul ignore next */
if (false) {
  // ..
}

I am also facing the same issue while running test case with only if statement.
Even '/* istanbul ignore else */' statement doesn't ignore else case and results branch coverage less.

The /* istanbul ignore else */ should only affect it's own level and not affect nested if else statements.

Definitely still a problem in<EMAIL_ADDRESS>and<EMAIL_ADDRESS> In fact, else if statements cause endless problems for both ignore if and ignore else... example:
/* istanbul ignore if: this can cover branch 1 */
if (false) {
    console.log("branch 1");
} /* istanbul ignore if: does not work */ else /* istanbul ignore if: not here either */ if (false) {
    console.log("branch 2");
} else if (false) {
    console.log("branch 3");
}

As soon as you need to ignore an if entry in a series of else if chains, you can never ignore another one.  Your only option is to use an ignore next -- but that actually ignores the entire rest of the chain, including branch 3.
(I realize this is slightly different than the ignore else case in the OP, but I think it's part of the larger problem with else-if chains.)

Still busted, still annoying as heck ...

I guess my example could be solved by putting /* istanbul ignore next*/ inside each if block, which isn't bad, whereas there is no easy solution for the else case.

This doesn't quite work -- I tried this too, and while it gets rid of part of the issue, it still results in the else if reporting that the else case was not taken

2 cents: #230 should never have been closed because the advice given doesn't actually work.

@fubar that was already suggested up-thread 2 years ago.

@getify the only mention or suggestion of an "ignore next" (not "ignore else") before (not after) an else statement that I can see in this thread is in your comment (https://github.com/gotwarlost/istanbul/issues/781#issuecomment-572738364), in which you said it does not work, whereas it does work for me, so I figured someone might find it helpful.
I have not tested this in chained else statements; however, chaining elses is not exactly good practice, and I'd suggest improving the OP's code by getting rid of the unnecessary else statements and using guards instead:
if (location) {
  return ...;
}
if (timezone) {
  return ...;
}
/* istanbul ignore next */
throw new Error(...);

Like I said, the "ignore next" in that comment is after the else, not before. I'm not sure if istanbul interprets it any differently though. And when I put it behind the else, prettier reformats it to be before it, so there may be another reason for it that I'm not aware of.

It was counter-intuitive, but I finally managed to isolate the last else by inserting /* istanbul ignore else */ before the second-to-last step in the chain.
if (val === 'up') {
  // ...
} else /* istanbul ignore else */ if (val === 'down') {
  // ...
} else {
  // this should never happen and should
  // be ignored from branch coverage
  assertNever(`${val} is invalid, should be up or down`);
}

I think the problem is thinking of if/else if/else as a list data structure, whereas Istanbul sees it as a nested data structure. Making braces explicit makes it clear:
if (val === 'up') {
  // ...
} else {
  /* istanbul ignore else */
  if (val === 'down') {
    // ...
  } else {
    // this should never happen and should
    // be ignored from branch coverage
    assertNever(`${val} is invalid, should be up or down`);
  }
}

@greim make it a switch (or guards if you can make it a separate function). Excessive else statements and nested ifs are code smells. In fact, your second example would be reformatted by prettier into an else if.
switch (val) {
  case 'up':
    // ...
    break;
  case 'down':
    // ...
    break;
  /* istanbul ignore next */
  default:
    throw new Error(`Invalid value: ${val}`);
}

@fubar - I didn't mean to suggest my second example is how code should be written, but rather to illustrate what Istanbul sees when it parses my first example. Hope that clears it up.

@greim this is basically what I suggested up-thread here.

@getify You suggested putting the comment immediately above the first if. Instead, try putting it in the second-to-last position like this:
if (thing) {
  // included
} else /* istanbul ignore else */ if (thing) {
  // included
} else {
  // excluded
}

As far as I can tell, nobody in this thread has suggested this, except for OP, who was apparently complaining it doesn't work? Maybe something got fixed in the interim, but it works fine for me.


Service command override stopped working with 1.0.0-rc1

Component
agent
Describe the bug
We use the following services definition with a command statement as a workaround for a bug in Timescaledb:
services:
  database_timescale:
    image: timescale/timescaledb:latest-pg15
    command: postgres -c timescaledb.max_background_workers=0

If we don't start postgres with this max_background_workers setting, Woodpecker is unable to clone the test database.
This worked with Woodpecker 0.15.11 and stopped working with Woodpecker 1.0.0-rc1. Have there been any changes regarding this services command override?
System Info
Woodpecker 1.0.0-rc1

Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

@ateuber did this worked for sure in the past?
should'nt it be  commands  <- missing s ?

https://github.com/woodpecker-ci/woodpecker/blob/release/v0.15/pipeline/frontend/yaml/container.go#L30-L31
vs.
https://github.com/woodpecker-ci/woodpecker/blob/main/pipeline/frontend/yaml/types/container.go#L23

ok if the v0.15 had this mentioned in the docs somewhere we have to handle it as breaking change and mention it in the cangelog and provide a migration path

likely a regression of  #1032

@ateuber we wont add it back for safety reasons.
but you can migrate any service by lookup how the entrypoint in the original image was and combine it into it's commands form. If the entrypoint already was a shell you just have to append an s as in your case.
services:
  database_timescale:
    image: timescale/timescaledb:latest-pg15
    commans: postgres -c timescaledb.max_background_workers=0

@6543, There's a typo in your response

commans:

Thanks @6543, it is working with commands. That was an easy fix. :laughing:

well it just has to be mentioned at the migration docs ->  #2056


Refactor MessagesRead response

Added entry to UnionMessageReply that represents response from MessagesRead.
Modified MessagesReadReplyEntry to include data as a sibling property to message

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.69%. Comparing base (c6d8526) to head (d4cfba9).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #776   +/-   ##
=======================================
  Coverage   98.69%   98.69%
=======================================
  Files          73       73
  Lines       11257    11263    +6
  Branches     1609     1609
=======================================
+ Hits        11110    11116    +6
  Misses        141      141
  Partials        6        6

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


Directives to add

Some that I definitely want in there:
From "core":

[x] list-table: https://docutils.sourceforge.io/docs/ref/rst/directives.html#list-table
[ ] csv-table: https://docutils.sourceforge.io/docs/ref/rst/directives.html#csv-table-1
[x] math #13
[ ] topic
[ ] sidebar
[ ] rubric

Maybe also things from extensions (optional?):

[ ] sphinx-book-theme margin
[ ] Things from sphinx-panels: https://sphinx-panels.readthedocs.io (actually now sphinx-design)
[ ] sphinx-tabs, sphinx-inline-tabs

Here's a list from https://rst-to-myst.readthedocs.io/en/latest/cli.html of all the "base" docutils+sphinx roles/directives:
From rst2myst roles list:
abbr abbreviation acronym anonymous-reference any citation-reference code command dfn download emphasis eq file footnote-reference guilabel index kbd literal mailheader makevar manpage math menuselection mimetype named-reference newsgroup pep pep-reference program raw regexp restructuredtext-unimplemented-role rfc rfc-reference samp strong subscript substitution-reference superscript target title-reference uri-reference c:data c:enum c:enumerator c:expr c:func c:macro c:member c:struct c:texpr c:type c:union c:var cpp:any cpp:class cpp:concept cpp:enum cpp:enumerator cpp:expr cpp:func cpp:member cpp:struct cpp:texpr cpp:type cpp:union cpp:var js:attr js:class js:data js:func js:meth js:mod math:numref py:attr py:class py:const py:data py:exc py:func py:meth py:mod py:obj rst:dir rst:role std:doc std:envvar std:keyword std:numref std:option std:ref std:term std:token

From rst2myst directives list:
acks admonition attention caution centered class code code-block codeauthor compound container contents cssclass csv-table danger date default-domain default-role deprecated describe epigraph error figure footer header highlight highlights hint hlist image important include index line-block list-table literalinclude math meta moduleauthor note object only parsed-literal pull-quote raw replace restructuredtext-test-directive role rst-class rubric sectionauthor sectnum seealso sidebar sourcecode table tabularcolumns target-notes tip title toctree topic unicode versionadded versionchanged warning c:alias c:enum c:enumerator c:function c:macro c:member c:namespace c:namespace-pop c:namespace-push c:struct c:type c:union c:var cpp:alias cpp:class cpp:concept cpp:enum cpp:enum-class cpp:enum-struct cpp:enumerator cpp:function cpp:member cpp:namespace cpp:namespace-pop cpp:namespace-push cpp:struct cpp:type cpp:union cpp:var js:attribute js:class js:data js:function js:method js:module py:attribute py:class py:classmethod py:currentmodule py:data py:decorator py:decoratormethod py:exception py:function py:method py:module py:property py:staticmethod rst:directive rst:directive:option rst:role std:cmdoption std:envvar std:glossary std:option std:productionlist std:program

Goal - get these into a spreadsheet/doc to help prioritize them and exclude various roles/directives.

+1 for sphinx-tabs and sphinx-inline-tabs!
These are super useful for all sorts of documentation, and are so frustrating to write in the regular, nested rst syntax. MyST makes it so much easier, and in-browser rendering thereof would be perfect.
Thanks for this effort. BTW am I right in understanding markdown-it-docutics supersedes markdown-it-myst?

+1 for sphinx-tabs and sphinx-inline-tabs!

well https://sphinx-design.readthedocs.io/en/furo-theme/tabs.html are the way forward 😉

Thanks for this effort. BTW am I right in understanding markdown-it-docutics supersedes markdown-it-myst?

So the idea is that eventually markdown-it-myst will be updated, to combine this plugin with others required by myst (https://github.com/executablebooks/markdown-it-dollarmath, etc) into a single "myst parser"
For example, I am currently doing this directly in https://github.com/executablebooks/myst-vs-code/blob/c8c96542171ebe6ccdd896cf8337a5ffffeb73d4/src/extension.ts#L1

Ah! I see. Sphinx-design is the new Sphinx-panels. Fancy, but I do like the gracefuleness of the inline tabs (most of the time the top-level "tab-set" directive is indeed redundant, so having an option to just have a bunch of neighboring tabs be grouped by default is pretty smart). Also small interoperable plugins sound like a nice idea, a bit worried about pulling in a lot of things of which you will still mostly use tabs ;)
Having said that - hey, if you implement sphinx-design, that's what I'm gonna use :) this is not a big deal.
Thanks for the explanation of your plans re myst parsing. I think the docutils part is really important as it is the main point of interop with Sphinx etc.

The evolution of tabs was actually; (1) I didn't really like the implementation/look of the ones in sphinx-tabs, so added tabs to sphinx-panels, (2) pradyunsg didn't like the fact that in sphinx-panels you have to load the full css framework and no syncronised tabs, so copied the logic from sphinx-panels to sphinx-inline-tabs, (3) In sphinx-design I removed the dependency on bootstrap and added the tab synchronisation, so pradsyung is back on board (https://github.com/executablebooks/sphinx-design/pull/22) lol

Thanks for the explanation of your plans re myst parsing. I think the docutils part is really important as it is the main point of interop with Sphinx etc.

yeh its just trying to get the balance, between trying to get myst as something that is not dependent on docutils/sphinx (and thus python), but not ending up re-writing the whole of these packages, see: #18

I'd like to propose that we add the figure-md directive for figures whose contents are written in Markdown?


Home Page buttons don't work

Learn More, Documentation, and Image Space don't go anywhere.
http://explorer.continuum.io/ for pilot demo.

@wmburke currently adding some tests for this. I'll let you know as soon as them are integrated into the deployed application.

Okay - I see that these work in Chrome also, but not in firefox. In Firefox, clicking on these buttons does nothing.

Ahh i see now. Thanks for clearing that up. I'm experiencing the same problems in firefox, also with the buttons. Thanks for catching that.

Fixed in #415


lists.podman.io is unberable slow (impossible to use)

The currently advertised mailing list seems not to be really functional. I spent more than an hour trying to register, confirm and post a message. Apparently is also moderated.
While there are only a couple of messages posted it seems that the mailing list website is almost impossible to use. I spent >30 min to manage to create and login only.
The average time to load a page is 10s-20s, which indicates some serious infra issue.
https://lists.podman.io/archives/profile/ --- time to load 19s
Can someone take a look at this?
I cannot refrain from wondering why we do not re-use another public mailing list service instead of spinning up a new one. To me it would make more sense to avoid extra maintenance needed and use something else.
The current state of https://lists.podman.io may explain why it has so few users.
PS. It would be good to add an infra label what we could use to mark infrastructure related issue, like github, services, irc.

@ssbarnea Thanks for the heads up.  This is the first I've heard of issue like this with the list.  When I've used it, it's always been very speedy, I don't think I've waited more than a second or two to transition from one page to another.  I'll go see if there's something going on there.

FWIW, it's speedy for me.

The average time to load a page is 10s-20s, which indicates some serious infra issue.

Can you check your browsers dev tool, specifically the network tab? What request(s) are consuming the most time and in what phase of the request does the time go (DNS, handshake/tls negotiation, content transfer... etc) ?

@ssbarnea I played around with the web interface yesterday from work and from my home PC's and I think the longest transition I had was close to 2 seconds, most were well under a second.
I just wanted to verify that the slowness you mentioned was that rather than the slowness to become a member when you register.  We'd a really bad spam attack in early November and required people to get OK'd by an admin before they became registered.  Unfortunately the server didn't sent mail out to the admins so we'd not realized a number of signups had come in, we were several weeks behind in getting those taken care of.

The issue seems to be resolved now; just tested. Please re-open if you are still experiencing performance issue.


[Suggestion] Ability to package custom instrument samples into .nbs file

Would make it easier to share NBS files using custom instruments as you wouldn't have to share the sample files separately.
Would be useful for individual songs that use different samples with the same name.

I've thought about this before, this would indeed make sharing songs a lot easier. The "Pack sounds to ZIP file" option added in 3.8.1 was intended to be an advancement in that direction, but I agree that packing everything into a single file would be even more convenient. Perhaps a middle-ground solution could be to package a ZIP file containing the .nbs file as well, not only the instruments.
If we ever do create a new file format for this purpose, it must be well though-out: will the binary data of each sound file just be appended at the end of the current .nbs file structure, or will it be a different file type (maybe a ZIP file internally?) Also, will we keep the same file extension, or use a different one? (such as .nbsi?) And more importantly, would it be viable for plugins to take advantage of that new structure to simplify song loading? (Likely not, since songs are loaded server-side while resources are client-side). These are just some things to keep in mind if we do implement this in the future. :)


Will PULID SDXL 1.1 be released as scheduled?

Hello, will PULID SDXL 1.1 be released soon as stated in the readme.md? I'm a fan of PULID technology, and I've been waiting for PULID SDXL 1.1 to be released since June this year. Is there going to be another delay?

PuLID-v1.1 for SDXL and PuLID-FLUX-v0.9.1 have been release now. Thanks for your waiting and patience.

@ToTheBeginning Thank you!


supports roks in acm 2.2

https://github.com/open-cluster-management/backlog/issues/11125

2.2.2 is out. so we can merge this PR once it is ready @marcolan018

/retest

/approved


Upgrade flake8 to allow type-ignore comments

Can we upgrade flake8 to the latest version? That's 4.0.1 at the time of writing.
We need to upgrade for compatibility with the mypy static type checker. Mypy's use was approved in #4944.
Mypy supports the use of control comments to silence type errors.
In my organizations-fixes branch I'm experimenting with adding types to the organizations models. I've added some control comments where the types are not strictly correct and I don't want to fix it yet.
An example from OrganizationsBackend:
    def create_organizational_unit(self, **kwargs: Any) -> ot.CreateOrganizationalUnitResponseTypeDef:
        # TODO: Arg type needs to be FakeOrganization, but it can sometimes be None.
        new_ou = FakeOrganizationalUnit(self.org, **kwargs)  # type: ignore[arg-type]
        self.ou.append(new_ou)
        self.attach_policy(PolicyId=utils.DEFAULT_POLICY_ID, TargetId=new_ou.id)
        return {"OrganizationalUnit": new_ou.describe()}

flake8, well, "flakes out" at this:
moto/organizations/models.py:418:62: F821 undefined name 'ignore'
moto/organizations/models.py:418:62: F821 undefined name 'arg'

In requirements-dev.txt flake8 is pinned to 3.7.8.
That version of flake8 depends on pyflakes:
    pyflakes >= 2.1.0, < 2.2.0

In my virtualenv it resolves pyflakes to v2.1.1.
That version of pyflakes is incompatible with mypy's control comments to ignore type errors.
This was fixed in pyflakes 2.2.0.

Allow type ignore to be followed by a code # type: ignore[attr-defined]

flake8 v4.0.1 generates about 60 linting errors on the moto code. If we upgrade flake8, those will have to be addressed as well.

Make sense @iainelder. I'll create a PR that fixes the linting issues on the new flake8.

Thanks for the quick resolution! I'll check how mypy works soon and confirm.

Now flake8 plays nicely with mypy's type-ignore comments. Thanks!


fix: manipulate Errors created by might-fail and remove the might-fail traces

https://github.com/meech-ward/might-fail/issues/8


Second step for new job sometimes broken

Steps to reproduce:
create a new job and for the Companyname choose some random text, do not select the autocomplete and then use the enter key (not the save button).
The Company name is saved and if you click "next to enter the job" you will only see "An error occurred
An unexpected error had occured. Please try again later.".
The TemplateController tries to fetch data from the organization, but in this case there is no data available
2015-03-11 01:14:26 NOTICE Trying to get property of non-object (errno 8) in /YAWIK/module/Jobs/src/Jobs/Controller/TemplateController.php on line 183
2015-03-11 01:14:26 ERR Argument 1 passed to Jobs\Controller\TemplateController::getOrganizationLogo() must be an instance of Organizations\Entity\Organization, null given, called in /YAWIK/module/Jobs/src/Jobs/Controller/TemplateController.php on line 187 and defined (errno 4096) in /YAWIK/module/Jobs/src/Jobs/Controller/TemplateController.php on line 199

This happens, if there is wrong logo reference stored in an organization.
The problem can propably be fixed by checking the $organization->image in
https://github.com/cross-solution/YAWIK/blob/develop/module/Jobs/src/Jobs/Controller/TemplateController.php#L201

The logo reference is not the problem.
there is no organization:
https://github.com/cross-solution/YAWIK/blob/develop/module/Jobs/src/Jobs/Controller/TemplateController.php#L187

I confirm this bug - both in the online demo (v0.17.2-145-g6316b43) and in my local installation (v0.17-4-g02a53f0). It happens EVERY time, I try to create a new job.

Creating of job opening works again since 0.18. Thanks for reporting


Editor crash when opening project

Tested versions
f47f4a02c good
79de2eaae bad
System information
Godot v4.3.dev (f47f4a02c) - Linux Mint 21.3 (Virginia) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 Ti (nvidia; 535.161.07) - Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz (4 Threads)
Issue description
If you exit the editor with scene tabs open, and the active scene tab is not the last one, it will crash the next time you open the project.
Crash log when reloading the project.
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.3.dev.custom_build (79de2eaae7fb3bb8f13031ac2ec9b19128b6f471)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
ERROR: FATAL: Index p_index = 1 is out of bounds (size() = 0).
   at: get (./core/templates/cowdata.h:205)

Crash log when reopening the project.
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.3.dev.custom_build (b345614adb7cb17aa3b9ee2cd17b413a54fa40b7)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x78656f042520] (??:0)
[2] /opt/godot/godot/bin/godot.linuxbsd.editor.dev.x86_64.llvm(__dynamic_cast+0x2d) [0x5bc007806c7d] (??:?)

-- END OF BACKTRACE --
================================================================

Steps to reproduce

Create a new project and open;
Create new scenes and save;
Select any scene tab except the last one;
Save to let the editor remember the selection;
Reload the project, crash;
Reopen the project, crash;

Minimal reproduction project (MRP)
N/A

Initial testing says e302fb2167aabcd83001e7f5d61e809f8f662692 is the broken pull request.

CC @RedMser


[monitor] Commits from upstream fork

These commits were made upstream on the parent fork. There are significant changes here in the code, we can't simply merge them in at this stage. Just creating this PR so that we can all monitor what's being changed in the upstream fork.

Don't care about this anymore.


Duplicating propTypes ?

There is the ESLint rule prop-types which I am using and looks like a good thing. However with @provide having separate propTypes this wont work and I would have to duplicate these.
I guess that pulling propTypes from component constructor instead of having it specified by argument to @provide is not an option because there might be other props mixed in which are not about to be provided. Any idea what could be done about this?

I personally stopped using ESLint because of running into silly stuff like this entirely too often.  It's too rigid/opinionated for my tastes.  That said, there are 3 options I can think of right now to solve this problem, best options first (in my opinion):

Fix the ESLint prop-types rule to look at the resulting (decorated, higher order) component's constructor's propTypes.
Disable the prop-types rule.
You should be able to simply call @provide() without any propTypes and merge your provided propTypes into your component's propTypes.  The reason for passing propTypes to provide() as a separate object is mainly for explicitness and readability/understandability.  It's to make it obvious to anyone looking at the component which props are expected to be provided by flux/redux as opposed to props provided by parent components.

That's interesting because I find this rule as one of very handy. I have plugin to Sublime Text which immaterially tells me when I use prop which is not on propTypes and thus most likely missing from the pipeline.
Anyway I will try to create issue for that rule and see if there is something possible to do. Frankly I am not sure how does this works, but I thought that static analysis cannot investigate used decorators.
Thanks for help.

Hey, as of 4.1.0, I changed the API for @provide so that instead of @provide(propTypes) it's just @provide and said propTypes are merged into the usual static propTypes = { ... };.  Can you let me know if that fixes the problem with ESLint?


Update the game over message

Update the game over message so people know how to play again!

lgtm


Collada Exporter not taking into account all the material/effects

Description

Expected behavior:

When using the Collada Exporter from ign-gazebo, all textures files should be exported into the final result.

Actual behavior:
They only get exported if their full path name includes "meshes/".

Steps to reproduce
In an environment that includes an Ignition installation:

Add the ColladaExporter plugin to the tunnel.sdf ign-gazebo example file.
Run the Collada Exporter on that file.
ign gazebo -v 3 -s -r --iterations 1 tunnel.sdf
Open the .dae exported to the path ./tunnel/meshes/tunnel.sdf

However, this can't be reproduced at the moment because it depends on fixing https://github.com/ignitionrobotics/ign-gazebo/issues/761.
I was able to track this problem to these conditional include statements like this one:
https://github.com/ignitionrobotics/ign-common/blob/d496d79d9d90b9474e7ccd298210115084e472ad/graphics/src/ColladaExporter.cc#L511
The collada exporter is only taking into account effects/textures if the path included "meshes/' in its name. However, ign-gazebo is able to open all files in its environment path variable and fuel models are usually loaded from ~/.ignition/fuel/fuel.ignitionrobotics.org/openrobotics/models/, in neither of those cases the file includes the meshes.
I imagine there was an old context for this check statement, I didn't find any in the history of this file though. If there are no problems I can open a PR to remove those checks or add to the check at least paths including "materials" as well. Let me know your thoughts.

WDYT @gonzodepedro

Ignition shouldn't enforce any specific paths, so I think it's ok to remove that check. Let's make sure we add a test exporting a texture without meshes in the path to check it works as intended.

I can't remember why it was done like that. You can see the commit history on Gazebo classic (the files were ported from there to Ignition):
https://github.com/osrf/gazebo/blame/gazebo11/gazebo/common/ColladaExporter.cc#L359
I didn't find any specific discussion about this on the pull request backup.
I originally wrote the ColladaExporter to simplify meshes for GzWeb, and GzWeb does enforce folder structures like meshes and materials/textures for assets, mainly because it's tough to traverse "directories" on the web. So my guess is that the reason is related to that, and it shouldn't be an issue here.


Question: Is it possible to hook into, or add a hook to allow for further token validation

I have a scenario where I need to validate the audience claim on the id token, is there away to add in a hook, or one be made available so that one could add additional token validation during on of the ResponseValidator steps?
i.e. say add a event that could get execute in the _validateIdTokenAttributes function, so that I could do an additional validation check there?

Currently that is not possible. You would need to provide a MR to add such a functionality. Also i am not so sure that this would be the correct location. Your validation the audience claims seems very user specific.  Why do you not make the validation in a post process after you have received an access token?


File path in Vscode terminal is not clickable to jump into again.

Version: 1.38.1
OS Mojave 10.14.6:

Steps to Reproduce:

Open terminal, ran Angular project and on purpose made a mistake in file to get error in terminal. For link it works but not for file path.
Installed the same version on Windows 10 and worked but not on MacOS.

Does this issue occur when all extensions are disabled?: Yes

I suspect this has the same root cause as https://github.com/xtermjs/xterm.js/issues/2458


custom ad sizes for Android and iOS

Hi , @matejdr , how are you ?  Custom AdSize, tested via Android and iOS ... In the component adSize="460x530" or "520x300" and so on

Thanks for your PR, I've used your code as part of the refactor here: https://github.com/NZME/react-native-ad-manager/pull/53/files#diff-88d23f79f39ba76dadc2fcea2e8fa71d6e333f12b3e28a00897e9ea462484907


Viterbi Algorithm

Implement viterbi algorithm

Some thoughts I've just had, @awohns:

I think we need to store traceback pointers for every edge in the TS (not every node).
We need grid_size traceback pointers per edge
Each pointer needs to indicate the hidden state of the edge.child it came from (hence we can simply store the index of the hidden state (e.g. 0..50)
I suggest we use 2 bytes (np.uint16) for these pointers, which allows up to 65536 hidden states. For UKB+TGP, which has 185 million edges, and with 50 timeslices, that means the traceback array should be 185 * 2 * 50 megabytes, or roughly 18GB, which is fine for a server. If we want 100 timeslices, it will obviously be twice that, which is still fine too.

4.  We can decide on what size to use for the base storage depending on the grid size. For <=256 hidden states, we can use np.uint8, for >256 but <65536 states we can use np.uint16, and for anything more we can use np.uint32 (and check that the user isn't asking for > 2^32 states!).
Since this is by far the largest use of memory in tsdate, we should perhaps think about storing it in a zarr array, so it can be disk mapped if necessary.

@hyanwong, is this still something we want to do?

I think we'll have problems with the loopiness. So we can drop this, but maybe we should have a "future ideas" section that we can add this sort of thing to?


App crash when click open and in test mode

Hi, I am new to Andorid apps anyway i am able to build the app but when i try to run it crash all the time both when I plug in the dji mini 2 and when I try test mode. If someone can help me i would appreciate it. I get the following error:

'E/UDT-JNI: stopped udp
E/getNetworkObject: network type:1
D/AndroidRuntime: Shutting down VM
E/AndroidRuntime: FATAL EXCEPTION: main
Process: sq.rogue.rosettadrone, PID: 14145
java.lang.IncompatibleClassChangeError: The method 'java.lang.Class java.lang.Object.getClass()' was expected to be of type interface but instead was found to be of type virtual (declaration of 'com.google.android.gms.dynamic.ObjectWrapper' appears in /data/app/sq.rogue.rosettadrone-6xqXF7rZNy05mYRqqHkyZQ==/base.apk)
at com.google.android.gms.dynamic.ObjectWrapper.unwrap(com.google.android.gms:play-services-basement@@18.0.2:4)
at com.google.android.gms.maps.zzau.onCreateView(com.google.android.gms:play-services-maps@@18.0.0:12)
at com.google.android.gms.dynamic.zad.zab(com.google.android.gms:play-services-base@@18.0.1:2)
at com.google.android.gms.dynamic.DeferredLifecycleHelper.zaf(com.google.android.gms:play-services-base@@18.0.1:1)
at com.google.android.gms.dynamic.DeferredLifecycleHelper.onCreateView(com.google.android.gms:play-services-base@@18.0.1:2)
at com.google.android.gms.maps.SupportMapFragment.onCreateView(com.google.android.gms:play-services-maps@@18.0.0:1)
at androidx.fragment.app.Fragment.performCreateView(Fragment.java:2963)
at androidx.fragment.app.FragmentStateManager.ensureInflatedView(FragmentStateManager.java:386)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:281)
at androidx.fragment.app.FragmentLayoutInflaterFactory.onCreateView(FragmentLayoutInflaterFactory.java:140)
at androidx.fragment.app.FragmentController.onCreateView(FragmentController.java:135)
at androidx.fragment.app.FragmentActivity.dispatchFragmentsOnCreateView(FragmentActivity.java:319)
at androidx.fragment.app.FragmentActivity.onCreateView(FragmentActivity.java:298)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:791)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:741)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:874)
at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:835)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:877)
at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:835)
at android.view.LayoutInflater.inflate(LayoutInflater.java:515)
at android.view.LayoutInflater.inflate(LayoutInflater.java:423)
at android.view.LayoutInflater.inflate(LayoutInflater.java:374)
at androidx.appcompat.app.AppCompatDelegateImpl.setContentView(AppCompatDelegateImpl.java:699)
at androidx.appcompat.app.AppCompatActivity.setContentView(AppCompatActivity.java:195)
at sq.rogue.rosettadrone.MainActivity.onCreate(MainActivity.java:713)
at android.app.Activity.performCreate(Activity.java:7383)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1218)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3256)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3411)
at android.app.ActivityThread.-wrap12(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1994)
at android.os.Handler.dispatchMessage(Handler.java:108)
at android.os.Looper.loop(Looper.java:166)
at android.app.ActivityThread.main(ActivityThread.java:7529)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921)
E/DJIUSBWifiSwitchManager: ****resetSwitchFromWifiFlag
E/DJIUsbAccessoryReceiver: receiver destroySession
I/Process: Sending signal. PID: 14145 SIG: 9'

Seems to be related with Google maps.
Did you configure valid keys following the README?

I don't think it's the same problem.
Did you maybe update gradle? Don't do it.
You could also try Terje's branch:
https://github.com/The1only/rosettadrone/tree/work_branch
He just updated versions.

Maybe this:
https://issuetracker.google.com/issues/232131782?pli=1

@The1only did you also fix this on your working branch?
Seems that this was the problem.
I didn't merge yet, because I didn't notice the problem.
I have been busy with the precision landing implementation. Trying to bring together two top projects for the long term:
https://github.com/chobitsfan/apriltag_plnd/issues/1

Yes I hade issues with Play services, took me a while to figure out to what level I could uppdate while stil be able to make things work.We support Android 5.1 and 7.1 that might be affected by this.TerjeBest regardTerje Nilsen9Tek ASNorwayOn 16 Mar 2023, at 19:24, Christopher Pereira @.***> wrote:
@The1only did you also fix this on your working branch?
Seems that this was the problem.
I didn't merge yet, because I didn't notice the problem.
I have been busy with the precision landing implementation. Trying to bring together two top projects for the long term:
chobitsfan/apriltag_plnd#1
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


python3Packages.django-leaflet: init at 0.29.0

Description of changes
https://pypi.org/project/django-leaflet/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 236107 run on x86_64-linux 1

4 packages built:

python310Packages.django-leaflet
python310Packages.django-leaflet.dist
python311Packages.django-leaflet
python311Packages.django-leaflet.dist


Task prep_nextcloud : set nextcloud domain config.php values fails on latest nextcloud 19.0.0

Deploying on fresh ubuntu 18.04 fails for latest Nextcloud 19.0.0
TASK [prep_nextcloud : set nextcloud domain config.php values] **************************************************************************************$
Tuesday 23 June 2020  22:42:27 +0200 (0:00:00.051)       0:01:09.197 **********
failed: [localhost] (item={'key': 'overwrite.cli.url', 'value': '--value=https://MASKED'}) => changed=true
  ansible_loop_var: item
  cmd: php occ config:system:set overwrite.cli.url --value=https://MASKED
  delta: '0:00:00.162633'
  end: '2020-06-23 22:42:27.796205'
  item:
    key: overwrite.cli.url
    value: --value=https://MASKED
  msg: non-zero return code
  rc: 1
  start: '2020-06-23 22:42:27.633572'
  stderr: |2-

      There are no commands defined in the "config:system" namespace.
  stderr_lines: <omitted>
  stdout: Nextcloud is not installed - only a limited number of commands are available
  stdout_lines: <omitted>
failed: [localhost] (item={'key': 'trusted_domains', 'value': '1 --value=MASKED'}) => changed=true
  ansible_loop_var: item
  cmd: php occ config:system:set trusted_domains 1 --value=MASKED
  delta: '0:00:00.188831'
  end: '2020-06-23 22:42:28.174882'
  item:
    key: trusted_domains
    value: 1 --value=MASKED
  msg: non-zero return code
  rc: 1
  start: '2020-06-23 22:42:27.986051'
  stderr: |2-

      There are no commands defined in the "config:system" namespace.
  stderr_lines: <omitted>
  stdout: Nextcloud is not installed - only a limited number of commands are available
  stdout_lines: <omitted>

I manually downgraded the inventory to Nextcloud 18.0.6, removed /var/www/nextcloud, dropped database nextcloud, redeployed, and then it worked for me!
sudo rm -rf /var/www/nextcloud
sudo -u postgres psql
DROP DATABASE nextcloud;
\q
vim inventory

Insert the following
#next_archive         = https://download.nextcloud.com/server/releases/latest.tar.bz2
next_archive         = https://download.nextcloud.com/server/releases/nextcloud-18.0.6.tar.bz2

Redeploy
./nextcloud.yml

Hi.
I just tried the playbook on an EC2 with Ubuntu 18.04 and couldn't reproduce the error.
The error message There are no commands defined in the "config:system" namespace. indicates to me that the inital setup didn't succeed in a former run.
https://github.com/ReinerNippes/nextcloud/blob/6fa327bb96f4adf80d6404793f5a3cb1c58219dd/roles/prep_nextcloud/tasks/main.yml#L67
The initial setup is only triggered if config.php doesn't exist.
So I can't comment on your error.
Nevertheless if you are using Ubuntu you should upgrade to Ubuntu 20.04 and use the nextcloud-reloaded branch.


Question: How can I obtain ~same speed as the server ?

Hello,
First of all thank you for sharing your work!
I tried to install and use colabfold locally, and use colabfold_search instead of the server (I have ~7000 proteins to predict). I managed to use it, and mobilised the required ressources (1tb ram, performant CPU etc), but I still can't manage to obtain the .a3m files with a correct speed. It takes ~1h per protein. I used this tutorial https://qiita.com/Ag_smith/items/bfcf94e701f1e6a2aa90 as an example for my code.
Could I see more examples of how do you run colabfold_search, especially for a folder full of fasta files?

OS: Ubuntu 22.04

Same problem!

Please check the following computational environment:

Is your database placed on a local SSD, not an HDD? If you are using HDD, the calculation speed will be extremely slow. In other cases, if the database is located on a network drive (such as NFS), it will delay the calculation.
vmtouch is useful to keep the database in the RAM. --db-load-mode 2 is also useful, but it will be effective from the second cycle.

Hi! I need to fold around ~1k dimers and I was wondering whether it is faster to download MMseqs2 locally (colabfold_search) or use the MSA server (colabfold_batch). If so, how much faster? Also, many of these dimers share the same monomer. Is there a way of speeding things up knowing that?


Additional suggested tag

Nowadays, most deployments are done with pipelines. For convenience, I recommend adding the git repository URL name-value pair (e.g., 'repositoryURL'). Based on my experience, it greatly reduces the time required to alter the deployments.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 4c7230a9-5b65-919f-1ed7-e4c3647cdc55
Version Independent ID: 705b4355-78aa-b573-c833-de558da2a958
Content: Define your tagging strategy - Cloud Adoption Framework
Content Source: docs/ready/azure-best-practices/resource-tagging.md
Service: caf
Sub-service: caf-methodology-ready
GitHub Login: @martinekuan
Microsoft Alias: martinek

Thank you for your feedback. We have created internal ticket 206037 to track and investigate this issue.

#please-close


Map

Is there any support for map's loading via load.tileMap?

You should be able to just throw the JSON file into your assets folder and the game will automatically load it and it will be available in the Assets class.
game.load.tilemap(Assets.JSON.Map.GetName(), Assets.JSON.Map.GetJSON(), null, Phaser.Tilemap.TILED_JSON);
Does that work? I don't have time to check at the moment.

I add automatic support for maps (I like automatic stuff).
I will clean up my codes a little and open a pull request
Thanks for your awesome work by the way.

Awesome! Thanks for the help.


DOC/DEV: update commit message guidance

This is a note-to-self to update http://scipy.github.io/devdocs/dev/contributor/development_workflow.html#writing-the-commit-message. A few points:

I believe that "If the commit is related to a ticket, indicate that with
"See #XXXX", "See ticket XXXX", "Closes #XXXX", or similar" is actually an anti-pattern (at least in some opinions), as it can clutter the linked issue. 'Closes ...'  belongs in the PR description, rather than in every commit, IMO. It should only really be included in the extended description if it significantly improves it.
It's useful to include the relevant module/function (when there is one) after the acronym, like ENH: stats.circmean: ... or MAINT: fft: .... This doesn't need to be enclosed in backticks.
The example given, ENH: add functionality X to SciPy.<submodule>., is not great, IMO. There is no need to include SciPy in the commit message - that's a given.

This may include updating the PR description template.

 Hence MAINT:fft:Some commit messageis fine and makes grepping much easier.

 Hence MAINT:fft:Some commit messageis fine and makes grepping much easier.

Point taken, but most people do put spaces around the colons[^1], so I think it's probably not worth enforcing either way - maybe saying that either is okay (or including both in examples) makes sense.
[^1]: and I think it looks nicer...

Agree with points 2 and 3. One comment on 2" backticks are not necessarily bad, and useful especially when referring to names with underscores, because that prevents formatting in release notes from going wrong (PR titles are included, and underscores are special syntax in reST.
Point 1 is a bit more complex. I agree with the first part. However, if there's a single commit that fixes an issue and you don't force-push that a lot, then adding Closes gh-1234 in the commit message is helpful. Commit messages need to be descriptive, and for future debugging it's quite relevant to see what a commit fixed without having to figure out what PR it was included in. So this is more a "it depends".

That all makes sense. This issue was partly motivated by the guidance to 'name and describe your PR as you would write a
commit message'. I think Closes gh-1234 is one case where it would be useful to draw a distinction between the two - "it depends" for commit messages, as you say, but almost never good for PR titles.


dev-env start errantly claims my WordPress version is not up to date.

Description
Fixed problem in dev-env start where the command would not recognize the correct wordpress version.
Steps to Test

Check out PR.
Run npm run build
Run ./dist/bin/vip-dev-env-start.js --slug=test
Verify WordPress version is observed as intended.

Superseded by #1005


How to get the activation's output

I want to get  the output value of each activiation layer after each sample through it.

Let  X be your input. Let model be a Sequential model  with say, 10 layers. If you want to get the activation at the 8th layer, then:
tmp = model.layers[:]
model.layers = model.layers[:8]
Y = K.eval(model(K.variable(X)))
model.layers = tmp
print(Y)

Alternatively you could do something like:
from keras import backend as K

layer = model.layers[8]
f = K.function([model.get_input(train=False)], [layer.get_output(train=False)])
print(f([x])[0])  # your activation tensor

@fchollet I am trying this to get the activations of the model if I call the predict() function:
layer = ae.model.layers[2]
f = K.function([ae.model.get_input(train=False)], [layer.get_output(train=False)])
print(f([v])[0])

Where ae is simply
class WordEmbeddingEncoder:

    def __init__(self, nb_dimensions, nb_outputs):

        in_x = Input(shape=(nb_dimensions,))

        e_h1 = Dense(1024, activation='relu')(in_x)

        encoded = Dense(64, activation='relu')(e_h1)

        output = Dense(nb_outputs, activation='softmax', trainable=False)(encoded)

        self.model = Model(input=[in_x], output=[output])
        self.model.compile(optimizer='adam', loss='mse')

But it appears that the API changed as I get
AttributeError: 'Model' object has no attribute 'get_input'

So, how could I get the activation of a certain layer as I call the predict() function?

Okay I think I figured it out myself
tmp = ae.model.outputs
ae.model.outputs = [ae.model.layers[2].output]
y_pred = ae.model.predict(v)

# In case a restoration is needed one can do it
# but I think this has a huge performance impact
ae.model.outputs = tmp
ae.model.predict_function = None

Just to tag onto this, I was able to print the output validations over my test set using the solution provided by @silentsnooc, but using multiple inputs (which I've had trouble getting to work). I've seen a few other examples where they use keras.backend.eval() on the model.layer[layer_name].output as is suggested in the documentation, but I haven't gotten this method to work. So thanks @silentsnooc for following up with a working solution to getting the actual activation output values. Here's what I did to print the activations to stdout:

...#Declare the model from two sets of layers called left_branch and right_branch
merged_branches = keras.layers.concatenate([left_branch, right_branch], axis=1)
final_layers= Dense(32, activation='linear', name='merge_fc1')(merged_branches)
final_layers = Dropout(.5)(final_layers)
final_layers = Dense(16, activation='relu', name='merge_fc2')(final_layers)
final_layers = Dropout(.5)(final_layers)
predictions = Dense(num_classes, activation='sigmoid', name="output_vals")(final_layers)
model = Model(inputs=[left_input, right_input], outputs=[predictions])
...
#In the epoch loop:
Test Set Evaluation.
scores = model.evaluate([x_test, x_test_r], y_test, verbose=1)
print( model.get_layer('output_vals').output )
tmp = model.outputs
model.outputs = [model.get_layer(layer_name).output]
y_pred = model.predict([x_test, x_test_r])
print(y_pred)
Which produces the following output for a single epoch:
Train on 600 samples, validate on 200 samples
Epoch 1/1
600/600 [==============================] - 16s - loss: 0.5712 - acc: 0.7083 - val_loss: 0.7051 - val_acc: 0.4400
192/200 [===========================>..] - ETA: 0s
Tensor("output_vals/Sigmoid:0", shape=(?, 2), dtype=float32)
[[ 0.3882978   0.48870558]
[ 0.38873807  0.48904496]
[ 0.38641962  0.48915014]
[ 0.38890356  0.48918203]
[ 0.38708338  0.48985761]
....
Thanks!