WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
There are several issues currently with the mailing list on librelist:

The website (http://librelist.com/) is currently down. This might be transient, or this might be because the service has been slowly decaying over the last months.

The synchro to http://flask.pocoo.org/mailinglist/archive/ is broken since 2012/10/29.

I've been unsubscribed a few months ago due to transient a problem with my DNS. I have since tried many times to subscribe again with the same address, with no success. This may be a very specific problem, or this may be a manifestation of more general issues with the mailing list management system.

I have also tried registering with gmail adresses created just for the purpose of reading the Flask mailing list. I've had mixed successes, and I've also noticed that some of the emails I could see on the librelist.com archives were not delivered to my account(s).

AFAICT, traffic to the mailing list has been going down over approximately the last 2-3 months. This might be because interest in Flask is slowly fading away (if true, bad news for us Flask users), or this might be because of some of the technical issues I've mentioned above (or others), in which case proactive actions should be taken to keep users engaged.

For these reasons, I'm wondering if moving to another mailing list management platform would not be appropriate.

S.

Issue 2:
Typing issue between mypy 0.960 (and all prior versions I tested) and Flask 2.1.2. Not sure whether the issue is in mypy or Flask, but I guess it has something to do with the later.

# file test.py
from flask import Flask, Response
app = Flask("hello")

def nope(res: Response) -> Response:
return res
app.after_request(nope)

Then run:

mypy test.py

Results in:

test.py:8: error: Argument 1 to "after_request" of "Scaffold"
has incompatible type "Callable[[Arg(Response, 'res')], Response]";
expected "Callable[[Response], Response]"
Found 1 error in 1 file (checked 1 source file)

However, the same tests is fine with Flask 2.0.0 (for instance).

Python version: 3.8.10

Flask version: 2.1.2
Issue 1:
I just upgraded to next@6.0.0, I use a custom server, when I try to run dev, I get an error.

npm run dev

> frontend-next@1.0.0 dev /Users/foo/gitlab/next-project/backend
> babel-node ./src/server.js

/Users/foo/gitlab/next-project/backend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:328
throw e;
^

Error: Plugin 0 specified in "/Users/foo/gitlab/next-project/backend/node_modules/next/babel.js" provided an invalid property of "default" (While processing preset: "/Users/foo/gitlab/next-project/backend/node_modules/next/babel.js")
at Plugin.init (/Users/foo/gitlab/next-project/backend/node_modules/babel-core/lib/transformation/plugin.js:131:13)
at Function.normalisePlugin (/Users/foo/gitlab/next-project/backend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:152:12)
at /Users/foo/gitlab/next-project/backend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30
at Array.map (<anonymous>)
at Function.normalisePlugins (/Users/foo/gitlab/next-project/backend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
at OptionManager.mergeOptions (/Users/foo/gitlab/next-project/backend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:234:36)
at /Users/foo/gitlab/next-project/backend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:265:14
at /Users/foo/gitlab/next-project/backend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:323:22
at Array.map (<anonymous>)
at OptionManager.resolvePresets (/Users/foo/gitlab/next-project/backend/node_modules/babel-core/lib/transformation/file/options/option-manager.js:275:20)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! frontend-next@1.0.0 dev: `babel-node ./src/server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the frontend-next@1.0.0 dev 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! /Users/foo/.npm/_logs/2018-04-30T08_41_09_819Z-debug.log

UPDATE all this passed after upgrading all babel packages to v7

Now this is the new error.... See below for complete error message

ERROR Failed to compile with 1 errors 10:32:07

error in ./pages/_document.js

Module build failed: Error: [BABEL] /Users/foo/gitlab/zyombo/backend/pages/_document.js: .value is not a valid Plugin property

Issue 2:
Can Next.js emit split chunks for server side code? Does this provide any meaningful boost to the build speed?

We need to measure and test this theory.
Issue 1:
I was thinking about recommending Atom to a friend, and I went to the https://atom.io/ to see if there were Windows builds. The site saw I was on Linux, showed me the .deb and .rpm links, and a link for "Other platforms". That page contained this text:

Prebuilt versions of Atom are available for OS X 10.8 or later, Windows 7 & 8, RedHat Linux, and Ubuntu Linux.

but doesn't link to them or really inspire confidence that they do exist somewhere. It seems like I'd be out of luck if I wanted to save one of their installers to a flash drive to install on another computer offline.

Issue 2:
Atom version: 0.189.0

Operating system: Linux Mint 17 Cinnamon 64-bit

Installed from the .deb package.

After using the editor for a while (~10 minutes) the moment I press the middle mouse button (to paste some text into editor) the whole editor crashes. The issue does not appear if I just open a new window and start pasting content, only after some changes have been done to file. I ran the editor with '-f' option and looked into developer tools but no error of any kind appears in logs.
Issue 1:
Bug summary

This possible bug seems to be related to some incompatibility between the “extend” argument in “plt.figure.colorbar” and “.ax.invert_yaxis()” functions. More specifically, if I just extend the max of colorbar (second figure) or just invert the y-axis of the colorbar, everything work fine. However, if I do this two at the same time, the colorbar would be inverted while the extended arrow is not(figure one).

Code for reproduction

# Generate X/Y point mesh grid
x = np.linspace(-4.5, 1.5, 400)
y = np.linspace(-8, -2, 400)
X, Y = np.meshgrid(x, y)
potential, rate_determining_step = calculate_limiting_potential_from_linear_relations(X, Y, free_energy_dict)[0], calculate_limiting_potential_from_linear_relations(X, Y, free_energy_dict)[1] # calculate limiting potential for each point on the mesh grid

# Create backup ground volcano plot
fig = plt.figure(figsize=[8, 6])
background = fig.add_subplot(111) # add sub plot

# Add contour plot
contour = background.contourf(X, Y, potential, levels=512, cmap="rainbow") # create filled contour (reverse rainbow)

# Create colorbar
cbar = fig.colorbar(contour, shrink=0.95, aspect=15, ticks=[1, 2, 3, 4]) # create colorbar (shrink/aspect for the size of the bar)
cbar.set_label("Limiting Potential (eV)", fontsize=16) # add label to the colorbar
cbar.ax.tick_params(labelsize=12) # set tick label size
cbar.ax.invert_yaxis() # put the colorbar upside down

Actual outcome

Expected outcome

The arrow should inverse with the colorbar itself.

Additional information

No response

Operating system

Windows11

Matplotlib Version

Matplotlib 3.5.1

Matplotlib Backend

No response

Python version

Python 3.10

Jupyter version

No response

Installation

pip

Issue 2:
Bug summary

The "over value" and the "under value" of colormap are not correctly shown when using ax.invert_yaxis (invert_xaxis if the colorbar is horizontal) function.

Code for reproduction

import numpy as np
import matplotlib.pyplot as plt
im=plt.imshow(np.arange(10000).reshape(100,100),vmax=9000,vmin=1000)
cb=plt.colorbar(im,extend='both')
cb.ax.invert_yaxis()

Actual outcome

Expected outcome

The "over value" and the "under value" could be shown in the right location by the way. The "under value" is expected to be at the top, if the y axis is reverted.

If this is not a bug, would it be a feature?

Additional information

No response

Operating system

CentOs

Matplotlib Version

3.5.0

Matplotlib Backend

No response

Python version

3.9.7

Jupyter version

No response

Installation

No response
Issue 1:
Summary of the new feature/enhancement

I would like to be able to bind PowerToys Run to windows key + f.

Description of the new feature/enhancement

I would like this because ctrl F is most other ' normal' searches. The windows system wide equivalent should be able to be bound to windows key + f in my opinion.

What should be changed

Allow the windows key to be mapped as a PowerToys Run command starting button e.g. windows key + f, to mimmic ctrl + f.

Issue 2:
Summary of the new feature/enhancement

When editing a FanzyZones layout, it would be handy to also see the pixel dimensions of each zone (perhaps just below the zone number).

Proposed technical implementation details (optional)
Issue 1:
@crutkas (PS I miss you) :-)

Environment

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

Steps to reproduce

Under FancyZones settings, make sure "Override Winows Snap Hotkeys is NOT enabled

Hold Win key + Left Arrow to snap window to the left

Result = Window Snaps to the left

Go back under FancyZones settings and enable "Override Windows Snap Hotkeys"

Hold Win key + Left Arrow to snap window to the left

Results = Windows Snaps to the right

Expected behavior

I expect the window to snap to the direction pressed

Actual behavior

The window snaps the opposite direction

Screenshots

Issue 2:
📝 Provide a description of the new feature

What is the expected behavior of the proposed feature? What is the scenario this would be used?

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Issue 1:
Current Behavior:

When a dependency is specified as dev dependency and as optional peer dependency, it is not installed.

Expected Behavior:

I expect all dev dependencies to be installed.

Steps To Reproduce:

luigi@ubuntu:~/ws$ node -v
v15.0.1
luigi@ubuntu:~/ws$ npm -v
7.0.3
luigi@ubuntu:~$ git clone https://github.com/websockets/ws.git
Cloning into 'ws'...
remote: Enumerating objects: 14410, done.
remote: Total 14410 (delta 0), reused 0 (delta 0), pack-reused 14410
Receiving objects: 100% (14410/14410), 10.68 MiB | 969.00 KiB/s, done.
Resolving deltas: 100% (11804/11804), done.
luigi@ubuntu:~$ cd ws
luigi@ubuntu:~/ws$ npm i
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

added 352 packages, and audited 352 packages in 25s

33 packages are looking for funding
run `npm fund` for details

found 0 vulnerabilities
luigi@ubuntu:~/ws$ npm ls utf-8-validate
ws@7.3.1 /home/luigi/ws
└── (empty)

Environment:

OS: Ubuntu 20.04

Node: 15.0.1

npm: 7.0.3

Issue 2:
Current Behavior:

When a dependency is specified as a devDependency and as a peerDependency, it is not installed. I tested it with npm@7.0.2, everything worked well with npm < 7.

Expected Behavior:

I expect that all dev dependencies should be installed.

Steps To Reproduce:

I created a very small repository to reproduce the issue, so you can just checkout it and install dependencies:

git clone git@github.com:mjeanroy/npm-7-bug-peer-dev.git
cd npm-7-bug-peer-dev
npm install

Environment:

OS: MacOS 10.15.7

Node: 15.0.0

npm: 7.0.2
Issue 1:
Shouldn't there be a white-space between inline DOM elements separated by a line break [1]?

I think this example describes the situation pretty well: http://jsfiddle.net/bstst/kb3gN/2847/

Right now the workarounds are pretty ugly -- either CSS (don't get me started!) or manual white-space inside the inline elements (as in <span>foobar </span>), both of which are quite non-semantic.

Hope it's not a duplicate of an earlier issue -- I did my research!

Cheers!

M.

[1] http://www.w3.org/TR/html401/appendix/notes.html#notes-line-breaks

Issue 2:
Website or app

google.com

Repro steps

This started after last update 4.20.0

How often does this bug happen?

Every time

DevTools package (automated)

No response

DevTools version (automated)

No response

Error message (automated)

No response

Error call stack (automated)

No response

Error component stack (automated)

No response

GitHub query string (automated)

No response
Issue 1:
📝 Provide a description of the new feature

I want a feature that helps me to resize my window to specific size given by user input ( 1024x724 or 1280x720).

What is the expected behavior of the proposed feature? What is the scenario this would be used?

This feature will help me to resize my window to whatever size I want so that I can keep my window to my video resolution.

For example, some times I use a 3440x1440 monitor. when I screen record I want to record the video in 1280x720 resolution. So I wan to resize my application window to exactly 1280x720 so that it fits perfectly in my video. currently I'm resizing my window manually by just adjusting it and it's taking very long time. If you can give me this feature then I can just drag and drop my window in that tile and it will automatically get resized to the given size.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Issue 2:
Summary of the new feature/enhancement

Sizing of custom zones in editor by dragging mouse is a little bit coarse (hit and miss) in terms of getting close to edges of screen symmetrically and allowing window edges of multiple zones to line up neatly. Some possible solutions are suggested for consideration.

Proposed technical implementation details (optional)

Perhaps have an option for the editor to snap to a grid of user specified n pixels.

Perhaps have optional ability to input window dimension and position directly in both absolute terms (n x n pixels) and in terms of percentage of screen width and height.
Issue 1:
Bug report

Bug summary

After setting scale to 'log' the default limits can cut off datapoints depending on the order of plotting.

Note: calling set_xscale/set_yscale before calling scatter does not reproduce this bug.

Code for reproduction

import numpy as np
import matplotlib.pyplot as plt

# smallest span
x1 = np.array([1, 10])
y1 = np.array([10, 1])

# largest span
x2 = np.array([0.1, 100])
y2 = np.array([100, 0.1])

fig, ((ax1, ax2), (ax3, ax4)) = plt.subplots(2,2, figsize=(8,8))

ax1.scatter(x1, y1)
ax1.scatter(x2, y2)
ax1.set_title('linear; smallest span first', color='g')

ax2.scatter(x1, y1)
ax2.scatter(x2, y2)
ax2.set_xscale('log')
ax2.set_yscale('log')
ax2.set_title('log; smallest span first', color='r')

ax3.scatter(x2, y2)
ax3.scatter(x1, y1)
ax3.set_title('linear; largest span first', color='g')

ax4.scatter(x2, y2)
ax4.scatter(x1, y1)
ax4.set_xscale('log')
ax4.set_yscale('log')
ax4.set_title('log; largest span first', color='g')

Outcome

Matplotlib version

Matplotlib version: 2.2.2

Matplotlib backend: MacOSX

Python version: 2.7.14 and 3.6.4

Issue 2:
As mentioned in this SE question a scatter plot is not autoscaling to include all of the data if plt.yscale('log') is used after plt.scatter(). This happens for the y-axis but not the x-axis in the example, and does not happen for plt.plot().

In an earlier answer by a developer, ax.set_yscale('log') is shown following ax.scatter(), so I am wondering if this may be a bug.

Using matplotlib version 1.5.1 and python 2.7.11

import matplotlib.pyplot as plt

X = [0.997, 2.643, 0.354, 0.075, 1.0, 0.03, 2.39, 0.364, 0.221, 0.437]
Y = [15.487507, 2.320735, 0.085742, 0.303032, 1.0, 0.025435, 4.436435,
0.025435, 0.000503, 2.320735]

plt.figure()

plt.subplot(2,2,1)
plt.scatter(X, Y)
plt.xscale('log')
plt.yscale('log')
plt.title('scatter - scale last')

plt.subplot(2,2,2)
plt.plot(X, Y)
plt.xscale('log')
plt.yscale('log')
plt.title('plot - scale last')

plt.subplot(2,2,3)
plt.xscale('log')
plt.yscale('log')
plt.scatter(X, Y)
plt.title('scatter - scale first')

plt.subplot(2,2,4)
plt.xscale('log')
plt.yscale('log')
plt.plot(X, Y)
plt.title('plot - scale first')

plt.show()
Issue 1:
This is a hypothetical but I couldn't find a good answer to it and thought might ask it here. Let's say my project requires foo@0.0.2 and bar@0.0.1. In the meantime, bar requires foo@0.0.1. Which version of foo would be loaded by webpack? Would both versions be loaded? What can I do to prevent both versions from being loaded, if that is the case?

Issue 2:
Bug report

What is the current behavior?

Our webpack build produces 15 chunks (3 initial manifest, main, vendor + the rest are dynamic chunks via import() or require.ensure()).

I wanted to experiment with split chunks (https://webpack.js.org/plugins/split-chunks-plugin/#splitchunks-chunks) -- as explained splitChunks.chunk can be a method returning a Boolean to decide whether a given chunk should be optimized further (additional code splitting) or not.

I put in place the following config:

optimization: {
splitChunks: {
chunks() {
console.dir(chunk.name)
return false
},

What is the expected behavior?

I would expect to see all the 15 chunks names, one time each -- each callback would decide whether to optimize a given chunk or not

What is the actual behavior?

I don't see certain chunks getting callback at all, and I see some other chunks listed twice.

There's no clear pattern about which kinds of chunks are missing and which are duplicated.

I.e. expected output:

chunk1
chunk2
chunk3
...
chunk15

Actual:

chunk1
chunk2
chunk3
chunk4
chunk3
chunk4
chunk8
chunk9
chunk10
chunk9
chunk10

Other relevant information:

webpack version: 4.26.0

Node.js version: 8.11.3

Operating System: Win 10

Does this look like a bug? Did someone encounter this too? Is it work digging further to find a minimum repro?

Maybe I misunderstand how this is supposed to work? (the docs are scarce so I'm not fully sure)
Issue 1:
We started getting this deprecation warning but I don't know what to do with it. Is there somewhere in your documentation that would explain this more? Thanks! Example log: https://github.com/astropy/astropy/runs/6838665326?check_suite_focus=true

matplotlib._api.deprecation.MatplotlibDeprecationWarning: The checkdep_usetex function
was deprecated in Matplotlib 3.6 and will be removed two minor releases later.
Use Vendor the code instead.

We use it like this:

TEX_UNAVAILABLE = not matplotlib.checkdep_usetex(True)

Hard to tell from the traceback where this is coming from inside matplotlib because the warning went through a generic matplotlib/_api/deprecation.py.

Issue 2:
Original report at SourceForge, opened Tue Nov 9 15:40:14 2010

The "pip" installation tool uses this URL to find the correct version of the matplotlib package:

http://pypi.python.org/simple/matplotlib/

matplotlib 1.0.0 appears on that page, but pip selects the very old 0.91.1 release for installation instead.

I'm not expert enough with either matplotlib or pip to determine whether this is a pip bug or a configuration

issue in the matplotlib entry on the Python Package Index.

Python 2.4.3 (#1, Sep 8 2010, 11:37:47)

[GCC 4.1.2 20080704 (Red Hat 4.1.2-48)] on linux2
Issue 1:
Bug summary

The image added in the text bbox is not saved with savefig if setting a bbox.

savefig without option do save the image

Code for reproduction

def GrabTextWithImage():

fig = plt.figure()
plt.subplot(111)

#Display Text
txt = plt.gcf().text(0.10, 0.5, " ................\n ................\n ................"
,bbox={'edgecolor':'black','alpha' : 0.2,'facecolor':'white', 'pad':10, 'linewidth' : 2},
verticalalignment='center', horizontalalignment='left', color='black', fontsize=12,zorder = 3)

#Add an image
an_array = numpy.random.random((20,20)) * 255
fig.figimage(an_array,70,240, zorder = 1)

#Grab around text and return image
ax = plt.gca()
r = fig.canvas.get_renderer()
bb = txt.get_window_extent(r)

transf = ax.transData.inverted()
bb_datacoords = bb.transformed(transf)
bbox = bb_datacoords.transformed(ax.transData).transformed(fig.dpi_scale_trans.inverted())

plt.axis('off')

fp = tempfile.TemporaryFile()
plt.savefig(fp, bbox_inches = bbox) #BUG : image is not displayed
# plt.savefig(fp) #Image is displayed

im = Image.open(fp)
return im

if __name__ == "__main__":
import numpy
print (mpl.__version__)

im = GrabTextWithImage()
plt.show()
im.show()

Actual outcome

Expected outcome

Additional information

No response

Operating system

Win, Python 3.8, Matplotlib 3.6.2

Matplotlib Version

3.6.2

Matplotlib Backend

QtAgg

Python version

3.8.2

Jupyter version

No response

Installation

pip

Issue 2:
Bug summary

figimage() is producing inconsistent results.

It appears a transform is sometimes applied to the image and sometimes not.

Code for reproduction

from matplotlib import pyplot
plt = pyplot
import numpy as np

fig = pyplot.figure()
ax = fig.subplots()

fig_bbox = fig.bbox
width, height = fig_bbox.width, fig_bbox.height

img = np.zeros((int(height), int(width), 3))
img += (127, 0, 0)

fig.figimage(img, 0, 0, zorder=-1)

# show the figure, image is not scaled as I would expect
plt.show()

# save as a png, image is scaled as I would expect
fig.savefig('foo.png')

# save as an svg, image matches the one in the FigureCanvas window.
fig.savefig('foo.svg')

# NB reversing the order of the two savefig calls produces images
# matching the FigureCanvas version.

Actual outcome

Expected outcome

I would expect all images to look like the png image, i.e. scaled to the figure size.

Additional information

No response

Operating system

Ubuntu 21.10

Matplotlib Version

3.5.0.dev2201+ge9bd017b2d.d20220707

Matplotlib Backend

'QtAgg'

Python version

Python 3.9.7

Jupyter version

No response

Installation

git checkout
Issue 1:
I have a javascript node project with some TypeScript definition files inside it. My jsconfig.json is as follows:

{

"compilerOptions": {

"target": "ES6",

"module": "commonjs"

}

}

If I rename a javascript source file to temp_hello.js or even temple.js (imagine if temples were in my business domain!) then the intellisense stops working for the file (it does not pick up anything in the typescript definition files) and it also forgets my jsconfig.json settings. That means I can't use ES6 syntax anymore!

Issue 2:
Hi.

Thanks for your product, I really enjoy using it. However I have one problem:

When using ES6 features, like the arrow functions, I get the message "This can only be used with ES6. Make sure to have a jsconfig.json-file which sets the target to ES6".

However I have a jsconfig.json-file in my root (the folder opened in Visual Studio Code), which contains:

{
"compilerOptions": {
"target": "ES6",
"module": "commonjs"
}
}

The weird part is that I get it for some files, and not for others. Even if the files are in the same directory. Right now I have three files in the subdirectory /app/bpm names bpm.js, bpmController.js and enterClick.js. All three are written with ES6-functionality, but I only get the warning and red underlined text for bpm.js.

UPDATE:

I just restarted VS Code, and the red underline disappeared from bpm.js too. It was a new file I had created after the two others, however the red underline only went away after a restart.