benebsiny
benebsiny
@NotMyFault The FormValidation can only shows the error message at most, just like some input fields in the Configure System page. In my opinion, if a user change the update...
I've followed the suggestion to make some modifications.
@basil Thanks for reminding me. After verifying using `RunLoadCounter`, I found that the method that searches build is flawed. If builds aren't put in the result list when iterating them,...
After trying `Spliterator`, I found that the result is the same as the [above I mention](https://github.com/jenkinsci/jenkins/pull/5597#issuecomment-1138529211). If I limit the number in advance and then search, some builds which are...
@basil I've made some changes, have a look at it please.
I've followed @Ehesp to change the `next.config.js` and `index.js`, and now it shows the error message... ``` ./node_modules/monaco-editor/esm/vs/base/browser/ui/codiconLabel/codicon/codicon.css ModuleParseError: Module parse failed: Unexpected character '' (1:0) You may need an...
> Thanks for clarifying @daniel-beck. @benebsiny Can you please perform the testing @daniel-beck has requested and update the testing section of PR description? Yes, I'll try it.
@basil Not yet. That's a great idea. I'll try it.
@basil Testcase added.
@daniel-beck I am unable to reproduce the [JENKINS-69487](https://issues.jenkins.io/browse/JENKINS-69487), but I though this PR could solve the problem you described in the `Notes` section