WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Hello, I was performing some simple tests and stumbled upon something that did not seem to behave as expected....

I wanted to set the window screen size different (bigger) than the viewport but when I evaluated screen.height I always got the viewport's height.

I tried setting ScreenSize in the context but also in a new page (check Snippet below), but both behaved the same way...

I always set the ScreenSize along with ViewportSize, as documentation suggests, so that did not seem to be the case.

Then it came to my mind to check the behavior of the other browsers as well. I tested Chromium & WebKit and they both work as expected!

So, I guess it's a firefox issue and it's probably a bug rather than feature... although, I cannot tell if it occurs also on the Playwright or it was introduced in the dotnet port.

Snippet to reproduce:

var width = 1920;
var height = 1200;

using var playwright = await Playwright.CreateAsync();
await using var browser = await playwright.Firefox.LaunchAsync(new() { Headless = false});

await using var context = await browser.NewContextAsync(new()
{
ScreenSize = new ScreenSize { Width = width, Height = height },
ViewportSize = new ViewportSize { Width = width, Height = 1080} //let's set something different in Viewport height
}) ;

var page = await context.NewPageAsync();
var altpage = await browser.NewPageAsync(new()
{
ScreenSize = new ScreenSize { Width = width, Height = height },
ViewportSize = new ViewportSize { Width = width, Height = 1080 } //let's set something different in Viewport height
}) ;

var screenheight = await page.EvaluateAsync<string>("screen.height"); // for firefox this value will be 1080 (ViewportSize Height )
var altscreenheight = await altpage.EvaluateAsync<string>("screen.height"); // for firefox this value will be 1080 (ViewportSize Height )

Issue 2:
Playwright version

1.15.2-1633455481000

Operating system

Windows

What browsers are you seeing the problem on?

Firefox

Other information

Python 3.1.0

What happened? / Describe the bug

Passing screen={'width': any_int, 'height': any_int} to context, is not properly reflected, as window.innerHeight and window.innerWidth will still equal to screen.height and screen.width even if the values passed to viewport are different.

Code snippet to reproduce your bug

from playwright.sync_api import sync_playwright

with sync_playwright() as p:
browser = p.firefox.launch(headless=False)

context = browser.new_context(
screen={'width': 1280, 'height': 720},
viewport={'width': 1280, 'height': 636}
)
page = context.new_page()

Relevant log output

Both screen.height and window.innerHeight will be 636 in this case, while screen.height should be 720.
Issue 1:
Original bug ticket: [https://npm.community/t/9947](https://npm.community/t/9947)
Originally filed: 2019-09-09T12:25:22.211Z

Issue 2:
Current Behavior:

running npx @package@version generate it with the current install version

Expected Behavior:

it should be generated with the given version

Steps To Reproduce:

ex. steps to reproduce the behavior:

run npm i -g npm@latest to install npm 7

run npx @angular/cli@next new

answer all questions of the angular cli, it doesn't matter what the answers are

it will install angular 11 (while next is 12)

Environment:

OS: Windows 10

Node: 14.16.1

npm: 7.12.0 (working fine with 6.14.13)
Issue 1:
Hi,

some days ago, I wanted to launch a debate about the console commands available in Standard edition.

Actual status

For the record, we have 72 commands available when we install Symfony (71 if we remove the Symfony ACL component).

I don't think this need a screenshot, we can say the first contact with the console is undoubtely disturbing for a lot of newbies:

too much commands;

too much options

some weird duplicates ... (this point is already fixed in 3.0.X release)

Before release the new major in november, the deletion of all deprecated command is planned (no specific issue) and the new UI update is in progress (#14138).

Commands of Standard Edition come from Bundles:

AsseticBundle

DoctrineBundle

SwiftMailerBundle

FrameworkBundle

...

They are autoloaded and registered without any intervention of developper. As @fabpot said, if we don't want the commands, we can uninstall the related bundle.

Commands come from bundles

But theses bundles provide a lot of others useful things that make them required in Standard Edition:

Compiler passes

Event listeners

Complete applications ? (like the WebProfiler)

So, I think remove some of theses bundles can't be an option.

Survey about Symfony commands

Few days ago, I started to share a survey about the Symfony commands use. You can see the complete results here

Some easy conclusions according to the survey:

Almost 15 commands are (mostly) never used

60% (~50 !) of theses commands are not used by a majority of developpers

Some ideas

To improve the DX of the Symfony console, many strategies can be applied:

Remove some commands;

Move theses commands into "Extra" Bundles (debug-command-bundle, security-command-bundle, doctrine-command-bundle ...);

Make some of theses command real console applications (yaml-linter, php-security-checker ...);

Play with the isEnabled() function: only enable to most used command by default;

Implement a "two levels" displaying of console like rails for instance: the first time we only see the categories of commands, then when we call a category (php app/console doctrine) the console returns all available commands in this category.

... and probably far better ideas you have :)

Of course, many strategies can be applied, and this issue is more about debate than suggest a pull request that remove everything :)

What do you think ?

Issue 2:
I suppose you already had this before as well, copying a route and forgetting to rename it. The old route gets overwritten and you might not even notice it until its too late.

How about throwing an Exception when the same route name is defined twice in the same YAML or XML file to increase developer experience?
Issue 1:
It's okay on Chrome 36 and on IE 11, sadly, it's pushing content to the left on Firefox 32.0, when you minimize the screen, then open the modal while it's minimized, then you maximize and open the modal again.

Issue 2:
div.input-append is a block that contains only floating elements, thus gets a 0px height; if a .help-block follows the div.input-append, it is displayed next to the div.input-append instead of under it, because the 0px-height div.input-append does not offset it vertically. adding "clear: left" to the .help-block seems to correct this problem, but I'm not sure if that won't break something else.
Issue 1:
Seeing is believing: http://doc.rust-lang.org/std/ops/trait.Drop.html

core::finally::Finallyalizer and collections::vec::PartialVecNonZeroSized are two of many dangling links in the Drop page. They shouldn't be visible at all because core::finally and PartialVecNonZeroSized are private items.

Issue 2:
For example, NaiveSearcher on the clone page: http://doc.rust-lang.org/std/clone/trait.Clone.html
Issue 1:
e.g. torch.sin(1) or torch.sin([1,2,3])

Numpy supports this feature, which makes programming very convenient.

Thx!

Issue 2:
Numpy automatically casts inputs to ndarrays when doing operations on them. For example:

>>> np.sum([1, 2])
3
>>> np.sqrt(9)
3.0

Pytorch fails instead:

>>> torch.sum([1, 2])
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: sum(): argument 'input' (position 1) must be Tensor, not list
>>> torch.sqrt(9)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: sqrt(): argument 'input' (position 1) must be Tensor, not int

It would be nice for Pytorch to do type-casting internally like numpy does.

cc @mruberry @rgommers @heitorschueroff
Issue 1:
It appears that dynamically provisioned volumes bypass the labelling admission controller, and so are not labeled with zone information.

Issue 2:
I created a PV and it wasn't labeled with the Ubernetes-Lite tags, but I wasn't running under Ubernetes-Lite at the time...

"annotations": {
"kubernetes.io/createdby": "aws-ebs-dynamic-provisioner",
"volume.alpha.kubernetes.io/storage-class": "foo",
"volume.experimental.kubernetes.io/provisioning-required": "volume.experimental.kubernetes.io/provisioning-completed"
}
Issue 1:
Description of the new feature/enhancement

Moving profiles.json to C:\Users\xxx\AppData\Roaming\WindowsTerminal would allow it to make use of the Roaming folder, and also put it in an easier and more consistent place for people to create symlinks to sync it across several machines using OneDrive/Google Drive/NextCloud/etc.

Issue 2:
Environment

Windows Terminal version (if applicable): 10.0.18362.356

Steps to reproduce

Execute man page command like:

user@xps:~$ man ls

Actual behavior

Some text in man page are invisible.

Trying to search -a in the man page:

The default One Half Light scheme:

{
"name": "One Half Light",
"foreground": "#383A42",
"background": "#FAFAFA",
"black": "#383A42",
"red": "#E45649",
"green": "#50A14F",
"yellow": "#C18301",
"blue": "#0184BC",
"purple": "#A626A4",
"cyan": "#0997B3",
"white": "#FAFAFA",
"brightBlack": "#4F525D",
"brightRed": "#DF6C75",
"brightGreen": "#98C379",
"brightYellow": "#E4C07A",
"brightBlue": "#61AFEF",
"brightPurple": "#C577DD",
"brightCyan": "#56B5C1",
"brightWhite": "#FFFFFF"
}

Similar problem happen in less page. Searched texts are not highlighted in One Half Light scheme.
Issue 1:
Describe what you were doing when the bug occurred:

1.

2.

3.

Please do not remove the text below this line

DevTools version: 4.2.0-a8b8ffb89

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:156567

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:156513)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157036)

at gl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:314363)

at fi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59263)

at Hi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:66573)

at lc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:104884)

at kc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89467)

at wc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89392)

Component stack: in gl

in div

in div

in div

in _o

in Unknown

in n

in Unknown

in div

in div

in zi

in Ge

in un

in ba

in Rc

Issue 2:
PLEASE INCLUDE REPRO INSTRUCTIONS AND EXAMPLE CODE

I got this error when I click 'Ranked'.

Please do not remove the text below this line

DevTools version: 4.0.4-3c6a219

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11441

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11387)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11920)

at _i (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56:277123)

at Ha (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:55890)

at Xl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:98280)

at Hl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:84255)

at Fl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:81285)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:25363

Component stack: in _i

in div

in div

in div

in Or

in Unknown

in n

in Unknown

in div

in div

in Ha

in le

in ve

in ko

in Ul
Issue 1:
I love the API for global shortcuts - is it possible to somehow use a similar API to add shortcuts to a focused BrowserWindow?

Issue 2:
I'd like to add some hotkeys for events in my app, and accelerators seem like the natural way to do that, but some of these things don't make sense in a menu. Is there a way to use accelerators without registering a global shortcut or a menu? I'd rather not have hidden menus.
Issue 1:
Bug report

Describe the bug

Scripts in the Head are run twice if marked async.

To Reproduce

Steps to reproduce the behavior:

Create next app

Create file at /static/log.js with console.log('hello'); inside

Attach to a page (make sure to add the async attribute)

<NextHead>
<script src="/static/log.js" async></script>
</NextHead>

Run site

See duplicate console.log in console.

Expected behavior

Scripts should only run once.

Screenshots

System information

OS: macOS

Version of Next.js: latest 9.1.1

Issue 2:
When starting the next build, nothing is shown for a good amount of time. This has caused several misunderstandings with newer developers and is fairly annoying to have no idea how much longer your build will take.

I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

I would expect something in the next.config like showBuildOutput: true that will show some indication of how far along the build is in the terminal or even a progress bar.

Current Behavior

Currently, you're staring at a nonchanging terminal window for a few minutes if the build takes a while.

Context

This could be considered a quality of life improvement but is something that I personally would expect to be a fundemental feature of any build.
Issue 1:
Expected Behavior

The app should've run

any flask app really

Actual Behavior

Flask didn't startup properly and threw an errorcode

$ flask run
* Serving Flask app "falsker"
* Forcing debug mode on
* Restarting with stat
File "C:\Anaconda3\envs\flaskui\Scripts\flask.exe", line 1
SyntaxError: Non-UTF-8 code starting with '\x90' in file C:\Anaconda3\envs\flaskui\Scripts\flask.exe on line 1, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

Environment

Python version: 3.6.2 on Anaconda

Flask version:0.12.2

Werkzeug version:0.12.2

Issue 2:
I am running apistar on python 3 and encountering an issue that has lead me to the werkzeug reloader.

(fresh) C:\Users\uskaxb07\PycharmProjects\testapi>apistar run
Starting up...
* Restarting with stat
File "C:\Users\uskaxb07\env\fresh\Scripts\apistar.exe", line 1
SyntaxError: Non-UTF-8 code starting with '\x90' in file C:\Users\uskaxb07\env\fresh\Scripts\apistar.exe on line 1, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

Removing the use_reloader from the call to run_simple() works. After digging into a couple of comments I found that https://github.com/pallets/werkzeug/blob/master/werkzeug/_reloader.py#L118 is doing some encoding to latin1 but only when the os is windows and the python version is 2. Could this be causing the Non-UTF-8 Syntax Error that I am recieving in python3?
Issue 1:
I'm creating pagination like the example in the documentation. I have previous and next links on each side and links to each page in the middle.

Out of the box doesn't look great when I scale down to a phone (wraps in the middle) so I figured I'd put .hidden-xs on the middle page number links so when I view on a phone it's just prev and next.

That caused it to look great on the phone, but on larger displays the "display: block !important;" causes the buttons to be stacked vertically.

Ideally there should be responsive pagination options.

Issue 2:
related to issues #8500 , #7808 , #4929 ; using .hidden-sm to hide span within .nav > li > a . Because class is display: block above -sm then text wraps to new line. Would you consider .hidden-* classes to be display: inline-block instead ?

Here's a jsfiddle of the two cases - but the repercussions could be greater outside of this situation so probably needs more consideration... http://jsfiddle.net/jholl/P86yf/
Issue 1:
Patrick Marschik opened SPR-9127 and commented

When you create an annotation based configuration class with a @PropertySource annotation that provides multiple .properties files and a name for that property source only one property source gets registered since all ResourcePropertySource s have the same name and thus get overwritten by the subsequent property sources.

Example:

@Configuration
@PropertySource(name = "someName", value = {"classpath:a.properties", "classpath:b.properties"})
public class MyConfiguration {
}

this will only register b.properties in the Environment since 2 ResourcePropertySources with the name someName are created and added to the environment.

Affects: 3.1 GA

Issue Links:

#14016 Resolving ${} system properties in @PropertySource annotation does not work anymore ("is duplicated by")

#13772 Fix regression in @PropertySource placeholder resolution

#16260 @PropertySource locations are being dropped in ConfigurationClassParser processPropertySource

Referenced from: commits 4df2a14, e30d610, 41ade68

Issue 2:
Christian Tzolov opened SPR-2186 and commented

When used for a void method invocation the MethodInvokingFactoryBean returns a 'null' value instead of VoidType.

(Test is attached)

Affects: 2.0 RC1

Attachments:

MethodInvokingFactoryBean_VoidReturnValueTest.java (1.06 kB)

TestContext.xml (877 bytes)
Issue 1:
Hi

I am using the Breevy (from http://www.16software.com) text expander for many things, including documentation, and it doesn't go well with vsCode.

The expander has 2 operating modes, one where it simulates key presses, and one where it uses the clipboard, simulating a cut/paste operation to insert text in the current application.

Works fine for while on anything I've been using, however the shortcuts are not expanded inside vsCode

I have tested with the Markdown editor and on a generic file, simply doing Ctrl+N to have a new edit window opened.

What happens is that the abbreviation seems to be recognized, as it's removed from the screen, but the expanded text is not inserted instead. Tried to change the shortcuts to avoid special chars, such as $ or =, same results.

This on win 7, 64 bits. VsCode 0.10.2.

Cheers

Issue 2:
VSCode Version: 1.0

OS Version: windows 10

Paste code var p = 1?2:(3<4?5:6), and everything after this will be in wrong color.
Issue 1:
I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

We have an AbstractControl with basic validators like (required, maxLength) in a ReactiveForm via TypeScript FormBuilder. To those basic validators we added a custom validator which dynamically change the validation strategy based on a dropdown value. Currently we are using the setValidators() method inside another component (AbstractControl is included via @Input()). The main problem is that it overwrites existing validators.

Example:

App Component

this.formBuilder.group({
zip: ['', [Validators.required, Validators.maxLength(10)]]
});

App Template

<zip ...
[control]="form.controls.zip">
</zip>

ZIP Component

@Input() control: AbstractControl;

this.control.setValidators([
// redundant to formBuilder
Validators.required,
Validators.maxLength(10),
// custom validation based on a dropdown value (via. valueChange Detection)
validateZipFn(countryCode)]
);

Expected behavior

To stay flexible we don't want to overwrite all validators. The below code would illustrate the behavior with a getValidators() method.

App Component

this.formBuilder.group({
zip: ['', [Validators.required, Validators.maxLength(10)]]
});

App Template

<zip ...
[control]="form.controls.zip">
</zip>

ZIP Component

@Input() control: AbstractControl;

let listOfAllValidationRules = this.control.getValidators().push(validateZipFn(countryCode)]);
this.control.setValidators(listOfAllValidationRules);

What is the motivation / use case for changing the behavior?

Being more flexible with dynamic validation.

Angular version: ~2.1.2

Browser: all

Language: TypeScript / ES6

Issue 2:
I'm submitting a Bug Report.

Current Behaviour

Running ngc generates a View_AppComponent_0() function that takes the logger as argument. If the component template does not declare any element or text that function is basically empty. The l parameter is not used, which can lead to errors when typescript builds it with noUnusedParameters.

Expected Behaviour

The factory code should not take an argument, or should always use that argument so that typescript doesn't show an error.
Issue 1:
The information in doc/source/user/c-info.how-to-extend.rst is repeated in `doc/source/reference/c-api.array.rst. The first should only reference the second, and the descriptive text should be merged.

This may be a good starter task. The cycle to fix this issue, based on the doc building documentation is to

create the documentation with make html

Note the many warnings about duplicate C object description in the two files

Edit the files to unify the documentation, one should be using .. c:function:: to define the functions and the other using :c:func: to reference it, perhaps with descriptive text.

Use firefox build/html/reference/c-api.array.html and firefox build/html/user/c-info.how-to-extend.html to view the changes

Issue 2:
I started out thinking I've found a docbug but I'm becoming less sure. The problem is that the documentation of numpy.ma.sort (devdocs version) says

Sort the array, in-place

[...]

Returns: sorted_array

Whereas the behaviour seems to be the opposite:

>>> import numpy as np
>>> arr = np.arange(5)[::-1]
>>> np.ma.sort(arr)
array([0, 1, 2, 3, 4])
>>> arr
array([4, 3, 2, 1, 0])

The weird thing is that I've found #1966 which suggests that until 2010 the docs had mentioned a copy and the behaviour was mutating, and the docstring was subsequently fixed. However looking at the git blame even in commit 5cb370e923 from 2008 I can see

from numpy import array as narray
# [...]
def sort(...):
a = narray(a, copy=True, subok=True)

This seems to me that even in 2008 it should have returned a copy, which makes the linked docbug issue very confusing. What am I missing?

Ultimately I think this is a docbug, because np.ma.sort should match np.sort which copies (and is documented as such), whereas the corresponding instance methods should sort in-place.