WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Playwright version

1.12.3

Operating system

MacOS

What browsers are you seeing the problem on?

Firefox

Other information

Node: v14.17.0

Mac OS: 11.4

Firefox: 89

What happened? / Describe the bug

When i try to download file in Firefox, i get a 'openFile / saveToDisk' dialog box. Same code works fine in Chrome and Webkit without prompting to open / save the file.

I followed the documentation mentioned here to download file.

I can share the actual code privately if it helps you to troubleshoot the issue

Code snippet to reproduce your bug

playwright.config.js
====================
use: {
browserName: 'firefox',
launchOptions: {
downloadsPath: path.join(__dirname, 'downloads'),
},
acceptDownloads: true,
}

example.spec.js
===============
let elmFrame = page.frames().find(frame => frame.name() === 'submainframe');

const [download] = await Promise.all([
page.waitForEvent('download'), // wait for download to start
elmFrame.click('css=tr > td >> text=PlaywrightTest >> xpath=parent::td/parent::tr >> td >> css=img[alt="Download"]'),
]);

let downloadPath;
downloadPath = await download.path();
console.log(downloadPath);

Relevant log output

n/a

Issue 2:
Playwright version

1.13.0

Operating system

MacOS

What browsers are you seeing the problem on?

Firefox

Other information

Node.js v14.15.3

What happened? / Describe the bug

Hello!

I’m having trouble with the file uploading. The following snippet works OK in Chromium, but fails in the Firefox.

Filechooser window appears in FF (Juggler) by clicking on browseForFilesLink if page.waitForEvent('filechooser') is removed.

Filechooser window does not appear if page.waitForEvent('filechooser') exists.

Unfortunately, I cannot share a website link since it's private.

Code snippet to reproduce your bug

const frame: Frame = await this.getFrame();
const [fileChooser] = await Promise.all([
page.waitForEvent('filechooser'),
frame.click(this.browseForFilesLink),
]);
await fileChooser.setFiles(path);

Relevant log output

● FIREFOX_ItemImport_ › Item_is_imported_successfully_and_found_via_search

page.waitForEvent: Timeout while waiting for event "filechooser"
=========================== logs ===========================
waiting for event "filechooser"
============================================================

