WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

12.0.1

What operating system are you using?

Windows

Operating System Version

Windows 10 Enterprise build no. 19041

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

When I print a pdf using print({ silent: true, printBackground: true }) } I expect for it to work and print without showing dialog box of printing options, but use the default print configuration.

Actual Behavior

It does not print but remains stuck if default print option is print. If I set it to Microsoft Print to Pdf, it prints an empty doc.

If I use executeJavaScript('window.print({ silent: true, printBackground: true })'), it prints but it is not silent. This problem exists only with pdf.

I updated electron version to 13.0.0 but there the pdf view does not work also, it stucks showing blank pages, so I had to downgrade.

Silent pdf printing is a very important feature and I have seen other people asking about it, but still no solution.

Testcase Gist URL

No response

Additional Information

No response

Issue 2:
Electron version: 1.6.13

Operating system: MacOS High Sierra

Expected behavior

With Developer Tools open, close frameless window should performs correctly.

Actual behavior

How to reproduce

Create a frameless window with titlebar & closeButton. Then openDevTools as an independent window. Close the main window directly, the window resource seems retains.
Issue 1:
Navbar dropdown links work fine normally in Chrome, but when navbar is collapsed links do not have any hover state and clicking on links just collapses the dropdown menu.

JSFiddle is here.. http://jsfiddle.net/richyclarke/urbnD/3/

Collapse the navbar by reducing the frame size and try to click on the 'IBM' link under the main navbar li 'Links'. It works in Internet Explorer (IE10 and maybe others) but not in Chrome (latest), Firefox (latest) or IOS devices (Chrome or Safari browser on iPad or iPhone)

This used to work in Bootstrap 2.1.x but has stopped working since 2.2.0 and still doesn't work in 2.3.x

Issue 2:
I had a project using more or less the same menu and it worked. Found out it was using Bootstrap version 2.3.1. Compared version 2.3.2 and 2.3.1 and found that in version 2.3.2 there's this snippet of CSS that reads:

.dropdown-backdrop {
position: fixed;
left: 0;
right: 0;
bottom: 0;
top: 0;
z-index: 990;
}

and the rule: position: fixed; seems to cause all the problems.

I still don't undertand the point of the markup that is added by the bootstrap dropdown plugin:

<div class="dropdown-backdrop"></div>

So I've temporarily fixed the bug on my end by adding a style to override the style causing the problem:

.dropdown-backdrop {
position: static;
}

To me this looks like a bug introduced from version 2.3.1 to 2.3.2. Maybe I'm wrong. If someone could explain the purpose of the empty div, it would be helpful.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Component Demos should be present on the corresponding Component API sections.

Current Behavior

Component Demos and Component API are separated in docs.

Context

While reading the docs https://material-ui.com/, I find myself with two windows open, the Component Demo and the corresponding Component API. I see the two sections aren't exactly 1:1, however I'm guessing the goal is to have a demo for every Component.

There will be a need for compositional demos, much like Semantic's Views docs. These demos can be linked to on each Component API doc page and indexed in a Composed Components top level nav.

Your Environment

Tech
Version

Material-UI
next

React

browser

etc

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

The Issue

When I provide NavLink as a component for Button it seems to work fine but I get this error in console :

Warning: Material-UI: you have provided a custom Component to the `component` property of `ButtonBase`.
In order to make the keyboard focus logic work, we need a reference on the root element.
Please provide a class component instead of a functional component.
You need to fix the: NavLink component.

providing Link works fine without errors.

Here is a sandbox demo : https://x0n7x11vw.codesandbox.io/

Your Environment

Tech
Version

Material-UI
v1.beta-10

React
15.6.1

browser
chrome
Issue 1:
Update

This issue is a duplicate of #2795

TL;DR

I believe this is just a typo. %5 should be actual width and %6 should be actual height. Instead, these two are swapped in the tooltip. The actual implementation in the format still works so doing %5 x %6 would give width x height, as expected.

ℹ Computer information

PowerToys version: v0.20.1

PowerToy Utility: Image Resizer

Running PowerToys as Admin: no

Windows build number: Version 1909 (OS Build 18363.1016)

📝 Provide detailed reproduction steps (if any)

Enable ImageResizer

Under File and the option Filename Format, use the following format: %1 %5 %6 (any format that uses %5 and %6 will work)

Resize any image file, ensuring that you make a copy when you resize it.

Check the filename for the resized image.

✔️ Expected result

Assuming the filename is oopsie.png. After the resize, assuming we picked 1920x1080 (fill), and the format is %1 (%6x%5) (actual width by actual height), the new filename is oopsie (1920x1080).png.

❌ Actual result

Assuming we choose the options and have the format as stated above, we'd instead get oopsie (1080x1920).png.

Issue 2:
Summary of the new feature/enhancement

I am using an US keyboard layout as input and would like to be able to either remap a key or a shortcut to generate unicode characters, in my case Umlauts (ä, ö, ü,...).

So ideally I'd like to remap a shortcut (i.e. CTRL+ALT+O) to generate a lower-case ö. I'd be totally fine with entering the desired unicode key in the 'Remap a key' or 'Remap a shortcut' dialogs.
Issue 1:
Do you want to request a feature or report a bug?

What is the current behavior?

RT

If the current behavior is a bug, please provide the steps to reproduce.

I have a multi Page app and I have two enties 'main.js','main2.js' for two pages.

//main.js
require(['./a','./b','./c'],function(){
console.log('main')
})

//main2.js
require(['./a','./b','./d'],function(){
console.log('main')
})

as you see. two entries share common './a', ',/b'.

if bundle the code now , './a', ',/b' will apear twice , result in large file size if they are big files

then I want to use CommonsChunksPlugins to remove duplicate module like

//webpack.config.js
new webpack.optimize.CommonsChunkPlugin({
async: true,
minChunks: 2
})

nothing change... then i change to

entry:{
main:'./main.js',
main2:'./main2.js',
common:['./a','./b']
},
plugins: [
new webpack.optimize.CommonsChunkPlugin({
name: ['share','common'],
async: true,
minChunks: 2
})
]

this time it generate share.js contain './a', ',/b'.

but entries main.js and main2.js still contain './a', ',/b'. it does not reduce ouptsize

What is the expected behavior?

extract common modules from entries to #share.js

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Window10

Webpack 2.2.0

node 6.9.2

Issue 2:
Bug report

What is the current behavior?

[webpack-cli] Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:130:10)
at BulkUpdateDecorator.hashFactory (/opt/src/node_modules/webpack/lib/util/createHash.js:155:18)
at BulkUpdateDecorator.digest (/opt/src/node_modules/webpack/lib/util/createHash.js:80:21)
at /opt/src/node_modules/webpack/lib/DefinePlugin.js:595:38
at Hook.eval [as call] (eval at create (/opt/src/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:100:1)
at Hook.CALL_DELEGATE [as _call] (/opt/src/node_modules/tapable/lib/Hook.js:14:14)
at Compiler.newCompilation (/opt/src/node_modules/webpack/lib/Compiler.js:1053:26)
at /opt/src/node_modules/webpack/lib/Compiler.js:1097:29
at Hook.eval [as callAsync] (eval at create (/opt/src/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Other relevant information:

webpack version: 5.59.0

Node.js version: 17.0.0

Operating System: linux x64
Issue 1:
Environment

Windows build number: 18363.418
Windows Terminal version: 0.5.2762.0

If a profile is defined with an invalid commandline, or if the shell specified has been uninstalled by the user, trying to open a tab with that profile will not show any warning about the failure to launch the shell process.

If the profile is defined with "closeOnExit":false, the tab will wait forever for the shell to get connected instead of showing an error message. If the profile is defined with "closeOnExit":true, the tab will immediately close with no explanation.

Steps to reproduce

Create a profile with a non-existing shell such as the following:

{

// A non-existing shell

"guid": "{0225F6B6-EC1C-4746-8384-A83DB214D13A}",

"closeOnExit": false,

"name": "dummy",

"commandline": "dummyshell.exe",

"hidden": false

},

Expected behavior

If the commandline cannot be launched, an error should notify the user that the process couldn't be created, so they know they have to look at the command line more closely.

Actual behavior

Instead of some error message, Windows Terminal keeps the tab open and cursor waiting with no hint that something went wrong launching the shell, or simply silently closes the tab if "closeOnExit":true.

Issue 2:
This is work that's following on from work that's being done for #1625.

I'm pulling the code for updating the drag region out of NonClientIslandWindow::OnSize into its own method. Unfortunately, both these methods need to do the following block of work:

const auto windowRect = GetWindowRect();
const auto width = windowRect.right - windowRect.left;
const auto height = windowRect.bottom - windowRect.top;

const auto scale = GetCurrentDpiScale();
const auto dpi = ::GetDpiForWindow(_window.get());

const auto dragY = ::GetSystemMetricsForDpi(SM_CYDRAG, dpi);
const auto dragX = ::GetSystemMetricsForDpi(SM_CXDRAG, dpi);

// If we're maximized, we don't want to use the frame as our margins,
// instead we want to use the margins from the maximization. If we included
// the left&right sides of the frame in this calculation while maximized,
// you' have a few pixels of the window border on the sides while maximized,
// which most apps do not have.
const auto bordersWidth = _isMaximized ?
(_maximizedMargins.cxLeftWidth + _maximizedMargins.cxRightWidth) :
(dragX * 2);
const auto bordersHeight = _isMaximized ?
(_maximizedMargins.cyBottomHeight + _maximizedMargins.cyTopHeight) :
(dragY * 2);

const auto windowsWidth = width - bordersWidth;
const auto windowsHeight = height - bordersHeight;
const auto xPos = _isMaximized ? _maximizedMargins.cxLeftWidth : dragX;
const auto yPos = _isMaximized ? _maximizedMargins.cyTopHeight : dragY;

const auto dragBarRect = GetDragAreaRect();
const auto nonClientHeight = dragBarRect.bottom - dragBarRect.top;

Doing this twice is clearly ridiculous, and more likely than not, wrong.

I'm thinking that on the resize, we could probably just cache some of these values. I think this will also important for dealing with maximizing, cause I think know the maximize borders are wrong on non-primary displays.
Issue 1:
Steps to reproduce:

Go to http://material-ui.com/#/components/text-fields

Click on the text field sample (first row, second column), specifically on the floating label

Actual: Clicking on the floating label the first time does not focus the field

Expected: Clicking on the floating label for the first time should focus the field input

Issue 2:
The css class names definitions are duplicated for some components - in my case it is duplicated (I guess from my debugging) for MuiIconButton and MuiModal - check current behavior

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

Expected Behavior

The class names should not be duplicated across components.

Current Behavior

My button styles:

The class is duplicated.

Styles definition:

It is working in development mode:

My buttons styles:

and found the definitions:

and from modal:

Steps to Reproduce (for bugs)

I can try to prepare the environment to reproduce the problem but right now I just wanted to report it here.

Context

I'm trying to release my application with the production environment.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.10

React
15.6.1

browser
any

webpack
^3.3.0

I need some hints where may be the problem. I'm not using withStyles solution anywhere - I use styled components for styles overriding.
Issue 1:
I'm submitting a ... (check one with "x")

[ x] bug report => search github for a similar issue or PR before submitting
[ ] 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

if more than 10 conditions in [ngClass] object, angular throw errors same as *ngFor = "let i of [1, 2, 3, .......11]"

Expected behavior

it should handle without throwing error

Minimal reproduction of the problem with instructions

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

try to validate when parsing the template without defining the object in .ts file.

Please tell us about your environment:

Angular version: 2.0.X

2.2.1

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Chrome

**Language:**TypeScript ES5

Node (for AoT issues): node --version = v6.2.0

Issue 2:
**I'm submitting a bug.

[x ] bug report
[ ] feature request
[ ] support request

Current behavior

I wanted to repeat particular element several amount of time, so I'm using *ngFor directive with hard-coded array like [1,2,3,4,5,6,7,8,9,10] and that got worked awesome. I achieved what I wanted to do.

Code

@Component({
selector: 'my-app',
template: `<h1>My First Angular App</h1>
<div *ngFor="let item of [1,2,3,4,5,6,7,8,9,10]">
{{item}}: My Element
</div>`
})

[Demo Plunkr][1]

But as soon as I increased the array size more than 10, I start getting below error. Which is really annoying.

zone.js@0.6.25?main=browser:355 Unhandled Promise rejection:

Unsupported number of argument for pure functions: 11 ; Zone: ;

Task: Promise.then ; Value: Error: Unsupported number of argument for

pure functions: 11(…) Error: Unsupported number of argument for pure

functions: 11

Template

<div *ngFor="let item of [1,2,3,4,5,6,7,8,9,10,11]">
{{item}}
</div>`

Expected behavior

I'm curious to know why that error is happening as soon as array size increase more than 10? But another interesting thing is when I put the same array in component inside variable items= [1,2,3,4,5,6,7,8,9,10,11] and used items in *ngFor and it got worked.

Angular version: 2.0.1

Browser: all

Language: TypeScript
Issue 1:
If using MultiIndex as columns, saving to CSV adds an extra line with no data between the column headers and the data. I couldn't find information that this is something that should happen so it was unexpected to me.

Code Sample, a copy-pastable example if possible

In IPython:

import pandas as pd
pd.DataFrame({('a','b'): [1, 2], ('c','d'): [3, 4]}).to_csv('temp.csv', index=False)
cat temp.csv

Outputs:

a,c
b,d
,
1,3
2,4

Expected Output

I expected not to have an empty row between column names and the data:

a,c
b,d
1,3
2,4

output of pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 3.5.1.final.0
python-bits: 64
OS: Linux
OS-release: 4.5.2-gnu-1
machine: x86_64
processor:
byteorder: little
LC_ALL: None
LANG: en_DK.UTF-8

pandas: 0.18.0
nose: 1.3.7
pip: 8.1.1
setuptools: 20.10.1
Cython: 0.24
numpy: 1.11.0
scipy: 0.17.0
statsmodels: None
xarray: None
IPython: 4.2.0
sphinx: 1.4
patsy: None
dateutil: 2.5.3
pytz: 2016.4
blosc: None
bottleneck: None
tables: 3.2.2
numexpr: 2.5.2
matplotlib: 1.5.1
openpyxl: None
xlrd: 0.9.4
xlwt: None
xlsxwriter: None
lxml: None
bs4: 4.4.1
html5lib: None
httplib2: 0.9.2
apiclient: 1.5.0
sqlalchemy: 1.0.12
pymysql: None
psycopg2: 2.6.1 (dt dec pq3 ext lo64)
jinja2: 2.8
boto: None

Issue 2:
This seems strange to me, but I don't often use a MultiIndex so I might be missing something obvious.

>>> pd.__version__
'0.13.1-420-g6899ed6'
>>> df2 = pd.DataFrame([1], columns=pd.MultiIndex.from_arrays([[1],[2]]))
>>> df2
1
2
0 1

[1 rows x 1 columns]
>>> df2.columns
MultiIndex(levels=[[1], [2]],
labels=[[0], [0]])
>>> print df2.to_csv()
,1
,2
,
0,1

Is there supposed to be that empty line at the end of the header? Compare

>>> print df2.to_csv(header=False)
0,1
Issue 1:
Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go version go1.6 darwin/amd64

What operating system and processor architecture are you using (go env)?

mac os x 10.9.5

What did you do?

(Use play.golang.org to provide a runnable example, if possible.)

I want to download golang package for mac os x from an ISP in Iran using golang.org

What did you expect to see?

I expect to see that golang is available for developers from Iran.

You call golang "open-source" that it means its OPEN for anybody. we are developers too.

What did you see instead?

That’s an error.

Your client does not have permission to get URL / from this server. (Client IP address: xxx.xxx.xxx.xxx)

We're sorry, but this service is not available in your country. That’s all we know.

Issue 2:
using go 1.5.1 and 1.6 on linux/x64

given this string

var cgroupname = "/machine.slice/machine-rkt\\x2dbad20ebf\\x2de8b8\\x2d48fe\\x2dabba\\x2de2e3f72123fb.scope/system.slice/alpine-sh.service"

trying to use this function to strip out part of it. (yes, can use regex, but that's a different point)

func parseName(name string) (string, error) {
splits := strings.Split(name, "/")
if len(splits) == 3 || len(splits) == 5 {
if splits[1] == "machine.slice" {
replacer := strings.NewReplacer("machine-rkt-", "", ".scope", "", "\\x2d", "-")
pod := replacer.Replace(splits[2])
pod = strings.Replace(pod, "machine-rkt-", "", -1)
if len(splits) == 3 {
return pod, nil
}
if splits[3] == "system.slice" {
container := strings.Replace(splits[4], ".service", "", -1)
return pod + ":" + container, nil
}
}
}

return "", fmt.Errorf("%s not handled by rkt handler", name)
}

the strings.Replace for pod shouldn't be necessary, I'd expect the replacer to work correctly, but it doesn't. Either it's buggy or i'm using it incorrectly, but I don't know what I'm doing wrong.

can duplicate with https://play.golang.org/p/p_akq9d3YW by playing with comenting out line 18
Issue 1:
System information (version)

OpenCV => 4.2

Operating System / Platform => Ubuntu 18.04

Detailed description

Incorrect output from cv2.dnn.NMSBoxes. I think it can because of incorrect rounding in python bindings.

Steps to reproduce

Incorrect

import cv2

rect1 = [0.0, 0.0, 0.2, 0.2]
rect2 = [0.2, 0.2, 0.4, 0.4]
cv2.dnn.NMSBoxes([rect1, rect2], [1.0, 1.0], 0.5, 0.5)

# output: array([[0]], dtype=int32)

Let's multiply each value of rectangles by 10. Now, output is correct

import cv2

rect1 = [0.0, 0.0, 2.0, 2.0]
rect2 = [2.0, 2.0, 4.0, 4.0]
cv2.dnn.NMSBoxes([rect1, rect2], [1.0, 1.0], 0.5, 0.5)

# output: array([[0], [1]], dtype=int32)

Also, code in c++ works correct:

#include <iostream>
#include <vector>

#include <opencv2/imgproc.hpp>
#include <opencv2/highgui.hpp>
#include <opencv2/dnn.hpp>
using namespace cv;
using namespace cv::dnn;
using namespace std;

int main() {
int a;
vector<float> confidences = {1.0, 1.0};
float confThreshold = 0.5;
float nmsThreshold = 0.5;
std::vector<int> indices;
vector<Rect2d> boxes = {{0, 0, 0.2, 0.2}, {0.2, 0.2, 0.3, 0.3}};
NMSBoxes(boxes, confidences, confThreshold, nmsThreshold, indices);
for (auto i: indices)
cout<<i<<endl;
return 0;
}
//Output:
//0
//1

Issue submission checklist

I report the issue, it's not a question

I checked the problem with documentation, FAQ, open issues,

answers.opencv.org, Stack Overflow, etc and have not found solution

I updated to latest OpenCV version and the issue is still there

There is reproducer code and related data files: videos, images, onnx, etc

Issue 2:
System information (version)

OpenCV => 4.0.1

Operating System / Platform => macOS 10.14.6

Compiler => Apple Clang 11.0.0 (clang-1100.0.33.16)

Detailed description

cv::dnn::NMSBoxes can accept std::vector<Rect2d> but only the one for std::vector<Rect> can be called from python.

Steps to reproduce

boxes_zero = [[0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0]]
conf = [.6, .5, .2]
print(cv2.dnn.NMSBoxes(boxes_zero, conf, 0, 0)) # returns [[0]]

boxes0 = [[1, 2, 3, 4], [2, 1, 3, 4], [4, 3, 2, 1]]
print(cv2.dnn.NMSBoxes(boxes0, conf, 0, 0)) # returns [[0], [2]]

boxes1 = [[float(elem) for elem in box] for box in boxes0]
print(cv2.dnn.NMSBoxes(boxes1, conf, 0, 0)) # returns [[0], [2]]

boxes2 = [[elem * 0.1 for elem in box] for box in boxes1]
print(cv2.dnn.NMSBoxes(boxes2, conf, 0, 0)) # returns [[0]]

boxes3 = np.array(boxes0)[np.newaxis, :]
print(cv2.dnn.NMSBoxes(boxes3, conf, 0, 0)) # returns [[0], [2]]

boxes4 = boxes3.astype(np.float64)
print(cv2.dnn.NMSBoxes(boxes4, conf, 0, 0)) # returns [[0], [2]]

boxes5 = boxes4 * 0.1
print(cv2.dnn.NMSBoxes(boxes5, conf, 0, 0)) # returns [[0]]

boxes6 = boxes5.astype(np.float32)
print(cv2.dnn.NMSBoxes(boxes6, conf, 0, 0)) # returns [[0]]

boxes7 = boxes6 * 10
print(cv2.dnn.NMSBoxes(boxes7, conf, 0, 0)) # returns [[0], [2]]