Positive Feedback ❤

Everyone loves to read positive feedback; feel free to use this issue as a place to jot down the things you enjoy about Zed.  If you want to give permission to the Zed team to use your comment in promotional content (Zed Twitter, zed.dev, etc.), place a 🚀 reaction on your post.

one thing that has really annoyed me in vs code or intellij is that accepting a code completion while the cursor is mid word will insert the whole suggestion there and ruin the whole idea of completion. To get a better idea of what I mean, see this:
https://user-images.githubusercontent.com/27063113/175758575-77a40c03-ff4d-45c8-a5c3-d8e1291916fc.mov
I love that zed is smarter and completes the word correctly.

I enjoy how response Zed is to every keystroke - taking notes in Zed is super satisfying.

Lovely. Feels really smooth. What font is it that you package with the editor? Looks awesome.

Lovely. Feels really smooth. What font is it that you package with the editor? Looks awesome.

Pretty sure it is a custom font called Zed Mono, it is basically just a custom configuration of Iosevka.

With Zed, writing code is an absolute pleasure. Its snappy interactions and lean UI help me focus on bringing ideas into reality. Having an editor that doesn't get in your way feels like having superpowers - it's like having a thin layer between my brain and the computer.
Discovering the journal was also mind-blowing; now, I have one reason less to switch away from the editor, which massively helps battle context-switching.
I almost entirely switched from VSCode to Zed in the past few weeks. I can use Zed for everything, but I still rely on VSCode for a few nits:

Terraform (and HCL) integration
Deep git integration (i.e. GitLens)

Startup-speed and LSP's responsiveness are simply amazing and since I am a sucker for looks, I'd also like to give props for making it look and feel so polished already! (including the nice little touch with rounding selected area highlights). Love that it's not forcing me to open a "project" so I can just open random files.
Totally brilliant implementation of project-wide search with live-edit; truly sweet.

The speed is honestly amazing. I don't really use macOS and the only machine I have is really rather slow (2014 vintage mac mini). Atom or VSCodium take sometimes >30s to load, Zed pops up in less than 5.

Just getting started with Zed. First impressions are that my other editors are crazy slow :-). The outline is a killer feature (and also surprisingly fast). Thanks!

It's still early days using Zed for me, but I love it so much!! You've got a fan in me 🚀

Another feedback from me: the new release fixing the input method for international keyboards is amazing. Working fine for me with US-International layout, thank you for this!

To me the multi-buffer editing and symbol renaming features are already SO great that I switch to Zed any time I need to refactor code.

From rkusa on Discord:

Just wanted to drop a quick: Excellent job Zed team!
I've successfully used Zed for the whole week as my main editor without any major issue (just some smaller UX things for which there are already issues on Github). Way quicker than VSCode, and better LSP and more stable than Sublime Text – exactly what I was waiting for. It definitely sparks joy - so I am personally ready to move my Sublime subscription over to Zed when you are 😉

So fast 💚

Thank you. Finally somebody has created a Text Editor where you can go back when I use go to definition

Just gave it a test run today. I really like the floating terminal window. And vim keybindings are also very welcomed. Great job!

I've seen these points mentioned in other comments, but I figured I would point them out nevertheless, as a reinforced positive note for the team 😄
I've tried multiple IDEs/text editors in the recent months because I wasn't happy with any of them and just kept hopping between the alternatives. Some of them fully fledged IDEs (e.g. JetBrains line-up) where I always feel like they are a bit too sluggish for my taste. Other, more lightweight alternatives, usually suffer from the fact that they are fast until you install the plugins you need to get a decent experience (hopefully Zed will not fall into this category).
Zed is very fast, I mean the input delay from keystroke to display is pretty impressive (not like I measured it, just from a feel perspective). Furthermore, it was smart and pragmatic to inherit a bunch of shortcuts from already existing editors, my learning curve was minimal when jumping from something like VS Code to Zed.
And last but not least, the UI is just clean and minimal. It does not have a lot going on, which to be honest, I enjoy; it helps focus on the code itself.
All in all amazing job.
(I don't think it matters, but I mostly used it for Go development)

lightning fast⚡great job!

Just wanted to say (as I’m filing issues here and there) that my first impressions were very good. I can’t quite use this for my daily driver yet—I spend too much time using Code as a debugger and not just a text editor—but it’s close to being a replacement for how I use Sublime: as a super fast and lightweight editor that I use for Git commits, quick example code, writing, etc. Keep up the good work!

Dang, Zed is really fast. Also, the golang language server integration is top notch. I liked how it showed me every changed instance and how fast it ran.

Want to try zed, but still in waitlist, is there someone can invite me?

https://zed.dev/invites/RZQYuVtW-cHunS8f

@evolify - let me know when you get your invite copied - going to remove these comments after to keep this thread clean for just positive feedback.  Feel free to join the Discord after you are in :)

@evolify - let me know when you get your invite copied - going to remove these comments after to keep this thread clean for just positive feedback.  Feel free to join the Discord after you are in :)

Sorry for polluting this issue even more, but where I can get the discord invite?

No worries

Log into your zed.dev account
Docs > Welcome (link should be here)

@evolify - let me know when you get your invite copied - going to remove these comments after to keep this thread clean for just positive feedback. Feel free to join the Discord after you are in :)

Got it, thank you!

Zed is:
Smooth
Clean
Beautiful
...
Less is More, I love zed's style
Thank you.

Opened up and edited a 50,000 line CSV file today. Helix choked when saving and didn't feel great in navigation. Zed didn't even hiccup at all, felt just as smooth as always. Searching was instant. Absolutely incredible!

Super editor!!! 🔥🔥🔥

Loving the speed. Reminds me of SublimeText which I love but had moved onto Visual Studio Code. And I have to say the unobtrusive UI is perfect and so refined. I love feeling like a kid in a candy story every time I open this app. Thank you!

Loving the speed. Reminds me of SublimeText which I love but had moved onto Visual Studio Code. And I have to say the unobtrusive UI is perfect and so refined. I love feeling like a kid in a candy story every time I open this app. Thank you!

Zed is as fast as Notepad using much less memory usage. Also, Zed opens faster than TextEdit, which makes me happy every time I start coding

Hi! First of all, thanks for sending an invite to test this awesome piece of software. I was (and still am) big fan of atom and was using it before "moved" to zed. Zed (obviously) much faster, responsive, with similar but much more simplified design. Even though, I expected super basic set of features out of the box like project browser, basic syntax highlighting with command-palette and file search and was super impressed when realised that there was a great work done in terms of code & definition navigation, cursor features etc. Not to mention language-related support (e.g. typescript) which you typically would expect after installing specific plugins/packages. Have not yet tested collaborative coding yet, which I am sure is a separate world on its own. 🚀

Hi all, I've been using Zed for a few weeks now and wanted to say thank you! 🙏 This is hands down the best IDE I've ever used and has been a major productivity booster. It strips away all of the flashy stuff that can distract you in the popular IDEs and gives you the tools you need to just focus and get stuff done. I've always wanted to go down the vim path, but it requires way too much time/setup/frustration and I always end up bailing after a while. Zed has exceeded my expectations for what I was looking for in my dream vim setup, and it's all out of the box - this is easy mode!
A couple of highlights from the past few weeks:

The Zed team is amazingly helpful and responsive!
This editor is insanely fast, even in collaboration mode which makes the experience a lot more fun/smooth
Collaboration mode is super easy, love the contacts feature
It sounds like there are some awesome collaboration changes in the pipeline 😎

I really lost all hope when atom was discontinued... but thanks to zed the sun is shining again!
I've fiddled around with it for a few hours now and there are many things to praise, eg. the way it lets me close tags when I want to close them or the cmd d option. It really lets me type the way I think. But most important of all in my opinion, is that it looks beautiful! After all, code editors are the things I stare at most of my waking hours. Thanks to zed, this is a pleasant experience :) please keep it up!

zed - fire!

Zed is my new favorite editor. I have been a Sublime Text user for 10 years. I invested lots of time to make my own theme/colorscheme that minimal and look closely to Atom's One theme. I didn't have to do the same with Zed.
One of the most satisfied feature is the keybinding is the same as Sublime Text ootb, so I don't have to relearn anything.
This is god blessing.

I am a big fan. I love how responsive and quick it is. Absolutely becoming my go-to and I'm looking forward to experiencing its growth

The first impression of the editor is fantastic. Love the speed and number of features available.

I've followed the development of Zed for a while now. It's amazing how quickly you all ship awesome stuff. Zed is so fast that I often write prose in it because it feels so good. I use it on airplanes because it doesn't drain my battery. It has most of the features I need while feeling clean and minimalistic. I learned zero new keybindings because everything already works the way I expect. 👏 👏 👏 👏

I'm delighted to try out Zed. It worked out of the box for me with rust-analyzer, all the defaults and keys seem sane to me. And most importantly - blazingly fast, even faster than Sublime Text. Worked with Zed a few days so far, got zero crashes or bugs, even though this is not a publicly released product. Amazing job, team! I hope you'll find a way to make this project sustainable (and would be willing to do my part, too). 🚀

Thanks for giving me alpha access 🙌  so far I love it, already becoming my new favourite editor 🔥 🚀 , the speed and the overall design are fantastic, opens large and navigates files in a flash, amazing work team 👏 👏 . Like a few others mentioned it feels a lot like Sublime Text in a good way, seems like a lot potential excited to see the project mature

Zed looks like the culmination of my dreams when it comes to a code editor! Glad the authors have a similar opinion on the performance of critical parts of the editor and the minimalist design. So far I have try many editors:

Nova from Panic. Excellent, native editor, but it is developed by one person - so it is full of smaller errors that spoil the workflow as a whole. In addition, the whole thing looks like a Christmas tree so it's hard to focus on the code, because everything around is colorful. Themes from extensions do not help, because most of them have poor quality and do not replace (because they can not), for example, colored icons.
VSCode - my current choice, on which I am literally forced to work, because it is the most "universal". It has its drawbacks - like poor speed in some scenarios and sometimes an illegible interface (lower and right panel), but thanks to the possibility of personalization you can very easy to simplify the appearance and adapt to your needs.
Sublime Text 4. It has strange problems with JSX syntax (e.g. hotkey commenting in some cases does not work or inserts // instead of {/**/}). Besides, I miss a bit of a clear and specific editor development (updates actually add nothing but some nonsense under the hood).
PHPstorm. Big, heavy IDE. On the one hand, it's perfectly "understands" and suggests syntax, on the other hand, this suggestions can be slow, and loading a more complex project takes centuries (even on strong device).

I have also used several editors that are still in the alpha/beta phase, but they are either just curiosities, or I doubt that they will ever leave the testing phase.
Zed has already stolen my heart and once the stable version comes out even if I don't use the remote collaboration feature, I'd love to add a few cents away every month to support development!

Great job y'all! I'm a sublime user and this looks like a potential worthy successor. I'll need Svelte support before I can use it as my daily driver but really like what I'm seeing so far. Would also like to see more theme support.

Just used this for the first time ten seconds ago-- innocuous remark, but I'm really surprised and impressed by how snappy it feels and how immediately the LSP config stuff I've so far seen is out-of-the-box flawless. Actually gonna use this for a few days for real and see how it goes. Nice.

i mainly write C++/Rust, and i used emacs before, sometimes vscode too. I heard Zed in emacs-china which says it's written in rust, so i tried.
Zed is very very fast, nowadays i wrote nearly all my c++/rust code in Zed.
I would like to buy/subscribe it in the future.

Love that it's extremely fast. It's able to detect libraries I'm importing and give me responsive help for documentation on what attributes are available for me and on how those attributes should be used.

I can't believe how efficient Zed is. 👏
I can write for hours without significantly impacting energy or memory resources. Navigating through code is so snappy that creativity just flows and I can open large files instantly.
While with VS Code I always tended to quit the application to prevent draining my battery I left Zed running quietly in the background for a week now.
This is what a code editor should be: lightweight, responsive, and without the bloat.

Absolutely lovely!  👏🏾
I'll be watching for a few things to come to speed in VIM mode, and look forward to replacing vscode.  Amazing piece of work.  Not from a critical view but more curiosity about the design process, I'd love to understand what drove the apparent decision to rebuild the VIM stuff rather than embedding neovim like vscode did.
Thanks for this, looking forward to watching it grow!

I've been through a lot of Mac editors - vscode, Atom, Brackets, Nova, *Storm, and none have had sensible out of the box defaults and performance where I could just get started with minimal configuration.
Super excited to see where this goes!
Once there's eslint / prettier integration, it’ll be 👌🏼, but incredibly usable and responsive as is. Kudos!

The output performance of the built-in terminal is amazing. Even 2 times faster than Kitty on my machine!

I'll echo the many comments praising the responsiveness of all elements of the UI, from typing to the appearance of completions and diagnostics to file navigation. With a built-in terminal, it's got just about everything I want from an editor.

I've been using Zed as my daily driver for 3 weeks now, and I'm convinced I'll never go back to vsCode. The boost in productivity from the performance, clean UI and instant code pairing is unmatched! Considering this is only in alpha, I'm really excited for the future of Zed!

It is incredible how usable it already is as a daily driver for web development (TS, React) even in the Alpha/Beta stages. Great work! And of course it is super snappy as everybody said already :)

Thanks for adding Command+N for opening new windows when none were open. Appreciate that!

Once there's eslint / prettier integration, it’ll be 👌🏼, but incredibly usable and responsive as is. Kudos!

ditto. that I've been using the Atom Dark (not One Dark) theme with a monokai flavor for eons now and eagerly awaiting the ability to use it in Zed

I've been hopping back and forth between vim and vscode for a long time, and I feel like zed is just what I've been looking for. A fast gui editor with built-in support for vim motions.

My other editor was lagging so much and it seemed to get worse every day no matter what I did. Seeing how fast Zed was convinced we to switch instantly.
Having access to project wide Typescript diagnostics was another key feature that really made the switch easy. This had been a pain point in other alternatives I had tried.
Super happy so far!

Zed is easily the smoothest scrolling editor in existence at 120hz on my MPB.

Looking out how Zed is getting build, I know it hasen't yet all things I need, but already is so hard to look back and feel how VS Code lags my Flow. Zed is an upgrade of the experience 🍄

I've added a few feature requests and bug reports already but only because I'm extremely excited about Zed.
I was a Sublime Text user for years, then switched to VSCode because it had features I needed that ST just didn't support, primarily LSP/Elixir stuff. I wanted an editor that was a text editor with a little light "IDE" added to it. It was a definite step down in terms of speed.
Here are some things I'm loving about Zed:

My god it is so fast. Boot time, UI interaction, typing latency. I feel it. It's like the experience of switching from iTerm to Kitty but times a thousand. I knew VSCode always felt sluggish, but I didn't realize how good things could really be. I'm honestly astounded.
Even with a few beta bugs I'm finding it's still got a feeling of being very polished. This makes me really excited about the future. If it feels this good now I can't imagine how great it'll feel at the 1.0 release.
I know you're planning to charge for collab features and make this editor free (IIRC?), but know that I would absolutely pay for it especially if it helps ensure long term active development of Zed well into the future.
I really like that it's fairly minimal. VSCode has become this beast of an editor and it's overwhelming (and slow), I don't need everything it does (I'm glad it's there for people that do!). So far Zed feels closer to Sublime Text, but faster, and with the extra stuff I need to do my job well. I hope that spirit continues, it seems like it will.
This treesitter stuff is awesome. The first time I pressed alt-up I said "whoa" out loud.
I also love the outline view.
Thanks so much for the Elixir and LSP support! I filed a bug that's blocking some people but I managed to hack together a little workaround and it's working well. Excited to try it on the truly massive codebase I work on during my day job next week, that'll be the real test of Zed and the Elixir LSP integration :D I'm optimistic.

My enthusiasm might seem excessive, but I've been waiting years for something better to come along. I've tried a dozen editors over that time in various states of completion waiting for one that felt just right, and even in beta Zed seriously feels like that editor.
That's it for now, thanks to all the Zed folks for your hard work.
Also glad this ticket exists! I always hate filing bugs without having the chance to talk about how much I like the project!

Well done Zed team🚀🚀 What I absolutely love about Zed is that there is no bloat in UI👌, like in VSCode icons everywhere. It is clean and responsive and could be even cleaner like my SublimeText. But that's a matter of taste. Also appreciate VIM modal navigation. Not perfect but we are getting there!! 💪💪 project overview 👌 go to definition 👌

Hello, :wave:. I am a long-time lurker and first-time user. I've been using Zed for about two weeks now and enjoy how clean and responsive it is. I love how most things just work.
I appreciate how frequently the updates are coming out. Each one of them is packed with functionality. Thank you for the great editor.

Why would you want to quit Zed?

@markthomasmiller just to update to new version

Thanks for adding the various text transformations to 0.99.1. They are awesome.

I'm really impressed by the rate of improvement of Zed. The input lag (or lack thereof) is excellent, the vim mode is drastically improved and clearly cared for, and I feel a confidence that improvements will continue to be prioritized based on community feedback, which is neat.
Also wanted to say thank you for allowing people to keep their editors as simple as desired (the settings option to disable Copilot integration, among others), while having a sane default for most languages that feels automatically good without configuration.
Cheers to the devs for making a truly viable and opinionated (in a good way) editor that holds its own.

Super great how you guys have opened up the issue list and are open to input and feedback! I can't wait for linux support and I can start using it. VScode and idea suite tools are memory hogs and extremely slow... can't wait for the responsiveness and light-weight experience that zed will deliver.

Same for me but waiting for the windows build, I use vscode all the time but it eats up performance and makes doing more than two things at once difficult. Love the clean design and aesthetic, and I can’t wait to be able to try it out!

I'm been using zed as my daily driver for a while now, the rate of improvement is quite impressive :)  ⭐
Keep up the good work!

A very good beginning. I am waiting to fix some critical issues like #340 to try zed instead of vscode. Also wouldn't mind buying a subscription even for personal use if it would speed up the product development.


Roadmap for Atlassian provisioning connector and its support model

I am exploring Atlassian provisioning connector in Azure AD, and in portal it say connector is in preview. I could not find when this connector will be GA released? I am using this connector from my Azure AD tenant for user provisioning onto Atlassian cloud.
Is this something you can help me?
Official guide - https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/atlassian-cloud-provisioning-tutorial

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 04509836-867e-279f-c1d6-135a237d357e
Version Independent ID: e05a10ce-c46b-334e-78e2-30b416ed904a
Content: Tutorial: Configure Atlassian Cloud for automatic user provisioning with Azure Active Directory
Content Source: articles/active-directory/saas-apps/atlassian-cloud-provisioning-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @zhchia
Microsoft Alias: jeedes

@gaurav1264 Thank you for your feedback . We will investigate and update the thread .

Hello @gaurav1264 , I am working with product team to get more insight. Kindly allow us sometime, will let you know as soon as have an update form team. Thank you for your time and patience.

Hello @gaurav1264 ,
Our Product group still working with vendor on this plan to GA some of these connectors. we don’t have the first dates of GA release at this time but once I have I will communicate with you.  Thanks!
Archiving for now : #please-close

Thanks @ssabat, One more query - Where to raise feature/ bug request in regards to this connector?

@ssabat Is there a possibility you see where vendor can never make GA release for this provisioning connector? This is very crucial for us to decide on Azure AD integration with Atlassian cloud.


Fully internationalize the widget

We still have a few Alerts which are in English such as "Uploading", "Text Copied to Clipboard", etc. These should be added to the options.

I've marked them as TODO in the library, so it should be easy to see what still needs to be done.

Working on this


Cqpss temp files

Fixes temp file issueby posting all the files to the server (#100)  and cleaning out tmp folder . Also means that the cqparts-server can be on a remote server.

Will have a look tonight.

Good catch , didn't even test it properly. (derp).
Merge Away !

Bam! :boom: tested... :sunglasses:
Merging.
Thanks again for the contribution @zignig , you're on fire :fire:

Thanks , more to come. the cqparts-server is taking shape too.


refactor(WEG-76 & WEG-80): Make labels hoverable and non interactive in individual view

:tada: This PR is included in version 1.0.0-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


last-working-dir plug-in causes unexpected behavior in Emacs

If you enable last-working-dir, shell commands in Emacs are executed in the directory stored in $cache_file rather than in the directory of the current file. So if you run (shell-command "pwd") in Emacs, it'll return the directory stored in $cache_file regardless of what file is open in Emacs.
This breaks packages that rely on shell commands' being run in the same directory as the current file. For example, an Emacs package called Projectile has a command for searching for files by filename in the current Git project. If you run this command with last-working-dir enabled, it will search the Git project associated with whatever path is in $cache-file. (It will produce an error if there's no associated project.) More details here
There might not be any easy way of fixing this issue, but I think it would be helpful to include a warning, either in a new README or a source-code comment.
This is similar to #3999.

Check out #5471, +1 it if it fixes your problem.

My understanding is that it would fix the problem unless I'm using a file in the root of the home directory. Is this correct? If so, it would probably make the plug-in usable again, though it could still cause unexpected behavior among unsuspecting users.

That's exactly the behavior. I've documented that as a README so hopefully users will understand that. I'm not aware of any other heuristic we can use, so for now this should fix most of the problems.


Finalize move to Github Actions

Update releases
Update description based on run link to tag
Update github badge (from travis)

Completed badge move in STATUS.md

Completed badge move in STATUS.md


Chore/doc filter create methods

Description of Change

Issues Resolved

closes #

Testing Procedure

PR Checklist
Did you remember to do the below?

[ ] Add unit tests to verify this change
[ ] Add an entry to CHANGELOG.md describing this change
[ ] Add docstrings for any new public parameters / methods / classes

@alanag13 Created this draft PR to have a view at a GUI diffs, it probably is not quite near ready for feedback yet


Are all of the undefs we use really necessary?

Verification

[x] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
As part of the Sorbet work, I went through and commented every file that uses undef so that others don't waste their time trying to make it typed: strict (because Sorbet doesn't support undef).
Carlo commented, wisely, that maybe we don't need to have the undefs anymore.
We should investigate this and remove any unnecessary undefs.
The files are:

