Switch matplotlib dependency to matplotlib-base

lalburst doesn't require the interactive portions of matplotlib, so we can just depend on matplotlib-base, which is a much smaller footprint.
Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The build section contained an unexpected subsection name. error_overdepending is not a valid subsection name.
The build section contained an unexpected subsection name. error_overlinking is not a valid subsection name.


Issue with testing Expect: 100-Continue

Bug Description
I want to test the correct behavior of a client I'm writing, in this particular case the behavior of the Expect: 100-Continue header/directive.
Wiremock implicitly sends the Http/1.1 100 Continue response. And I haven't found a way to control it. This is fine for most cases, but not when you want to test the error case.
When responding with 413 Entity too large I would have expected, wiremock not to send 100 Continue first.
Set a breakpoint here org.apache.hc.core5.http.impl.io.HttpRequestExecutor.java:154 to observe what the client sees.

[x] Which version of WireMock you're using wiremock-jre8:2.32.0
[x] A failing test case that demonstrates the problem

Reproducer
    implementation("org.apache.httpcomponents.client5:httpclient5-fluent:5.1.2")
    testImplementation("org.junit.jupiter:junit-jupiter-api:5.8.2")
    testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine")
    testImplementation("com.github.tomakehurst:wiremock-jre8:2.32.0")

package reproducer;

import com.github.tomakehurst.wiremock.junit5.WireMockRuntimeInfo;
import com.github.tomakehurst.wiremock.junit5.WireMockTest;
import com.github.tomakehurst.wiremock.matching.RequestPatternBuilder;
import org.apache.hc.client5.http.fluent.Request;
import org.apache.hc.client5.http.impl.classic.CloseableHttpClient;
import org.apache.hc.client5.http.impl.classic.HttpClientBuilder;
import org.apache.hc.core5.http.ContentType;
import org.apache.hc.core5.http.HeaderElements;
import org.apache.hc.core5.http.HttpHeaders;
import org.apache.hc.core5.http.io.entity.AbstractHttpEntity;
import org.junit.jupiter.api.Test;
import org.opentest4j.AssertionFailedError;

import java.io.IOException;
import java.io.InputStream;

import static com.github.tomakehurst.wiremock.client.WireMock.*;

@WireMockTest
public class WireMock100ContinueTest {
    @Test
    public void test(WireMockRuntimeInfo wireMockRuntimeInfo) throws IOException {
        stubFor(put(anyUrl())
            .willReturn(aResponse().withStatus(200)));

        String body = "Hello World!";
        try (CloseableHttpClient httpClient = HttpClientBuilder.create().build()) {

            Request.put(wireMockRuntimeInfo.getHttpBaseUrl() + "/")
                .addHeader(HttpHeaders.EXPECT, HeaderElements.CONTINUE)
                .bodyString(body, ContentType.TEXT_PLAIN)
                .execute(httpClient);
        }

        verify(1, RequestPatternBuilder
            .allRequests()
            .withHeader(HttpHeaders.EXPECT, equalTo(HeaderElements.CONTINUE))
            .withRequestBody(equalTo(body))
        );
    }

    @Test
    public void testFail(WireMockRuntimeInfo wireMockRuntimeInfo) throws IOException {
        stubFor(put(anyUrl())
            .willReturn(aResponse().withStatus(413)));

        String body = "Hello World!";
        try (CloseableHttpClient httpClient = HttpClientBuilder.create().build()) {

            Request.put(wireMockRuntimeInfo.getHttpBaseUrl() + "/")
                .addHeader(HttpHeaders.EXPECT, HeaderElements.CONTINUE)
                .body(new AbstractHttpEntity(ContentType.APPLICATION_OCTET_STREAM, null) {
                    @Override
                    public InputStream getContent() throws IOException, UnsupportedOperationException {
                        throw new AssertionFailedError("Should not be called");
                    }

                    @Override
                    public boolean isStreaming() {
                        return false;
                    }

                    @Override
                    public void close() throws IOException {

                    }

                    @Override
                    public long getContentLength() {
                        return 100000;
                    }
                })
                .execute(httpClient);
        }

        verify(1, RequestPatternBuilder
            .allRequests()
            .withHeader(HttpHeaders.EXPECT, equalTo(HeaderElements.CONTINUE))
            .withRequestBody(absent())
        );
    }
}

I've labelled this as an enhancement rather than bug, but I agree it'd be nice to be able to test this case specifically.
Do you feel like investigating whether Jetty will permit us to get in the middle of a 100-continue exchange?

A quick search turned up https://stackoverflow.com/a/35305306/16358266 which basically says:

If you want to respond that part of the request, then:

Don't attempt access to the request parameters (this needs to read the input stream to process all possible parameter sources)
Don't attempt access to the request input stream (this means you are accepting the 100-Continue Expectation and are ready to receive the actual request body content)
Don't attempt access to the request reader (this opens the request input stream too)
Don't attempt to use the servlet Async I/O layer (this opens the request inputstream and response outputstreams)
Do use the HttpServletResponse to send your alternate status code and/or response body content.

So I guess this needs some special handling so that it is processed before all the other things are evaluated.

