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.

Problem Description

If I am not mistaken, the cookie, localStorage, indexedDB and resource cache of the programs based on Electron store in the following locations currently:

Windows: C:\Users\<userName>\AppData\Roaming\<productName>

Linux: /home/<userName>/.config/<productName>

OS X: /Users/<userName>/Library/Application Support/<productName>

But when we use software in portable devices on different computers, we probably want to be able to freely specify the storage location to the portable device self, to use it anywhere continuously, or do not leave persistent traces in the temporary computer (maybe through in-memory session it's possible, but loadExtension is not supported in this case).

In addition, we may also have multiple programs based on Electron developing (or just using). Even if we are careful to avoid duplication of names, we will encounter problems when different versions of the same software coexist.

Proposed Solution

session.setPath(`<customPath>`);

Alternatives Considered

session.fromPartition('persist:name', {
path: `<customPath>`,
});

session.fromPartition('persist:<customPath>', {
path: true,
});

Additional Information

no

Issue 2:
In Electron 5, sandbox mode will no longer be experimental, and running with --enable-sandbox or --enable-mixed-sandbox will be the recommended way to use Electron. In Electron 6, --enable-mixed-sandbox will be on by default and the sandbox webPreferences option will be true by default.

This is still an early-stage proposal, so definitely keen to hear any feedback or concerns people might have!
Issue 1:
Please:

Check for duplicate requests.

Describe your goal, and if possible provide a code snippet with a motivating example.

I think the documentation for the jax.random.gamma random variable (sampler) could possibly be clearer. In particular, letting the user know that the standard form is implemented and how to incorporate the rate (or alternatively scale) parameter in their samples. Maybe an addendum along the lines of

"we implement the standard gamma density. Dividing the sample by the rate is equivalent to sampling from $\text{Gamma}(\alpha, \text{rate})$. And multiplying the sample by the scale is equivalent to sampling from $\text{Gamma}(\alpha, \text{scale})$."

The discussion for this started here and I'm mentioning @mattjj for visibility. Thanks!

Issue 2:
Please:

Check for duplicate issues.

Provide a complete example of how to reproduce the bug, wrapped in triple backticks like this:

# On Ubuntu 20.04.3, conda-forge channel only
conda create -n test python=3.9 openssl=1 jax jaxlib=0.3.0
conda activate test
python -c 'import jax'

If applicable, include full error messages/tracebacks.

[libprotobuf ERROR google/protobuf/descriptor_database.cc:641] File already exists in database: tensorflow/compiler/xla/xla_data.proto
[libprotobuf FATAL google/protobuf/descriptor.cc:2021] CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size):
terminate called after throwing an instance of 'google::protobuf::FatalException'
what(): CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size):
Aborted (core dumped)
Issue 1:
The docs for Pkg.dir() say "In particular, Pkg.dir(pkg) returns the path to the package pkg." However @tkelman points out in EcoJulia/Phylo.jl#2 that this doesn't happen when LOAD_PATH is set. As a result there's no way of finding the path to a file in an installed package (from outside that package), which is extremely desirable if, for instance, you want to install a resource with a package for reference. If this is right, this seems like a bug as it conflicts with the documented behaviour...

Issue 2:
it works fine if the package is in .julia/v0.x, but if it is somewhere else then it claims there is no test/runtests.jl even if my LOAD_PATH is set such that i can using it. i know that the recommended dev cycle is to keep packages in .julia, but would it make sense to make Pkg.test() work otherwise?
Issue 1:
The Playwright docs encourage the use of launch_persistent_context in headful mode in order to include a browser extension. I have been attempting to do this and struggling hard. While the code works flawlessly on my laptop, GitHub Actions using xvfb are failing.

I've filed a ticket in the downstream Python library here. Logs of the error can be found here. The relevant workflow file is here. The Python code that launches the browser is here.

Here's my request: This core library should add a unittest that verifies that the recommended use of launch_persistent_context with a browser extension. This would be similar to the existing test that captures video.

Issue 2:
Context:

Playwright Version: [what Playwright version do you use?] Version 1.10.0-next-1616530863000

Operating System: [e.g. Windows, Linux or Mac] WIndows 10 10.0.19043 N/A Build 19043

Node.js version: [e.g. 12.22, 14.6] Python 3.9

Browser: [e.g. All, Chromium, Firefox, WebKit] All

Extra: [any specific details about your environment]

Code Snippet

Try to launch playwright for codegen

$ playwright codegen https://github.com/

Describe the bug

When the playwright inspector is launched, It is out of my view of my display, so I clicked on taskbar with shift and clicked maximised I got inspector full screen but wasn't able to get inspector without maximising it.
Issue 1:
It would be great if VS Code supported the paradigm of semantic highlighting.

In short, it makes syntax highlighting more useful, by varying the colors of the same syntax-types of different names in a given scope. This makes it easier to catch mistakes and to see the flow of variables (since every variable in a given scope has a unique color, yet based of the same color range).

Here's an in depth explanation of what is is with some examples: https://medium.com/@evnbr/coding-in-color-3a6db2743a1e#.n2zb9ohw8

Example - before:

Example - after:

Issue 2:
From @Wosi on October 13, 2015 14:22

I'm looking for a way to implement an advanced source highlighting

where a language service changes the color of words in a file. The result would look similar to the output Visual Studio creates in C# files.

The screenshot shows C# code in Visual Studio. The word "Customer" is highlighted differently based on its context:

To implement highlighting like this it's necassary to let a language service decide about the color of a word after the grammar based highlighter has done its job.

I would like to see an API for this in the future.

Copied from original issue: Microsoft/vscode-extensionbuilders#14
Issue 1:
[Enter steps to reproduce below:]

...

...

Atom Version: 0.169.0

System: Mac OS X 10.10.2

Thrown From: Atom Core

Stack Trace

Uncaught Error: ENOENT, open '/Users/non/Repositories/ohmpieng/production/config/omniauth.rb'

At /Applications/Atom.app/Contents/Resources/app/node_modules/pathwatcher/node_modules/q/q.js:126

Error: ENOENT, open '/Users/non/Repositories/ohmpieng/production/config/omniauth.rb'
at Error (native)

Commands

4x -0:02.6 pane:show-previous-item (atom-text-editor.editor)
11x -0:00.0 pane:show-next-item (atom-text-editor.editor)

Config

{
"core": {
"themes": [
"atom-dark-ui",
"monokai"
]
},
"editor": {
"fontFamily": "Menlo",
"fontSize": 12,
"invisibles": {}
}
}

Installed Packages

# User
monokai, v0.8.0

# Dev
No dev packages

Issue 2:
switch the node_modules package from a version to a git repository

npm install

Atom Version: 0.165.0

System: Mac OS X 10.10.1

Thrown From: Atom Core

Stack Trace

Uncaught Error: ENOENT, open '/Users/joscha/Development/mailbutler/node_modules/grunt-crx/tasks/crx.js'

At /Applications/Atom.app/Contents/Resources/app/node_modules/pathwatcher/node_modules/q/q.js:126

Error: ENOENT, open '/Users/joscha/Development/mailbutler/node_modules/grunt-crx/tasks/crx.js'
at Error (native)

Commands

-0:28.1 find-and-replace:show (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
-0:26.0 core:confirm (input.hidden-input)
7x -0:19.3 core:move-left (input.hidden-input)
-0:14.9 core:backspace (input.hidden-input)
-0:14.2 core:move-left (input.hidden-input)
2x -0:13.7 core:move-right (input.hidden-input)
-0:13.1 core:move-left (input.hidden-input)
-0:12.8 core:backspace (input.hidden-input)
7x -0:12.5 core:move-right (input.hidden-input)
-0:11.3 core:backspace (input.hidden-input)
2x -0:10.9 core:move-right (input.hidden-input)
-0:09.7 core:backspace (input.hidden-input)
5x -0:09.3 core:move-left (input.hidden-input)
-0:02.6 core:copy (input.hidden-input)
-0:00.7 core:paste (input.hidden-input)
-0:00.0 core:save (input.hidden-input)

Config

{
"core": {
"ignoredNames": [
".git",
".svn",
".DS_Store"
]
},
"editor": {
"showInvisibles": true,
"autoIndentOnPaste": false
}
}

Installed Packages

# User
atom-jasmine, v0.4.0
editorconfig, v0.2.2
jsformat, v0.7.18
language-scala, v1.1.0
linter, v0.9.0
linter-coffeelint, v0.1.7
linter-jshint, v0.1.0
linter-php, v0.0.11
travis-ci-status, v0.11.1
visual-bell, v0.9.0

# Dev
No dev packages
Issue 1:
When I installed tensorflow with "pip install",I meet the "A protocol message was rejected because it was too big (more than 67108864 bytes) ",and I uninstall protobuf with pip,then download a new protobuf,install it with changing 256 << 20 in coded_stream.h as "Readme" said,but the same problem occurred,it seems that tensorflow hasn't used the new protobuf,how could I deal with this problem?

Issue 2:
I'm using tf: '2.0.0-rc1'

In the process to load image, you said

for image, label in labeled_ds.take(1):

print("Image shape: ", image.numpy().shape)

print("Label: ", label.numpy())

InvalidArgumentError: {{function_node __inference_Dataset_map_process_path_378}} slice index -1 of dimension 0 out of bounds.

[[{{node strided_slice}}]] [Op:IteratorGetNextSync]

and then:

train_ds = prepare_for_training(labeled_ds)

image_batch, label_batch = next(iter(train_ds))

InvalidArgumentError: {{function_node __inference_Dataset_map_process_path_378}} slice index -1 of dimension 0 out of bounds.

[[{{node strided_slice}}]] [Op:IteratorGetNextSync]

some kind of problem...
Issue 1:
In this simplified example I want to explain my problem using the grid-system. When I understand the grid system right you can add as many cols as you like in one row and when the 12-grids are full the next col break into the next line.

Until rc1 the following example worked well but with the release of Bootstrap 3.0 I've got an error. I think it's because of the missing "float:left" on the col-xs-12, col-sm-12 ... classes.

<div class="row">
<div class="col-xs-4">Col 1</div>
<div class="col-xs-4">Col 2</div>
<div class="col-xs-4">Col 3</div>
<div class="col-xs-12">Col 4</div>
<div class="col-xs-6">Col 5</div>
</div>

Can you tell me why the float:left has been removed with the rc2 of bootstap 3?

Issue 2:
Example:

`

.col-xs-6 .col-md-4

.col-xs-6 .col-md-4

.col-xs-6 .col-md-4

`

see: http://stackoverflow.com/questions/18428450/bootstrap-3-layout-with-panel-display-not-correct-on-small-device/18433782
Issue 1:
The SciPy documentation site does not load securely (in Google Chrome) due to mixed content (HTTPS vs HTTP). This seems to have been resolved in the Sphinx repo in this commit and in the SciPy Sphinx Theme repo in this commit. However, it doesn't appear that the doc site has been updated with these changes.

I couldn't find another issue with this, but if I overlooked it, feel free to refer me to the duplicate. Thanks.

Issue 2:
Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like.

I would like to be able to access the objective function value at each iteration of the differential_evolution algorithm provided in scipy.optimize. This is currently not available in the callback method.

Describe alternatives you've considered.

I have considered evaluating the function given the parameters value xk (which is available in the callback method). Unfortunately, this means I need to reevaluate the objective function, which in my case is prohibitive because the objective is very expensive to evaluate.

Additional context (e.g. screenshots, GIFs)

No response
Issue 1:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.x

Description:

I am using the PropertyInfo component to read phpdoc comments.

Somewhere we got :

/**
* Array of categories IDs
* @var array|null
* @SWG\Property(@SWG\Items(type="string"))
*/

and in our code $type->isNullable() returns "false".

$type is a Symfony\Component\PropertyInfo\Type instance.

Fix:

https://github.com/symfony/symfony/blob/3.2/src/Symfony/Component/PropertyInfo/Util/PhpDocTypeHelper.php#L107

The "nullable" argument should be used here i believe ?

I can provide a pull request to fix this if you agree that it is an issue (not sure if the argument is unused on purpose here ..)

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
2.8

PHP allows null value when using an array type hint but the PhpDocExtractor does not consider array and collections as nullable since the ReflectionExtractor does.

function setProperty(array $prop = null)
Issue 1:
es6-shim.d.ts conflicts with lib.es6.d.ts when typescript target is ES6.

Issue 2:
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

With the tag, if you use the multiple="false" property, the ngModel will not update the selected item. If you remove the multiple="false" property, it works correctly.
Expected behavior

Including the multiple="false" property of the tag will allow the ngModel to correctly select the item.

Minimal reproduction of the problem with instructions

<select id="mySelect" name="mySelect" [(ngModel)]="mySelectedValue" multiple="false" size="3">
<option *ngFor="let option of options" [ngValue]="option">{{option.label}}</option>
</select>

if multiple="true" it works correctly if mySelectedValue is set, if you remove multiple="false" it works as well, but you cannot dynamically set the value of multiple property utilizing [multiple]="myDecision" or multiple="false"

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

Please tell us about your environment:

Windows 7, Angular CLI (ng serve)

Angular version: 2.0.X

2.4.0

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, Firefox, IE

Language: [all | TypeScript X.X | ES6/7 | ES5]

all

Node (for AoT issues): node --version =
Issue 1:
💻

Would you like to work on a fix?

How are you using Babel?

@babel/cli

Input code

const fn = async () /* test */ => {
};

Configuration file name

No response

Configuration

No response

Current and expected behavior

using @babel/generator version 7.20.0 and newer results in error

last working version is 7.19.6

Environment

@babel/generator@7.20.0

Possible solution

No response

Additional context

also fails in babel repl

Issue 2:
💻

Would you like to work on a fix?

How are you using Babel?

babel-loader (webpack)

Input code

import { apiLogout } from "../api";
import { reportError } from "../libs/report_error";

export function logout() {
return reportError(async (/*dispatch*/) => {
await apiLogout();
window.location.reload();
});
}

Configuration file name

babel.config.js

Configuration

module.exports = function(api) {
const isTest = api.env('test');

const envOptions = isTest
? {
"targets": {
"node": "current"
}
}
: {
modules: false,
useBuiltIns: 'usage',
corejs: "3.25",
// debug: true,
};

return {
"presets": [
["@babel/preset-env", envOptions],
"@babel/preset-react"
],
};
};

Current and expected behavior

After an upgrade from 7.19.3 to 7.19.6 I've got a following failure.

ERROR in ./assets/actions/user.js 12:5
Module parse failed: Unexpected token (12:5)
File was processed with these loaders:
* ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
| export function logout() {
| return reportError(async /*dispatch*/
> () => {
| await apiLogout();
| window.location.reload();
@ ./assets/actions/index.js 2:0-37 12:13-24
@ ./assets/app.js 6:0-37 12:15-23

Babel inserts a new line and breaks async closure (I guess, auto-insertion of semicolon is involved).

The same error is reproducible in an online playground with other versions: 7.17.12 generates correct code while 7.20.1 generates invalid code

Environment

Environment w/o the issue

System:

OS: Linux 6.0 Debian GNU/Linux bookworm/sid

Binaries:

Node: 14.20.0 - ~/apps/nodejs/bin/node

Yarn: 1.22.19 - ~/apps/nodejs/bin/yarn

npm: 6.14.17 - ~/apps/nodejs/bin/npm

npmPackages:

@babel/core: ^7 => 7.19.3

@babel/eslint-parser: ^7 => 7.19.1

@babel/preset-env: ^7 => 7.19.3

@babel/preset-react: ^7 => 7.18.6

babel-jest: ^29 => 29.1.2

babel-loader: ^8.0.0 => 8.2.5

eslint: ^8.2 => 8.24.0

jest: ^29 => 29.1.2

webpack: ^5 => 5.74.0

Environment with the issue (after yarn upgrade)

System:

OS: Linux 6.0 Debian GNU/Linux bookworm/sid

Binaries:

Node: 14.20.0 - ~/apps/nodejs/bin/node

Yarn: 1.22.19 - ~/apps/nodejs/bin/yarn

npm: 6.14.17 - ~/apps/nodejs/bin/npm

npmPackages:

@babel/core: ^7 => 7.19.6

@babel/eslint-parser: ^7 => 7.19.1

@babel/preset-env: ^7 => 7.19.4

@babel/preset-react: ^7 => 7.18.6

babel-jest: ^29 => 29.2.2

babel-loader: ^8.0.0 => 8.2.5

eslint: ^8.2 => 8.26.0

jest: ^29 => 29.2.2

webpack: ^5 => 5.74.0

Possible solution

No response

Additional context

No response
Issue 1:
Whenever I try to open Dialog from Drawer, the Dialog shows up for very short time and disappears.

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

Expected Behavior

Dialog shows up while the Drawer slides back in the background.

Current Behavior

After clicking an ListItemText in the drawer with function to open the dialog passed to it's onClick prop, the dialog shows up and the drawer starts to slide off as it is supposed to do. When the drawer slides off completely, the dialog disappears too.

Steps to Reproduce (for bugs)

Create a component containing < ListItemText /> (inside < ListItem button >) and < Dialog >. Bind function to open the dialog to listitemtext prop onClick.

Import this component into < List > that is inside < Drawer >

Now you can open the dialog by clicking on list item in the drawer.

Working example : https://codesandbox.io/embed/3m46jpwk1

Context

I am react newbie but I am pretty sure that is problem caused by this framework.

I do not know how these components works, but from the behavior I guess when the Drawer stops rendering, the Dialog stops aswell as it is directly in it.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.8

React
15.6.1

browser
Chrome, v60

Issue 2:
Hi, just completed the process of migrating our application to material-ui-next. Most things are working great, but the color theme system only appears to work for some components. We have a configuration object that we run through the createMuiTheme utility and provide it as the theme to the MuiThemeProvider. Even though the theme and the palette are correctly generated, these colors do not carry down to all components, most notably the TabIndicator (which appears as the hideous pink color #f50057), and Input's inkbar:after psuedo-selector, which comes back as '#303f9f'. I can see where these colors appear to be coming from, but shouldn't they be inheriting from the provided theme? Here is my config object (palette is at the bottom). It seems like it should be working to me:

const options = {
palette: {
type: 'light',
primary: {
light: '#1abcf7',
main: '#1abcf7',
dark: '#006699'
},
secondary: {
light: '#00ff00',
main: '#1abcf7',
dark: '#006699'
}
}
}

const theme = createMuiTheme(options)

This has been driving me crazy. Thanks -- Steve

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

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

Material-UI

React

browser

etc
Issue 1:
🐛 Bug

Test case failed but test job passed in windows CI.

To Reproduce

Steps to reproduce the behavior:

Check recent PR's ci report, pytorch_windows_vs2019_py36_cuda10.1_test1 passed but in fact there's always one test cases failed.

It's the example link

Expected behavior

The test job of pytorch_windows_vs2019_py36_cuda10.1_test1 should be failed and block the PR into master.

cc @ezyang @seemethere @malfet @walterddr @peterjc123 @maxluk @nbcsm @guyang3532 @gunandrose4u @smartcat2010 @mszhanyi

Issue 2:
Have a look at those two for example:

https://app.circleci.com/pipelines/github/pytorch/pytorch/222634/workflows/005e1922-33bf-43e0-8e7f-d14cfae47fed/jobs/7964572

https://app.circleci.com/pipelines/github/pytorch/pytorch/222634/workflows/005e1922-33bf-43e0-8e7f-d14cfae47fed/jobs/7964565

TestAtomicOps.TestAtomicMul is failed, but run is considered successful

cc @ezyang @seemethere @malfet @walterddr @peterjc123 @maxluk @nbcsm @guyang3532 @gunandrose4u @smartcat2010 @mszhanyi
Issue 1:
Describe the issue:

Release notes document MD5 checksums for universal2 wheels. However, I can't seem to find one.

Any attempt to python3 -m pip install numpy --target foo --platform=universal2 results in building from source (asks to add --no-deps), which subsequently fails.

What would be the best way to install universal2 (e.g. arm64+x86_64) distribution of numpy?

Reproduce the code example:

n/a

Error message:

: error: no such file or directory: 'build/temp.macosx-10.9-universal2-3.9/numpy/core/src/multiarray/dragon4.o'

Full error: https://gist.github.com/w3sip/a99d0febfd44e7e991b6d32117ba3291

NumPy/Python version information:

$ python3.9 --version
Python 3.9.11
$ which python3.9
/usr/local/bin/python3.9
$ ls -la /usr/local/bin/python3.9
lrwxr-xr-x 1 root wheel 71 Mar 16 2021 /usr/local/bin/python3.9 -> ../../../Library/Frameworks/Python.framework/Versions/3.9/bin/python3.9

Issue 2:
Feature

The binary wheels for macOS on PyPI are currently for x86_64. Please also provide a universal2 wheel (x86_64 and arm64) for use with the (currently experimental) universal2 Python 3.9.1 installer on Python.org.
Issue 1:
I came across the following situation that had some really unexpected behavior:

let [left, top] = (function that returns [number, number]);

var reactComponent = (
<Component left={left} top={top} />
);

inside reactComponent, this.props.top was undefined...

I checked out the generated code, and it looks like babel was rewriting the variable top to _top, but it was also rewriting the prop to _top, so I was left with <Component left={left} _top={_top}, and was losing my prop.

(Rhyming totally unintentional...)

Issue 2:
Sorry for the lack of specificity of this message, but we upgraded from babel-core@5.3.3 / babel-loader@5.0.0 to the latest babel-loader@5.0.0 / babel-core@5.4.5 this morning and we are encountering major breaking changes our code. Pinning the versions back to 5.0.0/5.3.3 has resolved them.

Do you have any advice for how to address these breaking changes, or is this a mistake in this particular release?

Thanks!