I've started setting up different tools on my home server to create apps for personal use and experience. I'm using telegraf to pull metrics from arangodb's _admin/metrics but getting an error. This is due to one line in the response has a typo which has "guage" instead of "gauge".
https://www.arangodb.com/docs/stable/http/administration-and-monitoring.html#RestAdminMetrics_container
#TYPE arangodb_client_connection_statistics_client_connections guage
Will this be fixed in the next update? Also, if there is any workaround for now, please share. thanks
This has been fixed in PR https://github.com/arangodb/arangodb/pull/10625 which will be part of v3.7. I don't know if this will also be backported to 3.6, so you might want to create an issue on github.
Related
I'm trying to do some offline development with gcloud sdk where I want to build a Python Flask app presenting data queried from a datastore. The reason for doing it offline is simply that it's faster during development, it will be deployed online later using App Engine.
First of all: The datastore emulator is running.
However I am having trouble importing data into the datastore. I am using below from here to try and import (with my values).
curl -X POST localhost:8081/v1/projects/[PROJECT_ID]:import \
-H 'Content-Type: application/json' \
-d '{"input_url":"[ENTITY_EXPORT_FILES]"}'
The problem I am having is that it just returns
NOT FOUND
I think I know what it is but not how to solve it: I don't have a project defined in my offline environment. So I wonder, how do I set up a project in my "offline cloud SDK environment"?
The PROJECT_ID for the DataStore Emulator is set during it's installation.
I've looked a bit into it and in the link at the bottom you can see how it's done. You need to set your project-id as an environment variable, or do it with an automatic command that sets it for you.
Have a look here, I think this is what you're missing.
Hope this helps.
EDIT:
Hey again Nelumbo, I think that the NOT FOUND you received before and the NotFoundHandler are the same error. The common errors in Datastore reflect that NOT_FOUND is generated when an request attempts to update an entity that does not exist which means that it might be a malformed address.
Taking into account that your Datastore emulator starts correctly, that is my first thought of a probable cause, that we are pointing wrong or in the wrong format.
If you are completely sure that is not the case and I'm assuming you attempted different formats and double check.
I have a few other ideas of things that you can checked out in order to discard potential causes.
Are you running in a different port than 8081?
What is your cloud sdk components version? Have you updated them lately?
Have you attempted to pass manually the project ID in the curl?
Also, I'm understanding that you are importing data into the datastore emulator and everything is done locally.
Let me know.
EDIT2:
Hey Nelumbo, the only different things that I can think of that might be affecting you or for you to try is that I'm seeing that the configured port for the installation is 8432 and the one for the import is 8081 as you can see in the following docs. When you checked the environment variables was it 8432 or 8081?
Another thing that I would suggest is attempting to do this in the Cloud Shell to make sure it works and if it does raise a public issue tracker with the GCP team as it might be an issue with the Windows version.
And at least try to update the SDK version to the latest one maybe it's related to that. But yeah, as the initial question of how to add a PROJECT ID to the emulator is solved, making a new one in order to also bring more visibility to it might be helpful.
I noticed that Custom Vision is now returning the message {"code":"NotFoundIteration","message":"Invalid iteration"} instead of the expected (and previously provided) results.
Something has recently changed on the API call?
Thanks
I have seen the same issue happened and the latest news I got from support team is: Problem was identified ; due to recently introduced defect some published models were removed ; after which prediction requests against these published models would fail. The original bug was fixed and a repair program was ran that put back the missing published models. So I think your issue should be fixed now as well. If not, please let us know. Thank you.
Regards,
Yutong
I've been using AWS AMI sandbox, and have noticed that many screenshots in the sandbox are missing since recently as below:
One missing file is at https://raw.github.com/hunch7/sample-apps/app_description/configurationdemo/resources/pic/config_demo_2.png?raw=true
Have the files been removed?
Thanks
James
Looks like some links on the Kaa Sandbox 0.10.0 were directing to one of the sample-apps fork on the GitHub and are now removed.
We will fix this in the next Kaa fix version 0.10.1 Sandbox which is planned to be release soon.
Also, we will try to restore at least some resources on the GitHub fork as a fast workaround.
Update: The issue should be fixed now. Please check.
What's the dealio on importing data from a legacy issue tracker system into Gitlab CE?
Do tools exist for this? Schemas? Suggestions?
Please notice that this is really a legacy issue tracker system. It predates bugzilla, and runs on an old IIS server and SQL Server 2000).
(Say whatever you want about this setup, but it's nothing we haven't already heard.)
You should be using the REST APIs to create your migrations.
Generally recommendation questions are off topic, so if I mention
there is a redmine issue importer and there are issue tracker issues on the gitlab ce issue tracker requesting this. This sounds like a good kind of thing to make as a community contribution if it's a popular tool.
But if it's not, and you're the only person in the world using your tracker, you probably will want to study the python based redmine issue importer it may server as an example for you to write your own REST-api based tool that reads your db and creates the Gitlab Issue Tracker issues. You don't want and don't need to know the Gitlab side's PostGres schema. It will change over time anyways.
This happens when I try to deploy a Sharepoint WebPart solution. Is there a file or configuration option that I have missed that is causing this error to occur?
Thanks.
I assume that you're using VSeWSS 1.3 to deploy you solution and that these error occur when you try to deploy the solution. I'm not 100% sure but I think I had the same error some time ago. Unfortunately I could remember what I exactly did to solve this problem. But I'm quite sure the problem was related to some network issues as VSeWSS 1.3 uses web services to handle solutions.
So I would advise you to double check you network settings. For example you could try to adjust your hosts file so that your computer's name could be resolved.