I noticed that after I pulled version 1.0.0, I was no longer able to import allennlp.service. I see the docs are still updated only as far as 0.9.0 as well so I'm not sure what the status of the service module is.
Answer in comments above; the functionality was moved to http://github.com/allenai/allennlp-server as a plugin.
Related
I have before worked with Python extensions and configured PIP to point to our artifactory in my company, now I would like to do the same with VS Code.
I would like to be able to change the path of where VS Code downloads its extensions, to our own artifactory.
We want to control what users have which extensions, and don't want them to be able to download freely.
Can anyone please help me to which file or configuration I can make to point it to another site?
This is not possible at the moment. There is already an issue concerning this feature https://github.com/Microsoft/vscode/issues/21839 .
You can however disable the Gallery as mentioned by Thally by removing the "extensionsGallery" part from VSCode\resources\app\product.json.
And offer the vsix you want your users to have via any differnt path for selfservice or even just preinstall them under %USERPROFILE%\.vscode\extensions.
VSIX can be downloaded from the store for offline use as Mentioned by t3chb0t in his answer to how-to-install-vscode-extensions-offline
If you are still running into this, an updated answer is to use https://github.com/LOLINTERNETZ/vscodeoffline
So far it has worked well for us in a completely offline environment. The only gotcha that we have run into is that some extensions attempt to reach out and download additional things from github or elsewhere when first run which does not work if you are offline like in my situation. However, if you are online and simply want to control which extensions are available, I think this project will do the trick for you.
Anyway, by adding a product.json file to their user directory or setting env vars, your coworkers will be able to change the marketplace again: https://github.com/VSCodium/vscodium/pull/674
In the browser console, I see:
[Deprecation] document.registerElement is deprecated and will be
removed in M73, around March 2019. Please use
window.customElements.define instead. See
https://www.chromestatus.com/features/4642138092470272 for more
details.
It's coming from polymer-micro.html:443, which is coming from my Polymer 1.11.3 package in my project. I believe that's the latest v1 version.
How do I handle this without updating Polymer to v2? I tried updating to Polymer 2, but it's failing at runtime. I guess the api changed.
For polymer v1 based components to work with the latest versions of modern browsers you should add the Web Components v0 polyfills in a way similar to this in your main html
<script src="/bower_components/webcomponentsjs/webcomponents-lite-min.js"></script>
For more info on this check the polymer team's blog post
For example, entering http://mywordpresswebsite.example.com/?json=1 into the browser loads the main site html, the same as omitting the json querystring variable: http://mywordpresswebsite.example.com/
The JSON API is activated. I have tried reactivating and deactivating, checking .htaccess file settings, and deactivating all other plugins. None of those have made much difference so far.
TIA
I had the same problem with my localhost test page and was wondering, why my route worked last week and was not accessible this week.
Short explanation
After some tests and a lot of frustration, I was able to use the REST API Route again by following the wordpress documentation about routes-vs-endpoints with “Pretty Permalinks” and “Ugly” Permalinks
Longer explanation
I guess in my case it was based on the reinstall of my MySQL Database. By installing the new database, my previous setup has been reset to the wordpress standard installation with permalinks as "plain", which is an "ugly" permalink. That's the reason, why the answer of Mattygabe work for me after the reinstall of the database.
But with this solution, I had a problem with my filter value and therefore I found the solution with "pretty premalinks" and changed my permalinks to "Month and name", as shown in the picture. After this change, I could access my REST API via the desired route.
There could be also some difficulties with REST APIs related to the following examples:
using "wp" within the REST route
if you work on plugins, which should be shared, keep on mind that some plugins may restrict REST Access, e.g. iThemes Security
I'm likely doing it wrong, but when I form my requests for a Wordpress installation at http://www.example.com/ like this:
http://www.example.com/index.php?rest_route=/my/rest/route/here
I end up getting proper responses back.
I had a heck of a time figuring this out and ended up grokking a URL formatted like that in the HTML returned to me. I was expecting to make requests as http://www.example.com/wp_json/wp/v2/my/rest/route/here , but I only got HTML responses.
(FWIW, I am reposting this on all similar questions on the StackExchange network. Admins/mods - if this is against the rules or seen as rep spamming, feel free to take it down. Was hoping to help anyone else hitting the same issue I am, and to also learn what it is I've done wrong and why.)
Ok, so the new endpoint for Wordpress 4.7 is mywordpresswebsite.example.com/index.php/wp-json. It's part of Wordpress Core as of 4.7 and not a plugin anymore, there's nothing to be activated. Thank you, Mark Kaplun.
I also experienced this issue. I did install the WP API plugin and then realized I didn't need it so I deactivated it and deleted it. Afterwards I tried a GET request to https://example.com/wp-json/wp/v2/posts and received the HTML of my wordpress site.
To fix this I ended up deactivating all plugins and then I started receiving the JSON response from https://example.com/wp-json/wp/v2/posts so I stepped through each plugin reactivating and in the end all my plugins are active and the endpoint is responding with JSON.
I changed Permalinks (Settings => Permalinks)
I had an issue returning html page instead of JSON response on Wordpress 5.3 and I got resolved when I changed the Permalink as Post name from plain
We are using UI5 library version 1.36.12 in our Web app but due to chrome update some controls like IconTabBar, MulticomboBox are not working properly due to pointer events not disabled by default in the latest versions of Chrome.
One solution to this problem is to upgrade to version 1.38.14 but we are running in a tight schedule and we have to make many changes if we update the library.
One solution I tried is adding the fix in sap.ui.core.js file in current library jar files. But it is still not working. Should I have to rebuild sap.ui.core.js file and if yes how should I do that?
Please don't suggest to manually deactivate functionality in chrome through chrome://flags/#enable-pointer-events as client is not approving for that. Please suggest me a way to solve this issue without upgrading the library.
In the current UI5 version you can load your own Device object beforehand and UI5 will use it. I assume that this works in your version as well.
UPDATE: My proposal to reset the value later cannot work as it is used in the bootstrap mechanism. Therefore I removed this. Then the last resort is to use the approach mentioned by codeworrior on GitHub:
Before you bootstrap UI5 add a script tag and do the following:
if (/chrome/i.test(navigator.userAgent)) {
delete window.PointerEvent;
}
In this case pointer support is set to false.
I made an add-on that worked on 05/21.
At some point between then and now it broke.
The old code is no longer in the revision history which only goes back to 05/22.
I have tested version 1, and it works, which means it's using the right code.
I can run this working version, but I don't know how I can re-open the code for it.
How do I view the code for version 1 of my add-on?
EDIT
From #BryanP's comment, I've been informed that there is an existing request for this here.
It's a bit round the houses, but you could:
Create a test project
include the older version of your library
Use the debugger to step into the older version of the code and then copy and paste it somewhere safe.
I use this technique to poke around in the libraries I'm using.