WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
This is a strange bug.

When loading both https://deno.land/std@0.63.0/hash/mod.ts and some cjs files, deno checks the type of cjs.

export { createHash } from "https://deno.land/std@0.63.0/hash/mod.ts";
import {} from "./cjsTest.cjs"

error: TS2339 [ERROR]: Property 'test' does not exist on type '{}'.
return exports.test;
~~~~
at file:///C:/Users/stone/OneDrive/%EB%B0%94%ED%83%95%20%ED%99%94%EB%A9%B4/%EC%83%88%20%ED%8F%B4%EB%8D%94/postgres/cjsTest.cjs:4:18

Windows 10 v2004 - X

WSL (Ubuntu bionic) - X

macOS Catalina - X

Issue 2:
Receiving TS2531 [ERROR] when running the mjs/cjs after Deno 1.0.4.

save as "test.mjs"

import { exp } from "./test_mod.ts";
if (false) null.func();

save as "test_mod.ts"

export const exp = {};

and run

% deno run test.mjs
Compile file:/// ... /test.mjs
error: TS2531 [ERROR]: Object is possibly 'null'.
if (false) null.func();
~~~~
at file:/// ... /test.mjs:2:12

1.0.5 -- NG

1.0.4 -- NG

1.0.3 -- OK

without ts import -- OK

import mjs -- OK
Issue 1:
Summary of the new feature/enhancement

Well I did not see it suggested before so I would create a ticket for it

This is mostly as most game would used modifier keys (Ctrl,Alt,Shift) and depend on keyboard layout, Win key might be close to it and accidentally trigger would be costly in game.

Solution

So I would request either disable it or rebind it per focused app to non-interrupt combo like Home/End as those would mostly process if in-game chat was open

I still debate on if we still trigger like normal if it was Win+XXX Combo. Like Win+1 might be accident of Ctrl+1.

I understand that this is wait on per app binding feature.

Issue 2:
📝 Add option to only show taskbar hints on shortcut guide

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

The main reason I like the shortcut guide powertoy is because it shows the numbers over taskbar items to jump directly to them (e.g. WinKey + 5 to open the 5th taskbar item). This is useful because unlike other shortcuts, these are prone to change depending on which applications you have open and the powertoy keeps you from having to count out where an app is in the taskbar. It would be useful for other users like me who are familiar with the main shortcuts to have an option to only show the number hints over the taskbar without the rest of the overlay when the windows key is held.

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

I am trying build the ios app detailed in https://petewarden.com/2016/09/27/tensorflow-for-mobile-poets/

but it fails with:

checking whether we are cross compiling... configure: error: in /projects/tensorflow/tensorflow/tensorflow/contrib/makefile/downloads/protobuf': configure: error: cannot run C compiled programs. If you meant to cross compile, use--host'.

