question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Provide way to deal with distro inconsistencies

See original GitHub issue

There are Linux distros that have ionconsistent information in the data sources that ld uses.

For example , see issue #78 about Linux Mint. In that case, the precedence implemented by ld causes Linux Mint to be shown as an Ubuntu. While it is fairly compatible to Ubuntu, it is not Ubuntu. It has its own name, id, version (Linux Mint 17.3 is based upon Ubuntu 14.04), and code name (“rose” for Linux Mint 17).

I think that instead of asking the distros to become consistent, that calls for some mechanism in ld to deal with that.

We already parse all three data sources if available, and we could find out that the (normalized) IDs are different, and if so, trigger some special-case processing. In the case of Linux Mint, the special processing would be to ignore those data sources that advertise Ubuntu.

I guess the trick is to implement this without getting into endless if-elif-else statements.

Issue Analytics

  • State:open
  • Created 7 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
sethmlarsoncommented, Dec 23, 2021

I’m not sure that this fix is needed though, wouldn’t we see more chatter / +1s on this issue if there were widespread problems with distributions identifying incorrectly? Quoting @nir0s from 2016:

My intuition tells me that a “bug which happens once is not a bug”.

I feel we should place our already limited time+focus on new and non-deprecated platforms instead.

1reaction
brejoccommented, Dec 21, 2021

To make things easier for us and more consistent across multiple tools imo we should treat bugs in /etc/*-release files as bugs upstream instead of something actionable in Distro. Thoughts from other maintainers?

While I would absolutely sympathize with this approach, this might mean that things stay broken for a long time. It’s sometimes hard to motivate distros to change something in their *-release files, and even if they are willing to, the release cycles might be pretty long.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Detect and Fix Data Distribution Inconsistencies for Model ...
Have you come across scenarios where you build a machine learning model and obtain 95% accuracy on test data but when the model...
Read more >
Avoiding the Top 10 Mistakes with Distributor Agreements
There are several methods: First, solicit a model agreement from your industry's distributor association. Many distribution associations provide a model ...
Read more >
How to deal with Errors which are not following Normal ...
1 Answer 1 · okay. thanks. But problem is that I have only target values ( actual values and predicted values for two...
Read more >
Inconsistencies in the Villegas Method of Determining a Prior ...
Villegas proceeds by selecting a pivotal quantity which has a fixed distribution. Since there is nothing unique about this pivotal quantity, we note...
Read more >
5 Common Distribution Agreement Mistakes that Could Harm ...
An effective distribution agreement should include language outlining conditions where termination of the contract is possible and the ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found