WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
If you know how to fix the issue, make a pull request instead.

I tried using the @types/pino 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: @psnider @BendingBender @screendriver @paambaati @alferpal @mortiy

There seems to be an issue with the versioning of the @types/pino package. The latest is listed as 5.8.5, however there was a release of 5.20.0 about 6 months ago which takes precedence versioning wise, so if users are using "@types/pino": "*" they're getting the 5.20.0 version. Anyway that the latest can just be bumped to something higher. Thanks.

Richard

Issue 2:
Using the @types/react package and had problems.

Using the latest stable version of tsc@3.2.2.

After patch upgrade from 16.7.18 to 16.7.19, tsc command in my project is failing with the following error:

node_modules/@types/react-dom/node_modules/@types/react/index.d.ts(2667,14): error TS2300: Duplicate identifier 'LibraryManagedAttributes'.
node_modules/@types/react/index.d.ts(2682,14): error TS2300: Duplicate identifier 'LibraryManagedAttributes'.
error Command failed with exit code 1.

I am not sure whether the issue lies as I am not explicitly using LibraryManagedAttributes in my project, hence logging this ticket.

Thanks.
Issue 1:
when i pin windows terminal to taskbar, i would like to have access to adminstrator mode.

please add run as aminstrator in right click on icon in taskbar

Issue 2:
Environment

Hi, Recently I installed to PL/1 compiler from Iron-Spring http://www.iron-spring.com/index.html for Linux in the New Windows Terminal under WSL(Windows Subsystem for Linux), But I heard from certain online forums that the WSL of Windows will support only 64-bit executables and no 32-bit executables, Unfortunately the above-mentioned PL/1 compiler is a 32-bit compiler, so I tried to many times to get that working, but unable to do so, and I kept on getting the below error,

-bash: ./plic: cannot execute binary file: Exec format error

To you have any plans to implement the feature to support 32-bit executables in WSL and also in the final version of Windows New Terminal 1.0? If so when?

Also technically we cannot execute a 64-bit executable on a 32-bit operating system, but the other way round should be possible with certain minor changes in the system,

At last, I achieved the above action using some additional installation given in the below link,

microsoft/WSL#2468 (comment)

Steps to reproduce

Try to execute a 32-bit executable you will get this error.

Expected behavior

The windows terminal should execute 32-bit executables without throwing any error

Actual behavior

The windows terminal throws a blank error without proper error descritption when a 32-bit executable is tried
Issue 1:
Hi guys, my settings shows up and then goes back. I really don't know where does the program start from, please would someone provide the drawing to get an idea so that i could fix the issue. Even while debugging i can't see the settings show up. Someone please help me.

Issue 2:
Environment

W10 Pro V1903 Build 18362.295

PowerToys: 0.11.0

Settings Screen

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

Just installed and attempted to open settings. Screen is totally blank/empty.

I 'repaired - same issue.

Uninstalled, reboot and reinstall - same issue.

Expected behavior

Expect to see config options

Actual behavior

Blank window.

Screenshots

https://i.imgur.com/a7oWKgp.png
Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

When rendering with a suspense config, time spent before rendering appears to be subtracted from the timeout of the suspense config. If I spend 1 second before triggering an update with a suspense config with a timeout of 2 seconds, it takes only 1 second before the tree suspends.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

Open PR with failing test (#17015)

Create CodeSandbox with example (https://codesandbox.io/s/suspense-config-test-sw3fn)

In the sandbox, any time spent before click "Next page", reduces the time the pending state is shown before suspending. If you wait longer than 2 seconds, it immediately suspends.

What is the expected behavior?

I would expect the timeout of the suspense config to count from when the update is triggered.

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

Any version that allows rendering with a suspense config

Issue 2:
I was playing around with some unstable Suspense APIs and noticed this strange behaviour when using React.unstable_withSuspenseConfig.

If I understood correctly, the purpose of timeoutMs field is to tell React: "I'm okay with this update to not happen within this time. Then you can show fallback."

What it actually says is: "I'm okay with this update to not happen within this time since previous update." Meaning if nothing happened for some time, fallback will show up immediately.

Here's this case reproduced in sandbox: https://codesandbox.io/s/romantic-chebyshev-n59dk

Fun thing I noticed: it works as expected if I repeatedly perform updates anywhere in my App. So it may be hard to catch in real world.

My (unfamiliar with codebase) theory is that expiration time for my update is based on last update (commit?) time, but should've been based on the time it was triggered??

I know that this is unstable API and I might be misunderstanding something. Hope my case helps!

React 16.10.1

Tested on MacOS 10.4: Safari 13.0.1, Chrome 77
Issue 1:
Add support to FancyZones editor for pixel coordinates to allow for fine-grained FancyZones setups

The idea is to describe/configure the FancyZone rectangles as origin + dimensions in pixels in the UI.

This would help for video streaming and screen sharing setups, that just want to share parts of the screen, but have accurate window place. An example usage is in conjunction with OBS Studio and the crop screen feature (I am already using it like, but configuring the zones visually is prone to a lot of try and error).

If the amount of work for this is reasonable, I'd also love to help contributing this feature.

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

Issue 2:
Summary of the new feature/enhancement

Sizing of custom zones in editor by dragging mouse is a little bit coarse (hit and miss) in terms of getting close to edges of screen symmetrically and allowing window edges of multiple zones to line up neatly. Some possible solutions are suggested for consideration.

Proposed technical implementation details (optional)

Perhaps have an option for the editor to snap to a grid of user specified n pixels.

Perhaps have optional ability to input window dimension and position directly in both absolute terms (n x n pixels) and in terms of percentage of screen width and height.
Issue 1:
Using function shorthand in Object literals:

var store = {
save() { },
load() { },
delete() { },
}

Generates this JavaScript

"use strict";

var store = {
save: function save() {},
load: function load() {},
"delete": function delete() {} };

The problem is here — delete is a reserved word and cannot be used as an identifier name in function declarations:

"delete": function delete() {} };
^^^^^^

Issue 2:
var foo = {
try() {},
throw() {},
catch() {},
switch() {},
// etc.
}

SyntaxError: Unexpected token catch
at Function (native)
at compile (https://6to5.org/repl.html:200:33)

This was working in 1.x.
Issue 1:
@RLH and I have been discussing this problem for the past week. This issue is to track our thoughts.

The current GC pacer is conservative about scheduling mutator assists and this leads to a cycle where we over-assist (use too much CPU for GC) and under-shoot the heap goal.

Specifically, GC currently assumes it may have to scan the entire live heap before the live heap size reaches the heap goal. It sets the assist ratio accordingly. If the reachable heap is growing, this conservative assumption is necessary to prevent the mutator from outpacing the garbage collector and spiraling the heap size up. However, in steady state (where the reachable heap size is roughly the same as it was the last GC cycle), this means we'll finish garbage collection when we're less than 100/(GOGC+100) of the way from the trigger to the goal (1/2 way for GOGC=100; 1/4 way for GOGC=300; etc).

You might think the trigger controller would adapt by setting the GC trigger lower in response to the over-utilization, but in fact, this drives the trigger controller into a state of persistent CPU over-utilization and heap under-shoot. Currently, the trigger controller will leave the trigger where it is if we're anywhere on the white edge between CPU utilization and heap over-shoot shown below:

The under-shoot caused by the over-assist forces the trigger controller to the left of the ideal point on this curve. Since this persists, we eventually settle well to the left of the ideal, repeatedly setting the trigger too close to the goal, which leads to the next cycle setting a high assist ratio and again finishing early.

This is particularly visible in applications with a high allocation rate and/or high GOGC.

Issue 2:
by dop251:

What steps will reproduce the problem?

1. Create a package with the following code:

package bug

type S struct {}

func (s *S) test() {
goto end
end:
return
}

2. Create another package that imports the first one:

package importbug

import (
_ "bug"
)

3. Run 'go install' on that package

What is the expected output?

none

What do you see instead?

./bug.go:4: syntax error: unexpected <

Which compiler are you using (5g, 6g, 8g, gccgo)?

Which operating system are you using?

Linux/amd64

Which version are you using? (run 'go version')

1.2

Please provide any additional information below.
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

Current Behavior

I have prettier-plugin-packagejson installed (which has sort-package-json@1.51.0 as a dependency)

And trying to run npx sort-package-json@1.48 because I want to use version 1.48, before this tragic PR was merged

But npx picks up version 1.51.0 which is in my local deps, and in PATH. But it's the wrong version.

Expected Behavior

npx should make sure that it's running version 1.48, as requested.

Steps To Reproduce

Make sure sort-package-json is not installed globally (npm rm sort-package-json)

Make sure it's not in PATH: which sort-package-json should not return anything

Do npm init

Add these two scripts in package.json:

"z": "should be last",
"a": "should be first"

Do npm i prettier-plugin-packagejson

Run npx sort-package-json@1.48

Observe scripts still not sorted, because 1.51 was used (cat package.json, see "z" will be still before "a")

Optional:

Remove local deps: rm -rf ./node_modules/

Run npx sort-package-json@1.48 again

Observe scripts are now sorted because 1.48 was used (cat package.json, see "a" will be before "z")

Environment

OS: Ubuntu 20 (WSL)

Node: 16.7.0

npm: 7.19.0

Issue 2:
Current Behavior:

running npx @package@version generate it with the current install version

Expected Behavior:

it should be generated with the given version

Steps To Reproduce:

ex. steps to reproduce the behavior:

run npm i -g npm@latest to install npm 7

run npx @angular/cli@next new

answer all questions of the angular cli, it doesn't matter what the answers are

it will install angular 11 (while next is 12)

Environment:

OS: Windows 10

Node: 14.16.1

npm: 7.12.0 (working fine with 6.14.13)
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: xxx

Operating System version: xxx

Java version: xxx

Steps to reproduce this issue

xxx

xxx

xxx

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.6.2

Operating System version: x86_64 GNU/Linux

Java version: 1.7.0_80

Step to reproduce this issue

IPV6-zookeeper 连接地址：修改provide端连接zookeeper-IPV6的地址

2.启动错误信息：

java.lang.NumberFormatException: For input string: ":d243:1eff:fefa:8a47]:12189"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[?:1.7.0_80]
at java.lang.Integer.parseInt(Integer.java:492) ~[?:1.7.0_80]
at java.lang.Integer.parseInt(Integer.java:527) ~[?:1.7.0_80]
at com.alibaba.dubbo.common.URL.valueOf(URL.java:239) ~[dubbo-2.6.2.jar:2.6.2]
at com.alibaba.dubbo.common.utils.UrlUtils.parseURL(UrlUtils.java:68) ~[dubbo-2.6.2.jar:2.6.2]
at com.alibaba.dubbo.common.utils.UrlUtils.parseURLs(UrlUtils.java:137) ~[dubbo-2.6.2.jar:2.6.2]
at com.alibaba.dubbo.config.AbstractInterfaceConfig.loadRegistries(AbstractInterfaceConfig.java:190) ~[dubbo-2.6.2.jar:2.6.2]
at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:356) ~[dubbo-2.6.2.jar:2.6.2]
at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:317) ~[dubbo-2.6.2.jar:2.6.2]
at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:216) ~[dubbo-2.6.2.jar:2.6.2]
at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:123) ~[dubbo-2.6.2.jar:2.6.2]
at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:49) ~[dubbo-2.6.2.jar:2.6.2]
Issue 1:
Issue originally reported by @babel-bot in babel/babylon#306

Original issue submitted by @gsathya in #5145

Input Code

result = { __proto__: x, __proto__: y } = value;

Babel Configuration (.babelrc, package.json, cli command)

presets - latest

Expected Behavior

No error

Current Behavior

Error: Redefinition of __proto__ property

Possible Solution

Context

Your Environment

software
version

Babel

node

npm

Operating System

Issue 2:
Bug Report

Current Behavior

TypeError: Property types[0] of UnionTypeAnnotation expected node to be of a type ["FlowType"] but instead got "TSTypeAnnotation"
at validate (/work/node_modules/@babel/types/lib/definitions/utils.js:128:13)
at validator (/work/node_modules/@babel/types/lib/definitions/utils.js:97:7)
at Object.validate (/work/node_modules/@babel/types/lib/definitions/utils.js:172:7)
at validate (/work/node_modules/@babel/types/lib/validators/validate.js:17:9)
at builder (/work/node_modules/@babel/types/lib/builders/builder.js:46:27)
at UnionTypeAnnotation (/work/node_modules/@babel/types/lib/builders/generated/index.js:733:31)
at Object.createUnionTypeAnnotation (/work/node_modules/@babel/types/lib/builders/flow/createUnionTypeAnnotation.js:20:47)
at NodePath.ConditionalExpression (/work/node_modules/@babel/traverse/lib/path/inference/inferers.js:124:14)
at NodePath._getTypeAnnotation (/work/node_modules/@babel/traverse/lib/path/inference/index.js:63:20)
at NodePath.getTypeAnnotation (/work/node_modules/@babel/traverse/lib/path/inference/index.js:29:19)

Input Code

https://github.com/azz/babel-typescript-union-bug

function bug() {
const x = 1 ? a() : b();

return [...x];
}

function a(): number[] {
return [];
}

function b(): number[] {
return [];
}

Expected behavior/code

Not like this

Babel Configuration (.babelrc, package.json, cli command)

{
"plugins": ["@babel/plugin-transform-spread"],
"presets": ["@babel/preset-typescript"]
}

Environment

Babel version(s): 7.3.3

Node/npm version: 6.5.0

OS: macOS 10.14.2

Monorepo: no

How you are using Babel: cli

Possible Solution

The builder code for plugin-transform-spread is expecting a UnionTypeAnnotation instead of a TSUnionType in order to determine the type of x above, specifically in scope.toArray:

babel/packages/babel-traverse/src/scope/index.js

Lines 408 to 413
in
5bb1bb0

if (t.isIdentifier(node)) {

const binding = this.getBinding(node.name);

if (binding && binding.constant && binding.path.isGenericType("Array")) {

return node;

}

}

isGenericType ends up calling createUnionTypeAnnotation:

babel/packages/babel-traverse/src/path/inference/inferers.js

Lines 92 to 97
in
5bb1bb0

export function ConditionalExpression() {

return t.createUnionTypeAnnotation([

this.get("consequent").getTypeAnnotation(),

this.get("alternate").getTypeAnnotation(),

]);

}

Which creates a UnionTypeAnnotation, which works for Flow, but not TypeScript.
Issue 1:
Problem description

DatePicker onDismiss function called, when select date.

Here's working bin that reproduces the problem.

Materi UI version: 0.18.1

Actually, it worked fine on 0.18.0 version.

Issue 2:
Feature request

Description

I think it's ok to call dismiss function when date is changed. My case:

I have two DatePickers, when I select date from first one, it closes (autoOk prop) and then I open second picker automatically with prefilled date (based on value in first picker). If user doesn't change value in second picker, and just close it, it will trigger dismiss function. If user change date, it will trigger only handleTouchTapOk function. I think it's more logical to trigger dismiss always when open changes to false.

For now I must use same handler for onDismiss and onChange to catch this case, and I really don't like this solution.

Possible solution

before

handleTouchTapOk = () => {
if (this.props.onAccept && !this.refs.calendar.isSelectedDateDisabled()) {
this.props.onAccept(this.refs.calendar.getSelectedDate());
}

this.setState({
open: false,
});
};

after

handleTouchTapOk = () => {
if (this.props.onAccept && !this.refs.calendar.isSelectedDateDisabled()) {
this.props.onAccept(this.refs.calendar.getSelectedDate());
}

this.dismiss();
};

I can create PR for this.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.6.2

Operating System version: centos 6.8

Java version: java 8

服务在发布后，请求开始打到我们的api应用，api应用再去调后面的rpc应用，刚开始会产生大量超时，通过日志分析，时间消耗在消费者自身，并非提供者服务慢。请问消费者消费的238ms大概是什么原因导致的，请协助提供一下思路

If there is an exception, please attach the exception trace:

client elapsed: 238 ms, server elapsed: 65 ms, timeout: 300 ms

Just put your stack trace here!

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.7

Operating System version: macOS

Java version: 1.8u251

as I use dubbo spring boot , just wonder how to specify the serialization type like kryo or protobuff in @DubboService annotation ?
Issue 1:
//glide
compile 'com.github.bumptech.glide:glide:3.7.0'
compile 'com.github.bumptech.glide:okhttp3-integration:1.4.0@aar'

Device/Android Version:

Samsung Galaxy7 edge, android 6.0

meizu mx5, android 5.0

Glide.with(context)
.load(url)
.asGif()
.dontAnimate()
.placeholder(R.drawable.ic_stub)
.error(R.drawable.ic_error)
.into(imageView);

GIF will show some GIF frame is incomplete, but these GIF in the computer and other applications show no problem, so the GIF itself should be no problem.

ps:I try to use fresco no problem

Issue 2:
Hi! I'm using Glide in a Listview that loads preview images

Glide.with(activity)
.load(stringUrl)
.centerCrop()
.crossFade()
.into(imageView);

How can I fetch this loaded image file from cache?

Or better, can I set a name to a file when is saved in cache?

I know how to get cache directory that uses Glide

File cacheFile = Glide.getPhotoCacheDir();

but when I list files I see this:

/image_manager_disk_cache/ed35732ad0c7351708bd024cb2b423a055dbe79f592d48f4241940f344f2e75f.0
Issue 1:
Describe the bug

The axis arrows of the TransformControls are aligned with the component's local coordinate system, even if the default "world" space is used. Dragging the arrows still works as normal, so the movement of the object does not match the drag direction of the arrows if the transformed object is rotated.

Could be related to #21840, but does not require any parent object or snap configuration.

To Reproduce

This can be easily reproduced using the Transform Example:

Switch to Rotate mode

Rotate your object in any way

Switch back to Translate mode -> Notice that the axes are aligned to the cube, even though we are in "world" space

Drag the red arrow -> Note that the object still moves on the global X axis

Change to "local" space -> Note that the arrows are still aligned the same (correct)

Drag the red arrow again -> Movement follows the arrow (correct)

Live example

See steps explained above and the Transform Example.

Expected behavior

I believe that the arrows should be aligned to world axes in "world" space. They also have done so in past versions, IIRC.

Screenshots

Platform:

Device: Desktop

OS: Windows

Browser: Chrome, Firefox

Three.js version: r128

Issue 2:
Describe the bug

TransformControls setSpace() does not update gizmo transform as it did in Three r127.

To Reproduce

Steps to reproduce the behavior:

Go to https://threejs.org/examples/?q=transform#misc_controls_transform

Select the cube

Rotate it by ~30 degrees on one axis

Press Q to toggle world/local space

Gizmos are not updated

This is a video of trying to move the rotated cube while changing between local and world space. The transformation is applied correctly, but the gizmos are not oriented correctly.

bug.mp4

Expected behavior

Gizmos updated to match world/local space.

Platform:

Device: Desktop computer

OS: Linux Manjaro

Browser: Chrome 90

Three.js version: r128
Issue 1:
Electron Version: v2.0.2

Operating System (Platform and Version): Linux

Last known working Electron version:

Expected Behavior

while using window's background property in electron API and CSS background property I should get a similar result.

Actual behavior

I set the window's background property with color #141414 and also applied #141414 color to html, body tags with CSS but in the attached screenshot, the result isn't what I expect.

Note: the top section is CSS colored and the bottom section is native chromium background color. Also, this problem will occur while using --disable-gpu flag and well my window is frameless and in Linux by selecting a text object or something else and dragging it to out electron will crash.

Issue 2:
Electron version: 1.7.x

Operating system: macOS 10.12.5

Expected behavior

Setting a window backgroundColor should produce the same visual result as setting it via CSS.

Actual behavior

There is a slight flicker from where the background color from CSS kicks in.

How to reproduce

create a window with background color: new BrowserWindow({ width: 800, height: 600, backgroundColor: '#DDDDDD' })

in that window set the same background color via CSS: <body style="background-color: #DDDDDD;">

loadURL of the window with a slight timeout to see the difference

setTimeout(function () {
win.loadURL(url.format({
pathname: path.join(__dirname, 'index.html'),
protocol: 'file:',
slashes: true
}))
}, 2000);

The following video shows the difference clearly:

Could it be that the window backgroundColor somehow uses a different color space compared to the renderer one via CSS?