WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
This suggestion has a few pieces:

Implement boolean literal types for true and false, in a fashion similar to #1003

Implement type guards for booleans. Essentially, control flow constructs like if-else, while, for, etc would be subject to a type guard if their guard expression is a boolean.

Now we can update generators to have a next method that returns { done: false; value: TYield; } | { done: true; value: TReturn; }, where TYield is inferred from the yield expressions of a generator, and TReturn is inferred from the return expressions of a generator.

Iterators would return { done: false; value: TYield; } | { done: true; value: any; } to be compatible with generators.

for-of, spread, array destructuring, and the type yielded by yield* would only pick the value associated with done being false.

The value of a yield* expression would pick the value associated with done being true.

Introduce a Generator type that can be used to track the desired type of a yield expression. This would be TNext, and would be the type of the parameter for the next method on a generator.

The generator type would look something like this:

interface Generator<TYield, TReturn, TNext> extends IterableIterator<TYield> {
next(value?: TNext): IteratorYieldResult<TYield> | IteratorReturnResult<TReturn>;
throw(exception: any): IteratorYieldResult<TYield> | IteratorReturnResult<TReturn>;
return(value: any): IteratorYieldResult<TYield> | IteratorReturnResult<TReturn>;
[Symbol.iterator](): Generator<TYield, TReturn, TNext>;
[Symbol.toStringTag]: string;
}

Issue 2:
If one try to set a property that hasn't any getter defined, the compiler doesn't emit any error or warning and the code silently fails à runtime.

example:

class Greeter {
private _greeting: string;
get greeting(): string { return this._greeting; }

constructor(message: string) {
this.greeting = message; //no error at compile time and silent failure at execution time
}
greet() {
return "Hello, " + this.greeting;
}
}
Issue 1:
Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.5.2762.0

Steps to reproduce

Resize the window to smaller, then back to about its original size or even bigger.

Close the window.

Expected behavior

The window should simply disappear.

Actual behavior

For a fraction of a second, tons of horizontal and vertical lines, which look like the border of the window at its previous sizes, are painted inside the window area.

This suspiciously looks like some leftover widgets that don't get properly cleaned up during a resize, potentially consuming various resources (and maybe causing who knows what other problems).

(Could be related to #3207?)

Issue 2:
Issue 1:
VSCode Version: 0.10.11

OS Version: Windows 7

Steps to Reproduce:

Set the "Language Mode" to "Javascript"

Write "variable", you'll see that the prefix "var" is highlighted

This doesn't happen when the word starting with "var" is part of a function argument, or inside strings

*Tried with multiple themes, issues seems to be theme-agnostic (happens on all of them)

Issue 2:
From @f111fei on February 23, 2016 6:14

version： 0.10.10

letter

Copied from original issue: microsoft/vscode#3270
Issue 1:
Hi all,

First off, thanks for all your hard work on this project. It kicks ass.

This is my first time using bootstrap more extensively on a larger project, and I'm confused as to why the screen-xs breakpoint has been deprecated, and the xs breakpoint has been defined as everything less than 768px.

I was taking a look at #12913, and I don't know the history here, but at first glance it looks like the underlying problem was that there wasn't a way to specify default "mobile-first" behavior, since the xs breakpoint was between 480px and 767px. There was nothing for < 480px, so the xs breakpoint was changed to be just < 768px.

But I have run into several cases where I'd love to use the xs breakpoint. Basically, I'd like to say .make-xs-column(6), and have it wrap the columns when < 480 but go side by side at 480 and up.

Again, I don't know the history here, but it seems to me a better solution would be to add another set of mixins and helper classes to specify the default "mobile-first" behavior. Something like:

.my-row {
.make-row;
}

.my-row-item {
.make-column(6); // Default is 6 cols
.make-xs-column(3); // 3 cols at >= 480px
.make-md-column(2); // 2 cols at >= 768px
}

Would it be crazy to make the xs breakpoint act like the sm, md, and lg breakpoints (i.e. xs >= 480px) and add another set of helpers (e.g. .col-6, .visible-block, .make-column(8)) to handle the >= 0px default behavior?

Thanks

Issue 2:
The smallest grid column supported at the moment is .col-xs- (<768px), which seems like a big range.

Would it be advisable to have:

.col-xs- (>480px and <768px)

.col-tn- (<480px)

Reason being it still seems reasonable to have a 2 column grid on 768px (240px - 384px per column), while 480px have a stacked column.

Using the current .col-xs- (<768px) option, putting one stacked column on 768px seems too wide on some cases, and 2 columns on 480px seems ridiculous at times.
Issue 1:
Would it be possible to have line wrappings auto indent to match their starting line's indentation? The way that soft wrapping currently works in Atom is confusing and cluttered...

So, instead of this:

Could you provide an option for this:

I am trying to convince a co-worker to switch to Atom, and this is the only thing holding him back :)

Thank you! Atom Editor is the best.

Issue 2:
Ok, this one may be a personal preference, but it drives me nuts that softwrap doesn't match the indent.
Issue 1:
While installing celey==4.0.2 its giving error KeyError: 'async'. Upgraded dependencies should install only when the version is upgraded not in this case

Issue 2:
If we removed support for Redis, we'd be able to focus the time on RabbitMQ, or maybe Kafka/nsq.

There's also the huge task of porting to asyncio in Python 3.

I think this should be seriously considered. If we are to work on this for fun, then the popularity of the transport shouldn't matter.

In the end I will chose what I have the ability to work on anyway, but at least you can voice your concerns here.
Issue 1:
See this in (slow mo!) action: https://youtu.be/ljXgi7r62Pc

When a recipe in Pesto is animating up, notice how the shadow around the FAB flashes/clips.

(noticed in a material eng review)

Issue 2:
Hello everybody. Tell me please whether it is possible to create flutter app maker? Like storyboard in Xcode? drug and drop element in window and generate code. in web similar http://mutisya.com how it works?
Issue 1:
VSCode Version: Alpha - e77003f

OS Version: El Capitan

Steps to Reproduce:

Open any file in vscode

Make changes to that file outside of vscode, vscode is not picking up changes

File events seem to be completely broken for me, as git is also not picking up file event changes

Issue 2:
Today when you open VS Code on wrong casing workspace path, all file events stop to work. We should detect this case and either fix it or print a warning.
Issue 1:
As far as I can tell the runtime transform is all-or-nothing, all I'm interested in is getting rid of the redundant helpers inlined into every module, but it seems I can't have that without also the "risk" of getting dependencies on the other runtimes (notably core-js).

Have I missed something or would it not make sense to have a separate transform for just this? They seem to have rather separate concerns from my perspective (avoid redundant helper code vs add dependencies for optional features).

Issue 2:
This would be really nice for larger applications that aren't libraries, where they could still use the full, globally polluting polyfill, but the helpers wouldn't be duplicated across several modules. It would make the compiled code faster to load, and a lot smaller overall. These benefits are nice for both Node applications and web applications, where the deduplication would make programs significantly smaller. As for the core-js aliasing, it could just require the module at the top of every file that needs a feature from it, which doesn't add a lot of size overhead to the files.
Issue 1:
Hello

I am having trouble in checking existing data in scrapy. i have used elasticsearch as my database below code i am trying to execute ??

`

def checkIfURLExistsInCrawler(single_url):
elastic_query = json.dumps({
"query": {
"match_phrase": {
"url": single_url
}
}
})

result = es.search(index='test', doc_type='test', body=elastic_query)['hits']['hits']
return result

def start_requests(self):
urls = [

here i have some url there might be chance that some urls are duplicate so i have to put
validation but in for loop it doesn't working

]

for request_url in urls:
checkExists = self.checkIfURLExistsInCrawler(request_url)

if not checkExists :
beingCrawledUrl = {}
beingCrawledUrl['url'] = single_url
beingCrawledUrl['added_on'] = now.strftime("%Y-%m-%d %H:%M:%S")
json_data = json.dumps(beingCrawledUrl)
InsertData = es.index(index='test', doc_type='test', body=json.loads(json_data))
yield scrapy.Request();

`

if i execute this code all record inside urls = [ ] are inserted into "test" index even if its duplicated because of validation i put above is not working .

but if i run this again with same data validation works .so please can any one help this out.

Issue 2:
Would it make sense to add something to the top of scrapy.utils.request.request_fingerprint like:

if 'fingerprint' in request.meta:
return request.meta['fingerprint']

This is useful, for example, if you consider two pages to be identical if they share the same productID query parameter:

def parse(self, response):
...
request = Request(url)
m = re.search(r'productID=([^&]+)', url)
if m:
request.meta['fingerprint'] = m.group(1)

I'm currently handling this with a custom duplicate filter, but it seems like it would be broadly useful.
Issue 1:
model = AutoModelForSequenceClassification.from_pretrained("bert-base-uncased")

returns this warning message:

Some weights of the model checkpoint at bert-base-uncased were not used when initializing BertForSequenceClassification: ['cls.predictions.bias', 'cls.predictions.transform.dense.weight', 'cls.predictions.transform.dense.bias', 'cls.predictions.decoder.weight', 'cls.seq_relationship.weight', 'cls.seq_relationship.bias', 'cls.predictions.transform.LayerNorm.weight', 'cls.predictions.transform.LayerNorm.bias']
- This IS expected if you are initializing BertForSequenceClassification from the checkpoint of a model trained on another task or with another architecture (e.g. initializing a BertForSequenceClassification model from a BertForPretraining model).
- This IS NOT expected if you are initializing BertForSequenceClassification from the checkpoint of a model that you expect to be exactly identical (initializing a BertForSequenceClassification model from a BertForSequenceClassification model).
Some weights of BertForSequenceClassification were not initialized from the model checkpoint at bert-base-uncased and are newly initialized: ['classifier.weight', 'classifier.bias']
You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.

This just started popping up with v.3 so I'm not sure what is the recommended action to take here. Please advise if you can. Basically, any of my code using the AutoModelFor<X> is throwing up this warning now.

Thanks.

Issue 2:
Environment info

transformers version: 4.17.0

Platform: Linux-5.10.0-051000-generic-x86_64-with-glibc2.10

Python version: 3.8.5

PyTorch version (GPU?): 1.10.2+cu113 (True)

Tensorflow version (GPU?): not installed (NA)

Flax version (CPU?/GPU?/TPU?): not installed (NA)

Jax version: not installed

JaxLib version: not installed

Using GPU in script?: Yes (the same on CPU)

Using distributed or parallel set-up in script?: No

Who can help

@LysandreJik, @Narsil, @SaulLu

Information

Model I am using (Bert, XLNet ...): BERT (bert-large-cased)

The problem arises when using:

the official example scripts: (give details below)

my own modified scripts: (give details below)

The tasks I am working on is:

an official GLUE/SQUaD task: (give the name)

my own task or dataset: (give details below)

To reproduce

Steps to reproduce the behavior:

encoded = tokenizer("This thing costs £4.56")
decoded = tokenizer.decode(encoded["input_ids"], clean_up_tokenization_spaces=True)
print (decoded)

Real output: [CLS] This thing costs £4. 56 [SEP]

I tried it also with NER pipelines and other text inputs.

Additional example: got [CLS] ( including once - a - week tapping ) [SEP] instead of [CLS] (including once-a-week tapping) [SEP]

Expected behavior

Expected output: [CLS] This thing costs £4.56 [SEP].

I expected the tokenizer to cleanup all the spaces introduced. Is there any different way to do so? Am I missing some trivial parameter?
Issue 1:
Problem

When using contourf with alpha < 1, these ugly lines appear at the color boundaries. This is evident both in the contoured data as well as on the colorbar.

I can set antialiased=True in contourf to fix the problem with the data, but the lines on the colorbar remain.

As far as I can tell from the documentation, there doesn't seem to be a way to set antialiasing for the colorbar. Is there any way to get rid of these lines?

