iot
Here are 8,889 public repositories matching this topic...
-
Updated
Sep 29, 2020 - Python
Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13
Internet says it should return 204:
- https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
- https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests
Internet changed its mind since 2018 https://
-
Updated
Sep 15, 2020 - C
-
Updated
Sep 29, 2020 - C
-
Updated
Sep 29, 2020 - C
-
Updated
Sep 28, 2020 - JavaScript
The uncompensated temperature of the BMP180 is incorrectly converted to a 16-bit signed value, instead of a 32-bit signed value (long). Since the data is 16-bits wide and can therefore not be negative, the easy fix would be to do the following:
sip.js(1128): uncompensated = uint16(data[0], data[1]);
Please see page 15 of the manual of the BMP180 chip:
https://ae-bst.resource.bosch.com/media
Description
I get the following warnings once a minute:
2020-06-23 23:11:13,900 [salt.loaded.int.fileserver.roots:180 ][WARNING ][24993] Skipped invalid cache mtime entry in /var/cache/salt/master/roots/mtime_map: /srv/salt/a/b/c/ifcfg-eth0:0:1533517049.0
2020-06-23 23:11:13,901 [salt.loaded.int.fileserver.roots:180 ][WARNING ][24993] Skipped invalid cache mtime entry in /var/cache/salt
-
Updated
Sep 29, 2020 - C
-
Updated
Sep 29, 2020 - Java
-
Updated
Sep 27, 2020 - Go
-
Updated
Sep 29, 2020 - Erlang
-
Updated
Aug 26, 2020 - C#
A common protocol structure is to have a header containing a length field, followed by data of length bytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.
I do not know the best way to address this, but quick and easy way to support
-
Updated
Sep 28, 2020 - C++
-
Updated
Sep 27, 2020 - C
Summary of Problem
Not able to open port with stopbits as 1.5
I am currently building a desktop client using electron, where the COM port receives data correctly for values: baudRate: 2400, dataBits: 7, stopBits: 1.5, parity: 'none'
I found from the node-serialport documentation, stopBits Must be one of these: 1 or 2. But, should 1.5 be supported as well? especially for old & slow
-
Updated
Sep 29, 2020 - Python
-
Updated
Sep 28, 2020 - C
I recently installed the microk8s snap on a vanilla LXD container. At the time I hadn't come across https://microk8s.io/docs/lxd and it took a little while before I noticed that some components hadn't started up properly and I found my way to that doc.
Having found the documentation, it's excellent, thank you - following the instructions there left me with a very happy microk8s instance. From a
-
Updated
Feb 14, 2019 - JavaScript
Is your enhancement proposal related to a problem? Please describe.
Refer to zephyrproject-rtos/zephyr#27357 (comment)
and
zephyrproject-rtos/zephyr#27357 (comment)
Describe the solution you'd like
- Use sys_get_le24() to pass crc_init value
- Define CRC polynomial and use the define instead of magic numbers.
-
Updated
Sep 29, 2020 - C
-
Updated
Sep 29, 2020 - Java
-
Updated
Sep 29, 2020 - C++
What would you like to be added/modified:
To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.
To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef
Improve this page
Add a description, image, and links to the iot topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the iot topic, visit your repo's landing page and select "manage topics."
The PR is #4008