I'm having trouble integrating Firebase with Jira Server. Firebase shows the message:
Unable to access the Jira instance
Do I need to release any ports on the jira server? I'm putting the correct URL as per the information in the documentation. Previously I had done the process for Jira Software and it worked, but I can't make it work in Jira Sever. Can you help?
Related
Getting this warning Data won't be synchronized. No GraphQL endpoint configured. Did you forget Amplify.configure(awsconfig)? which I assume is the reason my data isn't being synced to the cloud and is only working locally while testing my application.
I have read many of the pasts posts about this issue and have followed all the steps such as configuring the endpoint url in aws-exports.js but nothing I'm finding online is working. Anyone have any success with this issue using API key as the default auth setting?
I'm looking for documentation detailing the API that allows clients to connect to Firebase Remote Config. I'm making a Unity project for a platform other than mobile, and I've built my own client code for other Firebase products since no client library is available to my knowledge; now, I'm looking to do the same for Remote Config but I can't seem to find any documentation for the actual REST API!
I'm aware of the Remote Config admin/configuration API, but this is NOT what I'm looking for, as it is built for developer/admin accounts to modify remote config data; instead, I'm asking for the API that the official Firebase client libraries use to fetch one single user's configuration.
A link to official or unofficial documentation or easy-to-read sample code would be greatly appreciated! Otherwise, I might end up reverse engineering the Google-provided client libraries and generate some myself.
firebaser here
There is currently no publicly documented REST API for accessing Remote Config data from a client. The only supported platforms are the ones for which an SDK is available.
Also see:
Firebase Rest api for remote config
Calling Firebase Remote Config REST API without auth
How to query firebase remote config rest API, where somebody tries to use the (afaik undocumented) REST API in a web app
I am unable to publish API in WSO2 API manager 2.6.0 environments.
Error message is:
Failed to publish Environments
Production and Sandbox
Error while publishing prototype API to the Gateway. Error while publishing API to the Gateway. No API exists by the name
I did checked API in the DB it exist.
I did searched over the net but did not find any solution on this issue.
Looks like Even after deleting the API, still context URI is persist somewhere so I think I need to delete the context URI - Please suggest
I found solution -
Even after deleting the API from WSO2 publisher, Looks like API will not completely deleted from WSO2 so I just checked is there API still exist in WSO2 and I found the API in the below mentioned location and deleted.
API Manager\2.6.0\repository\deployment\server\synapse-configs\default\api
Now I am able to create new API with the context URI.
I am setting up wso2 API manager 1.10.x with DAS 3.0.1 for publishing API statistics using mysql. My API manager system is clustered with gateway worker node on a separate VM. I followed the documents to enable analytics for API manager via UI. I also followed this document to manually enable analytics for gateway worker node. http://blog.rukspot.com/2016/05/configure-wso2-apim-analytics-using-xml.html After setup, I restart all servers, everything seems fine. But when I make a request to published API, gateway does not publish any statistics to DAS receiver. No data in DAS summary tables either.
By debugging wso2 Gateway, I am able to narrow it down to the fact that
private static ServiceDataPublisherAdmin dataPublisherAdminService; inside org.wso2.carbon.apimgt.impl.internal.APIManagerComponent never get set. Therefore APIMgtUsageHandler does not do anything.
Any idea on what could cause this to happen?
Thanks.
Figured it out myself.
bundle org.wso2.carbon.statistics_4.4.8 and 2 other statistics bundles are necessary for gateway worker to publish statistics data to DAS. But worker profile provided in the package of wso2 API manager 1.10.0 had them excluded.
To work around it, start wso2 on worker node with -Dprofile=default.
You can use osgi console to confirm the activation of these bundles. Once the bundle is activated, class inside is instantiated, gateway will start to publish statistics to DAS when you invoke a published API.
Since migration to V2 logs from Cloud ML jobs are not accessible on the Stackdriver logging console anymore. The last log displayed is
Waiting for Tensorflow to start.
The job is executed and completed successfully, I just can't access outputs in the logs
All Stackdriver APIs are enabled for the project.
There are no known issues with Cloud ML's Stackdriver logging. The fact that you see "Waiting for Tensorflow to start." indicates you are seeing log messages from Cloud ML.
If logs from your Python/TensorFlow program are missing that usually indicates Cloud ML hasn't been authorized to send logs to Stackdriver logging for your project. To check permissions do the following
Identify the Cloud ML service account by following these instructions
In the Cloud Console select the IAM Tab
Verify that the Cloud ML service account is listed and has Logs Writer permissions
This problem also took me two weeks to search answers online with frustration, until I came across this post. I did not see "migration to V2" as OP mentions but I simply could not get any application logs in StackDriver, only system logs of job started/completed. Following what Jeremy replies solves the problem.
To make Jeremy's reply simpler to follow, essentially you add the ML service account
cloud-ml-service#<project-id>.iam.gserviceaccount.com
to your project's IAM members, with at least "Logs Writer" role.
You can get "project-id" by:
gcloud config list project --format "value(core.project)"
I also assigned Project->Editor role to allow Bucket access.