Home/ Kenil Vasani/Answers
  1. Asked: In:

    Could not create token: Implicit conversion of keys from strings is deprecated. Please use InMemory or LocalFileReference classes

    Kenil Vasani

    Kenil Vasani

    View Profile
    Best Answer
    Kenil Vasani

    On this thread, two solutions has been proposed as quickfix: Solution 1: In config\jwt.php file Change 'jwt' => Tymon\JWTAuth\Providers\JWT\Lcobucci::class, to 'jwt' => Tymon\JWTAuth\Providers\JWT\Namshi::class, => It works for me <3 Solution 2: lcobucci/jwt:3.4 has this problem, composeRead more

    On this thread, two solutions has been proposed as quickfix:

    Solution 1:

    In config\jwt.php file Change ‘jwt’ => Tymon\JWTAuth\Providers\JWT\Lcobucci::class, to ‘jwt’ => Tymon\JWTAuth\Providers\JWT\Namshi::class, => It works for me <3

    Solution 2:

    lcobucci/jwt:3.4 has this problem, composer require lcobucci/jwt:3.3 can resolve it.

    It seems to be a problem with the lastest jwt package release (3.4.0)

    See less
    • 0
  2. Asked: In:

    Could not find tools.jar. Please check that /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home contains a valid JDK installation

    Kenil Vasani

    Kenil Vasani

    View Profile
    Best Answer
    Kenil Vasani

    The problem is that with the update the built-in java took precedence and it doesn't have the SDK because it's just the runtime. You just need to change your java home and add the java binary to your .zshrc to find your java home execute: /usr/libexec/java_home -V | grep jdk the output should be simRead more

    The problem is that with the update the built-in java took precedence and it doesn’t have the SDK because it’s just the runtime.

    You just need to change your java home and add the java binary to your .zshrc to find your java home execute:

    /usr/libexec/java_home -V | grep jdk

    the output should be similar to the following:

    Matching Java Virtual Machines (1):
1.8.0_272 (x86_64) "AdoptOpenJDK" - "AdoptOpenJDK 8" /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home
/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home

    you should take the path from the one that says SDK in my case

    /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home

    after that, you just add the following to the end of your .zshrc that should be in your home.

    You can edit it with (if you decide to use vim you can exit writing :wq! and pressing enter)

    vim .zshrc

    add the following:

    export JAVA_HOME=the/path/you/copied/before
