Karma Test Explorer Fails to Show Tests Angular 8

Describe the Bug
Karma Test Explorer fails to load
Steps to Reproduce the Behavior

Create a brand new Angular app using Angular 8
Open in VSCode with karma-test-explorer installed
Open test viewer
Tests fail to load

Describe the Expected Behavior
Tests appear in the karma-test-explorer panel
Provide Debug Logs

With the karmaTestExplorer.logLevel set to debug, please capture and attach the logs from all the Karma Test Explorer Output channels when the issue occurs.
Attached Angular 8 debug logs

[2023-11-17 16:59:38.630] [DEBUG] [Adapter]: Creating server output channel
[2023-11-17 16:59:38.630] [DEBUG] [Adapter]: Creating port acquisition client
[2023-11-17 16:59:38.630] [DEBUG] [Adapter]: Creating debugger
[2023-11-17 16:59:38.630] [DEBUG] [Adapter]: Creating project commands handler
[2023-11-17 16:59:38.630] [DEBUG] [Commands]: Registering command 'ShowLog' as namespaced command 'karmaTestExplorer.angular-tour-of-heroes: angular-tour-of-heroes:ShowLog
[2023-11-17 16:59:38.630] [DEBUG] [Commands]: Registering command 'Reset' as namespaced command 'karmaTestExplorer.angular-tour-of-heroes: angular-tour-of-heroes:Reset
[2023-11-17 16:59:38.630] [DEBUG] [Adapter]: Creating notifications handler
[2023-11-17 16:59:38.630] [DEBUG] [Adapter]: Creating test emitters
[2023-11-17 16:59:38.631] [DEBUG] [Adapter]: Assembling new test explorer
[2023-11-17 16:59:38.631] [DEBUG] [Adapter]: Re/creating test explorer with extension configuration: {
  "logger": {
    "loggerName": "ExtensionConfig",
    "appender": {
      "outputChannelName": "Karma Test Explorer (angular-tour-of-heroes: angular-tour-of-heroes)",
      "options": {
        "enabled": true,
        "lazyCreate": false
      },
      "outputChannel": {
        "name": "Karma Test Explorer (angular-tour-of-heroes: angular-tour-of-heroes)"
      }
    },
    "logLevel": "debug"
  },
  "projectType": "angular",
  "projectName": "angular-tour-of-heroes",
  "projectPath": "/Users/kevindiem/workspace/angular-tour-of-heroes",
  "projectInstallRootPath": "/Users/kevindiem/workspace/angular-tour-of-heroes",
  "projectKarmaConfigFilePath": "/Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js",
  "baseKarmaConfFilePath": "/Users/kevindiem/.vscode/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"
    ]
  },
  "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": "/Users/kevindiem/workspace/angular-tour-of-heroes"
  },
  "reloadOnChangedFiles": [],
  "defaultDebugPort": 9222,
  "excludeFiles": [
    "**/node_modules/**/*"
  ]
}
[2023-11-17 16:59:38.631] [DEBUG] [Adapter]: Creating main factory
[2023-11-17 16:59:38.631] [DEBUG] [MainFactory]: Detecting test framework from karma config file: /Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js
[2023-11-17 16:59:38.631] [DEBUG] [SimpleFileHandler]: Reading file synchronously: /Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js
[2023-11-17 16:59:38.631] [DEBUG] [MainFactory]: Detected frameworks from karma config: jasmine, @angular-devkit/build-angular
[2023-11-17 16:59:38.631] [DEBUG] [MainFactory]: Detected test framework: jasmine
[2023-11-17 16:59:38.631] [INFO] [MainFactory]: Using test framework: jasmine (auto-detected)
[2023-11-17 16:59:38.631] [DEBUG] [MainFactory]: Creating test helper
[2023-11-17 16:59:38.631] [DEBUG] [MainFactory]: Creating process handler
[2023-11-17 16:59:38.631] [DEBUG] [MainFactory]: Creating test locator
[2023-11-17 16:59:38.631] [DEBUG] [MainFactory]: Creating AST test definition provider
[2023-11-17 16:59:38.631] [DEBUG] [MainFactory]: Creating test store
[2023-11-17 16:59:38.631] [DEBUG] [Adapter]: Getting process handler from factory
[2023-11-17 16:59:38.631] [DEBUG] [Adapter]: Getting test locator from factory
[2023-11-17 16:59:38.631] [DEBUG] [Adapter]: Getting test store from factory
[2023-11-17 16:59:38.631] [DEBUG] [Adapter]: Getting test manager from factory
[2023-11-17 16:59:38.631] [DEBUG] [AngularFactory]: Creating Angular test server executor
[2023-11-17 16:59:38.631] [INFO] [AngularFactory]: Using Angular project 'angular-tour-of-heroes' at root path '/Users/kevindiem/workspace/angular-tour-of-heroes' and karma config file '/Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js'
[2023-11-17 16:59:38.631] [DEBUG] [KarmaFactory]: Creating Karma http test run executor
[2023-11-17 16:59:38.631] [DEBUG] [Adapter]: Getting file watcher from factory
[2023-11-17 16:59:38.631] [DEBUG] [FileWatcher]: Creating file watchers for monitored files
[2023-11-17 16:59:38.631] [DEBUG] [FileWatcher]: Registering file handler for files: [
  "karma.conf.js"
]
[2023-11-17 16:59:38.632] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern 'karma.conf.js' using base path: /Users/kevindiem/workspace/angular-tour-of-heroes
[2023-11-17 16:59:38.632] [DEBUG] [FileWatcher]: Creating file watchers for test file changes
[2023-11-17 16:59:38.632] [DEBUG] [FileWatcher]: Registering file handler for files: [
  "**/*{.,-,_}{test,spec}.{ts,js}",
  "**/{test,spec}{.,-,_}*.{ts,js}"
]
[2023-11-17 16:59:38.632] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern '**/*{.,-,_}{test,spec}.{ts,js}' using base path: /Users/kevindiem/workspace/angular-tour-of-heroes
[2023-11-17 16:59:38.632] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern '**/{test,spec}{.,-,_}*.{ts,js}' using base path: /Users/kevindiem/workspace/angular-tour-of-heroes
[2023-11-17 16:59:38.632] [DEBUG] [Adapter]: Creating test explorer
[2023-11-17 16:59:38.632] [DEBUG] [KarmaTestExplorer]: Test load started
[2023-11-17 16:59:38.632] [DEBUG] [KarmaTestExplorer]: Test hard refresh started
[2023-11-17 16:59:38.632] [DEBUG] [TestLocator]: Refresh requested for all spec file(s): ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 16:59:38.632] [DEBUG] [TestLocator]: No refresh currently in progress - will commence new refresh for files: ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 16:59:38.632] [DEBUG] [TestLocator]: Refreshing all spec file(s): ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 16:59:38.633] [DEBUG] [KarmaTestExplorer]: Refresh request - Test manager is not started - Starting it
[2023-11-17 16:59:38.637] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9976 acquired: 9977
[2023-11-17 16:59:38.637] [INFO] [DefaultTestManager]: Using requested --> available karma port: 9976 --> 9977
[2023-11-17 16:59:38.638] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9999 acquired: 10000
[2023-11-17 16:59:38.638] [INFO] [DefaultTestManager]: Using requested --> available karma listener socket port: 9999 --> 10000
[2023-11-17 16:59:38.638] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9222 acquired: 9223
[2023-11-17 16:59:38.638] [INFO] [DefaultTestManager]: Using requested --> available debug port: 9222 --> 9223
[2023-11-17 16:59:38.638] [DEBUG] [KarmaTestListener]: Attempting to listen on port 10000
[2023-11-17 16:59:38.639] [INFO] [KarmaTestServer]: Starting karma server
[2023-11-17 16:59:38.639] [DEBUG] [AngularTestServerExecutor]: Executing server start with karma port '9977' and karma socket port '10000'
[2023-11-17 16:59:38.639] [WARN] [AngularTestServerExecutor]: Could not locate '@angular/cli' module globally or under project at '/Users/kevindiem/workspace/angular-tour-of-heroes': Error: Cannot find module<EMAIL_ADDRESS>Require stack:
- /Users/kevindiem/.vscode/extensions/lucono.karma-test-explorer-0.8.2/dist/main.cjs
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-amd.js
- /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js
-
[2023-11-17 16:59:38.639] [ERROR] [KarmaTestServer]: Failed to start server for requested karmaPort 9977 and karmaSocketPort 10000: Error: Angular CLI does not seem to be installed. You may need to install your project dependencies or specify the right path to your project using the karmaTestExplorer.projectWorkspaces setting.
[2023-11-17 16:59:38.639] [INFO] [KarmaTestListener]: Waiting for Karma to connect on port 10000
[2023-11-17 16:59:38.645] [DEBUG] [PortAcquisitionClient]: Releasing ports: 9977
[2023-11-17 16:59:38.645] [DEBUG] [PortAcquisitionClient]: Releasing ports: 9223
[2023-11-17 16:59:38.645] [ERROR] [DefaultTestManager]: System component terminated with message: Karma server failed to start: Angular CLI does not seem to be installed. You may need to install your project dependencies or specify the right path to your project using the karmaTestExplorer.projectWorkspaces setting.
[2023-11-17 16:59:38.645] [DEBUG] [DefaultTestManager]: Test action in progress (System stop was not requested) - Initiating system stop
[2023-11-17 16:59:38.645] [DEBUG] [DefaultTestManager]: Stopping test manager
[2023-11-17 16:59:38.645] [DEBUG] [DefaultTestManager]: Stopping karma event listener
[2023-11-17 16:59:38.645] [DEBUG] [KarmaTestListener]: Closing connection with karma
[2023-11-17 16:59:38.645] [DEBUG] [KarmaTestListener]: Cleaning up connections
[2023-11-17 16:59:38.645] [DEBUG] [KarmaTestListener]: Karma connection closed on port 10000
[2023-11-17 16:59:38.646] [ERROR] [DefaultTestManager]: Error: Karma server failed to start: Angular CLI does not seem to be installed. You may need to install your project dependencies or specify the right path to your project using the karmaTestExplorer.projectWorkspaces setting.
[2023-11-17 16:59:38.646] [DEBUG] [DefaultTestManager]: Stopping test manager
[2023-11-17 16:59:38.646] [DEBUG] [DefaultTestManager]: Karma event listener is already stopped
[2023-11-17 16:59:38.646] [DEBUG] [DefaultTestManager]: Karma server is already stopped
[2023-11-17 16:59:38.646] [DEBUG] [DefaultTestManager]: Stopped test manager
[2023-11-17 16:59:38.646] [ERROR] [KarmaTestExplorer]: Failed to load tests - Karma server failed to start: Angular CLI does not seem to be installed. You may need to install your project dependencies or specify the right path to your project using the karmaTestExplorer.projectWorkspaces setting.
[2023-11-17 16:59:38.646] [DEBUG] [NotificationHandler]: Showing 'Error' notification with actions 'Retry Test Load' and message: Failed to load tests - Karma server failed to start: Angular CLI does not seem to be installed. You may need to install your project dependencies or specify the right path to your project using the karmaTestExplorer.projectWorkspaces setting.
[2023-11-17 16:59:38.646] [DEBUG] [KarmaTestExplorer]: Updating loaded test store
[2023-11-17 16:59:38.646] [DEBUG] [KarmaTestExplorer]: Clearing loaded root suite
[2023-11-17 16:59:38.646] [DEBUG] [TestStore]: Clearing stored tests
[2023-11-17 16:59:38.647] [INFO] [KarmaTestExplorer]: Finished loading tests in 0.01 secs (Failed)
[2023-11-17 16:59:39.460] [DEBUG] [SimpleFileHandler]: Resolved 2 file(s) from file patterns: ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 16:59:39.460] [DEBUG] [TestLocator]: Requested --> filtered file count to refresh: 2 --> 2
[2023-11-17 16:59:39.460] [DEBUG] [SimpleFileHandler]: Reading file async: /Users/kevindiem/workspace/angular-tour-of-heroes/e2e/src/app.e2e-spec.ts
[2023-11-17 16:59:39.475] [DEBUG] [AstTestFileParser]: Parse operation hquhg8bkimb: Parsed 1 total tests from file '/Users/kevindiem/workspace/angular-tour-of-heroes/e2e/src/app.e2e-spec.ts' in 0.00 secs
[2023-11-17 16:59:39.475] [DEBUG] [SimpleFileHandler]: Reading file async: /Users/kevindiem/workspace/angular-tour-of-heroes/src/app/app.component.spec.ts
[2023-11-17 16:59:39.477] [DEBUG] [AstTestFileParser]: Parse operation i62elow0ld: Parsed 3 total tests from file '/Users/kevindiem/workspace/angular-tour-of-heroes/src/app/app.component.spec.ts' in 0.00 secs
[2023-11-17 16:59:39.477] [DEBUG] [TestLocator]: Refreshed 2 spec files from glob list in 0.84 secs: ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 17:11:53.356] [INFO] [Adapter]: Resetting adapter
[2023-11-17 17:11:53.356] [DEBUG] [KarmaTestExplorer]: Test operation cancellation requested - Aborting any currently running test operation
[2023-11-17 17:11:53.356] [DEBUG] [DefaultTestManager]: Stopping test manager
[2023-11-17 17:11:53.357] [DEBUG] [DefaultTestManager]: Karma event listener is already stopped
[2023-11-17 17:11:53.357] [DEBUG] [DefaultTestManager]: Karma server is already stopped
[2023-11-17 17:11:53.357] [DEBUG] [DefaultTestManager]: Stopped test manager
[2023-11-17 17:11:53.361] [DEBUG] [DefaultTestManager]: Stopping test manager
[2023-11-17 17:11:53.361] [DEBUG] [DefaultTestManager]: Karma event listener is already stopped
[2023-11-17 17:11:53.361] [DEBUG] [DefaultTestManager]: Karma server is already stopped
[2023-11-17 17:11:53.361] [DEBUG] [DefaultTestManager]: Stopped test manager
[2023-11-17 17:11:53.363] [DEBUG] [Adapter]: Assembling new test explorer
[2023-11-17 17:11:53.363] [DEBUG] [Adapter]: Re/creating test explorer with extension configuration: {
  "logger": {
    "loggerName": "ExtensionConfig",
    "appender": {
      "outputChannelName": "Karma Test Explorer (angular-tour-of-heroes: angular-tour-of-heroes)",
      "options": {
        "enabled": true,
        "lazyCreate": false
      },
      "outputChannel": {
        "name": "Karma Test Explorer (angular-tour-of-heroes: angular-tour-of-heroes)"
      }
    },
    "logLevel": "debug"
  },
  "projectType": "angular",
  "projectName": "angular-tour-of-heroes",
  "projectPath": "/Users/kevindiem/workspace/angular-tour-of-heroes",
  "projectInstallRootPath": "/Users/kevindiem/workspace/angular-tour-of-heroes",
  "projectKarmaConfigFilePath": "/Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js",
  "baseKarmaConfFilePath": "/Users/kevindiem/.vscode/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"
    ]
  },
  "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": "/Users/kevindiem/workspace/angular-tour-of-heroes"
  },
  "reloadOnChangedFiles": [],
  "defaultDebugPort": 9222,
  "excludeFiles": [
    "**/node_modules/**/*"
  ]
}
[2023-11-17 17:11:53.363] [DEBUG] [Adapter]: Creating main factory
[2023-11-17 17:11:53.363] [DEBUG] [MainFactory]: Detecting test framework from karma config file: /Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js
[2023-11-17 17:11:53.363] [DEBUG] [SimpleFileHandler]: Reading file synchronously: /Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js
[2023-11-17 17:11:53.365] [DEBUG] [MainFactory]: Detected frameworks from karma config: jasmine, @angular-devkit/build-angular
[2023-11-17 17:11:53.365] [DEBUG] [MainFactory]: Detected test framework: jasmine
[2023-11-17 17:11:53.365] [INFO] [MainFactory]: Using test framework: jasmine (auto-detected)
[2023-11-17 17:11:53.365] [DEBUG] [MainFactory]: Creating test helper
[2023-11-17 17:11:53.365] [DEBUG] [MainFactory]: Creating process handler
[2023-11-17 17:11:53.365] [DEBUG] [MainFactory]: Creating test locator
[2023-11-17 17:11:53.365] [DEBUG] [MainFactory]: Creating AST test definition provider
[2023-11-17 17:11:53.365] [DEBUG] [MainFactory]: Creating test store
[2023-11-17 17:11:53.365] [DEBUG] [Adapter]: Getting process handler from factory
[2023-11-17 17:11:53.365] [DEBUG] [Adapter]: Getting test locator from factory
[2023-11-17 17:11:53.365] [DEBUG] [Adapter]: Getting test store from factory
[2023-11-17 17:11:53.365] [DEBUG] [Adapter]: Getting test manager from factory
[2023-11-17 17:11:53.365] [DEBUG] [AngularFactory]: Creating Angular test server executor
[2023-11-17 17:11:53.365] [INFO] [AngularFactory]: Using Angular project 'angular-tour-of-heroes' at root path '/Users/kevindiem/workspace/angular-tour-of-heroes' and karma config file '/Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js'
[2023-11-17 17:11:53.366] [DEBUG] [KarmaFactory]: Creating Karma http test run executor
[2023-11-17 17:11:53.366] [DEBUG] [Adapter]: Getting file watcher from factory
[2023-11-17 17:11:53.366] [DEBUG] [FileWatcher]: Creating file watchers for monitored files
[2023-11-17 17:11:53.366] [DEBUG] [FileWatcher]: Registering file handler for files: [
  "karma.conf.js"
]
[2023-11-17 17:11:53.366] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern 'karma.conf.js' using base path: /Users/kevindiem/workspace/angular-tour-of-heroes
[2023-11-17 17:11:53.366] [DEBUG] [FileWatcher]: Creating file watchers for test file changes
[2023-11-17 17:11:53.366] [DEBUG] [FileWatcher]: Registering file handler for files: [
  "**/*{.,-,_}{test,spec}.{ts,js}",
  "**/{test,spec}{.,-,_}*.{ts,js}"
]
[2023-11-17 17:11:53.366] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern '**/*{.,-,_}{test,spec}.{ts,js}' using base path: /Users/kevindiem/workspace/angular-tour-of-heroes
[2023-11-17 17:11:53.366] [DEBUG] [FileWatcher]: Creating file watcher for file or pattern '**/{test,spec}{.,-,_}*.{ts,js}' using base path: /Users/kevindiem/workspace/angular-tour-of-heroes
[2023-11-17 17:11:53.366] [DEBUG] [Adapter]: Creating test explorer
[2023-11-17 17:11:53.366] [DEBUG] [KarmaTestExplorer]: Test load started
[2023-11-17 17:11:53.366] [DEBUG] [KarmaTestExplorer]: Test hard refresh started
[2023-11-17 17:11:53.367] [DEBUG] [TestLocator]: Refresh requested for all spec file(s): ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 17:11:53.367] [DEBUG] [TestLocator]: No refresh currently in progress - will commence new refresh for files: ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 17:11:53.367] [DEBUG] [TestLocator]: Refreshing all spec file(s): ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 17:11:53.369] [DEBUG] [KarmaTestExplorer]: Refresh request - Test manager is not started - Starting it
[2023-11-17 17:11:53.370] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9976 acquired: 9976
[2023-11-17 17:11:53.371] [INFO] [DefaultTestManager]: Using requested --> available karma port: 9976 --> 9976
[2023-11-17 17:11:53.371] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9999 acquired: 9999
[2023-11-17 17:11:53.371] [INFO] [DefaultTestManager]: Using requested --> available karma listener socket port: 9999 --> 9999
[2023-11-17 17:11:53.372] [DEBUG] [PortAcquisitionClient]: Request for 1 port(s) at base port 9222 acquired: 9222
[2023-11-17 17:11:53.372] [INFO] [DefaultTestManager]: Using requested --> available debug port: 9222 --> 9222
[2023-11-17 17:11:53.372] [DEBUG] [KarmaTestListener]: Attempting to listen on port 9999
[2023-11-17 17:11:53.373] [INFO] [KarmaTestServer]: Starting karma server
[2023-11-17 17:11:53.373] [DEBUG] [AngularTestServerExecutor]: Executing server start with karma port '9976' and karma socket port '9999'
[2023-11-17 17:11:53.376] [DEBUG] [AngularTestServerExecutor]: Found '@angular/cli' module at: /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/@angular/cli
[2023-11-17 17:11:53.377] [DEBUG] [AngularTestServerExecutor::SimpleProcess]: Process 99vu2t02dn7:
Executing command: '/Users/kevindiem/.nvm/versions/node/v14.15.0/bin/node'
with args: ["/Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/@angular/cli/bin/ng","test","angular-tour-of-heroes","--karma-config=/Users/kevindiem/.vscode/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs","--progress=false","--no-watch"]
[2023-11-17 17:11:53.379] [DEBUG] [AngularTestServerExecutor::SimpleProcess]: Process 99vu2t02dn7 - process spawned successfully with PID 9518 for command: /Users/kevindiem/.nvm/versions/node/v14.15.0/bin/node /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/@angular/cli/bin/ng test angular-tour-of-heroes --karma-config=/Users/kevindiem/.vscode/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs --progress=false --no-watch
[2023-11-17 17:11:53.380] [INFO] [KarmaTestListener]: Waiting for Karma to connect on port 9999
[2023-11-17 17:11:53.524] [DEBUG] [SimpleFileHandler]: Resolved 2 file(s) from file patterns: ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 17:11:53.524] [DEBUG] [TestLocator]: Requested --> filtered file count to refresh: 2 --> 2
[2023-11-17 17:11:53.524] [DEBUG] [SimpleFileHandler]: Reading file async: /Users/kevindiem/workspace/angular-tour-of-heroes/e2e/src/app.e2e-spec.ts
[2023-11-17 17:11:53.526] [DEBUG] [AstTestFileParser]: Parse operation u1kvf4awo2: Parsed 1 total tests from file '/Users/kevindiem/workspace/angular-tour-of-heroes/e2e/src/app.e2e-spec.ts' in 0.00 secs
[2023-11-17 17:11:53.526] [DEBUG] [SimpleFileHandler]: Reading file async: /Users/kevindiem/workspace/angular-tour-of-heroes/src/app/app.component.spec.ts
[2023-11-17 17:11:53.527] [DEBUG] [AstTestFileParser]: Parse operation trsvqmzqc5: Parsed 3 total tests from file '/Users/kevindiem/workspace/angular-tour-of-heroes/src/app/app.component.spec.ts' in 0.00 secs
[2023-11-17 17:11:53.527] [DEBUG] [TestLocator]: Refreshed 2 spec files from glob list in 0.16 secs: ["**/*{.,-,_}{test,spec}.{ts,js}","**/{test,spec}{.,-,_}*.{ts,js}"]
[2023-11-17 17:11:57.173] [INFO] [KarmaTestListener]: Established new connection with Karma on port 9999
[2023-11-17 17:11:57.173] [DEBUG] [KarmaTestListener]: Listening for Karma events
[2023-11-17 17:11:59.320] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: file_list_modified
[2023-11-17 17:11:59.503] [DEBUG] [KarmaTestRunProcessor]: Karma server on karma port 9976 is ready for requests
[2023-11-17 17:12:02.549] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: file_list_modified
[2023-11-17 17:12:02.748] [DEBUG] [NotificationHandler]: User clicked status: Starting Karma (Click to show log)
[2023-11-17 17:12:04.808] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: browsers_change
[2023-11-17 17:12:04.808] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: browser_register
[2023-11-17 17:12:04.808] [DEBUG] [KarmaTestRunProcessor]: Browsers connected and ready for test execution
[2023-11-17 17:12:04.809] [DEBUG] [KarmaTestRunProcessor]: Test run started for browsers: HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)
[2023-11-17 17:12:04.809] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Beginning ambient test event processing
[2023-11-17 17:12:04.809] [DEBUG] [KarmaAutoWatchTestEventProcessor::KarmaTestEventProcessor]: Request to begin test event processing
[2023-11-17 17:12:04.809] [DEBUG] [KarmaAutoWatchTestEventProcessor::KarmaTestEventProcessor]: Proceeding to begin processing test events
[2023-11-17 17:12:04.810] [INFO] [DefaultTestManager]: Discovering tests
[2023-11-17 17:12:04.810] [DEBUG] [KarmaTestRunProcessor]: Processing test discovery for test run with id: 8fnzxcpg1ld
[2023-11-17 17:12:04.810] [DEBUG] [KarmaTestRunProcessor]: Started test event handling for test run Id: 8fnzxcpg1ld
[2023-11-17 17:12:04.810] [DEBUG] [KarmaTestRunner]: Executing test discovery run id: 8fnzxcpg1ld
[2023-11-17 17:12:04.811] [DEBUG] [KarmaHttpTestRunExecutor]: Sending karma run http request with data: {"args":["--grep=/$^/","--testRunId=8fnzxcpg1ld"],"refresh":true}
[2023-11-17 17:12:04.825] [DEBUG] [KarmaHttpTestRunExecutor]: Finished sending http test run request
[2023-11-17 17:12:04.839] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: file_list_modified
[2023-11-17 17:12:04.839] [DEBUG] [KarmaTestRunProcessor]: Test run started for browsers: HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)
[2023-11-17 17:12:04.839] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Aborting current ambient event processing - New test is starting
[2023-11-17 17:12:04.839] [DEBUG] [KarmaAutoWatchTestEventProcessor::KarmaTestEventProcessor]: Request to process test error event with message: New test is starting
[2023-11-17 17:12:04.839] [DEBUG] [KarmaAutoWatchTestEventProcessor::KarmaTestEventProcessor]: Request to conclude test event processing
[2023-11-17 17:12:04.839] [DEBUG] [KarmaTestRunProcessor]: Test run starting for requested test run Id: 8fnzxcpg1ld
[2023-11-17 17:12:04.839] [DEBUG] [KarmaTestRunProcessor]: Starting test capture session for current requested test run Id: 8fnzxcpg1ld
[2023-11-17 17:12:04.839] [DEBUG] [KarmaTestEventProcessor]: Request to begin test event processing
[2023-11-17 17:12:04.839] [DEBUG] [KarmaTestEventProcessor]: Proceeding to begin processing test events
[2023-11-17 17:12:04.840] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Aborting current ambient event processing - New test is starting
[2023-11-17 17:12:04.840] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Concluding ambient test event processing
[2023-11-17 17:12:04.840] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Retiring 0 skipped ambient test ids
[2023-11-17 17:12:04.840] [DEBUG] [KarmaAutoWatchTestEventProcessor]: Done concluding ambient test event processing
[2023-11-17 17:12:10.829] [DEBUG] [KarmaTestRunProcessor]: Test run started in browser: HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)
[2023-11-17 17:12:10.908] [DEBUG] [KarmaTestRunProcessor]: Processing received spec id 'spec2' with test processor: KarmaTestEventProcessor
[2023-11-17 17:12:10.908] [DEBUG] [KarmaTestEventProcessor]: Request to process test result event having status: Skipped
[2023-11-17 17:12:10.908] [DEBUG] [KarmaTestEventProcessor]: Resetting elapsed test event interval time to timeout value: 60000
[2023-11-17 17:12:10.908] [DEBUG] [KarmaTestEventProcessor]: Skipping test result event for test id spec2 - Emit events not enabled for test status Skipped
[2023-11-17 17:12:10.908] [DEBUG] [KarmaTestRunProcessor]: [SKIPPED] Test Skipped - HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)
[2023-11-17 17:12:11.165] [DEBUG] [KarmaTestRunProcessor]: Processing received spec id 'spec1' with test processor: KarmaTestEventProcessor
[2023-11-17 17:12:11.165] [DEBUG] [KarmaTestEventProcessor]: Request to process test result event having status: Skipped
[2023-11-17 17:12:11.165] [DEBUG] [KarmaTestEventProcessor]: Resetting elapsed test event interval time to timeout value: 60000
[2023-11-17 17:12:11.166] [DEBUG] [KarmaTestEventProcessor]: Skipping test result event for test id spec1 - Emit events not enabled for test status Skipped
[2023-11-17 17:12:11.166] [DEBUG] [KarmaTestRunProcessor]: [SKIPPED] Test Skipped - HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)
[2023-11-17 17:12:11.207] [DEBUG] [KarmaTestRunProcessor]: Processing received spec id 'spec0' with test processor: KarmaTestEventProcessor
[2023-11-17 17:12:11.207] [DEBUG] [KarmaTestEventProcessor]: Request to process test result event having status: Skipped
[2023-11-17 17:12:11.207] [DEBUG] [KarmaTestEventProcessor]: Resetting elapsed test event interval time to timeout value: 60000
[2023-11-17 17:12:11.207] [DEBUG] [KarmaTestEventProcessor]: Skipping test result event for test id spec0 - Emit events not enabled for test status Skipped
[2023-11-17 17:12:11.207] [DEBUG] [KarmaTestRunProcessor]: [SKIPPED] Test Skipped - HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)
[2023-11-17 17:12:11.328] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: browsers_change
[2023-11-17 17:12:11.328] [DEBUG] [KarmaTestRunProcessor]: Test run completed in browser: HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)
[2023-11-17 17:12:11.328] [DEBUG] [KarmaTestRunProcessor]: Ignoring received karma event: browser_complete_with_no_more_retries
[2023-11-17 17:12:11.329] [DEBUG] [KarmaTestRunProcessor]: Test run completed with status 'Error' for browsers: HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)
[2023-11-17 17:12:11.329] [WARN] [KarmaTestRunProcessor]: Test run encountered an error (Exit code: 0) - <no message>
[2023-11-17 17:12:11.329] [DEBUG] [KarmaTestRunProcessor]: Test error processing requested with message: Test run encountered an error
[2023-11-17 17:12:11.329] [DEBUG] [KarmaTestRunProcessor]: Sending test error event to test event processor with message: Test run encountered an error
[2023-11-17 17:12:11.329] [DEBUG] [KarmaTestEventProcessor]: Request to process test error event with message: Test run encountered an error
[2023-11-17 17:12:11.330] [DEBUG] [KarmaTestEventProcessor]: Request to conclude test event processing
[2023-11-17 17:12:11.330] [ERROR] [KarmaTestRunProcessor]: Could not capture Karma events - Test execution failed: Test run encountered an error
[2023-11-17 17:12:11.331] [DEBUG] [KarmaTestRunProcessor]: Done with test event handling for test run Id: 8fnzxcpg1ld
[2023-11-17 17:12:11.331] [ERROR] [DefaultTestManager]: Test discovery failed: Test run encountered an error
[2023-11-17 17:12:11.331] [ERROR] [KarmaTestExplorer]: Failed to load tests - Test discovery failed: Test run encountered an error
[2023-11-17 17:12:11.331] [DEBUG] [NotificationHandler]: Showing 'Error' notification with actions 'Retry Test Load' and message: Failed to load tests - Test discovery failed: Test run encountered an error
[2023-11-17 17:12:11.331] [DEBUG] [KarmaTestExplorer]: Updating loaded test store
[2023-11-17 17:12:11.331] [DEBUG] [KarmaTestExplorer]: Clearing loaded root suite
[2023-11-17 17:12:11.331] [DEBUG] [TestStore]: Clearing stored tests
[2023-11-17 17:12:11.332] [INFO] [KarmaTestExplorer]: Finished loading tests in 17.97 secs (Failed)
[2023-11-17 17:12:11.332] [DEBUG] [KarmaHttpTestRunExecutor]: Karma http request closed

