README

Author: mwrites

2-counter/README.md

@@ -17,5 +17,5 @@ Get a new program id:
 
 Run the tests and observe the logs:
 ```bash
-anchor test
+anchor test --skip-local-validator
 ```

distributor/README.md

@@ -21,14 +21,14 @@ We start by defining an instruction to execute, that is the __"WHAT"__:
 **2. Client Side - Creating a Thread**
 Time to switch perspective, we need to do some work off-chain now, we will create a Thread, that's the __"HOW"__:
 - Check the `tests` folder, we are using anchor tests as a client.
-- Run `anchor tests`, this will create a __Thread__ that listens for a certain account and print logs whenever the
+- Run `anchor test --skip-local-validator`, this will create a __Thread__ that listens for a certain account and print logs whenever the
   account is updated.
 
 ## How do I know if it works?
 Let's see how we can observe our newly created Thread:
 - Run the tests!
 ```bash
-anchor test
+anchor test --skip-local-validator
 ```
 - If you have the Clockwork Cli installed, you can use the `clockwork` command
 ```bash

event_stream/README.md

@@ -17,7 +17,7 @@ We start by defining an instruction to execute, that is the __"WHAT"__:
 
 Time to switch perspective, we need to do some work off-chain now, we will create a Thread, that's the __"HOW"__:
 - Check the `tests` folder, we are using anchor tests as a client.
-- Run `anchor test`, this will create a __Thread__ that listens for a certain account and print logs whenever the
+- Run `anchor test --skip-local-validator`, this will create a __Thread__ that listens for a certain account and print logs whenever the
   account is updated.
 
 ## How do I know if it works?

hello_clockwork/README.md

@@ -17,5 +17,5 @@ Get a new program id:
 
 Run the tests and observe the logs:
 ```bash
-anchor test
+anchor test --skip-local-validator
 ```

payments/README.md

@@ -23,7 +23,7 @@ We start by defining an instruction to execute, that is the __"WHAT"__:
 
 Time to switch perspective, we need to do some work off-chain now, we will create a Thread, that's the __"HOW"__:
 - Check the `tests` folder, we are using anchor tests as a client.
-- Run `anchor tests`, this will create a __Thread__ that listens for a certain account and print logs whenever the
+- Run `anchor test --skip-local-validator`, this will create a __Thread__ that listens for a certain account and print logs whenever the
   account is updated.
 
 ## How do I know if it works?
@@ -44,7 +44,7 @@ clockwork thread get <your_thread_label>
 Let's see how we can observe our newly created Thread:
 - Run the tests!
 ```bash
-anchor test
+anchor test --skip-local-validator
 ```
 - If you have the Clockwork Cli installed, you can use the `clockwork` command
 ```bash

pyth_feed/README.md

@@ -17,7 +17,7 @@ We start by defining an instruction to execute, that is the __"WHAT"__:
 
 Time to switch perspective, we need to do some work off-chain now, we will create a Thread, that's the __"HOW"__:
 - Check the `tests` folder, we are using anchor tests as a client.
-- Run `anchor tests`, this will create a __Thread__ that listens for a certain account and print logs whenever the
+- Run `anchor test --skip-local-validator`, this will create a __Thread__ that listens for a certain account and print logs whenever the
   account is updated.
 
 ## How do I know if it works?
@@ -33,19 +33,6 @@ ping tx: ✅ https://explorer.solana.com/tx/...
 clockwork thread get --address <your_thread_address> 
 clockwork thread get <your_thread_label>
 ```
-
-## How do I know if it works?
-Let's see how we can observe our newly created Thread:
-- Run the tests!
-```bash
-anchor test
-```
-- If you have the Clockwork Cli installed, you can use the `clockwork` command
-```bash
-clockwork thread get --address <your_thread_address> 
-clockwork thread get <your_thread_label>
-```
-
 ---
 
 ## Common Errors