Having problem deploying github repository to heoku - swift

Trying to deploy this repository to heoku using the deploy to heroku button.
https://github.com/abdulkhaliq92/FaxServer
I have a valid app.json file:
{
"name": "FaxServer",
"scripts": {},
"env": {},
"formation": {},
"addons": [],
"buildpacks": [
{
"url": "https://github.com/kylef/heroku-buildpack-swift"
}
]
}
The following error occurs while deploying.
Downloading swift-corelibs-libdispatch (swift-4.1-RELEASE)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 --:--:-- --:--:-- --:--:-- 1729k
Building Swift
This may take a very long time...
Building Swift failed
Check out the logfile for more information: /app/tmp/cache/swiftenv/tmp/swiftenv-build-4.1/swiftenv-build.20190214170118.272.log
You can inspect or delete the working tree at: /app/tmp/cache/swiftenv/tmp/swiftenv-build-4.1
! Push rejected, failed to compile Swift app.
! Push failed
EDIT:
Still getting the same error.
Here is the Package.swift file : https://github.com/abdulkhaliq92/FaxServer/blob/master/Package.swift

Related

Citus installation failing on GCP

After installing postgresql(13) on GCP, I tried installing citus using this command:
curl https://install.citusdata.com/community/rpm.sh | sudo bash
However I run into the following error. Any guidance/suggestions would be helpful.
[tony_stark#host]$ curl https://install.citusdata.com/community/rpm.sh | sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 8667 100 8667 0 0 21791 0 --:--:-- --:--:-- --:--:-- 21831
Detected operating system as centos/7.
Checking for curl...
Detected curl...
Checking for postgresql13-server...
Detected postgresql13-server...
Checking for EPEL repositories...
Detected EPEL repoitories
Downloading repository file: https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script...
curl: (7) Failed to connect to
Network is unreachable
Unable to run:
curl https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script
The link curl https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script works on my browser though.
Looks like a temporary issue on repository side. I just tried it and it works:
[sergiusz#host ~]$ curl https://install.citusdata.com/community/rpm.sh | sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 8667 100 8667 0 0 25686 0 --:--:-- --:--:-- --:--:-- 25718
Detected operating system as centos/7.
Checking for curl...
Detected curl...
Checking for postgresql13-server...
Installing pgdg13 repo... done.
Checking for EPEL repositories...
Detected EPEL repoitories
Downloading repository file: https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script.
.. done.
Installing pygpgme to verify GPG signatures... done.
Installing yum-utils... done.
Generating yum cache for citusdata_community... done.
The repository is set up! You can now install packages.
EDIT:
This file can be also downloaded manually:
curl "https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script" -o /etc/yum.repos.d/citusdata_community.repo

Error when uploading a large number of files to FireBase Hosting

I'm trying to upload 19,941 files weighing 222 MB to FireBase Hosting. I log in as usual with firebase login, then initialize firebase init and deploy firebase deploy. But when deploying, an error occurs:
=== Deploying to 'wowonder-b514c'...
i deploying hosting
i hosting[wowonder-b514c]: beginning deploy...
i hosting[wowonder-b514c]: found 19760 files in public
⠹ hosting: adding files to version [16000/19760] (80%)
Error: Task index 10 failed: retries exhausted after 4 attempts, with error: Failed to make request to https://firebasehosting.googleapis.com/v1beta1/sites/wowonder-b514c/versions/9b27e5663b5d8853:populateFiles
Error: Task index 10 failed: retries exhausted after 4 attempts, with error: Failed to make request to https://firebasehosting.googleapis.com/v1beta1/sites/wowonder-b514c/versions/9b27e5663b5d8853:populateFiles
firebase.json:
{
"hosting": {
"public": "public",
"ignore": [
"firebase.json",
"**/.*",
"**/node_modules/**"
]
}
}

"Building flutter tool..." takes forever

Due to some Android Studio problem, I invalidated flutter cache.
When I try flutter upgrade, I'm stuck with the "Building flutter tool ..." phase
$ flutter upgrade
Downloading Dart SDK from Flutter engine beb8a7ec48f6b980a778d19eeda613635c3897c9...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 16 100 16 0 0 25 0 --:--:-- --:--:-- --:--:-- 25
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
Throwing away 16 bytes
100 219M 100 219M 0 0 6082k 0 0:00:37 0:00:37 --:--:-- 6324k
Building flutter tool...
There is no verbose log either, after I tried -v.
Now flutter doctor is stuck at the same place.
What should I do?
Solved. Seems a network issue. I'm located in China. Had to use StealthVPN with https://pub.flutter-io.cn as the host URL to finish the building. None of the other local mirrors work, which require no StealthVPN.
It's super weird that I can download the Dart SDK from ALL the mirrors but only one of them can complete the "building".
There really should be a clear warning and detailed progress report. It's hard to imagine "building ..." involving internet access.

Logstash-Forwader 3.1 state file .logstash-forwarder not updating

I am having an issue with Logstash-forwarder 3.1.1 on Centos 6.5 where the state file /.logstash-forwarder is not updating as information is sent to Logstash.
I have found as activity is logged by logstash-forwarder the corresponding offset is not recorded in /.logstash-forwarder 'logrotate' file. The ./logstash-forwarder file is being recreated each time 100 events are recorded but not updated with data. I know the file has been recreated because I changed permissions to test, and permissions are reset each time.
Below are my configurations (With some actual data italicized/scrubbed):
Logstash-forwarder 3.1.1
Centos 6.5
/etc/logstash-forwarder
Note that the "paths" key does contain wildcards
{
"network": {
"servers": [ "*server*:*port*" ],
"timeout": 15,
"ssl ca": "/*path*/logstash-forwarder.crt"
},
"files": [
{
"paths": [
"/a/b/tomcat-*-*/logs/catalina.out"
],
"fields": { "type": "apache", "time_zone": "EST" }
}
]
}
Per logstash instructions for Centos 6.5 I have configured the LOGSTASH_FORWARDER_OPTIONS value so it looks like the following:
LOGSTASH_FORWARDER_OPTIONS="-config /etc/logstash-forwarder -spool-size 100"
Below is the resting state of the /.logstash-forwarder logrotate file:
{"/a/b/tomcat-set-1/logs/catalina.out":{"source":"/a/b/tomcat-set-1/logs/catalina.out","offset":433564,"inode":*number1*,"device":*number2*},"/a/b/tomcat-set-2/logs/catalina.out":{"source":"/a/b/tomcat-set-2/logs/catalina.out","offset":18782151,"inode":*number3*,"device":*number4*}}
There are two sets of logs that this is capturing. The offset has stayed the same for 20 minutes while activities have been occurred and sent over to Logstash.
Can anyone give me any advice on how to fix this problem whether it be a configuration setting I missed or a bug?
Thank you!
After more research I found it was announced that Filebeats is the preferred forwarder of choice now. I even found a post by the owner of Logstash-Forwarder that the program is full of bugs and is not fully supported any more.
I have instead moved to Centos7 using the latest version of the ELK stack, using Filbeats as the forwarder. Things are going much smoother now!

Knife-solo prepare fails

I'm trying to configure a fresh CentOS 6.5 x64 node via knife-solo. But when I run knife solo prepare root#centos I get a strange error.
Bootstrapping Chef...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15934 100 15934 0 0 36862 0 --:--:-- --:--:-- --:--:-- 95413
Downloading Chef 11.14.0.alpha.2 for el...
downloading https://www.opscode.com/chef/metadata?v=11.14.0.alpha.2&prerelease=false&nightlies=false&p=el&pv=6&m=x86_64
to file /tmp/install.sh.1750/metadata.txt
trying curl...
ERROR 404
Unable to retrieve a valid package!
Please file a bug report at http://tickets.opscode.com
Project: Chef
Component: Packages
Label: Omnibus
Version: 11.14.0.alpha.2
Please detail your operating system type, version and any other relevant details
Metadata URL: https://www.opscode.com/chef/metadata?v=11.14.0.alpha.2&prerelease=false&nightlies=false&p=el&pv=6&m=x86_64
When I try to debug that thing and run knife solo prepare -VV root#centos I get this: https://gist.github.com/Almaron/5709a69e09bad92f3475
I've tried to google it and found that it might be a proxy issue, but I have not set up any proxies what so ever.
UPDATE
Tried running knife solo prepare root#centos--bootstrap-version 11.12.0
Here's the result: https://gist.github.com/Almaron/2f7987f314132c80b8ed
Had the same problem. It seems there is a problem on the opscode site with version 11.14.0.alpha.2 - the http code returned is 404 Not Found.
A solution is to pin the chef version when preparing knife solo:
knife solo prepare root#centos --bootstrap-version 11.12.0