Unable to "cf push" into Bluemix, using swift_buildpack 2.0.5 - ibm-cloud

I am no longer able to push my app to Bluemix. I am using the swift_buildback for a Kitura app.
The last time I successfully pushed it, was yesterday. I noticed that the default buildpack is now 2.0.5. The last time I pay attention to that, it was 2.0.4. I don't know how to specify an older version of the buildpack, to rule out a problem there.
The cf push returns the following:
Downloading swift_buildpack...
Downloaded swift_buildpack
Creating container
Successfully created container
Downloading app package...
Downloaded app package (46.5M)
Downloading build artifacts cache...
Downloaded build artifacts cache (43.9M)
Staging...
-----> Buildpack version 2.0.5
-----> Default supported Swift version is 3.1
-----> Configure for apt-get installs...
-----> Writing profile script...
-----> Copying deb files to installation folder...
-----> No Aptfile found.
-----> Getting swift-3.0.2
-----> WARNING: Default supported Swift version: swift-3.1
-----> WARNING: Requested Swift version for your app: swift-3.0.2
Cached swift-3.0.2
-----> Unpacking swift-3.0.2.tar.gz
-----> Getting clang-3.8.0
Cached clang-3.8.0
-----> Unpacking clang-3.8.0.tar.xz
-----> .ssh directory and config file not found.
-----> Loading from cache:
-----> - Packages
-----> Fetching Swift packages and parsing Package.swift files...
-----> Additional packages to download: libcurl4-openssl-dev openssl libssl-dev
-----> libcurl4-openssl-dev is already installed.
-----> openssl is already installed.
-----> libssl-dev is already installed.
-----> No additional packages to download.
-----> Skipping installation of App Management (debug)
-----> Installing system level dependencies...
-----> Installing deb_files
dpkg-deb: error: failed to read archive `deb_files': No such file or directory
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223
Destroying container
FAILED
Error restarting application: BuildpackCompileFailed

In order to verify that your app works with the previous version of the buildpack, just add the -b <buildpack name> flag to your cf push command.
The names of the available buildpacks can be obtained by running cf buildpacks. In this case, since you want the old 2.0.4 buildpack version, the command will look like this:
cf push <app_name> -b swift_buildpack_v2_0_4-20170125-2344
The team that administers the Swift buildpack for Bluemix can help troubleshoot issues like this in their open Slack team - https://swift-at-ibm-slack.mybluemix.net.

Related

No yarnrc.yml even after following directions

This instruction:
`https://devcenter.heroku.com/articles/migrating-to-yarn-2
says to run yarn install and it will create a .yarnrc.yml file. It does not. yarn
install reports no errors and I can run yarn set version berry and I get:
Wed Jun 29 12:43:22 MDT 2022
➤ YN0000: Retrieving https://repo.yarnpkg.com/3.2.1/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-3.2.1.cjs
➤ YN0000: Done in 0s 327ms
I tried yarn set version 2 and then yarn install, but still no joy.
scottc in ~/Sites/vpermits.us on branch main > yarn set version 2
Wed Jun 29 12:44:52 MDT 2022
➤ YN0000: Retrieving https://repo.yarnpkg.com/2.4.3/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-2.4.3.cjs
➤ YN0000: Done in 0s 391ms
My build fails with this error message:
-----> Building on the Heroku-20 stack
-----> Determining which buildpack to use for this app
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
USE_YARN_CACHE=true
NODE_VERBOSE=false
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Build failed
! The 'yarnrc.yml' file is not found
It looks like the 'yarnrc.yml' file is missing from this project. Please
make sure this file is checked into version control and made available to
Heroku.
To generate 'yarnrc.yml', make sure Yarn 2 is installed on your local
machine and set the version in your project directory with:
$ yarn set version berry
Read more at the Yarn docs: https://yarnpkg.com/getting-started/install#per-
project-install
https://devcenter.heroku.com/articles/nodejs-support
! Push rejected, failed to compile Node.js app.
! Push failed`
There is no yarnrc.yml (or .yarnrc.yml) in my directory.

vscode assistance with building cpptools needed

Ubuntu 18.04 ARM64
I have download and built vscode and this appears to be working.
I can see the extension market place and install extensions. The C/C++ IntelliSense, debugging, and code browsing install but gets a dependency install failure sometimes:
Updating C/C++ dependencies...
Downloading package 'Mono Framework Assemblies' (5368 KB) Done!
Installing package 'Mono Framework Assemblies'
Failed at stage: installPackages
Error: end of central directory record signature not found
It seems to succeed on the second attempt but I'm not convinced.
So I have cloned vscode-cpptools and would like to built it myself but I'm not sure what dependencies it has or how to build it correctly.
Any tips appreciated!
So following the build and debug guide at:
$ git clone -b release https://github.com/Microsoft/vscode-cpptools
$ cd vscode-cpptools/Extension
$ npm install ! should install all dependencies but it forgets gulp
$ npm install gulp ! Manually install. I wonder what else it forgets
$ vsce package ! Should trigger the build and make the vsix package.
So the package is created and when I try and install it via the vscode extensions I get
Unable to start the C/C++ language server. IntelliSense features will be disabled. Error: Missing binary at ~/.vscode-oss-dev/extensions/ms-vscode.cpptools-0.22.1/bin/Microsoft.VSCode.CPP.Extension.linux.
Me thinks there are a lot of other dependencies that are missing!!!
Looking in the Extension bin folder and two important binaries are missing:
Microsoft.VSCode.CPP.Extension.linux
Microsoft.VSCode.CPP.IntelliSense.Msvc.linux
I also tried this on Intel Ubuntu 18.04 and while the Intel build appeared to do a whole lot more it also fails to build the binaries.
Found the answer in here : github.com/Microsoft/vscode-cpptools/issues/429 which indicates there is no support for Aaarch64 Arm64 at this point in time.

Heroku push hanging on "fetching gem metadata from rubygems" with no errors or trace of any kind

My deployment is stuck on fetching gem metadata from rubygems every time I deploy.
It worked this morning, had problems this afternoon and now it's not working again.
We tried from somewhere else and from other computers with the same result.
It works fine locally I can update from rubygems without a problem.
Visual:
Delta compression using up to 4 threads.
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 764 bytes, done.
Total 9 (delta 7), reused 0 (delta 0)
-----> Heroku receiving push
-----> Ruby/Rails app detected
-----> Using Ruby version: ruby-1.9.3
-----> Installing dependencies using Bundler version 1.2.1
Running: bundle install --without development:test --path vendor/bundle --binstubs bin/
Updating https://github.com/epetre/negative-captcha.git
Fetching gem metadata from http://rubygems.org/.......
Fetching gem metadata from http://rubygems.org/..
[IT HANGS HERE FOREVER]
Anyone has a clue?
Fixed by adding bundler to the gem file and forcing a version
gem 'bundler', '1.2.1'
Ok, fixed for good I think.
Turns out it only works when explicitly specifying the last versions of heroku and bundler.
The strange thing is that it can bundle without the explicit versions locally but not when deploying to heroku.
gem 'heroku', '2.33.0'
gem 'bundler', '1.2.1'
For me changing the protocol to fetch gem fixed the problem.
I changed https://github.com/epetre/negative-captcha.git to git://github.com/epetre/negative-captcha.git in gem file. Bundled it and pushed to heroku and it works.

Deploy to Heroku Error

I am failing to deploy my first app to Heroku. An error occurred while installing sqlite3 (1.3.6), and Bundler cannot continue.
Make sure that **gem install sqlite3 -v '1.3.6**' succeeds before bundling.
!
! Failed to install gems via Bundler.
!
! Heroku push rejected, failed to compile Ruby/rails app
After the I modified the Gemfile and installed sqlite3 1.3.6 by using the command:
user$ gem install sqlite3 1.3.6
I got:
Building native extensions. This could take a while...
Successfully installed sqlite3-1.3.6
ERROR: Could not find a valid gem ',' (>= 0) in any repository
ERROR: Could not find a valid gem '~>1.3.6' (>= 0) in any repository
1 gem installed
Installing ri documentation for sqlite3-1.3.6...
Installing RDoc documentation for sqlite3-1.3.6.
Just a note, I have deleted the Gemfile.lock but haven't committed the changes. Please help me install the necessary gems to deploy to Heroku

Why does Heroku always find unresolved dependencies?

I haven't installed any gems since the last time I deployed, but
Heroku keeps thinking there is something new I suppose, and that
significantly slows down my deployment time. How can I make sure that
I don't get this message?
EDIT:
This is from my deployment message. I dunno...is it normal?
Writing objects: 100% (13/13), 1.88 KiB, done.
Total 13 (delta 10), reused 0 (delta 0)
-----> Heroku receiving push
-----> Rails app detected
-----> Detected Rails is not set to serve static_assets
Installing rails3_serve_static_assets... done
-----> Gemfile detected, running Bundler version 1.0.7
Unresolved dependencies detected; Installing...
Using --without test:development:staging
Fetching source index for http://rubygems.org/
$ git add Gemfile.lock
$ git commit -m "We should always check in Gemfile.lock in our applications."
$ git push heroku master
I contacted support and they resolved it.