Page 1 of 1
session-setup: unicode as required
Published: October 31, 2019 - 11:11
by keeper
Hello,
I have two packages that I'm trying to configure. All the tests are functional from PyScripter, but once I run `session-setup` either at runtime or from the command line, I get this error:
2019-10-31 10:57:17,369 CRITICAL AttributeError: 'unicode' object has no attribute 'asrequirement'.
This happens even though the `session-setup` function only contains a simple `print` statement of 'toto'. My
Wapt version is 1.7.4.6229.
Re: session-setup: unicode as required
Published: October 31, 2019 - 11:17 AM
by keeper
Additional information: the error seems to be in the "common.py" file, line 6157: `
print(u"Running session_setup for package %s and user %s" % (package.asrequirement(),self.user))`.
Commenting it out fixes it, but I'm hesitant to do that on all agents. :/
Re: session-setup: unicode as required
Published: October 31, 2019 - 12:21
by keeper
I'm replying to myself again; for me, it's a bug. The correct line is this: `
print(u"Running session_setup for package %s and user %s" % (package_entry.asrequirement(),self.user))`
Re: session-setup: unicode as required
Published: October 31, 2019 - 12:57 PM
by htouvet
Yes, that's right. Thank you .
Re: session-setup: unicode as required
Published: October 31, 2019 - 1:36 PM
by htouvet
Re: session-setup: unicode as required
Published: October 31, 2019 - 2:42 PM
by keeper
Thanks for the feedback, and glad I could help.
However, how do I deploy the build? The CentOS repository only accepts the stable version, and in theory, it's only the agent that's causing the problem.
Re: session-setup: unicode as required
Published: November 4, 2019 - 12:48 PM
by htouvet
Version 6232 is now the stable version.
RPMs should be available with yum.
Otherwise, you can download only waptsetup.exe to your Wapt management machine and recreate waptagent.exe from there.