Skip to content

Commit 31ee9f8

Browse files
committed
fork versionize_derive
fork https://github.com/firecracker-microvm/versionize_derive.git Since our PR (firecracker-microvm/versionize_derive#23) can't be merged into upstream for a short time, here we fork it first. After the upstream is merged, switch to the upstream dependency. Signed-off-by: wllenyj <[email protected]>
1 parent 7119ec0 commit 31ee9f8

17 files changed

+1349
-0
lines changed
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# v0.1.5
2+
3+
- Ping dependency versions
4+
- Fix clippy errors and warnings
5+
- Bump rust-vmm-ci version
6+
7+
# v0.1.4
8+
9+
- Added more documentation and examples.
10+
11+
# v0.1.3
12+
13+
- Updated documentation.
14+
15+
# v0.1.2
16+
17+
- Removed union serialization support.
18+
19+
# v0.1.1
20+
21+
- Removed "versionize" dependency.
22+
- Added support for (de)serializing enum variants with zero or more fields.
23+
24+
# v0.1.0
25+
26+
- "versionize_derive" v0.1.0 first release.
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Contributing to versionize_derive
2+
3+
## Contribution Workflow
4+
5+
The versionize_derive repository uses the “fork-and-pull” development model. Follow
6+
these steps if you want to merge your changes:
7+
8+
1. Within your fork of
9+
[versionize_derive](https://github.com/firecracker-microvm/versionize_derive), create a
10+
branch for your contribution. Use a meaningful name.
11+
1. Create your contribution, meeting all
12+
[contribution quality standards](#contribution-quality-standards)
13+
1. [Create a pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/)
14+
against the master branch of the versionize_derive repository.
15+
1. Work with your reviewers to address any comments and obtain a
16+
minimum of 2 approvals, at least one of which must be provided by
17+
[a maintainer](MAINTAINERS.md).
18+
To update your pull request amend existing commits whenever applicable and
19+
then push the new changes to your pull request branch.
20+
1. Once the pull request is approved, one of the maintainers will merge it.
21+
22+
## Request for Comments
23+
24+
If you just want to receive feedback for a contribution proposal, open an “RFC”
25+
(“Request for Comments”) pull request:
26+
27+
1. On your fork of
28+
[versionize_derive](https://github.com/firecracker-microvm/versionize_derive), create a
29+
branch for the contribution you want feedback on. Use a meaningful name.
30+
1. Create your proposal based on the existing codebase.
31+
1. [Create a draft pull request](https://github.blog/2019-02-14-introducing-draft-pull-requests/)
32+
against the master branch of the versionize_derive repository.
33+
1. Discuss your proposal with the community on the pull request page (or on any
34+
other channel). Add the conclusion(s) of this discussion to the pull request
35+
page.
36+
37+
## Contribution Quality Standards
38+
39+
Most quality and style standards are enforced automatically during integration
40+
testing. Your contribution needs to meet the following standards:
41+
42+
- Separate each **logical change** into its own commit.
43+
- Each commit must pass all unit & code style tests, and the full pull request
44+
must pass all integration tests.
45+
- Unit test coverage must _increase_ the overall project code coverage.
46+
- Document all your public functions.
47+
- Add a descriptive message for each commit. Follow
48+
[commit message best practices](https://github.com/erlang/otp/wiki/writing-good-commit-messages).
49+
- Document your pull requests. Include the reasoning behind each change.
50+
- Acknowledge versionize_derive's [Apache 2.0 license](LICENSE) and certify that no
51+
part of your contribution contravenes this license by signing off on all your
52+
commits with `git -s`. Ensure that every file in your pull request has a
53+
header referring to the repository license file.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
[package]
2+
name = "versionize_derive"
3+
version = "0.1.5"
4+
license = "Apache-2.0"
5+
authors = ["Amazon Firecracker team <[email protected]>"]
6+
description = "Implements the Versionize derive proc macro."
7+
readme = "README.md"
8+
repository = "https://github.com/firecracker-microvm/versionize_derive"
9+
keywords = ["serialization", "version"]
10+
11+
[dependencies]
12+
proc-macro2 = "1.0.47"
13+
quote = "1.0.21"
14+
syn = { version = "1.0.13", features=["full", "extra-traits"]}
15+
16+
[lib]
17+
proc-macro = true
18+
19+
[badges]
20+
maintenance = { status = "experimental" }

crates/dbs-versionize-derive/LICENSE

Lines changed: 201 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,201 @@
1+
Apache License
2+
Version 2.0, January 2004
3+
http://www.apache.org/licenses/
4+
5+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6+
7+
1. Definitions.
8+
9+
"License" shall mean the terms and conditions for use, reproduction,
10+
and distribution as defined by Sections 1 through 9 of this document.
11+
12+
"Licensor" shall mean the copyright owner or entity authorized by
13+
the copyright owner that is granting the License.
14+
15+
"Legal Entity" shall mean the union of the acting entity and all
16+
other entities that control, are controlled by, or are under common
17+
control with that entity. For the purposes of this definition,
18+
"control" means (i) the power, direct or indirect, to cause the
19+
direction or management of such entity, whether by contract or
20+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
21+
outstanding shares, or (iii) beneficial ownership of such entity.
22+
23+
"You" (or "Your") shall mean an individual or Legal Entity
24+
exercising permissions granted by this License.
25+
26+
"Source" form shall mean the preferred form for making modifications,
27+
including but not limited to software source code, documentation
28+
source, and configuration files.
29+
30+
"Object" form shall mean any form resulting from mechanical
31+
transformation or translation of a Source form, including but
32+
not limited to compiled object code, generated documentation,
33+
and conversions to other media types.
34+
35+
"Work" shall mean the work of authorship, whether in Source or
36+
Object form, made available under the License, as indicated by a
37+
copyright notice that is included in or attached to the work
38+
(an example is provided in the Appendix below).
39+
40+
"Derivative Works" shall mean any work, whether in Source or Object
41+
form, that is based on (or derived from) the Work and for which the
42+
editorial revisions, annotations, elaborations, or other modifications
43+
represent, as a whole, an original work of authorship. For the purposes
44+
of this License, Derivative Works shall not include works that remain
45+
separable from, or merely link (or bind by name) to the interfaces of,
46+
the Work and Derivative Works thereof.
47+
48+
"Contribution" shall mean any work of authorship, including
49+
the original version of the Work and any modifications or additions
50+
to that Work or Derivative Works thereof, that is intentionally
51+
submitted to Licensor for inclusion in the Work by the copyright owner
52+
or by an individual or Legal Entity authorized to submit on behalf of
53+
the copyright owner. For the purposes of this definition, "submitted"
54+
means any form of electronic, verbal, or written communication sent
55+
to the Licensor or its representatives, including but not limited to
56+
communication on electronic mailing lists, source code control systems,
57+
and issue tracking systems that are managed by, or on behalf of, the
58+
Licensor for the purpose of discussing and improving the Work, but
59+
excluding communication that is conspicuously marked or otherwise
60+
designated in writing by the copyright owner as "Not a Contribution."
61+
62+
"Contributor" shall mean Licensor and any individual or Legal Entity
63+
on behalf of whom a Contribution has been received by Licensor and
64+
subsequently incorporated within the Work.
65+
66+
2. Grant of Copyright License. Subject to the terms and conditions of
67+
this License, each Contributor hereby grants to You a perpetual,
68+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69+
copyright license to reproduce, prepare Derivative Works of,
70+
publicly display, publicly perform, sublicense, and distribute the
71+
Work and such Derivative Works in Source or Object form.
72+
73+
3. Grant of Patent License. Subject to the terms and conditions of
74+
this License, each Contributor hereby grants to You a perpetual,
75+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76+
(except as stated in this section) patent license to make, have made,
77+
use, offer to sell, sell, import, and otherwise transfer the Work,
78+
where such license applies only to those patent claims licensable
79+
by such Contributor that are necessarily infringed by their
80+
Contribution(s) alone or by combination of their Contribution(s)
81+
with the Work to which such Contribution(s) was submitted. If You
82+
institute patent litigation against any entity (including a
83+
cross-claim or counterclaim in a lawsuit) alleging that the Work
84+
or a Contribution incorporated within the Work constitutes direct
85+
or contributory patent infringement, then any patent licenses
86+
granted to You under this License for that Work shall terminate
87+
as of the date such litigation is filed.
88+
89+
4. Redistribution. You may reproduce and distribute copies of the
90+
Work or Derivative Works thereof in any medium, with or without
91+
modifications, and in Source or Object form, provided that You
92+
meet the following conditions:
93+
94+
(a) You must give any other recipients of the Work or
95+
Derivative Works a copy of this License; and
96+
97+
(b) You must cause any modified files to carry prominent notices
98+
stating that You changed the files; and
99+
100+
(c) You must retain, in the Source form of any Derivative Works
101+
that You distribute, all copyright, patent, trademark, and
102+
attribution notices from the Source form of the Work,
103+
excluding those notices that do not pertain to any part of
104+
the Derivative Works; and
105+
106+
(d) If the Work includes a "NOTICE" text file as part of its
107+
distribution, then any Derivative Works that You distribute must
108+
include a readable copy of the attribution notices contained
109+
within such NOTICE file, excluding those notices that do not
110+
pertain to any part of the Derivative Works, in at least one
111+
of the following places: within a NOTICE text file distributed
112+
as part of the Derivative Works; within the Source form or
113+
documentation, if provided along with the Derivative Works; or,
114+
within a display generated by the Derivative Works, if and
115+
wherever such third-party notices normally appear. The contents
116+
of the NOTICE file are for informational purposes only and
117+
do not modify the License. You may add Your own attribution
118+
notices within Derivative Works that You distribute, alongside
119+
or as an addendum to the NOTICE text from the Work, provided
120+
that such additional attribution notices cannot be construed
121+
as modifying the License.
122+
123+
You may add Your own copyright statement to Your modifications and
124+
may provide additional or different license terms and conditions
125+
for use, reproduction, or distribution of Your modifications, or
126+
for any such Derivative Works as a whole, provided Your use,
127+
reproduction, and distribution of the Work otherwise complies with
128+
the conditions stated in this License.
129+
130+
5. Submission of Contributions. Unless You explicitly state otherwise,
131+
any Contribution intentionally submitted for inclusion in the Work
132+
by You to the Licensor shall be under the terms and conditions of
133+
this License, without any additional terms or conditions.
134+
Notwithstanding the above, nothing herein shall supersede or modify
135+
the terms of any separate license agreement you may have executed
136+
with Licensor regarding such Contributions.
137+
138+
6. Trademarks. This License does not grant permission to use the trade
139+
names, trademarks, service marks, or product names of the Licensor,
140+
except as required for reasonable and customary use in describing the
141+
origin of the Work and reproducing the content of the NOTICE file.
142+
143+
7. Disclaimer of Warranty. Unless required by applicable law or
144+
agreed to in writing, Licensor provides the Work (and each
145+
Contributor provides its Contributions) on an "AS IS" BASIS,
146+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147+
implied, including, without limitation, any warranties or conditions
148+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149+
PARTICULAR PURPOSE. You are solely responsible for determining the
150+
appropriateness of using or redistributing the Work and assume any
151+
risks associated with Your exercise of permissions under this License.
152+
153+
8. Limitation of Liability. In no event and under no legal theory,
154+
whether in tort (including negligence), contract, or otherwise,
155+
unless required by applicable law (such as deliberate and grossly
156+
negligent acts) or agreed to in writing, shall any Contributor be
157+
liable to You for damages, including any direct, indirect, special,
158+
incidental, or consequential damages of any character arising as a
159+
result of this License or out of the use or inability to use the
160+
Work (including but not limited to damages for loss of goodwill,
161+
work stoppage, computer failure or malfunction, or any and all
162+
other commercial damages or losses), even if such Contributor
163+
has been advised of the possibility of such damages.
164+
165+
9. Accepting Warranty or Additional Liability. While redistributing
166+
the Work or Derivative Works thereof, You may choose to offer,
167+
and charge a fee for, acceptance of support, warranty, indemnity,
168+
or other liability obligations and/or rights consistent with this
169+
License. However, in accepting such obligations, You may act only
170+
on Your own behalf and on Your sole responsibility, not on behalf
171+
of any other Contributor, and only if You agree to indemnify,
172+
defend, and hold each Contributor harmless for any liability
173+
incurred by, or claims asserted against, such Contributor by reason
174+
of your accepting any such warranty or additional liability.
175+
176+
END OF TERMS AND CONDITIONS
177+
178+
APPENDIX: How to apply the Apache License to your work.
179+
180+
To apply the Apache License to your work, attach the following
181+
boilerplate notice, with the fields enclosed by brackets "[]"
182+
replaced with your own identifying information. (Don't include
183+
the brackets!) The text should be enclosed in the appropriate
184+
comment syntax for the file format. We also recommend that a
185+
file or class name and description of purpose be included on the
186+
same "printed page" as the copyright notice for easier
187+
identification within third-party archives.
188+
189+
Copyright [yyyy] [name of copyright owner]
190+
191+
Licensed under the Apache License, Version 2.0 (the "License");
192+
you may not use this file except in compliance with the License.
193+
You may obtain a copy of the License at
194+
195+
http://www.apache.org/licenses/LICENSE-2.0
196+
197+
Unless required by applicable law or agreed to in writing, software
198+
distributed under the License is distributed on an "AS IS" BASIS,
199+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200+
See the License for the specific language governing permissions and
201+
limitations under the License.
Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
**Versionize is a framework for version tolerant serializion/deserialization of
2+
Rust data structures, designed for usecases that need fast deserialization
3+
times and minimal size overhead. It does not aim to be a generic serialization
4+
framework and only the [bincode](https://crates.io/crates/bincode) backend is
5+
supported.**
6+
7+
#### You may be looking for:
8+
- [Versionize documentation](https://docs.rs/versionize/)
9+
- [Releases](https://github.com/firecracker-microvm/versionize_derive/releases)
10+
11+
## Important note
12+
13+
This crate is currently used for cross-version serialization with the
14+
[Firecracker snapshot-restore dev preview][1], but has not been tested for
15+
other use cases. It should be considered **experimental software** outside the
16+
Firecracker context. It’s likely that this crate will see both interface and
17+
implementation changes in the future.
18+
19+
## Versionize in action
20+
21+
```rust
22+
extern crate versionize;
23+
extern crate versionize_derive;
24+
25+
use versionize::{VersionMap, Versionize, VersionizeResult};
26+
use versionize_derive::Versionize;
27+
28+
// The test structure is at version 3.
29+
#[derive(Debug, PartialEq, Versionize)]
30+
pub struct Test {
31+
a: u32,
32+
#[version(start = 2, end = 3)]
33+
b: u8,
34+
#[version(start = 3, default_fn = "default_c")]
35+
c: String,
36+
}
37+
38+
impl Test {
39+
// Default value for field `c`.
40+
// The callback is invoked when deserialization from and older version
41+
// where the field did not exist.
42+
fn default_c(_source_version: u16) -> String {
43+
"test_string".to_owned()
44+
}
45+
}
46+
47+
// Memory to hold the serialization output.
48+
let mut mem = vec![0u8; 512];
49+
// Create a new version map - it will start at version 1.
50+
let mut version_map = VersionMap::new();
51+
// Add new version and mark changes for Test struct: Set the current version
52+
// to point to Test struct version 2.
53+
version_map
54+
.new_version()
55+
.set_type_version(Test::type_id(), 2)
56+
.new_version()
57+
.set_type_version(Test::type_id(), 3);
58+
59+
let test_struct = Test {
60+
a: 1337,
61+
b: 0xFF,
62+
c: "c_value".to_owned(),
63+
};
64+
65+
// Serialize to version 2 - field c will not be serialized.
66+
test_struct
67+
.serialize(&mut mem.as_mut_slice(), &version_map, 2)
68+
.unwrap();
69+
70+
// Deserialize from version 2 - c should contain the default_fn() return value.
71+
let restored_test_struct = Test::deserialize(&mut mem.as_slice(), &version_map, 2).unwrap();
72+
73+
assert_eq!(
74+
restored_test_struct,
75+
Test {
76+
a: 1337,
77+
b: 255,
78+
c: "test_string".to_owned()
79+
}
80+
);
81+
```
82+
83+
[1]: https://github.com/firecracker-microvm/firecracker/tree/v0.24.0

0 commit comments

Comments
 (0)