See `config.log' for more details

system details;

macos sierra, 10.12

brew config output: Any pointers will be appreciated.

MacBook-Pro:tensorflow $ brew config

HOMEBREW_VERSION: 1.0.6

ORIGIN: https:/

HEAD: 35ee2831086e923e7fcaf75fb440b01312e3f9c5

Last commit: 7 days ago

Core tap ORIGIN: https:/

Core tap HEAD: 80f18defefc814d60d3799e58835cbeffc8e93c8

Core tap last commit: 2 hours ago

HOMEBREW_PREFIX: /usr/local

HOMEBREW_REPOSITORY: /usr/local/Homebrew

HOMEBREW_CELLAR: /usr/local/Cellar

HOMEBREW_BOTTLE_DOMAIN: https:/

CPU: quad-core 64-bit broadwell

Homebrew Ruby: 2.0.0-p648

Clang: 8.0 build 800

Git: 2.8.4 => /Applications/Xcode.app/Contents/Developer/usr/bin/git

Perl: /usr/bin/perl

Python: /usr/bin/python

Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby

Java: 1.8.0_60

macOS: 10.12-x86_64

Xcode: 8.0

CLT: 8.0.0.0.1.1472435881

X11: N/A

Issue 2:
When running compile_ios_protobuf.sh, it says:

checking whether we are cross compiling... configure: error: in '.../tensorflow/tensorflow/contrib/makefile/downloads/protobuf':

configure: error: cannot run C compiled programs.

If you meant to cross compile, use --host'. Seeconfig.log' for more details
Issue 1:
[c:/Program Files/Microsoft VS Code/resources/app/extensions/csharp-o]: Cannot read file c:/Program Files/Microsoft VS Code/resources/app/extensions/csharp-o/package.json: ENOENT: no such file or directory, open 'c:\Program Files\Microsoft VS Code\resources\app\extensions\csharp-o\package.json'

Issue 2:
Looking into repository, there is no longer folder named csharp-o.

I manually deleted the folder and restarted vscode and issue is gone. So, problem looks like installer not removing that file.
Issue 1:
There are several knobs in the plugins used by the fluentd setups, but none of them are exposed to users of the images. It would be great to have that, without requiring custom images: they're more work, tend to rot, etc.

I noticed that td-agent.conf supports an @ include directive. Would that work, along with drop-in files in e.g. /etc/td-agent/conf.d/? Is there a way perhaps to inject environment variables into configurations? I can help with PRs once there's agreement on which approach to choose.

cc @a-robinson @jimmidyson

Issue 2:
Kubernetes version: GitVersion:"v1.3.4+coreos.0", GitCommit:"be9bf3e842a90537e48361aded2872e389e902e7",

Environment:

Cloud provider or hardware configuration: AWS

OS (e.g. from /etc/os-release): CoreOS

Kernel: Linux ip-10-16-11-222.ec2.internal 4.6.3-coreos #2 SMP Fri Aug 5 04:51:16 UTC 2016 x86_64 Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz GenuineIntel GNU/Linux

Install tools: kube-aws

What happened:

I updated a deployment of a pod (a web server) to a version that crashes at runtime. The process still works, but any request will return 500. There is a readiness probe that checks if the server is up. The deployment has one replica, and maxUnavailable: 0, maxSurge: 1 rollingUpdate strategy. If I inspect the pods, I see two pods, the old one from the previous deployment, and the new one, both in Running status. After a while, the new one goes in CrashLoopBackOff Even though the new pod never gets healthy the rollout status says "deployment X successfully rolled out". This problem makes it very hard to identify bad deployments. It could be that this is the correct behavior for rollout status, but if it is, I don't know what's a good way to identify that a deployment is gone bad.

What you expected to happen:

I would expect rollout status to reflect the fact that the deployment didn't succeed. if I describe deployment X I get Replicas: 1 updated | 1 total | 1 available | 1 unavailable, I would also expect updated to be 0, unless I am not understanding correctly what that mean. The rollout status and the updated count are probably related.

How to reproduce it (as minimally and precisely as possible):

Updating a deployment to a new image that fails to pass the readiness probe
Issue 1:
Here's the warning message:

sklearn/externals/joblib/hashing.py:197: DeprecationWarning: Changing the shape of non-C
contiguous array by descriptor assignment is deprecated. To maintain the Fortran contiguity of a
multidimensional Fortran array, use 'a.T.view(...).T' instead
obj_bytes_view = obj.view(self.np.uint8)

The fix is already commited to the joblib repo, but it's not released yet.

I wasn't sure how you guys handle joblib updates, so I didn't create the pull request.

Issue 2:
I juste met a strange Deprecation warning on scikit-learn master:

sklearn/externals/joblib/hashing.py:197: DeprecationWarning: Changing the shape of non-C contiguous array by
descriptor assignment is deprecated. To maintain
the Fortran contiguity of a multidimensional Fortran
array, use 'a.T.view(...).T' instead
obj_bytes_view = obj.view(self.np.uint8)
Issue 1:
trait Hack: std::ops::Add<Self, Output = Self> + Copy {}
fn takes_hack(x: &Hack<Output=i32>) {}```
(which can't work of course)

Gives:
thread 'rustc' panicked at 'assertion failed: !ty.needs_infer()', ../src/librustc_typeck/lib.rs:152
on playpen's nightly and on an older nightly:
1: 0x7f2a73cac30e - sys::backtrace::write::h1e294cdf8b83f011srs
2: 0x7f2a73cb44d4 - panicking::on_panic::h759b2622c5bddde1mdx
3: 0x7f2a73c76ade - rt::unwind::begin_unwind_inner::hdb2ee52cd09f11c10Sw
4: 0x7f2a73415651 - rt::unwind::begin_unwind::h16407102452406535252
5: 0x7f2a73519747 - collect::convert_item::hee80771e2831a06bVHx
6: 0x7f2a735164c7 - collect::collect_item_types::hb25670e75e1ace20iPw
7: 0x7f2a735636c9 - check_crate::h699f9ca48d981e0dRWC
8: 0x7f2a74211cc9 - driver::phase_3_run_analysis_passes::closure.15891
9: 0x7f2a7421060b - middle::ty::ctxt<'tcx>::create_and_enter::h14877326799551551326
10: 0x7f2a7420b5b1 - driver::phase_3_run_analysis_passes::h13027946853248993312
11: 0x7f2a741ea80c - driver::compile_input::h1bb41626855952a5Tba
12: 0x7f2a742d0e83 - run_compiler::hed8febc643a5bd02A7b
13: 0x7f2a742ce85e - boxed::F.FnBox<A>::call_box::h3262743521461286850
14: 0x7f2a742ce0a9 - rt::unwind::try::try_fn::h13012207966773460524
15: 0x7f2a73d2f9d8 - rust_try_inner
16: 0x7f2a73d2f9c5 - rust_try
17: 0x7f2a73c9f647 - rt::unwind::try::inner_try::hcf9d4b2ce436da47TOw
18: 0x7f2a742ce2bb - boxed::F.FnBox<A>::call_box::h5485760352730305604
19: 0x7f2a73cb3131 - sys::thread::Thread::new::thread_start::h6bca3390d26c61e4GYv

Issue 2:
Code:

use std::ops::Add;

pub trait State: Add<Output=Self> {
fn new() -> State<Output=Self>;
}

Output:

thread 'rustc' panicked at 'assertion failed: !ty.needs_infer()', src/librustc_typeck/lib.rs:152

Backtrace:

stack backtrace:
1: 0x7f363e5e966e - sys::backtrace::write::ha67a6a2049d22fadIvs
2: 0x7f363e5f1d55 - panicking::on_panic::hfa4bf0215983f759lzx
3: 0x7f363e5b294e - rt::unwind::begin_unwind_inner::ha1b5da93bdf7e8ffC0w
4: 0x7f363dd48d91 - rt::unwind::begin_unwind::h12043835423437895913
5: 0x7f363de580e5 - collect::convert_method::h4805f8e025461365dEx
6: 0x7f363de466dd - collect::convert_item::h6b6cad92074d9a24CSx
7: 0x7f363de41407 - collect::collect_item_types::hd02205bf6b76e82bS0w
8: 0x7f363de8df39 - check_crate::h341139d405597625laD
9: 0x7f363eb4e199 - driver::phase_3_run_analysis_passes::closure.16542
10: 0x7f363eb4cab1 - middle::ty::ctxt<'tcx>::create_and_enter::h9578579149294230291
11: 0x7f363eb47991 - driver::phase_3_run_analysis_passes::h8415522514568150077
12: 0x7f363eb2ba90 - driver::compile_input::h52c7dafd49963360Tba
13: 0x7f363ec11a63 - run_compiler::h473c62e00f865fa9A7b
14: 0x7f363ec0f4de - boxed::F.FnBox<A>::call_box::h10713159552398332324
15: 0x7f363ec0ee09 - rt::unwind::try::try_fn::h16887904248528792425
16: 0x7f363e5f184d - __rust_try
17: 0x7f363e5dc8f7 - rt::unwind::try::inner_try::hafffff77ddacfa5fvWw
18: 0x7f363ec0f028 - boxed::F.FnBox<A>::call_box::h5417278073590676257
19: 0x7f363e5f0991 - sys::thread::Thread::new::thread_start::h29dca2a2cf2294b535v
20: 0x7f3638e904a3 - start_thread
21: 0x7f363e24e13c - clone
22: 0x0 - <unknown>

Version: 1.3.0
Issue 1:
Right-clicking on a line in search results will show a context menu, but it also navigates to the search result. I wasn't trying to leave the results, I was trying to figure out how to collapse some of them.

Atom Version: 0.48.0

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Atom/0.48.0 Atom-Shell/0.8.5 Safari/537.36

Issue 2:
When I right-click (or ctrl-click) on a file in the project search results, the contextual menu appears, but the interface also switches to a tab with that file buffer. This is frustrating when all I wanted to do was right-click to reveal in the file tree or some other contextual operation. Primary click should take me to the tab with that file buffer, not secondary click.
Issue 1:
The generated docs of typescript files don't show the type of class and interface members.

Issue 2:
Currently having an @Input on a directive / component with the same as a native property name will shadow input binding (that it, a directive will get the bound value, not the native element). Apparently different rules apply to @Outputs.

In this plunker https://plnkr.co/edit/TDCsPTWeRvgALildXmkt?p=preview there is a component with the change output. It turns out that adding (change) event handler to this component will pick up bubbling chnage events which I find surprising / inconsistent with rules in place for @Inputs.

I wonder if the the current behavior is correct and steams from the conscious design decision? Or rather a side effect of the existing implementation?
Issue 1:
The example codepen does not work. Looks like the openweathermap API needs a key to access.

http://www.openweathermap.org/api

The Javascript console says:

http://api.openweathermap.org/data/2.5/weather?lat=48.1270&lon=11.3665&units=metric&callback=jQuery2130876683295937255_1444809427340&_=1444809427342 Failed to load resource: the server responded with a status of 401 (Unauthorized)

Issue 2:
Our Weather Zipline example is now broken. Aparently the API @AdventureBear used on her Zipline no longer works. https://www.evernote.com/l/AlwSsfX2kblJYoOSp9uAq-BKFosOSCg8-aAB/image.png

We need to find an API that works and doesn't require adding an API key, or we need to make an API endpoint on Free Code Camp that campers can use (we don't want people exposing API keys on CodePen).

Thanks to @martoncsikos for spotting this issue.
Issue 1:
Steps to reproduce

Create a local JavaScript module file named /test-data.js: https://gist.githubusercontent.com/KSXGitHub/62cb052060dc169796ab3698ff53c33b/raw/9d7d84910b344eb8580be8b91cf539e18e565e5d/init.sh.

Execute deno run https://gist.githubusercontent.com/KSXGitHub/62cb052060dc169796ab3698ff53c33b/raw/9d7d84910b344eb8580be8b91cf539e18e565e5d/deno.js.

Resource: https://gist.github.com/KSXGitHub/62cb052060dc169796ab3698ff53c33b

Expected behavior

Error, just like in Chrome.

Actual behavior

It read data from local file and printed it.

Issue 2:
Issue 1:
Describe the bug

In version 0.19.1 my API worked for DELETE's against my .NET Core 3.1 API, but after upgrading to 0.20.0 this broke.

To Reproduce

My ts code:

public static async postDelete(payload: IAssetDeletionData): Promise<IAssetDeletionResult> {
const response = await (await getApi(this.apiBase)).delete('', {
data: payload
});
return response.data as IAssetDeletionResult;
}

Works with Axios 0.19.1 but not in 0.20.0.

I get a

{type: "https://tools.ietf.org/html/rfc7231#section-6.5.13", title: "Unsupported Media Type",…}

status: 415

title: "Unsupported Media Type"

traceId: "|3670a9cf-44c6c31efd70086d."

type: "https://tools.ietf.org/html/rfc7231#section-6.5.13"

Downgrading to 0.19.1...it works again.

Expected behavior

Expect still to work in 0.20.0 and be backwards compatible (as version is non-breaking according to NPM semantic versioning)

Environment

Axios Version 0.20.0

Browser Chrome

Browser Version 84.0.4147.135

Node.js Version 12.8.0

OS: Windows 10 2004

Additional Library Versions [e.g. VueJS 2.6.12, Vuetify 2.3.9, Firebase 7.19.0 etc.

Additional context/Screenshots

N/A

Issue 2:
Describe the bug

Axios last version (0.20.0) does not use data from config when making DELETE request. In 0.19.2 it's working fine

To Reproduce

axios.delete("...", {
data: { ids: [...] },
}).then(response => {
...
}).catch(error => {
...
});

Expected behavior

Axios send request data from config when making DELETE request

Environment

Axios Version 0.20.0

Browser Chrome

Browser Version 84.0.4147.125

Node.js Version 12.18.3

OS: Linux Mint

Additional Library Versions React 16.13.1

Additional context/Screenshots

None
Issue 1:
What problem does this feature solve?

Currently, you can set a true value on a prop by simply using the prop's name (i.e. <input readonly...>), but there is no equivalence for setting false values (i.e. <input :readonly="false">).

In most cases (like above), false is already the default value, but there are still many instances where a prop's default is true and must be overridden. The API is cumbersome in those instances.

What does the proposed API look like?

I'm proposing a simple, in-template, "false-assertion" shorthand that could significantly improve the Vue developer experience. The "false-assertion" operator would explicitly set props to false.

Current API

<input :readonly="false"/>

Proposed API

<input !readonly/>

Issue 2:
What problem does this feature solve?

There's already a nice shorthand for true props where you just add the prop name on its own, however there isn't an equivilent shorthand for false props. Below are a couple suggestions for that shorthand that would make writing/reading these props easier I think. It's a pretty minor feature request, but I think it would add to the already amazing developer experience of using Vue.

What does the proposed API look like?

<component !prevent /> translates to <component :prevent="false" />

<component :not-prevent /> translates to <component :prevent="false" />
Issue 1:
If you're coming from numpy you're used to be able to index and assign into arrays in the usual way.

Issue 2:
We should make our slicing and assignment ops more general to capture more of the functionality of numpy slicing, and add __getitem__ sugar for all of it. Specifically,

We should have a 2.5 dimensional set of ops, with dimensions (1) get vs. set, (2) slice type, and for the assignment ops (3) the update op. Currently we have slice, assign_update, assign_add, assign_sub, gather, scatter_update, scatter_add, scatter_sub. We should also have assign_slice_update, assign_slice_add, assign_slice_sub.

Both slicing and slice assignment should support strides, with no performance cost if strides aren't used.

Ideally, the slice ops should support negative indexing a la Python. Since the slice parameters are already CPU, this is implementable with near zero cost. The unfortunate bit is that since we picked the wrong format for specifying ranges (start + length instead of start : end), negative indexing might be awkward. Thus, it might be best left to a separate bug.

Support numpy-like boolean indexing.

Generalize gather and scatter_* to take an array of input index tensors, efficiently broadcast them, and do multidimensional indexing similar to numpy.

Make __getitem__ provide sugar for all of the above. Ideally we'd have something idiomatically similar at least to __setitem__, but this is problematic since the returned assignment op is important to have, __setitem__ does not return a value, and the nice range sugar is available only inside indexing / assignment calls.

@ebrevdo: I'm assigning this to you for now since you might get to it first, but feel free to grab only the piece of it that you need for now.
Issue 1:
Fork of #3810 and #3799. Decimal intervals would be useful for certain data types such as currencies, temperatures, lengths ...

Issue 2:
It would be really useful to allow for a 'grace period' between when ES notices that a particular node has gone down, and shard-reallocation begins. There are times when we might want to do a quick restart of an ES node ... or take one down for a full reboot ... and we don't want to do a re-allocation of shards because thats a very IO-intensive operation. In our case, we also use the Zookeeper plugin, and a shard-reallocation is triggered by a short communication break between the ES nodes and Zookeeper.
Issue 1:
It was okay in previous Go versions.

package main

import "fmt"

func main() {
var c rune
n, e := fmt.Sscanf("\n", "%c", &c)
fmt.Println(n, e)
// Go 1.5: 0 unexpected newline
// Go 1.2, 1.3, 1.4: 1 <nil>
}

Issue 2:
What version of Go are you using (go version)?

I found this when upgrading from Go 1.3.3 to Go 1.5

What operating system and processor architecture are you using?

GOARCH="amd64"
GOOS="linux"

What did you do?

$ cat scango.go

package main

import "fmt"

func main() {
var x int

n, err := fmt.Sscanf("A", "%c", &x)
println("n=", n, "x=", x, "err=", err)

n, err = fmt.Sscanf(" A", "%c", &x)
println("n=", n, "x=", x, "err=", err)

n, err = fmt.Sscanf(" ", "%c", &x)
println("n=", n, "x=", x, "err=", err)
}

What did you expect to see?

I expected what Go 1.3.3 did: it always gets the first character in the scanned string, either "A" or " ":

$ go run scango.go

n= 1 x= 65 err= (0x0,0x0)

n= 1 x= 32 err= (0x0,0x0)

n= 1 x= 32 err= (0x0,0x0)

That's also what my C compiler does

/* gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) */

$ cat scanc.c

#include <stdio.h>

main() {
char x[33];
int n = sscanf("A", "%c", x);
printf("n=%d <%d>\n", n, *x);
n = sscanf(" A", "%c", x);
printf("n=%d <%d>\n", n, *x);
n = sscanf(" ", "%c", x);
printf("n=%d <%d>\n", n, *x);
}

$ gcc scanc.c

$ ./a.out

n=1 <65>

n=1 <32>

n=1 <32>

What did you see instead?

Under Go 1.5, it skips the blank, and advances to the "A" (in the second clause) or EOF (in the third clause):

$ go run scango.go

n= 1 x= 65 err= (0x0,0x0)

n= 1 x= 65 err= (0x0,0x0)

n= 0 x= 65 err= (0x7f555757b028,0xc82000a1d0)
Issue 1:
Describe the workflow you want to enable

Linear and logistic regression allow l1, l2, or elasticnet regularization. However, the Poisson regression class (which is amazing to have!) only allows L2 regularization.

Describe your proposed solution

Enable flexible regularization choices for the Generalized Linear Models

Describe alternatives you've considered, if relevant

No response

Additional context

No response

Issue 2:
The L1 penalty with coordinate descent solver for GLM was proposed in #9405 and was not included in the minimal implementation merged in #14300.

It would be be good to add it, however care must to taken to avoid redundancy with the existing coordinate descent solver in ElasticNet.

Preliminary benchmarks were done in #9405 (comment)

Also see: #16634 #16635
Issue 1:
VSCode Version: 0.10.12-alpha

OS Version: OSX

#4022

Steps to Reproduce:

open a new file, add a workspace setting to enable javascript validation "javascript.validate.enable": false

in the file type:

var str = "qrqweqwewqe";
str.test();

Expected: error under test since test method is not defined on a string.

Issue 2:
See #6658 for background.

Currently for JavaScript files we provide a very limited set of errors, mostly for syntax errors. There are a number of grammatical and type errors that would be useful to display also.

Brief notes from ad hoc discussion in the team room include:

Move the code that flags TypeScript syntax in JavaScript files for better error handling

Add a distinction between errors and warnings to avoid "valid" JavaScript containing errors

Make the warnings user configurable as part of the project (i.e. may enable/disable certain warnings)

More detailed design to come...