export PATH=$JAVA_HOME/bin:$PATH

    where the/path/you/copied/before in my case would be

    /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home

    save the file and close all your terminals and open them again.

    The error should be solved.

    See less
    • 0
  3. Asked: In:

    Failed to read descriptor from node connection: A device attached to the system is not functioning error using ChromeDriver Selenium on Windows OS

    Kenil Vasani

    Kenil Vasani

    View Profile
    Kenil Vasani

    This error message... [14432:11656:1120/161059.539:ERROR:device_event_log_impl.cc(211)] [16:10:59.539] USB: usb_device_handle_win.cc:1020 Failed to read descriptor from node connection: A device attached to the system is not functioning. (0x1F) ...implies that the ChromeDriver raised an error whileRead more

    This error message…

    [14432:11656:1120/161059.539:ERROR:device_event_log_impl.cc(211)] [16:10:59.539] USB: usb_device_handle_win.cc:1020 Failed to read descriptor from node connection: A device attached to the system is not functioning. (0x1F)

    …implies that the ChromeDriver raised an error while in trying to initiate/spawn a new Browsing Context i.e. Chrome Browser session.

    Analysis

    This error occurs due to an USB device which is attached to the windows-10 system and isn’t functioning properly.

    This error is defined within usb_device_handle_win.cc as follows:

    void UsbDeviceHandleWin::GotDescriptorFromNodeConnection(
    TransferCallback callback,
    scoped_refptr<base::RefCountedBytes> request_buffer,
    scoped_refptr<base::RefCountedBytes> original_buffer,
    Request* request_ptr,
    DWORD win32_result,
    size_t bytes_transferred) {
  std::unique_ptr<Request> request = UnlinkRequest(request_ptr);
  if (win32_result != ERROR_SUCCESS) {
    SetLastError(win32_result);
    USB_PLOG(ERROR) << "Failed to read descriptor from node connection";
    std::move(callback).Run(UsbTransferStatus::TRANSFER_ERROR, nullptr, 0);
    return;
  }

    Solution

    This error isn’t harmful and doesn’t blocks the spawning of the new Browsing Context i.e. Chrome Browser session. So you can safely ignore the error.

    However in your code block you need to replace the keyword resource_path with executable_path and your effective code block will be:

    webdriver.Chrome(executable_path=r'C:\webdriver\chromedriver.exe') # to open the chromebrowser 
driver.get("https://web.whatsapp.com")
    See less
    • 0
  4. Asked: In:

    Error: PostCSS plugin tailwindcss requires PostCSS 8

    Kenil Vasani

    Kenil Vasani

    View Profile
    Kenil Vasani

    worked for me : npm install [email protected]:@tailwindcss/postcss7-compat [email protected]^7 [email protected]^9

    worked for me : npm install [email protected]:@tailwindcss/postcss7-compat [email protected]^7 [email protected]^9

    See less
    • 0
  5. Asked: In:

    Error: PostCSS plugin tailwindcss requires PostCSS 8

    Kenil Vasani

    Kenil Vasani

    View Profile
    Kenil Vasani

    You're integrating Tailwind with a tool that relies on an older version of PostCSS. You can use this doc https://tailwindcss.com/docs/installation#post-css-7-compatibility-build

    You’re integrating Tailwind with a tool that relies on an older version of PostCSS. You can use this doc https://tailwindcss.com/docs/installation#post-css-7-compatibility-build

    See less
    • 0
  6. Asked: In:

    create-react-app is not working since version 4.0.1

    Kenil Vasani

    Kenil Vasani

    View Profile
    Kenil Vasani

    I solved the issue by: uninstalling node via terminal using home-brew Make sure to do a deep clean by utilising the following commands: brew uninstall node; brew cleanup; brew uninstall --force node Go to https://nodejs.org/en/ and download the stable version package and install it. It should work nRead more

    I solved the issue by:

    1. uninstalling node via terminal using home-brew
    2. Make sure to do a deep clean by utilising the following commands: 
       brew uninstall node; 
 brew cleanup;
 brew uninstall --force node
    3. Go to https://nodejs.org/en/ and download the stable version package and install it. It should work now
    See less
    • 0
  7. Asked: In:

    create-react-app is not working since version 4.0.1

    Kenil Vasani

    Kenil Vasani

    View Profile
    Best Answer
    Kenil Vasani

    I also face the same problem but the problem gets solved when I uninstall the create-react-app globally and then again install it globally. Uninstalling Command: npm uninstall -g create-react-app installing Command: npm install -g create-react-app it solved my problem I hope it will solve yours

    I also face the same problem but the problem gets solved when I uninstall the create-react-app globally and then again install it globally.

    Uninstalling Command:

    npm uninstall -g create-react-app

    installing Command:

    npm install -g create-react-app

    it solved my problem I hope it will solve yours

    See less
    • 0
  8. Asked: In:

    SyntaxError: Generator expression must be parenthesized

    Kenil Vasani

    Kenil Vasani

    View Profile
    Kenil Vasani

    Generator expression must be parenthesized > Update Django version to 1.11.17 pip install django==1.11.17

    Generator expression must be parenthesized

    > Update Django version to 1.11.17

    pip install django==1.11.17
    See less
    • 0
  9. Asked: In:

    ssl.SSLError: tlsv1 alert protocol version

    Kenil Vasani

    Kenil Vasani

    View Profile
    Kenil Vasani

    Follow these steps: pip install cmake Install Visual Studio build tools from here. In Visual Studio 2017 go to the Individual Components tab, Visual C++ Tools for Cmake, and check the checkbox under the "Compilers, build tools and runtimes" section. pip install dlib

    Follow these steps:

    • pip install cmake
    • Install Visual Studio build tools from here.
    • In Visual Studio 2017 go to the Individual Components tab, Visual C++ Tools for Cmake, and check the checkbox under the “Compilers, build tools and runtimes” section.
    • pip install dlib
    See less
    • 0
  10. Asked: In:

    ssl.SSLError: tlsv1 alert protocol version

    Kenil Vasani

    Kenil Vasani

    View Profile
    Best Answer
    Kenil Vasani

    I had the same error and google brought me to this question, so here is what I did, hoping that it helps others in a similar situation. This is applicable for OS X. Check in the Terminal which version of OpenSSL I had: $ python3 -c "import ssl; print(ssl.OPENSSL_VERSION)" >> OpenSSL 0.9.8zh 14Read more

    I had the same error and google brought me to this question, so here is what I did, hoping that it helps others in a similar situation.

    This is applicable for OS X.

    Check in the Terminal which version of OpenSSL I had:

    $ python3 -c "import ssl; print(ssl.OPENSSL_VERSION)"
>> OpenSSL 0.9.8zh 14 Jan 2016

    As my version of OpenSSL was too old, the accepted answer did not work.

    So I had to update OpenSSL. To do this, I updated Python to the latest version (from version 3.5 to version 3.6) with Homebrew, following some of the steps suggested here:

    $ brew update
$ brew install openssl
$ brew install python3

    Then I was having problems with the PATH and the version of python being used, so I just created a new virtualenv making sure that the newest version of python was taken:

    $ virtualenv webapp --python=python3.6

    Issue solved.

    See less
    • 0