WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Electron version: 0.30+

Operating system: Windows, Mac & Linux

There are plenty of small & large desktop applications made in Electron, and while core application logic may be under a few megabytes, the installer (having its own Electron bundled) itself adds over 60 MB of weight. Once I have couple of Electron based apps installed, I have multiple Electron binaries installed dedicated for each single app.

Now, I'm aware that each such app may be using a different version of Electron itself (relying on features & bugs of a particular version to get the job done), but that's the point here, to make sure that run-time serves the platform and apps carry just its own dependencies (NPM modules unrelated of Electron), thus making resulting installers way less in size. Look at JVM or Adobe AIR, for example.

Obviously there can be special scenarios where Electron is patched for a particular app (Brave browser for instance, has process sandboxing enabled, a feature not natively supported in Electron itself), in such case installer can carry runtime along, but trivial applications don't need it.

Abricotine is one such example, where it is plain Markdown editor (and source is measly 2 MB), but 64bit Windows installer is 75 MB!.

This problem of redundant installations is only going to add bloat as adoption of technologies like Electron & NW.js increases to create Desktop applications (being dead simple to get apps running instead of going a native route).

Thanks.

Issue 2:
Currently developers using atom-shell have to ship the whole atom-shell binaries when distributing their apps, but since now we have asar as atom-shell's app format, we may add runtime mode to atom-shell like Adobe Air or Chrome Hosted Apps that developers only need to distribute packaged app in asar format as long as end users have the runtime mode of atom-shell installed.

The runtime mode can just be another app based on atom-shell (let's call it atom-runtime for now), and has deep platform integrations:

On Windows, we can provide installer and auto updater for atom-runtime, and register the .asar file type to be opened with it.

On Linux, we provide official software sources of atom-runtime for some popular distributions, and also register atom-runtime as handler of .asar files.

On Mac, we need to provide a tool to help users package their apps into Mac bundles. We can reference how Steam created bundles for downloaded games, or how Parallel created bundles for applications in hosted OS.

We can even provide a tool or service to help generating installers for developers' apps which can automatically download atom-runtime if it is not installed on user's machine, just like many .NET applications.
Issue 1:
Atom crashes every time when I try to open it, from command line and from dock. It crashes immediately after opening, I can't even see the window. I have used atom in my computer few months with out any problem.

When opening atom from terminal it prints following message every time:

LSOpenURLsWithRole() failed for the application /Applications/Atom.app with error -10810.

And OS X opens "Problem Report for Atom" window.

It contains following information

Process: Atom [27076]
Path: /Applications/Atom.app/Contents/MacOS/Atom
Identifier: com.github.atom
Version: ???
Code Type: X86-64 (Native)
Parent Process: launchd [353]
Responsible: Atom [27076]
User ID: 501

Date/Time: 2015-03-27 23:58:27.061 +0200
OS Version: Mac OS X 10.9.5 (13F1066)
Report Version: 11

...

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
Library not loaded: @rpath/libchromiumcontent.dylib
Referenced from: /Applications/Atom.app/Contents/Frameworks/Atom Framework.framework/Versions/A/Atom Framework
Reason: image not found

Binary Images:
0x7fff6e412000 - 0x7fff6e445817 dyld (239.4) <7AD43B9B-5CEA-3C7E-9836-A06909F9CA56> /usr/lib/dyld
0x7fff855f1000 - 0x7fff855f1fff com.apple.Carbon (154 - 157) <45A9A40A-78FF-3EA0-8FAB-A4F81052FA55> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff8727d000 - 0x7fff87419ff3 com.apple.QuartzCore (1.8 - 332.3) <72003E51-1287-395B-BCBC-331597D45C5E> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff8ee6d000 - 0x7fff8eebffff libc++.1.dylib (120) <4F68DFC5-2077-39A8-A449-CAC5FDEE7BDE> /usr/lib/libc++.1.dylib
0x7fff90102000 - 0x7fff90103ff7 libSystem.B.dylib (1197.1.1) <E303F2F8-A8CF-3DF3-84B3-F2D0EE41CCF6> /usr/lib/libSystem.B.dylib

Issue 2:
I am unable to open Atom from the command line on Mac OS X 10.10 (Beta 4)—I don't remember when it broke or what caused it, but re-downloading/re-installing the command line tools didn't fix it. I believe this is different from #1103 because I'm on Atom 0.119.0.

I investigated which line of /usr/local/bin/atom was causing the error and discovered that

open -a /Applications/Atom.app

works fine, but

open -a /Applications/Atom.app -n

causes the error.

Full error message:

LSOpenURLsWithRole() failed for the application /Applications/Atom.app with error -10810.
Issue 1:
TypeScript Version:

1.8.7

compiled: tsc --noImplicitAny error.ts

(the behavior is exactly the same with or without --noImplictAny)

Code

// A self-contained demonstration of the problem follows...
type Greeting = "hello" | "goodbye"

const apply = <T extends string,R>(t: T, f: (t:T) => R): R => f(t)
const f1 = (a: Greeting) => console.log('greetings')
const f2 = (a: number) => console.log(3+a)

apply("hello", f1) /* 1. should be good. is good */
apply("helo", f1) /* 2a. should be error. is good */
apply<Greeting, void>("helo", f1) /* 2b. should be error. is error */

apply("hello", f2) /* 3. should be error. is error */
apply(3, f1) /* 4. should be error. is error */
apply(3, f2) /* 5. should be error. is error */

Expected behavior:

2-5 should have an error:

2 should have an error because "helo" is not a member of "hello"|"goodbye"

3 should have an error because "hello" is not a number

4 should have an error because 3 is not a member of "hello"|"goodbye" and because 3 is not a member of type which extends string

5 should have an error because 3 is not a member of a type which extends string, and because number does not extend string.

Actual behavior:

1, 2b, 3-5 are correct

2a passes typechecking even though it should be equivalent to 2b

Issue 2:
TypeScript Version:

1.8.9

Code

Based on Using the Compiler API, to generate an AST, use createSourceFile like this:

// A self-contained demonstration of the problem follows...
ts.createSourceFile(<filename>, <file content>, ts.ScriptTarget.ES6, true)

What gets generated appears to be an untyped AST, i.e. the .type field only gets filled if it's declared explicitly in the source code.

What I'm looking for is to generated the typed AST, i.e. having the sources being loaded and typed-checked.

How can I do that? Thanks.
Issue 1:
import 'dart:async';

import 'package:flutter/widgets.dart';

final GlobalKey _kKey = new GlobalKey();
Future main() async {
runApp(new Block(
children: new List<Widget>.generate(
2,
(_) => new Padding(
padding: const EdgeInsets.all(8.0),
child: new Container(
key: _kKey,
width: 100.0,
height: 100.0,
decoration: new BoxDecoration(
backgroundColor: new Color(0xFFFFFF00)))))));
}

Issue 2:
If you're creating an app that has native and flutter components there is no way to share images or fonts between flutter and android/ios. This means that assets needed on both sides will have to be included in the binary twice and that could be expensive.
Issue 1:
Runas blows up because it's using old nan, but upgrading it to latest doesn't seem to help, yet when I just run npm install, it all works >:| It'd be cool if we could get on official io.js for building so we could just replace all references of node.js everywhere in the docs

Issue 2:
gyp http GET https://atom.io/download/atom-shell/v0.25.1/iojs-v0.25.1.tar.gz

gyp http 403 https://atom.io/download/atom-shell/v0.25.1/iojs-v0.25.1.tar.gz

It looks already released but can't access. Is it temporary?

https://github.com/atom/electron/releases
Issue 1:
When trying to drag the mouse in order to select text, nothing happen and the cursor stays where the mouse was first clicked. It also prevent from drag and dropping tabs in the same way.

I had the same bug as soon as I updated my Google Chrome to version 41. I had to add this flag '--touch-devices=123' when opening it as mentionned in this issue tracker:

https://code.google.com/p/chromium/issues/detail?id=456222#c102

I do not know how I can add this flag for Atom?

Windows 8.1 Host, Ubuntu 14.04 Guest, VirtualBox 4.3.26

Issue 2:
There is a known issue with Chrome41 engine running on Linux in VirtualBox. It actually became a show-stopper for Chrome42. TL;DR: in VB Chrome41 engine always runs in touch-screen mode, even on desktops.

Hotfix in Chrome41 is to pass --touch-devices=123 to the chrome command line.

Is it possible to pass parameters to Atom’s command line so that chrome engine will understand them?
Issue 1:
Electron version: 1.4.3

Operating system: macOS Sierra 10.12

Description:

I haven't found something in issues so I created it :) Maybe it is a duplicate. Than it can be closed :D

However. It would be great if we can create separator in Tray.

Like the menu-item type separator.

Current tray implementation (without separator):

(Here I like separators between upload and settings and between settings and close)

Example of macOS:

Issue 2:
Electron Version: 2.0.5

Operating System (Platform and Version): macOS Mojave beta4

Expected Behavior

Call browserWindow.setProgressBar(0.5), the app hard crashes citing an unrecognized selector. Doesn't happen on High Sierra

[_NSImageViewSimpleImageView setDoubleValue:]: unrecognized selector sent to instance 0x7fa6b7472040

Actual behavior

Don't crash, set the progress bar

To Reproduce

Clone the repo and press the crash button...

git clone https://github.com/wavebox/electron-quick-start.git -b mojave_set_progressbar_crash
cd electron-quick-start
npm install
npm start
Issue 1:
We should add some basic synchronization around multiple processes creating the node_modules folder at the same time. Basically do whatever cargo build does and have each process wait on the other.

This is necessary because it seems like multiple processes creating junctions at the same time causes some weird issues with the junctions becoming invalid. Also, it's duplicate work for the two processes to do this.

Edit: I have the code done for this... just need to write a test.

Issue 2:
I am using deno_core version 0.112.0 in my project. But when I make a release build and run it on another computer without cargo installed I get the following error:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: The system cannot find the path specified. (os error 3)', C:\Users\user\.cargo\registry\src\github.com-1ecc6299db9ec823\deno_core-0.112.0\runtime.rs:390:38

It appears to be trying to load 00_primordials.js which doesn't exist on my other system. Deno ships in a single executable so i figured that it is possible to do the same with deno_core.
Issue 1:
Do you want to request a feature or report a bug?

Report a bug.

What is the current behavior?

Getting the following error while trying to hydrate SSR content.

Expected server HTML to contain a matching <linearGradient> in <defs>.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template for React 16: https://jsfiddle.net/Luktwrdm/, template for React 15: https://jsfiddle.net/hmbg7e9w/).

The following check returns false

react/packages/react-dom/src/client/ReactDOM.js

Lines 453 to 462
in
177cd85

canHydrateInstance(

instance: Instance | TextInstance,

type: string,

props: Props,

): boolean {

return (

instance.nodeType === ELEMENT_NODE &&

type.toLowerCase() === instance.nodeName.toLowerCase()

);

},

as type is linearGradient and instance.nodeName.toLowerCase() is lineargradient

What is the expected behavior?

Node types are compared correctly as SVG uses camelCase for tagName

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

React 16

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

Bug

What is the current behavior?

I've started recieving this warning about my SVGs which is using feGaussianBlur:

Warning: Expected server HTML to contain a matching <feGaussianBlur> in <filter>.

What is the expected behavior?

Should be no warnings because there are no difference.

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

Such behavior started right after updating to React 16.0.0-rc.3 and never happened with React 15.6.1
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Dialog will scroll its own content when I make a scroll gesture on the phone

Current Behavior

Once I open a second fullscreen modal (which is opened previously by another fullscreen modal), the scroll won't work as expected, since it will scroll contents that are not visible (the Modal behind)

Steps to Reproduce (for bugs)

https://codesandbox.io/s/pkjk07o8o0

Open the link on iOS

Go to the second Dialog

Scroll to the very end, scroll two time more while at the end

Once at the end of the modal, scroll to the top

Scroll will start to feel weird.

Note: it seems that this is happening when you scroll tapping on a input, not 100% sure.

Context

I'm trying to go thru a list of Cards on a Dialog, click on a specific one so it will open a edit Modal, trying to add data to the fields on the 2nd modal will feel weird when I try to scroll.

Your Environment

Tech
Version

Material-UI
Next

React
16.2.0

browser
iOS

etc

Issue 2:
Tested dialogs in http://www.material-ui.com/#/components/dialog.

On desktop Chrome, background scrolling is disabled when dialogs are shown.

However, it is not disabled in iOS Safari or Chrome.
Issue 1:
📝 Provide a description of the new feature

I Would love to see a feature allowing us to set any window to be always on top of other windows. I thing a good way to enable the feature would just be add it to the context menu when you right click on the title bar of a window.

What is the expected behavior of the proposed feature? What is the scenario this would be used?

Enable the feature, the window stays always on top of ALL other windows.

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

Issue 2:
Please make an MSI available as was done in previous versions. It's nice that the EXE has apparently reached parity with the MSI, but MSI is much preferred for distribution in an enterprise environment using Configuration Manager.

If you'd like to see this feature implemented, add a 👍 reaction to this post.
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 a feature request that matches the one I want to file, without success.

Electron Version

11.2.3

What operating system are you using?

Windows

Operating System Version

Windows 10

What arch are you using?

x64

Last Known Working Electron version

5.10.0

Expected Behavior

When use fse.copy() function to copy a file from one location to another, it should works.

Actual Behavior

It seems like, on 11.2.3, fse.copy() will stop working sometimes, without any error or warning. It's like the app doesn't have the permission to perform the operation. On 5.10.0, the same code works perfectly.

Here is more information.

1.Not everyone will encounter this BUG.

2.For some people, they can temporarily solve this problem by restarting the app. The bug will show up afterwards.

3.For some people, even restarting the app will not solve this problem.

4.This bug is only found on Windows OS.

Testcase Gist URL

No response

Additional Information

Our app is a book reading app. We updated the version of electron from 5.10 to 11.2.3 last month.

We have got a lot of complaints about "can not add new books to the library sometimes." after the update.

Our team member has encountered the same problem once, but we cannot reproduce it afterwards.

Right now, we have narrowed down the problem to following functions fse.copy().

It seems like, on 11.2.3, fse.copy() will stop working sometimes, without any error or warning. It's like the app doesn't have the permission to perform the operation. On 5.10.0, the same code works perfectly.

Issue 2:
Our app is a book reading app. We updated the version of electron from 5.10 to 11.2.3 last month.

We have got a lot of complaints about "can not add new books to the library sometimes." after the update.

Our team member has encountered the same problem once, but we cannot reproduce it afterward.

Right now, we have narrowed down the problem to following functions fse.copy().

It seems like, on 11.2.3, fse.copy() will stop working sometimes, without any error or warning. It's like the app doesn't have the permission to perform the operation. On 5.x, the same code works perfectly.

Here is more information.

1.Not everyone will encounter this BUG.

2.For some people, they can temporarily solve this problem by restarting the app.

3.For some people, even restarting the app will not solve this problem.

4.This bug only found on Windows OS.

Does anyone know why this is? what should we do?

Thanks.
Issue 1:
Electron version:1.4.14

Operating system: mac v10.12.3

Expected behavior

setting BrowserWindow options frame false

browser Top frame zone

There is an invisible window

i want work css cursor:pointer

my option code

mainWindow = new BrowserWindow({
show: false,
frame: false,// look
title: "",
useContentSize: false,
width: mainWindowWidth,
minWidth: mainWindowWidth,
height: mainWindowHeight,
minHeight: mainWindowHeight,
maximizable:false,
fullscreenable:false,
icon: iconPath
});

Issue 2:
Electron version: 1.4.1

Operating system: Mac with retina display

Step to reproduce:

create a frameless window on a retina device

put an element at the very top, say a div, and set the cursor type to pointer

observe that the cursor does not always change to a 'pointer' type

I have a video here for demo purpose: https://youtu.be/yFZayteopgg

The video demonstrated the issue on Mac, but it's also reproducible on Windows, and on Windows it's worse because not only the cursor type does not change, the click event won't register either. Thus it's impossible to correctly implement close/maximize/minimize buttons with CSS.

Notice it's only reproducible on hi dpi devices, everything seems to work correctly on regular displays.

the demo in the video is made by adapting the frameless window example in the electron api demo app.
Issue 1:
Would it be possible to utilize APP_ENV variable when running yarn encore?

So instead of yarn encore dev or yarn encore production I would do yarn encore.

More explicit option would be yarn encore env that selects dev or production based on APP_ENV.

This would avoid duplication of install/deploy configurations between production and development.

Rest of Symfony is doing that already.

Issue 2:
Symfony version(s) affected: 4.1.1 (at least)

Description

I tried to decorate the serializer, but it's not possible; I get an exception:

Circular reference detected for service "App\Serializer", path: "App\Serializer -> App\Serializer.inner -> App\Serializer".

How to reproduce

With a fresh website skeleton, add this commit: lyrixx/test@f6e27f5

I tried to decorate the Router, in order to ensure the decoration system works as expected, and it works well. So I think there is something special with the serializer, but I don't know what :/

Note: Actually, I don't need this at all, I found that while trying to help someone
Issue 1:
I would like to apply a directive conditionally through something like [class.draggable]="someBool" with '.draggable' as the selector on the directive, but this is not supported. What then is the recommended way to conditionally apply a directive on an existing element? Do I use an attribute for the selector and pass in the boolean as an input (i.e. the directive is always "active")? I'd prefer not to use ng-ifs with duplicate elements everywhere. Is there a cleaner way to attach and detach a behavior?

Issue 2:
The metadata extractor allows this:

export function FACTORY(parentDispatcher: ViewportRuler) {
return parentDispatcher || new ViewportRuler();
};

But not this:

export const FACTORY = (parentDispatcher: ViewportRuler) => {
return parentDispatcher || new ViewportRuler();
};

The latter results in

Error: Error encountered resolving symbol values statically.
Function calls are not supported.
Consider replacing the function or lambda with a reference to an exported function
(position 59:48 in the original .ts file),
resolving symbol VIEWPORT_RULER_PROVIDER_FACTORY in...

Note from @chuckjaz:

The reason we don't today is because we blindly inline local references.
What we should should only conditionally inline (simplify) exported constants.
Issue 1:
PHP Fatal error: Can't inherit abstract function Symfony\Component\HttpKernel\Log\LoggerInterface::alert() (previously declared abstract in Psr\Log\LoggerInterface) in /home/olaurendeau/git/lafourchette-core/vendor/symfony/symfony/src/Symfony/Bridge/Monolog/Logger.php on line 23

Symfony interface LoggerInterface seems to conflict with Psr interface LoggerInterface .

Between Symfony class Logger

class Logger extends BaseLogger implements LoggerInterface, DebugLoggerInterface

And freshly updated Monolog class Logger

class Logger implements LoggerInterface

Issue 2:
As of today, we have a LoggerInterface declared in the HttpKernel component. This can be problematic for components that need a logger but do not depend on HttpKernel.

There are several options here to fix this "issue":

1/ Let the FIG group decide on an interface and rely on the FIG package that would declare this interface (keep in mind that we need to have something stable by the end of December for Symfony 2.2);

2/ Create a new Symfony component with just the LoggerInterface file;

3/ Remove the interface altogether and rely on Monolog instead;

4/ Create a Symfony Logger component that support both Monolog and the Zend Logger;

5/ Do nothing.

see #5911 for the start of the discussion.

I tend to prefer option 3 for the many reasons:

If we had created a Logger component when we decided to create Monolog (switching from the Zend Logger at that time), we wouldn't have this discussion about this today. So, I like to think of Monolog as being the Symfony Logger component;

There aren' that many other logger libraries in PHP and this is not the kind of problems that need to have the flexibility to be replaced by something else;

Monolog is flexible enough to cover all the use cases you will ever need;

If this is a must, we can also add support for the Zend Logger library within Monolog (@Seldaek agreed with this possibility);

Thanks to Composer, relying on an external library like Monolog is not a problem anymore.
Issue 1:
Function redirect returns the wrong type according to mypy:

# file "redir.py"
from flask import Response, redirect
def something() -> Response:
return redirect("https://wikipedia.org/")

Then mypy complains:

redir.py:3: error: Incompatible return value type (got "werkzeug.wrappers.response.Response", expected "flask.wrappers.Response")
Found 1 error in 1 file (checked 1 source file)

Function redirect should return a flask.wrappers.Response.

Environment:

Python version: 3.8.10

Flask version: 2.1.2

Issue 2:
I am not sure if this is a bug in Sphinx, but stuff like the root_path and static_url_path attributes/properties from _PackageBoundObject end up not documented in the API page of the docs. api.rst just contains this:

.. autoclass:: Flask
:members:
:inherited-members: