WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.18945.1001]
Windows Terminal version (if applicable): 0.3.2142.0

Any other software?

Steps to reproduce

Run Windows Terminal as an administrator.

Expected behavior

The program's name should show up correctly in the UAC prompt.

Actual behavior

The UAC prompt calls it "Unknown program" rather than "Windows Terminal". However, it's detected as a signed application and the icon is shown correctly.

Issue 2:
Environment

Windows build number: 10.0.18362.175

Windows Terminal: built from master af1a4dd

Steps to reproduce

In a powershell window, execute the command Get-Credential

Expected behavior

The credential dialog should open and be interactive; I should be able to enter inputs and close the dialog.

Actual behavior

The credential dialog appears and can be dragged around, but no buttons or input fields on it are responsive. It also blocks the rest of the terminal, requiring me to kill and restart the entire terminal.

This happens even when launching terminal as admin.

Other GUI dialogs (Show-Command) work as expected, but I haven't tried with any other blocking dialogs.
Issue 1:
type a struct {
B struct{}
}

func (a) C() {}

type D struct {
a
}

godoc will show C, but not B. B is accessible, comes up with various auto-complete tools etc.

Issue 2:
Within my code, I have the following structure.

type common struct {
Option1 bool
}

func (c *common) Method1() {
}

type A struct {
OptionA int
common
}

type B struct {
OptionB int
common
}

I want godoc to show that type A and type B have field Option1 available, and Method1 in
their method sets.

However, godoc would not show Option1, because common is not exported. It however show
Method1 (the full method set).

The only current workaround is to export common (which really is an internal
implementation detail), or duplicate the functionality across all types that share it.

TO fix, godoc should show these promoted fields got from unexported anonymous fields.

For example, godoc output for A could look like:

type A struct {
OptionA int
// contains filtered or unexported fields
// Available from unexported anonymous fields
Option1 bool
}

Which version are you using? (run 'go version')
go version devel +47b2b07a837f Fri Oct 11 16:39:40 2013 -0700 linux/amd64

Please provide any additional information below.
Issue 1:
go version devel +f74ea6c Tue Jun 16 01:04:10 2015 +0000 windows/amd64

func funA(a0, a1, b0, b1 uint32) uint32 {
return ((a0&0x12345678)>>2 + (a1&0x12345678)>>3 + (b0&0x12345678)>>4 + (b1&0x12345678)>>5) +
((((a0 & 0x87654321) + (a1 & 0x87654321) + (b0 & 0x87654321) + (b1 & 0x87654321) + 0) >> 7) & 0x87654321)
}

func funB(a0, a1, b0, b1 uint32) uint32 {
const mask0, mask1 = 0x12345678, 0x87654321
return ((a0&mask0)>>2 + (a1&mask0)>>3 + (b0&mask0)>>4 + (b1&mask0)>>5) +
((((a0 & mask1) + (a1 & mask1) + (b0 & mask1) + (b1 & mask1) + 0) >> 7) & mask1)
}

func BenchmarkA(b *testing.B) {
for i := 0; i < b.N; i++ {
for i := 0; i < (1 << 20); i++ {
funA(1, 2, 3, 4)
}
}
}

func BenchmarkB(b *testing.B) {
for i := 0; i < b.N; i++ {
for i := 0; i < (1 << 20); i++ {
funB(1, 2, 3, 4)
}
}
}

BenchmarkA-4 500 3828382 ns/op
BenchmarkB-4 300 5467213 ns/op

Issue 2:
The perf builders don't benchmark older commits:
http://build.golang.org/perf?page=100
and perf-todo requests from builders fail:
2014/10/14 12:54:05 datastore: query has no more results
2014/10/14 12:55:04 datastore: query has no more results
2014/10/14 12:55:34 datastore: query has no more results
2014/10/14 12:56:04 datastore: query has no more results
2014/10/14 12:56:35 datastore: query has no more results

