Ways to ask Claude to debug

 1) Asking for verification - do not use a generic prompt.

I'm working on a project to upgrade a liferay project from 7.2 to 7.4. Whenever I encounter an error, I would usually form a hypothesis in my mind, and ask Claude to verify if it's true or not. For example, I am having an issue with a library declared in build.gradle not being found in one of the module. The library being used in 7.2 was:

compileOnly group: "javax.portlet", name: "portlet-api"
compileOnly group: "javax.servlet", name: "javax.servlet-api"

But in 7.4, Claude recommended me to replace javax with jakarta.

compileOnly group: "jakarta.portlet", name: "portlet-api"
compileOnly group: "jakarta.servlet", name: "jakarta.servlet-api"

Upon building, I get an error:

> Could not find jakarta.portlet:portlet-api:.

       Required by:

           project :modules:thebank-cam-module:thebank-cam-services

     > Could not find jakarta.servlet:jakarta.servlet-api:.

Finding it weird, I went ahead to the project settings.gradle file, and find out the source of the library, which is in 

repositories {
  maven {
    url "https://repository-cdn.liferay.com/nexus/content/groups/public"
  }

I checked the repository, and the library - compileOnly group: "jakarta.servlet", name: "jakarta.servlet-api", does exist.

Normally, I would just feed the error message to Claude, have it identify the root cause of the issue, and suggest a solution. And guess what's Claude solution, removing the library out of build.gradle

Therefore, I tried changing the way to ask Claude, for example,

<verify>the library is getting from "https://repository-cdn.liferay.com/nexus/content/groups/public" defined in settings.gradle, and the library exists in the repository.</verify><instructions>identify the source of the library <verify>jakarta.servlet", name: "jakarta.servlet-api is an existing library, and there is no other library that replaces that.</verify>, and identify the root cause of why Could not find jakarta.servlet:jakarta.servlet-ap as shown in the deploy log</instructions>

Comments

Post a Comment

Popular posts from this blog

How to add environment variables into Heroku container

Image
 Method 1: Using .env file  NOTE: Please add your .env file into .gitignore to not make the file visiblein github. Before we start, please make sure you have ran ' heroku scale worker=1 -a (app) ' in your app.  1) Create an .env file and add your environment variable like so: your-environment-variable=123 2) In your code, import load_dotenv from dotenv like so: import os from dotenv import load_dotenv load_dotenv() test-env = os.getenv('your-environment-variable')  print(test-env)  Note: Please make sure you have requirements.txt present by doing 'pip freeze > requirements.txt' 3) Create your dockerfile FROM python:latest WORKDIR / COPY . . RUN pip install -r requirements.txt CMD [ "python", "test.py" ] 4) Run ' heroku container:push worker -a (app name) ' 5) Run ' heroku container:release worker -a (app name) ' 6) Wait for 10-20 seconds... 7) You can test if your app is working by running ' heroku logs -a (app name)...
Read more

Running CQL scripts in Cassandra

How to run CQL scripts in Cassandra  There are 2 ways to run a CQL script, the first way would be running the following command: - cqlsh -f {directory} The second way would be using the command within the CQLSH terminal: - source '{directory}' Where does the {directory} points to? The directory points to the root of your server. For example, if you are on linux, the root would be `/`. Therefore, if you placed your scripts under the folder `scripts`, your directory would look like this `/scripts/{cql_script_name}.cql`.  I've been running the command, but it keeps saying `No such file or directory`? If you met this error, please make sure that:      - The file actually exist in the directory. You can check if by typing `ls -l {directory}`. If it doesn't exist, it will show the same error. If you are on docker, and you are unsure of how to mount your CQL file into your container, you can check out this guide.      - The CQL file has the correct exten...
Read more

Failed to apply plugin Intellij Gradle

Image
 Failed to apply plugin in Intellij Gradle is caused by wrong Java version being used in Gradle. To fix it, go to Settings -> Build, Execution, Deployment  -> Build Tools -> Gradle , find Gradle section, and select the correct Gradle JVM version. The version of JVM used should be compatible with the version of Gradle you are using.  If all still can't work, try the following: - Invalidate cache (Go to File -> Invalidate Cache ) - Delete the global .gradle folder (Located in your Users folder), as well as your project .gradle folder, and run ./gradlew.bat --refresh-dependencies - Ensure the JAVA_HOME and PATH is pointing to the right JDK version. For my case, my project is using Java 11, so the values should reflect.  JAVA_HOME = C:\Program Files\Java\jdk-11.0.8 PATH=C:\Program Files\Java\jdk-11.0.8\bin Note: Also, please make sure that the \ bin is added at the back of the path. If you have multiple Java version installed, please make sure the path...
Read more