-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downgrading xmltodict to 0.12.0 makes the script slow #203
Comments
@dixudx or @gpongelli any other ideas how to solve it. would be helpful |
@SureshRIS Please try to install rtcclient with version 0.9.0. |
@dixudx I installed rtcclient with 0.9.0 and then i downgraded the xmltodict to 0.12.0 and i got the following warning/error while downgrading
But still even now with xmltodict-0.12.0 , the script is very slow. Thanks a lot for commenting or supporting @dixudx |
@SureshRIS I think there is no need to downgrade xmltodict to 0.12.0, which is a buggy version. That's why we pin xmltodict to 0.13.0. |
Okay, i also tried the possibility with rtcclient with 0.9.0 and xmltodict to 0.13.0 , but still i only get the RDF links (when accessing any attribute) {'@Rdf:resource': 'https://rb-almcom/jts/users/AEJ34JR'} -> for example |
Then there is no need to worry about the xmltodict version. Please go ahead on using rtcclient with 0.9.0.
From above resource link, it seems to be a user link. Lines 315 to 344 in 832019e
|
I face issue similar to issue #177 and i saw solutions provided with PR #178 and i tried this way (updating _init.py) and it makes fetching WI's very slow
As well as i tried downgrading my xmltodict to <=0.12.0 but this also makes fetching WI's very slow
Is there any alternative solution for this ? I would like to get attributes owned by or plannedFor but i only get them as a link like : https://rb-alm.com/ccm/oslc/workflows/_qi848CJaEeSy9NmiE0zU4Q/states/com.bosch.rtc.configuration.workflow.workflowdefinition.review/com.bosch.rtc.configuration.workflow.workflowdefinition.review.state.s1
The text was updated successfully, but these errors were encountered: