WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
It's noted on the docs pages at https://reactjs.org/docs/strict-mode.html

react-dom currently disables/mutates the global console in strict mode.

This seems to be an intentional feature/bug that's an unnecessary inconvenience.

React version: 17.0.1

Steps To Reproduce

Use react-dom in strict mode

Try to log something

The current behavior

logging is disabled in strict-mode

The expected behavior

Possible better solutions:

Make it more obvious that the console is being mutated/disabled

Use a proxy

Issue 2:
Describe what you were doing when the bug occurred:

Recorded activity using profiler tool.

Navigated to ranked tab.

Error message displayed.

Please do not remove the text below this line

DevTools version: 4.8.1-d4eadea6c

Component stack: Wl@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:347075

div

div

div

Eo@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:267242

$c<@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:371653

n@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:280167

ra/<@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:282951

div

div

Ji@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:330056

Ge@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:209982

sn@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:219298

Wa@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:298042

ps@moz-extension://11647b02-2c4c-4d9c-945f-5dde85fa8015/build/main.js:40:376893
Issue 1:
So, i am compileing a version of rustboot that uses some changes that someone else had made so that it could display text on the screen, but when I compile I get this:

rustc: /home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/llvm/lib/IR/Instructions.cpp:276: void llvm::CallInst::init(llvm::Value*, llvm::ArrayRef<llvm::Value*>, const llvm::Twine&): Assertion `(Args.size() == FTy->getNumParams() || (FTy->isVarArg() && Args.size() > FTy->getNumParams())) && "Calling a function with bad signature!"' failed.
make: *** [main.o] Aborted (core dumped)

i have checked all the other issues about this, but none of them have helped. My code looks like this:

#![no_std]
#![allow(ctypes)]
#![feature(lang_items)]

#[allow(dead_code)]
enum Color {
Black = 0,
Blue = 1,
Green = 2,
Cyan = 3,
Red = 4,
Pink = 5,
Brown = 6,
LightGray = 7,
DarkGray = 8,
LightBlue = 9,
LightGreen = 10,
LightCyan = 11,
LightRed = 12,
LightPink = 13,
Yellow = 14,
White = 15,
}

enum DisplayInfo {
VGAWIDTH = 80,
VGAHEIGHT = 25,
VGAADDRESS = 0xb8000,
}

#[lang="sized"]
fn clear_screen(background: Color) {
let limit = 80u * 25u;
let mut i = 0u;
while i < limit {
unsafe {
*((VGAADDRESS as u16 + i as u16 * 2) as *mut u16) = (background as u16) << 12;
}
i += 1;
}
}

fn make_vgaentry(c: u8, fg: Color, bg: Color) -> u16 {
let color = fg as u16 | (bg as u16 << 4);
c as u16 | (color << 8)
}
pub fn putc(x: u16, y: u16, c: u8) {
let idx: uint = (y * VGAWIDTH as u16 * 2 + x * 2) as uint;
unsafe {
*((VGAADDRESS as u16 + idx as u16) as *mut u16) = make_vgaentry(c, Green, Black)
}
}

#[lang="fail_bounds_check"]
pub fn write_x_y(s: &[u8], x: u16, y: u16, len: uint) {
let mut i = 0u;
while i < len {
putc(x + i as u16, y, s[i]);
i += 1;
}
}

#[no_mangle]
#[no_split_stack]
pub fn main() {
clear_screen(Black);
let prompt = b"==> ";
write_x_y(prompt, 2, 3, 4);
}

I am fairly new to rust, and pretty much copy-and-pasteing stuff in. You will notice I cannot program very rust-idiomaticly becouse I have to do without the standard library, and cannot compile libcore for i386-intel-linux, which is what the loader assembly code is written for.

Issue 2:
These aren't currently well-defined by the language. If you define anything with a somewhat matching LLVM signature, it will compile. Not only does it not care about the type signatures matching what it expects, there is no handling for these being defined on the wrong types of AST nodes.
Issue 1:
Hi,

The things i've been playing the most with three.js are the shaderMaterial and the json exporter.

My goal was to export the tangent space from 3ds max, and write a synced shader to unpack them.

A crude example can be seen here:

http://dusanbosnjak.com/test/webGL/new/poredjenjeNM/poredjenjeNormala_01.html

The crude json format that im using currently looks like this:

http://dusanbosnjak.com/test/webGL/new/poredjenjeNM/meshes/tocak_guma.js

I have some issues with these indecis, and UV channels along with normals/bitangent are scrambled, these can all probably be sorted during the export.

I am a bit confused as to how this data gets mapped on the gpu.

This particular mesh has 660 triangles, 360 vertices, 429 uv/norm/bitan. During the import I assign all of these values to each face, selecting them using the exported indecis from the json. I wanted to add a bitangent attribute, but there isn't a 'slot' so to speak.

I could not figure out how to add this through the material attribute. Some examples i've seen iterate through this based on geometry.vertices but there are duplicates/splits - vertices that share two or more normals or uvs.

The way i was able to hack this was by first extending face3 to hold another group of values for the bitang, and then copying the tangent buffer during the renderer setup. When the importer imports this mesh, it sets up a flag on it, and this additional attribute is created the same way it is for the tangents or normals. But now im stuck on using this particular build.

I wonder if this makes any sense. What would be the best way of importing this additional attribute, and making sure that each and every value goes exactly where it needs to go.

Issue 2:
Description of the problem

step 1:

change timeScale

const clipDuration = clip.duration; // eg: 20s
this.animationAction = this.mixer.clipAction(clip, this.character);
// change timeScale
this.timeScale = clipDuration / duration; // eg: 20s/10s = 2
this.animationAction.setEffectiveTimeScale(this.timeScale);

step 2:

change time

// duration is from 0 to 20;
this.animationAction.time = 10;

expected

Start playback from the correct time

The actual situation

Will not end normally

Three.js version

r117

Browser

Chrome

OS

macOS

Hardware Requirements (graphics card, VR Device, ...)
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.19041.264]
PowerToys version: Release v0.18.1
PowerToy module for which you are reporting the bug (if applicable): PowerRename

Steps to reproduce

Some files' names end with _\d and I want to change their names to _0\d. So I use Power Rename to search for _(\d)$ and try to change them to _0$1 but it doesn't work.

Expected behavior

Change _\d to _0\d.

Actual behavior

They were changed to _\d$1 and enumerated.

Screenshots

Issue 2:
due to #980 and #881, it may be helpful to inform user that they may need to enable 'match all' if we detect pattern matching like $1, $2 in the replace text box
Issue 1:
see image below, this works correctly if no keyword arguments are used. This is causing the current test failures of #9575

Issue 2:
Since empty arrays [] are of type Vector{None}, it will sometimes happen that people do mistakes like this:

julia> function f1(x::Vector{Int} = [])
true
end
f1 (generic function with 3 methods)

julia> function f2(; x::Vector{Int} = [])
true
end
f2 (generic function with 1 method)

julia> f1()
ERROR: no method f1(Array{None,1})
in f1 at none:2

julia> f2()
ERROR: no method __f2#3__(Array{None,1})

At least, in the second case, the function name is a bit weird. In the first case, the line number doesn't correspond to anything interesting. If it's possible, it would be great to print a more explicit message, like "default argument value is of an incorrect type".
Issue 1:
Summary of the new feature/enhancement

Ability to remap a single key (² for example, sleeping in the top left corner of my KB), and assign it for example to alt+space, in order to open powertoys run, or to "open a new terminal", or whatever

Issue 2:
📝 Provide a description of the new feature

What is the expected behavior of the proposed feature? What is the scenario this would be used?

When the dark mode is on, .md files should be rendered in a dark theme in the preview pane.

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Issue 1:
seems like 90% of the time I'm interacting with a database most of my DB code doesn't care if i'm within a TX or not. often there are queries I'm executing in various places with different contexts, some of which require a transaction, some which don't. But I can't share the code without writing my own Queryer style interface. now granted its only a few lines, but it seems like this is something that should just be in the sql package itself.

I'm happy to do the work, submit the PR etc. just curious if there is any object to adding it and why.

Issue 2:
Hi,

I'm proposing a interface that implements all functions in sql.DB and sql.Tx that takes a query string as one of its arguments. This could be useful when implementing "dumb" functions that retrieves information but in itself dose not need to be prepared however might be used to verify whether to commit or rollback.

The interface I'm proposing is: (The name can of course be changed)

type QueryAble interface {
Exec(query string, args ...interface{}) (sql.Result, error)
Prepare(query string) (*sql.Stmt, error)
Query(query string, args ...interface{}) (*sql.Rows, error)
QueryRow(query string, args ...interface{}) *sql.Row
}

This is an example function Get that can be used with or without transactions.

func Get (q Queryable)(int){
var test int
res , _ := q.Query("SELECT COUNT(*) FROM table;")
res.Next()
res.Scan(&test)
res.Close()
return test
}

func GetExample(db *sql.DB){

//When you just want to retrieve the information, no need for a transaction
fmt.Printf("Current len of Table %d\n", Get(db))

//Make a change
tx, _ :=db.Begin()
// Add data to table
if Get(tx) > 2 {
fmt.Printf("Table to large: %d robacking to: %d \n", Get(tx) , Get(db))
tx.Rollback()
} else {
fmt.Printf("Table update new len %d\n", Get(tx))
tx.Commit()
}
}
Issue 1:
datepicker becomes ugly:

up\down arrows placed near widget center

dropdown arrow disappeared

https://dl.dropbox.com/u/17458620/baddate.png

if i remove display: inline-block; from css same html is fine

https://dl.dropbox.com/u/17458620/gooddate.png

Issue 2:
Hi i found stange behavior date input in new chrome 24

link: http://jsfiddle.net/bteam/HvL25/

screenshoot:
Issue 1:
With some dataframes we encounter strange behaviours of the clustermap, where a dendrogram on one axis does not align with the heat map cells as it has too few branches.

An example:

import seaborn as sns
import pandas as pd
import matplotlib.pyplot as plt

df = pd.DataFrame({'A': {0: 0.5, 1: 0.0, 2: 1.0, 3: 0.0, 4: 0.0, 5: 0.0, 6: 0.0, 7: 0.0, 8: 0.0, 9: 0.0, 10: 0.0, 11: 0.5, 12: 0.0, 13: 0.5, 14: 0.0, 15: 0.0, 16: 0.0, 17: 0.0}, 'B': {0: 0.0, 1: 0.0, 2: 0.0, 3: 0.0, 4: 1.0, 5: 1.0, 6: 0.0, 7: 0.0, 8: 0.0, 9: 0.5, 10: 0.0, 11: 1.0, 12: 0.0, 13: 0.0, 14: 0.0, 15: 0.0, 16: 0.0, 17: 0.0}, 'C': {0: 1.0, 1: 0.0, 2: 1.0, 3: 1.0, 4: 1.0, 5: 1.0, 6: 1.0, 7: 0.5, 8: 0.5, 9: 0.0, 10: 1.0, 11: 0.0, 12: 0.0, 13: 0.0, 14: 0.0, 15: 0.5, 16: 0.5, 17: 0.0}, 'D': {0: 0.0,1: 0.5, 2: 1.0, 3: 0.5, 4: 0.5, 5: 0.5, 6: 0.0, 7: 0.5, 8: 0.0, 9: 0.0, 10: 1.0, 11: 1.0, 12: 1.0, 13: 1.0, 14: 0.5, 15: 0.0, 16: 0.0, 17: 1.0}})

sns.clustermap(df, cmap='Greens', col_cluster = False, linewidth=0.5, linecolor='red', tree_kws={'colors':'blue'})
plt.show()

In the resulting figure one can see that the dendogram leaves (blue) are not aligned with the heatmap cells (red grid), and that the dendrogram has only 13 leaves whereas the dataframe has 18 rows.

Any ideas why?

Versions

Seaborn 0.11.1

Scipy 1.6.3

Pandas 1.2.4

Issue 2:
Somehow similar to #2377, but for kind='hist' and with common_norm=False being ignored.

If I understand it well, passing common_norm=False to sns.distplot should produce plots with independent "z" scale. While this is the behaviour for kde plots, it seems to be ignored for bivariate histograms unless hue is also specified.

Test case:

x, y = np.random.randn(2, 200)
z = [0] * 150 + [1] * 50
sns.displot(x=x, y=y, col=z, kind="hist", cbar=True, common_norm=False)
sns.displot(x=x, y=y, col=z, hue=z, kind="hist", cbar=True, common_norm=False)

Running seaborn version 0.11.1

(I tried to look for other (open or closed) related issues, hope not duplicating them)
Issue 1:
When I pass cursor as data to DataFrame constructor an error occurs.

cursor = sqlite.execute(sql)
pd.DataFrame(cursor)

/usr/lib/python3/dist-packages/pandas/core/frame.py in __init__(self, data, index, columns, dtype, copy)
255 copy=copy)
256 elif isinstance(data, collections.Iterator):
--> 257 raise TypeError("data argument can't be an iterator")
258 else:
259 try:

TypeError: data argument can't be an iterator

But normal generators is accepted

def gen():
yield (1,2,3)
yield (4,5,6)
yield (7,8,9)

pd.DataFrame(gen())
Out[171]:
0 1 2
0 1 2 3
1 4 5 6
2 7 8 9

It feels like inconsistence.

Issue 2:
Hi there,

I have a codebase that (so far) consumes data series in the form of dict-yielding iterators, similar in form to how DataFrame's constructor accepts a list of such. Unfortunately it seems from current implementation of that constructor, there is no straightforward way to consume from an iterator straight into a DataFrame.

For example, I have a row factory for sqlite3 written in C that produces dicts. If pandas would accept an iterator, it should be possible to consume a series directly from speedy storage code into speedy data structure code. :)

Is there an inherent limitation preventing this? Otherwise with a few pointers I would be willing to try contribute the patch myself.

Thanks,

David
Issue 1:
In 1.0.0-beta.20 If I set autoHideDuration={null}, onRequestClose() is triggered immediately as if the value is 0

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

Expected Behavior

The docs say autoHideDuration will be disabled if set to null

Current Behavior

Currently null is treated like 0, however I can set it to undefined and it works like it used to.

I want to keep the snackbar visible indefinitely only if there are more details (accessed through a link in the snnackbar), so code looks something like this:

<Snackbar
onRequestClose={onDismiss}
autoHideDuration={hasMoreDetails ? null : 4000}
action={[ renderDetailsButton(hasMoreDetails), <CloseButton /> ]}
/>

The workaround is fine

autoHideDuration={hasMoreDetails ? undefined : 4000}

.. but then the docs need updating

Your Environment

Tech
Version

Material-UI
1.0.0-beta.20

React
15.6.2

browser
chrome

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

Expected Behavior

It should have large padding to make click easier.

Example from material.io docs

Example from Angular Material2

Also, on the image above, it has hover color, that's nice too.

Current Behavior

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.30

React
16.2.0

browser
Chrome 64
Issue 1:
Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Class hierarchy

Main (entry, common chunk)
/ \
ClassA ClassB
\ \
\ ClassC
\ /
ReusableComponent

Main require ClassA and ClassB using require.ensure().

ClassB require ClassC using require.ensure().

ClassA and ClassC require ReusableComponent using simple require().

Finaly webpack emits following chunks:

0.js - contains ClassA, ReusableComponent

1.js - contains ClassB

2.js - contains ClassC, ReusableComponent

main.js - contains Main class

Problem

I try to configure CommonsChunkPlugin to move ReusableClass to main chunk in order to remove code duplication.

new webpack.optimize.CommonsChunkPlugin({
name: 'main',
minChunks: 2,
children: true
})

And webpack does not do this.

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

repo: https://github.com/rasentry/webpack-chunks

What is the expected behavior?

ReusableCompoent class has to move to chunk main.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Node.js 7.2.1

Windows 10

Issue 2:
Bug report

▶️ You can try this repo to reproduce the bug: https://github.com/jaguilar87/webpack-issue-8099

What is the current behavior?

Since 4.20.0 I am unable to build using nested output.library:

{
entry: {
a: path.resolve(__dirname, 'a.js'),
b: path.resolve(__dirname, 'b.js'),
},
output: {
jsonpFunction: `webpackJsonp__[name]`,
library: ['globalVariable', '[name]'],
filename: `[name]--[chunkhash].js`,
path: path.resolve(__dirname, 'dist'),
publicPath: '/',
},
...

The output file starts with:

var undefined = ...

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

Use the previous configuration and try to build a package.

What is the expected behavior?

The output file should start with:

var globalVariable = typeof globalVariable === "object" ? globalVariable : {}; globalVariable["a"] = ...

Other relevant information:

webpack version: 4.20.0-4.20.2

Node.js version: v9.6.1

Operating System: Mac OS High Sierra
Issue 1:
Currently campers can still create a freeCodeCamp account using GitHub and this is leading to a lot of support issues. We need to update our authentication code to prevent account creation using GitHub.

Issue 2:
As a user, the initial email address I used to create my account will remain my email address even if I have a different email address on GitHub.

As a user, when I visit the /signin path, I only see an option to sign up with email, or to click a link that says "click here if you already have an account" - which then takes me to a sign in view with both email and GitHub login options.

Disable the ability for GitHub OAuth to create a new account

Add the original email validation as being discussed in #15205

edit(@BerkeleyTrue): Updated user stories

edit(@raisedadead): Updated user stories for email validation
Issue 1:
None - of the CSS styles work and the examples on your own website are not functional since none of the drop-downs work. Once you get your examples fixed - i may consider a download and using it but this is not a really good foot forward.

Issue 2:
Hovering the menu does nothing.

Failed to load resource: HTTP 404 /dist/js/bootstrap.js

http://examples.getbootstrap.com/carousel/index.html
Issue 1:
I've seen this with coffee-loader and cjsx-loader, but #1249 also reports this problem with jsx-loader. The problem seems to appear when we require the same file from outside a module and from within the module:

a.coffee (within module bb):

module.exports = {just: 'an object'}

b.coffee (within module bb):

module.exports = require './a'

odd.coffee:

a = require('bb/a');
b = require('bb/b');
console.log a is b # should be true

When you run coffee odd.coffee, sure enough, you get: true.

But when you run it through Webpack (with coffee-loader):

You get module a bundled twice:

[0] ./odd.coffee 94 bytes {0}
[1] /Users/guillermo/Docs/Docs.Prog/JavaScript/bb/a.coffee 56 bytes {0} [built]
[2] /Users/guillermo/Docs/Docs.Prog/JavaScript/bb/b.coffee 59 bytes {0}
[3] /Users/guillermo/Docs/Docs.Prog/JavaScript/bb/a.coffee 56 bytes {0} [built]

What's worse, you get an unexpected result in the browser: false

Issue 2:
Bug report

What is the current behavior?

There may be duplicate resource urls in the sourcemaps. Which is neither defined as valid, nor as invalid.

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

This is actually a query about an existing bug report:

https://bugs.chromium.org/p/chromium/issues/detail?id=1329997

It's a known bug now in Chrome 102, which has been bugging me for 3 weeks now.

I was wondering if there's a simple way to deduplicate urls in the sourcemap, so we can workaround the Chrome bug.

People may come here in search of a bugreport on webpack (I initially though it was a webpack issue and downgraded but it did not help).

What is the expected behavior?

Should play nice with Chrome Devtools.

The guys at Chromium say that they have been going back and forth between considering duplicate urls and deduplicating them. One side of it causes one kind of bug, the other side causes another kind of bug.

So if there's an override from webpack, we could avoid this hassle altogether.

Other relevant information:

webpack version: 5.73.0

Node.js version: 16.3.2

Operating System: WIndows 10

Additional tools:
Issue 1:
Given the following two files in a project:

//app.ts
enum MyEnum {
one,
two,
three
}

//class.ts
namespace MyNamespace {
//class must be exported for bug
export class MyClass {
private message = "hello";

log() {
//setTimeout must be returned, not just called
return setTimeout(() => console.log(this.message));
}
}
}

The generated JavaScript for MyClass.log will erroneously reference this instead of _this inside of the setTimeout method, i.e. it will emit:

MyClass.prototype.log = function () {
return setTimeout(function () { return console.log(this.message); });
};

instead of:

MyClass.prototype.log = function () {
var _this = this;
return setTimeout(function () { return console.log(_this.message); });
};

Here are the conditions necessary for this to happen. They may not be the only conditions necessary (every time I think I have this bug nailed another condition emerges), so if you cannot reproduce it let me know and I will send a full project that exhibits the bug.

"Compile on save" must be enabled

"Combine JavaScript output into file" must be enabled, with a file specified (say, out.js)

"Generate declaration files" must be enabled

MyClass must be exported from a namespace

setTimeout must be returned from MyClass.log, not just called

The output of app.ts must come before class.ts in the combined output file. I believe this is satisfied by the fact that "app.ts" is alphabetically before "class.ts".

If these conditions are satisfied, and if you alter app.ts without altering class.ts and save, the out.js that is generated in response to that save will have the erroneous code.

This is using Visual Studio 2015 and TypeScript 1.8.

Issue 2:
TypeScript Version:

1.8.0 (through npm), 1.8.2 (visual studio)

Code

namespace Bug {

export interface IDef {
test2: () => any;
test: (e:any) => any;
}

class TestController {
protected from: number;

public prepareDefinition(def: IDef) {
return def;
}

public prepared = this.prepareDefinition({
test2: () => {
var q = this.from; // uses _this;
var helper = () => {
var q2 = this.from; // uses _this
};
return {
fn1: (v) => {
var q3 = this.from; //uses this
},
fn2: helper
}
},
test: (e) => { }
}
);

}

}

The code is compiled to ES5

Expected behavior:

All the 3 assignments (q, q2, q3) should compile to using _this

Actual behavior:

The q3 assignment refers to "this". The code above (with the exception of the helper(), which I kept for comparison) seems to be the minimal code to trigger the issue - even removing test() or its parameters (or parameter of fn1) results in what I believe is the correct code (using _this). The code also compiles correctly in 1.7.x