by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 17 05:43
    dkastl closed #1611
  • Sep 17 05:43
    dkastl commented #1611
  • Sep 16 13:34
    ohadmanor commented #1611
  • Sep 16 01:56
    dkastl commented #1611
  • Sep 15 12:44
    ohadmanor labeled #1611
  • Sep 15 12:44
    ohadmanor opened #1611
  • Sep 14 23:09
    dkastl synchronize #1573
  • Sep 14 02:09
    dkastl commented #1610
  • Sep 14 02:09
    dkastl commented #1610
  • Sep 14 02:04
    cvvergara commented #1610
  • Sep 14 02:01
    dkastl commented #1610
  • Sep 14 01:49
    cvvergara commented #1610
  • Sep 14 01:42
    cvvergara commented #1610
  • Sep 14 01:37
    dkastl commented #1610
  • Sep 03 05:18
    dkastl milestoned #1610
  • Sep 03 05:18
    dkastl labeled #1610
  • Sep 03 05:18
    dkastl labeled #1610
  • Sep 03 05:18
    dkastl labeled #1610
  • Sep 03 05:18
    dkastl opened #1610
  • Aug 24 21:41

    cvvergara on develop

    Removed the links from linkchec… (compare)

Vicky Vergara
@cvvergara
We start in 10 minutes
Ashish Kumar
@krashish8

I had created gsoc-ashish branch on the GSoC-pgRouting repository few days back. However, the Travis CI Build is failing for this branch, though the GitHub build is passing. Same thing holds for @rajhim2 branch (edgeContract). Any reasons for this, and/or how to tackle this? The branch is created from the master branch of the main pgrouting repository, so it has the same commits as the master branch.

gsoc-ashish branch: https://github.com/pgRouting/GSoC-pgRouting/tree/gsoc-ashish
GitHub build: https://github.com/pgRouting/GSoC-pgRouting/actions/runs/102626864
Travis CI build: https://travis-ci.org/github/pgRouting/GSoC-pgRouting/builds/686157998

From the Travis Build, I guess this is the main error:
cp: cannot stat '/usr/lib/postgresql/11/lib/libpgrouting-3.0.so': No such file or directory
cp: cannot stat '/usr/share/postgresql/11/extension/pgrouting*': No such file or directory
The command "if [ "$DOCUMENTATION" == "OFF" ]; then make; sudo make install; sudo cp  /usr/lib/postgresql/11/lib/libpgrouting-3.0.so /usr/lib/postgresql/$POSTGRESQL_VERSION/lib/libpgrouting-3.0.so; sudo cp /usr/share/postgresql/11/extension/pgrouting* /usr/share/postgresql/$POSTGRESQL_VERSION/extension; fi" exited with 1.
Vicky Vergara
@cvvergara
I am having problems connecting my camera
and that has my mic
please everyone I want you to say hi
Please open an issue / Please send to user's mailing lists / please send to developer's mailing lists / please ask in stack exchange
find problem -> find solution
open issue -> open PR
Vicky Vergara
@cvvergara
SELECT * FROM pgr_dijkstra('SELECT * FROM edge_table', ARRAY[1,2], ARRAY[3,4]);
1->3, 1->4, 2->3, 2->4
SELECT * FROM pgr_dijkstra('SELECT * FROM edge_table', ARRAY[15], ARRAY[3,12]);
1, 3
1, 4
2, 3
2, 4
15, 3
15, 12
SELECT * FROM pgr_dijkstra('SELECT * FROM edge_table', ARRAY[1,1,2,2,15,15], ARRAY[3,4,2,4,3,12]
paralell => true);
CREATE TABLE foo AS (
sources BIGINT[],
targets BIGINT[]
)
sources | targets
{1,2} | {3,4}
{15} | {3,13}
Vicky Vergara
@cvvergara
```
SELECT FROM pgr_dijkstra(
'SELECT
FROM edge_table', -- edges sql query
'SELECT sources, targets FROM foo' --- combinations query
)
CREATE TABLE bar AS (
source BIGINT,
target BIGINT
)
source  | target
1  | 3
1 | 4
...
SELECT FROM pgr_dijkstra(
'SELECT FROM edge_table', -- edges sql query
'SELECT source, target FROM bar' --- combinations query
)
Vicky Vergara
@cvvergara
source | target
1 | 3
2 | 4
1 | 5
internally:
1 -> 3, 5
2 -> 4
SELECT 1 AS source, 3 AS target UNION SELECT 2,4 UNION SELECT 1,5 ---combinations query
'SELECT source, target FROM bar WHERE family = 1'
Mahmoud SAKR
@mahmsakr
WITH _src(seq1, id1) AS(
SELECT nextval('serial1'), id FROM sample1 limit 100
), _dest(seq2, id2) AS(
SELECT nextval('serial2'), id FROM sample2 limit 100
), srcdest AS(
SELECT id1, id2
FROM _src, _dest
WHERE seq1=seq2
Vicky Vergara
@cvvergara
SELECT * FROM pgr_dijkstra(
$$SELECT * FROM edge_table$$, -- edges sql query
--- the combinations query
$$WITH _src(seq1, id1) AS(
    SELECT nextval('serial1'),  id FROM sample1 limit 100
), _dest(seq2, id2) AS(
    SELECT nextval('serial2'),  id FROM sample2 limit 100
)
    SELECT id1 AS source, id2 AS target
    FROM _src, _dest
    WHERE seq1=seq2
$$);
CREATE TABLE foobar 
WITH _src(seq1, id1) AS(
    SELECT nextval('serial1'),  id FROM sample1 limit 100
), _dest(seq2, id2) AS(
    SELECT nextval('serial2'),  id FROM sample2 limit 100
)
    SELECT id1 AS source, id2 AS target
    FROM _src, _dest
    WHERE seq1=seq2;

SELECT * FROM pgr_dijkstra(
$$SELECT * FROM edge_table$$, -- edges sql query
--- the combinations query
$$SELECT * FROM foobar$$);
Vicky Vergara
@cvvergara
Plan:
  • pgRouting 3.0.0 final release must be done before June starts
  • meanwhile, MobilityDB team works on adding the new pgr_dijkstra overload function
When its ready, and "tested" incorporate to pgRouting and make a 3.1 release with the new function
as experimental
Vicky Vergara
@cvvergara
array[1] ARRAY [3,2] parallel
1 | 2
1 | 3
SELECT source, target FROM foo;
ARRAY[1,2,3,4,5 ..... 1000000] ARRAY[1000000, ...... 5,4,3,2,1]
SELECT source, target FROM foo WHERE target IN (3);
999998, 3
Vicky Vergara
@cvvergara
SELECT ARRAY[1,2,3,4,5 ..... 1000000] AS sources, ARRAY[1000000, ...... 5,4,3,2,1] as targets
Ashish Kumar
@krashish8
When are we having the next meeting? I'm sorry I didn't listen.
Is it Tomorrow Tuesday (19 May), 2pm UTC = 9am in Mexico = 7:30pm in India? @cvvergara
Vicky Vergara
@cvvergara
I didn't set up a date, but just be attentive for the last minute annoucement
Ashish Kumar
@krashish8
Okay. Thanks!
Vicky Vergara
@cvvergara
@krashish8 @rajhim2 @prakashupes please review pgRouting/pgrouting#1349
Vicky Vergara
@cvvergara

Topic: updating your working branch

The master branch has been updated, so you need to update the working branch

  • work on your GSoC-pgRouting clone
  • suppose remotes are:
    • origin your GSoC-pgRouting fork
    • upstream pgRouting repo
    • gsoc the GSoC-pgRouting repo

Steps:

  • If you haven't started coding:

    git fetch gsoc
    git checkout gsoc/<your branch> 
    git checkout -b <branch name>
    git fetch upstream
    git rebase upstream/master
    git push --set-upstream origin <branch name>

    And make a PR from <branch name> to gsoc/<your branch>

  • If you already started coding on branch: <branch name>

    git checkout <branch name>
    git fetch upstream
    git rebase upstream/master
    git push

    And make a PR from <branch name> to gsoc/<your branch>

I will check those PR (in my) tonight

end of topic

Vicky Vergara
@cvvergara
@rajhim2 why are you reverting the merge of the PR on the main repository
Ashish Kumar
@krashish8
@cvvergara I think we should force push in case "If you already started coding on branch: <branch name>"
git push -f
This is because rebasing would reorder the commits history, therefore the remote branch can't be fast-forwarded to local, without a force push.
Vicky Vergara
@cvvergara
yeah I forgot the -f, but that doesnt try to revert the master branch of the main repository
@krashish8 can you make the PR
Ashish Kumar
@krashish8
@cvvergara Done!