WhereIsAI/github-issue-similarity huggingface dataset:
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 rest服务，dubbo消费端用jar接口访问没有问题，如果非dubbo的客户端，怎么知道路径信息，zk上注册相关信息，？？？

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

Operating System version: centos-6

Java version: 1.7.0_71

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?

[DUBBO] Thread pool is EXHAUSTED! Thread Name: DubboServerHandler-xxxx, Pool Size: 100 (active: 0, core: 100, max: 100, largest: 100), Task: 8960329 (completed: 8960329), Executor status:(isShutdown:false, isTerminated:false, isTerminating:false), in dubbo://xxxxxxx:xxxx!, dubbo version: 2.5.3, current host: xxxxxxxxxx

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

Just put your stack trace here!
Issue 1:
Electron version: 1.2.5

Operating system: Windows 10

let win = new BrowserWindow({height: 600, width: 680})

As a result of win.show() i get BrowserWindow with 664px width(-16 px of actual width value)

Issue 2:
The Browser Window width and x coordinates are being calculated incorrectly in Windows 10 (Windows 8.1 did not have this problem). Here you can see that the getBounds() function is showing that my x value is 0 but the desktop background is showing through. I'm guessing this may have something to do with a subtle shadow that each window in Windows 10 is now casting.

Not sure how to fix this, but would be nice to resolve as I have some window state management code written to pin windows in the correct location, and now they are not properly being positioned.
Issue 1:
Hi all,

I am trying to run julia from multiple machines (bash launches multiple julia instances from various machines) and all share the same home dir.

The issue is that each machine recompiles the stale cache. (All are share the same package dir). Is this an issue? Is this a known issue? Is there a solution?

Thanks

Issue 2:
The crash happens when a user tries to decompose a Pair using a => operator on LHS. The correct approach is to use a tuple yet it is plausible users will try this syntax. I am not sure how it is interpreted by Julia.

julia> x = :a => 1
:a => 1

julia> (a => b) = x
Pair

julia> a┌ Error: Error in the keymap
│ exception =
│ MethodError: no method matching isless(::Symbol, ::Int64)
... (REPL crashes) ...

More context:

julia> versioninfo()
Julia Version 1.6.3
Commit ae8452a9e0 (2021-09-23 17:34 UTC)
Platform Info:
OS: Linux (x86_64-pc-linux-gnu)
CPU: Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-11.0.1 (ORCJIT, skylake)
Issue 1:
VSCode Version: latest alpha

OS Version: Windows 10

Steps to Reproduce:

After working through this #4783 I removed then re-added my node_modules folder from .gitignore

Go to the Git tab and clean all (266 files in my case)

Actual:

Caused VS Code to hang

Issue 2:
var and let at the head of variable names and property names are colored.

Version 0.10.10-insider
Commit 97d4ad1c55a82369f65078406ed770e8a34055fc
Date 2016-02-29T16:00:09.098Z
Shell 0.35.6
Renderer 45.0.2454.85
Node 4.1.1
Issue 1:
Add info about shortcut and working shortcut to every item on result list. (alt+orderID)

I guess we are powerusers :D using arrows to navigate through the list isn't the easiest way to select the result, moving hands to mouse either, so like we can use Win+number to launch a specific app from the taskbar we should be able to select the specific result from results.

Example from my fork of wox

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

Issue 2:
This sounds a bit silly, but I don't want to rely on any third party app to pin apps to the top of all other windows. This is partly because they have trashy design. Also, please add the feature to pin the app windows to the desktop. Like in windows seven, you could create sticky notes that just stayed on the desktop, even if you did "Win + D". These notes also didn't minimize when you opened another app.
Issue 1:
Duplicate of #1918

Basically the problem is if you want to do a bar plot with time series

df.plot(kind='bar')

it will create a label for every date entry instead one clean label and more dates when you zoom in.

Issue 2:
xref #5774

When time series is set as index, line plot uses the TimeSeries_DateFormatter for recognizable date formatting. However, bar plot use the FixedFormatter which outputs the datetime as it is. Can bar plot also use the DateFormatter?

In [1]: from pandas import *
In [2]: from numpy.random import *
In [3]: ts = Series(randn(100), index=date_range('1/1/2000', periods=100))
In [4]: df = DataFrame(randn(100, 4), index=ts.index, columns=['A', 'B', 'C', 'D'])
In [5]: df = df.cumsum()

In [7]: a = df.plot(kind='bar')
In [9]: a.get_xaxis().get_major_formatter()
Out[9]: <matplotlib.ticker.FixedFormatter instance at 0x108700f38>

In [11]: a = df.plot()
In [12]: a.get_xaxis().get_major_formatter()
Out[12]: <pandas.tseries.converter.TimeSeries_DateFormatter instance at 0x10877ccf8>
Issue 1:
Brice Ruth opened SPR-4506 and commented

Setting 'autoStartup' property to 'false' on ServerSessionMessageListenerContainer causes an exception during initialization of the MDP container. Basically, autoStartup prevents the Connection from being setup, but something else in ServerSessionMessageListenerContainer#doInitialize needs (or expects) that Connection to be valid.

Can provide full stack, if needed.

Affects: 2.0.5

Issue Links:

#8948 ServerSessionMessageListenerContainer102 cannot be initialized with autoStart=false ("duplicates")

Issue 2:
Julian Sareyka opened SPR-8817 and commented

I have tried to setup an in-memory db with hsql. In one of my scripts there is a stored procedure. Database setup fails when executing this script.

I found out that this is due to automatic statement splitting in ResourceDatabasePopulator. Here all statements in a script are split on semicolons. So my stored procedure is cut into pieces (after p_date_value DAY;).

CREATE FUNCTION pkg_verweildauer.get_pub_ende (IN p_pub_start TIMESTAMP, IN p_date_unit VARCHAR(255), IN p_date_value NUMERIC)
RETURNS timestamp
READS SQL DATA
BEGIN ATOMIC

DECLARE v_pub_ende timestamp;
case p_date_unit
when 'DAYS' then
SET v_pub_ende = p_pub_start + p_date_value DAY;
when 'WEEKS' then
SET v_pub_ende = TIMESTAMPADD(SQL_TSI_WEEK, p_date_value, p_pub_start);
when 'MONTHS' then
SET v_pub_ende = TIMESTAMPADD(SQL_TSI_MONTH, p_date_value, p_pub_start);
when 'YEARS' then
SET v_pub_ende = TIMESTAMPADD(SQL_TSI_YEAR, p_date_value, p_pub_start);
else
SET v_pub_ende = p_pub_start + 365 DAY;
end case;
RETURN v_pub_ende;

END;

A simple solution would be to add a parameter to the <jdbc:script> tag to disable splitting on file basis. Unfortunately ResourceDatabasePopulator cannot be exchanged in the EmbeddedDatabaseBuilder.

I had to write a post processing bean, to add the stored function.

Affects: 3.0.5

Issue Links:

#13525 Error when parsing PMS stored procedure script. ("is duplicated by")

#12356 Add configurable SQL statement delimiter to ResourceDatabasePopulator and JDBC XML namespace. ("is duplicated by")

#16310 Support EOF as statement separator in SQL scripts

#17970 Support triggers & stored procedures alongside standard statements in SQL scripts

3 votes, 2 watchers
Issue 1:
Libraries often use process.env.NODE_ENV so they can compile conditionally, but they also often try to guard against process' absence with some typeof check which BY DEFAULT is causing every consumer of the library to include i.e. process polyfill.

I think most webpack-generated code is targeting the browser and auto-polyfilling such things is at least unexpected. Its causing extra-bytes in users' bundles, but whats more troubling it causes it for UMD standalone builds too which causes serious duplication of the code which is not intended to run! And all of that often by accident.

Also while writing isomorphic libraries people often use such lines:

const asap = typeof setImmediate !== 'undefined' ? setImmediate : setTimeout

which when bundled by webpack will also include setImmediate's polyfill automatically - again by accident. And even if libraries authors are aware of this (but mostly not), certainly users are not and they do not put configurations like below while targeting browsers only and not thinking about this too much:

node: {
global: false,
process: false,
__filename: false,
__dirname: false,
Buffer: false,
setImmediate: false,
}

Issue 2:
Basically all from http://www.ecma-international.org/ecma-262/6.0/#sec-resolveexport

Star exports should not include 'default'

// entry.js
import def from './a';
console.log(def);

// a.js
export * from './b';

// b.js
export default 'b-default';

should log undefined because export * from only applies to named exports, not default. This is the main one on this list that seems like a problem, because it silently does the wrong thing, and users may accidentally rely on it.

Local exports take precedence over star exports.

// entry.js
import {foo} from './a';
console.log(foo);

// a.js
export var foo = 'a-foo';
export * from './b';

