On Windows platform '\\.\pipe\' directory can be monitored to catch the creation of named pipes.
When the following program is executed, the connection to the named pipe should not be processed, but the connection is made at the point of creation of the named pipe on the server process side, resulting in an error within the waiting process of the server process.
class PipeCreateEventHandler(FileSystemEventHandler):
def on_created(self, event):
print(f"on_created: {event.src_path}")
if event.src_path == r'\\.\pipe\mypipe':
observer.stop()
observer = Observer()
observer.schedule(PipeCreateEventHandler(), r'\\.\pipe''\\', recursive=False, event_filter=[FileCreatedEvent])
observer.start()
observer.join()
# Do something using '\\.\pipe\mypipe'
Perhaps the os.path.isdir() call in read_directory_changes.py is the cause.
On Windows platform '\\.\pipe\' directory can be monitored to catch the creation of named pipes.
When the following program is executed, the connection to the named pipe should not be processed, but the connection is made at the point of creation of the named pipe on the server process side, resulting in an error within the waiting process of the server process.
Perhaps the
os.path.isdir()
call in read_directory_changes.py is the cause.For reference, here is a server program for testing with PowerShell.