Looking at the symptoms it seems that Commit.Num's were manually updated, so that now
(1) PerfTodo entities contain invalid nums and (2) association between Commits and
CommitRun's is broken and (3) Commit nums jumped to 100'000, which created a huge hole
in CommitRun's which negatively affects the graphs UI (one could argue that benchmark
commits contain holes due to branches anyway, but small holes are OK and 100'000 is like
25 years of team's activity).

All these 3 points need to be repaired.
Issue 1:
Please:

Check for duplicate issues.

Provide a complete example of how to reproduce the bug, wrapped in triple backticks like this:

>>> import os
>>> os.environ["XLA_FLAGS"] = '--xla_force_host_platform_device_count=8'
>>> import jax
>>> jax.devices("cpu")
[CpuDevice(id=0), CpuDevice(id=1), CpuDevice(id=2), CpuDevice(id=3), CpuDevice(id=4), CpuDevice(id=5), CpuDevice(id=6), CpuDevice(id=7)]

But the following approaches don't work

>>> import os
>>> import jax
>>> jax.devices("cpu")
[CpuDevice(id=0)]
>>> os.environ["XLA_FLAGS"] = "--xla_force_host_platform_device_count=8"
>>> jax.devices("cpu")
[CpuDevice(id=0)]

>>> import os
>>> import jax
>>> from jax.lib import xla_bridge
>>> jax.devices("cpu")
[CpuDevice(id=0)]
>>> os.environ["XLA_FLAGS"] = "--xla_force_host_platform_device_count=8"
>>> xla_bridge.get_backend.cache_clear()
>>> jax.devices("cpu")
[CpuDevice(id=0)]

If applicable, include full error messages/tracebacks.

Issue 2:
MyPy says that jax.interpreters.xla.DeviceArray has no attribute "shape", is not indexable, etc. It seems that it points to DeviceArrayBase—not DeviceArray, which has the annotations.

I know that type annotations are a work-in-progress. This is just a placeholder issue :)
Issue 1:
Environment

Windows build number: Microsoft Windows [versão 10.0.18362.175]

Windows Terminal version (if applicable): Preview 0.2.1715.0

Steps to reproduce

Open Terminal.

Left click over title bar, left side of plus sing. (Between title of open tab and plus sign)

Try to move window.

Expected behavior

After click, windows should moved.

Actual behavior

Nothing is happing.

Issue 2:
I think its really nice that you can put the terminal-tabs in your titlebar but I got an issue there.

You can't move the window around klicking on the blank space in the the-bar to move the window around (highlighted in the screenshot).

Since people are moving their terminal quite often it would be nice to offer this space, so you can drag your terminal around.
Issue 1:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.4.8

Today i upgraded from Symfony 3.4.6 to 3.4.8 and the automatic redirect to website.test/login stopped working when hitting the homepage ( website.test ) as anonymous user using FOSUserBundle. All I see is welcome to Symfony 3.4.8

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
yes

RFC?
no

Symfony version
3.2.3

After upgrading to symfony 3.2.3 the annotations are not being read from the cache but always parsed from the real classes.

This decreases the performance of our functional tests drastically, don't know how it affects the real application because I have no benchmarks.

Seems like the Doctrine\Common\Annotations\CachedReader doesn't get initialized.

I found out that this is caused by the following change in the FrameworkExtension.php line 1046

v3.2.2...v3.2.3#diff-0e793081ceb720201745c982a568903fL1046

which comes from #21381

If I restore the line or if I put $container->setAlias('annotation_reader', 'annotations.cached_reader'); im my own AppBundle, an instance of Doctrine\Common\Annotations\CachedReader gets created and used as expected.

My config.yml looks like this:

framework:
test: ~
profiler:
collect: true
secret: "secret"
router:
resource: "%kernel.root_dir%/config/routing.yml"
strict_requirements: ~
templating:
engines: ['twig']
form: ~
csrf_protection: ~
validation: { enable_annotations: true }
default_locale: "%locale%"
trusted_hosts: ~
trusted_proxies: ~
session:
storage_id: session.storage.mock_file
fragments: ~
http_method_override: true

How to deal with this?
Issue 1:
ℹ Computer information

PowerToys version: v0.22.0

PowerToy Utility: FancyZones

Running PowerToys as Admin: Yes

Windows build number: [run "winver"] - Windows 10

📝 Provide detailed reproduction steps (if any)

… Opened PowerToys Setting

… Clicked on FancyZones Tab

… Launched Zones Editor

4... Selected Grid

5..When Holding "Shift" key and dragging the windows it does not any allow me to display into grid.

Note: Every time I select different template and apply it always goes back to by default on "Focus" template

✔️ Expected result

_What is the expected result of the above steps? It should've allowed my to hold the "Shift" key and apply drag screens into the grid template.

❌ Actual result

The selected templates other than focus not being Applied even though I did click on "Apply" button.

What is the actual result of the above steps?

📷 Screenshots

Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form

Issue 2:
ℹ Computer information

PowerToys version: v0.21.1

PowerToy Utility: FancyZones

Running PowerToys as Admin: No

Windows build number: Windows 10 Version 2004: 19041.450

📝 Provide detailed reproduction steps (if any)

Check the Allow zones to span across monitors checkbox

Configure a zone which uses multiple monitors via the Launch zones editor and Apply

Attempt to snap window to zones, or use Shift key to highlight zones while dragging

✔️ Expected result

A window should snap to a zone

Zone highlighting ought to be functional

The Allow zones to span across monitors setting should persist even when closing settings

If there are errors "Activating" the zones, these should be raised to the user

❌ Actual result

A window will not snap to a zone when the Allow zones to span across monitors is configured

Window zone highlighting is also not functional

When FancyZones settings is closed and re-opened, the Allow zones to span across monitors checkbox is unchecked

When Allow zones to span across monitors is toggled to checked, then unchecked, zone highlighting and snapping functions, though obviously not with the multi-monitor zones

📝 Other Notes

There is a difference in framerate/refresh rate between the two monitors--could that be an issue?

System is a SurfaceBook 2 in a Surface Dock which drives a 2560 x 1440 monitor at 60 fps and a 2560 x 1440 monitor at 30 fps

The fps cannot be made the same as far as I can tell. Likely a hardware limitation.

Display is an LG 49 ultra-wide ( 5120 x 1440)

📷 Screenshots

FancyZones Settings:

Zone Editor spanning monitors:

Monitor configuration:
Issue 1:
Seems that zypper_repository is not idempotent as expected. Running a zypper_repository task multiple times gives:

"Repository named 'reponame' already exists. Please use another alias."

P.S.: I'm aware that the error can be bypassed with ignore_errors: yes

Issue 2:
ISSUE TYPE

Bug Report

COMPONENT NAME

include_tasks:

ANSIBLE VERSION

ansible-2.4.0-100.git201708150932.e9c9473819.devel.el7.centos
ansible-2.4.0.0-100.git201709151233.91e1a5fe16.stable24.el7.centos
ansible-2.5.0-100.git201709201920.131d417c7a.devel.el7.centos

CONFIGURATION

[defaults]
timeout = 120
roles_path = ./core/roles
remote_user = ansible
remote_port = 48022
ansible_become = yes
become = yes
become_user = root
forks = 100
log_path = ./logs/ansible.log
#inventory = inventory/
host_key_checking = False
retry_files_enabled = True

callback_plugins = plugins
stdout_callback = actionable

[paramiko_connection]
record_host_keys = False

[ssh_connection]
ssh_args = -o ControlMaster=auto -o ControlPersist=600s -o UserKnownHostsFile=/dev/null
pipelining = True
control_path = /tmp/ansible-ssh-%%h-%%p-%%r

OS / ENVIRONMENT

Centos7

SUMMARY

Try to change all include: in my playbook to include_tasks:

77 include: changed to include_tasks:

