I have a problem trying to add Material-UI to my existing CRA project.
I run:
yarn add material-ui#next
I run:
yarn start
I get:
Module not found: Can't resolve 'material-ui/FlatButton' in 'C:\Users\...\src\components\DialogModal'
Looking in node_modules under material-ui, many folders (including FlatButton) have no content. What went wrong?
The installation worked fine. The problem is that material-ui v1 has many breaking API changes from material-ui v0. One of these is the removal of the FlatButton component in favor of a Button with props. Many other components have also been changed, renamed, or removed entirely.
When you installed material-ui#next, you installed v1 instead of v0, because the #next flag points to v1. So, the absence of these folders and components is expected. You can take a look at which components should be available in the v1 docs.
You have a couple of options:
Uninstall v1 and install v0 instead. You can install v0 by installing material-ui (without flags).
Migrate your code over to v1. You're going to have to do this eventually anyways, and v1 has many improvements over v0, so if this is a possibility for you I would recommend it.
Related
lately I was experimenting with Skaffold with our Helm Charts and I am in little bit in a dilemma that our Helm Chart \ Sub Charts are compatible with Skaffold or not.
Our helm Charts are looking like the following
my-helm-charts
+-charts
+-project1
+-project2
+-project3
+-project4
+-infrastructure_kafka
+-charts
+-kafka
+-zookeeper
+-infrastructure_cassandra
+-infrastructure_elasticsearch
+-Charts.yaml
+-Values.yaml
The reason we choosed to structure the Helm Charts this way, is that if necessary to spin up extra stages for our project.
Now when I want to develop project2 with Google Cloud Code / Skaffold (which I configured correctly and I can start without problem in IntelliJ) I have to start whole my-helm-charts.
That is actually Ok but the problem is, if I use Debug in Kubernetes, I have a feeling Google Cloud Code/Skaffold can really locate the project2 and no debugging occurs.
My feeling is Google Cloud/Skaffold is more oriented to work with following contruct...
project2-helm
+-templates
+-Charts.yaml
+-Values.yaml
My Subcharts contructs starts in Google Cloud Code/Skaffold without any exception but I can't debug, is it possible to achieve want I want with my structure and if yes, how?
Or is it not possible at all...
Thx for answers...
We recently added a feature called config dependencies which might help here. It allows you to create more specific skaffold.yamls and then map them together with a "requires" field:
https://skaffold.dev/docs/design/config/#configuration-dependencies
Once you have the skaffold.yamls created and the right dependency mapping you can run skaffold with the -m flag to choose once slice of your services:
skaffold dev -m project3
Cloud Code support for modules is incoming.
Cloud Code IntelliJ and Cloud Code VS Code recently added preview level support for deploying and debugging modules of a larger application which uses Skaffold. See more here https://cloud.google.com/code/docs/intellij/skaffold-modules
I decided to try out the new unity dots system, or, the new entities package (as well as the hybrid renderer), but I can't find the package in the package manager with preview packages enabled. After looking it up, I could not find any resources, other than one that told me that they moved some of the preview packages out of the package manager, and somewhere else. Does anyone have any idea where it could be?
This is what it looks like on my screen by the way:
From Entity Component System - DOTS Project Setup
Starting with Unity 2020.1, the DOTS packages are not listed in the package manager, even when preview packages are enabled. There are two alternative options to install those packages:
You can use "Add package from git URL..." under the + menu at the top left of the package manager to add packages either by name (such as com.unity.entities), or by git URL (but this option isn't available for DOTS packages). Note that it might take a few moments before the package starts installing.
Alternatively, you can add DOTS packages by directly editing the Packages\manifest.json file in your project. This file requires not only the package name but also a version which can be found by looking at the documentation of each package (such as "com.unity.entities" : "x.x.x-preview.x").
For example currently it would be com.unity.entities" : "0.17.0-preview.41"
And
Follow the link for more information about installing hidden packages.
Maybe also interesting for you:
The recommended set of core packages to be added to a DOTS project is:
com.unity.entities
com.unity.rendering.hybrid
com.unity.dots.editor
I look at this help requirement:
dependencies:
- name: postgresql
version: 8.6.2
repository: https://kubernetes-charts.storage.googleapis.com/
condition: postgresql.installdep.enable
Source: https://github.com/reportportal/kubernetes/blob/master/reportportal/v5/requirements.yaml
Postgres 8 is very very old. I guess this version is just the version of some package.
But how can I get more information about this package?
I look at https://kubernetes-charts.storage.googleapis.com/. But this URL seems made for robots, not for humans.
How can I (as a human) find more details about this dependency?
It looks like you can find the chart here: https://github.com/helm/charts/tree/master/stable/postgresql
It's current version is 8.6.4.
Your dependency looks like it references this PR and this version.
Also, as an aside that refers to the Chart version, not the postgres version. It looks like the current Chart is for postgres 11.
You can use helm dependency update locally: https://helm.sh/docs/helm/helm_dependency_update/
This will download all the dependencies to the ./charts subdir where you can check its contents and default vars.
Requirements.yaml is used to list Chart dependencies. Those dependencies can be built using helm dependency build from requirement.lock file.
Version describes chart version, not the image itself.
All necessary information about the chart are described in values.yaml- you can find there information about images to be installed, it's version etc. In this case it's postgresql:11.7.0.
You can retrieve information about the chart by using helm show values <chart_name> (chart doesn't have to be installed in the cluster) or it can be found on chart's github/ helm hub repository.
So I need to write a custom grafana plugin, that works like a funnel. I decided to try and integrate this funnel. Note that it is supposed to get the data from a mysql Server and use it just as a table and not as time series.
So far I read the grafana documentation and then watched this video. In the video a dataFormat is declared in the plugin.json file, however when I checked other working Plugins I didn't see that part written in the plugin.json. The GitHub repos in the video are also gone. I stumbled upon this one though, so then I copied it in the data/plugin directory. I restarted the Server and it was detected but when I tried making a new Panel I got an error saying that it could not be found. I was planning on starting with this example and then working my way towards integrating the funnel part but I can't seem to get it working. Any ideas where to start?
I have reproduced your problem with the same actions and got same error:
Panel plugin not found: myorgid-simple-panel
Just a guess: there is a dependency section in plugin.json file
"dependencies": {
"grafanaVersion": "6.3.x",
"plugins": []
}
My Grafana version is v6.2.5. Isn't this plugin template for future Grafana release (master or developement version)?
I had the same problem with simple-react-panel. To solve it, I ran in the simple-react-panel-master directory :
npm i #grafana/toolkit
npm i #grafana/ui
yarn build
and after I restart grafana service
I'm starting to use Symfony Flex to bootstrap my project and I realized that running composer install for the first time generates a file named symfony.lock for which I could find no documentation.
What does this file do? Should I keep it in my version control and deploy it or should I .gitignore it?
Yes, officially you must add it to the version control:
Flex keeps tracks of the recipes it installed in the symfony.lock file, which must be committed to your code repository.
https://symfony.com/doc/3.4/setup/flex#how-does-flex-work
Otherwise on staging or production stages it will be generated again by Flex, auto-configuring all installed packages with recipes and triggering bugs like this https://github.com/symfony/flex/issues/192