You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TemplateMinerConfig throws a TypeError if the value set for parameter extraction cache capacity is an int, saying that the expected value must be of type str.
But if it is set to be a string it throws the following error:
"TypeError: '>' not supported between instances of 'int' and 'str'
The default value of parameter extraction cache capacity is set to be 3000 in TemplateMinerConfig, so it is indeed supposed to be an integer.
I have tried switching the .get method to .getint method when retrieving the config values through config parser. but that didn't work - still gives this error "TypeError: '>' not supported between instances of 'int' and 'str'.
Any help on how to change this config value would be very appreciated.
Thanks!
Edit: It seems like this issue is fixed in the latest version of the code but a new version has not been released with the change. Is it possible to do that anytime soon?
The text was updated successfully, but these errors were encountered:
The TemplateMinerConfig throws a TypeError if the value set for parameter extraction cache capacity is an int, saying that the expected value must be of type str.
But if it is set to be a string it throws the following error:
"TypeError: '>' not supported between instances of 'int' and 'str'
The default value of parameter extraction cache capacity is set to be 3000 in TemplateMinerConfig, so it is indeed supposed to be an integer.
I have tried switching the .get method to .getint method when retrieving the config values through config parser. but that didn't work - still gives this error "TypeError: '>' not supported between instances of 'int' and 'str'.
Any help on how to change this config value would be very appreciated.
Thanks!
Edit: It seems like this issue is fixed in the latest version of the code but a new version has not been released with the change. Is it possible to do that anytime soon?
The text was updated successfully, but these errors were encountered: