Glad it was helpful Rose

Most welcome Marcelo

You are so welcome

So happy to hear this helped Gerald .. humbled

Damn I end up in same situation ...installed 22 version and my VS code saying 21 is the compatible one. Couldn't figure out how to delete the older version until now. So Thank you for this Video @RaghavPal

Hey do you mind sharing what all you learning in SF development ? I am on the same boat . Thanks

@@awesomekj5812 Sure. I've earned my Certified Admin and Platform App Builder cert so now I'm working on the Platform Developer material. I've been on trailhead working through the Platform Developer Beginner material. I'm learning more about installing and updating the org with Lightning Web Components is fun. I'm also learning about writing Apex which is challenging and pretty dull material so far. I don't have a coding background so it's taking me a little longer to grasp some of the concepts there but it's coming. How about you?

Glad it was helpful Guillermo

You are welcome

Great to know this Vikram

You're welcome

Most welcome Deshan

Necmettin Here's my take on it Understanding the Line: - Purpose: This line dynamically sets the `JAVA_HOME` environment variable to the path of the default Java version on your system, as determined by the `/usr/libexec/java_home` command. Your Situation: - Desired Java 17: You need Java 17 for your project. - Manual Path Set: You've already set the `JAVA_HOME` path to Java 17 at the end of your zshrc file. Recommendations: - Remove the Dynamic Line: Since you've manually specified the path to Java 17, keeping the dynamic line might lead to conflicts or unexpected behavior. It's generally recommended to remove it to ensure clarity and consistency in your environment. Steps: 1. Open zshrc: Use a text editor to open your zshrc file. It's typically located in your home directory: `~/.zshrc`. 2. Comment or Remove: - Comment: Add a `#` at the beginning of the line to temporarily disable it without removing it: ```bash # export JAVA_HOME=$(/usr/libexec/java_home) ``` - Remove: Delete the line entirely to permanently remove it. 3. Source zshrc: Apply the changes to your current shell session: ```bash source ~/.zshrc ``` Verification: - Check Java Version: Confirm that `java -version` now points to Java 17: ```bash java -version ``` Additional Considerations: - Multiple Java Versions: If you need to switch between Java versions frequently, consider using tools like `jenv` or `sdkman` to manage multiple installations seamlessly. - Project-Specific Requirements: If you're working with projects that require specific Java versions, using version managers or setting `JAVA_HOME` within those project environments can help isolate dependencies. By following these steps and considering the additional points, you can effectively manage your Java environment and ensure the correct version is used for your projects.

Svens 1. Yes, I will plan more lectures on these topics 2. I am not very sure on this

You're welcome

Irina I understand how frustrating it can be when dealing with Java versions and paths. Let's break it down: 1. Multiple Java Versions: - Having both Oracle and Homebrew versions of Java installed can indeed cause conflicts. - First, let's determine which version you need for your specific use case. 2. Spark and Java: - Apache Spark typically requires Java 8 (1.8) or later. - If you're using a specific SparkR version that relies on Java 8, then having Java 8 installed is crucial. 3. Checking Java Versions: - Open your terminal and run: ``` java -version ``` This will show you the default Java version. - To see all installed Java versions, use: ``` /usr/libexec/java_home -V ``` 4. Setting the Correct PATH: - Ensure that the correct Java version is in your `PATH`. - You can set the `JAVA_HOME` environment variable to point to the desired Java version. For example: ``` export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_XXX.jdk/Contents/Home ``` Replace `XXX` with the actual version number. 5. RStudio Configuration: - In RStudio, check if the Java path is correctly configured. - Go to Tools > Global Options > General and verify the Java path under "R version" settings. 6. Testing SparkR: - After adjusting the Java path, try connecting to Spark in RStudio again. - If you encounter any specific errors, feel free to share them, and I'll assist further. Remember, troubleshooting can be challenging, but we'll get through it --

Never mind, I fixed it, all are working now. I upload new R Studio and rJava packages, and miracle happen :) No actually, I add PATH from terminal output %echo $JAVA_HOME to R-Studio to Sys.getenv("JAVA_HOME") and it helped to miracle :)

Thanks for watching

I will plan

Goto Terminal Add path in .bash_profile (old macs) Or .zshrc (new macs) Starting with macOS Monterey (released in 2021), Apple switched the default shell from Bash to Zsh for new user accounts Check what is our default Shell echo $SHELL For e.g. for command echo $SHELL you got response as /bin/zsh that means your default shell is zsh (also called Z shell) and you will add env variables in file .zshrc (Else your default shell will be bash and you will add all env variables in file .bash_profile. And if that is the case just replace .zshrc with .bash_profile in all below commands) Now assuming the default shell is Zsh and we need to add env variables in .zshrc file Open Terminal Run command open .zshrc In case the file does not already exist, create the file touch ~/.zshrc This command creates the .zshrc file in your home directory (~ ) Now to edit .zshrc file we have 2 options On terminal, run command open .zshrc This should open the file in a text editor where you can edit and save it Add the below mentioned env variables and save the file If option 1 does not work, On terminal, run command cat .zshrc This will show the contents of the file on the terminal itself Now use vi editor to edit the file Run command vi .zshrc this will open file in vi editor Press i on keyboard to go into insert mode Now add the env variables as shown below (make sure to update the paths as per your system) export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-21.jdk/Contents/Home export PATH=$PATH:$JAVA_HOME/bin here you can also use $HOME in place of your home directory (e.g. /Users/raghavpal) Also notice, to give path of bin folder instead of mentioning the complete path we can refer from env variable JAVA_HOME that we have already set by using $JAVA_HOME After editing press escape key on the keyboard Now write wq! and hit Enter. This will write and quit To check the paths are set, open a new terminal and run commands cat .zshrc echo $JAVA_HOME echo $PATH Mac OS - To find all versions of JAVA available on the system and set a specific version Run command /usr/libexec/java_home -V This will show the available versions STEP 4 : Goto folder - /Library/Java/JavaVirtualMachines This should have folders of all Java/JDK available on the system STEP 5 : Goto the folder of JAVA you want and get the path of its home folder (which has bin folder) Update the path in JAVA_HOME and PATH env variables To remove Java Remove path for JAVA_HOME from shell file (.zshrc or .bash_profile) Check java -version in new terminal If you still get response Run command env Check if you see JAVA_HOME If yes run unset JAVA_HOME References: How to install Java JDK on Mac OS and set JAVA_HOME variable - kzfaq.info/get/bejne/o6d5q6yZu7CbfmQ.html How to Switch Java Version and set JAVA_HOME on Mac OS with Apple M1 M2 chip - kzfaq.info/get/bejne/Y8uTeplzxNCyh2w.html ..

Mario If you're encountering the "Unable to locate a Java Runtime" error on your Mac, there are a few steps you can take to resolve it: 1. Install Java JDK or JRE: - First, ensure that you have Java installed on your system. As of now, you can install Java versions from Java 8 to Java 21 on your Mac². It's recommended to get a stable LTS (Long Term Supported) version of Java. 2. Using Homebrew: - Open your terminal and run the following command to install OpenJDK 11 (you can choose other versions as well): ``` brew install openjdk@11 ``` - To make sure the system can find this JDK, create a symbolic link: ``` sudo ln -sfn $(brew --prefix)/opt/openjdk@11/libexec/openjdk.jdk /Library/Java/JavaVirtualMachines/openjdk-11.jdk ``` 3. Check Java Security Settings: - Go to System Preferences > Java > Security. - Make sure that "Enable launching Java Web Start applications from the browser" is enabled, even when launching them without a browser⁴. 4. Verify Java Installation: - Run the following command to check if Java is correctly set up: ``` java -version ``` - You should see information about the installed Java version. 5. Update Environment Variables: - Ensure that your `PATH` environment variable includes the correct path to the Java installation. - You can add the following line to your shell profile (e.g., `.zshrc` or `.bashrc`): ``` export PATH="/usr/local/opt/openjdk@11/bin:$PATH" ``` 6. Restart Your Terminal: - After making changes, close and reopen your terminal to apply the updates. Remember to replace `openjdk@11` with the desired Java version if you prefer a different one. Once you've completed these steps, try running your command again. It should locate the Java Runtime successfully.

Ashish yes, actually i have been planning that for long, but somehow it's getting delayed everytime. I will try to start on it as early as I can

@@RaghavPal ❤ thanks a lot! for considering my request.

If you're trying to display the value of the `JAVA_HOME` environment variable in your terminal, but nothing is showing up, there are a few steps you can take to troubleshoot this. Let's go through them: 1. Check if JAVA_HOME is Set: - First, confirm whether you have set the `JAVA_HOME` environment variable at all. - Open your terminal and type the following command: ``` echo $JAVA_HOME ``` - If it returns `%JAVA_HOME%` (or nothing), it means the variable is not set. 2. Windows Command Prompt (cmd.exe): - If you're using Windows Command Prompt, try this: ``` echo %JAVA_HOME% ``` - It should display the correct path to your Java installation (e.g., `C:\Program Files\Java\jdk1.7.0_80`). 3. Git Bash (within Windows): - If you're using Git Bash within Windows, use the following command: ``` echo $JAVA_HOME ``` - Again, it should show the correct path. 4. Windows PowerShell: - In Windows PowerShell, you can use either of these commands: ``` Get-ChildItem Env:JAVA_HOME ``` or ``` echo $env:JAVA_HOME ``` - Both should display the correct Java home directory. 5. Linux and macOS: - On Linux or macOS, simply use: ``` echo $JAVA_HOME ``` - It should show the correct path. 6. Double-Check the Path: - Make sure the path you've set for `JAVA_HOME` is correct. It should point to the root directory of your Java installation. Remember that environment variables are case-sensitive, so ensure you're using the correct capitalization. If you're still having issues, double-check your Java installation and verify that the `JAVA_HOME` variable is correctly set.

Can find these videos here - automationstepbystep.com/

As soon as possible

Getting a job in performance testing after a 5-year career gap due to government job preparation requires a strategic approach. Here are some steps you can take: 1. Highlight relevant skills and experience: * Focus on transferable skills: While your experience hasn't been directly in performance testing, highlight relevant skills gained during your govt job preparation, such as analytical thinking, problem-solving, time management, and data analysis. These skills are valuable in performance testing. * Quantify your achievements: Did you lead any projects, analyze data to draw conclusions, or implement efficiency measures? Quantify your achievements using metrics to demonstrate your effectiveness. * Relevancy of LoadRunner: Though LoadRunner may not be the latest tool, emphasize your proficiency in its core concepts like performance metrics, script development, and load generation. This knowledge can be translated to other tools. 2. Upskill and bridge the gap: * Refresh your LoadRunner knowledge: Take online courses or participate in boot camps to refresh your LoadRunner skills and stay updated with the latest features. * Learn new performance testing tools: Research popular tools like JMeter, NeoLoad, k6, and SoapUI. Choose one or two to learn based on industry demand and your career goals. Free online resources and tutorials are available. * Contribute to open-source projects: Participating in open-source performance testing projects can showcase your practical skills and passion for the field. 3. Network and build your brand: * Connect with performance testing professionals: Attend industry events, conferences, and workshops. Join online communities and forums to network with professionals and learn about current trends. * Build your online presence: Create a LinkedIn profile showcasing your skills and experience. Share relevant articles, blogs, and projects to demonstrate your knowledge and passion. * Reach out to recruiters: Contact recruiters specializing in performance testing roles. Express your enthusiasm and willingness to learn, highlighting your transferable skills and desire to bridge the gap. 4. Emphasize your learning agility and dedication: * Be transparent about your career gap: Address your gap upfront and frame it as a period of self-improvement and skill development. Highlight the skills you gained during that time. * Showcase your eagerness to learn: Show your willingness to learn new tools and adapt to industry changes. Your passion for performance testing and learning mindset will be appreciated. 5. Tailor your resume and cover letter: * Customize your resume for each job application: Highlight relevant skills and experience mentioned in the job description. Quantify your achievements and use keywords from the job posting. * Write a compelling cover letter: Explain your career journey and motivation for pursuing performance testing. Connect your skills and experience with the specific requirements of the job. Remember, landing a job after a career gap requires initiative, perseverance, and a willingness to learn. By highlighting your relevant skills, upskilling yourself, and building your network, you can increase your chances of success in performance testing. I hope this helps! Good luck with your job search!

@@RaghavPal ok tq sir

Naveen With your 1.5 years of experience as an automation tester with the skillset you mentioned (Selenium (Java), Cucumber, Appium, and API Testing (Postman and RestAssured)), you can expect a decent salary in both Chennai and Bangalore. Here's a breakdown: Salary Range: * Chennai: 4.5 Lakhs per annum (₹450,000) to 7 Lakhs per annum (₹700,000) * Bangalore: 5 Lakhs per annum (₹500,000) to 8 Lakhs per annum (₹800,000) Factors Affecting Salary: * Specific skills and experience: The depth of your knowledge in each tech stack and your experience with specific projects can significantly impact your salary. Strong expertise in frameworks like Appium or RestAssured can be particularly advantageous. * Company size and type: MNCs and product-based companies generally offer higher salaries compared to startups or service-based companies. * Negotiation skills: Don't hesitate to negotiate your salary based on your qualifications and market value. Additional Considerations: * Bonus and benefits: Some companies offer attractive bonuses, stock options, and comprehensive health insurance, which can add to your overall compensation package. * Location within the city: Certain areas in Bangalore might offer slightly higher salaries compared to others. Remember: 1.5 years is still early in your career. Focus on continuously improving your skills, gaining experience on diverse projects, and building a strong portfolio. This will put you in a better position to command a higher salary in the future. I hope this information helps.. best wishes

@@RaghavPal Thank you so much for this information and your tutorial videos, sir.

The error message `.zshenv:1: command not found: Export` suggests that there is a typo in your `.zshenv` file. The correct command should be `export` (all lowercase), not `Export`. The shell commands are case-sensitive, and having the wrong case can lead to such command not found errors. To fix this, you'll need to edit the `.zshenv` file and correct the command. Here's how you can do it: 1. Open the terminal. 2. Type `nano ~/.zshenv` and press Enter to open the file in the nano text editor. 3. Look for the line that contains `Export` and change it to `export`. 4. Save the changes by pressing `Ctrl + O`, then press Enter. 5. Exit nano by pressing `Ctrl + X`. After making these changes, the error should no longer appear when you open a new terminal window. If you're not comfortable using nano, you can use any other text editor you're familiar with to make this change. Remember to be cautious when editing configuration files like `.zshenv` to avoid further issues. .

Thank you, sir @RaghavPal. The error is gone now. Once again, thank you for your valuable comments. I subscribed to you.👍