WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Upon opening the collapsable element in Safari 7, after the opening animation completes the element quickly closes and opens up again. The closing animation also appears to not fire correctly; the element just closes without animating/with an accelerated animation. This is NOT an issue in version 3.0.3 and older.

This appears to be related to the height being set at "auto" at the end of the animation ("dimension", line 523 in unminified JS). Is there a reason this is being applied?

Issue 2:
I've searched the issues before submitting but did not find this issue reported.

This is using Bootstrap 3.0.0 and does not appear to be browser-dependent.

Steps to reproduce

Open this fiddle.

Click on "Toggle" to collapse the first column.

Click on "Toggle" to uncollapse the first column.

Expected behavior

The column should uncollapse to its original width.

Actual behavior

The column takes as much width as the browser will give it.

Observations

The problem is that $.collapse(), instead of just removing the CSS styling it added to the element to collapse it, forcibly sets the dimension of collapse to the scroll[Dimension] attribute of the element being collapse and then to "auto". This effectively overrides any styling that was previously done through the style attribute (which may be fair game) and styling done through the application of CSS stylesheets.

The fiddle gives a horizontal example but the issue is the same in either dimension. Also, while the fiddle uses the grid system, this happens whenever the CSS sets a specific dimension on the element which is to be collapsed and the collapsing is set to happen on this same dimension. So this is not a grid-dependent issue.

A quick edit of the boostrap.js file I have here shows that simply removing the dimension (width or height) from the CSS of the element is enough to get the expected behavior. What I've done is make show end with:

this.$element
.one($.support.transition.end, $.proxy(complete, this))
.emulateTransitionEnd(350)
this.$element.css(dimension, "")

And made the complete() function local to show not set the dimension to "auto".

I've used a workaround like this to at least get the original dimension back but this workaround makes the transition uneven:

jQuery("#collapse").on("shown.bs.collapse", function () { jQuery(this).css("width", ""); })
Issue 1:
Transferred from http://code.opencv.org/issues/2864

|| Mohammad Ishfaque Jahan Rafee on 2013-03-05 13:33
|| Priority: Low
|| Affected: None
|| Category: gpu (cuda)
|| Tracker: Feature
|| Difficulty: None
|| PR:
|| Platform: None / None

GPU module in Python

Wouldn't it be nice if GPU functions are available in Python bindings

History

Mohammad Ishfaque Jahan Rafee on 2013-03-05 13:37

Mohammad Ishfaque Jahan Rafee wrote:
> Wouldn't it be nice if GPU functions are available in Python bindings

I am a newbie. Sorry about duplicate post. I wanted to submit it as a feature request. But I can't find delete button anywhere.

Andrey Pavlenko on 2013-03-06 09:38

Anatoly, could you comment if it makes sense and if it's possible?
- Priority changed from Normal to Low
- Start date deleted (2013-03-05)
- Assignee set to Anatoly Baksheev
- Category set to gpu (cuda)
- Tracker changed from Bug to Feature

Issue 2:
System information (version)

OpenCV => '4.1.2' Python3

Operating System / Platform => Ubuntu 18.04

Detailed description

Expected result: it should work.

Actual result:

TypeError: Expected Ptrcv::UMat for argument '%s'

Steps to reproduce
Issue 1:
superset_tests_worker | Unable to load celery application.

superset_tests_worker | The module superset.tasks was not found.

Issue 2:
I connected superset with a local modify version of the superset-ui plugin legacy-country map but I got this viz:

I'm the the right geojson generated from the file downloaded from https://www.diva-gis.org/gdata with de ISO column updated to follow de ISO 3166-2 standard.

If someone help me solve this, I will make the corresponding PR!
Issue 1:
Original report at SourceForge, opened Wed Oct 7 13:51:02 2009

The documentation on mpl_toolkits.mplot3d.axes3d.Axes3D.scatter states:

Keyword arguments are passed on to

:func:~matplotlib.axes.Axes.scatter.

This does not seem to be the case (see attached code)

Note: I run Linux RedHat 5, python v2.6.2, with matplotlib v0.99.1.1 installed with backend = TkAgg

