Jobs | Simple Cron job manager | Cron Utils library

I am trying to get python 3.10.0 installed on my Apple M1 Silicon.

Installing via asdf venv manager. 3.7.9 and 3.9.4 work without any issues but installing 3.10.0 causes the following error:

Github Actions were working in my repository till yesterday. I didnt make any changes in .github/workflows/dev.yml file or in DockerFile.

But, suddenly in recent pushes, my Github Actions fail with the error

Setup, Build, Publish, and Deploy

...

I am trying to run a python async app with an asyncioscheduler scheduled job but the APScheduler fails during build because of this error:

'Only timezones from the pytz library are supported' error

I do include pytz in my app and i am passing the timezone. What is causing the error?

I am calling the asyncioscheduler in a class where i create job manager:

I have run in to an odd problem after converting a bunch of my YAML pipelines to use templates for holding job logic as well as for defining my pipeline variables. The pipelines run perfectly fine, however I get a "Some recent issues detected related to pipeline trigger." warning at the top of the pipeline summary page and viewing details only states: "Configuring the trigger failed, edit and save the pipeline again."

The odd part here is that the pipeline works completely fine, including triggers. Nothing is broken and no further details are given about the supposed issue. I currently have YAML triggers overridden for the pipeline, but I did also define the same trigger in the YAML to see if that would help (it did not).

I'm looking for any ideas on what might be causing this or how I might be able to further troubleshoot it given the complete lack of detail that the error/warning provides. It's causing a lot of confusion among developers who think there might be a problem with their builds as a result of the warning.

Here is the main pipeline. the build repository is a shared repository for holding code that is used across multiple repos in the build system. dev.yaml contains dev environment specific variable values. Shared holds conditionally set variables based on the branch the pipeline is running on.

When switching from Glue 2.0 to 3.0, which means also switching from Spark 2.4 to 3.1.1, my jobs start to fail when processing timestamps prior to 1900 with this error:

Trying to install openssl on homebrew using:

I'm trying to use the github actions for first time, I've created and followed the tutorial from github and my .github/workflows/push_main.yml is :

Ever since I've upgraded my Mac to Monteray, I've been having issues with Vagrant.

Initially, I use to see a vBoxManage error on terminal when running vagrant up. I posted a question on this on SO previously, see here for details.

Today, I uninstalled VirtualBox again (removed VirtualBox VMs folder and moved application to trash) and reinstalled VirtualBox 6.1.3 for OS X hosts` (link here).

I then ran vagrant up on terminal and it successfully compiled:

After seeing the famous green teddy, I tried going to vvv.test but, the page doesn't load. I've tried accessing URLs of sites that have been provisioned before, but they too do not load.

I've also ran vagrant up --debug, and nothing concerning was seen.

My Vagrant version is 2.2.19

Unsure what steps to take next?

Edit:

Steps taken:

1. Have ran vagrant up --provision to provision sites in config.yml file (config.yml file can be seen below)
2. Have tried to access website-dev.test, page doesn't load
3. Have tried to access vvv.test, page doesn't load
4. Have ran vagrant reload --provision and repeated steps 2 and 3, but same results
5. Have ran vagrant halt and vagrant up and repeated steps 2 and 3, but same results

I don't believe there's an issue in my config.yml file, as before Monteray update, everything was working fine (and I've made no changes to my yml file since). But, to cover all scenario's, here is my config.yml file:

I'd like to abstract some of my GitHub Actions with a reusable workflow.

In order to do this, I need to call my newly defined callable workflow in the format {owner}/{repo}/{path}/{filename}@{ref}

e.g. (from the docs)