WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
So I have structure of app like this

index.ts
package.json

package.json

worked

{
"scripts": {
"test": "deno run index.ts"
}
}

not working

{
"scripts": {
"test": "deno run index.ts"
}
}

I am not sure that whether or not deno will support execute script without extension name in the future.

Issue 2:
Hi guys! First of all let me say big thanks for all the job you already done! Deno looks extremely promising even before release.

Right now I am trying to get a bit more familiar with it and just spotted some kind of issue (I think this is issue but may be I am wrong) when importing my own typescript module.

Let's say we have this code

import { Timer } from "./serivce";
const id = new Timer().start();

It looks OK, but Deno will refuse to run it because it expects to see extension of the file:

Uncaught NotFound: Cannot resolve module "./serivce"

If I will change statement to use extension, as Deno expect, two bad things happens.

VsCode starts showing next error:

No IntelliSense provided because Timer starts to be "any" - typed

The first issue can be partially fixed using //@ts-ignore. But then, I have to add this every time, and that's a bit annoying. And the second issue seems not fixable for me (again, may be just not found the solution)

So my question: Is it possible to make Deno and Ts more friendly and get rid of this //@ts-ignore?
Issue 1:
actually there are 4 tabs, but only 3 tabs are displayed in the title bar!!!

Issue 2:
This bug-tracker is monitored by Windows Console development team and other technical types. We like detail!

Please use this form and describe your issue, concisely but precisely, with as much detail as possible

Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.18898.1000]

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

Video demonstration of both issues below

A newly created tab doesn't scroll the tab bar to the end - could possibly be a config variable

When using tabs in the title bar and creating a new partially hidden tab, the tab gets cut off.

What's wrong / what should be happening instead:

The tab should not be cut off.
Issue 1:
Add __inverse__ to Index.

