* feat: capture custom values in frappe monitor
lets monitor add extra info for:
- Save/Submit by doctype
- Report generation time by standard report name
(cherry picked from commit 967cc26fab)
* fix: use compact JSON representation for monitor
(cherry picked from commit 939bf872ae)
Co-authored-by: Ankush Menat <ankush@frappe.io>
* perf: initialise field map when initialising meta
(cherry picked from commit df8399f5d3)
* perf: simpler, faster meta cache
(cherry picked from commit 6c6a969d3a)
* fix: ensure error is thrown
(cherry picked from commit b529c27cb5)
* refactor: drop _allow_dict support
This is not required anymore since we store full doc anyway. Also since
they share same cache key calling get_cached_value and get_cached_doc
can end up doing duplicate / double work.
(cherry picked from commit abd018773b)
* fix: pickle doc objects directly
This seems to be missed out and causes performance regression in IRL
usage when get_doc is called on cached doc already.
(cherry picked from commit bcb5fe91aa)
* test: basic perf test for rps on get_list
(cherry picked from commit c28ddcc3e6)
* build: pin testing-library/dom temporarily
refer https://github.com/testing-library/dom-testing-library/issues/1169
(cherry picked from commit 40f6a34840)
* chore: semantic changes to document caching code
* fix: drop Meta cache during update
Revert "fix: drop Meta cache during update" (#18186)
* Revert "fix: drop Meta cache during update (#18182)"
This reverts commit 656f6df257.
* fix: replace meta cache keys
Old keys stored different types of data `dict` changing key to indicate
change in type.
* perf: cache `FormMeta` directly (#18165)
* perf: cache `FormMeta` directly
* perf: check if `dt` is table, use `db.get_value` instead of `get_all`
Co-authored-by: Sagar Vora <sagar@resilient.tech>
Co-authored-by: Ankush Menat <ankush@frappe.io>
* fix: change fieldtype of restrict_ip from data to small text
(cherry picked from commit 359f0c3dcb)
* test: use middle_name instead of restrict_ip in test_index_and_unique_constraints
(cherry picked from commit 82d0faf3d2)
Co-authored-by: phot0n <ritwikpuri5678@gmail.com>
if the event is completed today then user can mark it as completed not closed
Co-authored-by: Ankush Menat <ankush@frappe.io>
(cherry picked from commit 2e7d41047b)
Co-authored-by: MOHAMMED NIYAS <76736615+niyazrazak@users.noreply.github.com>
* build: move all devDependencies to Dependencies
These are real dependencies without which you can't locally build apps.
(cherry picked from commit 06aaaaaedf)
* fix: fail code when build fails in production
In production it is useful to fail with proper exit code. To avoid
silently pushing bad assets in built pipelines.
(cherry picked from commit 1ba99396bc)
Co-authored-by: Ankush Menat <ankush@frappe.io>
* perf: drop many unused indexes
- reference owner - only used for activity page which is unusable
*anyway*
- same for timeline and link doctypes
perf: drop unused index from Commment
Can't find a single query that uses this index
perf: drop pointless "Is home folder" index
just why? It's checkbox index with 1 entry which has unique name already
Most pointless index I've seen no far.
perf: Drop "attached to doctype" separate index
There is already a composite index for this.
perf: drop indexes from web page view log
BOTH are totally unused in any of the queries related to this doctype.
Only "website analytics" report uses this which doesn't even show this
data lmao.
perf: drop unused index from EPS log
We never filter by doctype or type. pointless indexing.
perf: fix up notification log indexes
- drop unused index
- add "for user" index
(cherry picked from commit 3a5a45d8af)
* perf: drop all old `parent` indexes
- re-add parent index on custom_docperm
(cherry picked from commit 7453e8e3a1)
Co-authored-by: Ankush Menat <ankush@frappe.io>
* allow multiple kanban board creation for the same doctype
* simplify show_kanban_dialog
* directly jump to a kanban if available/from last_opened_kanban property - no need to show a dialog for selection
(cherry picked from commit 255bc211af)
* feat: db.begin(read_only=True)
You can now start read only transaction by passing read only flag. Read
only transactions prevent any query that is of "WRITE" type like
insert/delete/update.
(cherry picked from commit 5e86e1f192)
* feat: allow reads during maintenance_mode
To reduce downtime reading from main db server during maintenance_mode
can be allowed. This lets users browse desk, static sites or any other
pages while ensuring that no writes happen to DB.
refactor: use read replica if available
(cherry picked from commit 5beccd8802)
* fix: always explicitly start a new transaction
Active read only transaction can be aborted by doing a commit and then
issuing queries. This prevents such edge cases.
(cherry picked from commit 4389447148)
* fix: dont renew session during read only mode
(cherry picked from commit 5922c0ea35)
* feat: wrap read only mode SQL errors
(cherry picked from commit f96505fae0)
* fix: defer logging during read only mode
Deferred:
- Error log
- view log
- web page view
Disable:
- "_seen" tracking used on list view to highlight unseen docs.
- "seen" on error log.
- dashboard chart last ts caching
(cherry picked from commit 55617b9e86)
* fix: ensure deferred insert are flushed during update
(cherry picked from commit 98b57f6a1a)
* fix: remove ad-hoc maintenance mode implementation
(cherry picked from commit e1253e8299)
* feat(UX): Disable write actions in read-only Desk
I won't be covering each and every aspect of desk that shouldn't work in
read only mode. This just handles major interactions and assumes that
user will get a hint about why other things aren't working.
Changes:
- Add read only badge on navbar.
- Disable forms
- Disable new doc creation
(cherry picked from commit 1ec03dacff)
* test: add api tests for read only mode
(cherry picked from commit 7f316fa427)
* feat(ux): `no-indicator-dot` for indicator pills
Adding this class will disable indicator's tiny dot added before text.
(cherry picked from commit f6c548c7b9)
* refactor: remove dead flag db.read_only
This was added in last DB refactor but it does nothing, it was probably
supposed to do something with the connection pool but to best of my
knowledge "read only" is not a property of a connection.
It can be achieved with users who only have read access, that however
isn't implemented anywhere.
Removing this for now.
(cherry picked from commit ea7fbb2c10)
# Conflicts:
# frappe/database/__init__.py
* fix(UX): show read only mode warning on web pages
(cherry picked from commit 06d888126b)
* perf: duplicate database initialization (#18049)
* fix: don't attempt to delete session during read only session
* fix: error handling without user set
* chore: conflicts
Co-authored-by: Ankush Menat <ankush@frappe.io>
Since we destroy the connection after app installation,
mariadb implicitly rollsback the transaction hence committing upon successfull
app installation to prevent data sync loss
(cherry picked from commit 3539dacdf0)
Ankush Menat
mergify[bot]
Aradhya Tripathi
Anoop Kurungadam
Aradhya
Nrtyck
Ankush Menat
Ritwik Puri
Sagar Vora
Shariq Ansari
Shariq Ansari