tzinfo | TZInfo - Ruby Timezone Library | Date Time Utils library

This happens, during the ground-truth-merge job, when the spark can't find any data either in '/opt/ml/processing/groundtruth/' or '/opt/ml/processing/input_data/' directories. And that can happen when either you haven't sent any requests to the sagemaker endpoint or there are no ground truths.

I got this error because, the folder /opt/ml/processing/input_data/ of the docker volume mapped to the monitoring container had no data to process. And that happened because, the thing that facilitates entire process, including fetching data couldn't find any in S3. and that happened because, there was an extra slash(/) in the directory to which endpoint's captured-data will be saved. to elaborate, while creating the endpoint, I had mentioned the directory as s3:////, while it should have just been s3:///. so, while the thing that copies data from S3 to docker volume tried to fetch data of that hour, the directory it tried to extract the data from was s3://////////(notice the two slashes). So, when I created the endpoint-configuration again with the slash removed in S3 directory, this error wasn't present and ground-truth-merge operation was successful as part of model-quality-monitoring.

I am answering this question because, someone read the question and upvoted it. meaning, someone else has faced this problem too. so, I have mentioned what worked for me. And I wrote this, so that StackExchange doesn't think I am spamming the forum with questions.

First of all, the message about DidYouMean is a deprecation warning not an error, it doesn't break your app. It means that usage of DidYouMean::SPELL_CHECKERS is deprecated and will be removed in a future version of ruby. In this case in Ruby 3.3. You shouldn't worry about it until you use versions that are lower than 3.3. It's not your code that triggers the warning. It comes from a gem named Thor. The issue was solved in thor version 1.2.0. You can update the gem by calling bundle update thor.

The actual error comes from the bootsnap gem:

Figured it out through other SO threads and the help of kind people over in the Django Forums.

We first need to make the request include the GET values. If following this tutorial where the request URL is constructed in JS through:

There are only 1000ms in 1 second, do you mean microseconds?

I had a similar problem but resolved by following steps.

1. Run the following command. heroku buildpacks:add heroku/nodejs --index 1
2. Update node version from 16.x to 12.16.2 in package.json.

Here's an O((n log n) + (m log n)) solution (where n is the count of StartTime-EndTime pairs and m is the count of dates event_time_utc to search) that would work whether there are overlapping dates in the yaml file or none.

1. O(n) Get all the StartTime-EndTime pairs

utcnow creates a naive datetime instance, because there was no UTC timezone object when it was introduced in Python. From the documentation for timestamp():

Naive datetime instances are assumed to represent local time and this method relies on the platform C mktime() function to perform the conversion.

Read the docs: https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.read_csv.html

There is no tzinfos parameter in pandas 1.3 pd.read_csv().

I think you need a webpacker.yml file in your apps config file. I also suggest running bundle install and bundle update commands before launching the rails server after you installed a gem. Here's a closed issue similar to your problem; https://github.com/rails/webpacker/issues/940