Change duplicated to return np.array (PR #9112)

Related to #7979

Because Index is no more the subclass of np.array, Index.duplicated returns Index with dtype=object. And Index don't accepts logical not.

idx = pd.Index([1, 2, 1, 3])

idx.duplicated()
# Index([False, False, True, False], dtype='object')

~idx.duplicated()
# TypeError: bad operand type for unary ~: 'Index'

As a result, it is impossible to drop data which have duplicated index using expression like df[~df.index.duplicated()]. This expression was worked at the timing of #7979.

Does Index.duplicated should return np.array with dtype=bool? Or Index should accept logical not?

Issue 2:
after #6380, ability to pretty easily move ops over to the mix-in

date/time (added in #6380)

more periods ops? #5202

additional field accessor (is_beg_year), #4823

validate argmin/max, (PR #7904)

StringMethods, e.g. str for Index (not for sub-classes though), #9068

(this turns out to be quite tricky, as sometimes construction depends on the existence of a tz attribute)

freq,frestr,inferred_freq

is_monotonic #13336

pd.infer_freq(), related #6407,#6408

is_unique,lexsort_depth,nlevels

nunique(),unique(),value_counts(), #6734

factorize() #7090

get_loc/find #4616

__invert__ #8875

These are related in that they are generic.py functions as they have to compute something then set the axis with the result.

normalize #5502

tz_convert/tz_localize (though this requires a bit of wrapping as they have an axis parm,

but should be possible), see also here: #7915 (currently implemented only on DatetimeIndex, PeriodIndex has these as not implemented (and delegating from NDFrame is in core/generic)

duplicated/drop_duplicates #4060, (PR #7979)

has_duplicates #9077
Issue 1:
We are using piprot in our security build. recently our build is getting failed because of the following risk given by piprot.

python-piprot medium urllib3 Module is one or more minor versions out of date Upgrade to v1.25.2 (Current: v1.24.2)

could you please let us know whether there is version upgrade possible in any time soon

Thanks in advance

Issue 2:
Support for urllib3 v1.25 (released today/yesterday). The usual yada-yada "my CI is broken".

Multiple packages that we depend on (eg google.cloud.storage, azure.storage) have strict version-check on requests using pkg_resources.require('requests >= 2.18.0'). Any unmet dependencies in the chain below and including requests will cause the check to fail and raise an exception. urllib3<1.25 is currently one such dependency.

Expected Result

No exception raised on import

Actual Result

pkg_resources.ContextualVersionConflict: (urllib3 1.25 (/usr/local/lib/python3.6/dist-packages), Requirement.parse('urllib3<1.25,>=1.21.1'), {'requests'})

The above exception was the direct cause of the following exception:
ImportError: ``requests >= 2.18.0`` is required by the ``google.resumable_media.requests`` subpackage.
It can be installed via
pip install google-resumable-media[requests].

Reproduction Steps

pip3 install sentry-sdk google-cloud-storage

>>> from google.cloud import storage

System Information

/home/laurie/env-tmp/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25) or chardet (3.0.4) doesn't match a supported version!
RequestsDependencyWarning)
{
"chardet": {
"version": "3.0.4"
},
"cryptography": {
"version": ""
},
"idna": {
"version": "2.8"
},
"implementation": {
"name": "CPython",
"version": "3.6.7"
},
"platform": {
"release": "4.18.0-17-generic",
"system": "Linux"
},
"pyOpenSSL": {
"openssl_version": "",
"version": null
},
"requests": {
"version": "2.21.0"
},
"system_ssl": {
"version": "1010100f"
},
"urllib3": {
"version": "1.25"
},
"using_pyopenssl": false
}
Issue 1:
Hi,

I have been running into a recurring issue with the test code below (I am just quoting the most minimal version but the issue manifests itself every time pyplot is invoked). I have been running matplotlib 3.4.3 on Visual Studio Code (which freezes and needs manual restart) and jupyter-lab ("The kernel appears to have died. It will restart automatically").

import matplotlib.pyplot as plt

plt.plot([1,2,3], [1,2,3])

plt.show()

On jupyter-lab, the above code also generates a deluge of runtime warnings (which I am happy to send them in a separate file).

I have tried removing and reinstalling matplotlib (multiple times) but the issue reproduces itself.

I am really not sure how to approach this. The code was working fine until a few weeks ago, at which point I am not sure what changed. I am running this on a Windows machine (arm64 architecture).

Thanks for any help, advice, or insight!

Issue 2:
If you assign any of the text fields in the figure options dialog to a "color-like" string, it changes into a color field the next time you open the dialog. This happens even in some not-so-obvious cases, like the letter 'y' (which you'd think you'd be able to use for a y axis label). This would be a little difficult to fix since the form dialog code is pretty complex, but a quick solution would be to only consider #ffffff style strings as colors, and add a helper function to convert the color properties to this format. a better solution would be to either wrap the color properties in an object, or add some kind of disambiguation parameter to the form parser (as an optional third entry in each tuple, i.e. "('Color', line.get_color(), 'color')").
Issue 1:
Bug report

Describe the bug

Next.js fails to compile

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

run npm run dev on http://github.com/voluntarily/vly2

watch the logs

Logs return

[ error ] ./node_modules/next/dist/client/next-dev.js 36:6
Module parse failed: Unexpected token (36:6)
You may need an appropriate loader to handle this file type.
|
|
> import('./noop'); // Support EventSource on Internet Explorer 11
|
| if (!window.EventSource) {
mongodb connected at: mongodb://localhost/vly2
Voluntari.ly running on http://localhost:3122/ Be Awesome
(node:81825) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'issuer' of null
at findEntryModule (/Users/walt/dev/vly2/node_modules/next/dist/server/hot-reloader.js:60:16)
at erroredPages (/Users/walt/dev/vly2/node_modules/next/dist/server/hot-reloader.js:68:29)
at HotReloader.getCompilationErrors (/Users/walt/dev/vly2/node_modules/next/dist/server/hot-reloader.js:308:33)
at processTicksAndRejections (internal/process/next_tick.js:81:5)
(node:81825) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:81825) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:81825) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'issuer' of null
at findEntryModule (/Users/walt/dev/vly2/node_modules/next/dist/server/hot-reloader.js:60:16)
at erroredPages (/Users/walt/dev/vly2/node_modules/next/dist/server/hot-reloader.js:68:29)
at HotReloader.getCompilationErrors (/Users/walt/dev/vly2/node_modules/next/dist/server/hot-reloader.js:308:33)
at processTicksAndRejections (internal/process/next_tick.js:81:5)
(node:81825) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

Expected behavior

I expect the site to render

Issue 2:
Bug report

Just upgraded to 8.0.0 and I'm really excited! I've run into an issue though that is preventing my project from compiling

Describe the bug

So when I run dev I am getting the following issue

You may need an appropriate loader to handle this file type.
|
|
> import('./noop');
| var _window = window,
| assetPrefix = _window.__NEXT_DATA__.assetPrefix;

It seems to be coming from webpack 4.29.0 (see here).

It looks like the issue was fixed with this which declared acorn": "^6.0.5 as a dependency but the change doesn't seem to be present on master

Maybe I upgraded too soon?
Issue 1:
Bug summary

2D arrays with more than about 8.000.000 columns are truncated on the right side.

Code for reproduction

import numpy as np
from matplotlib import pyplot

for length in range(6000000,10000000,500000):
s = .5 * np.sin(np.linspace(0,6*np.pi,length))
pyplot.plot(s)
pyplot.imshow(s.reshape((1,len(s))),aspect='auto',cmap='seismic')
pyplot.show()

Actual outcome

Image truncated on the right if length > 8000000.

Expected outcome

Expected same outcome independent of length.

Additional information

No response

Operating system

Windows 10

Matplotlib Version

3.1.0

Matplotlib Backend

module://ipykernel.pylab.backend_inline

Python version

3.7.3

Jupyter version

No response

Installation

pip

Issue 2:
Bug report

Bug summary

Hello, I am using plt.imshow to plot a very large array (~ 1 row x 150 million columns), and have noticed that the colors are not displayed properly.

Code for reproduction

import numpy as np
import matplotlib.pyplot as plt

# Very large
array = np.zeros(150000000, dtype=np.uint8)
array[len(array) // 2:] = 1
fig, ax = plt.subplots(figsize=(10, 3))
im = ax.imshow(array.reshape(1, -1), vmin=0, vmax=1, aspect='auto')
fig.colorbar(im, ax=ax)

# 10x smaller
array = np.zeros(15000000, dtype=np.uint8)
array[len(array) // 2:] = 1
fig, ax = plt.subplots(figsize=(10, 3))
im = ax.imshow(array.reshape(1, -1), vmin=0, vmax=1, aspect='auto')
fig.colorbar(im, ax=ax)

Actual outcome

Very large

10x smaller

Expected outcome

Since we set the later half of the array to 1 (and the rest is 0), we expect the image to change color at 75 million, but we see that all pixels are colored as 0.

Matplotlib version

Operating system: Ubuntu 20.04

Matplotlib version: 3.3.2 (also tested on 3.3.3)

Matplotlib backend: module://ipykernel.pylab.backend_inline

Python version: 3.8.3 (also tested on 3.6.9)

Jupyter version (if applicable):

Other libraries:

ipython 7.18.1
ipython-genutils 0.2.0
jupyter 1.0.0
jupyter-client 6.1.7
jupyter-console 6.2.0
jupyter-core 4.6.3
jupyterlab 2.2.8
jupyterlab-pygments 0.1.1
jupyterlab-server 1.2.0

Python installed via miniconda, but matplotlib was installed via pip.
Issue 1:
Consider the following function f:

function f()
if rand(Bool)
idxs = [[1,2],[1,2,3]]
else
idxs = [[1,2],[1,2,3]]
end

return idxs
end

As well as the functionally identical variation g:

function g()
if rand(Bool)
idxs = [[1,2],[1,2,3]]
else
idxs = [[1,2],[1,2,3]]
end

[idxs[j] for j in 1:length(idxs)]
return idxs
end

Here, f will infer perfectly fine - but adding an iterator over idxs in g (which, notably, is not used for anything) will cause inference to give up, inferring Any as return value. Effectively, using the iterator poisons everything.

Defining and using variables this way is definitely an anti-pattern (and can be avoided in several ways) but sincef works just fine (and e.g., is not disallowed) it struck me as unintended that g does not.

Issue 2:
using Images: realtype

function ifi{T<:Real,K,N}(img::AbstractArray{T,N}, kern::AbstractArray{K,N}, border::AbstractString, value)
if border == "circular" && size(img) == size(kern)
out = real(ifftshift(ifft(fft(img).*fft(kern))))
elseif border != "inner"
prepad = [div(size(kern,i)-1, 2) for i = 1:N]
postpad = [div(size(kern,i), 2) for i = 1:N]
fullpad = [nextprod([2,3], size(img,i) + prepad[i] + postpad[i]) - size(img, i) - prepad[i] for i = 1:N]
A = padarray(img, prepad, fullpad, border, convert(T, value))
krn = zeros(typeof(one(T)*one(K)), size(A))
indexesK = ntuple(d->[size(krn,d)-prepad[d]+1:size(krn,d);1:size(kern,d)-prepad[d]], N)::NTuple{N,Vector{Int}}
AF = ifft(fft(A).*fft(krn))
out = Array(realtype(eltype(AF)), size(img))
end
out
end

Test:

julia> @code_warntype ifi(rand(3,3), rand(3,3), "replicate", 0)
Variables:
#self#::#ifi
img::Array{Float64,2}
kern::Array{Float64,2}
border::ASCIIString
value::Int64
prepad::Box
...

Now comment out the indexesK = ... line (the output of which is not used at all). Suddenly prepad is inferred as Array{Int, 1}.
Issue 1:
The text has turned red, but I'm still not allowed to proceed.

Issue 2:
Challenge change-the-css-of-an-element-using-jquery has an issue.

User Agent is: Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0.

Please describe how to reproduce this issue, and include links to screenshots if possible.

<script>
$(document).ready(function() {
$("#target1").css("color","red");
});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>

```
even though it worksalright,an error shows up andi can't continue
Issue 1:
System info

Playwright Version: [v1.25]

Operating System: [All, Windows]

Browser: [All,]

Other info:

Source code

for (const page of context.pages())

await page.close();

await context.tracing.stop({ path: 'trace.zip' });

await context.close();

Link to the GitHub repository with the repro

[https://github.com//issues/23045]

Test file (self-contained)

for (const page of context.pages())
await page.close();
await context.tracing.stop({ path: 'trace.zip' });
await context.close();

Steps

[Run the test]

Expected

[Describe expected behavior]

Based on previous answers.I closes all pages, all network request should be aborted, and then saves the trace:

Actual

[Describe actual behavior]

But the actual situation is not like this

I still cannot collect requests that are still pending when the page is closed in the trace

Perhaps this is a bug

Issue 2:
System info

Playwright Version: v1.32.3

Operating System: macOS 13.2

Browser: Firefox

Other info:

Source code

I provided exact source code that allows reproducing the issue locally.

const playwright = require("playwright");

(async () => {
const browser = await playwright.firefox.launch({
headless: false,
permissions: ["geolocation"],
});
const context = await browser.newContext({
ignoreHTTPSErrors: true,
});
// Open new page
const page = await context.newPage();
await page.goto(
"https://chrisdavidmills.github.io/location-finder-permissions-api/"
);

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

Steps

Execute the script

Expected

Firefox shouldn't prompt for geolocation permissions

Actual

I get the geolocation message

Geolocation should be available in Firefox. At least it is mentioned here.

Update

I found that the permissions option in the newContext does work. Shouldn't newContext inherit that option?

const browser = await playwright.firefox.launch({
headless: false,
});
const context = await browser.newContext({
permissions: ["geolocation"],
ignoreHTTPSErrors: true,
});
Issue 1:
Hi

When pool_block=True on an HTTPAdapter is used and the connection fails

this one seems not return to the pool.

To reproduce:

# python
>>> import requests
>>> a = requests.adapters.HTTPAdapter(pool_maxsize=1, pool_block=True)
>>> s = requests.Session()
>>> s.mount("http://", a)
>>> s.get("http://localhost:12345")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 477, in get
return self.request('GET', url, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 465, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 573, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/adapters.py", line 413, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', error(111, 'Connection refused'))
>>> s.get("http://localhost:12345")

# here the session objects is stuck.

Cheers,

Issue 2:
Requests with Content-Type: multipart/form-data need to also have a ; boundary=someUniqueString in that header. I think this is actually true for all multipart/* MIME types.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#multipartform-data

This is how curl works, if you pass Content-Type: multipart/form-data it'll still add a boundary because users shouldn't need to know how all the HTTP headers work, that's the library's job. We are running into this issue when trying to convert curl commands into requests code curlconverter/curlconverter#248 and it would be convenient if Requests did the same thing as curl.

I don't see why anyone would ever want to pass Content-Type: multipart/form-data without a boundary, unless they just don't know about it. If you do actually need to not have a boundary you would have to explicitly add an empty one ; boundary= to your header. But I can also see how it might surprise users that even if they pass a header manually it gets modified.

Expected Result

Requests still adds a boundary to my header if I don't, i.e. when I pass headers={'Content-Type': 'multipart/form-data'} and files=

Actual Result

Requests uses the header as-is and the request fails.

Reproduction Steps

>>> import requests
>>>
>>> files = {
... 'hello': (None, 'world'),
... }
>>> requests.post('http://example.com', files=files).request.headers['Content-Type']
'multipart/form-data; boundary=498931185311c522b8ca559425b2b965'
>>>
>>> headers = {
... 'Content-Type': 'multipart/form-data',
... }
>>>
>>> requests.post('http://example.com', headers=headers, files=files).request.headers['Content-Type']
'multipart/form-data'

Compare with curl:

$ curl -vvv example.com -H "Content-Type: multipart/form-data" -F "hello=world"
[...]
> Content-Type: multipart/form-data; boundary=------------------------ff92aa2ea98d6cc3
Issue 1:
On 2012.12.18 the AWS region us-east-1 experienced an outage affecting service of the DescribeInstances and DescribeTags APIs. This is turn brought our two independent clusters operating in the region, as the Kubelet AWS clustering mechanisms rely on the DescribeInstances API. Networking was unaffected - master and nodes could still communicate without problem.

I propose that this AWS failure should not bring down a cluster.

The relevant Kubelet log message:

Error updating node status, will retry: failed to get node address from cloud provider: no instances found for name: ip----.ec2.internal

There are several issues that relate to this functionality. I am filing this issue to ensure that Kubernetes is not needlessly vulnerable to this type of outage.

Possibly Related

#17643 use private ip instead of local hostname for AWS

#18525 We shouldn't use node names as addresses

Incident details from http://status.aws.amazon.com/

1:02 PM PST We are investigating elevated latencies and error rates for the DescribeInstances and DescribeTags APIs in the us-east-1 region. Customers may observe elevated error rates or missing tags for instances in the AWS Management Console.

1:44 PM PST We have identified the root cause of elevated latencies and error rates for the DescribeInstances and DescribeTags APIs and are currently working to resolve. Customers may observe elevated error rates or missing tags for instances in the AWS Management Console.

3:03 PM PST Between 12:30 PM and 2:44 PM PST, we experienced elevated latencies and error rates for the DescribeInstances and DescribeTags APIs. During this period, customers may have observed elevated error rates and missing tags for instances in the AWS Management Console. During this event, instances continued running normally. Tags requested during this period are now visible. This issue has been resolved and the service is operating normally.

Issue 2:
Generate a UUID when you kube-up.sh a cluster.

One use case is for associating credentials with multiple clusters.

.kubernetes_auth format could have sections for each cluster UUID. So, if you start an e2e cluster it won't clobber your creds for your dev cluster. A flag to kubectl could let you set what UUID you are talking to.

e.g.: {"UUID": "123-...", "BearerToken": "abc"}\n { "UUID": "456-...", "User": "foo", "Password":"bar"}

more generally, if you have clusters in several regions. You don't want to identify by master IP since that might change. And you don't want to rely on DNS because you don't always have a DNS mapping from cluster-name to master IPs.

when we want to name resources that are unique to a cluster using an URL that is portable across clusters.

E.g: kubernetes:123-456-789-234234-567567/api/v1beta1/ns/mynamespace/pods/mypodname

Garbage collection of old UUIDs in the .kubernetes_auth is left as an exercise to the user.