WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Apache Airflow version

Other Airflow 2 version (please specify below)

What happened

I have a three node airflow cluster, after upgrade 2.6.0 from 2.3.4, task can't show log in webui. and when task in running state, i can see log in webui, however, after task is failed or sucess, task log is gone, only left hostname.

by the way, airflow webserver、woker、scheduler process don't have error log.

master node get logs requese is fine:

and, use api get logs, have same issue:

upgrade steps:

step-1

AIRFLOW_VERSION=2.6.0

PYTHON_VERSION="$(python3 --version | cut -d " " -f 2 | cut -d "." -f 1-2)"

pip3 install "apache-airflow==${AIRFLOW_VERSION}" --upgrade --constraint /home/airflow/deploy/upgrade/up_to_2_6_0/constraints-3.9.txt

step-2

kill worker process

upgrade db

airflow db upgrade

What you think should happen instead

No response

How to reproduce

upgrade 2.6.0 from 2.3.4

Operating System

centos7.6

Versions of Apache Airflow Providers

2.6.0

Deployment

Other

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct

Issue 2:
Description

The old documentation for First time contributor's should be reviewed and incorporated in Apache Airflow Blog

Use case / motivation

To remove documentation duplication and clean it up.

Related Issues

#10178
Issue 1:
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: 12.0.0-beta.11 and higher

Operating System: macOS 10.15 and 11.0

Last Known Working Electron version: 12.0.0-beta.10

Testcase:

mainWindow = new BrowserWindow({
width: 800,
height: 600,
webPreferences: {
nodeIntegration: true
},
titleBarStyle: 'hidden'
})

Working behavior (in beta 10 and lower):

Broken behavior (in beta 11):

#26960 looks related?

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:

12.0.0-beta.14

Operating System:

macOS 11.0.1

Last Known Working Electron version:

11.1.1

Expected Behavior

The fullscreen button should be enabled and work, see this image from electron 11.1.1

Actual Behavior

The fullscreen button is disabled and does not work, see this image from electron 12.0.0-beta.14.

To Reproduce

Simply take any project and update to Electron 12.0.0-beta.14
Issue 1:
When outputting debugger keywords in my code and connecting my IDE to the node debugger it is breaking in the compiled code, not the uncompiled code. Sourcemaps are stripped from custom codes/pages/etc.

The commons.js and main.js files follow the sourcemaps settings (devtool: cheap-module-eval-source-map in webpack settings by default)

Could this be related with the custom babel setting that are used for node?

-> https://github.com/zeit/next.js/blob/v3-beta/server/build/webpack.js#L205 🤔

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

Expected Behavior

The compiled custom code in the .next/dist folder should have sourcemaps generated according to settings in webpack/babel.

Current Behavior

No sourcemaps are generated for custom code accessible for server side debugging. The sourcemaps are however accessible on client side.

Steps to Reproduce (for bugs)

Create a next.js project with a index.js page and sourcemaps enabled (at time of writing the default setting)

Run nextto start dev server

Open .next/dist/pages/index.js and scroll down to the bottom of the file. It will have no //# sourceMappingURL comment

Open .next/dist/main.js and scroll down to the bottom of the file. It will have a //# sourceMappingURL comment!

Issue 2:
Bug report

Describe the bug

viewport tag gets duplicated in the browser (there's no custom viewport tag provided).

To Reproduce

This occurs on our site, but I've noticed that nextns.org has the same issue, so the instructions are for it:

Go to https://nextjs.org

Wait for the page to load

Inspect the element tree

Search for "viewport", you'll see two occurrences

Expected behavior

There should only be one.

Screenshots

System information

OS: macOS

Browser (if applies): Chrome

Version of Next.js: 9.0.5
Issue 1:
Currently (as of TypeScript 0.9), TypeScript supports overloading on constants, but string constants only.

This seems like a slightly arbitrary restriction, although I do agree that strings are the most obvious case where this is necessary. I do think there is (at least) one more case that comes up frequently though: booleans.

Motivation

My current motiviating example for this is in Lodash's _.flatten function: https://lodash.com/docs#flatten

This takes a boolean 2nd argument; a flag which changes the behaviour of the method slightly. If true, it recursively flattens, and if false it only flattens a single level.

Lodash also has _.flatten / _.flattenDeep methods without boolean arguments that follow each of these behaviours respectively without the flag. While I think we can agree that generally using the different methods where possible is often better, this still gets a lot of use, and boolean flags for this sort of thing are pretty common generally.

Notably, these two (recursive/non-recursive) behaviours do have different type signatures, as you can see in the DefinitelyTyped definitions of all three different methods (https://github.com/borisyankov/DefinitelyTyped/blob/master/lodash/lodash.d.ts#L848-L881). The method with the boolean signature though has to be overly general to cover both cases, even though when the flag passed is constant we can easily be more specific at compile time.

Design

Exactly the same as for string constants (https://github.com/Microsoft/TypeScript/blob/master/doc/spec.md#3.9.2.4), but with true/false values.

See below for examples:

interface MyClass {
serialize(x: true): string;
serialize(x: false): number;
serialize(x: boolean): string | number;
}

var obj: MyClass;
var aBoolean: boolean = Math.random() >= 0.5;

// Valid:
var x: string = obj.serialize(true);
var y: number = obj.serialize(false);
var z: string|number = obj.serialize(aBoolean);

// Not valid:
var a: number = obj.serialize(true);
var b: string = obj.serialize(false)

var c: number = obj.serialize(aBoolean);
var d: string = obj.serialize(aBoolean);

Issue 2:
For instance, in the following example where we declare the return type as an array type, we go from

function foo(): blah[] {/**/

to

function foo(): blah[]{
/**/

Notice the lack of whitespace between the blah[] and the {.
Issue 1:
Bug report

Describe the bug

If we use next/dynamic to import components in several files, we experience a flashing "loading..." text when the client mounts.

If we only import one place, it works fine.

It also works fine in development.

To Reproduce

Codesandbox example below shows that the One component flashes with "loading" text since it is imported twice, while the Two component does not flash, because it is only imported once.

Expected behavior

I expect the dynamic import to behave the same in development and production, as well as it not causing a flash when the client mounts.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

OS: macOS mojave

Browser: Chrome 69.0.3497.100

Version of Next.js: 7.0.2

Issue 2:
Bug report

Describe the bug

If we use next/dynamic to import components in several files, we experience a flashing "loading..." text when the client mounts.

If we only import one place, it works fine.

It also works fine in development.

To Reproduce

Codesandbox example below shows that the One component flashes with "loading" text since it is imported twice, while the Two component does not flash, because it is only imported once.

Expected behavior

I expect the dynamic import to behave the same in development and production, as well as it not causing a flash when the client mounts.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

OS: macOS mojave

Browser: Chrome 69.0.3497.100

Version of Next.js: 7.0.2
Issue 1:
Describe the issue:

In a very specific context, numpy incorrectly asserts that 0 + 1 == 2!

Reproduce the code example:

import numpy as np

# only works in fresh interpreter, possibly uninitialized variable?
assert np.add(0., 1, where=False) == 2.
assert np.add(0., 1, where=False) == 1.
assert np.add(0., 1, where=False) == 1.

Error message:

No response

NumPy/Python version information:

1.21.2 3.9.5 (default, Jun 26 2021, 07:40:15)
[GCC 6.3.0 20170516]

Then I upgraded numpy to

1.22.4 3.9.5 (default, Jun 26 2021, 07:40:15)
[GCC 6.3.0 20170516]

and the problem persists.

Issue 2:
First of all, thank you so much for the work on Numpy--an incredible contribution to science and progress.

Reproducing code example:

Numpy has excellent support for functional programming patterns, and the hundreds of np.* functions I regularly use act as pure functions with no side effects.

The current behavior of np.negative breaks this pattern, and is not deterministic:

>>> import numpy as np
>>> np.negative(np.arange(5), where=np.array([0,0,1,1,0],dtype=bool))
array([ 94871006724704, 171798691860, -2,
-3, 4285579895102272626])
>>> np.negative(np.arange(5), where=np.array([0,0,1,1,0],dtype=bool))
array([ 94871006750048, 140541164903200, -2, -3,
48])
>>> x = np.arange(5)
>>> np.negative(x,out=x, where=np.array([0,0,1,1,0],dtype=bool))
array([ 0, 1, -2, -3, 4])

Thus, np.negative does not act as a mathematical function, which is confusing and error-prone. It's hard to imagine that a user would ever want uninitialized values in the returned values.

A quick search on github reveals that there are thousands (if not hundreds of thousands) of instances where code introduces uninitialized values due to calls to np.negative: https://github.com/search?q=%22np.negative%22&type=Code

Based on reading #7158, I believe this issue applies to all ufunc. I understand in #11086 that the documentation was improved, but I wanted to open this issue to highlight both the danger of uninitialized values being returned, as well as how frequently in the wild these uninitialized values are silently corrupting data.

Numpy/Python version information:

>>> import sys, numpy; print(numpy.__version__, sys.version)
1.19.1 3.8.5 (default, Aug 5 2020, 08:36:46)
[GCC 7.3.0]

(Edit) Proposed default behavior

>>> def wrapped_negative(x, out=None, where=True):
... if (out is None):
... temp = x[()]
... else:
... temp = out
... return np.negative(x, out=temp, where=where)
>>> wrapped_negative(np.arange(5), where=np.array([0,0,1,1,0],dtype=bool))
array([ 0, 1, -2, -3, 4])
Issue 1:
Challenge Steamroller has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

var result = [];
function steamrollArray(arr) {
// I'm a steamroller, baby
for(var i = 0; i<arr.length; i++)
{
if(Array.isArray(arr[i]))
{
steamrollArray(arr[i]);
}
else if(!Array.isArray(arr[i]) && arr[i] !== null)
{
result.push(arr[i]);
}
}
return result;
}

steamrollArray([1, {}, [3, [[4]]]]);

Issue 2:
Challenge Name

Mainly JavaScript challenges

Issue Description

We've had many coding issues made on GitHub (a list of some from the past few months: #9532, #9137, #9118, #8940, #9058, #8436, #8266, #8156, #8092 [comment within this issue], #7655, #7441, #7629, #7470, #7453, #7442, #5290, #4819, #4733, #4686, #4187, #3755, #1345) on why their code doesn't work, which turn out to be because they have a global variable they mutate with their function.

Proposed Fix (Updated)

Somewhere early in the JavaScript challenges have a note on how the tests work, in that they will only run your function and any global variables mutated in the process will keep their state.

Detect unsafe global variable code and wrap them in isolated blocked scope.

Display a notification in such cases if applicable and tests fail to run.

cc/ @freeCodeCamp/moderators
Issue 1:
When displaying an image with matshow, the values x,y of the cursor position is displayed. It would be useful to also display the value of the array at this position (tuple for RGB image with imshow).

Issue 2:
In Matlab, imshow pets you see the data value under the mouse cursor. This would be helpful in Matplotlib. I'm thinking it would go at to bottom of the window where the mouse-position text is.

This seems like it should be easy to add. I'm just not sure where I need to look to add it. If someone can tell me where to look, I'll take a stab at it. Where is the code that does the x=, y= text?
Issue 1:
When selecting a new 'Canvas zone' I should, as a user, click on 'edit layout'. However, I am able to click on 'Apply'. The screen closes, but nothing happens and the zone is never created.

Additionally, the 'create new layout' button is visualized as a zone itself.

Would make more sense to have this as an action button that will create the zone and takes you to the Canvas zone editor directly.

cc @enricogior

Issue 2:
If no custom layout exists the entry "create new custom" could be automatically selected.

And instead of the button 'Apply' the button 'Edit selected layout' should be selected.

Expected behavior

If I switch to "custom Layouts" and there is no Layout exists, the entry "create new custom" is selected. That indicates that clicking on "edit selected Layout" creates a new one.

Without existing custom layout or when the item "create new custom" is selected the button Apply shouldn't work. Instead only the button Edit selected layout should be selected and should working.

Actual behavior

The entry "create new custom" is not selected. But I can create a new Layout while only clicking at "Edit selected layout".

It also makes no sense, that in this situation the button Apply is selected and works!
Issue 1:
If I run a test with

shuffle(np.arange(10), random_state=0)

I will get a different result when another test was run before.

it is more complicated...

Issue 2:
When I run

nosetests sklearn

everything looks fine, If I do

nosetests sklearn/svm/tests/

I get an error in test_sparse.py, but when I do

nosetests sklearn/svm/tests/test_sparse.py

I get no error.

I guess this has something to do with the shuffling of the dataset or other random things.

I thought the way it is written the shuffling is done once and for all for all the tests so I don't really understand how this can happen. Any ideas?
Issue 1:
Hi, i have example of own defined hook which returns always memorized callback setValue:

Problem

const [value, setValue] = useAppState( ... );

Then setValue used in hook which required deps, for example useEffect:

useEffect(() => {
if (value != 'a') {
setValue('a');
}
}, [value]);

But unlike 'useState' this generates an error:

I am found source which contain function to check this here:

https://github.com/facebook/react/blob/9198a5cec0936a21a5ba194a22fcbac03eba5d1d/packages/eslint-plugin-react-hooks/src/ExhaustiveDeps.js

Suggestion

Add configuration options to set own hooks to be handled as out of the box

Issue 2:
Right now only useRef and other first-party hooks are allowed to return a stable result that is not required to be listed in the dependencies array of other hooks.

We have the react-hooks/exhaustive-deps' additionalHooks option to specify additional hooks that take dependencies arrays, but we don't have a way to describe a hook that returns a stable result.

An example of such hook could be:

const useLatest = (value) => {
const ref = useRef(value);
ref.current = value;
return ref;
};

It would be extremely useful being able to define custom hooks like this with a rule that could look like the following:

"react-hooks/exhaustive-deps": [
"warn",
{
"stableKnownHookValues": "(useLatest|useSomethingElse)"
}
]

I'd be willing to work on a PR if this idea is deemed useful.
Issue 1:
Model description

Hi,

My name is Alexander, I am writing to you on behalf of Silero, a company maintaining our project silero-models.

We noticed that our models are rehosted here - https://huggingface.co/spaces/pytorch/silero_tts or here https://huggingface.co/spaces?search=silero.

We did not explicitly grant Hugging Face, Inc. any sort of permission to rehost, relicense and profit from our work and models.

Moreover it openly disregards our CC BY-NC-SA license.

Please immediately remove any of our models from your website and / or any of your resources.

Best,

Alexander

Open source status

The model implementation is available

The model weights are available

Provide useful links for the implementation

No response

Issue 2:
Hi,

My name is Alexander, I am writing to you on behalf of Silero, a company maintaining our project silero-models.

We noticed that our models are hosted here - https://huggingface.co/spaces/pytorch/silero_tts or here https://huggingface.co/spaces?search=silero.

We did not explicitly grant Hugging Face, Inc. any sort of permission to rehost, relicense and profit from our work and models.

Moreover it openly disregards our CC BY-NC-SA license.

Please immediately remove any of our models from your website and / or any of your resources.

Best,

Alexander
Issue 1:
On Elasticsearch 1.2.1, running the command

PUT /vd-rsa-2014-06-10-17/_settings
{
"index" : {
"cache.filter.expire" : "5m"
}
}

returns:

{
"error": "ElasticsearchIllegalArgumentException[Can't update non dynamic settings[[index.cache.filter.expire]] for open indices[[vd-rsa-2014-06-10-17]]]",
"status": 400
}

This should have worked, according to the documentation on the site and #874

Issue 2:
On Elasticsearch 1.2.1, running the command

PUT /vd-rsa-2014-06-10-17/_settings

{

"index" : {

"cache.filter.expire" : "5m"

}

}

gives mes:

{

"error": "ElasticsearchIllegalArgumentException[Can't update non dynamic settings[[index.cache.filter.expire]] for open indices[[vd-rsa-2014-06-10-17]]]",

"status": 400

}

This should have worked, according to the documentation on the site and #874
Issue 1:
I tried using "keyboard.press(control+shift+k)" in the msedge browser to Duplicate Browser Tabs in the same state, but it gave an error.

so Is there any way to Duplicate Browser Tabs. thanks.

Issue 2:
System info

Playwright Version: [v1.33.0]

Operating System: [All, Windows 11, Ubuntu 20, macOS 13.2, etc.]

Browser: [All, Chromium, Firefox, WebKit]

Other info:

Source code

I provided exact source code that allows reproducing the issue locally.

Link to the GitHub repository with the repro

[/pull/23158]

Expected

10 files of 50MB or 30MB should be added to input

Actual

files are not added to input
Issue 1:
Code Sample, a copy-pastable example if possible

data_frame.groupby(pd.TimeGrouper('D', convention='start', key=time_column)).count()
data_frame.groupby([pd.TimeGrouper('D', convention='start', key=time_column)]).count()

give below two different outputs

location price profit type
time
2017-07-23 1 1 1 1
2017-07-24 0 0 0 0
2017-07-25 1 1 1 1
2017-07-26 1 1 1 1
2017-07-27 3 3 3 3
2017-07-28 6 6 6 6

location price profit type
time
2017-07-23 1 1 1 1
2017-07-25 1 1 1 1
2017-07-26 1 1 1 1
2017-07-27 3 3 3 3
2017-07-28 6 6 6 6

Problem description

The origin data frame doesn't contain a record in 2017-07-24, you can see if I use time grouper with convention='start' lonely, the 2017-07-24 item has been filled, but if by group list, that item hasn't been filled

Output of pd.show_versions()

INSTALLED VERSIONS

commit: None

python: 2.7.10.final.0

python-bits: 64

OS: Darwin

OS-release: 16.7.0

machine: x86_64

processor: i386

byteorder: little

LC_ALL: None

LANG: None

LOCALE: None.None

pandas: 0.20.3

pytest: None

pip: 9.0.1

setuptools: 36.2.0

Cython: None

numpy: 1.13.1

scipy: 0.19.1

xarray: None

IPython: None

sphinx: None

patsy: None

dateutil: 2.6.1

pytz: 2017.2

blosc: None

bottleneck: None

tables: None

numexpr: None

feather: None

matplotlib: None

openpyxl: None

xlrd: None

xlwt: None

xlsxwriter: None

lxml: None

bs4: None

html5lib: 0.9999999

sqlalchemy: None

pymysql: None

psycopg2: None

jinja2: None

s3fs: None

pandas_gbq: None

pandas_datareader: None

Issue 2:
Code Sample

>>> df.groupby(pd.Grouper(freq='H')).agg({'value': 'mean'})
timestamp delta_t
2016-06-07 00:00:00 2.729111e+11
2016-06-07 01:00:00 NaN
2016-06-07 02:00:00 NaN
2016-06-07 03:00:00 NaN
2016-06-07 04:00:00 NaN
...

>>> df.groupby([pd.Grouper(freq='H')]).agg({'value': 'mean'})
timestamp delta_t
2016-06-07 2.729111e+11
2016-07-07 2.509444e+11
2016-07-13 2.775778e+11
2016-07-15 2.490556e+11
2016-07-16 2.676190e+11

Problem description

This is an inconsistent behavior, and there is no mention to this on groupby or Grouper documentation.

Expected Output

>>> df.groupby([pd.Grouper(freq='H')]).agg({'value': 'mean'})
timestamp delta_t
2016-06-07 00:00:00 2.729111e+11
2016-06-07 01:00:00 NaN
2016-06-07 02:00:00 NaN
2016-06-07 03:00:00 NaN
2016-06-07 04:00:00 NaN

Output of pd.show_versions()

pandas: 0.20.2
pytest: 3.1.1
pip: 9.0.1
setuptools: 27.2.0
Cython: 0.25.2
numpy: 1.12.1
scipy: 0.19.0
xarray: 0.9.6
IPython: 6.1.0
sphinx: 1.5.6
patsy: 0.4.1
dateutil: 2.6.0
pytz: 2017.2
blosc: None
bottleneck: 1.2.1
tables: 3.3.0
numexpr: 2.6.2
feather: None
matplotlib: 2.0.2
openpyxl: 2.4.7
xlrd: 1.0.0
xlwt: 1.2.0
xlsxwriter: 0.9.6
lxml: 3.8.0
bs4: 4.6.0
html5lib: 0.999
sqlalchemy: 1.1.10
pymysql: None
psycopg2: None
jinja2: 2.9.6
s3fs: None
pandas_gbq: None
pandas_datareader: None
Issue 1:
Bug report

What is the current behavior?

When I click the button to lazy-load a module which was already been prefetched (I can see it in the network tab), another network request for the same module is done.

If the current behavior is a bug, please provide the steps to reproduce.

Minimal repository: test-webpack-dynamic-import-prefetch

What is the expected behavior?

If the button is clicked that lazy-module should be called from the browser's cache without additional network request.

Other relevant information:

webpack version: 4.18

Node.js version: 8.11

Operating System: Windows 10

Additional tools: Chrome 69

Issue 2:
I want to use webpack to bundle unit tests in the test-folder. Therefore I want to search the test-folder for js-files and add these files to the bundle created by webpack. Is it possible to add multiple entry points like .addEntry() in browserify?