The latest snapshot version of Zeppelin which was checked out few minutes back is broken on helium. Even after enabling helium packages, it is not available as option on the visualization bar.
Related
I have Flink 1.12 and I am using Yarn cluster for deployment. I want to move to K8s but first I would like to upgrade to the latest version of Flink that is stable on K8s. What is the latest Flink version that is stable on K8s?
In general, the latest stable release of Flink should be running stable on K8s. (Flink documentation for 1.14)
From personal experience I can verify that version 1.13.2 is running stable.
I however did not test 1.14 yet, but plan to do soon.
As I'm sure many are aware, admob needed an update to use a newer SDK (7.64+) and this message appears on your admob account if you have apps using an SDK below that version:
Some of your iOS apps require a GMA SDK update To keep ads serving normally and minimize a loss in ad revenue, implement the GMA SDK 7.64.0 (or later) for your iOS apps. And configure the SKAdNetwork in your apps with Google's network ID.
Expo had a PR here that was merged 6 days ago. This should have updated the GMA SDK to 7.69.0. However, when I ran expo upgrade it states that it updated expo-ads-admob,
✅ The following packages were updated:
expo-ads-admob, expo-av, expo-keep-awake, expo-updates, react-native, react, react-dom, #babel/core, react-native-web, babel-preset-expo, expo
but no changes actually take effect. And if I have the newer version (10.0.0) that I manually installed as stated below, it downgrades it to 8.4.0.
When that wasn't working, I then went and manually updated expo-ads-admob to 10.0.0 via npm (also tried yarn) and it looked like the node package was actually updated (checking the CHANGELOG and it has info about 10.0.0).
Still when I build my app with expo build:ios, run the new app, and check my GMA SDK version on admob it is still using 7.55.1.
I have also tried completely removing expo-ads-admob and reinstalling, but the same issue occurs.
Any ideas as to why this is occurring? Is there some other method I should be using to upgrade to the latest commit on expo's master branch?
Appreciate all the assistance in advance and let me know if there is any additional info I can provide.
Additional Info:
SDK Version: 40.0.0
Platform: iOS
Workflow: Managed
EDIT: Received answer from Expo member, see answer below.
You cannot use updated packages if using the managed workflow, it must be bare workflow in order to update module versions manually. Therefore, this admob update won't take place for managed workflows until expo SDK 41 is released.
See expo forum here for more.
How could I find available versions of scalatestplus? I checked this page but it only tells the compatibility of scalatestplus with Play. How can I find which releases are available in 3.1.x?
You can see all the versions of scalatestplus-play via
Maven Central repository
Github releases page
Currently, 3.1.0, 3.1.1, and 3.1.2 have been released.
While trying to upgrade SonarQube plugin from 2.2.1 to 2.4, it failed and the plugin is gone. I had to uninstall 2.4 and reinstall 2.3. Now all the SonarQube Analysis Step disappeared from all projects. I can see it's still in the config.xml, but can't see from the web UI. I tried:
Reload configuration from disk
Manually change from plugin="sonar#2.2.1" to plugin="sonar#2.3" in the config.xml
Uninstall and reinstall 2.2.1, reload from disk
Manually add the step, compare the result conf.xml to the original, there is no different at all for this step.
Still can't see the step in the job. please help.
This is fixed by restarting Jenkins.
Today I've faced with a strange behavior of NuGet when installing a package.
A brief description: as a result of my build script there's a NuGet package. I don't change the version each time, so each and every build produces MyPackage.1.0.0.nupkg. As the final step of the build, I push the package to the NuGet server deployed inside the local network.
Now, on a different machine, I run nuget install MyPackage -Source http://myserver/nuget, which obviously installs the NuGet package.
The problem comes into play when I push another update of MyPackage - still of version 1.0.0. When I try to re-install it on client machine, I get the previous version of the package.
I found out it is the local cache to be blamed: if the package was installed, it gets into the local cache and the next time the package of the same version is installed, it is taken from cache. Fair enough!
But, on the other hand, there's a -NoCache option of the nuget install command, and I expect it to ignore the local cache.
However, this is not true. The first time I run it with -NoCache, it updates the cache and installs the true latest version. But, the next time the package is still taken from cache, even with -NoCache option.
Is it expected? Is it because of the version not being changed?
Just in case: all NuGet operations are done with NuGet.exe and from PowerShell session.
UPDATE: I observe strange behavior I can only explain by cache expiration. When the package is cached, all subsequent calls to nuget install pull the package from cache, until some time passes. I didn't notice the exact period, but it's definitely more than an hour. After this, nuget install updates the package in the cache, and the situation becomes the same...
Yan,
I push another update of MyPackage - still of version 1.0.0.
You should not be pushing more than one package with a particular version: packages should be immutable. If you've changed something in the package, increment the build number a.b.C and push a new version of the package.
The behaviour you experience is a side effect of NuGet expecting to be able to cache a given package version essentially indefinitely.
Yan,
NuGet caches the packages it downloads on your local hard drive. For my windows 7 machine the cache is located at C:\Users\jmelosegui\AppData\Local\NuGet\Cache.
So you can delete the nuget package you want to forget from the local cache directory. Then the next time you install the package you will get the lastest version from the server.
BTW: I am agree with #matthew-skelton.
You should not be pushing more than one package with a particular version: packages should be immutable. If you've changed something in the package, increment the build number a.b.C and push a new version of the package.
I hope this aproach fit in your scenario