SourceForge History

On Mon Jan 4 19:16:57 2010, by heeres: assigned_to: 100

Issue 2:
There are a lot of *args, **kwargs signatures in the API. In many cases, they could be better described by explicit arguments/kw-arguments. This makes for a more clear API and reduces the chance of unintended misuse.

For example pyplot.delaxes

def delaxes(*args):
"""..."""
if not len(args):
ax = gca()
else:
ax = args[0]
...

would be more clear with

def delaxes(ax=None):
"""..."""
if ax is None:
ax = gca()
...

For all intended uses, the API compatibility is preserved. Unreasonable and possibly wrong uses like

delaxes(ax1, ax2) or delaxes(ax, mykwarg=True) would raise an Exception after the change. In itself, this is a benefit, because these cases will then be detected as false usage. However it may break existing programs.

Before I do any pull requests, is there a policy how to handle such cases?

Do you want to change these things, or should they be left as they are:

for cases like the above one where arguments are directly resolved in the function/method?

for cases where the all the arguments are passed like e.g. pyplot.savefig?

Which branch should changes go into?
Issue 1:
From @Thaina on March 22, 2016 3:42

Please allow /// <reference> to support online file

Copied from original issue: microsoft/vscode#4539

Issue 2:
Creating TypeScript files using build/runtime environments, like Node, Gulp, etc., I regularly find myself referencing public repositories.

Currently it looks like the /// <reference path="" /> syntax only allows for referencing local files (at least I couldn't find any information of IRIs being supported, and TSC claims File not Found error when using a DefinitelyTyped URL).

But this results in a requirement to deliver .d.ts files of public repositories along with the project and to keep their relative position in sync with locally generated .d.ts files. (See SetTrend/TS18N failing project for reference).

So I propose to allow to use IRIs for reference:

/// <reference path="https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/node/node.d.ts" />
Issue 1:
This issue is to suggest a new option to the SimpleImputer(): For the missing values in a given column A_j, one could replace by random draws from the present value from that same column j. In comparison to the existing imputation strategies in SimpleImputer(), such "informed" approach does i) preserve some of the randomness that is present in the column instead of replacing by a constant and ii) the filled-in values reflect the distribution of the values really existing in that column.

Cf. #11209

Issue 2:
The purpose would be to provide an unbiased, stochastic, univariate imputer. The imputer would replace missing values by values sampled uniformly at random from the non-missing values of the sample column.

This would require to add additional random_state constructor parameter to the class.

As for #11208 this strategy should work both on numerical and non-numerical dtypes.
Issue 1:
Context:

Playwright Version: 1.27.1

Operating System: Windows

Node.js version: 16.17.0, 18.8.0

Browser: All

Extra: Vite, Vue 3

playwright test -c playwright-ct.config.ts

When creating ref with some mock data in '*.spec.tsx' test file and passing it to the tested component in mount, initial render works.

However, upon updating the ref value with a new value, the component doesn't automatically rerender.

This is, for example, working in Cypress component testing (mentioning it since I just migrated to Playwright).

I understand one can use Playwright's await component.rerender({ props: { *somepropname*: *someref.value* }})

But that has a few significant drawbacks:

It is not type safe, so upon refactoring component prop names, changing types etc., I will realize at best only after running the test. With reactivity, everything would be beautifully type safe and automatic.

It doesn't really allow you to test deep reactivity (list item property changes etc.). Only shallowRef at best. You can force the rerender, yes, but that destroys the purpose of deep reactivity testing.

I admit that reactivity testing is not always useful, but I have some use for it in my more complex components.

More importantly, the type safety is just really really nice to have.

It is also part of a reason why I use tsx tests instead of ts tests; because only mount(<ItemList items={...} />)) is type safe while also forcing you to provide values for all required props and warning you when providing values for non-existent props.

Full repro project. Steps to reproduce:

Download repro-project.zip

Install Volar extension (official Vue 3 support extension)

Enable Take Over mode for workspace (guide is in README.md if needed)

npm install

npm run dev to see a glorious ItemList.vue component drawing ten items

Check the 'ItemList.vue' component code

Check the 'ItemList.spec.tsx' test code

Try running the test from previous bullet. The test fails. There are a few exaplanatory comments in the test file with additional info.

Minor additional issue also demonstrated in the repro project:

interface MountResult from @playwright/experimental-ct-vue is not exported.

This is a little annoying since I can only pass the component reference as Locator from beforeEach where I'm mounting the actual component.

Then, in the aforementioned test file I have to do this await (component as any).rerender(...).

Issue 2:
System info

Playwright Version: [v^1.35.1]

Operating System: [macOS 13.3.1]

Steps

Set up sandbox project following the https://playwright.dev/docs/getting-started-vscode

Observe VS Code interactive window: "Testing/Testing Explorer"

Expected

All tests were found:

Actual

Neither test case was found:
Issue 1:
Environment

Windows build number: 10.0.18362.295
Windows Terminal version (if applicable): 0.4.2382.0
Ansible version: 2.5.1

Steps to reproduce

Through ansible-vault commands for encrypting specific variables, we should be able to copy and paste the generated key and encrypted value as the outputted in the terminal. It looks like that windows terminal is adding some characters at the beginning of each line.

sudo ansible-vault encrypt_string --vault-password-file ~/.ansible_dep_pwd 'value_encrypted' --name 'key'

Expected behavior

The paste result to any code editor or text processor should be like this:

Actual behavior

The current result of the paste it's actually like this:

It looks like multiple tabs or spaces are being added and copy with, generating weird spaced results.

Thanks everyone for having a look at this, great stuff with the terminal and keep the good work!

Issue 2:
Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Click on the drop down menu and click settings

Expected behavior

Settigns window should open

Actual behavior

It launches Visual Studio 2017
Issue 1:
I am working in a Symfony 2.8 and I am using latest FOSUser (~2.0@dev). This is how the security.yml looks like:

security:
encoders:
FOS\UserBundle\Model\UserInterface: bcrypt

role_hierarchy:
ROLE_ADMIN: ROLE_USER
ROLE_SUPER_ADMIN: ROLE_ADMIN

providers:
fos_userbundle:
id: fos_user.user_provider.username_email

firewalls:
dev:
pattern: ^/(_(profiler|wdt)|css|images|js)/
security: false

main:
pattern: ^/
anonymous: ~
logout: true

form_login:
provider: fos_userbundle
csrf_provider: security.csrf.token_manager
login_path: fos_user_security_login
check_path: fos_user_security_check

remember_me:
secret: '%secret%'
lifetime: 604800 # 1 week in seconds
path: /

access_control:
- { path: ^/login$, role: IS_AUTHENTICATED_ANONYMOUSLY }
- { path: ^/resetting, role: IS_AUTHENTICATED_ANONYMOUSLY }

- { path: ^/admin/, role: ROLE_ADMIN }

Now take a look to this picture:

As you can see (1) the URI points to app_dev.php so I am working on DEV environment (2) user is authenticated (3) although logout link points to non DEV env as shown in (4) which cause wrong logout route. Is this a issue or I miss something in configuration?

Issue 2:
Hi!

When logging out with developer toolbar link it dosn't work, mainly because the link goes to prod envirenment instead of dev (app_dev.php/)

The project I'm working on:

https://bitbucket.org/Richardh87/messenger/overview
Issue 1:
Feature Request

Currently react render children of Suspense with inline style display: none !important, referenced PR. would like to have a prop like mount or sth else to remount the children when suspended state changed.

Example

const Chid = () =>
// ...
return <div>{data}</div>

<Suspense mount fallback={<span>fallback</span>}>
<Chid />
</Suspense>

the above code will only render fallback component

<span>fallback</span>

instead of

<span>fallback</span>
<div style="display: none !important;">data</div>

Issue 2:
Do you want to request a feature or report a bug?

It's a feature.

What is the current behavior?

React.Suspense mounts its children with a display: none style if a promise is thrown. Once the thrown promise is resolved, React removes the display: none style.

What is the expected behavior?

The children components have no easy way to know when the display: none style is removed by React. This is problematic when one child component needs to read from the DOM layout to correctly display its elements. Most people wait for the componentDidMount callback to trigger, but because the element is display: none, it can't read any value from the DOM layout.

The issue was discovered in mui/material-ui#14077. I believe that React should provide a lifecycle so the children components know when they are visible, that it's safe to do layout computations.

The best workaround I'm aware of it to use the Intersection Observer API but it requires a polyfill on IE 11 and Safari.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

Version: 16.7.0-alpha.2
Issue 1:
It would be great to be able to open the preview window for Markdown in a separate window, so that I can, for example, have the preview projected to a TV-Screen, which everyone sees, while i got the Markdown on my laptop. That way, I could take notes in markdown and have them immediately on the screen, so everyone sees it.

Currently therefor I need to use md-server, which requires me to save the file always, before it's being updated by md-server.

Issue 2:
VSCode Version: 1.15.1, 64 bit

OS Version: Windows 10 64 bit

Steps to Reproduce:

Open markdown file, click the preview button

File/New Window

Try and drag just the preview part to the new window

It would be really nice if I could drag the markdown preview to a new window so I can edit the markdown on one monitor and see the preview result on another monitor.
Issue 1:
I have checked the issues list

for similar or identical enhancement to an existing feature.

I have checked the pull requests list

for existing proposed enhancements.

I have checked the commit log

to find out if the if the same enhancement was already implemented in the

master branch.

I have included all related issues and possible duplicate issues in this issue

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

Related Issues and Possible Duplicates

None that I'm aware of

Brief Summary

Logging args is really helpful, but it's currently only done with Rejected logs and it would be nice to also include in Received logs

See

celery/celery/app/trace.py

Line 259
in
f02d7c6

'args': sargs,

Design

Architectural Considerations

If a task takes a lot of args or large args, then it could make logs large

Proposed Behavior

Include args in Received logs

Proposed UI/UX

On by default with a way to turn it off

Diagrams

N/A

Alternatives

Off by default with a way to turn it on

Issue 2:
Checklist

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).

software -> celery:4.0.2 (latentcall) kombu:4.0.2 py:3.6.1
billiard:3.5.0.2 py-amqp:2.1.4
platform -> system:Darwin arch:64bit imp:CPython
loader -> celery.loaders.default.Loader
settings -> transport:amqp results:disabled

Steps to reproduce

Create a task that retries via raise self.retry()

Call the task with send_task and set expires

Expected behavior

The task should retry until the expires time is hit or the max_retries value is hit

Actual behavior

Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/celery/app/task.py", line 684, in retry
S.apply_async()
File "/usr/lib/python3.6/site-packages/celery/canvas.py", line 221, in apply_async
return _apply(args, kwargs, **options)
File "/usr/lib/python3.6/site-packages/celery/app/task.py", line 535, in apply_async
**options
File "/usr/lib/python3.6/site-packages/celery/app/base.py", line 729, in send_task
root_id, parent_id, shadow, chain,
File "/usr/lib/python3.6/site-packages/celery/app/amqp.py", line 334, in as_task_v2
expires = expires and expires.isoformat()
AttributeError: 'str' object has no attribute 'isoformat'
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: 5.0.6

Operating System: macOS Mojave

Last Known Working Electron version:

n/a

Expected Behavior

Calling BrowserWindow.setTitle ( '' ) should have a consistent effect across all platforms.

Actual Behavior

In macOS when I set the title to an empty string it kind of resets itself to the application name.

In linux (Lubuntu 18) instead my windows have "Unnamed Window" as title.

To Reproduce

call #setTitle ( '' ) on a window in Linux.

Screenshots

Additional Information

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:

5.0.6

Operating System:

macOS Mojave

Last Known Working Electron version:

n/a

Expected Behavior

Calling BrowserWindow.setTitle ( '' ) should have a consistent effect across all platforms.

Actual Behavior

In macOS when I set the title to an empty string it kind of resets itself to the application name.

In linux (Lubuntu 18) instead my windows have "Unnamed Window" as their title.

To Reproduce

Call #setTitle ( '' ) on a window in Linux.

Screenshots

Additional Information
Issue 1:
When using a RTL language, the label text seems to still be left aligned.

I have searched the issues of this repository and believe that this is not a duplicate. This is also apparently NOT related to #9007 (comment). cc @alitaheri who might know more about this!

Expected Behavior

Label text should be right aligned when dir="rtl"

Current Behavior

Label text is always left aligned:

dir="ltr"
dir="rtl"

Steps to Reproduce (for bugs)

Here is a minimal demo: https://942ywwnk4w.codesandbox.io/

Context

My labels are showing on misaligned, as per the screenshot above.

Inspecting the styles shows the text is `transform`ed to `top left` instead of `top right`

.MuiInputLabel-formControl-188 {
top: 0;
left: 0;
position: absolute;
transform: translate(0, 23px) scale(1);
}

.MuiInputLabel-root-187 {
transform-origin: top left;
}

Your Environment

Tech
Version

Material-UI
beta.22

React
16.1

browser
Chrome

Issue 2:
When I use TextField I have to add additional InputProps to make it actually full width as required.

I discovered it when I added a "display: block" to TextField's style.

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

Expected Behavior

I would like to use TextField like so:

<TextField
style={{display: 'block'}}
label="Some label"
fullWidth
value={value}
onChange={onValueChange}
/>

and I would expect the internal Input component in the tree to have fullWidth: true, but this is not the case (tested with react dev tools - If I toogle this prop on Input component under TextField it is properly rendered).

Current Behavior

I have to use the component like so:

<TextField
style={{display: 'block'}}
label="Some label"
fullWidth
InputProps={{ fullWidth: true }}
value={value}
onChange={onValueChange}
/>

to explicitly set fullWidth on Input component.

Steps to Reproduce (for bugs)

See:

Context

I needed this display: block for styling purposes and discovered a bug in the process.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.28

React
16.2.0

browser
Chrome 63.0.3239.132
Issue 1:
The compiler segfaults on the following program:

struct X { field: Option<X> }

fn main() { let x = X { field: None }; }

Surprisingly, the following program successfully compiles:

struct X { field: Option<X> }

fn main(){}

Issue 2:
The following program causes a stack overflow:

struct S {
element: Option<S>
}

fn main() {
}

There is a check that enums do not recurse in this way, but no such check for structs. (Note, though, that there is a check that structrs are instantiable, which is slightly different)
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

When an existing shrinkwrap is installed

npm init
npm i @polymer/polymer@3.2.0 @vaadin/vaadin-core-shrinkwrap@23.0.0-beta1 --save

And you lock the version of a package not mentioned in the shrinkwrap

# Add "overrides": { "@polymer/polymer": "$@polymer/polymer"} to package.json

You can then no longer upgrade the shrinkwrap

npm i @vaadin/vaadin-core-shrinkwrap@23.0.0-beta2

npm ERR! Unable to resolve reference $@polymer/polymer

Expected Behavior

You can install the new shrinkwrap even if an unrelated package has an override defined.

Steps To Reproduce

git clone https://github.com/Artur-/npm-overrides-test.git

cd npm-overrides-test

npm i @vaadin/vaadin-core-shrinkwrap@23.0.0-beta2

Environment

npm: 8.5.0

Node.js:v17.3.0

OS Name: Mac os Big Sur

System Model Name: Macbook Pro

npm config:

//registry.npmjs.org/:_authToken = (protected)

Issue 2:
What / Why

Recently I've been running npm init on modules to ensure that package.json is well-formed and has all of the relevant data. I just noticed a fun bug where npm init copies your optionalDependencies to dependencies, which the documentation discourages:

Entries in optionalDependencies will override entries of the same name in dependencies, so it’s usually best to only put in one place.

When

I run npm init on a module with optional dependencies.

Where

n/a

How

Current Behavior

npm init duplicates optionalDependencies to dependencies

Steps to Reproduce

cd $(mktemp -d)

npm init -y

npm i --save-optional lodash

npm init -y

I've made a Git repository with the output tree of each command here.

Expected Behavior

npm should not duplicate optionalDependencies to dependencies

Who

n/a

References

n/a