}

    // Test with network errors
    @Test
    void testResolveSids_NetworkError() throws CIFSException {
        doThrow(new CIFSException("Network error occurred")).when(sidResolver)
                .resolveSids(any(CIFSContext.class), anyString(), any(SID[].class));

        assertThrows(CIFSException.class, () -> sidResolver.resolveSids(mockContext, testServerName, testSids));

      // do not retry.
      if (e.cause is CertificateException) {
        return false
      }
    }
    if (e is SSLPeerUnverifiedException) {
      // e.g. a certificate pinning error.
      return false
    }
    // An example of one we might want to retry with a different route is a problem connecting to a
    // proxy and would manifest as a standard IOException. Unless it is one we know we should not

    }

    protected void handleFileUploadException(final FileUploadException e) throws ServletException {
        // suppress logging because it can be caught by logging filter
        //log.error("Failed to parse multipart request", e);
        throw new ServletException("Failed to upload the file.", e);
    }

    // ===================================================================================

            }
            throw new InterruptedRuntimeException(e);
        } catch (final Exception e) {
            if (logger.isDebugEnabled()) {
                logger.debug("Command execution failed for user: username={}, error={}", username, e.getMessage(), e);
            }
            throw new CommandExecutionException("Process terminated for user: " + username, e);
        } finally {
            if (mt != null) {

                            pomArtifact.getVersion()));
                }

                ModelBuildingResult modelResult = modelBuilder.build(modelRequest);
                // ModelBuildingEx is thrown only on FATAL and ERROR severities, but we still can have WARNs
                // that may lead to unexpected build failure, log them
                if (!modelResult.getProblems().isEmpty()) {

This was changed in version 0.110.0 to fix unhandled memory consumption from forwarded exceptions without a handler (internal server errors), and to make it consistent with the behavior of regular Python code.

    /** The key of the message: Error Count */
    public static final String LABELS_ERROR_COUNT = "{labels.errorCount}";

    /** The key of the message: Error Log */
    public static final String LABELS_ERROR_LOG = "{labels.errorLog}";

    /** The key of the message: Error Name */
    public static final String LABELS_ERROR_NAME = "{labels.errorName}";

            // Given
            byte[] buffer = new byte[100];
            when(mockAllocInfo.decode(any(byte[].class), anyInt(), anyInt()))
                    .thenThrow(new jcifs.internal.SMBProtocolDecodingException("Test error"));

            // When & Then
            assertThrows(jcifs.internal.SMBProtocolDecodingException.class, () -> mockAllocInfo.decode(buffer, 0, buffer.length));

/**
 * Logs execution events to logger, eventually user-supplied.
 *
 */
@Deprecated
public class ExecutionEventLogger extends AbstractExecutionListener {
    private static final int MAX_LOG_PREFIX_SIZE = 8; // "[ERROR] "
    private static final int PROJECT_STATUS_SUFFIX_SIZE = 20; // "SUCCESS [  0.000 s]"
    private static final int MIN_TERMINAL_WIDTH = 60;
    private static final int DEFAULT_TERMINAL_WIDTH = 80;

<setting id="org.eclipse.jdt.core.formatter.never_indent_line_comments_on_first_column" value="false"/>
<setting id="org.eclipse.jdt.core.compiler.problem.enumIdentifier" value="error"/>
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_and_in_type_parameter" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_for_inits" value="insert"/>