First thing I do after unpacking the SnowSQL Linux client is try to upgrade it. This has worked very well through at least v1.1.84. Today I downloaded v1.2.2, installed it, and got an error:
$ ~/bin/snowsql -Uv
No snowsql is available for download: url=https://sfc-repo.snowflakecomputing.com/snowsql, version=1.2
The error comes from this download. Has something changed? I get the same error even when I just try to use it with no options at all, or trying to connect by passing my account code and username.
The curl above was missing https and hence gave the wrong impression of 403 forbidden.
Some times due to a caching issue with the downloads it will not autoupgrade. There are two main components, one being bootstrap and the other one being the main snowsql component. The one you see the issue with is the main component (it is auto-downloaded when you run snowsql).
You can force new version download using snowsql -v 1.2.2 as an exmaple.
You can delete/move the .snowsql directory (~/.snowsql or ~/bin/.snowsql) to ensure a new main component version is downloaded by the new bootstrap.
You may also try using the newer versions for which the rpm is available at
https://sfc-repo.snowflakecomputing.com/snowsql/bootstrap/1.2/linux_x86_64/index.html
I noticed Snowflake has some weird firewall configs and similar errors can either happen consistently or intermittently.
The only option I'm aware of that can help if it happens consistently is to use --noup flag with your commands. This will not check for snowsql updates of course, but you can always manually download a newer version via your browser(with VPN is needed).
Related
I am trying to use the latest version of the appImage-builder because appimages of my application built with the old version of appImage-builder do not run on ubuntu 22.04 anymore. So I got the order to try and see if it works with the new appImage-builder.
Currently (June 2022), only versions below 1.0 which are based on ubuntu 18.04 are available on docker (which we previously used to build our appimage).
The newer versions are available via github (https://github.com/AppImageCrafters/appimage-builder/releases).
However, I seem to be unable to execute:
appimage-builder --generate
or
appimage-builder --recipe AppImageBuilder.yml
Is there any documentation available on how to correctly use the .appimage version of appImage-builder? All I could find in https://appimage-builder.readthedocs.io/en/latest/ seems to refer to the docker version or a manually built version of appImage-builder.
Depending on the error message you get, there could be a couple of issues at play here.
If you got an error related to FUSE, then you need to install the libfuse2 package with apt install libfuse2. AppImages rely on libfuse2, but Ubuntu has stopped including it since 22.04, in favor of libfuse3.
If you get an error related to "file not found", then it could be that you do not have AppImageLauncher installed. Sadly, with type 2 AppImages the design decision was taken to modify the ELF header of the executable with 3 magic bytes at offset 8 of the executable. This means that Linux linkers will not run the file. AppImageLauncher actually copies the file to a temporary directory and zeroes out the magic number in order to be able to execute it.
A good starting point for debugging issues like this is to run the strace command, which will let you see which system call likely cause the error. Keep in mind that if you try to execute a file and you get File not found, it might mean that the linker specified by the file can not be found on the system or the ELF header is not valid. You can also run the executable by using the linker directly, which might give you more clues. For example with: /lib64/ld-linux-x86-64.so.2 <NAME-OF-YOUR-EXECUTABLE>.
I get "The procedure entry point GetHostNameW could not be located in the dynamic link library WS2_32.dil" error when I command Heroku create . I already installed Heroku cli on my computer. For the first time (first project) it (Heroku create) worked fine.
But the 2nd time when I gave this command it gave me an error.
After a long research on the internet I could not get rid of this error.
Now please tell me how I can solve this problem ? Note: My OS is Windows 7
You cannot. GetHostNameW is only available in Windows 8 and above.
see: https://learn.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-gethostnamew
PROBLEMO
Heroku CLI current latest version (as of July 2022) is 7.60.2, which was forced by auto-update onto our machine regardless of our OS version; this CLI version somehow used WS2_32.dll with GetHostNameW API that only applicable to Windows 8+. Error:
Node.exe - The procedure entry point GetHostNameW could not be located in the dynamic link library WS2_32.dll
No Heroku problem-ticket was open as far as I know (and Heroku PROHIBITS me from opening a new ticket!)
SOLUTION
This is a "hack" (temporary) solution until - hopefully - Heroku addresses this issue! Basically we will force our local machine Heroku CLI to use the previous version that was working before the latest update.
Open: [YourLocalUserFolder]\AppData\Local\heroku\autoupdate.log => Go to the last update log (typically the LAST line at the bottom of the file), and see which version that was working before the latest updates who broke it. Example:
waiting until 2022-07-23T22:40:33.199Z to update
time to update
heroku: Updating CLI...
heroku: Updating CLI from 7.59.2 to 7.60.2... done
From this log, we found that the currently used CLI is v. 7.60.2. This version is the one broke my CLI on Windows 7, causing the error. The solution here is to go back and use the previously working version: 7.59.2
Go to and make backup of the following:
Folder [YourLocalUserFolder]\AppData\Local\heroku\client\7.59.2 => As: [YourLocalUserFolder]\AppData\Local\heroku\client\7.59.2_BACKUP_20220723. Why? This is the WORKING CLI version, so we want to preserve it from Heroku auto-delete!
(Optional) File [YourLocalUserFolder]\AppData\Local\heroku\client\bin\heroku.cmd => As: [YourLocalUserFolder]\AppData\Local\heroku\client\bin\heroku.cmd_ORIG_20220723. Why? This is the original CMD file containing the latest syntax after Heroku latest update. We are going to modify this file.
Modify file: [YourLocalUserFolder]\AppData\Local\heroku\client\bin\heroku.cmd => with the following:
"%~dp0..\7.59.2\bin\heroku.cmd" %*
What it is: To modify the last line only, change from whatever latest version to "7.59.2" version. By doing this, when we run heroku CLI again, it shall use this version, and not the latest one.
I have a little problem while I want to update my package. I'll explain this: I published my package. After that, I waited for 2-3 hours for my packages be in the microsoft/winget-pkgs in GitHub. My branch merged successfully, It works on any Windows devices but, I created a new version of my application: v3.6.2. The version that I released it was v3.5.7. So now, I can't publish that version because this error is showing when I execute this cmd command: wingetcreate update <packageIdentifier> -u https://github.com/YourUsername/yourrepository/releases/download/3.6.2/yourapp.exe --version 3.6.2 -t ghp_YourGithubPersonalAccessTokenWith_public_repo_setting.
If you want an image, i'll show you the image (My Windows is French btw): Here the image. But as you can see, the red is the error and I tried everything, I searched on Google and didn't find anything that fixed my problem, I tried the examples showed above when you only execute this command: wingetcreate.exe update but still the same error message that you can see on the image.
So I decided to take the third example but same, without success. Is there a way that could update my WinGet package? Thanks!
I don't know if this could help but I can give you some info: it's inno, the achitecture is Neutral.
IMPORTANT NOTE:
FIX HERE
The last answer works but if you type the command winget search <YourApp>, it will keep the previous version and if you install, it would install the previous one... How to fix that because it is litteraly NOT updating but doing nothing.
It's hard for me to know exactly what the issue is without knowing the contents of the manifest or the metadata of the installer. My gut feeling is that there is an architecture mismatch when trying to match the installer you provided with the existing installer that is currently specified in the existing manifest. To override the detected architecture you can use the '|' symbol followed by the desired architecture. Here is an example:
wingetcreate update <packageIdentifier> -u "https://github.com/YourUsername/yourrepository/releases/download/3.6.2/yourapp.exe|x64" --version 3.6.2 -t <githubToken>
If that doesn't work for you, I would encourage you to post an issue on the GitHub repository so we can help you further.
Okay, I found the way: You take the code that the previous answer contains, and add -s:
wingetcreate update -s <packageIdentifier> -u "https://github.com/YourUsername/yourrepository/releases/download/3.6.2/yourapp.exe|x64" --version 3.6.2 -t <githubToken>
It will publish the application on GitHub for verification, in the command prompt you put (replace the sentence in the quotes with your current manifest file):
winget validate --manifest "PathToYourManifestShowedInGreenAfterPublishing"
When the validation on GitHub is done, it's done and normally it should work.
NOTE: Verification on GitHub can take 2 to 3 hours or even 4 hours. Be patient! (I hope)
I attempted to check the version of my go executable with go version on an Ubuntu machine, however I got the following error:
No version set for command go
Consider adding one of the following versions in your config file at
golang 1.16.8
golang 1.17.1
How do I resolve this? I have no prior experience with config file, I searched on google but I found nothing which could solve this issue.
That seems to be an error message from asdf-vm/asdf, a tool which manages multiple runtime versions with a single CLI tool, extendable via plugins.
You can see that error message in asdf-vm/asdf issue 838.
The config file should be in $HOME/.tool-versions
To resolve this, as in this example:
asdf plugin add go
asdf install go latest
I am trying to get gomail via gopkg.in/gomail.v1 but my connection just stays hanging. In other words, on my console, when I type:
[developer#machine gocode]$ go get gopkg.in/gomail.v1
I get nothing
However in the /gocode/src/gopkg.in directory, I see a directory named gomail.v1 with nothing inside..
I hope this will help others. I spent almost 3 hours figuring this out. Apparently,
[developer#machine gocode]$ go get gopkg.in/wantedpackage
will not not work with git version < 1.7.9.5.
The trick is to upgrade your git version. I upgraded my git version to 1.7.12.4 and it works.
go get does not not display anything while downloading and installing libraries. So as long as you are connected to the internet just wait. If there are troubles connecting to the server it will display an error.
Depending on your platform: Check if you have installed git and hg.