Chapter 4: tz_correct KeyError: "CRS_ARR_TIME [while running 'flights:tzcorr-ptransform-157']"

In chapter 4. When I try to run the pipeline in the cloud using the following command ./df07.py --project $PROJECT --bucket $BUCKETNAME --region us-central1, I get the following error after over 70 minutes. For some reason it doesn't find the key CRS_ARR_TIME in the function tz_correct.
I'm following the 2022 version of the book.
Any suggestions on how to approach this?
Regards,
Jakob

Workflow failed. Causes: S18:ref_AppliedPTransform_flights-read-Read-SDFBoundedSourceReader-ParDo-SDFBoundedSourceDoFn-_22/ProcessElementAndRestrictionWithSizing+flights:read/_PassThroughThenCleanup/ParDo(PassThrough)/ParDo(PassThrough)+flights:tzcorr+FlatMap(get_next_event)+flights:bqout/BigQueryBatchFileLoads/RewindowIntoGlobal+flights:tostring+events:totablerow+events:bqout/BigQueryBatchFileLoads/RewindowIntoGlobal+events:bqout/BigQueryBatchFileLoads/AppendDestination+events:bqout/BigQueryBatchFileLoads/ParDo(WriteRecordsToFile)/ParDo(WriteRecordsToFile)+events:bqout/BigQueryBatchFileLoads/IdentityWorkaround+events:bqout/BigQueryBatchFileLoads/GroupFilesByTableDestinations/Write+events:bqout/BigQueryBatchFileLoads/ParDo(_ShardDestinations)+events:bqout/BigQueryBatchFileLoads/GroupShardedRows/Write+flights:bqout/BigQueryBatchFileLoads/AppendDestination+flights:bqout/BigQueryBatchFileLoads/ParDo(WriteRecordsToFile)/ParDo(WriteRecordsToFile)+flights:bqout/BigQueryBatchFileLoads/IdentityWorkaround+flights:bqout/BigQueryBatchFileLoads/GroupFilesByTableDestinations/Write+flights:bqout/BigQueryBatchFileLoads/ParDo(_ShardDestinations)+flights:bqout/BigQueryBatchFileLoads/GroupShardedRows/Write+flights:gcsout/Write/WriteImpl/WindowInto(WindowIntoFn)+flights:gcsout/Write/WriteImpl/WriteBundles+flights:gcsout/Write/WriteImpl/Pair+flights:gcsout/Write/WriteImpl/GroupByKey/Write failed., The job failed because a work item has failed 4 times. Look in previous log entries for the cause of each one of the 4 failures. For more information, see https://cloud.google.com/dataflow/docs/guides/common-errors. The work item was attempted on these workers: ch04timecorr-09010446-lgmu-harness-j021 Root cause: Traceback (most recent call last): File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 837, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1571, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "/home/jakob_salomonsson/data-science-on-gcp/04_streaming/transform/./df07.py", line 87, in tz_correct KeyError: 'CRS_ARR_TIME' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 284, in _execute response = task() File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 357, in <lambda> lambda: self.create_worker().do_instruction(request), request) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 597, in do_instruction return getattr(self, request_type)( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 635, in process_bundle bundle_processor.process_bundle(instruction_id)) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py", line 1003, in process_bundle input_op_by_transform_id[element.transform_id].process_encoded( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py", line 227, in process_encoded self.output(decoded_value) File "apache_beam/runners/worker/operations.py", line 526, in apache_beam.runners.worker.operations.Operation.output File "apache_beam/runners/worker/operations.py", line 528, in apache_beam.runners.worker.operations.Operation.output File "apache_beam/runners/worker/operations.py", line 237, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 1021, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process File "apache_beam/runners/worker/operations.py", line 1030, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process File "apache_beam/runners/common.py", line 1432, in apache_beam.runners.common.DoFnRunner.process_with_sized_restriction File "apache_beam/runners/common.py", line 817, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1581, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "apache_beam/runners/common.py", line 1694, in apache_beam.runners.common._OutputHandler._write_value_to_tag File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 907, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/worker/operations.py", line 908, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/common.py", line 1419, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 1491, in apache_beam.runners.common.DoFnRunner._reraise_augmented File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 623, in apache_beam.runners.common.SimpleInvoker.invoke_process File "apache_beam/runners/common.py", line 1581, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "apache_beam/runners/common.py", line 1694, in apache_beam.runners.common._OutputHandler._write_value_to_tag File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 907, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/worker/operations.py", line 908, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/common.py", line 1419, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 1507, in apache_beam.runners.common.DoFnRunner._reraise_augmented File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 837, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1571, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "/home/jakob_salomonsson/data-science-on-gcp/04_streaming/transform/./df07.py", line 87, in tz_correct KeyError: "CRS_ARR_TIME [while running 'flights:tzcorr-ptransform-157']" , ch04timecorr-09010446-lgmu-harness-hhsk Root cause: Traceback (most recent call last): File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 837, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1571, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "/home/jakob_salomonsson/data-science-on-gcp/04_streaming/transform/./df07.py", line 87, in tz_correct KeyError: 'CRS_ARR_TIME' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 284, in _execute response = task() File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 357, in <lambda> lambda: self.create_worker().do_instruction(request), request) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 597, in do_instruction return getattr(self, request_type)( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 635, in process_bundle bundle_processor.process_bundle(instruction_id)) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py", line 1003, in process_bundle input_op_by_transform_id[element.transform_id].process_encoded( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py", line 227, in process_encoded self.output(decoded_value) File "apache_beam/runners/worker/operations.py", line 526, in apache_beam.runners.worker.operations.Operation.output File "apache_beam/runners/worker/operations.py", line 528, in apache_beam.runners.worker.operations.Operation.output File "apache_beam/runners/worker/operations.py", line 237, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 1021, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process File "apache_beam/runners/worker/operations.py", line 1030, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process File "apache_beam/runners/common.py", line 1432, in apache_beam.runners.common.DoFnRunner.process_with_sized_restriction File "apache_beam/runners/common.py", line 817, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1581, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "apache_beam/runners/common.py", line 1694, in apache_beam.runners.common._OutputHandler._write_value_to_tag File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 907, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/worker/operations.py", line 908, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/common.py", line 1419, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 1491, in apache_beam.runners.common.DoFnRunner._reraise_augmented File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 623, in apache_beam.runners.common.SimpleInvoker.invoke_process File "apache_beam/runners/common.py", line 1581, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "apache_beam/runners/common.py", line 1694, in apache_beam.runners.common._OutputHandler._write_value_to_tag File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 907, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/worker/operations.py", line 908, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/common.py", line 1419, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 1507, in apache_beam.runners.common.DoFnRunner._reraise_augmented File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 837, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1571, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "/home/jakob_salomonsson/data-science-on-gcp/04_streaming/transform/./df07.py", line 87, in tz_correct KeyError: "CRS_ARR_TIME [while running 'flights:tzcorr-ptransform-157']" , ch04timecorr-09010446-lgmu-harness-j021 Root cause: Traceback (most recent call last): File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 837, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1571, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "/home/jakob_salomonsson/data-science-on-gcp/04_streaming/transform/./df07.py", line 87, in tz_correct KeyError: 'CRS_ARR_TIME' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 284, in _execute response = task() File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 357, in <lambda> lambda: self.create_worker().do_instruction(request), request) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 597, in do_instruction return getattr(self, request_type)( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 635, in process_bundle bundle_processor.process_bundle(instruction_id)) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py", line 1003, in process_bundle input_op_by_transform_id[element.transform_id].process_encoded( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py", line 227, in process_encoded self.output(decoded_value) File "apache_beam/runners/worker/operations.py", line 526, in apache_beam.runners.worker.operations.Operation.output File "apache_beam/runners/worker/operations.py", line 528, in apache_beam.runners.worker.operations.Operation.output File "apache_beam/runners/worker/operations.py", line 237, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 1021, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process File "apache_beam/runners/worker/operations.py", line 1030, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process File "apache_beam/runners/common.py", line 1432, in apache_beam.runners.common.DoFnRunner.process_with_sized_restriction File "apache_beam/runners/common.py", line 817, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1581, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "apache_beam/runners/common.py", line 1694, in apache_beam.runners.common._OutputHandler._write_value_to_tag File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 907, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/worker/operations.py", line 908, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/common.py", line 1419, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 1491, in apache_beam.runners.common.DoFnRunner._reraise_augmented File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 623, in apache_beam.runners.common.SimpleInvoker.invoke_process File "apache_beam/runners/common.py", line 1581, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "apache_beam/runners/common.py", line 1694, in apache_beam.runners.common._OutputHandler._write_value_to_tag File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 907, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/worker/operations.py", line 908, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/common.py", line 1419, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 1507, in apache_beam.runners.common.DoFnRunner._reraise_augmented File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 837, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1571, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "/home/jakob_salomonsson/data-science-on-gcp/04_streaming/transform/./df07.py", line 87, in tz_correct KeyError: "CRS_ARR_TIME [while running 'flights:tzcorr-ptransform-157']" , ch04timecorr-09010446-lgmu-harness-hhsk Root cause: Traceback (most recent call last): File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 837, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1571, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "/home/jakob_salomonsson/data-science-on-gcp/04_streaming/transform/./df07.py", line 87, in tz_correct KeyError: 'CRS_ARR_TIME' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 284, in _execute response = task() File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 357, in <lambda> lambda: self.create_worker().do_instruction(request), request) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 597, in do_instruction return getattr(self, request_type)( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 635, in process_bundle bundle_processor.process_bundle(instruction_id)) File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py", line 1003, in process_bundle input_op_by_transform_id[element.transform_id].process_encoded( File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/bundle_processor.py", line 227, in process_encoded self.output(decoded_value) File "apache_beam/runners/worker/operations.py", line 526, in apache_beam.runners.worker.operations.Operation.output File "apache_beam/runners/worker/operations.py", line 528, in apache_beam.runners.worker.operations.Operation.output File "apache_beam/runners/worker/operations.py", line 237, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 1021, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process File "apache_beam/runners/worker/operations.py", line 1030, in apache_beam.runners.worker.operations.SdfProcessSizedElements.process File "apache_beam/runners/common.py", line 1432, in apache_beam.runners.common.DoFnRunner.process_with_sized_restriction File "apache_beam/runners/common.py", line 817, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1581, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "apache_beam/runners/common.py", line 1694, in apache_beam.runners.common._OutputHandler._write_value_to_tag File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 907, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/worker/operations.py", line 908, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/common.py", line 1419, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 1491, in apache_beam.runners.common.DoFnRunner._reraise_augmented File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 623, in apache_beam.runners.common.SimpleInvoker.invoke_process File "apache_beam/runners/common.py", line 1581, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "apache_beam/runners/common.py", line 1694, in apache_beam.runners.common._OutputHandler._write_value_to_tag File "apache_beam/runners/worker/operations.py", line 240, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive File "apache_beam/runners/worker/operations.py", line 907, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/worker/operations.py", line 908, in apache_beam.runners.worker.operations.DoOperation.process File "apache_beam/runners/common.py", line 1419, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 1507, in apache_beam.runners.common.DoFnRunner._reraise_augmented File "apache_beam/runners/common.py", line 1417, in apache_beam.runners.common.DoFnRunner.process File "apache_beam/runners/common.py", line 837, in apache_beam.runners.common.PerWindowInvoker.invoke_process File "apache_beam/runners/common.py", line 981, in apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window File "apache_beam/runners/common.py", line 1571, in apache_beam.runners.common._OutputHandler.handle_process_outputs File "/home/jakob_salomonsson/data-science-on-gcp/04_streaming/transform/./df07.py", line 87, in tz_correct KeyError: "CRS_ARR_TIME [while running 'flights:tzcorr-ptransform-157']"

