WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I'm submitting a ...

[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

The global error handler logs and detects error only once. After that all other errors do not get logged to the console.

Expected behavior

Every error get's logged to the console regardless of whether a error was thrown before or not.

Minimal reproduction of the problem with instructions

Go to https://plnkr.co/edit/EPXTqlN0hvJGavNPVfm7?p=preview

Open console

Click a button

Click a second time on a button

Angular version: 2.4.9

Browser: [all]

Language: [TypeScript 2.X]

Issue 2:
Hi!

I was wondering how Angular 2 was handling duplicates with ngFor and it's default trackBy and I was surprised to not have any warning or error.

As you can see on this plunker: https://embed.plnkr.co/dv5BIa/

If you remove the first Foo element (component 0), Angular will keep the Guido pointing on component 1 but it will reuse component 0 for the next Foo.

Actually what it does is to use an identity track by but when it meets duplicates, it says nothing and does an implicit track by index on them.

Well, we could say that in most cases if you get the same input, you get the same result so we don't care but suppose the component has some internal state like in the plunker (the input's state).

This can be really disappointing.

Is it possible to still keep this implementation but at least log a warning when we get this error?

@teropa Are you the one taking care of ngFor documentation? Maybe you should present this behaviour when the trackBy section will be added to the documentation if it's not already there and I couldn't find it.

Thank you guys!
Issue 1:
Hi everyone

I want to monitor the worker who is alive and dead.

Does the live woker list store in redis key named “_kombu.binding.celeryev”?

If confirmed, I can read the content of the key to monitor workers😄

Issue 2:
Hi everyone

I want to monitor the worker who is alive and dead.

Does the live woker list store in redis key named “_kombu.binding.celeryev”?

If confirmed, I can read the content of the key to monitor😄
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.18950.1000]
Windows Terminal version (if applicable):0.3.2142.0

Steps to reproduce

Open the drop-down menu

Click on the TitleBar

Expected behavior

Expect the drop-down menu to close since it has lost focus

Actual behavior

The drop-down menu stays open

Issue 2:
Description of the new feature/enhancement

To simplify bug reporting, please provide the version you request from the community in one place.

I suggest adding the windows version in WT's About box and let the users easily copy/paste it in the GitHub issues.
Issue 1:
I've updated Next from version 5 to 6 and on build I get:

Error: .plugins[4][1] must be an object, false, or undefined
at assertPluginItem (/node_modules/@babel/core/lib/config/validation/option-assertions.js:157:15)
at /node_modules/@babel/core/lib/config/validation/option-assertions.js:134:14
at Array.forEach (<anonymous>)
at assertPluginList (/node_modules/@babel/core/lib/config/validation/option-assertions.js:133:9)
at /node_modules/@babel/core/lib/config/validation/options.js:84:20
at Array.forEach (<anonymous>)
at validate (/node_modules/@babel/core/lib/config/validation/options.js:62:21)
at /node_modules/@babel/core/lib/config/config-chain.js:141:36
at cachedFunction (/node_modules/@babel/core/lib/config/caching.js:40:17)
at init (/node_modules/@babel/core/lib/config/config-chain.js:122:12)
at /node_modules/@babel/core/lib/config/config-chain.js:206:17
at buildRootChain (/node_modules/@babel/core/lib/config/config-chain.js:85:20)
at loadPrivatePartialConfig (/node_modules/@babel/core/lib/config/partial.js:41:53)
at loadPartialConfig (/node_modules/@babel/core/lib/config/partial.js:66:16)
at babelConfig (/node_modules/next/dist/server/build/webpack.js:88:57)
at _callee2$ (/node_modules/next/dist/server/build/webpack.js:164:34)

My babel deps are:

"babel-eslint": "^8.2.3",
"babel-plugin-inline-react-svg": "^0.5.2",
"babel-plugin-transform-class-properties": "^6.24.1",
"babel-plugin-transform-decorators-legacy": "^1.3.4",
"babel-preset-env": "^1.6.1",
"babel-root-import": "^4.1.8",
"markdown-in-js": "1.1.4",

.babelrc

{
"presets": [
"env",
"next/babel"
],
"plugins": [
"markdown-in-js/babel",
"inline-react-svg",
"transform-decorators-legacy",
"transform-class-properties",
["babel-root-import", [{
"rootPathPrefix": "~",
"rootPathSuffix": "."
}, {
"rootPathPrefix": "$",
"rootPathSuffix": "app"
}, {
"rootPathPrefix": "#",
"rootPathSuffix": "shared"
}]]
]
}