Please also capture and attach the logs from all the Karma Server Output channels when the issue occurs.
Attached Angular 8 debug logs

------------------------------------
Karma Test Explorer: Launching Karma
------------------------------------

[2023-11-17 17:11:55.708] [DEBUG] [KarmaConfigLoader]: Loading Karma config: /Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js

[2023-11-17 17:11:55.901] [DEBUG] [KarmaConfigLoader]: Using custom launcher: {
  "base": "Chrome",
  "flags": [
    "--headless",
    "--disable-gpu",
    "--disable-dev-shm-usage",
    "--remote-debugging-port=9222"
  ]
}

17 11 2023 12:11:55.902:DEBUG [config]: Loading config /Users/kevindiem/.vscode/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs

17 11 2023 12:11:55.906:DEBUG [karma-server]: Final config [{"LOG_DISABLE":"1","LOG_ERROR":"2","LOG_WARN":"3","LOG_INFO":"4","LOG_DEBUG":"5","frameworks":"6","protocol":"7","port":9976,"listenAddress":"8","hostname":"9","httpsServerConfig":"10","basePath":"11","files":"12","browserConsoleLogOptions":"13","customContextFile":null,"customDebugFile":null,"customClientContextFile":null,"exclude":"14","logLevel":"5","colors":true,"autoWatch":true,"autoWatchBatchDelay":250,"restartOnFileChange":false,"usePolling":false,"reporters":"15","singleRun":false,"browsers":"16","captureTimeout":90000,"proxies":"17","proxyValidateSSL":true,"preprocessors":"18","urlRoot":"19","reportSlowerThan":0,"loggers":"20","transports":"21","forceJSONP":false,"plugins":"22","client":"23","defaultClient":"23","browserDisconnectTimeout":30000,"browserDisconnectTolerance":0,"browserNoActivityTimeout":86400000,"processKillTimeout":2000,"concurrency":null,"failOnEmptyTestSuite":true,"retryLimit":3,"detached":false,"crossOriginAttribute":true,"browserSocketTimeout":30000,"configFile":"24","coverageIstanbulReporter":"25","customLaunchers":"26","pingTimeout":86400000},"OFF","ERROR","WARN","INFO","DEBUG",["27","28"],"http:","<IP_ADDRESS>","localhost",{},"/Users/kevindiem/workspace/angular-tour-of-heroes",[],{"level":"29","format":"30","terminal":true},["31","24"],["32"],["33"],{},{},"/",["34"],["35","36"],["37","38","39","40","41","42","43"],{"args":"44","useIframe":true,"runInParent":false,"captureConsole":true,"clearContext":false},"/Users/kevindiem/.vscode/extensions/lucono.karma-test-explorer-0.8.2/dist/karma.conf.cjs",{"dir":"45","reports":"46","fixWebpackSourcePaths":true},{"KarmaTestExplorer_CustomLauncher":"47"},"jasmine","@angular-devkit/build-angular","debug","%b %T: %m","/Users/kevindiem/workspace/angular-tour-of-heroes/karma.conf.js","KarmaTestExplorerReporter","KarmaTestExplorer_CustomLauncher",{"type":"48","layout":"49"},"polling","websocket",{"framework:jasmine":"50"},{"launcher:Chrome":"51","launcher:ChromeHeadless":"52","launcher:ChromeCanary":"53","launcher:ChromeCanaryHeadless":"54","launcher:Chromium":"55","launcher:ChromiumHeadless":"56","launcher:Dartium":"57","test":"58"},{"reporter:kjhtml":"59"},{"reporter:coverage-istanbul":"60"},{"framework:@angular-devkit/build-angular":"61","reporter:@angular-devkit/build-angular--sourcemap-reporter":"62","reporter:@angular-devkit/build-angular--event-reporter":"63","middleware:@angular-devkit/build-angular--blocker":"64","middleware:@angular-devkit/build-angular--fallback":"65"},{"reporter:KarmaTestExplorerReporter":"66"},{"launcher:KarmaTestExplorer_CustomLauncher":"67"},[],"/Users/kevindiem/workspace/angular-tour-of-heroes/coverage/angular-tour-of-heroes",["68","69","70"],{"base":"71","flags":"72"},"console",{"type":"73","pattern":"74"},["75",null],["76",null],["76",null],["76",null],["76",null],["76",null],["76",null],["76",null],{},["76",null],["76",null],["75",null],["76",null],["76",null],["75",null],["75",null],["76",null],["75",null],"html","lcovonly","text-summary","Chrome",["77","78","79","80"],"pattern","%[%d{DATE}:%p [%c]: %]%m","factory","type","--headless","--disable-gpu","--disable-dev-shm-usage","--remote-debugging-port=9222"]

