WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Keith Donald opened SPR-7973 and commented

I found the following odd with @ImportResource usage:

The @ImportResource ResourceLoader does not appear to be the same ResourceLoader as the ApplicationContext. I am using a AnnotationConfigWebApplicationContext, and I got classpath-relative resources by default.

Configuration-class relative resource resolution does not work, and one might expect it to. For example, if I import @ImportResource("mvc-interceptors.xml") from the com.springsource.greenhouse.config.mvc package, I'd expect "mvc-interceptors.xml" to be in that package, and not the root of the classpath. Having to specify "com/springsource/greenhouse/config/mvc/mvc-interceptors.xml" is a lot more to type and feels strange.

Affects: 3.1 M1

Attachments:

mylyn-context.zip (26.03 kB)

Issue Links:

#12630 Dependency injection not supported on @FeatureConfiguration classes

Referenced from: commits 4cdb04a

Issue 2:
Chris Beams opened SPR-6310 and commented

Much like Spring's TestContext framework and its @ContextConfiguration annotation, processing @Configuration classes should support relative paths and loading resources by convention when using @ImportXml:

Relative paths:

package com.biz.app;
@Configuration
@ImportResource("Foo.xml")
public class AppConfig { ... }

It is assumed that Foo.xml resides in com.biz.app, the same package in which AppConfig is declared.

Import by convention:

package com.biz.app;
@Configuration
@ImportResource
public class AppConfig { ... }

It is assumed that classpath:/com/biz/app/AppConfig-context.xml exists.

See testImportXmlWithRelativePath() and testImportXmlByConvention(), which are both currently @Ignore'd in org.springframework.context.annotation.configuration.ImportXmlTests. See also TODO in ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsFromXml()

Issue Links:

#10826 Support @ImportResource within @Configuration classes ("depends on")

#13003 Relative imports in @Configuration classes

#10993 Preserve 'reader' attribute in @ImportResource hierarchies

Referenced from: commits ae11387

1 votes, 3 watchers
Issue 1:
Normally the columns in a row should float left in a row. When the row becomes to small for wrapping the columns, the columns should stack below and float again. Why is my last column not stacking in the small screen size (sm). Instead it floats also to the left on the first row of columns and dissapears behind the other, so it is not visible anymore. This is only with the class col-sm-12.

Now I solved it with col-sm-11 and that is stacking properly, but it is not what it should have been.

Issue 2:
The probleme occurs when viewing this frgment of page on a small screen : the "heading 1.1" and "heading 1.2" blocks are not displayed.

I am using Bootstrap 3.0.0, chrome 29.0.1547.57 on Linux.

In this example, i am not using any CSS or Javascript files except bootstrap.min.css, jquery-1.10.2.min.js and bootstrap.min.js.

You can also see it here : http://jsfiddle.net/tFHCY/

Here is the HTML code :

<section class="row">
<section class="col-lg-3 col-xs-6">
<div style="background-color:#CE45FF" class="heading">
<h2>Heading 2.1</h2>
<p>Donec id elit non mi porta gravida at eget metus. Fusce dapibus, tellus ac cursus commodo, tortor mauris condimentum nibh, ut fermentum massa justo sit amet risus. Etiam porta sem malesuada magna mollis euismod. Donec sed odio dui. </p>
<p><a class="btn btn-default" href="#">View details &raquo;</a></p>
</div>
</section>
<section class="col-lg-3 col-xs-6">
<div style="background-color:#DDBBFF" class="heading">
<h2>Heading 2.2</h2>
<p>Donec id elit non mi porta gravida at eget metus. Fusce dapibus, tellus ac cursus commodo, tortor mauris condimentum nibh, ut fermentum massa justo sit amet risus. Etiam porta sem malesuada magna mollis euismod. Donec sed odio dui. </p>
<p><a class="btn btn-default" href="#">View details &raquo;</a></p>
</div>
</section>
<section class="col-lg-6 col-xs-12">
<div style="background-color:#CDE9FF" class="heading">
<h2>Heading 2.3</h2>
<p>Donec sed odio dui. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Vestibulum id ligula porta felis euismod semper. Fusce dapibus, tellus ac cursus commodo, tortor mauris condimentum nibh, ut fermentum massa justo sit amet risus.</p>
<p><a class="btn btn-default" href="#">View details &raquo;</a></p>
</div>
</section>
</section>

