Update onenote-migration-service.md

content update/fix:
updated text, added back in section with diagram.  uploaded diagram separately. update TOC separately.

Diagram is still missing and should be located in the images folder at the root of the the document set. Obviously the best option is to submit PRs which are full edits containing all the referenced assets. This does require using GitHub tooling and forks as that's how the images work. More than happy to help with the guidance and tooling, if needed, but we cannot merge this until image is also submitted.

Thank you. Will correct and resubmit.
Sent from Outlookhttp://aka.ms/weboutlook

From: Vesa Juvonen<EMAIL_ADDRESS>Sent: Tuesday, January 14, 2020 7:33 AM
To: SharePoint/sp-dev-docs<EMAIL_ADDRESS>Cc: Joanne Hendrickson<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-docs] Update onenote-migration-service.md (#5132)
Diagram is still missing and should be located in the images folder at the root of the the document set. Obviously the best option is to submit PRs which are full edits containing all the referenced assets. This does require using GitHub tooling and forks as that's how the images work. More than happy to help with the guidance and tooling, if needed, but we cannot merge this until image is also submitted.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fpull%2F5132%3Femail_source%3Dnotifications%26email_token%3DAHJJJGAJROBV63OQO7SGHH3Q5XLONA5CNFSM4KGUZDPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI5BLDI%23issuecomment-574231949&data=02|01|jhendr%40microsoft.com|30bc074d8a86450c23ac08d799072ee1|72f988bf86f141af91ab2d7cd011db47|1|0|637146128437904159&sdata=tDnc2%2BSBIg6xUcUBr6jnzMXlplWw31DCcLdW4Z10x68%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHJJJGCOBHOBZQCI6XRNYI3Q5XLONANCNFSM4KGUZDPA&data=02|01|jhendr%40microsoft.com|30bc074d8a86450c23ac08d799072ee1|72f988bf86f141af91ab2d7cd011db47|1|0|637146128437904159&sdata=DoYWj9iCJ5%2BqScHBNIxK%2B2%2Bfp6yT0QDXwgCcXCwjdxI%3D&reserved=0.

Uploaded .png file to image folder.  Will need to edit TOC to have the topic listed directly below the entry "Migrate web parts using the Migration API".


Better plugin support

I hope this is the right place.
I would like better plugin support for Sass, like how Less does it. On my project that supports both Sass and Less, I had to make my own compile command just for Sass while I could just use Less plugins for everything on the Less side. If this is done, please have actual good docs unlike Less. This would make my life easier, and it would make my app easier to use for Sass.

libsass has a plugin system, but those plugins need to be written in C/C++
Some of the preprocessing can be done via custom importers feature.


pens are bought in wrappers now

About the PR
fixes #15179 by making all pens come in chocolate bar wrappers
the type of pen can be seen by examining so dont leave them out on the floor
Media
surplus with wrapped hypo:

each pen:
https://user-images.githubusercontent.com/39013340/230535991-1a39d7fb-23e5-4c84-8e32-6823aaad5b03.mp4

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

tweak: The Syndicate has started smuggling its sinister pens inside chocolate bars.

This isn't the correct way to solve this issue. Ideally someone with a traitor mind would be able to see an alternate description of the item.

This isn't the correct way to solve this issue. Ideally someone with a traitor mind would be able to see an alternate description of the item.

That was pr'd and rejected by PJB.

This isn't the correct way to solve this issue. Ideally someone with a traitor mind would be able to see an alternate description of the item.

That was pr'd and rejected by PJB.

Huh.
Well then honestly I don't think this should go through either.

Honestly i think its pretty funny. Maybe consider giving the wrappers a unique look?

Looking back at it, it's part of the fun not knowing what you got. It's a roulette box more or less unless you directly buy it.

The entire reason this is an issue is because traitors are accidentally triggering the explosive pen and killing themselves while trying to check what type of pen it is. Just remove explosive pens from surplus crates, problem solved.

I agree with keron that the best solution would be allowing traitors to know what type of pen it is on examine (which would also be nice for all the other stealthy traitor items that we keep removing unique descriptions from), but if PJB doesn't want that then removing the explosive pen from the surplus crate is the next best solution.

Why is removing the pen from the surplus any better than what this PR does? Removing the pen makes the surplus just a tiny bit less random, while this PR doesn't have any similar drawbacks.

One way to fix the problem could be to put a manifest on the surplus outlining all items contained within, using uplink names rather than examine names. Then again, it still wouldn't fully solve the problem of cluelessly activating the pen and dying.

what if the manifest says there's an e-dagger and an exploding pen?

well then that's funny

Good point. That is a rather unlikely occurrence, though.
I suppose some sort of logic could be implemented to put wrappers only on ambiguous items and only when they're in a surplus, but that may be out of scope.
Ultimately this PR is probably fine as it is.

i think this PR is fine as is

I think you should give the pen wrappers a unique sprite

like a modified chocolate bar or completely separate

The ideal solution would be for Traitor PDA to show what type of pen is inserted in it.
It keeps traitors just like every other player (how PJB wanted) and just lets them use their unique PDA which they can lose

I like this solution but it will be cooler if it wouldn't use chocolate wrappers.

committed toolbox again somehow lovely

@Emisse gave each funny pen a unique box is it good now


Add Python requests module to Dockerfile

After #2010 the Python requests module was dropped from the Docker image.  This adds it back.

build

This seems not enough. At least we need to add the module request:
13:57:43      import requests
13:57:43  ModuleNotFoundError: No module named 'requests'

I manually verified the requests module can be imported after this change, so my guess is that the CI ran in a stale Docker image.


Entity Framework gets slow in long Iteration Loops

Hello,
With the current setup, if we do long insert iteration loops through the use of a repository, Entity Framework will get slower and slower creating real performance issues.
I believe this is due to the dbContext maintaining all past insertions in cache. Also, we cannot use something like:
using (EfRepository<T> repo = new EfRepository<T>)
{
    .....
}

because the dbContext will be disposed and be unavailable to the repository on the next iteration.
Is there a way to configure StructureMap to allow us to use the above using clause (in the cases we deem it needed), with StructureMap providing a new instance of the dbContext? (Preferably maintaining the current behavior when we don't wish to use the using clause)
Thank you!
Damião Dias

The default EF Core lifetime is Scoped, which has nothing to do with StructureMap (but StructureMap will use this if it's used as the container as in this case). If you want to create separately-scoped instances of DbContext, you can create child scopes as described here:
https://stackoverflow.com/questions/43722463/how-to-create-a-child-scope-from-the-parent-with-default-dependency-injection-in
You might at that point need to pass the dbContext into a new instance of a repo you create yourself, rather than requesting one from the container. Let me know if that helps/makes sense.

Sorry it took me so long to get back to this.
I did not manage to solve the issue using your suggestion, but I'll leave here my workaround, in case it can be useful to someone else.
Basically I had a set of events that lead to a loop on 1000+ insertions, and as the dbContextkept everything in memory, it started to get slower and slower...
My solution was to detach all entities from the dbContext after each insertion, as they were not needed anymore.
...
// The event handler that dealt with the 1000+ similar events and thus generated 1000+ inserts
public void HandlePost(MyEntityCreatedEventPost domainEvent)
{
    ...
    _aggregate.Insert(entity);  // note: does a dbContext.SaveChanges()
    _aggregate.DetachAll();
    ...
}

// And the cleanup method to keep the dbContext nimble
public void DetachAll()
{
    foreach (EntityEntry dbEntityEntry in _dbContext.ChangeTracker.Entries().Where(e => e.Entity != null).ToList())
    {
        dbEntityEntry.State = EntityState.Detached;
    }
}


abstract middleware metrics

Codecov Report

Merging #173 (5359db0) into main (fd42a00) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #173   +/-   ##
=======================================
  Coverage   36.25%   36.25%
=======================================
  Files          14       14
  Lines        1015     1015
=======================================
  Hits          368      368
  Misses        599      599
  Partials       48       48

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


RHIROS-793 event producer for notifications

Thanks @r14chandra :ok_hand::tada::ice_cream: for addressing all comments & driving end to end notification integration


[elixir] Fix typo in function namespace

This pull request fixes the following error :
Error detected while processing [...]/neomake/autoload/neomake/makers/ft/elixir.vim:
line   29:
E746: Function name does not match script file name: neomake#markers#ft#elixir#dogma
Error detected while processing function neomake#Make:
line    3:
E171: Missing :endif

Thanks!
We should really have some test that actually sources and runs all makers somehow.
But for that it would be best to also have input that is targeted at them.  But we could have tests without that already.


Fix error when ZSH_VERSION is unset.

When set -u is specified, export.sh currently fails in bash.

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

Thanks for your contribution.

This has been cherry-picked as https://github.com/espressif/esp-idf/commit/d20a5c39da03f7b955c6de8438e405dee4cc0cb0, thanks again for your PR @reitermarkus!


better detection and rejection of corrupt images

TL;DR - need a way to detect and delete images with corrupt jpeg data to prevent them from messing up startrails and keograms.
For reasons not clear to me, some of the jpgs written to disk are corrupt, causing startrails to complain like this:
[5367/8285] image-20190924030959.jpg 0.142903
[5368/8285] image-20190924031003.jpg 0.142869
Corrupt JPEG data: bad Huffman code
[5369/8285] image-20190924031007.jpg 0.425546
[5370/8285] image-20190924031011.jpg 0.142781
[5371/8285] image-20190924031015.jpg 0.142778

and:
[6918/8285] image-20190924045609.jpg 0.150468
[6919/8285] image-20190924045613.jpg 0.15043
Corrupt JPEG data: 1146 extraneous bytes before marker 0xd9
[6920/8285] image-20190924045617.jpg 0.204732
[6921/8285] image-20190924045621.jpg 0.150463
[6922/8285] image-20190924045625.jpg 0.150506

which leads to strange startrail images like this.

The only possibly weird thing in dmesg is a few of these:
[134352.478664] usb 1-1.3: reset high-speed USB device number 6 using dwc_otg
[138920.669298] usb 1-1.3: reset high-speed USB device number 6 using dwc_otg
[141612.344527] usb 1-1.3: reset high-speed USB device number 6 using dwc_otg

but nothing in the allsky capture log indicating a capture error or failure to compress.
If I delete all the images with corrupt jpeg data and rerun startrail I get a much better looking image.

Regarding the message reset high-speed USB device number 6 using dwc_otg, this is basically saying that the connection to the camera was reset because of some issue (low voltage could be causing it).
I had this kind of issue happen to me on a RPi4 using the USB3 and powered with the RPi3 power supply (2.5V instead of 3V).
This could also happen because of a long or low quality USB cable.

I'm using the USB cable that came with my ZWO ASI120MM-S, but I'll see about swapping it for a shorter cable.
Was just checking into the power supply; I made sure to get a good 3A, 5.2V supply (to account for cable loss), and neither dmesg nor vcgencmd get_throttled give any indication of undervoltage events.

FYI, for long power runs I've used https://www.amazon.com/gp/product/B018X0BAYS.. so I'm actually sending 48V about 500ft and using that to convert it to 5V.

My power run is only 5ft. But thanks for the pointer to that buck converter, it might be useful for some other outdoor projects I'm working on.


Scan .git for large files

The .git folder is 286 MB. It should be scanned for large files that were accidentally committed and if there are any, they should be removed.

The culprit was sphinx's .doctrees/environment.pickle file, which is a cache every time the docs are built.


chore(apiaccess): Updated CreatedAt attr to nrtime.EpochSeconds

Changed EpochSeconds to nrtime.EpochSeconds.  This appears to be the correct golang time to handle createdAt fields returned in NerdGraph responses

Codecov Report

Merging #1038 (03c15d4) into main (0bcddff) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1038   +/-   ##
=======================================
  Coverage   41.62%   41.62%
=======================================
  Files          79       79
  Lines        4956     4956
=======================================
  Hits         2063     2063
  Misses       2745     2745
  Partials      148      148

Flag
Coverage Δ

unit
41.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

internal/http/client.go
69.49% <ø> (ø)

internal/http/graphql.go
46.51% <ø> (ø)

pkg/apiaccess/keys.go
0.00% <ø> (ø)

pkg/entities/entities_api.go
0.00% <ø> (ø)

pkg/synthetics/monitor_scripts.go
0.00% <ø> (ø)

pkg/synthetics/monitors.go
76.92% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


chore: remove unnecessary fields from bug template

Description of changes
When triaging issues, some of the fields do not provide much value for diagnosis, and instead can become a hurdle to filing issues. We can help narrow the focus and reduce the time of filing the report by removing the following fields:

removes section for Amplify Commands
removes section for Amplify Categories
removes section for GraphQL Schema (this no longer applies to the CLI repo)

I have also considered removing the checklist at the beginning of the document in favor of one of the following:

remove entirely
move to the end of the document (to align with wording of checklist heading, "Before submitting...")
remove in favor of noting the following at the top of the documentBe sure to read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/dev/CONTRIBUTING.md#bug-reports)

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

With the checklist at the beginning of the document its contents may be glossed over in order to dive into the details of the issue experienced. Moving the checklist to the end of the document serves as a final checklist before submitting where it may be more meaningful
UPDATE 2022-10-07:

condensed checklist
moved checklist to end of document
added note for reading bug report submission guide at the beginning of the document

Issue #, if available

Description of how you validated changes
Checklist

[x] PR description included

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #11121 (957c2c1) into dev (24dd409) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev   #11121   +/-   ##
=======================================
  Coverage   49.64%   49.64%
=======================================
  Files         666      666
  Lines       31916    31916
  Branches     6497     6497
=======================================
+ Hits        15845    15846    +1
+ Misses      14591    14590    -1
  Partials     1480     1480

Impacted Files
Coverage Δ

...li/src/domain/amplify-usageData/getUsageDataUrl.ts
100.00% <0.00%> (+12.50%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

thanks for improving the developer experience of our contributors!

Providing common troubleshooting documentation links that can be added to issue template:
CLI/GraphQL: https://docs.amplify.aws/cli/project/troubleshooting/
GraphQL: https://docs.amplify.aws/cli/graphql/troubleshooting/#backfill-opensearch-index-from-dynamodb-table

I did not mean to start a review 😵


Can classes be added rows at a table?

Can classes be added rows at a table?
This example is manually inserted through the browser:

Originally posted by @swara-mohammed in https://github.com/laravel-filament/filament/discussions/1481

Not yet, please don't use Issues for questions / feature requests


Fix arithmetic expression overflow

If the value of a->length is large (>= 2^12), then an integer overflow will occur for the signed type, which according to the C standard is UB.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
CLA: trivial

This pull request is ready to merge


BodySetup access

Hi,
In the PMC, a function GetBodySetup allow us to access to the bodySetup of a PMC . I saw that in the RMC you made the bodySetup directly accessible via a pointer but it is always empty for me(Not containing any convex).
Best,

Well the convex objects aren't handled there currently, and instead is handled currently more like the PMC. With that the body setup only has them after it's cooked. What are you trying to do with them though?

Hi,
I am trying to duplicate the RMC.

Ah… yeah… Well the best solution is to query the convex elements directly and copy those.  I believe It’s just RMC->ConvexCollisionSections.
Unfortunately what you’re doing will require multiple full copies of the mesh data on both main ram and vram + multiple mesh copies in PhysX… So I’d be careful on the quantity. With that said this is one of the driving reasons for the complete rewrite I’m currently doing so “Instancing” will be directly supported in the next version hopefully.
From: Swann Martinez<EMAIL_ADDRESS>Sent: Wednesday, January 4, 2017 5:40 AM
To: Koderz/UE4RuntimeMeshComponent<EMAIL_ADDRESS>Cc: Chris Conway<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Koderz/UE4RuntimeMeshComponent] BodySetup access (#18)
Hi,
I am trying to duplicate the RMC.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Koderz/UE4RuntimeMeshComponent/issues/18#issuecomment-270342316, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGLUYGdmZv-SiBFZhFzmIQjrYTI1VBijks5rO3brgaJpZM4LNczx.

Thank you :)


Properly support extended, experimental field Spec.CommonRouteSpec.ParentRefs[*].Port in TCPRoute & UDPRoute

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
Currently only field Spec.CommonRouteSpec.ParentRefs[*].SectionName is properly supported, see

https://github.com/Kong/kubernetes-ingress-controller/pull/4928

that fixes

https://github.com/Kong/kubernetes-ingress-controller/issues/4864

Setting Spec.CommonRouteSpec.ParentRefs[*].Port does not have any effect. It should work as described in the specification.
Proposed Solution
Implement support for Port field as described in the gateway-api spec.
Additional information
Conformance tests in gateway-api repo for checking this doesn't exist when it was been written. Ensure that is properly tested, consider adding such test to the upstream.
Acceptance Criteria

[ ] field Spec.CommonRouteSpec.ParentRefs[*].Port works as described in spec for TCPRoute & UDPRoute
[ ] it is properly tested

Could you please assign this to me? thanks!


edit "why performance matters" to use less and simpler words

What's changed, or what was fixed?

remove extraneous sentences
replace big words with simpler synonyms

Fixes: N/A
Target Live Date: 2018-10-05

[x] This has been reviewed and approved by @kaycebasques
[x] I have run npm test locally and all tests pass.
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

Whoops!
There were 1 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/performance/why-performance-matters/index.md#L188 - Line must be at most 100 characters


Clarify use of repository and context claims in OIDC setup

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect
What part(s) of the article would you like to see updated?
The article contains a list of possible claims here.
Repository claim
One of these claims is repository, which corresponds to repository name and the owner. However, the subject examples do not reference this claim name but rather repo:
repo:octo-org/octo-repo:environment:prod

In the above subject, environment is a claim listed in table of available claims but repo is not listed. Additionally, the API accepts repo but not repository. This sample also only talks about repo.
A clarification of this claim would be nice.
Context claim
This section talks about using context.
It goes on to say:

This example also demonstrates how to use "context" to define your conditions. This is the part that follows the repository in the default sub format. For example, when the job references an environment, the context contains: environment:.

I can't piece this one together from the available informationl. What can contextcontain? If it is always everything after repo, what happens when I customize my token claims?
The default sub format then mentions the job context, which in turn doesn't mention environment as a part of that context.
Some more samples to clarify the use of context would be nice.
Additional information
No response

@johanredeploy Thanks so much for opening an issue! I'll triage this for the team to take a look :eyes:

Sorry, I forgot to mention one thing above.
Example: Granting access to a specific repository links to Customizing the token URL for an enterprise, which seems to lead nowhere.

I'm not sure what the hold up has been with this. I'll get some expert 👀 to take a look at this.
As regards this:

Example: Granting access to a specific repository links to Customizing the token URL for an enterprise, which seems to lead nowhere.

The link seems to have been fixed now.

An SME in this area has told me:

repo is the same as repository. repo prefix in the subject claim contains NWO for the repository. repository claim in ID token would have the same data.

I don't personally know enough about this area to determine exactly what changes we need to make. If anyone reading this issue feels confident to suggest changes then it would be great if you can create a pull request and we can get a technical review of it.
Meanwhile I'll continue looking for some more assistance with this.

I see the documentation on this page has clarified the use of repo:, which is awesome, but I'm struggling to find examples or expectations regarding the "context" claim. As such, I'm not sure if the section of the original Issue on "context" was addressed or not.
I can see some examples that result in environment:prod being provided if "context" is given, but is that the limit to what it includes? If "context" isn't defined elsewhere, is this page a good place to define its purpose and contents? Otherwise, I'm inclined to assume it has nothing and use other claims in my tokens to guarantee it has what I require.

Hello @TomChapple 👋 !

I can see some examples that result in environment:prod being provided if "context" is given, but is that the limit to what it includes? If "context" isn't defined elsewhere, is this page a good place to define its purpose and contents?

Given the age of this issue, we'd recommend opening a new one within this repo that includes the questions you mentioned above. This will also likely be the fastest way to get a response from the team 💛


Make std::random_device generate true random numbers (IDFGH-10124)

Is your feature request related to a problem?
I intended to use a real random number generator for cryptographic purposes. So, I choose std::random_device, which should be a platform independent way that is able to return real random numbers.
However, the generator produces the same value<PHONE_NUMBER> every time the ESP32 is powered on, which is not random.
Sketch to reproduce problem (using Arduino core):
#include <random>
void setup()
{
 Serial.begin(115200);
 ... // wait until Serial is ready;
 std::cout << std::random_device()();
}

Original post: espressif/arduino-esp32#8201
Describe the solution you'd like.
I do know that ESP32 support a hardware random number generator for producing true random numbers. Maybe using that to implement std::random_device?
Describe alternatives you've considered.
No response
Additional context.
No response

We'll take a look if we can integrate the RNG into std::random_device and keep you updated about the results.
If you currently want to use the random number generator of an ESP32 chip, e.g., you can refer to the Random number generation documentation page. It explains the API and the conditions that need to be met to produce real random numbers.
Please note that std::random_device does not have to produce real (i.e., non-deterministic) random numbers:

std::random_device may be implemented in terms of an implementation-defined pseudo-random number engine if a non-deterministic source (e.g. a hardware device) is not available to the implementation. In this case each std::random_device object may generate the same number sequence.

(from std::random_device cppreference page)
If you really want to use std::random_device for cryptographic purposes, I strongly recommend checking the entropy via std::random_device::entropy first. Otherwise, you may end up with insecure RNGs depending on the platform you use. For ESP32, std::random_device::entropy currently returns 0.

@Zhu-jiatong please let us know if esp_random() works for you.
In a meanwhile we have decided improve std::random_device. This will require adding getentropy() implementation in ESP-IDF's newlib and then configuring the toolchain to use it. This patch however will be available later in Q3.

Thank you for your information. The esp_random() does work. I am looking forward to the addition of std::random_device.

From: Zim Kalinowski @.>
Sent: 18 May 2023 18:02
To: espressif/esp-idf @.>
Cc: Tony Zhu (Q-2020) @.>; Mention @.>
Subject: Re: [espressif/esp-idf] Make std::random_device generate true random numbers (IDFGH-10124) (Issue #11398)
@Zhu-jiatonghttps://github.com/Zhu-jiatong please let us know if esp_random() works for you.
In a meanwhile we have decided improve std::random_device. This will require adding getentropy() implementation in ESP-IDF's newlib and then configuring the toolchain to use it. This patch however will be available later in Q3.
—
Reply to this email directly, view it on GitHubhttps://github.com/espressif/esp-idf/issues/11398#issuecomment-1552825222, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXQECHSXJBTRHFIJ6AOSECDXGXXUPANCNFSM6AAAAAAYBASUUA.
You are receiving this because you were mentioned.Message ID: @.***>


TextAlignment GFX not working in PXmatrix library

Dear All,
I am trying to use the TextAlignment function of GFX in the display PxMatrix library but this GFX function is not available. Is there an alternative present in the library to use to get a center aligment on the text instead of a left top corner alignment?

Hi ... can you point to where this is implemented? Cannot find anything in AdafruitGFX.

2dom
Here is a reference I have found on the internet
https://forum.pjrc.com/threads/31939-ILI9341_t3-draw-centered-text-string

Doesn't seem to be part of the standard AdafruitGFX - you could try adding that section to your local copy of AdafruitGFX. This issue is not related to PxMatrix....closing


Fix missing WARC-Concurrent-To fields (#20)

This should finally fix #20 even though it needs some deeper testing, the script used in #18 generates the expected WARC.

@BubuAnabelas thanks for this! Hey if you would want to help out with creating some tests that would be awesome. Thats next on my list.....


Add new exercise sieve

I will port this from the JS track.

Closed by #101
Thanks @matthewmorgan


Bug: daysInMonth giving wrong values

I've never had problems with this until now. I couldn't find anything but flutter probably did update DateTime.weekday property, which make this plugin give wrong values.
Problem
Utils.daysInMonth(DateTime(2018, 9)) give us days from 26/oct to 29/sep, missing 30/sep to 6/oct.
This plugin calculates the last day by using:

var daysAfter = 7 - last.weekday;
var lastToDisplay = last.add(new Duration(days: daysAfter));

Weekday property says:
The day of the week [monday]..[sunday].

In accordance with ISO 8601
   * a week starts with Monday, which has the value 1.

Which means Sunday receives the value of 7, and the formula this plugin uses add 0 days.
Since I didn't saw this problem before and this plugin would be correct if Sunday would be 0, I think flutter team updated it.
Solution
Basically just transform Sunday into 0 again. I'm using daysInRange manually until this plugin is updated, hopefully soon.
var lastWeekday = last.weekday % 7;
var daysAfter = 7 - lastWeekday;
var lastToDisplay = last.add(new Duration(days: daysAfter));

This is fixed by https://github.com/apptreesoftware/date_utils/pull/7 - thanks!


'Tolgee' is not exported from '@tolgee/react'

We've been following this guide for Tolgee in Next with the app router a couple of months ago but we always had issues when the language is changed using lang toggle. The currently rendered page translates to the new language but going to some other page there is the chance it is still shown with the previously selected language...
Anyway, we see that the guide has been updated a bit with the new versions on tolgee/web, tolgee/react and next-intl, so we tried updating the libs and changing the latest stuff from the guide hoping it will fix our previous errors.
This new error happens on versions greater than:
"@tolgee/react": "^5.22.0",
"@tolgee/web": "^5.22.0",

It's present even on yesterday's latest version (5.28.5).

./tolgee/shared.ts
Attempted import error: 'Tolgee' is not exported from '@tolgee/react' (imported as 'Tolgee').
Import trace for requested module:
./tolgee/shared.ts
./tolgee/shared.ts
Attempted import error: 'FormatSimple' is not exported from '@tolgee/react' (imported as 'FormatSimple').
Import trace for requested module:
./tolgee/shared.ts
./tolgee/shared.ts
Attempted import error: 'DevTools' is not exported from '@tolgee/react' (imported as 'DevTools').
Import trace for requested module:
./tolgee/shared.ts
⚠<EMAIL_ADDRESS>Attempted import error: 'getFallbackArray' is not exported from '@tolgee/web' (imported as 'getFallbackArray').
Import trace for requested module:
<EMAIL_ADDRESS>./tolgee/shared.ts
<EMAIL_ADDRESS>Attempted import error: 'getTranslateProps' is not exported from '@tolgee/web' (imported as 'getTranslateProps').
Import trace for requested module:
<EMAIL_ADDRESS>./tolgee/shared.ts

Hey, we had this issue reported previously and users reported, that they were able to fix it either by upgrading next.js or tsconfig.json, so please try that. I would like to know what exactly is causing this, but I was not able to replicate.

Updating next to 14.2.4 resolves the 'Tolgee' is not exported from '@tolgee/react' issue. However, still when everything is upgraded to the latest versions and the files from the guide updated too we have that tolgee language switch issue present. Should I create a new issue for that here?
Here are the current versions:
"@tolgee/react": "^5.28.5",
"@tolgee/web": "^5.28.5",
"next": "14.2.4",
"next-intl": "3.15.3"


Moved quickstart/explain/index to configure/explain/index

@mirons-google Can you take another pass at this PR?

Hey @Tabrarian , can you take another pass at this PR?


ASAP implementation

Basic ASAP implementation and test set on NYC taxi.
Right now the operator assumes that the incoming datum only has two metrics: timestamp and value.

Coverage remained the same at 94.228% when pulling fae48de5a59f142a2e6f80a54bb187c8e6c4c278 on kexinrong:ASAP-mb into f18a04622d46f331d53b0646e288dc1076addfe5 on stanford-futuredata:master.

@kexinrong is this ready for review? I have some time over the next few days to review...

@pbailis Yes I think it is ready for review

Closing due to inactivity; code available on http://futuredata.stanford.edu/asap/


Build Error on Mac OS Regarding PexPython and UI component

My Mac OS has python 2.7.11, and I encountered the following error from a fresh build:
$ bazel build --config=darwin heron/...

INFO: From PexPython heron/ui/src/python/heron-ui.pex:
Traceback (most recent call last):
  File "bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex", line 105, in <module>
    Main()
  File "bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex", line 84, in Main
    'Cannot exec() %r: file not found.' % main_filename
AssertionError: Cannot exec() '/private/var/tmp/_bazel_zzhang/3964dd02d192385870c24d7a89344f18/heron/bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex.runfiles/3rdparty/pex/_pex.py': file not found.
ERROR: /Users/zzhang/workspace/heron/heron/ui/src/python/BUILD:18:1: null failed: _pex failed: error executing command bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex --not-zip-safe --entry-point heron.ui.src.python.main bazel-out/local_darwin-fastbuild/bin/heron/ui/src/python/heron-ui.pex ... (remaining 1 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.

Just wondering if you followed the instructions in the page
http://twitter.github.io/heron/docs/developers/compiling/mac/

@kramasamy Yes, I did, but got stuck in Step 8 due to the build error above.

That's really strange. the _pex.py file can't another instance of find itself. Can you try changing Trace.shsout_log to return True and see what you get:
https://github.com/twitter/heron/blob/master/3rdparty/pex/pex/tracer.py#L64
You'll also want to pass --verbose_failures to bazel build.

@billonahill Changing Trace.should_log does not print out any new error info, but enabling --verbose_failures does (see below).
INFO: From PexPython heron/ui/src/python/heron-ui.pex:
Traceback (most recent call last):
  File "bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex", line 105, in <module>
    Main()
  File "bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex", line 84, in Main
    'Cannot exec() %r: file not found.' % main_filename
AssertionError: Cannot exec() '/private/var/tmp/_bazel_zzhang/3964dd02d192385870c24d7a89344f18/heron/bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex.runfiles/3rdparty/pex/_pex.py': file not found.
ERROR: /Users/zzhang/workspace/heron/heron/ui/src/python/BUILD:18:1: null failed: _pex failed: error executing command
  (cd /private/var/tmp/_bazel_zzhang/3964dd02d192385870c24d7a89344f18/heron && \
  exec env - \
  bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex --not-zip-safe --entry-point heron.ui.src.python.main bazel-out/local_darwin-fastbuild/bin/heron/ui/src/python/heron-ui.pex bazel-out/local_darwin-fastbuild/bin/heron/ui/src/python/heron-ui.pex.manifest): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1: _pex failed: error executing command
  (cd /private/var/tmp/_bazel_zzhang/3964dd02d192385870c24d7a89344f18/heron && \
  exec env - \
  bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex --not-zip-safe --entry-point heron.ui.src.python.main bazel-out/local_darwin-fastbuild/bin/heron/ui/src/python/heron-ui.pex bazel-out/local_darwin-fastbuild/bin/heron/ui/src/python/heron-ui.pex.manifest): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.

@zuyu looks like 3rdparty/pex/_pex failed to execute without much messaging as to why. Specfically this:
cd /private/var/tmp/_bazel_zzhang/3964dd02d192385870c24d7a89344f18/heron && \
  exec env - \
  bazel-out/local_darwin-fastbuild/bin/3rdparty/pex/_pex --not-zip-safe --entry-point \
  heron.ui.src.python.main bazel-out/local_darwin-fastbuild/bin/heron/ui/src/python/heron-ui.pex bazel-out/local_darwin-fastbuild/bin/heron/ui/src/python/heron-ui.pex.manifest

Best way to debug would be to add some print statements into 3rdparty/pex/_pex to see identify it's failing and improve the messaging.

I have no build errors in another Mac laptop, although the origin one still has the same build issue.


How do we want to handle page titles?

We currently rely on title to generate the <title>. However, with the introduction of https://github.com/rails/rails/pull/49702, do we still feel we need this dependency?
If we want to continue using title, I think we'll need to ensure the existing regex still works.

If Suspenders continues using the Title gem, it would be helpful for the app to add the titles/application keys to en.yml so that the user knows where that value is coming from, as demonstrated in the Title README.
Without the keys in en.yml, Title defaults to something (possibly the project name), and the string value is not searchable in the project to know where to change it. You have to look at the application layout, see the title reference, then notice that  title is in the Gemfile, then read their README to figure out how to set it.
Suggested addition:
en:
  hello: 'Hello world'
  titles:
    application: Hello World

@stevepolitodesign Do you think a separate issue about this would be helpful, or is it better to keep it contained here for the moment until we decide whether or not to use Title?

I personally think that in the spirit of keeping Suspenders as close to rails new as possible, we should remove our dependency on title.
Let's see what others have to say, and if we find that we want to keep our dependency with title, then we can close this issue and open a new one with your suggested improvements.


Support all D3 scales

The following scales should be supported by the Scale mixin:

[ ] scaleBand
[ ] scalePoint
[ ] scaleIdentity
[ ] scaleLinear
[ ] scaleLog
[ ] scaleOrdinal
[ ] scaleImplicit
[ ] scalePow
[ ] scaleSqrt
[ ] scaleQuantile
[ ] scaleQuantize
[ ] scaleThreshold
[ ] scaleTime
[ ] scaleUtc
[ ] scaleCategory10
[ ] scaleCategory20b
[ ] scaleCategory20c
[ ] scaleCategory20
[ ] scaleSequential
[ ] scaleCubehelix
[ ] scaleRainbow
[ ] scaleWarm
[ ] scaleCool
[ ] scaleViridis
[ ] scaleMagma
[ ] scaleInferno
[ ] scalePlasma

Some of these define their own ranges. Those ranges should be used.

Part of #7

New module with more scales d3-scale-chromatic.
It should be possible to use any of these scales, and change the scale at runtime via a reactive property.

Now, the Scale mixin takes as input a scale constructor, and sets up a reactive function that sets its domain and range. This change makes it possible to use all scale types that depend only on domain and range to function.


User locking

UserManager locking as mentioned in #52
Added simple test, but testing is not easy now, as app contains some global variables (default content dir must exist for example).

@johniez I know I am asking a lot, but would you be willing to write some tests around user management so we can see whether this stuff will be compatible on python2 and python3?

@alexanderjulo Yes, I can write some tests for this.

Closing this PR due to lack of activity.


Train on custom dataset

Hi! How are you?
I found that tsdiff could be a great tool for generating eeg data. I have a dataset containing the channels measurements from an eeg obtained in an experiment and I would like to train your model with this data. How should I do in order to train your model with a custom dataset?
Thanks!

Hi @tomyjara!
You can use something like this to build a custom dataset.

Create a JSON lines file with your time series data. Basically every line has one time series in JSON format with two keys, start (the start time stamp) and target (the actual time series). I have attached an example file. Note that the time series are not required to have the same start or length.

Use this function to load the file as a GluonTS dataset.

from pathlib import Path

from gluonts.dataset.split import split
from gluonts.dataset.common import (
    MetaData,
    TrainDatasets,
    FileDataset,
)

def get_custom_dataset(
    jsonl_path: Path,
    freq: str,
    prediction_length: int,
    split_offset: int = None,
):
    """Creates a custom GluonTS dataset from a JSONLines file and
    give parameters.

    Parameters
    ----------
    jsonl_path
        Path to a JSONLines file with time series
    freq
        Frequency in pandas format
        (e.g., `H` for hourly, `D` for daily)
    prediction_length
        Prediction length
    split_offset, optional
        Offset to split data into train and test sets, by default None

    Returns
    -------
        A gluonts dataset
    """
    if split_offset is None:
        split_offset = -prediction_length

    metadata = MetaData(freq=freq, prediction_length=prediction_length)
    test_ts = FileDataset(jsonl_path, freq)
    train_ts, _ = split(test_ts, offset=split_offset)
    dataset = TrainDatasets(metadata=metadata, train=train_ts, test=test_ts)
    return dataset

This get_custom_dataset can be used as a replacement for https://github.com/amazon-science/unconditional-time-series-diffusion/blob/50f52da1c583d2eece4da8e933f34b73dc249a75/bin/train_model.py#L135
Modify the default config appropriately, especially the context length, lags, etc.

Thanks @marcelkollovieh for helping with the response!

tsdiff) rrr@rr:~/unconditional-time-series-diffusion$ python bin/train_model.py -c configs/train_fdr.yaml
DEBUG:root:Before importing pykeops...
DEBUG:root:After importing pykeops!
INFO:uncond_ts_diff.arch.s4:Pykeops installation found.
WARNING: Skipping key sampler_params!
WARNING:root:Cannot infer loader for /home/h/unconditional-time-series-diffusion/data/fdr/CAS/dummy_custom_data.json:Zone.Identifier.
WARNING:root:Cannot infer loader for /home/h/unconditional-time-series-diffusion/data/fdr/CAS/train - 副本.json:Zone.Identifier.
WARNING:root:Cannot infer loader for /home/h/unconditional-time-series-diffusion/data/fdr/CAS/dummy_custom_data.json:Zone.Identifier.
WARNING:root:Cannot infer loader for /home/h/unconditional-time-series-diffusion/data/fdr/CAS/train - 副本.json:Zone.Identifier.
GPU available: True (cuda), used: True
TPU available: False, using: 0 TPU cores
IPU available: False, using: 0 IPUs
HPU available: False, using: 0 HPUs
INFO:bin/train_model.py:Logging to ./lightning_logs/version_44
/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/trainer/configuration_validator.py:108: PossibleUserWarning: You defined a validation_step but have no val_dataloader. Skipping val loop.
rank_zero_warn(
You are using a CUDA device ('NVIDIA GeForce RTX 4060 Laptop GPU') that has Tensor Cores. To properly utilize them, you should set torch.set_float32_matmul_precision('medium' | 'high') which will trade-off precision for performance. For more details, read https://pytorch.org/docs/stable/generated/torch.set_float32_matmul_precision.html#torch.set_float32_matmul_precision
LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0]
┏━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━┓
┃   ┃ Name     ┃ Type            ┃ Params ┃
┡━━━╇━━━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━┩
│ 0 │ scaler   │ MeanScaler      │      0 │
│ 1 │ embedder │ FeatureEmbedder │      1 │
│ 2 │ backbone │ BackboneModel   │  193 K │
└───┴──────────┴─────────────────┴────────┘
Trainable params: 193 K
Non-trainable params: 0
Total params: 193 K
Total estimated model params size (MB): 0
DEBUG:fsspec.local:open file: /home/h/unconditional-time-series-diffusion/lightning_logs/version_44/hparams.yaml
DEBUG:fsspec.local:open file: /home/h/unconditional-time-series-diffusion/lightning_logs/version_44/hparams.yaml
Epoch 0/99 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0/-- 0:00:00 • -:--:-- 0.00it/s
Traceback (most recent call last):
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/dataset/jsonl.py", line 127, in iter
yield json.loads(line)
orjson.JSONDecodeError: unexpected end of data: line 2 column 1 (char 3)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "bin/train_model.py", line 286, in
main(config=config, log_dir=args.out_dir)
File "bin/train_model.py", line 224, in main
trainer.fit(model, train_dataloaders=data_loader)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 608, in fit
call._call_and_handle_interrupt(
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/trainer/call.py", line 38, in _call_and_handle_interrupt
return trainer_fn(*args, **kwargs)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 650, in _fit_impl
self._run(model, ckpt_path=self.ckpt_path)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1112, in _run
results = self._run_stage()
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1191, in _run_stage
self._run_train()
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1214, in _run_train
self.fit_loop.run()
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/loops/loop.py", line 199, in run
self.advance(*args, **kwargs)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/loops/fit_loop.py", line 267, in advance
self._outputs = self.epoch_loop.run(self._data_fetcher)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/loops/loop.py", line 194, in run
self.on_run_start(*args, **kwargs)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/loops/epoch/training_epoch_loop.py", line 160, in on_run_start
_ = iter(data_fetcher)  # creates the iterator inside the fetcher
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/utilities/fetching.py", line 180, in iter
self.prefetching()
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/utilities/fetching.py", line 243, in prefetching
self._fetch_next_batch(iterator)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/utilities/fetching.py", line 280, in _fetch_next_batch
batch = next(iterator)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/trainer/supporters.py", line 571, in next
return self.request_next_batch(self.loader_iters)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/pytorch_lightning/trainer/supporters.py", line 583, in request_next_batch
return apply_to_collection(loader_iters, Iterator, next)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/lightning_utilities/core/apply_func.py", line 64, in apply_to_collection
return function(data, *args, **kwargs)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/itertools.py", line 181, in iter
yield from itertools.islice(self.iterable, self.length)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/transform/_base.py", line 103, in iter
yield from self.transformation(
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/transform/_base.py", line 124, in call
for data_entry in data_it:
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/dataset/loader.py", line 37, in call
yield from batcher(data, self.batch_size)
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/itertools.py", line 100, in get_batch
return list(itertools.islice(it, batch_size))
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/transform/_base.py", line 178, in call
for data_entry in data_it:
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/itertools.py", line 77, in iter
for el in self.iterable:
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/itertools.py", line 125, in iter
for element in self.iterable:
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/transform/_base.py", line 103, in iter
yield from self.transformation(
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/transform/_base.py", line 124, in call
for data_entry in data_it:
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/transform/_base.py", line 124, in call
for data_entry in data_it:
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/transform/_base.py", line 124, in call
for data_entry in data_it:
[Previous line repeated 8 more times]
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/dataset/init.py", line 56, in iter
yield from self.iter_sequential()
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/dataset/init.py", line 47, in iter_sequential
yield from dataset
File "/home/h/anaconda3/envs/tsdiff/lib/python3.8/site-packages/gluonts/dataset/jsonl.py", line 129, in iter
raise GluonTSDataError(
gluonts.exceptions.GluonTSDataError: Could not read json line 0, b'{\r\n'
I've used dummy json as train.json, but the error comes out as above


trying to get basic example working

i could just be dumb but i cant get a simple unified version the basic NextJS code from the quickstart working:
in my [...ts-rest].tsx
import { initContract } from "@ts-rest/core"
import { createNextRoute, createNextRouter } from "@ts-rest/next"
import { z } from "zod"

const c = initContract()

const dogeContract = c.router({
  getDoge: {
    method: "GET",
    path: "/doge",
    responses: {
      200: z.object({
        message: z.string(),
      }),
    },
    summary: "Get doge",
  },
})

const api = {
  doge: dogeContract,
}

const dogeRouter = createNextRoute(api.doge, {
  getDoge: async () => {
    return { message: "wow" }
  },
})

const router = createNextRoute(api, {
  doge: dogeRouter,
})

// Actually initiate the collective endpoints
export default createNextRouter(api, router)

i get this type error:
Type '() => Promise<{ message: string; }>' is not assignable to type 'AppRouteImplementation<{ summary: "Get doge"; responses: { 200: ZodObject<{ message: ZodString; }, "strip", ZodTypeAny, { message: string; }, { message: string; }>; }; method: "GET"; path: "/doge"; }>'.
  Type 'Promise<{ message: string; }>' is not assignable to type 'Promise<Prettify<AppRouteResponses<{ summary: "Get doge"; responses: { 200: ZodObject<{ message: ZodString; }, "strip", ZodTypeAny, { message: string; }, { message: string; }>; }; method: "GET"; path: "/doge"; }, HTTPStatusCode, "server", "default">>>'.
    Type '{ message: string; }' is not assignable to type 'Prettify<AppRouteResponses<{ summary: "Get doge"; responses: { 200: ZodObject<{ message: ZodString; }, "strip", ZodTypeAny, { message: string; }, { message: string; }>; }; method: "GET"; path: "/doge"; }, HTTPStatusCode, "server", "default">>'.ts(2322)

what am i doing wrong here?
like am i crazy but does each of the quickstarts/code/examples give a different way to actually get things set up?
e.g.

what is c?
elsewhere:
import { initContract } from "@ts-rest/core"
const c = initContract()

but contract doesn't exist on c?

some of the docs say to use c.type in responses, elsewhere it says to use z.object()
elsewhere, we make a contract with c.router?

am confuse
is there a canonical self-contained example that i can just copy/paste and modfify?

Which version of Next are you using?

13.4.13

You need to return { status: 200, body: { message: 'wow' }} not just { message: 'wow' }


docs: API reference review

Changes

Configured API references, added missing steps/sections and updated docstrings to render them correctly
Removed individual LLM Gallery for better maintainability, as there were missing LLMs.
Minor update to regex in parse_google_docstring used in component_gallery.py, so that examples are rendered in API references and component_gallery
Added basic contributor docs
Changed OpenAI in quickstart and README by HF Inference Endpoints.

FYI

If using \n in examples, it breaks the rendering in docs, so better to use \\n
Examples should be written without a blank line as:

Examples:
    Bla bla bla

    ```python
    pass
    ```

@sdiazlor would you be able to add a google colab button to the first page of the docs, to one of the notebooks you will present during the community?


Add section to show the active AWS profile

Description

Implement AWS profile section based on the implementation on spaceship.

Show profile name when it exists and isn't set to "default"
Write tests for the new section

Clean up a whole lot of other tests

Update documentation with the new section

Motivation and Context

Closes #85
Types of changes

[ ] 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 not work as expected)

Screenshots (if appropriate):

How Has This Been Tested?

[x] I have tested using MacOS
[ ] I have tested using Linux

Checklist:

[x] I have checked that no other PR duplicates mine
[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 updated the tests accordingly.

Ahhh, it doesn't show when it's set to default, I was wondering why it's not working for me :)
Maybe a good idea to also show it when it's set to default, why not? That way you know you're on default, can be helpful.

The feature is implemented as is because spacefish is a port of spaceship-prompt. If you feel like this should behave differently, please open an issue there. Once this feature is updated on spaceship, we will port the functionality back to spacefish. 🙂


Cursor jumps to start with latest v1.3.0 update

First of all, thanks for this component. It's been working great up until this latest update.
Now, whenever I type into the element, the cursor jumps to the front of the element with every key that is entered. I've rolled back to v1.2.0 and everything works fine again. But if I reinstall v1.3.0, the cursor starts behaving funny again. I've locked my dependency back to v1.2.0 for now, so I'm okay for the time being.
I'm not sure what changed in that latest version to cause that behavior, but thought I should report it. Let me know if you need any further info from me.
FYI, this is on Chrome 65.0.3325.181

Fixed in 1.3.1! 🎉
The culprit? without(Object.keys(propTypes), ["content"]) should have been without(Object.keys(propTypes), "content")

Awesome. Thanks!


Network status hides Block Consolidation status

a little issue.
The "network status" is made as a semitransparent popup, covering all other GUI elements.
When clicking (switching) in the menu to any other content it looks like it doesn't work (appear)
The user first must click the X on top-right of the network-status overlay.
I would suggest the overlay can remain the same, but any other menu click should automatically close the overlay.

Hi @gufmar,
Thank you for your report. Could you describe the exact steps for this issue to occur?
We will investigate it.
Regards,
Danilo

@gufmar could you also, please, let us know which Daedalus version you are using?

it is version 0.13.1#<IP_ADDRESS>40
Steps to reproduce
Start Daedalus
Menu Daedalus > Block Consolidation Status (the page appears by replacing the wallet page = OK)
Menu Daedalus > Network Status (the page appears by poping up above the Block Consolidation status = OK)
Now when the user didn't note it is a full window size (popup) overlay that must be clicked away on top-right X and he clicks again in menu Daedalus > Block Consolidation status, the Network status overlay will remain on top, and it looks like the app is not reacting anymore (beside the status values updating)

Hi @gufmar. We have a new Daedalus finishing baking which will address this issue and also unify the layout for all overlays.
Many thanks for the information,
Danilo


coloring MarkerClusters based on some other aggregate features of the underlying markers

Hi
I am wondering if it would be possible to color the MarkerClusters based on some aggregate features of the markers belonging to each cluster? I mean instead of count use some mean values of the markers. Let say we have a price attribute for each market and now we are interested to color clusters based on the average or median price.
Thanks a lot.

Yes. Read the documentation and roll out your own iconCreateFunction.


Update pr template to add links and highlight use of the develop branch

Summary of the changes
Updated the pull request template to add link to the manual accessibility testing guidance and draw more attention to that PRs should be raised against the develop branch
Related issue
fix labelling of 'Radial indeterminate'
Checklist

[x] I have manually accessibility tested any changes, if relevant.

done, thanks @MI6-451 should have read my own PR and then the Contributing guidance! 🤦♂

Hey @chrisns. Is it OK if you rebase off develop so your PR doesn't include file changes you never made and fix conflicts please? Will make it easier to see your updates and get them merged in.

👍 done


Tool does not work with socket connections

In our environment, our source database superuser connection is limited only to socket connections, and not standard TCP/network connections. According to the docs, any valid libpq connection string should work, but it fails if you pass in a connection string with no host/port defined.
Traceback (most recent call last):
  File "/var/lib/postgresql/aiven-db-migrate/aiven_db_migrate/migrate/pgmigrate.py", line 943, in validate
    self.source.conn_info["host"] == self.target.conn_info["host"]
KeyError: 'host'

The connection string in question works with psql:
postgres@linus-db:~/aiven-db-migrate$ psql "postgres:///dafhp6nhpahgqn"
psql (12.1 (Ubuntu 12.1-1.pgdg18.04+1))
Type "help" for help.

dafhp6nhpahgqn=# \conninfo
You are connected to database "dafhp6nhpahgqn" as user "postgres" via socket in "/var/run/postgresql" at port "5432".
dafhp6nhpahgqn=#

It would be fine for us to grant the extra permissions needed to a non-superuser role that has network connectivity (and honestly it's less messy than running this code directly on the source db), but the docs are unclear as to exactly what permissions would be needed to support this.

did you try to add the unix socket file as the host parameter?

Ok, it seems to get past the parsing step at least if I do the connection string in this format:
"postgres:///dafhp6nhpahgqn?host=/var/run/postgresql"
Running into a different problem now with the binary detection

It seems like a network/host connection is required in order for the subscription to actually be able to work anyways?
Databases:
  dbaname: 'dafhp6nhpahgqn', method: 'replication', status: 'failed', message: 'could not connect to the publisher: could not connect to server: No such file or directory\n\tIs the server running locally and accepting\n\tconnections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?\nCONTEXT:  SQL statement "CREATE SUBSCRIPTION aiven_db_migrate_dafhp6nhpahgqn_sub connection \'application_name=\'\'aiven-db-migrate/0.0.1-13-g8a8bb0b/dafhp6nhpahgqn\'\' dbname=\'\'dafhp6nhpahgqn\'\' host=\'\'/var/run/postgresql\'\'\' publication aiven_db_migrate_dafhp6nhpahgqn_pub WITH (slot_name=\'aiven_db_migrate_dafhp6nhpahgqn_slot\', create_slot=FALSE, copy_data=true)"\nPL/pgSQL function pg_create_subscription(text,text,text,text,boolean,boolean) line 6 at EXECUTE\n'

I think I'll need a better understanding of your use case . Are you trying to replicate from one cluster to the other, both running on the same machine ?

We were attempting to replicate from an instance that does not expose a superuser account with login rights, but it seems that fundamentally won't work because of the way the replication has to connect. We set up a secondary superuser with login rights specifically for running this replication/migration in order to proceed. Closing this issue out.


[组件名称] 描述问题的标题 Because sfeapp depends on tdesign_flutter ^0.1.6 which depends on flutter_slidable 3.1.0, flutter_slidable 3.1.0 is required

tdesign-flutter 版本
0.1.6
重现链接
No response
重现步骤
Because sfeapp depends on tdesign_flutter ^0.1.6 which depends on flutter_slidable 3.1.0, flutter_slidable 3.1.0 is required
期望结果
No response
实际结果
No response
Flutter版本
No response
设备与机型信息
No response
系统版本
No response
补充说明
No response

手动引入一下flutter_slidable，之前swiper有这个问题


python310Packages.adafruit-platformdetect: 3.43.0 -> 3.44.0

Changelog: https://github.com/adafruit/Adafruit_Python_PlatformDetect/releases/tag/3.44.0
Description of changes

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 224972 run on x86_64-linux 1

4 packages built:

python310Packages.adafruit-platformdetect
python310Packages.adafruit-platformdetect.dist
python311Packages.adafruit-platformdetect
python311Packages.adafruit-platformdetect.dist


oauth2: disable chunked transfer for token request

Commit Message: Disable chunked transfer encoding in the oauth2 token request when disable_chunked_transfer: true is set.
Additional Description: When disable_chunked_transfer: true is set, the Content-Length header will be added, which effectively disables Transfer-Encoding: chunked. Azure AD login.microsoftonline.com does not support chunked transfers and returns a 404.
Risk Level: Low
Testing: Manual testing using a local docker image. The image is available at DockerHub as mhyllander/envoy:issue_20179_config.
Docs Changes: Documented the new disable_chunked_transfer configuration parameter.
Release Notes: N/A
Platform Specific Features: N/A
Fixes #20179

@mhyllander we've hit the same exact issue.

@lizan @daixiang0 Looks like I managed to fix the CI issues. So what about the configuration parameter, do we keep it or not?

@lizan looks like this one is ready to go - could you give it a final review?
/wait-any

is there a docker image i can use to test this build out until the next release after it has been merged?

@lizan As per the discussion above, I reverted the configuration parameter so that chunked transfer encoding is always disabled.

@marcosrmendezthd
see:

https://hub.docker.com/r/envoyproxy/envoy-dev/tags
https://hub.docker.com/r/envoyproxy/envoy-contrib-dev/tags

@marcosrmendezthd
see:

https://hub.docker.com/r/envoyproxy/envoy-dev/tags
https://hub.docker.com/r/envoyproxy/envoy-contrib-dev/tags

Thanks @phlax . I am searching for a build with that last commit, c5e91f0, but am unable to find it. Is there a trick to finding the builds for a specific PR?

sort of - but its not easy
you need to click through from one of the azure CI tests Details and then onto azp
in the top section of the azp pr run you can see a "related" section which has (for this PR) "11 published" which takes you to the "Artefacts" page
there, under "docker" you should find tarballs with all of the images created in/for CI - untar the relevant one and load the contents with docker load

@davidnarayan Thanks for that suggestion, I've added it. I wasn't sure what testing I could do.


VarT violates the applicative laws

I believe the Done constructor was added for efficiency, but exposing the constructor violates the applicative laws.

I've already hand-proven the applicative laws assuming that Done doesn't exist, and instead used pure x = VarT (\_ -> pure (x, pure x)), so the solution (I believe) is either:

Simply hide the VarT constructors
Rewrite <*> to pattern match on Done where appropriate so the laws work out.

Thoughts?

It's interesting you brought this up tonight, earlier I removed Done during profiling, I'll check in my changes in a branch and see what you think. For what it's worth though, I think the applicative laws are covered in our test cases. I'll have to check when I'm not on my phone!

It looks like we're only testing the applicative laws for splines. I'll have to add a test for regular var streams. 👍

@mitchellwrosen - in https://github.com/schell/varying/issues/6 I wrote a test for VarT's applicative homomorphism law. It passes just fine, though that's after I removed the Done constructor, which also greatly improved performance. It's a great win - in my downstream programs I don't even see Control.Varying in profiling any longer!

I'm super excited - at least at first glance the changes in #6 allow us to have varying values and the added abstraction of sequencing at a very low cost. Getting rid of the constructors in VarT and changing SplineT's type to use Either instead of a tuple has really improved performance. I think the main problem was that using a tuple (b, Event c) meant that there were many unevaluated output b values kicking around the runtime. The code itself is much less complex using Either, so that is another win.

Nice! I just want to clarify that I didn't mean to imply the instance buggy, but rather it was just incorrect, per the laws. I've seen this pattern before in the operational monad, for example - the main ProgramT type technically violates the monad laws, so its constructors are not exported. Then, end users don't get to see the law violations for themselves.
But, if ripping out the Done constructor actually resulted in better performance, all the better!

Oh, did you want me to poke around your pull request too?

@mitchellwrosen I always appreciate it. I'm going to merge when Travis finishes clean, but if you look and find anything let me know :)


[JitBackend] Implement simple binary ops

Depends on #1020.
Summary
"Parse" simple binary ops (add, sub, mul, div) in JIT.
Test Plan (required)
Unit tests are added.
make JitTensorTest
./flashlight/fl/test/JitTensorTest

Rebase.

Rebase.

Remove redundant code.

Rebase.


Bug fix: should not check stale cache node info before patch

Signed-off-by: TrafalgarZZZ<EMAIL_ADDRESS>
Ⅰ. Describe what this PR does
Fluid CSI Plugin should not check stale cache node info before patch.
Stale cache node may have stale information so it's not reliable.
Ⅱ. Does this pull request fix one issue?

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Is it safe if the node already has the fuseLabelKey?


#452 Fixed

#452
Store twitter followers count and other twitter details when create twitter_user so that twitter followers count can be displayed on admin organization listing

👍


Open Issue 11: SNOMED

Some SNOMED codes are used in the Disclosure profile and example. Should we get these approved, or define our own codes? Are there other available codes to use?

examples are allowed. remove issue.


Christmas design

Icons in top menu

#775

There was a duplicate issue
It's related to chat Christmas design. Would be better to continue in this issue instead of #816, so closing the duplicated one.


Fix typos in slashlinks rfc

Just noticed these when reading through the rfc. Great concept!

Thank you!


Add thread-pool-cpp

This looks like a nice lightweight performant thread pool.
https://github.com/inkooboo/thread-pool-cpp
I can add this one.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27186300-add-thread-pool-cpp?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1032790&utm_medium=issues&utm_source=github).

hunterized: https://github.com/headupinclouds/thread-pool-cpp/tree/hunter
@ruslo: Can you create hunter-packages/thread-pool-cpp and add me as a collaborator?

@ruslo: Can you create hunter-packages/thread-pool-cpp and add me as a collaborator?

done: https://github.com/hunter-packages/thread-pool-cpp

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.684
https://travis-ci.org/ingenue/hunter/builds/145972186

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.687
https://travis-ci.org/ingenue/hunter/builds/146089000

Uploading

Done. Package in branch develop. New wiki page: https://github.com/ruslo/hunter/wiki/pkg.thread-pool-cpp.


Parallelise GraphQL document validation

Description:
The current implementation of the graphql uses an array of visitors to validate the graphql document.
Tasks

[x] Find the dependency between validator visitors (dependency graph)
[x] Group the validators that can be executed in parallel by multiple workers
[ ] Check for performance improvement by comparing the load-test results

Describe your problem(s)
Each visitor is executed in sequence since the execution of some of these visitors depends on the previous visitor.
Describe your solution(s)
These visitors can be grouped by analysing the dependencies and executed parallelly to improve the performance.
Related Issues & PRs(optional):
#950
Suggested Labels (optional):

Suggested Assignees (optional):

Due to this intermittent failure, unable to compare the performance with the load test. Deprioritizing this task until issue #38047 gets fixed.


cobigen-cli does not seem to properly resolve classes from dependencies

I get this error from cobigen-cli:
[ERROR] Compiled class net/sf/mmm/util/entity/api/MutableRevisionedEntity has not been found. Most probably you need to build project

I have replaced devon4j default templates with custom templates. The requested class comes from a JAR dependency (mmm-util-entity) and that dependency is a transitive dependency of the custom templates project. I have checked my software/cobigen-cli/classPath.txt and it contains /Users/hohwille/.m2/repository/net/sf/m-m-m/mmm-util-entity/8.6.0/mmm-util-entity-8.6.0.jar and that file exists on my disc and has the proper content including the requested class.
I have no idea how cobigen-cli builds up his classpath.

does it include all dependencies from the templates project?
I assume it will have to add all dependencies for cobigen itself.
does it also include the dependencies of the current maven project where the generation is invoked?
if yes, the current project in $PWD or the module that is containing the code to taje as input for generation?
does cobigen do any classpath shading to avoid conflicts in dependencies of cobigen itself and the projects/templates dependencies (if different versions of a library are used in cobigen itself and the custom templates project for a specific project)?

Any ideas why the above class is not found or what I could do about it?

https://github.com/devonfw/cobigen/blob/bb492e477cd46dbb8f6eaf71004047418380ecf1/cobigen-cli/cli/src/main/java/com/devonfw/cobigen/cli/utils/ParsingUtils.java#L63
This is rather poor exception handling. Following devon4j coding conventions you should never loose stacktraces. When catching exceptions either rethrow including the catched exception as cause to the new exception or log the exception by supplying it to slf4j as such.

Looking at ParsingUtils I can answer most of the above questions about classpath/classloading myself.
It seems I found another bug in mmm-code here: the collecting of all the transitive dependencies is incorrect.

@hohwille, do you mean, as there is more to do in mmm-code or do we have to integrate a new version, which you already adapted?

With PR #1114 merged and release out, we can IMHO close this. If I find remaining or new problems I better file a new bug.


I hope to adapt to the native scroll bar of Windows 11

As the title
reference style：

the style is from Microsoft edge

Thorium is currently based on version 115. I have the impression that chromium already supports this style of scrollbar in a newer version, so we just need to wait for Thorium to update to the version that supports this style of scrollbar.
@Cryberghost

Thorium is currently based on version 115. I have the impression that chromium already supports this style of scrollbar in a newer version, so we just need to wait for Thorium to update to the version that supports this style of scrollbar.
@Cryberghost

real?

You can check whether there are related experimental flags in the canary or chromium version, in my impression there are related experimental flags
@Cryberghost

@Cryberghost Yeah. You might try the overlay scrollbars flag.


[rmodels] Optional GPU skinning

This adds a form of optional GPU skinning to raylib that doesn't interfere with the existing CPU skinning method, but does expose enough information for a user to write their own GPU skinning in shader code if they want.
Essentially the change works as follows:

For all animated meshes the boneIds and boneWeights vertex data are now uploaded to the GPU along with the rest of the vertex data.
Meshes contain a new boneMatrices array which is uploaded to the shader as a new uniform and is used to contain the skinning bone transformation matrices for that mesh. These matrices can be updated using the UpdateModelAnimationBoneMatrices function which essentially acts as a replacement to the UpdateModelAnimation function when you want to do GPU skinning.

And that is about it. The normal CPU skinning continues to work as intended where users call UpdateModelAnimation.  However with this update users can instead call UpdateModelAnimationBoneMatrices and write their own shader which does the skinning. That might look as follows:
#version 300 es

in vec3 vertexPosition;
in vec2 vertexTexCoord;
in vec3 vertexNormal;
in vec4 vertexColor;
in vec4 vertexBoneIds;
in vec4 vertexBoneWeights;

#define MAX_BONE_NUM 128
uniform mat4 boneMatrices[MAX_BONE_NUM];

uniform mat4 mvp;

out vec3 fragPosition;
out vec2 fragTexCoord;
out vec4 fragColor;
out vec3 fragNormal;

void main()
{
    int boneIndex0 = int(vertexBoneIds.x);
    int boneIndex1 = int(vertexBoneIds.y);
    int boneIndex2 = int(vertexBoneIds.z);
    int boneIndex3 = int(vertexBoneIds.w);

    vec4 skinnedPosition =
        vertexBoneWeights.x * (boneMatrices[boneIndex0] * vec4(vertexPosition, 1.0f)) +
        vertexBoneWeights.y * (boneMatrices[boneIndex1] * vec4(vertexPosition, 1.0f)) +
        vertexBoneWeights.z * (boneMatrices[boneIndex2] * vec4(vertexPosition, 1.0f)) +
        vertexBoneWeights.w * (boneMatrices[boneIndex3] * vec4(vertexPosition, 1.0f));

    vec3 skinnedNormal = normalize(
        vertexBoneWeights.x * (mat3(boneMatrices[boneIndex0]) * vertexNormal) +
        vertexBoneWeights.y * (mat3(boneMatrices[boneIndex1]) * vertexNormal) +
        vertexBoneWeights.z * (mat3(boneMatrices[boneIndex2]) * vertexNormal) +
        vertexBoneWeights.w * (mat3(boneMatrices[boneIndex3]) * vertexNormal));

    fragPosition = skinnedPosition.xyz / skinnedPosition.w;
    fragTexCoord = vertexTexCoord;
    fragColor = vertexColor;
    fragNormal = skinnedNormal;

    gl_Position = mvp * vec4(fragPosition, 1.0f);
}

I have tested this in my own little demo but I have not yet run through to see if it breaks anything else or to check it works with all the existing demos. That is still to do!
I know your intention is to keep raylib simple and minimal and this update is a little hacky in some senses so obviously feel free to close it if you think it is not the right approach or not useful. I just thought I would share it in case you think it might be valuable.
Many thanks in advance!
Dan

I checked and currently this does break the examples and the existing model rendering when no shader is supplied. I'm investigating why now.

The issue appeared to be inserting the new shader uniform locations into the middle of the shader locations enum. Perhaps someone with more experience can move them into a more logical position but I'm not sure right now what may be hard-coded in raylib which relies on the current locations and needs updating. I will also try to prepare a small example for the examples folder.

Okay I added a small example models_gpu_skinning and merged with the latest changes. Let me know if there are any other changes I can make - or as I mentioned before feel free to close this if it is not an approach you think raylib should take in the end :) Thanks!

@orangeduck Hi! Thank you very much for this improvement! It has actually been requested many times by raylib community! The main concern it was not added before was the lack of support for UBOs by some OpenGL versions but as per my understanding, this solution can work with any OpenGL version.
Just let me some days to review it more carefully, specifically the ShaderLocationIndex order issues and the function naming. Also a bit concerned about the Model structure size increment...
In any case, I'm really confident on merging this improvement, after all you are probably the developer that has pushed further raylib 3d models animations!

@raysan5 Brilliant, thank you!
Yes I think this can work on any OpenGL version. I believe the main limitation to this approach is the uniform mat4 boneMatrices[MAX_BONE_NUM]; uniform. For some platforms which have limited memory for uniforms MAX_BONE_NUM may need to be relatively small (my laptop GPU seemed okay with 128, but could not handle 256). For this reason I have seen some developers use a texture or a uniform buffer object instead - but then we are back to OpenGL version issues - so perhaps given raylib is already limited to 256 bones by the boneIds array this may be a practical trade-off for most people.
The other downside is of course that for animated models that use CPU skinning you will now pay the additional VRAM cost for uploading the boneIds and boneWeights.
Thanks again!

The other downside is of course that for animated models that use CPU skinning you will now pay the additional VRAM cost for uploading the boneIds and boneWeights.

Well, that can be addressed with a config.h flag, for example SUPPORT_MESH_GPU_SKINNING. Only upload boneIds and boneWeights to VRAM if enabled and use CPU if not.

@orangeduck About to merge this great improvement, just a small issue detected by the automatic analysis system.

@orangeduck Thank you very much for this great improvement! 😄


fix: token expiry calculation

fixes https://github.com/openfga/js-sdk/issues/26

Thanks for the contribution @KlausVii !


test full node outage and recovery

Description
This test tests a full node outage and recovery of liveness. This is to be added to the existing liveness recovery tests that run as CI.
Test Plan
How did you test the new or updated feature?

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

@ebmifa now that this is merged would you be able to assist with adding this to the existing liveness tests in CI?


small bug fixes

Current coverage is 66.86% (diff: 11.11%)

Merging #19 into master will decrease coverage by 0.17%

@@             master        #19   diff @@
==========================================
  Files            39         39
  Lines          2628       2635     +7
  Methods           0          0
  Messages          0          0
  Branches        473        474     +1
==========================================
  Hits           1762       1762
- Misses          727        733     +6
- Partials        139        140     +1

Powered by Codecov. Last update 86bbfef...6e06a12


More Information Requested

Within this page is a tip notification that says:

The service tags required to access the Azure portal (including authentication and resource listing) are AzureActiveDirectory, AzureResourceManager, and AzureFrontDoor.Frontend. Access to other services may require additional permissions, as described below.
However, there is a possibility that unnecessary communication other than communication to access the portal may also be allowed. If granular control is required, FQDN-based access control such as Azure Firewall is required.

Then it proceeds to list all the FQDNs.
The problem is, the service tags mentioned in this tip notification doesn't specify exactly which ones are covered and which ones are not.
Going to the Service Tags page: https://learn.microsoft.com/en-us/azure/virtual-network/service-tags-overview#available-service-tags
Also doesn't say which ones are covered.
The tip also says "Access to other services may require additional permissions, as described below."
But there is no information about any additional permissions... nothing is described below.
The tip is misleading, and doesn't provide the information necessary to continue.
With all the URL's provided in the groups, there should be information about which service tag is covering which access.
For example, the group "Azure portal authentication"... which service tag covers all of these if any? Are some FQDN's excluded from the service tag?
This page really needs more information about the service tags and which groups are covered.

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

ID: d8336877-da93-ecd6-829a-0cc068caaf29
Version Independent ID: 1e70f094-f220-92c6-7e5b-cfaf071101d5
Content: Allow the Azure portal URLs on your firewall or proxy server - Azure portal
Content Source: articles/azure-portal/azure-portal-safelist-urls.md
Service: azure-portal
GitHub Login: @JnHs
Microsoft Alias: jenhayes

@nubgamerz
Thanks for your feedback! We will investigate and update as appropriate.

Hi @nubgamerz -
Thanks for sharing your feedback, and I apologize for the long time to respond. I understand that you'd like more details, but the service tags we mention here are sufficient to enable general portal access. The reference to "described below" refers to specific URLs noted for different services/scenarios. As the note mentions, "If granular control is required, FQDN-based access control such as Azure Firewall is required." As you note, more info on the service tags can be found on that page, but we don't offer a specific list of which tags cover which parts of portal access.
I'll close this issue now, and have passed along your feedback to the product team. Again, thank you for sharing your feedback and I'm sorry for the delay.
#please-close


BP Stream pump modules update

This pull request contains 3 major updates:

bp_stream_pump_in and bp_stream_pump_out are attached to bp_cce_to_cache_new. And the FSM and relevant logic in the bp_cce_to_cache_new is updated to work with pumps.
bp_lite_to_stream is updated according to the update of BP Stream protocol, including no lock for signal beat cmd/resp and no lock for the last packet in a sequence of cmds/resps.
bp_cache_slice_new replaces the old one in bp_unicore, and the memory interface of bp_unicore is updated. Also, bp_burst_to_lite and bp_lite_to_stream are added and used to connected bp_unicore in the wrapper.

The PR passed riscv_testlist for fill_width=512, and is currently running beebs_teslist.
Note. e_bp_unicore_no_l2_cfg is not yet updated with the new bp_unicore memory interface.

It also pass beebs_testlist

Please do the following to clean up the diff:

rename _new modules to replace old modules directly
rebase on me_dev
checkout the new burst converters from me_dev and use those

It has been rebased on me_dev and updated with the burst to lite logic on me_dev. And the _new modules replaces the old ones as well. It passed both riscv and beebs testlist

The mentioned issues are mostly fixed with a few commits, except the "address_o" one.

There are 2 changes.

Replaced the cnt_o with stream_addr_o for the pump_in module like we discussed above. With this change, UCE and cce_to_cache will not need to repeatedly calculate the address, especially the address is demanding in multiple scenarios to fill the cache. It decouples the pump_in from fsm in a better way.
Changed the logic to get last_cnt for all three modules mentioned above, except the dff_en_bypass one as there is no special condition for the num_stream in the updated design any more
These changes passed cache_hammer, riscv_testlist and beebs, and it is ready for review.

The pump modules are changed with payload_mask_p and the pass/decode, pass/combine stream states are integrated. It passed cache_hammer, riscv and beebs testlist, and is ready for review.

Gave more feedback to simplify stream pumps

Updates are made based on the above suggestions and it is ready for review.

Found some issues in the pump_in when it is attached to UCE and got them fixed. The updated pump modules are tested.

Made the change of replacing lock signal with last signal and changes based on the feedback. Passed cache_hammer and riscv tests and is ready for review.

Combine signals in the pump modules. Update the pump_in with 1-bit FSM. Any additional comments on the pump_in module? Still working on combining signasl and fsm update  in pump_out.

Add variable stream_data_width support including stream_data_width == 512 bit. Discard the 1 bit fsm change because using 1-bit reigster can be more flexible to work with stream_data_width from 64bit to 512 bit.


4.25 support?

Hi! Is there any plans to port this plugin to the (currently) latest engine version?

Doesn't require any modifications, works in 4.25