[YAML] test_get_traction_info_empty - Exception: Query failed

[trentmc]

Background / motivation

Both tests in test_get_traction_info.py fail. It seems to be a sporadic failure. We should get to the bottom of the failures, and stabilize this test to be more reliable.

=========================== short test summary info ============================
FAILED pdr_backend/analytics/test/test_get_traction_info.py::test_get_traction_info_main_mainnet - Exception: Query failed. Url: https://v4.subgraph.sapphire-mainnet.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph. Return code is 503

            {
                predictSubscriptions(skip: 0, first: 1000 , where: {predictContract_: {id_in: ["0x123"]}, timestamp_gt: 1698883200, timestamp_lt: 1699142400}) {
                    id
                    txId
                    timestamp
                    user {
                        id
                    }
                    predictContract {
                        id
                        token {
                            id
                            name
                            lastPriceValue
                            nft{
                                nftData {
                                key
                                value
                                }
                            }
                        }
                    }
                }
            }
FAILED pdr_backend/analytics/test/test_get_traction_info.py::test_get_traction_info_empty - Exception: Query failed. Url: https://v4.subgraph.sapphire-mainnet.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph. Return code is 503

        {
            tokens(where: {
                nft_: {
                    owner: "0x4ac2e51f9b1b0ca9e000dfe6032b24639b172703"
                }
            }) {
                id
            }
        }
======= 2 failed, 330 passed, 3 skipped, 9 warnings in 108.16s (0:01:48) =======

See this log for full traceback.

Note: this failure is sporadic. So far, I've (Trent) only seen it once, in the log above (Jan 10, 2024).

• Q: Was this issue was likely introduced in the tweaks for network override as part of PR Fix #505: polars.exceptions.ComputeError: datatypes of join keys don't match #510 ?
• A: No, because both tests that fail have the network override off. (I double-checked this with more testing)

[calina-c]

Closed by #534.