12 lines
2.8 KiB
Markdown
12 lines
2.8 KiB
Markdown
## Gemini Added Memories
|
|
- The user and I were analyzing a RISC-V Go panic. The user provided a panic log showing a 'SIGQUIT: quit' signal. I concluded that the panic was not a bug, but rather the result of a test timeout in 'tsan_test.go', which was running a long, resource-intensive build of the standard library with the thread sanitizer enabled. The test harness sent SIGQUIT to terminate the build process and get a stack dump.
|
|
- When executing Go commands in the `/home/jcarr/go/src` project, I must first change into the `gemini/` directory. For example: `cd gemini/ && go run ...`
|
|
- When asked to commit code with git, I should follow this workflow: 1. Run `git status` to identify unstaged files. 2. Run `git add <files>` to stage the necessary files. 3. Run `git commit -m '<descriptive message>'` to commit the changes.
|
|
- To set git author details for a commit, use environment variables: GIT_AUTHOR_NAME='Gemini' GIT_AUTHOR_EMAIL='gemini@wit.com' git commit ... Do not modify the local .git/config file unless specifically asked.
|
|
- My git workflow: 1. `git status` to check for changes. 2. `git add <files>` to stage them. 3. Commit using `GIT_AUTHOR_NAME='Castor Gemini' GIT_AUTHOR_EMAIL='gemini@wit.com' git commit -m '...'`. 4. Push changes using `git push`. 5. If the push fails due to a missing upstream branch, use `git push --set-upstream origin <branch_name>`.
|
|
- When updating the `gemini/today.log` file, I must create a detailed, transcript-style log of the conversation, not a summary. This log must include any tables I generate, and these tables must be carefully formatted with space padding so that all `|` characters align vertically for a clean, fixed-width font display.
|
|
- For logging conversations, I will create a date-stamped text file (e.g., `log/YYYY-MM-DD.text`) inside the `gemini/` directory. The format should be the protobuf-like text format, similar to `log/sample.text`. I should not create JSON or simple .log files anymore.
|
|
- My standard workflow: Upon completing a task and verifying the solution, I will automatically commit the changes. The commit process is: 1. `git status`. 2. `git add <files>`. 3. `GIT_AUTHOR_NAME='Castor Gemini' GIT_AUTHOR_EMAIL='gemini@wit.com' git commit -m '...'`. 4. `git push`. I will handle missing upstream branches as needed. I should only commit after a task is successfully completed.
|
|
- Start of a new discussion topic: SiFive P550 board USB TTY issues. When generating the log file, the conversation should be segmented starting from this point.
|
|
- My standard git workflow: Upon completing a task and verifying the solution, I will automatically commit the changes. The commit process is: 1. `git status`. 2. `git add <files>`. 3. `GIT_AUTHOR_NAME='Castor Gemini' GIT_AUTHOR_EMAIL='gemini@wit.com' git commit -m '...'`. I will NOT run `git push` and will leave the pushing of commits to the user.
|