WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

windows 10 platform npm run build

Error: EISDIR: illegal operation on a directory, open 'E:\react\react-server-render.next'

Context

Your Environment

Tech
Version

next
2.4.7

node
v6.10.3

windows
10

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

Expected Behavior

Links can be used in tests that are run with Jest.

Current Behavior

at throwIfNoRouter (node_modules/next/dist/lib/router/index.js:107:11)
at Object.SingletonRouter.(anonymous function) [as prefetch] (node_modules/next/dist/lib/router/index.js:69:5)
at Link.prefetch (node_modules/next/dist/lib/link.js:143:24)
at Link.componentDidMount (node_modules/next/dist/lib/link.js:148:12)
at commitLifeCycles (node_modules/react-dom/cjs/react-dom.development.js:8770:24)
at commitAllLifeCycles (node_modules/react-dom/cjs/react-dom.development.js:9946:9)

Steps to Reproduce (for bugs)

"next": "^5.0.1-canary.15",

Create a component with a render method like that returns: (partial):

import Link from 'next/link';
...
render() {
...
return (
<h3>{messages.LABEL}</h3>
<ul>
<li>
<Link prefetch href={messages.LINK1_URL || ''}>
<a>{messages.LINK1_LABEL || ''}</a>
</Link>
</li>
<li>

3.

import React from 'react';
import Enzyme from 'enzyme';
import Adapter from 'enzyme-adapter-react-16';
import enzymify from 'expect-enzyme';
import IndexPage from '../../pages/index';

const {shallow, mount} = Enzyme;
Enzyme.configure({adapter: new Adapter()});

describe('Index', () => {
it('Renders', () => {
const messages = {
LABEL: 'Maguffin'
};

const indexPage = mount(
<IndexPage
country="us"
language="en"
path="/"
messageBases={messages}
/>
);

jest -t Index

Context

I'm trying to write a Jest test for a page that has a next/link on it.

Your Environment

Tech
Version

next
^5.0.1-canary.15

node
9

OS
OSX 10.12

browser
n/a

etc
Issue 1:
A number of times I have wanted to use one function in one configuration in another in all other configurations. There's just no way to express this currently. A simple way to implement it would be with a #[notcfg(...)] attribute, which would just do the opposite of #[cfg(...)].

Issue 2:
fn main() { assert(false); }

causes 16 Valgrind errors on my machine: https://gist.github.com/975527

Doing assert(true) instead causes none
Issue 1:
Right now Tabs accept initialSelectedIndex only, and it is stored in the component state.

It's impossible to change selected tab programmatically — on the parent component prop change or on any event other then explicit user click.

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

Expected Behavior

If I make a card which only have one element of CardContent and nothing else (no controls, no media) then the alignment of the card should be correct.

Current Behavior

When there is a Card with only one CardContent and nothing else, there is extra padding bottom applied.

Steps to Reproduce (for bugs)

Create a Card with only one CardContent

Or look at the forked example here --> https://codesandbox.io/s/1ow4q5557l

Notice that there is extra padding bottom, it is applied in 'last-child' selector. source file here : https://github.com/mui-org/material-ui/blob/v1-beta/src/Card/CardContent.js (line 9)

Now, this selector doesn't take effect if there is CardActions present. In fact, this selector will apply only when there are multiple instances of CardContent (in my opinion which should be never, since one Card should have only one Card Content).

I may be totally wrong here and please correct me if I am understanding this wrongly.

Context

Alignment for my Cards are off (when there are no actions).

Your Environment

Tech
Version

Material-UI
1.0.0-beta.27

React

browser

etc

note - I can submit a PR if you a confirm it as a bug.
Issue 1:
Two first points of the translation process are duplicating two first points of summarization process:

https://huggingface.co/transformers/task_summary.html#translation

Instantiate a tokenizer and a model from the checkpoint name. Summarization is usually done using an encoder-decoder model, such as Bart or T5.

Define the article that should be summarized.

Issue 2:
🚀

Use Pytorch's own attention and transformer modules.

Motivation

Pytorch now offers modules like nn.MultiheadAttention and nn.Transformer. It would be nice to use the official Pytorch implementations in transformers now that they are available.

Additional context

There is an offical Pytorch tutorial that shows how nn.Transformer can be used and customized.

These modules are only available in Pytorch 1.1 (nn.MultiHeadAttention) and 1.2 (nn.Transformer). Using them would mean that anyone with Pytorch 1.0 would have to update their own version.
Issue 1:
Just a suggestion: do not ignore the src and examples folders when installing three.js from npm and/or bower.

This would not break compatibility with existing projects that use npm or bower to install three.js, but provide a valid use case: it would allow to integrate a custom build process for three.js into our existing build pipelines for our apps.

The current way for custom builds as outlined in https://github.com/mrdoob/three.js/wiki/build.py,-or-how-to-generate-a-compressed-Three.js-file is focused on a manual process: clone the repo, run the build, and add the finished custom JS file to your app's git repo. However that cannot be automated conveniently within the context of existing build processes for our own apps. Upon updates of three.js you have to repeat these steps every time.

On the other hand if the src and examples files would not be excluded, one could use the package managing power of npm or bower to include your three.js dependency in your project (with the ability to target specific versions, version ranges, the dev branch...), and have your build workflow of choice (gulp, grunt, whatever) automate the custom build process, as it would be able to pick the individual src files from the installed package (node_modules/bower_components) now. This would allow for effortless updates, integration in CI server workflows etc.

I can file a PR (easy enough ;)), just wanted to know if there might be objections?

Issue 2:
The main source code has recently been ported to ES2015 modules (see #9310); however, some parts are still relying on global namespace pollution and have thus become unusable.

Specifically the things in /examples/js/ haven't been transformed to support modules yet; this makes them currently unusable from within environments such as webpack or SystemJS.

Edit, 11-20-2016: They can be used, but it requires a lot of setup: SystemJS, webpack. If you need assistance with these: Sorry, but this is the wrong thread to announce it! 😄
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.7.3-SNAPSHOT

Operating System version: mac os 10.13.6

Java version: 1.8.0_171

Steps to reproduce this issue

run the code in unit test:

@Test
public void testRestProtocol() {
protocol = ExtensionLoader.getExtensionLoader(Protocol.class).getExtension("rest");
URL url = URL.valueOf("rest://127.0.0.1:5342/rest/say?version=1.0.0&interface=org.apache.dubbo.rpc.protocol.rest.DemoService");
while (true) {
Invoker<DemoService> invoker = protocol.refer(DemoService.class, url);
invoker.destroy();
}
}

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

Actual Result

What actually happens?

the size of LinkedList [clients] will keep growing, the ResteasyClient hold by it will not release, which will cause OOM easily.

ResteasyClient client = new ResteasyClientBuilder().httpEngine(engine).build();
clients.add(client);

the clients in the linkedList will not release when invoker destroyed, they will only be released when the rest protocol destroyed.

I think the protocol layer should not hold the object's such like client, it should be hold by the invoker and has the same lifecycle with invoker

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

Operating System version: windows10

Java version: JDK1.8

Steps to reproduce this issue

set onconnect,ondisconnect parameter on @reference

write onconnect,ondisconnect callback on consumer

code:

@Reference(onconnect = "onconnect")
private HelloDubboService helloDubboService;

public void onconnect(){
System.out.println(">>>>>>>>>>>>>>>>>onconnect()");
}

Expected Result

it should invoke onconnect ,ondisconnect callback when the consumer connect the provider

Actual Result

it does not work

is it a bug?or these callback only be used on provider side?
Issue 1:
I suggest we add "es6" as an option to the "module" flag, and the result of using it is getting ES6-style modules (import, export, and default keywords). It should be an error to choose "es6" as the module emit type when targeting below ES6. When targeting ES6 or above, this can remain the default module emit type.

A primary personal driver for this is bundling, as bundling to an ES6 module when targeting ES6 is awkward (but possible) but bundling to other formats while still using the remaining ES6 feature set is very desirable, and, additionally, plays well into starting to break things out for #4692. A real world use would be compiling targeting node 4 - it supports most of our ES6 features, but not ES6 modules, making our ES6 emit impossible to use without an additional transpiler. :(

Additionally, it would bring us inline with the systemjs builder's output options, which are amd, cjs, and es6.

Issue 2:
As of August, 2015, there are several platforms that have JS implementations falling somewhere between ES5 and ES6. Chrome 45+ has block scoping, fat-arrow functions, Map/WeakMap/Set/WeakSet, and classes. io.js 3.x has all of these features as well except fat-arrow functions, but they're coming in Node.js 4.0 or so next month.

The big common case here is that none of these platforms support ES6 modules yet -- I imagine none of them will for some time.

Can we get a compiler mode to emit ES6 features selectively, or at least emit ES6 except for modules? @mhegazy mentioned in the TypeScript gitter that this would be effectively supporting --t es6 alongside --m commonjs in terms of compiler flags.
Issue 1:
Bug report

As per discussion on #15143

I'm building a react component library, so I declare react and react-dom as externals. I'm using webpack to build our library as a module, with experiments.outputModule = true, output.environment.module = true, and output.library.type = 'module'.

What is the current behavior?

When I import my component into a create-react-app project, I get this crash:

Uncaught TypeError: __webpack_require__.r is not a function
at Object../node_modules/webpack-external-repro-case/es/index.js (warning.js:62)
at __webpack_require__ (bootstrap:856)
at fn (bootstrap:150)
at Module.<anonymous> (index.module.css?438e:82)

When I switch optimization.minimize to true, my component can be imported successfully.

On the previous issue, there was some discussion of external type (module vs commonjs-module). I've confirmed this occurs with both externalTypes.

If the current behavior is a bug, please provide the steps to reproduce.

Reproduction repo (using the minification-bug branch): https://github.com/MustafaHaddara/webpack-external-repro-case/tree/minification-bug

(I used yalc to link but npm | yarn link probably works too)

Turn minification on and the component is imported successfully.

What is the expected behavior?

non-minified code should behave the same as minified code.

Other relevant information:

webpack version: 5.65.0 to build the component library, client is using webpack@4.44.2 via react-scripts@4.0.3

Node.js version: 14

Operating System:

Additional tools:

Issue 2:
Bug report

What is the current behavior?

Building a project in production mode using webpack5 results in a mod is not defined error at runtime.

If you build with development mode, no errors will occur at runtime. In webpack4 this error does not occur when building in production mode.

Also, when building with webpack4, there are no deprecation warnings.

So I think this is a bug in webpack5.

If the current behavior is a bug, please provide the steps to reproduce.

I haven't created a minimal reproducible repository yet, but here is the actual my project config.

https://github.com/syuilo/misskey/blob/develop/webpack.config.ts

What is the expected behavior?

No runtime error

Other relevant information:

webpack version: 5.0.0-beta.13

Node.js version: 13.7.0

Operating System: Windows10

Additional tools:
Issue 1:
When using a table-bordered inside a panel and with <thead> and <tbody> child elements, the border between the header and the first <tbody> element is not displayed.

This happens for me on Chrome 32.0.1700.107 and Safari 7.0.1 (9537.73.11). Firefox 27.0 does not suffer from the problem. (All on OS X 10.9.1)

Fiddle:

http://jsfiddle.net/andmor/7yPTL/1/

Seems related with #12353

Issue 2:
Hi,

The old documentation that included a page with variables that showed the different colors so you could pick one, has all gone.

This was done I believe because you did not want to duplicate the docs at LESS? Well LESS doesn't have them either so it is nigh on impossible to get this information in a readable form unfortunately :(

Is there any chance we can have it back? It was extremely useful resource and if I knew it was all being pulled down I would have saved the web site. Whoever did it did a great job.

Thanks for your hard work - hopefully you have a backup ;)
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.5

Operating System version: Windows10

Java version: 1.8.0

Steps to reproduce this issue

设置一个接口的响应时间为999999999ms；

进行泛化调用；

通过MethodConfig类设置方法的相关参数（方法名称、超时时间、重试次数）；

通过MethodConfig类中setRetries方法设置方法的重试次数为0；

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

Expected Result

What do you expected from the above steps？

只会调用一次，在第一次调用失败后不会重试。

Actual Result

What actually happens?

在第一次调用失败后进行重试，总共会调用3次。

What is the cause?

在FailoverClusterInvoker的doInvoke方法中获取获取重试次数时：

int len = this.getUrl().getMethodParameter(invocation.getMethodName(), "retries", 2) + 1;

由于invocation.getMethodName()为$invoke，在URL中重试次数为methodName.retries，而从URL中获取$invoke.retries，获取结果为空，然后采用默认值2，从而导致上述情况。

注：这里应该通过RpcUtil工具类中的getMethodName方法获取方法名称。

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

Operating System version: linux

Java version: 1.8

Steps to reproduce this issue

1.修改zookeeper源码，在 SessionTrackerImpl 的 设置session过期状态 与 清理session临时节点 代码中增加30s延迟，以模拟网络波动导致标记session过期与清理临时节点不同步的情况。以源码的方式启动zookeeper。

2.修改CuratorZookeeperClient，设置session过期时间为 5s ，并在createEphemeral中增加日志打印，当抛出NodeExistsException时，输出EphemeralOwner与当前的sessionId

3.启动provider，并确保provider的临时节点已注册到zookeeper中。

4.断开provider与zookeeper的网络连接，等待5s session过期后，恢复网络连接。

Expected Result

EphemeralOwner 与 sessionId 未被输出，或输出的 EphemeralOwner 与 sessionId 相同。等待一段时间后，provider的注册信息在zookeeper中仍然存在。

Actual Result

可以观察到日志打印的 EphemeralOwner 与 sessionId 不同，等待一段时间后，provider的注册信息被删除，且不再恢复。此时consumer调用时无法找到此provider。
Issue 1:
Description of the problem

https://github.com/mrdoob/three.js/blob/dev/examples/models/vrml/house.wrl

has 7 errors and

https://github.com/mrdoob/three.js/blob/a92f447d8a9190c8d118bae9baac63d122a96ea1/examples/models/vrml/house.wrl

has 45 errors when validated by Chisel ( http://www2.hrp.no/vr/tools/chisel/install.htm ).

The first error rof the dev version is at line 1902: "not a valid field for Transform"

https://github.com/mrdoob/three.js/blob/dev/examples/models/vrml/house.wrl#L1902

It looks like the children field is missing for the enclosing transform.

I noticed because cobweb ( http://titania.create3000.de/cobweb/ ) - a capable VRML browser - reported the same problem with the dev file.

Three.js version

Dev

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

Linux

Android

IOS

Hardware Requirements (graphics card, VR Device, ...)

none

related

#10290

Issue 2:
I have two GLB models that both reference the same external image (jpg) as a texture used in their materials - currently this results in two Textures created and uploaded to the GPU, is there a way to reuse the (identical) Texture's between models, like checking in the TextureLoader if that Texture has already been loaded and created? There's a similar question here for Babylon - but it gives a bit of more context: https://www.html5gamedevs.com/topic/37130-loading-gltf-files-that-share-same-textures/

Three.js version

r116

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS
Issue 1:
DynamicChangeDetection class and JitChangeDetection class were previously private, with only the functions for each made public. The doc comments are on the functions, so nothing shows up in the API docs.

Previously we were having issues with duplication in the list of exported public docs, it seems like this is still not quite fixed?

Issue 2:
Current behavior

Example

history of browser stack is [#/index/index -> #/product/product -> #/product/choice -> #/product/pay -> #/product/success ]

/// Follow CanDeactivate implement is for path #/product/success of SuccessComponent

canDeactivate(component: SuccessComponent, currentRoute: ActivatedRouteSnapshot, currentState: RouterStateSnapshot, nextState?: RouterStateSnapshot) {
console.log(currentState.url);
console.log(nextState.url)
return false;
}

First click back button on browser
console output “/product/success”
console output “/product/pay” // expect “/product/pay” so this is ok

Second click back button on browser
console output “/product/success”
console output “/product/choice” // expect “/product/pay” so this is error

Third click back button on browser
console output “/product/success”
console output “/product/product” // expect “/product/pay” so this is error

Fourth click back button on browser
console output “/product/success”
console output “/index/index” // expect “/product/pay” so this is error

Last click back button on browser

this time browser leave angular app even “return false” of canDeactivate be execute;

I feel when I click back button of browser, history stack of browser pop a history item even “return false” of method canDeactivate

Expected behavior

Recovery history of browser when "return false" of method canDeactivate, just like no click back button of browser.

Minimal reproduction of the problem with instructions

When config a CanDeactivate for a router, even "return false" of canDeactivate be execute, multi click back button of browser, we will reproduction this problem

Please tell us about your environment:

angular-cli tool

Angular version: 4.0.2

Browser: [all browser ]

Language: [ TypeScript 2.x ]

Node (for AoT issues): node --version = node: 7.0
Issue 1:
In documentation there is

<div class="row">
<div class="col-lg-4">...</div>
<div class="col-lg-4 col-lg-offset-4">...</div>
</div>

But col-lg-offset-4 class does not exist, I had to use col-offset-4 instead

Using 3.0.0 version

Issue 2:
So as per the documentation, I tried using two different offsets for desktop and phone. But I could not find the col-lg-offset on the CDN hosted css file.

http://netdna.bootstrapcdn.com/bootstrap/3.0.0-rc1/css/bootstrap.min.css

Am not sure if this is an issue or am I going wrong somewhere?
Issue 1:
The following program triggers this:

use std::thread::Thread;

fn main() {
Thread::spawn(move || { println!("Hello"); }).join();
println!("After join");
}

When compiled on DragonFly with most recent rust (and all versions since the removal of rustrt), it fails with:

hello
thread '<main>' panicked at 'assertion failed: `(left == right) && (right == left)` (left: `22`, right: `0`)',
/home/..../rust/src/libstd/sys/unix/mutex.rs:53

The code that fails is:

let r = ffi::pthread_mutex_destory(self.inner.get());
debug_assert_eq!(r, 0);

It returns with error code 22 (EINVAL) instead of 0. To me it seems that Mutex::destroy() is called twice! It might be related to the new TLS thread_local code and destructor support, but it's pretty hard to understand, so any ideas how to track the bug further down and fix it is welcomed.

Issue 2:
See http://doc.rust-lang.org/std/primitive.char.html#method.into_searcher as an example, CharEqPattern goes nowhere
Issue 1:
Migrated issue, originally created by Михаил Доронин (@warrior2031)

I would like to provide cross-platform Merge statement. I've seen this issue

I think there should be both dialect specific variants as well as the lowest common denominator between them. The reasons are

It's in sql 2003 standard and many databases support actual standard (okay, maybe they not so popular for sqlalchemy users)

It is now possible to implement lowest common denominator implementation in mysql, sqlite (maybe not that performant, but who uses sqlite for performance? And user can be warned about that in docs) and postgresql.

I believe that lowest common denominator is the actual most useful (and used) use case. Which is "insert values or update existing ones". Kind of like {**d1, **d2} in python3.

/* postgresql */
INSERT INTO table (a, b)
VALUES (1, 2), (2, 3)
ON CONFLICT (a) DO UPDATE SET dname = EXCLUDED.dname;

/* mysql */
INSERT INTO table (a, b)
VALUES (1, 2), (2, 3)
ON DUPLICATE KEY a=VALUES(a) UPDATE

/* sqlite */
INSERT OR REPLACE INTO table (a, b)
VALUES
(1, COALESCE((SELECT role FROM Employee WHERE id = 1), 2)),
(2, COALESCE((SELECT role FROM Employee WHERE id = 2), 3))

/* merge from wikipedia */
MERGE INTO table USING table_reference ON (condition)
WHEN MATCHED THEN
UPDATE SET column1 = value1 [, column2 = value2 ...]
WHEN NOT MATCHED THEN
INSERT (column1 [, column2 ...]) VALUES (value1 [, value2 ...]);

possible sqlalchemy interface insert(table, [(1, 2), (2, 3)]).merge(table.c.a)

I would be very happy to provide implementation if you can provide guidance on how to do that. I'm trying to understand your code, but aside from understanding that there is Insert class in sql/dlm.py and there are probably implementations of it in all dialects I haven't been able to figure out much.

Maybe you can show how to make that for postgres since it already has on_conflict in dialect. And then I can use that as example to add this to sqlite, sqlalchemy and maybe other dialects.

Issue 2:
Migrated issue, originally created by jek (@jek)

Implement generic MERGE, aka 'upsert'. In ANSI, it looks like:

MERGE INTO table_name1 USING table_name2 ON (condition)
WHEN MATCHED THEN UPDATE SET column1 = value1 [column2 = value2 ...](,)
WHEN NOT MATCHED THEN INSERT columns VALUES (values)

Dialect support differs pretty widely. A quick & likely inaccurate poll:

Oracle 9+ has a MERGE

t-sql 2008 has a MERGE, earlier can maybe do IF EXISTS(SELECT ...)

MySQL is limited to a key violation condition, and can do either INSERT ... ON DUPLICATE KEY UPDATE or REPLACE INTO, INSERT being preferable

SQLite is limited to a key violation condition, and has INSERT .. ON CONFLICT REPLACE