WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Hello,

I'm building a tray (menubar) app using electron.

I know that there is a way of getting tray icon bounds through tray.on('click' function(event, bounds){}) event, but sometimes I want to show a BrowserWindow without tray.on('click') event.

For example, when I want to show the BrowserWindow when pressing the GlobalShortcut, it doesn't pass tray.on('click'), so technically there is no way to get bounds of tray icon.

To do this, there is two possible way.

Get a tray position and call BrowserWindow.setBounds()

Call a tray.click event so I can get a tray bounds.

I would appreciate if someone give me any way to resolve this issue.

Thanks.

Issue 2:
For instance when you have a menubar app and you want to trigger window.show() with a global shortcut or any other way that does not involves clicking on the tray icon. :)
Issue 1:
Summary of the new feature/enhancement

I would like to see PowerToys Run offer various sizes of the search bar and results. The default size appears to be fairly large and takes up quite a bit of space on a screen. (my resolution is 1920x1080).

Offering a variety of sizing options can help prevent covering up of screen real estate.

I'm a longtime user of Launch and it offers various skins out of the box that are in different sizes.

Proposed technical implementation details (optional)

Issue 2:
Environment

Windows build number: 10.0.18362.476
PowerToys version: 0.13.0.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

Enable FancyZones

Open a browser (i.e. Chrome)

Create a couple new tabs

Drag a tab off the current browser window such that it becomes it's own window

Drag it around without letting go of the mouse button to another zone that the current browser is not in.

Drag this new window around a few times (usually around 3-4) to new zones.

Expected behavior

FancyZones zone is used by the window and overlay disappears

Actual behavior

After a few tries of moving the window around, the FancyZone overlay stays on the screen and appears to no longer work. If I use the shortcut key Windows + ~ and hit apply, most of the time this will fix the issue, the overlay disappears and it still works - but sometimes the overlay disappears and FancyZones no longer works (I have to kill PowerToys from Task Manager and restart it)

Screenshots
Issue 1:
It seems that the histogram legend appears twice. I expected it to show only once. Did I miss something?

Issue 2:
I'm running this code from Discovering structure in heatmap data example in the gallery.

%pylab inline

import pandas as pd
import seaborn as sns
sns.set()

# Load the brain networks example dataset
df = sns.load_dataset("brain_networks", header=[0, 1, 2], index_col=0)

# Select a subset of the networks
used_networks = [1, 5, 6, 7, 8, 12, 13, 17]
used_columns = (df.columns.get_level_values("network")
.astype(int)
.isin(used_networks))
df = df.loc[:, used_columns]

# Create a categorical palette to identify the networks
network_pal = sns.husl_palette(8, s=.45)
network_lut = dict(zip(map(str, used_networks), network_pal))

# Convert the palette to vectors that will be drawn on the side of the matrix
networks = df.columns.get_level_values("network")
network_colors = pd.Series(networks, index=df.columns).map(network_lut)

# Draw the full plot
sns.clustermap(df.corr(), center=0, cmap="vlag",
row_colors=network_colors, col_colors=network_colors,
linewidths=.75, figsize=(13, 13))

When I run it, the top and bottom rows are truncated by half causing all of the rows to slightly misalign with the dendrograms.

This is with the latest release 0.9.0 and matplotlib version 3.1.1.
Issue 1:
Bug report

Describe the bug

npm run build with invokes 'next build' is hanging forever.

To Reproduce

Cannot specify steps to reproduce because it suddenly not

Expected behavior

It should build normally so that I can run npm start.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

OS: [e.g. macOS, Windows]

Browser (if applies) [e.g. chrome, safari]

Version of Next.js: [e.g. 6.0.2]

Additional context

Add any other context about the problem here.

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

Expected Behavior

npm run build - expect to build for deploy

Current Behavior

receive an error:

Failed to build on C:\Users\psycu\AppData\Local\Temp\6d75aadf-8045-42b3-9a00-69e315dbec1c

{ Error: commons.js from UglifyJs

Unexpected token: name (onClickOutside) [commons.js:94268,33]

at D:\Sites\training\boilerplates\with-mobx\node_modules\next\dist\server\build\index.js:182:21

at emitRecords.err (D:\Sites\training\boilerplates\with-mobx\node_modules\webpack\lib\Compiler.js:269:13)

at Compiler.emitRecords (D:\Sites\training\boilerplates\with-mobx\node_modules\webpack\lib\Compiler.js:375:38)

at emitAssets.err (D:\Sites\training\boilerplates\with-mobx\node_modules\webpack\lib\Compiler.js:262:10)

at applyPluginsAsyncSeries1.err (D:\Sites\training\boilerplates\with-mobx\node_modules\webpack\lib\Compiler.js:368:12)

at next (D:\Sites\training\boilerplates\with-mobx\node_modules\tapable\lib\Tapable.js:218:11)

at Compiler.compiler.plugin (D:\Sites\training\boilerplates\with-mobx\node_modules\webpack\lib\performance\SizeLimitsPlugin.js:99:4)

at Compiler.applyPluginsAsyncSeries1 (D:\Sites\training\boilerplates\with-mobx\node_modules\tapable\lib\Tapable.js:222:13)

at Compiler.afterEmit (D:\Sites\training\boilerplates\with-mobx\node_modules\webpack\lib\Compiler.js:365:9)

at require.forEach.err (D:\Sites\training\boilerplates\with-mobx\node_modules\webpack\lib\Compiler.js:354:15)

errors: [ 'commons.js from UglifyJs\nUnexpected token: name (onClickOutside) [commons.js:94268,33]' ],

warnings: [] }

npm ERR! code ELIFECYCLE

npm ERR! errno 1

npm ERR! with-mobx@1.0.0 build: next build

npm ERR! Exit status 1

npm ERR!

npm ERR! Failed at the with-mobx@1.0.0 build script.

npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

npm ERR! C:\Users\psycu\AppData\Roaming\npm-cache_logs\2017-10-28T13_26_00_550Z-debug.log

Steps to Reproduce (for bugs)

im using firebase,mobx,emotion libraries.

on dev mode everything for fine, but buil cannot be completed.

I think it maybe some connection to my .babelrc file that include:

{ "presets": [ "next/babel" ], "plugins": [ "transform-decorators-legacy", [ "transform-assets-import-to-string", { "baseDir": "static", "baseUri": "/" } ], [ "emotion", { "inline": true } ] ] }

Your Environment

Tech
Version

next
latest

node
8.5.0

OS
windows 10 64bit

browser
chrome

etc
Issue 1:
So, I don't know if this is by design, but it sure confused me. to_timedelta() operates differently on the number 1000 compared to the string '1000':

In[3]: pd.to_timedelta(1000, unit='ms')
Out[3]: Timedelta('0 days 00:00:01')
In[4]: pd.to_timedelta(1000.0, unit='ms')
Out[4]: Timedelta('0 days 00:00:01')

and

In[6]: pd.to_timedelta('1000ms')
Out[6]: Timedelta('0 days 00:00:01')

while

In[5]: pd.to_timedelta('1000', unit='ms')
Out[5]: Timedelta('0 days 00:00:00.000001')

I've tried my best to come up with a reason for why this behaviour would be desirable, but I can't think of any.

Issue 2:
Code Sample, a copy-pastable example if possible

http://stackoverflow.com/questions/32750970/python-pandas-merge-causing-memory-overflow

# coding: utf-8
import pandas as pd
data = pd.read_csv('https://gist.githubusercontent.com/xgdgsc/8671a22136e1da937f1046a5f211c0ff/raw/d261706a6e7d1d7014e45e47122ead71e7159ef4/small.csv', index_col='<Date>')
print(data.shape)
another = data[[ ' <Open>']]
joined = data.join([another])
print(joined.shape)

Problem description

Currently having index with duplicate keys when joining dataframes would cause severe memory overflow, sometimes freezes the computer and user has to hard reboot, which can be disastrous for unsaved work.

Expected Output

Adding a simple checking before joining/merging , stop the operation and warn the user would be enough.

Output of pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 3.5.2.final.0
python-bits: 64
OS: Windows
OS-release: 10
machine: AMD64
processor: Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
byteorder: little
LC_ALL: None
LANG: None

pandas: 0.18.1

nose: 1.3.7

pip: 8.1.2

setuptools: 27.2.0

Cython: 0.24.1

numpy: 1.11.1

scipy: 0.18.1

statsmodels: 0.6.1

xarray: None

IPython: 5.1.0

sphinx: 1.4.6

patsy: 0.4.1

dateutil: 2.5.3

pytz: 2016.6.1

blosc: None

bottleneck: 1.1.0

tables: 3.2.2

numexpr: 2.6.1

matplotlib: 1.5.3

openpyxl: 2.3.2

xlrd: 1.0.0

xlwt: 1.1.2

xlsxwriter: 0.9.3

lxml: 3.6.4

bs4: 4.5.1

html5lib: None

httplib2: None

apiclient: None

sqlalchemy: 1.0.13

pymysql: None

psycopg2: None

jinja2: 2.8

boto: 2.42.0

pandas_datareader: None
Issue 1:
If a header has been set as a default, there does not appear to be any way to skip it on an individual request. Setting null or undefined doesn't do anything.

Issue 2:
Describe the issue

I have a component that initiates multiple requests to an API. If the user makes any subsequent requests to the same API before the server replies, previous calls are canceled. This works as expected. However, once a request gets canceled, an error is thrown, and axios doesn't correctly detect it is a cancel error (via axios.isCancel(error))

EXAMPLE:

Make API request, requestA, to '/api/does-stuff'

Before there is a response from requestA, make another API request, requestB, to '/api/does-stuff'

requestA gets canceled and throws an error

When handling the error, check if it is an axios cancelation error (via axios.isCancel(error))

axios.isCancel(error) always returns false 😭

Example Code

Code snippet to illustrate your question

// Custom helper in my app to build a cancelable request
function buildCancelableRequest() {
let call

return requestOptions => {
if (call) call.cancel()
call = axios.CancelToken.source()

return axios({ cancelToken: call.token, ...requestOptions })
.then(() => {
console.log('success')
})
.catch(error => {
console.log(axios.isCancel(error)) // This is always false, even when the request cancels
})
}
}

...

// Usage
const myService = buildCancelableRequest()
myService({
method: 'get',
url: '/api/my-custom-api'
})

Expected behavior, if applicable

axios.isCancel() should return true when the request cancels

Environment:

Axios Version: 0.19.2

Browser: Chrome

Browser Version: 79

Additional Library Versions: React 16.12.0
Issue 1:
Are static functions meant to be in trait scope, or module scope? Here's an example:

trait Vector2<T:Num Ord FuzzyEq> {
pure fn x() -> T;
pure fn y() -> T;

static pure fn make(&&x:float, &&y:float) -> self;
}

trait Vector3<T:Num Ord FuzzyEq> {
pure fn x() -> T;
pure fn y() -> T;
pure fn z() -> T;

static pure fn make(&&x:float, &&y:float, &&z:float) -> self;

fn cross(&&other:self) -> self;
}

trait Vector4<T:Num Ord FuzzyEq> {
pure fn x() -> T;
pure fn y() -> T;
pure fn z() -> T;
pure fn w() -> T;

static pure fn make(&&x:float, &&y:float, &&z:float, &&w:float) -> self;
}

This is the error I get when I try to compile:

rustc src/om3d.rc --lib --out-dir=lib
src/vec.rs:61:4: 61:64 error: Duplicate definition of value make
src/vec.rs:61 static pure fn make(&&x:float, &&y:float, &&z:float) -> self;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/vec.rs:53:4: 53:53 note: First definition of value make here:
src/vec.rs:53 static pure fn make(&&x:float, &&y:float) -> self;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/vec.rs:72:4: 72:75 error: Duplicate definition of value make
src/vec.rs:72 static pure fn make(&&x:float, &&y:float, &&z:float, &&w:float) -> self;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/vec.rs:61:4: 61:64 note: First definition of value make here:
src/vec.rs:61 static pure fn make(&&x:float, &&y:float, &&z:float) -> self;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: aborting due to 2 previous errors

