I am Creating snippet extention of react-native for VS-code. In that I want to add some images into README.md file, which finally show images on marketplace inside description tab of my extention.
I have tried below things in README.md but it gives me error:
ERROR Couldn't detect the repository where this extension is published. The image '/images/SnippetDemo1.png' will be broken in README.md. GitHub/GitLab repositories will be automatically detected. Otherwise, please provide the repository URL in package.json or use the --baseContentUrl and --baseImagesUrl options.
Related
PLEASE HELP((( I keep getting this error for 10000years now. Google says its because of gradle-wrapper.jar is missing, but here it is at my project.
What should I do?Where in the windows directory should gradle wrapper be? OR how to install gradle wrapper properly by hand with command promt? I tried to do it and i did it, but Im not sure if i did it right. Ive done gradle init, randomle selected options, after gradle init inside that directory what was created after gradle init, i ran gradle wrapper, and ive got this gradle-wrapper folder, it didnt help.
enter image description hereenter image description hereenter image description hereenter image description here
I have a google cloud function that is a subdirectory in a repository. It uses the "Directory with source code" option in the settings menu. I keep getting this error on deploy:
Deployment failure:
Build failed: go: parsing /utils/pubsub/go.mod: open /utils/pubsub/go.mod: no such file or directory
go: error loading module requirements
I'm assuming that GCF does not upload the entire directory to the instance, but instead only the folder? This breaks the replace functionality of Go modules. Is there something I am doing wrong?
Link to the repo: https://github.com/FreekingDean/jeffbotgo/tree/5d735cc/slackevent
I work at Google and on this product.
Only the directory where you run gcloud is uploaded. There is no staging step beyond zipping the current directory and uploading it.
Notably, modules are preferred by the builder over vendor. If there is a go.mod, modules will be used. When you upload your function, it only includes the directory with your function at the root, not any directories one level up. So, when there is a go.mod and you have a replace directive pointing one level up, it will not work.
The solution for now with this layout is to vendor and not upload the go.mod/go.sum files. When using gcloud, you can create a .gcloudignore file to do this for you. See https://cloud.google.com/functions/docs/concepts/go-runtime#specifying_dependencies for more detail. Alternatively, modify your project to include any necessary helper packages in subdirectories.
I had the same issue today.
When reading thru the documentation for the 8th time i came across a warning box bellow the "Vendor directory" headline.
Warning: If your project has both a go.mod file and a vendor directory
at the root of your project, the vendor directory will be ignored
during deployment. You must use a .gcloudignore file to ignore the
go.mod file in order to ensure that your vendor directory is used
during deployment.
So basically once i added a .gcloudignore file with go.mod (will add go.sum as well) everything worked. So i guess if you have a go.mod file the cloud function will try to fetch dependencies instead of using the ones uploaded in the vendor folder.
I'm just guessing here tough.
I had downloaded CKEDITOR version 4.5.5 and used the online CKBUILDER tool to remove the plugins not required. Now I need to add one more plugin - 'clipboard', to do so I am following the steps mentioned below:
git clone https://github.com/ckeditor/ckeditor-dev.git branch 4.5.x
copy pasted the build-config.js file from my downloaded version and added one plugin to the plugin list
edited build.sh from VERSION="4.5.11 dev" to VERSION="4.5.5"
ran build.sh
I still see all the plugins getting generated in release/ckeditor folder. But the excluded plugins are not built with ckeditor.js file. Thus I have only copied 'clipboard' plugin folder, ckeditor.js file and the lang folder. Does this seem correct or shall I copy all the previous plugins too?
Is my approach correct to get the correct version build by changing the VERSION variable to 4.5.5?
I have created a new version of my Joomla extension.
Manual upgrade via zip file or the directory works fine.
But the automatic upgrade (which used to work fine before), now gives an error 500 and the following error messages: "Unknown Archive type", "*Update path does not exist" and "Installation unexpectedly terminated: Update path does not exist".
I have no idea why those messages appear.
The update.xml references the correct zip files. Downloading it manually works just fine.
Joomla(/php/apache) has all rights on the folder containing the joomla installation.
After trying the automatic update, the tmp folder contains the downloaded zip archive with the latest extension version, interestingly without the .zip extension. Is the Joomla downloader not correctly naming the file and then failing upon finding that the file doesn't have a .zip extension?`Or what could it be?
Would be very thankful for any ideas...
Edit: My project is hosted on github, and github seems to automatically create a subfolder in the downloaded zip archive, named -.zip.
I'm using a link to the tagged github zip directly in my update.xml
I'm not sure if github always added this folder in the zip file, back when it still worked for me...
Might the Joomla problem have to do with the zip file containng such a folder, and not directly the extension stuff at root level? If so, anybody know if/how I can change github to not create that subfolder?
Right, just had a quick test of this.
I couldn't seem to find out how to automatically zip up a sub folder (there is a way but I need to do some more research/ask questions regarding this), however what you can do is the following:
Create a zip of your Repo
Open the zip, extract the folder you wish to be zipped then zip it
Create a new version and then drag your zip file into the upload box
Publish the release
Here is an example, have a look at the "Creating Releases" sections at the bottom:
https://github.com/blog/1547-release-your-software
Hope this helps
To answer my own question:
Yes, github seems to have recently changed their policy to create a root folder in the zip file, named as the repository the zip file is downloaded for (stupid, if you ask me, since the exact same information is encoded in the zip file name already anyway!).
Edit and Rewrite: It seems that either something changed in Joomla or that if you adhere to a naming convention - namely the root folder in the zip file having the exact extension name (or, I think and have to test, actually the same as the file name, without the version information), then the automatic update will work.
So as in my case, I have a Joomla package; the package is now in a repository pkg_mypkg. The zip file generated by github has the name pkg_mypkg-version.zip (e.g. pkg_myfancyext-1.0.9.zip), and contains a folder named pkg_mypkg. And inside the pkg_mypkg folder is a pkg_mypkg.xml file, the extension manifest. And this actually seems to be the configuration where automatic update works.
I see that Fossil UI allows the downloading of files ("artifacts") at the url /raw/directory/filename?name=artifactID. Is there a way to always get the latest version of the file without knowing the artifactID? I have tried ?name=trunk, ?name=current, ?name=, and ?name=tip. The only result I have gotten is to be returned to the homepage of the repository or given a text file with a listing of files in the repository. I also tried /doc/directory/filename, but that just gives me the contents of the file as a webpage, as intended.
For background, I have a script I would like to download without cloning the repository, but I would like a "permalink" to the latest version of the file.
What you are looking for is described here:
http://fossil-scm.hwaci.com/fossil/doc/trunk/www/embeddeddoc.wiki
In short, you would write <baseurl>/doc/tip/<filename>
you can read <filename> above to be the path to your file, exactly as it is shown after "file" in the artifact content page. In other words: through the UI you go to "files" and navigate the the files you want link to. Once you are at the file, the header of the page will be "Artifact Content" and show you the as a full path after "File" (right at the top, after the artifact ID)