WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
PowerToys is not for 32 bit Windows. I have a 32 bit PC so this is upsetting. Please make a 32 bit version!

Environment

Windows build number: [run "ver" at a command prompt]
PowerToys version:
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

Issue 2:
Summary of the new feature/enhancement

I propose a different way of thinking of FancyZones new/experimental snapping function. I appologize if this is a duplicate; I couldn't find in issue search.

The new 0.18 approach of being able to snap together zones is nice. It adds enormous flexibility in use. However, when I went to reshuffle my zone layout to take advantage of it, it became cumbersome to manage the many smaller zones I created to be able to snap together.

That also highlighted to me the current Destop Window Manager's snap-to functions (corner, left, right etc) was counter to how FancyZones works.

The DWM subdivides desktops; FancyZones combines zones.

I propose a different approach: Make fewer zones in layout setup, then subdivide them at use time. Exactly the same way DWM subdivides a desktop.

Proposed technical implementation details (optional)

Example use:

FancyZones Layout: 4K monitor subdivided to 3 columns.

FancyZones User input: Drag window near top-right corner of middle column.

FancyZones Response: Snaps window to top-right quadrant of middle column.
Issue 1:
if druid.server.maxSize is set smaller than the size of druid.segmentCache.locations, then the druid console gets really confused when at capacity, and claims that the server has negative bytes remaining.

Issue 2:
The rules for determining available space on a historical node for a segment seem to include both druid.server.maxSize and druid.segmentCache.locations:maxSize.

However, the Coordinator Console shows the Max Size and Percent Used based only on druid.server.maxSize.

It would be useful if the console showed both values to help diagnose "segment too large" errors thrown by the OmniSegmentLoader (when people accidentally set them to different values).

See https://groups.google.com/forum/#!searchin/druid-development/segment$20too$20large/druid-development/w8Q65ZRusi4/kN0JybUtUfAJ
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

Current Behavior

Deletes git repository.

(Removed .git and tracked files)

Expected Behavior

Install without error

Steps To Reproduce

Clone https://github.com/kdy1/swc.git

Checkout resolver branch

npm i

npm run build:dev

npm link

npm i -g @swc/cli

Environment

OS: macOS Big Sur

Node:

➜ swc-bugs node -v
v14.16.1

Note: I installed latest version of node js because of stack trace issue on github actions.

➜ swc-bugs brew info node
node: stable 16.3.0 (bottled), HEAD
Platform built on V8 to build network applications
https://nodejs.org/
/usr/local/Cellar/node/14.4.0 (107 files, 650KB)
Built from source
/usr/local/Cellar/node/15.12.0 (3,268 files, 55.5MB)
Poured from bottle on 2021-03-31 at 15:11:58
/usr/local/Cellar/node/16.2.0 (2,784 files, 49MB) *
Poured from bottle on 2021-05-30 at 20:06:55
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/node.rb
License: MIT
==> Dependencies
Build: pkg-config ✔, python@3.9 ✔
Required: brotli ✔, c-ares ✔, icu4c ✔, libuv ✔, nghttp2 ✔, openssl@1.1 ✔
==> Options
--HEAD
Install HEAD version
==> Analytics
install: 323,426 (30 days), 1,082,930 (90 days), 4,400,808 (365 days)
install-on-request: 254,200 (30 days), 847,506 (90 days), 3,304,651 (365 days)
build-error: 0 (30 days)

npm:

npm@7.14.0 /Users/kdy1/.nvm/versions/node/v14.16.1/lib/node_modules/npm

Issue 2:
Note that this same issue was reported back in 2017 on the now-archived repo: npm/npm#15783

Current Behavior:

I am using npm link to try to test changes I am making to an upstream dependency within my own project. In the dependency directory I run npm link. Then in my own project I run npm link ffmpeg-stream.

NPM gives the following error message when running the second link command:

npm ERR! code 1
npm ERR! path D:\git\node-ffmpeg-stream
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c "tsc"
npm ERR! Version 3.9.7
npm ERR! Syntax: tsc [options] [file...]

Afterwards, the directory of the upstream dependency is empty. Even the .git directory is deleted, so tough luck if you haven't pushed recently.

Expected Behavior:

NPM link should link the package without issue. If an error is encountered, NPM should not delete the entire folder contents.

Steps To Reproduce:

Clone https://github.com/JoshuaWalsh/node-ffmpeg-stream/

Clone https://github.com/JoshuaWalsh/subtitle-indexer

In node-ffmpeg-stream, run npm ci --include=prod

In node-ffmpeg-stream, run npm link

In subtitle-indexer, run npm link ffmpeg-stream

Observe that the node-ffmpeg-stream directory is now empty. (A small number of files may remain if they were in use at the time and couldn't be deleted)

Environment:

OS: Windows 10 Pro 10.0.19042

Node: 15.0.1

npm: 7.0.3

I am using nvm-windows to manage NodeJS, but currently only have one version installed.
Issue 1:
ℹ Computer information

PowerToys version: 0.23.0

PowerToy Utility: Installer

Running PowerToys as Admin: -

Windows build number: [run "winver"] 19041.508

📝 Provide detailed reproduction steps (if any)

Have a (relatively) new windows, where powertoys was never installed before

Download exe from github

Click install as normal user

Wait very, very long - the install never finishes.

✔️ Expected result

Have a quick install experience, with powertoys being available after the install.

❌ Actual result

A very slow install notification in the message pane (or whatever its called), which finally will stall at 99%.

Workaround

Fix this by installing 0.21.1 first, and then upgrade from there

Issue 2:
ℹ Computer information

Windows build number: Microsoft Windows [versão 10.0.18363.959]

PowerToys version: 0.20.0

PowerToy module: Installer

📝 Provide detailed reproduction steps (if any)

Download v0.20 Installer

Install

✔️ Expected result

Instalation done successfully

❌ Actual result

The instalation gets stuck in 75%. Tried the mentioned in theses answers, but didn't work: #5397 (comment)

#5397 (comment)

📷 Screenshots

Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form
Issue 1:
Electron version: 3.0.0-beta.1 to 10

Operating System: Windows

Expected Behavior

Shortcuts should be properly displayed in the the app menu.

Actual behavior

Using CommandOrControl+Shift+O shortcut, the menu entry shortcut should be shown as 'Ctrl+Shift+O', but "Ctrl+O" is displayed instead. The shortcut works fine though.

Same problem with roles. For instance forcereload will show Ctrl+R instead of Ctrl+Shift+R. Again, the shortcut works fine here.

To Reproduce

Simply change a shortcut or a role in the electron-quick-start menu.

Additional Information

Was working fine with latest 2.x version of electronjs.

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

Current master

dynamic import is not supported while it is supported in NodeJS Modules and CJS

Electron Version:

Operating System:

Last Known Working Electron version:

Expected Behavior

import('') loads ESM and CJS

Actual Behavior

Does Error when loading ESM and CJS

To Reproduce

use import('./your-url.js')

Screenshots

Additional Information
Issue 1:
I get these errors pretty frequently:

Uncaught RangeError: Maximum call stack size exceeded /Applications/Atom.app/Contents/Resources/app/node_modules/emissary/lib/behavior.js:44

EDIT: Restarting atom fixes this, of course. Thankfully, I'm still able to save my files too. I just can't really move the cursor or select text anymore.

Issue 2:
I learned this method when i was playing with DSL ages ago

you can highlight text then middle click to paste under linux (yes i get ticked every time i try this on MS Windows and get nothing)

anyway i have only had this issue in 2 places on linux, this application and firefox's scratchpad
Issue 1:
Is there a way to register additional "resultDataContents" values? Or would it be possible to create such a mechanism?

I want to use the transactional endpoint, but return additional data (specifically the ID, labels/type - like the "graph" resultDataContents) in the tabular/structured form of the "rows" type.

Issue 2:
I've currently got an ugly workaround in place to get the labels for a node returned in the transactional HTTP endpoint REST format that calls the URI for labels. It would be awesome if there were a format that had (all in one response):

node id

labels--one big list

properties

nothing else; no bloat!
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: v5.0.1

Operating system: MaxOS 10.14.4

Expected Behavior

As doc https://electronjs.org/docs/api/shell#shellopenexternalurl-options

Actual Behavior

Link opened in the browser, but the browser is not brought to the foreground.

To Reproduce

Upgrade electron to v5.0.1 in https://github.com/electron/electron-api-demos

And try "open external links" demo

Issue 2:
Electron version: 1.4.7

Operating system: Mac OS 10.11.6 & Ubuntu 14.04

Expected behavior

Garbage collector should clean memory.

Actual behavior

Memory usage increases rapidly in Main process. Eventually app performance will degrade until unusable.

How to reproduce

const path = require('path');
const {app, BrowserWindow} = require('electron');
app.disableHardwareAcceleration();

app.once('ready', () => {
const win = new BrowserWindow({
width: 4096,
height: 3072,
useContentSize: true,
enableLargerThanScreen: true,
show: false,
frame: false,
hasShadow: false,
transparent: true,
webPreferences: {
devTools: false,
webSecurity: false,
textAreasAreResizable: false,
defaultEncoding: 'utf8',
backgroundThrottling: false,
offscreen: true,
zoomFactor: 1,
experimentalFeatures: false,
experimentalCanvasFeatures: false
}
});

let index = 0;
const sizes = [
{width: 1024, height: 768},
{width: 2048, height: 1536},
{width: 4096, height: 3072}
];

win.loadURL('https://www.apple.com');
win.webContents.setFrameRate(60);
win.webContents.once('dom-ready', () => {
setInterval(() => {
if (index === sizes.length) {
index = 0;
}
const size = sizes[index++];

// changing the window size causes the memory leak
win.setSize(size.width, size.height, false);
}, 100);
})
});
Issue 1:
Trying to define an empty trait:

trait Foo {}

produces a confusing message about Self:

unnamed.rs:1:1: 1:13 error: parameter `Self` is never used
unnamed.rs:1 trait Foo {}
^~~~~~~~~~~~
unnamed.rs:1:13: 1:13 help: consider removing `Self` or using a marker such as `core::marker::PhantomFn`
error: aborting due to previous error

It appears that the compiler is internally treating the trait as though it had a type parameter defined called Self, and then complaining about the parameter being unused. But from the user's perspective there is no such parameter, and the suggestion to remove it is nonsense. The error message should be adjusted to recognize when it's complaining about Self and to explain itself better.

Issue 2:
Given the input

trait T {}

rustc will complain:

<anon>:2:1: 2:11 error: parameter `Self` is never used
<anon>:2 trait T {}
^~~~~~~~~~
<anon>:2:1: 2:11 help: consider removing `Self` or using a marker such as `core::marker::PhantomFn`
<anon>:2 trait T {}
^~~~~~~~~~

This may just be a diagnostics issue, but I'll let someone more familiar with Rust make that judgement.
Issue 1:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
2.8.*

No validation violation occurs on invalid values in EntityType.

This seems to be because EntityType uses ORMQueryBuilderLoader, and it's getEntitiesByIds does not validate that the number of inputs matches the number of outputs. It only does an SQL WHERE IN (provided IDs) query to get whatever values are valid.

To replicate - add an entity in the form type on the form, then either manually delete the entity in the database before submitting, or manipulate the request (POST) data to have invalid values on submit. The invalid values just drop, the valid values remain, and no validation error is raised.

I'm breaking this out from #17488 as that ticket is specifically addressing that it causes exceptions when using PostgreSQL; however, the bigger issue is that invalid values don't raise any validation.

This is not easy to workaround because $queryBuilder in ORMQueryBuilderLoader is private rather than protected, so the variable and every method in the class needs to be duplicated.

Issue 2:
Working through some tests using the bundled Security functionality, and we have noticed that on a logout action we are getting in our server logs:

[Mon Oct 29 16:43:14 2012] [error] [client xxx.xxx.xxx.xxx] PHP Fatal error: Uncaught exception 'ErrorException' with message 'Warning: SessionHandler::write(): Parent session handler is not open in /web_dir/app/cache/dev/classes.php line 558' in /web_dir/app/cache/dev/classes.php:558\nStack trace:\n#0 [internal function]: Symfony\\Component\\HttpKernel\\Debug\\ErrorHandler->handle(2, 'SessionHandler:...', '/web_dir...', 558, Array)\n#1 /web_dir/app/cache/dev/classes.php(558): SessionHandler->write('e0ua5bnj0vneq97...', '_sf2_attributes...')\n#2 [internal function]: Symfony\\Component\\HttpFoundation\\Session\\Storage\\Proxy\\SessionHandlerProxy->write('e0ua5bnj0vneq97...', '_sf2_attributes...')\n#3 [internal function]: session_write_close()\n#4 {main}\n thrown in /web_dir/app/cache/dev/classes.php on line 558

It seems this issue isn't unique to us as seen at:

https://groups.google.com/forum/?fromgroups=#!topic/symfony-devs/Q-f0lKT7OZ8

We are running a centos 6 machine running PHP v5.4.7 and Apache/2.2.15.

Anyone have any suggestions as to what is causing this and how we can eliminate this message on every log out?
Issue 1:
Version

2.5.16

Reproduction link

https://jsfiddle.net/50wL7mdz/337120/

Steps to reproduce

open console

click todo item

you will see destroyed and updated

What is expected?

only destroyed is printed.

updated life cycle should not be invoked after component has been destroyed.

What is actually happening?

updated life cycle invoked after component has been destroyed.

Issue 2:
What problem does this feature solve?

Consider the <input> element. It maintains its own internal state for its value (by the browser) irrespective of whether or not it is being driven by v-model.

After looking at some Vue component libraries, most of the components externalize their state through props, meaning that the parent component must define the value for that component in its data and use v-model to wire it up -- the component cannot be used without v-model because it doesn't maintain the state internally to the component.

Ideally I'd like to author input components that satisfy the following requirements:

Can be used without v-model (the component maintains the state itself)

Can be used with v-model (the state is driven entirely by the prop emitting input events)

This results in somewhat messy code like this:

Vue.component('checkbox', {
template: '<div class="checkbox" @click="toggle">{{ internalValue ? "Checked" : "Unchecked" }}</div>',

props: {
value: {
type: Boolean,
default: false,
},
},

data() {
return {
internalValue: false,
};
},

watch: {
value: {
immediate: true,
handler(value) {
this.internalValue = value;
},
},

internalValue(internalValue) {
this.$emit('input', internalValue);
},
},

methods: {
toggle() {
this.internalValue = !this.internalValue;
},
},
});

In order to distinguish between the prop and the data, I've used value and internalValue respectively. The problem is that value is rarely used in the code (it's only used in the watcher) and I have to remember to use internalValue throughout the component's code and template instead of value (since internalValue is the mutable source of truth).

