WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Hi,

I'm trying to spin up the container with Deno, the build works fine but when I run the docker file I get this error:

➜ docker run -it deno-app
deno: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

Information:

➜ deno --version
deno 1.8.2 (release, x86_64-apple-darwin)
v8 9.0.257.3
typescript 4.2.2

Dockerfile

FROM alpine

RUN apk update && apk add curl

RUN curl -fsSL https://deno.land/x/install/install.sh | sh && mv /root/.deno/bin/deno /bin/deno

ENTRYPOINT ["deno"]

CMD ["run", "--allow-net", "https://deno.land/std/examples/welcome.ts"]

Issue 2:
Running deno executable on alpine (frolvlad/alpine-glibc since glibc is required) fails since 1.8.0:

# running deno
deno: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

if I install libstdc++ via apk add libstdc++ I see (when running deno) a warning repeated 5 times:

deno: /usr/lib/libstdc++.so.6: no version information available (required by deno)
deno: /usr/lib/libstdc++.so.6: no version information available (required by deno)
deno: /usr/lib/libstdc++.so.6: no version information available (required by deno)
deno: /usr/lib/libstdc++.so.6: no version information available (required by deno)
deno: /usr/lib/libstdc++.so.6: no version information available (required by deno)
Download https://deno.land/std/examples/welcome.ts
Warning Implicitly using latest version (0.89.0) for http://deno.land/std/examples/welcome.ts
Download https://deno.land/std@0.89.0/examples/welcome.ts
Check https://deno.land/std/examples/welcome.ts
Welcome to Deno!

This is a regression since previously libstdc++ was not required to be dynamically linked. As well as the warning being somewhat loud/unnecessary (?).

cc @lucacasonato @caspervonb

https://github.com/hayd/deno-docker/runs/2024710911?check_suite_focus=true
Issue 1:
Ben Rowlands opened SPR-3313 and commented

Constructor injection is desirable for imutability but the Spring config is very much tied to implementation (ordering of args).

We could solve this problem using a @Property("..") annotation to decorate a constructor with the names of the ctor paramaters? (could locate param names from CGLIB but only if debug symbols stored in class).

For example:

public class Person

{

public Person( @Property("age") int age, @Property("name") String name )

{

...

}

}

Then the config could look same as the if we had used setter injection.

<bean class="Person">

<property name="age" value=".."/>

<property name="name" value=".."/>

</bean>

This could be achieved using a BeanFactoryPostProcessor to visit every bean definition and move properties from the setter map to the constructor map respecting the order the annotations are definied in?

Alternativly we could add an attribute to constructor-arg

<bean class="Person">

<constructor-arg name="age" value=".."/>

<constructor-arg name="name" value=".."/>

</bean>

Issue Links:

#6580 Attach tooling metadata to constructor arg definitions ("depends on")

#6769 Attach Source Metadata to Constructor Args

Referenced from: commits 53333c3

1 votes, 7 watchers

Issue 2:
Rob Harrop opened SPR-2077 and commented

Issue Links:

#7998 Add @annotation to name constructor arguments allowing names to be placed in config
Issue 1:
Testing #6099

When installing an extension with code-alpha --install-extension I need to pass the id that includes publisher and name.

It's not easy to find that id out. Especially the publisher part is not mentioned on the marketplace page itself: https://marketplace.visualstudio.com/items?itemName=donjayamanne.python

It is in the URL of that page though.

It would be good if it where as easy as described here

Issue 2:
When I create a new file, it does not recognize the jsconfig settings (ES6 for example). I need to go to jsconfig, make a change, dismake that change and then it the new file will be ok.
Issue 1:
Environment

Microsoft Windows [Version 10.0.18363.900]

PowerToys 0.19.2

Steps to reproduce

Open PowerToys settings window by double-clicking icon in notification area

Resize the window

Close the window

Open PowerToys settings window again

Expected behavior

Expected custom window size to be maintained on subsequent launch

Actual behavior

Window size is set to a size other than what I've personally set, perhaps a hard-coded default?

Screenshots

N/A

Issue 2:
Environment

Microsoft Windows [Version 10.0.19041.264]

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

Click powertoys in notification tray, window is on set size that cannot be adjusted, meaning everytime you click on the icon , the window reverts to default size and location

Expected behavior

Actual behavior

Screenshots
Issue 1:
Migrated issue, originally created by Alessandro Pelliciari (@apelliciari)

SQLAlchemy==1.1.9
SQLAlchemy-Utils==0.32.16

Working on sqlite, with a query like this:

