WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Bjorn Harvold opened SPR-6741 and commented

This RequestMapping doesn't work:

@RequestMapping(value = "/administration/user/{id}/account/{accountId}/transfer/{accounttransferId}", method = RequestMethod.GET)

This RequestMapping works:

@RequestMapping(value = "/administration/account/{accountId}/transfer/{accounttransferId}", method = RequestMethod.GET)

During startup, in both cases, Spring says that the above urls have been matched to a Class. There is only one method in the class to make sure nothing is being overridden. It seems this happens the moment I have more than 2 PathVariables defined.

Affects: 4.0.1

Issue Links:

#12552 Calling a @RequestMapping annotated method with a URI template with three variables does not work ("is duplicated by")

#16175 Cannot handle more than two @PathVariable with the route ends with ".png" ("is duplicated by")

#12245 Determination of the best pattern match to map a handler to an URL ("is duplicated by")

#13325 AntPathMatcher.AntPatternComparator algorithm wrong for hierarchical matches

#16239 RequestMapping path priority problem

Referenced from: commits d746e3f, ce0473f, f829cd1

3 votes, 6 watchers

Issue 2:
Gonne Martens opened SPR-2885 and commented

I have also noticed a high performance degradation from Spring 1.2.8 to Spring 2.0.1 with heavy use of prototype beans. I have attached a very simple test application which creates 100,000 prototype beans without multithreading and generated the following results:

Spring 1.2.8 2437ms

Spring 2.0 RC1 2813ms

Spring 2.0 RC2 3015ms

Spring 2.0 RC3 4515ms

Spring 2.0 RC4 4532ms

Spring 2.0 4594ms

Spring 2.0.1 4788ms

Profiling shows that about 30% of each bean creation is spent in the constructor of org.springframework.beans.SimpleTypeConverter called by the constructor of org.springframework.beans.factory.support.BeanDefinitionValueResolver during ...applyPropertyValues().

I think the main reason for the performance loss is the registration of custom editors in the constructor of BeanDefinitionValueResolver added in revision 1.12:

public BeanDefinitionValueResolver(AbstractBeanFactory beanFactory, String beanName, BeanDefinition beanDefinition)
{
this.beanName = beanName;
this.beanDefinition = beanDefinition;
this.beanFactory = beanFactory;
beanFactory.registerCustomEditors(this.typeConverter);
}

Please look at the screenshot of my profiling session.

We can not upgrade our production system from Spring 1.2.8 to Spring 2.0.1, because the load of our system would increase to high.

I am willing to help, but I need comments from the architects.

This is a duplicate of #7460 with a changed issue type and a higher priority, because of missing feedback so far.

Affects: 2.0 RC1, 2.0 RC2, 2.0 RC3, 2.0 RC4, 2.0 final, 2.0.1

Attachments:

screenshot profiling session.jpg (293.05 kB)

Spring2TestBean.java (672 bytes)

Issue Links:

#7460 Poor performance creating non-singleton beans with many threads ("duplicates")
Issue 1:
Since 0.210.0, it appears that Atom gets two icons instead of just one if Atom is pinned to the Windows taskbar. Clicking the pinned icon will open another icon that represents the running app. I would expect the first instance of Atom to reuse the pinned icon rather than adding a new one.

Issue 2:
Atom 0.199.0/win32 with all community packages disabled incorrectly autocompletes the following as soon as @ is typed:

/**
* @

This gets completed to...

/**
/**
* @

only happens on the first line after a /* or /**

happens regardless of document type (tested js, plain text and markdown)

if there is a line right below the @, cursor will be moved to the end of that line, otherwise will behind the @

tried 'ctrl-alt-q': 'unset!' under '.platform-win32 .editor' in keymap.cson to no effect (suggested here: atom/atom-keymap#35)

Sorry if this is a duplicate. Is there a way to search for single, non-alphanumeric characters on github (i.e. @) ?
Issue 1:
It may releated to Issue 2375: Crash: Use after free of std::function through CodepointWidthDetector, but I'm not sure.

Environment

Windows build number:
Microsoft Windows NT 10.0.18985.0

Windows Terminal version (if applicable):
0.4.2382.0

Any other software?
PowerShell Core 7.0.0-preview.3

Steps to reproduce

I'm not sure. Just typing in WSL in Windows Terminal and it crashed abruptly.

I tried to reproduce it by typing random strings and then crashed again, but maybe the reason of these crashes are not same.

Feedback Hub Link

https://aka.ms/AA63ois

Expected behavior

It shouldn't crash.

Actual behavior

It crashed.

Issue 2:
Hi,

I like the new terminal and use it often. One thing which doesn't look very nice is when I start the Terminal with "run as administrator" then I see the UAC prompt with the message "Unknown program". Can this be fixed to have "Windows Terminal" there?

Thanks!

best,

Oliver
Issue 1:
It's good to directly run WebAssembly files in deno like .js and .ts files. If so then I can run:

deno run myTask.wasm

without any additional files and steps. (it exports a common function like main or start or ...)

Also it's good to directly import these files to project with simple and readable syntax:

import { task1 } from ".../myLib.wasm"

Like this code in dev.to, it writes a simple library function called square and import it in .ts file and run that .ts file with deno.

Example above can be very simpler:

const wasmCode = await Deno.readFile("./target/wasm32-unknown-unknown/debug/wasm_deno_example.wasm");
const wasmModule = new WebAssembly.Module(wasmCode);
const wasmInstance = new WebAssembly.Instance(wasmModule);
const {
square,
} = wasmInstance.exports;

can write somthing like:

import { square } from "./target/wasm32-unknown-unknown/debug/wasm_deno_example.wasm";

It's much more readable, clean, easy to use, and also do not dirty the global context.

This simple feature enables more comfortable journey to publish libraries and write cross-platform deno apps.

Issue 2:
It was removed in #5135

Potentially this should be behind the --unstable flag?

cc @bartlomieju
Issue 1:
Running julia doc/genstdlib.jl to generate the ReST documentation fails on the following commit at the following line:

https://github.com/dpsanders/julia/blame/d633afac7d86021525056445efe1d12a1a7c3974/doc/stdlib/numbers.rst#L358

This is due to the fact that it finds a "duplicate" at

https://github.com/dpsanders/julia/blame/d633afac7d86021525056445efe1d12a1a7c3974/doc/stdlib/numbers.rst#L371

What is happening is that the first is a function definition, but the second is a usage of the same string within the docstring of a different function, and thus should not be a duplicate.

(This did not happen until with_rounding was merged with setrounding in #13232, which gave rise to this clash.)

Removing the exact text setrounding(T, mode) from within the definition of the second docstring successfully generates the correct documentation.

Issue 2:
I have not been able to compile Julia master successfully on my Apple Silicon Mac since Feb 9. Not exactly sure which commit led to this error:

LLVM ERROR: failed to perform tail call elimination on a call site marked musttail

signal (6): Abort trap: 6
in expression starting at none:0
__pthread_kill at /usr/lib/system/libsystem_kernel.dylib (unknown line)
Allocations: 158134957 (Pool: 158057440; Big: 77517); GC: 159
/bin/sh: line 1: 22471 Abort trap: 6 JULIA_BINDIR=/Users/gong/GitHub/julia/usr/bin WINEPATH="/Users/gong/GitHub/julia/usr/bin;$WINEPATH" /Users/gong/GitHub/julia/usr/bin/julia -O3 -C "apple-a12" --output-o /Users/gong/GitHub/julia/usr/lib/julia/sys-o.a.tmp --startup-file=no --warn-overwrite=yes --sysimage /Users/gong/GitHub/julia/usr/lib/julia/sys.ji /Users/gong/GitHub/julia/contrib/generate_precompile.jl 1
*** This error is usually fixed by running `make clean`. If the error persists, try `make cleanall`. ***
make[1]: *** [/Users/gong/GitHub/julia/usr/lib/julia/sys-o.a] Error 1
make: *** [julia-sysimg-release] Error 2

uname -a:

Darwin rocinante.local 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_ARM64_T8101 arm64
Issue 1:
Trying to load image in fragment but it doesn't work.

It says "Failed to load model" under onException

Glide.with(PImageFragment.this).load(Utility.productBaseURL + image_url)
.placeholder(R.drawable.ic_placeholder)
.error(R.drawable.ic_placeholder)
.diskCacheStrategy(DiskCacheStrategy.ALL)
.crossFade()
.listener(new RequestListener<String, GlideDrawable>() {
@Override
public boolean onException(Exception e, String model, Target<GlideDrawable> target, boolean isFirstResource) {

Utility.showLog(TAG,"onFailed");
Utility.showLog(TAG, e.getLocalizedMessage());

return false;
}

@Override
public boolean onResourceReady(GlideDrawable resource, String model, Target<GlideDrawable> target, boolean isFromMemoryCache, boolean isFirstResource) {

Utility.showLog(TAG, "onResource Ready");
return false;
}
})
.into(ivProductImage);

Issue 2:
Glide Version: 3.7.0

Hello guys,

We used a self-signed HTTPS cert on debug env, so may need to do litte thing on UrlConnection inside HttpUrlConnectionFactory under HttpUrlFetcher, is there anyway to configure/replace default DEFAULT_CONNECTION_FACTORY?

OR I have to rewrite a new module and stub by install module?

Thank you.
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/1736 on 2011-02-04 by @FrancescAlted, assigned to unknown.

The next script describes the problem.

import numpy as np

print "numpy version:", np.__version__

a = np.zeros((), dtype="S10")
a[()] = "hello1" # works!
print a
a[()] = np.array("hello2") # fails on 1.6.0.dev
print a

Running it with 1.5.0:

numpy version: 1.5.0.dev7987
hello1
hello2

With 1.6.0.dev:

numpy version: 1.6.0.dev-0e60ecb
hello1
Traceback (most recent call last):
File "/tmp/scalar-string-bug.py", line 8, in <module>
a[()] = np.array("hello2")
ValueError: cannot set an array element with a sequence

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/1735 on 2011-02-04 by @FrancescAlted, assigned to unknown.

The next script describes the problem.

import numpy as np

print "numpy version:", np.__version__

a = np.zeros((), dtype="S10")
a[()] = "hello1" # works!
print a
a[()] = np.array("hello2") # fails on 1.6.0.dev
print a

Running it with 1.5.0:

numpy version: 1.5.0.dev7987
hello1
hello2

With 1.6.0.dev:

numpy version: 1.6.0.dev-0e60ecb
hello1
Traceback (most recent call last):
File "/tmp/scalar-string-bug.py", line 8, in <module>
a[()] = np.array("hello2")
ValueError: cannot set an array element with a sequence
Issue 1:
I'm submitting a ... (check one with "x")

[X] bug report
[ ] 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

Adding the index: true attribute to a route breaks the path attribute. By this i mean that navigating to localhost/#/ gives me the route which has index:true, but navigating to the path that belongs to that route (e.g. /step/1) errors with: Cannot match any routes: 'step/1'

Expected/desired behavior

The path specified should work the same way / does.

Reproduction of the problem

Changing:

{ path: '/error', component: ErrorPage },
{ path: '/step/1', component: StartPage },
{ path: '/step/2', component: TwoPage },
{ path: '/step/3', component: ThreePage },
{ path: '/step/4', component: FourPage },
{ path: '/step/5', component: FivePage },
{ path: '/setup', component: SetupPage },

To:

{ path: '/error', component: ErrorPage },
{ path: '/step/1', component: StartPage, index: true },
{ path: '/step/2', component: TwoPage },
{ path: '/step/3', component: ThreePage },
{ path: '/step/4', component: FourPage },
{ path: '/step/5', component: FivePage },
{ path: '/setup', component: SetupPage },

breaks the path

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

It is not expected behaviour.

Please tell us about your environment:

Angular version: 2.0.0-rc.2

Browser: [all | Chrome 51.0.2704.84 ]

Language: TypeScript

Issue 2:
Steps to reproduce and a minimal demo of the problem

Clone https://github.com/sap9433/angular2-webpack-starter-kit,

npm install & npm start

App works fine because it's using "angular2": "2.0.0-beta.7"and "typings": "^0.7.9",

Update the dependencies npm-check-update -u

package.json is updated with "angular2": "2.0.0-beta.12", "typings": "^0.7.9",

Update your ambient dependencies as well to

{
"ambientDependencies": {
"es6-shim": "github:DefinitelyTyped/DefinitelyTyped/es6-shim/es6-shim.d.ts#7de6c3dd94feaeb21f20054b9f30d5dabc5efabd"
}
}

Do npm install and npm start

Now you will get plethora of duplicate identifier error like following

ERROR angular2-webpack-starter-kit/typings/browser/ambient/es6-shim/index.d.ts
(8,14): error TS2300: Duplicate identifier 'PropertyKey'.

ERROR in typings/browser/ambient/es6-shim/index.d.ts
(11,5): error TS2300: Duplicate identifier 'done'.
.....
.....

What steps should we try in your demo to see the problem?

Run the app in your local

look at the dev-server logs.

Current behavior

Updating angular2, typings, and ambient dependencies to latest release throwing error TS2300: Duplicate identifier errors.

Expected/desired behavior

App shouldn't throw error TS2300: Duplicate identifier errors

Other information

It might as well be an es6 shim issue with typescript , as both the files are using same global variable
Issue 1:
Version

2.6.10

Reproduction link

https://codepen.io/yhor1e/pen/agPbrL

https://github.com/yhor1e/vue-10249-reproduction

Steps to reproduce

Input data to the text field and push the enter button.

Take a heap snapshot in Chrome Developer Tools.

Click "Go to Second" button.

Click "Go to First" button.

Take a heap snapshot in Chrome Developer Tools.

Compare step5 heap snapshot with step2 heap snapshot. Then elements increased.

examples

ex1. Done the above steps with 1 input data.

ex2. Done the above steps with 10 input data after ex1.

What is expected?

Elements don't increase. (#Delta is 0)

What is actually happening?

Elements increase. (#Delta is not 0)

This maybe shows memory leaks.

Is this a bug?

Issue 2:
Version

2.6.10

Reproduction

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta http-equiv="X-UA-Compatible" content="ie=edge" />
<title>Document</title>
</head>
<body>
<script src="https://unpkg.com/vue"></script>

<div id="app">
<div id="nav">
<button @click="goHome">go to Home</button>
<button @click="goAbout">go to About</button>
</div>
<component :is="current"></component>
</div>

<script>
const Home = {
name: 'Home',
template: `
<div>
<h2>Home</h2>
</div>
`,
}

const About = {
template: `
<div class="about">
<h1>This is an about page</h1>
<input type="text" v-model="input">
</div>
`,
name: 'about',
data: () => ({
input: '',
}),
}

const vm = new Vue({
el: '#app',
data() {
return {
current: 'Home',
}
},

methods: {
goHome() {
this.current = 'Home'
},
goAbout() {
this.current = 'About'
},
},
components: { Home, About },
})
</script>
</body>
</html>

Steps to reproduce

go to the about page

type in the input

leave the page

collect garbage and take a snapshot with devtools

What is expected?

VueComponent count should be stable

What is actually happening?

VueComponent count keeps increasing.

seems to be related to typing in the input
Issue 1:
The status bar doesn't change when I click into the window and typing results in typing into the terminal window I started electron from.

Any idea why this might be happening?

Issue 2:
I’ve run into an odd issue testing the Neovim.AS Atom Shell app, where I cannot get its window to accept keyboard input on OS X 10.10.2 when I start it via the atom-shell CLI; instead, all keyboard input goes to the last active application – in the case of the screenshot, the shell in which Neovim.AS was started:

I also can’t switch to the window with Cmd-Tab, its OS X menu does not display, and the only way to quit it is issuing ^C in the originating shell. I have reproduced the issue with another, more straightforward Atom Shell app, pamm-atom, incidentally showing that the apps are responding to mouse input (Vim not being a really good object to judge that :)).

If I start pamm-atom via the GUI, none of the above occurs (not testable with Neovim.AS due to the Grunt requirement and lack of app folder).

Configuration:

OS X 10.10.2 German locale, German keyboard input. I’ve tried disabling my input hacks (specifically, Seil and Karabiner) and switching to a US keyboard map, but none of that helped.

atom-shell version 0.21.2 64 bit without symbols, downloaded from the Releases pages. The Atom Shell app runs without a hitch by itself, as does Atom the editor (which accepts my keyboard input like a champ, I hasten to add).

OS X stock Terminal.app running the system bash (GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin14)). The above screenshot shows a version running with TotalTerminal injected, but the same issue occurs within standard terminal windows [EDIT: and in iTerm 2].
Issue 1:
Current Behavior:

As already noted by someone else, there seems to be a problem with install/update of global packages:

$ npm up -g
npm ERR! code EPERM
npm ERR! syscall mkdir
npm ERR! path C:\Program Files\nodejs\node_modules\.npm-QXjMEw5N
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\.npm-QXjMEw5N'
npm ERR! [Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules\.npm-QXjMEw5N'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'C:\\Program Files\\nodejs\\node_modules\\.npm-QXjMEw5N'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\rbauer\AppData\Local\npm-cache\_logs\2021-03-08T10_46_40_199Z-debug.log

2021-03-08T10_46_40_199Z-debug.log

Expected Behavior:

Packages get updated.

Environment:

OS: Windows 10

Node: 14.16.0

npm: 7.5.6

Issue 2:
Current Behavior:

Attempting to update a package with a tag using the update command globally causes ALL global packages to be removed.

Expected Behavior:

Packages should not be removed when updating global packages.

Steps To Reproduce:

npm i -g typescript nodemon @angular/cli # Install some global packages
npm ls -g --depth=0 # This shows the 3 installed packages
npm update -g @angular/cli@latest # Attempt to update one of the packages with a @latest tag
# Oh no! removed 620 packages
npm ls -g --depth=0 # Shows `-- (empty)

Environment:

OS: Windows 10 20H2

Node: 15.9.0

npm: 7.11.2

Additional Info

This only happens on the global scope
Issue 1:
Not really sure where to possible report this issue. I noticed when i download bootstrap 3.0.1 via bower there appears to be an install error related to the bootstrap/dist/fonts/* no such file or directory. (fs.js) -

To test that this is indeed related to 3.0.1 i changed my bower to go back to 3.0.0 and did not encounter this issue.

Issue 2:
I'm receiving the following message when using grunt-bower-task or bower-installer to grab the main files from the repository:

no such file or directory 'bower_components/bootstrap/dist/fonts/*'

The folder is there, and the build tools dont seem to recognize the wildcard. Is this a problem for anyone else, or is could it be a problem with my installation? Any info is appreciated.

My Gruntfile looks like so:

module.exports = function(grunt) {

grunt.initConfig({
bower: {
install: {
options: {
targetDir: './bower',
layout: 'byType',
install: true,
verbose: true,
cleanTargetDir: true,
cleanBowerDir: true
}
}
}
});

grunt.loadNpmTasks('grunt-bower-task');

// Default task(s).
grunt.registerTask('default', ['bower']);

};

The commit that added the wildcard is here:

56f1ff6#diff-0a08a7565aba4405282251491979bb6b
Issue 1:
Deno will always die on unhandled exceptions / rejections.

I'd like to request the ability to change this for uncaught promises.

I know a lot of people just say hey if this happens it is your fault. Technically your right. But this is reality. And people make mistakes. Production crashing because of a mistake is a serious issue. Especially when it is so easily preventable. But the problem really gets amplified when even if you are perfect, and your code catches everything and everyone, you can still crash if one of your deps forgets. So you can not just rely on yourself being perfect but the entirety of the world needing to be perfect. This in my opinion makes Deno very hard to want to use in production. Processes crashing are not an acceptable solution imo.

Let's take a look at a simple example. Please bare with me here.

In this example, what happens is the process crashes. Because the developer of that third party dep forgot to catch something. Now this could be god knows how many deps deep. So the argument that you have to check every line of your deps code isn't really possible realistically. Nor is having to check every single commit of every single dependecy. This just adds on to more reason of why Deno is impossible to use in production.

If this was nested some 10-15 levels deep, we would never be able to debug this and even attempt a fix.

This is all to say that Deno in production is really hard to vouch for. Realistically Deno is only usable in production if you do not use any deps for your projects.

Now for another point of view. Deno is realllllllly hard to use for beginners. A lot of users wanting to use my library are first time developers. This means they are just getting into their very first coding project EVER! I have made it as easy as possible for users like this to be able to get started. They can literally use the strictest TS settings without even needing to know a thing about typing or casting or anything. However, this 1 issue of them forgetting .catch is a serious issue.

Time and time again I have users reporting their processes crashing because they simply forgot to catch something. Not have a training wheel so to speak makes this really difficult. A simple handler to prevent crashes could be soooo useful because I could have this internally built for them so it alerts them of where they are forgetting to catch so that they can fix their code and prevent their processes from crashing.

Issue 2:
I was looking for an equivalent to the Node.js "unhandledrejection" event in Deno, but it appears there isn't one on globalThis.

There does appear to be an onunhandledrejection event handler defined on workers, though.

Is there an equivalent event outside of workers, and if not, could there be? 😄