Julien 1203d5bd90 Don't use os.Stdout in tests (#16795) ... Some tests were writing directly to os.Stdout, causing noise for other tests. For `TestRunWithOutputDoesNotMissData` we don't need to write anything, we only need a slow writer. For `TestNonblockingStdout` we need to more carefully emulate the behaviour seen with os.Stdout. We can do this using a named pipe initially opened from Go without O_NONBLOCK. This ensures that Go thinks this file descriptor is blocking and does not add the file to its internal poller that handles non-blocking IO. As previously, we then trick Go by changing the file to be non-blocking behind its back and trigger the bug. --------- Co-authored-by: Fraser Waters <fraser@pulumi.com>		2024-07-25 12:14:02 +00:00
..
dynamic-provider	Upgrade to grpc-js 1.10.1 and remove calls to deprecated server.start (#15500)	2024-02-23 11:32:40 +00:00
pulumi-language-nodejs	Don't use os.Stdout in tests (#16795)	2024-07-25 12:14:02 +00:00
run	Only look for main in package.json if no entyrpoint was set via Pulumi.yaml (#16363)	2024-06-11 11:36:34 +00:00
run-policy-pack	Vendor TypeScript and ts-node (#15622)	2024-04-10 15:26:37 +00:00