[ ] Library/Homebrew/cli/args.rb
[ ] Library/Homebrew/dev-cmd/extract.rb
[ ] Library/Homebrew/extend/os/linux/cleanup.rb
[ ] Library/Homebrew/extend/os/linux/dependency_collector.rb
[ ] Library/Homebrew/extend/os/linux/diagnostic.rb
[ ] Library/Homebrew/extend/os/linux/formula.rb
[ ] Library/Homebrew/extend/os/linux/formula_installer.rb
[ ] Library/Homebrew/extend/os/linux/keg.rb
[ ] Library/Homebrew/extend/os/linux/parser.rb
[ ] Library/Homebrew/extend/os/linux/simulate_system.rb
[ ] Library/Homebrew/extend/os/mac/cleaner.rb
[ ] Library/Homebrew/extend/os/mac/cleanup.rb
[ ] Library/Homebrew/extend/os/mac/dependency_collector.rb
[ ] Library/Homebrew/extend/os/mac/dev-cmd/bottle.rb
[ ] Library/Homebrew/extend/os/mac/development_tools.rb
[ ] Library/Homebrew/extend/os/mac/diagnostic.rb
[ ] Library/Homebrew/extend/os/mac/extend/ENV/std.rb
[ ] Library/Homebrew/extend/os/mac/extend/ENV/super.rb
[ ] Library/Homebrew/extend/os/mac/formula.rb
[ ] Library/Homebrew/extend/os/mac/formula_installer.rb
[ ] Library/Homebrew/extend/os/mac/hardware/cpu.rb
[ ] Library/Homebrew/extend/os/mac/keg.rb
[ ] Library/Homebrew/extend/os/mac/keg_relocate.rb
[ ] Library/Homebrew/extend/os/mac/linkage_checker.rb
[ ] Library/Homebrew/extend/os/mac/readall.rb
[ ] Library/Homebrew/extend/os/mac/simulate_system.rb
[ ] Library/Homebrew/extend/os/mac/system_config.rb
[ ] Library/Homebrew/ignorable.rb

What is the motivation for the feature?
Reducing unnecessary code. Improving Sorbet coverage eventually maybe.
How will the feature be relevant to at least 90% of Homebrew users?
It won't be.
What alternatives to the feature have been considered?
Keeping them even though they may not be needed.

