WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
This is how I broke our build.

% pwd
/home/rog/src/go/src/local/gobug
% ls
% cat > foo.go
package foo
var X = 0
^D
% cat > bar.go
package foo
var Y = 0
^D
% cat > foo_test.go
package foo_test
import (
"testing"
foo "local/gobug"
)
func TestX(t *testing.T){
_ = foo.X
}
^D
% go test
PASS
ok local/gobug 0.011s
% go install
% rm foo.go # as it happens, i actually moved it elsewhere.
% go build
% go install
% go test
PASS
ok local/gobug 0.011s
# everything looks just fine, so i pushed to trunk here, breaking
# the build.
% touch *.go
% go test
# local/gobug_test
./foo_test.go:7: undefined: foo.X
FAIL local/gobug [build failed]
%

I wonder if the go tool should look at the mtime of the
directory as well as the source files when determining
whether to rebuild.

Issue 2:
What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. hg pull ;hg update;hg id

gobuild@raspberrypi:~/go/src$ hg id
5e3661048f2e+ tip
gobuild@raspberrypi:~/go/src$

2. check GOARM setting.
gobuild@raspberrypi:~/go/src$ echo $GOARM

gobuild@raspberrypi:~/go/src$

3. cd src;./all.bash

What is the expected output?

No errors.

What do you see instead?

two test errors, fmt and eoncoding/gob(this is logged in another ticket).

ok flag 0.120s
--- FAIL: TestNaN (0.00 seconds)
scan_test.go:459: didn't get NaNs scanning "nan nan nan": got NaN +Inf NaN
scan_test.go:459: didn't get NaNs scanning "NAN NAN NAN": got NaN +Inf NaN
scan_test.go:459: didn't get NaNs scanning "NaN NaN NaN": got NaN +Inf NaN
FAIL
FAIL fmt 0.876s
ok go/ast 0.171s

Which operating system are you using?

gobuild@raspberrypi:~/go/src$ uname -a
Linux raspberrypi 3.1.9+ #90 Wed Apr 18 18:23:05 BST 2012 armv6l GNU/Linux
gobuild@raspberrypi:~/go/src$

Which version are you using? (run 'go version')

gobuild@raspberrypi:~/go/src$ go version
go version weekly.2012-03-27 +5e3661048f2e
gobuild@raspberrypi:~/go/src$

Please provide any addgobuild@raspberrypi:~/go/src$ hg id
5e3661048f2e+ tip
gobuild@raspberrypi:~/go/src$
itional information below.
Issue 1:
Migrated issue, originally created by Michael Bayer (@zzzeek)

re: the "creator" function.

see #647 #2808 #3235 for what keeps coming up.

Issue 2:
Migrated issue, originally created by Sorin Sbarnea (@sorin)

Instead of hardcoding the backend engine to use for postgresql, sql alchemy should try to use pg8000 if the native module is not present.
Issue 1:
Several of the types in the Iterators package are widely useful, plus have very small implementations that perform well. I would say these are: Count, Take, Drop, Cycle, Repeat, and RepeatForever. It would make sense to have these in Base.

Also, iterators are afflicted by a mild case of "lettercase hell". We export both Enumerate and enumerate, etc. I would prefer to minimize the number of exported things that differ only in case. There are a few ways to deal with this:

Remove the lowercase versions entirely, and stick with the "uppercase means lazy" convention.

Rename the uppercase versions to something less appealing like EnumerateIterator so they are less easily confused.

Un-export (and possibly rename as well) the uppercase versions.

Issue 2:
Mutually recursive type declarations such as

type A
a :: B
b
end

type B
c :: A
d
end

appear to be presently unsupported, as per this discussion:

https://groups.google.com/forum/#!msg/julia-users/LctRzct1R-M/s_vLVUxSyVcJ

More generally, "out of order" type declarations also appear to be unsupported.

Mutually recursive declarations are important for many recursive data structures: in complex cases, the workarounds required to produce singly recursive declarations can produce highly unreadable code with excessive redundancy and obscure relationships to the original concept.

"Out of order" declarations are important for some forms of generic programming that depend on altering a subset of type definitions: in complex cases, the workarounds required to organize the inclusions in ordered form defeat much of the purpose of avoiding the unnecessary code duplication.

I believe this issue is already well known, but I did not find an open issue on Github, which prevents easily checking its status.
Issue 1:
Description of the new enhancement

Currently windows terminal does not support vim (vim for windows) completely. When vim is launched from the windows terminal, the document opens fine and all of the vim features are available. The only issue is that the rendering of the document is with blue color as opposed to normal terminal background-color (say black)

Due to the improper rendering, the syntax highlighting feature of vim no longer works.

When vim is launched from the terminal it should respect .vimrc file of the user.

It will be helpful if I can use vim in the windows terminal directly :)

A clear and concise description of what the problem is that the new enhancement would solve.

Describe why and how a user would use this new functionality (if applicable).

It would be really helpful if I can use vim for windows on the windows terminal. Ever since the new terminal was announced I was looking forward to using vim on it. Currently, I use vim software for windows.

A clear and concise description of what you want to happen.

It would be useful if something close to below happens:

Issue 2:
I just installed Windows Terminal for the first time this morning and the first thing I noticed -- before trying to make ANY changes to settings or even using the command lines -- was the semi-transparent background in the CMD tabs. I think it looks neat, but I am confused about why it is transparent when the terminal window is in use but becomes solid when the terminal window loses focus?

It would seem to make much more sense with those states reversed as it is much easier to read text on a single, solid background color and it may be useful to have an idea what is behind the inactive terminal window.

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.239]
Windows Terminal version (if applicable): 0.3.2171.0

Any other software? no

Steps to reproduce

Open a CMD tab and focus then unfocus the terminal window to see the background opacity change.

Expected behavior

My preference would be for solid when in use and some transparency when inactive. Or at least, I would like an option to choose that mode.

Actual behavior

The CMD tab is semi-transparent when in use and becomes solid when inactive.
Issue 1:
The get started part has a section MNIST for ML Beginners. In this tutorial you should download the test data via:

from tensorflow.examples.tutorials.mnist import input_data

mnist = input_data.read_data_sets("MNIST_data/", one_hot=True)

Unfortunately that's not working because of an connection error.

Issue 2:
I was able to run the Inception-v3 model on Android just fine, and I now want to run my own trained TensorFlow model on Android. I'm following the approach from TensorFlow's image recognition tutorial and the Android TensorFlow demo, and adapting as necessary. My changes include: (a) integrating Android OpenCV as part of the bazel build (b) using own model and label file and (c) adjusting parameters (img_size, input_mean, input_std, etc.) accordingly.

From Android logcat, running my model with the tensorflow android demo app gives:

E/native: tensorflow_inference_jni.cc:202 Error during inference: Invalid argument: Session was not created with a graph before Run()!
...
E/native: tensorflow_inference_jni.cc:159 Output [output/Softmax:0] not found, aborting!

What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?

Own (duplicate) SO thread: http://stackoverflow.com/questions/40555749/running-own-tensorflow-model-on-android-gives-native-inference-error-session-w

Environment info

OS X Yosemite (10.10.5), LGE Nexus 5 (Android 6.0.1), Android SDK 23, Android OpenCV SDK 23, Bazel 0.4.0.

Steps taken

Saved own model's checkpoint (.ckpt) and graph definition (.pb) files separately using tf.train.Saver() then tf.train.write_graph()

Froze graph using freeze_graph.py (using bazel), gives 227.5 MB file

Optimized the graph using optimize_for_inference.py (additionally tried strip_unused.py)

Copied frozen, optimized, or stripped graph to android/assets

Doubled the total byte limit using coded_stream.SetTotalBytesLimit() in jni_utils.cc to handle my large model size

Built the tensorflow android app using bazel

Installed on android device using adb and bazel

As a sanity check, I have tested my model in C++ built with bazel following the tutorial here label_image, and my model correctly outputs a prediction. I have also tried playing with the order by which I save my graph def and checkpoint files before freezing, but no change.

Any help would be great.

cc @drpngx @andrewharp
Issue 1:
I'm submitting a ... (check one with "x")

[x] bug report
[ ] feature request
[ ] support request

Current behavior

When a web component is used inside an Angular component, attributes specified on web component are not available inside attachedCallback of web component. Also, when an attribute value for a web component is specified using an interpolation operator value="{{value}}", Angular changes attribute name with a ng-reflect- prefix and manages it internally. Because of this there is no way attributeChangedCallback could trigger appropriately.

Expected behavior

There should be a way to use web component inside Angular component in a way such that attributes are available inside attachedCallback and attributeChangedCallback is triggered correctly for appropriate attributes.

Minimal reproduction of the problem with instructions

This shows a sample Toggle Button web component used inside Angular component.

https://plnkr.co/edit/MwLh8ssnjOdqA8C4PhZq?p=preview

Please tell us about your environment:

Angular version: 2.0.X

Browser: [Chrome]

Language: [ES6]

Issue 2:
I'm submitting a ... (check one with "x")

[x] bug report
[ ] feature request
[ ] support request

Current behavior

I'm trying to integrate ChartIQ library which has HTML Custom Elements to my angular 2 application.

Some of these elements have logic in createdCallback, but when it is firing innerHTML of Custom element is empty.

Expected behavior

If I use Custom Elements without Angular, createdCallback is firing when the full element (with all childrens added into it) inserted into DOM.

Minimal reproduction of the problem with instructions

http://plnkr.co/edit/OW500u9fr27aVteo3zJh

What is the motivation / use case for changing the behavior?

For now Angular 2 breaks some part of expected behavior of Custom Elements. It needs to be fixed to allow using Custom Elements in Angular apps.

Please tell us about your environment:

Windows 8, WebStorm, npm

Angular version:

2.2.1

Browser:

Chrome 55

Language:

all

Node (for AoT issues): node --version =

6.7.0
Issue 1:
The code completion functionality often gets in the way when typing prose into a text file. For example, if I were writing this comment in a .txt file with VS Code and tried to type the word fun immediately followed by the Enter key, I'd automatically have the word "functionality" instead, because Code "learned" from the first sentence above that "fun" might be the beginning of "functionality."

It's great that this is apparently turned off by default in Markdown files. Can the same default be applied to .txt files? It's unlikely that any useful word-completion heuristic can be deduced from the content of most text files.

Issue 2:
At the moment when none of the contributed completion processors returns any proposals, the textual completion processor starts adding proposals.

That's fine for languages where we have no sophisticated completion processor, but looks bad for languages that pretend to have a 'smart' completion processor.
Issue 1:
On current master (on macOS), I get these warnings when building Julia. I suppose they are safe to ignore.

LINK usr/lib/julia/sys.dylib
ld: warning: could not create compact unwind for _julia_Dict_17462: stack subq instruction is too different from dwarf stack size
ld: warning: could not create compact unwind for _julia_Dict_17470: stack subq instruction is too different from dwarf stack size
➜ julia git:(master) ./julia
_
_ _ _(_)_ | Documentation: https://docs.julialang.org
(_) | (_) (_) |
_ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
| | | | | | |/ _` | |
| | |_| | | | (_| | | Version 1.8.0-DEV.86 (2021-06-28)
_/ |\__'_|_|_|\__'_| | Commit 74fab49ffb (0 days old master)
|__/ |

Issue 2:
On macOS 10.14.6, I've started to get these warning when building Julia, at the very end:

$ make
...
LINK usr/lib/julia/sys.dylib
ld: warning: could not create compact unwind for _julia_Dict_16937: stack subq instruction is too different from dwarf stack size
ld: warning: could not create compact unwind for _julia_Dict_16945: stack subq instruction is too different from dwarf stack size
$

This also happens in the release-1.7 branch, but not in release-1.6, and also didn't happen like a month or so ago.
Issue 1:
Please add support for selecting multiple images at once using the image_picker plugin.

Issue 2:
Right now the picker defaults to single mode, it would be nice to be able to have a multi-mode, by passing a parameter when you launch it, then an array is returned of files instead of just one.

for android this might help speed things up

unique code

intent.putExtra(Intent.EXTRA_ALLOW_MULTIPLE, true);

full example

Intent intent = new Intent();
intent.setType("image/*");
intent.putExtra(Intent.EXTRA_ALLOW_MULTIPLE, true);
intent.setAction(Intent.ACTION_GET_CONTENT);
startActivityForResult(Intent.createChooser(intent,"Select Picture"), 1);

for iOS I think maybe using this library might help, and seems up to date.

https://github.com/hackiftekhar/IQMediaPickerController
Issue 1:
Describe the issue:

Hi,

I have recently created a new python environment using the 3.10.4 python version.

I have installed the latest public version (1.22.3) and when I am trying to catch the epsilon, I have an error that cannot allow me to use the command: numpy.finfo(float).eps or numpy.finfo(numpy.float32).eps

This can be very inconvenient because I hwill use some solutions of Scikit-Learn that calls this.

Sorry for the inconvenience. Best.

Reproduce the code example:

import numpy as np
eps = np.finfo(float).eps

Error message:

Traceback (most recent call last):**

File "C:\Users\ME\2022_deepl\lib\site-packages\numpy\core\getlimits.py", line 459, in __new__
dtype = numeric.dtype(dtype)

TypeError: 'numpy.dtype[bool_]' object is not callable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "C:\Users\ME\AppData\Local\Temp\ipykernel_10948\2225752278.py", line 1, in <cell line: 1>
np.finfo(float).eps

File "C:\Users\ME\2022_deepl\lib\site-packages\numpy\core\getlimits.py", line 462, in __new__
dtype = numeric.dtype(type(dtype))

TypeError: 'numpy.dtype[bool_]' object is not callable

NumPy/Python version information:

1.22.3 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)]

Issue 2:
Ravel and unravel are synonyms, but the methods where they appear accomplish inverse operations.

See my SO question for details and example.

Can you consider introducing alternative methods that contain unravel in their name (even functions containing ravel are IMHO not a happy choice)?

I propose to change e.g.

before
after

unravel_index()
index_to_coord()

ravel_multi_index()
index_to_flat
Issue 1:
I believe this is a bug, or if it isn't, I couldn't find anything in the documentation that says it should act this way.

It seems like random.choice is ignoring the masked values. As you can see in the code below, the output of random.choice gives values that have been previously masked on the array.

Reproducing code example:

import numpy as np
x = np.linspace(0,100,100)
xmask = np.ma.masked_where(x>75,x)
print(np.nanmax(xmask))

random_choice = np.random.choice(xmask,50)
print(np.nanmax(random_choice))

Output:

74.74747474747475

96.96969696969697

I've tried this several times, and the maximum value of random_choice always seems to be between 90 and 100.

Numpy/Python version information:

1.18.1 3.7.6 (default, Jan 8 2020, 19:59:22)

[GCC 7.3.0]

Issue 2:
The subject says it all, but in case you missed it: the function numpy.show_config() (an alias for numpy.__config__.show()) doesn't have a docstring, and it does not appear in the online docs.

A docstring that explains the information printed by show_config() would be helpful.
Issue 1:
1. What is a short input program that triggers the error?

(compile with -race enabled)

package pdl

var (
codec1 = codec{newE, "application/pdf"}
codec2 = codec{newE, "text/plain"}

availableCodecs = [...]codec{codec1, codec2}
)

type encoder interface{}

type codec struct {
NewWriter func() encoder
MimeType string
}

type E struct{}

func newE() encoder { return new(E) }

2. What is the full compiler output?

./y.go:7: internal compiler error: found non-orig name node availableCodecs

3. What version of the compiler are you using? (Run it with the -V flag.)

go version go1.3beta2 +e165495e81bf Fri May 23 12:29:29 2014 +1000 linux/amd64

Issue 2:
What steps will reproduce the problem?
1. Set your $INCLUDE environment variable to be longer than 500 characters.
2. Try to assemble any .s file. (I've been using
$GOROOT/src/pkg/runtime/$GOARCH/asm.s)
3. Get a segmentation fault.

I've reproduced with both 6a and 8a. I'm assuming 5a does the same thing.

Which revision are you using? (hg identify)
4d7f5eddd695 tip

The problem is due to a buffer overflow in macinc cc/macbody. symb is an
array of 500 characters and it's filled using strcpy without checking the
length of the source. $INCLUDE happens to be one of these sources and it's
easier than you might think to exceed 500 characters -- particularly in cygwin.

There might be other buffer overflows possible in this file through similar
means. There are a number of strcpy calls.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.8-SNAPSHOT

Operating System version: MacOS

Java version: oraclejdk1.8

Steps to reproduce this issue

xxx

xxx

xxx

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!

I will submit a pr.

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.6.9

Operating System version: centos 6.4

Java version: 1.8

Steps to reproduce this issue

dubbo服务端口20880，服务启动成功。

执行如下命令：

[root@serv87 ~]# telnet 192.168.128.187 20880

Trying 192.168.128.187...

Connected to 192.168.128.187.

Escape character is '^]'.

status -l

+------------+--------+--------------------------------------------------------+

| resource | status | message |

+------------+--------+--------------------------------------------------------+

| threadpool | OK | Pool status:OK, max:200, core:200, largest:19, active:1, task:19, service port: 20880 |

| load | OK | load:0.51,cpu:8 |

| memory | OK | max:1969M,total:1969M,used:289M,free:1680M |

| registry | OK | 192.168.128.187:2880(connected) |

| server | OK | /192.168.128.187:20880(clients:13) |

| spring | OK | classpath*:spring-config/*.xml |

| summary | OK | |

+------------+--------+--------------------------------------------------------+

显示dubbo服务信息，客户安全扫描认为不安全

请问，如何解决这个问题？
Issue 1:
This is related to #2461. Essentially if we wrap a render call in a try catch this works the first time. It seems like when React.render is called a second time (the update case) it does not work. It seems that React.render is async when updating an existing component tree.

I may be missing something but it seems like this leaves no way for developers to catch errors when rendering children components.

I have a JSBin demoing this issue here: http://jsbin.com/mifedepada/edit?js,console,output

Issue 2:
So I'm trying to put some graceful error handling in case 1 of my views crap out:

var MyGoodView = React.createClass({
render: function () {
return <p>Cool</p>;
}
});

var MyBadView = React.createClass({
render: function () {
throw new Error('crap');
}
});

try {
React.render(<MyBadView/>, document.body);
} catch (e) {
React.render(<MyGoodView/>, document.body);
}

However, MyGoodView does not get rendered w/ the following stack trace:

Seems like error throw React in a bad state where renderedComponent is undefined, thus cannot be unmounted. How do I handle this scenario?
Issue 1:
The docs pages for Send and Sync show duplicated and incorrect items in the "Implementors" section.

Specifically, an incorrect positive impl for Rc is present and the correct negative impl is present twice.

Also, impls for Arc and ArcInner appear multiple times, with and without trait bounds and where clauses, with Arc having three appearances:

impl<T> Send for Arc<T> where T: Send + Sync
impl<T: Sync + Send> Send for Arc<T>
impl<T> Send for Arc<T>

Issue 2:
Issue

I noticed with a few of my crates that I have some redundancies between my docs and the code in the crate, specifically testcases. As a example, here nice_example() is duplicated:

//! docs docs docs
//! docs docs docs
//! ```
//! fn nice_example() { ... }
//! ```

