Refreshing Storage Explorer while writing to AppendBlob leads to exception: "The blob has been modified while being read"

Package Name: azure-storage-blob
Package Version: 12.13.1
Operating System: Ubuntu 20.04 on WSL, Windows 10
Python Version: 3.8.9
Storage Explorer Version: 1.25.1

Describe the bug
Refreshing storage explorer while uploading data to an AppendBlob in a container in an ADLS Gen2 storage account leads to the following error: "azure.core.exceptions.ResourceExistsError: The blob has been modified while being read."
To Reproduce
Steps to reproduce the behavior:

Run this code:

import os
import asyncio
from azure.identity.aio import DefaultAzureCredential
from azure.storage.blob import BlobType
from azure.storage.blob.aio import BlobServiceClient

async def example():
    account_name = os.environ['AZURE_STORAGE_ACCOUNT']

    credential = DefaultAzureCredential(
        exclude_environment_credential=False,
        exclude_managed_identity_credential=False,
        exclude_visual_studio_code_credential=True,
        exclude_shared_token_cache_credential=True,
        exclude_cli_credential=True,
    )

    blob_service_client = BlobServiceClient(f"https://{account_name}.blob.core.windows.net/", credential)

    container_client = blob_service_client.get_container_client("censor")

    file_name = f"example.jsonl"

    for _ in range(1000):
        data = str([x for x in range(1000000)]) + "\n"

        await container_client.upload_blob(file_name, data, blob_type=BlobType.APPENDBLOB)

    container_client.close()

asyncio.run(example())

While browsing the container in Azure Storage Explorer, click refresh during the upload.

Expected behavior
It shouldn't crash, refreshing storage explorer shouldn't interfere with writes.
Traceback:
Traceback (most recent call last):
  File "crash.py", line 31, in <module>
    asyncio.run(example())
  File "/home/username/.pyenv/versions/3.8.9/lib/python3.8/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/home/username/.pyenv/versions/3.8.9/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "crash.py", line 27, in example
    await container_client.upload_blob(file_name, data, blob_type=BlobType.APPENDBLOB)
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/core/tracing/decorator_async.py", line 79, in wrapper_use_tracer
    return await func(*args, **kwargs)
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/aio/_container_client_async.py", line 847, in upload_blob
    await blob.upload_blob(
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/core/tracing/decorator_async.py", line 79, in wrapper_use_tracer
    return await func(*args, **kwargs)
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/aio/_blob_client_async.py", line 406, in upload_blob
    return await upload_append_blob(**options)
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/aio/_upload_helpers.py", line 326, in upload_append_blob
    process_storage_error(error)
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/_shared/response_handlers.py", line 181, in process_storage_error
    exec("raise error from None")   # pylint: disable=exec-used # nosec
  File "<string>", line 1, in <module>
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/aio/_upload_helpers.py", line 313, in upload_append_blob
    return await upload_data_chunks(
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/_shared/uploads_async.py", line 76, in upload_data_chunks
    range_ids.append(await uploader.process_chunk(chunk))
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/_shared/uploads_async.py", line 194, in process_chunk
    return await self._upload_chunk_with_progress(chunk_offset, chunk_bytes)
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/_shared/uploads_async.py", line 210, in _upload_chunk_with_progress
    range_id = await self._upload_chunk(chunk_offset, chunk_data)
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/_shared/uploads_async.py", line 335, in _upload_chunk
    self.response_headers = await self.service.append_block(
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/core/tracing/decorator_async.py", line 79, in wrapper_use_tracer
    return await func(*args, **kwargs)
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/storage/blob/_generated/aio/operations/_append_blob_operations.py", line 370, in append_block
    map_error(status_code=response.status_code, response=response, error_map=error_map)
  File "/home/username/git/repository/.venv/all/lib/python3.8/site-packages/azure/core/exceptions.py", line 107, in map_error
    raise error
azure.core.exceptions.ResourceExistsError: The blob has been modified while being read.
RequestId:CENSORED
Time:CENSORED
ErrorCode:BlobModifiedWhileReading
Content: <?xml version="1.0" encoding="utf-8"?><Error>BlobModifiedWhileReading<Message>The blob has been modified while being read.
RequestId:CENSORED
Time:CENSORED</Message></Error>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7f3bf08291f0>
Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7f3bf07e7340>, 26403.3207315)]']
connector: <aiohttp.connector.TCPConnector object at 0x7f3bf0829c70>
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7f3bf0829b80>
Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7f3bf0818f40>, 26400.7723782)]']
connector: <aiohttp.connector.TCPConnector object at 0x7f3bf0829b20>

Thanks for the feedback @vholmer, we'll investigate asap.

Hi @vholmer Viktor, I talked with the service team, and this is an unfortunate side-effect / limitation of how Append Blobs on ADLS Gen 2 accounts work in the backend. Without going into too much detail, performing a List Blobs call (the operation that happens when you refresh the container view in Storage Explorer) when writing to a blob will currently cause a conflict in the backend and return this error.
The current recommendation for this is to retry the write request as it should succeed the next time. The SDK has automatic retry logic for most HTTP 5xx errors, but the service is currently returning this as a 409 and therefore the automatic retry is not taking place. The service team has mentioned they are planning to fix this and start returning a 5xx error so that clients can retry (no ETA currently). In the meantime, you can try catching the azure.core.exceptions.ResourceExistsError and retrying the request.
The service team has additionally mentioned they are actively working on improving the logic to reduce / eliminate the chance for this conflict in the backend, but I do not have an ETA for that work either.
I know this isn't a great answer but there is not much we can do about this from the client side currently. Thanks.

Thanks for your answer @jalauzon-msft Jacob. Is this same issue also present in regular Blob Storage accounts? I actually don't have a specific need for ADLS Gen2 here, that's just an existing account I ended up using.

Hi @vholmer Viktor, this issue should not be present when using a regular Storage Account (with HNS disabled). I just tried the same example with a regular Storage Account and could not get the issue to repro.
So, if switching to a regular Storage Account is an option for you, that may be a good idea. Beyond this specific issue, if you do not need the ADLS Gen 2 capabilities, it's best to be using a regular account for other reasons as well. This is especially true if you are planning to use the Blob SDK as that is recommended only for non-HNS (flat) accounts. The datalake SDK is recommended for working with HNS accounts but does not currently support creating Append Blobs.

@jalauzon-msft thanks for the reply and assistance! I'll go with a regular storage account for this. 😄

This seems to also be happening when we OpenReadAsync even though we initiate the DataLakeOpenReadOptons to true in the Dotnet SDK.
 using Stream sr = await client.OpenReadAsync(new DataLakeOpenReadOptions(true) { Position = position });
 byte[] buffer = new byte[length];
 await sr.ReadAsync(buffer.AsMemory(0, length));

Throws
Microsoft.DeviceSecurity.FileStorage.Exceptions.StorageOperationException: The blob has been modified while being read.
RequestId:82d623e1-f01e-004f-435d-2b2d05000000
Time:2023-01-18T16:51:13.6679914Z
Status: 409 (The blob has been modified while being read.)
ErrorCode: BlobModifiedWhileReading
Content:
BlobModifiedWhileReadingThe blob has been modified while being read.
RequestId:82d623e1-f01e-004f-435d-2b2d05000000
Time:2023-01-18T16:51:13.6679914Z
Headers:
Server: Windows-Azure-Blob/1.0,Microsoft-HTTPAPI/2.0
x-ms-request-id: 82d623e1-f01e-004f-435d-2b2d05000000
x-ms-client-request-id: 4260babe-a88b-4d7f-b513-37fe82ebfb99
x-ms-version: 2021-06-08
x-ms-error-code: BlobModifiedWhileReading
Date: Wed, 18 Jan 2023 16:51:13 GMT
Content-Length: 237
Content-Type: application/xml
---> Azure.RequestFailedException: The blob has been modified while being read.
RequestId:82d623e1-f01e-004f-435d-2b2d05000000
Time:2023-01-18T16:51:13.6679914Z
Status: 409 (The blob has been modified while being read.)
ErrorCode: BlobModifiedWhileReading
Content:
BlobModifiedWhileReadingThe blob has been modified while being read.
RequestId:82d623e1-f01e-004f-435d-2b2d05000000
Time:2023-01-18T16:51:13.6679914Z
Headers:
Server: Windows-Azure-Blob/1.0,Microsoft-HTTPAPI/2.0
x-ms-request-id: 82d623e1-f01e-004f-435d-2b2d05000000
x-ms-client-request-id: 4260babe-a88b-4d7f-b513-37fe82ebfb99
x-ms-version: 2021-06-08
x-ms-error-code: BlobModifiedWhileReading
Date: Wed, 18 Jan 2023 16:51:13 GMT
Content-Length: 237
Content-Type: application/xml
at Azure.Storage.Blobs.BlobRestClient.DownloadAsync(String snapshot, String versionId, Nullable'1 timeout, String range, String leaseId, Nullable'1 rangeGetContentMD5, Nullable'1 rangeGetContentCRC64, String encryptionKey, String encryptionKeySha256, Nullable'1 encryptionAlgorithm, Nullable'1 ifModifiedSince, Nullable'1 ifUnmodifiedSince, String ifMatch, String ifNoneMatch, String ifTags, CancellationToken cancellationToken)
at Azure.Storage.Blobs.Specialized.BlobBaseClient.StartDownloadAsync(HttpRange range, BlobRequestConditions conditions, Boolean rangeGetContentHash, Int64 startOffset, Boolean async, CancellationToken cancellationToken)
at Azure.Storage.Blobs.Specialized.BlobBaseClient.DownloadStreamingInternal(HttpRange range, BlobRequestConditions conditions, Boolean rangeGetContentHash, IProgress1 progressHandler, String operationName, Boolean async, CancellationToken cancellationToken)
at Azure.Storage.Blobs.Specialized.BlobBaseClient.<>c__DisplayClass93_0.<b__1>d.MoveNext()
--- End of stack trace from previous location ---
at Azure.Storage.LazyLoadingReadOnlyStream'1.DownloadInternal(Boolean async, CancellationToken cancellationToken)
at Azure.Storage.LazyLoadingReadOnlyStream'1.ReadInternal(Byte[] buffer, Int32 offset, Int32 count, Boolean async, CancellationToken cancellationToken)
at Azure.Storage.LazyLoadingReadOnlyStream1.ReadAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)

Hi @jonycodes, this could be a similar cause if you are also writing to the same blob at the same time as you are performing the read. Retrying your read could help. If you need more help please open a new issue in the .NET repo, thanks.


Spec format & Usability for editors

We might want to revisit the spec format once v3 finalized content-wise, this collects some thoughts from my work with the v3 spec and from different discussions in the ZEP meetings. IMO larger changes should be done strictly afterwards to avoid conflicts with ongoing work regarding the v3 core spec and to avoid withdrawing any focus from it.

The current division how concepts are explained is confusing sometimes. Currently, there is the Concepts and terminology section, some parts have additional specific sections, and many of them are referenced in the Metadata section again.
E.g. for data types:

Data type in Concepts and terminology
Specific Data type section
data_type in the Array metadata
The concepts and terminology section are sometimes slightly too detailed. All of those sections should have cross-links to ease navigation between them. A short index with links to definitions in the end would be great IMO

cross-references etc are quite complicated atm
Some parts use quoted blocks to separate sections, e.g. the different parts in Concepts and terminology. This prevents cross-links to such parts.
It would be great to have better guidelines for edits in the README, e.g. mentioning the ZEP process, technical documentation (sphinx, rst, …), having templates for extensions/stores/dtypes/etc.
OME uses bikeshed for the spec (via markdown-to-spec, but isn't super happy with it as well, see https://github.com/ome/ngff/issues/147. Since there's quite an overlap between the contributers with this project, it might make sense to consider using the same tool.

See also the comments in #74.


Segmentation fault after invoking json_object_clear() and json_object_remove() back to back.

Consider the following snippet
    JSON_Value *foo = json_value_init_object();
    JSON_Object *bar = json_value_get_object(foo);
    json_object_set_string(bar, "key1", "string");
    json_object_clear(bar);
    json_object_remove(bar, "key1");
    json_object_set_string(bar, "key2", "test");

Call to json_object_remove() will still find "key1" key if freed heap (from calling json_object_clear()) is left untouched. json_object_get_cell_ix() will seek previously freed mem and find key. At that point, top-level count member will be decremented and possibly rollback to -1. Any further operation that relies on a valid obj->count value (like json_object_set_string() in example above) will probably generate a segmentation fault if this value rolled back over zero.
Suggestion
Reset obj->cell_capacity on json_object_clear() call
Maybe resetting obj->item_capacity as well might be a good idea?

Fixed in 1.5.1, thanks!


[fix] Broken slide on review section

fixed the jQuery CDN, that prevented the slide from working.
test link: https://shiny-dollop-55gj4r6g4qv34w7g-3000.app.github.dev/

@c4coderandcreator I noticed the slider was broken so I fixed it,
kindly review.

Hey @Petsamuel  The demo is not accessible , kindly provide the demo with gif/video !!

Also create the PR with UI-Improvement branch

@c4coderandcreator is this issue resolved ? should go ahead with the changes you requested?


Remove examples/ directory

Summary
This commit removes the examples/ directory from Qiskit. At one time in the past these scripts and qasm files served as a useful example for how to get started with Qiskit. However the patterns shown in these examples aren't very relevant anymore and have been superseded by the official documentation and the numerous tutorials out there now. While these examples still work as we've been running tests to validate they're still functional on every commit, there is little value in keeping them around. This commit removes the examples directory and all the files contained within. The test_examples unittest module is also removed since there is nothing left to test anymore.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.02%) to 88.784%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
5
92.73%

Totals

Change from base Build<PHONE_NUMBER>2:
0.02%

Covered Lines:
73481

Relevant Lines:
82764

💛  - Coveralls

the pyproject.toml has a test-command variable which uses the examples too

This should have been fixed by #13205

CONTRIBUTING.md mentions test_examples in explaining tests
the Makefile also runs the examples, doesn't it?

Fixed in: https://github.com/Qiskit/qiskit/pull/13218/commits/09365f8ec02766ab7ae681dafbba355b36cb8cff


Qiskit/qiskit#1303 change Markdown link to reStructuredText syntax

Fix https://github.com/Qiskit/qiskit/issues/1303

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


inconsistency between resourcemap.xml and actual access URLs

@pkdash @hyi
I'm working with a dev instance in SSL mode and have discovered an anomaly. When HydroShare puts a URL into a resourcemap, it always uses the non-SSL TCP port for it. However, when running in SSL, it isn't available at that port. The hs_restclient knows this and ignores that URL and constructs its own.
URLs that aren't actually pointing to the resource are of limited usefulness. We need to construct URLs that we're actually using!

@alvacouch please close or act if needed.

This is a deep issue that remains to be addressed.  As commented in later issues, the generation of URLs remains inconsistent between production and beta deployments, and is inconsistently implemented.

@alvacouch should we address this issue as a bug or is it an enhancement?

Scott indicated that URLs in resource map are being used successfully, so suggests closing.


debugger always fails to "restore"

VSCode Version:
0.10.11

OS Version:
Windows 10x64
Steps to Reproduce:

.NET CLI version

.NET Command Line Tools (1.0.0-rc2-002306)

Product Information:
 Version:     1.0.0-rc2-002306
 Commit Sha:  0747d31f86

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.10586
 OS Platform: Windows
 RID:         win10-x64

Install Visual Studio Code
Install the dot net cli
Open a command line (cmd or PowerShell)
Navigate to a folder
Type dot net new and hit ENTER to create a new project.
Right click inside the folder (Windows Explorer) and select Open with VS Code

The OUTPUT window appears and spouts off a lot of attempts to pull in files, and then yields an error; it is different each time for me.

This issue was moved to OmniSharp/omnisharp-vscode#169


[GLUTEN-6656][CELEBORN] Fix CelebornColumnarShuffleWriter assertion failed

What changes were proposed in this pull request?
After https://github.com/apache/incubator-gluten/pull/6432, if all of the ColumnarBatch have empty rows in CHCelebornColumnarShuffleWriter, the nativeShuffleWriter won't be initialized and causes assertion failed. The VeloxCelebornColumnarShuffleWriter  also has the same issue even without https://github.com/apache/incubator-gluten/pull/6432.
(Fixes: #6656)
How was this patch tested?
PASS CI

@exmy, VeloxCelebornColumnarShuffleWriter has the same problem without #6432, right? If yes, please update the description of this pull request.

Done.


Doesn't work on  IE9

It works well on Firefox, chrome, IE10, IE11, Edge, except  IE9, anyone has any ideas for this? Thanks in advance.

So, react-scrollable-anchor depends on jump.js, which relies on requestAnimationFrame. I also use history.replaceState in the hash utils. These two functions aren't supported in IE10. Therefore, the package doesn't support IE9 out of the box, and I'd prefer not to include polyfills in the package. I believe if you polyfill these, you would be good to go on IE9!


Add test that runs the S3 scrubber

In #6079 it was found that there is no test that executes the scrubber. We now add such a test, which does the following things:

create a tenant, write some data
run the scrubber
remove the tenant
run the scrubber again

Each time, the scrubber should actually not do anything. Before #6079 we would have errored.
Fixes #6080

tests fail due to missing control plane API. Obviously we don't have that one around. Should I add a mode that allows one to ignore the control plane, disabling the "does tenant exist check", and assuming it always exists?


Any idea about dotabuff's series feature

The dotabuff released series feature, which contains BO1,BO2,BO3 and BO5.
I know we can get series_type from GetMatchHistory.
However I found that series_type can only be 0, 1, 2, which represents BO1, BO3 and BO5.
Anyone have ideas about how they get type BO2?
Currently My idea is that if this match belongs to the same league same team with series_type=0, and if his next match's opponent remains unchanged then it's a BO2.
But this can only be detected  after the start of second game.
Anyone has better idea?

I believe the GC call for requestMatchDetails contains some series information.

GC call for requestMatchDetails contains same information as GetMatchHisotory API with league_id set, which lacks the type of BO2.
For BO1/BO2 series_id, series_type will all be 0.
For BO3/BO5, there will be a series_id set, and series type will be 1 for BO3 and 2 for BO5.

Unfortunately, I don't know a whole lot about this, but if you investigate and want to share your findings, it would be appreciated!
@Crazy-Duck is the node-dota2 expert and might have some idea on where the information might be found.

As far as I've been able to determine, there exists no such thing as a BO2 in the Dota2 client, nor the GC. BO2's are played either as two consecutive BO1's or as a BO3 that's cut short after the second game...

Closing since there is no action pending.  Feel free to update if you find out anything more!


As a single administrator of a small NPOs, I can find pairings of a volunteer to an elderly by keyword

Resolved by #98


Remove gist:Address from ranges of gist:toAgent and gist:fromAgent. Fixes #391.

There were someValuesFrom restrictions on gist:Message that repeated the union ranges in toAgent and fromAgent. Rather than removing Address from these as well, I replaced the restrictions with minCardinality restrictions, since there's no sense in duplicating the ranges in the restrictions.
The definition of Message was and is out of sync with the specified ranges is reflected in a new issue.


Required allowance for Function-Call Keys

Hi,
After this PR:
https://github.com/near/near-cli-rs/pull/330
allowance attribute became required, but the documentation states that this attribute is optional:
https://docs.near.org/concepts/protocol/access-keys#function-call-keys
allowance (Optional): The amount of NEAR allowed to be spent on gas. If omitted, the key can consume unlimited as gas

Which implementation is correct?

@pustovalov good catch. We had an internal discussion and thought that nobody would actually need that unlimited allowance any time soon. @FroVolod will jump on it now to introduce proper parsing of “--allowance unlimited”, cause absent CLI option is ambiguous


Fine-grained Coda status

What?
Node status (via coda client status) is very confusing and not detailed enough. It is hard to determine the state of the system with this one global status. It would be more useful to present the status of all subsystems.
Why now?
Brandon wasted 2 hours on Tuesday debugging something that would have been solved instantly. Node operators interacting with Coda get confused. Further, folks building on top of the protocol get stuck as well. Seems like it's worth investing in fixing this for velocity's sake.

I suggest we go about fixing this by first formalizing our daemon as a series of concurrent state machines (in an RFC). If we can identify the various concurrent subsystems (block production, snark verification, network pools, frontier processor, etc..), then we can formalize a high level state machine (representing status of the subsystem only; not internal state). We can use this the implement statuses for each of our subsystems, and have a more robust mechanism in coda client status (and graph status) to give granular statuses for each subsystem. It will also just be nice to have a single place of reference for the subsystems and their states.

Not in coda status but advanced coda status
Start with Block producer and then work down a prioritized list of other components.


Create pending state for tasks

Lemme know your thoughts on something like this.
Lint failures are due to max-complexity.

Obsoleted by #15


fix NPE and other exceptions thrown when work fails to process before work execution

StreamingModeExecutionContext requires a call to start() in order to work correctly.
If an exception is thrown during work execution before a call to start(), its possible that internal StreamingModeExecutionContext members are null.
Fix NPE in calls to invalidateCache() made w/o a call to start().
Also prevent ComputationWorkExecutor.invalidate() from crashing the worker.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @arunpandianp

@scwhittle ready for merge thank you!

Precommit failure is pubsub auth issue, seems unrelated.


Kazakhstan TZ change

The Feb 2024a release notes mentions:

Kazakhstan unifies on UTC+5.  This affects Asia/Almaty and Asia/Qostanay which together represent the eastern portion of the country that will transition from UTC+6 on 2024-03-01 at 00:00 to join the western portion.

When is the data expected to be updated/released with this change?

The changes from 2024a were included in tzinfo-data v1.2024.1 (released on 1 February). There will be a tzinfo-data release for each IANA Time Zone Database release, usually within a day or two.
The old tzinfo 0.3 branch has also been updated with the 2024a changes. TZInfo 0.3.x isn't really supported any longer with only occasional releases. You can obtain the latest 0.3.x code and data by loading the tzinfo gem from git in your Gemfile:
gem 'tzinfo', git: 'https://github.com/tzinfo/tzinfo.git', branch: '0.3'

@philr sorry, could you clarify a bit. We're currently using tzinfo (2.0.5) and tzinfo-data (1.2024.1)(latest) and we will need to downgrade to 0.3 in order to use the latest data? Bumping tzinfo-data independently doesn't mean we get the latest IANA updates, we still have to wait for them to be update in the tzinfo gem?

You don't need to downgrade.
You have the latest data tzinfo v2.0.5 and tzinfo-data v1.2024.1.

Prior to tzinfo v1.0.0, the data used to be bundled with tzinfo. Version 1.0.0 and onwards will obtain data from either tzinfo-data or the system zoneinfo files.

Got it! So the offset I'm seeing for Astana, Kazakhstan looks like it's still showing GMT+6 instead of the new GMT+5. So something is off.
pry(main)> TZInfo::Data::Version::TZDATA
=> "2024a"
pry(main)> ActiveSupport::TimeZone['Astana']
=> #<ActiveSupport::TimeZone:0x0000ffff69fd5f70 @name="Astana", @tzinfo=#<TZInfo::DataTimezone: Asia/Dhaka>, @utc_offset=nil>
pry(main)> ActiveSupport::TimeZone['Astana'].now.utc_offset
=> 21600
pry(main)> ActiveSupport::TimeZone['Astana'].tzinfo.identifier
=> "Asia/Dhaka"

=> #<ActiveSupport::TimeZone:0x0000ffff69fd5f70 @name="Astana", @tzinfo=#<TZInfo::DataTimezone: Asia/Dhaka>, @utc_offset=nil>

ActiveSupport's Astana time zone is mapped to Asia/Dhaka (Bangladesh). That seems to be incorrect (and that time zone didn't change in 2024a).
Asia/Almaty and Asia/Qostanay are the Kazakhstan time zones that have changed. With the previous v1.2023.4 tzinfo-data release (2023d), Asia/Almaty is on UTC+6 prior to and after 1 March 2024:
TZInfo::DataSource.get
#=> #<TZInfo::DataSources::RubyDataSource: tzdb v2023d, tzinfo-data v1.2023.4>
tz = TZInfo::Timezone.get('Asia/Almaty')
#=> #<TZInfo::DataTimezone: Asia/Almaty>
tz.to_local(Time.utc(2024,2,29,12,0,0))
#=> 2024-02-29 18:00:00 +0600
tz.to_local(Time.utc(2024,3,1,12,0,0))
#=> 2024-03-01 18:00:00 +0600

With v1.2024.1 (2024a), Asia/Almaty switches from UTC+6 to UTC+5:
TZInfo::DataSource.get
#=> #<TZInfo::DataSources::RubyDataSource: tzdb v2024a, tzinfo-data v1.2024.1>
tz = TZInfo::Timezone.get('Asia/Almaty')
#=> #<TZInfo::DataTimezone: Asia/Almaty>
tz.to_local(Time.utc(2024,2,29,12,0,0))
#=> 2024-02-29 18:00:00 +0600
tz.to_local(Time.utc(2024,3,1,12,0,0))
#=> 2024-03-01 17:00:00 +0500

The commentary in the Time Zone Database states that Asia/Almaty is for most locations in Kazakhstan including the Akmola region containing/surrounding Astana. I think ActiveSupport's Astana time zone should therefore actually be mapped to Asia/Almaty. You'll need to raise an issue on the rails/rails project.

Thank you!


Blank screen

Hello, very nice project.
I ran my local version (npm install) and all I get after I click the icon from the menu bar is a white screen. Any ideas how to debug this? I'm not watching the src since it got an error when installing via 'npm run watch'.
Thanks.
Peter

Hello @piclez! You can find all the instruction you need to run the project locally at https://github.com/ekonstantinidis/gitify#development .
Particularly make sure you run:
npm run build  # OR `npm run watch` which also builds the project
npm start  # To start the app

One more thing that will allow you to login, is to use the client id and secret key as explained in the above link (just copy, paste and re-build).
Let me know if you need further help!

Thanks @ekonstantinidis! I just had to install grunt-cli.
Really cool!
One last question, when I run via npm start and close and run it again the settings like "On Click, Mark as Read" are lost. Is this something it will work only when running the App?
Thanks.

Hello @piclez ! I'm not 100% but yes I think the settings are being erased every time you are running npm start. I can confirm that if you package your app then your settings will be stored.


chore(AutoControlledComponent): align API of trySetState() with React's

This PR is a slice of changes for AutoControlledComponent from #3452. The same changes were applied for Stardust UI, too.

This PR updates the trySetState() method of AutoControlledComponent to have the same API as setState() in React class components.

Codecov Report

Merging #3731 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #3731   +/-   ##
=======================================
  Coverage   99.83%   99.83%
=======================================
  Files         175      175
  Lines        3120     3120
=======================================
  Hits         3115     3115
  Misses          5        5

Impacted Files
Coverage Δ

src/modules/Search/Search.js
99.54% <100%> (ø)
:arrow_up:

src/modules/Rating/Rating.js
100% <100%> (ø)
:arrow_up:

src/modules/Dropdown/Dropdown.js
100% <100%> (ø)
:arrow_up:

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 2c71341...71b26ba. Read the comment docs.


feat: trpc 11

I upgraded the code to work with trpc 11.
fixed some uws invalid response access error too but as stated in my other PR #4 I know you are scared about changing the way the ws adapter given by the trpc team but I swear this is tested and better.
the actual state of this PR is deployed at trpc-uwebsockets-next and I will soon update with my uws-ish version if you want to test.
Moreover, with the actual state we can't set headers in the context while upgrading WS if we are staying with this version.

Thanks for the PR. I will review the changes in a bit. I dont understand the last part. The issue of unable to set headers with the responseMeta? The unit tests show that it works.
And I'm totally fine with changing the implementation, but in my opinion it would be better for long-term upgradability to keep it sync with other adapters. As long as the tests pass, and it makes the library better, I'm totally on board with changes.
Cheers!

Yes, I agree with you but as trpc themselves said this is kinda rough I think we could write this adapter more like the uws way.
But there is no responseMeta with the applyWSHandler, my need is to set cookie and/or rate limiter response while upgrading to the websocket too

I don't think it's a good idea to do anything rather then upgrade the connection. The initial request is to negotiate upgrade to websocket with 101 response.
I am not aware of any ws implementation that allows to set cookies, as it's outside of the websocket protocol.
This is why the browser does not allow sending custom headers with the request and does now allow see response headers. It only sends the cookies.
You can accomplish what you need with a separate http request.

Sending headers back in the upgrade is a common things supported by all WebSocket servers.
It is a different thing than changing headers in the client, of course it shows response headers

But you are unable to read these response headers in javascript.
This is out of spec. Why implement features which are not implemented anywhere else. The solution to your problem is do a separate http request.

I don't want to read it with javascript. I just want to add to this library a feature that have all websockets server out there, but no problem, I think I have to start a separate repository

Can you please explain why sending cookies is needed during the upgrade?
Implementing features just to have them is not sustainable. Keeping technical complexity low is more important. Also, why implement something that can be done in a simpler way, via an http request.
I have also dealt with cookies before and it can be a pain to work with. Properly sending multiple cookies takes a lot of effort and is very error prone.

For example, my clients need to know their rate limiting state. I agree with you for the complexity part, but a client shouldn't send more requests to know their limits. Its not that hard too, the createContext just need to be in the upgrade part. that way the context handler can send headers. I already have all of these in production but I was thinking more people could benefits from this. I tested in my staging environment to replace my adapter to this lib and everything was falling apart, I thought it could be good to contribute, but I will start my version aside, and will link to you to have a look if you want.

I have added these changes, they are now at  feat/v11 branch. The code works, but it uses v10 deprivated apis. Namely:
import {
  AnyRouter,
  callProcedure,
  getErrorShape,
} from '@trpc/server';

I've marked them with comment // FIXME depricated
Also this import does not look nice:
import type { MaybePromise } from '@trpc/server/dist/@trpc-core-unstable-do-not-import-this-please';

You can use the beta version via npm install trpc-uwebsockets@beta

Yes, totally agree, but they are still using this for their adapters too, maybe we have to wait more for this

Btw, I see another issue, you register 2 onAborted callback and uws only trigger one https://github.com/romanzy313/trpc-uwebsockets/blob/1245dad9b0942ff4a2d86a2dc09d8136411aeec1/src/utils.ts#L59 , I added the aborted = true on this one and totally remove the other to not have crash on production


[BUG] Harvester v0.2.0 dashboard layout broken on Safari 14.1.1

Describe the bug
Layout broken on macOS Safari 14.1.1
To Reproduce
Steps to reproduce the behavior:

Open harvester dashboard in Safari 14.1.1

Expected behavior
Layout the dashboard correctly
Environment:

Harvester ISO version: v0.2.0
Underlying Infrastructure: VirtualBox 6.1 on macOS 11.4

Additional context

Haven't check against master branch. Feel free to close if it is already fixed.

Tested in safari on mac os Version 14.1.1 (166<IP_ADDRESS>.4) and harvester version master-07efe71c-head. Verified as fixed.


[flann]Upgrade version to 1.9.1 and fix build error.

Upgrade version to 1.9.1 and fix build error.
Since the flann dependent port lz4 has a file conflict problem(xxhash.h), this PR needs to wait for the #6735 merge to merge.
Related: #6618.

Due to this branch has been deleted, close this PR and reopen a new PR #6931.


parseObject does not work for parseLiteral

When I pass a string to to a json field as a variable, I get a correct error message
Variable \"$a\" got invalid value \"foo\"; Expected type JSONObject. JSONObject cannot represent non-object value: foo

But when I do the same thing inline, without using a variable, I get this error
Expected type JSONObject, found \"foo\"; Cannot read property 'forEach' of undefined

the parseObject function expects a ast node

well, it works, but the error sort of sucks


Extra graphics modes - 384x288 with 8x8 cell based 3bpp colouring

Currently we have a 50x36 text buffer consuming 3,600 bytes, where we take the first and last colour as a border.
I propose a 384*288 1bpp framebuffer mode which takes colours from the text mode colour attributes. This would add 13,824 bytes but could be enabled on a line-by-line basis. There would be a slow-copy routine for blitting in arbitrary size bitmap into an arbitrary location, and a fast-copy routine for blitting a bitmap a multiple of 8 wide (an integer number of u8s) into a location that was a multiple of 8. The latter would be useful for writing characters to the display. We'd need to add an 8x8 font in addition to the 8x16 font for text mode, as we have 288 rows with line-doubling, not the 576 rows of text mode.
The function to enable graphics mode could take a buffer that was some multiple of 48 bytes and an odd scan-line to stitch the buffer in at. This would allow split-screen modes, with text at the top and bottom and graphics in the middle. The switch for text vs graphics is performed once per line and so isn't expensive, and both graphics and text ultimately go out to the same SPI FIFOs through the same colouring routines so graphics mode shouldn't be slower. If anything, without the font lookup it might be quicker.
Total memory used = 17,424 bytes max.

1bpp framebuffer implemented. Needs drawing routines.

Closed in favour of #23


🐛 Presigned url lambda doesn't reject unsupported formats

Describe the bug.
The presigned URL lamdba checks if the file suffix is empty, and returns 400, but it doesn't return a 400 if the format is unsupported, so in theory you can attempt to upload a JSON or another currently unsupported format and it won't break until later on in the processing.
To Reproduce
No response
Expected Behaviour
Return a 400 if the extension is not csv.
Additional context
The impact isn't so bad at the moment, as the data extractor script filters out anything that isn't csv.

Is the a list of currently supported formats anywhere?

@mitchdawson1982 it's just CSV right now


Rename scanner token methods

Also rename a method from formatting scanner.
This commit doesn't rename internals or usages.
Edit: setTokenEnd actually resets all 3 token positions. I'm still thinking of a better name for it.
Edit: 2: I'm going with resetTokenState
Fixes my inability to remember which scanner method refers to what edge of a token.

@typescript-bot run DT


Unresolved identifier 'FIRDynamicLinkComponents'

Trying to use Dynamic Links in Swift 3 project. I've pod installed 'Firebase' and 'Firebase/DynamicLinks' as well as 'import Firebase' in my viewController. Copied the code in the documentation.
Getting the error:

Use of unresolved identifier 'FIRDynamicLinkComponents'

on this line:
let components = FIRDynamicLinkComponents(link: link, domain: domain)
Is Dynamic Links working in Swift3/iOS10?

Can you upload your project?

My repo is private but I just made this one with the same configuration as mine: https://github.com/MarksCode/TestProj

The sample you uploaded doesn't compile, but after deleting all the code with errors and running pod update I'm able to build and run the project just fine.
If you haven't already, update your cocoapods installation to 1.2.1 and try again.

@morganchen12 I updated to 1.2.1  and ran pod update, my Dynamics Links is now v1.4. However, it still doesn't work. Can you check out my repository by any chance please?

I did.  This isn't a valid way of initializing a dictionary, nor does it convey any type information.
Sometimes the Xcode gives stale or meaningless error messages, but once you fix all your syntax errors your code should compile fine.

In my actual project's repository I fixed the dictionary syntax errors. The only ones I'm getting are the original error I posted. On the line let components = FIRDynamicLinkComponents(link: link, domain: domain) I'm getting Use of unresolved identifier 'FIRDynamicLinkComponents'. If I give you access rights to my repo can you please take a look?

No, please don't do that. GitHub's issue tracker isn't really for 1:1 help. If you've got an issue and can post its cause here, then I'm happy to help you as the solution will serve as a reference for others who run into the same issue, but if you seek help in private then suddenly that reference doesn't exist and it's much less valuable time spent for open source maintainers.
In your case the dictionary syntax issue wasn't the only issue, but the first of many syntax issues.
If you clean (Cmd+Shift+K) and rebuild, does Xcode produce more useful errors?

Clean build worked for me

Hello , I am also having the same issue. I could not found the class 'FIRDynamicLinkComponents' while integrating FirebaseDynamicLink in iOS. Actually  'FIRDynamicLinkComponents'  class is not available in the framework also. My pod version is 1.2.1. Please help me with this issue

@bpdubey87 I've had no luck solving it, let me know if you find out.

@MarksCode  I just solved the issue in following step:-

GO to project path where pod file is present.
run 'pod update' in terminal
again add    pod 'Firebase/DynamicLinks' in pod file
run command 'pod install'
You will see one extra class 'FDLURLComponents.h' inside the framework.

If you are having still issue then I am attaching class here :-
FDLURLComponents.h.zip

@bpdubey87 I'll try that. I thought I already installed pod 'Firebase/DynamicLinks' before but maybe they changed something.


AttributeError: 'NoneType' object has no attribute 'group'

Using version 2015.11.13, download on Fedora 22 fails as of today:
youtube-dl --verbose 'https://www.youtube.com/watch?v=qWmicId9ldk'
[debug] System config: [u'--prefer-free-formats']
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'https://www.youtube.com/watch?v=qWmicId9ldk']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.11.13
[debug] Python version 2.7.10 - Linux-4.2.6-200.fc22.x86_64-x86_64-with-fedora-22-Twenty_Two
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] qWmicId9ldk: Downloading webpage
[youtube] qWmicId9ldk: Downloading video info webpage
[youtube] qWmicId9ldk: Extracting video information
[youtube] {43} signature length 49.43, html5 player en_US-vflFEzfy7
[youtube] qWmicId9ldk: Downloading player https://s.ytimg.com/yts/jsbin/player-en_US-vflFEzfy7/base.js
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 744, in _extract_signature_function
cache_res = res(test_string)
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 796, in
return lambda s: initial_function([s])
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 254, in resf
res, abort = self.interpret_statement(stmt, local_vars)
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 55, in interpret_statement
v = self.interpret_expression(expr, local_vars, allow_recursion)
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 135, in interpret_expression
self._objects[variable] = self.extract_object(variable)
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 220, in extract_object
fields = obj_m.group('fields')
AttributeError: 'NoneType' object has no attribute 'group'
(caused by AttributeError("'NoneType' object has no attribute 'group'",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 744, in _extract_signature_function
cache_res = res(test_string)
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 796, in
return lambda s: initial_function([s])
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 254, in resf
res, abort = self.interpret_statement(stmt, local_vars)
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 55, in interpret_statement
v = self.interpret_expression(expr, local_vars, allow_recursion)
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 135, in interpret_expression
self._objects[variable] = self.extract_object(variable)
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 220, in extract_object
fields = obj_m.group('fields')
AttributeError: 'NoneType' object has no attribute 'group'
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/youtube_dl/YoutubeDL.py", line 661, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/common.py", line 290, in extract
return self._real_extract(url)
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 1356, in _real_extract
encrypted_sig, video_id, player_url, age_gate)
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 827, in _decrypt_signature
'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 744, in _extract_signature_function
cache_res = res(test_string)
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/youtube.py", line 796, in
return lambda s: initial_function([s])
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 254, in resf
res, abort = self.interpret_statement(stmt, local_vars)
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 55, in interpret_statement
v = self.interpret_expression(expr, local_vars, allow_recursion)
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 135, in interpret_expression
self._objects[variable] = self.extract_object(variable)
File "/usr/lib/python2.7/site-packages/youtube_dl/jsinterp.py", line 220, in extract_object
fields = obj_m.group('fields')
AttributeError: 'NoneType' object has no attribute 'group'
(caused by AttributeError("'NoneType' object has no attribute 'group'",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

You are using an outdated version of youtube-dl. YouTube changed their interface after the version you were using was release, so you need to update to the current version of youtube-dl. Refer to our FAQ if you have trouble updating.


fix: missing-radio-disabled-error

Hello,
Not sure if this is missed by mistake
it could be raised on iOS 14+, calling requestTechnology when the NFC toggle is off in the system settings
Thanks,

thanks @whitedogg13, could you also release a new version? :)

@moony-chen sure, v3.14.12 has been released~


Can you provide the NaturalQuestions test dataset?

The LongLLMLingua evaluate performance on "NaturalQuestions", but I cannot find any source to download it, can you provide this test dataset?
(I try to communicate the author of "Lost in Middle", but I haven't received a reply yet.)

Hi @czwlines, you can find the dataset in their repo.

Hi @czwlines, you can find the dataset in their repo.

thanks!!!


NIFI-2789 Add JMS properties to FlowFile attributes on receive in ConsumeJMS

Closing in favor of #1027 which includes the properties enhancement too.


[Android/iOS][Controls - Slider] The Slider disable state doesn't match design

Steps to Reproduce:

Launch app
From Burger menu select Controls
Tap Slider > Cupertino
Notice slider disabled state

Current behaviour

Expected behaviour

Repro rate
100%
Affected platform(s):
web
Android
iOS
Version & devices
Chrome
Samsung Galaxy A50 - 9
iPhone 6S - 14.0.1

Verified on build  1.0.0 (675)


rock64/mali optimised libsdl2-dev packages

Could you please add a rock64 optimised and easily installable libsdl2-dev package(s) to your ubuntu repo please?
libsdl2-dev from the official ubuntu repos fails to install because it depends upon libgles2-mesa-dev which in turn tries to install libegl1-mesa-dev which contains an egl.so that clashes with the mali egl library.
Here are some apps and games we could build and hopefully run under rock64 Linux if we have rock64 mali linked/optimised libsdl2-dev packages:
An open source Dreamcast emulator that supports GLES2 accel:
https://github.com/reicast/reicast-emulator
A PSP emu that does the same:
https://www.ppsspp.org/
Hurrican, then open source Turrican update / tribute:
https://sourceforge.net/projects/hurrican/
mupen64(plus)
https://github.com/mupen64plus
and maybe even Dolphin - the open source Gamecube and Wii emulator, which again supports GLES
https://dolphin-emu.org/

@danboid FYI - the emulation apps you've listed (except dolphin, because it's too hardware demanding) are all available in the recalbox release and run using GLES.
https://forum.pine64.org/showthread.php?tid=6351

Hi mrfixit!
Thanks for pointing out recalbox! I'd not heard of it before.
I've just given it a quick go but I'll give my feedback on the pine64 forum as we're getting OT.

The libmali rockcpu GPU driver package conflicts with some of the xorg dev packages. In order to install the xorg dev packages or anything that may require those packages (such as libsdl2-dev) you first need to forcefully remove the mali driver:
sudo dpkg --purge --force-all libmali-rk-utgard-450-r7p0

After installing all your required xorg etc dev packages, you ca forcefully re-install the Mali driver:
sudo apt-get -o Dpkg::Options::="--force-overwrite" install libmali-rk-utgard-450-r7p0

@danboid - definitely true. I outlined some of the install steps to force override package installs in my retropie writeup on the pine64 forums. Not a lot can be done about it tho, because there are libraries and files that are included in multiple packages that overlap the Mali package. That's why in the simplified Debian build I made available (https://github.com/mrfixit2001/debian_builds) I didn't install Mali as a package. I installed the headers and libraries and links manually. This way other packages can be cleanly installed. Then when you're done with installing all your packages I provided a script to run that fixes any links that got overwritten by other packages.  My builds are different from ayufan's in a number of ways, and the kernel is primarily geared towards emulation and media playback. Ayufan's are much better at other solutions that this board can be utilized for. But I hope this provides some insights.

@mrfixit2001
Your rock64 Debian build sounds interesting so I have a few questions:
Are you going to upload the source (for your patches) to GH or elsewhere?
Do you (plan to) have a repo for rock64/mali optimised packages such as mpv, ffmpeg, SDL and the custom kernel source/headers etc?
Have you got playback of 4K h264 files working reliably with mpv under your distro?
Does SDL (1 and 2) gles2 'just work' with the mali driver or does it require patching to get working properly?
Thanks

@danboid
At some point yes, I'll be propping up repos for all my stuff. Maybe not the debian image because I kept that pretty "stock", so frankly it's really just the debian bootstrapper with a minimal file system overlay (for mali and my boot-script) and a partition creation script which includes my kernel.
The source for my recalbox port needs to go into recalbox's gitlab (just waiting on them to provide a branch), but the rest will be on my github eventually.
I've got a robust retropie port I'm working on right now with a lot of custom patches that optimize emulator performance. Once that package is complete I'll be sharing it all out. I'm trying to include my custom patches into my recalbox release as I go as well, but the two builds don't always use the same emulator versions.
I don't plan to have dedicated repos for smaller libraries, because things like SDL, FFMPEG, and RKMPP are not my specialty. For the media libraries I'm using patches from the LE repo, as they are optimized: https://github.com/LibreELEC/LibreELEC.tv/tree/master/packages/multimedia
SDL, however, can be a bit special, depending on your implementation. For retropie support I have found using the retropie SDL repo is best. Recalbox goes directly to the libsdl source and then adds some patches specifically to support their back-end.
One piece of advice... when compiling from source, while patches are important at times, the "magic" is truly in the build flags. So don't just concentrate on the patches and diffs, read the packages for those compiler settings.


Webfont smoothing for FireFox

In _typography.scss, it would probably make sense to include -moz-osx-font-smoothing: grayscale; right after -webkit-font-smoothing: antialiased;, to support FireFox.
Related: http://maximilianhoffmann.com/posts/better-font-rendering-on-osx & http://stackoverflow.com/questions/11459746

Actually, we are looking to remove all font smoothing. https://github.com/thoughtbot/bitters/pull/180 A lot of font smoothing options is dependent on a number of factors including what app you are using and the display your using is using to see the site.
One of the bigger factors for bitters is that we don't know what fonts a designer/dev is going to want to use with their site. They may use a font that has good hinting so it is difficult to make blanket rules like 'all antialiased all the time'. For now we've decided to remove all smoothing.
@drtimofey let me know what you think.

With #180 merged, can this be closed? Should we add -moz-osx-font-smoothing just to the button styles, as we do with -webkit-font-smoothing?

Closing


Diners club

Hi
I'm trying to validate Diners Club number provided by Stripe https://stripe.com/docs/testing#cards (3056 9309 0259 04) but it's not working. I guess the right group pattern will be:
groupPattern: /(\d{1,4})?(\d{1,4})?(\d{1,4})?(\d{1,2})?/
thanks

Hi, take a look at some previous issues about Stripe's invalid test cards, I choose to do strict validation in the interest of validating real cards:
https://github.com/bendrucker/angular-credit-cards/issues/134
If you think there's a genuine card that won't validate feel free to report here:
https://github.com/bendrucker/creditcards-types


ENH: Add NGFF 0.4 JSON Schema validation test

Based on the work of @sbesson :pray:

Thanks for the heads up @thewtex. With https://github.com/ome/ngff/pull/113 now merged, https://ngff.openmicroscopy.org/0.4/schemas/image.schema and other schemas should now start resolving and I assume the downstream packages can start consuming these.
As mentioned in https://github.com/ome/ngff/issues/58, there are a few scalability and usability downsides with dynamically retrieving remote schemas  for eac validation. I suspect there will be a use case for distributing these schemas as library resources  but we have not yet established the best language-agnostic way to structure this.

Thanks for the heads up @thewtex. With https://github.com/ome/ngff/pull/113 now merged, https://ngff.openmicroscopy.org/0.4/schemas/image.schema and other schemas should now start resolving and I assume the downstream packages can start consuming these.
As mentioned in https://github.com/ome/ngff/issues/58, there are a few scalability and usability downsides with dynamically retrieving remote schemas  for eac validation. I suspect there will be a use case for distributing these schemas as library resources  but we have not yet established the best language-agnostic way to structure this.

Thanks for the heads up @thewtex. With ome/ngff#113 now merged, https://ngff.openmicroscopy.org/0.4/schemas/image.schema and other schemas should now start resolving and I assume the downstream packages can start consuming these.

@sbesson wonderful, thank you!
Migrating to this in #27

As mentioned in ome/ngff#58, there are a few scalability and usability downsides with dynamically retrieving remote schemas for eac validation. I suspect there will be a use case for distributing these schemas as library resources but we have not yet established the best language-agnostic way to structure this.

Yes, packages that could be used offilne would be nice.


Revert "Added TCP_USER_TIMEOUT auto-detection"

Reverts grpc/grpc#23401
breaks internal android targets

Fix forward in https://github.com/grpc/grpc/pull/23425


Add support for operator sidecar

Adds support for integration with the operator sidecar.
This makes an addition to the domain resource by adding a monitoring-exporter element, which can specify both the exporter image and the configuration.
Note that, at present, only connecting to the WLS plaintext port is actually working. We need to update the client truststore to handle certificates.

I'm curious if it's possible to enable the monitoring exporter configuration using helm chart values similar to how it's done for the ELK integration?

I'm not familiar with our ELK integration, but this pattern appears to work and is easy. There is nothing that Helm needs to be involved in, and the operator does need to know about the monitoring exporter to configure it.

I'm curious if it's possible to enable the monitoring exporter configuration using helm chart values similar to how it's done for the ELK integration?

I'm not familiar with our ELK integration, but this pattern appears to work and is easy. There is nothing that Helm needs to be involved in, and the operator does need to know about the monitoring exporter to configure it.

The Helm install is, of course, for the operator. @ankedia, are you thinking of a sort of global switch to enable the monitoring exporter with every domain? I'd like to keep what we have and then see if customers are asking for a configuration option that spans domains.

I'm curious if it's possible to enable the monitoring exporter configuration using helm chart values similar to how it's done for the ELK integration?

I'm not familiar with our ELK integration, but this pattern appears to work and is easy. There is nothing that Helm needs to be involved in, and the operator does need to know about the monitoring exporter to configure it.

The Helm install is, of course, for the operator. @ankedia, are you thinking of a sort of global switch to enable the monitoring exporter with every domain? I'd like to keep what we have and then see if customers are asking for a configuration option that spans domains.

[ANIL] Yes, I was thinking of a sort of global switch to enable monitoring exporter with basic configuration (similar to ELK integration). The users can then customize/add to the existing configuration for monitoring exporter.

I'm curious if it's possible to enable the monitoring exporter configuration using helm chart values similar to how it's done for the ELK integration?

I'm not familiar with our ELK integration, but this pattern appears to work and is easy. There is nothing that Helm needs to be involved in, and the operator does need to know about the monitoring exporter to configure it.

The Helm install is, of course, for the operator. @ankedia, are you thinking of a sort of global switch to enable the monitoring exporter with every domain? I'd like to keep what we have and then see if customers are asking for a configuration option that spans domains.

[ANIL] Yes, I was thinking of a sort of global switch to enable monitoring exporter with basic configuration (similar to ELK integration). The users can then customize/add to the existing configuration for monitoring exporter if they wanted.

As it works now, the exporter is only enabled IF the user specifies a configuration. What other customizations are you envisioning?

I'm curious if it's possible to enable the monitoring exporter configuration using helm chart values similar to how it's done for the ELK integration?

I'm not familiar with our ELK integration, but this pattern appears to work and is easy. There is nothing that Helm needs to be involved in, and the operator does need to know about the monitoring exporter to configure it.

The Helm install is, of course, for the operator. @ankedia, are you thinking of a sort of global switch to enable the monitoring exporter with every domain? I'd like to keep what we have and then see if customers are asking for a configuration option that spans domains.

[ANIL] Yes, I was thinking of a sort of global switch to enable monitoring exporter with basic configuration (similar to ELK integration). The users can then customize/add to the existing configuration for monitoring exporter if they wanted.

As it works now, the exporter is only enabled IF the user specifies a configuration. What other customizations are you envisioning?
I was thinking that the user will only set some value (say enableMonitoringExporter) to true in values.yaml when installing the operator Helm chart to enable the exporter. This will automatically add the required configuration to the domain resource. However, if a user specifies the configuration then that value in values.yaml will be ignored.

Anyways, I'm ok with what Ryan suggested above to keep what we have and then see if customers are asking for a configuration option that spans domains.


cl: build initAfter

fix https://github.com/goplus/llgo/issues/668

After apply this PR, the problems of init$after are fixed, but code in https://github.com/goplus/llgo/issues/668#issuecomment-2275600391 can't be linked:
ld64.lld: error: undefined symbol: github.com/goplus/llgo/x/foo.(*Promise).Done
>>> referenced by /var/folders/f2/88rgt2bx533_m89qy6pqqp8w0000gn/T/c6a93e01eae93812b32dda4baca85cf18d7c45de514cecd3ee3d11140cc6e01f-d-e105c4.o:(symbol main.init$after+0xf28)
>>> referenced by /var/folders/f2/88rgt2bx533_m89qy6pqqp8w0000gn/T/c6a93e01eae93812b32dda4baca85cf18d7c45de514cecd3ee3d11140cc6e01f-d-e105c4.o:(symbol main.init$after+0xf24)

ld64.lld: error: undefined symbol: github.com/goplus/llgo/x/foo.(*Promise).Async
>>> referenced by /var/folders/f2/88rgt2bx533_m89qy6pqqp8w0000gn/T/c6a93e01eae93812b32dda4baca85cf18d7c45de514cecd3ee3d11140cc6e01f-d-e105c4.o:(symbol main.init$after+0xcd8)
>>> referenced by /var/folders/f2/88rgt2bx533_m89qy6pqqp8w0000gn/T/c6a93e01eae93812b32dda4baca85cf18d7c45de514cecd3ee3d11140cc6e01f-d-e105c4.o:(symbol main.init$after+0xcd4)

Maybe this is another problem.


libcudnn (R5) not found in library path

new gtx 1070, installed cuda 8.0 and cudnn 5.1 ( echo $LD_LIBRARY_PATH gives /usr/local/cuda-8.0/lib64 and the files are in there) yet I get this error using cudnn as backend:
84: /home/rayset/torch/install/share/lua/5.1/cudnn/ffi.lua:1597: 'libcudnn (R5) not found in library path.
Please install CuDNN from https://developer.nvidia.com/cuDNN
Then make sure files named as libcudnn.so.5 or libcudnn.5.dylib are placed in your library load path (for example /usr/local/lib , or manually add a path to LD_LIBRARY_PATH)

I've tried all day, I'm on ubuntu 16 so I had to mess with gcc and g++.
Firstly I installed cudnn 5.1, then I added (but not removed the old ones) cudnn 5.0. could this be the problem?
here's what is in my cuda folders:
cuda-8.9/include: http://pastebin.com/1wuDgPmp
lib64: http://pastebin.com/bMKuXCk6
the files with the same name should all be from cudnn 5.0
here's my path:
/usr/local/cuda/lib64:/usr/local/cuda-8.0/lib64:/home/rayset/torch/install/lib:/home/rayset/torch/install/lib:
thanks in advance.

hi there, the error message that others suffered with is not the same as yours. I am actually unclear why your error happens.
Regardless, here's a solution:
export CUDNN_ROOT="/usr/local/cuda-8.0/lib64/libcudnn.so.5" # you can maybe add this line into ~/.bashrc for future use
luarocks install cudnn

To test that everything is successful:
th -lcudnn -e "print(cudnn.version)"

Thank you a lot! I can't believe it was something this simple.
I will report this fix over to neural style, I saw at least 3 other users with this problem. maybe the issue is in the tutorial over there :P
I'm really impressed with cudnn memory usage,worth every euro.

@soumith .... yes i followed your instruction ...yes i execute the follow commond
th -lcudnn -e "print(cudnn.version)"
and got the results... as attached....

But again i got the same error when run the code in matlab...


Update README.md

Found this while browsing the source
Related to https://github.com/symfony/demo/pull/1185

Sorry I missed this one. Merged! Thanks Antoine.


QA cypress automation sam lopez

@samfinch14 Hi Sam!
Thanks for the work on this small take home exercise. You don't need to create merge requests to the main repository, you can keep the work on your forked repository and when you're ready you can just provide the link to us and we'll take a look!

Hi @fonsleenaars sorry I accidentally pointed the PR on this repo supposedly it should be on the forked one. I'll give you the link once ready thank you!


feat: Add currency_code field to FieldContent struct

Title
Add currency_code field and validation to FieldContent struct
Type of Change

[x] New feature

Description
This PR introduces a currency_code field to the FieldContent struct, allowing the system to handle fields that represent monetary values more accurately. The field adheres to the ISO 4217 standard, ensuring correct and consistent use of currency codes.
Additionally, validation logic has been implemented to ensure only valid ISO 4217 codes are accepted. Unit tests have been added to cover the new field and its associated validation.
Testing

Verified the correct handling of valid and invalid currency codes in the FieldContent struct.
Added unit tests to check proper serialization and validation.
Tested edge cases where the currency_code field is missing or contains invalid values.

Impact

Affects all systems interacting with the FieldContent struct that deal with monetary data.
Minor performance impact due to added validation logic.
Backward-compatible as the currency_code field is optional and defaults to nil.

Additional Information
This change introduces stricter validation for currency-related fields but does not affect existing non-monetary data.
Checklist

[x] My code adheres to the coding and style guidelines of the project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings

closed: #147


Main delay calculation workflow: Look Direction is unused

The look_dir parameter as provided in a YAML file is never used. It is accessed in one spot to validate that it is either "left" or "right", and never again. A vscode all files search for the term "look_dir" only produces results from inside other data structures and that one validation check, and none where the look_dir from a YAML run config gets used.
Do we not use Look Direction anymore, or is it being left out somewhere on accident?
Desktop

RAiDER git tag:
commit 2a348023801fc1f7fb21427d3ae63150530e2382 (HEAD -> dev, tag: v0.5.2, upstream/main, upstream/dev, upstream/HEAD)
Merge: 223d862 2b7190c
Author: Jeremy Maurer<EMAIL_ADDRESS>Date:   Mon Jul 15 11:54:29 2024 -0500
    Merge pull request #670 from dbekaert/dev
    v0.5.2
OS: Arch Linux <IP_ADDRESS>-microsoft-standard-WSL2 on Windows 10

Not all sensors have same look direction. Will defer to @jlmaurer if this was a placeholder for the future. E.g. NISAR/ CSK etc.

@dbekaert @garlic-os yes this will depend on the sensor. Right now everything is right-looking, but very soon we will have a left-looking sensor (NISAR). We may want to take a look at the workflow and make sure the look direction is properly carried through.


HAI-2274 Create separate johtoselvitys from modal dialog

Description
Separate johtoselvitys without hanke being created first is done by opening a modal dialog and entering users phone number and work name. Email is pre-filled but can be edited. Creating johtoselvitys then works in similar way as creating hanke.
Jira Issue: https://helsinkisolutionoffice.atlassian.net/browse/HAI-2274
Type of change

[ ] Bug fix
[x] New feature
[ ] Other

Instructions for testing

Use yarn start-msw to use API mock as the backend for this is not yet implemented
Check that the dialog can be opened by clicking "Tee johtoselvityshakemus" linkbox in home page, "Tee johtoselvityshakemus" link in top bar or "täytä hakemus" link in the first page of hanke form
Fill the form in the dialog and click "Luo hakemus" button
You should end up in johtoselvitys form where the work name is filled

Checklist:

[x] I have written new tests (if applicable)
[x] I have ran the tests myself (if applicable)
[ ] I have made necessary changes to the documentation, link to confluence
or other location:

Other relevant info
Please describe here if there is e.g. some requirements for this change or
other info that the tester/user needs to know.

Tested all three ways to create application. All work but the phone number filled in modal does not come on the application form.

I was thinking that it probably is not needed to be filled in application form as those own information fields will be removed from the form.

Tested all three ways to create application. All work but the phone number filled in modal does not come on the application form.

I was thinking that it probably is not needed to be filled in application form as those own information fields will be removed from the form.

Ah, yes, you're right!


[bug] pouch inspect can not get valid cpuquota

Ⅰ. Issue Description
Through pouch inspect  cmd, we can't  get a valid CpuQuota
Ⅱ. Describe what happened
When we create pouch container by CRI, we assigned CpuQuota, but after created , the CpuQuota we get by  pouch inspect  is zero.

Ⅲ. Describe what you expected to happen
The cpuQuota which get by pouch inspect cmd same to what we assigned.
Ⅳ. How to reproduce it (as minimally and precisely as possible)

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

pouch version (use pouch version):

GitCommit:       633a2aa
GoVersion:       go1.9.1
KernelVersion:   3.10.0-327.ali2010.rc2.alios7.x86_64
Os:              linux
Version:         1.0.0
APIVersion:      1.24
Arch:            amd64
BuildTime:       2018-10-11T08:23:00+00:00

OS (e.g. from /etc/os-release):

Kernel (e.g. uname -a):

Install tools:

Others:

Can you post container create config, you can found that in /var/log/pouch @changyaowei

Can you post container create config, you can found that in /var/log/pouch @changyaowei

I will give it to you in private.

I check the pouch logs, and found that during we were creating the container, we also got a request UpdateContainerResources , the update request parameters:
time="2018-12-05T01:06:26.354598534+08:00" level=info msg="UpdateContainerResources for "cdb744a994dfba300d1813db003b1de9a7f42d7339b8164173fe399b5f7250d0" with &LinuxContainerResources{CpuPeriod:0,CpuQuota:0,CpuShares:0,MemoryLimitInBytes:0,OomScoreAdj:0,CpusetCpus:0-7,CpusetMems:,DiskQuota:map[string]string{},BlkioWeight:0,BlkioWeightDevice:[],BlkioDeviceReadBps:[],BlkioDeviceWriteBps:[],BlkioDeviceRead_IOps:[],BlkioDeviceWrite_IOps:[],KernelMemory:0,MemoryReservation:0,MemorySwappiness:nil,Ulimits:[],}"

the CpuQuota is 0 and it is considered valid, so the container's CpuQuota was updated to 0

Any update on this? @HusterWan @fuweid @rudyfly

Any update on this? @HusterWan @fuweid @rudyfly

@allencloud fix this problem is simple but before that @changyaowei should fix first. Am I right?


Improve iterators over Move and Post

Move and Post currently uses vector iterators, which might be not as efficient. It would be nice to isolate this either to custom iterator or extract to some template/type.

I share your scepticism about improving efficiency. The purpose of this issue as I understand it is truly simply abstracting the concrete implementation from the base class to make playing with the implementation details easier. I am not sure that we can achieve anything with this here, but I am open to ideas.

Well, what do you mean by abstracting the conrecte implementation? The struct Move has its own function begin() which currently redirects the call to the underlying vector. If someone one to reimplement Move, then he indeed need to reimplent this function as well according to his imlementation. I am little bit confused which other extraction/abstraction do you mean here?

If I understand it correctly, the idea behind this issue is to create different implementations for iterators, either as separate functions, or as a separate classes implementing the same interface (begin(), end(), back(), …). They can be then easily replaced, either in the body of Move::begin() or changing the implementation for class instances called in Move::begin(). It remains to be seen whether that is beneficial to us at all.

Well, you basically means to define Move::iterator which will currently only redirect everything to the underlying vector (or reimplement behaviour of vector). It is a long term investment to have clearly defined interface than something currently needed imho.
On the other hand, if someone come with a new Move implementation he will probably implement the iterators anyway (without need to be guided by interface which would  be created as a part of this issue).

It is a long term investment to have clearly defined interface than something currently needed imho.
On the other hand, if someone come with a new Move implementation he will probably implement the iterators anyway (without need to be guided by interface which would be created as a part of this issue).

I see it the same.

I edited the comment, so I hope it is clear that it is about efficiency of the iterators and not about some interface changes, that are just byproduct of the PR. Hence, I'm ending my involvement in this discussion. Howgh.

This issue should be resolved by our newest refactorization of all iterators, including iterators over current moves, transitions represented as Trans structures and more.


[Comment,  email Notifications] User doesn't receive notifications in case of chosen option 'daily', 'twice a day' for it

Environment: Windows 10, Chrome 127.0.6533.89, 64-bit.
Reproducible: always.
Build found: 25.10.2024
Preconditions
The page https://www.greencity.cx.ua/#/events is opened.
The user is logged in.
Steps to reproduce
Steps to reproduce
1.User 1 chooses 'daily' for notification in the setting of the profile and create own event.
2. User 2 comments the event of User 1.
3.User 1 checks the notifications on email next day.
4. User 1 chooses 'twice a day' for notification in the setting of the profile.
5.User 2 comments the  event of User 1 again.
6.User 1 checks the notifications on email till the end of the day.
Actual result
The user doesn't receive notifications on email about comments next day, when he/she has status 'daily'. The user doesn't receive notifications on email about comments till the end of the day, but he/she has status 'twice a day'. These statuses work as status 'never'.
Expected result
With 'daily' status for getting notifications user gets notifications on email about new comments at least next day. With 'twice a day' status user gets notification on email about new comments at least till the end of the day.
User story and test case links
https://github.com/ita-social-projects/GreenCity/issues/4665

Bug ready for retesting


feat: allow setting a cardinality given the count in the persisted data is compatible

Pull Request Checklist
Task Description/Number

Issue Number: DEV-1563

Add check that the current cardinality is included in the new cardinality or the persistent entities are compatible with the new cardinality.
Introduce PredicateRepository.
Move all queries to folder twirl/org/knora/webapi/messages/twirl/queries/sparql/v2/.

Basic Requirements
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix: represents bug fixes
[ ] Refactor: represents production code refactoring
[x] Feature: represents a new feature
[ ] Documentation: documentation changes (no production code change)
[ ] Chore: maintenance tasks (no production code change)
[ ] Style: styles updates (no production code change)
[ ] Test: all about tests: adding, refactoring tests (no production code change)
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR change client-test-data?

[ ] Yes (don't forget to update the JS-LIB team about the change)
[x] No

@seakayone is the PR title correct or instead of in there should be if?

@seakayone is the PR title correct or instead of in there should be if?

The "in" is correct actually.

There is still no documentation, but I assume you are going to add it later?

yes


On restart kernel, reconsider having the "Yes, and don't ask again" option...

Testing microsoft/vscode#131209
I'm not sure why we added the "Yes and don't ask again" choice when I restart a kernel. This seems like generally a bad idea, since restarting kernels can be a lossy proposition.
I think it's fine if we keep the setting, but I don't think we should advertise it.

The button should navigate the user to the settings UI page but not actually flip the setting value.

Closing as there haven't been any upvotes on this issue

Suggestion:
Due to https://github.com/microsoft/vscode/issues/163729  we might want to always ask the user & be consistent with Jupyter as well (i.e. remote the option do not show again)

Closing this issue, hasnt received any upvotes


Feature/pxblue 2527 update rebrand changelog

Fixes # https://jira-prod.tcc.etn.com/browse/PXBLUE-2527

Changes proposed in this Pull Request:

Update changelog and package

do not use Eaton internal links in your PR description


KeyError: 'scaled_focal_length is not a file in the archive' in 4.Transfer SMPL step

Hi I follow the instruction trying to build up my own motion data. In the 4.Transfer SMPL step. I encounter the following error:
CACHE_DIR_4DHUMANS: /home/nelson/.cache/4DHumans
Lightning automatically upgraded your loaded checkpoint from v1.8.1 to v2.2.2. To apply the upgrade to your files permanently, run `python -m pytorch_lightning.utilities.upgrade_checkpoint ../.cache/4DHumans/logs/train/multiruns/hmr2/0/checkpoints/epoch=35-step=1000000.ckpt`
WARNING: You are using a SMPL model, with only 10 shape coefficients.
['images', 'smpl_results']
Traceback (most recent call last):
  File "/opt/conda/envs/champ/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/conda/envs/champ/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/home/nelson/champ/scripts/data_processors/smpl/smpl_transfer.py", line 103, in <module>
    zip(result_dict_list["smpl"], result_dict_list["camera"], result_dict_list["scaled_focal_length"], driving_paths)
  File "/opt/conda/envs/champ/lib/python3.10/site-packages/numpy/lib/npyio.py", line 260, in __getitem__
    raise KeyError("%s is not a file in the archive" % key)
KeyError: 'scaled_focal_length is not a file in the archive'

How do I solve the issue?

Same problem.
It seems to be a problem with smooth_smpls.py, because smooth_smpls.py does not save scaled_focal_length, but generate_smpls.py saves scaled_focal_length, which means that smooth_smpls.py lost the information of scaled_focal_length.
I also noticed that the old version of generate_smpls.py did not save scaled_focal_length. It seems that smpl_transfer.py matched the old version.

It's a bug. We will fix it in the following couple of days.

for smpl_outs, cam_t, file_path in tqdm(
zip(result_dict_list["smpl"], result_dict_list["camera"], driving_paths)
):
img_fn, _ = os.path.splitext(os.path.basename(file_path))
result_dict = {key: value for key, value in result_dict_first.items()}
result_dict["smpls"] = smpl_outs
result_dict["cam_t"] = cam_t
if args.view_transfer:
scaled_focal_length = reference_dict["scaled_focal_length"]
result_dict["cam_t"] = reference_dict["cam_t"]
result_dict["scaled_focal_length"] = scaled_focal_length

It works.


Custom textarea  fields with multi-line content not possible

Custom textarea fields cannot be handled by the plugin. Something like
$@Multiline="
#Content

Lorem **ipsum** dolor sit amet...

But hey, it's _Markdown_.
"@$

should be possible, but isn't. It always fails.

Fixed by 1.5.0


Fix scroll_to_line ignores line separation

scroll_to_line will not scroll to the correct position if the line provided is part of a wrapped paragraph. This fixes that.

Thanks!


GTK webkit weirdness

Running a basic "Hello World" app in Linux I notices a bunch of strange stuff going on:

Multiple-second load times for the content after the window is initialized (might be inherent to platform, not sure if can be fixed)
Weird menus: App has two menus in the menubar: "First menu" and "Second menu". First menu gives a number of options like "About App", "Quit", etc., but they do nothing. Second menu creates a strange blank menu that has low width and big height.
Right-clicking in the window shows a menu with greyed out "Forward", "Stop", and "Backward", as well as working "Reload" and "Inspect Element". Hitting reload breaks the app.

The menus might be intended, but reload breaking stuff is clearly not.

Thanks for the report!

I've identified why 1) is happening - GTK/Windows don't receive a MainEventsCleared on startup.
Menus are a result of poor config merging, this is sorted out in the master branch
The context menu on right-click is a result of the platform/Tao (not inserted by us) and should be disabled in release mode of your app. I know the inspect menu goes away in release menu. Forward/back is the result of poor config merging.

The one thing I don't exactly know how to fix is reloading the page, so I think we need to override that manually.

Running a basic "Hello World" app in Linux I notices a bunch of strange stuff going on:

Multiple-second load times for the content after the window is initialized (might be inherent to platform, not sure if can be fixed)
Weird menus: App has two menus in the menubar: "First menu" and "Second menu". First menu gives a number of options like "About App", "Quit", etc., but they do nothing. Second menu creates a strange blank menu that has low width and big height.
Right-clicking in the window shows a menu with greyed out "Forward", "Stop", and "Backward", as well as working "Reload" and "Inspect Element". Hitting reload breaks the app.

The menus might be intended, but reload breaking stuff is clearly not.

Can you check is #84 works for you?
git checkout https://github.com/DioxusLabs/dioxus.git
git pull
git checkout jk/windows-lag
cargo run --example readme --features "desktop"

It should load immediately now.

Can you check is #84 works for you with respect to startup lag?

It does, now there is no lag between starting up the WebView and displaying the app.

Menus are a result of poor config merging, this is sorted out in the master branch
The context menu on right-click is a result of the platform/Tao (not inserted by us) and should be disabled in release mode of your app. I know the inspect menu goes away in release menu. Forward/back is the result of poor config merging.

This is great news!

The one thing I don't exactly know how to fix is reloading the page, so I think we need to override that manually.

Then I think we should probably rename the issue and keep it open until this particular quirk is resolved.
Anyway, thank you for the prompt answer and for writing this library in general. I'm looking forward to using it, and potentially even contributing when I have more free time.

Reload context menu is now disabled in production apps. We don't have a way of customizing the context menu, so it functionally serves no purpose in desktop apps beyond the default actions for things like selected text.
This functionality can be enabled/disabled through the cfg.


feat: prevent native assets disabling

:books: Linear Ticket :books:
LIQ1192

I think we were supposed to fix that, instead of preventing disabling?


Pictures of vehicles for LEOs

Describe the feature
For LEOs to be able to identify vehicles better, it would be nice to have the ability to see images of vehicle models. There are also two variants of how to approach this feature:

Just to be able to upload/define vehicle image inside /admin/values/vehicle, that would be visible to LEOs inside the modal with Searching vehicles
Additionally to have possibility to upload custom image of the vehicle for LEOs. If there is none, show the default image defined in the first point.

Additional Context
No response

Are you able to elaborate a bit on your first bullet point?

Are you able to elaborate a bit on your first bullet point?

Sure - basic thing is being able to define default picture for each vehicle model type. That is must-have so officers actually can see how that vehicle looks like. If you feel like it, then you can upgrade this feature by adding possibility to upload custom image to each vehicle record which will then override the default picture stored for that model. So officers can take photos of a vehicle by themselves to have more accurate picture of it.


FEAT(Git-Clone): Add git@ URLs

Add Github and Gitlab when using git@ URLs.

Hi @djarbz, do you plan to come back to this? I see we have linting issues.

@matifali thanks for the reminder.
Should be G2G now.

@michaelbrewer Could you review, too, as you are the original author? Thanks.


Custom task based execution

Changed d2 execution to a custom task to take advantage of 'jump to error' (#36)
Eliminated the need for temp files (#39)
Hot key for show command only active when d2 document is active (#41)

Don't forget to run the 'webpack --watch' task.  I just spent 15min wondering why my changes weren't running.

could you also run yarn prettier -w .?

It's been prettied.


Ensure that the initial notification for Results is always .Initial

There was logic which attempted to ensure this was the case, but it wasn't
tested, wasn't actually used, and didn't actually work.
Fixes #3501.

@bdash

👍


DllNotFoundException: FirebaseCppApp-9_5_0

DllNotFoundException: FirebaseCppApp-9_5_0

I am working on Windows 10 building my game for android and I am facing this issue:
DllNotFoundException: FirebaseCppApp-9_5_0
Firebase.AppUtilPINVOKE+SWIGExceptionHelper..cctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/android_unity/armeabi-v7a/app/swig/Firebase.App_fixed.cs:3909)
Rethrow as TypeInitializationException: The type initializer for 'SWIGExceptionHelper' threw an exception.
Firebase.AppUtilPINVOKE..cctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/android_unity/armeabi-v7a/app/swig/Firebase.App_fixed.cs:3929)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.AppUtilPINVOKE' threw an exception.
Firebase.AppUtil.SetLogFunction (Firebase.LogUtil+LogMessageDelegate arg0) (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/android_unity/armeabi-v7a/app/swig/Firebase.App_fixed.cs:4636)
Firebase.LogUtil..ctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/app/src/LogUtil.cs:81)
Firebase.LogUtil..cctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/app/src/LogUtil.cs:37)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.LogUtil' threw an exception.
Firebase.FirebaseApp..cctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/android_unity/armeabi-v7a/app/swig/Firebase.App_fixed.cs:1897)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.FirebaseApp' threw an exception.
AnalyticsHandler.Awake () (at Assets/AdsScripts/AnalyticsHandler.cs:18)
I am using unity 2020.3.38
I have tried reimporting, deleting Firebase from the project then importing again also I have tried deleting the library folder nothing helped me.
Does anyone have solutions for windows OS.

Hi @BadranRaza,
Thanks for reporting this issue. Could you confirm if the device you're working on makes use of an updated C++ Redistributable? Also, does the error message appear when playing the Unity editor or running the Android build (or both)?

the error appears on both devices but the issue has been resolved by installing
https://all-in-one-runtimes.updatestar.com/en


Update CONTRIBUTING.md to reflect recent changes

Updates documentation of install / watch / release based on changes to
nix/ dir.

Updates documentation of install / watch / release based on changes to
nix/ dir.
tz1dk5tsD3vr1ib7XY2CULdWa81vMBbVbjDj


Do you want me to add GitHub Actions?

If you want, I can contribute some advanced CI to your repository in a PR. Let me know if you want that.

Thank you for the offer. Some automation would be helpful, I think.

Do you want me to send in just hassfest and HACS, with flake8, or with flake8 and automatic formatting?

Puh...I don't know. This is all new to me. I think I can run flake8 in my virtual environment before pushing to github. So I don't have an idea, if this would make sense in Github. Maybe it's easier if there is an automatic formatting, so I don't have to do it by myself. What do you think?
For hassfest I found an instruction, so I could do this on my own.
Maybe the HACS would be helpful? Right now I have problems with a PR there.
What I really need is something, which makes me a description for a release, so that I have all the changes documented in there.

Try this out 😃
https://github.com/release-drafter/release-drafter

Thank you


Setup JHS directories

During testing, we noticed that the job history was created by 'yarn' user with 770 permissions. This means the 'mapred' user, which runs the JHS, cannot read these files. This adds execute blocks to create these directories and give them more permissive permissions to allow the JHS to read them.

LGTM