WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Minimal test case for this issue is here: https://github.com/KamilSzot/atom-shell-windows-bash-problem

Windows bash attempts to use slashes instead of backslashes and that probably interferes somehow with path calculations. Maybe there's some point there is a relative path calculated between directory where atom-shell lies and where the application lies?

Issue 2:
Electron Version (output of node_modules/.bin/electron --version):

Expected Behavior

PDF must be viewable

Actual behavior

It says 'Couldn't load plugin'

To Reproduce

I've set the plugins to true on BrowserWindows->webPreference but nothing works

Screenshots

Additional Information
Issue 1:
Summary of the new feature/enhancement

I use this program for watching multiple video feeds with VLC next to each another.

I currently have 4 zones.

It'd be great if I could automatically fill my feed at the assigned position from 1 to 4, every time I start an instance of VLC, without having to move the windows there manually.

There could also be an argument requiring the path of the application to make sure only a specific application (VLC in my case) is linked and dragged to those zones (excluding others)

So that every app can be linked to a specific window position of a specific profile (without having to switch profile and having to drag them manually to set their position)

Also, an "Always on Top" check box would be nice to prevent some windows from going in the background unless minimized.

Issue 2:
Hi all,

It would be great to choose what apps to show up on startup within a specific layout using FancyZones. For example, I have a setup of two displays and three virtual desktops and I need to open my apps and reposition them on the screen each time I boot-up my system.
Issue 1:
Context:

Playwright Version: 1.2.1

Operating System: Mac

Node.js version: 12.14

Browser: Chromium

Describe the bug

When navigating to PDF that is delivered with the header Content-Disposition: inline, Playwright opens in a new page and uses the embedded Chromium PDF viewer.

From this point it's impossible to get the actual PDF content. Even when inspecting the response event, the actual response object's body only contains the HTML presenting the embedded viewer with an inline ID representing the PDF.

Whilst I'm sure there are some situations that would warrant the in-browser PDF viewer being turned on, I would guess that having these download by default would be the more common use-case within Playwright.

Issue 2:
Hi!

On creation of a browser or context (permanent or otherwise), is it possible to set the config value AlwaysOpenPdfExternally or the equivalent plugins.always_open_pdf_externally preference?

I've tried a kludgy solution that has me navigate to chrome://settings/content/pdfDocuments on load and click the option. But we need to use Chromium in headless to export PDFs of pages as well as download PDF files that the browser always opens in its embedded viewer… and there seems to be no way of getting the actual PDF content out of that viewer.

Any help would be appreciated.

Cheers, Wayne
Issue 1:
The following piece of code contains a redundant mut, but triggers no warning:

fn main() {
let mut a;
a = 13;
println!("{}", a);
}

Issue 2:
If you have two methods in an impl block, each containing an enum (with the same name), each containing at least one value with the same name, rustc gives the same LLVM symbol for the two of them and fails, as it does not include the method name in the symbol name.

Minimal test case:

pub struct Foo;
impl Foo {
pub fn foo() {
enum Panic { Common };
}
pub fn bar() {
enum Panic { Common };
}
}
fn main() {
}

error: internal compiler error: duplicate LLVM symbol: _ZN14__extensions__5Panic6Common7descrim17_32f9788ad4163dc87_0$x2e0E
rust: task failed at 'explicit failure', /home/chris/vc/rust/src/libsyntax/diagnostic.rs:95
rust: task failed at 'explicit failure', /home/chris/vc/rust/src/librustc/rustc.rs:355
rust: domain main @0x19ffd90 root task failed
leaked memory in rust main loop (1 objects)
rustc: /home/chris/vc/rust/src/rt/memory_region.cpp:192: memory_region::~memory_region(): Assertion `false' failed.
Issue 1:
[Enter steps to reproduce below:]

Open atom

Grab popcorn

Atom Version: 0.169.0

System: linux 3.13.0-44-generic

Thrown From: Atom Core

Stack Trace

Uncaught Error: EACCES, open '/home/lloir/.atom/compile-cache/cson/5af7724b023a6274b520f79f04fb798a67319ca7.json'

At fs.js:75

Error: EACCES, open '/home/lloir/.atom/compile-cache/cson/5af7724b023a6274b520f79f04fb798a67319ca7.json'
at Error (native)

Commands

Config

{
"core": {
"disabledPackages": [
"metrics"
]
},
"editor": {}
}

Installed Packages

# User
No installed packages

# Dev
No dev packages

Issue 2:
Uncaught Error: UNKNOWN, open 'c:\Users\j-zhang.atom\compile-cache\cson\5c55bdf15d2eae5f441df1261e9dc3c0720aca1a.json'

Atom Version: 0.161.0

System: Windows 7 Enterprise

Thrown From: Atom Core

Steps To Reproduce

...

...

Stack Trace

At fs.js:75

Error: UNKNOWN, open 'c:\Users\j-zhang\.atom\compile-cache\cson\5c55bdf15d2eae5f441df1261e9dc3c0720aca1a.json'
at Error (native)
Issue 1:
As of React v15.2.0, the provided fiddle is throwing the "Missing React element for debugID" warning, which has been described as an internal (i.e. not user-facing) React warning.

https://jsfiddle.net/s4c36s0n/

This warning was not present in React v15.1.0.

(I make no claim that this is a sane usage pattern, only that it exists in real-world components and that it's an unexpected failure case.)

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

Bug

What is the current behavior?

As reported by @adamryvola in #6869 (comment), React is displaying a warning Warning: ReactComponentTreeDevtool: Missing React element for debugID 2 when building stack when another component is rendered in componentWillMount

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/reactjs/69z2wepo/).

import React, {Component} from 'react';
import ReactDOM from 'react-dom';

const container = document.getElementById('container');
const menuContainer = document.getElementById('menu-container');

export default class App extends Component {

componentWillMount() {
ReactDOM.render(<div />, menuContainer); // <= Trigger the warning
}

render() {
return (
<div>
<div>App</div>
</div>
);
}
}

ReactDOM.render(<App />, container);

JSFiddle: https://jsfiddle.net/0n3a6vp9/

What is the expected behavior?

According to @gaearon this warning is "against internal bugs in React, it's not meant for users" (source: #6869 (comment)) so this warning should not be triggered.

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

React 15.2.0, no issue with React 0.14.7
Issue 1:
In 3.5 the getPropertyPath does not return the correct path.

2.5.0 output:

[test1]:This value should not be blank.
[test1].[test2]:This value should not be blank.

2.4.6 output:

[test1]:This value should not be blank.
[test2]:This value should not be blank.

Test script:

<?php
use Symfony\Component\Validator;
require_once __DIR__ . '/vendor/autoload.php';

$constraint = new Validator\Constraints\Collection([
'fields' => [
'test1' => new Validator\Constraints\NotBlank(),
'test2' => new Validator\Constraints\NotBlank(),
],
]);

$data = [
'test1' => '',
'test2' => '',
];

$validator = Validator\Validation::createValidator();
$violations = $validator->validateValue($data, $constraint);
foreach ($violations as $violation) {
echo $violation->getPropertyPath() . ':' . $violation->getMessage() . '<br>' . PHP_EOL;
}

Issue 2:
Hello,

When using Validator 2.5 to validate an array of scalars, the propertyPath of the returned violations has really strange values.

Consider the following script:

<?php

require 'vendor/autoload.php';

use Symfony\Component\Validator\Constraints;
use Symfony\Component\Validator\Validation;

$constraints = array(
'foo' => array(
new Constraints\NotBlank(),
new Constraints\Date()
),
'bar' => new Constraints\NotBlank()
);

$collectionConstraint = new Constraints\Collection(array('fields' => $constraints));

$validator = Validation::createValidatorBuilder()
->setApiVersion(Validation::API_VERSION_2_5)
->getValidator();

$value = array(
'foo' => 'bar'
);

$violations = $validator->validate($value, $collectionConstraint);

foreach ($violations as $violation) {
var_dump($violation->getPropertyPath());
}

Output:

string(11) "[foo].[foo]"
string(17) "[foo].[foo].[bar]"

If I set Validation::API_VERSION_2_4 and call the old validateValue method, it outputs:

string(5) "[foo]"
string(5) "[bar]"

Is this something expected ?
Issue 1:
Let's say I use a data file data.txt containing:

a b c
d e f

If I do (in Python 3.4):

import numpy as np
data = np.loadtxt('data.txt', dtype='U')
print(data)

I get:

[["b'a'" "b'b'" "b'c'"]
["b'd'" "b'e'" "b'f'"]]

Note that the b is actually part of the string, so there is something wrong here. The same happens if I use dtype='U'. I am using Numpy dev as of a02f5c8.

Issue 2:
Environment

Python: Version 3.3 (python.org release) on OS X Mountain Lion

numpy: Cloned from git master

When calling numpy.loadtxt on file containing strings as follows:

import numpy as np
datestxt = np.loadtxt("NYSE_dates.txt", dtype=str)
print(datetxt)

Where NYSE_dates.txt is simply a list of dates (could be anything really):

7/5/1962
7/6/1962
7/9/1962
...
12/29/2020
12/30/2020
12/31/2020

Output is:

["b'7/5/1962'" "b'7/6/1962'" "b'7/9/1962'" ..., "b'12/29/2020'"
"b'12/30/2020'" "b'12/31/2020'"]

As you can see, all the strings have been bytes-casted, then stringified through conv, as you would get the same result from str(str('12/31/2020').encode('latin1')), per conv & compat.asbytes.

After looking at the code, it appears that all strings are bytes-casted with asbytes(...) pretty much throughout, as for example in split_line(...), so this must mean every routine in the module is broken.
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.175]

Windows Terminal version 0.0.1.0

Steps to reproduce

I am using 2 screens with the same resolution(1080p). When i drag the terminal to the secondary display, the boundaries gets out of screen. For example see attached photos below

Expected behavior

This behavior is from my main display

Actual behavior

This is from my secondary display(notice that everything is dragged outside of my monitor pixels, even the text and some portion of the tabs).

Issue 2:
Environment

Windows build number: [run "ver" at a command prompt]
Windows Terminal version (if applicable):

Any other software?

Microsoft Windows [Version 10.0.18892.1001]

Steps to reproduce

Press the maximize button when the terminal is on a non-primary monitor

Expected behavior

All text should be visible

Actual behavior

A portion of the leftmost column of cells is cut off.

The text is fine when maximized on the primary monitor.
Issue 1:
"Requests is not accepting feature requests at this time." I see.

But really guys, would it be too much to ask to get this implemented into the Sessions? I could submit a PR. Axios and many other libraries support this already, and it comes it really handy.

I know there are workarounds, subclass it and what not but that is so ugly when it could be built into the module with ~5 lines of code.

Please 💯

Thanks

Issue 2:
It seems that my code memory used is increase slowly,I find that even the simplest code will lead this.

Expected Result

memory won't slowly increase

Actual Result

memory is slowly increase, running after one hour

Reproduction Steps

import requests
def f():
while 1:
s = requests.get('https://www.baidu.com')
text = s.text

if __name__ == '__main__':
f()

System Information

$ python -m requests.help

{
"chardet": {
"version": "3.0.4"
},
"cryptography": {
"version": "2.3.1"
},
"idna": {
"version": "2.7"
},
"implementation": {
"name": "CPython",
"version": "3.6.6"
},
"platform": {
"release": "10",
"system": "Windows"
},
"pyOpenSSL": {
"openssl_version": "1010009f",
"version": "18.0.0"
},
"requests": {
"version": "2.19.1"
},
"system_ssl": {
"version": "100020ff"
},
"urllib3": {
"version": "1.23"
},
"using_pyopenssl": true
}
Issue 1:
After merge of https://github.com/kennethreitz/requests/pull/2379, to allow filenames to be int types, unicode filenames are no longer recognized under Python 2.

This checks that the filename is a builtin str, which has different behaviour on Python 2 and Python 3:

requests/utils.py:118: if name and isinstance(name, builtin_str) and name[0] != '<' and name[-1] != '>':

In requests/compat.py, builtin_str is defines as str, which is non-unicode bytes in Python 2 and unicode in Python 3. Perhaps the check should be against basestring, or is this change in behaviour intended?

Issue 2:
Starting from 2.0 requests does not send filename attribute of Content-Disposition header for multipart files with unicode names. Instead of this attribute with name filename* is sent.

# requests 1.2.3
>>> requests.post('http://ya.ru', files={'file': (u'файл', '123')}).request.body
'--db7a9522a6344e26a4ca2933aecad887\r\nContent-Disposition: form-data; name="file"; filename="\xd1\x84\xd0\xb0\xd0\xb9\xd0\xbb"\r\nContent-Type: application/octet-stream\r\n\r\n123\r\n--db7a9522a6344e26a4ca2933aecad887--\r\n'

# requests 2.0
>>> requests.post('http://ya.ru', files={'file': (u'файл', '123')}).request.body
'--a9f0de2871da46df86140bc5b72fc722\r\nContent-Disposition: form-data; name="file"; filename*=utf-8\'\'%D1%84%D0%B0%D0%B9%D0%BB\r\n\r\n123\r\n--a9f0de2871da46df86140bc5b72fc722--\r\n'

And this is a big problem, because looks like some systems does not recognize such fields as files. At least we encountered a problem with Django. Django places entire file's content in request.POST instead of request.FILES. It is clear from sources:

https://github.com/django/django/blob/1.7c1/django/http/multipartparser.py#L599-L601
Issue 1:
Glide Version/Integration library (if any): 3.6.0-SNAPSHOT

Device/Android Version: S4/4.4

Issue details/Repro steps: ImageVideoModelLoader acquires both InputStream and ParcelFileDescriptor for almost everything:

load(R.raw.svg):

android.resource://net.twisterrob.app/raw/svg

load(ContentUris.withAppendedId(ITEM_URI, id).toString()):

content://net.twisterrob.app/item/1579

load(new File(new File(context.getFilesDir(), "images"), "item.jpg").toString()):

file:///data/data/net.twisterrob.app/files/images/item.jpg

The realization that this happens came when I was profiling an activity startup and saw that there are two 800ms database accesses happening in the background. The 800ms was my bad (missing DB indices), but at least it was clearly visible:

I'm transitioning to a ContentProvider to give access to the images with openFile, so the above image displays how content://net.twisterrob.app/item/1579 looks like when handed to Glide. I was able to reduce the time required to query the PFD/IS but some may not be that lucky (web backend). Doubling the load time seems unnecessary and as you can see the image could have been already read if just queried once.

The case with R.raw.svg is even worse since the IS is already ready and trying to fetch a PFD fails all the time, because of a limitation on raw resources (only aapt uncompressed one can give a PFD).

Why is it needed to acquire the ParcelFileDescriptor when you already have an InputStream?

Is there an easy way to avoid going through ImageVideoModelLoader?

Is there a way for to always use only one or the other? (I guess with some .decoder magic).

Issue 2:
It should instead let ImageVideoWrapper lazily open these resources when necessary.
Issue 1:
i tried installing the react expo cli using "npm install -g expo-cli"

and i recieved this error in my log file

21640 error cb() never called!

21641 error This is an error with npm itself. Please report this error at:

21642 error https://npm.community

Issue 2:
What / Why

NPM reports unmet dependency after performing a recursive/deep update

When

After running npm --depth 9999 update

Where

n/a

How

Current Behavior

After update, npm ls reports a lot of missing/unmet dependencies, for example:

├─┬ @semantic-release/exec@3.3.8
│ ├── @semantic-release/error@2.2.0 deduped
│ ├── aggregate-error@3.0.1 deduped
│ ├─┬ debug@4.1.1
│ │ └── ms@2.1.2
│ ├─┬ UNMET DEPENDENCY execa@3.3.0

npm ERR! missing: execa@3.3.0, required by @semantic-release/exec@3.3.8

Steps to Reproduce

Create a folder locally and run npm init

Install a package with more than one level of dependencies, e.g. npm i -D @semantic-release/exec

Wait for one of their deep dependencies to get a newer version

Run npm --depth 9999 update

Expected Behavior

There shouldn't be any unmet dependencies. Updates are performed according to the package.json file of their parent or any npm-shrinkwrap.json of their ancestor.

In another word, it should act as if there is no package-lock.json and proceed to resolve all dependencies, install/update/remove as necessary, and then update the lockfile with the resolved tree.

Who

n/a

References

n/a
Issue 1:
Currently it's problematic to use Cucumber with Playwright because:

you can't use --ui mode

you can't use Selenium grid for parallelization

etc...

For example Cypress has plugin for that (see https://github.com/badeball/cypress-cucumber-preprocessor).

Cucumber is very popular BDD framework and I see many questions regarding Cucumber with Playwright (example of question https://stackoverflow.com/questions/76035903/using-playwright-ui-mode-with-cucumber)

So maybe it's possible to have similar plugin to use Cucumber js + Playwright js

Issue 2:
Our team has a case to use the BDD test, Playwright has any plan to add their own BDD implementation using the playwright test runner? That would be great if to have.

This can help many people who want to use BDD along with Playwright. That's where cucumber became popular 😉
Issue 1:
Situation

Let's consider the surface expr obtained when parsing short function forms

f(x::A) = body # (= (call f (:: x A)) body)
f(x::A, y::B) = body # (= (call f (:: x A) (:: y B)) body)

f(::A) = body # (= (call f (:: A)) body)
f()::A = body # (= (:: (call f) A) body)
f(::A)::B = body # (= (:: (call f (:: A)) B) body)

f(x::A) where A = body # (= (where (call f (:: x A)) A) body)
f()::A where A = body # (= (:: (call f) (where A A)) body)
f(::A)::B where A = body # (= (:: (call f (:: A)) (where B A)) body)
f(::A)::B where B = body # (= (:: (call f (:: A)) (where B B)) body)
f(::A)::B where {A,B} = body # (= (:: (call f (:: A)) (where B A B)) body)

As soon as we add a return type and a where clause, the return type predates the where clause.

Statistically, it seems that the where clause can concern either input type, io type more frequently that only output type.

If we want to obtain a where clause on the whole sig, we have to parenthesis things

(f()::A) where A = body # (= (where (:: (call f) A) A) body)
(f(::A)::B) where B = body # (= (where (:: (call f (:: A)) B) B) body)
(f(::A)::B) where {A,B} = body # (= (where (:: (call f (:: A)) B) A B) body)

Harder to read and understand.

Also notice that it does not follow the default for the long form function

# long form, where above call by default
function f(::A)::B where {A,B}; body end # (function (where (:: (call f (:: A)) B) A B) body)

# short form, where above call if parenthesised otherwise under
(f(::A)::B) where {A,B} = body # (= (where (:: (call f (:: A)) B) A B) body)
f(::A)::B where {A,B} = body # (= (:: (call f (:: A)) (where B A B)) body)

Proposal

let's the where clause being bound to the whole sig by default when both return type and where clause are present.

Issue 2:
In other words, ::ReturnType is incompatible with where clauses in the short function form declarations.

I thought an exemple was more clear than my words in the title.
Issue 1:
While editing a .md file, the highlight behaves incorrectly after *> occured in text. The whole file is displayed in pink after that. Please see the screenshot.

v 1.0.0 .deb package (it was also present in 0.188)

Issue 2:
If one wants to write a * as a normal char, not as a bold or italic start char, things will go wrong.

Even,when there is no newline after the line contains the *

When the * is the last char of one line, everything is ok...
Issue 1:
Dear Fabien,

Thank you for uploading your slides on the symphony hack day in Berlin.

I played around with the expression language and the got the error, that in the router the request is missing.

I created a fork of symfony standard to reproduce the problem:

https://github.com/sebastianblum/symfony-standard/tree/routing-condition

If I add the condition in the routing.yml

condition: "request.getMethod() in ['GET', 'POST'] and request.headers.get('User-Agent') matches '/firefox/i'"

see https://github.com/sebastianblum/symfony-standard/blob/routing-condition/src/Acme/DemoBundle/Resources/config/routing.yml

then I got the following error:

FatalErrorException: Error: Call to a member function getMethod() on a non-object

See complete stack trace https://gist.github.com/sebastianblum/7417064

Issue 2:
Symfony version(s) affected: 4.2.2

Description

The unique constraint validation does not work when the form collection entry type is mapped with an entity that have an unique constraint.

How to reproduce

Parent entity:

/**
* @ORM\Entity()
*/
class Family
{
/**
* Many Families has Many Attributes
*
* @var ArrayCollection
*
* @ORM\OneToMany(targetEntity="App\Entity\FamilyAttribute", mappedBy="family", orphanRemoval=true, cascade={"persist"})
* @Assert\Valid()
*/
private $familyAttributes;
}

Child entity:

/**
* THIS IS A JOIN TABLE WITH ADDITIONAL ATTRIBUTES
*
* @ORM\Entity()
* @ORM\Table(uniqueConstraints={@UniqueConstraint(name="family_attribute_idx", columns={"family_id", "attribute_id"})})
* @UniqueEntity({"family", "attribute"}, errorPath="attribute");
*/
class FamilyAttribute
{
/**
* @var Family
*
* @ORM\ManyToOne(targetEntity="App\Entity\Family", inversedBy="familyAttributes")
* @ORM\JoinColumn(nullable=false)
*/
private $family;

/**
* @var Attribute
*
* @ORM\ManyToOne(targetEntity="App\Entity\Attribute", inversedBy="familyAttributes")
* @ORM\JoinColumn(nullable=false)
* @Assert\NotBlank()
*/
private $attribute;
}

The form type:

$builder
->add('familyAttributes', CollectionType::class, [
'entry_type' => FamilyAttributeType::class,
'allow_add' => true,
])
;

The issue occurs when I add two "FamilyAttribute" with the same {$family; $attribute} pair.

The UniqueConstraint validation does not work if the duplicate collection entries are not already persisted in the database.

Possible Solution

No idea.