npm install error

i have finding the following error whenever i am trying npm install
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please use gulp-clean-css
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated<EMAIL_ADDRESS>connect 2.x series is deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
npm ERR! code 1
npm ERR! Command failed: /usr/bin/git checkout ~0.2.0
npm ERR! error: pathspec '~0.2.0' did not match any file(s) known to git.
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/bonnie/.npm/_logs/2018-03-06T16_13_47_658Z-debug.log
node version is v4.7.0
npm version is 5.7.1

There is an issue with some of the latest npm versions. You should use yarn instead: http://portainer.readthedocs.io/en/stable/contribute.html
See second coment in #1399, which points to npm/npm#18434 and npm/npm#17621.

Why are you using npm ? You should be using yarn instead. Have a look at our contribution docs: http://portainer.readthedocs.io/en/stable/contribute.html#build-portainer-locally
Closing as this should solve the problem, feel free to re-open if needed.


update java8 support feature description on tools page

Thanks! This will be live in a few minutes.


Suggestion - Get Revit context when testing

Hi guys! It's-a me again 😄
Not a bug, just a suggestion/request that I'd like to run through you to see if it makes sense.
Would it make sense to expose the context where the test runner is operating (i.e. the Application in Revit terms)?
This is my case: I created an object called RevitModel, that in some aspects wraps up Revit's Document object, but has a few other properties/methods.
One of the methods creates a new Revit file with Application.NewProjectDocument(string templatePath), which is a method of the Application object.
So I can't really test my method that creates a RevitModel because I can't get the Application that is running the test runner.
So what I'm thinking is, can we expose publicly xru.Uiapp so that it can be used to create objects? Or has it been set to private because that's the way it's has to be for some reason (like I am doing something that I'm not supposed to do in unit testing)?

Hey Tas, yep that makes sense.
We've currently limited the functionalities to what our use cases require, but we're happy to update to suit others needs!
Feel free to submit a PR with the change.

Yeah ok glad I was making sense! And no worries, Expect a PR from me soon 👍

I've been testing this possibility of exposing the Application in the xru class, but I'm hitting a snag and I'm wondering if you can help?
I have simply set to public (instead of private) the Uiappproperty in thexru` class here
https://github.com/specklesystems/xUnitRevit/blob/569b0401fe72ffe2856ef4797b3d479fe64bd7c6/xUnitRevitUtils2021/xru.cs#L19
I am able to get the Uiapp in my test and get the Application from it, but then when try to I use it (for example to create a new file from a template) it gives this error:
System.InvalidOperationException: 'The calling thread cannot access this object because a different thread owns it.'
Do you have any idea why this is happening?

I've been testing this possibility of exposing the UIApplication in the xru class and I got it working but it looks a bit cumbersome as a solution.
I initially just exposed the Uiapp property marking it as public here
https://github.com/specklesystems/xUnitRevit/blob/e6194701cee3f9a3257ac948d0a025b60f9cfd29/xUnitRevitUtils2021/xru.cs#L19
I then was able to get the peoperty from my tests' code, but I wasn't able to use it. I was getting an exception saying it was owned by a different thread.
So I understood that I also needed to expose the UiContext property too. I did that and I'm now able to run my tests in Revit (which is wonderful in itself and I love you guys for that ❤ ), but now my test's code looks a bit weird and I'm wondering if there's a more elegant solution to what I'm doing.
Here is an extract of my tests' fixture (where I set up the Revit Dcoument for the tests) using the public Uiapp and UiContext objects:
            // Create test document
            RevitModel model = new RevitModel();

            xru.UiContext.Send(x =>
            {
                model.CreateFromTemplate(xru.Uiapp.Application);
            }, null);

            xru.UiContext.Send(x =>
            {
                model.Document.SaveAs(saveTo);
            }, null);

            // Set project info
            xru.RunInTransaction(() =>
            {
                model.SetProjectInfo();
            }, model.Document).Wait();

Is there a better way to manage the threading without exposing the UiContext and calling it in my test? Or is this the way it is actually supposed to be?

Well you were getting an error because some Revit methods have to be called from the same thread in use by Revit, but tests are being triggered on another thread. Hence the use of the SyncronizationContext, you could simplify your code by merging the two xru.UiContext.Send methods in one, but otherwise it looks good!
I'm away today, can look at your PR upon my return!

Also, note that xru already has a method for creating a new document from a template file xru.CreateNewDoc... You could add your other helper methods there!

Yeah I've seen the CreateNewDoc method in xru and that's what I used at the beginning to see if the tests where working, but I need to test our RevitModel class that wraps up a few base Revit functionalities and integrates them with some company-specific properties and rules.
Enjoy your time off 😉


[KYLIN-2650] Upgrade Apache Calcite Avatica to version 1.17.0

Can one of the admins verify this patch?


Issue with access to locally stored data

In general, processes serialize or deserialize data in one of three ways:

Access via a service when the data is stored remotely.
Access via a service even when the data is stored locally.
Access via the host when the data is stored locally.

At present, the data lifecycle construction sequence tries these options in that order. The idea is that even locally stored daat should be accessed via a service is not unusual. For example:

a data processor may be designed to access data via a service so it doesn't matter whether the data is stored locally or remotely
a host may be configured such that data can only be accessed via a service, which can implement a more complex access control policy or a more comprehensive data access logging policy that could be achieved by the host.

The problem is that this can lead to odd or even dysfunctional outcomes when there is a data service, but a collocated process accesses data via its host, i.e., option (3), above. The existence of the data service leads the construction rules to consider option (2) first, and if the collocated process uses other processes that via some circuitous route connect to the data service, the wrong conclusion is drawn. Worse still, it is possible that no path to the data service may be found, leading to the conclusion that there is a modelling error.
This should be placed under user control, i.e., made dependent on asserted relationships. Henceforth, the rule should be that:

Access is via a service when the data is stored remotely.
Access is via a service even when the data is stored locally, if and only if the data processor and data service have a 'uses' relationship.
Access is otherwise via the host when the data is stored locally.

If none of these can be inferred, based on the process-process connections and hosting relationships, there is a modelling error.

Construction patterns fixed, but this doesn't entirely cure the problem. It is still possible for the local process to have connections to processes that eventually lead to the data service. In that situation, data paths are still found to the data service.
To fix this, we need to cut data paths at the point where a process is accessing the data locally.

Addressed in branch 103.
This is definitely an improvement on what we had before. No pull request made to merge into branch 6a, because these changes are necessary to complete work in branch 65, so it makes more sense to merge those branches first.


Fix OOVPA Error String Format

Apparently, I had overlooked OOVPAErrorString function already has SymbolDatabaseList *data with given index for able get library flag, function name, and version too. I also removed BuildVersion parameter passdown as well as it is not necessary.
Functional example:
Before: (wrong)
ERROR  : OOVPATable  1 4039 [  27] D3DDevice_BeginPush, comparing against OOVPATable  2 4039 [ 412] D3DDevice_BeginPush2 : OOVPA's are expanded (left +2, right +2)
ERROR  : OOVPATable  1 4531 [  30] D3DDevice_BeginPush2, comparing against OOVPATable  2 4531 [ 409] D3DDevice_BeginPush : OOVPA's are expanded (left +2, right +2)

After: (correct)
ERROR  : OOVPATable  1 4531 [  27] D3DDevice_BeginPush, comparing against OOVPATable  2 4039 [ 412] D3DDevice_BeginPush2 : OOVPA's are expanded (left +2, right +2)
ERROR  : OOVPATable  1 4039 [  30] D3DDevice_BeginPush2, comparing against OOVPATable  2 4531 [ 409] D3DDevice_BeginPush : OOVPA's are expanded (left +2, right +2)

Low risk merge


Switch to eslint

Use eslint instead of tslint
Use strict mode
Fix errors and add lots of typings

Some other smaller things also:

Fix docker production node version to match development's
Moved nodemon to be dev dependency
Replace npm commands with yarn
Try to fix github security alert :]

Pull Request Test Coverage Report for Build 76

4 of 8 (50.0%)  changed or added relevant lines in 1 file are covered.
17 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-4.0%) to 25.967%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/App.ts
4
8
50.0%

Files with Coverage Reduction
New Missed Lines
%

src/Controller/Api/HelpController.ts
1
50.0%

src/Routes/Api.ts
3
40.0%

src/Services/Database.js
4
0.0%

src/App.ts
9
52.63%

Totals

Change from base Build 73:
-4.0%

Covered Lines:
32

Relevant Lines:
121

💛  - Coveralls


FNIRT output specification issues

@htwangtw - I was debugging failing tests and it looks like there are several field in the FNIRT output spec (e.g. field_file) that have in_file as the only requirements, but this is not right.
In nipype one can specify full name by providing a string or set it to True in order to use the default nipype template. @effigies suggested that we don't have to support both, we could just allow for some user defined template.
Let me know if you have thoughts about it. Don't remember if we discussed similar cases

I agree with @effigies that we should just pick one.
I am inclined to ask for user defined template, as that would be more consistent with the docstring of FSL FNIRT. Tried to play around with it today but no success with fixing it.

There is no output spec for FNIRT anymore as a result of #41.
Everything is now derived from in_file as template for the default name in the input spec. This was necessary to get the tests green again.


card

Is your feature request related to a problem? Please describe.

Describe the solution you'd like:

Describe alternatives you've considered:

Additional context:

Thanks for reaching out, unfortunately this issue does not contain enough information for us to investigate the problem.
I will close it for now, but feel free to come back with more information.


How should nested inputs be handled?

When parsing nested inputs typescript-validation-schema will warn about unhandled scalar name for the nested inputs.
This can be addressed by adding the correct name of the generated schema to the scalarSchemas config:
scalarSchemas:
  AddressInput: AddressInputSchema

I'm just wondering if I have this correct, or if there's a better way?
Many thanks :)

@earnubs Thank you for making this issue!
Some extracts from the README This setting allows you to configure how the validation schema is assigned to the scalar.
scalarSchemas
type: ScalarSchemas
Extends or overrides validation schema for the built-in scalars and custom GraphQL scalars.
yup schema
config:
  schema: yup
  scalarSchemas:
    Date: yup.date()
    Email: yup.string().email()

zod schema
config:
  schema: zod
  scalarSchemas:
    Date: z.date()
    Email: z.string().email()

I think your configuration is right. But I don't understand what does this mean?

the nested inputs

I would be grateful if you could provide us with your schema set as a scalar and the TypeScript code generated for it to better understand it.

Made up example:
BusinessInput {
  address: AddressInput!
  name: String!
  code: BusinessIdentifierCode!
}

input AddressInput {
  addressLine1: String
  addressLine2: String
  city: String
  country: CountryAlpha3Code!
  postalCode: PostalCode
}

When the plugin encounters BusinessIdentifierCode and CountryAlpha3Code those are custom scalars, so the docs are clear and the scalarSchemas config should be used, something like:
config:
  schema: yup
  scalarSchemas:
    BusinessIdentifierCode: yup.string()
    CountryAlpha3Code: yup.string().max(3)

However AddressInput is also a field of BusinessInput, but it is not a Scalar, it's a GraphQL Input type.
It falls through https://github.com/Code-Hex/graphql-codegen-typescript-validation-schema/blob/main/src/yup/index.ts#L263 because it's not a scalar type. You can still add it to scalarSchemas, but you have to know if the input is an enum or not as enum schemas are not callable.
I think it would be possible to make the plugin smart enough to know when it had generated a type for an input already an use it in this case, without the need for config at all, but I haven't worked through it all yet.


Close the connection with failed HTTP/2 upgrade request early

Motivation:
When we are sure that we cannot reuse the HTTP/1 connection that we
failed to upgrade to HTTP/2, we do not need to wait until the response
is fully received.
Modifications:

Disconnect early when it's not possible to reuse the HTTP/1 connection
that we failed to upgrade to HTTP/2.

Improve how we determine whether it's possible to reuse or not, by
checking connection, content-length and transfer-encoding.

Record the response headers of rejected upgrade requests

Result:

Potentially lower initial connection latency by giving up hopeless
HTTP/1 connection early
Maybe easier to figure out why upgrade was failed

Thanks for reviewing, folks!


[ISSUE #5876] fix resource leak in DefaultLitePullConsumerTest

fix #5876

Codecov Report

Merging #5877 (89d30a5) into develop (cbad53d) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #5877      +/-   ##
=============================================
- Coverage      42.45%   42.36%   -0.09%
+ Complexity      8283     8263      -20
=============================================
  Files           1066     1066
  Lines          73670    73670
  Branches        9629     9629
=============================================
- Hits           31276    31213      -63
- Misses         38445    38505      +60
- Partials        3949     3952       +3

Impacted Files
Coverage Δ

...tools/command/namesrv/WipeWritePermSubCommand.java
50.00% <0.00%> (-19.24%)
:arrow_down:

...n/java/org/apache/rocketmq/test/util/StatUtil.java
15.49% <0.00%> (-14.09%)
:arrow_down:

...e/rocketmq/store/ha/autoswitch/EpochFileCache.java
77.08% <0.00%> (-4.17%)
:arrow_down:

...lient/impl/consumer/DefaultMQPushConsumerImpl.java
32.09% <0.00%> (-3.09%)
:arrow_down:

...ketmq/client/impl/consumer/PullMessageService.java
49.23% <0.00%> (-3.08%)
:arrow_down:

...ava/org/apache/rocketmq/filter/util/BitsArray.java
58.11% <0.00%> (-1.71%)
:arrow_down:

...mq/client/impl/consumer/RebalanceLitePullImpl.java
69.86% <0.00%> (-1.37%)
:arrow_down:

...rg/apache/rocketmq/remoting/netty/NettyLogger.java
13.60% <0.00%> (-1.37%)
:arrow_down:

...ent/impl/consumer/DefaultLitePullConsumerImpl.java
68.75% <0.00%> (-1.25%)
:arrow_down:

.../apache/rocketmq/store/ha/DefaultHAConnection.java
65.86% <0.00%> (-1.21%)
:arrow_down:

... and 22 more

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


How to change the cell background color based on condition

I would want to change the cell  background color based on some condition . I have made it work by creating html tag inside cell , but I would want change the cell bgcolr without creating another tag

@Suprit-S-M Can you provide an example of what you have so far?
I think a custom transform should be able to do the trick. You need to perform the check there and pass style containing the color based on your logic. That will inject to the table cell.

Ok thanks for your time , its really helps me.

No probs. Keep me updated. 👍

yeah sure

Hello , How to make by default cell edit should show edit box , Currently once I click on cell edit box is getting displaying . I want to show it without clicking . Could you please help me.

@Suprit-S-M I think they key is in controlling the isEditing flag. See the demo. Basically you would have to set the state so that the function evaluates as true by default to achieve what you want.

We can not set the state during render , I am not getting it how to do , Could you please help me to get it done.Because isEditing will call every reneder(cell display).

@Suprit-S-M I'm going to need some code to tell any better. I don't mind getting you guys on some kind of support plan if you want.

Yeah thanks for your time , I made it work ,  Thank you

Ok, cool. Let's close this one then.


Unable to generate key pair

Hello,
I am using latest release and it was working for me 20 days ago. I tried today and it stopped working.
======================================
mshanker-mbp-13:.okta mshanker$ java -jar okta-aws-cli-1.0.2.jar
Username<EMAIL_ADDRESS>Password:
Multi-Factor authentication is required. Please select a factor to use.
Factors:
[ 1 ] : Okta Verify (Push)
[ 2 ] : Okta Verify (TOTP)
Selection: 1
Push Factor Authentication
Waiting for you to approve the Okta push notification on your device...
Waiting for you to approve the Okta push notification on your device...
Waiting for you to approve the Okta push notification on your device...
Waiting for you to approve the Okta push notification on your device...
Aug 08, 2018 11:21:16 AM org.apache.http.client.protocol.ResponseProcessCookies processCookies
WARNING: Invalid cookie header: "Set-Cookie: Okta_Verify_Autopush_1039367086=false;Version=1;Path=/;Max-Age=31536000;Secure;Expires=Thu, 08 Aug 2019 05:51:16 GMT;HttpOnly". Invalid 'expires' attribute: Thu, 08 Aug 2019 05:51:16 GMT
Waiting for you to approve the Okta push notification on your device...
201118c-aOM0MMMLyvzzMYQlLEn9QXJEmouwh-mbsg1SmdyVxx9XXRb
Exception in thread "main" java.lang.RuntimeException: You do not have access to AWS through Okta.
Please contact your administrator.
at com.okta.tools.saml.OktaSaml.getSamlResponseForAws(OktaSaml.java:53)
at com.okta.tools.saml.OktaSaml.getSamlResponse(OktaSaml.java:45)
at com.okta.tools.OktaAwsCliAssumeRole.run(OktaAwsCliAssumeRole.java:88)
at com.okta.tools.awscli.main(awscli.java:33)
mshanker-mbp-13:.okta mshanker$
mshanker-mbp-13:.okta mshanker$ java -version
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode)
mshanker-mbp-13:.okta mshanker$
mshanker-mbp-13:.okta mshanker$ uname -a
Darwin mshanker-mbp-13 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64
mshanker-mbp-13:.okta mshanker$
======================================
Although it says "You do not have access to AWS through Okta.", I am able to login through browser and AWS app shows in my Okta.
Thanks,
Malyaj Shanker

It looks like a problem with the support for Okta Push. I haven’t tried Okta Push myself.
Do you get the push notification in the Okta Verify app on your phone?

Yes and I did approve it.
In fact, I tried a few other open source tools to generate keys through okta and found that they have stopped working too. Push and TOTP both are not working.
===================
mshanker-mbp-13:.okta mshanker$ java -jar okta-aws-cli-1.0.2.jar
Username<EMAIL_ADDRESS>Password:
Multi-Factor authentication is required. Please select a factor to use.
Factors:
[ 1 ] : Okta Verify (Push)
[ 2 ] : Okta Verify (TOTP)
Selection: 2
OKTA Token Factor Authentication
Enter 'change factor' to use a different factor
Token:
205638
Exception in thread "main" java.lang.RuntimeException: You do not have access to AWS through Okta.
Please contact your administrator.
at com.okta.tools.saml.OktaSaml.getSamlResponseForAws(OktaSaml.java:53)
at com.okta.tools.saml.OktaSaml.getSamlResponse(OktaSaml.java:45)
at com.okta.tools.OktaAwsCliAssumeRole.run(OktaAwsCliAssumeRole.java:88)
at com.okta.tools.awscli.main(awscli.java:33)
mshanker-mbp-13:.okta mshanker$
===================
I wrote a script myself (based on https://aws.amazon.com/blogs/security/how-to-implement-a-general-solution-for-federated-apicli-access-using-saml-2-0/) and found that the authentication is successful (I am doing it through Okta API).
The problem is when the script tries to access Okta AWS URL after successful authentication (e.g. https://MYORG.okta.com/home/amazon_aws/1a2b3c4d5e6f7g8h9i/111) . It redirects to login page which doesn't recognise the browser and doesn't redirect further to https://signin.aws.amazon.com/saml to get the "SAMLResponse".
I think that some change on the Okta end caused this. May be it requires some cookie to be set or something else.

@shankerm-ti do you think you could adapt your script to Java and integrate it with this project and submit a PR?

@shankerm-ti I just opened #173 which should help differentiate between the different failure modes here.
I just tested Okta Verify using token (TOTP-style) with an org-level authentication sign-on policy requiring MFA and it worked.
If you have prompt for re-authentication turned on in an App Sign On Rule, that also currently isn't supported.
I'm not sure how to test Okta Push as I have it enabled and it doesn't appear to be working.

@AlainODea I am sorry, I won't be able to convert it to Java. I used the same python script given in the link and changed the part for authentication to use API. Rest was same.
I re-looked at my Okta configuration and found that my Okta Super Admin has enforced app level MFA on all apps. I disabled that for AWS and it started working.
Apologies for the false alarm.
Thanks,
Malyaj Shanker

No need to apologise, @shankerm-ti!
What you experienced is a bug with MFA errors that #172 fixes. It would have made this fail right away with a clear message.
I have some better error messaging coming in #173 that indicates the kind of policy that is unsupported.
I’m glad this is working again for you.


First draft, adding screenshot and a little reorganization

https://csc-guide-preview.rahtiapp.fi/origin/delete-VM/cloud/pouta/vm-lifecycle/


Note about frame rate for the website?

We should discuss...
thanks!

Augustine is going to draft a sentence that we can add to the website...


Script bundler randomly not include boostrap-multiselect.js

Dear @volkanceylan,
I found an issue while the script bundler is enabled: sometime "boostrap-multiselect.js" file is not included in the bundle (honestly I don't know if this issue happens only for this file).
Symptom:

Broken bundle: https://dl.dropboxusercontent.com/u/55649962/eService/broken_bundle.txt
Working bundle: https://dl.dropboxusercontent.com/u/55649962/eService/working_bundle.txt
As you can see in the "broken" file the boostrap-multiselect library is missing at all.
Here there is my ScriptBundles.json:
{
  "Libs": [
    "~/Scripts/pace.js",
    "~/Scripts/rsvp.js",
    "~/Scripts/jquery-{version}.js",
    "~/Scripts/jquery-ui-{version}.js",
    "~/Scripts/jquery-ui-i18n.js",
    "~/Scripts/jquery.validate.js",
    "~/Scripts/jquery.blockUI.js",
    "~/Scripts/jquery.cookie.js",
    "~/Scripts/jquery.json.js",
    "~/Scripts/jquery.autoNumeric.js",
    "~/Scripts/jquery.colorbox.js",
    "~/Scripts/jquery.dialogextendQ.js",
    "~/Scripts/jquery.event.drag.js",
    "~/Scripts/jquery.scrollintoview.js",
    "~/Scripts/jsrender.js",
    "~/Scripts/select2.js",
    "~/Scripts/sortable.js",
    "~/Scripts/toastr.js",
    "~/Scripts/SlickGrid/slick.core.js",
    "~/Scripts/SlickGrid/slick.grid.js",
    "~/Scripts/SlickGrid/slick.groupitemmetadataprovider.js",
    "~/Scripts/SlickGrid/Plugins/slick.autotooltips.js",
    "~/Scripts/SlickGrid/Plugins/slick.headerbuttons.js",
    "~/Scripts/SlickGrid/Plugins/slick.rowselectionmodel.js",
    "~/Scripts/SlickGrid/Plugins/slick.rowmovemanager.js",
    "~/Scripts/bootstrap.js",
    "~/Scripts/Saltarelle/mscorlib.js",
    "~/Scripts/Saltarelle/linq.js",
    "~/Scripts/Serenity/Serenity.CoreLib.js",
    "~/Scripts/Serenity/Serenity.Script.UI.js",
    "~/Scripts/jquery.cropzoom.js",
    "~/Scripts/jquery.fileupload.js",
    "~/Scripts/jquery.iframe-transport.js",
    "~/Scripts/jquery.slimscroll.js",
    "~/Scripts/mousetrap.js",
    "~/Scripts/fastclick/fastclick.js",
    "~/Scripts/bootstrap-multiselect.js",
    "~/Scripts/bootbox.js",
    "~/Scripts/jquery.signalR-2.2.1.js"
  ],
  "Site": [
    "~/Scripts/adminlte/app.js",
    "~/Scripts/Site/eService.Web.js"
  ]
}

If I restart IIS it's likely that the bundle is properly regenerated...I don't know why randomly it's not properly generated, in particular the boostrap-multiselect.js is not bundled.
Thank you very much for your support
Bye

Sorry @marcobisio but i can't help you with this one. Computers are supposed to be deterministic, and they perform same way when operating in same set of inputs.
Skipping a particular script randomly is not something script bundler can do on purpose. It's gotta be a configuration problem in your site. E.g. double sites under IIS mapped under each other etc.

I've opened your both script bundles in Winmerge, side by side, as i guessed, bootstrap-multiselect is not the only difference.
Serenity.Script.UI.js includes are also different on both sides. Also in place where multiselect should be located, there is your Site.Script.js file with TicketPreAnswerForm etc.
So, i think DynJS.axd is handled by two different sites.

Here Serenity.Script.UI.js difference:

Your script containing TicketSeverityForm on one side, while multiselect other:

Thanks for the quick answer @volkanceylan!
The broken file is taken from the test environment while the working one is taken from the dev environment...my apologies...I forgot to tell you!
I took the bundle from two different environment because it's a "rare" issue and I'm keeping "frozen" the broken environment in order to do some diagnostic...
For sure there are differences, but I cannot understand why with the same configuration (the only thing that is different is the connection string) the multiselect library isn't included in the bundle...
I noticed also that the bundler throw exceptions (only if in the browser the dev tools are open ) because some js.map files are missing (at DynamicScriptHandler.cs row 23), but I think that such exceptions aren't related to my problem...
Perhaps I could modify the Serenity sources in order to log which files are bundled...
Thanks as always for your support @volkanceylan
Bye

About five days with the bundler disabled and no more issues...
I plan to investigate further, but for now I close the issue to avoid unnecessary "noise" on github!
Thanks anyway @volkanceylan
Bye


fabric8:deploy specifies wrong version in deployment manifest

Description
A project is successfully deployed to local minikube when I execute fabric8:resource, fabric8:build and fabric8:deploy goals at once:
mvn fabric8:resource fabric8:build fabric8:deploy
If I run commands separately as follows:
mvn fabric8:resource
mvn fabric8:build
mvn fabric8:deploy

then pod fails to start with ImagePullBackOff due to a wrong version specified in the deployment manifest: bla-container:snapshot-180324-122854-0943.
The digit part differs from the one generated by the build goal.
Do I need to set some sort of a parameter for mvn fabric8:deploy for it to pick up the latest available build in target folder?
Info

f-m-p version : 3.5.38
Maven version (mvn -v) : 3.5.3

Kubernetes / OpenShift setup and version : k8s 1.9.0

Hey
Try this order,
mvn fabric8:build
mvn fabric8:resource
mvn fabric8:deploy

Thanks, @piyush1594, this seems to be working.
But why then the following fails (swapped build and resource in places) with the same error as in the original post?
mvn fabric8:build fabric8:resource fabric8:deploy

Hey @gintautassulskus
This looks to be some issue, needs to look into this.
Thanks

#1093 is the original issue related to this which is already in the priority list.

Duplicate of #1093

Closing as duplicate.


Build: Documentation styling

:tada: This PR is included in version 0.5.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Why, for encoding of parquet page, only read and write operations are supported?

Is it because I didn't understand it or because of other reasons?
https://github.com/jorgecarleitao/arrow2/blob/main/src/io/parquet/write/primitive.rs#L39

Could you clarify the question? I am not sure I am understanding. Atm this only supports writing PLAIN, and, in PLAIN with nullable values, only valid slots should be written in parquet.

Thanks reply, Viewed:
https://github.com/jorgecarleitao/parquet2/blob/f86ba6f65fede75dd7b9f7dd6b0fe3e271d2aa58/src/serialization/read/mod.rs#L50；
https://github.com/jorgecarleitao/arrow2/blob/176569c82f4f4d84ad61562a36b80ab964efa621/src/io/parquet/read/mod.rs#L146
parquet2: page_iter_to_array vs  arrow2:page_to_array
I don’t understand:
Who should be subject to actual use

ahh, got it.

Who should be subject to actual use

it depends on what you are looking for: parquet2 makes no assumption about which in-memory format the consumer wants to use. It offers a minimal deserializer for a simple in-memory format that is mostly used to run integration tests against other producers and consumers.
This format does not have the complexities of arrow, and it is thus easier to understand for normal rust users (e.g. it uses Vec<Option<bool>>, not two bitmaps for validity and values of a boolean array).
Arrow2 on the other hand offers a deserializer specifically for arrow's in-memory format.
So, if you wish to use parquet without arrow, use parquet's version; else, use arrow's version. :)
For arrow, there is a guide on how to read and write via parquet:

https://jorgecarleitao.github.io/arrow2/io/parquet_read.html
https://jorgecarleitao.github.io/arrow2/io/parquet_write.html

and also examples in examples/.

thanks


refactor(ledger-connector-corda): add startMonitor features

Is your feature request related to a problem? Please describe.
On the current codes, some ledger-connectors (besu, quorum, corda, ...) does not have common API for monitoring block data on connected ledgers.
Corda has no block structure, but if some numbers of transactions are assumed as blocks, this feature can be developed.
This feature was already developed in cmd-socket-server and related ledger-connectors, but in case of merging those codes, we need to enhance the range.
Describe the solution you'd like
Add startMonitor feature to the above ledger-connector
EPIC
#1611

Applies to Corda v4.8

@petermetz I have some questions regarding corda connector and possible monitoring implementation, could you answer them please?

Does BLP (apiClient) ever need to call kotlin server directly? There're tests for that, but my assumption is that on production kotlin server could be strictly separated from the rest of the network.
Why there's a single API for both kotlin and typescript services? They'll either diverge along the way, or one of the services will be obsolete, or am I missing something?
Can we add watchBlocks endpoint to typescript component only, and different monitoring implementation endpoints on kotlin server (startMonitor, stopMonitor, getBlocks)?

Does BLP (apiClient) ever need to call kotlin server directly?

If the application is designed that way then yes. It is possible to design the application in such a way that the answer is no, but that limits certain options of course.

There're tests for that, but my assumption is that on production kotlin server could be strictly separated from the rest of the network.

You could deploy it on a separate network if you wanted to, yes.

Why there's a single API for both kotlin and typescript services? They'll either diverge along the way, or one of the services will be obsolete, or am I missing something?

The Typescript code is being redone to be the code for Corda v5. You just cannot see this on main yet but there's been a PR open for quite some time that we need to finalize and then merge (and then if you read the code on main it will make much more sense)

Can we add watchBlocks endpoint to typescript component only, and different monitoring implementation endpoints on kotlin server (startMonitor, stopMonitor, getBlocks)?

If you'd like to, sure thing. Just keep in mind that Kotlin server is for Corda v4 and the Typescript code of the connector is for Corda v5 (in the near future as soon as we can finalize the PR for it)

@petermetz The PR you have in mind is https://github.com/hyperledger/cactus/pull/1860?


Sketch palettes save not working

Just installed the latest version of the plugin, but saving the palette does nothing. Also, there is no flyout menu for global colors and document colors, just save palette which does nothing as mentioned.
Sketch 52.6, MacOS Mojave.
Behavior is exactly the same as in this previous issue with loading palettes.
https://github.com/andrewfiorillo/sketch-palettes/issues/52

Same issue, same Sketch version, High Sierra.

The latest version of the plugin does not work with older versions of Sketch. But, older versions of the plugin should work. You grab older versions of the plugin here:
https://github.com/andrewfiorillo/sketch-palettes/releases
However older versions of the plugin will of course not support saving names of presets, since that functionality didn't exist in older versions of Sketch.

I'm going to go ahead and close this issue. But let me know if the older version of the plugin doesn't work for you.


Alertmessage : Alert pop up message from antd added #360 done

Alertmessage : Alert pop up message from antd added #360 done.
https://github.com/user-attachments/assets/c905016c-ee8d-47b9-b1da-ed006637f669

Summary by CodeRabbit
Release Notes

New Features

Enhanced user feedback during login and signup processes with animated success and error messages.
Integrated Ant Design's message component for improved notification handling.

Bug Fixes

Corrected a typo in the error handling middleware import.

Chores

Updated contributors' section in the README with new contributor information.
Bumped the version of the Ant Design dependency.

Style

Added CSS styles for success and error message animations in the Login component.

@RamakrushnaBiswal Sir now you can check plz.


Add libgit2 to custom-words.txt

Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

@weshaggard Would you please take a look at this PR? Thanks!

@weshaggard Kindly ping on this RP. Thanks.

Sorry @leonard520 I was on holiday the last couple weeks. Can you help point me at where we need to use libgit2 at?

Sorry @leonard520 I was on holiday the last couple weeks. Can you help point me at where we need to use libgit2 at?

Here it is https://github.com/Azure/azure-rest-api-specs/blob/7a929a631841e4401b7df995ce03d73af3e177f6/specification/appplatform/resource-manager/Microsoft.AppPlatform/preview/2023-05-01-preview/appplatform.json#L9817


Update proto library reference and make curl forward/backward compatible

I'm working on fixing https://github.com/bazelbuild/bazel/issues/1681, which
will change the way Bazel organizes the execution root.  This has two
implications for tensorflow:

The protobuf library needs to be updated to a version that works with
old/new versions of Bazel (older versions won't be able to find
external protos).
The curl library needs to use ../curl as an include prefix in new
versions of Bazel and external/curl in old versions.

This patch should be forward/backward compatible.

Can one of the admins verify this patch?

@tensorflow-jenkins test this please

@jart is this good to go?

My name is Justine Tunney and I approve this pull request.

@tensorflow-jenkins test this please

I'm having trouble getting these tests to pass, even without my changes.  Is there anything in particular I need to set up to get, say, Linux CPU Tests working?  I've got a vanilla TF setup without my changes and I'm getting (for example, with bazel test //tensorflow/contrib/factorization/examples:mnist):
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
-----------------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/kchodorow/.cache/bazel/_bazel_kchodorow/d39e1471d317a89f747169f52aae8653/execroot/clean_tensorflow/bazel-out/local-opt/bin/tensorflow/contrib/factorization/examples/mnist.runfiles/org_tensorflow/tensorflow/contrib/factorization/examples/mnist.py", line 36, in <module>
    import tensorflow as tf
  File "/home/kchodorow/.cache/bazel/_bazel_kchodorow/d39e1471d317a89f747169f52aae8653/execroot/clean_tensorflow/bazel-out/local-opt/bin/tensorflow/contrib/factorization/examples/mnist.runfiles/org_tensorflow/tensorflow/__init__.py", line 24, in <module>
    from tensorflow.python import *
  File "/home/kchodorow/.cache/bazel/_bazel_kchodorow/d39e1471d317a89f747169f52aae8653/execroot/clean_tensorflow/bazel-out/local-opt/bin/tensorflow/contrib/factorization/examples/mnist.runfiles/org_tensorflow/tensorflow/python/__init__.py", line 124, in <module>
    from tensorflow.python.platform import test
  File "/home/kchodorow/.cache/bazel/_bazel_kchodorow/d39e1471d317a89f747169f52aae8653/execroot/clean_tensorflow/bazel-out/local-opt/bin/tensorflow/contrib/factorization/examples/mnist.runfiles/org_tensorflow/tensorflow/python/platform/test.py", line 83, in <module>
    import mock                # pylint: disable=g-import-not-at-top,unused-import
ImportError: No module named mock

@kchodorow: I notice that this import is conditional on the version:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/platform/test.py#L82
Could this check be wrong?

Ah, I didn't have mock installed!  sudo pip install mock made it pass.  Unfortunately, now it passes for me locally both with and without my change (gah!).  Is there a way to see the Bazel tests logs Jenkins generates (so I can see what, specifically, made these things fail)?

@kchodorow Click on "Console Output" link for the tests here:
https://ci.tensorflow.org/job/tensorflow-pull-requests-multijob/3566/
For the full log, click on the "Full Log" line at the top of the individual console output pages. They are very verbose, but searching for "Failure" usually does the trick.

Mr. Jenkins test this please

Okay, rebased my change on top of @jhseu's fix, so now it only updates the curl library.  Could you try triggering the Jenkins build again (hopefully for the last time)?

Jenkins, test this please

Horay!!!!

Friendly ping: could someone merge this in when you get a chance?


[Bazel] Fix all of the ign_common tests under bazel

Signed-off-by: Michael Carroll<EMAIL_ADDRESS>

All tests passing for me on docker container


Support for multiple resolutions

Hi, can we have something similar to playbackSpeed but for multiple resolution support like 480p, 720p, ...

Hi, can we have something similar to playbackSpeed but for multiple resolution support like 480p, 720p, ...

Sure :) very good idea. We'll add this to our ToDo List 👍 Thanks for your suggestion

@HosseinYousefi Please follow this branch: https://github.com/brianegan/chewie/tree/feat/resolutions
Work in Progress 👍

Should I use this branch this way in pubspec.yaml file?
  chewie:     git:       url: https://github.com/brianegan/chewie/tree/feat/resolutions
I get this error when I run this command:


Add internal call to prettyOncoplot to convert NA metadata values to literal "NA" string

I think because when we don't supply the custom colors it is internally handled but when the user provides it then there is trust no modifications are necessary. We can probably add internal call to convert NAs to literal string anyways
Slack Message

In another use case, the issue with factor was also discovered. So when the metadata column is factor, ComplexHeatmap tries to map to numeric value of factor level, causing similar issue.
We should add another internal call to convert metadata columns to characters if/when they are factors.
So the fix should contain two steps: 1. convert from factor to string then 2. replace NA values with “NA”

I think there is a related issue here that should be resolved. Have those standard columns in the metadata (e.g. pathology) always been set as factors or is this a recent change?

I think I got the idea of what is going on

In the recent update that I made to get rid of colors in the annotation colors that are displayed when no values for them are present in the metadata (PR #36, issue #35) I did not account for the metadata columns that had been passed to the prettyOncoplot as factors. This resulted in a bug that during subsetting of the colors list, the NA values were not properly handled, which generated this issue.
There was already a call that was converting factors to the characters, but it was done during subsetting for the remaining colors, and to fix the reported issue I have moved this call to occur prior to the color subsetting. Now the example works properly and can handle the sex column that is passed as factor. Here is the sample plot:

This is fixed in PR #44


Random "Error compiling Less stylesheet" errors when switching syntax themes

Just noticed this on Atom 1.0.9-020c11d on OSX 10.10.5 after I tried to switch the syntax theme from One Dark to Base16 Tomorrow Dark:

Notice how two errors are thrown first for the Base16 Tomorrow Dark, and then for the One Dark UI (which was already set as the UI theme).
I haven't touched any of those files. After I restarted Atom, Base16 Tomorrow Dark was successfully loaded at startup and I could switch themes just fine (no errors thrown).
I remember this happened once a few weeks/months ago as well, but I couldn't reproduce it back then either. I noticed one other similar issue (https://github.com/atom/atom/issues/6797), but that's related to styles.less.
cc @kevinsawicki in case you have any :thought_balloon: about this

Is this consistently happening or just the one time?

It's not happening consistently -- happened that one time, and I remember it happening once a few weeks ago as well. Tried to reproduce it a dozen times now and couldn't, with the same Atom setup as when it did happen.


Able to get system info, but unable to get arp table

Hi,
I'm using python 3.9.2, pano-os-python 1.6.0, pan-python 0.16.0
device version is 'sw-version': '8.1.18'
I'm able to get system info as per the SDK examples, e.g.:
from panos.firewall import Firewall
fw = Firewall ('device_ip', api_username='username', api_password = 'password')
resp = fw.op('show system info')

This works as expected, and I'm able to get the output of the command.
however, if I replace "show system info" with "show arp all", I'm getting this error:
Traceback (most recent call last):
File "c:\Users\roberto\pythonpalo\env\lib\site-packages\panos\base.py", line 3661, in method
super_method(self, *args, **kwargs)
File "c:\Users\roberto\pythonpalo\env\lib\site-packages\pan\xapi.py", line 951, in op
self.__type_op(cmd, vsys, extra_qs)
File "c:\Users\roberto\pythonpalo\env\lib\site-packages\pan\xapi.py", line 974, in __type_op
raise PanXapiError(self.status_detail)
pan.xapi.PanXapiError:  show -> arp -> all has unexpected text.
show -> arp  is unexpected
show  is unexpected
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\roberto\pythonpalo\pythonpalo\testpalo.py", line 19, in
res=fw.op('show arp all')
File "c:\Users\roberto\pythonpalo\env\lib\site-packages\panos\firewall.py", line 219, in op
return super(Firewall, self).op(
File "c:\Users\roberto\pythonpalo\env\lib\site-packages\panos\base.py", line 3822, in op
element = self.xapi.op(
File "c:\Users\roberto\pythonpalo\env\lib\site-packages\panos\base.py", line 3682, in method
raise the_exception
panos.errors.PanDeviceXapiError:  show -> arp -> all has unexpected text.
show -> arp  is unexpected
show  is unexpected
Using an ssh connection, I'm able to get results for both commands.
Any help would be greatly appreciated.

If you SSH to PAN-OS and run the following:
debug cli on
show arp all

You see that PAN-OS is actually formatting the call like this:
<request cmd="op" cookie="2801768344648204" uid="1000"><operations><show><arp><entry name='all'/></arp></show></operations></request>

Removing the cruft from that, what you'd need to send is this:
<show><arp><entry name='all'/></arp></show>

pan-os-python does do some auto formatting with op commands, but formatting things as an entry is not a format that can be automatically converted to.  So you'll have to do this yourself:
cmd = "<show><arp><entry name='all'/></arp></show>"
ans = fw.op(txt, cmd_xml=False)


QUESTION:  with modules now in the routes directory, where do I put modules that are shared?

Where do I put redux reducers that are shared across routes?

#832

Thanks @kolpav . Closing.


Cannot console into VM

Cannot console into my VM
kubectl describe pod virt-launcher-flex-vm-v8mwg
Name:               virt-launcher-flex-vm-v8mwg
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               k8s-master/<IP_ADDRESS>
Start Time:         Fri, 17 May 2019 13:48:28 -0400
Labels:             kubevirt.io=virt-launcher
                    kubevirt.io/created-by=fa5f48fe-78cb-11e9-b79a-0026b92c94fc
                    kubevirt.io/size=small
                    kubevirt.io/vm=flex-vm
Annotations:        kubevirt.io/domain: flex-vm
Status:             Running
IP:                 <IP_ADDRESS>
Controlled By:      VirtualMachineInstance/flex-vm
Containers:
  compute:
    Container ID:  docker://278494289f231ab120abaa453be0fca2fadfdc1e1600928a308896ed658ca0e3
    Image:         docker.io/kubevirt/virt-launcher:v0.14.0
    Image ID:      docker-pullable://kubevirt/virt-launcher@sha256:4a30833b31d0e21236722512fba35ef064a8d779dc9762948fef57610c933953
    Port:          <none>
    Host Port:     <none>
    Command:
      /usr/bin/virt-launcher
      --qemu-timeout
      5m
      --name
      flex-vm
      --uid
      fa5f48fe-78cb-11e9-b79a-0026b92c94fc
      --namespace
      default
      --kubevirt-share-dir
      /var/run/kubevirt
      --ephemeral-disk-dir
      /var/run/kubevirt-ephemeral-disks
      --readiness-file
      /var/run/kubevirt-infra/healthy
      --grace-period-seconds
      15
      --hook-sidecars
      0
      --less-pvc-space-toleration
      10
    State:          Running
      Started:      Fri, 17 May 2019 13:48:30 -0400
    Ready:          True
    Restart Count:  0
    Limits:
      devices.kubevirt.io/kvm:        1
      devices.kubevirt.io/tun:        1
      devices.kubevirt.io/vhost-net:  1
    Requests:
      devices.kubevirt.io/kvm:        1
      devices.kubevirt.io/tun:        1
      devices.kubevirt.io/vhost-net:  1
      memory:<PHONE_NUMBER>
    Readiness:                        exec [cat /var/run/kubevirt-infra/healthy] delay=2s timeout=5s period=2s #success=1 #failure=5
    Environment:                      <none>
    Mounts:
      /var/run/kubevirt from virt-share-dir (rw)
      /var/run/kubevirt-ephemeral-disks from ephemeral-disks (rw)
      /var/run/kubevirt-infra from infra-ready-mount (rw)
      /var/run/kubevirt-private/vmi-disks/mypvcdisk from mypvcdisk (rw)
      /var/run/libvirt from libvirt-runtime (rw)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  mypvcdisk:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  flex-vnf-volume-claim
    ReadOnly:   false
  infra-ready-mount:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  virt-share-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/kubevirt
    HostPathType:
  libvirt-runtime:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  ephemeral-disks:
    Type:        EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:   <unset>
QoS Class:       Burstable
Node-Selectors:  kubevirt.io/schedulable=true
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

kubectl get vm
NAME            AGE     RUNNING   VOLUME
testvm          6d16h   true
flex-vm   3d18h   true

kubectl get vm
NAME            AGE     RUNNING   VOLUME
testvm          6d16h   true
versa-flex-vm   3d18h   true

[dell@k8s-master ~]$ kubectl describe vm flex-vm
Name:         flex-vm
Namespace:    default
Labels:       kubevirt.io/vm=flex-vm
Annotations:  kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"kubevirt.io/v1alpha3","kind":"VirtualMachine","metadata":{"annotations":{},"creationTimestamp":null,"labels":{"kubevirt.io/...
API Version:  kubevirt.io/v1alpha3
Kind:         VirtualMachine
Metadata:
  Creation Timestamp:  2019-05-17T17:43:55Z
  Generation:          4
  Resource Version:    1223107
  Self Link:           /apis/kubevirt.io/v1alpha3/namespaces/default/virtualmachines/flex-vm
  UID:                 57dbf477-78cb-11e9-b79a-0026b92c94fc
Spec:
  Running:  true
  Template:
    Metadata:
      Creation Timestamp:  <nil>
      Labels:
        Kubevirt . Io / Size:  small
        Kubevirt . Io / Vm:    flex-vm
    Spec:
      Domain:
        Devices:
          Disks:
            Disk:
            Name:  mypvcdisk
          Interfaces:
            Bridge:
            Name:  default
        Machine:
          Type:
        Resources:
          Requests:
            Memory:  4G
      Networks:
        Name:  default
        Pod:
      Termination Grace Period Seconds:  0
      Volumes:
        Name:  mypvcdisk
        Persistent Volume Claim:
          Claim Name:  flex-vnf-volume-claim
Status:
  Created:  true
  Ready:    true
Events:     <none>

 ./virtctl vnc flex-vm
Can't access VMI versa-flex-vm: Can't connect to websocket (500): error dialing backend: dial tcp <IP_ADDRESS>:443: connect: no route to host

 ./virtctl console flex-vm
Successfully connected to versa-flex-vm console. The escape sequence is ^]

Just hangs at this prompt, any help is much appreciated.

I also encountered this problem，any help is much appreciated.

Sorry. Wrong button

@yinjingjiu the screenshot looks correct. Just got return to get the guest to refresh the prompt so that you can see it
@cclark what output did you get with virtctl console?

Im seeing the same console output as @yinjingjiu is seeing, the console connects but no other output is seen.
VMI appears to be fine:
kubectl describe vmi flex-vm
Name:         flex-vm
Namespace:    default
Labels:       kubevirt.io/nodeName=k8s-master
kubevirt.io/size=small
kubevirt.io/vm=flex-vm
Annotations:
API Version:  kubevirt.io/v1alpha3
Kind:         VirtualMachineInstance
Metadata:
Creation Timestamp:  2019-05-17T17:48:28Z
Finalizers:
foregroundDeleteVirtualMachine
Generate Name:  flex-vm
Generation:     7
Owner References:
API Version:           kubevirt.io/v1alpha3
Block Owner Deletion:  true
Controller:            true
Kind:                  VirtualMachine
Name:                  flex-vm
UID:                   57dbf477-78cb-11e9-b79a-0026b92c94fc
Resource Version:        1223105
Self Link:               /apis/kubevirt.io/v1alpha3/namespaces/default/virtualmachineinstances/flex-vm
UID:                     fa5f48fe-78cb-11e9-b79a-0026b92c94fc
Spec:
Domain:
Devices:
Disks:
Disk:
Bus:  sata
Name:   mypvcdisk
Interfaces:
Bridge:
Name:  default
Features:
Acpi:
Enabled:  true
Firmware:
Uuid:  3d1a0bb2-80f2-5e73-bd9c-cf414e9c6ae2
Machine:
Type:  q35
Resources:
Requests:
Memory:  4G
Networks:
Name:  default
Pod:
Termination Grace Period Seconds:  0
Volumes:
Name:  mypvcdisk
Persistent Volume Claim:
Claim Name:  flex-vnf-volume-claim
Status:
Conditions:
Last Probe Time:
Last Transition Time:
Status:                True
Type:                  LiveMigratable
Last Probe Time:
Last Transition Time:  2019-05-17T17:48:42Z
Status:                True
Type:                  Ready
Interfaces:
Ip Address:      <IP_ADDRESS>
Mac:             82:4c:65:42:a0:af
Name:            default
Migration Method:  LiveMigration
Node Name:         k8s-master
Phase:             Running
Events:

@cclark1974 what happens if you are connected to the console, and then hit  a c ouple of times?

@cclark1974 Can you try to connect via VNC, in most cases the console hangs when the VMI fails to boot correctly.

When I connect to the console and hit enter there is nothing back from the console, it appears to hang.
VNC is unsuccessful also
[dell@k8s-master ~]$ ./virtctl vnc flex-vm
Can't access VMI flex-vm: Can't connect to websocket (500): error dialing backend: dial tcp <IP_ADDRESS>:443: connect: no route to host

@cclark1974 Hm looks like some problem with the API server, can you show the output of
kubectl get pods --all-namespaces

kubectl get pods --all-namespaces
NAMESPACE     NAME                                 READY   STATUS    RESTARTS   AGE
cdi           cdi-apiserver-b9d98b7f-ztgqm         1/1     Running   0          7d19h
cdi           cdi-deployment-c87698db8-4wlw8       1/1     Running   0          7d19h
cdi           cdi-operator-79f8786f9-l9mnn         1/1     Running   0          7d19h
cdi           cdi-uploadproxy-7859c7bffc-lt468     1/1     Running   0          7d19h
default       cdi-upload-flex-vnf-volume-claim     1/1     Running   0          6d19h
default       virt-launcher-testvm-drgs9           2/2     Running   0          7d19h
default       virt-launcher-flex-vm-v8mwg    1/1     Running   0          6d19h
kube-system   coredns-fb8b8dccf-jztz6              1/1     Running   6          13d
kube-system   coredns-fb8b8dccf-v8jdr              1/1     Running   6          13d
kube-system   etcd-k8s-master                      1/1     Running   6          13d
kube-system   kube-apiserver-k8s-master            1/1     Running   6          13d
kube-system   kube-controller-manager-k8s-master   1/1     Running   6          13d
kube-system   kube-flannel-ds-amd64-6qxlj          1/1     Running   5          10d
kube-system   kube-flannel-ds-amd64-vpwzt          1/1     Running   4          10d
kube-system   kube-flannel-ds-dwvhn                1/1     Running   5          10d
kube-system   kube-flannel-ds-sw2td                1/1     Running   8          10d
kube-system   kube-multus-ds-amd64-c6gr7           1/1     Running   3          10d
kube-system   kube-multus-ds-amd64-z85g7           1/1     Running   5          10d
kube-system   kube-proxy-99rnk                     1/1     Running   6          13d
kube-system   kube-proxy-dhms6                     1/1     Running   3          10d
kube-system   kube-scheduler-k8s-master            1/1     Running   6          13d
kubevirt      virt-api-65cfcc9cc9-7v559            1/1     Running   3          9d
kubevirt      virt-api-65cfcc9cc9-pp9kv            1/1     Running   6          9d
kubevirt      virt-controller-8c7b94b6-m7fbj       1/1     Running   5          9d
kubevirt      virt-controller-8c7b94b6-v68zz       1/1     Running   15         9d
kubevirt      virt-handler-9k5wz                   1/1     Running   3          9d
kubevirt      virt-handler-sdx7r                   1/1     Running   5          9d

@cclark1974 Just to be sure that you use the right kubeconfig can you try to run virtctl command with
./virtctl --kubeconfig <cluster_kubeconfig> vnc flex-vm

@cclark1974 , I had the same issue.
If your VM is not starting, there will be a hint in the vm-launcher pod logs if its brcause of a VM launch error.
My particular problem occured because I had Kubernetes running behind a proxy for accessing the internet. This confused virtctl as it tries to connect to the kube API service.
After I removed the proxy setting from the kubelet manifest and restarted the service, I was able to access the console.

./virtctl --kubeconfig ~/.kube/config  vnc flex-vm
Can't access VMI flex-vm: Can't connect to websocket (500): error dialing backend: dial tcp <IP_ADDRESS>:443: connect: no route to host

@cclark1974 this is your master ip address or a service?
can you please run kubectl get svc --all-namespaces

@nilanjan-samajdar but commands like kubectl port-forward were working for you? I wonder what we need to change to make it work for virtctl too.

kubectl get svc --all-namespaces
NAMESPACE     NAME                          TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE
cdi           cdi-api                       ClusterIP   <IP_ADDRESS>            443/TCP                  11d
cdi           cdi-uploadproxy               ClusterIP   <IP_ADDRESS>           443/TCP                  11d
default       kubernetes                    ClusterIP   <IP_ADDRESS>                443/TCP                  18d
kube-system   kube-dns                      ClusterIP   <IP_ADDRESS>               53/UDP,53/TCP,9153/TCP   18d
kubevirt      kubevirt-prometheus-metrics   ClusterIP   <IP_ADDRESS>           443/TCP                  13d
kubevirt      virt-api                      ClusterIP   <IP_ADDRESS>             443/TCP                  13d

Yes kubectl port-forward was/is working

@rmohr
kubectl port-forward used to work.

@cclark1974 looks like the kube-api server is not available to connect to the virt-api service.
can you please try from your master host to run curl https://<IP_ADDRESS>

curl https://<IP_ADDRESS>
curl: (7) Failed connect to <IP_ADDRESS>:443; No route to host
How do I repair this?

@cclark1974 looks like an issue in your network plugin you should have connectivity can you try to take a look on your network plugin?
what plugin are you using?

Im using multus with flannel
kube-system   kube-apiserver-k8s-master            1/1     Running   6          18d
kube-system   kube-controller-manager-k8s-master   1/1     Running   6          18d
kube-system   kube-flannel-ds-amd64-6qxlj          1/1     Running   5          15d
kube-system   kube-flannel-ds-amd64-vpwzt          1/1     Running   4          15d
kube-system   kube-flannel-ds-dwvhn                1/1     Running   5          15d
kube-system   kube-flannel-ds-sw2td                1/1     Running   8          15d
kube-system   kube-multus-ds-amd64-c6gr7           1/1     Running   3          15d
kube-system   kube-multus-ds-amd64-z85g7           1/1     Running   5          15d

I found the networking issue... I am able to curl now
curl -v https://<IP_ADDRESS>

About to connect() to <IP_ADDRESS> port 443 (#0)
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 443 (#0)
Initializing NSS with certpath: sql:/etc/pki/nssdb
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
Server certificate:
subject: CN=virt-api.kubevirt.pod.cluster.local
start date: May 14 17:43:27 2019 GMT
expire date: May 13 17:43:27 2020 GMT
common name: virt-api.kubevirt.pod.cluster.local
issuer: CN=kubevirt.io
NSS error -8179 (SEC_ERROR_UNKNOWN_ISSUER)
Peer's Certificate issuer is not recognized.
Closing connection 0
curl: (60) Peer's Certificate issuer is not recognized.
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.

Im seeing this when I attempt the console connection:
./virtctl --kubeconfig ~/.kube/config vnc flex-vm
Error encountered: exec: "remote-viewer": executable file not found in $PATH
{"component":"virtctl","level":"info","msg":"connection timeout: 1m0s","pos":"vnc.go:137","timestamp":"2019-05-29T11:08:35.307797Z"}

Hi @cclark1974 thanks for the comment.
what is the operation system of the client you try to run the virtctl command from?

Attempting to run it from the master node it is running Centos

for VM we need to use some host that support GUI it will open a remove-viewer window

tigervnc is installed on the master, shouldnt that work?

I think so can you try to install the remote-viewer in the host?

./virtctl --kubeconfig ~/.kube/config vnc flex-vm
{"component":"virtctl","level":"info","msg":"connection timeout: 1m0s","pos":"vnc.go:137","timestamp":"2019-05-31T09:24:58.192788Z"}
{"component":"virtctl","level":"info","msg":"remote-viewer connected in 252.312527ms","pos":"vnc.go:148","timestamp":"2019-05-31T09:24:58.445101Z"}
I dont see anything else after, it just returns to the command prompt

Hi @cclark1974, just to be sure: are you connected to a graphical session on the master node?
If so, can you rerun the command with the --v 4 flag for more detailed logs, please?

Do you mean run:
./virtctl --kubeconfig ~/.kube/config vnc flex-vm . --v 4 ?
I tried running this and got an error with unrecognized option.

yes, almost, except you have a . in the line which shouldn't be there
you can also add the flag directly after ./virtctl, but that shouldn't make a difference iirc

Ok I ran the cmd from the Master desktop and got the following results:
[dell@k8s-master ~]$ ./virtctl --v 4 --kubeconfig ~/.kube/config vnc flex-vm
{"component":"virtctl","level":"info","msg":"Executing commandline: 'remote-viewer [vnc://<IP_ADDRESS>:45497 --debug]'","pos":"vnc.go:225","timestamp":"2019-06-03T11:10:51.149621Z"}
{"component":"virtctl","level":"info","msg":"connection timeout: 1m0s","pos":"vnc.go:137","timestamp":"2019-06-03T11:10:51.149391Z"}
{"component":"virtctl","level":"info","msg":"remote-viewer connected in 235.330205ms","pos":"vnc.go:148","timestamp":"2019-06-03T11:10:51.384723Z"}
I didnt see anything further, just a return to the cmd prompt.

that's strange....
does remote-viewer open when you run it manually from the commandline?

I ran as sudo user and see the following:
[dell@k8s-master ~]$ sudo ./virtctl --v 4 --kubeconfig ~/.kube/config vnc flex-vm
[sudo] password for dell:
{"component":"virtctl","level":"info","msg":"connection timeout: 1m0s","pos":"vnc.go:137","timestamp":"2019-06-04T08:49:22.191422Z"}
{"component":"virtctl","level":"info","msg":"Executing commandline: 'remote-viewer [vnc://<IP_ADDRESS>:36657 --debug]'","pos":"vnc.go:225","timestamp":"2019-06-04T08:49:22.191621Z"}
{"component":"virtctl","level":"info","msg":"remote-viewer connected in 659.441483ms","pos":"vnc.go:148","timestamp":"2019-06-04T08:49:22.850865Z"}
Error encountered: websocket: close 1006 (abnormal closure): unexpected EOF
[dell@k8s-master ~]$
I ran remote-viewer as well it came up successfully.

Hi @cclark1974 I see that everything in you cluster is running and that connection hangs. Indeed, this is strange.
Would you please share logs from following pods? I have prepared copy&paste, if you still have the same cluster:
kubectl -n default  logs virt-launcher-flex-vm-v8mwg  -c compute
kubectl -n kube-system  logs kube-apiserver-k8s-master
kubectl -n kubevirt virt-api-65cfcc9cc9-7v559
kubectl -n kubevirt virt-api-65cfcc9cc9-pp9kv
kubectl -n kubevirt virt-controller-8c7b94b6-m7fbj
kubectl -n kubevirt virt-controller-8c7b94b6-v68zz
kubectl -n kubevirt virt-handler-9k5wz
kubectl -n kubevirt virt-handler-sdx7r

Also please, what OS is running in your VM? How was this VM created? I see that it is mounted from PVC, but there is not clue regarding the VM OS itself.
Moreover, can you please ssh into the VM pod and try connecting to socket directly?
kubectl exec -it virt-launcher-flex-vm-v8mwg -c compute bash
$ /usr/share/kubevirt/virt-launcher/sock-connector /var/run/kubevirt-private/<YOUR VM ID GENERATED BY KUBEVIRT>/virt-serial0

It may require hitting return, but then it should allow you to console into the VM. Does it also hangs?
WARNING: You will need to close terminal to exit.
Thank you for your help with fixing this issue.

kubectl -n default  logs virt-launcher-flex-vm-v8mwg  -c compute
Log:
{"component":"virt-launcher","level":"info","msg":"Driver cache mode for /var/run/kubevirt-private/vmi-disks/mypvcdisk/disk.img set to none","pos":"converter.go:165","timestamp":"2019-05-17T17:48:42.853507Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Domain defined.","name":"flex-vm","namespace":"default","pos":"manager.go:517","timestamp":"2019-05-17T17:48:42.950811Z","uid":"fa5f48fe-78cb-11e9-b79a-0026b92c94fc"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event 0 with reason 0 received","pos":"client.go:203","timestamp":"2019-05-17T17:48:42.951060Z"}
{"component":"virt-launcher","level":"error","msg":"internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory","pos":"virDBusGetSystemBus:109","subcomponent":"libvirt","timestamp":"2019-05-17T17:48:43.034000Z"}
{"component":"virt-launcher","level":"error","msg":"At least one cgroup controller is required: No such device or address","pos":"virCgroupDetect:397","subcomponent":"libvirt","timestamp":"2019-05-17T17:48:44.143000Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Paused(3):StartingUp(11)","pos":"client.go:134","timestamp":"2019-05-17T17:48:44.155167Z"}
{"component":"virt-launcher","level":"info","msg":"Detected domain with UUID 3d1a0bb2-80f2-5e73-bd9c-cf414e9c6ae2","pos":"virt-launcher.go:237","timestamp":"2019-05-17T17:48:44.158400Z"}
{"component":"virt-launcher","level":"info","msg":"Monitoring loop: rate 1s start timeout 5m0s","pos":"monitor.go:251","timestamp":"2019-05-17T17:48:44.158495Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:190","timestamp":"2019-05-17T17:48:44.159252Z"}
{"component":"virt-launcher","level":"info","msg":"GuestAgentLifecycle event state 2 with reason 1 received","pos":"client.go:221","timestamp":"2019-05-17T17:48:44.308680Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Paused(3):StartingUp(11)","pos":"client.go:134","timestamp":"2019-05-17T17:48:44.312118Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:190","timestamp":"2019-05-17T17:48:44.313384Z"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event 4 with reason 0 received","pos":"client.go:203","timestamp":"2019-05-17T17:48:44.351520Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Running(1):Unknown(1)","pos":"client.go:134","timestamp":"2019-05-17T17:48:44.361566Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:190","timestamp":"2019-05-17T17:48:44.362666Z"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event 2 with reason 0 received","pos":"client.go:203","timestamp":"2019-05-17T17:48:44.395586Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Domain started.","name":"flex-vm","namespace":"default","pos":"manager.go:548","timestamp":"2019-05-17T17:48:44.412449Z","uid":"fa5f48fe-78cb-11e9-b79a-0026b92c94fc"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"flex-vm","namespace":"default","pos":"server.go:129","timestamp":"2019-05-17T17:48:44.414122Z","uid":"fa5f48fe-78cb-11e9-b79a-0026b92c94fc"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Running(1):Unknown(1)","pos":"client.go:134","timestamp":"2019-05-17T17:48:44.414469Z"}
{"component":"virt-launcher","level":"info","msg":"processed event","pos":"client.go:190","timestamp":"2019-05-17T17:48:44.415658Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"flex-vm","namespace":"default","pos":"server.go:129","timestamp":"2019-05-17T17:48:44.460459Z","uid":"fa5f48fe-78cb-11e9-b79a-0026b92c94fc"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"flex-vm","namespace":"default","pos":"server.go:129","timestamp":"2019-05-17T17:48:44.493404Z","uid":"fa5f48fe-78cb-11e9-b79a-0026b92c94fc"}
{"component":"virt-launcher","level":"info","msg":"Found PID for 3d1a0bb2-80f2-5e73-bd9c-cf414e9c6ae2: 171","pos":"monitor.go:220","timestamp":"2019-05-17T17:48:45.160780Z"}
[dell@k8s-master ~]$
kube-apiserver-k8s-master Log:
certificate is valid for virt-api, virt-api.kubevirt, virt-api.kubevirt.svc, virt-api.kubevirt.svc.cluster.local, not cdi-api.cdi.svc'
Trying to reach: 'https://<IP_ADDRESS>:443/openapi/v2', Header: map[]
I0605 19:51:24.677612       1 controller.go:127] OpenAPI AggregationController: action for item v1alpha1.upload.cdi.kubevirt.io: Rate Limited Requeue.
I0605 19:51:32.238978       1 controller.go:107] OpenAPI AggregationController: Processing item v1alpha3.subresources.kubevirt.io
I0605 19:52:32.240481       1 controller.go:107] OpenAPI AggregationController: Processing item v1alpha3.subresources.kubevirt.io
I0605 19:53:24.677866       1 controller.go:107] OpenAPI AggregationController: Processing item v1alpha1.upload.cdi.kubevirt.io
E0605 19:53:24.687378       1 controller.go:114] loading OpenAPI spec for "v1alpha1.upload.cdi.kubevirt.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: Error: 'x509: certificate is valid for virt-api, virt-api.kubevirt, virt-api.kubevirt.svc, virt-api.kubevirt.svc.cluster.local, not cdi-api.cdi.svc'
Trying to reach: 'https://<IP_ADDRESS>:443/openapi/v2', Header: map[]
I0605 19:53:24.687402       1 controller.go:127] OpenAPI AggregationController: action for item v1alpha1.upload.cdi.kubevirt.io: Rate Limited Requeue.
I0605 19:53:32.241955       1 controller.go:107] OpenAPI AggregationController: Processing item v1alpha3.subresources.kubevirt.io
I0605 19:54:32.243679       1 controller.go:107] OpenAPI AggregationController: Processing item v1alpha3.subresources.kubevirt.io
I0605 19:55:24.657602       1 controller.go:107] OpenAPI AggregationController: Processing item v1alpha1.upload.cdi.kubevirt.io
E0605 19:55:24.667524       1 controller.go:114] loading OpenAPI spec for "v1alpha1.upload.cdi.kubevirt.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: Error: 'x509: certificate is valid for virt-api, virt-api.kubevirt, virt-api.kubevirt.svc, virt-api.kubevirt.svc.cluster.local, not cdi-api.cdi.svc'
Trying to reach: 'https://<IP_ADDRESS>:443/openapi/v2', Header: map[]
I0605 19:55:24.667552       1 controller.go:127] OpenAPI AggregationController: action for item v1alpha1.upload.cdi.kubevirt.io: Rate Limited Requeue.
I0605 19:55:32.245184       1 controller.go:107] OpenAPI AggregationController: Processing item v1alpha3.subresources.kubevirt.io
E0605 19:55:35.754322       1 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
kubectl -n kubevirt virt-api-65cfcc9cc9-7v559
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:57:06.125891Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:57:16.126820Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:57:26.130063Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:57:36.126248Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:57:46.125831Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:57:56.129130Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:58:06.126844Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:58:16.126994Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:58:26.126360Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:58:36.126041Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:58:46.125685Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T19:58:56.127507Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
[dell@k8s-master ~]$
kubectl -n kubevirt virt-api-65cfcc9cc9-pp9kv
{"component":"virt-api","level":"info","msg":"http: TLS handshake error from <IP_ADDRESS>:35138: remote error: tls: bad certificate\n","pos":"server.go:2979","timestamp":"2019-06-05T20:00:47.904075Z"}
{"component":"virt-api","contentLength":552,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T20:00:48.591034Z","url":"/apis/subresources.kubevirt.io/v1alpha3?timeout=32s","username":"-"}
{"component":"virt-api","level":"info","msg":"http: TLS handshake error from <IP_ADDRESS>:35148: remote error: tls: bad certificate\n","pos":"server.go:2979","timestamp":"2019-06-05T20:00:49.299241Z"}
{"component":"virt-api","contentLength":146,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T20:00:53.661450Z","url":"/","username":"-"}
{"component":"virt-api","contentLength":146,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T20:00:53.661552Z","url":"/","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T20:00:55.388053Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T20:01:05.388031Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":552,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T20:01:05.639928Z","url":"/apis/subresources.kubevirt.io/v1alpha3?timeout=32s","username":"-"}
{"component":"virt-api","level":"info","msg":"http: TLS handshake error from <IP_ADDRESS>:35254: remote error: tls: bad certificate\n","pos":"server.go:2979","timestamp":"2019-06-05T20:01:05.651175Z"}
{"component":"virt-api","contentLength":349,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T20:01:15.388312Z","url":"/apis/subresources.kubevirt.io/v1alpha3/healthz","username":"-"}
{"component":"virt-api","contentLength":552,"level":"info","method":"GET","pos":"filter.go:46","proto":"HTTP/2.0","remoteAddress":"<IP_ADDRESS>","statusCode":200,"timestamp":"2019-06-05T20:01:20.296508Z","url":"/apis/subresources.kubevirt.io/v1alpha3?timeout=32s","username":"-"}
[dell@k8s-master ~]$
kubectl -n kubevirt virt-controller-8c7b94b6-m7fbj
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5902689 (5903749)","pos":"reflector.go:270","timestamp":"2019-06-05T18:22:04.146039Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5904036 (5904802)","pos":"reflector.go:270","timestamp":"2019-06-05T18:28:13.152101Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5905088 (5906424)","pos":"reflector.go:270","timestamp":"2019-06-05T18:37:42.158550Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5906709 (5907441)","pos":"reflector.go:270","timestamp":"2019-06-05T18:43:41.164809Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5907729 (5908864)","pos":"reflector.go:270","timestamp":"2019-06-05T18:52:00.170713Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5909148 (5910356)","pos":"reflector.go:270","timestamp":"2019-06-05T19:00:43.176277Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5910636 (5911653)","pos":"reflector.go:270","timestamp":"2019-06-05T19:08:20.182426Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5911940 (5912549)","pos":"reflector.go:270","timestamp":"2019-06-05T19:13:34.188557Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5912837 (5914036)","pos":"reflector.go:270","timestamp":"2019-06-05T19:22:16.194454Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5914323 (5915034)","pos":"reflector.go:270","timestamp":"2019-06-05T19:28:07.200824Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5915320 (5916633)","pos":"reflector.go:270","timestamp":"2019-06-05T19:37:28.206181Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5916920 (5918248)","pos":"reflector.go:270","timestamp":"2019-06-05T19:46:55.212091Z"}
{"component":"virt-controller","level":"warning","msg":"kubevirt.io/kubevirt/pkg/controller/virtinformers.go:168: watch of *v1.ConfigMap ended with: too old resource version: 5918535 (5919870)","pos":"reflector.go:270","timestamp":"2019-06-05T19:56:24.218129Z"}
kubectl -n kubevirt logs virt-controller-8c7b94b6-v68zz
{"component":"","level":"info","msg":"kubevirt-config ConfigMap does not exist. Using defaults.","pos":"config-map.go:75","timestamp":"2019-05-16T17:50:21.321459Z"}
{"component":"virt-controller","level":"info","msg":"DataVolume integration disabled","pos":"application.go:177","timestamp":"2019-05-16T17:50:21.334435Z"}
{"component":"virt-controller","level":"info","msg":"attempting to acquire leader lease  kubevirt/virt-controller...","pos":"leaderelection.go:205","timestamp":"2019-05-16T17:50:22.516197Z"}
{"action":"listening","component":"virt-controller","interface":"<IP_ADDRESS>","level":"info","port":8443,"pos":"application.go:203","service":"http","timestamp":"2019-05-16T17:50:22.516172Z"}
what OS is running in your VM? How was this VM created?
Ubuntu OS
Launched through kubectl yaml

I attempted to connect however it just hangs...
/usr/share/kubevirt/virt-launcher/sock-connector  /var/run/kubevirt-private/fa5f48fe-78cb-11e9-b79a-0026b92c94fc/virt-serial0
Hit return several times nothing came back.

The thing that might cause your issue is the VM itself. When you connect to the socket directly
/usr/share/kubevirt/virt-launcher/sock-connector /var/run/kubevirt-private/fa5f48fe-78cb-11e9-b79a-0026b92c94fc/virt-serial0

it should connect. It hangs or fails, when the VM was not properly set up for TTY.
How did you create the Ubuntu VM?

/usr/share/kubevirt/virt-launcher/sock-connector /var/run/kubevirt-private/fa5f48fe-78cb-11e9-b79a-0026b92c94fc/virt-serial0
-bash: /usr/share/kubevirt/virt-launcher/sock-connector: No such file or directory
I am not seeing it connect.
I launched the VM via: kubectl apply -f vm.yaml

Hi @cclark1974 it confirms my suspicion. The issue is with the VM.
How was the ubuntu VM created (the image)? Where did you get he VM image?

I created the VM based off a qcow2 image.
./virtctl image-upload --no-create --pvc-name=flex-vnf-volume-claim --pvc-size=80Gi --image-path=flexvnf.qcow2 --uploadproxy-url=https://<IP_ADDRESS>:2222 --insecure

@cclark1974 I know it may sound crazy but - please try to add rng: {} to VMI devices section and reboot. There is a bug with newer guest kernels that may lock booting its OS due to lack of entropy: https://github.com/kubevirt/kubevirt/issues/1847 and I wonder if you may have hit it here too. Worth a try.

Could you please elaborate?  Add rng: {} to devices section where?  Thanks

Is the sufficient to restart the VM? virtctl restart flex-vm

@cclark1974 there is no user guide documentation merged yet for RNG but you can follow this: https://github.com/kubevirt/user-guide/pull/262/files Do you think you can recreate the VM(I) with RNG device added and see if it helps in any way?

Ok I recreated the VM with the rng: added.

Im still not seeing anything in:
k8s-master ~]$ ls /var/run/kubevirt-private/
k8s-master ~]$

The VM reports:
Spec:
Running:  true
Template:
Metadata:
Creation Timestamp:
Labels:
Kubevirt . Io / Size:  small
Kubevirt . Io / Vm:    flex-vm
Spec:
Domain:
Devices:
Disks:
Disk:
Name:  mypvcdisk
Interfaces:
Bridge:
Name:  default
Rng:
Machine:
Type:
Resources:
Requests:
Memory:  4G
Networks:
Name:  default
Pod:
Termination Grace Period Seconds:  0
Volumes:
Name:  mypvcdisk
Persistent Volume Claim:
Claim Name:  flex-vnf-volume-claim
Status:
Created:  true
Ready:    true

Am I missing anything?

Hi @cclark1974 does this issue resolved itself with newer version of KubeVirt or does it still apply?

I’ll have to check I haven’t been able to verify
On Tuesday, August 20, 2019, Petr Kotas<EMAIL_ADDRESS>wrote:

Hi @cclark1974 https://github.com/cclark1974 does this issue resolved
itself with newer version of KubeVirt or does it still apply?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubevirt/kubevirt/issues/2303?email_source=notifications&email_token=AE6AD3VXLMITGHQDZFP5J2DQFQEKDA5CNFSM4HOKS34KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4WVY4Q#issuecomment-523066482,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE6AD3RMGY55EVDLJGL6KWTQFQEKDANCNFSM4HOKS34A
.

I also encountered this problem.  k8s version:1.20 kubevirt version:0.49 centos7u4.


Unclear error message when try publish package with not matching name and slug

You got message about fact you have not remote tag for your that suggest you to push tags to remote, even when there is already that tag.
{
...
"name": "username/my-package"
}

but it lives in username/my-package-something-else
as result i got Error:
-- NO TAG ON GITHUB ------------------------------------------------------------

You have version 1.0.0 tagged locally, but not on GitHub.

Run the following command to make this tag available on GitHub:

    git push origin 1.0.0

This will make it possible to find your code online based on the version number.

That is totally wrong - as repo already have that tag. Maybe we could add validation about fact, that slug (username/repo) matches name in elm.json

Isn't it better to expand the error message to show e.g. if the repo exists at all, ask users to double-check the git url, and maybe print the tags it did find? The github api that the compiler uses to download code gives 404 for both wrong url and non-existant tag, so the compiler currently doesn't know which of those two error cases you hit, but it could print a hint.

Also I believe that the compiler does not know the actual repo name.
It could eventually compare the name in elm.json to some remote in .git/config remotes, but the logic to find the actual correct remote might not be trivial/robust as you can have several ones.


Using array in cURL POSTFIELDS handled differently than string

Hey @adri
I have a few curl_setopt(...) calls that supply an array to CURLOPT_POSTFIELDS that are not playing well with VCR. On closer inspection, it seems that when you supply an array of parameters to CURLOPT_POSTFIELDS as supported by cURL, VCR handles it differently than if you just supply a string of urlencoded data.
The HttpClient uses $request->getBody() as the body content of the request, but due to the difference in handling CURLOPT_POSTFIELDS, supplying an array results in no body ever being set. Therefore the VCR wrapped request doesn't work
I'm wondering if this is intentional or an oversight. Thoughts/Comments/Advise?

Hey @stevemiketa Thanks a lot! I'm sorry for my late answer.
The highlighted code mimics curl_setopt behaviour when an array is specified as value.
From the CURLOPT_POSTFIELDS documentation:

this parameter can either be passed as a urlencoded string like 'para1=val1&para2=val2&...' or as an array with the field name as key and field data as value. If value is an array, the Content-Type header will be set to multipart/form-data.

Setting the post fields using setPostField does that.
Do you have a few example calls where a different behaviour is expected? That would be very helpful.

Hey, sorry I lost track of this! I will provide you with my example soon!
The issue is that when VCR intercepts the request and sends the code, it sends the body. But when you supply the array of key value data, the body never gets set on the request. So when the client tries to make the request, the body is empty.


Use -mod=vendor for golangci-lint too 👼

Changes

--modules-download-mode string Modules download mode. If not empty,
passed as -mod= to go tools

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

/lgtm
Looking Good! 🤙🏽