WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Currently lifetimes has little docs on manual, I found 14 matches for "lifetime" on http://static.rust-lang.org/master/doc/rust.html

The borrowed pointers tutorial mentions named lifetimes but doesn't mention the apostrophe symbol, newcomers might get confused about that.

Same goes for manual, there's no mention to apostrophe, just some examples using 'static. It also lacks grammar production.

Issue 2:
[NOTE: I misread ' as a backtick ]

I've come across types with backticks aka `.

Examples (from memory, could be wrong):

&`a
`static

From reading a presentation on memory I guess one use is to denote lifetype scope (???).

Since the compiler gives type errors that use backtick, it would be great to have a section on them.
Issue 1:
git status takes around 2 seconds to run on my large repository, the blue clock icon on git integration to indicate "working" can be quite visually distracting as it seems to ping the repo every 5-10 seconds.

I'm not so sure there is a benefit in indicating work unless the user explicitly requested it, such as when clicking the button.

Issue 2:
Several times now I've had mysteriously deleted files when doing a git pull in a console while Visual Studio Code is running. I've seen this roughly since version 0.10.

It seems that when auto-merging, Git is able to delete a file but not able to write the merged file back if it's open in Code. However that is just a hypothesis.

Seen the issue last with git version 1.9.5.msysgit.1 and Code 0.10.2.
Issue 1:
As far as I could tell, there is no place for the community to discuss tensorflow in realtime; the recommendations all seem to be about asking specific questions in a detailed async fashion.

It would be nice if there was a gitter.im or IRC channel for tensorflow so that the community could interact more easily. not even as a dedicated support channel.

There is already a gitter.im for skflow, but since fewer people know about skflow, let alone the gitter.im for it, it's pretty small: https://gitter.im/tensorflow/skflow

It would be even nicer if the channel was linked from the repo, but gitter.im is nice since it has some automatic discoverability if you're already familiar with gitter

Issue 2:
If we're in for the openess and effectiveness of the whole thing...

(1) Why not using gitter.im ?

I also believe we should have a discourse forums, which I'm more than willing to help / set up if you really need (just can't pay for it or move people from the mailing list without being official).

(2) Yes, discourse would be a perfect replacement for the mailing list and to this Issue tracker. :)
Issue 1:
When I use the scene with both InstancedMesh and normal Mesh, and set the scene.overrideMaterial =Depthmaterial; then object.instanceMatrix Is the undefined value, because normal Mesh does not have this property. In the setupVertexAttributes method of WebGLBindingStates, const attribute= attributes.get(object.instanceMatrix) On line 386, an exception is thrown. It is suggested to modify the get method of WebGLAttributes and add judgment:

function get(attribute) {
if (attribute === undefined) {
return undefined;
}
if ( attribute.isInterleavedBufferAttribute ) { attribute = attribute.data ;}
return buffers.get ( attribute );
}

Issue 2:
Description of the problem

I'm having a problem where the InstancedMesh method setMatrixAt seems to fail (the matrix positions doesn't change visually) whenever I add another object with the same material object (not a clone) in the scene. No log/warning/errors are emitted.

The following briefly illustrates:

var geometry = new THREE.BoxBufferGeometry();
var material = new THREE.MeshStandardMaterial( { roughness: 0, envMap: texture });
var mesh1 = new THREE.Mesh( geometry, material );
mesh1.position.set(0, 1, 0);
scene.add( mesh1 ); // removing this line makes the instanced mesh work as intended
mesh = new THREE.InstancedMesh( geometry, material, 9 ); // same material usage
scene.add( mesh ); // This works and I can see both meshes in the scene.

var dummy = new THREE.Object3D();
dummy.position.set( 1, 5, 1 );
dummy.updateMatrix();
mesh.setMatrixAt( 0, dummy.matrix ); // Nope, doesn't work, it just stays where it's at.
mesh.setMatrixAt( 1, dummy.matrix ); // Rotation seems to be applied, but position doesn't.
// It looks like every instance is at the same place, but I don't know.

Note that if I use material.clone() at the instanced mesh declaration, the problem also goes away / is fixed, but now I have two materials, and I intend to have one for performance reasons.

A live example is available here:

jsfiddle (The problem is that you should see multiple boxes, but only 1 or 2 are visible, remove line 41 to fix)

Three.js version

Dev

r109

r108

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)

(Not applicable, as far as I know)
Issue 1:
Consider a series of quoted strings in an array in ruby:

states = ['AL', 'AK', 'AZ', 'AR', 'CO', 'DE', 'FL', 'GA', 'HI', 'ID', 'IL', 'IN', 'IA', 'KS', 'KY', 'LA', 'ME', 'MD', 'MI', 'MN', 'MS', 'MO', 'MT', 'NE', 'NV', 'NH', 'NJ', 'NM', 'NY', 'NC', 'ND', 'OH', 'OK', 'OR', 'RI', 'SC', 'SD', 'TX', 'UT', 'VT', 'VA', 'WA', 'WV', 'WI', 'WY']

In atom, if this list stopped at MI syntax highlighting would resume as normal. However, it acts as if the rest of the file has a single quote at the top:

I'm using the Tomorrow theme but it shows up in others as well. This also happens in python, but the quote limit is one less and only the rest of the line is unquoted. Same with C, although again the quote limit changes. Very odd.

Issue 2:
I opened a Python file with the following line (#963):

PrintAndLog(u"SSID: " + RememberedNetwork["SSIDString"].decode("utf-8") + u" - BSSID: " + RememberedNetwork["CachedScanRecord"]["BSSID"] + u" - RSSI: " + str(RememberedNetwork["CachedScanRecord"]["RSSI"]) + u" - Last connected: " + str(RememberedNetwork["LastConnected"]) + u" - Security type: " + RememberedNetwork["SecurityType"] + u" - Geolocation: " + Geolocation, "INFO")

Which led to the following bug:

You can find this as the main file in osxauditor.py.
Issue 1:
Checklist

I have checked the issues list

for similar or identical feature requests.

I have checked the pull requests list

for existing proposed implementations of this feature.

I have checked the commit log

to find out if the if the same feature was already implemented in the

master branch.

I have included all related issues and possible duplicate issues

in this issue (If there are none, check this box anyway).

Related Issues and Possible Duplicates

Related Issues

None

Possible Duplicates

None

Brief Summary

I need to have a possibility to override backend implementation in my project.

Overriding backend implementation with Loader.override_backend was introduced years ago. But there is no way to set Loader.override_backends member -- nor with celeryconfig nor with command line arguments or env variables -- it is always empty dict.

So my request is to add a possibility to set Loader.override_backends with celeryconfig.

I have checked that setting override_backend field works and allows to override backend.

Design

Architectural Considerations

None

Proposed Behavior

Adding next dict to celeryconfig.py

override_backends = {
'db': 'my_module.DatabaseBackend',
}

should change Loader.override_backends from empty dict to

{
'db': 'my_module.DatabaseBackend',
}

which is used in celery.app.backends.by_name

to replace default backend implementation with custom one.

Proposed UI/UX

Diagrams

N/A

Alternatives

None

Issue 2:
Checklist

I have checked the issues list

for similar or identical bug reports.

I have checked the pull requests list

for existing proposed fixes.

I have checked the commit log

to find out if the bug was already fixed in the master branch.

I have included all related issues and possible duplicate issues in this issue

(If there are none, check this box anyway).

Related Issues and Possible Duplicates

Related Issues

None

Possible Duplicates

None

Description

docs/getting-started/next-steps.rst includes the text:

The backend argument specifies the result backend to use, It's used to keep track of task state and results. While results are disabled by default I use the RPC result backend here because I demonstrate how retrieving results work later, you may want to use a different backend for your application

However, the code that is included is examples/next-steps/proj/celery.py which uses the amqp backend.

Screenshot of the issue:

Suggestions

Simply change the next-steps.rst doc file to say "I use the AMQP/Rabbitmq result backend here because..."
Issue 1:
Bug report

What is the current behavior?

When loading 2 entry points on the same page that share a common module, the module is instantiated twice, even when it's bundled into the commons bundle.

We ran into this while upgrading Next.js to webpack 4 and it's currently blocking the upgrade until we know if this is expected behavior.

If the current behavior is a bug, please provide the steps to reproduce.

I've created a reproduction for both webpack 3 and webpack 4, also added an explanation about how Next.js handles things and research into the issue:

https://github.com/timneutkens/webpack-instantiation-issue

What is the expected behavior?

Following webpack 3 there should be only one instance of a shared module. Which is not the case in webpack 4 when having multiple entries on the same page. Though this might be expected.

My main question being: is this expected? Should we bind the "singleton" instance to window so that it will be the same across multiple module instances, or is this a regression/bug?

Other relevant information:

webpack version: 4.12.0

Node.js version: any

Operating System: any

Additional tools:

Issue 2:
I'm working on this larg(ish) project where we currently use AMD. It works all right, we don't build the project in development and load each module individually. It takes about ~2.5 seconds to load the page with ~420 modules/templates.

I'm exploring switching to webpack (which so far looks amazing) for all the benefits that would add. I have our entire existing project building with webpack with no modifications to the project, which is awesome.

It takes 14s to build the project, but if I use webpack-dev-server, the rebuilds are impressively fast ~1s.

However, if I turn on devtool: "source-map", the rebuilds then take ~4s which is slower than loading all modules individually with Require.js where source maps are not needed.

I've tried using devtool: "eval" and that's fast, but it's not .. a perfect sourcemap (e.g. requires are all numbers now and pathInfo: true doesn't seem to work for me).

So, my question really is, why does sourcemap slowdown rebuilds so much and how could I try to go around it. E.g. Should I try to make more smaller chunks? Should I try to move some of the shared dependencies from the chunks into the entry bundle? Am I doing something wrong with having so many megabytes of JavaScript?

Here's my current output just to give you the idea of the size of the project.

Version: webpack 1.0.0-rc3
Time: 14180ms
Asset Size Chunks Chunk Names
bundle.js 985492 0 [emitted] main
1.bundle.js 437111 1 [emitted]
2.bundle.js 552099 2 [emitted]
3.bundle.js 1848882 3 [emitted]
4.bundle.js 2413145 4 [emitted]

That's 5.9MB in total at the moment, even though the unuglified r.js build is 3.8MB. That's because there's a lot of code duplication in chunks 1, 2, 3, 4. I'd like to build all modules that are shared at least once into the parent bundle, but haven't figured how to do that yet.
Issue 1:
Electron Version(s)

1.3.1, 1.8.4, 8.4.0, 9.1.0 & 10.0.0-beta.12

Operating System:

MacOS

Last Known Working Electron version:

NA

Expected Behavior

I have an app which has 3 levels, level1 incudes a webview with page source level2.html; inside level2 an `<iframe>` element is embedded with source set to level3.html. Each page has button & input field.

The expected behavior would be while tabbing the screen readers should be able to focus & read through all three buttons & input fields.

Actual Behavior

Screen readers are reaching till the buttons & input fields of level 2 & ignoring level3. But if I relace <webview> with <iframe> everything seems to work fine.

Please check out the video for more details on the issue

Check the below image showing the accessibility tree not being generated properly incase of webview:

To Reproduce

Clone this repository

$ git clone https://github.com/microsoft/electron-webview-accessibility-issue

$ cd electron-quick-start

$ npm install

$ npm start || electron .

Turn on the screen reader

Tab across button & input fields

You will notice that the screen reader focus is not moving to level3 hence is not able to read the corresponding elements

Additional Information

This issue has been reported earlier & is a possible duplicate of #12478 but it contains more information on reproducing the bug for electron version 8.4.0

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

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

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

Electron Version

15.0.0

What operating system are you using?

Windows

Operating System Version

Windows 10

What arch are you using?

x64

Last Known Working Electron version

9.3.0

Expected Behavior

Custom titlebar with Draggable region would working with the resizable:false browser window.

Browser window property: resizable: false

CSS Property: -webkit-app-region: drag

Actual Behavior

It is not working with fixed-size browser window.

It is working with only resizable browser window.

Testcase Gist URL

No response

Additional Information

No response
Issue 1:
Since opera is webkit internally, we should remove the opera (-o-) css vendor prefix and prevent websites from bloated css, IMO.

Agreed? Other knowhow?

Issue 2:
When changing color values in variables.less to suit your app design, having the variables named after the hex color value they represent seems illogical. Would this not be better used to describe the color's purpose?

e.g.

@blue: #049CDB;

@green: #46a546;

@red: #9d261d;

changes to:

@primarycolor: #049CDB;

@successColor: #46a546;

@warningColor: #9d261d;
Issue 1:
The collapse js plugin should be made more flexible by not requiring a wrapping .panel for data-parent to work. The "show only one at a time" functionality is useful outside of accordions and without panel-like styling.

Fixing this is as easy as changing the selector in https://github.com/twbs/bootstrap/blob/v3.0.2/js/collapse.js#L51 to something purely semantic that doesn't come with styles -- try > .collapse-group > .in for example.

Also note that the docs do not explicitly mention what the DOM should be for data-parent to work.

See also discussion in #10023.

Issue 2:
Hi, i found this pull request: #7600

In the latest version i see that the parent option is now dependent on the .panel class, i.e.:

var actives = this.$parent && this.$parent.find('> .panel > .in')

Why don't you just leave it like it was (.collapse.in) or better yet, just:

var actives = this.$parent && this.$parent.find('.in')

Or, i get it if the parent must have a class, to avoid conflicts with other libraries, but can you please explain what's up with depending on dom structure? (the double > in the selector really don't look good to me)

Oh and, the docs are way behind on this one. There's an .accordion-group class mentioned, but not saying how it should be used, and the example doesn't have one at all (yet it works, probably on an old bootstrap version).

So basically, please decide on a structure and update the docs & examples accordingly. If you want i could help you with some of the workload, as you see fit.

Thank you.
Issue 1:
Original ticket http://projects.scipy.org/scipy/ticket/1292 on 2010-10-03 by trac user heroxbd, assigned to unknown.

In minpack.py, print "Warning: " msg is used to print Warning messages into stdout. This is not a good idea if one want to control its warning behavior using python's warnings module.

Please consider improving this.

Issue 2:
The issue

imread is in scipy.ndimage and scipy.misc.imread

imshow and imsave are in scipy.misc

This seems inconsistent / unlogical from a users perspective.

Proposed solution

Moving some to scipy.ndimage and others to scipy.io:

scipy.misc.imshow → scipy.ndimage.imshow

scipy.ndimage.imread, scipy.misc.imread → scipy.io.imread

scipy.misc.imsave → scipy.io.imwrite

scipy.misc.imfilter → scipy.ndimage.imfilter

scipy.misc.imresize → scipy.ndimage.imresize

scipy.misc.imrotate → scipy.ndimage.imrotate

scipy.misc.ascent → scipy.ndimage.ascent

scipy.misc.face → scipy.ndimage.face

I'm not sure about the remaining bytescale, fromimage, toimage.

What needs to be done

Moving the code from pilutil.py to io.py (and importing the functions from io.py in pilutil.py)

Adding deprecation warnings to pilutil.py

Adjusting tests

Adjusting documentation
Issue 1:
Bug report

There is no version information on the documentation pages.

Details

If you google code samples of matplotlib, you will get links to different versions of the matplotlib documentation. On these documentation pages, there is no hint, which version of matplotlib you are looking at. Even the URL of the documentation doesn't give a clue! If you try some code (official samples from the official documentation!), you may wonder why it is not working in your installation of matplotlib.

Why this matters

Especially for beginners, this is very frustrating! You may try to figure out whats wrong for hours and post questions on stackoverlow, just to find out, that the matplotlib documentation doesn't care to show a clue which version you are looking at (as happened to me examples/showcase/xkcd.py)!

Issue 2:
On the current live docs, the examples page claims to be from release 2.0.2, but it should be 2.1: http://matplotlib.org/examples/index.html
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-target-elements-by-id-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

When lessons in this section are loaded the <script> and </script> tags are changing to other characters. Might just be a browser issue(?) Safari 8.0.8 - OS X 10.10.5

Issue 2:
http://www.freecodecamp.com/challenges/waypoint-bring-your-javascript-slot-machine-to-life

