DetoxRuntimeError: Detox instance has not been initialized

Problem Description:
When trying to run the Detox tests  ,
the detox build is successful, but when trying to run the detox test
facing the following error of

DetoxRuntimeError:Detox instance has not been initialized
and also getting hint to use detox.init(), where Its already being present and initialized as per the logs

The Jest-init.js
const detox = require('detox');
const config = require('../package.json').detox;
const adapter = require('detox/runners/jest/adapter');
const specReporter = require('detox/runners/jest/specReporter');

// Set the default timeout
jest.setTimeout(120000);

jasmine.getEnv().addReporter(adapter);

// This takes care of generating status logs on a per-spec basis. By default, jest only reports at file-level.
// This is strictly optional.
jasmine.getEnv().addReporter(specReporter);

beforeAll(async () => {
console.log("*******************^^^^^^^^^^^^^^^^^^^^$$$$$$$$$$$$$$$$$$$$$$$$$%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%^^^^^^^^^^^^^")
await detox.init(config);
}, 300000);

beforeEach(async () => {
  await adapter.beforeEach();
});

afterAll(async () => {
  await adapter.afterAll();
  await detox.cleanup();
});

The detox log:
╭─      ~/t/testDetox/rippling-mobile     master !8 ?2 ▓▒░········░▒▓ 1 ✘  10.17.0 ⬢   13:20:49   
╰─ detox test -l trace -d --debug-synchronization
detox[39904] INFO:  [test.js] configuration="ios.sim.debug" loglevel="trace" debugSynchronization=3000 reportSpecs=true useCustomLogger=true DETOX_START_TIMESTAMP=1584085894264 node_modules/.bin/jest --config e2e/config.json '--testNamePattern=^((?!:android:).)*$' --maxWorkers 1 "e2e"
detox[39905] INFO:  at e2e/init.js:21:19
 *******************^^^^^^^^^^^^^^^^^^^^$$$$$$$$$$$$$$$$$$$$$$$$$%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%^^^^^^^^^^^^^

detox[39905] TRACE: [Detox.js/DETOX_CREATE] created a Detox instance with config:
{"deviceConfig":{"binaryPath":"ios/build/Build/Products/Debug-iphonesimulator/rippling.app","build":"xcodebuild -project ios/rippling.xcodeproj -scheme rippling -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build","type":"ios.simulator","device":{"type":"iPhone 11 Pro"}},"artifactsConfig":{"rootDir":"artifacts/ios.sim.debug.2020-03-13 07-51-34Z","plugins":{"log":{"enabled":false,"keepOnlyFailedTestsArtifacts":false},"screenshot":{"enabled":true,"shouldTakeAutomaticSnapshots":false,"keepOnlyFailedTestsArtifacts":false},"video":{"enabled":false,"keepOnlyFailedTestsArtifacts":false},"instruments":{"enabled":false,"keepOnlyFailedTestsArtifacts":false},"timeline":{"enabled":false}},"pathBuilder":{"_rootDir":"artifacts/ios.sim.debug.2020-03-13 07-51-34Z"}}}
detox[39905] INFO:  [DetoxServer.js] server listening on localhost:58967...
detox[39905] DEBUG: [AsyncWebSocket.js/WEBSOCKET_OPEN] opened web socket to: ws://localhost:58967
detox[39905] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"login","params":{"sessionId":"ceee7138-7532-bb7d-8f2d-fbad5b7aad73","role":"tester"},"messageId":0}
detox[39905] DEBUG: [DetoxServer.js/LOGIN] role=tester, sessionId=ceee7138-7532-bb7d-8f2d-fbad5b7aad73
detox[39905] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=tester, sessionId=ceee7138-7532-bb7d-8f2d-fbad5b7aad73
detox[39905] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"type":"loginSuccess","params":{"sessionId":"ceee7138-7532-bb7d-8f2d-fbad5b7aad73","role":"tester"},"messageId":0}

detox[39905] DEBUG: [exec.js/EXEC_CMD, #0] applesimutils --list --byType "iPhone 11 Pro"
detox[39905] TRACE: [exec.js/EXEC_SUCCESS, #0] [
  {
    "deviceType" : {
      "name" : "iPhone 11 Pro",
      "bundlePath" : "\/Applications\/Xcode.app\/Contents\/Developer\/Platforms\/iPhoneOS.platform\/Library\/Developer\/CoreSimulator\/Profiles\/DeviceTypes\/iPhone 11 Pro.simdevicetype",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro"
    },
    "state" : "Booted",
    "isAvailable" : true,
    "name" : "iPhone 11 Pro",
    "udid" : "9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269",
    "os" : {
      "buildversion" : "17C45",
      "bundlePath" : "\/Applications\/Xcode.app\/Contents\/Developer\/Platforms\/iPhoneOS.platform\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS.simruntime",
      "isAvailable" : true,
      "name" : "iOS 13.3",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-13-3",
      "version" : "13.3"
    }
  },
  {
    "deviceType" : {
      "name" : "iPhone 11 Pro",
      "bundlePath" : "\/Applications\/Xcode.app\/Contents\/Developer\/Platforms\/iPhoneOS.platform\/Library\/Developer\/CoreSimulator\/Profiles\/DeviceTypes\/iPhone 11 Pro.simdevicetype",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro"
    },
    "state" : "Shutdown",
    "isAvailable" : true,
    "name" : "iPhone 11 Pro",
    "udid" : "92B978D1-86D6-4805-A548-77F9046DEF7C",
    "os" : {
      "buildversion" : "17B102",
      "bundlePath" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 13.2.simruntime",
      "isAvailable" : true,
      "name" : "iOS 13.2",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-13-2",
      "version" : "13.2.2"
    }
  },
  {
    "deviceType" : {
      "name" : "iPhone 11 Pro",
      "bundlePath" : "\/Applications\/Xcode.app\/Contents\/Developer\/Platforms\/iPhoneOS.platform\/Library\/Developer\/CoreSimulator\/Profiles\/DeviceTypes\/iPhone 11 Pro.simdevicetype",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro"
    },
    "state" : "Shutdown",
    "isAvailable" : true,
    "name" : "iPhone 11 Pro",
    "udid" : "3D34B603-D148-48C2-A3F1-0A5CEF1ECEAA",
    "os" : {
      "buildversion" : "17A844",
      "bundlePath" : "\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS 13.1.simruntime",
      "isAvailable" : true,
      "name" : "iOS 13.1",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-13-1",
      "version" : "13.1"
    }
  }
]

detox[39905] DEBUG: [exec.js/EXEC_CMD, #1] applesimutils --list --byId 9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269 --maxResults 1
detox[39905] TRACE: [exec.js/EXEC_SUCCESS, #1] [
  {
    "deviceType" : {
      "name" : "iPhone 11 Pro",
      "bundlePath" : "\/Applications\/Xcode.app\/Contents\/Developer\/Platforms\/iPhoneOS.platform\/Library\/Developer\/CoreSimulator\/Profiles\/DeviceTypes\/iPhone 11 Pro.simdevicetype",
      "identifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro"
    },
    "state" : "Booted",
    "isAvailable" : true,
    "name" : "iPhone 11 Pro",
    "udid" : "9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269",
    "os" : {
      "buildversion" : "17C45",
      "bundlePath" : "\/Applications\/Xcode.app\/Contents\/Developer\/Platforms\/iPhoneOS.platform\/Library\/Developer\/CoreSimulator\/Profiles\/Runtimes\/iOS.simruntime",
      "isAvailable" : true,
      "name" : "iOS 13.3",
      "identifier" : "com.apple.CoreSimulator.SimRuntime.iOS-13-3",
      "version" : "13.3"
    }
  }
]

detox[39905] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBootDevice({ coldBoot: false,
  deviceId: '9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269',
  type: 'iPhone 11 Pro' })
detox[39905] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeUninstallApp({ deviceId: '9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269',
  bundleId: 'com.people.rippling' })
detox[39905] DEBUG: [exec.js/EXEC_CMD, #2] /usr/bin/xcrun simctl uninstall 9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269 com.people.rippling
detox[39905] DEBUG: [exec.js/EXEC_TRY, #2] Uninstalling com.people.rippling...
detox[39905] TRACE: [exec.js/EXEC_SUCCESS, #2]
detox[39905] DEBUG: [exec.js/EXEC_SUCCESS, #2] com.people.rippling uninstalled
detox[39905] DEBUG: [exec.js/EXEC_CMD, #3] /usr/bin/xcrun simctl install 9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269 "/Users/vayu/testReactNative/testDetox/rippling-mobile/ios/build/Build/Products/Debug-iphonesimulator/rippling.app"
detox[39905] DEBUG: [exec.js/EXEC_TRY, #3] Installing /Users/vayu/testReactNative/testDetox/rippling-mobile/ios/build/Build/Products/Debug-iphonesimulator/rippling.app...
detox[39905] TRACE: [exec.js/EXEC_SUCCESS, #3]
detox[39905] DEBUG: [exec.js/EXEC_SUCCESS, #3] /Users/vayu/testReactNative/testDetox/rippling-mobile/ios/build/Build/Products/Debug-iphonesimulator/rippling.app installed
detox[39905] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeTerminateApp({ deviceId: '9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269',
  bundleId: 'com.people.rippling' })
detox[39905] DEBUG: [exec.js/EXEC_CMD, #4] /usr/bin/xcrun simctl terminate 9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269 com.people.rippling
detox[39905] DEBUG: [exec.js/EXEC_TRY, #4] Terminating com.people.rippling...
detox[39905] TRACE: [exec.js/EXEC_SUCCESS, #4]
detox[39905] DEBUG: [exec.js/EXEC_SUCCESS, #4] com.people.rippling terminated
detox[39905] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onTerminateApp({ deviceId: '9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269',
  bundleId: 'com.people.rippling' })
detox[39905] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onBeforeLaunchApp({ bundleId: 'com.people.rippling',
  deviceId: '9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269',
  launchArgs:
   { detoxServer: 'ws://localhost:58967',
     detoxSessionId: 'ceee7138-7532-bb7d-8f2d-fbad5b7aad73' } })
detox[39905] DEBUG: [exec.js/EXEC_CMD, #5] SIMCTL_CHILD_DYLD_INSERT_LIBRARIES="/Users/vayu/Library/Detox/ios/263d0887413cd8a47c05eaf4190d024307b129a1/Detox.framework/Detox" /usr/bin/xcrun simctl launch 9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269 com.people.rippling --args -detoxServer "ws://localhost:58967" -detoxSessionId "ceee7138-7532-bb7d-8f2d-fbad5b7aad73"
detox[39905] DEBUG: [exec.js/EXEC_TRY, #5] Launching com.people.rippling...
detox[39905] TRACE: [exec.js/EXEC_SUCCESS, #5] com.people.rippling: 39945

detox[39905] DEBUG: [exec.js/EXEC_CMD, #6] /usr/bin/xcrun simctl get_app_container 9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269 com.people.rippling
detox[39905] TRACE: [exec.js/EXEC_SUCCESS, #6] /Users/vayu/Library/Developer/CoreSimulator/Devices/9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269/data/Containers/Bundle/Application/F3F545C6-F8E1-4D4D-A3BF-B34621B06F4F/rippling.app

detox[39905] INFO:  [AppleSimUtils.js] com.people.rippling launched. To watch simulator logs, run:
        /usr/bin/xcrun simctl spawn 9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269 log stream --level debug --style compact --predicate 'process == "rippling"'
detox[39945] TRACE: [ArtifactsManager.js/LIFECYCLE] artifactsManager.onLaunchApp({ bundleId: 'com.people.rippling',
  deviceId: '9FD7C5EA-F3B7-4E26-A79E-0A848ADE1269',
  launchArgs:
   { detoxServer: 'ws://localhost:58967',
     detoxSessionId: 'ceee7138-7532-bb7d-8f2d-fbad5b7aad73' },
  pid: 39945 })
detox[39905] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"isReady","params":{},"messageId":-1000}
detox[39905] TRACE: [DetoxServer.js/MESSAGE] role=tester action=isReady (sessionId=ceee7138-7532-bb7d-8f2d-fbad5b7aad73)
detox[39905] DEBUG: [DetoxServer.js/CANNOT_FORWARD] role=testee not connected, cannot fw action (sessionId=ceee7138-7532-bb7d-8f2d-fbad5b7aad73)
detox[39905] DEBUG: [DetoxServer.js/LOGIN] role=testee, sessionId=ceee7138-7532-bb7d-8f2d-fbad5b7aad73
detox[39905] DEBUG: [DetoxServer.js/LOGIN_SUCCESS] role=testee, sessionId=ceee7138-7532-bb7d-8f2d-fbad5b7aad73
detox[39905] INFO:  Example: should have welcome screen
detox[39905] INFO:  Example: should have welcome screen [FAIL]
detox[39905] INFO:  Example: should show hello screen after tap
detox[39905] INFO:  Example: should show hello screen after tap [FAIL]
detox[39905] INFO:  Example: should show world screen after tap
detox[39905] INFO:  Example: should show world screen after tap [FAIL]

 FAIL  e2e/firstTest.spec.js (300.954s)
  Example
    ✕ should have welcome screen (4ms)
    ✕ should show hello screen after tap (1ms)
    ✕ should show world screen after tap (2ms)

  ● Example › should have welcome screen

    Timeout - Async callback was not invoked within the 300000ms timeout specified by jest.setTimeout.Error: Timeout - Async callback was not invoked within the 300000ms timeout specified by jest.setTimeout.

      at mapper (../node_modules/jest-jasmine2/build/queueRunner.js:25:45)

  ● Example › should have welcome screen

    DetoxRuntimeError: Detox instance has not been initialized

    HINT: Make sure to call detox.init() before your test begins

      at MissingDetox.throwError (../node_modules/detox/src/utils/MissingDetox.js:67:11)
      at MissingDetox._defineRequiredProperty (../node_modules/detox/src/utils/MissingDetox.js:8:71)
      at DetoxExportWrapper.(anonymous function).args [as beforeEach] (../node_modules/detox/src/DetoxExportWrapper.js:53:32)
      at DetoxAdapterImpl.beforeEach (../node_modules/detox/runners/jest/DetoxAdapterImpl.js:17:22)

  ● Example › should have welcome screen

    DetoxRuntimeError: Detox instance has not been initialized

    HINT: Make sure to call detox.init() before your test begins

      1 | describe('Example', () => {
      2 |   beforeEach(async () => {
    > 3 |     await device.reloadReactNative();
        |           ^
      4 |   });
      5 |
      6 |   it('should have welcome screen', async () => {

      at MissingDetox.throwError (../node_modules/detox/src/utils/MissingDetox.js:67:11)
      at Object.device (../node_modules/detox/src/utils/MissingDetox.js:46:16)
      at Object._callee$ (firstTest.spec.js:3:11)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at Generator.invoke [as _invoke] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:288:22)
      at Generator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at invoke (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:152:20)
      at ../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:187:11
      at callInvokeWithMethodAndArg (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:186:16)
      at AsyncIterator.enqueue (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:209:13)
      at AsyncIterator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at Object.<anonymous>.runtime.async (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:233:14)
      at Object._callee (firstTest.spec.js:2:14)

  ● Example › should have welcome screen

    DetoxRuntimeError: Detox instance has not been initialized

    HINT: Make sure to call detox.init() before your test begins

       5 |
       6 |   it('should have welcome screen', async () => {
    >  7 |     await expect(element(by.id('welcome'))).toBeVisible();
         |                          ^
       8 |   });
       9 |
      10 |   it('should show hello screen after tap', async () => {

      at MissingDetox.throwError (../node_modules/detox/src/utils/MissingDetox.js:67:11)
      at Object.by (../node_modules/detox/src/utils/MissingDetox.js:46:16)
      at Object._callee2$ (firstTest.spec.js:7:26)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at Generator.invoke [as _invoke] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:288:22)
      at Generator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at invoke (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:152:20)
      at ../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:187:11
      at callInvokeWithMethodAndArg (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:186:16)
      at AsyncIterator.enqueue (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:209:13)
      at AsyncIterator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at Object.<anonymous>.runtime.async (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:233:14)
      at Object._callee2 (firstTest.spec.js:6:36)

  ● Example › should show hello screen after tap

    Timeout - Async callback was not invoked within the 300000ms timeout specified by jest.setTimeout.Error: Timeout - Async callback was not invoked within the 300000ms timeout specified by jest.setTimeout.

      at mapper (../node_modules/jest-jasmine2/build/queueRunner.js:25:45)

  ● Example › should show hello screen after tap

    DetoxRuntimeError: Detox instance has not been initialized

    HINT: Make sure to call detox.init() before your test begins

      at MissingDetox.throwError (../node_modules/detox/src/utils/MissingDetox.js:67:11)
      at MissingDetox._defineRequiredProperty (../node_modules/detox/src/utils/MissingDetox.js:8:71)
      at DetoxExportWrapper.(anonymous function).args [as beforeEach] (../node_modules/detox/src/DetoxExportWrapper.js:53:32)
      at DetoxAdapterImpl.beforeEach (../node_modules/detox/runners/jest/DetoxAdapterImpl.js:17:22)

  ● Example › should show hello screen after tap

    DetoxRuntimeError: Detox instance has not been initialized

    HINT: Make sure to call detox.init() before your test begins

      1 | describe('Example', () => {
      2 |   beforeEach(async () => {
    > 3 |     await device.reloadReactNative();
        |           ^
      4 |   });
      5 |
      6 |   it('should have welcome screen', async () => {

      at MissingDetox.throwError (../node_modules/detox/src/utils/MissingDetox.js:67:11)
      at Object.device (../node_modules/detox/src/utils/MissingDetox.js:46:16)
      at Object._callee$ (firstTest.spec.js:3:11)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at Generator.invoke [as _invoke] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:288:22)
      at Generator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at invoke (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:152:20)
      at ../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:187:11
      at callInvokeWithMethodAndArg (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:186:16)
      at AsyncIterator.enqueue (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:209:13)
      at AsyncIterator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at Object.<anonymous>.runtime.async (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:233:14)
      at Object._callee (firstTest.spec.js:2:14)

  ● Example › should show hello screen after tap

    DetoxRuntimeError: Detox instance has not been initialized

    HINT: Make sure to call detox.init() before your test begins

       9 |
      10 |   it('should show hello screen after tap', async () => {
    > 11 |     await element(by.id('hello_button')).tap();
         |                   ^
      12 |     await expect(element(by.text('Hello!!!'))).toBeVisible();
      13 |   });
      14 |

      at MissingDetox.throwError (../node_modules/detox/src/utils/MissingDetox.js:67:11)
      at Object.by (../node_modules/detox/src/utils/MissingDetox.js:46:16)
      at Object._callee3$ (firstTest.spec.js:11:19)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at Generator.invoke [as _invoke] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:288:22)
      at Generator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at invoke (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:152:20)
      at ../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:187:11
      at callInvokeWithMethodAndArg (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:186:16)
      at AsyncIterator.enqueue (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:209:13)
      at AsyncIterator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at Object.<anonymous>.runtime.async (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:233:14)
      at Object._callee3 (firstTest.spec.js:10:44)

  ● Example › should show world screen after tap

    Timeout - Async callback was not invoked within the 300000ms timeout specified by jest.setTimeout.Error: Timeout - Async callback was not invoked within the 300000ms timeout specified by jest.setTimeout.

      at mapper (../node_modules/jest-jasmine2/build/queueRunner.js:25:45)

  ● Example › should show world screen after tap

    DetoxRuntimeError: Detox instance has not been initialized

    HINT: Make sure to call detox.init() before your test begins

      at MissingDetox.throwError (../node_modules/detox/src/utils/MissingDetox.js:67:11)
      at MissingDetox._defineRequiredProperty (../node_modules/detox/src/utils/MissingDetox.js:8:71)
      at DetoxExportWrapper.(anonymous function).args [as beforeEach] (../node_modules/detox/src/DetoxExportWrapper.js:53:32)
      at DetoxAdapterImpl.beforeEach (../node_modules/detox/runners/jest/DetoxAdapterImpl.js:17:22)

  ● Example › should show world screen after tap

    DetoxRuntimeError: Detox instance has not been initialized

    HINT: Make sure to call detox.init() before your test begins

      1 | describe('Example', () => {
      2 |   beforeEach(async () => {
    > 3 |     await device.reloadReactNative();
        |           ^
      4 |   });
      5 |
      6 |   it('should have welcome screen', async () => {

      at MissingDetox.throwError (../node_modules/detox/src/utils/MissingDetox.js:67:11)
      at Object.device (../node_modules/detox/src/utils/MissingDetox.js:46:16)
      at Object._callee$ (firstTest.spec.js:3:11)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at Generator.invoke [as _invoke] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:288:22)
      at Generator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at invoke (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:152:20)
      at ../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:187:11
      at callInvokeWithMethodAndArg (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:186:16)
      at AsyncIterator.enqueue (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:209:13)
      at AsyncIterator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at Object.<anonymous>.runtime.async (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:233:14)
      at Object._callee (firstTest.spec.js:2:14)

  ● Example › should show world screen after tap

    DetoxRuntimeError: Detox instance has not been initialized

    HINT: Make sure to call detox.init() before your test begins

      14 |
      15 |   it('should show world screen after tap', async () => {
    > 16 |     await element(by.id('world_button')).tap();
         |                   ^
      17 |     await expect(element(by.text('World!!!'))).toBeVisible();
      18 |   });
      19 | });

      at MissingDetox.throwError (../node_modules/detox/src/utils/MissingDetox.js:67:11)
      at Object.by (../node_modules/detox/src/utils/MissingDetox.js:46:16)
      at Object._callee4$ (firstTest.spec.js:16:19)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at Generator.invoke [as _invoke] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:288:22)
      at Generator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at tryCatch (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:62:40)
      at invoke (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:152:20)
      at ../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:187:11
      at callInvokeWithMethodAndArg (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:186:16)
      at AsyncIterator.enqueue (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:209:13)
      at AsyncIterator.prototype.(anonymous function) [as next] (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
      at Object.<anonymous>.runtime.async (../node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:233:14)
      at Object._callee4 (firstTest.spec.js:15:4

My Detox Configurations:
"detox": {
    "test-runner": "jest",

    "configurations": {
      "ios.sim.debug": {
        "binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/rippling.app",
        "build": "xcodebuild -project ios/rippling.xcodeproj -scheme rippling -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build",
        "type": "ios.simulator",
        "device": {
          "type": "iPhone 11 Pro"
        }
      }
    }
  }

Environment:
Detox: 15.4.2
React Native: 0.59.10
Node: v10.17.0
Device: ios simulator, any model
Xcode: 11.3
iOS: 13.3
P.S:
I have even tried to run local detox server and pass the server details in config\
detox[33506] INFO:  [DetoxServer.js] server listening on localhost:8099...

with configuration
"detox": {
    "test-runner": "jest",

    "configurations": {
      "ios.sim.debug": {
        "binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/rippling.app",
        "build": "xcodebuild -project ios/rippling.xcodeproj -scheme rippling -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build",
        "type": "ios.simulator",
        "device": {
          "type": "iPhone 11 Pro"
        },
        "session": {
          "server": "ws://localhost:8099",
          "sessionId": "test"
        }
      }
    }
  }

Why is this issue labeled as a "questions for stackoverflow". I followed the docs on GitHub and ran into the exact same issue. The app builds fine but the tests do not run with Jest.
This is either a bug or should be addressed in the documentation.

the bot detected it as a question rather than a bug, also did the same for issue #1943.
please find the StackOverflow question for reference and follow up, as of today no correct solution for the issue.
https://stackoverflow.com/questions/60538614/detoxruntimeerrordetox-instance-has-not-been-initialized

Thanks for the quick response! I have seen the question on StackOverflow. It is using mocha instead of Jest.
I am not trying to run the tests with mocha to see if I run into the same issue. The StackOverflow question changed the firstTest.spec.js code, I am using the scaffolding detox provides itself.

FYI mocha gives error as well.
detox[75855] INFO:  [test.js] node_modules/.bin/mocha --opts e2e/mocha.opts --configuration ios.sim.debug --grep :android: --invert --use-custom-logger "true" "e2e"
detox[75856] ERROR: at internal/process/warning.js:27:3
 (node:75856) DeprecationWarning: Configuration via mocha.opts is DEPRECATED and will be removed from a future version of Mocha. Use RC files or package.json instead.

detox[75856] INFO:  [DetoxServer.js] server listening on localhost:62421...
detox[75856] INFO:  [AppleSimUtils.js] com.numuworld.Numu launched. To watch simulator logs, run:
        /usr/bin/xcrun simctl spawn F6C9D959-A42F-48AD-99EF-4382EB8FECDB log stream --level debug --style compact --predicate 'process == "numu"'
  1) "before all" hook in "{root}"

  0 passing (2m)
  1 failing

  1) "before all" hook in "{root}":
     Error: Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
      at listOnTimeout (internal/timers.js:531:17)
      at processTimers (internal/timers.js:475:7)

@AmarnathN @LeoNatan figured out my issue!
I am using react-native-splash-screen which was the cause of the issue! The same issue is also reported (here)[https://github.com/wix/detox/issues/400#issuecomment-361530205] and (here)[https://github.com/crazycodeboy/react-native-splash-screen/issues/463#issue-568040385].
Solution
In your AppDelegate.mfile, we amended the codem inside - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions method;
#if RELEASE
    [RNSplashScreen show];  // show splash screen if config is RELEASE only for Detox E2E tests
  #endif

Please note that Detox tests should normally be run in release mode.
The error here is unfortunate, but it's masking the actual underlying issue of launch not happening fast enough.
We are working on a fix that will remove these "instance not initialized" errors, and it will hopefully make it easier to find these issues in the future:
https://github.com/wix/Detox/pull/1929

Our own react-native-navigation framework handles splashscreens much better, as well as offer proper native navigation solution. Consider using that.


Add machine-readable cpes

It would be useful to have a column for machine-readable cpe's for each affected product version.

@epicfaace  thank you for this suggestion.  We will certainly take it into consideration.

@justmurphy thanks. This would especially useful in order to sync what's on this repository with the list of affected cpes on NVD (https://nvd.nist.gov/vuln/detail/CVE-2021-44228). This would also help https://github.com/cisagov/crossfeed, which depends on NVD's cpe-to-cve mapping to detect vulnerability, better detect CVE-2021-44228.

@epicfaace I agree that we need to move into the machine-readable direction. However, creating CPEs is not as easy as one would think. Just have a look at some CPEs for Siemens products. Therefore, if the advisory doesn't list them it is probably not safe to use them.
The Common Security Advisory Framework CSAF aims at that underlying problem that security advisories are currently only human-readable. It uses a standardized JSON structure which can be parsed automatically. It also provides the vendor to add several product_identification_helpers, including but not limited to CPE, purl, SBOM references, hashes and serial numbers.
Moreover, it has a profile for the Vulnerability Exploitability eXchange (VEX). Using that, suppliers can state that their product is NOT vulnerable.

However, creating CPEs is not as easy as one would think.

@tschmidtb51 interesting, thanks for sharing. To be clear, what exactly is the problem with CPEs you're referring to? Is it just that some existing CPEs aren't specific enough?

To be clear, what exactly is the problem with CPEs you're referring to? Is it just that some existing CPEs aren't specific enough?

@epicfaace I think there are multiple problems:

some existing CPEs aren't specific enough
multiple CPEs exist for one product (just have a look here, and here or here)
CPEs do not exist for all products
naming is hard - especially, if you are not the vendor (which then results in the problem that I described in 2)

Therefore: If you are a vendor and CPEs work for you, feel free to/please include them into your (machine-readable) advisories. If not, please provide another way for your customers to match on products in their asset database automatically.

Yes, thanks!

@epicfaace & @tschmidtb51 thank you for the input.  Closing this issue.


textarea placeholder is set into textarea value (IE11)

Vue.js version
2.0.3
Reproduction Link
https://jsfiddle.net/wxw3aa86/1/

It seems this is a bug in IE11:
https://connect.microsoft.com/IE/feedback/details/811408
We'll have to see if there is a way to work around this bug.

If this is a BUG
web-runtime-with-compiler.js#L67
Then here can not directly use outerHTML, is it?

The IE bug happens with both innerHTML and outerHTML
We use outerHTML to get the in-DOM template, this is not really a functionality we can replace.

@LinusBorg I know...I need to find the core members confirm, and then fix it....


Changing config values

I see that Kconfig was removed.  Is there currently a good way to modify config values without changing the espmqtt source?

Yes please restore the Kconfig.

@kylehendricks , you can also config in your main component.mk by adding for example CPPFLAGS += -DMQTT_MAX_PASSWORD_LEN=64

Check this: https://github.com/tuanpmt/espmqtt/commit/0d4d269dc357c51bb53070779da37b3c5ddadaf3


Issue with missing sass-loader and node-sass

I'm using Postcss and when trying to use the component I've issue on the build requesting sass-loader and node-sass dependencies.

npm install node-sass
npm install sass-loader


Envs.Elide cannot be reduced for uninhabitable intersections

When I try to compile the following:
val effect: Unit < Envs[String & Int & Boolean] = ???
val provided: Unit < Envs[Int & Boolean] = Envs[String].run("string")(effect)

I get the following error:
[error]     |                  Found:    Unit < kyo.Envs.Elide[Int & Boolean]
[error]     |                  Required: Unit < kyo.Envs[Int & Boolean]
[error]     |
[error]     |                  Note: a match type could not be fully reduced:
[error]     |
[error]     |                    trying to reduce  kyo.Envs.Elide[Int & Boolean]
[error]     |                    failed since selector Int & Boolean
[error]     |                    is uninhabited (there are no values of that type).

It looks like the issue is that match types won't reduce when it recognizes that type intersection being matched is uninhabitable (there cannot be a value of that type). Since this will frequently be the case for Envs intersections, I don't think match types will work here.
I see two alternatives:

Make Envs contravariant with E so that types are tracked by union rather than intersection.
Use a type class with an inner (dependent) type to derive the "remainder"

thanks for the report! I agree with making Envs contravariant. I also noticed this other bug with the new encoding: https://github.com/getkyo/kyo/issues/215

I personally don't see the value of using union types in the Env. Happy to try my hand at a PR this week.

My preference is for approach 2. In general, I've found match types don't work super well and I wouldn't recommend making decisions around them. I would only use unions in those cases where it makes semantic sense, like aborts.
Deriving the remainder of a dependency intersection is not too complicated (from discord):
type HasEnv[E, ES]:
  type Out

trait LowPriorityHasEnvs:
  given hasEnv[E, ER]: HasEnv[E, E & ER] with
    type Out = Envs[ER]

object HasEnv extends LowPriorityHasEnvs:
  given isEnv[E]: HasEnv[E, E] with
    type Out = Any

For visibility: we had a discussion on this topic yesterday reached a conclusion that using different variances for Envs and Aborts is necessary for soundness, so we'd need something like approach 2.
Thank you for your wisdom here @johnhungerford! If this change ends up making the match type not necessary anymore, I think we should try to move back to Scala 3.3 since 3.4 isn't an LTS release. Elide only worked on 3.4.

@hearnadam @johnhungerford would one of you be able to pick this up? I wanted to cut a new release and it'd be nice to have this fixed for it.

@fwbrasil I'll take a stab at it

fixed by https://github.com/getkyo/kyo/pull/240


Refactor project structure. FIx Compile Remove / Compile Include

@doboczyakos and @davidnemeti Can you take a look at this PR?
I still needed to fix some things.

I think the build error is because of the portable-net40+win8+wpa81+wp8+sl5 and portable-net45+win8+wpa81+wp8 target frameworks. You should consider removing them. In my opinion no other modifications are needed.

Changing back the LinqKit.Core namespace to LinqKit containing the AsExpandable extension will cause build error 'The call is ambiguous between the following methods or properties' if you have reference to both LinqKit.Core and LinqKit packages

LinqKit.EntityFramework.Tests.Net452.DbAsyncTests.DbAsync_EnumerateShouldWorkAsync [FAIL]
This is because AsExpandable() was called from LinqKit.Core instead of LinqKit. That's why we moved it to a new namespace to avoid the 'ambiguous call' build error and stay compatible when someone calls AsExpandable on an EF or EF Core IQueryable.
In that rare case when someone used AsExpandable from LinqKit.Core this is a breaking change but it can be simply resolved by adding 'using LinqKit.Core;'

Build is build.
However these changes:

Are still needed, because you don;t need to include source files anymore because we now include a project (LinqKit.Core)

Some files (ExpandableQuery, Extensions) are still needed that's why I've added #if NOEF to the beginning of appropriate files.

@doboczyakos
I think all is correctly fixed, can you check ?

@doboczyakos
I think all is correctly fixed, can you check ?

Seems great. Thanks.


Best practices when multiple Leaflet libraries are loaded

Users of Jupyter Notebooks and JupyterLab are running into problems when using multiple extensions that each try to load their own Leaflet libraries.
Examples:
https://github.com/jupyter-widgets/ipyleaflet/issues/337
https://github.com/jupyter-widgets/ipyleaflet/issues/294
I tried this as a solution here:
https://github.com/jupyter-widgets/ipyleaflet/pull/295
which fixed the problem in my Jupyter Notebooks use case but did not work in the case of the 337 issue above. It is not known if this is due to 337 using JupyterLab versus Jupyter or something else, such as the extension loading order.
Most problems see to revolve around plugins disappearing, so for example the first Leaflet load adds the Leaflet.Draw extension, then the second Leaflet loaded takes over the L global and the extension can't be found.
Both extensions are using require to load Leaflet.
Is there a pattern that Jupyter extension developers can adopt to load Leaflet safely that isolates each library?

I think the problem resides not in the several Leaflet instance, but in how the plugins (i.e. Leaflet Draw) attach themselves to the Leaflet instance.
Most plugins are written in such a way that they assume the L global variable to be defined (or window.L). That's the case of Leaflet.Draw, which code starts with L.drawVersion = "1.x" - that assignment assumes that Leaflet is available as a global variable.
Any other pattern would make plugins more cumbersome to develop and load :-|

Is there a pattern that Jupyter extension developers can adopt to load Leaflet safely that isolates each library?

There are a couple dirty javascript tricks that can be useful:

Shamelessly reassign the L global to the "active" instance before loading a plugin
Add more tooling to wrap the plugin code in a IIFE, kinda:

var myLeafletInstance = require('leaflet');
(function(L) {
    /* plugin code goes here */
})(myLeafletInstance);

There's nothing that we can do in core Leaflet to improve this, short of revamping the whole architecture and taking on the maintenance of plugins :-(


Triage finschia-sdk#345

The subject of the triage:

Finschia/finschia-sdk#345

They delete this ci because it was never triggered. related cosmos/cosmos-sdk#13361
But we has changed the trigger, so it sometimes works...
I think it is necessary, maybe in Finschia/cosmos-sdk


Logs aren't streamed to CloudWatch

Hello together,
I'm using this config file: https://github.com/awsdocs/elastic-beanstalk-samples/blob/master/configuration-files/aws-provided/instance-configuration/logs-streamtocloudwatch-linux.config
and this config file:
## set up custom logging for nginx and php-fpm

packages:
  yum:
    awslogs: []

files:
  "/etc/awslogs/awscli.conf":
    mode: "000600"
    owner: root
    group: root
    content: |
      [plugins]
      cwlogs = cwlogs
      [default]
      region = `{"Ref":"AWS::Region"}`

  "/etc/awslogs/awslogs.conf":
    mode: "000600"
    owner: root
    group: root
    content: |
      [general]
      state_file = /var/lib/awslogs/agent-state

files:
  "/etc/awslogs/config/logs.conf":
    mode: "000600"
    owner: root
    group: root
    content: |
      [/var/php-fpm/7.1/error.log]
      log_group_name = `{"Fn::Join":["/", ["/aws/elasticbeanstalk", { "Ref":"AWSEBEnvironmentName" }, "var/log/php-fpm/7.1/error.log"]]}`
      log_stream_name = {instance_id}
      file = /var/log/php-fpm/7.1/error.log

      [/var/log/nginx/access.log]
      log_group_name = `{"Fn::Join":["/", ["/aws/elasticbeanstalk", { "Ref":"AWSEBEnvironmentName" }, "var/log/nginx/access.log "]]}`
      log_stream_name = {instance_id}
      file = /var/log/nginx/access.log

      [/var/log/nginx/error.log]
      log_group_name = `{"Fn::Join":["/", ["/aws/elasticbeanstalk", { "Ref":"AWSEBEnvironmentName" }, "var/log/nginx/error.log "]]}`
      log_stream_name = {instance_id}
      file = /var/log/nginx/error.log

commands:
  "01":
    command: chkconfig awslogs on
  "02":
    command: service awslogs restart

But CloudWatch doesn't show up any of these logs. May there be some security settings that I've missed?
If I ssh into my instances and running sudo service awslogs status, everything seems fine: awslogs (pid  13278) is running...

I have same error,
How to solve it please?

@soulpresidente make sure your IAM role for your EBS environment is allowed to create log groups or\and log group streams.
By default, the name for IAM role is aws-elasticbeanstalk-ec2-role.
You can add CloudWatchLogsFullAccess policy just to test if the problem with permissions.


CoAPServer?

I cannot find any code for the server - is this another repo?

Sorry but the server implementation is on hold right now. I removed the information from the readme to avoid confusion.


QtGraphicalEffects module is missing and renders some SDDM Themes unusable.

Describe the package
I'd like to request the package qt5-qtgraphicaleffects because there are some SDDM themes like Sugar Candy or the Sugar Candy-based Tokyo-Night which make use of some effects and since it is missing, SDDM cannot load it as seen in this picture:

For the specific image, I'm choosing Nvidia as that's what I currently use, but the Standard Desktop KDE image should also get this package added, as it's unrelated to Nvidia or AMD.
Image
Nvidia

its already in the image though?

When I tried to do rpm-ostree earlier today, I saw it is marked as an inactive request. Perhaps that's what causes it?

I just found out that SDDM now uses Qt6 instead of Qt5, rendering all Qt5 themes unusable. I checked it with Sugar Eucalyptus Drop and it works. So it's not an issue in Bazzite but with the themes I tried. Closing this issue - sorry for wasting your time.


v2podman ps revert structure changes

reverting name changes to the listcontainer structure because it negatively impacted the direct consumption of the restful API.  instead we now use a local structure in the CLI to modify the output as needed.
Signed-off-by: Brent Baude<EMAIL_ADDRESS>

LGTM

/lgtm
/hold

Thanks, now it is usable as it was before. LGTM

/lgtm

/hold cancel


MdDialog component is not a "child component" of the component from which it is opened

Bug, feature request, or proposal:
Bug
What is the expected behavior?
MdDialog component should be a "child component" of the component from which it opens, so it has access to providers defined in this "parent component"
What is the current behavior?
MdDialog component has no access to providers defined in a component from which it is opened
What are the steps to reproduce?
https://plnkr.co/edit/ZvFMiG?p=preview
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

That's what the viewContainerRef option is for. Here's a forked Plunkr: https://plnkr.co/edit/vV2UGXong406SV9apPPH?p=preview

@crisbeto perfect, thank you!


Mapping OutputDataset to TaskName

in case of step/task chain, what is the best way to get
{
"Task1": ["output1"],
"Task2":[].
...
}
type of dictionnary ?

It seems we don't store OutputDataset by Task in reqmgr couch db. Only the list of Outdatasets for the whole workflow. Is there any correlation between task name and output datasets?
You can query like following to get the list separately.  (real task name, not Task1, etc)
https://cmsweb.cern.ch/wmstatsserver/data/filtered_requests?RequestStatus=running-closed&RequestType=TaskChain&mask=OutputDatasets&mask=TaskName

is there a way to get this from the "spec" https://cmsweb.cern.ch/reqmgr2/config?name=pdmvserv_task_BPH-PhaseIISpring17GS-00004__v1_T_170621_142219_4260 ?

This information is not stored anywhere but in the internals (object wise) of the workload. Each request has a list of output datasets. Said that, the only way to figure that out is coding against the WMCore libraries (and I'd rather keep it like that unless there is a very good reasoning behind it).

is there a chance to have this as an api ? or have it in the workload cache ?
For several operational things, it is mandatory to be able to do the mapping task/step <=> output.

Jean-Roch, can you please list and explain what are those use cases? Maybe we can accomplish what you need with existent apis/tools.

in essence I want to know the campaign of the task per output dataset.

I was able to do this going through the spec
https://cmsweb.cern.ch/reqmgr2/config?name=pdmvserv_task_HIG-RunIISummer15wmLHEGS-01262__v1_T_170906_162107_4411
and the subscriptions attributes
pdmvserv_task_HIG-RunIISummer15wmLHEGS-01262__v1_T_170906_162107_4411.tasks.HIG-RunIISummer15wmLHEGS-01262_0.subscriptions.RAWSIMoutput.dataset = '/ChargedHiggs_HplusTB_HplusToTauNu_IntermediateMassNoNeutral_M-200_13TeV_amcatnlo_pythia8/RunIISummer15wmLHEGS-MCRUN2_71_V1-v1/GEN-SIM'
for example.

Alan is working on the StepChain mapping, https://github.com/dmwm/WMCore/pull/8697
We will try to do the same way for TaskChain.


[Task]: The queries tab is not attention grabbing enough, and users click on the data tab rather than on the Queries tab

SubTasks
Emphasise queries rather than de-emphasize the datasources tab.

[ ] show the number of queries.
[ ] Increase the font-weight of the text.

@vinay-appsmith @momcilo-appsmith Can we get an indication of the font-weight we should use for this

Add a count next to the queries, JS, UI to reflect the number of entities. Font-weight changes to 500 in the segmented control.
from: @vinay-appsmith

Closing this in favor of #37881


Error reading the simtel MC shower on certain files

Related discussion: https://github.com/cta-observatory/ctapipe/pull/1447
This seems to happen at selected events only.
In this case I used the ctapipe-stage1-tool on the  proton_20deg_180deg_run2867___cta-prod3-demo-2147m-LaPalma-baseline.simtel.gz file of the Prod3-Benchmark data.

ERROR [Stage1ProcessorTool] (tool/run): Caught unexpected exception: unpack requires a buffer of 4 bytes
Traceback (most recent call last):
File "/net/nfshome/home/lnickel/ctapipe/ctapipe/core/tool.py", line 225, in run
self.start()
File "/net/nfshome/home/lnickel/ctapipe/ctapipe/tools/stage1.py", line 685, in start
self._process_events(writer)
File "/net/nfshome/home/lnickel/ctapipe/ctapipe/tools/stage1.py", line 468, in _process_events
for event in tqdm(
File "/home/lnickel/conda/envs/ctapipe_study/lib/python3.8/site-packages/tqdm/std.py", line 1152, in iter
for obj in iterable:
File "/net/nfshome/home/lnickel/ctapipe/ctapipe/io/eventsource.py", line 254, in iter
for event in self._generator():
File "/net/nfshome/home/lnickel/ctapipe/ctapipe/io/simteleventsource.py", line 338, in _generator
yield from self._generate_events()
File "/net/nfshome/home/lnickel/ctapipe/ctapipe/io/simteleventsource.py", line 355, in generate_events
for counter, array_event in enumerate(self.file):
File "/home/lnickel/conda/envs/ctapipe_study/lib/python3.8/site-packages/eventio/simtel/simtelfile.py", line 239, in iter_array_events
self.next_low_level()
File "/home/lnickel/conda/envs/ctapipe_study/lib/python3.8/site-packages/eventio/simtel/simtelfile.py", line 144, in next_low_level
self.current_mc_shower = o.parse()
File "/home/lnickel/conda/envs/ctapipe_study/lib/python3.8/site-packages/eventio/simtel/objects.py", line 1326, in parse
mc['cmax'] = read_float(byte_stream)
File "/home/lnickel/conda/envs/ctapipe_study/lib/python3.8/site-packages/eventio/tools.py", line 28, in read_float
return struct.unpack('<f', f.read(4))[0]
struct.error: unpack requires a buffer of 4 bytes

30 showers are written out, namely the ones with the event ids:

[ 30702,  30708,  30710,  30714,  48511,  69307,  73111,  77412,
124012, 158805, 192905, 193006, 193008, 193011, 221117, 262605,
262607, 262612, 262615, 321900, 321915, 334709, 364504, 399713,
435313, 447603, 447615, 461901, 502002, 502009]

I think the download just failed in the middle of the file.

Yes, the file on our server has 21MB (should be several GB)

But one more error to catch in next


Paynym retrieve error when using Tor proxy

With version 1.5.3 (and the beta) I get an error when trying to retrieve my PayNym while using a Tor proxy. The error is as follows:
2021-12-09 09:46:24,864 ERROR Error retrieving PayNym
com.samourai.wallet.api.backend.beans.HttpException: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused
	at com.sparrowwallet.nightjar@0.2.24/com.samourai.http.client.JacksonHttpClient$2.call(Unknown Source)
	at com.sparrowwallet.nightjar@0.2.24/com.samourai.http.client.JacksonHttpClient$2.call(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/io.reactivex.internal.operators.observable.ObservableFromCallable.subscribeActual(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/io.reactivex.Observable.subscribe(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/io.reactivex.internal.operators.observable.ObservableSubscribeOn$SubscribeTask.run(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/io.reactivex.Scheduler$DisposeTask.run(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/io.reactivex.internal.schedulers.ScheduledRunnable.run(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/io.reactivex.internal.schedulers.ScheduledRunnable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.client.util.FutureResponseListener.getResult(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.client.util.FutureResponseListener.get(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.client.HttpRequest.send(Unknown Source)
	at com.sparrowwallet.nightjar@0.2.24/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJson(Unknown Source)
	at com.sparrowwallet.nightjar@0.2.24/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJsonPost(Unknown Source)
	at com.sparrowwallet.nightjar@0.2.24/com.samourai.http.client.JacksonHttpClient$1.call(Unknown Source)
	... 13 common frames omitted
Caused by: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.io.SelectorManager.doFinishConnect(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.io.ManagedSelector.processConnect(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.io.ManagedSelector.access$1500(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.io.ManagedSelector$SelectorProducer.processSelected(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.io.ManagedSelector$SelectorProducer.produce(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produceTask(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produce(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(Unknown Source)
	at com.sparrowwallet.merged.module@1.5.3/org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(Unknown Source)
	... 1 common frames omitted

It fails right away, so it's not a Tor latency issue. When I disable the Tor proxy (in the server configuration) the PayNym retrieval works.

Strange - it's working on this side through Tor right now. PayNym.is is one of the few Samourai services not available as an .onion address, so there might be something in breaking out of a Tor exit node on your side. Odd that it fails immediately though. Is this with the internal Sparrow Tor proxy or an external one?

It's with an external Tor proxy.
How does one turn on the internal Tor proxy? I've been using an external one thinking Sparrow didn't come with one.

You need to connect to your Electrum server through a .onion address, have the proxy setting disabled, and the external Tor shutdown if running on port 9050. Not that I think it make much difference to the issue, but might be worth trying.

Any further progress on this? I don't believe it's a Sparrow issue (it would have been reported elsewhere if so by now).

I was unable to change the proxy's port on the external Tor. Something is not working properly with the NixOS module that configures Tor. And that Tor instance is used by my bitcoind node, which is in turn used by Sparrow. I suppose I'll just turn off the Tor proxy in Sparrow.

For what it's worth, today retrieving the Paynym worked using the same external Tor. I tried the Tools -> Show Paynym feature in 1.5.5 and it worked. About an hour later I tried it again, just for kicks and giggles, and it failed. Right away I pushed the button to retry and it worked :)

I've also seen this kind of intermittent issue. I think the best solution is to have paynym.is exposed as a hidden service, which should remove the need for Tor exit nodes. Samourai are implementing this.

Had the same problem but from one moment to the other it started to work again. So I think not a Sparrow issue. I leave the log here nevertheless. It seems to differ a little bit from the posted one above, so I don't know if it adds some value.
2022-03-17 10:35:10,255 ERROR [JavaFX Application Thread] c.s.s.p.PayNymController [null:-1] Error retrieving PayNym
com.samourai.wallet.api.backend.beans.HttpException: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused
	at com.sparrowwallet.nightjar@0.2.32/com.samourai.http.client.JacksonHttpClient$2.call(Unknown Source)
	at com.sparrowwallet.nightjar@0.2.32/com.samourai.http.client.JacksonHttpClient$2.call(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/io.reactivex.internal.operators.observable.ObservableFromCallable.subscribeActual(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/io.reactivex.Observable.subscribe(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/io.reactivex.internal.operators.observable.ObservableSubscribeOn$SubscribeTask.run(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/io.reactivex.Scheduler$DisposeTask.run(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/io.reactivex.internal.schedulers.ScheduledRunnable.run(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/io.reactivex.internal.schedulers.ScheduledRunnable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.client.util.FutureResponseListener.getResult(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.client.util.FutureResponseListener.get(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.client.HttpRequest.send(Unknown Source)
	at com.sparrowwallet.nightjar@0.2.32/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJson(Unknown Source)
	at com.sparrowwallet.nightjar@0.2.32/com.sparrowwallet.nightjar.http.JavaHttpClient.requestJsonPost(Unknown Source)
	at com.sparrowwallet.nightjar@0.2.32/com.samourai.http.client.JacksonHttpClient$1.call(Unknown Source)
	... 13 common frames omitted
Caused by: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
	at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.io.SelectorManager.doFinishConnect(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.io.ManagedSelector.processConnect(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.io.ManagedSelector.access$1500(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.io.ManagedSelector$SelectorProducer.processSelected(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.io.ManagedSelector$SelectorProducer.produce(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produceTask(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produce(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(Unknown Source)
	at com.sparrowwallet.merged.module@1.6.1/org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(Unknown Source)
	... 1 common frames omitted


Troubleshooting Install Dev

This provides some help in case the installation for developers fails (happened recently to me).

Yeah you are right - I actually first looked for the troubleshooting page by using the search function of the docs

which does not show that page - thus I assumed it is not there.


Sai mct

S2S changes

@v-sambati : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Docs Build status updates of commit 9d9cb91:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-community-training/rest-api-management/service-to-service-authentication.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


KeyError: 'weight' in method assign_weight_vector

Issue due to repetitive weights, if changed threshold value, so more records are retained this works fine.


feat: set prisma-fmt in VSCode options

closes #235

That's what the output looks like in case the setting was initially set with a path to a prisma-fmt binary and then deleted.

What happens if the user supplied an invalid path that would break the functionality?

What happens if the user supplied an invalid path that would break the functionality?

Currently the binary test would then fail, which would show up in the output, and after another try of the binary test, the Language Server will crash.  (Still need to find a better way to handle this)


Add Flotiq integration

Description
This MR introduces documentation for integrating Flotiq headless CMS with Astro, offering developers a guide to enriching their Astro projects with dynamic content from Flotiq.
It covers prerequisites, setting up content types in Flotiq, and connecting Astro components to Flotiq data, complete with code snippets and steps to display blog posts fetched from Flotiq.

Hello, could you please take a look at this MR when you have a moment? Thank you! :)

Hi @TheOtterlord. Thanks for the review! I've applied your suggestions and replied to your comment. I'd appreciate it if you could check it again.

Thanks! I'm out of town at the moment, but I'll be back on Saturday to review the new version.

Hi, it has been a few weeks and there has been no response to the request for more details about fetching data.
And, the example provided has a lot going on here that should not be in a minimal example. I don't think this makes it obvious how to use Flotiq and instead makes this difficult to follow: there's an extra, unnecessary date component, posts is defined twice, once fetching from content collections and once fetching from Flotiq, there's a debug statement.
This doesn't meet our standards for a helpful guide, and especially with no recent response from the PR reviewer, I'll be closing this PR.


Share more code between tasks, Maven and Gradle

Trying to share more code while retaining the current structure. I don't intend to radically change the current design in this PR, so this is largely moving around code.

PluginConfigurationProcessor configures both Containerizer and JibContainerBuilder.

Previously, tasks will need to create a TargetImage and a Containizer after calling PCP, and then call another PCP method to configure Containerizer.
Now, each task will call one of process...ForDockerDaemonImage, ...ForTarImage, or ...ForRegistryImage.

Shares the target image ref generation code.
Shares the code to add credential retrievers for adding the <from> and <to> auth info. (See configureCredentialRetrievers)

Looks great! This removed a lot of redundancy. I'll have someone else do the second pass and approval.


PhoneNumberOfflineGeocoder in javascript port?

Hi -- it seems the PhoneNumberOfflineGeocoder isn't available in the javascript version, and thus not available to nodejs, websites, etc.
Can it please be ported?
Thanks!

We don't plan on porting this, because the vast amount of geocoding data means the size would be prohibitive. I would imagine you would rather want to solve this via a service which JS can call. We don't have any plans to create such a service, but you could use the Java or C++ libraries to create a service yourself.

I use it client-side with https://github.com/jackocnr/intl-tel-input
But even so, I use a small port to run with nodejs here: https://github.com/seegno/google-libphonenumber so I currently run the entire libphone server side.

The entire geocoding folder is about 11mb with all the languages, which gzips to about 2mb... much bigger than the basic utils of 200kb simply minified.
Despite that, with the proliferation of server-side JS making size largely irrelevant, what would be required to port this over? If I would write that and submit a pull request, would that be accepted or is this not something you want to maintain?

Thanks for the offer! We'll have a chat and see what we think. Good point about JS being commonly used server-side these days.

Okay: we are happy to review and accept a PR. Note that we try and have our ports mirror the Java as much as possible so keep comments, var names etc the same as much as possible. Any public methods that aren't implemented should be documented in the README as such.
The PR will also need to have:
-- tests
-- code to build the geocoding data files suitable for inclusion as JS (ideally following the same principle as java/c++ where a string that appears multiple times is represented only once and referred to instead of including it lots of times)

I'm trying to grok the build system... firstly just for the data. I'm thinking that transforming the data into a response in javascript is far simpler than actually fully integrating into the system.
Firstly, how does the geocoding data from resources/geocoding/ become accessible? For java, it looks like it gets built -- into some sort of binary.
I know the other metadata gets transformed for JS, is there code already for transforming the geocoding data into JSON or just concatenating it?

Is there any update on this??
Can i use geo-location and timezone mapper facility with Javascript/Node?? If so please reply...


Configure javascript jshlint to check code style in tests

done in https://github.com/wejs/we-core/commit/f15d8df2b9daf2f892a0c4450ab885fb7367ba42


Things that haven't changed (but presumably should have) with the corrected 2022 spawning biomass

Chris re-ran the base model with updated SS, that now gives B_2022 agreeing with the 'forecasted' B_2022 value. Fixes the issue with the one-page summary.
Chris posted hake-assessment-2022-feb-08-base-model-corrected.pdf.  [only the base model re-run]
I made feb-08-base-model-corrected-diff.pdf which shows the text [not figure] differences with the submitted preSRG version.
So B_2022 has changed, but projections correctly haven't changed because they were using the correct B_2022 etc. all along.
However, I think some of these things should also have changed from the preSRG version but have not:

[ ] Table 18 (median biomass at age) for 2022.
[ ] Table 22 (biomass of large cohorts), should have changed for the final year for each cohort
[ ] Table 23 (medians of some things), some have correctly changed but age-2+ biomass should have also changed:

[ ] Table 24 - same thing, just for credible intervals
[ ] Table 32-34 - relative spawning biomass for sens runs and retros now not comparable to base model. Chris says he can just do the mceval step for those.
[ ] Figure 16 and 17 - bridging models should have different B_2022 but hasn't changed. Presumably need to do mceval step again for those.

Basically need to run mceval for everything we’ve done. I’ll write a script to do it all in parallel on AWS machine

next.treaty.catch <- f(base.model$catch.levels[[catch.default.policy.ind]][[1]][1], 0)

still comes up as 716,264, instead of the updated 715,643 that comes from
catch.limit.quantiles <- f(as.numeric(quantile(base.model$mcmc[[paste0("ForeCatch_", end.yr)]],
                                               probs = c(0.025, 0.5, 0.975))))```

[ ] But I think the bigger issue is that catch streams m and n need redoing, yes? As they now disagree with the corrected one-page summary.

The default catch value changed a bit so we have to re run the whole catch levels calcs and forecasting. Sigh.

@andrew-edwards
@kellijohnson-NOAA
@aaronmberger-nwfsc
It's finally done. The biomass trajectory is correct now as are the biomass numbers in the doc. The tables which remain unchecked above didn't change their 2022 values. My guess is SS doesn't output those values correctly, as they are coming straight from the SS output.
The default catch value is corrected as well, and all forecasts were re-run. See the decision table, it is now 715,643 in rows m and n.
Row m in table h should all be 1.00. I think it isn't quite because the tolerance wasn't high enough in the catch level determination routine. Could re-run that if we think it's necessary although I think it's close enough (at those high catch levels that won't be fished anyways).
To get all the updated RDS files, pull the repo and run the script download_models_from_s3.R. It will download and make small RDS's and will be way faster than trying to use the s3_download("models", ext=rds") method.
There's a copy of the doc on the Google Drive:
https://drive.google.com/file/d/1NkptX6615mJq6XBTtSbJgR0ZdC5iAP6m/view?usp=sharing
Andy here is the TEX file
hake-assessment.tex.txt

I pulled and don't see download_models_from_s3.R in the repo.


[Bug]: vllm 0.4.1 crashing after checking P2P status on single GPU

Your current environment
Collecting environment information...
PyTorch version: 2.2.1+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.4 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.29.2
Libc version: glibc-2.35

Python version: 3.10.13 (main, Sep 11 2023, 13:44:35) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-105-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 12.3.52
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: GRID A100X-40C
Nvidia driver version: 535.129.03
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      40 bits physical, 48 bits virtual
Byte Order:                         Little Endian
CPU(s):                             32
On-line CPU(s) list:                0-31
Vendor ID:                          AuthenticAMD
Model name:                         AMD EPYC-Milan Processor
CPU family:                         25
Model:                              1
Thread(s) per core:                 1
Core(s) per socket:                 1
Socket(s):                          32
Stepping:                           1
BogoMIPS:                           3992.50
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext perfctr_core invpcid_single ssbd ibrs ibpb stibp vmmcall fsgsbase tsc_adjust bmi1 avx2 smep bmi2 invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves clzero xsaveerptr wbnoinvd arat npt lbrv nrip_save tsc_scale vmcb_clean pausefilter pfthreshold umip pku ospke vaes vpclmulqdq rdpid arch_capabilities
Virtualization:                     AMD-V
Hypervisor vendor:                  KVM
Virtualization type:                full
L1d cache:                          1 MiB (32 instances)
L1i cache:                          1 MiB (32 instances)
L2 cache:                           16 MiB (32 instances)
L3 cache:                           1 GiB (32 instances)
NUMA node(s):                       1
NUMA node0 CPU(s):                  0-31
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Mitigation; safe RET
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.19.3
[pip3] torch==2.2.1
[pip3] torchaudio==2.2.1
[pip3] torchvision==0.17.1
[pip3] triton==2.2.0
[pip3] vllm-nccl-cu12==<IP_ADDRESS>.4.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] nvidia-nccl-cu12          2.19.3                   pypi_0    pypi
[conda] torch                     2.2.1                    pypi_0    pypi
[conda] torchaudio                2.2.1                    pypi_0    pypi
[conda] torchvision               0.17.1                   pypi_0    pypi
[conda] triton                    2.2.0                    pypi_0    pypi
[conda] vllm-nccl-cu12            <IP_ADDRESS>.4.0             pypi_0    pypiROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.4.1
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
^[[4mGPU0       CPU Affinity    NUMA Affinity   GPU NUMA ID^[[0m
GPU0     X      0-31    0               N/A

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

🐛 Describe the bug
Thanks for the great code!
I'm getting a strange nccl issue in the latest version of vllm (0.4.1). I had no problems with earlier releases (just confirmed that v0.3.0 runs without issue. From what I can tell of the error message, the code is attempting a peer-to-peer connection, but I'm only running on a single GPU. Running the minimal example above, I get:
(speakYSE) ubuntu@speakyse:/mnt/vol_llm$ python test.py
/mnt/vol_llm/packages/huggingface_hub/file_download.py:1132: FutureWarning: `resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.
  warnings.warn(
INFO 05-03 16:50:14 llm_engine.py:98] Initializing an LLM engine (v0.4.1) with config: model='facebook/opt-125m', speculative_config=None, tokenizer='facebook/opt-125m', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.float16, max_seq_len=2048, download_dir=None, load_format=auto, tensor_parallel_size=1, disable_custom_all_reduce=False, quantization=None, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), seed=0)

INFO 05-03 16:50:15 utils.py:608] Found nccl from library /home/ubuntu/.config/vllm/nccl/cu12/libnccl.so.2.18.1
INFO 05-03 16:50:15 selector.py:28] Using FlashAttention backend.
speakyse:3688:3688 [0] NCCL INFO Bootstrap : Using enp1s0:<IP_ADDRESS><0>
speakyse:3688:3688 [0] NCCL INFO NET/Plugin : dlerror=libnccl-net.so: cannot open shared object file: No such file or directory No plugin found (libnccl-net.so), using internal implementation
speakyse:3688:3688 [0] NCCL INFO cudaDriverVersion 12020
NCCL version 2.19.3+cuda12.3
speakyse:3688:3861 [0] NCCL INFO NET/IB : No device found.
speakyse:3688:3861 [0] NCCL INFO NET/Socket : Using [0]enp1s0:<IP_ADDRESS><0> [1]br-febe132fd1d0:<IP_ADDRESS><0>
speakyse:3688:3861 [0] NCCL INFO Using non-device net plugin version 0
speakyse:3688:3861 [0] NCCL INFO Using network Socket

speakyse:3688:3861 [0] misc/nvmlwrap.cc:143 NCCL WARN nvmlDeviceGetP2PStatus(0,0,NVML_P2P_CAPS_INDEX_READ) failed: Invalid Argument
speakyse:3688:3861 [0] NCCL INFO misc/nvmlwrap.cc:181 -> 2
speakyse:3688:3861 [0] NCCL INFO init.cc:351 -> 2
speakyse:3688:3861 [0] NCCL INFO init.cc:1387 -> 2
speakyse:3688:3861 [0] NCCL INFO group.cc:64 -> 2 [Async thread]
speakyse:3688:3688 [0] NCCL INFO group.cc:418 -> 2
speakyse:3688:3688 [0] NCCL INFO group.cc:95 -> 2
Traceback (most recent call last):
  File "/mnt/vol_llm/test.py", line 11, in <module>
    llm = LLM(model="facebook/opt-125m")
  File "/mnt/vol_llm/packages/vllm/entrypoints/llm.py", line 118, in __init__
    self.llm_engine = LLMEngine.from_engine_args(
  File "/mnt/vol_llm/packages/vllm/engine/llm_engine.py", line 277, in from_engine_args
    engine = cls(
  File "/mnt/vol_llm/packages/vllm/engine/llm_engine.py", line 148, in __init__
    self.model_executor = executor_class(
  File "/mnt/vol_llm/packages/vllm/executor/executor_base.py", line 41, in __init__
    self._init_executor()
  File "/mnt/vol_llm/packages/vllm/executor/gpu_executor.py", line 22, in _init_executor
    self._init_non_spec_worker()
  File "/mnt/vol_llm/packages/vllm/executor/gpu_executor.py", line 50, in _init_non_spec_worker
    self.driver_worker.init_device()
  File "/mnt/vol_llm/packages/vllm/worker/worker.py", line 110, in init_device
    init_worker_distributed_environment(self.parallel_config, self.rank,
  File "/mnt/vol_llm/packages/vllm/worker/worker.py", line 313, in init_worker_distributed_environment
    torch.distributed.all_reduce(torch.zeros(1).cuda())
  File "/mnt/vol_llm/packages/torch/distributed/c10d_logger.py", line 72, in wrapper
    return func(*args, **kwargs)
  File "/mnt/vol_llm/packages/torch/distributed/distributed_c10d.py", line 1992, in all_reduce
    work = group.allreduce([tensor], opts)
torch.distributed.DistBackendError: NCCL error in: ../torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp:1691, unhandled system error (run with NCCL_DEBUG=INFO for details), NCCL version 2.19.3
ncclSystemError: System call (e.g. socket, malloc) or external library call failed or device error.
Last error:
nvmlDeviceGetP2PStatus(0,0,NVML_P2P_CAPS_INDEX_READ) failed: Invalid Argument

Any ideas? Thanks!

I'm trying to set up llama3, so I'm hoping not to have to downgrade vllm versions if possible.

Any luck? I have the same issue..

Do you try newer versions? I believe this code is introduced in https://github.com/vllm-project/vllm/pull/4159 , and we have some update to that part of code later.

My educated guess is that this is some hardware problem. I see the gpu model is GPU 0: GRID A100X-40C, which I never saw before.

Any luck? I have the same issue on a single GPU machine.

Which GPU model are you using?

After further investigation, i think this is a nccl issue:

misc/nvmlwrap.cc:143 NCCL WARN nvmlDeviceGetP2PStatus(0,0,NVML_P2P_CAPS_INDEX_READ) failed: Invalid Argument

nccl calls nvmlDeviceGetP2PStatus and it does not work in vGPU mode (which leads to this GPU 0: GRID A100X-40C) . It seems nccl forgets to clear the error state, so this failed call affects the later nccl operations.
I suggest you report this to the nccl team at https://github.com/NVIDIA/nccl .

I talked with NCCL team, and they confirm they don't support vGPU. I created an issue to track this problem

I guess this problem is solved by https://github.com/vllm-project/vllm/pull/4591, can you confirm? @youkaichao

I don't have vGPU to test. It would be great if @alexandergagliano can test the latest code and see if this issue is resolved.

I can confirm that the error is still present on a vGPU in 0.4.3, but it is now triggered by the warmup at this line:
https://github.com/vllm-project/vllm/blob/246598a6b1e22616630b7f1bf11bd9bcb31dc860/vllm/distributed/parallel_state.py#L122
Commenting out that one line seems to make at least the openai compatible server work for me though!

/assign
Let me try to take a fix on this.

Commenting out that one line seems to make at least the openai compatible server work for me though!

glad to hear it works. do you know how to use vGPU in k8s so that our ci can test this case?


versions: Update golang to 1.10.4

Move to golang version 1.10.4 -- the oldest stable golang release at the
time of writing -- since golang 1.10+ is needed to make namespace
handling safe.
See:

https://github.com/golang/go/issues/20676
https://github.com/golang/go/commit/2595fe7fb6f272f9204ca3ef0b0c55e66fb8d90f

Also bumped languages.golang.meta.newest-version to golang version
1.11, which is the newest stable release at the time of writing.
Fixes #148.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

Like the idea - let's see if the CI can be agreeable.

I think this can only be fixed by reordering field in this structs.

lgtm
I think the maligned crying is not related to this patch, right?

/me tweaks branch to hopefully stop the linters bleating...

CI failed due to a factory test failure:
--- FAIL: TestNewFactory (0.01s)
    testing.go:771: race detected during execution of test

/cc @bergwolf.

Sigh - go 1.10 is spotting issues in other projects code and failing our tests ;((
# github.com/containerd/cri/integration
integration/image_load_test.go:39: T.Skip call has possible formatting directive %v

/test

CI turbines bombed @jodh-intel Is this still something you will pursue?

@jodh-intel Any updates?

@bergwolf See #806 - @amshinde has posted some patches upstream to containerd/cri - we need to get them pulled in so we can bump the golang version and not fail the build.

@bergwolf - yes, that is the merged PR. Over on #806 I have the patches to bump that versions.yaml and golang version change. I'll chase that up - I need to fix at least the yq dep for travis.

@jodh-intel ping from your weekly Kata herder.

/test

/test

/test

We now have a cyclic dependency since this PR is failing due to https://github.com/kata-containers/tests/pull/843 (and vice versa).

OK, we know this will fail on the xurl stuff, which we need to land this to fix:
INFO: Installing xurls utility
package mvdan.cc/xurls/v2: cannot find package "mvdan.cc/xurls/v2" in any of:
	/usr/local/go/src/mvdan.cc/xurls/v2 (from $GOROOT)
	/tmp/jenkins/workspace/kata-containers-runtime-ubuntu-16-04-PR/go/src/mvdan.cc/xurls/v2 (from $GOPATH)
Build step 'Execute shell' marked build as failure

@jodh-intel and I propose we force merge. Of course it carries some risk, but right now the CI is broken on the xurl item, and we can merge nothing else anyway...


Couldn't find Dnn.AdminExperience in tree v9.4.1

i try to find Dnn.AdminExperience in this link but it's not exist there, please help me.

Up to 9.4.1 it was not merged yet, you will find it here for 9.4.1 https://github.com/dnnsoftware/Dnn.AdminExperience/tree/release/3.0.x


Version number in setup.py is outdated

The setup.py is declaring that current version is still 1.2.4, but from the tags perspective, you already released 1.2.7.
This make difficult to "pip" to get the latest version

Current version in setup.py is 1.2.10.


How to distinguish backend from frontend?

Yii2 here, how can I tell from my code that it's running from backend or frontend, I've tried property_exists() but it fails, is there any documented way? Like IsFrontend()?

use forum
if (Yii::$app->id === 'frontend_app')


Highligth regex

Hi, how can i parse and detect if exist a string like #string to highlight it

This is not a question I can understand, and it certainly isn't a bug report, so I'm going to close it. Feel free to open a thread with a clearer formulation of your question on the forum.


Upgrade to d3v4

This pull request upgrade d3-grid code to d3v4.
This is still a work in progress and should not be merged yet
Goals
Upgrade to d3v4 : e2714ad
x = d3.scale.ordinal(), becomes x = d3.scaleOrdinal(),
x.domain(d3.range(_cols)).rangeBands become
var x = d3.scaleBand();
 x.domain(d3.range(_cols)).range([0, size[0]], padding[0], 0);

x.domain(d3.range(_cols)).rangePoints becomes
var x = d3.scalePoint();
x.domain(d3.range(_cols)).range([0, size[0]]);

Trim down the dependencies to modular d3: 838c964
The plugin now only loads d3-scale, instead of the whole of d3.
  "dependencies": {
    "d3-scale": "^1.0.6"
  },

Adopt d3v4 plugin structure: f3015dd
d3-grid.js has been moved to a src/ directory. See guidance on publishing a d3 plugin

:+1:

Thanks @gka - we're waiting on @herrstucki to merge this in!
That said, I've used it successfully in prod for the Times general election results page: https://www.thetimes.co.uk/electionresults (resize to < 768px across)

@basilesimon not sure if you're still working on it but the package.json was left broken in your last commit and the dependencies are missing. Please make sure the tests actually pass and the build process works before you push 😉  Thanks in advance! 🙇
P.S: I've also enabled Travis, so we get test feedback here as well.

@herrstucki Ah, this is about as far as I'm going to go. Some tests are still soft-failing (not being return what's expected)... I'd really welcome your help on these at this point.
The build and packaging have been fixed and now working nicely 💯  😀

Hey @herrstucki, sorry to bother you again, but I think I need some help to get this over the line.
It would be fantastic to have this plugin properly available. At the moment this is something I personally use all the time, but the implementation described in my above comment is pretty gross.
Also, we now have this fork with a confusing name (cc @finnfiddle).
Maybe it would be simpler if we had one, up-to-date version of this plugin we can all contribute to?


Failed to recalculated device parameter (No DPDB device match) due to dpdb.json connection refused

For me it's weird I have tried so many ways to place a simple box on mobile but it's not showing.
I am running my folder in the IIS server and accessing through my wifi on mobile.
The Steps I followed

Enabled SSL on my IIS and android mobile (chrome(checked with version 74 to 78-IOS Chrome also checked ), firefox) have detected my camera, after loading the object will not be shown, parallel I tested it on my computer it works well.(there is no error on console). And I have referenced previous github issues raised by others. MIME configured well.
Then I tested https://codepen.io/sureshwisdom/pen/NWWZZMj - on my mobile it works well.

This is my simple code below
`<!doctype HTML>

`

I inspected in mobile chrome via remote debugging, I am getting some errors. @nicolocarpignoli

Try using latest AR.js, so version 2.0.8
Also,which phone do you have? Which os version?

@nicolocarpignoli I have loaded camera_para.dat file in  and added it MIME Types, Then I checked It works well.
My Android version is 9, Device modal Redmi 6A
Do I need to add my device on the dpdb.json file?. How to configure it locally?

@nicolocarpignoli I Followed https://github.com/jeromeetienne/AR.js/issues/465#issuecomment-505354686 and it works on mobile.
Mobile Model: Redmi 6A, Android Version 9'P'.
Do I need to add my mobile configuration dpdb.json and Is any way to configure on the local machine (offline).

@nicolocarpignoli I Followed this solution  https://github.com/jeromeetienne/AR.js/issues/465#issuecomment-505354686 and it works on mobile.
Mobile Model: Redmi 6A, Android Version 9'P'.
Do I need to add my mobile configuration dpdb.json and Is any way to configure on the local machine (offline).

what is No DPDB ? never saw that problem. Are you sure you do not have custom code on the .html, or loaded external scripts?

Aframe says no DPDB device match, Its due to non-configuration of my android device. Here I am running on my own IIS server. So it's refusing the **https://dpdb.webvr.rocks/dpdb.json **. For that, I am getting the following errors on my console.

*Failed to recalculated device parameter
Sensor Could not be read
Failed to Load Resources https://dpdb.webvr.rocks/dpdb.json.**

**
Is there any way of resolving this issue. My server will not connect to the Internet.

Please stop mentioning random people - that is spam @sureshwisdom

@nicolocarpignoli  For mobile browser and desktop, the rendered model works well. When I have seen in tablet the model not showing with the light property. Pls refer my issue [https://github.com/jeromeetienne/AR.js/issues/662#issuecomment-559899948

](url)


kindnet for linux/arm64

Hi @aojea
long time no see,
we are starting to have more users trying to run networking topologies with kind and kindnet as a proper CNI suitable for networking OSes.
Unfortunately, we have a lot of Mac Os users (me included), who wanted to play with this on their macs. Would it be possible to build kindnet for linux/arm64 so that we get to enjoy kind clusters with it?
Should be a few lines in the workflow config, but this is sensitive for outside contributions, so maybe you may want to do this yourself.
Thank you!

@hellt do you still need the bridge mode?
is this still running inside kind on Mac?

yes, we still use the bridge mode both on mac and linux
also it seems it is quite in demand

ok, give me some days to fix this

@hellt the images should be published automatically after this job finish https://github.com/aojea/kindnet/actions/runs/9692669989
I'm going to be AFK for some time, if you check the images are correct and work feel free to close the issue

Thanks @aojea
I wonder if that would work as expected, though. Since the cni binaries are still not build for the target (arm64) architecture as far I can see from a quick glance at #36.
The go build is executed outside of the dockerfile, so I don't think the container image will contain the arm64 build cni binary...

hmm , to be honest I don't have it clear, it gets the GOARCH argument but I'm always confused building multiarch and never get it at the first try ... do you mind if we iterate based on current run?

ok, is doing the wrong thing
#16 [linux/arm64 builder 4/5] RUN CGO_ENABLED=0 go build -o /go/bin/kindnetd ./cmd/kindnetd
#16 DONE 618.8s
#20 [linux/arm64 builder 5/5] RUN echo "Installing CNI binaries ..."     && export CNI_TARBALL="v1.5.0/cni-plugins-linux-amd64-v1.5.0.tgz"     && export CNI_URL="[https://github.com/containernetworking/plugins/releases/download/${CNI_TARBALL}](https://github.com/containernetworking/plugins/releases/download/$%7BCNI_TARBALL%7D)"     && curl -sSL --retry 5 --output /tmp/cni.tgz "${CNI_URL}"     && mkdir -p /opt/cni/bin     && tar -C /opt/cni/bin -xzf /tmp/cni.tgz     && rm -rf /tmp/cni.tgz     && find /opt/cni/bin -type f -not (          -iname host-local          -o -iname ptp          -o -iname bridge          -o -iname portmap       )       -delete

let's see https://github.com/aojea/kindnet/actions/runs/9695000038/job/26753827829

this time it looks correct
#16 [linux/amd64 builder 5/5] RUN echo "Installing CNI binaries ..."     && export CNI_TARBALL="v1.5.0/cni-plugins-linux-amd64-v1.5.0.tgz"     && export CNI_URL="[https://github.com/containernetworking/plugins/releases/download/${CNI_TARBALL}](https://github.com/containernetworking/plugins/releases/download/$%7BCNI_TARBALL%7D)"     && curl -sSL --retry 5 --output /tmp/cni.tgz "${CNI_URL}"     && mkdir -p /opt/cni/bin     && tar -C /opt/cni/bin -xzf /tmp/cni.tgz     && rm -rf /tmp/cni.tgz     && find /opt/cni/bin -type f -not (          -iname host-local          -o -iname ptp          -o -iname bridge          -o -iname portmap       )       -delete
#16 0.288 Installing CNI binaries ...
#16 DONE 1.3s

#15 [linux/amd64->arm64 builder 5/5] RUN echo "Installing CNI binaries ..."     && export CNI_TARBALL="v1.5.0/cni-plugins-linux-arm64-v1.5.0.tgz"     && export CNI_URL="[https://github.com/containernetworking/plugins/releases/download/${CNI_TARBALL}](https://github.com/containernetworking/plugins/releases/download/$%7BCNI_TARBALL%7D)"     && curl -sSL --retry 5 --output /tmp/cni.tgz "${CNI_URL}"     && mkdir -p /opt/cni/bin     && tar -C /opt/cni/bin -xzf /tmp/cni.tgz     && rm -rf /tmp/cni.tgz     && find /opt/cni/bin -type f -not (          -iname host-local          -o -iname ptp          -o -iname bridge          -o -iname portmap       )       -delete
#15 DONE 1.3s

fantastic, it was a long time since I had to do this, happy to see the ecosystem improved a lot , really neat and simple these days to do multibuild
https://github.com/aojea/kindnet/pkgs/container/kindnetd/235911957?tag=v1.2.0

sweet, thanks a lot @aojea
Will do the testing on macOS 14 + kind


[Suggestion] Able to place down variant of the slab and delay

if player is half block lower and bridging with slab, it will place down variant ;)
Also add a configurable delay to activate bridging so it doesn't bridge when i don't want to

Slab placing is still in the works as I wanted to rewrite the placement logic to make it more feasible. Should see it in a later release.
There's now a way to disable bridging in the config while I work something like a delay. It could also be bindable to a hotkey to give a bit more control perhaps. The new placement logic prioritises vanilla-style placements over bridging anyway which hopefully should make this less of an issue :)

Right welp, that's both of the features implemented! I've opted for adding a key binding as I think that's a bit more controllable than a delay but feedback is always welcome :)
Shall be shipped in 2.1.0 soonTM


[BUG]:

What version of drizzle-orm are you using?
0.31.2
What version of drizzle-kit are you using?
0.22.7
Describe the Bug
Hello there!
I created an enum in my schema:
export const statusEnum = pgEnum('status', ['monitored', 'bought', 'sold', 'dropped']);
export const tokens = pgTable('tokens', {
  status: statusEnum('status'),
});

, but it seems that only the first 3 are taking into account. The migration appears correct though:
DO $$ BEGIN
 CREATE TYPE "public"."status" AS ENUM('monitored', 'bought', 'sold', 'dropped');
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;
--> statement-breakpoint
CREATE TABLE IF NOT EXISTS "tokens" (
	"status" "status",
);

But I look at my interface, I don't see the value dropped, and when I try to update my status with the dropped enum, I get an error: error: invalid input value for enum status: "dropped"

Expected behavior
No response
Environment & setup
No response

@jcoulaud Hey! It seems that the database already had a type with this name and only 3 values and it did not return an error about a duplicate. You can check this by running this query:
SELECT
     n.nspname as enum_schema,
     t.typname as enum_name,
     e.enumlabel as enum_value
FROM pg_type t
JOIN pg_enum e ON t.oid = e.enumtypid
JOIN pg_catalog.pg_namespace n ON n.oid = t.typnamespace;

If so, delete the type and run the migration again.

@jcoulaud Hey! It seems that the database already had a type with this name and only 3 values and it did not return an error about a duplicate. You can check this by running this query:
SELECT
     n.nspname as enum_schema,
     t.typname as enum_name,
     e.enumlabel as enum_value
FROM pg_type t
JOIN pg_enum e ON t.oid = e.enumtypid
JOIN pg_catalog.pg_namespace n ON n.oid = t.typnamespace;

If so, delete the type and run the migration again.

Hey Roman, I’ve updated my schema since then, but I remember that deleting the type and rerunning the migration did the trick. The key was to delete the type.


Fix typo

change from icon to entity in step 3

Thanks. I'm actually going to deprecate this and add the functionality to the button-card

Better! it will be more useable. Thanks


Usage with serverless framework

I've spent quite some time using this package with the serverless framework with https://github.com/UnitedIncome/serverless-python-requirements.
I always get an unable to import error, whatever version of python I am using (I've mostly tried 3.7 and 3.6).
Has anyone ever managed to use this lib with a similar setup?
serverless.yml:
service: render-test

frameworkVersion: '2'

custom:
  pythonRequirements:
    dockerizePip: non-linux
    # dockerImage: lambdaci/lambda:python3.6
    zip: true

provider:
  name: aws
  runtime: python3.6
  lambdaHashingVersion: '20201221'

functions:
  render:
    handler: handler.main
    events:
      - http:
          path: /render
          method: get

plugins:
  - serverless-python-requirements

handler.py:
import json
import boto3

from bpy_lambda import bpy

s3 = boto3.resource('s3')
BUCKET_NAME = '###'

def main(event, context):
    s3.Bucket(BUCKET_NAME).download_file('###', '###')

    bpy.ops.wm.open_mainfile(filepath="###", load_ui=False)
    bpy.context.scene.render.filepath = "rendertest.png"
    bpy.context.scene.render.resolution_x = 1500
    bpy.context.scene.render.resolution_y = 1500
    bpy.ops.render.render()

    s3.Bucket(BUCKET_NAME).upload_file('rendertest.png', 'test/rendertest.png')

    response = {"statusCode": 200, "body": json.dumps({"hello": "hello"})}

    return response

Error when running:
yarn serverless invoke -f render --stage test --aws-profile ###
yarn run v1.22.5
warning package.json: No license field
$ /Users/###/node_modules/.bin/serverless invoke -f render --stage test --aws-profile ###
{
    "errorMessage": "Unable to import module 'functions/render'"
}

 Serverless Error ----------------------------------------

  Invoked function failed

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com

  Your Environment Information ---------------------------
     Operating System:          darwin
     Node Version:              14.15.5
     Framework Version:         2.54.0 (local)
     Plugin Version:            5.4.3
     SDK Version:               4.2.6
     Components Version:        3.15.0

error Command failed with exit code 1.

@aldebout for what it's worth, AWS Lambda supports container images which I've personally found more suitable at this point for lambda powered Blender
https://aws.amazon.com/blogs/aws/new-for-aws-lambda-container-image-support/