Skip to content
This repository has been archived by the owner on Jul 27, 2022. It is now read-only.

Problem: full client flow not tested with "better" mock encryption+tx-query (CRO-510) #606

Merged
merged 1 commit into from Nov 21, 2019

Conversation

tomtau
Copy link
Contributor

@tomtau tomtau commented Nov 20, 2019

Solution:

  • still WIP -- didn't turn it on yet, as it'll require modifications in integration test deployments etc.
  • there were small problems discovered in full flow testing that should be fixed in this PR:
  1. dummy signer didn't follow the cryptographic padding convention, so the estimate fee would sometimes be wrong
  2. client couldn't connect to IP addresses, as they are not valid hostnames (hostname required by the TLS library)
  3. tx-query randomly failed some requests (witness on CI as well) -- probably due to trying to parse the whole allocated buffer (rather than just the actual request length slice)

@tomtau
Copy link
Contributor Author

tomtau commented Nov 20, 2019

bors try

bors bot added a commit that referenced this pull request Nov 20, 2019
@codecov
Copy link

codecov bot commented Nov 20, 2019

Codecov Report

Merging #606 into master will increase coverage by 0.03%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##           master     #606      +/-   ##
==========================================
+ Coverage   68.54%   68.57%   +0.03%     
==========================================
  Files         124      124              
  Lines       14826    14818       -8     
==========================================
- Hits        10162    10161       -1     
+ Misses       4664     4657       -7
Impacted Files Coverage Δ
client-core/src/cipher/default.rs 0% <0%> (ø) ⬆️
client-core/src/signer/dummy_signer.rs 96.07% <100%> (-0.15%) ⬇️
chain-core/src/tx/fee/mod.rs 88.17% <0%> (+0.49%) ⬆️

@bors
Copy link
Contributor

bors bot commented Nov 20, 2019

try

Build failed

…-query (CRO-510)

Solution:
- still WIP -- didn't turn it on yet, as it'll require modifications in integration test deployments etc.
- there were small problems discovered in full flow testing that should be fixed in this PR:
1) dummy signer didn't follow the cryptographic padding convention, so the estimate fee would sometimes be wrong
2) client couldn't connect to IP addresses, as they are not valid hostnames (hostname required by the TLS library)
3) tx-query randomly failed some requests (witness on CI as well) -- probably due to trying to parse the whole allocated buffer (rather than just the actual request length slice)
@tomtau
Copy link
Contributor Author

tomtau commented Nov 21, 2019

bors retry

bors bot added a commit that referenced this pull request Nov 21, 2019
@bors
Copy link
Contributor

bors bot commented Nov 21, 2019

@tomtau
Copy link
Contributor Author

tomtau commented Nov 21, 2019

bors r+

bors bot added a commit that referenced this pull request Nov 21, 2019
606: Problem: full client flow not tested with "better" mock encryption+tx-query (CRO-510) r=tomtau a=tomtau

Solution:
- still WIP -- didn't turn it on yet, as it'll require modifications in integration test deployments etc.
- there were small problems discovered in full flow testing that should be fixed in this PR:
1) dummy signer didn't follow the cryptographic padding convention, so the estimate fee would sometimes be wrong
2) client couldn't connect to IP addresses, as they are not valid hostnames (hostname required by the TLS library)
3) tx-query randomly failed some requests (witness on CI as well) -- probably due to trying to parse the whole allocated buffer (rather than just the actual request length slice)


Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>
@bors
Copy link
Contributor

bors bot commented Nov 21, 2019

@bors bors bot merged commit c973021 into crypto-com:master Nov 21, 2019
bors bot added a commit that referenced this pull request Dec 21, 2020
2401: Bump cbindgen from 0.15.0 to 0.16.0 r=tomtau a=dependabot-preview[bot]

Bumps [cbindgen](https://github.com/eqrion/cbindgen) from 0.15.0 to 0.16.0.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/eqrion/cbindgen/blob/master/CHANGES">cbindgen's changelog</a>.</em></p>
<blockquote>
<h2>0.16.0</h2>
<pre><code> * Remove artificial restriction on lifetime parameters on enums ([#604](mozilla/cbindgen#604))
 * Add an option for converting usize/isize into size_t/ptrdiff_t. ([#606](mozilla/cbindgen#606))
 * Allow controlling the cargo profile used for expansion. ([#607](mozilla/cbindgen#607))
 * Support wider range of expressions in enum discriminants ([#614](mozilla/cbindgen#614))
 * Support generation of Cython bindings ([#590](mozilla/cbindgen#590))
 * Fixed some issues with style=tag and recursive structs ([#615](mozilla/cbindgen#615))
 * Default C style to Both (as specified in docs) ([#615](mozilla/cbindgen#615))
 * Fix resolution of path dependencies from certain modules. ([#629](mozilla/cbindgen#629))
 * Support inlined definitions for tuple variants with a single field in C ([#631](mozilla/cbindgen#631))
</code></pre>
<p>Thanks to all the awesome contributors that contributed to this release.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/eqrion/cbindgen/commit/a00b4215a907601680f6e9acaf93df1cbafa8ded"><code>a00b421</code></a> v0.16.0</li>
<li><a href="https://github.com/eqrion/cbindgen/commit/b82e37525478d7d0bddbea2baf27e2eb9434531f"><code>b82e375</code></a> enum: Support inlined definitions for tuple variants with a single field</li>
<li><a href="https://github.com/eqrion/cbindgen/commit/eaf3e57e743dba7621bfa59d0c5bf0656a79cb71"><code>eaf3e57</code></a> enum: Remove some redundant function parameters</li>
<li><a href="https://github.com/eqrion/cbindgen/commit/0083c43e13c384787023c1fc8c491744d9f41070"><code>0083c43</code></a> Remove <code>Struct::tuple_struct</code></li>
<li><a href="https://github.com/eqrion/cbindgen/commit/8a5db0baebfd45f4c43681151d111cdcb31bc6c5"><code>8a5db0b</code></a> Minor cleanup to <code>fn close_brace</code></li>
<li><a href="https://github.com/eqrion/cbindgen/commit/1963f0c92e93456359713db353aa6276f6200f7b"><code>1963f0c</code></a> Partially support <code>#[cfg]</code>s on fields</li>
<li><a href="https://github.com/eqrion/cbindgen/commit/dfcee869ba536e661a0c972b5407ea3a5579d960"><code>dfcee86</code></a> enum: Do not forget to rename entities in enum discriminants</li>
<li><a href="https://github.com/eqrion/cbindgen/commit/fbc2237b7d7b8ab250ec184c709bc5d4129fceab"><code>fbc2237</code></a> parser: Fix resolution of #[path] dependencies from certain modules.</li>
<li><a href="https://github.com/eqrion/cbindgen/commit/9f558e30f3313f2fe6fcdc172b6f86c619564414"><code>9f558e3</code></a> enum: <code>enum_name</code> -&gt; <code>tag_name</code></li>
<li><a href="https://github.com/eqrion/cbindgen/commit/8997277cb71922b028a003349c59bd87ae0afe4d"><code>8997277</code></a> enum: Break up <code>Enum::write</code> into multiple functions</li>
<li>Additional commits viewable in <a href="https://github.com/eqrion/cbindgen/compare/v0.15.0...v0.16.0">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=cbindgen&package-manager=cargo&previous-version=0.15.0&new-version=0.16.0)](https://dependabot.com/compatibility-score/?dependency-name=cbindgen&package-manager=cargo&previous-version=0.15.0&new-version=0.16.0)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)



</details>

Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants