WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

When running NODE_ENV=staging next build I expect the .next folder to be generated with "staging" as process.env.NODE_ENV but I get "production" instead.

Steps to Reproduce (for bugs)

Run NODE_ENV=staging next build

Your Environment

Tech
Version

next
5.0.1-canary.14

node
6.10

Issue 2:
Feature request

Is your feature request related to a problem? Please describe.

There are many different methods of codebase organization in the wild and one popular one is to use an index.js file for the page component itself and surround it with sibling files for various subviews that are specific to that page.

However, next doesn't support this kind of structure because it automatically assumes all files inside of pages/ are real pages.

Describe the solution you'd like

There already is precedent in the codebase for convention over configuration when it comes to filenaming:

the [id].js pattern for dynamic routing

the _(app|document|error).js pattern for overriding built-in pages

I propose extending the leading-underscore naming pattern such that any file inside pages/ prefixed with an underscore will not be considered as a public page and can simply live in the folder.

pages/
index.js <- page
accounts/
index.js <- page
_constants.js <- not a page
_modal.js <- not a page

Describe alternatives you've considered

Another prefix I thought of was "$", e.g. $constants.js but this felt a little strange to write and actually is not supported in some filesystems.
Issue 1:
Hello,

It seems this line is duplicated, just one after the other.

Both in min and full 3.02 version.

.container:before,.container:after{display:table;content:" "}.container:after{clear:both}

.container:before,.container:after{display:table;content:" "}.container:after{clear:both}

Sincerely,

