name: Scorecards analysis
    runs-on: ubuntu-latest
    permissions:
      # Needed to upload the results to code-scanning dashboard.
      security-events: write
      # Needed to publish results and get a badge (see publish_results below).
      id-token: write

    steps:
      - name: "Checkout code"
        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
        with:

            SMBUtil.writeInt2(0, readBuffer, 12);

            // When
            int written = response.writeBytesWireFormat(writeBuffer, 5);
            int read = response.readBytesWireFormat(readBuffer, 10);

            // Then
            assertEquals(0, written);
            assertEquals(4, read);
        }

        @Test

 * Lesser General Public License for more details.
 *
 * You should have received a copy of the GNU Lesser General Public
 * License along with this library; if not, write to the Free Software
 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
package jcifs.smb.compression;

import java.io.ByteArrayInputStream;
import java.io.ByteArrayOutputStream;

    /**
     * Constructs a TransCallNamedPipe request to write data to a named pipe.
     *
     * @param config the SMB configuration
     * @param pipeName the name of the pipe to call
     * @param data the data buffer to write to the pipe
     * @param off the offset in the data buffer
     * @param len the length of data to write
     */

            assertEquals(0, SMBUtil.readInt2(buffer, headerStart + 42)); // WriteChannelInfoLength
            assertEquals(0x01, SMBUtil.readInt4(buffer, headerStart + 44)); // Write flags

            // Verify data offset is written correctly
            int dataOffsetValue = SMBUtil.readInt2(buffer, headerStart + 2);
            assertEquals(headerStart - 0 + 48, dataOffsetValue); // Assuming getHeaderStart() returns 0

        try (ByteArrayOutputStream baos = new ByteArrayOutputStream();
                PrintWriter writer = new PrintWriter(baos, false, Constants.CHARSET_UTF_8)) {
            exception.printStackTrace(writer);
            writer.flush();
            append(buf, "exception", () -> StringEscapeUtils.escapeJson(new String(baos.toByteArray(), Constants.CHARSET_UTF_8)));

  issue_comment:
    types:
      - created
  issues:
    types:
      - labeled
  pull_request_target:
    types:
      - labeled
  workflow_dispatch:

permissions:
  issues: write
  pull-requests: write

jobs:
  issue-manager:
    if: github.repository_owner == 'fastapi'
    runs-on: ubuntu-latest
    steps:
      - name: Dump GitHub context
        env:

on 16 drive MinIO deployment. If you use eight data and eight parity drives, the file space usage will be approximately twice, i.e. 100 MiB
file will take 200 MiB space. But, if you use ten data and six parity drives, same 100 MiB file takes around 160 MiB. If you use 14 data and
two parity drives, 100 MiB file takes only approximately 114 MiB.

    @Throws(IOException::class)
    override fun writeTo(sink: BufferedSink) {
      val forwardingSink =
        object : ForwardingSink(sink) {
          private var totalBytesWritten: Long = 0
          private var completed = false

          override fun write(
            source: Buffer,
            byteCount: Long,
          ) {
            super.write(source, byteCount)
            totalBytesWritten += byteCount

- [ ] Your pull request should address just one issue, without pulling in other changes.
- [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
- [ ] Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.