rclone/vfs/vfstest/write_windows.go

//go:build windows

package vfstest

import (
	"runtime"
	"testing"

	"golang.org/x/sys/windows"
)

// TestWriteFileDoubleClose tests double close on write
func TestWriteFileDoubleClose(t *testing.T) {
	t.Skip("not supported on " + runtime.GOOS)
}

// writeTestDup performs the platform-specific implementation of the dup() syscall
func writeTestDup(oldfd uintptr) (uintptr, error) {
	p := windows.CurrentProcess()
	var h windows.Handle
	return uintptr(h), windows.DuplicateHandle(p, windows.Handle(oldfd), p, &h, 0, true, windows.DUPLICATE_SAME_ACCESS)
}
build: fix linting issues reported by running golangci-lint with different GOOS 2024-04-18 09:36:22 +02:00			`//go:build windows`
mountlib: fix cross platform tests 2017-05-10 12:19:32 +02:00
vfstests: move functional tests from mountlib and make them work with VFS The tests are now run for the mount commands and for the plain VFS. This makes the tests much easier to debug when running with a VFS than through a mount. 2020-04-16 14:33:46 +02:00			`package vfstest`
mountlib: fix cross platform tests 2017-05-10 12:19:32 +02:00
			`import (`
			`"runtime"`
			`"testing"`
vfs: move writeback of dirty data out of close() method into its own method (FlushWrites) and remove close() call from Flush() If a file handle is duplicated with dup() and the duplicate handle is flushed, rclone will go ahead and close the file, making the original file handle stale. This change removes the close() call from Flush() and replaces it with FlushWrites() so that the file only gets closed when Release() is called. The new FlushWrites method takes care of actually writing the file back to the underlying storage. Fixes #3381 2019-10-06 22:05:21 +02:00
			`"golang.org/x/sys/windows"`
mountlib: fix cross platform tests 2017-05-10 12:19:32 +02:00			`)`

			`// TestWriteFileDoubleClose tests double close on write`
			`func TestWriteFileDoubleClose(t *testing.T) {`
			`t.Skip("not supported on " + runtime.GOOS)`
			`}`
vfs: move writeback of dirty data out of close() method into its own method (FlushWrites) and remove close() call from Flush() If a file handle is duplicated with dup() and the duplicate handle is flushed, rclone will go ahead and close the file, making the original file handle stale. This change removes the close() call from Flush() and replaces it with FlushWrites() so that the file only gets closed when Release() is called. The new FlushWrites method takes care of actually writing the file back to the underlying storage. Fixes #3381 2019-10-06 22:05:21 +02:00
			`// writeTestDup performs the platform-specific implementation of the dup() syscall`
			`func writeTestDup(oldfd uintptr) (uintptr, error) {`
Fix lint issues reported by staticcheck Used staticcheck 2022.1.2 (v0.3.2) See: staticcheck.io 2022-06-08 22:25:17 +02:00			`p := windows.CurrentProcess()`
vfs: move writeback of dirty data out of close() method into its own method (FlushWrites) and remove close() call from Flush() If a file handle is duplicated with dup() and the duplicate handle is flushed, rclone will go ahead and close the file, making the original file handle stale. This change removes the close() call from Flush() and replaces it with FlushWrites() so that the file only gets closed when Release() is called. The new FlushWrites method takes care of actually writing the file back to the underlying storage. Fixes #3381 2019-10-06 22:05:21 +02:00			`var h windows.Handle`
			`return uintptr(h), windows.DuplicateHandle(p, windows.Handle(oldfd), p, &h, 0, true, windows.DUPLICATE_SAME_ACCESS)`
			`}`