WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Description of the problem

This is a follow-up to #19077. The following svg is rendered correctly in firefox, chrome, and android, but incorrectly in three.js.

infinity.txt

Repro: https://jsfiddle.net/L3krx9ho/

Three.js version

Dev

r115

Browser

All of them

Chrome 80.0.3987.149

Firefox 74.0

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Issue 2:
Description of the problem

I tried exporting the mesh using the latest version of GLTFExporter.

However, the size of the output model is larger than I thought.

The size when exporting scene.gltf with the following sample is 928 KB.

three.js + GLTFExporter result:

In this model, vertex colors are not used, but it seems that attributes of white vertex colors are generated in the output glTF file. Perhaps by excluding unused attributes I think that the size can be made even smaller.

Three.js version

Dev

Browser

Chrome

OS

Windows

Hardware Requirements (graphics card, VR Device, ...)

ThinkPad X260 + Intel HD Graphics 520

Modified: Link of GLTFExporter was GLTFLoader, it was fixed.
Issue 1:
There are cases where we want to run a pod on every node. This'll be useful for monitoring things (cAdvisor, DataDog) or replicated storage agents (HDFS node).

Right now you can approximate this by (a) using a hostPort and (b) setting replication count > nodes. It would be better if we had an explicit way of doing this.

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

Failed: [k8s.io] Pod Disks should schedule a pod w/two RW PDs both mounted to one container, write to PD, verify contents, delete pod, recreate pod, verify contents, and repeat in rapid succession [Slow] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/pd.go:271
Expected error:
<*exec.ExitError | 0xc8208754e0>: {
ProcessState: {
pid: 11361,
status: 256,
rusage: {
Utime: {Sec: 0, Usec: 84000},
Stime: {Sec: 0, Usec: 24000},
Maxrss: 29572,
Ixrss: 0,
Idrss: 0,
Isrss: 0,
Minflt: 2131,
Majflt: 0,
Nswap: 0,
Inblock: 0,
Oublock: 0,
Msgsnd: 0,
Msgrcv: 0,
Nsignals: 0,
Nvcsw: 768,
Nivcsw: 3,
},
},
Stderr: nil,
}
exit status 1
not to have occurred
Issue 1:
Challenge http://freecodecamp.com/challenges/waypoint-add-different-margins-to-each-side-of-an-element has an issue. User Agent is: Mozilla/5.0 (Macintosh, Intel Mac OS X 10_10_5) AppleWebKit/600.8.9 (KHTML, like Gecko) Version/8.0.8 Safari/600.8.9. Please describe how to reproduce this issue, and include links to screenshots if possible.

It appears that I can redo a waypoint an unlimited amount of times, and thus get an unlimited amount of points. It doesn't appear to matter which waypoint it is. I have tried with the HTML5/CSS section. If you redo the waypoint, you will still get a point.

Issue 2:
Challenge http://freecodecamp.com/challenges/waypoint-import-a-google-font has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

I noticed new waypoints for HTML5/CSS sections. I completed some of the new ones, and just to refreshen up on some older waypoints I finished a while ago, I decided to redo some.

I noticed that I was receiving points for complete the waypoints that I have already done. These were the ones that were done before the new update in the curriculum.
Issue 1:
http://www.elasticsearch.org/guide/reference/query-dsl/custom-filters-score-query.html

Hello, I use in the application of custom - filters - score - query achieve business requirements, similarity calculation. But I found, two machines running for a period of time, of which one will search performance fell sharply,

Obviously see IO, speaking, reading and writing down, finally the following anomaly, but found that stop off one of the machine and returned to normal.

The 2012-08-16 10:46:37, 048 ERROR filter. ExceptionFilter - [DUBBO] Got unchecked and undeclare service method invoke exception: null, DUBBO version: 2.0.14, current host: 172.22.28.88

Org. Elasticsearch. ElasticSearchInterruptedException

At org. Elasticsearch. Action. Support. AdapterActionFuture. ActionGet (AdapterActionFuture. Java: 47)

Unfortunately I don't have specific anomaly information, only org. Elasticsearch. ElasticSearchInterruptedException. Please instruct me.

2 * （ 16 core 24 g physical machine ）

