Cannot use karma.config.local.js

Describe the Bug
For some reason, it still reads the karma.conf.js instead of karma.conf.local.js. So I cannot use the local karma file.
here is my settings
"karmaTestExplorer.karmaConfFilePath":"karma.conf.local.js"
Steps to Reproduce the Behavior

Go to VSCode settings
Set "karmaTestExplorer.karmaConfFilePath":"karma.conf.local.js"
karmaTestExplorer is not working
it is still reading karma.conf.js

Describe the Expected Behavior

karmaTestExplorer should work with multiple karma config

Provide Debug Logs

Karma Test Explorer work space log

[2023-05-09 08:31:23.250] [INFO] [Main]: Activating Karma Test Explorer, v0.8.2
[2023-05-09 08:31:23.251] [INFO] [Main]: Creating file handler
[2023-05-09 08:31:23.251] [INFO] [Main]: Creating workspace configuration resolver
[2023-05-09 08:31:23.251] [INFO] [Main]: Creating project factory
[2023-05-09 08:31:23.251] [INFO] [Main]: Creating config change manager
[2023-05-09 08:31:23.251] [DEBUG] [ConfigChangeManager]: Creating config change subscription
[2023-05-09 08:31:23.252] [INFO] [Main]: Creating preference manager
[2023-05-09 08:31:23.252] [INFO] [Main]: Creating port acquisition manager
[2023-05-09 08:31:23.252] [INFO] [Main]: Creating multi-status display
[2023-05-09 08:31:23.252] [INFO] [Main]: Registering project selection command
[2023-05-09 08:31:23.253] [INFO] [Main]: Registering function execution command
[2023-05-09 08:31:23.253] [INFO] [Main]: Setting initial multi-project context
[2023-05-09 08:31:23.253] [INFO] [Main]: Setting multi-project context to: false
[2023-05-09 08:31:23.253] [INFO] [Main]: Processing initial workspace folders
[2023-05-09 08:31:23.254] [INFO] [Main]: Discovering projects for workspace folders: [
  "/c/Projects/cirium-profiles/src/frontend"
]
[2023-05-09 08:31:23.254] [DEBUG] [ProjectFactory]: Inspecting workspace folder for testing: /c/Projects/cirium-profiles/src/frontend
[2023-05-09 08:31:23.255] [DEBUG] [ProjectFactory]: Including projects in workspace folder '/c/Projects/cirium-profiles/src/frontend' - 'karmaTestExplorer.enableExtension' is set to true
[2023-05-09 08:31:23.255] [DEBUG] [ProjectFactory]: Including projects in workspace folder - One or more inclusion conditions were satisfied: /c/Projects/cirium-profiles/src/frontend
[2023-05-09 08:31:23.257] [DEBUG] [SimpleFileHandler]: Reading file synchronously: /c/Projects/cirium-profiles/src/frontend/angular.json
[2023-05-09 08:31:23.259] [INFO] [ProjectFactory]: Using project type 'angular' (auto-detected) for workspace folder: /c/Projects/cirium-profiles/src/frontend
[2023-05-09 08:31:23.259] [DEBUG] [ProjectFactory]: Angular projects found for workspace folder '/c/Projects/cirium-profiles/src/frontend': cirium-profiles
[2023-05-09 08:31:23.260] [DEBUG] [Main]: Last loaded projects: [
  "/c/Projects/cirium-profiles/src/frontend"
]
[2023-05-09 08:31:23.260] [DEBUG] [Main]: Primary projects: []
[2023-05-09 08:31:23.260] [INFO] [Main]: Registering project: /c/Projects/cirium-profiles/src/frontend
[2023-05-09 08:31:23.260] [INFO] [Main]: Activating adapter for project: /c/Projects/cirium-profiles/src/frontend (frontend: cirium-profiles)
[2023-05-09 08:31:23.272] [INFO] [Main]: Done activating adapter for project: /c/Projects/cirium-profiles/src/frontend (frontend: cirium-profiles)
[2023-05-09 08:31:23.272] [INFO] [Main]: Setting multi-project context to: false
[2023-05-09 08:31:23.273] [INFO] [Main]: Subscribing to config changes for workspace folder: /c/Projects/cirium-profiles/src/frontend
[2023-05-09 08:31:23.274] [INFO] [Main]: Subscribing for subsequent workspace folder additions and removals
[2023-05-09 08:31:23.691] [DEBUG] [PortAcquisitionManager]: Request for 1 port(s) at base port 9976 acquired: 9976
[2023-05-09 08:31:23.691] [TRACE] [PortAcquisitionManager]: Currently assigned ports: 9976
[2023-05-09 08:31:23.707] [DEBUG] [PortAcquisitionManager]: Request for 1 port(s) at base port 9999 acquired: 9999
[2023-05-09 08:31:23.707] [TRACE] [PortAcquisitionManager]: Currently assigned ports: 9976, 9999
[2023-05-09 08:34:23.231] [DEBUG] [PortAcquisitionManager]: Releasing ports: 9999

Karma Server Log

karma.server.log

Another log