e.g.

$($('.slot')[0]).html(slotOne);

Doesn't work
Issue 1:
I am trying to rebuild application with latest Angular 2.0.0 version and everything works fine except that there are some intellisense errors in observables. Is this an issue with rxjs module where the error is throwing. How can i get rid of these error:

For some reason i cannot paste image here so getting somethign went wrong while uploading so providing link to stackoverflow:

http://stackoverflow.com/questions/39874609/intellisense-errors-while-rebuilding-application-in-angular-2-0-0-version

Issue 2:
When using the ContentChild annotation with a type query it works very well but when I try to use string query - for some reason the annotated field is always null.

the following is a SSCCE that reproduce the problem:

import {Component, ContentChild} from 'angular2/core';
import {bootstrap} from 'angular2/platform/browser';

@Component({
template: `
<ng-content select="inner"></ng-content>
`,
selector: 'ctr'
})
class TestContainerComponent {
@ContentChild('inner') inner;

ngAfterContentInit() {
console.log('inner: ', this.inner);
}
}

@Component({
template: `
<ctr> <inner> SOME TEXT </inner> </ctr>
`,
selector: 'app',
directives: [TestContainerComponent]
})
class TestAppComponent { }

function main() {
return bootstrap(TestAppComponent).catch(err => console.error(err));
}

document.addEventListener('DOMContentLoaded', main);

When running the above code the result is:

console: inner: null

view: SOME TEXT

although the API docs show a usage example with a type query, the type definition indicates that the query can be either a Type or a string (Type | string)
Issue 1:
I am using Python 3.4.4 |Anaconda 2.3.0 (64-bit) on win64 bits, with latest matplotlib and pyqt updated by conda install xx

for the following code, if I use unicode title in the for-loop, the images are shown with their corretced direction, i.e., the head is toward up like which is in original image. However, if I use English title, the images are upside-down: the people's head is toward earth

This can be observed for both TkAgg and Qt5Agg

#coding=utf-8
import matplotlib
#~ matplotlib.rcParams['backend'] = 'TkAgg'
matplotlib.rcParams['backend'] = 'Qt5Agg'

from pylab import *
import PIL.Image as Image

im=Image.open('Mario cosplay.jpg').convert('L')

orgsize=im.size
newsize=[int(i/4) for i in orgsize]

subplot(2,3,1)
imshow(im, cmap='gray', vmin=0, vmax=255)
title('original pic', fontsize=20);

filters=[Image.NEAREST, Image.BILINEAR, Image.BICUBIC, Image.ANTIALIAS]
filtersName=['NEAREST', 'BILINEAR', 'BICUBIC', 'ANTIALIAS']
for k in range(len(filters)):
subplot(2,3,k+2)
im1=im.resize(newsize, filters[k])
imshow(im1, cmap='gray', vmin=0, vmax=255)
title('原图的1/%i，插值法：%s' % (4, filtersName[k]), fontsize=20) # head up
title('size: 1/%i，interpolation: %s' % (4, filtersName[k]), fontsize=20) # head down

gcf().tight_layout()

show()

Issue 2:
When plotting a lot of subplots (here 6), with long y-labels and tight_layout, the y-axis is reverted.

In this example, it is particularly striking as I am plotting histograms.

import matplotlib.pyplot as plt
import numpy as np

alphas = [0.001, 0.1, 1, 10, 1000, 10000]
X = np.random.randn(len(alphas), 1000)

fig, axes = plt.subplots(nrows=len(alphas), ncols=2)
fig.set_tight_layout(True)
for i, alpha in enumerate(alphas):
ax = axes[i, 0]
ax.hist(X[i])
ax.set_xlabel("Number of features", fontweight="bold")
ax.set_ylabel("Number of genes", fontweight="bold")

ax = axes[i, 1]
ax.plot(sorted(X[i]))
ax.set_ylabel("Number of genes", fontweight="bold")

Expected outcome

Removing the tight layout, the labels collapse, but at least the plots are oriented the correct way.

Matplotlib should either raise a proper error raise a proper warning, or plot the histograms in the proper order.

Matplotlib version

Matplotlib 2.0.0