WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Bug report

Bug summary

Using the nbagg backend with matplotlib in a jupyter notebook and plotting the figure inside a ipywidgets.Output() widget breaks the functionality of the "Stop Interaction" button. If pressed, nothing happens.

Code for reproduction

Use inside a jupyter notebook.

import ipywidgets as widgets
import matplotlib.pyplot as plt

%matplotlib notebook
# or %matplotlib nbagg

o = widgets.Output()
display(o)
with o:
plt.plot(range(10), range(10))
plt.show()

Actual outcome

Red circle added on the button for emphasis.

Expected outcome

Matplotlib version

Operating system: Linux 5.10.11-arch1-1

Matplotlib version: 3.3.4

Matplotlib backend: nbagg

Python version: 3.9.1

Jupyter version:

jupyter core : 4.6.3

jupyter-notebook : 6.2.0

qtconsole : not installed

ipython : 7.19.0

ipykernel : 5.4.2

jupyter client : 6.1.7

jupyter lab : not installed

nbconvert : 6.0.7

ipywidgets : 7.6.2

nbformat : 5.0.8

traitlets : 5.0.5

All Python related packages installed via pip.

Issue 2:
Bug report

Bug summary

Plot not being displayed using notebook toolkit on the output widget depending on order of output.

Code for reproduction

cell 1:

%matplotlib notebook
from matplotlib import pyplot as plt
import ipywidgets as wg

cell 2:

test_out = wg.Output()
display(test_out)
with test_out:
plt.figure()
plt.plot([1,2,3])

cell 3:

test_out = wg.Output()
with test_out:
plt.figure()
plt.plot([1,2,3])
display(test_out)

Actual outcome

Expected outcome

same output for cell 3 as cell 2:

Matplotlib version

Operating system: win

Matplotlib version: 3.0.2

Matplotlib backend : nbAgg

Python version: Python 3.7.1

Jupyter version (if applicable): 5.7.4

Other libraries: ipywidgets 7.5.1
Issue 1:
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

No

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Any

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:

TensorFlow installed from (source or binary): source

TensorFlow version (use command below): 1.9

Python version: 3.5.3

Bazel version (if compiling from source): 1.12

GCC/Compiler version (if compiling from source):

CUDA/cuDNN version: 9.2

GPU model and memory: Titan XP

Exact command to reproduce:

Make sure you have numpy 1.15.0 installed:

run tensorboard

A few RuntimeWarning appear

If you have version 1.14.5 installed instead, no RuntimeWarnings appear.

Describe the problem

Running tensorboard with numpy 1.15.0 gives a few RuntimeWarning (see below). All is fine with numpy 1.14.5 and below.

Source code / logs

return f(*args, **kwds)
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88
return f(*args, **kwds)
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88
return f(*args, **kwds)
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88
return f(*args, **kwds)```

Issue 2:
This template is for miscellaneous issues not covered by the other issue categories.

For questions on how to work with TensorFlow, or support for problems that are not verified bugs in TensorFlow, please go to StackOverflow.

If you are reporting a vulnerability, please use the dedicated reporting process.

For high-level discussions about TensorFlow, please post to discuss@tensorflow.org, for questions about the development or internal workings of TensorFlow, or if you would like to know how to contribute to TensorFlow, please post to developers@tensorflow.org.
Issue 1:
System info

Playwright Version: 1.32

Operating System: macOS

Browser: Chromium

Other info:

Source code

Config file

// playwright.config.ts
import { defineConfig, devices } from '@playwright/test';

export default defineConfig({
projects: [
{
name: 'chromium',
use: { ...devices['Desktop Chrome'], },
},
});

Test file (self-contained)

import { test, expect } from '@playwright/test';

test.beforeEach(async ({ request }) => {
const test = await request.get(`https://catfact.ninja/fact`);
expect(test.ok()).toBeTruthy();
});

test('some steps', async ({ page }) => {
await page.goto('https://playwright.dev/');
await page.waitForTimeout(5000)
await expect(page).toHaveTitle(/Playwright/);
});

Steps

Run the test using UI watch mode and observe the live trace

Expected

The live trace is rendered as the test runs

Actual

The live trace is not rendered as the test runs.

In our framework implementation, we make api call to create a new workspace (in beforeEach block) in every test

Issue 2:
Context:

Playwright Version: 1.7.0

Operating System: Linux

Node.js version: 12.19

Browser: Chromium

Code Snippet

const { chromium } = require("playwright");

(async () => {
const browser = await chromium.launch();
const page = await browser.newPage();

let inProgress = 0;

page.on('request', request => {
console.log(Date.now(), '>>', request.method(), request.url());
inProgress++;
});
page.on('response', response => {
console.log(Date.now(), '<<', response.status(), response.url());
inProgress--;
});

console.log(Date.now(), "waiting for page");
await page.goto("http://localhost:3000/", {
// waitUntil: "networkidle",
});

console.log(Date.now(), "waiting 500");
await page.waitForTimeout(500);

console.log(Date.now(), "waiting for networkidle");
await page.waitForLoadState("networkidle");

console.log(Date.now(), "Requests in progress after networkidle:", inProgress);

await browser.close();
})();

Describe the bug

The networkidle event can fire even though requests are in progress (but are taking longer, for example). I would expect the event to fire after 500ms of no requests in progress. (The example script should always finish with inProgress === 0 but doesn't.)

I was not able to reproduce this during page load with waitUntil: "networkidle", so perhaps the logic is different there?
Issue 1:
Duplicate default label is a runtime error in JS, this should be a syntax error in TS

switch (moduleKind) {
default: return ModuleKind.None;
default: throw Error("unsuported ModuleKind value: " + moduleKind);
}

Issue 2:
Hi,

TS: 1.4

To reproduce.

Create a TypeScript project in Visual Studio with "Compile on save" set to on.

Add file enums.d.ts with code:

declare module enums {
const enum Bar {
one = 0,
two = 1,
}
}

Add file foo.ts with code:

/// <reference path="enums.d.ts" />
var foo = enums.Bar.one;

Compile the project and check that the output foo.js is correct:

/// <reference path="enums.d.ts" />
var foo = 0 /* one */;

Now trigger compile-on-save by saving foo.ts.

The output in foo.js is now broken:

/// <reference path="enums.d.ts" />
var foo = enums.Bar.one;

The following point is relevant: If the enum declaration is moved to foo.ts then things work correctly.

This is a significant issue because the code fails with a runtime error.
Issue 1:
Description of the problem

I noticed that there was a significant slowdown in the app I'm developing. I narrowed it down to being caused by initMaterial being called each frame under certain very specific conditions

. The minimum requirements to reproduce the bug (afaik) are:

Create two meshes which share the same MeshLambertMaterial.

Create two scenes and add the meshes to them.

Create a single DirectionalLight in one of the scenes, not both.

Create an OrthographicCamera overlooking the objects (not a perspective camera).

Call render twice, once for each scene.

If you don't notice the slowdown, use the performance tab in Firefox to measure the performance and you should see WebGLShader at the top of the call tree.

Live sample

Three.js version

Dev

Browser

Firefox

OS

Windows

Issue 2:
WebGLLights is used to store lighting state.

WebGLLights.hash property is used to determine whether or not a material needs to be re-built.

three.js/src/renderers/WebGLRenderer.js

Lines 1479 to 1482
in
bd63a6c

} else if ( materialProperties.lightsHash !== lights.state.hash ) {

properties.update( material, 'lightsHash', lights.state.hash );

programChange = false;

The way hash is built, it includes unique reference to WebGLLights instance:

three.js/src/renderers/webgl/WebGLLights.js

Line 319
in
efeb95f

state.hash = state.id + ',' + directionalLength + ',' + pointLength + ',' + spotLength + ',' + rectAreaLength + ',' + hemiLength + ',' + shadows.length;

constructor:

three.js/src/renderers/webgl/WebGLLights.js

Lines 103 to 111
in
efeb95f

var count = 0;

function WebGLLights() {

var cache = new UniformsCache();

var state = {

id: count ++,

this means that if you have 2 instances of WebGLLights and they are identical, except for id - you will end up rebuilding materials as you switch between these instances - inefficient.

Another problem with the current approach is that it is probabilistic, it's possible that hash remains the same even though lighting has changed.

I propose following:

remove id from hash calculation

use a fast hashing function to compute 64bit hash(javascript number is IEEE 64-bit Float) instead of using a string

pass more than just number of lights into the hash (as long as that makes sense).
Issue 1:
Operating System: Windows 8.1 x64, Windows 7 x64

Atom Version: v1.0.0

Attached screenshot for reference.

Issue 2:
From @GameplayJDK on June 7, 2015 10:28

I just updated to version 0.207.0 and found this:

Somehow the LAST_TODO file (which is a file without an extension) is hows as a folder in my tree view. As such, I can't open it from there and need to use "File -> Open File..." to do so.

This also happens to other files (with extensions), as shown below:

Copied from original issue: atom/atom#7152
Issue 1:
Chrome wrongly detects input devices, so it enables touchscreen interface. This means that:

menu is harder to use, as it doesn't detect mousemove

mouse input is broken, it detects all mouse buttons as button 1

selection is broken, a touchscreen selection tool appears

the same problems happen when I use Chrome internal controls, like dev tools

Bug still happens when I:

rm -rf ~/.atom ~/.config/Atom ~/.cache/Atom

run atom under a new user account

replace virtual machine graphic cards, change input devices

rebuild from scratch (scripts/clean)

try various chrome flags (--touch-events=disabled, --disable-touch-input, ...)

Bug doesn't happen when I:

run atom under a Xephyr X server.

Bug happens on:

master

v0.193.0

v0.194.0

v0.195.0

v0.196.0

v0.197.0

v0.198.0

Bug doesn't happen on:

v0.188.0

previous versions

I assume that the problem is due to upgrading to Chrome 21.

Issue 2:
There is a known issue with Chrome41 engine running on Linux in VirtualBox. It actually became a show-stopper for Chrome42. TL;DR: in VB Chrome41 engine always runs in touch-screen mode, even on desktops.

Hotfix in Chrome41 is to pass --touch-devices=123 to the chrome command line.

Is it possible to pass parameters to Atom’s command line so that chrome engine will understand them?
Issue 1:
I create some dynamic components with a sample router, but when I change the currentView value to render the component, there are some warn message print like:

Data field "xxx" is already defined as a prop. Use prop default value instead.

obviously, I passed the parent data by props

with Vue.js 1.0.0-alpha.8

Issue 2:
Version

2.6.11

Reproduction link

https://jsfiddle.net/dpcmr1tz/

Steps to reproduce

I can not using syntax babel in vue file, it error by vue-template-compile

What is expected?

I hope to can using syntax babel 7 like example: message?.name, with "message" is a object

What is actually happening?

I can not using syntax babel in vue file, it error by vue-template-compile
Issue 1:
If I look at the backend section of the FAQ:

https://matplotlib.org/faq/usage_faq.html#what-is-a-backend

it seems like the backend table is missing notebooks. If I instead go to the backends section of the introduction:

https://matplotlib.org/3.2.1/tutorials/introductory/usage.html#backends

I get a super similar table, but with (I think) a more up-to-date list, including the nbagg and ipympl backends.

Tellingly, the <title> for the former page says "Matplotlib 2.0.2 documentation", despite having no version indicator on the URL.

Apologies if this is a duplicate — I did try a quick search but did not turn up a similar issue.

Issue 2:
On the current live docs, the examples page claims to be from release 2.0.2, but it should be 2.1: http://matplotlib.org/examples/index.html
Issue 1:
I have just started noticing new(?) errors in the kubelet.log after a pull saturday.

E0810 16:21:55.554843 13225 volume.go:174] Could not read directory: /var/lib/kubelet/.bash_logout/volumes, (open /var/lib/kubelet/.bash_logout/volumes: not a directory)
E0810 16:21:55.554867 13225 volume.go:174] Could not read directory: /var/lib/kubelet/.bashrc/volumes, (open /var/lib/kubelet/.bashrc/volumes: not a directory)
E0810 16:21:55.554899 13225 volume.go:174] Could not read directory: /var/lib/kubelet/.profile/volumes, (open /var/lib/kubelet/.profile/volumes: not a directory)

Issue 2:
This error appears every 10 seconds (with .bash_logout & .bash_profile also), when set up with vagrant:

Aug 12 23:16:58 kubernetes-minion-1 kubelet[10777]: E0812 23:16:58.200218 10777 volume.go:174] Could not read directory: /var/lib/kubelet/.bashrc/volumes, (open /var/lib/kubelet/.bashrc/volumes: not a directory)

This is because the kubelet root directory defaults to /var/lib/kubelet, which is also the homedir for the kubelet user, and so the user's default files trip up kubelet. Manually deleting the files (rm /var/lib/kubelet/.bash*) causes the errors to stop without any obvious ill-effects.
Issue 1:
Make sure these boxes are checked before submitting your issue - thank you!

[yes] I have checked the superset logs for python stacktraces and included it here as text if any

[yes] I have reproduced the issue with at least the latest released version of superset

[yes] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

Superset 0.20.4

Expected results

Only one dashboard with multiple data source which can change for specific users.

Issue 2:
Imagine you've connected a data source to Superset, containing data on all your clients and their corresponding account managers. To help the account managers perform their jobs better, you decide to build a beautiful dashboard containing all the right charts and visuals. However, these account managers shouldn't be able to see each other's client data (sensitive, security, etc.)

If you only have a handful of account managers (AMs), it's easy to write a script to split the master data set into account manager-specific subsets before importing it to Superset, and then create tables from there. Problem solved.

What if you have hundreds of AMs? One way to go about this is create a single dashboard with slices associated to the master data set, add a filter box, select the AM you want to narrow the data down to, and then export the report as a static image. This has several drawbacks:

The dashboard the AM receives is a static image.

Someone has to do apply the filter and perform the export manually each time.

AMs have to wait for someone to send them the report each time they want it.

Now, if it were possible to adapt the existing filter box to auto-detect the Superset user and auto-apply a preset filter, then disable the dropdown menu from being changed, you could do away with those 3 drawbacks.

Of course there are millions of other ways to go about this, but thought I'd throw this out there.
Issue 1:
0.18.2 on windows , when close the devtools windows the renderer process not real closed. so repeatedly open and close the devtools cause multiple renderer processes remained.

Issue 2:
Here is my programme:

var app = require('app'); // Module to control application life.

// quit when all windows are closed.
app.on('window-all-closed', function() {
app.quit();
});

app.on('ready', function() {
var mainWindow = new BrowserWindow( {
title: "foobar",
width: 800,
height: 600,
show: false,
resizable: true,
} );

mainWindow.loadUrl('file://' + __dirname + '/index.html');
mainWindow.show();
// mainWindow.openDevTools();
});

If I comment out the opendDevTools() code, or if I open a dev-tools during using of my application, the application will not quit normally. It will stun at the end.

I test this in atom-shell v18.2 in Mac OSX.
Issue 1:
I found some discussion about this in #10146 (comment), but no dedicated issue.

What I would expect this to look like:

type Foo
a::Int32
b::Int32
c::Int32

function Foo()
return new(c = 123) # a and b undefinied
end
end

Issue 2:
The Problem

Currently, when defining inner constructors, we can decide to incompletely initialize a structure simply by passing to new(...) fewer values than the number of fields:

struct Incomplete
x1
x2
x3
...
x719
Incomplete(x1, x2, x3, x4) = new(x1, x2, x3, x4) # x5, ..., x719 are uninitialized
end

Since the call to new(...) accepts only positional arguments, this has the obvious limitation that we can only initialize a prefix of all the fields and leave the remaining ones uninitialized. It is impossible to initialize only x1, x42, x470 and x666.

The Proposal

My proposal is to allow new(...) to accept keyword arguments, so that the following code becomes legal:

struct Incomplete
x1
x2
x3
...
x719
Incomplete(a, b, c, d) = new(x1=a, x42=b, x470=c, x666=d) # the other fields are uninitialized
end

Remarks

Motivation

It is just useful sometimes to be able to do this. See for instance this thread where I asked on the forum if there was a way to achieve this with the current state of the language. There are plenty of workarounds, with more or less significant downsides (complexity-wise and performance-wise), but no direct solution.

Backward compatibility

This should be 💯.

Downsides

I honestly don't see any.

Labels

design, feature, keyword arguments, types and dispatch
Issue 1:
Hi,

I have a page with regular content div = mypage.html

and I want a part of this content to be displayed in modal popup

when the url have an id = mypage.html#2 (will popup only the div id#2)

Is this possible to have both way to display the content without duplicate the content?

Thanks

Issue 2:
In the docs (http://getbootstrap.com/css/#responsive-utilities-tests), the section titled "Hidden on..." says that the green boxes with checkmarks show which boxes are hidden on my screen, but this is not the case. The gray boxes are the ones that are hidden on my "large" screen:
Issue 1:
First of all I am Japanese and I am poor at English.

I am writing a sentence by specifying translation software. I am sorry if it does not pass

Please allow pushState when js file and query parameters in pages directory suffered

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

Expected Behavior

<Link { ...object } pushState>text</Link>

I want you to be pushState instead of replaceState when describing as described above

Steps to Reproduce (for bugs)

Precondition

/a/b/?query1=1 => express rewrite => /page1/?query=1&query=2

go to /

go to /page1/?query1=1 pushState

go to /a/b/?query1=1 replaceState

Context

An unintended replaceState occurred on the product page of EC site.

I want to return to the page in the order that it should be browser back

In particular

https://github.com/zeit/next.js/blob/canary/lib/router/router.js#L161

if (!this.urlIsNew(pathname, query))

Is it possible to add an option to switch whether to use pushState?

My Environment

Tech
Version

next
4.1.0

node
8.9.4

OS
mac high sierra

browser
all

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

👋 Hey everyone, I've been using next with TypeScript (was 6.0 canary, now with 6.0.1 canary) and HMR has been causing quite a lot of issues. I created an example repo to showcase it: nextjs-typescript-hrm-bug-example

Basically the default setup for HRM in nextjs means that making a change in a *.tsx file would cause an infinite loop with these errors

Which you need to kill the server to stop.

In making the example repo, I came up with the solution in my next.config.js:

if (dev && !isServer) {
const HMR = config.module.rules.find(r => r.loader === "hot-self-accept-loader")
if (HMR) {
HMR.test = /\.(ts|tsx|js|jsx)$/
HMR.options.extensions = /\.(ts|tsx|js|jsx)$/
}
}

Which modifies the HMR to support TS.

Expected Behavior

This should probably be documented somewhere 👍 (which in part this issue is meant to do for others with the same problem)

Perhaps the with-typescript example could be updated to babel's TypeScript instead, and this can be added to the config file?

Steps to Reproduce (for bugs)

git clone https://github.com/orta/nextjs-typescript-hrm-bug-example
cd nextjs-typescript-hrm-bug-example
yarn
yarn dev

Then change index.tsx

Context

n/a
Issue 1:
Dropdown is now collapsed by default inside responsive navbar, and required click to open. But on mobile devices, after the dropdown has been clicked open, it doesn't maintain "open" when user starts scrolling. It will automatically collapse making it not usable on mobile devices.

Try open below jsfiddle result on iPhone, open the "dropdown" within menu, and starts scrolling the page. Dropdown that was opened with now close.

Link: http://jsfiddle.net/y9FuQ/4/embedded/result/

In real life situation, when dropdown opens, it will most likely expand out of the screen. With it automatically collapse, it becomes not usable as it always collapse when scroll.

Issue 2:
I have simple dropdown buttons we built with 2.04

links are A tags, proper quotes, href='#'

Used to work fine.

Upgraded today to 2.1 and the links in any dropdown button don't work. The dropdown menu opens, but clicking on a link closes the menu without any action. tested on Android 2.3 and iOS 5

Rolledback to 2.04 and everything works again. Anyone else has this issue?
Issue 1:
Matplotlib draws markers centered around individual pixels of the picture, which means that actual marker coordinates are approximated. This is a considerable problem when smaller resolution plots are required (e.g. creating videos). In particular, markers with slightly different coordinates are displayed on the same position.

For MWE below, all six points have different ordinate values, yet it seems as if points 2,3 and points 4,5,6 have the same value.

MWE:

import matplotlib
from matplotlib import pyplot as plt

coor = [[0.5,0.525,0.55,0.575,0.6,0.625],[0.5,0.501,0.502,0.503,0.504,0.505]]

fig = plt.figure(figsize=(3.5,3.5))
plts=fig.add_subplot(1,1,1)
fig.subplots_adjust(left=0.01, right=0.99, bottom=0.01, top=0.99, hspace=0, wspace=0)

plts.set_xlim([0,1])
plts.set_ylim([0,1])
plts.get_xaxis().set_visible(False)
plts.get_yaxis().set_visible(False)

grph = plts.scatter(coor[0],coor[1],facecolor='k',marker='o',lw=0,s=25)
fig.savefig('test.png', bbox_inches='tight', dpi=100)

According to my visual experience, about two intermediate steps should be included so that the problem is no longer perceived.

The problem can be worked around by creating larger resolution plots and then downscaling them, which is sometimes a tedious process with bad side effects.

This problem was also reported on Stackoverflow:

http://stackoverflow.com/questions/43589568/increase-point-drawing-precision/

Best regards

Issue 2:
mpl 1.5.3/2.0b4/master, no matplotlibrc

_xs = np.linspace(0, 30, 201); plt.plot(_xs, scipy.stats.lognorm.pdf(_xs / 14, .472) / 14, ".")

Note the slight inaccuracy in positioning of the markers at the positioning of the markers at the positions marked with the red circles, resulting in a "step-like" behavior (you may need to open the image in a larger viewer to notice it).

The data itself does not present this behavior, as can be checked just by zooming in these regions.