Issue 2:
When trying to do rustc development on the stage1 compiler, I've been hitting a link error.

I suspect something has gone wrong in our make dependencies because I think the problem goes away if you first do a full build before doing check-stage1-cfail (I think, though I have not double-checked that scenario from scratch in a clean build dir yet).

% uname -a
Darwin fklockii-Eris.local 13.4.0 Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
% git log -1 --oneline
1b46b00 auto merge of #17784 : bkoropoff/rust/issue-17780, r=pcwalton
% ../configure --enable-debug --disable-optimize --enable-ccache --enable-clang --prefix=~/opt/rust-dbg-nopt && make clean && make check-stage1-cfail
[... expurgated ...]
/Users/pnkfelix/Dev/Mozilla/rust.git/src/compiletest/compiletest.rs:1:1: 1:1 error: can't find crate for `rt`
/Users/pnkfelix/Dev/Mozilla/rust.git/src/compiletest/compiletest.rs:1 // Copyright 2012-2014 The Rust Project Developers. See the COPYRIGHT
^
error: aborting due to previous error
make: *** [x86_64-apple-darwin/stage0/lib/rustlib/x86_64-apple-darwin/bin/compiletest] Error 101
Issue 1:
when sla happen, not always delete the dag_run, but it happen very frequently

when dag_run is deleted, my unfinished task will not schedule

mysql version: 8

executor: celery

with multi scheduler

if need anything else info please let me know

also, sometimes will call the sla callback twice(it is not the big problem)

Issue 2:
Description

This would allow users to create a bunch of connections at once from a file.

Use case / motivation

I think having some parody between the connections and variables commands could be beneficial and provide a more pleasant UX for cli users.

For example when I did airflow connections -h and didn't see a -i it felt weird seeing as how this is possible for variables.

So I was left feeling a little confused; I was expecting it to be there
Issue 1:
Summary of the new feature/enhancement

I think it would be nice if there were options to exclude certain items from PowerToys Run. This could include:

Installers

Uninstallers

UWP in-development apps

I don't like seeing a bunch of uninstallers when I'm trying to search for something, although some users may.

Issue 2:
I would like to have the possibility to remove icon tray from the taskbar.
Issue 1:
Normalizer gets executed for optional parameters when it is not passed.

This can cause several issues, eg.: Have an optional array option, and you want to do some normalization (filter out values, etc). Now I need to check in the normalizer closure, whether an array is passed and return an empty array if not, or I get an excpetion of invalid type.

So I think normalizers SHOULD NOT be executed on not passed optional options.

Issue 2:
See #6215 and #6233.

When running

$resolver->setOptional(array('foo'));
$resolver->setNormalizers(array(
'foo' => function (Options $options, $previousValue) {
return doSomethingWith($previousValue);
},
));

$options = $resolver->resolve(array());

then the normalizer is currently executed even though the option is missing. Since there is a test that asserts this behavior, we can't change it without breaking BC.

In Symfony 3.0, normalizers should not be executed for missing options.
Issue 1:
We are using AutoComplete with filtering for selecting options from hundreds of items. But when we specify filter and only one option is visible in suggestions, pressing enter should allow to select it (trigger onNewRequest with this item). Now user have to use keydown to select option and then press enter to select the option. It is a little annoying, especially that using keydown with AutoComplete and openOnFocus is problematic as described in #4922

I know that it can break some functionality with selecting values not listed. But connecting this feature with #5494 can give a great user experience.

Link to minimal working code that reproduces the issue

http://www.material-ui.com/#/components/auto-complete

example: 'Type 'peah', fuzzy search'

type 'peac' - only one option should be visible

press Enter - option 'Peach' should be selected

Versions

Material-UI: 0.18.4

React: 15.4.2

Browser: Chrome, IE

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

Expected Behavior

I would like the ability to modify the default TabScrollButtons when scrollButtons are enabled. This would include the following:

The ability to change the default SvgIcon for the Scroll Buttons in the Tabs component

The ability to disable the ripple effect for the TabScrollButtons with disableRipple

Current Behavior

When scrollButtons="on", two button elements are rendered for the previous/next arrows, each with their own SVG (KeyboardArrowRight and KeyboardArrowLeft). I currently am not aware of a solution to replace those with my own SVGs and further customize their settings.

Current Code

import React from 'react';
import Tabs, { Tab } from 'material-ui/Tabs';

const TabBar = ({ tabs, activeTab, setActiveTab }) =>
(<MaterialTabs>
<Tabs
value={activeTab}
onChange={setActiveTab}
scrollable
scrollButtons="on"
>
{tabs.map(({ id, name }) =>
(<Tab
key={id}
label={name}
value={id}
disableRipple
/>),
)}
</Tabs>
</MaterialTabs>);

export default TabBar;

Your Environment

Tech
Version

Material-UI
1.0.0-beta.13

React
15.6.2

browser
Chrome version 61.0.3163.100
Issue 1:
Migrated issue, originally created by Michael Bayer (@zzzeek)

people.join(managers).outerjoin(boss) in polymorph.py does not fold properly if you apply select(folded_equivalents=True) to it

Issue 2:
Migrated issue, originally created by Ronny Pfannschmidt (@RonnyPfannschmidt)

oracle stored procedures cant be invoked by a select, instead one must call them in a anonymous block

a way to either access those via the dbapi.callproc method or generating the fit sql would be nice

currently i work around by compiling to a block on oracle and a select on postgresql

i didnt examine other databases
Issue 1:
Just as the empty sum is 0 and the empty product is 1, the empty norm should be 0 in my opinion. In numpy, this convention has been implemented and is unit-tested for the default vector and matrix norms:

def test_empty(self):
assert_equal(norm([]), 0.0)
assert_equal(norm(array([], dtype=self.dt)), 0.0)
assert_equal(norm(atleast_2d(array([], dtype=self.dt))), 0.0)

Some of the non-default empty norms raise exceptions. The induced matrix 2-norm raises exceptions for two reasons -- first, attempting to compute the singular values of a size-0 matrix raises an exception, and second, even if the the empty array of singular values were to be returned, attempting to compute the max of an empty sequence also raises an exception. The empty induced matrix 1-norm and np.inf-norm each also raise an exception because they try to compute an empty max.

Issue 2:
It may sound silly but it may be of interest to be able to compute the norm of [] so that one has not to catch this case before (would make my code more readable).

At the moment numpy.linalg.norm(numpy.array([]),ord=):

works with ord = 0,1,2,... giving the result 0. Although here is a incosistency returning np.int in the case of ord = 0 and np.float in the others.

works not not with ord = numpy.inf since this computes abs(x).max() without checking if x is nonempty.

It would be very nice, if in the [] case also for ord = inf one would return 0, which would be consistent with matlab behaviour.
Issue 1:
💻

Would you like to work on a fix?

How are you using Babel?

Programmatic API (babel.transform, babel.parse)

Input code

async({ foo33 = 1 });

Configuration file name

No response

Configuration

Default parser config

Current and expected behavior

foo33 = 1 is parsed as an ObjectProperty whose value is an AssignmentPattern. It should throw, since objects cannot have property initializers with =.

Environment

Babel 7.14.4

Possible solution

No response

Additional context

Reported at https://twitter.com/buzyescayadev/status/1398526884955058181

Issue 2:
Bug Report

I would like to work on a fix!

Current behavior

REPL

Input Code

interface PropsType {
isTrue: boolean;
render: (
children: React.ReactElement | React.ReactElement[] | undefined,
props: {},
) => React.ReactElement;
children: React.ReactElement | React.ReactElement[] | undefined;
}

// definition
export const switchRender = ({
isTrue,
render,
children,
...props
}: PropsType): React.ReactElement | React.ReactElement[] | undefined =>
isTrue ? render(children, props) : children;

Error:

14 | children,
15 | ...props
> 16 | }: PropsType): React.ReactElement | React.ReactElement[] | undefined =>
| ^
17 | isTrue ? render(children, props) : children;

Expected behavior

Error should not be here.

Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)

Filename: babel.config.js

{
presets: [
[
'@babel/env',
{
useBuiltIns: 'usage',
corejs: 3,
},
],
'@babel/react',
'@babel/preset-typescript',
],
...
}

Environment

System:
OS: macOS 10.15.6
Binaries:
Node: 12.19.0 - /usr/local/opt/node@12/bin/node
Yarn: 1.22.10 - ~/Desktop/work/meep-lerna/node_modules/.bin/yarn
npm: 6.14.8 - /usr/local/opt/node@12/bin/npm
Monorepos:
Yarn Workspaces: 1.22.10
Lerna: 3.22.1
npmPackages:
@babel/cli: ^7.7.0 => 7.12.1
@babel/core: ^7.7.2 => 7.12.1
@babel/plugin-proposal-class-properties: ^7.7.0 => 7.12.1
@babel/plugin-proposal-decorators: ^7.7.0 => 7.12.1
@babel/plugin-proposal-export-default-from: ^7.5.2 => 7.12.1
@babel/plugin-proposal-nullish-coalescing-operator: ^7.7.4 => 7.12.1
@babel/plugin-proposal-optional-chaining: ^7.6.0 => 7.12.1
@babel/plugin-transform-runtime: ^7.6.2 => 7.12.1
@babel/preset-env: ^7.7.1 => 7.12.1
@babel/preset-react: ^7.7.0 => 7.12.1
@babel/preset-typescript: ^7.7.2 => 7.12.1
@babel/runtime: ^7.7.2 => 7.12.1
babel-eslint: ^10.0.3 => 10.1.0
babel-jest: ^24.9.0 => 24.9.0
babel-loader: ^8.0.5 => 8.1.0
babel-plugin-css-modules-transform: ^1.6.1 => 1.6.2
babel-plugin-module-resolver: ^3.1.1 => 3.2.0
babel-plugin-transform-imports: ^2.0.0 => 2.0.0
eslint: ^6.7.2 => 6.8.0
eslint-import-resolver-babel-module: ^5.0.0-beta.1 => 5.1.2
jest: ^24.9.0 => 24.9.0
lerna: ^3.19.0 => 3.22.1
webpack: ^4.41.2 => 4.44.2

Babel version(s): v7.12.1

Node/npm version: Node 12.19.0/npm 6.14.8

OS: OSX 10.15.6

Monorepo: Lerna

How you are using Babel: cli

Possible Solution

I think this bug is caused by #12183

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

Expected Behavior

icon props should no longer accept String type Icon font ligature.

Result:

API inconsistency.

Reduced user bundle size for affected components (no default Icon component import, and a few bytes less code).

Current Behavior

Only 5 of the 12 components with icon or xxxIcon props allow a string to be provided (IconButton, SwitchBase, Tab, BottomNavigationActions & ExpansionPanelSummary).

Avatar allows an Icon or string child, but treats the string as a label.

The internal implementation of ligature support is inconsistent, and in at least one case buggy.

Steps to Reproduce (for bugs)

N/A

Context

There have been no issues raised to add support to other components. It appears this functionality is unused.

Your Environment

N/A

Issue 2:
RTL support demo is not working as described:

https://codesandbox.io/s/yqypn8pprz

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

Expected Behavior

The label in the text box should be on the right side as in the example, but this is not the case.

Steps to Reproduce (for bugs)

Run the demo:

https://codesandbox.io/s/yqypn8pprz

Context

Your Environment

Tech
Version

Material-UI
Demo version