WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
This issue is for discussing how to make the new GC (#8699) thread-safe. A GC expert should check the arguments here. For background, see the elegant state transition diagram in src/gc.c.

I'm assuming that garbage collection operates in stop-the-world mode, and for now, that the mark/sweep phase is single-threaded. Each thread can have its own thread-local remset, with occasional duplication across the sets because of the race described below.

Key question: what state transitions can race against each other? If I understand the GC correctly, the only racy transitions arise from a write barrier for the same parent, and that transition is GC_MARKED --> GC_QUEUED, which changes the low two bits of the memory location from 01 to 10. If this is indeed the only racy transition, then a plain load, modify, plain store sequence will suffice, since all racing participants will be attempting to write the same value to the location. To be portable C11, we should use relaxed atomic loads/stores instead of the current assignments into bitfields, but that's a purist nitpick.

The possibility of a race will require lightening up on assertions that check for duplicate enqueuing of roots. There will need to be a memory_order_acq_rel fence between normal operation and garbage collection, but that's probably already implied by synchronization between normal operation and garbage collection.

Possible problem: gc_wb_buf appears to engaging in other transitions. If so, which of these might race against each other? Are these transitions always on different gc_bits than the ones affected by gc_wb?

Issue 2:
$ julia -e 'reinterpret(Nothing, nothing)'

$ julia --code-coverage=user -e 'reinterpret(Nothing, nothing)'
ERROR: bitcast: target type not a leaf primitive type
Stacktrace:
[1] reinterpret(::Type{Nothing}, ::Nothing) at ./essentials.jl:413
[2] top-level scope at none:1

Started behaving differently with 1.1, on 1.0 both fail. Arguably this use of reinterpret should be allowed, but the change in behavior based on code coverage had me stumped for a while.
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/1738 on 2011-02-09 by @nbecker, assigned to unknown.

find_first would be a performance enhancement. The current alternative would be something like:

argmax (some boolean function...)

which requires a lot of extra work if all you want is the index of the first occurance.

This is frequently wanted for 1-d arrays, where it's meaning is unambiguous. I think semantics for n-d (n > 1) arrays is up for discussion.

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/1673 on 2010-11-13 by trac user tom3118, assigned to unknown.

The "numpy for matlab users" suggests using

nonzero(A)[0][0]

to find the index of the first nonzero element of array A.

The problem with this is that A might be a million elements long and the first element might be zero.

This is an extremely common operation. An efficient, built-in method for this would be very useful. It also would easy people's transition from Matlab in which find is so common.
Issue 1:
Bug report

If one makes a scatter plot (or a line graph) having multiple points with different markers and colors, but the same label, this will result in an error in version 2.1.1 (but not 2.1.0). A small example is provided below:

Code for reproduction

#!/usr/bin/env python
import matplotlib as mpl
mpl.use('Agg')
import matplotlib.pyplot as plt

color='#00ff00ff'
plt.scatter(0.0, 1.0, color=color, marker='o', label='test')
color='#00ffaaff'
plt.scatter(0.5, 0.0, color=color, marker='v', label='test')
plt.legend()
plt.savefig('foo.png')

Actual outcome

This example uses a scatter plot, but the same issue can arise with line plots if one uses a numpy vector as a color (e.g., [0.0, 1.0, 0.0, 1.0]). The error produced for the above example is as follows:

Traceback (most recent call last):
File "foo.py", line 11, in <module>
plt.legend()
File "/home/ryan/.local/lib/python2.7/site-packages/matplotlib/pyplot.py", line 3748, in legend
ret = gca().legend(*args, **kwargs)
File "/home/ryan/.local/lib/python2.7/site-packages/matplotlib/axes/_axes.py", line 498, in legend
**kwargs)
File "/home/ryan/.local/lib/python2.7/site-packages/matplotlib/legend.py", line 1402, in _parse_legend_args
handles, labels = _get_legend_handles_labels(axs, handlers)
File "/home/ryan/.local/lib/python2.7/site-packages/matplotlib/legend.py", line 1360, in _get_legend_handles_labels
and not _in_handles(handle, label)):
File "/home/ryan/.local/lib/python2.7/site-packages/matplotlib/legend.py", line 1344, in _in_handles
if f_h.get_facecolor() != h.get_facecolor():
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

At the end of the day, this ends up being because the face (and edge) colors are converted to a numpy vector, which can't be compared with != since they have multiple elements. With the help of git bisect, I've tracked this down to this commit at the end of October.

Now I'll grant that this only happens if people use the same label for multiple symbols/lines, which is a bad idea...but one can't always prevent end users from doing that.

Issue 2:
Summary

120 seconds is an extremely long timeout when running locally and having failures. It would be good to only set the 120 seconds on CI/remote systems and have a shorter 10-20 second timeout for most contributors with reasonable CPU architectures.

matplotlib/lib/matplotlib/tests/test_backends_interactive.py

Line 79
in
515cce4

_test_timeout = 120 # A reasonably safe value for slower architectures.

Labeling good first issue because it is very contained and should likely just need some investigation into environment variables and detecting platforms we are running on.

Proposed fix

Set the _test_timeout variable differently depending on whether we are running on CI or not.
Issue 1:
It would help people to keep the font sizes on there site more consistent is classes were also offered as the same sizes as the the headings.

E.g. bits of text that semantically are not headings, but for styling purposes should appear the same size, or are different levels in the document structure.

The change would just be to add classes next to the headings in /less/type.less

h1, .h1 { font-size: (@font-size-base * 2.75); font-size: 4rem; } // ~38px
h2, .h2 { font-size: (@font-size-base * 2.25); font-size: 3rem; } // ~32px
h3, .h3 { font-size: (@font-size-base * 1.75); font-size: 2.5rem; } // ~24px
h4, .h4 { font-size: (@font-size-base * 1.25); font-size: 2rem; } // ~18px
h5, .h5 { font-size: @font-size-base; font-size: 1.6rem; }
h6, .h6 { font-size: (@font-size-base * 0.85); font-size: 1.2rem; } // ~12px

I can open the pull request, but mainly wondered about what naming style would be best.

So i also found this issue from 6 months ago but its now closed, #5203

But i don't think it was clear the first time with this issue that it could help the consistency between font sizes on the site, and that it would not only be useful for heading tags, but for any text on a page.

Issue 2:
Upon trying to add the examples' CSS to the csslint Grunt task, I discovered that some of them fail csslint:

Running "csslint:src" (csslint) task
Linting docs/examples/blog/blog.css ...ERROR
[L44:C1]
Rule is empty. Rules without any properties specified should be removed. (empty-rules)
[L73:C3]
vertical-align can't be used with display: block. Certain properties shouldn't be used with certain display property values. (display-property-grouping)
Linting docs/examples/grid/grid.css ...ERROR
[L21:C3]
Duplicate property 'background-color' found. Duplicate properties must appear one after the other. (duplicate-properties)
[L22:C3]
Duplicate property 'border' found. Duplicate properties must appear one after the other. (duplicate-properties)
Linting docs/examples/justified-nav/justified-nav.css ...ERROR
[L44:C3]
Duplicate property 'background-image' found. Duplicate properties must appear one after the other. (duplicate-properties)
Linting docs/examples/non-responsive/non-responsive.css ...ERROR
[L41:C3]
Duplicate property 'background-color' found. Duplicate properties must appear one after the other. (duplicate-properties)
[L42:C3]
Duplicate property 'border' found. Duplicate properties must appear one after the other. (duplicate-properties)
Issue 1:
Environment

Windows build number: [Versione 10.0.18362.356]
PowerToys version: 0.11.0
PowerToy module: FancyZones

Steps to reproduce

The Windows bottom bar appear at fullscreen in one of the zone I set (screenshot attached) .

It happens as long as I use on ore more Virtual Desktop WIN + CTRL + D

Open PowerToys

FancyZones

Edit layout

Change/Create new virtual desktop with WIN + TAB or just WIN + CTRL + L/R ARROW

(the actual Issue) The Win Bar appears full-height (as in image)

To exit from that view I have to click it or click in search then ESC

Sometimes the layout I created is not usable anymore, sometimes is (I dind't figure out why, but I will update this issue asap)

Expected behavior

To be able to set (potentially) a different layout for every Virtual Desktop

Windows bar shouldn't appear as long as I switch from a desktop to another

Actual behavior

The Windows bar take all vertical space in the zone I choosed

Screenshots

Issue 2:
Environment

Windows build number: Windows 10 1903 (18362.356) - 64bit
PowerToys version: 0.11.0
PowerToy module: Shortcut Guide, FancyZones

Steps to reproduce

Open the shortcut guide click onto the taskbar and then trigger the window controls to move a window to a specific zone (Windows + Arrow Keys), the taskbar gets moved into that zone even when locked. Weird behaviour appears when switching virtual desktops (see GIF below).

Screenshots

GIF

Imgur
Issue 1:
Challenge Use the Twitchtv JSON API has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36.

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

The current link for step 8 is : https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Zipline-Use-the-Twitchtv-JSON-API

I believe it should be : https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Front-End-Project-Use-the-Twitchtv-JSON-API

Issue 2:
Related to challenge /use-the-twitchtv-json-api.

I think it should be https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Front-End-Project-Use-the-Twitchtv-JSON-API.
Issue 1:
Feature

What is the current behavior?

With a UI kit that uses forwardRefs, I get error messages like this:

What is the expected behavior?

It would look a lot better if forwardRefs were a bit less obtrusive, and if they picked up the functions displayName rather than just the name of the function they wrap.

In our UI Kit we have a pattern like:

const View = forwardRef(function UIView(){ return <div /> })
View.displayName = 'SomeDisplayName'

For some reason it's not showing that, just showing the inner one. Further the "bigness" of ForwardRef() makes it hard to see visually when scanning. Perhaps something more like this would help:

Warning: Encountered two children with the same key, `confluence`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.
in div (created by ForwardRef(Gloss))
in Gloss (ForwardRef)
in Gloss (ForwardRef) (created by OnboardMain)
in div (created by Gloss (ForwardRef))
in Gloss (ForwardRef)
in Gloss (ForwardRef) (created by SliderPane)

Further, the created by information is often more useful to me, but it's never aligned nicely. Could do something like:

Warning: Encountered two children with the same key, `confluence`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.
in div (created by ForwardRef(Gloss))
in Gloss (ForwardRef)
from OnboardMain:
in Gloss (ForwardRef)
from Gloss (ForwardRef):
in div
in Gloss (ForwardRef)
from SliderPane:
in Gloss (ForwardRef)

All together, if it would pick up displayNames, the stack would be far more readable for me:

Warning: Encountered two children with the same key, `confluence`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.
in div (created by Row)
in View (forwardRef)
from OnboardMain:
in Row (forwardRef)
from Col (forwardRef):
in div
in Grid (forwardRef)
from SliderPane:
in View (forwardRef)

Issue 2:
People lose hours of work debugging a simple issue: two versions of React being loaded at the same time.

gaearon/react-hot-loader#32 (comment)

KyleAMathews/coffee-react-quickstart#10 (comment)

gaearon/react-document-title#1 (comment)

clayallsopp/react.backbone#26

Because there is no warning right away when this happens, they usually discover the problem through invariant violations. Some of them are descriptive (e.g. Uncaught Error: Invariant Violation: The handler for Route "hello" must be a valid React component) and I think I even saw warning that said something like "check if two copies of React are loaded", but some are really cryptic: Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs....

Is there a reason why we don't want to warn right away when two copies of React are loaded?
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-use-css-selectors-to-style-elements has an issue.

When completing this challenge, before I had placed the closing curly bracket, the challenge updated to finished.

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-use-css-selectors-to-style-elements has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

It gives you the green light to go to the next challenge after writing just this:

<style>h2{color: blue</style>

Notice the missing ; and the missing }.
Issue 1:
In responding to a stackoverflow question, I noticed that

sns.clustermap(data=corr, col_cluster=False, annot=True, fmt='d', cmap='Greens')

produced annotation only in the lower left corner. This looks like a bug?

Issue 2:
I know this feature has been suggested before as part of #479. My use case is however a bit different.

I suggest to put a normalization factor in the kdeplot function. When looking at a subset of data, I would like to scale the KDE to normalize to the fraction of included data. Now you get something like the figure below, where blue is the total data set and green/orange are two subsets of my data. If we could include a normalization parameter, we can match the KDE's of the subsets to the KDE of the total set.
Issue 1:
with xcode-select pointed to Xcode 8:

$ xcode-select -p
/Applications/Xcode.app/Contents/Developer

I get the following compile error with build_all_ios.sh on Sierra:

checking whether we are cross compiling... configure: error: in `/Users/serkan/tensorflow/tensorflow/contrib/makefile/downloads/protobuf':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details

Not sure if this is related to Xcode 8 or to code signing on Sierra

Issue 2:
When running compile_ios_protobuf.sh, it says:

checking whether we are cross compiling... configure: error: in '.../tensorflow/tensorflow/contrib/makefile/downloads/protobuf':

configure: error: cannot run C compiled programs.

If you meant to cross compile, use --host'. Seeconfig.log' for more details
Issue 1:
flutter.yaml's assets support is a convenient way to add assets for both platforms. Unclear if we want to keep it long term, but if we do it would be nice to add support for directories and/or file globbing. Right now I'm in the process of writing a script to update my flutter.yaml when my directory of images change. :/

Issue 2:
I'd like to be able to add an entire folder of assets without having to enumerate each one in my flutter.yaml.
Issue 1:
I tried using the @types/openlayers package and had problems.

I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript

I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).

Mention the authors (see Definitions by: in index.d.ts) so they can respond.

Authors: @osechet

I have a bunch of errors (more than 600 in index.d.ts) on my project when trying to switch to TypeScript 2.3.0. It works well with 2.2.2.

Namespace 'ol.ol' has no exported member 'Collection'.
...

Issue 2:
I tried using the latest passport/passport.d.ts file in this repo and had problems.

The authors of that type definition are cc/ @Horiuchi_H

When I use with

"@types/passport": "0.2.34",
"@types/passport-local": "1.0.29",

I got error:

ERROR in [at-loader] node_modules/@types/passport-local/node_modules/@types/passport/index.d.ts:51:5
Duplicate identifier 'export='.

ERROR in [at-loader] node_modules/@types/passport/index.d.ts:84:5
Duplicate identifier 'export='.

This line causes the error.

It works well in @types/passport 0.2.32. The error starts from @types/passport 0.2.33, and also shows in 0.2.34
Issue 1:
TypeScript Version:

1.8.7

Code

file1.ts:

export enum MyEnum {
FOO
};

export var object1 = {
foo: MyEnum.FOO
};

file2.ts:

export enum MyEnum {
BAR
}

export var object2 = {
foo: MyEnum.BAR
};

file3.ts

import * as file1 from "./file1";
import * as file2 from "./file2";

let broken = [
file1.object1,
file2.object2
];

Run tsc file1.ts file2.ts file3.ts

Expected behavior:

Either compiler emits an error saying that it cannot find a common type for broken, or compilation succeeds.

Actual behavior:

/usr/local/lib/node_modules/typescript/lib/tsc.js:32996
throw e;
^

Error: Debug Failure. False expression:
at Object.assert (/usr/local/lib/node_modules/typescript/lib/tsc.js:757:23)
at reportError (/usr/local/lib/node_modules/typescript/lib/tsc.js:15894:26)
at enumRelatedTo (/usr/local/lib/node_modules/typescript/lib/tsc.js:16444:29)
at isRelatedTo (/usr/local/lib/node_modules/typescript/lib/tsc.js:15922:34)
at propertiesRelatedTo (/usr/local/lib/node_modules/typescript/lib/tsc.js:16256:43)
at objectTypeRelatedTo (/usr/local/lib/node_modules/typescript/lib/tsc.js:16178:30)
at isRelatedTo (/usr/local/lib/node_modules/typescript/lib/tsc.js:15991:38)
at checkTypeRelatedTo (/usr/local/lib/node_modules/typescript/lib/tsc.js:15882:26)
at checkTypeSubtypeOf (/usr/local/lib/node_modules/typescript/lib/tsc.js:15757:20)
at isTypeSubtypeOf (/usr/local/lib/node_modules/typescript/lib/tsc.js:15751:20)

Note that casting the array explicitly, eg:

let broken: any[] = [
file1.object1,
file2.object2
];

let broken: any = [
file1.object1,
file2.object2
];

let broken = [
file1.object1,
file2.object2
] as any;

let broken = <any[]>[
file1.object1,
file2.object2
];

all fail, but casting either object1 or object2 to any would make compilation succeed. For example,

let broken = [
file1.object1 as any,
file2.object2
];

I'm guessing this is because the compiler does a subtype checking after it figures out the array type (which it fails to).

Issue 2:
TypeScript Version:

1.7.5 / 1.8.0-beta / nightly (1.9.0-dev.20160217)

Code

// try augmenting the SymbolContructor to have some expected symbol on it.
// in RxJS5's case, it'll be the Symbol.observable symbol from the es-observable spec.
interface SymbolConstructor {
observable: symbol;
}

interface Observablesque<T> {
[Symbol.observable]: () => Subscribable<T>
}

or

// try importing some symbol reference (I get why this might not work)
import {$$observable} from './symbol/observable';

interface Observablesque<T> {
[$$observable]: () => Subscribable<T>
}

Expected behavior:

I should be able to enforce types that have symbols on them, custom or otherwise.

Actual behavior:

I get really confused and go get myself a coffee.
Issue 1:
Description of the problem

@donmccurdy

glTF 2.0 allows each texture referenced from a material (the textureInfo structure) to include a texCoord value. By default, this is 0 to use the first UV channel. It looks like three.js doesn't support anything other than 0 here. The value is just ignored so any models using the second UV channel don't render correctly.

Is this intensional?

Three.js version

Dev

r91

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Issue 2:
Hello,

I'm running into a display bug at large output sizes with the WebGLRenderer. Fiddle here.

When setting the canvas size (with renderer.setSize) to a width or height above 4096, the output begins to distort and the camera appears to go off center. It happens with both Orthographic and Perspective cameras. You can get a feel for what's happening by just changing the width in the fiddle. Above 4096 the effect begins and becomes more and more pronounced as you go up from there.

It looks like everything renders correctly when using CanvasRenderer, so I think it's a problem in the WebGLRenderer.

Thanks!
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

In page component lifecycle method, it could access req and res in server side.

Current Behavior

In static method getInitialProps, the argument context has fields req and res which is express request & response. However, there is no way to access req and res in page component lifecycle methods, because life cycle methods are instance methods.

Context

In some cases, it is preferred to have access to req and res in component lifecycle methods in server side. I tried to have getInitialProps to return req & res as props, but next.js throw warnings about that these objects are not OK to be dehydrated.

For the time being, I used request-local-storage to transfer access from getIntialProps method. I hope next.js could have some native support for this scenario.

Issue 2:
Can you please add an example here:

https://github.com/zeit/next.js/tree/master/examples

that uses API routes to handle POST requests with also a custom Express server to serve the application? I feel like there are conflicts between routes provided by the Express server, the file system routing of Next and the API routes within the api folder. The following are related issues:

#7960

#8178

#8120

In order to make it work now I have to do something that seems pretty crazy:

pages/api/signin.js

'use strict';
module.exports = require('../../src/apiHandlers').postSignIn;

server.js

expressApp.post('/api/signin', require('./pages/api/signin'))
Issue 1:
Windows Build Microsoft Windows [Version 10.0.17763.134]

Building linux kernels using make menuconfig is functional and produces slight gibberish in the console. Attached should be screenshots of the console and xterm after launching make menuconfig in the linux kernel repository as pulled from github. (git clone https://github.com/torvalds/linux then cd linux and finally make menuconfig to reproduce what I've done.

I've tried to make the font sizes similar between WSL and Windows and in the interests of time I stopped with the fonts you see in the screenshots.

The WSL console produces this:

This is what it should look like (ignore the difference in font.)

I have no idea what VT sequences are not being handled or what's going on, I just noticed that it didn't look right.

This is probably a duplicate of #208 however I don't see exactly the same behavior as the animation in that bug, so maybe this deserves its own bug. Close it if it's a duplicate.

Issue 2:
Summary of the new feature/enhancement

New tab button and drop-down menu should be right next to the tab instead of spacing far away, like Edge. And the tab button should be designed like Edge.

Proposed technical implementation details (optional)

This is just an example. I think the new tab and drop-down button should be designed to suit with the tab button's design.

It can be designed like this: