WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Marten Deinum opened SPR-3417 and commented

In our current project I wanted to use Introductions. We already use the aop:config block(s) quite extensivly. We decided to use this block also for the <aop:declare-parents />.

However this alows only for 3 parameters to be specified

types-matching="[aspectj expression]"

implement-interface="[interface to introduce]"

default-impl="[Class of the default implementation]"

However in our default implementation (default-impl) we need to have some beans injected. For now we created a patchy solution with a singleton which holds a reference to the applicationContext. At construction time/initializing time we use this to retrieve the desired beans.

However what I would like to do is to wire up this delegate from my spring configuration and use that in our aop:declare-parents/ tag.

Something like this.

<bean id="someDelegate" class="com.mybiz.myapp.common.SomeDelegate">

<property name="hibernateTemplate" ref="hibernateTemplate"/>

</bean>

<aop:declare-parents types-matching="[aspectj expression]" implement-interface="[interface to introduce]" delegate-ref="someDelegate"/>

Affects: 2.0.4

1 votes, 2 watchers

Issue 2:
Dave Syer opened SPR-2872 and commented

I seems limiting (maybe there's a reason and I haven't figured it out) that I can only declare an introduction implementation as a class to be instantiated, not an actual bean instance. E.g. instead of:

<aop:declare-parents types-matching="test.aop.TestBean"

implement-interface="test.aop.Counter"

default-impl="test.aop.NullCounter"/>

we might see

<aop:declare-parents types-matching="test.aop.TestBean"

implement-interface="test.aop.Counter"

default-ref="nullCounter"/>

Affects: 2.0.1

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

Expected Behavior

Once a Collapse has finished animating in and has the entered className, overflow should be set to visible so borders, box-shadows, Checkbox ripples, contents positioned outside etc are visible.

Current Behavior

Currently the implementation only sets the height to auto, and the contents of a component which uses Collapse (like StepContent) can be clipped e.g. shadows around Papers, Cards etc

Steps to Reproduce (for bugs)

https://codesandbox.io/s/koo6069llv

Context

The most common case where this will pop up is when using a form in a Stepper with orientation set to vertical. The ripple from a Checkbox will clip at the edge of the Collapse used in StepContent.

Your Environment

See codesandbox link above.

Workaround

I was able to use theme overrides to work around this for now:

createMuiTheme({
overrides: {
MuiCollapse: {
entered: {
height: "auto",
overflow: "visible"
}
}
}
});

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

Expected Behavior

The documentation of checkbox and radio button components at the docs website has 'label'.

Current Behavior

'label' property is missing.

Steps to Reproduce (for bugs)

Link: http://www.material-ui.com/#/components/checkbox

PS: I'm happy to help to update docs, would be cool if you guide me where props types are coming from.
Issue 1:
Guten Tag!

For my project i used the 0.8 version of rust.

After i started to work on a parser module for my project.

rustc crashed at compile time and i decided to go and use the git version now i get an error message.

task 'rustc' has overflowed its stack
[1] 2625 illegal hardware instruction (core dumped) rustc main.rs

My project compiles without

pub mod parser;

in my main.rs perfectly.

But i don't get an error message, what says what goes wrong.

So I think thats an issue so thats reason you read that.

Thanks for every help on the irc and for my problem!

Sebastian Pielawa

Issue 2:
The following program causes a stack overflow:

struct S {
element: Option<S>
}

fn main() {
}

There is a check that enums do not recurse in this way, but no such check for structs. (Note, though, that there is a check that structrs are instantiable, which is slightly different)
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

15.0.0

What operating system are you using?

Windows

Operating System Version

Windows 10

What arch are you using?

x64

Last Known Working Electron version

13.1.7

Expected Behavior

-webkit-app-region: drag move the window

Actual Behavior

-webkit-app-region: drag is not moving the window

Testcase Gist URL

No response

Additional Information

I created a BrowserWindow with this configuration

{
frame: false,
width: 315,
minWidth: 315,
height: 485,
minHeight: 485,
resizable: false,
maximizable: false,
webPreferences:{
nodeIntegration: true,
preload: path.join(__dirname, "preload.js")
}
}

In the window there was a div with this style: -webkit-app-region: drag

But he not moves this window

After some tests I found out that the property resizable: false was what caused the problem and the property

movable: true does not fix the error

Sorry for the poor English I'm not fluent :)

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

14.0.0

What operating system are you using?

Windows

Operating System Version

Windows 10 Pro - 20H2 - 19042.1165 - Windows Feature Experience Pack 120.2212.3530.0

What arch are you using?

x64

Last Known Working Electron version

13.2.2

Expected Behavior

When creating a new, frameless BrowserWindow setting resizable: false should not change the behaviour of custom app drag regions defined using -webkit-app-region: drag;.

Actual Behavior

When creating a new, frameless BrowserWindow with the test scenario in the Gist (using Electron Fiddle) the region I've defined as draggable using -webkit-app-region: drag; does not allow me to drag the BrowserWindow if resizable is set to false.

You can see the difference by commenting/uncommenting the resizable: false line in the Electron Fiddle Gist example.

Testcase Gist URL

https://gist.github.com/68a75365505163c4a19ab19c5ffd062a

Additional Information

Just to note that I've also tried using win.setResizable(false); after the BrowserWindow has loaded and this then also disables the ability to drag the frameless BrowserWindow. Using the following code also then re-enables dragging after 5 seconds so the bug seems directly tied to the BrowserWindow not being resizable.

setTimeout(() => {
mainWindow.setResizable(true);
}, 5000);
Issue 1:

Issue 2:
Environment

Windows build number: Windows 10 1903

Windows Terminal version (if applicable): 0.2.1715.0

Steps to reproduce

you can only drag the window when clicking on the window title that is actually colored in Windows 10 color style ([1]marked green)

click on the window title ([1]marked red) you cannot move the window

![windows terminal drag window]

![1]

(https://user-images.githubusercontent.com/45657752/59983328-9258f700-961e-11e9-9522-357b93c911b0.png)

Expected behavior

I expect that left mouse click and hold on the complete window title should allow dragging of the Windows Terminal window.

Actual behavior

The left space this is reserved ([1]marked red) for new tabs or existing tabs (black) cannot be used to move the window
Issue 1:
It would be nice if the bottom-docked pane (integrated terminal, Output view, etc.) could optionally appear as a column alongside the editors, instead of docked to the bottom. My team has a command-line test watcher and node server that we keep an eye on while developing. Our terminal output tends to be tall and narrow. A column view or side-docked view would fit better and not cover vertical space of the editors.

Issue 2:
It's nice that the implementations of FormatDocumentProvider and DocumentSymbolProvider can be used via executeCommand. However, the return types are undocumented and subtely different from what the implementation side produces.

Is this intentional?

Is it considered a supported scenario for extensions to use executeCommand on these commands? Or should they factor out their implementation and use the implementation code directly?

For FormatDocumentProvider for example, I provide a TextEdit[] which is:

[
{
"_range": {
"_start": {
"_line": 2,
"_character": 7
},
"_end": {
"_line": 4,
"_character": 4
}
},
"_newText": ""
},
{
"_range": {
"_start": {
"_line": 4,
"_character": 14
},
"_end": {
"_line": 5,
"_character": 1
}
},
"_newText": ""
}
]

but executeCommand("vscode.executeFormatDocumentProvider", ...) receives this as:

[
{
"text": "",
"range": {
"startLineNumber": 3,
"startColumn": 8,
"endLineNumber": 5,
"endColumn": 5
}
},
{
"text": "",
"range": {
"startLineNumber": 5,
"startColumn": 15,
"endLineNumber": 6,
"endColumn": 2
}
}
]

The combination of completely different shape plus the 1-based numbering makes this data difficult to work with.

Similarly different results are returned from others similar commands.
Issue 1:
Uncaught Error: spawn /usr/share/atom/atom ENOENT

Atom Version: 0.154.0

System: linux 3.13.0-40-generic

Thrown From: Atom Core

Steps To Reproduce

...

...

Stack Trace

At events.js:85

Error: spawn /usr/share/atom/atom ENOENT
at exports._errnoException (util.js:742:11)
at Process.ChildProcess._handle.onexit (child_process.js:1051:32)
at child_process.js:1142:20
at process._tickCallback (node.js:378:11)

Issue 2:
TEMPORARY WORKAROUND: ln -s /usr/share/atom/atom "/usr/share/atom/atom (deleted)"

Uncaught Error: spawn /opt/atom/atom (deleted) ENOENT

Atom Version: 0.152.0

System: linux 3.13.0-40-generic

Thrown From: Atom Core

Steps To Reproduce

...

...

Stack Trace

At events.js:85

Error: spawn /opt/atom/atom (deleted) ENOENT
at exports._errnoException (util.js:742:11)
at Process.ChildProcess._handle.onexit (child_process.js:1051:32)
at child_process.js:1142:20
at process._tickCallback (node.js:378:11)
Issue 1:
Related issues: 4501, 4234

The package net contains some APIs that fetches the kernel state, specifically
network interfaces and its belongings for creating new connections. issue #4501,
4234 focus on transport API, Dial and Listen, but are not for under the hood API.

This issue holds that how could we support IPv6 scoped address zone support
for such under the hood API, including whether it should be a part of net API.

API that would be affected:
type IPNet struct
method (*IPNet) String
type IPAddr struct
method (*IPAddr) String
func Interfaces
func InterfaceAddrs
method (*Interface) Addrs
method (*Interface) MulticastAddrs

Issue 2:
http://play.golang.org/p/yjqyCAEMyR

What is the expected output?

I expect all examples to listen on an IPv4 address. On the playground this is the case.

What do you see instead?

net.Listen("tcp", "0.0.0.0:11111") listens on [::]:11111 on my
system.

The full output is:
2014/02/25 19:59:14 0.0.0.0:11111
2014/02/25 19:59:14 [::]:11112
2014/02/25 19:59:14 127.0.0.1:11113
2014/02/25 19:59:14 127.0.0.1:11114

Which operating system are you using?

Ubuntu 12.04, 3.8.0-36-generic

Which version are you using? (run 'go version' or 'gccgo --version')

go version go1.2 linux/amd64

The only reason the examples use different ports is because the playground doesn't
Close() quickly enough for the program to succeed (it works when I Close() locally).
From testing, I don't think port number makes a difference to the behaviour.

Admittedly the workaround is trivial, but I thought this worth reporting anyway.
Issue 1:
It appears that kube-ui supports only 'default' namespace.

Any pod,rc,service created in namespaces other than 'default' are not shown/accessible via kube-ui.

Issue 2:
While debugging #5091 I noticed that when I'm creating guestbook application by running ./cluster/kubectl.sh create -f examples/guestbook there is a chance that frontend pods come up before information about environment variables of redis is propagated. In such case frontend can't connect to database during its whole life.

It's actually more general problem, since most of complex application might be affected by this. Also I think create a set of resource (especially by specifying the directory of their config files) should just work no matter of the order of creation.

I can see few solutions of such problem:

Get rid off HOST:PORT stuff and start using DNS service instead.

Add ability to wait for such information being propagated.

Injecting environment variables to container somehow(?).
Issue 1:
The title says it all. I'd like if fetch could also open local files, just like the browser can if the origin ist file://.

There is even a test that checks that this does not work here:

deno/cli/tests/unit/fetch_test.ts

Lines 14 to 20
in
e568ddf

await assertThrowsAsync(

async (): Promise<void> => {

await fetch("file:///");

},

TypeError,

"not supported",

);

Allowing file:// could profit any library or script that really just needs the contents of a file and doesn't really care where it is.... just like deno run in fact.

At this moment, you'd have to implement some kind of wrapper.

async function readTextFile(url: URL): Promise<string> {
if (url.protocol === 'file:' && typeof Deno.readTextFile !== 'undefined') {
return await Deno.readTextFile(url.pathname)
} else {
const response = await fetch(url)
return await response.text()
}
}

There are a few things interesting points to look out for:

Error code mapping aka: 404 = not found/file does not exist, 403 = unauthorized/--allow-read-missing/filemod

Partial request?

Post/Put request?

Issue 2:
Hello,

I was trying to debug a small app and was surprised when console.log did not print the private properties of a class. I ran the code in Chrome and it printed the private property. So at least there is an inconsistency between Chrome and Deno. I would say private properties should be logged by console.log and friends, i.e.: debug, warn, error and trace. It's very useful for debugging purposes. Is this intended behavior?

Example

class Test {
#q = "qwe"
a = "asd"
}
let t = new Test()
console.log(t)

Deno Result

Chrome Result
Issue 1:
Migrated issue, originally created by MartinH (@dwt)

I've found that the documentation for join at http://docs.sqlalchemy.org/en/rel_0_8/orm/query.html#sqlalchemy.orm.query.Query.join was lacking the information that the direction of the join, i.e. what is the left side and what is the righthand side of a join can be decided by the way you write the argument to the join call.

So it makes a difference if you write DBSession.query(User).join(Track.user) - that will select * from Track join User or if you write DBSession.query(User).join(User.tracks) which will select * from User join Track.

As far as my understanding of sql is that shouldn't make a difference, but when you switch from join to outerjoin(), suddenly this distinction becomes very important as it defines the lefthand side of the left outer join and someting you cannot override even with select_from().

And that is what cost us quite some time today to figure out - so a clearer mention of this in the documentation would be really helpfull.

Hope this clarifies what I mean,

Best Regards,

Martin

Issue 2:
Migrated issue, originally created by Michael Bayer (@zzzeek)

from sqlalchemy import *
from sqlalchemy.orm import *
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.ext.declarative import declared_attr

Base = declarative_base()

class A(Base):
__tablename__ = 'a'

id = Column(Integer, primary_key=True)
data = Column(String)
bs = relationship("B")

class B(A):
__tablename__ = 'b'

id = Column(Integer, ForeignKey('a.id'), primary_key=True)

class C(A):
__tablename__ = 'c'

c_id = Column(Integer, ForeignKey('a.id'), primary_key=True)

from sqlalchemy.sql.elements import ClauseList

# ClauseList / Bundle are equivalent
print(ClauseList(A.id, C.c_id))
print(Bundle("pk", A.id, C.c_id).__clause_element__())

# w/ same name, they are not because it creates the clause list using *c without using exprs
print(ClauseList(A.id, B.id))
print(Bundle("pk", A.id, B.id).__clause_element__())

output:

a.id, c.c_id
a.id, c.c_id
a.id, b.id
b.id

fix:

diff --git a/lib/sqlalchemy/orm/query.py b/lib/sqlalchemy/orm/query.py
index 98747c680..0b6b32a07 100644
--- a/lib/sqlalchemy/orm/query.py
+++ b/lib/sqlalchemy/orm/query.py
@@ -1738,7 +1738,7 @@ class Query(object):
self._group_by = False
return

- criterion = list(chain(*[_orm_columns(c) for c in criterion]))
+ criterion = c = list(chain(*[_orm_columns(c) for c in criterion]))
criterion = self._adapt_col_list(criterion)

if self._group_by is False:
@@ -3964,7 +3964,7 @@ class Bundle(InspectionAttr):
return cloned

def __clause_element__(self):
- return expression.ClauseList(group=False, *self.c)
+ return expression.ClauseList(group=False, *self.exprs)

@property
def clauses(self):
Issue 1:
The following code:

use std::rc::Rc

struct ProblemType {
children [Option<Rc<ProblemType>>; 8],
}

impl ProblemType {
fn breaks_compiler() -> Option<Rc<ProblemType>> {
None
}
}

Causes LLVM to fail an assertion, claiming:

rustc: /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/llvm/lib/IR/DataLayout.cpp:636: unsigned int llvm::DataLayout::getAlignment(llvm::Type*, bool) const: Assertion `Ty->isSized() && "Cannot getTypeInfo() on a type that is unsized!"' failed.

Issue 2:
Example program:

use std::mem;

struct AlignmentStruct {
ptr: *mut [AlignmentStruct, ..1]
}

fn main() {
println!("{}", ::std::mem::align_of::<AlignmentStruct>());
}

Error message:

rustc: /home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/llvm/lib/IR/DataLayout.cpp:636: unsigned int llvm::DataLayout::getAlignment(llvm::Type*, bool) const: Assertion `Ty->isSized() && "Cannot getTypeInfo() on a type that is unsized!"' failed.
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-invert-regular-expression-matches-with-javascript has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

My regex is returning the value 7, but assert(test === 36)

Second test is passing with an invalid test:

'You should be using the following expression /+S/gi to find the spaces in the testString.'

This test is passing with the regex /\s/gi

/+S/gi makes no sense - as it is searching for all matches of the literal '+' followed by a literal 'S'

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-construct-javascript-objects-with-functions has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

This is very similar to the bug I filed just a few minutes ago. The instructions tell the user to use "engine" as the name for one of the attributes. However, when you do that, your submission is flagged as incorrect.
Issue 1:
Environment

Windows build number: [run "ver" at a command prompt]
PowerToys version:
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

Issue 2:
When PowerToys loads at startup "Start typing..." appears on the screen/desktop for about half a second. Just text and no other design elements. I'm sure you hadn't meant it to. Otherwise I'm loving it

PowerToys v0.18.3 on Windows 10 Home (Version 2004 - OS Build 19041.264 - WinFE Pack 120.2202.130.0)
Issue 1:
Flutter Doctor

E:>flutter doctor

Doctor summary (to see all details, run flutter doctor -v):

[√] Flutter (on Microsoft Windows [Version 10.0.16299.248], locale en-US, channel beta)

[√] Android toolchain - develop for Android devices (Android SDK 27.0.0)

[√] Android Studio (version 3.0)

[!] Connected devices

! No devices available

! Doctor found issues in 1 category.

What's the problem here???

Issue 2:
Flutter Doctor

C:\>flutter doctor -v
[√] Flutter (on Microsoft Windows [Version 10.0.16299.248], locale en-US, channel beta)
• Flutter version 0.1.4 at C:\flutter
• Framework revision f914e701c5 (9 days ago), 2018-02-19 21:12:17 +0000
• Engine revision 13cf22c284
• Dart version 2.0.0-dev.27.0-flutter-0d5cf900b0

[√] Android toolchain - develop for Android devices (Android SDK 27.0.0)
• Android SDK at C:\Users\zowhair\AppData\Local\Android\sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-27, build-tools 27.0.0
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[√] Android Studio (version 3.0)
• Android Studio at C:\Program Files\Android\Android Studio
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[!] Connected devices
! No devices available

! Doctor found issues in 1 category.
Issue 1:
Today doing something like:

@torch.jit.script
def foo(s: Any):
if isinstance(s, dict):
print(s.items())

gives:

RuntimeError: Unknown type name 'dict':

And capitalizing "dict" will produce a segfault. Yikes!

A related issue is that doing something like:

isinstance(foo, Dict[str, Tensor])

is not actually possible in Python, since the type annotations are mostly static constructs that the interpreter doesn't know anything about.

A potential compromise is to have isinstance(foo, dict) refine the type of foo to Dict[Any, Any]. And then the user can further type refine to get an actual things they want. So:

if isinstance(foo, dict):
for k, v in foo.items():
assert isinstance(k, str)
assert isinstance(v, Tensor)

Another potential solution is to have a torch.jit.isinstance(foo, Dict[str, tensor]) that boils down to isinstance(foo, dict) in Python but performs the correct type refinement in TS.

cc @suo @gmagogsfm

Issue 2:
🐛 Bug

PyTorch 1.6.0 is imported with a segmentation fault when built from source on a computer with an old CPU (not supporting AVX/AVX2/SSE4 instructions).

To Reproduce

Steps to reproduce the behavior:

Run python setup.py build on a computer with an old CPU (such as AMD Athlon II X4).

python -c import torch

???

Segmentation fault!

Log of gdb -ex r --args python -c "import torch": https://pastebin.com/RuXGLdLE

Output of cat /proc/cpuinfo: https://pastebin.com/EgPSEGS0

Expected behavior

Successful build and package import.

Environment

When torch is installed

$ python collect_env.py

returns Illegal instruction (core dumped).

When torch is not installed

$ python collect_env.py

exits with the error:

Collecting environment information...
Traceback (most recent call last):
File "collect_env.py", line 429, in <module>
main()
File "collect_env.py", line 424, in main
output = get_pretty_env_info()
File "collect_env.py", line 419, in get_pretty_env_info
return pretty_str(get_env_info())
File "collect_env.py", line 276, in get_env_info
if torch.version.hip is None: # cuda version
NameError: name 'torch' is not defined

PyTorch Version (e.g., 1.0): 1.6

OS (e.g., Linux): Linux 5.8.13-arch1-1 #1 SMP PREEMPT Thu, 01 Oct 2020 20:40:35 +0000 x86_64 GNU/Linux

How you installed PyTorch (conda, pip, source): source

Build command you used (if compiling from source): makepkg -s

Python version: 3.8.5

CUDA/cuDNN version: 11.1

GPU models and configuration: 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX 1650] (rev a1)

Any other relevant information:

Additional context

I'm building pytorch using ArchLinux PKGBUILD file from this repo: https://github.com/archlinux/svntogit-community/tree/packages/python-pytorch/trunk

As can be seen, it contains a section with a x86_64 preconfiguration (meant to turn off any optimizations) and this patch to disable AVX/AVX2/etc.