#          allow-empty-results: true
      # Upload additional logs
      - google-cloud-storage:
          credentials-id: 'elasticsearch-ci-gcs-plugin'
          uploads:
            - classic:
                file-pattern: 'build/*.tar.bz2'
                storage-location: 'gs://elasticsearch-ci-artifacts/jobs/$JOB_NAME'
                share-publicly: false
                upload-for-failed-jobs: true
                show-inline: true

 * override one or more methods to modify the behavior of the backing multimap as desired per the <a
 * href="http://en.wikipedia.org/wiki/Decorator_pattern">decorator pattern</a>.
 *
 * <p><b>{@code default} method warning:</b> This class does <i>not</i> forward calls to {@code
 * default} methods. Instead, it inherits their default implementations. When those implementations

                                    # pydantic >= 2.12.0
                                    {
                                        "type": "string",
                                        "pattern": r"^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$",
                                    },
                                ),
                            ],
                        },
                    },
                },

        @Test
        @DisplayName("Should handle special offset patterns")
        void testSpecialOffsetPatterns() {
            // Given - alternating bit pattern
            long pattern1 = 0xAAAAAAAAAAAAAAAAL;
            long pattern2 = 0x5555555555555555L;
            int pattern3 = 0xDEADBEEF;
            SrvCopychunk chunk = new SrvCopychunk(pattern1, pattern2, pattern3);
            byte[] buffer = new byte[EXPECTED_SIZE];

 * should override one or more methods to modify the behavior of the backing future as desired per
 * the <a href="http://en.wikipedia.org/wiki/Decorator_pattern">decorator pattern</a>.
 *
 * <p>Most subclasses can just use {@link SimpleForwardingListenableFuture}.
 *
 * @author Shardul Deo
 * @since 4.0
 */
@GwtCompatible

 * approximately equivalent in behavior to the same code written with try-with-resources.
 *
 * <p>This class is intended to be used in the following pattern:
 *
 * {@snippet :
 * Closer closer = Closer.create();
 * try {
 *   InputStream in = closer.register(openInputStream());
 *   OutputStream out = closer.register(openOutputStream());
 *   // do stuff

            "maven.build.allowExpressionInEffectiveProjectVersion";

    private static final Pattern CI_FRIENDLY_EXPRESSION = Pattern.compile("\\$\\{(.+?)}");
    private static final Pattern EXPRESSION_PROJECT_NAME_PATTERN = Pattern.compile("\\$\\{(project.+?)}");

    private static final String ILLEGAL_FS_CHARS = "\\/:\"<>|?*";

* Some public APIs have incorrect nullability annotations (both overly restrictive and overly permissive)

While there are competing ways to represent absence (`Optional`, "Null Object" pattern, method overloads),
it is unlikely that we'll be able to remove `null` entirely.

After migrating to Java 8, we can use pluggable type checkers to ensure that our annotations are consistent, 
and there are no missing null checks.

                0x7FFFFFFFFFFFFFFFL, // Long.MAX_VALUE
                0x8000000000000000L, // Long.MIN_VALUE
                0x0101010101010101L, // Repeating pattern
                0xFEFEFEFEFEFEFEFEL // Another pattern
        };

        for (long testValue : testValues) {
            FileInternalInfo testInfo = new FileInternalInfo();
            byte[] buffer = new byte[8];

 * override one or more methods to modify the behavior of the backing map as desired per the <a
 * href="http://en.wikipedia.org/wiki/Decorator_pattern">decorator pattern</a>.
 *
 * <p><b>{@code default} method warning:</b> This class forwards calls to <i>only some</i> {@code
 * default} methods. Specifically, it forwards calls only for methods that existed <a