A small tool to view real-world ActivityPub objects as JSON! Enter a URL
or username from Mastodon or a similar service below, and we'll send a
request with
the right
Accept
header
to the server to view the underlying object.
{
"id": "https://discourse.osgeo.org/ap/object/f089e13fc70d6ddcc82cf0d24a00cb70",
"type": "Note",
"audience": "https://discourse.osgeo.org/ap/actor/e12a97a00c04f88ba48156f05cd55220",
"to": "https://discourse.osgeo.org/ap/actor/e12a97a00c04f88ba48156f05cd55220",
"cc": [
"https://www.w3.org/ns/activitystreams#Public"
],
"published": "2025-04-18T15:26:03Z",
"updated": "2025-04-18T15:26:03Z",
"url": "https://discourse.osgeo.org/t/pgrouting-contraction-hierarchies/111686/28",
"attributedTo": "https://discourse.osgeo.org/ap/actor/698c8043a23f42700545ea9c7bd6f21a",
"context": "https://discourse.osgeo.org/ap/collection/23ba824686812042edcb1ff2f421791b",
"content": "<p>Hi @AuBousquet</p><p>Had to do additional work on the <a href=\"https://github.com/pgRouting/pgrouting/pull/2844\">PR 2844</a>.</p><ul><li><p>The code is supposed to go to main repository.</p></li><li><p>And there is a file where a many lines were changed because of formatting (loosing the history of the original developer).</p></li><li><p>The <a href=\"https://github.com/pgRouting/pgrouting/pull/2853\">PR 2853</a> to main:Now the <a href=\"https://github.com/pgRouting/pgrouting/pull/2853/commits/26d5437bb6f56c61aa9145092213380d017684c0\">commit 26d5437b</a> basically has the least changes. (You are authored, I am just committer)</p></li></ul><p>And we use code rabbit so some changes had to be done. as you can see on these <a href=\"https://github.com/pgRouting/pgrouting/pull/2853#commits-pushed-255c4c1\">list of commits</a></p><p>The <a href=\"https://github.com/pgRouting/pgrouting/pull/2854\">PR 2854</a> to develop is just administrative that cherry picks commits from the PR to main, with the difference that the additional commits I made I just squashed them into 1 commit.</p><p>About <a href=\"https://github.com/pgRouting/pgrouting/pull/2846\">PR 2856</a> \"Fixing contraction documentation\": Those aren't fixes those are attempts to promote the functions to become official. We have the policy of new functions to enter as proposed when they are a derivative of some other function In this case they both use the <code>_pgr_contraction</code> code. To make them official they need a motion from the PSC. So they are still proposed as many others until we get a vote for promotion to official.</p><p>Also functions that are not based on already existing functions in the project come as experimental. And a vote for promotion to proposed is needed, then a vote to convert to official is needed after that.</p><p>About <a href=\"https://github.com/pgRouting/pgrouting/pull/2843\">PR 2843</a> you are complicating all the lines. Just a new example on how to pass an specific location of the <code>pg_config</code> file is sufficient. Otherwise in all examples of the <code>cmake</code> lines its missing everything, the build documentation, all the languages we handle all, the type of build etc.The user is to copy the <code>run.sh</code> & <code>taptest.sh</code> to their <strong>root</strong> repository (not to the build repository) and use/adjust them as they see fit to their operative system. (and your changes caused the shell check to fail)</p><p>So I converted to draft, waiting for a simple example of add the specific path to <code>pg_config</code> and removing my name. (Do not force push, at the end it will be squashed)</p><p>RegardsVicky</p><br><br><a href=\"https://discourse.osgeo.org/t/pgrouting-contraction-hierarchies/111686/28\">Discuss this on our forum.</a>",
"inReplyTo": "https://discourse.osgeo.org/ap/object/237b628a6e55644371946e9db866b912",
"@context": "https://www.w3.org/ns/activitystreams"
}