* Adding document describing how to use logger
* Adjusting logs to follow a new guide
* Change order in log header:
line number is now before function name
Outbox endpoint will be used to provide notifications
about changes in messages/threads/calls during connection
with Mudita Center. This mechanism will ensure an efficient
data synchronization between Mudita Pure and Mudita Center.
In case of disconnection from MC during reception of large messages
(e.g. to FS endpoint), the parser may be left in a state expecting
further parts of the message. This causes incorrect handling of new
messages arriving after reconnection to MC.
Added a timer to reset a Parser when transfer times out.
Split module-utils into smaller components for better dependency
management. Fix many dependencies throughout the project.
Signed-off-by: Marcin Smoczyński <smoczynski.marcin@gmail.com>
Changed:
- Runtime disabled logs which didn't add value from ServiceDesktop
- Runtime disabled logs which didn't add value from SystemManager
- Added possibility to change runtime logging levels
- Integrated ServiceDesktop developer code a bit - it might be used
as virtual base with little to no modifications for other endpoints
which would result with less redundant code
We have no controll on UART over the device flushing, minimum code
added to assure that data could be flushed
We do not close services when these are closed with reason
Body field was always added to response json, even if
it was containing only null. Now empty body is
not attached to response json, and status code
for such message is set to 204. Additionaly some
minor cleanup in service desktop was done.
- Added pass code unlock from MC
- Removed Set USB security status
- Changed isLocked to phoneLocked in request for phone lock status
- Removed remainings of USB security in Settings App
- Reworked USB security model to depend both on
Phone lock state and Pass code being enabled
- Updated test_security.py
Remove body field from response message,
if it contains null. Add 204 and 501 status codes
and use them in proper responses.
204 stands for success but no content, and 501
means endpoint is not implemented.
Additionally some minor fixes.
Fix wrong "count" key word in contacts, and add test for variables in
device info endpoint.
Disabled test jira:
5906 - test_calendar_events.py
5907 - test_connection_security.py
5908 - test_dom_dump.py
5909 - test_usb_echo.py
Pagination added for contact endpoint.
Introduced PagedContext and query message for contacts that returns
the required contacts together with the number of all contacts in db.
Introducing changes according to new messages endpoint api
proposal doc. All request have been updated, and some new were added.
Harness tests were updated too. These changes will be followed up with
pagination implementation.
In order to be able to interrupt the OS update after its launch in
the phone, it was necessary to implement the new "Abort" message
for the Update Endpoint API.
Handling queues with static std::string implementation caused
problem of double-free memory on turning off simulator. Applied
solution to the problem is to pass ownership of queued string to
a receiver side.
* [EGD-4559] store update history in settings db
* [EGD-4559] first review fixes
* [EGD-4559] catch changed
Co-authored-by: Alek Rudnik <aleksander.rudnik@mudita.com>
