WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Hello,

The description of some of the commands on the list are too long. This makes them difficult to read.

I think that some text should be moved to descriptions of individual commands e.g. `airflow days backfill --help. We currently do not have descriptions for individual commands. After executing the --help '' command, we only have a list of arguments.

After making changes it may look like the screen below.

Descriptions can be set by the parameters description or epilogue.

airflow/airflow/cli/cli_parser.py

Lines 1280 to 1282
in
8517cb1

sub_proc = subparsers.add_parser(

sub.name, help=sub.help

)

sub_proc = subparsers.add_parser(
- sub.name, help=sub.help
+ sub.name, help=sub.help, description="DESCRIPTION", epilog="EPILOG"
)

I would be happy if all the commands had a description. It may duplicate the description from the list.

Issue 2:
Description

I think adding the following operators/sensors would benefit companies that need to start/stop RDS instances programmatically.

Name
Description
PR

RdsStartDbOperator
Start an instance, and optionally wait for it enter "available" state
#27076

RdsStopDbOperator
Start an instance, and optionally wait for it to enter "stopped" state
#27076

RdsDbSensor
Wait for the requested status (eg. available, stopped)
#26003

Is this something that would be accepted into the codebase?

Please let me know.

Use case/motivation

1. Saving money

RDS is expensive. To save money, a company keeps test/dev environment relational databases shutdown until it needs to use them. With Airflow, they can start a database instance before running a workload, then turn it off after the workload finishes (or errors).

2. Force RDS to stay shutdown

RDS automatically starts a database after 1 week of downtime. A company does not need this feature. They can create a DAG to continuously run the shutdown command on a list of databases instance ids stored in a Variable. The alternative is to create a shell script or login to the console and manually shutdown each database every week.

3. Making sure a database is running before scheduling workload

A company programmatically starts/stops its RDS instances. Before they run a workload, they want to make sure it's running. They can use a sensor to make sure a database is available before attempting to run any jobs that require access.

Also, during maintenance windows, RDS instances may be taken offline. Rather than tuning each DAG schedule to run outside of this window, a company can use a sensor to wait until the instance is available. (Yes, the availability check could also take place immediately before the maintenance window.)

Related issues

No response

Are you willing to submit a PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct
Issue 1:
Current Behavior:

The docs for npm@7 mention hook scripts as a feature:

If you want to run a specific script at a specific lifecycle event for ALL packages, then you can use a hook script.

Place an executable file at node_modules/.hooks/{eventname}...

^ https://github.com/npm/cli/blob/latest/docs/content/using-npm/scripts.md#hook-scripts

Expected Behavior:

This section should be removed from NPM docs since the hook script functionality no longer works. It appears to be no longer supported in npm@7, according to the @npmcli/run-script readme:

Hook scripts are not run by this module. If the caller wishes to run hook scripts, then they can override the default package script with an explicit cmd option pointing to the node_modules/.hook/${event} script.

^ https://github.com/npm/run-script#differences-from-npm-lifecycle

Steps To Reproduce:

n/a

Environment:

n/a

Issue 2:
First of all, thanks for all of the work being done on the npm CLI and the ecosystem! Tons of new amazing things in v7.

Current Behavior:

Hook scripts (documented in the docs here) seem to no longer get run for npm v7.

For example, an executable file at node_modules/.hooks/postinstall with the following contents not get run:

#!/usr/bin/env node
console.log('ran hook');

I also tried this:

#!/usr/bin/env bash
echo 'ran hook'

This will not get run during npm install or npm install <pkg name>

Expected Behavior:

The hook scripts should be run

Steps To Reproduce:

Create a new package with one of the file contents above in an executable file under node_modules/.hooks/postinstall

Run npm install

Hook script does not get run

Environment:

OS: macOS 11.2.1

Node: 15.8.0

npm: 7.5.4

Alternatives considered

Maybe Hook Scripts are no longer supported? In this case, they should be removed from the documentation.
Issue 1:
System info

Playwright Version: [v1.32.3]

Operating System: [macOS 12.6.5]

Browser: [Chromium]

Other info:

Source code

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

Link to the GitHub repository with the repro

Steps

npx playwright test --ui

Try to run the only existing test in the repro (hit play on the single test)

Notice errors in the console:

Error: TypeError: Cannot read properties of undefined (reading '_createTestResult')
at Be._onTestBegin (http://localhost:58924/trace/watch.575ca3b3.js:1:3028)
at Be.dispatch (http://localhost:58924/trace/watch.575ca3b3.js:1:1991)
at window.dispatch (http://localhost:58924/trace/watch.575ca3b3.js:3:296)
at eval (eval at evaluate (:195:30), <anonymous>:2:10)
at UtilityScript.evaluate (<anonymous>:197:17)
at UtilityScript.<anonymous> (<anonymous>:1:44)Error: TypeError: Cannot read properties of undefined (reading 'resultsMap')
at Be._onStepBegin (http://localhost:58924/trace/watch.575ca3b3.js:1:3534)
at Be.dispatch (http://localhost:58924/trace/watch.575ca3b3.js:1:2119)
at window.dispatch (http://localhost:58924/trace/watch.575ca3b3.js:3:296)
at eval (eval at evaluate (:195:30), <anonymous>:2:10)
at UtilityScript.evaluate (<anonymous>:197:17)
at UtilityScript.<anonymous> (<anonymous>:1:44)Error: TypeError: Cannot read properties of undefined (reading 'resultsMap')
// etc...

Run tests regularly: npx playwright test

Notice that tests run 5 times as expected and pass

Expected

Test should run

Actual

Test does not run, errors appear in console

Issue 2:
System info

Playwright Version: [v1.34.2]

Operating System: [macOS 13.2]

Browser: [WebKit]

Other info:

Source code

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

Link to the GitHub repository with the repro

https://github.com/ArrayZoneYour/playwright-screenshot

Steps

pnpm install

npm run test

npm run test:ui

Expected

[Describe expected behavior]

webkit screenshot is the same as it display under ui mode

Actual

[Describe actual behavior]

webkit screenshot rotateY is not worked as expected
Issue 1:
Challenge Name

Get set for our algorithm challenges

Issue Description

This isn't a challenge, it is just the overview/instruction page for basic-algorithm-scripting. It loads page 1/4 but the "Go to my next step" button is broken so you cannot navigate to pages 2, 3, and 4. You have to just skip to the first challenge. That means you don't get that satisfying green checkbox on the map.

Tested with Chrome and IE

Issue 2:
Expected Behavior: When I click "Go to my next step", I should go to my next step.

Current Behavior: When I click "Go to my next step", I stay on that page and nothing happens.

I have tried refreshing, clearing cache and history, re-logging in, but the current behavior has not changed.

Challenge Name

https://www.freecodecamp.com/challenges/get-set-for-our-front-end-development-projects

Issue Description

Click 'Map' in menu

When side map pops up, click 'basic-front-end-development-projects' under the Front End Dev

Click 'Get Set for our Front End Development Projects'

Click 'Go to my next step'

Nothing happens

Browser Information

Browser Name, Version: Google Chrome, Version 52.0.2743.116 (64-bit)

Operating System: Mac OS X El Capitan Version 10.11.6

Desktop (Web)

Screenshot
Issue 1:
A component in 2.0.0-alpha.45 with

template: `<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 100"></svg>`

arrives in the DOM as

<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 100 100" version="1.1"></svg>

Note the lower-case b of viewbox. That way, the SVG doesn't render correctly.

As a workaround, I'm using an ElementRef in the constructor to manually set the correct property.

Issue 2:
SVG elements inside templates are not visible with alpha.38. From what I can see, the browser is not recognizing the svg element.

Works in alpha.37: http://plnkr.co/edit/GOEp4DSa0Q3HGZGxXVAi

Breaks in alpha.38: http://plnkr.co/edit/thIhnOB9zhzIQeEnmZUA

import {bootstrap, bind, Component, View} from 'angular2/angular2';

@Component({
selector: 'app-cmp'
})
@View({
template: `
<div>
<svg fill="000000" width="24" height="24" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">
<path d="M9 16.2L4.8 12l-1.4 1.4L9 19 21 7l-1.4-1.4L9 16.2z"></path>
</svg>
</div>
`
})
class App {
constructor() {}
}

bootstrap(App);
Issue 1:
Hi!

I used the customizer to generate my own bootstrap 3 css files and using it to display a dialog with 'fade' in the class made the dialog background go black instead of 50% opacity black.

Inspecting the modal-backdrop I figured the .fade opacity: 1 attribute was overriding the .modal-backdrop opacity: 0.5 attribute.

Simply changing the order in which those classes show up in the bootstrap css fixed the problem.

I am attaching some pictures to show the problem.

Issue 2:
Hi!

I just generated a customized version and the modal background is totally black (I also generated a version without any change to be sure it wasn't me that caused that):

The download link on the home page does have transparency:
Issue 1:
We're missing some library copies, I'll have a look into it.

cc @brson

Issue 2:
http://buildbot.rust-lang.org/builders/master-mac/builds/94/steps/compile/logs/stdio

http://buildbot.rust-lang.org/builders/master-linux/builds/95/steps/compile/logs/stdio

These are configured something like ../configure --host-triples=x86_64-apple-darwin,i686-apple-darwin
Issue 1:
Font-family not being passed to SnackBar as expected.

Add a SnackBar component at the root of your project. Without any parent from which it will catch the font family, it goes to the serif default browser font.

Material-UI: Current

React: Current

Browser: Any

Issue 2:
Problem description

A <SnackBar> component added inside a <MuiThemeProvider> element displays with a bad font.

Steps to reproduce

Create a <Snackbar /> inside a document with no default styles in the body - just a <MuiThemeProvider> wrapper.

<MuiThemeProvider>
<div>
<Notification open={true} message="hello, world" autoHideDuration={10000}/>
</div>
</MuiThemeProvider>

Versions

Material-UI: 0.15.2

React: 15.2.1

Browser: Chrome 51

Images & references
Issue 1:
I'm see in docs inside SelectionControls an usage example of Switch with label, it's supposed to be used like:

<FormControlLabel
control={
<Switch
checked={this.state.checkedA}
onChange={(event, checked) => this.setState({ checkedA: checked })}
/>
}
label="A"
/>

But my state never changes. To fix it I did:

<FormControlLabel
control={
<Switch
checked={this.state.enableCache}
/>
}
label="Enable cache?"
onClick={() => this.setState({ enableCache: !this.state.enableCache })}
/>

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

Expected Behavior

When clicking it should change state

Current Behavior

State unchanged

Steps to Reproduce (for bugs)

Create a component with just a div

Add a initial state for that component with value true or false

Inside that div copy+paste this:

<FormControlLabel
control={
<Switch
checked={this.state.checkedA}
onChange={(event, checked) => this.setState({ checkedA: checked })}
/>
}
label="A"
/>

Your Environment

Tech
Version

Material-UI
1.0.0-beta.25

React
16.2.0

browser
Google Chrome

etc

Issue 2:
It would be a nice feature to not collapse a Collapse component all the way, but instead to collapse it to a height specified. This would allow for a small preview of the collapsable content.

There could be other ways to implement the same functionality.

Thanks for the consideration!

I have searched the issues of this repository and believe that this is not a duplicate.
Issue 1:
Since DCN make convolution networks gain a massive accuracy, it's that possible adding DCN inside pytorch natively?

Or does it already supported in somewhere in someway?

Issue 2:
🚀 Feature

Exactly as introduced in Microsoft paper : https://arxiv.org/pdf/1703.06211.pdf

Motivation

This operator has great advantages and abilities, and his popularity is increasing.

I don't think that any further explanation is needed.

BTW, other frameworks already have this operator, and I'm not talking about private people githubs..
Issue 1:
Superset returns an internal server error when there are duplicated calculated column names

Expected results

No 5xx

Actual results

5xx

Screenshots

How to reproduce the bug

While recently creating a new set of calculated columns I forgot to change the name from the default of for all the fields. While attempting to save this, I wound up getting an internal server error on the front end which mapped to a "Duplicate entry '-77284' for key 'uq_table_columns_column_name'" internally.

It would be nice if that exception was caught or a specific error message surfaced so that people knew what they did wrong.

Environment

superset version: master

python version: 3.6

node.js version: 8.6

Checklist

Make sure these boxes are checked 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.

Issue 2:
Make sure these boxes are checked before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if 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

Superset version

0.25.6

Expected results

Expected result in 0.17.6 is :

Actual results

Actual result which I am getting in 0.25.6 is :

Steps to reproduce

Open the slice and select the table view.

In the group by select any column with date as datatype

select any metric against it.

Output is epoch time against the metric
Issue 1:
When I try trace a model, I got this error:

TracedModules don't support parameter sharing between modules

After digging into jit module source codes, this error thrown for the reason that:

the module weights already inside a set, but id is different with exists one, then out performs this error

however, this message is confusing. I think it's nothing to do with parameters sharing, instead, it because of 2 modules or more with same weights but not same id.

I think the best way to indicates users to solve this, at least provide which layer or which modules conflicts with each other since they have same weights but not same id.

If you got same error when tracing a pytorch model. You should think about give my advise a 👍

Issue 2:
When tracing a model like this:

class BasicConv(nn.Module):

def __init__(self, in_planes, out_planes, kernel_size, stride=1, padding=0, dilation=1,
groups=1, relu=True, bn=True, bias=False):
super(BasicConv, self).__init__()
self.out_channels = out_planes
self.conv = nn.Conv2d(in_planes, out_planes, kernel_size=kernel_size,
stride=stride, padding=padding, dilation=dilation, groups=groups, bias=bias)
self.bn = nn.BatchNorm2d(out_planes, eps=1e-5, momentum=0.01, affine=True) if bn else None
self.relu = nn.ReLU(inplace=True) if relu else None

def forward(self, x):
x = self.conv(x)
if self.bn is not None:
x = self.bn(x)
if self.relu is not None:
x = self.relu(x)
return x

class FuckNet2(nn.Module):

def __init__(self):
super(FuckNet2, self).__init__()

self.welcome_layer = BasicConv(3, 256, 3, 1, 1)
self.block_1 = BasicConv(256, 256, 3, 1, 1)
self.fuck_layers = nn.Sequential()
for i in range(5):
self.fuck_layers.add_module('{}'.format(i), self.block_1)

def forward(self, x):
x = self.welcome_layer(x)
return self.fuck_layers(x)

I got error:

ValueError: TracedModules don't support parameter sharing between modules

Why does above net can not trace? In order to trace how should we write model ? I thought my written has no problem........

BTW, this error message has nothing to help, I think it would be better to indicates users where causes the parameters sharing.
Issue 1:
I'm submitting a ... (check one with "x")

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

If you have two CSS classes containing the same attribute (e.g. color) and apply them both to the same element with ngClass, the attribute value selected seems indeterministic.

Expected behavior

Applying CSS classes with the same attribute to an element with ngClass should use the duplicated elements in a known order.

Minimal reproduction of the problem with instructions

http://plnkr.co/OOMWOL

In the above Plnkr, I have two CSS styles, one red (colour: red) and one green (colour: green). Applying these styles to the same element, what colour should the text be?

When red is used first, followed by green, the text is red. When green is first, followed by red, the test is still green.

The expectations is that one style will take priority over another based on the order it is applied using ngClass.

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

Applying event based styles which override previous styles within an element.

Please tell us about your environment:

MacOS, Chrome, Opera

Angular version: 2.0.0

Browser: [all]

Issue 2:
I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request

Current behavior

Components added dynamically that have ChangeDetectionStrategy.OnPush do not detect input changes. For example, if such a component is instantiated at runtime via ViewContainerRef.createComponent, then setting an @Input property to a new immutable object does not trigger change detection. Instead, the component must be marked for check manually, with ChangeDetectorRef.markForCheck, rather than triggering change detection automatically.

Expected behavior

Setting an @Input property value on a dynamically created component that has OnPush change detection should automatically trigger a change detection run, following the same behavior as components created from a template.

Minimal reproduction of the problem with instructions

Plunker to demonstrate

The ChangeDetectionOnPushComponent does not detect the change to its @input property.

(Also related Stack Overflow question with markForCheck workaround.)

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

I believe this may be a bug because push change detection for dynamically created components behaves differently from static components, and is not what might be expected for ChangeDetectionStrategy.OnPush. My use case is an application that uses many dynamically created nested components that would benefit from lightweight on-push change detection.

Angular version: 2.0.X

2.4.4

Browser:

All

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

TypeScript 2.0.2
Issue 1:
The TypeScript definition for Array.filter specifies the callback must return a boolean, thus the code example at the bottom of this post fails to compile. Here's the current definition:

filter(callbackfn: (value: T, index: number, array: T[]) => boolean, thisArg?: any): T[];

The spec says this about the callback parameter:

callbackfn should be a function that accepts three arguments and returns a value that is coercible to the Boolean value true or false.

Thus I propose the definition should be changed to:

filter(callbackfn: (value: T, index: number, array: T[]) => any, thisArg?: any): T[];

Note: using a double not-operator is a sufficient workaround with negligible implications

TypeScript Version:

1.8.7

Code

Playground

// the purpose is to weed out falsey values
let a = [1, 2, 3, undefined, 0, 42, ""].filter(i => i)
// "i => i" is an error because it does not return boolean
// the following has no error
let b = [1, 2, 3, undefined, 0, 42, ""].filter(i => !!i)

Expected behavior:

No compile errors

Actual behavior:

Compile errors

Issue 2:
From here: https://typescript.codeplex.com/workitem/2464

I have a possible solution: Just allow this:

class A {
[index: number]: A; // <- since you can already do this
(...args): A; // <- why not allow this also?
constructor(...args) { }
}

Other suggestion by fdecampredon was:

class A {
(): string {
//do something
return 'hello world';
}
constructor(): A {
//do something else
}
}

could be transformed into that :

function A() {
if (!(this instanceof A)) {
//do something
return 'hello world';
} else {
//do something else
}
}
Issue 1:
ℹ Computer information

PowerToys version: 0.22.0

PowerToy Utility: Video Conference

Running PowerToys as Admin: Yes

Windows build number: [run "winver"] 19401.450

📝 Provide detailed reproduction steps (if any)

Use Video Conference in high resolution monitor

✔️ Expected result

Show correctly

What is the expected result of the above steps?

❌ Actual result

Shown in very small size

What is the actual result of the above steps?

📷 Screenshots

Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form

Issue 2:
📝 Provide a description of the new feature

I am on a 43" 4k monitor with Windows scaled to 150%. The Video Conference toolbar is quite small - see attachment. It might be nice if this was scalable.

I tested and it seems to not change size as you change scaling in Windows. I think it should at least follow scaling set in Windows, if not scalable separately.

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