220 | async uploadFile(path: string): Promise<void> {
221 | const [fileChooser] = await Promise.all([
> 222 | page.waitForEvent('filechooser'),
| ^
223 | this.waitAndClick(this.browseForFilesLink),
224 | ]);
225 | await fileChooser.setFiles(path);

at GeneralPopup.<anonymous> (src/pages/generalPopup.ts:222:18)
at step (src/pages/generalPopup.ts:48:23)
at Object.next (src/pages/generalPopup.ts:29:53)
at src/pages/generalPopup.ts:23:71
at Object.<anonymous>.__awaiter (src/pages/generalPopup.ts:19:12)
at GeneralPopup.Object.<anonymous>.GeneralPopup.uploadFile (src/pages/generalPopup.ts:489:16)
at src/Tests/ItemSourcing/ItemImport.test.ts:42:28
at step (src/Tests/ItemSourcing/ItemImport.test.ts:33:23)
at Object.next (src/Tests/ItemSourcing/ItemImport.test.ts:14:53)
at fulfilled (src/Tests/ItemSourcing/ItemImport.test.ts:5:58)
Issue 1:
Context:

Playwright Version: 1.28.1

Operating System: Mac

Node.js version: 18.10

Visual Studio Code version: 1.73.1

Playwright for VSCode extension version: 1.0.1

Browser: Chromium

Describe the bug

When I click on "record at cursor" in one of my tests, the browser is opened but the page never loads. I'm stuck on about:blank.

Enregistrement.de.l.ecran.2022-11-30.a.13.55.24.mov

Issue 2:
System info

Playwright Version: 1.36.0-next

Operating System: Ubuntu 22.04

Browser: All

Other info: running the latest docker image mcr.microsoft.com/playwright:v1.36.0-alpha-jun-16-2023, but it also happens in other environments

Source code

Default example suite can be used.

Steps

run the tests in ui mode with a host + port provided e.g. npx playwright test --ui --ui-host=127.0.0.1 --ui-port=8007

using Chrome or firefox browser visit the host + port e.g. http://127.0.0.1:8007 to access the web ui

the path gets redirected to a to the trace view, with a randomly generated hahs identifier in the url. I.e. /trace/uiMode.html?ws=<random hash id>

restart the server

visit the root path / again in the browser

Expected

The web ui should load the (example) tests

Actual

The ui doesn't load and some errors are thrown in the console.

I pinned this down to the redirect here using a 301 status code.

This means the browser will cache the redirect indefinitely.

The effect is that the browser will now keep redirecting to the trace id of the initial run. Which in turn causes an error when the app tries to connect to the ws interface using that stale identifier.

Current workaround is to use the browser devtools and disable caching in the network tab, but that is not ideal.

Proposed solution is to use a 307 redirect, which would not be cached indefinitely.
Issue 1:
Device: Nexus4

Browser: Chrome32

To replicate:

Open http://getbootstrap.com/2.3.2/ in Android Chrome

Click on menu button on the top right of the page to open the menu, all links display properly.

Close the menu by clicking on the menu button.

Now, opens the menu the SECOND time. All links will disappear.

Issue 2:
How to reproduce:

Open bootstrap [ http://getbootstrap.com/2.3.2/ ] or any website using bootstrap in chrome on mobile android in portrait mode.

then click on menu to open, then close & then click again to open

this time the navigation is coming blank even thought the links are there and can be clicked but can't be seen

Works fine in landscape mode.

Screenshot:
Issue 1:
xref #8640 #12699 #13361 #13410

There's been discussion of a few overlapping uses of Categorical:

as 'true' categorical data with a known set of values

as 'lazy' categorical data which adds new categories as needed

as an interned string data type, with no particular categorical interpretation

Option 1 is currently well-supported. Option 2 can be achieved explicitly by union_categorical, see #13361 #13410, but will not happen automatically e.g. when setting values or concatenating, see #12699. Option 3 is similar to 2, and has been discussed as a new String type, see #8640, but may have different semantics to 2.

While I completely agree that option 1 should be the default, I'd like to see more support for option 2 if possible; there are cases where I really do want to work with categorical data, but I don't yet know what the categories are, e.g. when concatenating a table together from several different source files.

One option would be to mimic Matlab's 'protected' flag for categorical data. By default, a Categorical would be created protected, and throw errors when performing actions which implicitly change the category set. However, the user could choose to declare a Categorical as unprotected, in which case these operations would be performed as intended.

While this behaviour could be achieved with the proposed String type, it's unclear whether that type would share the Categorical API, or be efficiently convertible to Categorical. Having the behaviour as part of Categorical would allow the user to build up a Categorical iteratively, from multiple sources, and then quickly mark it protected once the category set is known.

Issue 2:
Currently, Categorical serves two main purposes

A type for expressing data from a fixed set of categories

A memory efficient storage format for low-cardinality objects

This proposal is to add a new extension type (let's call it DictEncodedArray

for now) for the second use case. The storage format would be the same as

Categorical: an Index of the unique "keys" (categories) and an array of codes.

Much of the implementation would be shared. But they would have different

semantics on operations

concat (union by default)

groupby (unobserved categories would be dropped by default)

value_counts (unobserved categories would be dropped by default)

This is most useful for strings, but could even be useful for storing a large

array of 64-bit precision items (store the 64-bit items once, then use an int16

or int32 array for the codes).
Issue 1:
This code:

enum Command {
Create{qname:~str},
Help,
Unknown,
}

fn main() {
let val = Unknown;

match val{
Create{qname: qname} => {
print(fmt!("Create %?", qname));
}
Help => {
print(~"Help");
}
_ => {
print(~"Other");
}
}
}

Gives segmentation fault in runtime.

Issue 2:
Running this test.rs causes a segfault on Ubuntu 12.10 (compiled with incoming bda4dd3):

enum Foo {
Bar,
Baz {a: uint}
}

impl Foo {
fn equals(&self, other: &Foo) -> bool {
match *self {
Bar => match *other { Bar => true, _ => false },
Baz {a: ref sa} => match *other {
Baz {a: ref oa} => sa == oa,
_ => false
}
}
}
}

pub fn main() {
let x = Baz {a: 4};
let y = Bar;
x.equals(&y);
}

Valgrind says this about it:

==16637== Thread 2:
==16637== Use of uninitialised value of size 8
==16637== at 0x400AE8: uint::__extensions__::meth_2509::eq::_693b4a7b2ad824e5::_00 (test.rs:1)
==16637== by 0x400A9D: ptr::__extensions__::eq_2502::_37b8589111841e1::_00 (test.rs:1)
==16637== by 0x400A3B: __extensions__::meth_2459::equals::_e3a12daf95a36916::_00 (test.rs:11)
==16637== by 0x400B68: main::_6706ae2286769fe::_00 (test.rs:21)
==16637== by 0x400B9D: _rust_main (test.rs:12)
==16637== by 0x535E4C3: task_start_wrapper(spawn_args*) (rust_task.cpp:162)
==16637==
==16637== Invalid read of size 8
==16637== at 0x400AE8: uint::__extensions__::meth_2509::eq::_693b4a7b2ad824e5::_00 (test.rs:1)
==16637== by 0x400A9D: ptr::__extensions__::eq_2502::_37b8589111841e1::_00 (test.rs:1)
==16637== by 0x400A3B: __extensions__::meth_2459::equals::_e3a12daf95a36916::_00 (test.rs:11)
==16637== by 0x400B68: main::_6706ae2286769fe::_00 (test.rs:21)
==16637== by 0x400B9D: _rust_main (test.rs:12)
==16637== by 0x535E4C3: task_start_wrapper(spawn_args*) (rust_task.cpp:162)
==16637== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==16637==
==16637==
==16637== Process terminating with default action of signal 11 (SIGSEGV)
==16637== Access not within mapped region at address 0x0
==16637== at 0x400AE8: uint::__extensions__::meth_2509::eq::_693b4a7b2ad824e5::_00 (test.rs:1)
==16637== by 0x400A9D: ptr::__extensions__::eq_2502::_37b8589111841e1::_00 (test.rs:1)
==16637== by 0x400A3B: __extensions__::meth_2459::equals::_e3a12daf95a36916::_00 (test.rs:11)
==16637== by 0x400B68: main::_6706ae2286769fe::_00 (test.rs:21)
==16637== by 0x400B9D: _rust_main (test.rs:12)
==16637== by 0x535E4C3: task_start_wrapper(spawn_args*) (rust_task.cpp:162)

Note that the following variants of the last line of main do not cause a segfault:

x.equals(&x);

y.equals(&y);

y.equals(&x);
Issue 1:
I was wondering how it's the best way to render server-side (without rendering this on the client) AND handle the state changes. What I mean here is how to get the HTML from a server component that has a state changing.

Example:

A server gets a requests to generate an HTML

The server 'requires' a react component, passing some props

The react component renders in the server, but it has to do an Ajax/Socket query to get some info. The event is sent and the response comes later.

The react component changes the state, changing the output

The HMTL generated is ready and with the latest state changes.

What's happening here is that ReactDOM.renderToStaticMarkup(), as expected, doesn't wait for the component to finish the state changes (in this case, wait for the data and re-render).

How can I achieve this? Doing all the queries first and passing all the data as props? Is this the only way?

Thanks!

Issue 2:
Do you want to request a feature or report a bug?

Bug.

What is the current behavior?

render() runs immediately only when provided unique props or on initial, main-parent rendering component, in v. 16.4.0.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

When render() executed immediately after being called, it followed a code path through shouldComponentUpdate(), and when it has delayed execution because of non-unique props, it followed a code path through componentWillMount().

When it worked: shouldComponentUpdate() immediately ran after calling ReactDOM.render(childcomponent, parentcomponent);.

When it didn't work: componentWillMount() ran after the current function of the parentcomponent had finished executing.

Please let me know if this is insufficient info.

What is the expected behavior?

In ReactJS, 15.6.2, render() always runs, and runs immediately, whether its props are unique or not.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

This was last working in 15.6.2. It is not working in 16.4.0.
Issue 1:
Deno bundle is awesome, I can drop countless NPM tooling for a non-deno specific project.

One question is how to generate typescript definition files from the bundler, as that would provide the interfaces to code against the es module file generated by the bundle command.

It seems that specifying a config as below has no effect.

{
"compilerOptions": {
"declaration": true,
"sourceMap": true
}
}

Issue 2:
With #3352, bundles are going to be a mechanism to distribute "libraries" in Deno. It is logical that someone might want to use a distribution bundle in another Deno workload (or consume it in other runtimes) and would want to have type safe consumption of those files, therefore we should generate the declarations along with a bundle.

Related to #2475.
Issue 1:
It seems that if you're conditionally rendering between two elements then they can't have a different root node, for example switching between an input and a div. In order to get around the issue you have to wrap everything in a common container element for React to be able to handle it.

Sample plunkr is here which demonstrates the behavior. I'd expect in this case it to switch between showing 'Test' and 'Test 2' when activating the checkbox, instead it ends up duplicating the node.

Interestingly I don't get any errors in this simplified test case, in a more complex app React complains about two unrelated nodes sharing the same React id after activating the checkbox.

Issue 2:
Hi,

I am pretty new to react, and I am trying to build a DIV that requests an image-scaling service on the backend for images in specific resolutions, to do this I need to use CSS image-set, this CSS value need vendor prefixes, but the CSS key does not, my problem is that I can't have duplicate keys in the style object. I ended up manually setting the style attribute in componentDidUpdate, but it is a hack to get around the system. I suggest that you could perhaps also expect an array of key value pairs, then I could do like this:

[{backgroundImage : 'value1'}, {backgroundImage : 'value 2'}]

a specific example of the css I am trying to modify can be found here.

height : 818px;
width : 1440px;
background-size : cover;
background-image : url(https://images.blockbuster.dk/movie/divergent?width=1440&height=818);
background-image : -webkit-image-set(url(https://images.blockbuster.dk/movie/divergent?width=1440&height=818) 1.0x, url(https://images.blockbuster.dk/movie/divergent?width=2880&height=1636) 2.0x);
background-image : -moz-image-set(url(https://images.blockbuster.dk/movie/divergent?width=1440&height=818) 1.0x, url(https://images.blockbuster.dk/movie/divergent?width=2880&height=1636) 2.0x);
background-image : -ms-image-set(url(https://images.blockbuster.dk/movie/divergent?width=1440&height=818) 1.0x, url(https://images.blockbuster.dk/movie/divergent?width=2880&height=1636) 2.0x);
background-image : -o-image-set(url(https://images.blockbuster.dk/movie/divergent?width=1440&height=818) 1.0x, url(https://images.blockbuster.dk/movie/divergent?width=2880&height=1636) 2.0x)
Issue 1:
If i am trying to change the font size with CMD + in the React Editor, my console is opening and i am getting the following error:

I also get into an endless loop and so i can't close the console and have to restart the wohle editor.

Issue 2:
Changing font size (or any font property, really) in the settings page on Mac 10.9.2 causes a crash with React enabled (doesn't happen with React disabled).

The dev tools can't be closed (will pop open again) and can't change the devtools tab (jumps back to console).

It looks like it has something to do with the cursor blink.

Message: Uncaught Error: You must assign a non-zero lineHeight before calling ::getVisibleRowRange()

Stack:

Uncaught Error: You must assign a non-zero lineHeight before calling ::getVisibleRowRange() /Applications/Atom.app/Contents/Resources/app/src/display-buffer.js:350
module.exports.DisplayBuffer.getVisibleRowRange /Applications/Atom.app/Contents/Resources/app/src/display-buffer.js:350
module.exports.DisplayBuffer.intersectsVisibleRowRange /Applications/Atom.app/Contents/Resources/app/src/display-buffer.js:360
module.exports.DisplayBuffer.selectionIntersectsVisibleRowRange /Applications/Atom.app/Contents/Resources/app/src/display-buffer.js:367
module.exports.Editor.selectionIntersectsVisibleRowRange /Applications/Atom.app/Contents/Resources/app/src/editor.js:2006
(anonymous function) /Applications/Atom.app/Contents/Resources/app/src/cursors-component.js:31
module.exports.React.createClass.render /Applications/Atom.app/Contents/Resources/app/src/cursors-component.js:44
(anonymous function) /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactCompositeComponent.js:1394
(anonymous function) /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactCompositeComponent.js:1326
ReactCompositeComponentMixin._performComponentUpdate /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactCompositeComponent.js:1264
ReactCompositeComponentMixin._performUpdateIfNecessary /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactCompositeComponent.js:1207
Mixin.perform /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/Transaction.js:159
ReactComponent.Mixin.performUpdateIfNecessary /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactComponent.js:478
ReactCompositeComponentMixin.performUpdateIfNecessary /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactCompositeComponent.js:1157
enqueueUpdate /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactUpdates.js:107
ReactCompositeComponentMixin.replaceState /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactCompositeComponent.js:1041
ReactCompositeComponentMixin.setState /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactCompositeComponent.js:1020
module.exports.React.createClass.toggleCursorBlink /Applications/Atom.app/Contents/Resources/app/src/cursors-component.js:71
boundMethod /Applications/Atom.app/Contents/Resources/app/node_modules/react/lib/ReactCompositeComponent.js:1434
Issue 1:
As seen in the screen shot, there are tabs getting cut off (on the right) or are not shown in the tab bar so you can only reach them with keyboard short cuts.

It would be great if you could scroll tabs too.

Issue 2:
Windows 7, Atom version 0.115.0

Opening a large number of files (21 <) causes new tabs to be opened off screen.

Ctrl + Tabbing through opened tabs does not bring the current tab on screen.
Issue 1:
Environment

Windows build number:
Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable):
0.6.2951.0

Feedback Hub link:

https://aka.ms/AA6gvsu

Steps to reproduce

Open Windows Terminal in one screen then move the window to another screen, the app will crash.

Here's the error log from the Event Viewer:

Faulting application name: WindowsTerminal.exe, version: 1.0.1910.22001, time stamp: 0x5daf7ab2
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.449, time stamp: 0xb90db728
Exception code: 0xc000027b
Fault offset: 0x0000000000712ec0
Faulting process id: 0x3f4c
Faulting application start time: 0x01d59330b1915a64
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 135f8f3c-f6b8-4100-a6a8-448f12eb7247
Faulting package full name: Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Issue 2:
Environment

Windows build number: Microsoft Windows [version10.0.18362.175]
Windows Terminal version (if applicable): Version: 0.2.1831.0

Any other software?
Anaconda

Steps to reproduce

open terminal

input-> "conda activate python3.6" (my conda environment name which use python3.6.8 )

input->"python"

the env is base (use python3.7) rather than python3.6

Expected behavior

use cmd:

Actual behavior
Issue 1:
Hi,

I'm building some experiment with chrome canary and everything is fine. But when I tried with chrome 20.0.1132.57 I was surprised to have something like 1 frame per second. Commenting the texture.needsUpdate made everything run again at a comfortable 60fps so I created a jsfiddle to make sure this is what was causing the slowdown.

The jsfiddle confirmed that it was this line which was causing the problem, but I find it strange that is has so much impact. Firefox too doesn't seem to like the needsUpdate flag.

http://jsfiddle.net/sDUZ5/3/

You can simply set the first line to true to enable the needsUpdate. On my machine this cause the framerate to go from 60fps to 9fps.

Is there anything wrong with my code? Any idea if maybe the next three.js release would help in this scenario?

Issue 2:
Just sharing a change I made in https://Clara.io. I killed our support for Lambert materials a few months ago. Instead I just tell people to create Phong materials with the specular color black to reproduce the behavior of Lambert.

I'd suggest doing the same change in Three.JS. Having two shaders with tons of duplicated code is a bit of a pain when really there is almost no difference between the two.