Skip to content

Remove log renamings of tracing crate #74747

Closed

Description

@oli-obk

In #74726 I made a dependency import hack to reduce the diff size. We should replace all of these imports with tracing = "0.1" and then adjust the crate source by replacing all uses of log imports with tracing import.

Ideally only a few of these are done at a time to keep conflicts at a minimum and get such PRs merged fast.

Note: do not start working on this until #74726 is merged.

Activity

  1. added
    E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
    on Jul 25, 2020
  2. added
    C-cleanupCategory: PRs that clean code up or issues documenting cleanup.
    on Jul 25, 2020
  3. added
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on Jul 25, 2020
  4. changed the title [-]Remove from `log` renaming of `tracing` crate[/-] [+]Remove `log` renamings of `tracing` crate[/+] on Jul 25, 2020
  5. bishtpawan commented on Jul 26, 2020

    @bishtpawan
    Contributor

    Hi @oli-obk I saw your PR of (#74726 ) where you have replaced log="0.4" to log = { package = "tracing", version = "0.1" } and in this issue, you have mentioned like we have to replace all log imports to tracing imports. My question here is when you have already changed the package from log to tracing so now what left in it because the import name cannot be changed in files if we have used log as a crate name in Cargo.toml?
    Do we need to replace the name of dependency from log to tracing then we'll clean up the code by replacing the log imports with tracing imports in the corresponding files? Or is there anything else you want?

    Thanks,
    Waiting for your response.

  6. oli-obk commented on Jul 26, 2020

    @oli-obk
    ContributorAuthor

    Do we need to replace the name of dependency from log to tracing then we'll clean up the code by replacing the log imports with tracing imports in the corresponding files? Or is there anything else you want?

    Yes, that's exactly it. Replace log = { package = "tracing", version = "0.1" } with tracing = "0.1" and then fix up the errors by changing the import names. Note that the PR isn't merged yet, so this issue is not yet actionable.

  7. bishtpawan commented on Jul 26, 2020

    @bishtpawan
    Contributor

    Thanks for the response. Yes, I'm waiting for your PR to be merged first.

  8. georgio commented on Jul 31, 2020

    @georgio
    Contributor

    I would like to give this a shot when #74726 is merged

  9. oli-obk commented on Jul 31, 2020

    @oli-obk
    ContributorAuthor

    Once the PR is merged, before you work on anything, please post here which libs you are going to work on so that you don't conflict with others who are doing the same

  10. pawanbisht62 commented on Aug 1, 2020

    @pawanbisht62
    Contributor

    As they are independent, we can make changes on multiple files right? If yes then I'll work on following libs

    • librustc_ast_lowering
    • librustc_ast_passes
    • librustc_ast_pretty
    • librustc_builtin_macros
    • librustc_codegen_llvm
    • librustc_codegen_ssa
    • librustc_data_structures)
      After that will pick new libs accordingly if we will left with some.
      Thanks
  11. gdhuper commented on Aug 2, 2020

    @gdhuper
    Contributor

    If no one else is planning on tackling the following:

    • librustc_session
    • librustc_span
    • librustc_symbol_mangling
    • librustc_target
    • librustc_trait_selection
    • librustc_traits
    • librustc_ty
    • librustc_typeck
    • compiletest
      I would like to take a stab. Thanks
  12. georgio commented on Aug 2, 2020

    @georgio
    Contributor

    I could take care of the remaining files:

    • librustc_ast
    • librustc_data_structures
    • librustc_driver
    • librustc_errors
    • librustc_expand
    • librustc_hir
    • librustc_incremental
    • librustc_infer
    • librustc_interface
    • librustc_lint
    • librustc_metadata
    • librustc_middle
    • librustc_mir
    • librustc_mir_build
    • librustc_parse
    • librustc_passes
    • librustc_privacy
    • librustc_query_system
    • librustc_resolve
    • librustc_save_analysis
  13. added a commit that references this issue on Aug 2, 2020
  14. georgio commented on Aug 4, 2020

    @georgio
    Contributor

    Hey everyone, I would like to apologize for not being able to carry this through at the moment. My country was rocked by a massive explosion and I have to be on the ground to help. I wouldn't mind getting back to this as soon as things calm down a bit but if you're short on time I would suggest that someone else takes care of my part of the issue.

  15. gdhuper commented on Aug 4, 2020

    @gdhuper
    Contributor

    Hey everyone, I would like to apologize for not being able to carry this through at the moment. My country was rocked by a massive explosion and I have to be on the ground to help. I wouldn't mind getting back to this as soon as things calm down a bit but if you're short on time I would suggest that someone else takes care of my part of the issue.

    Hey @georgio, so sorry to hear that. I can take care of the rest.

  16. georgio commented on Aug 5, 2020

    @georgio
    Contributor

    @gdhuper thank you very much. I really appreciate it.

  17. CloudNClock commented on Aug 5, 2020

    @CloudNClock

    I will take care of librustdoc, then every task is claimed if I am not mistaken.
    Stay safe.

    It seems librustdoc has been updated already.

  18. added a commit that references this issue on Aug 15, 2020
    9b88e0a
  19. pawanbisht62 commented on Aug 16, 2020

    @pawanbisht62
    Contributor

    @bors can you please look at the PR #75187 as it is related to this issue and still in open state. Thanks

  20. oli-obk commented on Aug 17, 2020

    @oli-obk
    ContributorAuthor

    @pawanbisht62 bors is a bot, You can just post messages like the one you did in this issue without pinging it. We just need to ping it when giving it commands to merge PRs

  21. added a commit that references this issue on Aug 17, 2020
  22. oli-obk commented on Aug 26, 2020

    @oli-obk
    ContributorAuthor

    I think we solved all of these

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-cleanupCategory: PRs that clean code up or issues documenting cleanup.E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions