Can't build web_app #46
Comments
|
I think the error you're looking for is: "ERROR: /private/var/tmp/_bazel_da_allgeier/b8fe2dfec5c3e6f1134b315cf0fed080/external/local_config_cc/BUILD:55:5: in apple_cc_toolchain rule @local_config_cc//:cc-compiler-armeabi-v7a: Xcode version must be specified to use an Apple CROSSTOOL. If your Xcode version has changed recently, try: "bazel clean --expunge" to re-run Xcode configuration" To me it sounds like your Xcode config/setup is incompatible. I've only ever done deployments from Linux (Debian/Ubuntu). Doing a search for this has landed a potential solution, though: Can you try running the following: Steps from: https://stackoverflow.com/questions/45276830/xcode-version-must-be-specified-to-use-an-apple-crosstool |
|
Thank you for your help. After running your suggestions I now get the following outputs: Their is still no App Engine Project deployed. Am I "just" missing the Thank you again for your help! |
|
Been a while since I deployed but I looked through my notes and I see I
encountered the same issue. This is my note on the resolution I took:
Copy the bazel-bin folder contents over into the new bazel-bin folder
So, it sounds like it's just missing the file.
…On Mon, Apr 15, 2019 at 3:01 PM Dominik Kugelmann ***@***.***> wrote:
Hi @helfrichmichael <https://github.com/helfrichmichael>
Thank you for your help.
After running your suggestions I now get the following outputs:
~/D/loaner> bash loaner/deployments/deploy.sh web prod
INFO: Checking for gcloud on PATH and version...
SUCCESS: gcloud was found on PATH and is at or above the minimum version.
INFO: Checking for bazel on PATH and version...
SUCCESS: bazel was found on PATH and is at or above the minimum version.
INFO: Checking for npm on PATH and version...
SUCCESS: npm was found on PATH and is at or above the minimum version.
INFO: Checking gcloud authentication...
INFO: Going to the loaner directory...
INFO: Initiating the build of the python deployment script...
INFO: Analysed target //loaner/deployments:deploy_impl (0 packages loaded,
0 targets configured).
INFO: Found 1 target...
Target //loaner/deployments:deploy_impl up-to-date:
bazel-out/darwin-py3-fastbuild/bin/loaner/deployments/deploy_impl
INFO: Elapsed time: 0.443s, Critical Path: 0.01s
INFO: 0 processes.
INFO: Build completed successfully, 1 total action
*loaner/deployments/deploy.sh: line 248:
../bazel-out/k8-py3-fastbuild/bin/loaner/deployments/deploy_impl: No such
file or directory*
Their is still no App Engine Project deployed. Am I "just" missing the
deploy_impl file and shall I re download the file OR am I still doing
something wrong?
Thank you again for your help!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#46 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Asw-8ox5XOdH_Y0NU-v-LetKpXfCkRpDks5vhMyBgaJpZM4ct_Xf>
.
--
David Aulick
Promevo | Customer Engineer
david.aulick@promevo.com | promevo.com (888) 380-1061 x733
|
|
Can you share what folders exist in your ../bazel-out/* directory? I'm guessing that there's a mismatch between the output directory on Linux vs. Mac OS, but not 100% sure. Additionally, which version of bazel are you running?
Should provide the version. |
|
Should I be trying the bazel clean - expunge with my build issue too? (Sorry, I don't mean to hijack). I'm Linux. |
|
@templesnr for your issue, I haven't had a ton of time to dive into it. We're working internally on getting the package.json updated in coming pushes, but I have no ETA on when that will happen. The problem is that finding the right dependencies can be tricky. You could look into using NCU (https://www.npmjs.com/package/npm-check-updates) to update the packages, but know that you will likely still need to make modifications to support other dependencies. |
|
So I am running bazel v.0.24.1 And this is the output I am getting from ../bazel-out/* |
|
Upon inspection of the output I saw that I needed to change line 248 in I think this started the process of building the web_app. Sadly it still spit out the following errors. I've also edited the tomorrow I will setup a new config.ts as it is still sending out more and more errors... I will get their -- somehow... |
|
You're so close! My recommendation would be to go to backup the config.ts and pull a fresh copy and reconfigure if possible just to make sure nothing is out-of-place. As for the deploy_impl issue, that's likely a bug that we'll need to look into at some point since it seems we have two different behaviors now depending on the OS (Linux vs. Mac OS). |
|
Thank you so much @helfrichmichael! So the new config.ts doesn't make issues - I think. Now I am stuck again... Changing the username from |
|
It looks like the issue is that your username has a underscore which is a forbidden character for the versioning. You can do the following:
OR
|
|
Changing the user name worked - and I really wanted to change it anyway :D So now I have the following error (I am losing my mind 🤯).. |
|
That's likely my fault since I didn't test against a Mac OS device when I made the upgrade to our deploy_impl script due to some dependencies needing upgrading/dir name changes. In your bazel output directory (./bazel-loaner/external/), can you tell me if you have a folder resembling the following name? "com_google_appengine_python" Or anything similar to that? Depending on what your appengine python package is, you need to adjust the deploy_impl script to remove that folder before deployment at the following line: https://github.com/google/loaner/blob/master/loaner/deployments/deploy_impl.py#L295 |
|
I am seeing the com_google_appengine_py folder. How do I remove that folder on this line? |
|
In your local deploy_impl script, is it targetting com_google_appengine_py or com_google_appengine_python? The script will prevent dependencies such as these from being pushed to GCP. |
|
It is targeting com_google_appengine_python. So I just change it to com_google_appengine_py? |
|
yeah. that worked. |
|
Yeah, there were some changes with Bazel dependencies that caused the folder structure to change. The latest push to master/HEAD includes these changes for what it's worth. |
|
Good to know. So the app engine is deployed now. I can see all 4 services. When going to .appspot.com I now get an internal server error... 🙈 I am losing my patients now... Next time make a pro to do this... Anyway here is the page output: What can I do to fix this? Additionally I can see the following error in a cron job:
|
|
@daallgeier Did you add the service account to the Technical Admins group? You can do this by copying the email address for the service account IAM & Admin > Service Accounts and adding it to the technical_admins group you made within the Chrome Management console. |
|
@scassidy01 I have just now and then rebuild - it still won't work... 😕 |
|
Ensure you have the correct Client ID listed in the admin console. The
Client ID of the GCP service account needs to be added the Scopes section
of the Admin Console (*admin.google.com <http://admin.google.com> >Security
Manage Client API Access*).
The service account in question is the one mentioned in step 2v of the
setup Guide. The step 2iii. Client ID does is* not *the correct Client ID to
be added to the admin console.
https://github.com/google/loaner/blob/master/docs/setup_guide.md#prerequisites
If it's not that, ensure the Application Type is set to Public, as
mentioned in step iv above.
…On Wed, Apr 24, 2019 at 1:42 PM Dominik Kugelmann ***@***.***> wrote:
@scassidy01 <https://github.com/scassidy01> I have just now and then
rebuild - it still won't work... 😕
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#46 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALGD54XUTULF3K7HGTTJ4UTPSCLZBANCNFSM4HFX6XPQ>
.
--
David Aulick
Promevo | Customer Engineer
david.aulick@promevo.com | promevo.com (888) 380-1061 x733
|
|
Hello all, I'm getting this error:
Do you have any idea? Thanks |
|
Hi, I have fixed my error, just opening the file: py_appengine.bzl, that is located in this folder: /home/gng2/.cache/bazel/_bazel_gng2/65a9a5e69e2d406d9df52991805e9eda/external/io_bazel_rules_appengine/appengine and editing the row: 165: Kind regards! |
|
You can also juse the Bazel Version 0.24.0 for anyone else running into this issue Will not work with newer versions. Run the following versions: Uninstall the version you have: Installing Bazel Then Run the installation: Check your version You can now even go into the web app folder and check the build processes with |
|
For those on macOS, we had to roll back 0.22.0 in order to get around this build error. |
|
@jbaker10 or @helfrichmichael can you guys provide the brew tap syntax to downgrade to bazel version 22? Thanks, So I was able to figure out what corresponded to the Brew Version. BAZEL 22 Not sure if this will be helpful to anyone, but as a total newb to Git/homebrew, here's a page that has the commits for the Master Formula for Bazel https://github.com/bazelbuild/homebrew-tap/commits/master/Formula |
|
Going to resolve this since there hasn't been any further update in some time. Thanks and let us know if this isn't resolved. |
Expected Behaviour
Smooth initial deployment of App Engine web_app.
What I am running:
Actual Behaviour
Steps to Reproduce
running the latest versions of bazel, npm, gcloud follow the steps until Build and Deploy on the Web App Deployment Guide. Error occurs after while running the deploy.sh script.
MacOS 14.4
The text was updated successfully, but these errors were encountered: