we are using MPP14Reader to read tasks from Microsoft Project, and recently for some of the projects, we are seeing that getOutlineNumber is giving wrong value. (ex: in Microsoft Project OutlineNumber is 1.2 ,
where as task.getOutlineNumber() is resulting in 2.4).
going through MPXJ code, found that this has been fixed in latest release via commit https://github.com/joniles/mpxj/commit/628df2b4a9dc4f00f59c5d8ad1c54648292a5c41
looking at commit description, seems this is happening after Microsoft June Update !!
do we have any workaround here ? can some one please help
Not all projects have this issue, seems to be issue with some of the projects
This issue with MPXJ was recently fixed, as discussed here: https://github.com/joniles/mpxj/issues/107
Related
I noticed that Custom Vision is now returning the message {"code":"NotFoundIteration","message":"Invalid iteration"} instead of the expected (and previously provided) results.
Something has recently changed on the API call?
Thanks
I have seen the same issue happened and the latest news I got from support team is: Problem was identified ; due to recently introduced defect some published models were removed ; after which prediction requests against these published models would fail. The original bug was fixed and a repair program was ran that put back the missing published models. So I think your issue should be fixed now as well. If not, please let us know. Thank you.
Regards,
Yutong
is Azure Fucntion runtime 2.0 released now ? or it is still under preview ? What it is going to be realsed please ?
I coulnd't figure it out. Few MS documents say it is preview and some of the are saying it is alpha released ?
Update
Azure Function 2.0 has been generally available.
The short answer is runtime 2.x is still preview. We can use it in development but not for production. As you may have seen in Azure Document.
You may have seen Alpha release in Azure function host. It is marked as pre-release.
And also you can see Runtime version: 2.0.11651.0 (beta) in Azure portal.
Both of them means runtime 2.x is still preview and will become GA later.
In terms of deprecation, 1.x will continue to exist for a considerable amount of time after 2.x becomes GA. See GitHub issue reply.
I want to know how to apply the issue changes done in the Liferay Issues can be applied in our portal.
For example my issues are cleared in the following links,
https://issues.liferay.com/browse/LPS-14417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
https://issues.liferay.com/browse/LPS-14220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
I want to apply the issue changed in the above links in my portal.
Please some one help me to achieve this.
Thanks in Advance.
Regards,
Dinesh M K
You have to see the resolution and fix version stated.
the second issue says :
Fix Version/s: --Sprint 12/11, 6.1.0 CE RC1
and that means that the issue was solved in all Portals after version 6.1.0 CE.
the first issue , is no longer reproducible, and duplicate of https://issues.liferay.com/browse/LPS-14220 which is again solved in 6.1.0 CE RC1
In other words, If your portal is older than this version, you can't do anything. You'll have to upgrade to version 6.1.0 RC1 or later
It seems that the fixed-in version is a bit weirdly set in those issues - e.g. LPS-14220 is a subtask of a story in LPS-14414, which is stated as completed for 6.2.0. Careful: I did not fully read through all of the issue's descriptions, links and mix what I read with the answer (and comment to) #yannicuLar gave
Basically, this seems to be a new feature. The way to backport it to your installation is to identify the relevant commits (e.g. download the repository from https://github.com/liferay/liferay-portal or https://github.com/liferay/liferay-plugins, identify the relevant commits (they all contain the LPS number), "backport" them (e.g. see if they can just be applied to your codebase or if they need manual adaptation because the whole code changed.
Some features are easier to backport than others, I can't tell about the complexity for this one.
In order to separate your changes from Liferay's core changes, you should try to implement this in plugins (or patched plugins) rather than changing the original code and recompile. Most likely it's only the kaleo-web plugin that's effected, but if there are core changes, you'd be better of having them isolated in plugins.
The simplest (and most futureproof) possibility is to wait a bit for 6.2 (RCs are already out) and upgrade your portal to this version. If you want to stay on a version that gets updates, you should do this soon anyway.
I'm following an Install Guide to IBM Connections 4.0. This guide and many others point to the following Cumulative Release 2 Fix Pack:
4.0.0.0-IC-Multi-TDISOL-CR2-LO72170
All my online searches have failed me and keep referencing a different fix pack part of a later cumulative release.
This is the only fix pack I'm missing for the full IBM Connections 4 Installation.
Please can someone assist me in finding a download link to this Fix Pack.
Connections 4.0 CR4 is also available; this could be used instead of both CR2 and CR3
http://www-01.ibm.com/support/docview.wss?uid=swg21637538
CR3 is released. You should try that instead.
http://www-933.ibm.com/support/fixcentral/swg/doSelectFixes?options.selectedFixes=4.0.0.0-IC-Multi-TDISOL-CR3-LO73535&continue=1
TDISOL is just the method to load the users/sync users.
Note, I had issues with CR2, and used CR1 as a fix. CR3 is an option that should work in your case.
I've recently upgraded my Orchard site to version 1.4. Since I had an source code enlistment I just updated to the latest Default branch, and built and deployed the new version. Since the deployment, my blog is totally missing. Thinking it had something to do with the new Autoroute feature, I enabled the Migrate14 module and migrated to 1.4, but still the blog is totally missing in both the Admin UI and at the site.
Do anyone have any ideas on what might have gone wrong?
Check if you have "Blog" feature enabled, this is the first thing.
Second - please check the logs in /App_Data/Logs for any exceptions being thrown and paste your findings here. This could give us a bit more detail.
Third - try upgrading your source to recent 1.x branch. I've been setting up a site using that one yesterday (also upgraded to 1.4) and everything went smoothly.
See this answer's comments for more information related to solution.