WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Marcel Overdijk opened SPR-9221 and commented

It would be nice to add more flexibility to the form:errors tag.

E.g. to render something like

<ul>

<li>error1</li>

<li>error2</li>

<ul>

With element="ul" a part can be implemented but the <li> element is not possible.

The delimiter attribute just outputs it content after eacht error.

Maybe the form:errors tag can be extended with something like errorElement or itemElement indicating a wrapper element for the each error.

Something like this:

<form:errors path="*" element="ul" errorElement="li" />

Affects: 3.1.1

Issue Links:

#8073 Better error handling from the form:errors tag ("duplicates")

Issue 2:
William Shields opened SPR-3390 and commented

form:errors is a pretty crude mechanism for displaying multiple errors. It uses a default delimieter of <br>. It should allow for more sophisticated methods of displaying errors.

In the simple case, I would like to see "schemes" introduced. For example:

<form:errors path="*" scheme="ul"/>

which would craete:

<ul>

<li>error1</li>

<li>error2</li>

</ul>

Note: if there were no errors the enclosing <ul> tag should not be rendered.

Example schemes could be:

table

ul

ol

Potentially this may require another attribute to distinguish between the CSS class given to the enclosing tags and that given to each element, although if the enclosing tag got the value of cssClass, a CSS selector could resolve that problem without adding an attribute.

In the more complicated example, it is possibly worthwhile (although arguably unnecessary if you have sufficient schemes as defined above) to allow either the programmer to write their own schemes or to have sufficient attributes to achieve the same thing.

Example:

<form:scheme name="errorTable">

form:pre

<table>

<tr>

<th>Error #</th>

<th>Error Description</th>

</tr>

</form:pre>

<form:loop var="count">

<tr>

<td><c:out value="${count}"/></td>

<td><form:error/></td>

</tr>

</form:loop>

form:post

</table>

</form:post>

</form:scheme>

The simple example of this kind of thing would be adding attributes:

<form:errors path="*" block="ul" item="li"/>

alternatively have a heading block within:

<form:errors path="*" block="ul" item="li">

<p>The following errors have occurred:</p>

</form:errors>

Anywa, you get the idea.

Affects: 2.0.4

Issue Links:

#13859 Extend form:errors with something like errorElement ("is duplicated by")

20 votes, 14 watchers
Issue 1:
I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x] 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

We can use ChangeDetectionStrategy onPush to set components to checkOnce, but there is no way to set one @Input to checkOnce without changing others.

Expected behavior

Could we add a way to set one @Input to checkOnce without changing others?

Minimal reproduction of the problem with instructions

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

There is no angularjs double colon expression equivalent in current angular version. It will be more convenient for the developer to have this feature in angular.

In a angularjs, when we declare a value such as `{{ ::foo }}` inside the DOM, once this value

becomes defined, Angularjs will render it, unbind it from the watchers and thus reduce the

volume of bindings inside the $digest loop.

Please tell us about your environment:

null

Angular version: 2.0.X

4.1.2

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]

all

Node (for AoT issues): node --version =

7

Issue 2:
Changes to newly created Components with DynamicComponentLoader are not detected.

Angular Version alpha.33

An easy example you can find here:

index.ts

bootstrap(App).then((appRef:ApplicationRef)=>{
var appComp:Promise<App> = appRef.injector.get(App);
appComp.then((app) =>{
app.createLoginView();
});
}).catch((e)=>{console.log(e)});

app.html

<div>
<div #main>{{msg}}</div>
</div>

app.ts

@Component({
selector: 'app',
injectables: [DynamicComponentLoader, Injector, ElementRef]
})
@View({
templateUrl: 'src/component/app/app.html',
styleUrls: ['src/component/app/app.css']
})
export class App {

componentLoader:DynamicComponentLoader;
injector:Injector;
elementRef:ElementRef;
msg:string = "Foo";

constructor(loader:DynamicComponentLoader, injector:Injector, elementRef:ElementRef) {
this.componentLoader = loader;
this.injector = injector;
this.elementRef = elementRef;
}

createLoginView():void {
this.componentLoader.loadIntoLocation(Login, this.elementRef, "main").then(componentRef=> {
this.msg = "Bar";
}).catch(e=>console.log(e));
}
}

The provided "Bar" string is not loaded to the app.html and "Foo" is still displayed (Change was not detected). As soon the first event is triggered by any component, the "Bar" msg will shows up. It seems to be an issue within:

this.componentLoader.loadIntoLocation(Login, this.elementRef, "main").then(componentRef=> {
this.msg = "Bar";
}).catch(e=>console.log(e));

If I call createLoginView() from the App constructor and not from the bootstrap Promise, the app.html displays the correct "Bar" msg.

Is there something I'm doing wrong? Thx
Issue 1:
I'm submitting a...

bug report

Webpack version:

2.1.0-beta.13

Please tell us about your environment:

OSX 10.11.5

Current behavior:

When loaders are defined with -loader (e.g. babel-loader), because the default value of moduleExtensions is -loader, module resolution attempts to find babel-loader-loader, which causes an erroneous npm install with this plugin:

https://github.com/ericclemmons/npm-install-webpack-plugin

Expected/desired behavior:

Expected that that this enforces the -loader extension, so that babel becomes babel-loader. It should noop if /-loader$/ matches.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem along with a gist/jsbin of your webpack configuration.

I believe this is due to these two files:

https://github.com/webpack/enhanced-resolve/blob/d154f01b6f74b90f3ac3c5ea6cca89abead5236c/lib/ResolverFactory.js#L164-L169

https://github.com/webpack/enhanced-resolve/blob/master/lib/ModuleAppendPlugin.js

Issue 2:
http://typescript.codeplex.com/

If this post gets +5 I'll plan to do this...
Issue 1:
System information (version)

OpenCV => ❔

Operating System / Platform => ❔

Compiler => ❔

Detailed description

Steps to reproduce

Issue 2:
System information (version)

OpenCV => 3.4.2 or higher

Operating System / Platform => Linux 64

Compiler => Unbatu 16.04 gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf -> arm-linux-gnueabihf-g++

Detailed description

I found that in the same environment configuration, cross-compilation after installing ffmpeg-4.1, OpenCV 3.4.2 or later can not use FFMPEG library (but OpenCV 3.2.0 can)

In cmake3.5.1

OpenCV 3.2.0 can recognize FFMPEG:

Video I/O:

DC1394 1.x: NO

DC1394 2.x: NO

FFMPEG: YES

avcodec: YES (ver 56.60.100)

avformat: YES (ver 56.40.101)

avutil: YES (ver 54.31.100)

swscale: YES (ver 3.1.101)

avresample: NO

However, OpenCV 3.4.2 does not recognize FFMPEG:

Video I/O:

DC1394: NO

FFMPEG: NO

avcodec: NO

avformat: NO

avutil: NO

swscale: NO

avresample: NO

GStreamer: NO

libv4l/libv4l2: NO

v4l/v4l2: linux/videodev2.h

gPhoto2: NO

I carefully compared the code they identified in the FFMPEG module and found that OpenCV 3.4.2 is impossible to use FFMPEG：（OpenCVFindLibsVideo.cmake）

Look at this variable carefully

${FFMPEG_INCLUDE_DIRS}

in OpenCV 3.2.0 Can find configuration

but in in OpenCV 3.4.2 Can not find configuration

OpenCV 3.2.0 is very useful, but it is difficult to use on OpenCV 3.4.x version! I am constantly changing the FFMPEG version and running out of various configurations, but the OpenCV 3.4.x version does not correctly recognize FFMPEG. I don't know what caused this recognition process to be so complicated. Why is it so difficult to use OpenCV 3.4.x???

Steps to reproduce
Issue 1:
le is a point-wise math operator so porting it from the TH code to Aten (and TensorIterator) expected to be easy. Such migration will help to clean up the code, simplify dispatch as well as provide immediate 2-3x operator performance gain.

Porting guide: https://github.com/pytorch/pytorch/wiki/TH-to-ATen-porting-guide

Example PR with porting of the adaptive_avg_pool2d: #14714

How to use TensorIterator: https://github.com/pytorch/pytorch/wiki/How-to-use-TensorIterator

Issue 2:
Porting TH operators is essential for code simplicity and performance reasons.

Porting guides and Q&A are available in umbrella issue: #24507

Feel free to add @VitalyFedyunin as a reviewer to get a prioritized review.
Issue 1:
in the new version of the Glide 4.3 i'm trying to use it but it crash whenver i use it and whatever context i passed to it

this is the error showed to me

java.lang.AbstractMethodError: abstract method "void com.bumptech.glide.module.RegistersComponents.registerComponents(android.content.Context, com.bumptech.glide.Glide, com.bumptech.glide.Registry)"

this is my code i tired

Glide.with(getApplicationContext()).
load(url)
.into(imageView);

and

Glide.with(getContext()).
load(url)
.into(imageView);

and it give me that warning

W/Glide: Failed to find GeneratedAppGlideModule. You should include an annotationProcessor compile dependency on com.github.bumptech.glide:compiler in your application and a @GlideModule annotated AppGlideModule implementation or LibraryGlideModules will be silently ignored

and the code in lib in gradle

compile 'com.github.bumptech.glide:glide:4.3.1'
annotationProcessor 'com.github.bumptech.glide:compiler:4.3.1'

i posted it into stackoverflow also

Issue 2:
Glide Version: 4.0.0-RC0

Integration libraries: okhttp3-integration

In my gradle:

compile 'com.github.bumptech.glide:glide:4.0.0-RC0'
annotationProcessor 'com.github.bumptech.glide:compiler:4.0.0-RC0'
compile ('com.github.bumptech.glide:okhttp3-integration:1.5.0@aar'){
exclude group: 'glide-parent'
}

My new Glide configuration:

@GlideModule
public class GlideConfiguration extends AppGlideModule {
@Override
public void applyOptions(Context context, GlideBuilder builder) {
// Apply options to the builder here.
RequestOptions requestOptions = new RequestOptions();
requestOptions.format(DecodeFormat.PREFER_ARGB_8888);
builder.setDefaultRequestOptions(requestOptions);
}

@Override
public void registerComponents(Context context, Registry registry) {
final OkHttpClient.Builder builder = RestCoreRetrofit.getInitialOkHttpClientBuilder();
registry.append(GlideUrl.class, InputStream.class, new OkHttpUrlLoader.Factory(builder.build()));
}
}

For information getInitialOkHttpClientBuilder():

public static OkHttpClient.Builder getInitialOkHttpClientBuilder() {
OkHttpClient.Builder httpClient = new OkHttpClient.Builder();

// Setup timeouts
httpClient.connectTimeout(20, TimeUnit.SECONDS);
httpClient.readTimeout(60, TimeUnit.SECONDS);
httpClient.writeTimeout(60, TimeUnit.SECONDS);

return httpClient;
}

So, I've migrated v3 to v4 (http://bumptech.github.io/glide/doc/migrating.html). Migration and build are successful, but when I start my App, I have this crash now directly from the first GlideApp calling:

In my fragment:

GlideApp.with(this)
.load(resourceId)
.into(mBgImageView);

java.lang.AbstractMethodError: abstract method "void com.bumptech.glide.module.RegistersComponents.registerComponents(android.content.Context, com.bumptech.glide.Registry)"

at com.bumptech.glide.Glide.initGlide(Glide.java:217)

at com.bumptech.glide.Glide.get(Glide.java:154)

at com.bumptech.glide.Glide.getRetriever(Glide.java:513)

at com.bumptech.glide.Glide.with(Glide.java:585)

at com.myapp.util.GlideApp.with(GlideApp.java:92)

I can't understand why. I checked several times the documentation.

Thank you very much for your support guys!
Issue 1:
Description of the problem

Currently when we want to change things inside a GLTF, for instance making meshes drop shadows, material props, etc, we have to do messy deep traversals.

GLTF loader already returns scenes, cameras and assets, but looking though the source it still knows about nodes and materials internally. If this could be exposed it would be very efficient for us to make changes:

new GLTFLoader().load(url, gltf => {
gltf.materials["base"].roughness = 0.5
gltf.nodes["plane"].castShadow = true
})

i have made a tool for gltf-jsx exports that does something similar, and i've started implementing the above variant in a test, it looks like this now:

would it be possible to add these two collections officially to the gltf result?

Issue 2:
Description of the problem

I have a FBX model with several animations and for some reason each animation got a delay, like they are placed one after another (notice a duration here):

I tried converting it with fbx2gltf, didn't succeeded to actually render it yet but at least timings look fine:

Here's the model (pass: fbxbug):

female.zip

And here's how one of animations looks like compared with Autodesk FBX Review:

Screen Recording 2019-09-19 at 19.44.06.zip

Three.js version

Dev

r108

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)
Issue 1:
When I switch tasks Atom -> other program -> Atom my cursor is hidden, so I don't know where I'm typing. When I start typing and press backspace I'll see the cursor again.

Atom 0.153.0.de619a7 (git)

Linux

Issue 2:
I'm on Ubuntu 14.04 and every time I alt+tab or make Atom lose focus in any way, the cursor position disappears. I have to click on the window to make it reappear.
Issue 1:
I'm getting the error: "Error plug in failed to initialize // Testing Challenge "

var Car = function() {
//Change this constructor
this.wheels = wheels;
this.seats = seats;
this.engines = engines;
};

//Try it out here
var myCar = new Car(3,2,1);

// Only change code above this line

(function() {return JSON.stringify(myCar);})();

Issue 2:
Can't run code because of this error error: plugin failed to initialize it is showing in the lower left corner. Tried different browsers, computer, and devices same error. Have a really slow internet connection
Issue 1:
It appears that the unit tests in e2e are sometimes failing due to a 60 minute timeout, but it does not appear to be being correctly applied.

Logs here:

https://console.developers.google.com/storage/browser/kubernetes-jenkins/pr-logs/0586d866de1b0ca888ad3de53ad41cdb2077dd0e/kubernetes-pull-test-unit-integration/10243/

The weird thing is that the logs show that the unit tests themselves only took the normal amount of time - ten minutes or so (14:38 - 14:50 in the logs). But I'm guessing there is an invisible delay before the first timestamp or after the last timestamp (or the 60 minute limit is not being correctly applied).

The wall clock time in between my request to retest and the failure result being posted was a little more than an hour (I think), so I think there is a silent delay somewhere.

Issue 2:
I'm not sure what happened, but our unit/integration tests started timing out recently (I mean build is timing out).

I1221 17:31:43.944771 4488 genericapiserver.go:303] Node port range unspecified. Defaulting to 30000-32767.
Build timed out (after 45 minutes). Marking the build as aborted.
Build timed out (after 45 minutes). Marking the build as failed.
FATAL: Unable to delete script file /tmp/hudson8166020313250965666.sh

An example failure:

https://pantheon.corp.google.com/storage/browser/kubernetes-jenkins/pr-logs/173718059d925d29c746b832c739058f10bbd1d6/kubernetes-pull-test-unit-integration/6967/?debugUI=DEVELOPERS

@kubernetes/goog-testing @ixdy @spxtr
Issue 1:
Challenge http://beta.freecodecamp.com/challenges/waypoint-use-a-css-class-to-style-an-element has an issue.

Solving this bonfire and attempting to move on produces a 502 Bad Gateway error.

Issue 2:
Challenge http://beta.freecodecamp.com/challenges/waypoint-use-a-css-class-to-style-an-element won't move on to next Waypoint. After changing the code as indicated and clicking the "Go to my next challenge" button, it goes to a 502 Bad Gateway page instead of going to the next Waypoint.

The Waypoint (Waypoint 10) is checked off on the map though, so it does know that the challenge has been completed, but it doesn't link to the next challenge.
Issue 1:
these classes cannot be found in the RC1 css file at http://netdna.bootstrapcdn.com/bootstrap/3.0.0-rc1/css/bootstrap.min.css

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:
Florent Ramiere opened SPR-6902 and commented

When this method is executed

@ExceptionHandler
@ResponseBody
public String dummyExceptionHandler(Exception e) {
return e.getMessage();
}

Spring mvc tries to resolve the view using the method output --> 404.

As the method is annotated with @ResponseBody, it should directly write the method output to the response.

Affects: 3.0.1

Attachments:

spr-6902.zip (32.61 kB)

Issue Links:

#11850 AnnotationMethodHandlerAdapter and AnnotationMethodHandlerExceptionResolver should supports MappingJacksonHttpMessageConverter by default ("is duplicated by")

#12476 Add support for @Request-/@ResponseBody to @ExceptionHandler methods ("is duplicated by")

#11626 @ResponseStatus does not work with @ExceptionHandler

Referenced from: commits 157623b, 7f8c91a

0 votes, 8 watchers

Issue 2:
Yaozong Zhu opened SPR-4759 and commented

I am trying to integrate my tests into Spring 2.5 availing of TestContext annotations. But I met a support issue. The followings are relevant codes:

@RunWith(SpringJUnit4ClassRunner.class)

@TestExecutionListeners(value = {

DependencyInjectionTestExecutionListener.class,

DirtiesContextTestExecutionListener.class,

TransactionalTestExecutionListener.class

})

@ContextConfiguration(locations = {

"classpath:/applicationContext-resources.xml",

"classpath*:/applicationContext.xml"

}, inheritLocations = true)

@TransactionConfiguration(transactionManager = "transactionManager", defaultRollback = true)

@Transactional

public abstract class BaseTestCase extends AbstractJUnit4SpringContextTests {...}

@ContextConfiguration(locations = {

"classpath:/applicationContext-jmx.xml",

"/WEB-INF/applicationContext*.xml",

"/WEB-INF/dispatcher-servlet.xml"

}, inheritLocations = true)

public abstract class BaseWebControllerTestCase extends BaseTestCase{...}

public class UserFormControllerTest extends BaseWebControllerTestCase{

@Autowired

private UserFormController c = null;

@Test

...

}

java.lang.IllegalStateException: WebApplicationObjectSupport instance [xxx.UserFormController@123961b] does not run in a WebApplicationContext but in: org.springframework.context.support.GenericApplicationContext@1fc2fb: display name [org.springframework.context.support.GenericApplicationContext@1fc2fb]; startup date [Mon Apr 28 15:35:37 BST 2008]; root of context hierarchy

at org.springframework.web.context.support.WebApplicationObjectSupport.getWebApplicationContext(WebApplicationObjectSupport.java:101)

at org.springframework.web.context.support.WebApplicationObjectSupport.getServletContext(WebApplicationObjectSupport.java:115)

...

Affects: 2.5.2

Issue Links:

#9917 Support loading WebApplicationContexts with the TestContext Framework ("duplicates")

1 votes, 1 watchers
Issue 1:
System information

MacOS High Sierra 10.13.2:

Python 3.6.3:

TensorFlow Latest Pull from 1/17/18:

Describe the problem

I am following Pete Warden's TensorFlow for Mobile Poets guide and seem to have a found an error. When I run "tensorflow/contrib/makefile/build_all_ios.sh" after about 20 minutes it returns an error.

I have tried running lipo -info /Users/ryan/Downloads/tensorflow2/tensorflow/contrib/makefile/gen/protobuf_ios/lib/libprotobuf.a

and this returns:

Architectures in the fat file:

/Users/ryan/Downloads/tensorflow2/tensorflow/contrib/makefile/gen/protobuf_ios/lib/libprotobuf.a are: i386

I have the entire error script here:

https://drive.google.com/file/d/1JovTMGBJKbqzRPBzXy3cIQ-hbz76n0ab/view?usp=sharing

Source code / logs

ld: symbol(s) not found for architecture x86_64

clang: error: linker command failed with exit code 1 (use -v to see

invocation)

make: *** [/Users/ryan/Desktop/tensorflow-

master/tensorflow/contrib/makefile/gen/bin/ios_X86_64/benchmark] Error 1

'[' 2 -ne 0 ']'

echo 'x86_64 compilation failed.'

x86_64 compilation failed.

exit 1

Issue 2:
I try to build tensorflow support at Android and iOS by makefile tutorial in current master branch 04c318b

When running the build_all_ios.sh script, the below error message show

Undefined symbols for architecture x86_64:
"nsync::nsync_mu_init(nsync::nsync_mu_s_*)", referenced from:
tensorflow::mutex::mutex() in env.o
tensorflow::mutex::mutex() in random.o
"nsync::nsync_mu_lock(nsync::nsync_mu_s_*)", referenced from:
tensorflow::mutex::lock() in env.o
tensorflow::mutex::lock() in random.o
tensorflow::mutex::lock() in histogram.o
"nsync::nsync_mu_unlock(nsync::nsync_mu_s_*)", referenced from:
tensorflow::mutex::unlock() in env.o
tensorflow::mutex::unlock() in random.o
tensorflow::mutex::unlock() in histogram.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/Users/CSL.Peter/tensorflow/tensorflow/tensorflow/contrib/makefile/gen/host_bin/proto_text] Error 1
+ '[' 2 -ne 0 ']'
+ echo 'armv7 compilation failed.'
armv7 compilation failed.
+ exit 1

The download_dependencies.sh and compile_ios_protobuf.sh run successfully but compile_ios_tensorflow.sh failed. I find same issues #3191 and #4252 and seem to be fixed at #4287, but this problem still happen.
Issue 1:
It seems like the parser tries to read the type where it isn't:

fn main() {
let a : u32 = 0;
let b : usize = 0;

a as usize > b; // ok
a as usize < b; // error: expected one of `(`, `+`, `,`, `::`, `<`, or `>`, found `;`
}

I think it's rather strange that the operator > works, but the operator < doesn't at the same place.

rustc 1.0.0-nightly (522d09dfe 2015-02-19) (built 2015-02-20)

Issue 2:
lib.rs:11:21: 11:23 error: expected type, found token LIT_INT_UNSUFFIXED(16i64)
lib.rs:11 if foo as int < 16 {}

The solution is of course to parenthesize the cast so it doesn't get parsed as generics, but the error message does not help at all.