I'm using Kiwi TCMS version 6.2 in a docker-compose environment. Just trialing it right now.
All working OK in relation to created/edit/delete/run features.
However, I'm also trying to get the Github integration working so that I can create Github issues from within a test case run.
When I click the "Report" link it shows me my Github integration in the dropdown, I click Report button and this error is shown:
"Enable reporting to this Issue Tracker by configuring its base_url!"
In the "Bug Tracker" admin page I have it filled out as follows
Type Github
Base URL https://FQDN/ORG/repo/
APU URL blank
API username blank
API password or Token - A token that I generated from my Github account via Settings-->Developer Settings-->Personal Access Tokens
I have looked at the Kiwi console by starting docker-compose without the "-d" option and I dont see anything useful in the console.
Any thoughts on what I've done wrong or missing?
Is my token generated from the wrong place maybe?
thanks
https://kiwitcms.readthedocs.io/en/latest/modules/tcms.issuetracker.types.html#tcms.issuetracker.types.GitHub
Base_url:
URL to a GitHub repository for which we’re going to report issues
Related
I'm developing a site in Gatsby. Users receive an email with a link containing a single-use token, like this:
https://www.example.com/approval?token=hIPdI7oSw6KV6k8ttsXG3XAHmIqExyB01YkChxiLR9leksJ67iRme6yyxfBztz3Z
This should take them to the approval page and supply the token as parameter.
It works fine in the development build, but in the production build the parameter is missing from the url and the user is simply directed to https://www.example.com/approval
Does anyone know why Gatsby might be re-writing the url without the parameter in the production build, and is there some way to prevent that from happening?
EDIT: This site is hosted on CloudFront, and we've enabled forwarding of query params. Possibly there are some a re-direct happening at another level?
It turned out to be Gatsby/CloudFront madness: https://github.com/gatsbyjs/gatsby/issues/20139
The Gatsby dev server was unhelpfully injecting a / in front of the ?. The production build on CloudFront wasn't doing that, triggering a re-direct. CloudFront requires query strings in the format /? - for future reference!
I am following Get started on the Microsoft Teams platform with Node.js and App Studio
to add app in MSTeams. All the steps worked as per the documentation, however the last step "Register your app in Teams" failed during installing of the application. Below is the image attached
I also tried to upload the custom application , but it also throws error that something went wrong.
Below are the images:
Here are the permissions, I have enabled them all to test, still the issue remains the same
Can someone please suggest to fix this issue?
You need to make sure that you have the correct permissions to side-load custom apps into Teams, and this can be controlled at the Org (i.e. Tenant) level, the Team level, and the individual level. Have a look here for more.
I am trying to build an action messaging extension with a task module implementation which uses a URL attribute to load the page. Attached is the screenshot of the task module code which was generated by Yeoman Teams generator.
The popup comes up blank. So it means it's not loading the HTML file path, but if I open Chrome and try to load the URL, it works fine.
Also instead of using URL if I use an adaptive card it works fine. Only the URL part doesn't load on the popup. Attached is another screenshot of the popup inside teams:
What could be wrong with the code?
The other answer is correct in that your url needs to be reflected 100% correctly in your manifest. However, there are a few things that you need to be clear on:
It's not per se the address of the BOT that's important, but rather the address of the web page itself that needs to be listed in your safe domains list in your manifest. In your case, they're hosted in the same endpoint, but they might not be in your final solution, depending on how you end up hosting this.
While you're developing locally, rather use App Studio. That way, you don't need to fiddle with the zip file every time - you can just change it in App Studio and immediately redeploy with the updated URL
Every time when you compile and run the project, a new hostname is generated since ngrok free license is used in the yo teams scaffolding, which makes the app to reference to the old URL.
You need to uninstall the app from the Teams app store under your organization and upload the new app from the package folder .zip (Only after gulp ngrok-serve)
If it still does not work, check the below
Unzip the package file and verify the manifest whether it's pointing to the right hostname of the action html page
Go to http://localhost:4040 to inspect the ngrok tunnel traffic that should give more info on the routed requests.
I am new to Hybris, I have succeeded in standing up the Powertools B2B site and have discovered a 404 error. I would like to learn how to trouble shoot this 404 error along with other such errors.
Steps to reproduce:
Start up the OOTB version of Hybris 1811 with Powertools B2B site configured
In Backoffice, change the password for user screwdriverslover#pronto-hw.com
Log into the Powertools storefront with user screwdriverslover#pronto-hw.com
In the upper right select My Account > Returns History
And you will get a big 404 page not found.
How would I go about tracking down this error? While I seek the solution, the steps to find the solution are far more important to me right now.
You need to check the log (console or log file) to find the root cause.
The page/component you are trying to access might not have been created as part of the initialization. In Hybris, the pages/components are part of the content catalog. If the page/component you are trying to access has not have been created, you will need to import relevant ImpEx. The other possibility might be the wrong URL configured for this page. You can check all these things in the backoffice application.
Update: copying the following text from my comment:-
You need to put into localextensions.xml, the extensions and addons responsible for order management. In the case of addons, you will also need to install the addon using ant addoninstall. A simple way to do it is to install b2c_b2b_acc_oms recipe. Alternatively, look into the build.gradle file of b2c_b2b_acc_oms for the OMS (Order Management System) extensions and addons and include/install them manually. When you are doing it manually, make sure to clean, build, and update your application using ant clean all updatesystem.
I have deployed a new version of my App that contains a new cloud endpoint.
I have made the new version the default version.
I have even deleted the old version (version 1).
If I try to hit https://<myappid>.appspot.com/_ah/api/ then I get a
404 Not Found.
If I try to hit https://2-dot-<myappid>.appspot.com/_ah/api/ then
my request gets served.
It's been a full 24 hours since I uploaded version 2. And more than an hour since I marked version 2 as default and deleted version 1, but I'm still getting the 404.
I don't want to ship my client explicitly pointing to 2-dot-<myappid> as this locks the client to a particular version.
Any ideas on what is going wrong?
Cloud Console currently doesn't automatically update Endpoints when changing app versions. You need to use the old App Engine Admin Console to make it update. So, I suggest trying switching versions to another version and switching back immediately. It should fix it for you.
Upload a new major version of your app. This can be identical to your current default version, which just the version name changed.
Visit the App Engine Admin Console and select your project.
Click Versions.
Change the default version to the one you just deployed.
Change the default version back to the one it just was.
At this point, the default domain should be working for you.
how about trying "https://xandar-wordgame.appspot.com/_ah/api/explorer",it may redirect the page to api-explorer where you can explore your api.
Others:
I've also encountered the same problem. but then I realized I have not changed the javascript code that load the api client. I changed the version in java annotation , but forgot to change the gapi.client.load(_apiName, _version, _your_call_back_function,_apiRoot) in web client .
Hope it will help.