WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Trying to build the project (and using Babel JS)

I get these error messages

(Something in the mergeAndPrefix => Extend chain is trying to create two copies of teh same property on these lines)

ERROR in ./lib/icon-button.jsx

Module parse failed: F:\Projects\app\node_modules\babel-loader\index.js?stage=1!F:\Projects\app\material-ui\src\icon-button.jsx Line 72:

Duplicate data property in object literal not allowed in strict mode

| transition: Transitions.easeOut(),

| padding: this.getSpacing().iconSize / 2,

| width: this.getSpacing().iconSize * 2,

| height: this.getSpacing().iconSize * 2

| },

@ ./lib/index.js 16:14-38

ERROR in ./lib/tabs/tab.jsx

Module parse failed: F:\Projects\app\node_modules\babel-loader\index.js?stage=1!F:\Projects\app\material-ui\src\tabs\tab.jsx Line 36:

Duplicate data property in object literal not allowed in strict mode

| textAlign: 'center',

| verticalAlign: 'middle',

| height: '48px',

| color: Colors.white,

| opacity: '.6',

@ ./lib/index.js 46:7-28

ERROR in ./lib/menu/subheader-menu-item.jsx

Module parse failed: F:\Projects\app\node_modules\babel-loader\index.js?stage=1!F:\Projects\app\material-ui\src\menu\subheader-menu-item.jsx Line 43:

Duplicate data property in object literal not allowed in strict mode

| height: subheaderHeight + gutterMini,

| lineHeight: subheaderHeight + 'px',

| color: this.getTheme().textColor,

| borderTop: 'solid 1px ' + this.getTheme().borderColor,

| paddingTop: gutterMini,

@ ./lib/menu/menu.jsx 17:24-56

ERROR in ./lib/styles/themes/light-theme.js

Module parse failed: F:\Projects\app\node_modules\babel-loader\index.js!F:\Projects\app\material-ui\src\styles\themes\light-theme.js Line 145:

Duplicate data property in object literal not allowed in strict mode

| separatorColor: 'rgba(0, 0, 0, .175)',

| menuHoverColor: 'rgba(0, 0, 0, .10)',

| menuHoverColor: Colors.white

| }

| };

@ ./lib/styles/theme-manager.js 9:9-40

ERROR in ./lib/enhanced-textarea.jsx

Module parse failed: F:\Projects\app\node_modules\babel-loader\index.js?stage=1!F:\Projects\app\material-ui\src\enhanced-textarea.jsx Line 101:

Duplicate data property in object literal not allowed in strict mode

| style: inputStyles,

| rows: this.props.rows,

| style: AutoPrefix.all(inputStyles),

| onChange: this._handleChange }))

| );

@ ./lib/text-field.jsx 13:23-53

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

I found the documentation diverged from the version of this package I have installed which caused a lot of wasted time trying to debug non existent issues. It should be possible to easily view the documentation for a specified version of this package.

Tech
Version

Material-UI
1.0.0-beta.23
Issue 1:
Hello,

Why a date field with the options below is it limited. Choice available between 1902 and 2037?

$Builder-> add ('date', 'date', array (
'input' => 'datetime'
'widget' => 'choice'
'years' => range (1850,2050) "
));

documentation says:

If timestamp is used, DateType is limited to dates entre Fri, Dec. 13, 1901 8:45:54 p.m. GMT and Tue, January 19, 2038 3:14:07 GMT on 32bit systems. This is due to a limitation in PHP Itself.

Is it normal that the option datetime have the same limitation?

For information i use symfony 2.3

Thank you for this great framework.

Issue 2:
https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Form/Extension/Core/Type/DateType.php#L277

When I set date options like

$builder->add('expire', 'date', array('years' => range(2000, 2100)));

year choice field shows

<select>
<option value="2000">2000</option>
<option value="2000">2000</option>
...
<option value="2037">2037</option>
<option value="2038"></option>
<option value="2039"></option>
...
<option value="2100"></option>

It's perhaps because gmmktime on 32-bit is only suitable for up to 2038-01-19 03:14:07 .

On 32-bit php

$ php -r 'echo gmmktime(0,0,0,6,15,2037);'
2128636800
$ php -r 'echo gmmktime(0,0,0,6,15,2038);'
## shows nothing ##
$ php -r 'var_dump(gmmktime(0,0,0,6,15,2038));'
bool(false)

On 64-bit php

$ php -r 'echo gmmktime(0, 0, 0, 6, 15, 2037);'
2128636800
$ php -r 'echo gmmktime(0, 0, 0, 6, 15, 2038);'
2160172800
Issue 1:
I'm using 6to5 on a big app. I like that you guys use regenerator to implement generators, so I'm confused why you care that things get renamed. I have a lot of generator functions, and if I minimize, I see the error "GeneratorFunction renamed?"

http://jlongster.com/s/genfunc-err.png

If there isn't a solution to this, this may be a showstopper for me using 6to5. Surely you guys support minification?

Issue 2:
See here.

The author of this code tries to be clever and set GF.name in the line above, but this actually isn't possible to do (try it in Chrome or Firefox, it will just ignore the assignment).

Having "GeneratorFunction" as the constructor name is mandated by the specification. However, I would argue it's not a very important part of the specification, and that convenient minification is much more important. At the very least, the throw line should be removed, so people who don't care what the constructor name is aren't affected. It's worth noting that Regenerator itself does not care what the constructor name is.

However, there is a case for removing the "GeneratorFunction" trick altogether: it would allow for removing the mark() call in the following, improving the readability of the generated code:

root@smogon-dev:~$ echo 'function* foo() { }' | 6to5
"use strict";

var foo = regeneratorRuntime.mark(function foo() {
return regeneratorRuntime.wrap(function foo$(_context) {
while (true) switch (_context.prev = _context.next) {
case 0:
case "end": return _context.stop();
}
}, foo, this);
});

Here's the issue which lead to mark being added: facebook/regenerator#48. The primary reason seems to be allowing the co library to perform some magic to distinguish between regular functions and generator functions. I guess I'm not swayed by this because co isn't very useful when you have async functions (like we do).
Issue 1:
I've tried to create a simple example that utilizes workers to send and receive messages, but the main "thread" for lack of a better word fails to receive any kind of message from my worker.

According to deno -V I'm using deno 1.5.3

Below are my test files, run them with deno run --unstable --allow-read test.ts

test.ts (click to expand)

const worker = new Worker(new URL('testworker.ts', import.meta.url).href, { type: 'module', deno: true });

worker.onmessage = (e) => {
//This is never executed
console.log('Stuff in worker done:', e.data);
};

worker.postMessage('test');

testworker.ts (click to expand)

import Random from 'https://deno.land/x/random@v1.1.2/Random.js';

async function doStuff(data: any) {
console.log('Doing stuff:', data);
const r = new Random();
const randInt = r.int(200, 2000);
await new Promise((res, _) => setTimeout(() => res(randInt), 1000));
}

//deno-lint-ignore ban-ts-comment
//@ts-ignore
onmessage = async (e) => {
try {
//deno-lint-ignore ban-ts-comment
//@ts-ignore
postMessage(await doStuff(e.data))
console.log('Stuff done:', e.data);
} catch (e) {
console.error('Stuff error', e);
}
}

The output shows the following:

Output (click to expand)

Doing stuff: test
Stuff done: test

As you can see, the line Stuff in worker done: is never logged to the console. Unless I'm doing something wrong that's just not how it's supposed to work as far as I'm aware.

Issue 2:
Example:

worker.ts:

self.addEventListener('message', ev => {
try {
const {data} = ev as MessageEvent;
console.log('worker <- main:', data);
const value = data > 0 ? data * 2 : undefined;
(self as any).postMessage(value);
console.log('worker -> main:', value);
}
catch (ex) {
console.error(ex);
}
});

main.ts:

const data = 0;

const main = async (): Promise<void> => {
let resolve: (value: number) => void;

const workerUrl = new URL('worker.ts', import.meta.url).href;
const worker = new Worker(workerUrl, {deno: true, type: 'module'});

const handleWorkerMessage = (ev: MessageEvent): void => {
const {data} = ev;
console.log('main <- worker:', data);
resolve(data);
worker.terminate();
};

worker.addEventListener('message', handleWorkerMessage);
worker.addEventListener('messageerror', () => console.log('message error'));
worker.addEventListener('error', () => console.log('error'));

const result = await new Promise(res => {
resolve = res;
worker.postMessage(data);
console.log('main -> worker:', data);
});

console.log(result);
};

if (import.meta.main) main();

When run, it just hangs forever after the worker posts undefined back to the main process because the handler is never invoked:

example % deno run --unstable --allow-read=. main.ts
main -> worker: 0
worker <- main: 0
worker -> main: undefined
^C

If—on line 1 of main.ts—data is changed to a number greater than 0, the worker will post back a number instead of undefined and everything works as expected:

