WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Christopher Sahnwaldt opened SPR-2815 and commented

I have a property named arrays of type List<String[]>

public void setArrays( List<String[]> arrays )

I try to set it like this:

<property name="arrays">

<list value-type="java.lang.String[]">

<list>

<value>value1</value>

<value>value1</value>

</list>

</list>

</property>

But at runtime I get a List that contains a List, not a List that contains a String array. I added the value-type="java.lang.String[]" attribute, but it didn't change anything.

I would expect this work since I can set a property of type String[]

public void setArray( String[] array )

like this:

<property name="array">

<list>

<value>value1</value>

<value>value1</value>

</list>

</property>

This is similar to (or even a duplicate of?) #7198 and #7494.

Affects: 2.0 final

Attachments:

generic.beans (657 bytes)

Generic.java (1.02 kB)

Issue 2:
Oliver Hutchison opened SPR-1307 and commented

In CachingMapDecorator the field targetMap is synchronized through the call to Collections.synchronizedMap(internalMap) in the constructor, which would indicate to me that CachingMapDecorator is intended to be thread safe, however there is no synchronization on the method get which could result in duplicate calls to the create method for a given key.

So should the class a) be documented as being thread safe and have the get method synchronized as well or b) be documented as not thread safe and have the call to Collections.synchronizedMap(internalMap) removed from the constructor?

My guess is that a) would be the better option given that some people may already be using this class and assuming it is thread safe.

Affects: 1.2.4
Issue 1:
Hi

When clicking on a button dropdown which is located close to the right side (RHS) of the screen, the dropdown overflows the screen.

Steps:

goto: http://getbootstrap.com/components/#btn-dropdowns (on mobile or emulate screen in browser)

click on dropdown which is close to the RHS of screen.

Thanks in advance!

Issue 2:
A picture is worth a thousand words; this is taken directly from the docs with chrome at 515px wide.

I've implemented the following solution in my own project to remedy this, and would like to know if it is worth submitting a pull request for (modified, of course)

$(document).on('shown.bs.dropdown', function () {
OffsetDropdown()

$(window).on('resize.bs.dropdown', function () {
OffsetDropdown()
})
})

$(document).on('hide.bs.dropdown', function() {
$(window).off('resize.bs.dropdown')
})

var OffsetDropdown = function() {
var dropdown = $('.open>.dropdown-menu')

if (dropdown.length == 0)
return

var rightOffset = dropdown.offset().left + dropdown.width()
var browserWidth = $('body').innerWidth()
var neededLeftOffset = dropdown.position().left - (rightOffset - browserWidth)

if (neededLeftOffset < 0) {
dropdown.css({ left: neededLeftOffset - 3 })
} else {
dropdown.css({ left: 0 })
}
}
Issue 1:
Celery 3.0.13

Biliiards 2.7.3.19

Workers consuming 10,000 tasks a day.

We kill a worker after executing 1 task. Max_Task_Per_Child = 1

Overtime, we deadlocked workers.

Can't get a pystack for you.

In the Stack Trace, it shows that the deadlock happens while billiards is trying to acquire a lock.

#0 0x0000003cff40c0ed in sem_wait () from /lib64/libpthread.so.0

#1 0x00002b180708129a in Billiard_semlock_acquire (self=0x3d165f9340, args=, kwds=) at Modules/_billiard/semaphore.c:312

Strace shows the processes in a futex wait state.

What sort of data can help you debug this problem?

Issue 2:
I am using Celery version 3.0.19 from pypi (upgraded and tested today). Here are my steps to reproduce:

app.py:

from time import sleep
from celery import Celery

celery = Celery(broker="amqp://")
celery.conf.update(
CELERYD_CONCURRENCY=1,
CELERYD_MAX_TASKS_PER_CHILD=1,
)

@celery.task
def accept_argument(argument):
sleep(5)

script.py:

from app import accept_argument

big_data = "A" * 1024 * 1024 * 8

accept_argument.delay(big_data)
accept_argument.delay(big_data)

Run the worker:

$ celery worker --app=app -l info

Crash the worker:

$ python script.py

Expected result:

Both tasks are run, in sequence.

The worker (sub)process restarts at the 5 second mark after the first task completes (MAX_TASKS_PER_CHILD=1 reached)

The worker process restarts at the 10 second mark after the second task.

Actual result:

The first task runs.

The first worker process goes into a zombie state.

The worker main process hangs in Modules/_billiard/socket_connection.c

Observe by attaching gdb to the running process.

Presumably the main process is writing the second task to the zombie original worker, but should be writing it to a new worker process.

I strongly suspect that this is the same problem as issue #957, but that was closed-presumed-fixed as of version 3.0.13 and I am using a later version of Celery.

EDIT: tweaking reproduction code.
Issue 1:
icc v14.0.1

julia 01:38:26 {master} ~/julia-icc$ make
CC src/task.o
task.c(332): catastrophic error: Cannot match asm operand constraint
compilation aborted for task.c (code 1)
make[1]: *** [task.o] Error 1
make: *** [julia-src-release] Error 2

Issue 2:
Continuing discussion from https://groups.google.com/forum/#!topic/julia-users/pSeB8VwrW3A. Paraphrasing from the thread:

I'm on commit a318578. Running `make' gives me:

$ source /gpfs/runtime/opt/intel/2013.1.106/mkl/bin/mklvars.sh intel64 ilp64
$ export MKL_INTERFACE_LAYER=ILP64
$ make
CC src/task.o
task.c(352): catastrophic error: Cannot match asm operand constraint
compilation aborted for task.c (code 1)
make[2]: *** [task.o] Error 1
make[1]: *** [julia-release] Error 2
make: *** [release] Error 2"

Make.user:

USEICC = 1
USEIFC = 1
USE_INTEL_MKL = 1
USE_INTEL_MKL_FFT = 1
USE_INTEL_LIBM = 1
JULIA_CPU_TARGET = core2

Weirdly, the exact same setup works fine compiling v0.3.

I'm trying to compile on a Linux machine with gcc 4.7.2 and MKL 11.1.1. I'm aware of #8294 but this seems like a distinct problem.
Issue 1:
Steps to reproduce and a minimal demo of the problem

Plunkr: http://plnkr.co/edit/IIZFhPWaFDIRSg0fmEAB?p=preview

What steps should we try in your demo to see the problem?

See two children on the page, and the message, that only 2 children are alive.

Click update button

See that another 2 items with new uuids appeared;

See that more then 2 components are alive already

Do click on the BODY to see (in console) that mentioned children are really alive

Current behavior

Each second component is not destroyed.

Expected/desired behavior

All components should properly be destroyed (you should have every time 2 children alive on the page)

Other information

In angular2-beta.15 issue does not exist. Components created / destroyed properly.

Also interesting part is that each 2nd component in ng-for is not destoyed.

If you remove ngIf from parent - everything will work as expected

Issue 2:
Steps to reproduce and a minimal demo of the problem

demo http://plnkr.co/edit/7uoVecfa62i8No8GtQHI?p=preview

Angular2 beta 16 or higher - When I hide first section with nested components using *ngIf, ngOnDestroy of every nested component is triggered - this is OK.

<div *ngIf="!ff2">
<my-component
></my-component>
<my-component
></my-component>
<my-component
></my-component>
<my-component
></my-component>
<my-component
></my-component>
</div>

Outpu in console is

init
init
init
init
init
destroy
destroy
destroy
destroy
destroy

But when I hide second section where subcomponents are duplicated by *ngFor, not every ngOnDestroy is triggered.

<div *ngIf="!ff">
<my-component
*ngFor="#i of [1,2,3,4,5,6]"
></my-component>
</div>

output in console is

(6) init
(3) destroy

Current behavior

not every ngOnDestroy is triggered

Expected/desired behavior

every ngOnDestroy should be triggered

Other information

in angular2 beta 9 it was working correctly

http://plnkr.co/edit/Q8tLJKlpF6wEVcMWfxH1?p=preview
Issue 1:
I am attempting to get Firebase, specifically Firestore, working with Deno but am running into issues. I've raised this as a question on StackOverflow.

These issues seem to be with the compatiblity between the firebase module and Deno, as the error even occurs in the Deno Firebase tutorial, and if running the source code directly with deno run --allow-net https://deno.com/examples/firebase.js.

Issue 2:
When utillizing the code and following the tutorial at: https://deno.com/deploy/docs/tutorial-firebase/

On first visit, the deploy fails.

0
TypeError: Cannot read properties of null (reading 'INTERNAL') at Ke (https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:2184:21) at new Ze (https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:2310:9) at https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:3835:32 at https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:8108:4

1
isolate start time: 9 milliseconds

2
TypeError: Cannot read properties of null (reading 'INTERNAL') at Ke (https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:2184:21) at new Ze (https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:2310:9) at https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:3835:32 at https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:8108:4

3
isolate start time: 14 milliseconds

4
TypeError: Cannot read properties of null (reading 'INTERNAL') at Ke (https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:2184:21) at new Ze (https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:2310:9) at https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:3835:32 at https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:8108:4

5
isolate start time: 12 milliseconds

6
TypeError: Cannot read properties of null (reading 'INTERNAL') at Ke (https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:2184:21) at new Ze (https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:2310:9) at https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:3835:32 at https://cdn.skypack.dev/-/@firebase/auth@v0.16.8-zp4BWpLW0rBfBR0kDd0B/dist=es2019,mode=imports/optimized/@firebase/auth.js:8108:4

7
isolate start time: 265 milliseconds
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 an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

11.1.0

Operating System:

Windows 10 x64 Bit (lots of different builds)

Last Known Working Electron version:

Unknown

Expected Behavior

Not to throw errors on boot.

Actual Behavior

Throwing errors on startup.

To Reproduce

No idea how to...I pushed an update to our users, and it seems like there was some kind of outage from our CDN for 10 minutes or so at the same time I pushed out the update.

Screenshots

https://i.gyazo.com/thumb/1200/5210051076f1b041e7335ff180fcab67-png.jpg

Additional Information

Logs showing the error from one user:

2021/01/01 17:13:02:459 Error: net::ERR_CONNECTION_RESET
at SimpleURLLoaderWrapper.<anonymous> (electron/js2c/browser_init.js:105:6497)
at SimpleURLLoaderWrapper.emit (events.js:315:20)
2021/01/01 17:14:23:446 Error: net::ERR_CONNECTION_RESET
at SimpleURLLoaderWrapper.<anonymous> (electron/js2c/browser_init.js:105:6497)
at SimpleURLLoaderWrapper.emit (events.js:315:20)
2021/01/01 17:14:24:933 Cannot download differentially, fallback to full download: Error: net::ERR_CONNECTION_RESET
at SimpleURLLoaderWrapper.<anonymous> (electron/js2c/browser_init.js:105:6497)
at SimpleURLLoaderWrapper.emit (events.js:315:20)

I cannot find the code anywhere in the repo, but I guess it has something to do with the way things are packaged. Anyways it definitely seems like some kind of internet outage issue coupled with logic that does not handle connection errors? I don't see any of my code in the stack trace here, which is the weird part....or I would just catch and handle it myself.

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.

Problem Description

If you're sending notification from the main process, theres no way to determine programmatically if the OS allows them to display.

Proposed Solution

There should be a function or something one could run on start up to determine if notifications are allowed to display from the main process. I thought there was one, but I can't find any reference to it.

Alternatives Considered

I can't find any other way to check if my app has permissions to send notifications on Mac or Windows. If y'all do please let me know.

Additional Information

Please don't like me mdn docs for renderer process notifications permissions. I'm sending these from the main process.
Issue 1:
Karl Moore opened SPR-3194 and commented

There doesn't seem to be a reference to OpenSessionInView anywhere in the reference manual. As this is a pretty common usage pattern, it might be useful to include some information on it. The question has been raised a few times now, might be nice to have an example.

Issue Links:

#6322 Doc: Hibernate3 OpenSessionInView and getCurrentSession() example ("duplicates")

1 votes, 0 watchers

Issue 2:
Costin Leau opened SPR-1625 and commented

A lot of users on the forum have problems setting up an application using the OpenSessionInView. Most of the times the solution is outside the spring samples at points at various blogs or demo applications. I think a simple OSIV (mainly with Hibernate) should be added inside the main distribution samples (even if as a comment).

Issue Links:

#7879 OpenSessionInView Filter/Interceptor lacks documentation coverage ("is duplicated by")

5 votes, 5 watchers
Issue 1:
Example can be seen here:

http://getbootstrap.com/javascript/

When scrolling to the bottom of the page on OSX (which has the 'overscroll' effect built into browsers, I'm using Chrome but it's built into the OS from what I can see) the 'affix' sidebar behaves erratically as you overscroll.

Unsure whether this was an issue in earlier releases, but it was present from at least 3RC1 onward.

Issue 2:
Poor affix is sick. Chrome for Mac. When the docs html tag is at 1201px wide, do the following:

Scroll down to the very end of the documentation's "Components" tab

With the Apple MightyMouse, "overscroll up" the page

Notice affix boy goes into oscillatory shakes mode
Issue 1:
Environment

Windows build number: 18363.476
PowerToys version: 0.13.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

Unknown

Expected behavior

Nothing happens and the number keys remain functional.

Actual behavior

Some unknown circumstances cause FancyZones to take control of the number keys (preventing normal input) and just flashing certain zones until an open window is moved.

This might be a coincidence since I very often have a setup like this but most times I had this happen (only happens every few days) I had one or multiple windows snapped to built-in Windows snapping locations, using the mouse cursor to snap it again resolves the issue.

The "flashing" I am talking about is a single zone from my selected configuration lighting up for only a couple of milliseconds and nothing else happening.

Edit: The zones lighting up only happens when pressing one of the number keys on the number row, the number pad is completely unaffected.

Edit 2: I just remembered that a few times this happens I noticed it when attempting to input a special character from the number row, I wonder if that might be connected? Key combinations using the number row also don't work in the glitched state by the way.

Edit 3: I am also 99% sure that this is a new bug on 0.13.0 or 0.12.0, I used 0.11.0 for a while and never had this issue.

It only happens very rarely so I am still investigating what could be causing this, I decided to just post it in case someone else has it and just hasn't made a post yet or you guys figure out what happened just from that description.

Issue 2:
Description

From time to time while using my computer, PowerToys disables my numb-keys (the normal keyboard ones not numbpad).

I'm quite sure that it is PowerToys due to the fact that when I turn it off, the keys are working as usual again.

I have yet to find the reason or a way to reproduce it, but I will update this issue if/as soon as I do.

Environment

Microsoft Windows [Version 10.0.18362.356]

PowerToys 0.11.0

Steps to reproduce

None found yet.

Expected behavior

Number keys working as usual.

Actual behavior

Number keys not working at all.
Issue 1:
Symfony default behaviour for handling reordering in collection type is wrong.

When you reorder to items saved in database as:

id: 56, name: first, order: 0

id: 57, name: second, order: 1

After changing they positions I receive:

id: 56, name: second, order: 0

id: 57, name: first, order: 1

Instead of:

id: 56, name: first, order: 1

id: 57, name: second, order: 0

Last occurrence at version 2.0.15

Issue 2:
I expected to get an exact copy of the original with only my passed params merged in, as per docs.

https://github.com/symfony/symfony/blob/master/src/Symfony/Component/HttpFoundation/Request.php#L393

What is the purpose of this nulling process?

thanks!
Issue 1:
Much simpler example

In [1]: df = pandas.DataFrame({ 'x' : [], 'y' : [], 'z' : []})

In [2]: df
Out[2]:
Empty DataFrame
Columns: [x, y, z]
Index: []

In [3]: df.applymap(lambda x: x)
Out[3]:
x NaN
y NaN
z NaN
dtype: float64

In [4]: df = pandas.DataFrame({ 'x' : [1], 'y' : [1], 'z' : [1]})

In [5]: df.applymap(lambda x: x)
Out[5]:
x y z
0 1 1 1

The docs for Dataframe.applymap clearly say it will return a DataFrame. However that does not happen if you call it on a DataFrame with no rows -- it returns a series. Not only that, the series has values in it, which is not what anyone would expect from an empty DataFrame.

This is with pandas 0.18.0.

#For our use case, an 0-row dataframe is 100% legitimate. This experiment really did return 0 rows.
df = pandas.DataFrame({ 'x' : [], 'y' : [], 'z' : []}) #empty dataframe
len(df) #returns 0, just what you'd expect from an empty dataframe.

#Strip off whitespace from any strings in the dataframe. Obviously not needed for this empty
#dataframe, but would be needed on a dataframe that had rows. (Yes, I know there's alternative
#ways to do this, I'm not looking for workarounds. I'm focused on how applymap works.)
df2 = df.applymap(lambda x : x.strip() if isinstance(x, str) and len(x) > 0 else x)
len(df2) #WHOA! This is 3, not 0. How'd that happen?
type(df2) #Oh, it returned a series instead of a dataframe. The docs do NOT say it does that.
#The docs says it always returns a DataFrame, which is what most developers would expect.

Almost anyone would expect applymap() on an empty DataFrame to return an empty DataFrame, not convert it to a Series with NaNs. We should change it to return an empty DataFrame.

Issue 2:
I'm unsure about a corner case I encountered:

>>> pd.DataFrame([]).applymap(round)
Series([], dtype: float64)

full example

In [1]: df = pandas.DataFrame({ 'x' : [], 'y' : [], 'z' : []})

In [2]: df
Out[2]:
Empty DataFrame
Columns: [x, y, z]
Index: []

In [3]: df.applymap(lambda x: x)
Out[3]:
x NaN
y NaN
z NaN
dtype: float64

In [4]: df = pandas.DataFrame({ 'x' : [1], 'y' : [1], 'z' : [1]})

In [5]: df.applymap(lambda x: x)
Out[5]:
x y z
0 1 1 1

I would have expected to get the empty DataFrame back.
Issue 1:
Would be nice if the title for the API reference pages gave some context to the class it's referencing. The following is a screenshot of the tabs I see in Firefox (Safari gives even less context because the icon is missing). All of them just say "Atom".

The left tab has the API reference for Color, the middle for CommandRegistry, and the right for TextBuffer, but it's unclear without selecting them which one's which.

Propose something along the lines of "Atom - TextBuffer API" or even just "Atom - TextBuffer" for clarity.

/cc @thedaniel 📝

Issue 2:
Those are all different pages on atom.io – no idea which is which. Pages on atom.io should have dynamic titles to reflect their content to avoid this kind of tab hell.
Issue 1:
Migrated issue, originally created by Anonymous

Firstly. Fantastic software guys!

Here's the problem:

changing lazy=True to lazy='dynamic' on an orm.relation function with a 'secondary_join' and an 'order_by' filter results in broken SQL.

Essentially the secondary table is aliased in the SQL but the order_by reference to the secondary is not.

I have a small program that exhibits the problem on a MySQL database.

Issue 2:
Migrated issue, originally created by pkyosx (@pkyosx)

Suppose we have Parent and Child classes as One-To-Many relationship. If I move child from one parent to another, the order of changing foreign_key and foreign_object result in different behavior. Following are the briefing of reproducing steps. Attachments are runnable reproducing scripts. It still happens in 1.1.0b1.dev0 build.

// Models
class Parent(Base):
__tablename__ = 'parent'
id = Column(Integer, primary_key=True)
children = relationship("Child", back_populates="parent")

class Child(Base):
__tablename__ = 'child'
id = Column(Integer, primary_key=True)
parent_id = Column(Integer, ForeignKey('parent.id'))
parent = relationship("Parent", back_populates="children")

// Initial Setting
p1 = Parent()
p2 = Parent()
c = Child()
c.parent = p1
s.commit()

// Scenario1: Move c from p1 to p2
c.parent_id = p2.id
c.parent = p2
assert c in p2.children, "this will fail"

// Scenario 2: Move c from p1 to p2
c.parent = p2
c.parent_id = p2.id
assert c in p2.children, "this will success"

Attachments: fail.py | test.py
Issue 1:
All open files are written on 'Save All', causing unnecessary triggers of change watchers, for example.

Issue 2:
Due to #1690 now when you call window:save-all, all the files opened by the editor get touched. That is definitely not a good idea, since it can trigger file watcher for files that didn't change, and it can cause performance problems when you have a lot of files open and you are working on a slow disk, or with third party programs that monitor your filesystem (Dropbox, anyone?)