...

#[test]
fn nice_example() { ... }

Now, there are right now two ways to deal with this:

Keep both copies

Con: redundant copies, code can start drifting apart unintentionally.

Pro: If docs and tests diverge intentional, no additional work is needed.

Remove the separate unit test copy of the code.

Pro: The docs will get tested anyway

Pro: No redundancy

Con: Unit tests get split between two locations

Con: Unit tests start mixing with documentation, a change to either might cause changes to both and/or moving the unit test code back and forth between the docs and the crate.

As an additional issue, having rust code in doc comments be highlighted as rust code is kinda complicated - or at least not implemented in most highlighters.

Proposal

Have a way in doc comments to "include" the source code of an item in the documented crate, eg:

//! docs docs docs
//! docs docs docs
//! ```
//! #rustdoc_include self::nice_example
//! ```

...

#[test]
fn nice_example() { ... }

Pro: Only one copy of the actual code

Pro: No redundancy

Pro: Unit tests can be kept separate from the docs, even if they are nicely documented and used as example code in them.

Pro: If the docs don't want to use that particular code example anymore, only the reference needs

to be deleted, and a nicely commented unit test remains.

The one copy of the code is outside doc comments, and thus will get highlighted correctly.

Con: More machinery for rustdoc to support

Con: Harder to read and write the documentation directly in the source.