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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log ai_settings.yaml in logs/DEBUG/[TIMESTAMP_AGENT_NAME]/001/ 0_ai_settings.yaml #3960

Closed
1 task done
waynehamadi opened this issue May 7, 2023 · 3 comments
Closed
1 task done
Labels

Comments

@waynehamadi
Copy link
Contributor

waynehamadi commented May 7, 2023

Duplicates

  • I have searched the existing issues

Summary 馃挕

if we put the ai_settings in the logs/DEBUG we will easily be able to reproduce people's bugs.
Log ai_settings.yaml in logs/DEBUG/[TIMESTAMP_AGENT_NAME]/001/ 0_ai_settings.yaml

todo:
in agent.py
just before:

self.log_cycle_handler.log_cycle(
                self.config.ai_name,
                self.created_at,
                self.cycle_count,
                self.full_message_history,
                FULL_MESSAGE_HISTORY_FILE_NAME,
            )

call self.log_cycle_handler but pass the ai_settings instead.

Make sure you test your changes by running python -m autogpt --debug

Examples 馃寛

No response

Motivation 馃敠

No response

@Boostrix
Copy link
Contributor

Boostrix commented May 7, 2023

agreed regarding the usefulness, but that is a potential privacy issue, so people should explicitly be told what info is in there.
This is now also heavily overlapping with requirements to support multiple projects as per #3549 and #3039

The background here being, the requirements are very much overlapping and for devs/contributors to be able to reproduce a certain setup, it would obviously be helpful to just hand a certain folder over to agpt and tell it to treat it as its workspace, but also to look for its ai_settings.yaml file in it - at that point, we'd basically have multi-project support (via sub-directories) but also a capability to reproduce issues (as long as the yaml file doesn't have implicit assumptions about data in the workspace) - that being said, providing an option to also zip up the workspace itself would make sense to get more/better data that can be more easily reproduced

@github-actions
Copy link
Contributor

github-actions bot commented Sep 6, 2023

This issue has automatically been marked as stale because it has not had any activity in the last 50 days. You can unstale it by commenting or removing the label. Otherwise, this issue will be closed in 10 days.

@github-actions github-actions bot added the Stale label Sep 6, 2023
@github-actions
Copy link
Contributor

This issue was closed automatically because it has been stale for 10 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants