1. 12 4月, 2019 1 次提交
    • V
      Alternative Improve _uploadReadByte (#2656) · 25c0b522
      Victor Aprea 提交于
      * add opportunity for more than one retry to _uploadReadByte
      
      * an alternative timeout-based method to making _uploadReadByte more resilient
      
      * move timing variables in the correct scope
      
      * implement and use client.getTimeout instead of hard-coded timeout in _uploadReadByte
      
      * add missing return
      
      * some refactoring to address respecting the timeout in a potentially deadlocked connection
      
      * fix spelling in comment
      
      * address review comments; move impl to cpp file for getTimeout, and remove local variable for currentMillis
      
      * remove redundant cast
      
      * need to check for timeout outside the inner while as well
      
      * update WebUpdate example to print something in unexpected callback condition
      
      * update log_e messages per review comments
      25c0b522
  2. 10 4月, 2019 1 次提交
    • D
      Reset retry counter upon successful write (#2638) · a0c975df
      dyarkovoy 提交于
      Currently  WiFiClient::write is unable to send messages over 25Kb, because of the hard-coded retry limit of 10, that is getting decremented on every successful send. Since we cannot send more than 2*MTU bytes in one go, and have only 10 retries, write() is limited to approximately 25Kb. Technically it is not a bug, as it correctly returns the number of sent bytes and the caller can set up futher retries. But not all libs are aware of this behavior, for example, WebServer is not.
      I suggest improving current behavior by resetting retry counter every time we had a successful write, so the limit of 10 retries will apply to Failed writes only, and will not apply to Successful writes. This will allow to write() blobs of arbitrary sizes.
      a0c975df
  3. 03 3月, 2019 3 次提交
  4. 20 2月, 2019 1 次提交
  5. 14 2月, 2019 3 次提交
  6. 23 1月, 2019 1 次提交
  7. 22 1月, 2019 1 次提交
  8. 02 1月, 2019 1 次提交
  9. 29 12月, 2018 1 次提交
  10. 16 12月, 2018 1 次提交
  11. 07 12月, 2018 2 次提交
  12. 05 12月, 2018 1 次提交
  13. 03 12月, 2018 1 次提交
  14. 01 12月, 2018 1 次提交
  15. 29 11月, 2018 1 次提交
    • L
      Clean warnings when all warning enabled (#2112) · ce340faf
      Luc 提交于
      * Clean warnings when all warning enabled
      
      Not used variables / functions due to debug log
      
      Dual define with different values :
      cores\esp32/binary.h
      #define B110 6
      #define B1000000 64
      
      tools/sdk/include/newlib/sys/termios.h
      #define B110        3
      #define B1000000   23
      
      Local variable returned in WiFiclient Secure
      
      * change due to deprecated function
      
      * Update with proper variable and label
      
      * Update esp32-hal-i2c.c
      
      * Apply changes requested
      
      * Fix warnings due to #define conflict thanks @atanisoft
      ce340faf
  16. 19 11月, 2018 6 次提交
  17. 21 9月, 2018 1 次提交
    • M
      Update IDF to 3.2-3276a13 and esptool.py to 2.5.0 (#1878) · 96822d78
      Me No Dev 提交于
      * TX Flow Control and Code cleanup
      
      * Use semaphore instead of delay
      
      TX functionality is done.
      
      * Use single buffer and empty queue on exit
      
      * Fix compile issues because of LwIP code relocation
      
      * Add temporary header to fix Azure not compiling
      
      * Fix AsyncUDP early init
      
      * AsyncUDP Multicast fixes
      
      * Add source mac address and rework multicast
      
      * Allow redefinition of default pins for Serials 1 and 2
      
      * Update IDF to 3276a13
      
      * Update esptool.py to 2.5.0
      
      * Fix sketches
      
      * Fix log level in BluetoothSetial
      96822d78
  18. 18 9月, 2018 3 次提交
  19. 14 8月, 2018 1 次提交
  20. 30 7月, 2018 2 次提交
  21. 25 7月, 2018 3 次提交
  22. 17 7月, 2018 2 次提交
  23. 11 7月, 2018 1 次提交
  24. 10 7月, 2018 1 次提交