npx stryker run with Jest does not work

Summary
I was running the 0.34.x version previously in my project.  I have since removed all traces to stryker, installed the new @stryker-mutator/core and proceeded to use the npx stryker init to install the dependencies and try to get stryker working in my environment with Jest and Yarn.
While my Jest tests all run normally, I get errors running stryker: npx stryker run stryker.conf.js.  The error indicates that test files were not found.
11:49:51 (11656) WARN ChildProcessProxy Child process [pid 13664] exited unexpectedly with exit code 1 (without signal). Last part of stdout and stderr was:
No tests found, exiting with code 1
Run with --passWithNoTests to exit with code 0
No files found in C:\Users\stevens\Development\TestScripts\Emulator.stryker-tmp\sandbox1586172.
Make sure Jest's configuration does not exclude this directory.
To set up Jest, make sure a package.json file exists.
Jest Documentation: facebook.github.io/jest/docs/configuration.html
Pattern:  - 0 matches

Stryker config

module.exports = function(config) {
  config.set({
    mutator: "typescript",
    packageManager: "yarn",
    reporters: ["html", "clear-text", "progress"],
    testRunner: "jest",
    transpilers: ["typescript"],
    coverageAnalysis: "off",
    tsconfigFile: "tsconfig.json",
    mutate: [
    	"src/**/*.ts",
		"!src/**/*.spec.ts"
    ],
	htmlReporter: {
		baseDir: 'docs/mutation'
	}

  });
};

Stryker environment

$ yarn list |grep stryker
├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>

$ yarn list |grep jest
├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  └─ @types/jest-diff@*
├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>
Test runner environment

jest --config jest.config.js --no-cache

module.exports = {
	// Indicates whether the coverage information should be collected while executing the test
	collectCoverage: true,

	// An array of glob patterns indicating a set of files for which coverage information should be collected
	collectCoverageFrom: [
		'<rootDir>/src/**/*.ts',
		'!<rootDir>/src/**/*.mock.ts',
		'!<rootDir>/src/**/*.module.ts',
		'!<rootDir>/src/**/*.spec.ts',
		'!<rootDir>/src/**/*.test.ts',
		'!<rootDir>/src/**/*.d.ts',
		'!<rootDir>/src/**/__*__/*',
	],
	// The directory where Jest should output its coverage files
	coverageDirectory: "<rootDir>/docs",

	// An array of regexp pattern strings used to skip coverage collection
	coveragePathIgnorePatterns: [
		"\\\\node_modules\\\\"
	],

	// A list of reporter names that Jest uses when writing coverage reports
	coverageReporters: [
		"lcov",
		"clover"
	],

	// Make calling deprecated APIs throw helpful error messages
	errorOnDeprecated: true,

	// A set of global variables that need to be available in all test environments
	globals: {
		"ts-jest": {
			"diagnostics": false,
			"tsConfig": "tsconfig.json"
		}
	},

	// An array of file extensions your modules use
	moduleFileExtensions: [
		"ts",
		"tsx",
		"js"
	],

	// A list of paths to directories that Jest should use to search for files in
	roots: [
	   "<rootDir>/src"
	],

	// The test environment that will be used for testing
	testEnvironment: "node",

	// The glob patterns Jest uses to detect test files
	testMatch: [
		"**/*.spec.ts"
	],

	// A map from regular expressions to paths to transformers
	transform: {
		"^.+\\.(ts|tsx)$": "ts-jest"
	},

	// Indicates whether each individual test should be reported during the run
	verbose: false
};

Your Environment

software
version(s)

node
11.6.0

npm
6.5.0-next.0

yarn
1.15.2

Operating System
Windows 10

Add stryker.log
stryker.log

Hi @Chowarmaan thanks for opening this issue.
Could you please remove the transpilers part of your stryker.conf.js file and try again? Since your using Jest, it will take care of the typescript transpiling. Stryker doesn't need to do that for you.

@nicojs That corrected my issue.  I guess I still flagged the additional transpiler option during the stryker init as I did not enter that myself.  It has allowed my tests to run again.

One of the questions during stryker init is:

[optional] What kind transformations should be applied to your code?

That's where you probably selected typescript. Maybe this question should be reworded to:

[optional] What kind transformations should Stryker apply code? If your test runner transpiles your code, select none here,

@Chowarmaan would that help you?
@simondel, agree?

I think that might of, but maybe still not in my case unless the note is clearer for Jest somehow as I would still have expected to need to transpile the code for things to work.  I did not think to deep about it, or really understand what you might be pointing at, even though webpack and others are there (if it is the area I am thinking of).

Hmmm maybe we should give a warning from the JestRunner. Something like: "WARN: You configured the "typescript" transpiler. This is probably not needed since Jest normally takes care of that.   I actually just ran your same init over an Angular CLI project, and the caution about needing a transpiler (I did not) made me think as well.  I think for the more beginner users like myself with Stryker, and some of the ecosystem of these tools, who are working with Typescript and trying to make the best code possible, these clearer examples would help.
On a side note, love the tool as Mutation testing has certainly helped me improve and find some subtle bugs.

@nicojs I think we should improve the message using Stryker init and we should warn the user when they specify transpilers with Jest. I'm fine with leaving this warning on instead of introducing another config setting.

@simondel @nicojs
Faced with same issue
Looks like it is jest issue https://github.com/facebook/jest/issues/8520
Stryker creates temp folder with name .stryker-tmp
D:\My\Dev\node-package-starter>npx jest --runInBand --testMatch "<rootDir>/.stryker-tmp/sandbox6795124/src/**/*.spec.ts"
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In D:\My\Dev\node-package-starter
  11 files checked.
  testMatch: D:/My/Dev/node-package-starter\.stryker-tmp/sandbox6795124/src/**/*.spec.ts - 0 matches
  testPathIgnorePatterns: \\node_modules\\ - 11 matches
  testRegex:  - 0 matches
Pattern:  - 0 matches

After renaming temp folder to stryker-tmp without dot
D:\My\Dev\node-package-starter>npx jest --runInBand --testMatch "<rootDir>/stryker-tmp/sandbox6795124/src/**/*.spec.ts"
 PASS  stryker-tmp/sandbox6795124/src/index.spec.ts
  √ smoke (6ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        2.204s, estimated 3s
Ran all test suites.

Can we configure name of the temp folder?

So what about it?

Suggested workaround in facebook/jest#8520 replace <rootDir> by real absolute path.

Can't help in this case because  is dynamic when I run stryker run.

It works correctly when I changed temp directory name to stryker-tmp in source code (right in node_modules, just for test). So, can you rename it or at least add config option to rename it?

For me I hit this issue too when using ts-jest. Removing the config-part transpilers: ["typescript"], from the stryker.conf.js helped.
As there already are none-options to select, how about just giving the option to not have transpilers being filled? Would reduce this to a RTFM-issue the next time ;) (at least regarding this configuration issue).

Is this issue still present?

The initial errors were corrected via my configuration and removing the transpilers. Not sure if this issue still being open is for the help/error/init messaging or another reason.

so i believe it can be closed?


Investigate memory usage of BoundsChecker

Followup w/ @velvia re: memory profiling results

check bounds doesn't really allocate much at all, I'm going to repurpose this issue. As I think the real issue is running the bytecode verifier every time the module is used/loaded.

@tnowacki note that I did not observe any check_bounds for prod profiling when the memory was above 1GB.  So the above issue might be something only for no load, no follower CI setup environment, ie this can be considered very low priority.


Extension issue

Issue Type: Bug
Extension Name: jupyter
Extension Version: 2021.2.603412351
OS Version: Windows_NT x64 10.0.19041
VSCode version: 1.53.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:
{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 2681,
		"activateCallTime": 16,
		"activateResolvedTime": 4469,
		"activationReason": {
			"startup": false,
			"extensionId": {
				"value": "ms-toolsai.jupyter",
				"_lower": "ms-toolsai.jupyter"
			},
			"activationEvent": "onLanguage:python"
		}
	},
	"runtimeErrors": [
		{
			"name": "Error",
			"message": "IPyKernel not installed into interpreter Python 3.9.2 64-bit:C:\\Users\\micae\\AppData\\Local\\Programs\\Python\\Python39\\python.exe"
		},
		{
			"name": "Error",
			"message": "IPyKernel not installed into interpreter Python 3.9.2 64-bit:C:\\Users\\micae\\AppData\\Local\\Programs\\Python\\Python39\\python.exe"
		}
	]
}

thank you, i don't know why it hasn't bug now!


Bump log4j to 2.17.1

Is your feature request related to a problem? Please describe.
Coming from https://github.com/opensearch-project/opensearch-build/issues/1417, Log4j 2.17.1 is available with CVE-2021-44832.
OpenSearch core already upgraded, so build is failing for 1.3.0 as well.
Describe the solution you'd like
Bump log4j to 2.17.1.

https://github.com/opensearch-project/sql/pull/354

https://github.com/opensearch-project/sql/pull/356


Test coverage is below 100%

The current test coverage report for the master branch is (omitting the test program itself):
---------- coverage: platform linux2, python 2.6.9-final-0 -----------
Name                Stmts   Miss  Cover   Missing
-------------------------------------------------
ld/__init__           155     15    90%   124, 191, 366, 370, 374, 378, 382, 390, 394, 398, 402, 406, 410, 414, 418
ld/constants           15      0   100%
-------------------------------------------------

Looking at the missing lines of code, it seems possible to get to 100%.
I have an idea for all of them, and will post a few merge requests.

All conflicts resolved, see PR #39.

PR #46 brings the test coverage to 100%.


Better grep format handling

my grep (and git grep) configuration produce the following output:
path/to/file:123:some text here
The grepped text follows the last colon, without any space. When I
double click on my terminal, it stops at first space, then my following
line would be:
vim path/to/file:123:some
Current regex pattern recognizes this text as valid, but the len is not
valid.
This patch takes into account the potential text following the last
colon.

Merged, thanks!


osce11-0-en.url.trendmicro.com

Regarding osce11-0-en.url.trendmicro.com
It is used for my Trend Micro AV to initiate Smart Scans, and it is their Global Web Rating Server
Safe to remove. Only one 545 (literally actually) other blocklist has this, and I have reported it there as well.
https://success.trendmicro.com/solution/1113595-smartscan-unavailable-shows-up-and-agents-cannot-connect-to-the-global-scan-server-in-officescan
https://success.trendmicro.com/tw/solution/1107850

I've added it to the whitelist, and thanks for reporting it upstream.


Popup windows getting closed when we click on the outside

This is more visible with slow network connections. Let say we deprecated an API and there will be a popup window saying "Deprecating the API". When the operation completed, the popup window will be automatically closed. But when there is a slow network connection, it will get some time to close. If accidentally someone clicked on outside, the popup will go away and now it is difficult to figure out when the operation completes.

This behavior is not valid since the new UI revamp (3.x) hence closing the issue, Fixed in master branch.


[#162113648] UAA: allow emails with more than 4 domain parts

What
The default allowlist for UAA's internal IDP only allows users with 4
parts in their email domain[1]. This means that UAA returns an error
when we (or an Org Manager) attempts to invide a user with 5 or more
components in their email domain.
It doesn't appear to be possible to configure this via UAA's config file
(as per a conversation on CF slack[2]), and therefore via the manifest,
so instead we have to add a post-deploy job to update this via UAA's
API. This extends the list to allow up to 6 components in the domain.
This should be enough for now, and it's reasonably simple to extend
further if needed.
[1]https://github.com/cloudfoundry/uaa/blob/4.24.0/server/src/main/java/org/cloudfoundry/identity/uaa/util/DomainFilter.java#L103
[2]https://cloudfoundry.slack.com/archives/C03FXANBV/p1542628288065500
How to review
I've already done the following in my dev env:

Attempt to invite a user with 5 components in the email (eg user@a.b.c.example.com), and see it fail.
Deploy from this branch
Repeat the attempt and see it succeed.

This script might be useful to manually invite a user:
#!/bin/bash

set -e -u -o pipefail

# INPUTS

uaa_admin_client_secret=<INSERT_HERE>
login_url=https://login.${DEPLOY_ENV}.dev.cloudpipeline.digital
uaa_url=https://uaa.${DEPLOY_ENV}.dev.cloudpipeline.digital
redirect_uri=https://admin.${DEPLOY_ENV}.dev.cloudpipeline.digital

# SCRIPT

basic_auth_client_creds=$(echo -n "admin:$uaa_admin_client_secret" | base64)
access_token="$(curl \
  --silent \
  --fail \
  --header "Authorization: Basic $basic_auth_client_creds" \
  --data 'grant_type=client_credentials' \
  "$login_url/oauth/token" | jq -r '.access_token')"

email=$1

curl --fail \
  -H "Authorization: bearer $access_token" \
  -H "Accept: application/json" -H "Content-Type: application/json" \
  -X POST \
  -d "{\"emails\": [\"${email}\"]}" \
  "${uaa_url}/invite_users?redirect_uri=${redirect_uri}&client_id=user_invitation"

Who can review
Not me.

I've tested that this only affects inviting users, and that they can still login when this gets reverted, so I think this is an acceptable workaround for the time being.
I'm going to raise an issue against UAA to get a more permanent fix implemented. I'll raise a follow-up story to look at that in a little while to see whether we need to fix that ourselves


Get status of services via API

Hi,
I'm working on a dashboard that would also display a summary of our Cabot monitoring.
The API should be the way to go, but after playing with it for some time I can't find a call that returns the current status of our services? Am I missing something or is this feature just not available?
Thank you for your feedback!
Jeroen

depending on what you're looking for:
you can grab the information needed through this endpoint:
http://[my cabot host]/api/status_checks/
example:
{
        "name": "my_check",
        "active": true,
        "importance": "ERROR",
        "frequency": 5,
        "debounce": 2,
        "calculated_status": "passing", <== LOOK HERE
        "id": 787
    },

or this api endpoint:
http://[my cabot host]/api/services/
example:
 {
        "name": "my_services",
        "users_to_notify": [
            3,
            4,
            5,
            6
        ],
        "alerts_enabled": true,
        "status_checks": [
            790,
            789,
            792,
            791,
            787,
            788
        ],
        "alerts": [
            1,
            4
        ],
        "hackpad_id": "",
        "url": "[my hostname]",
        "instances": [],
        "overall_status": "PASSING",  <== LOOK HERE
        "id": 132
    },

a bit of json parsing should fullfill your needs :)
hoping this helps,

Thanks for you fast response!
We were not running the latest version. A simple git pull added the calculated_status field!


Import-AzSentinelAlertRule: Issue

Hi,
I am trying to create the Office 365 DLP rules in sentinel, stuck with below error
//Error//
Import-AzSentinelAlertRule:
Line |
18 |  … tem $file | Import-AzSentinelAlertRule -WorkspaceName $workspacename  …
|                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Unable to invoke webrequest with error message: Response status code does not indicate success: 400 (Bad Request).
//Error//
Below details verbrose for reference
//Verbrose//
VERBOSE: Rule Identified_PII_Data_in_Cloud_Low doesn't exist in Azure Sentinel
VERBOSE: Creating new rule: Identified_PII_Data_in_Cloud_Low
VERBOSE: PUT https://management.azure.com/subscriptions/ca6d3f14-Removed-47d2-bd39-57313ef18abc/resourcegroups/sentinel-lab-rg/providers/microsoft.operationalinsights/workspaces/sentinellabws/providers/Microsoft.SecurityInsights/alertRules/db1c463c-17ea-44fa-9dfe-removeda66a758?api-version=2019-01-01-preview with 1624-byte payload
VERBOSE: received 401-byte response of content type application/json
VERBOSE: {"error":{"code":"BadRequest","message":"FailedToResolveScalarExpression; Message: {"error":{"message":"The request had some invalid properties","code":"BadArgumentError","innererror":{"code":"SemanticError","message":"A semantic error occurred.","innererror":{"code":"SEM0100","message":"'extend' operator: Failed to resolve scalar expression named 'ObjectId_s'"}}}};"}}
Import-AzSentinelAlertRule:

Usually this is because you don't have events from both SharePoint and Exchange. From the verbose output you can see that it is successfully connected to your Sentinel instance. But fails upon rule creation.

Closing this for now please ask again if you don't get it to work.


Docs should indicated when connecting with KVM won't work in CCM Mode

@bwendlandt-intel has this issue been resolved?

This is mentioned during the CCM vs ACM branch as well as in a note when showcasing the device dashboard.  These have been included for a few versions.  Open to opinions if it is enough or is too easily skippable.

@rsdmike Docs update seems to cover this now.  Mike, you good with closing this?


Allow reordering of queued deployments

Imagine someone has queued 10-20 releases, but suddently there's an emergency on 21st and you need to push it out ASAP. Not sure if doable at all? Or does it even make sense?

Get what you are saying, not entirely sure it would be possible.... a queue is just that, a FIFO structure. I guess one potential would be to have a separate "high" priority queue which deployments only get put onto if you select a "high priority" option when deploying and then have a listener just for that queue. i'll have a think


Update docs on setting store credentials secret

Github UI has changed,
so the navigation path to setting a secret is different. Also update the screenshot,
because the previous screenshot showed
an example of data that was no longer a valid format.
Fixes: #39

cc @jhenstridge @sergiusens in case this was missed, thanks. :)

Gentle ping. The misleading screenshot caused me some unnecessary frustration.


Launching contributed command via TreeView Item UI doesn't always have a parameter

Does this issue occur when all extensions are disabled?:
Issue applies to the Extension API

VS Code Version: 1.60
OS Version: Ubuntu 20.04

Steps to Reproduce:

Create a basic vs code extension
Contribute a command to a TreeView, e.g. with the JSON below

{
	"contributes": {
		"viewsContainers": {
			"activitybar": [
				{
					"id": "viewContainer",
					"title": "View Container",
					"icon": "./resources/view-container.svg"
				}
			]
		},
		"views": {
			"viewContainer": [
				{
					"id": "view",
					"name": "View"
				}
			]
		},
		"commands": [
			{
				"command": "issue.command",
				"title": "Issue command",
				"icon": "$(x)"
			}
		],
		"menus": {
			"commandPalette": [
				{
					"command": "issue.command",
					"when": "false"
				}
			],
			"view/item/context": [
				{
					"when": "view == view",
					"group": "inline@1",
					"command": "issue.command"
				}
			]
		}
	}
}

Register a basic TreeViewProvider to match the above contribution
Click the icon on the newly-contributed TreeView
Repeat until the issue (randomly) happens

Expected
The command launches, with the TreeViewItem on which we clicked earlier as its argument
Actual
The command launches, sometimes with no argument. It then crashed, and shows an Information message saying the provided command could not run, ignoring vscode.window.showXMessage() if we attempt to run any
Additionnal info
The same behavior does not happen on other VS Code API implementations (e.g. theia), but the code was developed for VS Code, and tested on both

@clovis-dugue my understanding based on this issue is that the problem should occur for any tree view with any inline contributed command, is that correct?
I tried to repro ~30 times on an existing tree view, but I wasn't able to see the behavior you describe. Can you provide a repo with a full sample?


feat: add Title and new Typography #224

#216
close #224

:tada: This PR is included in version 7.34.0-next.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 7.35.0-next.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Revoking Apple Sign-In Authentication Tokens from Apple Server Upon User Deletion in AWS Amplify

Describe the bug
I am currently utilizing the Apple Sign-In function in my application through the hosted WebUI in AWS Amplify. Additionally, I have implemented the delete user account feature. However, despite using the delete user API (Amplify.Auth.deleteUser()), the user's account is not fully removed from the Apple Server.
Steps To Reproduce

1. Implement Apple Sign-In functionality in an iOS application using the hosted WebUI .
2. Implement the delete user account feature using the `deleteUser()` function provided by AWS Amplify.
3. Attempt to delete a user account and observe that the user's account is not fully removed from the Apple Server.
4. Verify that the app is still associated with Apple Sign-In: On your iPhone, go to Settings, then tap your name, tap "Sign-In & Security," then tap "Sign in with Apple."

Expected behavior
Upon initiating account deletion through the application, the user's account should be fully removed from the Apple Server, and the app should no longer appear under the settings: On your iPhone, go to Settings, then tap your name, tap "Sign-In & Security," then tap "Sign in with Apple.
Amplify Framework Version
2.27.0
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5.8
CLI version
12.10.0
Xcode version
15.1
Relevant log output
<details>
<summary>Log Messages</summary>

INSERT LOG MESSAGES HERE

```
Is this a regression?
Yes
Regression additional context
No response
Platforms
iOS
OS Version
iOS 17.0
Device
All iPhone Devices
Specific to simulators
No response
Additional context
No response

Hi @harsh62 , Do you have any update on this issue?

Hi @harsh62 ,
Thank you for providing the answers and the reference link. Is there any way I can obtain the latest token and authorization code to call the revoke Apple API endpoint before the user deletes their account? As mentioned, if the user doesn't manually delete their account or if we don't call the endpoint, the next time the user tries to register, AWS Amplify shows an error stating missing name and email attributes.

Hi @harsh62 , Thanks for the response. One more question in order to revoke we need one more required parameter which is client_secret . Where  can I get that? Is it also available or I need to map the same in custom attributes
https://developer.apple.com/documentation/sign_in_with_apple/revoke_tokens


Fix #221

Issue with .sg expiry parsing; simple update to the regex. I also accidentally included the fix for the datetime.UTC import, sorry about that - you can either remove it or accept it. For what it's worth, tests are passing for that change
Fixes #221

Thanks for all the PRs!


Show Request Body contents

Greetings, thanks for your great work, I have a problem showing the Request Body contents, what I send in the request is this:
{
"content": {
"username": "",
"password": "",
"channel": "",
"sourceChannel": ""
}
}
Here is the result:

What is needed is to show is the content JSON from the Request Body in the description field, can you tell me what to do?
Thanks again for your great effort.

it seems to me that you're encoding the JSON you're sending with base64 and then sending it, thus why it ends up this way.
Perhaps you're using something like JWT tokens?
In any case, we ourselves do not encode the request in the package, so it must be you doing it and sending it through like this.
You could perhaps hook into the lifecycle of the handler and decode the encoded token value, but that seems like a wrong solution and it will not represent the API correctly in the first place.

It may be related to #104

Any luck? im currently facing this issue

I guess I found the reason.
If u look at the official README.md
there is place:
Parameters and response body not documented!

Express-oas-generator (EOG) adds parameters handler as a very last middleware. If any middleware or path in router breaks the chain and doesn't pass execution to next middleware/router then very last EOG middleware won't be called. So call next() or next(err) as the very last line in your handler. Some docs:

calling next() https://expressjs.com/en/guide/writing-middleware.html
handling errors with next() https://expressjs.com/en/guide/error-handling.html
For more info please read the entire issue report

I tried to remove last middleware, that performs return res.json(rs);

If I'm reading https://expressjs.com/en/guide/writing-middleware.html correctly middlewares:

should not do return
should always call next()

In your case, I guess, the solution would be to modify return res.json(rs); to:
res.json(rs);
next()


Feature/users controller

Added some functionality. But still in progress.
Issue #3

Still need to test middleware controllers.


Unable to catch exception

I set up some audio addresses that could not be played and tried to get an exception. but 'audioPlayer.play( )' is always return 1 ,  and 'audioPlayer.onPlayerError.listen'  no message.
WrappedMediaPlayer can provide an optimization? thanks !
Logcat Message
I/flutter (21685): result = 1
E/MediaPlayer(21685): error (1, -2147483648)
E/MediaPlayer(21685): Error (1,-2147483648)
E/MediaPlayer(21685): stop called in state 0, mPlayer(0xb201ad00)
E/MediaPlayer(21685): error (-38, 0)

I'm having the same issue when the device in in airplane mode or there is no network connection and I'm playing an otherwise correct URL. I'd like to get an exception in this case or some other way to determine whether or not the URL can be loaded.

@luanpotter can we confirm if this still happens?

This issue is outdated or uses a very old version of the project, could you please test if this happens on newer versions? And in case that this still happens, open a new issue?


Cannot build as a framework

(I am working from one week of total iOS, and XCode experience, so please bear with me!)
I think this project cannot build as a framework when used by a Swift project (at least with XCode 7 beta 6). The main problem is "Include of non-modular header inside framework module".
From my limited research, I gather that this issue is somewhat new (as apparently frameworks are not the only way to organize subprojects); but it is becoming more urgent, since Swift projects cannot work around it. (One can disable this compiler error; however, the disabling is not honored in Swift projects, whether by bug or design.) A clear description of the problem is here: http://inessential.com/2015/03/16/swift_blocker
In any case, it sounds like the situation XCode caught is indeed problematic and should be fixed. (My understanding is that, .h files should not import system-wide .h files--.m files should; something about a naming conflict as multiple frameworks compile together). Here is your dependency, CocoaLumberjack struggling with the same issue.
So, modulo my naïve understanding, to be complete (except of course as a NOFIX), CDTDatastore needs to fix its own issues and then also upgrade to all dependencies when they fix theirs. This issue only applies to this project's specific build failure.
AFAICT, there is only one problem in the codebase:
/Users/jhs/src/cloudant/CDTDatastore/Classes/common/Encryption/Attachments/CDTBlobEncryptedDataConstants.h:20:9: Include of non-modular header inside framework module 'CDTDatastore.CDTBlobEncryptedDataConstants'

Unfortunately FMDB, also lacks support for frameworks, although that is being worked on see: https://github.com/ccgus/fmdb/issues/309 .There is a way around the frameworks issue. You need to add a bridging header to your project and use that to import CDTDatastore for use in your swift code.
The easiest way I've found to create a bridging header, is to create a new cocoa class from in the new file wizard, changing the language to objective-c and selecting the option to create the bridging header. In the bridging header you then add the line #import "CloudantSync.h". You'll have access to all the CDTDatastore classes from your swift code automatically, no need for import statements in your swift files.

Thanks @rhyshort!
Yes, my larger mission was, in fact, to work without the bridging header. That seems to be the future, AFAIK. CocoaPods tells Swift users to use_frameworks! and the GitHub issues on all these projects indicates that we are in a transitional period.
For expediency, I will work with a bridging header, thanks!
Again, I am a complete novice so I haven't got the perspective for this project or any Mac/iOS development. But my larger question is, is framework support an eventual goal for CDTDatastore?

Yes, we plan to support frameworks as soon as possible, once https://github.com/ccgus/fmdb/issues/309
get's fixed, we'll be looking into making CDTDatastore build as framework again.

The hack mentioned in ccgus/fmdb#309 is enough to work around the FMDB issues with building that module. However, once CDTDatastore is installed as a framework, my app's import CDTDatastore line generates the following error: Include of non-modular header inside framework module 'CDTDatastore.CDTBlobEncryptedDataConstants'
This error is coming from the following import statement:
#import <CommonCrypto/CommonCryptor.h>

Thanks for find that, I'll look into it when fmdb officially supports building a framework.

Hmm that's a bummer, I'd've hoped that CommonCrypto was modularised. Perhaps we buggered something up when building that bit.

I've just used version 1.0.0 with use_frameworks! on Xcode 7.2.1 and its not working. Is there something else required?  trying to remove use_frameworks! and add a bridging header is causing us a lot of issues with other pods.

Framework support hasn't been released yet, the current plan is to have it included in 1.1, but there are some other strategic priorities we'd like to include in the that release as well.

I'm just disabling Defines Module and Allowing Non-Modular frameworks to include CDT in my otherwise Swift-only project.

@rhyshort ok thanks. Is there any roadmap for 1.1? Were looking to integrate this into some products, but hacking are way around it isn't something we want to do. We got around it for our next POC by moving another pod to Objective-C, not a great story to tell. I would have figured swift interoperability would have been on the top of the list given IBM's shift.

Has there been any update on this?
Seems someone created a "SwiftFramework" branch inside FMDB 4 months ago, its not merged into master but may still solve the issue: https://github.com/ccgus/fmdb/tree/swiftFramework
Also why is this issue closed? isn't this still an issue? You are blocked on a dependency and have a plan to fix it in 1.1, but it hasn't been resolved yet. So should it not remain open until there is a fix available in a cocoapod release?

The issue is closed because CDTDatastore on Master can successfully built as a framework using the CocoaPods use_frameworks! directive.  FMDB fixed the issue of building as a framework in 2.6, which is the version we use. Our sample project makes use of this see Project/Podfile.
The issue is closed because it is resolved, our work flow is to close issues when the code is complete as this allows us to better track our status moving towards the next release.  Keeping the issue in the open state would make it difficult to track what we have done, and what issues we have yet to resolve which may be blocking the release. Therefore we attempt to close issues when the fix has been merged into master, which indicates it is ready for release.


Bug: When opening Files, it will close after 1–2 seconds

Description
When I enable “Toggle the preview pane”, it will automatically close when I close it and open it again
Screenshot

From Windows Event Viewer
Category: Files.App.App
EventId: 0

A cycle occurred while laying out the GUI.

Exception:
Microsoft.UI.Xaml.LayoutCycleException: A cycle occurred while laying out the GUI.

Solution
I found out that by disabling the “Toggle the preview pane” fixes the problem.

Steps To Reproduce

Open Files App
Click the three dots "..." or "See more" in the upper right corner
Click "New Pane"
Enable "Toggle the preview pane" or press "Ctrl + P"
Close the Files App
Open it again

Requirements
Fix crash when opening Files App because of adding a New Pane in Home and enabling “Toggle the preview pane”
Files Version
Version: <IP_ADDRESS>, Windows Version: 10.0.19044.2965
Windows Version
Windows 10 Pro 21H2 27/08/2022 19044.2965 Windows Feature Experience Pack 1000.19041.1000.0
Log file
debug.log

Thanks for the report. I am unable to reproduce this, Can you give the following information.

Can you see if this is an issue in the preview version. https://files.community/download

@Josh65-2201 this type of issue is usually dependent on the screen size and resolution, at the end of the day it's an issue with WinUI but there are workarounds that sometimes help. The main challenge is being able to reproduce the issue to work on a fix.

I reproduced by following steps.

Enable the Tags widget.
Enable the preview pane.
Star the dual pane mode.

@hishitetsu thank you so much

I forgot I change some of its settings

The crash seems to occur when the home page is too long vertically. The Tags widget tends to be longer and crashes more easily, but this is not a problem with the Tags widget itself.

@hishitetsu Do you think this is related issue in the WinUI team? https://github.com/microsoft/microsoft-ui-xaml/issues/7768

@hishitetsu Do you think this is related issue in the WinUI team? https://github.com/microsoft/microsoft-ui-xaml/issues/7768

It's the same issue, that said, the workaround mentioned in that issue won't work for us because we're on WinUI 3.

@wharjack this issue will be resolved in the upcoming v2.5.20 release.


fix: Properly dispose images when cache is cleared

Description
Disposes the images when they are removed or when the image cache is cleared.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the
relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[x] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[x] I have updated/added tests for ALL new/updated/fixed functionality.
[x] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[x] I have updated/added relevant examples in examples.

Breaking Change
Does your PR require Flame users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change. (Indicate it in the Conventional Commit prefix with a !,
e.g. feat!:, fix!:).
[x] No, this is not a breaking change.

Related Issues
Closes #1309

We are currently not following this recommendation (in particular, fromCache creates a shareable reference but doesn't invoke clone()). It's probably impractical for us to adhere to those rules, but we definitely MUST clarify the intended usage both in doc-comments and in the main documentation site.

Indeed, will add proper docs.


dead pixel modules

dead pixel modules are used to fill deadvectors.
The feature is enabled by default.

In the 2021 setup in 11_3_X (SiPixelQuality_phase1_Run3Beginning) there are 56 modules with bad ROCs, of these 18 are fully bad, which is still 73% of the bad ROCs.

compare this with around 1840 modules with hits ==> around 1% of modules is covered by this PR

in the 2024 setup (SiPixelQuality_phase1_Run3Endof4years) there are 92 modules with bad ROCs and the difference is in the fully bad modules (54). So, for this setup this PR will cover 89% of the bad ROCs.

Validation is available in http://uaf-10.t2.ucsd.edu/~slava77/figs/mic/mtv/ttbar50_mkFit-pr351-dead-pix-modules_m7944010_c9b3bccd  (made with mkfit=all option in our 11_2_X setup) and compares with the dev as of trackreco/mkFit#351
It's a bit hard to pick up a clear large difference in the validation plots in the 2021 setup
The following plots are from the pixelLess iteration:
in  built tracks around 1% more tracks have 0 missing hits

there is some small increase in the number of pixel hits

The impact on the highPurity is even better (3% more tracks with 0 missing)

The HP eff and fakes look OK

@mmasciov or @leonardogiannini please run on 2024 setup

MTV results after enabling 4 "default" mkFit iterations in CMSSW, for 113X samples with different failure scenarios are collected at:
http://uaf-10.t2.ucsd.edu/~mmasciov/MkFit_devs/pixelDBInformation/
--> No significant difference is found in out-of-the-box performance, as mkFit is only enabled for pixel-seeded iterations.

At the same link, MTV results after enabling only pixelLessStep for mkFit are available (names of sub-directories are self-explanatory).

Please add smth like IndexOptions NameWidth=80 in the .htaccess of this dir or even your public_html/ so that the names are more visible


Helm upgrade --install doesn't restart/recreate the pod if the image revision is the same

Output of helm version:
3.2.0
Output of kubectl version:
latest
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
GKE - Google Kubernetes Engine
ISSUE
Hey guys! I am coming today because I am facing a situation where I didn't find any workaround yet.. So here I come!
Context
I have a pod running in a GKE which got deployed throught HELM strategy (using Cloud Build).
deploy.yaml
steps:
- name: 'gcr.io/${_PROJECT_ID}/helm'
  args: ['dependency', 'update' , 'deployments/helm/${_PROJECT_NAME}']
  env:
  - 'CLOUDSDK_COMPUTE_ZONE=${_CLUSTER_ZONE}'
  - 'CLOUDSDK_CONTAINER_CLUSTER=${_CLUSTER_NAME}'
  - 'TILLERLESS=true'
  - 'TILLER_NAMESPACE=${_PROJECT_NAMESPACE}'
- name: 'gcr.io/${_PROJECT_ID}/helm'
  args: ['upgrade',
         '${_RELEASE_NAME}', 'deployments/helm/${_PROJECT_NAME}', '--install', '--force', '--reset-values',
         '--wait', '--timeout', '120s',
         '--namespace', '${_PROJECT_NAMESPACE}',
         '--values', 'deployments/helm/${_VALUES_ENV}.values.yaml',
         '--set-string', 'image.tag=${_IMAGE_VERSION}',
         '--set-string', 'key1="${_VALUE}_1"',
         '--set-string', 'key2="${_VALUE_2}"']
  env:
  - 'CLOUDSDK_COMPUTE_ZONE=${_CLUSTER_ZONE}'
  - 'CLOUDSDK_CONTAINER_CLUSTER=${_CLUSTER_NAME}'
  - 'TILLERLESS=true'
  - 'TILLER_NAMESPACE=${_PROJECT_NAMESPACE}'
  - 'HELM_TILLER_STORAGE=secret'
  - 'HELM_TILLER_HISTORY_MAX=10'

Everything works like a charm but the following situation.
Problem
I have a version master-123456a running. I am now deploying an update of my code which got as revision tag master-9802ale. It gets deployed like a charm and the pod is working as well after a clean restart.
Now, for some reason, someone just kills a service we are listening to!!  We so want to just restart the pod and so, we run the command above and.. NOTHING HAPPENS
If we do an edit on the code and commit the changes (then of course rebuild the image), it does get deployed.
helm upgrade --install (as stated in the doc) doesn't restart the pod (or redeploy) a version that already exists. So what would be the best approach for me?

Change the naming approach for each built images
Add a flag that goes against --install policy/logic

Because what I want is redeploy my built image without loosing time to rebuild it
Thanks for any feedback!

Most (if not all) workload types in Kubernetes allow you to specify an image pull policy. By changing that pull policy to "always", any time a pod is restarted, it will re-fetch the container image from the registry.
That way when you "just restart the pod", it will attempt to re-grab the image.
Hope that helps.

That being said most software applications are built with some form of versioning system in mind. With proper version control, you should be releasing a new version of the image each time a new release is available. In doing so, you ensure that an upgrade of your system will pick up the new image and you circumvent this issue altogether.
In other words, I would suggest adopting some form of versioning system for your container images.

I don't think this is an image-pull-policy problem.
If I understand the request, the desire is to restart the pod, because logic in the pod is failing to retry to another service which went down, so you just want to kill it. The helm upgrade command is just trying to trigger that by redeploying an unchanged chart.
In this case, @Emixam23-FCMS, I think you don't need to helm install. You just want to trigger the Pods in the Deployment to restart, so use
kubectl rollout restart deployment <deploymentname>

for whatever the Deployment's name is that contains the Pods you want to restart. See the kubectl reference and a similar answer on Stack Overflow for more details.
If it's just one Pod you want to restart, you can just kubectl delete pod <podname>, and the Deployment will recreate it.

Have you checked your UpdateStrategy in Values.yaml?. If it is set as OnDelete then change it to RollingUpdate and if not then please use as suggested by @TBBle

I'm still confused about this discussion, isn't helm upgrade --install command supposed to start a rolling update? Do I need to call kubectl rollout restart deployment everytime I upgrade?
In my case I have a pipeline that builds the "latest" image and then I call the helm command to start using the updated version in production.

helm upgrade --install updates the deployed resources to match the chart. (Since it's a 3-way merge, it's slightly more complicated, but this is accurate enough for our purposes here).
If the resulting resources are different, then kubernetes naturally does a rolling upgrade, the same as for any other system that modifies a Deployment or similar, including manually editing with kubectl edit. Helm doesn't do any of the actual rolling upgrades etc, that's all up to kubernetes. As noted in https://github.com/helm/helm/issues/9041#issuecomment-1146019668, it's possible to disable this in some cases, e.g. UpdateStrategy, but that's still a kubernetes thing, not Helm-specific.
If the resources are unchanged (as is the case here, because it's doing an "upgrade" to the version that's already deployed) kubernetes doesn't see any difference and doesn't roll anything, by design of kubernetes (as a state-reconciliation system).
So if you use helm upgrade --install to actually change the resources (new chart version, changed values, etc), then a rolling update will happen as you'd expect.
If you are trying to use helm upgrade --install to just restart some pods (as the original poster was), it probably won't work with a bunch of noisy messing about; that's what kubectl rollout restart deployment is for.


fix bug of testing with -OsVHD

Previously, when Runn-LISAv2 with '-OsVHD' and leave '-TestLocation' empty (which means LISA will select a TestLocation automatically), test will failed, and the VHD may have been copied to some unexpected storage account. The previous workaround is have some '-TestLocation' provided to Run-LISAv2
Here's the PR to fix the problem, so Run-LISAv2 can have full compatible with backward (using '-OsVHD') and align with design '-TestLocation' can be empty and optional.
===================Test Logs=====================
08/05/2020 03:31:30 : [INFO ] Cleanup test environment if required ...
08/05/2020 03:31:31 : [INFO ] Test ED71 finished
08/05/2020 03:31:31 : [INFO ]
[LISAv2 Test Results Summary]
Test Run On : 08/05/2020 02:23:03
VHD Under Test : http://lisasoutheastasia.blob.core.windows.net/vhds/lisCent-validation-185-role-0-ptzdrivwue-osdisk.vhd
Total Test Cases : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:1:8
ID TestArea TestCaseName TestResult TestDuration(in minutes)
1 CORE                 VERIFY-DEPLOYMENT-PROVISION                                                       PASS                 1.91
OsVHD: http://lisawestus2.blob.core.windows.net/vhds/lisCent-validation-185-role-0-ptzdrivwue-osdisk.vhd, TestLocation: westus2, VMGeneration: 1, Kernel Version: 2.6.32-642.15.1.el6.x86_64
FirstBoot : PASS
FirstBoot : Call Trace Verification : PASS
Reboot : PASS
Reboot : Call Trace Verification : PASS
Logs can be found at C:\LISAv2\ED71\TestResults\2020-08-05-02-22-25-0937
08/05/2020 03:31:31 : [DEBUG] Creating 'C:\LISAv2\ED71\Azure-ED71-TestLogs.zip' from 'C:\LISAv2\ED71\TestResults\2020-08-05-02-22-25-0937'
08/05/2020 03:31:31 : [DEBUG] C:\LISAv2\ED71\Azure-ED71-TestLogs.zip created successfully.
08/05/2020 03:31:31 : [INFO ] Analyzing test results ...
08/05/2020 03:31:31 : [INFO ] LISAv2 exit code: 0
======================Another TestLog==============================
08/05/2020 06:57:22 : [INFO ] VHD 'lisCent-validation-185-role-0-ptzdrivwue-osdisk.vhd' had ever been copied to 'lisawestus2', skip copying again
...
[LISAv2 Test Results Summary]
Test Run On : 08/05/2020 06:47:06
VHD Under Test : http://lisasoutheastasia.blob.core.windows.net/vhds/lisCent-validation-185-role-0-ptzdrivwue-osdisk.vhd
Total Test Cases : 2 (2 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:16
ID TestArea TestCaseName TestResult TestDuration(in minutes)
1 CORE                 CPU-VERIFY-ONLINE                                                                 PASS                  0.3
OsVHD: http://lisawestus2.blob.core.windows.net/vhds/lisCent-validation-185-role-0-ptzdrivwue-osdisk.vhd, OverrideVMSize: Standard_DS3_v2, TestLocation: westus2, VMGeneration: 1, Kernel Version: 2.6.32-642.15.1.el6.x86_64
2 CORE                 VERIFY-DEPLOYMENT-PROVISION                                                       PASS                 1.94
OsVHD: http://lisawestus2.blob.core.windows.net/vhds/lisCent-validation-185-role-0-ptzdrivwue-osdisk.vhd, TestLocation: westus2, VMGeneration: 1, Kernel Version: 2.6.32-642.15.1.el6.x86_64
FirstBoot : PASS
FirstBoot : Call Trace Verification : PASS
Reboot : PASS
Reboot : Call Trace Verification : PASS
Logs can be found at C:\LISAv2\DC97\TestResults\2020-08-05-06-46-28-9931
08/05/2020 07:04:02 : [DEBUG] Creating 'C:\LISAv2\DC97\Azure-DC97-TestLogs.zip' from 'C:\LISAv2\DC97\TestResults\2020-08-05-06-46-28-9931'
08/05/2020 07:04:02 : [DEBUG] C:\LISAv2\DC97\Azure-DC97-TestLogs.zip created successfully.
08/05/2020 07:04:02 : [INFO ] Analyzing test results ...
08/05/2020 07:04:02 : [INFO ] LISAv2 exit code: 0
===================Another Log with expected Exception====================
08/08/2020 07:33:51 : [INFO ] (2/2) testing started: TVM-TEST-SECUREBOOT-COMPATIBILITY
08/08/2020 07:33:51 : [INFO ] SetupConfig: { ARMImageName: Canonical 0003-com-ubuntu-server-trusted-vm 18_04-gen2 latest, OverrideVMSize: Standard_D2s_v3, TestLocation: eastus2euap, VMGeneration: 2 }
08/08/2020 07:33:51 : [INFO ] Deploy target machine for test if required ...
08/08/2020 07:33:51 : [INFO ] Current test setup: OneVM
08/08/2020 07:33:51 : [INFO ] Checking the subscription usage...
08/08/2020 07:33:51 : [INFO ] Estimating VM #1 usage.
08/08/2020 07:33:51 : [ERROR] Exception detected. Source : DeployVMs()
08/08/2020 07:33:51 : [ERROR] EXCEPTION : VM size 'Standard_D2s_v3' is not enabled in 'eastus2euap' for the current subscription, or LISA has not found available StorageAccount for this TestLocation 'eastus2euap', please check  from XMLSecretFile or  from C:\LISAv2\Libraries..\XML\RegionAndStorageAccounts.xml
08/08/2020 07:33:51 : [ERROR] Source : Line 169 in script .\Libraries\Azure.psm1.
08/08/2020 07:33:51 : [WARN ] VMData is empty (null). Aborting the testing.
08/08/2020 07:33:51 : [INFO ] End of testing: TVM-TEST-SECUREBOOT-COMPATIBILITY with SetupConfig: { ARMImageName: Canonical 0003-com-ubuntu-server-trusted-vm 18_04-gen2 latest, OverrideVMSize: Standard_D2s_v3, TestLocation: eastus2euap, VMGeneration: 2 }, result: Aborted
08/08/2020 07:33:51 : [INFO ] PASS    - 1
08/08/2020 07:33:51 : [INFO ] SKIPPED - 0
08/08/2020 07:33:51 : [INFO ] FAIL    - 0
08/08/2020 07:33:51 : [INFO ] ABORTED - 1
08/08/2020 07:33:51 : [INFO ] PENDING - 0
08/08/2020 07:33:51 : [INFO ] Cleanup test environment if required ...
08/08/2020 07:33:52 : [INFO ] Test DQ56 finished
08/08/2020 07:33:52 : [INFO ]
[LISAv2 Test Results Summary]
Test Run On           : 08/08/2020 07:31:32
ARM Image Under Test  : Canonical : 0003-com-ubuntu-server-trusted-vm : 18_04-gen2 : latest
Total Test Cases      : 2 (1 Passed, 0 Failed, 1 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:2
ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
1 WALA                 WALA-VERIFY-WAAGENT-LOG                                                           PASS                 0.35
  ARMImageName: Canonical 0003-com-ubuntu-server-trusted-vm 18_04-gen2 latest, TestLocation: westus2, Initial Kernel Version: 5.3.0-1034-azure
2 TVM                  TVM-TEST-SECUREBOOT-COMPATIBILITY                                              Aborted                    0
  ARMImageName: Canonical 0003-com-ubuntu-server-trusted-vm 18_04-gen2 latest, OverrideVMSize: Standard_D2s_v3, TestLocation: eastus2euap, VMGeneration: 2, Initial Kernel Version: 5.3.0-1034-azure
  VM size 'Standard_D2s_v3' is not enabled in 'eastus2euap' for the current subscription, or LISA has not found available StorageAccount for this TestLocation 'ea..

Logs can be found at C:\LISAv2\TestResults\2020-08-08-00-30-41-7060
08/08/2020 07:33:52 : [DEBUG] Creating 'C:\LISAv2\Azure-DQ56-TestLogs.zip' from 'C:\LISAv2\TestResults\2020-08-08-00-30-41-7060'
08/08/2020 07:33:52 : [DEBUG] C:\LISAv2\Azure-DQ56-TestLogs.zip created successfully.
08/08/2020 07:33:52 : [INFO ] Analyzing test results ...
08/08/2020 07:33:52 : [INFO ] LISAv2 exit code: 1

@juhlee-microsoft Please take a look, all the comments resolved/updated. this is needed for partner engineers to test with custom -OsVHD.


UI Accessibility work

Bug 402111: Accessibility: MAS42A : High Contrast: Environment selection from combo box is not in compliance with HC themes
Bug 402112: Accessibility: MAS42A : High Contrast: Select Environment combo box when focused using keyboard doesn't get a highlight
Bug 402121: Accessibility: MAS42A : High Contrast: Text selection in Workspaces pane > Text boxes in not in compliance with HC themes
Bug 402675: Accessibility: MAS42A: High Contrast: Load package radio buttons when focused using keyboard are hardly identifiable in HC themes
Bug 402676: Accessibility: MAS42A: High Contrast: Uninstall package buttons when focused using keyboard are hardly identifiable in HC themes
Bug 402678: Accessibility: MAS42A: High Contrast: Vertical separator/Grid Splitter when focused using keyboard is not identifiable in HC black
Bug 403509: Accessibility: MAS42A: High Contrast: 'Dismiss' and 'Dismiss All' buttons in error pop-up bar are not in compliance with HC themes
Bug 403504: Accessibility: MAS42A: High Contrast: Workspaces > Local Connection Settings > Cancel button is not in compliance with HC themes

Added 2 more

403509 and 403504 - we can just make them into buttons and be done.

403509 will be fixed as a result of #3458


go/store/datas: commit.go: Start storing commit parents as a List instead of a Set.

Commit parent order has meaning in our use case. The branch that gets merged
into is always the first commit in the parents list. Up until this change, the
noms layer stores commit parents as a Set, which is unordered and orders the
parents based on their commit hash.
This changes commit struct to carry both parents Set and parentsList List.
CommitOptions supplies a ParentsList, but both get stored for backwards
compatibility with existing dolt clients.
This change does not include changes to start using the stored parentsList in
things like ancestor traversal or dolt log. The intended migration is that
the read logic will read from parentsList in a commit if it is present, and
will fall back to the parents Set if it is not.
Eventually we will be able to migrate to not writing parents Set anymore.
There is no current plan to drop support for reading parents Set when
parentsList is not available.

@bheni Somewhat of a request for comment here. Not sure I love how this turns out, but something like this seems like the best direction.


James Longdev

Please reference the Slurm Charms Change Summary Document for an in-depth explanation of these changes.
Changes include:

remove jinja2 and replace with Path().write_text()
remove slurm-ops-manager 3rd party dep and replace with local slurmrestd_ops.py
consolidate the yaml files into a single charmcraft.yaml
rename interface slurmrestd -> slurmctld

Hey @jamesbeedy :wave:
Similar to the slurmd operator, could you please apply the changes you made to the slurmdbd and slurmctld operators here as well before merging? We can focus on feature refinement in follow-on pull requests :smile:

@NucciTheBoss g2g on my end


Forward+ render projects not opening in AMD laptop

Tested versions
Godot 4.2.1 stable
System information
Godot v4.2.1.stable - Pop!_OS 22.04 LTS - X11  - RENOIR (radeonsi, renoir, LLVM 15.0.7, DRM 3.54, 6.6.10-76060610-generic) () - AMD Ryzen 9 5900HS with Radeon Graphics (16 Threads)
Issue description
When I create a new project with Forward+ renderer or change the renderer of a project from Compatibility to Forward+ I get this blank screen and the engine freezes whenever I try to open the project.

Steps to reproduce
1-Create a new project in an AMD Ryzen laptop
2-Choose a Forward+ renderer
3-Open the project
Minimal reproduction project (MRP)
Just an empty project since it doesn't open.

Unable to reproduce in Windows, must be something with how your OS is setup.
I have a Thinkpad T14s AMD that also only has an iGPU.
Godot v4.2.1.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - integrated AMD Radeon(TM) Graphics (Advanced Micro Devices, Inc.; 31.0.23013.1023) - AMD Ryzen 7 PRO 6850U with Radeon Graphics (16 Threads)

Can you reproduce this when creating a project with the Mobile rendering method?

I have this same issue on Windows 10 Pro, using an Alienware Alpha (GeForce GTX 860m) with 16GB of RAM. Switching to Mobile fixes it. Can't start Godot (either from Steam or from an individual build) without a command line or project setting set to change the renderer.

Can you reproduce this when creating a project with the Mobile rendering method?

I tried to create a new project. Same problem with Mobile renderer.

Can't start Godot (either from Steam or from an individual build) without a command line or project setting set to change the renderer.

The project manager always uses the Compatibility rendering method, unless you use --rendering-driver vulkan to force it to use Vulkan (in which case it'll use Forward+ unless --rendering-method mobile is specified).

I'm pretty sure that's backwards. I have to add the option for
compatibility mode to the Steam launch options or Godot 4.2 crashes on
launch in Windows.
On Fri, Feb 9, 2024, 3:11 AM Hugo Locurcio @.***> wrote:

Can't start Godot (either from Steam or from an individual build) without
a command line or project setting set to change the renderer.
The project manager always uses the Compatibility rendering method, unless
you use --rendering-driver vulkan to force it to use Vulkan (in which
case it'll use Forward+ unless --rendering-method mobile is specified).
—
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/87909#issuecomment-1935731037,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKRQ34NMVDT5PBWOUISECDYSX75NAVCNFSM6AAAAABCYGBV2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVG4ZTCMBTG4
.
You are receiving this because you commented.Message ID:
@.***>

I attempted something different today. I downloaded the TPS template from here. I opened the project and it worked even though it's a Forward+ renderer so that means the problem is only when starting a new project or changing the renderer of an existing project.

@ahmed-mo2nis Can you run Godot from the command line with the --verbose option and then let us know what GPUs are detected by the engine. From your original post, it looks like the engine isn't running on your GPU, which may be the source of your issue.
The full command is:
./Godot_v4.2.1-stable_linux.x86_64 --verbose

It will print out a lot of information. After you open the TPS demo, if you scroll up you should find a section that looks like:
Vulkan devices:
  #0: Intel Intel(R) Xe Graphics (TGL GT2) - Supported, Integrated
Vulkan API 1.3.267 - Forward Mobile - Using Vulkan Device #0: Intel - Intel(R) Xe Graphics (TGL GT2)

(This is how it appears for me with a project using the Mobile renderer)

@ahmed-mo2nis Can you run Godot from the command line with the --verbose option and then let us know what GPUs are detected by the engine. From your original post, it looks like the engine isn't running on your GPU, which may be the source of your issue.
The full command is:
./Godot_v4.2.1-stable_linux.x86_64 --verbose

It will print out a lot of information. After you open the TPS demo, if you scroll up you should find a section that looks like:
Vulkan devices:
  #0: Intel Intel(R) Xe Graphics (TGL GT2) - Supported, Integrated
Vulkan API 1.3.267 - Forward Mobile - Using Vulkan Device #0: Intel - Intel(R) Xe Graphics (TGL GT2)

(This is how it appears for me with a project using the Mobile renderer)
Could you also try doing the same thing, but opening a project that fails to load?

I tried creating a new project after opening Godot in the command line. The same problem is still here. Here is the message I received in the terminal :
Vulkan devices:
#0: AMD AMD Radeon Graphics (RADV RENOIR) - Supported, Integrated
#1: NVIDIA NVIDIA GeForce RTX 3060 Laptop GPU - Supported, Discrete
#2: Unknown llvmpipe (LLVM 15.0.7, 256 bits) - Supported, CPU
Vulkan API 1.3.260 - Forward+ - Using Vulkan Device #1: NVIDIA - NVIDIA GeForce RTX 3060 Laptop GPU
Optional extension VK_KHR_incremental_present not found
Optional extension VK_GOOGLE_display_timing not found

Vulkan Variable Rate Shading supported:
Pipeline fragment shading rate
Primitive fragment shading rate
Attachment fragment shading rate, min texel size: (16, 16), max texel size: (16, 16)
Vulkan multiview supported:
max view count: 32
max instances: 134217727
Vulkan subgroup:
size: 32
min size: 32
max size: 32
stages: STAGE_VERTEX, STAGE_TESSELLATION_CONTROL, STAGE_TESSELLATION_EVALUATION, STAGE_GEOMETRY, STAGE_FRAGMENT, STAGE_COMPUTE, STAGE_RAYGEN_KHR, STAGE_ANY_HIT_KHR, STAGE_CLOSEST_HIT_KHR, STAGE_MISS_KHR, STAGE_INTERSECTION_KHR, STAGE_CALLABLE_KHR, STAGE_TASK_NV, STAGE_MESH_NV
supported ops: FEATURE_BASIC, FEATURE_VOTE, FEATURE_ARITHMETIC, FEATURE_BALLOT, FEATURE_SHUFFLE, FEATURE_SHUFFLE_RELATIVE, FEATURE_CLUSTERED, FEATURE_QUAD, FEATURE_PARTITIONED_NV

There's nothing obvious from that information.
Can you test 4.3 dev 4 (https://godotengine.org/article/dev-snapshot-godot-4-3-dev-4/) and see if it works for you? We have done a few important fixes to problems that are similar to what you describe.

There's nothing obvious from that information.
Can you test 4.3 dev 4 (https://godotengine.org/article/dev-snapshot-godot-4-3-dev-4/) and see if it works for you? We have done a few important fixes to problems that are similar to what you describe.

I tried it to create a new project and everything seems to be working :) I created a new project with the Forward+ Renderer and changed it to Mobile to see if anything will crash or freeze. No problems so far. I created a simple scene as shown in these screenshots to fully test it. Thanks for fixing the issue :)

Amazing! Thank you for confirming that dev4 works for you. I will close this issue as resolved in 4.3.
For future reference I think https://github.com/godotengine/godot/pull/87340 is responsible for fixing this issue, but I am not 100% certain.


PR

Adding power support ppc64le
This is part of the Ubuntu distribution for ppc64le. This helps us simplify testing later when distributions are re-building and re-releasing. For more info tag @gerrith3.
The Python Versions=pypy are not available for download and hence excluded from the travis.yml & the build is enabled for other versions of python.
Build is enabled for both arch: ppc64le/amd64.

Can this PR be accepted?

If all the tests are successful, Can you please consider this PR to process further?

@audreyfeldroy If all the checks are successful, Can we have this PR processed further? It's been open from quite a few days now.

@audreyfeldroy If all the tests are successful, Can we have this PR processed further?

Can you please check this PR & approve?

In case there are no further checks to be verified, Can we have this PR approved? It is open from quite sometime now.

Can you Please check & approve? It's been open from very long time.,

@audreyfeldroy Herewith Checking if you have any further questions on this.
Thank you!!

A gentle nudge, Checking if you have any questions on this PR!!

A gentle reminder to Let us know if you have any further queries on this PR?

Checking herewith if there are any further queries here?

@audreyfeldroy Are there any queries open on this PR?

@santosh653 We are rebooting the project and we are no longer using Travis since they changed their support for FOSS projects. So I can only close this. It would be awesome to get this to run on GitHub actions though. Thank you in all cases.


Unable to run inference on free tier Colab.

I tried running this quick start code on free tier Colab.
import mii
pipe = mii.pipeline("mistralai/Mistral-7B-v0.1")
response = pipe(["DeepSpeed is", "Seattle is"], max_new_tokens=128)
print(response)
Got this error
RuntimeError: Unable to load ragged_device_ops op due to no compute capabilities remaining after filtering

Hi @sudhir2016 What GPU are you trying to run on? I suspect it does not have compute capability >=8.0

I was using T4 which is only 7.5 !

Unfortunately, we are unable to support GPUs without >= 8.0 CUDA compute capability for the latest DeepSpeed-MII. However, we still support these older architectures within MII Legacy.

Ok thanks.


Request feature to download a single lecture from the course

Hi swargaraj,
Request feature to download a specific lecture from the course
waiting for your commit/s or new branch
regards

Hey There! This feature will be added in the next release.

Thanks so much for your patience! I'm letting you know that this feature will be included in the next pull request. I appreciate your interest in improving the project!


intermittent connectivity issues w/ Sandbox

Guidelines

Neo4j version: Sandbox Recommendations - 3.5.117, Enterprise

Neo4j Mode:  Sandbox Recommendations

Driver version: 4.0.0

Operating system: Mac OS Catalina

Steps to reproduce

Expected behavior

Connect to the Recommendations (movies, genres, actors etc) sandbox using the driver
make about 5 queries for movies and movies by genre (loading a page with movies by genre)
receive results

Actual behavior

Connect to the Recommendations (movies, genres, actors etc) sandbox using the driver
make about 5 queries for movies and genres
receive some results, other times receive

neo4j.exceptions.ServiceUnavailable: Failed to read from defunct connection IPv4Address(('<IP_ADDRESS>', 34260)) (IPv4Address(('<IP_ADDRESS>', 34260)))

@whatSocks Hi could you please add a code snippet.
It is normal in network applications that a connection could die and then you have to catch the error and do another query.
Please read this article. https://medium.com/neo4j/try-and-then-retry-there-can-be-failure-30bf336383da


nuclei: 2.6.1 -> 2.6.2

Motivation for this change
https://github.com/projectdiscovery/nuclei/releases/tag/v2.6.2
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

nuclei


[Bug]: Cannot parse Date when deserializing com.github.dockerjava.api.model.Network object

Module
Core
Testcontainers version
1.20.3
Using the latest Testcontainers version?
Yes
Host OS
Ubuntu 20.04
Host Arch
x86_64
Docker version
Client:
 Version:           24.0.7
 API version:       1.43
 Go version:        go1.21.1
 Git commit:        24.0.7-0ubuntu2~20.04.1
 Built:             Wed Mar 13 20:29:24 2024
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          24.0.7
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.21.1
  Git commit:       24.0.7-0ubuntu2~20.04.1
  Built:            Wed Mar 13 20:29:24 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.12
  GitCommit:
 runc:
  Version:          1.1.12-0ubuntu2~20.04.1
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:

What happened?
We have some integration tests written in Junit5 brining up a GenericContainer for end-to-end tests between components. When the tests are run in a host process the GenericContainer object is created successfully, but when tests are run within a container (like in Jenkins) the GenericContainer fails to build, throwing the exception reported in the log pane.
Debugging the code, it seems the GenericContainer fails to deserialize dates in com.github.dockerjava.api.model.Network object when inspecting the docker network. The date format returned with docker network inspect is indeed "2024-11-13T21:04:48.309416219+0100", but apparently the BaseSettings initialized in ObjectMapper uses a StdDateFormat that is not able to parse it.
Reverting the dependency to testcontainers 1.17.6 made it work. I think this could be a regression.
Relevant log output
java.lang.RuntimeException: org.testcontainers.shaded.com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not deserialize value of type java.util.Date from String "2024-11-13T21:04:48.309416219+01:00": not a valid representation (error: Failed to parse Date value '2024-11-13T21:04:48.309416219+01:00': Can not parse date "2024-11-13T21:04:48.309416219+0100": while it seems to fit format 'yyyy-MM-dd'T'HH:mm:ss.SSSZ', parsing fails (leniency? null))

 at [Source: N/A; line: -1, column: -1] (through reference chain: com.github.dockerjava.api.model.Network["Created"])
	at org.testcontainers.shaded.com.github.dockerjava.core.DefaultInvocationBuilder.get(DefaultInvocationBuilder.java:77) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.shaded.com.github.dockerjava.core.exec.InspectNetworkCmdExec.execute(InspectNetworkCmdExec.java:26) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.shaded.com.github.dockerjava.core.exec.InspectNetworkCmdExec.execute(InspectNetworkCmdExec.java:12) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.shaded.com.github.dockerjava.core.exec.AbstrSyncDockerCmdExec.exec(AbstrSyncDockerCmdExec.java:21) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.shaded.com.github.dockerjava.core.command.AbstrDockerCmd.exec(AbstrDockerCmd.java:33) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.shaded.com.github.dockerjava.core.command.InpectNetworkCmdImpl.exec(InpectNetworkCmdImpl.java:7) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.dockerclient.DockerClientProviderStrategy.resolveDockerHostIpAddress(DockerClientProviderStrategy.java:453) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.dockerclient.DockerClientProviderStrategy.getDockerHostIpAddress(DockerClientProviderStrategy.java:424) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.DockerClientFactory.dockerHostIpAddress(DockerClientFactory.java:344) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.ContainerState.getHost(ContainerState.java:64) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.wait.strategy.HostPortWaitStrategy.waitUntilReady(HostPortWaitStrategy.java:112) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:901) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:492) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:346) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81) ~[duct-tape-1.0.8.jar:?]
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:336) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:322) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.PortForwardingContainer.createSSHSession(PortForwardingContainer.java:43) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.PortForwardingContainer.getSshConnection(PortForwardingContainer.java:38) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.PortForwardingContainer.exposeHostPort(PortForwardingContainer.java:69) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.containers.PortForwardingContainer.exposeHostPort(PortForwardingContainer.java:63) ~[testcontainers-1.20.3.jar:1.20.3]
	at org.testcontainers.Testcontainers.exposeHostPorts(Testcontainers.java:14) ~[testcontainers-1.20.3.jar:1.20.3]

Additional Information
No response

This issue has been fixed in jackson-databind 2.9.1 FasterXML/jackson-databind#1745 https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.1

Do you mean the Jackson library shaded in testcontainers embeds a prior version with that bug?
In our maven dependencyManagement we link to Jackson 2.17.0. But I don't think it gets picked up by testcontainers, otherwise the entire shaded logic would not work as intended

Yes, testcontainers includes an outdated version of the Jackson library.
Please see https://github.com/testcontainers/testcontainers-java/blob/f7267c7639d2e87c600f40fbb68e72f6268d3e0c/core/build.gradle#L66
Thus, Testcontainers should provide a fix.

In the meantime, you can update the dependency by yourself. I have done that in another project and list network wit no issues. Jackson version has not been updated to keep compatibility with other projects using older versions, see https://github.com/testcontainers/testcontainers-java/issues/3433.

In the meantime, you can update the dependency by yourself. I have done that in another project and list network wit no issues. Jackson version has not been updated to keep compatibility with other projects using older versions, see #3433.

@eddumelendez
How would I override the shaded jackson-databind to 2.9.1?

shaded dependencies can not be overridden. jackson dependencies are shaded and transitives dependencies in testcontainers. So, what I meant is just updating the transitives dependencies.


when will get react-native version？

trying to integrate on mobile

This sounds very unlikely, as far as I know Highcharts is focused on DOM.
You would probably get a better answer if you ask the same question in the actual highcharts repo.  Also there is a variety of native alternatives out there.

Feel free to reopen

https://github.com/TradingPal/react-native-highcharts


Architecture Discussion

Here's a link to a draw.io architecture diagram (can open in draw.io and make changes I believe)
https://drive.google.com/file/d/1U54sHhv3xVk7-CZ5dnR1l-UjgkhmGyRO/view?usp=sharing
I'm happy to recreate it in a more collab-friendly software if anyone has suggestions.

Architecture looks good so far,
I do have some concerns about the flow:

Handle bloom user account: Thoughts on Public/private attestation. Also, I believe reputations should be more than just number of attestaion (Maybe future versions will handle this), except if all attestations are public and the accounts making the attestations are public as well.
IPFS verification: we need to confirm that the content on Ipfs is same as that provided to contract: (IPFS hash)

I think we should make sure that it's do-able within the hackathon parameters (i.e. this looks like a pretty long roadmap). Probably might need to oversimplify a lot of things
I think a non-trivial aspect of it is actually the business use case - @wimanesti and I are spending quite a bit of extra time making sure that this is legally above board, and speaking w/ her and her family about the responsibilities of the loan

@onggunhao Yeah, the simplest possible version is the target.I think we have about 5 days left


Include sstream for std::stringstream

Build with clang version 14.0.5:
src/McBopomofo.cpp:161:23: error: implicit instantiation of undefined template 'std::basic_stringstream<char>'
    std::stringstream sst;
                      ^
/usr/include/c++/v1/iosfwd:145:32: note: template is declared here
    class _LIBCPP_TEMPLATE_VIS basic_stringstream;
                               ^
src/McBopomofo.cpp:179:23: error: implicit instantiation of undefined template 'std::basic_stringstream<char>'
    std::stringstream sst;
                      ^
/usr/include/c++/v1/iosfwd:145:32: note: template is declared here
    class _LIBCPP_TEMPLATE_VIS basic_stringstream;
                               ^
2 errors generated.

Thanks!


Initial proposal for #173: Adding context to existing CS/CF instances

Well spotted, I've corrected them, let me know if that's fine.

@FroMage CI complains about unused import:
04:16:15 [ERROR] /home/jenkins/agent/workspace/microprofile-concurrency-prs/api/src/main/java/org/eclipse/microprofile/context/ManagedExecutor.java:28:8: Unused import - org.eclipse.microprofile.context.spi.ContextManager. [UnusedImports]

But it's used by javadoc, that's wrong…

Upgraded checkstyle to a version which understands javadoc wrt. unused imports.

Except now I don't get why CI won't run the build :-/

Ah, CI passed now. Shall I merge this then, or should I add TCK tests first?

Ah, CI passed now. Shall I merge this then, or should I add TCK tests first?

Adding TCK tests in a separate pull is fine if you want to merge this first


Reorder arguments if block given and no encoding needed

If one tries to use the vanilla mail_to through the gem, the arguments will get messed up if used with a block. This is due to line 48 which is executed in the gem as well as in the super, messing up the order of arguments.
We effectively need to reverse line 48 if we want to call the super, otherwise the html_options will not be passed to the super.

I just hit this as well and can confirm the fix resolves the issue for me.


Cleanup route guide client and server code

Client code:
-- Need to make the namespace idiomatic
-- Various RouteGuideUtil methods could be extension methods (good example of "extending" protobuf messages; or just use partial classes - the latter would allow LatitudeDegrees or whatever as a property…)
--When catching an exception in the client, use "throw;" rather than "throw e;" to avoid losing context
-- In ListFeatures, extract call.ResponseStream as a local variable?
-- Would disposing of call.ResponseStream (which we don't at the moment) dispose of call? If so, we don't need call at all…
-- Same question with call.RequestStream for RecordRoute, although we use call.Result there...
-- Consider renaming ForEach to ForEachAsync
-- Using string interpolation, we don't need Log(string, object[]) at all
Server:
-- get rid of non-ascii variable names
-- CalcDistance could be an extension method (or method in a partial class) on Point
-- I'd use LINQ for CheckFeature, and ideally Point equality
-- Rectangle.Contains(Point) would be a useful extension method :)
-- The RouteChat locking etc feels a little clunky. Would ConcurrentBag help?

#3207


Icon binding with MVVM not working

Icon is not displayed when a binding is applied with MVVM.
ViewModel example :
private FontAwesomeSolidIcons _myIcon;
public FontAwesomeSolidIcons MyIcon
{
            get => _myIcon;
            set
            {
                _myIcon = value;
                RaisePropertyChanged(() => MyIcon);
            }
}

public async Task PageAppearingAsync()
{
             MyIcon = FontAwesomeSolidIcons.AddressBook;
}

Related view component (Button)
<Button
    Command="{Binding SearchAddressCommand}"
    Text="{mi:FontAwesomeSolid BindingContext={x:Reference HomeViewPage}, Icon={Binding MyIcon}, IconColor={DynamicResource
   PrimaryColor}, IconSize=25}" />

Yes I will try to provide it soon.
In my current project I'm using MVVM Helpers library but I will provide an example without it.
Nevertheless, it would be interesting to provide a simple sample with MVVM bindings

We have made a some improvements to overall binding support with v4 and that makes this no longer issue at all.
Additionally, we are final stage of the release. Stay tuned for v4


Adding module support for Commonjs, AMD or Browser

Please take note that no change have been made to your code and your tests will pass just as before. But now this module can be used with either Commonjs module pattern or AMD.
The code added is based on this SO question :
http://stackoverflow.com/questions/13673346/supporting-both-commonjs-and-amd

Please create an issue first before taking the effort to do this. I'm almost 100% sure this won't get merged, but I let @sindresorhus make the call.
You can always use webpack or browserify if you want to use this in your browser.

I understand my mistake.
For people using TypeScript in Visual Studio and not wanting a dependency on webpack or browserify this does the trick, and I assume (I can be terribly wrong ) it wont brake for people using browserify either.
I will create an issue tomorow. Thank you.

For people using TypeScript in Visual Studio and not wanting a dependency on webpack or browserify this does the trick

I'm afraid this is something that should be resolved by the user of the module, not by the module itself. It adds extra overhead and it made the code much worse in terms of readability and thus maintainability.

I will create an issue tomorow.

No need to, now it can be discusses in the PR :)

Originally, we supported AMD but removed support in https://github.com/sindresorhus/object-assign/commit/6e57ecf8e9c27b1de90c03e718879a372d9360ad.

No thanks.
Here's a standalone version you can run directly in the browser: https://wzrd.in/standalone/object-assign

Ok guys.
My interest here was to have a module that can be used with AMD(requirejs).
Maybe you are right and an extra dependency on browserify is better that the overhead and poor readability introduced by this change.
Thanks.


"true SSLContext not available" / NoSuchAlgorithmException in Logstash 2.3.2

When using RabbitMQ input with ssl => true in Logstash 2.3.2 against RabbitMQ 3.6.1 , connection fails with "true SSLContext not available" / Java::JavaSecurity::NoSuchAlgorithmException.
Connecting to RabbitMQ. Settings: {:vhost=>"/", :host=>"max", :port=>5671, :user=>"user", :automatic_recovery=>true, :pass=>"pass", :timeout=>0, :heartbeat=>0, :tls=>"true", :tls_certificate_path=>"", :tls_certificate_password=>""} {:level=>:debug, :file=>"logstash/plugin_mixins/rabbitmq_connection.rb", :line=>"147", :method=>"connect"}
Using TLS/SSL version true
true SSLContext not available {:class=>"Java::JavaSecurity::NoSuchAlgorithmException", :location=>"sun.security.jca.GetInstance.getInstance(sun/security/jca/GetInstance.java:159)", :level=>:warn, :file=>"logstash/inputs/rabbitmq.rb", :line=>"180", :method=>"register"}

Strangely, this doesn't happen in Logstash 2.3.1 even though the plugin version is the same.
├ $ logstash-2.3.2/bin/plugin list --verbose | grep rabbit
logstash-input-rabbitmq (4.0.1)
logstash-output-rabbitmq (3.0.9)

├ $ logstash-2.3.1/bin/plugin list --verbose | grep rabbit
logstash-input-rabbitmq (4.0.1)
logstash-output-rabbitmq (3.0.9)

@andrewvc
Steps to test:
# docker pull rabbitmq
# docker run -d --hostname my-rabbit --name some-rabbit -p 15672:15672 -p 5671:5671 -v /opt/etc-rabbitmq:/etc/rabbitmq  rabbitmq:3-managementrabbitmq:/etc/rabbitmq  rabbitmq:3

where /opt/etc-rabbitmq contains: rabbitmq.config:
[
  {rabbit, [
     {ssl_listeners, [5671]},
     {ssl_options, [{cacertfile,"/etc/rabbitmq/cacert.pem"},
                    {certfile,"/etc/rabbitmq/servercert.pem"},
                    {keyfile,"/etc/rabbitmq/serverkey.pem"},
                    {verify,verify_peer},
                    {fail_if_no_peer_cert,false}]}
   ]}
].

and also the given cert files (you're on your own)
Next, mozey into the admin interface http://localhost:15672/ and:

Add the user called index with password index, set permission to the / virtualhost.
Add the queue called logstash.queue

Configure logstash to test:
# Pull from rabbitmq queues
input {
        rabbitmq {
                host => "max"
                user => "index"
                ssl => true
                port => 5671
                password => "index"
                queue => "logstash.queue"
                key => "logstash.queue"
                durable => true
                threads => 1
                prefetch_count => 1000
        }
}
output {
 stdout {
        codec => rubydebug
 }
}

@PhaedrusTheGreek this will be fixed in https://github.com/logstash-plugins/logstash-mixin-rabbitmq_connection/pull/22

@andrewvc this bit me earlier today....running logstash 2.3.1 with the following versions installed
*logstash-input-rabbitmq-4.0.1
*logstash-mixin-rabbitmq_connection-2.4.0
I see new 5.x versions on rubygems, but these are only for logstash 5.x right?  Any idea if this will be fixed for 2.3.X or what a workaround would be?

My mistake. I'll release a 2.3.x version ASAP
On Fri, May 13, 2016 at 12:33 AM, Domingo Kiser<EMAIL_ADDRESS>wrote:

@andrewvc https://github.com/andrewvc this bit me earlier
today....running logstash 2.3.1 with the following versions installed
*logstash-input-rabbitmq-4.0.1
*logstash-mixin-rabbitmq_connection-2.4.0
I see new 5.x versions on rubygems, but these are only for logstash 5.x
right? Any idea if this will be fixed for 2.3.X or what a workaround would
be?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/logstash-plugins/logstash-input-rabbitmq/issues/82#issuecomment-218955853

@andrewvc nice!  in theory i should be able to do a plugin update afterwards and update my settings to the new types and be GTG.  I was getting a file not found error when i had SSL on via "TLSv1.1" due to the tls_certifciate_path key being in the rabbitmq_settings bag.
error after realizing I needed a version string instead of 'true'
Using TLS/SSL version TLSv1.2
No such file or directory -  {:class=>"Errno::ENOENT", :location=>"org/jruby/RubyFile.java:370:in `initialize'", :level=>:warn, :file=>"logstash/inputs/rabbitmq.rb", :line=>"180", :method=>"register"}
Connecting to RabbitMQ. Settings: {:vhost=>"services", :host=>"localhost", :port=>5672, :user=>"guest", :automatic_recovery=>true, :pass=>"guest", :timeout=>0, :heartbeat=>0, :tls=>"TLSv1.2", :tls_certificate_path=>"", :tls_certificate_password=>""} {:level=>:debug, :file=>"logstash/plugin_mixins/rabbitmq_connection.rb", :line=>"147", :method=>"connect"}

original code in the mixin i had
s[:tls_certificate_path] = @tls_certificate_path || ""

monkey patch workaround
s[:tls_certificate_path] = @tls_certificate_path if @tls_certificate_path

The new mixin should fix all this right?

Also as a workaround, you can set ssl => “TLSv1.2" instead of ssl => true, but if you apply the workaround, it will break when the fix is applied, so be sure to set it back to ssl => true when you upgrade.

@PhaedrusTheGreek that workaround didn't work for me due to the tls_certificate_path problem posted above.  The workaound that did work for me was manually installing compatible versions of logstash-input-rabbitmq and logstash-mixin-rabbitmq_connection after removing the originally installed versions from the gemfile lock in the Logstash distro.  Plugin updates would never work for me due to rubygems trying to install version 5.x of logstash-input-rabbitmq.
What worked for me was the following, specifically choosing 4.1.0 as the logstash-input-rabbitmq plugin, otherwise it only found 5.0.1.
# TODO: rip this thing out when new rmq plugin code has been pushed to
#       upstream rubygems.org per
#       https://github.com/logstash-plugins/logstash-input-rabbitmq/pull/86
#       AND https://github.com/elastic/logstash/blob/2.3/Gemfile.jruby-1.9.lock
#       no longer locks in the old versions.
RUN logstash-plugin uninstall logstash-input-rabbitmq \
        && logstash-plugin uninstall logstash-output-rabbitmq \
        && logstash-plugin install --version 4.1.0 logstash-input-rabbitmq

Thanks for posting the update @dkiser it is much appreciated :) Sorry the workaround didn't work as I'd thought.


Bayesian setup

Right now, the constructor is setting up a Bayesian filter.  This could be totally unnecessary. Maybe it would be better to wait until that filter is called.

I factored this out so it will be easier to adjust.


Geocoder::Lookup::Test & BigDecimal

Hi guys, discovered a problem trying to stub reverse geocodes. My lat/lng comes from an object which is a number stored in BigDecimal object each.
I've stubbed with the following:
Geocoder::Lookup::Test.add_stub(
  [40.7143528,-74.0059731], [
    {
      'latitude'     => 40.7143528,
      'longitude'    => -74.0059731,
      'address'      => 'New York, NY, USA',
      'state'        => 'New York',
      'state_code'   => 'NY',
      'country'      => 'United States',
      'country_code' => 'US'
    }
  ]
)

but instead end up getting this error:
unknown stub request [#<BigDecimal:7fd795afd6a0,'0.407143528E2',18(45)>, #<BigDecimal:7fd795afcf70,'-0.740059731E2',18(45)>]

Any thoughts on a fix or patch?

Temporary solution is obviously to use:
Geocoder::Lookup::Test.add_stub(
  [BigDecimal('40.7143528'),BigDecimal('-74.0059731')], [
    {
      'latitude'     => 40.7143528,
      'longitude'    => -74.0059731,
      'address'      => 'New York, NY, USA',
      'state'        => 'New York',
      'state_code'   => 'NY',
      'country'      => 'United States',
      'country_code' => 'US'
    }
  ]
)

That workaround was what I was going to suggest. :)
It's not immediately obvious to me that this is something geocoder should take into account. You're stubbing a very particular input, and that happens to be an array of BigDecimals. I mostly stub strings (city or street names).
When stubbing I would imagine it's better to be very exact, rather than trying to guess at what other inputs should be covered.

Of course it might become frustrating e.g. if you often have to stub both the BigDecimal and the float variant of the same coordinates. In that case you could maybe write your own stubbing helper which creates the multiple variations:
def add_coordinate_stub(coordinates, results)
  Geocoder::Lookup::Test.add_stub(coordinates.map(&:to_f), results)
  Geocoder::Lookup::Test.add_stub(coordinates.map(&:to_d), results)
end

@lime yep I'll close it out but it's now discoverable for others. Using the stub based on BigDecimal works ok :)