Issue 2:
Hello, I use in the application of custom - filters - score - query achieve business requirements, similarity calculation. But I found, two machines running for a period of time, of which one will search performance fell sharply,

Obviously see IO, speaking, reading and writing down, finally the following anomaly, but found that stop off one of the machine and returned to normal.

The 2012-08-16 10:46:37, 048 ERROR filter. ExceptionFilter - [DUBBO] Got unchecked and undeclare service method invoke exception: null, DUBBO version: 2.0.14, current host: 172.22.28.88

Org. Elasticsearch. ElasticSearchInterruptedException

At org. Elasticsearch. Action. Support. AdapterActionFuture. ActionGet (AdapterActionFuture. Java: 47)

Unfortunately I don't have specific anomaly information, only org. Elasticsearch. ElasticSearchInterruptedException. Please instruct me.

2 * （ 16 core 24 g physical machine ）
Issue 1:
deno --version

deno 1.5.0
v8 8.7.220.3
typescript 4.0.3

deno bundle "https://deno.land/x/djwt@v1.9/mod.ts" > djwt.js

using the bundled djwt.js produces the following error:

ReferenceError: convertUint8ArrayToHex is not defined

convertUint8ArrayToHex is declared in deps.ts of the djwt lib

referencing an issue opened against djwt

Issue 2:
echo "import createGraph from \"https://dev.jspm.io/ngraph.graph\"; console.log(createGraph);" > test.ts
deno run test.ts
Check file:///Users/jveres/temp/test.ts
[Function: createGraph]

deno bundle test.ts test.bundle.js
Bundle file:///Users/jveres/temp/test.ts
Check file:///Users/jveres/temp/test.ts
Emit "test.bundle.js" (10.65KB)

deno run test.bundle.js
error: Uncaught ReferenceError: _npmNgraphDew is not defined
var eventify = _npmNgraphDew();
^
at dew (file:///Users/jveres/temp/test.bundle.js:10:20)
at file:///Users/jveres/temp/test.bundle.js:304:21
Issue 1:
I notice this that doing simply operations on an array can allocate a lot of memory when I don't think it would need to. For example:

julia> function foo(a::AbstractArray, value::Int)
for i in 1:length(a)
a[i] += value
end
end
foo (generic function with 1 method)

julia> len = 100000000; a = collect(1:len);

julia> foo(a, 20); #compile

julia> @time foo(a, 20);
0.116317 seconds (4 allocations: 160 bytes)

julia> @time a[:] += 20;
1.871425 seconds (13 allocations: 1.490 GB, 6.84% gc time)

julia> @time a += 20;
0.542140 seconds (8 allocations: 762.940 MB, 0.33% gc time)

julia> @time a + 20;
1.095872 seconds (8 allocations: 762.940 MB, 7.90% gc time)

From the example above, foo,(a, 20), a[:] += 20, and a += 20 are all doing the same thing, but my foo function is much faster and takes a fraction of the allocated memory.

Should julia's memory management be able to identify those cases and avoid the extra allocation?

Issue 2:
The following code fails with an InexactError():

X = [1,2,3]
Y = [4 5]
broadcast(atan2, X, Y)

whereas

[atan2(x,y) for x in X, y in Y ]

(albeit producing an array of type Any), while

atan2([1,2,3],[4,5,6])

produces an array of Float64.

Can we improve the type inference so that all three cases can generate Float64 arrays? Note that this is needed for #4363 (for @vectorize_2arg to use broadcast).
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-iterate-with-javascript-while-loops has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

"Let's try getting a for loop to work by pushing values to an array."

Should probably read as:

"Let's try getting a while loop to work by pushing values to an array."

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-remove-classes-from-an-element-with-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Expected passing code: $("button").removeClass("btn-default");

Exercise automatically passes with: $("button").removeClass();
Issue 1:
Stupid question of the day, why does this not work:

class A {
foo: string;
}

class B {
bar: string;
}

class C {
qat: string;
}

class D {
baz: string;
}

function c(a: A): C; /* Overloaded signature not compatible with function implementation */
function c(b: B): D;
function c(a: A|B): C|D {
if (a instanceof A) {
return new C();
}
else {
return new D();
}
}

Where as this is valid:

function c(a: A): C|D;
function c(b: B): C|D;
function c(a: A|B): C|D {
if (a instanceof A) {
return new C();
}
else {
return new D();
}
}

I am allowed to "delegate" the sorting out of the typing of my argument to my overloaded function implementation, but, I am not allowed to delegate the return type, though I am contracting to only return to return a certain type of return value (which is what I am doing with the handling arguments). Is there a good reason I am missing?

Issue 2:
Consider some code:

/* ... disjoint classes Giraffe, Elephant which extend Animal ... */
function f(n: string): Giraffe;
function f(n: number): Elephant;
function f(n: any): Animal {
if(typeof n === 'string') {
return new Giraffe(n);
} else if(typeof n === 'number') {
return new Elephant(n);
}
}

Perhaps surprisingly, this yields errors on the overload signatures because the function implementation signature is not assignable to the overload signatures. This is unfortunate for implementors as they must use :any when implementing a function with disjoint parameter types in its overloads. Now that union types are possible, the implementor of f could even write Giraffe|Elephant to get more specific type checking of their return expressions.

One option is to change the relation in 6.1 from "assignable to" to "assignable to or from". This solves the issue above, but has a negative side effect of allowing an implementation signature to have more required parameters than any of the overloads. This might be a desirable trade-off compared to not allowing implementations to have good return expression checking. Alternatively, we could create some new kind of relation that is bivariant for return types but maintains the existing requirements of parameter arity.

Note that we do want to use the opposite assignability relation here as the implementation signature may be of an inconsequentially more-specific type.
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-kops-aws/1949/

Failed: [k8s.io] EmptyDir volumes should support (root,0666,default) [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/empty_dir.go:101
Expected error:
<*errors.errorString | 0xc420f90700>: {
s: "failed to get logs from pod-ae4ea1da-b22b-11e6-a421-0242ac110008 for test-container: an error on the server (\"unknown\") has prevented the request from succeeding (get pods pod-ae4ea1da-b22b-11e6-a421-0242ac110008)",
}
failed to get logs from pod-ae4ea1da-b22b-11e6-a421-0242ac110008 for test-container: an error on the server ("unknown") has prevented the request from succeeding (get pods pod-ae4ea1da-b22b-11e6-a421-0242ac110008)
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2169

Issue 2:
Validation as it exists today is pretty wrong - it tracks internal types. Once we have long-term support for v1 API and are deep into v2 rework, the validation errors that are produced for v1 will be less and less useful.

We've gone back and forth about this but have not yet come up with a good answer on how to do this generically. I propose we just move it to be per-version, same as defaulting.

Given that v1beta[12] are on the block right now and v1beta3 will be soon, this is the right time. The same day we delete v1beta3 we should move pkg/api/validation into v1 and make it use versioned types.

Yes, it will be tedious to make changes, but I think that is the cost of having multiple versioned APIs in support cycles.
Issue 1:
Hi,

Hope this doesn't take you guys too much time to look into it.

See here for a runnable example: http://jsbin.com/qecuhoka/1/edit

Try clicking the button 'Open a popover' multiple times, the content of popover becomes more and more.

Just would like to know if this is an intended behavior.

Thank you very much.

Issue 2:
Hey there,

A recent change 5bf1391 related to issue: #10658

Leads to behavior I'd consider at the very least undesired(and probably overlooked). The net effect is that by using "append", the content returned by the popover method gets re-appended on every single popover toggle.

http://jsfiddle.net/jQxdv/

This is different than the plugin's behavior historically. Was this a desired change? If yes, why is piling up content considered correct in this case?
Issue 1:
It would be great to have a way of obtaining elements of a mini batch from within vmap, i.e. an equivalent of pmap's all_gather.

Abstracting away the batch dimension seems like one of the core JAX features, but there are a lot of use cases where batch information is necessary. Some that come to mind are normalizing modules, such as BatchNorm, or contrastive estimation which often depends on positive/negative samples across the minibatch.

Related to this, are there any plans to unify vmap and pmap and potentially expose the rest of the parallel operators for use with vmap?

Issue 2:
JAX has a number of semantically different ways to vectorize, parallelize or loop:

vmap (vectorization)

pmap (parallelization)

lax.map (XLA loop)

map (Python builtin loop)

(and combinations thereof)

These are all different ways of implementing the same "mapped" function with various performance tradeoffs. But they cannot be easily swapped back and forth because they use different syntax:

Signatures:

vmap and pmap are function transformations

lax.map acts along the first axis of arrays

map acts directly on Python sequences

Functionality:

pmap supports collective operations along mapped axes, but requires that the axis size matches the number of dimensions.

It would be a boon to user productivity if we could use the exact same API to specify every type of "map", including hybrid versions like soft_pmap (mixed pmap/vmap).

This would be valuable even within JAX, because higher level functionality that relies upon mapping (e.g., jacfwd, jacbwd, hvp, numpy.vectorize, soft_pmap) could be parameterized to support any type of map, not just vmap.
Issue 1:
Using a navbar and a navbar-right ( as shown in the examples here http://getbootstrap.com/components/#nav )

But when i scale the browser down, it's overlapping.

<ul class="nav navbar-nav">

</ul>
<ul class="nav navbar-nav navbar-right">

</ul>

Issue 2:
Been looking at this (and I apologize if this issue was already addressed) - and took this site I'm working on (mcgarrybair.com) right out of the BS3 RC2 examples. Resizing the window from -lg to -md wraps the nav-bar into multiple lines. You can see this on the law firm site I just published at http://mcgarrybair.com - this causes the site to render unaccaptably in an iPad (tablet view). I think the navbar should not wrap - but go immediately from one-line of menus to collapse? Wrapping the navbar that is a navbar-fixed-top into multiple lines of li items causes it to overlap the content of the site.
Issue 1:
I've developed an OpenGL-based C++ animation engine. I'm wrapping it into a Node.js module using SWIG and would like to hook it into an Electron app.

The engine has a very encompassing test suite -- Between that and the simplest node scripts, I can see all basic functionality working as expected outside an Electron app. The test suite and scripts also work when running Electron as Node via ELECTRON_RUN_AS_NODE.

Mysteriously, I can't perform any rendering inside an Electron app in neither the browser nor render process.

More accurately, any calls to glGenX return 0. Querying glGetString(GL_VERSION) returns null, afterward glGetError reports no error. I've made a StackOverflow question that describes how I check context creation; I don't think I'm missing anything, but contexts still appear to be dysfunctional.

Is this perhaps known behavior? Is there a caveat I'm missing?

I'm running Debian Stretch and Electron 1.5.1, unable to upgrade to a newer version without module version mismatches.

In case Chromium is interfering with my OpenGL contexts somehow, I've tried disabling hardware acceleration, ensuring it is disabled before the app is ready. I've also tried passing --disable-gpu.

All OpenGL actions are 100% definitely occurring in the same thread.

Architecture of electron and the module are both x64.

Issue 2:
Electron version: 1.6.1

Operating system: Linux

Expected behavior

I have created a nodejs addon that works inside electron as well. When running against nodejs I can

create a GLFW window with a GLES2 context and use it as expected. When running against electron, a GLFW window is created, the context briefly exists, then as soon as I call a GL function, it behaves as if the context is gone. glGetString(GL_VERSION) returns null immediately after creating the window, and after explicitly making the context current. glGetError also returns 0.

This worked previously just fine in v1.4.15.

How to reproduce

This requires that GLFW3, Electron, and node-gyp are installed on the system.

The build script is also hard coded to build for electron 1.6.1.

git clone https://github.com/MyUPlay/MyEngine
cd MyEngine
make -j8
electron test/core/BasicExample-electron.js

To prove the code works otherwise (from inside the repo):

NODEBUILD=1 make -j8
node test/core/BasicExample.js

The js has to be different, obviously, so that it doesn't call electron to do the UI, which should be the only difference.
Issue 1:
Docker supports a way to push environment variables to the containers using env files. I see that there is a way to push env-variables via the pod creation JSON but I don't see anyway to push env-files for the same. Is there any other way to do this?

Issue 2:
Forked from #1743

One of the critical features we're lacking on the configuration front is template parameterization. We should decide on what approach we want to take.

Working list of requirements:

It should be schema-respecting, not arbitrary textual transformation, in order to facilitate schema validation and independent substitution/decoration passes.

Input parameters should be clearly declared, such as to facilitate form generation, as discussed in #4210 and #6487.

Substitution should be independent of reconciliation, as per @ghodss's comment.
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-use-the-bootstrap-grid-to-put-elements-side-by-side has an issue.

Coding area shows the sample CSS when it should show the sample HTML. Challenge asks student to edit the HTML.

Issue 2:
http://www.freecodecamp.com/challenges/waypoint-make-object-properties-private

Only the code up to line 10 is shown until I scroll the window, then all of the code appears.

http://i.imgur.com/mZgRdxR.png

http://i.imgur.com/IAilUT0.png

It's a small bug, but it really threw me off at first as I couldn't figure out if I was supposed to be writing the methods myself that the question was referring to.
Issue 1:
Not important but I would expect this to work.

Issue 2:
After updating to 1.6.0, deno completions command is crashing with zsh, note that earlier shell completions are working, just the deno completions zsh is crashing, other completions like deno completions bash or even deno completions elvish working fine.

error:

thread 'main' panicked at 'Fatal internal error. Please consider filing a bug report at https://github.com/clap-rs/clap/issues', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.33.3/src/completions/zsh.rs:407:29
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

with backtrace:

thread 'main' panicked at 'Fatal internal error. Please consider filing a bug report at https://github.com/clap-rs/clap/issues', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-2.33.3/src/completions/zsh.rs:407:29
stack backtrace:
0: rust_begin_unwind
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:483
1: core::panicking::panic_fmt
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:85
2: core::option::expect_failed
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/option.rs:1226
3: core::option::Option<T>::expect
4: clap::completions::zsh::get_args_of
5: clap::completions::zsh::get_subcommands_of
6: deno::flags::flags_from_vec_safe
7: deno::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

this looks clap-rs issue to me, not sure if something is wrong on deno side
Issue 1:
Several LAPACK routines have been deprecated in the current development of LAPACK.

NOTE that one can still force the addition of the routines, but the default is not to add the symbols to the LAPACK library table.

I am not sure how deprecation symbols should be handled in scipy, hence I refrain from beginning a PR.

The bug arises when trying to import scipy.linalg where it errors out due to missing symbols (obviously).

Currently my own work-around are these steps:

sed -i '/[sdcz]gegs/d' scipy/linalg/cython_lapack_signatures.txt, remove signatures

Note that this should also be applied to alle these routines as well:

gegv

gelsx

geqpf

ggsvd

ggsvp

latzm

lahrd

tzrqf

sed -i '/2[c]*>gegv/{N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;N;d}' scipy/linalg/flapack.pyf.src, remove interfaces for f2py (only the gegv routine is in the pyf source)

python _cython_wrapper_generators.py, regenerate cython_lapack.pxd from signatures

python tools/cythonize.py, update the cython_lapack.c file

and it works again.

Possibly checking the LAPACK library for the corresponding interfaces would be sufficient to decide whether the interface should be added or not.

Issue 2:
This was originally planned in #12603 already but was then weakened to a doc-only deprecation in c88177c based on feedback by @rgommers:

Can you doc-deprecate it instead? A real deprecation in the absence of bugs or other major issues seems a bit gratuitous.

I think by now, this could be reconsidered, as having duplicate methods is not ideal either...
Issue 1:
We are extensively using javascript auto format code feature in vs code to reduce js lint errors.

Ex: spaces after function and function name etc ...

after updating to v0.10.10 above formatting is not working any more and it reset all the formatted functions without spaces.

Can someone help or give information how to override this rule ?

var test = function() { }; //this is what new version format js code to.

but we are expecting and previously worked before like below.

var test = function () { };

Issue 2:
From @isidorn on January 26, 2016 15:50

js workspace, have salsa enabled

"editor.formatOnType": true

The format on type is too aggrressive and does not respect current indentiation. This is especially noticable when trying to create object literals

if salse is disabled this works nicely

Copied from original issue: microsoft/vscode#2377