Trouble with installing the package telescope-posts - bash

I am trying to get rid of the character/text limit which is found in the package https://github.com/TelescopeJS/Telescope/tree/master/packages/telescope-posts.
I tried just doing "meteor add telescope-posts" but I received the error:
=> Errors while parsing arguments:
While adding package telescope-posts:
error: no such package
I then tried to create a package but when I enter ".meteor/packages" or "myProjectName/.meteor/packages" I receive:
-bash: .meteor/packages: Permission denied
Any help on how to install the package telescope-posts is greatly appreciated. Thank you.


Have you tried this:
meteor add telescope:posts
More likely, you should look at: https://telescope.readme.io/v0.20/docs/installing-telescope

Related

getting error while using webview_windows package only for windows in flutter

last few days before this package is working fine but now its not working. Getting some error like environment creating failed.
https://github.com/jnschulze/flutter-webview-windows/issues/198
Thank you

Yarn add - Private package - 404 Not Found

I want to install a private package hosted on an internal Gitlab with Yarn.
So, I configured my .npmrc with this informations :
#mypackage:registry=https://gitlab.intra/api/v4/packages/npm/
//gitlab.intra/api/v4/projects/819/packages/npm/:_authToken=xxxxx
//gitlab.intra/api/v4/packages/npm/:_authToken=xxxxx
always-auth=true
When I attempt to install the package with yarn add #mypackage/lib-node-client, Yarn give me an error :
Trace:
Error: https://gitlab.intra/api/v4/projects/725/packages/npm/#mypackage/lib-node-common/-/#mypackage/lib-node-common-21.7.1.tgz: Request failed "404 Not Found"
at ResponseError.ExtendableBuiltin (/usr/lib/node_modules/yarn/lib/cli.js:696:66)
at new ResponseError (/usr/lib/node_modules/yarn/lib/cli.js:802:124)
at Request.<anonymous> (/usr/lib/node_modules/yarn/lib/cli.js:67062:16)
at Request.emit (node:events:369:20)
at Request.module.exports.Request.onRequestResponse (/usr/lib/node_modules/yarn/lib/cli.js:141640:10)
at ClientRequest.emit (node:events:369:20)
at HTTPParser.parserOnIncomingClient (node:_http_client:646:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:129:17)
at HTTPParser.execute (<anonymous>)
at TLSSocket.socketOnData (node:_http_client:512:22)
So, Yarn can't find the URL : https://gitlab.intra/api/v4/projects/725/packages/npm/#mypackage/lib-node-common/-/#mypackage/lib-node-common-21.7.1.tgz
If I try to get this on my browser, I can download the package...
If anyone can help me please, thank's for all :)

In your .npmrc file, you tell how to connect to GitLab for the project 819. The error is about the project 725. GitLab simply refuse the connexion.
Try with
#mypackage:registry=https://gitlab.intra/api/v4/packages/npm/
//gitlab.intra/api/v4/projects/725/packages/npm/:_authToken=xxxxx
//gitlab.intra/api/v4/projects/819/packages/npm/:_authToken=xxxxx
//gitlab.intra/api/v4/packages/npm/:_authToken=xxxxx
always-auth=true

We had a gitlab private package registry, and was constantly getting this error.
npm i #placeholder/package-name works fine, but yarn add #placeholder/package-name was giving 404 errors.
I tried all possible solutions listed on this thread. At last, there was a section in gitlab on troubleshooting yarn installation [1].
It said,
try adding this to your .npmrc file (and replace <your_token> with your personal access token or deploy token):
//gitlab.example.com/api/v4/projects/:_authToken=<your_token>
Our previous .npmrc looked like this
save-exact=true
unsafe-perm=true
#placeholder:registry=https://gitlab.com/api/v4/packages/npm/
//gitlab.com/api/v4/packages/npm/:_authToken=${PLACEHOLDER_TOKEN}
With the above new line addition, it looked like this,
save-exact=true
unsafe-perm=true
#placeholder:registry=https://gitlab.com/api/v4/packages/npm/
//gitlab.com/api/v4/packages/npm/:_authToken=${PLACEHOLDER_TOKEN}
//gitlab.com/api/v4/projects/:_authToken=${PLACEHOLDER_TOKEN}
With that addition, yarn add #placeholder/package-name worked fine.
[1] https://docs.gitlab.com/ee/user/packages/npm_registry/#error-running-yarn-with-the-package-registry-for-npm-registry

This should be the accepted answer. //gitlab.com/api/v4/projects/:_authToken=${PLACEHOLDER_TOKEN} Was the piece I was missing, which supercedes needing to list each project id as in Joel's answer.

Failed to start JFrog Open Source artifactory on Mac OS

I am trying to set-up JFrog OSS on mac-os. I followed all the instructions listed on the below installation page:
https://www.jfrog.com/confluence/display/JFROG/Installing+Artifactory#InstallingArtifactory-Mac(Darwin)Installation
But on starting the artifactory using command $JFROG_HOME/artifactory/app/bin/artifactoryctl as mentioned in Step-5 of above link, below error is appearing. Any clue of the fix?
$ $JFROG_HOME/artifactory/app/bin/artifactoryctl
/opt/jfrog/artifactory/app/bin/installerCommon.sh: line 2850: syntax error near unexpected token `>'
/opt/jfrog/artifactory/app/bin/installerCommon.sh: line 2850: ` JF_PRODUCT_HOME=${homeDir} ${VALIDATE_BINARY} run ${DIAGNOSTICSYAMLFILEPATH} &>>$SYSTEM_DIAGNOSTICS_LOG_FILE'
[ERROR] Unable to source /opt/jfrog/artifactory/app/bin/installerCommon.sh, please check if the adnansohail user has permissions to perform this action

Thanks for raising this. This is found and fixed in Artifactory 7.12. Please upgrade the version and try out.

Error: package or namespace load failed for ‘xgboost’

I keep getting this error even though I've already installed the xgboost package. I tried the following code and it keep saying the same when I run library(xgboost). Anyone has any idea?
I've already tried this code and it keep saying the same thing:
remove.packages("xgboost")
install.packages('xgboost', dependencies = TRUE)
Thanks in advance!

MAC go get github.com/go-gl/gl

On MAC i am trying to setup GO-GL, but when i run
go get github.com/go-gl/gl
I get the following error:
In file included from src/github.com/go-gl/gl/attriblocation.go:7:./gl.h:2:10: fatal error: 'GL/glew.h' file not found
Someone please help me figure this out!

Unless you have a good reason not to, you should use go-gl/glow package instead of go-gl/gl. It will provide you and your users with a better experience.
https://github.com/go-gl/glow#glow

Resources