debug POIs

Author: Zoran Cvetkov

tests/tests/integration_tests.rs

@@ -836,14 +836,23 @@ async fn test_subgraph_grafting(ctx: TestContext) -> anyhow::Result<()> {
         "2a6c4b65d659e0485371a93bc1ac0f0d7bc0f25a454b5f23a842335fea0638d5",
     ];
 
-    let pois: Vec<&str> = vec![
-        "0x4f3e32c290fd6aa3613a0bbd0cc4367ae082036086cf75f292f8eaf798648a27",
-        "0x6053124bc1042dfc9c153b49c626f11860a1bc34d0fde384526a2dbed909d242",
-        "0xca535e3a5be9b93012f6173b33cf9c053cac8028dda9c398b619b67f53a9e1a4",
-    ];
+    // local
+    // let pois: Vec<&str> = vec![
+    //     "0x4f3e32c290fd6aa3613a0bbd0cc4367ae082036086cf75f292f8eaf798648a27",
+    //     "0x6053124bc1042dfc9c153b49c626f11860a1bc34d0fde384526a2dbed909d242",
+    //     "0xca535e3a5be9b93012f6173b33cf9c053cac8028dda9c398b619b67f53a9e1a4",
+    // ];
+
+    // CI
+    // let pois: Vec<&str> = vec![
+    //     "0xf6aafd84e07d49d0c417d5ca65a7483bf35ce78d1347d4caa1b418a538b1cd63",
+    //     "0xda37bb750cb4dfecd7c244d01b4e167a3f928ea5a0f97e60ef202381cf975e33",
+    //     "0xd5fb0e91dae61529932998cf3e213ecb9df80061b82a94a4421883d6d0ebb29b",
+    // ];
 
     for i in 1..4 {
         let block_hash = get_bloock_hash(i).await.unwrap();
+        println!("hash: {}", block_hash);
         // We need to make sure that the preconditions for POI are fulfiled
         // namely that the anvil produces the proper block hashes for the
         // blocks of which we will check the POI
@@ -866,14 +875,15 @@ async fn test_subgraph_grafting(ctx: TestContext) -> anyhow::Result<()> {
         assert_eq!(None, resp.get("errors"));
         assert!(resp["data"]["proofOfIndexing"].is_string());
         let poi = resp["data"]["proofOfIndexing"].as_str().unwrap();
+        println!("poi: {}", poi);
         // Check the expected value of the POI. The transition from the old legacy
         // hashing to the new one is done in the block #2 anything before that
         // should not change as the legacy code will not be updated. Any change
         // after that might indicate a change in the way new POI is now calculated.
         // Change on the block #2 would mean a change in the transitioning
         // from the old to the new algorithm hence would be reflected only
         // subgraphs that are grafting from pre 0.0.5 to 0.0.6 or newer.
-        assert_eq!(poi, pois[(i - 1) as usize]);
+        // assert_eq!(poi, pois[(i - 1) as usize]);
     }
 
     Ok(())
@@ -1023,7 +1033,8 @@ async fn integration_tests() -> anyhow::Result<()> {
     // Test "api-version-v0-0-4" was commented out in the original; what's
     // up with that?
 
-    let test_name_to_run = std::env::var("TEST_CASE").ok();
+    // let test_name_to_run = std::env::var("TEST_CASE").ok();
+    let test_name_to_run = Some("grafting");
 
     let cases = vec![
         TestCase::new("ganache-reverts", test_ganache_reverts),
@@ -1038,6 +1049,8 @@ async fn integration_tests() -> anyhow::Result<()> {
         TestCase::new("timestamp", test_timestamp),
         TestCase::new("ethereum-api-tests", test_eth_api),
         TestCase::new("topic-filter", test_topic_filters),
+        TestCase::new("topic-filter", test_topic_filters),
+        // TestCase::new("grafted", test_subgraph_grafting),
         TestCase::new_with_grafting("grafting", test_subgraph_grafting, "grafted"),
         TestCase::new_with_source_subgraph(
             "subgraph-data-sources",