error when hit GET /get_plan using API v2 #39

indraaristya · 2023-02-06T01:49:51Z

500 status code error was occurred when I tried to hit /get_plan endpoint.
Body response: Undefined property: stdClass::$dataset_id

{
    "error": "Undefined property: stdClass::$dataset_id"
}

The text was updated successfully, but these errors were encountered:

shaheelroshankhan · 2023-02-06T06:21:04Z

I'm also hitting the same. Other APIs are working fine
APIError: TestRail API returned HTTP 500 ({'error': 'Undefined property: stdClass::$dataset_id'})

bdfariello · 2023-02-08T15:58:40Z

We're seeing the same in our TestRail Cloud instance

TestRail version: 7.8.0 Default (1136)
Built On: 1/25/2023
Database version: 20230105013501

We only started noticing it today

Moriarty16 · 2023-02-09T04:08:06Z

The same error while querying "api/v2/get_plan": "error": "Undefined property: stdClass::$dataset_id"

bdfariello · 2023-02-09T14:21:58Z

Something else I noticed today - we have some api/v2/get_plan/{plan_id} requests working successfully, while others do not

It seems like there was an attribute change in the back-end Test Plan objects, and so Plans created BEFORE we got this update trigger this bug, while Plans created AFTER we got this update do NOT trigger the bug.

sf0319 · 2023-02-09T18:03:53Z

Just wanted to pile to try and get more attention to this issue. I am seeing the exact same error for our instance as well since updating to TestRail version: 7.8.0 Default (1136).

indraaristya · 2023-02-10T01:21:35Z

Something else I noticed today - we have some api/v2/get_plan/{plan_id} requests working successfully, while others do not

It seems like there was an attribute change in the back-end Test Plan objects, and so Plans created BEFORE we got this update trigger this bug, while Plans created AFTER we got this update do NOT trigger the bug.

I've tried to update the test plan (only change the name) and save it then api/v2/get_plan/{plan_id} works perfectly again. Thanks!

indraaristya · 2023-02-10T01:22:47Z

[UPDATE]

You guys might need to update the test plan, try to change the name only or else and save it. The api/v2/get_plan/{plan_id} endpoint should be working fine after that. I've tried mine and it's works.

sf0319 · 2023-02-10T01:33:10Z

@indraaristya I wouldn't say that this issue is Resolved (or ready to be closed) just because there is a workaround. I would appreciate it if this bug was re-opened so that Gurock could address it and make a proper fix.

indraaristya · 2023-02-10T01:41:39Z

@indraaristya I wouldn't say that this issue is Resolved (or ready to be closed) just because there is a workaround. I would appreciate it if this bug was re-opened so that Gurock could address it and make a proper fix.

Sure, done.

Moriarty16 · 2023-02-13T08:54:17Z

4 days ago, request for plan A via this API fails, today the same request for plan A is successful.
However, request for another plan B still fails with the same error today.

bdfariello · 2023-02-13T13:23:45Z

Gurock has confirmed in a Tech Support case that I filed that they have internally reproduced the bug, but have not provided a timeline for its resolution.

…

On Mon, Feb 13, 2023, 3:54 AM MadHatter ***@***.***> wrote: 4 days ago, request for plan A via this API fails, today the same request for plan A is successful. However, request for another plan B still fails with the same error today. — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACDIDR7JJIWDOFS3SAWXCH3WXHZEHANCNFSM6AAAAAAUSDTYXU> . You are receiving this because you commented.Message ID: ***@***.***>

SarLecobee · 2023-02-13T18:30:58Z

Also started noticing this issue today.

patrick-cichon-gcx · 2023-02-15T08:08:17Z

We're also having the same issue since approximately a week

justinokoli · 2023-02-16T20:10:20Z

We are having this issues since a week now, all our operations are halted and we are considering next step with testrail

jbrekesJC · 2023-02-23T18:34:38Z

We have the same problem in my company since 2023-02-07, and I don't think that editing old plans would be so practical since we would have more than 2000 plans to change.

jnowo · 2023-02-27T14:56:23Z

I have the same problem since ~2023-02-20

Moriarty16 · 2023-03-02T10:41:50Z

The issue has been reported to TestRail 3 weeks ago, they confirmed it can be reproduced internally. But the issue has not been fixed so far...

Moriarty16 · 2023-03-03T11:23:34Z

It is said "There is no ETA for to bug but the fix will soon be released, most likely in the next TestRail update or the next two version upgrades".

So we may have to use the workaround for now until the new release fixes the issue.

jon-waite-tgcs · 2023-03-04T11:22:24Z

This is bad, it is blocking our reporting as an organization. Test Rail APIs are already overly verbose and nested, and now they do not work.

jnowo · 2023-03-10T08:31:31Z

For me it started working fine since yesterday. I don't get any errors with dataset_id now.

Moriarty16 · 2023-03-10T08:35:44Z

@jnowo As we tested earlier, we may fail to fetch data for some projects earlier, but then later we can successfully get the data for those projects. However, as I checked just now, I still get the same errors for some projects.
The issue is not fixed yet.

shaheelroshankhan · 2023-03-10T08:42:35Z

It started working for me as well. But still I'm seeing the same error for some of the *plan_id. *

…

On Fri, Mar 10, 2023 at 2:05 PM MadHatter ***@***.***> wrote: @jnowo <https://urldefense.com/v3/__https://github.com/jnowo__;!!MZ3Fw45to5uY!JFPC6mLa7wrYku7mH69W-LijWjMRInLUxpRMEwTKVC6jH7bcvMb9jWVDhNJDV4FkQRVkSE19GGGXtmTb9xKGdCHRI7mHALiVSFA$> As we tested earlier, we may fail to fetch data for some projects earlier, but then later we can successfully get the data for those projects. However, as I checked just now, I still get the same errors for some projects. *The issue is not fixed yet.* — Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/gurock/testrail-api/issues/39*issuecomment-1463454137__;Iw!!MZ3Fw45to5uY!JFPC6mLa7wrYku7mH69W-LijWjMRInLUxpRMEwTKVC6jH7bcvMb9jWVDhNJDV4FkQRVkSE19GGGXtmTb9xKGdCHRI7mHpdcH22k$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/A5WI4AD2CROHJRHKROUMEGDW3LRWXANCNFSM6AAAAAAUSDTYXU__;!!MZ3Fw45to5uY!JFPC6mLa7wrYku7mH69W-LijWjMRInLUxpRMEwTKVC6jH7bcvMb9jWVDhNJDV4FkQRVkSE19GGGXtmTb9xKGdCHRI7mHHLP9DXA$> . You are receiving this because you commented.Message ID: ***@***.***>

Moriarty16 · 2023-03-20T09:16:14Z

Possible workaround:

Get all the plans via get_plans/{project_id}
Loop all the plans, use try-catch to get all the plans with the "Undefined property: stdClass::$dataset_id" issue
For all the plans with the issue, change the plan names(maybe add _temp to the end of the plan name) via update_plan/{plan_id}, refer to update_plan
Change these plans to their original names
Query the data of these plans again, the issue should be fixed.

Note: This is just a possible workaround, as I haven't tested the API update_plan/{plan_id}, we only know if we manually update the plan name(add suffix and change back), then the http request will be fine.

Pls ignore the above comments, stupid I'm. Just realize, if there is an error in the request, we cannot get the plan name via API.

ziadtawfeek · 2023-03-20T10:31:09Z

I think this should be fixed now https://support.gurock.com/hc/en-us/articles/13703699589780-TestRail-7-8-0-Default-1140-

Moriarty16 · 2023-03-20T10:34:11Z

Actually we've heard the the issue should have been fixed within the above update, but the issue remains unfixed.
And as I tested locally, the issue hasn't been fix at this moment.
We've synced with TestRail again, waiting for their update.

Moriarty16 · 2023-04-04T06:34:26Z

We found the issue about 2 months ago, just tried locally, this issue can still be reproduced now.
Unbelievable, is this bug so complex that it need several months to fix......

jbrekesJC · 2023-04-20T18:11:23Z

This bug is really complicating some of our processes. Still no news on the solution?

Moriarty16 · 2023-04-21T03:00:52Z

They sueggest us to create freash projects, manually create fresh TestRun, TestCases, without any import(To confirm some assumptions).
The current plans we're testing are possibly corrupt, according to the recent conversations with them.

So the only solution for us is: Write a script to list all the current test plans in all the projects, then make requests to all the plans via API, record all the plans with this issue. Finally make the workaround to all these plans(rename) manually.