Change the value of HOMEBREW_RUBY_WARNINGS to (I can't remember which) -W1 or -W0.
The undef are/were necessary because we're redefining methods which produced/produce warnings.
There was a previous goal to get rid of these warnings.

You answered a question I didn't even know I had (yet): how do I actually check for these being unused. Thanks!

$ HOMEBREW_RUBY_WARNINGS="-W2" brew info wget
/opt/homebrew/Library/Homebrew/extend/os/mac/hardware/cpu.rb:38: warning: method redefined; discarding old in_rosetta2?
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of in_rosetta2? was here
/opt/homebrew/Library/Homebrew/extend/os/mac/hardware/cpu.rb:92: warning: method redefined; discarding old virtualized?
/opt/homebrew/Library/Homebrew/hardware.rb:163: warning: previous definition of virtualized? was here
/opt/homebrew/Library/Homebrew/extend/pathname.rb:235: warning: method redefined; discarding old extname
/opt/homebrew/Library/Homebrew/extend/pathname.rb:507: warning: method redefined; discarding old rmtree
/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/pathname.rb:598: warning: previous definition of rmtree was here
<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/cli/parser.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:50:in  `<main>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cli/parser.rb:4:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/abstract_command.rb:4:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

/opt/homebrew/Library/Homebrew/extend/os/mac/development_tools.rb:64: warning: method redefined; discarding old installation_instructions
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of installation_instructions was here
/opt/homebrew/Library/Homebrew/extend/os/mac/development_tools.rb:69: warning: method redefined; discarding old custom_installation_instructions
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of custom_installation_instructions was here
<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/cask/cask_loader.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:6:in  `<top (required)>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:8:in  `<module:Homebrew>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:9:in  `<module:MissingFormula>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:198:in  `singleton class'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/os/missing_formula.rb:4:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/os/mac/missing_formula.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/cask_loader.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/cask.rb:6:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/cask/cask.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:6:in  `<top (required)>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:8:in  `<module:Homebrew>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:9:in  `<module:MissingFormula>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:198:in  `singleton class'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/os/missing_formula.rb:4:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/os/mac/missing_formula.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/cask_loader.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/cask.rb:8:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/dsl.rb:7:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/livecheck.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

/opt/homebrew/Library/Homebrew/extend/os/mac/missing_formula.rb:24: warning: method redefined; discarding old cask_reason
/opt/homebrew/Library/Homebrew/missing_formula.rb:194: warning: previous definition of cask_reason was here
/opt/homebrew/Library/Homebrew/extend/os/mac/missing_formula.rb:31: warning: method redefined; discarding old suggest_command
/opt/homebrew/Library/Homebrew/missing_formula.rb:196: warning: previous definition of suggest_command was here
/opt/homebrew/Library/Homebrew/extend/os/mac/formula_support.rb:6: warning: method redefined; discarding old applicable?
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of applicable? was here
/opt/homebrew/Library/Homebrew/extend/os/mac/keg.rb:33: warning: method redefined; discarding old codesign_patched_binary
/opt/homebrew/Library/Homebrew/keg.rb:548: warning: previous definition of codesign_patched_binary was here
<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/formula.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:8:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/formula.rb:28:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/linkage_checker.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/formula.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:8:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/formula.rb:29:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/ENV.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/diagnostic.rb:6:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/extend/ENV.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:8:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/formula.rb:29:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/ENV.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/diagnostic.rb:11:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/system_config.rb:7:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

/opt/homebrew/Library/Homebrew/extend/os/mac/system_config.rb:32: warning: method redefined; discarding old core_tap_config
/opt/homebrew/Library/Homebrew/system_config.rb:136: warning: previous definition of core_tap_config was here
/opt/homebrew/Library/Homebrew/extend/os/mac/extend/ENV/super.rb:7: warning: method redefined; discarding old shims_path
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of shims_path was here
/opt/homebrew/Library/Homebrew/extend/os/mac/language/java.rb:6: warning: method redefined; discarding old java_home
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of java_home was here
==> wget: stable 1.24.5 (bottled), HEAD
Internet file retriever
https://www.gnu.org/software/wget/
Installed
/opt/homebrew/Cellar/wget/1.24.5 (92 files, 4.5MB) *
  Poured from bottle using the formulae.brew.sh API on 2024-07-04 at 10:26:26
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/w/wget.rb
License: GPL-3.0-or-later
==> Dependencies
Build: pkg-config ✔
Required: libidn2 ✔, openssl@3 ✔, gettext ✔, libunistring ✔
==> Options
--HEAD
	Install HEAD version
==> Analytics
install: 74,368 (30 days), 265,276 (90 days), 1,001,763 (365 days)
install-on-request: 74,218 (30 days), 264,636 (90 days), 999,749 (365 days)
build-error: 9 (30 days)
mikebook # HOMEBREW_RUBY_WARNINGS="-W2" brew info wget
/opt/homebrew/Library/Homebrew/extend/os/mac/hardware/cpu.rb:38: warning: method redefined; discarding old in_rosetta2?
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of in_rosetta2? was here
/opt/homebrew/Library/Homebrew/extend/os/mac/hardware/cpu.rb:92: warning: method redefined; discarding old virtualized?
/opt/homebrew/Library/Homebrew/hardware.rb:163: warning: previous definition of virtualized? was here
/opt/homebrew/Library/Homebrew/extend/pathname.rb:235: warning: method redefined; discarding old extname
/opt/homebrew/Library/Homebrew/extend/pathname.rb:507: warning: method redefined; discarding old rmtree
/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/pathname.rb:598: warning: previous definition of rmtree was here
<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/cli/parser.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:50:in  `<main>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cli/parser.rb:4:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/abstract_command.rb:4:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

/opt/homebrew/Library/Homebrew/extend/os/mac/development_tools.rb:64: warning: method redefined; discarding old installation_instructions
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of installation_instructions was here
/opt/homebrew/Library/Homebrew/extend/os/mac/development_tools.rb:69: warning: method redefined; discarding old custom_installation_instructions
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of custom_installation_instructions was here
<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/cask/cask_loader.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:6:in  `<top (required)>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:8:in  `<module:Homebrew>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:9:in  `<module:MissingFormula>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:198:in  `singleton class'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/os/missing_formula.rb:4:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/os/mac/missing_formula.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/cask_loader.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/cask.rb:6:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/cask/cask.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:6:in  `<top (required)>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:8:in  `<module:Homebrew>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:9:in  `<module:MissingFormula>'
	from /opt/homebrew/Library/Homebrew/missing_formula.rb:198:in  `singleton class'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/os/missing_formula.rb:4:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/os/mac/missing_formula.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/cask_loader.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/cask.rb:8:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cask/dsl.rb:7:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/livecheck.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

/opt/homebrew/Library/Homebrew/extend/os/mac/missing_formula.rb:24: warning: method redefined; discarding old cask_reason
/opt/homebrew/Library/Homebrew/missing_formula.rb:194: warning: previous definition of cask_reason was here
/opt/homebrew/Library/Homebrew/extend/os/mac/missing_formula.rb:31: warning: method redefined; discarding old suggest_command
/opt/homebrew/Library/Homebrew/missing_formula.rb:196: warning: previous definition of suggest_command was here
/opt/homebrew/Library/Homebrew/extend/os/mac/formula_support.rb:6: warning: method redefined; discarding old applicable?
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of applicable? was here
/opt/homebrew/Library/Homebrew/extend/os/mac/keg.rb:33: warning: method redefined; discarding old codesign_patched_binary
/opt/homebrew/Library/Homebrew/keg.rb:548: warning: previous definition of codesign_patched_binary was here
<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/formula.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:8:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/formula.rb:28:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/linkage_checker.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/formula.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:8:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/formula.rb:29:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/ENV.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/diagnostic.rb:6:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

<internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37: warning: loading in progress, circular require considered harmful - /opt/homebrew/Library/Homebrew/extend/ENV.rb
	from /opt/homebrew/Library/Homebrew/brew.rb:65:in  `<main>'
	from /opt/homebrew/Library/Homebrew/commands.rb:37:in  `valid_internal_cmd?'
	from /opt/homebrew/Library/Homebrew/extend/kernel.rb:11:in  `require?'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/cmd/info.rb:8:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/formula.rb:29:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/extend/ENV.rb:5:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/diagnostic.rb:11:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from /opt/homebrew/Library/Homebrew/system_config.rb:7:in  `<top (required)>'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'
	from <internal:/opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.4_1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in  `require'

/opt/homebrew/Library/Homebrew/extend/os/mac/system_config.rb:32: warning: method redefined; discarding old core_tap_config
/opt/homebrew/Library/Homebrew/system_config.rb:136: warning: previous definition of core_tap_config was here
/opt/homebrew/Library/Homebrew/extend/os/mac/extend/ENV/super.rb:7: warning: method redefined; discarding old shims_path
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of shims_path was here
/opt/homebrew/Library/Homebrew/extend/os/mac/language/java.rb:6: warning: method redefined; discarding old java_home
/opt/homebrew/Library/Homebrew/vendor/bundle/ruby/3.3.0/gems/sorbet-runtime-0.5.11514/lib/types/private/methods/_methods.rb:257: warning: previous definition of java_home was here
==> wget: stable 1.24.5 (bottled), HEAD
Internet file retriever
https://www.gnu.org/software/wget/
Installed
/opt/homebrew/Cellar/wget/1.24.5 (92 files, 4.5MB) *
  Poured from bottle using the formulae.brew.sh API on 2024-07-04 at 10:26:26
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/w/wget.rb
License: GPL-3.0-or-later
==> Dependencies
Build: pkg-config ✔
Required: libidn2 ✔, openssl@3 ✔, gettext ✔, libunistring ✔
==> Options
--HEAD
	Install HEAD version
==> Analytics
install: 74,368 (30 days), 265,276 (90 days), 1,001,763 (365 days)
install-on-request: 74,218 (30 days), 264,636 (90 days), 999,749 (365 days)
build-error: 9 (30 days)

It's unclear to me what the "right"/Sorbet-friendly way to do this is. CC @dduugg for thoughts.

Here's how Sorbet deals with it:
https://github.com/sorbet/sorbet/issues/1150
https://github.com/sorbet/sorbet/pull/1266

I'm so honored someone asked! I haven't been a fan of how we do OS-specific code, and I would be curious to hear about how we landed there. (I wasted hours in confusion before I caught on, not realizing that methods may be dynamically redefined based on the OS.)
Using Cleaner as an example, how do folks feel about something like this? (It's a breaking change, but it could be written in a backward-compatible manner).
Also, is there a reason we're reluctant to do OS checks within methods? Feels like an over-optimization to avoid them (it should be plenty fast, though we should be able to cache the result). This seems ~fine to me:
sig { params(path: Pathname).returns(T::Boolean) }
def executable_path?(path)
  if OS.mac?
    path.mach_o_executable? || path.text_executable?
  elsif OS.linux?
    path.elf? || path.text_executable?
  else
    path.text_executable? || path.executable?
  end
end

Also, I'm a bit reluctant to mention this option, but since the sorbet error is well-scoped, we could suppress it in the sorbet config. (Sorbet won't delete the method from its model, which is ~fine, as we use it to replace defs.)

Using Cleaner as an example, how do folks feel about something like this? (It's a breaking change, but it could be written in a backward-compatible manner).

I'd be game to try something like this.

Also, is there a reason we're reluctant to do OS checks within methods?

I think the reason has to do with readability -- littering OS.mac? or OS.linux? all over the place can make the code unreadable. The existing way we handle OS-specific code is a bit like enforcing that you only get to call either of OS.mac? or OS.linux? once in any given method.

I haven't been a fan of how we do OS-specific code, and I would be curious to hear about how we landed there. (I wasted hours in confusion before I caught on, not realizing that methods may be dynamically redefined based on the OS.)

I'm a bit sympathetic to this. I think moving OS-specific code into separate files makes these methods harder to reason about (since you now need to have multiple files open to do this), and there was definitely a point where I had the same confusion you did. It also makes the source displayed on rubydoc.brew.sh pretty useless for some methods (example).

I'm not that big a fan of the existing platform-specific code organization approach either but I'm not aware of any better approaches. I wonder if it'd make sense to add some developer documentation about it so that it's more obvious for new contributors how it works assuming it doesn't already exist somewhere.

Using Cleaner as an example, how do folks feel about something like this? (It's a breaking change, but it could be written in a backward-compatible manner)

Am OK changing up the way things are but I'm not particularly a fan of a factory approach in Ruby.

I haven't been a fan of how we do OS-specific code, and I would be curious to hear about how we landed there.

I did much of the original cross-platform work in Homebrew/brew and decided on the approach that would be landed in Homebrew/brew when Linuxbrew merged in.
This was based on my work across several other open source projects and ~4 companies building and maintaining cross-platform software in a way that was maintainable in the longer-term.

Also, is there a reason we're reluctant to do OS checks within methods? Feels like an over-optimization to avoid them (it should be plenty fast, though we should be able to cache the result).

Yes:

I think the reason has to do with readability -- littering OS.mac? or OS.linux? all over the place can make the code unreadable. The existing way we handle OS-specific code is a bit like enforcing that you only get to call either of OS.mac? or OS.linux? once in any given method.

This is part of it. Another part of it is, if you're porting to a new OS in future (this is not hypothetical, I have an email in my inbox asking about porting Homebrew to Windows so this is timely 😁): being able to relatively easy tell "which parts of Homebrew already require cross-platform code" rather than "grep for OS.linux?/OS.mac? everywhere" is a much nicer solution.

I think moving OS-specific code into separate files makes these methods harder to reason about (since you now need to have multiple files open to do this), and there was definitely a point where I had the same confusion you did.

It also makes the source displayed on rubydoc.brew.sh pretty useless for some methods (example).

This would be good to address in RubyDoc. I don't think adjusting the code to improve the generated documentation makes sense.

Am OK changing up the way things are but I'm not particularly a fan of a factory approach in Ruby.

Same here. I strongly dislike it, sorry.
I would be game for something that maintains the file separation we have today while avoiding the need to undef as we do today.
I would ideally like us to lean harder into this approach and have fewer still/no OS.mac? or OS.linux? checks (or Homebrew::SimulateSystem.simulating_or_running_on_macos? or Homebrew::SimulateSystem.simulating_or_running_on_linux? checks which have sadly broken some of above rules) so that we can get a better indication still of what code is run on macOS, Linux, both, neither (the "generic" layer) by looking at the names of the code rather than having to look for specific if calls.

I wonder if it'd make sense to add some developer documentation about it so that it's more obvious for new contributors how it works assuming it doesn't already exist somewhere.

I'm game to do this if someone can suggest where they'd expect to find said documentation.
A "cross-platform code" section in docs.brew.sh for "Contributors"?

I'm game to do this if someone can suggest where they'd expect to find said documentation.
A "cross-platform code" section in docs.brew.sh for "Contributors"?

I don't imagine this to be helpful, if it's a general "methods may be redefined in extend/os" disclaimer. A standard warning colocated with redefined code would be my preference. A custom YARD tag (e.g. @redefined_in_extend_os) could be a possibility.

I don't imagine this to be helpful, if it's a general "methods may be redefined in extend/os" disclaimer.

My thinking was more that this documentation would explain how we separate code by OSs and why to ease people doing either Homebrew/brew platform work or porting to a new platform.
Another undef-avoiding option would be that we move the "generic" layer to os/extend/generic and we have these methods actually undefined in the original classes.
Similarly, we could use include SomeClassLinuxModule instead of reopening the class elsewhere.
I'm open to ideas, I just mainly want to avoid:

scattering more if/else all over the place
putting all definitions for all OSs in the same file(s) rather than in their own directory structures

My thinking was more that this documentation would explain how we separate code by OSs and why to ease people doing either Homebrew/brew platform work or porting to a new platform.

Agreed, personally I love (/feel reassured) when reading how technical decisions were thought out and considered.

Similarly, we could use include SomeClassLinuxModule instead of reopening the class elsewhere.

I think this is a very promising approach!  (prepend might make more sense here, though that's getting into the weeds a bit…)

I think this is a very promising approach! (prepend might make more sense here, though that's getting into the weeds a bit…)

To be clear: I'm not personally planning on rolling out this approach any time soon but someone in this thread who feels strongly should do so 😁.
To unblock things for now (CC @issyl0!), I'd like to strongly suggest we either do:

Also, I'm a bit reluctant to mention this option, but since the sorbet error is well-scoped, we could suppress it in the sorbet config. (Sorbet won't delete the method from its model, which is ~fine, as we use it to replace defs.)

or, which I'd now be fine with: just remove these undef because the Sorbet work is clearly higher priority than the "be able to run Homebrew one day at a higher level of warnings" work.

As of https://github.com/Homebrew/brew/pull/18056 we suppress type errors caused by using undef at typed: strict.
Here is a draft of using prepended modules rather than undef for OS extensions (using Cleaner, arbitrarily).

Gah, https://github.com/Homebrew/brew/pull/18056 doesn't work like I had hoped.
You can see that https://github.com/Homebrew/brew/blob/70b072a/Library/Homebrew/extend/os/mac/readall.rb is marked typed: strict now, but the sole method defined therein (valid_casks?) lacks a sig. Static sorbet typechecking can still identify type errors (it uses the original, undefined sig), but sorbet-runtime cannot.
I was somewhat indifferent to the prepend approach in the previous comment (it still has some discoverability issues IMO), but it does not suffer from this specific bug.

Should probably just remove the undefs instead of doing
https://github.com/Homebrew/brew/blob/fc8b80accf7c655829b26fa6e42f41e361ac7b31/Library/Homebrew/sorbet/config#L7

I don't think undef has anything to do with that - the behaviour is identical without it.

I was somewhat indifferent to the prepend approach in the previous comment (it still has some discoverability issues IMO), but it does not suffer from this specific bug.

Does it?
module A
  def f(x)
    p "no error"
  end
end

class B
  sig { params(x: Integer).void }
  def f(x)
    p x
  end
end

B.prepend(A)

B.new.f("ABC")
=> no error

It also doesn't work at all for class methods - I think that would require splitting further.

I don't think undef has anything to do with that runtime behaviour - the behaviour is identical without it.

Sorry, yes, tbc it's due to defining the same method multiple times within the same namespace. Sorbet is happy at strict if just one definition has a sig, but sorbet-runtime needs a sig each time to work.

I was somewhat indifferent to the prepend approach in the previous comment (it still has some discoverability issues IMO), but it does not suffer from this specific bug.

Does it?
module A
  def f(x)
    p "no error"
  end
end

class B
  sig { params(x: Integer).void }
  def f(x)
    p x
  end
end

B.prepend(A)

B.new.f("ABC")
=> no error

It also doesn't work at all for class methods - I think that would require splitting further.

Sorry, that isn't quite my bug report. If module A is in a typed: strict file, your example would require a sig for the A#f office. A sig is not required if it redefines B#f.

Ah, gotcha. Though it does however lose the ability for arity checking:
https://sorbet.run/#%23 typed%3A strong

module A
  extend T%3A%3ASig

  sig { params(x%3A String%2C y%3A String).void }
  def f(x%2C y)
    "uh oh"
  end
end

class B
  extend T%3A%3ASig

  sig { params(x%3A Integer).void }
  def f(x)
    p x
  end
end

B.prepend(A)

B.new.f(1)

Method redefinitions at least checked that behaviour.

Ah, gotcha. Though it does however lose the ability for arity checking:
https://sorbet.run/#%23 typed%3A strong

module A
  extend T%3A%3ASig

  sig { params(x%3A String%2C y%3A String).void }
  def f(x%2C y)
    "uh oh"
  end
end

class B
  extend T%3A%3ASig

  sig { params(x%3A Integer).void }
  def f(x)
    p x
  end
end

B.prepend(A)

B.new.f(1)

Method redefinitions at least checked that behaviour. Not sure how to best to get that back.

I imagine interfaces could be one solution there.

It occurs to me that if a generic-OS path existed, it would solve the discoverability issue for me, as well as the undef problem. Has that approach been considered? PoC: https://github.com/Homebrew/brew/compare/cleaner-interface?expand=1
(The above code also uses in an interface to enforce consistent signatures (e.g. arity checking). However, it suffers from the issue that signatures are not enforced in every OS extension file, even at typed: strict. That could be solved by defining modules in the OS-specific paths that are then included in Cleaner though.)
(Sorry for throwing so many approaches onto this thread, though it's helping me understand what coding styles are aligned with Homebrew. Folks in the sorbet Slack may find a more definitive answer there…)

It occurs to me that if a generic-OS path existed

It does already. Run brew tests --generic which exercises this 😁

Has that approach been considered? PoC: cleaner-interface?expand=1 (compare)

I like this approach more than others suggested above and mostly more than what exists already. It'd be nice to be able to reduce the boilerplate there a little, if at all possible but not a blocker, but I agree having the method defined just in the else case feels nicer.

It still suffers from the issue that signatures are not enforced in every OS extension file, even at typed: strict. That could be solved by defining modules (e.g. CleanerLinux) in the OS-specific paths that are then included in Cleaner, e.g.

I like this even more, nice work.

Sorry for throwing so many approaches onto this thread, though it's helping me understand what coding styles are aligned with Homebrew.

No, it's good. More ideas means we get a better end result!

Are we good to close this, now that we have an approach from https://github.com/Homebrew/brew/pull/18305 ?
Or should we wait until all the undefs are gone?

Or should we wait until all the undefs are gone?

I think it'd be good to wait for this. After that, I think it'd be good to have:

A "cross-platform code" section in docs.brew.sh for "Contributors"?

Based on the format we've decided and used consistently.

There doesn't seem to be an obvious way to remove the remaining undef usages throughout the codebase so maybe we can close this. It might be nice to add a linter rule to prevent undef from being used in new code as well if something like that doesn't already exist.

A linter rule, you say? My favourite!


A visual glitch in Mod Browser

Description
There is a visual glitch in Mod Browser in Brazilian Portuguese (possible other languages as well)
Versions
Terraria <IP_ADDRESS>
tModLoader v<IP_ADDRESS>
Mods
None
Additional Information

Just noticed it happens on some other places too.

Yeah, we'll need to recalculate the sizes and offsets based on the translations.

Oh yeah, I fixed this in 80cc3b892c53f8213731a48f3204a30b7d51f1ad
Once the next releaser/open beta is out, it would be neat if you could revisit this issue and let us know anything you notice that still needs changing.


Update paths and file name according to documentation

https://docs.sonarqube.org/latest/analysis/coverage/
https://docs.sonarqube.org/latest/analysis/external-issues/

Thanks for your PR @stefanerwinmayer.
This change would improve the integration with SonarScala, but it would break it for sonar-scala, which uses a different set of properties for scoverage and scapegoat. To make this work for both Scala plugins, we could use both sets of properties and automatically set them all (so in addition to the new properties that you added I'd also keep the old ones). This might result in sbt-sonar showing warnings about setting unused properties when running analysis using both SonarScala and sonar-scala (we'd need to check that it's not an error), but at least it's a quick way to make this work for both plugins. @BalmungSan does that sound ok to you?

I think we either should change sonar-scala to have the same flags. Or to add a flag / setting to this plugin to indicate which sonar plugin one is using.
I prefer the last.

add a flag / setting to this plugin to indicate which sonar plugin one is using

Yes, that would also be my preferred option 👍 I'd like to keep sonar-scala as the default option for compatibility reasons, but you could toggle a flag to switch over to SonarScala compatible properties. I'm trying to come up with any good names, but the best I've got so far is sonarUseCommunityPlugin which defaults to true and setting it to false toggles SonarScala compatibility. Can you think of any better alternatives?

I am really bad a naming things, and I liked yours. Thus, no alternatives from my side.

Hi @stefanerwinmayer, does the solution I proposed above make sense to you? Is that something you would be able to contribute as a part of this PR?

Hi @stefanerwinmayer, does the solution I proposed above make sense to you? Is that something you would be able to contribute as a part of this PR?

Yes I will do that.

Superseded by #117.


AppService 1.2 deployment issues

Hello,
I am trying to deploy AppService <IP_ADDRESS> package on our Azure Stack deployment. We have problem in "Deploy AppService" (AppService.DeployCloud / SharedWorkerTierScaleSetDeploy) step. This is error message we are getting:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "InternalExecutionError",\r\n "message": "Failed to update and/or remove existing disks for VM 'bfe15235-018b-4bd9-8cd7-00ef8735add1'"\r\n }\r\n ]\r\n }\r\n}"}]}
We've made several attempts to redeploy AppService and every time we got the same error.
We don't have any problems with deploying other Virtual Machines.
Do you have any ideas or suggestions how we can move forward?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 26ee2047-e51e-cf36-1bde-6919b2c5f3cf
Version Independent ID: c4e207d0-be8b-8096-52ad-04e0d029d1e2
Content: Deploy App Services: Azure Stack
Content Source: articles/azure-stack/azure-stack-app-service-deploy.md
Service: azure-stack
GitHub Login: @apwestgarth
Microsoft Alias: anwestg

@lzieba91 Thanks for the feedback. We are actively investigating and will get back to you soon.

@lzieba91 What's your stamp version? How many nodes you have?

Hi, We have 12 nodes and we were trying to deploy AppService on 1805. We managed to resolve that issue. Looks like memory usage on WAS and WASP machines was very high. We resolved this problem by rebooting whole Azure Stack.

Hi @lzieba91 as this is an integrated system on which you are experiencing the issue, please open a support ticket, then CSS, the Azure App Service on Azure Stack team and the rest of the Azure Stack teams can support you.  This is not an issue with the documentation and is more an issue with your Azure Stack instance.
Thanks
Andrew

@lzieba91 Glad to hear that issue has been resolved. Please leave your feedback at https://feedback.azure.com/forums/344565-azure-stack
If you are experiencing any further issues with your Azure Stack Integrated Systems, please open a support request as Andrew advised.

@lzieba91 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Is it a linux-based environment？

I can't meet the following requirements at the same time：python2.7 & pytorch0.4.0/0.4.1 with CUDA & Windows .
So is it necessary for me to change my OS?
Thanks!

Yes, I use ubuntu 16.


Does PAL work with indirect role assignments using an Azure AD group?

Do we need to do the role assignment directly with the user account on a resource or will PAL also be recognized if I add a user to an Azure AD group and give only the group access to a resource?
For example, let's take an AAD group "PROJECT_CONTRIBUTOR" with member<EMAIL_ADDRESS>Max has configured PAL, and there is a resource group named "RG-Any-Project" in which the AAD group PROJECT_CONTRIBUTOR has contributor privileges. Is PAL recognized even if Max has no direct role assignment to the resource group, but indirectly through the group?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5f901056-c225-b086-cdaa-c8bd978db64c
Version Independent ID: 9c067eb4-54cb-e141-d82f-e136ff3c671e
Content: Link an Azure account to a partner ID
Content Source: articles/cost-management-billing/manage/link-partner-id.md
Service: cost-management-billing
Sub-service: billing
GitHub Login: @dhirajgandhi
Microsoft Alias: banders

@mjisaak Thank you for the feedback. We are actively investigating and will get back to you soon.

@mjisaak, I have assigned this issue to the content author for further comment, review, and update. Please let us know if you have any question.
@dhirajgandhi, can you please look in to this and share your thoughts.

@AnuragSingh-MSFT, Thank you. Right now I don't have any additional questions - looking forward to hearing from the content author.

https://github.com/MicrosoftDocs/azure-docs-pr/pull/178724
@mjisaak Hi there. Good question. Yes, if a group has Azure RBAC access, then PAL is recognized for all the users in the group. I've updated the article to add that point.
Thanks for asking and helping us improve the documentation.
#please-close


How do we know which Certificate Authorities are considered "well known" for AZ App Gateway V2 backend settings?

It would be useful to have instructions on how to determine which Certificate Authorities are considered "Well Known" by this setting:

Can you provide instructions on where to find this information?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 77a317f1-deef-4ba7-5839-f39ce3733655
Version Independent ID: d85aa8fe-7270-d073-ea56-d1c0759383b8
Content: Enabling end to end TLS on Azure Application Gateway
Content Source: articles/application-gateway/ssl-overview.md
Service: application-gateway
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

According to a survey done in July 2022, these are the top CAs used around the world:

Are all of these considered "Well Known"?

@pgbfnf
Thank you for your feedback! We will review and update as appropriate.

I believe that in this context, the term 'well-known' means trusted. Most or all well-known public certification authorities are trusted. Refer to the top of the dialog box where it says "Trusted Root Certificate" instead of the phrase just above the yes/no selection. I'm sorry this is a little confusing.  I am in the process of scrubbing the certificate instructions in all the docs to make it clearer what is a trusted and/or well-known certificate.
For example, if you have your own Root CA then a client could trust this Root certificate, but it wouldn't be a 'well-known' public certificate.  So, the terms are used a little too loosely here.

I understand we can add our own internal CA root certificate, but it would be helpful to know EXACTLY which companies MS/Azure trusts, instead of guessing. Even if it's some external list that is managed by a global authority, just some way to know - If I buy a certificate from X company, then it will be automatically considered Trusted by MS/Azure. For example, is there a "Trust Store" somewhere that is updated over time?

Maybe the gateway pulls from this list?
https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT


Look into compatibility with cc-get

A. See if we can directly use the cc-get sources and install packages from there as a fallback to our system.
B. See if we can create a cc-get package to install cc-get alongside cc-paw? Warn that this can lead to incompatibility issues.

http://cc-get.djranger.com/


ngResource multiple deletion DELETE

HI, is there any way to pass data with $delete or $remove actions?
For example: I need to do multiple deletion, the method and url are: DELETE /api/v1/user/
and along with I need to send array of ids to be deleted.

@iyel please direct support questions like this one to one of those support channels. We want to keep GitHub issues for bug reports and feature requests only. Thnx!


Support push notifications for Email

Push documentation https://jmap.io/spec-core.html#push

See https://tools.ietf.org/html/rfc8887

Encountering some problems to send HTTP headers with browser websocket API.
See https://stackoverflow.com/questions/4361173/http-headers-in-websockets-client-api
See https://github.com/whatwg/html/issues/3062


'T5Stack' object has no attribute 'first_device

I have already begun the fine tuning. However, some thing wrong:
***** Running training *****
  Num examples = 2830
  Num Epochs = 6
  Instantaneous batch size per device = 8
  Total train batch size (w. parallel, distributed & accumulation) = 64
  Gradient Accumulation steps = 8
  Total optimization steps = 264
  0%|                                                                                | 0/264 [00:00<?, ?it/s]Traceback (most recent call last):
  File "workspace/train_code5.py", line 268, in <module>
    train()
  File "workspace/train_code5.py", line 262, in train
    trainer.train(resume_from_checkpoint=training_args.resume_from_checkpoint)
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/transformers/trainer.py", line 1498, in train
    return inner_training_loop(
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/transformers/trainer.py", line 1740, in _inner_training_loop
    tr_loss_step = self.training_step(model, inputs)
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/transformers/trainer.py", line 2470, in training_step
    loss = self.compute_loss(model, inputs)
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/transformers/trainer.py", line 2502, in compute_loss
    outputs = model(**inputs)
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/deepspeed/utils/nvtx.py", line 15, in wrapped_fn
    ret_val = func(*args, **kwargs)
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/deepspeed/runtime/engine.py", line 1768, in forward
    loss = self.module(*inputs, **kwargs)
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1538, in _call_impl
    result = forward_call(*args, **kwargs)
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/transformers/models/t5/modeling_t5.py", line 1621, in forward
    torch.cuda.set_device(self.decoder.first_device)
  File "/root/miniconda3/envs/seedpicker/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1614, in __getattr__
    raise AttributeError("'{}' object has no attribute '{}'".format(

I check the issue repo and install the transformers with version 4.21.3 as suggestion https://github.com/salesforce/CodeT5/issues/113.
What should I do? Thanks.

Face the same problem here : (


Using nf-core :green_apple:  template on MTBseq-nf step :two: :

Update the main modules and add description and copyright info
Hey there :wave:,
On this PR I've worked on updating our mtbseq-nf modules to the nf-core template in the middle term of our template and nf-core template, not assuming all the rules of nf-core that we could refine later on.
This is a first step on the development of nf-core/mtbseq
I'm available to make any necessary change and discuss possible modifications of this work.
Thank you for your attention!

And - could we please also update the nf-core template to version 2.10 ?

I've just bumped to version 2.10 template, on the last commit https://github.com/mycobactopia-org/MTBseq-nf/pull/79/commits/21e1d63e18cbb877b7752c5dad61f47f521bec41, this added a lot of file changes

Thanks Davi, I think we can take it forward with the merge and start the next iteration  :)


[FEA] kernel for date_trunc and trunc that has a scalar format

Is your feature request related to a problem? Please describe.
The current implementation of trunc and date_trunc use a kernel where the format is a column.
This works great. In my tests I saw a 180x speedup over the CPU (16 cores).  But we could save a lot of memory if the format is a scalar, which I think is the most common case.
In the best case where the format string is "DD", a new kernel we would save about 6 bytes per row of input. On a date that is 150% increase in memory usage. For a timestamp that is only a 75% increase in memory usage.  But for the worst case on a date it is "QUARTER" or a 275% increase in memory usage. For a timestamp it is "MICROSECOND", which would be 187.5% increase in memory usage.  This is probably minor, but it would be nice.

The current JNI implementation is already optimized for memory. Although the scala is promoted into a column, such column has only one row thus there is no change in memory usage.
However, I agree that we can optimize further in term of performance. Currently, a column format is parsed when processing every row. We can do better by parsing the scalar format (on host) before calling the kernel, saving time for the GPU by not doing so again. I'll post a JNI PR shortly.


opensync: enable dhcp sniffing only on bridge interface

Reduce nm running memory footprint by enabling dhcp sniffing only on bridge interface.
Signed-off-by: Arif Alam<EMAIL_ADDRESS>

Did testing confirm DHCP sniff worked for bridge and NAT, for VLAN and non-VLAN?
Do we anticipate it will work with the GRE tunnel?

Should ideally work with GRE tunnel as long as it works on other bridge interfaces

Thanks for testing the additional scenarios, merged.