WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Atom 0.158 on Mac OS.

Pushing up/down arrow key, I expected the cursor to move to the nearest location vertically.

tab indent also seems to be laid out in wrong way.

Issue 2:
Atom has a problem in dealing with Devanagari, in that the cursor position does not always reflect the actual position if there is some Devanagari text in the current line. Same goes for selecting within lines containing Devanagari.

I can also see that Atom renders Devangari as fully formed Devangari with half-forms, conjuncts (ligatures), and so on. For an editor I would much prefer the Sublime Text approach, where Devanagari text is treated as a string of characters with no attempt to render half-forms, conjuncts, and do the other advanced OpenType compositing features. Instead the text is rendered the way it is typed, which is much much easier to edit.

Here is some sample text that borks Atom:

<span class="Glyphs">NO LANG ‘रृ’ “रॄ” ल- लृ–!!!???,.</span></span></br>

(Try here to select the ??? and delete them…)

<span class="ModelNorthern">रृ रॄ ल लृ लॄ ऌ ॡ </span></b>

(Try here to select the Devanagari characters and delete them…)

Also try to paste those strings into Sublime Text and see how ST renders the Devanagari as full-forms + halants/virama + matras in sequential order, which I would prefer.

Because the monospaced fonts we use often do not have Devanagari, the Devanagari is rendered in a proportional fall-back font. If you did as in Sublime Text you could force the advance-width of all the Devanagari glyphs to be the same as the default monospaced font. That way you could preserve monospaced text and get around the whole – very thorny – issue of mixing in complex non-latin scripts in a monospaced environment.

Just an idea, so up to you to find out if that would actually be a way to go.

I note that you have partially fixed the issue in 0.140, but it’s still not perfect. Take this example line:

<span style="word-wrap: break-word">क ख ग घ ङ च छ ज झ ञ ट ठ ड ढ ण त थ द ध न प फ ब भ म य र ऱ ल ळ व श ष स ह क़ ख़ ग़ ज़ ड़ ढ़ फ़ य़ ॹ ॻ ॼ ॾ ॿ</span><br><br>

If you try to select it with the mouse, from the end towards the beginning of the line, then the last br> is not selected.

If you select the Devanagari text and press delete, then you end up with this:

<span style="word-wrap: break-word">pan><br><br>

(notice the missing </s in the closing span tag).

Atom Version: 0.140.0

OS Version: Mac OS X 10.10

Misc Versions

�apm� �0.108.0�

�npm� �1.4.4�

�node� �0.10.32�

�python� �2.7.6�

�git� �1.9.3�
Issue 1:
Hey all, just learning Deno. Nice docs so far, clear, concise, consistent.

Anyway, this page is a 404.

https://deno.land/manual@v1.28.1/runtime/cache_api

Issue 2:
Hi Deno Team,

I upgraded to Deno 1.31.2 today and found some extremely annoying behavior in deno-fresh.

I report that here, since fresh did not change and the behavior appeared directly after upgrading to Deno 1.31.2.

I'm working on this repo based on deno-fresh: https://github.com/codemonument/deno_audio_logbook.

Problem

When I start the dev server by using deno task start,

it works at first (*), but when I change anything in any watched file,

it seems to recompile successfully, but it can't restart the server correctly:

deno task start
Task start doppler run -- deno run -A --cached-only --watch=static/,routes/ dev.ts
Watcher Process started.
The manifest has been generated for 5 routes and 4 islands.
loadSecrets: 462ms
initDb: 813ms
Watcher File change detected! Restarting!
loadSecrets: 828ms
initDb: 1331ms
PostCSS Transformed and Cached: /Users/bjesuiter/Develop/codemonument/deno_audio_logbook/css/global.css { fileHash: "ptYaR1kyC6IFD87cIeOC6y9DmGXlAE8T6/ALXQzupNk=" }
error: Uncaught AddrInUse: Address already in use (os error 48)
const listener = Deno.listen({
^
at Object.listen (ext:deno_net/01_net.js:356:39)
at Server.listenAndServe (https://deno.land/std@0.150.0/http/server.ts:181:27)
at serve (https://deno.land/std@0.150.0/http/server.ts:589:20)
at start (https://deno.land/x/fresh@1.1.4/src/server/mod.ts:70:11)
at async file:///Users/bjesuiter/Develop/codemonument/deno_audio_logbook/main.ts:14:1
Watcher Process finished. Restarting on file change...

(*) - after restarting VSCode, simply starting the server has the same problem.

I can resolve it though by manually killing all deno instances running on my system and restarting vscode.

deno task start
Task start doppler run -- deno run -A --cached-only --watch=static/,routes/ dev.ts
Watcher Process started.
The manifest has been generated for 5 routes and 4 islands.
loadSecrets: 462ms
initDb: 813ms
PostCSS Transformed and Cached: /Users/bjesuiter/Develop/codemonument/deno_audio_logbook/css/global.css { fileHash: "ptYaR1kyC6IFD87cIeOC6y9DmGXlAE8T6/ALXQzupNk=" }
error: Uncaught AddrInUse: Address already in use (os error 48)
const listener = Deno.listen({
^
at Object.listen (ext:deno_net/01_net.js:356:39)
at Server.listenAndServe (https://deno.land/std@0.150.0/http/server.ts:181:27)
at serve (https://deno.land/std@0.150.0/http/server.ts:589:20)
at start (https://deno.land/x/fresh@1.1.4/src/server/mod.ts:70:11)
at async file:///Users/bjesuiter/Develop/codemonument/deno_audio_logbook/main.ts:14:1
Watcher Process finished. Restarting on file change...
Issue 1:
table class="table visible-phone" causes the table rows only to be as wide as the content they hold. As the table has width 100% I thought the table rows would also be 100%.

http://jsfiddle.net/leeaston/9vXGq/

Perhaps I'm confused...

Issue 2:
Hi,

I'm building an application with Twitter Bootstrap one of the reasons because I need it to be responsive and readable with hand-held devices.

The responsive layout works like a charm, but tables not so much, they have a fixed min width where they can't go any thiner, I get that, but it would be so cool if the tables would be responsive, meaning when they can't go any thinner they change their layout to show the information somehow to fit the screen.

I don't know how would you achieve this, maybe changing the scale (or zoom) on the table so it go smaller, since on a hand-held you can zoom in with a pinch.

Is there an easy solution to solve this?

Thanks!
Issue 1:
today, i updating my xcode turns into version 10. after that i keep failed to run my application project. it says :

Xcode's output:
↳
error: Multiple commands produce '/Users/lumos/Office/Git Project/ios/tanamduit-ios-app/tanamduit-app-ios/build/ios/Debug-iphoneos/Runner.app/Frameworks/Flutter.framework':
1) Target 'Runner' has copy command from '/Users/lumos/Office/Git Project/ios/tanamduit-ios-app/tanamduit-app-ios/ios/Flutter/Flutter.framework' to '/Users/lumos/Office/Git Project/ios/tanamduit-ios-app/tanamduit-app-ios/build/ios/Debug-iphoneos/Runner.app/Frameworks/Flutter.framework'
2) That command depends on command in Target 'Runner': script phase “[CP] Embed Pods Frameworks”
warning: The iOS deployment target is set to 7.0, but the range of supported deployment target versions for this platform is 8.0 to 12.0. (in target 'Protobuf')
warning: The iOS deployment target is set to 5.0, but the range of supported deployment target versions for this platform is 8.0 to 12.0. (in target 'GoogleToolboxForMac')
warning: The iOS deployment target is set to 4.3, but the range of supported deployment target versions for this platform is 8.0 to 12.0. (in target 'nanopb')
warning: The iOS deployment target is set to 6.0, but the range of supported deployment target versions for this platform is 8.0 to 12.0. (in target 'firebase_analytics')
warning: The iOS deployment target is set to 6.0, but the range of supported deployment target versions for this platform is 8.0 to 12.0. (in target 'firebase_remote_config')
warning: The iOS deployment target is set to 4.3, but the range of supported deployment target versions for this platform is 8.0 to 12.0. (in target 'image_picker')
warning: ignoring duplicated output file: '/Users/lumos/Office/Git Project/ios/tanamduit-ios-app/tanamduit-app-ios/build/ios/Debug-iphoneos/Runner.app/Frameworks/Flutter.framework' (in target 'Runner')
note: Using new build systemnote: Planning buildnote: Constructing build description

right before i update my xcode its run as well . Here my flutter doctor:

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v0.8.2, on Mac OS X 10.13.6 17G65, locale en-ID)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[!] iOS toolchain - develop for iOS devices (Xcode 10.0)
! CocoaPods out of date (1.5.0 is recommended).
CocoaPods is used to retrieve the iOS platform side's plugin code that responds to your plugin usage on the Dart side.
Without resolving iOS dependencies with CocoaPods, plugins will not work on iOS.
For more info, see https://flutter.io/platform-plugins
To upgrade:
brew upgrade cocoapods
pod setup
[✓] Android Studio (version 3.0)
[!] VS Code (version 1.27.2)
[✓] Connected devices (3 available)

! Doctor found issues in 2 categories.

Issue 2:
From URL: https://flutter.io/tutorials/layout/

The "Title Section" figure is duplicated.
Issue 1:
Hi,

I am working with tensorflow to build a network using mnist data set but it is showing connection refused error.

File "neuralnw1.py", line 4, in

mnist = input_data.read_data_sets('MNIST_data', one_hot=True) # one-hot -> '2' = (0,0,1,0,0,0,0,0,0)

File "/usr/local/lib/python3.4/dist-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py", line 189, in read_data_sets

SOURCE_URL + TRAIN_IMAGES)

File "/usr/local/lib/python3.4/dist-packages/tensorflow/contrib/learn/python/learn/datasets/base.py", line 157, in maybe_download

urllib.request.urlretrieve(source_url, temp_file_name)

File "/usr/lib/python3.4/urllib/request.py", line 186, in urlretrieve

with contextlib.closing(urlopen(url, data)) as fp:

File "/usr/lib/python3.4/urllib/request.py", line 161, in urlopen

return opener.open(url, data, timeout)

File "/usr/lib/python3.4/urllib/request.py", line 463, in open

response = self._open(req, data)

File "/usr/lib/python3.4/urllib/request.py", line 481, in _open

'_open', req)

File "/usr/lib/python3.4/urllib/request.py", line 441, in _call_chain

result = func(*args)

File "/usr/lib/python3.4/urllib/request.py", line 1210, in http_open

return self.do_open(http.client.HTTPConnection, req)

File "/usr/lib/python3.4/urllib/request.py", line 1184, in do_open

raise URLError(err)

urllib.error.URLError: <urlopen error [Errno 111] Connection refused>

Issue 2:
The website of Yann LeCun is down at the moment.

Therefore the MNIST-Script for downloading the files doesn't work either. (-> learn/python/learn/datasets/mnist.py won't work)

Are there any mirrors?
Issue 1:
As of next version "next": "^2.0.0-beta.22"

Whenever you use a _document.js fragment to overwrite the default construction of the page document, styles are not applied when getInitialProps() is used.

If you comment out getInitialProps(), then styles will be applied. They DO NOT however hot load, and require a page refresh. Change to use <styled jsx global> does not resolve issue.

Expected that styled jsx applies styles (global or not) regardless of the use of getInitalProps(). Also expected to hot load like any other page in the application.

import Document, { Head, Main, NextScript } from 'next/document'

export default class MyDocument extends Document {
static async getInitialProps ({ renderPage }) {
const page = renderPage()
return { ...page }
}

render () {
return (
<html>
<Head>
<title>Site Title</title>
</Head>
<body>
<Main />
<NextScript />
</body>
<style jsx global>{`
html, body {
background-color: #f00;
font-size: 16px;
color: #fef;
}
p {
color: red;
}
`}</style>
</html>
)
}
}

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

I'd like to use a custom sub directory to store my "pages". I looked in the next.config.js but couldn't find any way of customizing it. Also, I found https://github.com/zeit/next.js/blob/07af67bfea3eb366c3b3457db9534d532d2e902b/server/build/webpack/utils.js#L4 which makes me thing it's not possible yet.

Is this something you intend to support?
Issue 1:
Is this confusing performance a bug? Version 1.3.1

img = rand(512,512,16)
@time mapslices(sum, img, dims=[3])
@time sum([img[:,:,i] for i=1:size(img)[3]])

0.423263 seconds (2.89 M allocations: 74.065 MiB, 2.89% gc time)
0.054033 seconds (53.06 k allocations: 64.729 MiB)

Issue 2:
julia> displaysize(stdout)
(17, 160)

julia> displaysize(IOContext(stdout))
(17, 160)

julia> sprint(; context=stdout) do io
print(io, displaysize(io))
end
"(24, 80)"

Imo, the last one should be consistent with the others.

Workaround:

julia> ioc = IOContext(stdout, :displaysize=>displaysize(stdout));

julia> sprint(; context=ioc) do io
print(io, displaysize(io))
end
"(17, 160)"
Issue 1:
Description

Provide a next run field in the DAG details page for scheduled dags

Use case / motivation

Schedules can be trick to get at a first glance (since it related to start_date and schedule_interval). We could help users to easily see when the DAG will run next time

Are you willing to submit a PR?

Maybe 😁

Issue 2:
Description

The old documentation for Common Pitfalls should be reviewed and incorporated in Airflow Docs

Use case / motivation

To remove documentation duplication and clean it up.

Related Issues

#10178
Issue 1:
I guess it's a bit late now, but couldn't have not only the runtime be written in Rust but also every other API and be compiled to WASM? in the longer term it would translate in faster start-up times better more predictable performance. I imagine the community could later create a WASM version of the std and any other API right? or are there major blockers that make it hard to do?

Issue 2:
This might not be the best place to ask this, but I'm not sure where if not here. I've starred deno a while ago - year maybe more, but compilation-to-JavaScript step is basically a turnaway point. I know there are lots of benefits in using deno over node, but the only one that matters I think is just that - bypassing JavaScript altogether. How feasible is that? Is there anyone working on that currently? Why not compile directly to WebAssembly for example?
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/435 on 2007-01-24 by @chanley, assigned to unknown.

The accumulator used in the mean algorithm should not be single precision by default. This default can cause unexpected results. Please see the following example:

In [5]: a.dtype
Out[5]: dtype('>f4')

In [6]: print a
[[ 132. 132. 132. ..., 132. 132. 132.]
[ 132. 132. 132. ..., 132. 132. 132.]
[ 132. 132. 132. ..., 132. 132. 132.]
...,
[ 132. 132. 132. ..., 132. 132. 132.]
[ 132. 132. 132. ..., 132. 132. 132.]
[ 132. 132. 132. ..., 132. 132. 132.]]

In [7]: a.min()
Out[7]: 132.0

In [8]: a.max()
Out[8]: 389.0

In [9]: a.mean()
Out[9]: 129.742439153

However, if you recast the array as float64 you get the correct result:

In [11]: a.astype(numpy.float64).mean()
Out[11]: 132.062805059

I believe that double precision would be a more appropriate default type for the accumulator.

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/465 on 2007-03-07 by @chanley, assigned to unknown.

The default data type for the accumulator variable in the mean method should be double precision. The problem can best be illustrated with the following example:

Python 2.4.3 (#2, Dec 7 2006, 11:01:45)
[GCC 4.0.1 (Apple Computer, Inc. build 5367)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy as n
>>> n.__version__
'1.0.2.dev3571'
>>> a = n.ones((1000,1000),dtype=n.float32)*132.00005
>>> print a
[[ 132.00004578 132.00004578 132.00004578 ..., 132.00004578
132.00004578 132.00004578]
[ 132.00004578 132.00004578 132.00004578 ..., 132.00004578
132.00004578 132.00004578]
[ 132.00004578 132.00004578 132.00004578 ..., 132.00004578
132.00004578 132.00004578]
...,
[ 132.00004578 132.00004578 132.00004578 ..., 132.00004578
132.00004578 132.00004578]
[ 132.00004578 132.00004578 132.00004578 ..., 132.00004578
132.00004578 132.00004578]
[ 132.00004578 132.00004578 132.00004578 ..., 132.00004578
132.00004578 132.00004578]]
>>> a.min()
132.000045776
>>> a.max()
132.000045776
>>> a.mean()
133.96639999999999

Having the mean be greater than the maximum is a tad odd.

The calculation of the mean is occurring with a single precision accumulator variable. A user can force a double precision calculation with the following command and receive a correct result:

>>> a.mean(dtype=n.float64)
132.00004577636719
>>>

However, this is not going to be obvious to the casual user and will appear to be an error.

I realize that one reason for not doing all calculations as double precision is performance. However, it is probably better to always receive the correct answer than to quickly arrive at the wrong one.

The current default behavior needs to be changed. All calculations should be done in double precision. If performance is needed the "expert user" can go back and start setting data types after having shown that their application arrives at a correct result.

Not having to worry about overflow problems in the accumulator variable would also make numpy consistent with numarray's behavior.
Issue 1:
Please, add backends based on PySide6 (successor of PySide2) and PyQt6 as the new Qt6 engine lives now.

Many thanks ;-).

Issue 2:
Both qt6 and gtk4 have been recently released. qt6 already has a working python binding in pyside6; i guess both qt6 and a gtk4-supporting pygobject should be available "soon". (For qt6 I first raised the issue #16836 but that issue ended up being mostly about qt4.)

It turns out to be very easy to support pyside6 -- it's just a couple of import renames and certain things having moved out of the Qt namespace -- and I basically already have a patch for that. The main question, however, is whether we want to put that support in a "qt6agg" (and "qt6cairo") backend, or if we decide to move towards having a single "qtagg" (and "qtcairo") backend and fully move qt binding selection to 1) checking if anything is already imported in the process and 2) the QT_API environment variable.

Even as of today, if one selects the qt5agg backend but already has PyQt4 imported in the process, we'll silently switch to qt4agg for you (well, modulo the deprecation warning for qt4 support), so we already treat the two backends as somewhat interchangeable. Although I guess one of the reasons for doing so was that it was not possible to import both PyQt4 and PyQt5 into the same process at all (the second import would fail); I don't know if that's also going to be the case for qt6...

I'd say it makes sense to just have a single qtagg backend instead. The alternate solution of having both qt5agg and qt6agg would probably involve copy-pasting all of backend_qt5agg.py into backend_qt6agg.py, and then replacing backend_qt5agg.py by a small stub similar to the current backend_qt4agg.py, which is a bit... ugh.

The same question basically exists for gtk3/gtk4, although perhaps we can wait for a pygobject release that supports gtk4 to make sure it'll indeed make sense to go back to a single gtkagg. There we'd need to introduce a new GTK_API environment variable though? Also, there's the additional question of whether that'll confuse people using fairly old docs/versions and confusing that with the old gtkagg (=gtk2) backend, which was removed in matplotlib 2.0... (also, note that a non-numbered qtagg backend also existed back in the times of qt3(!) support (which was removed in matplotlib 1.3).)

TL;DR: 1) perhaps wait for PyQt6 and "pygobject4" before deciding on what to do with PySide6; 2) perhaps move to a single backend_qtagg and a single backend_gtkagg instead of splitting by version?
Issue 1:
After upgrading Angular and CLI versions, I'm getting error only when building for production

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

when used common ng build, it builds with no problem

When used ng build --prod, gives an error:

Expected behavior

Prod build should work too

Minimal reproduction of the problem with instructions

app.module.ts:

import { BrowserModule } from '@angular/platform-browser';

import {NgModule} from '@angular/core';

import {CommonModule} from '@angular/common';

import {HttpModule} from '@angular/http';

import { AppComponent } from './app.component';

@NgModule({

declarations: [ AppComponent],

imports: [ ],

providers: [{ provide: 'Window', useValue: window }],

bootstrap: [AppComponent]

})

export class AppModule { }

some-class.ts:

import {Inject , Injectable} from '@angular/core';

@Injectable()

export class ServiceBase {

private _urlPrefix = "http://";

private _urlPostfix = ":8080/mycode/";

constructor(
@Inject('Window') window: Window
) {}

public get servcieURL() : string {
return this._urlPrefix + window.location.hostname + this._urlPostfix;
}

}

now build using ng build : works

now build again using ng build --prod, it fails

Please tell us about your environment:

Node: V7.5.0

NPM: 4.1.2

Angular: 2.4.0

Angular CLI: 1.0.0-rc.0

Angular version: 2.4.0

Browser: [Chrome XX ]

Language: [TypeScript 2.0.0 ]

Node (for AoT issues): node --version = V7.7.0

Issue 2:
Currently Component and routable component lifecycles are defined via interfaces (e.g. OnInit).

This is problematic because the interfaces have no runtime representation in JavaScript. So at runtime, we just check if the method defined in the interface (e.g. onInit) exists on the component instance and if it does we call it. If a component has a method onInit that is not meant to be a lifecycle hook, we'll still call it.

These name collisions can result in surprising results, and if we add new lifecycle hooks, we can end up breaking existing components.

For these reasons, I propose that we move away from interfaces and use property decorators instead.

Before:

import {Component, OnInit} from 'angular2/angular2';

@Component({
selector: 'test-foo'
})
class TestFoo implements OnInit {
onInit() { ... }
}

After:

import {Component, OnInit} from 'angular2/angular2';

@Component({
selector: 'test-foo'
})
class TestFoo {
@OnInit() onInit() { ... }
}

Dart notes: this api can be implemented via transformers for production and via mirrors for development mode.

Migration notes: I'm not sure how to deal with migration just yet because we are going to reuse the same symbol for different purpose. there might be no good way to provide a transitional path, which would argue for making this change asap.

//cc: @mhevery @vsavkin @tbosch @btford