issue-tracking issueshttps://gitlab.distantaccess.com/f-interop-contributors/issue-tracking/-/issues2018-03-25T15:58:01Zhttps://gitlab.distantaccess.com/f-interop-contributors/issue-tracking/-/issues/7some small GUI visualization modifs2018-03-25T15:58:01ZFederico Sismondifsismondi@mandint.orgsome small GUI visualization modifshello @pgaudet @lbaron
I have some rather small changes recommendations to improve the visualization part ()
1) the "Session action" and "Session options" take too much space, can reduce the size of those two boxes so messages that go...hello @pgaudet @lbaron
I have some rather small changes recommendations to improve the visualization part ()
1) the "Session action" and "Session options" take too much space, can reduce the size of those two boxes so messages that go into the "Pending action" box dont get cut? (see image attached).
I would re-size the boxes to:
- Timeline -> 25% of the width
- Pending action -> 50% of the width
- Session options + Session action -> 25% of the width
![Screen_Shot_2018-03-25_at_17.42.23](/uploads/9c6fe460f4327be8a9c6951bccce3488/Screen_Shot_2018-03-25_at_17.42.23.png)
2) Session action -> Session management (some terms dont overlap with the "Pending action"), else we could change "Session action" to "Pending test actions"
3) the websocket health box, whenever the websocket "brakes", it goes from green to red, but it doesnt really captures the attention of the user (at least in my case it hasn't).
Do you think you can make the red box blink? or change something that makes that look more like an alarm..
thanks :DPauline Gaudet-ChardonnetPauline Gaudet-Chardonnethttps://gitlab.distantaccess.com/f-interop-contributors/issue-tracking/-/issues/6No response from analyser with broadcast frames2018-03-17T16:06:40ZConstant DAIXNo response from analyser with broadcast framesWhen executing the test that need to send a broadcast frame from one EUT the test stops at the "Step (verify) EXECUTED".
Nothing happen after this message and refresh does nothing.
You can see in the history the session : c9b23463-9c57-...When executing the test that need to send a broadcast frame from one EUT the test stops at the "Step (verify) EXECUTED".
Nothing happen after this message and refresh does nothing.
You can see in the history the session : c9b23463-9c57-4fc8-8b00-ad3005eb0487Federico Sismondifsismondi@mandint.orgFederico Sismondifsismondi@mandint.orghttps://gitlab.distantaccess.com/f-interop-contributors/issue-tracking/-/issues/4GUI lags a lot after the 500 messages received (the whole thing becomes very ...2018-03-19T14:24:59ZFederico Sismondifsismondi@mandint.orgGUI lags a lot after the 500 messages received (the whole thing becomes very irresponsive)So with the following snippet I managed to reproduce the lagging issue @cdaix talks about.
Create file with snippet, create a dummy session, export AMQP_URL, the run `python3 nameOfTheSnippteFile.py'
```
from urllib.parse import urlp...So with the following snippet I managed to reproduce the lagging issue @cdaix talks about.
Create file with snippet, create a dummy session, export AMQP_URL, the run `python3 nameOfTheSnippteFile.py'
```
from urllib.parse import urlparse
import os
import json
import pika
import threading
from event_bus_utils import publish_message, amqp_request
from messages import *
try:
AMQP_EXCHANGE = str(os.environ['AMQP_EXCHANGE'])
except KeyError as e:
AMQP_EXCHANGE = "amq.topic"
AMQP_URL = str(os.environ['AMQP_URL'])
print('Env vars for AMQP connection succesfully imported')
connection = pika.BlockingConnection(pika.URLParameters(AMQP_URL))
class MessageGenerator(threading.Thread):
"""
blindly' publishes messages in list until it's empty
"""
keepOnRunning = True
def __init__(self, amqp_url, amqp_exchange, messages_list, wait_time_between_pubs=2.0):
threading.Thread.__init__(self)
self.messages = messages_list
self.wait_time_between_pubs = wait_time_between_pubs
self.connection = pika.BlockingConnection(pika.URLParameters(amqp_url))
self.channel = self.connection.channel()
logging.info("[%s] AMQP connection established" % (self.__class__.__name__))
def run(self):
logging.info("[%s] lets start 'blindly' generating the messages which take part on a coap session "
"(for a coap client)" % (self.__class__.__name__))
try:
while self.keepOnRunning:
time.sleep(self.wait_time_between_pubs)
m = self.messages.pop(0)
publish_message(self.connection, m)
logging.info("[%s] Publishing in the bus: %s" % (self.__class__.__name__, repr(m)))
except IndexError:
# list finished, lets wait so all messages are sent and processed
time.sleep(5)
pass
except pika.exceptions.ChannelClosed:
pass
finally:
logging.info("[%s] shutting down.. " % (self.__class__.__name__))
self.connection.close()
def stop(self):
self.keepOnRunning = False
m_list1 = []
BUTTON_MSG_SEND_LEN = 101
for i in range(1, BUTTON_MSG_SEND_LEN):
m_list1.append(
MsgUiRequestQuestionRadio(
title="Do you see me? BUTTON_MSG_SEND Message number %s/%s" % (i, BUTTON_MSG_SEND_LEN-1),
tags={'BUTTON_MSG_SEND': None}
)
)
m_list2 = []
DISPLAY_MSG_SEND_LEN = 1001
for i in range(1, DISPLAY_MSG_SEND_LEN):
m_list2.append(
MsgUiDisplayMarkdownText(
title="Do you see me? DISPLAY_MSG_SEND Message number %s/%s" % (i, DISPLAY_MSG_SEND_LEN-1),
tags={'DISPLAY_MSG_SEND': None}
)
)
producer1 = MessageGenerator(
amqp_url=AMQP_URL,
amqp_exchange=AMQP_EXCHANGE,
messages_list=m_list1,
wait_time_between_pubs=2
)
producer2 = MessageGenerator(
amqp_url=AMQP_URL,
amqp_exchange=AMQP_EXCHANGE,
messages_list=m_list2,
wait_time_between_pubs=0.1
)
producer1.start()
producer2.start()
for m in m_list1:
# # display messages
# for i in range(1, 4):
# publish_message(connection, MsgUiDisplay(title="Do you see me? (PRE-request) %s" % i))
# publish_message(connection, m)
# request messsages
amqp_request(
connection=connection,
request_message=m,
component_id='bug_tester',
retries=20
)
# # display messages
# for i in range(1, 4):
# publish_message(connection, MsgUiDisplay(title="Do you see me? (POST-request) %s" % i))
time.sleep(0.5)
producer1.join()
producer2.join()
```Loic BaronLoic Baronhttps://gitlab.distantaccess.com/f-interop-contributors/issue-tracking/-/issues/3[GUI] user names creation2018-03-19T14:23:52ZFederico Sismondifsismondi@mandint.org[GUI] user names creationHello,is there a reason why we have some random chars appended at the end of the use name?
e.g.:
FEDERICO_SISMONDIOJXUHello,is there a reason why we have some random chars appended at the end of the use name?
e.g.:
FEDERICO_SISMONDIOJXULoic BaronLoic Baronhttps://gitlab.distantaccess.com/f-interop-contributors/issue-tracking/-/issues/2[GUI] buttons not displayed in GUI2018-05-02T09:20:26ZFederico Sismondifsismondi@mandint.org[GUI] buttons not displayed in GUI(im migrating from https://gitlab.f-interop.eu/f-interop/gui/issues/28 so open call contributors can comment on this one)
@lbaron @pgaudet I have been testing with some open call partners the GUI trying to reproduce the error and the la...(im migrating from https://gitlab.f-interop.eu/f-interop/gui/issues/28 so open call contributors can comment on this one)
@lbaron @pgaudet I have been testing with some open call partners the GUI trying to reproduce the error and the last thing we discovered is :
- it's not only that some buttons are not displayed in the GUI, but also sometimes a button will appear and right after that disappear (before you can click on it)
- some OS/webbrowser combinations manifest the error more often than others(win>linux>macos)
- **network conditions factor affects a lot how often the bug manifests**
e.g. if you use a VPN and connect to Germany, London, etc, the bug will appear quite often.
I have tested also with Seul(ping reaction time of >600ms) and the bus appears all the time, like one message out of two will trigger the bug.
I guess this is why I started experiencing this only once we went to the technical review in Brussles, and not before.
From INRIA I get:
```
>>> ping dev.gui.f-interop.eu
PING dev.gui.f-interop.eu (132.227.122.109): 56 data bytes
64 bytes from 132.227.122.109: icmp_seq=0 ttl=54 **time=8.783 ms**
```
Do you think you can push a quick patch for this week (sth like websockets reconnect & refresh when heartbeats are not received for more that 5 seconds) ?
Kereval is waiting for a fix for recording a video and sending it to the IETF participants for disseminating and attracting participants to the plugtest/plugfest event they are planning for