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.

Sign up for GitHub

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

Jump to bottom

Migration of loggers to Bazel #1519

Open
Sarthak2601 opened this issue Jul 24, 2020 · 2 comments
Open

Migration of loggers to Bazel #1519

Sarthak2601 opened this issue Jul 24, 2020 · 2 comments
Assignees
@BenHenning
Labels
bug End user-perceivable behaviors which are not desirable. Impact: Low Low perceived user impact (e.g. edge cases). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Priority: Important This work item is really important to complete for its milestone, but it can be scoped out. Type: Task A single task of work corresponding to a greater milestone. Generally corresponds to a single PR. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@Sarthak2601
Copy link
Contributor

Even after the current implementation of restructuring via #1433 we'll still not be able to re-route the calling of loggers from the utility, data and testing modules to the restructured OppiaLogger. However this problem can be solved once we migrate to Bazel. So this issue tracks the migration of loggers to bazel from gradle and restructuring the logging calls in the mentioned modules.
@Sarthak2601 Sarthak2601 added Priority: Important This work item is really important to complete for its milestone, but it can be scoped out. Type: Task A single task of work corresponding to a greater milestone. Generally corresponds to a single PR. labels Jul 24, 2020
@Sarthak2601
Copy link
Contributor Author

@miaboloix FYI since you're doing the migration.

@miaboloix miaboloix self-assigned this Aug 10, 2020
@BenHenning BenHenning assigned fsharpasharp and unassigned miaboloix Feb 19, 2021
@BenHenning
Copy link
Sponsor Member

Assigning this to you @fsharpasharp to decide what to do with.

@Broppia Broppia added dev_team Impact: Low Low perceived user impact (e.g. edge cases). labels Jul 29, 2022
@BenHenning BenHenning added Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Z-ibt Temporary label for Ben to keep track of issues he's triaged. issue_user_developer labels Sep 15, 2022
@seanlip seanlip added bug End user-perceivable behaviors which are not desirable. and removed issue_type_infrastructure labels Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@BenHenning BenHenning

Labels
bug End user-perceivable behaviors which are not desirable. Impact: Low Low perceived user impact (e.g. edge cases). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Priority: Important This work item is really important to complete for its milestone, but it can be scoped out. Type: Task A single task of work corresponding to a greater milestone. Generally corresponds to a single PR. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Projects
[Task Force] Migrate to Bazel - Android
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
6 participants
@seanlip @BenHenning @fsharpasharp @miaboloix @Sarthak2601 @Broppia