This appears to be fairly recent, but previously if I were to click a folder in the Google Cloud Storage web browser, it would take me to the directory even if there were spaces in the directory. The name of the folders in the breadcrumb navigation are showing up as:
Unknown%20Company
When previously it would have been:
Unknown Company
It seems like this has recently started happening, is there some kind of changelog for the frontend of this application? All the files are still accessible through gsutils if I do something like:
gsutil ls -a gs://bucket-name/Folder\ Name
I've confirmed this is an issue in the GCS UI and is being worked on. I'll post an update here when it has been resolved.
Update: As of 2018-05-08 03:12 PDT, the issue has been resolved.
Related
I am trying to sign the plugin I am working on, but no matter what I have tried it always says grafana is unable to load it because it is “modified”.
I made a brand new backend datasource plugin, ran the basic yarn install and build commands, then the go and mage commands from the readme, then signed it using the docs procedure for the private key, and nothing else. Still says its modified.
Even checked that the hashes of the files in the manifest were the same as what the manifest had, but no matter what it is always marked as modified.
Discovered and fixed the issue. So the issue was with an img/logo.svg path being "", but I couldn’t modify it in the manifest file by hand after the signature process since that would make it invalid. And resigning would make the \ appear again. So the simple fix is removing the img folder and moving the logo.svg to the /src folder with the other files. Made the change in the logo paths set in the src/plugin.json as well. Then when plugin is signed the manifest file just has logo.svg instead of img\logo.svg and it passes and is viewable from grafana dashboard.
Here is a link to the grafana forum post where we went through this issue in more detail: https://community.grafana.com/t/signed-backend-plugin-keeps-throwing-modified-signature-error/39687
I just deployed a setup to a new server and typo3 suddenly can't find files anymore that are present in the file admin. For example I have some textpic that show me that warning.
I can access the files directly via the browser, but the file admin is marking them as missing too. I cleared the caches several times.
Do you have any idea what I could do to restore those file references?
When adding https://www.npmjs.com/package/material-design-icons as a dependency to my Node application, cf push fails with Disk quota exceeded when running npm install. Since the complete application including node_modules has about 100 MB (way below the limit of 1 GB), I assume it might have to do with the fact that material-design-icons has about 86'000 files (for whatever reason).
Is there any workaround for this?
Another solution is to ignore the node_modules directory using the .cfignore file (the same concept as the .gitignore file). The files described in the .cfignore aren't uploaded to Cloud Foundry when you push your app.
You can find more about .cfignore here: https://docs.developer.swisscom.com/apps/deploy-apps/prepare-to-deploy.html#exclude
The solution is to delete the directory node_modules from your app directory before to push it. The description of the needed modules must be in the file package.json under dependencies. I tested a simple express app adding the material-design-icons module. Pushing the application without the content of the directory node_modules works, since in staging the modules are downloaded and added to the application.
The solution is to delete the directory node_modules from your app directory before to push it. The description of the needed modules must be in the file package.json under dependencies. I tested a simple express app adding the material-design-icons module. Pushing the application without the content of the directory node_modules works, since in staging the modules are downloaded and added to the application.
The solution with .cfignore should work. You might need to delete and re-push your app though, since Cloud Foundry caches some files and the container might be filled with these cached files. If you delete and re-push the app, you're getting a clean container from scratch which might solve your problem.
I have faced the same problem. I solved it by doing the following:
Using .cfignore
Specifying the update nodejs in package.json
Using the latest buildpack
As I have assigned to work on magento, according to our requirement i tried to install Arabic extension for magento. The extension got successfully installed. Later on refreshing the admin panel, it shows the URL not found. The Stores FrontEnd CMS home page is loading, But when Iclick on any products, it shows again URL not found..
How can i solve this...
When diagnosing things like this, try the following..
Delete (or move to another folder) files in /var/www/var/cache
Delete (or move to another folder) files in /tmp
From a shell, run
/var/www/shell$ php indexer.php --reindexall
You've just manually cleared your caches and re indexed your data.
See if your system comes back to life.
For me I was redirected to wrong URL from MagentoConnect after installation of extension.
My admin URL: <-hostname->/index.php/admin
Redirected To: <-hostname->/admin
I had same issue when I added extension manually. I could find the issue when checked via shell command and it returned missing table error. This is issue happened when I installed module manually.
I am having a few issues configuring JIRA (Mac OSX 10.6.8), specifically setting my JIRA home directory. I ran the JIRA configuration tool, and defined my path. Upon running JIRA on my localhost, I get the message: No jira.home is configured. Through my terminal, I went in to edit my jira-application.properties files, and it says jira.home = /Applications/MAMP/jira/htdocs. At this point, I am not sure what I am doing wrong, as it seems jira.home is defined. Any help? Thanks.
Have a look at Setting your JIRA Home Directory and make sure you are pointing to the Jira home folder:
Edit the jira-application.properties file and set the value of the 'jira.home'
property to the desired location for your JIRA Home Directory. If you are specifying
this location's path on Windows, use double back-slashes ("\") between subdirectories.
For example, X:\\path\\to\\JIRA\\Home
To find where Jira home is located, have a look at JIRA Installation Directory page, the folder should contain the logs,jss and plugins folders.
So, if for example the Jira is installed at /var/atlassian/application-data/jira , the
jira-application.properties should have the following line:
jira.home = /var/atlassian/application-data/jira
Please note - Jira home directory is referring to a data directory and not the installation directory
Installing Jira on MacOS:
https://confluence.atlassian.com/display/JIRA042/Installing+JIRA+Standalone+on+Mac+OS
NOTE: Setting your Home (aka data) directory to /Applications/MAMP/jira/htdocs means that your Jira installation is located in your MAMP web root... Are you sure that's where Jira is installed? Typically, on a Mac, the home directory is located here:
/Applications/Jira/HOME