I'm facing an issue with some providers which are not compatible with terraform-Arm64.
For example - the Spotinst provider, so I switched the terraform binary installed on my MacOS to terraform-Amd64 as they consulted me to do, and then everything seemed to work fine.
But after, it caused errors with other providers which worked with my previous installation of terraform-Arm64.
I have an Apple M1 Pro chip, and I currently installed both of the binaries and called one of the commands terraform-arm and the other terraform-amd.
I switch between them when necessary, but I'm not sure that this is the right way to manage it.
Do you know any other ways to use both of the downloads?
Related
Background
I have been playing around with Scenic to make a desktop app across multiple environments. While the Install dependencies for Ubuntu are outdated and don;t work for the latest LTS (v20) I was still able to figure out the packages and install it on Ubuntu Linux.
However ... there is nothing for Windows.
Questions
Does Scenic even work on Windows?
If so, what are the dependencies? What need I to install?
Answer
Unfortunately, Scenic does not run on Windows, nor can it support it.
At the time of writing of this post, I am also unaware of any plans to make it work on a Windows system.
The confirmation came from an official collaborator from the Scenic project:
https://github.com/boydm/scenic/issues/206
I am having difficulty installing various Julia packages on my Windows 7 laptop. When trying to add certain packages I receive the following error:
(v1.3) pkg> add MbedTLS
Updating registry at `C:\Users\uname\.julia\registries\General`
Updating git-repo `https://github.com/JuliaRegistries/General.git`
Resolving package versions...
ERROR: Unable to automatically install 'MbedTLS' from 'C:\Users\uname\.julia\packages\MbedTLS_jll\wUtL4\Artifacts.toml'
Several packages install happily, and I think I've narrowed it down to those that are supplied via BinaryBuilder.jl, such as MbedTLS, Arpack, OpenSpecFun. If I try to install any packages that have any such packages as a dependency I get the same error message when it hits one of these (initially encountered when I was trying to install Genie.
I am using the latest Julia (1.3.1), although I encountered the same issue previously in 1.2 - I managed to fix things eventually in that case, and tried a similar approach (manually downloading and placing in packages folder) but have not been able to fix things in this instance (although I confess that my notes were a little lacking so can't be certain I'm doing the correct thing). The various packages seem to exist in ...\.julia\packages\ (although not in .julia\compiled), but julia complains whenever I try to add them to some environment.
I don't think I understand julia's package system well enough to see quite what is going on here. I have seen other people with similar issues but not found anything yet which has worked - any help would be much appreciated!
This usually is due to an issue with your powershell installation, which is what we use to download these binaries in Julia 1.3 and 1.4. In particular, most of the internet (including GitHub, where most of our binaries are hosted) disabled SSL v3, TLS 1.0, and TLS 1.1 in 2018. Windows 7 is old enough that it doesn't speak TLS 1.2+ natively; instead you must install two packages:
This TLS easy_fix
Windows Management Framework 3.0 or later, to get Powershell v3+
This is necessary on Windows 7, but not on Windows 10. For more instructions, you can read the Julia platform specific instructions: https://julialang.org/downloads/platform/
I recently installed the windows branch of Caffe onto my windows machine. It works fine but then we I tried running some other projects I found online they didn't work at all and gave me all kinds of errors.
I think the reason it doesn't work is because they were using a different branch of caffe, this one for instance.
Is there a fix to this problem? Can I run ssd caffe on windows somehow?
The Caffe-SSD is not a branch, but a fork of the vanilla Caffe. Compiling and using Caffe on Windows requires certain effort (e.g. pre-building some external libs, adjusting CMake config etc.), which was not done for the Caffe-SSD fork.
You need to merge the contributions from the Windows branch into the Caffe-SSD. There are some existing solutions for that (https://github.com/runhang/caffe-ssd-windows, https://github.com/gustavkkk/caffe-ssd-win, google for more), but I did not use those.
I've been reading about youcompleteme plugin for VIM.
The problem is, however, that I want a setup I just can move onto my other dev platforms (OpenIndiana, FreeBSD, Linux and OS X).
Wouldn't using macvim make that somewhat difficult, moving plugin from platform to platform?
Cheers
MacVim is simply a distribution of Vim for Mac OS but most of Vim plugins are compatible with the multiples versions of Vim for the different OS.
Still YouCompleteMe comports a compiled component so your question is legit to wonder if it will work on different OSes. According to the installation section of the Readme of the project, YCM can be installed on OSX, Linux and FreeBSD with a plugin manager like Vundle. (I really don't know OpenIndiana and it isn't mentioned on the Readme page so I can't say if you'll have a problem with this one)
One point you should take care is that if you update the plugin and the compiled component has changed you'll have to recompile it but it doesn't happen that often and you should get a warning at the update.
TL;DR This shouldn't be an issue to use YCM on most of the common OSes but when updating remember that you might need to recompile the compiled component sometimes.
I would like to try scidb as a replacement for hdf5. I would like to test it on my Debian laptop (no clusters) to give it a try.
Is this possible? Might be that Debian (as opposed to Ubuntu) is not supported?
I had no luck with the installation instructions. The deployment script tells that my OS is not supported. The scidb userguide says about some pre-built packages (for Ubuntu, at least). But there is no hint on how to obtain them.
SciDB is limited to RedHat / CentOS, and to Ubuntu as of the 14.9 release. Folk who want to run it on other distros generally compile from code.
Information about how to obtain the sources (as well as current documentation and community discussion) can be found on the forums here ... http://www.scidb.org/forum/. You'll need to register as a forum user.
Specifically, have a look at http://www.scidb.org/forum/viewtopic.php?f=16&t=364. There's a list of releases and links to code bundles there.
I installed SciDB several times using several ways (building from sources and installing from packages, installing the cluster version and the dev version).
Installation from packages
First, if you choose to install from packages (the easiest and fastest way), SciDB is very very sensitive about your Linux version. For example, for the last version of SciDB (14.8), if you choose to install on a Ubuntu, it has to be a Ubuntu 12.04 (and not a 14.04, a common mistake) 64 bits (meaning you have to install the AMD64 version even if you have an Intel processor). It won't work if you have a different version.
If you have an Ubuntu 12.04 AMD64, Paradigm4 provides a deployment script and a documentation with very simple steps:
https://github.com/Paradigm4/deployment
Installation from sources
It's not so difficult but it can be painful and time consuming. I did it because we had to compile a custom plugin for SciDB. You have two types of installation: dev install (in SciDB user directory) and cluster install (in /opt/ directory).
You have to be registered on their forum to have the link to the source code. They provide a specific documentation to build from source.
Good luck.
Several months ago I have dealt with porting SciDB 14.12 to an unsupported Linux - Fedora 19. If your OS is not supported, it will neither be supported if you try to install from the sources. You have to start from the sources, but then you have to adapt the deployment and installation scripts. The sources can be downloaded from SciDB forum.
Namely, add a new platform to deployment/common/os_detect.sh. Then, there are multiple platform specific deployment scripts, such as deployment/common/prepare_toolchain.sh, deployment/common/prepare_coordinator.sh and deployment/common/prepare_chroot.sh. You need to make sure those prepare the environment as they would on the supported OS'. I used Red Hat 6 and CentOS 6 as a reference, as those are both more similar to Fedora. Since your OS is Debian, you can first try falling back to Ubuntu deployment (in os_detect.sh).
Another problem you may encounter are the 3rd party tools, specially Boost. In my case, I had to build it manually from sources.
Sometimes when porting and debugging it is not convenient to run the scripts with deploy.sh, but it's better to run the deployment scripts directly on the target machine (e.g. coordinator).
Probably the best way to install and to start with SciDB is to download a standard image. With this image you only have to import the virtual machine with a software to virtualize. Moreover there are some characteristics of this virtual machine that are great to develop your first applications.
The main advantage, is that you have an API to SciDB queries and another to R. Then you can explore all options and to test SciDB.
This is the version that I downloaded few months ago: http://www.paradigm4.com/forum/viewtopic.php?f=14&t=1329&sid=606f614e401900cfa750375ba56de656
Nevertheless, there is a problem, the community is too poor. There are little people developing with SciDB.