At first I was getting this error on my local build server, but I managed to fix it there... the query is still the same, but gatsby isn't throwing any errors with the query. But every time I try to deploy on Netlify it fails with the following message:
toFormat seems to be empty, we need a fileExtension to set it.
1 | fragment GatsbyContentfulFluid_tracedSVG on ContentfulFluid {
> 2 | tracedSVG
| ^
3 | aspectRatio
4 | src
5 | srcSet
6 | sizes
7 | }
failed during stage 'building site': Build script returned non-zero exit code: 1
8 |
9 | query optbuildreposrccomponentsshopProductsJs2136335468 {
10 | products: allContentfulProduct {
11 | edges {
12 | node {
Shutting down logging, 22 messages pending
File path: /opt/build/repo/src/components/shop/Products.js
Plugin: none
This is the same error I was getting locally and I have no idea why it is occurring. There should be no reason that toFormat is a required parameter. This is using the standard gatsby-source-contentful plugin API request which has always served the image without issue in the past. If I change the request to 'fixed' instead of 'fluid' the problem goes away, but I need fluid images for this part of the site.
I emailed the Netlify staff a few days ago, but am yet to receive a reply. Any help would be greatly appreciated.
For Those who are facing the same issue I came up with a simple solution.
Remove from all your file places that you used this extension _tracedSVG.
eg.
GatsbyContentfulFixed_tracedSVG
to
GatsbyContentfulFixed
Stop your gatsby server and use the follow command:
gatsby clean && gatsby develop
Commit and push your changes (in case you are using Github)
On Netlify find the option: Clear cache and deploy site
It should fix your Deployment on Netlify as well errors on your console :)
Two suggestions:
Local: Double check your content for any image references that do not append a suffix of .png or .jpg
Netlify: Clear cache and deploy site
Related
Is it possible to report on / query the data that is displayed here (red arrows in screen shot below) for individual octopus deployment steps? I have looked at the database schema and their RESTful API but don't see anything. I am trying to generate a report that aggregates time spent for each process across deployments.
The information presented here is calculated from the task log. You can access the task log via the API at /api/{spaceId}/tasks/{taskId}/raw
For example:
| == Success: Step 1: Run a Script ==
01:04:18 Verbose | Run a Script completed
|
| == Success: Worker ==
01:04:12 Verbose | Octopus Server version: 2022.3.425
01:04:12 Verbose | Environment Information:
-- snip ---
01:04:18 Verbose | Successfully finished Run a Script on a Worker
|
From the Task Log view:
There is some examples of interacting with the API for tasks in the OctopusDeploy-Api repo, such as this one to get task details.
The logs around the error is this below. It used to work but after a few days ago, this start failing. I didn't not change deploy flow.
The only change is that we started to pay. Before that we used it as a trial member.
Though I don't think that is the cause...
Does anyone know how to get over this error?
Using app from: /Users/vagrant/deploy/app-production-[REDACTED]-bitrise-signed.apk
Configuration read successfully
Authenticating
Authenticated client created
Create new edit
editID: xxxxxxx
Edit insert created
Upload apks or app bundles
Uploading /Users/vagrant/deploy/app-production-[REDACTED]-bitrise-signed.apk 1/1
Uploaded apk version: 36
Done uploading of 1 apps
New version codes to upload: 36
Applications uploaded
Update track
Release version codes are: [36]
alpha track will be updated.
updated track: alpha
Track updated
Committing edit
Failed to commit edit, error: googleapi: Error 403: You cannot rollout this [REDACTED] because it does not allow any existing users to upgrade to the newly added APKs., forbidden
| |
+---+---------------------------------------------------------------+----------+
| x | google-play-deploy#3.6 (exit code: 1) | 19.44 sec|
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-io/steps-google-play-deploy/issues |
| Source: https://github.com/bitrise-io/steps-google-play-deploy |
+---+---------------------------------------------------------------+----------+
We have several projects in Octopus Deploy Cloud and we have never had issues deploying to the existing targes.
As of today, all deployment steps get skipped with this message in the logs:
Skipping this step as no matching targets were found
This has affected all projects, all channels and all environments (we have five different environments in five different AWS accounts).
== Skipped: Step 1: Create or Update IIS Website == 10:40:29
Verbose | Searched for targets: 10:40:29 Verbose | *
specifically matching these ids: Machines-534 and Machines-535
| * that are enabled
| * with no id exclusions
| * with no environment exclusions
| * has a role that overlaps: APII
| * with no tenant exclusions
| * has a health status of: Healthy or HasWarnings 10:40:29 Info | Skipping this step as no
matching targets were found
The above is part of the raw log.
All deployment targets in the given environment and channel are Healthy (green). Any idea what can be the cause of this?
You have encountered this bug. This issue can be resolved by upgrading to 2019.10.12 or later.
I've installed MEAN.IO as in the instructions here: http://mean.io/#!/docs
Along the lines I did see some errors in the installation process and I had to manually install grunt-cli globally.
When I create a testapp and run grunt then this is my output:
MEAN:~/testApp$ grunt
Running "clean:0" (clean) task
Running "jshint:all" (jshint) task
packages/slack/server/routes/slack.js
2 |var posts = require("../controllers/posts");
^ Strings must use singlequote.
11 | });
^ Missing semicolon.
11 | });
^ Expected an identifier and instead saw ')'.
11 | });
^ Expected an assignment or function call and instead saw an expression.
22 |};
^ Expected '(end)' and instead saw '}'.
14 | app.get('/slack/all', auth.requiresLogin, function(req, res, next){
^ 'app' is not defined.
14 | app.get('/slack/all', auth.requiresLogin, function(req, res, next){
^ 'auth' is not defined.
15 | Slack.render('index', {
^ 'Slack' is not defined.
>> 8 errors in 47 files
Warning: Task "jshint:all" failed. Use --force to continue.
Aborted due to warnings.
What's going wrong here?
For completeness here are my versions:
MEAN:~/testApp$ mean -v && npm -v && node -v
0.5.7
1.4.14
v0.10.29
I am very new to the MEAN.io framework and just install it and got the same error. The simplest way around it seems to be running the following in the root directory of the app.
mean package -d slack
then
mean package slack
Fixed it for me. Seems there was an update 6 hours ago.
Jay is correct. You can see this commit https://github.com/linnovate/mean/commit/433609f295dc4377882998e7e811c9a307bcbe89 that slack has been removed from the project.
You have 3 ways to correct the issue.
git pull upstream master to get the new updates
Do as Jay suggested by removing the slack package
Create a clean project with mean init myApp
I'm new to joomla and I'm configuring my first site, but ended having a problem with the Global Configuration, when I try to save it, i receive a 500 error.
I'm using php internal server to run it, "php -S localhost:8081"... everything else is working fine..
here's the stacktrace, doesn't seem to be a permission error, but i'm not sure.
500 - An error has occurred.
JModel: :getName() : Can't get or parse class name.
Return to Control Panel
Call stack
# Function Location
1 JAdministrator->dispatch() /home/dshiga/dev/joomla_hairs/administrator/index.php:46
2 JComponentHelper::renderComponent() /home/dshiga/dev/joomla_hairs/administrator/includes/application.php:153
3 JComponentHelper::executeComponent() /home/dshiga/dev/joomla_hairs/libraries/joomla/application/component/helper.php:351
4 require_once() /home/dshiga/dev/joomla_hairs/libraries/joomla/application/component/helper.php:383
5 JController->execute() /home/dshiga/dev/joomla_hairs/administrator/components/com_config/config.php:18
6 ConfigControllerApplication->save() /home/dshiga/dev/joomla_hairs/libraries/joomla/application/component/controller.php:761
7 JController->getModel() /home/dshiga/dev/joomla_hairs/administrator/components/com_config/controllers/application.php:55
8 JController->createModel() /home/dshiga/dev/joomla_hairs/libraries/joomla/application/component/controller.php:793
9 JModel::getInstance() /home/dshiga/dev/joomla_hairs/libraries/joomla/application/component/controller.php:599
10 JModel->__construct() /home/dshiga/dev/joomla_hairs/libraries/joomla/application/component/model.php:201
11 JError::raiseError() /home/dshiga/dev/joomla_hairs/libraries/joomla/application/component/model.php:220
12 JError::raise() /home/dshiga/dev/joomla_hairs/libraries/joomla/error/error.php:251
Finally found out, the problem is caused by the use of php internal server through "php -S" command, not sure of exactly what causes the error in this circustances, but hosting the site under apache solved the problem.