// b.js
export var foo = 'b-foo';

should log a-foo since named exports take precedence over star exports. Currently it throws because the export * from tries to redefine the non-configurable property.

Local exports take precedence over indirect exports

// entry.js
import {foo} from './a';
console.log(foo);

// a.js
export var foo = 'a-foo';
export {foo} from './b';

// b.js
export var foo = 'b-foo';

should log a-foo since named exports take precedence over indirect exports. Currently it throws because the export * from tries to redefine the non-configurable property.

Indirect exports take precedence over star exports.

// entry.js
import {foo} from './a';
console.log(foo);

// a.js
export {foo} from './c';
export * from './b';

// b.js
export var foo = 'b-foo';

// c.js
export var foo = 'c-foo';

should log c-foo because indirect exports take precedence.
Issue 1:
Bug report

Describe the bug

pages-manifest.json and __precacheManifest are outed with "\" in path on Windows which causes error when copied in UNIX production

To Reproduce

Build on Windows -> deploy on UNIX

Expected behavior

{"/_app":"static\\_DvcWWKlkG5i2aGcOyE\\pages\\_app.js",

should be

{"/_app":"static/_DvcWWKlkG5i2aGcOyE/pages/_app.js",

System information

OS: Windows

Version of Next.js: 7.0.2

Fix

To fix the issue on pages-manifest.json ; I guess __precacheManifest is from next-offline and I'll investigate there

\next\dist\build\webpack\plugins\pages-manifest-plugin.js

L59:

pages["/".concat(pagePath.replace(/\/g, '/'))] = name.replace(/\/g, '/');

Issue 2:
Because code is run on browser and server, we cannot take full advantage of webpack tree shaking. The code is transformed to commonjs before anything.

How is it possible to take full advantage of tree shaking? (I've tried webpack-common-shake without success)

ESM is landing in node 8.5 with --experimental-module and also available with @std/esm package. Do you have any plan about this?

I have searched the issues of this repository and believe that this is not x duplicate.
Issue 1:
is there any way we can use material-ui components in react-native iOS app ?

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

Expected Behavior

Elements with postition: fixed;, right: 123px and .mui-fixed class applied doesn't move on Modal open

Current Behavior

it moves, because additional padding doesn't affect element with right position

Steps to Reproduce (for bugs)

Reproducer:

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.21

React
16.0.0

browser
Firefox-57, Chrome-62

etc
Issue 1:
localhost:~# uname -a
Linux localhost 5.4.51-0-lts #1-Alpine SMP Fri, 10 Jul 2020 10:54:20 UTC x86_64 Linux
localhost:~# wget https://github.com/denoland/deno/releases/download/v1.2.0/deno-x86_64-unknown-linux-gnu.zip
localhost:~# unzip deno-x86_64-unknown-linux-gnu.zip
Archive: deno-x86_64-unknown-linux-gnu.zip
inflating: deno
localhost:~# ldd deno
/lib64/ld-linux-x86-64.so.2 (0x7fdb1cc33000)
libdl.so.2 => /lib64/ld-linux-x86-64.so.2 (0x7fdb1cc33000)
librt.so.1 => /lib64/ld-linux-x86-64.so.2 (0x7fdb1cc33000)
libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7fdb1cc33000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fdb1a2d2000)
libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7fdb1cc33000)
Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by deno)
libm.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7fdb1cc33000)
Error relocating deno: __res_init: symbol not found
Error relocating deno: strtoull_l: symbol not found
Error relocating deno: __memcpy_chk: symbol not found
Error relocating deno: __isnan: symbol not found
Error relocating deno: __vfprintf_chk: symbol not found
Error relocating deno: strtoll_l: symbol not found
Error relocating deno: backtrace: symbol not found
Error relocating deno: __vsnprintf_chk: symbol not found
Error relocating deno: __isnanf: symbol not found
Error relocating deno: __isinf: symbol not found
Error relocating deno: backtrace_symbols: symbol not found
Error relocating deno: __register_atfork: symbol not found

Issue 2:
Previously I was able to use --target x86_64-unknown-linux-musl on rusty_v8 and deno (excluding the plugin). denoland/rusty_v8#49

It's unclear to me if it's best to only target x86_64-unknown-linux-musl or to additionally support it. e.g. sccache seems to only provide binaries for that target.

