I am trying to upgrade apache-superset from 0.38.0 to 1.0.0. But even though the UI version says it is 1.0.0, I don't see most of the new UI components like filters, advanced search options, and thumbnail views on Dashboard, Charts, and Query views.
I can see the updated UI on my local which I build from source. I even tried creating a wheel file from my local source installed it on the server but sees the same old UI.
Can someone please help me understand the issue?
Some of the new features are behind feature flags. In your config, add:
FEATURE_FLAGS = {
"THUMBNAILS": True,
"DASHBOARD_NATIVE_FILTERS": True,
"OMNIBAR": True
}
Other feature flag options can be found in config.py
Related
A few days ago, maybe a week or more, if i update my api definitions, swagger in my case, there was a button to "validade" my docs, collection created from definitions, and then update/sync my collection. So if i add or delete something from definitions file it would reflect in my collection.
But after the update i cant find how to do it anymore
things i try
connect an github repo, and no yet no success
(still connected to github) delete previous docs, create a new one, then update the definitions file (inside postman), again docs refuse to update
how the screen was before update
And now this is my actual screen
Postman
Version 10.0.27
UI Version: 10.0.27-ui-221013-1124
Desktop Platform Version: 10.0.1 (10.0.1)
My organization is using Ember addons to develop a set of shared components between our applications. Let's call this repository app-components. Currently the components application's primary responsibility is to distribute CSS, fonts and images.
We are also building a living styleguide that will ingest our shared components and present them in a neutral way for developers to reference. Let's call this repository app-styleguide. Our goal is to deploy app-styleguide using ember-deploy to deploy this solution to Github Pages. The url follows this pattern:
https://organization.github.io/app-styleguide/
When the app-styleguide application makes it to the gh-pages branch and is served as a webpage, all of the fonts and images being delivered by app-components are giving us a 404. I have referenced a handful of different solutions to this problem, but I keep coming across the same solutions that we have tried.
I have tried using the following two ember addons that automate the deploy to github pages:
https://github.com/poetic/ember-cli-github-pages
https://www.npmjs.com/package/ember-cli-deploy-gh-pages
In the end we went with a vanilla ember-cli-deploy solution, as those two addons are quite old...
I have followed the instructions here to add rootUrl andlocationTypeproperties to ourenvironment.js` file, which has not worked:
https://github.com/ember-cli/ember-cli/issues/398
Our environment.js file looks like this:
if (environment === 'production') {
ENV.rootURL = '/app-styleguide';
ENV.locationType = 'hash';
}
And our requests continue to not add app-styleguide to the request URL's for assets coming from the Addon. Here is an example of a failed request from the Chrome DevTools Network tab:
Request URL:https://organization.github.io/assets/images/thumbnail-icons/person.svg
Request Method:GET
Status Code:404 Not Found
As you can see, app-styleguide is not added to the request.
Any help is greatly appreciated!
I was able to receive some help over on the Ember Slack Community
(special thanks to #alexspeller). It turns out I needed to update a couple of settings in the fingerprinting of assets.
Using the included broccoli-asset-rev library I had to modify my ember-cli-build.js to include the following:
var app = new EmberApp(defaults, {
fingerprint: {
extensions: ['js', 'css', 'png', 'jpg', 'gif', 'map', 'svg', 'ttf', 'woff'],
prepend: '/app-styleguide/'
}
});
I needed to update the options to account for SVG, TTF, & WOFF, as well as the proper prepended url segment.
You can read about the functionality here:
https://ember-cli.com/asset-compilation#fingerprinting-and-cdn-urls
Available options:
https://github.com/cibernox/broccoli-asset-rev?files=1#options
In Redmine, I can use edit button to edit everything of an issue. However, in daily work, the most frequent actions other than update the issue status are "resolve an issue", "close an issue" and sometimes, "re-activate an issue". When resolving an issue, the "assign to" field will be updated to the opener and issue status to "resolved".
I used to add an js to the issue details page to do similar work but it will be gone after redmine upgrading. What's the correct way to do accomplish this task?
Thanks
If you want your custom code to be preserved while doing Redmine upgrades, there are few options:
make it a plugin
install Redmine via svn or git, and perform code updates, it should preserve code that you wrote, and automatically merge rest of
the code
run your custom javascript via greasemonkey or tampermonkey
Im using WSO2 Governance Registry 5.2.0.
When I create a new artifact type, it containt a lot of new fields (You create and define this XML in the CARBON ADMIN CONSOLE). So in the PUBLISHER you can see the new fields, create and consult a new item of the artifact.
But the problem is in the STORE, I cannot see the this new fields. So in order to do this, I made the custom fields available by modifying
GREG_HOME>/repository/deployment/server/jaggeryapps/store/extensions/app/greg-store-defaults/themes/store/partials/asset-attributes.hbs file. Thanks to Malintha's Blog,
This is perhaps an answer, but it will get much worse if for each artifact I have to edit the file to add the fields, editing this file will get a lot worse over the time...
So my question is: Is there a way to create a custom theme (*.hbs, etc) for each new artifact I create?
THANKS!
As far as I understand your in the development phase of the project that you have to create registry extensions(RXTs) and showing up the data in G-Reg Store. As far as I know there is no easy dynamic way that you can do this, either you have to extend the default hbs files. Like you have done using Malintha's blog. This is okay if there is a minor change to be done, However this is not the recommended way because if there is a migration to do such as moving to all new WSO2 G-Reg 5.3.0 you might face lot of trouble if you updated the out of the box files in G-Reg 5.2.0, Therefore I suggest you to write asset extensions(GREG_HOME/repository/deployment/server/jaggeryapps/store/extensions/assets) for each and every rxt that you are going to introduce. There is plenty of blog posts that can help you.
Please find the below list of blog posts(I will update the list if I found any).
Adding a New Asset Type
How to view the json payload sent to the Store UI in GREG 5.1.0
How to extend an asset's store view in WSO2 GREG 5.1.0
WSO2GREG-5.2.0- WRITING EXTENSION TO REPLICATE MORE ARTIFACT
METADATA IN STORE
Overriding default "look and feel" of GREG - 5.3.0
Note:
There is no much difference between 5.1.0 and 5.2.0.(5.2.0 is more stable)
You can start(learn) creating a new extension by simply extending restservice.rxt and the relevant asset extension(GREG_HOME/repository/deployment/server/jaggeryapps/store/extensions/assets/restservice), I prefer you to use this blog post and start from there.
If there is a lot of development to be done I prefer you to seek help from WSO2 experts from they're official portal, if not you can always stick to stackoverflow.
I am new to solr 4.1.0 and was trying to set it up on my MacOSX machine using Tomcat7 and the instructions on the following page:
http://contextllc.com/node/76
I was able to do everything properly, and it worked! I then followed instructions on the haystack documentation to setup haystack and output a schema.xml file. I then created a new core using SolrAdmin and used that schema and keep getting:
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Plugin init failure for [schema.xml] fieldType "text": Plugin init failure for [schema.xml] analyzer/filter: Error loading class 'solr.EnglishPorterFilterFactory'
Is there something i'm missing in the above? I have included all of the solr jar files and cannot find anything else that would be required?
Not sure why..but the issue went away after I switched to solr 3.6.2... Something definitely changed with the versions.