text:
Release 0.4.0

New release so we can update the test kits to use ruby 3.

Codecov Report
Base: 73.59% // Head: 95.38% // Increases project coverage by +21.79% :tada:

Coverage data is based on head (7f1f5b9) compared to base (d5619cf).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #273       +/-   ##
===========================================
+ Coverage   73.59%   95.38%   +21.79%
===========================================
  Files         184      113       -71
  Lines        8859     2992     -5867
  Branches      328        0      -328
===========================================
- Hits         6520     2854     -3666
+ Misses       2014      138     -1876
+ Partials      325        0      -325

Impacted Files
Coverage Δ

...c/components/InputsModal/InputOAuthCredentials.tsx

...mponents/TestSuite/TestSuiteDetails/ResultIcon.tsx

client/src/components/Header/Header.tsx

...TestSuite/TestSuiteDetails/TestListItem/styles.tsx

client/src/components/ThemeProvider.tsx

...stSuite/TestSuiteDetails/TestListItem/TabPanel.tsx

...s/TestSuite/TestSuiteDetails/TestSuiteMessages.tsx

client/src/components/LandingPage/styles.tsx

...ents/TestSuite/TestSuiteTree/TestGroupTreeItem.tsx

...nts/RequestDetailModal/__mocked_data__/mockData.ts

... and 61 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: Jammjammjamm codecov-commenter

repo: inferno-framework/inferno-core


text:
[Bug]: Flask Version Conflict with Flask_script

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
infiniflow/ragflow
Commit ID
#flaskwrongrag0001
Other environment information
OS Type:CentOs stream 9

Actual behavior
at first ,when i ran the ./entrypoint.sh with bash , it came out error with the manager which is not defined ,then i imported flask_script and defined manager but it appear the error with conflict between flask and flask_script:ImportError: cannot import name ‘_request_ctx_stack’ from 'flask'.after that i changed the commands.py file of flask_script:
from flask import _request_ctx_stack

changed to:
from flask import request_ctx
but it did not success :
ImportError: cannot import name 'request_ctx' from 'flask' (/root/.conda/envs/ragflow/lib/python3.11/site-packages/flask/__init__.py)
Expected behavior
No response
Steps to reproduce
1,bash run the entrypoint.sh
2,define manager
3,flask version conflict with flask_script

Additional information
No response

Install the requirements. And run python scripts as the entrypoint.sh tends to do.

Install the requirements. And run python scripts as the entrypoint.sh tends to do.

I did it,but it didn't work!But i fixed it by installing this project again in other folder!it's a strange project! 😄

source: gharchive/issue

repo: infiniflow/ragflow

license_type: permissive

license_source: github-api


text:
ISPN-5729 Remote query - org/apache/lucene/uninverting/UninvertingRea…

…der missing on "order by" query
https://issues.jboss.org/browse/ISPN-5729

@anistor What's left here?

Updated. Waiting for CI.

source: gharchive/pull-request

authors: anistor galderz

repo: infinispan/infinispan


text:
ISPN-10435 Support for serving static content

https://issues.jboss.org/browse/ISPN-10435
Static content from the server's static/ folder will be served under e.g. http://locahost:11222/rest/static, allowing console and/or docs to be hosted there.

Conflicts !

authors: gustavonalle tristantarrant


text:
🛑 Client Portal is down

In 25e3ee2, Client Portal (https://accounts.infinite8.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Client Portal is back up in b98cbec.

license: MIT


text:
v9 (yarn): unable to run yarn android on windows

Describe the bug
PS E:\react-native> npx ignite-cli@latest new FlixPulse
Need to install the following packages:
ignite-cli@9.0.0
Ok to proceed? (y)

✅ What bundle identifier? · app.flixpulse
✅ Where do you want to start your project? · E:\react-native\FlixPulse
✅ Choose a workflow: · Expo Prebuild
✅ Do you want to initialize a git repository? (Y/n) · Yes
✅ Remove demo code? We recommend leaving it in if it's your first time using Ignite (y/N) · No
✅ Which package manager do you want to use? · yarn
✅ Do you want to install dependencies? (Y/n) · Yes
✅ ❗EXPERIMENTAL❗Would you like to enable the New Architecture? (y/N) · No

                                               .;;,.    .clll.
                                              .clll,    ,llll.           ...
                                               .,;,.    ;lllc'.,.   .';cllllc,
     .',,.                           ...      .'',,. .:lllllllll. .;lllc:;clll,
    .llll,                    .,...;cllll:.   ,llll, .llllllc,,'  clll:'.,cllc.
    ,llll'       ......;::.  'llcclllllllll'  ,llll,   .llll.    ,lllllllll:'
    ,llll.    .;clllllclll.  'llllc,..,llll,  :llll.   'llll.    ,lllc,''..
    ;llll.   :llllc:cllllc.  ,llll.   .llll, .lllll.   ,lllc...  ,lll:...';:.
   .llllc.  ;lll;.   :lll,   ;lll;    'llll, .llllc.   ,llllcll' .:lllllllll,
   .llll,  'lll:    .clll,   :lll,    ,llll. 'llll,    'lllllcc'   ';::::;'.
   .llll,  ,lll:    .llll'  .llll,    ;llll. ,llll,     .....             .',..
   ,llll.  'llll:,,:cllll.  .lllc.    .''..  ... ....',;         ..',,:::;'..
   ,llll.   'clllllllllll.     .....        ..,::cllllc.   .',:clllc;,'.
   :llll.     ',;,'.;lllc...,;:clll;  ..',:cllllllllll:,;clllllc;,'.
   llll:        ...'cllllllllllllll::cllllllc;,',cllllllllc;'..
   llll,   ..,clllllllll::,,.,lllllllc:,'...    :lllllc,..
   c:;,.  .cllllc:;:llll.    ,ll:;,..          ;ll:,..
          :lll,.  .clll,     ..               .,..
          :lll:,,cllll,
          .cllllllllc'
           .'cllll:.

    █ Creating FlixPulse using Ignite 9.0.0
    █ Powered by  ∞ Infinite Red  (https://infinite.red)
    █ Package Manager: yarn
    █ Bundle identifier: app.flixpulse
    █ Path: E:\react-native\FlixPulse
    ────────────────────────────────────────────────────

    🖨  3D-printing a new React Native app
    🎨 Getting those last few details perfect
    🧶 Installing yarn dependencies (wow these are heavy)
       Configuring app.json
    🛠  Generating native template via Expo Prebuild
    🛠  Removing fancy demo markup
    🗄  Backing everything up in source control
    For next time: here are the Ignite options you picked!
      npx ignite-cli new FlixPulse \
        --bundle=app.flixpulse \
        --git \
        --install-deps \
        --packager=yarn \
        --target-path=E:\react-native\FlixPulse \
        --remove-demo=false \
        --workflow=prebuild \
        --no-timeout=false

    ────────────────────────────────────────────────────

    Need additional help?

    Join our Slack community at http://community.infinite.red.

    ────────────────────────────────────────────────────

    Now get cooking! 🍽
      cd E:\react-native\FlixPulse
      yarn android

PS E:\react-native>
PS E:\react-native>
PS E:\react-native>
PS E:\react-native> cd .\FlixPulse\
PS E:\react-native\FlixPulse> yarn android
yarn run v1.22.21
$ npx expo run:android
› Building app...
Configuration on demand is an incubating feature.

> Configure project :expo

Using expo modules
  - expo-application (5.4.0)
  - expo-constants (14.4.2)
  - expo-file-system (15.4.4)
  - expo-font (11.6.0)
  - expo-keep-awake (12.3.0)
  - expo-localization (14.5.0)
  - expo-modules-core (1.5.11)
  - expo-modules-core$android-annotation (1.5.11)
  - expo-modules-core$android-annotation-processor (1.5.11)
  - expo-splash-screen (0.20.5)

> Configure project :react-native-reanimated
No AAR for react-native-reanimated found. Attempting to build from source.
Android gradle plugin: 7.4.2
Gradle: 8.0.1
WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL.

The Kotlin Gradle plugin was loaded multiple times in different subprojects, which is not supported and may break the build.
This might happen in subprojects that apply the Kotlin plugins with the Gradle 'plugins { ... }' DSL if they specify explicit versions, even if the versions are equal.
Please add the Kotlin plugin to the common parent project or the root project, then remove the versions in the subprojects.
If the parent project does not need the plugin, add 'apply false' to the plugin line.
See: https://docs.gradle.org/current/userguide/plugins.html#sec:subprojects_plugins_dsl
The Kotlin plugin was loaded in the following projects: ':shopify_flash-list', ':expo-modules-core', ':react-native-gesture-handler', ':react-native-safe-area-context', ...

> Task :app:processDebugMainManifest
E:\react-native\FlixPulse\android\app\src\debug\AndroidManifest.xml:6:5-162 Warning:
        application@android:usesCleartextTraffic was tagged at AndroidManifest.xml:6 to replace other declarations but no other declaration present
E:\react-native\FlixPulse\android\app\src\debug\AndroidManifest.xml:21:9-30:20 Warning:
        provider#expo.modules.filesystem.FileSystemFileProvider@android:authorities was tagged at AndroidManifest.xml:21 to replace other declarations but no other declaration present

> Task :expo-modules-core:compileDebugKotlin FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':expo-modules-core:compileDebugKotlin'.
> Could not resolve all files for configuration ':expo-modules-core:debugCompileClasspath'.
   > Failed to transform expo-modules-core$android-annotation.jar (project :expo-modules-core$android-annotation) to match attributes {artifactType=android-classes-jar, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.jvm.environment=standard-jvm, org.gradle.jvm.version=11, org.gradle.libraryelements=jar, org.gradle.usage=java-api, org.jetbrains.kotlin.platform.type=jvm}.
      > Execution failed for JetifyTransform: E:\react-native\FlixPulse\node_modules\expo-modules-core\android-annotation\build\libs\expo-modules-core$android-annotation-1.1.1.jar.
         > Failed to transform 'E:\react-native\FlixPulse\node_modules\expo-modules-core\android-annotation\build\libs\expo-modules-core$android-annotation-1.1.1.jar' using Jetifier. Reason: IllegalArgumentException, message: Unsupported class file major version 63. (Run with --stacktrace for more details.)
           Suggestions:
            - Check out existing issues at https://issuetracker.google.com/issues?q=componentid:460323&s=modified_time:desc, it's possible that this issue has already been filed there.
            - If this issue has not been filed, please report it at https://issuetracker.google.com/issues/new?component=460323 (run with --stacktrace and provide a stack trace if possible).

> Run with --stacktrace option to get the stack trace.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 2s
151 actionable tasks: 34 executed, 117 from cache
Error: E:\react-native\FlixPulse\android\gradlew.bat exited with non-zero code: 1
Error: E:\react-native\FlixPulse\android\gradlew.bat exited with non-zero code: 1
    at ChildProcess.completionListener (E:\react-native\FlixPulse\node_modules\@expo\cli\node_modules\@expo\spawn-async\build\spawnAsync.js:52:23)
    at Object.onceWrapper (node:events:629:26)
    at ChildProcess.emit (node:events:514:28)
    at cp.emit (E:\react-native\FlixPulse\node_modules\@expo\cli\node_modules\cross-spawn\lib\enoent.js:34:29)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)
    ...
    at Object.spawnAsync [as default] (E:\react-native\FlixPulse\node_modules\@expo\cli\node_modules\@expo\spawn-async\build\spawnAsync.js:17:21)
    at spawnGradleAsync (E:\react-native\FlixPulse\node_modules\@expo\cli\build\src\start\platforms\android\gradle.js:72:46)
    at Object.assembleAsync (E:\react-native\FlixPulse\node_modules\@expo\cli\build\src\start\platforms\android\gradle.js:52:18)
    at runAndroidAsync (E:\react-native\FlixPulse\node_modules\@expo\cli\build\src\run\android\runAndroidAsync.js:36:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Ignite version
9.0.0
Additional info
PS E:\react-native\FlixPulse> npx ignite-cli doctor
System
  platform           win32
  arch               x64
  cpu                12 cores     Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  directory          FlixPulse    E:\react-native\FlixPulse

JavaScript (and globally-installed packages)
  node               20.9.0       D:\nodejs\node.EXE
  npm                10.1.0       D:\nodejs\npm.CMD
    yarn             1.22.21
  yarn               1.22.21      C:\Users\chankruze\AppData\Roaming\npm\yarn.CMD
  pnpm               -            not installed
  bun                -            not installed
  expo               49.0.18      managed

Ignite
  ignite-cli         9.0.0        C:\Users\chankruze\AppData\Local\npm-cache\_npx\e31027f3785124a8\node_modules\.bin\ignite.CMD
  ignite src         build        C:\Users\chankruze\AppData\Local\npm-cache\_npx\e31027f3785124a8\node_modules\ignite-cli\build

Android
  java               19.0.2       D:\jdk-19.0.2\bin\java.EXE
  android home       -            D:\Android\Sdk

Tools
  git                git version 2.36.1.windows.1   D:\Git\cmd\git.EXE

Now I'm trying to go with Expo Go and npm. Let's see...

You have the incorrect JDK set up it looks like, try following the environment setup docs here: https://reactnative.dev/docs/environment-setup?os=windows&platform=android

Yes, jdk-11 resolves this issue.

authors: chankruze frankcalise

repo: infinitered/ignite

license: mit

license_source: bigquery


text:
Generated folder is incomplete

Hiya!
I've been trying to create a new project with the new version but it does not include Android and IOS folder etc Basically it does not complete. The new command ends with the output below
✔ Linking external libs
⠋ Linking external libs./PickUp/ios/PickUp/Info.plist: file does not exist or is not readable or is not a regular file (Error Domain=NSCocoaErrorDomain Code=260 "The file “Info.plist” couldn’t be opened because there is no such file." UserInfo=0x7f9df14152a0 {NSFilePath=./PickUp/ios/PickUp/Info.plist, NSUnderlyingError=0x7f9df1413f80 "The operation couldn’t be completed. No such file or directory"})
✔ Updating PList file
⠋ Cleaning up after messy guestscd: no such file or directory: PickUp/android
/bin/sh: ./gradlew: No such file or directory
✔ Cleaning up after messy guests

So I think it's broken

[x] Issue does not already exist
Identify exactly what aspect your issue is about

[ ] ignite base application
[ ] ignite the cli
[x] ignite generated code

Also, for the quickest assistance i run ignite doctor and the everything is below (including the lines with 3 backticks).
Computer
  Platform: darwin

Ignite
  Version: 1.8.0
  Path: /Users/osi/.nvm/versions/node/v4.2.1/bin/ignite

Node
  Version: v4.2.1
  Path: /Users/osi/.nvm/versions/node/v4.2.1/bin/node

NPM
  Version: 3.8.6
  Path: /Users/osi/.nvm/versions/node/v4.2.1/bin/npm

Yeoman
  Version: 1.8.4

React Native CLI
  Version: 1.0.0

App
  React Native Version: ¯\_(ツ)_/¯

Hey!  What happens when you create a react native project without Ignite?  Does it make those 2 folders?

I think i traced the problem. An npm package in my local cache had a corrupted package.json file, so that kept breaking the install process. It would be nice if there was a nice error stating that npm could not install dependencies or something

that's wild!  If you give us a good way to detect that, we can add that to our CLI

This issue is related to npm/npm#6084. I'll look into it

authors: GantMan osiloke


text:
First run at adding RNR episodes, additional refactoring, and docs

This is a WIP -- I'll explain in more detail later. It probably won't live in the main tab bar...maybe.

Latest commit should fix CI.


text:
Feature/repo add with optionals

Add a funtion to allow repository add with the other command line parameters. Useful to add authenticated repositories

Hi @andreclaudino, thanks for the PR! I'll read through this and leave some comments sometime in the next day :)

@andreclaudino can you minimize this PR to only semantic changes in the code? It is easier to review when there is not the extra diff noise of moving code from one file to another. I saw you opened another PR for just breaking lib.rs into multiple modules, but you're also doing some of that here. Would you mind moving all of the refactor-only changes to that PR?

@nicholastmosher, You can just ignore this PR for a while. Evaluate the other, if is ok, I can just open a new PR with the complements.

authors: andreclaudino nicholastmosher

repo: infinyon/fluvio-helm


text:
Influx CLI 2.6

ETA: December 15 2022
See changelog for all PRs associated with this release:
Bug Fixes

ac1eb0b: Handle "every" when defined inside of flux

Other

e16398c: Chore: upgrade Go to 1.19.3
41059f5: Chore: update to openapi 5.1.1 to enable arm builds
11859bd: Chore: update 2.5 changelog (and add missing entries)
429cc0e: Chore: upgrade Go to 1.19.4
90e825c: Chore: update go-prompt to fix terminal clear issue

These are all the changes as of now, I don't expect anything further to be merged but will update if there are.


text:
Can't custom the size of charts in Dashboard?

URL for relevant page?
What products and version are you using?
Chronograf 0.13 start by Docker Container
Where did you look before opening the issue?
Also can't move the charts at all.

@yonger1516 this looks like an issue with Chronograf, not the docs. Please email chronograf@influxdb.com for bug reports and feature requests on Chronograf.


text:
golang influx client missing

In golang we used the "github.com/influxdata/influxdb/client/v2" package to have a influx client in golang...
It seems that the client is now missing from the repository...
No client, no doc, no info on how to transition...
go get github.com/influxdata/influxdb/client/v2
package github.com/influxdata/influxdb/client/v2: cannot find package "github.com/influxdata/influxdb/client/v2" in any of:
/usr/local/go/src/github.com/influxdata/influxdb/client/v2 (from $GOROOT)
/go/src/github.com/influxdata/influxdb/client/v2 (from $GOPATH)

Same issue here, i am using CentOS 7.5
go get -u github.com/influxdata/influxdb/client/v2
package github.com/influxdata/influxdb/client/v2: cannot find package "github.com/influxdata/influxdb/client/v2" in any of:
/usr/lib/golang/src/github.com/influxdata/influxdb/client/v2 (from $GOROOT)
/root/go/src/github.com/influxdata/influxdb/client/v2 (from $GOPATH)

@satishdotpatel look into https://github.com/influxdata/influxdb/issues/11035#issuecomment-453783909

Estou com o mesmo erro também, alguém conseguiu resolver?
CentOS Linux release 7.6.1810 (Core)
[root@mq gowork]# go get -u github.com/influxdata/influxdb/client/v2
package github.com/influxdata/influxdb/client/v2: cannot find package "github.com/influxdata/influxdb/client/v2" in any of:
/usr/lib/golang/src/github.com/influxdata/influxdb/client/v2 (from $GOROOT)
/opt/gowork/src/github.com/influxdata/influxdb/client/v2 (from $GOPATH)
[root@mq gowork]#

Refer to https://github.com/influxdata/influxdb/issues/11035#issuecomment-453783909
go get -u github.com/influxdata/influxdb1-client/v2

@pauldix Errm, you didn't put the latest v2 client into https://github.com/influxdata/influxdb1-client... my december fixup (https://github.com/influxdata/influxdb/pull/10130) wasn't ported over.

Added it in this PR https://github.com/influxdata/influxdb1-client/pull/10. Will have someone review tomorrow and merge.

Where are the docs for github.com/influxdata/influxdb/client/v2 ?

@maxp-edcast https://github.com/influxdata/influxdb-client-go
This isn't quite ready for use...

@pauldix It seems like the following does not work inside go projects with go modules enabled, since the repo has no v2 branch or tag:
go get github.com/influxdata/influxdb1-client/v2
go: finding github.com/influxdata/influxdb1-client/v2 latest
go: github.com/influxdata/influxdb1-client/v2@v2.0.0-20190402204710-8ff2fc3824fc: missing github.com/influxdata/influxdb1-client/go.mod and .../v2/go.mod at revision 8ff2fc3824fc
go: error loading module requirements

Even specifying the master branch does not work:
go get github.com/influxdata/influxdb1-client/v2@master
go: finding github.com/influxdata/influxdb1-client/v2 master
go: github.com/influxdata/influxdb1-client/v2@v2.0.0-20190402204710-8ff2fc3824fc: missing github.com/influxdata/influxdb1-client/go.mod and .../v2/go.mod at revision 8ff2fc3824fc
go: error loading module requirements

Please take a look at: https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

authors: cblomart florentinolim gihankarunarathne karalabe maxp-edcast mback2k pauldix satishdotpatel timhallinflux

repo: influxdata/influxdb


text:
geo package raises error for specific timeframes

Hi,
I would like to report a bug I found in geo package:
Despite having bucked created and records in it, Influx raises error {"error": "not found: error calling function \"filterRows\": error calling function \"getColumn\": error calling function \"tableFind\": no table found"} when there are no records to return for certain time frame. Which is inconsistent behaviour to the regular query which returns empty result and doesn't raise error.
Steps to reproduce:
I'm using influxdb v2 and golang client
writing record:
package main

import (
	"fmt"
	"strconv"
	"time"

	geos2 "github.com/golang/geo/s2"
	influxdb2 "github.com/influxdata/influxdb-client-go/v2"
)

var (
	token   = "securityToken"
	address = "http://localhost:9999"
	dbName  = "myBucket"
	dbOrg   = "myOrg"
)

func main() {

	client := influxdb2.NewClientWithOptions(address, token, influxdb2.DefaultOptions())
	writeAPI := client.WriteAPI(dbOrg, dbName)

	errorsCh := writeAPI.Errors()
	go func() {
		for err := range errorsCh {
			fmt.Printf("write error: %s\n", err.Error())
		}
	}()

	pt := influxdb2.NewPointWithMeasurement("test")
	pt.AddTag("tag1", strconv.FormatUint(1, 10))
	pt.AddField("value", []byte("here comes payload"))
	pt.AddField("lat", 4.8)
	pt.AddField("lon", 16.32)

	pt.SetTime(time.Now())

	ll := geos2.LatLngFromDegrees(4.8, 16.32)
	cellid := geos2.CellIDFromLatLng(ll)
	pt.AddTag("s2_cell_id", cellid.ToToken())

	writeAPI.WritePoint(pt)
	writeAPI.Flush()

	client.Close()
}

reading record:
package main

import (
	"context"
	"fmt"
	"time"

	influxdb2 "github.com/influxdata/influxdb-client-go/v2"
	"github.com/influxdata/influxdb-client-go/v2/api"
)

var (
	token   = "securityToken"
	address = "http://localhost:9999"
	dbName  = "myBucket"
	dbOrg   = "myOrg"
)

func readFromInfluxGeo(queryAPI api.QueryAPI, time uint32) {

	query := fmt.Sprintf(`import "experimental/geo" from(bucket: "%s") `, dbName)
	query += fmt.Sprintf(`|> range(start: -%vs, stop: now()) `, time)
	query += `|> filter(fn: (r) => r.tag1 == "1") `
	query += `|> geo.filterRows(region: {lat: 4.79, lon: 16.319, radius: 10.0}, strict: true)`

	result, err := queryAPI.Query(context.Background(), query)
	if err != nil {
		fmt.Printf("Error: %v\n", err.Error())
		return
	}

	for result.Next() {
		vals := result.Record().Values()
		fmt.Printf("  %v\n", vals)
	}

	if result.Err() != nil {
		fmt.Printf("Error: %v", result.Err())
		return
	}
}

func readFromInflux(queryAPI api.QueryAPI, time uint32) {

	query := fmt.Sprintf(`from(bucket: "%s") `, dbName)
	query += fmt.Sprintf(`|> range(start: -%vs, stop: now()) `, time)
	query += `|> filter(fn: (r) => r.tag1 == "1")`

	result, err := queryAPI.Query(context.Background(), query)
	if err != nil {
		fmt.Printf("Error: %v\n", err)
		return
	}

	for result.Next() {
		vals := result.Record().Values()
		fmt.Printf("  %v\n", vals)
	}

	if result.Err() != nil {
		fmt.Printf("Error: %v", result.Err())
		return
	}
}

func main() {

	client := influxdb2.NewClientWithOptions(address, token, influxdb2.DefaultOptions())
	queryAPI := client.QueryAPI(dbOrg)

	fmt.Printf("\n\nRead records with 10s window:\n\n")
	readFromInfluxGeo(queryAPI, 10)

	time.Sleep(time.Second * 3)

	fmt.Printf("\n\n\n\nRead records with 1s window:\n\n")
	readFromInfluxGeo(queryAPI, 1)  // raises error

	fmt.Printf("\n\n\n\nRead records with 30s window:\n\n")
	readFromInfluxGeo(queryAPI, 30)

	fmt.Printf("\n\n")

	fmt.Printf("-----------------------------------------------------------------------\n\n")
	fmt.Printf("\n\nRead records with 10s window:\n\n")
	readFromInflux(queryAPI, 10)
	time.Sleep(time.Second * 3)

	fmt.Printf("\n\n\n\nRead records with 1s window:\n\n")
	readFromInflux(queryAPI, 1) // returns empty result

	fmt.Printf("\n\n\n\nRead records with 30s window:\n\n")
	readFromInflux(queryAPI, 30)

	client.Close()
}

Expected behavior:
call readFromInfluxGeo(queryAPI, 1) should return empty result
Actual behavior:
error raised: "no table found"
Environment info:

System info: running inside docker: Linux 4.19.76-linuxkit x86_64
InfluxDB version: InfluxDB 2.0.0-beta.14

i'm going to close this for now since it was opened against a pre-release version of influxdb. if you are still facing this problem, please open a new issue with the details.


text:
Influx 2.0.5 restore fails with: Error: failed to restore KV snapshot: InfluxDB OSS-only command failed: 500 Internal Server Error: An internal error has occurred

Background:
I'm trying to upgrade from 2.0.5 to 2.1.1 on a separate raspberry pi. I've tried to restore the 2.0.5 backup both to a fresh install of 2.1.1, and when that failed, a fresh install of 2.0.5.
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

On a populated 2.0.5 database run "influx backup name_of_backup_dir -t $TOKEN"
Copy directory to a new raspberry pi and follow install instructions:
wget https://dl.influxdata.com/influxdb/releases/influxdb2-2.0.5-linux-arm64.tar.gz  (Ideally, I'd want 2.1.1 to work here)
tar xvzf influxdb2-2.0.5-linux-arm64.tar.gz
sudo cp influxdb2-2.0.5-linux-arm64/influxd /usr/local/bin/
wget https://dl.influxdata.com/influxdb/releases/influxdb2-client-2.2.0-linux-arm64.tar.gz
tar xvzf influxdb2-client-2.2.0-linux-arm64.tar.gz
sudo cp influxdb2-client-2.2.0-linux-arm64/influx /usr/local/bin/
influxd --reporting-disabled --storage-retention-check-interval=24h
influx setup --token $TOKEN
influx restore ~/backup name_of_backup_dir/ --full

Expected behavior:
All data restored and replaced with time series data and InfluxDB key-value data such as tokens, users, dashboards, from the original backup.
Actual behavior:
INFO: Restoring KV snapshot
Error: failed to restore KV snapshot: InfluxDB OSS-only command failed: 500 Internal Server Error: An internal error has occurred
Trying to view the web interface just shows a loading circle.
Environment info:

System info: Linux 5.10.103-v8+ aarch64 GNU/Linux (Bullseye)
InfluxDB version: InfluxDB 2.0.5 (git: 741389781e) build_date: 2021-04-27T17:57:07Z
Other relevant environment details: Raspberry Pi3 with fresh OS, updated & upgraded, no other modifications made/programs installed.

Config:
Just the two command line flags: --reporting-disabled --storage-retention-check-interval=24h
Maybe important: the original backup database location was on a mounted SSD storage, whereas I'm restoring to a default but different) location.
Logs:
The 2.0.5 logs didn't give further details. At the risk on confusing the issue, the output from when I tried the same steps but with 2.1.1 were:
2022-03-20T10:51:35.802221Z     warn    internal error not returned to client   {"log_id": "0_LjC2sG000", "handler": "error_logger", "error": "[shard 606] optogen/606/index/3/MANIFEST: too many open files"} 2022-03-20T10:51:35.802309Z     error   manifest write failed, index is potentially damaged     {"log_id": "0_LjC2sG000", "service": "storage-engine", "indexi/.influxdbv2/engine/data/14a8ce509a563be6/autogen/606/index/0/MANIFEST: too many open files"} 2022-03-20T10:51:35.802334Z     error   manifest write failed, index is potentially damaged     {"log_id": "0_LjC2sG000", "service": "storage-engine", "indexi/.influxdbv2/engine/data/14a8ce509a563be6/autogen/606/index/2/MANIFEST: too many open files"} Error: failed to restore KV snapshot: InfluxDB OSS-only command failed: 500 Internal Server Error: An internal error has occurred - check server logs

How much RAM does this Raspberry Pi have and do you have the ability to test the restore on another, larger machine? You also might need to raise your ulimit given the too many open files error logs.
Can you also just run a tree or something similar on the data directory (looks like you're using the default at ~.influxdbv2) and provide the number of directories and files reported?

pi@hass:~/.influxdbv2 $ tree -a
.
└── configs

0 directories, 1 file

All the files are on an SSD, which tree reports "1246 directories, 2019 files"
The Pi is a 2 GB version.
This issue is still a problem, but I worked around it by exporting each month in line protocol, and then using the UI in version 2.6 to drag n drop each file in.


text:
fix: don't break on auto detected delimiters

this is the fix for influxdata/idpe#7553, influxdata/idpe#5420 for the flux parser that sits behind the fluxParser feature flag within influxdb.
this had something to do with papaparse choosing its own delimiters for tearing apart a csv. Hard coding them made the whole thing fall away.
Also set up a pattern where we can capture offending flux results from network requests as a CSV and load them straight into the testing framework. It was super cool to not understand what was wrong with the code and still write a test to capture it before trying to fix it. TDD FTW.

i honestly dont know what the bug is, or how it was caused, just that adding those things made it work. Those seem like the same defaults we've been relying on for all of the other queries, so why did being specific make them work?
all this to say, i dont know what to change it to?


text:
Change the default stats interval to 1 second instead of 10 seconds

Update the configuration file's comment to mention the limitations of max-select-point.

[ ] Rebased/mergable
[ ] Tests pass
[ ] CHANGELOG.md updated
[ ] Sign CLA (if not already signed)
[ ] Config changes: update sample config (etc/config.sample.toml), server NewDemoConfig method, and Diagnostics methods reporting config settings, if necessary

@rbetts this is separated into two commits so we can cherry pick the first commit to 1.3.


text:
Update client README - close client resources

The best practice is to close used resources at the end. I've had a problem when I used this code in AWS Golang Lambda function without c.Close(): socket: too many open files - I've reached connection limit because InfluxDB connections have been still opened.

[X] Sign CLA (if not already signed)
[X] Provide example syntax

@jangaraj can you squash the commits for this?

@jsternberg done

authors: jangaraj jsternberg


text:
Too many alerts even with stateChangesOnly - bug in evalNode?

Hi!
I'm using Kapacitor 1.3 and InfluxDB 1.2.
I use an influxDBOutNode to write in influxDB. So as not to get spam all day long I use a stateChangesOnly(24h) on my alertNode.
Yet sometimes (not always, I didn't manage to find a criteria) multiple alerts are written on influxDB. Plus, values of fields are modified where they souldn't have been (I suspect due to an evalNode).
Here is my tick script:
var alert = data
  |alert()
    .crit(lambda: "value"!=0 AND "value"!=1)
    .message('ENERWHERE {{ .Level }} ALERT: anormal value of drive1_mode = {{index .Fields "value"}} (should be 0 or 1)')
    .id('driveMode')
    .idTag('id')
    .levelTag('level')
    .messageField('message')

// Alert
alert
.log('/tmp/driveMode_alert.log')

//Writing on InfluxDB
|eval(lambda: if ("value"!=0 AND "value"!=1, 1, 0), lambda: "value", lambda: "message")
    .as('crit','data','msg')
    .keep('crit','data','msg')
|where(lambda: "id" != '')
|influxDBOut()
    .database('enerwhere')
    .retentionPolicy('autogen')
    .measurement('alert')
    .tag('tracker',tracker)

Here is the data I find strange:
InfluxDB shell version: 1.2.4
> select crit,id,level,data,msg from alert where id='driveMode'

name: alert
time                crit id        level    data msg
----                ---- --        -----    ---- ---
1497174631000000000 1    driveMode CRITICAL 4    ENERWHERE CRITICAL ALERT : anormal value of drive1_mode = 4 (should be 0 or 1)
1497174632000000000 0    driveMode CRITICAL 1    ENERWHERE CRITICAL ALERT : anormal value of drive1_mode = 4 (should be 0 or 1)
1497193780000000000 0    driveMode OK       0    ENERWHERE OK ALERT : anormal value of drive1_mode = 0 (should be 0 or 1)

First, I don't understand why two CRITICAL alerts are written in influxDB. I verified, only one has been logged on /tmp/driveMode_alert.log.
Second, as you can see in the script, when the level is CRTITICAL the field crit should be 1. In addition, the field data is nothing but the field value renamed, data has changed but the msg is identical!
Any idea?

I do not see stateChangesOnly anywhere in your example.

@phemmer thank you for noticing I took the wrong example.
Here is another one with the right alert:
TICK script:
// Thresholds
var alert = data
  |alert()
    .warn(lambda: ("value" > warn OR "value" < -warn) AND "roll" < max_roll_angle AND "roll" > min_roll_angle AND "sun" == '1' AND "mode"==5)
    .crit(lambda: ("value" > crit OR "value" < -crit) AND "roll" < max_roll_angle AND "roll" > min_roll_angle AND "sun" == '1' AND "mode"==5)
    .message('UNIVRABAT {{ .Level }} ALERT : wrong roll angle : {{index .Fields "value"}}')
    .id('roll')
    .idTag('id')
    .levelTag('level')
    .messageField('message')
    .stateChangesOnly(24h)

// Alert
alert
.log('/tmp/roll_alert.log')

//Writing on InfluxDB
|eval(lambda: if (("value" > crit OR "value" < -crit) AND "roll" < max_roll_angle AND "roll" > min_roll_angle AND "sun" == '1' AND "mode"==5, 1, 0), lambda: "value", lambda: "message")
    .as('isCrit','data','msg')
	.keep('isCrit','data','msg')
|where(lambda: "id" != '')
|influxDBOut()
	.database('univrabat')
    .retentionPolicy('autogen')
    .measurement('alert')
	.tag('tracker',tracker)

What I find strange:
InfluxDB shell version: 1.2.4
> select * from alert where id='roll'
name: alert
time                crit data                 id   isCrit level    msg                                                              tracker
----                ---- ----                 --   ------ -----    ---                                                              -------
1497939180000000000      5.942759999999993    roll 0      WARNING  UNIVRABAT WARNING ALERT : wrong roll angle : 6.136759999999995   F3
1497939240000000000      6.136759999999995    roll 0      WARNING  UNIVRABAT WARNING ALERT : wrong roll angle : 6.136759999999995   F3
1497940380000000000      9.87554              roll 0      CRITICAL UNIVRABAT CRITICAL ALERT : wrong roll angle : 10.071699999999993 F3
1497940440000000000      10.071699999999993   roll 1      CRITICAL UNIVRABAT CRITICAL ALERT : wrong roll angle : 10.071699999999993 F3
1497952020000000000      0.02480000000000615  roll 0      OK       UNIVRABAT OK ALERT : wrong roll angle : 0.02480000000000615      F3
1497952080000000000      0.012290000000000134 roll 0      OK       UNIVRABAT OK ALERT : wrong roll angle : 0.02480000000000615      F3
1498111980000000000      5.888289999999998    roll 0      WARNING  UNIVRABAT WARNING ALERT : wrong roll angle : 6.085419999999999   F3
1498112040000000000      6.085419999999999    roll 0      WARNING  UNIVRABAT WARNING ALERT : wrong roll angle : 6.085419999999999   F3
1498113180000000000      9.821340000000006    roll 0      CRITICAL UNIVRABAT CRITICAL ALERT : wrong roll angle : 10.017539999999997 F3
1498113240000000000      10.017539999999997   roll 1      CRITICAL UNIVRABAT CRITICAL ALERT : wrong roll angle : 10.017539999999997 F3
1498134060000000000      83.7139138           roll 0      OK       UNIVRABAT OK ALERT : wrong roll angle : 83.7139138               F3
1498134120000000000      83.9312362           roll 0      OK       UNIVRABAT OK ALERT : wrong roll angle : 83.7139138               F3

All the alerts are "doubled" with 1 second interval, with the same field issue I mentioned above.
Thanks again!

I just replayed my first example with stateChangesOnly(24h), it lead to the same result as I expected.
As I said above the problem doesn't come from the "kapacitor part" of the script. Indeed the correct number of alerts are logged.
The problem seems to occur with or after the evalNode, in the influxDBOut process.

authors: lblt phemmer

repo: influxdata/kapacitor


text:
Cannot connect localhost:8086 when tunnelling to InfluxDB UI

I use -L 8086:x.x.x.x:8086 to tunnel some private IP's on our network. InfluxDB UI does query directly from the browser.
Any way for InfluxDB UI to proxy the queries instead?
The workaround is to tunnel 8086 on localhost as well. But that means 1 connection possible.

@smalenfant there is no setting for the Admin UI to proxy requests, there's only the explicit connection setting to select the port (and that must match the config file setting as well.)
@rossmcdonald any thoughts on how this might work?

@smalenfant I think the easiest solution would be to proxy the communication at the browser level. You can do this directly using SSH's -D <port> option (opening a SOCKS proxy), or you can use a more robust solution such as squid or polipo if you will have multiple people/services connecting at once. Once you have the proxy setup, you can modify the settings in your browser (or use a plugin) to forward the communication over the proxy instead of trying to query Influx directly.
I hope that helps!

authors: beckettsean rossmcdonald smalenfant

repo: influxdb/influxdb


text:
Libvirt Plugin

This Plugin collects virtdomain infos from a Libvirt deamon.
I'm planning to add interface and block device statistics in a later pull request.
$ ./telegraf -config etc/config.toml -test
* Plugin: libvirt, Collection 1
> libvirt_cpu_time,host=test,node=odin value=1447157114730809000i 1447157114730815923
> libvirt_max_mem,host=test,node=odin value=8388608i 1447157114730880494
> libvirt_memory,host=test,node=odin value=2097152i 1447157114730906774
> libvirt_nr_virt_cpu,host=test,node=odin value=2i 1447157114730921874

(Disclaimer: This is my first Go code. Feedback is much appreciated.)

Any idea why the libvirt-go package can't be found by CircleCI?

@neckhair you need to add it to the godep dependencies, like this:
go get github.com/tools/godep
godep restore ./...
godep save ./...

If you are having trouble using godep, you can give me write-access to your branch and I can fix it, or pull your changes and make a separate PR

@neckhair thank you very much for this! looks good, could you please also update the supported plugins list on the README and add this to the CHANGELOG (under features)

@sparrc Thanks for your comments. I'll try to work on them in the next few days.

@sparrc Ready for another review. Do you like all the commits to be squashed?

@neckhair don't worry about squashing the commits.
I definitely know that some users would like this plugin, but I think I need to figure something out that won't make libvirt a build requirement. The reason being is that libvirt would be the first external (non-go) dependency added to the Telegraf project. Let me think and talk with some other Influx folks about what our options may be.
cc @otoolep @pauldix @toddboom thoughts on adding libvirt as an external dependency to Telegraf? Other build options we may have for "optional" plugins?

Not a huge fan of adding an external dependency like this. Will I forced to get this library to build Telegraf? What if it doesn't exist for my platform?

As long as we can still build for all platforms (Windows and ARM included) then I don't think it's an issue. Might make the builds more complex?

@otoolep yes, you would be forced to, I'm trying to think of a way that a plugin could be optionally compiled

@pauldix it means that building doesn't just require a Go environment, but also the libvirt C library

Any news on this? If this gets merged I will work on network and disk stats.

@neckhair I don't really like making libvirt a compile-time dependency of Telegraf, mainly because it means that we wouldnt be able to only use standard Go tools to build the project anymore, and also means that there would need to be an OS switch in the makefile for Ubuntu, Darwin, FreeBSD, CentOS, etc.

Ok, I understand the concerns. I close this PR and we'll keep our own fork for internal use and reference for others. I created a new PR against our fork to keep track of it: https://github.com/ninech/telegraf/pull/3.

@neckhair please re-open, I haven't gotten to updating the build process yet but still would like to include this in Telegraf

@sparrc I'd like to but github doesn't let me (because I force-pushed?). Let me know when you have a way to do it. I'll create a new PR then.

force pushes should be OK, I'll see what I can do

@neckhair Do you think you can re-open this PR based off master?
It's probably easiest to just re-copy the plugin into the new plugins/inputs directory. I've got a sensors plugin that relies on libsensor now, so we can go forward with having plugins with C dependencies.

@neckhair ( cc: @sofixa ): are you able to re-submit this as comments above mentions?
there are several users who would like to see this merged, including @sparrc. :)

I'll give it a try later today.

@sparrc I am currently working on rebasing the libvirt plugin with the current version of Telegraf, but i've hit something on the road:
The libvirt-go package @neckhair used no longer seems to be supported by the same person(the new repo is here https://github.com/rgbkrk/libvirt-go), and there are incompatibility issues with various versions of libvirt, so there are two packages  - v1 and v2(as tagged in GitHub) for versions 0.9.8 and below, and 1.2.2 and up, respectively (at least that's what i understand).
How should i proceed? Import both versions and, depending on the libvirt version, use the one that corresponds? Or use only the v2, thus making the input unusable with older versions of libvirt?

@sofixa @sparrc Thank you for working on this. Unfortunately I am busy with other stuff at the moment and can't help.

@sofixa ASAIK libvirt-go v1 and v2 share the same API to get libvirt version, so we can using this api to detect which libvirt-go version I should used.  Also we should include both v1 and v2 into dependencies. Does it make sense?

authors: Millnert gtt116 neckhair otoolep pauldix sofixa sparrc

repo: influxdb/telegraf


text:
🛑 alternative site is down

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

HTTP code: 0
Response time: 0 ms

Resolved: alternative site is back up in 3dbf6bf after 9 minutes.


text:
🛑 alternative site is down

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

HTTP code: 0
Response time: 0 ms

Resolved: alternative site is back up in a1054da after 1 hour, 35 minutes.


text:
🛑 alternative site is down

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

HTTP code: 0
Response time: 0 ms

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


text:
Fix layout of webpage

The last three lines belong to the body block.
Signed-off-by: Stefan Weil sw@weilnetz.de

I think this was fixed along the way. Thank you.

authors: kba stweil

repo: infolis/infolis-web


text:
Investigate transaction submission from Hermes

Background
We should investigate the details of how transaction submission works in Sovereign SDK chains and, essentially, answer the following questions:

How to encode transactions
How to query for transaction status
How to interpret transaction errors

(This list may get updated as we move forward)

Accomplished by https://github.com/informalsystems/hermes-sdk/pull/191

repo: informalsystems/sovereign-ibc


text:
Change makefile targets to fix Github Actions issues

Currently for testing we use a bunch of npm dependencies that are not needed while building chaise. That's why we listed them as part of devDepencendies and this allows us to do npm install --production during make install, while we have to do npm install before testing.
I'm not sure when this happened, but it seems like the behavior of npm install --production is not the same as before. If you do npm install and then npm install --production it will remove all the dev dependencies. That's why the test cases in Github Actions started failing since last week.
So,

Introduced a install-test-deps Makefile target to install dependencies after doing make install in Github Actions.
Updated test Makefile targets to not install anything by default and only run tests. Previously we used to update webdriver as part of test target. This was causing issues in Github Actions as we have to use the privileged user for changing the folder, but the CI environment variable is not available for the privileged user in Github.
Introduced a update-webdriver that can be used before running test cases.
Updated documentation based on the changes (I need to update the docs and remove the parts that mention we're updating webdriver automatically. I didn't do it so it doesn't affect the currently running test build)

@jrchudy The PR is ready to be reviewed. I made the changes based on our discussions and cleaned up the documentation/help target to reflect these changes.

repo: informatics-isi-edu/chaise


text:
RDT improvements

Added support for visualising historical tracks of storms, future expected direction (based on AMV winds), and enhanced hovertool features.

@claretandy it seems to me that every sub-Loader, e.g. PolygonLoader etc. is loading the same file, they don't need to use the Locator they can just be given a file by the top-level Loader. I'll go ahead and make that change and test it on the tutorial data

Also, now the sub-Loaders are classes with a single method, I think inlining them makes sense. It wasn't clear when we started that an inline solution would be cleaner

I spotted a bug when FileNotFound happens

@claretandy that pull request was quite complicated, I tested it with the tutorial data to make sure it worked. I fixed a few bugs and simplified the design (sorry if it impacted your number of lines statistic)

authors: andrewgryan claretandy

repo: informatics-lab/forest


text:
feat(aws): Add support AWS WAFv2

Init commit
Issue #506
aws_wafv2_web_acl:
component : Rule groups
I can't get value rule.rule_group_reference_statement.arn(always 0) - I need advice what logic to implement this component

Looks like the TF file has an issue in this PR? Have you tried running this to see if that works ok locally?
 INFRACOST_LOG_LEVEL=info make -s run ARGS="breakdown --path internal/providers/terraform/azure/your_project"

    Error: Too many action blocks
      on  line 0:
      (source code not available)
    No more than 1 "action" blocks are allowed
    Error: Too many action blocks
      on  line 0:
      (source code not available)
    No more than 1 "action" blocks are allowed

=== CONT  TestWafV2WebAclGoldenFile
    tftest.go:197:
        	Error Trace:	tftest.go:197
        	            				wafv2_web_acl_test.go:15

I can't get value rule.rule_group_reference_statement.arn(always 0) - I need advice what logic to implement this component

@NeverovDS can you please paste an example terraform block, or point me to which of the tests in this PR have the issue so I can reproduce/investigate it?

repo: infracost/infracost


text:
Fixed 'or' error for BitSets of longer length

Code to reproduce below. To correct I think you could either make a temp copy of the shorter and increase it's length (slow), permanently increase the length of the shorter (little faster), request the # of flags length in the constructor (faster, but prone to user error & changes in requirements), or perform a length check & flip (as shown in the PR)
a = new BitSet();
b = new BitSet();
a.set(1);
b.set(50);
a.or(b).toString(2)
"10"
b.or(a).toString(2)
"100000000000000000000000000000000000000000000000010"

Thanks for that!

I changed your pull request and fixed it for the other methods as well. You made a really good point here. Thanks again for that!
BTW I just upgraded to 3.0.0, which also incorporates a change on the API that every function call returns a new instance to make it an immutable class. This was a flaw in the previous design.
Robert

authors: infusion mattkrick


text:
Catch generic Exception on dispatch and do Skip.

If something bad happens while processing a request, the exception will be caught by the dispatcher so the program does not crash and the request is simply skipped.

Codecov Report

Merging #53 into master will decrease coverage by 0.5%.
The diff coverage is 20%.

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
- Coverage    91.6%   91.09%   -0.51%
==========================================
  Files          31       31
  Lines        1405     1415      +10
==========================================
+ Hits         1287     1289       +2
- Misses        118      126       +8

Impacted Files
Coverage Δ

connect/resources/fulfillment_automation.py
37.5% <0%> (-2.8%)
:arrow_down:

connect/resources/tier_config_automation.py
90.47% <40%> (-6.83%)
:arrow_down:

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 a9031ba...2dccd38. Read the comment docs.

Codecov Report

Merging #53 into master will decrease coverage by 0.5%.
The diff coverage is 20%.

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
- Coverage    91.6%   91.09%   -0.51%
==========================================
  Files          31       31
  Lines        1405     1415      +10
==========================================
+ Hits         1287     1289       +2
- Misses        118      126       +8

Impacted Files
Coverage Δ

connect/resources/fulfillment_automation.py
37.5% <0%> (-2.8%)
:arrow_down:

connect/resources/tier_config_automation.py
90.47% <40%> (-6.83%)
:arrow_down:

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 a9031ba...2dccd38. Read the comment docs.

authors: JaviCerveraIngram codecov-io

repo: ingrammicro/connect-python-sdk


text:
how to use it with blog articles ?

Hi,
how to use it with blog articles ?
They do not appear in the sitemap.xml
what am i missing ?
thanks

Hi Chris,
Thanks for using our plugin.
Well, I guess you haven't configured the blog post page to be enabled in the sitemap. You'll probably want to set model to RainLab\Blog\Models\Post, scope to isPublished and param to something like slug:slug.
Just my guess but if you do so and the items still won't appear in the sitemap, let us know.
Cheers,
Tomasz

thank you very much for your clear reply.
it works for posts and categories as well.

authors: chrisvidal tomaszstrojny

repo: initbiz/seostorm-plugin


text:
Fix typeing of influxdb (#4689)

Pull request opened by the merge tool on behalf of #4689

Pull request rejected by merge tool. The tests for this branch did not succeed.

Merged into branches iso5 in 477afb50d9c34e674c204e90ec39a5688e128532

repo: inmanta/inmanta-core


text:
issue/4651-improve-log-pip

Description
The following information will be logged (in a separate logger inmanta.pip):

the pip command itself
the content of the requirements.txt file

closes #4651
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[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
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

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

@arnaudsjs I'm not sure I took your all your comments (correctly) into account. Is this what you had in mind about logging "at once with the command"?

Pull request rejected by merge tool. Multiple change entry files found (changelogs/unreleased/1190-bytecompile.yml,changelogs/unreleased/1291-irt-archive-mypy-stdout.yml,changelogs/unreleased/4277-partial-compile-doc.yml,changelogs/unreleased/4384-regular-timeouts-on-core-tests.yml,changelogs/unreleased/4398-fix-agent-restart-storm.yml,changelogs/unreleased/4398-improved-agent-manager-logging.yml,changelogs/unreleased/4401-resource-actions-join-table.yml,changelogs/unreleased/4402-resource-actions-joint-table.yml,changelogs/unreleased/4412-put-partial-dynamic-version-allocation.yml,changelogs/unreleased/4479-doc-test-db-migration-scripts.yml,changelogs/unreleased/4497-add-support-for-extras.yml,changelogs/unreleased/4500-improve-module-install-logging.yml,changelogs/unreleased/4589-convert-a-v1-module-to-a-v2-with-the-presence-of-a-setuppy-file.yml,changelogs/unreleased/4620-fix-log-project-install.yml,changelogs/unreleased/4636-dependabot.yml,changelogs/unreleased/4642-dependabot.yml,changelogs/unreleased/4643-dependabot.yml,changelogs/unreleased/4651-improve-pip-logging.yml,changelogs/unreleased/4652-dependabot.yml,changelogs/unreleased/4653-dependabot.yml,changelogs/unreleased/4674-dependabot.yml,changelogs/unreleased/4675-dependabot.yml,changelogs/unreleased/4684-keep-requirements-v1tov2.yml,changelogs/unreleased/4688-influxdb_metrics_are_typed_inconsistently.yml,changelogs/unreleased/4699-dependabot.yml,changelogs/unreleased/4708-dependabot.yml,changelogs/unreleased/4709-dependabot.yml,changelogs/unreleased/4713-venv-inheritance-no-pythonpath.yml,changelogs/unreleased/4714-fix-empty-string-VirtualEnv.yml,changelogs/unreleased/4715-dependabot.yml,changelogs/unreleased/4718-uninstall-inmanta-pkgs.yml,changelogs/unreleased/4722-fix-wait-condition-autostartedagentmgr.yml,changelogs/unreleased/4723-fix--override-pip-extra-index-url.yml,changelogs/unreleased/4730-dependabot.yml,changelogs/unreleased/4750-dependabot.yml,changelogs/unreleased/4754-dependabot.yml,changelogs/unreleased/4755-dependabot.yml,changelogs/unreleased/4761-venv-check-bis.yml,changelogs/unreleased/4761-venv-check.yml,changelogs/unreleased/4768-dependabot.yml,changelogs/unreleased/4781-compiler-service-doesnt-log-consistently-in-same-timezone.yml,changelogs/unreleased/4782-dependabot.yml,changelogs/unreleased/4789-dependabot.yml,changelogs/unreleased/4790-dependabot.yml,changelogs/unreleased/4795-fix-security-issue.yml,changelogs/unreleased/4796-dependabot.yml,changelogs/unreleased/4797-dependabot.yml,changelogs/unreleased/4803-compiler-service-notification.yml,changelogs/unreleased/4812-dependabot.yml,changelogs/unreleased/4831-dependabot.yml,changelogs/unreleased/4834-acquire-lock-on-correct-db-table.yml,changelogs/unreleased/4859-dependabot.yml,changelogs/unreleased/4861-dependabot.yml,changelogs/unreleased/bump-compiler-version-2022-4.yml,changelogs/unreleased/compiler-test-performance.yml,changelogs/unreleased/compilerloglevels.yml,changelogs/unreleased/convert-module-tag-build.yml,changelogs/unreleased/db-dump-tool-sql-extension.yml,changelogs/unreleased/db-enum-inconsistency.yml,changelogs/unreleased/ensure-reset-of-env-settings.yml,changelogs/unreleased/fix-bugs-in-merge-partial-compile.yml,changelogs/unreleased/fix-cleanup-editable-installs-in-test-suite.yml,changelogs/unreleased/fix-db-dump-rename.yml,changelogs/unreleased/fix-incorrect-assignment-modulev2metadata.yml,changelogs/unreleased/fix-race-in-test-autostart-mapping-update-uri.yml,changelogs/unreleased/fix-test-case-resource-ordering.yml,changelogs/unreleased/fix-test-case-test-compile-runner.yml,changelogs/unreleased/fix-test-case-warnings.yml,changelogs/unreleased/fix-tests-sys-meta-path.yml,changelogs/unreleased/fix-type-assignment.yml,changelogs/unreleased/improve-logs-query-performance.yml,changelogs/unreleased/improve-query-performance.yml,changelogs/unreleased/improved_warning_assertions.yml,changelogs/unreleased/pep660-increased-compatibility.yml,changelogs/unreleased/remove-model-exporter.yml,changelogs/unreleased/remove-test-warning.yml,changelogs/unreleased/scheduler_backward_compatibility.yml,changelogs/unreleased/set-git-askpass-env-var.yml,changelogs/unreleased/use-snippetcompiler-clean-fixture.yml). This may happen when a change entry was removed from the remote repository due to a reverted change. In that case, make sure the latest changes from origin/master are merged into issue/4651-improve-log-pip before triggering merge bot.

Processing this pull request

Merged into branches master in 255983bdc4a4985c38cb1f81c2ccc458736b6ba1

Processing #4930.

authors: FloLey inmantaci


text:
Build(deps): Bump react-router-dom from 6.2.1 to 6.2.2 (#2926)

Pull request opened by the merge tool on behalf of #2926

Merged in f41fc50c00469633d57b2f1382453bd33da79f34

repo: inmanta/web-console


text:
Build(deps-dev): Bump @typescript-eslint/eslint-plugin from 5.38.0 to 5.38.1 (#4105)

Pull request opened by the merge tool on behalf of #4105

Merged in 329be1b3117d1c2bc2e38028c208a7402bebff38


text:
Build(deps): Bump @patternfly/react-styles from 4.92.0 to 4.92.3 (#4461)

Pull request opened by the merge tool on behalf of #4461

Merged in a2e8a029bdffc5c4fc906f671c82254476674111


text:
Update IR3 channel

It is still the old electronic chain. The calibration must be updated.

Linearity need to be changed. Dark current should also be changed IF we have data. The new IR3 channel is called FM9. Check if gabriel has data on that.


text:
Add markdown support using jupytext

If we have a filetype that can be converted to a notebook using jupytext, by default allow that.
Also have a switch to disallow particular filetypes or disable jupyext parsing.

Fixed by https://github.com/innovationOUtside/nb_quality_profile/commit/56ca1619a15729a0bb6e908d78725d33ba579994


text:
[BE] Spring 포팅 - User

해당 사항 (중복 선택)

[x] FEAT : 새로운 기능 추가 및 개선
[x] FIX : 기존 기능 수정 및 정상 동작을 위한 간단한 추가, 수정사항
[ ] BUG : 버그 수정
[ ] REFACTOR : 결과의 변경 없이 코드의 구조를 재조정
[ ] TEST : 테스트 코드 추가
[ ] DOCS : 코드가 아닌 문서를 수정한 경우
[ ] REMOVE : 파일을 삭제하는 작업만 수행
[ ] RENAME : 파일 또는 폴더명을 수정하거나 위치(경로)를 변경
[ ] ETC : 이외에 다른 경우 - 어떠한 사항인지 작성해주세요.

설명

아래 링크에 이슈번호를 적어주세요. 예) .../42cabi/issues/738

https://github.com/innovationacademy-kr/42cabi/issues/1038

userController, AdminController 생성
JavaDoc 추가
테스트 코드 추가 (controller 테스트 제외)
UserCabinetPaginationDto 생성 -> 수정 필요해보이나 우선 구현

아직 완벽히 하진 못 했습니다만..
머지 한 번 하는 게 좋을 것 같아 PR 올립니다!

고생하셨습니다!


text:
cardano-node 1.34.1 compatibility

Is support for the latest node version on the horizon?

I have not tried it, but I am at least 90% sure it will JustWork (tm).

@Vardominator Did you try this? Can this ticket be closed?

I'm running with 1.34.1 and all appears fine from a node -> dbsync perspective

@Elitestakepool @erikd
I'm seeing the following on testnet:
SqlError {sqlState = "42P01", sqlExecStatus = FatalError, sqlErrorMsg = "relation \"block\" does not exist", sqlErrorDetail = "", sqlErrorHint = ""}

Using a snapshot seems to be working but let me track it for some time and make sure all is good

I'm trying a snapshot with a node that has not yet synced. I'm seeing the following:
[db-sync-node:Info:51] [2022-04-21 20:03:58.31 UTC] Cardano.Db tip is at slot 56030398, block 3488192
[db-sync-node:Info:56] [2022-04-21 20:03:58.31 UTC] Running DB thread
[db-sync-node:Info:56] [2022-04-21 20:03:58.36 UTC] Rolling back to genesis
[db-sync-node:Info:56] [2022-04-21 20:04:12.72 UTC] Deleting 3488192 blocks up to slot 56030398

Is this expected?

@erikd It appears to be stuck here forever:
[db-sync-node:Info:680] [2022-04-22 04:47:24.72 UTC] Cardano.Db tip is at slot 56030398, block 3488192
[db-sync-node:Info:685] [2022-04-22 04:47:24.72 UTC] Running DB thread
[db-sync-node:Info:685] [2022-04-22 04:47:24.72 UTC] Rolling back to slot 56088801, hash 2bc7a51571c5236ebef5f1a8b9b300ae9487f3610cd7c13cf14668675b9cb1e9
[db-sync-node:Info:685] [2022-04-22 04:47:24.73 UTC] Deleting 4331 blocks up to slot 56233504

DB sync has been in this state for over 40 minutes now. I'm using the latest snapshot.
Here the logs from postgres:
2022-04-22 05:58:06.600 UTC [100] ERROR:  relation "withdrawal_id_seq" already exists
2022-04-22 05:58:06.600 UTC [100] STATEMENT:  CREATE SEQUENCE public.withdrawal_id_seq
            START WITH 1
            INCREMENT BY 1
            NO MINVALUE
            NO MAXVALUE
            CACHE 1;

Seems to be stuck as well.
I really have no idea what I'm supposed to be doing here.

Yet another point of confusion:
[db-sync-node:Info:462] [2022-04-22 07:02:48.16 UTC] Starting chainSyncClient
[db-sync-node:Info:462] [2022-04-22 07:02:48.17 UTC] Cardano.Db tip is at slot 56241728, block 3494571
[db-sync-node:Info:467] [2022-04-22 07:02:48.17 UTC] Running DB thread
[db-sync-node:Info:467] [2022-04-22 07:02:48.18 UTC] Rolling back to slot 56088801, hash 2bc7a51571c5236ebef5f1a8b9b300ae9487f3610cd7c13cf14668675b9cb1e9
[db-sync-node:Info:467] [2022-04-22 07:02:48.18 UTC] Deleting 311 blocks up to slot 56098114
[db-sync-node.Subscription:Notice:46] [2022-04-22 07:02:48.18 UTC] Identity Required subscriptions started

Seems to be stuck here now with not much CPU activity.

i dont see this issue, I have DBSync 12.0.2 across both my servers running 1.34.1 node version and also restored snapshot from IOHK repo
dbsync1:~$ cardano-node version
cardano-node 1.34.1 - linux-x86_64 - ghc-8.10
git rev 73f9a746362695dc2cb63ba757fbcabb81733d23

dbsync1:~$ cardano-db-sync version
cardano-db-sync 12.0.2 - linux-x86_64 - ghc-8.10
git revision 935e1fe5d5d11d694e9b6c54030a592b85742671

dbsync1:~$ wget https://update-cardano-mainnet.iohk.io/cardano-db-sync/12/db-sync-snapshot-schema-12-block-7128371-x86_64.tgz
There is a new snapshot just uploaded from latest epoch boundary, this is the snapshot i used

Sorry that doesn't help me. The database is undergoing deadlock and I'm not sure why that's the case:
[db-sync-node.ErrorPolicy:Error:6] [2022-04-22 14:30:16.98 UTC] IP LocalAddress "/node-ipc/node.socket" ErrorPolicyUnhandledApplicationException (SqlError {sqlState = "40P01", sqlExecStatus = FatalError, sqlErrorMsg = "deadlock detected", sqlErrorDetail = "Process 65 waits for ShareLock on transaction 3676; blocked by process 122.\nProcess 122 waits for ShareLock on transaction 3675; blocked by process 65.", sqlErrorHint = "See server log for query details."})

This tool is so difficult to deploy and work with. I can't tell which errors I should pay attention to or which ones are expected. Why am I seeing duplicate key errors while restoring a snapshot?
psql:/tmp/db-sync-snapshot-zWgWJDFqNt/db-sync-snapshot-schema-12-block-3488192-x86_64.sql:50838904: ERROR:  could not create unique index "unique_withdrawal"
DETAIL:  Key (addr_id, tx_id)=(16967, 375910) is duplicated.
psql:/tmp/db-sync-snapshot-zWgWJDFqNt/db-sync-snapshot-schema-12-block-3488192-x86_64.sql:50838912: ERROR:  could not create unique index "withdrawal_pkey"
DETAIL:  Key (id)=(1046) is duplicated.

authors: Elitestakepool Vardominator erikd

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


text:
new typed-protocols for cardano-node

input-output-hk/ouroboros-network#3818 and input-output-hk/ouroboros-network#3675 must be merged first

Update dependencies: new version of typed-protocols.

Implements input-output-hk/cardano-node#4221

Closing this. Please re-open the PR when it is closer to being reviewed + merged

repo: input-output-hk/cardano-node


text:
[CSL-1727] Wallet acid cleanup worker

Needs to be refactored and reviewed a little bit

refactored, it's up to reviews now

I cherry-picked to the cardano-sl-1.0-exchanges branch and fixed ghc and hlint warnings. We should do the same fixes here and squash into one patch for the cardano-sl-1.0 branch.

@dcoutts i think i've already fixed hlint/warnings (an hour ago or so with forcepush).

i think i've already fixed hlint/warnings (an hour ago or so with forcepush).

Ah ok, sorry I didn't notice. Thanks.

@dcoutts can we merge this one? I've squashed commits.

This is now included in https://github.com/input-output-hk/cardano-sl/pull/1727

authors: Martoon-00 dcoutts volhovM

repo: input-output-hk/cardano-sl


text:
[CBR-167] Improve README in wallet-new

https://iohk.myjetbrains.com/youtrack/issue/CBR-167

Merging this one overriding CI by the virtue of the fact this touches only documentation stuff.

authors: adinapoli-iohk denisshevchenko


text:
🏛 [EPIC] : Create local signing key

Summary
Create local signing key
Description
Parent #727
When a user creates a new account, they do so by creating a new keychain. A 12-word seed phrase serves as the root for that keychain, from which everything else is derived. The first 'key' on the keychain is a master signing key, derived from the raw seed phrase.
When a user creates a new account or restores their account on a new device, the app needs to derive the master signing key from the seed phrase, and store it in a local vault. This local vault uses a device specific password to lock / unlock access.
GIVEN a new user in the 'get started' workflow
WHEN user click 'get your keychain now"
THEN generate new seed phrase AND show to user AND confirm user has right seed phrase
AND WHEN user enters / confirms "unlock password"
THEN derive master signing key from seed phrase AND encrypt with device password AND store in local vault
Children

[x] #811
[x] #812
[ ] #813
[x] #876

Questions:

what specific algorithm will be used for seed phrase generation? how will app interact with that algo?
need to force app to "forget" seed phrase after showing to user and deriving signing key?
at which point should key generation happen? at which point should it be encrypted?

All building blocks to submit the RBAC transaction are in place. In the future when key derivation algorithm will be specified the temporary key derivation from #876 will be replaced by #813

authors: dtscalac mike-mcnulty

repo: input-output-hk/catalyst-voices


text:
Chore/DAEF-496 Ada redemption tests in mainnnet mode

This PR modifies Ada redemption tests to run in mainnet mode, where Ada redemption warning is not shown.
All tests are now green when ran with NETWORK=mainnet npm run test

@darko-mijic this PR is ready to be merged. I did not do it myself as I was not sure if we are allowed to do so ;)

Thanks @nikolaglumac. We will merge this on Monday since it is not urgent and we are publishing a release over the weekend.

@darko-mijic what's the status on this PR? can be merged?

authors: DominikGuzei darko-mijic nikolaglumac

repo: input-output-hk/daedalus


text:
Chore/ddw 46 upgrade to react 16 (FORK)

IMPORTANT: please merge #709 first as this is based on it
NOTE: You have to test this PR against https://github.com/input-output-hk/react-polymorph/pull/41
This PR upgrades to React 16 and includes all necessary changes to make it work! (not many were needed).

Will review this as soon as https://github.com/input-output-hk/daedalus/pull/709 is fixed and merged.

Unfortunately there are some new problems with flow … this needs more work :(

@DominikGuzei can you please merge in latest develop in your branch? I will review this PR after you do that. Thanks!

authors: DominikGuzei nikolaglumac


text:
Introduce CardanoBlock

Plan:

[x] 1. Initially CardanoBlock = ShelleyBlock
[x] 2. DegenFork ShelleyBlock (depends on #2075)
[x] 3. HardForkBlock '[ByronBlock, ShelleyBlock] (depends on #2074, #2078, verify that it can sync against mainnet).

We also need a Protocol constructor for CardanoBlock, and make sure the cardano-node can run with it.
UPDATE: replaced ByronBlock with ShelleyBlock in steps 1 and 2, see #2075 for why.

Addressed by #2147.

authors: edsko mrBliss

repo: input-output-hk/ouroboros-network


text:
plutus-book: skeleton

This adds a skeleton for the Plutus Book, with a spine file and
a demo chapter, as well as the Nix build and some instructions.
The Nix build creates the HTML, PDF, and EPUB version. We can
also do Kindle, but kindlegen has an unfree license, and I should
check that's okay.

Added an example of using literate haskell and the infrastructure to build it.

repo: input-output-hk/plutus


text:
marking MAlonzo.* as autogen-modules; restoringmetatheory to cabal.project

With metatheory listed as a package in cabal.project
$ cabal v2-install language-plutus-core

gives this error message:
...
cabal: Error: Could not find module: MAlonzo.Code.Main with any suffix:
["gc","chs","hsc","x","y","ly","cpphs","hs","lhs","hsig","lhsig"]. If the
module is autogenerated it should be added to 'autogen-modules'.

The modules MAlonzo.* are autogenerated. I tried moving them from other-modules to autogen-modules in metatheory/plc-agda.cabal as suggested by the error message. It seems to work for me.

ok, this is not going as well as I had hoped...

I am able to run tests and build  and run plc-agda using:
$ cd metatheory
$ agda --compile --ghc-dont-call-ghc Main.lagda
$ cd ..
$ cabal v2-build metatheory
$ cabal v2-test metatheory
$ cd metatheory
$ cabal v2-run plc-agda -- --help

cabal v2-install metatheory doesn't work anymore as it doesn't include the generated MAlonzo.* modules in the sdist:
$ cabal v2-sdist metatheory -l
metatheory/LICENSE
metatheory/Main.hs
metatheory/NOTICE
metatheory/Opts.hs
metatheory/README.md
metatheory/Raw.hs
metatheory/Scoped.hs
metatheory/TestDetailed.hs
metatheory/TestSimple.hs
metatheory/plc-agda.cabal

But, I guess this isn't crucial and I am not sure whether the Agda code or the generated Haskell should really be included in a hypothetical standalone package.

Yes, the sdist is a source distribution, so shouldn't include autogenerated files. Those should be created by the setup. But as discussed we don't really want to spend lots of time writing a custom setup to do the Agda extraction... Also, sdist really doesn't matter for plc-agda as I doubt it's ever going on Hackage.

sdist does matter for v2-install though, which is annoying but manageable.  I will make an issue for making a custom setup/to record that you can't v2-install metatheory and mark it as low priority.

authors: jmchapman michaelpj


text:
Configuration UI shows invalid agent summary when "combine services" is used

Since version 2.0.2, the configuration UI is able to group agents in the agent status view, which use the same service name. When using this feature, the agent summary (how many agents exist and are shown) shows invalid data.

Would this be the expected behaviour?

authors: Napfschnecke mariusoe

repo: inspectIT/inspectit-ocelot


text:
Allow typing only year

Signed-off-by: Tomasz tomaszgy@gmail.com

Merged

authors: jmartinm tomaszgy

repo: inspirehep/bootstrap-datetimepicker


text:
When creating a service, after selecting a image, there are some images that click No reaction after clicking Next [REPLACEMENT ISSUE]

The original issue
Id: 761
Title: When creating a service, after selecting a image, there are some images that click No reaction after clicking Next

could not be created.
This is a dummy issue, replacing the original one. It contains everything but the original issue description. In case the gitlab repository is still existing, visit the following link to show the original issue:
TODO

In GitLab by @yhua123 on Nov 8, 2019, 07:43
system need filter image without "/" (no project name).

In GitLab by @sokril on Nov 8, 2019, 07:43
the image has filtered，fixed with pr#763

In GitLab by @cuiaq123 on Nov 8, 2019, 07:43
fixed

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

In GitLab by @sokril on Nov 8, 2019, 08:16
assigned to @cuiaq123

repo: inspursoft/board


text:
add a build image method with upload image package. - [closed]

In GitLab by @liyanq528 on Dec 19, 2018, 08:16
Merges 20181006 -> dev

In GitLab by @wknet123 on Nov 13, 2019, 11:34
closed


text:
node swagger api  name  should not be required

In GitLab by @luotian-github on Aug 23, 2017, 16:36
the note of swagger-prepare sh is wrong

In GitLab by @Robin-Mao on Nov 8, 2019, 07:35
api /v1/dashboard/node/ parameter node_name should not be required in swagger.yaml

In GitLab by @luotian-github on Nov 8, 2019, 07:35
#239

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

In GitLab by @sokril on Nov 8, 2019, 08:08
assigned to @luotian-github


text:
Dashboard and grafana pod and service number is wrong

In GitLab by @wknet123 on Mar 14, 2018, 11:30

In GitLab by @luotian-github on Nov 8, 2019, 07:46
sometimes more, sometimes less

In GitLab by @luotian-github on Nov 8, 2019, 07:46
database sevice list 20
dashboard service 18

In GitLab by @tmon546596046 on Nov 8, 2019, 07:46
now the pod/container in grafana show total count no matter running or not.

In GitLab by @tmon546596046 on Nov 8, 2019, 07:46
board dashboard only show pods which must belong to one service

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

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


text:
Handling external deletion of the resources in the clusterresources group

Issue 572
Added:

handling of the external deletion of the resources on Instaclustr
fixed external changes for VPC peering resources when Instaclustr API returns a list of subnets in a different order

closes #572
Want a bit of help
I want to hear your opinion about the added state field which indicates the state of the resource on Instaclustr. Maybe changing it to something like instaclustrResourceState will be better. Because some resources also have their status codes like AWS VPC peering. So it looks a bit weird when there is the following status:
status:
  state: CREATED
  statusCode: deleted

The field state indicates that the resource is created on Instaclustr, but statusCode: deleted indicates that the VPC peering is deleted on AWS.
So, what do you think?

I agree with your statment, we should rename "state" to "instaclustrResourceState"

I want to hear your opinion about the added state field which indicates the state of the resource on Instaclustr. Maybe changing it to something like instaclustrResourceState will be better.

The source of truth is the Instaclustr Console. So whatever the state/status of the Instaclustr resource is, it should be directly reflected on the k8s state field without any deviation. For now, I don't see a good reason to create a new field or give a new name to the existing state field of the resource.

Because some resources also have their status codes like AWS VPC peering. So it looks a bit weird when there is the following status:
status:
  state: CREATED
  statusCode: deleted

The field state indicates that the resource is created on Instaclustr, but statusCode: deleted indicates that the VPC peering is deleted on AWS.

In this example, I suggest you maintain consistency between the state and statusCode fields, or, even better, you can consider using only the state field to represent the statusCode.

authors: OleksiienkoMykyta ribaraka worryg0d

repo: instaclustr/operator