WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
File "C:\[path]\api\utilities\tokenizers.py", line 4, in <module>
gpt2 = GPT2TokenizerFast.from_pretrained("gpt2")
File "C:\[path]\venv\lib\site-packages\transformers\tokenization_utils_base.py", line 1750, in from_pretrained
commit_hash = extract_commit_hash(resolved_vocab_files[file_id], commit_hash)
File "C:\[path]\venv\lib\site-packages\transformers\utils\hub.py", line 225, in extract_commit_hash
search = re.search(r"snapshots/([^/]+)/", resolved_file)
File "C:\Program Files\Python310\lib\re.py", line 200, in search
return _compile(pattern, flags).search(string)
TypeError: expected string or bytes-like object

Just started getting this error today, any idea for a workaround or a good version to rollback to?

Issue 2:
Just some context, we use TRANSFORMERS_OFFLINE=1 in the NeMo CI to ensure we load from the local cache. With the latest transformers version we noticed this bug in our CI!

System Info

transformers version: 4.22.1

Platform: Linux-5.15.0-41-generic-x86_64-with-glibc2.31

Python version: 3.9.12

Huggingface_hub version: 0.9.1

PyTorch version (GPU?): 1.12.1+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?: no

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

Who can help?

@SaulLu

Information

The official example scripts

My own modified scripts

Tasks

An officially supported task in the examples folder (such as GLUE/SQuAD, ...)

My own task or dataset (give details below)

Reproduction

Create this script reprod.py:

from transformers import AutoTokenizer

AutoTokenizer.from_pretrained(pretrained_model_name_or_path='gpt2')

run:

python reprod.py
TRANSFORMERS_OFFLINE=1 python reprod.py

First one runs successfully, second one fails:

Traceback (most recent call last):
File "/home/snarenthiran/NeMo/reprod.py", line 3, in <module>
AutoTokenizer.from_pretrained(pretrained_model_name_or_path='gpt2')
File "/home/snarenthiran/anaconda3/lib/python3.9/site-packages/transformers/models/auto/tokenization_auto.py", line 549, in from_pretrained
tokenizer_config = get_tokenizer_config(pretrained_model_name_or_path, **kwargs)
File "/home/snarenthiran/anaconda3/lib/python3.9/site-packages/transformers/models/auto/tokenization_auto.py", line 418, in get_tokenizer_config
commit_hash = extract_commit_hash(resolved_config_file, commit_hash)
File "/home/snarenthiran/anaconda3/lib/python3.9/site-packages/transformers/utils/hub.py", line 225, in extract_commit_hash
search = re.search(r"snapshots/([^/]+)/", resolved_file)
File "/home/snarenthiran/anaconda3/lib/python3.9/re.py", line 201, in search
return _compile(pattern, flags).search(string)
TypeError: expected string or bytes-like object

Expected behavior

To create the tokenizer from the local files.
Issue 1:
Since many follows a pull-request flow. It would be ideal if a developer could see a (HEAD+changes)-to-branch diff views and not ont only Changes-to-HEAD diff view as it is currently.

Many make some changes and makes some commits on a feature or bug branch. They push the new commits to their fork and review the changes before submitting a pull request. The review is a diff against, most likely, an upstream master branch. The problem is, that it is time consuming to make many micro changes online by force pushing etc. It would be more ideal if this diff view could be viewed locally in VSCode and not only on Github.

Issue 2:
It would be awesome to be able to squash commits right from the UI too
Issue 1:

Issue 2:
@gaearon You're arguing that ref functions need to be called twice (once with null) due to internal implementation details that are insignificant with respect to how end users use React.

End user don't care how their ref functions are called, just that they work. Honestly having them called twice is strange from a perspective of an end-user who knows nothing about React's internal implementation.

You haven't stated why end users actually need to guard against null values from duplicate calls to ref functions. It only complicates end-user code.

I would urge for the internal implementation to be modified to stop calling ref functions twice.
Issue 1:
You can find the correct location on the tree view, but on title the location don't change.

If this location is represent for the current folder on the view, it will confuse the user. It will be a disaster for a user editing 2 files with the same name in different folders.

I think this title is to indicate the current file location, so this must be a bug..

Issue 2:
When a project is open (i.e. the file browser is open), if I open the LICENSE or other non-project file, then the title bar will show like:

LICENSE -- /path/to/project

This is misleading because it implies that the LICENSE file is inside the /path/to/project when it is not. In fact... I have no idea where the hell LICENSE is. It would be better to have something else in the title bar. Recommendations are:

LICENSE

Atom - LICENSE

Atom - Version 0.179.0 - LICENSE

Now, for example, when I open "Open your Config", the titlebar shows config.cson -- /path/to/project, I am unsure if this is a global config file or if the file is actually saved at /path/to/project/config.cson.
Issue 1:
<a v-bind:[someAttr]="value"> ...

Issue 2:
Version

2.6.6

Reproduction link

https://jsfiddle.net/6s4cg2pv/3/

Steps to reproduce

when you open the fiddle you will see dynamic attributes refers camel case varibales(slotName , attributeName) but vue is looking for lower case variables.

if you cahange varibale names in data to slotname and attributename it works fine.

What is expected?

dynamic attribute variables must look for exact variable name

What is actually happening?

dynamic attributes refers camel case varibales but vue is looking for lower case variables.
Issue 1:
by damm@google.com:

I found a few issues with "Codelab: Writing Web Applications":

In section "Handling non-existant pages," the function signature includes a
third parameter, "title string" which is not introduced until later in the
last section. This may be confusing to some readers.

In section "Template caching," the code snippet for the init() function is not
in blockquote source code formatting.

In section "Validation," the code block for constructing the regular
expression is empty. I think it is supposed to read:

"""
var titleValidator regexp.Regexp = regexp.MustCompile("^[a-zA-Z0-9]+$")
"""

but there currently is nothing in the <pre> tag for that line.

Also, this is not an error, but it would be circumspect if you could give an example URL
that would be dangerous in the "Validation" section. When I tried to do
something nasty like "http://localhost:8080/view/../../../etc/passwd" or
similar, the URL was automatically rewritten to remove all '../' and preceding
directories. I suppose this is a part of the URL parsing in the http package? I was
able to form an attack only by creating more files underneath my tree (or soft-linking
my home directory from the go-wiki directory), and even then only when the extension
matched the one used for wiki content (which I had changed to .wiki early on). Even if
this is the extent of that possible attack, I agree that it's a good idea to mention it,
I just think a more specific example might be worthwhile.

Great tutorial, thanks for providing it!

Issue 2:
Under normal circumstances you would place test code into a file matching the test build constraint/tag, e.g. my_test.go. The naming convention of the file has led me to believe that this is a build constraint/tag.

However, it is not possible to exclude some code from being built into tests ran by go test, because writing a file like foo.go:

// +build !test

package foo

...

Will always compile under go test. This is a shame because there are some situations that do warrant different behavior for testing, and this makes it hard to deal with such situations.
Issue 1:
Emoji Keyboard Extension

In Windows 10, we have a special emoji keyboard for whenever we need to add emoji while writing anything. but it would be great if I don't have to switch to keyboard. Like suppose if I write :rocket then it should be automatically turned to emoji 🚀 . Same way we use emojis on Github. If we can use this extension in whole Windows 10 PC ecosystem. It will be great !!. It will be great of user experience as we do it on mobile platforms such as when we write some key words that matches to a emoji it suggests us to use an emoji. Using this extension we can add this feature to Windows PCs.

We can do it easily on mac using Rocket app. But I just don't think there's another way to do it on PC without using emoji keyboard.

Let me know what you think of this guys.

Issue 2:
A simple text replacement tool, my examples are from macOS and iOS, it is also a feature in Android.

Basically this feature: Text Replacements

On your Mac, choose Apple menu > System Preferences, click Keyboard, then click Text.

Another example: Third one down "Set up text replacement"

It's very handy if you have things you need to type regularly, and just typing one word and having my system fill in a whole sentence saves a lot of time and effort at work instead of keeping a copy past text file. I have many web addresses I send to customers and many full sentences for my notes at work that used repeatedly and this kind of feature is surprisingly missing from Windows.

Sorry to open a new issue for this, but my last one was closed already.
Issue 1:
Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.17763.292]

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

When using the new ConPTY feature it seems there is some behind the scenes optimisation happening surrounding colours that is assuming colour state. For example when using the default background/foreground escape sequences ([49m/[39m), they are either getting removed or changed into a reset sequence ([m), this make it difficult to write a frontend to ConPTY that wants to for example have a window background colour that isn't one of the colours specified by the escape sequences. (i.e. where [m and [49m would do different things).

And example of this is at https://github.com/brads55/conpty-testcase (based on the EchoCon sample), where the following can be seen:

I also suspect this is the cause of #293.

What's wrong / what should be happening instead:

It would be great if either these optimisations didn't happen or there was at least a way of disabling them in order to get the real raw escape sequences.

Issue 2:
bash repro: echo -e '\x1b[40mabc'

powershell repro: Write-Host -BackgroundColor Black "Hello"

Expected (conhost/powershell.exe):

Actual (vscode/conpty):
Issue 1:
Simon Wong opened SPR-9479 and commented

The Spring reference didn't mention that I MUST use @Configuration for the configuration class being imported. And I found that the bean could be created normally most of the time.

The case I found that if @Configuration is missing, transaction is not behave normally in some cases.

I have setup a simple program to illustrate this. Please refer to "readme.txt" for the running procedures. From the log, I have checked that the transaction commit command has been issued, but the end result is the value is not committed.

In the example, I have already used SingleConnectionDataSource, to avoid multiple database connection issue.

I have also tried to move the @EnableTransactionManagement and transactionManager() to other Spring Java Config class (no matter with/without @Configuration), but the problem still occurs.

Affects: 3.1.1

Attachments:

TestSpring31Transaction.zip (8.20 kB)

Issue Links:

#13690 spring-test allows you to reference configuration classes that aren't annotated with @Configuration ("duplicates")

Issue 2:
Keith Donald opened SPR-9051 and commented

When a @ContextConfiguration test class references a config class missing a @Configuration annotation, @Bean dependencies are wired successfully but the bean lifecycle is not applied (no init methods are invoked, for example). Adding the missing @Configuration annotation solves the problem, however the problem and solution isn't obvious since wiring/injection appeared to work.

It would be better if an integration test failed-fast if you reference a config class with no @Configuration annotation.

Affects: 3.1 GA

Issue Links:

#14114 Missing @Configuration annotation will cause transaction not working ("is duplicated by")

#14061 Document @Bean 'lite' mode and annotated classes in the reference manual

#15002 Log warning when using inner-bean referenced without @Configuration

#15599 Throw exception when @ContextConfiguration#classes are not annotated with @Configuration

#14037 Improve documentation for @Bean 'lite' mode and annotated class support in the TestContext Framework ("is superseded by")

Referenced from: commits 500a4dd, 2017b24, 1cec0f9, 78c6d70

0 votes, 5 watchers
Issue 1:
There seems to be a bug in the way React interfaces with controlled inputs of type number

If the input contains an invalid number (let's say --2 or 2++), then trying to clear the input value by setting it to an empty string does nothing.

You can check an example to reproduce there: https://jsfiddle.net/96bnn12r/2/

The onChange handler will set the controlled value to the value returned by ev.target.value.

In the case of an invalid value, the input returns an empty string (as per html spec https://html.spec.whatwg.org/multipage/forms.html#states-of-the-type-attribute 4.10.5.1.12) so this should actually clear the input but the invalid input stays.

When setting the input value to an empty string after entering an invalid value, it should clear the input content not keep the invalid value.

Seen in React 0.14.8, 15.0.1, 15.1.0 on OSX Chrome v50, Firefox 46.0.1

Issue 2:
A controlled number input, without a corresponding setState function, still allows e, - and . to be entered (and numbers can be inputted afterwards). I could be incorrect but I don't believe this is the desired behavior.

Here's a JSFiddle demonstrating the issue.
Issue 1:
Describe the bug

https://threejs.org/examples/webgl_water_flowmap.html works in Safari/Firefox, but not Chrome

To Reproduce

Steps to reproduce the behavior:

In Chrome (Version 85.0.4183.121)

Go to https://threejs.org/examples/webgl_water_flowmap.html

Water doesn't flow. No errors in console.

Code

https://github.com/mrdoob/three.js/blob/dev/examples/webgl_water_flowmap.html

Live example

https://threejs.org/examples/webgl_water_flowmap.html

Expected behavior

Example works

Screenshots

Platform:

Device: Desktop

OS: MacOS 10.15.7

Browser: Chrome Version 85.0.4183.121

Three.js version: dev

I first noticed this issue while browsing and studying http://swamp.lt/. I remember it was working in a Chrome version 3 months ago when I first see it. FYI @Mugen87

Issue 2:
Description of the problem

No errors or warnings in the console (some discrepancy in the shader code for my old computer's gpu?), and no water:

It renders fine in other browsers.

Three.js version

Viewed from the latest website examples (https://threejs.org/examples/?q=water#webgl_water)

Browser

Chrome, Version 73.0.3683.86 (Official Build) (64-bit)

OS

macOS 10.14.1

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

MBP 15-inch Late 2013

GPU: Intel Iris Pro 1536 MB
Issue 1:
Add ability to save remote connection bookmarks - similar to mRemoteNG

Proposed technical implementation details (optional)

Can be based on the native Windows SSH client.

Issue 2:
Summary of the new feature/enhancement

My most used feature of Cmder is the shortcut to bring Cmder to the foreground whether it is minimized or just in the background and then minimize it when it is open.

by default that's ctrl + `

It overrides a few programs because the key combo is no longer passed through to the current foreground task, notably Vscode wont toggle console because Cmder captures it, which is a desirable outcome for me.
Issue 1:
by mikaelbrg:

After updating from go1.0.3 to tip, I am no longer able to build my module, which uses a
.so-file and cgo (to communicate with hardware). The log below shows the result of
building with the latest tip version (produces error), and with go1.0.3 (successful).

mikaelbe@ITK-D727 ~/work/sotest
$ go version
go version devel +9ca85035f95a Thu Mar 21 22:37:13 2013 -0700 windows/amd64

mikaelbe@ITK-D727 ~/work/sotest
$ go build sotest
# sotest
C:\Users\mikaelbe\AppData\Local\Temp\go-build854994423\sotest.a(_all.o): malform
ed pe file: unexpected flags for PE section .idata$2

mikaelbe@ITK-D727 ~/work/sotest
$ go version
go version go1.0.3

mikaelbe@ITK-D727 ~/work/sotest
$ go build sotest

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. Source code with .go, .so and .h files available at
https://bitbucket.org/mikaelbe/sotest/overview
2. Build with "go build sotest"

What is the expected output?
Executable file

What do you see instead?
Error as shown in log above

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

Which operating system are you using?
Windows 7 (64-bit)

Which version are you using? (run 'go version')
go version devel +9ca85035f95a Thu Mar 21 22:37:13 2013 -0700

Mikael

Issue 2:
It would be useful if PublicKey interface has Fingerprint method which returns the value described bellow:

http://tools.ietf.org/html/rfc4716#section-4

Now I'm trying to make my ssh server with go.

When I made it with python twisted.conch, I used twisted.conch.ssh.keys.Key#fingerprint method to find user's public key, It was useful.
Issue 1:
Migrated issue, originally created by Michael Bayer (@zzzeek)

i.e.:

def get_history(self, state, passive=PASSIVE_OFF):
return History.from_attribute(
self, state, state.dict.get(self.key, NO_VALUE))

should be more like:

def get_history(self, state, passive=PASSIVE_OFF):
if self.key in state.dict:
return History.from_attribute(self, state, state.dict[self.key](self.key))
else:
current = self.get(state, passive=passive)
if current is PASSIVE_NORESULT:
return HISTORY_BLANK
else:
return History.from_attribute(self, state, current)

this to support extensions which need to get attribute history regardless of an object being expired or having deferred columns. workaround is to force a load using getattr(). but the passive flag shouldn't be silently ignored.

however, SA's ORM doesn't need this itself, and the fact that it's ignored right now might be fulfilling part of the current behavioral contract, i.e. don't load the old value unnecessarily. So ensure that get_history() is always called with PASSIVE_OFF for scalars right now and that honoring the flag doesn't result in unnecessary loads.

Issue 2:
Migrated issue, originally created by Anonymous

We are doing some stuff with history and have a little problem.

After commit, history has been reseted to empty state: there no value in unchanged and after attribute is changed there is no value in deleted.

Probably, it is a bug. If it is correct behaviour, how is it expained?

Both on 0.8.2 and dev versions. Here is a test case.

class HistoryTest(_fixtures.FixtureTest):
run_inserts = None

def test_commit_history(self):
from sqlalchemy.orm.attributes import get_history, History

User, users = self.classes.User, self.tables.users

m2 = sa.MetaData()
users_unbound = users.tometadata(m2)
mapper(User, users_unbound)

sess = Session(binds={User: self.metadata.bind})
u = User(id=1, name='daniel')
sess.add(u)
print get_history(u, 'name')
assert get_history(u, 'name') ==\
History(['daniel']('daniel'), (), ())

sess.commit()
print get_history(u, 'name')
assert get_history(u, 'name') == \
History((), ['daniel']('daniel'), ())
# fails: History((), (), ())

u.name = 'peter'
print get_history(u, 'name')
assert get_history(u, 'name') == \
History(['peter']('peter'), (), ['daniel']('daniel'))
# fails: History(['peter']('peter'), (), ())

Attachments: 2787.patch
Issue 1:
Not sure how the character got into my code but it does not show up in Atom even with Show Invisibles set to true.

Info on the character can be found here http://www.fileformat.info/info/unicode/char/200b/index.htm

My specific issue: If this character comes after a CSS closing curly bracket, all following styles are inaccessible and do not parse.

Example: https://jsfiddle.net/9tuy9w8o/2/

Setting the image class to cat works but setting it to dog causes it to break.

Issue 2:
Halp ticket:

support/b6556d18b6f511e396195226a240cace

Control characters aren't showing up. For example, create a file in vim and type ctl+v,ctl+h to insert a backspace character in a shell script and notice that it is invisible in Atom. Maybe not all invisibles should be hidden. Then again, I just started using this today, so maybe I haven't discovered the proper setting.

Screenshot time! Here's Vim:

And here's Sublime:

And Atom:
Issue 1:
It would be nice to have the published development docs to actually reflect the current state of master.

This has come up recently with a couple of issues being raised about typos etc. in them which were already fixed on master (e.g. #7444 )

I would envision a similar solution to the one that scipy uses scipy/scipy#5383

I'd be happy to work on this but I think this will need to have some input from one the numpy devs. Their solution hosts the devdocs on github pages then redirects the docs.scipy.org to point to that. Obviously as a mere mortal that part I wouldn't be able to setup!

Issue 2:
The exponents in the denominators of the Freedman–Diaconis and Scott estimators are shown incorrectly in the typeset maths on this page:

http://docs.scipy.org/doc/numpy-dev/reference/generated/numpy.histogram.html

The offending lines of source code were corrected in commit 41de3c2 in December, and incorporated on the maintenance/1.11.x branch, but the generated documentation doesn't yet reflect this, having been last updated in October.
Issue 1:
Currently the common directives (CORE_DIRECTIVES and FORM_DIRECTIVES) are included automatically and do not need to be manually referenced in a component's @view annotation. However this is not the case for the TestComponentBuilder, which fails to build the component if the component uses unreferenced common directives. An example error message is:

{"message":"Template parse errors: Can't bind to 'ngFormControl' since it isn't a known native property...

It's possible to add these references in to the component definition, but ideally the TCB should be able to build whatever Angular builds normally. Also the way the TCB handles errors (calling the onrejected callback of the promise, which I seldom see anyone binding to) means that tests can be regarded as passing if the component fails to build:

tcb.createAsync(testComponent).then((fixture: ComponentFixture) => {
expect(true).toBe(false)
})

Will pass if the TCB fails to create the component.

So proposed solution would be to make the common directives available to the TCB.

Issue 2:
Spotted by @teropa and confirmed on my side in the ng2 directives for Bootstrap project (see: ng-bootstrap/ng-bootstrap#115):

I'm getting errors about platform directives like ng-for when using TestComponentBuilder. Seems like they're not "ambient" in the unit tests like they are during normal execution. I can fix it by including CORE_DIRECTIVES in the component, but that seems backward. Any ideas how to make them available?