17 11 2023 12:11:55.906:DEBUG [plugin]: Loading inlined plugin (defining framework:jasmine).

17 11 2023 12:11:55.906:DEBUG [plugin]: Loading inlined plugin (defining launcher:Chrome, launcher:ChromeHeadless, launcher:ChromeCanary, launcher:ChromeCanaryHeadless, launcher:Chromium, launcher:ChromiumHeadless, launcher:Dartium, test).

17 11 2023 12:11:55.906:DEBUG [plugin]: Loading inlined plugin (defining reporter:kjhtml).

17 11 2023 12:11:55.906:DEBUG [plugin]: Loading inlined plugin (defining reporter:coverage-istanbul).

17 11 2023 12:11:55.906:DEBUG [plugin]: Loading inlined plugin (defining framework:@angular-devkit/build-angular, reporter:@angular-devkit/build-angular--sourcemap-reporter, reporter:@angular-devkit/build-angular--event-reporter, middleware:@angular-devkit/build-angular--blocker, middleware:@angular-devkit/build-angular--fallback).

17 11 2023 12:11:55.906:DEBUG [plugin]: Loading inlined plugin (defining reporter:KarmaTestExplorerReporter).

17 11 2023 12:11:55.906:DEBUG [plugin]: Loading inlined plugin (defining launcher:KarmaTestExplorer_CustomLauncher).

