WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I added some input textboxes and buttons with a very long dropdonw menus.

Then I put them into a div that is in a narrow Collapse or Togglable tabs.

But the dropdown menus cannot display whole menus. The menus was cut off by the region of div.

How to let the dropdown menu display out of the parent div?

Because I want to use Collapse group (accordion-group) to make up our UI. So please don't suggest to use other components.

Any suggestions on how to handle this?

Issue 2:
I'm running the latest version of bootstrap (2.0.3) and there appears to be a clipping problem when I place a dropdown into tabbed content. I see that this was resolved in version 2.0.2 (#2079) where the overflow:hidden was changed to display: table.

.tab-content {

display: table; // prevent content from running below tabs

width: 100%;

}

Now, in 2.0.3 the scrolling and cut is back, is it possible because the navs.less reads:

.tab-content {

overflow: auto; // prevent content from running below tabs

}

At any rate, this problem appears to be back. I rolled back the tab-content to display: table and that seems to work for now.
Issue 1:
When tapping a image (i.e. hero) that is below the app bar, the hero animation immediately places it on top (this particular animation is not so bad). When pressing the back button, the moment when the app bar comes back on top is late an noticeable, making the animation look janky.

Issue 2:
Open Gallery, open pesto, scroll up enough to minimize the app bar. Tap a recipe.

Notice how the app bar immediately disappears, before the recipe begins its motion up. This is a jarring effect that the user could notice.

We could try something more subtle, like animating or fading the app bar away as the recipe opens?
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

WinOS

Expected Behavior

No response

Steps To Reproduce

In this environment...

With this config...

Run '...'

See error...

Environment

npm:

Node.js:

OS Name:

System Model Name:

npm config:

; copy and paste output from `npm config ls` here

Issue 2:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

OS name: WinOS

OS version: Microsoft Windows [Version 10.0.19044.2486]

node v18.6.0

npm v9.3.0

I ran into an ugly bug when trying to publish some packages over the weekend. With a horribly vague error message, it was quite a task to determine the actual problem. After much churn, here's the simple reproducible case I was able to generate:

package.json

{
"name": "@rivy-labs/-x-8ff8f63d-6ef9-44ee-999b-fc9edf489c98-basic",
"version": "2.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "require('fs').writeFileSync()"
},
"author": "Roy Ivy III <rivy.dev@gmail.com> (https://rivy.dev/)",
"license": "MIT"
}

npm publish fails with this vaguely horrifying message:

npm ERR! code E403
npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/@rivy-labs%2f-x-npm_***-basic
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.

Expected Behavior

npm publish succeeds.

Steps To Reproduce

Create a new package with npm init

npm publish will succeed (ie, https://www.npmjs.com/package/@rivy-labs/-x-8ff8f63d-6ef9-44ee-999b-fc9edf489c98-basic)

Change the "test" script text to "require('fs').writeFileSync()"

npm publish fails with E403...

Environment

OS Name: Windows
Issue 1:
The first time I build an app, flutter run just seems to hang after giving some obscure error message (something from FlutterDynamicsServiceLoader.mm). Eventually though (after I have up waiting) it completes and everything is fine.

We should make it faster.

We should also give progress while it's doing whatever it's doing so that you don't time out while waiting.

Steps:

flutter create testapp
cd testapp
flutter run

Issue 2:
Steps to Reproduce

On the iOS simulator...

flutter create new-project
cd new-project/
flutter run

Wait 1 minute and nothing has occurred. The app icon is not present on the simulator.

Flutter Doctor

[✓] Flutter (on Mac OS, channel master)
• Flutter at /Users/drewwarren/flutter
• Framework revision abeb5c7363 (10 minutes ago), engine revision fe509b0d96

[x] Android toolchain - develop for Android devices
x Android Studio / Android SDK not found. Download from https://developer.android.com/sdk/
(or visit https://flutter.io/setup/#android-setup for detailed instructions).

[✓] iOS toolchain - develop for iOS devices (Xcode 7.3.1)
• XCode at /Applications/Xcode.app/Contents/Developer
• Xcode 7.3.1, Build version 7D1014

[✓] Atom - a lightweight development environment for Flutter
• flutter plugin version 0.2.4
• dartlang plugin version 0.6.34

Logs and Crash Reports

new-project$ flutter run
Running lib/main.dart on iPhone 5s...

No additional output after a minute
Issue 1:
I'm trying to parametrize mlab tests (which cuts out many many lines of classes), but there are a few differences between similar tests which makes it really difficult to parametrize things (e.g., real vs. complex). Here are some differences:

Between real and complex:

len_x differs in:

nosig_defaultsided_trim (1024 vs 256)

NFFT_density differs in:

nosig_*_defaultsided_nopad_to (-1 vs None)

nosig_*_defaultsided_oddlen (33 vs 128)

nosig_*_defaultsided_trim (512 vs 128)

nosig_*_twosided_nopad_to (-1 vs None)

Between onesided and twosided:

NFFT_density differs in:

nosig_complex_*_nopad_to (-1 vs None)

Between onesided/twosided and defaultsided:

len_x differs in:

nosig_complex_*_trim (1024 vs 256)

NFFT_density differs in:

nosig_complex_*_nopad_to (-1 vs None)

nosig_complex_*_oddlen (33 vs 128)

nosig_complex_*_trim (512 vs 128)

Does anyone know why these differ in this way? @vollbier?

Can I replace some of the values by the others (and which by which?)

Issue 2:
Bug summary

THIS IS NOT A POST FOR COMMUNITY HELP.

THIS IS A BUG REPORT.

PLEASE DO NOT CLOSE BEFORE REPLICATION.

Code for reproduction

%matplotlib ipympl

import numpy as np
import matplotlib.pyplot as plt
import matplotlib.animation as animation
import time

fig, ax = plt.subplots()

XX=[1,2,3]
YY=[2,4,6]
line, = ax.plot(XX,YY)

ax.set_xlim(-2,100)
ax.set_ylim(-2,100)

num=0

def init():
line.set_ydata(YY)
line.set_xdata(XX)
return line,

def animate(i):
ii=0
while ii!=3:
XX[ii]+=1
ii+=1

'''for ii in XX:
ii+=1'''
line.set_ydata(YY)
line.set_xdata(XX)
return line,

ani = animation.FuncAnimation(
fig, animate,init_func=init,interval=50, blit=True, save_count=50) #interval is millisecond

plt.show()

Actual outcome

the pic do not move.

Expected outcome

the pic should move.

Additional information

use while instead of for can solve this problem.

Operating system

windows 10

Matplotlib Version

3.5.1

Matplotlib Backend

ipympl

Python version

3.8.1

Jupyter version

3.0.16

Installation

pip
Issue 1:
When using globs in ES6 template strings, VSCode's syntax highlighting thinks there is a unclosed comment. Example: ${settings.tests}**/*.js

Notice that after the /* all coloring is green, until the next start / end of a comment.

Issue found on https://github.com/elgervb/skeletonSPA

gulpfile.babel.js line 297, task scripts-tests

Issue 2:
Right now, those keywords like import class from are all plain white.
Issue 1:
A call to mapslices that takes a dims argument is type unstable. This is the case in all recent versions of Julia (1.1.1, 1.2.0, 1.3.1, 1.4.2).

For example:

d = rand(10)
mapslices(identity, d; dims=1)

Shows the following with @code_warntype:

Variables
#unused#::Core.Compiler.Const(getfield(Base, Symbol("#kw##mapslices"))(), false)
@_2::NamedTuple{(:dims,),Tuple{Int64}}
@_3::Core.Compiler.Const(mapslices, false)
f::Core.Compiler.Const(identity, false)
A::Array{Float64,1}
dims::Int64
@_7::Int64

Body::Any
1 ─ %1 = Base.haskey(@_2, :dims)::Core.Compiler.Const(true, false)
│ %1
│ (@_7 = Base.getindex(@_2, :dims))
└── goto #3
2 ─ Core.Compiler.Const(:(Core.UndefKeywordError(:dims)), false)
└── Core.Compiler.Const(:(@_7 = Core.throw(%5)), false)
3 ┄ (dims = @_7)
│ %8 = (:dims,)::Core.Compiler.Const((:dims,), false)
│ %9 = Core.apply_type(Core.NamedTuple, %8)::Core.Compiler.Const(NamedTuple{(:dims,),T} where T<:Tuple, false)
│ %10 = Base.structdiff(@_2, %9)::Core.Compiler.Const(NamedTuple(), false)
│ %11 = Base.pairs(%10)::Core.Compiler.Const(Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}(), false)
│ %12 = Base.isempty(%11)::Core.Compiler.Const(true, false)
│ %12
└── goto #5
4 ─ Core.Compiler.Const(:(Base.kwerr(@_2, @_3, f, A)), false)
5 ┄ %16 = Base.:(#mapslices#111)(dims, @_3, f, A)::Any
└── return %16

Due to this type instability, things like Statistics.median(d; dims=n) are also type unstable.

Issue 2:
Consider the following piece of code:

n=10^6;
X = randn(1,n);
V(x) = 0.5 * dot(x,x);
f(V, X) = [ V((@view X[:,n])) for n = 1:size(X,2) ]

Timing on this reveals:

julia> @time mapslices(V, X, 1);
1.177690 seconds (12.00 M allocations: 267.024 MiB, 6.91% gc time)
julia> @time f(V,X);
0.047745 seconds (1.00 M allocations: 53.406 MiB, 5.58% gc time)

which is substantially different.

Note that in this simple example, my data could be a column vector; however, this is a surrogate for problems where I have time series data and X is d x n with 1< d << n.
Issue 1:
I've just tried using the customised download facility to create me a Bootstrap v2.0 stylesheet by specifying only the colours I required to be different from the core Bootstrap definitions. However, this is how my app's coming out looking like when using the bundled bootstrap.min.css file:

Issue 2:
Hey guys,

I download the custom bootstrap from the site with all options, but in min.css don't have the body{} element...
Issue 1:
On the Dashboard example there is a typo in the dashboard.css under the "Main Content" section.

@media (min-width: 768px) {
.main {
padding-left: 40px;
pading-right: 40px; <---- Change to padding-right
}
}

Issue 2:
@@ File: examples/dashboard/dashboard.css

@@ Line: 69 // pading- => padding-

@media (min-width: 768px) {

.main {

padding-left: 40px;

pading-right: 40px;

padding-right: 40px;

}

}
Issue 1:
It would be great when I want to perform a Quick Open on a file that VSCode would search as I type. Atom and Sublime do this and it makes finding files so much easier.

Issue 2:
Ubuntu 12.04, vscode 0.10.1

I have found Go to file's indexing against a full Chromium workspace to be very slow. It took ~40 seconds to find "Tab.java" whereas a simple find command took less than a second:

$ time find . -name "Tab.java"
./chrome/android/java/src/org/chromium/chrome/browser/tab/Tab.java

real 0m0.559s
user 0m0.268s
sys 0m0.284s

Note that the workspace is on an SSD.
Issue 1:
Electron version:

0.37.5.

Operating system:

OSX 10.11.4

I'm using the X509 (https://www.npmjs.com/package/x509)

I followed the instructions here https://github.com/electron/electron/blob/master/docs/tutorial/using-native-node-modules.md to but the module is still crashing electron.

npm install --save-dev electron-rebuild

# Every time you run "npm install", run this
./node_modules/.bin/electron-rebuild

# On Windows if you have trouble, try:
.\node_modules\.bin\electron-rebuild.cmd

Issue 2:
Hello, my app uses the native ursa module. I just upgraded to atom-shell 0.23.0, rebuilt the ursa module and now my app is broken. Atom-Shell v0.22.3 was working properly.

Debian Linux x64, io.js@1.5.0, npm@2.7.1, node-gyp@1.0.3

Here's the error I get when I launch my application:

/usr/lib/node_modules/atom-shell/dist/atom .: symbol lookup error: /home/matt/noxious/node_modules/ursa/build/Release/ursaNative.node: undefined symbol: BN_new

You can see my build script for the ursa module here: https://github.com/mattcollier/noxious/blob/master/build_x64.sh

Here is the output of the build: http://hastebin.com/asalunuxop.vhdl

Of course, I have changed the target to 0.23.0.
Issue 1:
Upgrading packages...

Running "flutter packages upgrade" in flutter_update_packages_qQnlPY...

! analyzer 0.31.2-alpha.0 from path /Users/xxx/Documents/GitHub/flutter/packages/flutter_tools/../../bin/cache/dart-sdk/lib/analyzer

! front_end 0.1.0-alpha.10 from path /Users/xxx/Documents/GitHub/flutter/packages/flutter_tools/../../bin/cache/dart-sdk/lib/front_end

! kernel 0.3.0-alpha.10 from path /Users/xxx/Documents/GitHub/flutter/packages/flutter_tools/../../bin/cache/dart-sdk/lib/kernel

Running "flutter packages get" in bots... 0.6s

Running "flutter packages get" in vitool... 0.6s

Running "flutter packages get" in tools... 0.6s

Running "flutter packages get" in ui... 0.6s

Running "flutter packages get" in external_ui... 0.6s

Running "flutter packages get" in flavors... 0.6s

Running "flutter packages get" in platform_interaction... 0.6s

Running "flutter packages get" in channels... 0.6s

Running "flutter packages get" in manual_tests... 0.6s

Running "flutter packages get" in devicelab... 0.6s

Running "flutter packages get" in complex_layout... 0.7s

Running "flutter packages get" in microbenchmarks...

Package intl_translation has no versions that match 0.16.1 derived from:

microbenchmarks depends on version 0.16.1

pub get failed (1)

Issue 2:
flutter update-packages --force-upgrade fails because intl_translation package 0.16.1(latest) has upper bound on analyzer package

dependencies:
analyzer: '>=0.29.1 <0.31.0'

but analyzer that comes into flutter with sdk is 0.31.2-alpha.0
Issue 1:
Hi.Is it possible to add a new light after the scene setup?I have a scene and i want the user to add light in a selected position by pressing a button.I have tried it and it's not working.

Issue 2:
HI,

I'm having some difficulty while trying to add a light after some time to the scene. If the light is created in the init() function there is no issue, but as soon as you create it later it makes everything look black.

Here is a sample script showing this issue: http://jsfiddle.net/GKCx6/1/

there is a variable "dynamic_light" that you can set to false to show a working version (light created in init). If dynamic_light is set to true you will have to click "add light" to see the issue.

I hope i'm not missing something obvious.
Issue 1:
[X ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behaviour

No error in ESLint

Alternatively: Clicking the icon -> expands the card

handleExpandChange = (expanded) => {

^

this.setState({expanded: expanded});

};

Error: Unexpected Token, fatal error (on the word expanded)

Current Behaviour

ES Lint provides fatal error.

Steps to Reproduce (for bugs)

https://codesandbox.io/s/z3y0624rr3

Take the above sandbox

Put it in Atom 1.22.1 with Linter-eslint 8.4.1

Get error

However, the code works.

Context

I managed to fix the esLinter error by using the commented out code in the sandbox.

However: this creates a different bug: The icon is prevented from being able to expand the code. The Card Header is still able to expand the code. Uncomment the code to reproduce (and comment out handleExpandChange)

Your Environment

Tech
Version

Material-UI
0.20.0"

React
16.2

browser
64.0.3282.167

etc
Atom 1.22.1 with Linter-eslint 8.4.1

Thanks

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

Expected Behavior

I was expecting that body2 type in Typography will use same element as body1 which is a p element for body1.

Current Behavior

<Typography type="body1"> Lorem ipsum </Typography> // this uses a `p` element
<Typography type="body2"> Lorem ipsum </Typography> // this uses an `aside` element

As a result, the nowrap attribute doesn't work on body2 types.

<Typography type="body2" nowrap> {bigString} </Typography> // Does not work

Following also does not work:

<Typography type="body2" component="p" nowrap> {bigString} </Typography>

Steps to Reproduce (for bugs)

Add a typography component

Add property nowrap to the compnent

Set the type property of the component to body2

Context

Your Environment

Tech
Version

Material-UI
1.0 beta 29

React

browser

etc
Issue 1:
Problem description

When I use onMouseEnter and onMouseLeave to show a popup (tooltip behavior), the popup does not appear.

Link to minimal working code that reproduces the issue

https://codesandbox.io/s/wpjvm86AM

Versions

Material-UI: 0.18.2

React: 15.5.3

Browser: N/A

I suspect the issue is that when the popup is open it adds an overlay to the screen, so that the button is no longer on top, resulting in immediate onMouseLeave.

Is there a way to overcome this? I thought that maybe setting a different zIndex to the popup might fix this, but I'm not sure.

Issue 2:
Hi there,

According to your description of AppBar: "App bars are a collection of components placed as a static header for an application", I was thinking that the AppBar wouldn't scroll off the page when you put a long list below it, let's say. But it does. See this example if you'd like: http://www.donwoodlock.com/TextDon/index.html

Is there a property I should set to keep it fixed on top? Or a particular wrapper I should use for everything else to create a designated scrolling area?

Please advise. Thx.

Don
Issue 1:
Code:

fn foo(v: &[int]) {
match v {
[_] => {},
[_, ..] => {},
_ => {},
}
}

Wrong error is:

/home/vagrant/tmp2.rs:4:9: 4:16 error: unreachable pattern
/home/vagrant/tmp2.rs:4 [_, ..] => {},
^~~~~~~
error: aborting due to previous error

Issue 2:
Until friday (commit 3047614) the following (very contrived) code compiled:

fn main() {
println!("{}", count_members(&[1, 2, 3, 4]));
}

fn count_members(v: &[uint]) -> uint {
match v {
[] => 0,
[_] => 1,
[_x, ..xs] => 1 + count_members(xs)
}
}

With ca3e557, it fails with:

array_match.rs:9:5: 9:15 error: unreachable pattern
array_match.rs:9 [_x, ..xs] => 1 + count_members(xs)
^~~~~~~~~~
error: aborting due to previous error

I'll try to bisect and get to a single commit
Issue 1:
Do you want to request a feature or report a bug?

bug

What is the current behavior?

My application consists of two parts. The main web application and a module which gets dynamically loaded into the web application.

Both web application and the module uses React 16.9.0.

The module is loaded into the web application using React.lazy() and dynamic import() statement.

When the module is loaded the application crashes with the following message in the console.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

To reproduce the issue, we require an application and 2 modules each having their own build.

Therefore a demo couldn't be created in codesandbox. I've attached a demo which can be used to reproduce the issue.

lazy-loading.zip

Download the attached demo app.

Navigate to "\app\modules\module1" and "\app\modules\module1" folders and run "npm install" and "npm build" to build the modules.

Navigate to "\app" folder and run "npm install" and "npm start" to run the main app.

Open the dev tools and Browse to http://localhost:3000.

Application will try to load the module which uses react hooks and crashes. The error message in the above screenshot will be displayed in the console.

In app.jsx comment the line < LazyModule1 /> and un-comment the line < LazyModule2 />. Now the application will try to load the module which does not use react hooks.

The app will now load successfully.

What is the expected behavior?

When both the app and the dynamically imported module is using the latest version of react the app should load without crashing.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

React - v16.9.0

Browser - Chrome

OS - Windows 10

Issue 2:
To people coming from search: please read this page first. It contains most common possible fixes!

Do you want to request a feature or report a bug?

Enhancement

What is the current behavior?

I had multiple instances of React by mistake.

When trying to use hooks, got this error:

hooks can only be called inside the body of a function component

Which is not correct since I was using function components. Took me a while to find the real cause of the issue.

What is the expected behavior?

Show the correct error message. Maybe detect that the app has multiple instances of React and say that it may be the reason of bugs.
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-make-images-mobile-responsive` has an issue. Once completed, clicking Go to my next challenge takes you to http://www.freecodecamp.com/challenges/waypoint-manipulate-arrays-with-push rather than the next challenge.

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-sift-through-text-with-regular-expressions has an issue.

We have this regular expression:

/the+/gi;

And that's how it's explained:

Let's break this down a bit:

the is the pattern we want to match.

+ means we want to find one or more occurrences of this pattern.

But it's incorrect. + in this expression is really says that we want to match one or more e after th.

Also, i think there is mistype in this challenge title - there should be Shift word instead of Sift.
Issue 1:
Add Flutter to existing apps explains how to use FlutterViewController (in Swift/Objective-C) or Flutter.createView (in Kotlin/Java) to create a Flutter view from an existing native app codebase. When creating a new view/screen, rarely is the user's activity from that screen going to be completely isolated from the rest of the app. Normally I would want to pass data to that screen via something like dependency injection, and then receive the results as data back in the native app codebase.

In Swift, when creating a new screen, I would normally provide it with the data it needs by passing an object into the initializer of a UIViewController subclass. FlutterViewController takes no arguments to replicate that pattern. To receive data back, I would set a delegate on the UIViewController subclass. The delegate would have one of its methods called when the screen is ready to be dismissed, and the results from that screen would be passed as arguments into the delegate method. The delegate would then be responsible for dismissing the screen.

From what I've found online, the only way to pass data between Flutter and a native codebase is by writing custom platform-specific code. So for my Flutter screen to receive data and send it back upon dismissal, I would have to manage separate asynchronous calls between Swift/Kotlin and Dart before the Flutter view is created, and before it is dismissed. This seems relatively cumbersome. Is there a better way?

Issue 2:
[This is very similar to http://github.com//issues/15798]

I wanted to open a new issue for this because the issue above is quite generic. Our clients have been complaining that ability to only send strings down is too limiting from API point of view. They would love to have initialRoute (or some similar mechanism) to support protocol buffers.