text:
Error when installing DBeaver plugin in eclipse.

Description
When installing DBeaver plugin via "Install New Software" in eclipse I receive this error:
Cannot complete the install because one or more required items could not be found.
Software being installed: DBeaver IDE 23.3.3.202401110022 (org.jkiss.dbeaver.ide.feature.feature.group 23.3.3.202401110022)
Missing requirement: DBeaver PostgreSQL UI 1.0.99.202401110022 (org.jkiss.dbeaver.ext.postgresql.ui 1.0.99.202401110022) requires 'osgi.bundle; org.eclipse.gef 0.0.0' but it could not be found
Cannot satisfy dependency:
From: DBeaver Databases UI 1.0.114.202401110022 (org.jkiss.dbeaver.db.ui.feature.feature.group 1.0.114.202401110022)
To: org.eclipse.equinox.p2.iu; org.jkiss.dbeaver.ext.postgresql.ui [1.0.99.202401110022,1.0.99.202401110022]
Cannot satisfy dependency:
From: DBeaver IDE 23.3.3.202401110022 (org.jkiss.dbeaver.ide.feature.feature.group 23.3.3.202401110022)
To: org.eclipse.equinox.p2.iu; org.jkiss.dbeaver.db.ui.feature.feature.group [1.0.114.202401110022,1.0.114.202401110022]
DBeaver Version
Community Edition 23.3.202401110022
Operating System
Both
Linux Redhat
Windows 10
Database and driver
No response
Steps to reproduce
Clean install of Eclipse 2023-09 and after that installation of dBeaver into it.

Downloaded the jar files from this update site: https://dbeaver.io/files/ea/update/ce/ into a local folder.
In Eclipse, Install New Software > Add > Archive > folder > content.jar

Additional context
I have to download all the necessary jars/files and install them in an offline environment in eclipse.

Hi, DBeaver requires GEF plugin to be installed, it can be installed using following p2 repository
https://download.eclipse.org/tools/gef/classic/release/3.18.0

Thanks, now it's saying
Cannot complete the install because one or more required items could not be found.   Software being installed: GEF Classic Zest Examples 3.15.200.202311222042 (org.eclipse.zest.examples 3.15.200.202311222042)   Missing requirement: GEF Classic Zest Examples 3.15.200.202311222042 (org.eclipse.zest.examples 3.15.200.202311222042) requires 'osgi.bundle; org.eclipse.pde 0.0.0' but it could not be found

@BrandonBlackwell Zest examples can be excluded.

I exclude Zest examples and it gives me this:
An error occurred while collecting items to be installed session context was:(profile=_home_entds.ngisn.com_4n36571_eclipse_java-2023-09_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.draw2d_3.14.100.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.draw2d_3.14.100.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.draw2d_3.18.0.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.draw2d_3.18.0.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.draw2d.source_3.14.100.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.draw2d.source_3.14.100.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.draw2d.source_3.18.0.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.draw2d.source_3.18.0.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef_3.16.0.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef_3.16.0.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.doc.isv_3.13.300.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.doc.isv_3.13.300.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef.examples_3.18.0.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef.examples_3.18.0.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.flow_3.15.100.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.flow_3.15.100.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.flow.source_3.15.100.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.flow.source_3.15.100.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.logic_3.14.200.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.logic_3.14.200.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.logic.source_3.14.200.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.logic.source_3.14.200.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.shapes_3.14.100.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.shapes_3.14.100.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.shapes.source_3.14.100.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.shapes.source_3.14.100.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef.examples.source_3.18.0.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef.examples.source_3.18.0.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.text_3.14.100.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.text_3.14.100.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.text.source_3.14.100.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.examples.text.source_3.14.100.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef_3.18.0.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef_3.18.0.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef.sdk_3.18.0.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef.sdk_3.18.0.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.source_3.16.0.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/plugins/org.eclipse.gef.source_3.16.0.202311222042.jar Artifact not found: jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef.source_3.18.0.202311222042.jar. jar:file:/home/entds.ngisn.com/4n36571/Downloads/GEF-Updates-3.18.0.zip!/features/org.eclipse.gef.source_3.18.0.202311222042.jar

I excluded Zest Examples and Draw2D Features. Now I'm recieving this:
An error occurred while collecting items to be installed session context was:(profile=_home_..._eclipse_java-2023-09_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No artifact repository available. noArtifactRepositoriesAvailable

Any update on this?

UPDATE:
I was able to install via dropins folder. The jars from Dbeaver and Eclipse GEF features folder need to be in the same folder as well as plugin jars, from both, in plugins folder.

authors: BrandonBlackwell Destrolaric


text:
A query containing dollar-quoted format string causes SQL editor to run other commands unintentionally (Postgres)

Discussed in https://github.com/orgs/dbeaver/discussions/22543

Originally posted by philosaur December 28, 2023
Description
Running a query (Execute SQL query) that contains a dollar-quoted format string causes DBeaver to run that query as well as all subsequent queries in the same editor--as if "Execute SQL script" had been run instead.
My last version of DBeaver was from probably 6 moths ago, and this behavior began when I upgraded to the Christmas Day version.
DBeaver Version
Community Edition, vers. 23.3.1.202312241705
Operating System
Windows 10
Database and driver
Postgres, (PostgreSQL JDBC Driver)
Steps to reproduce

Click "Execute SQL Script" or press F5 (by default) with this SQL:

SELECT format($$%1$s$$, 'foo');

SELECT 'bar';

SELECT 'baz1';

SELECT 'baz2';

SELECT 'baz3';

DBeaver produce five separate output tabs with output from each respective command, instead of running just the first command.
Switching the dollar quotes to single quotes causes it to only run the first query, as expected.

This is still an issue in Version 24.0.4.202405051837 (released on May 6 2024).

As a temporary workaround this can be fixed by changing the connection setting to read $$...$$ as string

I seem to be getting a similar error again in 24.1.3. Coworkers using 24.1.2 don't seem to be getting the error when running the exact same script that I am:

I seem to be getting a somewhat related error again in 24.1.3. Coworkers using 24.1.2 don't seem to be getting the error when running the exact same script that I am:

I did try the Show $$ quote as: String just in case, but wasn't able to get it to work.
A workaround that does work for me is as suggested above to highlight the entire script and then Execute SQL query.

@torikamal could you provide some minimal example of the query? And what database do you use? For now, I can't reproduce the issue.

Hi @E1izabeth, I have added a zipped SQL file, an image of my SQL Processing settings, and some additional information.
Thank you!

@torikamal thank you

source: gharchive/issue

repo: dbeaver/dbeaver

license_type: permissive

license_source: github-api


text:
SQL Server: use MS driver 8.2.0 by default

We need to upgrade from old 7.4 driver

verified

authors: serge-rider uslss


text:
#21086 avoid NPE in the SQL Editor

Maybe toolItem != null is better, but I'm not sure

Verified

source: gharchive/pull-request


text:
Character Stats Screen Is Missing Wanderer Title

On the main menu, Statistics -> Character Stats -> Scroll down to specific character statistics. The CULL and the base characters have "titles" for their sections of stats, but Wanderer does not.

never mind, its showing up now?

repo: dbjorge/jorbs-spire-mod

license: MIT


text:
yolact++ eval error

i have install DCN success

cuda 9

@dbolya

Did you solve this?

repo: dbolya/yolact


text:
fix: check for database in _get_one_catalog (#247)

Description

Resolves #247.
The adapter method _get_one_catalog didn't account for the schema database when it was passed in the schema.yml file. Now if catalog_id is not awsdatacatalog, _get_one_catalog will get the catalog_id/database from the information_schema.
Models used to test - Optional

Checklist

[x] You followed contributing section
[x] You kept your Pull Request small and focused on a single feature or bug fix.
[x] You added unit testing when necessary
[ ] You added functional testing when necessary

LGTM. To my understanding the InformationSchema is a dict of database and their matching schemas ?

It does hold the database info, but I'm not sure if it has the matching schemas info. This class AthenaSchemaSearchMap holds both the InformationSchema and the respective schemas and relations. The _get_catalog_schemas returns an AthenaSchemaSearchMap object and both its key and value are passed to the _get_one_catalog here. Hope that's not too confusing.

It makes total sense ! Thanks for the contribution 🔥

authors: Jrmyy maiarareinaldo

repo: dbt-athena/dbt-athena


text:
1.5.0rc1 changelog

Description
Create 1.5.0rc1 changelog
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[ ] I have run changie new to create a changelog entry

I'm assuming we don't have to be too concerned about the lack of adapter tests running on this

authors: VersusFacit mikealfare

repo: dbt-labs/dbt-bigquery


text:
[CT-377] dbt_project enhancement

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
As per the documentation while this works:
$ dbt run --profiles-dir path/to/directory

and so does
$ export DBT_PROFILES_DIR=path/to/directory

I would prefer to set it in dbt_project.yml and forget about it.
[profiles-path]: directorypath

Describe alternatives you've considered
.env file in repo
Who will this benefit?
cli users
Are you interested in contributing this feature?
yes
Anything else?
No response

Hi @dbrtly and thanks for the feature request!  I'll add this as a backlog ticket and we'll get it prioritized as soon as it makes sense.  In the interim, I've generally recommended .env files for these sorts of use cases in the past.

removing stale and clearing assignee, this sounds useful. perhaps we can pick this up for 1.4?

Sounds a lot like the changes we made to support target-path and log-path (https://github.com/dbt-labs/dbt-core/pull/5402). For consistency with those and other "global"/runtime configs, the precedence order would want to be:

CLI flag: --profiles-dir
Env var: DBT_PROFILES_DIR
Project config: profiles-dir: in dbt_project.yml

This is also related to @dbeatty10's proposed change, to look for profiles.yml in IF a custom --profiles-dir is not set (https://github.com/dbt-labs/dbt-core/issues/5411, https://github.com/dbt-labs/dbt-core/pull/5717). Taking that into account, the updated precedence order would actually look like:

--profiles-dir command-line argument
DBT_PROFILES_DIR environment variable
profiles-dir property of dbt_project.yml NEW
current working directory of dbt_project.yml NEW
HOME directory of the user (i.e. ~/.dbt/)

:) yes please
Thanks,
Daniel

From: Jeremy Cohen @.>
Sent: Friday, September 16, 2022 8:27:13 PM
To: dbt-labs/dbt-core @.>
Cc: Daniel Bartley @.>; Mention @.>
Subject: Re: [dbt-labs/dbt-core] [CT-377] dbt_project enhancement (Issue #4885)
Sounds a lot like the changes we made to support target-path and log-path (#5402https://github.com/dbt-labs/dbt-core/pull/5402). For consistency with those and other "global"/runtime configs, the precedence order would want to be:

CLI flag: --profiles-dir
Env var: DBT_PROFILES_DIR
Project config: profiles-dir: in dbt_project.yml

This is also related to @dbeatty10https://github.com/dbeatty10's proposed change, to look for profiles.yml in IF a custom --profiles-dir is not set (#5411https://github.com/dbt-labs/dbt-core/issues/5411, #5717https://github.com/dbt-labs/dbt-core/pull/5717). Taking that into account, the updated precedence order would actually look like:

--profiles-dir command-line argument
DBT_PROFILES_DIR environment variable
profiles-dir property of dbt_project.yml NEW
current working directory of dbt_project.yml NEW
HOME directory of the user (i.e. ~/.dbt/)

—
Reply to this email directly, view it on GitHubhttps://github.com/dbt-labs/dbt-core/issues/4885#issuecomment-1249199202, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADLXPTOZIJF4OWF27LDIAEDV6RDQDANCNFSM5Q5NL42Q.
You are receiving this because you were mentioned.Message ID: @.***>

Update: I realized that this might be very tricky because of the order in which dbt parses each config at run initialization. I think we need to read and locate profiles.yml first, in order to set UserConfig, before we start reading dbt_project.yml. In which case, this could be much trickier to implement.
We have been discussing moving UserConfig out of profiles.yml and into a dedicated .env / config file, which would also make sense.

Agreed that the implementation would be quite involved!
Oooh, I like the idea of separating the current profiles.yml file into separate configuration files 🤩:

user configuration

config key in current profiles.yml
maybe named something like user_config.yml

connection configuration

<profile-name> keys in current profiles.yml
probably still named profiles.yml

@dbrtly how would you imagine using the proposed profiles-dir property of dbt_project.yml?
Are you aiming to specify the user configuration for the dbt project? Or the database connection configuration? Or both?
If you have multiple dbt projects, would you intend to point them all at a single shared profiles.yml file? Or would you point each of them at their own unique profiles.yml files (one per dbt project)?
If each project would have its own profiles.yml file, where would you put it? In the same directory as dbt_project.yml?

My initial beef was annoyance at setting $DBT_PROFILES_DIR over and over. These days, I’m also using direnv to run gcloud auth login … so direnv is doing more than one thing.
If dbt looked for profiles.yml in the same directory as the dbt_project.yml file, I would be happy with that.
If you are going to change this, my perspective is that there should be an option to use a pyproject.toml file for compatibility with the wider modern Python ecosystem.
Something like:
[tools.dbt.config]
# https://docs.getdbt.com/reference/global-configs

send_anonymous_usage_stats = False
use_colors = True
partial_parse = False
printer_width = 90
write_json = True
warn_error_include= all
log_format = json
debug = False
version_check = False
fail_fast = False
use_experimental_parser = False
static_parser = False

[tools.dbt.targets.dev]
# https://docs.getdbt.com/reference/warehouse-setups/bigquery-setup

type = bigquery
method = oauth
location = “US” # Optional, one of US or EU, or a regional location
# project = use $GOOGLE_PROJECT_ID
# actively discourage hardcoded secret in config

Github Actions treats Google project ID as a secret. It never prints it to the logs (always uses a dummy string). I find it a code smell that dbt encourages users to handle the ID with less care.

Commenting to add my support for using the pyproject.toml file for project configuration 🚀
Like @dbrtly mentioned, the pyproject.toml file is becoming the standard way to configure project settings in the Python ecosystem
I'm less opinioned on how much stuff to put into pyproject.toml compared to dbt_project.yml, but at the very minimum I would love to be able to specify the project_dir and profiles_dir so that I can avoid setting $DBT_PROFILES_DIR and $DBT_PROFILES_DIR each time I want to run dbt (same gripe as dbrtly!)
Relating this to the precedence order mentioned before, I'd tweak item 3 to the pyproject.toml file:

--profiles-dir command-line argument
DBT_PROFILES_DIR environment variable
profiles_dir property of pyproject.toml <- NEW
current working directory of dbt_project.yml
HOME directory of the user (i.e. ~/.dbt/)

(I think 4 has changed recently to just the current working directory, which is also more intuitive)
This is already supported by the SQLFluff package's dbt-templater plugin:
[sqlfluff:templater:dbt]
project_dir = <relative or absolute path to dbt_project directory>
profiles_dir = <relative or absolute path to the directory that contains the profiles.yml file>
profile = <dbt profile>
target = <dbt target>

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

Commenting to keep this alive

Labeling this as triage for us to choose between one of the following approaches for this request:

Support a pyproject.toml file to read dbt project config
Add a profiles-dir property to dbt_project.yml
Status quo / do nothing

Encourage using an .env or .envrc (direnv) file with DBT_PROFILES_DIR specified

Currently, the parent directory for profiles.yml is determined using the following precedence [1]:

--profiles-dir CLI flag
DBT_PROFILES_DIR environment variable
current working directory (conventional file location 1)
~/.dbt/ directory (conventional file location 2)

@jtcohen6 and I got a chance to discuss this briefly today. We decided a couple things:

Our location for specifying dbt configuration is dbt_project.yml, so we're not planning to add an additional file format (i.e., pyproject.toml)
Given that we already have a CLI flag, environment variable, and two conventional file locations, it's not a priority for us to add profiles-dir property to dbt_project.yml

So I'm closing this issue as "not planned".

authors: Bilbottom dbeatty10 dbrtly iknox-fa jtcohen6 lostmygithubaccount

repo: dbt-labs/dbt-core


text:
[Feature] Be able to --favor-state for sources

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
See "Anything else" below.
It seems like there should be a way for --favor-state to utilize sources in addition to models, possibly via a --include-sources flag. To preserve current behavior, it would an opt-in with a default of false.
Alternatively, we could consider the current behavior a bug and make it opt-opt with a default of true. Or just skip creating a new flag and just change the behavior to include sources when --favor-state is included.
The decision above could apply to --state as well.
Describe alternatives you've considered
No response
Who will this benefit?
I tried out using --defer --favor-state --state while replying to https://github.com/dbt-labs/dbt-core/issues/9550#issuecomment-1950970298, and I discovered that it didn't apply to sources.
Are you interested in contributing this feature?
No response
Anything else?
models/_sources.yml
sources:
  - name: my_source
    database: db
    schema: "{{ target.schema }}"
    tables:
      - name: source_x

models/model_j.sql
-- model_j: {{ this }}
-- depends on:
--   nothing

select 1 as id

models/model_k.sql
-- model_k: {{ this }}
-- depends on:
--   model_a: {{ ref("model_j") }}
--   source_x: {{ source("my_source", "source_x") }}

select 1 as id

Assuming I have targets named dev and prod and I run the following:
dbt compile --target prod --target-path prod-run-artifacts
dbt compile --select model_k  --defer --favor-state --state prod-run-artifacts --target dev

I'd expect to get this:
-- model_k: "db"."feature_2"."model_k"
-- depends on:
--   model_a: "db"."prod"."model_j"
--   source_x: "db"."prod"."source_x"

select 1 as id

But I actually get this:
-- model_k: "db"."feature_2"."model_k"
-- depends on:
--   model_a: "db"."prod"."model_j"
--   source_x: "db"."feature_2"."source_x"

select 1 as id

@graciegoheen and I discussed this last week, and we were wondering:

How does --favor-state currently treat each of the non-model resource types that can be referenced (snapshots, seeds, and sources)?

Answer
Seeds and snapshots both utilize the state that is favored -- only snapshots do not.
My opinion
I think there should be a way for snapshots to also favor the state that was given (either as the default behavior or via an opt-in flag).
Reprex
This model gives us a peek at each of these:
models/model_k.sql
-- model_k: {{ this }}
-- depends on:
--   model_a: {{ ref("model_j") }}
--   seed_x: {{ ref("seed_x") }}
--   snapshot_x: {{ ref("snapshot_x") }}
--   source_x: {{ source("my_source", "source_x") }}

select 1 as id

Create some state and then favor it:
dbt compile --target prod --target-path prod-run-artifacts
dbt compile --select model_k  --defer --favor-state --state prod-run-artifacts --target dev

Output:
-- model_k: "db"."feature_456"."model_k"
-- depends on:
--   model_a: "db"."prod"."model_j"
--   seed_x: "db"."prod"."seed_x"
--   snapshot_x: "db"."prod"."snapshot_x"
--   source_x: "db"."feature_456"."source_x"

select 1 as id

So seeds and snapshots both utilize the state that is favored -- only snapshots do not.

Backstory
From convo with @jtcohen6:
Currently, deferral only works on non-ephemeral, "refable" nodes. This does not include the source node type at this time:

Node
Exists in database
Refable
Supports model versions

Source
✅
❌
❌

Seed
✅
✅
❌

Snapshot - timestamp
✅
✅
❌

Snapshot - check
✅
✅
❌

Model - incremental - append
✅
✅
✅

Model - incremental - delete+insert
✅
✅
✅

Model - incremental - merge
✅
✅
✅

Model - incremental - insert_overwrite
✅
✅
✅

Model - incremental - custom strategy
✅
✅
✅

Model - table
✅
✅
✅

Model - materialized view
✅
✅
✅

Model - view
✅
✅
✅

Model - ephemeral
❌
❌
✅

Analysis
❌
❌
❌

New behavior
Creating a definition of "deferable" that includes "refable" + sources would feel like more consistent behavior. Alternatively, we could consider adding sources to the refable list directly as long as we fully understand and accept those implications.
We wouldn't want jump all the way to use "exists in database" as the criteria because exported saved queries and results of data tests can both also exist in the database, but not in a way that can be referenced in the dbt DAG.
Opt-in
If there any way this behavior change could either be "breaking" or an unpleasant surprise for someone's workflow, we'd  want to utilize an opt-in mechanism for this behavior.

Is this related https://github.com/dbt-labs/dbt-core/issues/8727?

Is this related #8727?

I haven't looked at the implementation of state:modified / state:new to determine one way or the other.

@katieclaiborne-duet ran into this with a unit test during a slim CI build. The model being unit tested relies upon a source table that contains environment-aware logic similar to the code example in this issue.


text:
Ensure meta is both at node top level and in node.config. Fix snapshots with schema config.

resolves #4459, #4693
Description
This fixes a bug in schema file config processing, where an empty meta overwrote the root level meta. It also fixes a bug in snapshot schema config handling, where the snapshot SQL file config was lost.
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change

Thrilled that these look like quick fixes! Two quick meta notes (hah):

I'm going to remove myself from review — feel free to tag me back if there are questions about the original bugs, or anything specific you want me to look at
After merging, I would like to see us backport these fixes to 1.0.latest for inclusion in 1.0.3rc1. These aren't net-new bugs in v1.0 exactly, but it seems likely that they were net-new in v0.21, so folks will encounter them as part of their larger v1.0 upgrades. This will allow us to tell the Metadata team, with confidence, that meta fields are reliable for all v1.0+ versions of dbt.


text:
Fix recency test to work properly with day datepart

resolves #414
This is a:

[ ] documentation update
[x] bug fix with no breaking changes
[] new functionality
[ ] a breaking change

All pull requests from community contributors should target the main branch (default).
Description & motivation

When datepart is day or greater, the recency test should compare against the current date instead of current timestamp
The test wasn't working with timestamp columns in BigQuery before (since you can't compare a timestamp with datetime). This PR fixes that by converting timestamp to datetime first.
Note: this PR was done in collaboration with @rodrigoaps

Checklist

[x] This code is associated with an Issue which has been triaged and accepted for development.
[ ] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[x] BigQuery
[ ] Postgres
[ ] Redshift
[ ] Snowflake

[x] I followed guidelines to ensure that my changes will work on "non-core" adapters by:

[x] dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
[x] using the limit_zero() macro in place of the literal string: limit 0
[ ] using dbt.type_* macros instead of explicit datatypes (e.g. dbt.type_timestamp() instead of TIMESTAMP

[ ] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)
[x] I have added an entry to CHANGELOG.md

This is looking great @yuanminglee! A couple of comments and potential changes, let me know what you think!
I'm aiming to cut the release candidate for 1.0 at the start of next week, so please also let me know if you won't be able to get to this before then.

Thanks @joellabes! I've made the suggested change, and removed the unused line 😃

Closing in favour of #731 - sorry for all the hassle @yuanminglee!

authors: joellabes yuanminglee

repo: dbt-labs/dbt-utils


text:
Period Over Period Cast To Float

Description
Once again, the most confusing and asinine aspect of PostgreSQL strikes again - if you do simple division, it returns as an integer instead of a float or floating numeric.
Example:

Solution
In the period_over_period secondary calculation, we need to cast to float for Postgres and Redshift as they both exhibit this known behavior.

Resolution was moving the cast( as float) to the numerator instead of the full division in default__metric_comparison_strategy_ratio.
cast(coalesce({{ metric_name }}, 0) as {{ dbt_utils.type_float() }}) / nullif({{ calc_sql }}, 0)

Will go out with next PR.

Starting with Core 1.2, you can use type_float from the global namespace:
cast(coalesce({{ metric_name }}, 0) as {{ type_float() }}) / nullif({{ calc_sql }}, 0)

An alternative is giving it an explicit namespace:
cast(coalesce({{ metric_name }}, 0) as {{ dbt.type_float() }}) / nullif({{ calc_sql }}, 0)

I prefer the former.
I'd recommend making the change sooner rather than later, because the 1.0 release of dbt_utils intends to drop type_float altogether.
Side note: not currently on the roadmap, but I'm attracted to dbt Core containing cross-database casting macros like cast_as_float and safe_cast_as_float.


text:
Update metadata-querying.md

Description & motivation
Single tenant deployments do not have access to the metadata API.
Pre-release docs
Is this change related to an unreleased version of dbt?

[ ] Yes: please

update the base branch to next
add Changelog components: <Changelog>[New/Changed] in v0.x.0</Changelog>
add links to the "New and changed documentation" section of the latest Migration Guide

[x] No: please ensure the base branch is current
[ ] Unsure: we'll let you know!

hey @jeremyyeo thanks for opening this up and apologies for the delay here. since this is still an active clarification that applies and this pr has merge conflicts, do you mind opening up a new pr by editing this page [here](https://docs.getdbt.com/docs/dbt-cloud-apis/metadata-querying) to bypass it? i can open up the pr for you too, but i also would prefer you get the contribution credit too!
I've suggested the below tweaks from your original pr:

In order to query the dbt Metadata API, you’ll need to meet the following:

Have a Team or Enterprise dbt Cloud  account
Have a multi-tenant dbt Cloud account

Note: The Metadata API is currently not available to accounts on Single Tenant deployments.


text:
model query and auto-exposures beta

this pr adds model query history and auto exposures (beta) to the doca site for the broader beta cycle.
docs project
[ ] PM review required
[ ] Docs review optional since beta

thank you soo much @nataliefiann !

ok so it looks like we’re waiting on two things:
clarification on tableau server + allowlisting IP addresses from @reubenmc

@cafzal 's ok and approval too

i do think there’s a benefit in having a callout to all the docs saying this is available in beta for limited users and then rolling out. that way we make it clear for users that it’ll get rolled out soon and will hopefully address users questions without them needing to reach out to support. i’ve added it as a sugg and if eeryone is ok, can someone from the docs team commit them? :ty:

Approved


text:
Clarify that advanced CI is enterprise and MT/MC

Update the callout on the advanced CI page to say that it's available on enterprise plans, and not available for ST customers yet

hey @reubenmc , just confirming if advanced ci is avail for enterprise MT and not ST? i double check pb and it seems like it's not yet rolled out to ST yet?

Hey @joellabes , Reuben has confirmed that advanced ci is GA and available to all mt and st. Am I ok closing this pr out?

Yes this is obsolete now!


text:
Switch to non-polymorphic variant ?

@yminsky makes the point that it makes the type a little bit easier to use (avoid subtyping and problems due to polyvar inference).
The loss would be a tighter coupling between clients and this module. But if we can get this line
type ('a, 'b) result = Ok of 'a | Error of 'b

in Pervasives, the point becomes moot.

Are there any proposals to add result to Pervasives?

Not yet. We were discussing this with @yminsky.

There is now.
https://github.com/ocaml/ocaml/pull/147

authors: dbuenzli rgrinberg yminsky

repo: dbuenzli/result

license: ISC


text:
pull nginx tutorial

per @gabrielhartmann this is broken

@gabrielhartmann - what was the issue? I just updated the Universe package for nginx, so wondering if I broke it!

@ssk2 The issue is that you can't see the nginx instance from outside the cluster.  You can't see it either through admin router or through the public IP.

Okay, I'll look into that - and will fix this tutorial. (We should try to fix the underlying issues instead of removing docs!)

@ssk2 the docs should be removed until it is fixed though. it reflects poorly on us. as soon as the code is fixed, let's push the doc back out.

@gabrielhartmann That's not true, I just ran through all the tutorial steps and it worked for me as it's documented in the tutorial. You can access nginx after you install it via <dcos-hostname>/service/nginx URL. I wonder how you are trying to access the cluster.
Also, you need to remember the it takes a while before adminrouter starts routing stuff to NGINX due to the delay caused by mesos-dns.
cc: @ssk2 @joel-hamill @pyronicide

Should we revert this PR?

Did somebody tried and confirmed that the tutorial didn't work, before reverting it ?

@mohitsoni @gabrielhartmann i have not. one thought is, which version of DC/OS are you trying? Remember that DC/OS 1.7 is EA, DC/OS 1.6 is GA. The docs on docs.mesosphere are 1.6 GA, docs.io are 1.7 EA.

authors: gabrielhartmann joel-hamill mohitsoni ssk2

repo: dcos/dcos-docs


text:
1.14.0 Added Mesos patch to address SSL certificate validation issues.

We noticed that recent TLS changes broke the communication between master and schedulers in the case where the scheduler is running inside a non-host networking container.
This commit adds a hotfix to Mesos until a more suitable long-term solution is agreed upon.

High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (required)

DCOS-57220 TLS certificate issue with scheduler within container in non host-networking mode.

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot override-status teamcity/dcos/test/terraform/aws/onprem/static/group2 https://jira.mesosphere.com/browse/DCOS-56866

@mesosphere-mergebot changelog-not-required bugfix for 1.14.0 feature

@mesosphere-mergebot override-status teamcity/dcos/test/terraform/aws/onprem/static/group2 https://jira.mesosphere.com/browse/DCOS-56866

@mesosphere-mergebot changelog-not-required bugfix for 1.14.0 feature

@mesosphere-mergebot sync

authors: tillt vinodkone

repo: dcos/dcos

license_source: bigquery


text:
SI Tests for File Based Secrets

Summary: added a SI test similar to the env secrets test but this time for File Based Secrets
Jira issues: DCOS_OSS-4449

woot!!

repo: dcos/metronome


text:
Can't flash redherring_vial.hex [could not find USB device ]

Hello, I have a problem when I flashing the vial firmware. What should I do, please? These are the qmk tookbox output:
*** USBasp device disconnected (WinUSB): Van Ooijen Technische Informatica USBasp (16C0:05DC:0102)
*** AVRISP device connected (usbser): Microsoft USB 串行设备 (COM38) (16C0:0483:0100) [COM38]
*** USBasp device connected (WinUSB): Van Ooijen Technische Informatica USBasp (16C0:05DC:0102)
*** USBasp device connected (WinUSB): Van Ooijen Technische Informatica USBasp (16C0:05DC:0102)
*** Attempting to flash, please don't remove device
>>> avrdude.exe -p atmega32a -c avrisp -U flash:w:"D:\Program Files\avrdude-v7.0-rc1-windows-x64\redherring_vial.hex":i -P COM38

    avrdude.exe: AVR device initialized and ready to accept instructions

    Reading | ################################################## | 100% 0.01s

    avrdude.exe: Device signature = 0x000001
    avrdude.exe: Expected signature for ATmega32A is 1E 95 02
                 Double check chip, or use -F to override this check.

    avrdude.exe done.  Thank you.
*** Flash complete

>>> avrdude.exe -p atmega32a -c usbasp -U flash:w:"D:\Program Files\avrdude-v7.0-rc1-windows-x64\redherring_vial.hex":i
    avrdude.exe: error: could not find USB device with vid=0x16c0 pid=0x5dc vendor='www.fischl.de' product='USBasp'

*** Flash complete
    avrdude.exe done.  Thank you.

My guess is that you're using the incorrect COM port.  When you go into your Windows Device Manager, what do you see listed in the Serial port section?

Thanks for your reply! I have solved this problem with using MSYS to flash the hex. But I still can't flash hex with toolbox... Also I tried the 3V solenoid and it works very well👏

authors: DAydDaY dcpedit

repo: dcpedit/redherring


text:
Verify input of maximum leafs

On the Pentium II, with CPUID.8000_0000h(ECX=0h), the value in EAX will be 03020101h which may confuse ddcpuid.
Getting checking against 0x4000_0000 and 0x8000_0000, the minimum and maximum (+0xfff_ffff) should be used to check again the input leaf

Done in 3f418eb1acb0e7683b46998d37e1e231ece7cba4


text:
🛑 Danbs is down

In 41de361, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 210 ms

Resolved: Danbs is back up in 3aa8e5a after 331 days, 5 hours, 16 minutes.

repo: ddanbs/upptime


text:
🛑 Danbs is down

In b516f2a, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 222 ms

Resolved: Danbs is back up in 5e299b8 after 6 minutes.


text:
🛑 Danbs is down

In 4e25d93, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 2723 ms

Resolved: Danbs is back up in f55faad after 14 minutes.


text:
🛑 Danbs is down

In 83ba5fa, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 3421 ms

Resolved: Danbs is back up in 33d1522 after 44 minutes.


text:
🛑 Danbs is down

In e8c5367, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 4044 ms

Resolved: Danbs is back up in df1c4ad after 6 minutes.


text:
🛑 Danbs is down

In e3b0567, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 187 ms

Resolved: Danbs is back up in e80ce1d.


text:
🛑 Danbs is down

In 1e3b263, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 195 ms

Resolved: Danbs is back up in feccd44.


text:
🛑 Danbs is down

In a633aa1, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 155 ms

Resolved: Danbs is back up in 927af84.


text:
🛑 Danbs is down

In 890c6bd, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 166 ms

Resolved: Danbs is back up in 12caa7a.


text:
🛑 Danbs is down

In 0a4137b, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 189 ms

Resolved: Danbs is back up in 9e21825.


text:
条件分岐の情報を追加

#122 に関連して
条件分岐の情報を追加する

対象となった if 文　（文全体ではなく、条件判断式がわかれば良い）
else 句の有無
switch文の場合は、評価対象の変数名と、case の一覧

条件分岐の情報を実際に追いかけてみると、改善ネタがゴロゴロ転がっている。
なかなか良い。

バイトコードからだとこれらの情報には届かない。
条件分岐の位置に対応したソースコードを引っ張ってこれるようにする。
ソースコードからどの程度の情報が読み取れるかは要調査（現状javaparser依存）。
デバッグ情報を使用すれば条件分岐の位置のソースコードを取得はできるが、デバッグ情報に頼らなくてもメソッドは特定できるので、メソッド全体を対象にしてもいいかもしれない。
第一ステップとしては「メソッドのソースコード全体を取得して出力してみる」あたりかな。

repo: dddjava/Jig


text:
Update README.md for OpenMage

The Issue
How This PR Solves The Issue
Manual Testing Instructions
Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

Thank you for the PR!

repo: ddev/ddev-xhgui


text:
fix: create mutagen-agents tarball if it doesn't exist, fixes #6421

The Issue

#6421

The app is unable to start without a mutagen-agents.tar.gz file in the global bin directory.
How This PR Solves The Issue
This PR adds a check to make sure the tarbell exists in the DownloadMutagenIfNeeded function, and if it does not, downloads mutagen. It also adds a test to test this functionality works.
Manual Testing Instructions
Remove the tarbell file in the global bin directory e.g. rm ~/.ddev/bin/mutagen-agents.tar.gz and restart the app e.g. ddev restart
Automated Testing Overview
Adds the TestDownloadMutagen test which has the same setup as TestMutagenSimple but removes the tarbell if it exists, then starts the app. Then it verifies that the tarbell has been downloaded. Then it removes it again and restarts the app, and finally verifies that the tarbell has been downloaded again.

Release/Deployment Notes

Thanks!

authors: davearch rfay

repo: ddev/ddev


text:
Speed up processing

Add async processing for requests

Embedding generation is now handled in batches, which significantly improves the speed

repo: deadbits/vector-embedding-api


text:
Disable metrics for some/all queues

Hello there,
I'm trying to disable metrics collected for queues and exchanges (e.g. rabbitmq_queue_disk_reads).
Ideally I'm able to disable only for certain queues, however it would be alright to disable any queue related metrics.
(The reason is we have very high number of queues and the metrics take away significant performance from our brokers.)
So far I've tried:
[...]
{ prometheus, [
  { rabbitmq_exporter, [
    { path, "metrics" },
    { queue_messages_stat, [ ] },
    { exchange_messages_stat, [] }
  ] }
] },
[...]

Is there a simple way to disable any queue related metrics?
Thanks in advance for your help :)
Cheers,
Thubo

Hi, thanks you for using this exporter. I hope can look into this at the beginning of the next week.

Thanks a lot. If I can provide any help (logs, tests, ...) please let me know.

Unfortunately this took longer than expected. Rescheduled to 3.6.8 release support

application:set_env(prometheus, rabbitmq_exporter, [{exchange_messages_stat, [messages_published_total]}]).

leaves only rabbitmq_exchange_messages_published_total.
example config
[
 {rabbit,
  [
   {loopback_users, []}
  ]},
 {prometheus,
  [{rabbitmq_exporter,
    [
     {queue_messages_stat, [messages_published_total]},
     {exchange_messages_stat, [messages_published_total]}
    ]}
  ]}
].

This however can't disable ALL queue metrics.
If you need this for performance reasons then rendering metrics isn't that costly at all. Enumerating and getting stat OTOH can be costly. So filtering by queue name can help here probably.
Getting queue info is a two-step process:

rabbit_amqqueue:info_all(VHost);
rabbit_mgmt_db:augment_queues(Queues, ...).

Not sure info_all can be removed (perhaps replaced with lighter version, but this is just an ETS query).
But augment_queues can be called only for required queues.
Can you give more details about your situtations and how to reproduce?

So, i've updated my RabbitMQ image to 3.6.8 (as well as your plugin).
Next enabled the rabbitmq_management plugin, but not your plugin.
If I use the configuration you posted above I run into the following error, as soon as I want to access any queue metrics (through the normale WebGUI). If I remove the config snippet, the WebGUI works as expected.
=ERROR REPORT==== 28-Mar-2017::07:28:37 ===
JSON encode error: {bad_term,{<<"x-priority">>,signedint,10}}
While encoding:
[{incoming,[]},
 {deliveries,[]},
 {messages_details,
     [{avg,0.0},
[...]

enabling the prometheus_rabbitmq_exporter plugin results in
=ERROR REPORT==== 28-Mar-2017::07:33:33 ===
** gen_event handler rabbit_mgmt_reset_handler crashed.
** Was installed in rabbit_event
** Last event was: {event,plugins_changed,
                          [{enabled,[prometheus,prometheus_rabbitmq_exporter]},
                           {disabled,[]}],
                          none,1490686413890}
** When handler state == []
** Reason == {'function not exported',
                 [{prometheus_http,setup,[],[]},
                  {prometheus_rabbitmq_exporter,dispatcher,0,
                      [{file,"src/prometheus_rabbitmq_exporter.erl"},
                       {line,11}]},
                  {rabbit_mgmt_dispatcher,'-build_dispatcher/1-lc$^2/1-2-',1,
                      [{file,"src/rabbit_mgmt_dispatcher.erl"},{line,32}]},
                  {rabbit_mgmt_dispatcher,'-build_dispatcher/1-lc$^2/1-2-',1,
                      [{file,"src/rabbit_mgmt_dispatcher.erl"},{line,33}]},
                  {rabbit_mgmt_dispatcher,build_dispatcher,1,
                      [{file,"src/rabbit_mgmt_dispatcher.erl"},{line,32}]},
                  {rabbit_mgmt_app,register_context,2,
                      [{file,"src/rabbit_mgmt_app.erl"},{line,50}]},
                  {rabbit_mgmt_reset_handler,handle_event,2,
                      [{file,"src/rabbit_mgmt_reset_handler.erl"},{line,55}]},
                  {gen_event,server_update,4,
                      [{file,"gen_event.erl"},{line,533}]}]}

and neither the WebGUI nor the prometheus endpoint are working any longer.
I guess some of the changes in RabbitMQ 3.6.8 are not compatible with your plugin :(
As for our situation in general: We are running multiple brokers, each with 10k to 100k queues & connections. This leads to two issues:

There is a significant RAM and CPU impact on the brokers (the resource consumption approx. triples and the brokers have a tendency to crash more easily) if we export the queue-related metrics. (Also running some queries like rabbitmqctl list_queues becomes quite slow and creates a significant impact on CPU/RAM.)
We generate quite a lot of data we don't want/need: Our prometheus becomes quite busy handling the data for every queue, while we are only interested in the total number of queues (and possibly the number of delivered messages). Right now we use the 'normal' api endpoint to gather this data, but it would be nice to use something more native.

Does this help to clarify the situation?
Thanks again for your great work and your help!

Hi!
Setup & Configuration.
JSON encode error: {bad_term,{<<"x-priority">>,signedint,10}}
While encoding:

My plugin doesn't use JSON at all :-(. And before suggesting you this config snippet I've tested it on my fresh 3.6.8 install. But let's forget for the moment about this.
{enabled,[prometheus,prometheus_rabbitmq_exporter]}

New exporter version depends on two more plugins - accept and prometheus-httpd. Please download them from the release and try to enable it.
Btw I also pushed docker image too. Maybe you can use it as a base image. https://cloud.docker.com/swarm/deadtrickster/repository/registry-1.docker.io/deadtrickster/rabbitmq_prometheus/general.
Load handling
The quickest solution is to just don't use queues collector:

[
 {rabbit, [
           {loopback_users, []}
          ]},
 {prometheus,
  [{collectors,
    [
     %% Standard prometheus collectors
     prometheus_vm_statistics_collector,
     prometheus_vm_system_info_collector,
     prometheus_vm_memory_collector,
     prometheus_mnesia_collector,

     %% Process Info Collector
     prometheus_process_collector,

     %% Rabbitmq collectors
     prometheus_rabbitmq_overview_collector,
     prometheus_rabbitmq_exchanges_collector,
     prometheus_rabbitmq_mnesia_tables_collector,
     prometheus_rabbitmq_nodes_collector
    ]}
  ]}
].

This config will give you only queues count.
To filter queues by name we need to list them, right? So I'm curious what you are using now: Right now we use the 'normal' api endpoint to gather this data.
Thanks!

On the "JSON-Error":
I'm starting the following image:
docker run --rm -p 15672:15672 -p 5672:5672 deadtrickster/rabbitmq_prometheus:3.6.8.1

Next I create an exchange/queue, send a message to the exchange and consume the queue using pika 0.10.0.
Navigating to the GUI results in:

The same message also appears in the logs:
=ERROR REPORT==== 9-Apr-2017::09:21:22 ===
JSON encode error: {bad_term,{<<"x-priority">>,signedint,10}}
While encoding:
[{incoming,[]},
 {deliveries,[]},
 {messages_details,
     [{avg,0.0},
      {avg_rate,0.0},
      {samples,
          [[{timestamp,1491729685000},{sample,0}],
           [{timestamp,1491729680000},{sample,0}],
[...]

As for the endpoint I mentioned: The management plugin provides the /api/overview endpoint.
The returned JSON holds (among other information):
  "message_stats": {
    "publish": 1,
    "publish_details": {
      "rate": 0.2
    },
    "confirm": 0,
    "confirm_details": {
      "rate": 0
    },
    "return_unroutable": 0,
    "return_unroutable_details": {
      "rate": 0
    },
    "disk_reads": 0,
    "disk_reads_details": {
      "rate": 0
    },
    "disk_writes": 0,
    "disk_writes_details": {
      "rate": 0
    },
    "get": 0,
    "get_details": {
      "rate": 0
    },
    "get_no_ack": 0,
    "get_no_ack_details": {
      "rate": 0
    },
    "deliver": 0,
    "deliver_details": {
      "rate": 0
    },
    "deliver_no_ack": 1,
    "deliver_no_ack_details": {
      "rate": 0.2
    },
    "redeliver": 0,
    "redeliver_details": {
      "rate": 0
    },
    "ack": 0,
    "ack_details": {
      "rate": 0
    },
    "deliver_get": 1,
    "deliver_get_details": {
      "rate": 0.2
    }
  },
  "queue_totals": {
    "messages_ready": 0,
    "messages_ready_details": {
      "rate": 0
    },
    "messages_unacknowledged": 0,
    "messages_unacknowledged_details": {
      "rate": 0
    },
    "messages": 0,
    "messages_details": {
      "rate": 0
    }
  },
  "object_totals": {
    "consumers": 1,
    "queues": 1,
    "exchanges": 9,
    "connections": 1,
    "channels":

It seems - I haven't done any in depth analysis so far (!) - this endpoint is cached or a least lot less expensive, since we can use it to collect the metrics we need without the mentioned performance impact.
Right now I cannot test the config example you posted - but I will report back to you as soon as I can.
Hope this helps.
Thanks!

Hi,
Did you try suggested config yet? I will try to look at /api/overview shortly.
As for JSON... Can you please disable all prometheus stuff and see how it goes?
Thanks!

/api/overview returns cluster wide data. Since prometheus scrapes each node I'm breaking down this cluster-wide stat to per-node stat.
rabbitmq_message_stats_deliver_get{node="nonode@host"} = 1

Thoughts?

actually since all metrics are cluster-wide I don't think splitting by node just here makes sense

I would expect the metrics to be cluster-wide, as the other metrics are cluster wide as well.
I have some good and some bad news:
The good news: With the image deadtrickster/rabbitmq_prometheus:latest (c92d59f43fea) the JSON errors are gone and I can access the metrics in the GUI as expected.
However:
Accessing the /api/metrics endpoint at the image stated above gives me:
=WARNING REPORT==== 17-Apr-2017::15:52:56 ===
Management delegate query returned errors:
[{<0.404.0>,
  {error,badarg,
         [{ets,select,
               [queue_exchange_stats_publish,
                [{{{{'$1','$2'},'_'},'_'},
                  [{'==',{{resource,unknown,queue,
                                    {resource,<<"/">>,queue,<<"myqueue">>}}},
                         '$1'}],
                  [{{'$1','$2'}}]}]],
               []},
          {rabbit_mgmt_data,get_table_keys,2,
                            [{file,"src/rabbit_mgmt_data.erl"},{line,372}]},
          {rabbit_mgmt_data,queue_raw_deliver_stats_data,2,
                            [{file,"src/rabbit_mgmt_data.erl"},{line,169}]},
          {rabbit_mgmt_data,list_queue_data,2,
                            [{file,"src/rabbit_mgmt_data.erl"},{line,208}]},
          {rabbit_mgmt_data,'-all_list_queue_data/3-fun-0-',3,
                            [{file,"src/rabbit_mgmt_data.erl"},{line,75}]},
          {lists,foldl,3,[{file,"lists.erl"},{line,1263}]},
          {delegate,safe_invoke,2,[{file,"src/delegate.erl"},{line,219}]},
          {delegate,invoke,3,[{file,"src/delegate.erl"},{line,111}]}]}}]
=ERROR REPORT==== 17-Apr-2017::15:52:56 ===
** Generic server rabbit_mgmt_db_cache_queues terminating
** Last message in was {fetch,#Fun<rabbit_mgmt_db.22.11931579>,
                           [[[{pid,<0.587.0>},
                              {name,{resource,<<"/">>,queue,<<"myqueue">>}},
                              {durable,false},
                              {auto_delete,false},
                              {arguments,[]},
                              {owner_pid,''},
                              {exclusive,false},
                              {messages_ready,0},
                              {messages_unacknowledged,0},
                              {messages,0},
                              {reductions,3339},
                              {policy,''},
                              {exclusive_consumer_pid,''},
                              {exclusive_consumer_tag,''},
                              {consumers,1},
                              {consumer_utilisation,0.9989540506968384},
                              {memory,22248},
                              {slave_pids,''},
                              {synchronised_slave_pids,''},
                              {recoverable_slaves,''},
                              {state,running},
                              {garbage_collection,
                                  [{max_heap_size,0},
                                   {min_bin_vheap_size,46422},
                                   {min_heap_size,233},
                                   {fullsweep_after,65535},
                                   {minor_gcs,3}]},
                              {messages_ram,0},
                              {messages_ready_ram,0},
                              {messages_unacknowledged_ram,0},
                              {messages_persistent,0},
                              {message_bytes,0},
                              {message_bytes_ready,0},
                              {message_bytes_unacknowledged,0},
                              {message_bytes_ram,0},
                              {message_bytes_persistent,0},
                              {head_message_timestamp,''},
                              {disk_reads,0},
                              {disk_writes,0},
                              {backing_queue_status,
                                  [{mode,default},
                                   {q1,0},
                                   {q2,0},
                                   {delta,{delta,undefined,0,0,undefined}},
                                   {q3,0},
                                   {q4,0},
                                   {len,0},
                                   {target_ram_count,infinity},
                                   {next_seq_id,1},
                                   {avg_ingress_rate,0.1274716363635783},
                                   {avg_egress_rate,0.1274716363635783},
                                   {avg_ack_ingress_rate,0.0},
                                   {avg_ack_egress_rate,0.0}]},
                              {messages_paged_out,0},
                              {message_bytes_paged_out,0}]]]}
** When Server state == {state,none,[],undefined,5}
** Reason for termination ==
** {badarg,[{dict,fetch,
                  [{resource,unknown,queue,
                             {resource,<<"/">>,queue,<<"myqueue">>}},
                   {dict,0,16,16,8,80,48,
                         {[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]},
                         {{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]}}}],
                  [{file,"dict.erl"},{line,131}]},
            {rabbit_mgmt_db,'-list_queue_stats/3-lc$^1/1-1-',4,
                            [{file,"src/rabbit_mgmt_db.erl"},{line,363}]},
            {rabbit_mgmt_db,list_queue_stats,3,
                            [{file,"src/rabbit_mgmt_db.erl"},{line,360}]},
            {timer,tc,2,[{file,"timer.erl"},{line,181}]},
            {rabbit_mgmt_db_cache,handle_call,3,
                                  [{file,"src/rabbit_mgmt_db_cache.erl"},
                                   {line,107}]},
            {gen_server,try_handle_call,4,
                        [{file,"gen_server.erl"},{line,615}]},
            {gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,647}]},
            {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}

=CRASH REPORT==== 17-Apr-2017::15:52:56 ===
  crasher:
    initial call: rabbit_mgmt_db_cache:init/1
    pid: <0.621.0>
    registered_name: rabbit_mgmt_db_cache_queues
    exception exit: {badarg,
                        [{dict,fetch,
                             [{resource,unknown,queue,
                                  {resource,<<"/">>,queue,<<"myqueue">>}},
                              {dict,0,16,16,8,80,48,
                                  {[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                   [],[]},
                                  {{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                    [],[]}}}],
                             [{file,"dict.erl"},{line,131}]},
                         {rabbit_mgmt_db,'-list_queue_stats/3-lc$^1/1-1-',4,
                             [{file,"src/rabbit_mgmt_db.erl"},{line,363}]},
                         {rabbit_mgmt_db,list_queue_stats,3,
                             [{file,"src/rabbit_mgmt_db.erl"},{line,360}]},
                         {timer,tc,2,[{file,"timer.erl"},{line,181}]},
                         {rabbit_mgmt_db_cache,handle_call,3,
                             [{file,"src/rabbit_mgmt_db_cache.erl"},
                              {line,107}]},
                         {gen_server,try_handle_call,4,
                             [{file,"gen_server.erl"},{line,615}]},
                         {gen_server,handle_msg,5,
                             [{file,"gen_server.erl"},{line,647}]},
                         {proc_lib,init_p_do_apply,3,
                             [{file,"proc_lib.erl"},{line,247}]}]}
      in function  gen_server:terminate/7 (gen_server.erl, line 812)
    ancestors: [rabbit_mgmt_db_cache_sup,rabbit_mgmt_sup,
                  rabbit_mgmt_sup_sup,<0.441.0>]
    messages: []
    links: [<0.553.0>]
    dictionary: []
    trap_exit: false
    status: running
    heap_size: 1598
    stack_size: 27
    reductions: 399
  neighbours:

=SUPERVISOR REPORT==== 17-Apr-2017::15:52:56 ===
     Supervisor: {local,rabbit_mgmt_db_cache_sup}
     Context:    child_terminated
     Reason:     {badarg,
                     [{dict,fetch,
                          [{resource,unknown,queue,
                               {resource,<<"/">>,queue,<<"myqueue">>}},
                           {dict,0,16,16,8,80,48,
                               {[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                []},
                               {{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                 []}}}],
                          [{file,"dict.erl"},{line,131}]},
                      {rabbit_mgmt_db,'-list_queue_stats/3-lc$^1/1-1-',4,
                          [{file,"src/rabbit_mgmt_db.erl"},{line,363}]},
                      {rabbit_mgmt_db,list_queue_stats,3,
                          [{file,"src/rabbit_mgmt_db.erl"},{line,360}]},
                      {timer,tc,2,[{file,"timer.erl"},{line,181}]},
                      {rabbit_mgmt_db_cache,handle_call,3,
                          [{file,"src/rabbit_mgmt_db_cache.erl"},{line,107}]},
                      {gen_server,try_handle_call,4,
                          [{file,"gen_server.erl"},{line,615}]},
                      {gen_server,handle_msg,5,
                          [{file,"gen_server.erl"},{line,647}]},
                      {proc_lib,init_p_do_apply,3,
                          [{file,"proc_lib.erl"},{line,247}]}]}
     Offender:   [{pid,<0.621.0>},
                  {id,rabbit_mgmt_db_cache_queues},
                  {mfargs,{rabbit_mgmt_db_cache,start_link,[queues]}},
                  {restart_type,permanent},
                  {shutdown,5000},
                  {child_type,worker}]

=ERROR REPORT==== 17-Apr-2017::15:52:56 ===
Ranch listener rabbit_web_dispatch_sup_15672 had connection process started with cowboy_protocol:start_link/4 at <0.620.0> exit with reason: [{reason,{{badarg,[{dict,fetch,[{resource,unknown,queue,{resource,<<"/">>,queue,<<"myqueue">>}},{dict,0,16,16,8,80,48,{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]},{{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]}}}],[{file,"dict.erl"},{line,131}]},{rabbit_mgmt_db,'-list_queue_stats/3-lc$^1/1-1-',4,[{file,"src/rabbit_mgmt_db.erl"},{line,363}]},{rabbit_mgmt_db,list_queue_stats,3,[{file,"src/rabbit_mgmt_db.erl"},{line,360}]},{timer,tc,2,[{file,"timer.erl"},{line,181}]},{rabbit_mgmt_db_c
ache,handle_call,3,[{file,"src/rabbit_mgmt_db_cache.erl"},{line,107}]},{gen_server,try_handle_call,4,[{file,"gen_server.erl"},{line,615}]},{gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,647}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]},{gen_server,call,[<0.621.0>,{fetch,#Fun<rabbit_mgmt_db.22.11931579>,[[[{pid,<0.587.0>},{name,{resource,<<"/">>,queue,<<"myqueue">>}},{durable,false},{auto_delete,false},{arguments,[]},{owner_pid,''},{exclusive,false},{messages_ready,0},{messages_unacknowledged,0},{messages,0},{reductions,3339},{policy,''},{exclusive_consumer_pid,''},{exclusive_consumer_tag,''},{con
sumers,1},{consumer_utilisation,0.9989540506968384},{memory,22248},{slave_pids,''},{synchronised_slave_pids,''},{recoverable_slaves,''},{state,running},{garbage_collection,[{max_heap_size,0},{min_bin_vheap_size,46422},{min_heap_size,233},{fullsweep_after,65535},{minor_gcs,3}]},{messages_ram,0},{messages_ready_ram,0},{messages_unacknowledged_ram,0},{messages_persistent,0},{message_bytes,0},{message_bytes_ready,0},{message_bytes_unacknowledged,0},{message_bytes_ram,0},{message_bytes_persistent,0},{head_message_timestamp,''},{disk_reads,0},{disk_writes,0},{backing_queue_status,[{mode,default},{q1,0},{q2,0},{delta,{delta,undefined,
0,0,undefined}},{q3,0},{q4,0},{len,0},{target_ram_count,infinity},{next_seq_id,1},{avg_ingress_rate,0.1274716363635783},{avg_egress_rate,0.1274716363635783},{avg_ack_ingress_rate,0.0},{avg_ack_egress_rate,0.0}]},{messages_paged_out,0},{message_bytes_paged_out,0}]]]},60000]}}},{mfa,{prometheus_rabbitmq_exporter_handler,handle,2}},{stacktrace,[{gen_server,call,3,[{file,"gen_server.erl"},{line,212}]},{rabbit_mgmt_db,submit_cached,4,[{file,"src/rabbit_mgmt_db.erl"},{line,690}]},{prometheus_rabbitmq_queues_collector,'-collect_mf/2-lc$^0/1-0-',1,[{file,"src/collectors/prometheus_rabbitmq_queues_collector.erl"},{line,76}]},{prometheus
_rabbitmq_queues_collector,collect_mf,2,[{file,"src/collectors/prometheus_rabbitmq_queues_collector.erl"},{line,76}]},{prometheus_collector,collect_mf,3,[{file,"src/prometheus_collector.erl"},{line,157}]},{prometheus_registry,'-collect/2-lc$^0/1-0-',3,[{file,"src/prometheus_registry.erl"},{line,78}]},{prometheus_registry,collect,2,[{file,"src/prometheus_registry.erl"},{line,78}]},{prometheus_text_format,format,1,[{file,"src/formats/prometheus_text_format.erl"},{line,74}]}]},{req,[{socket,#Port<0.26180>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.620.0>},{method,<<"GET">>},{version,'HTTP/1.1'},{peer,{{172,17,0,1},51666
}},{host,<<"localhost">>},{host_info,undefined},{port,15672},{path,<<"/api/metrics">>},{path_info,undefined},{qs,<<>>},{qs_vals,[]},{bindings,[]},{headers,[{<<"host">>,<<"localhost:15672">>},{<<"connection">>,<<"keep-alive">>},{<<"cache-control">>,<<"max-age=0">>},{<<"upgrade-insecure-requests">>,<<"1">>},{<<"user-agent">>,<<"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36">>},{<<"accept">>,<<"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8">>},{<<"dnt">>,<<"1">>},{<<"accept-encoding">>,<<"gzip, deflate, sdch, br">>},{<<"accept-
language">>,<<"en-DE,de-DE;q=0.8,de;q=0.6,en-US;q=0.4,en;q=0.2">>},{<<"cookie">>,<<"grafana_sess=7b12ae45f1d12b8b; m=2258:Z3Vlc3Q6Z3Vlc3Q%253D">>}]},{p_headers,[{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[]},{body_state,waiting},{buffer,<<>>},{multipart,undefined},{resp_compress,true},{resp_state,waiting},{resp_headers,[]},{resp_body,<<>>},{onresponse,#Fun<rabbit_cowboy_middleware.onresponse.4>}]},{state,{default}}]

Would it make sense to track these errors in another issue? I fear this thread is rather complicated to follow...

I thought this error was fixed there: https://github.com/deadtrickster/prometheus_rabbitmq_exporter/issues/22 :-(.
Have you tried the config?

Ok it must be something with my? docker images. I tested git version (make run-broker) and I tested their 3.6.9-1 deb package. It works there

looks like I finally fixed docker images. Also I started to integrate metrics from /api/overview.

Hi, I added some /api/overview metrics. I attached latest plugin build. Don't forget to rename zip to ez.
prometheus_rabbitmq_exporter-v3.6.9.1.zip

Using rabbitmq 3.7.4, erlang 20.3 on Windows I am unable to disable queue metrics.  I have tried using the config from your comment posted Mar 28 2017, and have also added exchange_messages_stat, [] but all queue metrics are still exported.  Note that the config below does disable exchange metrics.
[
{rabbit, [
{queue_master_locator, "min-masters"}
]},
{prometheus, [
{rabbitmq_exporter, [
{path, "/mymetrics"},
{connections_total_enabled, false},
{queue_messages_stat, []},
{exchange_messages_stat, []}
]},
{collectors,
[
%% Standard prometheus collectors
prometheus_vm_statistics_collector,
prometheus_vm_system_info_collector,
prometheus_vm_memory_collector,
prometheus_mnesia_collector,
 %% Process Info Collector

%%     prometheus_process_collector,
 %% Rabbitmq collectors

%%     prometheus_rabbitmq_overview_collector,
%%     prometheus_rabbitmq_exchanges_collector,
prometheus_rabbitmq_mnesia_tables_collector
%%     prometheus_rabbitmq_nodes_collector
]}
]},
{rabbitmq_management, [
{listener, [
{port, 15672},
{ssl, false}
]}
]}
].

right, because messages_stat controls messages stat. and you also have exchange_collector disabled. you can try the same with queue_collector.

Is there another way to disable the queue_collector?  I have tried with the updated config below, limiting queue metrics to messages_published_total, and I still see the full complement of queue metrics returned.
[
{prometheus, [
{rabbitmq_exporter, [
{path, "/mymetrics"},
{connections_total_enabled, false},
{queue_messages_stat, [messages_published_total]},
{exchange_messages_stat, []}
]},
{collectors,
[
%% Standard prometheus collectors
prometheus_vm_statistics_collector,
prometheus_vm_system_info_collector,
prometheus_vm_memory_collector,
prometheus_mnesia_collector,
%% Rabbitmq collectors
prometheus_rabbitmq_mnesia_tables_collector
]}
]},
{rabbitmq_management, [
{listener, [
{port, 15672},
{ssl, false}
]}
]}
].
With the above config, queue metrics returned include:
rabbitmq_queue_durable
rabbitmq_queue_auto_delete
rabbitmq_queue_exclusive
rabbitmq_queue_messages_ready
rabbitmq_queue_messages_unacknowledged
rabbitmq_queue_messages
rabbitmq_queue_messages_ready_ram
rabbitmq_queue_messages_unacknowledged_ram
rabbitmq_queue_messages_ram
rabbitmq_queue_messages_persistent
rabbitmq_queue_message_bytes
rabbitmq_queue_message_bytes_ready
rabbitmq_queue_message_bytes_unacknowledged
rabbitmq_queue_message_bytes_ram
rabbitmq_queue_message_bytes_persistent
rabbitmq_queue_head_message_timestamp
rabbitmq_queue_disk_reads
rabbitmq_queue_disk_writes
rabbitmq_queue_disk_size_bytes
rabbitmq_queue_consumers
rabbitmq_queue_consumer_utilisation
rabbitmq_queue_memory
rabbitmq_queue_state
rabbitmq_queue_messages_published_total

ok, I'll look at this

ok, found, looks like not-so-great-hack https://github.com/deadtrickster/prometheus_rabbitmq_exporter/blob/master/src/prometheus_rabbitmq_exporter.erl#L9
proper fix is coming

@kfreem02 please try the latest release

Confirm fixed

Great, thanks

authors: Thubo deadtrickster kfreem02


text:
Beep and red line

hi
1)Is there any way to beep when the barcode is scanned?
2) Have red line in the middle of the scanning part ?

Not currently, though both could potentially be implemented. The first seems like a more worthy feature than the second, as getting a buzz/beep when the scan is complete could be a convenient feature.

authors: cissemy forrestmid

repo: dealrinc/cordova-gmv-barcode-scanner


text:
Not compiling with SDCC

Hi,
I'm using platformio to develop for an STM8 but nanoMODBUS is not compiling.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/ststm8/stm8sblue.html
PLATFORM: ST STM8 (2.1.0) > ST STM8S103F3 Breakout Board
HARDWARE: STM8S103F3P6 16MHz, 1KB RAM, 8KB Flash
DEBUG: Current (stlink) External (stlink)
PACKAGES:
 - framework-arduinoststm8 @ 0.50.210317
 - tool-stm8binutils @ 0.230.0 (2.30)
 - toolchain-sdcc @ 1.30901.11242 (3.9.1)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 13 compatible libraries
Scanning dependencies...
Dependency Graph
|-- nanoModbus
Building in release mode
Compiling .pio\build\stm8sblue\src\main.c.rel
Compiling .pio\build\stm8sblue\libb6b\nanoModbus\nanomodbus.c.rel
src\main.c:32: warning 85: in function read_serial unreferenced function argument : 'arg'
src\main.c:51: warning 85: in function write_serial unreferenced function argument : 'arg'
src\main.c:63: warning 85: in function handler_read_holding_registers unreferenced function argument : 'unit_id'
src\main.c:63: warning 85: in function handler_read_holding_registers unreferenced function argument : 'arg'
lib\nanoModbus\nanomodbus.c:1152: error 2: Initializer element is not a constant expression
lib\nanoModbus\nanomodbus.c:1290: error 0: Duplicate symbol 'subreq_file_number', symbol IGNORED
lib\nanoModbus\nanomodbus.c:1261: error 177: previously defined here
lib\nanoModbus\nanomodbus.c:1291: error 0: Duplicate symbol 'subreq_record_number', symbol IGNORED
lib\nanoModbus\nanomodbus.c:1262: error 177: previously defined here
lib\nanoModbus\nanomodbus.c:1292: error 0: Duplicate symbol 'subreq_record_length', symbol IGNORED
lib\nanoModbus\nanomodbus.c:1263: error 177: previously defined here
lib\nanoModbus\nanomodbus.c:1293: error 20: Undefined identifier 'subreq_record_length'
lib\nanoModbus\nanomodbus.c:1296: error 20: Undefined identifier 'subreq_file_number'
lib\nanoModbus\nanomodbus.c:1296: error 20: Undefined identifier 'subreq_record_number'
lib\nanoModbus\nanomodbus.c:1297: error 20: Undefined identifier 'subreq_record_length'
lib\nanoModbus\nanomodbus.c:1305: error 20: Undefined identifier 'subreq_record_length'
lib\nanoModbus\nanomodbus.c:1311: error 20: Undefined identifier 'subreq_record_length'
*** [.pio\build\stm8sblue\libb6b\nanoModbus\nanomodbus.c.rel] Error 1
========================================================================================= [FAILED] Took 10.02 seconds =========================================================================================

I'm new to C development and microcontrollers in general so I'm sorry if this is something obvious.
Any help is appreciated.

Can you try building with the --std-c99 compiler flag? I expect it to fix at least the errors about undefined identifiers

I never used this compiler, so I made a couple of tests:

with latest SDCC 4.3.0, almost all errors are gone, except for the one about VLAs (Initializer element is not a constant expression), which looks like SDCC is not supporting at all
with your version, 3.9.0, I couldn't find any flag that could mitigate the problem, as per the documentation C99 support is incomplete

So I would say, since all the errors are inside handle_read_file_record(), as a workaround you could disable it by defining NMBS_SERVER_READ_FILE_RECORD_DISABLED, if you don't plan on using FC 20  .
Otherwise this function should be substantially changed to remove the usage of features not supported by SDCC

The new new one builds with the c99 flag. The defines didn't do anything.

The new new one builds with the c99 flag.

Nice! Also I think the --std-c99 was never necessary, so you can omit it

The defines didn't do anything.

Strange, how are you defining them? I added -DNMBS_SERVER_READ_FILE_RECORD_DISABLED -DNMBS_SERVER_WRITE_FILE_RECORD_DISABLED to the sdcc command line and these functions were skipped as expected

I just put
#define NMBS_SERVER_READ_FILE_RECORD_DISABLED
#define NMBS_SERVER_WRITE_FILE_RECORD_DISABLED

into my main.c.

ae6a93c963b497fc71296aa727ba09b40c15a2e7

@debevv,  I want to discuss about commit a08d59c. I think, it is non-optimal memory usage in struct subreq. Now, it usage 7*23=245 bytes on stack always. It may be big for embedded devices. It's a shame that almost always only the first element will be used (when we didn't use multiple sub-requests in one request). Maybe we can leave variable-length array (VLA)? VLA is part of C99 standard. Old versions SDCC were not supported VLA, but it fixed in last year and it already available in SDCC-4.3.0-RC1. Also, I can offer next variant:
struct {
        uint8_t reference_type;
        uint16_t file_number;
        uint16_t record_number;
        uint16_t record_length;
    }
#ifdef __STDC_NO_VLA__
    subreq[35];    // 245 / subreq_header_size
#else
    subreq[subreq_count];
#endif

Macros __STDC_NO_VLA__ is is part of the standard С11, but old versions SDCC understand it too, including --std-c99.
What do you think?

@arhiv6 Yes, that would be a downside of this approach. But consider that this is not the only place where it happens: the first one it comes to my mind is in handle_read_discrete() where a whole nmbs_bitfield is loaded onto the stack (or, in general, the nmbs_bitfield array itself when used by the user). For me it's a decent compromise between memory usage and ease of development.
Anyway, in this case it doesn't make sense to not use your solution, I really didn't know the existence of these macros. I will implement it asap
PS are you sure about SDCC 4.3.0 rc1? Because I tried 4.9.0 and the VLA didn't compile (see my previous comment)

I checked VLA in SDCC 4.3.0-rc1 and it it not fully supported :( They added support VLA to their changelog and removed the line from the "SDCC Compiler User Guide" that VLA is not supported. I will send them a issue.  But this is not so important if you use a macro __STDC_NO_VLA__. Good news: I checked supporting macros __STDC_NO_VLA__ for different SDCC versions. It supported since version 3.2 (released in July 2012) to last version 4.3 (released 07.07.2023).
Where did you get version 4.9.0? Maybe we are talking about different compilers? I checked it: https://sdcc.sourceforge.net/.

@debevv, I want to discuss about commit a08d59c. I think, it is non-optimal memory usage in struct subreq. Now, it usage 7*23=245 bytes on stack always. It may be big for embedded devices. It's a shame that almost always only the first element will be used (when we didn't use multiple sub-requests in one request). Maybe we can leave variable-length array (VLA)? VLA is part of C99 standard. Old versions SDCC were not supported VLA, but it fixed in last year and it already available in SDCC-4.3.0-RC1. Also, I can offer next variant:
struct {
        uint8_t reference_type;
        uint16_t file_number;
        uint16_t record_number;
        uint16_t record_length;
    }
#ifdef __STDC_NO_VLA__
    subreq[35];    // 245 / subreq_header_size
#else
    subreq[subreq_count];
#endif

Macros __STDC_NO_VLA__ is is part of the standard С11, but old versions SDCC understand it too, including --std-c99.
What do you think?

e3456986b551c891d4b95e89aaf5eded15e6f3a2

authors: DracoTomes arhiv6 debevv

repo: debevv/nanoMODBUS


text:
DBZ-4388 Resolve default values for non-optional columns

https://issues.redhat.com/browse/DBZ-4388

The Vitess error is unrelated, logged as DBZ-4399

Closed in favor of PR #3017

repo: debezium/debezium


text:
Admin Portal Related

New Features

add interface of pagination user
support filter email and display name in user list
support edit user active and display name
add .idea/ to .gitignore

:shipit:

authors: XeniaLu lbhsot

repo: decentfox/fence


text:
windows batch files broken

'.' is not recognized as an internal or external command, operable program or batch file. '--fast' is not recognized as an internal or external command, operable program or batch file. '--loglevel' is not recognized as an internal or external command, operable program or batch file. '--port' is not recognized as an internal or external command, operable program or batch file. '--httpport' is not recognized as an internal or external command, operable program or batch file. '--contentport' is not recognized as an internal or external command, operable program or batch file. '--prefix' is not recognized as an internal or external command, operable program or batch file. '--n' is not recognized as an internal or external command, operable program or batch file. '--apikey' is not recognized as an internal or external command, operable program or batch file. '--startminer' is not recognized as an internal or external command, operable program or batch file.
Looks like the windows files are broken. ran start.bat and this happened.

Your console directory needs to be on the bronzeage-node directory. There you can start it by running this command:
bin\start.bat
If you want to start start.bat file from anywhere, you need to edit it's contents as such:
@ECHO OFF

setlocal
for %%P in (%PATHEXT%) do (
    if exist "%%~$PATH:node.exe" (
      start "server" %%~$PATH:node.exe ./browser/server.js --apikey %RPC_API_KEY% --serverport %SERVER_PORT% --daemon
      GOTO next
    )
  )
)

:next

%~dp0/decentraland-node \
  --fast \
  --loglevel=info \
  --port=2301 \
  --httpport=8301 \
  --contentport=9301 \
  --prefix="data" \
  --n=testnet \
  --apikey=%RPC_API_KEY% \
  --startminer=%START_MINER%

Replace the contents of the start.bat file with the contents above.
Note that you still need to replace %RPC_API_KEY% with a API key of your choosing, for example: "test1234"
Please report if you encounter any further issues.

authors: NullFlex Rajatapaus

repo: decentraland/bronzeage-node

license: mit


text:
Failing to build

Hello,
The following error is being thrown when running npm install.
OS: MacOS Big Sur (command line tools up to date)
Node: 16.17.0 (fresh install with node-gyp)
npm ERR! path /Users/<username>/code/ion/ion-tools/node_modules/node-webcrypto-ossl
npm ERR! command failed
npm ERR! command sh -c -- node-gyp rebuild
npm ERR! CXX(target) Release/obj.target/nodessl/src/main.o```

Hi, I've got same issue.
Did you fix it?

authors: Hyunhum stonebraker

repo: decentralized-identity/ion-tools


text:
Cannot repeat the experiment results of LTSF.

With default setting, I tried to repeat the experiment of LTSF (PatchTST on ETTh1, both look-back window and predict window have length of 96). But the results seem completely different from the paper.

test_report.csv
Are there any further steps to process the report?

Thank you for your attention and question, the test_report.csv stores the results calculated after de_normalization. You can unzip the generated zip file, and the metric results ending in _norm are the normalized results, which are the multivariate forecasting results in the paper.
The results corresponding to the metrics shown in the red box in the following figure are the normalized results.

Thank you for your timely response. The issue is closed.

repo: decisionintelligence/TFB


text:
Sorting albums by name

Albums can be sorted by count, date and name. When sorting by name, the order is not alphabetical.

True, sorting by name places special folders (Camera, Shortcuts, app
folders...) before regular folders. This custom sort style can be found as
the default in the Samsung Gallery, for example.
I think it's a useful tweak, but I will add an option to sort purely by
name.
On Wed, 6 Jan 2021, 07:57 Donkey-Doug, notifications@github.com wrote:

Albums can be sorted by count, date and name. When sorting by name, the
order is not alphabetical.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deckerst/aves/issues/41, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKBEXNNP6W65BYZELRUP73SYOKOTANCNFSM4VWROXHQ
.

authors: Donkey-Doug deckerst

repo: deckerst/aves


text:
Incompatible with Paradise Lost

Cannot be used with the Paradise Lost mod (https://www.curseforge.com/minecraft/mc-mods/paradise-lost).

This issue has since been fixed in the newest 1.18.2 version it would seem

authors: Tishbyte decodinatorX

repo: decodinatorX/Liroth-Revamped-Fabric


text:
Home page issue

[x] Fixes issue #13 : "Improve the home page

"
[x] Other checks

Reason for pull request:
"Why was this pull request created"
Description of changes or additions:
"Insert description of changes made in this pull request here"
Screenshots:
"Insert screenshots here if available"

The validation comments are now visible :)

Looks good to me. Thanks a lot for all of your efforts @snehalkhandve .


text:
[CONTROLLER/PROMETHEUS] support encoding str

This PR is for:

Server
-->

support encoding str
Checklist

[ ] Added unit test.

Backport to branches

main

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: deepflowio/deepflow


text:
remove the target that was not aim for by this version

So the current main repo is what was the v3 branch?
looking through it the look at the deepgram seems to have been retargeted to --
netcoreapp3.1;net5.0;net6.0;net7.0;netstandard2.0
were it was reworked to just target--
net6.0;net7.0
the other framework were targeted in the V2-support and why I went back to add the feature to that branch.
also, I noticed in the CI.yml & CD.yml was also targeting other versions and not just [6.0,7.0]
that may be why you are getting the error in https://github.com/deepgram/deepgram-dotnet-sdk/issues/115

Is this a breaking change?

authors: CopperBeardy lukeocodes

repo: deepgram/deepgram-dotnet-sdk


text:
Failing Test TestSparkStorageUtils

Issue Description
After 46400bcc701a111895c6b7a39f386d05b35db973, i.e. after https://github.com/deeplearning4j/DataVec/pull/304:
Failed tests:
  TestSparkStorageUtils.testSaveRestoreMapFile:78 expected:<[zero, 0, 0.0]> but was:<[two, 22, 22.0]>
  TestSparkStorageUtils.testSaveRestoreMapFileSequences:131 expected:<[[zero, 0, 0.0], [one, 1, 1.0], [two, 2, 2.0]]> but was:<[[Bzero, 10, 10.0], [Bone, 11, 11.0], [Btwo, 12, 12.0]]>

See
https://github.com/deeplearning4j/DataVec/blob/master/datavec-spark/src/test/java/org/datavec/spark/storage/TestSparkStorageUtils.java#L76-L78
Same issue in https://github.com/deeplearning4j/DataVec/blob/master/datavec-spark/src/test/java/org/datavec/spark/storage/TestSparkStorageUtils.java#L76-L78

Fixed here: #307
Thanks for flagging this.

authors: AlexDBlack huitseeker


text:
ctr_lon/lat argument in gridding script

Sometimes, such as when using a preset domain like conus, ctr_lon and ctr_lat are required in make_GLM_grids.py but are then ignored. Define and document a consistent logic for which arguments are required, and when.

It would be a good idea to refactor all the if blocks, etc. into a set of higher level decisions and then functions called as a result of those decisions
e.g.
start_end_times()
determine_gridding_mode()
kwargs_for_split_event_fixed_grid()
These will be easier to test.

split_events and fixed_grid should without goes_sector should interpret ctr_lon,ctr_lat and width,height alongside dx,dy to make an inference about custom fixed grid coordinates.

Reference on testing scripts:
http://dustinrcollins.com/testing-python-command-line-apps

Closed by https://github.com/deeplycloudy/glmtools/commit/ef415fdd895c5cf327112e276e89a3f8c134026d

repo: deeplycloudy/glmtools


text:
git clone an earlier version

Hello alphafold support, I wonder if there is a command that I can check out version 2.1.1, for example:
$ git clone -b 2.1.1 https://github.com/deepmind/alphafold.git
Cloning into 'alphafold'...
fatal: Remote branch 2.1.1 not found in upstream origin
Unexpected end of command stream
I want to reproduce a result from 2.1.1; Thank you!

Hi, there is a small typo in your command -- the branch is called v2.1.1 instead of 2.1.1.
The correct command is:
git clone -b 'v2.1.1' https://github.com/deepmind/alphafold.git

authors: Augustin-Zidek ryao-mdanderson

repo: deepmind/alphafold


text:
change int64 to int32 to avoid warnings

I have some annoying warnings because the int64 are converted to int32 on my GPU.
They can easily be avoided by changing the dtypes to int32 (which is quite sufficient).

I hope I did it right now, I changed all +1 occurences with safe_int32_increment.
All tests are ok. And I fetched upstream.
Now I do have errors when I use the faulty dtype. It seems everything is covered.

Btw: this is a small change so I'd be happy to approve the PR and patch the change in myself as it is merged. Let me know whether that's okay for you :-)! Thanks a lot again!

Hi @mkunesch
Sorry for my slow response. I hope I did that last one correct.
Nice to hear that the change also makes the code safer!

authors: mkunesch rdaems

repo: deepmind/optax


text:
Create .gitignore

Based on JAX's gitignore

Hey Neil, thanks for the contribution.
Yeah I think we can safely remove those entries since Optax does not rely on Bazel/TF etc.

If you can remove those entries we can then merge the PR.
Apologies for the delay in getting back to you.

Done as requested :)

Hey @NeilGirdhar @hbq1 what's the state of this PR? Having a gitignore sure helps :)

It should be ready to check in right?  Unless you want me to rebase onto master?

Apologies for the delay! Merged now.


text:
License?

What license covers this work?

Using Apache License 2 as storm does. License file added.

authors: deepnighttwo timmolter

repo: deepnighttwo/yet-another-storm-ui


text:
源码

后期会提供模型的源码吗？

@yyfyyf123 https://github.com/deepseek-ai/DeepSeek-V2/issues/7


text:
feat: specify individual connection parameters

Related Issues

fixes #928

Proposed Changes:
Allow user to provide connection parameters as a dictionary of individual arguments
How did you test it?

Ran existing test
Updated existing test
Added unit test for to_dict() and from_dict()

Notes for the reviewer
This PR is labeled as a feature rather than a bug because the underlying library, rather than Haystack itself, contains the bug.
Checklist

I have read the contributors guidelines and the code of conduct
I have updated the related issue with new insights and changes
I added unit tests and updated the docstrings
I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.

No problems @anakin87! Thank you for stepping in. I reverted the changes and enhanced the docstrings in the latest commit.

repo: deepset-ai/haystack-core-integrations


text:
ERROR Error: Uncaught (in promise): ReferenceError: GoldenLayout is not defined

Current behavior

I am using Golden Layout in Angular 4 application with webpack. As solution suggested here I m using this plunker code. It throws below error
ERROR Error: Uncaught (in promise): ReferenceError: GoldenLayout is not defined

Location:
ngOnInit(){
    this.layout = new **GoldenLayout**(this.config, $(this.el.nativeElement).find("#layout"));

    this.layout.registerComponent('test1', (container, componentState) => {
          let factory = this.componentFactoryResolver.resolveComponentFactory(AppComponent);

          var compRef = this.viewContainer.createComponent(factory);
          compRef.instance.setEventHub(this.layout.eventHub);
          compRef.instance.message = componentState.message;
          container.getElement().append($(compRef.location.nativeElement));
    });

    this.layout.registerComponent('test2', (container, componentState) => {
          let factory = this.componentFactoryResolver.resolveComponentFactory(App2Component);

          var compRef = this.viewContainer.createComponent(factory);
          compRef.instance.setEventHub(this.layout.eventHub);
          compRef.instance.message = componentState.message;
          container.getElement().append($(compRef.location.nativeElement));
    });

    this.layout.init();
  }

Expected behavior:

Application should work fine.
Codepen example:

issue resolved by defining variable in webpack config.
plugins: [
    new webpack.ProvidePlugin({
      'GoldenLayout': 'golden-layout'
    }),
]

repo: deepstreamIO/golden-layout


text:
feat request: return hardhat errors on failed factories

Is your feature request related to a problem? Please describe.
We were getting an unable to generate smock spec from string error when trying to construct a fake from an interface contract. It wasn't directly clear from smock what the issue was. In our case, we found the root cause to be that there were two different IERC20 artifacts in the repo -- which breaks getContractFactory. See hardhat error: multiple artifacts for a contract issue
Describe the solution you'd like
We should probably surface errors when parsing the spec string

Solution A: Log out caught errors (probably not ideal because we rely optional catch binding to parse spec)
Solution B: Store caught errors and log them if all tries fail

Additional context
https://github.com/defi-wonderland/smock/blob/d6397b7ed3b414395f43a97f697ef22fb46054a2/src/factories/ethers-interface.ts#L6-L19

hi @JChiaramonte7,
thanks for pointing this out, we've created a task to the roadmap to address this issue,
hope this is fixed soon :)

closed with #127

repo: defi-wonderland/smock


text:
Pathfinder: Kingmaker integration

Add integration for Pathfinder Kingmaker import

kingmaker will be imported as a premium module by foundry or sigil team

authors: DawidIzydor deidril


text:
chore(roadmap): update roadmap for 2.x

Closes https://github.com/deis/workflow/issues/309
Linked to related issues from deis/deis for roadmap items where it makes sense. Many of these roadmap items still need Workflow/Kubernetes-focused proposals.

Thanks for making those fixes @slack!

No problemo!

authors: sgoings slack

repo: deis/workflow


text:
fix: update e2e resource for initContainers and ephemeralContainers

Description
What this PR does / why we need it:

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes a e2e test in #1086
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ ] CI tests

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

Thanks for the fix @junczhu. Happy to approve when you think it's ready

authors: akashsinghal junczhu

repo: deislabs/ratify


text:
Messages.po not filled by bash ./i18n.sh

index.php
<html>
<body>
<h1>_('Hello World')</h1>
</body>
</html>

Structure:

index.php
locale
-- en
--- LC_MESSAGES
---- messages.po
-- nl
--- LC_MESSAGES
---- messages.po
-- fr
--- LC_MESSAGES
---- messages.po

➜  testlocales ls
composer.json composer.lock index.php     locale        vendor
➜  testlocales cd vendor/delight-im/i18n
➜  i18n bash ./i18n.sh NL
Extracting and updating translations
sed: 1: "locale/messages.pot": extra characters at the end of l command

I might be misinterpreting the functionality, but I was expecting 'hello world' to appear in the NL messages.po.

Thanks for your question and the perfect description of the problem!
The cause of this issue is that i18n.sh must be at the root of your project, at the same level as, or higher than, all your PHP source files. I see that this is not documented.
In order to solve the issue, you would thus have to replace your regular
cd vendor/delight-im/i18n

with a one-time
cp vendor/delight-im/i18n/i18n.sh .

to copy the script to your project’s root folder. But I understand that this may be undesirable, because it duplicates code and may force you to include the script in your project’s .gitignore – which would also force you to repeat the step of copying the script on every new machine.
Does that help?
Apart from that quick fix, the script certainly needs a parameter to specify which directory it should operate on.

Yes, progress.
I now see new text variables defined in index.php appear in a new locale/messages.pot file.
It doesn't make a difference if I do ./18n.sh nl-BEor ./18n.sh nl.

I found the fix (for me). I removed the double quotes on lines 18, 23, 28, 46, 53

Had to fix some more stuff. This is the script I ended up with.

Notice removal of double qoutes around variables with strings
Notice the explicit sed expression '' (see above)
Notice mkdir -p (--parent doesn't exist on macOS)
Notice commented lines for sed replace - I don't know how to fix this.
sed: 1: "0,/\"Content-Type: text ...": bad flag in substitute command: '}'

Thanks for looking into this!

Regarding the sed problem, the issue is that GNU sed (Linux) only supports sed -i and sed -i'', while BSD sed (macOS) only supports sed -i ''. There’s no way to make the syntax compatible with both standards.
What we could do is use sed -i.bak and then remove the unneeded backup file, either after every call or once at the end.
Another solution would be using sed on "$file" without the -i argument, redirecting the output to "$file.temp" every time, and renaming "$file.temp" to "$file" after every call, as with mv -- "$file.new" "$file".

As for the “bad flag in substitute command” error, that’s because the syntax sed '0,/foo/{s/foo/bar/}' (to replace the first occurrence only) is specific to GNU sed as well. We would need a replacement that works on both systems.

As for the removal of double qoutes around variables with strings, is that really necessary? Did you verify that it does not work without that (and only with the other solutions)?

Replacing mkdir -p with mkdir --parents – sure, that would be fine.

An alternative solution for (1) and (2) would be to install GNU sed on macOS, e.g. via Homebrew (brew install gnu-sed).

1+2: Completely OK with gnu-sed.
3: Just tested again after installing gnu-sed, no issues.
4. Yey!

authors: ocram piejanssens


text:
Set-OMETemplateNetwork not working

@TrevorSquillario - First sorry for the influx of issues, I have created. Its also totally possible I am doing something stupid...
"TEST_VLAN_11" | Get-OMENetwork

"TEST_TEMPLATE" | Get-OMETemplate

"TEST_TEMPLATE" | Get-OMETemplate | Get-OMETemplateNetwork

"TEST_TEMPLATE" | Get-OMETemplate | Set-OMETemplateNetwork -NICIdentifier "NIC in Mezzanine 1A" -Port 1 -TaggedNetworks $("TEST_VLAN_11" | Get-OMENetwork) -Verbose

"TEST_TEMPLATE" | Get-OMETemplate | Get-OMETemplateNetwork

if I then manually add "TEST_VLAN_11" to "Port 1" in the GUI
"TEST_TEMPLATE" | Get-OMETemplate | Get-OMETemplateNetwork

Just add the -Mode "Append" parameter. It was supposed to throw an error if you don't specify it, that wasn't working. I added a fix for it in future releases.

Thank you. Is it possible to pass two ports in the same command?

Technically yes but I'm going to leave it as separate commands for now. Could be a potential enhancement in the future.

repo: dell/OpenManage-PowerShell-Modules