17 11 2023 12:11:57.051:DEBUG [web-server]: Instantiating middleware

17 11 2023 12:11:57.051:DEBUG [reporter]: Trying to load reporter: KarmaTestExplorerReporter

17 11 2023 12:11:57.055:DEBUG [reporter]: Trying to load color-version of reporter: KarmaTestExplorerReporter (KarmaTestExplorerReporter_color)

17 11 2023 12:11:57.055:DEBUG [reporter]: Couldn't load color-version.

17 11 2023 12:11:57.055:DEBUG [reporter]: Trying to load reporter: @angular-devkit/build-angular--sourcemap-reporter

17 11 2023 12:11:57.055:DEBUG [reporter]: Trying to load color-version of reporter: @angular-devkit/build-angular--sourcemap-reporter (@angular-devkit/build-angular--sourcemap-reporter_color)

17 11 2023 12:11:57.055:DEBUG [reporter]: Couldn't load color-version.

17 11 2023 12:11:57.055:DEBUG [reporter]: Trying to load reporter: @angular-devkit/build-angular--event-reporter

17 11 2023 12:11:57.055:DEBUG [reporter]: Trying to load color-version of reporter: @angular-devkit/build-angular--event-reporter (@angular-devkit/build-angular--event-reporter_color)

17 11 2023 12:11:57.055:DEBUG [reporter]: Couldn't load color-version.

17 11 2023 12:11:59.319:DEBUG [karma-server]: List of files has changed, trying to execute

17 11 2023 12:11:59.319:WARN [karma]: No captured browser, open http://localhost:9976/

17 11 2023 12:11:59.502:INFO [karma-server]: Karma v4.1.0 server started at http://<IP_ADDRESS>:9976/

17 11 2023 12:11:59.502:INFO [launcher]: Launching browsers KarmaTestExplorer_CustomLauncher with concurrency unlimited

17 11 2023 12:11:59.515:INFO [launcher]: Starting browser Chrome

17 11 2023 12:11:59.515:DEBUG [launcher]: null -> BEING_CAPTURED

17 11 2023 12:11:59.515:DEBUG [temp-dir]: Creating temp dir at /var/folders/m2/w1sr4mkx1x31mw17kr_79dx00000gn/T/karma-77963442

17 11 2023 12:11:59.516:DEBUG [launcher]: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --user-data-dir=/var/folders/m2/w1sr4mkx1x31mw17kr_79dx00000gn/T/karma-77963442 --no-default-browser-check --no-first-run --disable-default-apps --disable-popup-blocking --disable-translate --disable-background-timer-throttling --disable-renderer-backgrounding --disable-device-discovery-notifications --headless --disable-gpu --disable-dev-shm-usage --remote-debugging-port=9222 http://localhost:9976/?id=77963442

17 11 2023 12:12:02.548:DEBUG [karma-server]: List of files has changed, trying to execute
17 11 2023 12:12:02.549:WARN [karma]: No captured browser, open http://localhost:9976/

17 11 2023 12:12:04.161:DEBUG [web-server]: serving: /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/karma/static/client.html

17 11 2023 12:12:04.295:DEBUG [web-server]: serving: /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/karma/static/karma.js

17 11 2023 12:12:04.759:DEBUG [karma-server]: A browser has connected on socket C-LjfUGVSsvNlQtYAAAA

17 11 2023 12:12:04.807:DEBUG [HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)]: undefined -> CONNECTED

17 11 2023 12:12:04.807:INFO [HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)]: Connected on socket C-LjfUGVSsvNlQtYAAAA with id 77963442

17 11 2023 12:12:04.808:DEBUG [launcher]: BEING_CAPTURED -> CAPTURED
17 11 2023 12:12:04.808:DEBUG [launcher]: Chrome (id 77963442) captured in 5.305 secs

17 11 2023 12:12:04.808:DEBUG [karma]: All browsers are ready, executing
17 11 2023 12:12:04.808:DEBUG [karma]: Captured 1 browsers

17 11 2023 12:12:04.809:DEBUG [web-server]: upgrade /socket.io/?EIO=3&transport=websocket&sid=C-LjfUGVSsvNlQtYAAAA

17 11 2023 12:12:04.826:DEBUG [karma]: Execution (fired by runner)

17 11 2023 12:12:04.834:DEBUG [karma]: Merging client.args with  [ '--grep=/$^/', '--testRunId=8fnzxcpg1ld' ]

17 11 2023 12:12:04.834:DEBUG [karma]: Refreshing all the files / patterns

17 11 2023 12:12:04.838:DEBUG [karma-server]: List of files has changed, trying to execute

17 11 2023 12:12:04.838:DEBUG [karma]: All browsers are ready, executing
17 11 2023 12:12:04.838:DEBUG [karma]: Captured 1 browsers

17 11 2023 12:12:04.882:DEBUG [middleware:karma]: custom files<EMAIL_ADDRESS><EMAIL_ADDRESS>null

17 11 2023 12:12:04.882:DEBUG [middleware:karma]: Serving customContextFile<EMAIL_ADDRESS>
17 11 2023 12:12:04.883:DEBUG [web-server]: serving<EMAIL_ADDRESS>
17 11 2023 12:12:04.950:DEBUG [middleware:karma]: custom files<EMAIL_ADDRESS><EMAIL_ADDRESS>null

17 11 2023 12:12:04.950:DEBUG [middleware:karma]: Serving customContextFile<EMAIL_ADDRESS>17 11 2023 12:12:04.950:DEBUG [web-server]: serving (cached<EMAIL_ADDRESS>
17 11 2023 12:12:04.956:DEBUG [web-server]: serving: /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/karma/static/context.js

17 11 2023 12:12:04.958:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/runtime.js

17 11 2023 12:12:04.958:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/runtime.js

17 11 2023 12:12:04.995:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/polyfills.js
17 11 2023 12:12:04.995:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/polyfills.js

17 11 2023 12:12:04.997:DEBUG [middleware:source-files]: Requesting /base/node_modules/source-map-support/browser-source-map-support.js?0a776857d457dcbb7a4bc82b263431477788990d

17 11 2023 12:12:04.997:DEBUG [middleware:source-files]: Fetching /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/source-map-support/browser-source-map-support.js

17 11 2023 12:12:04.997:DEBUG [middleware:source-files]: Requesting /base/node_modules/karma-source-map-support/lib/client.js?fcb459e84379f1ce8e91fe200d87463f3780ca1b

17 11 2023 12:12:04.997:DEBUG [middleware:source-files]: Fetching /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/karma-source-map-support/lib/client.js

17 11 2023 12:12:04.997:DEBUG [middleware:source-files]: Requesting /base/node_modules/jasmine-core/lib/jasmine-core/jasmine.js?be3ff9a5e2d6d748de5b900ac3c6d9603e2942a7

17 11 2023 12:12:04.997:DEBUG [middleware:source-files]: Fetching /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/jasmine-core/lib/jasmine-core/jasmine.js

17 11 2023 12:12:04.997:DEBUG [web-server]: serving (cached): /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/source-map-support/browser-source-map-support.js

17 11 2023 12:12:04.998:DEBUG [web-server]: serving (cached): /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/karma-source-map-support/lib/client.js

17 11 2023 12:12:04.998:DEBUG [web-server]: serving (cached): /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/jasmine-core/lib/jasmine-core/jasmine.js

17 11 2023 12:12:04.999:DEBUG [middleware:source-files]: Requesting /base/node_modules/karma-jasmine/lib/boot.js?945a38bf4e45ad2770eb94868231905a04a0bd3e

17 11 2023 12:12:04.999:DEBUG [middleware:source-files]: Fetching /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/karma-jasmine/lib/boot.js

17 11 2023 12:12:04.999:DEBUG [middleware:source-files]: Requesting /base/node_modules/karma-jasmine/lib/adapter.js?3098011cfe00faa2a869a8cffce13f3befc1a035

17 11 2023 12:12:04.999:DEBUG [middleware:source-files]: Fetching /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/karma-jasmine/lib/adapter.js

17 11 2023 12:12:04.999:DEBUG [web-server]: serving (cached): /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/karma-jasmine/lib/boot.js

17 11 2023 12:12:04.999:DEBUG [web-server]: serving (cached): /Users/kevindiem/workspace/angular-tour-of-heroes/node_modules/karma-jasmine/lib/adapter.js

17 11 2023 12:12:05.000:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/styles.js

17 11 2023 12:12:05.000:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/styles.js

17 11 2023 12:12:05.000:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/scripts.js

17 11 2023 12:12:05.000:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/scripts.js

17 11 2023 12:12:05.000:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/vendor.js
17 11 2023 12:12:05.000:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/vendor.js

17 11 2023 12:12:05.003:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/main.js

17 11 2023 12:12:05.003:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/main.js

17 11 2023 12:12:05.612:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/vendor.js
17 11 2023 12:12:05.612:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/vendor.js

17 11 2023 12:12:05.658:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/vendor.js
17 11 2023 12:12:05.658:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/vendor.js

17 11 2023 12:12:09.981:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/main.js
17 11 2023 12:12:09.981:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/main.js

17 11 2023 12:12:09.990:DEBUG [middleware:source-files]: Requesting /_karma_webpack_/main.js

17 11 2023 12:12:09.990:DEBUG [middleware:source-files]: Fetching /_karma_webpack_/main.js

17 11 2023 12:12:10.828:DEBUG [HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)]: CONNECTED -> EXECUTING

