libremesh/lime-app

Geek-free Web App for setup and mantainance of Libremesh nodes built on Preact

lime-app's Issues

Error on websocket non consecutives responses

Example: When the answer id = 13 arrives before the 12, the call that depended on the answer 12 never receives the information.

Test-bed

Generate a fake websocket api that mimics behavior libremesh rpc, and setup test environment.

Map: on no location found

When the node has no location, do not show the dot and put a sign saying: "set location ..."

Alignment page

Issues related to the antenna alignment page/functionality

Capturas de pantalla para traductores / Screenshots for translators

Las capturas de pantalla dan contexto a los mensajes del software cuando están en la plataforma de traducción. Aquí unas ideas de cómo organizarnos para las capturas de LiMeApp, y después avanzamos a otros repos. Ya conversamos @gmarcos87 y yo de esto, y anoto a @nicopace para que vaya viendo esta parte del proceso. Supongo que pasos 1 y 2 son tuyos @gmarcos87, y 3 y 4 míos.

1) Hacer las capturas. Algunas ya se ven en el GIF en el Readme. @gmarcos87 podrías hacer más, y/o pedir a otras que están allí que hagan. (Yo en este momento no tengo acceso a ningún router con LibreMesh, así que no puedo hacer capturas realísticas.)

2) Poner las capturas en algún lado. Una vez que estemos en TranslateWiki, las ponemos allí, pero por ahora tal vez en este repo de lime-app, o como sea que pusiste las del Readme, o en el repo lime-org, o en Nextcloud, o como quieras.

3) Aclarar cuál captura muestra cuál string/mensaje. Poner el código del idioma y el nombre del mensaje como el nombre de la captura (p.e. en-change_dcaa253a.png o es-full_path_metrics_2859608f.jpg) es una opción que me gusta. O si no hay ganas o motivo para este paso, se podría saltar.

4) Poner un enlace a la imagen en el lugar indicado en qqq.json. Para que queda algo así:
"align_11050992" :"[[File:en-align_11050992.jpg]]", # para imágenes en TranslateWiki
"align_11050992" :"[[www.archivos.net/en-align_11050992.png|Captura de pantalla]]", # para imágenes en otro lado

Ahí estaría me parece. Siguiente sería lo demás de la documentación del mensaje, como indican en TranslateWiki y en MediaWiki.

Diagnostic: Show loading

Full path metric does not display "measuring links" when you press the button.

Refresh notes content on base node change

When selecting a new base node, the Notes page displays the content from the previous base node.

Demo website doesn't work

https://libremesh.github.io/lime-app/#/

It fails because it tries to talk to a standard websocket insteaad of a secure websocket.

This is because github.io forces requests to go through https

Injecting Dependencies Into Epics

Remove window.wsAPI and use dependency injection in Redux
https://redux-observable.js.org/docs/recipes/InjectingDependenciesIntoEpics.html

Community settings

When the app shows values such as signal level, throughput or packet loss, we differentiate acceptable values from bad values graphicaly (green vs. red). This acceptable values may vary for different communities and it should be possible to establish them in a config file.

suggested: /etc/config/lime-app

config lime-app
option good_signal '-65'
option bad_signal '-82'
option good_bandwidth '5' # measured in Mbps
option bad_bandwidth '1'
option acceptable_loss '20' # percentage

Apply i18n

Apply internalization in the core interface and plugins. Is important make it easy to contribute.

Documentation on how to install it on a Node

Right now this doesn't come with the router.

How do I install a build in the router?

Change mtr by traceroute6

Node Status

Features and issues related to the landing page for the App, which is an "X-ray" (info + status) of the current node.

Networks metrics: Suggestions to the user based on what was diagnosed

Part of #17

IP Box on Rx screen

Let the IP Address box appear collapsed and be expandable.

Use the device GPS functionality

When the app is installed as an apk we should use the GPS functionality to help establish location in the Map page.

Related to #25

Review the most active node selection

The algorithm with which the most active link is obtained does not seem to coincide with what is observed or expected to be found. We were able to check it in our network, and the data obtained is wrong. In our network 'Cantor' shows 'Pablo' and should show 'Mario'

https://github.com/libremesh/lime-ui-ng/blob/master/lime-api-orange-rpc/files/usr/lib/orange/api/lime/api.lua#L363

Go back on error

Expected behavior: When the base node changes and is unsuccessful, it automatically returns to the previous node

Navigation drawer

Remove header navbar and add a navigation drawer.

Metrics page

Issues related to the Metrics page/functionality

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Handle recently broken path to the Internet

When a node looses Internet connectivity because there's problems with an intermediary node, get_path to the gateway returns a partial result like
{
"path": ["hop_1", "hop_2", "???"]
}

this is related to mtr not being able to resolve the rest of the path, which is inexistent.

LiMe app should request get_last_internet_path in this case and run metrics based on that path instead.

Part of #17

Settings: State error on change node

In Settings, if you have a node selected and you want to "activate"
it does not change. You have to choose another and change it again.

Color bar not working

Color not respond to signal changes
#31

Change name

Change name Lime to LiMe in all places

Use the device's Text To Speech functionality for antenna alignment

When the app is installed using an apk, we can make use of the Text To Speech functionality to read signal values in the alignment page.

Related to #31

Network check on background

Initial Node Status functionality

Display api/get_node_status information in the Node Status page.

Part of #27

Do I have at least one neighbor with whom I have a good signal?

Part of #17

Navigation between nodes

Simplify navigation between nodes (which can be selected by clicking on the top bar)

Map page

Issues related to the map/location functionality

• #26 Differentiate community and node location
• #30 Use the device GPS functionality
• #28 Community Settings

Show Internet connectivity in Metrics page

After running the path to the gateway metrics, check if there is Internet connectivity and show the result.

Part of #17

Diagnostic: Clear list

When clicking "measure only the gateway", update the path and delete the results of the previous test.

Differentiate community and node location

Center map but don't show pointer when node location is not set and the api returns the community location.
Part of #25

fetch last known Internet path when there is no gateway

When there is no gateway available get_gateway replies with an error. LiMe App should then request the last known Internet path. Refers to #12

Part of #17

Path traveled to the gateway

Show the path traveled to the gateway and the state of each hop.

Part of #17

Default node in Alignment

Make the most active link the default node to align.

An in-range update of preact is breaking the build 🚨

Version 8.2.2 of preact just got published.

Branch	Build failing 🚨
Dependency	preact
Current Version	8.2.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

preact is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 11 commits.

• adceb20 8.2.2
• a42390d Update rollup and modify configs accordingly (fixes #800)
• 99c856d preact/debug: Allow string refs when preact-compat is present (fixes #807)
• ec80880 Fix issue where preact/debug errored if preact-compat was not present
• 5645573 Add prepublishOnly script (#825)
• 4ea1bc7 Move donation message to scripts (#804)
• 0dea3b7 Add rugby board as an example (#821)
• 68fa510 Fix preact/debug accessing attributes that don't have toString (#754)
• 0a88752 Update import paths for #792 (#796)
• 1b2b106 Minor capitalization correction for GitHub in README (#787)
• 947d9d8 Weui for preact (#793)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Metrics page

Node and Network Diagnostic Wizard

• What packet loss and latency I have at GW
• Do I have at least one neighbor with whom I have a good signal?

An in-range update of serve is breaking the build 🚨

Version 6.4.6 of serve was just published.

Branch	Build failing 🚨
Dependency	serve
Current Version	6.4.5
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

serve is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

6.4.6

Patches

• Migrated to Yarn: 0a7e898

Commits

The new version differs by 2 commits.

• 6349e12 6.4.6
• 0a7e898 Migrated to Yarn

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Core modules and plugins

Create packages for core modules and plugis. Remove from the main repository and add as dependencies.

Changes in Metrics

Rename Metrics by Diagnostics
And add above all the name of the starting node and at the end "INTERNET"

Release v0.0.1

Release core app and plugins:

• Config
• Auth
• Align
• Locate

Status Box on Rx screen

On the Status (Rx) screen:
  - Add uptime and netperf to gw (app)
  - Return uptime in get_node_status (api)
  - Show "traffic from $ uptime"

Map: Change location

That the node functions as "a target", that is to say that it is always in the center and to move what moves is the map

Speech on round numbers

If the number ends in zero, you must say the complete number.

An in-range update of copy-webpack-plugin is breaking the build 🚨

Version 4.2.2 of copy-webpack-plugin was just published.

Branch	Build failing 🚨
Dependency	copy-webpack-plugin
Current Version	4.2.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

copy-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

Release v4.2.2

4.2.2 (2017-11-23)

Bug Fixes

• copying same file to multiple targets (#165) (43a9870)

Commits

The new version differs by 8 commits ahead by 8, behind by 2.

• 6e81e75 chore(release): 4.2.2
• 13fe3c8 refactor: use const instead var
• 19b3a17 chore(package): remove unused dependencies (fs-extra, node-dir)
• af80033 chore: drop unused deps
• 7707512 refactor: use const instead var
• dcddf86 docs: Fixes changelog issue from 4.2.1
• 7477183 chore(release): 4.2.1
• 43a9870 fix: copying same file to multiple targets (#165)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Glosary page

The app uses technical terminology which should be referenced in a glosary page that the user can browse for clarification.

Waiting for connection

"Trying to connect to $ node_name" instead of the URL of the websocket.