I now use a barebones Jetty implementation as a workaround.
Server server = new Server(0)
server.setHandler(new AbstractHandler() {
    @Override
    void handle(String target, Request baseRequest, HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException {
        response.sendError(HttpServletResponse.SC_REQUEST_ENTITY_TOO_LARGE)
    }
})


add a "test.sh" script

since we dont have CI lets do this.

Add a test.sh script to the repo
When we make PRs , people run the test.sh script.
The script  takes as input (CNI, k8s commit ID).

runs make all... makes a new cluster from k8s master w calico or antrea (option)
Runs operational readiness spec w/ Core test specification
Passes or Fails based on results

This can be broken into two issues.

First we make the test.sh script
Then, we add the Operational Readiness spec tests

Once it works, locally, w vbox, it can be standard protocol to run it for new commits.
Then, eventually we can use this as the basis for #206

/assign

@jayunit100 we have VT-x limitation describe in #206 please let me know your thoughts.


[FEATURE] Show detailed information about vm status

Is your feature request related to a problem? Please describe.
When the vm status is not running, display the detailed information of the associated crd, such as the error message of pod or vmi

When the vm is in the failed migration state, no error message can be seen on the vm state, and it cannot be migrated again.
The migration failure can be reproduced by the following operations:

Migrate vm from host A to host B
Shutdown host B
Restart the vm

For failed migrations(https://github.com/harvester/harvester/issues/693#issuecomment-824591476), in some cases reason for the failure is not available.
If the VMI.status.migrationState is correctly set, we should be able to get the event message for the details(REASON==Migrated)
LAST SEEN   TYPE      REASON                       OBJECT                                                 MESSAGE
23m         Warning   Migrated                     virtualmachineinstance/lawr                            VirtualMachineInstance migration uid c01c564e-f93e-4a06-856d-3af245d00ca8 failed. reason:Live migration failed virError(Code=9, Domain=31, Message='operation failed: guest CPU doesn't match specification: missing features: ss,fma,movbe,f16c,rdrand,fsgsbase,bmi1,avx2,smep,bmi2,erms,invpcid,abm')
34m         Normal    Migrated                     virtualmachineinstance/test                            The VirtualMachineInstance migrated to node node1.
32m         Normal    Migrated                     virtualmachineinstance/test                            The VirtualMachineInstance migrated to node node1.
28m         Warning   Migrated                     virtualmachineinstance/test                            VirtualMachineInstance migration uid e024cf21-2a4f-4036-9299-8bf5e55f9b2f failed. reason:Live migration failed virError(Code=1, Domain=7, Message='internal error: client socket is closed')

validated on v0.2.0-rc4


chore: test on node 14

Closes #711
Closes #996

@mayurkale22 I updated the wording and added a table of supported versions. PTAL and merge if you think it's ok.


Add support for creating data providers in C# and apply a few Resharper suggestions

This change is

This doesn't add USFM support yet.  It just adds a simple C# data provider to start.  Once ParatextData integration is working, this code can be used to create a USFM data provider.


No syntax highlighting for html

It seems like there is no syntax highlighting for html. It would be nice if that was included as well.

+1

The screenshot in the repo shows highlighting for html, and also a Jinja-HTML language that I can't find.

I switched language mode to HTML and everything is highlighted properly now (including Jinja)

It used to work, but was removed when a change to Code was made for understanding mixed languages. See my comment in https://github.com/wholroyd/vscode-jinja/issues/19 for background.


Use Conda to update the seam-installer

seamm_installer version: 2021.3.17
Python version: 3.8
Operating System: all

Description
Currently the installer updates itself using pip, which seems to cause some issues. Change to use the conda package!

Closed by PR#4


Allow Kitura-NIO to only listen on one network address

Description
@billabt was nice enough to add support for this at the BlueSocket layer here. However, I really want to use that functionality to fix https://github.com/IBM-Swift/Kitura/issues/1450.
I also have code ready to go for https://github.com/IBM-Swift/Kitura-net/pull/299 and Kitura.
Obviously, this is the Kitura-NIO version of the Kitura-Net change.
Motivation and Context
This is necessary to close https://github.com/IBM-Swift/Kitura/issues/1450. Should I open another issue for Kitura-NIO?
How Has This Been Tested?
Manual testing by myself. I also modified the test harness to use the new code path.
Checklist:

[x] I have submitted a CLA form
[x] If applicable, I have updated the documentation accordingly.
[x] If applicable, I have added tests to cover my changes.

I believe that my latest changes fix everything that was requested and bring this PR in line with the one for Kitura-Net. Let me know if I missed anything.

Good catch. I missed that since they conformed to the same Server protocol.


torchsparse 2.1.0 missing PointTensor

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I just attempted to use torchsparse with NeuralRecon, and found that I am unable to proceed because PointTensor is completely missing from the package. There is no documentation as to why it was removed or where it's now located. There isn't even source code for 2.1.0, only 2.0.0. I am unable to install an older version because there are only wheels for 2.1.0 online.
Expected Behavior
Either documentation on whereabouts or deprecation of PointTensor, replacement of PointTensor back into torchsparse (if it's an error), or access to older wheel files.
Environment
- GCC: 9.4.0
- NVCC: 11.7
- PyTorch: 1.13.1
- PyTorch CUDA: 11.7
- TorchSparse: 2.1.0+torch113cu117

Anything else?
No response

Hi @TetraEngine,
This is the expected behavior. We deprecated PointTensor from torchsparse because it is only used in the SPVNAS project. We instead provided a better implementation of this class in spvnas, which can be accessed here.
Best,
Haotian

你好@TetraEngine,
这是预期的行为。我们弃用PointTensor了 torchsparse，因为它仅在 SPVNAS 项目中使用。相反，我们在 spvnas 中提供了此类的更好实现，可以在此处访问。
最好的， 昊天

你好@TetraEngine,
这是预期的行为。我们弃用PointTensor了 torchsparse，因为它仅在 SPVNAS 项目中使用。相反，我们在 spvnas 中提供了此类的更好实现，可以在此处访问。
最好的， 昊天

How can I introduce or use alternatives


Just In Time Error

Microsoft PowerToys version
0.71.0
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
When my pc start this error happens pls look at the screenshots. I tried deleting every visual studio app it did not change anything ı tried useing the insider version of visual studio it did not change anything too. I use the turkish version of the app sorry for that.
On Event Manager it gives this:
Hatalı uygulama adı: PowerToys.PowerLauncher.exe, sürüm: <IP_ADDRESS>, zaman damgası: 0x648f9b5c
Hatalı modül adı: ntdll.dll, sürüm: 10.0.22621.1928, zaman damgası: 0x7dd9e350
Özel durum kodu: 0xc0000409
Hata uzaklığı 0x000000000008ea6f
Hatalı işlem kimliği: 0x0x3354
Uygulama başlangıç zamanı: 0x0x1D9C1931C926047
Hatalı uygulama yolu: C:\Program Files\PowerToys\modules\launcher\PowerToys.PowerLauncher.exe
Hatalı modül yolu: C:\Windows\SYSTEM32\ntdll.dll
Rapor kimliği: 52a7cc69-5297-44cb-ad3b-413433966387
Hatalı paket tam adı:
Hatalı paketle ilgili uygulama kimliği:

✔ Expected Behavior
this error not showing on startup.
❌ Actual Behavior
this error happens.
Other Software
No response

edit : sometimes the application which gives the error in the sreenshot changes but it is always about just in time debugger and in event manager it always says power toys is the one that gives the error.

Updating to 72 fixed this.


Problem: outdated send your first tx docs

Preview here https://crypto-chain-doc.surge.sh/getting-started/send_your_first_transaction.html

@foreseaz @lezzokafka what is the plan about this PR?

@foreseaz  is finishing the last import/export tx bit, will be updated soon.

@foreseaz @lezzokafka what is the plan about this PR?

@foreseaz is finishing the last import/export tx bit, will be updated soon.

I break it and raised a new issue #92, so that @foreseaz  can finish this PR first.

Updated & pls review~ Due to my local cli env problems, I left the export & import tx commands for @lezzokafka to finish #92 Thanks.


Porting CC 139 Calculating Digits of Pi With Collisions

Important Note
The p5.js web editor version is unable to load the clack.wav as well as the block.png file, and hence the sketch isn't running:
https://editor.p5js.org/codingtrain/sketches/4FuKfd-LJ
I've kept this link added in the code example in case it's changed and made to work.
The code from the GitHub repo works fine, so reuploading those files could solve the problem, maybe.
https://github.com/CodingTrain/Coding-Challenges/tree/main/139_Pi_Collisions/P5
Added:

timestamps
showcase contribution screenshots, updated metadata
updated tags, descriptions

Todo:

[ ]  adding the images directory

Also, I was wondering if something like this could be used for the index.jpg. It's fine if anything better can be used in place of it since this is a very special coding challenge! For now I've added one without any texts.

p5 web editor version is fixed!


Normalize Code

Remove Trailing Whitespace
Ensure one newline at EOF.

Let's just use standard, sound good?

I had tried standard earlier, however, I'm not sure how to eliminate some errors. For example:
/home/ryan/rock/lib/rock.js:52:17: Expected error to be handled.

nextflow is handling errors here.

nextflow is handling errors here.

Cool, let's kill the usage of nextflow.

Cool, let's kill the usage of nextflow.

@jprichardson What do you have in mind?

Use named functions and have each function call the next one?

This sounds great.

Removed nextflow, now for standard...

@jprichardson All done! :tada:

Awesome, thank you!


Add friends pending req

Thank you for opening a PR!
The implementation looks good to me, I would just love if you added interfaces to the response. I know the existing code does not implement it properly as well, but I'll give it a good rewrite when I have time!
If you can add this interface in the models folder:
export interface PlexFriend {
  status: string;
  sharedServers: any[];
  sharedSources: any[];
  id: number;
  uuid: string;
  title: string;
  username: string;
  restricted: boolean;
  email: string;
  friendlyName: any;
  thumb: string;
  home: boolean;
}

And used in the method like this:
getPendingFriends(): Promise<PlexFriend[]> {
  if (this.accessToken === "")
    return this.authenticate().then(() => this.getPendingFriends());
  let friends: PlexFriend[] = [];
  let options: {} = {
    method: "GET",
    url: "https://plex.tv/api/v2/friends?status=pending_sent&includeSharedServers=true",
    json: true,
    headers: {
      "X-Plex-Token": this.accessToken,
    },
  };
  return new Promise((resolve) => {
    request(options)
      .then((fetchedFriends: PlexFriend[]) => {
        fetchedFriends.forEach((friend: PlexFriend) => {
          friends.push(friend);
        });
        resolve(friends);
      })
      .catch((error: any) => {
        throw new Error(error.message);
      });
  });
}

It would also be nice if the documentation was updated as well with your changes - I don't mind doing this part though.


Code 128 manual subset selection

I was wondering whether it is possible to create a Code 128 barcode, but with different subsets used for different parts of it? More specifically, say subset A for the first 8 characters, B for the next 10, etc.

On 15 April 2016 at 12:38, Simon Mansfield<EMAIL_ADDRESS>wrote:

I was wondering whether it is possible to create a Code 128 barcode, but with different subsets used for different parts of it? More specifically, say subset A for the first 8 characters, B for the next 10, etc.

The specifications discourage such usage.
It sounds like what you might find useful would be the ability to
directly specify the codewords, avoiding the high-level encoding
entirely?
Might I ask what the use case is?

Am 15.04.2016 um 14:40 schrieb Terry Burton:

On 15 April 2016 at 12:38, Simon Mansfield<EMAIL_ADDRESS>wrote:

I was wondering whether it is possible to create a Code 128 barcode,
but with different subsets used for different parts of it? More
specifically, say subset A for the first 8 characters, B for the next
10, etc.

Simon,
Normally, the character changes are chosen automatically to get minimal
code length. You want that, as shorter codes increase readability.
Example data: 1234567A
Low Level Codewords (automatically chosen): [Start C] [12] [34] [56]
[Change B] [7] [A] [Check] [Stop]
-> 9 Codewords
Perhaps you don't know, that bwipp cares about this automatically and
there is no need to specify anything.
A reason to specify the "charset" is to get contant code length with
constant data length. If you specify "Set B" for the upper code, you get
a constant length, even if you encode digits or alphas:
[Start B] [1] [2] [3]... -> 11 Codewords
Those two use-cases are covered. Is your use case one of those ?
Hope this helps,
Harald

I need to generate a barcode to the Interlink specification, which states that certain parts of the barcode must be encoded with specific subsets.
Here's a copy of the spec:
Interlink UK.pdf

Am 15.04.2016 um 14:55 schrieb Simon Mansfield:

I need to generate a barcode to the Interlink specification, which
states that certain parts of the barcode must be encoded with specific
subsets.
Here's a copy of the spec:
Interlink UK.pdf
https://github.com/bwipp/postscriptbarcode/files/221002/Interlink.UK.pdf

Ok, thank you.
Harald

Simon,
I've just remembered that I included a "raw" option (or "encoding=raw") that allows you to specify the codewords directly.
See: https://github.com/bwipp/postscriptbarcode/wiki/Code-128
Alongside the encoding table here: https://en.wikipedia.org/wiki/Code_128#Bar_code_widths

@terryburton I saw the raw option, but to be completely honest, I had no-idea how to use it! Any way I could get you to do a small example of it's usage? Hell, I'm sure it'd be useful in the Wiki too

Updated comment above.

Awesome, thanks! I'll give that a go now. 👍

Leaving this fragment from offline here:

Terry Burton (@terryburton) wrote:
Grrr. The GeoPost specification should not be dictating what the
internal representation of the barcode should be since a
standards-compliant barcode reader would not reveal such data anyway!
That said, a very brief reading of the spec seems to indicate that
the data format complies with a run of alphanumeric data following by
numeric data. If that is so then BWIPP's optimising encoder will
naturally produce Mode B data for the leading characters (including
the short run of digits in a post code) then switch to Mode C for the
numeric tail.
Royal Mail has similar requirements over Data Matrix for their new
postal symbology. After talking to their developers it turns out that
all they intended to achieve was stability in the output size, which
is probably the case here.

Terry, just to add a note to this closed issue.
We had a situation at a factory where we had to program a fixed scanner to ignore code128 symbols that started in subset-C.  The labels it was scanning contained three code128 symbols, with the top one always starting in subset-C.  We wanted only the other two bar codes.
Why I bring this up?  Sometimes, because of automatic encoding, one of the other two bar codes would also start in subset-C....
We unfortunately had no control over those labels, but I think it demonstrates a use-case for at least forcing the starting subset.
Cheers, Mark

On 15 Apr 2016 19:38, "metafloor"<EMAIL_ADDRESS>wrote:

Terry, just to add a note to this closed issue.
We had a situation at a factory where we had to program a fixed scanner
to ignore code128 symbols that started in subset-C. The labels it was
scanning contained three code128 symbols, with the top one always starting
in subset-C. We wanted only the other two bar codes.
Why I bring this up? Sometimes, because of automatic encoding, one of the
other two bar codes would also start in subset-C....
We unfortunately had no control over those labels, but I think it
demonstrates a use-case for at least forcing the starting subset.

That's useful, thanks!

When using the bwip-js.js library to generate a Code 128 barcode, if the symtext content is "^105^012^034^056^100^023^033" and symopts are set to include text with "includetext raw" option, the text content will not be displayed. How can this be resolved?


Fix the UndeclaredEntityException message when not providing a relationship name

The issue
Look at the A_blabla_to_B_null part in the stacktrace.
Better to remove the _ as separator too and use brackets.

The stacktrace
An error has occurred:
	UndeclaredEntityException
Error message:
	In the association A_blabla_to_B_null, the entity A is not declared.
Stack trace:
Error
    at Object.<anonymous> (/usr/lib/node_modules/jhipster-uml/lib/exceptions/undeclared_entity_exception.js:7:39)
    at Module._compile (module.js:398:26)
    at Object.Module._extensions..js (module.js:405:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/usr/lib/node_modules/jhipster-uml/lib/dsl/dsl_parser.js:12:33)
    at Module._compile (module.js:398:26)
    at Object.Module._extensions..js (module.js:405:10)

The XMI or JDL file
relationship ManyToMany {
  A{blabla} to B
}

Versions

JHipster
JHipster UML

2.27.2
1.6.4

Hello, you actually have to declare A entity A and B entity B.

@MathieuAA,
I know that. This was intentional.
Like I said, look at the message: In the association A_blabla_to_B## null, the entity A is not declared._

Oh, sorry then!
I'll have a look in a few minutes.

I don't think you use v1.6.4 of JHipster-UML... this message was replaced by: In the Many-to-Many relationship from A to B, only bidirectionality is supported for a Many-to-Many relationship..
You might still be stuck to v1.6.2...
Now for the error, I suggest you read the "Managing Relationships" page in the doc. I'll keep this thread open if you want help getting the last version, I know this can be very painful!

 $ jhipster-uml -v
The current version of JHipster UML is 1.6.4.

Please look at https://github.com/jhipster/jhipster-uml/blob/master/lib/dsl/dsl_parser.js#L233

Weird...

Ok. I don't know for you, but it's quite late, or early, in France.
I get your error when and only when I don't declare my entities in the JDL file.
Please check again.

Too tired to see the real problem, sorry.

Took me a real long time to understand what you wanted... but for the really long explanation: you don't have IDs in the JDL because we don't need to identify objects in the JDL file. However, we need them to access objects later in the generation process.
If a user has an error, this message will tell us the nature of the relationship and how it was created. That's completely normal.
Again, sorry to have taken such a long time to correctly understand you.

Hehehe... Maybe I'm being too laconic, sorry.
jhipster-uml is correct when it throws the UndeclaredEntityException. What bothers me is the message when you don't provide the relationship name. You should test to see if the relationship name is not declared and put empty instead of null.

Take a look at https://github.com/jhipster/jhipster-uml/blob/master/lib/dsl/dsl_parser.js#L49

You're not. But it's actually really difficult for people to understand one another when not communicating face to face.
I'll see what I can do about it sometime after at least ten hours of sleep and a nice cup of tea.
I'll release the enhancement before tomorrow I hope.

The new error message: In the relationship between A and B, the entity A is not declared.

@MathieuAA,
The message just below should not be changed too?
https://github.com/jhipster/jhipster-uml/blob/master/lib/dsl/dsl_parser.js#L251

Oh. I didn't see it at all. Thanks!

Merged the checks/throws into one:
  var absentEntities = [];

  if (!this.parsedData.getClass(association.from.name)) {
    absentEntities.push(association.from.name);
  }
  if (!this.parsedData.getClass(association.to.name)) {
    absentEntities.push(association.to.name);
  }
  if (absentEntities.length !== 0) {
    throw new UndeclaredEntityException(
        'In the relationship between '
        + association.from.name
        + ' and '
        + association.to.name
        + ', '
        + absentEntities.join(' and ')
        + (absentEntities.length === 1 ? ' is' : ' are')
        + ' not declared.'
    );
  }


refactor(ts): generate logging types from proto

Alternative to hand-writing the type-definitions https://github.com/googleapis/nodejs-logging/pull/309.

The second step would be to check-in the generated proto/ directory. The proto typedefs will need to be updated very rarely, so it is not necessary to generate them on each CI.

While we are here, we should also address https://github.com/googleapis/nodejs-logging/issues/133.


(3.0.53) RowanClassServiceTest>>#test_setSuperSubIndicators (commit 76b27b8) failing

Here are the test failures I just noticed:
Rowan STON Cypress Tonel tests for GemStone '3.2.15'
648 run, 637 passed, 5 failed, 6 errors
  errors
-->	RowanClassServiceTest>>#test_setSuperSubIndicators
-->	RowanTestClassServiceTest>>#test_setSuperSubIndicators
	RwBrowserToolApiTest>>#testMoveGlobalExtensionSessionMethods
	RwHybridBrowserToolTest>>#testHybridMoveMethodFromSessionMethodsIntoSessionMethods
	RwHybridBrowserToolTest>>#testHybridMoveMethodIntoSessionMethods
	RwRowanProjectIssuesTest>>#testIssue150_branches
  failures
	RowanClassServiceTest>>#test_addedProjectNotOnDisk
	RowanProjectServiceTest>>#test_addedProjectNotOnDisk
	RowanTestClassServiceTest>>#test_addedProjectNotOnDisk
	RwLoadingTest>>#testPoolDictionaryChanges
	RwSymbolDictionaryTest>>#testClassVersioningPatch

When I did the original merge of Oscar-3.0.53 the tests passed ... Also when I did my most recent commit on the candidateV1.2 branch the tests pass ... but today running in a stone built in a new location the tests fail in a batch job run against both v1.3 and v1.2  ... as well as failing interactivley ..
Like #333 and #336, the test failures should be addressed for the January release ...
In the interactive failure the class RowanSubClass is missing and a search for the string in the image, shows that the only place this string shows up is in the test itself ... I'm guessing that this test is depending upon side effects from other tests to run correctly ...

Like #333 and #336, the test failures should be addressed for the January release ...

@dalehenrich - did you mean #335?  #336 is not related to a failing test.

Sorry, I was referring to #366, not #336

@dalehenrich The test is relying on the RowanSample1 project which I load. RowanSubClass is in that project. Is it not safe to assume that RowanSample1 will be available as a directory when the server tests are run?
	RowanProjectService new newGitProject: 'file:$ROWAN_PROJECTS_HOME/Rowan/samples/RowanSample1.ston' root: '$ROWAN_PROJECTS_HOME' useSsh: true.
	Rowan projectTools load loadProjectNamed: 'RowanSample1'.

The two lines of code you show will certainly create (if needed) and load the RowanSample1 project, however it is not a good practice for tests to download projects into $ROWAN_PROJECTS_HOME ... you run the risk of installing a project into a user's space and potentially disrupting the user's own work ... I think what happened in this case is that you starting using my local version of RowanSample1 and it so happens that I don't have my repo on a branch that you were expecting so the tests are failing ...
A better practice for tests is to use the test scratch directory for installing test projects: Rowan/test/testRepositories/repos and using this test code as a template for installing your repositories ... This way the test code is under your total control and cannot affect the users own ROWAN_PROJECTS_HOME.

@dalehenrich  Trying to implement the code you referred to  ...
This line of code (shown below in the debugger) appears to expect a .ston file which does not exist in the RowanSample1 repository. Is it generated in the rowan tests somehow?  Or should I be pulling RowanSample1 from somewhere other than https://github.com/dalehenrich/RowanSample1

It looks like the path in the debugger is referring to this directory in the RowanSample1 and there are two .ston files to choose from ... I'd suggest this one: RowanSample1.ston  ...

That seemed, at first glance, to get my over the hurdle.

RowanSample1 load updated in test & subclass created on fly to avoid dependency on disk version of project. Should be fixed in Oscar 3.0.54 but I'll double check before releasing.


feat: Fetching chain_id

Resolves: #673
Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Testing

What is the new behavior?
chain_id is fetched using kakarot client instead of hardcoded
Does this introduce a breaking change?

[ ] Yes
[x] No

This change is

@Eikix  a few comments :
in src/starknet_client/mod.rs :
        let chain_id = request.chain_id.unwrap();
```  will just panic if the request fails. Should i still use `unwrap_or_else` with a hardcoded value?

in tests/test_utils/evm_contract.rs , i don't see how to grab chain_id , as there is not kakarot client, and therefore no starknet_provider to use. Currently, i removed the hardcoded chain_id and set chain_id to 0 in this file. What would be the best option?

@Eikix  sorry this completely forgot about this PR.
I made some changes, tell me if this is correct. I'm really new with Rust.
I still need to refactor

@Eikix  could i have a hint about how to do this refactoring? i'm not sure how to proceed


⚠ Bofrost.lu has degraded performance

In dbda91a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1058 ms

Resolved: Bofrost.lu performance has improved in c2ed681.


RFC: tempfile: Add build-time global prefix for temporary files

This is mostly useful for sandboxed Linux environments that
restrict access to /dev/shm/{...}, specifically snaps, which
require a "snap.{appname}." prefix.
Can bet set at build-time via ldflags.
Not terribly elegant but rather simple. I'd need something like this for my ongoing snap-packaging efforts, so consider this a conversation starter.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1185   +/-   ##
=======================================
  Coverage   62.55%   62.55%
=======================================
  Files         184      184
  Lines       10273    10273
=======================================
  Hits         6426     6426
  Misses       3045     3045
  Partials      802      802

Impacted Files
Coverage Δ

pkg/tempfile/file.go
71.43% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


coverage: shard coverage tests

Signed-off-by: Lizan Zhou<EMAIL_ADDRESS>Description:
Risk Level: Low
Testing:
Docs Changes:
Release Notes:

Yeah in Circle is 40mins vs 30mins, the test running time is down from 10mins to 1min.

Thanks!


The second message is selected automatically after moving the first message

Storage Explorer Version: 1.32.0-dev (93)
Build Number: 20230928.9
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Ventura 13.5 (Apple M1 Pro)
Architecture: x64/x64/x64
How Found: From running testing
Regression From: Previous release (1.31.1)
Steps to Reproduce

Expand one storage account -> Queues.
Create two queues -> Right click one queue -> Click '[NEW] Open in New Tab'.
Add two messages -> Select first message -> Click 'Move -> Move Selected' -> Select another queue -> Move.
Check whether the second message is not selected automatically.

Expected Experience
The second message is not selected automatically.

Actual Experience
The second message is selected automatically.

Verified this issue on the main build 20231007.7. Fixed. So we are going to close it.


Watch every resource managed by the operator

If something changes - like a deployment is mistakenly deleted - the operator will reconcile the state.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Two things is currently under development for the PR.

the related object reconcile triggering is going to be configurable
fix #73


Can't find file of buffer

When I try to convert the mp3 file I get this error:
Error: ENOENT: no such file or directory, unlink '/Users/test/Projects/proba-mp3/node_modules/node-lame/lib/build/../../temp/encoded/5op8Wh0WgCuDsYDddmAqeE6I5ICQbzT4'
It doesn't matter what I use - file or buffer, I get this error.
npm version: 6.0.1
node version: 9.4.0

I had the same issue just a moment ago on Windows, my problem was that the lame installation wasn't in the env path since I forgot about to add it after installing it .

ENOENT: no such file or directory, unlink

Excuse my late reply, please.
Please make sure you have LAME installed, as @edumuj says. Also make sure that the input file exists.
If you still have problems using node-lame, please reopen this issue.


Fix typo

Ty for the PR .. please read and change the target branch: https://github.com/pivpn/pivpn#pull-requests

Apologies. I'll get that done

Actually it's with capital G.


useless

options on options
accounts on accounts

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: dac10c25-1625-4f0d-b113-a1fdd7a7a900
Version Independent ID: dac10c25-1625-4f0d-b113-a1fdd7a7a900
Content: Get started - Overview - Teams
Content Source: msteams-platform/get-started/get-started-overview.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: lajanuar

@edthehorse - Could you please elaborate your issue to investigate further?

thanks Nivedipa but id rather not.
i spent 1/2 day yesterday and got nowhere  with it.
I understand that "sandbox" can short circuit all this configuration
stuff so i might try that.
On 05/06/2023 05:51, Nivedipa-MSFT wrote:

@edthehorse [1] - Could you please elaborate your issue to investigate
further?
--
Reply to this email directly, view it on GitHub [2], or unsubscribe
[3].
You are receiving this because you were mentioned.Message ID:
@.***>

Links:
[1] https://github.com/edthehorse
[2]
https://github.com/MicrosoftDocs/msteams-docs/issues/8781#issuecomment-1576037149
[3]
https://github.com/notifications/unsubscribe-auth/AB6M5UFLRS3TEH3VVE5XVZ3XJVQVFANCNFSM6AAAAAAYZ6O45A


Add Output Transformer to set aggregate labels fields Secret at runtime

Missing a few test cases. Thinking this is the correct direction.
Here's an example console output:
@guin:gcp-labels🦉 pulumi up
Previewing update (dev)

View in Browser (Ctrl+O): https://app.pulumi.com/guinevere-pulumi-corp/dev/dev/previews/5b1266d0-aaf1-4aa3-9aa3-faadf930618e

     Type                     Name          Plan       Info
 +   pulumi:pulumi:Stack      dev-dev       create     2 warnings
 +   ├─ pulumi:providers:gcp  gcp-provider  create
 +   └─ gcp:storage:Bucket    my-bucket     create

Diagnostics:
  pulumi:pulumi:Stack (dev-dev):
    warning: using pulumi-resource-gcp from $PATH at /Users/guin/go/src/github.com/pulumi/pulumi-gcp/bin/pulumi-resource-gcp
    warning: using pulumi-resource-gcp from $PATH at /Users/guin/go/src/github.com/pulumi/pulumi-gcp/bin/pulumi-resource-gcp

Outputs:
    bucketName       : output<string>
    pulumiAllLabels  : [secret]
    resourceSetLabels: [secret]

Resources:
    + 3 to create

Do you want to perform this update? yes
Updating (dev)

View in Browser (Ctrl+O): https://app.pulumi.com/guinevere-pulumi-corp/dev/dev/updates/75

     Type                     Name          Status              Info
 +   pulumi:pulumi:Stack      dev-dev       created (4s)        2 warnings
 +   ├─ pulumi:providers:gcp  gcp-provider  created (0.08s)
 +   └─ gcp:storage:Bucket    my-bucket     created (2s)

Diagnostics:
  pulumi:pulumi:Stack (dev-dev):
    warning: using pulumi-resource-gcp from $PATH at /Users/guin/go/src/github.com/pulumi/pulumi-gcp/bin/pulumi-resource-gcp
    warning: using pulumi-resource-gcp from $PATH at /Users/guin/go/src/github.com/pulumi/pulumi-gcp/bin/pulumi-resource-gcp

Outputs:
    bucketName       : "gs://my-bucket-e7310c1"
    pulumiAllLabels  : [secret]
    resourceSetLabels: [secret]

Resources:
    + 3 created

Duration: 5s

Closing via #1238


PersistentVolumeClaim is not bound: "es-data-es-data-example-es-cluster-hostpath-storage-0"

Kubernetes 1.9
I used the examples as listed in master
controller.yaml
example-es-cluster-hostpath.yaml
hostpath-sc.yaml
as is
I am getting this error.
PersistentVolumeClaim is not bound: "es-data-es-data-example-es-cluster-hostpath-storage-0"
Is the example missing another YAML for the PVC?

I think I am onto something looks like hostpath is Will not work in a multinode environment.
I have a baremetal 5 node cluster. I guess there is no way to use the local drives in my case.
Would you suggest a NSF Setup and if so could you let me know what would need to change in the es-cluster-??? and what a new nsf-sc.yaml would look like? Thanks

After some heavy googling I have came to this as a possible solution for local store for Baremetal Clusters Released in Kubernetes 1.9..Volume Topology-aware Scheduling
https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/volume-topology-scheduling.md
This looks promising for the issue of local PV for multi node K8's  Would the current operator take into account this Bound PVC Enforcement for Node Scheduling.

Thanks, Ya I am currently looking at the NSF vol option but the issue will be performance. Where as the solution in the link would allow the local storage in Multi Node Clusters.

Awesome! Let me know if you need more help or have questions, just re-open. =)

Hi @stevesloka. Could you elaborate a little on why local hostPath storage will not work for multi-node ElasticSearch cluster?


Add files via upload

What the program do ?

In what programming language it is written?

This pull request do not contains files in specific folders. Please fix it and reopen


How do I change the icon Opengts web is already integrated with traccar?

Hi All Parties,
Please help me to change the icon point.png become car.png on OpenGTS. Thanks

You should ask this question in OpenGTS project. It's not related to Traccar.


Update package.json

Update marked to fix sanitization issue on david-dm

Thanks for contributing!

Sorry, wrong button :laughing:


Optimize key partition

What problem does this PR solve?
#1410
Fixed the problem that indices were not sorted correctly.

/run-all-tests tikv=v3.1.0 tidb=v3.1.0 pd=v3.1.0


pyenv + pipenv: Linting fails: E0401 Unable to import  (import-error)

DISCLAIMER: I am new to python.
DISCLAIMER 2: I have found similar issues on this repository, but they are closed and locked and did not answer my problem, so here I am.
Environment data

VS Code Version: 1.43.2
Extension version: 2020.3.69010 (19 March 2020)
OS: Darwin x64 17.7.0
Python version: 3.7.7
Pyenv version: 1.2.17
Type of virtual environment used: pipenv
pipenv: 2018.11.26
pylint: 2.4.4
black: 19.10b0
python.jediEnabled: default
python.languageServer: default

Gist
Gist with all the file of the projects bar Dockerfile & README.md can be found here
Expected behaviour
Two behaviours:

pylint main.py in terminal in folder should result in the same result as the linting in editor.

flask is installed locally using pipenv and thus if the setup is done properly, should not return an error for both in terminal and in editor.

Misc:

formatting (black) on save works

Actual behaviour
Behaviour 1:
pylint main.py in the terminal outputs the following errors:
************* Module main
main.py:1:0: C0114: Missing module docstring (missing-module-docstring)
main.py:4:0: E0401: Unable to import 'flask' (import-error)
main.py:11:0: C0116: Missing function or method docstring (missing-function-docstring)
main.py:16:0: C0116: Missing function or method docstring (missing-function-docstring)

------------------------------------------------------------------
Your code has been rated at 2.00/10 (previous run: 5.00/10, -3.00)

while in the editor, only main.py:4:0: E0401: Unable to import 'flask' (import-error) is caught. Hence linting on open and save does not output convention linting (C0XXX) errors.
Behaviour 2:

linting on open and save outputs an E0401 import error for flask when flask seems to be properly installed.

Misc:

formatting (black) on save works

Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Once again: Gist with all the file of the projects bar Dockerfile & README.md can be found here
I have gone through a lot of github issues (including some from here answered by @DonJayamanne) to try to figure this one out, without success.
As you can see by now my settings.json is starting to be fat from all the specified settings for python.
I have tried the following combinations:
Pipenv:

black & pylint installed in Pipfile + /Users/philippefutureboy/.pyenv/shims/{black,pylint} in settings.json:{python.linting.pylintPath, python.formatting.blackPath}
black & pylint installed in Pipfile + /Users/philippefutureboy/.pyenv/version/3.7.7/bin/{black,pylint} in settings.json:{python.linting.pylintPath, python.formatting.blackPath}

Pip in Pyenv:

black & pylint installed in pyenv using pip + paths in settings.json pointing to the bin folder of current python env, /Users/philippefutureboy/.pyenv/versions/3.7.7/bin
black & pylint installed in pyenv using pip + paths in settings.json pointing to the shims /Users/philippefutureboy/.pyenv/shims/{black,pylint}

Logs
> ~/.pyenv/versions/3.7.7/bin/pylint --disable=all --enable=F,unreachable,duplicate-key,unnecessary-semicolon,global-variable-not-assigned,unused-variable,unused-wildcard-import,binary-op-exception,bad-format-string,anomalous-backslash-in-string,bad-open-mode,E0001,E0011,E0012,E0100,E0101,E0102,E0103,E0104,E0105,E0107,E0108,E0110,E0111,E0112,E0113,E0114,E0115,E0116,E0117,E0118,E0202,E0203,E0211,E0213,E0236,E0237,E0238,E0239,E0240,E0241,E0301,E0302,E0303,E0401,E0402,E0601,E0602,E0603,E0604,E0611,E0632,E0633,E0701,E0702,E0703,E0704,E0710,E0711,E0712,E1003,E1101,E1102,E1111,E1120,E1121,E1123,E1124,E1125,E1126,E1127,E1128,E1129,E1130,E1131,E1132,E1133,E1134,E1135,E1136,E1137,E1138,E1139,E1200,E1201,E1205,E1206,E1300,E1301,E1302,E1303,E1304,E1305,E1306,E1310,E1700,E1701 --msg-template='{line},{column},{category},{symbol}:{msg}' --reports=n --output-format=text ~/Documents/Arthur/arthur-monorepo/pink-dolphin/pipeline/postprocessor/main.py
cwd: ~/Documents/Arthur/arthur-monorepo/pink-dolphin/pipeline/postprocessor
##########Linting Output - pylint##########
************* Module main
4,0,error,import-error:Unable to import 'flask'

------------------------------------------------------------------
Your code has been rated at 5.00/10 (previous run: 5.00/10, +0.00)

Well from reading the above I see that C0XXX (convention) linting is disabled. Is that normal, and how can I enable it if I want it?

Thank you for your answers!
Cheers,
Philippe

Hi @philippefutureboy, thank you for reaching out.
We have a set of minimal checkers we use with pylint, so if you want to customize them you'll have to disable them all with "python.linting.pylintUseMinimalCheckers": "false" in your settings, or by unchecking this setting in the settings UI:

You can then re-add the ones you want in the python.linting.pylintArgs setting:

Hi @kimadeline :)
Thanks for your answer! It definitely solves the first of the two behaviours - Great!
As for the second one, any idea how to solve the problems with "E0401 - Unable to import" error?
Thanks a lot!
Cheers,
Philippe

It is not related to the extension, since you said that you get this error when you run pylint main.py in the terminal.
Please note that you shouldn't have to specify the python.pylintPath setting, since it's installed in the same environment as the Python interpreter for this workspace.
What happens if you call ~/.pyenv/versions/3.7.7/bin/python -m pylint ~/Documents/Arthur/arthur-monorepo/pink-dolphin/pipeline/postprocessor/main.py, or ~/.pyenv/versions/3.7.7/bin/python -c "import flask" directly in your terminal?

Hi @kimadeline!
Sorry for the delay in answers, it's quite hectic at work these days 🙃
Here's the answer to your question:
Call to ~/.pyenv/versions/3.7.7/bin/python -m pylint ~/Documents/Arthur/arthur-monorepo/pink-dolphin/pipeline/postprocessor/main.py results in:
************* Module main
main.py:1:0: C0114: Missing module docstring (missing-module-docstring)
main.py:4:0: E0401: Unable to import 'flask' (import-error)
main.py:11:0: C0116: Missing function or method docstring (missing-function-docstring)
main.py:16:0: C0116: Missing function or method docstring (missing-function-docstring)

------------------------------------------------------------------
Your code has been rated at 2.00/10 (previous run: 2.00/10, +0.00)

(same behaviour essentially)
 ~/.pyenv/versions/3.7.7/bin/python -c "import flask" results in:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'flask'

And pipenv run start (equivalent to python main.py, where which python returns /Users/philippefutureboy/.pyenv/shims/python) returns:
* Serving Flask app "main" (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)

Does that give you any additional information?
To note: I did not remove the python.pylintPath before running these commands. Should I have?
Thanks a lot for your help, it is really appreciated 🌟

~/.pyenv/versions/3.7.7/bin/python -c "import flask" results in:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'flask'

Flask isn't installed in this environment, which explains why pylint won't find it.
I suspect that when you run python main.py via pipenv run start this python executable isn't the same as ~/.pyenv/versions/3.7.7/bin/python.

I did not remove the python.pylintPath before running these commands. Should I have?

It doesn't matter too much, if you specify python.pylintPath then whenever you call it in the extension we will call {value of python.pylintPath} file.py, while if you don't modify it then we'll call python -m pylint file.py.

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.


kubeinit Deployment in Fedora35 failing to complete

Describe the bug
After cloning kubeinit repository, and following all the steps on the README file, the deployment fails during:
TASK [kubeinit.kubeinit.kubeinit_services : Wait for connection to "okdcluster-credentials" container] **************************************************************************************
task path: /home/german/.ansible/collections/ansible_collections/kubeinit/kubeinit/roles/kubeinit_services/tasks/prepare_credentials.yml:101
Tuesday 08 February 2022  15:53:41 -0500 (0:00:00.065)       0:02:15.112 ******

Error:
fatal: [localhost -> okdcluster-credentials]: FAILED! => {
    "changed": false,
    "elapsed": 305,
    "msg": "timed out waiting for ping module test: Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo /tmp `\"&& mkdir \"` echo /tmp/ansible-tmp-1644353921.9780402-2437089-121246699102612 `\" && echo ansible-tmp-1644353921.9780402-2437089-121246699102612=\"` echo /tmp/ansible-tmp-1644353921.9780402-2437089-121246699102612 `\" ), exited with result 125"

To Reproduce
Steps to reproduce the behavior:

Clone '...'
Create an Alias for nyctea in /etc/hosts

cat /etc/hosts
<IP_ADDRESS>   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

<IP_ADDRESS> Server-TR	nyctea

Deploy ssh keys to nyctea.

if [ -f ~/.ssh/id_rsa ]; then
  ssh-keygen
  ssh-copy-id /root/.ssh/id_rsa root@nyctea
fi

Verified root access to nyctea with no password

ssh root@nyctea
Activate the web console with: systemctl enable --now cockpit.socket

Last login: Tue Feb  8 15:30:34 2022 from <IP_ADDRESS>
[root@Server-TR ~]#

Install requirements:

# Install the requirements assuming python3/pip3 is installed
pip3 install \
        --upgrade \
        pip \
        shyaml \
        ansible \
        netaddr

cd kubeinit

# Install the Ansible collection requirements
ansible-galaxy collection install --force --requirements-file kubeinit/requirements.yml

# Build and install the collection
rm -rf ~/.ansible/collections/ansible_collections/kubeinit/kubeinit
ansible-galaxy collection build kubeinit --verbose --force --output-path releases/
ansible-galaxy collection install --force --force-with-deps releases/kubeinit-kubeinit-`cat kubeinit/galaxy.yml | shyaml get-value version`.tar.gz

Run with these variable '...'

ansible-playbook \
    -v --user root \
    -e kubeinit_spec=okd-libvirt-3-1-1 \
    -i ./kubeinit/inventory \
    ./kubeinit/playbook.yml

See error

TASK [kubeinit.kubeinit.kubeinit_services : Wait for connection to "okdcluster-credentials" container] **************************************************************************************
task path: /home/german/.ansible/collections/ansible_collections/kubeinit/kubeinit/roles/kubeinit_services/tasks/prepare_credentials.yml:101
Tuesday 08 February 2022  15:53:41 -0500 (0:00:00.065)       0:02:15.112 ******

Error:
fatal: [localhost -> okdcluster-credentials]: FAILED! => {
    "changed": false,
    "elapsed": 305,
    "msg": "timed out waiting for ping module test: Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo /tmp `\"&& mkdir \"` echo /tmp/ansible-tmp-1644353921.9780402-2437089-121246699102612 `\" && echo ansible-tmp-1644353921.9780402-2437089-121246699102612=\"` echo /tmp/ansible-tmp-1644353921.9780402-2437089-121246699102612 `\" ), exited with result 125"

Expected behavior
An OKD cluster deployed with 3 Control and 1 Compute Nodes
Screenshots
If applicable, add screenshots to help explain your problem.
Infrastructure

Hypervisors OS: Fedora
Version : 35

Deployment command
ansible-playbook -vvv --user root \
    -e kubeinit_spec=okd-libvirt-3-1-1 \
    -i ./kubeinit/inventory \
    ./kubeinit/playbook.yml

Inventory file diff
Run the following command:
diff \
    <(curl https://raw.githubusercontent.com/Kubeinit/kubeinit/main/kubeinit/hosts/k8s/inventory) \
    <(curl https://raw.githubusercontent.com/Kubeinit/kubeinit/main/kubeinit/hosts/okd/inventory)

And paste the output:
here

Additional context
Add any other context about the problem here.
Deploying the cluster to my local Server-TR Fedora 35 which is also acting as Hypervisor-01

I was able to reproduce this in the CI, I was only able to provision the hosts with F35 so the issue is reproduced out of the box.
[root@nyctea ~]# podman ps
CONTAINER ID  IMAGE                                             COMMAND               CREATED        STATUS            PORTS                    NAMES
12e9c53c1d0b  k8s.gcr.io/pause:3.5                                                    6 minutes ago  Up 6 minutes ago  <IP_ADDRESS>:26973->8000/tcp  f00f36a649b7-infra
964c5f7879e7  docker.io/recordsansible/ara-api:latest           bash -c /usr/loca...  6 minutes ago  Up 6 minutes ago  <IP_ADDRESS>:26973->8000/tcp  api-server
d2718ae04ac9  k8s.gcr.io/pause:3.5                                                    4 minutes ago  Up 4 minutes ago                           ef1044587dd6-infra
af205bdd8a1a  localhost/kubeinit/k8scluster-credentials:latest  sleep infinity        3 minutes ago  Up 3 minutes ago                           k8scluster-credentials

[root@nyctea ~]# podman pod list
POD ID        NAME                    STATUS      CREATED        INFRA ID      # OF CONTAINERS
ef1044587dd6  k8scluster-service-pod  Running     4 minutes ago  d2718ae04ac9  2
f00f36a649b7  ara-pod                 Running     6 minutes ago  12e9c53c1d0b  2

[root@nyctea ~]# podman port -a
12e9c53c1d0b	8000/tcp -> <IP_ADDRESS>:26973
964c5f7879e7	8000/tcp -> <IP_ADDRESS>:26973

[root@nyctea ~]# podman ps -a --pod
CONTAINER ID  IMAGE                                             COMMAND               CREATED        STATUS            PORTS                    NAMES                   POD ID        PODNAME
12e9c53c1d0b  k8s.gcr.io/pause:3.5                                                    7 minutes ago  Up 7 minutes ago  <IP_ADDRESS>:26973->8000/tcp  f00f36a649b7-infra      f00f36a649b7  ara-pod
964c5f7879e7  docker.io/recordsansible/ara-api:latest           bash -c /usr/loca...  7 minutes ago  Up 7 minutes ago  <IP_ADDRESS>:26973->8000/tcp  api-server              f00f36a649b7  ara-pod
d2718ae04ac9  k8s.gcr.io/pause:3.5                                                    4 minutes ago  Up 4 minutes ago                           ef1044587dd6-infra      ef1044587dd6  k8scluster-service-pod
af205bdd8a1a  localhost/kubeinit/k8scluster-credentials:latest  sleep infinity        3 minutes ago  Up 3 minutes ago                           k8scluster-credentials  ef1044587dd6  k8scluster-service-pod

@Gl1TcH-1n-Th3-M4tR1x @gmarcy im not sure what is wrong here, Ill try to test F34 to see if there is something different there.

@Gl1TcH-1n-Th3-M4tR1x could you also tell us what the ansible playbook client side environment is like?  I can do the git clone on the same F35 host that I'm deploying to, similar to how the github actions run, but would like to match.  other thought would be to do the clone and run the container build and run the install from the container, just to rule out any issues in the host running the playbook.

The Ansible playbook client is the same Fedora 35 hypervisor-01, basically I run the ansible playbook from the Hypervisor, all I have is an alias for nyctea on my hypervisor-01. Let me try to run the build from the container.

@Gl1TcH-1n-Th3-M4tR1x found this in my fedora kickstart, wondering if you updated fedora to accept RSA keys?
update-crypto-policies --set DEFAULT:FEDORA32
I had forgotten about this as I had switched from rsa to ed25519 when I added support for the KUBEINIT_COMMON_SSH_KEYTYPE environment variable.
$ export | grep SSH_KEYTYPE
declare -x KUBEINIT_COMMON_SSH_KEYTYPE="ed25519"

More info here

@Gl1TcH-1n-Th3-M4tR1x are you running the ansible-playbook under root or a non-root user?

I'm running the playbook with a non-root user.

Running from the Container failed even faster:
TASK [kubeinit.kubeinit.kubeinit_prepare : Put secret values into a dictionary] *************************************************************************************************************
task path: /home/kiuser/.ansible/collections/ansible_collections/kubeinit/kubeinit/roles/kubeinit_prepare/tasks/gather_kubeinit_secrets.yml:39
skipping: [localhost] => (item=None)  => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false
}
skipping: [localhost] => (item=None)  => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false
}
skipping: [localhost] => (item=None)  => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false
}
skipping: [localhost] => (item=None)  => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false
}
skipping: [localhost] => (item=None)  => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false
}
skipping: [localhost] => (item=None)  => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false
}
skipping: [localhost] => (item=None)  => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false
}
skipping: [localhost] => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false
}

TASK [kubeinit.kubeinit.kubeinit_prepare : Add secrets to kubeinit secrets] *****************************************************************************************************************
task path: /home/kiuser/.ansible/collections/ansible_collections/kubeinit/kubeinit/roles/kubeinit_prepare/tasks/gather_kubeinit_secrets.yml:49
fatal: [localhost]: FAILED! => {
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result"
}

NO MORE HOSTS LEFT **************************************************************************************************************************************************************************

PLAY RECAP **********************************************************************************************************************************************************************************
localhost                  : ok=6    changed=1    unreachable=0    failed=1    skipped=3    rescued=0    ignored=0

@Gl1TcH-1n-Th3-M4tR1x found this in my fedora kickstart, wondering if you updated fedora to accept RSA keys?
update-crypto-policies --set DEFAULT:FEDORA32
I had forgotten about this as I had switched from rsa to ed25519 when I added support for the KUBEINIT_COMMON_SSH_KEYTYPE environment variable.
$ export | grep SSH_KEYTYPE
declare -x KUBEINIT_COMMON_SSH_KEYTYPE="ed25519"

More info here

Updated Fedora 35 crypto policies, and set KUBEINIT_COMMON_SSH_KEYTYPE to ed25519, and I've got:
TASK [kubeinit.kubeinit.kubeinit_prepare : Confirm that we have ansible host connectivity] **************************************************************************************************
task path: /home/german/.ansible/collections/ansible_collections/kubeinit/kubeinit/roles/kubeinit_prepare/tasks/gather_host_facts.yml:21
Thursday 10 February 2022  04:28:00 -0500 (0:00:00.074)       0:00:01.429 *****
Using module file /usr/local/lib/python3.10/site-packages/ansible/modules/ping.py
Pipelining is enabled.
<nyctea> ESTABLISH SSH CONNECTION FOR USER: root
<nyctea> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=accept-new -i '~/.ssh/id_ed25519' -o 'ControlPath="/home/german/.ansible/cp/19b2ae1270"' nyctea '/bin/sh -c '"'"'/usr/bin/python3 && sleep 0'"'"''
fatal: [localhost -> hypervisor-01]: UNREACHABLE! => {
    "changed": false,
    "msg": "Data could not be sent to remote host \"nyctea\". Make sure this host can be reached over ssh: Warning: Identity file /home/german/.ssh/id_ed25519 not accessible: No such file or directory.\nBad owner or permissions on /home/german/.ssh/config\r\n",
    "unreachable": true
}

PLAY RECAP **********************************************************************************************************************************************************************************
localhost                  : ok=37   changed=6    unreachable=1    failed=0    skipped=11   rescued=0    ignored=0

Running from the Container failed even faster:

I am so sorry... I've fallen behind on keeping the docs up to date with the code. We switched from volume mounts to podman secrets for ssh keys, so instead of mounting ~/.ssh keys in the container you would do
podman secret create kubeinit_ssh_key ~/.ssh/id_<keytype>
podman run --secret kubeinit_ssh_key ...

that would replace the params
    -v ~/.ssh/id_rsa:/root/.ssh/id_rsa:z \
    -v ~/.ssh/id_rsa.pub:/root/.ssh/id_rsa.pub:z \

After creating nyctea as a Virtual machine with CentOS8-Stream and a podman secret with:
podman secret create kubeinit_ssh_key ~/.ssh/id_rsa

And running:
podman run --rm -it --secret kubeinit_ssh_key -v ~/.ssh/config:/root/.ssh/config.z kubeinit/kubeinit -vvv --user root -e kubeinit_spec=okd-libvirt-3-1-1 -i ./kubeinit/inventory ./kubeinit/playbook.yml

Kubeinit went all the way to:
TASK [kubeinit.kubeinit.kubeinit_libvirt : Wait for changes to propagate] *************************************************************************
task path: /home/kiuser/.ansible/collections/ansible_collections/kubeinit/kubeinit/roles/kubeinit_libvirt/tasks/cleanup_libvirt.yml:132
Using module file /home/kiuser/.local/lib/python3.9/site-packages/ansible/modules/command.py
Pipelining is enabled.
<nyctea> ESTABLISH SSH CONNECTION FOR USER: root
<nyctea> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=accept-new -i '~/.ssh/id_rsa' -o 'ControlPath="/home/kiuser/.ansible/cp/19b2ae1270"' nyctea '/bin/sh -c '"'"'/usr/bin/python3 && sleep 0'"'"''
<nyctea> (1, b'\n{"changed": true, "stdout": "", "stderr": "2022-02-10T21:37:09Z|00001|fatal_signal|WARN|terminating with signal 14 (Alarm clock)", "rc": -14, "cmd": ["/usr/bin/ovn-nbctl", "--wait=hv", "--timeout=30", "sync"], "start": "2022-02-10 16:36:39.303190", "end": "2022-02-10 16:37:09.338535", "delta": "0:00:30.035345", "failed": true, "msg": "non-zero return code", "invocation": {"module_args": {"_raw_params": "/usr/bin/ovn-nbctl --wait=hv --timeout=30 sync", "_uses_shell": false, "warn": false, "stdin_add_newline": true, "strip_empty_ends": true, "argv": null, "chdir": null, "executable": null, "creates": null, "removes": null, "stdin": null}}}\n', b'')
<nyctea> Failed to connect to the host via ssh:
fatal: [localhost -> hypervisor-01(nyctea)]: FAILED! => {
    "changed": false,
    "cmd": [
        "/usr/bin/ovn-nbctl",
        "--wait=hv",
        "--timeout=30",
        "sync"
    ],
    "delta": "0:00:30.035345",
    "end": "2022-02-10 16:37:09.338535",
    "invocation": {
        "module_args": {
            "_raw_params": "/usr/bin/ovn-nbctl --wait=hv --timeout=30 sync",
            "_uses_shell": false,
            "argv": null,
            "chdir": null,
            "creates": null,
            "executable": null,
            "removes": null,
            "stdin": null,
            "stdin_add_newline": true,
            "strip_empty_ends": true,
            "warn": false
        }
    },
    "msg": "non-zero return code",
    "rc": -14,
    "start": "2022-02-10 16:36:39.303190",
    "stderr": "2022-02-10T21:37:09Z|00001|fatal_signal|WARN|terminating with signal 14 (Alarm clock)",
    "stderr_lines": [
        "2022-02-10T21:37:09Z|00001|fatal_signal|WARN|terminating with signal 14 (Alarm clock)"
    ],
    "stdout": "",
    "stdout_lines": []
}

PLAY RECAP ****************************************************************************************************************************************
hypervisor-01              : ok=17   changed=3    unreachable=0    failed=0    skipped=8    rescued=0    ignored=0
hypervisor-02              : ok=0    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0
localhost                  : ok=173  changed=40   unreachable=0    failed=1    skipped=51   rescued=0    ignored=0

After creating nyctea as a Virtual machine with CentOS8-Stream and a podman secret with:

I don't believe that hypervisors can be virtual machines without a lot of extra effort, some kernel dependencies in the openvswitch/ovn services if I remember correctly.

@Gl1TcH-1n-Th3-M4tR1x I was able to deploy a cluster from the container built from main using the following command
podman run --rm -ti -e KUBEINIT_COMMON_SSH_KEYTYPE --secret kubeinit_ssh_key kubeinit/kubeinit -e kubeinit_hypervisor_hosts_spec='[[host=hypervisor-01,ssh_hostname=<IP_ADDRESS>]]' -vvv --user root -e kubeinit_spec=okd-libvirt-3-1-1 -i ./kubeinit/inventory ./kubeinit/playbook.yml

The replacement for the ssh config volume mount
-v ~/.ssh/config:/root/.ssh/config.z

was
-e kubeinit_hypervisor_hosts_spec='[[host=hypervisor-01,ssh_hostname=<IP_ADDRESS>]]'

