rwth-acis/social-bot-framework

A framework to model, train and integrate social bots into technology enhanced learning applications.

social-bot-framework's Issues

Dropdown menus

Currently, the models and datasets are loaded by inputting their names in a text input field. It woul be nice if instead all stored models and datasets could be listed in a dropdown menu.

[DOC] Example Bots

1. Bot Examples - We have a lot of bots and should also provide a showcase table in our readme.
2. Location - We should describe the examples in the Readme table that is already existing.

• MensaBot
• SurveyBot @Taeuber-hub
• FeedBot
• ReaderbenchBot
• LitBot @Aran30
• LA-Bot @AlexanderNeumann
• CitBot @AlexanderNeumann

Always need to import Metamodel again when another user joins the space

The problem occurs when you are on a specific space and you already imported a metamodel to work with. Once a new user joins (by "new" I refer to users who never entered that specific space before), the default model (vls.js) will be automatically loaded as the current metamodel.

[ENH] Intent coverage

1. Motivation - If you model a large bot with lots of different intents then it is sometimes tiresome to check whether your nlu-model contains training data for each intent you used in the bot model. It would be great to have a button on the training page where you could check if your nlu training data contains all intents that your bot model has
2. Specification - This can be done entirely in the frontend. Add a function extractIntentsFromBotModel() that returns the set of intents in the bot model. Add a function extractIntentsFromNLUModel() that returns the set of intents in the nlu file. Finally add a function checkCoverage that determines the list of intents that are contained in the bot model but not the nlu model
3. Finalised state - A button is on the page that says check intent coverage. Clicking this button the user gets the coverage as % value as well as any missing intents

[ENH] Migrate to LitElement

Polymer has been deprecated. We should move to Lit as described on the official page

[BUG] Widget cannot get userinfo

1. Summary - Widgets cant get the user information from learning layers.
2. Bug Details - The response I got from the server is now:

   {error: "invalid_request", error_description: "Token not provided"}
   

   even though the access token is provided as a payload
3. How - On https://sbf-dev.tech4comp.dbis.rwth-aachen.de/modeling open the console, click the login button, sign in. The error is then shown in the logs.

Load and store status messages

Currently, when loading or storing models in the SBF frontend, the status messages will always display that the operations were successful, even though they actually weren't. This needs to be fixed to reflect the actual result of the operations.

[BUG] Error running apt-get when building using Docker

System: M1 Mac version 12.6
Building the framework using the docker command fails when running the apt-get step
docker build -t rwthacis/sbf-utils .

The solution would be to edit my repository configuration as suggested here: https://unix.stackexchange.com/questions/743839/apt-get-update-failed-to-fetch-debian-amd64-packages-while-building-dockerfile-f but there is no /etc/apt directory

[ENH] Add "delete running bot" Button

1. Motivation - The new social bot manager release https://github.com/rwth-acis/las2peer-social-bot-manager-service/releases/tag/v1.2.0 comes with a new function to delete running bots. Yet, apart from using POSTMAN (or other tools), there is currently no way to delete bots only using the frontend.
2. Specification - Add a new button to the frontend which calls the new function to delete bots (similar to the submit button).
3. Finalised state - Users are able to deactivate their bots.

[BUG] Message repeated after pressing enter

1. Summary
   Every time I press enter in an element it gets repeated
2. Bug Details
   

[BUG] `npm i` fails for utilities frontend for node version higher than 11

1. Summary - I tried installing new packages on the utilities frontend when I noticed that the install command fails.
2. Bug Details :
   1. What? - Running npm i in Utilities Frontend\app\ directory results in an error. I am using node version v14.16.1. The following log is produced:

$ npm i 

> [email protected] install C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil
> node-gyp rebuild


C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.
  bufferutil.cc
  win_delay_load_hook.cc
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(25,30): error C2039: 'Handle': is not a member of 'v8' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8-platform.h(16): message : see declaration of 'v8' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(25,36): error C2061: syntax error: identifier 'Handle' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(33,14): error C2065: 'target': undeclared identifier [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(33,1): error C2660: 'v8::FunctionTemplate::GetFunction': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(6482,46): message : see declaration of 'v8::FunctionTemplate::GetFunction' (compiling source file ..\src\bufferutil.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(49,1): error C2660: 'v8::Value::ToObject': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(2822,44): message : see declaration of 'v8::Value::ToObject' (compiling source file ..\src\bufferutil.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(56,1): error C2661: 'v8::Object::Get': no overloaded function takes 1 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(67,1): error C2660: 'v8::Value::ToObject': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(2822,44): message : see declaration of 'v8::Value::ToObject' (compiling source file ..\src\bufferutil.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(69,1): error C2660: 'v8::Value::ToObject': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(2822,44): message : see declaration of 'v8::Value::ToObject' (compiling source file ..\src\bufferutil.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(88,1): error C2660: 'v8::Value::ToObject': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(2822,44): message : see declaration of 'v8::Value::ToObject' (compiling source file ..\src\bufferutil.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(89,1): error C2660: 'v8::Value::ToObject': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(2822,44): message : see declaration of 'v8::Value::ToObject' (compiling source file ..\src\bufferutil.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(91,1): error C2660: 'v8::Value::ToObject': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(2822,44): message : see declaration of 'v8::Value::ToObject' (compiling source file ..\src\bufferutil.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(92,1): error C2660: 'v8::Value::Int32Value': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(2869,40): message : see declaration of 'v8::Value::Int32Value' (compiling source file ..\src\bufferutil.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(93,1): error C2660: 'v8::Value::Int32Value': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(2869,40): message : see declaration of 'v8::Value::Int32Value' (compiling source file ..\src\bufferutil.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(114,12): error C2065: 'Handle': undeclared identifier [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(114,19): error C2275: 'v8::Object': illegal use of this type as an expression [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(3664): message : see declaration of 'v8::Object' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(114,27): error C2065: 'target': undeclared identifier [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(114,6): error C2182: 'init': illegal use of type 'void' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(115,1): error C2448: 'init': function-style initializer appears to be a function definition [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\src\bufferutil.cc(120,1): warning C4312: 'type cast': conversion from 'int' to 'node::addon_register_func' of greater size [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil\build\bufferutil.vcxproj]
←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mbuild error←[0m 
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mstack←[0m Error: `C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe` failed with exit code: 1
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mstack←[0m     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:194:23)
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mstack←[0m     at ChildProcess.emit (events.js:315:20)
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mstack←[0m     at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mSystem←[0m Windows_NT 10.0.22000
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mcommand←[0m "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mcwd←[0m C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\bufferutil
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mnode -v←[0m v14.16.1
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mnode-gyp -v←[0m v5.1.0
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mnot ok←[0m
←[0m
> [email protected] install C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate
> node-gyp rebuild


C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.
  validation.cc
  win_delay_load_hook.cc
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(107,30): error C2039: 'Handle': is not a member of 'v8' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8-platform.h(16): message : see declaration of 'v8' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(107,36): error C2061: syntax error: identifier 'Handle' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(113,14): error C2065: 'target': undeclared identifier [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(113,1): error C2660: 'v8::FunctionTemplate::GetFunction': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(6482,46): message : see declaration of 'v8::FunctionTemplate::GetFunction' (compiling source file ..\src\validation.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(132,1): error C2660: 'v8::Value::ToObject': function does not take 0 arguments [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(2822,44): message : see declaration of 'v8::Value::ToObject' (compiling source file ..\src\validation.cc) [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(141,12): error C2065: 'Handle': undeclared identifier [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(141,19): error C2275: 'v8::Object': illegal use of this type as an expression [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Users\ben\AppData\Local\node-gyp\Cache\14.16.1\include\node\v8.h(3664): message : see declaration of 'v8::Object' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(141,27): error C2065: 'target': undeclared identifier [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(141,6): error C2182: 'init': illegal use of type 'void' [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(142,1): error C2448: 'init': function-style initializer appears to be a function definition [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\src\validation.cc(147,1): warning C4312: 'type cast': conversion from 'int' to 'node::addon_register_func' of greater size [C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate\build\validation.vcxproj]
←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mbuild error←[0m 
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mstack←[0m Error: `C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe` failed with exit code: 1
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mstack←[0m     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:194:23)
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mstack←[0m     at ChildProcess.emit (events.js:315:20)
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mstack←[0m     at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mSystem←[0m Windows_NT 10.0.22000
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mcommand←[0m "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mcwd←[0m C:\Repositories\Social-Bot-Framework\Utilities Frontend\app\node_modules\utf-8-validate
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mnode -v←[0m v14.16.1
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mnode-gyp -v←[0m v5.1.0
←[0m←[37;40mgyp←[0m ←[0m←[31;40mERR!←[0m ←[0m←[35mnot ok←[0m
←[0mnpm WARN [email protected] No repository field.
npm WARN [email protected] No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\bufferutil):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\ben\AppData\Roaming\npm-cache\_logs\2021-11-23T22_26_37_769Z-debug.log

2. Where? - In the Utilities Frontend\app\ directory
3. How?/Current state - Just call in npm i in the Utilities Frontend\app\ directory.

[BUG] Exported Meta Model is faulty

When you import a valid Meta Model file and export it again, the received file is no longer a working model file.

[ENH] Add dynamically bot answers in a single element

The sections for an enhancement issue are:

1. Motivation - Currently we have to add a new element for every single response possibility. In this example there are three answers provided.
   
   It would be better to have a single element and in the attribute widget a button to add another answer possibility or even upload a list of answers (e.g. online list of greetings) or NLG.
   This should make our bot model smaller.

2. Specification - Add a button that enables to add another response answer. (should be a list)

3. Finalised state - I can add multiple possible answers of the bot in a single element and not in multiple ones.

[BUG] "Content" fields of action parameters don't accept German umlauts (ä, ö, ...)

The "Content" field of an action parameter in the SBF (e.g. submissionSucceeded and submissionFailed) holds what the bot says after the action has been performed.
The field doesn't like umlauts. In a test, i put "Äh. Hier ist deine Auswertung." This is what the bot said:

The same happens with other umlauts.

[ENH] model notifications

Allow to model user actions that trigger Chat Responses

[BUG] Interwidget communiction failure

1. Summary - Using the new slim version of the debug widget somehow breaks communication from the canvas widget to the other widgets
2. Bug Details - :
   1. What? - I tried importing the new slim version of the debug widget, which is published under version 1.2.0. This slim version is a modification of the original version which hides the metamodel and guidance import fields from the view.
   2. Where? -This concerns version 1.2.0 of the widgets. The changes can be compared here
   3. When?/How often? - This occurs all the time. If I use the original widget again, then it works without problems
   4. How?/Current state - The canvas widget has an infinite loading spinner. The logs show the following errors:

Uncaught TypeError: Cannot read properties of undefined (reading 'payload')
    at IWC.Client.onIntentReceivedCallback [as _callback] (IWCWrapper.js:181)
    at IWC.Client.receiveMessage (iwc.js:204)

WaitForCanvas.js:30 
Property Browser:No response from canvas. Send message again.

full log
Screenshot of the page

[ENH] SBF Colors

1. Motivation - Only with the color white, it looks a little empty.

2. Specification - Add some colors.
   e.g.

[BUG] Default intent is always automatically followed by default intent

For bitbot I have defined a default intent i0 and a regular intent ir (among others).

• ir is successfully called whenever I certain things (like "upload") to bitbot.
• i0 is successfully called whenever bitbot doesn't understand what I'm saying.
  Both i0 and ir lead to the same four different new intents i1,i2,i3,i4
• after ir has been understood, bitbot can successfully understand any of i1,i2,i3,i4, depending of what I say to bitbot
• BUT: after i0 has been understood, bitbot always understands the same intent i1 next, no matter what I say
  i1 seems be the automatic default intent for this particular path. So it seems, after the bot has chosen the first default step, it automaticall choses default in the next step as well.
  I've tested this bevahior with other cases and intents and the same thing happened: default is always followed by default.

[DEV] Default values are reinserted on reload

On the dev instance the default values for Bot manager endpoint and rasa endpoint are appended every time to the existing value leading to strings like

This was observed with version 1.3.0 in the dev instance
Locally, this error could not be reproduced

[ENH] Slim version of the debug widget

1. Motivation - Slim version of the debug widget. Some options are not needed and should be changed only in one version of the frontend.
2. Specification - Either remove some items or remove the widget completely and only show necessary buttons next to the load and store button? (import/export/delete bot model). The meta-model should be connected to the SBF version. So we do not want an import meta-model function for end-users, if they are using another bot version they should stick to the corresponding SBF Frontend version.

[ENH] Navigation Bar Button Position

The sections for an enhancement issue are:

1. Motivation
   

2. Specification - A detailed list of what needs to be done in order to complete the issue.
   Add some space.

[ENH] Specify own Rocket.Chat instance

1. Motivation - Currently the framework can only handle our own Rocket.Chat instance. It should be possible to specify any Rocket.Chat instance.
2. Specification - Extend the meta-model to specify the URL of the Rocket.Chat instance.
3. Finalised state - Extended Meta Model + it should work with any Rocket.Chat instance URL.

[BUG] Null Pointer Exception on performTrigger

1. Summary - Calling SocialBotManagerService.performTrigger will lead to a NullPointer exception on SocialBotManagerService.java:1034 line
2. Bug Details
   1. What? - NullPointerException
   2. Where? - This happens on the develop branch of the Social Bot Framework. The bot is connected via Slack
   3. When?/How often? - It occurs every time a user messages the bot
   4. How?/Current state -
      I cloned the Mensa Service and created my own branch called chatbotCCA. I created a bot using the Social Bot Framework on the modeling space called mensabot. I configured a bot action which should trigger a function called getDefaultMenu on the path http://127.0.0.1:8080/mensa/default. I deployed the bot to my local instance of the Social Bot Manager Service. The bot is connected to Slack. I wrote a message to the bot, asking it for menu. The intent menuDefault is correctly recognized which should in theory trigger the mensa service funtion. However this results in a NullPointerException and the mensa service is never called.

Bot MensaBot triggered:
[]
null
default
MensaBot    pass actingAgent
botagent is b4a9aded5f657ae757c823c78ccad693d34f913d16330cb6dc1ae98a39c26a9133b54e5cafcfaedc9fb1d170a008f69861e60eedcf08d490060ff7ab3720843e
mensanull ; {"msg":"menu","botName":"b4a9aded5f657ae757c823c78ccad693d34f913d16330cb6dc1ae98a39c26a9133b54e5cafcfaedc9fb1d170a008f69861e60eedcf08d490060ff7ab3720843e","channel":"D01920S699A","intent":"menuDefault","email":null,"contextOn":true} null null My string iss:{"msg":"menu","botName":"b4a9aded5f657ae757c823c78ccad693d34f913d16330cb6dc1ae98a39c26a9133b54e5cafcfaedc9fb1d170a008f69861e60eedcf08d490060ff7ab3720843e","channel":"D01920S699A","intent":"menuDefault","email":null,"contextOn":true}
java.lang.NullPointerException
        at i5.las2peer.services.socialBotManagerService.SocialBotManagerService.performTrigger(SocialBotManagerService.java:1034)
        at i5.las2peer.services.socialBotManagerService.SocialBotManagerService.performIntentTrigger(SocialBotManagerService.java:770)
        at i5.las2peer.services.socialBotManagerService.SocialBotManagerService$BotResource$2.run(SocialBotManagerService.java:644)
        at java.lang.Thread.run(Thread.java:748)
Intent processing finished.

[ENH] Adjust height of widgets

1. Motivation - Auto-adjust the height of the widget or make them resizable. On my monitor, I have a lot of free space, but I cannot use it for modeling bots.

Restrict bot actions to channel types

1. Motivation - Sometimes a bot might need to restrict certain actions to only be available in private chat or vice versa.
2. Specification - The bot creator should be able to specify if a bot action should only be applicable in private channels.
3. Finalised state - On the canvas, when selecting the bot action element, the properties page displays a select menu. The bot creator can select the types of channel for which that bot action is allowed. He can choose between private, public, 1on1 conversation or all types. Per default all bot actions allow all types.

[ENH] Rename Intent Label to State label

Description:

We currently have an Intent Label field within the Incoming Message element. However, as this element now mainly represents a state, we propose renaming it to State Label for clarity and alignment with its actual function.

Details:

Current Implementation: The Incoming Message element contains an "Intent Label" field, originally designed to represent user intent. It now covers intent, context, and conversation state.

Reason for Renaming: "Intent Label" is misleading; renaming it to "State Label" aligns with its purpose and enhances system clarity.

Impact: This change benefits development, reducing confusion and improving user-friendliness.

Documentation Update: Update relevant documentation. Especially the fact that end users should use unique labels

[ENH] Better error handling when submitting bots

1. Motivation - If something is wrong with your model when submitting the bot, or if any other error occurs while submitting the model, you don't get any concrete explanation on what happened. The only thing the users see, is "Sending failed". Making it hard to understand what exactly went wrong, making viewing the logs neccessary...
2. Specification - Upgrade the error messages in the frontend and create more specific error explanations in the backend.
3. Finalised state - People using the frontend have a better grasp on what is wrong with their model.

Note: Changes need to take place in both frontend and backend.

Load Current Metamodel and a default Bot Model when entering new space

1. Motivation
   Every user that creates a new space currently needs the current Metamodel to import it (redundant).
   Providing an example Bot Model might help new users to understand the bot creation better.
   (The default Metamodel feature was present in an older version, but got deactivated as it resulted in another Issue )
2. Specification

• Load current Metamodel once new space is joined.
• Load example Bot Model (the one used in the evaluation) once new space is joined.

3. Finalised state
   New Users won't need to import current Metamodel themselves (redundant work) and will receive an example Bot Model when joining a space, so that they can see how a simple bot looks like.

[BUG] Loading models does not work anymore

Clicking on load does nothing. the logs show that a query selector for the value fails

[BUG] User activities not showing usernames

1. Summary -The user activity widget is not showing the usernames for the activities
2. Bug Details
   The user seems to be logged in. At least the username is showing in the las2peer status bar, but for some reason, it is not shown in the activity widget, even after manually refreshing the iframe. A 400 HTTP error is also logged in the console for getting the user info from oidc.

[ENH] Specific naming of generated Feedback pdf files (bot <> Tmitocar)

Currently students can have bitbot and FeedBot analyze uploaded texts via Tmitocar. As a result, the bot gives them a pdf file called "Feedback.pdf".

It would be nicer if the resulting pdf file was named according to the uploaded file, e.g. "MyText01.pdf" -> "Feedback-MyText01.pdf" so that they can differentiate several feedbacks later on.

[BUG] Missing attributes, when importing chat interface generated models.

All non-label attributes are not working.
Caused by attribute ids that are not matching the meta-model.

[BUG] Rateable not always available

1. Summary - The rateable option is not showing within bot modeling
2. Bug Details - When initializing a new bot model, the rateable and isFile option does not appear as attributes. This also happens, when the model is loaded from the database.

[DOC] Extend the Bot Modelling Guide

1. Subject
   A much needed documentation on how to use the bot modelling elements needs to be created. This documentation should include the idea of the elements, how they interact with each other and how one can use them to create bot models (Some bot models could also be included as examples).
2. Location
   For now, the documentation should be continued in the readme, where the new additions to the bot elements are already explained.

[ENH] More storage options and information

1. Motivation -We can only set a name and store a model as that name. The problem with this is that users forget when they have stored the model for the last time and often, I have observed that users will start calling their models: botmodel1 botmodel2 botmodel3, botmodelbackup, botmodelbackup2,... So if you want to use the latest version of a certain model you do not know which one is the latest.
2. Specification - For each model store not only the name but also metadata like the date when it was stored, a version number and the user which stored the model
3. Finalised state - If a user wants to store a model, they click on the store model button. This opens up a form in which the user is able to specify the name and an optional version tag. If they click on submit then this model is stored along with the current timestamp, the username (anonymous if not logged in) the optional version tag. If the user wants to load a model, they can use a search field. The suggestions are based on the search input and also list the version tag if available. A more info button expands the search result to reveal the username and date of submission

Management of Participants who can enter Space

1. Motivation
   As is, everyone can create new spaces and there are no real restrictions to who can enter the created space. Thus, everyone is able to see the created models or generally the space's content. There might services that can be called by the bot that might need authentication tokens as parameters, which should be kept private. If anyone has access to a Moodle wstoken, they could potentially delete course content and so on. The same goes for the model itself, anyone entering the space could delete the model or make changes to it without permission. Therefore, a way to handle who can enter your space would seem fitting.

2. Specification

• Add user management in spaces.
• Add space entering restrictions.
• Make use of the Learning Layers accounts which are already used by the activity widget.

3. Finalised state

• Users who are logged in with their Learning Layers Account can create spaces that only they can enter at first.
• The "admin" could then invite other people to their space using the Learning Layers account.

Submitting of mensabot model in SBF fails

When subitting the model of the MensaBot in the SocialBotFramework the following Error occurs:

"There is something wrong with your bot model: Exception during RMI invocation!".

Space: mensabot

[ENH] Extending the Bot Model Process to be Sequential

1. Motivation - rwth-acis/las2peer-social-bot-manager-service#208 (comment) - With how the process is structured now as a star network, a Bot Action that takes a while or fails is not able to be handled properly and the process proceeds to the next IncomingMessage regardless.
2. Specification - As mentioned by @lakhoune, Bot Actions would lead to a new IncomingMessage. Action Parameters would still be attached in a star structure.
3. Finalised state - Modeling the process in a sequential way would allow checks to be made so that if a Bot Action fails or in the case where Bot Actions are chained, if one of the Bot Actions fails, the process can be interrupted.

[ENH] Use Better Labeling Tool for Intents and Entities

1. Motivation - The usability of the current editor could be enhanced by using modern solutions like brat, doccano or INCEpTION.
   It is difficult for non computer scientists to create such annotations with the current editor.

2. Specification - You would have to change the editor and exchange it with one of the mentioned solutions or maybe another one.

3. Finalised state - It would be nice if the user can use such annotation tools and there is a translation to markdown/yaml which can be used by rasa (I would prefer yaml since it is used by the latest version of rasa)

[BUG] Imported Bot Models faulty

1. Summary - When importing some bot models which possess bot action parameters, the content of the parameter is empty even though it should not be.

2. Bug Details

   1. What? - Some attributes go missing when importing bot models. Most notably the content attribute of the bot action parameter element.
   2. Where? - Bot Modeling Frontend while using the debug widget from Syncmeta.
   3. When?/How often? - Seems pretty random. Created a new space and imported same model there and it worked. Yet on the original space, even after re-importing the metamodel and bot model, the content attribute remains empty.

   Might actually be related to syncmeta...

[ENH] Update Syncmeta dependencies

There is a dependency in Syncmeta which is limited to node version less than 11.
We should see if this dependency can be updated, removed or replaced