The one concern is that glibc is required for plugins (but I don't know if that means glibc cannot be used on a binary created with musl 🤷‍♂ ).

This is useful for platforms without glibc, examples alpine linux and amazon linux (which is occasionally a pain building, so would be helpful if a compatible binaries was in deno's CI).

xlink: #3243 #1658 #1495 #3356
Issue 1:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
yes

RFC?
no

Symfony version
3.3.6

symfony/web-profiler-bundle 3.3.6

symfony/security 3.3.6

Silex 2

the web profiler crash with

(1/1) Twig_Error_Syntax
Unknown argument "max_depth" for function "profiler_dump(value)".

seams symfony/web-profiler-bundle/Twig/WebProfilerExtension.php has a deprecated (?) function.

// line 31
public function getFunctions()
{
return array(
new \Twig_SimpleFunction('profiler_dump', array($this, 'dumpValue')),
);
}

public function dumpValue($value) // <-- just adding a parameter $maxDepth here fix the crash (but does nothing of course)
{
if (null === $this->valueExporter) {
$this->valueExporter = new ValueExporter();
}

return $this->valueExporter->exportValue($value);
}

I'm duplicating this issue silexphp/Silex-WebProfiler#124

Issue 2:
The form component DateType does not follow the documented behavior and naive selection process breaks any attempt to utilize the DateType element pattern field.

According to the official documentation the DateType will first check for the pattern configuration. If none is set, it will attempt to convert the format option. Finally if neither are set it will use a default pattern.

If you notice the relevant code (DateType.php line 147) you will see the pattern selection completely ignores the pattern option (instead pulls in the format), the regex on line 156 in using the 3 matching groups accidentally requires that 3 fields be present (even though those 3 fields could be the same portion, e.g. 3 year dropdowns).

Essentially as of right now the behavior is: pattern is ignored, and format requires at least 3 elements. I will work on a patch for now to conform to documented behavior.
Issue 1:
System info

Playwright Version: v1.32.3

Operating System: windows11

Browser: Chromium

This happen when I use the codegen to generate script. Like the upon image, for example, I found I has a typo on the word "too", but I can't put the cursor in the middle of the sentence, the cursor can only start from the end of the line. Is there any solution on this situation?

Issue 2:
System info

Playwright Version: [v1.32.3]

Operating System: [Windows 11]

Browser: [Chromium]

Other info: Node v16.15.0

It's possible I need to file this bug to MS Teams instead of playwright. Please let me know if I should do so.

I believe this is best reproduced with npx playwright codegen as the only action is to login to teams.

Call is answered properly if it is a direct call to the agent's email address. The bug occurs specifically for MS call queue in combination with playwright.

Source code

I provided exact source code that allows reproducing the issue locally. You can also reproduce this with npx playwright codegen.

Config file

// playwright.config.ts
import { defineConfig, devices } from '@playwright/test';

const config: PlaywrightTestConfig = {
timeout: 40000,
expect: {
timeout: 5000,
},
projects: [
{
name: 'chromium',
use: {
...devices['Desktop Chrome'],
},
},
],
};
export default config;

Test file (self-contained)

it('launch MS teams', async ({ page }) => {
const browser = await chromium.launch({
headless: false,
args: ['--use-fake-ui-for-media-stream', '--use-fake-device-for-media-stream'], //needed for mic/camera
});
const context = await browser.newContext();
const page = await context.newPage();

await page.goto('https://teams.microsoft.com/go#');
await page.getByPlaceholder('Email, phone, or Skype').fill(YOUR_USERNAME);
await page.getByRole('button', { name: 'Next' }).click();
await page.getByPlaceholder('Password').click();
await page.getByPlaceholder('Password').fill(YOUR_PASSWORD);
await page.getByRole('button', { name: 'Sign in' }).click();
await page.getByRole('button', { name: 'No' }).click();

});

Steps

[Run the test to open an MS Teams instance]

[Configure your MS Teams address to receive a call from an MS call queue ]

[Call the call queue number. This should result in an incoming call on your chromium teams window]

[Manually click the answer button on MS Teams]

Expected

[The call establishes and there is an active teams conversation conversation in the Chromium MS Teams tab.]

Actual

[Observe that the call establishes for a brief moment and is immediately being terminated]
Issue 1:
Here is the wiki article for them Duplication and Elimination Matrices. It would be nice to have direct functions for them.

Given a square matrix A of size n x n, duplication matrix D and elimination matrix E will satisfy:

D vech(A) = vec(A) and E vec(A) = vech(A).

The original paper which introduces duplication matrix

Issue 2:
I'm having difficulties displaying the NumPy reference in HTML format. There seems to be some formatting shining through which isn't correctly translated to HTML, or the rendering engine can't display the content properly.

The problem shows, for example, when looking at the ndarray reference, subsection "Internal memory layout of an ndarray". Here I get garbled formulae like this:

n_{\mathrm{offset}} = \sum_{k=0}^{N-1} s_k n_k

The problem occurs both with firefox and chromium on kubuntu 18.04, the docu is version 1.15.
Issue 1:
Vendoring a project which makes use of the automatic runtime JSX transpilation leads to an error when running the project. This is because vendoring isn't aware of the JSX compiler options and skips vendoring that dependency. It should account for the value in compilerOptions.jsxImportSource. The value set there is expanded to either <value>/jsx-runtime or <value>/jsx-dev-runtime depending on whether jsx is set to jsx-react or jsx-reactdev.

Error:

error: Relative import path "preact/jsx-runtime" not prefixed with / or ./ or ../ and not in import map from "file:///projject/main.tsx"
at file:///project/main.tsx:1:1

Steps to reproduce

Clone https://github.com/marvinhagemeister/deno-vendor-jsx-runtime

Run deno run main.tsx which will print <h1>it works</h1>

Run deno venodr main.tsx

Run deno run --no-remote --import-map=vendor/import_map.json main.tsx -> Error

Issue 2:
deno vendor does not honor jsxImportSource. It should automatically vendor code defined by jsxImportSource

minimal repro at https://github.com/sylc/repro_issue_deno_vendor_jsxImportSource

Note:

The current work around to get it vendored correctly is to explicitly call, in the program code, the jsx source, for example adding

import { h } from "preact/jsx-runtime";

$ deno --version
deno 1.26.0 (release, x86_64-pc-windows-msvc)
v8 10.7.193.3
typescript 4.8.3
Issue 1:
Q
A

Bug report?
no

Feature request?
yes

BC Break report?
-

RFC?
-

Symfony version
-

Hello,

I'm constantly wondering myself which Interface are picked up by the container to add service tag automatically when you use autoconfigure: true config.

The documentations mentions the Twig_ExtensionInterface Interface, but It would be awesome to have a command that tells us all the interfaces and classes that will apply a tag to my autoconfigured service.

ex: bin/console debug:autotags <--- not a good name, but 😅

PS: Is this already possible to know that (even without a command) ? If so I'd like to know how.

Issue 2:
Q
A

Bug report?
no

Feature request?
yes

BC Break report?
no

RFC?
yes

Symfony version
4.1

Inspired by symfony/symfony-docs#9229.

I've been wondering why there's no list available showing the tags that are applied on certain classes through autoconfiguration. I know it's just a small detail but I wanted to raise the issue nonetheless, autoconfiguration might be optional but so is autowiring.

I've checked out https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/Command/ContainerDebugCommand.php, and I can see why it hasn't been added before. The command compiles the container from cache, but the container dump doesn't contain the information anymore about which classes have been wired through autoconfiguration.

It would be mainly used for debugging purposes and just to show the developer what types of services they can wire through autoconfiguration. It could be called something like

debug:container --interfaces

and explained as

Displays autoconfiguration interfaces for an application

What do you think?
Issue 1:
Issue Type:

Bug Report / Feature Idea

Ansible Version:

latest and v2.0.0-0.7.rc2

Ansible Configuration:

Nothing relevant

Environment:

OSX

Summary:

The warning about duplicate dict keys when parsing yaml is annoying for legitimate use cases and there should be a feature to disable it.

Steps To Reproduce:

I use YAML anchors/aliases extensively to make my giant var files much easier to read. The following gist demonstrates what I'm doing and what I'm seeing:

https://gist.github.com/mspiegle/ef4630cbdf8b18f93613

The Ansible code responsible for this is:

https://github.com/ansible/ansible/blob/v2.0.0-0.7.rc2/lib/ansible/parsing/yaml/constructor.py#L67

Expected Results:

I either expect Ansible to not bother me about this, or provide some way for me to disable this particular warning.

Actual Results:

I get lots of warnings about duplicate dict keys. The duplicate dict keys are completely normal and expected in my use case.

Issue 2:
ISSUE TYPE

Feature Idea

COMPONENT NAME

sysctl

ANSIBLE VERSION

2.4.1

SUMMARY

There should be an option in sysctl module to change/set the owner, group & mode of the file updated/created. Currently it uses default owner/umask