Skip to content

Conversation

@adfoster-r7
Copy link
Contributor

Pin date dependency; as it looks like 3.5.0 might be causing issues:

$ ./msfconsole
[*] Bundler failed to load and returned this error:

   'You have already activated date 3.5.0, but your Gemfile requires date 3.4.1. Prepending `bundle exec` to your command may solve this.'

[*] You may need to uninstall or upgrade bundler

But this will require additional cycles to verify, so pinning for now

Verification

Ensure CI passes

@bwatters-r7 bwatters-r7 self-assigned this Nov 4, 2025
@bwatters-r7
Copy link
Contributor

bwatters-r7 commented Nov 4, 2025

FWIW, pinning the date dependency makes recovery easier, but I can re-create the original error by updating pretty much any of these that have interdependencies:

metasploit_data_models
actionpack
railties
activemodel
activesupport
activerecord

[ruby-3.3.8@metasploit-framework]((HEAD detached at upstream/pr/20673)) tmoose@ubuntu-dev2024:~/rapid7/metasploit-framework$ ./msfconsole -q
[-] No results from search
[-] Failed to load module: payload/cmd/linux/http/multi/meterpreter_reverse_tcp
msf > exit
[ruby-3.3.8@metasploit-framework]((HEAD detached at upstream/pr/20673)) tmoose@ubuntu-dev2024:~/rapid7/metasploit-framework$ bundle update actionpack
Fetching gem metadata from https://rubygems.org/..........
Resolving dependencies...
Resolving dependencies...
Using activesupport 7.2.3 (was 7.2.2.2)
Using activemodel 7.2.3 (was 7.2.2.2)
Using actionview 7.2.3 (was 7.2.2.2)
Using activerecord 7.2.3 (was 7.2.2.2)
Using actionpack 7.2.3 (was 7.2.2.2)
Using railties 7.2.3 (was 7.2.2.2)
Bundle updated!
1 installed gem you directly depend on is looking for funding.
  Run `bundle fund` for details
[ruby-3.3.8@metasploit-framework]((HEAD detached at upstream/pr/20673)) tmoose@ubuntu-dev2024:~/rapid7/metasploit-framework$ ./msfconsole -q
/home/tmoose/rapid7/metasploit-framework/config/application.rb:10:in `<top (required)>': unhandled exception
	from /home/tmoose/.rvm/rubies/ruby-3.3.8/lib/ruby/3.3.0/bundled_gems.rb:69:in `require'
	from /home/tmoose/.rvm/rubies/ruby-3.3.8/lib/ruby/3.3.0/bundled_gems.rb:69:in `block (2 levels) in replace_require'
	from /home/tmoose/.rvm/gems/ruby-3.3.8@metasploit-framework/gems/bootsnap-1.18.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'

I have no idea why or which of those appears to hate bootsnap, but they crash regardless of me using the original bootsnap 1.18.4 or the new 1.18.6

@adfoster-r7
Copy link
Contributor Author

Thanks! That's expected as those dependencies are implicitly pinned in the codebase itself and that's expected for now ✅

I'll put up a separate PR to improve the error handling there 👍

@bwatters-r7 bwatters-r7 added the rn-fix release notes fix label Nov 4, 2025
@bwatters-r7 bwatters-r7 merged commit b70d9c0 into rapid7:master Nov 4, 2025
62 checks passed
@bwatters-r7
Copy link
Contributor

Release Notes

Temporarily pins date dependency to 3.4.1 due to possible issues associated with 3.5.0 to allow for further testing.

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

Labels

rn-fix release notes fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants