I upgraded our JIRA from version 6 to version 6.1. Suddenly the Activity Streams are always empty. It is very annoying for the users who were very dependent on them. So I need to get the activity streams back.
What I have tried so far:
1. Reindexing
2. Creating a new widget for activity stream
What log can I look into to see what is broken? Do I need to create a new filter or something?
Please do not create activitystream-gadget.xml. Instead, remove the gadgets you have now and install the latest versions of each--including the Activity Stream gadget itself.
Please look at your atlassian-jira.log file.
Mostly this is caused by outdated plugins using deprecated (and now removed) classes. Similar thing happened to me when OSUser class was removed due to deprecation and an older plugin still used it.
If you are not able to view the log, try disabling user installed plugins.
Related
My code show this error. I didn't use "flutter_secure_storage" dependency but it shows this error. But the app is working well, What is the reason for this and how to fix this also if didn't fix this, the effect of this error?
flutter_secure_storage is a plugin which uses platform specific APIs to interact with the device.
This warning suggests that it is using a deprecated Java API on the Android device. You can't really fix it unless you know Java and are willing to contribute to the plugin. At the same time, you can safely-ish ignore it for now: even deprecated APIs usually last a long time, and it won't affect any functioning until the underlying API is actually removed.
The best thing to do is regularly check for updates to the package, which might fix this warning.
As the error suggests, the package flutter_secure_storage use the file specified in the error, which in turn use or implements a deprecated API.
You might not use that plugin, but you are using some other plugin that use it.
You are not affected by it now because it is just a warning/information.
You could get affected by it when the depreciation goes to be removed instead. But by that time the package will have been updated. So all you have to do is update the package at a later time when said deprecation has been solved.
I recently upgraded to Flutter 2.0. I have dozens of Flatbuttons that are now deprecated. It's going to take me a few days to fix them all. What are the consequences of shipping an update before then with deprecation warnings? The app still builds and runs fine.
Basically this code will be deleted in future releases of flutter/flutter packages. Most of the time, api's get deprecated when a bug that requires a completely new implementation that will break compatibility or a better implementation that will break compatibility.
Therefore, you can use deprecated code but you should be very careful as they are not maintained and might stop working or deleted in the future. So as long as you are not updating versions you should be fine but it is highly unadvisable.
The problem is that your code will be updated and the flutter will no longer support this widget.
But flutter 2.0 has a tool to help with that. Run the command on your terminal to see what has been depreciated and needs to be updated.
dart fix --dry-run
And execute this other command for fix the depreciated items.
dart fix --apply
For more details about fix, click here
I want to upgrade my existing umbraco version project 4.11.10 to 7.5.4, and i decided to upgrade step by step in incremental manner. When upgrading version 4.11.10 to 6.0.0 using nuget package and replacing old dll files with newer one, i am able to run back end and front end side, but on back end, i am not able to view the list of "content" and list of "document types" from my existing project as well as looks like still it displays ui of back end of older version 4, but when i click on "about us", it displays version 6.0.0 as attached in screenshot, please help me to find out the solution, Thanks :) Check here in attached screenshotCheck here - Content not loading
Upgrading from 4.11 to the newest version of 7 should work, HOWEVER, if you're using custom data types, the chances are that some stuff is going to break, as v7 doesn't use UserControls for DataTypes anymore. Some data types can be straight swapped, some not so much. You should be able to see all the DocTypes and content etc though.
When you've swapped the DataTypes out, you may need to reformat the data to match the new DataTypes so you don't lose any data as well. This is something you'd probably have to do either with the API of directly in the database.
I've written some blog posts on upgrading Umbraco, have a read and see if they help:
http://www.attackmonkey.co.uk/blog/2015/10/upgrading-to-73-part-1-preparation
http://www.attackmonkey.co.uk/blog/2015/10/upgrading-to-73-part-2-the-upgrade
http://www.attackmonkey.co.uk/blog/2015/12/upgrading-to-73-part-3-switching-to-razor
http://skrift.io/articles/archive/umbraco-upgrade-strategies/
This is about sonarqube 5.1 version
I have issue assign plugin and also subscribed to the emails in my profile page. I've done some erroneous SVN commits deliberately to check the email notification settings but it doesn't seem to work correctly. I receive emails sometimes but other times it doesn't work like that.
I know this is not a constructive enough question but I'm really stucked here after trying all the scenarios and going through the documentation.
Any insight would be highly appreciated.
You should uninstall this plugin. It is compatible, but it does not work correctly. The problem is that SonarQube 5.1 introduced core auto assignment (see automatic issue assignment and SONAR-5906). The core functionality & plugin execution order is as follows:
Plugin during the execution assigns issues & collects information to whom he should send e-mails. Next core functionality reassign issues.
Core functionality reassigns issues
Plugin sends emails with incorrect data
See topic on SonarQube mailing list
I am also using SQ 5.1 and Issue Assign plugin works perfectly fine without any issues. You should check your email notification settings.
I upgrade facebook unity plugin from version 4.2.4 to 4.3.3 yesterday.
For the old version, I just add the jar file in project/plugin/Android and add some specific code to use it.
As for the new version, it just give me a whole facebook android project, what am I supposed to do with it?
Compile it to an jar and use it like before?
Export my project and also with FB project then package it in Eclipse?(which is super waste of time everytime)
In fact I tried both:
1 . this is not works anymore, result in some resource id errors.
2 . I did make out a package, but it can not login like it works before in 4.2.4.
Does anyone meet same problem like I did?
I really think A sdk should not give whole prject out, because as a running project, there is too much sdk to add in, we dont have to much time to deal with each plugin everytime. A big company like facebook should make things easier.
BTW: the instructions on Facebook page is old, I could not get useful information from them.
You should be able to just "Build and Run" with the new 4.3.3 version (if you imported the package and left the structure as is. Be sure to clear out the old Facebook SDK before you import this one.) Unity would automatically compile it in with your project.
To answer your questions on why we did this:
The reason why it got switch away from a jar is that in the older version when it was compiled to the jar, it meant the R class had hard-coded resource ids at compile time (of the jar). Unfortunately, when other plugins were introduced into a project, it reorders the resource ids but doesn't adjust the R class within the jar. This would break integration and make integrating Facebook with the other android plugins useless.
The source of the android files were packaged along with it because several developers requested more ways to edit the code to their needs. There's several android plugins for Unity out there and while we do our best to make sure our Unity SDK plays nice with them, there can be cases were a developer would like extra control on how they merge together.
With that said, since you upgraded your project from 4.2.4 to 4.3.3, did you follow the changelog here: https://developers.facebook.com/unity/change-log-4.x/#131013?
Basically what happened was that since importing a package doesn't let us delete old files, there was no way to clean up projects that used the jar method. Keeping them both in the project breaks the android build. This is only a one time migration that should happen again.