WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
[ ] bug report => search github for a similar issue or PR before submitting
[x ] 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

I have an angular 2 app that gives a number of errors like the one below when the app is build using angular cli 1.0

ERROR in C:/Source/xxx/MemberUI/src/$$_gendir/app/journal/journal-component.ngfactory.ts (232,79): Supplied parameters do not match any signature of call target.

Unfortunately, this is to little information for me to fix the bug and I am unable to see the generated ngfactory file to learn more.

Angular version: 2.4.10

(unfortunately, the app does not work yet with 4.0.1)

Language: TS 2.1.5

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

7.7.1

Issue 2:
Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [X] feature request

Versions.

angular-cli 1.0.0

angular 2.4.10

Repro steps.

With the latest bugfix that uncovered AOT errors, I noticed how hard it is to pinpoint those errors. The reason is that all we get is an error during compilation like this:

ERROR in /src/$$_gendir/app/lazy/support/support.component.ngfactory.ts (2126,52): Supplied parameters do not match any signature of call target.

The offending file is transient and cannot be inspected. Due to the recently fixed bug, the code error has been there for a long time and it is now very difficult to spot the offending code in a module that has been working for months.

Desired functionality.

There should be a way to inspect (= keep) the transient file to get a better idea what the AOT compiler complains about.
Issue 1:
📝 Provide a description of the new feature

What is the expected behavior of the proposed feature? What is the scenario this would be used?

In the PT-Run window, if I want to select the 2nd item, I must use arrow keys or mouse, which could be more efficient

by introducing ALT+Num as the shortcut to choose the items.

Flow.Launcher supports this already:

It allows me to use ALT+1-9 to select items, which is more handy than mouse or arrow keys.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Issue 2:
Environment

Windows build number: [run "ver" at a command prompt]
PowerToys version: 0.16
PowerToy module for which you are reporting the bug (if applicable): General

Steps to reproduce

Wait for an update to install, then don't install it for a few days

Open the action center

Expected behavior

There is one notification there telling you about the update

Actual behavior

There are as many notifications there as days have passed, which all say the same thing and take up space

Screenshots
Issue 1:
See discussion here:

http://stackoverflow.com/questions/16999586/matplotlib-wont-plot-line-of-same-x-values/17000144?noredirect=1#comment24658630_17000144

If a graph is generated with a single horizontal line, the line is not visible in Chrome, but it is in Illustrator and in Internet Explorer.

As soon as the line stops being "straight" it becomes visible. This is not a reproduction of the vertical/horizontal issue with zoom/refresh.

Issue 2:
Perfectly horizontal or vertical lines do not show up in svgs on my machine. Could be an issue with my specific setup, I am curious if anyone else can reproduce the issue.

Here is the code that causes the bug for me:

import pylab as plt

plt.plot([-1,1],[1,1]) #perfectly horizontal line does not render

plt.savefig('/Users/Andrew/Desktop/plot.svg', format='svg')

Here is a workaround I found:

import pylab as plt

plt.plot([-1,1],[1,1.001]) #not a perfectly horizontal line; renders

plt.savefig('/Users/Andrew/Desktop/plot.svg', format='svg')

My environment:

Matplotlib 1.10 on Mac OS X 10.7 obtained from Enthought
Issue 1:
Hi

a bunch of examples seem to be missing import numpy as np. At least for me they throw NameError: name 'np' is not defined.

Following examples seem to be missing import numpy as np (non exhaustive):

scipy.signal.spectrogram

scipy.signal.periodogram

scipy.signal.welch

scipy.__version__ gives 1.4.1. However, the examples seem to be the same in the current master.

Maybe I am missing something? Any help is appreciated!

Thanks :)

Issue 2:
It is not really a bug but an issue of typical int32 overflow.

Below is an image, which, if converted to a numpy matrix is int32 and the scipy center of mass function delivers coordinates outside the grid, which is wrong. This happens, because in scipy:

normalizer = sum(input, labels, index)

overflows. Especially as 16bit images contain large numbers.

There are many methods to avoid, like making the matrix float, etc, but can it maybe be handled inside the scipy functions?

Reproducing Code Example

from PIL import Image
from scipy import ndimage
import numpy as np

im = Image.open('nf_2.png')

npa = np.array(im)

print(npa.shape,npa.dtype) # is int32
print('min/max of array',npa.min(),npa.max())
print(ndimage.center_of_mass(npa))

com_x = 0.0
com_y = 0.0
sum = 0.0 # float
for x in range(npa.shape[1]):
for y in range(npa.shape[0]):
sum += npa[y][x] # overflow if sum is int32
com_x += float(npa[y][x])*float(x)
com_y += float(npa[y][x])*float(y)
com_x /= sum
com_y /= sum
print('should be:',com_y,com_x)

Error message

(1216, 1936) int32
min/max of array 96 65520
(2645.1217782736508, 4121.233298317583)
should be: 622.3249332060187 969.6136707837329

SciPy/NumPy/Python version information

1.7.1 1.20.3 sys.version_info(major=3, minor=7, micro=7, releaselevel='final', serial=0)
Issue 1:
Mos opened SPR-6410 and commented

Please check http://forum.springsource.org/showthread.php?t=80800

RC2 doesn't work with Apache CXF anymore.

I'm sure there are other frameworks out there

which also breaks with RC2.

M4 and RC1 didn't have this problem.

Was there an accidental breaking change in RC2?

Affects: 3.0 RC2

Reference URL: http://forum.springsource.org/showthread.php?t=80800

Issue Links:

#11078 CXF integration broken in Spring 3 RC2 ("duplicates")

#11032 Cannot import bean definitions using classpath*: resource location

2 votes, 3 watchers

Issue 2:
Glyn Normington opened SPR-8903 and commented

The planned implementation of #12770 for Spring 3.2 excludes support for publishing Spring framework bundles to the SpringSource Enterprise Bundle Repository (EBR). The subset of the OSGi community that uses Spring, which includes the communities surrounding the popular Eclipse Virgo and Gemini Blueprint projects, will be impacted if such support is not put in place or some suitable workaround found.

The particular value of publishing Spring framework bundles to the EBR is that the EBR captures those bundles' transitive dependencies on "bundleised" versions of 3rd party libraries such as Hibernate which are present in the EBR. If Spring framework 3.2 bundles are omitted from the EBR, then users will need to resort to educated guesswork to determine the correct "bundleised" transitive dependencies.

The purpose of this JIRA is to track the work to implement or work around the issue, but also to raise awareness of the issue among the user community and to encourage discussion.

Although this feels more like a blocker for the OSGi/Spring community, I have raised it as critical to provide a more balanced view from the perspective of the much larger Spring community.

BTW let's not use this issue to discuss the rationale for switching to Gradle - that's the subject of #12770.

Affects: 3.2 M1

Issue Links:

#14434 Migration to gradle build lost OSGi headers ("is duplicated by")

8 votes, 22 watchers
Issue 1:
Got error messages if don't access the body data in POST route. And I guess lost connection.

127.0.0.1 - - [12/Apr/2022 00:39:05] "POST /good HTTP/1.1" 200 -
127.0.0.1 - - [12/Apr/2022 00:39:13] "POST /bad HTTP/1.1" 200 -
127.0.0.1 - - [12/Apr/2022 00:39:13] code 400, message Bad HTTP/0.9 request type ('{"id":')
127.0.0.1 - - [12/Apr/2022 00:39:13] "None /bad HTTP/0.9" HTTPStatus.BAD_REQUEST -

Return data both good, but Bad route do something criminal

Example:

from flask import Flask, request
app = Flask(__name__)

@app.route('/bad', methods=['POST'])
def bad():
return 'OK'

@app.route('/good', methods=['POST'])
def good():
# j = request.get_json() also works
d = request.data
return 'OK'

if __name__ == "__main__":
app.run(host='127.0.0.1', port=8000, debug=True, use_reloader=False)

Request 1:

curl -X POST -H 'Content-Type: application/json' -H 'Connection: keep-alive' -d '{"id": "fo"}' http://127.0.0.1:8000/good -v

GOOD: no error messages in log

127.0.0.1 - - [12/Apr/2022 00:39:05] "POST /good HTTP/1.1" 200 -

Request 2:

