ACD - Added jline acceptable security exception#49
Conversation
|
build now |
…ating a system terminal which falls back to a dumb one
|
build now |
|
Internal build has been started. Your results will be available at completion. See build progress in legacy Jenkins UI or in Blue Ocean UI. |
|
Build failure. See the job results in legacy Jenkins UI or in Blue Ocean UI. |
|
build now, |
|
Internal build has been started. Your results will be available at completion. See build progress in legacy Jenkins UI or in Blue Ocean UI. |
|
Build success! See the job results in legacy Jenkins UI or in Blue Ocean UI. |
| java\.io\.FilePermission ".*somaxconn", "read" | ||
| io\.netty\.util\.NetUtil\$.*:267 | ||
|
|
||
| # At startup time, Karaf tries to create a system terminal and will fall back to a dumb one of it c |
| java\.io\.FilePermission ".*somaxconn", "read" | ||
| io\.netty\.util\.NetUtil\$.*:267 | ||
|
|
||
| # At startup time, Karaf tries to create a system terminal and will fall back to a dumb one of it c |
There was a problem hiding this comment.
In this context, what is the difference between a system terminal and a dumb [terminal]? Is a system terminal have rich text (colors, bolding, and so one) while a dumb terminal has no character formatting?
There was a problem hiding this comment.
Good question. I don 't really know. I just know all our itests have always fallback to dumb terminal. But in this case, it ain't a security failure since the code is designed to handle this type of security exception.
There was a problem hiding this comment.
But what is dumb terminal? That's what I'd like to know.
There was a problem hiding this comment.
? This is what Karaf calls it ...
|
build now |
|
Internal build has been started. Your results will be available at completion. See build progress in legacy Jenkins UI or in Blue Ocean UI. |
|
Build success! See the job results in legacy Jenkins UI or in Blue Ocean UI. |
| java\.io\.FilePermission ".*somaxconn", "read" | ||
| io\.netty\.util\.NetUtil\$.*:267 | ||
|
|
||
| # At startup time, Karaf tries to create a system terminal and will fall back to a dumb one of it |
There was a problem hiding this comment.
There one type. The word "of" should be "if", here:
expected: "dumb one it it"
actual: "dumb one of it"
|
build now |
|
Internal build has been started. Your results will be available at completion. See build progress in legacy Jenkins UI or in Blue Ocean UI. |
|
Build success! See the job results in legacy Jenkins UI or in Blue Ocean UI. |
4 participants
Description of the Change
Added jline acceptable security exception to handle failure creating a system terminal which falls back to a dumb one.
Alternate Designs
None
Benefits
All DDF itests are reporting this failure which is an acceptable one. This will make the debugger report it as an acceptable one from now on.
Possible Drawbacks
None
Verification Process
Run DDF itests with this new debugger and see it reported as acceptable.
Applicable Issues
Fixes: #___