Issue 2:
This is the underlying problem raised in #1178.

It is illustrated by the test below; note that boundary anomalies are visible in all forms--agg on the screen, and pdf and svg displayed with a viewer--but in different places depending on the viewer and the size of the figure as rendered.

Note that the colorbar is rendered using pcolormesh, which has its own renderer with agg but otherwise is handled by draw_path_collection.

import numpy as np
import matplotlib.pyplot as plt

z = np.arange(150)
z.shape = (10,15)

fig, axs = plt.subplots(2,2)

ax = axs[0,0]
cs0 = ax.contourf(z, 20)
cbar0 = fig.colorbar(cs0, ax=ax)

ax = axs[0,1]
cs1 = ax.contourf(z, 20, alpha=0.3)
cbar1 = fig.colorbar(cs1, ax=ax)

ax = axs[1,0]
im2 = ax.imshow(z, interpolation='nearest')
cbar2 = fig.colorbar(im2, ax=ax)

ax = axs[1,1]
im3 = ax.imshow(z, interpolation='nearest', alpha=0.3)
cbar3 = fig.colorbar(im3, ax=ax)

plt.savefig("test1.pdf")
plt.savefig("test1.svg")
plt.show()
Issue 1:
Bug report

What is the current behavior?

I'm using code splitting (via SplitChunksPlugin) to extract common dependencies. I have multiple entry points. The output target is node.

When trying to run the successfully bundled code, I get the error TypeError: Cannot read property 'call' of undefined.

When I remove code splitting from my config, the output runs without error.

Some commonalities with previous comments:

I have multiple named entry points and one depends on the other, as in #959 (comment)

One of my files imports the relative path '../../fixtures/mock_users.json', similar to #959 (comment).

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

I've provided a minimal project setup that reproduces the problem: https://gitlab.com/jlapointe/codesplittingtest

What is the expected behavior?

The code generated using code splitting should behave identically to the code generated without using code splitting.

Other relevant information:

webpack version: 4.31.0

Node.js version: 10.15.3

Operating System: Ubuntu 18.04 LTS

Additional tools: NodeExternals

Issue 2:
If you add aliases into your DllPlugin, it will only write out the raw file path. This causes issues when you have to dual maint. aliases. Also when you are trying to abstract out logic, such as locale-specific bundles.

@sokra Is there a likelihood that this feature is possible and would be accepted if I put in a PR?

Example:

DllPlugin

vendor.js

require('underscore');

vendor.config.js

{
entry: {
locale: [path.resolve('./vendor.js')]
},
output: {
path: path.resolve('./build/'),
filename: '[name].bundle.js',
library: '[name]'
},
plugins: [
new webpack.DllPlugin({
name: '[name]',
path: 'build/vendor-manifest.json'
})
],
resolve: {
extensions: ['', '.js'],
alias: {
'underscore': path.join('bower_components', 'lodash', 'dist', 'lodash.js')
}
}
}

vendor-manifest.json

{
"name": "vendor",
"content": {
"./bower_components/lodash/lodash.js": 1,
"./vendor.js": 2
}
}
Issue 1:
Is it possible to duplicate tabs as on linux terminals?

On gnome term I can use ctrl+shift+t and it duplicates the current tab on the same directory while ctrl+t opens a new tab.

Issue 2:
Is this indicative of a larger problem? Should we file an outstanding work item to audit all sites of manipulating the active buffer and/or somehow change the design such that the methods cannot accidentally be called without resolving which one is the active one first?

For the latter, my proposal would be to hide all the verbage methods off the base class and implement some sort of interface that holds them that is only returned when/if someone has correctly queried for the active one first. I'd accept competing proposals, though.

Originally posted by @miniksa in #2729 (comment)
Issue 1:
According Docs

http://www.elasticsearch.org/guide/reference/api/search/facets/terms-facet/

and code

org.elasticsearch.search.facet.terms.TermsFacet

ordering works for "count" and "term" in two directions.

for "count", the tie breaker is a "normal" compareTo, which will compare the String Text of the term. However this will produce a reverse order on the term names. For "reverse_count", this is the opposite.

so I end up with z:1, a:1, rather than a:1,z:1 which, to my expectation, more people would be able to use to find the matching entries.

Additionally, the comparison is always case sensitive and cannot be changed.

So in the end, It looks like I always will need to resort the entries myself. But this creates wasted effort. Right now, it is not possible to get the facets without any sorting.

Elasticsearch will always sort the Facets, and then I will have to sort them again.

Issue 2:
Hi

My apologies if I am doing something dumb but I have been trying to get this working for a while now.

I have downloaded and unpacked elasticsearch 2.1 (ZIP from elastic.co) and get the error below. I have reinstalled Java 1.8 and cleaned up any old installations but still get the same error. Any suggestions? I have repeated the download and install of both ElasticSearch and Java a couple of times to be sure.

JAVA_HOME set to C:\Progra~1\Java\jdk1.8.0_25

Thanks in advance

CM

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\WorkSpace\elasticsearch-2.1.0\bin>java -version

java version "1.8.0_25"

Java(TM) SE Runtime Environment (build 1.8.0_25-b18)

Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

C:\WorkSpace\elasticsearch-2.1.0\bin>elasticsearch.bat

Exception in thread "main" java.lang.UnsupportedClassVersionError: org/elasticsearch/bootstrap/Elasticsearch : Unsupported major.minor version 51.0

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630)

at java.lang.ClassLoader.defineClass(ClassLoader.java:614)

at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)

at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)

at java.net.URLClassLoader.access$000(URLClassLoader.java:58)

at java.net.URLClassLoader$1.run(URLClassLoader.java:197)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

at java.lang.ClassLoader.loadClass(ClassLoader.java:305)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)

at java.lang.ClassLoader.loadClass(ClassLoader.java:246)

Could not find the main class: org.elasticsearch.bootstrap.Elasticsearch. Program will exit.
Issue 1:
The bug can be demonstrated on the following example:

from sqlalchemy import Table, MetaData, Integer
from sqlalchemy.dialects import mysql

metadata = MetaData()

table = Table('table', metadata,
Column('id', Integer, primary_key=True),
Column('int_or_null', Integer, nullable=True),
)

def dump_sql(query):
return str(query.compile(dialect=mysql.dialect()))

query = mysql.insert(table) \
.on_duplicate_key_update(int_or_null=None)

print(dump_sql(query))

which generates an invalid SQL that subsequently fails to execute:

INSERT INTO `table` (id, int_or_null)
VALUES (%s, %s)
ON DUPLICATE KEY UPDATE

The missing int_or_null = %s or int_or_null = NULL part is apparently being cut in the visit_on_duplicate_key_update(...) function:

sqlalchemy/lib/sqlalchemy/dialects/mysql/base.py

Lines 1241 to 1242
in
e2521b5

if val is None:

continue

Issue 2:
Migrated issue, originally created by Michael Bayer (@zzzeek)

the ZBlog demo can illustrate this. this relationship in mapper.py:

Topic.mapper = mapper(Topic, tables.topics)

TopicAssociation.mapper = mapper(TopicAssociation,tables.topic_xref,
primary_key=[tables.topic_xref.c.topic_id](tables.topic_xref.c.post_id,),
properties={
'topic':relation(Topic.mapper, lazy=False),
})
Post.mapper = mapper(Post, posts_with_ccount, properties={
'id':posts_with_ccount.c.post_id,
'topics':relation(TopicAssociation, lazy=False, private=True, association=Topic)
}, is_primary=True, order_by=[desc(posts_with_ccount.c.datetime)](desc(posts_with_ccount.c.datetime)))

this creates TopicAssociation as a many-to-many association object. If you go to the interface and enter a post, and put the same topic name twice, it saves. This is the bug. the list of TopicAssociations should somehow be unique based on the Topic object its attached to, just like any other collection. then if you go to update that post, the update on the topicassocaitions returns 2 rows instead of 1 and the concurrency detector goes off.