Add business tax and additional breakouts to revenue decomposition

This PR adds business tax revenue changes and additional breakouts when decomposing the overall revenue effects measured in OG-USA in the output_tables.dynamic_revenue_decomposition() function.

@rickecon This PR is ready for review.

@rickecon This PR is ready for review.

Codecov Report

Merging #701 (6cf13ac) into master (4eeba92) will decrease coverage by 1.53%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #701      +/-   ##
==========================================
- Coverage   84.33%   82.80%   -1.54%
==========================================
  Files          23       23
  Lines        3907     3925      +18
==========================================
- Hits         3295     3250      -45
- Misses        612      675      +63

Flag
Coverage Δ

unittests
82.80% <100.00%> (-1.54%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

ogusa/output_tables.py
96.74% <100.00%> (+0.29%)
:arrow_up:

ogusa/TPI.py
75.07% <0.00%> (-19.88%)
:arrow_down:

Codecov Report

Merging #701 (6cf13ac) into master (4eeba92) will decrease coverage by 1.53%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #701      +/-   ##
==========================================
- Coverage   84.33%   82.80%   -1.54%
==========================================
  Files          23       23
  Lines        3907     3925      +18
==========================================
- Hits         3295     3250      -45
- Misses        612      675      +63

Flag
Coverage Δ

unittests
82.80% <100.00%> (-1.54%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

ogusa/output_tables.py
96.74% <100.00%> (+0.29%)
:arrow_up:

ogusa/TPI.py
75.07% <0.00%> (-19.88%)
:arrow_down:

@jdebacker. I can't figure out why the codecov/project is failing. In the details, it says that code coverage in TPI.py went down to 75% because of this PR. That doesn't make any sense to me.

@jdebacker. I can't figure out why the codecov/project is failing. In the details, it says that code coverage in TPI.py went down to 75% because of this PR. That doesn't make any sense to me.

@jdebacker . Do you care about updating the docstring in this branch's output_tables.py lines 445 to 461? This PR introduces an extra business tax line to the decomposition.

@jdebacker . Do you care about updating the docstring in this branch's output_tables.py lines 445 to 461? This PR introduces an extra business tax line to the decomposition.

@jdebacker. This looks different than I thought we discussed on the phone today. I thought we were going to do the following:

Series A: total tax revenue, baseline variables = [IIT, CIT, behavior, macro], reform variables = []
Series B: total tax revenue, baseline variables = [CIT, behavior, macro], reform variables = [IIT]
Series C: total tax revenue, baseline variables = [behavior, macro], reform variables = [IIT, CIT]
Series D: total tax revenue, baseline variables = [macro], reform variables = [IIT, CIT, behavior]
Series E: total tax revenue, baseline variables = [], reform variables = [IIT, CIT, behavior, macro]

We already have series A and E as the respective baseline and reform total tax revenue series. Having the three distinct artificial series B, C, and D, would allow us to have a decomposition table with the following lines.

IIT effect, B - A (holding CIT, behavior, and macro constant)
CIT effect, C - B (holding behavior and macro constant)
behavior effect, D - C (holding macro constant)
macro effect, E - D

I like the option of combining the IIT and CIT effects into one total tax effect, and I like Ben's idea of the option of combining the behavior and macro effects into one macro feedback effect. But my default would be this particular breakout with all four lines.
This is a matter of preference. I would love to get your thoughts.

@jdebacker. This looks different than I thought we discussed on the phone today. I thought we were going to do the following:

Series A: total tax revenue, baseline variables = [IIT, CIT, behavior, macro], reform variables = []
Series B: total tax revenue, baseline variables = [CIT, behavior, macro], reform variables = [IIT]
Series C: total tax revenue, baseline variables = [behavior, macro], reform variables = [IIT, CIT]
Series D: total tax revenue, baseline variables = [macro], reform variables = [IIT, CIT, behavior]
Series E: total tax revenue, baseline variables = [], reform variables = [IIT, CIT, behavior, macro]

We already have series A and E as the respective baseline and reform total tax revenue series. Having the three distinct artificial series B, C, and D, would allow us to have a decomposition table with the following lines.

IIT effect, B - A (holding CIT, behavior, and macro constant)
CIT effect, C - B (holding behavior and macro constant)
behavior effect, D - C (holding macro constant)
macro effect, E - D

I like the option of combining the IIT and CIT effects into one total tax effect, and I like Ben's idea of the option of combining the behavior and macro effects into one macro feedback effect. But my default would be this particular breakout with all four lines.
This is a matter of preference. I would love to get your thoughts.

@rickecon I don't know what's up with the code coverage either.  The test_TPI.py script is not affected here, so I don't know why there's not coverage of TPI.inner_loop, which was covered before.
Regarding you questions about decomposition.  You propose:

IIT effect, B - A (holding CIT, behavior, and macro constant)
CIT effect, C - B (holding behavior and macro constant)
behavior effect, D - C (holding macro constant)
macro effect, E - D

Note that CIT rate changes have no direct effect on the IIT+payroll tax revenue and IIT+payroll rate changes have no direct effect on CIT revenue.  So if you want those four changes you note above, you would look to the following rows from the table output (using the dynamic_revenue_decomposition function with the options include_business_tax=True and full_break_out=True):

IIT: Pct Change due to tax rates
CIT: Pct Change due to tax rates
All: Pct Change due to behavior
All: Pct Change due to macro

"All" referes to all taxes (CIT + IIT + payroll).  Additional detail is provided to allow one to see the behavioral/macro contributions to the IIT+payroll tax revenues and the CIT tax revenues separately, but all the splits you are asking about are there.

I like the option of combining the IIT and CIT effects into one total tax effect, and I like Ben's idea of the option of combining the behavior and macro effects into one macro feedback effect.

If one wants to lump the behavioral and macro effects together to get a total dynamic revenue effect, one can set the option full_break_out=False.  This then returns three items (optionally, three for each of individual, business, and all taxes if include_business_tax=True):

Static effect
Behavior + macro effect (aka dynamic effect - this is what Ben is looking for)
Total change in taxes (static + behavior + macro)

Let me know if you still think something is missing.  I've erred on the side of having more detail in the tables.  One can ignore certain rows if one wishes, but I think it's helpful as a diagnostic tool to separately see what is happening with different revenue sources.  I hope this hasn't caused confusion in reading the output.

@rickecon I don't know what's up with the code coverage either.  The test_TPI.py script is not affected here, so I don't know why there's not coverage of TPI.inner_loop, which was covered before.
Regarding you questions about decomposition.  You propose:

IIT effect, B - A (holding CIT, behavior, and macro constant)
CIT effect, C - B (holding behavior and macro constant)
behavior effect, D - C (holding macro constant)
macro effect, E - D

Note that CIT rate changes have no direct effect on the IIT+payroll tax revenue and IIT+payroll rate changes have no direct effect on CIT revenue.  So if you want those four changes you note above, you would look to the following rows from the table output (using the dynamic_revenue_decomposition function with the options include_business_tax=True and full_break_out=True):

IIT: Pct Change due to tax rates
CIT: Pct Change due to tax rates
All: Pct Change due to behavior
All: Pct Change due to macro

"All" referes to all taxes (CIT + IIT + payroll).  Additional detail is provided to allow one to see the behavioral/macro contributions to the IIT+payroll tax revenues and the CIT tax revenues separately, but all the splits you are asking about are there.

I like the option of combining the IIT and CIT effects into one total tax effect, and I like Ben's idea of the option of combining the behavior and macro effects into one macro feedback effect.

If one wants to lump the behavioral and macro effects together to get a total dynamic revenue effect, one can set the option full_break_out=False.  This then returns three items (optionally, three for each of individual, business, and all taxes if include_business_tax=True):

Static effect
Behavior + macro effect (aka dynamic effect - this is what Ben is looking for)
Total change in taxes (static + behavior + macro)

Let me know if you still think something is missing.  I've erred on the side of having more detail in the tables.  One can ignore certain rows if one wishes, but I think it's helpful as a diagnostic tool to separately see what is happening with different revenue sources.  I hope this hasn't caused confusion in reading the output.

@rickecon asks:

Do you care about updating the docstring in this branch's output_tables.py lines 445 to 461? This PR introduces an extra business tax line to the decomposition.

Good catch - just updated those to just generally refer to tax revenue since different sources can be accounted for now.

@rickecon asks:

Do you care about updating the docstring in this branch's output_tables.py lines 445 to 461? This PR introduces an extra business tax line to the decomposition.

Good catch - just updated those to just generally refer to tax revenue since different sources can be accounted for now.

@jdebacker LGTM.

@jdebacker LGTM.


JSC Always shows when all engines are untoggled

There is an issue currently where JSC experimental always shows when you untoggle all engines.
https://test262.fyi/#|

Already fixed, should work fine in next run (~tomorrow)


Livemarks does not parse isPermaLink=false

Add-on version
v2.7
Describe the bug
Livemarks does not parse "isPermaLink=false" which yields an invalid URL that leads to a 404
To Reproduce
Steps to reproduce the behavior:

Register a feed that uses the tag, for exemple the freefilesync.org feed
Open Livemarks and hover on an item's link

Notes:

The feed is deemed valid RSS by feedvalidator.org

Thanks for reporting! Seems like isPermaLink should be taken in account according to: https://validator.w3.org/feed/docs/rss2.html#ltguidgtSubelementOfLtitemgt
I'll make items like this redirect to https://<website-homepage>/?itemguid=<guid> (the ?itemguid=<guid> bit is so the read indicator would still work).


Support for cloud-init (custom-data) on the compute nodepool

Given the recent emphasis on SAS Workload Management for compute, could we get a way to inject a cloud-init script into the compute nodepool/vmss?  I am using hostPath for SASWORK, and the mounted NvME drive does not have the appropriate permissions/ownership by default.  Currently (with a fixed number of nodes in my compute nodepool) I have to execute a script after the node is instantiated to make that NvMe drive appropriate for SASWORK -- which works fine. In an autoscaling situation (for SAS WLM) I need to have that happen dynamically as kubernetes adds new compute nodes on its own.  I've seen some JIRAs about maybe creating a daemonset to handle this, but those appear to have gone nowhere to me.  The solution that I have found is to use the az vmss update --custom-data ./myscript.sh command to add my NvME reconfiguration script to the instance start up.  It would be nice if I could inject that from the get-go (in the IAC project) rather than having to figure out how to set the nodes up properly after-the-fact.

Opened internal ticket for PM review, PMCPFR-1534.

Thank you for your suggestion.  Unfortunately, the feature request PMCPFR-1534 was rejected due to security concerns.  Closing this issue as we will not proceed further.


chore: php7 and v2

Codecov Report

Merging #5 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master     #5   +/-   ##
=======================================
  Coverage       100%   100%
  Complexity       19     19
=======================================
  Files             5      5
  Lines            55     54    -1
=======================================
- Hits             55     54    -1

Impacted Files
Coverage Δ
Complexity Δ

src/AlgoliaSpecification/Registry.php
100% <100%> (ø)
3 <2> (ø)
:arrow_down:

.../AlgoliaSpecification/QueryFactory/AndXFactory.php
100% <100%> (ø)
3 <2> (ø)
:arrow_down:

src/AlgoliaSpecification/Handler.php
100% <100%> (ø)
3 <1> (ø)
:arrow_down:

...c/AlgoliaSpecification/QueryFactory/NotFactory.php
100% <100%> (ø)
7 <2> (ø)
:arrow_down:

...c/AlgoliaSpecification/QueryFactory/OrXFactory.php
100% <100%> (ø)
3 <2> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Add polyline

Description
ITK is missing support for PolyLine, which makes interoperability with VTK hard.
Expected behavior
Reading a .vtk file which contains PolyLines, and then immediately writing to a different file, should result in the file with the same content as the original.
Actual behavior
All PolyLines in the original file are chopped up into a sequence of Lines, thus losing connectivity information.
Additional Information
Steps:

Add itk::PolyLineCell class
Use it in mesh readers
Update relevant conversion classes in https://github.com/InsightSoftwareConsortium/ITKMeshToPolyData
Check whether anything else needs updating

@PranjalSahu will work on this.

Resolve via #3393


Implement AsFd and bidirectional conversion to/from OwnedFd

In particular, this makes it possible to get a BorrowedFd from an
Inotify, which allows integration with polling mechanisms that don't
use RawFd. This will be needed to work with the next version of
async-io.

Thank you for the pull request, @joshtriplett! This looks good, but CI fails because our MSRV is too low. I've opened #203.
I'll probably find some time to address this soon, but if anyone's reading this while I still haven't, feel free to jump in with a pull request! This PR is blocked until then.

This will be needed to work with the next version of async-io.

I assume this means you need me to publish a new release, once this is merged?

@hannobraun Right, this PR itself will raise the MSRV as well, for AsFd/BorrowedFd/OwnedFd.

@hannobraun I've updated this to also fix the MSRV and CI. 1.63, which has the I/O Safety types stabilized, will ship in the Debian stable release shipping in a few days.

Thank you, @joshtriplett! It would have been a bit nicer go have the MSRV bump in a separate pull request, so I don't get confused later when writing the changelog. But this works too!

And yes, I'd really appreciate a release with this change, once merged.

Understood. I'll try to get it out today.

New version is out: https://github.com/hannobraun/inotify-rs/pull/204, https://crates.io/crates/inotify/0.10.1

@hannobraun Thank you!


Change capitalization of 'More' in the 'More than 1 year ago' validation content, or change content to "Validated over a year ago"

Any message following the word 'Validated' should start with a lower case letter.
All other data labels seem OK, but the 'More than 1 year...' should read "Validated more than 1 year ago", or, preferably "Validated over a year ago"

 gogetta now says it was validated exactly a year ago so I have nothing to compare it to, I tried to find it by searching for pantries as they are the most outdated dataset; many of them are now indicating they were validated 2 months ago while, in fact, they might be 2 years old. For example:

There are now no instances of more than a year as we just say like in gogetta, 2 years ago 3 years ago and so on.

Additionally, all of the statements have double space after the word "Validated"
@adambard1 @jbeard4 This might be a high-priority issue, as I just proved we have a bug sharing misleading information about the recency of validation.


Wrong regexp ( only with !~ ) result in SHOW TAG VALUES

Bug report
System info:[InfluxDB 0.13.0, Centos 6.7]
SHOW TAG VALUES from <measurement_name> WITH KEY = "<key_name>" WHERE <key_name> !~ /<strig_to_exclude>/
The regexp works only if there are no match at all for the string you are trying to exclude

Duplicate of #6607.


KafkaHeaders.DLT_EXCEPTION_FQCN is always a KafkaListenerExecutionException

When using the dead letter recoverer, KafkaHeaders.DLT_EXCEPTION_FQCN is almost always a KafkaListenerExecutionException. This makes the header less helpful than it could be. Is there any way we can add a header for the cause of the exception?

This is a reasonable request; you can, however, see the cause in the stack trace header.


fix: bumps toml to tomllib for dumpers.Toml

Use tomllib from python standard library in python 3.11, fallback to tomli_w for older versions.

Codecov Report

Merging #53 (4fbef11) into main (3184a78) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #53   +/-   ##
=======================================
  Coverage   51.18%   51.18%
=======================================
  Files          20       20
  Lines         715      715
=======================================
  Hits          366      366
  Misses        349      349

Impacted Files
Coverage Δ

incipyt/_internal/dumpers.py
96.00% <100.00%> (ø)

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


JObject.Merge contract wrong

JObject.Merge expect only JObject as parameter
but has signature Merge(object)

Well, you are both wrong and yet kinda right.
The wrong bit first: JObject itself possesses no Merge method.
The Merge method is from JContainer, the base class for JObject (both the JObject documentation as well as Intellisense will tell you that). JContainer is also the base class for JArray -- and this is important to understand why the parameter type of the Merge method is not JObject. Because JArray accepts any kind of JToken enumerables (as long as each of these JTokens are either JValue, JObject, or JArray), such as JToken[] for example.
Still, in my personal opinion, your post has merit and has a point. Because it underscores the Merge method being a poorly designed API that invites misunderstandings and confusion, and also highlights the lack of documentation surrounding this method. A much better API design would be to implement the Merge method for each JObject and JArray with the matching parameter type respectively separately, either hiding/shadowing the underlying base JContainer.Merge method or getting rid of JContainer.Merge although (although the latter might break code that specifically calls Merge on JContainer references...)


⚠ Samsung has degraded performance

In 4e76641, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2966 ms

Resolved: Samsung performance has improved in 26bb002.


Announce page change using aria-live=assertive

#18

This looks good, but we've got some conflicts to resolve now.

I am a little bit lost, and first time I am doing this.


HIVE-16727: REPL DUMP for insert event should't fail if the table is already dropped.

Already merged to master.


Upgrade actions before Node 16 reaches end of life

GitHub support for Node 16 is coming to an end this spring (reference) and we've been receiving warning in our workflows about it. We should upgrade the action versions to use Node 20.
I gathered the following list of actions, but it may be incomplete:

actions/checkout@v3 to v4
actions/setup-python@v4 to v5
actions/cache@v3 to v4
peter-evans/find-comment@v2 to v3
peter-evans/create-or-update-comment@v3 to v4
<EMAIL_ADDRESS>(does not seem to have support yet)

Do we need to be using specific versions of the workflows, or could we specify @main and only pin to a specific version when necessary?


HMR not working when importing a library with embedded Vue

Vue version
3.2.45
Link to minimal reproduction
https://stackblitz.com/edit/vue-consume-vue-hmr?file=README.md
Steps to reproduce

Run the vue app with npm run dev
Edit content in src/components/HelloWorld.vue

What is expected?

Browser automatically shows updated content when a component is edited

What is actually happening?

Terminal output indicates that vite recognizes the changed module
Browser console output from vite indicates that the component was hot updated
No content changes are actually visible in the browser until manual reload

System Info
No response
Any additional comments?
I submit this as a Vue issue because the behavior of vite seems correct, from simple observation.
The usage of a library with embedded Vue is helpful for sharing a self-contained "black box" featureset without dependency or structural conflict for the consuming app.
Related resources for reproduction example
The library app is a minimal Vue 3 app, built with Vite in library mode, visible here:

https://github.com/abrbabey/sample-library-vue-app

I don't think you should package the vue code into your library because it will overwrite some of the global variables that vue needs to use.

I don't think you should package the vue code into your library because it will overwrite some of the global variables that vue needs to use.

@zhangzhonghe, thank you for the reply. It is true that removing vue from the library package will avoid this conflict, but that also greatly weakens my real use case for this library pattern.
Following Vue's goal of being flexible and incrementally adoptable, packaging vue within the library has allowed me to provide a rich Vue-developed featureset to several different consumers, ranging from unstructured legacy web apps to modern framework apps using various versions of Angular, React, and Vue (as examples). Aside from the broken HMR at development time when consumed by a Vue 3 app, the pattern works quite well!
The major benefit of the embedded vue is similar to the spirit of Embedded Web Components, where we want to "leverage Vue in a completely consumer-agnostic fashion". Because Vue is a very modern and fast-evolving framework (which I love), the ability to generate an insulated output module is quite valuable to ensure the library can be consumed by applications which are slow to upgrade or have conflicting Vue version dependencies for an extended time.
I think it makes sense for Vue as "The Progressive Framework" to avoid conflict with itself in this usage, and it seems very close to working already. Are there any mechanisms for protecting the global variables you mention from interference? Perhaps a configuration or transformation to be applied to Vue in the library code or its build process?

Are there any mechanisms for protecting the global variables you mention from interference? Perhaps a configuration or transformation to be applied to Vue in the library code or its build process?

You can change the vite.config.ts to this:
export default defineConfig(({ mode }) => {
    return {
        plugins: [vue()],
        build: {
            lib: {
                entry: resolve(__dirname, "src/lib.js"),
                name: "SampleLibraryVueApp",
                fileName: "library",
            },
        },
        // to replace the process.env.NODE_ENV in the vue library
        define: {
            'process.env.NODE_ENV': JSON.stringify(mode)
        }
    };
});

This will ensure that the tree shakes off HMR-related code during build time. It might solve your problem.

This will ensure that the tree shakes off HMR-related code during build time. It might solve your problem.

I started thinking in this direction after your first comment, and a fresh skim of the code led me to one portion of global HMR registration in Vue's runtime-core/src/hmr.ts which looks like this:
if (__DEV__) {
  getGlobalThis().__VUE_HMR_RUNTIME__ = {
    // ... removed for brevity
  }
}

An inspection of my library's build output shows that __DEV__ is translated into process.env.NODE_ENV !== 'production', so it makes sense that this behavior is active when my consuming application is running on development server.
I don't know where exactly this __DEV__ replacement happens, but the result is clear enough to identify the issue as a mistake in my configuration of Vite rather than an issue with Vue (in fact, there are comments in the Vue code explaining the intent of the __DEV__ check to support proper tree-shaking at build time).
For my consumer-agnostic use case, I want my library to build in a production-like manner, without including any dynamic dev-time hooks, so I believe this resolution strategy is sound.
Your example modification of the vite.config.ts looks like a nice solution. I should have some time to try this soon, and I will report back here for documentation purposes and close my issue if it is successful.
Thank you again for taking the time to look, I appreciate the help and thoughtful response.

The recommended change in vite.config.ts worked to prevent my library from interfering with the consuming app's HMR operations. This makes my library build output closer to a production-like artifact, as I intended.
Thank you @zhangzhonghe, I am closing this issue!


Make npm start install the dependencies

typings install is setup to be a post install script so this will
install all the dependenies

I originally had this but it turned out to be too much magic for some developers and is also a problem with ci environments

I don't like it either.

I'm going to close this but if you like you can make a section in the read called extending or something for how people can expand upon the starter


feat(detection_area)!: sync latest feature

Description
This PR suppress abort behavior after departing the stop line
This PR is hand-made cherry-pick of the following PRs.
https://github.com/autowarefoundation/autoware.universe/pull/3114
https://github.com/autowarefoundation/autoware.universe/pull/9255
Related links
Parent Issue:

Link

How was this PR tested?
Test criteria: https://docs.google.com/presentation/d/1_OSWKhMmRUf1QYhQGOVd9jnOLOWl8S7rGE-5VcO04zk/edit#slide=id.g315595f3e6d_0_12942
Test results: https://tier4.atlassian.net/browse/AEAP-1903?focusedCommentId=194502
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.

Please add the following to 'How was this PR tested?' section
(This is to ensure that test perspectives and results can be tracked in the commit):

Test criteria: https://docs.google.com/presentation/d/1_OSWKhMmRUf1QYhQGOVd9jnOLOWl8S7rGE-5VcO04zk/edit#slide=id.g315595f3e6d_0_12942
Test results: https://tier4.atlassian.net/browse/AEAP-1903?focusedCommentId=194502

@yuki-takagi-66

The basic design document clearly states that "please consider the detailed design," but this PR makes no mention of the detailed design.
Could you attach the detailed design to the PR?
Or, if you have decided that implementing it as per the basic design document is fine, please state that in the Description field.

Please justify all changes in the PR (show that the changes are necessary and sufficient).
In the "Description" field, clearly list the features and clarify how they correspond to the implementation.

In the "How was this PR tested?" field, please include not only the URL, but also a summary of the results and your judgement as the PR submitter as to whether the changes to this PR are appropriate.


⚠ Bofrost.be has degraded performance

In b6bbc39, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1319 ms

Resolved: Bofrost.be performance has improved in 39d7545 after 6 minutes.


Closes #132 #136 #138 #139 Re-vamp of the pharmaverse blog

Closes #132
Closes #136
Closes #138
Closes #139
Thank you for your Pull Request! We have developed this task checklist to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your blog post.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

[ ] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update), and make sure the corresponding issue is linked in the Development section on the right hand side
[ ] Run the script from CICD.R line by line to first check the spelling in your post and then to make sure your code is compatible with our code-style. Address any incongruences by following the instructions in the file!
[ ] Choose (possibly several) tag(s) or categories from the current list: c("metadata", "submission", "qc", "ADaMs", "SDTMs", "community", "conferences", "admiral", "roak", "xportr", "metatools", "metacore") for your blog post. If you cannot find anything that fits your blog post, add your own tag! We occasionally tidy up all tags for consistency.
[ ] Blog post is short, personalized, reproducible and readable
[ ] Add a disclaimer at the top of your post, if appropriate (example: Disclaimer
This blog contains opinions that are of the authors alone and do not necessarily reflect the strategy of their respective organizations.)
[ ] Address all merge conflicts and resolve appropriately
[ ] Assign two of us (@bms63, @manciniedoardo, @StefanThoma, @kaz462) as reviewers in the PR.
[ ] Pat yourself on the back for a job well done! Much love to your accomplishment!

Hi all, I did a bunch of updates in this PR to re-vamp our blog:

I made a hex for the pharmaverseblog and saved it in the media folder. This hex now appears in the tab image, in our README and at the top of the blog header

I changed the header colours to match the pharmaverse palette. I removed dark mode as I couldn't get it to work and it looked pretty bad anyway.
I made the (non)capitalisation of "pharmaverse" consistent across all posts
I slimmed down the list of categories to the following, and recategorised all posts:

TLGs
ADaM
SDTM
Shiny
Community
Conferences
Submissions
Metadata
Technical

I resized any images that were too big for the blog preview so they all look nicer now
I wrote descriptions so that every post now has one.

This image is missing

Such a nice touch!!

This image is missing

Yeah I'm having some issues getting it to display... thought it maybe was just on my side, any ideas?

This image is missing

Yeah I'm having some issues getting it to display... thought it maybe was just on my side, any ideas?

it is missing the contributiors.png file in the post

This image is missing

Yeah I'm having some issues getting it to display... thought it maybe was just on my side, any ideas?

it is missing the contributiors.png file in the post

can you see it now? because even though i added it, it's still not rendering for me (same with some of the pharmaverse posts, see image below)

@manciniedoardo this is really Nice!! I think I might have found a few more places where pharmaverse is in propcase, should they also be in all lowercase

I have also found cases where pharmaverse is all capitalized but this might be a bit tricky since some times the upper case pharmaverse is part of the title for that talk the author referred to and other times it's not. Should the instances where it's the author referring to pharmaverse also be consistent (all lower case)

Thanks, looks like I missed some, although some of the ones on there are part of capitalised titles or the first word in a sentence, so I left them alone.

I have now addressed the others that needed changing.


BUG in API <IP_ADDRESS>80 - Object reference not set to an instance of an object

Hi,
In API <IP_ADDRESS>80 we can't generate ideacon file by IOM.
In 23.1 version everything is ok.
bug.zip
Best regards
Witek

@rewiteq, apologies for this inconvenience. We are aware of this and will be fixed in the next patch which has been brought forward to the end of this week.
Cheers
Nathan

I have the same problem :-(

work w <IP_ADDRESS>3


[CHALLENGE SUBMISSION]

Please provide the following information for your submission:
What is your name? (First, Last)
Drew Skwiers-Koballa
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/dzsquared/25-days-of-serverless-day3
What Challenge is this for? (Challenge number between 1 and 25)
3
(Optional) Anything else we should know? e.g., language used, location, blog post?
C# in Azure Function and Azure SQL, https://www.drewsk.tech/2019/12/03/25-days-of-serverless-day-3/

THANK YOU FOR YOUR #25DaysOfServerless SUBMISSION
We checked out your repository. We're thrilled to say your solution is now listed in our Hall of Fame
Thank you for your contributions!
This issue is now resolved! 🎉


Margin calculation & refactoring

Sry, should have cut more contained commits, will see to do that next time 😬
The buy margin is calculated from initial_price, quantity and leverage.
The sell margin is calculated from initial_price and quantity (no leverage trading for the seller at the moment).
Includes several refactors:

Separate API interface for Cfd and CfdOffer when mapping toSseEvent. This allows internal modelling to be different than the exposed API.

Remove the profit calculation internally, it is only relevant on the UI feed API level.
Move code that is specific to taker/maker http API from model to the respective routes module.

Some simplification of the calculation model of Usd (could be further improved by deriving calculation traits)

Just noticed that the UI integration is not complete, still have to add the margin into the taker's buy view and trigger re-calculation upon quantity change.

I'll squash and rebase this work and then see to get it merged :)


Determine bridge and container network interface requirements

In certain types of deployment (e.g. CNI) weave will not be in charge of creating bridge devices and container network interfaces. An analysis of weave must be performed to identify specific problems and document them as issues for resolution.

[ ] #1255 - Don't rely on disabling TSO

I think when this was filed the thinking was that we could piggy-back on the CNI 'bridge' plugin.  Since then we have implemented our own Weave Net CNI plugin which does create and set up veths.
We tell people to use this after calling weave launch, which will create the bridge, so that part of the premise also bears re-considering.

Closing: it's been a long time since anyone asked about working with an existing bridge.


Installation of git.install fails

(git.install) Installation fails
Expected Behavior
Installation works without issues
Current Behavior
Installer script does not find Commandlets from chocolatey-core

ERROR: The term 'Get-AppInstallLocation' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
git.install can be automatically uninstalled.

Steps to Reproduce (for bugs)
choco install -y -v git.install
Context
Same is true for other packages (e.g. yed)
Your Environment

Package Version used: chocolatey-core.extension 1.3.3
Operating System and version: Windows Server 2019 Std
Chocolatey version: 0.10.7
Install/uninstall gist: https://gist.github.com/I-R/e9a85e79ddc75f7b214a85469982c201

Sounds like you have a rogue package library directory in the lib folder.
Look in the directory %ChocolateyInstall%\lib to see if there are any similarly named directories (only difference being that one have a version number, and another don't).
We you got any directories like that, try deleting the one with the version number (remember to back up the directory first, just in case), and then try installing git.install again. (I am actually assuming there is a directory called chocolatey-core.extension and chocolatey-core.extension.1.3.3, or something similar).
NOTE: The variable %ChocolateyInstall% is the install location of the chocolatey program, typically C:\ProgramData\Chocolatey.

Hey,
thanks for that. I only had the folder chocolatey-core.extension.1.3.3. After moving that away, installation of yed and git worked!
Just to be save - i also see folders:
PS C:\ProgramData\chocolatey\lib> ls .\chocolatey
Verzeichnis: C:\ProgramData\chocolatey\lib\chocolatey

Mode                LastWriteTime         Length Name

-a----       21.10.2019     12:36        4067171 chocolatey.nupkg
PS C:\ProgramData\chocolatey\lib> ls .\chocolatey.0.10.15\
Verzeichnis: C:\ProgramData\chocolatey\lib\chocolatey.0.10.15

Mode                LastWriteTime         Length Name

d-----       21.10.2019     14:34                tools
-a----       21.10.2019     14:33        4067171 chocolatey.0.10.15.nupkg
is that correct?

Hello,
I am also experiencing similar issues.
I have already uninstalled (removed choco's install folder) and reinstalled but it didn't help.
Windows 7 Pro (Spanish ISO).
Any help will be greatly appreciated.
C:\ProgramData\chocolatey>choco install git --force -y
Chocolatey v0.10.15
Installing the following packages:
git
By installing you accept licenses for the packages.
git v2.24.0 already installed. Forcing reinstall of version '2.24.0'.
Please use upgrade if you meant to upgrade to a new version.
Progress: Downloading git 2.24.0... 100%
chocolatey-core.extension v1.3.4 (forced) [Approved]
chocolatey-core.extension package files install completed. Performing other installation steps.
Installed/updated chocolatey-core extensions.
The install of chocolatey-core.extension was successful.
Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-core'
git.install v2.24.0 (forced) [Approved]
git.install package files install completed. Performing other installation steps.
You must provide a value expression on the right-hand side of the '-' operator.
The specified module 'C:\ProgramData\chocolatey\extensions\chocolatey-core\chocolatey-core.psm1' was not loaded because
no valid module file was found in any module directory.
Using Git LFS
Installing 64-bit git.install...
git.install has been installed.
ERROR: The term 'Get-AppInstallLocation' is not recognized as the name of a cmdlet, function, script file, or operable p
rogram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
The install of git.install was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\git.install\tools\chocolateyInstall.ps1'.
See log for details.
git v2.24.0 (forced) [Approved]
git package files install completed. Performing other installation steps.
The install of git was successful.
Software install location not explicitly set, could be in package or
default install location if installer.
Chocolatey installed 2/3 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures

git.install (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\git.install\tools\chocolateyInstall.ps1'
.
See log for details.

Well,
for me the suggested solution worked. I am no expert in that, i only did, what had been suggested and deleted the folder chocolatey-core.extension.1.3.3 and did a choco install -y git.

Well,
for me the suggested solution worked. I am no expert in that, i only did, what had been suggested and deleted the folder chocolatey-core.extension.1.3.3 and did a choco install -y git.

I see.
Well, that didn't work for me.
And I even went as further as completely removing chocolatey from my computer and that didn't work as well, hence why I decided to post here for help...

I don't think our issue is related. So I decided to open a new issue and will take it from there.


Active Button Highlight Stuck on Home Button in Navbar Despite Navigation

Description:
In the navigation bar, there are buttons such as Home, About, Category, Team, Page, and Contact. Each button is expected to highlight when clicked to indicate the active page. However, the highlight (active state) remains on the Home button even when navigating to other pages.
Expected Behavior:
The button corresponding to the active page should be highlighted, and the highlight should switch as the user navigates between pages.
Actual Behavior:
The highlight (active state) is stuck on the Home button, even after navigating to a different page.
Before:

AFTER:

Additional Information:
Ensure that the active state correctly switches to the current page’s button when navigating. This might require adjustments to the CSS or JavaScript handling the active class.
If you assigned this issue to me under gssoc'24-extd, I can fixed it.

@Hamza20203064 Issue acknowledged! you are going to be assigned

im interested please assign me, ill share my proposed solution as soon as u ping me

Hey @Hamza20203064, it's been 2 days, and you haven't responded, so I have to reassign this. Please don't be discouraged. I will assign this to @lakshyeahh. Please create a PR as soon as possible and let me know when you start working on it.

@mdazfar2 please give me 24 hour I will pull the request within 24 hour. This is my request.

Sir can i also work along side?

Right on it sir.

@mdazfar2 had created the pull request. Please review and accept the pull request

@Hamza20203064 please update the sync fork and let me know.

@mdazfar2 I updated the sync, if there is any issue let me know

@mdazfar2 I updated the sync, if there is any issue let me know

@Hamza20203064 The login/signup page opens only from the homepage and does not open from any other page. Hope you understand. If you want to work on it, kindly create an issue and PR. Thank you!

Yeah, sure, I can do that. Please assign it to me.
On Fri, 4 Oct 2024 at 08:38, Md Azfar Alam @.***> wrote:

@mdazfar2 https://github.com/mdazfar2 I updated the sync, if there is
any issue let me know
@Hamza20203064 https://github.com/Hamza20203064 The login/signup page
opens only from the homepage and does not open from any other page. Hope
you understand. If you want to work on it, kindly create an issue and PR.
Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/mdazfar2/Ezyshop/issues/13#issuecomment-2392709111,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASYQ4NDJIPTT6DNLCGR7UHDZZYBETAVCNFSM6AAAAABPF4MEXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJSG4YDSMJRGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


update compose, remove useless bash and improve tests

Signed-off-by: Victor Vieux<EMAIL_ADDRESS>

Let's retry test on master.
not ok 154 docker volume rm
# (from function `docker' in file api/../helpers.bash, line 42,
#  from function `docker_swarm' in file api/../helpers.bash, line 53,
#  in test file api/volume.bats, line 88)
#   `docker_swarm rm test_container' failed
...
# time="2016-04-14T21:33:57Z" level=debug msg="HTTP request received" method=DELETE uri="/v1.24/volumes/node-1/5472c846c475a45cb2091fa6023f143635f64619dc0e387b6ab968b6ebb33d6c"
# time="2016-04-14T21:33:57Z" level=error msg="HTTP error: node-1: Error response from daemon: Unable to remove volume, volume still in use: remove 5472c846c475a45cb2091fa6023f143635f64619dc0e387b6ab968b6ebb33d6c: volume is in use - [25657b9a93051e1314f9ff7285f55e77d04a3841075825700eb3f72b7d75d951]" status=500
# time="2016-04-14T21:33:57Z" level=debug msg="HTTP request received" method=DELETE uri="/v1.24/containers/test_container"
# time="2016-04-14T21:33:57Z" level=error msg="HTTP error: 409 Conflict: You cannot remove a running container 25657b9a93051e1314f9ff7285f55e77d04a3841075825700eb3f72b7d75d951. Stop the container before attempting removal or use -f\n" status=500

@dongluochen isn't is related to https://github.com/docker/swarm/pull/2116 ?

@vieux It looks like so.

@dongluochen @nishanttotla PTAL

LGTM

Did top change the default format recently?

@MHBauer it's using the host's top, the test now works with more base images

LGTM


Possible regression: Connection to libvirt via SSH fails with provider version 0.6.14

This is maybe related to #864
This looks like a regression introduced in 0.6.14

System Information
Linux distribution
Terraform is running on MacOS 12.3
Libvirt is running on Red Hat Enterprise Linux Server release 7.9 (Maipo)
Terraform version
$ terraform -v
Terraform v1.1.7
on darwin_amd64
+ provider registry.terraform.io/dmacvicar/libvirt v0.6.14
+ provider registry.terraform.io/hashicorp/template v2.2.0

Description of Issue/Question
Setup
This is the .tf i use:
terraform {
  required_version = ">= 0.13"
  required_providers {
    libvirt = {
      source  = "dmacvicar/libvirt"
      version = "=0.6.13"
    }
  }
}

provider "libvirt" {
  uri = "qemu+ssh://ansible@zzzzzz/system?keyfile=/Users/xxxxxx/.ssh/id_rsa"
}

module "vm" {
  source  = "MonolithProjects/vm/libvirt"
  version = "1.9.0"

  vm_hostname_prefix = "server"
  vm_count           = 3
  memory             = "2048"
  vcpu               = 1
  pool               = "terra_pool"
  system_volume      = 20
  dhcp               = true
  local_admin        = "local-admin"
  ssh_admin          = "ci-user"
  ssh_private_key    = "~/.ssh/id_rsa"
  local_admin_passwd = "$6$rounds=4096$xxxxxxxxHASHEDxxxPASSWORD"
  ssh_keys = [
    "ssh-rsa AAAAB3NzaC1yxxxxxxxxJ68xkHrWxiQ== xxxxx@yyyyy",
  ]
  time_zone  = "CEST"
  os_img_url = "http://mirror.chpc.utah.edu/pub/almalinux/8/cloud/x86_64/images/AlmaLinux-8-GenericCloud-latest.x86_64.qcow2"
}

output "ip_addresses" {
  value = module.vm
}

Steps to Reproduce Issue
If I specify version = "=0.6.13" in above Terraform file, it works:
$ terraform init -upgrade; terraform plan -out=out.plan
Upgrading modules...
Downloading registry.terraform.io/MonolithProjects/vm/libvirt 1.9.0 for vm...
- vm in .terraform/modules/vm

Initializing the backend...

Initializing provider plugins...
- Finding dmacvicar/libvirt versions matching ">= 0.6.9, 0.6.13"...
- Finding latest version of hashicorp/template...
- Installing dmacvicar/libvirt v0.6.13...
- Installed dmacvicar/libvirt v0.6.13 (self-signed, key ID 96B1FE1A8D4E1EAB)
- Using previously-installed hashicorp/template v2.2.0

(...)

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # module.vm.libvirt_cloudinit_disk.commoninit[0] will be created
  + resource "libvirt_cloudinit_disk" "commoninit" {
      + id             = (known after apply)
      + name           = "server_init01.iso"
(...)

If I change it to version = "=0.6.14" it fails:
$ terraform init -upgrade; terraform plan -out=out.plan
Upgrading modules...
Downloading registry.terraform.io/MonolithProjects/vm/libvirt 1.9.0 for vm...
- vm in .terraform/modules/vm

Initializing the backend...

Initializing provider plugins...
- Finding dmacvicar/libvirt versions matching ">= 0.6.9, 0.6.14"...
- Finding latest version of hashicorp/template...
- Installing dmacvicar/libvirt v0.6.14...
- Installed dmacvicar/libvirt v0.6.14 (self-signed, key ID 96B1FE1A8D4E1EAB)
- Using previously-installed hashicorp/template v2.2.0

(...)
╷
│ Error: failed to dial libvirt: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
│
│   with provider["registry.terraform.io/dmacvicar/libvirt"],
│   on test.tf line 11, in provider "libvirt":
│   11: provider "libvirt" {
│
╵

I was thinking I'm affected by this issue too, however in my case locking the version to an older one does not fix it. After more testing on the current release version I found that using:
qemu+ssh://{USER}@{IP}/system?keyfile={keyPath}&sshauth=privkey

Note it needed to have sshauth=privkey otherwise would fail.

Hello, no fixed this problem?

@tiknick - you may want to try debugging the client and server side configs. As noted if you are using ssh keys you should try adding &sshauth=privkey. Or potentially you may even need to add &no_verify=1 too. While attempting to run the terraform plan you should consider SSHing into the target system and watching the system logs. Potentially you could find an error on the server that could give insight.

Error from remote server in /var/log/secure:
sshd[17513]: Connection closed by <host_IP> port 46874 [preauth].
Port number changes with each new connection in the logfile.

@tiknick - That's really odd but unfortunately there's not enough info for me to go off of to help more. It sounds as though you've tried a lot more things already so any more suggestions will probably just overlap with things you attempted. Nothing more about what you've shared here.
The only remaining bits of advice that stick out are:

Verify the SSH key (public and private) file permissions are correct (644 for public, 600 for private)
Review the SSHD configs on the server you're trying to reach - maybe something will stand out. (though if it work swith normal SSH it's a shot in the dark)

Based on the logs you found on the server it's not even getting an auth from the client - that's generally what that line means. As it's saying it was still in preauth meaning the connection was closed before the client even sent an auth attempt. That's kinda why I'm wondering about SSH key perms - maybe terraform isn't accessing the key and sending the auth.
Given that this seems just as likely to be a terraform/client bug as potential to be a server bug, you may want to consider trying to capture more logging on the terraform side too. You can follow this resource: https://www.terraform.io/internals/debugging To try and enable more logging on your client before attempting further debugging. I'd suspect these logs could lead you to find more areas to investigate.

@mallardduck thank you for your answer.
Host - ubuntu 22.04
Remote_server - centos 7
SSH key generate is default and correct privileges.
Virsh by terminal is work: virsh -> then "connect qemu+ssh://root@<remote_server>/system" -> then "list" and i see all virtual mashines on remote server.
And I use Virtual Machine Manager with this link for connect to remote_server.
And if I want go to remote server via SSH, i use standart SSH-connect: ssh root@<remote_server> without problem.
`Terraform v1.2.5
on linux_amd64

provider registry.terraform.io/dmacvicar/libvirt v0.6.14
provider registry.terraform.io/hashicorp/template v2.2.0`

Just curious, but does it work with:

provider registry.terraform.io/dmacvicar/libvirt v0.6.13

Because in my case, the exact same config and tf works with v0.6.13, but
not v0.6.14.
On Fri, Jul 22, 2022 at 08:01 tiknick @.***> wrote:

@mallardduck https://github.com/mallardduck thank you for your answer.
Host - ubuntu 22.04
Remote_server - centos 7
SSH key generate is default and correct privileges.
Virsh by terminal is work: virsh -> then "connect qemu+ssh://root@<remote_server>/system"
-> then "list" and i see all virtual mashines on remote server.
And I use Virtual Machine Manager with this link for connect to
remote_server.
And if I want go to remote server via SSH, i use standart SSH-connect: ssh
root@<remote_server> without problem.
`Terraform v1.2.5
on linux_amd64

provider registry.terraform.io/dmacvicar/libvirt v0.6.14
provider registry.terraform.io/hashicorp/template v2.2.0`

—
Reply to this email directly, view it on GitHub
https://github.com/dmacvicar/terraform-provider-libvirt/issues/939#issuecomment-1192607481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZNOK6MVXZGSEZ3KFS3UZYLVVKSUHANCNFSM5SBI7GMA
.
You are receiving this because you commented.Message ID:
@.***>

--
Kind regards,
Jordan
--
Jordan Olin
Senior Solution Engineer
508-982-4872
...It’s all connected

Just curious, but does it work with: - provider registry.terraform.io/dmacvicar/libvirt v0.6.13 Because in my case, the exact same config and tf works with v0.6.13, but not v0.6.14.
On Fri, Jul 22, 2022 at 08:01 tiknick @.> wrote: @mallardduck https://github.com/mallardduck thank you for your answer. Host - ubuntu 22.04 Remote_server - centos 7 SSH key generate is default and correct privileges. Virsh by terminal is work: virsh -> then "connect qemu+ssh://root@<remote_server>/system" -> then "list" and i see all virtual mashines on remote server. And I use Virtual Machine Manager with this link for connect to remote_server. And if I want go to remote server via SSH, i use standart SSH-connect: ssh root@<remote_server> without problem. Terraform v1.2.5 on linux_amd64 - provider registry.terraform.io/dmacvicar/libvirt v0.6.14 - provider registry.terraform.io/hashicorp/template v2.2.0 — Reply to this email directly, view it on GitHub <#939 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZNOK6MVXZGSEZ3KFS3UZYLVVKSUHANCNFSM5SBI7GMA . You are receiving this because you commented.Message ID: @.>
-- Kind regards, Jordan
…
-- Jordan Olin Senior Solution Engineer<PHONE_NUMBER> ...It’s all connected

It's didn't work on 0.6.9-pre3, 0.6.10-0.6.14. :(

TF_LOG=debug terraform apply  2022-07-22T17:09:31.830+0300 [INFO]  Terraform version: 1.2.5 2022-07-22T17:09:31.830+0300 [DEBUG] using github.com/hashicorp/go-tfe v1.0.0 2022-07-22T17:09:31.830+0300 [DEBUG] using github.com/hashicorp/hcl/v2 v2.12.0 2022-07-22T17:09:31.830+0300 [DEBUG] using github.com/hashicorp/terraform-config-inspect v0.0.0-20210209133302-4fd17a0faac2 2022-07-22T17:09:31.830+0300 [DEBUG] using github.com/hashicorp/terraform-svchost v0.0.0-20200729002733-f050f53b9734 2022-07-22T17:09:31.830+0300 [DEBUG] using github.com/zclconf/go-cty v1.10.0 2022-07-22T17:09:31.830+0300 [INFO]  Go runtime version: go1.18.1 2022-07-22T17:09:31.830+0300 [INFO]  CLI args: []string{"terraform", "apply"} 2022-07-22T17:09:31.830+0300 [DEBUG] Attempting to open CLI config file: /home/nikita/.terraformrc 2022-07-22T17:09:31.830+0300 [DEBUG] File doesn't exist, but doesn't need to.  2022-07-22T17:09:31.930+0300 [DEBUG] checking for provisioner in "/usr/local/bin" 2022-07-22T17:09:31.930+0300 [INFO]  backend/local: starting Apply operation 2022-07-22T17:09:31.931+0300 [DEBUG] created provider logger: level=debug 2022-07-22T17:09:31.931+0300 [INFO]  provider: configuring client automatic mTLS 2022-07-22T17:09:31.948+0300 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 args=[.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14] 2022-07-22T17:09:31.948+0300 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 pid=52479 2022-07-22T17:09:31.948+0300 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 2022-07-22T17:09:31.953+0300 [INFO]  provider.terraform-provider-libvirt_v0.6.14: configuring server automatic mTLS: timestamp=2022-07-22T17:09:31.953+0300 2022-07-22T17:09:31.961+0300 [DEBUG] provider.terraform-provider-libvirt_v0.6.14: plugin address: address=/tmp/plugin824496895 network=unix timestamp=2022-07-22T17:09:31.961+0300 2022-07-22T17:09:31.961+0300 [DEBUG] provider: using plugin: version=5 2022-07-22T17:09:31.983+0300 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unimplemented desc = unknown service plugin.GRPCStdio" 2022-07-22T17:09:31.983+0300 [DEBUG] No provider meta schema returned 2022-07-22T17:09:31.985+0300 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 pid=52479 2022-07-22T17:09:31.985+0300 [DEBUG] provider: plugin exited 2022-07-22T17:09:31.985+0300 [DEBUG] created provider logger: level=debug 2022-07-22T17:09:31.985+0300 [INFO]  provider: configuring client automatic mTLS 2022-07-22T17:09:32.003+0300 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 args=[.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4] 2022-07-22T17:09:32.005+0300 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 pid=52491 2022-07-22T17:09:32.005+0300 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 2022-07-22T17:09:32.009+0300 [INFO]  provider.terraform-provider-template_v2.2.0_x4: configuring server automatic mTLS: timestamp=2022-07-22T17:09:32.009+0300 2022-07-22T17:09:32.035+0300 [DEBUG] provider.terraform-provider-template_v2.2.0_x4: plugin address: address=/tmp/plugin930588629 network=unix timestamp=2022-07-22T17:09:32.035+0300 2022-07-22T17:09:32.035+0300 [DEBUG] provider: using plugin: version=5 2022-07-22T17:09:32.078+0300 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unimplemented desc = unknown service plugin.GRPCStdio" 2022-07-22T17:09:32.078+0300 [DEBUG] No provider meta schema returned 2022-07-22T17:09:32.080+0300 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 pid=52491 2022-07-22T17:09:32.080+0300 [DEBUG] provider: plugin exited 2022-07-22T17:09:32.080+0300 [DEBUG] Building and walking validate graph 2022-07-22T17:09:32.081+0300 [DEBUG] adding implicit provider configuration provider["registry.terraform.io/hashicorp/template"], implied first by data.template_file.user_data_master1 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "libvirt_volume.vm_worker1" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "libvirt_volume.vm_worker2" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "libvirt_cloudinit_disk.cloudinit_worker1" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "libvirt_volume.vm_master1" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "libvirt_domain.worker1" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "libvirt_network.kvm_kube_net" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "libvirt_volume.os_image_ubuntu_master" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "data.template_file.user_data_worker2" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/hashicorp/template"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "libvirt_domain.worker2" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "data.template_file.user_data_master1" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/hashicorp/template"] 2022-07-22T17:09:32.081+0300 [DEBUG] ProviderTransformer: "libvirt_cloudinit_disk.cloudinit_worker2" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.082+0300 [DEBUG] ProviderTransformer: "libvirt_pool.pool_k8s" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.082+0300 [DEBUG] ProviderTransformer: "data.template_file.user_data_worker1" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/hashicorp/template"] 2022-07-22T17:09:32.082+0300 [DEBUG] ProviderTransformer: "libvirt_volume.os_image_ubuntu_worker" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.082+0300 [DEBUG] ProviderTransformer: "libvirt_domain.master1" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.082+0300 [DEBUG] ProviderTransformer: "libvirt_cloudinit_disk.cloudinit_master1" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.082+0300 [INFO]  ReferenceTransformer: reference not found: "path.module" 2022-07-22T17:09:32.082+0300 [DEBUG] ReferenceTransformer: "data.template_file.user_data_worker1" references: [var.VM_USER] 2022-07-22T17:09:32.082+0300 [DEBUG] ReferenceTransformer: "libvirt_domain.worker2" references: [libvirt_cloudinit_disk.cloudinit_worker2 var.VM_HOSTNAME_WORKER_2 var.VM_IP_ADDRESS_WORKER_2 libvirt_network.kvm_kube_net libvirt_network.kvm_kube_net libvirt_volume.vm_worker2] 2022-07-22T17:09:32.082+0300 [DEBUG] ReferenceTransformer: "libvirt_domain.worker1" references: [var.VM_HOSTNAME_WORKER_1 libvirt_cloudinit_disk.cloudinit_worker1 var.VM_IP_ADDRESS_WORKER_1 libvirt_network.kvm_kube_net libvirt_network.kvm_kube_net libvirt_volume.vm_worker1] 2022-07-22T17:09:32.082+0300 [DEBUG] ReferenceTransformer: "libvirt_network.kvm_kube_net" references: [var.VM_CIDR_RANGE] 2022-07-22T17:09:32.083+0300 [INFO]  ReferenceTransformer: reference not found: "path.module" 2022-07-22T17:09:32.083+0300 [DEBUG] ReferenceTransformer: "data.template_file.user_data_master1" references: [var.VM_USER] 2022-07-22T17:09:32.083+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.os_image_ubuntu_master" references: [libvirt_pool.pool_k8s var.VM_IMG_URL] 2022-07-22T17:09:32.083+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.os_image_ubuntu_worker" references: [var.VM_IMG_URL libvirt_pool.pool_k8s] 2022-07-22T17:09:32.083+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.vm_worker1" references: [var.VM_IMG_FORMAT libvirt_pool.pool_k8s libvirt_volume.os_image_ubuntu_worker var.VM_HOSTNAME_WORKER_1 var.VM_IMG_FORMAT] 2022-07-22T17:09:32.083+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.vm_worker2" references: [libvirt_pool.pool_k8s libvirt_volume.os_image_ubuntu_worker var.VM_HOSTNAME_WORKER_2 var.VM_IMG_FORMAT var.VM_IMG_FORMAT] 2022-07-22T17:09:32.083+0300 [DEBUG] ReferenceTransformer: "var.VM_IP_ADDRESS_WORKER_2" references: [] 2022-07-22T17:09:32.083+0300 [DEBUG] ReferenceTransformer: "output.ip_config_worker2" references: [libvirt_domain.worker2] 2022-07-22T17:09:32.084+0300 [DEBUG] ReferenceTransformer: "var.VM_IP_ADDRESS_WORKER_1" references: [] 2022-07-22T17:09:32.084+0300 [DEBUG] ReferenceTransformer: "provider[\"registry.terraform.io/dmacvicar/libvirt\"]" references: [] 2022-07-22T17:09:32.084+0300 [DEBUG] ReferenceTransformer: "libvirt_domain.master1" references: [libvirt_cloudinit_disk.cloudinit_master1 var.VM_HOSTNAME_MASTER_1 libvirt_network.kvm_kube_net libvirt_network.kvm_kube_net var.VM_IP_ADDRESS_MASTER_1 libvirt_volume.vm_master1] 2022-07-22T17:09:32.085+0300 [DEBUG] ReferenceTransformer: "var.VM_HOSTNAME_WORKER_2" references: [] 2022-07-22T17:09:32.085+0300 [DEBUG] ReferenceTransformer: "var.VM_IMG_FORMAT" references: [] 2022-07-22T17:09:32.086+0300 [DEBUG] ReferenceTransformer: "var.VM_CIDR_RANGE" references: [] 2022-07-22T17:09:32.086+0300 [DEBUG] ReferenceTransformer: "libvirt_cloudinit_disk.cloudinit_worker2" references: [var.VM_HOSTNAME_WORKER_2 libvirt_pool.pool_k8s data.template_file.user_data_worker2] 2022-07-22T17:09:32.086+0300 [DEBUG] ReferenceTransformer: "libvirt_cloudinit_disk.cloudinit_master1" references: [var.VM_HOSTNAME_MASTER_1 libvirt_pool.pool_k8s data.template_file.user_data_master1] 2022-07-22T17:09:32.086+0300 [DEBUG] ReferenceTransformer: "var.VM_IP_ADDRESS_MASTER_1" references: [] 2022-07-22T17:09:32.086+0300 [DEBUG] ReferenceTransformer: "var.VM_IP_ADDRESS_NEXUS_1" references: [] 2022-07-22T17:09:32.086+0300 [DEBUG] ReferenceTransformer: "libvirt_pool.pool_k8s" references: [] 2022-07-22T17:09:32.087+0300 [DEBUG] ReferenceTransformer: "var.VM_IMG_URL" references: [] 2022-07-22T17:09:32.087+0300 [DEBUG] ReferenceTransformer: "var.VM_HOSTNAME_NEXUS_1" references: [] 2022-07-22T17:09:32.087+0300 [DEBUG] ReferenceTransformer: "provider[\"registry.terraform.io/hashicorp/template\"]" references: [] 2022-07-22T17:09:32.087+0300 [DEBUG] ReferenceTransformer: "libvirt_cloudinit_disk.cloudinit_worker1" references: [libvirt_pool.pool_k8s data.template_file.user_data_worker1 var.VM_HOSTNAME_WORKER_1] 2022-07-22T17:09:32.087+0300 [DEBUG] ReferenceTransformer: "var.VM_HOSTNAME_MASTER_1" references: [] 2022-07-22T17:09:32.087+0300 [DEBUG] ReferenceTransformer: "output.ip_config_master1" references: [libvirt_domain.master1] 2022-07-22T17:09:32.087+0300 [DEBUG] ReferenceTransformer: "output.ip_config_worker1" references: [libvirt_domain.worker1] 2022-07-22T17:09:32.088+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.vm_master1" references: [libvirt_pool.pool_k8s var.VM_IMG_FORMAT libvirt_volume.os_image_ubuntu_master var.VM_HOSTNAME_MASTER_1 var.VM_IMG_FORMAT] 2022-07-22T17:09:32.088+0300 [INFO]  ReferenceTransformer: reference not found: "path.module" 2022-07-22T17:09:32.088+0300 [DEBUG] ReferenceTransformer: "data.template_file.user_data_worker2" references: [var.VM_USER] 2022-07-22T17:09:32.088+0300 [DEBUG] ReferenceTransformer: "var.VM_HOSTNAME_WORKER_1" references: [] 2022-07-22T17:09:32.088+0300 [DEBUG] ReferenceTransformer: "var.VM_USER" references: [] 2022-07-22T17:09:32.089+0300 [DEBUG] Starting graph walk: walkValidate 2022-07-22T17:09:32.091+0300 [DEBUG] created provider logger: level=debug 2022-07-22T17:09:32.092+0300 [INFO]  provider: configuring client automatic mTLS 2022-07-22T17:09:32.111+0300 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 args=[.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4] 2022-07-22T17:09:32.113+0300 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 pid=52504 2022-07-22T17:09:32.113+0300 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 2022-07-22T17:09:32.118+0300 [INFO]  provider.terraform-provider-template_v2.2.0_x4: configuring server automatic mTLS: timestamp=2022-07-22T17:09:32.117+0300 2022-07-22T17:09:32.148+0300 [DEBUG] provider.terraform-provider-template_v2.2.0_x4: plugin address: address=/tmp/plugin532097705 network=unix timestamp=2022-07-22T17:09:32.148+0300 2022-07-22T17:09:32.148+0300 [DEBUG] provider: using plugin: version=5 2022-07-22T17:09:32.190+0300 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unimplemented desc = unknown service plugin.GRPCStdio" 2022-07-22T17:09:32.190+0300 [DEBUG] created provider logger: level=debug 2022-07-22T17:09:32.191+0300 [INFO]  provider: configuring client automatic mTLS 2022-07-22T17:09:32.191+0300 [DEBUG] No provider meta schema returned 2022-07-22T17:09:32.207+0300 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 args=[.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14] 2022-07-22T17:09:32.208+0300 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 pid=52515 2022-07-22T17:09:32.208+0300 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 2022-07-22T17:09:32.213+0300 [INFO]  provider.terraform-provider-libvirt_v0.6.14: configuring server automatic mTLS: timestamp=2022-07-22T17:09:32.213+0300 2022-07-22T17:09:32.223+0300 [DEBUG] provider.terraform-provider-libvirt_v0.6.14: plugin address: address=/tmp/plugin2422042871 network=unix timestamp=2022-07-22T17:09:32.223+0300 2022-07-22T17:09:32.223+0300 [DEBUG] provider: using plugin: version=5 2022-07-22T17:09:32.240+0300 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unimplemented desc = unknown service plugin.GRPCStdio" 2022-07-22T17:09:32.240+0300 [DEBUG] No provider meta schema returned 2022-07-22T17:09:32.241+0300 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 pid=52504 2022-07-22T17:09:32.241+0300 [DEBUG] provider: plugin exited 2022-07-22T17:09:32.249+0300 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 pid=52515 2022-07-22T17:09:32.249+0300 [DEBUG] provider: plugin exited 2022-07-22T17:09:32.249+0300 [INFO]  backend/local: apply calling Plan 2022-07-22T17:09:32.249+0300 [DEBUG] Building and walking plan graph for NormalMode 2022-07-22T17:09:32.249+0300 [DEBUG] adding implicit provider configuration provider["registry.terraform.io/hashicorp/template"], implied first by data.template_file.user_data_master1 (expand) 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "data.template_file.user_data_worker1 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/hashicorp/template"] 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "data.template_file.user_data_master1 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/hashicorp/template"] 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "libvirt_volume.os_image_ubuntu_worker (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "libvirt_network.kvm_kube_net (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "libvirt_cloudinit_disk.cloudinit_worker1 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "libvirt_domain.worker1 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "libvirt_volume.vm_worker2 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "libvirt_domain.master1 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "libvirt_volume.os_image_ubuntu_master (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.249+0300 [DEBUG] ProviderTransformer: "libvirt_volume.vm_worker1 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.250+0300 [DEBUG] ProviderTransformer: "libvirt_cloudinit_disk.cloudinit_worker2 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.250+0300 [DEBUG] ProviderTransformer: "libvirt_volume.vm_master1 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.250+0300 [DEBUG] ProviderTransformer: "libvirt_cloudinit_disk.cloudinit_master1 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.250+0300 [DEBUG] ProviderTransformer: "data.template_file.user_data_worker2 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/hashicorp/template"] 2022-07-22T17:09:32.250+0300 [DEBUG] ProviderTransformer: "libvirt_domain.worker2 (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.250+0300 [DEBUG] ProviderTransformer: "libvirt_pool.pool_k8s (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/dmacvicar/libvirt"] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "libvirt_domain.master1 (expand)" references: [libvirt_cloudinit_disk.cloudinit_master1 (expand) var.VM_HOSTNAME_MASTER_1 libvirt_network.kvm_kube_net (expand) var.VM_IP_ADDRESS_MASTER_1 libvirt_network.kvm_kube_net (expand) libvirt_volume.vm_master1 (expand)] 2022-07-22T17:09:32.250+0300 [INFO]  ReferenceTransformer: reference not found: "path.module" 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "data.template_file.user_data_master1 (expand)" references: [var.VM_USER] 2022-07-22T17:09:32.250+0300 [INFO]  ReferenceTransformer: reference not found: "path.module" 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "data.template_file.user_data_worker1 (expand)" references: [var.VM_USER] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_CIDR_RANGE" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "output.ip_config_master1" references: [libvirt_domain.master1 (expand)] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.vm_master1 (expand)" references: [var.VM_IMG_FORMAT var.VM_HOSTNAME_MASTER_1 var.VM_IMG_FORMAT libvirt_volume.os_image_ubuntu_master (expand) libvirt_pool.pool_k8s (expand)] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.os_image_ubuntu_worker (expand)" references: [var.VM_IMG_URL libvirt_pool.pool_k8s (expand)] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "libvirt_cloudinit_disk.cloudinit_master1 (expand)" references: [data.template_file.user_data_master1 (expand) var.VM_HOSTNAME_MASTER_1 libvirt_pool.pool_k8s (expand)] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_IP_ADDRESS_MASTER_1" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "libvirt_pool.pool_k8s (expand)" references: [] 2022-07-22T17:09:32.250+0300 [INFO]  ReferenceTransformer: reference not found: "path.module" 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "data.template_file.user_data_worker2 (expand)" references: [var.VM_USER] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_IP_ADDRESS_NEXUS_1" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "output.ip_config_worker1" references: [libvirt_domain.worker1 (expand)] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "libvirt_network.kvm_kube_net (expand)" references: [var.VM_CIDR_RANGE] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_HOSTNAME_WORKER_1" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_HOSTNAME_WORKER_2" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_IP_ADDRESS_WORKER_2" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_IMG_FORMAT" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_USER" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.os_image_ubuntu_master (expand)" references: [libvirt_pool.pool_k8s (expand) var.VM_IMG_URL] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_HOSTNAME_MASTER_1" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_IMG_URL" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "var.VM_IP_ADDRESS_WORKER_1" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "output.ip_config_worker2" references: [libvirt_domain.worker2 (expand)] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "provider[\"registry.terraform.io/hashicorp/template\"]" references: [] 2022-07-22T17:09:32.250+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.vm_worker2 (expand)" references: [libvirt_volume.os_image_ubuntu_worker (expand) var.VM_HOSTNAME_WORKER_2 var.VM_IMG_FORMAT libvirt_pool.pool_k8s (expand) var.VM_IMG_FORMAT] 2022-07-22T17:09:32.251+0300 [DEBUG] ReferenceTransformer: "libvirt_domain.worker2 (expand)" references: [var.VM_HOSTNAME_WORKER_2 libvirt_cloudinit_disk.cloudinit_worker2 (expand) libvirt_network.kvm_kube_net (expand) var.VM_IP_ADDRESS_WORKER_2 libvirt_network.kvm_kube_net (expand) libvirt_volume.vm_worker2 (expand)] 2022-07-22T17:09:32.251+0300 [DEBUG] ReferenceTransformer: "libvirt_volume.vm_worker1 (expand)" references: [var.VM_HOSTNAME_WORKER_1 var.VM_IMG_FORMAT libvirt_pool.pool_k8s (expand) var.VM_IMG_FORMAT libvirt_volume.os_image_ubuntu_worker (expand)] 2022-07-22T17:09:32.253+0300 [DEBUG] ReferenceTransformer: "libvirt_cloudinit_disk.cloudinit_worker1 (expand)" references: [var.VM_HOSTNAME_WORKER_1 libvirt_pool.pool_k8s (expand) data.template_file.user_data_worker1 (expand)] 2022-07-22T17:09:32.253+0300 [DEBUG] ReferenceTransformer: "libvirt_domain.worker1 (expand)" references: [libvirt_cloudinit_disk.cloudinit_worker1 (expand) var.VM_HOSTNAME_WORKER_1 var.VM_IP_ADDRESS_WORKER_1 libvirt_network.kvm_kube_net (expand) libvirt_network.kvm_kube_net (expand) libvirt_volume.vm_worker1 (expand)] 2022-07-22T17:09:32.253+0300 [DEBUG] ReferenceTransformer: "var.VM_HOSTNAME_NEXUS_1" references: [] 2022-07-22T17:09:32.253+0300 [DEBUG] ReferenceTransformer: "libvirt_cloudinit_disk.cloudinit_worker2 (expand)" references: [libvirt_pool.pool_k8s (expand) data.template_file.user_data_worker2 (expand) var.VM_HOSTNAME_WORKER_2] 2022-07-22T17:09:32.253+0300 [DEBUG] ReferenceTransformer: "provider[\"registry.terraform.io/dmacvicar/libvirt\"]" references: [] 2022-07-22T17:09:32.254+0300 [DEBUG] Starting graph walk: walkPlan 2022-07-22T17:09:32.254+0300 [DEBUG] created provider logger: level=debug 2022-07-22T17:09:32.254+0300 [INFO]  provider: configuring client automatic mTLS 2022-07-22T17:09:32.270+0300 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 args=[.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14] 2022-07-22T17:09:32.271+0300 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 pid=52528 2022-07-22T17:09:32.271+0300 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 2022-07-22T17:09:32.277+0300 [INFO]  provider.terraform-provider-libvirt_v0.6.14: configuring server automatic mTLS: timestamp=2022-07-22T17:09:32.277+0300 2022-07-22T17:09:32.285+0300 [DEBUG] provider: using plugin: version=5 2022-07-22T17:09:32.286+0300 [DEBUG] provider.terraform-provider-libvirt_v0.6.14: plugin address: address=/tmp/plugin2486542373 network=unix timestamp=2022-07-22T17:09:32.285+0300 2022-07-22T17:09:32.302+0300 [DEBUG] created provider logger: level=debug 2022-07-22T17:09:32.302+0300 [INFO]  provider: configuring client automatic mTLS 2022-07-22T17:09:32.302+0300 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unimplemented desc = unknown service plugin.GRPCStdio" 2022-07-22T17:09:32.303+0300 [DEBUG] No provider meta schema returned 2022-07-22T17:09:32.320+0300 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 args=[.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4] 2022-07-22T17:09:32.321+0300 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 pid=52539 2022-07-22T17:09:32.321+0300 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 2022-07-22T17:09:32.327+0300 [INFO]  provider.terraform-provider-template_v2.2.0_x4: configuring server automatic mTLS: timestamp=2022-07-22T17:09:32.325+0300 2022-07-22T17:09:32.353+0300 [DEBUG] provider.terraform-provider-template_v2.2.0_x4: plugin address: address=/tmp/plugin634369649 network=unix timestamp=2022-07-22T17:09:32.352+0300 2022-07-22T17:09:32.353+0300 [DEBUG] provider: using plugin: version=5 2022-07-22T17:09:32.396+0300 [DEBUG] provider.terraform-provider-libvirt_v0.6.14: 2022/07/22 17:09:32 [DEBUG] Configuring provider for<EMAIL_ADDRESS>&{map[uri:0xc00051a000] <nil> <nil> 0xc00047a1a0 map[] <nil> 0xc00047a220 0xc000498210 0xc0005b63c0 false map[] {1 {0 0}} false false} 2022-07-22T17:09:32.397+0300 [DEBUG] No provider meta schema returned 2022-07-22T17:09:32.397+0300 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unimplemented desc = unknown service plugin.GRPCStdio" 2022-07-22T17:09:32.398+0300 [DEBUG] Resource instance state not found for node "data.template_file.user_data_worker2", instance data.template_file.user_data_worker2 2022-07-22T17:09:32.398+0300 [INFO]  ReferenceTransformer: reference not found: "path.module" 2022-07-22T17:09:32.398+0300 [INFO]  ReferenceTransformer: reference not found: "var.VM_USER" 2022-07-22T17:09:32.398+0300 [DEBUG] ReferenceTransformer: "data.template_file.user_data_worker2" references: [] 2022-07-22T17:09:32.398+0300 [DEBUG] Resource instance state not found for node "data.template_file.user_data_worker1", instance data.template_file.user_data_worker1 2022-07-22T17:09:32.398+0300 [INFO]  ReferenceTransformer: reference not found: "var.VM_USER" 2022-07-22T17:09:32.398+0300 [INFO]  ReferenceTransformer: reference not found: "path.module" 2022-07-22T17:09:32.398+0300 [DEBUG] ReferenceTransformer: "data.template_file.user_data_worker1" references: [] 2022-07-22T17:09:32.398+0300 [DEBUG] Resource instance state not found for node "data.template_file.user_data_master1", instance data.template_file.user_data_master1 2022-07-22T17:09:32.398+0300 [INFO]  ReferenceTransformer: reference not found: "path.module" 2022-07-22T17:09:32.398+0300 [INFO]  ReferenceTransformer: reference not found: "var.VM_USER" 2022-07-22T17:09:32.398+0300 [DEBUG] ReferenceTransformer: "data.template_file.user_data_master1" references: [] data.template_file.user_data_worker2: Reading... data.template_file.user_data_master1: Reading... data.template_file.user_data_worker1: Reading... data.template_file.user_data_worker2: Read complete after 0s [id=8e5452d4842975f9c2a17101d65ea4d5b13609c3e906205bb35617bd7768355c] data.template_file.user_data_worker1: Read complete after 0s [id=64cc73b8370390084cbfc4f6908d68b1e512f615be43675385601373777685a8] data.template_file.user_data_master1: Read complete after 0s [id=7fbbd83259fbf96330312c7461f0d930e286990d61d185582b6381c72d7f2beb] 2022-07-22T17:09:32.407+0300 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/hashicorp/template/2.2.0/linux_amd64/terraform-provider-template_v2.2.0_x4 pid=52539 2022-07-22T17:09:32.407+0300 [DEBUG] provider: plugin exited 2022-07-22T17:09:32.451+0300 [ERROR] vertex "provider[\"registry.terraform.io/dmacvicar/libvirt\"]" error: failed to dial libvirt: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain ╷ │ Error: failed to dial libvirt: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain │  │   with provider["registry.terraform.io/dmacvicar/libvirt"], │   on main.tf line 10, in provider "libvirt": │   10: provider "libvirt" { │  ╵ 2022-07-22T17:09:32.452+0300 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/dmacvicar/libvirt/0.6.14/linux_amd64/terraform-provider-libvirt_v0.6.14 pid=52528 2022-07-22T17:09:32.452+0300 [DEBUG] provider: plugin exited

Can you make sure you use the URI format I suggested? The SSH client used by this provider needs you to set the keyfile parameter. In the debug logs I see you're just using the raw /system path with no parameters.
Please use qemu+ssh://root@<IP_ADDRESS>/system?keyfile={keyPath}&sshauth=privkey
Just because using the more simple URI works with QEMU client doesn't mean it will work with this. I would suggest you keep this suggested URI consistent thru your further testing.
If you read this providers source code you will find this is required unless you are using "${HOME}/.ssh/id_rsa" as the SSH key. Given that you said you are using ed25519 you should include this parameter and direct it to the full/absolute path to the key. See here:
https://github.com/dmacvicar/terraform-provider-libvirt/blob/e5bec5d00819d6fe71a66ee022d1e9d9acd4fe5c/libvirt/uri/ssh.go#L19
https://github.com/dmacvicar/terraform-provider-libvirt/blob/e5bec5d00819d6fe71a66ee022d1e9d9acd4fe5c/libvirt/uri/ssh.go#L32-L34

I tried all possible methods and combinations. Now I use the standard id_rsa key, but I also tried id_ed25519 in my link. Both keys are already flushed to remote_server in the authorized_keys file.
I have updated the output of the command above.

cat main.tf
terraform {
  required_providers {
    libvirt = {
      source = "dmacvicar/libvirt"
      version = "0.6.14"
    }
  }
}

provider "libvirt" {
  uri = "qemu+ssh://root@ip/system?sshauth=privkey"
}

terraform plan
╷
│ Error: Plugin did not respond
│
│   with provider["registry.terraform.io/dmacvicar/libvirt"],
│   on main.tf line 10, in provider "libvirt":
│   10: provider "libvirt" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ConfigureProvider call. The plugin
│ logs may contain more details.
╵

Stack trace from the terraform-provider-libvirt_v0.6.14 plugin:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x128002a]

goroutine 14 [running]:
golang.org/x/crypto/ssh.publicKeyCallback.auth(0x11, {0xc0005a6220, 0x20, 0x20}, {0xc00003ee4b, 0x4}, {0x1bad3d0, 0xc0005b8180}, {0x1b9dac0, 0xc00007e660})
	golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client_auth.go:235 +0x24a
golang.org/x/crypto/ssh.(*connection).clientAuthenticate(0xc0005b0080, 0xc0005ac000)
	golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client_auth.go:63 +0x3a9
golang.org/x/crypto/ssh.(*connection).clientHandshake(0xc0005b0080, {0xc00020a0a8, 0x11}, 0xc0005ac000)
	golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client.go:113 +0x26a
golang.org/x/crypto/ssh.NewClientConn({0x1bc21c8, 0xc0005a4008}, {0xc00020a0a8, 0x11}, 0xc0000cb800)
	golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client.go:83 +0x12b
golang.org/x/crypto/ssh.Dial({0x1a22411, 0x5}, {0xc00020a0a8, 0x11}, 0xc0000cb800)
	golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client.go:190 +0x59
github.com/dmacvicar/terraform-provider-libvirt/libvirt/uri.(*ConnectionURI).dialSSH(0xc0000cb9c8)
	github.com/dmacvicar/terraform-provider-libvirt/libvirt/uri/ssh.go:130 +0x465
github.com/dmacvicar/terraform-provider-libvirt/libvirt/uri.(*ConnectionURI).DialTransport(0xc00003ee40)
	github.com/dmacvicar/terraform-provider-libvirt/libvirt/uri/connection_uri.go:83 +0x45
github.com/dmacvicar/terraform-provider-libvirt/libvirt.(*Config).Client(0x1a4b923)
	github.com/dmacvicar/terraform-provider-libvirt/libvirt/config.go:35 +0x73
github.com/dmacvicar/terraform-provider-libvirt/libvirt.providerConfigure(0xc00018a150)
	github.com/dmacvicar/terraform-provider-libvirt/libvirt/provider.go:68 +0xff
github.com/hashicorp/terraform-plugin-sdk/helper/schema.(*Provider).Configure(0xc000532000, 0xc00037a6c8)
	github.com/hashicorp/terraform-plugin-sdk@v1.9.0/helper/schema/provider.go:275 +0xb4
github.com/hashicorp/terraform-plugin-sdk/internal/helper/plugin.(*GRPCProviderServer).Configure(0xc00037a068, {0xc00037ce80, 0x1111946}, 0xc00037ce80)
	github.com/hashicorp/terraform-plugin-sdk@v1.9.0/internal/helper/plugin/grpc_provider.go:487 +0x1d2
github.com/hashicorp/terraform-plugin-sdk/internal/tfplugin5._Provider_Configure_Handler({0x19f4140, 0xc00037a068}, {0x1bb4c30, 0xc00001d440}, 0xc0004f9c20, 0x0)
	github.com/hashicorp/terraform-plugin-sdk@v1.9.0/internal/tfplugin5/tfplugin5.pb.go:3251 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0000ae180, {0x1bc2380, 0xc0000ae300}, 0xc00058c700, 0xc00008e540, 0x215f0b8, 0x0)
	google.golang.org/grpc@v1.27.1/server.go:1024 +0xd1e
google.golang.org/grpc.(*Server).handleStream(0xc0000ae180, {0x1bc2380, 0xc0000ae300}, 0xc00058c700, 0x0)
	google.golang.org/grpc@v1.27.1/server.go:1313 +0xa56
google.golang.org/grpc.(*Server).serveStreams.func1.1()
	google.golang.org/grpc@v1.27.1/server.go:722 +0x98
created by google.golang.org/grpc.(*Server).serveStreams.func1
	google.golang.org/grpc@v1.27.1/server.go:720 +0xef

Error: The terraform-provider-libvirt_v0.6.14 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

Hello I confirm it's works
example:

terraform {

required_version = ">= 0.14.0"

  required_providers {
    libvirt = {
      source  = "dmacvicar/libvirt"
      version = "0.6.14"
    }
  }
}

provider "libvirt" {
  uri = "qemu+ssh://USER@IP/system?keyfile=/tmp/id_rsa_sample&sshauth=privkey"
}

Works:
"Apply complete! Resources: 4 added, 0 changed, 0 destroyed."
best regards

Hi @dmacvicar
confirming similar issue, works with "virsh -c" and not with terraform --> but adding more details maybe it helps - would appreciate some help, if some workaround is found or so... <-- kinda tried everything (no other key works, like ed25519, swapped also provider versions - same issue  )
terraform: 1.3.2
libvirt-provider: 0.6.10-14 and 0.7.0
Tested on:
os: centos 7.9 (2009) and red hat 7.9 maipo
provider "libvirt" {
  ## Configuration options
  uri = "qemu+ssh://root@10.*.*.5/system?keyfile=/root/.ssh/id_rsa"
#   uri = "qemu+ssh://root@10.*.*.5/system?keyfile=/root/.ssh/id_rsa?sshauth=privkey"
}

terraform plan
2022-10-14T12:39:45.057+0100 [ERROR] vertex "provider[\"registry.terraform.io/dmacvicar/libvirt\"]" error: failed to dial libvirt: failed to connect to libvirt on the remote host: ssh: rejected: administratively prohibited (open failed)
2022-10-14T12:39:45.057+0100 [INFO]  backend/local: plan operation completed
╷
│ Error: failed to dial libvirt: failed to connect to libvirt on the remote host: ssh: rejected: administratively prohibited (open failed)
│
│   with provider["registry.terraform.io/dmacvicar/libvirt"],
│   on provider.tf line 20, in provider "libvirt":
│   20: provider "libvirt" {
│

╵
Destination server(..*.5) --> key is accepted but does not go forward
Oct 14 12:34:05 hv2 sshd[90019]: Accepted publickey for root from <IP_ADDRESS> port 35702 ssh2: RSA SHA256:3Q7NpIRujvbsPARh7cp9BVERrw0ApI/7JE8QndprVBo
Oct 14 12:34:05 hv2 sshd[90019]: pam_unix(sshd:session): session opened for user root by (uid=0)
Oct 14 12:34:05 hv2 sshd[90019]: refused streamlocal port forward: originator  port 0, target /var/run/libvirt/libvirt-sock
Oct 14 12:34:05 hv2 sshd[90019]: pam_unix(sshd:session): session closed for user root

SSHD_CONFIG
UsePAM yes

#slagian-libvirt-sock
AllowAgentForwarding yes
AllowTcpForwarding no
PermitOpen any
PermitTunnel yes
#GatewayPorts no
X11Forwarding yes
...

I had the same issue on Centos 7.9.2009. The problem is due to openssh 7.4 on CentOS/RHEL not allowing root user ssh tunnel on a socket.
References:
https://bugzilla.redhat.com/show_bug.cgi?id=1527565
https://bugs.centos.org/view.php?id=14291
I have resolved it by creating a new user and adding it to libvirt group:
usermod -a -G libvirt <username>
Hope this does the trick also for you!

I'm not sure if this is related, but I had a similar issue with SSH failing and it ended up being caused by incomplete support for the ETM (Encrypt-them-MAC) HMAC ciphers in the Go ssh libraries.
I came across golang/go#32075 where I found the following comment:

https://github.com/golang/go/commit/84bacda6ede319f5074d43b5d096b7ee7f3f5d77 added support for<EMAIL_ADDRESS>however only implemented it for stream ciphers (arcfour*) and not for CBC block ciphers (aes128-cbc and 3des-cbc). This means that the SSH client will advertise support for EtM, the SSH server will select a CBC cipher with EtM, then the client fails to handle the resulting packets correctly

As a work-around, I disabled those HMAC ciphers by adding the following line to the /etc/ssh/sshd_config file on the libvirt host. This way the SSH server will never use EtM.
MACs hmac-sha1,hmac-sha1,hmac-sha1-96,hmac-sha1-96,hmac-sha2-256,hmac-sha2-256,hmac-sha2-512,hmac-sha2-512,hmac-md5,hmac-md5,hmac-md5-96,hmac-md5-96,umac-64@openssh.com,umac-64@openssh.com,umac-128<EMAIL_ADDRESS>
I got the list by running ssh -Q mac to show all supported ciphers and removed the ones using EtM. Some of these are less secure than others, so use your own discretion and make sure you understand the implications. I have no idea if all of them should be enabled on the server.

I had the same issue on Centos 7.9.2009. The problem is due to openssh 7.4 on CentOS/RHEL not allowing root user ssh tunnel on a socket.
References: https://bugzilla.redhat.com/show_bug.cgi?id=1527565 https://bugs.centos.org/view.php?id=14291
I have resolved it by creating a new user and adding it to libvirt group: usermod -a -G libvirt <username>
Hope this does the trick also for you!

It's work on 0.7.1 version, thanks. I created other user and added him on libvirt group.
Finally link is: uri = "qemu+ssh://terraform@<ip_adress>/system"

Works on Mac and Ubuntu 22.04. No need to specify the key since id_rsa is the default.
terraform {
required_providers {
libvirt = {
source  = "dmacvicar/libvirt"
version = "0.7.1"
}
}
}
provider "libvirt" {
uri = "qemu+ssh://robin@<IP_ADDRESS>/system?sshauth=privkey&no_verify=1"
}

I think this issue is already fixed with latest provider version.


Value error when running decode attention with FP8 KV cache

I have k_cache and v_cache as torch.float8_e4m3fn tensors and am calling run (decode attention). I am getting this error.
ValueError: FlashInfer Internal Error: Invalid configuration : NUM_FRAGS_Q=1 NUM_FRAGS_D=8 NUM_FRAGS_KV=1 NUM_WARPS_Q=1 NUM_WARPS_KV=4 please create an issue (https://github.com/flashinfer-ai/flashinfer/issues) and report the issue to the developers.

Hi @sugunav14 what's the head dimension you are using?

num_heads_q is 32 and num_heads_kv is 8

Also, another observation I made is that I am facing this error only when I set fuse_rope = True


[BUG] The Slider step divisions feature has issues when the min and max values are not 0 and 1

Describe the bug
The MRTK Slider UX component includes a feature to cause snapping to a specific number of subdivisions. E.g. if set to 5, there will be 5 snap points along the slider's length. However if you set the Min and Max values to anything but 0 and 1, it seems that the slider will get stuck.
To reproduce
Steps to reproduce the behavior:

Go to the Canvas Tearsheet scene in the dev templates
Set the Max value of one of the sliders to 20, and enable 5 slider step divisions
Launch the scene
Try using the slider. Notice that the slider handle is stuck at 0 and won't move to other values.

Expected behavior
The slider should support movement side to side to the 5 step divisions
Screenshots

Your setup (please complete the following information)

Unity Version 2021.3.21f1
MRTK Version or Commit e3002c17a9294c223ce7ab7296b732775bf92d9c

Target platform (please complete the following information)

Unity Editor

Additional context
Add any other context about the problem here.

Thanks for bug. This should be resolved in #479


bug: ingress-apisix does not work when configured with apisixroute

Issue description
hi guys
I have a very strange problem, ingress-apisix does not work when configured with apisixroute, but it works in the dashboard, how can I troubleshoot this problem?
Environment

apisix-ingress-controller-0.6.0
Kubernetes 1.19.7
centos7.9

Minimal test code / Steps to reproduce the issue
k describe ApisixRoute foo-bar-route
Name:         foo-bar-route
Namespace:    default
Labels:
Annotations:
API Version:  apisix.apache.org/v1
Kind:         ApisixRoute
Metadata:
Creation Timestamp:  2021-08-19T12:29:05Z
Generation:          1
Managed Fields:
API Version:  apisix.apache.org/v1
Fields Type:  FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.:
f:kubectl.kubernetes.io/last-applied-configuration:
f:spec:
.:
f:http:
Manager:         kubectl-client-side-apply
Operation:       Update
Time:            2021-08-19T12:29:05Z
Resource Version:  602410
Self Link:         /apis/apisix.apache.org/v1/namespaces/default/apisixroutes/foo-bar-route
UID:               3133c83f-39d7-4ed3-a65a-84b7f2cb5a5c
Spec:
Http:
Backend:
Service Name:  foo
Service Port:  80
Match:
Hosts:
foo.com
Paths:
/foo*
Name:  foo
Backend:
Service Name:  bar
Service Port:  80
Match:
Paths:
/bar
Name:  bar
Events:

the problem is solved in the new version