#1171 Use the same module inheritance for components in Prosody and in prosodyctl
Reporter
Link Mauve
Owner
MattJ
Created
Updated
Stars
★ (1)
Tags
Status-Fixed
Priority-Medium
Milestone-0.10
Type-Defect
Link Mauve
on
What steps will reproduce the problem?
1. Have a module listed in the global modules_enabled (such as proxy65).
2. Have a component loaded (without this module).
3. Run `prosodyctl check`.
What is the expected output?
No check run for this module.
What do you see instead?
Checking DNS for component component.linkmauve.fr...
File transfer proxy component.linkmauve.fr has no A/AAAA record. Create one or set 'proxy65_address' to the correct host/IP.
What version of the product are you using? On what operating system?
trunk f25fa63750fb on ArchLinuxARM.
Please provide any additional information below.
N/A
This *does* appear to work fine, but I'm closing this issue - now that 0.11 is released, I don't think we will be backporting minor stuff like this to 0.10.
What steps will reproduce the problem? 1. Have a module listed in the global modules_enabled (such as proxy65). 2. Have a component loaded (without this module). 3. Run `prosodyctl check`. What is the expected output? No check run for this module. What do you see instead? Checking DNS for component component.linkmauve.fr... File transfer proxy component.linkmauve.fr has no A/AAAA record. Create one or set 'proxy65_address' to the correct host/IP. What version of the product are you using? On what operating system? trunk f25fa63750fb on ArchLinuxARM. Please provide any additional information below. N/A
Fixed in https://hg.prosody.im/trunk/rev/d4c98115e00c However I'm going to leave this open as a candidate for 0.10 backport if it proves reliable.
ChangesThis *does* appear to work fine, but I'm closing this issue - now that 0.11 is released, I don't think we will be backporting minor stuff like this to 0.10.
Changes