w.r.t. developing in master vs specific feature branch ... what stops doing it right now? I don't see any reason why not developing in feature branch, then merging to master when ready.
nothing! Just a few maintainers to manage that process and merge PR's into a feature branch rather than master, then when everything on that branch is building neatly against tests then it can be pushed to master
--repoflag with the path to the build command. As far as I understand, that sets that folder as the mOS source, hence building against a specific commit. I have NOT used that flag in some time now, but I believe that's how it works.
mongoose-osis just a module, so the above is equivalent to this:
modules: - location: https://github.com/cesanta/mongoose-os version: HASH
/mongoose-os/src/mgos_net.c: In function 'mgos_update_nameserver': <command-line>: error: too many decimal points in number
modules_version) will pin everything.
make…. ’-j’ ’10’but I don’t see any
-Ousage, so I thought by defining flags in the
mos.ymlthat I would see my compile flags get inserted somewhere in the build process. But I do not.
cxxflags: # or cflags (I’ve tried both) - "-Os"
-Osto the compilation to optimize for size?
MQTT queue never sends
I'm seeing odd behaviour where occasionally the MQTT queue is not drained, i.e. mgos_mqtt_num_unsent_bytes() returns a positive value that never decreases.
The device is an ESP32 connecting via PPPoS (Quectel M65) to AWS infrastructure
The system never recovers from this. Incoming MQTT published from AWS test client work ok, and then after a while they are no longer received by the device.
Internet connectivity is fine though - i have a button press that performs a HTTP GET from a web site, and this continues to work retrieving content, indicating outgoing and incoming data is flowing through the PPPoS connection.
Has anyone experienced anything like this? or have idea.
Since july, I noticed that mos tool is failing on my mac computer . I am getting errors opening the serial port when running some of the commands like mos license or mos config-get with the following message
Error: write: /dev/cu.usbserial-[XXXX]: file already closed
On the other hand, mos flash and mos console seem to be working fine.
The device are working OK, as I am able to check through the console.
I tried, upgrading mos to 2.20.0, de-installing and re-installing mos completely and a fresh mos install on another MAC computer (using the instructions from this page Mongoose OS Documentation).
I keep having the same issue,
Do you have any recommendation on how to troubleshoot this issue ?