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
bash-4.4# cset set
Traceback (most recent call last):
File "/usr/bin/cset", line 47, in <module>
main()
File "/usr/lib/python3.6/site-packages/cpuset/main.py", line 234, in main
command.func(parser, options, args)
File "/usr/lib/python3.6/site-packages/cpuset/commands/set.py", line 212, in func
else: list_sets('root', options.recurse, options.usehex)
File "/usr/lib/python3.6/site-packages/cpuset/commands/set.py", line 243, in list_sets
pl.append(set_details(s,' ', 78, usehex))
File "/usr/lib/python3.6/site-packages/cpuset/commands/set.py", line 487, in set_details
pathb = set.path[len(set.path//2):]
TypeError: unsupported operand type(s) for //: 'str' and 'int'
Hi. I'm having the same issue. 'cpuset' was installed from Arch's AUR repository with 'yay'. Should I manually change the source myself as suggested?
Traceback (most recent call last):
File "/usr/bin/cset", line 47, in <module>
main()
File "/usr/lib/python3.11/site-packages/cpuset/main.py", line 234, in main
command.func(parser, options, args)
File "/usr/lib/python3.11/site-packages/cpuset/commands/set.py", line 186, in func
else: list_sets('root', options.recurse, options.usehex)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/cpuset/commands/set.py", line 243, in list_sets
pl.append(set_details(s,' ', 78, usehex))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/cpuset/commands/set.py", line 487, in set_details
pathb = set.path[len(set.path//2):]
~~~~~~~~^^~
TypeError: unsupported operand type(s) for //: 'str' and 'int'
Thanks for the reminder.
That's looks like a typo and it has been fixed in the commit a4b6b27 -- included in v1.6.1, so downstreams can bump their versions.
Closing.
Running 'cset set' might result in:
Should the code in set.py be updated like:
?
The text was updated successfully, but these errors were encountered: