Polymer-starter-kit: my-app.html missing from bundled build folder - build

I am using the polymer-starter kit for my app and tried building it. When opening the index.html of the builded app the my-app.html is missing. I didn't change any files in the starter kit, and the problem also appears.
Steps to Reproduce
Create an application project: polymer init --> select polymer-starter-kit
Build: polymer build
Try viewing index.html
This is what I get in the console:
/src/my-app.html Failed to load resource: net::ERR_FILE_NOT_FOUND
webcomponents-loader.js Failed to load resource: net::ERR_FILE_NOT_FOUND
index.html:1 Uncaught (in promise) DOMException: Failed to register a ServiceWorker: The URL protocol of the current origin ('null') is not supported.
/images/favicon.ico Failed to load resource: net::ERR_FILE_NOT_FOUND

Related

Failing to deploy GitHub pages because of write permission

I'm building my website forked from https://github.com/academicpages/academicpages.github.io. During the job setup, the log clearly prints:
GITHUB_TOKEN Permissions:
Contents: read
Metadata: read
Pages: write
But during deployment, it still shows:
Error: Failed to create deployment (status: 403) with build version 9ffb90cf2f2dc3f0730157bdaaf35866ed4b6a35. Ensure GITHUB_TOKEN has permission "pages: write".
I tried building from Actions but that created more errors, so I'm just trying to get build from branch to work.

Fail to deploy project to Google Cloud App Engine Standard

I have a project that has been running fine, but I want to make some changes and solve some bugs so I tried to deploy my app using the Google Cloud SDK (gcloud app deploy)
Services to deploy:
descriptor: [/home/projects/Myproject/app.yaml]
source: [/home/projects/Myproject/]
target project: [my-project]
target service: [default]
target version: [20200902t153320]
target url: [https://my-project.uc.r.appspot.com]
Do you want to continue (Y/n)?
Beginning deployment of service [default]...
╔════════════════════════════════════════════════════════════╗
╠═ Uploading 2 files to Google Cloud Storage ═╣
╚════════════════════════════════════════════════════════════╝
File upload done.
Updating service [default]...failed.
ERROR: (gcloud.app.deploy) Error Response: [9] Cloud build 3ebf37fb-b18d-4c68-b352d-10bd8758f90b0 status: FAILURE
Error type: OK
Full build logs: https://console.cloud.google.com/cloud-build/builds/3ebf37fb-b18d-4c68-b32d-10bd8s78f90b0?project=my-projectid
This used to work yesterday fine but now it gives me this error and I cannot make any changes:
ERROR: build step 6 "us.gcr.io/gae-runtimes/buildpacks/python38/builder:python38_20200816_3_8_5_RC01" failed: step exited with non-zero status: 246
ERROR
Finished Step #6 - "exporter"
Step #6 - "exporter": ERROR: failed to export: failed to write image to the following tags: [us.gcr.io/my-project/app-engine-tmp/app/ttl-2h/default/buildpack-app:latest: GET https://us.gcr.io/v2/token?scope=repository%3Amy-project%2Fapp-engine-tmp%2Fapp%2Fttl-2h%2Fdefault%2Fbuildpack-app%3Apush%2Cpull&scope=repository%3Agae-runtimes%2Fbuildpacks%2Fpython38%2Frun%3Apull&service=us.gcr.io: DENIED: Token exchange failed for project 'my-project'. Access denied.]
Step #6 - "exporter": *** Digest: sha256:bd8121f23cb362683e7c32a8bbdf2a900606373f8edfsdf36fe0ffb17014
Step #6 - "exporter":
Step #6 - "exporter": us.gcr.io/my-project/app-engine-tmp/app/ttl-2h/default/buildpack-app:latest - GET https://us.gcr.io/v2/token?scope=repository%3Amy-project%2Fapp-engine-tmp%2Fapp%2Fttl-2h%2Fdefault%2Fbuildpack-app%3Apush%2Cpull&scope=repository%3Agae-runtimes%2Fbuildpacks%2Fpython38%2Frun%3Apull&service=us.gcr.io: DENIED: Token exchange failed for project 'my-project'. Access denied.
Step #6 - "exporter": *** Images (sha256:bd8121f23cb362683e7c32adfssd73f8ea51326f36fe0ffb17014):
I tried changing my authentication, so i used gcloud auth revoke and gcloud app login to refresh them. I also deleted the files in the storage and loaded them again. I even tried to upload the code to GitHub and make the deployment from there using an activator. Noting seems to work out.
The project has all the permissions. The service accounts are enabled. And I just don't understand what is wrong. I am not using Docker, so I did not change any of the default configurations in the Standard app engine
I have faced this recently.
Billing is not always the issue. Sometimes if there are no changes going in and you are trying to deploy the same version again, creates this problem as well.
Two Workarounds (not solutions)
Use a random versioning scheme instead of --version SOME_STATIC_VALUE
Ensure that there are some changes in the code getting deployed.
I ran into the same issue until running other GCP commands lead to the conclusion (for me) that GCP refused to deploy because there was no billing account associated with my project. App Engine and the logs did not tell me about it and just told me about some docker push issues. Try checking to see if you have an active billing account set up and if there's any issues with that billing account.
Linking a billing account solved the issue for me and I was able to deploy my stuff fine using App Engine.

Expo builds locally, won’t publish

I have my un-ejected expo app up and running and I've managed to build and run it successfully locally on both android and iOS without errors. However, when I try to publish the app I get the unable to resolve module error.
Here's the full error:
[exp] Failed building JavaScript bundle.
[exp] Unable to resolve module `BikeShare/theme/components` from `/Users/gdaunton/Projects/BikeShare/App.js`: Module does not exist in the module map
[exp]
[exp] This might be related to https://github.com/facebook/react-native/issues/4968
[exp] To resolve try the following:
[exp] 1. Clear watchman watches: `watchman watch-del-all`.
[exp] 2. Delete the `node_modules` folder: `rm -rf node_modules && npm install`.
[exp] 3. Reset packager cache: `rm -fr $TMPDIR/react-*` or `npm start -- --reset-cache`.
[exp] Packager URL http://localhost:19001/node_modules/expo/AppEntry.bundle?dev=false&minify=true&hot=false&assetPlugin=/Users/gdaunton/Projects/BikeShare/node_modules/expo/tools/hashAssetFiles&platform=ios returned unexpected code 500. Please open your project in the Expo app and see if there are any errors. Also scroll up and make sure there were no errors or warnings when opening your project.
Basically I have a a setup like this:
BikeShare
- static
- js
- theme
- components
- index.js
- App.js
and a .babelrc with:
["module-alias", [
{ "src": "./static/js", "expose": "BikeShare" }
]]
I found out that it was because I had aliases that branched off of my main alias (i.e. BikeShare/img). I had to switch all of those to be namespaced separately (just img/). I also switched to using module-resolver instead of module-alias since that was recommended in a few places.

404 Page not found while deploying MicroStrategy Web sample

I am a newbie to MicroStrategy. I have managed to install MicroStrategy and Install the sample (MSTR-SDK/samples/javaExternalSecuritySample) in MicroStrategy Root directory /web aspx/plugin directory.
I am still getting below error when I launch the MicrosStrategy web tool.
HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
How do I fix this?
Can you browse to the file on your webserver at the location indicated (inetpub\wwwroot\plugins\ESM\JSP\mstrWeb.jsp) ?

Failed to stage application, with error code 170001

App deployment into Pivotal Cloud Foundry is failing. Find below staging error log. I am guessing download of buildpack could be failing.
log of 'cf push' command:
Creating app gs-serving-web-content in org DEV / space Project-1 as abc.xyz...
OK
Creating route gs-serving-web-content.cf.myorg.com...
OK
Binding gs-serving-web-content.cf.myorg.com to gs-serving-web-content...
OK
Uploading gs-serving-web-content...
Uploading app files from: gs-serving-web-content-0.1.0.jar
Uploading 546.7K, 89 files
Done uploading
OK
Starting app gs-serving-web-content in org DEV / space Project-1 as abc.xyz...
FAILED
Server error, status code: 400, error code: 170001, message: Staging error: failed to stage application:
Error downloading: Response status: unknown, Error: Errno::ECONNREFUSED
Try to check if enough stagers are there. I believe its a memory issue. just try to increase memory in you cf instance.