Moriarty16 · 2023-05-09T06:55:09Z

Now we're used a script to list all the plans with this issue, then run the workaround(rename, save, and rename back) on each of these plans one by one.
Now we can access all the plans via API...

indraaristya closed this as completed Feb 10, 2023

indraaristya reopened this Feb 10, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

error when hit GET /get_plan using API v2 #39

error when hit GET /get_plan using API v2 #39

indraaristya commented Feb 6, 2023

shaheelroshankhan commented Feb 6, 2023 •

edited

Loading

bdfariello commented Feb 8, 2023

Moriarty16 commented Feb 9, 2023

bdfariello commented Feb 9, 2023

sf0319 commented Feb 9, 2023

indraaristya commented Feb 10, 2023

indraaristya commented Feb 10, 2023

sf0319 commented Feb 10, 2023 •

edited

Loading

indraaristya commented Feb 10, 2023

Moriarty16 commented Feb 13, 2023

bdfariello commented Feb 13, 2023 via email

SarLecobee commented Feb 13, 2023

patrick-cichon-gcx commented Feb 15, 2023

justinokoli commented Feb 16, 2023 •

edited

Loading

jbrekesJC commented Feb 23, 2023

jnowo commented Feb 27, 2023

Moriarty16 commented Mar 2, 2023

Moriarty16 commented Mar 3, 2023 •

edited

Loading

jon-waite-tgcs commented Mar 4, 2023

jnowo commented Mar 10, 2023

Moriarty16 commented Mar 10, 2023

shaheelroshankhan commented Mar 10, 2023 via email

Moriarty16 commented Mar 20, 2023 •

edited

Loading

ziadtawfeek commented Mar 20, 2023

Moriarty16 commented Mar 20, 2023 •

edited

Loading

Moriarty16 commented Apr 4, 2023 •

edited

Loading

jbrekesJC commented Apr 20, 2023

Moriarty16 commented Apr 21, 2023 •

edited

Loading

Moriarty16 commented May 9, 2023

error when hit GET /get_plan using API v2 #39

error when hit GET /get_plan using API v2 #39

Comments

indraaristya commented Feb 6, 2023

shaheelroshankhan commented Feb 6, 2023 • edited Loading

bdfariello commented Feb 8, 2023

Moriarty16 commented Feb 9, 2023

bdfariello commented Feb 9, 2023

sf0319 commented Feb 9, 2023

indraaristya commented Feb 10, 2023

indraaristya commented Feb 10, 2023

sf0319 commented Feb 10, 2023 • edited Loading

indraaristya commented Feb 10, 2023

Moriarty16 commented Feb 13, 2023

bdfariello commented Feb 13, 2023 via email

SarLecobee commented Feb 13, 2023

patrick-cichon-gcx commented Feb 15, 2023

justinokoli commented Feb 16, 2023 • edited Loading

jbrekesJC commented Feb 23, 2023

jnowo commented Feb 27, 2023

Moriarty16 commented Mar 2, 2023

Moriarty16 commented Mar 3, 2023 • edited Loading

jon-waite-tgcs commented Mar 4, 2023

jnowo commented Mar 10, 2023

Moriarty16 commented Mar 10, 2023

shaheelroshankhan commented Mar 10, 2023 via email

Moriarty16 commented Mar 20, 2023 • edited Loading

ziadtawfeek commented Mar 20, 2023

Moriarty16 commented Mar 20, 2023 • edited Loading

Moriarty16 commented Apr 4, 2023 • edited Loading

jbrekesJC commented Apr 20, 2023

Moriarty16 commented Apr 21, 2023 • edited Loading

Moriarty16 commented May 9, 2023

shaheelroshankhan commented Feb 6, 2023 •

edited

Loading

sf0319 commented Feb 10, 2023 •

edited

Loading

justinokoli commented Feb 16, 2023 •

edited

Loading

Moriarty16 commented Mar 3, 2023 •

edited

Loading

Moriarty16 commented Mar 20, 2023 •

edited

Loading

Moriarty16 commented Mar 20, 2023 •

edited

Loading

Moriarty16 commented Apr 4, 2023 •

edited

Loading

Moriarty16 commented Apr 21, 2023 •

edited

Loading