I am trying to fetch the doc file text using "textract" npm module but for this I have to install one of its dependency "antiword" on heroku
The command I used to install it was:
heroku buildpacks:add https://github.com/ropensci/antiword.git
But antiword is throwing error at the time of extracting text from doc file
error is Error: antiword read of file named [[ 1619419536356test.doc ]] failed: Error: Command failed: antiword -m UTF-8.txt "/app/public/user_files/1619419536356test.doc"
2021-04-26T06:45:38.048275+00:00 app[web.1]: I can't open your mapping file (UTF-8.txt)
2021-04-26T06:45:38.048276+00:00 app[web.1]: It is not in '/app/.antiword' nor in '/usr/share/antiword'.
2021-04-26T06:45:38.048277+00:00 app[web.1]: Name: antiword
Related
I'm trying to upgrade from circleci/ruby:2.7.0-node-browsers to cimg/ruby:2.7-node and I'm getting this error: cannot load such file -- 2.7/ffi_c
Before there weren't any problems with the ruby:2.7.0 image.
I am trying to run the collection-examples-as near example but when I run yarn deploy it gives me the following error
$ near dev-deploy --wasmFile="./contract.wasm"
Starting deployment. Account id: dev-1637744501224-6323200, node:
https://rpc.testnet.near.org, helper: https://helper.testnet.near.org, file:
./contract.wasm
An error occurred
Error: ENOENT: no such file or directory, open './contract.wasm'
[Error: ENOENT: no such file or directory, open './contract.wasm'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: './contract.wasm'
}
error Command failed with exit code 1.
I think the error is it can't find the path to ./contract.wasm so I run yarn build the I tried to deploy it again using yarn deploy but I got another error which is:
$ near dev-deploy --wasmFile="./contract.wasm"
Starting deployment. Account id: dev-1637744501224-6323200, node:
https://rpc.testnet.near.org, helper: https://helper.testnet.near.org, file:
./contract.wasm
An error occurred
Error: Can not sign transactions for account dev-1637744501224-6323200 on network
default, no matching key pair found in
InMemorySigner(MergeKeyStore(UnencryptedFileSystemKeyStore(/home/rasha/.near-
credentials), UnencryptedFileSystemKeyStore(/home/rasha/collection-examples-
as/neardev))).
{
type: 'KeyNotFound',
context: undefined
}
any help or suggestions?
There's an issue with old versions of near-cli and dev-deploy.
As a workaround, you can try running the latest cli directly from your terminal:
near dev-deploy --wasmFile="./contract.wasm" -f
Just check that you installed the latest version of near-cli, currently 2.2.0. You can check your version with near --version.
Be sure to run yarn build first, so you'll have the compiled contract.wasm file.
Note: When you run yarn deploy, it uses the old near-cli version defined in package.json. (probably some old version like 1.6.0)
You might also want to check this GitHub issue (dev-deploy error): https://github.com/near/create-near-app/issues/1408
Im using golangci-lint and getting the following error in CI, any idea what could be the reason? and how can I avoid this.
Our GitHub repo is already have all the vendor packages so it shouldn't install it in first place.
golangci-lint run --config golangci.yml
level=error msg="Running error: context loading failed: failed to load packages: failed to load with go/packages: err: exit
status 1: stderr: go: github.avt.corp/ding/logger-ut#v1.1.0:
unrecognized import path "github.avt.corp/ding/logger-ut" (https
fetch: Get https://github.avt.corp/ding/logger-ut?go-get=1: x509:
certificate signed by unknown authority)\n"
btw I was able to clone the project and run it
Use the following:
run:
modules-download-mode: vendor
or add this to the command you are runnig
--modules-download-mode vendor
I try to upload cookbook with dependencies, here is a log:
[root#redhat cookbooks]# knife cookbook upload reference-app --include-dependencies
Uploading my-cookbook [0.1.0]
Uploading maven [1.2.0]
Uploading hipsnip-jetty [0.9.0]
Uploading ark [0.9.0]
Uploading java [1.29.0]
Uploading windows [1.34.8]
Uploading 7-zip [1.0.2]
Uploading chef_handler [1.1.6]
WARNING: Uploaded 8 cookbooks ok but 2 cookbooks upload failed.
It is all log. Is there a way to sse what cookbook were failed exactly?
Using the verbose flag will show you why it didn't upload correctly.
For instance I added some bad code to the apt cookbook...
[scarman#coldlight cookbooks]$ knife cookbook upload apt --include-dependencies -n -V
Uploading apt [2.6.0]
INFO: Validating ruby files
FATAL: Cookbook file recipes/default.rb has a ruby syntax error:
FATAL: /home/scarman/DevOps/cookbooks/apt/recipes/default.rb:29: `##' is not allowed as an instance variable name
FATAL: /home/scarman/DevOps/cookbooks/apt/recipes/default.rb:29: syntax error, unexpected end-of-input, expecting '('
FATAL: uha897*#S::##!!
FATAL: ^
And also turned my internet off for a moment...
[scarman#coldlight cookbooks]$ knife cookbook upload apt --include-dependencies -n -V
ERROR: Error connecting to https://api.opscode.com/organizations/cls-chef/cookbooks?num_versions=all, retry 1/5
ERROR: Error connecting to https://api.opscode.com/organizations/cls-chef/cookbooks?num_versions=all, retry 2/5
ERROR: Error connecting to https://api.opscode.com/organizations/cls-chef/cookbooks?num_versions=all, retry 3/5
ERROR: Error connecting to https://api.opscode.com/organizations/cls-chef/cookbooks?num_versions=all, retry 4/5
ERROR: Error connecting to https://api.opscode.com/organizations/cls-chef/cookbooks?num_versions=all, retry 5/5
ERROR: Network Error: Error connecting to https://api.opscode.com/organizations/cls-chef/cookbooks?num_versions=all - getaddrinfo: Name or service not known
Check your knife configuration and network settings
That should hopefully provide you with more insight as to why it's failing.
I am new to DocPad, and I was running the KitchenSink demo with no issues.
I then decided to follow the Beginner Guide on the DocPad website (no skeleton), and I am hitting a snag at "Installing the template engine" section.
I got this warning when I tried to run docpad. I get the warning even if I stop DocPad (ctrl+c) and restart it. I am on OSX.
info: Generating...
warning: Failed to load the file: /path-to-project/src/documents/about.html
The error follows:
warning: An error occured:
Unable to parse.
warning: Failed to load the file: /path-to-project/src/documents/index.html
The error follows:
warning: An error occured:
Unable to parse.
Docpad throws this error when there is a malformed yaml file. For me it was a missing space between attribute and value. Instead of
---
keywords: "my keywords"
---
I had
---
keywords:"my keywords"
---