To avoid this, I could instead name the prop externalValue and the data value, but now I would have to use <checkbox :external-value="x"> which is not ideal (the external prop should be called simply "value").

I'm proposing a feature in which you can specify what internal name a prop should be exposed as within the component without changing the external name of that prop in templates (kind of like how method arguments work in objective-c).

What does the proposed API look like?

Vue.component('foo', {
props: {
value: {
internalName: 'valueProp',
},
},

template: '<div>{{ valueProp }}</div>',
});

<foo value="bar">
Issue 1:
Challenge change-the-color-of-text has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0.

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

<h2 style="color: red">CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

Issue 2:
Challenge change-the-color-of-text has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0.

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

<h2>CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

<h2>CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

<h2 style="colr:red;">CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

<h2 style="colr:red;">CatPhotoApp</h2>

<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

This had previously passed. Resubmitted now its failing. Cleared my code and tried to reenter now it doesnt accept the code at all. It resents and clears my text inputed when I click run code.
Issue 1:
Could we get Swift's dot notation for enum values?

It is very cumbersome to import an enum declaration and having to write them in function calls:

// ABC.ts
export const enum ABC {
A,
B,
C,
}

export function testABC(abc: ABC) {
}

// test.ts
import { ABC } from './ABC';
import { testABC } from './ABC';

// it is very cumbersome to import ABC and type ABC.
testABC(ABC.A);

Swift introduced the most laziest way to write them. It would be good if TS could support it also.

// test.ts
import { testABC } from './ABC';
testABC(.A);

Here is an another example with a switch statement, where you don't need to write ABC on every case:

import { ABC } from './ABC';
let abc: ABC;
switch (abc) {
case .A:
break;
case .B:
break;
case .C:
break;
}

Issue 2:
Porting over this issue from:http://typescript.codeplex.com/workitem/260.

This is a request to add support for get/set accessors in interfaces. This would allow the interface to define the ability of the interface. For example, in the case where the property is read-only, "get" keyword in the interface would indicate that the property is read-only.
Issue 1:
Stacktrace here:

https://gist.github.com/ssfrr/248bd3f34a31456acea457756ce4feb6

I can reproduce reliably with LibSndFile master on Win64.

using LibSndFile
buf = LibSndFile.load("C:\\Users\\sfr\\Dropbox\\chris_mann.wav") # use your own wav file here

Versioninfo:

Julia Version 0.7.0-rc2.0
Commit 78540cba4c (2018-08-02 19:14 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.0 (ORCJIT, skylake)
Environment:
JULIA_NUM_THREADS = 2

Issue 2:
This script works fine on 0.6, but segfaults on master:

using Base.LinAlg
using Base.LinAlg.BLAS: libblas, BlasInt, @blasfunc

function gemm!(transA::Char, transB::Char, M::Int, N::Int, K::Int, alpha::(Float64), A::Ptr{Float64}, B::Ptr{Float64}, beta::(Float64), C::Ptr{Float64})
if transA=='N'; lda=M; else; lda=K; end
if transB=='N'; ldb=K; else; ldb=N; end
ldc = M;
ccall((@blasfunc(dgemm_), libblas), Void,
(Ptr{UInt8}, Ptr{UInt8}, Ptr{BlasInt}, Ptr{BlasInt},
Ptr{BlasInt}, Ptr{Float64}, Ptr{Float64}, Ptr{BlasInt},
Ptr{Float64}, Ptr{BlasInt}, Ptr{Float64}, Ptr{Float64},
Ptr{BlasInt}),
&transA, &transB, &M, &N, &K,
&alpha, A, &lda, B, &ldb, &beta, C, &ldc)
end

x = zeros(12, 4)
w = zeros(2, 2, 1, 1)
y = zeros(4, 3, 1, 1)

gemm!('N','N',12,1,4,1.0,pointer(x),pointer(w),0.,pointer(y))

➜ NNlib.jl git:(julia-0.7) ✗ j --depwarn=no test.jl

signal (11): Segmentation fault
in expression starting at /home/mike/projects/flux/NNlib.jl/test.jl:21
_ZNK4llvm5Value16DoPHITranslationEPKNS_10BasicBlockES3_ at /home/mike/projects/julia/usr/bin/../lib/libLLVM-6.0.so (unknown line)
Allocations: 341387 (Pool: 341240; Big: 147); GC: 0
[1] 3837 segmentation fault (core dumped) j --depwarn=no test.jl

Tried some older versions and it doesn't seem to be recent (e.g. newoptimizer related).
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-link-to-external-pages-with-anchor-elements has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

When attempting to Run a test, the checklist below the button disappeared, and will not re-appear when trying to Reset. It does, however, re-appear when refreshing the browser page.

Issue 2:
Waypoint hints do not always appear after the page has loaded. Refreshing the page does not always seem to work. Closed & reopened browser does not seem to change behaviour. Issue is not specific to certain waypoints but started to occur in the jQuery section.

Issue experienced on Chrome 44.0.2403.55 on Windows 8.1. Attached screenshot for clarity.
Issue 1:
Sublime Text has the option:

// Set to "none" to turn off drawing white space, "selection" to draw only the
// white space within the selection, and "all" to draw all white space
"draw_white_space": "selection",

I would like to see selection added to list of possible values for editor.renderWhitespace. I find it incredibly useful.

While writing code, I prefer to not show whitespace. However, when I copy-paste code snippets, I like to know the whitespace matches the target document by simply selecting it (usually via Ctrl+A), not using the arrow keys or toggling a setting.

Thanks

Issue 2:
Hey,

methods in POJOs don't autocomplete like here:

var foo = {
bar() {
}

baz() {
this.bar<ctrl+space>
}
}

although it works just fine for ES6 classes:

class Foo {
bar() {
}

baz() {
this.bar<ctrl+space>
}
}

BR

Dominik