Apologies again for not keeping up with the docs on this change.  When we switched to running kubeinit/kubeinit as a non-root container it made volume mounts unreliable and so they were replaced with a new mechanism.

update-crypto-policies --set DEFAULT:FEDORA32

This fixed the issue in my F35 box, from the standard deployment methods without containers.

Hi @Gl1TcH-1n-Th3-M4tR1x this is what I did (what is running in the CI).

Deploy a fresh F35 machine.
From the install node script 1 install the dependencies.
This would be in your case:
* https://github.com/Kubeinit/kubeinit/blob/main/ci/install_gitlab_node.sh#L43-L59
* https://github.com/Kubeinit/kubeinit/blob/main/ci/install_gitlab_node.sh#L102-L119
* https://github.com/Kubeinit/kubeinit/blob/main/ci/install_gitlab_node.sh#L158-L182
* https://github.com/Kubeinit/kubeinit/blob/main/ci/install_gitlab_node.sh#L210-L230
Run the deployment from what is in the readme (I didn't do any other additional change).

If you see the script, the only 'new' thing is this command update-crypto-policies --set DEFAULT:FEDORA32.
This is an example of a successful CI job with the previous steps https://storage.googleapis.com/kubeinit-ci/jobs/okd-libvirt-1-1-1-h-periodic-pid-weekly-u/records/1.html running the previous steps.
@gmarcy did an amazing job putting these prepare steps in a playbook2 but I didn't find time to integrate it in the CI.

After Deploy a fresh F5 machine my steps are:
$ cat /etc/os-release
NAME="Fedora Linux"
VERSION="35 (Thirty Five)"
ID=fedora
VERSION_ID=35
...
$ update-crypto-policies --show
DEFAULT:FEDORA32
$ sudo dnf install -y git podman
...
$ git --version
git version 2.35.1
$ podman --version
podman version 3.4.4
$ export  KUBEINIT_COMMON_SSH_KEYTYPE="ed25519"
$ ssh-keygen -t ed25519
...
$ sudo mkdir ~root/.ssh
$ sudo chmod 700 ~root/.ssh
$ sudo cp ~/.ssh/id_ed25519.pub ~root/.ssh/authorized_keys
$ ssh root@<ip-address> python3 -V
Python 3.10.0
$ podman secret create kubeinit_ssh_key ~/.ssh/id_ed25519
...
$ git clone https://github.com/Kubeinit/kubeinit.git
...
$ cd kubeinit
$ podman build -t kubeinit/kubeinit .
...
$ podman run --rm -ti -e KUBEINIT_COMMON_SSH_KEYTYPE --secret kubeinit_ssh_key kubeinit/kubeinit -e hypervisor_hosts_spec='[[host=hypervisor-01,ssh_hostname=<ip-address>]]' -vvv --user root -e kubeinit_spec=okd-libvirt-3-1-1 -i ./kubeinit/inventory ./kubeinit/playbook.yml
...
I would be very interested in knowing if this does not work properly for you.

Here what I did, Created a fresh FC35 server, followed your instructions to the letter, and the podman deployment got stuck on exactly the same place:
podman run --rm -ti -e KUBEINIT_COMMON_SSH_KEYTYPE --secret kubeinit_ssh_key kubeinit/kubeinit -e hypervisor_hosts_spec='[[host=hypervisor-01,ssh_hostname=<ip-address>]]' -vvv --user root -e kubeinit_spec=okd-libvirt-3-1-1 -i ./kubeinit/inventory ./kubeinit/playbook.yml

a

After Deploy a fresh F35 machine my steps are:
$ cat /etc/os-release NAME="Fedora Linux" VERSION="35 (Thirty Five)" ID=fedora VERSION_ID=35 ... $ update-crypto-policies --show DEFAULT:FEDORA32 $ sudo dnf install -y git podman ... $ git --version git version 2.35.1 $ podman --version podman version 3.4.4 $ export KUBEINIT_COMMON_SSH_KEYTYPE="ed25519" $ ssh-keygen -t ed25519 ... $ sudo mkdir ~root/.ssh $ sudo chmod 700 ~root/.ssh $ sudo cp ~/.ssh/id_ed25519.pub ~root/.ssh/authorized_keys $ ssh root@<ip-address> python3 -V Python 3.10.0 $ podman secret create kubeinit_ssh_key ~/.ssh/id_ed25519 ... $ git clone https://github.com/Kubeinit/kubeinit.git ... $ cd kubeinit $ podman build -t kubeinit/kubeinit . ... $ podman run --rm -ti -e KUBEINIT_COMMON_SSH_KEYTYPE --secret kubeinit_ssh_key kubeinit/kubeinit -e hypervisor_hosts_spec='[[host=hypervisor-01,ssh_hostname=<ip-address>]]' -vvv --user root -e kubeinit_spec=okd-libvirt-3-1-1 -i ./kubeinit/inventory ./kubeinit/playbook.yml ...
I would be very interested in knowing if this does not work properly for you since this is the direction we expect future updates to take.

Here what I did, Created a brand new Bare-Metal FC35 Workstation with 32 Cores, 256GB RAM and 4 TB HDD, followed your instructions to the letter and after running the podman run command, it got stuck exactly at the same step as before:
TASK [kubeinit.kubeinit.kubeinit_okd : Verify that controller nodes are ok] *******************************
task path: /home/kiuser/.ansible/collections/ansible_collections/kubeinit/kubeinit/roles/kubeinit_okd/tasks/main.yml:41
Using module file /home/kiuser/.local/lib/python3.9/site-packages/ansible/modules/command.py
Pipelining is enabled.
<<IP_ADDRESS>> ESTABLISH SSH CONNECTION FOR USER: root
<<IP_ADDRESS>> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=accept-new -i '~/.ssh/okdcluster_id_ed25519' -o 'ProxyCommand=ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=accept-new -i ~/.ssh/okdcluster_id_ed25519 -W %h:%p -q root@nyctea' -o 'ControlPath="/home/kiuser/.ansible/cp/2a631e4199"' <IP_ADDRESS> '/bin/sh -c '"'"'/usr/bin/python3 && sleep 0'"'"''
<<IP_ADDRESS>> (1, b'\n{"changed": true, "stdout": "", "stderr": "Unable to connect to the server: EOF", "rc": 1, "cmd": "set -o pipefail\\nexport KUBECONFIG=~/install_dir/auth/kubeconfig; oc get nodes | grep master | grep \\" Ready\\"\\n", "start": "2022-02-15 21:12:20.071571", "end": "2022-02-15 21:13:10.182005", "delta": "0:00:50.110434", "failed": true, "msg": "non-zero return code", "invocation": {"module_args": {"executable": "/bin/bash", "_raw_params": "set -o pipefail\\nexport KUBECONFIG=~/install_dir/auth/kubeconfig; oc get nodes | grep master | grep \\" Ready\\"\\n", "_uses_shell": true, "warn": false, "stdin_add_newline": true, "strip_empty_ends": true, "argv": null, "chdir": null, "creates": null, "removes": null, "stdin": null}}}\n', b"Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.\r\n")
<<IP_ADDRESS>> Failed to connect to the host via ssh: Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
FAILED - RETRYING: [localhost -> service]: Verify that controller nodes are ok (60 retries left).Result was: {
    "attempts": 1,
    "changed": false,
    "cmd": "set -o pipefail\nexport KUBECONFIG=~/install_dir/auth/kubeconfig; oc get nodes | grep master | grep \" Ready\"\n",
    "delta": "0:00:50.110434",
    "end": "2022-02-15 21:13:10.182005",
    "invocation": {
        "module_args": {
            "_raw_params": "set -o pipefail\nexport KUBECONFIG=~/install_dir/auth/kubeconfig; oc get nodes | grep master | grep \" Ready\"\n",
            "_uses_shell": true,
            "argv": null,
            "chdir": null,
            "creates": null,
            "executable": "/bin/bash",
            "removes": null,
            "stdin": null,
            "stdin_add_newline": true,
            "strip_empty_ends": true,
            "warn": false
        }
    },
    "msg": "non-zero return code",
    "rc": 1,
    "retries": 61,
    "start": "2022-02-15 21:12:20.071571",
    "stderr": "Unable to connect to the server: EOF",
    "stderr_lines": [
        "Unable to connect to the server: EOF"
    ],
    "stdout": "",
    "stdout_lines": []
}

Created a brand new Bare-Metal FC35 Workstation

Server or Workstation?
I'm booting from
https://download.fedoraproject.org/pub/fedora/linux/releases/34/Server/x86_64/iso/Fedora-Server-dvd-x86_64-34-1.2.iso
Minimal package install - anaconda-ks.cfg has
%packages
@^custom-environment
@standard

%end

Just trying to understand where the differences are coming from.
My output for the same task is identical to yours, but my response is
<<IP_ADDRESS>> (1, b'\n{"changed": true, "stdout": "", "stderr": "No resources found", "rc": 1, "cmd": "set -o pipefail\\nexport KUBECONFIG=~/install_dir/auth/kubeconfig; oc get nodes | grep master | grep \\" Ready\\"\\n", "start": "2022-02-15 18:39:41.902631", "end": "2022-02-15 18:39:42.249062", "delta": "0:00:00.346431", "failed": true, "msg": "non-zero return code", "invocation": {"module_args": {"executable": "/bin/bash", "_raw_params": "set -o pipefail\\nexport KUBECONFIG=~/install_dir/auth/kubeconfig; oc get nodes | grep master | grep \\" Ready\\"\\n", "_uses_shell": true, "warn": false, "stdin_add_newline": true, "strip_empty_ends": true, "argv": null, "chdir": null, "creates": null, "removes": null, "stdin": null}}}\n', b"Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.\r\n")
<<IP_ADDRESS>> Failed to connect to the host via ssh: Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
FAILED - RETRYING: [localhost -> service]: Verify that controller nodes are ok (60 retries left).Result was: {

I'm using Fedora-Workstation-Live-x86_64-35-1.2.iso

Not sure, but it looks like the coreOS VMs are not getting ipaddresses:
virsh # list
 Id   Name                       State
------------------------------------------
 6    okdcluster-bootstrap       running
 8    okdcluster-controller-01   running
 10   okdcluster-controller-02   running
 12   okdcluster-controller-03   running

virsh # domiflist okdcluster-bootstrap
 Interface        Type     Source      Model    MAC
-------------------------------------------------------------------
 veth0-0a000005   bridge   kimgtnet0   virtio   52:54:00:c0:6f:53

 virsh # domiflist okdcluster-controller-01
 Interface        Type     Source      Model    MAC
-------------------------------------------------------------------
 veth0-0a000001   bridge   kimgtnet0   virtio   52:54:00:35:a0:d6

virsh # domiflist okdcluster-controller-02
 Interface        Type     Source      Model    MAC
-------------------------------------------------------------------
 veth0-0a000002   bridge   kimgtnet0   virtio   52:54:00:4b:00:a8

virsh # domiflist okdcluster-controller-03
 Interface        Type     Source      Model    MAC
-------------------------------------------------------------------
 veth0-0a000003   bridge   kimgtnet0   virtio   52:54:00:9b:04:11

virsh # domifaddr okdcluster-bootstrap
 Name       MAC address          Protocol     Address
-------------------------------------------------------------------------------

virsh # domifaddr okdcluster-controller-01
 Name       MAC address          Protocol     Address
-------------------------------------------------------------------------------

virsh # domifaddr okdcluster-controller-02
 Name       MAC address          Protocol     Address
-------------------------------------------------------------------------------

virsh # domifaddr okdcluster-controller-03
 Name       MAC address          Protocol     Address
-------------------------------------------------------------------------------

virsh #

Still trying to get anything working on F35 Workstation, behaves like a different operating system than F35 Server.  Noticing in particular that libvirtd is often inactive even when there are virtual machines running, so we don't always cleanup old virtual machines.

Where do the VMs get the IP Address from? when created, the VMs are configured to use dhcp and get connected to br-int bridge.

IIRC, it's a combination of things...
# ovn-nbctl show
switch 7c611c5c-be12-4382-a6a1-95da0b35882a (sw-okdcluster)
    port sw-okdcluster-lr0
        type: router
        router-port: lr0-sw-okdcluster
    port bc2788b6-44ac-5cc8-b682-2e136f346347
        addresses: ["52:54:00:11:9f:95 <IP_ADDRESS>"]
    port 9a1cf3eb-91a4-568e-8a83-a9571341c0d7
        addresses: ["52:54:00:41:8d:6d <IP_ADDRESS>"]
    port 2468be6a-70a0-5172-bae3-3ee42af2b4a6
        addresses: ["52:54:00:cb:2c:dd <IP_ADDRESS>"]
    port 011de5eb-faba-5cf3-9765-3781278fb400
        addresses: ["52:54:00:92:77:d0 <IP_ADDRESS>"]

and
# ovs-vsctl list interface veth0-0a000001
...
external_ids        : {attached-mac="52:54:00:92:77:d0", iface-id="011de5eb-faba-5cf3-9765-3781278fb400", iface-status=active, ovn-installed="true", ovn-installed-ts="1645218538948", vm-id="800814ee-19d5-4ea6-a291-028443ffe8ea"}

Switched to CentOS8-Stream for the Hypervisor and deployed with the quay image method.


move database seeding into yarn db command

database now gets seeded with data from the json files in db/seedData/ when yarn db is run

This personally looks good to me.. nice work!

@timdavish Cheers! Did you run it on your machine and it worked okay?

Yep! Was able to log in as Kevin as well


Code injection while using side by side preview not working

I have a css style inserted in my code injection. Everything looks good but when I am using the side by side preview modus in ghost the html code don't show up.
Can this be fixed?
I really like when I see my working html code in live preview modus.

@squadramunter This is by design - the side-by-side preview is meant to be a simple preview of what the post content would look like. However, implementing this has the potential to mess up other things - e.g. if you write some css in the post code injection and it gets rendered, it could potentially mess up how Ghost-Admin functions. If you're wanting more of a live-preview, there is the preview link which you can access from the PSM.
All that aside, I'm going to close this because we use Github to track bugs and ongoing feature work - if you wish to submit a feature request please use https://ideas.ghost.org. Thank you! 😄


feat: add basic support for alarm creation and adapting for SQS

@voho I think it is now the right time to take inputs from @eladb on the new implementation. Alarms will be a critical part I feel.

Agree, I will try to extend the PR description on why I decided to do things the way they are.

Hi folks, how do we proceed? Anyone willing to review this?


Day384

Resolves #776.

Pull Request Test Coverage Report for Build 1476

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1474:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


FullyConnected reference_integer_ops miscalculate output data due to endianness issue on s390x

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 2.3.1
Python version: 3.6.9
Bazel version (if compiling from source): 3.4.1
GCC/Compiler version (if compiling from source): Ubuntu 7.5.0-3ubuntu1~18.04
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
The Test case //tensorflow/lite/micro/examples/hello_world:hello_world_test failed on s390x with error:
Testing LoadModelAndPerformInference
0. (1.0*2^-127) near value (-1.1018541*2^0) failed at tensorflow/lite/micro/examples/hello_world/hello_world_test.cc:103
0.841 (1.6819992*2^-1) near value (-1.1018541*2^0) failed at tensorflow/lite/micro/examples/hello_world/hello_world_test.cc:111
0.141 (1.1279996*2^-3) near value (-1.1018541*2^0) failed at tensorflow/lite/micro/examples/hello_world/hello_world_test.cc:118
-0.959 (-1.9179993*2^-1) near value (-1.1018541*2^0) failed at tensorflow/lite/micro/examples/hello_world/hello_world_test.cc:125
0/1 tests passed
~~~SOME TESTS FAILED~~~

On debugging, I found that GetTensorData<int32_t>(bias) returns tensor data in LE format, where bias is an Optional Input Tensor being populated in Eval as const TfLiteTensor* bias = GetOptionalInputTensor(context, node, kBiasTensor);
This tensor data of bias is used in reference_integer_ops FullyConnected in calculation of acc.
I tried a solution of byte-swapping this data while populating acc which fixed the test case. The solution looked like this:
if (bias_data) {
#if FLATBUFFERS_LITTLEENDIAN
        acc += bias_data[out_c];
#else
        acc += __bswap_32(bias_data[out_c]);
#endif

in fully_connected.h
Since, I do not have a view of the reach and use of this optional tensor, can you please suggest if there is another way that you would like me to try or if I should PR this solution?
Describe the expected behavior
The tensor data on BE systems must be in correct format and the test case should pass.
Standalone code to reproduce the issue
To reproduce the issue, please run this test case:
bazel --host_jvm_args="-Xms1024m" --host_jvm_args="-Xmx2048m" test --host_javabase="@local_jdk//:jdk" --test_tag_filters=-gpu,-benchmark-test,-v1only,-no_oss,-oss_serial -k --test_timeout 300,450,1200,3600 --build_tests_only -c dbg --copt=-O -c opt --copt=-g --strip never --color=yes --curses=yes --test_output=errors --verbose_failures  -- //tensorflow/lite/micro/examples/hello_world:hello_world_test

Other info / logs

I found that a similar fix is also required for micro_speech_binary_mock_test and micro_speech_test test cases to pass on s390x. The changes are required in depthwise_conv.h. Here also, the bias data needs to be byte-swapped before populating acc.

Hi @advaitjain , just posting an update here..
In tensorflow release 2.4.1, this solution causes regression to //tensorflow/lite/micro/kernels:fully_connected_test and similarly, fix in  depthwise_conv.h causes //tensorflow/lite/micro/kernels:depthwise_conv_test test case to fail.
It seems that these tests require bias_data to be in Little Endian format and is handling data accordingly while for hello_world_test and micro_speech_tests, bias_data is being used in calculation assuming that it's in BE format and hence, it's messing up the calculation of acc.

Hi @advaitjain , just posting an update here..
In tensorflow release 2.4.1, this solution causes regression to //tensorflow/lite/micro/kernels:fully_connected_test and similarly, fix in  depthwise_conv.h causes //tensorflow/lite/micro/kernels:depthwise_conv_test test case to fail.
It seems that these tests require bias_data to be in Little Endian format and is handling data accordingly while for hello_world_test and micro_speech_tests, bias_data is being used in calculation assuming that it's in BE format and hence, it's messing up the calculation of acc.

Any updates from the community for this issue? Thanks!

Hi @advaitjain , hope all is well.
Wonder if you have any updates reg this issue? Thanks!

This issue could be closed since test case //tensorflow/lite/micro/examples/hello_world:hello_world_test has been moved out of tensorflow/tensorflow repository.

Hi @kun-lu20 @skribm9
I was checking if this issue still persists.
The hello_world_test is now evaluate_cc_test as given here.
I've tried running
bazel --host_jvm_args="-Xms1024m" --host_jvm_args="-Xmx2048m" test --host_javabase="@local_jdk//:jdk" --test_tag_filters=-gpu,-benchmark-test,-v1only,-no_oss,-oss_serial -k --test_timeout 300,450,1200,3600 --build_tests_only -c dbg --copt=-O -c opt --copt=-g --strip never --color=yes --curses=yes --test_output=errors --verbose_failures  -- //tensorflow/lite/micro/examples/hello_world:evaluate_cc_test and was able to build successfully without any error.
Please find the screenshot below.

Please feel free to close the issue if it is resolved.
Thanks.

Hi @pjpratik ,
Thanks for checking this!
Since this test case has been moved out of tensorflow/tensorflow repo, we are not tracking it on s390x any more. Could you please close this issue? Thanks again.

@kun-lu20 Thanks for the confirmation.


Matter-thermostat add support for mains powered thermostats

I only added profiles for the nostate profiles since currently all thermostats are joined using those profiles.

looks like we might have a duplicate profile. You can probably just git mv the existing one to match the naming scheme, although I'd double-check locally that you're allowed to "delete" a profile. At some point in the past it wasn't allowed. Might not be still.

Hello,
I was going through the matter-thermostat driver and came across this issue where few attributes are not being subscribed by the hub, hence ST App controls are disabled for cluster's corresponding capabilities.
Currently as observed, driver subscribes to attributes only when the corresponding capability is also listed in the profile applied during driver's matter device instance initialization (populate_subscribed_attributes_from_driver_defaults) in st/matter/device.lua
Considering the device being onboarded has both fan control and humidity clusters along with thermostat cluster on endpoint 1 (thermostat device type 0x301), the profile applied would be thermostat.yml, but since init(subscribe) occurs before do_configure(profile update), fanControl and humidity cluster's attributes are not being subscribed. Please correct me if I am missing something in my understanding.

@sathvik-gatti thanks for bringing finding this bug. I added a fix to subscribe to the device during the info_changed event. I did it here rather than do_configure because during do_configure, the profile has not been updated on the device record. The info_changed event will fire when the profile has updated and therefore we can re-subscribe at a point when the new capabilities can be considered.

looks like we might have a duplicate profile.

I missed removing the battery cap from this profile when doing my copy pastas

@sathvik-gatti thanks for bringing finding this bug. I added a fix to subscribe to the device during the info_changed event. I did it here rather than do_configure because during do_configure, the profile has not been updated on the device record. The info_changed event will fire when the profile has updated and therefore we can re-subscribe at a point when the new capabilities can be considered.

Thanks @cjswedes for considering this issue, but it seems like device:subscribe() fetches a subscribed attributes list from lua device's store (key=SUBSCRIBED_ATTRIBUTES_KEY) and subscribes to those attributes present in it. This list as last seen, is populated when the lua matter device is instantiated. I was thinking maybe we can use device:add_subscribed_attributes() to add updated attributes to the list if their cluster was found on any endpoint right before profile update. Once the profile updates then info_changed would subscribe. I tried suggesting here, please let me know what you think or if there is any other way to handle this as well.

Looks like my fixup doesn't actually fix the issue of subscribed attributes since MatterDevice:subscribe() does not reconsider the devices capabilities and drivers handlers each time it is called. Ill manually do this in the info_changed handler for now, but I will get this changed in the next Lua library release to always recalculate the subscribed attributes/events for a device prior to issuing the subscribe request to the hub.

@sathvik-gatti Thanks for the help on this one, I think it should be good now, but Ill wait for your 👍🏼 since I think you can run a manual test, which is always useful.

Thank you @cjswedes , for your response on this issue. I tested your fix from my side and it is working fine. The hub is subscribing to all the required attributes :) 👍


Alt+drag should duplicate even if element not currently selected

I think this is how it worked a while ago, and thus is a regression.
This is also how Figma does it (and desktop vector apps, I think).

i probably broke this in #874. will fix it this evening


Consolidate Juttle runtime: Pass Juttle runtime as a dependency

Pass Juttle runtime as an explicit dependency to code evaluated in the flowgraph and eval stages of the compiler. This means this code does not depend on the juttle variable being present in the evaluation context. The change will allow making other dependencies such as JuttleMoment explicit too in the future.
Part of work on #97.

@bkutil @demmer

Looks good to me. +1


[NETBEANS-1164] Move modules from php cluster into a subdirectory

https://issues.apache.org/jira/browse/NETBEANS-1164

Moving php modules into php subdirectory
Replace ../nbbuild with ../../nbbuild
Replace <project basedir="." default="netbeans" name=" with <project basedir="." default="build" name="php/

OK, any reason not to merge this now?

OK, everything green; merging.


logging_fail fail for x64 in VS2013, libglog_static

The following code will fail to compile in logging.cc under VS2013 x64  for libglog_static because _asm is no longer supported.
static void logging_fail() {
#if defined(_DEBUG) && defined(_MSC_VER)
  // When debugging on windows, avoid the obnoxious dialog and make
  // it possible to continue past a LOG(FATAL) in the debugger
  _asm int 3
#else
  abort();
#endif
}

If I change the code to this, the code will compile but when I use glog and fire a LOG(FAIL) in a debugger I will get the R6010 abort() dialog box.
#if defined(_DEBUG) && defined(_MSC_VER) && defined(_M_IX86)
What is the fix for R6010 that will also work for VS2013 x64?

Found on this website: http://blog.csdn.net/fksec/article/details/44341531
You may want to replace the inline assembly code:
_asm int 3
with:
__debugbreak();


Getting an error:  'list_issues': wrong number of arguments (given 3, expected 0..2) (ArgumentError)

Describe the bug
Running it on my private private repo, which does not have any issues logged, but does have a bunch of tags,  although the same error happens even after I created a dummy issue.
$  cat .github_changelog_generator
since-tag=v0.2.0
$ github_changelog_generator --project YYYY --user XXXXX -t ZZZZZ
/Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/octokit-4.20.0/lib/octokit/client/issues.rb:30:in 'list_issues': wrong number of arguments (given 3, expected 0..2) (ArgumentError)
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/github_changelog_generator-1.16.1/lib/github_changelog_generator/octo_fetcher.rb:415:in 'block in iterate_pages'
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/retriable-3.1.2/lib/retriable.rb:61:in 'block in retriable'
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/retriable-3.1.2/lib/retriable.rb:56:in 'times'
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/retriable-3.1.2/lib/retriable.rb:56:in 'retriable'
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/github_changelog_generator-1.16.1/lib/github_changelog_generator/octo_fetcher.rb:446:in check_github_response'
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/github_changelog_generator-1.16.1/lib/github_changelog_generator/octo_fetcher.rb:415:in 'iterate_pages'
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/github_changelog_generator-1.16.1/lib/github_changelog_generator/octo_fetcher.rb:164:in 'fetch_closed_issues_and_pr'
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/github_changelog_generator-1.16.1/lib/github_changelog_generator/generator/generator.rb:144:in 'fetch_issues_and_pr'
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/github_changelog_generator-1.16.1/lib/github_changelog_generator/generator/generator.rb:55:in 'block in compound_changelog'
	from /Users/kig/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/async-1.28.9/lib/async/task.rb:265:in 'block in make_fiber'

To Reproduce
Unfortunately, this is a private repo.
Ruby versions tried:

2.7.2
3.0.0

Gem version tried:

1.16.1

The method called is here:
https://github.com/github-changelog-generator/github-changelog-generator/blob/master/lib/github_changelog_generator/octo_fetcher.rb#L415

If you need a public repo to reproduce the issue: We ran into the same issue in stimulus_reflex.
Downgrading github_changelog_generator to v1.15.2 seems to resolve the issue for us.
Locally I can reproduce the ArgumentError with this using Ruby 3.0.0 and 1.16.1:
github_changelog_generator -u hopsoft -p stimulus_reflex --exclude-labels duplicate,question,invalid,wontfix,nodoc --token {token}


Add a logline to include connection ID when describing a request and response pair

The method Observer.describeRequestAndResponse is used to generate request/response information to log when the observer throws an exception. The generated request/response information will be logged together with the exception thrown by the observer.
Logging the connection ID along with the exception will help us understand how the value of connection ID plays a part in the exception and help us root cause the problem.

Please make sure you follow this format in the commit message:
[LI-HOTFIX] Ignore the flaky test MetricsTest.testGeneralBrokerTopicMetricsAreGreedilyRegistered

TICKET = KAFKA-9786
LI_DESCRIPTION =
The test is flaky since gradle can use the same jvm to run multiple tests concurrently
EXIT_CRITERIA = KAFKA-9786

Please also commit this change to the 2.4-li-dev-6 branch


fix: updated a snapshot and added SHEIN logo and website

Changes
Updated snapshot and added SHEIN logo and website

Testing
All tests have been passed.

Docs
Docs have been updated.

Thank you, and I'm glad you're enjoying Snowpack! Can you share more about how you're using it on the site / at the company?


[Feature Request] Server-side Waypoints Sharing

https://github.com/rfresh2/XaeroPlus/blob/c37503e0b312f95fa00c93df22ac36fce4acb122/README.md#modifications doesn't list anything relevant. There is desire for this, per https://www.reddit.com/r/feedthebeast/comments/s8q6l7/is_there_a_option_too_see_other_players_waypoints/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button.

There is no automatic waypoints sharing feature in XaeroPlus or the base mods.
There is a way to share waypoints in chat which other players can click on to add but that's it.

https://github.com/rfresh2/XaeroPlus/issues/141#issuecomment-2183523969

@rfresh2, indeed, hence the request, since this repository appears to exist to improve it. The absence of any ability so display Waypoints between players is a reason that I and my friends are being forced to search for alternatives.

Ok, wasn't clear if this was a feature request or a support question.
XaeroPlus is currently a client-side only mod but its something i've considered before.

https://github.com/rfresh2/XaeroPlus/issues/141#issuecomment-2183552158

I've also filed this at the original mod's issue tracker - https://legacy.curseforge.com/minecraft/mc-mods/xaeros-world-map/issues/859 - so that if it's accepted there, maintenance of this feature shan't be your burden unnecessarily.

yeah its probably for the best if xaero does it
there's actually some code already in the base mods referring to serverWaypoints but its not fully implemented.
its been there since at least late 2022 when i started tracking changes but i guess he just hasn't got around to finishing it


Generate dependency declarations

will be done via https://github.com/exasol/project-keeper-maven-plugin/issues/95


Integrate upstream changes

Ignoring Circle CI, I think it's broken.
I hope it's broken?
Removing it from the config and proceeding bravely on Travis's say-so.