17 11 2023 12:12:11.327:DEBUG [HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)]: EXECUTING -> CONNECTED

Angular 8 app

In a public github repo, create a minimal project that reproduces the issue
Provide a link to the project

Screenshots

If applicable, add screenshots to help explain the issue you are having.

Please Provide the Following Information

OS and Version: macOS Sonoma 14.0
Environment: N/A
Node Version: 14.5.0
VS Code Version: 1.84.2 (Universal)
Karma Version: 4.1.0
Browser and Version: HeadlessChrome 119.0.6045 (Mac OS X 10.15.7)
Frameworks: Angular, Jasmine
Angular Version: 8.2.14

Additional Context
This worked on repos I use for work at some point; I can't remember the particular commit or repo where I was using it. Suddenly it won't work on Windows or macOS.
Running ng test works, as does taking the command and arguments run from the debug output except for the .cjs karma conf provided by karma-test-explorer.

@kgdiem Note that with the deprecation of Karma runner, this extension is also now deprecated. While you continue to use Karma and this extension, I encourage you to post any new issues in the Discussions area to possibly get help from other users.
For this specific issue, perhaps try upgrading your Karma version to v6 or later. If that doesn't help, try posting in the Discussions area to possibly get help from other users.


Split static lib between core platform agnostic and platform specific

This PR introduces two new imgui static libs to replace the existing imgui.lib.
imgui_core contains platform agnostic code, needed for linking to rtc.dll for an embedded uses case. Using this instead of the existing imgui.lib  fixes a number of issues (UWP certification failures, mobile dependencies).
imgui_ex contains platform specific-functionality for windowing and interaction and is needed only by internal test apps.
Plan is to build and deploy these in addition to imgui.lib and then remove imgui.lib after all rtc code has been switched over.

@garythomson can you also update https://github.com/Esri/imgui/blob/runtimecore/imgui.lua to just call these two lua files so things just work and no changes are needed to the architecture repo?

@chri7325 - updated


fix(Icon): Resolves build-time TypeError: Cannot read property "name" of undefined

Howdy! I upgraded to v6.0.2 and noticed a build-time error (my build logs: https://zeit.co/4cm4k1/personal-website/m6doong9t), so I went ahead and fixed it. Let me know if more is needed for this PR. Thanks! 😄

Ah, thanks! Didn't trigger in my test cases. Fix one problem, cause another... Will get a patch out right now.

Patch released, v6.0.3


Agreements Overview

route to test this feature:
/bases/<baseId>/transfers/agreements
use the following logins to try different access levels:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
done:

show data of transfer Agreements correctly
add create Agreement button
add sorting of columns
add forwarding to shipment page
status modals
tests
when new agreement is created data is directly written to the table
filter

additional nice to haves:

optimistic updates
forward to CreateAgreement with fields being filled

I moved my last commits from shipments-overview here.
Everything is in place now @pylipp


Scraper only returns 1050 results

Hi Toby, great scraper you got here, but it seems to be only returning 1050 results, I may just be using it wrong though..
I have loaded the script in PyCharm with the correct version of Python and have downloaded the dependencies.
I have entered this into the Python console:
from rightmove_webscraper import RightmoveData
url = "https://www.rightmove.co.uk/property-for-sale/find.html?locationIdentifier=REGION^87490&propertyTypes=&includeSSTC=false&mustHave=&dontShow=&furnishTypes=&keywords="
rm = RightmoveData(url)
rm.results_count

Even if I change the URL, the results still appear to be of 1050. Maybe my approach is wrong?

Hi Nick, glad you are enjoying using the scraper!
Unfortunately this is expected behaviour determined by the rightmove website, so is beyond our control. If you scroll to the bottom of the page of the url you used you'll see there are a total of 42 pages of results - each contains 25 listings, for a total of 1050. So even though the first results page states that there are 40,193 results, it is really only possible to see the first 1050.
The workaround to this limitation is to narrow the scope of the search, by searching for a smaller geographical area or by searching for listings published in a shorter period of time, and then to combine the results from multiple different searches.
I'll add something to the documentation to explain this limitation as this issue has been raised once or twice before. It also may be simple to modify the API so that you can pass multiple URLs to a single instance and scrape them all at once so I'll look into doing that too.

Is there a workaround on this, other than narrowing down the search area or time?

As far as I know there isn't.


Performance Question

I absolutely love this library, and I'm trying to incorporate it into my software. I have reasonably large SVG files (~300KB) and have noticed that 're-render' times are in the 150ms range. I have to 're-render' the SVG multiple times a second as part of some animation elements.
Is there a way to have a re-render only render a smaller invalid region? I.e., can I tell it which components where modified (color, text, etc) and only draw the modifications and anything else in a region?
When I run performance analysis, it shows that Svg.SvgRenderer.FillPath is the worst offender of time, but since that is a direct GDI call... Are there any tricks to speeding it up? Do different render targets (graphics, canvas, bmp) have difference performance?

I've come up with one solution so far, but figured I'd report back findings for other folks.
The rendering type plays a significant roll on rendering speeds. For example, it anti-aliasing is off for the SvgDocument render times are notably faster.
Because of the huge reduction in image quality, this wasn't a viable solution for my needs. Instead what I've come up with so far seems to work since I can't figure out how to get clipping regions to work.
After I load the SVG, I make new SVG with the same initial SvgDocument properties (basically a deep copy followed by deleting all children). As I walk the first document tree I'm looking for elements I know are going to be modified. For each one that I find, I remove it from the first SVG and put it into the 2nd SVG. When I'm doing this, I also apply any parent transforms to the new child since it doesn't need/have all of it's parents.
Once I'm done, I render the first SVG to an Image. When any of the 'animating' elements are changed, the 2nd SVG is rendered on top of a copy of the first SVG's rendering to form a complete composite. This prevents all the non-moving elements for having to re-render, unless of course the target graphics width/height changes. This is giving huge performance gains.
There is still one problem I'm working on, and that is of occlusion. It's possible based on the drawing order, that the moving components should be underneath non-moving components. So my next step is to detect any static elements that would be physically in the same bounds as a modifying element, and move those to a 3rd layer that is also an static SVG image.


Add prefix scan sum

Add support for dynamic input shapes to the operation prefix_scan_op and its child, prefix_scan_sum.  This is a prerequisite for parsing the Multinomial op. from Onnx.

See PR #1921


Appearance customization

Changing the navigationcontroller properties is quite easy and well documented.For the other views (collection, album selection) we have to use the UIAppearance protocol and the official documentation is referenced. The process for changing the appearance for these views is complex due to their containment, making the process tedious and very much trial and error.
Would it be possible to give more concrete examples for customizing the appearance of the cells and other views used in this picker? Besides UIAppearance customization, more control or access to the appearance properties of the used cells and views would also be helpful if at all possible.

@Remyoman There's would be a more detailed sample for customising in the coming major release. Stay tuned.

Added in the v3.0.0-beta.1


BUG: Change of Url in Frontend/src/app.jsx

Is there an existing issue for this?

[x] I have searched the existing issues

What happened?
Should be this

In the place of

Please assign me this issue I wanna change it. under GSSOC'24
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Sibam-Paul the master branch is used for development on vercel and it needs some back end to fetch from so vercel url is used.


Log Archiving and Rotation

Feature Request
Is your feature request related to a problem? Please describe:
The log behavior is different from TiDB and PD, lack of archiving function.
Describe the feature you'd like:
Log parameters and behavior are consistent with TiDB and PD.

/type feature-request

I have a dream that one day TiDB, TiKV and TiFlash can use the same programing language.


Fix #115: dependencies can be represented as a dir

Here is a fix for #115.
In newer gradle versions subproject dependencies are directories.  So we should not calculate checksums from them.

Thanks for this pull request and sorry for the delayed response @steven-aerts.
We'd like to merge this pull request.
Can you please join our contributors community by signing JFrog's CLA so that we can merge your code?


Assembly on NuGet in Debug release?

I'm testing something with Benchmark.NET and when I attempt to benchmark some code referencing this library, I get the message that Microsoft.IO.RecyclableMemory is non-optimized.  Is it possible that the public NuGet package is accidentally including the debug config?

Hmm...that would be a bad mistake. Let me take a look at the binaries and our build and see if something needs fixed here.

For what it's worth, the below code uses the exact extension methods that Benchmark.NET is using to test this.  I built the source myself from this repo in both Debug and Release configuration.  Referencing the different assemblies with the below code returned false for the Release config and true for the Debug config, so I'm fairly confident the public NuGet does have the Debug release by accident.
By the way I loved your book :-)

    class Program
    {
        static void Main(string[] args)
        {
            var assembly = Assembly.Load("Microsoft.IO.RecyclableMemoryStream");
            Console.WriteLine($"Are Jit optimizations DISABLED on this assembly? {assembly.IsJitOptimizationDisabled()}");
        }
    }

    internal static class AssemblyExtensions
    {
        internal static bool? IsJitOptimizationDisabled(this Assembly assembly)
            => GetDebuggableAttribute(assembly).IsJitOptimizerDisabled();

        internal static bool? IsDebug(this Assembly assembly)
            => GetDebuggableAttribute(assembly).IsJitTrackingEnabled();

        internal static bool IsTrue(this bool? valueOrNothing) => valueOrNothing.HasValue && valueOrNothing.Value;

        private static DebuggableAttribute GetDebuggableAttribute(Assembly assembly)
            => assembly?.GetCustomAttributes()
                .OfType<DebuggableAttribute>()
                .SingleOrDefault();

        private static bool? IsJitOptimizerDisabled(this DebuggableAttribute attribute) => attribute?.IsJITOptimizerDisabled;

        private static bool? IsJitTrackingEnabled(this DebuggableAttribute attribute) => attribute?.IsJITTrackingEnabled;
    }

Found the problem. The build pipeline was missing the --no-build parameter on the pack command, so it was rebuilding and then packing the default version, Debug. I've upload version 1.3.1 to nuget.org.
I'll also open a work item for myself to add a build step to verify Release mode of the final binaries.

1.3.2 should contain the fix

Amazing- thanks!!

Thanks @benmwatson - my benchmark went from 5.325 us to 4.217 us with less error!!


fig.height and fig.width parameters are not respected for remote blocks

If I set the fig.height and fig.width parameters for a remote code block in an rmd, the image instead is returned at the same default size as always.
fig-height-fig-width.zip

I've been investigating ways to adjust this but its quite complex due to the nature of the integration.
For context, the knitr engine routes code to be executed on the specified Databricks cluster, when it does this the code is executed via slightly different mechanisms for each language. For R, it controls the size of the viz via options that would need to be adjusted and changed back for every command execution. Not only does it require it to be changed, the option doesn't apply to the command where its changed.
Long story short, supporting this currently would duplicate the number of commands sent to the cluster and add significant overhead.
My intention when building this feature was predominantly a "hack" for interactive use outside Databricks notebooks and not for it to be the vehicle to render reports as most traditionally use rmarkdown for.
I intended to either:

Revisit this once the Databricks capability supports adjusting the image size options without requiring a second command
Consider removing the knitr engine in order to add other features that integrate better

I'm currently leaning towards (2) as it will remove confusion and provide a more opinionated approach.

Removing knitr engine from package in next version.


Add support for koa-unless

Hello @stiang and @citius.
As an alternative to #17 I created this PR using koa-unless.
This is what express-jwt does and I think it is more complete.
It allows you to conditionally run koa-jwt. You could skip it for certain URL, certain extensions or even provide a custom exception.
What do you think? :+1:

Hi @Foxandxss looks very well! I think this is true way for excluding some paths from handling jwt validation! And special thanks for koa-unless :relaxed:

I agree that this is the way to go, so I merged it and pushed a new release. Thanks a lot for your contribution!

@stiang Right, then I will see what others things needs to be done and PR away.


Push new version to ruby gems

To include language_iso and other changes, you may want to push a new version to ruby gems.

1.0.6 has now been released.


xy-output-component loading spinner does not show on zoom/pan

Screen Recording 2023-03-03 at 3.44.40 PM.webm

Picked by Traviz


package_checker creates file scaling.json in result directory

When running the package checker to check for a valid MLPerf training submission, the package_checker leaves a file
scaling.json in the results/.../maskrcnn directory. This file makes the submission directory invalid for submission it seems.
python3 -m mlperf_logging.package_checker Final/Lenovo training 2.1.0 --rcp_bert_train_samples

I think this is because of #271 .
You can certainly get rid of these files before creating submission with something like:
find <submission folder> -type f -name 'scaling.json' -delete .
We can also add a flag to the package checker to prevent creation of these scaling.json files (or disable by default and flag to enable), however the scaling.json files must be present to ensure the results summarizer produces accurate normalized scores.
@pgmpablo157321 @emizan76 what do you think, does it make sense to add such a flag to the package checker ?

@maanug-nv I think for now the default value of the flag should be to not create such files. That way it wont mess any submission by accident, we can call the package checker with the flag in the submission UI


Stuck on 'Activating privacy features...'

I'm using Caddy version 0.8.3 as a Proxy.
This worked well for a number of months, until I tried to restart Caddy today.
Now its just stuck on 'Activating privacy features...'
My caddyfile is the following and I start it using: ./caddy. The domains and their DNS are online and unchanged.
:80 {
}

my.domain.com:443 {
    proxy / other.domain.com {
        proxy_header Host {host}
        proxy_header X-Real-IP {remote}
        proxy_header X-Custom-SSL "true"
    }
}

Upgrading to Caddy 0.9.1 solved it, without any other change. It would be great to know what might have cased it though.

Would have been helpful to have some log output but I'm glad you fixed it by upgrading. :+1:

I'm running into the same issue right now, running caddy git master.


New Control: Attachments

Q
A

Bug fix?
[ ]

New feature?
[X]

New sample?
[ ]

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
It looks like there is an existing PR #177 for a List-Item-Attachments control from @joaojmendes, but I hadn't seen it before I build this for my own use. I figured I'd submit this anyway, since @joaojmendes' version seems to be on hold.

Codecov Report

Merging #212 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #212   +/-   ##
=======================================
  Coverage   72.71%   72.71%
=======================================
  Files          16       16
  Lines         744      744
  Branches      138      138
=======================================
  Hits          541      541
  Misses        159      159
  Partials       44       44

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 6985a86...3005afd. Read the comment docs.

@sympmarc @joaojmendes I was checking both of your list item attachment controls and I see that you both used @pnp/js. Would any of you be able to create it without that dependency? Calling the SharePoint APIs directly is significantly decreasing the bundle size.

Working on it...

Awesome @sympmarc!

Looks like @joaojmendes beat me to it. Let me know if you still want me to do anything; otherwise, I'll hold.

Hello,
Sorry for the later answer 😊. I did the changes, but only now I have opportunity to send the e-mail.
Thank you.
From: Marc D Anderson<EMAIL_ADDRESS>Reply to: SharePoint/sp-dev-fx-controls-react<EMAIL_ADDRESS>Date: Thursday, 7 February 2019 at 18:37
To: SharePoint/sp-dev-fx-controls-react<EMAIL_ADDRESS>Cc: joaojmendes<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-fx-controls-react] New Control: Attachments (#212)
Looks like @joaojmendeshttps://github.com/joaojmendes beat me to it. Let me know if you still want me to do anything; otherwise, I'll hold.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-fx-controls-react/pull/212#issuecomment-461546006, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AL-D1f0XI6Ty9i-df6EjZ7hpXszyrxxZks5vLHKAgaJpZM4Zll2F.

@sympmarc the control from @joaojmendes has now been merged. Feel free to test it out and enhance it if necessary.
I'll close this PR for now.


Example implementation of MobileSAM on Android / iOS?

So far I did not find any example implementations for actually running on the mobile device. Does someone have a link?

It has nothing to do with mobile


test_engine segmentation fault

Description
tests/python/unittest/test_engine.py
Occurrences
https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fedge/detail/PR-19624/2/pipeline#step-276-log-165

https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fedge/detail/PR-19624/4/pipeline/

You may skip the test to improve CI stability

The segmentation fault should be unrelated to test_engine. I'm updating the title.

I will look into this today. Seems to be affecting many prs

@josephevans helped launched a bunch of new worker machines and edge should be able to pass now. I restarted the edge pipeline on a few of the recent prs that were previously blocked

Thank you @Zha0q1 @josephevans


🕰 Use monotonic clock in Lock (and tests)

Pull Request check-list
Please make sure to review and check all of these items:

[ ] Does $ tox pass with this change (including linting)?
[x] Does travis tests pass with this change (enable it first in your forked repo and wait for the travis build to finish)?
[ ] Is the new or changed code fully tested?
[x] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
During a call to acquire(), if the call is blocking and has a
blocking_timeout set, it uses time.time() calls to determine when to
give up attempting to acquire the lock.
However, since time.time() is marked as "adjustable", it is possible
for it to go backwards or forwards at a rate other than 1 second per
second, meaning the spinloop may exit earlier or later than expected.
By changing the implementation to use time.monotonic(), which is
guaranteed to never go backwards, and not be affected by system clock
updates, this potential problem is fixed.
For the same reason, some time dependent lock tests have also been
changed to use time.monotonic().

In regards to

Is the new or changed code fully tested?

I have honestly no idea how to set up a scenario to test the difference between time.time and time.monotonic. Suggestions welcome.

Codecov Report

Merging #1402 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1402   +/-   ##
=======================================
  Coverage   85.90%   85.90%
=======================================
  Files           6        6
  Lines        2894     2894
=======================================
  Hits         2486     2486
  Misses        408      408

Impacted Files
Coverage Δ

redis/lock.py
100.00% <100.00%> (ø)

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 e4067e8...22900cb. Read the comment docs.

Thanks @coiax !


docs: Add change log

@Urigo I allowed myself to push all the missing tags to angular2-apollo and mark them as releases. I also defined list of changes in each one of them.


Fix the lint errors for travis-ci

Great, thank you @gartz
I will release the version now

You're welcome my friend! I thank you for your hard work here 👍


create an example Workflow (Github Action) for running sqlfmt in CI

Should include two examples:

Simple check workflow
Format-and-commit workflow

Also consider packaging this as an Action.

+1 for this!
Was trying to look at the possibility of doing something like the "Drizly" workflow described here of getting all the sqlfmt changes as annotations to be accepted / rejected in the PR workflow action.
Unfortunately my current team is divided between VS code users (who can use the pre-commit sqlfmt execute) and dbt Cloud IDE users.... who I dont believe have the ability to manage the environment to the enable the "run on save" or "run pre-commit" by default.
Thanks!

Came up with this as a basic workflow action to run the entire models directory on each run.
Working on a variation of this for changed files only.
`# GitHub Action that uses sqlfmt to reformat the sql in an incoming pull request.
If all sql in the pull request is compliant with sqlfmt then this Action does nothing.
Otherwise, sqlfmt is run and its changes are committed back to the incoming pull request.
name: autosqlfmt
on: [pull_request]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: Set up Python 3.7
uses: actions/setup-python@v1
with:
python-version: 3.7
- name: install sqlfmt
run: pip install shandy-sqlfmt[jinjafmt]
- name: if needed, commit sqlfmt changes to the pull request
run: |
sqlfmt models/.
git config --global user.name 'autosqlfmt'
git config --global user.email<EMAIL_ADDRESS>git remote set-url origin https://x-access-token/:${{ secrets.GITHUB_TOKEN<EMAIL_ADDRESS>git checkout $GITHUB_HEAD_REF
git commit -am "fixup: format sql with sqlfmt"
git push`

@sgoley how's this for changed files only?
sqlfmt $(git diff --name-only)

@tconbeer here's what I ended up doing since Emily Hawkins rightly pointed out from drizly that there can be a lot of edge cases:
https://gist.github.com/sgoley/af3e1f857251786afb1d739ada2e2a03
I actually had to fork the dbt cloud actions package from fal.ai to get the schema override working but it does everything I need now.

thanks. @sgoley fwiw, sqlfmt will ignore/exclude any files that don't end in .sql or .sql.jinja, so you shouldn't need all of those grep steps on changed files -- you can pass files with any extension to sqlfmt and we'll do the right thing.

And the reason we did the loop like this:
run: |
          for changed_file in ${{ steps.get_files_to_lint.outputs.lintees }}; do
            echo "formatting ${changed_file}"
            sqlfmt ${changed_file} || continue
          done

was because if the entire change manifest was submitted in a batch, one unformattable file would kill the whole job.
(We had a column which included a unicode character in the name)
Versus when you submit file by file, it will just fail that one file but correctly format the rest.


Add IPEX-LLM with GPU

Add IPEX-LLM with GPU

add a jupyter notebook for gpu like this https://github.com/run-llama/llama_index/pull/13097/files#diff-4de70abde948df04dbda0c1a6cc564e1bf27c5481665939db1f014df156e6679
add a new example which works for both CPU and GPU, migrate this example to use the new interface https://github.com/intel-analytics/ipex-llm/blob/main/python/llm/example/GPU/LlamaIndex/rag.py.
update the more_data_types to use GPU, but need to test other data types which only works on GPU, etc. fp4

add a jupyter notebook for gpu like this https://github.com/run-llama/llama_index/pull/13097/files#diff-4de70abde948df04dbda0c1a6cc564e1bf27c5481665939db1f014df156e6679
add a new example which works for both CPU and GPU, migrate this example to use the new interface https://github.com/intel-analytics/ipex-llm/blob/main/python/llm/example/GPU/LlamaIndex/rag.py.
update the more_data_types to use GPU, but need to test other data types which only works on GPU, etc. fp4

Various data types were tested, including: fp4, fp8, fp16, bf16, nf3, nf4, fp8_e4m3, fp8_e5m2. All generate normally.

remove rag.py and we shall add it to the next PR.
write a simple inference example just like in jupyter and add -d, -q, -m params
support only cpu/xpu and report error for others

also fix the test errors

add a jupyter notebook for gpu like this https://github.com/run-llama/llama_index/pull/13097/files#diff-4de70abde948df04dbda0c1a6cc564e1bf27c5481665939db1f014df156e6679
add a new example which works for both CPU and GPU, migrate this example to use the new interface https://github.com/intel-analytics/ipex-llm/blob/main/python/llm/example/GPU/LlamaIndex/rag.py.
update the more_data_types to use GPU, but need to test other data types which only works on GPU, etc. fp4

Various data types were tested, including: fp4, fp8, fp16, bf16, nf3, nf4, fp8_e4m3, fp8_e5m2. All generate normally.

add those options to example choices

Why using langchain description here?


Ensure that we check the ASN.1 type of an "otherName" before using it

We should not assume that the type of an ASN.1 value is UTF8String as
expected. We must actually check it, otherwise we could get a NULL ptr
deref, or worse memory errors.
Reported by David Benjamin.

Fixup pushed addressing feedback. Please take another look.

To be merged before the 3.0 branch.

Merged to master.


Change security CI build version 'latest' into build version '6705'

Signed-off-by: Ryan Liang<EMAIL_ADDRESS>Description
Change security plugin CI build version 'latest' into build version '6705' to include the change of removing jackson-databind in gradle for security plugin.
Category
Test fix
Issues Resolved

Related https://github.com/opensearch-project/security/issues/2324#issuecomment-1346908811
Related https://github.com/opensearch-project/security/pull/2325

Testing
GitHub Action
Check List

[x] New functionality includes testing
[ ] ~New functionality has been documented~
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Here is the link to the distribution build on Jenkins: https://build.ci.opensearch.org/job/distribution-build-opensearch/6705/


Default FUZZYCD_MODE is inconsistent in readme

Hi, I noticed that the Fuzzy search section says interactive mode is the default:

If more than one directories match, you will be prompted to choose one of the matching directories when running in interactive mode (default), or you will cd to the best match when running in non-interactive mode.

However the Show Usage Pattern section says non-interactive mode is the default:

FUZZYCD_MODE
Set operation mode (one of: m, i, p)
m = minimal, non interactive, always cd to best match (default)
i = interactive when needed, no preview
p = interactive when needed, with ls preview

Based on my setup process it looks like non-interactive is the correct default.

Thank you for pointing that out.
Originally, the interactive mode was the default, but with the latest release (changelog), I decided to make the non interactive mode the default - since I personally was using the non interactive mode exclusively from the get go, and figured people don't want to waste time in menus when CDing.
I will fix the README.


[ Question ] There are two setting files in indexing directory: .env and settings.yaml. Which one is necessary to make this project work?

It looks that the .env file is used by Indexer Application and API, and settings.yaml is used by Embeddings Proxy?
Will it be combined into one file in the future?
Another question:
We can change the settings in  .env file through index_app.py .
How can we update the content of settings.yaml ? Can we just modify it manually now?

same question...


[Edge] handle invalid port number

Add error case if given port number is invalid.
Signed-off-by: Jaeyun<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #52. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


[UI] Fix dark mode on "Beginner-Friendly Repos"

Category

[ ] Resource Addition
[ ] Documentation
[ ] Codebase
[x] User Interface
[ ] Feature Addition

Description
Hey, I noticed that the cards on the page "Beginner-friendly repos" are very hard to read when the page is in dark mode. I would be happy to fix that!

Good catch, @Elaa257!
Go ahead. I'm assigning this to you.


Hoist SubmitMoveForm initial values up to page level

Description
This PR moves the initialValues passed into the SubmitMoveForm up to the Agreement page level. This should prevent Happo tests from failing all the time, since one of those initial values defaults to the current date. This is also an architectural improvement, since most of the time initialValues data will come from the API / Redux / some other external source and will need to be mocked out in Storybook anyways.

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 3f637e1706990ec8349472645dc9b1f964b0bed7


chore: add skipOnWin and skipOnUnix test helpers

This adds skipOnWin and skipOnUnix to help us manage our platform-dependent
tests. These methods give a nice warning message when we skip tests. We may also
consider adding warnings when running platform-dependent tests.
Part of the motivation for this is if we ever update to AVA v0.19. This version
requires at least one assertion per test case. While this could be disabled with
an AVA setting, we instead benefit from warnings for any case when we
unintentionally skip assertions.
This adds chalk as a dev dependency to enable colored messages.

Codecov Report

Merging #746 into master will decrease coverage by 0.25%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #746      +/-   ##
==========================================
- Coverage   97.38%   97.12%   -0.26%
==========================================
  Files          33       33
  Lines        1222     1252      +30
==========================================
+ Hits         1190     1216      +26
- Misses         32       36       +4

Impacted Files
Coverage Δ

src/exec.js
96.33% <0%> (-3.67%)
: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 5823ab1...adc4613. Read the comment docs.

The coverage report is wrong, this doesn't actually change exec coverage. I just didn't rebase off master after #742 landed.

self-LGTM since this doesn't affect production logic (and doesn't actually affect coverage)


enable / disable mechanism for logging of files, which is outside of project

Dear developer,
https://github.com/gitflow-incremental-builder/gitflow-incremental-builder/blob/05538a565ed7422e0234b7ad23406e2315a4e439/src/main/java/io/github/gitflowincrementalbuilder/ChangedProjects.java#L58
do you can add a configuration to enable / disable this logging? it makes a problem (shows to much ignoring files at pipeline or logs), if we want use it with multi module project (contains not maven projects). It would be better enable or disable it.

Hi @TheMertos,
funny you mention this given I've literally just lowered it from WARN to DEBUG.
In upcoming 4.2.0 you won't be seeing such messages anymore (unless you activate debug loggin).
Does this already address your concern or do you need more?

hmm. i am asking me, that it can be enough or not enough for us. when do you want publicate the 4.2.0 version?

4.2.0 is out. I'll close this for now but if people complain and want a toggle instead, I'll reopen this issue.

Thx for new release, it is working.


Test /overdue command with some chores

Improve test_overdue_command():

[x] Create some chores with factories
[x] Check if the chores appear in the output of the /overdue command

Done in #53.


Can someone kindly tell me how to use YCSB to access the HBase cluster with Kerberos authentication enabled

Can someone kindly tell me how to use YCSB to access the HBase cluster with Kerberos authentication enabled.
I tried many methods, but nothing worked.
Such as :
./ycsb run hbase20 -P /data0/backup/ycsb/ycsb-hbase20-binding-0.16.0-SNAPSHOT/workloads/workloada -p table=acceptanceTestTable -p columnfamily=cf1 -p recordcount=1000 -p operationcount=1500 -p fieldcount=1 -p fieldlength=3 -p kerberos=true -p kerberoskeytab=/etc/security/keytabs/spnego.service.keytab -p<EMAIL_ADDRESS>-p debug=true
But i got is ：
Tue Sep 15 17:40:45 CST 2020, RpcRetryingCaller{globalStartTime=1600162716959, pause=100, maxAttempts=16}, javax.security.sasl.SaslException: Call to /<IP_ADDRESS>:16020 failed on local exception: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7) - LOOKING_UP_SERVER)] [Caused by javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Server not found in Kerberos database (7) - LOOKING_UP_SERVER)]]

you need to let the hbase client know what your hbase configuration is. usually this happens by adding an appropriate hbase configuration directory via the classpath. with that you can just kinit before running ycsb.
e.g. ./bin/ycsb run hbase20 -cp /etc/hbase/conf -p columnfamily=family -s -P workloads/workloada

Thank you very much for your reply.I solved this problem by adding the attribute:
-p keytab=/etc/security/keytabs/hbase.headless.keytab -p principal=xx
Of course hbase configuration  of YCSB  is the same as HBase cluster configuration.
I am new to ycsb, thank you very much for resolving my problem.
`

hbase.security.authentication
kerberos

<property>
  <name>hbase.security.authentication.spnego.kerberos.keytab</name>
  <value>/etc/security/keytabs/spnego.service.keytab</value>
</property>

<property>
  <name>hbase.security.authentication.spnego.kerberos.principal</name>
  <value>xxx</value>
</property>

<property>
  <name>hbase.security.authorization</name>
  <value>true</value>
</property>

`

happy to help.


use built in dynamic service module instead of import from node_modules

replaces @kbase/narrative-utils KBaseDynamicServiceClient with internal dynamic service interface
Fixes issue where dynamic service will only make calls to the ci environment.
https://github.com/kbaseIncubator/narrative-utils/blob/master/src/config.ts#L22

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 6 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 51.253%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/client/components/dashboard/NarrativeList/ControlMenu/RevertNarrative.tsx
1
2
50.0%

src/client/utils/narrativeData.ts
2
4
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
962

Relevant Lines:
1667

💛  - Coveralls


Fix compactor skips data from last compacted Ledger

The PR is fixing the compacted data lost during the data compaction.
We see a few events deletion but the compacted events obviously dropped a lot.

After investigating more details about the issue, only the first read operation reads the data from
the compacted ledger, since the second read operation, the broker start read data from the original
topic.
2021-10-19T23:09:30,021+0800 [broker-topic-workers-OrderedScheduler-7-0] INFO  org.apache.pulsar.compaction.CompactedTopicImpl - =====[public/default/persistent/c499d42c-75d7-48d1-9225-2e724c0e1d83] Read from compacted Ledger = cursor position: -1:-1, Horizon: 16:-1, isFirstRead: true
2021-10-19T23:09:30,049+0800 [broker-topic-workers-OrderedScheduler-7-0] INFO  org.apache.pulsar.compaction.CompactedTopicImpl - =====[public/default/persistent/c499d42c-75d7-48d1-9225-2e724c0e1d83] Read from original Ledger = cursor position: 16:0, Horizon: 16:-1, isFirstRead: false

The compaction task depends on the last snapshot and the incremental
entries to build the new snapshot. So for the compaction cursor, we
need to force seek the read position to ensure the compactor can read
the complete last snapshot because the compactor will read the data
before the compaction cursor mark delete position.

@codelipenghui:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)


scikit-image handout

First public draft of the scikit-image handout. Comments welcome. This is loosely based on the Tufte-LaTeX/tufte-latex handout theme, but I've customized it heavily. The idea was to have a professionally created, two-sided, single page document available to hand out to tutorial attendees or from an open source table.
This is a fully reproducible document. cd into skimage-media/handout and run make, which

Cleans the directory of any temporary files
Generates and saves figures with individual Python scripts
Runs the necessary LaTeX routines to build the document