curl -X POST -H 'Content-Type: application/json' -H 'Connection: keep-alive' -d '{"id": "fo"}' http://127.0.0.1:8000/bad -v

BAD:

127.0.0.1 - - [12/Apr/2022 00:39:13] "POST /bad HTTP/1.1" 200 -
127.0.0.1 - - [12/Apr/2022 00:39:13] code 400, message Bad HTTP/0.9 request type ('{"id":')
127.0.0.1 - - [12/Apr/2022 00:39:13] "None /bad HTTP/0.9" HTTPStatus.BAD_REQUEST -

Environment:

Python version: 3.8.0

Flask version: Flask 2.1.1, Werkzeug 2.1.1

Issue 2:
With the following example:

from flask import Flask

app = Flask(__name__)

@app.route('/', methods=['POST'])
def hello_world():
return 'Hello World!'

if __name__ == '__main__':
app.run()

When you set the request body to {} with Postman or any HTTP clients, the first request will return 200, while the second request will return a 405 error response. The log shows the request method is {}POST:

"{}POST / HTTP/1.1" 405

Notice the request body became the part of the request method.
Issue 1:
As described in the gitter.im channel 7. April 2015 16:12 Uhr ...

Summary:

The @annotation doesn't receive hygiene treatment such as other vars do on actually pointing to an import ...

Issue 2:
Consider this test case:

import {Async} from '../';

@Async
export default class App extends React.Component {
}

@Async
class Nested extends React.Component {
}

which is compiled by ./node_modules/.bin/babel --stage 0 ./babel-bug.js into:

'use strict';

var _classCallCheck = ...

var _inherits = ...
Object.defineProperty(exports, '__esModule', {
value: true
});

var _Async = require('../');

var App = (function (_React$Component) {
function App() {
_classCallCheck(this, App);

if (_React$Component != null) {
_React$Component.apply(this, arguments);
}
}

_inherits(App, _React$Component);

exports.App = App = Async(App) || App;
return App;
})(React.Component);

exports['default'] = App;

var Nested = (function (_React$Component2) {
function Nested() {
_classCallCheck(this, Nested);

if (_React$Component2 != null) {
_React$Component2.apply(this, arguments);
}
}

_inherits(Nested, _React$Component2);

Nested = _Async.Async(Nested) || Nested;
return Nested;
})(React.Component);

module.exports = exports['default'];

Now this fails with:

exports.App = App = Async(App) || App;
^
ReferenceError: Async is not defined
Issue 1:
Issue #8703 describes exactly the problem. It is duplicate of #2895 but is much more clearly described. The problem is that it is closed but is not resolved.

Issue 2:
Electron version: 1.4.15

Operating system: macOS Sierra, Windows 10

Expected behavior

Top level menu items should be hidden when the visible property is false and not be clickable when enabled property is false.

Actual behavior

The visible and enabled properties do not behave correctly on top level menu items. It seems to work correctly for submenu items.

How to reproduce

Create a menu with this code:

const { Menu } = require('electron').remote;

const template = [
{
label: 'Should not be visible',
visible: false,
submenu: [
{
label: 'Should not be visible either',
visible: false
}
]
},
{
label: 'Should not be enabled',
enabled: false,
submenu: [
{
label: 'Should not be enabled either',
enabled: false
}
]
},
];

const menu = Menu.buildFromTemplate(template);

Menu.setApplicationMenu(menu);

Both menu items will still be visible and clickable.
Issue 1:
I setup a global keyboard shortcut as command+space:

globalShortcut.register('CommandOrControl+Space', function(){
mainWindow.show()
})

This is actually what happens though:

https://www.youtube.com/watch?v=HTN9aIRaLWw

I would expect spotlight search to be disabled.

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 feature request that matches the one I want to file, without success.

Problem Description

I need a way to give custom responses directly for some http requests from render process.

The page url should not be navigate to another url.

The virtual code explains what I want to do. (Electron has no this api.)

webRequest.filterRequest((req, res, passthrough) => {
if (req.url == 'https://github.com/') {
//res.status(200).sendFile('/path/to/hello.htm');
res.status(200).sendText('HELLO');
} else {
passthrough();
}
})

When electron run mainWindow.loadURL('https://github.com/'), user can see HELLO instead of github page. But the page's location is still https://github.com/

Proposed Solution

Alternatives Considered

Additional Information

Currently, webRequest.onBeforeRequest can redirect a request to another url. but cannot send a response directly without change the url.
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.295]
Windows Terminal version (if applicable):Windows Terminal (Preview)
Version: 0.5.2661.0

Any other software?
Visual Studio 17 15.9.4

Steps to reproduce

Run Windows Terminal (Preview)

In drop down menu press Settings

Expected behavior

Showing settings for terminal.

Actual behavior

MS Visual studio is launching with argument /dde instad settings.

Issue 2:
Environment

Windows build number: [版本 10.0.18362.239]
Windows Terminal version (if applicable):Windows Terminal (Preview) Version: 0.2.1831.0 (Microsoft Store build)

Any other software?
OpenSSH client: OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

Steps to reproduce

1.Start an ssh session in a tab(current or new would do) with RSA certificate identification.

2.Close the tab while the ssh is still connected.

Expected behavior

The tab should be closed.

Actual behavior

The Terminal stops responding and then the typical Windows messagebox for

unresponding apps will show.
Issue 1:
https://groups.google.com/forum/#!topic/julia-users/8S41r1KjdC4

How about not emitting this warning in the case where the variable name used twice is _? I'm not proposing making _ special in any other way – just skipping this warning for it.

Issue 2:
It'd be convenient to have a designated dummy variable _ (actually keyword), which would simply ignore everything stored into it. For example, you often want to deconstruct tuples like so

a, _, b, _, c = f()

where the _ values are uninteresting. Likewise, one may want to ignore function arguments, like so

function foo(a, _, b, _, c)
return (a, b, c)
end

This is actually a syntax error right now, because two arguments have the same name, which makes sense if you actually want to read their values. The idea here is to instead discard them, and reading the value of _ would be a syntax error.

In theory, this is purely about code readability: when one sees _, one knows that the value is not used and thus won't need to be thought about any further; OTOH if one sees something else, then the value is probably going to be used further down the line and needs to be kept track of. One also won't need to behold the unsightly output of wetware gensym() implementations in unused function argument names. In practice though, there is also a performance difference with the current compiler:

function f1(x1, x2, x3, x4, x5)
a, _, b, _, c = x1, x2, x3, x4, x5
return (a, b, c)
end

function f2(x1, x2, x3, x4, x5)
return (x1, x3, x5)
end

code_native(f1, (Int, String, Int, Int, Int))
code_native(f2, (Int, String, Int, Int, Int))

The assembly for f2 is significantly shorter.
Issue 1:
I'm using react 14.3, babel 6.0.15 and react test utils addon 0.14.6 . Jasmine 2.3 is my testing framework of choice.

It seems as though any stateless function component cannot be tested by TestUtils.renderIntoComponent or TestUtils.createRenderer().render(). Either returns null when rendering the function component.

Test with any stateless function component and it should yield the same result.

Component:

import React from 'react';

const User = ({name, age}) => ( return <div>{name}, {age}</div> );

module.exports = User;

Test:

expect(TestUtils.renderIntoDocument(<User name={"bob"} age={20} />)).toBeTruthy();

Error:

Expected null to be truthy.

Issue 2:
In PooledClass.js we have some static poolers based on the number of arguments & the comment specifies it's not made dynamic so we don't have to use arguments.

I have 2 questions with this:

What is the issue with using arguments (i noticed we're using it in other place reference) if it's going to reduce duplicate code ?

Can't we use the spread syntax for this like this:

function nArgumentPooler(...args) {
var Klass = this;
if (Klass.instancePool.length) {
var instance = Klass.instancePool.pop();
Klass.call(instance, args);
return instance;
} else {
return new Klass(args);
}
}
Issue 1:
integration test for consul registry and some logic to fix in consul registry

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

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:
The Dubbo version report to registry is 2.0.1 after dubbo 2.5.9 and 2.5.10.

It should be the same as the dubbo version i think.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The server should respond to requests without error. The server responds fine with NextJS 5.10.

Current Behavior

The server responds 'Internal Server Error' to all requests.

Below is the stack trace that gets logged to CloudWatch. Note the mix of forward and back slashes in the file path it is trying to resolve. I am running 'next build' (on windows) before deployment and have checked node_modules is also getting deployed.

Error: Cannot find module '/var/task/.next/dist/bundles\pages\_error.js' at Function.Module._resolveFilename (module.js:547:15) at Function.Module._load (module.js:474:25) at Module.require (module.js:596:17) at require (internal/module.js:11:18) at _callee$ (/var/task/node_modules/next/dist/server/require.js:87:46) at tryCatch (/var/task/node_modules/regenerator-runtime/runtime.js:62:40) at Generator.invoke [as _invoke] (/var/task/node_modules/regenerator-runtime/runtime.js:296:22) at Generator.prototype.(anonymous function) [as next] (/var/task/node_modules/regenerator-runtime/runtime.js:114:21) at step (/var/task/node_modules/@babel/runtime/helpers/asyncToGenerator.js:12:30) at _next (/var/task/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:9) code: 'MODULE_NOT_FOUND'

Steps to Reproduce (for bugs)

Deploy NextJS V6 app using an express custom server to Lambda using aws-serverless-express.

Context

Works fine with NextJS V5.1.0. I am unable to upgrade to NextJS V6 because of this.

next.config.js

const { PHASE_DEVELOPMENT_SERVER } = require('next/constants')

const withTypescript = require('@zeit/next-typescript');
const withSass = require('@zeit/next-sass');

module.exports = (phase, {defaultConfig}) => {
return withTypescript(withSass({
webpack(config, options) {
return config;
},
publicRuntimeConfig: {
API_HOST: (phase === PHASE_DEVELOPMENT_SERVER) ? 'http://localhost:4000' : 'https://api.xxxx'
}
}));
}

Your Environment

Tech
Version

next
6.00

node
8.10

OS
AWS Linux AMI (Linux kernel version – 4.9.85-38.58.amzn1.x86_64)

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

Expected Behavior

Current Behavior

I have custom route something like:

router.get('/feed/:id/subs', async (ctx, next) => {
....
await n.render(ctx.req, ctx.res, '/feed/subs', query)
})

And in the getInitialProps of page /feed/subs I throw error like:

let error = new Error('没有权限')
error.statusCode = 401
throw error

I can have error message shown correctly, but the status code would always 500, I think I should have the ability to change the status code.

Context

I've tried to change status code after render, but no hope, response is finished after render

Your Environment

Tech
Version

next
3.2.2

node
8.5

OS
MacOS

browser
any

etc
Issue 1:
I've been getting this problem for about 2 versions or more:

https://www.dropbox.com/s/0yiq384ihyqul5l/atom_bug.mov?dl=0

Please could you look into it and try fixing it?

The files are on a remote drive.

Mac OS X 10.10 (Atom installed at around Beta 1 of Yosemite, and now on release)

Latest version running of Atom

Issue 2:
I'm trying to remove files/dirs using sidebar, Atom asks if I want to move them to Trash and then nothing happens (files stay in the sidebar and on the disk).

This is valid only for files on a network partition, everything is ok with local ones

Version: 0.123
Issue 1:
python tests/lax_numpy_indexing_test.py --num_generated_cases=1 on Python 3.7 (fresh Anaconda install on a macOS 10.13.6). Numpy version 1.15.4.

Issue 2:
Description

Error message when importing jax. How can I solve it?

Below is the result of "pip show jax jaxlib".

What jax/jaxlib version are you using?

jax 0.4.8, jaxlib 0.4.7

Which accelerator(s) are you using?

No response

Additional system info

python - 3.9.16, MacOS 13.0, M1 Pro

NVIDIA GPU info

No response
Issue 1:
glide load cache image in SamsungNote2 ，image view always appear light green background.

glide version is 3.6.1

Issue 2:
This is the original image:

This is the image rendered using Glide and ImageView:

I'm already using the ARGB_8888 option with the following initialization code:

new GlideBuilder(this).setDecodeFormat(DecodeFormat.PREFER_ARGB_8888);

Switching to Picasso does seem to resolve the problem. What might be wrong here?