[Do not merge] Cargo lockfile V2 format.Generated using cargo generate-lockfile

[LalatenduMohanty]

rust-lang/cargo#7070

Testing if it works in our CI

Signed-off-by: Lalatendu Mohanty [email protected]

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LalatenduMohanty

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 [LalatenduMohanty]

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

[LalatenduMohanty]

I was also playing around with cargo audit and found that as the lock file is regenerated, some dependency package using recent versions and it fixed two security advisories (it was not intentional and I had plan to send a separate PR for the cargo audit fixes)

Crate:    bumpalo                                                                                                                                                                   [324/1954]
Version:  3.1.2                            
Date:     2020-03-24                  
URL:      https://rustsec.org/advisories/RUSTSEC-2020-0006                                     
Title:    Flaw in `realloc` allows reading unknown memory                                      
Solution:  upgrade to >= 3.2.1                 
Dependency tree:                                                                               
bumpalo 3.1.2                                  
└── wasm-bindgen-backend 0.2.58                                                                
    ├── wasm-bindgen-webidl 0.2.58                                                             
    │   └── web-sys 0.3.35                                                                     
    │       ├── wasm-bindgen-futures 0.4.8   
    │       │   └── reqwest 0.10.1                                                             
    │       │       ├── quay 0.0.0-dev                                                         
    │       │       │   ├── graph-builder 0.1.0                                                
    │       │       │   └── cincinnati 0.1.0                                                   
    │       │       │       ├── policy-engine 0.1.0                                            
    │       │       │       ├── graph-builder 0.1.0                                            
    │       │       │       └── e2e 0.1.0                                                      
    │       │       ├── graph-builder 0.1.0                                                    
    │       │       ├── e2e 0.1.0                                                              
    │       │       ├── dkregistry 0.4.0-alpha.0                                               
    │       │       └── cincinnati 0.1.0                                                       
    │       └── reqwest 0.10.1                                                                 
    └── wasm-bindgen-macro-support 0.2.58                                                      
        └── wasm-bindgen-macro 0.2.58                                                          
            └── wasm-bindgen 0.2.58                                                            
                ├── web-sys 0.3.35                                                             
                ├── wasm-bindgen-futures 0.4.8                                                 
                ├── reqwest 0.10.1                                                             
                └── js-sys 0.3.35             
                    ├── web-sys 0.3.35       
                    ├── wasm-bindgen-futures 0.4.8
                    └── reqwest 0.10.1

==============================================

ID:       RUSTSEC-2019-0013
Crate:    spin
Version:  0.5.1
Date:     2019-08-27
URL:      https://rustsec.org/advisories/RUSTSEC-2019-0013
Title:    Wrong memory orderings in RwLock potentially violates mutual exclusion
Solution:  upgrade to >= 0.5.2
Dependency tree: 
spin 0.5.1
└── prometheus 0.7.0

[openshift-ci-robot]

@LalatenduMohanty: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/images	fc7eb6d	link	/test images
ci/prow/yaml-lint	fc7eb6d	link	/test yaml-lint
ci/prow/cargo-test	fc7eb6d	link	/test cargo-test
ci/prow/e2e	fc7eb6d	link	/test e2e
ci/prow/rustfmt-1.44.0	fc7eb6d	link	/test rustfmt-1.44.0
ci/prow/rustfmt-1.45.0	fc7eb6d	link	/test rustfmt-1.45.0
ci/prow/rustfmt-1.43.0	fc7eb6d	link	/test rustfmt-1.43.0
ci/prow/rustfmt-1.41.0	fc7eb6d	link	/test rustfmt-1.41.0
ci/prow/rustfmt-1.40.0	fc7eb6d	link	/test rustfmt-1.40.0
ci/prow/rustfmt-1.42.0	fc7eb6d	link	/test rustfmt-1.42.0
ci/prow/rustfmt-1.46.0	fc7eb6d	link	/test rustfmt-1.46.0

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-merge-robot]

@LalatenduMohanty: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/build-only	fc7eb6d	link	/test build-only

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.