pdflatex
bibtex
pythontex
pdflatex
pdflatex (just to be sure)

Clips the final, wasted page which contains only a redundant bibliography

I have used only the minimal necessary media files to keep the repo size down, so no example version of the handout PDF is included. However, at time of submission it should look like this: handout.pdf

Ping @stefanv, @blink1073 - How does this look to you? I wrestled with LaTeX for a while trying to get a symmetric two-column layout going, Stefan, and it wasn't working well. So I opted to fall back on the style of Edward Tufte.

References are missing.

There is literally no space to attempt to reference everything going on in the handout. The only reference is to the scikit-image paper, and the citation for this style is inline (specifically, to the right). The bibliography is redundant with that citation, so it's pushed onto a third page and clipped. Superscripts use the \footnote command, which in this style prints to the right column, for figure captions to save room.

This looks great @JDWarner, thank you!  It would be nice to have a link to the PDF in the intro notebook, in case folks want a soft copy.  By the way, what was the mechanism for uploading that file?

Drag and drop! GitHub magic. Works just like an image in the post, except no preview.
Tried it on a whim... I didn't expect it to work, to be honest ;)

Excellent, free perma-link.

Updated handout PDF
including the latest three commits. All live functions on reverse side now properly colored DarkBlue.

Works for me, merging.  Thanks @JDWarner!


No horizontal scrollbar on wide tables

The Problem
There is not horizontal scrollbar on wide images.

The solution
Modifying the CSS of tables to suggest that tables too wide for the screen are horizontally scrollable.

Got the same issue here with the latest version. It is really annoying that the UI is not adjusting itself to the Flipper window. The only way to 'scroll' to data is to select the row and just move the move to the left or right.
It should be really great if this issue was resolved.


replace apache reload command failed using nginx

Hello,
There is a problem using nginx ,I get the following error :
==> web: NoMethodError
==> web: -------------
==> web: undefined method `log' for Chef::Resource::RubyBlock
==> web:
==> web: Cookbook Trace:
==> web: ---------------
==> web: /tmp/vagrant-chef/aba213e03e907056b52b53b485f9b906/cookbooks/zendserver/recipes/default.rb:99:in `rescue in block (2 levels) in from_file'
==> web: /tmp/vagrant-chef/aba213e03e907056b52b53b485f9b906/cookbooks/zendserver/recipes/default.rb:95:in `block (2 levels) in from_file'
==> web:
==> web:
==> web: Resource Declaration:
==> web: ---------------------
==> web: # In /tmp/vagrant-chef/aba213e03e907056b52b53b485f9b906/cookbooks/zendserver/recipes/default.rb
==> web:
==> web:
==> web:  93: ruby_block 'replace apache reload command' do
==> web:
==> web:  94:   block do
==> web:
==> web:  95:     begin
==> web:  96:       r = resources('service[apache2]')
==> web:  97:       r.reload_command('/bin/true')
==> web:
==> web:  98:     rescue Chef::Exceptions::ResourceNotFound
==> web:
==> web:  99:       log "service[apache2] resource not defined. Skipping restart."
==> web:
==> web: 100:     end
==> web: 101:   end
==> web: 102: end

Thanks

@Arnch Thanks for opening the issue - I added the block due to a problem with Apache, but omitted to put a guard for Nginx - I will fix shortly.
Thanks!


Reliability vs Plausibility

in trying to empathize for the end user (a person interested in reliability of representation of real human behavior over n time),   I find myself asking:

what has this done wrong about real time human behavior?
what would be more real natural and organic?
is this framework even reasonable or reliable?

Let's ask AI about these questions:
The provided JSON structure outlines a simulation setup to model consumer reactions to a new product launch in the consumer electronics market, specifically a smartwatch. It employs a combination of environmental settings, agent attributes, and time configurations to generate a series of events using AI. Here are several considerations regarding the realism, naturalness, and reliability of this framework when it comes to capturing real-time human behavior:
Simplicity vs Complexity:
The model seems to simplify human behavior to a set of predefined traits, interests, and past experiences. Real human behavior is complex and can be influenced by a myriad of factors including emotions, external events, and interactions with other individuals which are not accounted for in this model.
Static vs Dynamic Attributes:
The attributes of agents are static as defined in the model. In reality, individuals evolve over time based on their experiences and interactions. Their awareness, interests, and affiliations could change over time, which is not captured in this static model.
Individual vs Collective Behavior:
The simulation appears to focus on individual behavior without a clear mechanism for collective behavior emergence. In real markets, trends and collective behaviors play a significant role. For example, the popularity of a product could change based on collective reactions, which in turn could influence individual decisions.
Predictability vs Unpredictability:
Human behavior is inherently unpredictable and can be highly influenced by external factors. The model may not capture this unpredictability if it relies solely on predefined conditions and deterministic rules.
Homogeneous vs Heterogeneous Agents:
The model has a structured approach to defining agent attributes, which may lead to the creation of homogeneous agents. In reality, consumer markets are characterized by heterogeneous agents with diverse behaviors, preferences, and decision-making processes.
Explicit vs Implicit Relationships:
The model defines explicit relationships between agents. However, in real life, many relationships are implicit or hidden, and their influence on decision-making is subtle and complex.
Deterministic vs Stochastic Processes:
The real world often involves stochastic processes where outcomes have a degree of uncertainty, whereas the model might lean towards deterministic outcomes based on the set conditions.
Feedback Loops:
The model doesn't seem to account for feedback loops where the agents' decisions influence the environment and vice versa. Feedback loops are crucial for understanding complex systems dynamics.
Context Awareness:
The model outlines a specific environment context but it's not clear how deeply the simulation considers the broader socio-economic-political context, which can significantly impact consumer reactions.
Validation and Calibration:
For this framework to be reliable, it would require rigorous validation and calibration against real-world data to ensure that it accurately reflects real human behavior and market dynamics.
Data-Driven vs Assumption-Driven:
It's important that the assumptions and initial conditions in the model are data-driven and reflect real-world conditions as closely as possible. Otherwise, the simulation results may not be reliable or generalizable.
In conclusion, while the framework provides a structured approach to simulating a market scenario, its realism, naturalness, and reliability in capturing real-time human behavior might be limited. Enhancements such as incorporating dynamic attributes, stochastic processes, feedback loops, and a mechanism for emergent collective behavior, along with rigorous validation against real-world data, could make the framework more realistic and reliable.

Thanks for addressing this. We are currently trying to improve on these points. More to come.


feat: multiple tcp collectors, broadcast actions

Closes #
Enable multiple collectors, broadcasting actions as received, to all connected applications.
Changes

Accept multiple TCP connections
Broadcast actions to all connected applications, let the application choose if they want to process the received action or not

NOTE: current_action still limits how many actions we can process at a time, so if an action was broadcast to all connected apps, uplink will not broadcast the next action until the action being processed times out or returns a "Completed"/"Failed" status.
Why?
Users might want to connect multiple applications to a single uplink instance, with the same TCP port/bridge.
Trials Performed

Multiple applications are able to connect and send data, while also being able to receive the same action as each other.
When no application is connected, bridge down error is forwarded to platform.

we could make use of a rendezvous channel to ensure no action is left waiting while we are processing another action.

@de-sh Bridge disconnected status is not being sent. To reproduce send an action and then disconnect the client

@de-sh Bridge disconnected status is not being sent. To reproduce send an action and then disconnect the client

Because we are moving to a broadcast mechanism and do not have context on which device is handling what action, it would only be possible to send bridge disconnected response when there are no apps connected and the action times out. I suggest we remove that response and keep to the regular "Action timed out" response in that case.

@bmcpt have come up with a way to notify bridge disconnection. Still believe this a bit more complicated than we require it to be. An application that is not consuming the current_action will still hold the "Bridge disconnected" response hostage till timeout, when the concerned application dies out while consuming.

Great, this retains the current behavior for single client connections.


Unable to install vim-gitgutter

I am trying to install vim-gitgutter using Vundle but I'm getting the following error:
[2017-07-26 23:09:05] Plugin URI change detected for Plugin vim|  1
    -gitgutter                                                     |~
  2 [2017-07-26 23:09:05] >  Plugin vim-gitgutter old URI:         |~
  3 [2017-07-26 23:09:05] >  Plugin vim-gitgutter new URI: https://|~
    github.com/airblade/vim-gitgutter.git                          |~
  4 [2017-07-26 23:09:05]                                          |~
  5 [2017-07-26 23:09:05] Plugin airblade/vim-gitgutter            |~
  6 [2017-07-26 23:09:05] $ cd '/home/aks/.config/nvim/bundle/vim-g|~
    itgutter' && git remote set-url origin 'https://github.com/airb|~
    lade/vim-gitgutter.git' && git fetch && git reset --hard origin|~
    /HEAD && git submodule update --init --recursive               |~
  7 [2017-07-26 23:09:05] > fatal: Not a git repository (or any of |~
    the parent directories): .git                                  |~
  8 [2017-07-26 23:09:05] >

Can you please help me with this?
I have also opened an issue here
https://github.com/airblade/vim-gitgutter/issues/429

Seems you have the plugin (without cloning a repo in /home/aks/.config/nvim/bundle/vim-gItgutter)


Microcharts.forms failed to load assembly

Hello,
I installed Microcharts.Forms to my project and tried to add in a content page "<microcharts:ChartView x:Name="chartView" />" as in the example, but when I run on iOS I get the following error: "Failed to resolve assembly:'Microcharts.Forms, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null".
Version 0.7.1 for Microcharts.Forms and I am using Xamarin Live Player.
Thanks

Hi
I have same problem...

i have solved this problem.
i added "var ignore_chartView = new Microcharts.Forms.ChartView();" in FinishedLaunching method (AppDelegate.cs)

Hello @gribnikpayk ,
I tried adding that line, but it still does not work for me. It does not even enter this method.
`[Register("AppDelegate")]
public partial class AppDelegate : global::Xamarin.Forms.Platform.iOS.FormsApplicationDelegate
{
public override bool FinishedLaunching(UIApplication app, NSDictionary options)
{
        var ignore_chartView = new Microcharts.Forms.ChartView();
        global::Xamarin.Forms.Forms.Init();
		LoadApplication(new App());
        return base.FinishedLaunching(app, options);
	}
}`

Did u try adding that line after
global::Xamarin.Forms.Forms.Init();

Yes, I did. I still have the same problem. It does not even enter in that method

I have installed microcharts nuget package to iOS project. I have also installed microcharts.forms to .NET Standard project.

I'm having the same issue on VS Mac 7.3.2 But it works as demonstrated on Windows VS 15.5.0
In comparing the 2 environments, I notice that Windows is using targeted Framework .Net Standard 2.0 and OSX is using .Net Standard 1.5.  I've been struggling getting the OSX VS project to work, but Windows works as described.   Does anyone more familiar with the project/environments have a workaround or advise?  I've tried the advise recommended above bit it does not change the outcome
Generally frustrating now that I have dueling VS environments on and such different behaviors/outcomes on each...   Thanks in advance for any advise

I would suggest to switch to preview channel if you didn't try yet. A new release is coming by the beginning of 2018.
Do you have the same issues with the samples ?

Hello! I'm attempting to clean up some of these older issues that haven't had any movement for a few months, if here is still and issue or enhancement to be made, please create a new issue, and feel free to reference relevant parts of this issue if necessary.
Thanks!