WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
System info

Playwright Version: [v1.33]

Operating System: [Windows 10]

Browser: [All]

Other info:

Source code

playwright install

Downloading Chromium 113.0.5672.53 (playwright build v1060) from https://playwright.azureedge.net/builds/chromium/1060/chromium-win64.zip

stuck for hours. but can download the chromium manually in less than 60 seconds

what should i do?

Issue 2:
System info

Playwright Version: v1.31.2

Operating System: All

Browser: All

Other info:

Source code

We use playwright._electron.launch and electron.firstWindow() to smoke test VS Code. We noticed that with the latest version, a file playwright-core/lib/server/electron/loader.js opens, so we assume it is being added to the path when launching VS Code.

This breaks all our smoke tests that assume no file would open.

//cc @mxschmitt
Issue 1:
When using the mediastream typings with typescript 2.0, a lot of errors like these are logged:

All declarations of 'volume' must have identical modifiers.
All declarations of 'id' must have identical modifiers.
etc.

What exactly does this mean?

cc @vvakame, @nakakura, @horiuchi, @groege, @Garciat, …

Issue 2:
Version of ts-toolbelt used by @types/ramda declares global modules and names, it causes errors of duplication when I want to use ramda with other packages that also use ts-toolbelt or having two packages in my monorepo use ramda.

If you know how to fix the issue, make a pull request instead.

I tried using the @types/ramda package and had problems.

I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript

I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).

Mention the authors (see Definitions by: in index.d.ts) so they can respond.

Authors: @TheHandsomeCoder, @donnut, @mdekrey, @mrdziuban, @sbking, @afharo, ...

If you do not mention the authors the issue will be ignored.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

do not autofocus AnchorElement onClose

Current Behavior

autofocus AnchorElement onClose. this lead to the tooltip be activated (occurred in Menu Model Dialog components)

Steps to Reproduce (for bugs)

DEMO

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.23

React
16.0.0

browser
chrome 62.0.3202.94 (Official Build) (64-bit)

etc

Issue 2:
When using Hot Module Replacement with material ui, the style change cannot be reloaded.

JSS and react-hot-loader should be able to work together

https://github.com/cssinjs/react-jss/issues/29#issuecomment-192795272

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

Expected Behavior

HMR should replace/update the <style> tags in <header>

Current Behavior

The new component has been sent through, but <style> tags in <header> didn't change

Steps to Reproduce (for bugs)

create-react-app to create a new app

add react-hot-loader@next and material-ui@next

eject the app to configure HMR by yarn eject

then change entry of ./config/webpack.config.dev.js into following

entry: [
'react-hot-loader/patch', // <---add
require.resolve('webpack/hot/dev-server'), // <---uncomment
require.resolve('webpack-dev-server/client') + '?/', // <---uncomment
// require.resolve('react-dev-utils/webpackHotDevClient'), // <--- comment out this line
paths.appIndexJs // <-- unchanged
]

add HOC for react-hot-loader, in src/index.js

// ... other imports
import { AppContainer } from 'react-hot-loader';

const render = App => {
ReactDOM.render(
<AppContainer>
<App />
</AppContainer>,
document.getElementById('root')
);
};
render(App);

registerServiceWorker();

// Enable hmr
if (module.hot) {
module.hot.accept('./App', () => {
render(require('./App').default);
});
}

add babel config in package.json

"babel":{
//...others
"plugins":[
...other plugins,
"react-hot-loader/babel" <--- add this line
]
}

try change text value to see hmr actually works (the page shouldn't refresh and there should be a request from url like http://localhost:3000/0.d1087ac819fcd47659f1.hot-update.js)

create a component and use withStyles

try change the values in styles and the style isn't changed by HMR,

refresh the page the style will change.

see network tab can see the component change has been sent through (from url like http://localhost:3000/0.d1087ac819fcd47659f1.hot-update.js contain the transpiled code of this file)

Context

we cannot use HMR with webpack when we need to persist states in application and make changes through HMR.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.11

React
15.6.1

browser
Chrome 60.0.3112.113 (Official Build) (64-bit)

react-hot-loader
3.0.0-beta.7

webpack
3.5.1

webpack-dev-middleware
1.12.0

webpack-dev-server
2.7.1
Issue 1:
Currently, the form component add some strong requirements on the way to access field values. It would be a good idea to allow to specify a different getter or setter (defaulting to the current behavior) to give more flexibility.

And for collections, it would be a good idea to be able to use addXXX and removeXXX instead of recreating the collection entirely using a setXXXs setter, which has really bad performances for Doctrine toMany relations as it removes all relations and add new ones.

Issue 2:
The collection type is broken when using it for the inversed side of a Doctrine relation as it modifies the collection instead of calling some setter in the class. As Doctrine does not track changes in the inversed side, the changes are not persisted.

The best practice for Doctrine is to call the setter of the owning side in the setter of the inversed side. But as the setter is not called, this has no effect for the forms. And there is currently no way to change this behavior in user-land forms.

I suggested in #1141 to allow defining the setter used. A collection type should then call addXXX and removeXXX on the object instead of modifying the collection to allow having additionnal logic when adding and removing elements.
Issue 1:
When I have textAlign: TextAlign.center, and TextField is in SizedBox and when I enter first character the blinking line gets bugged and moves from center to the beginning of the TextField. As soon as I enter second character, line is okay once again.

Example:

import 'package:flutter/material.dart';

void main() => runApp(new MyApp());

class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
final appTitle = 'Test';

return new MaterialApp(
title: appTitle,
home: new Scaffold(
appBar: new AppBar(
title: new Text(appTitle),
),
body: new Test(),
),
);
}
}

class Test extends StatefulWidget {
@override
TestState createState() {
return new TestState();
}
}

// Create a corresponding State class. This class will hold the data related to
// the form.
class TestState extends State<Test> {
// Create a global key that will uniquely identify the `Form` widget
@override
Widget build(BuildContext context) {
// Build a Form widget using the _formKey we created above
return new Stack(
children:[
new Positioned(
left: 100.0,
right: 100.0,
top: 200.0,
height: 20.0,
child: Row(
children: <Widget>[
new SizedBox(
width: 50.0,
child: new TextField(
textAlign: TextAlign.center,
style: new TextStyle(
color: Colors.blue,
),
),
),
],
),
),
],
);
}
}

I think this issue is the same with all text input widgets.

A lil off topic - I didn't see how can we align, lets say, error text. If I use validation in TextFormField which covers whole width of the screen, and I use TextAlign.center for input, it's very ugly that error is on the left, and entered text in center of the widget.

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v0.5.5-pre.10, on Mac OS X 10.13.4 17E202, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4)
[✓] Android Studio (version 3.1)
[!] IntelliJ IDEA Ultimate Edition (version 2018.1.2)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] Connected devices (2 available)

Issue 2:
I'm using a TextField and have set its alignment to center.

body: new Container( color: Colors.blue, child: new Center( child: new TextField( decoration: new InputDecoration( hintText: "Anything goes here" ), textAlign: TextAlign.center, ), ), ),

However, I have noticed that after I enter the first character, the cursor blinks at the beginning of the text field, after that the position stays at the center. This is only view-able after inputting the first character.
Issue 1:
My steps to repro:

Open Firefox 9 on Mac

Go to bootstrap main page (I'm assuming is working off 1.4.0 )

Scrolldown to look at dropdown input element. Style is broken.

Issue 2:
The select form in chrome is displayed beatifully compared to firefox (at least my version 6.0.2) where you see an "ugly" arrow.

I am not sure whether it can be solved or not and it isn't actually a bug.. It also happens in twitter preferences.
Issue 1:
David Pedowitz opened SPR-4774 and commented

More brainstorming from training session in LA, 5/1/08 with Chris Beams, Tchavdar Ivanov (FIM) and myself.

@Validator could be a class level annotation eligible for component scans, the methods of which could be annotated with @Validate (or similar) which would enable method/request param specific validation within the request handling workflow

Like the @HandlerInterceptor design (#9447) @Validator could take a list of @Controller classes for a more fine grained approach or @Controller could take a list of @Validator which would match the current register model (I think I like the later)

@Validate would define a method used to validate an @RequestParam, it'd might be neat if it handled superset of @RequestParam and @RequestMapping arguments for a very fine grained approach, i.e. @Validate("reward", method=RequestMethod.POST).

Another option would be to register the Validator with the @RequestParam

Hope you dig the ideas

Issue Links:

#4803 Support for declarative validation (Hibernate Validator, anticipating JSR 303)

#14072 Improve support for registering Validator implementations in Spring MVC ("is superseded by")

9 votes, 10 watchers

Issue 2:
Kenny MacLeod opened SPR-3219 and commented

When using the form:options tag where the items data is a Map, the itemLabel and itemValue attributes are ignored. Instead, the rendering logic simply uses the toString() of the map key for the option's value, and the toString() of the map value as the option's label. This isn't much use when either the map key or value is a bean.

A more sensible approach would be to use the itemValue attribute to retrieve a property of the map key, and the itemLabel attribute to retrieve a property of the map value.

Alternatively, since Map.Entry is itself bean-compliant, the itemValue and itemLable values could be used as properties of the Map.Entry, e.g. itemValue="key.x" or itemLabel="value.y"

This was previously raised as #7349, but I thought it warranted a bug report.

Affects: 2.0.2

Issue Links:

#7349 Make itemLabel/itemValue meaningful in map-based option rendering? ("duplicates")
Issue 1:
Reproducing code example:

import numpy as np

np.double(3.0,x=3.1,y=3.2,z=3.4,q=3.14)
np.double(3.0,x=3.1)

3.0

returns

np.double(x=3.1)

returns

0.0

Error message:

No error, but too tolerant of keyword arguments

NumPy/Python version information:

1.20.2 3.8.10 (default, May 19 2021, 18:05:58)
[GCC 7.3.0]

Issue 2:
Unlike the other scalar types, numpy.float64 silently ignores unknown keyword arguments:

In [17]: np.__version__
Out[17]: '1.20.0.dev0+f0171ba'

In [18]: np.float64(123, foobar="plate of shrimp")
Out[18]: 123.0

The other types raise the exception TypeError: function takes at most 1 argument (2 given):

In [19]: np.float32(123, foobar="plate of shrimp")
---------------------------------------------------------------------------
TypeError Traceback (most recent call last)
<ipython-input-19-2f7cf4afa2cb> in <module>
----> 1 np.float32(123, foobar="plate of shrimp")

TypeError: function takes at most 1 argument (2 given)

In [20]: np.uint32(123, foobar="plate of shrimp")
---------------------------------------------------------------------------
TypeError Traceback (most recent call last)
<ipython-input-20-8b32fef69395> in <module>
----> 1 np.uint32(123, foobar="plate of shrimp")

TypeError: function takes at most 1 argument (2 given)
Issue 1:
Prior to r69 SpotLight.target was being added to the scene when SpotLight or its parent was added to it, not anymore.

Because of that changing SpotLight.target has no effect on the direction of the light anymore. Right now as a workaround SpotLight.target should be added to the scene manually, then light's direction will change when SpotLight.target.position will be updated.

Issue 2:
Bug: The changes to spotLight.target.position are not affecting.

Normal work with r68: http://jsfiddle.net/doexclusive/jhoe4ynr/

Bug with r69 and from dev branch: http://jsfiddle.net/doexclusive/6dhdbpw9/
Issue 1:
Issue Type:

Bug Report

Ansible Version:

ansible 2.1.0 (devel c5b4e19) last updated 2016/02/02 20:48:56 (GMT +200)

Environment:

Ubuntu 15.10

Summary:

When running a playbook by specifying tags, fact gathering is skipped.

Steps To Reproduce:

Run any playbook with --tags tagname.

Expected Results:

Facts should be gathered like in version before 2.0 when specifying tags.

Actual Results:

Facts are not gathered when any tag is specified.

Issue 2:
Issue Type:

Bug Report

Ansible Version:

ansible 2.1.0 (devel 49c15c8137) last updated 2016/01/31 08:09:48 (GMT +000)
lib/ansible/modules/core: (detached HEAD 93d02189f6) last updated 2016/01/31 08:32:26 (GMT +000)
lib/ansible/modules/extras: (detached HEAD fff5ae6994) last updated 2016/01/31 08:32:46 (GMT +000)
config file =
configured module search path = Default w/o overrides

Ansible Configuration:

N/A

Environment:

Ubuntu 14.04 LTS

Summary:

The destructive integration test for apt_repository fails as of commit 5587b08.

The test passes using commit ceef202 and earlier.

Steps To Reproduce:

Run the destructive integration test on test_apt_repository:

ansible-playbook destructive.yml -i inventory -e @integration_config.yml -v --tags test_apt_repository

Expected Results:

TASK [test_apt_repository : set_fact] ******************************************
ok: [testhost] => {"ansible_facts": {"test_ppa_filename": "menulibre-dev", "test_ppa_key": "A7AD98A1", "test_ppa_name": "ppa:menulibre-dev/devel", "test_ppa_spec": "deb http://ppa.launchpad.net/menulibre-dev/devel/ubuntu trusty main"}, "changed": false}

Actual Results:

TASK [test_apt_repository : set_fact] ******************************************
fatal: [testhost]: FAILED! => {"failed": true, "msg": "The conditional check 'ansible_distribution in ('Ubuntu', 'Debian')' failed. The error was: error while evaluating conditional (ansible_distribution in ('Ubuntu', 'Debian')): 'ansible_distribution' is undefined\n\nThe error appears to have been in '/root/ansible/test/integration/roles/test_apt_repository/tasks/main.yml': line 19, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- include: 'apt.yml'\n ^ here\n"}
to retry, use: --limit @destructive.retry
Issue 1:
I have managed to find a session bug that is easily reproducible.

First you have to enalbe database sessions, i did so by following this guide http://symfony.com/doc/current/cookbook/configuration/pdo_session_storage.html

Then you can create 2 actions like this:

/**
* @Route("/lol", name="myroute_lol")
*
*/
public function lolAction()
{
$this->container->get('session')->set('testsess', 'aasasaasasas@ooo.com');

//send an email
$message = \Swift_Message::newInstance()
->setSubject('Test subject')
->setFrom('test@mail.com')
->setTo('something@test.gr')
->setBody($this->renderView('MyBundle:Default:mail.txt.twig', array('body' => 'some body text')))
;
$this->get('mailer')->send($message);

return $this->redirect($this->generateUrl('myroute_lol2'));
}

/**
* @Route("/lol2", name="myroute_lol2")
*/
public function lol2Action()
{
$email = $this->container->get('session')->get('testsess');
return new Response('email:'.$email);
}

If you clear you browser cookies then each time you go to the /lol url then you get redirected to /lol2 and the session returns an empty string for session variable 'testsess'

If you refresh /lol2 then the second time it works and shows the correct value.

It has something to do with mail. If you comment out the line where the send() happens then all is ok. It has something to do with not writing the session in the database after the completion of the execution of the action.

I have debugged the swift mail bundle a bit and it seems that when send() is called the mail is saved in memory (spool memory, uses class Swift_MemorySpool), so i suppose mails are sent after the completion of the action, after the action returns, somewhat asynchronously i suppose.

It seems that something happens in the code after the action returns a redirect.

If you change the redirect and simply output something then the session is ok.

This bug has 3 conditions, using mysql sessions, sending an email and then redirecting to another action.

It is reproducible. I hope i didn't cause confusion.

Thank you.

P.S. using symfony 2.1.7

Issue 2:
Hi,

probably I have found an issue in using form with Twig templates. I have a base Twig template source with which I check if a block is filled deeper in the hierarchy.

# WebBundle:Default:base.html.twig
{% if block('body') is not empty %}
{% block body %}{% endblock %}
{% endif %}

The following is the Twig template that inherit the previous template:

# WebBundle:Default:form.html.twig
{% extends 'WebBundle:Default:base.html.twig' %}
{% block body %}
{{ form(form) }}
{% endblock %}

In this way the form is left empty: ONLY THE <FORM/> TAG IS PRINTED, but not its content.

If I remove the condition in the first file it works properly, rendering the required form with all the fields, as expected.

# WebBundle:Default:base.html.twig
{% block body %}{% endblock %}

Thank you.
Issue 1:
julia> c = '1'
'1': ASCII/Unicode U+0031 (category Nd: Number, decimal digit)

julia> c'

signal (11): Segmentation fault: 11
in expression starting at no file:0
unknown function (ip: 0xffffffffffffffff)
Allocations: 3423488 (Pool: 3422945; Big: 543); GC: 6

Issue 2:
A surprising way to trigger a surprising error:

julia> ""'
julia: /home/jeff/src/julia/src/codegen.cpp:1378: jl_generic_fptr_t jl_generate_fptr(jl_method_instance_t*, const char*, size_t): Assertion `fptr.fptr != __null' failed.

signal (6): Aborted
in expression starting at no file:0
raise at /build/buildd/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c:56
abort at /build/buildd/eglibc-2.19/stdlib/abort.c:89
__assert_fail_base at /build/buildd/eglibc-2.19/assert/assert.c:92
__assert_fail at /build/buildd/eglibc-2.19/assert/assert.c:101
jl_generate_fptr at /home/jeff/src/julia/src/codegen.cpp:1378
jl_compile_method_internal at /home/jeff/src/julia/src/julia_internal.h:367 [inlined]
jl_call_method_internal at /home/jeff/src/julia/src/julia_internal.h:395 [inlined]
jl_apply_generic at /home/jeff/src/julia/src/gf.c:2081
inline_call at ./inference.jl:5361
inline_expr at ./inference.jl:5273
jl_call_fptr_internal at /home/jeff/src/julia/src/julia_internal.h:380 [inlined]
jl_call_method_internal at /home/jeff/src/julia/src/julia_internal.h:399 [inlined]
jl_apply_generic at /home/jeff/src/julia/src/gf.c:2081
inline_expr at ./inference.jl:5277
inlining_pass! at ./inference.jl:5257
optimize at ./inference.jl:3759
Issue 1:
Electron version: 1.4.15

Operating system: OSX 10.12.2

Expected behavior

MenuItem with role should be disabled when a set a menuItem with enabled:false

Actual behavior

MenuItem with role are not disabled whereas a MenuItem without role is correctly disabled

How to reproduce

I made a small repo that shows the bug : https://github.com/jbleuzen/electron-menu

If you have any questions... :)

Issue 2:
Electron version: 1.1.0

Operating system: MacOS

var template = [{
accelerator: 'CmdOrCtrl+Z',
click: function (item, win) {
},
enabled: false
},
{
accelerator: 'CmdOrCtrl+Y',
click: function (item, win) {
},
enabled: false
},
{
accelerator: 'CmdOrCtrl+X',
role: 'cut',
enabled: false
},
{
accelerator: 'CmdOrCtrl+C',
role: 'copy',
enabled: false
},
{
accelerator: 'CmdOrCtrl+V',
role: 'paste',
enabled: false
},
{
accelerator: 'CmdOrCtrl+A',
role: 'selectall',
enabled: false
}]

contextMenu = Menu.buildFromTemplate(template);
contextMenu.popup(BrowserWindow.getFocusedWindow());

Items with defined click, are disabled, others - no.
Issue 1:
On Windows 8.1, with a high DPI screen, min-width/min-height behave wrongly - the value is multiplied by the current DPI over standard DPI, resolving in higher actual values.

For example, when the min-width is set to 1000, the system has a resolution width 2560, but Electron renders as if the width of the screen is around 1330 (so that things do not appear to small), the actual window width based on min-width resolves in around 1500px, but the actual window comes up wider than the screen because the width is already re-calculated according to this.

The point is, min-width/min-height shouldn't be re-calculated according to DPI since width/height of the window already are.

Labels: windows, bug

Issue 2:
I'm seeing two problems with the min-width and min-height properties.

First, when opening a window that includes the native window chrome, the window width and height that is set when creating the window includes the width and height of the native window chrome. So if I set width to 800px and height to 600px, the entire window is 800 x 600. However, if we also set min-width to 800px and min-height to 600px, these measurements seem to exclude the native chrome. So if I try to resize it at all (or even to drag the window on Windows), it will resize itself so that the contents (excluding the chrome) are 800 x 600. The window will get bigger by the size of the chrome, which is the height of the header on OSX and about 15px x 38px on Windows.

Secondly, on Windows only, if you have auto-scaling turned on, this is being applied once when opening the BrowserWindow with a specified width and height, but is being applied a second time when evaluating min-width and min height. For example, my PC has a screen resolution of 3200 x 1800, and the recommended scaling is 200%. With these settings, if we create a browser window as 400px wide and 300px high, then it's actually created as 800 x 600, which is what I'd expect with 200% scaling. However, it seems that if I also set the min-width to 400 and the min-height to 300, and drag or attempt to resize the window, then the minimum dimensions are evaluated, and doubled again, so I end up with a window that jumps to twice the expected size (1626 x 1271). While I can get around this by turning off auto-scaling (setting scaling to 100%), because the recommended setting for my resolution is to have this turned on, I would expect that a lot of Windows users with high-resolution monitors would run into a similar problem.

Thank you.