synd | Opinionated rsync wrapper that respects gitignore files | Incremental Backup library

A -keep option as the one below should do the trick, it prevents ProGuard from removing the class and renaming it. You might see similar issues for different classes and methods show up afterwards, you will need to add a -keep option for those as well.

-keep class com.rometools.rome.feed.synd.impl.ConverterForAtom10

While creating these -keep options try not to use too many wildcards, it will allow ProGuard to better shrink, optimize and obfuscate the code. You can see the impact of your -keep rules in a visual way using the ProGuard Playground.

The most common causes for function strstr() to crash are:

• if one of the provided char* is nullptr,
• if one of the provided char* points to string that has no '\0' terminator.
• if one of the provided char* was subject of a buffer overflow.

There are plenty of other possible causes. If this does not help, provide the code that suffers from the issue.

Better to handle mapping manually to see what's the problem like the following:

The __common_interrupt: 10.55 No irq handler for vector is a firmware issue. Seems you are using AMD CPU I guess? You will want to checkout whether there is a newer version of bios for your motherboard. And update bios should solve this, if not, just wait for it.

And for the mce: [Hardware Error], probably is caused by the above error, but if your system is working fine. It means it's been corrected. But still you can do:

From your comment:

for example if the system timezone is in UTC and rss feed contains the publishedDate as Sat, 28 Mar 2020 13:42:38 IST, the libary parses it to Sat Mar 28 11:42:38 GMT 2020

It took me a bit of investigation, but I have reproduced the behaviour. The problem is that IST is ambiguous: it may mean Irish Summer Time, Israel Standard Time, India Standard Time plus a few other possible time zone abbreviations. A similar ambiguity exists for very many time zone abbreviations, so we should not rely on them. Since you asked for a difference of 5 h 30, I take it that you intended India Standard Time. However, Java interprets IST as Israel Standard Time, which is at offset +02:00 from UTC/GMT. This explains your observed 2 hours difference. It does so even though Israel doesn’t use IST at this time of year, it uses Israel Daylight Time, IDT (at offset +03:00). However, when your default time zone is Asia/Kolkata (India Standard Time), Java does interpret IST to mean this. This explains why you got the expected and correct result in this case.

While fixing this problem in one’s own code would not be too hard, how to persuade your library to do as you want is a different matter. A couple of options come to mind:

1. The best solution is if you can persuade the publisher of your RSS feed not to use IST as time zone. According to the RSS 2.0 specification, the published date should be in RFC 822 format, and according to RFC 822, IST is not a valid time zone. So you have got arguments. From what I have seen, GMT is very often used here and is in agreement with the specs.
2. I don’t know rometools, so there could be possibilities that I don’t know of and which you should investigate if you can. You may of course also file a bug report with the library developers.
3. You may try setting your default time zone to Asia/Kolkata at the time when rometools instantiates the formatter that it uses for parsing. Whether it does this on initialization, on the first call or on every call — make some experiments, or if you want to be sure, inspect the source code on GitHub. If you need to, you can always set the default time zone back to UTC afterward. It’s a very bad hack and not without the risk of occasional incorrect results.

4. If the published date from your RSS feed is always in IST in the sense India Standard Time, you may of course correct the wrong date that you get: