-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.2.0 alpha #138
base: master
Are you sure you want to change the base?
0.2.0 alpha #138
Conversation
Codecov Report
@@ Coverage Diff @@
## master #138 +/- ##
==========================================
+ Coverage 68.69% 76.29% +7.60%
==========================================
Files 66 50 -16
Lines 5836 5050 -786
==========================================
- Hits 4009 3853 -156
+ Misses 1827 1197 -630
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
I have |
are you running the examples in our vagrant environment? they only work inside vagrant+docker setup because they have to assume a certain network topology with specific device names. if you are using vagrant, can you post the program output? I will take a look. |
I'm running examples in the same environment where I run 0.1 examples. Old version runs just fine. note that I modified the device name and device id according to my network. I can give you access to my testing machine if you like
…------------------ Original ------------------
From: Daniel Jin ***@***.***>
Date: Sat, Apr 10, 2021 11:38 PM
To: capsule-rs/capsule ***@***.***>
Cc: QiuJiangkun ***@***.***>, Comment ***@***.***>
Subject: Re: [capsule-rs/capsule] 0.2.0 alpha (#138)
are you running the examples in our vagrant environment? they only work inside vagrant/docker setup because they have to assume a certain network topology with specific device names. if you are using vagrant, can you post the program output? I will take a look.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
At this time, we are only going to support the but if you set the log level to |
Maybe my environment was not clean enough. After rebooting, all examples are runnable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still going through stuff and testing on baremetal, but starting through the process.
core/src/ffi/mod.rs
Outdated
} | ||
} | ||
|
||
// delete later? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@drunkirishcoder just not something we're using currently?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm honestly don't remember why I commented this, been almost a year. lol. I guess I had to do something during migrating code from v0.1
to v0.2
? I will see what happens if I delete this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed comment. it is being used. might clean up in the following work around mbuf clones.
|
||
/// Makes NonNull even easier to use with the downside that it hides the | ||
/// unsafeness of the underlying pointer access. | ||
pub(crate) struct EasyPtr<T>(NonNull<T>); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a better alternative to investigate here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably not? this is completely internal to capsule ffi. it just cuts down on how many unsafe {}
we have to sprinkle through out the code base and the use is completely limited to the ffi layer. for example, all the packet headers are held as NonNull
, not EasyPtr
. if you see any usage outside the ffi layer, call it out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will double check
core/Cargo.toml
Outdated
libc = "0.2" | ||
metrics-core = { version = "0.5", optional = true } | ||
metrics-runtime = { version = "0.13", optional = true, default-features = false } | ||
metrics = "0.14" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@drunkirishcoder should we remove for now (until we return metrics separately)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so a few minor updates to make, but think we're ready to bring this in.
Will finish running this on the baremetal linux box as well.
@drunkirishcoder also maybe do a deps update and see if we can fix the security issue related to chrono/time. |
8e818aa
to
74ab2b5
Compare
sigh getting blocked by an indirect dependency. not sure which lib is pulling it in, but will need to update the sandbox to the latest stable rust. will do it when I find time soon. |
a8a0686
to
e76ccb7
Compare
e76ccb7
to
beb33cb
Compare
bffcbb9
to
1232a4c
Compare
Description
Finally here. Long waited divorce from Tokio pre-alpha as the underlying runtime. Along the way we also wanted to re-envision how we process packets. Major breaking changes,
a couple things still missing
Type of change