cisco-open / blaze Goto Github PK

Description

flask_socketio test cases giving insufficient memory

Issue Type:

• Feature Request
• Enhancement

Description:

I propose implementing a versatile file loader for Blaze that enables parsing data from various sources, including but not limited to PDFs, websites, document files, and CSVs. This enhancement would enhance Blaze's capabilities to handle diverse data sources, making it more flexible for users working with different types of data.

Use Case:

As a user of Blaze, I often encounter datasets stored in different formats such as PDFs, websites, documents, and CSV files. Having a unified file loader would streamline the data loading process, allowing users to seamlessly incorporate data from various sources into Blaze.

Proposed Solution:

I suggest implementing a modular and extensible file loader that can handle parsing from PDFs, websites, document files (e.g., Word, Excel), and CSVs. The loader should be able to intelligently detect the file type and apply the appropriate parsing logic.

Additional Information:

This enhancement aligns with the goal of making Blaze a versatile and user-friendly tool for handling diverse datasets.
Consideration should be given to potential dependencies and the need for additional libraries or modules.
Related Issues or PRs:

Description

Pyenv instructions - the directory is not specified , as well as the instructions required to activate the pyenv shell .
Also there is a problem with the requirements.txt and conflict in requirements.

ERROR: Cannot install -r requirements.txt (line 7) and Werkzeug==1.0.1 because these package versions have conflicting dependencies.

The conflict is caused by:
The user requested Werkzeug==1.0.1
flask 2.1.1 depends on Werkzeug>=2.0

To fix this you could try to:

1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

Steps to Reproduce

1. pyenv local venv
2. pwd
3. cd code/Blaze/
4. pip install -r requirements.txt

Checklist

• I have read the contributing guidelines
• I have verified this does not duplicate an existing issue

Problem Statement

clean

Proposed Solution

Refractored backend

Alternatives Considered

Please briefly describe which alternatives, if any, have been considered, including merits of alternate approaches and
tradeoffs being made.

Additional Context

Description

This issue is to update the README to provide a clear guidelines to install and run the front end made with react

Problem Statement

Migrating frontend from python dash to frontend framework

Proposed Solution

Creating frontend with React for its potential to reuse components. It saves time for developers as they don't have to write various codes for the same features. Furthermore, if any changes are made in any particular part, it will not affect other parts of the application.

Alternatives Considered

Please briefly describe which alternatives, if any, have been considered, including merits of alternate approaches and
tradeoffs being made.

Additional Context

Please provide any other information that may be relevant.

Set Python environment
Run:
pip install dev_requirements.txt

Config:
Add OpenAI_key, in backend/config.py

Add Swagger settings (url,host,access_key,access_secret) in
yaml/07_panoptica_bot.yaml

external_apps/slackbot/slackbot_settings.py
add SLACK_BOT_TOKEN , SLACK_APP_TOKEN

https://slack.dev/bolt-python/tutorial/getting-started
guide is meant to walk you through getting up and running with a Slack app using Bolt for Python.(This will help us setup keys)

bash run.sh server yaml=yaml/07_panoptica_bot.yaml
to run server and slackbot

Problem Statement

When the meeting is live, the users should be able to recvieve the actionables to their webexbot, on defined intervals

Proposed Solution

changed the index.js to push processed actionables to webex bot

Issue Description

Update Summary

1. Multi-Tasking: Users now have the capability to add and manage multiple tasks efficiently.

2. New Route '/actionables': A new route named '/actionables' has been introduced to enhance navigation and interaction with specific elements or actions within the application.

3. OpenAI Model Integration: This update includes the integration of the openAI model, expanding the application's capabilities and improving its functionality.

Issue Type

Feature Enhancement

Priority

Medium

Description

Create shell script to run backend or frontend, or both together passing yaml as parameter

Description

The current Readme references older instructions and needs to be corrected

Checklist

• I have read the contributing guidelines
• I have verified this does not duplicate an existing issue

Problem Statement

A lot of files are old and no longer functional given how quickly BLAZE has evolved.

Proposed Solution

Files need to be renamed, reorganized, or deleted to ensure clarity in the repository.

Problem Statement

Change the config to use environment variables

Proposed Solution

Taking config keys from environment variables.

-> Change font in BlazeLogo
-> Rename custom to User question
-> Display Seconds for avg/q in comparison and benchmark
-> Give option to use Validate or Train from SQUAD
-> Fix WebEx Demo light app
-> connect https://cisco-open.github.io/Blaze/
->

Problem Statement

Fetch transcripts from webex and store the data into .txt file

Proposed Solution

If yaml contains webx_meetings for datasets and provided webex access token in settings. Fetch all the transcripts and store into file object

Problem Statement

Add run shell script to run different services

Description

Check why generating summary from BART is long

Description

Fix image loading in readme.md

Expected Behavior

Should display two images

Actual Behavior

Images are broken in readme

Affected Version

Please provide the version number where this issue was encountered. main