logos-co
/
roadmap
mirror of https://github.com/logos-co/roadmap.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update documentation

This commit is contained in:
Jenkins 2023-10-02 13:03:01 +00:00
parent deeb07a54a
commit 8cf1dc63aa
3 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
static/contentIndex.json
View File

File diff suppressed because one or more lines are too long

2
waku/updates/2023-09-11.html
View File

@ -4,7 +4,7 @@
<p><strong><a href="https://github.com/waku-org/pm/issues/62" class="external">1.1 Network requirements and task breakdown</a></strong> {E:1.1 Network requirements and task breakdown}</p>
<ul>
<li><em>achieved:</em> Opened first raw version of Waku Network RFC for review.</li>
<li><em>next:</em> Address any feedback on the Waku Network RFC and complete underdefined sections.</li>
<li><em>next:</em> Address any feedback on the Waku Network RFC and complete under-defined sections.</li>
</ul>
<hr/>
<h3 id="docs">Docs<a aria-hidden="true" tabindex="-1" href="#docs" class="internal"> §</a></h3>

12
waku/updates/2023-09-18.html
View File

@ -48,7 +48,10 @@
<p><strong><a href="https://github.com/waku-org/nwaku/issues/1883" class="external">chore: do not advertise multiaddr with port 0</a></strong> {bug}</p>
<ul>
<li><em>achieved</em>: tested two different solutions: updating the port with an addressMapper, and not allowing the user to use port 0. Analyzed and discussed technical implications of both solutions. Initially followed decision to proceed with 2nd solution for now, with intention of implementing the first solution in the future.
Opened a draft PR and updated tests for the solution of not allowing the user to choose port 0.</li>
<ul>
<li>Opened a draft PR and updated tests for the solution of not allowing the user to choose port 0.</li>
</ul>
</li>
<li><em>next</em>: after further feedback received today, we have to complete the discussion of how to move forward and either review and proceed with current PR, or plan and implement solution that updates all the data structures consistently across the node</li>
</ul>
<p><strong><a href="https://github.com/waku-org/nwaku/issues/1872" class="external">feat: HTTP REST API: Filter support v2</a></strong> {E:REST API service node}</p>
@ -59,8 +62,11 @@ Opened a draft PR and updated tests for the solution of not allowing the user to
<p><strong><a href="https://github.com/waku-org/nwaku/issues/1576" class="external">chore: update resolved enr ip when using <code>dns4-domain-name</code> flag</a></strong> {enhancement}</p>
<ul>
<li><em>achieved</em>: implemented solution that does DNS IP resolution during node bringup when no external IP is found but a DNS address is provided.
Validated and tested “happy paths” of the solution, raised draft PR and got feedback about the solution
-<em>next</em>: discuss and define the system’s behavior on errors, implement error handling and adding tests for this feature.</li>
<ul>
<li>Validated and tested “happy paths” of the solution, raised draft PR and got feedback about the solution</li>
</ul>
</li>
<li><em>next</em>: discuss and define the system’s behavior on errors, implement error handling and adding tests for this feature.</li>
</ul>
<hr/>
<h3 id="js-waku">js-waku<a aria-hidden="true" tabindex="-1" href="#js-waku" class="internal"> §</a></h3>