Skip to content
#

iot

Here are 11,496 public repositories matching this topic...

netdata
HolgerHees
HolgerHees commented May 17, 2019

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

joshkping
joshkping commented Nov 16, 2021

Is there an existing issue for this?

  • I have searched the existing issues

Kong version ($ kong version)

2.5.1.0

Current Behavior

When calling kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2:

A sender MUST NOT send a Content-

averelon
averelon commented Aug 7, 2020

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

urh
jacobagilbert
jacobagilbert commented Sep 18, 2020

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

questdb
TheTanc
TheTanc commented Nov 21, 2021

Is your feature request related to a problem?

I like to use the chart tab in the console. However, the chart scale is not customisable and starts at 0. This makes it hard to visualise data where the changes are relatively small.

Describe the solution you'd like.

Either

  • Dynamic scaling of the charts based on results values
  • Manual scaling by adding a range min/max input in the con

This repository contains all the DSA (Data-Structures, Algorithms, 450 DSA by Love Babbar Bhaiya, FAANG Questions), Technical Subjects (OS + DBMS + SQL + CN + OOPs) Theory+Questions, FAANG Interview questions, and Miscellaneous Stuff (Programming MCQs, Puzzles, Aptitude, Reasoning). The Programming languages used for demonstration are C++, Python, and Java.

  • Updated Nov 28, 2021
  • Jupyter Notebook
microk8s
typoworx-de
typoworx-de commented Aug 31, 2021

While struggling around with ingress (#2546) I figured out some inconsistencies. For most k8s services it is possible to override args or configs. But for ingress this doesn't work.

It should be possible to customize enable.{my-service} and {my-service}.yaml by having a local copy in:
/var/snap/microk8s/current/microk8s-resources/

But this doesn't seem to work.

node-serialport
SVSagi
SVSagi commented Jul 30, 2018

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

Improve this page

Add a description, image, and links to the iot topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the iot topic, visit your repo's landing page and select "manage topics."

Learn more