WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
http://www.celeryproject.org/ says "Celery is easy to integrate with ... Flask, using the ... Flask-Celery add-on packages."

Meanwhile, https://pypi.python.org/pypi/Flask-Celery states in bold "FROM CELERY 3.0 THIS LIBRARY IS NO LONGER NECESSARY, INSTEAD YOU SHOULD USE THE STANDARD CELERY API."

So the suggestion should be removed from the Celery project homepage?

Issue 2:
http://www.celeryproject.org/ says "Celery is easy to integrate with ... Flask, using the ... Flask-Celery add-on packages."

Meanwhile, https://pypi.python.org/pypi/Flask-Celery states in bold "FROM CELERY 3.0 THIS LIBRARY IS NO LONGER NECESSARY, INSTEAD YOU SHOULD USE THE STANDARD CELERY API."

So the suggestion should be removed from the Celery project homepage?

(Moved from celery/celery#1205 )
Issue 1:
Issue Type:

Bug Report

Ansible Version:

ansible 1.7 (devel 6bc056e) last updated 2014/06/02 19:46:03 (GMT -700)

Environment:

Mac OS X 10.9.3

Summary:

Subsequent dependent roles are ignored when a role containing the dependency is conditionally skipped and the dependency is marked allow_duplicates: no.

Steps To Reproduce:

Playbook contains:

roles:
- { role: role_a, when: false }
- role_b

role_a and role_b have dependencies in meta/main.yml:

dependencies:
- role_c

role_c disables duplicates in meta/main.yml:

allow_duplicates: no

Expected Results:

role_c is skipped, role_a is skipped.

role_c executes as a dependency of role_b

role_b executes.

Actual Results:

role_c is skipped, role_a is skipped.

role_b executes, but role_c dependency is never satisfied.

Issue 2:
Issue Type:

Bug Report

Ansible Version:

master

Environment:

N/A

Summary:

If a role dependency is skipped, via:

---
dependencies:
- { role: foo, when: false }

Then it's children are also skipped, even if they are required by other roles.

Steps To Reproduce:

# roles/foo/meta/main.yml

---
dependencies:
- { role: child, when: false }

# roles/bar/meta/main.yml

---
dependencies:
- { role: child }

# roles/parent/meta/main.yml

---
dependencies:
- { role: foo }
- { role: bar }

If the parent role is used, then child will never be executed.

Expected Results:

Roles are re-run if required by subsequent roles, and have not been run already (under no-duplicate roles policy).

Actual Results:

Role is skipped for the rest of the play.
Issue 1:
A clear and concise description of what the bug is.

How to reproduce the bug

set a LOG_FORMAT , e.g. '{"severity":"%(levelname)s","message":"%(message)s","timestamp":"%(asctime)s"}'

Expected results

all logs respect it

Actual results

some log messages get logged duplicated, once with and once w/o the format

Serving from cache │
{"severity":"INFO","message":"Serving from cache","timestamp":"2023-04-28 15:47:30,865"}
Cache key: 7003a08fde69f54ab83686bded041a57
{"severity":"INFO","message":"Cache key: 7003a08fde69f54ab83686bded041a57","timestamp":"2023-04-28 15:47:30,877"}

The field `timeseries_limit` is deprecated, please use `series_limit` instead.
{"severity":"WARNING","message":"The field `timeseries_limit` is deprecated, please use `series_limit` instead.","timestamp":"2023-04-28 15:48:00,513"}

Environment

superset version: 2.1

Checklist

Make sure to follow these steps before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if there are any.

I have reproduced the issue with at least the latest released version of superset.

I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

Issue 2:
Every log message (except event logs) is logged 2 times, once in the custom format set in the "superset_config.py" (or the default one in "config.py" if not set otherwise) and the second time just the message without any context.

How to reproduce the bug

Run apache/superset image locally with docker

Look at logs

Expected results

See every log entry once

Actual results

See every log entry twice

Logs from docker logs

logging was configured successfully

2022-09-29 12:14:17,528:INFO:superset.utils.logging_configurator:logging was configured successfully
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-give-a-background-color-to-a-div-element has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

This happens on all Waypoints I've tried since the update. It did not happen prior. Here's a video of the behavior:

http://www.screencast.com/t/925RcgPZ

Mac OS X Yosemite

10.10.4 (14E46)

Safari Version 8.0.7 (10600.7.12)

Issue 2:
Issue Description

As a developer, having a notification on beta challenges that tests are incomplete would help me find issues to work on.

As a product owner, having a notification of missing tests on beta challenges will reduce the number of incoming tickets and duplicate tickets because users will know the challenge is incomplete.

Additionally, I think this could be easier for users to spot opportunities to work on the project.

example:

"id": "587d7b89367417b2b2512b48",
"title": "Use the Spread Operator",
"description": [
"ES6 introduces the <dfn>spread operator</dfn>, which allows us to expand arrays and other expressions in places where multiple parameters or elements are expected.",
"The ES5 code below uses <code>apply()</code> to compute the maximum value in an array:",
"<blockquote>var arr = [6, 89, 3, 45];<br>var maximus = Math.max.apply(null, arr); // returns 89</blockquote>",
"We had to use <code>Math.max.apply(null, arr)</code> because <code>Math.max(arr)</code> returns <code>NaN</code>. <code>Math.max()</code> expects comma-separated arguments, but not an array.",
"The spread operator makes this syntax much better to read and maintain.",
"<blockquote>const arr = [6, 89, 3, 45];<br>const maximus = Math.max(...arr); // returns 89</blockquote>",
"<code>...arr</code> returns an unpacked array. In other words, it <em>spreads</em> the array.",
"However, the spread operator only works in-place, like in an argument to a function or in an array literal. The following code will not work:",
"<blockquote>const spreaded = ...arr; // will throw a syntax error</blockquote>",
"<hr>",
"Copy all contents of <code>arr1</code> into another array <code>arr2</code> using the spread operator."
],
"challengeSeed": [
"const arr1 = ['JAN', 'FEB', 'MAR', 'APR', 'MAY'];",
"const arr2 = [];",
"// change code below this line",
"// change code above this line",
"arr1.push('JUN');",
"console.log(arr2); // arr2 should not be affected"
],
"tests": [
"// Test arr2 is correct copy of arr1",
"// Test arr1 has changed",
"// Test spread operator was used"
]
Issue 1:
Issue originally made by @bergus

Bug information

Babel version: v6.x (babel.io/repl)

Options

plain preset es-2015, nothing else

Input code

"use strict";
function foo1() {
for (let bar = 2; bar < 3; bar++) {
let bar = 4;
}
}
function foo2() {
var bar;
for (let bar = 2; bar < 3; bar++) {
let bar = 4;
}
}

[[ https://babeljs.io/repl/#?evaluate=true&lineWrap=false&presets=es2015&code="use%20strict"%3Bfunction%20foo1()%20{%20%20for%20(let%20bar%20%3D%202%3B%20bar%20<%203%3B%20bar%2B%2B)%20{%20%20%20%20let%20bar%20%3D%204%3B%20%20}}function%20foo2()%20{%20%20var%20bar%3B%20%20for%20(let%20bar%20%3D%202%3B%20bar%20<%203%3B%20bar%2B%2B)%20{%20%20%20%20let%20bar%20%3D%204%3B%20%20}} | produces ]]

"use strict";

function foo1() {
for (var bar = 2; bar < 3; bar++) {
var bar = 4;
}
}
function foo2() {
var bar;
for (var bar = 2; bar < 3; bar++) {
var _bar = 4;
}
}

Description

In foo1 it should produce two different bar variables - the one in the body of the loop is block-scoped and not the same as the one created by the loop. See also http://stackoverflow.com/q/37855990/1048572

Now that might be a simple bug, but it's getting weird in foo2 where a function-level bar is introduced (both let and var and parameters reproduce this). Here the bar variables of the loop and the body are indeed separated as expected, but the one of the loop header collides with the function-scope one. This does usually work - as long as there is no let declaration in the loop body.

Issue 2:
Issue originally reported by @Faithree in babel/babel-preset-env#422

Somebody tell me how to do it? In addition to using polyfill
Issue 1:
I'm submitting a ... (check one with "x")

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

Expected/desired behavior

Reposted from router v3 repo via @choeller

With the deprecated Router it was possible to add additional data to a Route-Configuration like this:

@RouteConfig([

{path: '/about', component: AboutComponent, name: 'About', data: {title :"About us"}},

])

with this information it was possible to do some generic operations when activating the route (e.g. setting the page title via Title-Service. It would be cool to have this possibility again.

Reproduction of the problem

If the current behavior is a bug or you can illustrate your feature request better with an example, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?

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

Please tell us about your environment:

Angular version: 2.0.0-rc.X

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]

Issue 2:
I'm submitting a ... (check one with "x")

[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

Try creating a ngFor look in a component template with an invalid statement (in this case the prefixed let token is missing):

<div *ngFor="item of items" class="item">
{{ item }}
</div>

Expected behavior

It would be nice to have a clear error message that informs the user that the ngFor expression is invalid, instead of something like this:

Error: Template parse errors:
Can't bind to 'ngFor' since it isn't a known property of 'div'. ("
<div [ERROR ->]*ngFor="item of items" class="item">
{{ item }}
</div>

Minimal reproduction of the problem with instructions

Just follow the steps above.

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

NgFor is the most important templating feature in Angular and it looks like this error can show up quite a bit. Let's make this easier on the user.

Please tell us about your environment:

Works anywhere. This is in the angular/angular project.

Angular version: 2.0.X

4.0.0

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Chrome (running on Karma).

Language: [all | TypeScript X.X | ES6/7 | ES5]

TS

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

This is running in runtime. Not sure how this looks post AOT.
Issue 1:
Electron version:

Electron 1.3.0

Operating system:

Windows 7 - Windows 10

Issue:

After the new so far not officially released Brave version has included that update towards Electron 1.3.0 there are rendering glitches/tearing effects when scrolling down with deactivated hardware acceleration. There are also some when activating it, but so far deactivating hardware acceleration has removed that white lines/glitches/tearings when scrolling.

This is no longer the case after that update to Electron 1.3.0

Can be avoided in other Chromium based browsers that deactivating smooth scrolling is used, which is missing in Electron. You plan to add that option? Problem is that Google will also remove that feature at one point from the flags, could you find a way to keep that in Electron somehow then?

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

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

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

Issue Details

Electron Version:

6.0.9

Operating System:

window7

Nodejs version:

12.10.0

Expected Behavior

boot the app normal

Actual Behavior

black screen on started
Issue 1:
I get this error:

src/lib.rs:57:7: 57:10 warning: unused variable: `enc`, #[warn(unused_variables)] on by default
src/lib.rs:57 let enc = EncodingOverride::lookup("ascii".as_bytes());
^~~
rustc: /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/llvm/lib/CodeGen/LexicalScopes.cpp:179: llvm::LexicalScope* llvm::LexicalScopes::getOrCreateRegularScope(llvm::MDNode*): Assertion `DISubprogram(Scope).describes(MF->getFunction())' failed.
Could not compile `rust_url_capi`.

It seems to be a compiler bug.

It occurs at this line, since commenting it seems to fix the problem:

https://github.com/valenting/rust-url-capi/blob/64c0a049bbffdb2676d39e0bc97ba0c5abb66ba6/src/lib.rs#L57

My guess is that the problem occurs because from rust_url_capi lib.rs:57-> rust-url encoding.rs:44 -> rust-encoding label.rs:13

Issue 2:
STR

#![crate_type = "staticlib"]
#![feature(core)]
#![feature(lang_items)]
#![feature(no_std)]
#![no_std]

extern crate core;

mod lang_items {
use core::fmt::Arguments;

#[lang = "stack_exhausted"]
extern "C" fn stack_exhausted() { }

#[lang = "eh_personality"]
extern "C" fn eh_personality() { }

#[lang = "panic_fmt"]
fn panic_fmt(_: &Arguments, _: &(&'static str, usize)) -> ! {
loop {}
}
}

pub enum Input {
Floating,
}

pub mod low {
use super::Mode;

pub enum Pin {
_0,
}

pub struct Cr(u32);

impl Cr {
pub fn set(&mut self, pin: Pin, mode: Mode) {
self.0 |= mode.value() << (4 * pin as u8)
}
}
}

pub mod high {
use super::Mode;

pub enum Pin {
_8,
}

pub struct Cr(u32);

impl Cr {
pub fn set(&mut self, pin: Pin, mode: Mode) {
self.0 |= mode.value() << (4 * pin as u8)
}
}
}

pub enum Mode { Input(Input) }

impl Mode {
fn value(&self) -> u32 {
match *self {
Mode::Input(Input::Floating) => 4,
}
}
}

Output

rustc: /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/llvm/lib/CodeGen/LexicalScopes.cpp:179: llvm::LexicalScope* llvm::LexicalScopes::getOrCreateRegularScope(llvm::MDNode*): Assertion `DISubprogram(Scope).describes(MF->getFunction())' failed.

cc @michaelwoerister Same error message as #17677, but I don't know if it's the same bug, this one needs -O.
Issue 1:
Hi,

We use Visual Studio 2013 Premium Update 4 and develop applications in TypeScript 1.4. We have a very serious issue, when we start debugging the code, entering into another method in another class would freeze the whole Visual Studio. It is then stalled for at least few minutes. The only way to quickly work with the Visual Studio again is by terminating the Visual Studio process from the task manager and restart the application again.

Any ideas on how to solve this issue? Thanks in advance.

By the way, I posted the same thing in CodePlex, I received a reply asking me to use GitHub instead. Reference link: https://typescript.codeplex.com/workitem/2657

Thanks again.

Issue 2:
I've been using TypeScript successfully in my project for a while now (love it!), but after making some changes to my code recently I've run into an issue where Visual Studio now hangs whenever I step into a function while debugging. I won't claim that my changes were bug-free, but bringing Visual Studio to a full stop doesn't seem like something my changes should have caused. Also, I continue to see this behavior after reverting those recent changes to a point where I'm certain things were still working fine with TypeScript.

I'm running Visual Studio Ultimate 2013 Update 4 and I did a repair installation on it while struggling with this problem. I originally was using TypeScript v1.0 but upgraded to v1.4 in hopes it would solve the problem, but it did not. I'd be happy to provide logs and traces and so forth if someone can tell me where to find them.
Issue 1:
Environment

Microsoft Windows [Version 10.0.18362.295]

Any other software?

Not applicable

Steps to reproduce

Open multiple tabs

Expected behavior

As the number of tabs increase, I would expect the tab bar to behave like tabs from a web browser: the size of the tab would shrink in order to make space for the newly created tab.

If the above doesn't happen, I would expect a setting that would limit how much text is displayed in a particular tab, so that one long tab doesn't take the entire tab bar real-estate.

Actual behavior

Tabs do not shrink nor is the text in one tab limited, causing one tab with a lot of text to take up the entire tab bar real estate.

The new tabTitle setting does not fix this issue, since long tab bars are created by the shell writing to them (such as a Razzle build environment).

Issue 2:
Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.18362.86]

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

In conhost or Windows Terminal, using both Vim.exe and WSL Vim, background color rendering becomes broken if a background color >16 or true colors is used.

With an example file, e.g. https://github.com/GilbertsHub/web-utils/blob/master/cgibinIntercept.sh:

vim -u NONE cgibinIntercept.sh +"hi Normal ctermbg=17" # for Windows: +"set t_Co=256"
# scroll down with CTRL-D

In general it is much easier to reproduce in WSL than Vim.exe, because it doesn't seem to occur after the initial scroll on Vim.exe and the effects are a bit different as described below. I can reproduce with any combination of conhost/terminal and Vim 8.1.883 on Ubuntu/8.0 on Debian/8.1 on Win32. Does not reproduce with neovim (v0.4.0-430-g8698830cb).

A few cases of example behavior:

Debian with conhost, Vim from official repository

$ sudo apt install vim
$ vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Sep 30 2017 18:21:38)
Included patches: 1-197, 322, 377-378, 550, 703, 706-707

Same behavior in the new terminal.

Vim.exe on conhost cmd.exe installed from https://github.com/vim/vim-win32-installer/releases/download/v8.1.1099/gvim_8.1.1099_x64.exe

Background color is wrong on the text part but correct otherwise (purple, although this seems to depend on active colorscheme) but is fixed after a Ctrl-L redraw.

Vim.exe on Terminal cmd.exe, same as above

Background color is again wrong, but the background highlight completely disappears after a Ctrl-L redraw.

What's wrong / what should be happening instead:

Background rendered the whole width of the window, e.g. in wsltty:

The effect is very similar to the issue #375, however that one happens with bg color set to <16 (darkBlue). However I cannot reproduce that issue anymore, including the terminal bg change.

The issues for Win32 and Linux versions might be separate, since their effects are pretty different as described above.

I also haven't been able to reproduce this using VT sequences, but I hope the bug report is still useful.
Issue 1:
Original

@dec
export class C {
}

Expected

var C = (function () {
function C() {
}
return C;
}());
C = __decorate([
dec
], C);
exports.C = C;

Actual

exports.C = (function () {
function C() {
}
return C;
}());
C = __decorate([
dec
], C);

decoratorOnClass2

Issue 2:
Expected:

var MyClass = (function () {
function MyClass(db) {
this.db = db;
this.db.doSomething();
}
return MyClass;
}());
MyClass = __decorate([
someDecorator,
__metadata("design:paramtypes", [db_1.db])
], MyClass);
exports.MyClass = MyClass;

Actual:

var MyClass = (function () {
function MyClass(db) {
this.db = db;
this.db.doSomething();
}
return MyClass;
}());
MyClass = __decorate([
someDecorator,
__metadata("design:paramtypes", [db_1.db])
], MyClass);

Failed tests:

tests/cases/compiler/decoratorMetadataWithImportDeclarationNameCollision2.ts

decoratorOnClass2
Issue 1:
The link to the 1.3.1 pdf documentation on docs.julialang.org is broken.

https://raw.githubusercontent.com/JuliaLang/docs.julialang.org/assets/julia-1.3.1.pdf

Issue 2:
The PDF document is invalid:

https://raw.githubusercontent.com/JuliaLang/docs.julialang.org/assets/julia-1.3.0.pdf

and the link is found here:

https://docs.julialang.org/en/v1.3/
Issue 1:
ISSUE TYPE

Bug Report

COMPONENT NAME

core

ANSIBLE VERSION

ansible 2.1.1.0
config file =
configured module search path = Default w/o overrides

CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

We recently had a change submitted to the triple-quickstart project

that contained the following code:

- name: Rebuild inventory
hosts: localhost
roles:
- rebuild-inventory
tags:
- provision
# check the target virthost distro for RHEL or CentOS
hosts: virthost
roles:
- provision/support_check
tags:
- provision

Note that the second task list is missing the YAML list marker; it

should look like this:

- hosts: virthost
roles:
- provision/support_check
tags:
- provision

This is a clear error, but it passes through the YAML parser with only

the following warning:

[WARNING]: While constructing a mapping from /home/lars/src/tripleo-
quickstart/playbooks/provision.yml, line 21, column 3, found a
duplicate dict key (roles). Using last defined value only.

STEPS TO REPRODUCE

(see above playbook samples)

EXPECTED RESULTS

Since duplicate keys are in fact not possible, I would expect Ansible

to abort with an error at this point.

ACTUAL RESULTS

Ansible ignores the error and continues on its merry way.

Because this warning comes from deep within the parser, it's not even

possible for something like ansible-lint to catch the problem,

either.

ADDITIONAL COMMENTARY

This is, oddly enough, the exact opposite of #13603.

Issue 2:
The unarchive module supports --diff for tar.gz files, which is great. Unfortunately this always fails when specifying a sudo_user for the task, since tar reports an altered uid/gid.
Issue 1:
After upgrading to atom 0.175.0 this morning, the x button is no longer present in the tab header (on hover or otherwise).

Looking in the inspector, the close-icon div is present, but nothing is inside it, nor is any CSS rule causing an 'x' to be rendered.

<li is="tabs-tab" class="tab sortable" data-original-title="" title="">
<div class="title" data-name="app-main.js" data-path="/src/app-main.js">app-main.js</div>
<div class="close-icon"></div>
</li>

I am running Ubuntu 14.04.

Issue 2:
I just upgraded to 0.174.0 from 0.172.0 today using Webupd8's PPA.

The 'x' button in each tab seems to be missing, and it therefore makes closing tabs much more difficult (now you have to right-click the tab you want to close and click Close Tab).

Replicated on Ubuntu 14.10, Atom 0.174.0, safe mode. I don't think a picture is needed, but if you want one, just tell me.