WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
It seems that reloading or including a file or package causes multiple, duplicate method listings to be stored and/or displayed. When I'm working on a package or file that defines types and methods, I find that if I load changes with reload or include and then call methods on one of my methods, I get multiple listings of the same method/signature. It also seems that when I call the method, I don't necessarily get the most recent version.

The code below is a minimal example of this behavior. I have observed this behavior with julia 0.3.4, 0.3.5, and 0.3.6 on OSC Mavericks (10.9.5).

Create this file:

File: "dup.methods.jl"

module Dups

import Base: splice!
export splice!

type Foo
thing::Int
end

function splice!(x::Foo,i,item)
Foo.thing = 5
end

end

Then reload it a few times and list the methods on splice!.

julia> include("dup.methods.jl")

julia> include("dup.methods.jl")
Warning: replacing module Dups

julia> include("dup.methods.jl")
Warning: replacing module Dups

julia> include("dup.methods.jl")
Warning: replacing module Dups

julia> methods(splice!)
#12 methods for generic function "splice!":
splice!(a::Array{T,1},i::Integer) at array.jl:598
splice!(a::Array{T,1},i::Integer,ins::AbstractArray{T,N}) at array.jl:598
splice!{T<:Integer}(a::Array{T,1},r::UnitRange{T<:Integer}) at array.jl:614
splice!{T<:Integer}(a::Array{T,1},r::UnitRange{T<:Integer},ins::AbstractArray{T,N}) at array.jl:614
splice!(B::BitArray{1},i::Integer) at bitarray.jl:724
splice!(B::BitArray{1},r::Union(Integer,UnitRange{Int64})) at bitarray.jl:735
splice!(B::BitArray{1},r::Union(Integer,UnitRange{Int64}),ins::BitArray{1}) at bitarray.jl:735
splice!(B::BitArray{1},r::Union(Integer,UnitRange{Int64}),ins::AbstractArray{Bool,1}) at bitarray.jl:772
splice!(x::Foo,i,item) at /Users/phaverty/dup.methods.jl:11
splice!(x::Foo,i,item) at /Users/phaverty/dup.methods.jl:11
splice!(x::Foo,i,item) at /Users/phaverty/dup.methods.jl:11
splice!(x::Foo,i,item) at /Users/phaverty/dup.methods.jl:11

julia>

Note the one entry of splice!(x::Foo,i,item) for each include call. This happens with proper packages and with reload as well. I believe that using reload is what is recommended in the "workflow" section of the documentation. Please correct me if I'm just doing it wrong.

Issue 2:
It would be nice to have a clearly defined AbstractSparseArray <: AbstractArray with an interface that defines where the non-zero values are, and that way generic looping over sparse arrays can be defined. Special matrix types like Tridiagonal should fall under AbstractSparseArray to allow for generic sparse iteration, and then it would make it easier for things like @dlfivefifty 's BandedMatrices.jl to plug into a more generic system of sparsity support.
Issue 1:
Issue Description

Campers will often accidentally create duplicate accounts (most of this is because we made the mistake of offering multiple authentication options).

When they unsubscribe from emails, we want to make sure they are unsubscribed from all emails for all accounts with that email address, including duplicate accounts.

The unsubscribe code just needs to be refactored to get all accounts with that email address. Currently it's a findOne query.

It's located in the RandomAPIs.js and the relevant function is called

To test your code, you'll want to create multiple accounts that have the same email address. You'll then want to test the unsubscribe functionality (https://www.freecodecamp.com/unsubscribe/[email]) and verify that both accounts are unsubscribed. This means all three of these attributes should be set to false:

"sendMonthlyEmail"

"sendNotificationEmail"

"sendQuincyEmail"

Issue 2:
Now when I click in the code area.. now all of the lines of the example show up. Why does it do this? Seems like a bug. Thanks
Issue 1:
Hello, I'd like to suggest the following syntax that you may add to future releases.

<my-component ::params @@myMethod />

Could be equivalent to

<my-component :params="params" @myMethod="myMethod" />

That would make code much cleaner when we have to pass multiple props to a child component and those props have the same name as the variables in the parent component. The same thing can be said about events.

I hope you take this into consideration and that my suggestion will help you improve VUE.

Issue 2:
What problem does this feature solve?

When passing props to a component, the following pattern is very common,

<my-component :propA="propA" :propB="propB" />

I am proposing that when the prop name is the same as the variable name being passed to it, that the following more concise syntax be applicable,

<my-component :propA :propB :propC />

This would mimic ES6's object property declaring shorthands (like here http://www.benmvp.com/learning-es6-enhanced-object-literals/)

What does the proposed API look like?

<my-component :propA :propB :propC />

instead of

<my-component :propA="propA" :propB="propB" />
Issue 1:
I wrote a function to rotate the coordinates of a 2D MvNormal distribution, and in the course of testing it I discovered the Cholesky factorization throws an error depending on the input with bit-level sensitivity. Is this a bug? For my use case, the workaround of wrapping the input in Hermitian() doesn't work, because I can't pass a Hermitian to the MvNormal constructor, which is calling cholesky for me.

Example:

julia> VERSION
v"1.1.0"

julia> rot1 = [1 -1; 1 1] / sqrt(2)
2×2 Array{Float64,2}:
0.707107 -0.707107
0.707107 0.707107

julia> rot2 = [cos(π/4) -sin(π/4); sin(π/4) cos(π/4)]
2×2 Array{Float64,2}:
0.707107 -0.707107
0.707107 0.707107

julia> cholesky(rot1 * [25.0 0.0; 0.0 4.0] * rot1')
Cholesky{Float64,Array{Float64,2}}
U factor:
2×2 UpperTriangular{Float64,Array{Float64,2}}:
3.80789 2.75744
⋅ 2.62613

julia> cholesky(rot2 * [25.0 0.0; 0.0 4.0] * rot2')
ERROR: PosDefException: matrix is not Hermitian; Cholesky factorization failed.
Stacktrace:
[1] checkpositivedefinite(::Int64) at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.1/LinearAlgebra/src/factorization.jl:11
[2] #cholesky!#97(::Bool, ::Function, ::Array{Float64,2}, ::Val{false}) at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.1/LinearAlgebra/src/cholesky.jl:182
[3] #cholesky#101 at ./none:0 [inlined]
[4] cholesky at /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v1.1/LinearAlgebra/src/cholesky.jl:275 [inlined] (repeats 2 times)
[5] top-level scope at none:0

Related issues from Discourse:

https://discourse.julialang.org/t/multivariate-normal-with-positive-semi-definite-covariance-matrix/3029

https://discourse.julialang.org/t/is-this-a-bug-with-cholesky/16970

https://discourse.julialang.org/t/numerical-stability-of-cholesky-factorization/20063

Issue 2:
I have a function where i determine the hessian with finite difference using the hessian function in the Calculus package. Then I test if the hessian is positive definite with isposdef this always return false because, ishermitian is called at:

julia/base/linalg/dense.jl

Lines 27 to 28
in
5e2a617

isposdef!{T<:BlasFloat}(A::StridedMatrix{T}, UL::Symbol) = LAPACK.potrf!(char_uplo(UL), A)[2] == 0

isposdef!(A::StridedMatrix) = ishermitian(A) && isposdef!(A, :U)

before the LAPACK.potrf! is called. Due to numerical inaccuracy will ishermitian always return false because A[i,j] != ctranspose(A[j,i]) in

julia/base/linalg/generic.jl

Line 282
in
5e2a617

if A[i,j] != ctranspose(A[j,i])

, will return true for some i,j due to numerical inaccuracy. If I change the line to !isapprox(A[i,j],ctranspose(Aj,i])) the ishermitian returns true and hence also call the LAPACK.potrf! to check if it is positive definite.

So from my point of view, should ishermitian test approximately equality.
Issue 1:
error: mismatched types: expected core::option::Option<alloc::arc::Arc<std::collections ::hash::map::HashMap<&'static str, alloc::arc::Arc<collections::vec::Vec<item::Item>>>>>,

found core::option::Option<alloc::arc::Arc<std::collections::hash::map::HashMap<&str, alloc::arc::Arc<collections::vec::Vec<&generator::Job>>>>>

would be much more readable as

error: mismatched types: expected Option<Arc<HashMap<&'static str, Arc<Vec<Item>>>>>,

found Option<Arc<HashMap<&str, Arc<Vec<&Job>>>>>

One possibility is to use the names in scope where the type error appears. In any event, we should make sure none of the unqualified names in a given error are ambiguous.

Issue 2:
Right now, when using rustc to only parse an input file, only errors are displayed. There should be an option to also display warnings (and notes) without having to fully compile the program.

Trying again with a recent build of rustc, it appears that not even errors are displayed with rustc 0.5
Issue 1:
Example:

import jax.numpy as jnp
import numpy as np
a = jnp.arange(10).reshape((2, 5))

type(a)

jaxlib.xla_extension.DeviceArray

But if we do:

b, c = a

We get

type(b), type(c)

(numpy.ndarray, numpy.ndarray)

https://colab.research.google.com/gist/romanngg/bc4197d71a404f28224914a2b0dc4481/jnp-np-coversion-when-unpacking.ipynb

Issue 2:
Looping through a DeviceArray like in a list comprehension, for loop, or enumerate returns numpy.ndarray. Is this expected behaviour?

import jax.numpy as np

X = np.array(range(3)).reshape(3,1)
print(type(X))
#<class 'jax.interpreters.xla.DeviceArray'>

x0,x1,x2 = [xi for xi in X]
print(type(x0))
#<type 'numpy.ndarray'>

for xi in X:
print(type(xi))
#<type 'numpy.ndarray'>
#<type 'numpy.ndarray'>
#<type 'numpy.ndarray'>

This is unexpected to me. Why are these not also DeviceArrays?
Issue 1:
System info

Playwright Version: [v1.34.3]

Operating System: [macOS 13.3.1]

Browser: [All]

Other info:

Test file (self-contained)

test.only('Alice Bob', async ({
page,
}) => {
await page.route('http://foo.bar', (route) => {
route.fulfill({
status: 303,
headers: {
location:
'http://alice.bob',
},
});
});

await page.route('http://alice.bob', (route) => {
route.fulfill({
status: 200,
body: 'Alice Bob!'
});
});

await page.goto('http://alice.bob');
await page.goto('http://foo.bar');
});

Steps

[Run the test]

Expected

http://alice.bob ← Alice Bob!

http://foo.bar ← Alice Bob!

Actual

http://alice.bob ← Alice Bob!

http://foo.bar ← DNS_PROBE_FINISHED_NXDOMAIN

Issue 2:
System info

Playwright Version: v1.35

Operating System: macOS 11.6.1

Browser: Chromium

Config file

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

export default defineConfig({
testDir: './tests',
fullyParallel: true,
forbidOnly: !!process.env.CI,
reporter: 'html',
timeout: 60000,
use: {
baseURL: 'https://pressreleasehub-staging.pa.media/',
trace: 'retain-on-failure',
headless: false,
browserName: 'chromium',
viewport: { width: 1680, height: 1050 },
video: 'retain-on-failure',
screenshot: 'only-on-failure',
actionTimeout: 30000,
launchOptions: {
slowMo: 300,
},
},
workers: 4
});

Test file (self-contained)

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

test.describe('Verify Press Release Hub Contributor Pages', () => {

test.only('Verify Contributor Pages', async ({ page }) => {
await page.goto('https://pressreleasehub-staging.pa.media/');

// Open the Contributors menu
await page.click('#navbar-contributors');

// Get all menu links within the Contributors menu
const allLinks = await page.locator('.NavigationBar_subMenuColumns__fN1Rt > li > a').all();

// Assert 37 menu links are present
expect(allLinks.length).toBe(37);

for(let i = 0; i < allLinks.length; i++) {
const contributorName = (await allLinks[i].innerText()).toLowerCase();
await allLinks[i].click();

const contributorHeading = page.locator('.SectionHeader_sectionHeader___3ygo ').getByRole('heading', {name: contributorName.toLowerCase()});
await contributorHeading.waitFor();

await page.goBack();
await page.click('#navbar-contributors');
}
});
});

Steps

Run the test

Expected

All stages of the test should complete successfully

Actual

The test itself does actually seem to pass, however, instead of completing successfully it hangs until the timeout value of 60 seconds is reached and then fails with the following error:

Test finished within timeout of 60000ms, but tearing down "context" ran out of time. Please allow more time for the test, since teardown is attributed towards the test timeout budget.

However, the test is completing well before that 60 second timeout.
Issue 1:
The spec seems to allow package main to import another package main under another name.
However, the experience with the go tool is inconsistent:

% cd $GOPATH/src/foo
% cat a/a.go
package main

import _ "foo/b"

func init() { println("init: a") }
func main() {}
% cat b/b.go
package main

func init() { println("init: b") }
func main() {}
% rm -f $GOPATH/bin/a
% rm -f $GOPATH/bin/b
% go install ./a
% touch a/a.go
% go install ./a
# foo/a
a/a.go:3: can't find import: "foo/b"
%

My setup:

% go env
GOARCH="amd64"
GOBIN=""
GOCHAR="6"
GOEXE=""
GOGCCFLAGS="-g -O2 -fPIC -m64 -pthread -fno-common"
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/p/go"
GOROOT="/usr/local/Cellar/go/1.0.3"
GOTOOLDIR="/usr/local/Cellar/go/1.0.3/pkg/tool/darwin_amd64"
CGO_ENABLED="1"
%

Issue 2:
Looking at a liveness bitmap while debugging a garbage collector crash (probably caused
by a linker bug):

(gdb) x/16xw 'fmt.Sprintf.gclocals·0'
0x10b780 <fmt.Sprintf.gclocals·0>: 0x00000005 0x00000006 0x00000004 0x00000006
0x10b790 <fmt.Sprintf.gclocals·0+16>: 0x00000004 0x00000006 0x00000005 0x00000006
0x10b7a0 <fmt.Sprintf.gclocals·0+32>: 0x00000005 0x00000006 0x00000004 0x00000000
0x10b7b0 <fmt.Sprintf.gclocals·0+48>: 0x00000000 0x00000000 0x00000000 0x00000000
(gdb)

That's 5 bitmaps, each of 6 bits, and the bit pattern is sometimes 4 sometimes 5.
The corresponding pcdata is:

fmt.Sprintf pcdata=1:
0-30: -1 (really 0)
30-98: 1
98-131: 2
131-165: 3
165-208: 4

A few observations:

The default padding to 16 bytes is not helping; if we record an explicit alignment
for the symbol we can pad only to 4-byte boundaries, which will cut the size of
the symbol from 16 words to 11.
The bitmap size is the same for all bitmaps and could be stored just once.
That would cut the size of the symbol from 11 words to 7.
Bitmaps with the same bits could be stored just once for a given symbol.
That would cut the size of the symbol from 7 words to 4.
A global dedup might be interesting too but this local dedup might be an easier first
step.
In aggregate these changes would be a 4x reduction for this simple case and probably at
least 2x overall.

Should do for Go 1.3 to reduce memory footprint but not immediately urgent.
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1478/

Failed: [k8s.io] [HPA] Horizontal pod autoscaling (scale resource: CPU) [k8s.io] [Serial] [Slow] ReplicaSet Should scale from 5 pods to 3 pods and from 3 to 1 and verify decision stability {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/horizontal_pod_autoscaling.go:64
Expected error:
<*errors.errorString | 0xc8212e98d0>: {
s: "Only 0 pods started out of 1",
}
Only 0 pods started out of 1
not to have occurred

Issue 2:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1446/

Failed: [k8s.io] [HPA] Horizontal pod autoscaling (scale resource: CPU) [k8s.io] [Serial] [Slow] Deployment Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/horizontal_pod_autoscaling.go:50
Expected error:
<*errors.errorString | 0xc820c91020>: {
s: "Only 0 pods started out of 1",
}
Only 0 pods started out of 1
not to have occurred
Issue 1:
To improve the API docs and to reduce duplicated documentation work, it seems to be useful to link to certain parts of the documentation from the API docs (for example, as stated in #12496, linking to the cookbook that explains how to use Form events easily adds additional value to the API docs of the existing events without the need to duplicate information).

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.2.13

I have implemented form field for collection with allow_delete = true, allow_add = true and by_reference = false options.

I added needed js code to delete elements and append forms for new objects of this collection from prototype.

This works as I expected, but when I submit a few subforms for this collection with indexes not in order (for example 0, 1, 3 instead of 0, 1, 2), then errors from subform with index 3 are assigned to index 2 (which not exists), but subforms are rendered with indexes 0, 1, 3 (same as before submit) after invalid form submit...

I'm sure that it worked correctly in Symfony (errors from subform with index 3 are assigned to subform with same index).
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Exact highlight underline alignment all the time (even after heat death of the universe).

Current Behavior

(In my app) after page reload the line goes under the second tab. It fixes itself on second render or on window resize.

Steps to Reproduce (for bugs)

I don't have a small project to reproduce this. I made only this video https://streamable.com/swsom

If you have no idea why it happens just close this issue (I will try to fix it later).

<Tabs
indicatorColor="primary"
textColor="primary"
value={this.props.activeTab}
onChange={this.onTabsChange}
fullWidth
>
<Tab label="Sign In" value="login" />
<Tab label="Sign Up" value="register" />
</Tabs>

Your Environment

Tech
Version

Material-UI
1.0.0-beta.31

React
16.2.0

browser
Chromium 63.0.3239.132

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

Expected Behavior

Pass a class with styles to component and change label color

Current Behavior

in any possible way based from material-ui docs in 0.15 and 1.0 version it is impossible to change/override a color of label

Steps to Reproduce (for bugs)

create and style constant and use withStyle HOC

const styles = theme => ({
button2: {
color: '#ec5c5d',
fontSize:"15px",
'&:hover': {
color: '#ec5c5d',
},
label: {
color: '#ec5c5d',
},
InputLabel: {
root: {
color: '#ec5c5d',
}
},
MuiInputLabel: {
root: {
color: '#ec5c5d',
}
}
}
})

<TextField id="breeders-races-filter-search" label="Search race" fullWidth margin="normal" className={this.props.classes.button2} />

text-size works, colors do not !

Context

Impossible to use it in system, we are close to remove whole lib and rewrite over 20k of lines.

Your Environment

Mac os x

next.js

Tech
Version

Material-UI
1.00

React
16

browser
chrome current
Issue 1:
I'm trying to use both fitCenter and placeholder but the image does not get resized.

This code works fine (image is scaled down, aspect ratio is correct):

Glide.with(this).load(url).fitCenter().into(mImage);

This code does not work (placeholder is correct, but loaded image appears squished, aspect ratio is wrong):

Glide.with(this).load(url).placeholder(R.drawable.placeholder).fitCenter().into(mImage);

Issue 2:
Glide Version/Integration library (if any): 3.5.2

Device/Android Version: S4/4.4

Issue details/Repro steps: Load a different sized thumbnail and image, or placeholder and image and note the result:

Glide load line:

class Delay extends UnitTransformation {
private final int sleepTime;
public Delay(int sleepTime) { this.sleepTime = sleepTime; }
@Override public Resource transform(Resource resource, int outWidth, int outHeight) {
try { Thread.sleep(sleepTime); } catch (InterruptedException ex) {}
return super.transform(resource, outWidth, outHeight);
}
}

@Override protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
final ImageView image = new ImageView(this);
setContentView(image);

// Saved as R.drawable.placeholder
String placeholder = "http://placehold.it/300x500/eedddd.png&text=PLACEHOLDER";
// Square image
String thumb = "http://placehold.it/300x300/eeeedd.png&text=THUMB";
// Wide image
final String full = "http://placehold.it/300x100/eedddd.png&text=FULL";
// Prepared request with unimportant clutter
final DrawableRequestBuilder<String> req = Glide
.with(this)
.fromString()
.diskCacheStrategy(DiskCacheStrategy.SOURCE) // disable network delay for demo
.skipMemoryCache(true) // make sure transform runs for demo
.crossFade(2000) // default, just stretch time for noticability
;

req.clone()
.thumbnail(req.clone()
.transform(new Delay(500)) // wait a little
.load(thumb)
)
.transform(new Delay(1000)) // wait before going from thumbnail to image
//.dontAnimate() // solves the problem
.load(full)
.into(image);

image.setOnClickListener(new OnClickListener() {
@Override public void onClick(View v) {
req.clone()
.load(full)
.placeholder(R.drawable.placeholder)
.transform(new Delay(1000))
//.animate(R.anim.abc_fade_in) // also solves the problem
.into(image);
}
});

By removing all the delaying parts, the end result is better, but the now the thumbnail is messed up:
Issue 1:
Q
A

Bug report?
no

Feature request?
yes

BC Break report?
no

RFC?
no

Symfony version
4.x

Introduction

Symfony 3.3 introduced a convention of naming services with their FQCN. The update pathway for legacy applications is simple: just start using new naming convention and slowly all services will get new names.

The problem

While refactoring parts of the application it's worth to clean up a little bit. One of the steps which I perform is ensuring services are names by their FQCNs (which simplifies the configuration due to autoregistration). However, especially for public services, I cannot ensure old names aren't used somewhere.

Solution

Long time ago I assumed deprecated tag can be used on aliases - 4 proved me wrong nicely throwing The configuration key "deprecated" is unsupported.

What if we actually introduced deprecated key on aliases to mark them as deprecated while the service itself stays non-deprecated?

Issue 2:
Would love to hear your feedback. Thanks!
Issue 1:
String.prototype.localeCompare() on MDN

I noticed that some results differ significantly from Chrome in test cases when using this method. I'm not sure if/how this is standardized or where the responsibility lies, but I wanted to surface this because it seems like a bug.

Here's an example you can copy+paste to run in a browser console or Deno REPL:

(() => {
const pairs = [
['a', 'á'],
['á', 'a'],
['a', 'b'],
['b', 'a'],
['á', 'b'],
['b', 'á'],
];

const compare = (a, b) => a.localeCompare(b, 'en-US', {sensitivity: 'base'});
const results = pairs
.map(pair => [...pair, compare(...pair)].join(' '))
.join('\n');
console.log(results);
})();

a
b
Chrome
Deno

a
á
0
-128

á
a
0
128

a
b
-1
-1

b
a
1
1

á
b
-1
127

b
á
1
-127

Chrome 83.0.4103.97

Deno 1.1.0

Specifically, note the description for using the value "base" for the "sensitivity" option:

Only strings that differ in base letters compare as unequal. Examples: a ≠ b, a = á, a = A

In the example above for a and á, Chrome returns 0 (equal), but Deno does not.

Issue 2:
As seen in #1952 / #1636 ICU needs to be added in Deno build.

Switching this flag to true maybe: https://github.com/denoland/deno/blob/master/.gn#L50 ?

ref: https://v8.dev/docs/i18n