Fixing cases in which the number starts with 0 and is considered base 8

[chiarazampolli]

@shahor02
I am still checking why I had wc -l...

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2022-pp-apass4
async-2023-pbpb-apass
async-2023-pp-apass1
async-data
async-mc
async-2022-pp-apass6

[chiarazampolli]

In this case, -l gives a negative value --> so I take the substring from the end:
e.g.:
3027145464:-9 --> 027145464
-c gives a positive value, and it is used as offset for the substring:
e.g.:
3027145464:1 --> 027145464
So the net result is the same.
I think that -c is better, because -l will always be 1, no matter the length of the proc_id.

[chiarazampolli]

Note that with this script, we don't get the last 10 or 9 digits, as in the comment, but the last 9 (base 32) or 8 (base 16).
To get the last 10 (or 9), we could just use:

ALIEN_PROC_ID_OFFSET_INT32=$((10#${ALIEN_PROC_ID: -10}))
ALIEN_PROC_ID_OFFSET_INT16=$((10#${ALIEN_PROC_ID: -9}))

I will try with more time tomorrow.

[chiarazampolli]

Hello @shahor02 , @davidrohr ,

This seems much better to me. Can you please check?

Chiara

[chiarazampolli]

Hello @davidrohr , @shahor02 ,

Any comment about this PR?

Chiara

[davidrohr]

I didn't test it, but fine with me

[shahor02]

Fine for me