WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
On Windows, deallocation of Vecs is extremely slow, orders of magnitude slower than on Linux. I have some sample code below; after it prints "Initialized x...", it takes several seconds to deallocate x. If I use an array instead, it's nearly instantaneous on both platforms.

I'm using Windows 7, 64-bit, with 32-bit Rust.

Edit: If I pass the -O flag to rustc, it performs as expected. Still, I think this optimization is important enough that it might be worth enabling by default.

fn main() {
let x = box Vec::from_elem(50000000, 5.0f32);
// let x = box [5.0f32, ..50000000];

println!("Initialized x with length: {}", x.len());
}

Issue 2:
The internal representation of String is Vec<u8>, but vec.truncate loops to drop members.

Perhaps setting the length directly?
Issue 1:
Builds are becoming relatively slow. Using go version go1.5.1 darwin/amd64, my build (presumably mostly link) time is:

real 0m2.879s

user 0m3.584s

sys 0m0.461s

For a very modest program. Building with -x shows that compile, and link are running only for the main package, which contains no fancy build directives.

I'm not sure how else to report this, but it is a concern that build times are inflating version over version.

Issue 2:
all.bash is taking too long. There are many reasons. This is a general tracking bug for work to fix this.
Issue 1:
Migrated issue, originally created by eevee (@eevee)

Reported here, but seen someone else experience it too: http://stackoverflow.com/q/24720380/17875

My diagnosis from figuring it out with the someone else on IRC:

18:43 <!eevee> somehow calling self._on_metadata_create within the metadata's create event is adding itself as an event listener again
18:44 <!eevee> because, i think, it re-creates a dialect-specific enum with the same args...
18:44 <!eevee> looks pretty clearly like a bug wow
18:44 <@Zhorken> it specifically hangs with SQLite
18:44 <@Zhorken> or at least, not with Postgres
18:45 <!eevee> ah, postgres has a real enum type; sqlite doesn't so it gets a fallback

Issue 2:
Migrated issue, originally created by Anonymous

Objects whith bool(obj) == False are dropped from session after commit. There is nothing about it in documentation, and no warnings or exceptions raised. There is test code:

from sqlalchemy import *
from sqlalchemy.orm import *

import pickle

engine = create_engine('sqlite://')

metadata = MetaData()

obj = Table('obj', metadata,
Column('id', Integer, primary_key=True),
Column('data', Unicode(32)),
)

class Obj(object):
def __nonzero__(self):
return False

mapper(Obj, obj)

metadata.create_all(bind=engine)

session = create_session(bind=engine)

o = Obj()

o.data = 'test'

session.begin()
session.save(o)
session.commit()

assert o in session
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behaviour

When navigated using <Link scroll={false}> the component below should restore the saved scroll position when the component mounts.

let scrollY = 0

export default class Thing extends Component {
constructor(props) {
super(props)
this.onScroll = this.onScroll.bind(this)
}

onScroll(e) {
scrollY = window.scrollY
}

componentDidMount() {
window.addEventListener('scroll', this.onScroll)
window.scroll(0, scrollY)
}

componentWillUnmount() {
window.removeEventListener('scroll', this.onScroll)
}

...
}

Current Behaviour

The code works on latest Chrome (macOS) and Edge (Windows 10), but fails on Safari 10 (macOS).

The behaviour I'm observing in Safari is that the scroll position is first briefly set to my correct saved position, but then another scroll event is fired and the scroll position reset somewhere nearer the top of the page (always the same pixel value). I think it might have something to do with component load order, or a race condition, since I'm observing the problem on a fairly image heavy page.

Steps to Reproduce (for bugs)

There's a live example here http://www.gillythomas.co.uk

Using Safari 10 visit the site and scroll down the page to near the bottom

Click an image to view a larger version

Click the "back to gallery" button

Observe that the scroll position wasn't properly restored

Try on different browsers, should work well on Chrome for example

Context

This is using the Next.js v3 beta and new static site output feature. I'm just trying to persist the scroll position on a page, but its not working on Safari.

Your Environment

Next.js version: 3.0.1-beta.8 static export

Environment name and version (e.g. Chrome 39, Node.js 5.4): Safari 10

Operating System (Linux, maxOS, Windows): macOS

Issue 2:
Bug report

Describe the bug

Dependencies not properly shared across pages and _app.js

To Reproduce

Create a number of pages. Add a module to _app.js.

Increase the number of times a module is included from once to N times, track progress

Takes at least 2 pages for a dep included in _app.js to be factored out.

Expected behavior

Once a module has been included in _app, it should never be packed again.

Screenshots

In a 4 page + _app + _document app

// _app only (_app.js includes Auth)

// 1 page (_app.js + submit.js include Auth)

// 2 pages (_app.js + submit.js + scorecard.js include Auth)

System information

OS: Mac OS X

Version of Next.js: canary, 7.0.2

Additional context

Related to: #3818 (though in this case import isn't being exported as in HOC)

Related to: #118 and #253

Potential solutions: expose or document modifying the threshold for placing a dependency in the common bundle.

However, it seems there should be a more intelligent procedure, in which unnecessary data is not bundled for any descendants of _app.js.
Issue 1:
fn main() {

let xs[i32; 1] = [1];

}

2:9: 2:11 error: internal compiler error: ident only path should have been covered already

2 let xs[i32; 1] = [1];

^~

note: the compiler unexpectedly panicked. this is a bug.

Issue 2:
$ cat testje.rs
fn main(){
let mut v=std::vec::Vec::<isize>::new();
v.push(1);
v.push(2);
// The next line makes rust crash. It does not make any sense (it was just a typo) but thought i'd report it anyway.
let v[0]=v[1];
}

$ rustc --version
rustc 1.0.0-nightly (890293655 2015-02-28) (built 2015-03-01)

$ RUST_BACKTRACE=1 rustc testje.rs
testje.rs:6:9: 6:10 error: internal compiler error: ident only path should have been covered already
testje.rs:6 let v[0]=v[1];
^
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: run with `RUST_BACKTRACE=1` for a backtrace
thread 'rustc' panicked at 'Box<Any>', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libsyntax/diagnostic.rs:129

stack backtrace:
1: 0x577a6c4f - sys::backtrace::write::hb08af03691eab78a5kA
2: 0x577cf782 - panicking::on_panic::h37164609ca1c02afBnJ
3: 0x5770f63a - rt::unwind::begin_unwind_inner::h24d5e7492198457b43I
4: 0x54a55a8d - rt::unwind::begin_unwind::h9113908695753286194
5: 0x54a55a33 - diagnostic::SpanHandler::span_bug::hcbc27df468564853WBD
6: 0x54a7b905 - parse::parser::Parser<'a>::parse_pat::hf7a2ebdbbed007b1d3J
7: 0x54a8df2d - parse::parser::Parser<'a>::parse_local::h7d6c62c9c63efba1xkK
8: 0x54a8f22f - parse::parser::Parser<'a>::parse_stmt::h622ba475055891c9inK
9: 0x54a97e89 - parse::parser::Parser<'a>::parse_block_tail_::hb2f43cc30c93d511ryK
10: 0x54a75dec - parse::parser::Parser<'a>::parse_inner_attrs_and_block::h554d87549b4ccdacTwK
11: 0x54a9c465 - parse::parser::Parser<'a>::parse_item_fn::hbda705c8fc5a7ac1icL
12: 0x54a92778 - parse::parser::Parser<'a>::parse_item_::hf9f9cf23aa0f1cd4iaM
13: 0x54aa2985 - parse::parser::Parser<'a>::parse_mod_items::habe606a27fa5b86dSAL
14: 0x54aacc6c - parse::parser::Parser<'a>::parse_crate_mod::h8c08698d71a0eba6PAM
15: 0x54abf61e - parse::parse_crate_from_file::ha077e55f357e36faJNT
16: 0x57e341b1 - driver::phase_1_parse_input::closure.15399
17: 0x57e0e7b7 - driver::phase_1_parse_input::h21d9f24721445c1fvqa
18: 0x57e0b181 - driver::compile_input::hee81c045ab46c74fIba
19: 0x57ed6e6e - run_compiler::h875c1e123fe4ae2cF5b
20: 0x57ed4a1c - thunk::F.Invoke<A, R>::invoke::h12424714292252424185
21: 0x57ed3770 - rt::unwind::try::try_fn::h4021821266450575721
22: 0x5783afe8 - rust_try_inner
23: 0x5783afd5 - rust_try
24: 0x57ed3e5c - thunk::F.Invoke<A, R>::invoke::h8199562432922027576
25: 0x577bb2d5 - sys::thread::thread_start::h1b1bb1e7ac08d3a6yRE
26: 0x5150db4f - start_thread
27: 0x573a270c - <unknown>

