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

According to the docs a page is cached for 25sec in development by default. However, when you change something on the API-side or even in the JSX of a page, the page will update (both by HMR and when calling manually using F5).

So I'm curious, what exactly is cached here, what exactly do you specify with maxInactiveAge?

Your Environment

Tech
Version

next
5.0.0

node
9.5.0

OS
Win10

Issue 2:
Feature request

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

I want to match **/[foo].tsx when I access / with **/[foo].tsx but no **/index.tsx. But now, it redirects to 404 page.

I'd like to use SSR at first, but once reaching the browser, I'd like to use shallow transition.

The following situations are possible on the UI:

Home | About | Blog
^^^^
↑
This route is "/" or "/home".

I want "Home" to be displayed on both "/" and "/home".

Describe the solution you'd like

If **/[foo].tsx exists and **/index.tsx does not exist, when we access /, matching **/[foo].tsx.

Describe alternatives you've considered

I considered following solutions.

Creating index.tsx

foo
|-[bar].tsx
|-index.tsx

However, this method causes SSR twice, for example, transitioning from / to /about.

Using server (302) redirect.

But, this method makes / route unusable.
Issue 1:
If you reload a page, an isolated route will work, but route params will not.

Related to:

#2920

http://stackoverflow.com/questions/32429089/how-do-i-support-routeparams-on-page-reload-using-angular-2-dart?noredirect=1#comment52795245_32429089

FTA:

Im using the Router and RouteParams in Angular 2 Dart.

My routes are as follow:

@RouteConfig(const [
const Route(path: '/', component: ViewLanding, as: 'home'),
const Route(path: '/landing', component: ViewLanding, as: 'landing'),
const Route(path: '/flights', component: ViewFlights, as: 'flights'),
const Route(path: '/picker/:cityDepart/:cityArrival/:dateDepart/:dateArrival/', component: ViewFlights, as: 'picker'),
const Route(path: '/order/:id/:level/:dateDepart/:dateArrival/', component: ViewOrder, as: 'order'),
const Route(path: '/order/complete', component: ViewComplete, as: 'orderComplete')
])

// Application Entry Point

void main() {
print('-- Main.dart 2 --');
bootstrap(Tickets, [
routerInjectables,
client_classes,
// The base path of your application
bind(APP_BASE_HREF).toValue('/'),
// uncomment this if you want to use '#' in your url
bind(LocationStrategy).toClass(HashLocationStrategy)
]);
}

This works fine with router-outlet / router-link / router.navigate

However, on page reload - i don't get a positive match for routes with params. IE: if i refresh http://localhost:8080/#/picker/SAN/SFO/2015-01-01/2015-04-02 - i goto the parent view with no child routes. This symptom is true for any route with params.

Navigating directly to or refreshing to: http://localhost:8080/#/flights/ - works as expected - the ViewFlights component is instantiated

Symptoms:

routing with params fails.

Question:

How do i define route configurations to work with parameters on refresh

Links:

https://github.com/rightisleft/web_apps_dart/blob/angular2/web/main.dart

https://github.com/rightisleft/web_apps_dart/blob/angular2/lib/client/tickets.dart

Issue 2:
When user visits URL like the http://example.com/path/part?queryParam=value, there is no access to the "queryParam" via RouteParams in the component that is configured to match the "/path/part" route.

When the RootRouter class calls to the navigate method in its constructor, it passes in as a parameter only the path part of a URL discarding all query string parameters.
Issue 1:
I made tests a bit too verbose in #11616.

Might be a good time to revisit how we write them now.

There's a few separate issues:

Asserting on warning messages is too verbose. Need a DEV block, call spyOnDev, normalize stack, etc. Ideally I wish there was a higher level helper that lets us "push" expected warning assertions and validate them as they happen. It should handle component stacks automatically without having to copy-paste the normalization helper everywhere.

In some cases I added actual duplication in #11616, in particular for cases that throw in development but don't throw in production. Maybe need a toThrowInDev()? Although on the other hand this pattern needs to be highly visible so maybe extracting common code in a closure is good enough.

Issue 2:
Conditional Rendering Components JSX-Control-Statement produces incorrect coverage in if / else branches. We are using it in our project and we want official Facebook's opinion about these as whether it will be updated with babel's AST for future support. If not please warn the developers that they will get incorrect branch coverage. See the reported issue below.

istanbuljs/nyc#812

Will facebook support any approach similar to JSX-Control-Statements in the future?

If facebook does not support any approach like above, facebook should warn it's developers about using such library due to incorrect coverages.

Issue consistent in jest and nyc since they both use babel's AST.

https://github.com/AlexGilleran/jsx-control-statements

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

Feature(?)

What is the current behavior?

Incorrect Coverage

What is the expected behavior?

Correct Coverage Report on custom conditional rendered components.
Issue 1:
The weekly build with nightly wheels from numpy and pandas

has failed. Check the logs for any updates that need to be

made in matplotlib.

https://github.com/matplotlib/matplotlib/actions/runs/3072055013

Issue 2:
The weekly build with nightly wheels from numpy and pandas

has failed. Check the logs for any updates that need to be

made in matplotlib.

https://github.com/matplotlib/matplotlib/actions/runs/3163174215
Issue 1:
Challenge Change Text Inside an Element Using jQuery has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36.

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

My code:

<script>
$(document).ready(function() {
$("#target1").addClass("animated bounce");
$("h3").html("<em>jQuery Playground</em>");
});

$(document).ready(function() {
$("#target4").html("<>#target4</em>");
});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>

Issue 2:
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

6.0.0-beta.11

Operating System:

macOS 10.14.5

Last Known Working Electron version:

6.0.0-beta.10

Expected Behavior

systemPreferences.isDarkMode() should return true when the system is in dark mode.

Actual Behavior

systemPreferences.isDarkMode() always returns false.

To Reproduce

Open Electron

Open Developer Tools Console

Execute the following commands:

const electron = require('electron');

electron.remote.systemPreferences.isDarkMode();

Observe that the return value is false even if the system is in Dark Mode.

Screenshots

Additional Information

I believe this bug was probably introduced in #18958.

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

5.0.6

Operating System:

macOS 10.15 Developer Beta 2 (19A487l)

Last Known Working Electron version:

5.0.x (worked before Catalina)

Expected Behavior

systemPreferences.isDarkMode on macOS 10.15 Catalina should report whether it's in dark mode or not, even when set to Auto Mode (based on time of day). Electron 5.0.6 fixed some of the issues from #18913 , but isn't working correctly.

Actual Behavior

systemPreferences.isDarkMode is always reporting to be false.

To Reproduce

Repository: https://github.com/hyperspacedev/hyperspace

$ git clone https://github.com/hyperspacedev/hyperspace -b catalina-vibrancy
$ npm install
$ npm run electrify

Screenshots

Dark mode reports to be `false` here and is expected because it's in light mode.

Dark mode reports to be `false` here as well since, at the time of Auto Mode, it shouldn't be in dark mode.

However, dark mode reports to be `false` here, even though that isn't true.

Additional Information

I speculate that the name of the dark appearance might have changed.
Issue 1:
Hi --

According to what I'm hearing in the community, there is a feature request in to allow for setting a ttl at the index level rather than only at the doc level. See here: https://discuss.elastic.co/t/set-a--ttl-value-at-the-index-level/31668/3 where theuntergeek -- Aaron Mildenstein says "there is no index-level TTL presently. There's a feature request issue out for it (I forget the number), but it has not yet been added." and https://discuss.elastic.co/t/index-level-ttl-how-do-we-track-this-feature-request/37775 where warkolm (Mark Walkom) responded to my request about how to track such a feature with "It'd be in here - #1. If you find it, please link it here so others can benefit 😄 (I couldn't find it!)"

I've checked in issues and features and am not finding anything. Can someone please point me to where to track this feature request? I'm surprised there isn't more noise about this one, since it would make index maintenance much simpler.

Thanks,

Casie

Issue 2:
Allow setting ttl to index, so the whole index gets deleted when expired
Issue 1:
I have run the cuda version of cascade classifier in OpenCV 2.4.11 on cpu and a 860M GPU. The results can be wildly different in terms of being accurate. To a point where a detected object that was found in CPU has the same rectangle size on GPU version, but in a location that is way off. I need to know if anyone has experienced this. If you have. Did you retrain the classifier on that GPU?

I have tested my trained data(2.4.11) in OpenCV 2.4.11 cpu. I then was like well let me update the code base to use 3.2. Same, thing. Wildly different. Sometimes its correct sometimes it isn't.

I'm using LPB and blasting full 1920x1080 images at it.

This is a bug and a question.

Issue 2:
My system

OpenCV version: 3.1

Host OS: Linux (Ubuntu 14.04)

CPU: intel i7 3770

Video card: GTX-950

Video driver: v.352.93

In which part of the OpenCV library you got the issue?

objdetect, cudaobjdetect

cv::CascadeClassifier, cv::cuda::CascadeClassifier

Expected behaviour

I built the latest OpenCV version with cuda support from master branch. After that I tried to use CPU cv::CascadeClassifier and GPU cv::cuda::CascadeClassifier, but faced with a strange result. I use same xml from opencv/data/haarcascades_cuda/haarcascade_fullbody.xml for both CPU and GPU version of CascadeClassifier. CPU Classifier with this xml shows much more objects than GPU classifier.

Another strange thing, that when I set ScaleFactor to 2, speed of CPU version boosted up to 4 times, but GPU version becomes just slightly faster.

Additional description

OpencvQA

Video demo: example.ogv.zip

Video demo with same parameters values: example_v2.ogv.zip

Code example to reproduce the issue

Bitbucket: main.cpp

Bitbucket: qmake project + deps build bash script
Issue 1:
Replace pending dubbo-config-api hard coded values with constant and small refactoring to optimize code.

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.0

Operating System version: xxx

Java version: xxx

Steps to reproduce this issue

xxx

xxx

xxx

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.x

Operating System version: all

Java version: all

Steps to reproduce this issue

1.Define an interface that have multiple methods with the same name and different argument types.

2.Config every overload method with different parameters.

3.Methods configed later will overwrite the previously configed method.

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!
Issue 1:

Issue 2:
Hello everyone,

I am having an issue when finetuning OpenAI's Whisper Medium on Mozilla's Common Voice 11 Dataset with the Arabic language.

The training and validation loss are both decreasing but the WER is being 100% after some steps (specially when the loss becomes < 1) and I see that the model is performing well and that WER is just miscalculated.

Notes :

This error is just happening with the medium model, other models (small, tiny, large-v2 ,etc.) are working fine.

I am following the famous blog about Whisper's finetuning (https://huggingface.co/blog/fine-tune-whisper).

@sanchit-gandhi
Issue 1:
Electron Version:

5.0.0-beta (all)

Operating System:

Ubuntu 18.10, Linux 4.18, x64

Last known working Electron version (if applicable):

4.0.5

Expected Behavior

Google API should work as it they are meant to.

Actual behavior

Any Google API calls may crash renderer process (even if they are run on Worker thread).

The request may be done and the answer given, but immediately or after several seconds the renderer process may crash.

To Reproduce

$ git clone https://github.com/ruslang02/youtube-electron-crash-example
$ npm install electron@beta
$ npm start || electron .

Version 5 will randomly crash, version 4: doesn't

Additional Information

May be a Node.JS bug, but not sure

Issue 2:
Electron Version:

v5.0.0-beta.5

Operating System:

Windows 10 Pro.

Last Known Working Electron version::

4.x (latest)

Expected Behavior

When I perfrom a GET-request using http or https built-in library, I expect the app to keep running after the request completes.

Actual Behavior

When performing a GET request to an arbitrary host, the app crashes after a few seconds after completing the request. Usually ranges between 5 and 20 seconds.

To Reproduce

https://github.com/haroldiedema/electron-5x-http-crash

$ git clone https://github.com/haroldiedema/electron-5x-http-crash
$ npm install
$ node_modules/.bin/electron .

Sit back and wait for a few seconds for the app to crash with exit code 127. (or exit code 1 if started from npm or yarn).

Screenshots

N/A

Additional Information

I think this might have something to do with either:

A) Electron not handling the closing of sockets correctly anymore, or

B) The garbage collector kicking in and cleaning up the socket resource which makes electron crash.

Then again, that is purely speculation on my end.
Issue 1:
I have set up parameterized routing in conjunction with shallow routing in our project as per https://github.com/zeit/next.js/blob/master/examples/parameterized-routing and https://github.com/zeit/next.js/tree/master/examples/with-shallow-routing.

The router appears to be replacing history state instead of pushing history state if I push a different parameterized route for the same pathname. This results in pushing parametrized routes to appear to work until the user attempts to use the browser's back button and it skips over all state changes.

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

Expected Behavior

User follows a link to /example.

Router.push is called with the route /example and asPath /example/test1 and the shallow option.

Router.push is called with the route /example and asPath /example/test2 and the shallow option.

User his the back button and the URL is set to /example/test1.

Current Behavior

User follows a link to /example.

Router.push is called with the route /example and asPath /example/test1 and the shallow option.

Router.push is called with the route /example and asPath /example/test2 and the shallow option.

User his the back button and the URL is set to /example.

Your Environment

Tech
Version

next
2.4.5

node
6.9.1

OS
macOS sierra

browser
chrome 59

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

Expected Behavior

Editing stlye jsx styles should work with HMR.

Current Behavior

When I change a style jsx css property, the page reloads with HMR, but then I get the error:

StyleSheetRegistry: styleId: `jsx-1655195659` not found.
Error: StyleSheetRegistry: styleId: `jsx-1655195659` not found.
at invariant (http://localhost:3000/_next/-/page/index.js:47200:11)

Steps to Reproduce (for bugs)

I started with the with-styled-jsx-scss: npx create-next-app --example with-styled-jsx-scss with-styled-jsx-scss-app

Clone this minimal reproduction.

yarn install, yarn run dev

Go to localhost:3000

Change a CSS rule, f.i. background-color in src/components/Canvas.jsx

See it breaking

Your Environment

Tech
Version

next
v5.0.0

node
v8.10

OS
Windows 10

browser
Latest Chrome
Issue 1:
Hey,

So I'm a fairly new developer who had a working app until version v0.14.8, and just updated to v15.0.1 today. The update did remove a few errors/warnings I was struggling with (so a great relief there), but brought up this issue.

Specifically, the app itself renders fine, with all the pages looking fine (all components, text, etc. in the right places), but is just "frozen" - completely non-functional, not allowing me to click on anything etc.

The error message I see are as follows (from Chrome and Firefox):

I back-tracked it to where I could and found this being the part where the "node" is coming off as null:

So I have absolutely no clue what's going on and there seems to be no hint as to what exactly is causing this issue. I will try ripping the app apart and do a thorough debugging, but wouldn't expect much from it (due to my unfamiliarity with development yet...).

I really really appreciate the help in advance, and hope that this problem can contribute somewhat to improving the React ecosystem!

Issue 2:
Do you want to request a feature or report a bug?

BUG/ERROR

What is the current behavior?

"Element ref was specified as a string" error when using npm link

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:

https://github.com/odrzutowiec/react-bootstrap-jest-link-bug

What is the expected behavior?

Shouldn't error

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

React 16.4 OSX 10.13 (Chrome 66, but it doesnt matter)

Hello, I am really sorry for reporting this issue, but I got nowhere else to turn. Can you help me identify if there's a problem with my webpack in /lib or is this due to react-bootstrap/uncontrollable? Or just help me understand what is wrong here. I googled for two days, some people seem to have the same issue but no one received an answer or solution. I did npm ls react and it shows only one line, but im not sure if it takes into account the npm linked package.

I believe this issue is related or at least similar #12626
Issue 1:
https://www.tensorflow.org/versions/ says that 0.12 is most recent stable branch, which is causing new users to install the older version --

#9590 (comment)

Issue 2:
This really is a small issue but I couldn't submit a PR as I couldn't find the file for it.

At https://www.tensorflow.org/versions/ the current version is stated as 0.12 when it should be 1.0!

The docs at root (i.e. in tensorflow.org/api_docs) refer to the most recent stable branch (in this case, r0.12)

That's it. Sorry for raising an issue for such a trivial detail! Thanks
Issue 1:
Please port icons to next release. Or are you planning to move them into separate package? Cause now i can't move from 0.16.7 to next

Issue 2:
Hi, I don't believe this is a duplicate, but I've found that spreading "extra" props into the component prop is confusing and counter-intuitive (info found here: https://stackoverflow.com/questions/37843495/material-ui-adding-link-component-from-react-router). It would make a lot more sense to allow an actual render prop that can be used to actually render out a component.

For example:

// current implementation for a Tab with a Link

<Tab
value="tabOne"
component={Link}
to={`/orgs/${props.params.orgId}/members`} // this prop doesn't exist in the docs, but it works
/>

Result from proposed change:

<Tab
value="tabOne"
render={<Link to="/my/relative/path" />}
/>

This would make implementation a lot more intuitive.