WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Bug report

What is the current behavior?

webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Resolving '.pnpm/es5-ext@0.10.53/node_modules/es5-ext/array/#/clear' in /Users/scamden/creditiq/uno/common/temp/node_modules/.pnpm/es6-iterator@2.0.3/node_modules/es6-iterator for build dependencies doesn't lead to expected result '/Users/scamden/creditiq/uno/common/temp/node_modules/.pnpm/es5-ext@0.10.53/node_modules/es5-ext/array/#/clear.js', but to '/Users/scamden/creditiq/uno/common/temp/node_modules/.pnpm/es5-ext@0.10.53/node_modules/es5-ext/array/#/clear.js' instead. Resolving dependencies are ignored for this path.

warning on writing persistent cache in development mode if the dep has a # in the path and has already been loaded by node prior to dependency resolution for the cache.

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

https://github.com/creditiq/simple-repros/tree/webpack-cache-resolution-warning

Repro:

Clone the above

npm i

cd nested

npm run build

(note: this branch also contains a repro for bug: #12156, if you do the same steps but replace step 3 with cd \#nested)

Result:

warning above

Expected:

no warning

I have tracked the bug down to a \u0000 in the resolved result (that was added by webpack code when escaping the # one stack frame above the warning) that is not there in the job.expected value.

The expected value in my case was resolved via the require.cache inside the RBDT_FILE_DEPENDENCIES job as a RBDT_RESOLVE_CJS_FILE_AS_CHILD. I checked every path and child path one level deep in that cache and not one value had a \u0000 in it so I'm guessing the fix is to escape # with \0 when the file was found in the require.cache, but the code is a bit over my head so hopefully this lead gives someone more familiar a light bulb. Maybe alternatively the expected and result values should be compared with any \0 stripped out. Hopefully a maintainer will know 😬 I've made a PR #13149 for the latter because it feels lower risk, but if the right solution is to add escaping to paths found in the require.cache, I'm happy to do that instead :)

webpack version: 5.31.0

Node.js version: 14.16.0

Operating System: Mac OS X Catalina

Additional tools:

Issue 2:
webpack --json --profile reports a chunk more than once for a single entrypoint under "entrypoints".

"entrypoints": {
"site": {
"chunks": [
5,
1,
0,
null,
5,
4
],
...
}
}

My first impression was that these chunks are ordered and not repeating. What guarantees does an entrypoint have in this context?
Issue 1:
Sign in Error

I cannot log in or change the password

And all that I get is "oops something went wrong" 😢

Browser Information

*Chrome Latest

Windows 10 latest

Mobile, Desktop, or Tablet:

Your Code

Screenshot

Issue 2:
Challenge use-css-selectors-to-style-elements has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Firefox/52.0.

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

<style>
h2 {color: blue;}
</style>
<h2>CatPhotoApp</h2>
<main>
<p>Click here to view more <a href="#">cat photos</a>.</p>

<a href="#"><img src="https://bit.ly/fcc-relaxing-cat" alt="A cute orange cat lying on its back."></a>

<div>
<p>Things cats love:</p>
<ul>
<li>cat nip</li>
<li>laser pointers</li>
<li>lasagna</li>
</ul>
<p>Top 3 things cats hate:</p>
<ol>
<li>flea treatment</li>
<li>thunder</li>
<li>other cats</li>
</ol>
</div>

<form action="/submit-cat-photo">
<label><input type="radio" name="indoor-outdoor" checked> Indoor</label>
<label><input type="radio" name="indoor-outdoor"> Outdoor</label><br>
<label><input type="checkbox" name="personality" checked> Loving</label>
<label><input type="checkbox" name="personality"> Lazy</label>
<label><input type="checkbox" name="personality"> Energetic</label><br>
<input type="text" placeholder="cat photo URL" required>
<button type="submit">Submit</button>
</form>
</main>
Issue 1:
Hi,

I am having problems uploading my codepen Pomodoro Timer. The green submit button doesn't work. Then when I hit ctrl enter, the box opens and I'm able to paste my link but not submit. Frustrated cuz I worked very hard on this. please help.

Issue 2:
Hello,

I'm having difficulty submitting work for the "Simon" zipline. In fact, I'm unable to click on the "I've completed this challenge" and the "Bug" buttons. While the pop-up window comes up when I press ctrl+enter, I'm unable to submit the form.

Thing's I've tried:

Using 3 different browsers (Chrome, Firefox, Safari)

Doing a hard refresh

Clearing local storage

Thanks and please let me know if you need more info!

(sorry if this is a repost, but my first issue somehow got lost)
Issue 1:
Context:

Playwright Version: [what Playwright version do you use?]

Operating System: [e.g. Windows, Linux or Mac]

Node.js version: [e.g. 12.22, 14.6]

Browser: [e.g. All, Chromium, Firefox, WebKit]

Extra: [any specific details about your environment]

Code Snippet

Help us help you! Put down a short code snippet that illustrates your bug and

that we can run and debug locally. For example:

const {chromium, webkit, firefox} = require('playwright');

(async () => {
const browser = await chromium.launch();
const context = await browser.newContext();
const page = await context.newPage();

// Please include a snippet of HTML that shows an example of the content
// you are testing.
await page.setContent(`
<div>
…
</div>
`);
// Alternatively, if you are testing a public application, include the URL:
// await page.goto('https://example.com/')

await page.locator(…);
})();

Describe the bug

Add any other details about the problem here.

Executable doesn't exist at /home/.cache/ms-playwright/firefox-1319/firefox/firefox
╔═════════════════════════════════════════════════════════════════════════╗
║ Looks like Playwright Test or Playwright was just installed or updated. ║
║ Please run the following command to download new browsers: ║
║ ║
║ playwright install ║
║ ║
║ <3 Playwright Team ║

as doc said default folder for linux should be

~/.cache/ms-playwright on Linux

why /home/.cache/ms-playwright/firefox-1319/firefox/firefox

Issue 2:
Your question

i have tried all ways to install and config /playwright install to make my app work

Executable doesn't exist at /home/.cache/ms-playwright/chromium-978106/chrome-linux/chrome

- name: Install dependencies
run: |
pip install -r requirements.txt
playwright install
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.145]
Windows Terminal version (if applicable): Latest commit c3e32eb 2 hours ago

Any other software? VS2019 x64 Release

Steps to reproduce

Activate the drop down.

Move the terminal window.

Expected behavior

The dropdown should track the moving window.

Actual behavior

Sometimes the drop down does not move.

Sometimes the drop down moves to the new position in a jerky manner after some lag.

Issue 2:
Description of the new feature/enhancement

Create a Release Pipeline that pushes the release to the Github Release page. There is already a Build Pipeline so half of the battle is already done. Just need to copy it and adjust to go to master as the current one is for PR checking. Then once a week, the Release Pipeline would deploy to the Github Release page. An eventual todo is setup a deploy to the Microsoft Store in addition to the Github Release page.

A clear and concise description of what the problem is that the new feature would solve.

Automates the deployment of the app in addition to starting the set up of an update schedule.

A clear and concise description of what you want to happen.

I'd like to see releases more frequently from Github that require little administrative effort from the core team.
Issue 1:
Since the Line constructor takes the same Geometry as Mesh, it feels a bit of a waste that morph targets are not supported, and morphTargetInfluences not available. It would be very useful to move and morph lines without losing the original vertex positions.

Is this feature on the roadmap? Otherwise I'd like to ask for the recommended approach to achieve this. Thanks!

Issue 2:
Duplicate point checking in triangulateShape seems to be looking at x,y coords of vertices only. Is that how its supposed to work? I can't start with a Cube and re-triangulate from its vertices.

var cubeGeometry = new THREE.CubeGeometry(1,1,1);

var cubeHoles = [];

Cube vertices = [{"x":0.5,"y":0.5,"z":0.5},{"x":0.5,"y":0.5,"z":-0.5},{"x":0.5,"y":-0.5,"z":0.5},{"x":0.5,"y":-0.5,"z":-0.5},{"x":-0.5,"y":0.5,"z":-0.5},{"x":-0.5,"y":0.5,"z":0.5},{"x":-0.5,"y":-0.5,"z":-0.5},{"x":-0.5,"y":-0.5,"z":0.5}]

cubeTriangles = THREE.Shape.Utils.triangulateShape( cubeGeometry.vertices, cubeHoles );

Warning, unable to triangulate polygon! three.min.js:529

Duplicate point 0.5:0.5 three.min.js:561

Duplicate point 0.5:-0.5 three.min.js:561

Duplicate point -0.5:0.5 three.min.js:561

Duplicate point -0.5:-0.5
Issue 1:
ECMAScript has the concept of implementation defined global object, so that properties of the window object in a web page can be accessed globally. Implementing this can eliminate a bunch of duplicated declarations in the default lib and also make it easier to target other runtime environments.

Issue 2:
Suggestion moved over from codeplex

I was working with a rather large enum type with more than 50 items in it. Some of the item names are rather long. Given that TypeScript repeats each item string twice in the JavaScript implementation, the output starts to look rather ugly at some point.

I mean:

enum MyEnum {
SOME_BIG_UGLY_NAME_THAT_I_CANNOT_ABBREVIATE
}

compiles to:

var MyEnum;
(function (MyEnum) {
MyEnum[MyEnum["SOME_BIG_UGLY_NAME_THAT_I_CANNOT_ABBREVIATE"] = 0] = "SOME_BIG_UGLY_NAME_THAT_I_CANNOT_ABBREVIATE";
})(MyEnum || (MyEnum = {}));

I was thinking why not repeat the number part instead (to avoid bringing duplicate string literal):

var MyEnum;
(function (MyEnum) {
MyEnum[MyEnum[0] = "SOME_BIG_UGLY_NAME_THAT_I_CANNOT_ABBREVIATE"] = 0;
})(MyEnum || (MyEnum = {}));

and, for enums with many items not use an iterator? like:

var MyEnum;
(function (MyEnum) {
MyEnum["SOME_BIG_UGLY_NAME_THAT_I_CANNOT_ABBREVIATE"] = 0;
//...
//...
//...
})(MyEnum || (MyEnum = {}));
for (var key in MyEnum) {
MyEnum[MyEnum[key]] = key;
}

Thanks!
Issue 1:
I just downloaded the most current version of Firefox, it seems the ripple effect of buttons is not working.

Just browse to http://www.material-ui.com/#/components/raised-button with Firefox, you will see it. The behavior is similar on IE11.

On MS edge, the ripple effect works but not very smooth when the React component is updated.

Issue 2:
I am using Firefox 45 on Linux, and the demo app at http://www.material-ui.com/#/customization/themes (version 0.14.4) shows that the ripple effect works well for everything but the buttons.

That includes the Tab headers, which I suspect are buttons as well.

The problem is present with alphas for 0.15 as well
Issue 1:
In v1, I've set my MuiTheme like so

const theme = createMuiTheme({
typography: {
fontFamily: 'Montserrat',
fontSize: '5rem'
},
palette: {
primary: lightBlue,
secondary: amber
},
overrides: {
MuiAppBar: {
// Name of the styleSheet
root: {
// Name of the rule
boxShadow: 'none',
},
},
},
});

However, by default, all the text in buttons, AppBars, etc are black, whereas I'd like them to be white, in order to overlay the amber. How do I set the default "contrast color" to be white?

I've tried to set the contrastDefaultColor in the primary and secondary fields to "light", and I've tried making the type of the palette "dark," but neither worked. Please advise.

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

Expected Behavior

render options properly

Current Behavior

Cannot read property 'props' of null
TypeError: Cannot read property 'props' of null

Steps to Reproduce (for bugs)

const arr = ["2", "3", "4"];
const arr2 = undefined;
return (
<FormControl component="fieldset" required>
<FormLabel component="legend">Gender</FormLabel>
<RadioGroup
aria-label="gender"
name="gender"
value="2"
onChange={stub}
>
{arr2 && arr2.map(v => <FormControlLabel key={v} value={v} control={<Radio />} label={v} />)}
{arr && arr.map(v => <FormControlLabel key={v} value={v} control={<Radio />} label={v} />)}
</RadioGroup>
</FormControl>
)

Context

In our app we sometimes have the case that a radio get's options from multiple places and instead of pre merging them I tried to map over them one by one

source1 && source1.map(o => <option />)
source2 && source2.map(o => <option />)
<defaultOption />

I think this is somehow related to: #3627 (comment) , but I don't fully understand how this works - how is it even possible that {source1 && ...} generates a problem when source1 is undefined/false or empty?

Your Environment

Tech
Version

Material-UI
beta.9

React
15.6.1
Issue 1:
Documentation Link

No response

Problem

The first two paragraphs in the template matplotlibrc file are nearly duplicate of one another ("you can find a copy...") and should be deduplicated.

The :rc: role now renders the link as rcParam["name.of.rc"], but the correct name is rcParams, not rcParam.

At least the second issue would be good to fix in 3.6? But feel free to remilestone.

Suggested improvement

No response

Issue 2:
I would like to suggest adding a fourth option for the where kwarg of plt.step: where="auto". This would take x and y arguments which differ by 1 (in either way) in length, and make a step plot that either has horizontal segments at both ends (if len(x) == len(y) + 1) or has vertical segments at both ends (if len(y) == len(x) + 1).

As far as I know, currently, to make such a plot one must manually duplicate either the first or the last value in the shorter of the two arrays, which is a bit awkward. Additionally, "auto"-mode would make it much easier to rotate such a plot by 90° (in the "vertical" direction): you'd just have to switch the x and y arguments, without worrying about whether you need to change where or which element to duplicate.

Thoughts?
Issue 1:
Describe what you were doing when the bug occurred:

Start/Stop Profiling

Click "Ranked" tab

Please do not remove the text below this line

DevTools version: 4.2.1-3816ae7c3

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157108

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157054)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157577)

at vl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:314907)

at gi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59907)

at jl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:107381)

at Lc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92715)

at Pc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92640)

at wc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89544)

Component stack: in vl

in div

in div

in div

in wo

in Unknown

in n

in Unknown

in div

in div

in Li

in $e

in dn

in Ca

in Pc

Issue 2:
PLEASE INCLUDE REPRO INSTRUCTIONS AND EXAMPLE CODE

I got this error when I click 'Ranked'.

Please do not remove the text below this line

DevTools version: 4.0.4-3c6a219

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11441

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11387)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11920)

at _i (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56:277123)

at Ha (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:55890)

at Xl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:98280)

at Hl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:84255)

at Fl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:81285)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:25363

Component stack: in _i

in div

in div

in div

in Or

in Unknown

in n

in Unknown

in div

in div

in Ha

in le

in ve

in ko

in Ul
Issue 1:
Dealing with some annoying strings that I try to tame with .normalize() but it doesn't seem to work in deno (while it does in browsers), can you confirm that?

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/normalize

Issue 2:
As seen in #1952 / #1636 ICU needs to be added in Deno build.

Switching this flag to true maybe: https://github.com/denoland/deno/blob/master/.gn#L50 ?

ref: https://v8.dev/docs/i18n
Issue 1:
Bring up the command palette and search "Install". Results:

Find And Replace: Select All

Application: Install Update

Settings View: Uninstall Themes

Settings View: Uninstall Packages

Settings View: Install Packages and Themes

I'd say that we should mirror Sublime's technique, where:

We only match the action name (or we weight the name higher)

An exact word match (versus a partial match) should be weighted higher ("Install Packages" should be higher than "Uninstall Packages")

Built in packages should be weighted higher?

Application: Install Update should probably be intentionally weighted lower, as users will more often want to install packages I imagine

Issue 2:
When searching for commands in the palette, the order is usually baffling (see #2). Short of #18, which requires use in order to get tuned, I propose ordering the commands by how well they match the search term. Ideally if I type a word, if it exists, unbroken, and perhaps in it's entirety, I would expect to see those results above Find And Replace: Select All

I do like the idea of #18, but one can argue about the UX, a la the adaptive menus in Office 2000 wherein shuffling around commands should be done with care. This proposes to keep a fixed order for any given search term.
Issue 1:
fn main() {
println!(format!("{}",123));
}

When compiled, rustc will prints:

macro.c:12:11: 12:17 error: macro undefined: 'format'
macro.c:12 println!(format!("{}",123));
^~~~~~
macro.c:12:11: 12:17 error: macro undefined: 'format'
macro.c:12 println!(format!("{}",123));
^~~~~~
macro.c:12:11: 12:17 error: macro undefined: 'format'
macro.c:12 println!(format!("{}",123));
^~~~~~
macro.c:12:11: 12:17 error: macro undefined: 'format'
macro.c:12 println!(format!("{}",123));
^~~~~~
macro.c:12:11: 12:17 error: macro undefined: 'format'
macro.c:12 println!(format!("{}",123));
............

Issue 2:
Apologies if this has been reported before. A search didn't turn up anything but you know how GH's search is.

$ cat t.rs
fn main() { print!(format!("BAM")); }

$ rustc t.rs 2>&1 | head -20
t.rs:1:20: 1:26 error: macro undefined: 'format'
t.rs:1 fn main() { print!(format!("BAM")); }
^~~~~~
t.rs:1:20: 1:26 error: macro undefined: 'format'
t.rs:1 fn main() { print!(format!("BAM")); }
^~~~~~
t.rs:1:20: 1:26 error: macro undefined: 'format'
t.rs:1 fn main() { print!(format!("BAM")); }
^~~~~~
t.rs:1:20: 1:26 error: macro undefined: 'format'
t.rs:1 fn main() { print!(format!("BAM")); }
^~~~~~
t.rs:1:20: 1:26 error: macro undefined: 'format'
t.rs:1 fn main() { print!(format!("BAM")); }
^~~~~~
t.rs:1:20: 1:26 error: macro undefined: 'format'
t.rs:1 fn main() { print!(format!("BAM")); }
^~~~~~
t.rs:1:20: 1:26 error: macro undefined: 'format'
t.rs:1 fn main() { print!(format!("BAM")); }

Tested with today's x86_64 lucid nightly from https://launchpad.net/~hansjorg/+archive/rust
Issue 1:
Implement GrContextOptions::PersistentCache and provide it to Skia GrContextOptions.fPersistentCache. This allows Skia to cache shaders compilations to persistent storage. Even if platforms cache shader bytecode, Skia still has to do some non-trivial amount of work to generate the shader source in the first place. Using the persistent cache allows Skia to avoid repeating this work.

Issue 2:
On some apps, the first time you run a "big" animation (like a hero transition), there appears to be some jitter/jank. After the animation is warmed up, it appears to become smoother.

This is a tracking issue to investigate and solve.
Issue 1:
Bug report

What is the current behavior?

When importing a file that exports a simple object, attempting to use that import with optional chaining results in the operator being stripped.

A full reproduction can be found on the repo here: https://github.com/Cherry/webpack-optional-chaining-imports, but here's a quick example:

An imported.js and an index.js. imported.js looks like

export const foo = {
bar: {
baz: {},
},
};

index.js looks like this:

import {foo} from './imported.js';

console.log(foo?.bar?.baz?.thing?.unknown);

const bar = {
foo2: {
baz2: {}
}
};

console.log(bar?.foo2?.baz2?.thing?.unknown);

The resulting output is then as follows (removing the webpack bootstrap):

__webpack_require__.r(__webpack_exports__);
/* harmony import */ var _imported_js__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__(/*! ./imported.js */ "./src/imported.js");

console.log(_imported_js__WEBPACK_IMPORTED_MODULE_0__.foo.bar.baz.thing.unknown);

const bar = {
foo2: {
baz2: {}
}
};

console.log(bar?.foo2?.baz2?.thing?.unknown);

As you can see, the optional chaining for the initial import from imported.js is entirely stripped, which causes a TypeError when run. The optional chaining on the inline object remains intact.

What is the expected behavior?

The expected behaviour would be for the console.log(_imported_js__WEBPACK_IMPORTED_MODULE_0__.foo.bar.baz.thing.unknown); line to instead read console.log(_imported_js__WEBPACK_IMPORTED_MODULE_0__.foo?.bar?.baz?.thing?.unknown);

Other relevant information:

webpack version: 5.44.0

Node.js version: 14.7.3

Operating System: Windows 10 21H1

Issue 2:
Bug report

What is the current behavior?

Webpack incorrectly compiles x?.value to (something).value when x is something that's been imported.

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

webpack.config.js:

module.exports = {
entry: "./index.js",
target: "web",
};

index.js:

import x from './x.js';
console.log(`optional value is: ${x?.value}`);

x.js:

export default undefined;

Produces dist/main.js:

(()=>{"use strict";console.log(`optional value is: ${(void 0).value}`)})();

which leads to TypeError: Cannot read property 'value' of undefined at runtime.

What is the expected behavior?

The ? should be retained or converted to a ternary operator.

When import x from './x.js'; is removed and replaced with const x = (() => void console)(); (something complicated enough that webpack doesn't completely constant-fold it), the output is:

(()=>{const o=void console;console.log(`optional value is: ${o?.value}`)})();

which is as expected (the ? is retained).

Other relevant information:

webpack version: latest, 5.27.2

Node.js version: v15.9.0

Operating System: macOS 11.2.2