and i get very very slowed playbook

playbook with include: runned 6 min

playbook with include_tasks: runned 28 min, and earn all 64 Gb RAM memory on server

OOM killed other procecces !

and finnaly in log

ERROR! A worker was found in a dead state

STEPS TO REPRODUCE

play playbook with lot of include_tasks:

ACTUAL RESULTS

playbook with include_tasks: runned 28 min, and earn all 64 Gb RAM memory on server

OOM killed other procecces !

top - 22:47:04 up 23 days, 12:39, 0 users, load average: 2.49, 2.65, 4.53
Tasks: 68 total, 4 running, 64 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.8 us, 41.2 sy, 0.0 ni, 52.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 65646916 total, 0 free, 64420964 used, 1225952 buff/cache
KiB Swap: 524288 total, 500544 free, 23744 used. 804202 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
23218 robot 20 0 11.355g 0.011t 1860 S 36.0 17.7 0:01.10 ansible-playboo
23269 robot 20 0 11.355g 0.011t 1860 S 35.3 17.7 0:01.06 ansible-playboo
23240 robot 20 0 11.355g 0.011t 1860 S 29.3 17.7 0:00.88 ansible-playboo
23213 robot 20 0 11.355g 0.011t 1860 S 28.7 17.7 0:01.04 ansible-playboo
23212 robot 20 0 11.355g 0.011t 1860 S 24.0 17.7 0:00.93 ansible-playboo
25800 robot 20 0 11.354g 0.011t 5968 S 17.0 17.7 4:55.41 ansible-playboo
Issue 1:
When using the bulk API with a lot of documents (say 100K), it's kind of pointless to get a response for each of those documents because the response is huge! Cannot we have a way to call this API and only receive a response that is either:

Successful insertion of all documents (count).

Some insertion failed (count of the ones that failed).

All insertion failed (count).

I know that I could probably use Bulk UDP (and I'll probably give it a go soon), but UDP doesn't receive any response whatsoever, so it's like having black&white, but not any shade of grey.

Thanks!

Issue 2:
Elasticsearch version: 2.3.1

JVM version:8u77

OS version:OL 7u1 and Solaris 11.2

Description of the problem including expected versus actual behavior:

Cluster is operating normally and runs into an out of space condition on a node, that is the 85% value is reached. Shard stays in initializing state and following does not clear the condition.

Attempts to reassign ( Message below)

Reboots of nodes with shard having issue resident

Change of replicas from 4 to 2

Steps to reproduce:

Run a cluster and fill up the disk on some node

Have other indices with continuous writes

wait until shards start showing unassigned

Provide logs (if relevant):

2016-04-19 22:32:35] {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"[move_allocation] can't move [logstash-feeder-df-2016.04][1], shard is not started (state = INITIALIZING]"}],"type":"illegal_argument_exception","reason":"[move_allocation] can't move [logstash-feeder-df-2016.04][1], shard is not started (state = INITIALIZING]"},"status":400}
Issue 1:
When updating one or more packages the "Settings" button won't work anymore.

I came across this issue some time ago when i wanted to read the changelog of the updated package, so i can't really say in which version i first experienced this.

Actually using 0.200.0, also tried in --safe mode, same result.

It's a bit difficult to reproduce the issue as you need updateable package, so here's a anim do demonstrate:

Issue 2:
..does not work after having updated the package. For example, I just updated One-Dark-UI but the settings button does nothing in that view now.
Issue 1:
In the presence of top level inner hits query level inner hits are missing from the result, even if there are no name collisions. This necessitates rewriting query level inner hits as top level inner hits with a duplicate of the main query, which I assume is suboptimal.

ES 2.1.1.

Issue 2:
I have got an issue for few days and I have no idea how can I resolve it. I got no matching while percolating a document when obviously it should match a created percolator.

Here is how to reproduce this issue:

