WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Currently the carousel has only one transition effect which is a slide between pictures.

It would be great if we can have a fade effect too.

In a tiny project I made, you can see an exemple of a possible implementation :

https://github.com/GuillaumeAmat/bootstrap-more/blob/master/bootstrap-more.css#L493

Issue 2:
With the addition of the fade transition on this js module, the most common options found on a website will be covered. For many types of images, instead of sliding the fade in would be a lot better. For all other cases, users will have to use a separate plugin.
Issue 1:
Describe the bug

When calling clock.getDelta() after clock.getElapsedTime(), the returned value is not the delta between successive calls to clock.getDelta().

Live example

https://codesandbox.io/s/three-frame-delta-ev4d9

Expected behavior

Sometimes I want to animate certain objects based on the elapsed time and others based on time deltas. I expect to be able to call clock.getDelta() once per frame and have the result represent the time between frames. However, given the implementation of clock.getElapsedTime(), this is not the case if you are also calling clock.getElapsedTime in the same loop.

If you read closely, the docs do correctly describe this behavior ("Get the seconds passed since the time oldTime was set"), but IMO it is not the expected behavior.

Or perhaps this is more of an enhancement request: could there be a separate function like clock.getFrameDelta() that is independent of clock.getElapsedTime()? Or is the suggested workaround to use multiple clocks here?

Platform:

Three.js version: r128

Issue 2:
https://dl.dropboxusercontent.com/u/1595444/shaka-player/stream-texture.html

(on Chrome clicking play on the video element shows an upside down render of the video on the canvas element. In Safari/Firefox texImage2D is real upset)
Issue 1:
main.go:

package main
const foo = `
//+build ignore
`

Running vet produces:

main.go:3: +build comment must appear before package clause and be followed by a blank line

This also contributes to noise in the vet output for core, e.g.

./src/crypto/x509/root_darwin_arm_gen.go:181: +build comment must appear before package clause and be followed by a blank line
./src/crypto/x509/root_darwin_arm_gen.go:182: +build comment must appear before package clause and be followed by a blank line
./src/crypto/x509/root_darwin_arm_gen.go:183: +build comment must appear before package clause and be followed by a blank line

Issue 2:
I ran into a likely false positive from go vet when writing a program that auto-generates code.

This program generates a warning +build comment must appear before package clause and be followed by a blank line

This equivalent program without the // autogenerated by... comment in the first line doesn't

In either case, i don't think go vet should be vetting contents of the string,
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behaviour

Should not throw an error

Current Behavior

Throws the following error:

Menu.js:107 Uncaught TypeError: Cannot read property 'focus' of null

at Menu._this.focus (Menu.js:107)

at Object.Menu._this.handleEnter [as onEnter] (Menu.js:122)

at Object.Popover._this.handleEnter (Popover.js:226)

at Object.chainedFunction [as onEnter] (helpers.js:85)

at Object.Grow._this.handleEnter [as onEnter] (Grow.js:86)

at Object.CSSTransition._this.onEnter (CSSTransition.js:217)

at Transition.performEnter (Transition.js:242)

at Transition.updateStatus (Transition.js:215)

at Transition.componentDidMount (Transition.js:157)

at commitLifeCycles (react-dom.development.js:8770)

Steps to Reproduce (for bugs)

Place a Select control within a Dialog and click on the control.

Tech
Version

Material-U I
v1.0.0-beta.24

React
v16.2.0

Cromium
Version 63.0.3239.84 (Official Build) Built on Ubuntu , running on Ubuntu 17.04 (64-bit)

Issue 2:
Description

When you click on item «Phone ringtone» in list - you see broken layout of confirmation dialog.

Steps to Reproduce

https://material-ui-1dab0.firebaseapp.com/demos/dialogs/#confirmation-dialogs

Environment

Tech
Version

Material-UI
v1.0.0-beta.21

Browsers
Google Chrome 61.0.3163.100 (Official Build) (64-bit), Mozilla Firefox 57.0 (64-bit)
Issue 1:
This,

/// A binary tree with nodes labelled with `T`
pub struct Tree<T> {
pub value: T,
pub left: Option<Box<Tree<T>>>,
pub right: Option<Box<Tree<T>>>,
}

impl<T> Tree<T> {
pub fn map_step<F, V>(self, f: &mut FnMut(T) -> V) -> Tree<V> {
Tree {
left: self.left.map(|x| { let a: Tree<V> = x.map_step(f);
Box::new(a) }),
right: self.right.map(|x| Box::new(x.map_step(f))),
value: f(self.value),
}
}
}

fn main() {}

fails with,

hi.rs:12:58: 12:69 error: unable to infer enough type information about `_`; type annotations required [E0282]
hi.rs:12 left: self.left.map(|x| { let a: Tree<V> = x.map_step(f);
^~~~~~~~~~~

All of my attempts at helping the compiler find the right types have failed, therefore I suspect it's a bug.

Issue 2:
This code producesses an unclear error

pub trait ValueGiver<T> {
fn give(_: Option<Self>) -> T;
}

struct m;

impl<f64> ValueGiver<f64> for m {
fn give(_:Option<m>) -> f64 {
0.5f64
}
}

fn main() {
let y : f64 = ValueGiver::give(None::<m>);
}

Here the error of course is the impl<f64> that should be impl, but the error message is not clear :

c.rs:64:5: 68:6 error: unable to infer enough type information about `_`; type annotations required
c.rs:64 impl<f64> ValueGiver<f64> for m {
c.rs:65 fn give(_:Option<m>) -> f64 {
c.rs:66 0.5f64
c.rs:67 }
c.rs:68 }

Could this error message be more helpful ?
Issue 1:
We have a lot of modules which a user might want to import, and it would be nice to show a list of these as a completion hint after import {} from '

Additionally, we have so many modules that walking the filesystem is not practical, and some of them are generated external module names, not files. So we would like to run a periodic indexing, and then somehow provide a list of these to the language services (eg. an RPC, or a file we stage on local disk, etc.)

cc @mprobst @rkirov

Issue 2:
Hi,

Visual Studio (2013 Ultimate) provides intellisense for the src attribute for script elements, by reading the file system and displaying available files or folders.

It will be quite useful if similar functionality can be provided for <reference> and import statements:

<reference path="foo/ <--- here

import foo = require('foo/ <--- and here
Issue 1:
Isn't the idea of 'inplace' that nothing needs to be returned? Additionally, when I have a lot of columns, the notebook's printout of the returned dataframe 'cramps my style'. ;)

Issue 2:
Is there any reason that whenever I'm doing inplace=True I always get self returned? Obviously not a huge deal, but this is kind of wart-y IMO. I wouldn't expect inplace to return anything.
Issue 1:
I'm updating the Matrix4 docs and there's a method called Matrix4.makePerspective( fov, aspect, near, far )

Internally this calculates the values of left, right, top and bottom and calls

Matrix4.makeFrustum( left, right, bottom, top, near, far )

and it looks like it is intended for use in PerspectiveCamera.updateProjectionMatrix()

However the PerspectiveCamera calculates its own versions of left, right, top and bottom in a slightly more complex way, taking into account zoom, view (if set) and filmOffset, and then calls Matrix4.makeFrustum directly.

So it seems that Matrix4.makePerspective() is superfluous - is there a use case that I am missing?

Issue 2:
Description of the problem

When using a NodeMaterial, setting needsUpdate to true because of a change made to the material will not yield the expected result as it's not recompiled. The change related to #17968 produces this result, and when reverting this blob in specific, the material updates as expected. This issue is present from r111 and up, possibly relating to the fact that the needsUpdate flag is never reset to false.

In relation, this proposed change by @sunag (coming from #18347) seems to work as well:

this.onBeforeCompile = function ( shader, renderer ) {
var materialProperties = renderer.properties.get( this );

if ( this.version !== materialProperties.__version ) {

this.build( { renderer: renderer } );

shader.uniforms = this.uniforms;
shader.vertexShader = this.vertexShader;
shader.fragmentShader = this.fragmentShader;

this.needsCompile = false;
}
};

Three.js version

Dev

r113

r112

r111

r110

Browser

All of them

OS

All of them

Paging @sunag.
Issue 1:
by peter.polakovic:

When working with large images I found, that windows port doesn't free large chunks of
memory.

The following code

package main

import "fmt"
import "runtime"

func main() {
for i:=0; i<10; i++ {
a := make([]byte, 5000000)
if a == nil { }
a = nil
runtime.GC()
fmt.Println(i, runtime.MemStats.Alloc, runtime.MemStats.Sys, runtime.MemStats.HeapObjects)
}
fmt.Println()
for i:=0; i<10; i++ {
a := make([]byte, 20000000)
if a == nil { }
a = nil
runtime.GC()
fmt.Println(i, runtime.MemStats.Alloc, runtime.MemStats.Sys, runtime.MemStats.HeapObjects)
}
}

produces the following output

0 5176576 8887420 422
1 5213848 14564476 433
2 5213848 14564476 433
3 5213848 14564476 433
4 5213848 14564476 433
5 5213848 14564476 433
6 5213848 14564476 433
7 5213848 14564476 433
8 5213848 14564476 433
9 5213848 14564476 433

0 20250336 37125244 436
1 40288024 59686012 442
2 60325656 82246780 444
3 80363288 104807548 446
4 100400920 127368316 448
5 100437784 149929084 449
6 120438552 149929084 450
7 120475416 172489852 451
8 140476184 172489852 452
9 140513048 195050620 453

On OS X port first part of output seems similar to second one (allocated memory and
number of heap objects is the same in each iteration).

The same result when using runtime.Malloc() and runtime.Free().

I'm using binary distribution of release.r57.1 on Windows7 (32 bit).

Issue 2:
by prencher:

This was originally reported in issue #4829. I posted a comment on it, but as it has
been marked fixed, I don't know if that is monitored. If it is, please by all means
close this issue as a duplicate and accept my apology.

When trying to get packages that depend on cgo, I get the error "argument unused
during compilation: '-fno-eliminate-unused-debug-types'":

$ go get bazil.org/fuse
# bazil.org/fuse
clang: error: argument unused during compilation: '-fno-eliminate-unused-debug-types'

$ go version
go version devel +f4d1cb8d9a91 Thu Sep 19 22:34:33 2013 +1000 darwin/amd64

$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.0 (clang-500.2.76) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin12.5.0
Thread model: posix

$ clang --version
Apple LLVM version 5.0 (clang-500.2.75) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin12.5.0
Thread model: posix
Issue 1:
Migrated issue, originally created by Konsta Vesterinen (@kvesteri)

I'm trying to do atomic SELECT or INSERT as explained here: http://stackoverflow.com/questions/6722344/select-or-insert-a-row-in-one-command/6722460#6722460

I'v been able to construct the query, however when I try to execute this query it gives me:

AttributeError: 'CompoundSelect' object has no attribute '_returning'

Here is a minimal test case for reproducing the issue:

import sqlalchemy as sa
from sqlalchemy import create_engine
from sqlalchemy.dialects import postgresql
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.sql.expression import CTE, exists

Model = declarative_base()

dns = 'postgres://postgres@localhost/my_test_db'

engine = create_engine(dns)
# engine.echo = True
connection = engine.connect()

class MyModel(Model):
__tablename__ = 'my_model'

id = sa.Column(sa.Integer, autoincrement=True, primary_key=True)
key = sa.Column(sa.Unicode(255), nullable=False)

sa.orm.configure_mappers()
Model.metadata.create_all(connection)

table = MyModel.__table__
value = 'some_key'

select = (
sa.select(['*'], from_obj=table)
.where(table.c.key == value)
)
insert = CTE(
table.insert()
.from_select(
[table.c.key],
sa.select([sa.text(value)])
.where(~ exists(select))
)
.returning(sa.text('*')),
name='new_row'
)
query = sa.select(['*'], from_obj=insert).union(select)
print connection.execute(query).fetchall()

Edit: Another problem is that the CTE isn't adding parenthesis around the insert statement whereas it should be (otherwise PostgreSQL doesn't understand the query).

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

apparently its all possible now. might as well make a new syntax bonanza out of it:

WITH upsert AS (
UPDATE metric k SET k.count = k.count + 5
WHERE event = "foo" AND interval = "D" and date = "whatever"
RETURNING k.*
)
INSERT INTO metric (event, interval, date, count)
SELECT ("foo", "D", "whatever", 5)
WHERE NOT EXISTS (
SELECT 1 FROM upsert
);

http://www.postgresql.org/docs/9.1/static/sql-insert.html

Attachments: ticket_2551.patch | CTE.sqlalchemy
Issue 1:
This is scrapy's default Dupefilter class method request_seen

class RFPDupeFilter(BaseDupeFilter):

def request_seen(self, request):
fp = self.request_fingerprint(request)
if fp in self.fingerprints:
return True
self.fingerprints.add(fp)
if self.file:
self.file.write(fp + os.linesep)

While implementing a custom dupefilter. i cannot retrieve the spider object from this class unlike other scrapy middleware

Is there any way i can know which spider object this is? so i can customize it via a spider on spider basis?

Also i cannot just implement a middleware which reads urls and puts it into a list & checks duplicates instead of a custom dupefilter. This is because i need to pause/resume crawls and need scrapy to store the request fingerprint by default using the JOBDIR setting

Issue 2:
Summary

Let us use DI framework in the pipelines and spiders. My personal favourite: https://python-dependency-injector.ets-labs.org/introduction/di_in_python.html

Motivation

We have a lot of common code we want to reuse in our scraping framework. Using DI to keep them tidy is nice to have.

Describe alternatives you've considered

Duplicate all the code and constructions. But only idiots likes duplicated codes or make global variables.
Issue 1:
From @dogfish182

unable to get local issuer certificate

Issue 2:
VSCode Version: 1.5

OS Version: 10.11.6

Steps to Reproduce:

Install a transparent man-in-the-middle firewall with a self signed cert and be sure that all traffic is being intercepted.

Install VSCode 1.4.

Notice that VSCode can't update extensions due to MITM.

Set http.proxyStrictSSL=false

Notice that VSCode can now update extensions or search extensions, etc.

Upgrade to 1.5

Notice that VSCode can no longer speak to the internet when trying to search for an extension
Issue 1:
if all historicals (and peon) respond within the query timeout specified and it is broker spending time doing the merge (usually in the case of merging lots of sketches) then timeout wouldn't be honored irrespective of however long broker takes to merge things.

on the client side, clients typically use the same timeout to close the connection... so broker doing all the work is eventually wasted.

one possibly simple (maybe crude) fix is that broker puts query processing startTime in query context and all things taking time to process the query continuously watch the time spent and fail if it exceeds. I'm imagining probably in QueryToolChest.mergeResults(..) impl and may be in the QueryResource where it is streaming the results to response.

another alternative to startTime would be to do query processing in a thread pool and cancel the future on query timeout .... druid code that takes time in processing the query would continuously check if the thread is interrupted.

Issue 2:
Currently If I specify a timeout query context when querying a broker, that timeout is not honored. It is entirely possible to set a timeout of 90s and have the broker hog resources for the query for 15m while it tries to complete the request.

The expected behavior is that the broker terminates the returning data stream once timeout has expired, and also that it cancels any outstanding query efforts on the historicals related to the query.

The current state of timeouts seems to be enforced on a per-segment basis, and not a per-query basis. Meaning that if historical nodes take an abnormally long time on queries, the overall query can take a very long time compared to the timeout.

This stems from 2 things:

Lack of checking in QueryResource for commands taking too long. (see #1416 )

Lack of ability to interrupt streaming results properly.

Part of this comes from the assumption stated in io.druid.query.AsyncQueryRunner::run

//Note: this is assumed that baseRunner does most of the work eagerly on call to the
//run() method and resulting sequence accumulate/yield is fast.

because the a lot of the query workload is actually lazily done in yield.
Issue 1:
Issue originally made by @ondras

Bug information

Babel version: 6.4.0

Node version: 0.10.25

npm version: 3.5.2

Input code

export function a() {
alert("a");
}

function b() {
a();
}

b();

Description

Exported and non-exported functions end up in different scopes, which makes exported functions uncallable from within non-exported functions.

Output code (using SystemJS module output):

System.register("...", [], function (_export, _context) {
function b() {
a();
}

return {
setters: [],
execute: function () {
function a() {
alert("a");
}

_export("a", a);

b();
}
};
});

Issue 2:
So, we have various files that are being compiled into a single library, many of which depend on core-js. The syntax import core from 'core-js' is invalid because core-js does not export default. However, compiling import * as core from 'core-js' in multiple files throws an error: Duplicate declaration "core".
Issue 1:
When you select an item from the affix menu (see the bootstrap website) The item you selected scrolls under the navbar and can not be seen.

Issue 2:
I have a navbar-fixed-top navbar. Links that include "scroll to id" (as in href="#myid") don't adjust scroll position to account for the 50px of the navbar.

Can you add some JS to detect this situation on the URL and adjust the scroll position back by the height of the navbar?
Issue 1:
Challenge change-the-color-of-text has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0.

I've been trying to solve this, but I think everything is alright. I have no idea how to fix it.

`

CatPhotoApp

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

`

Issue 2:
Challenge change-the-color-of-text has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0.

Please describe how to reproduce this issue, and include links to screenshots if possible.

<h2>CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

<h2>CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

<h2 style="colr:red;">CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

<h2 style="colr:red;">CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

This had previously passed. Resubmitted now its failing. Cleared my code and tried to reenter now it doesnt accept the code at all. It resents and clears my text inputed when I click run code.
Issue 1:
I'm unable to make a simple IPC communication between node and spawned electron process working on linux ubuntu. It works fine on Windows.

node.js code

var electron = require('electron-prebuilt')
var spawn = require('child_process').spawn

var child = spawn(electron, ['electron-script.js'], {
stdio: ['ipc']
})

child.on('message', function (m) {
console.log('Yes it works!')
})

electron script

process.send('I am ok')
process.exit(0);

On windows I get back Yes it works! to console. There seems to be no communication happening and nothing is printed on ubuntu. Thank you for the help.

Electron version: ~ 1.3.1

Operating system: Ubuntu

Issue 2:
Electron version:

1.8.4

Operating system:

Arch Linux

Freetype version:

2.9.0

Expected behavior

Electron should render fonts using subpixel rendering

Actual behavior

Fonts are rendered in greyscale mode.

How to reproduce

I guess the issue is related to freetype. It started after the new freetype release. It happens to every electron-based application (vscode, atom, ... ).
Issue 1:
VSCode Version: v1.1

OS Version: windows 10

nodejs Version: v6

Steps to Reproduce:

( a little bit complicate)

mkdir try-bugs && cd try-bugs

2.npm install -g vue-cli

2.vue init webpack

3.npm install

4.set up a task in task.json, whose command is npm, args is ["run", "build"]

press contrl + shift + b to build the project

6.then babel of webpack does not work in the right way

Further description and guess:

I have install a extension of vscode called new-cmd , which can enable you to open a new terminal from current work space directory by typing command cmd after pressing f1 in vscode.

If I open a terminal using this extension and then run npm run build in this terminal, it will show me the same bug as run the build task from vscode.

However, if I open a terminal manually by right click and run the same command, everything goes well.

I notice that there is one difference between the two terminal is that the disk name. The disk name in former terminal is d:\ while the later one is D:\.

In the project, from one hand, there are some code, the config of webpack specifically, related to path.join(__dirname, ...), which will generate an absolute path to files begin with D:\. From the other hand, there are some other code use relative path to locate file, which will result in path to file begin with d:\.

I wonder whether this caused my problem or not.

By the way, if I repeat the process with node5, the bug disappear.

Issue 2:
OS Version: Windows

generate a source map where the 'sourceRoot' uses an absolute path starting with a drive letter.

set a breakpoint in the source and try to hit it

edit the source map and change the case of the drive letter

restart the debug session and try to hit it again

Observe: the breakpoint will be only hit once

The problem is a path comparison in node-debug that doesn't ignore the case of the drive letter.