Export AnnData error

Hi,
I've been processing my IMC data through steinbock without issue, but have come across one file/ROI which I continue to get the below error for when trying to create AnnData object:
C:\Users\mb2925\IMC\AIN\DriveDuplicate\Batch7>steinbock export anndata --no-concat --intensities intensities --data regionprops --neighbors neighbors -o anndata
2024-01-10 17:55:52,766 INFO steinbock - anndata/Batch7a_001.h5ad
2024-01-10 17:55:53,138 INFO steinbock - anndata/Batch7a_002.h5ad
2024-01-10 17:55:53,479 INFO steinbock - anndata/Batch7a_003.h5ad
2024-01-10 17:55:53,843 INFO steinbock - anndata/Batch7a_004.h5ad
2024-01-10 17:55:54,233 INFO steinbock - anndata/Batch7a_005.h5ad
2024-01-10 17:55:54,527 ERROR steinbock.export.data - Error creating AnnData object for image Batch7a_006.tiff; skipping image
Traceback (most recent call last):
File "/app/steinbock/steinbock/export/data.py", line 123, in try_convert_to_anndata_from_disk
yield (
GeneratorExit
Exception ignored in: <generator object try_convert_to_anndata_from_disk at 0x7fcd75ae4ba0>
Traceback (most recent call last):
File "/app/steinbock/steinbock/export/_cli/data.py", line 273, in anndata_cmd
anndata_file = write_anndata(adata, anndata_file)
RuntimeError: generator ignored GeneratorExit
Traceback (most recent call last):
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/utils.py", line 214, in func_wrapper
return func(elem, key, val, *args, **kwargs)
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/specs/registry.py", line 171, in write_elem
_REGISTRY.get_writer(dest_type, (t, elem.dtype.kind), modifiers)(
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/specs/registry.py", line 24, in wrapper
result = func(g, k, *args, **kwargs)
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/specs/methods.py", line 346, in write_vlen_string_array
f.create_dataset(k, data=elem.astype(str_dtype), dtype=str_dtype, **dataset_kwargs)
File "/opt/venv/lib/python3.8/site-packages/h5py/_hl/group.py", line 149, in create_dataset
dsid = dataset.make_new_dset(group, shape, dtype, data, name, **kwds)
File "/opt/venv/lib/python3.8/site-packages/h5py/_hl/dataset.py", line 145, in make_new_dset
dset_id.write(h5s.ALL, h5s.ALL, data)
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "h5py/h5d.pyx", line 232, in h5py.h5d.DatasetID.write
File "h5py/_proxy.pyx", line 145, in h5py._proxy.dset_rw
File "h5py/_conv.pyx", line 444, in h5py._conv.str2vlen
File "h5py/_conv.pyx", line 95, in h5py._conv.generic_converter
File "h5py/_conv.pyx", line 249, in h5py._conv.conv_str2vlen
TypeError: Can't implicitly convert non-string objects to strings
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/app/steinbock/steinbock/main.py", line 17, in
steinbock_cmd_group(prog_name="steinbock")
File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1130, in call
return self.main(*args, **kwargs)
File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1055, in main
rv = self.invoke(ctx)
File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1657, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1657, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/opt/venv/lib/python3.8/site-packages/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "/app/steinbock/steinbock/_cli/utils.py", line 35, in wrapper
return func(*args, **kwargs)
File "/app/steinbock/steinbock/export/_cli/data.py", line 273, in anndata_cmd
anndata_file = write_anndata(adata, anndata_file)
File "/app/steinbock/steinbock/export/_cli/data.py", line 203, in write_anndata
adata.write_h5ad(anndata_file)
File "/opt/venv/lib/python3.8/site-packages/anndata/_core/anndata.py", line 1918, in write_h5ad
_write_h5ad(
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/h5ad.py", line 98, in write_h5ad
write_elem(f, "obs", adata.obs, dataset_kwargs=dataset_kwargs)
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/utils.py", line 214, in func_wrapper
return func(elem, key, val, *args, **kwargs)
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/specs/registry.py", line 175, in write_elem
_REGISTRY.get_writer(dest_type, t, modifiers)(f, k, elem, *args, **kwargs)
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/specs/registry.py", line 24, in wrapper
result = func(g, k, *args, **kwargs)
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/specs/methods.py", line 514, in write_dataframe
write_elem(group, colname, series._values, dataset_kwargs=dataset_kwargs)
File "/opt/venv/lib/python3.8/site-packages/anndata/_io/utils.py", line 220, in func_wrapper
raise type(e)(
TypeError: Can't implicitly convert non-string objects to strings
Above error raised while writing key 'image_recovery_file' of <class 'h5py._hl.group.Group'> to /
All steps before this ran smoothly, the folder structures/file names match, and there was no issue with this run or that particular ROI.  I have attached this one file in case needed.  Not sure what to do -- I did try starting over and got the same error messages.
I attached a zip file with the img file and anndata file for this region, had to exclude a lot of the other data for this region due to the size limits for upload.  Let me know what you think, and if you need any other file outputs to see what might be going on.
Batch7 (4).zip

Hi @megleila
Thanks for reaching out. I am afraid I cannot reproduce the error with the provided files and the output seems fine. How do you use steinbock (python package vs container, version, flavor...)?

I use Docker, a container.  I’ve had no issues with all my other files — everything else works.  Strange that you got no error; I’ve re-done this multiple times. Not sure what to do.

On Jan 17, 2024, at 11:49 AM, Milad4849 @.***> wrote:
Hi @megleila https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmegleila&data=05|02|megan.baker%40yale.edu|a005f0ff481c445d309208dc177c508a|dd8cbebb21394df8b4114e3e87abeb5c|0|0|638411069896968754|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2FiqNK6GqkABYNaRVd2roIxfa8szjzprNcizYMz2i8oI%3D&reserved=0
Thanks for reaching out. I am afraid I cannot reproduce the error with the provided files and the output seems fine. How do you use steinbock (python package vs container, version, flavor...)?
—
Reply to this email directly, view it on GitHub https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBodenmillerGroup%2Fsteinbock%2Fissues%2F235%23issuecomment-1896205427&data=05|02|megan.baker%40yale.edu|a005f0ff481c445d309208dc177c508a|dd8cbebb21394df8b4114e3e87abeb5c|0|0|638411069896978384|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=UkrFBDKpbEn4Kd7pQQYX0WdafCovghMCwiE7fJTWsRg%3D&reserved=0, or unsubscribe https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FBAH2R6LZENGAHPGOECMDKQ3YO76KVAVCNFSM6AAAAABBVE7ZIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJWGIYDKNBSG4&data=05|02|megan.baker%40yale.edu|a005f0ff481c445d309208dc177c508a|dd8cbebb21394df8b4114e3e87abeb5c|0|0|638411069896986558|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=mz1NsZ3TUfuxZNgtsgC6Vh%2FzCsH7BDLh8MjMSZhxJZs%3D&reserved=0.
You are receiving this because you were mentioned.

Closing due to inactivity


az resource move generate invalid json when passing multiple resources resources

Describe the bug
When using az resource move I'm getting an error
The json generated is invalid, the string is not splited on spaces

Related command

az resource move --destination-group staging-mc-hub-storage-rg \
    --destination-subscription-id 04bf988d-ee80-4bb3-be58-4b24a576aa51 \
    --ids '/subscriptions/5955fbbf-b804-4315-a74e-4b9eff6fc762/resourceGroups/some-rg/providers/Microsoft.Storage/storageAccounts/resource1 /subscriptions/5955fbbf-b804-4315-a74e-4b9eff6fc762/resourceGroups/some-rg/providers/Microsoft.Storage/storageAccounts/resource2 /subscriptions/5955fbbf-b804-4315-a74e-4b9eff6fc762/resourceGroups/some-rg/providers/Microsoft.Storage/storageAccounts/resource3 /subscriptions/5955fbbf-b804-4315-a74e-4b9eff6fc762/resourceGroups/some-rg/providers/Microsoft.Storage/storageAccounts/resource4 /subscriptions/5955fbbf-b804-4315-a74e-4b9eff6fc762/resourceGroups/some-rg/providers/Microsoft.Storage/storageAccounts/resource5 /subscriptions/5955fbbf-b804-4315-a74e-4b9eff6fc762/resourceGroups/some-rg/providers/Microsoft.Storage/storageAccounts/resource6' \
    --debug

Errors
{"error":{"code":"TooManyExtensionProviders","message":"The number of extension providers in the request URI exceeds limit. ARM supports up to 3 extension providers."}}
Issue script & Debug output
cli.knack.cli: Command arguments: ['resource', 'move', '--destination-group', 'staging-mc-hub-storage-rg', '--destination-subscription-id', '04bf988d-ee80-4bb3-be58-4b24a576aa51', '--ids', '/subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource1 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource2 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource3 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource4 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource5 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/
[]...]
msal.telemetry: Generate or reuse correlation_id: 61e4db65-ab94-45d4-ad58-eb299b5497a3
cli.azure.cli.core.sdk.policies: Request URL: 'https://management.azure.com/subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/moveResources?api-version=2022-09-01'
cli.azure.cli.core.sdk.policies: Request method: 'POST'
cli.azure.cli.core.sdk.policies: Request headers:
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json'
cli.azure.cli.core.sdk.policies:     'Content-Length': '1058'
cli.azure.cli.core.sdk.policies:     'Accept': 'application/json'
cli.azure.cli.core.sdk.policies:     'x-ms-client-request-id': '51cd6c49-06d1-11ee-a1db-a598e71c1dd2'
cli.azure.cli.core.sdk.policies:     'CommandName': 'resource move'
cli.azure.cli.core.sdk.policies:     'ParameterSetName': '--destination-group --destination-subscription-id --ids --debug'
cli.azure.cli.core.sdk.policies:     'User-Agent': 'AZURECLI/2.48.1 (DEB) azsdk-python-azure-mgmt-resource/22.0.0 Python/3.10.10 (Linux-5.19.0-40-generic-x86_64-with-glibc2.35)'
cli.azure.cli.core.sdk.policies:     'Authorization': '*****'
cli.azure.cli.core.sdk.policies: Request body:
cli.azure.cli.core.sdk.policies: {"resources": ["/subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource1 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource2 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource3 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource4 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource5 /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/providers/Microsoft.Storage/storageAccounts/resource6"], "targetResourceGroup": "/subscriptions/04bf988d-ee80-4bb3-be58-4b24a576aa51/resourceGroups/staging-mc-hub-storage-rg"}
urllib3.connectionpool: Starting new HTTPS connection (1): management.azure.com:443
urllib3.connectionpool: https://management.azure.com:443 "POST /subscriptions/0c6f1acd-31ba-4e86-beca-e264f808ec30/resourceGroups/staging-mc-hub-db-rg/moveResources?api-version=2022-09-01 HTTP/1.1" 400 168
cli.azure.cli.core.sdk.policies: Response status: 400
cli.azure.cli.core.sdk.policies: Response headers:
cli.azure.cli.core.sdk.policies:     'Cache-Control': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Pragma': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json; charset=utf-8'
cli.azure.cli.core.sdk.policies:     'Expires': '-1'
cli.azure.cli.core.sdk.policies:     'x-ms-failure-cause': 'gateway'
cli.azure.cli.core.sdk.policies:     'x-ms-ratelimit-remaining-subscription-writes': '1199'
cli.azure.cli.core.sdk.policies:     'x-ms-request-id': 'e8780fb8-f319-410c-811e-735350b1c66a'
cli.azure.cli.core.sdk.policies:     'x-ms-correlation-request-id': 'e8780fb8-f319-410c-811e-735350b1c66a'
cli.azure.cli.core.sdk.policies:     'x-ms-routing-request-id': 'CANADAEAST:20230609T142419Z:e8780fb8-f319-410c-811e-735350b1c66a'
cli.azure.cli.core.sdk.policies:     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
cli.azure.cli.core.sdk.policies:     'X-Content-Type-Options': 'nosniff'
cli.azure.cli.core.sdk.policies:     'Date': 'Fri, 09 Jun 2023 14:24:18 GMT'
cli.azure.cli.core.sdk.policies:     'Content-Length': '168'
cli.azure.cli.core.sdk.policies: Response content:
cli.azure.cli.core.sdk.policies: {"error":{"code":"TooManyExtensionProviders","message":"The number of extension providers in the request URI exceeds limit. ARM supports up to 3 extension providers."}}
cli.azure.cli.core.azclierror: Traceback (most recent call last):
  File "/opt/az/lib/python3.10/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/command_modules/resource/custom.py", line 2233, in move_resource
    return rcf.resources.begin_move_resources(resources[0]['resource_group'], parameters=resources_move_info)
  File "/opt/az/lib/python3.10/site-packages/azure/core/tracing/decorator.py", line 78, in wrapper_use_tracer
    return func(*args, **kwargs)
  File "/opt/az/lib/python3.10/site-packages/azure/mgmt/resource/resources/v2022_09_01/operations/_operations.py", line 9391, in begin_move_resources
    raw_result = self._move_resources_initial(  # type: ignore
  File "/opt/az/lib/python3.10/site-packages/azure/mgmt/resource/resources/v2022_09_01/operations/_operations.py", line 9271, in _move_resources_initial
    raise HttpResponseError(response=response, error_format=ARMErrorFormat)
azure.core.exceptions.HttpResponseError: (TooManyExtensionProviders) The number of extension providers in the request URI exceeds limit. ARM supports up to 3 extension providers.
Code: TooManyExtensionProviders
Message: The number of extension providers in the request URI exceeds limit. ARM supports up to 3 extension providers.

cli.azure.cli.core.azclierror: (TooManyExtensionProviders) The number of extension providers in the request URI exceeds limit. ARM supports up to 3 extension providers.
Code: TooManyExtensionProviders
Message: The number of extension providers in the request URI exceeds limit. ARM supports up to 3 extension providers.
az_command_data_logger: (TooManyExtensionProviders) The number of extension providers in the request URI exceeds limit. ARM supports up to 3 extension providers.

Expected behavior
It should work according to the documentation
https://learn.microsoft.com/en-us/cli/azure/resource?view=azure-cli-latest#az-resource-move

Environment Summary
{
"azure-cli": "2.48.1",
"azure-cli-core": "2.48.1",
"azure-cli-telemetry": "1.0.8",
"extensions": {
"aks-preview": "0.5.137",
"azure-devops": "0.26.0",
"ssh": "1.1.6"
}
}
Additional context
No response

Thank you for opening this issue, we will look into it.

@Socolin Please use --ids 'id1' 'id2' 'id3' instead of --ids 'id1 id2 id3', because the whole of  'id1 id2 id3' will be considered as an id

/unresolve
Ok thanks, then the documentation need to be updated because this is misleading.

@zhoxing-ms why did you close this, I thjink the documentation is misleading and should be fixed before.

/unresolve
@zhoxing-ms
I just tested it, and it only moved the last resources specified in --ids so it does not seems to work, it only take 1, so there is a problem in the code

@Socolin Sorry, I thought this issue had been resolved, so I closed the issue first, we will add the additional examples later.
If this issue has not been resolved yet, could you please send me the debug log (add --debug parameter)  using the method I recommend by email? My email is<EMAIL_ADDRESS>thank you

@Socolin Sorry, I thought this issue had been resolved, so I closed the issue first, we will add the additional examples later. If this issue has not been resolved yet, could you please send me the debug log (add --debug parameter) using the method I recommend by email? My email is<EMAIL_ADDRESS>thank you

I sent you the logs with --debug

@Socolin I replied to your email, please take a look

So for anyone having this issue, the cli is expecting the following args[]
'--ids', 'id1' 'id2'

@Socolin I have submitted a PR #26756 to add a sample for this case, which will be automatically updated into our document after the next new version of CLI is released.

Thanks !


Recommended abbreviation for NAT gateway

There is no recommended abbreviation for NAT gateways (Microsoft.Network/natGateways)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8c22eb33-2fde-55b4-021d-e229c857e51b
Version Independent ID: 1f767675-7d50-6ea5-b798-1323cd4a63a1
Content: Recommended abbreviations for Azure resource types - Cloud Adoption Framework
Content Source: docs/ready/azure-best-practices/resource-abbreviations.md
Service: cloud-adoption-framework
Sub-service: ready
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 431711

Thanks for your feedback. We are in the process of reviewing and updating this article.


feat: port Combinatorics.SimpleGraph.Matching

only one thing not working in IsMatching.even_card: curious what is going on:
I make a have: (fun v  => (SimpleGraph.degree (Subgraph.coe M) v)) = (fun v => 1) , and I though this is exactly contained in the current goal, but neither rw nor simp is making the substitution...

What seems to be missing is some sort of statement like:
∀ (v : M.verts), @SimpleGraph.degree (↑M.verts) (Subgraph.coe M) v (coeFiniteAt v)  =
        @SimpleGraph.degree (↑M.verts) (Subgraph.coe M) v (neighborSetFintype (Subgraph.coe M) v)

but coe_degree can't provide that.

https://leanprover.zulipchat.com/#narrow/stream/287929-mathlib4/topic/coe_degree.20for.20simple.20graphs

bors r+


[Swup] For Swup's dev dependencies exclusion from our yarn.lock

Q
A

Bug fix?
yes/no

New feature?
yes/no

Issues
Fix #...

License
MIT

While working on #2219, I've noticed we had a very old Rollup version that we do not use at all.
The issue comes from Swup v3, which ship its building dependencies as prod dependencies, which means we install microbundle and all its dependencies:
<EMAIL_ADDRESS>  version "0.15.1"
  resolved "https://registry.npmjs.org/microbundle/-/microbundle-0.15.1.tgz"
  integrity sha512-aAF+nwFbkSIJGfrJk+HyzmJOq3KFaimH6OIFBU6J2DPjQeg1jXIYlIyEv81Gyisb9moUkudn+wj7zLNYMOv75Q==
  dependencies:
    "@babel/core" "^7.12.10"
    "@babel/plugin-proposal-class-properties" "7.12.1"
    "@babel/plugin-syntax-import-meta" "^7.10.4"
    "@babel/plugin-syntax-jsx" "^7.12.1"
    "@babel/plugin-transform-flow-strip-types" "^7.12.10"
    "@babel/plugin-transform-react-jsx" "^7.12.11"
    "@babel/plugin-transform-regenerator" "^7.12.1"
    "@babel/preset-env" "^7.12.11"
    "@babel/preset-flow" "^7.12.1"
    "@babel/preset-react" "^7.12.10"
    "@rollup/plugin-alias" "^3.1.1"
    "@rollup/plugin-babel" "^5.2.2"
    "@rollup/plugin-commonjs" "^17.0.0"
    "@rollup/plugin-json" "^4.1.0"
    "@rollup/plugin-node-resolve" "^11.0.1"
    "@surma/rollup-plugin-off-main-thread" "^2.2.2"
    asyncro "^3.0.0"
    autoprefixer "^10.1.0"
    babel-plugin-macros "^3.0.1"
    babel-plugin-transform-async-to-promises "^0.8.18"
    babel-plugin-transform-replace-expressions "^0.2.0"
    brotli-size "^4.0.0"
    builtin-modules "^3.1.0"
    camelcase "^6.2.0"
    escape-string-regexp "^4.0.0"
    filesize "^6.1.0"
    gzip-size "^6.0.0"
    kleur "^4.1.3"
    lodash.merge "^4.6.2"
    postcss "^8.2.1"
    pretty-bytes "^5.4.1"
    rollup "^2.35.1"
    rollup-plugin-bundle-size "^1.0.3"
    rollup-plugin-postcss "^4.0.0"
    rollup-plugin-terser "^7.0.2"
    rollup-plugin-typescript2 "^0.32.0"
    rollup-plugin-visualizer "^5.6.0"
    sade "^1.7.4"
    terser "^5.7.0"
    tiny-glob "^0.2.8"
    tslib "^2.0.3"
    typescript "^4.1.3"

This PR won't impact developers, it's only for our yarn.lock which contains a bunch of useless dependencies, and some of them are vulnerable too (listed on https://github.com/symfony/ux/security/dependabot)

Thanks a lot @Kocal 😃


Animations

:+1:
Only thing is we don't have bevy animation exporting, as I don't know how to grab relevant AnimationClips.
We may need to add an export parameter for manual declaration of any animations you wish to export.

Actually... might be able to grab all clips and check if their EntityPath matches a node in the scene. Will investigate.


winmerge : autoupdate issues

winmerge: 2.16.24 (scoop version is 2.16.16) autoupdate available
https://github.com/brave-simpletons/scoop-the-business/actions/runs/3833011235/jobs/6523989191#step:3:430
The manifest may need to be updated

Since to be fine now...


License Update to BSD-Clause 3 + headers various updates

Here are source file headers updated . An exception is made with *.ino files

Just made the merging of current developpment version and made few updates. Waiting for your review :)


patching issue 2 return if there is one picture

Thanks, I will improve later.

No, thats the main problem of everything. After I've removed the return and called the same function for other ones, it worked well

oops, I have no time to check this PR. Just merged, If you have any updated about this to make it works. Please PR, Thanks.


Bug?

it's the best there is, but the problem is that the vehicle list always goes back up every time you press on a vehicle in the list

Issue was resolved.


Error during face recognition: Unsupported image type, must be 8bit gray or RGB image.

face_recognition version: 1.3.0
Python version: 3.12.4
Operating System: MacOS Sonoma Version 14.5 (23F79)

Description
I am trying to implement a face recognition login system using the face_recognition library in a Flask web application. The image is captured from a webcam using JavaScript, converted to a data URL, and sent to the server. However, I am consistently encountering the error Unsupported image type, must be 8bit gray or RGB image despite ensuring the image is in the correct format.
What went wrong:
•	The error occurs during the face_recognition.face_encodings function call.
•	Debugging indicates that the image is converted to RGB and is an 8-bit image, but the error persists.

Expected:
•	The function face_recognition.face_encodings should process the image and return face encodings if faces are detected.

What I Did
Traceback:
DEBUG: STREAM b'IHDR' 16 13
DEBUG: STREAM b'sRGB' 41 1
DEBUG: STREAM b'IDAT' 54 8192
DEBUG: Original image mode: RGBA
DEBUG: Converted image mode: RGB
DEBUG: Image shape: (480, 640, 3), dtype: uint8
ERROR: Error during face recognition: Unsupported image type, must be 8bit gray or RGB image.
INFO: <IP_ADDRESS> - - [27/Jun/2024 22:23:00] "POST /login HTTP/1.1" 200 -

version de reconnaissance faciale : 1.3.0
Version Python : 3.12.4
systeme d'exploitation :windows 10
j'essaie d'implementer un systeme de reconnaissaance faciale a l'aide de la bibliotheque face_recognition . Cependant, je rencontre systématiquement l'erreur Type d'image non pris en charge, doit être une image grise ou RVB 8 bits, même si je m'assure que l'image est au bon format.

Hello! I've run into this issue a lot of times, and what worked for me was downgrading to numpy 1.26.1. Numpy 2 seems to have changed some functionality which causes this issue. Once you've downgraded your numpy, make sure to change the line containing "rgb_small_frame" to be:
rgb_small_frame = np.ascontiguousarray(small_frame[:, :, ::-1])
instead.

Hello! I've run into this issue a lot of times, and what worked for me was downgrading to numpy 1.26.4. Numpy 2 seems to have changed some functionality which causes this issue. Once you've downgraded your numpy, it's working fine.


Add some missing LICENSE files to crates, and add CI to verify all crates have LICENSE files.

Fixes #3761 (again).
I'm not sure about adding LICENSE to all of these crates, but it seems that it
doesn't hurt exactly (all the code is covered under the license regardless,
as we have LICENSE at the root of the repo), and it is easier than trying to
distinguish based on publish = directives or whatnot.

Personally I do not want to organize the repository like this. I don't think it's useful to have this copied all over the place and even with CI checking it that just seems like it'll be more annoying than anything else.
IIRC Cargo does processing of a license-file directive and puts it into the root crate, so could that be investigated instead of copying the files around?

I tend to agree, but downstream packagers want this -- @decathorpe in #3761 needs LICENSE files in each crate (or at least the published ones) for packaging in Fedora (IIRC?).
@decathorpe, would it be acceptable instead to remove all LICENSE files except for the root one, and then update your packaging setup to refer to that?

If I understand correctly, "license-file" is only supposed to be used when using a non-standard license, i.e. the two fields in Cargo.toml are mutually exclusive:
https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields
Concerning inclusion of the license text in individual crates: Lawyers / people who understand licenses better than me explained it this way: Some software licenses (including Apache-2.0 and MIT, the de-facto standard licenses for Rust projects), include a requirement that redistributed sources MUST contain a copy of the actual license text (i.e. the LICENSE file).
So, since you are redistributing this project as individual crates on crates.io (and subsequently, Linux distributions might create and redistribute packages for those crates), they need to include license file(s) to be in compliance with the license that you yourselves have chosen for your project.
It also looks like you added copies of the LICENSE files in some places where they are actually not needed (for example, workspace directories that don't contain crates, or "internal" crates that are not published individually).
And, assuming that the operating system that "cargo publish" is run on for this project supports symbolic links, you don't actually need to include full copies of the file everywhere, but a symbolic link is sufficient for cargo to include it.

I understand that license and license-file are typically mutally exclusive. Your packaging use case does not appear to respect license = "..." in the manifest and requires that some file is present. We do not want to remove license = "..." for Rust-based tooling reasons. I'm proposing a compromise where, if you're willing to put in the work, license-file annotations are added which all point to the root LICENSE in the repository which I believe Cargo will then copy to the crate.

Your packaging use case does not appear to respect license = "..." in the manifest and requires that some file is present.

Our tooling for creating RPM packages does read the package.license value from Cargo.toml, and uses that value to populate the License field of packages.
But even if that were not the case, and the license string was determined by asking an oracle, the problem is the missing license text / file:
c.f. https://choosealicense.com/licenses/apache-2.0/ at 4. Redistribution, (a):

You must give any other recipients of the Work or Derivative Works a copy of this License

I don't see a distinction between redistribution via crates.io and redistribution by linux distributions here (other than the fact that in the first case, you're violating your own license terms, while in the second case, it usually prevents linux distributions from redistributing your code), so the problem is definitely not specific to Linux distribution packages.

@decathorpe understood that we need to include the license file, one way or another, in the tarball that is uploaded to crates.io. I think this is covered by what @alexcrichton was proposing:

I'm proposing a compromise where, if you're willing to put in the work, license-file annotations are added which all point to the root LICENSE in the repository which I believe Cargo will then copy to the crate.

I just checked locally with cargo package locally and in a crate with license and license-file attributes, with the latter pointing out-of-tree (to the parent directory), the following happens:

The package does include the license file; it is copied in by Cargo.
However, Cargo emits a warning:   Packaging a v0.0.1 (/Users/cfallin/t/a)
   Verifying a v0.0.1 (/Users/cfallin/t/a)
warning: only one of `license` or `license-file` is necessary
`license` should be used if the package license can be expressed with a standard SPDX expression.
`license-file` should be used if the package uses a non-standard license.
See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.

and as @alexcrichton notes, we cannot drop the license attribute for a bunch of reasons (tooling reads and depends on it).

@alexcrichton, do you know if there is a way to suppress this warning?

I don't know how to suppress that myself, and that sounds like an issue for upstream Cargo.

This looks like rust-lang/cargo#8537, which is closed with a "we won't support this" disposition -- see this comment in particular. Their reasoning is that adding both keys (license and license-file) could be ambiguous, and Cargo doesn't want the complexity, and tools on top of Cargo should be responsible for gathering license files for standard licenses.
(As an aside, I bet there are a whole bunch of crates on crates.io that have a standard SPDX license expression and don't include the file itself; @decathorpe have you looked at this much for other crates?)
The person who opened that Cargo issue cc'd tokio-rs/tracing#842 where the tracing crate had exactly the same discussion that we're having here, and concluded that they just needed to duplicate LICENSE into every crate.
So it seems that's kind of our only option to (i) satisfy legal requirements and (ii) work with Cargo. I'll pare this PR down to just adding LICENSE in the two new crates, and I'll either see if I can find a way to hack the CI license-is-present check into the publish.rs script for just published crates, or omit it for now.

@decathorpe I've modified this PR to add LICENSE files just to the six (!) crates we have added recently without LICENSE files, and to add a check to the publish.rs script that runs in our CI to verify publishability.
Unfortunately it looks like wasi-nn is missing a LICENSE file as well, and that's an upstream repo that would need a separate PR to fix and then a PR here to pull in a new submodule version. Would you be willing to do that legwork? If that's merged then CI here should pass and hopefully we can merge this.
@alexcrichton thoughts on this new CI check?

Looks good to me, thank you.

Sorry, I missed that one.
I can try, but I'm not really interested in wasi-nn as it's dependencies don't look like they'd be available to be.
More important is wasi-common, which also has a problem like this, and it's been ignored for a while: https://github.com/bytecodealliance/wasmtime/issues/3912

I'm cleaning up old PRs and am going to go ahead and close this for now; this has become out-of-date anyway (new crates in the meantime). @decathorpe please feel free to recreate a new version of the PR as you see fit.


Update topics/preinstalled-software-on-teamcity-cloud-ubuntu-agents.md

PR created by http://unit-1592.labs.intellij.net:8111/buildConfiguration/TestProject_UpdateSoftwareInfoViaPr/3490

Closing this PR as obsolete, there is a more recent one


What is the Alpha Grid?

I couldn't find any info about it. What does it do / What is it's purpose? Also noticed that is available to players too.

Yeah, I think I should do something to increase feature discoverability.
Here is the demo: https://youtu.be/m_cWFK2YCGk
If you have more questions feel free to ask them here (even in closed issue) or reach me in Discord: Averrin#0374


Add an Operations API for Commitment Plan RP

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

 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.:x: weedqian sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Can one of the admins verify this patch?

Looks good.


Add PIL image checker to _probe_duration func

Although commit 61a0eb4 from #13 solves the condition if the -shortest flag is provided, it does not handle images as input. Images will, in most cases, have extremely short durations, so adding this function will make it so only the duration of the shortest of the non-image files will be used. The changes in indentation are most likely automatic changes from my IDE, but should not affect the functionality.

Oh, I see this requires another dependency. Maybe the image2 check would be the easier option that does not add package requirements?

I have tried variations of the following that doesn't particularly work:
def is_image(file_name):
    try:
        command = ['ffmpeg', '-v', 'error', '-i', file_name, '-f', 'null', '-']
        output = subprocess.check_output(command, stderr=subprocess.STDOUT).decode().lower()
        return 'image2' in output  # No error, considered as an image
    except subprocess.CalledProcessError:
        return False  # Error occurred, not an image

Another (tedious) option is to create a list of codec names supported by ffmpeg and then use ffprobe as outlined here to check against. This is also similar to just having a list of image extensions and just using Python string comprehension to check whether the extensions match that list.
The program could also read the file header and detect that way:
def is_image(file_name):
    with open(file_name, 'rb') as file:
        header = file.read(32)
        if header.startswith(b'\xff\xd8\xff\xe0') or header.startswith(b'\xff\xd8\xff\xe1'):
            return True  # JPEG/JFIF or Exif format
        if header.startswith(b'\x89PNG\r\n\x1a\n'):
            return True  # PNG format
        if header.startswith(b'GIF87a') or header.startswith(b'GIF89a'):
            return True  # GIF format
        if header.startswith(b'BM'):
            return True  # BMP format
        if header.startswith(b'\x00\x00\x01\x00'):
            return True  # ICO format
        return False

Another method is to use the mimetypes built-in library:
import mimetypes

def is_image(file_name):
    mime_type = mimetypes.guess_type(file_name)
    return mime_type.startswith('image/')

By checking for image2, I meant looking at the existing ffmpeg command's output. A further complication is that when you don't use the loop option, images actually have an intrinsic short duration and the command will exit early (when using -shortest). So this has to be considered as well.
Please check https://github.com/slhck/ffmpeg-progress-yield/pull/15 for an alternative. Does that work for you?

#15 works well, I approved directly there. Thank you for your help with this!


[build-presets] Enable stdlib assertions on Linux installations

Enable stdlib assertions in mixin_linux_installation.
Other presets which use mixin_lightweight_assertions, such as
buildbot_linux_crosscompile_android and buildbot_osx_package, are not
affected by this change.
Stdlib assertions are needed by reflection validation tests on Linux
(see https://github.com/apple/swift/pull/32339).
cc @augusto2112

@swift-ci smoke test

@shahmishal is the right person for this imo.

@swift-ci smoke test

Huh, two lldb tests are unexpectedly passing after this change. I'll take a look.
18:21:11 Unexpected Passing Tests (2):
18:21:11     lldb-api :: lang/swift/tagged_pointer/TestSwiftTaggedPointer.py
18:21:11     lldb-api :: lang/swift/variables/dict_nsobj_anyobj/TestSwiftDictionaryNSObjectAnyObject.py

These two are known UPASS after updating to newer Xcode.
https://github.com/apple/llvm-project/pull/1378
https://github.com/apple/llvm-project/pull/1379

This PR disables it for now: https://github.com/apple/llvm-project/pull/1375
@swift-ci smoke test macOS

@swift-ci smoke test macOS

It looks like CI couldn't find the llvm-project PR:
/Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/llvm-project failed (ret=128): ['git', 'fetch', 'origin', 'pull/1375/merge:ci_pr_1375', '--tags']
fatal: couldn't find remote ref pull/1375/merge
It got merged, so maybe that's why. I'll try again.

@swift-ci smoke test macOS


Fix bundler not exporting module

This adds the version comment using Banner and sets the Format to api.FormatESModule. It still doesn’t resolve #403 though, as the module is not exported. Can you please take a look, @delaneyj?

@bencroker I think you have to adjust the template of intermediate datastar.ts
{% func bundlerContent(manifest PluginManifest) %}

import { Datastar as DS } from "../engine";
{%- for _, p := range manifest.Plugins -%}
import { {%s p.Name %} } from "{%s p.Path %}";
{%- endfor -%}

DS.load(
{%- for _, p := range manifest.Plugins -%}
    {%s p.Name %},
{%- endfor -%}
);

export const Datastar = DS;
{% endfunc %}

For reference I used the bundled datastar.ts used by the release process.

Good catch, @stefanohrmann!
I’ve fixed and this is ready for @delaneyj to review.


integrating changes made in acs codebase back into dcos

Moving large .deb files onto the ephemeral disk for faster read write
times on setup. Making about a 2 min speed up in standing up a cluster.(Not exhaustively tested, but speed up was noticeable in ad-hoc testing.

Now stored in the  new folder /var/lib/mesos/dcos/
Making ssh work on port 22 on the master load balancer. Achieved by:
opening port 2222 for ssh on the master vms by modifiy sshd_config
NATing port 22 on LB to port 2222 on master 0
updating rest of networking resources to make that work.
this is none ideal in a few ways:
the arm template isn't perfectly optimized, all masters NICs depend on the new NAT rule but only one uses it, minor since the rule comes up very quickly. Didn't just drop the old NAT rule as that would be a breaking change, and wanted to do this in a none breaking manner.
messes with the sshd_config. Required since NAT rules have to be 1:1 so I couldn't reuse old port. Also uses regex and sed to modify the file. Since we start from a known state it works just none ideal. Couldn't think of a better way to do it in cloud init.

I can't see why the azure integration failed.  The vagrant appears to be a build system issue.   Can someone take a look at the details of the azure failure send them to me?

A comment about the limit you guys were hitting before. there is a limit but it is much higher than you experienced before. The compute resource provider had a bug which they fixed.  Last I knew you guys had 6000 more characters you could use in your custom data before running into an issue, currently your at about 8000 if I remember correctly.  I'll still try to make the changes you suggested though

@JackQuincy if you could address my comment on the layout and squash this PR into a single commit, I think this will be good to go. Once squashed I'll run a final pass test and we can get this merged. Thanks!!

@JackQuincy I think I would rather support a wider range of instance types at the expense of some ephemeral disk space. So I'd prefer to do a 45,45,10 layout for now. Also, it appears that one thing missing in this PR is the 550MB DC/OS bootstrap tarball is still downloading to /tmp. You can see how it needs to be adjusted in my test branch here.
So if you could take care of the layout update, the bootstrap fix, and squashing this all into 1 or 2 commits this will be ready to merge. I'm happy to help with that you don't have time. LMK. Thanks.

thanks for the help Jeremy. I just got time to make the last couple changes. Let me know if I did the layout/bootstrap right. I haven't looked at this in a while.

Thanks @JackQuincy this is ready to merge! I've also run tests verifying that ports 22 and 2200+ are forwarding as expected.


Updating the dependency to fix the security issue reported by trivy

Updating the dependency to fix the security issue reported by trivy

We seem to have bumped up versions for a number of dependencies instead of enforcing a certain version of gogo/protobuff as an indirect dependency. Would that have been the better approach? This seems to touch a lot of vendored dependencies.

We seem to have bumped up versions for a number of dependencies instead of enforcing a certain version of gogo/protobuff as an indirect dependency. Would that have been the better approach? This seems to touch a lot of vendored dependencies.

it does work but we have taken a decision to bump the direct dependency rather than doing indirect way


Little error in my GM / Latest crashdetect 4.15.1

Hello Zeex,
I found a little problem in my GM from the latest plugin.
Can you check, please?
"[13:28:01] [debug] Server crashed due to an unknown error
[13:28:01] [debug] Native backtrace:
[13:28:01] [debug] #0 f73f4e8b in _ZN10StackTraceC1EPv () from plugins/crashdetect.so
[13:28:01] [debug] #1 f73edbcf in _ZN11CrashDetect20PrintNativeBacktraceERSoPv () from plugins/crashdetect.so
[13:28:01] [debug] #2 f73eedbc in _ZN11CrashDetect20PrintNativeBacktraceEPv () from plugins/crashdetect.so
[13:28:01] [debug] #3 f73ef226 in _ZN11CrashDetect11OnExceptionEPv () from plugins/crashdetect.so
[13:28:01] [debug] #4 f73f4adc in ?? () from plugins/crashdetect.so
[13:28:01] [debug] #5 f7710410 in ?? ()
[13:28:01] [debug] #6 f748924a in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
[13:28:01] [debug] #7 f748b475 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
[13:28:01] [debug] #8 f748d8ec in __libc_malloc () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
[13:28:01] [debug] #9 f76177b5 in _Znwj () from /usr/lib/i386-linux-gnu/libstdc++.so.6
[13:28:01] [debug] #10 0807da8e in ?? () from samp03svr
[13:28:01] [debug] #11 080705bf in ?? () from samp03svr
[13:28:01] [debug] #12 08074928 in ?? () from samp03svr
[13:28:01] [debug] #13 080763fe in ?? () from samp03svr
[13:28:01] [debug] #14 f76bdc39 in ?? () from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
[13:28:01] [debug] #15 f74ed78e in clone () from /lib/i386-linux-gnu/i686/cmov/libc.so.6"
Thank you!
Best regards,
FratziWear | CEO Founder #GPR

You need to contact SA-MP developers about this, I can't help you, sorry.


A bit clearer docs

Made it more clear in the docs that complicating name prop in the Field component is also a string

Codecov Report

Merging #3663 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #3663   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          70      70
  Lines        1577    1577
======================================
  Hits         1577    1577

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f23a36e...4aa4ef6. Read the comment docs.


[New game]: Space Invaders

🎮 Game Request
Game logic and basic description:
To hit the opponents/ enemies from bullets by moving.
To defend your spaceship from enemy bullets.
Point down the features
Game points:
Hitting enemies with bullets.
Defending spaceship my movement.
Restart Game available
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @chinmayjain08 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @chinmayjain08!
We are already having a similar game request in #1108 👀
Make sure you come up with a cool unique idea 😀
Waiting for your new game idea 💗.

Hey @chinmayjain08 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


WIP Fallback policy

Proposed changes:

add policy for triggering a fallback action when nlu or core model confidence is low

to be used in an ensemble

if nlu confidence is below nlu_threshold, predict fallbackaction with probability 1

else predict fallback action with probability core_threshold

fixes https://github.com/RasaHQ/rasa_core/issues/137

Status (please check what you already did):

[x] made PR ready for code review
[x] added some tests for the functionality
[x] updated the documentation
[x] updated the changelog

@amn41  So now we need to simply pass this Fallback policy to Agent like how we are passing Keras and Memoization?

yes http://core.rasa.com/master/patterns.html#fallback-default-actions

@amn41  i implemented the fallback policy it's working fine and thanks for that but i have a question on running the bot after training it on some instance fallback  is being initialising automatically and the phrase is being coming out 3-4 times .

can you please run your bot with --debug to see what's going on?
maybe it's worth adding a story like
* default_intent
  - action_fallback

to your data so that Rasa Core knows to predict action_listen after action_fallback
(the end of the story will have action_listen added to it during training)

Actually I am running bot with below code:
while True:
    a = input("user: ")
    if a == 'stop':
        break
    responses = agent.handle_message(a)
    for response in responses:
        print("bot: ", response['text'])

I didn't get how to run bot in debug mode.
I took the latest pull and added fallback policy and a story like:
* out_of_context <!-- it is an intent defined in nlu.md -->
   - utter_default <!-- utter_default is 'Sorry i didn't get that' -->

When I run the bot with an input like bla bla bla, the bot says:
"Sorry i didn't get that" 10 times.
I tried debugging into the code and my understanding is:
action_listen is at index 0 in list of actions. So in order to return action_listen the index returned must be 0
but the below snippet returns index other than 0
def predict_next_action(self, tracker, domain):
     # type: (DialogueStateTracker, Domain) -> (float, int)
     """Predicts the next action the bot should take after seeing x.

     This should be overwritten by more advanced policies to use ML to
     predict the action. Returns the index of the next action"""
     probabilities = self.probabilities_using_best_policy(tracker, domain)
     max_index = np.argmax(probabilities) # **It should return 0 but it doesn't**
     logger.debug("Predicted next action '{}' with prob {:.2f}.".format(
             domain.action_for_index(max_index).name(),
             probabilities[max_index]))
     return max_index

Please help

to run in debug mode, you can pass the --debug flag to rasa_core.run, or in your python code:
import logging

logger = logging.getLogger()
logger.setLevel(logging.DEBUG)

I think that needs to go into the docs, you need to have a story that tells the bot what to do after the fallback action. otherwise, it might run into a loop.

@tmbo I tried adding a story to tell the bot to perform next thing after fallback action but it didn't worked.
## Fallback story
* out_of_context
  - utter_default
* thank_you{"thanku_msg": "thanks"}
  - utter_thanks

Output is:
user: bla bla bla
bot:  Sorry, I didn't understand that
bot:  Sorry, I didn't understand that
bot:  Sorry, I didn't understand that
bot:  Sorry, I didn't understand that
bot:  Sorry, I didn't understand that
bot:  Sorry, I didn't understand that
bot:  Sorry, I didn't understand that
bot:  Sorry, I didn't understand that
bot:  Sorry, I didn't understand that
bot:  Sorry, I didn't understand that

user: thanks
bot:  Thank you

In below method, the value of action_name is utter_default instead of action_listen  when user types out of context statement, so the comparison always fails and it returns True
    @staticmethod
    def should_predict_another_action(action_name, events):
        is_listen_action = action_name == ACTION_LISTEN_NAME
        return not is_listen_action

And below is the code where it goes in loop for 10 times and give utter_default  because should_predict_another_action always returns True and self.max_number_of_predictions is 10 by default.
        # action loop. predicts actions until we hit action listen
        while (should_predict_another_action
               and self._should_handle_message(tracker)
               and num_predicted_actions < self.max_number_of_predictions):
            # this actually just calls the policy's method by the same name
            action = self._get_next_action(tracker)

            should_predict_another_action = self._run_action(action,
                                                             tracker,
                                                             dispatcher)
            num_predicted_actions += 1

Can you try adding a story that directly starts with the fallback instead of yours, e.g.
## run listen after fallback
  - utter_default
* thank_you{"thanku_msg": "thanks"}
  - utter_thanks

It works fine If I put the input statement bla bla bla into intent out_of_context  like:
user: bla bla bla
bot:  Sorry, I didn't understand that
user: thanks
bot:  Thank you

but if the sentence is not into the intent out_of_context it returns utter_default 10 times which is an issue.

@imsurinder90 @tmbo  same thing is happening in my case i.e when fallback is occurring it is repeating multiple times
Generated Story -7574258607929036394

In Dialog Fallback

action_fallback

Does this PR fixes this issue? https://github.com/RasaHQ/rasa_nlu/issues/387

To me it looks like that with a fallback I cannot train the model via the command line anymore. I am used to call something like:
python -m rasa_core.train -d domain.yml -s data/stories.md -o models/partybot/partybot_nlu -u models/partybot/partybot_nlu/ --epochs 200 --online

But how can I integrate this new python file? Do I need to start the online training from a python script them? I am not sure how to integrate this fallback properly.

Yes it needs to be done in a python file, that command only uses the standard policies.
You need to add the fallback action as presented here (probably also include the MemoizationPolicy in the list of policies): http://rasa.com/docs/core/fallbacks/
And then load your data and train your model like it's done here: https://github.com/RasaHQ/rasa_core/blob/master/rasa_core/train.py#L114

i recived same problme. any solutions????


Dockerfile results in method_missing error

I am currently deploying looker_deployer at a client and am following the README to create the Docker image where commands can be run. Unfortunately I keep getting the same error. I see issue #79 where a similar error message was reported, the solution in this case was to update the gazer version (this version is now outdated so this approach is not possible). Any ideas why I am getting this "undefined method `space'" error or steps I can take to debug?
Steps to repeat:

Initialise looker.ini with a "dev" target.
Run:

docker build -t ldeploy .
docker run ldeploy content export --env dev --ini looker.ini --debug --folders 12 --local-target ./export

Resulting logs:
{"levelname": "DEBUG", "module": "deploy_content_export", "funcName": "main", "message": "ini file", "ini": "looker.ini", "timestamp": "2023-04-03T13:47:19.176112Z"}
{"levelname": "INFO", "module": "deploy_content_export", "funcName": "main", "message": "Exporting content", "env": "dev", "folders": ["12"], "dashboards": null, "looks": null, "local_target": "./export", "timestamp": "2023-04-03T13:47:19.176343Z"}
{"levelname": "DEBUG", "module": "deploy_content_export", "funcName": "recurse_folders", "message": "recursive folder crawl status", "current_id": "12", "folder_name": "Marketing", "current_list": ["Marketing"], "timestamp": "2023-04-03T13:47:20.822746Z"}
{"levelname": "DEBUG", "module": "deploy_content_export", "funcName": "recurse_folders", "message": "going for recursion", "parent_id": "1", "timestamp": "2023-04-03T13:47:20.822962Z"}
{"levelname": "DEBUG", "module": "deploy_content_export", "funcName": "recurse_folders", "message": "recursive folder crawl status", "current_id": "1", "folder_name": "Shared", "current_list": ["Marketing", "Shared"], "timestamp": "2023-04-03T13:47:21.407126Z"}
{"levelname": "DEBUG", "module": "deploy_content_export", "funcName": "send_export", "message": "folder_list", "folder_id": "12", "list": ["Shared", "Marketing"], "timestamp": "2023-04-03T13:47:21.407325Z"}
/var/lib/gems/2.7.0/gems/looker-sdk-0.1.2/lib/looker-sdk/client/dynamic.rb:106:in `method_missing': undefined method `space' for #<LookerSDK::Client:0x000055e2e8ce4ed0> (NoMethodError)
        from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/modules/space.rb:65:in `query_space'
        from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/commands/space/export.rb:89:in `process_space'
        from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/commands/space/export.rb:83:in `block in execute'
        from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/modules/session.rb:249:in `with_session'
        from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/commands/space/export.rb:51:in `execute'
        from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/commands/space.rb:82:in `export'
        from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
        from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
        from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
        from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/invocation.rb:116:in `invoke'
        from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor.rb:243:in `block in subcommand'
        from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
        from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
        from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
        from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/base.rb:485:in `start'
        from /var/lib/gems/2.7.0/gems/gazer-0.2.59/exe/gzr:36:in `<top (required)>'
        from /usr/local/bin/gzr:23:in `load'
        from /usr/local/bin/gzr:23:in `<main>'
options: {"debug"=>true, "host"=>"<REDACTED>", "port"=>"19999", "ssl"=>true, "verify_ssl"=>true, "timeout"=>60, "force"=>false, "persistent"=>false, "client_id"=>"<REDACTED>", "client_secret"=>"<REDACTED>", "dir"=>"export/Shared"}
using options ["debug=>true", "host=><REDACTED>", "port=>19999", "ssl=>true", "verify_ssl=>true", "timeout=>60", "force=>false", "persistent=>false", "client_id=><REDACTED>", "dir=>export/Shared"]
API current_version 4.0
API versions ["3.0", "3.1", "4.0"]
connecting to ["api_endpoint=>https://<REDACTED>:19999/api/4.0", "connection_options=>{:ssl=>{:verify=>true, :verify_mode=>3}, :request=>{:timeout=>60}}", "user_agent=>Gazer 0.2.59", "client_id=><REDACTED>", "client_secret=><REDACTED>"]
check for connectivity: true
verify authentication: true
logout

Versions:
root@1b1a4454b1f5:/looker_deployer# ruby -v
ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux-gnu]
root@1b1a4454b1f5:/looker_deployer# gem -v
3.2.5
root@1b1a4454b1f5:/looker_deployer# gem list | grep "gazer"
gazer (0.2.59)
root@1b1a4454b1f5:/looker_deployer# gem list | grep "looker"
looker-sdk (0.1.2)

Dockerfile:
FROM python:3.9-slim

RUN apt update
RUN apt -y install ruby ruby-dev
RUN gem install gazer

RUN apt -y install git
RUN git clone https://github.com/looker-open-source/looker_deployer.git --branch looker-deployer-v0.3.9

WORKDIR /looker_deployer

COPY looker.ini .
RUN pip install -e .

ENTRYPOINT ["ldeploy"]

Interestingly, downgrading the version of gazer does not result in this issue:
FROM python:3.9-slim

RUN apt update
RUN apt -y install ruby ruby-dev
RUN gem install gazer --version 0.2.58

RUN apt -y install git
RUN git clone https://github.com/looker-open-source/looker_deployer.git --branch looker-deployer-v0.3.9

WORKDIR /looker_deployer

COPY looker.ini .
RUN pip install -e .

VOLUME /export

ENTRYPOINT ["ldeploy"]

I'm experiencing this issue as well using --branch mcramer_alerts
/var/lib/gems/2.7.0/gems/looker-sdk-0.1.2/lib/looker-sdk/client/dynamic.rb:106:in method_missing': undefined method space' for #<LookerSDK::Client:0x000055f04906ecc8> (NoMethodError) 	from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/modules/space.rb:65:in query_space'
from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/commands/space/export.rb:89:in process_space' 	from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/commands/space/export.rb:83:in block in execute'
from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/modules/session.rb:249:in with_session' 	from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/commands/space/export.rb:51:in execute'
from /var/lib/gems/2.7.0/gems/gazer-0.2.59/lib/gzr/commands/space.rb:82:in export' 	from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/command.rb:27:in run'
from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in invoke_command' 	from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor.rb:392:in dispatch'
from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/invocation.rb:116:in invoke' 	from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor.rb:243:in block in subcommand'
from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/command.rb:27:in run' 	from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in invoke_command'
from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor.rb:392:in dispatch' 	from /var/lib/gems/2.7.0/gems/thor-1.2.1/lib/thor/base.rb:485:in start'
from /var/lib/gems/2.7.0/gems/gazer-0.2.59/exe/gzr:36:in <top (required)>' 	from /usr/local/bin/gzr:23:in load'
from /usr/local/bin/gzr:23:in <main>'
The folder I'm exporting is within the Shared folder. In case it helps pinpoint the issue, I do see that the ldeploy command successfully creates a Shared folder within the directory passed via --local-target (though it is empty)
Specifying gazer --version 0.2.58 in dockerfile fixed the issue for me as well, really appreciate your follow up comment with the workaround @pgoslatara

Updated to API 4.0 per latest release - v0.3.10 - should resolve issues.


Test: initial debug / run experience

Refs: https://github.com/microsoft/vscode/issues/84677

[ ] anyOS @jrieken
[x] anyOS @sandy081

Complexity: 3
We have improved the debug start experience for new users.
Open VSCode in the purple no folder mode and verify:

Content of the debug viewlet makes sense and helps you to start debugging / running your program
Content of the debug viewlet changes as the active file changes, buttons get disabled when you are on a file which can not be debugged

Open VSCode in a folder with no launch.json and verify:

Content of the the debug viewlet makes sense and guides you to start debugging or to create a launch.json file. Buttons get disabled / enabled based on the active file.
Once you have created the launch.json the start view is no longer visible

The point of these changes is to simplify the start debug experience to new users. Any feedback on how to better do this are  welcome.

Is this what is causing my issues since around 22 hours ago?
Launcher[1] disconnected unexpectedly

No

@FantasySoftwareDesigns

Is this what is causing my issues since around 22 hours ago?
Launcher[1] disconnected unexpectedly

Look at https://github.com/chrmarti/testissues/issues/52646

Hi,
I discovered the issue. The version of the Python library and Visual

Studio Code had auto-updated and the versions simply do not work.
On Fri, Nov 29, 2019 at 2:18 PM Isidor Nikolic<EMAIL_ADDRESS>wrote:

No
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/85774?email_source=notifications&email_token=AN5B4B4WJIJFORZZBYSUC53QWEQCPA5CNFSM4JSWBFS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFO675Q#issuecomment-559804406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN5B4B3ZI5OQJRVR3DVKU6DQWEQCPANCNFSM4JSWBFSQ
.


Generating from 18x512 latents

First, thanks for making this library.
I have some 18x512 latents that I optimized using the official version. What parameters should I use to generate the same image from those latents as the official version? I'm using the same weights but getting different results.

If you use latent variables instead of noise inputs, you can use input_is_latent in the forward function of the generator.

I'm having the same issue, I'm trying to use a couple of external images and do a style mixing withm interpolation in between the external images
The process I'm following is:

run this command for both external images python projector.py --ckpt ../ffhq-dataset/550000.pt --step=1000 --w_plus --size 256 style_mix/external1.jpg
This generates the correct latent space and noise values for both external images
I load the .pt file into memory in the generator.py
Heres my modified the code in the generator.py to do

data_1 = torch.load('external1.pt')
data_2 = torch.load('external2.pt')
latent_1 = data_1['style_mix/external1.jpg']['latent']
latent_2 = data_2['style_mix/external2.jpg']['latent']
sample, _ = g_ema([latent_1, latent_2], inject_index=i, input_is_latent=True)

Run the generator with python generate.py --size 256 --pics 1 --ckpt ../ffhq-dataset/550000.pt

Latent_1 and latent_2 shapes are 14x512, which makes the generator create a strip of 14 images instead of the 1 original image I sent over to the projector.
Is there any way to have the generator use the original external images I fed the projector instead of it thinking that there are 14 images?
Here's the images I'm feeding and the sample output I get from the generator.
External Image after projector is run

Generated Image

@ElHacker You can concat & unsqueeze two latent codes like this: torch.cat((latent_1[:index], latent_2[index:]), 0).unsqueeze(0)

Thanks @rosinality that worked.
Leaving my code here if someone is having issues with this
           latent_1 = data_1['style_mix/image1.png']['latent'].reshape(1, batch_size, 512)
           latent_2 = data_2['style_mix/image2.png']['latent'].reshape(1, batch_size, 512)
           latent = torch.cat((latent_1[:, :i], latent_2[:, i:]), 1)
           sample, _ = g_ema([latent], inject_index=i, input_is_latent=True)

A slight adjustment I had to make to the tensors was to add an extra dimension at the beginning. For example: if latent shape is 14x512 I had to reshape to 1x14X512 so that the model could generate the correct image. No unsqueeze was needed on my case.
batch_size is the number rows of the latent vector. For example if the latent vector shape is 14x512, then batch_size will be 14


Local pull request branches does not include pull requests created beforehand

Local pull request branches only shows the ones checked out or created from the extension. It doesn't show all the pull requests for which there is already a local branch, but created manually.
An alternative would be to allow "matching" or "assigning" a PR to a local branch maybe?

It seems you can manually add a github-pr-owner-number to the branch definition in your .git/config to make it show up there, e.g.:
github-pr-owner-number = "moby#moby#41638"

for PR 41638 from https://github.com/moby/moby/
That's the same annotation the extension adds to branches it creates when you "Checkout a Pull Request'.

Thanks for the tip! One-liner to set the correct github-pr-owner-number (requires gh):
git config branch.$(git branch --show-current).github-pr-owner-number \
  "$(gh pr view --json url | jq -r .url | sed 's@https://github.com/@@; s@/pull/@#@; s@/@#@g')"


Why updater is not depending on OS architecture on Win or Mac

Why the updater is not downloading win32/64 package?

Looking for this issue. Why no mac32/64 package too?

+1

Because no one got around to it. Pull-requests / suggestions / specs are more than welcome. For my usage, there's no real benefit. It's essential for Linux support though.

How to execute the step 5 and step 6 after gui.App.quit()
5. The new app (in temp) will copy itself to the original folder, overwriting the old app.
6. The new app will run itself from original folder and exit the process.


Aggregate signature verification (on an Attestation) fails due to custody_bitfield

Honest Validator spec states that the attestation.custody_bitfield should be a byte array filled with zeros.
However, during per-block processing, when processing attestations we use attestation.custody_bitfield to get custody_bit_1_participants. These participants are later passed on to bls_aggregate_pubkeys to generate an aggregate public key. Having custody_bitfield set to all zeros, the custody_bit_1_participants becomes an empty list.
First, bls_aggregate_pubkeys function seems to be undefined when there are no public keys, as in this case, because custody_bitfield was set to all zeros.
Second, during process_attestations, bls_verify_multiple is used to check the aggregate signature on the attestation, however, bls_verify_multiple currently takes two message hashes. One where AttestationDataAndCustodyBit has its custody_bit set to false and another with its custody_bit set to true. bls_verify_multiple require two aggregate public keys when passed two message hashes. Specifically, the message hash with custody_bit set to true requires the aggregate public key of Validators who had their custody_bitfield set, which in our case is none. This makes bls_verify_multiple to produce an assert.

This is a duplicate (non-)issue of https://github.com/ethereum/eth2.0-specs/issues/651.

bls_aggregate_pubkeys function seems to be undefined when there are no public keys

The zero sum is the point at infinity.

which in our case is none. This makes bls_verify_multiple to produce an assert.

As mentioned above it's not none, but rather the point at infinity. I've clarified this in #782.

Thanks for the quick fix.


"Ciocănăi", "Dealu Viilor" are listed in the drop-down menu

Description:
When user writes "Ciocănăi", "Dealu Viilor" the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Ciocănăi"

Expected results
The location appears in the drop-down menu as "Ciocănăi, Argeș (Moșoaia)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Dealu Viilor"

Expected results
The location appears in the drop-down menu as "Dealu Viilor, Argeș (Moșoaia)"


perf!: optimization

@DanySK @angelacorte Please check if my conflict resolution has not lost anything on the way.


Delete operation

See #57
In this ticket, we should take a decision about how the delete operation will be written with the Datastax driver and/or LowLevelAPI.

Once created the methods detailed in issue #70, the delete operation will be written as follows:
Delete
# CQL
DELETE name FROM User where id = <myId>;

// Datastax code
val prepSt = session.prepare("DELETE name FROM User where id = ?")
val boundStatement = prepSt.bind()
boundStatement.setBytesUnsafe("id", c1.serialize(myId))
val resultSet = session.execute(boundStatement)

   import lowLevelAPI._

    for {
      preparedStatement <- prepare("DELETE name FROM User where id = ?")
      boundedStatement  <- bind(preparedStatement)
      _                 <- setBytesUnsafe[UUID](boundedStatement, "id", user.id)
      resultSet         <- executeStatement(boundedStatement)
    } resultSet

@fedefernandez could you please review this? Thanks!

:+1:


No instances of MSBuild could be detected. Try calling RegisterInstance or RegisterMSBuildPath to manually register one.

When running the build server with the dotnet-sdk installed from in Fedora official repository, you get a similar Error:
No instances of MSBuild could be detected. Try calling RegisterInstance or RegisterMSBuildPath to manually register one."
data = {
  code = -2146233079,
  message = "No instances of MSBuild could be detected.\nTry calling RegisterInstance or RegisterMSBuildPath to manually register one.",
  stack = "   at Microsoft.Build.Locator.MSBuildLocator.RegisterDefaults()\n   at dotnet_bsp.Handlers.BuildInitializeHandler.HandleRequestAsync(InitializeBuildParams request, RequestContext context, CancellationToken cancellationToken) in /var/home/ak/devel/dotnet-bsp/src/bsp-server/
Handlers/BuildInitializeHandler.cs:line 20\n   at BaseProtocol.QueueItem`3.StartRequestAsync(TRequestContext context, CancellationToken cancellationToken) in /var/home/ak/devel/dotnet-bsp/src/bp/QueueItem.cs:line 134\n   at BaseProtocol.Server.AbstractBaseProtocolServer`1.DelegatingE
ntryPoint.EntryPointAsync[TRequest,TResponse](TRequest request, CancellationToken cancellationToken) in /var/home/ak/devel/dotnet-bsp/src/bp/Server/AbstractBaseProtocolServer.cs:line 192",
  type = "System.InvalidOperationException"
}

I am currently investigating the root cause.

Ok I used dotnet-sdk-9.0  and tried to compile the server for <TargetFramework>net8.0</TargetFramework>, this does not work. Using net9.0 in TargetFramework solves the issue.

The reason why dotnet-sdk-8.0 did not work is because I was mixing microsoft and fedora rpm repositories. They stopped distributing SDKs >= net9, for details see https://learn.microsoft.com/en-us/dotnet/core/install/linux#packages. Installing both SDKs from fedora sources, solved all compilation errors.


[BUG] Sprint Showcase - Task Creation not working correctly (multiple issues)

Adding an epic but no task still puts it in the no-epic
Plan page does not show newly-created story
Clicking away from Plan page causes task to not be added.

I think 1 is epic but no story?

Okay, resolved part 1, I think I'm going to roll 2 and 3 up into a function that just puts the created task into the task schedule screen. That way the usage is uniform.


Storing Data In Rhino File

http://python.rhino3d.com/threads/508-Storing-Data-in-a-Rhino-File
We need a mechanism for embedding data in a 3dm file beyond just strings.  I think the best way to do this would be to add support for embedded of any file type directly in a 3dm and have a way to access/create these files.  This would allow the python scripter to use something like pickle to embed custom data.
This is a concept of how the embedded file system would work.
I haven't come up with an interface for this yet in RhinoCommon so it may change while I work out the details
import cPickle as pickle
import scriptcontext
import Rhino

data1 = Rhino.Geometry.Point3d(1,2,3)
selfref_list = [1, 2, 3]
selfref_list.append(selfref_list)

#output = open("C:\\test.pkl", "wb")
output = scriptcontext.doc.EmbeddedFiles.Open("test.pkl", "wb")

# Pickle dictionary using protocol 0.
pickle.dump(data1, output)

# Pickle the list using the highest protocol available.
pickle.dump(selfref_list, output, -1)

output.close()

#pkl_file = open('C:\\test.pkl', 'rb')
pkl_file = scriptcontext.doc.EmbeddedFiles.Open("test.pkl", "rb")

data1 = pickle.load(pkl_file)
print data1

data2 = pickle.load(pkl_file)
print data2

pkl_file.close()

http://mcneel.myjetbrains.com/youtrack/issue/RH-30033


DO NOT MERGE - Fixed defaults not being added correctly to CoAP create packet from server XML handler

Now if an internal error occurs, an AwaError_Internal tag will be added to the
response for that object / object instance node.
Signed-off-by: Roland Bewick<EMAIL_ADDRESS>

run valgrind

run valgrind

[valgrind]

retest this please


Operator SDK does not support Helm v3 charts

Bug Report
What did you do?
 is a Helm chart created thanks to the Helm v3 (Version:"v3.0.1") command.
The API version of such a chart is "apiVersion: v2" (in Chart.yaml file).
$ operator-sdk new  --helm-chart  --type=helm
INFO[0000] Creating new Helm operator 'my-operator'.
Error: failed to create helm chart: failed to fetch chart: apiVersion 'v2' is not valid. The value must be "v1"ope
What did you expect to see?
The same result as the one produced when the chart has been created with a helm v2.x command line.
What did you see instead? Under which circumstances?
$ operator-sdk new  --helm-chart  --type=helm
INFO[0000] Creating new Helm operator 'my-operator'.
Error: failed to create helm chart: failed to fetch chart: apiVersion 'v2' is not valid.

Possible Solution
As a temporary workaround, replacing the "v2" information by "v1" for "apiVersion" in the Chart.yaml seems do the trick.
Additional context
NA

@tapairmax Helm 3 support is not present in that commit. Please recompile from the latest master. If you still experience issues, let us know and we can re-open!
And thanks for testing this out! We'd love to be able to iron out any issues with the Helm 3 change before it makes it into a release.

Hi, I've upgraded the operator-sdk version up to the latest on the master branch and tested again.
Now, the Helmv3 Chart is no longer and issue, however when I run the Controller I see some errors like this:
$ operator-sdk up local
INFO[0000] Running the operator locally.
INFO[0000] Using namespace default.
{"level":"info","ts":1576571116.9778278,"logger":"cmd","msg":"Go Version: go1.13.4"}
{"level":"info","ts":1576571116.9778664,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":1576571116.9778714,"logger":"cmd","msg":"Version of operator-sdk: v0.13.0+git"}
...
{"level":"error","ts":1576571818.116149,"logger":"helm.controller","msg":"**Failed to get release manager","namespace":"default","name":"example-orangecockroachdbinsecurek8schart","apiVersion":"charts.helm.k8s.io/v1alpha1","kind":"OrangeCockroachdbInsecureK8SChart","error":"failed to convert releases from v2 to v3: invalid label value: \"example-orangecockroachdbinsecurek8schart-3o49npdtlvxc95vwunmg2xoda\": must be no more than 63 characters","stacktrace":"github.com/go-logr/zapr.(*zapLogger)**.Error\n\t/home/cloud/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\ngithub.com/operator-framework/operator-sdk/pkg/helm/controller.HelmOperatorReconciler.Reconcile\n\t/home/cloud/go/src/github.com/operator-sdk/pkg/helm/controller/reconcile.go:82\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/cloud/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:256\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/cloud/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/home/cloud/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/home/cloud/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191004115801-a2eda9f80ab8/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/home/cloud/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191004115801-a2eda9f80ab8/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/home/cloud/go/pkg/mod/k8s.io/apimachinery@v0.0.0-20191004115801-a2eda9f80ab8/pkg/util/wait/wait.go:88"}

@tapairmax I hit that too. Resolved it by changing the apiVersion in my Chart.yaml from v1 to v2.


Badge alignment.

#113

Looks good to me 🙌
@swasthikcnayak do you have any other suggestions?

Looks good to me 🙌
@swasthikcnayak do you have any other suggestions?

Looks good

Looks good

https://github.com/18praneeth/sushiksha-website/blob/master/templates/badge-create.html
Hey can you do the same to badge.html as we have two types of badge giving pages, this is second one

Yes ill do the same

https://github.com/18praneeth/sushiksha-website/blob/master/templates/badge-create.html
Hey can you do the same to badge.html as we have two types of badge giving pages, this is second one

Yes ill do the same


Prettify Readme

Add badges and other stuff

Rust
MongoDB
Go Amizone
Discord Bot invite link
poise (maybe)

License shows up as unspecified

#5 fixes this


fix: apply url_params in global async query

SUMMARY

fix Jinja template is not working when the global async query is enabled.
Currently, Superset uses serialized query_obj and form_data to generate query_cache_key. But in the global async query, we didn't pass form_data. We have to get cached data from the data cache and put the cache data to g.form_data to fix it.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before
https://user-images.githubusercontent.com/2016594/155511464-b0f99a24-cb90-467e-ad2a-7e862d6fd769.mov
After
https://user-images.githubusercontent.com/2016594/155512121-c2feea8f-e880-483f-b5c4-e4860cd5c88d.mov
TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[x] Has associated issue: fix: https://github.com/apache/superset/issues/16650
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@zhaoyongjie I believe global async queries have 2 code paths. Does superset/explore_json/data also need to be updated in this PR?
I applied this patch to our internal fork of v1.3 and verified this fix works when requests are sent to api/v1/chart. However I still see issues when url_params are used with GAQ and the request is sent to superset/explore_json/data.

Hi @kekwan, This issue has been fixed by PR. So I closed this one.

Hi, I am facing the same kind of issue. I am using the Jinja template variable {{ current_aw_user_id() }} in my queries.
my queries is very simple:
SELECT * FROM attendance where id ='{{current_aw_user_id()}}';
SELECT * FROM user where reporting_to_id ='{{current_aw_user_id()}}';
I am facing the same "Unexpected error" issue.

what could be the issue, I went through multiple posts but didn't find any solution.

hey @zhaoyongjie. i don't believe this issue is fixed by https://github.com/apache/superset/pull/18960. I am on 1.5.1 which includes that PR but I'm still encountering this bug.
I put up https://github.com/apache/superset/pull/23641 which has your fix and also a fix for legacy charts that use /explore_json endpoint as well.


Add some example, please

Loïc. Would You be so kindly to add some example of usage for this code?
How should handler properly behave on once/false flags, etc?

I'll add an example to cowboy_examples tomorrow.

Yeah. I actually started writing it today, but stopped when I noticed I should probably write a bigger example to better explain how it works. Showing how Active should be handled can't be done with just timers and so I'll be expanding this to add a session that lets the user speak to himself or something. It's coming this week anyway, I need it to test something.

Some edocs or detailed -specs or a txt file with documentation, or a javascript/HTML example if possible.
I'm waiting on this one too :P
At this moment have no idea how to send response to client.

I added some documentation in the README file with both JS and Erlang sides explained. Please tell here what you don't understand and I'll update it again with answers!

Hello.
How to write a dispatch rule for a bullet handler?

Which is format of url?
var bullet = $.bullet(url);

ws://host/path?qs
or wss://host/path?qs for secure transport
I'll fix the doc later today.

Added more documentation based on user reports! See README.
All that's missing now is a user guide with step by step walkthrough, but that one will have to wait a bit.

There is code from real applications which can serve as example.
https://github.com/freeakk/cascadae/blob/master/src/c_stream_handler.erl
https://github.com/freeakk/rhyacotriton/blob/master/source/class/rhyacotriton/store/Remote.js

Nice!


Errors running on GCE due to alpine linux being unable to read /etc/resolv.conf search directive

Hi,
I think the overall issue with GCE is that kube-lego is unable to properly resolve DNS. This is due to the Alpine:3.5 base image of the kube-lego docker container.
Look at this alpine linux restriction concerning DNS, that does not use any search directives inside /etc/resolv.conf: https://github.com/gliderlabs/docker-alpine/blob/master/docs/caveats.md#dns
and it seams that this restriction is still present in the latest alpine docker image.
The /etc/resolv.conf on GCE looks like the following:
/ # cat /etc/resolv.conf
search default.svc.cluster.local svc.cluster.local cluster.local google.internal c.xxx-0000.internal
nameserver <IP_ADDRESS>
options ndots:5

Quick fix: look at this docker image - https://github.com/janeczku/docker-alpine-kubernetes. What would you say?

Which image tag of kube-lego are you using?
The alpine image is not released yet

I am using kube-lego:0.1.3. So you say that this version does not inherit FROM alpine:3.5?
Because with kube-lego:0.1.3 I am getting the following error message:
Error while process certificate requests: Secret \"echoserver-tls\" is invalid: [data[tls.crt]: Required value, data[tls.key]: Required value]" context=kubelego

Also enabling the debug output doesn't provide any further hints. I thought that the problem is due to not correctly resolving DNS inside kubernetes GCE.
When I use kube-lego:0.1.0 it works though.
Any hints on how to fix this? It seams that many are having the same issue when used with GCE.

I was able to resolve the issue by building a kube-lego docker image from the current master. https://hub.docker.com/r/seblau/kube-lego/
It works with GCE now!


Gulp- Error: File to import not found or unreadable: bourbon.

I'm creating a starter project using latest versions of Neat and Bourbon. However, I'm having trouble importing bourbon to my stylesheet. Please see below or feel free to download the project here
Package.json
I have no packages installed globally.
"devDependencies": {
    "bourbon": "^4.3.4",
    "bourbon-neat": "^2.1.0",
  }

Gulpfile.js
var bourbon 	= require('bourbon').includePaths;
var neat		= require('bourbon-neat').includePaths;

gulp.task('sass', function(){
	gulp.src('source/scss/*.scss')
       .pipe(sass({
        	includePaths: bourbon,
        	includePaths: neat
      	}))
	.pipe(gulp.dest('public/css')) // save output in public css folder
	.pipe(browserSync.stream());
});

SCSS file
@import "bourbon";
@import "neat";
@import "grid-settings";

Error
Error: File to import not found or unreadable: bourbon.
>> @import "bourbon";
   ^

Well, that's fixed it!. Thanks!

@ssosina check out https://github.com/thoughtbot/gulp-bourbon-neat-example
I put together an example repo for an upcoming blogpost that has everything set up.

@whmii Gracias amigo!


Attempt at Flowables::fromPublisher, and an example

The example has an "onSubscribe" function, and a fromPublisher operator. I think this is what @benjchristensen had in mind.

closing as it landed with https://github.com/ReactiveSocket/reactivesocket-cpp/pull/356


fix(send user to right url when selecting no): send user to right url when selecting NO

send user to right url when selecting NO

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

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


jxrlib: 1.1 -> 2019.10.9

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://github.com/4creators/jxrlib/releases.
meta.description for jxrlib is: "Implementation of the JPEG XR image codec standard"
meta.homepage for jxrlib is: "https://jxrlib.codeplex.com"

Quoted meta.homepage for RFC 45

Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2019.10.9 with grep in /nix/store/xygzr8vm3mb4s182z9ip7akqs75yg2vs-jxrlib-2019.10.9

directory tree listing: https://gist.github.com/a17ee17efeee21354d7f326762161b44

du listing: https://gist.github.com/e0d825f39c8e60db1f1a083dfa5c426f

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
jxrlib

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xygzr8vm3mb4s182z9ip7akqs75yg2vs-jxrlib-2019.10.9 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A jxrlib https://github.com/r-ryantm/nixpkgs/archive/8d34fc7a6f4db7f7387f0e04d309a0e64c2b4717.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xygzr8vm3mb4s182z9ip7akqs75yg2vs-jxrlib-2019.10.9
ls -la /nix/store/xygzr8vm3mb4s182z9ip7akqs75yg2vs-jxrlib-2019.10.9/bin

cc @romildo for testing.

It is the same revision in the git repository. What is new is that now there is a release.

@romildo The diff is bad because it doesn't change src or src hash

@romildo The diff is bad because it doesn't change src or src hash

I think the hash should not have changed, because it is the same revision in the repository.


grammatical fixes

-change verb tense to subjunctive
-fix translation of 'behind the scenes'
-fix 'su' to 'tu' to go with informal use of 'tu' throughout document

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[ ] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

Thanks @mmmeyers can you get someone (native speaker) to peer review this for us to be able to merge this.


Add integer, dimen, glue group parsers

Size argument
Primitive commands, such as \above and kern commands don't not allow braced size argument. This PR introduces a new argument type size_primitive to parse it. For backward compatibility, braced size arguments are allowed in non-strict mode. (BREAKING CHANGE) Fixes #1936.
Furthermore, a blank size argument was allowed for most commands. This PR introduces a new argument type size_or_blank, which allows a blank argument, and use it only for \genfrac.[2]

Codecov Report

Merging #2139 into master will decrease coverage by 0.96%.
The diff coverage is 38.88%.

@@            Coverage Diff             @@
##           master    #2139      +/-   ##
==========================================
- Coverage   94.81%   93.85%   -0.97%
==========================================
  Files          81       81
  Lines        5281     5334      +53
  Branches      926      941      +15
==========================================
- Hits         5007     5006       -1
- Misses        250      291      +41
- Partials       24       37      +13

Flag
Coverage Δ

#screenshotter
88.76% <33.33%> (-0.93%)
:arrow_down:

#test
87.64% <38.88%> (-0.9%)
:arrow_down:

Impacted Files
Coverage Δ

src/parseNode.js
84.21% <ø> (ø)
:arrow_up:

src/macros.js
97.48% <ø> (-0.17%)
:arrow_down:

contrib/render-a11y-string/render-a11y-string.js
89.18% <0%> (-1.05%)
:arrow_down:

src/units.js
95.45% <100%> (ø)
:arrow_up:

src/functions/char.js
100% <100%> (+9.09%)
:arrow_up:

src/Parser.js
85.32% <38.82%> (-11.27%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d10f375...e97159d. Read the comment docs.

@ylemkimon the tests are passing now.  Is there more that you wanted to do with this PR or is it ready for review now?

Codecov Report

Merging #2139 into master will decrease coverage by 1.78%.
The diff coverage is 63.77%.

@@            Coverage Diff             @@
##           master    #2139      +/-   ##
==========================================
- Coverage   94.77%   92.99%   -1.79%
==========================================
  Files          83       84       +1
  Lines        5360     5508     +148
  Branches      940      985      +45
==========================================
+ Hits         5080     5122      +42
- Misses        257      340      +83
- Partials       23       46      +23

Flag
Coverage Δ

#screenshotter
87.66% <60.12%> (-0.79%)
:arrow_down:

#test
86.90% <63.46%> (-1.73%)
:arrow_down:

Impacted Files
Coverage Δ

contrib/render-a11y-string/render-a11y-string.js
88.50% <0.00%> (-0.69%)
:arrow_down:

src/functions.js
100.00% <ø> (ø)

src/functions/cr.js
95.65% <ø> (ø)

src/parseNode.js
80.00% <ø> (ø)

src/functions/arithmetic.js
9.61% <9.61%> (ø)

src/functions/def.js
93.33% <66.66%> (-3.50%)
:arrow_down:

src/Parser.js
86.40% <67.40%> (-10.46%)
:arrow_down:

src/units.js
91.17% <84.61%> (-4.28%)
:arrow_down:

src/MacroExpander.js
93.75% <89.28%> (-2.98%)
:arrow_down:

src/functions/char.js
100.00% <100.00%> (+9.09%)
:arrow_up:

... and 15 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5749289...338e89d. Read the comment docs.

This incorporates changes from #2085, so it'd be preferable to review it first.


Select 'enhanced' Improper Rendering

The Select 'enhanced' prop appears to cause improper rendering with its contents (demonstrated below).

Using the README code as a template, I created this app to demonstrate the behavior.
I am not sure if this is reproducible behavior, wanted to submit just in case.

did u import<EMAIL_ADDRESS>?

You actually need to import all of these:
import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>

opening pr

Per your suggestions, the expected behavior was accomplished with the following imports:
import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>
Attempts at importing import<EMAIL_ADDRESS>resulted in an error (see here). Thank you for your assistance, @will-ebm and @moog16!

Hm that's strange as sass file does exist. Might be an issue with turbo modules as well...


Compatibility to bulma.io css framework

At the moment, both prism and Bulma are using the same CSS class 'number'. This causes that numbers within a code block are displayed wrong formatted.
I think the number class should be renamed to something less generic or a prefix should be added to the class (e.g.: prism-number).
Quick fix for bulma.io users with jQuery:
    $( document ).ready(function() {
        removeNumberClassFromCode();
    });

    function removeNumberClassFromCode() {
        $('.token').each(function () {
            $(this).removeClass('number');
        });
    }

Hi!
We do have a plugin to add prefix to all classes added on tokens. You'll have to change the theme's stylesheet yourself, though.


translated /content/plugins/module-concatenation-plugin.md

describe your changes...

[x] Read and sign the CLA. PRs that haven't signed it won't be accepted.
[x] Make sure your PR complies with the writer's guide.
[x] Review the diff carefully as sometimes this can reveal issues.
Remove these instructions from your PR as they are for your eyes only.

@Aladdin-ADD fixed

@Aladdin-ADD  fixed

thats it


QoL for scribble_font_bake_outline_and_shadow

Hey Juju,
in the docs I can see
Change in every glyph’s SCRIBBLE_GLYPH.SEPARATION value.
For a shader that adds a border of 2px around the entire glyph, this value should be 4px

So, the separation can be calculated easily in the scribble_font_bake_outline_and_shadow function, as you already have a variable for the _outlineSize, adding a bit QoL by making the _separation argument optional. It defaults to 2 * _outline_size. User can still enter another separation, as he can enter another texture size.
kind regards,
Gris/Mike

This was a feature for the old outline (border) functions and I got a surprising number of people asking me how to "fix" the QOL change.


Pushed logic into config class

Converted build_easy_paths to "private".  That logic should be
handled inside the config class as part of init.  We aren't going
to initialize a config object without doing this.
Removed update_ansible_defaults all together.  Not sure why this
is necessary.  These options are specific to ansible, not molecule,
so should live under the ansible section.
Removed env['MOLECULE_PLATFORM'].  No idea why env var was being used
for.

Looks good! 👍

LGTM 👍


Update about-workflows-long.md (missing 'of')

Why:
I think you missed an 'of' in "each which can perform.."

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@Write2Hack Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


CommandResult Message

There is a bug that I found so far.

With commands that require task index, Command will throw an IndexOutOfBound Error and GUI is unable to capture this.
Please remove the throws and wrap it inside the getFeedbackToUser() method. @VietAnh1010

Next, I don't see the need for getFeedbackToUser() when we could use toString()?
For the Command @liujiayue314 @DerenC , the current message doesn't seem to be very nice.
For example: When creating a task, I get the following result:
New task created: Todo description: Finish CS2103T v1.3 status: not done
Could we perhaps change it to a more pleasing message? Such as.
Created a new to-do: Finish CS2103T v1.3

To finalise what should we show in the toString() of a task,
some samples of task.toString():

OP1 reflection --> Show only title
OP1 reflection by 2023-04-01 --> Show title & deadline
OP1 reflection by 2023-04-01 !!! --> Show title, deadline & priority
OP1 reflection by 2023-04-01 under 'ES2660', 'essay'  --> Show title, deadline & labels
OP1 reflection by 2023-04-01 under 'ES2660', 'essay' !!! --> Show title, deadline, labels & priority

Also should we display task's status in toString()?
Which one yall find that it makes most sense? To me showing labels & status are kinda not important (and labels might make it looks too cluttered), thus I am more inclined towards (3)

Will keep task.toString() untouched so that can use it to debug