WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Receiving errors in vscode from the Deno Language Server

<--- Last few GCs --->

[77365:0x7fe610008000] 156574 ms: Scavenge (reduce) 1397.1 (1422.7) -> 1396.5 (1423.0) MB, 2.21 / 0.00 ms (average mu = 0.145, current mu = 0.011) allocation failure;
[77365:0x7fe610008000] 156796 ms: Mark-Compact (reduce) 1397.2 (1423.0) -> 1396.3 (1423.2) MB, 218.90 / 0.00 ms (average mu = 0.102, current mu = 0.058) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

#
# Fatal JavaScript out of memory: Ineffective mark-compacts near heap limit
#

After investigating it seems like importing certain packages can trigger this. I am able to cause this error and stop receiving this error merely by adding or removing this package:

import * as goog from "https://esm.sh/googleapis@118.0.0";

Issue 2:
Hi, I need to reimport script after changes (by others) at runtime, but deno doesn't want to recompile sources.

Simple test:

File test.ts

await import("./abc.ts");

await Deno.writeTextFile("./abc.ts", "console.log('After changes');");

await import("./abc.ts");

File abc.ts

console.log('Before changes');

Execute:

deno run --unstable --allow-all test.ts

Console output:

ubuntu@deno:~/workspace/deno$ deno run --unstable --allow-all test.ts
Compile file:///home/ubuntu/workspace/deno/test.ts
Before changes
ubuntu@deno:~/workspace/deno$

File abc.ts after run:

console.log('After changes');

Deno version

deno 1.0.2
v8 8.4.300
typescript 3.9.2

OS Linux
Issue 1:
Condor opened SPR-2076 and commented

It would be nice if the HTML tags would contain support for message code resolving for the title, alt, accessKey and itemLabel attributes (just like the Struts HTML taglib).

I suggest adding titleCode, altCode, accessKeyCode and itemLabelCode attributes to specify a message code instead of a value.

Affects: 2.0 RC1

Issue Links:

#7255 form:label/ should have MessageSource support ("duplicates")

Issue 2:
Erwin Vervaet opened SPR-9046 and commented

When using @ActiveProfiles to activate certain profiles in a test that uses AnnotationConfigContextLoader to load a @Configuration context definition which imports XML application context definitions using @ImportResource, the active profiles are not considered when loading the XML context definition.

See the attached files for a test reproducing the problem. This test fails with the following error:

org.springframework.beans.factory.NoSuchBeanDefinitionException: No matching bean of type [test.ContextLoadingProblem$Bar] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}

Note that if you use XML throughout (i.e. import one XML context definition from another), the problem does not arise.

Affects: 3.1 GA

Attachments:

bar-context.xml (613 bytes)

ContextLoadingProblem.java (1.31 kB)

Issue Links:

#13632 @ActiveProfiles are not cascaded down to contexts loaded via @ImportResource ("duplicates")

#13040 AnnotatedBeanDefinitionReader's constructor should inherit Environment of supplied BeanDefinitionRegistry
Issue 1:
I am trying to make a loss function with varying input sizes. I am getting the following error:

TypeError: __int__ returned non-int (type NoneType) when compiling the model

Steps to get the error:

Make architecture in Keras with None type as input: input_image = Input(shape=(None, None, 3))

Then make a custom loss function and try to access the size of the tensor

def custom_loss(y_true, y_pred):

yp_size = [int(y_pred.get_shape()[0]), int(y_pred.get_shape()[1]), int(y_pred.get_shape()[2]), int(y_pred.get_shape()[3])]

cell_x = tf.tile(tf.range(yp_size[1]), [yp_size[2]]) # And code will go on eventually returning loss

Then compile model:

model.compile(loss=custom_loss, optimizer=optimizer)

Theoretically the method should run fine at runtime but it is showing this error. Can I get any workaround for this?

P.S. I don't want to pad my tensors to a fixed size. And sorry if the issue got uploaded multiple times.

Issue 2:
I am trying to make a loss function with varying input sizes. I am getting the following error:

TypeError: __int__ returned non-int (type NoneType) when compiling the model

Steps to get the error:

Make architecture in Keras with None type as input: input_image = Input(shape=(None, None, 3))

Then make a custom loss function and try to access the size of the tensor

def custom_loss(y_true, y_pred):

yp_size = [int(y_pred.get_shape()[0]), int(y_pred.get_shape()[1]), int(y_pred.get_shape()[2]), int(y_pred.get_shape()[3])]

cell_x = tf.tile(tf.range(yp_size[1]), [yp_size[2]]) # And code will go on eventually returning loss

Then compile model:

model.compile(loss=custom_loss, optimizer=optimizer)

Theoretically the method should run fine at runtime but it is showing this error. Can I get any workaround for this?

P.S. I don't want to pad my tensors to a fixed size
Issue 1:
Upon clicking open files using the scroll wheel, instead of closing, a scroll symbol appears.

This is the expected behaviour in Chrome:

This is the resulting behaviour in VSCode:

This works in VSCode on OS X.

Issue 2:
Forgive if this is already submitted but I couldn't find a similar ticket when I searched the issues. I love the Git integration in VSCode but what do you think about add filters to the Git Sidebar? My thought is that you have toggle buttons for different Git Statues (Added, Modified, Deleted, Confict) and then an input field that allows you to filter the list. This would make large amounts of changes such as those in a merge conflict so much easier to deal with it and finding the right file.
Issue 1:
http://stackoverflow.com/questions/21773473/twitter-bootstrap-icons-and-opera-mobile

Issue 2:
When I checked my site to be compatible with my phone (Android 2.3.6), I noticed that the Glyphicons not work. Previously, when not used fonts and PNG image problems were not.

Sreenshot:

I use browser Opera Mobile v12.10. In default browser this work fine
Issue 1:
If I am not mistaken, after enabling _ttl & _timestamp, one must also then add a request for the _ttl & _timestamp fields (and _source, otherwise, it disappears) to (every) search request thereafter in order to get the values - if we want to display them.

Is there a downside to having them included with the other hit fields (_id, _index, _type, _score) automatically?

It seems to me to be the most intuitive behaviour.

At least thats what I (and my pair) were expecting - and we had to go on a bit of a tour of stackexchange to find out why it wasnt behaving like that what hoops we had to jump through

Issue 2:
When you search or GET to retrieve documents you don't get back the value for _parent field (or _routing for that matter) which is part of the essential metadata. Meaning the document cannot be retrieved or updated without the value. This is breaking some functionality, example use cases:

reindex (results of scan being fed into bulk) cannot work

persistence layers on top of elasticsearch cannot update a document they retrieved from ES without additional info/queries

you cannot GET a document you searched for (for example to retrieve fields you excluded)

I believe it would be worth the cost to retrieve the value of _parent field when retrieving a child document.
Issue 1:
I'd like to select second 'text="John"' in the list.

Issue 2:
waitForSelectors

There are quite a few requests for more advanced logic to retrieve elements matching selectors. For example:

wait for at least one element matching selector and get all matching elements;

wait for at least one element matching selector to be visible and get it.

Proposal:

page.waitForSelectors(selector, countOrPredicate, { state?: 'attached' | 'visible' | 'hidden', filter? }): Promise<ElementHandle[]>

This method will query all elements matching selector, filter them by them by visibility state, then filter by the filter predicate, and then resolve with remaining elements if there are not less than countOrPredicate of them when it's a number or the predicate returns true.

Examples:

page.waitForSelectors('button', 2) - at least two buttons.

page.waitForSelectors('button', buttons => buttons.length >= myButtonsCount) - at least myButtonsCount buttons;

page.waitForSelectors('button', 1, { state: 'visible' }) - at least one visible button;

page.waitForSelectors('button', 3, { state: 'visible', filter: b => !b.disabled }) - at least three visible and enabled buttons.

selectors.visible

There are requests to match not the first element, but the first visible one. This is more flaky and the preferred way is to use a stable selector the uniquely identifies the visible target element. That said, maybe it makes sense to introduce a wrapper that takes a regular selector:

selectors.visible('css=div')

Questions:

How does this interact with waitForSelector() state option that could be visible | hidden | attached | detached?

selectors.index

This could simplify selecting a particular item from the list.

Examples:

page.click(selectors.index('.my-list-item', 3)) - click at the third list item;

page.waitForSelector(selectors.index('button', 2)) - wait until there are at least two buttons.
Issue 1:
See here:

http://plnkr.co/edit/sKkTPTraGIP2BcLWzEQU?p=preview