#Create an index with a geo_point mapping as nested object
curl -XPUT 'http://localhost:9200/geonestedindex' -d '
{
"mappings":{
"test":{
"properties":{
"location":{
"type":"nested",
"properties":{
"point":{
"type":"geo_point"
}
}
}
}
}
}
}'

#Create a percolator

curl - XPOST 'http://localhost:9200/geonestedindex/.percolator/1' -d '
{
"query": {
"filtered": {
"query": {
"match_all": {}
},
"filter": {
"nested": {
"filter": {
"geo_bbox": {
"point": {
"top_left": [
4.559326171875,
45.08127861241874
],
"bottom_right": [
5.2130126953125,
44.692088041727814
]
}
}
},
"path": "location"
}
}
}
}
}'

#Trying to match a document
curl -XPOST 'http://localhost:9200/geonestedindex/test/_percolate' -d '
{
"doc": {
"location": {
"point": "44.933, 4.9"
}
}
}'
Issue 1:
Steven Devijver opened SPR-599 and commented

It would be nice if the property editors registered with BeanWrapperImpl are also used on value elements in lists and maps. Right now they are handled as strings and need to be handled by the classes that receive them. This leads to boilerplate code that could be avoided.

Using BeanWrapperImpl on list and map elements would be possible in my view since the destination type is Object. No default editors are registered for Object so none of them would be picked. This would allow users to register a custom editor for Object that would inject other types than strings.

Registering a custom editor with Object doesn't interfere with normal property handling as the default editors come first in the list.

Issue Links:

#5271 Property editors support for indexed and mapped properties ("duplicates")

Issue 2:
Barry Kaplan opened SPR-2275 and commented

AbstractTransactionalSpringContextTests has no onSetup* hook for test methods marked as @NotTransactional. The onSetup methods only invokes onSetupBeforeTransaction if the transactionDefinition is not null. And since the AbstractTransactionalSpringContextTests.onSetup is set to be final, there is no way to add in any type of additional setup hooks.

Maybe onSetup/TeardownBeforeNonTransaction()?

Affects: 2.0 RC2

Issue Links:

#8081 AbstractTransactionalSpringContextTests shoud still call onSetupBeforeTransaction if transactions are prevented ("is duplicated by")

1 votes, 1 watchers
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Modal should have smooth transitions on open and close or give users the ability to add them.

Current Behavior

Currently in your Modal example, there is a short transition in and when closing a modal the content pops off the screen. Your standard transitions for the backdrop are being cut off as well, as I'm assuming the modal is killing itself before transitions finish.

Looking at your implementation, I could be reading it incorrectly, but it looks like it is supposed to handle transitions before "exited" state.

The dialog component appears to not have these issues.

Steps to Reproduce (for bugs)

Visit Modal example

Open modal and notice there is a short transition for opacity.

Close the modal and notice all content pops off instead of transitioning.

Context

It is important for us to have a smooth experience for our users so that it is pleasant to use the site and tools. We do everything we can to avoid harsh transitions.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.27

React
15.6.1

browser
Chrome Version 64.0.3282.167 (Official Build) (64-bit)

Issue 2:
src/styles/index.js and src/styles/index.d.ts these two documents are not consistent,

This will cause the TypeScript environment to run well but in the browser environment will be an error

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

Expected Behavior

import { createMuiTheme, createBreakpoints } from 'material-ui/styles';
const theme = createMuiTheme({
breakpoints: createBreakpoints({
values: {
xs: 360,
sm: 575,
md: 768,
lg: 991,
xl: 1199,
},
});

In the TypeScript environment is nothing wrong, but in the browser environment got a Uncaught TypeError: Object(createBreakpoints) is not a function.

Current Behavior

Now import it like this

import { createMuiTheme /*, createBreakpoints*/ } from 'material-ui/styles';
import createBreakpoints from 'material-ui/styles/createBreakpoints';
const theme = createMuiTheme({
breakpoints: createBreakpoints({
values: {
xs: 360,
sm: 575,
md: 768,
lg: 991,
xl: 1199,
},
});

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.17

React
16

browser
chrome 62

TypeScript
2.5.3
Issue 1:
See code here:
http://play.golang.org/p/50TI5VuWHN

What is the expected output?
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMloop: tick tsecs=1.001247, secs=1.001247, cnt=32412156
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMloop: tick tsecs=2.002406, secs=1.001159, cnt=34743305
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMloop: tick tsecs=3.001494, secs=0.999088, cnt=3168060

What do you see instead?
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM ...

Which compiler are you using (5g, 6g, 8g, gccgo)?
6g

Which operating system are you using?
MacOS X 10.7.5

Which version are you using? (run 'go version')
1.0.3
1.1 (go version devel +13e00572ed0b Thu Apr 18 17:37:21 2013 -0700 darwin/amd64)

Please provide any additional information below.
With Go 1.0.3 this program works the same with GOMAXPROCS=1 or GOMAXPROC > 1
With Go 1.1 this program works the same as 1.0.3 when GOMAXPROC > 1
With Go 1.1 when GOMAXPROC=1 the Ticker never ticks.

This represents a change in behavior from 1.0.3 to 1.1.

In my mental model of the Go runtime, at least when GOMAXPROCS=1, the "select"
statement *must* call the scheduler to allow other goroutines to run. If this is not the
case, then it should be documented what one needs to do in order to get scheduling to
occur.

Questions:

1. Is it really the case that I must insert a call to runtime.Gosched() to get the
correct behavior in Go 1.1? I find that a very unappealing solution to say the least.

2. Are there any guarantees at the language reference specification level of what one
must do to prevent goroutine scheduling starvation, especially when GOMAXPROCS=1? If
not, should there be?

This simple program was distilled down from a larger program that does I/O and compute
in the spot where the example does cnt++.. The larger program is collecting I/O metrics
and the Ticker is used to decide when to collect the metrics and reset the them. With Go
1.1 and GOMAXPROCS=1 I saw some bizarre behavior. The Ticker (set at 1s duration) would
tick fine for 300 seconds and then it would stop for a long time. Occasionally it would
send something down the channel. Really it was very strange.

Issue 2:
by sjbogdan:

A 64-bit executable consumes 540 MB on "hello world" project on startup
32-bit executable (on x86-64 system) uses acceptable amount of memory ~ 9 MB

Version affected : v1.1beta2 and v1.1rc1 compiles

> go version
go version devel +bea6199b09ea Tue Apr 30 17:47:39 2013 -0700 windows/amd64

Code : any hello world program compiled with 6g
Example :
package main

import "time"

func main () {
time.Sleep ( 1 * time.Minute )
}

---
See attachments

Additional information :
Windows 8 ( x86-64 ) Enterprize
Never used intaller, extracted from zip and set up GOROOT & GOPATH

Attachments:

ResMonitor.png (18103 bytes)

PM_amd64.png (19327 bytes)

PM1_amd64.png (9353 bytes)

PM_386.png (19339 bytes)

PM1_386.png (9393 bytes)
Issue 1:
at here:

http://tensorflow.org/how_tos/variable_scope/index.md

The tutorial talk about using "two sets of variables" and talk about their duplication, however the network itself uses 2 layers of convolution. So there's 2 different things that can be the quantity of 2.

The number of layers is 2, being conv1 and conv2, these 2 should be distinct

The number of image filters, applied once to each image, these 2 should be identical

I was having a hard time understanding at first and thought we're attempting to use the same weights for both of the conv layers. It didn't help that the definition for "variables_dict" only explicitly states the existence for the weights for the first conv layer, leading me to believe that the weights of the 2 layers are actually shared as well.

I think a simple fix is to make the network have say 5 conv layers instead of 2, this way you get to demonstrate variable_scope as well in the later section

Just my 2 cents, I starred at this for much longer than I should have because of this confusion.

Issue 2:
I would like to know if this feature exist in the library or if there's any plan to have it in the future.

Thanks!