forked from nodemcu/nodemcu-firmware
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Master #1
Merged
Merged
Master #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Due to Windows limitations. Sigh.
This reverts commit af9b123.
* Add DHCP option 42 / NTP * Update dhcp.c * resolve merge conflict * add lineend at end of file * fix merge conflict resolution error
* list_ref can become LUA_REFNIL, because that's what rawgeti returns for LUA_NOREF. Defensively guard for this, rather than falling into the sntp_dolookups loop with nil on the stack. * set_repeat_mode should not call itself, but should rather always do what it's going to do and then optionally do the rest if directed. * sntp_sync should not try to special case the single string argument: we should be queueing that name for DNS resolution, too. Towards that end, if we are given a single string, build a table and make that the list_ref and call off to sntp_dolookups, just like we otherwise do. FIXES: #2699
We just don't have the memory to be a real TLS client on the 8266. Put that in a big box and point at it from the http and mqtt modules; others may also wish to give reference.
* Create mispec_file.lua * Initial commit of gambiarra * Adapt gambiarra to NodeMCU * adapt to NodeMCU spacing and add nok functionality * Some refactoring to make it easier to add new functionality * Add methode `fail` to check failing code and pass error messages to output - fail can be called with a function that should fail and a string which should be contained in the errormessage. - Pass failed check reasons to output. * Create gambiarra_file.lua * Add reporting of tests that failed with Lua error * ok, nok and fail will terminate the running test * Add capability to run sync and async tests in mixed order and have a task.post inbetween them * fix gambiarra self test to also run on device (not only host) Use less ram in checking tests directly after they ran. Use nateie task.post to tame watchdog. * Update file tests + add async tmr tests * Another fix in executing async test * Catch errors in callbacks using node.setonerror * change interface to return an object with several test methods * Update README.md * Change interface of Gambiarra + add reason for failed eq * Update gambiarra documentation * Add coroutine testcases to gambiarra * Delete mispec_file.lua as it is superseeded by gambiarra_file.lua * improve regexp for stack frame extraction * Use Lua 53 debug capabilities * move actual tests upfront * remove debug code + optimization * Show errors immediately instead of at the end of the test, freeing memory earlier * Split tests to be run in 2 tranches * rename to NTest and move to new location * Add tests to checking mechanisms * Add luacheck to tests * Some pushing around of files * more (last) fixes and file juggling * Minor tweaks and forgotten checkin * Add NTest selftest to travis * Trying how to master travis * another try * restrict NTest selftest to linux
* Allow turning off softwd again as documented * fix luacheck warnings * fix outcome of review
* COnvert the rst to md... * CLeanup the automatic conversion * Try and make the tables work * And again * Get rid of the end-of-table marker
* DHT module negative values bug fix * Revamp of the DHT module, DHT12 support * Updated documentation
And move luaL_checkudata to it, as in 5.3.
Will build in parallel and covers more environments than the Travis build.
These have been handy within the test harness for streaming files and LFS images across to the DUTs. Add nrec method to pipe Co-authored-by: Gregor Hartmann <HHHartmann@users.noreply.github.com>
* convert mispec tests to NTest and remove mispec * fix luacheck
* mqtt: remove concept of connection timeout Just rely on the network stack to tell us when things have gone south. * mqtt: remove write-only mqtt_state.port field * mqtt: drop useless conditional * mqtt: decouple message sent flag from timer * mqtt: reconnect callback does not need to hang up The network stack has certainly done that for us at this point. Similarly, since we're about to call mqtt_socket_disconnected, don't bother unregistering the timer here, either. * mqtt: don't tick once per second Set the timer for the duration of the wait and cancel it on the other side. * mqtt: defer message queue destruction to _disconnect We're going to want to publish a disconnect message for real, so doing this in _close does no one any favors * mqtt: miscellaneous cleanups No functional change intended * mqtt: close() should send disconnect message for real This means waiting for _sent() to fire again before telling the network stack to disconnect. * mqtt: tidy connect and dns - Push the self-ref to after all allocations and error returns - Don't try to extract IPv4 from the domain string ourselves, let the resolver, since it can - Don't try to connect to localhost. That can't possibly work. * mqtt: common up some callback invocations * mqtt: don't retransmit messages on timeout There's no point in retransmitting messages on timeout; the network stack will be trying to do it for us anyway. * mqtt: remove unnecessary NULL udata checks * mqtt: hold strings in Lua, not C Eliminates a host of C-side allocations. While here, move the rest of the mqtt_connect_info structure out to its own thing, and pack some flags using a bitfield. * mqtt: mqtt_socket_on use lua_checkoption * mqtt: slightly augment debug messages These changes have made some debugging ever so slightly easier.
There was a memory leak related to not dropping all references to fifosock's ssend.
`ws2812` buffer extracted to new `pixbuf` module. * The new pixbuf module has more functionality than the `ws2812`-specific buffer it replaces. * This is work in progress towards #2916 * The LED driver modules `ws2812`, `ws2801`, `apa102`, and `tm1829` have sprouted `pixbuf` support. * `NTest` tests for `pixbuf` now exist. While here, document the ws2812 UART-based overlapping with mainline execution. Fixes #3140 Co-authored-by: Gregor Hartmann <HHHartmann@users.noreply.github.com>
I am sure I have seen this in the PR at some time
…on the host emulating node.task.post (#3357) * Change NTest so it can run tests on the host emulating node.task.post * Add executing first host test * Regression: fix luaL_typerror
* apa102: remove dead code We can't store strings of hundreds of thousands of characters in RAM, so this can't possibly have fired, historically. Pixbufs are still RAM objects, so that's still out. With LFS, it would take a pathological example to hit the required 400KB TSTRING. * Add IRQ management functions * ws2812: fill UART FIFOs with IRQs off Refactor code to make the use of two fill loops less gross.
* LiquidCrystal I2C 4-bit robustness - Fix up some formatting - Initialization is now more conformant with the datasheet. - Read-backs don't needlessly (or erroneously!) store back While here, document some unexpected behaviour of read-back commands. * liquidcrystal i2c 4bit NTest
* Rename to tests/README.md * Expand tests/README.md a bit * NTest: remove report() in favor of named fields Use a metatable to provide defaults which can be shadowed by the calling code. * NTest: remove old interface flag I think we have few enough tests that we can verify not needing this alert for ourselves. * NTest tests: new standard prelude Allow for NTest constructor to be passed in to the test itself. The test harness can use this to provide a wrapper that will pre-configure NTest itself. * NTest output handler for TAP messages * expect tests: core library functions * expect tests: file xfer TCL module * expect tests: add TAP-based test runner * Begin documenting TCL goo * Add .gitattributes to make sure lineends are correct ... ... if checked out under windows and executed under linux (say docker) * tests/README: enumerate dependencies * tests: more README.md Co-authored-by: Gregor Hartmann <HHHartmann@users.noreply.github.com>
- Changed the note about bme280_math dependency into a blue note box, like in the [bh1750 documentation](https://nodemcu.readthedocs.io/en/release/lua-modules/bh1750/) - Added a paragraph on differentiating between BMP280 and BME280 sensors. It put it in an orange caution box for now, might be too visible for a rare problem. - Small fixes in bme280.setup() description
While we intend our release strategy to be that we just fast-forward our `release` branch to `dev`, things have come a little off the wheels. This is a "git merge -s recursive -X theirs" of `dev` into `release` instead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resync fork to 3.0.0