Background music

Can we have the same featured u had on soundbox for background music?
We were told by the elders that bkground music is recommend in the letter for sound. It be very handy to have the feature like on soundbox with lower volume.

@talkingdragon thanks for feedback. there is a background music function in JW Library - I won't try to reproduce functions that are provided by JWL.

Antony,
Can you enlighten me as to where this function is in JWL? I have been looking but can only see how to play one song at time..
Thanks
Mike

On 29 Sep 2018, at 09:51, Antony Corbett<EMAIL_ADDRESS>wrote:
@talkingdragon https://github.com/talkingdragon thanks for feedback. there is a background music function in JW Library - I won't try to reproduce functions that are provided by JWL.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/AntonyCorbett/OnlyM/issues/52#issuecomment-425628666, or mute the thread https://github.com/notifications/unsubscribe-auth/ApK_I1BzY6peyQTtthvGaiewLhq0gg3Xks5ufzSXgaJpZM4W_HtU.

Uff made my day with that name @pickels-the-cat when I media tab and in audio. If u select a section u want so music with chorus at top u got the play button and it randomly plays that section. Wich is grate.. Except it full volume wich is rly annoying in out setup and its a difrent tab so when time start u rushing to the meeting tab.. Wich are laptop.. Don't know how to rush.. Hahaha

Thanks, but that isn’t really a random play. It will “Play All” so will always do this from the first song and you will hear this at every meeting as you can’t start the play back from anywhere else, and if you do you just get that song played and then it stops.
Is there anyway you know to “Play All” in a random way?
Thanks
Mike

On 29 Sep 2018, at 14:52, talkingdragon<EMAIL_ADDRESS>wrote:
Uff made my day with that name @pickels-the-cat when I media tab and in audio. If u select a section u want so music with chorus at top u got the play button and it randomly plays that section. Wich is grate.. Except it full volume wich is rly annoying in out setup and its a difrent tab so when time start u rushing to the meeting tab.. Wich are laptop.. Don't know how to rush.. Hahaha
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/AntonyCorbett/OnlyM/issues/52#issuecomment-425646852, or mute the thread https://github.com/notifications/unsubscribe-auth/ApK_I5pv_BGXE2ADyd34bw9NoTmzvtwwks5uf3szgaJpZM4W_HtU.

If u select a section u want so music with chorus for e.g. at top u got the play button and it randomly plays that section. Wich is grate.. Except it full volume wich is rly annoying in out setup and its a difrent tab so when time start u rushing to the meeting tab.. Wich are laptop.. Don't know how to rush.. Hahaha

Can't you lower the volume in the notebook? (You don't use a mixer to control all audio devices, do you?)
Also you can go in the "media" page in the "Meetings" section, do what you need in other sections of the app and when you click on "Meetings" again you will already be in the media page.

Thanks.. I have never noticed that and you are right it does work.
Thanks for reading the instructions, always helps!
Mike

On 29 Sep 2018, at 15:28, TizianoNoto<EMAIL_ADDRESS>wrote:
If u select a section u want so music with chorus for e.g. at top u got the play button and it randomly plays that section. Wich is grate.. Except it full volume wich is rly annoying in out setup and its a difrent tab so when time start u rushing to the meeting tab.. Wich are laptop.. Don't know how to rush.. Hahaha
Can't you lower the volume in the notebook? (You don't use a mixer to control all audio devices, do you?)
Also you can go in the "media" page in the "Meetings" section, do what you need in other sections of the app and when you click on "Meetings" again you will already be in the media page.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/AntonyCorbett/OnlyM/issues/52#issuecomment-425649334, or mute the thread https://github.com/notifications/unsubscribe-auth/ApK_I9DtuHo5uoUKJXCxkgn8ifv_agzNks5uf4OegaJpZM4W_HtU.


drag and drop

Users can now drag and drop anywhere on the page.  This builds upon the EXIF pull request.

This includes #177

Thanks, Ray.  I'm going to leave these for the moment, because I expect
Nathan will want to do a more critical review than I'm willing or able to
do.  (I shouldn't have bothered with the lightbox branch on origin -- it's
so easy to pull your branch directly and test it as is before merging the
PR.)
On Sun, Sep 6, 2015 at 3:13 PM, Raymond Suelzer<EMAIL_ADDRESS>wrote:

This includes #177
https://github.com/MushroomObserver/mushroom-observer/pull/177
—
Reply to this email directly or view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/178#issuecomment-138131309
.

All good.
From: Jason Hollinger<EMAIL_ADDRESS>Sent: Sunday, September 6, 2015 6:17 PM
To: MushroomObserver/mushroom-observer<EMAIL_ADDRESS>Cc: Raymond Suelzer<EMAIL_ADDRESS>Subject: Re: [mushroom-observer] drag and drop (#178)
Thanks, Ray. I'm going to leave these for the moment, because I expect
Nathan will want to do a more critical review than I'm willing or able to
do. (I shouldn't have bothered with the lightbox branch on origin -- it's
so easy to pull your branch directly and test it as is before merging the
PR.)
On Sun, Sep 6, 2015 at 3:13 PM, Raymond Suelzer<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

This includes #177
https://github.com/MushroomObserver/mushroom-observer/pull/177
—
Reply to this email directly or view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/178#issuecomment-138131309
.

—
Reply to this email directly or view it on GitHub https://github.com/MushroomObserver/mushroom-observer/pull/178#issuecomment-138132171 .  https://github.com/notifications/beacon/ABHzFcJE1TFdApyQzst69ACA3a06lwM0ks5ovLLIgaJpZM4F4rT3.gif

Apparently I can't push my conflict fix to this branch, so I created a new pull.  Don't know if that's the right approach or not.  In any case I've not been able to get this functionality to work locally.  I'll followup with details on the mo-dev mailing list.


Detecting closed eye from webcam feed

Thanks for this awesome library.
I want to detect when user closes the eyes. I highly appreciate if I get code example.

I am not sure there is an API in face-api for this. All the relevant examples possible are given in the examples folder. Not seen one for eye lid detection. This is more aimed at the face itself.

You can use face landmark for eyes, and then find the vertical distance between the eyelids to recognize blink ore closed eyes.

You can use face landmark for eyes, and then find the vertical distance between the eyelids to recognize blink or closed eyes.

No the model doesn't recognise whether eye is closed. The landmarks just show the position of eye.

You can use face landmark for eyes, and then find the vertical distance between the eyelids to recognize blink or closed eyes.

No the model doesn't recognise whether eye is closed. The landmarks just show the position of eye.

I am facing this issue now. The distance doesn't make too much difference when eyes are open and then closed. Just wondering what you did to address it.


Update views.view.policy_definitions.yml

We have more than one content type using the Policy Definitions vocabulary – yet I did not see a ticket for enabling and updating the existing Policy Definitions vocabulary.
The help text on those fields reference [/policy/definitions].  I created a redirect to /agency-directives/definitions.
The Policy Definitions view is on EPA@Work but is disabled. The view:
•	was enabled
•	page path was updated to /agency-directives/definitions
•	The data export path updated to agency-directives/definitions/export

This was a hotfix on PROD.

Thanks Jess looks good to merge.


SPStorkController dismiss delegate method

How we can identify that current Presented SPStorkController controller get dismissed.
somehow the  parent controller view will appear method is not calling when dismissed the  SPStorkController controller.
Thanks

Please, see SPStorkControllerDelegate


Revert "util/dofile.pl: only quote stuff that actually needs quoting"

This wasn't a good solution, too many things depend on the quotes being
there consistently.
This reverts commit 49cd47eaababc8c57871b929080fc1357e2ad7b8.

If I find the issue that got me to make that change in the first place, I'll fix it differently...

I'm gonna wait for the CIs, okay?

Merged.
master:
00701e5ea84861b74d9d624f21a6b3fcb12e8acd Revert "util/dofile.pl: only quote stuff that actually needs quoting"
1.1.0:
7ee2a43069913fb7c444c656048996ea92cc465e Revert "util/dofile.pl: only quote stuff that actually needs quoting"

Merged.
master:
00701e5ea84861b74d9d624f21a6b3fcb12e8acd Revert "util/dofile.pl: only quote stuff that actually needs quoting"
1.1.0:
7ee2a43069913fb7c444c656048996ea92cc465e Revert "util/dofile.pl: only quote stuff that actually needs quoting"


Beyond consolidated metadata for V3: inspiration from Apache Iceberg

I just reviewed the V3 spec. As with V2, the core spec does not address how to deal with unlistable stores. In V2, we developed the semi-ad-hoc "consolidated metadata" approach. I know there is already an issue about this vor V3 (#136), but I am opening a new one with the hope of broadening the discussion of what consolidated metadata can be.
Background: What is Apache Iceberg
I have recently been reading about Apache Iceberg.  Iceberg is aimed at tabular data, so it is not a direct alternative or competitor to Zarr. Iceberg is not a file format itself (it can use Parquet, Avro, or ORC for individual data files). Instead, it is a scheme for organizing many data files individual into a larger (potentially massive) single "virtual" table. In addition to the table files, it tracks copious metadata about the files. In this sense, it is similar to Zarr: Zarr organizes many individual chunk files into a single large array.
For folks who want quickly come up to speed on Iceberg, I recommend reading the following documents in order:

What is Iceberg? Features and Benefits (via Dremio)
Iceberg Spec

Architecturally, these are the main points

This table format tracks individual data files in a table instead of directories. This allows writers to create data files in-place and only adds files to the table in an explicit commit.
Table state is maintained in metadata files. All changes to table state create a new metadata file and replace the old metadata with an atomic swap. The table metadata file tracks the table schema, partitioning config, custom properties, and snapshots of the table contents. A snapshot represents the state of a table at some time and is used to access the complete set of data files in the table.
Data files in snapshots are tracked by one or more manifest files that contain a row for each data file in the table, the file’s partition data, and its metrics. The data in a snapshot is the union of all files in its manifests. Manifest files are reused across snapshots to avoid rewriting metadata that is slow-changing. Manifests can track data files with any subset of a table and are not associated with partitions.
The manifests that make up a snapshot are stored in a manifest list file. Each manifest list stores metadata about manifests, including partition stats and data file counts. These stats are used to avoid reading manifests that are not required for an operation.

This diagram says 1000 words.

Another interesting part of the spec, regarding the underling storage system capabilities:

Iceberg only requires that file systems support the following operations:

In-place write – Files are not moved or altered once they are written.
Seekable reads – Data file formats require seek support.
Deletes – Tables delete files that are no longer used.

These requirements are compatible with object stores, like S3.
Tables do not require random-access writes. Once written, data and metadata files are immutable until they are deleted.

Within the data lake / warehouse / lakehouse world, you can think of Iceberg as an open-source alternative to Databricks Delta Lake. It can be used by many different data warehouse query engines like Snowflake, Dremio, Spark, etc.
Inspiration for Zarr
It doesn't make sense to use Iceberg directly for Zarr--it's too tied to the tabular data model. There are lots of interesting ideas and concepts in the Iceberg spec that I think are worth trying to copy in Zarr. Here is a list of some that come to mind
Manifests
Manifests are essentially files which list other files in the dataset. This is conceptually similar to our V2 consolidated metadata in that it removes the need to explicitly list a store. We could store whatever is useful to us in our manifests. For example, we could explicitly list all chunks and their sizes. This would make many operations go much faster, particular on stores that are slow to list or get files information.
Snapshots, Commits, and Time Travel
Iceberg tables are updated by simply adding new files and then updating the manifest list to point to the new files. The new state is registered via an atomic commit operation (familiar to git users). A snapshot points to a particular set of files. We could imagine doing this with zarr chunks, e.g. using the new V3 layout
data/root/foo/baz/c1/0_v0
data/root/foo/baz/c1/0_v1

where _v0 and _v1 are different versions of the same chunk. We could check out different versions of the array corresponding to different commits, preserving the whole history without having to duplicate unnecessary data. @jakirkham and I discussed this idea at scipy. (TileDB has a similar feature.)
Applying the same concept to metadata documents would allow us to evolve array or group schemas and metadata while preserving previous states.
Partition Statistics
If we stored statistics for each chunk, we could optimize many queries. For example, storing the min, max, and sum of each chunk, with reductions applied along each combination of dimensions, would sometimes allow us to avoid explicitly reading a chunk.
Different underlying file formats
Zarr V2 chunks are extremely simple: a single compressed binary blob. As we move towards the sharding storage transformer (#134, #152), they are getting more complicated--a single shard can contain multiple chunks. Via kerchunk, we have learned that most other common array formats (e.g. NetCDF, HDF5) can actually be mapped directly to the zarr data model. (🙌  @martindurant) We are already using kerchunk to create virtual zarr datasets that map each chunk to different memory locations in multiple different HDF5 files. However, that is all outside of any Zarr specification.
Iceberg uses this exact same pattern! You can use many different optimized tabular formats (Parquet, Avro, ORC) for the data files and still expose everything as part of a single big virtual dataset. Adopting Iceberg-style manifests would enable us to formalize this as a supported feature of Zarr.
Implementation Ideas
Having finally understood how storage transformers are supposed to work (thanks to https://github.com/zarr-developers/zarr-specs/pull/149#discussion_r942309150), I have convinced myself that the iceberg-like features we would want can all be implemented via a storage transformer. In pseudocode, the API might look like this
base_store = S3Store("s3://some-bucket")
zarrberg_store = ZarrIcebergStorageTransformer(base_store)

# check out a the latest version
zarrberg_store.checkout()
group = zarr.open_group(zarrberg_store)

# update some data
group['foo'][0, 0] = 1

new_version = zarrberg_store.commit()

#  check out some older version
zarrberg_store.checkout("abc123")
older_group = zarr.open_group(zarrberg_store)

The storage transformer class would do the work of translating specific storage keys requests into the correct paths in the underlying store (e.g. data/root/foo/0.0 ➡ data/root/foo/0.0_v2).
Summary
I'm quite excited about the possibilities that this direction would open up. Benefits for Zarr would be

Even better performance on slow-to-list stores
Time-travel and versioning
Ability to wrap other array file types explicitly, formalizing what we are already doing with Kerchunk
A solution for concurrent writes to the same chunk (one of the commits would fail and have to be retried with updated data)
Alignment with a widely adopted and successful approach in enterprise big data architecture

At the same time, I am aware of the large amount of work involved. I think a useful path forward is to look for the 90/10 solution--what could we imitate from Iceberg that would give us 90% of the benefits for 10% of the effort.

If I understand correctly, really what you are looking for is a key value-store adapter that handles versioning, snapshots, possibly packs things into a smaller number of files, and avoids the need for a list operation on the underlying storage.
This is actually precisely what is addressed by this proposal that we are working on implementing as part of tensorstore (but is not tied to tensorstore):
https://docs.google.com/document/d/1PLfyjtCnfJRr-zcWSxKy-gxgHJHSZvJ2y4C3JEHRwkQ/edit?resourcekey=0-o0JdDnC44cJ0FfT8K6U2pw#heading=h.8g8ih69qb0v
My understanding is that "storage transformers" were intended to apply only to the chunk data, not the metadata.  Since the goal here seems to be to also version the metadata and store it in the same way as the chunks, it seems like this would more appropriately be implemented at the key-value store and not need any particular integration with zarr, just that zarr would be used with it.

Thanks for sharing @jbms! I am currently reading and digesting that proposal.
One point of clarification: storage transformers can act on any of the items in the store (chunks AND metadata). For example, the sharding transformer (#152) declares explicitly that

This sharding transformer only adapts entries where the key starts with
data/root, as they indicate data keys for array chunks, see
:ref:storage-keys. All other entries are simply passed on.

Thanks for sharing @jbms! I am currently reading and digesting that proposal.
One point of clarification: storage transformers can act on any of the items in the store (chunks AND metadata). For example, the sharding transformer (#152) declares explicitly that

This sharding transformer only adapts entries where the key starts with
data/root, as they indicate data keys for array chunks, see
:ref:storage-keys. All other entries are simply passed on.

Currently, storage_transformers are specified as part of the array metadata, so the array metadata must be known and therefore it doesn't seem to make sense for it to affect anything other than data keys for that single array.  I suppose a different type of storage transformer could instead be specified in the root metadata, and could then also affect metadata keys.

Ah good point. I was confused by the comment above. I guess for this to work we would want the storage transformer in the root metadata.

Kerchunk would welcome being formalised as (part of) a zarrberg manifest, if that gets us a large fraction of the way to your goals. I think it can, since the storage layer can then express a change in the target of a key and could also be a place for per-chunk transformations if we want. That is not the same as a higher-level transformer; but see for example the ability to concat bytes from several references in preffs. A new version is a new references set (or some sort of delta scheme). Of course, it doesn't have to be via kerchunk, especially if you really want to have transformations a separately specified entity.
Note that kerchunk does also have aims with non-zarr data, such as the very directory-file structure of parquet/orc you mentioned, or even just finding valid byte start offsets in a CSV or zstd compressed file. Those are all related-but-not-the-same.

I wanted to pipe up and say I absolutely love this proposal, @rabernat :)

@rabernat can we have a huddle about this sometime soon. We are evaluating a feature at ESDIS level to better understand what a persistant zarr store would look like, you pointed me to this thread awhile back, we're now having more active conversations and I would like to better understand this proposal because it might exactly address our need.

@briannapagan , would be happy to take part too.
As an orthogonally connected topic, I have also made a client for reading actual iceberg datasets into dask (i.e., tabular as opposed to zarrish nd-arrays).

@briannapagan - sure thing. I'll ping you via email. For context, this idea is central to what Joe an I are now building at Earthmover.

I'd be interested in joining (if that's ok). Though no worries if not

me too!

also (always) happy to join.

I have a discussion with my colleague the other day about Time-travel and versioning for Zarr, this proposal is fantastic! We will be happy to contribute to the project if that's okay. @rabernat

Picking up this conversation as we have an open ticket at ESDIS. @christine-e-smit gave a great summary of our use case:

Setup:

Paul has a Zarr store in s3. This Zarr store currently has a data array called precipitation of shape 180x360x504 (latitude/longitude/time). The chunk size is 10x10x100, so there are 18x36x6 chunks.
Amy is using the Zarr precipitation array to run calculations. These calculations use multiple independent workers, which pull data from multiple zarr chunks at different times. The workers also sometimes read zarr metadata at different times. (Note: if Amy is using dask, dask will generally read the metadata once, calculate what tasks need to be run, and then run them on available workers. But Amy may have a complicated calculation that requires her to run dask more than once. So even if she is using dask, she may end up reading the metadata more than once.)

Scenario:

Paul gets data for a new time slice and needs to append this data to his existing Zarr array. With this new data added, the data array will have shape 180x360x505.

Paul resizes the precipitation array and sets precipitation[:,:,504] =  new_data. There are 18x36 chunks that must be updated with new data and at least one metadata object. His code (somehow) downloads what is currently in these chunks, updates them locally, and then copies them into s3. Note: it is not possible to update all these chunks simultaneously. s3 does not have this capability. So, in general, someone reading the chunks in s3 while Paul is writing them will get a mixture of old and new chunks.
Amy tries to run her calculations. Some of her workers read the zarr metadata before the resize and some read it afterwards. In addition, some workers read the chunks before they have been updated and some read them afterwards. Amy's code has no way of knowing that Paul is in the middle of updating data. Her code fails because it is getting inconsistent shape information. Or, even if all the workers happen to see the same shape, she gets a weird answer because some workers got data chunks before they were updated and some got data chunks after they were updated.

We've had tangent discussions in pangeo-forge with some solutions mentioned including consolidated-metadata, and @rabernat pointing out that the core issue is an ACID transaction to update the Zarr store.

You want to make changes to multiple files, but you don’t want those changes to become visible to the users until the change is complete; otherwise users see an inconsistent state.

I am proposing another discussion so we can try and sync these two ongoing conversations.
For those interested in joining a discussion with NAsA folks, please fill in this doodle by end of day Friday March 17th: https://doodle.com/meeting/participate/id/aQkYRPMd

As part of the tensorstore project we have developed a key-value store database format called OCDBT (Optionally-cooperative distributed B+tree) that can sit as an adapter between an array format like zarr and the underlying base filesystem / object store.
This format is designed to support versioning and copy-on-write snapshots, which could be used in various ways to solve the scenario described above:

An entire database, which may consist of one or more zarr arrays including both their json metadata and the chunks, is versioned; every batch of writes creates a new versino, which can be accessed as a static snapshot.
Distributed pipelines can be configured to read a specific version (indicated by a generation number) rather than reading the floating latest version.  This ensures that they operate on a consistent snapshot.
You can "save" specific snapshots of individual arrays or of the entire database by "copying" arbitrary prefixes of the key space to a new prefix.  This can be used to create e.g. named versions of the precipitation array, or to perform the writes on a temporary copy of the precipitation array before replacing the original precipitation array with the new version.

You can find a high-level description of the format and its motivations here:
https://docs.google.com/document/d/1PLfyjtCnfJRr-zcWSxKy-gxgHJHSZvJ2y4C3JEHRwkQ/edit?resourcekey=0-o0JdDnC44cJ0FfT8K6U2pw#heading=h.8g8ih69qb0v
And a description of the current on-disk format here:
https://google.github.io/tensorstore/kvstore/ocdbt/index.html#storage-format

@jbms I don't have your contact information but also for anyone else able to join here is the meeting information for tomorrow 2PM eastern:
Forward Stream Processing + Zarr Stores
Monday, March 20 · 2:00 – 3:00pm
Google Meet joining info
Video call link: https://meet.google.com/shq-zenj-xqm
Or dial: (US) +1<PHONE_NUMBER> PIN: 691 877 052#
More phone numbers: https://tel.meet/shq-zenj-xqm?pin=2854704778130

Some of us in the fusion energy research world have started using zarr (see [mastapp.site](https://mastapp.site if you’re curious!). For this data repository, we’re looking at using lakefs to handle versioning, but this proposal outlines a much better and more lightweight way to version our data.
I’ll be following this with keen interest and would love to have an idea on timelines and progress.

@NathanCummings : lakeFS versions individual files within a set, I think, which would make it hard to use for this kind of thing

Snapshots, Commits, and Time Travel
Iceberg tables are updated by simply adding new files and then updating the manifest list to point to the new files. The new state is registered via an atomic commit operation (familiar to git users). A snapshot points to a particular set of files. We could imagine doing this with zarr chunks, e.g. using the new V3 layout
data/root/foo/baz/c1/0_v0
data/root/foo/baz/c1/0_v1
where _v0 and _v1 are different versions of the same chunk. We could check out different versions of the array corresponding to different commits, preserving the whole history without having to duplicate unnecessary data. @jakirkham and I discussed this idea at scipy. (TileDB has a similar feature.)
Applying the same concept to metadata documents would allow us to evolve array or group schemas and metadata while preserving previous states.

@martindurant if something like this were implemented, it would suit our needs nicely.

Absolutely, version control as described in this thread sounds like what you might want (cc @rabernat , if you want to comment). tiledb has yet another take on amending array data in-place.

Yes, tiledb is another option that we considered before deciding to use zarr. It’s still something I’m keeping in the back of my mind.

Continuing on the https://github.com/zarr-developers/zarr-specs/issues/314#issuecomment-2356633740 by @rabernat since more relevant here

FYI, we are planning on open sourcing the solution we have built at Earthmover later this fall.

any specifics on what components would be open-sourced/what they would allow to do?

I'm sure the community would be very excited to hear about what's to come from Earthmover, and interest could be stirred by such specifics; but it's hard for developers (not me!) to reveal too much, especially if licenses have not yet been updated in all the places. "later this fall" sounds pretty soon to me, it being already mid-September.

Our Arraylake platform already offers transactions, serializable isolation, and version control for Zarr data, with the feature set described here (and more technical details here). The way this works today requires both object storage AND interaction with our REST API. With our forthcoming open source release, we have figured out how to do with without the REST API, using only object storage.
Happy to chat in person if you're interested in hearing more details<EMAIL_ADDRESS>

More than two years after writing this ticket, we finally built it.
https://icechunk.io/
💯 open source (Apache 2.0)


推論時間的FPS定義問題？

作者您好，根據論文的敘述 inference 時使用一張RTX 4090，執行速度為FPS 9.0，
因為環周影像一次是6張相片同時由Dataloader輸入，
想請問這裡只的FPS 9.0，是把6張環周相片視為一張影像？
還是輸入的6張環周影像算為6張影像？

我目前使用RTX 4080執行一次6張相片視為一個影像的效率約為1.5秒，
大約為FPS 0.667，因此想確認是否符合論文描述，謝謝。

是环视六张图像一起输入，可以使用tools/benchmark.py测试FPS。

I think some layers like deformable aggregation better works at fp32, other layers can be converted to fp16.

Thanks for your help and suggestions. I have figured it out, and now I am using the RTX 4080 for inference. Its performance is approximately 3-4 FPS, which is lower than my expectation of 6.3 FPS (calculated as fps 9 * 0.7).
Have you released an FP16 quantization version?
I sincerely appreciate your efforts.

The model is trained with fp32 weights, you can run model with fp16 using torch.autocast.


fix: Add samples folder as test root

I'm sorry, I forgot to add samples as test root the tests there has been ignored.
Signed-off-by: Jakub Koci<EMAIL_ADDRESS>

Codecov Report

Merging #215 (40d4b01) into main (6004441) will increase coverage by 3.51%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #215      +/-   ##
==========================================
+ Coverage   85.48%   89.00%   +3.51%
==========================================
  Files         174      174
  Lines        3300     3300
  Branches      364      364
==========================================
+ Hits         2821     2937     +116
+ Misses        476      360     -116
  Partials        3        3

Impacted Files
Coverage Δ

src/agent/Agent.ts
100.00% <0.00%> (+2.77%)
:arrow_up:

src/agent/AgentConfig.ts
94.87% <0.00%> (+5.12%)
:arrow_up:

src/modules/connections/ConnectionsModule.ts
72.36% <0.00%> (+5.26%)
:arrow_up:

...onnections/messages/ConnectionInvitationMessage.ts
91.17% <0.00%> (+5.88%)
:arrow_up:

src/agent/MessageReceiver.ts
85.71% <0.00%> (+6.12%)
:arrow_up:

...ecorators/transport/TransportDecoratorExtension.ts
73.33% <0.00%> (+13.33%)
:arrow_up:

...c/modules/routing/services/MessagePickupService.ts
42.10% <0.00%> (+15.78%)
:arrow_up:

src/agent/EnvelopeService.ts
100.00% <0.00%> (+25.00%)
:arrow_up:

src/modules/routing/messages/BatchMessage.ts
81.81% <0.00%> (+27.27%)
:arrow_up:

src/helpers.ts
68.75% <0.00%> (+31.25%)
:arrow_up:

... and 8 more

Continue to review full report at Codecov.

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


[AutoPR cognitiveservices/data-plane/LUIS/Authoring/cognitiveservices/data-plane/LUIS/Runtime] Adding specific error codes to LUIS APIs and adding the subscription key as a requirement to the APIs.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4584

(message created by the CI based on PR content)


ARROW-7663: [Python] Raise better error message when passing mixed-type (int/string) Pandas dataframe to pyarrow Table

This PR homogenizes error messages for mixed-type Pandas inputs to pa.Table.
The message for Pandas column with int followed by string  is now
In [2]: table = pa.Table.from_pandas(pd.DataFrame({'a': [ 19, 'a']}))
(... traceback...)
ArrowInvalid: ('Could not convert a with type str: tried to convert to int', 'Conversion failed for column a with type object')

the same as for double followed by string:
In [3]: table = pa.Table.from_pandas(pd.DataFrame({'a': [ 19.0, 'a']}))
(... traceback...)
ArrowInvalid: ('Could not convert a with type str: tried to convert to double', 'Conversion failed for column a with type object')

As a side effect, this snippet [xref #5866, ARROW-7168] now throws an ArrowInvalid (has been FutureWarning since 0.16):
In [8]: cat = pd.Categorical.from_codes(np.array([0, 1], dtype='int8'), np.array(['a', 'b'], dtype=object))
   ...: typ = pa.dictionary(index_type=pa.int8(), value_type=pa.int64())
   ...: result = pa.array(cat, type=typ)
(... traceback...)
ArrowInvalid: Could not convert a with type str: tried to convert to int

Finally, this does break a test [xref #4484, ARROW-4036] - see code comment

@jorisvandenbossche was there more to be done here?

Thanks for the ping. I think all good. @arw2019 can you just rebase to ensure it's still all passing with latest master?

@jorisvandenbossche Rebased and seeing some failures. They're ones also popping up in other, unrelated, PRs, so not sure they're to do with this patch? I'm happy to investigate, though

There are some known failures on Mac and Appveyor at the moment, so nothing to worry about for this PR.

Thanks @arw2019 !

Thanks @jorisvandenbossche for reviewing!


Change the default course_id

This change allows ansible-provision-locust-master to work out of the box.

Do we need to update all the hardcoded problem blocks in the rest of the tests?
I assume this is for running against sandboxes vs the loadtest env (which still uses that old draft module and I would love for it to use split, but lots of other things need updating)

Quoting Kevin Falcone (2016-07-08 16:25:06)

Do we need to update all the hardcoded problem blocks in the rest of the tests?

It's possible, this only addresses the lms tests.  The other tests are broken for
various different reasons:
https://openedx.atlassian.net/wiki/display/ENG/State+of+Locust

I assume this is for running against sandboxes vs the loadtest env (which still
uses that old draft module and I would love for it to use split, but lots of
other things need updating)

Correct.  Ah, I wasn't thinking of the loadtest env.  In that case I'd rather
not merge this because it would make it impossible to run tests against the
loadtest env since evironment variables are not currently configurable (unless
you shell in, set COURSE_ID, then re-run locust).
Troy

I was referring to the lms tests, they have hardcoded blocks in there, I can find them on Monday if you're curious.
I would love the loadtest env to also use a split course (not a draft course) by default, I currently shell in, change the course ID and modify tests to use other blocks.  It's a PITA and not complete by any measure.


Discussion iOS WakeUp Push

We have issues with receiving push notifications if the user if offline for some time (> 1h)
I was trying to understand the WakeUp Push behavior but I'm not sure if I fully understand. Maybe you can correct me if I'm wrong at some point.
It seems that a wake up push is send in two cases

A notification is send via mobile Push channel
A notification is confirmed as seen

I think case 1. is the reason for our issue. If I understand the timers correct, the wakeup is delayed for 30 seconds. Means the wakeup push is always send after the real notification. Because iOS is only saving the last notification the real notification is never send directly only via our pull mechanism. But if the wakeup notification is also delayed by apple or just not send completely, you will get the notifications only by the next event notification. This happened for some of our users in our last tests. Our at least this would be my explanation why they didn't receive the notifications when they come online again but later (ca. 2h)  when an event notification was triggered.
Case 2 should not be necessary if we load all pending notifications when receiving the first notification after coming online. It could just be a safety line if there is something wrong with the inital pull. Not sure if this is really helpful or could be an issue.
What do you think about these assumptions?

About case 2: I think the main reason for that, was to offload the pulling from service. because of the time constraint. Therefore we send the wakeup again to force the app to become online
The reason for the delay of the wakeup is that we want to offload the notification so that it cannot affect our normal notification it to improve error reporting and I do not really see an option here. But I guess every normal notification could also be a wakeup notification, so perhaps this is not needed.

I agree, case 2 is related to the timing constraint in the notification service extension. In older versions of the sdk we only pulled after receiving the wake up message. Here it was necessary absolutely necessary.
I'm not sure what's exactly the meaning of "offload the notification" and "improve error reporting". I don't think that a normal notification wakes up the main app. That's exactly the reason of the background notificaitons and they are very limited and must have the content-available flag and are not allowed to include any other user specific input.
But I just figured out some issue with the wake up message body and created a pull request. Maybe this helps to fix it.

I'm not sure what's exactly the meaning of "offload the notification" and "improve error reporting".

I mean to push it back to the internal queue in squidex backend to have all the benefits of retry and so on.

That's exactly the reason of the background notificaitons and they are very limited and must have the content-available flag and are not allowed to include any other user specific input.

I just thought a normal notification could also be a background notification.


Method call on parenthesized expression

Description:
The expression
("abc").length()
causes a compiler error message. Is this a parser error, or do I misread the spec?
As the static type of
("abc")
is string, a call of function length() from library lang.string is expected (per 6.20 Method call expression). The expression
"abc".length()
on the other hand, works as expected.
Steps to reproduce:
Complete source code:
import ballerina/io;
public function main() {
var len = ("abc").length();
io:println("len: ", len);
}

@hrennau yes this should work, but I'm afraid the implementation does not support this at the moment.
Closing this issue since it is being tracked with https://github.com/ballerina-platform/ballerina-lang/issues/19020. Please do reopen if you have further concerns.


Fix line endings to LF

These files had mixed line endings it seems, and were always appearing
as uncommitted changes in my environment, which makes it harder to see
the changed state of things (I'm on Linux), and also makes it impossible to do some switches between branches.

Codecov Report

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

@@            Coverage Diff            @@
##             master    #1253   +/-   ##
=========================================
  Coverage     93.81%   93.81%
  Complexity      458      458
=========================================
  Files             2        2
  Lines          6753     6753
  Branches       1823     1823
=========================================
  Hits           6335     6335
  Misses          126      126
  Partials        292      292

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 9c2447d...03c7155. Read the comment docs.

Great to see a PR that addresses this issue, since I was bothered from/struggling with this issue, too (I'm on Windows most of the time).
I hope this won't be reintroduced when regenerating the docs. I saw the issue come first two weeks ago (or so), shortly after we upgraded the asciidcotor-gradle-plugin. IIRC, it disappeared for some time and then came back again. I couldn't find any pattern and didn't have the time to investigate this, though.

It might still be there, after regenerating the docs. I notice that it's always the same snippet. The asciidocs thing must be pulling this snippet from one file. I will try to make all the files in the docs folder just have Unix line endings.

I've changed the entry for .html files in the .gitattributes file to ensure that the file is always checked in with LF line endings. I hope this fixes it. It seems that it introduced by the Asciidoctor documentation generation, it must have that faulty CSS/JS snippet inside its code somewhere, but this should hopefully keep it fixed more permanently.

Merged.
Thanks for the contribution!


Issue 24

https://github.com/Ckbhatia/Ck-gatsby-blog/issues/24 feat: implement pwa

Hi @bhavika24, I am glad to see your PR for this issue. Thanks for contributing to this project.
I am quite busy with my other task. I will review your changes soon.

Hi @bhavika24, Can you please take a pull from feature branch, merge and push changes to this PR.
I want to accept your PR.

Hey @Ckbhatia I have resolved the conflicts.


Error.txt

error.txt
I was trying to make a funny gif what do these funny words mean

Seems like either Discord or the connection to their servers is acting up. Unfortunately there isn't much I can do about this, as the connection to Discord is handled by the Eris library, not by the bot itself.


vscode intellisense pop up truncates the api details.

There is a vertical scroll bar but no horizontal scroll bar.
https://github.com/redhat-developer/vscode-java/issues/514
vscdoe: 1.22.2

/duplicate #29757


fix: sync endpoint rather than endpointSlice

What type of PR is this?

fix: fix bug

What does this PR do?

Which issue(s) does this PR fix?

Fixes #85
Special notes for your reviewer:

Screenshots (if applicable):

Additional Comments:

/cc @wuyingjun-lucky @wangyizhi1

/cc @hanweisen @xyz2277

/assign @wangyizhi1

/lgtm

/approve


No AUR build

There is no binary/release for arch, it would be nice if there could be an easier way to install NewCP on an arch based distro.

Just use flatpak.


BUG: Wrongly displaying data in marker

It should not display number but category. Reproduce bug with test and fix this.

bug was introduced with #53


N7edPMiO: Improve MSA Logging

What
MSA logs don't contain a lot of useful information. It's hard to use them to identify what a problem is.
We should implement error logging changes to the MSA so that the full stacktrace is returned to the Verify Hub when an HTTP 500 error happens in the MSA.
There is some further background in Anshul's investigation into MSA 500 errors.
Original Zendesk ticket:
https://govuk.zendesk.com/agent/tickets/3651026
How
Add new LocalMatchingService exception to wrap exceptions thrown while communicating with the LMS.
This will allow us to determine if MSA errors being thrown are internal MSA or being thrown by LMS.

 Improve MSA logging

Closing if favour of different approach.


***Manifest not found for componentId and Field Customizer

Created a hello world field customizer
Updated serve.json, write-manifests.js and @node module per instructions
Opened link as follows

https://MyTenant.sharepoint.com/sites/SiteCollection/Lists/List A/AllItems.aspx?debugManifestsFile=https://spfx:4321/temp/manifests.js&loadSPFX=true&fieldCustomizers={"HelloWorld":{"id":"5e2385b5-bfd4-44c5-97d6-a392e942a6ab","properties":{"sampleText":"Value"}}}

Tried updating debugManifestsFile parameter with <IP_ADDRESS> and localhost with no success
Ensured that the field exists as expected

SPFX version: 1.6.0
Docker-SPFX: latest

Can you navigate in your browser to https://spfx:4321/temp/manifests.js?

Already did that and skipped certificate check.

Is the component ID mentioned in the URL in the manifests.js file?

Opened https://spfx:4321/temp/manifests.js
Component ID is not found there
Attached is a link to the solution: https://1drv.ms/u/s!AiJb5ImzKg3U3jJUpAwPWwo4vrQ8?e=cPNUb3
In the same browser I've opened: https://spfx:4321/ and https://localhost:4321/
Proceeded to bypass the certificate
To debug, I am accessing
https://tentn.sharepoint.com/sites/siteCollection/Lists/List A/AllItems.aspx?debugManifestsFile=https://spfx:4321/temp/manifests.js&loadSPFX=true&fieldCustomizers={"SPFCustomDialog":{"id":"7fb6b701-ff7e-4407-989b-3c37ff532071","properties":{"sampleText":"Value"}}}

If the component ID is not there, it could explain the issue. Have you tried running gulp clean and gulp serve again?

Already tried that out, removed by hand

OK, I've fixed it by re-building the solution from scratch - something was missing somewhere. I'd assume that it has something to do with the component ID as I was playing around it.

Good to hear you're unblocked 👍


python311Packages.boltons: disable failing test on Python 3.11

Description of changes
Fix build (https://hydra.nixos.org/build/209270696)

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

14 packages built:

dinghy (python310Packages.dinghy)
eliot-tree
ghdorker
python310Packages.boltons
python310Packages.eliot
python310Packages.face
python310Packages.glom
python311Packages.boltons
python311Packages.dinghy
python311Packages.eliot
python311Packages.face
python311Packages.glom
semgrep
tahoe-lafs


ESlint fixes plus other minor improvements

This PR contains some ESlint fixes, plus some minor improvements (most were SonarQube suggestions):

Remove the e.stack.split("\n").slice(0, 2).join("\n") + "\n" + err.stack; expressions, because they had no effect
Renamed toPrimitedType to toPrimitiveType (typo)
Refactored nested if ... else { if .... } to if ... else if .... else if
Replace type ? type : parseDefinition(...) with more concise type ?? parseDefinition(...)
Removed unread variable allMethods

edit: the eslint things are also handled in #81, I might rebase after that one gets merged

Thanks for your PR!
Do you think it would be possible to include sonarqube check as part of GH Actions? Would be nice to have some kind of badge or any other SonarQube verification on top of this Repo for better security feeling

Do you think it would be possible to include sonarqube check as part of GH Actions? Would be nice to have some kind of badge or any other SonarQube verification on top of this Repo for better security feeling

I'm using my own SonarQube subscription here, I don't know if there's a 'free' SQ github action available.
However, the majority of these findings can also be found using a stricter eslint config. Might be best to look at that in the shorter term.

Makes sense, let's merge this. Thanks ! :)


[TRACKING] CI Integration for "falco rules mitre checker module"

CI Integration for "falco rules mitre checker module", see https://github.com/falcosecurity/rules/pull/181.
CC @IceManGreen @leogr @FedeDP

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale


security: upgrade dependencies to resolve multiple CVEs

Closes https://github.com/plotly/dekn/issues/7259
Upgrade dependencies to resolve:

CVE-2022-31836
CVE-2021-30080
CVE-2023-2253
CVE-2023-39325
GHSA-m425-mq94-257g

I forget why we have our fork of Harbor. Do you happen to remember?
I'm asking because it's too time-consuming to review/validate changes made here without any CI. It would be nicer to have this work land upstream and have the maintainers review it.
Anyway, in the interest of time, I'm OK with approving this and catching potential regressions in dek-deployment via e2e tests 🚀

Agreed. We forked it because it had vulnerabilities and was not really being maintained a few releases ago. I can get some tests put together for this.

@devinturner it looks like their Helm chart is under more active development. Therefore, I think we should move away from their operator altogether since we only manage one instance anyway.


Dynamically change the CameraView size

Hi there,
in my application, I need to make the size of the CameraView dynamic (I want a fullscreen view, with support for orientation changing). So I do not want to set HeightRequest, and WidthRequest of the control. If i dont set these values, the AdjustAspectRatio function may calculate wrong values, and the image is distortet or stretched (or its not fitting inside the fullscreen; like zoomed in). This happens espacially if you change the device orientation. It seems, that after changing the orientation, somtimes the CameraView calculates (RectF viewRect = new(0, 0, Width, Height);) with values from the old orientation. I think it refreshes  before the actual PlatformView gets resized. With appropriate breakpoints inside the AdjustAspectRatio function, it calculates and transforms correctly. Also the preview image seems to get cut instead of having some fitting logic for the corresponding apsect ratio. In my special case, I need to open the camera preview in an 4:3 aspect ratio.
I just call
var size = _cameraAspectRatios.Where(x => x.Item1.Numerator == 4 && x.Item1.Denominator == 3).MaxBy(x => x.Item2);
await CameraView.StartCameraAsync(new Size(size.Item2, size.Item3));

to get the highest 4:3 resolution. What I expect would be a fullscreen mode, adjusting the width and height corresponding to the given AspectRatio AND the current orientation (fitting the image, whith black borders for example).
I just tested this on Android right now.
I hope you get the idea and have a solution for my problem.

I am facing the same issues on Android devices. Even device performance seems to be affected, as I've been trying for two days to catch this issue occurring on one device during debugging, but not present in the release build.
On another device, which was used for tests when writing code earlier, the problem occurred very rarely even during debugging.
When rotating a device with screen rotation enabled, the device is engaged in animation playback. And judging by the debugging information, the AdjustAspectRatio function in Platform.Android.MauiCameraView.cs is called sometimes before and sometimes after the width and height have been changed according to the screen position. For this reason, further calculations are not correct and the preview is displayed crookedly on the screen.
Here is an example of debugging information when an error occurs:
Before turn, Portrait mode:
[0:] viewSize [w: 720 h: 1457]
[0:] videoSize [w: 2560 h: 1440]
After turn, Landscape mode:
[0:] viewSize [w: 720 h: 1457]
[0:] videoSize [w: 2560 h: 1440]
As you can see, the dimensions of the view have not changed.
Sometimes there are cases when the values have already been changed.
I hope this helps a little more understanding of the problem @Falco94 outlined above.

Hi @michailowski, I had the same problem as you even with release build mode. The preview screen is just not stretched when I turn the phone. I'm stuck in this situation and don't know what to do. Have you solved this problem yet?


The sizes of these beats look different

Describe the bug
The sizes of these beats look different, it's so weird.

Expected behavior
They should have the same size.
Info

Uptime Kuma Version: latest
Using Docker?: Yes
OS: MacOS
Browser: Chrome and Safari

Duplicate of #326


isSingleResource, model.get is not a function

currently the following regex is used to determine if a route is a single resource:
  isSingleResource: Ember.computed.match('currentPath', /(?:^(?!.*s\b))(?:^(?!index)).*$/),

this regex checks if one of the following conditions is true:

currentRouteName is not equal to index
currentRouteName isn't plural (only checks if it doesn't end with an 'S')

however this regex breaks on routes such as: not-found because it
a. isn't equal to index
b. isn't plural
a simple check in the activeRoute computed property on the presence of the id property is a possible workaround that I'll implement soon.

I created a pull request related to this: https://github.com/alexanderjeurissen/ember-cli-history-mixin/pull/3 –– not sure if my solution is the best solution, but it worked for me in my project.

closed by #3


Unable to invoke face liveness view

Describe the bug
Feedback from several users indicates that when attempting to open the facial verification page, a blank page is displayed.
I have not been able to replicate this issue myself, and there are no error logs, so I am unsure how to troubleshoot this error.
I need assistance in troubleshooting.
This issue occurs sporadically;
most users can use the feature normally, but a small number of users are unable to use it.
Attached are videos showing the feature being used normally (by me) and the issue where it cannot be used, along with screenshots of the code.
https://github.com/aws-amplify/amplify-ui-swift-liveness/assets/16227011/10728adb-3e56-484e-bc5c-952f037e50ba
https://github.com/aws-amplify/amplify-ui-swift-liveness/assets/16227011/1fc8ecdd-ca4f-421f-a1f6-595019a4530e

Steps To Reproduce
auth is ok
face liveness error

Expected behavior
I want to be able to use the face verification function normally
Swift Liveness Version
1.2.5
Xcode version
15.3
Relevant log output
<details>
<summary>Log Messages</summary>

INSERT LOG MESSAGES HERE

```
Is this a regression?
Yes
Regression additional context
No response
OS Version
iOS 17.1.1(user) 17.4.1(me)
Device
iPhone 14（user）iPhone 12（me）
Specific to simulators
No response
Additional context
No response

@LiangLuDev I have not been able to reproduce this issue.  It looks like there's been several bug fixes releases from the current version you're using.  Are you able to update to the latest released version and see if issue still exists?
Are you able to add additional logging to see if an error code or exception is returned from the component? Are you observing this issue on any specific iOS version or device?

I have already added logs to the location where results can be obtained, but there is no error information on our analytics platform. From the feedback, it seems that the issue is not related to the iOS version, as the errors occurred on different iOS versions. I will first update the Amplify-related versions and see how it progresses.

@phantumcode
I have upgraded the package to the latest version, but git status does not show any changes. How can I confirm that I have upgraded to the latest version?

@LiangLuDev Yess, version 1.2.13 is the latest version.

Hi @phantumcode .
I would like to inquire whether there are any restrictions related to facial recognition authentication for user accounts. According to the data I reviewed, our facial recognition feature has been live for approximately two months. However, we have recently received increased feedback about users being unable to invoke the facial recognition page in the past two weeks, despite there being no modifications made or new versions released during this period. I am unsure where to submit a ticket to track and address this issue.

@LiangLuDev Can you clarify what you mean by "restrictions related to facial recognition authentication for user accounts"?  Your authentication and user accounts are up to you to setup and maintain.  Your backend service to create the session id and get the result are up to you to setup and maintain.
Also, please clarify and be more specific on what you mean "unable to invoke the facial recognition page in the past two weeks".  Are the users unable to create a session id? Are the users unable to get the result?  Are the users able to get a session id and start a liveness session and unable to complete the liveness check? If so, what is the exception or error message you're seeing or capturing?  Do you have example of sessions that are running into this issue? If so can you provide the session ids that the service team can look into?  Are this issues occurring on a specific platform (iOS/Android/Web) or specific region?

Currently, this issue is only occurring on the iOS platform.
Based on all the logs and screen recording analysis available to us, user login sessions are successful.
The redirection to the facial recognition page occurs only after the user successfully creates a session. This can be observed from the code screenshot provided earlier.
I will share the session ID with you tomorrow.
As stated above, I am unable to reproduce this issue myself. This feedback was given to me by a user.

When I call Amplify.configure(), an error occurs, but the facial recognition page can still be invoked normally. Will this have any impact? I noticed that your demo is also written this way.
Unable to configure Amplify PluginError: Could not cast incoming configuration to JSONValue
Recovery suggestion: The specified configuration is either nil, or not convertible to a JSONValue. Review the configuration and ensure it contains the expected values, and does not use any types that aren't convertible to a corresponding JSONValue:nil

The demo requires Amplify Auth and Amplify API configured to run properly, see the README.md
failure at Amplify.configure is due to your amplifyconfiguration.json being incorrect.  If you're using Amplify Auth to provide  user authentication, then this would have an impact.  Please share the code snippet where you configure Amplify and your amplifyconfiguration.json file with any sensitive information removed/redacted.

The initConfig function is called during application startup.

amplifyconfiguration.json

@LiangLuDev It looks like the amplifyconfiguration.json is missing configuration for Amplify API but in your startup you're configuring the Ampplify API with the line try Amplify.add(plugin: AWSAPIPlugin())

@phantumcode I would like to ask about the role of the AWSAPIPlugin.
I noticed that it is added in the demo, but I am unsure if we need to utilize it since the application still runs normally even after I commented out "try Amplify.add(plugin: AWSAPIPlugin())".

@LiangLuDev The API Plugin is used to make REST calls to create the session id and get the result.  If you are using other methods to call your backend to get the session id and result, then it is not needed and you can remove that line of code in the startup configuration.

@LiangLuDev Can you clarify what you mean by "restrictions related to facial recognition authentication for user accounts"? Your authentication and user accounts are up to you to setup and maintain. Your backend service to create the session id and get the result are up to you to setup and maintain.
Also, please clarify and be more specific on what you mean "unable to invoke the facial recognition page in the past two weeks". Are the users unable to create a session id? Are the users unable to get the result? Are the users able to get a session id and start a liveness session and unable to complete the liveness check? If so, what is the exception or error message you're seeing or capturing? Do you have example of sessions that are running into this issue? If so can you provide the session ids that the service team can look into? Are this issues occurring on a specific platform (iOS/Android/Web) or specific region?

Hi, @phantumcode
This is session id for user, I will help investigate. Thank you very much.
Since the user has tried multiple times, there will be multiple session IDs.
7d631d5c-530b-484e-a192-3e6438346ade
a05e30e6-409e-477d-acdf-fb682579acfb
37620b49-2397-4299-a9e3-9ad886638c68
802b6d0b-49f4-4084-a55a-e5832e43c17f
ad4b2004-a9af-4c76-a7eb-230eaa9b20da
b89cb244-90fc-47f9-a42d-6b25e3e6ca5c
98027b29-8824-445f-9031-fa53afb03219

@LiangLuDev Can you provide what region and approximate timeframe these sessions are for? The service team is not finding them in us-east-1 for the last 4 weeks.

@LiangLuDev Can you provide what region and approximate timeframe these sessions are for? The service team is not finding them in us-east-1 for the last 4 weeks.

This happened the 2024-05-13

@LiangLuDev Can you provide what region and approximate timeframe these sessions are for? The service team is not finding them in us-east-1 for the last 4 weeks.

Please help check if there is an issue on our server side when creating sessions.
We are using the Go language SDK function CreateFaceLivenessSession.
The time frame is approximately [2024-05-13T04:59:56.967212753Z] - [2024-05-13T06:07:04.805981851Z]

@LiangLuDev What region is it deployed to? us-east-1?

@LiangLuDev What region is it deployed to? us-east-1?

Yep.

@LiangLuDev We were able to see those sessions get created in us-east-1 but don't see any logs for starting the sessions.  It is likely an issue on the client side before any connection is not established to start the liveness check.
Are you able to release and observe if issue still occurs after updating to the latest version of library or capture additional logs/exceptions?

Okay, we are planning to release a new version by the end of the month.

@phantumcode Hi, I have already upgraded to the latest version, but the issue with the white screen still occurs as mentioned above. Please assist me in troubleshooting. Otherwise, the boss said we might need to consider an alternative solution.
this is sessionId: efbc1261-1b40-489a-b10c-d3cba8ecde77

@LiangLuDev Are you able to provide a sample app that demonstrates how you've integrated Liveness component? I understand that you've provided code snippet in the issue, but it would be helpful to have a sample app to help debug the issue and get more context on how you getting the session id and constructing the view.

@LiangLuDev Are you able to provide a sample app that demonstrates how you've integrated Liveness component? I understand that you've provided code snippet in the issue, but it would be helpful to have a sample app to help debug the issue and get more context on how you getting the session id and constructing the view.

Of course, I will try to provide an example project following my project structure as much as possible tomorrow.

@LiangLuDev following up on this.
Are you still facing this issue? If so, were you able to create the sample app?
Thanks!


Update to React 18

This PR updates the Facet packages to be based on React 18 (18.2.0 in specific), finally adding support to concurrent mode.
We are marking this PR for review, but will only proceed with merging after some internal testing within Mojang.
This PR has been a massive endeavor, with collaborations from @marlonicus and @ja-ni.
Release candidate
There is a new "release candidate" pushed in v0.6.0-rc.4, so you can help test this new release by getting the new release from npm:
"@react-facet/core": "^0.6.0-rc.4",

Deprecation of @react-facet/deferred-mount
The "Deferred Mount" solution was only needed as an alternative to "concurrent mode" while that wasn't available. So, this PR deletes the package from the repository, and we recommend any consumer to look at React 18's documentation and leverage their new APIs:

useTransition
useDeferredValue

After merging, we will deprecate the package on NPM, and will be no longer maintaining it.
Effectless useFacetWrap, and new useFacetWrapMemo hook
In our internal codebase at Mojang, we rely a lot on useFacetWrap to keep components compatible with both regular values and Facets in their APIs. However while testing the improvements of this React 18 upgrade, we have identified that even though React makes the setup of the components concurrently, all the effects are actually run synchronously right after attaching the nodes to the DOM (as confirmed by this article):

Second, all effects (useInsertionEffect, useLayoutEffect, useEffect) run only after the render phase, which means that by the time they run, not only the component they’re being called in will have finished rendering, but also it will have been committed, which means that the whole component subtree for which the render was scheduled has finished rerendering.

So, to make sure this final synchronous step is smallest as possible (to avoid any frame spike), we have changed the default behaviour of the useFacetWrap hook so that it doesn't rely on an effect to update the wrapping value.
The main change this implies is that now if the wrapping value changes (is a different reference), a new Facet will be created.
As this change can have consequences down the rendering tree, there is also now a new component useFacetWrapMemo that retains the previous behaviour, ensuring that the resulting wrapped Facet is always the same and its just updated with new values.
On upgrading to this new version, we recommend profiling the application, and using the new hook as necessary to address performance regressions.
Now useFacetMemo can have an initial value
Previously the resulting Facet of calling useFacetMemo would always have NO_VALUE as its initial value, even if the Facet's it was dependent on had values.
This has been changed to help ensure that when React goes concurrently through a component tree, if a data is available, then it will be available at that time, and not at a later moment after all the effects were executed.
Changes to unit tests
Now that React no longer runs updates synchronously, any state update within a unit test must be wrapped in an await act:
await act(async () => {
  // perform state changes that would cause a component to update for testing purposes
})

The Map and Mount components are "deferred"
We have considered a good standard behaviour to have all "mount" operations to be considered low-priority and to have them run in concurrent mode.
From internal testing within Mojang, we believe this will give the smoothest experience to users of the UI.
This has no change in the API, and will be a transparent upgrade to any consumers of the library.
Updates to the benchmark test suite
With React 18 and concurrent mode, we had to do some fixes to the benchmark test suite to correctly measure and compare Facets with "Vanilla React". The main change revolves around getting the correct trace event FunctionCall, instead of just the FireAnimationEvent.
It also updates the tests to make sure we enable concurrent mode on the React 18 examples by using the createRoot API.

We can't do the update for now, as the type definitions are still not up-to-date. We could either wait for someone in the community to update, or maybe try to prepare a PR ourselves?
For now, I'm holding this PR until further notice.

New type definitions were published! So I took another stab at making this work.
Brute-forcing adding the new APIs as needed resulted in the examples working, but next step is understanding what and how we should use these new methods.
I've been using the https://github.com/pmndrs/react-three-fiber/blob/master/packages/fiber/src/core/renderer.ts as a reference implementation.

The React version 18.2.0 made some breaking changes to it's type definitions. The children property was removed from the FC type constructor but fortunately there is a migration script available to help update the existing type definitions:
https://github.com/eps1lon/types-react-codemod
This script does not completely alleviate the issue since for a number of our components we accept facets as children, in these instances the automatically generated types had to be adjusted.
Another issue that has arisen from the React 18 type changes is that the Element and ReactNode types are now misaligned with our current version of react-router. An upgrade of the react-router package is one solution to this issue but it is one that would require significant effort on planning.

this was last updated 2022. It's 2024


Long length sms are not sent

I was trying to send SMS, which is very long but it was not sending the message and not showing the error also. Then I tried to send small sms and got sent immediately.

only 160 letters are allowed not more then that . It work on only one sms token . if you use emojis then capacity will decreased


Search

the $scope.getActivityDetails method should be getting the same data as the old application now.

:+1:


部署包优化

内否对admin打包结构做下优化，方便部署和修改配置。例如这种结构：
├─bin
│      setenv.sh
│      start.bat
│      start.sh
│      stop.sh
├─config
│      application.properties
│      logback-spring.xml
│─dubbo-admin-0.1.jar

Sorry, because this issue was raised very early, we have closed it temporarily. You can verify whether this problem still exists in the latest code of the develop branch. If this problem still exists, please reopen it at any time.


Remove experimental CALL_CREDENTIALS option

This was a backup plan for xdsproxy, to enable use of JWT from Envoy
directly. Since xdsproxy is now default/stabilized, we don't need this
anymore
Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
63733da69fca098090c0c01d63aa5220390b79d3
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@howardjohn: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@howardjohn: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
3e44ddd909fc099c507772fde571a36ee5bc3c82
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
3e44ddd909fc099c507772fde571a36ee5bc3c82
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
3e44ddd909fc099c507772fde571a36ee5bc3c82
link
/test integ-security-multicluster-tests_istio

gencheck_istio
3e44ddd909fc099c507772fde571a36ee5bc3c82
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
3e44ddd909fc099c507772fde571a36ee5bc3c82
link
/test integ-security-multicluster-tests_istio

gencheck_istio
3e44ddd909fc099c507772fde571a36ee5bc3c82
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
3e44ddd909fc099c507772fde571a36ee5bc3c82
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
3e44ddd909fc099c507772fde571a36ee5bc3c82
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test lint_istio

/test lint_istio


Project Description and README does not use inclusive language.

Both in the project README and the description you repeatedly refer to the victim of your fake verification using the he/him/his pronouns. I belive this skips an important fact that people who fall for such scams are almost always both men and women without much difference in the amounts or ratios. A better way to word the about me would be:
This script developed in python3 allows you to create a verification QR Code, that the user will have to scan on their arrival to the server. Once scanned, you will get their information including their Token.
I have also taken some liberty to correct small grammatical mistakes.
A similar rework could be applied to the README.
Please consider using more inclusive language in your future malware.

This bot is being used to scam people, and you're worried about inclusive pronouns??? I wouldn't be surprised if you are using it to scam people as well.


Decorators which alternate docstrings are ignored

Hi,
I've currently switched to mkdocs and I have have to say that this is an amazing project :)
But there are a few minor issues I did not manage to resolve on my own. I am using a simple self-written decorator from decorit which copies the Parameters section from a function to another. The function looks like the following:
def copy_doc_params(source: Callable) -> Callable:
    """Copy parameters from docstring source."""
    @beartype
    def wrapper_copy_doc(func: Callable) -> Callable:
        PARAMS_STRING = 'Parameters'
        doc_source = source.__doc__
        doc_func = func.__doc__
        if doc_source and doc_func and doc_source.find(PARAMS_STRING) != -1:
            # find last \n before keyphrase
            idx = doc_source[:doc_source.find(PARAMS_STRING)].rfind('\n')
            doc_params = doc_source[idx:]

            doc_params = doc_source[doc_source.find(PARAMS_STRING):]
            func.__doc__ = '{0}\n\n{1}'.format(  # noqa: WPS125
                doc_func.rstrip(),  # ensure that doc_func ends on empty line
                doc_params,
            )
        return func
    return wrapper_copy_doc

def func(a):
    """Function func.

    Parameters
    -----------------
    a : int
        Variable with name a.

    """
    pass

@copy_docs_params(func)
def gunc(a):
    """Function gunc."""
    pass

print(func.__name__, func.__doc__)
print(gunc.__name__, gunc.__doc__)

Printing the names, the docstring is copied as expected. But using it with mkdocs, it shows me only the original docstring of gunc. Including functools.wrap did not change the result.
Thank you for your help.
Best, Daniel

Hi, thanks :heart: !
Are you sure you're using pytkdocs, through the mkdocstriings-python-legacy handler?
The behavior you witness would make perfect sense if you're using the mkdocstrings-python handler, which only visits the AST and does not inspect code loaded in memory.

Thanks for your reply and I've confused the repos, so you are right! I am using the new python handler. Should I create a new issue at the correct repo, or is it a know issue?

It is not an issue per se, but the way to make it work is not documented yet (I'm working on it) :)

We now have a small how-to on how to support custom decorators: https://mkdocstrings.github.io/griffe/guide/users/how-to/support-decorators/.

Thank you so much for your time and effort :)


How to access variables/functions inside AssemblyScript?

Hi, I am unable to access the length of a local array or any other declared variable inside AssemblyScript. Once the array is initialized, if I wish to call the inbuilt property such as length, I get the appropriate local variable and try to access the length but do not know how to do so. The length does not seem to be retained in memory anywhere. Also, when testing arrays, the .length operator returns a constant value, which means that it is not being stored correctly.
eg, the following function returns 1 when called.
export function getLength(): int {
let v: int[] = new Array(9);
v[0] = 1;
v[1] = 17;
v[2] = 15;
v[3] = 71;
v[4] = 17;
v[5] = 16;
v[6] = 14;
v[7] = 32;
v[8] = 12;
return v.length;
}

Just tested with master:
loading 'test.wasm' ...  index.html:48:3
> exports.memory  index.html:57:11
> exports.getLength(0)  index.html:55:11
loaded.  index.html:61:7
exports.getLength()
9

Feel free to reopen if the issue still persists in master.


Customizing the 3DS (3D Secure) form

Hi everyone! I'm using the Adyen checkout flow, and for my use case, both the payment and cart are in a single step. However, I would like to separate the 3DS form into a different section to prevent any updates to the cart (like cart modifications) while the payment is being processed.
Is it possible to use a 3DS form in a modal? For example:

Hi @vunguyen10111995
This is an interesting use case. Could you please let us know which version of Adyen Web you are integrating with? Additionally, are you using the session flow or the advanced flow?
Furthermore, could you confirm whether you are integrating with the Drop-in approach or the component-only approach?


Right-aligning positions in \job pushes text too far right

Hi there,
Thank you for an interesting template!
I have been experimenting with right-aligning the positions in \job, but somehow the text is pushed way too far to the right. I have tried both \raggedleft and \hfill to the same effect.
Any ideas? Many thanks!

Answering my own question after I've got a moment to look into it:
My problem was due to minipages being too wide. If the width of both of them is set to 0.4 and \hfill is added between them, then everything works as expected and a \hfill before position name will make it right-aligned.
Why 0.49 or something isn't working is not exactly clear - maybe some margins appear from somewhere or something, but probably I'll sleep better if I wouldn't know.

Glad you could figure it out. Right now I also can't tell why larger values do not work. You are probably right that a margin of some sort steal some of the available space. Once I have more time again, I will try to look into it.


documentation/website improvements

http://roots.cx/ is a nice web site - but boy! No link to the github repo?
And on http://roots.cx/articles/blogs not even a link to some example code?

I humbly suggest an article on how to update roots. I am on Version 3.1.0 and can't find the reference on how to update to 3.2.2

@ganar since Roots is an npm module, you can update it just like any other npm module - $ npm update roots -g
@tcurdt I see your point - but this issue should really be taken up on the roots.cx repo, since the docs are a separate project to roots itself
Please post your feedback there

Agreed, thanks Declan!


Server crash in create a train

Describe the Bug
When I press the done button of the following station after linking the train with glue, the server crashes.
Reproduction Steps
1.Create a train
2.Use the funnel as part of the body
3.Click finish in the station
Expected Result
I want to create a train
Screenshots and Videos
No response
Crash Report or Log
Log https://pastebin.com/gWpuJxPw / Crash report https://pastebin.com/KHu3K6Fx
Operating System
MacOS 13.1
Mod Version
0.5.0g
Minecraft Version
1.19.2
Other Mods

starlight-1.1.1+fabric.ae22326
otyacraftengine-fabric-mc1.19.2-3.2.0
minimotd-fabric-mc1.19.2-2.0.9
lithium-fabric-mc1.19.2-0.10.4
lazydfu-0.1.3
iammusicplayer-fabric-mc1.19.2-3.19.4
ferritecore-5.0.3-fabric
fabric-carpet-1.19.2-1.4.84+v221018
fabric-api-0.70.0+1.19.2
cloth-config-8.2.88-fabric
architectury-6.3.56-fabric

Additional Context
No response

duplicate of #503
wait for next update or remove minimotd

duplicate of #503 wait for next update or remove minimotd

is it safe to add back now?


ENH: Add pauseRender function to ctkVTKAbstractView

The pauseRender function allows applications to pause the invocation of forceRender from scheduleRender calls.
Useful for temporarily disabling rendering until all elements of the view have been correctly set.
Unpausing will call scheduleRender if scheduleRender was called while the view was paused.
Also adds a test for pauses and unpausing rendering using a ctkVTKSliceView.
Related issue: https://github.com/openigtlink/SlicerOpenIGTLink/issues/61

Comments addressed.

Please explain how different it is from renderEnabled.

Good point. There is a very important difference (rendering requests arriving while renderEnabled(false) makes rendering requests to be forgotten, while they are just delayed while rendering is paused) but it may not be obvious at first. I think renderEnabled is made obsolete by the new mechanism.

Thanks, I understand better. I'm not sure I would get rid of renderEnabled however. I can think of some scenarii where you really want to discard rendering requests, and when you re-activate rendering, you don't want to trigger a delayed rendering request. Maybe that behavior could be merged with the new pause rendering (e.g. resumeRender(bool i_ignorePausedRenderingRequests = false).
Here is one scenario:

you know VTK is triggering rendering requests for wrong reasons (by the vtkWidgets for example) and you don't have time/knowledge/... to investiguate the root issue, maybe you could wrap the erronous VTK code with some "render pausing" block and when you re-enable rendering, you want to discard the rendering requests. It might not be a correct but I hope you get the idea..

I agree that we should keep renderEnabled, I meant that pauseRender could replace it in most use cases.

Gotcha, then I'm all for it. Just add documentation to explain the difference between the 2 techniques and we're all set :-)

Changes made.

Changes should be implemented.

Thinking more about it, what about the following ctkVTKAbstractView API:
int ctkVTKAbstractView::setRenderPaused(bool)
int ctkVTKAbstractView::pauseRender()
int ctkVTKAbstractView::resumeRender()

where:

calling pauseRender() would increment a counter, resumeRender would decrement
pauseRender() equivalent to setRenderPaused(true) and return counter value
resumeRender() equivalent to setRenderPaused(false) and return counter value
isRenderPaused() returns true if counter > 0
if calling resumeRender() leads to a counter reaching 0, scheduleRender() is called
calling resumeRender() is counter is already 0 is equivalent to calling scheduleRender()

I think this would greatly simplify the management of paused state implemented in Slicer.  See https://github.com/Slicer/Slicer/pull/1016#issuecomment-419618055

There are two options for implementing this API:

Option A. bool pauseRender(bool)
Option B. pauseRender() / resumeRender()

I don't think it's a good idea to implement both on the public API, as they are very similar. It would just increase API complexity without significant benefits.
For me difference in ease-of-use is marginal (as both of them just two lines).
However, I've searched the Qt API a bit and found that although there is a very common example for option A (bool blockSignals(bool)), it seems that option B is chosen for more methods:
A:

QObject::blockSignals(bool)

B:

QMutex::lock()/unlock()
QWidget::grab...()/release...()
QGuiApplication::setOverrideCursor(const QCursor &cursor)/restoreOverrideCursor()

So, it seems reasonable to choose the somewhat simpler and more frequently used option B. The API would be:
int ctkVTKAbstractView::setRenderPaused(bool)
int ctkVTKAbstractView::pauseRender()
int ctkVTKAbstractView::resumeRender()
bool ctkVTKAbstractView::isRenderPaused()

Implemented the new interface:
int ctkVTKAbstractView::setRenderPaused(bool)
int ctkVTKAbstractView::pauseRender()
int ctkVTKAbstractView::resumeRender()
bool ctkVTKAbstractView::isRenderPaused()

Tested in Slicer, and the methods are callable through python.

setRenderPaused(bool) is not needed if we have pauseRender()/resumeRender()

I think keeping setRenderPaused(bool) as a slot makes sens, it allows easy connection with signal
int ctkVTKAbstractView::pauseRender()
{
  return  this>setRenderPaused(true);
}

int ctkVTKAbstractView::resumeRender()
{
  return  this>setRenderPaused(false);
}

The layout manage in Slicer would also have a similar API

I've added the warning message and fixed some formatting issues.


Example should be renamed to include simpletest

Example miniesptool_esp32multifile.py should be renamed to miniesptool_esp32multifile_simpletest.py to fit with CircuitPython library standards.

In this case, the examples are really not "simple tests" they are used to load code to the esp32 module.  A user should not run this to "see how it works".  Is "simpletest" really the appropriate name?

@jerryneedell Perhaps not. I guessed. What would be considered a simpletest for this library?

I'm not sure there really is one.  It would be like having a simpletest for a .uf2 file. If you run it , it will write the file to your board.

Fair enough. Closing this issue. I think we should consider figuring out what would be considered a simpletest for this lib though, if at all possible.

perhaps @brentru would have some ideas -- this may fit into his guide for the esp32spi...


Consistent output format

Same format as the previous "blocks".

@richlander

@richlander can you please review? This PR is two months old

do you wanna resolve the merge conflicts here @cincuranet?

Thanks!
Fixed in https://github.com/dotnet/core/pull/5579. This PR as merge conflicts (due to your other changes) and I wanted to update it anyway.

OK. No problem.


unvalidate bundle cache when lockfile changed

Hi,
This is concerning bundler caching as documented here: https://github.com/MicrosoftDocs/azure-devops-docs/blob/63e80f516fa31d7472ae14ca756f386d321053cd/docs/pipelines/release/caching.md#bundler
I found that updating/adding deps won't invalidate the cache and thus these dependencies will keep being missed and will be installed again on every run until the cache is missed, wasting previous time for things we should be able to cache.
For example

you run your pipeline a first time

there is a cache miss, bundle folder is uploaded

you add gem x to your gemfile
you run pipeline

there is a cache hit
bundle folder does not contain gem x yet
it installs gem x
there is a cache hit because the key is the same, bundle folder is not uploaded

you run pipeline

every cache hit won't have gem x so you will install it again and again

I I have done in my pipeline is to use a checksum of the lock file that way:
  - bash: |
      echo "##vso[task.setvariable variable=gemLockChecksum;]$(sha1sum Gemfile.lock)"

  # Bundle cache
  - task: Cache@2
    displayName: Bundle Cache
    inputs:
      key: 'gems | "$(Agent.OS)" | "$(gemLockChecksum)"'
      restoreKeys: |
        gems | "$(Agent.OS)"
        gems
      path: $(Build.SourcesDirectory)/.ci/volumes/bundle

I think that could be added to the documentation instead of the current example.
Thanks

You don't need the bash command. Files referenced in the cache key are hashed automatically. See Configure the Cache task for details

@ramiMSFT can you please give an example of how this can help to solve the issue I mentioned? Because right now the doc does not allow to cache rubygem as I would expect


Article links to an old version of Enterprise Deployment whitepaper

The "Planning an Enterprise Deployment Whitepaper" link at the bottom of this article points to an old July 2018 v2 file.
The newer May 2020 v3.1 that you can get at this URL. https://docs.microsoft.com/en-us/power-bi/guidance/whitepaper-powerbi-enterprise-deployment

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

ID: ea1adec6-8c0c-a72c-c165-19a72bae7cc6
Version Independent ID: a2543cc8-a37b-dde4-b0fe-5ebeb9ed2560
Content: Power BI Premium FAQ - Power BI
Content Source: powerbi-docs/admin/service-premium-faq.md
Service: powerbi
Sub-service: powerbi-premium
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi @edhans,
Thank you for your suggestion.  We've made the update and set the article to republish.
All the best,
The DOCS team


access: token based access control

See https://github.com/zenodo/zenodo-accessrequests/blob/master/zenodo_accessrequests/tokens.py

Implemented in zenodo/zenodo-accessrequests for now.


Redo dark mode

https://github.com/pacocoursey/next-themes#avoid-hydration-mismatch

On reload in dark mode, moon show up instead of sun symbol


Add batch renderer API for rendering standalone applications.

Motivation and Context
This changeset adds a general render() method to replay renderer to render into default framebuffer.
This is used by standalone applications, i.e. applications that don't create their own context, like Habitat-lab.
How Has This Been Tested
Tested locally on Habitat-lab integration prototype.
Types of changes

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

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Closing as obsolete.
After discussion, we decided to move forward with a different API for rendering with CUDA from standalone applications:
CudaPointers render(RenderTargets)


[TASK] PL1-2774 Fix Scan in ClusterClient

Not ready yet

Coverage decreased (-0.07%) to 97.198% when pulling 24002d6afac0331a5252f7306e0d16076b03c0db on PL1-2774 into 332d1957950028720a43090b1945615532019c3b on master.


try win

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin rerender

@conda-forge-admin rerender

@moorepants there needs to be an "openblas.lib" in this folder: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=270616&view=logs&j=5be07ae1-d8ba-5406-47b6-8e3a3a12f825&t=0bf03e01-0bec-5b85-5316-b1633322e895&l=422
Do you know how to resolve this?

@moorepants there needs to be an "openblas.lib" in this folder: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=270616&view=logs&j=5be07ae1-d8ba-5406-47b6-8e3a3a12f825&t=0bf03e01-0bec-5b85-5316-b1633322e895&l=422
Do you know how to resolve this?

that might work

that might work

@moorepants there needs to be an "openblas.lib" in this folder:

Why does it need to be openblas? You should be able to build against netlib's blas/lapack and it will work with other implementations like openblas. See: https://conda-forge.org/docs/maintainer/knowledge_base.html#blas

@moorepants there needs to be an "openblas.lib" in this folder:

Why does it need to be openblas? You should be able to build against netlib's blas/lapack and it will work with other implementations like openblas. See: https://conda-forge.org/docs/maintainer/knowledge_base.html#blas

Is there some reason pyshtools can only work with a specific blas implementation? If not, you should be building against the netlib versions.

Is there some reason pyshtools can only work with a specific blas implementation? If not, you should be building against the netlib versions.

It should work with any blas implementation. However, numpy distutils is supposed to autodetect the blas library if launched inside of conda build, and it failed to do so. First, I need to find out why that is happening, and then I can submit a fix.

It should work with any blas implementation. However, numpy distutils is supposed to autodetect the blas library if launched inside of conda build, and it failed to do so. First, I need to find out why that is happening, and then I can submit a fix.

what's confusing is that it does autodetect fftw3, like it is supposed to. But the blas is not found.

what's confusing is that it does autodetect fftw3, like it is supposed to. But the blas is not found.

I wonder if the windows fftw-feedstock is doing something fishy?

I wonder if the windows fftw-feedstock is doing something fishy?

the problem is that there is no 'openblas.lib' listed: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=270648&view=logs&j=5be07ae1-d8ba-5406-47b6-8e3a3a12f825&t=0bf03e01-0bec-5b85-5316-b1633322e895&l=420
it's missing!

the problem is that there is no 'openblas.lib' listed: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=270648&view=logs&j=5be07ae1-d8ba-5406-47b6-8e3a3a12f825&t=0bf03e01-0bec-5b85-5316-b1633322e895&l=420
it's missing!

There will never be an openblas.lib if built against the netlib versions of blas/lapack. If the package links against openblas.lib then I don't think the package is correctly setup. You can see all the files that are present here: https://github.com/conda-forge/lapack-feedstock/blob/master/recipe/meta.yaml. I've asked if pyshtools requires something special or unique form openblas that isn't present in the netlib versions. If it does then the standard approach may not work.

There will never be an openblas.lib if built against the netlib versions of blas/lapack. If the package links against openblas.lib then I don't think the package is correctly setup. You can see all the files that are present here: https://github.com/conda-forge/lapack-feedstock/blob/master/recipe/meta.yaml. I've asked if pyshtools requires something special or unique form openblas that isn't present in the netlib versions. If it does then the standard approach may not work.

there is nothing special required; it should be done like it's done in numpy. the autoconfiguration that I put in numpy no longer works because conda-forge changed the blas libs.
I set this aside for now because I have other things to work on. I may come back to it.

there is nothing special required; it should be done like it's done in numpy. the autoconfiguration that I put in numpy no longer works because conda-forge changed the blas libs.
I set this aside for now because I have other things to work on. I may come back to it.