Uwe Raabe

I somehow expected that. After catching the first error it is most likely to stumble over the next one. The question is: Did it write something to the log file?

You may have a hard time getting this amount in these days.

You may have to provide a value in ResourceOptions.PersistentFileName to allow storing the structure and data from the last retrieved records when online. If you deploy a basic file with just the structure (best created from an online connection during development) that may fit your needs.

I have uploaded a new beta version that allows to do some logging: MMX Beta Setup There is a new entry in MMX properties MMX Debugging: Enable log to file, close IDE, install CodeSite Tools and restart IDE. Then try the same as before to trigger the exception and look in the given folder for the log file.

To be fair, it at least contains a simple question and thus seems pretty valid for this forum:

Why not using the longer descriptive name for the declaration and then add a shorter type alias later. That way everyone can choose, while the more descriptive name is used by the IDE tooling.

Same here. Unless you are able to provide a reproducible test case we will have hard time to help you.

There are also some code templates in Delphi to simplify writing these comments: summary, params, returns, remarks

As a short time workaround you can use the Trial installed from the ISO. A link for that as well as other information can be found in this blog post: Some Embarcadero Servers Are Experiencing A Hardware Outage

It's not like they did it on purpose.

I just want to emphasize that the DocWiki is not only back again, but also seems to be pretty fast and stable now.

I wish I'd know. There are other cases with a similar error, but I wasn't able to reproduce it, nor could I spot the trigger. In case you can manage to create a reproducible test case I would love to use that for finding the root cause. As long as I am not able to reproduce any code change would be a blind guess.

Actually QP ought to be a subsystem from the internal Jira. The InternalTrackingLink ist a hint for that. One of the reasons to make QP read-only is probably to allow for a final synchronize before moving the internal Jira to the new one.

It may be delayed, but not necessarily. The development systems should be functional even without these servers.

Can you try with Light as the initial theme?

AFAIK, they plan to internally use a cloud based Jira (you won't get any other) while getting rid of the public QP instance in favor of limited public access to the new one. At least that has been discussed for quite a while, because the synchronization between the internal and external instance was error prone and often lagging behind. So the statement that the current system seems to work fine probably didn't take into account the whole picture. On the other hand, as I mentioned in my initial post, such criticism was somehow expected. The same as my expectations are mostly based on speculation, so are others. Personally I just feel better expecting an improvement. So for me it stays to be a good thing until it turns out otherwise.

Are you talking about the Community Edition? That would be the only one I know of available to the public without an ISO.

The blog post recently got an update: https://blogs.embarcadero.com/we-are-experiencing-a-hardware-outage/

If you don't want to have the panel stored to the stream as the parent of its controls, you shouldn't do so: MemStr.WriteComponent(pnlSource); // write component to panel source Compare that to the code writing only the controls: for idx := 0 to pnlSource.ControlCount - 1 do begin MemStr.Position := 0; MemStr.WriteComponent(pnlSource.Controls[idx]); StreamConvert(MemStr); end;

I am even able to compile for industrial Windows XP systems with Delphi 12. Of course one is limited in which features can be used and which cannot, but that would be even more restricted when working with Delphi 7 or Delphi 5. I would rather drop these kind of projects than even think about using such an old Delphi version. Actually I have just one project that is bound to Delphi 2007 in the moment. As long as it is dormant it can stay that way, but I would try to convince the customer to port it to a newer Delphi version once it is going to be resurrected. Otherwise I have to adjust my hourly rate to cover up for the additional stresses and strain.

Not very long in general. It just might not help either if the server doesn't happen to be the root of the outage.

If you did not install from the ISO in the first place or have already changed to online mode before, open a command prompt in the Delphi bin folder and execute getitcmd c=useoffline You can as well change the SeviceKind setting to Offline in the registry in HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\23.0\CatalogRepository (for Delphi 12). There you can specify the path to the gof file from the ISO under ServicePath. Up to here, all this is to tell the Feature Manager where to look for the installation files. Then start the IDE and select Tools - Manage Features. There you can select Help and install it.

DocWiki has a workaround with a local help installation from the ISO. The breakage of GetIt is crucial indeed.

Part of the services are available again. The rest is expected to follow shortly.

As a side note: For quite some time one can find some NexusDB related files in the FireDAC sources, albeit we are waiting for a working NexusDB link since about a similar time frame. Seems it is far from trivial to implement that.