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

Fix #3056 & #3076: Create a BUILD.bazel file for the logging package in the utility module #3079

Merged
merged 15 commits into from
May 10, 2021

Conversation

jonathanalvares9009
Copy link
Contributor

@jonathanalvares9009 jonathanalvares9009 commented Apr 10, 2021

Created a BUILD.bazel file for the logging package in the utility module.
Fixes #3056 and #3076

Explanation

Checklist

  • The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
  • The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
  • The PR follows the style guide.
  • The PR does not contain any unnecessary auto-generated code from Android Studio.
  • The PR is made from a branch that's not called "develop".
  • The PR is made from a branch that is up-to-date with "develop".
  • The PR's branch is based on "develop" and not on any other branch.
  • The PR is assigned to an appropriate reviewer in both the Assignees and the Reviewers sections.

@BenHenning
Copy link
Sponsor Member

@fsharpasharp can you take a first pass on this & assign it back after it looks good to you?

Copy link
Contributor

@fsharpasharp fsharpasharp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work! This was a lot of libraries. Main thing here is to create another BUILD.bazel file for the firebase specific libraries.

srcs = [
"LogLevel.kt",
],
visibility = ["//:oppia_api_visibility"],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to omit the visibility field and make this library private? It seems like it is only used within the package itself.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I'll do it private

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@jonathanalvares9009
Copy link
Contributor Author

@fsharpasharp I'm getting this error can you help me?
Screenshot 2021-04-13 at 11 44 48 PM

@jonathanalvares9009
Copy link
Contributor Author

I'm trying to push to origin

@fsharpasharp
Copy link
Contributor

Try pulling the latest develop branch first.

@jonathanalvares9009
Copy link
Contributor Author

I got this error after merging the latest changes into my local branch. I'm using GitHub oath tokens is it creating this issue @fsharpasharp ?

@fsharpasharp
Copy link
Contributor

I got this error after merging the latest changes into my local branch. I'm using GitHub oath tokens is it creating this issue @fsharpasharp ?

Hm, could you check if there's anything on here that could help: https://stackoverflow.com/questions/64059610/how-to-resolve-refusing-to-allow-an-oauth-app-to-create-or-update-workflow-on

I'm not familiar with the issue.

@jonathanalvares9009 jonathanalvares9009 changed the title Fix #3056: Create a BUILD.bazel file for the logging package in the utility module Fix #3056 & #3076: Create a BUILD.bazel file for the logging package in the utility module Apr 16, 2021
@jonathanalvares9009
Copy link
Contributor Author

@fsharpasharp if I run bazel tests locally it passes for both testing and data but here it fails.

Copy link
Sponsor Member

@BenHenning BenHenning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jonathanalvares9009. This LGTM.

The Bazel failure is unrelated to this PR, so we can ignore it.

@BenHenning BenHenning removed their assignment Apr 27, 2021
Copy link
Contributor

@vinitamurthi vinitamurthi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks

@vinitamurthi vinitamurthi removed their assignment Apr 27, 2021
@jonathanalvares9009
Copy link
Contributor Author

@fsharpasharp can you review my PR?

@fsharpasharp
Copy link
Contributor

Thanks @jonathanalvares9009 !

@jonathanalvares9009
Copy link
Contributor Author

@BenHenning could you merge the PR?

@seanlip
Copy link
Member

seanlip commented Apr 28, 2021

@JonathanAlvares FYI there are a couple of failing checks (see the Robolectric unit tests).

@anandwana001 anandwana001 added the PR don't merge - NEEDS UPDATE Corresponds to PRs that need to be updated with the latest develop changes before they can be merged label May 7, 2021
@fsharpasharp
Copy link
Contributor

Hey @jonathanalvares9009. Could you try updating the PR with the latest develop branch so we can look to get this merged? Also let me know if you're interested in doing more Bazel stuff as we look towards /domain and /app.

@jonathanalvares9009
Copy link
Contributor Author

jonathanalvares9009 commented May 8, 2021

@fsharpasharp yes I would like to work on Bazel issues

@anandwana001
Copy link
Contributor

Assigning @fsharpasharp to confirm and merge the PR if it's good to go.

@fsharpasharp fsharpasharp removed the PR don't merge - NEEDS UPDATE Corresponds to PRs that need to be updated with the latest develop changes before they can be merged label May 10, 2021
@fsharpasharp
Copy link
Contributor

Looks good to me @anandwana001. I don't think I'm able to merge though.

@anandwana001
Copy link
Contributor

Looks like few tests are failing, should I merge PR with these failure?

@fsharpasharp
Copy link
Contributor

Looks like few tests are failing, should I merge PR with these failure?

Yes, I think we can merge the PR with the failure.

@anandwana001 anandwana001 merged commit 7a97e50 into oppia:develop May 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create a BUILD.bazel file for the logging package in the utility module
6 participants