#1025 mod_firewall test error in IN ROSTER?

Reporter Zash
Owner Zash
Stars ★ (1)
  • Status-Accepted
  • Type-Defect
  • Priority-Medium
  • Component-Community
  1. Zash on

    What steps will reproduce the problem? These rules: KIND: message NOT IN ROSTER? DROP. Input: <message to="localuser@localhost" from="nobody@elsewhere.example" type="chat"/> What is the expected output? ** Summary ** ------- ** ** 1 processed ** 0 passed ** 1 droppped ** 1 input lines ** What do you see instead? Failed to execute command: Error: ./core/rostermanager.lua:102: attempt to index upvalue 'bare_sessions' (a nil value) stack traceback: ./core/modulemanager.lua:31: in function <./core/modulemanager.lua:31> [C]: in function 'parse' ./util/xmppstream.lua:271: in function 'feed' extra/mod_firewall/test.lib.lua:55: in function <extra/mod_firewall/test.lib.lua:9> (...tail calls...) [C]: in function 'xpcall' ./core/modulemanager.lua:31: in function <./core/modulemanager.lua:28> (...tail calls...) ./prosodyctl:1469: in main chunk [C]: in ? What version of the product are you using? 5df2f240173b trunk Please provide any additional information below. Problem is that prosodyctl doesn't set up the global 'prosody' object the same way as the prosody executable itself. #851 would be useful.

  2. Zash on

    Ops, I had a patch applied and this runs fine.

    • owner Zash
    • tags Status-Invalid
  3. Zash on

    Never mind, that change was unrelated to this rostermanager error.

    • tags Status-Accepted
  4. Zash on

    • tags Component-Community

New comment

Not published. Used for spam prevention and optional update notifications.