example % deno run --unstable --allow-read=. main.ts
Check file:///Users/jesse/example/main.ts
main -> worker: 1
worker <- main: 1
worker -> main: 2
main <- worker: 2
2

I'm not sure why this behavior is happening, but undefined is a meaningful value, and this seems like a bug.
Issue 1:
Sorry, the best testcase I have right now is Servo master. If you run the binary under gdb and try to break anywhere in the compositing crate, the symbols just don't exist. You can't break by filename either. You can break on mangled symbols, but there are no source positions. Other crates (like script, for example) work perfectly fine.

Issue 2:
Reproduce Steps

Create a project using cargo new test_rust

Edit the lib.rs file to:

pub trait HasArea {
fn area(&self) -> f64 {
0f64
}
}
pub fn print_area<T: HasArea>(shape: T) -> f64{
shape.area()
}
fn main() {
struct Square {
side: f64,
}
impl HasArea for Square {
fn area(&self) -> f64 {
self.side * self.side
}
}

let s = Square {
side: 20f64,
};

let b = print_area(s);
println!("Area: {}", b);
}

Basically, it defines a trait and a generic method which accepts it as an argument.

3. Run rustc -g src/lib.rs to compile it and run gdb lib to debug. It could step into the print_area() function and the result is correct as well.

4. If I move the main() function into a standalone file main.rs and referece this library using external crate test_rust, call cargo build to build the library(I already set the debug flag in Cargo.toml) and run rustc -g -extern test_rust=target/libXXXX main.rs. I could not debug into the print_area() function, though the running result is correct. In gdb, it just goes to next line instead of going to the function definition.

Please note if I don't use generic for the function, both cases are working as expected.

OS

Archlinux x86_64

Rust version

rustc 0.13.0-nightly (81eeec0 2014-11-21 23:16:48 +0000)

binary: rustc

commit-hash: 81eeec0

commit-date: 2014-11-21 23:16:48 +0000

host: x86_64-unknown-linux-gnu

release: 0.13.0-nightly
Issue 1:
The following code:

fn main() {
[].iter();
}

results in the following compiler error:

test.rs:2:1: 2:3 error: internal compiler error: borrow-vec associated with bad sty: &ty_err
This message reflects a bug in the Rust compiler.
We would appreciate a bug report: https://github.com/mozilla/rust/wiki/HOWTO-submit-a-Rust-bug-report
test.rs:2 [].iter();
^~
task 'rustc' failed at 'explicit failure', /home/sami/Programmes/rust-git/src/rust/src/libsyntax/diagnostic.rs:76
task '<main>' failed at 'explicit failure', /home/sami/Programmes/rust-git/src/rust/src/librustc/lib.rs:396

I’m using revision df41115 (2013-12-01), with c6e934f cherry-picked to make make install work (pull request 10753, now merged into master).

Issue 2:
fn main() {
let v = &[];
let it = v.iter();
}

vec-ice.rs:3:13: 3:14 error: internal compiler error: borrow-vec associated with bad sty: &ty_err
vec-ice.rs:3 let it = v.iter();
^

