Information about bug

Reproduce

1. Open the report "Employee Billing Summary"
2. Select an Employee

Error

TypeError: '<' not supported between instances of 'NoneType' and 'datetime.datetime'

See Stacktrace below

Module

projects

Version

ERPNext: v13.21.0 (version-13)
Frappe Framework: v13.21.0 (version-13)

Installation method

manual insta

Describe the bug
The output PO file has comments with a leading period:

#. Your free trial will end on August 6th and will not renew.
#: src/components/routes/billing/Status/Status.tsx:56
msgid "and will not renew."
msgstr ""

To Reproduce
Steps to reproduce the behavior, possibly with minimal code sample, e.g:

import { t } from "@lingui/macro"

cons

Describe the problem

It would be greate to have a way to define state of the unit on creation via an API.
If we will do it in 2 steps (1 — create unit, 2 — patch unit state), there may be an issue with data consistency. For example 1st request is done, but on second there will be network issue, or requester server has died unexpectedly.

`POST /api/translations/(string: project)/(string: c

https://github.com/traduora/traduora/blob/f921f7c5eab3b96d467a8a8a5dd8dd57f0615ee6/webapp/src/app/shared/components/search/search.component.ts#L21

Search result count is 10.
How can i set the pagesize on user side

It would be cool to add Google Translate support, because most likely Google Translate is better than Microsoft Translate.

And maybe it would be good idea to use Google Apps Script, because it has a free unlimited Google Translate. Here is an [example article](https://techstreams.github.io/2016/01/07/translation-automation-with-wor

This issue was created automatically by a script.

Bug 1703773

Bug Reporter: @flodolo
CC: @mathjazz

Currently sync runs following the alphabetical order of language names, not locale codes. That's not intuitive, and makes debugging sync issues harder.

Implement a feature matching tracker that matches features using descriptors instead of using KLT optical flow.

This feature may be related to Issue #4.