[2023-05-09 08:31:23.267] [DEBUG] [Adapter]: Creating server output channel
[2023-05-09 08:31:23.268] [DEBUG] [Adapter]: Creating port acquisition client
[2023-05-09 08:31:23.268] [DEBUG] [Adapter]: Creating debugger
[2023-05-09 08:31:23.268] [DEBUG] [Adapter]: Creating project commands handler
[2023-05-09 08:31:23.268] [DEBUG] [Commands]: Registering command 'ShowLog' as namespaced command 'karmaTestExplorer.frontend: cirium-profiles:ShowLog
[2023-05-09 08:31:23.268] [DEBUG] [Commands]: Registering command 'Reset' as namespaced command 'karmaTestExplorer.frontend: cirium-profiles:Reset
[2023-05-09 08:31:23.268] [DEBUG] [Adapter]: Creating notifications handler
[2023-05-09 08:31:23.268] [DEBUG] [Adapter]: Creating test emitters
[2023-05-09 08:31:23.518] [DEBUG] [Adapter]: Assembling new test explorer
[2023-05-09 08:31:23.518] [DEBUG] [Adapter]: Re/creating test explorer with extension configuration: {
  "logger": {
    "loggerName": "ExtensionConfig",
    "appender": {
      "outputChannelName": "Karma Test Explorer (frontend: cirium-profiles)",
      "options": {
        "enabled": true,
        "lazyCreate": false
      },
      "outputChannel": {
        "name": "Karma Test Explorer (frontend: cirium-profiles)"
      }
    },
    "logLevel": "debug"
  },
  "projectType": "angular",
  "projectName": "cirium-profiles",
  "projectPath": "/c/Projects/cirium-profiles/src/frontend",
  "projectInstallRootPath": "/c/Projects/cirium-profiles/src/frontend",
  "projectKarmaConfigFilePath": "/c/Projects/cirium-profiles/src/frontend/karma.conf.js",
  "baseKarmaConfFilePath": "/home/ubuntu/.vscode-server/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs",
  "karmaPort": 9976,
  "testTriggerMethod": "http",
  "testParsingMethod": "ast",
  "failOnStandardError": false,
  "defaultSocketConnectionPort": 9999,
  "logLevel": "debug",
  "karmaLogLevel": "debug",
  "karmaReporterLogLevel": "disable",
  "autoWatchEnabled": true,
  "karmaReadyTimeout": 900000,
  "testGrouping": "folder",
  "flattenSingleChildFolders": true,
  "environment": {},
  "envExclude": [],
  "reloadOnKarmaConfigChange": true,
  "customLauncher": {
    "base": "Chrome",
    "flags": [
      "--headless",
      "--disable-gpu",
      "--disable-dev-shm-usage",
      "--remote-debugging-port=9222"
    ]
  },
  "browser": "chrome_no_sandbox",
  "testFiles": [
    "**/*{.,-,_}{test,spec}.{ts,js}",
    "**/{test,spec}{.,-,_}*.{ts,js}"
  ],
  "allowGlobalPackageFallback": true,
  "excludeDisabledTests": false,
  "showOnlyFocusedTests": false,
  "showUnmappedTests": true,
  "showTestDefinitionTypeIndicators": true,
  "debuggerConfig": {
    "name": "Karma Test Explorer Debugging",
    "type": "chrome",
    "request": "attach",
    "browserAttachLocation": "workspace",
    "address": "localhost",
    "port": 9222,
    "timeout": 60000,
    "webRoot": "/c/Projects/cirium-profiles/src/frontend"
  },
  "reloadOnChangedFiles": [],
  "excludeFiles": [
    "**/node_modules/**/*"
  ]
}
[2023-05-09 08:31:23.519] [DEBUG] [Adapter]: Creating main factory
[2023-05-09 08:31:23.519] [DEBUG] [MainFactory]: Detecting test framework from karma config file: /c/Projects/cirium-profiles/src/frontend/karma.conf.js
[2023-05-09 08:31:23.519] [DEBUG] [SimpleFileHandler]: Reading file synchronously: /c/Projects/cirium-profiles/src/frontend/karma.conf.js
[2023-05-09 08:31:23.521] [DEBUG] [MainFactory]: Detected frameworks from karma config: jasmine, @angular-devkit/build-angular
[2023-05-09 08:31:23.521] [DEBUG] [MainFactory]: Detected test framework: jasmine
[2023-05-09 08:31:23.522] [INFO] [MainFactory]: Using test framework: jasmine (auto-detected)
[2023-05-09 08:31:23.522] [DEBUG] [MainFactory]: Creating test helper
[2023-05-09 08:31:23.522] [DEBUG] [MainFactory]: Creating process handler
[2023-05-09 08:31:23.522] [DEBUG] [MainFactory]: Creating test locator
[2023-05-09 08:31:23.523] [DEBUG] [MainFactory]: Creating AST test definition provider
[2023-05-09 08:31:23.524] [DEBUG] [MainFactory]: Creating test store
[2023-05-09 08:31:23.526] [DEBUG] [Adapter]: Getting process handler from factory
[2023-05-09 08:31:23.526] [DEBUG] [Adapter]: Getting test locator from factory
[2023-05-09 08:31:23.527] [DEBUG] [Adapter]: Getting test store from factory
[2023-05-09 08:31:23.527] [DEBUG] [Adapter]: Getting test manager from factory
[2023-05-09 08:31:23.534] [DEBUG] [AngularFactory]: Creating Angular test server executor
[2023-05-09 08:31:23.534] [INFO] [AngularFactory]: Using Angular project 'cirium-profiles' at root path '/c/Projects/cirium-profiles/src/frontend' and karma config file '/c/Projects/cirium-profiles/src/frontend/karma.conf.js'
[2023-05-09 08:31:23.536] [DEBUG] [KarmaFactory]: Creating Karma http test run executor
[2023-05-09 08:31:23.536] [DEBUG] [Adapter]: Getting file watcher from factory
[2023-05-09 08:31:23.537] [DEBUG] [FileWatcher]: Creating file watchers for monitored files
[2023-05-09 08:31:23.537] [DEBUG] [FileWatcher]: Registering file handler for files: [
  "karma.conf.js"
]
[2023-05-09 08:31:23.538] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern 'karma.conf.js' using base path: /c/Projects/cirium-profiles/src/frontend
[2023-05-09 08:31:23.542] [DEBUG] [FileWatcher]: Creating file watchers for test file changes
[2023-05-09 08:31:23.542] [DEBUG] [FileWatcher]: Registering file handler for files: [
  "**/*{.,-,_}{test,spec}.{ts,js}",
  "**/{test,spec}{.,-,_}*.{ts,js}"
]
[2023-05-09 08:31:23.542] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern '**/*{.,-,_}{test,spec}.{ts,js}' using base path: /c/Projects/cirium-profiles/src/frontend
[2023-05-09 08:31:23.544] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern '**/{test,spec}{.,-,_}*.{ts,js}' using base path: /c/Projects/cirium-profiles/src/frontend
[2023-05-09 08:31:23.545] [DEBUG] [Adapter]: Creating test explorer
[2023-05-09 08:31:23.545] [DEBUG] [KarmaTestExplorer]: Test load started
[2023-05-09 08:31:23.546] [DEBUG] [KarmaTestExplorer]: Test hard refresh started
[2023-05-09 08:31:23.548] [DEBUG] [TestLocator]: Refresh requested for all spec file(s): ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-05-09 08:31:23.548] [DEBUG] [TestLocator]: No refresh currently in progress - will commence new refresh for files: ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-05-09 08:31:23.549] [DEBUG] [TestLocator]: Refreshing all spec file(s): ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-05-09 08:31:23.580] [DEBUG] [KarmaTestExplorer]: Refresh request - Test manager is not started - Starting it
[2023-05-09 08:31:23.691] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9976 acquired: 9976
[2023-05-09 08:31:23.692] [INFO] [DefaultTestManager]: Using requested --> available karma port: 9976 --> 9976
[2023-05-09 08:31:23.706] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9999 acquired: 9999
[2023-05-09 08:31:23.707] [INFO] [DefaultTestManager]: Using requested --> available karma listener socket port: 9999 --> 9999
[2023-05-09 08:31:23.707] [DEBUG] [KarmaTestListener]: Attempting to listen on port 9999
[2023-05-09 08:31:23.720] [INFO] [KarmaTestServer]: Starting karma server
[2023-05-09 08:31:23.720] [DEBUG] [AngularTestServerExecutor]: Executing server start with karma port '9976' and karma socket port '9999'
[2023-05-09 08:31:23.764] [DEBUG] [AngularTestServerExecutor]: Found '@angular/cli' module at: /c/Projects/cirium-profiles/src/frontend/node_modules/@angular/cli
[2023-05-09 08:31:23.766] [DEBUG] [AngularTestServerExecutor::SimpleProcess]: Process dqne5twmiow:
Executing command: '/home/ubuntu/.nodenv/shims/node'
with args: ["/c/Projects/cirium-profiles/src/frontend/node_modules/@angular/cli/bin/ng","test","cirium-profiles","--karma-config=/home/ubuntu/.vscode-server/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs","--progress=false","--no-watch"]
[2023-05-09 08:31:23.858] [DEBUG] [AngularTestServerExecutor::SimpleProcess]: Process dqne5twmiow - process spawned successfully with PID 22813 for command: /home/ubuntu/.nodenv/shims/node /c/Projects/cirium-profiles/src/frontend/node_modules/@angular/cli/bin/ng test cirium-profiles --karma-config=/home/ubuntu/.vscode-server/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs --progress=false --no-watch
[2023-05-09 08:31:23.864] [INFO] [KarmaTestListener]: Waiting for Karma to connect on port 9999
[2023-05-09 08:31:32.697] [DEBUG] [SimpleFileHandler]: Resolved 47 file(s) from file patterns: ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-05-09 08:31:32.699] [DEBUG] [TestLocator]: Requested --> filtered file count to refresh: 47 --> 47
[2023-05-09 08:31:32.700] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/app-config.service.spec.ts
[2023-05-09 08:31:32.741] [DEBUG] [AstTestFileParser]: Parse operation 7xm0dmrjyel: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/app-config.service.spec.ts' in 0.03 secs
[2023-05-09 08:31:32.742] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/app-user.service.spec.ts
[2023-05-09 08:31:32.794] [DEBUG] [AstTestFileParser]: Parse operation nev62xh23jl: Parsed 3 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/app-user.service.spec.ts' in 0.03 secs
[2023-05-09 08:31:32.794] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/app.component.spec.ts
[2023-05-09 08:31:32.826] [DEBUG] [AstTestFileParser]: Parse operation 9afhm94qdkk: Parsed 3 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/app.component.spec.ts' in 0.02 secs
[2023-05-09 08:31:32.826] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/script-injector-service.spec.ts
[2023-05-09 08:31:32.854] [DEBUG] [AstTestFileParser]: Parse operation vj1givi6gib: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/script-injector-service.spec.ts' in 0.01 secs
[2023-05-09 08:31:32.854] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/helpers/browserHelpers.spec.ts
[2023-05-09 08:31:32.869] [DEBUG] [AstTestFileParser]: Parse operation kop16t8p89: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/helpers/browserHelpers.spec.ts' in 0.01 secs
[2023-05-09 08:31:32.870] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/helpers/functionalHelpers.spec.ts
[2023-05-09 08:31:32.930] [DEBUG] [AstTestFileParser]: Parse operation ksekqhsunrf: Parsed 18 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/helpers/functionalHelpers.spec.ts' in 0.05 secs
[2023-05-09 08:31:32.930] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/helpers/profilesHelpers.spec.ts
[2023-05-09 08:31:32.945] [DEBUG] [AstTestFileParser]: Parse operation tcasdwc265: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/helpers/profilesHelpers.spec.ts' in 0.00 secs
[2023-05-09 08:31:32.945] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/helpers/aircraftRoutesHelpers.spec.ts
[2023-05-09 08:31:32.964] [DEBUG] [AstTestFileParser]: Parse operation vtuluik4ds: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/helpers/aircraftRoutesHelpers.spec.ts' in 0.01 secs
[2023-05-09 08:31:32.964] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/news/helpers/newsHelpers.spec.ts
[2023-05-09 08:31:32.984] [DEBUG] [AstTestFileParser]: Parse operation 2twhzfwfv8: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/news/helpers/newsHelpers.spec.ts' in 0.01 secs
[2023-05-09 08:31:32.984] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/news/services/news-shared-data.service.spec.ts
[2023-05-09 08:31:32.993] [DEBUG] [AstTestFileParser]: Parse operation esprlysw4a6: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/news/services/news-shared-data.service.spec.ts' in 0.00 secs
[2023-05-09 08:31:32.993] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/services/profiles-excel-data-service.spec.ts
[2023-05-09 08:31:33.016] [DEBUG] [AstTestFileParser]: Parse operation geh0inky28l: Parsed 6 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/services/profiles-excel-data-service.spec.ts' in 0.01 secs
[2023-05-09 08:31:33.016] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/services/profiles-preferences-service.spec.ts
[2023-05-09 08:31:33.044] [DEBUG] [AstTestFileParser]: Parse operation f9749lwke8g: Parsed 12 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/services/profiles-preferences-service.spec.ts' in 0.02 secs
[2023-05-09 08:31:33.045] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/analytics/analytics-service.spec.ts
[2023-05-09 08:31:33.066] [DEBUG] [AstTestFileParser]: Parse operation nkp9ircnhx: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/analytics/analytics-service.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.066] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/components/aircraft-routes-line-chart/aircraft-routes-line-chart.service.spec.ts
[2023-05-09 08:31:33.083] [DEBUG] [AstTestFileParser]: Parse operation y870s1c1dmf: Parsed 4 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/components/aircraft-routes-line-chart/aircraft-routes-line-chart.service.spec.ts' in 0.01 secs
[2023-05-09 08:31:33.083] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/components/aircraft-routes-metrics/aircraft-routes-metrics.component.spec.ts
[2023-05-09 08:31:33.086] [DEBUG] [AstTestFileParser]: Parse operation 75d7hadw76u: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/components/aircraft-routes-metrics/aircraft-routes-metrics.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.086] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/components/aircraft-routes-metric-toggle/aircraft-routes-metric-toggle.component.spec.ts
[2023-05-09 08:31:33.090] [DEBUG] [AstTestFileParser]: Parse operation 5mj6fhuabj5: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/components/aircraft-routes-metric-toggle/aircraft-routes-metric-toggle.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.090] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/components/aircraft-routes-table/aircraft-routes-table.service.spec.ts
[2023-05-09 08:31:33.115] [DEBUG] [AstTestFileParser]: Parse operation keh0ib8d6e: Parsed 4 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/aircraft-routes/components/aircraft-routes-table/aircraft-routes-table.service.spec.ts' in 0.02 secs
[2023-05-09 08:31:33.115] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-details-table/fleet-details-table.component.spec.ts
[2023-05-09 08:31:33.132] [DEBUG] [AstTestFileParser]: Parse operation gf8060v09t: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-details-table/fleet-details-table.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.132] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-details-table/fleet-details-table.service.spec.ts
[2023-05-09 08:31:33.152] [DEBUG] [AstTestFileParser]: Parse operation k5lmiin0yrg: Parsed 10 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-details-table/fleet-details-table.service.spec.ts' in 0.02 secs
[2023-05-09 08:31:33.152] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-jitter-chart/fleet-jitter-chart.service.spec.ts
[2023-05-09 08:31:33.169] [DEBUG] [AstTestFileParser]: Parse operation t2smz0827fq: Parsed 6 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-jitter-chart/fleet-jitter-chart.service.spec.ts' in 0.02 secs
[2023-05-09 08:31:33.169] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-progress-bar/fleet-progress-bar-age.service.spec.ts
[2023-05-09 08:31:33.182] [DEBUG] [AstTestFileParser]: Parse operation xxh77g5p9uo: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-progress-bar/fleet-progress-bar-age.service.spec.ts' in 0.01 secs
[2023-05-09 08:31:33.182] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-progress-bar/fleet-progress-bar.component.spec.ts
[2023-05-09 08:31:33.190] [DEBUG] [AstTestFileParser]: Parse operation bi85rtx5tks: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-progress-bar/fleet-progress-bar.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.190] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-progress-bar/fleet-progress-bar.service.spec.ts
[2023-05-09 08:31:33.195] [DEBUG] [AstTestFileParser]: Parse operation i7ean069sje: Parsed 4 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-progress-bar/fleet-progress-bar.service.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.195] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-grouping/fleet-grouping.component.spec.ts
[2023-05-09 08:31:33.202] [DEBUG] [AstTestFileParser]: Parse operation 6neaqeq5hvm: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-grouping/fleet-grouping.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.202] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-summary-counts/fleet-summary-counts.component.spec.ts
[2023-05-09 08:31:33.212] [DEBUG] [AstTestFileParser]: Parse operation cyuyt87h5h: Parsed 8 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-summary-counts/fleet-summary-counts.component.spec.ts' in 0.01 secs
[2023-05-09 08:31:33.212] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-stacked-bar-chart/fleet-stacked-bar-chart.service.spec.ts
[2023-05-09 08:31:33.229] [DEBUG] [AstTestFileParser]: Parse operation 8ros3zr59zs: Parsed 10 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-stacked-bar-chart/fleet-stacked-bar-chart.service.spec.ts' in 0.02 secs
[2023-05-09 08:31:33.229] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-table/fleet-age-table.service.spec.ts
[2023-05-09 08:31:33.238] [DEBUG] [AstTestFileParser]: Parse operation ck71flkzafh: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-table/fleet-age-table.service.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.238] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-table/fleet-table.component.spec.ts
[2023-05-09 08:31:33.242] [DEBUG] [AstTestFileParser]: Parse operation sywrzf5vzwa: Parsed 3 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-table/fleet-table.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.242] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-table/fleet-table.service.spec.ts
[2023-05-09 08:31:33.254] [DEBUG] [AstTestFileParser]: Parse operation qvxzpb7j06: Parsed 3 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/fleets/components/fleet-table/fleet-table.service.spec.ts' in 0.01 secs
[2023-05-09 08:31:33.254] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/ground-events/components/ground-events-chart/ground-events-chart.component.spec.ts
[2023-05-09 08:31:33.258] [DEBUG] [AstTestFileParser]: Parse operation v3txto1dq1i: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/ground-events/components/ground-events-chart/ground-events-chart.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.258] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/ground-events/components/ground-events-grouping/ground-events-grouping.component.spec.ts
[2023-05-09 08:31:33.261] [DEBUG] [AstTestFileParser]: Parse operation 1xnji36dwr: Parsed 2 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/ground-events/components/ground-events-grouping/ground-events-grouping.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.261] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/ground-events/components/ground-events-tab/ground-events-tab.component.spec.ts
[2023-05-09 08:31:33.263] [DEBUG] [AstTestFileParser]: Parse operation mrrqrqgvtd: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/ground-events/components/ground-events-tab/ground-events-tab.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.263] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/home/components/home-shortcuts/home-shortcuts.component.spec.ts
[2023-05-09 08:31:33.270] [DEBUG] [AstTestFileParser]: Parse operation e6a5nfhz9bp: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/home/components/home-shortcuts/home-shortcuts.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.270] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/home/components/home-tab/home-tab.component.spec.ts
[2023-05-09 08:31:33.271] [DEBUG] [AstTestFileParser]: Parse operation 5ir3p6n1xx4: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/home/components/home-tab/home-tab.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.271] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/home/components/home-table/home-table.component.spec.ts
[2023-05-09 08:31:33.275] [DEBUG] [AstTestFileParser]: Parse operation f0l2tkk6b58: Parsed 8 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/home/components/home-table/home-table.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.276] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/news/components/news-articles/news-articles.component.spec.ts
[2023-05-09 08:31:33.283] [DEBUG] [AstTestFileParser]: Parse operation 9x663gm0ma: Parsed 3 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/news/components/news-articles/news-articles.component.spec.ts' in 0.01 secs
[2023-05-09 08:31:33.283] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/news/components/news-article/news-article.component.spec.ts
[2023-05-09 08:31:33.295] [DEBUG] [AstTestFileParser]: Parse operation 5wtswga2p2y: Parsed 4 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/news/components/news-article/news-article.component.spec.ts' in 0.01 secs
[2023-05-09 08:31:33.296] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/news/components/news-tab/news-tab.component.spec.ts
[2023-05-09 08:31:33.299] [DEBUG] [AstTestFileParser]: Parse operation imq4lmsj51: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/news/components/news-tab/news-tab.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.299] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-filter/displayed-filter-options.pipe.spec.ts
[2023-05-09 08:31:33.304] [DEBUG] [AstTestFileParser]: Parse operation tczdiqo2kee: Parsed 5 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-filter/displayed-filter-options.pipe.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.304] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-filter/profiles-filter.component.spec.ts
[2023-05-09 08:31:33.309] [DEBUG] [AstTestFileParser]: Parse operation 7qd7kngwk26: Parsed 6 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-filter/profiles-filter.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.309] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-filter/profiles-filter.service.spec.ts
[2023-05-09 08:31:33.336] [DEBUG] [AstTestFileParser]: Parse operation mb7xzg5erkm: Parsed 15 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-filter/profiles-filter.service.spec.ts' in 0.03 secs
[2023-05-09 08:31:33.336] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-header/profiles-header.component.spec.ts
[2023-05-09 08:31:33.341] [DEBUG] [AstTestFileParser]: Parse operation ehaqyi39x1c: Parsed 3 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-header/profiles-header.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.342] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-loading/profiles-loading.component.spec.ts
[2023-05-09 08:31:33.348] [DEBUG] [AstTestFileParser]: Parse operation bosj7uyqk1: Parsed 5 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-loading/profiles-loading.component.spec.ts' in 0.01 secs
[2023-05-09 08:31:33.348] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-notice/profiles-notice.component.spec.ts
[2023-05-09 08:31:33.354] [DEBUG] [AstTestFileParser]: Parse operation we0rddkbbc: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-notice/profiles-notice.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.354] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-not-found/profiles-not-found.component.spec.ts
[2023-05-09 08:31:33.360] [DEBUG] [AstTestFileParser]: Parse operation aokqy0y0d8f: Parsed 1 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-not-found/profiles-not-found.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.360] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-organization-picker/profiles-organization-picker.component.spec.ts
[2023-05-09 08:31:33.379] [DEBUG] [AstTestFileParser]: Parse operation six7rgnurk: Parsed 10 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-organization-picker/profiles-organization-picker.component.spec.ts' in 0.02 secs
[2023-05-09 08:31:33.379] [DEBUG] [SimpleFileHandler]: Reading file async: /c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-preferences/profiles-preferences.component.spec.ts
[2023-05-09 08:31:33.388] [DEBUG] [AstTestFileParser]: Parse operation 91qrweftf5u: Parsed 5 total tests from file '/c/Projects/cirium-profiles/src/frontend/src/app/modules/shared/components/profiles-preferences/profiles-preferences.component.spec.ts' in 0.00 secs
[2023-05-09 08:31:33.389] [DEBUG] [TestLocator]: Refreshed 47 spec files from glob list in 9.84 secs: ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-05-09 08:34:09.769] [INFO] [KarmaTestListener]: Established new connection with Karma on port 9999
[2023-05-09 08:34:09.769] [DEBUG] [KarmaTestListener]: Listening for Karma events
[2023-05-09 08:34:10.113] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: file_list_modified
[2023-05-09 08:34:10.316] [DEBUG] [KarmaTestRunProcessor]: Karma server on karma port 9976 is ready for requests
[2023-05-09 08:34:14.836] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: browsers_change
[2023-05-09 08:34:14.836] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: browser_register
[2023-05-09 08:34:14.837] [DEBUG] [KarmaTestRunProcessor]: Browsers connected and ready for test execution
[2023-05-09 08:34:14.839] [INFO] [DefaultTestManager]: Discovering tests
[2023-05-09 08:34:14.839] [DEBUG] [KarmaTestRunProcessor]: Processing test discovery for test run with id: xn25bif03d
[2023-05-09 08:34:14.839] [DEBUG] [KarmaTestRunProcessor]: Started test event handling for test run Id: xn25bif03d
[2023-05-09 08:34:14.839] [DEBUG] [KarmaTestRunner]: Executing test discovery run id: xn25bif03d
[2023-05-09 08:34:14.845] [DEBUG] [KarmaHttpTestRunExecutor]: Sending karma run http request with data: {"args":["--grep=/$^/","--testRunId=xn25bif03d"],"refresh":true}
[2023-05-09 08:34:14.848] [DEBUG] [KarmaTestRunProcessor]: Test run started for browsers: Chrome Headless 103.0.5058.0 (Linux x86_64)
[2023-05-09 08:34:14.848] [DEBUG] [KarmaTestRunProcessor]: New test run starting with id 'undefined' is not for the current requested test run Id: xn25bif03d
[2023-05-09 08:34:14.849] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Beginning ambient test event processing
[2023-05-09 08:34:14.849] [DEBUG] [KarmaAutoWatchTestEventProcessor::KarmaTestEventProcessor]: Request to begin test event processing
[2023-05-09 08:34:14.849] [DEBUG] [KarmaAutoWatchTestEventProcessor::KarmaTestEventProcessor]: Proceeding to begin processing test events
[2023-05-09 08:34:14.853] [DEBUG] [KarmaHttpTestRunExecutor]: Finished sending http test run request
[2023-05-09 08:34:15.153] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: file_list_modified
[2023-05-09 08:34:15.154] [DEBUG] [KarmaTestRunProcessor]: Test run started for browsers: Chrome Headless 103.0.5058.0 (Linux x86_64)
[2023-05-09 08:34:15.154] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Aborting current ambient event processing - New test is starting
[2023-05-09 08:34:15.154] [DEBUG] [KarmaAutoWatchTestEventProcessor::KarmaTestEventProcessor]: Request to process test error event with message: New test is starting
[2023-05-09 08:34:15.154] [DEBUG] [KarmaAutoWatchTestEventProcessor::KarmaTestEventProcessor]: Request to conclude test event processing
[2023-05-09 08:34:15.154] [DEBUG] [KarmaTestRunProcessor]: Test run starting for requested test run Id: xn25bif03d
[2023-05-09 08:34:15.154] [DEBUG] [KarmaTestRunProcessor]: Starting test capture session for current requested test run Id: xn25bif03d
[2023-05-09 08:34:15.154] [DEBUG] [KarmaTestEventProcessor]: Request to begin test event processing
[2023-05-09 08:34:15.154] [DEBUG] [KarmaTestEventProcessor]: Proceeding to begin processing test events
[2023-05-09 08:34:15.155] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Aborting current ambient event processing - New test is starting
[2023-05-09 08:34:15.155] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Concluding ambient test event processing
[2023-05-09 08:34:15.155] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Retiring 0 skipped ambient test ids
[2023-05-09 08:34:15.155] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Done concluding ambient test event processing
[2023-05-09 08:34:15.156] [DEBUG] [KarmaTestRunProcessor]: Test run started for browsers: Chrome Headless 103.0.5058.0 (Linux x86_64)
[2023-05-09 08:34:15.156] [DEBUG] [KarmaTestRunProcessor]: Test run starting for requested test run Id: xn25bif03d
[2023-05-09 08:34:15.156] [DEBUG] [KarmaTestRunProcessor]: New requested test run with run id 'xn25bif03d' is starting while another one with same Id is already in progress - Continuing with existing test
[2023-05-09 08:34:23.224] [ERROR] [KarmaTestRunProcessor]: Browser error while listening for test events: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close)
[2023-05-09 08:34:23.225] [DEBUG] [KarmaTestRunProcessor]: Test error processing requested with message: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close)
[2023-05-09 08:34:23.225] [DEBUG] [KarmaTestRunProcessor]: Sending test error event to test event processor with message: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close)
[2023-05-09 08:34:23.225] [DEBUG] [KarmaTestEventProcessor]: Request to process test error event with message: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close)
[2023-05-09 08:34:23.225] [DEBUG] [KarmaTestEventProcessor]: Request to conclude test event processing
[2023-05-09 08:34:23.226] [DEBUG] [KarmaTestListener]: Closing connection with karma
[2023-05-09 08:34:23.226] [DEBUG] [KarmaTestListener]: Cleaning up connections
[2023-05-09 08:34:23.231] [DEBUG] [PortAcquisitionClient]: Releasing ports: 9999
[2023-05-09 08:34:23.233] [ERROR] [DefaultTestManager]: System component terminated with message: Karma disconnected unexpectedly: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close)
[2023-05-09 08:34:23.234] [DEBUG] [DefaultTestManager]: Test action in progress (System stop was not requested) - Initiating system stop
[2023-05-09 08:34:23.234] [DEBUG] [DefaultTestManager]: Stopping test manager
[2023-05-09 08:34:23.235] [DEBUG] [DefaultTestManager]: Stopping karma event listener
[2023-05-09 08:34:23.235] [DEBUG] [KarmaTestListener]: Request to stop karma listener - Listener is still stopping
[2023-05-09 08:34:23.235] [ERROR] [KarmaTestRunProcessor]: Could not capture Karma events - Test execution failed: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close)
[2023-05-09 08:34:23.241] [ERROR] [DefaultTestManager]: Test discovery failed: Karma disconnected unexpectedly: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close)
[2023-05-09 08:34:23.241] [ERROR] [KarmaTestExplorer]: Failed to load tests - Test discovery failed: Karma disconnected unexpectedly: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close)
[2023-05-09 08:34:23.243] [DEBUG] [NotificationHandler]: Showing 'Error' notification with actions 'Retry Test Load' and message: Failed to load tests - Test discovery failed: Karma disconnected unexpectedly: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close)
[2023-05-09 08:34:23.244] [DEBUG] [KarmaTestExplorer]: Updating loaded test store
[2023-05-09 08:34:23.244] [DEBUG] [KarmaTestExplorer]: Clearing loaded root suite
[2023-05-09 08:34:23.244] [DEBUG] [TestStore]: Clearing stored tests
[2023-05-09 08:34:23.248] [INFO] [KarmaTestExplorer]: Finished loading tests in 179.70 secs (Failed)
[2023-05-09 08:34:23.256] [DEBUG] [KarmaTestRunProcessor]: Done with test event handling for test run Id: xn25bif03d
[2023-05-09 08:34:23.284] [DEBUG] [KarmaTestListener]: Karma connection closed on port 9999
[2023-05-09 08:34:25.260] [DEBUG] [NotificationHandler]: User selected 'Show Log' for 'Error' notification: Failed to load tests - Test discovery failed: Karma disconnected unexpectedly: Browser Error - Disconnected Client disconnected from CONNECTED state (transport close) (Click to show log)

Please Provide the Following Information

OS and Version: Windows 11
Environment: WSL
Node Version: 16.14.0
VS Code Version:
Karma Version: v0.8.2
Browser and Version: Chrome No Sanbox
Frameworks: Angular
Angular Version (if using Angular): 15

@doantranthanh Please also provide a minimal github project that reproduces the issue.

@doantranthanh you don't need to share your actual project. You can create a simple basic project on GitHub and make sure it shows the karma.conf issue.

@doantranthanh please reopen if still experiencing this issue.

Sorry I am on holiday so I dont have time to create the minimal github. I will do it after I come back. thank you

@doantranthanh feel free to re-open when you do, thanks.


feat(ReadableStreams): Support for ReadableStreams e.g. from(readableStream)

Description:
Support ReadableStream and other similar objects by checking for getReader() existence. In theory this isn't foolproof, but in practice I can't see this ever actually causing issues in practice. instanceof checks don't work with cross-Realm instances and neither ReadableStream nor ReadableStreamDefaultReader implement Symbol.asyncIterator yet (which is why this custom support is needed)
Related issue (if exists):
Closes #6006

General approval from me. Pending @cartant's approval.

I had a look at adding a dtslint test for a ReadableStreamLike source to spec-dtslint/observables/from-spec.ts and found some things we might want to address in this PR.
IMO, we should export ReadableStreamLike - primarily because it's unused in the union type ObservableInput which is exported.
In the dtslint test I had to import it like this:
import { from, of, animationFrameScheduler } from 'rxjs';
import { ReadableStream } from 'web-streams-polyfill';
import { ReadableStreamLike } from '../../src/internal/util/isReadableStreamLike';

In the test, ReadableStream seemed to be match the AsyncIterable type in the ObservableInput and the inference wasn't what I expected:
it('should accept a ReadableStream', () => {
  const stream = new ReadableStream<string>({
    pull(controller) {
      controller.enqueue('x');
      controller.close();
    },
  });
  // Nope, this expectation fails 'cause Observable<any> is inferred
  const o = from(stream); // $ExpectType Observable<string>
});

However, trying to assign it to an explicitly-typed ReadableStreamLike variable - to test the inference using that type - like this:
it('should accept a ReadableStream', () => {
  const stream: ReadableStreamLike<string> = new ReadableStream<string>({
    pull(controller) {
      controller.enqueue('x');
      controller.close();
    },
  });
  const o = from(stream); // $ExpectType Observable<string>
});

fails with this TypeScript error:
Type 'ReadableStream<string>' is not assignable to type 'ReadableStreamLike<string>'.
  Types of property 'getReader' are incompatible.
    Type '{ ({ mode }: { mode: "byob"; }): ReadableStreamBYOBReader; (): ReadableStreamDefaultReader<string>; }' is not assignable to type '() => ReadableStreamDefaultReaderLike<string>'.ts(2322)

TypeScript is such a party pooper.

@cartant @jayphelps I've added a couple of commits (it should have been one, but I rushed the first one and forgot some important bits) to:

Export the ReadableStreamLike type with some documentation around what it is.
Add a dtslint test around it.
Make the ReadableStreamLike type not have compilation errors with the default ReadableStream impl's types (They're apparently more exact with how they define the iterator results for that, and it's a little annoying it doesn't pass, but whatever)


add a reference for dropout in mnist tutorial

add a reference for dropout in mnist tutorial

Can one of the admins verify this patch?

Can one of the admins verify this patch?


pgstac migration do not work

https://github.com/developmentseed/eoAPI/blob/384e35e6d2c4533a512de414612e47241074024d/deployment/handlers/db_handler.py#L80-L90

@vincentsarago that code there is only ever going to build a from scratch 0.3.4, for incremental upgrades, you should directly use https://github.com/stac-utils/pgstac/blob/main/pypgstac/pypgstac/migrate.py#L132 which will use incremental migrations.


EPIC: Fault Model updates

New crustal FM required to remove unwanted class of faults (many with 0 slip rates) + new Puysegur Subduction FM is needed.
Done When:

[x] #90
[ ] add updated crustal FM in Stirling 2010 depths to project
[x] Produce New Coulomb Rupture set with similar config to RmlsZTozMDMuMEJCOVVY D90
[ ] Produce New Coulomb Rupture set with similar config to RmlsZTo4NTkuMDM2Z2Rw Stirling 2010
[ ] add updated GEODETIC models for new Coulomb Rupture sets to project
[x] Add Puysegur FM to project (need slip rate model)
[x] Produce Puysegur Rupture Sets

@chrisbc see #89

@chrisbc see #89

@voj Pls take a look at this and recommend  what if anything needs doing here. Is one of our fault model files incorrect? Maybe raise a ticket if we need to make changes, and more importantly does this impact inversions?


[Feature]: Ligther requirement for Install when used with Connect only

Does the upstream have similar features?
No idea.
Is your feature request related to a problem? Please describe.
When using Connect to a remote end on a BrowserType, you still need to do a full install which is slow and bring a lot of unnecessary dependencies. Would be nice to reduce those needs.
Describe the solution you'd like
When doing a playwright.Playwright.playwright.BrowserType.Connect, we still need to do a playwright.Install and playwright.Run which bring requirement on the install. Ideally, we should be able to connect with no local requirement at all.
Additional context

#478


Unpack tar itself instead of using busybox

Try using https://crates.io/crates/tar-parser

Probably we should use https://crates.io/crates/tar instead, as it is used by cargo.

Preliminary support is available in df84d71 (newtar branch)

Didn't see your comment so started to work on this too =)
https://github.com/anti-social/vagga/commit/cd13b9ab280b7ee8da5ad7bdbd16eb82ce0336ed
I decided not to implement low level unpacking. Think tar library should do all that work.

It's been already merged into the master.


Set default JVM memory settings for the build

Will be picked up when building a sub-module
Doesn't work with --file option (MNG-5889)

The rat plugin wasn't working for the project - added a commit to fix it.


WIP: define and inspect ACLs

Codecov Report

Merging #49 into master will decrease coverage by 3.94%.
The diff coverage is 61.76%.

@@            Coverage Diff             @@
##           master      #49      +/-   ##
==========================================
- Coverage     100%   96.05%   -3.95%
==========================================
  Files           7        8       +1
  Lines         605      659      +54
==========================================
+ Hits          605      633      +28
- Misses          0       26      +26

Impacted Files
Coverage Δ

ldap2pg/config.py
100% <100%> (ø)
:arrow_up:

ldap2pg/utils.py
100% <100%> (ø)
:arrow_up:

ldap2pg/psql.py
100% <100%> (ø)
:arrow_up:

ldap2pg/script.py
100% <100%> (ø)
:arrow_up:

ldap2pg/acl.py
46.15% <46.15%> (ø)

ldap2pg/manager.py
91.36% <53.84%> (-8.64%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9004701...b580344. Read the comment docs.


BREAKING CHANGE AFTER CORDOVA ANDROID 7+

In the latest version of cordova android(7.0) the directory structures have changed , so i guess the hook is unable to execute the java file at the specified path
getting the following error in cordova android 7.0
Error: ENOENT: no such file or directory, open 'C:\Users\divyas\cordovaapps\latestPlatformTest\platforms\android\src\com\tkyaji\cordova\DecryptResource.java'
The same is working with cordova android 6.3.0

open plugins/cordova-plugin-crypt-file/hooks/after_prepare.js and change line 58 from  var pluginDir = path.join(platformPath, 'src'); to
var pluginDir = path.join(platformPath, 'app/src/main/java');

@SEUNAKINTOLA
Thanx it worked for me

Answare

open plugins/cordova-plugin-crypt-file/hooks/after_prepare.js and change line 58 from var pluginDir = path.join(platformPath, 'src'); to
var pluginDir = path.join(platformPath, 'app/src/main/java');

this fix the problem of build but when i try to run application show this message
net::ERR_FILE_NOT_FOUND (file:///android_asset/www/+++/index.html)
this is my info
Ionic:
ionic (Ionic CLI)  : 4.1.1 (C:\Users\yassine\AppData\Roaming\npm\node_modules\ionic)
Ionic Framework    : ionic-angular 3.9.2
@ionic/app-scripts : 3.2.0
Cordova:
cordova (Cordova CLI) : 8.0.0
Cordova Platforms     : not available
Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.2.3, (and 15 other plugins)
System:
Android SDK Tools : 26.1.1 (C:\Users\yassine\AppData\Local\Android\Sdk)
NodeJS            : v8.2.1 (C:\Program Files\nodejs\node.exe)
npm               : 5.3.0
OS                : Windows 10


Adding Hover button with bottom detail [GSSOC'23]

This is a(n):

[ ] Update to an existing Animated Button
[ ] Any Error
[x] Proposal to the Repository
[ ] Documentation / README.md changes

Details:

I would like animated button which on hovering would give bottom detail effect.
Preview
https://github.com/Spyware007/Animating-Buttons/assets/34830305/c4fb6c66-a581-43c4-8fc2-78f4436e1e4a
Pls assign this issue to me for GSSOC'23

@sohil1234 Assigned to you!

Hi, are you still working on this issue? If you've already made a PR with the changes that have been merged then please close the issue. If you have an open PR, please mention this issue number in your PR in order to link them.


Introduction to Git and GitHub

What is Git?
What is GitHub?
What is GitHub repository?

[x] add more details
[ ] add new bullet points

Thank you very much for your contribution! 😄
This issue is now resolved. 👍


Update github client dependency

What does this PR do?
Updates google/go-github to current latest version.
Supersedes https://github.com/hellofresh/janus/pull/344.
Links

https://github.com/google/go-github/blob/b1f138353a6287df5156971b3963e9107eca06a1/github/orgs_teams.go#L382
https://github.com/google/go-github/blob/cc20b8df44a10cf7439649ec5a2192f06e97fe43/github/teams.go#L356

+1


S3 pagination marker failing. Should use ContinuationToken instead of NextContinuationToken

The s3 watcher is failing on a bucket with a lot of metadata.
Error:
Parameter validation failed:
Unknown parameter in input: "NextContinuationToken", must be one of: Bucket, ContinuationToken'
Probably a cloudaux issue.
https://github.com/Netflix-Skunkworks/cloudaux/search?utf8=✓&q=NextContinuationToken
I wonder if AWS changed the name of their pagination marker for AnalyticsConfigurationList or MetricsConfigurationList or if we've had it wrong since adding analytics/metrics support.

It looks like the issue is that the S3 API uses both --
When requesting a new page, you need to send over ContinuationToken. In the response from AWS, there will be a NextContinuationToken for the next page in the results.
This appears to be newer behavior as other AWS services just use Marker that changes along with each request. CloudAux's pagination logic will need to be updated to reflect differing Request/Response pagination markers.

Addressed in: https://github.com/Netflix-Skunkworks/cloudaux/pull/18

Merged CloudAux PR. Submitting new PR to SM to up CloudAux dependency to >=1.1.1.

Addressed in #560


Create Account Page Layout

I'll create this layout

@tmoradi this is already done (create account = signup). See #3


[Question]: multi-agent not "released" when finished with its jobs

Describe your question
I have three private build agents each running a multi-agent Visual Studio Test job in a build pipeline.
Question: When one of the build agents is finished with its work, should the agent be freed to work on other jobs in other build pipelines?
I ask, because that doesn't seem to be happening. This build agent finished its work about 20 minutes ago, and it's hung waiting at the Visual Studio Test step, whilst the other two servers are busy running tests.

Versions

Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[X] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Operation system
No response
Version controll system
No response
Azure DevOps Server Version (if applicable)
No response

Hi @polyvisual thanks for reporting!
We are working on more prioritized issues at the moment, but will get back to this one soon.


When the computation load is small, openblas will use only one thread continuously.

This is by design - for small loads, the overhead of distributing the load over multiple threads and managing concurrent access to the data is usually larger than the performance gain from working in parallel. The switchover point from single
to multithreading is defined individually in the respective interface files, or more generally through the compile-time parameter GEMM_MULTITHREAD_THRESHOLD
Do you have a test case where a single thread is actually slower ?


fix: 🐛 s3 #current-cloud-backend bucket out of sync

s3 #current-cloud-backend bucket is out of sync when modifying schema during deployment

Description of changes
Added snapshot capabilities of current schema for user not to modify the original backend schema.

Issue #, if available

Description of how you validated changes
Checklist

[x] PR description included
[x] yarn test passes (for the modified packages)
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @jhockett  - E2E tests are run for this PR here - https://app.circleci.com/pipelines/github/aws-amplify/amplify-cli/12866/workflows/0e79408e-7c7c-4947-b6fc-f47a20278a38 I'd suggested to @ncarvajalc that we run e2e as a quick smoke test on the change. He's also looking in parallel into potentially snapshotting into a VFS so instead of just reducing surface area of this bug type (user could still delete amplify/.snapshot/<whatever>, but surface area is reduced. That's probably the useful context for this change.


List in documentation files that retain the hub configuration and that need to be backed up

Although the whole setup and configuration of TLJH is performed with ansible playbooks, it would be nice to know which files or directories of TLJH should be backed up on the server.

In the Configuration section, it could be nice to have the list of directories where:

TLJH is installed
the PlasmaBio extension is installed

This will mostly be about linking to the JupyterHub and TLJH documentations:

DB backup: https://jupyterhub.readthedocs.io/en/stable/admin/upgrading.html#backup-database-config
TLJH installer: http://tljh.jupyter.org/en/latest/topic/installer-actions.html#what-does-the-installer-do

Also the uninstall.yml playbook provides some information on where things are installed.

Yes @jtpio a link to the proper TLJH doc will be sufficient ;-)


Logo proposal

Hi @nunuhara
I want to create my portfolio and therefore I am contributing with open source repositories.
I can Present a logo that represents your project.
Thanks for your time
Cheers!

It doesn't really make sense for this project to have a logo, since it is just some scripts for packaging other software. Thanks though.


fix: upgrade sdk to fix device cache issue

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[X] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[X] I am not introducing a new dependency (add notes below if you are)
[N/A] I have added unit tests for the new feature or bug fix (if not, why?)
[X] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[N/A] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

make test
make docker
/compose-builder$ git checkout levski
/compose-builder$ make pull
/compose-builder$ make gen no-secty ds-onvif-camera (this generates docker-compose.yml with levski based edgex images)
Replace onvif service docker image in docker-compose.yml with your latest image created using make docker from the previous step
/compose-builder$ make up
/bin/configure-subnets.sh without error
/bin/map-credentials.sh without error
Onvif devices should be registered in Edgex
Sending any valid command to the onvif device should be successful
Restart the onvif docker service
Re-sending commands to the device as done previously should be successful

New Dependency Instructions (If applicable)

@ajcasagrande , please add the testing instructions

@ajcasagrande , please add the testing instructions

I have added testing instructions in the usual way we add in Edgex, you can modify as you need.

Codecov Report

Merging #261 (423cd15) into levski (ef0e1dc) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           levski     #261   +/-   ##
=======================================
  Coverage   31.77%   31.77%
=======================================
  Files          18       18
  Lines        1822     1822
=======================================
  Hits          579      579
  Misses       1179     1179
  Partials       64       64

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Validation looks good.


[SPARK-5677] [SPARK-5734] [SQL] [PySpark] Python DataFrame API remaining tasks

DataFrame.renameColumn

DataFrame.show() and repr

Use simpleString() rather than jsonValue in DataFrame.dtypes

createDataFrame from local Python data, including pandas.DataFrame

cc @rxin

Test build #27283 has started for   PR 4528 at commit 6cbc154.

This patch merges cleanly.

Test build #27286 has started for   PR 4528 at commit 46f5f95.

This patch merges cleanly.

Test build #27283 has finished for   PR 4528 at commit 6cbc154.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27283/
Test FAILed.

Test build #27286 has finished for   PR 4528 at commit 46f5f95.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TaskCommitDenied(
class CommitDeniedException(
  class OutputCommitCoordinatorActor(outputCommitCoordinator: OutputCommitCoordinator)

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27286/
Test FAILed.

Test build #27293 has started for   PR 4528 at commit 6ba526e.

This patch merges cleanly.

For functions taking a table name as an input parameter, can we make the parameter name consistent in this PR? There are a few places in Python where we call it name. But, in Scala/Java, we call it tableName.

@yhuai  We're trying our best to have the same API between Scala, Java and Python, but sometimes we can't, because the difference between languages. For those out of scope of API, I think we should follow the conversation for the language, for example, we should follow PEP8 in Python.
If an argument is not keyword argument, the name is not part of the API (even user could still use it as keyword argument), we should feel free to choose the proper name for it. In Python, we prefer simple things, not the verbose or complicated one.

Test build #27295 has started for   PR 4528 at commit 014acea.

This patch merges cleanly.

Test build #27293 has finished for   PR 4528 at commit 6ba526e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27293/
Test PASSed.

Test build #27295 has finished for   PR 4528 at commit 014acea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27295/
Test PASSed.

Merging in master. Thanks.


Setup automated builds

Setup GitHub actions to

build the CLI executable for macOS, Windows, and Linux when a version tag is pushed
rename the build artifacts with the version number
publish the release artifacts to the run

pushed changes direct to master


Key Handlers don't respect modifiers

The shortcuts defined here aren't respecting key modifiers. I noticed this because I generally pull up the site and then do Apple + M to minimize it, but instead of minimizing, the track mutes. The same is also true for back/forward navigation not working because left and right arrow keys are bound to next/previous track. I looked at the code a bit to see if I could take a crack at a PR, but couldn't wrap my head around how to ignore key press events that don't contain modifiers.

Thanks for logging this - I'll get it fixed by the next release!

I'd never heard of KeyboardEvent.getModfierState() before but that's what I used for this.
Here's the commit: https://github.com/generative-music/generative.fm/commit/6ea3d4b82738900b33e10e1863efa43c085aaa45.
Will get pushed out with v1.5.0 on Sunday at the latest.


Add github actions workflows

It looks like this failed during a rebase issue of several PRs, will merge this for now, since the CI is working.


Re-release with @mdi/js version v6.6.96

We'd love to use some of the icons that have been added recently!

Thanks for the reminder! I should automate this process with github actions... Ideally with a trigger from mdi/js

Bumping this, did the release go through?

Hey @leMaik – sorry to keep poking, but would you mind triggering another release?

Thanks for the reminder. Done in v5.36.0, v6.25.0 and v7.3.0 :ship:

Thank you!


Added Web.dev

Added new Optimization tool Web.dev

Thanks, @marcobiedermann for reviewing this PR.
Yes I also think  that web.dev is a great tool for optimization that's why I added it to SEO within optimization section: https://github.com/marcobiedermann/search-engine-optimization#optimization
because we don't have a separate page for optimization so.
I think this is a good fit for it.

Thanks, @marcobiedermann for merging my first PR to Awesome


Pipewire bindings/remove CLI

Right now we're shelling out to control stuff like track routing and track level. We need to preferably write some python bindings for pipewire or at the very least adjust the code to minimize the drops to CLI we're doing as they're killing our performance.
@aendra-rininsland was happy to look into writing the python bindings for pipewire

Mesbah found this bindings link, I believe this is what we're looking for


Add new "metacell" option, where metadata is extracted from the first notebook cell

(sorry, accidentally deleted original PR  #89, this is new one, with rebased branch)
Concept based on https://github.com/peijunz/ipynb2pelican, where the metadata is extracted from the first cell of the notebook.
This makes things easier because the metadata can trivially be managed from within the notebook (no need for a separate .ipynb-meta file or manually editing the .ipynb json)

note that this PR conflicts with PRs #90 and #91  because it also changes the get_html_from_filepath call in markup.py

(FYI rebased this PR now that #90 is merged)


scheduler not fully backwards compatible

The port allocations changes were not backwards compatible if you upgrade cattle to 1.4.0 but did not upgrade the scheduler service.
You should be able to run 1.4 cattle with 1.3 services.

Fresh install of rancher-server version - v1.3.3
Created few services with exposed ports ,health check enabled services, lbs and global services.
Upgrade rancher-server  to v1.4.0-rc9.
Do not upgrade any of the infrastructure stacks including scheduler which is rancher/scheduler:v0.5.1.
Allocation relating to exposed ports works fine.
Following are  few of the scenarios tested:
Scale up existing instance with exposed ports .
Create new instances with exposed ports.
service reconciles relating to stop/start/delete of instances of instance with exposed ports.
Stopping/Starting of services for release port checks.
Metadata checks for exposed ports.
Endpoint checks for exposed ports.
Following use case fails which is an existing  issue in v1.3.3  with rancher/scheduler:v0.5.1:

Create service - s1 with scale 3  exposed port say 7777 (edited)
Create another service - s2 with scale 3  exposed port say 7777 ..fails allocation as expected
Stop service - s1
service - s2  starts now as expected
Try to start S1.

Service S1 starts successfully with exposed ports pointing to instances of service S2.
Expected behavior is for S1 to not able start successfully because of ports not being made available.
This issue works as expected in rancher-sercer version - v1.4.0-rc9 with rancher/scheduler:v0.6.3


get the error "Minified React error #321;" when call react hook inside at webpart component

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

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

Additional environment details

SPFx version 1.16.1
Node.js version 16.x
React version 17.0.1
gulp version 4.0.2

Describe the bug / error
I'm trying to create a new project but I get an error
ERROR:
Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
when displaying the webpart on the sharepoint site
this happens whenever i use a react hook inside at webpart component
`
import * as React from 'react';
import styles from './HelloWorld.module.scss';
import { IHelloWorldProps } from './IHelloWorldProps';
import { escape } from '@microsoft/sp-lodash-subset';
export default class HelloWorld extends React.Component<IHelloWorldProps, {}> {
public render(): React.ReactElement {
const {
hasTeamsContext,
} = this.props;
const [id_DocClo, setId_DocClo] = React.useState("test");

return (
  <section className={`${styles.helloWorld} ${hasTeamsContext ? styles.teams : ''}`}>

Welcome to SharePoint Framework! {id_DocClo}

);

}
}
`
when I use
const [id_DocClo, setId_DocClo] = React.useState("test");
I get this error

but if I remove any mention of a react hook like useState or useEffect
I can use the normal webpart without any impediment
Steps to reproduce
1.yo @microsoft/sharepoint
2.use react hook like useState useEffect or any other hook at webpart component
3.gulp serve
Expected behavior

I was messing up when calling the hook inside the class
I managed to fix it by turning the class into a function


fix: window.backdrop option is ignored in .toggle() API (#77)

fixes #76
fixes #77

config.colors() now has optional parameter options.
view.open() will call config.colors() when entering zen-mode.

This will allow use to:

have correct highlight group (ZenBG) after colorscheme change.
respect backdrop value passed to require("zen-mode").toggle()

@folke I know you're probably busy with lazy.nvim stuffs lately,
but can you take a quick look at this please?
It's a really simple fix that does not break anything and solves 2 issues at once.

@folke Fixed and tested again with/without options. Everything works as intended now.

Thank you!


Split examples into separate packages

closes: #13
This change reduces the number of dependencies that the main package is required to import.

All examples still work.
Changes to the main package are reflected in the example package

Ya, that is a good point, it never crossed my mind about the checks. I will add in two more jobs for testing the examples.


Invalid product ID when i try RNIap.requestPurchase('SKU')

Version of react-native-iap
"react-native-iap": "^5.2.0",
Version of react-native
"react-native": "0.63.1",
Platforms you faced the error (IOS or Android or both?)
IOS & Android
Expected behavior
Purchase complete and display [Environment: Sandbox] end of the purchase
Actual behavior

Tested environment (Emulator? Real Device?)
Real Device
Steps to reproduce the behavior
// Version 3 apis - function
requestPurchase = async (sku): void => {
    try {
      RNIap.requestPurchase(sku);
    } catch (err) {
      console.warn(err.code, err.message);
    }
};

//render method
<NativeButton
    onPress={(): void =>
      this.requestPurchase('sb001')
    }>
    Request purchase for above product
</NativeButton>

Looks like you are testing our example project. You need to get invited by us to make this happen. Try to test this in your own project! Here is how you can configure iap in each project.


fix: remove rounding of x-axis location

This will perfect the spacing between candles by removing the unnecessary discretization (which was impacting both react-stockcharts and react-financial-charts).
NOTE: This is #2 of 2 pull requests. This one is focused on CandlestickSeries.tsx.

Checklist

[x] My commits follow Conventional Commits
[ ] documentation is updated

Did this finish successfully @markmcdowell  ?

It looks like it needs to be rebased, it hasn't auto merged because it's out of date.


Change ‘BUY’ to ‘INQUIRE’ button when an artwork has multiple editions.

E.g. https://www.artsy.net/artwork/josh-soskin-lone-surfer
Currently we show a ‘BUY’ button for these works, but when tapped the user gets shown an inquire form: https://github.com/artsy/eigen/blob/4f2ba8040b2f188c00dec4c703d1b180f2838b25/Artsy/View_Controllers/Artwork/ARArtworkViewController%2BButtonActions.m#L174-L179
We should reflect this by changing the button’s caption to e.g. ‘INQUIRE’. @katarinabatina do you agree?

Ideally we would have UI to select the multiple editions and simply purchase it, of course.

worth checking if that's supported in martsy

@orta @alloy in Martsy, it works perfectly. It just take me to the actual order form and I can enter my shipping details and then click "continue to checkout."

What does it look like? Is there a way to choose which edition on the page?

I've attached screenshots; yes, you can choose the edition on the page and it will take you to the checkout page, similar to how it looks like on a web browser.

@katarinabatina - to do this right, we'd want to do a more native-y feeling version of that ^

@orta I think the checkout flow can be supported by microgravity but I agree that a native view for the page needs to be devised.

I can add a edition selector to the artwork page?
I don't want to replace the full checkout process, but the artwork page we can probably still do, I'll see what they do on microgravity.
FWIW, I'd rather it be something you tap that expands, I'm not sure I'm that into the idea of scrolling through all the editions on every artwork with them.

@orta I will take a look. I don't think the editions lists are ever very long and it's nice to see what your options are before you tap buy or have to expose additional information.

adding to the milestone cause I can look after this

@alloy this story is what Amy mentioned yesterday.


Handlebars uses JSON instead of POJO

To avoid reflection.

Related https://github.com/sphereio/sphere-sunrise/issues/138

won't do it


[Enhancement][Cherry-Pick] Support column default for default value

Fixes #28857
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:disappointed: fail : 2 / 5 (40.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/service/FrontendServiceImpl.java
0
1
00.00%
[942]

:large_blue_circle:
com/starrocks/catalog/Column.java
2
4
50.00%
[573, 574]


where is markdown itself in the credits and where is its source code?

The marked MD renderer is credited in the README. Markdown itself is a specification and not "source code". I guess I could have credited John Gruber, but do we really credit every spec-creator in every piece of software? We'd be at it all day.


Fix price feed for atomic exchange

Subject of the issue
Atomic Swaps on Kwenta Exchange use the chainlink price. We should use the value number instead.

that value number is the price user will be getting when exchange atomically, systemValue is the chainlink price systemSourceRate is chainlink price of source and systemDestinateRate is the chainlink price of destination
ExchangeRatesWithDexPricing

Deliverables

Make sure atomic exchange price feed uses value

Note: The current implementation of useExchange.ts needs to be cleaned up first before adding the Atomic Price Feed. Ticket has been paused until then.

Note: The current implementation of useExchange.ts needs to be cleaned up first before adding the Atomic Price Feed. Ticket has been paused until then.
/ Edit: Refactor done, re-evaluate this PR

I will create a new PR to add this feature.


Release version 2.2 on pypi

Please release version django-configurations 2.2 with support to django 3.0 released today because django-configuration 2.1 is broken with django 3.0
I tried to tag a v2.2 version following this instructions
https://jazzband.co/about/releases#continuous-integration
but something didn't work so I removed the tag.
@jezdez can you tag version 2.2 and release it on pypi ?

Yeah, I'll do that later.

Thanks.

So yeah, @blueyed broke the deployment a while ago: https://github.com/jazzband/django-configurations/pull/209#issuecomment-561082938

So what can we do now to help with the release of django-configuration 2.2 ?

I'm working right now on moving the travis/tox config to tox-travis (#246) and then do the release. It'll happen in the next few hours.

Ok, thanks !

2.2 is out.

Thanks for the release.


[New Feat] Unify clean up branches

Snapshot diff report vs main
There is no screenshot change exist in this pull request !


[IOTDB-4364]Reduce read amplication in compaction

Description
In massive timeseries scenarios, each device has 20 timeseries, and each file has tens of thousands of devices, that is, millions of timeseries. Read throughput in cross compaction is 100~1000 times greater than write throughput.
Solution
When compacting, it is necessary to obtain devices and timeseries from all source files, as well as the metadata of each timeseries. To avoid traversing the Zesong tree multiple times, we record the intermediate nodes of the Zesong tree. Please refer to IOTDB-4364 for the experimental results.

CI is failed.


Verify if parent rev id is included in revision hash

See https://forums.couchbase.com/t/conflict-that-refuses-to-resolve/3326/9?u=traun

It does not include the rev id.  Here is the relevant code from Database.generateIDForRevision:
    // Generate a digest for this revision based on the previous revision ID, document JSON,
    // and attachment digests. This doesn't need to be secure; we just need to ensure that this
    // code consistently generates the same ID given equivalent revisions.

   try {
        md5Digest = MessageDigest.getInstance("MD5");
    } catch (NoSuchAlgorithmException e) {
        throw new RuntimeException(e);
    }

    int length = 0;
    if (previousRevisionId != null) {
        byte[] prevIDUTF8 = previousRevisionId.getBytes(Charset.forName("UTF-8"));
        length = prevIDUTF8.length;
    }
    if (length > 0xFF) {
        return null;
    }
    byte lengthByte = (byte) (length & 0xFF);
    byte[] lengthBytes = new byte[] { lengthByte };

    md5Digest.update(lengthBytes);

    int isDeleted = ((rev.isDeleted() != false) ? 1 : 0);
    byte[] deletedByte = new byte[] { (byte) isDeleted };
    md5Digest.update(deletedByte);

    List<String> attachmentKeys = new ArrayList<String>(attachments.keySet());
    Collections.sort(attachmentKeys);
    for (String key : attachmentKeys) {
        AttachmentInternal attachment = attachments.get(key);
        md5Digest.update(attachment.getBlobKey().getBytes());
    }

    if (json != null) {
        md5Digest.update(json);
    }
    byte[] md5DigestResult = md5Digest.digest();

Note that prevIDUTF8 is generated inside the if block and never used other than to take its length before going out of scope...
the comment says it is part of the algorithm but it is not.

@deanelhard Thank you very much for all your help!!

I am looking at the modified code, and it is actually still broken...
It seemed to fix the problem because it resulted in a different hash than the one previously created, but it would have the same issue if a 3-way conflict occurred again.
The problem is here:
    byte lengthByte = (byte) (length & 0xFF);
    byte[] lengthBytes = new byte[] { lengthByte };
    md5Digest.update(lengthBytes); // prefix with length byte
    if (length > 0 && prevIDUTF8 != null) {
        md5Digest.update(lengthBytes);
    }

Note that the second digest call digests the length of the parent ID for a second time rather than hashing the value of the parent ID (prevIDUTF8)


Can't get it to work after the refactor

I tested the new version, ref your comment in amerlyq/urxvt-ext-evolved#1, but thought it was best to create a new issue here, instead of commenting there.
I can't seem to get it to work though. I tried looking at the code, but I don't know how the plugin works or how to debug it, so didn't get very far. Found some things though:

let g:focau_options.events   = {'<F25>': "\e[I", '<F26>': "\e[O"}

These were F24 and F25 in the previous version. Is it correct that they have changed?
I don't use the widgets, but tried to activate them to see if they worked, and got some errors:

"g:focau_clipreg" at line 25 of widget.vim should be "g:focau_clipregs".
There are missing some 's at lines 28-31 of widget.vim.

However, none of those fix the issue. Do you have any tips for how to find out what's wrong?

F25/26 -- it ok, because on some systems/terminals escape codes for F24 and S-F12 are equivalent and I didn't want to obstruct standart keys.
You are right, I forgot to test widgets yesterday. Thanks. They fixed now.
It's my bad, that there are no tests, but I had no idea how to test autocmds and focus events anyway:(
I haven't seen how availible testframeworks could do exactly that -- only testing consequences...
To test if it works, I open two terminal and launch vim in one of them with 'number' widget enabled.
Therefore by switching focus between terminals I can affirm events working. Manual labour, heh...
Currently, I changed way events was triggered in mappings, because they had rare but nasty bugs when mapped directly.
But it seems, with new method Focus* autocmd are launched in sandbox (see :h sandbox), therefore saving buffers on FocusLost don't work, however copying registers and toggle interface elements must do. I will check what I can do about this...

Hm, I still can't get it to work properly.
The clipboard and number widgets seem to work now. The number widget only works when in insert mode though. But triggering other plugins which have registered commands to Focus* doesn't work.

Alright, I returned old way mappings worked to allow sideeffects and slightly changed them.
It seems, though, in cmdline sideeffects aren't allowed anyway. Please, see updated FAQ.
If you confirm, that in nxoi all your events work -- then it's maximum possible at current moment.
Reopen issue if there are some troubles yet not fixed.

Thanks! Now it works very well.


Multiple initial chunks with different targets for one and the same set of entries

I'm working on universal starter for angular2. It should prerender the application on a server and execute it in a web worker on a client. So I have three environments (targets):

browser main thread
web worker
server

There are several chunks that can be shared between these three environments (in parentheses I pointed on the environments where the chunk should be executed):

vendors (main_thread, web_worker, server)
app (server, web_worker)
server (server)
browser (main_thread)
worker (web_worker)

I don't want a web worker to load its own vendors chunk, which differs from the main thread vendors chunk only in a name of a callback (webpackChunk(cunkIds, cb) vs webpackJsonp(chunkIds, cb)). A vendors chunk can be huge, no need for extra traffic. Also there is no need to compile the same chunks (app and vendors) several times for different targets (and I would like to have only one config after all). So I want something like this:
const TargetPlugin = webpack.optimize.TargetPlugin;
const CommonsChunkPlugin = webpack.optimize.CommonsChunkPlugin;

module.exports = {
  entry: {
    vendors: 'vendors.js',
    app: 'app.js',
    server: 'server.js',
    browser: 'browser.js',
    worker: 'worker.js'
  },
  output: { /* ... */ },
  plugins: [
    // remove duplicate "app"" code from 'server', 'browser' and 'worker',
    new CommonsChunkPlugin({ name: 'app', chunks: ['server', 'browser', 'worker'], minChunks: Infinity }),
    // remove duplicate "vendor" code from 'server', 'browser' and 'worker',
    new CommonsChunkPlugin({ name: 'vendor', chunks: ['server', 'browser', 'worker'], minChunks: Infinity }),
    // Initial chunk for server
    new TargetPlugin({ name: 'boot_server', chunk: 'server', target: 'node'}),
    // Initial chunk for browser's main thread
    new TargetPlugin({ name: 'boot_browser', chunk: 'browser', target: 'web' }),
    // Initial chunk for web worker
    new TargetPlugin({ name: 'boot_worker', chunk: 'client', target: 'webworker' }),
  ],
};

Because of  the TargetPlugin the app, vendor, server, browser and worker chunks are not initial chunks anymore. They are normal chunks and can be used with any of boot_* chunks (which are initial now). Could you tell me can something like this be implemented?

Hi,
Did you manage to proceed with this?

@alexpods @bebraw where you able to implement this?


WasiP1 Support (only a subset for now)

I've still got some work to do here. But opening up now. API looks like this.
var fakeStdin = new ByteArrayInputStream("Benjamin".getBytes());
var wasiOpts = WasiOptions.builder().setStdout(System.out).setStdin(fakeStdin);
var wasi = new WasiP1(wasiOpts);
var imports = new HostImports(wasi.toHostFunctions());
var instance = Module.build(new File("src/test/resources/compiled/greet-wasi.rs.wasm"))
                        .instantiate(imports);
var run = instance.getExport("_start");
run.apply();

Outputs can be set as PrintStreams and stdin can be passed an InputStream. You can also inherit from the parent process with: WasiOptions.build().inheritSystem().

Feel free to ping me for assistance if you have any trouble with Maven :+1: happy to help!

Feel free to ping me for assistance if you have any trouble with Maven 👍 happy to help!

be careful what you wish for 😈

I moved it to it's own package. Eventually we should move this to it's own module. Maybe have it's own unit tests and stuff. it's a bit too much for me at the moment. I want to just use this to more easily test the runtime.

Another follow-up task is gonna be documentation, updating the readme etc., not required in this PR as it's already big enough.

Another follow-up task is gonna be documentation, updating the readme etc., not required in this PR as it's already big enough.

Agreed. I think let's hold off until we're more confident though. I'd prefer for this to be hidden for the time being. I just want to use it to get some more modules in here for testing purposes.


Critical Path Add 0 weight causal edges for kernel launches

What does this PR do?
When we modify the CPGraph for performance simulations, we do not want GPU kernels to start before their CPU launch counterparts. To prevent this we always add a 0 weight edge for runtime launch -> kernel the launch delay is not in critical path.
Details

Add a helper to add launch edges.
Include 0 weight edges whenever launch edges are not added.
Handle overlaying these edges.

note for overlaid trace
Displaying these edges is disabled in overlaid trace to avoid confusing users :) The environment variable CRITICAL_PATH_SHOW_ZERO_WEIGHT_LAUNCH_EDGE=1 will help you enable it.
Test notebook
We can see for the simple add example we have
All the launch edges are now shown

You can see for this epilogues kernel, there is a 0 weight edge

While we have a kernel-kernel edge

Critical path is not impacted as shown

Unit test
Unit tests are also working and validating critical path.
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos, doc improvements)

[x] N/A

[x] Did you write any new necessary tests?

[ ] N/A

[x] Did you make sure to update the docs?

[ ] N/A

[ ] Did you update the changelog?

[ ] N/A

Codecov Report
Attention: Patch coverage is 96.77419% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 90.57%. Comparing base (ec3abf1) to head (2b491e6).

Files
Patch %
Lines

hta/analyzers/critical_path_analysis.py
95.45%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #106      +/-   ##
==========================================
+ Coverage   90.53%   90.57%   +0.03%
==========================================
  Files          43       43
  Lines        3899     3924      +25
==========================================
+ Hits         3530     3554      +24
- Misses        369      370       +1

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


modified readme and index test

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

https://github.com/Afifa156/dp-203-azure-data-engineer.git


ignore exp dirs in recipe directories

Fixes #149.
Wasn't really sure what was the best place in .gitignore for these lines

Sure, I just moved it below uploader_info.yml. Is this alright?


Game quits after rendering calls on main rendering device if multithreaded rendering is enabled

Godot version
v4.1.beta3.official [ada712e06]
System information
Godot v4.1.beta3 - Windows 10.0.22621 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 2080 with Max-Q Design (NVIDIA; <IP_ADDRESS>61) - Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 Threads)
Issue description
I am using the main renderingdevice to do offscreen drawing to a texture. If I use the same code on a local rendering device created using RenderingServer.create_local_rendering_device(), it works fine, but the moment I do anything on the main rendering device (from RenderingServer.get_rendering_device() ), my code will run for one or two frames, then the game quits silently.
I've narrowed it down with a passthrough shader and no actual draw calls - just any call to draw_list_begin and draw_list_end, and it dies.
If you use single threaded renderingdevice, it works.
I feel like this is a good test of the stability of the vulkan multithreading ( see https://github.com/godotengine/godot-proposals/discussions/7163 ) - if we want to allow multithreaded use of a single renderingdevice, then this should work.
Steps to reproduce
Hit play on the project below. It will hopefully print out before, inside, after, then silently quit. Does on mine at least, on dev builds and on 4.1b3. If you set rendering to single-threaded (safe or unsafe), then it works happily.
Minimal reproduction project
crashtest.zip

I can confirm this on 4.1.dev d95b516d312a9f3930a96c0fdd51cf975345f16f (Linux, GeForce RTX 4090 with NVIDIA 535.54.03).
Backtrace:
true
before
inside
after
before
inside
after
ERROR: Condition "draw_list_current_subpass >= draw_list_subpass_count - 1" is true. Returning: INVALID_FORMAT_ID
   at: draw_list_switch_to_next_pass (drivers/vulkan/rendering_device_vulkan.cpp:7474)
ERROR: Condition "!dl" is true.
   at: draw_list_bind_uniform_set (drivers/vulkan/rendering_device_vulkan.cpp:7201)
ERROR: Condition "!dl" is true.
   at: draw_list_bind_uniform_set (drivers/vulkan/rendering_device_vulkan.cpp:7201)
ERROR: Condition "!dl" is true.
   at: draw_list_bind_uniform_set (drivers/vulkan/rendering_device_vulkan.cpp:7201)
ERROR: Condition "draw_list_current_subpass >= draw_list_subpass_count - 1" is true. Returning: INVALID_FORMAT_ID
   at: draw_list_switch_to_next_pass (drivers/vulkan/rendering_device_vulkan.cpp:7474)
ERROR: Condition "!dl" is true.
   at: draw_list_bind_render_pipeline (drivers/vulkan/rendering_device_vulkan.cpp:7127)
ERROR: Condition "!dl" is true.
   at: draw_list_bind_uniform_set (drivers/vulkan/rendering_device_vulkan.cpp:7201)
ERROR: Condition "!dl" is true.
   at: draw_list_bind_uniform_set (drivers/vulkan/rendering_device_vulkan.cpp:7201)
ERROR: Condition "!dl" is true.
   at: draw_list_bind_uniform_set (drivers/vulkan/rendering_device_vulkan.cpp:7201)
ERROR: Condition "!dl" is true.
   at: draw_list_bind_uniform_set (drivers/vulkan/rendering_device_vulkan.cpp:7201)
ERROR: Condition "!dl" is true.
   at: draw_list_bind_index_array (drivers/vulkan/rendering_device_vulkan.cpp:7274)
ERROR: Condition "!dl" is true.
   at: draw_list_set_push_constant (drivers/vulkan/rendering_device_vulkan.cpp:7308)
ERROR: Condition "!dl" is true.
   at: draw_list_draw (drivers/vulkan/rendering_device_vulkan.cpp:7326)
ERROR: Caller thread can't call this function in this node (/root). Use call_deferred() or call_thread_group() instead.
   at: propagate_notification (./scene/main/node.cpp:2208)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.1.rc.custom_build (d95b516d312a9f3930a96c0fdd51cf975345f16f)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib64/libc.so.6(+0x3db70) [0x7f62ec25fb70] (??:0)
[2] /lib64/libnvidia-glcore.so.535.54.03(+0x18ab0fe) [0x7f62b84ab0fe] (??:0)
[3] /lib64/libnvidia-glcore.so.535.54.03(+0x18add01) [0x7f62b84add01] (??:0)
[4] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x49ab61b] (/home/hugo/Documents/Git/godotengine/godot/drivers/vulkan/rendering_device_vulkan.cpp:7635)
[5] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9476440] (/home/hugo/Documents/Git/godotengine/godot/servers/rendering/renderer_rd/forward_mobile/render_forward_mobile.cpp:1037 (discriminator 1))
[6] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9280f72] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/renderer_rd/renderer_scene_render_rd.cpp:1042)
[7] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x8fba9b8] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/renderer_scene_cull.cpp:3316 (discriminator 4))
[8] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x8fa35ef] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/renderer_scene_cull.cpp:2589 (discriminator 1))
[9] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x90033fb] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/renderer_viewport.cpp:212 (discriminator 1))
[10] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9003a9b] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/renderer_viewport.cpp:279)
[11] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x90098d4] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/renderer_viewport.cpp:729)
[12] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9073618] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/rendering_server_default.cpp:92)
[13] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x907663d] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/rendering_server_default.cpp:354)
[14] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x910665c] (/home/hugo/Documents/Git/godotengine/godot/./core/templates/command_queue_mt.h:322)
[15] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x3380ecc] (/home/hugo/Documents/Git/godotengine/godot/./core/templates/command_queue_mt.h:374)
[16] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x3381037] (/home/hugo/Documents/Git/godotengine/godot/./core/templates/command_queue_mt.h:414)
[17] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x907673b] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/rendering_server_default.cpp:373)
[18] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x907666c] (/home/hugo/Documents/Git/godotengine/godot/./servers/rendering/rendering_server_default.cpp:363)
[19] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9a730d6] (/home/hugo/Documents/Git/godotengine/godot/./core/os/thread.cpp:63)
[20] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9a91bf3] (/usr/include/c++/13/bits/invoke.h:61)
[21] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9a91abc] (/usr/include/c++/13/bits/invoke.h:97)
[22] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9a91977] (/usr/include/c++/13/bits/std_thread.h:292)
[23] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9a8eb26] (/usr/include/c++/13/bits/std_thread.h:299)
[24] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0x9a8ca32] (/usr/include/c++/13/bits/std_thread.h:244)
[25] /home/hugo/Documents/Git/godotengine/godot/bin/godot.linuxbsd.editor.x86_64() [0xa5f50e3] (msdf-error-correction.cpp:?)
[26] /lib64/libc.so.6(+0x8c907) [0x7f62ec2ae907] (??:0)
[27] /lib64/libc.so.6(+0x112870) [0x7f62ec334870] (??:0)
-- END OF BACKTRACE --
================================================================


Bug/delete old admin dashboard

Description

What work was done?
Deleted previous work for Admin Dashboard

Why was this work done?
A new Admin Dashboard will be created from scratch

What feature / user story is it for?
https://trello.com/c/PWdISCLn/819-as-an-admin-i-want-a-page-where-i-can-manage-our-site-so-that-i-can-have-a-secure-place-to-manage-the-site

eslint reformated styles file DeveloperOperations.less. css is unchanged

https://www.loom.com/share/906a30c7fdc44b15ab70347301d5a202
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)

Change Status

[ ] Complete, tested, ready to review and merge

Checklist

[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer
[x] My changes generate no new warnings
[x] There are no merge conflicts

@Kishkuman13 Got it, thanks! I also deleted that DeveloperOperations.less file since it was part of the work to be replaced


Inventory Device type detection

as part of conducting the device inventory detect the device type to populate the ITAM database.
Requirements

[ ] Playbook updated
[ ] Detects Computer

marked this issue as related to #74

added 2m of time spent

In GitLab by @jasonpagetas on Jul 20, 2024, 23:49
added 3m of time spent

In GitLab by @jasonpagetas on Jul 20, 2024, 23:49
During the gather facts stage one of the returns is: (This was on a laptop)

  "ansible_form_factor": "Notebook",

In GitLab by @jasonpagetas on Jul 21, 2024, 24:50
Even if it doesn't you can still gather the hardware facts using something like this

---
- name: Collect Form factor
  hosts: localhost
  become: false
  gather_facts: false
  tasks:
  - name: Collect 'hardware' only facts!
    setup:
      gather_subset:
      - hardware
  - name: debug
    debug:
      var: hostvars[inventory_hostname].ansible_form_factor

added 2m of time spent

this will need to be confirmed via the docs if the value is always populated.

In GitLab by @jasonpagetas on Jul 21, 2024, 24:54
This is the link to where i mentioned the values that can be returned for ansible_form_factor
github link


Adds prints of rna information to the list command

This is the fix for #1390

+1

+1

@kozbo btw topic branches should be pushed to your github server repo, not the ga4gh server repo

Thanks for catching that @dcolligan, I will avoid it next time.