WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Checklist

I have verified that the issue exists against the main branch of Celery.

This has already been asked to the discussions forum first.

I have read the relevant section in the

contribution guide

on reporting bugs.

I have checked the issues list

for similar or identical bug reports.

I have checked the pull requests list

for existing proposed fixes.

I have checked the commit log

to find out if the bug was already fixed in the main branch.

I have included all related issues and possible duplicate issues

in this issue (If there are none, check this box anyway).

Mandatory Debugging Information

I have included the output of celery -A proj report in the issue.

(if you are not able to do this, then at least specify the Celery

version affected).

I have verified that the issue exists against the main branch of Celery.

I have included the contents of pip freeze in the issue.

I have included all the versions of all the external dependencies required

to reproduce this bug.

Optional Debugging Information

I have tried reproducing the issue on more than one Python version

and/or implementation.

I have tried reproducing the issue on more than one message broker and/or

result backend.

I have tried reproducing the issue on more than one version of the message

broker and/or result backend.

I have tried reproducing the issue on more than one operating system.

I have tried reproducing the issue on more than one workers pool.

I have tried reproducing the issue with autoscaling, retries,

ETA/Countdown & rate limits disabled.

I have tried reproducing the issue after downgrading

and/or upgrading Celery and its dependencies.

Related Issues and Possible Duplicates

Related Issues

#6898

#6885

Possible Duplicates

None

Environment & Settings

Celery version:

celery report Output:

Steps to Reproduce

Required Dependencies

Minimal Python Version: N/A or Unknown

Minimal Celery Version: N/A or Unknown

Minimal Kombu Version: N/A or Unknown

Minimal Broker Version: N/A or Unknown

Minimal Result Backend Version: N/A or Unknown

Minimal OS and/or Kernel Version: N/A or Unknown

Minimal Broker Client Version: N/A or Unknown

Minimal Result Backend Client Version: N/A or Unknown

Python Packages

pip freeze Output:

Other Dependencies

N/A

Minimally Reproducible Test Case

Expected Behavior

'args': req.argsrepr,
'kwargs': req.kwargsrepr,

Actual Behavior

'args': safe_repr(args),
'kwargs': safe_repr(kwargs),

Issue 2:
Hi, I am running celery worker command as follows:-

pipenv run celery worker -A <celery_instance_file> -l info on windows OS.

I checked the version of celery module installed in python. It says 5.0.0.

#Python interpreter

import celery

celery.version

'5.0.0'

So the error is as follows:-

Usage: celery worker [OPTIONS]

Try 'celery worker --help' for help.

Error: no such option: -A

I checked the documentation of celery version 5.0.0, and it still has the option -A.

https://docs.celeryproject.org/en/latest/reference/cli.html

So let me know if this is limitation with windows or if this is a bug.
Issue 1:
Environment

Windows build number: 10.0.18362.0

Windows Terminal version: 0.4.2382.0

Steps to reproduce

Enter any command with more string then windows height.

$a = @{

1

2

... etc

Expected behavior

Terminal allow entering command with as many string as needed.

Actual behavior

Oops, something went wrong. Please report this bug with the details below.

Report on GitHub: https://github.com/lzybkr/PSReadLine/issues/new

Last 43 Keys:

$ a Space = Space @ { Enter
1 Enter
2 Enter
3 Enter
4 Enter
5 Enter
6 Enter
7 Enter
8 Enter
9 Enter
0 Enter
q Enter
w Enter
e Enter
r Enter
t Enter
y Enter
u Enter
i

Exception:

System.ArgumentOutOfRangeException: The value must be greater than or equal to zero and less than the console's buffer size in that dimension.
Parameter name: top
Actual value was -1.
at System.Console.SetCursorPosition(Int32 left, Int32 top)
at Microsoft.PowerShell.PSConsoleReadLine.ReallyRender(RenderData renderData, String defaultColor)
at Microsoft.PowerShell.PSConsoleReadLine.ForceRender()
at Microsoft.PowerShell.PSConsoleReadLine.Insert(Char c)
at Microsoft.PowerShell.PSConsoleReadLine.SelfInsert(Nullable`1 key, Object arg)
at Microsoft.PowerShell.PSConsoleReadLine.ProcessOneKey(ConsoleKeyInfo key, Dictionary`2 dispatchTable, Boolean ignoreIfNoAction, Object arg)
at Microsoft.PowerShell.PSConsoleReadLine.InputLoop()
at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics, CancellationToken cancellationToken)

Issue 2:
Other

This bug seems to be tied to yarn or react-scripts. I ran a python interpreter in one tab, opened another tab and then closed my terminal. Everything worked as expected. It maybe a bug in yarn or react-scripts, but I am fairly confident that it is not due to step 4. in steps to reproduce. The fact that you have to be out of the tab running the long running process in order to trigger the bug implies to me that this is an issue with terminal.

Environment

Windows build number: 10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): 0.4.2382

