On Fri, 4 Sep 2026 15:57:23 GMT, Alan Bateman <[email protected]> wrote:
>> Hi @AlanBateman. >> No, I’m not the submitter — I found the bug on JBS while looking for a small >> core-libs fix. I haven’t seen this in real code; the issue reads like a >> differential-testing/fuzzer finding, not a production failure. >> >> I’ll update the PR to align with IllegalServiceTypes2. > >> No, I’m not the submitter — I found the bug on JBS while looking for a small >> core-libs fix. I haven’t seen this in real code; the issue reads like a >> differential-testing/fuzzer finding, not a production failure. >> >> I’ll update the PR to align with IllegalServiceTypes2. > > When a JBS issue is assigned then it's usually best to check with the > assignee first. In this case, we had 3 options, some prototype changes, but > low priority to work on. The IllegalServiceTypes2 is currently the > frontrunner, all options requires spec updates. > > Maybe the simplest for you would be to close this PR and find another issue > to work on? @AlanBateman Thanks for the feedback — that makes sense. I wasn’t aware the issue was already being worked on with IllegalServiceTypes2 as the frontrunner. I’ll close this PR and look for another issue to contribute on. ------------- PR Comment: https://git.openjdk.org/jdk/pull/32515#issuecomment-5543814548