It is a situation that occurs after minification with mangling, but I tried to reproduce without minification by using the same class name for both components (since I don't know how to easily provide a minified example in Plunkr). Mangling will typically convert all class names to something like "a".

As you can see, both components are rendered with the template of Component2, unless you switch back to beta.0.

I have found several other issues about minification, but not any open one that is exactly the same as this.

#6397 mentions there might be name collisions in TemplateCompiler.

Issue 2:
Hello,

I have trouble for build an application with JSPM and angular2 (2.0.0-beta.0).

When we install angular2 through npm, the package is in node_modules and with a good tsconfig configuration we can load angular2 modules with TypeScript without trouble like this:

import { Component } from 'angular2/core';

But I use JSPM for my app.

So I install angular2 through it and JSPM put the dependency in the subfolder jspm_packages by default. When I load it in the browser with SystemJS I don't have any problems.

The only issue is in the TypeScript compiler.

When I try to import angular2 modules, the TypeScript compiler will try to load modules specify in tsconfig (files) and in node_modules but like I said, the dependency isn't in node_modules but in jspm_packages.

Therefore, I have the following error which is normal :

Cannot find module 'angular2/core';

Because TypeScript try to load nodes_modules/angular2/core instead of jspm_packages/.../angular2/core.

So, my question is how I can do for load angular2 correctly inside the TypeScript compiler ?
Issue 1:
We already have bcrypt and argon2 modules on /x, it would be nice to have them in std just like in golang, also i think both of them (and others too) can be implemented via wasm for better perfomance

Issue 2:
Some applications like handling password will require hashing and encryption. These operations could be implemented in js/ts, but It really needs to be handled from a trusted environment to be secure. It looks like there have been some attempts to get this one rolling before recently with #1461.
Issue 1:
I have a service, which is a class that internally uses Http:

@Injectable()
export class ProductService{

constructor( private http: Http){}

getProductByID(productID: string): Observable{
return this.http.get(`/products/${productID}`)
.map(res => res.json());
}
}

To use this service, an external component must specify [HTTP_PROVIDERS]. This breaks encapsulation of my ProductService (a.k.a. Leaky Abstraction): now it's not a reusable black box but has strings attached. If I decide to replace Http with another service in the above code, the external component must modify its code as well. It would be nice if there was a way to allow a class (not a component) to specify its own providers.

Am I asking for too much? :)

Issue 2:
In the new typings files for http the following lines

type-alias RequestOptionsArgs;

type-alias ResponseOptionsArgs;

are throwing this error message

typings/angular2/http.d.ts(367,16): error TS1005: ';' expected.

typings/angular2/http.d.ts(374,16): error TS1005: ';' expected.

One solution is to comment/remove them.

The file is the one obtained doing

npm install angular2@2.0.0-alpha.35

See #3733

and https://gitter.im/angular/angular?at=55d4b40d1ba62e4a21fa68cc
Issue 1:
Problem description

When navigating through forms, tabbing into a Toggle element displays a rectangular translucent square imposed on top of the switch. I think we could do better than this. It could at least be the circular like the switch is.

Steps to reproduce

Go to http://www.material-ui.com/#/components/toggle and tab through the Examples section.

Versions

Material-UI: 0.15.3

React: 15.3.0

Browser: Chrome

Images & references

Default State:

Keyboard Focus State:

My recommendation would be to make it look similar to disabled state, possibly a different shade of gray.

Disabled state:

I'd be happy to PR this once consensus is reached on how focus state should be rendered.

Issue 2:
Problem description

I have a form with multiple fields. It's easy to use the keyboard to switch between fields, however when the focus switches to the toggle field, it's impossible to tell.

Steps to reproduce

Create a form with a textfield and a toggle. Use tab to change focus.

Versions

Material-UI: 0.15.0

React: 15.1.0

Browser: Chrome, 50.0.2661.102
Issue 1:
System info

Playwright Version: [v1.35.1]

Operating System: [macOS 13.2]

Browser: [All]

Other info:

Source code

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

Test file (self-contained)

// loginPage fixture file
async setExtraHTTPHeaders(): Promise<void> {
await this.page.setExtraHTTPHeaders({ "Client-Id": "", "Client-Secret": "" });
await this.page.route(/(https:\/\/(.*))/, (route) => {
const headers = route.request().headers();
headers["token"] = process.env.token ?? "";
headers["secret"] = process.env.secret ?? "";
route.continue({ headers });
});
}

async navigateTo(path?: string): Promise<void> {
await this.setExtraHTTPHeaders();
await this.page.goto("https://www.google.com")
}

// test file
test("@GCC-demo ABC", async ({ loginPage }) => {
test.setTimeout(10 * 1000);
await test.step("demo1", async () => {
await loginPage.navigateTo();
});
});

Steps

[Run the test]

Please refer to related issue

Expected

It should not display the route.continue outside of the test step

Actual

Issue 2:
Context:

Playwright Version: 1.23.1

Operating System: Linux (ubuntu)

Node.js version: 14.19.1

Browser: Chromium

Code Snippet

Repro repo: https://github.com/thdk/playwright-headless-popup

Describe the bug

I think this issue is a duplicate of closed issue #12342

The problem seems to be that popups won't open in headless mode when they are not initiated from a button element.

This is probably by design. So I'm mainly writing this here as documentation.

If your popup is not opening in headless playwright tests:

Make sure the click event is on a button.

<button onClick={() => openPopup();}>click me</button>

Playwright seems not to open the popup in headless mode when a div element is clicked.
Issue 1:
This seems to be a very inconsistant issue, but I think it's related to macros.

Here's an example of a list of comments that don't get parsed properly:

bitflags! {
flags Tests: Test {
/// Test
static TestA = 0x80,
// TODO: Document this.
static TestB = 0x40
}
}

This code will error saying "no rules expected the token /// Test".

http://is.gd/Zkpgvd

Issue 2:
This would allow doc comments to parse them as $_:meta elements in macro invocations. This is useful for example with bitflags!:

bitflags! {
#[doc = "Some flags"]
#[doc = ""]
#[doc = "A new line"]
#[deriving(Show)]
flags Flags: u32 {
#[doc = "Flag A"]
static FlagA = 0x00000001,
#[doc = "Flag B"]
static FlagB = 0x00000010
}
}

vs:

bitflags! {
/// Some flags
///
/// A new line
#[deriving(Show)]
flags Flags: u32 {
/// Flag A
static FlagA = 0x00000001,
/// Flag B
static FlagB = 0x00000010
}
}

Where the bitflags! match rule is defined as:

($(#[$attr:meta])* flags $BitFlags:ident: $T:ty {
$($(#[$Flag_attr:meta])* static $Flag:ident = $value:expr),+
})
Issue 1:
I am using Python 3.8.10, seaborn 0.11.2

As you can see in the code below, the color (in line_kws) did not render the KDE line. I mean the kde line should be in red instead of blue.

import numpy as np
import seaborn as sns

x = np.random.normal(-1,1,1000)

fig, ax = plt.subplots(figsize=(10,10))
sns.histplot(x,kde=True,line_kws={"color":"red","linewidth":3})

Issue 2:
I was trying to give the distribution KDE a different color when I use sns.histplot(),

Was thinking kde_kws = {'color': ...} would work, but it didn't.

sns.histplot(data=..., kde=True, kde_kws={"color": 'r'})

File ".../Python-library/seaborn/distributions.py", line 1422, in histplot

p.plot_univariate_histogram(

File ".../Python-library/seaborn/distributions.py", line 414, in plot_univariate_histogram

densities = self._compute_univariate_density(

File ".../Python-library/seaborn/distributions.py", line 283, in _compute_univariate_density

estimator = KDE(**estimate_kws)

TypeError: init() got an unexpected keyword argument 'color'
Issue 1:
Hello,

I will try to summarize my problem in a simpler one. Suppose an H Hermitian operator that depends on an α parameter

H = H (α), ψ (x) are eigenfunctions of H, ψ = ψ (x, α). Consider the following function

where f(x) is a continuous function.

The LinearAlgebra.eigvecs function provides ψ correctly, except that the ψ signal fluctuates randomly by + and -. Which is physically correct, because if ψ is a eigenfunction of H, then -ψ is also a eigenfunction with the same eigenvalue. So for some values of α, ψ is positive and for others negative, this happens randomly. In the end, the function J(α) is full of discontinuities. Is it possible to keep the ψ sign?

Thanks

Issue 2:
Issue 1:
http://facebook.github.io/react/docs/interactivity-and-dynamic-uis.html

At the end, there is a confusing explanation about "Duplicated data from props" in the section "What Shouldn’t Go in State?":

Duplicated data from props: Try to use props as the source of truth where possible. Because props can change over time, it's appropriate to store props in state to be able to know its previous values.

Perhaps what is trying to be said is something like:

Duplicated data from props: Try to use props as the source of truth where possible. One valid use to store props in state is to be able to know it's previous values, because props can change over time.

Issue 2:
Currently custom html attributes that start with 'x-' are not allowed.

Here's a test case: http://jsbin.com/jehefo/edit?html,js,console

Allowing custom attributes would be helpful as for example things like Firefox OS use x-inputmode="digit" to provide a hint that the keyboard should only contain only digits. [1]

[1] http://www.wufoo.com/html5/attributes/23-inputmode.html
Issue 1:
Describe your issue.

I've noticed an inconsistency in the behavior of scipy.sparse objects when using the built-in python operators ("",` "@", "/") to multiply or divide by a vector. The "" operator produces a dot product, as opposed to the expected element-wise multiplication (lines 7-9). The "/" operator, on the other hand, performs the expected element-wise operation with broadcasting (lines 11-12), which may be more confusing since it is not consistent with the "*" operator.

I have not tested this behavior across all scipy.sparse matrix types, just the diags used below. I'm happy to submit a PR if this is just a feature that is not yet implemented.

Reproducing Code Example

[1]>>> import numpy as np
[2]>>> from scipy.sparse import diags
[3]>>> D = diags([1, 1], [-1, 0], shape=(6, 5))
[4]>>> D.toarray()
[4]===
array([[1., 0., 0., 0., 0.],
[1., 1., 0., 0., 0.],
[0., 1., 1., 0., 0.],
[0., 0., 1., 1., 0.],
[0., 0., 0., 1., 1.],
[0., 0., 0., 0., 1.]])
[5]>>> x = 1 + np.arange(D.shape[1])
[6]>>> x
[6]=== array([1, 2, 3, 4, 5])
[7]>>> D * x
[7]=== array([1., 3., 5., 7., 9., 5.])
[8]>>> D @ x
[8]=== array([1., 3., 5., 7., 9., 5.])
[9]>>> D.toarray() * x
[9]===
array([[1., 0., 0., 0., 0.],
[1., 2., 0., 0., 0.],
[0., 2., 3., 0., 0.],
[0., 0., 3., 4., 0.],
[0., 0., 0., 4., 5.],
[0., 0., 0., 0., 5.]])
[10]>>> D.toarray() @ x
[10]=== array([1., 3., 5., 7., 9., 5.])
[11]>>> D / x
[11]===
matrix([[1. , 0. , 0. , 0. , 0. ],
[1. , 0.5 , 0. , 0. , 0. ],
[0. , 0.5 , 0.3333, 0. , 0. ],
[0. , 0. , 0.3333, 0.25 , 0. ],
[0. , 0. , 0. , 0.25 , 0.2 ],
[0. , 0. , 0. , 0. , 0.2 ]])
[12]>>> D.toarray() / x
[12]===
array([[1. , 0. , 0. , 0. , 0. ],
[1. , 0.5 , 0. , 0. , 0. ],
[0. , 0.5 , 0.3333, 0. , 0. ],
[0. , 0. , 0.3333, 0.25 , 0. ],
[0. , 0. , 0. , 0.25 , 0.2 ],
[0. , 0. , 0. , 0. , 0.2 ]])

Error message

No error message.

SciPy/NumPy/Python version information

[1]>>> import sys, scipy, numpy; print(scipy.version, numpy.version, sys.version_info) 1.7.1 1.20.3 sys.version_info(major=3, minor=9, micro=6, releaselevel='final', serial=0)

Issue 2:
While sitting with @stefanv last week we discussed (and then @stefanv started implementing) sparse array classes that use the same code as the existing matrix classes, but instead satisfy the ndarray interface (only up to two dimensions). For example slicing out rows would result in 1d arrays rather than 2d matrices, the * operator means elementwise multiply rather than matrix multiply, etc..

This would be valuable for a number of communities and, in particular, anyone trying to use sparse arrays and numpy arrays interchangably, as happens in Pandas, Scikit-Learn, and Dask.array.

I thought I'd raise this issue to track this work (and also to subtly prod @stefanv).

Also cc @NelleV and @njsmith
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-sift-through-text-with-regular-expressions has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

The challenge ask to find all occurrences of the word 'and' expecting '/and+/gi' as solution, but the use of '+' is unnecessary and not clear.

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-create-bootstrap-wells has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

The first step currently reads:

Add two div elements inside your div class="well"> element both with the class col-xs-6

I believe it should be

Add two div elements with class well inside the div with class col-xs-6

For reference, this is the passing code:

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<div class="well">
</div>
</div>
<div class="col-xs-6">
<div class="well">
</div>
</div>
</div>
</div>