Jan Harkes
Jan Harkes
Maybe more of a coda-packaging issue, but we should try to avoid restarting the coda-client when upgrading the package. When the restart fails it breaks the upgrade process and restarts...
Don't think I've seen this one before. coda-7.0.5 ``` Assertion failed: VV_Check(&HowMany, VV, 0) || IsWeaklyEqual(VV, VSG_MEMBERS), file "resfile.cc", line 184 ***BackTrace*** /usr/sbin/codasrv(coda_assert+0x82)[0x80eaef2] /usr/sbin/codasrv(_Z11FileResolveP11res_mgrpentP7ViceFidPP17ViceVersionVector+0x7d1)[0x80c2d31] /usr/sbin/codasrv[0x807207a] /usr/sbin/codasrv(FS_ViceResolve+0xad)[0x807243d] /usr/sbin/codasrv(srv_ExecuteRequest+0x4e4)[0x8088934] /usr/sbin/codasrv[0x8066c21] /usr/lib/coda/liblwp.so.2(+0x5c54)[0xb76c6c54] linux-gate.so.1(__kernel_sigreturn+0x0)[0xb7759c8c]...
- There are quite a few warnings from gcc-7.3.0 that have not been looked into. - @krichter722 suggested looking into [cppcheck](http://cppcheck.sourceforge.net/) for additional checks.
On Ubuntu-xenial, python-notify was replaced by python-notify2 which is not quite compatible enough to be a drop-in replacement.
When a server is restarted (or upgraded/downgraded) the existing logs are overwritten by the new process. I lost some valuable information in the logs when I downgraded from an experimental...
Every place we pack/unpack defines their own copy struct foo_in/foo_out and there are no helper functions to perform the packing or unpacking. Some ioctls are used in up to 6...
Not in a state to be merged. Just a place holder to track comments and progress.
Several smaller fixes split out from a larger type hinting change I'm still working on.
If the app is started and fps is supposed to be enabled, it doesn't show until after we go to the settings to check if it is enabled.