Screenshot simulating an xs screen size :

Thanks,

Yann scheydeker
Issue 1:
If you go to preferences, open the Install page, enter something into the search form, then a list of packages will show up. Their titles will be styled as links, but clicking on the titles of uninstalled packages does nothing. (I'd expect it to go to a page about that package, or at least open the package's page on atom.io in a browser window.) Clicking the title of an installed package brings you to an atom page for the package that gives you more info about the package.

Atom 0.170.0 on OS X

Issue 2:
From @gfarrell on January 9, 2015 12:14

When trying to find out more about a package, in the Install view of the Settings page in Atom 0.169.0, clicking the title does nothing, but clicking the author opens the author page in a browser.

Copied from original issue: atom/atom#4947
Issue 1:
While trying to play a large sized gif (11mb) on Android 6 it plays very slowly, even if the gif is inside the app and not fetched from the network.

Smaller gifs play well, so I assume this is related to memory limit, is there anything that can be done to work around this?

I already tried the override down to 50x50, still plays extremely slow.

Issue 2:
Here is a screen capture of two gifs playing w/ Glide 3.7:

Here is a screen capture of the same two gifs playing w/ Glide 4.2:

GlideApp.with(context)
.load(url)
.diskCacheStrategy(DiskCacheStrategy.ALL)
.into(view);

This happens with any gif that I've tried, here's an example:

https://media.giphy.com/media/3ohjV3cQ9lvPeCVLOg/giphy.gif

Glide Version: 4.2.0

Integration libraries: None

Device/Android Version: Nexus 5, OnePlus One, Pixel
Issue 1:
I'm submitting a ... (check one with "x")

[ x ] bug report
[ ] 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 executing "webpack -p" against existing project w/o any changes other than upgrading the version number from rc.4 -> rc.5 (aka, not converting code to use NgModule), child components do not get rendered.

"webpack -p" works when the version is rc.4 and also works with rc.5 with "webpack -d"

Expected/desired behavior

Expected for the minified code via "webpack -p" would render all components like it does with rc.4

Angular version 2.0.0-rc.5

Browser latest Chrome

Language TypeScript 1.8.7 | ES6; generated from VS 2015

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

[x] bug report
[ ] 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

Minified bundle breaks, but SOLVED temporarily by either:

turning mangle off (change the option here)

re-order your components/pipes/directives declarations in NgModule

Use AOT compilation: ngc, or a.k.a @angular/compiler-cli (Update from @IgorMinar ) -> most recommended

Error traces:

lib-2cf12bf509.js:7 Unhandled Promise rejection: Template parse errors:
Can't bind to 'brand' since it isn't a known property of 'as-navbar'.
1. If 'as-navbar' is an Angular component and it has 'brand' input, then verify that it is part of this module.
2. If 'as-navbar' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
("<as-navbar [ERROR ->][brand]="appBrand"></as-navbar>
<div class="container" style="margin-top: 100px;">
<router-outlet></"): a@0:11 ; Zone: <root> ; Task: Promise.then ; Value:

Expected/desired behavior

The minified bundle should work as in RC4

Reproduction of the problem

https://github.com/OasisDigital/rc5-declaration-order

npm install

// try run in dev, it works well now
npm start

// try run in prod, the bundle created but break
npm run serve-build

// now try changing the mangle option and retry, it works!

What is the expected behavior?

Should work as in RC4

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.0-rc.5

Browser: [all | Chrome 52 | Web Browser

Language: [all | TypeScript 1.8.10]
Issue 1:
This doesn't seem right:

julia> [1][begin:end]
1-element Vector{Int64}:
1

julia> @less [1][begin:end]
ERROR: UndefVarError: begin not defined
Stacktrace:
[1] top-level scope
@ REPL[16]:1

Julia 1.6.1

Issue 2:
This would be heavily breaking, so definitely not a 1.x thing, but it has come up (I can't recall where but perhaps @JeffBezanson can link) that comparing unrelated objects with == can hide bugs in situations where it doesn't make sense to compare two objects. In static languages, this will typically be a type error, whereas dynamic languages have traditionally been quite liberal with what can be compared for equality since it's often useful to be able to check whether two objects are the same object, for example, or to have heterogenous collections like dicts where equality is used to compare very different kinds of objects sometimes. The best practice in Julia for such situations, however, is to use === for comparing object identity when you want the strict comparison and isequal to compare objects in collections where you need an intuitive equivalence relation. That actually leaves us in the position to remove the x == y fallback that calls x === y and make == fail unless there's an explicit method for the comparison. Any case where x == y was previously being used to compare disparate objects would then have to changed to using === or isequal as appropriate.
Issue 1:
We've had quite a few issues crop up about how to define types of outputs given inputs. My view is that this is revealing limitations in the promotion system. A proposal to deal with this might be to define arithmetic on types.

For example, here would be some rules:

Int*Int == Int
Int+Int == Int
Meter{Float64}+Meter{Float64} == Meter{Float64}
Meter{Float64}*Meter{Float64} == Meter{Float64}^2
Meter{Float64}/Meter{Float64} == Float64
Matrix{Int}+Matrix{Float64} == Matrix{Float64}

and so on.

Issue 2:
3^(-5) gives a Float64 of value 0.004115226337448558

while

@code_llvm ^(3, -5) emits the following llvm code

; @ intfuncs.jl:221 within `^'
define i64 @"julia_^_11097"(i64, i64) {
top:
%2 = call i64 @julia_power_by_squaring_990(i64 %0, i64 %1)
ret i64 %2
}

which indicates that the function has an integer return type.

The output of versioninfo() is as follows-

Julia Version 1.2.0
Commit c6da87ff4b (2019-08-20 00:03 UTC)
Platform Info:
OS: macOS (x86_64-apple-darwin18.6.0)
CPU: Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.1 (ORCJIT, broadwell)
Environment:
JULIA_EDITOR = atom -a
JULIA_NUM_THREADS = 2
Issue 1:
I created a custom JSON encoder class extended from flask.json.JSONEncoder but it is not called when calling flask.jsonify. Additionally, I removed my custom JSON encoder and confirmed that flask.json.JSONEncoder isn't called either via a break statement in Pycharm.

from flask import Flask
from flask import jsonify
from flask.json import JSONEncoder

class MyEncoder(JSONEncoder):
def default(self, obj):
if hasattr(obj, '__json__'):
return obj.__json__()
else:
try:
iterable = iter(obj)
except TypeError:
pass
else:
return list(iterable)

return JSONEncoder.default(self, obj)

class MyClass(object):
key = 'a'
value = 'b'

def __json__(self):
return {'key': self.key, 'value': self.value}

app = Flask(__name__)
app.json_encoder = MyEncoder

@app.route('/')
def hello_world():
return jsonify(MyClass())

if __name__ == '__main__':
app.run(debug=True)

Issue 2:
ECMAscript 5 changed behavior of Array literals. That part of the documentation is outdated by now. We should check what browsers are affected by this and update the docs accordingly.
Issue 1:
Environment

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

Steps to reproduce

echo -e '\e[4m underlined \e[33m yellow \e[39m should still be underlined \e[m'

Expected behavior

The entire line should be underlined.

Actual behavior

The "should still be underlined" bits aren't underlined.

Note that SGR codes 22, 27, 39 and 49 seem to cause this effect, but only if they're predeced by a 1, 7, 30-37 or 40-47, resp., that is, only if they do actually turn off some other attribute.

Also note that if the "should still be underlined" text is made longer so that it overflows to the next line (or even multiple new lines), it's underlined in the last one of these lines. This makes it perhaps a reincarnation of #47.

Furthermore, changing the window width and thus causing a reflow of the text removes the underlining from the last line.

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.356]
Windows Terminal version (if applicable): 0.5.2681.0

# Steps to reproduce

Try to select, copy and paste with the normal windows shortcuts for these operations.

# Expected behavior

I can select, copy and paste text with these shortcuts just like in the old console

# Actual behavior

The operations do not work
Issue 1:
A very useful feature of Powershell terminal is being able to get all commands that start with a particular string just writing the initial letters and clicking Ctrl-Space... that give us a bunch of similar commands to select from. That feature seems missing in new Windows Terminal.

Example: typing ConvertTo

Issue 2:
Environment

Windows build number: 10.0.18990.1
Windows Terminal version 0.5.2681.0
Windows Snip & Sketch

Steps to reproduce

When I open a Terminal window, and start writing some commands, some lines doesn't show properly and are truncated. I think the problem might be my current Windows resolution, which I set on 125%

Expected behavior

The most weird thing is that when taking a screenshot with the Windows Tool, everything appears normal on the screenshot like above.

Actual behavior

Here's below what I really see on my screen (when taking a photo of it). For eg., first line is truncated.

Sorry for the image Github doesn't want to turn it anyway but clicking on it shows the photo correctly :)
Issue 1:
$ godep restore
can't load package: package github.com/influxdb/influxdb/client: code in directory /home/decarr/code/kubernetes/src/github.com/influxdb/influxdb/client expects import "github.com/influxdata/influxdb/client"
godep: restore: exit status 1
can't load package: package github.com/influxdb/influxdb/influxql: code in directory /home/decarr/code/kubernetes/src/github.com/influxdb/influxdb/influxql expects import "github.com/influxdata/influxdb/influxql"
godep: restore: exit status 1
package github.com/influxdb/influxdb/meta: cannot find package "github.com/influxdb/influxdb/meta" in any of:
/usr/lib/golang/src/github.com/influxdb/influxdb/meta (from $GOROOT)
/home/decarr/code/kubernetes/src/github.com/influxdb/influxdb/meta (from $GOPATH)
godep: restore: exit status 1
package github.com/influxdb/influxdb/snapshot: cannot find package "github.com/influxdb/influxdb/snapshot" in any of:
/usr/lib/golang/src/github.com/influxdb/influxdb/snapshot (from $GOROOT)
/home/decarr/code/kubernetes/src/github.com/influxdb/influxdb/snapshot (from $GOPATH)
godep: restore: exit status 1
can't load package: package github.com/influxdb/influxdb/toml: code in directory /home/decarr/code/kubernetes/src/github.com/influxdb/influxdb/toml expects import "github.com/influxdata/influxdb/toml"
godep: restore: exit status 1
can't load package: package github.com/influxdb/influxdb/tsdb: code in directory /home/decarr/code/kubernetes/src/github.com/influxdb/influxdb/tsdb expects import "github.com/influxdata/influxdb/tsdb"
godep: restore: exit status 1

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No.

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

documentation title

docs title

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Kubernetes version (use kubectl version): N/A

This is about docs on kubernetes.io.

What happened: Searched for "kubernetes readiness probe" on google, noticed title of first result was "Kubernetes - Persistent Storage", but clicked on it anyway since there was a fitting subheading with relevant-seeming info, as well as a potentially-matching URL: http://kubernetes.io/docs/user-guide/production-pods/

What you expected to happen: That that particular docs page would be titled something like "Production Pods" or "Working with containers in production" (its link name in the menu on the left).

How to reproduce it (as minimally and precisely as possible): (see above)

Anything else do we need to know:

I would gladly send a PR to fix the issue, if someone kindly pointed me towards where such a change may be done. I'm assuming there's some kind of config file or text file from which the menu item titles are drawn, which could be used to fix this. Not sure if there's a more appropriate way than to use those titles as both page title and auto-generating an initial heading.
Issue 1:
I'm submitting a Improvement for documents

[ ] bug report
[x] feature request
[x] improvement request
[ ] support request

Current behavior

For example, in HostListener doc, there is no detailed descriptions for eventName.

In common that should be dom event names, but actually we could use it some way like document:click/keyup.esc etc.

Expected behavior

I think it should be a more clear doc for any details even that advanced usage,

e.g. how can we use that eventName in HostListener decorator.

Angular is moving fast, any details should be checkable for developers.

Thx.

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

[x] bug report
[ ] feature request
[ ] support request

Current behavior

Generating a correct URL from a route containing an auxiliary route seems to be impossible in some cases. For example, in my use case, the correct route would be /Test/(List//details:/Details/1) but the router generates /Test/List(details:Details/1).

Expected behavior

The router should generate the correct route.

Minimal reproduction of the problem with instructions

Here is the plunker: https://plnkr.co/edit/2xo6WFI2JzGbIcAzio04

What is the motivation/use case for changing the behavior?

In my plunker, I want to generate the details below the list in an auxiliary route.

Please tell us about your environment:

Windows/ASP.NET

Angular version: 2.0.X

Angular 2.3

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

all

Language: [all | TypeScript X.X | ES6/7 | ES5]

TS 2.1, ES5
Issue 1:
If I have a form 'A' which has an embedded form 'B' that map an object, and that object has defaults values in the constructor, with the current implementation I lose those defaults values when displaying the 'A' form. Of course this is bad...

Is there a way to fix this?

Issue 2:
It is currently not possible to set default values for a Collection prototype. The default values specified in an entity are not passed to the prototype. However, setting the data option causes the prototype to have the value set.
Issue 1:
The editor.insertSpaces setting can autodetect if it should insert spaces or tabs. Some people like tabs more then spaces, but it's just personal preference.

I think in Code < 0.10 it inserted tabs when the setting was set to auto. In Code >= 0.10 it changed to spaces. I'm more a tab guy, except for json files. So that's why I don't want to set it to false because I would have to change it forth and back when in a JSON file.

The setting should not be reverted, but maybe an extra setting like editor.insertSpacesDefault which can only be set to true and false and has a default of true (to not break the current behaviour). If editor.insertSpaces is set to auto and a new file is created, it will check the editor.insertSpacesDefault setting.

@alexandrudima I guess you are the person for this as you wrote the tests regarding the insertSpaces autodetect :)

Issue 2:
When insertSpaces = auto is set and you create a new file, pressing the tab key will insert spaces rather than a tab character. This is a problematic default because it means there is no easy way to actually get the first tab into the file so the auto can start learning what the file's indentation mechanism is. If you want space indent, you can simply press the space bar a few times to start the learning process. In order to start a new file with tab indentation though you (currently) need to go find another file with a tab in it, copy the tab, and paste it into the new file.

I recommend having the fallback behavior for an empty file be that the space bar inserts spaces and the tab key inserts tabs. This way both camps (spaces and tabs) have the ability to reasonably start new files when in auto-mode.
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

6.9.0

Operating System:

Windows 10

Last Known Working Electron version:

Expected Behavior

The defaultId property in the Options object in dialog.showMessageBox should change the default button.

Actual Behavior

The defaultId property in the Options object in dialog.showMessageBox isn't changing the default button. The rest of the properties work just fine

To Reproduce

dialog.showMessageBox(mainWindow, { type: 'warning', buttons: ['Yes', 'No', 'Cancel'], defaultId: 2, cancelId: 2, detail: "...you want to continue?", message:"You are about to delete the current calendar!" })

Screenshots

Additional Information

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

8.0.0

Operating System:

Windows 10 (18362)

Ubuntu 14.04 x64

Last Known Working Electron version:

Expected Behavior

dialog.showMessageBoxSync(null, { type:'warning', buttons: ['Yes', 'No'], defaultId: 1, cancelId: 1, title: 'Power Control', message: "Warning!", });

I set "defaultId:1", after executing the function,it should focus on the "No" button.

Actual Behavior

Execute the function, in windows 10, it focuses on the "Yes" button. And it focuses on the "No" button in Ubuntu 14.04.

To Reproduce

$ git clone git@github.com:ForJason/electron-smt.git
$ cd electron-smt
$ npm start

Screenshots

Additional Information