No direct link to the job posting

[hadriandjohari]

Hi,

We, Case Western Reserve University, would like to post a job (Research Computing Technologist 2, job ID 11905) to the hpc.social job posting. We typically ask the user to go to our general career website: https://case.edu/hr/careers, and then search for job ID 11905. I am not sure if this would work properly in the job submission form. I just put https://case.edu/hr/careers in the "Link to Posting", but that might not be enough, right?

Let us know how we can resolve the issue. Thank you.

[vsoch]

hey @hadriandjohari ! I would suggest that you put the job id alongside the title, and then the link with the URL. The reason is because this is a fairly rare format and it would be cumbersome to add an extra field just for (what comes down to) a little extra description. The job would be unique from others that are similar due to that id. If you want to try that out, I can take a look after and see how it looks. Let me know if you have any questions, and thanks for the post!

[hadriandjohari]

Hi, I did submit the job with the job id in the title.
Let me know how it looks from your side.

Another link that can get to the search location directly is This Link.
Thank you!

[hadriandjohari]

Hi, I have submitted the job posting with the job id in the title and the link to the job search webpage. I have not seen the job posted, please take a look. Thank you.

[vsoch]

I don't have time to take a look, but perhaps @alansill can help! I did see it in slack.

[alansill]

It came through on the Slack, Mastodon, and Discord servers (twice each, so I assume it was posted more than once), but I don't see anything since August 24 on the jobs web page itself for some reason.

[vsoch]

@alansill the way to debug this would be to clone and try running the script locally I think, and see what's up!

[hadriandjohari]

I submitted the job twice, please use the second one (the newer one). The first one has a link with an ampersand (&) symbol at the end, which is incorrect. Thanks for your time looking into this. Hadrian

…

On Tue, Sep 19, 2023 at 12:14 PM Vanessasaurus ***@***.***> wrote: @alansill <https://github.com/alansill> the way to debug this would be to clone and try running the script locally I think, and see what's up! — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALOXCYRVKBGRWJTO53MPWL3X3HAGNANCNFSM6AAAAAA4Z5OKJ4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Hadrian Djohari HPC Director, [U]Tech Case Western Reserve University (W): 216-368-0395 (M): 216-798-7490

[alansill]

There are warnings on the "pages build and deployment" saying "github-pages can't satisfy your Gemfile's dependencies."

[vsoch]

yeah let me run it locally quickly, I'm really busy but it's not fair to leave you to work on it. Will report in a few minutes.

[alansill]

I don't understand what I am seeing. The jobs made it to https://github.com/hpc-social/jobs/blob/main/_data/jobs.yaml and all the actions steps completed successfully for these two Case Western jobs, as well as many others, but the page at https://hpc.social/jobs/ is not displaying anything posted past 8/24/2023.

[vsoch]

I don't understand what I am seeing. The jobs made it to https://github.com/hpc-social/jobs/blob/main/_data/jobs.yaml and all the actions steps completed successfully for these two Case Western jobs, as well as many others, but the page at https://hpc.social/jobs/ is not displaying anything posted past 8/24/2023.

It's likely the pinned dependency, testing that now. You are right the jobs automation itself is OK.

[vsoch]

It's not the dependency, and the same renders locally. The data also shows up in the page. My best guess is that something in the data is breaking the javascript after the last job we see.

[vsoch]

This needs some local debugging, I just don't have time soon.

[alansill]

I tried removing some special characters (dashes, commas, single quotes) from the forms data and corresponding identical changes to the jobs.yaml file. It seemed very unhappy about a colon in the job title for one job during htis process until I removed that, but the result even after the automation started passing again is still not producing updated content on he web site.

Putting in page into debug mode in my browser shows some oddities in how the dates show up in the table. Some dates have slash formatting and some do not. I don't know why this is the case.

[vsoch]

That's because it wasn't the underlying issue. I would restore the previous version (it's going to cause a lot of issues to have differences in the data here vs. the sheet) and then start debugging. I already verified that the data yaml is rendering in the page, so what you want to do next (locally) is do a print of the metadata in the jobrows include and see if/why it is stopping. It's either there is a bug there, or with the javascript.

[alansill]

A bit more detail on the change in formatting in the table:

[alansill]

Is there supposed to be a file jobs-previous.yaml in the _data directory? The script seems to make reference to one, but it is not there.

I've gone through the logic and it appears to be going through the whole jobs.yaml file correctly but nothing past 8/24/2023 is detected as needing to be posted to the web page. Note that it does seem to post to the social media sites fine on new entries, though, so it's something to do with how the web pages are being built. It's not an error rendering the page in the browser, either, as far as I can tell.

[vsoch]

@alansill it's generated with the automation action. I have it locally when I run it.

Also, I've run it locally and confirmed the data is complete and renders at the top of the page. As I mentioned earlier, the bug is with how that data is further rendered (or not) into the page.