Issue 2:
show on bootstrap.css

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L581

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L723

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L743

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2023

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2433

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2617

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2637

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3032

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3296

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3453
Issue 1:
The message valid_resources should instead be a list of "primary resources", their shortcuts, and an optional description returned by the Factory (and probably generated by the same code that is used to resolve resource names, so as not to duplicate it). Or it should be generated by p.HandledResources (although that doesn't have shortcut info).

Ideal structure:

get invokes p.HandledResources and iterates

it retrieves shortcut (if any) from the RESTMapper or factory

it retrieves a short description from the description we generate for swagger (first sentence?)

As is, it is easy for someone to miss.

Issue 2:
Continued from #1518 and #3024, and also relates to #1624.

Since there will necessarily be a higher barrier to entry for new objects, we should make replication controller composable (e.g., with auto-scalers and deployment managers), pluggable, hookable (#2804), to delegate decisions like which pod to kill to decrease the replica count, when pods should be killed and replaced (esp. moving to new nodes), when the whole collection should terminate (for RestartPolicyOnFailure), etc.

For jobs that terminate (RestartPolicyOnFailure), I'd make the count auto-decrement on success. I'm tempted to say we should support terminating jobs of the per-node variety, but then we'd have to keep track on which nodes the pods had executed, which seems ugly.

It should support graceful termination (#1535), but I've removed that from this sketch, since it's not specific to replication controller.

Stab at a definition, also using my latest proposed name change:

type OverseerSpec struct {
ReplicationPolicy *ReplicationPolicy `json:"replicationPolicy,omitempty"`
Selector map[string]string `json:"selector,omitempty"`
TemplateRef *ObjectReference `json:"templateRef,omitempty"`
Template *PodTemplateSpec `json:"template,omitempty"`
}
type ReplicationPolicy struct {
Count *ReplicationPolicyCount `json:"count,omitempty"`
PerNode *ReplicationPolicyPerNode `json:"perNode,omitempty"`
}
type ReplicationPolicyCount struct {
Count int `json:"count"`
}
type ReplicationPolicyPerNode struct {
}

Forgiveness example was moved to #1574.

Additional example policies have been removed.

/cc @smarterclayton @thockin @brendandburns @erictune @lavalamp
Issue 1:
Repro:

Repro'd on 22dd214678739e71bf51fcba7697e98f33ce191d for me. This only repros in C++ mode - C mode correctly ends the string literal in the right place.

Issue 2:
VSCode Version: 0.10.11

OS Version: Windows 7

Issue 1:

In the following code (using C++ syntax highlighting), the string literal(s) are not highlighted at all.

This issue is exclusive to C++ syntax highlighting and does not occur with C syntax highlighting.

Code:

int main()
{
printf("%s\n", "a string");
}

Result

Issue 2:

In custom tmLanguage based colorizers that reference source.c from within rules that begin with certain patterns, the inlined C highlighting is incorrect (this issue also applies to rules using source.c++ but does not occur in rules using source.js).

Code

(See https://github.com/SE2Dev/VSCode-BugExample)

Result
Issue 1:
Bug summary

Based on this code below, the line is exactly on top of the surface plot but by rotating along the z-axis, it's obvious that the perspective of the line with respect to the surface changes, as it should not.

Code for reproduction

from mpl_toolkits.mplot3d import Axes3D
import matplotlib.pyplot as plt
import numpy as np
import math
pi = math.pi

x, y = np.meshgrid( np.linspace(-3, 7, 100) , np.linspace(-3, 7, 100))

V = np.linspace(-4, 4, 100)
U = np.linspace(-4, 4, 100)

U, V = np.meshgrid(U, V)
X = U**2
Y = V**2

Z = U + 2*V

fig = plt.figure('1', figsize=(8,7))
ax = fig.add_subplot(111, projection='3d')
ax.plot_surface(X, Y, Z, cmap = plt.cm.coolwarm)

k=10
ax.plot(np.linspace(-2-k, 1+k, 10), np.linspace(-4-k, 1+k, 10), np.linspace(3-k, 4+k, 10), 'k' )

ax.set_xlabel('x')
ax.set_ylabel('y')
ax.set_zlabel('z')
plt.tight_layout()

Actual outcome

The line seems to be plotted below the surface for some azimuthal angles.

Expected outcome

The line should always be seen on top of the surface.

Additional information

No response

Operating system

Windows 10

Matplotlib Version

3.2.2

Matplotlib Backend

Qt5Agg

Python version

No response

Jupyter version

No response

Installation

conda

Issue 2:
Bug report

Bug summary

When using the voxels rendering for Axes3D, surfaces and lines are not stacked correctly in the visual perspective of the axes.

Code for reproduction

Adding the following lines to the example from matplotlib's example https://matplotlib.org/gallery/mplot3d/voxels.html produces the glitch:

(xx, yy) = np.meshgrid(x, x, indexing='ij')
zz = np.ones_like(xx) * 4
ax.plot_surface(xx, yy, zz)

or

ax.plot_wireframe(xx, yy, zz)

before the line

plt.show()

Actual outcome

Expected outcome

The plane should be rendered below the green voxels and some of the red voxels.

When rotating, some of the voxels become visible.

Matplotlib version

Using matplotlib from a miniconda distribution:

Operating system: linux64

Matplotlib version: 3.0.2

Matplotlib backend : Qt5Agg

Python version: 3.6

Thank you in advance!

Cheers,

Nicola
Issue 1:
Challenge http://freecodecamp.com/challenges/waypoint-generate-random-whole-numbers-with-javascript has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Section "Waypoint: Generate Random Whole Numbers with JavaScript"

Just a typo , the word "lot"

but it's even more useful if we "lot" more useful to generate a random whole number.

Issue 2:
Challenge http://freecodecamp.com/challenges/waypoint-generate-random-whole-numbers-with-javascript has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

I believe there is a typo in the first paragraph of the tutorial:

"It's great that we can create random decimal numbers, but it's even more useful if we lot more useful to generate a random whole number."
Issue 1:
I'm submitting a ... (check one with "x")

[ x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Return key event was not fired when the following criteria were met (all): 1. bluetooth input device 2. iOS, 3. Angular 2

Expected behavior

Return key event was fired

Reproduction of the problem

Connect your iPhone or iPad with a bluetooth keyboard

On your iOS device, iPhone or iPad, open your favourite browser.

Visit the TODO MVC for angular 2, http://todomvc.com/examples/angular2/

or the contact list app on Made with Angular 2: https://embed.plnkr.co/ns1tfi/

Type something on bluetooth connected physical keyboard and hit Enter key.

Nothing happened.

What is the motivation / use case for changing the behavior?

My app was built using Angular 2, and targeted to all device, including iOS environment.

Please tell us about your environment:

Angular version: 2.0.0-rc.6

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

All

Language: [all | TypeScript X.X | ES6/7 | ES5]

all

Node (for AoT issues): node --version =

Issue 2:
Current behavior

When you bind (keyup.enter) to an element it doesn't trigger in IE10.

Other information

I tried to create a plnkr from the issues' one and it doesn't run in IE10.

http://plnkr.co/edit/YhxMmgqL9YKcFF2Qm035?p=preview
Issue 1:
VSCode Version:1.8.2

OS Version:ubuntu 15.10

Steps to Reproduce:

i can create multi cursors by alt-shift+(down/up) but not all the time where i wanna place cursor is exactly under the line in sublime i can press and hold ctrl and click to add cursor to any location but seems theres no way to do this in vscode . is there a way to to this without hacking ctrl-d combination by adding prefix?

Issue 2:
VSCode Version: 1.2.0-insider

Commit 24e811a

Date 2016-06-07T07:55:32.262Z

Shell 0.37.6

Renderer 49.0.2623.75

Node 5.10.0

OS Version: Windows 10

Steps to Reproduce:
Issue 1:
I'm trying to use the new (introduced in r70 with d433472) THREE.BufferGeometry.prototype.merge() functionality on buffer geometries created with THREE.PlaneBufferGeometry but I'm getting this error during the subsequent render call (the merging itself does not throw an error):

Uncaught TypeError: Cannot read property 'array' of undefined (in Chrome) or

TypeError: this.attributes.position is undefined (in Firefox)

at this line in THREE.BufferGeometry.prototype.computeBoundingSphere():

I was able to reduce the test case to a simple scene where I try to merge all 6 faces of a cube into a single THREE.BufferGeometry. Here is a jsfiddle of how it should look using normal non buffer geometries http://jsfiddle.net/3vwj3rj1/ and here is the jsfiddle for the same scene using buffer geometries throwing the error: http://jsfiddle.net/3vwj3rj1/1/ .

Using the Java Script debugger it looks like that THREE.BufferGeometry.prototype.merge() does not have copied the attributes at all.

I opened this stackoverflow question about the same issue

Edit: I think I somehow understand the problem now: THREE.BufferGeometry.prototype.merge() doesn't take care of resizing the buffer attributes at all and I should do something like this http://jsfiddle.net/3vwj3rj1/3/ , but I still have no idea what to do with the index attribute.

Issue 2:
Was there a significant change in the GLTFLoader in version 90? We're having problems with gltf/glb files that we export from Paraview, the colors are not visible in our viewer. If changing the version to version 89, the colors are visible. Here is an example file:

005.zip
Issue 1:
such as

file: '/node_modules/material-ui/BottomNavigation/BottomNavigationButton.js.flow'
severity: 'Error'
message: 'React element `Icon` (This type is incompatible with empty See also: React element `Icon`)'
at: '145,16'
source: 'flow'

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

Expected Behavior

No errors.

Current Behavior

Config the flow config with create-react-app settings. it seems to work with previous version.

Steps to Reproduce (for bugs)

create-react-app

eject

flow-init

copy paste .flowconfig

if use the MUI component to nested in, say, a div

<div>
<Button>test</Button>
</div>

then run flow

error comes out

Context

Your Environment

Tech
Version

Material-UI
^1.0.0-beta.19

React
^16.0.0

browser

flow-bin
0.58.0

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

Expected Behavior

I have set a callback function for the onItemClick property of Menu. I expect the call back function to be executed for all nested levels of menu items upon clicking that item

Current Behavior

As of now only the first level of menu items work as expected. The nested menu items below the first level do not invoke the call back function

Steps to Reproduce (for bugs)

My render function code is as described below

render() {

if (this.state.redirect) {
return <Redirect push to={{ pathname: this.state.redirectPath }}	/>
}

return(
<MuiThemeProvider>
<div style={styles.megaMenuContainerStyle} >
<Menu
desktop={true}
width={100}
onItemClick={this.menuItemClicked}
>
<MenuItem primaryText="Map View" insetChildren={true} />
<MenuItem
primaryText="Chart View"
insetChildren={true}
rightIcon={<ArrowDropRight />}
menuItems={[
<MenuItem primaryText="Time Series Chart View" />,
<MenuItem primaryText="Scatter Chart View" />,
<MenuItem primaryText="Calendar Chart View" insetChildren={true} />
]}
/>
<MenuItem primaryText="Table View" insetChildren={true} />
<MenuItem primaryText="Schematic View" insetChildren={true} />
</Menu>
</div>
</MuiThemeProvider>
)
}

Your Environment

Tech
Version

Material-UI
0.20

React
16.0

browser Chrome
63.0.3239.84
Issue 1:
Website or app

https://angular.io/start

Repro steps

Go to https://angular.io/start or https://vuejs.org/

Click on React Dev Tools extension

You should see message This page is using the production build of React. ✅

How often does this bug happen?

Every time

DevTools package (automated)

No response

DevTools version (automated)

No response

Error message (automated)

No response

Error call stack (automated)

No response

Error component stack (automated)

No response

GitHub query string (automated)

No response

Issue 2:
Website or app

youtube.com, github.com, gmail.com, lucidchart.app

Repro steps

Open any web app not made with React (e.g.: youtube.com, amazon.com, github.com, gmail.com, lucidchart.app)

The react icon is ON and the popover message says:

'This page is using the production build of React. ✅'

How often does this bug happen?

Every time

DevTools package (automated)

No response

DevTools version (automated)

No response

Error message (automated)

No response

Error call stack (automated)

No response

Error component stack (automated)

No response

GitHub query string (automated)

No response
Issue 1:
Javascript editor duplicate characters

How to reproduce the bug

Go to new chart with deck.gl Screen Grid

Enable ENABLE_JAVASCRIPT_CONTROLS and start input characters into window

Input "1234"

See error

Expected characters in this window "1234", actual characters "1234123121"

Expected results

1234

Actual results

1234123121

Screenshots

Environment

browser type and version: Chrome Version 97.0.4692.71 (Official Build) (x86_64)

superset version: 1.4.0

python version: Python 3.8.10

node.js version: v10.19.0

DISTRIB_ID=Ubuntu

DISTRIB_RELEASE=20.04

Checklist

Make sure to follow these steps before submitting your issue - thank you!

[V] I have checked the superset logs for python stacktraces and included it here as text if there are any.

[V] I have reproduced the issue with at least the latest released version of superset.

[V] I have checked the issue tracker for the same issue and I haven't found one similar.

Issue 2:
Is your feature request related to a problem? Please describe.

It's difficult to find specific charts and dashboards that I've created.

Describe the solution you'd like

As a user, I would like to be able to logically group my charts and my dashboards. I would like either folders or to be able to filter by tags when accessing the list of charts and dashboards.

Additional context

This is a much requested feature with many closed issues:

Allow users to tag dashboards from November, 2017

Folder structure for dashboard and slice from December, 2017

Organising Charts List from April, 2019

Group Dashboards folders or tags from April, 2019

Ability to Tag Charts for Easy Filtering

There's even a PR but it appears that it may need to be rewritten to be accepted:

Tagging frontend
Issue 1:
Currently to get the size of a widget you need to do this:

Size get _size {
assert(mounted);
RenderBox box = context.findRenderObject();
assert(box != null);
assert(box.hasSize);
return box.size;
}

It'd be nice to have this as a built in api.

((I'm copying this code all over the place.))

Similarly getting the size of the widget via GlobalKey would be good too. Maybe something can be added to GlobalKey?

Issue 2:
In the tabs section of the gallery, the beach ball can get in a state where it sits slightly under the header. The resting state should be sitting fully underneath the header.

Steps to Reproduce

Build and install latest Flutter Gallery from the repo, enter "Tabs" section,

scroll "Left" section to the bottom,

select to "Right" tab,

Notice that the beach ball is scrolled under the header a little bit, and will sit there.

Flutter Doctor

[✓] Flutter (on Mac OS X 10.12.4 16E195, locale en-US, channel master)

• Flutter at /Users/KG/Developer/Flutter/flutter

• Framework revision 37e32d5 (21 hours ago), 2017-06-12 12:23:13 -0700

• Engine revision ffe8181

• Tools Dart version 1.24.0-dev.6.7

[✓] Android toolchain - develop for Android devices (Android SDK 25.0.3)

• Android SDK at /Users/KG/Library/Android/sdk

• Platform android-25, build-tools 25.0.3

• ANDROID_HOME = /Users/KG/Library/Android/sdk

• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java

• Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] iOS toolchain - develop for iOS devices (Xcode 8.3.3)

• Xcode at /Applications/Xcode.app/Contents/Developer

• Xcode 8.3.3, Build version 8E3004b

• ios-deploy 1.9.1

• CocoaPods version 1.2.1

[✓] Android Studio (version 2.3)

• Android Studio at /Applications/Android Studio.app/Contents

• Gradle version 3.2

• Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] IntelliJ IDEA Community Edition (version 2017.1.4)

• Flutter plugin version 14.0

• Dart plugin version 171.4694.29
Issue 1:
I have seen similar bug reports, apologies if this is a duplicate. In my case, when I am using a collection field as follows:

$builder->add('goods', 'collection', array(
'type' => new GoodType(),
'allow_add' => true,
'allow_delete' => true,
'prototype' => true,
'by_reference' => false
));

And a callback validator

constraints:
- Callback:
methods: [checkGoods]

/**
* Callback validator for Goods
* @param ExecutionContext $context
*/
public function checkGoods(\Symfony\Component\Validator\ExecutionContext $context) {
if (! is_null($this->goods) && $this->goods->count() == 0) {
$propertyPath = $context->getPropertyPath() . '.goods';
$context->setPropertyPath($propertyPath);
$context->addViolation('Please provide at least one good', array(), null);
}
}

I see the "Please provide at least one good" at the root of the form, where

{{ form_errors(form) }}

is called, but I expect it to be output with the field itself, presumably in the div that contains the data-prototype definition.

Issue 2:
Hello,

I'm having a problem with collection field type. If I set error_bubbling to false in order to display errors next to collection field label I will get these errors output twice. Seems that errors get written in form_row and then in form_widget:

{% block collection_widget %}
{% spaceless %}
{% if prototype is defined %}
{% set attr = attr|merge({'data-prototype': form_row(prototype) }) %}
{% endif %}
{{ block('form_widget') }}
{% endspaceless %}

The following fix worked for me

{% block collection_row %}
{{ form_label(form) }}
{{ form_widget(form) }}
{% endblock %}

BTW why render forms with form_widget instead of form_row? The problem was generally caused by this and at first glance the form_row approach seems more consistent (in regard field types).
Issue 1:
What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?

Similar errors identified as name conflicts between module and directory

Environment info

Operating System: macOS Sierra

If installed from binary pip package, provide:

A link to the pip package you installed:

current osx nightly

The output from python -c "import tensorflow; print(tensorflow.__version__)".

0.11.0rc0

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)

In terminal window run 'tensorboard'

Output:

File "/tensorflow/lib/python2.7/site-packages/tensorflow/tensorboard/tensorboard.py", line 43, in main

logdir = os.path.expanduser(FLAGS.logdir)

AttributeError: 'NoneType' object has no attribute 'logdir'

What other attempted solutions have you tried?

A workaround is to rename tensorboard.py (I used tensorboard1.py) and execute with full path to that file.

Originally I printed __name__ and learned it was 'tensorflow.tensorboard.tensorboard'.

Issue 2:
Running tensorboard results in this:

logdir = os.path.expanduser(FLAGS.logdir)
AttributeError: 'NoneType' object has no attribute 'logdir'

Best practice in this case is arg(opt)parse.