There are a few issues with the same error message, but they seem to have been fixed before my nightly - and the way to cause it is also different
Issue 1:
We have a very strange edge case only happening in Firefox but its def causing some problems.

This is whats happening is I navigate to the root http://localhost:3000, get redirected on the server to /about2

I click I button which Router.replace shallow:true which replaces the url to /about2?key=value

I refresh the browser at the current state, url is /about2, I expect it to be /about2=key=value

Here a video recording of the scenario.

https://drive.google.com/file/d/1c0oN-UZIVuG5lt6oZiJOlwZSzAM98gSX/view?usp=sharing

To be a friendly guest here's the repro repo, examples/hello-world

npm install && npm run dev

https://github.com/ptomasroos/next.js/tree/firefox-loses-querystrings

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

Firefox 58 (latest)

Issue 2:
So, on my eternal quest to try to make CSS work with this repo, I have arrived to the following config:

config.module.rules.push({
test: /\.(png|jpg|gif|eot|ttf|woff|woff2)$/,
use: {
loader: 'url-loader',
options: {
limit: 8192
}
}
});

config.module.rules.push({
test: /\.css$/,
use: ExtractTextPlugin.extract({
fallback: 'style-loader',
use: 'css-loader'
}),
});

config.plugins.push(
new ExtractTextPlugin({
filename: 'styles.css',
allChunks: true
})
);

The extraction works as planned, and the file gets generated properly. However, source-map-support seems to somehow cough up on the CSS file, and gives this error:

@font-face {
^

SyntaxError: Invalid or unexpected token
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:588:28)
at Module._compile (/Users/danny/src/insights-frontend/node_modules/source-map-support/source-map-support.js:492:25)
at Object.Module._extensions..js (module.js:635:10)
at Module.load (module.js:545:32)
at tryModuleLoad (module.js:508:12)
at Function.Module._load (module.js:500:3)
at Module.require (module.js:568:17)
at require (internal/module.js:11:18)

Is there any ideas? Am I missing something? Is there a way to tell source-map-support to ignore *.css files?

I have searched the issues of this repository and believe that this is not a duplicate.
Issue 1:
This doesn't work:

trait Foo {
type Bar;
fn Bar();
}

The error you get:

trait_type_method_same_name.rs:3:5: 3:14 error: duplicate definition of type or module `Bar`
trait_type_method_same_name.rs:3 fn Bar();
^~~~~~~~~
trait_type_method_same_name.rs:2:5: 2:14 note: first definition of type or module `Bar` here
trait_type_method_same_name.rs:2 type Bar;
^~~~~~~~~

It seems this should be allowed since they are in different namespaces.

Issue 2:
This is a FIXME issue; right now, an ident contains information used by expansion. After expansion, this is collapsed down to a single Name (an index into the interner). However, the downstream stuff in librustc refers to "ast::ident" everywhere. It would save space and time to just pass around one int rather than two, by replacing uses of "ident" with "Name". I don't know if I'll have time to do this. (Planning for my untimely demi^H^Hparture.)
Issue 1:
Electron version: 1.7.5

Operating system: macOS Sierra 10.12.6

Expected behavior

When creating a saveDialog with multiple extensions configured in .filter, the dialog should allow the user to pick an extension, like here:

Actual behavior

There is no extension picker:

How to reproduce

const { dialog } = require('electron').remote

dialog.showSaveDialog({
filters: [
{ name: 'M3U8', extensions: ['m3u8'] },
{ name: 'PLS', extensions: ['pls'] }
]
}, filePath => {})

Issue 2:
Electron version: 1.7.5

Operating system: macOS Sierra 10.12.6

Expected behavior

When creating a saveDialog with multiple extensions configured in .filter, the dialog should allow the user to pick an extension, like here:

Actual behavior

There is no extension picker:

How to reproduce

const { dialog } = require('electron').remote

dialog.showSaveDialog({
filters: [
{ name: 'M3U8', extensions: ['m3u8'] },
{ name: 'PLS', extensions: ['pls'] }
]
}, filePath => {})
Issue 1:
The commit 139a077 doesn't work with the normal button which doesn't contain any image.

Issue 2:
Since 139a077, also picked up by @deytao

I guess either go back to event.target or switch the delegate selector to something like '[data-toggle^=button] .btn' causecurrentSelector` is set to the element matched by the delegate selector (even Bean does this now btw!) and at the moment it's the parent of the buttons. See docs/javascript.html, they don't work.
Issue 1:
Hi,

As witnessed in the following JSbin:

http://jsbin.com/liwexa/5/edit?html,js,output

When filtering on multiple fields, the search value should be null instead of an empty string. When a user types something in the search box, the filter works, but when deleting the input again, the output results in duplicate entries. The initial rendering can be fixed by initialising search as null.

Cheers,

Koen

Issue 2:
Version

2.3.3

Reproduction link

https://codepen.io/timwis/pen/YQKXBY

Steps to reproduce

Type something in the box below, click outside the area (to blur), and watch it appear double.

What is expected?

The editable div keeps what you typed in it.

What is actually happening?

The editable div adds what you typed in it assumedly as part of the virtual dom update, showing it twice.

My hunch is this is an issue with how virtual dom patches a <div contenteditable> that starts with an empty value. If you change its starting value in the demo to an actual value (like foo) this issue doesn't happen.

Related to #5234. Let me know if you prefer we keep the conversation there and we can close this issue.
Issue 1:
Apache Airflow version: 1.10.12

Environment:

OS (e.g. from /etc/os-release): Any OS: Mac OS, Linux

Install tools: Pipenv

Others:

What happened:

Trying to lock pip dependencies with pipenv is not working, I'm 90% sure because Apache Airflow specifies attrs package dependency at "~=19.3" somewhere in the project. Here's the error message:

ERROR: ERROR: Could not find a version that matches attrs>=17.3.0,>=17.4.0,>=20.1.0,~=19.3 Tried: 15.0.0, 15.0.0, 15.1.0, 15.1.0, 15.2.0, 15.2.0, 16.0.0, 16.0.0, 16.1.0, 16.1.0, 16.2.0, 16.2.0, 16.3.0, 16.3.0, 17.1.0, 17.1.0, 17.2.0, 17.2.0, 17.3.0, 17.3.0, 17.4.0, 17.4.0, 18.1.0, 18.1.0, 18.2.0, 18.2.0, 19.1.0, 19.1.0, 19.2.0, 19.2.0, 19.3.0, 19.3.0, 20.1.0, 20.1.0, 20.2.0, 20.2.0

What you expected to happen:

Pipenv dependencies lock without errors

How to reproduce it:

Try to add apache-airflow = {extras = ["postgres", "redis", "s3", "ssh", "crypto", "kubernetes"],version = "==1.10.12"} to Pipfile and run pipenv install

Anything else we need to know:

Here's how pipenv graph lists apache-airflow dependencies:

apache-airflow==1.10.12
...
- attrs [required: ~=19.3, installed: 19.3.0]
- cached-property [required: ~=1.5, installed: 1.5.2]

Whereas in setup.py file, https://github.com/apache/airflow/blob/master/setup.py, attrs are locked at 'attrs>=20.0, <21.0'.

Question:

I know it might pipenv-related question, but did you pin attrs package version at 19.3 anywhere in the project? And do you have any idea on how can I alter the version number so that pipenv stops complaining

In fact, I face quite a lot of issues with pipenv due to Airflow subdependencies. Is it a known issue that Airflow is not working well with Pipenv?

Issue 2:
Apache Airflow version

2.2.0 (latest released)

Operating System

Ubuntu 20.04.3 LTS

Versions of Apache Airflow Providers

apache-airflow-providers-oracle==2.0.1

apache-airflow-providers-ssh==2.1.1

Deployment

Virtualenv installation

Deployment details

No response

What happened

During the the command airflow db upgrade we got this error:

[2021-10-12 06:25:10,721] {db.py:815} ERROR - Automatic migration is not available
[2021-10-12 06:25:10,721] {db.py:817} ERROR - The task_instance table has 1392 rows without a corresponding dag_run row. You must manually correct this problem (possibly by deleting the problem rows).

What you expected to happen

It would be nice if the output of airflow db upgrade is the list of objects' ID that needs to be deleted, in order to preserve future's version consistency.

Or even better the SQL statement to manually remove them.

I tried to identify those rows but it is not a trivial task.

How to reproduce

No response

Anything else

No response

Are you willing to submit PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct
Issue 1:
I want to use https://github.com/github/time-elements

But in JSX Gotchas http://facebook.github.io/react/docs/jsx-gotchas.html

says React won't render is="" attribute.

Fill this fixed? Or there is workaround?

Issue 2:
Is there reason why React restricts you to just a subset of DOM elements and attributes ? Unfortunately it makes it really hard to use it with new HTML or non standard features unless support for that is added.

I noticed I could create custom elements via React.createFactory("custom")

https://github.com/facebook/react/blob/master/src/browser/ReactDOM.js#L30

https://github.com/facebook/react/blob/master/src/classic/element/ReactElement.js#L201-L209

But it's not documented & not sure if supported in long term. And even if it was supported that still does not solve problem of attributes as ones not listed in the docs seem to be ignored.

I think it would be good idea to allow defining custom virtual DOM Elements with a custom list of attributes so that users could implement them even if support for new element isn't in the core yet.

Finally support for namespaces would be super useful for using react even in more environments & should not be too hard either. I have successfully used vtree / vdom to do that.
Issue 1:
I think this is by design, but it would be nice that the Scene exported from the Editor would also include map URLs in the JSON. Since the editor spits out the JSON, it would make sense why the URLs are not included (the maps are not downloaded). I am using the editor to help 'reverse-engineer' the 4.3 scene format (get examples of different scenes, how different objects show up in the JSON, etc) and I noticed if I give a map to an object's material, this does not show up in the material in the generated JSON.

Issue 2:
Hi,

Just found this missing functionality.

The exported JSON does not include that field of attribute.

Is this can be fixed?

Thanks.
Issue 1:
Description

Currently composing emitter doesn't support having low-level emitter of the same type inside because it instantiates emitters by name

return injector.getInstance(Key.get(Emitter.class, Names.named(s)));

Hence composing emitter may contain only one http emitter, one logging emitter, etc.

Motivation

The goal is to add support of instantiating multiple low-level emitters of the same type using a composing emitter. For example: instantiate multiple http emitters to duplicate metrics event to another endpoint.

Issue 2:
Affected Version

v0.17.0

This is a serious regression bug for us. Queries like the following used to work in Druid 0.16.0 and are broken in 0.17.0

We used Druid 0.17.0 with SQL compatible null handling DISABLED.

Description

The following query produces a rule error in the SQL engine:

SELECT
CASE cityName WHEN NULL THEN FALSE ELSE TRUE END AS col_a,
CASE countryName WHEN NULL THEN FALSE ELSE TRUE END AS col_b
FROM wikipedia
GROUP BY 1, 2

the error is:

Unknown exception / Error while applying rule DruidQueryRule(AGGREGATE), args [rel#592:LogicalAggregate.NONE.[](input=RelSubset#591,group={0, 1}), rel#599:DruidQueryRel.NONE.[](query={"queryType":"scan","dataSource":{"type":"table","name":"wikipedia"},"intervals":{"type":"intervals","intervals":["-146136543-09-08T08:23:32.096Z/146140482-04-24T15:36:27.903Z"]},"virtualColumns":[{"type":"expression","name":"v0","expression":"1","outputType":"LONG"}],"resultFormat":"compactedList","batchSize":20480,"limit":9223372036854775807,"order":"none","filter":null,"columns":["v0"],"legacy":false,"context":{"forceLimitPushDown":"false","sqlOuterLimit":100,"sqlQueryId":"f83cf8c0-1856-4dc9-aeb6-fc487b92750f","useApproximateTopN":"false","vectorize":"false"},"descending":false,"granularity":{"type":"all"}},signature={v0:LONG, v0:LONG})] / java.lang.RuntimeException

Following is a comparison between what a similar query got translated to in Druid 0.16.0 vs now

in 0.16.0:

{
"queryType": "groupBy",
...
"virtualColumns": [
{
"type": "expression",
"name": "v0",
"expression": "case_searched((\"integrationType\" == null),0,1)",
"outputType": "LONG"
},
{
"type": "expression",
"name": "v1",
"expression": "case_searched((\"integrationVersion\" == null),0,1)",
"outputType": "LONG"
}
],
"dimensions": [
{
"type": "default",
"dimension": "v0",
"outputName": "v0",
"outputType": "LONG"
},
{
"type": "default",
"dimension": "v1",
"outputName": "v1",
"outputType": "LONG"
}
],
...
}

In v 0.17.0, there seem to be several things that compound:

a) the query is rewritten into a scan query although it augh to be a groupby query

b) the main issue seems to be that instead of recognizing the two CASE statements as being different and generating different logical names "v0" and "v1" for them, the two statements are being given the same name "v0" which is then consecutively leading to an illegal query syntax.

c) instead of faithful CASE expressions, a virtual column expression gets generated that is just a constant number "1"

{
"queryType":"scan",
...
"virtualColumns":[
{
"type":"expression",
"name":"v0",
"expression":"1",
"outputType":"LONG"
}
],
"columns":[
"v0"
],
...
}
Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

NA

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Feature Request

Kubernetes version (use kubectl version):

1.3 1.4 master

Environment:

Cloud provider or hardware configuration: vSphere

OS (e.g. from /etc/os-release): Linux

Kernel (e.g. uname -a): NA

Install tools: kube-up.sh

Others:

What happened:

Currently credentials for communicating with vCenter are stored on each node. There does not seem an inherent need to do this and might be a question of code clean in the cloud provider or code change in kubernetes.

What you expected to happen:

Only the master node needs access to vCenter

How to reproduce it (as minimally and precisely as possible):

Kubelet fails to come up if vSphere cloud provider is used and is not configured with credentials.

Anything else do we need to know:

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

Yes

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

1.4.0

yosemite

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

BUG REPORT

Kubernetes version (use kubectl version):

1.4.0

Environment:

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release): OSX Yosemite (homebrew bot)

Kernel (e.g. uname -a):

Install tools:

Others:

What happened:

Homebrew build bot fails due to race condition

What you expected to happen:

Homebrew build bot should succeed

How to reproduce it (as minimally and precisely as possible):

In OSX Yosemite, run make WHAT=/bin/kubectl GOFLAGS=-v

Anything else do we need to know:

Link to this issue here

Homebrew/homebrew-core#5558