Yarn: 1.17.3
react-scripts: 3.0.1

Steps to reproduce

Open a terminal

Run yarn start on a CRA Project.

Open a new tab

Navigate to the new tab (this is a requirement)

Click the close button.

Wonder why the terminal is still running

Expected behavior

No matter the amount of open tabs and long running processes, clicking close should kill all running processes in all tabs.

Actual behavior

When a user opens a tab and runs a long running process in it, then opens another tab and then finally closes the terminal, the terminal should kill all running processes.

In my instance I run yarn start with my CRA project in one tab and use the other tab for testing and running git commands. When I click the close button, the terminal does not kill all processes.
Issue 1:
I'm having some issues using the ursa module on electron.

I installed the module using npm like so:

npm install --save ursa

Then rebuilt the native extensions for electron like so:

./node_modules/.bin/electron-rebuild

This seemed to exit immediately / not actually do anything, and when I ran the app I got the usual error message:

Error: Module version mismatch. Expected 44, got 14.

So I rebuild the native extension manually using node-gyp like so:

HOME=~/.electron-gyp node-gyp rebuild --target=0.28.1 --arch=ia64 --dist-url=https://atom.io/download/atom-shell

And I now get the following error message:

dyld: lazy symbol binding failed: Symbol not found: _RSA_generate_key
Referenced from: /Users/daniel/work/kuddl/electron-client/node_modules/ursa/build/Release/ursaNative.node
Expected in: dynamic lookup

dyld: Symbol not found: _RSA_generate_key
Referenced from: /Users/daniel/work/kuddl/electron-client/node_modules/ursa/build/Release/ursaNative.node
Expected in: dynamic lookup

Here's my code:

var ursa = require('ursa');
var key = ursa.generatePrivateKey(2048, 65537);

I think this may be related to this issue: #1410

Version Numbers:

Electron Version
v0.28.1

Operating System
Mac OSX 10.10.0

ursa
v0.8.5

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:
Returns an error

Hope to repair it as soon as possible, thank you. Point a praise

Issue 2:
EDIT (@nicolo-ribaudo): We have identifier the issue and reported it upstream (mjackson/unpkg#162). If you are affected, please give a 👍 to that issue and, if requested, give any information that could help fixing it!

Note: Different people are affected but not everyone, and part of the discussion is at #1901.

Original issue submitted by @renyuns in babel/babel#9223

Bug Report

Current Behavior

A clear and concise description of the behavior.

Input Code

REPL or Repo link if applicable:

var your => (code) => here;

Expected behavior/code

A clear and concise description of what you expected to happen (or code).

Babel Configuration (.babelrc, package.json, cli command)

{
"your": { "config": "here" }
}

Environment

Babel version(s): [e.g. v6.0.0, v7.0.0-beta.34]

Node/npm version: [e.g. Node 8/npm 5]

OS: [e.g. OSX 10.13.4, Windows 10]

Monorepo: [e.g. yes/no/Lerna]

How you are using Babel: [e.g. cli, register, loader]

Possible Solution

Additional context/Screenshots

Add any other context about the problem here. If applicable, add screenshots to help explain.
Issue 1:
TS 1.7.5, Target ES6, Environment Windows 8.1, Node 5.6

Since switching the "target" to ES 6, "target.name" is empty in class decorators. With ES5 ist worked as expected.

I'm decorating my classes with class and property decorators:

The decorated TS class:

@sg.DMClass
export class User implements IUser {
@sg.DMProperty
firstName: string;
@sg.DMProperty
lastName: string;
@sg.DMProperty
friends: User[];
@sg.DMProperty
blogPosts: BlogPost[];
@sg.DMProperty
test: User;
}

The TS decorator:

export function DMClass(target: any) {
var t = Reflect.getMetadata("design:paramtypes", target);
var om = Reflect.getOwnMetadataKeys(target);
console.log("schemaGen.DMClass: target: %s: %O", target.name, target);
var schema = target.prototype[Schema];
target[IsDomainClass] = true;
target[Schema] = target.prototype[Schema];
schema.class = target.name;
console.log("schemaGen.DMClass: schema: %O", schema);
}

Current (faulty) behaviour:

So "target.name" is empty. Having a look at the generated js file seems to reveal the problem:

var gq = require("./gq");
var sg = require("./schemaGen");
var cons = console;
let User = class {
};
__decorate([
sg.DMProperty,
__metadata('design:type', String)
], User.prototype, "firstName", void 0);
__decorate([
sg.DMProperty,
__metadata('design:type', String)
], User.prototype, "lastName", void 0);
__decorate([
sg.DMProperty,
__metadata('design:type', {name: 'Array<User>', type:'Array', elemType:'User'})
], User.prototype, "friends", void 0);
__decorate([
sg.DMProperty,
__metadata('design:type', {name: 'Array<BlogPost>', type:'Array', elemType:'BlogPost'})
], User.prototype, "blogPosts", void 0);
__decorate([
sg.DMProperty,
__metadata('design:type', User)
], User.prototype, "test", void 0);
User = __decorate([
sg.DMClass,
__metadata('design:paramtypes', [])
], User);
exports.User = User;

Expected behaviour:

So TS generates class without name. I think it should generate following:

let User = class User {
};

Manually adding "User" as class name of course solves the problem, because then "target.name"( == "class.name") is just accessing an ES 6 property.

Any help ist appreciated,

best Mind

Issue 2:
I have decorator:

export function Document() {
return function(objectConstructor: Function) {
console.log(objectConstructor.name); // when targeting es5 it gives me what I want - the name of my class. When targeting es6 it does not give anything
}
}

Here is decorator usage:

@Document()
export class User {
}

Im using "User" class name to create a document called "User", I need information how class is called. I always used es5, but now when I switched to es6 compile target I dont have information about class name anymore. Is it a bug, or it by design? If second then what is the way to get the class name?
Issue 1:
Hello, I'd like to import some JSX files in my test files. My use case is to import test helpers from my main codebase. Those include JSX code.

Right now, when I import those files, I get this kind of errors:

SyntaxError: Unexpected token '<'

Is there a simple way to add JSX support to playwright test?

Issue 2:
Context:

Playwright Version: 1.28.1

Operating System: Mac

Node.js version: v16.16.0

Browser: All

Extra: Typescript Monorepo

Code Snippet

Here is an example repo which demonstrates the issue

https://github.com/rubber-duck-software/playwright-typescript-monorepo-tsx

Describe the bug

This is a followup to #17964. Playwright can now do the jsx transform in general, but it cannot handle jsx fragments. As far as I can tell babel-plugin-syntax-jsx does support fragments, so I am not sure about the underlying cause of this issue.
Issue 1:
Issue Type: Feature Idea

Component Name: module_utils/ec2.py

Ansible Version: devel

Summary:

I know there is this module:

http://docs.ansible.com/ansible/sts_assume_role_module.html

But having this in the ec2.py module utility seems like a much better way to go as it is a lot of boiler plate to have to add sts_assume_role to every playbook that assumes roles. We only assume roles at our company to do anything with AWS so it is painful for us. It would be pretty trivial for me to add this to ec2.py.

Issue 2:
ISSUE TYPE

Bug Report

COMPONENT NAME

ec2 dynamic inventory script

ANSIBLE VERSION

ansible 2.0.1.0

OS / ENVIRONMENT

On Ubuntu Linux, and Amazon Linux on AWS

SUMMARY

I cannot assume a role on the command line by exporting the new temporary credentials as environment variables and run the inventory script.

I have my 'master' AWS account's credentials in ~/.aws/credentials, then I assume a role on another account, and export the AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SECRET_TOKEN and AWS_SESSION_TOKEN values it gives me. When I run the inventory script (which I have updated from latest devel, as of now) I get:

ERROR: "Authentication error retrieving ec2 inventory.
- AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment vars found but may not be correct
- Boto configs found at '~/.aws/credentials', but the credentials contained may not be correct", while: getting EC2 instances

I am using the latest inv/ec2.py as of now.

Thanks
Issue 1:
Issue Type: Bug Report

Ansible Version: ansible 1.9.3

Environment: Debian Jessie x64

Summary:

Recurrence of issue #9074. The same steps may be used to reproduce this bug.

Issue 2:
Issue Type: Bug Report

Ansible Version:

root@68b23fe4c544:~/Code/devel/tools/python/atlas# ansible --version

ansible 1.9

configured module search path = /usr/share/ansible:./modules

root@68b23fe4c544:/opt/ansible-new# git log -p -1

commit fb717ff

Merge: a68ca90 57c81df

Author: Brian Coca bcoca@ansible.com

Date: Fri Mar 6 11:45:07 2015 -0500

Merge pull request #10345 from emonty/features/openstack-inventory-docs

Add documentation for the new OpenStack Inventory

Environment:

I am running ansible from within a cloudfoundry/lucid64:minbase Docker image. I installed ansible from git.

The system that I am orchestrating is a Fedora 15 machine.

Summary:

Service module tries to use systemctl when it detects the system is using systemd, but the service I am trying to restart is using still using Sys V style init script. Further described ( including a possible fix ) on the ansible developer list ( see https://groups.google.com/forum/#!topic/ansible-devel/0ml1y6gkmEc )

Steps To Reproduce:

On the Fedora 15 system I am managing, auditd and sshd are both Sys V init scripts as well as our custom service init scripts.

- hosts: fedora
sudo: yes

tasks:
- service: name=auditd state=restarted enabled=yes

Expected Results:

I would expect the service module to recognize that the service is not managed by systemd and use rc.local or the init script to manage the service.

Actual Results:

TASK: [service name=auditd enabled=yes] ***************************************
<10.17.217.203> ESTABLISH CONNECTION FOR USER: root on PORT 22 TO 10.17.217.203
<10.17.217.203> REMOTE_MODULE service name=auditd enabled=yes
<10.17.217.203> EXEC /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1425923472.38-164975472934968 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1425923472.38-164975472934968 && echo $HOME/.ansible/tmp/ansible-tmp-1425923472.38-164975472934968'
<10.17.217.203> PUT /tmp/tmpAPdmFn TO /home/sgadmin/.ansible/tmp/ansible-tmp-1425923472.38-164975472934968/service
<10.17.217.203> EXEC /bin/sh -c 'LANG=C LC_CTYPE=C /usr/bin/python /home/sgadmin/.ansible/tmp/ansible-tmp-1425923472.38-164975472934968/service'
failed: [10.17.217.203] => {"failed": true}
msg: Error when trying to enable auditd: rc=1 Unit name auditd is not a valid unit name.
Cannot install unit auditd: Invalid argument

FATAL: all hosts have already failed -- aborting
Issue 1:
package p
type F1 func(i int) (i int)
type F2 func(i int, i int) (i int)
type F3 func(i int) (i int, i int)

Compiling this with 6g gives an error "duplicate argument i" for the F2 and F3
lines, but does not give an error for the F1 line. I think that either all or none
should give errors.

My reading of the spec is that none should give errors. The spec does not say anything
about the parameter names in a function type. It is implied that they serve only as
comments. So I think the correct action is to change F2 and F3 to not give errors.

But it would also be OK with me to change the spec and to make F1 give an error.

(Of course all three should and do give an errors when used in a function declaration
rather than a function type declaration.)

Issue 2:
by yunge.fu:

When http.Client receives http redirect response, it just copy part of origin Headers,
such as "Referer", for the new Request.
But sometimes people need original or custom Headers, such as UserAgent, by now
http.Client will always use defaultUserAgent.

I think just copy the original Header for the new Request is a better way.

The related code is in:
http://golang.org/src/pkg/net/http/client.go, func doFollowingRedirects()
Issue 1:
From @mattflix on April 24, 2016 10:6

VSCode Version: 1.0.0

OS Version: Mac OS 10.11.3

Steps to Reproduce:

Create the example project outlined below. (This is a valid program than runs under Node.)

Intellisense for imports within ./index.js does not work.

Example:

// ./jsconfig.json

{
"compilerOptions": {
"target": "es6",
"module": "commonjs"
}
}

// ./index.js

var hello = require('foo');

console.log(hello('world'));

// ./node_modules/foo/index.js

module.exports = function(name) {
return 'hello ' + name;
}

With VS Code opened to the folder designated by the dot (.) in the paths above, there is no meaningful Intellisense provided for symbol "hello" in ./index.js. Why not?

I did notice that, if an appropriate ./node_modules/foo/index.d.ts file is added, then Intellisense appears. But, I can't and/or don't want to use a Typescript definition for every module in my program.

In any case, TypeScript embellishment is beside the point... I thought VS Code was supposed to provide some minimum useful Intellisense even for plain Javascript, no? The advertised "rich editing support" features for Javascript described at https://code.visualstudio.com/Docs/languages/javascript certainly implied as much to me.

I mean, the static analysis engine should at least be able to infer that the default export of module "foo" is a function, with a parameter called "name", returning "any", right?

Or, do I not understand what the following feature descriptions (quoted from the aforementioned web page) are trying to say?

IntelliSense

The JavaScript Support uses different strategies to provide IntelliSense.

IntelliSense based on type inference

JavaScript uses the same inference as TypeScript to determine the type of a value.

The following patterns are also recognized:

"ES3-style" classes, specified using a constructor function and assignments to the prototype property.

CommonJS-style module patterns, specified as property assignments on the exports object, or assignments to the module.exports property.

The "IntelliSense based on type inference" and "CommonJS-style module patterns" is what initially caught my eye when looking into using VS Code for my Javascript work.

But, when I tried the example code shown above, in an attempt to test out both of these features, I could not get them to work even in the simplest of toy projects.

Am I doing something wrong?

Copied from original issue: microsoft/vscode#5714

Issue 2:
From @alexandrudima on January 27, 2016 14:48

Testing #2218

File structure:

node_modules

something2

main.js

package.json

consumer.js

node_modules/something2/main.js:

var f = function() {
if (true || true) {
return 5;
}
return '5';
}
exports.x = f();

node_modules/something2/package.json:

{
"name": "something2",
"version": "0.0.0",
"main": "./main.js"
}

consumer.js

var s2 = require('something2');
s2.

Observe: x is not suggested for s2

Copied from original issue: microsoft/vscode#2459
Issue 1:
The following code:

pub fn log(x: f64) -> f64
{
let out: f64;
unsafe {
asm!("fldln2
fldl $1
fyl2x" : "=t"(out) : "m"(x));}
out
}

errors with the message:

error: couldn't allocate output register for constraint 't' at line 27

The constraint t refers to the top of the floating point stack in GCC's inline assembly, and the unsafe guide says our constraints mirror theirs.

Issue 2:
The sum and product methods are wrappers around fold, but only work with iterators where the element type A directly implements Add<A, A>/Mul<A, A>. With an iterator of references to numbers, you can do iter().fold(0, |a, b| a + *b), but with sum/product the elements have to be cloned via map (inefficient for big integers, and uglier than using fold).

The to_owned_vec method simply calls collect, and removes the need to specify a type annotation. It's the only method on iterators using a specific container type, which is ugly. A language solution to this problem (partial type hints? collect::<~[_]>()) would be nice.

These are good candidates for being marked with a stability warning attribute.
Issue 1:
iris = sns.load_dataset("iris")

sns.pairplot(data=iris, x_vars=['sepal_length', 'petal_length','petal_width'], y_vars=['sepal_width']);

sns.pairplot(data=iris, x_vars=['','sepal_length', 'petal_length','petal_width'], y_vars=['sepal_width']);

sns.pairplot(data=iris, x_vars=['sepal_length', '', 'petal_length','petal_width'], y_vars=['sepal_width']);

First plot of pairplot is not being displayed when using multiple variables in [x_vars.]

(https://github.com/RPunyatoya/Seaborn-Issue/blob/master/Seaborn%200.11.0%20Issue.ipynb)

Also when giving wrong column name such as blank (''), It's not throwing any error instead just displaying empty plot in the 1st place where as getting appropriate error when providing '' as 2nd onward column name.

Thank you..!!

Issue 2:
Just updated to seaborn 0.11.0 and matplotlib 3.3.1.

Run this code:

iris = sns.load_dataset("iris")
sns.pairplot(data=iris, hue="species", y_vars='sepal_width');
sns.pairplot(data=iris, hue="species", y_vars='sepal_width', x_vars=['sepal_length', 'petal_length']);

And saw it:

And this problem appeared in all previously created pairplots, that have parameter y_vars
Issue 1:
For Keyboard Manager, one can remap a keyboard key for combination of keys.

Example, one can map:

[Fn] + [Right Arrow] = End

[Fn] + [Left Arrow] = Home

Also, one can remap a shortcut using "Function" key". The possibilities are amazing and endless!!

Example: [Fn] + M = Opens Minecraft

Issue 2:
Summary of the new feature/enhancement

I really love this feature since I am a mac user first but started using windows for some WFH on my gaming machine.

however it would be great to disable power toys run automatically when not needed, e.g. full screen/borderless windowed applications such as games.

if disabling automatically is not possible, how about a little toggle when right clicking the taskbar icon.
Issue 1:

Issue 2:
Hi,

The code used on last Thursday worked fine. But after updated to latest code on Monday (GMT+8), the modal dialog when clicks to dismiss for seconds onward cannot be close.

I am checking on source code line 932, if I commented out this line then it is working again.

this.$element

.removeClass('in')

.attr('aria-hidden', true)

//.off('click.dismiss.modal')

Am I missing anything...?

Sorry for the grammar. Thanks.