I think I found the problem. When creating the flights view in BigQuery in an earlier step, I missed typing out one row (see below). As a result, the CRS_ARR_TIME column didn't exist in the view and it could therefore not be accessed in the tz_correct function.

CREATE OR REPLACE VIEW dsongcp.flights AS

SELECT FlightDate AS FL_DATE,
       Reporting_Airline AS UNIQUE_CARRIER,
       OriginAirportSeqID AS ORIGIN_AIRPORT_SEQ_ID,
       Origin AS ORIGIN,
       DestAirportSeqID AS DEST_AIRPORT_SEQ_ID,
       Dest AS DEST,
       CRSDepTime AS CRS_DEP_TIME,
       DepTime AS DEP_TIME,
       CAST(DepDelay AS FLOAT64) AS DEP_DELAY,
       CAST(TaxiOut AS FLOAT64) AS TAXI_OUT,
       WheelsOff AS WHEELS_OFF,
       WheelsOn AS WHEELS_ON,
       CAST(TaxiIn AS FLOAT64) AS TAXI_IN,
       CRSArrTime AS CRS_ARR_TIME,           -- THIS ROW WAS MISSING
       ArrTime AS ARR_TIME,
       CAST(ArrDelay AS FLOAT64) AS ARR_DELAY,
       IF(Cancelled = '1.00', True, False) AS CANCELLED,
       IF(Diverted = '1.00', True, False) AS DIVERTED,
       DISTANCE
FROM `<Project ID>.dsongcp.flights_raw_data`

Awesome! Glad you were able to figure it out.
Instead of typing the code out, you can consider copy-paste from this repo.
Of course, many people prefer to type it out because it helps them think
things through ...
thanks,
Lak
On Thu, Sep 1, 2022, 8:58 PM Jakob Salomonsson @.***>
wrote:

I think I found the problem. When creating the flights view in BigQuery
in an earlier step, I missed typing out one row (see below). As a result,
the CRS_ARR_TIME column didn't exist in the view and it could therefore
not be accessed in the tz_correct function.
CREATE OR REPLACE VIEW dsongcp.flights AS
SELECT FlightDate AS FL_DATE,
Reporting_Airline AS UNIQUE_CARRIER,
OriginAirportSeqID AS ORIGIN_AIRPORT_SEQ_ID,
Origin AS ORIGIN,
DestAirportSeqID AS DEST_AIRPORT_SEQ_ID,
Dest AS DEST,
CRSDepTime AS CRS_DEP_TIME,
DepTime AS DEP_TIME,
CAST(DepDelay AS FLOAT64) AS DEP_DELAY,
CAST(TaxiOut AS FLOAT64) AS TAXI_OUT,
WheelsOff AS WHEELS_OFF,
WheelsOn AS WHEELS_ON,
CAST(TaxiIn AS FLOAT64) AS TAXI_IN,
CRSArrTime AS CRS_ARR_TIME,           -- THIS ROW WAS MISSING
ArrTime AS ARR_TIME,
CAST(ArrDelay AS FLOAT64) AS ARR_DELAY,
IF(Cancelled = '1.00', True, False) AS CANCELLED,
IF(Diverted = '1.00', True, False) AS DIVERTED,
DISTANCEFROM <Project ID>.dsongcp.flights_raw_data
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/data-science-on-gcp/issues/156#issuecomment-1234663444,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANJPZ435IZLFZBC7D32KG3V4D4EBANCNFSM6AAAAAAQCQU5VE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>


open close doors do not update Light sight...

if a door is opened or closed the sight is only updated after some token movement, I believe it is some other module incompatibility, but havent been able to find anything, even disabling all modules except ligthspeed do not solves it..

There's a module called "find the culprit" that'll help you figure out which module is responsible.

Tks! it helped!   it was Less fog.... what a shame.. I liked it...
but like yours more!

Am I understanding you correctly, that lessfog doesn't work properly with Lichtgeschwindigkeit enabled?

Less fog apply normally the reduced intensity of darkness, but for some reason when both modules are on open and closing doors do not update the vision...
like a token is at a closed door and can't see inside, when the door opens, even with light, the area remains dark until the token moves...  but if you close the same door before moving, it reveals the area...
I will try make a video showing this for you

Good to hear!


Open up regex

Updated the regex to be a little more open since other countries have different formats.

Good idea / the regex looks clean to me


How to use this library with Java?

I try to implement library in my project with Java and I faced a problem:
What to write in parentheses mRatingView.setRatingChangeListener(); ? I can't text just a parameters previousRating and newRating like in Kotlin:
ratingView.setRatingChangeListener { previousRating, newRating ->
            emotionView.setRating(previousRating, newRating)
            gradientBackgroundView.changeBackground(previousRating, newRating)
        }

Same, if i want to use in jave , how i will ratingview parameter use


Add get_map_objects_min_distance_meters logic

Implement map objects and interaction distance restrictions via the haversine formula.  Also updated the download settings to be saved on every API call in order to update the restrictions.
The haversine formula is in Utils so it can be used to implement the encounter restrictions also found in the download settings response.  Since the pokemon lat,lng isn't passed into the client, however, that restriction will need to be implemented by the consumer.

There's quite some controversial over this PR but i think everyone is forgetting 2.0 branch. Why are people ignoring it and continuing to develop here?
 How it's used is up to the user. I think this PR goes against that idea entirely.

@MakuraYami: I've removed the interaction range portion of the PR to put to rest some of the controversy.  The 2.0 branch is a month old with little to no progress according to the issue.  Do you have a timeline for release yet?  If you think this belongs there, that is fine, I can move it.
Now, if this is indeed intended to purely be an API client with no additional logic, I would be happy to update the PR to pull out the existing throttling logic based on get_map_objects_min_refresh_seconds.

I just read through https://github.com/cyraxx/pogobuf/issues/54 which is where the throttling was added initially to prevent errors from Niantic.  I will do some more testing on my end with the client, but I believe that the requests can be made faster than the standard 10 second minimum delay so long as it is not being done in the same location and you are moving at a rate of speed faster than 1 meter per second.  If that is the case, scanners that are using this API can be made more efficient by changing the default throttling to include the distance limitations.

What I usually say is that the purpose of the library is to enable you to call API methods while preventing you from getting error messages as much as possible. That's why we have the map objects delay and the retry logic: So you can make your map objects calls without having to worry about rate limiting errors. However, the library still allows you to make API calls that don't make sense or will get you blocked, and it does not implement any "human behavior simulation". So if you make one call that puts you in Europe and then another one right afterwards that puts you in Australia, it will let you do that. It doesn't stop you from always getting 100% perfect Pokémon catches either.
The logic you provided is kind of an edge case. If you do the testing you mentioned and it results in enabling us to decrease delay times while still being as neutral as possible, I'm not against including it. And don't get me wrong, I very much appreciate your contribution either way.
@MakuraYami is also right though: We should focus on getting the 2.0 branch finished and migrate the library to 2.0 instead of keeping the two separate versions. I will make 2.0 my priority before adding major new features that would then only have to be ported to the other branch.

Closing all issues as this repository is no longer being maintained. See README for further information.


Inconsistency between the paper and the code

Hi,
I noticed that there is an inconsistency Eq.9 in the paper (https://arxiv.org/pdf/2210.05144.pdf) and https://github.com/yikangshen/MoA/blob/master/moa_layer/parallel_linear/moe.py#L124C8-L125C69. Could you please clarify which version was used for the numbers in the paper?
Thank you,
Robert

this idea of the paper  copied from the ModuleFormer. even code is the same with it.

Hi Robert,
Normalization can be considered an optional feature. In my experience, using normalization could result in slightly better performance when k=2.
Regards,
Yikang

Can I download it to my computer? Is it the same as this? https://snap-research.github.io/mixture-of-attention/


wet property not available for Convolver in Tone.JS 14.7.77 ?

Hello, and congratulations for this fantastic library.
I'm learning to code while discovering it, so excuse my question if it's something I didn't understand. I'm using Tone.JS v14.7.77, the "wet" property is not available for the Convolver, while it existed in previous versions. How to mix between sound with/without convolver in this case? (I use the convolver to make a reverb).
Thanks

Hello!
Don't know if something has changed between version and that the "wet" property disappeared for some reason but what you could do is to use a CrossFade and then use that as a way to mix between the wet and dry signal.
Read more about how to implement it here:
https://tonejs.github.io/docs/14.7.77/CrossFade

Thanks for the tip, I will try this

This is the updated API going into 14.7 as noted in the CHANGELOG. It seemed better to me to just keep that component simple, but maybe worth adding a ConvolverEffect which behaves similar to the previous Tone.Convolver if there is a demand for it. PRs are very welcome if this is a component that you'd like to add.


add my name

@extwiii, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?

@Roshanjossey Thank you for merging my PR. It is really exciting to know you can involve really popular projects like Freecodecamp, React.js, Redux etc. This tutorial will provide the first step of my journey to join open source community.
Thanks

@extwiii, I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://firstcontributions.herokuapp.com


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
2015ae9 -> d6af6b1

github.com/IBM/go-sdk-core/v5
require
patch
v5.17.0 -> v5.17.3

github.com/gruntwork-io/terratest
require
patch
v0.46.13 -> v0.46.14

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.30.8 -> v1.33.2

go (source)
toolchain
minor
1.21.3 -> 1.22.3

terraform-ibm-modules/common-pipeline-assets
action
minor
v1.21.9 -> v1.22.1

Release Notes

IBM/go-sdk-core (github.com/IBM/go-sdk-core/v5)
v5.17.3
Compare Source
Bug Fixes

request_builder: encode unresolved path string prior to path parameter insertion (#219) (5f567da)

v5.17.2
Compare Source
Bug Fixes

errors: flatten sdk problem chains to reduce hash complexity (#218) (9fc1ebc)

v5.17.1
Compare Source
Bug Fixes

use correct error variable in external auth case (#217) (0b70d7d)

gruntwork-io/terratest (github.com/gruntwork-io/terratest)
v0.46.14
Compare Source
Modules affected

opa

Description

Updated go-getter to 1.7.4

Related links

https://github.com/gruntwork-io/terratest/pull/1404

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.33.2
Compare Source
Bug Fixes

nil to NULL (#814) (3522e90)

v1.33.1
Compare Source
Bug Fixes

bugs (27bbbf0)

v1.33.0
Compare Source
Features

enhancements to cloud project and stack testing (#812) (a8342e2)

v1.32.0
Compare Source
Features

added variable for passphrase protected ssh keys. (#771) (8dee786)

v1.31.9
Compare Source
Bug Fixes

Logging improvements (#807) (11a3f1a)

v1.31.8
Compare Source
Bug Fixes

deps: update gomod (#809) (5f06800)

v1.31.7
Compare Source
Bug Fixes

deps: update gomod (#804) (0ba3b0c)

v1.31.6
Compare Source
Bug Fixes

deps: update gomod (#802) (efcfa2f)

v1.31.5
Compare Source
Bug Fixes

ensure all stack members are listed in the stack order (#800) (04e23c7)

v1.31.4
Compare Source
Bug Fixes

enhance error message (#799) (0409a07)

v1.31.3
Compare Source
Bug Fixes

update log messages (#798) (c1f41db)

v1.31.2
Compare Source
Bug Fixes

minor projects fixes (#797) (cfe0774)

v1.31.1
Compare Source
Bug Fixes

update stack input handling (#796) (99dbf4e)

v1.31.0
Compare Source
Features

alpha projects/stacks support (#793) (d0a6052)

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.22.1
Compare Source
Bug Fixes

fix permissions required for GH Pages Release pipeline (#684) (d1434dc)

v1.22.0
Compare Source
Features

add pages release action (#681) (f06fe28)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 1.7.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


chore: sets minimum node.js version

Fixes #16
This sets the minNodeVersion property in the projen config.
Node 18.20.2 was chosen as it is the latest LTS of Node.js 18 as of the creation of this PR.
Please feel free to discuss the usage of other versions below so that the best decision can be made.
It would be great to use 18.x as the minNodeVersion but as far as I can tell it is not possible using projen config.

Is there a good reason to choose LTS?
Do we need any node features from this specific version?
I'd recommend setting it to the lowest realistic version we could support. Or even better, align with the cdk project.

It would be great to use 18.x as the minNodeVersion but as far as I can tell it is not possible using projen config.

(Except to talk about whether 18.x is better or 18.20.2 or some other version...)
If we want to do the same thing as 18.x, how about the following?

AwsCdkConstructLibrary in .projenrc.ts

  workflowNodeVersion: '18.x',
  minNodeVersion: '18.0.0',

It would be great to use 18.x as the minNodeVersion but as far as I can tell it is not possible using projen config.

(Except to talk about whether 18.x is better or 18.20.2 or some other version...)
If we want to do the same thing as 18.x, how about the following?

AwsCdkConstructLibrary in .projenrc.ts

  workflowNodeVersion: '18.x',
  minNodeVersion: '18.0.0',

Ah nice!
I was worried that it was changing the build.yml.
This solves it 😄


Chrome 75.x: Package is invalid: 'CRX_REQUIRED_PROOF_MISSING'

Hello all,
Thanks so much for your work on this amazing package!
Seems like Chrome 75 doesn't like it when crx-generated extensions are sent for download by the server. When trying to download crx files within Chrome, the download fails and the following message is displayed:
Package is invalid: 'CRX_REQUIRED_PROOF_MISSING'

Chrome: 75.0.3770.80 (Official Build) (64-bit)
OS: MacOS High Sierra
The crx is sent for download by sending the following headers:
Content-type: application/x-chrome-extension
Content-disposition: attachment; filename=something.crx
<-- crx file -->

Any idea what changed and how we can support the new version of Chrome?

Found a workaround, sending a different Content-type but still saving the file with the .crx extension:
Content-type: application/octet-stream
Content-disposition: attachment; filename=something.crx
<-- crx file -->

Not sure anout Windows 10 , but on my Work pc ( osx) I still get this:

@realjax Are you trying to generate a new extension here?
https://applicationize.me/now
It works for me now on Chrome 75 using the workaround above.

@eladnava, @realjax according to documentation about linux hosting, extension has to specify update_url in its manifest.json file, which respondes with XML file/data: https://developer.chrome.com/extensions/linux_hosting#update_url

According to documentation, Chrome does not allow installing CRX from outside of their store, unless in developer mode or through enterprise policy: https://developer.chrome.com/extensions/hosting_changes, or on Linux (it's mentioned at the beginning of linux_hosting i linked in my previous comment).
So that may be a reason, because in their source, proof missing error is returned only if either public key is missing, or "required key" is missing:
https://github.com/chromium/chromium/blob/c48c9b176af94f7ec65e20f21594524526d2a830/components/crx_file/crx_verifier.cc#L178
"required key" seems to be their predefined key:
https://github.com/chromium/chromium/blob/c48c9b176af94f7ec65e20f21594524526d2a830/components/crx_file/crx_verifier.cc#L134
and
https://github.com/chromium/chromium/blob/c48c9b176af94f7ec65e20f21594524526d2a830/components/crx_file/crx_verifier.cc#L42
I'm guessing that's the public part of Chrome Web Store key? There's no easy or even "practical" way to create signature that will match their key.
So, either it's the missing Chrome Web Signature key, or something is wrong with how we create signature using developer's key.

When i drag&dropped tiny test CRX onto Chrome's window (onto default new tab) i got the same error.
When i drag&dropped it onto a tab opened on chrome://extensions/ it worked OK.
@eladnava @realjax can you check that too?

Hi @ahwayakchih,
Chrome used to allow downloading CRX files via HTTP file download (using application/x-chrome-extension mime-type).
Chrome 75 broke that, but .crx files can still be downloaded, just the Content-type header needs to be changed:
Content-type: application/x-chrome-extension

This is the workaround we used, we can close this issue.

Hey guys, I'm receiving this issue with the same version of chrome but not when downloading a CRX file. I pack my extension via Chrome's "Pack Extension" button on the extensions page. When I double click the crx file I just create, it gives me the error CRX_REQUIRED_PROOF_MISSING.
I'm in developer mode, and could use some advice. The end goal is to load the extension into a Selenium automated browser. Even though I'm loading the extension into Selenium, it's not appearing and I believe this is the cause. Any thoughts?

@stephenarifin According to documentation, Chrome on Windows blocks installing CRX if it's not from their web store. But you may still work around that using policies (look for "chrome policy force_install") and webserver that serves both CRX and XML files.
Or test using data from ZIP file instead of full CRX file (look for "Testing Chrome Extensions with Selenium" article from 28th of January 2019) - but i did not test that, so i don't know if that works with latest Chrome.
Or test on Linux - documentation mentions that it's allowed to install CRX on Linux (or maybe on Windows too, but using Chromium instead of Chrome?), if it is served with proper headers.

@ahwayakchih, thanks for the response. To be clear, I'm actually using MacOS and not installing the extension from a web server. This is a local dev copy of an extension i'm developing.

@stephenarifin what happens when you go to chrome://extensions page, switch developer mode on and drag and drop CRX file into the window?
Here, on Linux with Chromium, i get confirmation dialog, click "Add extension" and it installs OK.
But when i drag & drop CRX file on some other page, it shows CRX_REQUIRED_PROOF_MISSING error, even after i click "continue" on warning dialog.
But it should be possible to force_install it through policy file created in correct directory. After starting the browser, extension should already be installed.
Check this for Mac:

https://support.google.com/chrome/a/answer/7517624?hl=en&ref_topic=9023246
https://www.chromium.org/administrators/mac-quick-start

@ahwayakchih, if I drag and drop the CRX file into the extension window, I get the confirmation dialog and installs correctly. However, if I double click the CRX file, I get the CRX_REQUIRED_PROOF_MISSING error. If I drag and drop the CRX on another page that isn't extensions, nothing happens.

@stephenarifin OK, so for checking manually if CRX file works, you can still install it through extensions window. CRX_REQUIRED_PROOF_MISSING error is about missing signature from Chrome's web store AFAIK, so if it installs through extensions window, file is valid, just unsigned.
To test if extension works after it's installed, you may try using ZIP file or a path to extension's directory (the one with sources, manifest.json file, etc...). It works with Puppeteer, so maybe it will also work with Selenium (sorry, i don't use Selenium, so i can't be sure).
To automate testing if CRX file is valid, without emulating user interaction, use policy file - it won't install CRX file that is somehow invalid. I'm currently working on setting that up with Docker and Alpine Linux.
As for allowing end-users to install it... i don't know. If you can control environment, e.g., you work in corporate IT, you can use policy files and internal web server. Otherwise, if you do not want to distribute extension through Google's web store... AFAIK the only way is to ask users to go to extensions page and install CRX there (unless you find Google's private key).

@stephenarifin check these:

Configuring policy files on Mac: https://www.chromium.org/administrators/configuring-policy-for-extensions#TOC-Mac
Enabling installing CRX from custom URLs: https://www.chromium.org/administrators/policy-list-3#ExtensionInstallSources

So, for Mac, to enable installing local CRX files, plist file could be like (not tested!):
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.google.Chrome.ExtensionInstallSources</key>
    <array>
      <string>file:///*</string>
    </array>
    </dict>
</plist>

I just tested that on Linux (using JSON policy file at /etc/chromium/policies/managed/test_policy.json), and it worked OK: i got confirmation dialog, just like the one on the extensions page in developer mode, clicked "Add extension" and got extension installed.


Datatype RFCTYPE_DECF34

We want to call a function that returns a table. In this table, a field has the data type RFCTYPE_DECF34.
The call fails with the error message:
Unknown type for parameter KAQTY.
It comes from rfc_parameters.c:rfc_get_field_value.
Is it possible to implement support for this data type?

I will have a look at this.

Support for DECFLOAT16 and DECFLOAT34 is now in master.
Both types are mapped to PHP strings to prevent rounding errors.

Great! I have tested it under Linux.
It's working as expected.


Set CUTTING_EDGE to release-0.8

This will ensure shipyard scripts use release-0.8 images for testing and
such.
This should pass E2E once corresponding PRs are merge to release the images
Signed-off-by: Mike Kolesnik<EMAIL_ADDRESS>

I guess it needs rebase, but no update button

Closing in favor of https://github.com/submariner-io/shipyard/pull/455


Use bedtools's own little test utility instead of samtools in the test suite

Now that bedtools uses htslib, it's easy to write a small utility to use in the test suite instead of invoking a separately-installed samtools.
This is something I started a while ago when (IIRC) I noticed that the test suite couldn't distinguish which of SAM/BAM/CRAM bedtools might be outputting, as samtools autodetects any of the three; and also that all the 2>/dev/null was less than ideal when things went wrong. It's more relevant now that command-line option changes in samtools 1.10 would require adding --no-PG to some of the tests in test/intersect, which would then not work with earlier versions of samtools — see PR #817.
Also a few minor tidy ups in the test suite. Supersedes and closes #817, and fixes one of the problems in #814.

Thanks for doing this @jmarshall! Do you think we also update the local version of htslib that @38 created to HTSlib 1.10.x?


Add a "working-directory" input

Hi,
Thanks for your work on this github action ! I made a small update to fit my use case where I needed to execute the jest command in a subdirectory. I added a working-directory input. This may interest someone else. I also noticed 2 small mistakes that I fixed.
Here's the list of what I've done :

[x] Add a working-directory input
[x] Add missing documentation for only-changes input
[x] Fix documentation about jest-command which is optional
[x] Add a % sign in the comment
[x] Handle unwanted lines deletion at the beginning of the comment

Wow, this is great, I appreciate this. 😄😄

Oh thanks for merging ! :)


Android OpenCL sample

A way of processing camera preview images with OpenCL via OpenCV's TAPI.
Also shows a way of working with the recent Camera2 API.

:+1:


Server returns "Not Found"

Hi
I cloned it and deployed it to Vercel.(https://vitesse-suspense-test.vercel.app/)
I recognized this App was in SSR, but index.html(Inspect → Source) returned from server didn't include any content.
I assume that this problem comes from the failure of rendering.
Does anyone know how to fix this.

Not found

@takechihorn Hi! Not sure what the problem is in your project but you can have a look at this example using suspense with vite-ssr: https://github.com/frandiox/vite-ssr/issues/8
Also, one problem I noticed with<EMAIL_ADDRESS>and async setups, you need to call useHead function before having any await in the setup. Otherwise it will tell you something like "you forgot to call app.use(head)".
Please tell me if you can fix it following that information.

@frandiox
Thank you for your response. I cloned your project and tried
pnpm build
pnpm deploy
https://vitesse-suspense-test.vercel.app/
useHead was already set at App.vue.
app.use(head) was also set at main.ts.
However, It returned HTML below.
I can't understand why it doesn't offer correct  HTML.

Not found

@takechihorn I've checked your code and I think you need to move Suspense to App.vue like in the issue I linked in my previous comment 🤔

@frandiox
Thank you for checking my code.
Though I moved Suspense to App.vue, Not Found wasn't disappeared.
I don't understand what's going on.  Please tell me if it was wrong.
https://vitesse-suspense-test-takechihorn.vercel.app
https://github.com/takechihorn/vitesse-suspense-test

@frandiox and @takechihorn I think I am seeing a similar issue.  I am doing the following:
git clone ...
pnpm install
pnpm build

These steps all work:
❯ pnpm build

> @ build /Users/chujanen/Documents/code/testing/vitetest/my-vitesse-app
> pnpm clean && cross-env NODE_ENV=production vite-ssr build && ./scripts/move-dist.sh

> @ clean /Users/chujanen/Documents/code/testing/vitetest/my-vitesse-app
> rm -rf dist && rm -rf serverless/public && rm -rf serverless/api/renderer

vite v2.1.5 building for production...
✓ 82 modules transformed.
dist/client/index.html                    1.11kb
dist/client/manifest.webmanifest          0.38kb
dist/client/registerSW.js                 0.13kb
dist/client/manifest.json                 3.36kb
dist/client/ssr-manifest.json             5.20kb
dist/client/assets/README.772426b8.js     0.96kb / brotli: 0.38kb
dist/client/assets/[...all].a1bf4aa7.js   0.25kb / brotli: 0.18kb
dist/client/assets/about.68c39e47.js      1.57kb / brotli: 0.56kb
dist/client/assets/[name].49adc410.js     1.44kb / brotli: 0.74kb
dist/client/assets/home.2278cad3.js       0.38kb / brotli: 0.24kb
dist/client/assets/en.ba60c5c3.js         0.74kb / brotli: 0.25kb
dist/client/assets/404.131333f2.js        1.12kb / brotli: 0.57kb
dist/client/assets/es.7e7714ee.js         0.76kb / brotli: 0.29kb
dist/client/assets/fr.1173ee0c.js         0.77kb / brotli: 0.29kb
dist/client/assets/it.f960f036.js         0.76kb / brotli: 0.29kb
dist/client/assets/ja.c3e907af.js         0.69kb / brotli: 0.32kb
dist/client/assets/ko.2cf3595f.js         0.67kb / brotli: 0.31kb
dist/client/assets/tr.3a5ea217.js         0.75kb / brotli: 0.32kb
dist/client/assets/vi.cd0bd6ab.js         0.52kb / brotli: 0.27kb
dist/client/assets/zh-CN.1e1b42d2.js      0.66kb / brotli: 0.28kb
dist/client/assets/index.a133aadc.css     17.60kb / brotli: 3.59kb
dist/client/assets/index.8fe815a1.js      39.51kb / brotli: 12.58kb
dist/client/assets/vendor.f81e899f.js     74.75kb / brotli: 25.97kb
vite v2.1.5 building SSR bundle for production...
[plugin:replace] @rollup/plugin-replace: 'preventAssignment' currently defaults to false. It is recommended to set this option to `true`, as the next major version will default this option to `true`.
✓ 51 modules transformed.
dist/server/manifest.webmanifest   0.38kb
dist/server/registerSW.js          0.13kb
dist/server/main.js                75.04kb

But when I look in my dist/client directory, the index.html is missing.
Shouldn't it be there?  Is there something I am not understanding?

I am also try to deploy to vercel with no luck. Everything works perfectly with pnpm preview, but I have never been able to deploy successfully.
I wonder if it has to do with the build commands. But as @chujanen says, I can't find an index.html in client, after running pnpm build (which runs vite-ssr build)

@chujanen @nicholasoxford Did you install dependencies also in serverless directory?
Vite is not bundling some dependencies so for now we need to install them separately there as well. Use npm there instead of pnpm since I don't think Vercel supports the latter.

But when I look in my dist/client directory, the index.html is missing.
Shouldn't it be there? Is there something I am not understanding?

This is expected, the index.html is "embedded" in the server code.
Other than that, I just deployed this template yesterday and didn't have any issue 🤔
Does it work for you if you try to deploy this without modifying anything?

I tried npm install on my project and got the same results. I tried from a blank template and got:

I tried what you said on both the repo I am working on and a fresh one with the same results.  I shared repo access to my local project.

@nicholasoxford can you see anything in the logs?

23:53:26.329  	Retrieving list of deployment files...
23:53:27.984  	Downloading 43 deployment files...
23:53:28.315  	Analyzing source code...
23:53:28.752  	Installing build runtime...
23:53:29.276  	Build runtime installed: 523.134ms
23:53:29.870  	Installing build runtime...
23:53:30.387  	Build runtime installed: 516.633ms
23:53:30.979  	Installing build runtime...
23:53:31.506  	Build runtime installed: 526.435ms
23:53:32.097  	Installing build runtime...
23:53:32.596  	Build runtime installed: 499.619ms
23:53:33.188  	Installing build runtime...
23:53:33.738  	Build runtime installed: 550.699ms
23:53:34.328  	Installing build runtime...
23:53:34.852  	Build runtime installed: 524.144ms
23:53:37.312  	Looking up build cache...
23:53:37.455  	Looking up build cache...
23:53:37.456  	Looking up build cache...
23:53:37.518  	Looking up build cache...
23:53:37.518  	Build cache found. Downloading...
23:53:37.570  	Build cache found. Downloading...
23:53:37.599  	Looking up build cache...
23:53:37.601  	Build cache found. Downloading...
23:53:37.623  	Build cache found. Downloading...
23:53:37.741  	Build cache found. Downloading...
23:53:37.959  	Build cache downloaded [2.39 MB]: 443.83ms
23:53:38.042  	Build cache downloaded [2.39 MB]: 418.98ms
23:53:38.057  	Build cache downloaded [2.39 MB]: 487.431ms
23:53:38.106  	Build cache downloaded [2.39 MB]: 504.357ms
23:53:38.155  	Build cache downloaded [2.39 MB]: 417.26ms
23:53:39.024  	Installing dependencies...
23:53:39.217  	Installing dependencies...
23:53:39.426  	Installing dependencies...
23:53:39.473  	Installing dependencies...
23:53:39.532  	Installing dependencies...
23:53:39.901  	npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
23:53:40.057  	up to date in 0.262s
23:53:40.073  	9 packages are looking for funding
23:53:40.073  	  run `npm fund` for details
23:53:40.615  	npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
23:53:40.836  	up to date in 0.34s
23:53:40.856  	9 packages are looking for funding
23:53:40.856  	  run `npm fund` for details
23:53:41.453  	npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
23:53:41.466  	Uploading build outputs...
23:53:41.648  	up to date in 0.322s
23:53:41.668  	9 packages are looking for funding
23:53:41.668  	  run `npm fund` for details
23:53:42.029  	Deploying build outputs...
23:53:42.434  	npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
23:53:42.676  	up to date in 0.491s
23:53:42.700  	9 packages are looking for funding
23:53:42.700  	  run `npm fund` for details
23:53:43.168  	Uploading build outputs...
23:53:43.230  	Uploading build outputs...
23:53:43.415  	npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
23:53:43.672  	up to date in 0.422s
23:53:43.695  	9 packages are looking for funding
23:53:43.696  	  run `npm fund` for details
23:53:43.736  	Deploying build outputs...
23:53:43.980  	Deploying build outputs...
23:53:44.518  	Uploading build outputs...
23:53:44.728  	Uploading build outputs...
23:53:45.079  	Done with "api/get-page-props.js"
23:53:45.116  	Installing dependencies...
23:53:45.186  	Deploying build outputs...
23:53:45.273  	Deploying build outputs...
23:53:45.328  	Done with "api/index.js"
23:53:45.807  	up to date in 0.239s
23:53:45.824  	9 packages are looking for funding
23:53:45.824  	  run `npm fund` for details
23:53:46.475  	Done with "api/renderer/main.js"
23:53:46.480  	Done with "api/stripe-checkout.js"
23:53:46.603  	Uploading build outputs...
23:53:47.130  	Deploying build outputs...
23:53:48.296  	Done with "api/get-aws.js"
23:53:49.766  	Uploading build outputs...
23:53:50.862  	Deploying build outputs...
23:53:51.646  	Done with static build
23:53:53.911  	Build completed. Populating build cache...
23:53:54.995  	Uploading build cache [2.39 MB]...
23:53:55.137  	Build cache uploaded: 141.888ms
23:53:55.349  	Done with "api/get-images.js"

@nicholasoxford Is this your site? 😛  https://dreamland-test-frandiox.vercel.app/
Problems

Use import.meta.env.xxx instead of process.env.xxx
As mentioned earlier, you need to add dependencies to serverless/package.json. It was missing @stripe/stripe-js

For the next time, you can just check the runtime logs in Vercel (not the build, but the runtime -- Tab called "Functions"). This part was showing errors saying "did you forget to add @stripe/stripe-js to dependencies?"
@chujanen Please check if you have the same issue.
I think Vercel was adding support for pnpm, things should be simpler when that happens since we can just copy the lock file automatically.

That worked! Thank you!!! Makes sense I have to check the functions tab.
Is this the right syntax?

That worked! Thank you. Makes sense to check the function tab.
I really appreciate your help 🤗
Is this the right syntax?

Yeah, you can see Vite docs here: https://vitejs.dev/guide/env-and-mode.html#env-files

@frandiox -- I am attempting to serve this up on my own Docker container (I was going to use Express)... so that is why I was looking for the index.html.  Does my use case not fit in here?

@chujanen It should work the same way. There's an Express.js example here. In that example you can see that anything that doesn't match /api will be rendering an HTML page. That renderPage function has a copy of the index.html inside, basically.

For env varibales, do I need to import them in the index.js? I keep getting this error, no matter where I place the import statement

@nicholasoxford You need import.meta only in Vite environment. In the cloud functions environment you still need process.env.


ComponentDefinition view should link to the Sequence view

Rather than showing the sequence on the CD view, instead link to the sequence view.  In this case, could remove the Download FASTA also.  This also adds support for multiple sequences.

Done


Update the content type of JSONResponseMixin to 'application/json; charset=utf-8'

Created a new pull request - https://github.com/brack3t/django-braces/pull/162

Done


IMAP settings greyed out

I have 2 phones. On one, I configured the IMAP settings for my Gmail account, and it works as expected. On the other phone, when I select "Custom IMAP server", all IMAP settings are greyed out, so I cannot configure them.

Android 6.0.1
Samsung A3 (SM-A300FU)
SMS Backup+ version 1.5.11

I have to admit I'm quite puzzled by this.
While I investigate, please upgrade to beta-release of the version (1.6) and let me know if that fixes the problem.

First install today went smoothly on phone including setting of custom IMAP (gmail server). However my newly created calendar was not listed. As an experiment I created several calendars with varying security and sharing settings but still no luck with detection even after restarting phone.
After reinstalling SMS Backup+ as next test, custom IMAP settings are greyed out.
Hmmm!
Android 6.0.1
Samsung S5
SMS Backup+ version 1.5.11

can confirm working in beta 2 as clean install, as update to 1.5.11 password was not being stored. I have not tried reinstalling and would be a couple of days before am able.
Android 6.0.1
Samsung S5
SMS Backup+ version 1.5.11 to 1.6.0-BETA2

Something worth checking…
Calendar access requires XOAUTH separate from the IMAP login; logging the phone into the account, such as via Chrome or the Email client.
(If that doesn't work, some folk find that logging using Firefox helps, though it's unclear why that makes a difference.)


Changes in cloudformation template get reverted when trying to push to the cloud

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v20.10.0
Amplify CLI Version
12.12.0
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
I made some changes specifically to the guest access for the getObject action for amplify storage. After updating this in cloudformation-template.json, I attempted to do an 'amplify push' but instead of pushing these changes it only pulls and reverts back to what it was before. It seems like it doesn't recognize these changes I made here:
          {
              "Action": "s3:GetObject",
              "Effect": "Allow",
              "Resource": [
                {
                  "Fn::Join": [
                    "",
                    [
                      "arn:aws:s3:::",
                      {
                        "Ref": "S3Bucket"
                      },
                      "/public/*"
                    ]
                  ]
                },
                {
                  "Fn::Join": [
                    "",
                    [
                      "arn:aws:s3:::",
                      {
                        "Ref": "S3Bucket"
                      },
                      "/protected/*"
                    ]
                  ]
                }
              ]
            },

Expected behavior
I expect this change to be recognized and then pushed to the cloud
Reproduction steps

make a change in the getObject policy in cloudformation-template for storage
attempt to 'amplify push' these changes

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey, thank you for reaching out. If you are looking to modify the storage config i would suggest using the Amplify overrides to make the changes.
https://docs.amplify.aws/gen1/nextjs/build-a-backend/storage/modify-amplify-generated-resources/
Amplify CLI runs a pull before the push ensuring the local copy is in sync with the current-cloud-backend, the override provides the capability to modify the CloudFormation template on resources such as auth and storage using cdk.

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue


[Feature request] Shards should track their last modified (wall) time

Feature Request
Proposal:
When I run SHOW SHARDS, I would like to see the wall time of the last time a shard was modified (either data inserted or deleted). Currently this information is not available through InfluxQL.
Use case:
To assist with incremental backup and restore, seeing when a shard was last modified would inform the operator whether a single shard's backup needs to be updated or whether it is still up-to-date.
If a shard's end time is in the future, it will typically need to be re-backed up. But for old shards, there's no simple way to know if a backup is still in sync or whether old data has been modified.

I think this might be possible by just using the mtime of the latest mtime within the folder.

#7651 exposes the underlying data.  Query language could be updated now.

A few notes about this. @jwilder thinks this should be used to improve incremental backup rather than forcing an operator to look up the times with SHOW SHARDS so we may want to add that functionality as part of this. I'm not aware of what we would have to do to make that happen, but it seems like a decent idea that should be written down.
For the original proposal, there's a little bit of an issue that may be the case when it comes to this. There's no way to send back a time in the JSON without using either a string or an integer. So I'm not sure which one of these to send back. Sending back an integer, while probably better, may be an issue in that the client won't know to convert that integer into a time value for pretty print displays.


CMAKE_ARM_COMPILER is not a standard cmake variable

The CMAKE_ARM_COMPILER variable is not a standard cmake variable according to the documentation here: https://cmake.org/cmake/help/v3.16/manual/cmake-variables.7.html
This should be cleaned up in the cmake files.

Fixed by #622.


Make repository optional in config-mako

Make repository to be optional in config-mako configmap, since it's only required for Github operations. This PR is unblocking eventing since they don't want setting up alert for now.
/cc @adrcunha
/cc @chaodaiG
/cc @grantr

Ping for approval :-)
Thanks

/unassign
/assign @adrcunha

/lgtm
/approve


Bug in EIGEN_ALIGN16

There is a known bug in EIGEN_ALIGN16 in PCL: https://github.com/leggedrobotics/tensorflow-cpp/blob/master/ISSUES.md
Due to the bug, the clang-tidy make the following CRITICAL warning
expected ';' after struct

'alignas' attribute only applies to variables, data members and tag types

in https://github.com/tier4/nebula/blob/main/nebula_common/include/nebula_common/point_types.hpp
struct PointXYZIR
{
  PCL_ADD_POINT4D;
  float intensity;
  uint16_t ring;
  EIGEN_MAKE_ALIGNED_OPERATOR_NEW
} EIGEN_ALIGN16;
...
struct PointXYZIRADT
{
  PCL_ADD_POINT4D;
  float intensity;
  uint16_t ring;
  float azimuth;
  float distance;
  uint8_t return_type;
  double time_stamp;
  EIGEN_MAKE_ALIGNED_OPERATOR_NEW
} EIGEN_ALIGN16;

Could you avoid the bug?

Hi, thanks for bringing attention to this!
This is a known issue - I would love to use all the Clang tooling for Nebula - but even when fixing this, I found that transport_drivers also does not compile with Clang so I gave up for the time being. I will look into this some time in the near future. If you want a fix now, please feel free to PR :bowing_man:

@mojomex
Thank you for your quick reply!!
My first concern is whether the struct PointXYZIR and PointXYZIRADT are aligned, in spite of the pcl bug?
If they are NOT aligned, it should be solved soon.
If they are aligned, then I think we have two options:

use pcl>=v1.10.0
It is reccomnended here: https://github.com/leggedrobotics/tensorflow-cpp/blob/master/ISSUES.md
do nothing for now, and look into in some future as you say

May I close it?

@veqcc The fix is currently merged into develop, we'll close the issue once it is merged into main!

Fixed by

#166


OpenSSL 1.1 compatibility

Update Crypto to be OpenSSL 1.1 compatible.
Ubuntu 18.04 ships with OpenSSL 1.1 as part the standard install.   However, since Crypto is not yet OpenSSL 1.1 compatible, then Vapor on a source level would not be Ubuntu 18.04 compatible. [see vapor/documentation/issues/359 comments]
Although an OpenSSL 1.1-compatible Crypto may not happen any time soon due current priorities and/or level of effort required, this issue provides a place to (1) communicate this as a known issue and (2) provide some guidance or milestone as to how far out a Vapor/Crypto with OpenSSL 1.1 might be.

The other thing blocking this is that Swift doesn't (officially) support 18.04 and it requires NIO to support 1.1 as well (the work of which is almost done)

@0xTim yes, NIO's has landed a few days ago in swift-nio-ssl 1.3.1

If only there was a wrapper for EVP, not just the TLS-related functions 😊

@vzsg I know... We don't consider any of our OpenSSL bindings public API though. So from NIO's point of view the public API are the TLS channel handlers/options/etc only.
I know that's not a great answer for vapor/crypto but longer term that should rely on the platform's TLS library anyway, right? For example NIO with NIOTransportServices now works fine on iOS and there you wouldn't even use swift-nio-ssl at all because Network.framework is used to provide the TLS functionality. Vapor/crypto won't work on iOS as long as it keeps its OpenSSL dependency (short of vendoring OpenSSL) but the Swift Server Work Group is naturally looking into a cross-platform crypto library that could then be used for vapor/crypto on Linux & Darwin. IBM's BlueCryptor does support OpenSSL 1.0 & CommonCryto already.

Sad news. Until this issue is not resolved I give up Vapor on Arch Linux.

OpenSSL 1.1 support added in #75.

Awesome news! This patch just unlocked Vapor on Arch Linux!
Thank you @tanner0101 and team!


Multiple games missing full resolution list

Games have a limited list of resolutions available.
Software information
Call of Duty Modern Warfare 2
Grand Theft Auto 4
System information

GPU: 1080 Ti
Driver: 436.02
Wine version: N/A
DXVK version: 0.20 Frog

Log files

d3d9.log: http://www.mediafire.com/file/j4pve5zrdvgb7t7/iw4sp_d3d9.log/file

Can you show me what you mean?

https://i.imgur.com/e27iAsw.png
The list tops out at 1280x1024 100Hz when in native D3D9 it shows all available resolutions for my display, which is a 2560x1440 144hz panel. The same list of resolutions is in Call of Duty Modern Warfare 2. There may be more games that exhibit this behavior which I haven't found yet.

Do you have multiple monitors?

I do and I thought it might be that so I tested with only my primary plugged in. Still the same.

I created api traces for both games but I'm not sure if it is going to help: http://www.mediafire.com/file/h0gqj75c72oyvrj/apitraces.rar/file
Both games still affected as of v 0.30.

You have the 4:3 aspect ratio selected.

GTA IV's resolution list works fine for me.
Can you make sure this isn't just the fact you had the aspect ratio locked on 4:3?

Still happens regardless of aspect ratio setting. It's more for applying a different scaling to the currently selected resolution and has not bearing on available options. Call of Duty doesn't even have this option anyway.
Strangely enough I just went to test that option and when I launched the game, it decided to use my Nvidia DSR setting of 5120x2880 which is extremely far off the list of available resolutions: https://i.imgur.com/mYnTOXf.png
The second I make an adjustment to the resolution the list crunches down to the normal size and tops out at the old shortened list of 1280x1024 @ 100hz and 5120x2880 is not longer selectable: https://i.imgur.com/ONRtv2k.png
I thought perhaps it might be due to DSR that this issue is happening so I tested with it completely turned off. Same issue is present. All that accomplished was now I can't get 5k out of the game with D9VK anymore.
Just to be clear I am testing this on a native Windows environment as Vulkan provides far better compatibility in modern Windows 10 versions than native DX9 support. You are singlehandedly saving the DX9 library on Windows PCs so I hope this doesn't get tossed aside and ignored.

I have a 2060 Super so I will try and see if I can repro there in GTA IV...

I can't repro.

I'm wondering if it's maybe your monitor. I have a 2560x1440 144hz monitor. Every resolution gets a 24hz, 60hz, 85hz, 100hz, 120hz and 144hz listing. Under native D3D9 GTA IV and Call of Duty MW2 report the full list of resolutions and refresh rates, but with D9VK it's limited to a significantly smaller range.
What monitor are you testing on out of curiosity? I am thinking it might be 60hz only.

Can you try with this build please?
d3d9.zip

No change.

I have made some progress in understanding this bug. Here I am in game with D9VK able to select all resolutions: https://i.imgur.com/r0AXTxR.png
What I did was go into CRU and stripped away all refresh rates besides 60hz and 144hz. This dramatically cuts down on the reported available resolution/refresh rate combinations that D9VK is reporting to the game, chopping the list down to a much smaller number.
Here's the thing, with D9VK for some odd reason every refresh rate + resolution listing gets multiplied 3 times over. This only happens with D9VK, when using native D3D9 each combination (ie - 2560x1440 @144hz) only gets 1 listing in the resolution switch options.
So this is clearly the problem. D9VK is misreporting each resolution + refresh rate combination when enumerating the list of available options and multiplying each listing times 3. This only happens for COD:MW2 and GTA IV that I have found thus far. Right now my only solution is to basically modify my monitor's EDID in software to lie about what refresh rates it can support to bring the list size down far enough so I can choose either native 2560x1440 144hz or for older games my preferred 5120x2880 144hz DSR.

Another update to this problem:
I tested another display to see if this problem is due to my monitor or something else, using a basic 640x480 60hz CRT TV through HDMI which only has 2 resolution options and 2 refresh rate options (59hz and 60hz.) The triple listing problem persisted, even with my gaming monitor disconnected. This is not a monitor issue.
I also had a friend test it out on his Nvidia 2080 Ti with a 144hz issue, and even on Windows he did NOT have this issue. Now I am wondering if this is possibly related to the series graphics card being used as I cannot fathom what else could possibly be variable in this equation that would affect something like this.
Joshua you have a 2060 you do tests for Nvidia on correct? If you have a 10 series card available, would you be able to test on that to see if you can repro this issue? I'm really baffled here on what could be the cause.

Closing this issue because I was able to reproduce it in a native OpenGL emulator without any connection to D9/DXVK. It's apparently a problem with this specific monitor (perhaps some others?) and OpenGL/Vulkan misreporting non-native resolutions and refresh rate combinations. The issue wasn't present under native D3D9 but when running under Vulkan it presents itself.


alphabetizes each section and the lists of each section

this makes it easy to read and find things

@cglewis not to be the barer of bad news, but this is likely to be closed by @sindresorhus

#216 #234 #304 #201 #177 #548

https://github.com/sindresorhus/awesome/issues/548#issuecomment-189576619


KOGITO-1362 - Missing POM properties and JAR sources

Merging as build error is not related, see https://github.com/kiegroup/kogito-cloud/pull/97


chain-bench: init at 0.0.2

Description of changes

~Wait for x86_64-darwin build~ built fine on ofborg, removed broken line
Package chain-bench for nixpkgs
https://github.com/aquasecurity/chain-bench
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[X] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

nice™ number #177777

Result of nixpkgs-review pr 177777 run on x86_64-linux 1

1 package built:

chain-bench

Related to #81418


FIX: Transpose issue of CSP.plot_filters

Reference issue
Fixes #8579.
What does this implement/fix?
Just add a transpose to correct the CSP filters plot.

Thanks @rubyyhj!


Self with #[derive(DynStruct)]

Self in struct declaration with #[derive(DynStruct)] becomes "mangled" with some _DynStruct_Single:
    #[repr(C)]
    #[derive(DynStruct)]
    struct MyNode{
        pub link: ListLink<Self>,
        pub dynamic: [u32],
    }

Is this possible to overcome?

Hmm, in the derive macro we generate a new struct containing all but the last field (the _DynStruct_Single you are seeing), which we then used the Header in DynStruct<Header, Tail>. In order for this to work though, we need to guarantee that the _DynStruct_Single has the same layout as MyNode in your example. For this we use #[repr(C)] on both structs. However, this does mean that the Self gets mangled to the new struct, which as you noticed might not be all that great.
Best would be if Rust allowed us to create a tuple with #[reprC)] somehow, but as far as I'm aware that's not possible...
The alternative would be to change the derive macro such that all occurances of Self in the fields of the input be translated to MyNode. In general this would also need to handle cases such as MyNode<'a, T, N>, but should be doable.
This is not something I'm to keen on doing though. So I suggest you either open a PR with a fix, or use the workaround of just performing the substitution manually.

Ok, I see, thanks!
Maybe that Self caveat should be mentioned in documentation...


Swiping too quickly inbetween tabs breaks app

When on either the details or edit fragment, dwiping between the tag and photos tab while the app is loading the image for the photos listView will break the app

Looks like this got fixed with the image adapter changes. I am unable to replicate.


Integration will not display on 2021.1.3 with HACs 1.10

Version of the custom_component

0.32
Configuration

Add your logs here.

Describe the bug
HACS 1.10 running on 2021.1.3.  Installs the custom component correctly but even after restart the integration is not available in the UI list. Other integrations via HACS have successfully installed.
Debug log

Add your logs here.

This sounds a bit like issue #2 .
It sounds like it can be a home assistant integration list cache issue. I know that HACS documentations says that "Before HACS can show up in the list you need to clear your browser cache". Maybe this is sometime is the case with integrations installed using HACS as well.

This sounds a bit like issue #2 .
It sounds like it can be a home assistant integration list cache issue. I know that HACS documentations says that "Before HACS can show up in the list you need to clear your browser cache". Maybe this is sometime is the case with integrations installed using HACS as well.


Add Export for TF backend

This PR adapts the export library from tf.keras to Keras Core, along with adapting its corresponding test suite.
Note that this PR only implements export for the TF backend and expansion to JAX is still in the planning stage.
I have included some TODOs for further test coverage or debugging for certain edge use cases.

The lookup table tests is failing, though it isn't entirely clear what the issue is.

I've decided to comment out the lookup test for now, as it's unclear how CI is affected after investigating. It's a blocker for this PR and can be addressed separately.


Fix bug when trying to predict 8 hrs into the future.

OK, I think I understand the problem:
The random t0 time periods include:

2020-02-19 08:25 to 2020-02-19 15:30
2020-02-21 08:20 to 2020-02-21 15:30

pd.DataFrame([{"start_dt": "2020-02-19 08:25", "end_dt": "2020-02-19 15:30"}, {"start_dt": "2020-02-21 08:20", "end_dt": "2020-02-21 15:30"}])
Given these periods, the RawNWPDataSource would've attempted to load data with init_times from 2020-02-21 06:00 to 2020-02-22 00:00
BUT! init times 2020-02-21 is missing init times at 06 and 09.
So, I think the solution is fairly simple: in RawNWPDataSource._convert_t0_time_periods_to_periods_to_load, don't take the floor of the start_dt. Instead find the most recent init_time_utc.


Remove retry for credentials providers

Remove retry for credentials providers
See #715

Is the retry crate being used anywhere after this change or could that dependency be removed as well?

No it's not used anywhere else.
I forgot to remove it thanks for catching it.

Looks good.  Integration tests pass.   Thanks for contributing!


Check for valid mail URL before creating

This fixes issue #103 , it simply adds the same type of guard in MailLinkElementGenerator that LinkElementGenerator has prior to creating a URL (as what the regex thinks is valid may differ from what Uri class does).

Thanks for fixing it. Do you have an ETA for when this will be released and published?

@jimfoye @dgrunwald Any ideas when this gets released on Nuget? Thanks!

I can't answer, I'm just a humble fixer :)


Command line not prompting error on invalid path

Godot version
3.4, 4.0a (supposedly)
System information
Windows 10, AMD Ryzen 2700x, Nvidia 1070ti
Issue description
Running godot from command line, having godot in PATH, running godot -e --path <some invalid path> with invalid path just opens the project manager, not prompting what is wrong in terminal. To make matters worse it starts in low DPI, which looks awful.
Steps to reproduce

Add godot to PATH
run godot -e --path <some invalid path>
Observe incorrect behavior

Minimal reproduction project
No response

To make matters worse it starts in low DPI, which looks awful.

This is likely because the editor-specific codepath isn't triggered when doing this, which means hiDPI support is not forced. This won't be an issue anymore in 4.0 thanks to https://github.com/godotengine/godot/pull/29553.


DOC typo fix in ner.rst

the same typo is fixed in https://github.com/deepmipt/DeepPavlov/pull/833.


add: wrapper table component to export it

Related Issue
#734
Description
Trying to create and export a wrapper table component to acces from outside and customize it.
Impacted Areas in Application
List general components of the application that this PR will affect:
*
MTableWrapper --- new component
material-table.js

Hi 2 things: can you explain the reason for the PR and could you remove all changes that are prettier and not code related?

Hi 2 things: can you explain the reason for the PR and could you remove all changes that are prettier and not code related? Like what do you want to achieve that cannot be done right now: just add the sx parameter or what ?

This is related to de issue #734 This way I can add a custom Wrapper and modify there what I need.
If there is a way to achieve what I ask in the issue, That will be great.

Yes I know, but what do you want to achieve and how do you do it? Can you share a Sandboy or something on what you are doing.

Yes I know, but what do you want to achieve and how do you do it? Can you share a Sandboy or something on what you are doing.

Ideally we can have a prop that allow to group the th on the table.
I didnt know how to do that, so I expect to add a custom wrapper and in this wrapper insert after the table the groups of the th, doing some math to manage the width of each th.
I get the table columns with a fixedLayout and then if group A, have three cols, I sum the trhe width and insert in the custom component a new div with that div, and something like that. Is no ideal but I didnt find another way of doing this.
I really can use some help here to achive this #734

So in the image you have an extra row with custom table cells for a second header? So you  just want to add a custom row on top. Can you explain in words what you would like to get. I am still not clear. To avoid confusion, I don't ask how you would achieve it, but what you want to achieve on more detail than I want to wrap them please. The sentence " I want to group the th " is not accurate because you add a second th row. Which one etc.

So in the image you have an extra row with custom table cells for a second header? So you just want to add a custom row on top. Can you explain in words what you would like to get. I am still not clear. To avoid confusion, I don't ask how you would achieve it, but what you want to achieve on more detail than I want to wrap them please. The sentence " I want to group the th " is not accurate because you add a second th row. Which one etc.

There are certain cases in complex tables in which it is necessary to group the columns in order to specify what that group of columns represents. For example, let's say we have a table that has the data of a company's services, customer data, supplier data, tax data, etc. What I would like is to be able to group the columns that represent the data of the service with another column called Services, those of the provider with a call Provider, etc. As depicted in the image I shared.
There are libraries that achieve this using a data structure like this:
`import * as React from 'react';
import {
DataGridPro,
GridColDef,
GridColumnGroupingModel,
} from '@mui/x-data-grid-pro';
const columns: GridColDef[] = [
{ field: 'id', headerName: 'ID', width: 90 },
{
field: 'firstName',
headerName: 'First name',
width: 150,
},
{
field: 'lastName',
headerName: 'Last name',
width: 150,
},
{
field: 'age',
headerName: 'Age',
type: 'number',
width: 110,
},
];
const rows = [
{ id: 1, lastName: 'Snow', firstName: 'Jon', age: 35 },
{ id: 2, lastName: 'Lannister', firstName: 'Cersei', age: 42 },
{ id: 3, lastName: 'Lannister', firstName: 'Jaime', age: 45 },
{ id: 4, lastName: 'Stark', firstName: 'Arya', age: 16 },
{ id: 5, lastName: 'Targaryen', firstName: 'Daenerys', age: null },
{ id: 6, lastName: 'Melisandre', firstName: null, age: 150 },
{ id: 7, lastName: 'Clifford', firstName: 'Ferrara', age: 44 },
{ id: 8, lastName: 'Frances', firstName: 'Rossini', age: 36 },
{ id: 9, lastName: 'Roxie', firstName: 'Harvey', age: 65 },
];
const columnGroupingModel: GridColumnGroupingModel = [
{
groupId: 'Internal',
description: '',
children: [{ field: 'id' }],
},
{
groupId: 'Basic info',
children: [
{
groupId: 'Full name',
children: [{ field: 'lastName' }, { field: 'firstName' }],
},
{ field: 'age' },
],
},
];
export default function BasicGroupingDemo() {
return (
<div style={{ height: 400, width: '100%' }}>
<DataGridPro
experimentalFeatures={{ columnGrouping: true }}
rows={rows}
columns={columns}
checkboxSelection
disableSelectionOnClick
columnGroupingModel={columnGroupingModel}
/>

);
}`

Could we simply fix this by removing the div from the table wrapper and make it into a box and pass the given sx tag?

Could we simply fix this by removing the div from the table wrapper and make it into a box and pass the given sx tag? And can you add a sandbox of how you achieve this, like what you pass?

Idon't get how doing that we can achieve something like the post before. With the sx we can add styles but not insert code into the wrapper or am I missing something?

The multi header row is not supported as of yet. Of you have a decent idea on how to implement it natively, that would be interesting. Bit just adding a random wrapper might not be the best idea here

The multi header row is not supported as of yet. Of you have a decent idea on how to implement it natively, that would be interesting. Bit just adding a random wrapper might not be the best idea here

I guess so but any idea of how to achieve that? Do you have in mind to add this feature any time soon? I really need it for a production enviroment this will be a life saver.


Memory usage

Sails version: v0.12.3
Node version: v4.4.7
NPM version: v2.15.8
Operating system: Ubuntu v14.4

Hi guys,
To be short, I've setup a no frontend sails project with a basic controller and hit it with loadtest, the memory keeps increasing and no sign of stablizing. I've read previous posts and have disabled grunt, session, socket, pubsub and etc.
Setup:
Sails version: v0.12.3
Node version: v4.4.7
NPM version: v2.15.8
Reproduce:
create new sails project
sails new Project --no-frontend

edit .sailsrc:
{
  "generators": {
    "modules": {}
  },

  "hooks": {
    "session": false,
    "sockets": false,
    "pubsub": false,
    "grunt": false,
    "i18n": false
  }
}

added controllers/TestController.js:
module.exports = {
  hi: function (req, res) {
    return res.send("Hi there!");
  }
};

run load test:
var loadtest = require('loadtest');

var host = 'http://localhost:1337';

var options = {
    url: host + '/test/hi',
    requestsPerSecond: 50
};

loadtest.loadTest(options, function(error, result)
{
    if (error)
    {
        return console.error('Got an error: %s', error);
    }
    console.log('Tests run successfully: '+result);
});

Thank you for your help.
Mars

Ok, fixed!

@marspark I've spent a lot of time testing v0.12.1, v0.12.2, and v0.12.3 for memory leaks (with the help of @particlebanana, @sgress454, and others), and so far, we have never been able to reproduce a memory leak.  Of course it's always possible we're missing something, so I'm curious to see what you're running across.  That said, we have tested the exact scenario you're describing, the only difference being that we tested on Mac OS instead of Ubuntu.  So please bear with me-- I don't mean to cause any offense, just need to get to the bottom of it as efficiently as possible.
First off, I saw you posted in the other issue: https://github.com/balderdashy/sails/issues/2779#issuecomment-209735285
In that issue, I posted a comment with some best practices on how to report a memory leak.  So you've probably already seen them, but just to be sure:  it's not clear to me from looking at this issue if you are running Sails with recommended production settings-- are you?
If you are, then the next step is to make sure we're on the same page about what a memory leak is:
When you start looking at this kind of stuff, it can sometimes be really difficult to know what is and isn't a leak.  (At least I know it used to confuse me quite a bit!)   To be clear: a Node process will grow its memory usage until it decides it's time to run the garbage collector.  Just because memory is going up continually does not mean there is a memory leak-- it means that the garbage collector has not run yet.
To show what I mean, take a look at the notes I wrote up on how to analyze memory usage here: https://github.com/balderdashy/waterline/issues/1323#issuecomment-214025388
Next, take a look at the graphs @particlebanana posted here: https://github.com/balderdashy/waterline/issues/1323#issuecomment-214554282
For more technical background and notes on the garbage collector in Node.js, you might also check out:
https://github.com/nodejs/node-v0.x-archive/issues/5345
So after reading the stuff above, it turns out that we weren't on the same page-- no problem!  On the other hand, if we're on the same page, and you're confident that there's a memory leak here, then please continue on below.
Testing for memory leaks
The only surefire way to diagnose a memory leak is to run your Node process with the --expose-gc flag enabled, to manually run the garbage collector , and then to compare the "valleys" of the chart.  Here's a step by step:
1.   For example: https://github.com/balderdashy/sails-hook-dev/blob/master/index.js#L190-L203
(you can also just install sails-hook-dev in your project).
2. Monitor
Start up a program that monitors your Node process's memory.  I recommend NodeSource.
3. Lift
Lift your app with all recommended production settings (see deployment and scaling docs on sailsjs.org).  But also make sure you tell Node.js to allow your code programmatic use of the garbage collector.  For example, I like to do this by running:
NODE_ENV=production node --expose-gc app.js

4.   In this example, that would be sending GET requests to /.  After about 30 minutes of this, if you take a look at the graphs, they might look slopey and bad, or they might flat and good.  But that doesn't matter at all-- we have no idea about whether there are memory leaks at this point.
5.   You'll see the graphs drop dramatically after a moment.  Take note of the lowest point in the graph (the "valley").  This is the amount of memory that the process is using, and that could not be reclaimed using the garbage collector.  This is the memory where stuff you're actually using lives-- e.g.  the require() cache, and local variables that are still in use.  If you're reporting a suspected memory leak, please be sure to take a screenshot of the graphs and memory usage in GB at this point.
6. Do stuff or run load tests (round 2)
Now do exactly the same thing we did in step 4 again, for another 30 minutes.
7. Force garbage collector to run (round 2)
Now do exactly the same thing we did in step 5 again.  After a moment, if you notice that the "valley" in the graph is significantly higher than it was in step 5, there might be something going on (there seems to be some amount of natural variation in what the garbage collector can actually reclaim-- in some cases this second "valley" is actually lower).  If you're reporting a suspected memory leak, please be sure to take a second screenshot of the graphs and memory usage in GB at this point.
Finally, if after running through the steps above, it seems likely that there is a memory leak (i.e. the second "valley" was significantly higher than the first), then please repeat steps 6 and 7 one more time to be sure.  If there is a memory leak, you'd expect the second "valley" to be significantly higher than the first, and the third "valley" to be significantly higher than the second.  If you notice that this is the case, then please let me know ASAP in this issue.
Thanks for the help!

@mikermcneil Hi Mike, thank you for your reply.
The problem I'm encountering is not a memory leak, it's just that the garbage collector won't run as long as the sails server stays online.
I was using sails 0.9.7 on my other server and it triggers garbage collector correctly therefore I'm wondering if there's anything I can do to make sails 0.12.3 behaviors the same way.
Thank you!
Mars

@marspark Ah ok, I think I understand the mixup now.    In fact, it couldn't control that even if it wanted to (you'd have to enable the --expose-gc flag for framework/app-level code to be able to call the garbage collector, and the only way I can think of to prevent it from running would be to while(true){}-- which would also completely block all incoming requests.  Obviously, you wouldn't want to do that!)
The rest of the Sails team and I keep an eye on the amount of memory a Sails process uses, and we do our best to keep the memory footprint of Sails as small as possible.  So far, I've never heard of anyone experiencing deployment problems relating to memory usage, so I'm curious what issue you're running into.  I could see how maybe deploying a Sails app on a server with a very small amount of RAM (e.g. 64MB) could cause issues though-- is that what's going on here?
Thanks!

@mikermcneil It can be easily reproduced by the steps I've described in my 1st post:

create a fresh no-frontend project

disable session/socket in .sailsrc

create a basic controller (from the documentation section in the sails website):
module.exports = {
hi: function (req, res) {
return res.send("Hi there!");
}
};

hit it with loadtest (or just do it over 100 times manually)

The results:

Memory never drops as long as the server is up
It can stack up to multi-GBs and eventually crash the server

Hi @marspark, these issues can be a real pain to get to the bottom of.  We can all empathize.  The reality is that we have several large-scale Sails deployments in production at the moment (including the Sails website and Treeline.io) that we monitor pretty closely, and they've been running for a long time without gobbling up memory indefinitely or crashing servers.  I don't dispute that you're seeing something happen.  Rather, I'm suggesting that either:

What you think you're seeing as a never-ending increase of memory, isn't.  I don't know anything about the loadtest package, it might be awesome.  I'm just saying that the tooling around these sorts of metrics is often tricky and misleading, and can sometimes work differently between platforms and Node versions.

If there really is a problem of never-ending memory consumption, it involves something particular to your configuration.  It's still possible that something in Sails is contributing to it, but it can't just be Sails, because if all it took to make a Sails app consume all of your server's resources was to hit a "hello there" endpoint 100 times, this forum would be flooded by folks with crashed servers.

In almost every case like this we've seen so far, it eventually comes down to, "ah, it turns out it wasn't really consuming all those resources after all, it just looked like it because of X" where X is most often a misunderstanding of the load testing tool (how to use it, or how to interpret the results).
I really wish we could be of more help, believe me I know how annoying this can be!

@marspark @sgress454 Hey y'all, for future reference, found a great link on this subject that does a better job explaining it than I did above:

The key in this case lies in the fact that after each drop in memory use, the size of the heap remains bigger than in the previous drop. In other words, although the garbage collector is succeeding in collecting a lot of memory, some of it is periodically being leaked.

Full article: https://auth0.com/blog/four-types-of-leaks-in-your-javascript-code-and-how-to-get-rid-of-them/