I am not able to view Google Cloud Build logs in the console. For each step that I click on I cannot see the associated logs in the Build Log window on the right (see picture). This occurs with both the Build Summary and each detail step. The only way to view these logs is to click View Raw, but that is only a great workaround.
Another issue is that each build step status (Success/Failure) is only populated at the end of the entire build process, as opposed to updating after each step.
Is anybody also experiencing this or have suggestions to rememdy this issue? My browser is Google Chrome Version 93.0.4577.82 (Official Build) (x86_64)
Experience shows that there can be adverse interactions between Chrome Plugins and a variety of websites that have rich content or streaming (such as Google's Console). If something seems odd, try and create a new Chrome profile or try running in incognito mode and see if that resolves the issue. If it does, you can incrementally add (or remove) the plugins until you find the one that is causing problems. If you do find the culprit plugin, consider posting that as a comment to others on what you find.
As per the documentation, if you’re storing your build logs in logging, you won’t be able to see them in the cloud build page, instead you will be able to see them in the Logging page(i.e. Operations logging).
To view the build in Cloud Build page in the Cloud Console, if your build logs are present in the Google-created Cloud Storage bucket, grant the Project Viewer role on the project but if your build logs are in a user-specified Cloud Storage bucket, grant the Storage Object Viewer role. And for more information, consider looking at the documentation.
Your second point is an expected behaviour, please look here.
Adding on Kolban's answer above, one of the Chrome extensions that interfered is Imagus. Uninstalling / disabling it should fix the problem.
Another Chrome extension that seems to cause the problem is "Dark Mode". My version is 0.4.2 on Chrome version 96.0.4664.110 and disabling this and refreshing the Build Detail page restored the build log listing.
Related
Currently have issues with AWS Opensearch dashboard.
Can't download the AWS OpenSearch dashboard as either PDF or PNG
Created Opensearch dashboard and need to download as PDF. After i click the reporting tab next to "EDIT" Generate Reports appears with Download PDF and PNG. But after i click the PDF OR PNG It keeps refreshing and cant download.
What is the Difference between "Row" and "Formatted" Download excels on dashboard. Both are downloaded as CSV files. Any differences between them?
We are facing the same issue and the AWS has communicated to us that their developers are working on a fix.
As a short cut, the CLI mentioned here is being suggested to be used https://github.com/opensearch-project/dashboards-reports/issues/345
I was also facing same problem while downloading reports in Opensearch .
Issue is there are some additional libraries required to run the report extraction in headless mode. I installed required dependencies and issue is resolved.
Please refer this link https://github.com/opensearch-project/dashboards-reports/blob/main/dashboards-reports/rendering-engine/headless-chrome/README.md#additional-libaries
I use Java APIs for the CRUD operations of the google cloud deployment manager API. I can create, preview, delete deployments OK.
But when I try to update an existing deployment that's in preview mode, the API returns the below error.
Deployment in preview must not have a target with UPDATE
The same inputs works OK for create and preview. So, I'm sure that the inputs are OK.
I looked up for others who have reported this issue.
Here is one such report but no solution.
Does anyone know if there's a git hub repo for google cloud deployment manager where we can report this issue?
As mentioned in the answer here, is a known issue and you can still use the workaround suggested.
I have created an issue tracker for this error message. So, you can add your comments there and follow up for upcoming updates.
I followed the instructions in the link (https://docs.wso2.com/display/IOTS330/Enterprise+IoT+solution) in Windows to start WSO2 IoT server. So, broker, iot-server and analytics are started. But, when I'm trying to log in to the device management console using admin login or the login credentials I created, it gives me an authentication error.
I tried the solutions in this answer (Not able to access WSO2 IoTS Device Management Console in wso2-iot-3.3.0 when logged in 'admin') also (Reducing Java version to 1.8.0_144 and making the compression parameter to off in all the catalina-server.xml files). But any of it didn't work for me.
I have attached the screen shots of the error. Please help me to go through this! Thank you.
Error in browser
Error description in iot-server console-Part 1
Error description in iot-server console-Part 2
This is related to the issue mentioned in the github issue mentioned below and it seems, it is already fixed in latest master.
As a quick workaround you could try to modify the startup script files (bat files in this case) and add the changes mentioned in the above git issue.
For example, you can change the file modules/distribution/src/core/bin/iot-server.bat at line number 73 as below.
FOR %%D in ("%CARBON_HOME%\wso2\lib\commons-lang*.jar") DO set CARBON_CLASSPATH=!CARBON_CLASSPATH!;".\wso2\lib\%%~nD%%~xD"
Similarly do the same change as above for files mentioned below as well.
modules/distribution/src/core/resources/profiles/backend/iot-server.bat
modules/distribution/src/core/resources/profiles/keymanager/iot-server.bat
modules/distribution/src/core/resources/profiles/manager/iot-server.bat
This should resolve the issues you are facing.
Related github issue - https://github.com/wso2/product-iots/pull/1838/files
When I try to create a new instance for deep learning on Google Cloud Platform, by following various tutorials including http://cs231n.github.io/gce-tutorial/, I can't select a zone or boot disk (I'd like to use Ubuntu 16.04. There is no response when I click these features. How can I set them?
I've tried to reproduce this issue with various levels of authorisation in my own project and I've not been able to reproduce this issue. As you have access to the Create Instance page, It looks to like this might be a browser specific issue, rather than and issue with authorisation, or any settings within your project.
Would it be possible for you to try and perform this task from a different browser and see if the result is the same? For example, can you try this in Chrome browser and in an Incognito window?
If you are able to perform the action from a different browser, you probably have an issue with cookies, or a third-party browser add on affecting the functionality with GCP. You could try enabling the cookies for the browser to see if that makes a difference, or disabling/removing third party add ons to see if that makes a difference.
Regardless of the browser I'm using, I can't get stackdriver debugging work. After navigating to the source for the code that runs on app engine, clicking on the gutter doesn't do anything.
I'm not using github or bitbucket or google cloud source repo, so uploaded the code from local. I noticed this msg after uploading the dist from local..did anyone succeed in setting this up?
Yes, many use node.js apps with Stackdriver Debugger successfully.
As long as your local source code matches the deployed source code, this is a benign message.
Please email cdbg-feedback#google.com for further support.