Tech
Version

next
6

node
v8.9.3

OS
macOS H.S.

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

Expected Behavior

When encountering an internal server error, it's expected that the server rendered markup matches the clients, thus avoiding flashing content.

Current Behavior

Currently internal server errors will cause a flash. More explicitly, the statusCode prop isn't present when rendering _error.js in the client, causing the markup to differ.

Steps to Reproduce (for bugs)

Setup a simple Next.js project.

Add a page pages/500.js with the following content:

export default () => { throw new Error('Boom!') }

next build && next start

Point a browser to http://localhost:3000/500.

Context

When deploying an application to production, internal server errors cause an unwanted flash of content.

Your Environment

Tech
Version

next
v5.0.1-canary.7

node
v9.4.0

OS
macOS v10.13.3

browser
Chrome v64
Issue 1:
System information (version)

OpenCV => 3.4.2

Operating System / Platform => Android P

Compiler => clang

Detailed description

libc.debug.malloc detec the memory leak when used getCoreTlsData() although implement singleton lazy initialization is already included.

256,1,"#00 pc 0xc934 /system/lib64/libc_malloc_debug.so (InternalMalloc(unsigned long)+0x164)

#1 pc 0xc768 /system/lib64/libc_malloc_debug.so (debug_malloc+0x60)

#2 pc 0x715e5c /vendor/lib64/libwa_depth.so (operator new(unsigned long)+0x20)

#3 pc 0x5297b0 /vendor/lib64/libwa_depth.so (cv::TlsStorage::setData(unsigned long, void*)+0x94)

#4 pc 0x5295bc /vendor/lib64/libwa_depth.so (cv::TLSDataContainer::getData() const+0x64)

#5 pc 0x513110 /vendor/lib64/libwa_depth.so (cv::theRNG()+0xc)

#6 pc 0x4f0088 /vendor/lib64/libwa_depth.so (cv::parallel_for_(cv::Range const&, cv::ParallelLoopBody const&, double)+0x15c)

#7 pc 0x38f7e0 /vendor/lib64/libwa_depth.so (cv::threshold(cv::_InputArray const&, cv::_OutputArray const&, double, double, int)+0xab0)

#8 pc 0xba430 /vendor/lib64/libwa_depth.so (PortraitEdgeRefine::getConfidenceMapFBS()+0x154)

#9 pc 0xb7ee8 /vendor/lib64/libwa_depth.so (PortraitEdgeRefine::runFilter(cv::Mat const&, cv::Mat const&, std::_ndk1::vector<cv::Rect, std::_ndk1::allocator<cv::Rect>> const&)+0xc5c)

#10 pc 0xbed90 /vendor/lib64/libwa_depth.so (ZNSt6__ndk114__thread_proxyINS_5tupleIJNS_10unique_ptrINS_15__thread_structENS_14default_deleteIS3_EEEEM18PortraitEdgeRefineFvRKN2cv3MatESB_RKNS_6vectorINS8_5Rect_IiEENS_9allocatorISE_EEEEEPS7_S9_S9_SH_EEEEEPvSO+0x48)

#11 pc 0x83114 /system/lib64/libc.so (__pthread_start(void*)+0x24)

#12 pc 0x233bc /system/lib64/libc.so (__start_thread+0x44)

When it try to use parallel_for_, it should use

cv::RNG& cv::theRNG(){

return getCoreTlsData().get()->rng;

}

if getData() return null , it will new ThreadData() in setData() but it will not be released. nobody call releaseThread(). so the new ThreadData() maybe leaked.

Can we release it with pthread_key_create 2nd parameter after thread finish?

int pthread_key_create(pthread_key_t *key, void (destructor)(void));

modules/core/src/system.cpp

TlsAbstraction::TlsAbstraction()

{

CV_Assert(pthread_key_create(&tlsKey, release_threadData) == 0);

}

void release_threadData(void* thread_data)

{

getTlsStorage().releaseThread();

}

Issue 2:
OpenCV => 3.3.0

Operating System / Platform => Arch Linux (4.12.13-1-ARCH SMP PREEMPT x86_64 GNU/Linux)

Compiler => gcc 7.2.0 and clang 5.0.0

Detailed description

It seems that a significant portion of memory is leaked in every thread.

The following code snippet consumes cca 100MB/s.

Steps to reproduce

#include <opencv2/opencv.hpp>
#include <future>
int main()
{
while(true) {
std::async(std::launch::async, []() { cv::Mat::zeros(1, 1, CV_32FC3); }).wait();
}
}
Issue 1:
Is it possible to create a unique session per webview? I've got a situation where I need to open up tabs to multiple sites on the same server, but I want each tab to be its own session. It would be quite convenient if I could control this on a per-tab basis, so I could make two tabs share the same session where two other tabs would have their own session entirely.

Issue 2:
When I use a webview and log in to a website (let's say github) it appears the session/cookie information is lost after restarting the application. Is there a way to enable this on the webview?
Issue 1:
Current Behavior:

npm v7 does not install linked local packages dependencies.

Expected Behavior:

In npm v6 the dependencies of a local linked package are installed. This means that if app has my-local-pkg as a dependency, running npm install generates app/node_modules folder and also my-local-pkg/node_modules (with its dependencies).

In npm v7, however, only app/node_modules is generated.

Steps To Reproduce:

I created the following repository to illustrate it. The README.md has the instructions on how to reproduce it.

Simplified, the steps are:

Add the following folder structure: ./app and ./my-local-pkg, each with their own package.json

Include this in the ./app/package.json:

{
"name": "app",
"dependencies": {
"my-local-pkg": "file:../my-local-pkg",
"prettier": "^2.2.1"
}
}

Include this in the ./my-local-pkg/package.json:

{
"name": "my-local-pkg",
"dependencies": {
"typescript": "^4.1.3"
}
}

Go to ./app and run npm install.

npm version 6 produces:

node_modules
.bin
my-local-pkg
node_modules
typescript
prettier

while npm version 7 produces:

node_modules
.bin
my-local-pkg
prettier

Compare the two outputs, npm v7 does not install my-local-pkg dependencies, there is no ./my-local-pkg/node_modules folder generated.

Environment:

npm v7.1.2

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

npm ci wipes out scripts in the .bin folder instead of reinstalling them.

Expected Behavior

npm ci reinstalls .bin scripts for each package

Steps To Reproduce

Use the npm version that comes with Node LTS this is NPM 8.1

npm install --save-dev prettier typescript

npm ci

npm ci

observe that tsc and prettier are not present in the node_modules\.bin

shake fist in confusion as previous scripts that pointed to tsc and prettier in the .bin folder fail

Environment

npm: 8.1

Node: 16.13.0

OS: Windows 10

platform: Surface Laptop

npm config:

; "builtin" config from C:\Program Files\nodejs\node_modules\npm\npmrc

prefix = "C:\\Users\\<REDACTED>\\AppData\\Roaming\\npm"

; "user" config from C:\Users\<REDACTED>\.npmrc

email = "not-used@example.com"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = <REDACTED>
; HOME = <REDACTED>
; Run `npm config ls -l` to show all defaults.

note: should be an option to remove customer information in the npm config ls
Issue 1:
Bug report

Describe the bug

I have a Next.JS app with Express routing. Locally, my code works as expected, however when I deploy the code, I get a different behavior that breaks the site.

Locally, I get a 200 from the API I'm calling, and I display the correct page. However, when I deploy this exact same code to an Azure app service inside a Docker container, the behavior is different and causes 404s.

I hit this URL in both local and deployed scenarios: <host>/research/US/Employer=7-Eleven%2c_Inc./Hourly_Rate.

I have these lines of code to log information about the req object passed in from the Express router.

console.log(`req.originalUrl: ${req.originalUrl}`);
console.log(`req.url: ${req.url}`);
console.log(`req.path: ${req.path}`);

Locally, my logging produces this (this is the desired behavior):

req.originalUrl: /research/US/Employer=7-Eleven%2c_Inc./Hourly_Rate
req.url: /research/US/Employer=7-Eleven%2c_Inc./Hourly_Rate
req.path: /research/US/Employer=7-Eleven%2c_Inc./Hourly_Rate
path: /research/US/Employer=7-Eleven%2c_Inc./Hourly_Rate

In Azure, it produces this:

req.originalUrl: /research/US/Employer=7-Eleven,_Inc./Hourly_Rate
req.url: /research/US/Employer=7-Eleven,_Inc./Hourly_Rate
req.path: /research/US/Employer=7-Eleven,_Inc./Hourly_Rate

The difference being: the comma in the url is encoded locally, but not when deployed.

To eliminate the possibility that Docker is a cause of this, I pulled the Docker image the Azure App Service is pointing to, and ran it locally. That runs without a problem, and behaves as my local app behaves.

Expected behavior

I expect both the local and the deployed app to log the same thing when given the same URL.

System information

OS: all (but I'm using Mac)

Browser: all (but I'm using Chrome)

Version of Next.js: 7.0.2

Version of Express: 4.16.4

Version of Node locally: 11.9.0

Version of Node in Docker container: 10.15.1

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

Expected Behavior

More like desired behavior; but it would be nice if a customScroll event could be passed by the user when executing shallow routing if the default scroll event provided by next here is not the desired effect.

Current Behavior

At the moment if trying to create your own custom scroll events or if using a third party library the scroll events will either be ignored or the scroll event being used by next takes precedence leading to two scroll events happening.

Steps to Reproduce (for bugs)

Please see this repo for demo & a proposed solution (albeit probably not the greatest idea)

Context

Really wanting shallow routing for a website I'm building with a scrolling layout. I'm using the react-scroll library to achiever the scrolling layout; but so far have found no concrete method for using the customScroll events being called by the library with the shallow routing feature in next.

Your Environment

Tech
Version

next
3.0.1-beta.8

chrome
59.0.3071.115

node
8.1.3

macOS
10.12.5
Issue 1:
Jonathan Nuñez Aguin opened SPR-7425 and commented

Spring needs to update the AbstractPdfView class to point to the renamed itextpdf package names.

For now, the alternative is to download an old version of iText (2.1.7) that has the com.lowagie.* package names. The actual version for iText is 5.0.2.

Affects: 3.0.3

Issue Links:

#12614 Update AbstractPdfView to use com.itextpdf.* package ("duplicates")

Issue 2:
Costin Leau opened SPR-2222 and commented

Update the petclinic.html page to mention JPA, the jar with the latests toplink drop and the code to get around the 'stale cache' issue.

Affects: 2.0 RC1
Issue 1:
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.6.0.2

Operating System version: centos-7

Java version: 1.8.0_131

Steps to reproduce this issue

服务端响应很快，但客户端老超时

如上图cat截图，客户端调用接口与服务收到接口之间，相差3秒左右

上图是pinpoint截团，说明在AbstractInvoker.invoke方法处耗时过长。

我的怀疑可能有两个原因

1）网络抖动，之所以这么怀疑是因为两个服务不在一个网段内，这个区别于他们不超时的客户端。这个不好排除，得等之后再出现异常时观察

2）客户端请求积压，对于了其他服务，这个客户端访问量并不大，且比别的不超时的客户端请求少的多。但是在服务端与客户端的异常日志中均没有找到线程池任务过多被拒绝的异常。

当前的解决办法：把配置中接口调用改为异步，并把上面的超时时间去掉走默认的1秒（之前设置的5秒超时），连接数10个。上线之后暂时没有异常，不清楚是改动造成的还是网络自己好的。

请问谁遇到过类似问题，如何判断是请求积压还是网络问题呢

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.6.5

Operating System version: xxx

Java version: 1.8

Steps to reproduce this issue

服务A helloservice注册在注册中心“shanghai”

服务B helloservice注册在注册中心"beijing"

客户端使用集群广播模式，订阅注册中心 “shanghai,beijing”无法对服务A，B进行广播

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:
Environment

Windows build number: 10.0.18362.476
PowerToys version: 0.13.0.0

Steps to reproduce

Keys randomly become disabled or behave unexpectedly. I think it issue only affects the behavior of the Shift key. When it occurs, the issue is usually noticeable when the Shift + any key to produce a character will fail (ex Shift + 5 to produce %).

I have not been able to determine what leads to this behavior. The does not begin immediately after the app is launched; it begins randomly, or after some sequence of keystrokes from me that I haven't identified, but once the issue begins, the only way to stop it is to exit PowerToys.

Expected behavior

Shift + any key returns expected character

Ex: Shift + 7 returns &

Actual behavior

Shift + any key returns no response

Issue 2:
First of all, the Color Picker is awesome to have and I use it all the time. Thank you for making/including it.

One thing I noticed tho is that several programs I use that accept a hex code limit the input field to 6 characters, so when I use the picker and then paste into the field, it chops off the last character because the pound sign is not intended to be included.

This means I either need to remember the last character, paste the Pick'd code, delete the #, and enter the remembered-character, or paste from the Picker into a text editor (or usually a browser URL bar, if it's closest :)) and then highlight/copy the code again without the "#".

This feels like unnecessary run-around that could be easily fixed by just adding a 3rd option in the "Appearance & behavior" dropdown for just the hex code sans # sign, and I hope you will consider implementing this.

Thanks.

chris
Issue 1:
It seems to me that output is line-wrapped by conhost before being sent through the ConPTY stdout pipe. This makes sense, though it has the unfortunate downside that in Alacritty we can't do the line-wrapping ourselves.

This wouldn't matter that much, but when selecting and copying text in Alacritty which has been line-wrapped by conhost, Alacritty isn't aware that the text was originally a single line and inserts a newline into the content placed on the clipboard.

Is it possible to disable the line wrapping by conhost?

(Perhaps this would be something that would naturally be in the "passthrough" mode I've seen mentioned elsewhere in this issue tracker?)

Issue 2:
Windows 10.0.18362.0, Windows Terminal Preview 0.4

The character is the Scotland flag emoji.
Issue 1:
When you pass doctrine proxy object to twig render function e.g.

{{ render(controller('ExampleBundle:Example:index', {'item', md.item})) }}

where "md" is entity with property "item" that represent object of many to one relationship, render function converts proxy object to array and "indexAction" of "ExampleController" gets that array instead of proxy object and you lose all access to getters and setters.

See this issue #7122;

Issue 2:
Personally I think it should be supported by default, only having to specify locale to override.

For example if I have routes:

/contact

/about

/fr/contact

/fr/about

on /fr/about I have a path:

{{ path('contact') }}

Why would that create a path for /contact by default instead of /fr/contact ?

From what I understand to create what should be default behavior on a per link basis, I must:

{{ path('address', {'_locale': app.request.attributes.get('_locale')}) }}

Any plans to amend this?
Issue 1:
Issue description

As it illustrates in the doc, torch.nn.Batchnorm1d supports both input of size (N, C, L) and (N, C) . Howevere, when the input size is (1, C)(batch size is 1), pytorch will produce an error. It seems that if N > 1, there will be no error at all.

Another interesting fact is, when I try to seperate a minibatch into multi cards(by using torch.nn.DataParallel), since the batch size for each gpu is not decided by me, this error may also happens with N > 1(for a specific gpu, its batch size may be 1 under some circumstances). I know currently PyTorch does not support distributed batchnorm, but it still worth a report, I think.

Code example

import torch

class Foo(torch.nn.Module):
def __init__(self):
super(Foo, self).__init__()
self.bn = torch.nn.BatchNorm1d(3)

def forward(self, x):
return self.bn(x)

def main():
x1 = torch.ones(1,3)
x2 = torch.ones(2,3)
model = Foo()
y = model(x1) # this line will fail to run
y = model(x2) # this line can run without error

if __name__ == '__main__':
main()

System Info

PyTorch version: 0.4.0

Is debug build: No

CUDA used to build PyTorch: 9.1.85

OS: Debian GNU/Linux unstable (sid)

GCC version: (Debian 6.4.0-17) 6.4.0 20180424

CMake version: version 3.11.1

Python version: 3.6

Is CUDA available: Yes

CUDA runtime version: 9.1.85

GPU models and configuration: GPU 0: GeForce GTX 1070

Nvidia driver version: 390.48

cuDNN version: Probably one of the following:

/usr/lib/cuda/lib64/libcudnn.so.7.1.3

/usr/lib/cuda/lib64/libcudnn_static.a

Versions of relevant libraries:

[pip3] numpy (1.14.2)

[pip3] torch (0.4.0)

[pip3] torchvision (0.2.0)

[conda] Could not collect

Issue 2:
I find in some tasks , for example, semantic segmentation, detection, sync batch norm is crucial for performance.In these tasks, batch size per gpu is small so we need sync the bn's mean and variance to enlarge the bn's "batch size". It need synchronize parameters and gradient across multi gpus in forward and backward. This will obviously improve the performance. I believe this will attract more and more users. So can you implement it in pytorch?