lastpass shows up on the bottom of the screen

Electron version:
chromium-54
Operating system:
Linux

/home/posi/brave/browser-laptop-bootstrap/src/out/Release/brave --user-data-dir=brave-development --enable-logging --v=0 /home/posi/brave/browser-laptop-bootstrap/src/browser-laptop
[26840:26840:1206/161323:ERROR:browser_main_parts.cc(173)] Could not set linux app data path
(node:26840) DeprecationWarning: Using Buffer without `new` will soon stop working. Use `new Buffer()`, or preferably `Buffer.from()`, `Buffer.allocUnsafe()` or `Buffer.alloc()` instead.
Crash reporting enabled
(node:26840) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:26840) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
[26840:26840:1206/161326:ERROR:extension_function_dispatcher.cc(613)] Unknown Extension API - permissions.contains
[26840:26840:1206/161346:ERROR:CONSOLE(19)] "Uncaught TypeError: The first argument is the receiver and must be an object", source: extensions::SafeBuiltins (19)
[26840:26840:1206/161346:ERROR:CONSOLE(19)] "Uncaught TypeError: The first argument is the receiver and must be an object", source: extensions::SafeBuiltins (19)
[26840:26840:1206/161353:ERROR:CONSOLE(19)] "Uncaught TypeError: The first argument is the receiver and must be an object", source: extensions::SafeBuiltins (19)
[26840:26840:1206/161353:ERROR:CONSOLE(19)] "Uncaught TypeError: The first argument is the receiver and must be an object", source: extensions::SafeBuiltins (19)
WARNING: requesting non-HTTPS URL http://johnkalberer.com/favicon.ico

also happens on mac

permission.contains error is fixed in fd6561a8a2355857f
but on the bottom problem still exists

@darkdh we are behind on the version of LastPass, just FYI
Per discussion on Slack in #extensions, version 4.1.34 is available but we are on 4.1.28. @bbondy will be updating them soon :smile:


Add ability to delete fee payments through frontend for system admins

Ticket https://myaegee.atlassian.net/browse/MA-68

@WikiRik I made the modal wider if there is the table in the content field of the modal. I also added the name of the person that you are doing something for in the title, but that might get cut off if the content is again empty

:tada: This PR is included in version 1.42.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


New sozluk term: JWT

add-jwt-sozluk-term
Description
Please describe your changes. Be descriptive enough to reduce churn for review process.
Checklist

[ ] discord username: username#0001
[ ] Closes #
[ ] PR must be created for an issue from issues under "In progress" column from our project board.
[ ] A descriptive and understandable title: The PR title should clearly describe the nature and purpose of the changes. The PR title should be the first thing displayed when the PR is opened. And it should follow the semantic commit rules, and should include the app/package/service name in the title. For example, a title like "docs(@kampus-apps/pano): Add README.md" can be used.
[ ] Related file selection: Only relevant files should be touched and no other files should be affected.
[ ] I ran npx turbo run at the root of the repository, and build was successful.
[ ] I installed the npm packages using npm install --save-exact <package> so my package is pinned to a specific npm version. Leave empty if no package was installed. Leave empty if no package was installed with this PR.

How were these changes tested?
Please describe the tests you did to test the changes you made. Please also specify your test configuration.

add-jwt-sozluk-term
Description
Please describe your changes. Be descriptive enough to reduce churn for review process.
Checklist

[ ]  discord username: username#0001
[ ]  Closes #
[ ]  PR must be created for an issue from issues under "In progress" column from our project board.
[ ]  A descriptive and understandable title: The PR title should clearly describe the nature and purpose of the changes. The PR title should be the first thing displayed when the PR is opened. And it should follow the semantic commit rules, and should include the app/package/service name in the title. For example, a title like "docs(@kampus-apps/pano): Add README.md" can be used.
[ ]  Related file selection: Only relevant files should be touched and no other files should be affected.
[ ]  I ran npx turbo run at the root of the repository, and build was successful.
[ ]  I installed the npm packages using npm install --save-exact <package> so my package is pinned to a specific npm version. Leave empty if no package was installed. Leave empty if no package was installed with this PR.

How were these changes tested?
Please describe the tests you did to test the changes you made. Please also specify your test configuration.

İlk defa PR açtığını görüyorum süpersin 👌
Senden ricam o todo listte PRın için geçerli yerleri doldurman. Özellikle discord username 😄


Group 6 Final Submission

This is not our final. We will submit a new one before class.

Our suggested distribution is our own: Team 6 medium distribution for both task difficulty and abilities.


StandardMerkleTree.of  Added support for more data types in solidity

describe('openzeppelin/merkle-tree test object', () => {
    // (1)
    const vs = [
        ["0x80000001677f23a227dfed6f61b132d114be83b8ad0aa5f3c5d1d77e6ee0bf5f73b0af750cc34e8f2dae73c21dc36f4a", "32000000000000000000", "1"],
        ["0x800003d8af8aa481646da46d0d00ed2659a5bb303e0d88edf468abc1259a1f23ccf12eaeaa3f80511cfeaf256904a72a", "33000000000000000000", "2"],
        ["0x800006d4b1026b6149168b342e6883d48ede9539202cc414448b1b796394440a5401e8d6620e65d7c77654bf1db199b1", "34000000000000000000", "3"],
    ];

    const tree = StandardMerkleTree.of(vs, ["bytes", "uint256", "uint256"]);

    console.log('Merkle Root:', tree.root);

    test('merkle object root', () => {
        expect(tree.root).toBe("0xa934c462ec150e180a501144c494ec0d63878c1a9caca5b3d409787177c99798");
    });

    test('merkle object verify', () => {
        for (const [i, v] of tree.entries()) {
            if (v[0] === '0x80000001677f23a227dfed6f61b132d114be83b8ad0aa5f3c5d1d77e6ee0bf5f73b0af750cc34e8f2dae73c21dc36f4a') {
                // (3)
                const proof = tree.getProof(i);
                console.log('Value:', v);
                console.log('Proof:', proof);
            }
        }

        let leafHash = tree.leafHash(["0x80000001677f23a227dfed6f61b132d114be83b8ad0aa5f3c5d1d77e6ee0bf5f73b0af750cc34e8f2dae73c21dc36f4a", "32000000000000000000", "1"]);
        console.log('leafHash:', leafHash);

    });
});

The above code test can pass
But if you
const tree = StandardMerkleTree.of(vs, ["bytes", "uint256", "uint256"]);

Replace with:
const tree = StandardMerkleTree.of(vs, ["bytes32", "uint128", "uint32"]);

那么将会报错：
 Test suite failed to run

    incorrect data length (argument=null, value="0x80000001677f23a227dfed6f61b132d114be83b8ad0aa5f3c5d1d77e6ee0bf5f73b0af750cc34e8f2dae73c21dc36f4a", code=INVALID_ARGUMENT, version=abi/5.7.0)

The data type of bytes32 is not supported

Currently, the method similar to array nested array is supported
const vs = [
        [
            "0x80000001677f23a227dfed6f61b132d114be83b8ad0aa5f3c5d1d77e6ee0bf5f73b0af750cc34e8f2dae73c21dc36f4a",
            "32000000000000000000",
            "1",
        ],
        [
            "0x800003d8af8aa481646da46d0d00ed2659a5bb303e0d88edf468abc1259a1f23ccf12eaeaa3f80511cfeaf256904a72a",
            "33000000000000000000",
            "2",
        ],
        [
            "0x800006d4b1026b6149168b342e6883d48ede9539202cc414448b1b796394440a5401e8d6620e65d7c77654bf1db199b1",
            "34000000000000000000",
            "3",
        ],
    ];

Can it support the form of an array nested object
[
        {age: 1, name: "Job"},
        {age: 2, name: "Zh"},
        {age: 3, name: "Ha"},
]

bytes32 is supported, but your input is not a valid bytes32.
Bytes32 are expected to be 32 bytes, so 64 chars long in hex format (66 with the 0x prefix)
0x80000001677f23a227dfed6f61b132d114be83b8ad0aa5f3c5d1d77e6ee0bf5f73b0af750cc34e8f2dae73c21dc36f4a is too big to be a valid bytes32.

Can it support the form of an array nested object
[
        {age: 1, name: "Job"},
        {age: 2, name: "Zh"},
        {age: 3, name: "Ha"},
]

We support all the types that Ethers.js supports. You could use objects like this if you specify a type tuple(uint age, string name), but note that you still need to pass each value as an array.
StandardMerkleTree.of([
  [{ age: 1, name: 'Job' }],
  [{ age: 2, name: 'Zh' }],
], ['tuple(uint age, string name)']);

I am not sure what this will correspond to in the Solidity side for computing the leaf.


Pass promise returning disposer to Promise.using

Right now, Promise.using accepts only Disposer instances but not promises that resolve to disposers.
For example in this code:
createTmp = function() {
	return tmp.fileAsync()
	.disposer( function( tmp ) {
		cleanup = tmp[2];
		cleanup();
	} );
};

createTmpDelayed = function() {
	return Promise.delay(1000)
	.then( function() {
		return createTmp();
	} );
};

passing createTmpDelayed() to Promise.using has a different outcome than passing createTmp().
This is not expected, as usually the bluebird API allows passing promises resolving to instances of a class, when the function expects a specific class. For example, .bind allows to pass promises that will be resolved to the object that will be binded.
Also, there is no way currently to write createTmpDelayed in such a way so as to transform the promise into a disposer.
createTmpDelayed = function() {
	return Promise.delay(1000)
	.then( function() {
		return createTmp();
	} ).dispose( function(disposer) {
		disposer.dispose(); // no such documented function
	} );
};

This makes it impossible to make generic functions that return Promises that resolve to disposers.

You are awesome! Thanks for quick fix!


provide_any causes fail in stable channel

Cargo.toml:
[package]
name = "this_error_bug"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
thiserror = "1.0"

main.rs:
fn main() {
    println!("Hello, world!");
}

action:
cargo build

output:
error[E0554]: `#![feature]` may not be used on the stable release channel
   --> C:\Users\kkolyan\.cargo\registry\src\github.com-1ecc6299db9ec823\thiserror-1.0.37\src\lib.rs:238:34
    |
238 | #![cfg_attr(provide_any, feature(provide_any))]
    |                                  ^^^^^^^^^^^

Duplicate of #192.

Maybe this issue should be pinned?
Quick fix - cargo clean


logging sample seems to be a lot harder than it should be...

Refresh sample, it shouldn't need paging anymore, just a single loop.
It seems way harder than it should be.

Related #826 , #830


Support Deno

Description
Hey everyone, thank you for the wonderful package!
Just wondering if there are any plans to support other runtimes than nodejs, more specifically Deno.
Thanks!

Hey @AlaaZorkane, thanks for the message! I haven't looked into it yet and not opposed at all, but it depends on demand. The current focus are upcoming clients. Are you able to outline what changes would roughly need to happen in order to support Deno?

ping @AlaaZorkane

Hey, I just started to try this lib out, its awesome! One thing that Deno requires is the file extension for imports, so teh current generated files will error out simply because they are missing the .ts extension in the import from statements.
Is there any current options with the configuration API to add the extension when generating files?

@bombillazo That's nice to hear! There were no direct attempts at making this compatible with Deno yet. Might prioritise soon... you can use my sponsors page for list of current priorities before there's a proper roadmap https://github.com/sponsors/mrlubos

On the way to support Deno, I opened this PR to help
#936

@bombillazo @mrlubos @AlaaZorkane Maybe what's needed is to create a Deno client, if that is a thing? That would resolve the issue to determine how to change the generated code (especially on the import), and maybe allow to generate a Deno workspace where the current index.ts file would be renamed mod.ts and a deno.json file would be generated alongside the code with a simple:
{
  "name": "@scope/openapi",
  "version": "0.0.1",
  "exports": "./mod.ts"
}


Fatal Python error:

I run into the following error when enabling the integration test plugin on Windows 7.
Fatal Python error: Failed to initialize Windows random API (CryptoGen)
[INFO]  Executed 1 integration tests
I am using Python 3.4

Please attach full debug log (pyb -X)

Thank you. Below is the full debug log.
[ERROR] Integration test failed: C:/XXXX/run_opt_tests.py
File C:/XXXX/run_opt_tests.py
File C:\XXXX\run_opt_tests.err:
Traceback (most recent call last):
Fatal Python error: Failed to initialize Windows random API (CryptoGen)
File "C:\Anaconda\envs\py34an2_3_0\lib\site-packages\pybuilder\cli.py", line 403, in main
[INFO]  Executed 1 integration tests.
environments=options.environments, tasks=arguments)
File "C:\Anaconda\envs\py34an2_3_0\lib\site-packages\pybuilder\reactor.py", line 128, in build
BUILD FAILED - 1 of 1 integration tests failed.
return self.build_execution_plan(tasks, execution_plan)
Build finished at 2016-11-02 15:24:11
File "C:\Anaconda\envs\py34an2_3_0\lib\site-packages\pybuilder\reactor.py", line 170, in build_execution_plan
reactor=self)
File "C:\Anaconda\envs\py34an2_3_0\lib\site-packages\pybuilder\execution.py", line 351, in execute_execution_plan
Build took 112 seconds (112647 ms)
summaries.append(self.execute_task(task, **keyword_arguments))
File "C:\Anaconda\envs\py34an2_3_0\lib\site-packages\pybuilder\execution.py", line 298, in execute_task
task.execute(self.logger, keyword_arguments)
File "C:\Anaconda\envs\py34an2_3_0\lib\site-packages\pybuilder\execution.py", line 169, in execute
executable.execute(argument_dict)
File "C:\Anaconda\envs\py34an2_3_0\lib\site-packages\pybuilder\execution.py", line 100, in execute
self.callable(*arguments)
File "C:\Anaconda\envs\py34an2_3_0\lib\site-packages\pybuilder\plugins\python\integrationtest_plugin.py", line 62, in run_integration_tests
reports_processor.write_report_and_ensure_all_tests_passed()
File "C:\Anaconda\envs\py34an2_3_0\lib\site-packages\pybuilder\plugins\python\test_plugin_helper.py", line 54, in write_report_and_ensure_all_tests_passed
raise BuildFailedException("%d of %d integration tests failed." % (self.tests_failed, self.tests_executed))
pybuilder.errors.BuildFailedException: 1 of 1 integration tests failed.

http://bugs.python.org/issue20614
On Windows, if Python is started with an empty environment (no environment variable at all), Python fails with:

"Fatal Python error: Failed to initialize Windows random API (CryptoGen)"

It's the Windows error 0x80090006 which is not displayed in the error message :-(

In fact, it's because Python 3 cannot be started without SYSTEMROOT environment variable. Otherwise, CryptAcquireContext() is unable to find some DLL.

IMO the script_helper should be fixed to copy the variable.

Thank you Arcadiy. I read the link above and your reply, but still not too sure what I should do to resolve the issue. Could you please explain a bit more in terms of what I should do? I don't see the script_helper anywhere in the link. Really appreciate your help on this.

What version of PyB are you using?

I'm using 0.11.9

@jljs bump

https://github.com/pybuilder/pybuilder/blob/ff540b75b7feffc51684b2cbc9f76f1eb39ba02/build.py#L156


Device name changes to 'nimble' after pairing

Hi,
I am using a variation of the example code provided for the BLE Keyboard.  What I noticed is that my device gets advertised with the name I define with the following:
let device = BLEDevice::take();
// ...
let ble_advertising = device.get_advertising();
ble_advertising.name("ESP32 Keyboard")
//...

However after pairing the name on the client side changes to 'nimble'.
This happens on my Linux laptop and on my Android phone. For the FireTV Cube the name stays as advertised.
Any idea what could cause this?
Thanks in advance for any pointers,
schaze

Ok, I searched the whole day for this and 10 minutes after opening the issue I find the solution...
I simply hat to set the actual device name beforehand as well via:
        BLEDevice::set_device_name("my device name").unwrap();


Wider strokePath for smaller circles

I've been playing with the examples in JSFiddle for a while now and I can't find a good balance between making the circle smaller and keeping a thicker/wider strokePath.
Is there a way to manually override the stroke path in CSS or some options I haven't found in the official docs? I'm trying to use circles that are around 45px width and height, but the stoke path becomes extremely narrow at that size.

The stoke width is always a percent value relative to the size of svg canvas element. You can find more from svg specification.
Did you already try the strokeWidth option for progressbar? Some svg properties are possible to edit with css but I'm not sure if stroke-width is one of them.

Apparently there is a stroke-width css property, but I didn't have much luck getting it to update the width of the ProgressBar strokes, maybe because the script is loaded in after and overrides any CSS value? Not sure.
Either way, I believe the problem I was having is when using the ProgressBar.Circle text property. If I don't use it, then I'm able to have a small circle with a wide stroke and it works great, but if I add the text property back in, it seems to really throw off the scaling.
I can always just use my own text options though.
Thanks for the response!

The text option shouldn't affect the strokeWidth in any way.
This works fine for me:
var circle = new ProgressBar.Circle('#container', {
    color: '#FCB03C',
    strokeWidth: 10,
    text: {
      value: 'test'
    }
});

You can also modify the value with CSS like this, where #container is the container which you use when initializing ProgressBar instance.
#container > svg > path:last-child {
  stroke-width: 2;
}

You can read more about the HTML structure ProgressBar.js is generating in here: http://progressbarjs.readthedocs.io/en/latest/api/general/#html-structure
You can consider this DOM structure quite safe to be relied on. I'll bump the major version if the generated DOM structure will change.

Thanks! Very helpful. Not sure how I missed that in the docs.

To make use of the "text" option, do I only need to add:
text: {       value: 'test'     }
If your above example it seems that is the case, but when I only add that, I have no change to my circles.
I used this from the docs:
var circle = new ProgressBar.Circle('#example-percent-container', {     color: '#FCB03C',     strokeWidth: 3,     trailWidth: 1,     text: {         value: '0'     } });
But I don't even get the  tag in my DOM when I inspect the circle.


Pages served from page cache have X-Frame-Options set to Same-Origin

Fixed by https://github.com/divio/django-cms/pull/6368


Parcel with Rust fails to write to cache if paths have spaces

🐛 bug report
When building a rust project, if there are spaces in the path parcel fails with the following error where the path was /path/with spaces in it/. Note: this is not a fatal error, it just logs to the console. Everything else still seems to work.
Previous discussion here: parcel-bundler/parcel#2521
✨  Built in 1.72s.
🚨  Error writing to cache: ENOENT: no such file or directory, stat '/path/with\'

🔦 Context
To reproduce:

get the rust parcel template
place it in a path with spaces in it
run npm run start or npm run build

🤔 Expected Behavior
Parcel should properly build a bundle.
😯 Current Behavior
Parcel complains about writing to the cache with the error above.
💁 Possible Solution
Properly handle paths with spaces (and special characters) in them.
🌍 Your Environment

Software
Version(s)

Parcel
1.11.0

Node
8.14.0

npm
6.5.0

Operating System
macOS 10.13.6

Sorry for the late fix. Version 1.2.10 solve this issue.


vector compare instruction overlap constraint

In current spec, resource & destination group overlap constraint is not applied to vector mask compare instruction.
But when vmseq.vv v11, v10, v2 and lmul >1, v11 may be updated before vs2 read.
Why this overlap constraint is not applied to vector compare instruction ?

The last statement in section 12.7 is:
For all comparison instructions, an illegal instruction exception is raised if the destination vector register overlaps a source vector register group and LMUL > 1.
So I think this constraint is applied.


say does not speak Chinese with the right pronunciation

Hello, The Chinese words '你好' should be pronunced 'ni hao'. But when I try this on windows 10
const Say = require('say').Say;
const say = new Say('win32');
say.speak('你好');

It says something sounds like 'huan chai' to me.
Is that a problem or should I install some more plug-in? Thanks.

Actually, nodejs encode string as utf-8 as default, so as say.js. But it seems that platform like win32 decodes it as GBK.
To fix this problem, I forked this repository, and add setEncoding method for Say Class.
You can setEncode('gbk') before speak.
Here is an example.

Actually, nodejs encode string as utf-8 as default, so as say.js. But it seems that platform like win32 decodes it as GBK.
To fix this problem, I forked this repository, and add setEncoding method for Say Class.
You can setEncode('gbk') before speak.
Here is an example.

Thanks for your idea, although I failed to act in your way, as the code doesn't know the 'gbk' code.
However, I worked this out with the encoding package 'iconv-lite' with your guidance. A new solution could be found in my repository, which can be an optional way for the other guys.

The fix can be as simple as setting the command = 'chcp 65001 >NUL & powershell' instead of 'powershell' in the file win32.js. See https://stackoverflow.com/questions/68988696/set-utf-8-input-and-get-utf-8-output-through-pipe-to-from-powershell-with-c-c for more info about setting stdin's encoding to be UTF-8.


feat: add Option methods description and examples in 6.1 section

Option enum are well described in Cairo Book, but there is no mention about Option methods : expect , unwrap, is_some and is_none .
Unwrap is briefly mentioned in an example in 6.2 section.
I think it could be helpful to describe Option methods and how they work exactly, with short examples.

This would be great for the docs of the corelib but not adapted for the content of the book, imo.
The problem is just that there is no corelib reference. But if you open the source code, it's actually well documented


Textfield - type password

When a password type TextField is used, it hangs on IOS tablet device, i.e. there is some delay between clicking on the field and the keyboard popping up for the input.

Can you provide more information about what device you're using and what browser version you're on?
I've tried it on my iphone 12pro with 14.3 and i'm not noticing any delay  https://codesandbox.io/s/sweet-rhodes-0x4h6?file=/src/App.js

Can you provide more information about what device you're using and what browser version you're on?
I've tried it on my iphone 12pro with 14.3 and i'm not noticing any delay  https://codesandbox.io/s/sweet-rhodes-0x4h6?file=/src/App.js

Device-
iPad mini 4
OS version- 14.3
Browser-
Safari
From: Robert Snow<EMAIL_ADDRESS>Date: Monday, 4 January 2021 at 11:58 PM
To: adobe/react-spectrum<EMAIL_ADDRESS>Cc: Dheeraj Saraf<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [adobe/react-spectrum] Textfield - type password (#1437)
Can you provide more information about what device you're using and what browser version you're on?
I've tried it on my iphone 12pro with 14.3 and i'm not noticing any delay https://codesandbox.io/s/sweet-rhodes-0x4h6?file=/src/App.jshttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fsweet-rhodes-0x4h6%3Ffile%3D%2Fsrc%2FApp.js&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359062506|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=DAeB3p3UkyQxEcck2hKNtPp%2FHSJwxnVl5eBS%2F4%2FndlI%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fadobe%2Freact-spectrum%2Fissues%2F1437%23issuecomment-754138840&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359062506|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=R03xm3RUQyFWT7DKDp%2FXQbyq5DYnfgIU%2FSODhUqZLy4%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQ4HGCWGQUYHXDFCXMROXNDSYICGNANCNFSM4VS2TPDQ&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359072499|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=tB90uqiIX4c0WQnhYgWTCVstEkLe0LEnsJsVYNTjy%2BA%3D&reserved=0.

Device-
iPad mini 4
OS version- 14.3
Browser-
Safari
From: Robert Snow<EMAIL_ADDRESS>Date: Monday, 4 January 2021 at 11:58 PM
To: adobe/react-spectrum<EMAIL_ADDRESS>Cc: Dheeraj Saraf<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [adobe/react-spectrum] Textfield - type password (#1437)
Can you provide more information about what device you're using and what browser version you're on?
I've tried it on my iphone 12pro with 14.3 and i'm not noticing any delay https://codesandbox.io/s/sweet-rhodes-0x4h6?file=/src/App.jshttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fsweet-rhodes-0x4h6%3Ffile%3D%2Fsrc%2FApp.js&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359062506|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=DAeB3p3UkyQxEcck2hKNtPp%2FHSJwxnVl5eBS%2F4%2FndlI%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fadobe%2Freact-spectrum%2Fissues%2F1437%23issuecomment-754138840&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359062506|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=R03xm3RUQyFWT7DKDp%2FXQbyq5DYnfgIU%2FSODhUqZLy4%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQ4HGCWGQUYHXDFCXMROXNDSYICGNANCNFSM4VS2TPDQ&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359072499|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=tB90uqiIX4c0WQnhYgWTCVstEkLe0LEnsJsVYNTjy%2BA%3D&reserved=0.

Device-
iPad mini 4
OS version- 14.3
Browser-
Safari
Textfield is not working with type=’password’
From: Dheeraj Saraf<EMAIL_ADDRESS>Date: Tuesday, 5 January 2021 at 3:46 PM
To: adobe/react-spectrum<EMAIL_ADDRESS>Subject: Re: [adobe/react-spectrum] Textfield - type password (#1437)
Device-
iPad mini 4
OS version- 14.3
Browser-
Safari
From: Robert Snow<EMAIL_ADDRESS>Date: Monday, 4 January 2021 at 11:58 PM
To: adobe/react-spectrum<EMAIL_ADDRESS>Cc: Dheeraj Saraf<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [adobe/react-spectrum] Textfield - type password (#1437)
Can you provide more information about what device you're using and what browser version you're on?
I've tried it on my iphone 12pro with 14.3 and i'm not noticing any delay https://codesandbox.io/s/sweet-rhodes-0x4h6?file=/src/App.jshttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fsweet-rhodes-0x4h6%3Ffile%3D%2Fsrc%2FApp.js&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359062506|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=DAeB3p3UkyQxEcck2hKNtPp%2FHSJwxnVl5eBS%2F4%2FndlI%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fadobe%2Freact-spectrum%2Fissues%2F1437%23issuecomment-754138840&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359062506|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=R03xm3RUQyFWT7DKDp%2FXQbyq5DYnfgIU%2FSODhUqZLy4%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQ4HGCWGQUYHXDFCXMROXNDSYICGNANCNFSM4VS2TPDQ&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359072499|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=tB90uqiIX4c0WQnhYgWTCVstEkLe0LEnsJsVYNTjy%2BA%3D&reserved=0.

Device-
iPad mini 4
OS version- 14.3
Browser-
Safari
Textfield is not working with type=’password’
From: Dheeraj Saraf<EMAIL_ADDRESS>Date: Tuesday, 5 January 2021 at 3:46 PM
To: adobe/react-spectrum<EMAIL_ADDRESS>Subject: Re: [adobe/react-spectrum] Textfield - type password (#1437)
Device-
iPad mini 4
OS version- 14.3
Browser-
Safari
From: Robert Snow<EMAIL_ADDRESS>Date: Monday, 4 January 2021 at 11:58 PM
To: adobe/react-spectrum<EMAIL_ADDRESS>Cc: Dheeraj Saraf<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [adobe/react-spectrum] Textfield - type password (#1437)
Can you provide more information about what device you're using and what browser version you're on?
I've tried it on my iphone 12pro with 14.3 and i'm not noticing any delay https://codesandbox.io/s/sweet-rhodes-0x4h6?file=/src/App.jshttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fsweet-rhodes-0x4h6%3Ffile%3D%2Fsrc%2FApp.js&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359062506|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=DAeB3p3UkyQxEcck2hKNtPp%2FHSJwxnVl5eBS%2F4%2FndlI%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fadobe%2Freact-spectrum%2Fissues%2F1437%23issuecomment-754138840&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359062506|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=R03xm3RUQyFWT7DKDp%2FXQbyq5DYnfgIU%2FSODhUqZLy4%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQ4HGCWGQUYHXDFCXMROXNDSYICGNANCNFSM4VS2TPDQ&data=04|01|dsaraf%40adobe.com|b42106ea28b246459d5c08d8b0de97b1|fa7b1b5a7b34438794aed2c178decee1|0|0|637453817359072499|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|2000&sdata=tB90uqiIX4c0WQnhYgWTCVstEkLe0LEnsJsVYNTjy%2BA%3D&reserved=0.

So we've tested this on
iPhone 7 iOS 13.7
iPad Pro on iOS 13.3
iphone XS Max on iOS 14.2
iphone 12pro with 14.3
All of them appear to be working fine.
Are you able to reproduce it in the codesandbox i linked?
Otherwise, can you post the code you're using or post a video screen capture showing the issue?

So we've tested this on
iPhone 7 iOS 13.7
iPad Pro on iOS 13.3
iphone XS Max on iOS 14.2
iphone 12pro with 14.3
All of them appear to be working fine.
Are you able to reproduce it in the codesandbox i linked?
Otherwise, can you post the code you're using or post a video screen capture showing the issue?

As I mentioned before, it is working perfectly fine on all the devices but Safari/604.1 on iPad mini 4, OS version- 14.3. The keyboard is popping up after a considerable time lag for this particular device.
This is the way we have implemented the password textfield in our code.

From: Robert Snow<EMAIL_ADDRESS>Date: Wednesday, 6 January 2021 at 2:37 AM
To: adobe/react-spectrum<EMAIL_ADDRESS>Cc: Dheeraj Saraf<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [adobe/react-spectrum] Textfield - type password (#1437)
So we've tested this on
iPhone 7 iOS 13.7
iPad Pro on iOS 13.3
iphone XS Max on iOS 14.2
iphone 12pro with 14.3
All of them appear to be working fine.
Are you able to reproduce it in the codesandbox i linked?
Otherwise, can you post the code you're using or post a video screen capture showing the issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fadobe%2Freact-spectrum%2Fissues%2F1437%23issuecomment-754899514&data=04|01|dsaraf%40adobe.com|216b266267304cdb22cf08d8b1bde360|fa7b1b5a7b34438794aed2c178decee1|0|0|637454776476397410|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=v%2B9EZAH2jizZaqk1yfTVjHrCXYQB7bKIXH8oP5poWZ0%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQ4HGCWDYCBZAHXMKOMDIOTSYN5QNANCNFSM4VS2TPDQ&data=04|01|dsaraf%40adobe.com|216b266267304cdb22cf08d8b1bde360|fa7b1b5a7b34438794aed2c178decee1|0|0|637454776476397410|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=By%2FrW1VeHP5ctPQ6E3Aio0%2BtKqVothb8q4Fql47q96M%3D&reserved=0.

As I mentioned before, it is working perfectly fine on all the devices but Safari/604.1 on iPad mini 4, OS version- 14.3. The keyboard is popping up after a considerable time lag for this particular device.
This is the way we have implemented the password textfield in our code.

From: Robert Snow<EMAIL_ADDRESS>Date: Wednesday, 6 January 2021 at 2:37 AM
To: adobe/react-spectrum<EMAIL_ADDRESS>Cc: Dheeraj Saraf<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [adobe/react-spectrum] Textfield - type password (#1437)
So we've tested this on
iPhone 7 iOS 13.7
iPad Pro on iOS 13.3
iphone XS Max on iOS 14.2
iphone 12pro with 14.3
All of them appear to be working fine.
Are you able to reproduce it in the codesandbox i linked?
Otherwise, can you post the code you're using or post a video screen capture showing the issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fadobe%2Freact-spectrum%2Fissues%2F1437%23issuecomment-754899514&data=04|01|dsaraf%40adobe.com|216b266267304cdb22cf08d8b1bde360|fa7b1b5a7b34438794aed2c178decee1|0|0|637454776476397410|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=v%2B9EZAH2jizZaqk1yfTVjHrCXYQB7bKIXH8oP5poWZ0%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQ4HGCWDYCBZAHXMKOMDIOTSYN5QNANCNFSM4VS2TPDQ&data=04|01|dsaraf%40adobe.com|216b266267304cdb22cf08d8b1bde360|fa7b1b5a7b34438794aed2c178decee1|0|0|637454776476397410|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=By%2FrW1VeHP5ctPQ6E3Aio0%2BtKqVothb8q4Fql47q96M%3D&reserved=0.

I believe you that TextField with type=password is having an issue on your device. Since none of us have that device though, we cannot verify or work through this issue. I'm trying to gather more information from you so we can make an educated guess as to what is happening.
Can you provide a video showing the issue?
Can you verify that you see the issue in the codesandbox link I sent? or is it only happening in your application?

I believe you that TextField with type=password is having an issue on your device. Since none of us have that device though, we cannot verify or work through this issue. I'm trying to gather more information from you so we can make an educated guess as to what is happening.
Can you provide a video showing the issue?
Can you verify that you see the issue in the codesandbox link I sent? or is it only happening in your application?

The codesandbox link you shared is not using Textfield. Can you share an example using Textfield as type="password"?
Also, attached is the video showcasting the issue we are facing in iPad Mini 4. This seems to be a device specific issue as we are not facing this issue in any other device.
https://user-images.githubusercontent.com/70808330/103926677-3e016380-513f-11eb-8731-b51a7f7f997e.MP4

The codesandbox link you shared is not using Textfield. Can you share an example using Textfield as type="password"?
Also, attached is the video showcasting the issue we are facing in iPad Mini 4. This seems to be a device specific issue as we are not facing this issue in any other device.
https://user-images.githubusercontent.com/70808330/103926677-3e016380-513f-11eb-8731-b51a7f7f997e.MP4

Terribly sorry, not sure where I got that link, I've updated the comment with a new link. Including here as well. https://codesandbox.io/s/nifty-platform-kur8q?file=/src/App.js

Terribly sorry, not sure where I got that link, I've updated the comment with a new link. Including here as well. https://codesandbox.io/s/nifty-platform-kur8q?file=/src/App.js

PFA the attachment. The issue is reproducing with this piece of codesandbox code. The keyboard is not appearing even after clicking on the TextField element.
Uploading Textfield password codesandbox.MP4…

PFA the attachment. The issue is reproducing with this piece of codesandbox code. The keyboard is not appearing even after clicking on the TextField element.
Uploading Textfield password codesandbox.MP4…

PFA the attachment. The issue is reproducing with this piece of codesandbox code. The keyboard is appearing with a considerable lag after clicking on the TextField element.
Uploading Textfield password codesandbox.MP4…

PFA the attachment. The issue is reproducing with this piece of codesandbox code. The keyboard is appearing with a considerable lag after clicking on the TextField element.
Uploading Textfield password codesandbox.MP4…

PFA the attachment. The issue is reproducing with this piece of codesandbox code. The keyboard is appearing with a considerable lag after clicking on the TextField element.
https://user-images.githubusercontent.com/70808330/103989160-4c8a6200-51b5-11eb-89fc-947788e7e2b5.MP4

PFA the attachment. The issue is reproducing with this piece of codesandbox code. The keyboard is appearing with a considerable lag after clicking on the TextField element.
https://user-images.githubusercontent.com/70808330/103989160-4c8a6200-51b5-11eb-89fc-947788e7e2b5.MP4

@D-Saraf and @snowystinger,
I have been unable to reproduce the issue on an iPad mini 2 with iOS 12.5, which is the most recent version of iOS supported by this device.
https://user-images.githubusercontent.com/154077/104213508-5ce44c00-5404-11eb-9068-0803e975e31a.MP4

@D-Saraf and @snowystinger,
I have been unable to reproduce the issue on an iPad mini 2 with iOS 12.5, which is the most recent version of iOS supported by this device.
https://user-images.githubusercontent.com/154077/104213508-5ce44c00-5404-11eb-9068-0803e975e31a.MP4

@D-Saraf since we’re unable to reproduce and we don’t know what might be causing this, you may need to do some profiling detective work in order to narrow it down.  I’m going to close this issue for now, feel free to reopen if you learn more.

@D-Saraf since we’re unable to reproduce and we don’t know what might be causing this, you may need to do some profiling detective work in order to narrow it down.  I’m going to close this issue for now, feel free to reopen if you learn more.


Split UnwindSection::unwind_info_for_address

It is now a wrapper around UnwindSection::fde_for_address and FrameDescriptionEntry::unwind_info_for_address. If users need the FDE as well, then they can do the two steps themselves.
Also add FrameDescriptionEntry::rows, and automatically do context initialization in UnwindTable::new.
Fixes #311

Coverage decreased (-0.003%) to 86.57% when pulling 54cf31989459a415dc59a62304f58c4a08bdce88 on philipc:issue-311 into 039e0427b843ee3349d9313e652469ff9b06b610 on gimli-rs:master.


chore(master): release 1.27.0

:robot: I have created a release beep boop
1.27.0 (2023-08-17)
Features

remove local argument (c0d67ee)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/indykite/indykite-sdk-python/releases/tag/v1.27.0 :sunflower:


X-Ray daemon not sending traces to X-Ray service

I am trying to run a the x-ray daemon inside a docker container
this is my docker-compose.yaml
version: '3'

services:
//Other services

  app:
    build: ./
    volumes:
      - ./:/var/www/app
    ports:
      - 8080:8080
    links:
      - redis
    depends_on:
      - db
    command:
      sh -c 'npm i && npm run start'

  xray:
    build:
      context: ./
      dockerfile: Dockerfile.xray
    ports:
    - 2000:2000/udp
    - 2000:2000/tcp
    environment:
      - AWS_REGION=ap-southeast-1

Docker file for the xray image
FROM amazonlinux
RUN yum install -y unzip
RUN curl -o daemon.zip https://s3.dualstack.us-east-2.amazonaws.com/aws-xray-assets.us-east-2/xray-daemon/aws-xray-daemon-linux-3.x.zip
RUN unzip daemon.zip && cp xray /usr/bin/xray
ENTRYPOINT ["/usr/bin/xray", "-t", "<IP_ADDRESS>:2000", "-b", "<IP_ADDRESS>:2000"]
EXPOSE 2000/udp
EXPOSE 2000/tcp

my instrumented nodejs app
const AWSXRay = require('aws-xray-sdk')
app.use(AWSXRay.express.openSegment('my-backend'))
// all the routes here
// ...

app.use(AWSXRay.express.closeSegment())

Those are the docker-compose logs
xray_1   | 2020-03-03T06:16:28Z [Info] Initializing AWS X-Ray daemon 3.2.0
xray_1   | 2020-03-03T06:16:28Z [Info] Using buffer memory limit of 9 MB
xray_1   | 2020-03-03T06:16:28Z [Info] 144 segment buffers allocated
xray_1   | 2020-03-03T06:16:28Z [Info] Using region: ap-southeast-1

xray_1   | 2020-03-03T06:30:27Z [Info] HTTP Proxy server using X-Ray Endpoint : https://xray.ap-southeast-1.amazonaws.com
xray_1   | 2020-03-03T06:30:27Z [Info] Starting proxy http server on <IP_ADDRESS>:2000

I have a IAM role attached to my EC2 with AWSXrayFullAccess policy.
Obviously I am sending a bunch of requests, but still I do not see anything anything in the X-Ray console as well as the  [Info] Successfully sent batch of 1 segments in the docker-compose logs
Any idea?
Thanks
EDIT:
I have tried to send manually a segment with cat segment.txt > /dev/udp/<IP_ADDRESS>/2000 and it worked
xray_1   | 2020-03-03T09:22:52Z [Info] Successfully sent batch of 1 segments (0.020 seconds)

So I must have done something wrong with the SDK

Ok after checking out the documentation I just forgot that the host of the daemon was different as I am inside docker therefore I have added this line of code:
AWSXRay.setDaemonAddress('http://xray:2000')

However now I have this error:
 Error: Failed to get the current sub/segment from the context.
app_1    |     at Object.contextMissingRuntimeError [as contextMissing] (/var/www/app/node_modules/aws-xray-sdk-core/lib/context_utils.js:21:15)
app_1    |     at Object.getSegment (/var/www/app/node_modules/aws-xray-sdk-core/lib/context_utils.js:92:45)
app_1    |     at Object.resolveSegment (/var/www/app/node_modules/aws-xray-sdk-core/lib/context_utils.js:73:19)
app_1    |     at close (/var/www/app/node_modules/aws-xray-sdk-express/lib/express_mw.js:95:29)
app_1    |     at Layer.handle_error (/var/www/app/node_modules/express/lib/router/layer.js:71:5)
app_1    |     at trim_prefix (/var/www/app/node_modules/express/lib/router/index.js:315:13)
app_1    |     at /var/www/app/node_modules/express/lib/router/index.js:284:7
app_1    |     at Function.process_params (/var/www/app/node_modules/express/lib/router/index.js:335:12)
app_1    |     at Domain.next (/var/www/app/node_modules/express/lib/router/index.js:275:10)
app_1    |     at Domain.emit (events.js:198:13)
app_1    |     at Domain.EventEmitter.emit (domain.js:448:20)
app_1    |     at Domain._errorHandler (domain.js:246:21)
app_1    |     at Object.setUncaughtExceptionCaptureCallback [as captureFn] (domain.js:145:29)
app_1    |     at process._fatalException (internal/bootstrap/node.js:496:31)
app_1    |     at process._asyncFatalException [as _fatalException] (/var/www/app/node_modules/async-listener/glue.js:211:34)

Ah yes we are familiar with the segment missing from context error. Would you mind posting a small snippet of code showing your instumentation/setup/dependencies, as well as version of the X-Ray SDK, over on the Node SDK repo? The devs there will be happy to help you out!
Since you've resolve the issues for the daemon can I close out this ticket in favor of the Node ticket? Thanks!

@awssandra Thanks for the answer, I have opened an issue there. I will close this down.
Thanks for the hep


Create separate sub-module for WAR build

Description
Prepare build script improvements. Create separate module for WAR builds to simplify fineract-provider.

@ptuomola Hi Petri... could you do me a favor and approve this one... it's in preparation to get the performance improvements in place and a proper Docker image build. Thanks.

@ptuomola Hi Petri... could you do me a favor and approve this one... it's in preparation to get the performance improvements in place and a proper Docker image build. Thanks.


ln: failed to create symbolic link '/home/jovyan/ENVRI-Summer-School': File exists

The lab will not start in jupyterhub. We get en error: ln:
failed to create symbolic link '/home/jovyan/ENVRI-Summer-School': File exists

need to force:
ln -sf /home/ENVRI-Summer-School /home/jovyan/ENVRI-Summer-School


Update codeowners

@eistarov , can you please remain an hevce code reviewer while you're in a transition to a new hevce design?

@eistarov , can you please remain an hevce code reviewer while you're in a transition to a new hevce design?

I can, but only for the refactored part - not the legacy one.

Sure. Thank you!


Issue with swagger-codegen-maven-plugin

We are using swagger-codegen-maven plugin in our project. The code is generated everytime during maven build even if there is no change in .yaml file. Is there any way to exclude the already compiled/generated file to get overwritten.
I have posted this question with other details on below url.
http://stackoverflow.com/questions/42037240/swagger-codegen-maven-plugin-regeneration-code-on-mvn-compile

@j9amit you posted this issue on the wrong github project.


feat: support extended branching (pow2 only) with tests

fix: remove support for non-pow2 leafs and branches
re-factor: various cleanups

Some notes: This generalizes the merkle_tree and proof generation/validation code to N branches, where 2 is sort of a default (in tests anyway).  This also removes support for non-pow2 data size (leaf) values and only supports branch values that are a power of 2.  Branch values of 2/4/8 are tested in various ways, but there's no known reason larger branching tests can't be constructed if needed.  This will require upstream changes if merged.

This looks basically good. I have one blocking change, one blocking request (below), and a suggestion — which we can discuss over time and need not necessarily land here:
1. Blocking change: why are we tagging internal nodes of the tree? Unless this is necessitated by the new structure in a way I can't guess (which we should then discuss), I don't see why this would be introduced, and it doesn't seem consistent with our poseidon planning either. (Again, maybe I'm missing the point.)

2. Blocking request: can we add some negative tests — i.e. intelligently chosen fake proofs which are well-formed but incorrect (e.g. transposing order of hashes, etc.) which demonstrably fail verification?

3. Design consideration. I think we should strongly consider a proof structure in which `lemmas` is always a flat vector of hashes, with the root last. I see the apparent simplicity of nesting them, but I think this complicates things and adds to the cognitive load of understanding. In my proposed model (which I think is consistent with previous proofs), verification can proceed by incrementally reading and interpreting groups of hashes from the lemma. This does require that we know the shape of the tree over which the proof is given, but I think that is a requirement anyway.

This isn't introduced, it's how existing merkle_light works and this just stays compatible for the binary case.  Unrelated to this PR, it could be removed, and a fair number of internal tests will require updates.

@dignifiedquire also mentioned negative tests, and the only issue with them is that they expose internal proof structure.  If there's a good way to modify internal elements without making them public, that should help.

The lemma design hasn't changed either, it's for compatibility also.  It could be implemented either way, but the most straight-forward adaptation (at least to me) is what's proposed, based on what was already present.  Also unrelated to this PR, there are a number of existing checks on proof lemma length as a relationship to tree height, so collapsing it is possible, but more invasive and at least at the moment, less intuitive to me (checking length and indexing by calculation instead, etc).

Is this 'just' N::to_usize()?

Wow, thanks -- this cleans up a lot of nasty instances!


Fix entries per page selected value

Fixes #9212.
The images index view's context includes a variable entries_per_page which was overridden by the label. Regression from https://github.com/wagtail/wagtail/commit/eac5e0bc2cda0d78d1ffb13da32b8cc8410f2b0b
Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Merged (with test added) in 0f26facde4b551862f6676542213b17ddf376413 (main) and ab127df9cb556a848dab9f527869b3fb4f613fc8 (stable/4.0.x).


CLI colors

Are any possibilities to enable it ?
cat ~/.phpbrew/php/php-5.5.27/etc/php.ini | grep cli_server.color
Gives me:
cli_server.color = On
But I still can't se colors on shell

What kind of color do you want? the console output color? you need to make sure that your terminal supports the ANSI console colors.

This is an example:
When I run command on terminal:
php app/console cache:clear
Then output is:
Clearing the cache for the dev environment with ...
Text wrapped by "info" tag should be colorized.
It works on my native php, but it does not work with phpbrew.
Both php.ini are identical.
How can I enable colorizing for phpbrew ?
Example of CLI script:
https://github.com/symfony/FrameworkBundle/blob/master/Command/CacheClearCommand.php#L69

I doubt this is caused by phpbrew itself. Are you testing this against the same php version (from system and phpbrew)?
A deeper check. Please add a breakpoint on this line https://github.com/symfony/symfony/blob/2.8/src/Symfony/Component/Console/Formatter/OutputFormatter.php#L240 and check if $this->isDecorated() yields the same value on both environments. The console component might be doing some "clever" decision somewhere and disabling colors. But I'd like to confirm this before investigating more.

friendly ping

Ok sorry for my delay, I was on vacation :)
Firstly I want to congrats for your amazing investigation. It was helpfully tip.
I noticed that:
https://github.com/symfony/Console/blob/master/Output/StreamOutput.php
StreamOutput::hasColorSupport method returns false when phpbrew switch 5.5.27
and this method returns true when phpbrew off
This is caused by missing posix_isatty() for phpbrew's php.
Are any possibilities to install posix_isatty with phpbrew  ?

Hi, ok you just need the posix extension. Run phpbrew ext | grep posix, if you get no output, proceed with phpbrew ext install posix :)
The strange thing is that +posix should be installed by default or if you use the +default variant. Just in case, can you post the output of phpbrew list -v?
Thanks.

phpbrew ext install posix enabled color in CLI for me thx.

That's great, thanks for reporting back.

+1 phpbrew ext install posix


v6.3 breaks editing table value with custom data type

System information:

Operating system (distribution) and version: Win 10 v1909
DBeaver version: v<IP_ADDRESS>912011827
Additional extensions: None

Connection specification:

Database name and version: PostgreSQL 9.6.11 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28), 64-bit
Driver name: PostgreSQL JDBC Driver
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
Since upgrading to v6.3 it is no longer possible to change the value of a cell that is based on a custom data type.
Steps to reproduce, if exist:
Run this query:
CREATE TYPE public.custom_type AS ENUM ('Type1', 'Type2');

CREATE TABLE type_tester (
	id serial NOT NULL,
	type public.custom_type,
	CONSTRAINT "type_tester_pkey" PRIMARY KEY (id)
);

insert into type_tester (type) values ('Type1');

Open the table type_tester in dbeaver and open the Data tab if not open by default.
Try to change Type1 into Type2
Include any warning/errors/backtraces from the logs

thanks for the bug report. This error happens only with enum data types.

verified


go get github.com/HewlettPackard/lustre_exporter Does not work with go1.16.3.

Doing 'go get' on latest (go1.16.3) Fails
$ go get github.com/HewlettPackard/lustre_exporter
# github.com/HewlettPackard/lustre_exporter
pkg/mod/github.com/!hewlett!packard/lustre_exporter@v2.0.0+incompatible/lustre_exporter.go:153:28: undefined: prometheus.InstrumentHandler

Version
$ cat /usr/local/go/VERSION
go1.16.3[root@centos79 go]#

However, droping a version down and retrying it passes and works on (go1.15.11).
It most likely looks like the go1.16.3 breaks 'lustre_exporter'.
Additional Info:
$ uname -a
Linux centos79 3.10.0-1160.15.2.el7.x86_64 #1 SMP Wed Feb 3 15:06:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)

Hi,
this fork is active and working with go1.17.5:
https://github.com/GSI-HPC/lustre_exporter

Hi,
Thanks for the update. As I mentioned in by bug report it also did work with (go1.15.11) at the time. Only with the latest (at that time it was (go1.16.3)) it did not work. I have not tried out with go1.17.5 yet, I know it worked for 15.11 and as you mentioned it works for 17.5. It does not work for 16.3 only.  Something that should be looked into?

Hi,
as I said, we are running a fork and that was tested successfully with 1.17.5.
It might also be running with lower/higher version of go...
If you strongly rely on a specific golang version, you have to check it out.
I would recommend building the project with the tested version.

Hi,

https://github.com/GSI-HPC/lustre_exporter
I failed to mentioned that I used this fork as base. What failed was (HewlettPackard/lustre_exporter). The project does not depend upon golang version. It was just that at that time the latest was 16.3 and  HP/lustre_exporter (go get) failed to work. Thanks!

You welcome!
This project is not active since 2019...

This project is not active since 2019..

Yes. However, this had more latest commits than HP's

Yes, the HP project has not been updated since 2019.
As I said, https://github.com/GSI-HPC/lustre_exporter is an active fork.


#1214: Wip documentation.

Description
Still working on this as there seems to be a bug with translatable json fields.
This pr also fixes translatable attributes in json.
Related Issues
fixes #1214

Looks great, thank you! Was https://github.com/area17/twill/pull/1151 incomplete regarding translated fields?

@haringsrob The added documentation looks great! I'm not sure I follow re. what's being added in getFormFieldsHandleFieldsGroups(). I'll do a quick test on my end to refresh my memory on this.

Well, what is happening is that even if you have a json field translatable it would return a flat array.
Per the docs the $fields to the frontend would contain:
link_target = target
link_url = url
link_label = label

This wont work as the fields are marked as translatable.
So the front-end expects this:
link_target = en: target, nl: target
link_url = en:URL, nl:url
link_label = en:label, nl: label

Does this have anything to do with the cast property on the model? IIRC this is needed on the translated model.

With these changes this is the result in the db:

@haringsrob The following configuration works for me on https://github.com/area17/twill/pull/1151
Does this make any sense?
Migration
Schema::create('page_translations', function (Blueprint $table) {
    createDefaultTranslationsTableFields($table, 'page');
    $table->string('title', 200)->nullable();
    $table->text('description')->nullable();
    $table->json('footer')->nullable();
});

Model
protected $fillable = [
    'footer',
];

public $translatedAttributes = [
    'footer',
];

Translation Model
public $casts = [
    'footer' => 'array',
];

Repository
protected $fieldsGroups = [
    'footer' => ['title', 'subtitle'],
];

public $fieldsGroupsFormFieldNamesAutoPrefix = true;

Form
@formField('input', [
    'name' => 'footer_title',
    'label' => 'footer Title',
    'translated' => true,
    'maxlength' => 100
])

@formField('input', [
    'name' => 'footer_subtitle',
    'label' => 'footer Subtitle',
    'translated' => true,
    'maxlength' => 100
])

Frontend
{{ $page->footer['title'] }}
{{ $page->footer['subtitle'] }}


[WFCORE-5171] Upgrade XNIO to 3.8.3.Final

Issue: https://issues.redhat.com/browse/WFCORE-5171

Core - Full Integration Build 10105 outcome was FAILURE using a merge of 0ccff479dabbe0d7b208b56ea136f1719c16449e
Summary: Exit code 1 (Step: Build & test core (Maven)) (new) Build time: 00:01:04

Core - Full Integration Build 10150 outcome was FAILURE using a merge of 0ccff479dabbe0d7b208b56ea136f1719c16449e
Summary: Exit code 1 (Step: Build & test core (Maven)) (new) Build time: 00:01:11

@fl4via @dmlloyd It seems this release is not present in nexus.

It looks like the xnio-all artifact is, but the others aren't.  It seems like something went wrong with the Maven deploy and I'm not sure how to fix it.  I think I might have to torpedo that one and try again with 3.8.4.Final.

3.8.4.Final is released; it should (🤞🏻) be on Nexus in the next 24 hours.

@gaol Can you change the JIRA / commit msg / PR title to 3.8.4 please? Thanks.

@bstansberry Done !


Need more 1080p sources

Hey needs more 1080p sources please , Thank you

you have any websites you can provide?

OK mrknow and other developers,now i will give you some great tv shows and movie sources:
123movies.to(movies/tv shows)
dayt.se tv(tv shows)
cdn.serieswatch.tv/2 (movies with 5.1 audio and big number of tv shows)
fardadownload.ir (bunch of tv shows in hd and x265)
I will add more soon

Anyone here??

yes

Good news. dayt.se added (mail.ru). Please check new version 2<IP_ADDRESS>. Tomorrow will try to add cdn.serieswatch.tv/2.
thanks for this sources

Ok mrknow.
123movies.to is great source,make sure you add it if you can!
Thanks for this

kiwihd.com- bunch of tvshows and movies in hd

123movies.to - added as Muchmovies
dayt.se - added without youtube sources ...

list taken from this YouTube video (https://www.youtube.com/watch?v=RCDaGdi25xE) and seems to work well
your Sources list order should look like this order more or less:

sezonlukdizi - (Episodes ) (Episodes Only) (HD Source)
DayT - (Episodes) (HD Source)
dizilab - (Episodes Only) (HD Source) (HC TURK for some)
TVWTVS - (Episodes) (HD Source)
Watch5s - (Movies and Episodes) (HD Source) *new
9Movies - (Movies Only) (HD Source)
123movies - (Movies Only) (HD Source)
CloudMovie- (Movies) (HD Source)
HEVCBluRay - (Movies Only) (HD Source )
FardaDownload - (Movies and Episodes) (HD Source)
PirateJunkies - (Movies) (HD Source) *new
Torba - (Movies and Episodes) (HD Source) (great source but ned a verification to watch)
Serieswatch - (Movies & Episodes) (HD Source)
Filmovizija - (Movies & Episodes) (HD Source) *new
HDmovie14 - (Movies and Episodes) (HD Source)
MiraDeTodo - (Movies Only) (HD Source)
dizimag - (Episodes Only) (HD Source)
MWM - (Episodes) (HD Source )
Dizibox - (Episodes) (HD Source)
MovieSub - (Movies Only) (HD Source )
Emovies.pro - (Movies Only) (HD Source)
dizigold - (Episodes) (HD Source)
vivo.to - (Movies and Episodes) (HD Source)
xvideos8.v2 - (Movies Only) (HD Source)
pubfilm - (Movies Only) (HD Source)
MovieXK - (Episodes And Movies) (HD Source ) (have MovieXK watermark)
clickplay.to - (Episodes Only) (HD Source)
Stage66 - (Movies Only) (HD Source )
RainierLand - (Movies and Episodes) (HD Source)
ViewMovies - (Movies Only) (HD Source)
Kiwihd - (Movies and Episodes) (HD Source) (have Kiwihd watermark) *new
PutMV - (Movies Only) (HD Source)
Zumvo - (Movies Only) (HD Source)
primewire - (Movies and Episodes) (SD Source)

Great list . I start work on it in June

hd host from fastest to slowest
MrFile
Gvideo
Yify
Dizimag
VK
Muchmovies
Videomega
Turbovideos
Openload
Vidplay
MovieTV
Moviefarsi

sd host from fastest to slowest
Openload HQ
Mrfile HQ
Uptobox HQ
Dizimag HQ
Turbovideos HQ
V-vids HQ
Skyvids HQ
Gvideo HQ
Mightupload HQ
zStream HQ
Vidspot MQ
Streamin MQ
Allmyvideos MQ
Vidto MQ
Streamcloud MQ
Letwatch MQ
Divxpress LQ
Filehoot LQ
Beststreams LQ
Vidzi LQ

old issue


Change default api_key query string parameter to access_token

Is there any way to change the default access key query string that is appended from api_key to access_token.
I tried adding this to my custom.js file
ApiKeyButton.prototype.applyApiKey = function () {
    var elem;
    window.authorizations.add('access_token', new ApiKeyAuthorization('access_token', $("#input_apiKey_entry").val(), this.model["in"]));
    window.swaggerUi.load();
    return elem = $('#apikey_container').show();
};

Hi there
Admittedly, there is a general lack of support for this in both SB and to a lesser extent the swagger-ui.
However, SB does provide a simple mechanism to inject custom JavaScripts into the UI which you can use to workaround this issue with relative ease. You should have a quick read over the section in the readme entitled "Injecting Custom Content". Then, tweak and inject the following script:
$(function () {
    $('#input_apiKey').off();
    $('#input_apiKey').on('change', function () {
        value = this.value;
        if (value && value.trim() != '')
            window.authorizations.add('myKey', new ApiKeyAuthorization("mykey", value, "header"));
    });
});

Thanks, I'll try it out in the morning :)

I wasn't able to get this to work with that code. I was able to get it to work if it was appended to the header with the following code:
$(function () {
    $('#input_apiKey').off();
    $('#input_apiKey').on('change', function () {
        var key = this.value;
        if (key && key.trim() !== '') {
            key = 'Bearer ' + key;
            window.authorizations.add('key', new ApiKeyAuthorization('Authorization', key, 'header'));
        }
    });
})();

Thanks guys, this resolved it for me as well.

@niemyjski
With your solution I get  "Uncaught TypeError: value.apply is not a function".
Anyone got an idea what that's about?

@RobvanGeloven Are you sure you are seeing an issue with my code? I'm not calling apply() anywhere.

My apolagies: I see that there's an updated script on the wiki:
// add a new SwaggerClient.ApiKeyAuthorization when the api-key changes in the ui.
$('#input_apiKey').change(function() {
var key = $('#input_apiKey')[0].value;
if(key && key.trim() != "") {
swaggerUi.api.clientAuthorizations.add("key", new SwaggerClient.ApiKeyAuthorization("api_key", key, "header"));
}
})
That one works like charm :)

Thank you guys, you save me a night.


Add a deprecated version of mbedtls_platform_memcmp.

@AndrzejKurek , I hope  MBEDTLS_DEPRECATED_REMOVED flag is not enabled in nano client internal branch

@AndrzejKurek , I hope MBEDTLS_DEPRECATED_REMOVED flag is not enabled in nano client internal branch

It would be great to know what config are they using. A grep through the mbed-cloud-client-internal repository, master branch shown that there's no use of any deprecated keyword, but it is present in the baremetal example config here: https://github.com/ARMmbed/mbedtls/blob/baremetal/configs/baremetal.h.
The nanoclient config however does not define it:
https://github.com/ARMmbed/pmi-arm-firmware/blob/master/apps/nanoclient-example/mbedtls_mbed_client_config_cert.h

@AndrzejKurek , I hope MBEDTLS_DEPRECATED_REMOVED flag is not enabled in nano client internal branch

It would be great to know what config are they using. A grep through the mbed-cloud-client-internal repository, master branch shown that there's no use of any deprecated keyword, but it is present in the baremetal example config here: https://github.com/ARMmbed/mbedtls/blob/baremetal/configs/baremetal.h.
The nanoclient config however does not define it:
https://github.com/ARMmbed/pmi-arm-firmware/blob/master/apps/nanoclient-example/mbedtls_mbed_client_config_cert.h

nano client use this FLAG definition from https://github.com/ARMmbed/pmi-arm-firmware/blob/master/libs/mbed-os/features/mbedtls/inc/mbedtls/config.h#L273
so in pmi repo the API will be disabled. The set this flag using some importer script https://github.com/ARMmbed/pmi-arm-firmware/blob/master/libs/mbed-os/features/mbedtls/importer/adjust-config.sh#L199


nbc.com

It would be great if this tool supported nbc.com. I think it would be difficult because of the complex encryption. This script would be a good start. https://github.com/K-S-V/Scripts/blob/master/AdobeHDS.php

Thanks @codesparkle, closing.
@archstar NBC.com is now supported, but the video you provided seems gone. (It redirects to http://www.nbc.com/the-tonight-show) If you still encounter problems, feel free to open a new issue.


Automated Package Upgrade

:tada: This PR is included in version 5.3.135 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Store the refresh state timing in a separate unlogged table

As part of the ongoing catalog optimisation efforts, let's try to move out the next_update_at timestamp column from refresh_state into its own table. Also, make that table UNLOGGED on postgres, making it not contribute to disk I/O at all.
This experiment looks to reduce WAL pressure and lock contention, leaving the refresh_state table completely unchanged unless entity data actually does change. We have debated whether to make it possible to externalize this queue into a separate system such as redis, but let's start with this as a baseline and see if we feel that that extra complexity is worth it after things settle.
For now, the deferred stitching related columns stay in refresh_state for two reasons: losing state in them has actual impact (risks data loss), and they only change whenever the processed output and stitched output need to change anyway.

Probably wanna update the otel metrics and alike right now?


Support for channel_file out parameter

Optional channel_file parameter for out that reads a list of additional (whitespace separated) Slack channels from a file generated by a previous task.
For example, sometimes its nice to be able to send a DM to the author of each build's source code commit. This way, the preceding task can pull the username out of the Git log or GitHub API and map that to their Slack username.

Would it be possible to add a test case(s) for your changes

@miromode this is now in latest docker image


🐛 Fix jsonable_encoder using include and exclude parameters for non-Pydantic objects

This fixes #2594. I added more few cases with include and exclude parameters, which were missing. Now the parameters are consistent with the way that it works with Pydantic.
When I first added the new tests in test_jsonable_encoder.py (without changing the codebase), these were the errors I got:
================================= test session starts =================================
platform linux -- Python 3.8.5, pytest-5.4.3, py-1.10.0, pluggy-0.13.1
rootdir: /home/xaviml/work/fastapi
plugins: cov-2.10.0, asyncio-0.14.0
collected 15 items

tests/test_jsonable_encoder.py FFF............                                  [100%]

====================================== FAILURES =======================================
__________________________________ test_encode_dict ___________________________________

    def test_encode_dict():
        pet = {"name": "Firulais", "owner": {"name": "Foo"}}
        assert jsonable_encoder(pet) == {"name": "Firulais", "owner": {"name": "Foo"}}
>       assert jsonable_encoder(pet, include={"name"}) == {"name": "Firulais"}
E       AssertionError: assert {'name': 'Fir...name': 'Foo'}} == {'name': 'Firulais'}
E         Omitting 1 identical items, use -vv to show
E         Left contains 1 more item:
E         {'owner': {'name': 'Foo'}}
E         Use -v to get the full diff

tests/test_jsonable_encoder.py:99: AssertionError
__________________________________ test_encode_class __________________________________

    def test_encode_class():
        person = Person(name="Foo")
        pet = Pet(owner=person, name="Firulais")
        assert jsonable_encoder(pet) == {"name": "Firulais", "owner": {"name": "Foo"}}
>       assert jsonable_encoder(pet, include={"name"}) == {"name": "Firulais"}
E       AssertionError: assert {'name': 'Fir...name': 'Foo'}} == {'name': 'Firulais'}
E         Omitting 1 identical items, use -vv to show
E         Left contains 1 more item:
E         {'owner': {'name': 'Foo'}}
E         Use -v to get the full diff

tests/test_jsonable_encoder.py:112: AssertionError
________________________________ test_encode_dictable _________________________________

    def test_encode_dictable():
        person = DictablePerson(name="Foo")
        pet = DictablePet(owner=person, name="Firulais")
        assert jsonable_encoder(pet) == {"name": "Firulais", "owner": {"name": "Foo"}}
>       assert jsonable_encoder(pet, include={"name"}) == {"name": "Firulais"}
E       AssertionError: assert {'name': 'Fir...name': 'Foo'}} == {'name': 'Firulais'}
E         Omitting 1 identical items, use -vv to show
E         Left contains 1 more item:
E         {'owner': {'name': 'Foo'}}
E         Use -v to get the full diff

tests/test_jsonable_encoder.py:125: AssertionError
================================== warnings summary ===================================
env/lib/python3.8/site-packages/aiofiles/os.py:10
env/lib/python3.8/site-packages/aiofiles/os.py:10
env/lib/python3.8/site-packages/aiofiles/os.py:10
env/lib/python3.8/site-packages/aiofiles/os.py:10
env/lib/python3.8/site-packages/aiofiles/os.py:10
env/lib/python3.8/site-packages/aiofiles/os.py:10
  /home/xaviml/work/fastapi/env/lib/python3.8/site-packages/aiofiles/os.py:10: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
    def run(*args, loop=None, executor=None, **kwargs):

-- Docs: https://docs.pytest.org/en/latest/warnings.html
=============================== short test summary info ===============================
FAILED tests/test_jsonable_encoder.py::test_encode_dict - AssertionError: assert {'n...
FAILED tests/test_jsonable_encoder.py::test_encode_class - AssertionError: assert {'...
FAILED tests/test_jsonable_encoder.py::test_encode_dictable - AssertionError: assert...
====================== 3 failed, 12 passed, 6 warnings in 0.51s =======================

You can see that even I added the same tests to test_encode_model_with_default, they all passed. This is because the include and exclude done by Pydantic was done correctly. Therefore, what this PR adds is:

More test cases to include and exclude parameters from the jsonable_encoder function
Consistent functionality with different types of objects (BaseModel, dict, and Object)

Hi @falkben,
Thank you for your reply. You are indeed correct it is a recursive function, however, when passing to children, the include and exclude is not passed (this was like this already). Not sure what is desired or not, but I am seeking consistency, so I went ahead and try how it works when passing a BaseModel object:
class Model1(BaseModel):
    foo: str
    bar: str
    blabla: str

class Model2(BaseModel):
    foo: str
    bar: str
    model1: Model1

def test_jsonable_encoder_nested():
    model1 = Model1(foo="foo1", bar="bar1", blabla="blabla1")
    model2 = Model2(foo="foo1", bar="bar1", model1=model1)
    jsonable_encoder(model2, include={"foo"})
    # returns: {'foo': 'foo1'}
    jsonable_encoder(model2, exclude={"foo"})
    # {'bar': 'bar1', 'model1': {'bar': 'bar1', 'blabla': 'blabla1', 'foo': 'foo1'}}

Then if we try with a dict:
def test_jsonable_encoder_nested_dict():
    model = {'bar': 'bar1', 'foo': 'foo1', 'model1': {'bar': 'bar1', 'blabla': 'blabla1', 'foo': 'foo1'}}
    jsonable_encoder(model, include={"foo"})
    # {'foo': 'foo1'}
    jsonable_encoder(model, exclude={"foo"})
    # {'bar': 'bar1', 'model1': {'bar': 'bar1', 'blabla': 'blabla1', 'foo': 'foo1'}}

You can see that it behaves the same way as Pydantic, which is not including and excluding for children objects.
I guess this will need to be added to the test suite, so we can define how the function is expected to work for future reference. Do you agree?
Regards,
Xavi M.

Hi @falkben,
Thank you for your reply. You are indeed correct it is a recursive function, however, when passing to children, the include and exclude is not passed (this was like this already). Not sure what is desired or not, but I am seeking consistency, so I went ahead and try how it works when passing a BaseModel object:
class Model1(BaseModel):
    foo: str
    bar: str
    blabla: str

class Model2(BaseModel):
    foo: str
    bar: str
    model1: Model1

def test_jsonable_encoder_nested():
    model1 = Model1(foo="foo1", bar="bar1", blabla="blabla1")
    model2 = Model2(foo="foo1", bar="bar1", model1=model1)
    jsonable_encoder(model2, include={"foo"})
    # returns: {'foo': 'foo1'}
    jsonable_encoder(model2, exclude={"foo"})
    # {'bar': 'bar1', 'model1': {'bar': 'bar1', 'blabla': 'blabla1', 'foo': 'foo1'}}

Then if we try with a dict:
def test_jsonable_encoder_nested_dict():
    model = {'bar': 'bar1', 'foo': 'foo1', 'model1': {'bar': 'bar1', 'blabla': 'blabla1', 'foo': 'foo1'}}
    jsonable_encoder(model, include={"foo"})
    # {'foo': 'foo1'}
    jsonable_encoder(model, exclude={"foo"})
    # {'bar': 'bar1', 'model1': {'bar': 'bar1', 'blabla': 'blabla1', 'foo': 'foo1'}}

You can see that it behaves the same way as Pydantic, which is not including and excluding for children objects.
I guess this will need to be added to the test suite, so we can define how the function is expected to work for future reference. Do you agree?
Regards,
Xavi M.

Sorry I did not answer your question about nested include and exclude. This PR does not add the functionality that Pydantic has with nested includes and excludes as defined in here. In my opinion, this would be part of a new feature if we are interested in adding it, so should be treated in another PR. This PR fixes a bug that the jsonable_encoder function has.

Sorry I did not answer your question about nested include and exclude. This PR does not add the functionality that Pydantic has with nested includes and excludes as defined in here. In my opinion, this would be part of a new feature if we are interested in adding it, so should be treated in another PR. This PR fixes a bug that the jsonable_encoder function has.

Hi there,
Just for the awareness, this bug impacts the code from full-stack-fastapi-postgresql, which is a widely used template project for FastAPI. The problem comes when there is a circular dependency in the ORM (e.g. SQLAlchemy), then the jsonable_encoder would fall into a RecursionError: maximum recursion depth exceeded in comparison error. For this reason, I changed this line to:
obj_data = jsonable_encoder(db_obj, include=set(obj_in.__fields__.keys()))

Finally, after this change in my code is when I realized this bug, which made me realized that includes does not work when passing an ORM object instead of a Pydantic one.
I am not worried because I checked out the jsonable_encoder function to my private repository, but I am just concerned that someone else might be facing the same problem.
Regards,
Xavi M.

PR was rebased and fixed to be compatible with include and exclude dictionaries, which was added in this PR and merged: https://github.com/tiangolo/fastapi/pull/2016

Great, thank you @xaviml! :rocket:
Thanks for the detailed explanation and tests. And thanks @falkben for the input! :cake:


Check contract names when performing migrations

If you want to report a security issue, please follow our security policy: https://github.com/White-Whale-Defi-Platform/migaloo-core/blob/main/SECURITY.md

Improvement description
This will prevent accidentally migrating to other contracts.

Additional context
Add any other context here, code snippets, json responses, screenshots and so on.

Code sample

Logs

Screenshots

Fixed in #195


Sensu JIT proxy client timestamp is not set on initial creation

Sensu JIT proxy client timestamp is not set on initial creation, the dashboard will display "Invalid Date".
Expected Behavior
The proxy client timestamp should be set to the current epoch time at creation.
Current Behavior
Sensu JIT proxy client timestamp is not set on initial creation, the dashboard will display "Invalid Date".

Possible Solution
Add :timestamp => Time.now.to_i to https://github.com/sensu/sensu/blob/master/lib/sensu/server/process.rb#L600-L608
Steps to Reproduce (for bugs)

Push a check result to a client socket with a new "source", e.g. "source": "FAIL"
Observe the dashboard, the "FAIL" client will have an "Invalid Date"

Closed by #1752


Query: adding stats to the remote engine

We are currently losing track of query stats because the remote engine does not transmit performance stats on gRPC calls.
In this PR I am adding some fields to the Query API response to include some stats.

[x] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Adding new fields on the response of the QueryAPI to carry stats in gRPC calls.
Implementing the Stats() method from the prometheus Query interface for the remoteQuery so we can get stats on the thanos/promql-engine.
Changes on promql-engine to properly consume stats from upstream queries (see https://github.com/thanos-io/promql-engine/pull/452)

Verification

Blocked on https://github.com/thanos-io/promql-engine/pull/452, but opening for reviews.

   Retrying in next tick" err="getting metrics: Get \"http://<IP_ADDRESS>:32769/metrics\": dial tcp <IP_ADDRESS>:32769: connect: connection refused"
09:08:12 Stopping downsampler-downsample
09:08:12 downsampler-downsample: ts=2024-05-16T07:08:12.516356177Z caller=main.go:182 level=info msg="caught signal. Exiting."  http2=false address=[::]:8080
09:08:13 compact-working: ts=2024-05-16T07:08:12.986095959Z caller=fetcher.go:626 level=info name=compact-working component=block.BaseFetcher msg="successfully synchronized block metadata" duration=14.377241ms duration_ms=14 cached=6 returned=6 partial=0
09:08:13 compact-working: ts=2024-05-16T07:08:12.988254958Z caller=fetcher.go:626 level=info name=compact-working component=block.BaseFetcher msg="successfully synchronized block metadata" duration=16.464281ms duration_ms=16 cached=6 returned=4 partial=0
09:08:13 compact-working: ts=2024-05-16T07:08:12.988277541Z caller=clean.go:34 level=info name=compact-working msg="started cleaning of aborted partial uploads"
09:08:13 compact-working: ts=2024-05-16T07:08:12.988286166Z caller=clean.go:61 level=info name=compact-working msg="cleaning of aborted partial uploads done"
09:08:13 compact-working: ts=2024-05-16T07:08:12.988288916Z caller=blocks_cleaner.go:44 level=info name=compact-working msg="started cleaning of blocks marked for deletion"
09:08:13 compact-working: ts=2024-05-16T07:08:12.988292333Z caller=blocks_cleaner.go:58 level=info name=compact-working msg="cleaning of blocks marked for deletion done"
09:08:13 compact-working: ts=2024-05-16T07:08:12.990274248Z caller=fetcher.go:626 level=info name=compact-working component=block.BaseFetcher msg="successfully synchronized block metadata" duration=4.135122ms duration_ms=4 cached=6 returned=6 partial=0
09:08:13 compact-working: ts=2024-05-16T07:08:12.992100122Z caller=fetcher.go:626 level=info name=compact-working component=block.BaseFetcher msg="successfully synchronized block metadata" duration=3.802039ms duration_ms=3 cached=6 returned=4 partial=0
09:08:13 compact-working: ts=2024-05-16T07:08:12.992119914Z caller=compact.go:1493 level=info name=compact-working msg="start of GC"
09:08:13 compact-working: ts=2024-05-16T07:08:12.99246608Z caller=compact.go:1516 level=info name=compact-working msg="start of compactions"
09:08:13 compact-working: ts=2024-05-16T07:08:12.993142038Z caller=compact.go:1136 level=info name=compact-working group="300000@{case=\"downsampled-block-with-overlap\"}" groupKey=300000@14846485652960182170 msg="compaction available and planned" plan="[01HY03NN47AHEX1HAK96CDCHQ0 (min time:<PHONE_NUMBER>014, max time:<PHONE_NUMBER>000) 01HY03NN16FY7NGAVRG92WPGH1 (min time:<PHONE_NUMBER>014, max time:<PHONE_NUMBER>000)]"
09:08:13 compact-working: ts=2024-05-16T07:08:12.993162538Z caller=compact.go:1145 level=info name=compact-working group="300000@{case=\"downsampled-block-with-overlap\"}" groupKey=300000@14846485652960182170 msg="finished running pre compaction callback; downloading blocks" duration=2.75µs duration_ms=0 plan="[01HY03NN47AHEX1HAK96CDCHQ0 (min time:<PHONE_NUMBER>014, max time:<PHONE_NUMBER>000) 01HY03NN16FY7NGAVRG92WPGH1 (min time:<PHONE_NUMBER>014, max time:<PHONE_NUMBER>000)]"
09:08:13 compact-working: ts=2024-05-16T07:08:12.999358534Z caller=fetcher.go:626 level=info name=compact-working component=block.BaseFetcher msg="successfully synchronized block metadata" duration=7.140621ms duration_ms=7 cached=6 returned=4 partial=0
09:08:13 compact-working: ts=2024-05-16T07:08:13.009822568Z caller=compact.go:1203 level=info name=compact-working group="300000@{case=\"downsampled-block-with-overlap\"}" groupKey=300000@14846485652960182170 msg="downloaded and verified blocks; compacting blocks" duration=16.645822ms duration_ms=16 plan="[/Users/pedro/src/github.com/pedro-stanaka/thanos/test/e2e/e2e_3499631035/data/compact-working/compact/300000@14846485652960182170/01HY03NN47AHEX1HAK96CDCHQ0 /Users/pedro/src/github.com/pedro-stanaka/thanos/test/e2e/e2e_3499631035/data/compact-working/compact/300000@14846485652960182170/01HY03NN16FY7NGAVRG92WPGH1]"
09:08:13 compact-working: ts=2024-05-16T07:08:13.015165523Z caller=compact.go:757 level=info name=compact-working msg="Found overlapping blocks during compaction" ulid=01HY03NQTKGEAC36QQV2ASFJ88
09:08:13 compact-working: ts=2024-05-16T07:08:13.018910353Z caller=intrumentation.go:67 level=warn name=compact-working msg="changing probe status" status=not-ready reason="error executing compaction: compaction: group 300000@14846485652960182170: paniced while compacting 01HY03NN16FY7NGAVRG92WPGH1,01HY03NN47AHEX1HAK96CDCHQ0: unexpected seriesToChunkEncoder lack of iterations"
09:08:13 compact-working: ts=2024-05-16T07:08:13.018935853Z caller=http.go:91 level=info name=compact-working service=http/server component=compact msg="internal server is shutting down" err="error executing compaction: compaction: group 300000@14846485652960182170: paniced while compacting 01HY03NN16FY7NGAVRG92WPGH1,01HY03NN47AHEX1HAK96CDCHQ0: unexpected seriesToChunkEncoder lack of iterations"
09:08:13 compact-working: ts=2024-05-16T07:08:13.018984187Z caller=http.go:110 level=info name=compact-working service=http/server component=compact msg="internal server is shutdown gracefully" err="error executing compaction: compaction: group 300000@14846485652960182170: paniced while compacting 01HY03NN16FY7NGAVRG92WPGH1,01HY03NN47AHEX1HAK96CDCHQ0: unexpected seriesToChunkEncoder lack of iterations"
09:08:13 compact-working: ts=2024-05-16T07:08:13.018997353Z caller=intrumentation.go:81 level=info name=compact-working msg="changing probe status" status=not-healthy reason="error executing compaction: compaction: group 300000@14846485652960182170: paniced while compacting 01HY03NN16FY7NGAVRG92WPGH1,01HY03NN47AHEX1HAK96CDCHQ0: unexpected seriesToChunkEncoder lack of iterations"
09:08:13 compact-working: ts=2024-05-16T07:08:13.01911052Z caller=main.go:171 level=error name=compact-working err="group 300000@14846485652960182170: paniced while compacting 01HY03NN16FY7NGAVRG92WPGH1,01HY03NN47AHEX1HAK96CDCHQ0: unexpected seriesToChunkEncoder lack of iterations\ncompaction\nmain.runCompact.func7\n\t/go/src/github.com/thanos-io/thanos/cmd/thanos/compact.go:440\nmain.runCompact.func8.1\n\t/go/src/github.com/thanos-io/thanos/cmd/thanos/compact.go:525\ngithub.com/thanos-io/thanos/pkg/runutil.Repeat\n\t/go/src/github.com/thanos-io/thanos/pkg/runutil/runutil.go:91\nmain.runCompact.func8\n\t/go/src/github.com/thanos-io/thanos/cmd/thanos/compact.go:524\ngithub.com/oklog/run.(*Group).Run.func1\n\t/go/pkg/mod/github.com/oklog/run@v1.1.0/group.go:38\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_arm64.s:1197\nerror executing compaction\nmain.runCompact.func8.1\n\t/go/src/github.com/thanos-io/thanos/cmd/thanos/compact.go:552\ngithub.com/thanos-io/thanos/pkg/runutil.Repeat\n\t/go/src/github.com/thanos-io/thanos/pkg/runutil/runutil.go:91\nmain.runCompact.func8\n\t/go/src/github.com/thanos-io/thanos/cmd/thanos/compact.go:524\ngithub.com/oklog/run.(*Group).Run.func1\n\t/go/pkg/mod/github.com/oklog/run@v1.1.0/group.go:38\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_arm64.s:1197\ncompact command failed\nmain.main\n\t/go/src/github.com/thanos-io/thanos/cmd/thanos/main.go:171\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:267\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_arm64.s:1197"
09:08:35
Error: No such object: c-issue6775-compact-working

09:08:35 Killing minio
--- PASS: TestCompactorIssue6775 (37.51s)
PASS

@GiedriusS and/or @MichaHoffmann do you mind giving a second look here pls? Thx


Method does not override method from its superclass

After integrating the module, when I run 'react-native run-android', the build fails at this error message, in the MSREventBridge class.
Versions

"react": "16.0.0",
"react-native": "0.50.3"

@kckunal2612 Hey, can you post in the exact error message to see which method is not overwritten? Thanks!

We just released version 0.8.0 , so just update your npm dependencies and it should resolves this issue.

Thanks for the reply ! So, I updated the dependencies (now on version 0.8.0) and now I get a different error in the debugger console.

Invariant Violation: If you would like receive events you have to define the reactTag in your contexts. Component: App

Here's my code (React Native and Android Native both) -
React Native
export default class App extends Component<{}> {

    _eventSubscription: ?EmitterSubscription;

    componentDidMount() {
        console.log("componentDidMount");
        // Register for an event that will be sent from the native side
        /* eslint-disable no-unused-vars */ // For some reason info is marked as unused :/
        this._eventSubscription = EventBridge.addEventListener(
            this,
            (name, info) => {
                /* eslint-enable no-unused-vars */
                console.log(
                    `Received event from native: ${name} with info: {JSON.stringify(info)}`
                );
            }
        );
    }
......
}

Android

private void sendNotification(Context context) {
        Log.e("sendNotification", "SHOW NOTIFICATION");
        // Emit event via MSREventBridgeModule
        WritableMap map = new WritableNativeMap();
        map.putString("rowSelected", "10");
        MSREventBridgeModule.emitEventContext(context, "eventName", map);
    }

@kckunal2612 I think the README is not up to date. I think in your case you have to import PropTypes from 'prop-types' and use for contextTypes:
static contextTypes = {
    rootTag: PropTypes.number,
};

You can also find more information about why the React team moved the PropTypes into an external lib in here: https://reactjs.org/docs/typechecking-with-proptypes.html

@kckunal2612 See my comment from above, that should resolve your issue. Otherwise let me know and we will reopen the issue. Thanks!

Hi. So that issue got solved when I followed your comment, but now I keep getting this error -

 E/unknown:ReactNative: Exception in native call java.lang.ClassCastException:
com.test.MainApplication cannot be cast to net.mischneider.MSREventBridgeInstanceManagerProvider
                                                                 at com.test.MainActivity.onEventCallback(MainActivity.java:49)

even though I have followed the example app given here.
Please see the gist below for the code -
https://gist.github.com/kckunal2612/1311ec0cfaff27c5ff2c1890a69c25a2

@kckunal2612  - Please make sure your Application implements MSREventBridgeInstanceManagerProvider
See - https://github.com/maicki/react-native-event-bridge/blob/master/example/android/app/src/main/java/com/eventbridgeexample/MainApplication.java

Worked perfectly now ! Thanks a ton ! :+1:

Awesome. Seems like @thorbenprimke was faster than me to figure out the last blocker :) Glad it works for you know.


change port to something more obscure

9966 is used pretty frequently with budo / beefy / etc. something else would be better.

fixed


'writer' Role can't update a Sequence

OrientDB Version: 3.0.7 and 3.2
Java Version: 8
OS: MacOs
Expected behavior
When I create a new database, and create a sequence, the writer user should be able to get the next value of the sequence.
Actual behavior
I get an exception stating that:
com.orientechnologies.orient.core.exception.OSecurityAccessException: User 'writer' does not have permission to execute the operation 'Update' against the resource: ResourceGeneric [name=CLASS, legacyName=database.class].OSequence

Steps to reproduce

Create a new database called test
CREATE SEQUENCE idseq TYPE ORDERED
SELECT sequence('idseq').next()

Additional Info
When I log into Studio as the root user, I can see that the writer role is set up as a "deny all but" role type. Under database.class.osequence only read is checked.  If I also check "update" then the SQL will work just fine.  Looking at the OSecurityShared class https://github.com/orientechnologies/orientdb/blob/f2e2240e215bf5d00caf15bb6e13e286e7401cf9/core/src/main/java/com/orientechnologies/orient/core/metadata/security/OSecurityShared.java#L422
The writer role is definitely only being created with Read Permissions for sequences.  Is this correct? It seems like sequences are not usable by the writer.

I am running into this issue again in version 3.2.
The error is now:
com.orientechnologies.orient.core.exception.OSecurityException: Cannot update record #8:0: the resource has restricted access due to security policiesDB name="test"

The root user, and a user with the admin role work just fine. A user with only the writer role can not update the sequence.
I should note that the following command does work: SELECT sequence('idseq').current()
@laa @lvca

Also. In 3.0.x I had a workaround as follows:
val writer = db.getMetadata.getSecurity.getRole("writer")
      writer.addRule(ORule.ResourceGeneric.CLASS, OSequence.CLASS_NAME, ORole.PERMISSION_READ + ORole.PERMISSION_UPDATE)

This seems to no longer work. I beleive it is due to the introduction of security policies.  The policy for writer for database.class.osequence" points to an OSecurityPolicy that has beforeUpdateandafterUpdateset tofalse`.  I have not found a way to update the security policy in the role through the Java API.


[Feature] support  Marimekko  chart, which is stack bar chart which has different width

What problem does this feature solve?

https://mp.weixin.qq.com/s/rzlYCu8LzYpIRV6oT35ziA
What does the proposed API look like?
暂无

support in 1.12.0


Delete the fingerprint on success.

https://github.com/tus/tus-js-client/blob/ebc5189eac35956c9f975ead26de90c896dbe360/lib/upload.js#L441
Take into account the following use case.
"After a file has been completely uploaded, it may happens that the user deletes it from the server, and then the same user decides to upload it again"
In such a case, the new file should be treated as a brand new file, with a new id, but if we don't remove the fingerprint from the storage, the client tries to upload using the same id.
Furthermore, the local storage keeps growing while the user loads files successfully!
The idea is to add something like the following, what do you think about it?
if (this.options.resume ) {
    // Remove stored fingerprint and corresponding endpoint,
    // a new upload of the same file must be treated as a different file
    Storage.removeItem(this._fingerprint);
}

"After a file has been completely uploaded, it may happens that the user deletes it from the server, and then the same user decides to upload it again"
In such a case, the new file should be treated as a brand new file, with a new id, but if we don't remove the fingerprint from the storage, the client tries to upload using the same id.

This is true but no the full story. When tus-js-client tries to resume an upload which has been deleted from the server it will remove the fingerprint from its storage and start a brand new upload (see
https://github.com/tus/tus-js-client/blob/master/lib/upload.js#L335-L361).

I agree, this could be a problem. Even if the fingerprint per upload is small, it will accumulate over this.

The idea is to add something like the following, what do you think about it?

I like it, would you be able to open a PR for this?


fix: links not working

It was just minor change for links to get worked, you can test it out from your end

Resolved issue https://github.com/pritipsingh/The-Productive-Champion/issues/6

Thank you for contributing @ravirupareliya :) Means a lot!!!


Added information about command line options

Added a link directing to a list of the command line options on the SSH website

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

This looks great to me.  Thank you for your contribution!


Silenced exception fix

If something bad happens before channel init, exception will never shown. Just removing unnecessary throwable.

Fixed in https://github.com/Steveice10/PacketLib/commit/ce140f43d619bfeafd8ae452b6e1fa3061d3671f
Rather than removing the exception catching, I fixed exception handling to actually fire the event.


Composer 2

Please make this plugin Composer 2 compatible.

Have not had an issue until today while attempting to upgrade Drupal core. I've been using Composer 2 since around the end of September.
Only happens when running update --with-all-dependencies.
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - composer/installers[v1.7.0, ..., v1.8.0] require composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
    - Root composer.json requires composer/installers ^1.2 -> satisfiable by composer/installers[v1.7.0, v1.8.0].

You are using Composer 2, which some of your plugins seem to be incompatible with. Make sure you update your plugins or report a plugin-issue to ask them to support Composer 2.

Based on the commit https://github.com/composer/installers/commit/d2a98321ab66945396ef147387f93eee4c05089f#diff-d2ab9925cad7eac58e0ff4cc0d251a937ecf49e4b6bf57f8b95aab76648a9d34, and the release notes in https://github.com/composer/installers/releases/tag/v1.9.0, the 1.9.0 release of this package is Composer 2.0 compatible.
The output shown in the comment above (composer/installers[v1.7.0, ..., v1.8.0]) suggests that the reporter has a specific ^1 version requirement (I got the same issue with an explicit requirement of "composer/installers": "1.7.0".
Therefore, the appropriate resolution should be to update requirement dependencies; this issue likely can be closed.

Composer.json:
"composer/installers": "^1.2"
Composer.lock:
"name": "composer/installers",
"version": "v1.9.0",

@jacobsaw , try: composer update drupal/core 'drupal/core-* composer/*' --with-all-dependencies
(I still maintain this is an issue with version/dependencies, rather than Composer 2 compatibility in this package).

@markfullmer - Thanks, that does return no errors!


Hide mouse pointer in full screen mode

The title pretty much says it all. Is this feature planned?

Implemented! :) Will be part of the next version.