SELECT
DATE(creation_date, -strftime('%d', data) || ' days', '+1 day') AS __timestamp
FROM table_xyz

SQLAlchemy when compiling escapes percent sign inside strtfime, making the query wrong and meaningless:

SELECT
DATE(creation_date, -strftime('%%d', data) || ' days', '+1 day') AS __timestamp
FROM table_xyz

notice the double percent inside strftime function.

I think the problem is in the sqlite dialect: it doesn't cover this case, but I don't know very well SQLAlchemy so i don't know where to look to patch it.

I don't have an easy reproducible case because this issue came up using Superset (https://github.com/apache/incubator-superset/), who's using SQLAlchemy to do the interrogation on the database, so not knowing SQLAlchemy well I can't isolate the case.

Relevant Superset code doing the query:

def get_query_str(self, query_obj):
engine = self.database.get_sqla_engine()
qry = self.get_sqla_query(**query_obj)
sql = str(
qry.compile(
engine,
compile_kwargs={"literal_binds": True}
)
)
logging.info(sql)
sql = sqlparse.format(sql, reindent=True)
return sql

In my case, engine is:

#!

(Pdb++) pp engine.__dict__
{'_echo': None,
'dialect': <sqlalchemy.dialects.sqlite.pysqlite.SQLiteDialect_pysqlite object at 0x7f6f62e74290>,
'engine': Engine(sqlite:////home/superset/consuntivo.db),
'logger': <logging.Logger object at 0x7f6f6ad7c350>,
'pool': <sqlalchemy.pool.NullPool object at 0x7f6f62e74350>,
'url': sqlite:////home/superset/consuntivo.db}

qry is:

#!

<sqlalchemy.sql.selectable.Select at 0x7f83d83b9950; Select object>

and raw columns in qry object are ok:

#!

(Pdb++) pp qry._raw_columns[0].__dict__
{'_allow_label_resolve': True,
'_element': <sqlalchemy.sql.elements.ColumnClause at 0x7f83d85d7ad0; DATE(data, -strftime('%d', data) || ' days', '+1 day')>,
'_key_label': u'__timestamp',
'_label': u'__timestamp',
'_proxies': [<sqlalchemy.sql.elements.ColumnClause at 0x7f83d85d7ad0; DATE(data, -strftime('%d', data) || ' days', '+1 day')>],
'_resolve_label': u'__timestamp',
'_type': DateTime(),
'comparator': <sqlalchemy.sql.sqltypes.Comparator object at 0x7f83d84e50a0>,
'element': <sqlalchemy.sql.elements.ColumnClause at 0x7f83d85d7ad0; DATE(data, -strftime('%d', data) || ' days', '+1 day')>,
'key': u'__timestamp',
'name': u'__timestamp',
'type': DateTime()}

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

Currently, literal_column() doubles up percent signs as the base compiler.py level, which is inconsistent with the behavior of text() and column(), which both do it at the per-dialect level. But also, at the per-dialect level, the mysqldb and psycopg2 compilers hardcode this behavior in two separate places for text(), column(), and the modulus operator.

doubling of percents should be done based on paramstyle alone and can be done by default in the base compiler. literal_column() should not unconditionaly double percents as this is legacy behavior.
Issue 1:
Summary of the new feature/enhancement

When certain applications are on the taskbar, right-clicking their icons shows additional special menu options (ex: VS Code provides options to open recently opened files, workspaces, etc., calculator has a tasks section, to open the calculator in standard, programming, etc. modes, Outlook has a menu to create new tasks, emails, etc.). It would be convenient to include similar functionality for Terminal, so that a user could open a new Terminal window that is not the configured default.

For example, if a user's default is Ubuntu 18.04, and the user needs to open a Powershell window, then the user could simply right-click the taskbar icon, and the menu would allow opening Terminal directly to either Powershell or any of the other terminal options. This interaction would prevent a user from having to open with a fresh Ubuntu terminal, then open a Powershell window (by either navigating to the menu or using keyboard shortcuts), and closing the unwanted Ubuntu terminal.

Proposed technical implementation details (optional)

Add menu contributions to the normal default right-click taskbar menu, which allows a user to open Terminal directly into any one of the configured terminal options.

Issue 2:
The Task Bar context menu

should show the items from the configured profiles that populate the new shell menu
Issue 1:
I'm implementing a custom BufferAggregator. The doc in the code level is pretty good! I just have extra questions that, as a dev user, could ask:

What does buf actually hold? Are they bytes of metrics or bytes of aggregators?

When we say "Implementations must not change the position, limit or mark of the given buffer", do we always want to use buf.duplicate(); or buf.slice() as the first statement in implementation? Why does the position of the given buffer could possibly be non-zero? Is it because the same byteBuffer has been used in initialization of other kinds of aggregators? If so, when did the init happen?

What's the difference between Aggregator and BuffereAggregator? Is Aggregator post agg and BufferAggregator non-post agg?

Issue 2:
Affected Version

Druid Built From Source as of Fri Jun 5, 2020

Description

We are trying to create new druid ingestion specs to pull from s3 directly via index_parallel rather than hadoop. The outputs simply don't seem to be partitioned though.

To make it easy to reproduce, here is a simple config that shows the issue:

{
"spec": {
"type": "index_parallel",
"ioConfig": {
"type": "index_parallel",
"inputSource": {
"type": "http",
"uris": [
"https://druid.apache.org/data/wikipedia.json.gz",
"https://druid.apache.org/data/wikipedia.json.gz"
]
},
"inputFormat": {
"type": "json"
}
},
"tuningConfig": {
"type": "index_parallel",
"partitionsSpec": {
"type": "single_dim",
"partitionDimension": "channel",
"maxRowsPerSegment": 2000
},
"forceGuaranteedRollup": true,
"maxNumConcurrentSubTasks": 4
},
"dataSchema": {
"dataSource": "wikipedia-test-partitioned-2",
"granularitySpec": {
"type": "uniform",
"segmentGranularity": "DAY",
"queryGranularity": "HOUR",
"rollup": true,
"intervals": [
"2000-01-01/2030-01-01"
]
},
"timestampSpec": {
"column": "timestamp",
"format": "iso"
},
"dimensionsSpec": {
"dimensions": [
"channel",
"cityName",
"comment",
"countryIsoCode",
"countryName",
"diffUrl",
"flags",
"isAnonymous",
"isMinor",
"isNew",
"isRobot",
"isUnpatrolled",
"metroCode",
"namespace",
"page",
"regionIsoCode",
"regionName",
"user"
]
},
"metricsSpec": [
{
"name": "count",
"type": "count"
},
{
"name": "sum_added",
"type": "longSum",
"fieldName": "added"
},
{
"name": "sum_commentLength",
"type": "longSum",
"fieldName": "commentLength"
},
{
"name": "sum_deleted",
"type": "longSum",
"fieldName": "deleted"
},
{
"name": "sum_delta",
"type": "longSum",
"fieldName": "delta"
},
{
"name": "sum_deltaBucket",
"type": "longSum",
"fieldName": "deltaBucket"
}
]
}
},
"type": "index_parallel"
}

Since maxRowsPerSegment is 2,000 and there are 24,000 rows in the dateset, I was expecting many partitions.

I made sure to set two files so that it could be parallelized, since I saw some comments about needing to set maxNumConcurrentSubTasks and figured this might also apply to needing multiple input files.

Of course the data that I have is much larger, coming out to a few GB, but I'm seeing the exact same issue.

I have tried both setting targetRowsPerSegment and maxRowsPerSegment, and neither work.
Issue 1:
In the 1.9 branch (including whats in the centos 6 repo) in the Runner class, it appears ansible is trying to duplicate the fileno for a new stdin, however, this introduces a file descriptor leak since the dup is never closed.

Additionally, self._new_stdin is not used anywhere else in this class.

self._new_stdin = new_stdin
if not new_stdin and fileno is not None:
try:
self._new_stdin = os.fdopen(os.dup(fileno))
except OSError, e:
# couldn't dupe stdin, most likely because it's
# not a valid file descriptor, so we just rely on
# using the one that was passed in
pass

In stable-1.9/lib/ansible/runner/init.py#L582

This file descriptor leaks one fd for each.

It appears in the master branch as well, only its is being used by the TaskExecutor. However, since its not being closed, it will be a file descriptor leak there as well.

Issue 2:
ISSUE TYPE

Bug Report

ANSIBLE VERSION

$ ansible --version
ansible 2.2.0 (devel 3b3ab605f6) last updated 2016/06/13 13:46:21 (GMT -500)
lib/ansible/modules/core: (detached HEAD d6f01d0b4f) last updated 2016/06/13 10:41:06 (GMT -500)
lib/ansible/modules/extras: (detached HEAD 43760b2c4a) last updated 2016/06/13 10:41:06 (GMT -500)
config file = /Users/tanner/projects/ansible.git/playbooks.git/ansible.cfg
configured module search path = Default w/o overrides

CONFIGURATION

ANSIBLE_KEEP_REMOTE_FILES=1

OS / ENVIRONMENT

Management host OX 10.11.5

Managed host Windows 7

SUMMARY

Results from task show the log is always "", even when a package is uninstalled

changed: [win7-90day] => {"changed": true, "invocation": {"module_name": "win_msi"}, "log": ""}

STEPS TO REPRODUCE

{89F4137D-6C26-4A84-BDB8-2E5A4BB71E00} = Microsoft Silverlight

- name: remove packages (win_msi)
win_msi: >
path="{89F4137D-6C26-4A84-BDB8-2E5A4BB71E00}"
wait="True"
state="absent"

With Microsoft Silverlight installed

$ ANSIBLE_KEEP_REMOTE_FILES=1 ansible-playbook -i customers/testing-servers --ask-vault-pass windows-workstations.yml
<snip>
changed: [win7-90day] => {"changed": true, "invocation": {"module_name": "win_msi"}, "log": ""}
PLAY RECAP *********************************************************************
win7-90day : ok=2 changed=1 unreachable=0 failed=0

Microsoft Silverlight is uninstalled.

Reinstall Microsoft Silverlight

RDP into win7-90day

> cd C:\Users\Administrator\AppData\Local\Temp\ansible-tmp-XXXX
> win_msi.ps1
<snip>
{"changed":true,"log":"MSI (s) (3C:44) [16:21:00:682]: Final Patch Application Order:\r\nMSI (s) (3C:44) [16:21:00:682]
: {0107D3B1-6348-41E9-89D3-0CC803B3B483} - \r\n=== Logging started: 6/13/2016 16:21:00 ===\r\nAction start 16:21:00:

EXPECTED RESULTS

Microsoft Silverlight would be uninstalled and the results log would contain the logfile info like when I run the win_msi.ps1 from the powershell command line

ACTUAL RESULTS

Empty log in the results

changed: [win7-90day] => {"changed": true, "invocation": {"module_name": "win_msi"}, "log": ""}
Issue 1:
Plugins can fail in ways that aren't the fault of the code being compiled. This could be an internal error in the plugin (which is still different from an ICE in Rust itself), or something like failure to load an external configuration file.

Ideally, plugins would call the usual methods like bug, err, span_bug, etc., and the resulting messages would include the name of the plugin crate. Unfortunately we can't do this by setting session state about which plugin is running, because they can call back into librustc and errors there shouldn't be reported as plugin errors. We could introduce plugin_bug, plugin_err, plugin_span_bug, etc, but this API duplication is ugly, and you have to remember to use different methods when writing plugins.

The nicer (though harder-to-implement) solution is to have these functions walk the stack and then look at which shared object their caller was defined in. In glibc this can be done with backtrace() and dladdr(), but I don't know how hard it is on other platforms.

Whatever we do, we should also make these error methods accessible from the Registry, for use handling errors that occur during plugin initialization.

Issue 2:
The AST formatting functions have a lot of duplication. Abstract out patterns

like fmt_sequence and fmt_bracketed.
Issue 1:
Some machines don't have SSE4.1 CPU instructions, resulting in this error:

#7138

Instead of forcing users to manually compile their version of tensorflow you should offer a compiled binary (on pip) with SSE4.1 instructions disabled.

Issue 2:
As announced in release notes, TensorFlow release binaries version 1.6 and higher are prebuilt with AVX instruction sets. This means on any CPU that do not have these instruction sets either CPU or GPU version of TF will fail to load with any of the following errors:

ImportError: DLL load failed:

A crash with return code 132

Our recommendation is to build TF from sources on these systems.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): ubuntu/windows/macos

TensorFlow installed from (source or binary): binary

TensorFlow version (use command below): 1.6 and up

Python version: 2.7, 3.3, 3.4, 3.5, 3.6 and any newer

Bazel version (if compiling from source): n/a

GCC/Compiler version (if compiling from source): n/a

CUDA/cuDNN version: any

GPU model and memory: any

Exact command to reproduce: python -c "import tensorflow as tf"
Issue 1:
From the point of view of the Flex implementation, there's children with fixed sizes, and children that are flexible and whose sizes need to be established.

But from the point of view of Flex users, the definitions don't make sense. The "fixed" children are the ones that can have any size they want, and the "flexible" children are the ones that get given a fixed size.

I've had multiple people say sentences along the lines of "oh, I have to use Flexible so that they get a fixed size" to me while I've been helping them.

Issue 2:
We've received feedback from new users that our Flex implementation is kinda-but-not-really the Flexbox they know and love from the web. This can cause a bit of friction as they learn how our Flex is and is not Flexbox.

We can consider renaming Flex to help avoid users drawing parallels and miss-set expectations. One idea was the rename to Linear.

Presumably this would be a breaking change and if we do this, we can email our users, etc.
Issue 1:
Describe the bug

If both the relationship and query define order_by, subsequent executions of the same query lead to addition of duplicate order clauses to the query. This also manifests itself as a memory leak.

To Reproduce

from sqlalchemy import Column, ForeignKey, Integer, create_engine
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.orm import backref, relationship, sessionmaker

engine = create_engine('postgresql://test@localhost/db', echo=True)
Base = declarative_base()
Session = sessionmaker(engine)

class Parent(Base):
__tablename__ = 'parent'
id = Column(Integer, primary_key=True)

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

parent = relationship(
Parent, backref=backref('children', lazy='dynamic', order_by=id)
)

Base.metadata.create_all(engine)

with Session() as session:
parent = Parent(id=1)
session.add(parent)
parent.children.order_by(Child.id.asc()).all() # ORDER BY child.id, child.id ASC
parent.children.order_by(Child.id.asc()).all() # ORDER BY child.id, child.id ASC, child.id ASC
parent.children.order_by(Child.id.asc()).all() # ORDER BY child.id, child.id ASC, child.id ASC, child.id ASC

I'd have expected the last 3 lines to generate identical queries, but each subsequent line adds an additional clause to the ORDER BY.

Error

No error, but a memory leak.

Versions.

OS: MacOS 11.4

Python: 3.6.13

SQLAlchemy: 1.4.15

Database: PostgreSQL

DBAPI: psycopg2

Issue 2:
Migrated issue, originally created by Anonymous

(original reporter: rbu) We had quite a hard time figuring out the JOIN order as generated by a query(A).join(B) statement. All examples in the documentation have A as left and B as right side. Apparently though, when giving an explicit criterion as query(A).join(B.a), B will be the left side even when adding a select_from.

Details:

# surprising
>>> print DBSession.query(User.id).outerjoin(Track.user)
SELECT user.id AS user_id
FROM track LEFT OUTER JOIN user ON user.id = track.user_id

# bug?
>>> print DBSession.query(User.id).select_from(User).outerjoin(Track.user)
SELECT user.iduser AS user_id
FROM track LEFT OUTER JOIN user ON user.id = track.user_id

# expected
>>> print DBSession.query(User.id).outerjoin(User.tracks)
SELECT user.iduser AS user_id
FROM user LEFT OUTER JOIN track ON user.id = track.user_id

This magic ordering based on the explicit criterion given should be covered in the documentation, but we did not find such note.
Issue 1:
With this code:

require('babel/polyfill');

function* g() {
yield 1;
}

Babel gives:

'use strict';

var marked0$0 = [g].map(regeneratorRuntime.mark);
require('babel/polyfill');

function g() {
return regeneratorRuntime.wrap(function g$(context$1$0) {
while (1) switch (context$1$0.prev = context$1$0.next) {
case 0:
context$1$0.next = 2;
return 1;

case 2:
case 'end':
return context$1$0.stop();
}
}, marked0$0[0], this);
}

where var marked0$0 = [g].map(regeneratorRuntime.mark); appears before require('babel/polyfill');. That makes an error: regeneratorRuntime undefined.

Issue 2:
require("babel/polyfill");
function *hello () {};

After babelification:

"use strict";

var hello = regeneratorRuntime.mark(function hello() {
return regeneratorRuntime.wrap(function hello$(context$1$0) {
while (1) switch (context$1$0.prev = context$1$0.next) {
case 0:
case "end":
return context$1$0.stop();
}
}, hello, this);
});

require("babel/polyfill");
;

This would result in ReferenceError: regeneratorRuntime is not defined was found when discussion this issue with @zeusdeux
Issue 1:
This is a tracking issue for the unstable str_parse_error and utf8_error features in the standard library. Some various small error types popped up once FromStr had an associated error type and haven't been considered too closely for stabilization.

Some thoughts are:

Are the names of these types appropriate?

Are we covered in terms of future extensibility?

Are the relevant portions of the error exposed well?

Issue 2:
I'm in the finishing touches of adding a container::MutableSeq, and I'm realizing it's a bit inconsistent that vec has methods like push() whereas DList has push_back(). I personally feel that we should rename the vec methods to make it explicit where exactly we are pushing/popping the values. I suggest that we make these following renames:

.push() => .push_back()
.pop() => .pop_back()
.unshift() => .push_front()
.shift() => .pop_front()

We could also use append() and prepend() for push() and pop(), but I don't like that as much. Or we could rename the DList methods, but I'm also not in favor of that. What does everyone else think?