text:
[UI - Dashboard/Data Explorer] Configure cell throws exception Cannot destructure property 'keys'

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

Generate some test data covering the past month
Create a Dashboard and then a cell to display the test data - save the cell so that the dashboard is shown
Click configure of the cell

(For Data Explorer see further comment)
Expected behavior:
That the cell edit view loads without issue so that the query can be manipulated.
Actual behavior:
The Flux schema navigation pane contains the message "An InfluxDB error has occured..."   I don't see any obvious error messages in the influxdb log, however console log contains.
TypeError: Cannot destructure property 'keys' of 'en(...).queryBuilder.tags[t.index]' as it is undefined.

Screencast

Environment info:

System info: Run uname -srm and copy the output here

Linux 4.4.0-169-generic x86_64

InfluxDB version: Run influxd version and copy the output here
This was detected in the nightly build docker image

ts=2019-11-28T08:48:48.770163Z lvl=info msg="Welcome to InfluxDB" log_id=0JOJ0tWW000 version=nightly commit=f27198c1a build_date=2019-11-28T07:25:07Z

Other relevant environment details: Container runtime, disk info, etc

Browser: Chrome 78
Config:
Copy any non-default config values here or attach the full config as a gist or file.
Started with end to end testing enabled
--e2e-testing=true

Logs:
Console Log:
index.ts:470 Error
    at index.ts:116
    at :9999/async http:/localhost:9999/3.18328136f3.js:1
(anonymous) @ index.ts:470
async function (async)
(anonymous) @ index.ts:462
(anonymous) @ index.js:9
(anonymous) @ redux.js:449
Jg.handlePositionChange @ DashboardPage.tsx:254
Tg.handleLayoutChange @ Cells.tsx:132
t.onLayoutMaybeChanged @ ReactGridLayout.js:219
t.onResizeStop @ ReactGridLayout.js:324
(anonymous) @ GridItem.js:385
(anonymous) @ Resizable.js:168
ia @ react-dom.production.min.js:193
ra @ react-dom.production.min.js:193
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
Ms @ react-dom.production.min.js:245
es @ react-dom.production.min.js:243
enqueueSetState @ react-dom.production.min.js:130
_.setState @ react.production.min.js:13
(anonymous) @ Resizable.js:167
i.handleDragStop @ react-draggable.js:1010
Object.isExtensible.Object.isExtensible.e.___hb.e.___hb @ honeybadger.js:466
2react-dom.production.min.js:198 TypeError: Cannot destructure property 'keys' of 'en(...).queryBuilder.tags[t.index]' as it is undefined.
    at Function.mapToProps (TagSelector.tsx:272)
    at r (wrapMapToProps.js:41)
    at Function.r.mapToProps (wrapMapToProps.js:50)
    at r (wrapMapToProps.js:41)
    at selectorFactory.js:22
    at Object.run (connectAdvanced.js:22)
    at s.l.initSelector (connectAdvanced.js:182)
    at new Connect(dE) (connectAdvanced.js:119)
    at li (react-dom.production.min.js:132)
    at Oo (react-dom.production.min.js:167)
fa @ react-dom.production.min.js:198
Da.o.componentDidCatch.n.callback @ react-dom.production.min.js:211
ia @ react-dom.production.min.js:193
ra @ react-dom.production.min.js:193
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
As @ react-dom.production.min.js:251
Cn @ react-dom.production.min.js:85
Object.isExtensible.Object.isExtensible.e.___hb.e.___hb @ honeybadger.js:466
index.ts:734 Uncaught (in promise) TypeError: Cannot set property 'keysStatus' of undefined
    at Proxy.<anonymous> (index.ts:734)
    at e.value (immer.module.js:661)
    at Ai (index.ts:730)
    at timeMachines (index.ts:222)
    at redux.js:435
    at v (redux.js:213)
    at queryStringConfig.ts:10
    at resizeLayout.ts:7
    at middleware.js:22
    at index.js:9
(anonymous) @ index.ts:734
value @ immer.module.js:661
Ai @ index.ts:730
timeMachines @ index.ts:222
(anonymous) @ redux.js:435
v @ redux.js:213
(anonymous) @ queryStringConfig.ts:10
(anonymous) @ resizeLayout.ts:7
(anonymous) @ middleware.js:22
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:183
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:268
async function (async)
(anonymous) @ queryBuilder.ts:247
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:218
async function (async)
(anonymous) @ queryBuilder.ts:190
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:166
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:147
async function (async)
(anonymous) @ queryBuilder.ts:133
(anonymous) @ index.js:9
(anonymous) @ redux.js:449
componentDidMount @ QueryBuilder.tsx:41
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
As @ react-dom.production.min.js:251
Cn @ react-dom.production.min.js:85
Object.isExtensible.Object.isExtensible.e.___hb.e.___hb @ honeybadger.js:466
2react-dom.production.min.js:198 TypeError: Cannot destructure property 'keys' of 'en(...).queryBuilder.tags[t.index]' as it is undefined.
    at Function.mapToProps (TagSelector.tsx:272)
    at r (wrapMapToProps.js:41)
    at Function.r.mapToProps (wrapMapToProps.js:50)
    at r (wrapMapToProps.js:41)
    at selectorFactory.js:22
    at Object.run (connectAdvanced.js:22)
    at s.l.initSelector (connectAdvanced.js:182)
    at new Connect(dE) (connectAdvanced.js:119)
    at li (react-dom.production.min.js:132)
    at Oo (react-dom.production.min.js:167)
fa @ react-dom.production.min.js:198
Da.o.componentDidCatch.n.callback @ react-dom.production.min.js:211
ia @ react-dom.production.min.js:193
ra @ react-dom.production.min.js:193
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
As @ react-dom.production.min.js:251
Cn @ react-dom.production.min.js:85
Object.isExtensible.Object.isExtensible.e.___hb.e.___hb @ honeybadger.js:466
index.ts:734 Uncaught (in promise) TypeError: Cannot set property 'keysStatus' of undefined
    at Proxy.<anonymous> (index.ts:734)
    at e.value (immer.module.js:661)
    at Ai (index.ts:730)
    at timeMachines (index.ts:222)
    at redux.js:435
    at v (redux.js:213)
    at queryStringConfig.ts:10
    at resizeLayout.ts:7
    at middleware.js:22
    at index.js:9
(anonymous) @ index.ts:734
value @ immer.module.js:661
Ai @ index.ts:730
timeMachines @ index.ts:222
(anonymous) @ redux.js:435
v @ redux.js:213
(anonymous) @ queryStringConfig.ts:10
(anonymous) @ resizeLayout.ts:7
(anonymous) @ middleware.js:22
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:183
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:268
async function (async)
(anonymous) @ queryBuilder.ts:247
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:218
async function (async)
(anonymous) @ queryBuilder.ts:190
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:166
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:147
async function (async)
(anonymous) @ queryBuilder.ts:133
(anonymous) @ index.js:9
(anonymous) @ redux.js:449
componentDidMount @ QueryBuilder.tsx:41
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
As @ react-dom.production.min.js:251
Cn @ react-dom.production.min.js:85
Object.isExtensible.Object.isExtensible.e.___hb.e.___hb @ honeybadger.js:466

Also appears in Data Explorer

Open Data Explorer and create an initial query to where a graph is shown
Open home page
Open Data Explorer again

Same issue occurs
Screenshot

Console Log
TypeError: Cannot destructure property 'keys' of 'en(...).queryBuilder.tags[t.index]' as it is undefined.
    at Function.mapToProps (TagSelector.tsx:272)
    at r (wrapMapToProps.js:41)
    at Function.r.mapToProps (wrapMapToProps.js:50)
    at r (wrapMapToProps.js:41)
    at selectorFactory.js:22
    at Object.run (connectAdvanced.js:22)
    at s.l.initSelector (connectAdvanced.js:182)
    at new Connect(dE) (connectAdvanced.js:119)
    at li (react-dom.production.min.js:132)
    at Oo (react-dom.production.min.js:167)
fa @ react-dom.production.min.js:198
Da.o.componentDidCatch.n.callback @ react-dom.production.min.js:211
ia @ react-dom.production.min.js:193
ra @ react-dom.production.min.js:193
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
As @ react-dom.production.min.js:251
Cn @ react-dom.production.min.js:85
Object.isExtensible.Object.isExtensible.e.___hb.e.___hb @ honeybadger.js:466
2react-dom.production.min.js:198 TypeError: Cannot destructure property 'keys' of 'en(...).queryBuilder.tags[t.index]' as it is undefined.
    at Function.mapToProps (TagSelector.tsx:272)
    at r (wrapMapToProps.js:41)
    at Function.r.mapToProps (wrapMapToProps.js:50)
    at r (wrapMapToProps.js:41)
    at selectorFactory.js:22
    at Object.run (connectAdvanced.js:22)
    at s.l.initSelector (connectAdvanced.js:182)
    at new Connect(dE) (connectAdvanced.js:119)
    at li (react-dom.production.min.js:132)
    at Oo (react-dom.production.min.js:167)
fa @ react-dom.production.min.js:198
Da.o.componentDidCatch.n.callback @ react-dom.production.min.js:211
ia @ react-dom.production.min.js:193
ra @ react-dom.production.min.js:193
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
Ms @ react-dom.production.min.js:245
es @ react-dom.production.min.js:243
enqueueSetState @ react-dom.production.min.js:130
_.setState @ react.production.min.js:13
l.onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
t.notifyNestedSubs @ Subscription.js:62
l.onStateChange @ connectAdvanced.js:204
notify @ Subscription.js:23
t.notifyNestedSubs @ Subscription.js:62
l.onStateChange @ connectAdvanced.js:204
notify @ Subscription.js:23
t.notifyNestedSubs @ Subscription.js:62
l.onStateChange @ connectAdvanced.js:204
v @ redux.js:220
(anonymous) @ queryStringConfig.ts:10
(anonymous) @ resizeLayout.ts:7
(anonymous) @ middleware.js:22
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ index.ts:150
async function (async)
(anonymous) @ index.ts:148
(anonymous) @ index.js:9
(anonymous) @ redux.js:449
getResourceDetails @ GetResources.tsx:133
(anonymous) @ GetResources.tsx:105
componentDidMount @ GetResources.tsx:104
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
As @ react-dom.production.min.js:251
Cn @ react-dom.production.min.js:85
Object.isExtensible.Object.isExtensible.e.___hb.e.___hb @ honeybadger.js:466
Show 2 more frames
index.ts:734 Uncaught (in promise) TypeError: Cannot set property 'keysStatus' of undefined
    at Proxy.<anonymous> (index.ts:734)
    at e.value (immer.module.js:661)
    at Ai (index.ts:730)
    at timeMachines (index.ts:222)
    at redux.js:435
    at v (redux.js:213)
    at queryStringConfig.ts:10
    at resizeLayout.ts:7
    at middleware.js:22
    at index.js:9
(anonymous) @ index.ts:734
value @ immer.module.js:661
Ai @ index.ts:730
timeMachines @ index.ts:222
(anonymous) @ redux.js:435
v @ redux.js:213
(anonymous) @ queryStringConfig.ts:10
(anonymous) @ resizeLayout.ts:7
(anonymous) @ middleware.js:22
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:183
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:268
async function (async)
(anonymous) @ queryBuilder.ts:247
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:218
async function (async)
(anonymous) @ queryBuilder.ts:190
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:166
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ queryBuilder.ts:147
async function (async)
(anonymous) @ queryBuilder.ts:133
(anonymous) @ index.js:9
(anonymous) @ redux.js:449
componentDidMount @ QueryBuilder.tsx:41
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
Ms @ react-dom.production.min.js:245
es @ react-dom.production.min.js:243
enqueueSetState @ react-dom.production.min.js:130
_.setState @ react.production.min.js:13
l.onStateChange @ connectAdvanced.js:207
notify @ Subscription.js:23
t.notifyNestedSubs @ Subscription.js:62
l.onStateChange @ connectAdvanced.js:204
notify @ Subscription.js:23
t.notifyNestedSubs @ Subscription.js:62
l.onStateChange @ connectAdvanced.js:204
notify @ Subscription.js:23
t.notifyNestedSubs @ Subscription.js:62
l.onStateChange @ connectAdvanced.js:204
v @ redux.js:220
(anonymous) @ queryStringConfig.ts:10
(anonymous) @ resizeLayout.ts:7
(anonymous) @ middleware.js:22
(anonymous) @ index.js:9
dispatch @ redux.js:563
(anonymous) @ index.ts:150
async function (async)
(anonymous) @ index.ts:148
(anonymous) @ index.js:9
(anonymous) @ redux.js:449
getResourceDetails @ GetResources.tsx:133
(anonymous) @ GetResources.tsx:105
componentDidMount @ GetResources.tsx:104
Wa @ react-dom.production.min.js:216
Ba @ react-dom.production.min.js:220
(anonymous) @ react-dom.production.min.js:250
t.unstable_runWithPriority @ scheduler.production.min.js:18
Ps @ react-dom.production.min.js:250
Rs @ react-dom.production.min.js:249
Ls @ react-dom.production.min.js:248
As @ react-dom.production.min.js:251
Cn @ react-dom.production.min.js:85
Object.isExtensible.Object.isExtensible.e.___hb.e.___hb @ honeybadger.js:466
Show 28 more frames

Note this is not happening with cells in dashboards generated from templates.

@karel-rehor can you check to see if this is still happening? I believe it should have been resolved by e52705d2b1f3f2949d46ad8aad48c159ef54ff32

@desa in the latest nightly build both the Dashboard and the Data Explorer use cases seem to be working normally again.
ts=2019-12-05T09:12:46.226260Z lvl=info msg="Welcome to InfluxDB" log_id=0JXLAg_W000 version=nightly commit=5f19c6cac build_date=2019-12-05T07:25:48Z

closing

source: gharchive/issue

authors: desa karel-rehor

repo: influxdata/influxdb

license_type: permissive

license_source: github-api


text:
Search all InfluxData sources Curl add data to influxdb says {“error”:”unable to parse invalid field format”}

Hello Team,
I am trying to add data with below curl command but it gives error
echo -e “usage,host=influxdb,cluster=louis,pl_instance_name=2i-retegas,gitlabusage=“Thu Oct 20 13:48:02 2022”,jenkinsusage=“Fri Jan 20 06:52:05 2023”,sonarqubeusage=“Mon Oct 17 11:52:20 2022”,nexususage=“Not Use 00 00:00:00 0000” lastused=averagetime” | curl -X POST --data-binary @- https://influxdb-.com/write?db=usage
error
{“error”:“unable to parse ‘usage,host=influxdb,cluster=louis,pl_instance_name=2i-retegas,gitlabusage=Thu Oct 20 13:48:02 2022,jenkinsusage=Fri Jan 20 06:52:05 2023,sonarqubeusage=Mon Oct 17 11:52:20 2022,nexususage=Not Use 00 00:00:00 0000 lastused=averagetime’: invalid field format”}
can you please guide what I am missing here I tried to escape space with \ but no luck
Regards,
SAM

I believe you need to escape every space in each of the tag values. The following LP inserts fine for me:
usage,host="influxdb",cluster="louis",pl_instance_name="2i-retegas",gitlabusage="Thu\ Oct\ 20\ 13:48:02\ 2022",jenkinsusage="Fri\ Jan\ 20\ 06:52:05\ 2023",sonarqubeusage="Mon\ Oct\ 17\ 11:52:20\ 2022",nexususage="Not\ Use\ 00\ 00:00:00\ 0000" lastused="averagetime"

Thank you @jeffreyssmith2nd  I have corrected it,


text:
[0.13.0~rc1] Unable to start - config parse issue

InfluxDB: version 0.13.0~rc1, branch 0.13, commit c6518b564fd6044652e319f33a477b28fc92f28f (official packages)
OS: Ubuntu 14.04
:~# influxd -config /etc/influxdb/influxdb.conf

 8888888           .d888 888                   8888888b.  888888b.
   888            d88P"  888                   888  "Y88b 888  "88b
   888            888    888                   888    888 888  .88P
   888   88888b.  888888 888 888  888 888  888 888    888 8888888K.
   888   888 "88b 888    888 888  888  Y8bd8P' 888    888 888  "Y88b
   888   888  888 888    888 888  888   X88K   888    888 888    888
   888   888  888 888    888 Y88b 888 .d8""8b. 888  .d88P 888   d88P
 8888888 888  888 888    888  "Y88888 888  888 8888888P"  8888888P"

[run] 2016/05/07 16:32:36 InfluxDB starting, version 0.13.0~rc1, branch 0.13, commit c6518b564fd6044652e319f33a477b28fc92f28f
[run] 2016/05/07 16:32:36 Go version go1.6.2, GOMAXPROCS set to 4
[run] 2016/05/07 16:32:36 Using configuration at: /etc/influxdb/influxdb.conf
run: parse config: Near line 0 (last key parsed ''): Bare keys cannot contain '/'.

or just simple:
:~# influxd config
config: parse config: Near line 0 (last key parsed ''): Bare keys cannot contain '/'.
:/etc/influxdb# ls -al
total 12
drwxr-xr-x   2 root     root     4096 May  7 16:13 .
drwxr-xr-x 114 root     root     4096 May  7 16:12 ..
-rw-r--r--   1 influxdb influxdb 2053 May  7 16:12 influxdb.conf.old
:/etc/influxdb# influxd config > influxdb.conf
config: parse config: Near line 0 (last key parsed ''): Bare keys cannot contain '/'.
:/etc/influxdb# ls -al
total 12
drwxr-xr-x   2 root     root     4096 May  7 16:13 .
drwxr-xr-x 114 root     root     4096 May  7 16:12 ..
-rw-rw-r--   1 root     root        0 May  7 16:13 influxdb.conf
-rw-r--r--   1 influxdb influxdb 2053 May  7 16:12 influxdb.conf.old

As soon there is /etc/influxdb/influxdb.conf config parse crash. Without that file it's possible to run influxd config.
I'm suspecting it might be result of https://github.com/influxdata/influxdb/commit/9c0902350802e6a353d481b1e1c28858f0ae772b
With or without environment variable is the same.

@ljagiello Thanks for the report, I'm seeing the same thing.
@jsternberg Do you know why this might be happening? I'm getting the same error when running with a blank configuration as well:
[run] 2016/05/08 04:13:58 InfluxDB starting, version 0.13.0~rc1, branch 0.13, commit c6518b564fd6044652e319f33a477b28fc92f28f
[run] 2016/05/08 04:13:58 Go version go1.6.2, GOMAXPROCS set to 1
[run] 2016/05/08 04:13:58 Using configuration at: blank-conf
run: parse config: Near line 0 (last key parsed ''): Bare keys cannot contain '\n'.

Where with 0.12.2, a blank configuration would have thrown this error:
[run] 2016/05/08 04:15:19 InfluxDB starting, version 0.12.2, branch 0.12, commit 383332daed5595926c235f250b11433f67229c35
[run] 2016/05/08 04:15:19 Go version go1.4.3, GOMAXPROCS set to 1
[run] 2016/05/08 04:15:19 Using configuration at: blank-conf
run: Meta.Dir must be specified. To generate a valid configuration file run `influxd config > influxdb.generated.conf`

It seems like maybe the config path is being interpreted as the configuration contents?

same issue for me, on the 0.13.0-rc1.
Itried adding a config file, modifiy the existing config file but it throws the same error.
Compiling with go-1.6.2.

master branch is working ok.

Ok so the problem is commit - 3c3f7be3551969124d703d9cb569c9e65009a87e
It's not in master branch but it's in 0.13. If I revert that commit from 0.13 it's working fine again.

Fixed here: https://github.com/influxdata/influxdb/pull/6579

authors: ljagiello rossmcdonald vincentserpoul


text:
Silently discarding data on invalid timestamp

InfluxDB returns 204 but silently discards data when the timestamp is not in Nanoseconds and precision hasn't been set.
Tested query:
curl -XPOST -v 'http://192.168.133.40:8086/write?consistency=&db=infping&precision=&rp=default' --data 'ping,host=146.148.116.51 avg=18.8,loss=0i,max=19.2,min=18.5 1472128844'
*   Trying 192.168.133.40...
* Connected to 192.168.133.40 (192.168.133.40) port 8086 (#0)
> POST /write?consistency=&db=infping&precision=&rp=default HTTP/1.1
> Host: 192.168.133.40:8086
> User-Agent: curl/7.43.0
> Accept: */*
> Content-Length: 70
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 70 out of 70 bytes
< HTTP/1.1 204 No Content
< Request-Id: eda70a56-6ac3-11e6-8914-000000000000
< X-Influxdb-Version: 1.0.0-beta3
< Date: Thu, 25 Aug 2016 13:00:41 GMT
<
* Connection #0 to host 192.168.133.40 left intact

You'll notice that we got a return of 204 No Content which according to the docs is everything was accepted without issue.
On the influx server itself:
Visit https://enterprise.influxdata.com to register for updates, InfluxDB server management, and monitoring.
Connected to http://localhost:8086 version 1.0.0-beta3
InfluxDB shell version: 1.0.0-beta3
> show databases
name: databases
---------------
name
_internal
infping

> use infping
Using database infping
> show series
> show measurements
>

If we do the curl without the timestamp this shows up as expected same with setting precision to s
According to the documentation this should be returning a 200 error

Looks like the data is probably being "written" to a time further in the past than the retention policy would have retained.
Here's a minimal repro script and its output:
#!/bin/sh

set -e

echo "creating database"
curl -XPOST http://localhost:8086/query --data-urlencode "q=CREATE DATABASE short WITH DURATION 1d"

echo "writing current data, should be accepted"
curl -v -XPOST http://localhost:8086/write?db=short --data-binary "ctr n=100i" # no timestamp, should be properly accepted

echo "writing old data, should be discarded"
curl -v -XPOST http://localhost:8086/write?db=short --data-binary "ctr n=1i 123" # timestamp WAY in the past

creating database
{"results":[{}]}writing current data, should be accepted
*   Trying ::1...
* Connected to localhost (::1) port 8086 (#0)
> POST /write?db=short HTTP/1.1
> Host: localhost:8086
> User-Agent: curl/7.43.0
> Accept: */*
> Content-Length: 10
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 10 out of 10 bytes
< HTTP/1.1 204 No Content
< Request-Id: f4667c97-6ad7-11e6-8006-000000000000
< X-Influxdb-Version: 1.0.0-beta3
< Date: Thu, 25 Aug 2016 15:24:03 GMT
<
* Connection #0 to host localhost left intact
writing old data, should be discarded
*   Trying ::1...
* Connected to localhost (::1) port 8086 (#0)
> POST /write?db=short HTTP/1.1
> Host: localhost:8086
> User-Agent: curl/7.43.0
> Accept: */*
> Content-Length: 12
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 12 out of 12 bytes
< HTTP/1.1 204 No Content
< Request-Id: f46e7212-6ad7-11e6-8007-000000000000
< X-Influxdb-Version: 1.0.0-beta3
< Date: Thu, 25 Aug 2016 15:24:03 GMT
<
* Connection #0 to host localhost left intact

Confirmed behavior on 1.0.0-beta3 and master at a30f9b6c70d1f5cc9003171a2a2f2a771701ae92.
Probably related to #6919. Thoughts @jsternberg?

If you're writing data to a retention policy that's older than the retention policy allows, this is expected. The data was written successfully, it was just immediately deleted. We drop it because we don't want to go through the work of creating a shard for it just to be deleted very soon after.

Ahhh that would make sense, the retention policy was set to 4 weeks thanks @jsternberg @mark-rushakoff

authors: jsternberg liv3d mark-rushakoff


text:
Changing UDP precision can corrupt default timestamp decoding

Bug report
System info: InfluxDB 1.2, Debian Stretch
Steps to reproduce:
I started by creating a new database, importing old data into it, which had been input using influx's http api, most of them with precision=ms.
I then enabled the udp api, didn't specify a precision and started writing measurements without including a timestamp. Everything was okay; I then set precision="s", everything was still okay but at that point I found out I needed higher precision accuracy, so I switched the udp input to ms (still not sending timestamps through udp).
In doing so, all new timestamps are now off by a factor of 1000. I then changed udp.precision back to an empty string, but timestamps are now still off by 1000x. In fact, if I change it to anything else than "s", it's broken.
I don't understand how this behaviour makes sense. The UDP writer should know what unit to use to write to the database; the input precision setting should only be used for decoding timestamp values. When a timestamp value is not specified, it should set the precision of the value it generate, but when writing it to influx it should still know to write a correct timestamp.
In other words, setting the precision without specifying a timestamp should never write bad timestamps; and precision="" should especially not write bad timestamps.

Thinking through the code:

The parsing happens here in service.go, using ParsePointsWithPrecision with a default time.Now().UTC().
This jumps to parsePoint, passing the precision argument.
We call scanTime(), which sets the .ts attribute to the timestamp string
We then create a point as pt, pt.ts is the timestamp string
if pt.ts is empty, pt.time is set to defaultTime and pt.SetPrecision(precision) is called.
Doing so truncates the time to match that precision.

okay, wtf? I dropped and recreated the database and it still has the same issue unless I use s precision.


text:
fix: removing default sort on tables

this addresses influxdata/ear#1644
the current default behavior is to implement a sort on the first column returned from the backend. this over-writes any sort that was explicitly defined in the query and not in the interface. i made it return data just like it came back from the server unless the user specifies a sort in the view options.
weary about the product level consequences, so i'm wrapping it in a flag to let russ click around before removing the flag

i would need to do that if rolling out to users required config cat (for reverting live code or whatever), but right now i just need sign off from product that this is what they want

source: gharchive/pull-request


text:
check admin exists instead of user count

Required for all non-trivial PRs

[x] Rebased/mergable
[ ] Tests pass
[x] CHANGELOG.md updated

When authenticating a request, check that an admin user exists instead
of checking for len(users) > 0. This prevents getting stuck with no
admin users and being unable to create one.

LGTM 👍
Note that this will probably require a change to the wording in the docs

Note: If you enable authentication and have no users, InfluxDB will not enforce authentication and will only accept the query that creates a new admin user. InfluxDB will enforce authentication once there is an admin user.

Should probably say something like ...and have no admin users... /cc @rkuchan

authors: dgnorton e-dard


text:
Fix data race in WAL

Fixes #9577.
This PR fixes a data race in the WAL, which can occur when writes and deletes are being executed concurrently. The WAL uses a buffer pool of []byte when reading from the log. WAL entries are unmarshaled into these buffers and passed along to the relevant methods handling the different
types of entry (write, delete etc).
In the case of deletes, the keys that need to be deleted were being stored for later processing, however these keys were part of the backing array of initial buffer from the pool. As such, those keys could be written to at a future time when handling other parts of the WAL.
The original bug can be triggered as follows:
$  go test -c -race github.com/influxdata/influxdb/tsdb
$ repeat 100 ./tsdb.test -test.run TestStore_Sketches

In master the race should appear after a few iterations. I've ran a few hundred iterations on this PR and it's 🍏 📗 💚

.hooks/pre-commit 100755 → 100644

Removing the executable bit looks unintentional and unrelated to the fix.

authors: e-dard mark-rushakoff


text:
Error found when convert int to float

This is the error found in /var/log/kapacitor/kapacitor.log:
[system_load:eval2] 2017/06/15 13:55:29 E! Cannot call function "float" with args signature (missing), available signatures are [(boolean), (string), (int), (float)].

And this is the system_load tickscript:
    |from()
        .database('telegraf')
        .retentionPolicy('autogen')
        .measurement('system')
        .groupBy('host', 'inst')
    |eval(lambda: "load1" / float("n_cpus"))
        .as('perload')
    |alert()
        .id('{{ index .Tags "host" }}/{{ index .Tags "inst" }}')
        .message('{{ .Level}}: {{ .ID }} has high perload: {{ index .Fields "perload" }}')
        .stateChangesOnly()
        .crit(lambda: "perload" > 0.5)
        .exec('/data/mysqlscript/tick/alarm.py')```

This error continue to appear in error log,  but the question is, the alert still be triggered correctly...
So what does the error mean?

@nathanielc Can you look into this?
I tried the above script and even I am facing issue.
Kapacitor version: v1.3.1

@zhangleqi It means that the n_cpus field is missing from some of your data points. I am not sure why and that error message is horrible. We have an open issue to improve the error message see https://github.com/influxdata/kapacitor/issues/1452
The reason the alert still works is that the points that are missing the n_cpus field are simply dropped. Since other points do have the field they make it through to the alert node just fine.

authors: adityacs nathanielc zhangleqi

repo: influxdata/kapacitor

license: MIT


text:
Update line protocol to require trailing i for field values that are integers

Many people have reported problems with writing data in and confusion around when a number is a float64 or an int64. Because we take the type of the first written value as that field's type for the measurement, it's causing errors for people later on.
I briefly thought of dropping support for ints (#3479) to make things easier, but it looks like enough people really want them still. So, this will solve the usability problem and give people the ability to still have integers.
After this change in the line protocol, any number in a field will be parsed as a float64, unless that number has a trailing i. Examples:
# here are some float64 values
cpu,host=A value=0
cpu,host=A value=23
cpu,host=A value=23.2

# here are some int64 values
cpu,host=A value=0i
cpu,host=A value=23i

# here is an invalid write that throws an error
cpu,host=A value=23.2i

This will be a breaking change between 0.9.2 and 0.9.3. Hopefully it is small enough that client libraries can be updated with little effort. We had no plan to make breaking changes in the 0.9 line, but this seems the best course of action and it's best to get it out of the way as soon as possible. It's also a very small change.
Apologies for the breakage, but it's our best bet to fix usability and keep those who want integers happy.

Completed in https://github.com/influxdb/influxdb/pull/3526

In the future (or next release) having an intermediate version which supports both versions would be helpful. e.g. the i is optional, and numbers parsed as usual (unless i present)
Then in the next version enforce non-decimal as floats.
Reason being that we can't upgrade without simultaneous client + db update which increases downtime

Is there any way to convert exiting data from int to floats?

@jgeiger sadly not currently without re-writing all the data.  @pauldix any thoughts on a utility to do this in the future?

@corylanou it would be pretty tricky to create a utility for this, particularly now that we have multiple storage engines that can exist. Not something that can't be done, but we're unlikely to get to it in the next 2 months.

What about automatically casting numeric values to integers for series that previously held integers? That is to say, make this:
cpu,host=A value=23

Equivalent to this:
cpu,host=A value=23i

If and only if the measurement type is an integer. By doing this 1) you would ensure a smooth non-breaking transition for 0.9.2 users while 2) enforcing float64 by default for new measurements unless values are provided with the 'i' trailing character.
The reason I suggest this is that in our case we tested 0.9.3 today and decided to stay with 0.9.2 for the time being, because figuring out how to properly upgrade our queries in such a way that it works with our existing data is a pain; we can't know the type of an existing measurement in all cases to properly adjust the query since this happened behind the scenes previously.

I agree with @jportoles even if the change is only in effect for 0.9.3 and removed in 0.9.4 for smooth upgrade purposes

authors: Zolmeister corylanou jgeiger jportoles pauldix

repo: influxdb/influxdb

license: mit

license_source: bigquery


text:
[0.9.5.1] database seems to be storing null values with INTO queries

An INTO query with a single function doesn't report null values:
> select min(source) into mins from mymeas where time >= '2015-12-15T00:11:54.354492928Z' and time <= '2015-12-15T00:13:40.956464882Z' group by time(1m)
> select * from mins
{
    "results": [
        {
            "series": [
                {
                    "name": "mins",
                    "columns": [
                        "time",
                        "min"
                    ],
                    "values": [
                        [
                            "2015-12-15T00:11:00Z",
                            1
                        ],
                        [
                            "2015-12-15T00:13:00Z",
                            8
                        ]
                    ]
                }
            ]
        }
    ]
}

An INTO query with more than one function does report null values:
> select min(source), max(source) into minmax from mymeas where time >= '2015-12-15T00:11:54.354492928Z' and time <= '2015-12-15T00:13:40.956464882Z' group by time(1m)
> select * from minmax
{
    "results": [
        {
            "series": [
                {
                    "name": "minmax",
                    "columns": [
                        "time",
                        "max",
                        "min"
                    ],
                    "values": [
                        [
                            "2015-12-15T00:11:00Z",
                            2,
                            1
                        ],
                        [
                            "2015-12-15T00:12:00Z",
                            null,
                            null
                        ],
                        [
                            "2015-12-15T00:13:00Z",
                            89,
                            8
                        ]
                    ]
                }
            ]
        }
    ]
}

@rkuchan can you test this against TSM? If there's no issue there I'm going to close this out since the other engines will be going away in 0.10.0

@pauldix, there's no issue with tsm1.

It looks like this works correctly now with tsm1, but I'm also going to include something to automatically switch any fill(null) calls to fill(none) since fill(null) is the default. I don't think there's any time where a fill(null) call makes sense in the context of an INTO query.

authors: jsternberg pauldix rkuchan


text:
0.9.6.1 shows gaps

First off, I think this version has so far been pretty stable, congrats for that.
However since we upgraded to this version we see some temporary gaps that then automatically disappear.
As a reminder, we push metrics via UDP (we have a few UDP ports and we hash our metrics through them). I looked into our injection logs and it does not show any gap on writing (also the injection part has not changed in the last weeks), the same thing goes with the influxdb logs. The closest to a non query/http entry is:
[retention] 2015/12/23 19:14:25 retention policy shard deletion check commencing
[retention] 2015/12/23 19:14:25 retention policy enforcement check commencing
[tsm1] 2015/12/23 19:15:21 compacted 22 tsm into 1 files in 3m6.078521546s
[tsm1] 2015/12/23 19:15:21 compacting 4 TSM files
[tsm1] 2015/12/23 19:15:42 compacted 4 tsm into 1 files in 20.213362013s
[tsm1] 2015/12/23 19:16:22 compacting 3 TSM files
[tsm1] 2015/12/23 19:16:52 compacted 3 tsm into 1 files in 30.479634201s
[tsm1] 2015/12/23 19:16:52 compacting 3 TSM files
[retention] 2015/12/23 19:44:25 retention policy enforcement check commencing
[retention] 2015/12/23 19:44:25 retention policy shard deletion check commencing
Any other graphs or stats you find worthy? You have a grafana dashboard that uses _internal that I could copy and use?

Forgot to mention that this is our influxdb config:
reporting-disabled = true

[meta]
  dir = "/usr/local/var/influxdb/meta"
  bind-address = ":8088"
  retention-autocreate = true
  election-timeout = "1s"
  heartbeat-timeout = "1s"
  leader-lease-timeout = "500ms"
  commit-timeout = "50ms"
  cluster-tracing = false

[data]
  dir = "/usr/local/var/influxdb/data"
  engine = "tsm1"
  max-wal-size = 1073741824
  wal-flush-interval = "2m0s"
  wal-max-memory-size-threshold = 524288000
  wal-partition-flush-delay = "2s"
  wal-dir = "/usr/local/var/influxdb/wal"
  wal-logging-enabled = true
  wal-ready-series-size = 30720
  wal-compaction-threshold = 0.5
  wal-max-series-size = 1048576
  wal-flush-cold-interval = "5s"
  wal-partition-size-threshold = 20971520

[cluster]
  force-remote-mapping = false
  write-timeout = "5s"
  shard-writer-timeout = "5s"
  shard-mapper-timeout = "5s"

[retention]
  enabled = true
  check-interval = "30m0s"

[shard-precreation]
  enabled = true
  check-interval = "10m0s"
  advance-period = "30m0s"

[admin]
  enabled = true
  bind-address = ":8083"
  https-enabled = false
  https-certificate = "/usr/local/conf/influxdb/ssl/influx.pem"

[monitor]
  store-enabled = true
  store-database = "_internal"
  store-interval = "10s"

[http]
  enabled = true
  bind-address = ":8086"
  auth-enabled = false
  log-enabled = true
  write-tracing = false
  pprof-enabled = false
  https-enabled = false
  https-certificate = "/usr/local/conf/influxdb/ssl/influx.pem"

[collectd]
  enabled = false
  bind-address = ":25826"
  database = "collectd"
  retention-policy = ""
  batch-size = 1000
  batch-pending = 5
  batch-timeout = "10s"
  typesdb = "/usr/share/collectd/types.db"

[opentsdb]
  enabled = false
  bind-address = ":4242"
  database = "opentsdb"
  retention-policy = ""
  consistency-level = "one"
  tls-enabled = false
  certificate = "/usr/local/conf/influxdb/ssl/influx.pem"
  batch-size = 1000
  batch-pending = 5
  batch-timeout = "1s"

[continuous_queries]
  log-enabled = true
  enabled = true
  recompute-previous-n = 2
  recompute-no-older-than = "10m0s"
  compute-runs-per-interval = 10
  compute-no-more-than = "2m0s"

[hinted-handoff]
  enabled = true
  dir = "/usr/local/var/influxdb/hh"
  max-size = 1073741824
  max-age = "168h0m0s"
  retry-rate-limit = 0
  retry-interval = "1s"

[[udp]]
enabled = true
bind-address = ":4340"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4341"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4342"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4343"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4344"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4345"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4346"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4347"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4348"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4349"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4440"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4441"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4442"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4443"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4444"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4445"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4446"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4447"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4448"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

[[udp]]
enabled = true
bind-address = ":4449"
database = "metrics"
batch-size = 1000
batch-pending = 5
batch-timeout = "1s"

We saw something very similar to this. You generally wont see error logs, if you are dropping. Do you see drops in the kernel (ss) - we did when we went digging.
You may want to review https://github.com/influxdb/influxdb/pull/5201 and/or move to a nightly since yesterday. Combined with https://github.com/influxdb/influxdb/issues/5217 and moving our WAL onto a very, very high performing IO device we believe we have eliminated drops.

concur with @daviesalex recommendation, especially given the sheer number of udp endpoints you have. Out of curiosity, are you using telegraf for your metrics engine or a custom generator?

thanks. I'll give a try to nightly and increase our UDP payload on the config (we already increased our UDP buffer via sysctl).
As wrt to telegraph, no, I've a perl script that pulls data from ganglia and then throws it to influxdb. It has been working fairly well, each ganglia host forks into a new process and then the metrics are sent to influxdb with a hash load-balancing algo (just based on metric name).

Are you still seeing this with 0.10 nightlies?

authors: daviesalex jwilder pfischermx sebito91


text:
🛑 alternative site is down

In 3a92b2c, alternative site (https://almgro7al3nzy.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: alternative site is back up in e6ccae6 after 10 minutes.


text:
🛑 alternative site is down

In 1bde7d6, alternative site (https://almgro7al3nzy.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: alternative site is back up in 1027d66 after 18 minutes.


text:
🛑 alternative site is down

In b505d79, alternative site (https://almgro7al3nzy.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: alternative site is back up in 04151f5 after 19 minutes.


text:
Compile chain binary from remote

Closes #111
Example usage,
atomkraft init transfer
cd transfer
atomkraft chain remote gh:cosmos/cosmos-sdk --ref v0.45.8
...
atomkraft test trace ...

I need this feature to write tests for methods used in chain subcommands.

repo: informalsystems/atomkraft


text:
feat: create local genesis devnets

there are some commont scripts place like
https://github.com/cosmology-tech/starship/blob/main/charts/devnet/scripts/neutron/create-neutron-genesis.sh
or custom
https://github.com/osmosis-labs/osmosis/blob/main/tests/localosmosis/scripts/setup.sh
these scripts allow to setup local devnet
so cosmos.nix could use these to provide default devnets on top of just binaries

nix does not need docker or helm, but nix can reuse starship bash and be like starship

I also looked into creating nixos modules to facilitate nixos tests (which support arbitrary number of nodes via qemu). Unfortunately spinning up chains is extremely imperative and stateful and was hard for me to get right. I think there are a lot of solutions that could work here.

yeah. port binding is one of issues which hard to handle. so in theory can do most common/representative nodes so(cosmos hub, cosmwasm node).
so reusing existing sh files worked well. and starship genesises work well enough. but need more thinking.

nixos tests (which support arbitrary number of nodes via qemu).

nice, where can I read about this? never saw such setup

@dzmitry-lahoda the documentation is really awful, but here is a small piece https://nix.dev/tutorials/nixos/integration-testing-using-virtual-machines.html
You can also look some of the experimental work I did here and here. Not shown in the git tree is that I manually generated the data dirs for the chains and simply referenced them in the tests. Ideally initializing the chains would be reproducible and declarative as well.

I think there are a lot of solutions that could work here.

yeah. seems direct reuse of bash in bad idea in general eventually. but assuming startship catches up, it is best one, just follow starship.  but as of now not so many published startship modules. so it may be deadend.
as of nix, it can git reuse bash from chains from start.
and later it can have nixos modules with default and override accounts and bash sub scripts to init account amounts.
as of now I maintain 3 chains in simpler way, will have to do afaik +2 more. so total 5 cosmos chains.
my current approach is stupid - copy bash into my nix, use ${....} to plug shared parameters.
run post gen pos run scripts to setup IBCs

I think there needs to be more planning around this, but its something we should support. Would you be willing to either sketch out the approach in pseudo code / a comment, or propose a simple PR with a proof of concept?

I guess alignment is first.
I will described how I ended up in https://github.com/ComposableFi/composable/blob/main/flake/process-compose.nix .
Before I ended up with process-compose solution, I considered(and tried) docker/podman/systemd/launchd/k8s and several others process managers. I have experience in k8s, but not local.
There are 2 faces - end user functional area(QA/xdapps deps/FE) and developer area(nix developer).

I think end user wants lightweight portable any CPU rootless zero config dashboarded way to run set of process.
So:
docker - needs root to setup and some config, not lightweights until build OCI image which is not container
k8s - how same config portable accross all machines
both above are fat (need big image), so alfa hacks not to build image like this nix-snapshotter or some articles about OCI structure.
so not really ready or cool.
podman - config, without root possible, but limited, not slick/documented/compatibe as docker
systemd/launchd - seems may be, as soon as some nixd project will unify both under same module, so it is blocker. i am nix tooling user - not writer. but if such exists - i would look at it very sure. problem - not all linuxes are systemd.
pure linux sucks as process manager, there are several attemps to write own (all so so tbh), and some like parity wrote their own (zombienet). the have DSL which allows to emit podman/k8s/native (native basically their own written process manager - it sucks tbh - no dashboard).
so i stayed with process-manager-flake - risk it is only 300 starts, not 3000k, so dev is reponsive.

Another topic for nix devs, is how to stucture configs and share/reuse genesis overrides/generators.
Structure codes - process-compose-flake and terranix has nice examples of modules usage out of nixos, and also https://discourse.nixos.org/t/best-resources-for-learning-about-the-nixos-module-system/1177
Seems like each chain to be module for dynamic composition via eval (my current nix is static). But need to design modules first.
Other question how to share scripts?
Reuse from repo of chain team? From starship? Wrap TS/Python they have for cooking as nix commands? Write own bash? Generated from scrach in pure nix? Cosmos SDK genesis builder?
I found using bash(and linux cli tools) and anything chain team has is best approach. Do not write TS, wait TS/GO/Python tools emerge works for me.
So need design for modules and pick 2/3 chains to start first (Cosmos Hub/CosmWasm simulator seems may be good to go for devs).
And also realyers not dicussed - so bash and tools to for me.
At least this apprach supports ether/polkadot/cosmsos and soon(sure sure) solana ibc.

Also I think these people are ready https://developers.openibc.com/docs/category/ibctl-cli-tool ? I think they are alfa and not flexible.
Same as osmosis beaker.
So really nix + modules + bash(dasel/jq/base64/tar+each teach tooling) + process compose is like way to processed.
Modules need desing

@JonathanLorimer  TLRD;
First need to align on process manager, I am for process-compose; OR for OCI with only link to /nix/store, but not all closures copied, whatever runner - k8s, docker, podman; OR systemd/launchd.
OCI as it is built

here is module model for process-compose https://github.com/juspay/services-flake
so not sure if it is good one.
how to express graph dependencies, for example that relayer depends on 2 chains?

as i need this now and multi chain (not only cosmos) and need from shell from devnet to mainnet, i go for now:

https://github.com/ComposableFi/networks
process-compose

please consider moving cosmos.nix to cosmos org to allow improved collaboration on devnets if needed.

as i see set of configs can be
BINARY=${BINARY:-neutrond}
BASE_DIR=./data
CHAINID=${CHAINID:-test-1}
FEEDENOM=STAKEDENOM
STAKEDENOM=${STAKEDENOM:-untrn}
CHAIN_DIR="$BASE_DIR/$CHAINID"

P2PPORT=${P2PPORT:-26656}
RPCPORT=${RPCPORT:-26657}
RESTPORT=${RESTPORT:-1317}
ROSETTA=${ROSETTA:-8081}
``
kind of cosmos-sdk subset.

other things - jq/sed is bearshish. sed may overwrite good value. so seems dasel is most structured and universal for rewrite of toml/json/yaml.

authors: JonathanLorimer dzmitry-lahoda


text:
Have a metric on failed transactions

Summary
I am setting up a relayer right now and am thinking of which metrics to build alerts upon. Somehow the relayer is misconfigured apparently (this part is not in the scope of this feature request, but helps illustrating what I want to have) and I have the following errors in logs somehow:
2024-01-14T20:14:36.847866Z ERROR ThreadId(17) worker.batch{chain=sentinelhub-2}:supervisor.handle_batch{chain=sentinelhub-2}:supervisor.process_batch{chain=sentinelhub-2}:worker.packet.cmd{src_chain=sentinelhub-2 src_port=transfer src_channel=channel-0 dst_chain=osmosis-1}:relay{odata=3c3befd3 ->Destination @2-14490644; len=1}:send_messages_and_wait_check_tx{chain=osmosis-1 tracking_id=3c3befd3}:send_tx_with_account_sequence_retry{chain=osmosis-1 account.sequence=245}: failed to broadcast tx with unrecoverable error response=Response { code: Err(11), data: b"", log: "out of gas in location: WritePerByte; gasWanted: 300000, gasUsed: 504515: out of gas", hash: Hash::Sha256(BF7F0D4C3AA977AC027FB0D031F0D08D78B4C3003C896C2BDA22F26DADA2861B) } diagnostic=the gas requirement is higher than the configured maximum gas! please check the Hermes config.toml

I want to be aware if a transaction fails due to something misconfigured in relayer (whether I misconfigured it from the beginning, or if the chain settings changed in some way, or if the node is faulty etc.)
For that I need some metric indicating the amount of transactions that failed (apparently Hermes knows that it was failed), ideally with labels as src/dst chain/channel and error type/code.
I couldn't find anything similar in /metrics response (please let me know if this is already in place), hence this feature request.

Problem Definition

See above.
Proposal

Have a metric in metric set returned by Hermes that displays the amount of failed transaction by src/dst chain/channel and error code.
Acceptance Criteria
See "Proposal".

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Ouch, just found broadcast_errors_total and it seems to be exactly what I was looking for. Sorry :(

repo: informalsystems/hermes


text:
Test informalsystems/cosmos.nix#64

Description
This is a test branch for running integration tests with the new Go packages built in https://github.com/informalsystems/cosmos.nix/pull/64.

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

@romac with https://github.com/informalsystems/cosmos.nix/pull/64 merged, we can now enable back Gaia v6 on the CI by pinning directly to v6.0.2 instead of v6.0.3.

repo: informalsystems/ibc-rs


text:
🛑 Aulas virtuales is down

In 8030585, Aulas virtuales (https://aulasvirtuales.unimonserrate.edu.co/) was down:

HTTP code: 503
Response time: 2327 ms

Resolved: Aulas virtuales is back up in bc94750.

repo: infraestructuraidt/status


text:
Quickstart on quicklab was broken

Bug
$ QUICKSTART_CONFIG=configs/quicklab.bash ./deploy/quickstart.sh
[...]
waiting for SAO...
service-telemetry-operator.v0.1.1   Service Telemetry Operator    0.1.1                                      Succeeded
error: error parsing STDIN: error converting YAML to JSON: yaml: mapping values are not allowed in this context

$ source ./deploy/configs/quicklab.bash

$ oc create -f - <<< ${KIND_SERVICEASSURANCE}
error: error parsing STDIN: error converting YAML to JSON: yaml: mapping values are not allowed in this context

Huh.
Fix
$ echo "$KIND_SERVICEASSURANCE" > t.yml

$ oc create -f t.yml
servicetelemetry.infra.watch/stf-default created

$ oc delete servicetelemetry --all
servicetelemetry.infra.watch "stf-default" deleted

$ oc create -f - <<< "${KIND_SERVICEASSURANCE}"
servicetelemetry.infra.watch/stf-default created

Note the quotes.
Testing
This is not covered by CI because the only QUICKSTART_CONFIG override we test with is a blank one.
$ oc delete servicetelemetry --all
servicetelemetry.infra.watch "stf-default" deleted

$ QUICKSTART_CONFIG=configs/quicklab.bash ./deploy/quickstart.sh
[...]
service-telemetry-operator.v0.1.1   Service Telemetry Operator    0.1.1                                 Succeeded
servicetelemetry.infra.watch/stf-default created

@pleimer guess the gist stuff needs to be updated/fixed since it reverted back to pleimer and the link in Details is now invalid.

This link does work however --> https://gist.github.com/infrawatch-bot/07bca9b7a24c727733ab71b2cb3c2d69

This is one I'm going to actually try because I need to get an environment up for Edge DFG anyways.

 Get stftest server setup so that Edge DFG can have an endpoint to point at in downstream CI

Re-fired the CI webhook. My change doesn't even get executed, no good reason for it to fail.

Ah - looks like I didn't relaunch the bot after the organizational change. I will re-fire your changes after I get it set back up

authors: csibbitt leifmadsen pleimer

repo: infrawatch/service-telemetry-operator


text:
not suppport for MacOS

When i use my mac to connect to the network with wifi by DHCP,  i can see the error:
Unknown option 95

I tried Android and Debian, those were OK.

This is the message i got
{
    "op": 1,
    "htype": 1,
    "hlen": 6,
    "hops": 0,
    "xid": 2189072989,
    "secs": 51,
    "flags": 0,
    "ciaddr": "0.0.0.0",
    "yiaddr": "0.0.0.0",
    "siaddr": "0.0.0.0",
    "giaddr": "0.0.0.0",
    "chaddr": "hi-de-th-is-hi-de",
    "sname": "",
    "file": "",
    "magicCookie": 1669485411,
    "options": {
        "12": "wudenggangdeMBP",
        "51": 7776000,
        "53": 1,
        "55": [
            1,
            121,
            3,
            6,
            15,
            119,
            252,
            95,
            44,
            46
        ],
        "57": 1500,
        "61": "\u0001\bi~`w:"
    }
}

And this is my code:
    const server: DhcpServer = dhcp.createServer(options);
    server.on('message', data => {
      logger.info(data);
    });
   server.listen();

According to https://tools.ietf.org/html/rfc3679
it is an unsupported option by Apple. We can add it to dhcp.js though. What I can't figure out is if Apple uses this field as freetext or as a list of IP addresses. The latter would be cleaner. Could you please add the following to the options.js file to test if the format is correct?
  95: {
    name: 'LDAP Servers,
    type: 'IPs',
    config: 'ldapServer'
  },

That works! Thanks toooo much

Okay, that's nice to know. I'll add it to the main branch, but without a release so far. It will be on npm soon.

Okay, is added. Sorry for the error, but I want people to report such things in order to make the library more robust the more people that gets their hands on it.

It's my mistake, I throw the error immediately in the handler for the error event, then the process of distributing the IP is interrupted by that. So my mac can't get the IP. I use
process.on('uncaughtException', () => {})

to prevent the program being crashed.
Now, I just ignore the error (Unknown option 95), and my mac get IP correctly.
Then I add the code provided by you, also works. The only thing i know is that the code won't cause issues.

And what i have to point out is that: it works too , without your added code when I ignore i error instead of throwing it stupidly.

authors: FreePoi infusion

repo: infusion/node-dhcp


text:
Added RQL Library for new endpoints

Now Directory for new endpoints uses RQL notation, also filters can be passed using RQL as object of class Connect\RQL\Query

Codecov Report

Merging #34 into master will increase coverage by 0.07%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #34      +/-   ##
============================================
+ Coverage     98.98%   99.06%   +0.07%
- Complexity      339      372      +33
============================================
  Files            48       49       +1
  Lines           891      963      +72
============================================
+ Hits            882      954      +72
  Misses            9        9

Impacted Files
Coverage Δ
Complexity Δ

src/RQL/Query.php
100% <100%> (ø)
31 <31> (?)

src/Modules/Directory.php
100% <100%> (ø)
13 <4> (+2)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2df1889...132c62f. Read the comment docs.

authors: codecov-io marcserrat

repo: ingrammicro/connect-php-sdk


text:
Clustering Via Multi-aerender setting

Hi Team ,
We are trying to making the multiple instance via multiple AE folder  with reuse  previous AE render instance  like

I have running command like
nexrender-worker --host=http://localhost:4000  --binary="C:\Program Files\Adobe\Adobe After Effects CC 2020\Support Files\aerender.exe" --reuse=ro --workpath="C:\Users\Administrator\Documents\temp\temp1"
and
nexrender-worker --host=http://localhost:4000  --binary="C:\Program Files\Adobe\Adobe After Effects CC 2019_01\Support Files\aerender.exe" --reuse=ro --workpath="C:\Users\Administrator\Documents\temp\temp2"
during running these commands we are getting result from one render but another one always running...
getting error  on after effect 2020:
$ nexrender-worker --host=http://localhost:4000  --binary="C:\Program Files\Adobe\Adobe After Effects CC 2020\Support Files\aerender.exe" --reuse=ro --workpath="C:\Users\Administrator\Documents\temp\temp1" --debug

starting nexrender-worker endpoint http://localhost:4000; using secret: no
using automatically determined directory of After Effects installation:

C:\Program Files\Adobe\Adobe After Effects 2020\Support Files\aerender.exe
adding default render-only-node licenses for After Effects at:
C:\Users\Administrator\Documents\ae_render_only_node.txt
C:\Users\Administrator\Documents\Adobe\ae_render_only_node.txt
checking After Effects command line renderer patch...
command line patch already is in place
[Z1KlA-yNVe84TdgUghwJ3] setting up job...
[Z1KlA-yNVe84TdgUghwJ3] working directory is: C:\Users\Administrator\Documents\temp\temp1\Z1KlA-yNVe84TdgUghwJ3
[Z1KlA-yNVe84TdgUghwJ3] downloading assets...
[Z1KlA-yNVe84TdgUghwJ3] applying prerender actions...
[Z1KlA-yNVe84TdgUghwJ3] running script assemble...
[Z1KlA-yNVe84TdgUghwJ3] rendering job...
[Z1KlA-yNVe84TdgUghwJ3] spawning aerender process: C:\Program Files\Adobe\Adobe After Effects 2020\Support Files\aerender.exe -project C:\Users\Administrator\Documents\temp\temp1\Z1KlA-yNVe84TdgUghwJ3\Project_controller.aepx -comp Render_Youtube 16:9_19201080 -output C:\Users\Administrator\Documents\temp\temp1\Z1KlA-yNVe84TdgUghwJ3\result_[#####].jpg -OMtemplate Image preview -RStemplate Image preview -s 00032 -e 00032 -r C:\Users\Administrator\Documents\temp\temp1\Z1KlA-yNVe84TdgUghwJ3\nexrender-Z1KlA-yNVe84TdgUghwJ3-script.jsx -reuse
[Z1KlA-yNVe84TdgUghwJ3] rendering took ~3.198 sec.
[Z1KlA-yNVe84TdgUghwJ3] writing aerender job log to: C:\Users\Administrator\Documents\temp\temp1\aerender-Z1KlA-yNVe84TdgUghwJ3.log
[Z1KlA-yNVe84TdgUghwJ3] applying postrender actions...
[Z1KlA-yNVe84TdgUghwJ3] error occurred: Error: Error loading postrender module @nexrender/action-copy: Error: ENOENT: no such file or directory, open 'C:\Users\Administrator\Documents\temp\temp1\Z1KlA-yNVe84TdgUghwJ3\result_00000.jpg'
at requireg.catch.err (C:\Users\Administrator\AppData\Roaming\npm\node_modules@nexrender\worker\node_modules@nexrender\core\src\tasks\actions.js:25:35)
[g4kRm7kLa-iGZQVWvI-8z] setting up job...
[g4kRm7kLa-iGZQVWvI-8z] working directory is: C:\Users\Administrator\Documents\temp\temp1\g4kRm7kLa-iGZQVWvI-8z
[g4kRm7kLa-iGZQVWvI-8z] downloading assets...
[g4kRm7kLa-iGZQVWvI-8z] applying prerender actions...
[g4kRm7kLa-iGZQVWvI-8z] running script assemble...
[g4kRm7kLa-iGZQVWvI-8z] rendering job...
[g4kRm7kLa-iGZQVWvI-8z] spawning aerender process: C:\Program Files\Adobe\Adobe After Effects 2020\Support Files\aerender.exe -project C:\Users\Administrator\Documents\temp\temp1\g4kRm7kLa-iGZQVWvI-8z\Project_controller.aepx -comp Render_Youtube 16:9_19201080 -output C:\Users\Administrator\Documents\temp\temp1\g4kRm7kLa-iGZQVWvI-8z\result_[#####].jpg -OMtemplate Image preview -RStemplate Image preview -s 00032 -e 00032 -r C:\Users\Administrator\Documents\temp\temp1\g4kRm7kLa-iGZQVWvI-8z\nexrender-g4kRm7kLa-iGZQVWvI-8z-script.jsx -reuse
[g4kRm7kLa-iGZQVWvI-8z] rendering took ~0.404 sec.
[g4kRm7kLa-iGZQVWvI-8z] writing aerender job log to: C:\Users\Administrator\Documents\temp\temp1\aerender-g4kRm7kLa-iGZQVWvI-8z.log
[g4kRm7kLa-iGZQVWvI-8z] applying postrender actions...
[g4kRm7kLa-iGZQVWvI-8z] error occurred: Error: Error loading postrender module @nexrender/action-copy: Error: ENOENT: no such file or directory, open 'C:\Users\Administrator\Documents\temp\temp1\g4kRm7kLa-iGZQVWvI-8z\result_00000.jpg'
at requireg.catch.err (C:\Users\Administrator\AppData\Roaming\npm\node_modules@nexrender\worker\node_modules@nexrender\core\src\tasks\actions.js:25:35)

Administrator@iZ0xibhyxnnr2mZ MINGW64 ~/Desktop
============================================
Please help me out for solve these issues related to the Multiple render with  multi-aerender.exe file with reuse them

So, in theory you don't have to use multiple temp folders and create multiple copies of the process to render many videos at the same time.
Reuse, however, is a very specific thing, and it works on the after effects level. I would even say it is quite dangerous. I don't think you can run 2 instances of after effects GUI app, and expect that 2 spawned aerender instances will definitely reuse 2 existing processes. I feel it is as likely as both will attempt to use a first running process, and one of them will immediately fail.
What I would recommend is either:
Using reuse flag and doing that on "microscopic level": small virtual environments with a controlled amount of memory and CPU cores, running a SINGLE copy of after effects, and doing a single render at a time using reuse flag.
OR
Changing the settings within aerender to influence the number of cores/memory used, and running multiple aerender jobs right on the host machine, without reuse flag.
In all other cases, it seems to me that combining reuse and multiple instances on a single machine is a very bad idea.

@inlife Thank you!

authors: inlife pixelfactorydevelopmentteam

repo: inlife/nexrender


text:
Manipulating Javascript attributes

Added new wrap data variant for attributes

strategy is "freely mix attributes and properties"

using eval for expressions

Looks good. Also, I like that fact that so little changes required for adding quite a lot of possibilities.

authors: brassel inlife


text:
Fix doller sign escaping issue

Description
Fix doller sign escaping issue in installation documentation.
Self Check:

[ ] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master in a74dcc42952e4bb5e0c6d376da27c1d6b08940c0

authors: arnaudsjs inmantaci

repo: inmanta/inmanta-core


text:
Move DB-related functions and classes to inmanta.db.util module

Description
Moved the do_clean_hard and postgres_get_custom_types functions and the PGRestore and the AsyncSingleton classes to the inmanta.db.util module. This way it can be used from other Inmanta extensions.
closes #5383
Self Check:

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation

I didn't check the implementation in inmanta.db.util under the assumption that it remained unchanged. Let me know if that is not the case.

I added some code to fix the typing issues. But the logic should remain the name.

Processing this pull request


text:
[FE] 우측 구역(사물함 상세정보) 배치 및 css 조정

작업 설명
작업한 컴포넌트들을 합치면서 누락된 부분을 main 페이지에 합치고 css 조정하겠습니다.
접근 방법
MainPage에 CabinetInfoArea를 배치하고 css 조정
대체 방안 (선택 사항)
No response

Closed by PR

PR #646


text:
Add scrollRef prop to Vue Virtualizer

It's necessary for complex markup.
Just port React implementation.

is scrollRef working on react ? did not found the implementation and was not being able to make it work with a list that has header before the actual list and scroll is done by some parent view

@billouboq
React's implementation is here.
https://github.com/inokawa/virtua/blob/d6faef0012e5089e896a9a7a680d99874b8a60a6/src/react/Virtualizer.tsx#L262-L267
I just tried to implement it for Vue in https://github.com/inokawa/virtua/pull/393. However, it is not working correctly at the moment. I'm not an expert of Vue so maybe something is wrong.

authors: billouboq inokawa

repo: inokawa/virtua


text:
npm

Hi, could you consider putting this library on npm?

Done: https://www.npmjs.com/package/digest-auth-request

That was quick, thanks!
On Fri, Jan 8, 2016, 22:50 Jamie Perkins notifications@github.com wrote:

Done: https://www.npmjs.com/package/digest-auth-request
—
Reply to this email directly or view it on GitHub
https://github.com/inorganik/digest-auth-request/issues/17#issuecomment-170137869
.

authors: inorganik oskbor

repo: inorganik/digest-auth-request


text:
rewards table should track rewards received from treasury/reserves by MIR process

There isn't a good authoritative source for this using just db-sync. I suggest rewards table should have a reward_type as an enum POOL|TREASURY|RESERVE and any rewards paid out from treasury/reserve at epoch boundary should be logged in this table.

This would need to be implemented in ledger-specs first.

What do you think needs to be implemented in ledger-specs? Rewards from pools come via the reward updates, the other rewards come via the MIR certs, marked as either Treasury or Reserves.

As far as db-sync and the actual accounting is concerned, there is no real difference whether rewards come from owning/delegating to a pool or from reserves/treasury.
Secondly pulling treasury and reserve rewards out of the transactions (where the MIR certs are) is way more complicated than pulling them out of the ledger state.
In my ideal API, staking rewards and reserves/treasury rewards would all be lumped together in one big map, with each reward being tagged with where it came from (eg LeaderReward , MemberReward , TreasuryPayment or ReservesPayment).

In my ideal API, staking rewards and reserves/treasury rewards would all be lumped together in one big map, with each reward being tagged with where it came from (eg LeaderReward , MemberReward , TreasuryPayment or ReservesPayment).

As I understand different kinds of rewards might have different "enabling" formula as a function of their "epoch" parameter. E.g. delegation rewards inserted during epoch N would have "epoch" value equal to N-1 but would only be spendable starting with N+1. Meanwhile any MIR inserted durin epoch N would have "epoch" value equal to N but would be spendable also from N+1, is that correct?
@erikd, just confirming, do you plan to add the spendable_epoch column (as discussed here: https://github.com/input-output-hk/cardano-db-sync/pull/704#issuecomment-885326111) to encapsulate all this difference?

Yes, there will be two columns, earned_epoch and spendable_epoch .

authors: JaredCorduan disassembler erikd vsubhuman

repo: input-output-hk/cardano-db-sync


text:
Add instructions to README on how to run node with testnet and mainnet

As was fairly pointed out on Reddit: there no instructions on

... how to connect the current code-base to either Byron mainnet or testnet, do you have some docs on that or is it going to be more of a trial and error type of thing?

Would you prefer it as part of README.md or a separate document? Connecting my Docker images do the testnet and mainnet is my next step, so I'll be reverse-engineering the process from the mainnet.sh script and documenting it for myself anyway, so it's not much additional effort to make it fit for the upstream repo...

authors: mark-stopka tatyanavych

repo: input-output-hk/cardano-node


text:
Fix for: metric tracing crashes node #4076

Use an MVAR instaed of an IOVar for metrics

bors r+

authors: deepfire jutaro


text:
[CSL-298] Modify SscReq to take multiple addresses

@gromak

@gromak
Did we decide not to do it? Why?

@gromak
Ok, it's 351.

repo: input-output-hk/cardano-sl


text:
Update text rendering of dependency graph

This is the current dependency graph. It is an ASCII rendering of
the PNG output from stack dot | ... | dot. -test and -bench
packages are omitted.
This graph was run through tred which eliminates redundant deps
(those which are implied by transitivity).

That sounds reasonable. It would be a pain to keep that thing up-to-date... And since everyone has stack dot accessible, it's just a matter of having graphviz, which is no biggie.


text:
Perform rollback in wallet restoreStep restoration loop

Context
Glue the bits together to finish the rollback feature.
Decision

Adjust restoreBlocks so that it adds a checkpoint for every Wallet returned by applyBlocks.
Change restoreStep so that it handles RollBackward by rolling back the database to the given slot.

Acceptance Criteria

Wallet must roll back the database when nextBlocks returns RollBackward.
Restoration should begin immediately after rollback.
There must be adequate logging to inform the user of this situation.
The impact on restore time of maintaining rollback information should be examined.

Development Plan

[x] I have added an extra callback to the restoration worker to rollback on ... rollbacks.
[x] Made sure we don't purge the very first checkpoint we create in the wallet. We might roll back up to the genesis block, so this checkpoint is needed (and currently discarded after k blocks)
[x] Added a listCheckpoints function to the database layer to return a full list of block headers to use to find an initial intersection. The greatestCommonBlockHeader now works fine with sparse lists so no work to do in this area :tada:
[x] Extended the state-machine to also yield listCheckpoints calls

PR

Number
Base

#812
master

QA

Added a read-only function listCheckpoints to the database layer, and to the state-machine. So, now tested in all sort of interleaving with other calls.

Rolling back in the wallet layer is the direct composition (see here and here) of:

Detecting chain switches at the network-level (fully tested as part of #648)
Rolling back the database (fully tested as part of #645)

So, under the assumption that the network-level can correctly yield a "RollBackward" when needed, and that the call rollbackTo to the database works as we expect, the wallet should have no problem rolling back during the restoration loop.

The chain follower will log a line at the INFO level in the event of rollback, so this could be controlled during some smoke tests:

            logInfo tr $ "Rolling back to " <> pretty point

lgtm :+1:

authors: piotr-iohk rvl

repo: input-output-hk/cardano-wallet


text:
Bump version from 2021.8.27 to 2021.9.9

299f381fdde16ba69df9e69137a859721ea41a1c
Bump version from 2021.8.27 to 2021.9.9

Comments
Had this issue with make_release.sh script:
Generating unresolved issues list into GENERATED_KNOWN_ISSUES.md...
ERROR Invalid Usage: JSON Parse Error: invalid character 'B' looking for beginning of value from "Basic authentication with passwords is deprecated.  For more information, see: https://confluence.atlassian.com/cloud/deprecation-of-basic-authentication-with-passwords-for-jira-and-confluence-apis-972355348.html\n"
The "jira release-notes-bugs" command didn't work.

But as far as version bump seems to be ok I think.
Issue Number

bors r+

bors r+

bors r+

bors r+


text:
Block fetch logic

Work in progress for the block fetching logic, part of #66.
Main achievements so far is a plausible design. We have the outline of the state management with STM, and the pure decision logic. Working code so far includes making a decision to fetch a chain suffix, subject to concurrency limits.
Yet TODO:

[ ] mock block fetch client and server
[ ] fetched block set
[ ] tests demonstrating full download iterations

Now open as #407 and #408.

repo: input-output-hk/ouroboros-network


text:
Update Haskell.nix for updating HLS to latest version

This pulls in HLS-1.2.0 and updates haskell.nix and index-state to recent versions.

Superseded by #3272


text:
Consider removing the bare Database.items API

With the introduction of a richer descriptor for item/bookmark queries, it might make sense to remove the legacy API which accepts both search strings and tags.

This should be implemented as part of #166.

repo: inseven/bookmarks


text:
Exit cleanly if a configuration file cannot be found

It's important to show a helpful error if no configuration file is present and explain how users can run InContext.

I've been thinking the most elegant way to do this might be to have special exception that can be thrown which is caught at the top-level and converted into an error log event and an exit(1). That way these kinds of exists can be made clean, but also made available to top-level integration testing.

repo: inseven/incontext


text:
How to make time row always visible?

How to make the time row always visible when scrolling, just like the channel column? Thanks!

How to achieve this one? I want time visible always. if we scroll the collectionView it is disappear.

@hansolowireless @m1entus
Is it possible? Thanks

Everything is possible, you should easly implement it, you have already big bunch of code which you should be grateful.

@m1entus
I'm very thankful for what you have done already it's really great. Actually i don't have too much experience in objective c so it will be very helpful for me if you guide me or provide some demo code.
Thanks.

authors: AdnanAliShabir hansolowireless m1entus


text:
Strongify weakSelf in blocks where it expects self to be nonnull

I haven't looked into other spots where this is happening but wanted to get your thoughts on this. Thanks!

This doeasn't make any sense in this case, strongSelf should be used in different situations. In this case there is no effect

Got it, I ran into a "object deallocated while in use" crash report in the field with INSReachabilityCondition but it seems to be unrelated to this. I'll close it out.

repo: inspace-io/INSOperationsKit


text:
Cleanup custom-columns CLI flag

Current situation
We used to have a CLI flag custom-columns but it does not exist anymore: it was renamed to columns. However, git grep custom-columns shows left overs in comments, documentation, tools and code.
custom-columns was renamed to columns by #1281.
Impact
Suggested commands from the code base actually don't work anymore:
$ ./kubectl-gadget trace dns -n demo --timeout 3 -o custom-columns=pod,comm,qr,qtype,name
Error: invalid output mode "custom-columns"

Ideal future situation
git grep custom-columns does not give any results.
Implementation options
Remove custom-columns or rename as appropriate.
Additional information
$ git grep custom-columns
cmd/common/utils/flags.go:30:   OutputModeCustomColumns = "custom-columns"
docs/gadgets/audit/seccomp.md:65:$ kubectl gadget audit seccomp -o custom-columns=namespace,pod,syscall,code
docs/gadgets/common-features.md:50:This can be overridden with either `json` or `custom-columns`.
docs/gadgets/common-features.md:78:Using `-o custom-columns=column1,column2` we can choose which columns to
docs/gadgets/common-features.md:87:$ kubectl gadget trace oomkill -A -o custom-columns=kpid,kcomm
docs/gadgets/profile/cpu.md:89:$ kubectl gadget profile cpu --timeout 1 --podname random -o custom-columns=node,pod
docs/gadgets/profile/cpu.md:100:$ kubectl gadget profile cpu --timeout 1 --podname random -o custom-columns=node,namespace,pod,container,pid,comm,count,stack
docs/gadgets/top/ebpf.md:59:you can call the gadget with the custom-columns option and specify the cumulruntime and cumulruncount columns.
docs/gadgets/top/ebpf.md:64:$ kubectl-gadget top ebpf -o custom-columns=node,progid,type,name,pid,comm,cumulruntime,cumulruncount --sort cumulruntime --timeout 60
docs/gadgets/trace/capabilities.md:165:    -o custom-columns=comm,syscall,capName,verdict,targetuserns,currentuserns,caps,capsnames
docs/ig.md:113:- JSON format and `custom-columns` output mode are supported through the
integration/command.go:209:               NAMESPACES=$(kubectl get seccompprofile --all-namespaces --no-headers --ignore-not-found -o custom-columns=":metadata.namespace" | uniq)
pkg/gadgets/traceloop/types/types.go:79:        // -o custom-columns.
tools/demos/trace-dns/demo.sh:24:run "kubectl gadget trace dns -n demo --timeout 3 -o custom-columns=pod,comm,qr,qtype,name"
tools/demos/trace-exec/demo.sh:21:run "kubectl gadget trace exec -n demo --timeout 4 -o custom-columns=pod,pid,comm,args"

#1326 will fix a part of this.

repo: inspektor-gadget/inspektor-gadget


text:
ui: display imprints from books

#2171

I believe the date should be formatted in the same way as the date at the top (see screenshot). @StellaCh ?

yes, consistency is key. It should be displayed as the example I have in the first comment of the issue: https://github.com/inspirehep/inspirehep/issues/2171 , similar to the other date

updated date format

authors: StellaCh hanadikaleel michamos

repo: inspirehep/inspirehep


text:
To optimize the Board Service

In GitLab by @cuiaq123 on Jul 26, 2018, 10:47
Optimize the Board Service to stronger,to fix some problems
1,The ApiService is invalid when the collector not in working;
2,The ApiService can't normal work when the db container not ready;

In GitLab by @sokril on Nov 8, 2019, 08:26
assigned to @liyanq528

In GitLab by @sokril on Dec 26, 2019, 02:57
changed the description

repo: inspursoft/board


text:
Dashboard more details:cluster pod capacity and CPU capacity have no unit

In GitLab by @sokril on Mar 21, 2018, 15:25

In GitLab by @tmon546596046 on Nov 8, 2019, 07:48
this is grafana ui component, we can't change it.

In GitLab by @tmon546596046 on Nov 8, 2019, 07:48
this is grafana design, we can't modify it. so i will close it.

In GitLab by @sokril on Nov 8, 2019, 08:19
closed

In GitLab by @sokril on Nov 8, 2019, 08:19
assigned to @tmon546596046


text:
[Issue] Query Button Width than Screen

In GitLab by @cuiaq123 on Jul 6, 2018, 16:59
If you are reporting a problem, please make sure the following information are provided:

Version of board (last git commit number) , docker engine and docker-compose.
Config files of board, you can get them by packaging "board.cfg" and files in the same directory, including subdirectory.
Log files, you can get them by package the /var/log/board/.
Other necessery information.

In GitLab by @liyanq528 on Nov 8, 2019, 07:54
fixed by pull request #1059

In GitLab by @yhua123 on Nov 8, 2019, 07:54
wrong PR number

In GitLab by @liyanq528 on Nov 8, 2019, 07:54
fixed by pull request #1537

In GitLab by @yhua123 on Nov 8, 2019, 07:54
LGTM

In GitLab by @sokril on Nov 8, 2019, 08:24
closed

In GitLab by @sokril on Nov 8, 2019, 08:24
assigned to @yhua123


text:
A question about qmix_cql

Why   all_mixed_ood_qs.append(chosen_action_qs) # [B, T, Ra + 1] in og_marl/tf2/systems/qmix_cql.py line 170.
I am a little confused about this, since "chosen_action_qs" is not a "ood_action", but an  "action" in buffer.

Hi @zyh1999, thank you for posting a question. You are certainly correct that chosen_action_q is not an OOD action. Its been a while since I did the implementation but I believe it was done this way because we found (empirically) that the CQL loss diverged when I omitted the chosen actions Q-value from the log_sum_exp term. And I was inspired to add it to the log_sum_exp term since in the single agent DQN-CQL implementation (see here ) the log_sum_exp calculation is done across all Q-values (which includes the chosen action Q-value). Having said that, I do not have a good theoretical justification for doing it this way. So if you find a better way of doing it, or that performance is better when omitting it, then please do let us know.

Well, I know the reason.  Yesterday, I conducted an experiment and found that removing the CQL loss led to divergence. Thank you very much for your prompt response!

Its my pleasure. Please let me know if you have any further questions or you have any trouble getting the code to run on some configuration.

repo: instadeepai/og-marl


text:
App is getting crashed if I use this Repo

App crashed with the following fatal error as soon as it starts
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0xc1e4e8d4 in tid 9035
Please let me know the reason.
Here is the gradle config I am using
apply plugin: 'com.android.application'
android {
    compileSdkVersion 28
    buildToolsVersion "28.0.3"
    defaultConfig {
        applicationId "<package-name>"
        minSdkVersion 26
        targetSdkVersion 28
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
    packagingOptions {
        exclude 'META-INF/DEPENDENCIES'
        exclude 'log4j.properties'
        exclude 'org/bytedeco/javacpp/macosx-x86_64/libusb-1.0.dylib'
    }
}
dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation 'com.android.support:appcompat-v7:28.0.0'
    implementation 'com.android.support.constraint:constraint-layout:1.1.3'
    implementation 'org.brunocvcunha.instagram4j:instagram4j:1.8'
    testImplementation 'junit:junit:4.12'
    implementation 'commons-codec:commons-codec:1.10'
    compileOnly 'org.projectlombok:lombok:1.16.16'
    annotationProcessor "org.projectlombok:lombok:1.16.16"
    compileOnly 'org.glassfish:javax.annotation:10.0-b28'
    implementation(
            [group: 'com.fasterxml.jackson.core', name: 'jackson-core', version: '2.8.6'],
            [group: 'com.fasterxml.jackson.core', name: 'jackson-annotations', version: '2.8.6'],
            [group: 'com.fasterxml.jackson.core', name: 'jackson-databind', version: '2.8.6']
    )
    implementation 'com.squareup.okhttp3:okhttp:3.9.0'
    implementation 'com.writingminds:FFmpegAndroid:0.3.2'
    androidTestImplementation 'com.android.support.test:runner:1.0.2'
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
}

Can you provide a more complete log? Also, using debug tools, can you track down the statement or function causing the crash and post it here?

Thanks for your reply @jemand771 basically this happening only when I call the login method, upto setup it's fine. I also tried with android:hardwareAccelerated="false" but not fixed.

Hi @rajenpal033 , do you have found a solution?

Maybe this library is not compatible with android. I don't really know though.
#303 suggets to use https://github.com/charlieAndroidDev/Instagram4Android instead

@jemand771 the problem of Instragram4Android is that this library has not been updated for a long time

Addressed in rewrite or no longer relevant.


text:
No module named requests - infinity feedlike

when I try to run "infinity_feedlike" this error happens
Last login: Sun Oct 22 20:28:10 on ttys001
MBP-de-iran:~ iran$ cd '/Users/iran/Desktop/instabot-master/examples/' && '/usr/bin/pythonw' -S  '/Users/iran/Desktop/instabot-master/examples/infinity_feedlike.py'  && echo Exit status: $? && exit 1
Traceback (most recent call last):
File "/Users/iran/Desktop/instabot-master/examples/infinity_feedlike.py", line 14, in
from instabot import Bot
File "/Users/iran/Desktop/instabot-master/examples/../instabot/init.py", line 1, in
from .api import API
File "/Users/iran/Desktop/instabot-master/examples/../instabot/api/init.py", line 1, in
from .api import API
File "/Users/iran/Desktop/instabot-master/examples/../instabot/api/api.py", line 1, in
import requests
ImportError: No module named requests
MBP-de-iran:examples iran$

have you tried pip install -U instabot or sudo pip install -U instabot?

Yes! I was already running, but when the macbook unloaded, and I tried to run again, gave this error

Can someone help me? PLEASE

All questions can be asked in Google.
Just read the error that terminal gives you. It said:

ImportError: No module named requests

That means that you should install requests module.
So you should google:
how to install python module

or
python install requests module

It will answers you to type in terminal:
pip install requests

authors: iransales ohld

repo: instagrambot/instabot


text:
Mention.py

mention users followers in comment section of latest media

Codecov Report

Merging #862 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #862   +/-   ##
=======================================
  Coverage   49.15%   49.15%
=======================================
  Files          26       26
  Lines        2616     2616
=======================================
  Hits         1286     1286
  Misses       1330     1330

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ca6d115...76bac1c. Read the comment docs.

all example should be in example folder

I'll close this PR since no changes were provided.

authors: codecov-io ohld virginsince1997


text:
How to use

Im pretty much trying to use the module to do a bunch of stuff that the module provides us. The documentation confuses me and i cant seem to make it work.
I can use the download post even tho i got some trouble making it use the path i want to be saved + fast update not working
after loading an account i managed to use download saved posts + feed posts
but cant download specific profile of my choice (stories/highlights/reels) nor hashtag posts the same way i use the download_posts
HTTP redirect from https://www.instagram.com/graphql/query to https://www.instagram.com/accounts/login/
this also shows up and i cant bypass it
so a youtube guide with examples of the docs would be pretty much appreciated

You won't have more luck if you open another issue. You didn't describe in detail in #1327. You didn't add much more details here.
The redirect to login wants you to login with a valid account to continue.

You won't have more luck if you open another issue. You didn't describe in detail in #1327. You didn't add much more details here. The redirect to login wants you to login with a valid account to continue.

its not about luck. Its about getting help
im literally describing what i wanna do and i cant do it
the account is valid the thing gets stack and i cant do anything at all

repo: instaloader/instaloader


text:
feat: self-disable if detected Node.js runtime version is too old

This change prevents @instana packages from loading in (and thereby crashing)
Node.js processes that run on an unsupported, outdated Node.js version.
refs 80206

Super sweet!

repo: instana/nodejs


text:
LENIENT Strictness should ignore unconsumed .emit().items()

Feature description
Suppose you have a model
Model validModel;
void setup() {
  validModel = Instancio.of(Type.class)
  .generate(field(a), gen -> gen.collection().size(2))
  .generate(field(a), gen -> gen.emit().items(true, false))
  .set(all(field(b), false))
  .toModel();
}

@Test
void myTest() {
 Instancio.of(validModel).
.lenient() //for overriding the set
.set(all(field(b), true))
.generate(field(a), gen -> gen.collection().size(0))
.create(); // will fail cause emit values were not consumed
}

I have to change the model by adding gen.emit().items(true, false).ignoreUnused()
This would allow me to use the One Bad Attribute pattern and not forgetting the ignoreUnused

I think this change will violate separation of concerns. The lenient() method is used to ignore unused selectors. It's not related to generators. Any reason why you can't add ignoreUnused() to the model?

authors: armandino dcebotarenco

repo: instancio/instancio


text:
Updated for Swift 3?

I'm interested in using this but it doesn't seem to be compatible for Swift 3 at the moment, will it be updated?

Hi!
Yep, i'll update the view!
I've added it to my TODO list 👍

Great! I'm glad this project is active 👍 😄

hope project support swift3

@holzleitner @lou-lan  @flamingfusion
I have updated the framework to Swift 3. See #request for more.

how can i update to swift 3

You can use my fork, which is compatible with Swift 3.
https://github.com/sanjeetsuhag/ISTimeline

Have a look at the release ISTimeline v0.0.4 🤙

authors: O16MuhammadAhmedBaig flamingfusion holzleitner lou-lan sanjeetsuhag

repo: instant-solutions/ISTimeline


text:
Change image perspective

I am trying to get an image from the same person (image_1) but from a camera position that I am inferring from a face of other image (image_2).
"face_image" and "face_emb" are from image_1 and "face_kps" are from image_2.
Also, my prompt and negative prompt are empty.
Is there anything else I should modify or correct?

You'r correct.

authors: alvarofdzg haofanwang

repo: instantX-research/InstantID


text:
Added docs badge to README

Docs are live at https://intake.github.io/fsspec-reference-maker

I should write some docstrings...
Also, the GRIB and TIFFfile should be included (the latter is not in this repo)

authors: lsterzinger martindurant

repo: intake/fsspec-reference-maker


text:
Intake Take2 is about to release

Please consider pinning intake<2 to keep this package working, if it breaks with the new code.

It should be possible to port existing users to intake.readers.catalogs.THREDDSCatalogReader

Any plan to make this intake-thredds compatible with the newer intake 2?
If we want intake-xarray 2, we need intake 2, but then this intake-thredds is not compatible with intake 2.

Good point - I'll look into it. Intake 2 does have a THREDDSCatalogReader internally, so it should not be much work (hopes).

authors: martindurant tlvu

repo: intake/intake-thredds


text:
🛑 Shopintake is down

In 921ae6a, Shopintake (https://www.shopintake.com) was down:

HTTP code: 403
Response time: 228 ms

Resolved: Shopintake is back up in 00b7586 after 7 minutes.


text:
🛑 FoodB2B is down

In 938923b, FoodB2B (https://www.foodb2b.kr) was down:

HTTP code: 503
Response time: 1162 ms

Resolved: FoodB2B is back up in 328d74b.


text:
🛑 Shopintake is down

In 0bec1dc, Shopintake (https://www.shopintake.com) was down:

HTTP code: 403
Response time: 358 ms

Resolved: Shopintake is back up in 497cd63 after 20 minutes.


text:
Delete old queues

The jobs in these queues were migrated and processed in the installation queue and no new jobs are stored in there. So we don't need to keep them in the code.

@tcbyrd Cool. Thanks for checking that!

repo: integrations/jira


text:
remove aura dev setting allow_delayed_proposal

closes #994

Can you add labels? ❤

authors: gaudenzkessler haerdib

repo: integritee-network/worker


text:
issue-81: is readFully necessary for Input interface

The pull request for https://github.com/intel-hadoop/chimera/issues/81

LGTM. I noticed that you use the same commit message for all the commits in the pull request. Which will leads multiple commits in the master with the same messages which is not the right way.  Please take this note for consideration in your future commits.

authors: colinmjj jerrychenhf

repo: intel-hadoop/chimera


text:
Other Hardware

Hello
We use a different board with an NXP iMX6. Without having a supported plattform, I am currently excluded from using Mraa properly. What is the standing on this? Can I add a generic Platform definition or make the driver code not crash if "platform" is NULL?
Thanks

You can indeed make a generic platform, there's no reason not too, generally people like to add their board in though. I'm happy to take a 'generic' platform that will just call the _raw functions in passthrough.

authors: arfoll smuellener

repo: intel-iot-devkit/mraa


text:
Query: What is the rate at which AIO read and GPIO write can be called

i am using mraa on Raspberry PI with Grove Kit.
I see occasional failures when I use mraa_aio_read (read_status = -1) and mraa_gpio_write (status = MRAA_ERROR_UNSPECIFIED).  I have several writes to GPIO and reads from AIO (various pins). All the calls are serialized and I invoke these apis continuously. I would like to know if there is any limitation w.r.t successive reads/writes using mraa.
Can retry mechanism in these cases help or should i try writing to/reading from after a delay?

Hi @BinduRao2018,
IMO this behavior is the limitation of SYSFS interface for both GPIO and AIO. You can test this by writing a simple shell script which just reads from AIO (/sys/bus/iio/devices/iio:device0/in_voltage0_raw) and writes to GPIO through SYSFS. I would suggest you to provide a delay after each read/write.

Thanks for the info @Mani-Sadhasivam. I will look into this.


text:
Pull wt5001 use mraa_uart_get_dev_path

The request updates the driver to use mraa_uart_get_dev_path().
It also renames the JS example from w5001 -> wt5001, like the C++ example.
Then the JS example is fixed to support the new driver interface.

https://github.com/intel-iot-devkit/upm/commit/06b48d8e0783faa7a5a516d192f6323234d9fc56

authors: Jon-ICS Propanu

repo: intel-iot-devkit/upm


text:
openssl-qat-engine: update component versions

Signed-off-by: Mikko Ylinen mikko.ylinen@intel.com

Codecov Report

Merging #1120 (a3f30d8) into main (d826548) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head a3f30d8 differs from pull request most recent head 326f102. Consider uploading reports for the commit 326f102 to get more accurate results

@@           Coverage Diff           @@
##             main    #1120   +/-   ##
=======================================
  Coverage   52.99%   52.99%
=======================================
  Files          40       40
  Lines        4357     4357
=======================================
  Hits         2309     2309
  Misses       1921     1921
  Partials      127      127

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter mythi


text:
Error log for network-attachment-definition

Corrected the error for missing network-attachment-definition

This is awesome! Thanks for the detailed eye on these PRs, we appreciate them a lot!

@dougbtv thanks for quick review!

authors: ashish-billore dougbtv

repo: intel/multus-cni


text:
docker/build.sh fails if UID is not 1000

On a system when UID is not 1000 (i.e. a second user was created and that account was used to run build), the build will fail.
Run docker/build.sh and you will get the following error
ERROR: Could not install packages due to an EnvironmentError: [Errno 13] Permission denied: '/.local'
Check the permissions.

To workaround the problem, modify tools/model_downloader/model_downloader.sh so that user is root
$SOURCE_DIR/docker/run.sh --user root ...

Fixed in v0.6.0-beta

repo: intel/video-analytics-serving