feat: Add support for multiple plugins with a single ApisixConsumer

Description
I want to use multiple auth mechanism in a single route which requires to create consumer with multiple auth plugin. This is possible via apisix admin api. Example:
curl http://localhost:9180/apisix/admin/consumers -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
    "username": "xyz",
    "plugins": {
        "hmac-auth": {
            "access_key": "ejncd934fie",
            "secret_key": "whrbkjndc239o",
            "validate_request_body": true
        },
        "key-auth": {
            "key": "auth-one"
        }
    }
}'

But for convenience I want to keep it in config file and want to create consumer via ApisixConsumer CRD. I want something like this:
kind: ApisixConsumer
metadata:
  name: jack
spec:
  authParameter:
      hmacAuth:
        value:
          access_key: "ejncd934fie"
          secret_key: "whrbkjndc239o"
          validate_request_body: true
      keyAuth:
        value:
          key: "auth-one"

It works for single plugin consumer But more than one schema (plugin config) is not supported, hence throwing error :

The ApisixConsumer "jack" is invalid: : Invalid value: "": "spec.authParameter" must validate one and only one schema (oneOf). Found 2 valid alternatives

Kindly add support for the above mentioned feature.

I also think this feature would be very useful. If I am not mistaken, I think it is possible to do this using the dashboard.


Dynamic progress bar perentage.

Is there any option to dynamically update the progress bar % values?

the percentage value is calculated automatically, you have to change the total/current values


problem in setup project

I am new to the Ios developent and
As instructions given in readme file i followed and installed project after updating pods i am getting error in code related to firebase the error is saying that
"FIRAuth is change to Auth and FIRDatabase change to Database"
when i try to change FIRAuth to Auth another errors start coming.
when i was updating the pod file message was showing that Firebase(4.8.2) was 3.10.0
that may have cause this problem.
what would be the possible solution for this problem any suggestion will be helpful.

It’s because the FireBase was updated to ver. 4 that has broken the project. If you still need this you can try the fixed version: https://github.com/IvanYurchenko/Quick-Chat I created a pull request, but I’m not sure if the author of this repo comes frequently enough to merge it.

@IvanYurchenko  thank you for the help got it up and running.

Were you able to make it work? I was able to compile and run it but it doesn’t allow me to register correctly and when I’m trying to log in it tells me that "You are alone in this world".

@IvanYurchenko
i have registered two users and i was able to send messages from one user to another user.
when i register for first time i got "You are alone in this world" then i logut that user and register another user and everything works fine i can see the new user from the users tab.

@d33pak-s1ngh Could you please share your project? Registration is broken for me for some reason and I can’t make it working regardless of what I’m doing. It just stucks on the loading spinner when I press Register and then either registers the user in some incorrect way or doesn’t register at all.

have u setup your firebase setup properly ? can you see the users into
firebase database when you register any user ?
On Mon, Feb 19, 2018 at 2:45 PM, Ivan Yurchenko<EMAIL_ADDRESS>wrote:

@d33pak-s1ngh https://github.com/d33pak-s1ngh Could you please share
your project? Registration is broken for me for some reason and I can’t
make it working regardless of what I’m doing. It just stucks on the loading
spinner when I press Register and then either registers the user in some
incorrect way or doesn’t register at all.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aslanyanhaik/Quick-Chat/issues/53#issuecomment-366629317,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWiDMPpONZYOGbnP-k0N-OPoZyrWmJafks5tWTuWgaJpZM4R4ESt
.

@d33pak-s1ngh Excuse me for a long response, haven't had a chance to work on this. Yes, I can see registered users but it still tells me that I'm alone.

well i have done nothing extra then installing the project you shared to
me. i have also seen the same message, i tried to login from the other
registered users and then i was able to see the users list. so please try
to login from the users that you have registered.
On Mon, Feb 26, 2018 at 5:16 PM, Ivan Yurchenko<EMAIL_ADDRESS>wrote:

@d33pak-s1ngh https://github.com/d33pak-s1ngh Excuse me for a long
response, haven't had a chance to work on this. Yes, I can see registered
users but it still tells me that I'm alone.
[image: qqqq authentication firebase console 2018-02-26 13-43-45]
https://user-images.githubusercontent.com/13982503/36668887-6da9cf82-1afb-11e8-990b-b973cb204be7.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aslanyanhaik/Quick-Chat/issues/53#issuecomment-368475204,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWiDMOXvscK1uziZhh2r6ZTqOV3LESRRks5tYpmWgaJpZM4R4ESt
.

Quick-Chat-master copy.zip
https://drive.google.com/file/d/1EWeG8cWLQVYbzG2nVvg3VlXvnsa1s80c/view?usp=drive_web

On Mon, Feb 26, 2018 at 5:26 PM, Deepak Rajput<EMAIL_ADDRESS>wrote:

well i have done nothing extra then installing the project you shared to
me. i have also seen the same message, i tried to login from the other
registered users and then i was able to see the users list. so please try
to login from the users that you have registered.
On Mon, Feb 26, 2018 at 5:16 PM, Ivan Yurchenko<EMAIL_ADDRESS>wrote:

@d33pak-s1ngh https://github.com/d33pak-s1ngh Excuse me for a long
response, haven't had a chance to work on this. Yes, I can see registered
users but it still tells me that I'm alone.
[image: qqqq authentication firebase console 2018-02-26 13-43-45]
https://user-images.githubusercontent.com/13982503/36668887-6da9cf82-1afb-11e8-990b-b973cb204be7.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aslanyanhaik/Quick-Chat/issues/53#issuecomment-368475204,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWiDMOXvscK1uziZhh2r6ZTqOV3LESRRks5tYpmWgaJpZM4R4ESt
.

@d33pak-s1ngh Thank you for assistance! I've tried your project and it doesn't work for me as well. I'll try to create my Firebase project from scratch, maybe the problem is there. And yeah, I accessed from iphone and simulator simultaneously and it still didn't work.

Add your google plist file in the project which i have shared.
If you want chat application, there is a channel on youtube "lets build
that app" there is play list available for creating firebase chat which i
have followed.
On Feb 26, 2018 9:11 PM, "Ivan Yurchenko"<EMAIL_ADDRESS>wrote:

@d33pak-s1ngh https://github.com/d33pak-s1ngh Thank you for assistance!
I've tried your project and it doesn't work for me as well. I'll try to
create my Firebase project from scratch, maybe the problem is there. And
yeah, I accessed from iphone and simulator simultaneously and it still
didn't work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aslanyanhaik/Quick-Chat/issues/53#issuecomment-368544471,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWiDMIfNtTeA70XEKXPpLgK_GU7sAyiVks5tYtCZgaJpZM4R4ESt
.

Oh awesome, thank you very much for the recommendation! I'll try to go through it. Do you have a source code of finished app somewhere so I could watch it while doing mine?
Also, do you have telegram or something? I could help you with back-end/front-end development if you'll ever need it. 😄

And yea, I added google plist to the project though it still doesn't work and gets stuck when I click Register button.

Hey,
I just signed the petition "Amazon.com: Amazon Stop insulting Hindus with
Floor Mats and Toilet Mats with Hindu Gods." and wanted to see if you could
help by adding your name.
Our goal is to reach 50,000 signatures and we need more support. You can
read more and sign the petition here:
http://chng.it/4N9KSmYcsP
Thanks!
Deepak


Unable to Setup Checks with Fastlane

The following error offers no help and no clear way to understand why there is a failure:
HTTP request to checks.google.com failed with
status: 403
body:
{
  "error": {
    "code": 403,
    "message": "The caller does not have permission",
    "status": "PERMISSION_DENIED"
  }
}

Permission denied is absolutely inadequate when you have multiple account numbers, keys, service accounts and myriad other authentication hoops to jump through to understand how to use the software. Additionally, the documentation on this repo for the specific task of setting up a service account with Google goes to a 404 page.

Ah fount the actual documentation: https://developers.google.com/checks/guide/integrate/cli/install-checks-cli#authenticate-service
Good grief.


Please provide sample for saving disconnected entities with relationship changes

I met issues when I wanna save disconnected entities which has relationship changes(navigation property changes), I don't know whether it is bug or not ... could you team provide a sample for demonstrating the correct way for saving disconnected entities with relationship changes.
Thanks a lot.

@ajcvickers

@vincedan There is a sample referenced from the documentation page.


Auto-Commit Produces [Teradata Database] [TeraJDBC <IP_ADDRESS>] [Error 3932] [SQLState 25000] Only an ET or null statement is legal after a DDL Statement.

Description
In Auto-Commit mode this error occurs.
SQL Error [3932] [25000]: [Teradata Database] [TeraJDBC <IP_ADDRESS>] [Error 3932] [SQLState 25000] Only an ET or null statement is legal after a DDL Statement.
This was working in Community Edition 24.0.2
DBeaver Version
Community Edition 24.0.3
Operating System
macOS Sonoma
Database and driver
Teradata Database <IP_ADDRESS>
com.teradata.jdbc.TeraDriver <IP_ADDRESS>
Steps to reproduce
CREATE SET TABLE EMPLOYEE,FALLBACK (
EmployeeNo INTEGER,
FirstName VARCHAR(30),
LastName VARCHAR(30),
DOB DATE FORMAT 'YYYY-MM-DD',
JoinedDate DATE FORMAT 'YYYY-MM-DD',
DepartmentNo BYTEINT
)
UNIQUE PRIMARY INDEX ( EmployeeNo );
INSERT INTO Employee (
EmployeeNo,
FirstName,
LastName,
BirthDate,
JoinedDate,
DepartmentNo
)
VALUES (
101,
'Mike',
'James',
'1980-01-05',
'2005-03-27',
01
);
COLLECT STATS ON
EMPLOYEE INDEX (EmployeeNo);
Additional context
No response

Thank you for report.
Could you try switching Blank line is statement delimiter setting to Always? Does it help?

Hi Elizabeth, yes that worked! Thank you for your quick response.
David Whittaker
Global Practice, Sr. Technologist | Success Enablement
Teradata Applications Center of Excellence
m:<PHONE_NUMBER>
linkedin.com/in/dgwhittaker
[A black and orange text  Description automatically generated]https://www.teradata.com/
17095 Via Del Campo Ct.
San Diego, CA 92127
teradata.comhttps://www.teradata.com/
From: Elizabeth @.>
Date: Thursday, April 25, 2024 at 10:26 AM
To: dbeaver/dbeaver @.>
Cc: Whittaker, David @.>, Author @.>
Subject: [EXTERNAL] Re: [dbeaver/dbeaver] Auto-Commit Produces [Teradata Database] [TeraJDBC <IP_ADDRESS>] [Error 3932] [SQLState 25000] Only an ET or null statement is legal after a DDL Statement. (Issue #26772)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
[CAUTION: External Email]
Thank you for report.
Could you try switching Blank line is statement delimiter setting to Always? Does it help?
image.png (view on web)https://github.com/dbeaver/dbeaver/assets/28875055/be8457a0-d62c-4acb-ac2f-67ce518cf3f5
—
Reply to this email directly, view it on GitHubhttps://github.com/dbeaver/dbeaver/issues/26772#issuecomment-2077339184, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASY7SBG56755VCZHF7Z36BLY7EHCRAVCNFSM6AAAAABGYYPC7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXGMZTSMJYGQ.
You are receiving this because you authored the thread.Message ID: @.***>

The fix will be included in DBeaver 24.0.4.
Also you can try Early Access version with fix https://dbeaver.io/files/ea/ now.


Update .travis.yml

Coverage remained the same at 99.573% when pulling d6bb18f0a8f86ee7610574d1f5ae3ab07d39ceba on andreybolonin:patch-1 into c72d50304716c60a8c016eaf2b0faf2fca72f46d on marcelog:master.

Coverage remained the same at 99.573% when pulling d6bb18f0a8f86ee7610574d1f5ae3ab07d39ceba on andreybolonin:patch-1 into c72d50304716c60a8c016eaf2b0faf2fca72f46d on marcelog:master.


fixed mono sound playback

mono sounds were split as well and sounded weird

@CatCuddler has openend a PR for this as well https://github.com/KTXSoftware/Kore/pull/123 so i'm closing mine

Uh, sorry, should have merged earlier.


chore: bdd-sbhg-1592584862 to 0.0.1

chore: Promote bdd-sbhg-1592584862 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add header and footer in login page

improve the over all design of login page
you can get the design from figma file.
get design from README.md file
https://www.figma.com/file/hXcM6chTK70O6rAqCTFxuc/Vigy?node-id=0%3A1&t=px6VNjlFCos5Ll9z-1

Hey vivek, I would like to work on this issue.

I believe that adding a polished header and footer to the login page can significantly elevate its overall aesthetics and user-friendliness. I'm excited to take on this task, leveraging my design skills and attention to detail to create a seamless and visually appealing login experience for our users.

Hello, Vivek
please assigned me on this project.

Can I work on this issue

Hello, Vivek
please assigned me on this project.

I can improve the over all design of login page. Can you please assign me to this issue !!

Hello @codervivek5 , I hope you're doing well. I'm interested in contributing to this task of adding header and footer to the login page. I am eager to help in any way I can and believe I can make valuable contributions to the project. I humbly request you to assign me with the task.
Thank you for considering my request. I look forward to your response.

any update @namithashaji

Almost done. Will be finished in these days.

OK..... I will check and if everything is okay then I will merge your PR :)


Add support for local machine ID

This is in the context of issue https://github.com/signadot/signadot/issues/3837.
Runs on top of the following PRs: https://github.com/signadot/signadot/pull/3857, https://github.com/signadot/libconnect/pull/38, https://github.com/signadot/go-sdk/pull/36

started the review.
Some comments/questions:

Should we remove the api related stuff from internal/config/locald.go?

Not sure, I understand what you mean by that, can you expand?

Should we remove the grpc/go-sdk model conversions?

Do you mean across the whole CLI? (what would look like a massive change to me).

Should we detect operator version and error out on old operator appropriately (since local is beta)?

I think that's a good idea.

Should we remove the grpc/go-sdk model conversions?

Do you mean across the whole CLI? (what would look like a massive change to me).

I renamed these funcs:
23-11-09 scott@air cli % git diff | grep func
-func ToModelsSandboxSpec(grpcSpec *structpb.Struct) (*models.SandboxSpec, error) {
+func xToModelsSandboxSpec(grpcSpec *structpb.Struct) (*models.SandboxSpec, error) {
@@ -23,7 +23,7 @@ func ToModelsSandboxSpec(grpcSpec *structpb.Struct) (*models.SandboxSpec, error)
-func ToGRPCSandbox(sb *models.Sandbox) (*structpb.Struct, error) {
+func xToGRPCSandbox(sb *models.Sandbox) (*structpb.Struct, error) {
@@ -32,7 +32,7 @@ func ToGRPCSandbox(sb *models.Sandbox) (*structpb.Struct, error) {
-func ToGRPCSandboxSpec(sbs *models.SandboxSpec) (*structpb.Struct, error) {
+func xToGRPCSandboxSpec(sbs *models.SandboxSpec) (*structpb.Struct, error) {
@@ -42,7 +42,7 @@ func ToGRPCSandboxSpec(sbs *models.SandboxSpec) (*structpb.Struct, error) {
-func ToModelsSandbox(grpcSandbox *structpb.Struct) (*models.Sandbox, error) {
+func xToModelsSandbox(grpcSandbox *structpb.Struct) (*models.Sandbox, error) {

in internal/locald/api/sandboxmanager/convert and it compiles fine, so they are now unused.

Should we remove the api related stuff from internal/config/locald.go?

Not sure, I understand what you mean by that, can you expand?

Sorry, it was too vague.  Was thinking that with the removal of sandbox apply from sandbox manager, we would probably not need the api key nor initialise APIConfig inside of anything in locald.  I thought I remembered adding this CIConfig api support specifically for the sandbox apply proxy, and greping around it looks to me like we can remove APIKey from the CIConfig struct, as well as related code setting up the config for a *manager to communicate with the API.
wdyt?

@scott-cotton, I implemented this:

Should we detect operator version and error out on old operator appropriately (since local is beta)?

In PR https://github.com/signadot/cli/pull/92

Should we remove the grpc/go-sdk model conversions?

Do you mean across the whole CLI? (what would look like a massive change to me).

I renamed these funcs:
23-11-09 scott@air cli % git diff | grep func
-func ToModelsSandboxSpec(grpcSpec *structpb.Struct) (*models.SandboxSpec, error) {
+func xToModelsSandboxSpec(grpcSpec *structpb.Struct) (*models.SandboxSpec, error) {
@@ -23,7 +23,7 @@ func ToModelsSandboxSpec(grpcSpec *structpb.Struct) (*models.SandboxSpec, error)
-func ToGRPCSandbox(sb *models.Sandbox) (*structpb.Struct, error) {
+func xToGRPCSandbox(sb *models.Sandbox) (*structpb.Struct, error) {
@@ -32,7 +32,7 @@ func ToGRPCSandbox(sb *models.Sandbox) (*structpb.Struct, error) {
-func ToGRPCSandboxSpec(sbs *models.SandboxSpec) (*structpb.Struct, error) {
+func xToGRPCSandboxSpec(sbs *models.SandboxSpec) (*structpb.Struct, error) {
@@ -42,7 +42,7 @@ func ToGRPCSandboxSpec(sbs *models.SandboxSpec) (*structpb.Struct, error) {
-func ToModelsSandbox(grpcSandbox *structpb.Struct) (*models.Sandbox, error) {
+func xToModelsSandbox(grpcSandbox *structpb.Struct) (*models.Sandbox, error) {

in internal/locald/api/sandboxmanager/convert and it compiles fine, so they are now unused.

Oh, I see! It's done now.

Should we remove the api related stuff from internal/config/locald.go?

Not sure, I understand what you mean by that, can you expand?

Sorry, it was too vague. Was thinking that with the removal of sandbox apply from sandbox manager, we would probably not need the api key nor initialise APIConfig inside of anything in locald. I thought I remembered adding this CIConfig api support specifically for the sandbox apply proxy, and greping around it looks to me like we can remove APIKey from the CIConfig struct, as well as related code setting up the config for a *manager to communicate with the API.
wdyt?

Got it, yes, looks like a good idea.
I will check it and remove unneeded things.

Should we remove the api related stuff from internal/config/locald.go?

Not sure, I understand what you mean by that, can you expand?

Sorry, it was too vague. Was thinking that with the removal of sandbox apply from sandbox manager, we would probably not need the api key nor initialise APIConfig inside of anything in locald. I thought I remembered adding this CIConfig api support specifically for the sandbox apply proxy, and greping around it looks to me like we can remove APIKey from the CIConfig struct, as well as related code setting up the config for a *manager to communicate with the API.
wdyt?

@scott-cotton, this is done now, in https://github.com/signadot/cli/pull/91/commits/eaf51d88248e472a8cafec20433975ce1a1cd6cc


WH517S controls not working

Include all of the following:

Model - WH517S
Number of speeds the fan supports (not including "off") 3
Does the fan support oscillating? No
What preset modes are supported? Hi Med Low
Is temperature supported? Yes

Make sure you've installed this integration, then from the integration settings page, select Download Diagnostics and attach that file.
I know this unit is not one of the ones listed, so I wanted to give some feedback. Let me know if I can provide anything to help get this unit fully working with Home Assistant.
I have the integration and have linked my heater to it.
I can turn the device on and off with Home Assistant.... once. After I turn it off, it no longer reacts to any input. Home Assistant, the Dreo app, or even the control panel on the unit. Nothing works until I unplug it and plug it back in. Also, if I use Home Assistant to turn the unit off, it doesn't register that it has been turned off in the app.
If I don't use Home Assistant and only use the app or on-board controls, it works fine.

https://github.com/JeffSteinbok/hass-dreo/pull/237


Install fails on VirtualBox 6.1.6

seems installation is failing for me.
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18363 N/A Build 18363
Vagrant: Vagrant 2.2.7
Virtual Box: Version 6.1.6 r137129 (Qt5.6.2)
Laravel Homestead commit 387598313fbb0e44864f59d6e45a7cc0db7eba0d
Stock vagrantfile & config from fresh Laravel Homestead setup ^
Was getting:
GuestAdditions versions on your host (6.1.6) and guest (6.1.4) do not match
so I tried manually specifying the url:
config.vbguest.iso_path = "https://download.virtualbox.org/virtualbox/6.1.6/VBoxGuestAdditions_6.1.6.iso"
still ended up with:
C:\Users\mail\Code\Homestead> vagrant up --provision
Bringing machine 'homestead' up with 'virtualbox' provider...
==> homestead: Importing base box 'laravel/homestead'...
==> homestead: Matching MAC address for NAT networking...
==> homestead: Checking if box 'laravel/homestead' version '9.5.0-alpha1' is up to date...
==> homestead: Setting the name of the VM: homestead
==> homestead: Clearing any previously set network interfaces...
==> homestead: Preparing network interfaces based on configuration...
    homestead: Adapter 1: nat
    homestead: Adapter 2: hostonly
==> homestead: Forwarding ports...
    homestead: 80 (guest) => 8000 (host) (adapter 1)
    homestead: 443 (guest) => 44300 (host) (adapter 1)
    homestead: 3306 (guest) => 33060 (host) (adapter 1)
    homestead: 4040 (guest) => 4040 (host) (adapter 1)
    homestead: 5432 (guest) => 54320 (host) (adapter 1)
    homestead: 8025 (guest) => 8025 (host) (adapter 1)
    homestead: 9600 (guest) => 9600 (host) (adapter 1)
    homestead: 27017 (guest) => 27017 (host) (adapter 1)
    homestead: 22 (guest) => 2222 (host) (adapter 1)
==> homestead: Running 'pre-boot' VM customizations...
==> homestead: Booting VM...
==> homestead: Waiting for machine to boot. This may take a few minutes...
    homestead: SSH address: <IP_ADDRESS>:2222
    homestead: SSH username: vagrant
    homestead: SSH auth method: private key
    homestead: Warning: Connection reset. Retrying...
    homestead:
    homestead: Vagrant insecure key detected. Vagrant will automatically replace
    homestead: this with a newly generated keypair for better security.
    homestead:
    homestead: Inserting generated public key within guest...
    homestead: Removing insecure key from the guest if it's present...
    homestead: Key inserted! Disconnecting and reconnecting using new SSH key...
==> homestead: Machine booted and ready!
[homestead] GuestAdditions versions on your host (6.1.6) and guest (6.1.4) do not match.
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version (2.3-3ubuntu9.7).
linux-headers-4.15.0-91-generic is already the newest version (4.15.0-91.92).
linux-headers-4.15.0-91-generic set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Downloading VirtualBox Guest Additions ISO from https://download.virtualbox.org/virtualbox/6.1.6/VBoxGuestAdditions_6.1.6.iso

Copy iso file C:/Users/mail/.vagrant.d/tmp/VBoxGuestAdditions_6.1.6.iso into the box /tmp/VBoxGuestAdditions.iso
Cleaning up downloaded VirtualBox Guest Additions ISO...
==> homestead: Checking for guest additions in VM...
==> homestead: Forcing shutdown of VM...
==> homestead: Destroying VM and associated drives...
C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/buffered_io.rb:66:in `recv': An existing connection was forcibly closed by the remote host. - recvfrom(2) (Errno::ECONNRESET)
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/buffered_io.rb:66:in `fill'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/session.rb:275:in `block in ev_do_handle_events'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/session.rb:271:in `each'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/session.rb:271:in `ev_do_handle_events'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/event_loop.rb:112:in `ev_select_and_postprocess'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/event_loop.rb:31:in `process'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/session.rb:228:in `process'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/session.rb:181:in `block in loop'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/session.rb:181:in `loop'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/session.rb:181:in `loop'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-ssh-5.1.0/lib/net/ssh/connection/channel.rb:272:in `wait'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-scp-1.2.1/lib/net/scp.rb:284:in `upload!'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/communicators/ssh/communicator.rb:327:in `block (2 levels) in upload'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/communicators/ssh/communicator.rb:333:in `block in upload'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/communicators/ssh/communicator.rb:742:in `block in scp_connect'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/communicators/ssh/communicator.rb:382:in `connect'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/communicators/ssh/communicator.rb:740:in `scp_connect'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/communicators/ssh/communicator.rb:303:in `upload'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/installers/base.rb:230:in `upload'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/installers/linux.rb:66:in `install'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/installers/debian.rb:22:in `install'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/installers/ubuntu.rb:19:in `install'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/installer.rb:63:in `install'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/machine.rb:106:in `block (2 levels) in guest_additions_state'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/micromachine-3.0.0/lib/micromachine.rb:53:in `block in change'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/micromachine-3.0.0/lib/micromachine.rb:53:in `each'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/micromachine-3.0.0/lib/micromachine.rb:53:in `change'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/micromachine-3.0.0/lib/micromachine.rb:23:in `trigger'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/machine.rb:39:in `install'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/machine.rb:25:in `run'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-vbguest-0.23.0/lib/vagrant-vbguest/middleware.rb:25:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/customize.rb:40:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/wait_for_communicator.rb:71:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/customize.rb:40:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/boot.rb:18:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/customize.rb:40:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/disk.rb:25:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/sane_defaults.rb:38:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/set_hostname.rb:16:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/forward_ports.rb:31:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/network_fix_ipv6.rb:41:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/network.rb:123:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/clear_network_interfaces.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/set_default_nic_type.rb:64:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:19:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/synced_folders/nfs/action_cleanup.rb:19:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:49:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/env_set.rb:19:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/Users/mail/.vagrant.d/gems/2.4.9/gems/vagrant-hostmanager-1.8.9/lib/vagrant-hostmanager/action/update_all.rb:27:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/provision.rb:80:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/set_name.rb:50:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/clean_machine_folder.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:130:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:130:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:130:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/box_check_outdated.rb:92:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:130:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/match_mac_address.rb:22:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/discard_state.rb:15:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/import.rb:74:in `import'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/import.rb:13:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/prepare_clone_snapshot.rb:17:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/prepare_clone.rb:15:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/customize.rb:40:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:130:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:130:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:130:in `block in finalize_action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/call.rb:53:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/check_virtualbox.rb:26:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builder.rb:116:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `block in run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/runner.rb:102:in `run'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/machine.rb:238:in `action_raw'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/machine.rb:209:in `block in action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/environment.rb:613:in `lock'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/machine.rb:195:in `call'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/machine.rb:195:in `action'
        from C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run'

If I uninstall vagrant-vbguest plugin, my vagrant box provisions successfully

when i first run vagrant up, i got the similiar error.
and i try to downgrade the virtualbox to 6.1.4/6.1.2/6.1.0, the error still exist,

[temp-node1] No Virtualbox Guest Additions installation found.
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile

base: mirrors.huaweicloud.com
extras: mirrors.huaweicloud.com
updates: mirrors.huaweicloud.com
Package centos-release-7-8.2003.0.el7.centos.x86_64 already installed and latest version
Nothing to do
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
base: mirrors.huaweicloud.com
extras: mirrors.huaweicloud.com
updates: mirrors.huaweicloud.com
http://vault.centos.org/7.7.1908/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors
If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
One of the configured repositories failed (CentOS-7.7.1908 - Base),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Run the command with the repository temporarily disabled
        yum --disablerepo=C7.7.1908-base ...

 4. Disable the repository permanently, so yum won't use it by default. Yum
    will then just ignore the repository until you permanently enable it
    again or use --enablerepo for temporary usage:

        yum-config-manager --disable C7.7.1908-base
    or
        subscription-manager repos --disable=C7.7.1908-base

 5. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=C7.7.1908-base.skip_if_unavailable=true

failure: repodata/repomd.xml from C7.7.1908-base: [Errno 256] No more mirrors to try.
http://vault.centos.org/7.7.1908/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

@seyvoue I believe your issue is different from the OP (Laravel homestead is ubuntu based) and more similar to the one I created: #374

Possibly related: https://github.com/dotless-de/vagrant-vbguest/pull/373

I'm having the exactly same issue on Virtualbox 6.1.6 trying to spin up a centos/7 guest box.

Finally, after many and many problems (ISO uploads randomly fails, Windows DLLs not recognized as signed by Vagrant, etc etc), I fixed the problem which seems to have been caused by a recent Windows upgrade (to a Insiders version).
So I don't reproduce any of the problem I encountered before this issue 👍


Better handle nil response status in client

I've seen responses have a nil status when we're experiencing availability issues, so this prevents an "undefined method `>=' for nil" exception.

thanks


Use SimpleDropdown to reduce code duplication

Description

Reduces code duplication.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] Code quality improvements

Checklist

[x] I have tested this code
[ ] I have updated the documentation

@RichDom2185 I see this PR is stalled for quite a while already, so I have gone ahead and did some simple analysis & investigation for the problem.
The issue was related to how React tracks state and props, especially in the useState hook, as the initial value of useState is only considered during component mount, but otherwise discard in component re-render. Thus, this brings us to the question, does SimpleDropdown really needs to maintain its own state over the selected value?
If we look again at what state it is handling (selectedValue), we can see that it is not really needed, as any changes in selectedValue (that is triggered by the clicking of the inner MenuItem component) will be propagated upwards through the onClick event, which will eventually cause an update in the lang value (or any value that is tied to the current defaultValue prop on SimpleDropdown). Here is something worth reading that goes into more detail for useState and props. Therefore, I suggest doing away with its own internal state for the SimpleDropdown wrapper, and to rename defaultValue to selectedValue for better representation of its functionality.
This will not affect how the dropdown works, as this is handled and managed by the inner Popover2 component instead, which holds and controls its own state (to render or not render the dropdown) which is unrelated to the scope of the SimpleDropdown wrapper.
As a side issue, the MenuItem component rendered within SimpleDropdown also does not have a key property, which did exist previously and is good practice to have one when dealing with multiple same component children.
I will be pushing and updating these changes accordingly, and this completes the refactor to SimpleDropdown, bringing this PR out of the (stalled) draft state. I have also updated the relevant files that currently uses SimpleDropdown (which is Grading.tsx), could you kindly help me check and verify that there are no regressions introduced caused by the change in the implementation of SimpleDropdown?
As for the tests I'm not sure if my changes are the best way to go with, so do let me know your comments if you have any.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 37.325%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
5717

Relevant Lines:
14393

💛  - Coveralls

Looks good! I've also tested Grading.tsx locally and there seem to not be any regressions.

Thanks! Alright, I'll wait for a 3rd person opinion on this (since I authored a significant portion of the code), and I think it should be auto-merged once approved with no outstanding issues.


Fix Report Link

Please fix the report link, since it leads to the URL Protection report incorrectly.
"Go to Threat protection status report at https://security.microsoft.com/reports/URLProtectionActionReport and filter by View data by Email > Spam."
Suggesting:
"In the Threat protection status report, select View data by Email > Spam. To go directly to the report, open one of the following URLs:
Defender for Office 365: https://security.microsoft.com/reports/TPSAggregateReportATP
EOP: https://security.microsoft.com/reports/TPSAggregateReport"
(Source: https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/view-email-security-reports?view=o365-worldwide#threat-protection-status-report)

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

ID: 5942c743-89c5-43c8-330a-dafbbb2dde37
Version Independent ID: 025fd91b-9ddf-fc72-16e4-2f19ab860ed7
Content: What's the difference between junk email and bulk email? - Office 365
Content Source: microsoft-365/security/office-365-security/what-s-the-difference-between-junk-email-and-bulk-email.md
Product: m365-security
Technology: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

@hudish, fixed.
In the future, you too can make changes like this directly. No need to open an Issue first. Instructions are here.
Thanks for the feedback.
Closing


Docker Hub Issues

Hi, I was trying to pull the docker image of "oracle/database-enterprise:<IP_ADDRESS>" from Docker Hub but seems the pages are deprecated.
https://hub.docker.com/_/oracle-database-enterprise-edition
and the publisher page is deprecated too.
Is it all oracle docker images will only publish to https://container-registry.oracle.com/ from now on?

Yes


Formatting bug when using Week of Year in template

For context, I am trying to add a link from daily notes back to the corresponding weekly note.
Observed behavior:
[[{{date:gggg}}
-W{{date:ww}}]]

[[{{date:gggg}}-W{{date:ww}}]]

Renders as
[[2021
-W14]]

[[2021}}-13{{3amt3:14]]

Desired behavior
[[{{date:gggg}}-W{{date:ww}}]]

should render as
[[2021-W14]]

Another example as I was trying to simplify the test case:
{{date:YYYY-MM}} {{date:YYYY-MM}}

2021-03}} {{3amt3:2021-03

So it's something about two date templates on the same line, maybe?

Hi @muness, thanks for the report. Looks like it's a regression I introduced with the latest version. I can reproduce the issue and will have a fix shortly.

This should be fixed in the new version 0.0.13. Let me know if you're still having issues.

Also, unrelated, but instead of [[{{date:gggg}}-W{{date:ww}}]], you can just do [[{{date:gggg-[W]ww}}]] for something a bit simpler 😄

@liamcain thanks for the quick fix!
believe me, it started with the [[{{date:gggg-[W]ww}}]] and got increasingly more complicated as I was trying to figure out what I was doing wrong and then realizing there was probably a regression to report. Went back to it after updating and it's working as expected again. Yay!


ERROR: error code -6 (No module named digits_python_layers)

Hello  all , I have reinstall my caffe with newest version: 1.0.0-rc4 with cuda 8.0, cudnn 5.0.5 by following steps:
cat $CAFFE_ROOT/python/requirements.txt | xargs -n1 sudo pip install
cd $CAFFE_ROOT
mkdir build
cd build
cmake ..
make --jobs=4

I can run simple LeNet code.
DIGITS version:
5.1-dev
Caffe version:
1.0.0-rc4
Caffe flavor:
BVLC

However, when I used dice.py layer in  example. I got the error
ERROR: error code -6

Memory required for data: 496687996
Creating layer dice

This is terminal log
20170214-115244-80a5/solver.prototxt --gpu=0 --weights=/home/xxx/fcn/voc-fcn16s/fcn16s-heavy-pascal.caffemodel"
I0214 14:37:35.349880  3810 net.cpp:139] Memory required for data: 40976020
I0214 14:37:35.349885  3810 layer_factory.hpp:77] Creating layer dice
ImportError: No module named digits_python_layers

I sure it is from python layer (because I remove dice layer in prototxt and it worked) How should I fix it? Thanks.

Fixed it by using command at the fist time
CAFFE_ROOT=/home/xxx/caffe ./digits-devserver --port 5000


There are no any integration test can be passed on MacOS 11

Because it found the wrong path.
excepted: .../go-server/dist...
actually:   .../go-server/tests/dist...
Running integration test for application go-server
2020/12/05 17:39:00 [InitLog] warn: ioutil.ReadFile(file:dist/darwin_amd64/release/conf/log.yml) = error:open dist/darwin_amd64/release/conf/log.yml: no such file or directory
2020/12/05 17:39:00 [consumerInit] unmarshalYmlConfig error ioutil.ReadFile(file:dist/darwin_amd64/release/conf/client.yml) = error:open dist/darwin_amd64/release/conf/client.yml: no such file or directory
I will fix it.

You should run make follow the README.md in dubbo-go-samples.
It points out run make in helloworld/go-server not helloworld/go-server/tests or run follow script in root dir
./integrate_test.sh helloworld/go-server

You should run make follow the README.md in dubbo-go-samples.
It points out run make in helloworld/go-server not helloworld/go-server/tests or run follow script in root dir
./integrate_test.sh helloworld/go-server

I try to run it follow and get a err
cd helloworld/go-server
make -f ../../build/Makefile integration

You should run make follow the README.md in dubbo-go-samples.
It points out run make in helloworld/go-server not helloworld/go-server/tests or run follow script in root dir
./integrate_test.sh helloworld/go-server

I try to run it follow readMe and get a err
cd helloworld/go-server
make -f ../../build/Makefile integration

You should run make -f ../../build/Makefile docker-up for start zookeeper and make -f ../../build/Makefile start for start provider before make -f ../../build/Makefile integration.Can not  just run make -f ../../build/Makefile integration
If you have not docker , you should install a zookeeper server for  integration.

You should run make follow the README.md in dubbo-go-samples.
It points out run make in helloworld/go-server not helloworld/go-server/tests or run follow script in root dir
./integrate_test.sh helloworld/go-server

I try to run it follow readMe and get a err
cd helloworld/go-server
make -f ../../build/Makefile integration

You should run make -f ../../build/Makefile docker-up for start zookeeper and make -f ../../build/Makefile start for start provider before make -f ../../build/Makefile integration.Can not just run make -f ../../build/Makefile integration
If you have not docker , you should install a zookeeper server for integration.

yep, i start zookeeper  and go-server, then integration test and got a err

/dist in helloworld/go-server
and tests try to find /dist in helloworld/go-server/tests

/dist in helloworld/go-server
and tests try to find /dist in helloworld/go-server/tests

ok,you are right


Mesh & Point Cloud htype's docs

🚀 🚀 Pull Request
Checklist:

[ ]  My code follows the style guidelines of this project and the Contributing document
[ ]  I have commented my code, particularly in hard-to-understand areas
[ ]  I have kept the coverage-rate up
[ ]  I have performed a self-review of my own code and resolved any problems
[ ]  I have checked to ensure there aren't any other open Pull Requests for the same change
[ ]  I have described and made corresponding changes to the relevant documentation
[ ]  New and existing unit tests pass locally with my changes

Changes
Added docs for mesh and point_cloud types

@adolkhan please increase cod coverage and this is good to go


Cannot convert undefined or null to object from $allErrors when correcting a field that got an error

Description
When using $allErrors in accordance to the documentation https://superforms.vercel.app/concepts/error-handling#listing-errors in the latest release (0.8.1) I get the following error "Uncaught (in promise) TypeError: Cannot convert undefined or null to object".
If I remove $allErrors it works properly, and also the $errors store works properly.

Thank you for making such a great library!

Hello, thank you for reporting, allErrors is probably not taking the new realtime behavior into account. I'll make some tests and will be back.

@ciscoheat Just tested it and it works! Thanks for the quick turnaround


Feature/label persist

Description
Adds an array of projects to labels for label persistence.
Adds a boolean on status for toggling visibility
FrontEnd PR: https://github.com/Lambda-School-Labs/mission-control-fe/pull/265
Fixes # (issue)
Type of change
schema and mutation change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)

Change Status

[ ] Complete, tested, ready to review and merge

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

 Label drop down selection persist

Errors fixed, nice job!


[Cherry-pick to 4.15] Update generators to 4.15.2 (#6178)

Fixes #minor

Pull Request Test Coverage Report for Build 291877

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 78.682%

Totals

Change from base Build 291374:
0.02%

Covered Lines:
24866

Relevant Lines:
31603

💛  - Coveralls


Use AWS_REGION, not AWS_DEFAULT_REGION.

It's what the Ruby SDK seems to expect. :)

ref: http://docs.aws.amazon.com/sdkforruby/api/index.html
LGTM :+1: Thanks :exclamation:

:+1: thanks for terraforming, which is amazing! I'll try to help add stuff.


can we add token label to the number of tokens you have ?

can we add a label on the top of tokens because at the first time it felt confusing i thought I have a running vm when the number increased from 0 to 1

verified


Switched Base URL Prepend Filter to Relative URL Filter

(Hopefully) fixes #244

Thank you for working on this, @loganfranken!  Fingers crossed!

Yes it did!!! Yippee!


Number of unique contracts

Currently we should number of accounts with contracts and show how many are active.
Given we highly frequently leverage the factory pattern, where the same contract is deployed on many accounts (like staking pools, lockup, multisigs, etc).
This doesn't allow to understand how many unique contracts does NEAR have.
We can just count dedupped on contract hash to show number of unique contracts on-chain.
This is especially interesting to compare between testnet and mainnet, seeing how much development gets converted into mainnet.

We can use the DEPLOY_CONTRACT action to get the contract binary hash:
SELECT * FROM action_receipt_actions WHERE action_kind = 'DEPLOY_CONTRACT' LIMIT 1;

There are currently 4868 unique DEPLOY_CONTRACT actions on testnet, and 117 on mainnet (over the whole history):
SELECT COUNT(DISTINCT args->>'code_sha256') FROM action_receipt_actions WHERE action_kind = 'DEPLOY_CONTRACT';

If we want to have it in a chart over time, we need to use something like this (pseudocode):
SELECT
    day,
    (SELECT COUNT(DISTINCT args->>'code_sha256')
       FROM action_receipt_actions
       WHERE  receipts.included_in_block_timestamp <= g.day
    ) AS dist_contract_deploys
FROM  (SELECT generate_series('2021-01-01'::date, '2021-01-06'::date, '1d')::date) AS g(day))

Basically, we will need to compute the unique value for each date. Alternatively, we may consider to pull all the DEPLOY_CONTRACT actions and compute the computation on Explorer backend side keeping the uniqueness accounting rolling.

We can pull all the DEPLOY_CONTRACT events and aggregate them (iterate) on the Explorer backend (and cache it):
SELECT * FROM action_receipt_actions WHERE action_kind = 'DEPLOY_CONTRACT' ORDER BY included_in_block_timestamp;

from my understanding, for this unique contracts, we should separate it into two parts:

display daily unique deployed contracts amount (even though the contract can be deployed previously, at that day, it is unique deployed)
A list of unique contracts that on-chain for near( this definitely should be on a separate page /contracts, we can display the list totally there for now and then ask for design)
@frol @ilblackdragon

need help with Corwin if we display for the list of unique contract. @frol @corwinharrell


Fix RG16F typo

Noticed an RG16F texture wasn't displaying correctly, and tracked it down to this typo in the format table.

This is not typo.
See how it's handled for GLES3: https://github.com/bkaradzic/bgfx/blob/7559cb20bf5db7da057eb5dd87e98a048fed0f1d/src/renderer_gl.cpp#L2491
On which GL version/platform you have this issue?

Linux: OpenGL 3.1 (NVIDIA 450.102.04), and Mac: OpenGL 2.1.

Does it fail to create texture? Or content of texture is completely wrong?

It successfully creates the texture, and that format is flagged as supported, but the contents are wrong because the data has been interpreted as GL_FLOAT instead of GL_HALF_FLOAT. (I see garbage starting halfway down the texture as you might expect.)
There doesn't seem to be anything in the OpenGL path that updates that value, similar to the GLES code you referenced above. When the glTexImage2D() call is hit, the source data _type passed is GL_FLOAT.
Also, the R16F and RGBA16F formats both use GL_HALF_FLOAT in that table. (And work okay.) I think this is why I assumed it was a typo.

Also, the R16F and RGBA16F formats both use GL_HALF_FLOAT in that table. (And work okay.) I think this is why I assumed it was a typo.

Yeah, I forgot exactly why it's done this way. Since you tested it, I'll accept PR, and then see if anyone else complains. :)

Heh. GL/GLES texture formats over all the different platform and driver paths are mental, so anything's possible :). But it works okay here, across 2x platforms, 3x GL versions, and our headless Linux GLES path.


How to run in --net=host mode?

I have followed the quick start in the readme file, everything worked perfectly, I was able to connect a client to the server.
However, for my need, I need to run in host networking mode, which I have been trying to do for the last 2 days unsuccessfully.
These are the commands I ran on a default 5$ Digital Ocean droplet (with all ports open):
OVPN_DATA="ovpn-data-example"
docker volume create --name $OVPN_DATA
docker run -v $OVPN_DATA:/etc/openvpn --rm kylemanna/openvpn ovpn_genconfig -N -u udp://digitalocean-public-IP(eth1 IP)
docker run -v $OVPN_DATA:/etc/openvpn --rm -it kylemanna/openvpn ovpn_initpki
docker run -v $OVPN_DATA:/etc/openvpn --rm -it kylemanna/openvpn easyrsa build-client-full CLIENTNAME nopass
docker run -v $OVPN_DATA:/etc/openvpn --rm kylemanna/openvpn ovpn_getclient CLIENTNAME > CLIENTNAME.ovpn

Finally:
root@host:~/test# docker run -v $OVPN_DATA:/etc/openvpn --net=host --cap-add=NET_ADMIN kylemanna/openvpn
Checking IPv6 Forwarding
Sysctl error for default forwarding, please run docker with '--sysctl net.ipv6.conf.default.forwarding=1'
Sysctl error for all forwarding, please run docker with '--sysctl net.ipv6.conf.all.forwarding=1'
Running 'openvpn --config /etc/openvpn/openvpn.conf --client-config-dir /etc/openvpn/ccd --crl-verify /etc/openvpn/crl.pem '
Sat Nov 27 00:40:24 2021 OpenVPN 2.4.9 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Apr 20 2020
Sat Nov 27 00:40:24 2021 library versions: OpenSSL 1.1.1g  21 Apr 2020, LZO 2.10
Sat Nov 27 00:40:24 2021 Diffie-Hellman initialized with 2048 bit key
Sat Nov 27 00:40:24 2021 CRL: loaded 1 CRLs from file /etc/openvpn/crl.pem
Sat Nov 27 00:40:24 2021 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Nov 27 00:40:24 2021 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Nov 27 00:40:24 2021 ROUTE_GATEWAY PUBLIC-IP/<IP_ADDRESS> IFACE=eth0 HWADDR=6e:2d:3f:71:f5:7d
Sat Nov 27 00:40:24 2021 TUN/TAP device tun0 opened
Sat Nov 27 00:40:24 2021 TUN/TAP TX queue length set to 100
Sat Nov 27 00:40:24 2021 /sbin/ip link set dev tun0 up mtu 1500
Sat Nov 27 00:40:24 2021 /sbin/ip addr add dev tun0 local <IP_ADDRESS> peer <IP_ADDRESS>
Sat Nov 27 00:40:24 2021 /sbin/ip route add <IP_ADDRESS>/24 via <IP_ADDRESS>
Sat Nov 27 00:40:24 2021 /sbin/ip route add <IP_ADDRESS>/24 via <IP_ADDRESS>
Sat Nov 27 00:40:24 2021 Could not determine IPv4/IPv6 protocol. Using AF_INET
Sat Nov 27 00:40:24 2021 Socket Buffers: R=[212992->212992] S=[212992->212992]
Sat Nov 27 00:40:24 2021 UDPv4 link local (bound): [AF_INET][undef]:1194
Sat Nov 27 00:40:24 2021 UDPv4 link remote: [AF_UNSPEC]
Sat Nov 27 00:40:24 2021 GID set to nogroup
Sat Nov 27 00:40:24 2021 UID set to nobody
Sat Nov 27 00:40:24 2021 MULTI: multi_init called, r=256 v=256
Sat Nov 27 00:40:24 2021 IFCONFIG POOL: base=<IP_ADDRESS> size=62, ipv6=0
Sat Nov 27 00:40:24 2021 Initialization Sequence Completed

Then on the client I am running:
root@ubuntu:/etc/openvpn# openvpn --config /etc/openvpn/CLIENTNAME.ovpn
Sat Nov 27 00:41:43 2021 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 19 2021
Sat Nov 27 00:41:43 2021 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO 2.10
Sat Nov 27 00:41:43 2021 TCP/UDP: Preserving recently used remote address: [AF_INET]PUBLIC-IP:1194
Sat Nov 27 00:41:43 2021 UDP link local: (not bound)
Sat Nov 27 00:41:43 2021 UDP link remote: [AF_INET]PUBLIC-IP:1194

At this point nothing happens, I am not getting any response from either end, and the client gives up after 60 seconds.
Any idea what is wrong?

--net=host模式时，确实无法访问其他机器，最终使用普通模式实现（虽然多了一次nat）


Update key-figures-finland

Updated the filename and ids

This looks good now and it's ready for Adam's review.
Would you like to format it with Black?  If not we can do that after it's merged.
Thanks!

I just formatted it with Black.

@Coding-with-Adam
Maybe this could work...
json.loads(json.dumps(requests.get(url).text))

@Coding-with-Adam
Could you please change the reading csv part to have encoding to utf-8? If it's not the same encoding, some regions will not be rendered on the map.
df = pd.read_csv('https://raw.githubusercontent.com/plotly/datasets/master/Dash-Examle-Index/key_figures_regions.csv', encoding="utf-8").rename(columns={"Region 2021": "Region"}).set_index("Region")

, encoding="utf-8").rename(columns={"Region 2021": "Region"}).set_index("Region")

Done. Sorry I missed that.
@tuopouk
I also tweaked the line of code that originally replaced the comma with a space. This was a suggestion by Ann that I agreed with.
Let me know if you like the final code/result. And I will merge the app.

@Coding-with-Adam
Looks great and the regions render correctly as well as their names. It's actually better to have comma as a separator. It would be different if the app was non-English. I guess you can merge from my part. Thanks!

Thanks for adding that file back, @tuopouk


error readCreateProcess: cabal-helper-wrapper "print-build-platform" (exit 1): failed

I'm using:

Ubuntu 18.04.2 LTS (under Windows WSL)
NVIM v0.4.0-811-gca1ce5902
LanguageClient-neovim 41c948e (2019-05-08 21:17:55)
haskell-ide-engine 33d4581f (2019-05-18 21:37:50)

My workaround:
export PATH="$PATH:$(stack path --compiler-bin)"

The problem of my workaround:
When I'm working on single files outside of any project, hie cannot find modules correctly.
Another workaround I have tried:
Add following file into PATH dir, name it ghc and chmod +x ghc
#!/bin/sh
stack exec -- ghc "$@"

But this workaround failed, seems that cabal-helper-wrapper is not finding ghc in PATH.
Here is a related issue: https://github.com/alanz/vscode-hie-server/issues/128

Hie does not work if the cabal file is missing, iirc.

The error message could be better. User errors should never look like crashes.

That feature request should be a separate issue.

Can we close the issue as invalid?

Not supported out of the box.
Can be worked around now with a custom cradle, e.g. direct cradle where you specify all the ghc options.


Expand Available Aggregate Methods for Table Columns

Functionality currently exists to allow a table column to utilize the Laravel method withCounts. This PR expands that functionality to allow the use of the Laravel Methods withMin, withMax, withAvg, withSum, and withExists.

Very nice, we'll probably want to add some docs for this :) Expanding the existing ones for counts()

Updated docs were part of this PR - unless I did it wrong?

Apologies - I saw them yesterday and collapsed that file in the GitHub UI. Thanks!


Add log rotation. Fix #132.

Fixes #132 with gzipped rotation for logs of 10MB in size.

With this, a 44M log dropped to 3.2M.


<EMAIL_ADDRESS>

Release: https://github.com/ERGO-Code/HiGHS/tree/v1.7.0
Used by:

https://github.com/google/or-tools

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (highs) have been updated in this PR. Please review the changes.

Maybe some targets are missing -lpthread linkopts?


Fire crashes when attempting to kill Chrome on a locked down system

Expected Behavior
It should close Chrome without any issues, or should just display an error.
Current Behavior
It kills some Chrome processes, but then crashes.
Steps to Reproduce (for bugs)

Open Chrome
(Optional, but may be required) Close and reopen Chrome.

Check if Fire has crashed.

Context
Trying to kill the process tree causes a crash, as such I can't close Chrome using Fire.
Your Environment

Version used: <IP_ADDRESS>
Operating System and version: Windows 10 FCU (locked down, no task manager, etc.)

Can you run a command through the Powershell or Command Prompt?


Datasets not available

Hi, I am not able to find the datasets online. Could you upload it for download?
Thank you!

Hi, you can download the dataset by joining the Pixel SkelNetOn challenge: https://competitions.codalab.org/competitions/21169#learn_the_details


Can I check write-only access to photo library  permission in iOS11?

First, thanks to provide this perfect plugin.
While i develop in my work, i have a request to check 'NSPhotoLibraryAddUsageDescription' which is support in iOS 11, but i found there is only "photos" in permissions which is full control, not just write access.  Is there any way to check this permission by plugin?
more Information:https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW1

thanks!

It is whichever that you have in there I believe. So the docs say that in iOS 10 + you need to put one of them... but in 11+ they introduced Add. so my assumption is that if you want Add only then you app can only support 11+ and you can only have that permission in there.
I just call apple's request code:  PHPhotoLibrary.RequestAuthorization

I see, I will try and research that you mentioned. Thanks for your replay!