(Doesn't happen with .slice.)
Issue 1:
Willis Blackburn opened SPR-9068 and commented

I'm trying to implement RFC 2324 but cannot return HTTP response code 418 because it's not defined in the HttpStatus enumeration.

More generally, the enumeration of specific status values precludes the use of any others.

Affects: 3.1 GA

Issue Links:

#11418 RestTemplate throws IllegalArgumentException when HTTP status is not in the HttpStatus enum ("duplicates")

Issue 2:
Rick Evans opened SPR-2566 and commented

(c.f. comment from Matt Raible on #7043)

It would be cool if this tag supported a "key" attribute so you could read directly from your messageSource. For example:

<form:label path="firstName" key="user.firstName"/>

Just a thought.

Matt

Affects: 2.0 RC3

Issue Links:

#8047 Provide comprehensive I18N support for the Spring form tag library. ("is depended on by")

#6768 Add MessageSource support to HTML taglib ("is duplicated by")

15 votes, 12 watchers
Issue 1:
Installed the react development tools to chrome Version 89.0.4389.114 (Official Build) (64-bit)

Open my development version of my react app localhost:3000 with several components and I see the react icon

Go to the inspect and component to and nothing is showing

I'm using this chode https://codesandbox.io/s/react-devtools-dk9gj?fontsize=14

and when you open this in chrome it works.

I open it from localhost and it does not work.

"react": "16.8.6",
"react-dom": "16.8.6",
"react-scripts": "^4.0.3"

npm --version 7.6.3

nodejs v14.16.0

Steps To Reproduce

Link to code example:

The current behavior

The expected behavior

Issue 2:
When I use DevTools to select an element on the page, it can't jump/find it.

It also doesn't show it in the Components page.

This was checked by finding its parent and checking the children, non of the newly generated ones are there.

As a probably related bug Profiler doesn't show/record the changes.

React version: 16.13.1

React-dom version: 16.13.1

Parcel: 2.0.0-beta.1

Steps To Reproduce

Have a parent element

Have a child element (A)

Using conditional rendering (condition ? A : B) "hide" A

B now shows

Try and select B using Chrome Dev Tools's "Select an element in the page to inspect it"

Jumps nowhere/Can't find it manually in the list.

Example

In this example, I demonstrate that it works on the Search Bar (light grey bar) which is the TextField=>InputBase tree, and the Container that contains the search & images and how hovering over the image doesn't do anything.

I then click on the image and nothing happens & the state panel on the right of Dev Tools empties itself.

The current behaviour

Can't find newly rendered components in React Dev Tools Components panel

The expected behavior

Being able to find the newly rendered components in React Dev Tools Components panel
Issue 1:
What problem does this feature solve?

Currently if we render a slot for multiple times (eg. inside a v-for loop), we'll get

Duplicate presence of slot "${name}" found in the same render tree - this will likely cause render errors.

I know it's intentional to prevent render errors (like losing correct data binding) but consider the following use case: I have a v-breadcrumbs component which has a default item separator of a text node /, and I want to allows users to specify their own separators which can be anything, like an <v-icon> component.

Currently if I want to make it work, I have to define a scoped slot in the v-breadcrumbs component and bind nothing to it:

<slot name="sep" v-bind="{}">/</slot>

And component users must define slot-scope on it and not use anything from it:

<v-breadcrumbs>
<v-icon slot="sep" slot-scope="_" name="angle-right"/>
</v-breadcrumbs>

And currently Vue is using slots as fallbacks for scoped slots with the same name. Whether the users can use a slot doesn't rely on if they want data from slot scope, but on whether the slot is gonna be rendered for multiple times inside the component self, this may raise more confusion for our users (like #8175).

So why don't we just get rid of such caveats and let a slot to be rendered more than once? We can clone them on duplication to prevent render errors as we already run the scoped slot function each time anyway. This makes the logic a lot simpler for users IMO: if we do not expect to use data from the slot scope, just use a slot, otherwise we'll always have to declare slot-scope to create the binding.

In addition, this would make documenting the (scoped) slots of a component more consistent, we just declare the data structure for a slot scope and users can decide if they want some data to bind to the slot-scope and don't need to care about how many times it will be rendered.

What does the proposed API look like?

No additional API needed, just clone the slot nodes upon render and remove the waring about duplicated slots.

It may be implemented in userland today in a quite hacky way, see: https://codesandbox.io/s/lp11y2wovz

I just tweaked the cloneVNode function from the Vue core a little bit and it seemed to be working as expected using render function (without losing reactivity and event binding). There maybe some other edge situations I missed so correct me if it's not such trivial.

Issue 2:
What problem does this feature solve?

github missing repository vuejs/vue-ssr-webpack-plugin, i update webpack to version 5 and have error

[vue-server-renderer-webpack-plugin] webpack config output.libraryTarget should be "commonjs2".

What does the proposed API look like?

in my output.libraryTarget is libraryTarget: 'commonjs2'
Issue 1:
Example

import { readJson } from 'https://deno.land/std/fs/mod.ts'

const f = await readJson('./settings.json')

deno run https://raw.githubusercontent.com/SimonSiefke/deno-sample/master/src/index.ts

Expected behavior:

It compiles without errors.

Current behavior:

Compile https://raw.githubusercontent.com/SimonSiefke/deno-sample/master/src/index.ts
error TS2339: Property 'utime' does not exist on type 'typeof Deno'.
await Deno.utime(dest, statInfo.atime, statInfo.mtime);
~~~~~
at https://deno.land/std/fs/copy.ts:90:16

error TS2339: Property 'utimeSync' does not exist on type 'typeof Deno'.
Deno.utimeSync(dest, statInfo.atime, statInfo.mtime);
~~~~~~~~~
at https://deno.land/std/fs/copy.ts:101:10

error TS2339: Property 'symlink' does not exist on type 'typeof Deno'.
await Deno.symlink(originSrcFilePath, dest, type);
~~~~~~~
at https://deno.land/std/fs/copy.ts:114:14

error TS2339: Property 'utime' does not exist on type 'typeof Deno'.
await Deno.utime(dest, statInfo.atime, statInfo.mtime);
~~~~~
at https://deno.land/std/fs/copy.ts:119:16

error TS2339: Property 'symlinkSync' does not exist on type 'typeof Deno'.
Deno.symlinkSync(originSrcFilePath, dest, type);
~~~~~~~~~~~
at https://deno.land/std/fs/copy.ts:132:8

error TS2339: Property 'utimeSync' does not exist on type 'typeof Deno'.
Deno.utimeSync(dest, statInfo.atime, statInfo.mtime);
~~~~~~~~~
at https://deno.land/std/fs/copy.ts:137:10

error TS2339: Property 'utime' does not exist on type 'typeof Deno'.
await Deno.utime(dest, srcStatInfo.atime, srcStatInfo.mtime);
~~~~~
at https://deno.land/std/fs/copy.ts:157:16

error TS2339: Property 'utimeSync' does not exist on type 'typeof Deno'.
Deno.utimeSync(dest, srcStatInfo.atime, srcStatInfo.mtime);
~~~~~~~~~
at https://deno.land/std/fs/copy.ts:185:10

error TS2339: Property 'link' does not exist on type 'typeof Deno'.
await Deno.link(src, dest);
~~~~
at https://deno.land/std/fs/ensure_link.ts:28:14

error TS2339: Property 'linkSync' does not exist on type 'typeof Deno'.
Deno.linkSync(src, dest);
~~~~~~~~
at https://deno.land/std/fs/ensure_link.ts:52:8

error TS2339: Property 'symlink' does not exist on type 'typeof Deno'.
await Deno.symlink(src, dest, srcFilePathType);
~~~~~~~
at https://deno.land/std/fs/ensure_symlink.ts:31:14

error TS2339: Property 'symlinkSync' does not exist on type 'typeof Deno'.
Deno.symlinkSync(src, dest, srcFilePathType);
~~~~~~~~~~~
at https://deno.land/std/fs/ensure_symlink.ts:58:8

Found 12 errors.

Additional information

deno --version
deno 1.0.0-rc1
v8 8.2.308
typescript 3.8.3

Issue 2:
Parts of the standard library now require the --unstable option to function. I suggest we move all things that use unstable APIs into different files which are then re-exported by multiple entry points: mod.ts and unstable.ts. unstable.ts would re export mod.ts + all unstable features.
Issue 1:
One of my coworkers made the following observation:

I noticed the julia profiler is sampling all the threads in a deterministic order, which can skew the profile for multithreaded code. When you stop one thread holding an important mutex, you can get a pileup of threads blocking for that mutex, which can make it seem like there's lots of mutex contention, but really that mutex contention is caused by the profiler.

We talked about this with @JeffBezanson last month, and I'm opening an issue about this so we don't forget. :)

We guessed probably the best thing to do is to select one thread at random and record a sample for just that thread? But it'd be best to consult an expert on multithreaded profiling.

Issue 2:
julia> sort(unsigned.([1,0,1,0,1,1]), rev=true)
6-element Vector{UInt64}:
0x0000000000000001
0x0000000000000000
0x0000000000000001
0x0000000000000000
0x0000000000000001
0x0000000000000001

see #42718 for why this bug exists
Issue 1:
From URL: https://flutter.io/get-started/test-drive/

In Android Studio 3.1 for Linux it also asks you to fill out the Flutter SDK path

Issue 2:
As the title says, I can build from the command line and install on my device, but when I try to run an archive in Xcode, I get the following error.

ld: warning: directory not found for option '-L/Volumes/Jeff/Library/Developer/Xcode/DerivedData/Runner-dhytviduagshlmbbozuwftfdndsj/Build/Intermediates.noindex/ArchiveIntermediates/Runner/BuildProductsPath/Release-iphoneos/flutter_youtube'
ld: warning: directory not found for option '-L/Volumes/Jeff/Library/Developer/Xcode/DerivedData/Runner-dhytviduagshlmbbozuwftfdndsj/Build/Intermediates.noindex/ArchiveIntermediates/Runner/BuildProductsPath/Release-iphoneos/video_player'
ld: library not found for -lXCDYouTubeKit
clang: error: linker command failed with exit code 1 (use -v to see invocation)