import/no-duplicates groups incompatible import paths

I'm having problems using import/no-duplicates in a Svelte application (not that it is important) that contains the following imports:
import { onMount } from 'svelte'
import { writable } from 'svelte/store'

When running ESLint with the --fix flag, the code will be converted into the following code:
import { onMount, writable } from 'svelte'

And this, of course, will break the application from resolving the module:

"writable" is not exported by<EMAIL_ADDRESS>
In addition, this issue doesn't show up in normal lint mode (without --fix), which made it hard to identify the rule causing the issue.

My suspicion is that you're using TypeScript - if so, what version of TS and the TS eslint import resolver are you using?

{
	"devDependencies":
	"eslint-import-resolver-typescript": "^3.6.3",
	"eslint-plugin-import": "^2.30.0",
	"typescript": "^5.5.4"
}

eslint 8 is the latest version that everything supports, still, so i'd def suggest updating - but the rest are good.
what's your eslint config look like?

Updating to eslint@8 fixes our issue. Is there any in value in still posting our config or shall we close this?
I guess setting strict-peer-dependencies would have prevented us running into this in the first place.

I tested again with ESLint 8.57.1, we got the same issue

.eslintrc.cjs
/** @type { import("eslint").Linter.Config } */
module.exports = {
	extends: ['@sveltejs'],
	root: true,
	extends: [
		'plugin:@typescript-eslint/recommended',
		'plugin:jsonc/recommended-with-json',
		'plugin:storybook/recommended',
		'plugin:svelte/recommended',
		"plugin:import/recommended",
	],
	parser: '@typescript-eslint/parser',
	plugins: ['@typescript-eslint'],
	parserOptions: {
		sourceType: 'module',
		ecmaVersion: 2020,
		extraFileExtensions: ['.svelte'],
	},
	settings: {
		/**
		 * Needed in combination with `eslint-import-resolver-typescript` to enforce `import/extensions` rule.
		 * @see {@link https://github.com/import-js/eslint-plugin-import/blob/main/README.md#typescript}
		 */
		"import/resolver": {
			"typescript": true,
			"node": true,
		},
	},
	env: {
		browser: true,
		es2017: true,
		node: true,
	},
	overrides: [
		{
			files: ['*.json'],
			parser: 'jsonc-eslint-parser',
			rules: {
				'jsonc/no-comments': 'off',
			},
		},
		{
			files: ['*.svelte'],
			parser: 'svelte-eslint-parser',
			parserOptions: {
				parser: '@typescript-eslint/parser',
			},
		},
	],
	rules: {
		curly: 'error',
		'svelte/block-lang': [
			'error',
			{
				enforceScriptPresent: true,
				enforceStylePresent: false,
				script: ['ts', null], // a list of languages or null to signify no language specified
				style: 'scss', // same as for script, a single value can be used instead of an array.
			},
		],
		'svelte/button-has-type': [
			'error',
			{
				button: true,
				submit: true,
				reset: true,
			},
		],
		'svelte/no-at-html-tags': 'warn',
		'import/extensions': ['error', 'always', { ignorePackages: true }],
	},
};

I'll conduct another test with ESLint v9, since I would be happy to put this chore on completed :wink:

Upgrading to ESLint 9.x was the solution for us, but on second thought it might still be considered an issue for the plugin. You mentioned earlier that 8.x is the minimum version supported by the plugin. Shouldn't this be reflected in the peerDependencies version range for ESLint then?

Same issue here, but with eslint 9:
        "@eslint/js": "^9.17.0",
        "@stylistic/eslint-plugin": "^2.12.1",
        "eslint": "^9.17.0",
        "eslint-import-resolver-typescript": "^3.7.0",
        "eslint-plugin-import": "^2.31.0",
        "eslint-plugin-jest": "^28.9.0",
        "eslint-plugin-unicorn": "^56.0.1",
        "globals": "^15.14.0",
        "typescript-eslint": "^8.18.1"
        "eslint-plugin-svelte": "^2.46.1",
        "svelte-eslint-parser": "^0.43.0"

Svelte eslint settings is:
import ts from 'typescript-eslint';
import eslintPluginSvelte from 'eslint-plugin-svelte';
import svelteParser from 'svelte-eslint-parser';

    ...
    plugins: {
        svelte: eslintPluginSvelte,
        '@typescript-eslint': ts.plugin,
    },
    processor: eslintPluginSvelte.processors.svelte,
    languageOptions: {
        parser: svelteParser,
        parserOptions: {
            parser: ts.parser,
            project: './tsconfig.json',
            extraFileExtensions: ['.svelte'],
            svelteFeatures: {
                experimentalGenerics: true,
            },
        },
    },


Installing with MSSQL using the default config, we are getting errors in RabbitMQ.

Describe the bug
Installing with MSSQL using the default config, we are getting errors in RabbitMQ.
senzing-rabbitmq        | PLAIN login refused: user 'rabbitmq' - invalid credentials
senzing-rabbitmq        | 2020-08-18 07:22:30.423 [error] <0.969.0> Error on AMQP connection <0.969.0> (<IP_ADDRESS>:38822 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq        | PLAIN login refused: user 'rabbitmq' - invalid credentials
senzing-rabbitmq        | 2020-08-18 07:22:30.437 [error] <0.972.0> Error on AMQP connection <0.972.0> (<IP_ADDRESS>:38826 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq        | PLAIN login refused: user 'rabbitmq' - invalid credentials
error-log.txt

@docktermj Please take a look at this issue asap. We are blocked by this from starting the installation to Guide House.
Everything was working before 2 weeks after your last fix. But, while I retry the instructions before handing over to them, I got this issue. Please take a look.
Let me know if you need more details.

Trying to recreate using https://github.com/Senzing/docker-compose-demo/blob/master/resources/mssql/docker-compose-rabbitmq-mssql.yaml

Seen in https://github.com/Senzing/docker-compose-demo/files/5088905/error-log.txt
senzing-rabbitmq | 2020-08-18 02:14:24.118 [info] <0.643.0> Statistics database started.
senzing-rabbitmq | 2020-08-18 02:14:24.118 [info] <0.642.0> Starting worker pool 'management_worker_pool' with 3 processes in it
senzing-rabbitmq | 2020-08-18 02:14:24.133 [info] <0.652.0> accepting AMQP connection <0.652.0> (<IP_ADDRESS>:47804 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:24.133 [info] <0.655.0> accepting AMQP connection <0.655.0> (<IP_ADDRESS>:47808 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:24.133 [info] <0.658.0> accepting AMQP connection <0.658.0> (<IP_ADDRESS>:47806 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:24.137 [error] <0.658.0> Error on AMQP connection <0.658.0> (<IP_ADDRESS>:47806 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq | PLAIN login refused: user 'rabbitmq' - invalid credentials
senzing-rabbitmq | 2020-08-18 02:14:24.137 [error] <0.655.0> Error on AMQP connection <0.655.0> (<IP_ADDRESS>:47808 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq | PLAIN login refused: user 'rabbitmq' - invalid credentials
senzing-rabbitmq | 2020-08-18 02:14:24.137 [error] <0.652.0> Error on AMQP connection <0.652.0> (<IP_ADDRESS>:47804 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq | PLAIN login refused: user 'rabbitmq' - invalid credentials
senzing-rabbitmq |  completed with 3 plugins.
senzing-rabbitmq | 2020-08-18 02:14:24.338 [info] <0.8.0> Server startup complete; 3 plugins started.
senzing-rabbitmq |  * rabbitmq_management
senzing-rabbitmq |  * rabbitmq_web_dispatch
senzing-rabbitmq |  * rabbitmq_management_agent
senzing-rabbitmq | 2020-08-18 02:14:27.138 [info] <0.652.0> closing AMQP connection <0.652.0> (<IP_ADDRESS>:47804 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:27.138 [info] <0.655.0> closing AMQP connection <0.655.0> (<IP_ADDRESS>:47808 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:27.138 [info] <0.658.0> closing AMQP connection <0.658.0> (<IP_ADDRESS>:47806 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:27.641 [info] <0.665.0> accepting AMQP connection <0.665.0> (<IP_ADDRESS>:47814 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:27.642 [info] <0.668.0> accepting AMQP connection <0.668.0> (<IP_ADDRESS>:47818 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:27.642 [info] <0.671.0> accepting AMQP connection <0.671.0> (<IP_ADDRESS>:47820 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:27.646 [error] <0.665.0> Error on AMQP connection <0.665.0> (<IP_ADDRESS>:47814 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq | PLAIN login refused: user 'rabbitmq' - invalid credentials
senzing-rabbitmq | 2020-08-18 02:14:27.646 [error] <0.671.0> Error on AMQP connection <0.671.0> (<IP_ADDRESS>:47820 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq | PLAIN login refused: user 'rabbitmq' - invalid credentials
senzing-rabbitmq | 2020-08-18 02:14:27.646 [error] <0.668.0> Error on AMQP connection <0.668.0> (<IP_ADDRESS>:47818 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq | PLAIN login refused: user 'rabbitmq' - invalid credentials

Seen in recreation attempt:

2020-08-18 14:17:53.395 [info] <0.641.0> Statistics database started.
2020-08-18 14:17:53.395 [info] <0.640.0> Starting worker pool 'management_worker_pool' with 3 processes in it
 completed with 3 plugins.
2020-08-18 14:17:53.557 [info] <0.8.0> Server startup complete; 3 plugins started.
 * rabbitmq_management
 * rabbitmq_web_dispatch
 * rabbitmq_management_agent
2020-08-18 14:18:06.913 [info] <0.664.0> accepting AMQP connection <0.664.0> (<IP_ADDRESS>:56136 -> <IP_ADDRESS>:5672)
2020-08-18 14:18:06.921 [info] <0.664.0> connection <0.664.0> (<IP_ADDRESS>:56136 -> <IP_ADDRESS>:5672): user 'user' authenticated and granted access to vhost '/'
2020-08-18 14:18:06.935 [info] <0.680.0> accepting AMQP connection <0.680.0> (<IP_ADDRESS>:56140 -> <IP_ADDRESS>:5672)
2020-08-18 14:18:06.939 [info] <0.680.0> connection <0.680.0> (<IP_ADDRESS>:56140 -> <IP_ADDRESS>:5672): user 'user' authenticated and granted access to vhost '/'
2020-08-18 14:18:06.954 [info] <0.691.0> accepting AMQP connection <0.691.0> (<IP_ADDRESS>:56144 -> <IP_ADDRESS>:5672)
2020-08-18 14:18:06.958 [info] <0.691.0> connection <0.691.0> (<IP_ADDRESS>:56144 -> <IP_ADDRESS>:5672): user 'user' authenticated and granted access to vhost '/'
2020-08-18 14:18:06.980 [info] <0.702.0> accepting AMQP connection <0.702.0> (<IP_ADDRESS>:56148 -> <IP_ADDRESS>:5672)
2020-08-18 14:18:06.984 [info] <0.702.0> connection <0.702.0> (<IP_ADDRESS>:56148 -> <IP_ADDRESS>:5672): user 'user' authenticated and granted access to vhost '/'
2020-08-18 14:18:12.518 [info] <0.664.0> closing AMQP connection <0.664.0> (<IP_ADDRESS>:56136 -> <IP_ADDRESS>:5672, vhost: '/', user: 'user')
2020-08-18 14:18:12.520 [info] <0.680.0> closing AMQP connection <0.680.0> (<IP_ADDRESS>:56140 -> <IP_ADDRESS>:5672, vhost: '/', user: 'user')
2020-08-18 14:18:12.522 [info] <0.702.0> closing AMQP connection <0.702.0> (<IP_ADDRESS>:56148 -> <IP_ADDRESS>:5672, vhost: '/', user: 'user')
2020-08-18 14:18:12.522 [info] <0.691.0> closing AMQP connection <0.691.0> (<IP_ADDRESS>:56144 -> <IP_ADDRESS>:5672, vhost: '/', user: 'user')
2020-08-18 14:18:35.915 [info] <0.750.0> accepting AMQP connection <0.750.0> (<IP_ADDRESS>:47462 -> <IP_ADDRESS>:5672)
2020-08-18 14:18:35.919 [info] <0.756.0> accepting AMQP connection <0.756.0> (<IP_ADDRESS>:47466 -> <IP_ADDRESS>:5672)
2020-08-18 14:18:35.921 [info] <0.750.0> connection <0.750.0> (<IP_ADDRESS>:47462 -> <IP_ADDRESS>:5672): user 'user' authenticated and granted access to vhost '/'

So in the error condition, it appears that the login user is rabbitmq, but in the recreation, the login user is user.   So the question is:  "Why?"
@jaymuthus Just to make sure we're working with the same level of bitnami/rabbitmq:3.8.2, can you run the following on the machine having the error:
docker pull bitnami/rabbitmq:3.8.2

I'm showing this SHA on download:
Digest: sha256:f6a30ae08cc6efdeeee3d06fdc24255b9963f4de871c8612a72ba149cf58cab5

@jaymuthus Are you using the following definition of the rabbitmq: service:
https://github.com/Senzing/docker-compose-demo/blob/ed5b4f5530732946e23f88b617d6c3b95af2c363/resources/mssql/docker-compose-rabbitmq-mssql.yaml#L31-L45
Or are you running with modifications?

In https://github.com/Senzing/docker-compose-demo/files/5088905/error-log.txt it does look like user is also used.
senzing-rabbitmq | 2020-08-18 02:14:36.405 [info] <0.701.0> accepting AMQP connection <0.701.0> (<IP_ADDRESS>:60118 -> <IP_ADDRESS>:5672)
senzing-rabbitmq | 2020-08-18 02:14:36.410 [info] <0.701.0> connection <0.701.0> (<IP_ADDRESS>:60118 -> <IP_ADDRESS>:5672): user 'user' authenticated and granted access to vhost '/'

@jaymuthus You may also have a different issue.   In https://github.com/Senzing/docker-compose-demo/files/5088905/error-log.txt this is seen:
senzing-stream-loader | 2020-08-18 02:15:03,512 senzing-50010890E G2Engine.addRecord() Exception: 9000E|LIMIT: Maximum number of records ingested: 100000; JSON: {"ADDR_CITY": "Dlalas", "ADDR_LINE1": "788 Alma ST", "ADDR_POSTAL_CODE": "75215", "ADDR_STATE": "TX", "CC_ACCOUNT_NUMBER": "50185881568895705", "DATA_SOURCE": "TEST", "DATE_OF_BIRTH": "6/2/1952", "DRIVERS_LICENSE_NUMBER": "V995121498988", "DRIVERS_LICENSE_STATE": "MD", "DSRC_ACTION": "A", "ENTITY_TYPE": "TEST", "GENDER": "N/A", "NAME_LAST": "THOMPSON", "PHONE_NUMBER": "347-4506", "RECORD_ID": "181734352", "SSN_NUMBER": "501-27-9836", "entityid": "181734352", "srccode": "MDMPER"}

Looks like you don't have a sufficient Senzing license at /etc/opt/senzing/g2.lic.  (a.k.a ${SENZING_ETC_DIR}/g2.lic on the failing machine.)

In https://github.com/Senzing/docker-compose-demo/files/5088905/error-log.txt it does look records are getting into the RabbitMQ queue:
senzing-stream-producer | 2020-08-18 02:14:38,316 senzing-50140104D Thread: Process-0-FilterQueueDictToJsonRabbitmqThread-0 Records sent to queue: 3000
senzing-stream-producer | 2020-08-18 02:14:38,935 senzing-50140104D Thread: Process-0-FilterQueueDictToJsonRabbitmqThread-2 Records sent to queue: 4000

And it does look like records are being consumed from the queue:
senzing-stream-loader | 2020-08-18 02:15:03,512 senzing-50010890E G2Engine.addRecord() Exception: 9000E|LIMIT: Maximum number of records ingested: 100000; JSON: {"ADDR_CITY": "Dlalas", "ADDR_LINE1": "788 Alma ST", "ADDR_POSTAL_CODE": "75215", "ADDR_STATE": "TX", "CC_ACCOUNT_NUMBER": "50185881568895705", "DATA_SOURCE": "TEST", "DATE_OF_BIRTH": "6/2/1952", "DRIVERS_LICENSE_NUMBER": "V995121498988", "DRIVERS_LICENSE_STATE": "MD", "DSRC_ACTION": "A", "ENTITY_TYPE": "TEST", "GENDER": "N/A", "NAME_LAST": "THOMPSON", "PHONE_NUMBER": "347-4506", "RECORD_ID": "181734352", "SSN_NUMBER": "501-27-9836", "entityid": "181734352", "srccode": "MDMPER"}

So I think your base problem is the Senzing license at /etc/opt/senzing/g2.lic

I see the following about the lic:
senzing-stream-loader   | 2020-08-18 19:22:21,371 senzing-50010160I -------------------- LICENSE --------------------
senzing-stream-loader   | 2020-08-18 19:22:21,371 senzing-50010161I           Version: 2.0.1 (2020-07-23)
senzing-stream-loader   | 2020-08-18 19:22:21,371 senzing-50010162I          Customer:
senzing-stream-loader   | 2020-08-18 19:22:21,372 senzing-50010163I              Type: EVAL
senzing-stream-loader   | 2020-08-18 19:22:21,372 senzing-50010164I   Expiration date: 2021-01-22
senzing-stream-loader   | 2020-08-18 19:22:21,375 senzing-50010165I   Expiration time: 156 days until expiration
senzing-stream-loader   | 2020-08-18 19:22:21,375 senzing-50010166I           Records: 100000
senzing-stream-loader   | 2020-08-18 19:22:21,376 senzing-50010167I          Contract:
senzing-stream-loader   | 2020-08-18 19:22:21,376 senzing-50010299I -------------------------------------------------
senzing-stream-loader   | 2020-08-18 19:22:21,425 senzing-50010123I Total     memory:<PHONE_NUMBER>0 bytes
senzing-stream-loader   | 2020-08-18 19:22:21,425 senzing-50010124I Available memory:<PHONE_NUMBER>6 bytes
senzing-stream-loader   | 2020-08-18 19:22:21,680 senzing-50010140I System Resources:
senzing-stream-loader   | 2020-08-18 19:22:21,681 senzing-50010141I     Physical cores: 2
senzing-stream-loader   | 2020-08-18 19:22:21,681 senzing-50010142I      Logical cores: 4
senzing-stream-loader   | 2020-08-18 19:22:21,682 senzing-50010143I       Total Memory: 14.5 GB
senzing-stream-loader   | 2020-08-18 19:22:21,682 senzing-50010144I   Available Memory: 11.1 GB
senzing-stream-loader   | 2020-08-18 19:22:21,682 senzing-50010145I Resource requested:
senzing-stream-loader   | 2020-08-18 19:22:21,682 senzing-50010146I                     Processes: 1
senzing-stream-loader   | 2020-08-18 19:22:21,682 senzing-50010147I           Threads per process: 4
senzing-stream-loader   | 2020-08-18 19:22:21,682 senzing-50010148I     Minimum recommended cores: 1
senzing-stream-loader   | 2020-08-18 19:22:21,682 senzing-50010149I    Minimum recommended memory: 4.5 GB
senzing-redoer          | 2020-08-18 19:22:22,204 senzing-50100160I -------------------- LICENSE --------------------
senzing-redoer          | 2020-08-18 19:22:22,204 senzing-50100161I           Version: 2.0.1 (2020-07-23)
senzing-redoer          | 2020-08-18 19:22:22,204 senzing-50100162I          Customer:
senzing-redoer          | 2020-08-18 19:22:22,204 senzing-50100163I              Type: EVAL
senzing-redoer          | 2020-08-18 19:22:22,204 senzing-50100164I   Expiration date: 2021-01-22
senzing-redoer          | 2020-08-18 19:22:22,207 senzing-50100165I   Expiration time: 156 days until expiration
senzing-redoer          | 2020-08-18 19:22:22,207 senzing-50100166I           Records: 100000
senzing-redoer          | 2020-08-18 19:22:22,208 senzing-50100167I          Contract:

This is after a fresh installation

But still, seeing the error
senzing-rabbitmq        | PLAIN login refused: user 'rabbitmq' - invalid credentials
senzing-rabbitmq        | 2020-08-18 19:22:24.449 [error] <0.859.0> Error on AMQP connection <0.859.0> (<IP_ADDRESS>:42498 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq        | PLAIN login refused: user 'rabbitmq' - invalid credentials
senzing-rabbitmq        | 2020-08-18 19:22:24.449 [error] <0.865.0> Error on AMQP connection <0.865.0> (<IP_ADDRESS>:42500 -> <IP_ADDRESS>:5672, state: starting):
senzing-rabbitmq        | PLAIN login refused: user 'rabbitmq' - invalid credentials

i see the following too as you said.
senzing-rabbitmq        | 2020-08-18 19:22:24.760 [info] <0.872.0> connection <0.872.0> (<IP_ADDRESS>:59618 -> <IP_ADDRESS>:5672): user 'user' authenticated and granted access to vhost '/'
senzing-rabbitmq        | 2020-08-18 19:22:24.761 [info] <0.878.0> connection <0.878.0> (<IP_ADDRESS>:59622 -> <IP_ADDRESS>:5672): user 'user' authenticated and granted access to vhost '/'
senzing-rabbitmq        | 2020-08-18 19:22:24.761 [info] <0.869.0> connection <0.869.0> (<IP_ADDRESS>:59616 -> <IP_ADDRESS>:5672): user 'user' authenticated and granted access to vhost '/'

Any idea, why is it attempting to connect as "rabbitmq" and how to resolve it?

In case, if you can't reproduce, please let me know if we can spend like 30mins tomorrow in the morning before 10AM PST.
I will show you and you can help with this.
Thanks for your time and help on this @docktermj

@jaymuthus
The license seen is the "evaluation" license that only supports 100,000 records.
senzing-stream-loader | 2020-08-18 19:22:21,375 senzing-50010166I Records: 100000

Errors in the log suggest you are trying to insert more than 100K records.  You need to insert a license that supports more than the complimentary 100K records.
The errors seen in the senzing-rabbitmq log suggest that there is some other process that is trying to login as username "rabbitmq".   From what I can see, there are no processes in the docker-compose.yaml file that are trying to access RabbitMQ as user "rabbitmq".   Do you have another process that is accessing RabbitMQ?

@docktermj Yes, in that machine, it seems another team has installed a BPM software and that was trying to login using the user rabbitmq. So, we can mark it resolved.


[Nitpick] USB Profiles no longer being loaded?

Game Mode
No response
Give an example of what is wrong
I was doing stuff with it during 0.4.16 but after the update to 0.4.17 it's not working anymore.
I did the following so far so that I know that something happened between the versions.

Checked ability to use the USB at all by going through multiple themes
Checked Preferences.ini file on possible overwrites
Checked usability of USB on older SM versions
Deleted OutFox folder inside the USB for potential faulty values
Deleted entire Save folder for sudden incompatibility

And none of them worked out in the end.
Give an example of what it should look like
Not sure as I don't know if it had been deactivated on purpose or not.
The changelog didn't specify.

It shouldn't have been disabled, we'll look into this and try to get a fix for 4.17.1 asap.
Thanks for reporting!

i see that that issue started when you guys started doing the long term stable builds, and it's still not fixed by 4.18.1. It's also broken on alpha 5's builds, steam and standalone, so i'm guessing it's one of the edits from when you guys started making the LTS builds, might be a good area to check, see if anything there removed or edited the code for USB/Memory Card checking.
i hope this is fixed soon, it always felt cool to plug in a usb drive and have my profile, no matter what pc i was playing on.
sidenote: is it possible that the LTS builds were made after alpha 5's steam builds, and valve required the usb drive read/write disabled to allow it on steam? i wouldn't put it past them, as that has the possibility of being used for malicious practices.

we are currently coding a fix for this, so it should be done when we have the next releases out on all platforms, just waiting on @concubidated to confirm things so it can be properly sorted out
We haven't forgotten!

Fixed in 4.19 / 5.0.0-r32


[Feature Idea] Any plans to create a ChromeOS app on the Web Store?

Do you have any plan to put this on the ChromeOS Web Store in the future? Maybe with the ability to work without an internet connection?

This can be done easily! I did it just using the tutorial here: https://developer.chrome.com/apps/first_app
manifest.json:
{
  "name": "v86!",
  "description": "v86 for Chrome Apps",
  "version": "0.1",
  "manifest_version": 2,
  "app": {
    "background": {
      "scripts": ["showapp.js"]
    }
  }
}

loadapp.js:
chrome.app.runtime.onLaunched.addListener(function() {
  chrome.app.window.create('index.html', {
    'outerBounds': {
      'width': 1920,
      'height': 1080
    }
  });
});

@copy Would you be interested in a PR?

Would you be interested in a PR?

Thanks for the offer, but I don't think those files need to be in the repo.
I think a first step would be to make v86 work offline (like some websites do).

@copy this could be done using Service Workers, as #219 would complement that

ChromeOS apps will be deprecated soon - consider closing this issue.

Would you be interested in a PR?

Thanks for the offer, but I don't think those files need to be in the repo.
I think a first step would be to make v86 work offline (like some websites do).

I'll work on that using Workbox.

ChromeOS apps will be deprecated soon - consider closing this issue.

Time for a PWA, then.

ChromeOS apps will be deprecated soon - consider closing this issue.

Time for a PWA, then.

PWA works in this case then! Although we do need to make the UI a bit more intuitive.

@sr229 how is the pwa going? or is it just a speculation for now?


clicking the cell being edited does not change the editing state

fixed #175

Coverage increased (+0.04%) to 92.02% when pulling 9e4926af39edd1cd7e8d05f12c81d09c1e01858c on yoshidax:fix_dont_change_the_editing_state_if_the_same_cell into ef80a69659570166475f5d6520dd446d63e26ec0 on nadbm:master.


Update README.md

Badget Is Updated It Better To Know Pypi Version and Python Version used

I specified Python version (3.10.) and pip == 23.1.2. Did it work out for you?

Thanks :-)


[BUG]: Crowdsourced Patient Database button redirects to API page.

Describe the bug
Crowdsourced Patient Database button on the main website and on the API home page, both redirect to API page itself.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://www.covid19india.org/'
Scroll down to 'The End of the page'
Click on 'CROWDSOURCED PATIENT DATABASE'
See error: Redirects to the API page.

Expected behavior
Its should transfer to the Database page where everything is placed, typically in a Spreadsheet - Google Sheets as before?
Desktop (please complete the following information):

OS: Windows
Browser: Edge, Chrome
Version: Respective Latest Versions

Smartphone (please complete the following information):

Device: Samsung Galaxy A6+
OS: Android Pie
Browser: Edge, Chrome
Version: Respective Latest Versions

Additional context
If that button isnt functional anymore - or even temporarily not functioning, it should be removed.
While I am fully Aware of the data partition that took place, I have raised this issue from a UX perspective.

This Button for "CROWDSOURCED PATIENT DATABASE" should be removed, and also the hyperlinks on https://api.covid19india.org

I can take up the issue and submit a PR if Status is turned to Available.

API is still a database in a way no? Why should it go away?

What I think is, when you put a button for the Database for public access, they generally look for something like a spreadsheet.
Problem
A common man wont understand the API and how it works, they wont know how to look at JSON files and HTTP requests. This has happened to me when I showed the website to my parents and relatives. Some of them who dont have a technical background, yet get fascinated by technology clicked that button and got redirected to the API page and then got confused what to do. They wont understand variables like raw_data. And I am sure this might be a case for a lot of them.
Solution
So, maybe if the name can be changed to something more appropriate, say, Opensource API or Open Data Sources or Open Data Store something on those lines, then it would make more sense than redirecting users to the API page.
Additionally
The API page redirection could happen through a Call to action button saying, "Use Our API" or a longer CTA, say, "Create your own tracker using our API".
Finally
I would be willing to make the appropriate changes if allowed.

@jeremyphilemon your views on this?

I agree that the terminology might be confusing now. We can switch if we have a good alternative

Assigned to @Cryptonex7 Please change it to "Crowdsourced data API"


[BUG] Pasting image don't work on WSL2

Please confirm

[ ] I am running the latest version of this plugin

Describe the bug
Cannot paste image from clipboard using either the xclip or wl-paste on Ubuntu runned on WSL2.
What I get is:
Unable to write image /home/user/zettelkasten/img/pasted_img_20240829123455.png.
Is there an image on the clipboard?
See also issue 131
Press ENTER or type command to continue
Unable to write image /home/user/zettelkasten/img/pasted_img_20240829123455.png
Press ENTER or type command to continue

I tried with only wl-paste installed, only xclip or both in the same time. Nothing works.
Linked issue didn't not help at all.
Ofc, everything is updated.
To Reproduce
Steps to reproduce the behavior:

Start nvim
Open note
Use paste image from clipboard
See error

Expected behavior
Working image pasting
Screenshots
If applicable, add screenshots to help explain your problem.
Operating system (please complete the following information):

OS: Nvim on Linux, running on WSL2.

Additional context
Add any other context about the problem here.

I am seeing the same, is there a workaround for this? I haven't tried, but I assume manually moving an image to the correct dir, and linking that way would work.


[decompiler] Several small fixes

Fixes a bug where logtest used to generate a GOAL boolean wasn't recognized (using conditional move, like the last condition in an and to bool for example)
Fix a bug where order of bitfield enums is different between windows and linux if there are multiple entries for the same value. (#771)
Make labels work inside of expressions so far labels should work. (#718)
Stricter casting on function return types (#772)

and also #773


Compact navbar option

Description

Related Issue(s)

closes #{issue number}

Verification/QA

Manual functionality testing

[ ] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
[ ] No testing done/necessary

Automated tests

[ ] Unit test(s) have been added/updated
[ ] Cypress E2E test(s) have been added/updated
[ ] No automatic tests are needed here (no functional changes/additions)
[ ] I want someone to help me make some tests

UU/WCAG (follow these guidelines until we have our own)

[ ] I have tested with a screen reader/keyboard navigation/automated wcag validator
[ ] No testing done/necessary (no DOM/visual changes)
[ ] I want someone to help me perform accessibility testing

User documentation @ altinn-studio-docs

[ ] Has been added/updated

[ ] No functionality has been changed/added, so no documentation is needed
[ ] I will do that later/have created an issue

Changes/additions to component properties

[ ] Changes are reflected in both src/layout/layout.d.ts and layout.schema.v1.json, and these are all backwards-compatible
[ ] No changes made

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[ ] This change/feature does not require any changes to Altinn Studio

Sprint board

[ ] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
[ ] I don't have permissions to do that, please help me out

Labels

[ ] I have added a kind/* label to this PR for proper release notes grouping
[ ] I don't have permissions to add labels, please help me out

Not sure what's going on here with the cypress tests failing, but the navigation bar seems to have disappeared.. Did the tests work when running locally?

Closing PR and creating a new one: https://github.com/Altinn/app-frontend-react/pull/935


rollback spring boot maven plugin version to 1.3.5.RELEASE

To fix the potential startup issue of chown: cannot access '': No such file or directory

Codecov Report

Merging #1557 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1557      +/-   ##
============================================
+ Coverage     48.62%   48.63%   +<.01%
- Complexity     1896     1897       +1
============================================
  Files           393      393
  Lines         11495    11495
  Branches       1192     1192
============================================
+ Hits           5590     5591       +1
+ Misses         5477     5476       -1
  Partials        428      428

Impacted Files
Coverage Δ
Complexity Δ

...amework/apollo/openapi/util/ConsumerAuditUtil.java
83.33% <0%> (+2.77%)
7% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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


(Solved) Plugin 5.5 branch compiler errors on Linux

I've built branch 5.5 of this plugin successfully on Linux, with UE 5.5.1 (prebuilt). There were a few compiler errors caused by "&&" clauses within "||" expressions. Apparently the clang compiler is not happy assuming higher precedence for && than for ||. I fixed the problems easily by enclosing the && clauses within parentheses. Here is a diff of the changes, with the left side being the tracked branch and the right being my local version.
diff -r ProjectCleaner.git/Source/Pjc/Private/PjcSubsystem.cpp /opt/UnrealEngine_5.5.1_prebuilt/Engine/Plugins/Marketplace/ProjectCleaner/Source/Pjc/Private/PjcSubsystem.cpp
549,550c549,555
< 					bExistsInSearchList && !bSearchInvert ||
< 					!bExistsInSearchList && bSearchInvert
---
> 					(
> 						bExistsInSearchList && !bSearchInvert
> 					)
> 					||
> 					(
> 						!bExistsInSearchList && bSearchInvert
> 					)
1144c1149
< 	return GEditor && GEditor->PlayWorld || GIsPlayInEditorWorld;
---
> 	return ( GEditor && GEditor->PlayWorld ) || GIsPlayInEditorWorld;
diff -r ProjectCleaner.git/Source/Pjc/Private/Slate/SPjcTabAssetsCorrupted.cpp /opt/UnrealEngine_5.5.1_prebuilt/Engine/Plugins/Marketplace/ProjectCleaner/Source/Pjc/Private/Slate/SPjcTabAssetsCorrupted.cpp
188a189
> 			(
191a193
> 			)
diff -r ProjectCleaner.git/Source/Pjc/Private/Slate/SPjcTabAssetsIndirect.cpp /opt/UnrealEngine_5.5.1_prebuilt/Engine/Plugins/Marketplace/ProjectCleaner/Source/Pjc/Private/Slate/SPjcTabAssetsIndirect.cpp
252a253
> 			(
256a258
> 			)

I'm providing this as a diff rather than a pull request (unless you request otherwise) to prevent my Linux editor from messing up the tab expansion or newlines for the source files. Since this is a small changeset I thought it might be easier this way. Also, I'm new enough to C++ that I may not have the source formatted exactly the way you prefer.

Hey @sna-scourtney
Thanks for PR, I accepted your changes in 5.5 branch. Everything working fine in windows v5.5.


picasa/slurp: use the redirect-less flow instead

Current coverage is 88.02% (diff: 100%)

Merging #2732 into master will decrease coverage by <.01%

@@             master      #2732   diff @@
==========================================
  Files           245        245
  Lines         18287      18287
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits          16099      16098     -1
- Misses         1925       1926     +1
  Partials        263        263

Powered by Codecov. Last update 067dc26...be03112


Add advance on Bytes and BytesMut

In order to avoid unnecessary allocations, a Bytes structure remembers
the capacity with which it was first created. When a reserve operation
is issued, this original capacity value is used to as a baseline for
reallocating new storage.
Previously, this original capacity value was stored in its raw form. In
other words, the original capacity usize was stored as is. In order to
reclaim some Bytes internal storage space for implementing advance,
this original capacity value is compressed from requiring 16 bits to 3.
To do this, instead of storing the exact original capacity. The original
capacity is rounded down to the nearest power of two. If the original
capacity is less than 1024, then it is rounded down to zero. This
roughly means that the original capacity is now stored as a table:
0 => 0
1 => 1k
2 => 2k
3 => 4k
4 => 8k
5 => 16k
6 => 32k
7 => 64k

For the purposes that the original capacity feature was introduced, this
is sufficient granularity.
The second commit implements advance by using this new storage capacity
to store the window offset into the vec. The ptr, len, and cap fields
represent the active window, i.e. the user view after a call to advance. This
makes common operations like dereferencing the slice fast.
Relates to #74

Sorry I'm pretty out of touch with the implemenation here, you'll likely wish to find a different reviewer


(PUP-7042) Mark strings in graph

This commit marks user-facing error and info strings in
lib/puppet/graph/* for translation.

CLA signed by all contributors.

Closing and reopening to fix Travis.

Updated.

@McdonaldSeanp are you good with the updated changeset?

Looking at the comment @McdonaldSeanp left, it has been addressed. I think this is good to merge as he is unavailable for a bit.


CharsReaderObservableSuite has a flaky test

It sometimes fails on CI with
[info] - fromCharsReader closes the file handle on cancel *** FAILED ***
[info]   received Some(Success(())) != expected None (CharsReaderObservableSuite.scala:181)

e.g. in https://travis-ci.org/monix/monix/jobs/585428074

it wouldn't change anything if we changed the sleep duration to something longer, right?
i wonder if it would make sense to see what data makes this test fail? and then see if its reproducible locally?

it wouldn't change anything if we changed the sleep duration to something longer, right?

I don't think so, it uses TestScheduler and s.tick() doesn't allow any time to pass

i wonder if it would make sense to see what data makes this test fail? and then see if its reproducible locally?

I suppose we could create a PR which prints generated input and rerun CI until it fails

I just fixed it in #1122
The problem is that randomReaderWithOnFinish, uses randomString(), which can return an empty string, yielding an empty Observable.


CI is fails because of metric test cases

Is this a BUG REPORT or FEATURE REQUEST?:
Bug which is causing CI failure in hotpot

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
When new PR raised some jobs in CI fails by throwing following error
ok  	github.com/opensds/opensds/contrib/drivers	0.037s	coverage: 18.9% of statements
E1128 06:28:38.393831   19493 metrics_cli.go:52] file ReadDefaultConfigFile can't readrados: Invalid argument
E1128 06:28:38.397011   19493 metrics_cli.go:461] unmarshal failed
--- FAIL: TestCollectMetrics (0.02s)
    ceph_metrics_test.go:208: expected metric spec
    ceph_metrics_test.go:210: &{InstanceID:b987-654-321 InstanceName:opensds-ceph-b987-654-321 Job:ceph Labels:map[cluster:ceph pool:rbd] Component:pool Name:used Unit:bytes AggrType: MetricValues:[0xc0000a1200]}
    ceph_metrics_test.go:212: &{Timestamp:123456 Value:859}

What you expected to happen:
CI should pass successfully for all jobs
How to reproduce it (as minimally and precisely as possible):
Raising PR in hotpot code against master/development branch
After raising PR check CI jobs status
Anything else we need to know?:
Environment:

Hotpot(release/branch) version:
master branch
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

@Shruthi-1MN , Please check and close

@NajmudheenCT , Please assign to someone who knows about metric test cases. I still don't know the RCA.


Separate/upstream Util directory

Some relevant discussion in https://github.com/project-oak/silveroak/pull/910
Right now, we have a lot of code in cava/Cava/Util that is not specific to our project. That means our dependency structure is a little strange; a lot of things that are defined in cava2 have dependencies on cava/ anyway because they use the Util files. Restructuring our directories so that Util is a separate library that cava and cava2 both depend on will simplify this and speed up our CI.
Additionally, some of the stuff in Util might be useful for other Coq projects, especially the list/vector lemmas and some of the tactics. If we want to be good open-source citizens, we could upstream some of those things to coqutil (it would be good to address #896 first, because the list/vector infrastructure makes heavy use of autorewrite).

Regarding upstreaming to coqutil, that'd be very welcome, I think. I'm just not sure about vector lemmas, I think neither @andres-erbsen nor myself endorse usage of dependently typed vectors, so we might want to keep them out of coqutil.

Fair enough about the vector lemmas -- I agree it might do people a disservice to point them in that direction.

coqutil also already has primitive tuples and hlists, so it's not like we have a principled record of favoring less dependent types. But I do pretty much agree with the impression one would get from https://github.com/coq/coq/issues/6459regarding stdlib vectors. :shrug:

We since moved away from vectors on this project because of those issues. In the meantime, we did write some things that make standard library vectors more sane to work with (for instance, the example in that issue, rev (rev x), works fine with the alternate definition, reverse, that we've defined, which recurses on the length of the vector instead of using eq_rect_r nonsense):
Compute (rev (rev [1;2;3])). (* huge ugly expression with proof terms *)
Compute (reverse (reverse [1;2;3])). (* [1; 2; 3] *)

We also have, for example, resize_default, which resizes a vector by padding/truncating it and rewrites to the identity in proofs if the lengths are equal (used for, for instance, changing a vector of length n+m to a vector of length m+n in a way that doesn't wreck computation). My general stance here is that standard library vectors are best avoided, but that if someone is already committed to using them we've developed some useful tools that make them easier. I'm not sure there's a good way to communicate "don't use this unless you really have to", though, so happy to leave them out.
I think in an ideal world, the best way to upstream the work we've done on vectors would be to write a new vector library in coqutil that replaces the standard library one, has all of our lemmas/automation, and is more computation-friendly. This would probably be a much more effective "use this, not the standard library" signal, but is also considerably more work. I'm not sure I'm ready to commit to doing it, but would coqutil accept such a library if I found myself with the time/inclination?

I just saw that coq-ext-lib, which is used by Cava, also has its own vector, so maybe instead of writing yet another definition of vectors, that could be a place for it?
But given that we're moving from Cava1 to Cava2, which does not use vectors any more, would there still be a project using these vectors? As in, would you keep eating your own dogfood?

I just saw that coq-ext-lib, which is used by Cava, also has its own vector, so maybe instead of writing yet another definition of vectors, that could be a place for it?

I think coq-ext-lib is not focused on being computation-friendly, and my impression is that its main focus is to implement things that make Coq look more like Haskell for people who are approaching Coq with a Haskell background. I think it's a somewhat different purpose than coqutil, which I see (very selfishly) as providing the useful lemmas and tactics that should be in the standard library but that I'd otherwise have to define for myself every time I start a new project.

But given that we're moving from Cava1 to Cava2, which does not use vectors any more, would there still be a project using these vectors? As in, would you keep eating your own dogfood?

That's a good point -- I think there would probably be no immediate use for them. Leaning "not worth it".


add section on theory and best practices of hyperparameter tuning

@rbarreto

https://www.analyticsvidhya.com/blog/2022/02/a-comprehensive-guide-on-hyperparameter-tuning-and-its-techniques/


Fix Binance ExchangEinfo downloader

Description

Improve Binance ExchangeInfoDownloader. Add minimum_order_size  to symbol properties db file.
Also updated Binance symbol properties
exchangeInfo_20211006.zip
Related Issue

N/A
Motivation and Context

Doesn't include min order size to output data
Requires Documentation Change

N/A
How Has This Been Tested?

manually, Binance symbol props are also updated

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[ ] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

@Marinovsky
right, @Martin-Molinero highlighed that minimum_order_size should be in base currency, so I've changed the implementation so lot_size comes from LOT_SIZE size filter (stepSize property), but minimum_order_size comes from MIN_NOTIONAL (minNotional property)
Agree?

@Marinovsky
right, @Martin-Molinero highlighed that minimum_order_size should be in base currency, so I've changed the implementation so lot_size comes from LOT_SIZE size filter (stepSize property), but minimum_order_size comes from MIN_NOTIONAL (minNotional property)
Agree?

Hmm not really since most brokerage models use the minimum order size by the base currency and not always the parameters LOT_SIZE in the symbol-properties-database.csv is the same as the minimum_order_size we get from the LOT_SIZE filter in the Binance API, for example in ADABRL


Follow up with Bart RE: Design Document

I've decided to create a technical specification document based off the templates provided.

Closing this issue, I've submitted the other design document as well with the things we know, the things we think we know, and items we do not know.


SF: Project admin can override the language codes used by Serval for the source and target

Issue 3: https://docs.google.com/spreadsheets/d/13Y8d3z3JajAoR2B1zDbsjb0q_GLVQaB6iX9rZPM9it4/edit#gid=0

Guidance for user in UI: the language for the training source and the pretranslation source must be the same.
Admin UI: Allow overriding the source and target language code that will be used by Serval - and call out the NLLB language codes as recommended for sources.

See https://jira.sil.org/browse/SF-2624


Add language translations

Support for the top 10 languages

Mandarin Chinese – 882 million

Spanish – 325 million

English – 312-380 million

Arabic – 206-422 million

Hindi – 181 million

Portuguese – 178 million

Bengali – 173 million

Russian – 146 million

Japanese 128 million

German – 96 million

Planning to set up a paid service to translate app-wide text after the re-design.

Add support for crowdin translations https://github.com/nighthawk-apps/nighthawk-wallet-android/pull/128
Contributors are invited to help translate strings at https://crowdin.com/project/nighthawk-wallet


Added hints and tips section to minikube tutorial

Added hints and tips section to minikube tutorial.

/assign @sarahmaddox

@sarahmaddox
Thanks for your review! I have modified the file as per your review feedback. Please review and feel free to let me know if further change is needed.

Thanks @janeman98!
/lgtm
/approve

Thanks @sarahmaddox .
Question:
Should we rename the minikube tutorial back to getting-started-minikube.md and move it back to docs/started directory? If not, we probably need to change the url that point to the previous getting-started-minikube.md to this new minikube tutorial location.
Please let me know which way is better and I will create a PR to change it.


unknown attribute 'key' for Activity

I am using public_activity for my "goals" model where I want to track and display users activities on a goals (ex: Skylar created a new goal, Cyrus updated his goal, etc...)
I already have a table called Activities in my schema so I changed the name of the table the gem provides from activities to events.
Now when a goal is created and saved, I get an error ActiveRecord::UnknownAttributeError at /goals unknown attribute 'key' for Activity.. Any idea what is going wrong?
Cheers!

Have you renamed your model Activity to Event aswell?

Are you talking about a model that I created prior to this gem or do I need a model for Event to use this gem?

The one you had prior.
On 10 April 2015 at 20:55, Cyrus Ghazanfar<EMAIL_ADDRESS>wrote:

Are you talking about a model that I created prior to this gem or do I
need a model for Event to use this gem?
—
Reply to this email directly or view it on GitHub
https://github.com/pokonski/public_activity/issues/213#issuecomment-91651251
.

No i did not, I kept my original model and table as activity

class Goal < ActiveRecord::Base

  include PublicActivity::Model
  tracked

	has_many :activities, dependent: :destroy
	has_many :goal_tags
	has_many :tags, through: :goal_tags
	has_many :comments, as: :commentable, dependent: :destroy
	belongs_to :user

  validates :name, :description, presence: true
  validates :due_date, presence: true

  accepts_nested_attributes_for :tags

  def days_left
    (self.due_date - Time.now.to_date).to_i
  end

end

This is the model I want to track.
It seems like it is looking for a a key attribute in my activity model as opposed to the "events" table of the public_activity gem

Yes there's a name clash. One way to solve this problem is to rename your app's model Activity to Event and set table_name to sth like events and let public_activity have Activity model and activities table.

@cyzanfar how did you resolve this issue? I'd like to keep my original Activities table without renaming it.


Refactor deletePolicy to change report names without calling fetchAllReports

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Break down in numbered steps
Expected Result:
Describe what you think should've happened
Actual Result:
Describe what actually happened
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
Reproducible in staging?:
Reproducible in production?:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub

Sorry @strepanier03 no action to take here. I forgot to remove the label :)

No update yet

No update

No update, blocked on n7

No update, blocked on n7

Same as last week

hold

no update

No update, still focused on API refactor before this.

we're almost ready for this!

This was fixed by other PRs and the method no longer exists. Closing.


MuiSvgIcon in v4 are blurry

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
With the latest version the MuiSvgIcon has a fontSize set in rem's which makes the icons blurry. Previously it was in px.
Overriding the style, and returning the value of 24px fixes the problem, but the default is not nice.
Also with the default value of 1.5rem the icons are larger then what they were previously.

Your Environment 🌎

Tech
Version

Material-UI
v4.3.3

React

Browser

TypeScript

etc.

Duplicate of #13491.


Editorconfig support

Ideally would be great if something like the editorconfig integration would happen directly in the rust-${editor} integration, in the mean time would be quite neat to have a mean to extract the information from the rustfmt configuration and produce a .editorconfig.

Isn't this a duplicate of #2938?

Isn't this a duplicate of #2938?

Its the other way around. I'd like this way more.

While I think this is an interesting idea, I'm going to close as it's not something the rustfmt will implement and I think it's a feature that's better served via a community crate.
If anyone does decide to implement as a crate feel free to post and we'll be happy to link out to it/reference from our docs. Also, similarly to #2938, anyone sufficiently motivated may certainly still submit a PR for review and consideration; just a bit too far outside our core goals/feature focus areas for us to consider.


Adding the ls_lin modules to support the ls command on linux devices.

The python empire agent does not have support for the ls command on the Linux OS, it was developed for the mac OS.  I copied that module and updated it to work on Linux and moved it into the Multi folder as ls_lin.py.  I also updated the empire.py to add the alias and module. It may be a good idea to update the original ls module for mac os to help differentiate between the two.

@jarrodcoulter Can you resubmit this without removing the pre-obfuscate command and removing it from the main menu class?


[Bug and Solution] Weird bug with examples in checkbox, radio, dropdowns (White outline on focused radio and checkbox elements)(ring-offset-gray-700)

Describe the bug
This is how I see it on your example page

And this is how I see it when I copy/paste the exact same code into my page on my own site

0 code changes, and I've tried a relative empty/clean project with no unusual overrides happening anywhere else.
I've spent soooo many hours trying to figure out what the heck was going on. I finally tracked down the 'issue'.
In both your 'html' code for the various things, and on the html itself you use dark:ring-offset-gray-700
However, the way to fix it on my end is to do dark:focus:ring-offset-gray-700 or just focus:ring-offset-gray-700 since I'm not using dark mode code.
My suggested fix is to update your 4 examples here to be the dark:focus:ring-offset-gray-700, since I think that's whats intended here?
4 locations of it in the readme, not sure where your website code is or if it references the md directly.
https://github.com/themesberg/flowbite/search?q=ring-offset-gray-700*
I am not sure if there is some other setting that is causing some weird behavior, but I know that simple change made fixed it.
Desktop (please complete the following information):

OS: Windows
Browser Chrome
Version 107+

Additional context
Add any other context about the problem here.

Not sure if there is some other subtle override happening somewhere else, like in a tailwind.config.js or something, so other ideas are welcome too.

Hey @namrog84,
Did you install Flowbite as a plugin inside your tailwind.config.js file?
Generally that is where we add these pseudo classes.
Cheers,
Zoltan

My plugins in my tailwind.config.js looks like this
plugins: [
    require('@tailwindcss/forms'),
    require('@tailwindcss/aspect-ratio'),
    require('flowbite/plugin'),
  ],

Hey @namrog84,
The Flowbite plugin already adds styles for the form pseudo elements - what happens if you remove the official @tailwindcss/forms plugin? Or do you use something essential from there?

Hi @zoltanszogyenyi,
@namrog84 is indeed right.

Tailwind playgroud: https://play.tailwindcss.com/ljnQ8F3gvi
As @namrog84 suggested dark:focus:ring-offset-gray-700 fixes this!

Thanks @CorwinDev for the input - seems like we have to update all our occurences in the docs.

Fixed in https://www.producthunt.com/golden-kitty-awards.


electron: (mostly) remove dependency on libXss.so

Description of changes
Electron 10, which is built from Chromium 85.0.4183.84, no longer depends on libXScrnSaver. This was removed from Chromium upstream in revision 782094, which landed in Chromium 85.0.4182.0.
This change removes the LD_PRELOAD of libXss.so.1 (which probably should have been done differently in the first place) and simply includes libXScrnSaver in the rpath for Electron versions prior to 10.0.0.
I tested the only package that still depends on Electron 9, authy, which seems to start up fine, as well as a package that depends on Electron 10, teleprompter, which also starts seemingly correctly. I also verified that the newer binaries don't have libXss.so.1 in their DT_NEEDED.
Fixes #150541
Fixes #165148
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.

The change looks great, thank you! I pinged authors of https://github.com/NixOS/nixpkgs/issues/150541 and https://github.com/NixOS/nixpkgs/issues/165148 in respective issues to test whether this change fixes the issues.

Merged, thanks @impl!

Backport to stable in https://github.com/NixOS/nixpkgs/pull/173176


OCI_DequeueGet returns null pointer when message has empty payload

Hi Vincent,
It appears that OCI_DequeueGet exits prematurely and returns a null pointer whenever a message being dequeued has NULL payload. I have a RAW queue in my app, and the data is passed as a correlation ID, hence the payload is NULL. If the payload has at least one byte, everything works fine.
Here is my test case:
begin
   dbms_aqadm.create_queue_table(
      queue_table            => 'test_qtab',
      queue_payload_type     => 'raw');
end;
/

begin
   dbms_aqadm.create_queue(
      queue_name          => 'test_q',
      queue_table         => 'test_qtab');
end;
/

exec dbms_aqadm.start_queue (queue_name => 'test_q');
declare
  l_enqueue_options     dbms_aq.enqueue_options_t;
  l_message_properties  dbms_aq.message_properties_t;
  l_message raw(256);
  c_msg_queue_name varchar2(100) := 'test_q';
  message_handle raw(16);
begin
  l_message_properties.correlation := '123'; -- the only thing I need from the message
  l_message := null; --hextoraw('FF'); -- works fine when the payload is not empty
  dbms_aq.enqueue(
        queue_name              => c_msg_queue_name,
        enqueue_options         => l_enqueue_options,
        message_properties      => l_message_properties,
        payload                 => l_message,
        msgid                   => message_handle
    );
  commit;
  dbms_output.put_line('enqueued msg ' || rawtohex(message_handle));
end;
/

By the way, even though OCI_DequeueGet returns null, which is an indication of a failure, OCI_GetLastError doesn't return any error.
Thanks!

Hi,
Indeed, OCI_DequeueGet() returns a null OCI_Msg when payload is null.
I will change its behaviour to return a valid OCI_Msg even if payload is null.
Code changes and tests will be committed today.
Regards,
Vincent

Fix committed for this issue.
Some issues were related to the 4.7.0 code refactoring :(
This week, I will add more non regression tests on this part of the API in the Test suite.
Regards,
Vincent

I can dequeue the message now, but I think the latest change in OcilibMessageGetID is breaking this function now, i.e. I'm not getting the message ID. It worked in the previous version.
My guess is that since max_len is always 0, len is also 0 because of min(). Hence the value is not copied.
`unsigned int max_len = 0;
*len = 0;
if (msg->id)
{
    const ub4 raw_len = OCIRawSize(msg->typinf->con->env, msg->id);

    *len = min(max_len, raw_len);

    memcpy(id, OCIRawPtr(msg->typinf->con->env, msg->id), (size_t) (*len));
}`

hi,
Sorry for the issue.
Previous change was committed to quickly.
I've just fixed it.
I will add more tests i the test suite this week on updated code.
Regards,
Vincent

Works like a charm! Thanks for building and maintaining this amazing library.

Sorry, one more question about OcilibMessageGetID()
During Enqueue, I'd like to retrieve a message ID that has just been put in the queue. So I make the following sequence of calls:
OCI_TypeInfoGet
OCI_EnqueueCreate
msgHandle = OCI_MsgCreate
OCI_MsgSetCorrelation
// put in the message body if not empty
OCI_EnqueuePut
if success {
OCI_MsgGetID(msgHandle)
// check for success and unpack the buffer
commit
}

OCI_MsgGetID returns success, but the message ID is not in the buffer. I ran it in debugger, and I think the message ID that is supposed to be returned by OCIAQEnq function is being ignored in the following call in OcilibEnqueuePut:
ret = OCIAQEnq(enqueue->typinf->con->cxt, enqueue->typinf->con->err,
                       (OraText*)name, enqueue->opth, msg->proph,
                       enqueue->typinf->tdo, &payload, &ind, NULL, OCI_DEFAULT);

Is this something you can fix?
Thanks!

Hi, I will create an issue and commit a fix today for that :)
Thanks for reporting that msg id is was not available after enqueue on the msg :)
Regards,
Vincent

Created issued #284 and committed a change (c371644e) to implement the enhancement request


Disqus is not working

Browser： Google
os:windows 10
I've determined that shorname is correct, and when Disqus is enabled, it will not display properly at the end of the article.
Here is the effect shown in the comments section of my local web page.:

Hi, this is the maintainer of @staticmanlab, a public GitLab instance of Staicman. Have you ever thought of migrating from Disqus, which has a plethora of shortcomings that deter many bloggers, say

privacy issues
slow load speed
no markdown support
poor SEO
high cost of migration

You may refer to these articles to know more.

https://victorzhou.com/blog/replacing-disqus/
https://old.reddit.com/r/programming/comments/b9022a/switching_off_of_disqus_reduced_my_page_weight_by/
https://medium.com/remys-blog/ejecting-disqus-4120e9985823


Invalid Pod spec leads to config volume never being deleted

Current Behavior
If one of the resources in the manifest part of a podman-kube workload is invalid,
this can lead to podman kube play and podman kube down to fail.
As during the creation of the workload, the config volume is written first and
this volume is not deleted if the deletion of the workloads fails,
the volume will never be deleted.
Each time the Ankaios agents starts, it sees the volume, and tries to delete this workload again.
After a restart of the Ankaios agent, it is also confuses the workload instance name of the incorrect and the correct workload and
deletes the correct workload.
Expected Behavior
After deleting a podman-kube workload and this workload not having any Podman resources anymore,
the Ankaios agent shall delete the config volume of this workload, even if podman kube down fails.
The Ankaios agent shall also be able the handle multiple existing workloads instances with the same workload name and
only delete the not needed workload instances.
Steps to Reproduce

Start ank-server with the startup state given below
Start ank-agent
Stop ank-agent and ank-server
Fix the error in the startup state, by setting the apiVersion to v1
Start ank-server
Start ank-agent
Stop and start ank-agent

Use podman volume ls to see, the config volume for the nginx workload is not deleted.
Look at the log output of ank-agent during the third start. The ank-agent sees two reusalbe workload,
also once should already be deleted.
It will also fail to delete first workload again.

state.yml:
workloads:
   nginx:
     runtime: podman-kube
     agent: agent_A
     restart: true
     updateStrategy: AT_MOST_ONCE
     accessRights:
       allow: []
       deny: []
     tags: []
     runtimeConfig: |
       manifest: |
         apiVersion: 1
         kind: Pod
         metadata:
           name: nginx
         spec:
           restartPolicy: Never
           containers:
           - name: server
             image: docker.io/nginx:latest
             ports:
             - containerPort: 80
               hostPort: 8080

Context (Environment)
Tested inside LXD containers running Arch Linux and Ubuntu 23.
This also interacts with an Podman error, as a failing podman kube play can leave already created resource (Podman #17434).
Logs
ank-agent first start:
[2023-11-29T13:04:05Z DEBUG ank_agent] Starting the Ankaios agent with
        name: 'agent_A',
        server url: 'http://<IP_ADDRESS>:25551/',
        run directory: '/tmp/ankaios/'
[2023-11-29T13:04:05Z TRACE ank_agent::control_interface::directory] Reusing existing directory '"/tmp/ankaios/agent_A_io"'
[2023-11-29T13:04:05Z INFO  ank_agent::agent_manager] Starting ...
[2023-11-29T13:04:05Z DEBUG ank_agent::agent_manager] Start listening to server.
[2023-11-29T13:04:05Z DEBUG grpc::client] gRPC Communication Client starts.
[2023-11-29T13:04:05Z TRACE grpc::execution_command_proxy] RESPONSE=ExecutionRequest { execution_request_enum: Some(UpdateWorkload(UpdateWorkload { added_workloads: [AddedWorkload { name: "nginx", runtime: "podman-kube", dependencies: {},
restart: true, update_strategy: AtMostOnce, access_rights: None, tags: [], runtime_config: "manifest: |\n  apiVersion: 1\n  kind: Pod\n  metadata:\n    name: nginx\n  spec:\n    restartPolicy: Never\n    containers:\n    - name: server\n
    image: docker.io/nginx:latest\n      ports:\n      - containerPort: 80\n        hostPort: 8080\n" }], deleted_workloads: [] })) }
[2023-11-29T13:04:05Z DEBUG ank_agent::agent_manager] Agent 'agent_A' received UpdateWorkload:
        Added workloads: [WorkloadSpec { agent: "agent_A", name: "nginx", tags: [], dependencies: {}, update_strategy: AtMostOnce, restart: true, access_rights: AccessRights { allow: [], deny: [] }, runtime: "podman-kube", runtime_config:
"manifest: |\n  apiVersion: 1\n  kind: Pod\n  metadata:\n    name: nginx\n  spec:\n    restartPolicy: Never\n    containers:\n    - name: server\n      image: docker.io/nginx:latest\n      ports:\n      - containerPort: 80\n        hostPort: 8080\n" }]
        Deleted workloads: []
[2023-11-29T13:04:05Z INFO  ank_agent::runtime_manager] Received a new desired state with '1' added and '0' deleted workloads.
[2023-11-29T13:04:05Z DEBUG ank_agent::runtime_manager] Handling initial workload list.
[2023-11-29T13:04:05Z DEBUG ank_agent::runtime_connectors::runtime_facade] Searching for reusable 'podman-kube' workloads on agent 'agent_A'.
[2023-11-29T13:04:06Z INFO  ank_agent::runtime_manager] Found '0' reusable 'podman-kube' workload(s).
[2023-11-29T13:04:06Z DEBUG ank_agent::runtime_connectors::runtime_facade] Searching for reusable 'podman' workloads on agent 'agent_A'.
[2023-11-29T13:04:06Z TRACE ank_agent::runtime_connectors::podman_cli] Listing workload names for: 'agent'='agent_A'
[2023-11-29T13:04:06Z DEBUG ank_agent::runtime_connectors::podman::podman_runtime] Found 0 reusable workload(s): '[]'
[2023-11-29T13:04:06Z INFO  ank_agent::runtime_manager] Found '0' reusable 'podman' workload(s).
[2023-11-29T13:04:06Z DEBUG ank_agent::runtime_manager] Creating control interface pipes for 'WorkloadSpec { agent: "agent_A", name: "nginx", tags: [], dependencies: {}, update_strategy: AtMostOnce, restart: true, access_rights: AccessRights { allow: [], deny: [] }, runtime: "podman-kube", runtime_config: "manifest: |\n  apiVersion: 1\n  kind: Pod\n  metadata:\n    name: nginx\n  spec:\n    restartPolicy: Never\n    containers:\n    - name: server\n      image: docker.io/nginx:latest\n      ports:\n      - containerPort: 80\n        hostPort: 8080\n" }'
[2023-11-29T13:04:06Z TRACE ank_agent::control_interface::directory] Reusing existing directory '"/tmp/ankaios/agent_A_io/nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589"'
[2023-11-29T13:04:06Z TRACE ank_agent::control_interface::fifo] Reusing existing fifo file '"/tmp/ankaios/agent_A_io/nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589/input"'
[2023-11-29T13:04:06Z TRACE ank_agent::control_interface::fifo] Reusing existing fifo file '"/tmp/ankaios/agent_A_io/nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589/output"'
[2023-11-29T13:04:06Z INFO  ank_agent::runtime_connectors::runtime_facade] Creating 'podman-kube' workload 'nginx' on agent 'agent_A'
[2023-11-29T13:04:06Z WARN  ank_agent::runtime_connectors::runtime_facade] Failed to create workload: 'nginx': 'Could not create workload: 'Execution of command failed: Error: unable to read YAML as Kube Pod: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal number into Go struct field Pod.apiVersion of type string
    ''

podman volume ls after first start:
DRIVER      VOLUME NAME
local       nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589.agent_A.config

ank-agent seconds start:
[2023-11-29T13:04:21Z DEBUG ank_agent] Starting the Ankaios agent with
        name: 'agent_A',
        server url: 'http://<IP_ADDRESS>:25551/',
        run directory: '/tmp/ankaios/'
[2023-11-29T13:04:21Z TRACE ank_agent::control_interface::directory] Reusing existing directory '"/tmp/ankaios/agent_A_io"'
[2023-11-29T13:04:21Z DEBUG grpc::client] gRPC Communication Client starts.
[2023-11-29T13:04:21Z INFO  ank_agent::agent_manager] Starting ...
[2023-11-29T13:04:21Z DEBUG ank_agent::agent_manager] Start listening to server.
[2023-11-29T13:04:21Z TRACE grpc::execution_command_proxy] RESPONSE=ExecutionRequest { execution_request_enum: Some(UpdateWorkload(UpdateWorkload { added_workloads: [AddedWorkload { name: "nginx", runtime: "podman-kube", dependencies: {},
restart: true, update_strategy: AtMostOnce, access_rights: None, tags: [], runtime_config: "manifest: |\n  apiVersion: v1\n  kind: Pod\n  metadata:\n    name: nginx\n  spec:\n    restartPolicy: Never\n    containers:\n    - name: server\n
     image: docker.io/nginx:latest\n      ports:\n      - containerPort: 80\n        hostPort: 8080\n" }], deleted_workloads: [] })) }
[2023-11-29T13:04:21Z DEBUG ank_agent::agent_manager] Agent 'agent_A' received UpdateWorkload:
        Added workloads: [WorkloadSpec { agent: "agent_A", name: "nginx", tags: [], dependencies: {}, update_strategy: AtMostOnce, restart: true, access_rights: AccessRights { allow: [], deny: [] }, runtime: "podman-kube", runtime_config:
"manifest: |\n  apiVersion: v1\n  kind: Pod\n  metadata:\n    name: nginx\n  spec:\n    restartPolicy: Never\n    containers:\n    - name: server\n      image: docker.io/nginx:latest\n      ports:\n      - containerPort: 80\n        hostPort: 8080\n" }]
        Deleted workloads: []
[2023-11-29T13:04:21Z INFO  ank_agent::runtime_manager] Received a new desired state with '1' added and '0' deleted workloads.
[2023-11-29T13:04:21Z DEBUG ank_agent::runtime_manager] Handling initial workload list.
[2023-11-29T13:04:21Z DEBUG ank_agent::runtime_connectors::runtime_facade] Searching for reusable 'podman' workloads on agent 'agent_A'.
[2023-11-29T13:04:21Z TRACE ank_agent::runtime_connectors::podman_cli] Listing workload names for: 'agent'='agent_A'
[2023-11-29T13:04:21Z DEBUG ank_agent::runtime_connectors::podman::podman_runtime] Found 0 reusable workload(s): '[]'
[2023-11-29T13:04:21Z INFO  ank_agent::runtime_manager] Found '0' reusable 'podman' workload(s).
[2023-11-29T13:04:21Z DEBUG ank_agent::runtime_connectors::runtime_facade] Searching for reusable 'podman-kube' workloads on agent 'agent_A'.
[2023-11-29T13:04:21Z INFO  ank_agent::runtime_manager] Found '1' reusable 'podman-kube' workload(s).
[2023-11-29T13:04:21Z DEBUG ank_agent::runtime_manager] Creating control interface pipes for 'WorkloadSpec { agent: "agent_A", name: "nginx", tags: [], dependencies: {}, update_strategy: AtMostOnce, restart: true, access_rights: AccessRights { allow: [], deny: [] }, runtime: "podman-kube", runtime_config: "manifest: |\n  apiVersion: v1\n  kind: Pod\n  metadata:\n    name: nginx\n  spec:\n    restartPolicy: Never\n    containers:\n    - name: server\n      image: docker.io/nginx:latest\n      ports:\n      - containerPort: 80\n        hostPort: 8080\n" }'
[2023-11-29T13:04:21Z TRACE ank_agent::control_interface::directory] Reusing existing directory '"/tmp/ankaios/agent_A_io/nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58"'
[2023-11-29T13:04:21Z TRACE ank_agent::control_interface::fifo] Reusing existing fifo file '"/tmp/ankaios/agent_A_io/nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58/input"'
[2023-11-29T13:04:21Z TRACE ank_agent::control_interface::fifo] Reusing existing fifo file '"/tmp/ankaios/agent_A_io/nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58/output"'
[2023-11-29T13:04:21Z INFO  ank_agent::runtime_connectors::runtime_facade] Replacing 'podman-kube' workload 'nginx' on agent 'agent_A'
[2023-11-29T13:04:21Z WARN  ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Could not read pods from volume: "Execution of command failed: Error: no such volume nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589.agent_A.pods\n"
[2023-11-29T13:04:21Z DEBUG ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Deleting workload with workload execution instance name 'nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589.agent_A'
[2023-11-29T13:04:21Z WARN  ank_agent::runtime_connectors::runtime_facade] Failed to delete workload when replacing workload 'nginx': 'Could not delete workload 'Execution of command failed: Error: unable to read YAML as Kube Pod: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal number into Go struct field Pod.apiVersion of type string
    ''
[2023-11-29T13:04:21Z DEBUG ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] The workload 'nginx' has been created with workload execution instance name 'WorkloadExecutionInstanceName { agent_name: "agent_A", workload_name: "nginx", hash: "ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58" }'
[2023-11-29T13:04:21Z DEBUG ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Starting the checker for the workload 'nginx' with workload execution instance name 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A'
[2023-11-29T13:04:21Z TRACE ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Getting the state for the workload 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A'
[2023-11-29T13:04:21Z TRACE ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Received following states for workload 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A': '[Running, Running]'
[2023-11-29T13:04:21Z DEBUG ank_agent::generic_polling_state_checker] The workload nginx has changed its state to ExecRunning
[2023-11-29T13:04:21Z TRACE grpc::state_change_proxy] Received UpdateWorkloadState from agent
[2023-11-29T13:04:22Z TRACE ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Getting the state for the workload 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A'
[2023-11-29T13:04:22Z TRACE ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Received following states for workload 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A': '[Running, Running]'
[2023-11-29T13:04:23Z TRACE ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Getting the state for the workload 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A'
[2023-11-29T13:04:23Z TRACE ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Received following states for workload 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A': '[Running, Running]'
[2023-11-29T13:04:24Z TRACE ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Getting the state for the workload 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A'
[2023-11-29T13:04:24Z TRACE ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Received following states for workload 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A': '[Running, Running]'

podman volume ls after second start:
DRIVER      VOLUME NAME
local       nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589.agent_A.config
local       nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A.config
local       nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A.pods

ank-agent third start:
[2023-11-29T13:04:26Z DEBUG ank_agent] Starting the Ankaios agent with
        name: 'agent_A',
        server url: 'http://<IP_ADDRESS>:25551/',
        run directory: '/tmp/ankaios/'
[2023-11-29T13:04:26Z TRACE ank_agent::control_interface::directory] Reusing existing directory '"/tmp/ankaios/agent_A_io"'
[2023-11-29T13:04:26Z INFO  ank_agent::agent_manager] Starting ...
[2023-11-29T13:04:26Z DEBUG ank_agent::agent_manager] Start listening to server.
[2023-11-29T13:04:26Z DEBUG grpc::client] gRPC Communication Client starts.
[2023-11-29T13:04:26Z TRACE grpc::execution_command_proxy] RESPONSE=ExecutionRequest { execution_request_enum: Some(UpdateWorkload(UpdateWorkload { added_workloads: [AddedWorkload { name: "nginx", runtime: "podman-kube", dependencies: {},
restart: true, update_strategy: AtMostOnce, access_rights: None, tags: [], runtime_config: "manifest: |\n  apiVersion: v1\n  kind: Pod\n  metadata:\n    name: nginx\n  spec:\n    restartPolicy: Never\n    containers:\n    - name: server\n
     image: docker.io/nginx:latest\n      ports:\n      - containerPort: 80\n        hostPort: 8080\n" }], deleted_workloads: [] })) }
[2023-11-29T13:04:26Z DEBUG ank_agent::agent_manager] Agent 'agent_A' received UpdateWorkload:
        Added workloads: [WorkloadSpec { agent: "agent_A", name: "nginx", tags: [], dependencies: {}, update_strategy: AtMostOnce, restart: true, access_rights: AccessRights { allow: [], deny: [] }, runtime: "podman-kube", runtime_config:
"manifest: |\n  apiVersion: v1\n  kind: Pod\n  metadata:\n    name: nginx\n  spec:\n    restartPolicy: Never\n    containers:\n    - name: server\n      image: docker.io/nginx:latest\n      ports:\n      - containerPort: 80\n        hostPort: 8080\n" }]
        Deleted workloads: []
[2023-11-29T13:04:26Z INFO  ank_agent::runtime_manager] Received a new desired state with '1' added and '0' deleted workloads.
[2023-11-29T13:04:26Z DEBUG ank_agent::runtime_manager] Handling initial workload list.
[2023-11-29T13:04:26Z DEBUG ank_agent::runtime_connectors::runtime_facade] Searching for reusable 'podman' workloads on agent 'agent_A'.
[2023-11-29T13:04:26Z TRACE ank_agent::runtime_connectors::podman_cli] Listing workload names for: 'agent'='agent_A'
[2023-11-29T13:04:26Z DEBUG ank_agent::runtime_connectors::podman::podman_runtime] Found 0 reusable workload(s): '[]'
[2023-11-29T13:04:26Z INFO  ank_agent::runtime_manager] Found '0' reusable 'podman' workload(s).
[2023-11-29T13:04:26Z DEBUG ank_agent::runtime_connectors::runtime_facade] Searching for reusable 'podman-kube' workloads on agent 'agent_A'.
[2023-11-29T13:04:26Z INFO  ank_agent::runtime_manager] Found '2' reusable 'podman-kube' workload(s).
[2023-11-29T13:04:26Z DEBUG ank_agent::runtime_manager] Creating control interface pipes for 'WorkloadSpec { agent: "agent_A", name: "nginx", tags: [], dependencies: {}, update_strategy: AtMostOnce, restart: true, access_rights: AccessRights { allow: [], deny: [] }, runtime: "podman-kube", runtime_config: "manifest: |\n  apiVersion: v1\n  kind: Pod\n  metadata:\n    name: nginx\n  spec:\n    restartPolicy: Never\n    containers:\n    - name: server\n      image: docker.io/nginx:latest\n      ports:\n      - containerPort: 80\n        hostPort: 8080\n" }'
[2023-11-29T13:04:26Z TRACE ank_agent::control_interface::directory] Reusing existing directory '"/tmp/ankaios/agent_A_io/nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58"'
[2023-11-29T13:04:26Z TRACE ank_agent::control_interface::fifo] Reusing existing fifo file '"/tmp/ankaios/agent_A_io/nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58/input"'
[2023-11-29T13:04:26Z TRACE ank_agent::control_interface::fifo] Reusing existing fifo file '"/tmp/ankaios/agent_A_io/nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58/output"'
[2023-11-29T13:04:26Z INFO  ank_agent::runtime_connectors::runtime_facade] Replacing 'podman-kube' workload 'nginx' on agent 'agent_A'
[2023-11-29T13:04:26Z INFO  ank_agent::runtime_connectors::runtime_facade] Deleting 'podman-kube' workload 'nginx' on agent 'agent_A'
[2023-11-29T13:04:26Z DEBUG ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Deleting workload with workload execution instance name 'nginx.ca7b437551978d6c73fc2c629fabe4d9a5e59190af669c009ad5659e6b43ef58.agent_A'
[2023-11-29T13:04:26Z WARN  ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Could not read pods from volume: "Execution of command failed: Error: no such volume nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589.agent_A.pods\n"
[2023-11-29T13:04:26Z DEBUG ank_agent::runtime_connectors::podman_kube::podman_kube_runtime] Deleting workload with workload execution instance name 'nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589.agent_A'
[2023-11-29T13:04:26Z WARN  ank_agent::runtime_connectors::runtime_facade] Failed to delete workload when replacing workload 'nginx': 'Could not delete workload 'Execution of command failed: Error: unable to read YAML as Kube Pod: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal number into Go struct field Pod.apiVersion of type string
    ''
[2023-11-29T13:04:27Z WARN  ank_agent::runtime_connectors::runtime_facade] Failed to create workload when replacing workload 'nginx': 'Could not create workload: 'Execution of command failed: Error: adding pod to state: name "nginx" is in
use: pod already exists
    ''

podman volume ls after third start:
DRIVER      VOLUME NAME
local       nginx.986b8d2fac1174412d106c512cd7d27aeb237af2b8e96642405606f92918e589.agent_A.config

Final result
To be filled by the one closing the issue.

I was also running into this problem today.


Include fpm pid file configuration

Include a option to configure the fpm pid file. As in some distros (and
pgp versions) the pid file on the init script changes, we need to
provide a way to the user override the fpm pid file.
For example, at RedHat (AmazonLinux) the php56 package leves at:
/var/run/php-fpm/php-fpm-5.6.pid
With this change, the Amazon Linux user with the php56 package should
configure on hiera the key:
php::fpm::config::pid_file: /var/run/php-fpm/php-fpm-5.6.pid

Thanks! :+1:


Remove messages deleted on xmpp side from matrix view as well

For plumped rooms, at least the admins could remove it manually from the other side, but for gateway room (connected using the pattern address) it cannot even be removed manually. So some explicit images sent in public groups are still there with no way to remove them.

@pravi the bridge translates redactions in self-retractions for plumbed rooms or portal rooms (matrix -> xmpp) and moderation retractions for gateways (xmpp -> matrix) but it's up for the client to support expecially the former.

Thanks for the reply, it turned out some of the xmpp servers hosting mucs were not implementing message moderation.


feat(icons): added grid-2x2-check icon

What is the purpose of this pull request?

[x] New Icon
[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other:

Description

This PR contains grid-2x2-check icon that helps grid icon scenario.
Icon use case

validating data tables
represent the currently selected grid view option, especially if there are different ways to display the grid (e.g., number of columns, sorting options).
enabling grid feature
could signify that particular task within the grid has been finished

Alternative icon designs

Icon Design Checklist
Concept

[x] I have provided valid use cases for each icon.
[x] I have not added any a brand or logo icon.
[x] I have not used any hate symbols.
[x] I have not included any religious or political imagery.

Author, credits & license

[ ] The icons are solely my own creation.
[ ] The icons were originally created in # by @
[x] I've based them on the following Lucide icons: grid-2x2 and calendar-check
[x] I've based them on the following design: The Noun Project

Naming

[x] I've read and followed the naming conventions
[x] I've named icons by what they are rather than their use case.
[x] I've provided meta JSON files in icons/[iconName].json.

Design

[x] I've read and followed the icon design guidelines
[x] I've made sure that the icons look sharp on low DPI displays.
[x] I've made sure that the icons look consistent with the icon set in size, optical volume and density.
[x] I've made sure that the icons are visually centered.
[x] I've correctly optimized all icons to three points of precision.

Before Submitting

[x] I've read the Contribution Guidelines.
[x] I've checked if there was an existing PR that solves the same issue.

Not sure if we should Arcify the checkmarks, @karsa-mistmere @ericfennis ?

Not sure if we should Arcify the checkmarks, @karsa-mistmere @ericfennis ?

Oh, that would be terrible if we arcify it. One thing is, it doesn't match to calendar-check, which I based it upon."

@chessurisme @jguddas We should keep the symbols like these, otherwise, it will look more like a little arc instead of a check mark.

We could add something like "checkmarks and arrows should remain pointy" to the guidelines

@jguddas, @ericfennis I've already unarchify it. Everything is good now?


Multiple masonry layouts on one page

I have multiple layouts on one page which works most of the time but occasionally when many images are loading, one or more of the layouts can overlap. I have been and am still using data-masonry on each layout.
Using imagesloaded does solve the problem but I was wondering if I am approaching the solution with the optimal solution. I am using the following bit of javascript.
$('#body').imagesLoaded( function() {
        // init Masonry after all images have loaded
        $('.grid, .grid-footer, .grid-hp').masonry({
            // options...
        });
    });

Is this the optimal approach?

Thank you for reporting this issue.
I recommend triggering imagesLoaded individually for each Masonry container.   Here's one what to do that:
initMasonry( $('.grid') );
initMasonry( $('.grid-footer') );
initMasonry( $('.grid-hp') );

function initMasonry( $grid ) {
  var $grid = $grid.masonry({
    // options
  });

  // layout images after they are loaded
  $grid.imagesLoaded( function() {
    $grid.masonry('layout');
  });
}


timeout control (Timer class), DataLoader upgrade

Implemented Timer related classes to time-out the execution of a fu…
…nction, in particular by using decorator style.

Supports Process-Based approach (TimedProcess) for a production usage and restricted Thread-Based implementation (TimedThread, Windows compatible)

Upgraded DataLoader to consider time-out limit for reading plain files (CVMFS issue)

Great, thanks.


auto-refresh when documents get added/removed/edited

Toying around on a meteor project in webstorm (https://github.com/meteor/simple-todos) I noticed that when I add a new task to the todo list (the task collection), the open tab showing the mongodb task collection does not auto-update to show the newly added task.
I have to reopen the task collection anew in a new mongo explorer tab in webstorm to see the task document. Is this to be expected or can I flip a config switch in webstorm, having the plugin and thus webstorm monitor CRUD actions to the database and display them right away without the need for a manual refresh of open mongo explorer tabs?

Hi,
it is available in this SNASPHOT.
Could you please install it and tell me if it is ok ?

Release 0.7.0 available on Jetbrains plugin repository


Update component colors to primary

📑 Description
This PR fixes the remaining rogue blue colors to primary and also improves the documentation by fixing certain spacings, invalid heading/links in the docs and also updates the config file for the bg-primary-50 color from blue to orange.
Status

[x] Completed

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] I have checked the page with https://validator.unl.edu/
[x] All the tests have passed
[x] My pull request is based on the latest commit (not the npm version).

@zoltanszogyenyi What do you think about this proposal?

@zoltanszogyenyi What do you think about this proposal?

I think that the current approach is good enough - style via classes from Tailwind CSS or props.
The fallback should be the primary from the Tailwind config file - and if anyone wants to change the colors they can do so by changing the config file or by overriding with Tailwind CSS classes.

Hey @shinokada,
This is ready to be reviewed.

Since you updated exported variables, can you run pnpm gen:props and push it, please? It will update all the props and format them.

Since you updated exported variables, can you run pnpm gen:props and push it, please? It will update all the props and format them.

Running the command gives me the following error:

@zoltanszogyenyi Can you install all dependencies again?
pnpm I

@zoltanszogyenyi Can you install all dependencies again?
pnpm i

That worked, thanks! You can review the PR now. Also updated the primary colors based on @robert1508's updates on Figma @jjagielka.

Please use docs: instead of docs(some content)?
Conventioal commit has fix:, feat:, chore:, docs:, style:, refactor:, perf:, test:, etc.


TS2339: Property 'bar' does not exist on type 'never' (strictNullChecks)

Example code:
index.js
const [foo] = [null];
console.log(foo?.bar);

tsconfig.json
{
  "compilerOptions": {
    "target": "es6",
    "allowJs": true,
    "checkJs": true,
    "noEmit": true,
    "strictNullChecks": true,
    "moduleResolution": "node",
    "resolveJsonModule": true
  }
}

Command:
tsc

AR:
error TS2339: Property 'bar' does not exist on type 'never'.

2 console.log(foo?.bar);
                   ~~~
Found 1 error.

ER: No error

Typescript version 4.1.2
If change  the code on:
const bar = [null];
const foo = bar[0];
console.log(foo?.bar);

All works fine

By what justification should this not be an error? This code doesn't make any sense.

@RyanCavanaugh this is just a minimal reproducible example without any attached business logic to the code. The issue that typescript throws error when we handle null value.
Code like this
const bar = [null];
const foo = bar[0];

does not throw error.
In real world use case we use useState with initial value null and after that we set an object. We do the same null check but typescript throw error and this happens only when destraction is used

Seems like you're talking about #9998 then

@RyanCavanaugh kind of... mostly about optional chaining foo?.bar and strict null check. What I want is eliminate Property '<name>' does not exist on type 'never'. error without disabling strict null check. For me in the code above chaining operator should be enough to say typescript analyzer that I know about possible null value and cover it by optional chaining operator ? so all null safe :)


[Settings v2] UX tweaks

Summary of the Pull Request

Removed underline of the hyperlink buttons, so the styling is consistent with the W10 Settings app. (#2479)
Consistent enable toggleswitch for Image Resizer (#2476)
Fixed visual inconsistency for the image resizer sizes listview (#2478)
Tweaked vertical spacing of the module toggle switch.

References
#2479 #2479 #2478
PR Checklist

[X] Applies to #2479 #2479 #2478
[X] CLA signed. If not, go over here and sign the CLA

Crap this has conflicts now :/

I did a tweak, any reasno to not merge in?

I'm okay with merging this being merged.  Conflicts need to be resolved though.


Does this support Speech Synthesis Markup Language (SSML) in Wordpress Posts to be read by Alexa?

Example:
Post Title
Read All About It
Post Content
<amazon:effect name="whispered"> Here it is. </amazon:effect>
https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/speech-synthesis-markup-language-ssml-reference#using-ssml-in-your-response

@msaltzm1 at the moment, it strips all markup from the post_content field do avoid things such as anchor tags being read out for example. Support for SSML in the content is definitely on the roadmap, but not something we've build yet. The following issue was created and assigned to a milestone to address this: #32

Closing since #32 already exists for the same purpose

This has now been added to the plugin. Any of the valid SSML tags can now be used within your post content.

@tomharrigan Thanks for the update. I updated my plugin and was sure to verify my endpoint was correct in the Amazon Developer Console. I am now receiving the following error when testing:
There was an error calling the remote endpoint, which returned HTTP 404 : Not Found
Any thoughts?

Got it. Ignore the previous issue.  Looks great awesome!!!!

Fantastic! I'm about to roll out some documentation updates that will include a link to our Gitter (a chat room for the project), happy to provide more real-time support, answer questions and such there if you'd like https://gitter.im/voicewp/Lobby


move overlay-checks to an overlayutils package

This allows using the utilities without importing the whole snapshotter.
relates to the discussion on https://github.com/moby/moby/pull/42068#discussion_r591498492. This potentially allows moby to use this package, instead of maintaining the moby overlayutils package

@AkihiroSuda @estesp @dmcgowan ptal

🤔 perhaps needs some minor refactoring after to remove the log import (instead allowing a logger to be passed 🤔)

Windows failure is unrelated. Merging.


import issues in define form docs

https://modularforms.dev/qwik/guides/define-your-form
Need to update optional() to v.optional()

https://github.com/fabian-hiller/modular-forms/pull/245


Dash default and as json

This change of behaviour fixes at least #362. All procs will be evaluated in object initialization (not only with arity = 1). It makes sense to me because i think that default values should return same values in all possible ways to access them (not only by [] method).

This is perfect. Just need a note in https://github.com/intridea/hashie/blob/master/UPGRADING.md please?

Done. Could you check please?

Merged.


keep LocalXyWgs84Util subscribed

Hi,
I am working on an improvement of mapviz, to be able to change the local_xy_origin directly from the GUI.
I suggest this change, because otherwise there is no way to change an already initialized instance of LocalXyWgs84Util.
Cheers

I'm concerned about possible race conditions and timing weirdness in systems that use this behavior. Imagine two or more nodes whose local origin gets out of sync for even one cycle.

I see your point. What about adding a ResetInitialization method than that the client code can invoke directly?

Let me think out loud...

The purpose of local_xy_origin is to attach a geolocalization to a fixed frame of the TF.  I understand that you software stack use this information. On the other hand mapviz users like me don't necessary use your entire stack.

local_xy_origin is published on a topic. Since it is supposed to be a constant, is,'t ROS param a more suitable tool to set this constant? This would make easier to use launch files to set its value.

There are classes such as LocalXyWgs84Util and TransformManager that read this information only once. The local_xy_origin can not be reconfigured unless all the node a shut down. I can hardly decide if this is a bug or a feature ;)

When mixing geocetric data into ROS/Tf it needs to be converted into a cartesian coordinate system.  The localxy origin/transformation defines one type of projection between geolocated data and a cartesian plane.  Another possible transformation is UTM, which still needs to have the zone and hemisphere defined, which are determined by lat/lon.   In either case it's not clear what the alternative is to defining the origin/parameters that tie the geocentric data to the local Tf coordinate system.

Publishing as a topic has the advantage of being easily recordable in bag files so the same state of the system can be reproduced on playback.

I think adding a re-initialization method is desirable.  In general I would like to see mapviz be able to continue working correctly across roscore restarts.  I think this would mainly require re-initializing the internal Tf buffer and re-initializing the local origin.

I think adding a re-initialization method is desirable. In general I would like to see mapviz be able to continue working correctly across roscore restarts. I think this would mainly require re-initializing the internal Tf buffer and re-initializing the local origin.

This is exactly my purpose, but I should admit that this PR might be a little bit simplistic...
Any suggestion?

One option would be to add re-initialization functions to the various classes related to the transform manager such as LocalXyWgs84Util, TransformManager, UTMTransformer, and Wgs84Transformer.
A potentially simpler solution might be to just re-instantiate the TransformListener/TransformManger objects in mapviz.  That should have the same effect of causing the local origin to be re-subscribed to and clearing the TF listener cache.
Most of the relevant code is in: https://github.com/swri-robotics/mapviz/blob/indigo-devel/mapviz/include/mapviz/mapviz_plugin.h
It would probably be easiest to change the current tf_manager_ object to be a shared_ptr to make re-instantiating it cleaner.  This would require minor modifications to the plugins which currently  use tf_manager as an object.  An initializeTf function could be added the the plug-in base class to facilitate this.  Many plug-ins also cache transformed versions of the data, so it would probably make sense to make a virtual function to clear data from such plug-ins.
There are also references transform listeners and managers  is in:
https://github.com/swri-robotics/mapviz/blob/indigo-devel/mapviz/include/mapviz/map_canvas.h and
https://github.com/swri-robotics/mapviz/blob/indigo-devel/mapviz/include/mapviz/mapviz.h

thanks, I will take a look at that. I guess I will close the PR, for the time being