Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: OPTIC-1367: Find opportunities for property cache #6808

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

mcanu
Copy link
Contributor

@mcanu mcanu commented Dec 18, 2024

PR fulfills these requirements

  • Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
  • Tests for the changes have been added/updated (for bug fixes/features)
  • Docs have been added/updated (for bug fixes/features)
  • Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
  • Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)

(check all that apply)

  • Product design
  • Backend (Database)
  • Backend (API)
  • Frontend

Describe the reason for change

We are proactively trying to use cached_property to address performance issues and standardize caching methodologies of properties.
I changed @property methods that looked low risk and I understood its usage.
self.get_parent_object() was the only piece of code that I identified was being called two times in the same request in OrganizationMemberDetailAPI.

Does this PR introduce a breaking change?

(check only one)

  • Yes, and covered entirely by feature flag(s)
  • Yes, and covered partially by feature flag(s)
  • No
  • Not sure (briefly explain the situation below)

What level of testing was included in the change?

(check all that apply)

  • e2e
  • integration
  • unit

Which logical domain(s) does this change affect?

(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

@github-actions github-actions bot added the feat label Dec 18, 2024
Copy link

netlify bot commented Dec 18, 2024

Deploy Preview for label-studio-docs-new-theme canceled.

Name Link
🔨 Latest commit 968a881
🔍 Latest deploy log https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/67633d3b676d1c0008de6096

Copy link

netlify bot commented Dec 18, 2024

Deploy Preview for heartex-docs canceled.

Name Link
🔨 Latest commit 968a881
🔍 Latest deploy log https://app.netlify.com/sites/heartex-docs/deploys/67633d3bd082b10008c3d087

Copy link

codecov bot commented Dec 18, 2024

Codecov Report

Attention: Patch coverage is 93.75000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 76.79%. Comparing base (bd3498d) to head (968a881).

Files with missing lines Patch % Lines
label_studio/data_import/models.py 80.00% 2 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #6808      +/-   ##
===========================================
+ Coverage    76.78%   76.79%   +0.01%     
===========================================
  Files          171      171              
  Lines        14023    14030       +7     
===========================================
+ Hits         10767    10775       +8     
+ Misses        3256     3255       -1     
Flag Coverage Δ
pytests 76.79% <93.75%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant