Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurations Not loading for the connector #19

Closed
CC-isha opened this issue Aug 6, 2024 · 5 comments
Closed

Configurations Not loading for the connector #19

CC-isha opened this issue Aug 6, 2024 · 5 comments

Comments

@CC-isha
Copy link
Member

CC-isha commented Aug 6, 2024

Description:
I am encountering an issue with the MuleChain Connector version 0.2.0 where the configurations do not seem to load properly. Despite multiple refreshes and attempts to reload, the configurations fail to appear.

Steps to Reproduce:

Install MuleChain Connector version 0.2.0.
Open the connector configuration settings.
Attempt to load the configurations.
Refresh the configurations multiple times.
Expected Behavior:
The configurations should load successfully upon refreshing.

Actual Behavior:
The configurations do not load, even after multiple refresh attempts.

Environment:

MuleChain Connector version: 0.2.0
Mule runtime : 4.6.1
OS : Windows

image

@amirkhan-ak-sf
Copy link
Member

Hi @arpitg-1

I sometimes have the same issue, but mostly when my machine is on heavy CPU usage due to Slack, Google Meet, etc. I thought it was only me, but looks like other users are also facing the issue. Any idea?

@arpitg-1
Copy link
Contributor

arpitg-1 commented Aug 7, 2024

Hi,

Just wanted to know few things to debug further.

  • Is this occurring only for "Model Name"? If so, can we try to select "Llm type" explicitly and then check on "Model Name".
  • How many times can we reproduce this issue?

@CC-isha
Copy link
Member Author

CC-isha commented Aug 7, 2024 via email

@arpitg-1
Copy link
Contributor

arpitg-1 commented Aug 9, 2024

Hi Isha,

We need to convert the configuration from static to dynamic one and then resolve values. Please find the steps as mentioned below for a quick fix to this.

Steps:

  1. Make any non-list config parameter to contain data weave values. For eg: lets take File Path & click on "fx"
  2. Provide some dummy value inside the text box, eg: envVars.json
  3. Try to refresh the config values for Llm Type and others.
  4. After this the values will be cached, then we can remove value in “File Path”

We are currently working on the permanent fix.

@CC-isha
Copy link
Member Author

CC-isha commented Aug 9, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants