1. 07 Nov, 2020 22 commits
  2. 09 Sep, 2020 1 commit
  3. 08 Sep, 2020 1 commit
  4. 07 Sep, 2020 2 commits
  5. 05 Sep, 2020 1 commit
  6. 04 Sep, 2020 2 commits
    • vsky's avatar
      Fixes `net.ifinfo` failure · e28cf8d9
      vsky authored
      e28cf8d9
    • galjonsfigur's avatar
      SoftUART module fixes and code simplification (#3104) · e7620b06
      galjonsfigur authored
      * SoftUART fixes:
      
      - Simplify code by using lua_L* functions and using userdata properly
      - Fix some edge-cases
      - Add more examples to documentation
      
      * Don't de-register interrupt hook if there is more RX instances
      
      * More bug fixes and registering simplification with luaL_reref and unref2
      
      * Correct documentation of SoftUART module
      e7620b06
  7. 03 Sep, 2020 1 commit
  8. 01 Sep, 2020 1 commit
  9. 30 Aug, 2020 1 commit
  10. 29 Aug, 2020 3 commits
  11. 23 Aug, 2020 2 commits
  12. 22 Aug, 2020 2 commits
  13. 11 Aug, 2020 1 commit
    • Caleb Mingle's avatar
      mqtt: fix connfail callback · e547c2a0
      Caleb Mingle authored
      I've not been able to get the mqtt `connfail` callback to work.
      
      I'm consistently receiving `method not supported` errors:
      ```
      application.lua:53: method not supported
      stack traceback:
              [C]: in function 'on'
              application.lua:53: in main chunk
              [C]: in function 'dofile'
              init.lua:18: in function <init.lua:6>
      ```
      
      Example code:
      ```
      function on_connection_failed(client, reason)
          print("mqtt connection failed: " .. reason)
      end
      
      m:on("connfail", on_connection_failed)
      ```
      
      I believed this to be caused by the incorrect length comparison for `connfail`
      that is updated here.
      
      Once I changed that, the error went away, however the callback was never called.
      
      I believe the callback was never called because of an incorrect assignment.
      
      However, I saw this somewhat confusing description in the docs so this
      assignment may be expected?
      > The second (failure) callback aliases with the "connfail" callback available through :on(). (The "offline" callback is only called after an already established connection becomes closed. If the connect() call fails to establish a connection, the callback passed to :connect() is called and nothing else.)
      e547c2a0