Add echo-server image alternative for Apple Silicon chips

Issue mentioned in minikube repository.
I could find an issue in this repository, if someone is aware of a ticket tracking this then feel free to link it in. :)

I also agree that the fix should be with the container image
Closing the PR, feel free to reopen if you feel otherwise
/close


About features mode in forecasting performance

Thank you for your excellent work! I just want clearly know if this table is test on 'M' mode or 'MS' mode of features parameter?

Hi, the feature mode was set to 'M', you can refer to the .conf files in data_configs folder.


Annotate generated classes with @Generated

Generated classes like CheckedFunction0 could be annotated with javax.annotation.Generated to differentiate them from hand written code.
Furthermore the generator class as well as the actual generator method could be referenced via the comment attribute to ease finding the appropriate generator method.

Hi Thomas,
thank you for your suggestion! Could you please elaborate on the use-case(s)?
Currently we ensure that PRs will fail when generated code is manually modified. Our CI build does this by...

performing a git clone (which may contain manually modified generated code)
running the build (which overwrites generated code)
checking for changes using git status (there shouldn't be changes)

By using annotations, we make the 'is generated' property part of the public API. However, users should not bother whether source is generated or not. We need the freedom to change that property without affecting backward-compatibility.
I'm looking forward to learn about your use-case.

Maybe this might come handy when we use an 'inline code generator' (see Seamlessly fuse hand-written and generated code)

I just saw that @Generated has the retention policy 'SOURCE' - now I understand that the use-case you meant is documentation. So, let's do it!


Add support for _ as an alternative to ^

Useful for layouts where ^ is a dead key.

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


[Bug]: Failures with INGEST_STAGED jobs  during load test

Checked for duplicates
Yes - I've already checked
Describe the bug
When we performed few load tests, there were many failures with INGEST_STAGED jobs.
Here are few common errors captured.

Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 193, in publish_dataset
osaka.main.put(publ_ctx_file, publ_ctx_url, params=params, noclobber=True)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 38, in put
transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 118, in transfer
transfer.transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 128, in transfer
raise err
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 87, in transfer
raise osaka.utils.NoClobberException(error)
osaka.utils.NoClobberException: Destination, s3://s3-us-west-2.amazonaws.com:80/opera-dev-rs-fwd/products/HLS.S30.T36QUE.2022025T082231.v2.0.B12/_publish.context.json, already exists and no-clobber is set

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 434, in ingest
publish_dataset(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 195, in publish_dataset
raise NoClobberPublishContextException(
hysds.dataset_ingest.NoClobberPublishContextException: Failed to clobber s3://s3-us-west-2.amazonaws.com:80/opera-dev-rs-fwd/products/HLS.S30.T36QUE.2022025T082231.v2.0.B12/_publish.context.json when noclobber is True.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/job_worker.py", line 1412, in run_job
post_processor_sigs.append(func(job, context))
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 692, in publish_datasets
prod_json = publish_dataset(prod_dir, dataset_file, job, ctx)
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 595, in publish_dataset
metrics, prod_json = get_func("hysds.dataset_ingest.ingest")(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 540, in ingest
publish_dataset(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 206, in publish_dataset
osaka.main.put(abs_path, dest_url, params=params, noclobber=True)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 38, in put
transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 118, in transfer
transfer.transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 128, in transfer
raise err
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 87, in transfer
raise osaka.utils.NoClobberException(error)
osaka.utils.NoClobberException: Destination, s3://s3-us-west-2.amazonaws.com:80/opera-dev-rs-fwd/products/HLS.S30.T36QUE.2022025T082231.v2.0.B12/HLS.S30.T36QUE.2022025T082231.v2.0.B12.met.json.md5, already exists and no-clobber is set

Traceback (most recent call last):
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 38, in enter
self.dlock.lock(lockMetadata)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/lock.py", line 78, in lock
raise osaka.utils.OsakaException("Lock file already locked")
osaka.utils.OsakaException: Lock file already locked

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/job_worker.py", line 1412, in run_job
post_processor_sigs.append(func(job, context))
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 692, in publish_datasets
prod_json = publish_dataset(prod_dir, dataset_file, job, ctx)
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 595, in publish_dataset
metrics, prod_json = get_func("hysds.dataset_ingest.ingest")(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 434, in ingest
publish_dataset(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 206, in publish_dataset
osaka.main.put(abs_path, dest_url, params=params, noclobber=True)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 38, in put
transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 118, in transfer
transfer.transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 128, in transfer
raise err
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 104, in transfer
with osaka.cooperator.Cooperator(source, dlock, lockMetadata) as coop:
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 43, in enter
self.whenLocked()
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 66, in whenLocked
ex_source = self.dlock.getLockMetadata("source")
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/lock.py", line 102, in getLockMetadata
filelike = handle.get(self.luri)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/storage/s3.py", line 152, in get
obj.download_fileobj(fh)
File "/home/ops/verdi/lib/python3.9/site-packages/boto3/s3/inject.py", line 759, in object_download_fileobj
return self.meta.client.download_fileobj(
File "/home/ops/verdi/lib/python3.9/site-packages/boto3/s3/inject.py", line 679, in download_fileobj
return future.result()
File "/home/ops/verdi/lib/python3.9/site-packages/s3transfer/futures.py", line 103, in result
return self._coordinator.result()
File "/home/ops/verdi/lib/python3.9/site-packages/s3transfer/futures.py", line 266, in result
raise self._exception
File "/home/ops/verdi/lib/python3.9/site-packages/s3transfer/tasks.py", line 139, in call
return self._execute_main(kwargs)
File "/home/ops/verdi/lib/python3.9/site-packages/s3transfer/tasks.py", line 162, in _execute_main
return_value = self._main(**kwargs)
File "/home/ops/verdi/lib/python3.9/site-packages/s3transfer/download.py", line 569, in _main
response = client.get_object(
File "/home/ops/verdi/lib/python3.9/site-packages/botocore/client.py", line 391, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/home/ops/verdi/lib/python3.9/site-packages/botocore/client.py", line 719, in _make_api_call
raise error_class(parsed_response, operation_name)
botocore.errorfactory.NoSuchKey: An error occurred (NoSuchKey) when calling the GetObject operation: The specified key does not exist.

Traceback (most recent call last):
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 38, in enter
self.dlock.lock(lockMetadata)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/lock.py", line 78, in lock
raise osaka.utils.OsakaException("Lock file already locked")
osaka.utils.OsakaException: Lock file already locked

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/job_worker.py", line 1412, in run_job
post_processor_sigs.append(func(job, context))
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 692, in publish_datasets
prod_json = publish_dataset(prod_dir, dataset_file, job, ctx)
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 595, in publish_dataset
metrics, prod_json = get_func("hysds.dataset_ingest.ingest")(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 434, in ingest
publish_dataset(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 193, in publish_dataset
osaka.main.put(publ_ctx_file, publ_ctx_url, params=params, noclobber=True)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 38, in put
transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 118, in transfer
transfer.transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 128, in transfer
raise err
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 104, in transfer
with osaka.cooperator.Cooperator(source, dlock, lockMetadata) as coop:
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 43, in enter
self.whenLocked()
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 74, in whenLocked
raise CooperationNotPossibleException(
osaka.utils.CooperationNotPossibleException: /data/work/jobs/2022/07/28/21/23/ingest-staged-HLS.S30.T34JDL.2022025T082231.v2.0.B11.tif-20220728T210017.689691Z/.pub_contextzv_jor72/_publish.context.json differs incoming source /data/work/jobs/2022/07/28/21/23/ingest-staged-HLS.S30.T34JDL.2022025T082231.v2.0.B11.tif-20220728T210017.716229Z/.pub_contextzo7dkr8s/_publish.context.json. Cooperation not possible for s3://s3-us-west-2.amazonaws.com:80/opera-dev-rs-fwd/products/HLS.S30.T34JDL.2022025T082231.v2.0.B11/_publish.context.json

Traceback (most recent call last):
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 38, in enter
self.dlock.lock(lockMetadata)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/lock.py", line 78, in lock
raise osaka.utils.OsakaException("Lock file already locked")
osaka.utils.OsakaException: Lock file already locked

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/job_worker.py", line 1412, in run_job
post_processor_sigs.append(func(job, context))
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 692, in publish_datasets
prod_json = publish_dataset(prod_dir, dataset_file, job, ctx)
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 595, in publish_dataset
metrics, prod_json = get_func("hysds.dataset_ingest.ingest")(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 434, in ingest
publish_dataset(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 193, in publish_dataset
osaka.main.put(publ_ctx_file, publ_ctx_url, params=params, noclobber=True)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 38, in put
transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 118, in transfer
transfer.transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 128, in transfer
raise err
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 104, in transfer
with osaka.cooperator.Cooperator(source, dlock, lockMetadata) as coop:
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 43, in enter
self.whenLocked()
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 70, in whenLocked
raise CooperationNotPossibleException(
osaka.utils.CooperationNotPossibleException: No source specified. Cooperation not possible for s3://s3-us-west-2.amazonaws.com:80/opera-dev-rs-fwd/products/HLS.L30.T36RWR.2022025T081814.v2.0.B05/_publish.context.json

Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 193, in publish_dataset
osaka.main.put(publ_ctx_file, publ_ctx_url, params=params, noclobber=True)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 38, in put
transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 118, in transfer
transfer.transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 128, in transfer
raise err
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 87, in transfer
raise osaka.utils.NoClobberException(error)
osaka.utils.NoClobberException: Destination, s3://s3-us-west-2.amazonaws.com:80/opera-dev-rs-fwd/products/HLS.S30.T37SBV.2022025T082231.v2.0.B11/_publish.context.json, already exists and no-clobber is set

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 434, in ingest
publish_dataset(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 195, in publish_dataset
raise NoClobberPublishContextException(
hysds.dataset_ingest.NoClobberPublishContextException: Failed to clobber s3://s3-us-west-2.amazonaws.com:80/opera-dev-rs-fwd/products/HLS.S30.T37SBV.2022025T082231.v2.0.B11/_publish.context.json when noclobber is True.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/job_worker.py", line 1412, in run_job
post_processor_sigs.append(func(job, context))
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 692, in publish_datasets
prod_json = publish_dataset(prod_dir, dataset_file, job, ctx)
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 595, in publish_dataset
metrics, prod_json = get_func("hysds.dataset_ingest.ingest")(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 448, in ingest
osaka.main.get(publ_ctx_url, orig_publ_ctx_file, params=osaka_params)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 76, in get
transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 118, in transfer
transfer.transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 128, in transfer
raise err
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 106, in transfer
metrics = self.transfer_uri(source, shandle, dest, dhandle)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 157, in transfer_uri
counts = osaka.utils.product_composite_iterator(source, shandle, transfer_one)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/utils.py", line 105, in product_composite_iterator
return list(map(callback, uris))
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 152, in transfer_one
stream = shandle.get(uri)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/storage/s3.py", line 155, in get
raise osaka.utils.OsakaFileNotFound(
osaka.utils.OsakaFileNotFound: File s3://s3-us-west-2.amazonaws.com:80/opera-dev-rs-fwd/products/HLS.S30.T37SBV.2022025T082231.v2.0.B11/_publish.context.json doesn't exist.

Traceback (most recent call last):
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 38, in enter
self.dlock.lock(lockMetadata)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/lock.py", line 78, in lock
raise osaka.utils.OsakaException("Lock file already locked")
osaka.utils.OsakaException: Lock file already locked

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/job_worker.py", line 1412, in run_job
post_processor_sigs.append(func(job, context))
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 692, in publish_datasets
prod_json = publish_dataset(prod_dir, dataset_file, job, ctx)
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/utils.py", line 595, in publish_dataset
metrics, prod_json = get_func("hysds.dataset_ingest.ingest")(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 434, in ingest
publish_dataset(
File "/home/ops/verdi/ops/hysds-1.1.5/hysds/dataset_ingest.py", line 206, in publish_dataset
osaka.main.put(abs_path, dest_url, params=params, noclobber=True)
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 38, in put
transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/main.py", line 118, in transfer
transfer.transfer(
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 128, in transfer
raise err
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/transfer.py", line 104, in transfer
with osaka.cooperator.Cooperator(source, dlock, lockMetadata) as coop:
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 43, in enter
self.whenLocked()
File "/home/ops/verdi/ops/osaka-1.1.0/osaka/cooperator.py", line 74, in whenLocked
raise CooperationNotPossibleException(
osaka.utils.CooperationNotPossibleException: /data/work/jobs/2022/07/28/21/17/ingest-staged-HLS.L30.T35PRN.2022025T082301.v2.0.B02.tif-20220728T205833.247175Z/output/HLS.L30.T35PRN.2022025T082301.v2.0.B02/HLS.L30.T35PRN.2022025T082301.v2.0.B02.tif differs incoming source /data/work/jobs/2022/07/28/21/17/ingest-staged-HLS.L30.T35PRN.2022025T082301.v2.0.B02.tif-20220728T205833.211162Z/output/HLS.L30.T35PRN.2022025T082301.v2.0.B02/HLS.L30.T35PRN.2022025T082301.v2.0.B02.tif. Cooperation not possible for s3://s3-us-west-2.amazonaws.com:80/opera-dev-rs-fwd/products/HLS.L30.T35PRN.2022025T082301.v2.0.B02/HLS.L30.T35PRN.2022025T082301.v2.0.B02.tif
What did you expect?
When there was duplicate ingest jobs, I expected one job executed successfully and one job would marked as deduped and not executed at all.
Gerald recommended to update ISL lambda function to set 'payload_hash' parameter using s3.object.eTag value.
Reproducible steps
No response
Environment
- PCM 1.0.0-rc.2.0
- dev-common cluster

Modified ISL lambda function to set 'payload_hash' with s3.object.eTag value and delivered https://github.com/nasa/opera-sds-lambdas/commit/d309c4f0448dc43acd3a3c80c2eaad5d2fabd266


Sort labels like buildifier does

buildifier sorts labels by package, then the rule, not by treating the label like a string and sorting that.
This improves the sorting and normalization of labels to avoid foo:foo situations.

sorry for merging this without review. I assumed that it would block on one PR approval.


Copied blob has incorrect content type

After copying a blob, the copy has a content type of "application/octet-stream" instead of whatever was on the source blob.
Example powershell code to reproduce below.
When it runs against a real Azure storage account, the copy's resultant content type is "image/png" as expected.
New-Item "emptyfile.zzz"

#Upload as blob
$ctx = New-AzureStorageContext -Local
$container = New-AzureStorageContainer "mime-bug-repro" -Context $ctx
$originalBlob = Set-AzureStorageBlobContent -Blob "emptyfile.zzz" -Container $container.Name -File "emptyfile.zzz" -BlobType Block -Properties @{"ContentType" = "image/png"} -Context $ctx

#Initiate copy
$copyJob = Start-AzureStorageBlobCopy -SrcBlob $originalBlob.Name -SrcContainer $container.Name -DestBlob "copy-of-emptyfile.zzz" -DestContainer $container.Name -Context $ctx -DestContext $ctx
#Wait for copy.
while(($copyJob | Get-AzureStorageBlobCopyState).Status -ne "Success")
{
    sleep 5
}

#Get copy
$copiedBlob = Get-AzureStorageBlob -Container $container.Name -Blob "copy-of-emptyfile.zzz" -Context $ctx

#Check ContentType
"The content type of the copy is: $($copiedBlob.ContentType)"

#Clean up file and container
$container | Remove-AzureStorageContainer -Force
Remove-Item "emptyfile.zzz"

This issue should have be resolved.


Horizontal Bar Chart Not Appear

My sample code to generate horizontal stacked bar chart with datetime to be display as x-axis. However, when I was try to set x-axis limit to the range of minDateTime.AddSeconds(-1).ToOADate() till maxDateTime.ToOADate(), the bar chart does not displayed out. I had to zoom out to certain scale only the chart appear.
P/S: minDateTime is the minimum datetime of datasets in the chart, whereas maxDateTime is the maximum datetime of datasets in the chart.
Random r = new Random();
mcChartObj.Insert(0, new MCChartObject()
{
    xs = new double[] { 1 },
    ys = new double[] { DateTime.Now.AddMinutes(count).ToOADate() },
    color = !machineRunning
        && !machineError ? System.Drawing.Color.Yellow : machineRunning
        && !machineError ? System.Drawing.Color.GreenYellow : System.Drawing.Color.Red,
});

mcChart.plt.Clear(p => p is PlottableBar);

foreach (MCChartObject model in mcChartObj)
{
    mcChart.plt.PlotBar(model.xs, model.ys, fillColor: model.color, horizontal: true, barWidth:0.1);
}

var min = mcChartObj.Min(x => x.ys[0]);
DateTime minDateTime = DateTime.FromOADate(min);

var max = mcChartObj.Max(x => x.ys[0]);
DateTime maxDateTime = DateTime.FromOADate(max);
mcChart.plt.Axis(minDateTime.AddSeconds(-1).ToOADate(), maxDateTime.ToOADate());
mcChart.plt.Ticks(dateTimeX: true);

Application.Current.Dispatcher.Invoke(() => { mcChart.Render(true); });
count++;

Something that i want:
(but i would like to have my axis limit start with DateTime.Now.addMinutes(-1).ToOADate(), unfortunately the chart does not show the bar chart. It only worked for axis limit start with DateTime.Now.addHours(-1).ToOADate())
mcChart.plt.Axis(x1:DateTime.Now.addHours(-1).ToOADate(), x2:maxDateTime.AddMinutes(1).ToOADate());

Situation when axis limit is set with
mcChart.plt.Axis(x1:DateTime.Now.ToOADate(), x2:maxDateTime.AddMinutes(1).ToOADate(), y1:0, y2:2);

Hi @Moo1211,
Unfortunately I'm having a very difficult time understanding your question. This is why I didn't reply earlier, and I suspect it's why others have not offered suggestions too.

sample code to generate horizontal stacked bar chart with datetime to be display as x-axis

If you haven't already, check out the DateTime Bar Plot cookbook demo:
https://swharden.com/scottplot/cookbooks/4.1.13-beta/category/plottable-bar-graph/#datetime-bar-plot
It's pretty hard to tell from your code why you are experiencing a problem. Consider making known DateTime objects and plotting those, then add complexity like determining min/max DateTimes. I suspect something in your DateTime logic (not your plotting code) may be causing your issue here.
Hope it helps!


fix(deps): update terraform terraform-ibm-modules/cos/ibm to v8.13.2

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
8.13.1 -> 8.13.2

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.13.2
Compare Source
Bug Fixes

deps: update terraform-module (#748) (62c5981)

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

:tada: This PR is included in version 1.7.3 :tada:
The release is available on:

GitHub release
v1.7.3

Your semantic-release bot :package::rocket:


Convert a number of reference tests, for documents with corrupt XRef tables, from load to eq

As part of attempting to fix a number issues containing PDF documents with corrupt XRef tables, I'd like to improve the reference test-coverage slightly first.
Obviously this will increase the runtime of the tests a bit, however I'd rather "waste" resources on the bots instead of developer time fixing regressions which could have been avoided.

/botio test

Test coverage is indeed very important for such changes. Looks good!
/botio makeref


Fixes issue with not having data because of caching

Fixes #447
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have read CONTRIBUTING.md
[x] I fully understand Github Flow.
[x] My code adheres to the code style of this project.
[x] I have updated the documentation in /docs if I have changed the config, arguments, logic in how the bot works, or anything that understandably needs a documentation change.
[x] I have updated the config file accordingly if my change requires a new configuration setting or changes an existing one.
[ ] I have tested the bot with no issues for 24 continuous hours. If issues were experienced, they have been patched and tested again.

Need to let this run for 24-48 hrs to be sure.

Yep. Was trying to find the most minimal way of fixing the issue. The first call by the Data.* function is what creates an empty cache cause it doesn't use any of that data. But the subsequent calls by lend_all(), if done within the next 60s, will receive the empty array and ticker won't contain the data. getTicker() uses usedCurrencies to do it's filtering.

This wasn't happening on the Poloniex api as there is no cache there, I'm just wondering why the difference. @mahiso might be able to shed light.

Poloniex API 'returnTicker" returns ticker of all pairs. There is no equivalent on Bitfinex to get all in one call, API have to call for each pair separately. Therefore the caching and filtering to reduce the needed calls.

@mahiso I read that too about their API. Sucks. They should change it to allow fetching all. It would reduce their own load as well cause people wouldn't have to make so many calls.

@utdrmac: It is in v2: https://api.bitfinex.com/v2/tickers. But v2 is still beta. One other cool way could be the websocket interface (https://bitfinex.readme.io/v2/reference#ws-public-ticker). But I have not play with it until now.

@utdrmac is this tested now?

I think I hit it again. Not sure if it was holdover from previous iteration or not. Let me keep on this.


databricks-cli: Init at 0.227.0

Description of changes
Add new go based databricks cli tool.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[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

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

2 packages blacklisted:

nixos-install-tools
tests.nixos-functions.nixos-test

2 packages built:

databricks-cli
nixpkgs-manual

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

1 package blacklisted:

nixos-install-tools

3 packages built:

databricks-cli
disko
nixpkgs-manual

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4471


Add helpful comments related to false negatives

Related to #170
Just some helpful comments without changing the logic. This could help in understanding the flow od codec registration checker compiler plugin.

All fixed as suggested


Enhance the query performance in Fast Mode

Enhancement
For some complex queries, the query performance in the fast mode is worse than in the normal mode. Thus we need to enhance the performance in these queries, to make the performance in the fast mode is always better than in the normal mode.

Looks like we cannot reproduce the issue, can we close it? @hongyunyan


fix(be): check if admin when get submissions

Description

closes TAS-837
Get Submissions API 호출 시 Admin은 항상 모든 Submission을 불러올 수 있도록 수정합니다.
Additional context

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines
[ ] Read the Contributing Guidelines and follow the Commit Convention
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

@jimin9038 넵!

아마 사용하지 않을 것 같은데 닫아도 될까요 ?

버그이긴 하지만, 확실히 유즈케이스는 거의 없겠네요...
확인했습니다! 👍


Depth_first_search.c

Title -
what will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[x] Improving Code
[x] Improving Documentation
[x] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[x] Python
[x] C++
[x] Java
[x] C
[x] Go
[x] Other language

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

Hi!
can i send my BFS & DFS code (using C )  for this issue?
thanks!

already added

could you merge my code to?


Uncaught TypeError: Cannot read property 'length' of undefined

[Enter steps to reproduce:]

Do nothing. Wait for it to happen.
It could be about my lists:
list1 = "Bob",        "Bob2",        "Bob3"

Atom: 1.27.2 x64
Electron: 1.7.15
OS: Mac OS X 10.13.3
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'length' of undefined
At /Users/griffin/Desktop/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/screen-line-builder.js:329

TypeError: Cannot read property 'length' of undefined
    at ScreenLineBuilder.emitText (/Users/griffin/Desktop/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/screen-line-builder.js:329:30)
    at ScreenLineBuilder.buildScreenLines (/Users/griffin/Desktop/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/screen-line-builder.js:141:22)
    at DisplayLayer.getScreenLines (/Users/griffin/Desktop/Atom.app/Contents/Resources/app/node_modules/text-buffer/lib/display-layer.js:643:41)
    at TextEditorComponent.queryScreenLinesToRender (/Users/griffin/Desktop/Atom.app/Contents/Resources/app/src/text-editor-component.js:881:57)
    at TextEditorComponent.updateSyncBeforeMeasuringContent (/Users/griffin/Desktop/Atom.app/Contents/Resources/app/src/text-editor-component.js:385:16)
    at TextEditorComponent.updateSync (/Users/griffin/Desktop/Atom.app/Contents/Resources/app/src/text-editor-component.js:275:16)
    at TextEditorComponent.didMouseWheel (/Users/griffin/Desktop/Atom.app/Contents/Resources/app/src/text-editor-component.js:1560:59)

Commands
  2x -0:21.6.0 editor:newline (input.hidden-input)
  3x -0:19.6.0 core:backspace (input.hidden-input)

Non-Core Packages
clear-night-syntax 1.3.17
clear-night-ui 1.4.2
no-caffeine-syntax 0.18.1
teletype 0.13.2

I restarted atom, it's now fixed.

how do i close this

oh nvm


Bug: getTranslationsByFromDefinitionId resolver called multiple times in useEffect hook

Go to maps, hit translate all, get this output:
getTranslationsByFromDefinitionId resolver
multiple times. I think useEffect is executing too many times

EXPLAIN select distinct
cursor,
type,
o_id,
o_like_string,
o_definition,
o_definition_id,
o_language_code,
o_dialect_code,
o_geo_code,
o_created_at,
o_created_by
from v_map_words_and_phrases_with_tr_info
where true
and o_language_code = 'en' and (some_to_word_tr_id is null and some_to_phrase_tr_id is null)
order by cursor ASC limit 30

data-1698329361845.csv


clickSchedule/beforeCreateSchedule/beforeUpdateSchedule events do not fire in v2.1.3

Version
2.1.3
Test Environment
Google Chrome, Microsoft Edge
Current Behavior
Based on the suggestions in this past issue: https://github.com/nhn/tui.calendar/issues/812 , I am trying display a custom pop for event creation:
        .  .  .
        const options = {
            defaultView: 'week',
            usageStatistics: false,
            useFormPopup: false,
            useDetailPopup: false,
            useCreationPopup: false,
            timezone: {
                zones: [
                {
                    timezoneName: 'America/Los_Angeles',
                    displayLabel: 'Los Angeles',
                },
                ],
            },
            calendars: [
                {
                id: 'calendar1',
                name: 'Personal',
                },
            ],
            week: {
                taskView: false,
            },
        };

        const Calendar = tui.Calendar;
        this.calendarInstance = new Calendar(container, options);

        // Event handlers
        //
        this.calendarInstance.on({
          'clickSchedule': function(e) {
              console.log('clickSchedule', e);
          },
          'beforeCreateSchedule': function(e) {
              console.log('beforeCreateSchedule', e);
          },
          'beforeUpdateSchedule': function(e) {
              console.log('beforeUpdateSchedule', e);
          },
          'beforeDeleteSchedule': function(e) {
              console.log('beforeDeleteSchedule', e);
          }
        });

However, when I  click the calendar to create a new event, none of these events fire/nothing is printed in the console:

Note: If i  re-enable  useFormPopup: true, useDetailPopup: true, useCreationPopup: true, I  am able to use other events such as beforeCreateEvent, beforeUpdateEvent, beforeDeleteEvent, etc. However, these above events still do not fire.
Expected Behavior
Are these events not supported any longer? How can I  display custom pop-ups in the current version?
Thank you!

It's a duplicate of #1262.
https://github.com/nhn/tui.calendar/issues/1262#issuecomment-1227816561
Please note that we don't use the term 'Schedule' anymore. You've read an issue about the previous version but same strategy is needed to create custom popups.
https://github.com/nhn/tui.calendar/blob/main/docs/en/guide/migration-guide-v2.md#change-term-from-schedule-to-event


Broken links in README.md

The link to AUDITS.md is broken, I think because it uses the wrong case (s/Audits.md/AUDITS.md/).
The link to callsha is broken. I think it needs to be Verification/VST/sha.

Also, s/Valdiation/Validation/

Thanks for the reports.


Error listening for ICMP packets: socket: permission denied

Run as root, but have a error: Error listening for ICMP packets: socket: permission denied

so... what was the solution ?


Upgrade to Python 3.7

We've just upgraded to Python 3.5, which is the version available in stretch.
We should upgrade to Python 3.7.  This means we can run black in the development environment, and opens up shiny new features.

When we do this, we should reopen https://github.com/ebmdatalab/openprescribing/pull/2245, and check whether any other unmerged dependency PRs should be reopened.

As per #2925 and #2926 we've now upgraded to Python 3.8.
Closing this and pulling dependency review stuff in a new ticket.


Cannot find the training data

Hi,
Thanks for holding this interesting task.
I carefully read this repo, but cannot find the entry to download the training data.
Is this dataset released?

not yet! finalizing to release tonight or tomorrow morning at latest!

training data has been released! more to come.


fix(Babel): Rename stryker-babel to stryker-babel-transpiler

I renamed it. Let's see if this build succeeds 🥇


BUG: fixes datetime resampling

Reference issue
Closes #16216
What does this implement/fix?

Additional information

Thank you for the PR @SahebehDadboud. LGTM based on the example in the issue. Could you add a test for this actually? It would just be running your example and checking the values are as expected.

working on it.

FYI we are freezing the next release at the end of the week.

we are freezing the next release at the end of the week.

thanks for the update. I had problems writing a test (as a total beginner). I got sense of it, but still not completely done. I can push with what I wrote already. The test functions works, but testing it with numpy.testing.assert_allclose or any other testing, it gives mismatch or even errors.

Feel free to push. It's then easier to help. If you are worried about using too much CI, you can disable some. E.g. add the following in the commit message to not build doc (which here makes sense) [skip circle].

CI failure is related here.

CI failure is related here. Could you also merge main to your branch? Otherwise more CI will fail.

@tupui I've merged the main to my branch. Anything else I have to do?
btw, I've tested the function I wrote and It throws errors. You can of course see the errors.

@tupui I've merged the main to my branch. Anything else I have to do?
btw, I've tested the function I wrote and It throws errors. You can of course see the errors.

The CI needs to pass so we need to fix the errors.

@tupui I've merged the main to my branch. Anything else I have to do?
btw, I've tested the function I wrote and It throws errors. You can of course see the errors.

The CI needs to pass so we need to fix the errors.

@tupui I just familiarised myself more with testing. yet on my local machine all of the tests fail. is there anything I can do?

@tupui I just familiarised myself more with testing. yet on my local machine all of the tests fail. is there anything I can do?

How did you build SciPy? You need to follow this guide https://scipy.github.io/devdocs/dev/dev_quickstart.html (use conda and dev.py).
Does the test you added work on your side?
Otherwise, please revert the changes in _lib and optimize. This is making the CI fail.

yes I did everything on a Conda env (scipy-dev), but I don't know why nothing works. I might have changed interpreter and now I don't know on which one I built everything. I guess I do everything from scratch.
that's the last error I got by running tests:
ImportError: The scipy install you are using seems to be broken, (extension modules cannot be imported), please try reinstalling.

@tupui I just familiarised myself more with testing. yet on my local machine all of the tests fail. is there anything I can do?

How did you build SciPy? You need to follow this guide https://scipy.github.io/devdocs/dev/dev_quickstart.html (use conda and dev.py).
Does the test you added work on your side?
Otherwise, please revert the changes in _lib and optimize. This is making the CI fail.

yes I did everything on a Conda env (scipy-dev), but I don't know why nothing works. I might have changed interpreter and now I don't know on which one I built everything. I guess I do everything from scratch.
that's the last error I got by running tests: ImportError: The scipy install you are using seems to be broken, (extension modules cannot be imported), please try reinstalling.

@tupui I just familiarised myself more with testing. yet on my local machine all of the tests fail. is there anything I can do?

How did you build SciPy? You need to follow this guide https://scipy.github.io/devdocs/dev/dev_quickstart.html (use conda and dev.py).
Does the test you added work on your side?
Otherwise, please revert the changes in _lib and optimize. This is making the CI fail.

@tupui I was constantly getting error even with building the setups. I'll do everything from scratch

What do you mean with building the setups? You must not build all setups yourself. The guide is telling you to

Init git submodules
Setup a conda env using our environment file
Build using python dev.py build

If you do anything else, you will likely trouble to make it work or it will just be broken if you miss some manual steps.

Looks like we have a bug with GitHub here. I have no clue what happened but it's saying you merge your branch with scipy/main which is not the case since you don't have rights

well I never thought it's that easy to merge sth to main. I hope it didn't make that much troubles.
regarding python dev.py build. it threw errors multiple times. I did the same procedure as you mentioned.

No worries, you did not merge anything to main. It's just here that it wrongly tells us that. I am not sure what you did to get the UI to do that but as it is your PR is closed and I cannot even reopen it. So you might have to create a new one.
What errors do you have? Can you post a log?

No worries, you did not merge anything to main. It's just here that it wrongly tells us that. I am not sure what you did to get the UI to do that but as it is your PR is closed and I cannot even reopen it. So you might have to create a new one.
What errors do you have? Can you post a log?
@tupui  ok I'm losing my brain over this. after doing the steps you mentioned, this is what I get,  and yes the whole time. any help would be appreciated.

[import scipy
Traceback (most recent call last):
File "/Users/sahebedadboud/Projects/scipy/scipy/init.py", line 121, in
from scipy.config import show as show_config
ModuleNotFoundError: No module named 'scipy.config'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "", line 1, in
File "/Users/sahebedadboud/Projects/scipy/scipy/init.py", line 126, in
raise ImportError(msg) from e
ImportError: Error importing SciPy: you cannot import SciPy while
being in scipy source directory; please exit the SciPy source
tree first and relaunch your Python interpreter.](url)

@SahebehDadboud Did you follow the instructions from the error message?
ImportError: Error importing SciPy: you cannot import SciPy while
        being in scipy source directory; please exit the SciPy source
        tree first and relaunch your Python interpreter.

Note that if you do this you also need to manually set your PYTHONPATH to the build directory (not the source directory).
Instead, simply use python dev.py test --help. You also have other commands such as shell and ipython.

@SahebehDadboud Did you follow the instructions from the error message?
ImportError: Error importing SciPy: you cannot import SciPy while
        being in scipy source directory; please exit the SciPy source
        tree first and relaunch your Python interpreter.

Note that if you do this you also need to manually set your PYTHONPATH to the build directory (not the source directory).
Instead, simply use python dev.py test --help. You also have other commands such as shell and ipython.

to be honest it worked this time.

@SahebehDadboud Did you follow the instructions from the error message?
ImportError: Error importing SciPy: you cannot import SciPy while
        being in scipy source directory; please exit the SciPy source
        tree first and relaunch your Python interpreter.

Note that if you do this you also need to manually set your PYTHONPATH to the build directory (not the source directory).
Instead, simply use python dev.py test --help. You also have other commands such as shell and ipython.

@tupui  to be honest it worked this time.


Prepare 0.18.0 release

Summary
To prepare for the upcoming 0.18.0 release this commit moves all the
release notes into a 0.18 subdirectory to keep them separate from future
development notes post-release. It also adds a release note with the
prelude section providing the high level overview of the release. When
this merges it should be the commit used to tag the 0.18.0 release.
Details and comments
TODO:

[x] Rewrite and fix release notes

Ok, I've finished my first pass at the release notes we have so far. So this is basically ready for review now. But I'm leaving it as on hold until we're ready to release so that I updated all the release notes that for the open PRs for the release which haven't merged yet.

ok, now that #6581 has merged this is unblocked now and we can release. Once this is approved and merged we'll tag the 0.18.0 release


2023 / 2024 schedule out yet available?

Just curious how ya'll create your schedules easily if there is a way? Guess no one has an updated schedule out yet. Thanks

Are you on the discord?  I make an excel file each year to generate SQL for the update and just posted it there.
https://discord.gg/mByMgc7n

Ok. Thank you rbiddle.

Hi Robert,
For some reason, I can't verify myself on Discord. I've verified my email, but now
it wants to bot me, but still can't get to the script for some reason. Any clues ?
Thanks so much

On 07/26/2023 7:31 PM EDT Robert Biddle @.***> wrote:
Are you on the discord? I make an excel file each year to generate SQL for the update and just posted it there..
https://discord.gg/mByMgc7n
—
Reply to this email directly, view it on GitHub https://github.com/rothkj1022/phppickem/issues/53#issuecomment-1652681310, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANLUW2E5U2Z3J3D23PPVNU3XSGSDXANCNFSM6AAAAAA2ZAHFEA.
You are receiving this because you authored the thread.Message ID: @.***>

Can anyone post their 2023 schedule here?.   I also tried Discord and verified.   Was not able to located the file.   A SQL export preferred...

fetchSchedule.php.zip
This is a page that I wrote it scrapes the games/times from ESPN. There's a debug flag towards top of the code that just echos the output into the browser if set to true, if set to false it deletes all data from picks/ picksummary / schedule tables and then dumps new schedule into the schedule table.
I've used it for a few years and figured I would share it here as people seem to have this question every year.
** Use at your own risk. I recommend a full DB backup before running something like this. **

That worked great.  Very much appreciated!
From: The Wizard of Foss @.>
Sent: Tuesday, August 1, 2023 3:18 PM
To: rothkj1022/phppickem @.>
Cc: Subscribed @.***>
Subject: Re: [rothkj1022/phppickem] 2023 / 2024 schedule out yet available? (Issue #53)
fetchSchedule.php.ziphttps://github.com/rothkj1022/phppickem/files/12233194/fetchSchedule.php.zip
This is a page that I wrote it scrapes the games/times from ESPN. There's a debug flag towards top of the code that just echos the output into the browser if set to true, if set to false it deletes all data from picks/ picksummary / schedule tables and then dumps new schedule into the schedule table.
I've used it for a few years and figured I would share it here as people seem to have this question every year.
** Use at your own risk. I recommend a full DB backup before running something like this. **
—
Reply to this email directly, view it on GitHubhttps://github.com/rothkj1022/phppickem/issues/53#issuecomment-1660937297, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA5CUMMZROHQW4KHSD5O2DTXTFI57ANCNFSM6AAAAAA2ZAHFEA.
You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>

Wow thewizardoffoss, THANK YOU!!!
Thank you so much for your effort on this.

Here's my version of the build schedule with the espn api to run from command line.
Also de SQL for this 2023-2024 season, pay attention to the collate version of your DB, mine is COLLATE utf8_general_ci.
I hope it helps.
buildSchedule2_ElWert0.txt
SQL_nfl_schedule_2023_by_elWert0.txt

Here's my version of the build schedule with the espn api to run from command line.
Also de SQL for this 2023-2024 season, pay attention to the collate version of your DB, mine is COLLATE utf8_general_ci.
I hope it helps. buildSchedule2_ElWert0.txt SQL_nfl_schedule_2023_by_elWert0.txt

the gametime is off by 1 hour,
UPDATE nflp_schedule
SET gameTimeEastern = DATE_ADD(gameTimeEastern, INTERVAL 1 HOUR);


Terminal prompt occurs midway through Neofetch image on Kinetic Kudu Beta.

Description
The terminal prompt "chadano@ubuntu:~$" occurs midway through Neofetch Image on Ubuntu 22.10 Kinetic Kudu Beta.

[x] Does this issue still occur in the master branch? (Required if issue)

Neofetch version
Neofetch 7.1.0
Ubuntu 22.10 Kinetic Kudu Beta
Screenshot

Config file
Unedited, default config file.
Verbose log
https://pastebin.com/5B3k0vxH

I've confirmed this aswell and assigned Launchpad Bug 1991457 to this: https://bugs.launchpad.net/ubuntu/+source/neofetch/+bug/1991457

Confirming this bug occurs as well.  The terminal prompt always ends up the line under the machine specifications and cuts through the logo produced regardless.

This also occurs on macOS.

Yep, occuring here too
-using fish in android termux

Also occurs on fedora

/usr/bin/neofetch: line 3985: bad substitution: no closing `}' in ${block_spaces// /${blocks}nl}
probably something similar to bug for bash 5.2+. try fixes came up in #2195.

If neofetch --disable cols works for you when you hide the color bars, then I think it’s the same issue as #2195.
Worst case: neofetch --disable title underline distro model kernel uptime packages shell resolution de wm term term_font cpu gpu memory

If neofetch --disable cols works for you when you hide the color bars, then I think it’s the same issue as #2195.
Worst case: neofetch --disable title underline distro model kernel uptime packages shell resolution de wm term term_font cpu gpu memory

Experienced the same issue on fedora. --disable cols solved it for me.

for me I repaired it by replacing this line 3803 and 304 :
 [[` "$blocks"  ]] && cols+="${block_spaces// /${blocks}nl}"
 [[ "$blocks2" ]] && cols+="${block_spaces// /${blocks2}nl}"

by this:
 [[ "$blocks"  ]] && cols+="${block_spaces// /${blocks}nl]}"
 [[ "$blocks2" ]] && cols+="${block_spaces// /${blocks2}nl]}"

I just closed the squared bracket

@Sir-Thom 's solution of closing the square bracket no longer results in an error when executing get_cols(). However, this resulted in the added square brackets becoming visible in the output. (See below)

There did not appear to be any issues resulting from removing the square brackets entirely, and that also resolved the error.
[[ "$blocks"  ]] && cols+="${block_spaces// /${blocks}mnl}"
[[ "$blocks2" ]] && cols+="${block_spaces// /${blocks2}mnl}"

I will not take any action in the form of a pull request myself, because I am not aware of the purpose of aforementioned the square brackets. But, if someone else is able to determine that they serve no purpose, that is the solution that worked for me.

@JacksonBarker  it seem that by correcting the line to this
     # Convert the spaces into rows of blocks.
        [[ "$blocks"  ]] && cols+="${block_spaces// /${blocks}nl}"
        [[ "$blocks2" ]] && cols+="${block_spaces// /${blocks2}nl}"

        # Add newlines to the string.
        cols=${cols%%nl}
        cols=${cols//nl/
[${text_padding}C${zws}}

seem to fixes more correctly the issue  it gave me those result

note: my first square is the same color as my background.

Same issue on OpenSUSE MicroOS:

Passing --disable cols parameter "fixes" it:

The column cutoff issue on Bash ≥5.2 is fixed in HyFetch 1.4.3 / neowofetch 7.3.3 by the pull request https://github.com/hykilpikonna/hyfetch/pull/24.

HyFetch is a fork of neofetch with LGBTQ pride flags, but the repo also maintains an updated version of the original neofetch, addressing many pull requests that are not merged in the original repo.
Read the "Running Updated Original Neofetch" section for more info!

It is a bug of Bash 5.2. Bash 5.2.4 has fixed it.
Debian has packaged Bash 5.2.15-2 and accepted it into testing ("Bookworm") and unstable ("Sid") recently. If you are using these Debian suites, upgrade your Bash installation.
Ubuntu is a package thief. It steals packages from Debian unstable ("Sid") constantly. For now, Bash 5.2.15-2 has been stolen from Debian, patched with Ubuntu-specific patches, and entered the proposed repository of Lunar Lobster. Probably in a few days, it will enter the main repository of Lunar Lobster, and some extra days after that it should be able to enter the Kinetic Kudu repository.


Fix ruby generator tests

@haywood These tests seem to have been broken in 2015, fixing since I have another pull request I'm working on.

thanks! merging


Siting - Getting to know pints

This is just a primer to understand the logic of pints a little bit, as we will need this later in the project.
Create a notebook that solves the SIR model, and is able to recover the parameters using a pints.optimiser

[ ] Look at the in pints implemented SIR model, solve the model and create a line chart plot with plotly. See https://pints.readthedocs.io/en/stable/toy/sir_model.html for documentation of SIR model.
[ ] Following the example notebook here recover the parameters.
[ ] For this you need to tie the model to the simulation results using a pints.SingleOutputProblem
[ ] and then use the pints.optimise function. Use the pints.CMAES optimiser to recover the parameters.
[ ] Compare the parameters used for the simulation to the recovered parameters.

@siting-miao  Check out #32 for more details on the inference notebook for tomorrow.

You can find a notebook implementing all the above here (Feel free to use this for your presentation tomorrow).


community: Fix sparkllm authentication problem.

Description: fix sparkllm authentication problem.The current timestamp is in RFC1123 format. The time deviation must be controlled within 300s. I changed to re-obtain the url every time I ask a question. https://www.xfyun.cn/doc/spark/general_url_authentication.html#_1-2-鉴权参数

@baskaryan PTAL


Metrics/initial catchup time

Thank you for contributing to Mina! Please see CONTRIBUTING.md if you haven't
yet. In that doc, there are more details around how to start our CI.
Explain your changes here.
Explain how you tested your changes here.
Checklist:

[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

Closes #0000
Closes #0000

Can you fill out the initial PR comment?


fix build error in RIP-28 at getmQclientFactory

Make sure set the target branch to develop
What is the purpose of the change
fix build error in RIP-28 at getmQclientFactory
Brief changelog
change to getmQclientFactory
Verifying this change
mvn compile -DskipTests
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

link #3694


Split open form command by whitespace char

Closes https://github.com/flow-storm/flow-storm-debugger/issues/162

Thanks @alexmalcoci !


Node modules

Hey,
Does this work with node modules. If so how does it work? (Is there an example)

Yes if the node modules don't use node. I'd recommend bundling with https://esbuild.github.io/ then passing the bundle into gov8,.

Yes if the node modules don't use node.

I think this means things like require aren't available, because it's a higher-level Node API, not V8.
So, many modules will work, but if a module uses Node's APIs, they will fail at runtime. For example:
ReferenceError: require is not defined

I have not been able to find a work-around. So, I guess I'll have to pull Node itself into this project, run it as a subprocess, and implement a bridge API (perhaps using go-plugin).

I second what @matthewmueller suggested, that's what I use to run most npm packages on v8go

As mentioned I also recommend esbuild for this. Just dont use stuff from node like fs or crypto etc and esbuild will bundle everything to a single file you can load.

Does single file builds with rollup work too?
I receive this error when trying to call an exported function bundle.js
Let's say I have deguasser.js (bundle file). And I have the following .go code
func callDegausser(node string, options string) {
	ctx := v8.NewContext()

	importDegausser := `var degausser = require('./degausser.js');`
	consoleLog := `console.log('WORKING!'); `
	callDegausser := importDegausser + consoleLog + `degausser('` + "" + `','` + "" + `')`

	// val, _ := ctx.RunScript(importDegausser + callDegausser, "degausser.js") // executes a script on the global context
	val, err := ctx.RunScript(callDegausser, "degausser.js") // executes a script on the global context

	log.Println("value: ", val, err)
}

I'm receving ReferenceError: require is not defined error

@sb-bilal-dev-ev as I commented above,
require is a Node API. It's not part of V8. It won't work in this context.

I'm running into a similar issue.
I've bundled a small script that uses external modules with esbuild, but when importing packages (either through require or import keyword), I always get the SyntaxError: Unexpected identifier or similar syntax errors, with no further details.
Is there any way to make this more verbose so I can understand what's going on?


Tell users accepted characters next to fields

Making them pretty costs extra

@skylenewman what fields are you referring to?


Karpenter unable to handle pod affinity rules while the node is starting up

Version
karpernter version: v0.27.1
eks k8's version: 1.25
Expected Behavior
I want group of pods(size = 3) land on the same node. the number of groups can be 100 or more.
Actual Behavior
I set the affinity rules for every group of pods and k8's seem to schedule fine as long the node is completely provisioned and ready however during the launch of a node by karpenter the pods go to pending state and never get scheduled. It fails with the following error

Warning  FailedScheduling  2m4s (x4 over 2m30s)  default-scheduler  0/3 nodes are available: 1 Insufficient memory, 1 node(s) didn't match pod affinity rules, 2 Insufficient cpu. preemption: 0/3 nodes are available: 1 Preemption is not helpful for scheduling, 2 No preemption victims found for incoming pod.
  Warning  FailedScheduling  64s (x15 over 2m14s)  karpenter          (combined from similar events): Failed to schedule pod, incompatible with provisioner "default", key kubernetes.io/hostname, kubernetes.io/hostname DoesNotExist not in kubernetes.io/hostname In [hostname-placeholder-0129]

Steps to Reproduce the Problem
set the affinity rules similar to the spec below for a group of pods, turn off consolidation and launch a set of pods until a new node is getting spun up. watch the pod carefully when the node is getting spun up. it will result in an error
    spec:
      affinity:
        podAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: groupId
                    operator: In
                    values:
                      - "{{ .GroupId }}"
              topologyKey: "kubernetes.io/hostname"

Resource Specs and Logs
    spec:
      affinity:
        podAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: chainId
                    operator: In
                    values:
                      - "{{ .ChainId }}"
              topologyKey: "kubernetes.io/hostname"

here is my provisioner
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
 name: default
spec:

 providerRef:
   name: default
 requirements:
 - key: karpenter.k8s.aws/instance-category
   operator: In
   values:
   - c
   - m
   - r
 - key: karpenter.k8s.aws/instance-generation
   operator: Gt
   values:
   - "2"
 - key: karpenter.k8s.aws/instance-family
   operator: In
   values: [c5, r5]
 # Exclude small instance sizes
 - key: karpenter.k8s.aws/instance-size
   operator: NotIn
   values: [nano, micro, small, large]
 - key: "karpenter.k8s.aws/instance-cpu"
   operator: In
   values: ["16", "32"]

 kubeletConfiguration:
   maxPods: 96

 # If omitted, the feature is disabled and nodes will never expire.  If set to less time than it requires for a node
 # to become ready, the node may expire before any pods successfully start.
 ttlSecondsUntilExpired: 2592000 # 30 Days = 60 * 60 * 24 * 30 Seconds;

---
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
 name: default
spec:
 securityGroupSelector:
   karpenter.sh/discovery: "eks-cluster-1"
 subnetSelector:
   karpenter.sh/discovery: "eks-cluster-1"
 blockDeviceMappings:
   - deviceName: /dev/xvda
     ebs:
       volumeSize: 200Gi
       volumeType: gp3
       iops: 10000
       encrypted: true
       deleteOnTermination: true
       throughput: 125

Here is the error from describing one of the pending pods

Warning  FailedScheduling  2m4s (x4 over 2m30s)  default-scheduler  0/3 nodes are available: 1 Insufficient memory, 1 node(s) didn't match pod affinity rules, 2 Insufficient cpu. preemption: 0/3 nodes are available: 1 Preemption is not helpful for scheduling, 2 No preemption victims found for incoming pod.
  Warning  FailedScheduling  64s (x15 over 2m14s)  karpenter          (combined from similar events): Failed to schedule pod, incompatible with provisioner "default", key kubernetes.io/hostname, kubernetes.io/hostname DoesNotExist not in kubernetes.io/hostname In [hostname-placeholder-0129]

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

2023-04-04T18:21:28.975Z	INFO	controller.provisioner	found provisionable pod(s)	{"commit": "7131be2-dirty", "pods": 33}
2023-04-04T18:21:28.975Z	INFO	controller.provisioner	computed new machine(s) to fit pod(s)	{"commit": "7131be2-dirty", "machines": 1, "pods": 2}
2023-04-04T18:21:28.975Z	INFO	controller.provisioner	launching machine with 2 pods requesting {"cpu":"4155m","memory":"4216Mi","pods":"5"} from types c5.4xlarge, r5.4xlarge, r5.8xlarge	{"commit": "7131be2-dirty", "provisioner": "default"}
2023-04-04T18:21:29.036Z	DEBUG	controller.provisioner.cloudprovider	discovered kubernetes version	{"commit": "7131be2-dirty", "provisioner": "default", "kubernetes-version": "1.25"}
2023-04-04T18:21:29.076Z	DEBUG	controller.provisioner.cloudprovider	discovered new ami	{"commit": "7131be2-dirty", "provisioner": "default", "ami": "ami-0a3da8b47de1d87b8", "query": "/aws/service/eks/optimized-ami/1.25/amazon-linux-2/recommended/image_id"}
2023-04-04T18:21:32.017Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "7131be2-dirty", "provisioner": "default", "id": "i-03977264ff6381b65", "hostname": "ip-172-16-114-70.ec2.internal", "instance-type": "c5.4xlarge", "zone": "us-east-1b", "capacity-type": "on-demand"}
2023-04-04T18:21:37.573Z	ERROR	controller.provisioner	Could not schedule pod, incompatible with provisioner "default", key kubernetes.io/hostname, kubernetes.io/hostname DoesNotExist not in kubernetes.io/hostname In [hostname-placeholder-0069]	{"commit": "7131be2-dirty", "pod": "saga-kantchain-1680622524149559-1/chainlet-7cb4f48ccb-46f88"}
2023-04-04T18:21:37.573Z	ERROR	controller.provisioner	Could not schedule pod, incompatible with provisioner "default", key kubernetes.io/hostname, kubernetes.io/hostname DoesNotExist not in kubernetes.io/hostname In [hostname-placeholder-0070]	{"commit": "7131be2-dirty", "pod": "saga-kantchain-1680622288085200-1/blockscout"}
2023-04-04T18:21:37.573Z	ERROR	controller.provisioner	Could not schedule pod, incompatible with provisioner "default", key kubernetes.io/hostname, kubernetes.io/hostname DoesNotExist not in kubernetes.io/hostname In [hostname-placeholder-0071]

Can you share your full pod/deployment spec as well?

apiVersion: apps/v1
kind: Deployment
metadata:
  name: "{{ .Name }}"
  namespace: "{{ .Namespace }}"
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: "{{ .Name }}"
  template:
    metadata:
      labels:
        app: "{{ .Name }}"
        chainId: "{{ .ChainId }}"
      annotations:
        prometheus.io/scrape: "true"
        prometheus.io/port: "26660"
    spec:
      affinity:
        podAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: chainId
                    operator: In
                    values:
                      - "{{ .ChainId }}"
              topologyKey: "kubernetes.io/hostname"
      containers:
        - image: "{{ .Image }}"
          name: "{{ .Name }}"
          imagePullPolicy: Always
          env:
          - name: CHAINID
            value: "{{ .ChainId }}"
{{ range $key, $value := .EnvVars }}
          - name: {{ $key | ToUpper }}
            value: "{{ $value }}"
{{ end }}
{{ range $key, $value := .SpcVars }}
          - name: SPCPARAM_{{ $key | ToUpper }}
            value: "{{ $value }}"
{{ end }}
          ports:
            - containerPort: 9090
            - containerPort: 1317
          resources:
            requests:
              memory: "2Gi"
              cpu: "1"
            limits:
              memory: "4Gi"
              cpu: "2"
          volumeMounts:
          - name: "saga-{{ .Name }}-persistent-storage"
            mountPath: "/root/.sagaevmd"
      volumes:
      - name: "saga-{{ .Name }}-persistent-storage"
        persistentVolumeClaim:
          claimName: "saga-{{ .Name }}-pvc"
      restartPolicy: Always

Discussed in slack. You're running into common hostname affinity + autoscaling issues. Recommendation is to run the containers in the same pod. https://kubernetes.slack.com/archives/C02SFFZSA2K/p1680612757618919


Design System >  There is no option in raaghu to disable datepicker & we are getting todays date as default value (we want as blank initially). While clearing the selected dates I am getting issue. (Image is from client site)

There is no option in raaghu to disable datepicker & we are getting todays date as default value (we want as blank initially). While clearing the selected dates I am getting issue. (Image is from client site)

@suchithravipin1991  PR not attached  against task

@hemalatagaikwad  : PR attached

Fixed on staging


cv::putText for non-ascii characters

love from china

implemented since https://github.com/nihui/opencv-mobile/commit/b71dcfe02f8d5be40711bb42240cd8bad45885a1


Refactor failure recovery

Proposed changes
Refactors the recovery mechanism in order to first retrieve the Tendermint recovery parameters via the ACN before attempting to reset.
Fixes
n/a
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[x] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
n/a

Interesting e2e failure:
>       assert missing_agent_logs == "", missing_agent_logs  # nosec
E       AssertionError: Strings ['local height == remote height; continuing execution...'] didn't appear in agent_00001 output.
E       ''registration_startup_round' round is done with event: Event.DONE' appeared only 0 out of 1 times


The related bug id is incorrect on Releases Notes Fixes section

Storage Explorer Version: 1.11.1
Build: 20191120.3
Branch: hotfix/1.11.1
Platform/OS: Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer -> Help -> View Release Notes.
Check the third and four fix bugs id in Fixes section.

Expect Experience:
The related bug id is correct.
Actual Experience:
The related bug id is incorrect.

Fixed.


Pod label not coming up for some pod

We have deployed the dcgm exporter to get the gpu related metrics. We are able to get the metric, but for some application the pod label is not coming up ( but for some we are getting the label ) and they are running in same namespace.
Image version -- nvcr.io/nvidia/k8s/dcgm-exporter:2.3.1-2.6.0-ubuntu20.04
We are running this on EKS 1.21 version.
and we using the "uid" to get the GPU label.
            - name: DCGM_EXPORTER_KUBERNETES
              value: 'true'
            - name: DCGM_EXPORTER_LISTEN
              value: ':9400'
            - name: DCGM_EXPORTER_KUBERNETES_GPU_ID_TYPE
              value: uid

@tsingh-asapp,
Could you provide raw output from the dcgm-exporter monitoring (Prometheus format) for both cases?
Could you also clarify the dcgm-exporter command line arguments you specify in the values.yaml file (I assume you are using Helm)?

@nikkon-dev i found the issue, The is related to the  nvidia.com/gpu: '1' . As i understand from the code , this is need by the exporter to identify the application which use the gpu. This value in required in the limit section of the pod resource at pod/deployment template.
We can close the case


Side panel filters does not reset after using search box

Steps to reproduce:

Navigate to table
Select any 1 service from the side panel filter
search any table
Clear the search criteria and Hit Enter
Clear side panel filters
Verify side panel filter

Thanks @kshinde2512 for filing this.
@parthp2107 we need to catch these kind of bugs in our tests cc @shahsank3t


Change class name UclaMiniscopeV4CameraFrame -> UclaMiniscopeV4CameraDataFrame

This name change suggestion is to adhere to our naming convention. The operator is UclaMiniscopeV4CameraData so its corresponding frame should be appended by "Frame": UclaMiniscopeV4CameraDataFrame.

There apparently was a discussion about why this particular operator had a different name.
If this is the case, we should at least document in the code the rationale for not adhering to the convention.


advisory: stream command

Start version streaming for a package by moving its advisories into a new package.
This command will move most advisories for the given package into a new package. And rename the
package to the new package name. (i.e., from foo.advisories.yaml to foo-X.Y.advisories.yaml) If the
target file already exists, the command will try to merge the advisories. To ensure the advisories
are up-to-date, the command will start a scan for the new package.
The command will move the latest event for each advisory, and will update the timestamp
of the event to now. The command will not copy events of type "detection", "fixed",
"analysis_not_planned", or "fix_not_planned".

Test it:
1. `go install .`
2. Jump to https://github.com/wolfi-dev/advisories/ dir
3. Run `wolfictl advisory stream kyverno kyverno-1.12`

Thanks for doing this, @Dentrax! This looks like it will be useful.
One overall question before diving in too deep: would this be more useful as a generalized "move"/"rename" command? It sounds like one use case is when we start to version stream a package that wasn't version streamed before, like the kyverno example. But IIUC, the same logic applies for any package rename — does that sound right to you?
I'm wondering if by generalizing this command to something like wolfictl advisory mv (inspired by and analogous to the Unix mv command, which handles file renames too), and keeping almost all of the logic in this PR (minus the version stream regex checking), we'd solve not just the "new version stream" case but all package rename cases... and also be well on our way to a "moved across repos" solution as well. What are your thoughts? Feel free to tell me I'm misunderstanding things here. 😄

Great advice @luhring! Renamed to move (mv). 👍

Would you mind looking at the code a bit again before we review further? It looks like there is still some version stream logic left over, documentation files from the old command name, and references to scanning that we ended up deciding not to do. Once this is in a state that's ready for more scrutiny, just ping me!

Apologies for the oversight @luhring! I should have double-check it.
It's now ready for review. PTAL when possible!

and references to scanning that we ended up deciding not to do.

I couldn't find this, actually i didn't include this functionality. 🤔


ledc: Do not drive output during init if the output is inverted (IDFGH-6875)

If the output of LEDC GPIO is inverted, then the correct level must be set before initializing the GPIO, otherwise it will be driven until the next call to stop LEDC output.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

No.
If the output is inverted, and gpio_set_level() is called after
gpio_set_direction(), then the output will have an invalid value for a
short period of time.
Setting the level before the direction avoids the invalid output.
On Fri, Mar 4, 2022, 15:15 Pedro @.***> wrote:

@.**** commented on this pull request.
Shouldn't gpio_set_direction be called before gpio_set_level?
—
Reply to this email directly, view it on GitHub
https://github.com/espressif/esp-idf/pull/8497#pullrequestreview-900276696,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADAIHNSE2H5UF6DBA5YAKTU6ILITANCNFSM5P4ZK5NA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

sha=062f6164ae89d54df3f1a89a67f01e82ae56e0d8

@nonoo Unrelated to the PR, but not completely, I found out I know nothing about GPIOs. Can you tell me why driving a GPIO before setting the direction works? And since it works and it's set to output, why set the direction at all?


Hardware Setup

Haven't found Q&A section, so will leave the question here.
I really want to reproduce your setup, but I don't understand how do you stream the video over wifi from the camera connected to RPi.
Could you please explain? Thank you in advance.

Hi Igor. Video is not being streamed over wifi. The camera is plugged directly into the Raspberry Pi and handled with cv2.VideoCapture
Let me know if that helps.

Thank you, Tim.
So, am I right that the video of the flight with the horizon overlay was recorded onboard, it was not an fpv stream to a goggles/screen?

Onboard, I only record the raw video and some diagnostic data, which includes the horizon detections and everything else necessary for producing the video with the overlay. After the flight, I run produce_video.py to produce the overlay video that you are referring to


bug: z-index issue with iOS

Type: bug
Platform: ios 7 webview
Seems that with the new click-blocks setup, there are some z-index problems on iOS.
http://codepen.io/mhartington/pen/mHjDv
So if you open the side-menu in a browser or android device it all works fine. But on ios, the background image does not show.
Inspecting the side-menu in safari's dev tools shows that there is a z-index of 0 being added. When you comment this out, the image shows correctly.

Greetings, @mhartington!
My sensors indicate that this issue has been inactive for a while.
Due to this, the issue will be closed in 7 days.
If you believe the issue has not been fixed, please add a comment.
This will notify us so we can assist you, and will prevent the issue from being automatically closed.
Feel free to include the following information about the issue, so that we may assist you:

Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
What platform does this happen on? (iOS, Android, all, etc.)
What platform versions does this happen on? (Android 4.2, iOS 7, all, etc.)
Is this an issue with the Ionic Framework, or Ionic CLI?

Thank you for allowing me to assist you.

Does't appear to be an issue anymore.


Error during project generation

Hi George,
Thanks for this generator, it looks really interesting but unfortunately it hasn't work for me yet.
I keep getting the following error message when I attempt to generate a project using "yo makrina".
I have tried in in an Windows environment and with Ubuntu and different node version. Maybe you can help?
Ubuntu with Node v4.7.0
? Project name osboxes
? Verbose name Osboxes
? Description Osboxes
? Git repository URL
? Author
? Organization
? Organization URL
? Deploy host
? New Relic license key
? Angular app short name admin
? Angular app name osboxesAdminApp
? Angular app path public/javascripts
? Object name (recommended camelCase) node
? Object title (recommended PascalCase) Node
? Object API URL and directory name (recommended kebab-case) node
Generating angular-app application module
Generating angular-core-service module
Generating angular-component-list module
Generating angular-component-detail module
Generating model for mongoose and api endpoints
events.js:141
      throw er; // Unhandled 'error' event
      ^

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:8:11)
    at Object.posix.join (path.js:479:5)
    at Base.destinationPath (/home/osboxes/.nvm/versions/node/v4.7.0/lib/node_modules/generator-makrina/node_modules/yeoman-generator/lib/base.js:752:28)
    at /home/osboxes/.nvm/versions/node/v4.7.0/lib/node_modules/generator-makrina/generators/angular-app/index.js:50:15
    at Array.forEach (native)
    at module.exports.yeoman.Base.extend.writing (/home/osboxes/.nvm/versions/node/v4.7.0/lib/node_modules/generator-makrina/generators/angular-app/index.js:47:19)
    at Object.<anonymous> (/home/osboxes/.nvm/versions/node/v4.7.0/lib/node_modules/generator-makrina/node_modules/yeoman-generator/lib/base.js:439:23)
    at /home/osboxes/.nvm/versions/node/v4.7.0/lib/node_modules/generator-makrina/node_modules/run-async/index.js:25:25
    at /home/osboxes/.nvm/versions/node/v4.7.0/lib/node_modules/generator-makrina/node_modules/run-async/index.js:24:19
    at /home/osboxes/.nvm/versions/node/v4.7.0/lib/node_modules/generator-makrina/node_modules/yeoman-generator/lib/base.js:440:9

Ubuntu with node v7.3.0
? Project name osboxes
? Verbose name Osboxes
? Description Osboxes
? Git repository URL
? Author
? Organization
? Organization URL
? Deploy host
? New Relic license key
? Angular app short name admin
? Angular app name osboxesAdminApp
? Angular app path public/javascripts
? Object name (recommended camelCase) node
? Object title (recommended PascalCase) Node
? Object API URL and directory name (recommended kebab-case) node
Generating angular-app application module
Generating angular-core-service module
Generating angular-component-list module
Generating angular-component-detail module
Generating model for mongoose and api endpoints

events.js:160
      throw er; // Unhandled 'error' event
      ^

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.join (path.js:1211:7)
    at child.Base.destinationPath (/home/osboxes/.nvm/versions/node/v7.3.0/lib/node_modules/generator-makrina/node_modules/yeoman-generator/lib/base.js:752:28)
    at /home/osboxes/.nvm/versions/node/v7.3.0/lib/node_modules/generator-makrina/generators/angular-app/index.js:50:15
    at Array.forEach (native)
    at child.writing (/home/osboxes/.nvm/versions/node/v7.3.0/lib/node_modules/generator-makrina/generators/angular-app/index.js:47:19)
    at Object.<anonymous> (/home/osboxes/.nvm/versions/node/v7.3.0/lib/node_modules/generator-makrina/node_modules/yeoman-generator/lib/base.js:439:23)
    at /home/osboxes/.nvm/versions/node/v7.3.0/lib/node_modules/generator-makrina/node_modules/run-async/index.js:25:25
    at /home/osboxes/.nvm/versions/node/v7.3.0/lib/node_modules/generator-makrina/node_modules/run-async/index.js:24:19
    at /home/osboxes/.nvm/versions/node/v7.3.0/lib/node_modules/generator-makrina/node_modules/yeoman-generator/lib/base.js:440:9

Hi and thanks a lot for the time taken to write this issue.
This is indeed a bug with the generator. A fix will be released in the next hour.
More specifically, it has to do with the new parameter angularAppPath that was introduced in the sub-generators with the latest 0.5.1 release, issue #26 .
The main generator failed to provide a default angularAppPath to the sub-generators.

Published v0.5.2, it should fix this.


px-dropdown-content is not being displayed relative to the dropdown

Expected behavior and actual behavior:
Expected:
When I click on the px-dropdown I should be able to see the dropdown list in the px-dropdown-content just under or above the dropdown(i.e relative to the px-dropdown).
Actual:
When I click on the px-dropdown I am not able to see the dropdown list in the px-dropdown-content just under or above it. The dropdown-content is displayed at a fixed position irrespective if the position of the px-dropdown.
sometimes it is not even visible on the page as it is being displayed out of the page bounds.
Steps to reproduce the problem:
Include the latest px-dropdown with some other form objects like input boxes and dropdowns.
Use predix-layout-design to wrap and arrange the input items.
Environment (component version number, Browser (including version), operating system, hardware, etc):
component version: 2.4.4
Chrome: 53.0.2785.143
OS: OS X El captain

Fixed in v2.4.5, sorry for the mixup.

@randyaskin Thanks for the quick fix.


Front-end: Sort data

Description:
A way to select the columns being displayed.
User story:
As a teacher, I want to select the information to be displayed so I can see what is important to me at the time.
Phase 1:

[ ] I see a list of selectable columns groups.
[ ] I see a list of selectable columns.
[ ] I can select a column group to hide or show.
[ ] I can select a column to hide or show.

Design:
https://projects.invisionapp.com/share/RW2MNTCVK#/screens/71720400?maintainScrollPosition=true

Updates under "Demographics":

"ELL" == LEP"
"FLRP" -> "FRPL"

Include new assessment - STAR (Math & Reading):

PR = percentile rank
IRL = instructional reading level (Reading only)


Install ember cli mocha

Chose Ember-cli-mocha for our tests. Wrote an initial test which makes sure the component renders.

I'm fine with mocha :+1:


Error loading the CMS configuration

Describe the bug
Error when loading the admin page.  Error states it cannot find the collections in my config.yml but it is there.  See screenshot for full error.
To Reproduce

Go to 'www.codenexus.xyz/admin' or 'practical-brown-7a0ff6/admin'

Expected behavior
netlify-cms should load
Screenshots

Applicable Versions:

Netlify CMS version: 2.0.9
Git provider: GitHub
OS: Windows 10
Browser version Chrome Version 68.0.3440.106 (Though it happens in all browsers)

CMS configuration
backend:
  name: git-gateway
media_folder: "images/uploads"
collections:
  - name: "posts"
    label: "Posts"
    folder: "source/_posts"
    create: "true"
    slug: "{{slug}}"
    fields:
      -  {label: "Extends", name: "extends", widget: "hidden", default: "_layouts.post"}
      -  {label: "Title", name: "title", widget: "string"}
      -  {label: "Author", name: "author", wiget: "hidden"}
      -  {label: "Date", name: "date", widget: "datetime"}
      -  {label: "Content", name: "section", widget: "hidden", default: "content"}
      -  {label: "Body", name: "body", widget: "markdown"}

Additional context
Application is using jigsaw as it's static site generator.

Check your deployed config here: http://codenexus.xyz/admin/config.yml
That's all the CMS can see, you'll need to troubleshoot why your deployed config is not the same as your source config. Second file somewhere that's the real source? Builds failing?

That was it.  The build_production directory didn't have the latest config.yml as the build was failing on netlify.  I checked the deploy logs and dependencies were failing due to usage of php 5.6 instead of 7.2.


navbar resources dropdown menu showing same link for the list item 2 & 3

bootstrap icons should redirect to this link: https://icons.getbootstrap.com/

Fixed, thanks for reporting


[GLUTEN-1632][CH]Daily Update Clickhouse Version (20241130)

Auto commit by gluten daily build, please check the build status and merge it if it's green.

It may be safer to  let max_bytes_ratio_before_external_group_by be 0.0. We cannot let the spill happen inside  Aggregator,  it is conflict with GraceAggregation

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_master_11_30_2024_time.csv
log/native_master_11_08_2024_76b375d998_time.csv
difference
percentage

q1
52.01
51.32
-0.698
98.66%

q2
40.19
29.71
-10.487
73.91%

q3
80.27
53.28
-26.993
66.37%

q4
63.48
42.41
-21.065
66.81%

q5
155.99
105.13
-50.860
67.39%

q6
21.77
12.86
-8.918
59.04%

q7
179.17
111.85
-67.324
62.42%

q8
160.44
115.95
-44.492
72.27%

q9
252.82
173.29
-79.529
68.54%

q10
89.42
68.23
-21.184
76.31%

q11
37.31
26.70
-10.606
71.57%

q12
41.78
31.57
-10.206
75.57%

q13
77.88
50.61
-27.268
64.99%

q14
36.42
25.08
-11.335
68.87%

q15
59.98
51.04
-8.949
85.08%

q16
21.54
17.80
-3.739
82.64%

q17
224.11
126.93
-97.173
56.64%

q18
343.58
196.89
-146.688
57.31%

q19
34.62
28.08
-6.539
81.11%

q20
58.45
39.86
-18.592
68.19%

q21
1456.39
340.05
-1116.342
23.35%

q22
32.51
16.01
-16.496
49.25%

total
3520.12
1714.64
-1805.483
48.71%


Create py.typed

Allow for automatic typehints and mypy support

More info here: https://peps.python.org/pep-0561/

Thanks!


Published OSBA Docker Image Incompatible with Cloud Foundry

We can currently run OSBA on CF using the go build pack, but that requires the user to clone the repository. CF supports running applications as containers as well, but Cloud Foundry has a requirement of Docker images that we don't currently meet.

The Docker image must contain an /etc/passwd file with an entry for the root user. In addition, the home directory and the shell for that root user must be present in the image filesystem.

Should we modify our Dockerfile to include the shell and /etc/passwd?

It is common for CF users to clone the repo then push the app. For PCF users, they usually install app by a tile. We can build a tile to release in Pivotal Network after resolving https://github.com/Azure/open-service-broker-azure/issues/129.
So I think there is no strong requirement to make the image work for CF. Still, it is nice to make it work.

Yeah, I thought this was a nice to have. I have a blog post ready to go on using it with pcf dev and thought I'd try to deploy with docker and noticed this one.
We are planning on resolving 129 (we'll support both env variables), so that will be good to get a new tile.

@jeremyrickard it sounds like conforming would require us to stop being FROM scratch. Is that right?
That's something I'd rather avoid, if possible, because my feeling is that distributions bring a whole lot of new attack vectors along with them. For instance-- right now it's (nearly?) impossible to even exec into a running OSBA container. I'm not keen to undo that.

You don't need any distribution. Just shell, which starts app commands. I've made my own Golang shell implementation (simplified https://github.com/tianon/gosu with -c flag implementation), which is compiled as a static binary /bin/sh and CF is happy with that.

@jangaraj including a shell still brings along new attack vectors. As I mentioned, you currently cannot exec into a running OSBA container and I regard that as a feature, tbh.

Any idea how can you exploit it with this fake shell?

This looks pretty safe to me. I don't think I'd understood how narrow in scope the shell in question was.
I think we could consider this.


remove the piaware username/password prompt

We're slowly trying to get away from putting FA username/password on the piaware client side.
It's still there as a legacy thing but it is a bit of a security hole and we'd rather not have people configure it.
Can you remove the prompt for a FA username/password from the setup scripts?

(somewhat related, as of 3.3 you can get a URL from /run/piaware/status.json "site_url", which will point to the user's stats page, so you don't need to know the username ahead of time)

Sure, I will try to take a look at this over the weekend and thank for highlighting the site_url value :)

So I reviewed the install code and it's a fairly minimal change so I should be able to do it later this week, although it would be in my 2.6.0 branch which due to the volume of changes may not make it into Joe's release.
I agree that moving away from having credentials stored locally seems wise, but suspect there may still be some use cases such as being configured for deployment at remote location...
So I just wanted to check if you would see my issues with retaining the option to configure the username/password, but with the default option being to skip and the text updated to highlight that this is not recommended due to security considerations etc? :)

I'd like the default to not even mention it ideally.
You can still configure it if needed via piaware-config.

Part of the ethos of this project is to assist users in configuring multiple feeders so would rather avoid having to suggest using other tools to be able to have a comparable install to what the scripts do today...
Does the 'Claim My Pi' function allow users to track down their receiver without say knowing the IP/MAC address, or is there any other means to identify it remotely if the user is not given the option to configure the user/pass during the initial setup?

The only case you ever need to set a username/password is an install where you cannot reach the FA website from the same IP address as the feeder. That case will, itself, go away in the future. It is not a common case.
If you put a prompt in for username/password (even if it's surrounded by warnings) in the default flow, users will fill that in when it's not needed, which is a security problem that I really don't need.
If you are going to retain the ability to configure the username/password then please put it somewhere that is not in the default install flow.

Thanks for the update and just to confirm that I understand correctly there is presently a requirement for the user to be able to access the FlightAware website from the same public IP as the receiver is sending its data in order for it to be available to be 'claimed' by the user, but this may be addressed in future?

The automated claim process requires that you visit the claim webpage from the same external IP as the Pi is connecting from. Once you've done that once and the receiver is claimed, there's no further requirement.

Thanks for confirming and as it seems the 'claim my pi' functionality should work in most, but not all, use cases I have proposed the following wording in my changes against the 2.6.0 branch:

whiptail --backtitle "${RECEIVER_PROJECT_TITLE}" --title "Claim Your PiAware Device" --yesno
Although it is possible to configure your FlightAware credentials locally, these will be stored in plaintext which represents a security risk that should be avoided.
FlightAware recommends claiming your feeder online using the following page:
http://flightaware.com/adsb/piaware/claim
Will you be able to access the FlightAware website from the same public IP address as the feeder will be sending data from?

If the user answers Yes then the next dialog confirms they will need to claim their pi and repeats the address, whereas answering No leads to the existing username/password configuration dialog.
So although not what was requested, does this seem like a reasonable interim step to decrease the number of users who have credentials stored locally while retaining the ability to do so for the corner cases where the requirement to access the  webpage from the same public IP?

Sure, that is an improvement over the status quo.

Sorry for the delay getting on this request but I see no problem removing this step and displaying instructions on how to claim their receiver using the website. I have this as next on my "machine gun catch up list" and should have it merged into the master branch within the next day.

Actually an easy fix just moved the contents of an else statement outside the if. Users should now be instructed to visit https://flightaware.com/adsb/piaware/claim to claim their device.
Commit: ceed37718299bae4e126f2b8e0c8269887574672


Failed to start xrdp.service: Unit xrdp.service is masked.

Hello,
I have compiled and installed xrdp server 0.9.3 on Ubuntu 17.04. Desktop: Gnome 3.
I cannot start it because of the next error:
$ sudo service xrdp start
Failed to start xrdp.service: Unit xrdp.service is masked.

What am I doing wrong?
Regards

I'm not a systemd expert, but in the past it has been sufficient for me to say
systemctl unmask xrdp
and then start the service.

On Aug 10, 2017, at 4:08 AM, Alexandr Porunov<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hello,
I have compiled and installed xrdp server 0.9.3 on Ubuntu 17.04. Desktop: Gnome 3.
I cannot start it because of the next error:
$ sudo service xrdp start
Failed to start xrdp.service: Unit xrdp.service is masked.
What am I doing wrong?
Regards
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/neutrinolabs/xrdp/issues/846, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFFe7BqN9WmUAWN6B3OOuynXzEkC_JRks5sWta2gaJpZM4OzN2u.
https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png https://github.com/neutrinolabs/xrdp https://github.com/neutrinolabs/xrdp/issues/846

Thank you. Solved the problem by removing old xrdp.service

hey! I started kali linux on AWS later on CMD i tried to connect to rdp for kali and   I  am getting  this error !!
root@kali:/home/ec2-user# systemctl start xrdp
Failed to start xrdp.service: Unit xrdp.service not found.

@Lucifer-00007 - Just for the record, there is an extra step from the norm that needs to be completed after compilation, and that is the installation of files for the system service. It goes a little something like this.
cd instfiles
sudo make install
# then (for debian & Kali & Ubuntu & mint)
sudo systemctl unmask xrdp.service xrdp-sesman.service \
  && sudo systemctl enable xrdp.service xrdp-sesman.service \
    && sudo systemctl start xrdp.service xrdp-sesman.service

Then it should run, but I am getting a failure due to xrdp-sesman.service

@Lucifer-00007 Samething for me. Appears that setting exe prefix has no affect.