refactor, fix cannot save and query Date field

The azure-documentdb JsonSerializable cannot set a Date type value directly.

Codecov Report

Merging #50 into master will increase coverage by 0.21%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #50      +/-   ##
==========================================
+ Coverage   75.64%   75.86%   +0.21%
==========================================
  Files          30       30
  Lines         661      667       +6
  Branches       87       89       +2
==========================================
+ Hits          500      506       +6
  Misses        114      114
  Partials       47       47

Impacted Files
Coverage Δ

...entdb/core/convert/MappingDocumentDbConverter.java
69.81% <100%> (+1.81%)
:arrow_up:

...pring/data/documentdb/core/DocumentDbTemplate.java
77.09% <100%> (+0.3%)
:arrow_up:

Continue to review full report at Codecov.

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

#48


Need to remove the authentication from the server-startup-healthcheck endpoint - APIM 4.1.0

Description
Currently, we need to parse the basic authorization header for this server-startup-healthcheck API [1] call to see whether all the APIs got deployed in the gateway level. But this is kind of a health check endpoint and therefore, no need to have the authorization mechanism for this.
[1] https://apim.docs.wso2.com/en/4.1.0/reference/product-apis/gateway-apis/gateway-v2/gateway-v2/#/paths/~1server-startup-healthcheck/get
Steps to Reproduce
N/A
Affected Component
APIM
Version
4.1.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Merge-pending public PR: https://github.com/wso2/carbon-apimgt/pull/12213


[Pro] Allow new molecule format for Docker driver

Proposal:
Author: RockAndSka <@RockAndSka> IRC: RockAndSka
Date: 2019-04-10

Status: New
Proposal type: core design
Estimated time to implement: more or less 3 days (without the docs)

Motivation

Allowing users to be able to have access to the full docker modules used by molecule and avoid many issues / PR related to modules arguments missing.
Avoid repetition for platforms common options (images build arg, docker host settings etc..)

Problems
What problems exist that this proposal will solve?

#1879
#1878
#1847
#1688
#1817
#1920
#1889

and many others
Solution proposal
All modules used are in a unique dict avoiding to pass to the modules the "args" key with a dict of the options.
Allowing a new molecule format for docker driver (compatible with the old version too) will let the users been able to use all the args available for modules (docker_network, docker_image,docker_container)
A working example is provided here: rockandska/repro-issues
Dependencies (optional)
None
Testing (optional)
A little test is provided in my repo but need to be more tested with different cases already tested.
Documentation (optional)
Will be provide in case this proposal is accept and the format well defined and validated
Anything else?
Any comments , questions are welcome and could be discuss on IRC too if needed
Edit:

many jinja kung-fu could be avoid by writing some libraries but didn't done it since it is a POC
didn't done it too, but will be better if new and old create/destroy yaml are separate in sub_playbooks and import by create/destroy depending on the schema version to avoid the "skipped" tasks
the warnings triggered by the usage of passing a dict as args to the modules could be avoid by adding "INJECT_FACTS_AS_VARS=false" (ansible>=2.5) only for the create/destroy "ansible-playbook" commands. (having it for other tasks have too many implications)

Related (one possible solution to the current design): #1642


bug: toggle floating does not properly unlock

zellij --version: zellij 0.41.0
Terminal version: foot version: 1.18.1 +pgo +ime +graphemes -assertions
Operating system: Linux 6.10.10-arch1-1 #1 SMP PREEMPT_DYNAMIC x86_64 GNU/Linux
Issue description
When toggling floating panes in a window that is locked by a program defined in triggers, the ui is not unlocked.
Minimal reproduction
Zellij Config:
plugins {
    autolock location="file:/home/jonny/.config/zellij/zellij-autolock.wasm" {
        triggers "nvim"
    }
}

keybinds {
    normal {
        bind "Enter" {
            WriteChars "\u{000D}";
            MessagePlugin "autolock" {};
        }
    }
    shared_except "normal" "locked" {
        bind "Esc" { SwitchToMode "Normal"; }
    }
    // Standard Mode Bindings
    shared_except "locked" {
        bind "Alt ." { SwitchToMode "Locked"; }
        // Floating Settings
        bind "Alt o" { ToggleFloatingPanes; }
    }
}

Open two panes
Open Neovim in one pane

:!zellij action move-focus-or-tab right moves focus and unlocks the ui.
:!zellij action toggle-floating-panes opens the floating pane but the ui is still locked.

Other relevant information
Thanks for the work on this!  I tried taking a swing at getting this fixed but its been a few years since I've even touched Rust and I've never done much with it.  Maybe I am not correctly configuring for this use case so any help would be great!

Can you just do bind "Alt o" { ToggleFloatingPanes; SwitchToMode "Normal"; }.
Or equivalently :!zellij action toggle-floating-panes && zellij action switch-mode normal

That works for swapping into floating panes mode but if I'd swap back to Neovim, Zellij wouldn't autolock again.  My workaround for now is just adding the following to my zellij config and manually unlocking if I need to when floating panes are toggled on.
locked {
    bind "Alt o" { ToggleFloatingPanes; }
}

Thanks for the report and the suggested workaround. This seems to be an inherited limitation in the Zellij API. Aram hasn't cut a Zellij release in a while, but has been hard at work on it. I'll revisit this after the next Zellij release.

FWIW, when opening a floating pane from within [Neo]vim using the companion plugin, zellij.vim, the floating window is opened in "Normal" mode (unlocked). This also has the helpful effect of opening the floating window in Vim's current working directory.
I have this in my Zellij config.kdl:
    shared_except "locked" {
        /* Put keybindings here if they conflict with Vim or others. */
        ...
        bind "Alt t" { ToggleFloatingPanes; }
        bind "Alt o" { NewPane "Down"; }
        bind "Alt v" { NewPane "Right"; }
        ...
    }

and this in my .vimrc:
" Open floating Zellij pane with `Alt+f`.
execute "set <M-t>=\ef"
noremap <M-t> :ZellijNewPane<CR>

" Open Zellij pane below with `Alt+t`.
execute "set <M-o>=\et"
noremap <M-o> :ZellijNewPaneSplit<CR>

" Open Zellij pane to the right with `Alt+v`.
execute "set <M-v>=\ev"
noremap <M-v> :ZellijNewPaneVSplit<CR>

These configs result in the desired behavior, when using [Neo]vim at least.


How to restore token object from access_code

Maybe I'm looking in the wrong direction, but how would one go about to restore the token object from an access_code in storage (say in a session). It looks like the public function validateAccessToken in Azure.php is the right candidate, but it throws an error
Undefined variable: provider	 Fatal error: Call to a member function getClientId() on null in D:\home\site\vendor\thenetworg\oauth2-azure\src\Provider\Azure.php on line 237
Am I missing something?
-- UPDATE:
Nevermind, figured out I can leverage the new \League\OAuth2\Client\Token\AccessToken class for this.

What do you mean by access_code? Do you mean the code which is returned by the authorization code flow?


python3Packages.aioconsole: disable failing test

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

Things done

Built on platform(s)

[x] 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/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

5 packages built:

home-assistant-component-tests.whirlpool
python310Packages.aioconsole
python310Packages.whirlpool-sixth-sense
python39Packages.aioconsole
python39Packages.whirlpool-sixth-sense


Banned

After some disconnect noaut....

อ่อน

อ่อน

พี่เข้าใจ น้องอาจจะยังงงอยู่

the api of kingdom/enter seems to be changed. The web client posts json=FRI%3D. therefore, i tried to add this, but it returned 400 bad request (and banned lol).
Even though the issue of kingdom/enter/ will solved, the response is now also "encrypted", so BASE64ENCODE_URL_WHITELIST` will probably need to be changed

any plan about updating the bot or encryption is hard now ?

the way to request on kingdom/enter seems to be identified, but the response is maybe really encrypted.
in order to get the response from kingdom/enter, we need to set sticky session key on cookie. (seems the LoK server has become distributed by sticky session. great job lol. therefore, duplicated login error once occurs after updates)
in the client.py...
class LokBotApi:
    def __init__(self, access_token, captcha_solver_config, request_callback=None):
        self.opener = httpx.Client(
            headers={
                'content-type': 'application/x-www-form-urlencoded',
                'sec-fetch-site': 'same-site',
                'user-Agent': 'Mozilla/5.0 (X11; Linux i686; rv:100.0) Gecko/20100101 Firefox/100.0',
                'x-access-token': access_token
            },
            http2=True,
            base_url=lokbot.enum.API_BASE_URL
        )
        self.cookies = httpx.Cookies()
        self.cookies.set(
            'AWSALB',
            'XXXXXwXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXQ+',
            domain='lok-api-live.leagueofkingdoms.com'
        )
        self.cookies.set(
            'AWSALBCORS',
            'XXXXXwXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXQ+',
            domain='lok-api-live.leagueofkingdoms.com'
        )

...
    @ratelimit.limits(calls=1, period=0.1)
    def post(self, url, json_data=None):
        if json_data is None:
            json_data = {}

        post_data = json.dumps(json_data)
        if url not in BASE64ENCODE_URL_WHITELIST:
            post_data = base64.b64encode(post_data.encode()).decode()

        if url == "kingdom/enter":
            logger.info(f"try kingdom enter, cookie: {self.cookies}")
            post_data = "json=FRI%3D"
            response = self.opener.post(url, data=post_data, cookies=self.cookies)

thre response from kingdom/enter still need to be analyzed.

as you may know, kingdom/connect returns sticky session as a set-cookie like the followings. the need value is only first strings
AWSALB=XXXXXwXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX; Expires=Sat, 02 Jul 2022 AA:BB:CC GMT; Path=/

in addition, the token for socf_thread is also changed... the token is started from FU0..., which is different with access_token like ey...

so is there a way to make the bot work again ? or now it become impossible ?

Check this bot: https://www.youtube.com/watch?v=BpeEHzkbl6U it does work with encryption and it does not give ban, as it emulates mouse movement and uses image recognition.

the script still works?


Don't split log writes by line

I want to use this PR to discuss the current behaviour and suggest a different one.
Currently, if a Docker container logs a multi-line message in a single write() (e.g. echo -en "foo\nbar\n"), the copier splits those messages into lines, such that the log driver will receive one call to Log() per line (rather than one call to Log() per write that the container did). That behaviour somewhat breaks multi-line logging.
For a bit of context: We are playing around with implementing a Kafka logging driver for Docker (someone from the core team encouraged that and said other people might be interested) and we would like to send one Kafka message per "log event". Splitting the output of the container into lines would result in us sending multiple Kafka messages.
Thoughts?
@LK4D4 @crosbymichael @sirupsen @graemej

oh, hm, I just realized that this implementation doesn't do what I thought it does. I kinda wanted to mimic the behaviour of io.Copy. But ReadFrom actually reads everything in one go until EOF... Will rework this. (But feel free to comment on the general idea anyway.)

@fw42 - FYI on Kafka - as part of Logspout (https://github.com/gliderlabs/logspout), @dylanmei wrote a Logspout Kafka module: https://github.com/gettyimages/logspout-kafka. This might be useful for you to use, or as inspiration.

There is an issue with going this route too. If an incomplete line is written, it'll get sent off to the logger as a full line, and the rest of the line will get sent off as another line. This is unfortunately very common in apps (to perform multiple write()s for a single line).

@phemmer: Good point. What's your suggestion how to fix this? I could do what io.Copy does (have a loop that tries to read N bytes at a time and write those N bytes, without having any concept of "lines"). But that doesn't really solve the problem completely (if your N is not large enough). Thoughts?

I think this breaking current logging drivers. We should do it in configurable manner, like Splitter interface.

@LK4D4: You mean an additional command line argument? How do you feel about the idea itself? Any tips on how you would like to see this implemented? Is a Read()/Write() copy loop (like io.Copy) okay with you?

Idea is ok for me. Not sure about argument for now, but probably if we'll find people with usecases for other drivers.
Seems like we need refactor copier to call something from drivers instead of just scanner.

There is no way to reliably detect multi-line messages. You're basically trying to convert a stream into datagrams.
You could try and implement this, but I think it'll cause more problems than it solves. People will constantly be complaining because it erroneously lumped multiple messages together, or split single messages apart.

@phemmer Yes, now I see this too. It is possible only if your application will mark end of messages somehow. We logging just stdout from container and not allowing applications to write logs directly to docker logging drivers.

You're basically trying to convert a stream into datagrams.

Yeah I see your point :/


[Chart] When TravelBuddy is cleared using 'clear' command, chart is not cleared immediately.

Thanks for resolving the issue.


Implement DbtCloudJobRunOperatorAsync and DbtCloudJobRunSensorAsync

Implemented Dbt Cloud Run Job Operator Async DbtCloudJobRunOperatorAsync and run job Sensor DbtCloudJobRunSensorAsync .
Refer https://astronomer.slack.com/archives/C0387PMM2E7/p1659702674640089

[x] Added DbtCloudJobRunOperatorAsync Operator, Hooks, Trigger
[x] Added DbtCloudJobRunSensorAsync
[x] Added Example DAG
[x] Added Docs
[x] Exception Handling in case of errors
[x] Added Test case for Hook, Triggers, Operator

closes: #575

@pankajkoti @phanikumv @BasPH Addressed the review comments, can you please take a look at it

@pankajastro Addressed your review comments, please take a look at it.


Something's wrong with the Left Side bar

Squeezed? or Indented to the Right? Here's some screenshots...

This is not a bug.If you want to communicate some ideas or improvements, you can post them here: https://github.com/ant-vel/Discussion
taking on account that you could be willing to develop them.
Thanks for testing!

I thought it was because previously before the recent commits, it shows up fine, aligned to left together with the headers.. anyway, i'll take a look at the codes later and see if I could find where to adjust the width.:) Thanks Gustavo, as always. Will be posting it later at the Discussion page.

Sorry Gustavo, my bad. Was playing around with the CSS.... i accidentally left the margin-left to 90px... thinking the nav bar would only be affected. It seems the left side bar was also affected.... Just clarifying this as a non-bug.. You're right. Apologies.

keep in mind that antvel uses bootstrap to control the styles and resolutions in devices!

Copy that, G! Thanks!  Where do you prefer having custom css be at? Right now, I'm just overriding app.css at the bottom section. Would that be ok or there's a better way for this?

I really recommend to you learning less css, gulp >>> https://github.com/ant-vel/antVel/blob/master/gulpfile.js, and all the new tools because it seems like you are new in this!

Thanks for the guide. I am new in Laravel and its components... But had years of experience in non-standardized non-frameworked PHP... So yeah, I'm still digging in this new framework, and so far i love the way it is structured and organized. so LESS CSS and GULP it is....

https://laravel.com/docs/5.2/elixir


Why overridding std function defs in examples?

Some of the examples have this code at the bottom:
namespace std
{
  void __throw_bad_function_call() {}
  void __throw_length_error(char const *) {}
}

This causes my build to fail with this error:
Linking .pio/build/teensy41/firmware.elf
/Users/sam/.platformio/packages/toolchain-gccarmnoneeabi-teensy/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld: /Users/sam/.platformio/packages/toolchain-gccarmnoneeabi-teensy/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+dp/hard/libstdc++.a(functexcept.o): in function `std::__throw_length_error(char const*)':
(.text.unlikely._ZSt20__throw_length_errorPKc+0x0): multiple definition of `std::__throw_length_error(char const*)'; .pio/build/teensy41/src/main.cpp.o:main.cpp:(.text.unlikely._ZSt20__throw_length_errorPKc+0x0): first defined here
collect2: error: ld returned 1 exit status
*** [.pio/build/teensy41/firmware.elf] Error 1

To fix my build, I had to change all my uses of std::string to char. Then I realized I could just delete the above lines and all seemed fine. So what is the purpose of these overrides???

Just delete the two lines.
there was once a time before std was standard in teensyduino. Blah blah

Hi Nic, thanks for you super quick answer! I'll mark this issue as closed.


Update broken links for networking samples

Summary
Ron, I found links to all the samples except the following:
HttpListener ASPX Host Application Sample
Socket Performance Technology Sample
PeerToPeer Technology Sample
But as you mentioned, they sample pages do exist in the .NET 2.0 documentation, for example https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2008/bb906998(v=vs.90)
However, I could not find the code files for the missing samples.
Would it be better to link to the old documentation for these, as opposed to removing them?
Fixes #4931

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


Add one additional waypoint to match vegas_track waypoint 151

related with issue #219 to fix missing additional waypoints for Vegas_track.npy

@dmh23 , could you help to review this


fix: pubsub

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


Non max suppression for line extraction

Implementation of merging lines using NMS from DeepLSD computes the principal line direction for each connected component of lines, projects all merge candidate line endpoints onto the principal direction vector and chooses the furthest two points as the line endpoints after merge.
To ensure a wireframe like structure at the output of line extraction i.e. line endpoints are a subset of the detected keypoints, this PR modifies NMS to return keypoint indices after line merging instead of the endpoints. After projection onto the principal direction vector, the keypoint (indices) that lead to the furthest points after projection are returned.
Major updates in gluefactory/models/lines/line_refinement.py.

@hardik01shah is this ready to be merged? Or at least to be raised to a non-draft PR?

@FelixMoeller3 Yes! Requested changes from @RaphaelKreft have been made. Merging.


Use multiple from_address

In order for me to use multiple from_address (e.g. to forward to the same address), do I need to re-deploy the entire stack?
How can I duplicate the lamdba function that was created?

In order for me to use multiple from_address (e.g. to forward to the same address), do I need to re-deploy the entire stack?
How can I duplicate the lamdba function that was created?

I added additional recipients to the SES rule.  Then I changed line 13 in the lambda function so my email shows who was the intended initial address:
    // var email = msgInfo.content, headers = "From: "+forwardFrom+"\r\n";
    var email = msgInfo.content, headers = "From: "+msgInfo.mail.commonHeaders.to[0]+"\r\n";

this makes the from_address not used in this case.


Rhino 7 doesn't run after installing

The installation appears to work OK, but I am unable to get Rhino running. Rhino crashes during the startup process, the first license dialog never appears. Note in the attached screenshots of the console the rhino crashdump reporter is running.  It never succeeds in uploading the crashdump, though. But looking at the crashdump gives no usable information at all. None of the threads have a good callstack. The crashdump also says the windows version it was created on was 6.2.9200, which is wrong.
I am using Lutris <IP_ADDRESS>:

The wine version used in Lutris is set to lutris-6.10.7
Below is the winetricks log for the system as it is currently installed.

nathan@blender ~/.rhino7 $ cat winetricks.log
andale
arial
comicsans
courier
georgia
impact
times
trebuchet
verdana
webdings
corefonts
w_workaround_wine_bug-34803
remove_mono
remove_mono
winxp
dotnet40
dotnet48
renderer=no3d

I changed the windows version to 10

The following info appears in the wine console when renderer=no3d

I tried with all the other renderer settings, but they all have similar info in the wine console. Here with GDI:

My system configuration is:

System:    Kernel: 5.8.0-63-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.0.5
wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial:  Chassis: type: 3
serial:
Mobo: Gigabyte model: F2A85X-UP4 v: x.x serial:  UEFI: American Megatrends
v: F2 date: 08/31/2012
CPU:       Topology: Quad Core model: AMD A10-6800K APU with Radeon HD Graphics bits: 64 type: MCP
arch: Piledriver rev: 1 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 32739
Speed: 4372 MHz min/max: 2000/4100 MHz Core speeds (MHz): 1: 4335 2: 4356 3: 2495
4: 2009
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: XFX Pine
driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:67df
Display: x11 server: X.Org 1.20.9 driver: amdgpu unloaded: modesetting
alternate: ati,fbdev,vesa resolution: 1920x1080~60Hz
OpenGL:
renderer: AMD Radeon RX 480 Graphics (POLARIS10 DRM 3.38.0 5.8.0-63-generic LLVM 11.0.0)
v: 4.6 Mesa 20.2.6 direct render: Yes

That’s interesting. 🤔  I check this later. 🕛
Is there a way to test the latest version of Rhino 3D as like you?

steve@localhost:~/.rhino3d7> cat winetricks.log
w_workaround_wine_bug-34803
remove_mono
remove_mono
winxp
dotnet40
dotnet48
renderer=vulkan
renderer=no3d


Banner tagline text is not visible in light mode.

🐛 Banner tagline text is not visible in light mode
In the banner, we can barely see the tagline text in light mode. It can be fixed and will be easy to catch.
Expected behavior
The tagline text should be easy to catch in the eye. For example, it could be white or gray-white colored at least.
Screenshot/Video
https://github.com/akshitagupta15june/PetMe/assets/122348996/cf2b8687-6fe7-4a65-a831-1362d2b9c53d

I want to work on it! Waiting to be assigned to this task.

Please allow me to work on this


[prod] Database Error

Got an email/Teams report from Greg Moran this morning stating that Moodle PROD was down generally with the following error:

I was able to login to the console and look at the logs for the pod in question.
I determined from the log that the pod had run out of disk space for its Persistent Volume Claim (PVC)
I expanded the PVC for moodle-1 in the DEV environment from 4gb to 8gb with no deleterious affect
I expanded the PVC for moodle-1 in PROD from 4gb to 8gb
The extra room allowed the pod to come back up on its own
Service restored

I don't really know if there will be knock-on effects from doing this, but I will continue to daily monitor for disk usage until Warren and Kunal come back from vacation and we can:
a) Figure out why the database is so big (it's likely logging too much and in the wrong place) and stop it growing so much
b) Codify standard responses to this sort of issue and
c) Have a disaster response plan in place that the Learning Centre can follow (me for now until we can hire the support FTEs)

Heard from Kunal (who graciously responded outside office hours) and told him about what I did. He assured me that the backup process looks OK and didn't mention any issues with the PVC capacity increase.
I will continue to monitor this.


RFC: Publish release notes extensibility

Problem
Release notes can have multiple homes, changesets updates the CHANGELOG.md files in the repo. We then have changesets/action which wraps the CLI tool to create a GitHub release.
This makes the responsibilities of the changeset components a bit difficult to understand. Git tagging is done by the changeset tool, but then the release is published by an external tool. Also the changeset action facilitates a very specific workflow, if you don't use that workflow then it's pretty clunky to get GitHub releases published.
Related issues
https://github.com/changesets/changesets/issues/264
https://github.com/changesets/changesets/issues/387
Proposed solution
New extension point which 'publishes' the release notes, it is run directly after tagging. I think the word publish is being overloaded though. Maybe we should call this 'target' or something else?
This will open up publishing release notes to BitBucket, GitLab or even to JIRA or other tools like Octopus Deploy etc.
Config
  "publish": [
    "@changesets/publish-github",
    { "repo": "changesets/changesets" }
  ],

There are a number of open issues, by splitting out the release notes publication step it would allow config for that package to be introduced, reducing top level config sprawl but also give the escape hatch
Migration
The changeset/action component should detect if the github publisher is not being used and create a note inside the PR to update your config. If it detects the config change has been made, it will no longer create the release because that will be done by changesets itself.

I think I overall like the idea because I found myself confused in the past about the responsibilities of each component and I've seen people being confused about this multiple times. It could also potentially make it easier to pass information between the CLI and the "publisher" - right now we are relying on parsing stdout which is... less than ideal.
To clarify - what would be the responsibility of changesets/action with this implemented? Would the sole responsibility of this "component" be to publish the release notes?

what would be the responsibility of changesets/action with this implemented? Would the sole responsibility of this "component" be to publish the release notes?

Open a pull request with the release notes, run changeset publish when there are no pending changesets?

I'd rename this config option to something like releaseNotes to make it clear what this component is about. One good thing about the current architecture~ is that changesets/action can be used without any further configuration. But perhaps in the future, it could provide the @changesets/release-notes-github as a default somehow. It can also continue working as it does for a considerable future (when changeset/config.json#releaseNotes would be absent).
We also need to figure out what arguments this should receive for it to create those release notes in a clean way.
I'd like to run this RFC by @mitchellhamilton before you get to implementing this - he might have some additional thoughts about this.

I think I'd rather see this as a separate CLI that works a bit differently to what the Action currently does. Basically, instead of looking at releases, work like the publish command does and read all the changelogs, extract out the latest releases, look at the GitHub releases and publish releases for ones that don't already exist. And we could have the "read all the changelogs, extract out the latest releases" part extracted into a package to make it easier to build these sorts of things.

What would be the motivation to keep this in a separate CLI? My main concerns about this idea and the current way of doing things are that I believe that passing around arguments is way more error-prone than extracting things from other files post-factum and the mentioned "components" fatigue. It is really not that straightforward for newcomers to understand how current pieces fit together - I've seen experienced devs being confused about this (to some extent) despite me explaining to them what each thing does. They probably grasped this right after my explanation but they were forgetting how this all works after a day or two. The current composition~ of the pieces is more unusual and hinders "internalizing" the execution flow.

I'm ok with @mitchellhamilton 's suggestion because I think it could fix some of the problems that you mention about the mental model @Andarist.
If the responsibilities of changeset cli were update CHANGELOG.md, version numbers in manifest files (package.json) and git tagging that is a nice box.
The CLI can then be updated to have read functionality, ie get me the changeset versions for package X. Get me the CHANGELOG for package@version
Then the publish GitHub release functionality can be pulled out of the changeset/action into it's own CLI tool, the action would then:

Version
Package Publish
Release notes Publish

There is a risk that it creates an ecosystem which feels like cobbling together tooling but documentation and nice scenario based guides could mitigate that. The main decision is if we want 'release notes publishing' to be an extensible out of the box function, or an additional tool to run after (I still am partial to the plugin model, but think either is an improvement on the current setup)

There is a risk that it creates an ecosystem which feels like cobbling together tooling

This is my concern here - the given new CLI wouldn't be completely decoupled from Changesets anyway because it would assume how the CHANGELOG.md has been generated, how headings are structured etc.
I somewhat doubt there is a huge demand for this being a separate CLI and I don't think would get a lot of non-Changesets users. And at that point... what's the point in separating them? :p

creating a new changeset cli purely for the purpose of encapsulating new opinions on how changelogs and releases are created will just result in more frustration from people who feel they have been excluded from using changesets to solve their particular workflow and process.
Instead if you release a new major version of changesets that is merely something to execute a pipeline on plugins (the defaults of which can be ones that replicate what changesets currently does).
Yes, you could argue that at this point: "how are we different from @conventional-commits/cli" ?
I would posit, that the differentiation would be the consideration (already) given to how people actually use monorepos.
Currently all the other tools, either don't care and ignore the problem, or expose some kind of path scoping option and then you're in charge of calculating changes and running a matrix of jobs on those changes:

https://github.com/googleapis/release-please

the current way of doing things are that I believe that passing around arguments is way more error-prone than extracting things from other files post-factum

Not sure if you're agreeing or disagreeing with my proposed behavior of "read all the changelogs, extract out the latest releases, look at the GitHub releases and publish releases for ones that don't already exist" but my reasoning behind that proposed behavior is so that if the publishing to GitHub releases fails or someone uses pnpm -r publish for example, running the publishing again would eventually result in everything being published.

I somewhat doubt there is a huge demand for this being a separate CLI and I don't think would get a lot of non-Changesets users. And at that point... what's the point in separating them? :p

That's fair, the main reason why is so that this potential separate CLI and Changesets itself can evolve separately. I'm particularly concerned about them evolving separately because the current behaviour of the action doing "publish the changelog entry for every package" is often not desirable given you often want an aggregated changelog entry so I'd want to avoid baking the assumption that you want to publish each changelog entry into Changesets itself.


✒ Add issue Templates

Follow the guidelines and add 2 issue templates

👨💻 New project
🐛 Bug Found

assign it to me


Unable to utilize ModelExpression with [HtmlAttributeName(DictionaryAttributePrefix = "myprefix-")] Dictionary

Within razor,  I've created the following:
<div<EMAIL_ADDRESS>I'd like to be able to create a tag helper with the following so I can create multiple [expression bound] attributes witht he same prefix.
     [HtmlAttributeName(DictionaryAttributePrefix = "myprefix-")]
        public IDictionary<string, ModelExpression> Values { get; set; } = new Dictionary<string, ModelExpression>();

However when running the application, I receive the following as runtime:

Dictionary values must not be of type 'Microsoft.AspNetCore.Mvc.ViewFeatures.ModelExpression'.

I should note that the razor tooling accepts the markup above.
Any thoughts would be greatly appreciated.

@NTaylorMullen @DamianEdwards Is there any specific reason to not support this?

MVC supports ModelExpression only when used as the type of a tag helper property.
Further this is a rather large feature request with an unclear upside. With no enforced commonality between the dictionary values (beyond being lambda expressions), about all the tag helper could do is evaluate the expressions and convert them to strings. What would you like to do with those values?

I should note that the razor tooling accepts the markup above.

How is that relevant?

Thanks for the quick responses @danroth27 & @dougbu...
The use case centers around [strongly-typed] template generation for Angular 2.  For example:
<input ng-bind-ngModel="MyProperty" ... />
becomes...
<input [ngModel]="myProperty" ... />
Utilizing DictionaryAttributePrefix would enable a simple set of TagHelpers that correspond to Angular's binding syntax:
https://angular.io/docs/ts/latest/guide/template-syntax.html#!#binding-syntax
Being "generic" (e.g. ng-bind-XXX) would allow for any Component property being able to be bound in this way.  This becomes especially important when targeting @Input annotations on UI Components. For example:
<my-button ng-bind-title="someTitleProperty" ... />
becomes...
<my-button [title]="someTitleProperty" ... />
While I certainly appreciate the effort to support ModelExpression the commonality [or lack of it] should be of no consequence to the TagHelper framework.  The Dictionary's value being a primitive type, a user-defined class/interface, object, etc provides no more "clarity" then ModelExpression as it's up to the author of the TagHelper to interpret these values accordingly, regardless.
As far as my note regarding the razor tooling, I was simply pointing out that this issue was not surfaced until run time.  Ideally, such "things" are flagged at design time.

ModelExpression is not just a primitive type. Something needs to create the ModelExpressions and the lambda expression needs to be based on the Model type.
I'm still not understanding the value of generating property.Add("title", new ModelExpression(m => m.someTitleProperty)) versus property.Add("title", someTitleProperty) i.e. using a Dictionary<string, string> property and ng-bind-title="@someTitleProperty".

ModelExpression is not just a primitive type. Something needs to create the ModelExpressions and the lambda expression needs to be based on the Model type.

My apologies, I was not asserting that ModelExpression  is a primitive type.  Instead I was indicating that the Dictionary's Value type  should be honored, regardless of type (e.g. primitive, class/interface, object, and ideally ModelExpression).  I do understand, ModelExpression  is special!!!

I'm still not understanding the value of generating property.Add("title", new ModelExpression(m => m.someTitleProperty)) versus property.Add("title", someTitleProperty) i.e. using a Dictionary<string, string> property and ng-bind-title="@someTitleProperty".

I need to get at the metadata for the Model's property.  At a minimum, I need the property's name, but perhaps other metadata as I look to support more advanced templating scenarios.  If I'm not mistaken, "@someTitleProperty" would simply yield that property's value, not its name (just tested and confirmed).  Not to mention, that if the property was not a string (e.g. int),Razor seems to doing an implicit convert of int => string.  In this case, someInt = 123 would generate [title]="123", this is obviously not the desired result.

Do you need both the property's name and it's value? I'd like to understand whether you need a ModelExpression versus an editing context which helps you type only model property names i.e. use a Dictionary<string, string> property and ng-bind-title="someTitleProperty" but prevent typing ng-bind-title="notAProperty" .

I do not need the value...  In fact, in all likelihood, I won't even have a controller given that the Component I've been referencing is being utilized in lieu of an actual controller.  So, no return View(new SomeModel()) necessary.
So I understand, in the ng-bind-title="someTitleProperty" markup, how are the following distinctions to be made/enforced?:

ng-bind-title="someTitleProperty" // The model someTitleProperty property's  "Editing Context"
ng-bind-title="someTitleProperty" // The string literal "someTitleProperty"

how are the following distinctions to be made/enforced?

Your requirements are now much more clear. They might be satisfied any number of ways e.g. a new [HtmlAttributeName(OnlyModelProperties = true)] property and some tooling support. But your original Dictionary<string, ModelExpression> idea is likely less work. Put another way, I agree this is a valid use case for such a tag helper property -- the first we've heard about.
This issue is currently in the backlog, meaning we would accept a well-written PR filling the gap.
In the meantime, I'd recommend using a Dictionary<string, string> and having your customers use nameof in the .cshtml file e.g. ng-bind-title="nameof(Model.someTitleProperty)".
Your tag helper could also confirm the dictionary values match one of ViewContext.ViewData.ModelMetadata.Properties.Select(p => p.PropertyName). Hmm, that might be the cheapest solution here though it wouldn't be enforced at design time.

@dougbu, Thanks for the great exchange!  The issue with @nameof is that you loose support for dot-notation:
@nameof(Model.MyClass.MyProperty)  produces [title]="myProperty" when it should render [title]="myClass.myProperty", but...
Please pardon my ignorance, first time getting to this point.  As for a PR, should I create one? is there a template?  How to submit?
Thanks again!

I agree deeper properties get more complex when using the tag helper enforcement approach. Probasbly best to have users type in arbitrary dotted property names and recursively checking each segment (at runtime) in the tag helper.
Note Dictionary<string, ModelExpression> has something of the opposite problem: There's no restrictions on the lambda expression used: While asp-for="myClass.myProperty" is common<EMAIL_ADDRESS>is completely supported.
Feel free to create a PR. I suspect the core change will be in MvcTagHelperAttributeValueCodeRenderer but the bulk of the effort will be on tests. Fork the MVC repo in your own GitHub repo, create a branch containing the feature, then submit a PR in this repo using that branch.

@dougbu confirmed that this ought to be fairly straight-forward to fix - it mostly consists of removing the exception and updating tests.

I've just forked the repo and have begun to dig into the existing tests to see where best to incorporate then necessary test(s) as part of my TDD.  I'm struggling to locate an existing set of tests that explicitly parses, generates AND renders the necessary markup.
@dougbu, You were right... the heavy-lifting was in the tests!
I was able to build out an specific TagHelper test (based on InputTagHelperTest for ModelExpression and FormTagHelperTest for prefix-value specification examples) which of course worked b/c the ModelExpression was explicitly added to the Dictionary of values annotated with DictionaryAttributePrefix.
In addition, I was able to adjust the Razor.Host test's ModelExpressionTagHelper.cshtml file to include an instance of my DictionaryAttributePrefix-based test tag helper.  The code generated properly [seemingly] but never "renders" it thus the tests do not throw the aforementioned exception, thereby allowing me to resolve.
Any guidance would be greatly appreciated.  I'd really like to run this down to completion.

@cjrosa updating the tests using InputTestTagHelper and ModelExpressionTagHelper.cshtml to cover IDictionary<string, ModelExpression> is a great start. That basically ensures the generated C# looks as expected.
Note even that test will fail unless you change MvcRazorParser. But you're correct confirming compilation succeeds and everything connects end-to-end would be useful here.
I suggest adding one similar functional test, extending the TagHelpersWebSite, that adds a couple of expressions to the dictionary. Not sure exactly what the new tag helper should do w/ the dictionary but fine as long as the response makes it obvious the expected entries are present.

60d600d

@cjrosa many thanks for finding this issue and then fixing it!

I have also created a tag helper that uses a dictionary of types <string, ModelExpression>, and it works great.
But when a view (.cshtml) that uses this taghelper is open in VS, building the solution still gives this output in the VS Error List:
Error		Invalid tag helper property 'SomeNamespace.SomeTagHelper.some-prefix'. Dictionary values must not be of type 'Microsoft.AspNetCore.Mvc.ViewFeatures.ModelExpression'.
Is this some error in VS? I'll report it in the VS feedback tool as well.

@deap82 can you please open a new issue on https://github.com/aspnet/Razor and include a screenshot of the error in the errors window.
Posting feedback on a closed issue makes it really easy for us to lose track of it.

@rynowak
Done; https://github.com/aspnet/Razor/issues/1444
It's also posted here and got a "Triaged" state: https://developercommunity.visualstudio.com/content/problem/66937/vs-reports-invaliud-tag-helper-property-even-thoug.html


Remove condition change handling

Investigated why we still use changed:

All our tests still work without it
We introduced pkg/conditions/condition_manager.go#102-110
which we believe ensures the status object emitted by finalize()
is identical when nothing has changed.
manually ensured that client.Status().Update() does not cause a
resourceVersion bump when applying an identical status.

Co-authored-by: Emily Johnson<EMAIL_ADDRESS>

Doesn't the old implementation avoid unnecessary calls to StatusUpdate() ?


faultInjectionPolicy on Direct Response

Title: faultInjectionPolicy on Direct Response
Description:
I have been attempting to configure fault injection on a direct_response configuration and it doesn't seem to be valid unless I'm proxying to some kind of upstream even if the upstream is a microservice on localhost.  Is this possible? The documentation is very unclear.
Example Configuration:
admin:
  address:
    socket_address: { address: <IP_ADDRESS>, port_value: 15000 }

static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address: { address: <IP_ADDRESS>, port_value: 9090 }
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          codec_type: AUTO
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match: { prefix: "/" }
                direct_response:
                  status: 200
                  body:
                    inline_string: "we're good"
              - match: { prefix: "/delay/10"}
                direct_response:
                  status: 200
                  body:
                      inline_string: "10 second response"
                  route_action:
                    faultInjectionPolicy:
                      delay:
                        fixedDelay:
                          seconds: 10
                          nanos: 0
          http_filters:
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
          - name: extensions.filters.common.fault.v3.FaultDelay
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router

cc: @zuercher

@RyanTheOptimist can you update the tags so this doesn't close? Id really like an answer on this


Extend toHaveFetched test output to show options diff

Asserting against a certain output, especially a body, is currently very cumbersome.
Scenario: I want to mock a POST request with a specific body, and i want to piece together the body in a test-driven manner.
The assertion only tells us that fetchMock was not called with the right url, which is not even technically correct. This is what it looks like if i pass a wrong body:

The only way to proceed now is to manually console.log the calls i've received with fetchMock.calls() and see where it goes wrong.
In this PR i've extended the output to:

json-parse the body (if possible)
use jest-diff to display the diff between the expected options object and the received options object
for all calls that match the filter

This is what the new output looks like:

still waiting on an update here :)

published under<EMAIL_ADDRESS>for preview purposes

published new version with latest jest version under<EMAIL_ADDRESS>

@wheresrhys Any thing we can do to help get this merged in? This would make dealing with assert failures much easier to understand.

Yeah, that's really a pain to distinguish between not-called API and called with a different request payload. Also have spent quite a lot of time just to figure out what's the cause for such an error report.

Updated the fork to newest version of jest, available under<EMAIL_ADDRESS>new functionality:
you're now able to use jest matches in the body you are expecting. for example:
fetch('http://example.com/path', {
	method: 'post',
	headers: {
		test: 'header',
	},
	body: {
		test: {
			value: "value"
		},
		otherValue: {
			value: "value"
		}
	}
})

it("matches when using jest expect matchers", () => {
	expect(fetch).toHavePosted('http://example.com/path', {
		method: 'post',
		headers: {
			test: 'header',
		},
		body: expect.objectContaining({
			test: {
				value: "value"
			}
		})
	});
})

+1 I was about to start looking into writing this. So nice to see someone has already written the code. What do we need to do to get this merged?


Use Instasharp in Asp.net Web Form

Hi
How Login,Authentication user And Show My Feed In Asp.net Web Form 4.5 ?

!?

I don't have any sample. You probably need to use ASHX to login.
Instagram removed my feed API


Failing To Open Viewport After Abrupt Debug Exit

Overview
While working through replacing the hexView component w/ the data editor, I've been seeing an issue in version 0.9.76 where Omega Edit will continuously fail to create a viewport of the DFDL Debugger data file.
It will initially create and serve a viewport successfully. The failures occur when stopping the DFDL debugger, closing the window, then attempting to re-run the DFDL debugger w/ the same schema and data file.
It seems that if the data editor is left open when closing VSCode, the extension or Omega Edit will not properly handle the destroySession function call. This leaves a lingering Omega Edit server with an active viewport of the previously opened data file.

Per @stricklandrbls:

This is resolved by DataEditorClient Content Disposal Resolution by stricklandrbls · Pull Request #961 · apache/daffodil-vscode (github.com)
It was just a matter of making sure a DataEditorClient instance was being disposed of when the panel is closed / debug session termination. What was happening was the the disposables for a DataEditorClient instance we being pushed to the vscode ExtensionContext so they would only be disposed of when the extension was closed. Also, portions of the DataEditorClient instance were being disposed on panel close so when the extension tried to dispose the related Disposables, it would just fail and never hit the destroySession or stopServer portions of the code.


Feat request: backend agnostic compression

Hi,
Would it be possible to add an option for compressing values before they are sent to the cache backend?
I see that Badger supports zstd, but others don't (I use Redis).
thanks

Hi @tasiotas, actually I'm not compressing data before send them to the storage provider, I need to have some metrics about the cost to decompress data each time we want to get them.

sorry, I wasn't clear enough.
I would like to compress data before sending to backend.
I am aware of possible costs of compression/decompression.
Perhaps giving user option to choose compression level and algorithm, so we can decide costs vs benefits of saving memory.
http://facebook.github.io/zstd/
Seems like zstd is the king 👑

Compressor name
Ratio
Compression
Decompress.

zstd 1.4.5 -1
2.884
500 MB/s
1660 MB/s

zlib 1.2.11 -1
2.743
90 MB/s
400 MB/s

brotli 1.0.7 -0
2.703
400 MB/s
450 MB/s

zstd 1.4.5 --fast=1
2.434
570 MB/s
2200 MB/s

zstd 1.4.5 --fast=3
2.312
640 MB/s
2300 MB/s

quicklz 1.5.0 -1
2.238
560 MB/s
710 MB/s

zstd 1.4.5 --fast=5
2.178
700 MB/s
2420 MB/s

lzo1x 2.10 -1
2.106
690 MB/s
820 MB/s

lz4 1.9.2
2.101
740 MB/s
4530 MB/s

lzf 3.6 -1
2.077
410 MB/s
860 MB/s

snappy 1.1.8
2.073
560 MB/s
1790 MB/s

after thinking about it for a while:

zstd is not the best algorithm for this case. As none of the browser can accept responses encoded with zstd, it would have to be decompressed before sending to the client. With gzip and brotli this can be avoided, so we only have to pay the cost of compressing.
I can encode responses with Caddy's encode directive before it's sent to cache, but is that going to work if souin receive encoded response? Seems ok at first glance, but you might have a better idea.

Might not need any implementation in souin after all!
Caddyfile
{
  debug
  order cache before rewrite
  order cache before encode
  cache {
    log_level debug
    allowed_http_verbs POST
    ttl 20000s
    api {
      souin
    }
    redis {
      url redis:6379
    }
}

website.com {
  handle /api* {
    encode {
      gzip
    }
    reverse_proxy http://django:8000
    cache
  }
}

That's great if it can work without any additional code! But I wonder if the encode respect the no-transform Cache-Control directive. That means in the request context that the requests should not be altered and the same in the response context.

unfortunately it ignores it.
I tried curl with -H "Cache-Control: no-transform" and it returned and cached gziped response

FWIW:
  order cache before rewrite
  order cache before encode

This doesn't make sense, only the last order for a directive you set will take effect. So effectively it will be before encode, always.
What order does is insert the directive at some spot in this list https://caddyserver.com/docs/caddyfile/directives#directive-order at the position you specify.

thank you @francislavoie for pointing out my silly line of code.
I forgot to remove first line during debugging.

compression is working well, thanks!


Please add query with params to ScanamoFree

Guys, could you add to ScanamoFree method with access to  all query options, something like this
object ScanamoFree {

  type QueryResult[K, V] = (List[Either[DynamoReadError, V]], Option[Either[DynamoReadError, K]])

  //...

  def queryWithParams[K, T](t: Table[T])(
      index: Option[String],
      query: Query[_],
      options: ScanamoQueryOptions
  )(implicit kf: DynamoFormat[K], tf: DynamoFormat[T]): ScanamoOps[QueryResult[K, T]] =
    QueryResultStream
      .stream[T](ScanamoQueryRequest(t.name, index, query, options))
      .map({
        case (v, ko) => (v, ko.map(k => kf.read(k.toDynamoValue)))
      })
 //...
}

hi @Ravenow
Would you be kind enough to let me know what use case the Table query DSL does not solve that you need access to the underlying data types?
That would be super useful 🙏 There are a few things that bother me with the current API, mostly that there is not typing for keys and no proof one can extract a key from a record (which is why you have to universally quantify on K 😞 ).
Also: are you directly using ScanamoFree methods?

I just wanna query secondary index with filter condition and some sort of "pagination"
val scanamo: ScanamoCats[F] = ???
val devices: Table[Value] = ???

  def indexQuery(
      query: Query[_],
      filter: Option[Condition[_]],
      limit: Int,
      startKey: Option[StartKeyValue]): F[QueryResult[StartKeyValue, Value]] = {
    val startKeyObj = startKey.map(DynamoFormat[StartKeyValue].write).flatMap(_.asObject)
    val queryOptions = ScanamoQueryOptions.default.copy(
      limit = limit.some,
      filter = filter,
      exclusiveStartKey = startKeyObj
    )
    scanamo.exec(queryWithParams(table)(index.some, query, queryOptions))
  }

Ha, pagination is back! Excellent topic, as recently I introduced scanPaginatedM and queryPaginatedM and was wondering if there were existing users out there. Have you seen and/or tried them out already?

Yeah, i seen them, but from my point of view there is no way to specify filter and startKey. Also for me its not clear how to extract key from response in methods you mentioned :)

Yes, fair enough. I think we just need to add a more generalised version of those APIs that allows you to stop in the middle. Adding a callback that receives the start key should be enough. As for the filter, indeed this is more complex 🤔 Let me think about it.

I think it will be a good tradeof if there would be fancy dsl for common things, but when there is need to dive deeper u could use some advanced api with all features available.
PS: Wanna mention that i wouldnt post any issues here if scanamo internals not private :)) Because for now there is no way to add extension methods(via implict classes) or change behaviour without copy&paste some part of scanamo internals into the project.

@Ravenow hi, sorry for the delay. You can use table.from(key).scan0 for example. scan0/query0 produce the raw result, while from allow you to set a starting key.


buildMavenPackage: quote maven directory

Description of changes

The path for the maven artifacts gets built in the shell script. However the identifier (or whatever is the right terminology in the maven world) might contain characters that mess up this path building. Concretely I ran into the issue when a dependency version range was specified and the brackets tripped the shell.
Things done

Quoted the directory path.

Built on platform(s)

[x] 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

[x] 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/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Recent changes in the maven build architecture made this change obsolete.


Implement time-delta fulfillment (making jobs queries work)

The growth rate computation considers last 10 years and ensures it is resilient to seasonality for monthly data.
Also, include jobs and medical conditions topic SVs under an SVPG.
With this PR, the two jobs queries and health query should be handled, as shown below.

TESTED: all Jan demo scripts

Thanks both for the quick review!


About bbs and topo

I would like to know how the bbs and topo in the COF database(or other) are decomposed.
Do you decompose by cif?
Thanks!

Hi @Yong-Q,
Can you elaborate on what you mean by BBS and TOPO being disassembled, do you mean when you create the BBS and TOPO database?

Right, I just wanted to ask you about how to create BBS ahd TOPO database.
Best wishes!

For the topology, we used the cgd file available in the RSCR database (https://rcsr.anu.edu.au/). For 2D topology, we converted it to 3D and used it. For building blocks, we used 130 genetic structures provided by Lan et al (
Materials genomics methods for high-throughput construction of COFs and targeted synthesis), we used the 130 genetic structure units provided by Lan et al, adding functional groups.
We did not decompose the building blocks separately. If you want to decompose the building blocks, you can use the decomposer provided by pormake. (https://github.com/Sangwon91/PORMAKE/blob/main/pormake/experimental/decomposer/README.md)

For Topo, it is not the case that every porous material is consistent, whether COF or MOF

What exactly do you mean by "not consistent" - do you mean different types of topologies used, or do you mean that the same topology can be used differently?
For topoolgy types, the type used for each material in the synthesized database can be different. In our work, we dealt with hypothetical porous materials, so we assumed that we could create hypothetical topologies that were not synthesized. Therefore, we created hypothetical porous materials regardless of the actual topology used. This is because the porous materials we created are only used in the pre-training process for PMTransformer, so we do not need strict criteria for each material. If each material needs to be created with strict criteria, such as a generative model, the topology can be determined using a program such as topospro after decomposition into building blocks.
The different use of topology seems to depend on the building block. If the building block is a complex conformation, it may be determined to be a different topology than the one previously generated by pormake according to the strict definition of topology. (see: figure 1 of MOFId paper https://pubs.acs.org/doi/10.1021/acs.cgd.9 B01050) In our work, the topology was determined as single node, and the topology may be different if used with other methodologies (e.g. all node, metal-oxo). However, we believe that this depends on the basis of dividing the building blocks and not on the porous material.

I see what you mean. The key to distinguish MOF from COF is whether there are metal nodes in bbs.
Thanks!


The app is taking a lot of time while doing associate contact.

@Parsh please debug and identify the time-consuming steps in this process.

-Verified this issue on dev app v1.7.5(299)


IOptionsSettings rename and implementation change

Two major changes:

Renamed IOptionsSettings -> IEnvironmentOptions to better reflect what it actually provides; environment options.

Changed it's implementation to call through IDteServices - so it no longer needs to do a UI thread check and GetService.

tag @dotnet/project-system


add 3 x scale images for icons where svg cannot be used

Description
add 3 x scale images for icons where svg cannot be used
Note: Ideally these should be svg not png
Use images 3 x required size to allow for pixel density
On what platform have you tested the change?

[x] Android - Emulator
[ ] Android - Physical device
[x] iOS - Emulator
[ ] iOS - Physical device

Screenshots

Please attach screenshots showing the change if relevant
Checklist

[ ] I have updated mockServer
[ ] I've added analytics as relevent
[ ] I have run npm test
[ ] I have run npm run test:i18n

Out of scope and potential follow-up
Is there any related changes that you plan to do in a follow-up PR or voluntarily excluded from the scope?

@petermason Would this approach here be of use:
https://docs.expo.io/versions/v36.0.0/react-native/images/

@petermason Would this approach here be of use:
https://docs.expo.io/versions/v36.0.0/react-native/images/

@petermason Would this approach here be of use:
https://docs.expo.io/versions/v36.0.0/react-native/images/

I'm simply loading the larger version and setting the size to an absolute amount so will work for all devices.

@petermason Would this approach here be of use:
https://docs.expo.io/versions/v36.0.0/react-native/images/

I'm simply loading the larger version and setting the size to an absolute amount so will work for all devices.


Open FAB button to the right side

Can I do a FAB (action) button open options to the right side instead the left side?

The design spec if for the button to be on the right, so right now it only supports opening up and to the left. but you can easily modify the code if you want it to do something else.

@Dogfalo Thanks, could you help pointing out witch are the property i need change to overwrite this behavior ?


Conductor refactor follows

What Changed

Major conductor, basic data model refactoring
Removed a bunch of unused code
Replaced a good number of integration tests with unit tests

Issues

Fixes #377
Fixes #371
Fixes #370

For #377, let's not use the phrase 'kill contract.'
Instead:

remove contract from use
disable and archive contract
remove contract

@shellicious while I agree with using a less violent word in spirit, we should probably stick with the language used by OMB as a rule.

Can I merge this?

Screenshots:


highlight theme if table

Moves the highlight.createHighlightGroups for a theme so that inline custom themes can be parsed as well. Otherwise the readme is incorrect

Used some local state to track the theme changes and only apply the highlighting once.

Used some local state to track the theme changes and only apply the highlighting once.

Used some local state to track the theme changes and only apply the highlighting once.

This approach does prevent you changing the theme live in an instance, which is quite nice to try them out now there's multiple (or if you're defining your own). Maybe there could be a specific function to both set M.theme and reset theme_set?

Used some local state to track the theme changes and only apply the highlighting once.

This approach does prevent you changing the theme live in an instance, which is quite nice to try them out now there's multiple (or if you're defining your own). Maybe there could be a specific function to both set M.theme and reset theme_set?

This is resolved with https://github.com/hoob3rt/lualine.nvim/commit/3ab706671898746c268f59ca7f02a4919072690f
Have fun setting your colorscheme!

This is resolved with https://github.com/hoob3rt/lualine.nvim/commit/3ab706671898746c268f59ca7f02a4919072690f
Have fun setting your colorscheme!


Reopen previous files being edited

The last files, including REPLs, should be opened when I relaunch light-table.

Just install the Reminisce plugin via plugin manager. It reopens the files upon reopening LT


OkHttpClient sync

This PR introduces:

sync interface for http client with default blocking over async impl
sync implementation in okhttp client package
more httpclient tests for various types of binary data.

Disclaimer. This is mostly to unblock benchmarking not to provide perfect impl.

API changes have been detected in com.azure:azure-core. You can review API changes here

API changes have been detected in com.azure:azure-core-test. You can review API changes here

API changes have been detected in com.azure:azure-core. You can review API changes here


why i can't find plugin-descriptor.properties in this branch

hi,i'm using elasticsearch and i want to watch it's states,howerve,after i install elasticsearch,when i use command:plugin install lukas-vlcek/bigdesk ,i get an error like this:
Trying https://github.com/lukas-vlcek/bigdesk/archive/master.zip ...
Downloading ..........................................................................................................................................
..............................................................................................................DONE
Verifying https://github.com/lukas-vlcek/bigdesk/archive/master.zip checksums if available ...
NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Could not find plugin descriptor 'plugin-descriptor.properties' in plugin zip
and i can't find this file ,so i wonder why this file was not included,do you miss or delete it?

thanks to #76 ,he also found this problem,but his plugin-descriptor.properties seems can't work,i still can't start my elasticsearch,so i change this file as follows:
description=bigdesk - Live charts and statistics for Elasticsearch cluster.
version=master
site=true
name=bigdesk
then i succeed

This is still an issue with the latest elastic(2.1.1-1)

Verifying https://github.com/lukas-vlcek/bigdesk/archive/master.zip checksums if available ...
NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Could not find plugin descriptor 'plugin-descriptor.properties' in plugin zip

Seems like the issue is fixed, but still not merged. I have modified the code to work on elasticsearch 2.2.0 and kept it at https://github.com/jayant2014/bigdesk
It is tested with 2.2.0 and works fine.

Hello @jayant2014,
I tried with plugin install https://github.com/jayant2014/bigdesk/archive/master.zip and it doesn't work for me on ES 2.2.1. Do I need to do something specific to get it work on 2.2.1 ?
Thanks.

@nsphung  This worked for me.
bin/plugin install jayant2014/bigdesk

I have modified bigdesk code to be compatible with elasticsearch 2.x
https://github.com/nishantsaini/bigdesk
Hope this helps

I am archiving this repository now. Thanks for contributions.


Add color space for Linear Rec2100

Closes #443
I wasn't 100% sure if I should use the toBase and fromBase functions from Linear Rec2020 or import the matrices from Linear Rec2020 and set the toXYZ_M and fromXYZ_M options.

Looks good overall, not sure what to do about the linting errors though.


Updating plot_track from gliderpy

Adding new function plot_track to plotting.py, decorating with pandas-flavor and adding pytest .

There are conflicts in this PR. You probably need to update your main branch or start new PRs directly from upstream/main. We can go over this in today's meeting.

pre-commit.ci autofix


Modify zone in RFC 1035

I want to try store zones in kv storage key - domain, val - full zone.
But if i need update zone for example add / delete record do it possible to do that using this package?
Or how can i do that?

[ Quoting<EMAIL_ADDRESS>in "[miekg/dns] Modify zone in RFC 1035..." ]

I want to try store zones in kv storage key - domain, val - full zone.
But if i need update zone for example add / delete record do it possible to do that using this package?
Or how can i do that?

Uhm? How is this question related to go dns? Other than that you're storing DNS
data.

Ok, i have zonefile , and i parse it via this package, does it possible to add RR record to exiting parsed zone or modify ?

[ Quoting<EMAIL_ADDRESS>in "Re: [miekg/dns] Modify zone in RFC ..." ]

Ok, i have zonefile , and i parse it via this package, does it possible to add RR record to exiting parsed zone or modify ?

This package has no concept of a zone, there only is a []dns.RR so you'll have
to implement that yourself.

Thanks! If i have []dns.RR does this package support serializing it to buffer in RFC 1035 style ?

Yes, this package supports the wireformat


Update create_endpoint.py

Flashboot is not an option.
See API docs:
https://rachfop.github.io/ghpages/runpod.api.ctl_commands.html#create_endpoint
Parameters for create_endpoint

Parameter
Type
Description

name
str
The name of the endpoint.

template_id
str
The ID of the template to use for the endpoint.

gpu_ids
str
The IDs of the GPUs to use for the endpoint.

network_volume_id
str
The ID of the network volume to use for the endpoint.

locations
str
The locations to use for the endpoint.

idle_timeout
int
The idle timeout for the endpoint, in seconds.

scaler_type
str
The scaler type for the endpoint (e.g., 'manual', 'auto').

scaler_value
int
The scaler value for the endpoint, used in conjunction with scaler_type for scaling settings.

workers_min
int
The minimum number of workers for the endpoint.

workers_max
int
The maximum number of workers for the endpoint.

Which version of the SDK were your docs made from?


Invalid tokenization

Function call is different from function definition but the extension mark both of them as function definition.
The desired behavior is that function call are differentiated from declaration and thus colored by a color other than the color assigned to function definition.

This may be an issue with the C# textmate grammar. If this is still a problem, please open an issue at https://github.com/dotnet/csharp-tmLanguage/issues


Disable XInput => use DS4 as DS4

The double input issue can be turned off with the 'Hide DS4' option. I would like to do the reverse, hide the XInput-emulated DualShock 4 and use it as a DS4 alone, as if the driver were never installed.
Is this possible? If not, consider this a feature request.

You can get these feature now...
Is easy... modify a Profile, and you can see the option "Use Dimput Only".
But the only problem you need to disable the "Hide DS4" option in Settings, but a good idea is making this thing in profiles too... and you can change easily Emulated xBox360 to Real DS4 Profile without open the DS4Windows with Swipe to change profiles.

Thank you very much for your swift and helpful response!
I had no idea that plain DS4 worked merely as a generic DirectInput controller (which means no rumble!). I was under the impression by online commenters that the buttons in Dragon's Dogma: Dark Arisen and Metal Gear Solid V would magically change to DS4 style, but I just tried it and can confirm that's not the case.


big num with trend line: strange results.

Make sure these boxes are checked before submitting your issue - thank you!

[X ] I have checked the superset logs for python stacktraces and included it here as text if any
[X ] I have reproduced the issue with at least the latest released version of superset
[ X] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
{"GIT_SHA": "", "version": "0.18.2"}
Expected results
When using 'big number with trend line, the number shown is consistent with big num, and table view.
Actual results
Big num shows the correct value, as does table big num with trend line shoes something else.
Steps to reproduce
Using this data:
__timestamp	sum__price
5/24/17 14:27	160
5/24/17 14:30	170
5/24/17 14:35	230
5/24/17 14:41	161
5/24/17 14:45	90
5/24/17 14:48	170
5/24/17 14:54<PHONE_NUMBER>
5/24/17 14:56	170
5/24/17 15:09	0
This data came processed via superset csv export. It matches the source data
Ok:

Change type to big num with trend line:

Big Number with Trendline shows the last data point value in the time series. Big number shows the sum that applies over the period selected. If you want Big Number to show the latest data point, you can add some subquery in the WHERE clause as in dt IN (SELECT max(dt) FROM foo WHERE dt > [reasonable time range]). The WHERE [reasonable time range] in the subquery can be useful depending if that field is partitioned or indexed, avoiding an full extra table to find the max date.

Ok.. My expectation was that big num with trendline would show the same value as big number: the metric over the time period.  Now I know.. thanks!


Load pause music asynchronously

This is good but do not use name?.function() as many people still use older haxe versions to compile

Ok


Llama factory

Hi Dusty,
We can use the GPU on Jetson to fine-tune large models. I have successfully loaded and fine-tuned the Phi-1.5-1.3B model using llama-factory on the Orin NX 16GB, and the results are very good.

According to the estimates from llama-factory, we can even fine-tune a 70B model on the AGX Orin 64GB device.

This is cool @yuyoujiang , thanks.  Can you try dustynv/llama-factory:r36.3.0 ?  I added flash-attention to it.  I saw the web UI but did not run a training.

Thank you for your interest in this container. I tested the container you provided and it does have a problem. There seem to be two crises:

Can not access huggingface.co.
This problem may be due to the Python version (The default python version of Jetpack6 is 3.10), I refer here to reduce requests==2.27.1  after the training program can be normal operation.

Do not have permission to access the protected model.
If we need to download the model like llama3 from huggingface,  we need to do some extra work.

Request access to the llama3 at huggingface .
Configure the huggingface token by huggingface-cli login in the jetson. I have tried to configure global variables when starting the container, but doing so does not work. (--env HUGGINGFACE_TOKEN=<YOUR-ACCESS-TOKEN>)

I use the following steps to start the training program:

bash sudo docker run -it --network host --runtine nvidia -v /home/seeed/jetson-containers/data:/data dustynv/llama-factory:r36.3.0
Open another terminal, enter the container above (docker exec), and execute: bash pip3 install requests==2.27.1
Set Model name: Phi-1.5-1.3B, Dataset: alpaca_zh  and other parameters remain default
Click the Start button to start the training program


Do I have to define attributes?

I'm lazy and dont want to define attributes. Is possible to utilise Object.keys to help with this? Here's my concept
var user = Parse.User.current();
Parse.defineAttributes(Parse.User, Object.keys(user.toJSON()));

This wont work as I'm defining the attributes after the Get. But maybe there another way Object.keys can be used.

This should work
var user = Parse.User.current();
Parse.defineAttributes(Parse.User, Object.keys(Parse.User.prototype.attributes));

or
var user = Parse.User.current();
Parse.defineAttributes(user, Object.keys(user.attributes));


CMake parallel build failure

Summary
👋 trying to build the latest release, but run into some build issue. The error log is as below:

build error
[ 95%] Generating suites/test_suite_psa_crypto_generate_key.generated.data, suites/test_suite_psa_crypto_not_supported.generated.data, suites/test_suite_psa_crypto_storage_format.current.data, suites/test_suite_psa_crypto_storage_format.v0.data cd /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0 &&<EMAIL_ADDRESS>/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/../tests/scripts/generate_psa_tests.py --directory /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests/suites Traceback (most recent call last): File "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/scripts/generate_test_code.py", line 1142, in <module> main() File "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/scripts/generate_test_code.py", line 1133, in main generate_code(funcs_file=args.funcs_file, data_file=args.data_file, File "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/scripts/generate_test_code.py", line 1055, in generate_code raise IOError("ERROR: %s [%s] not found!" % (name, path)) OSError: ERROR: Data file [/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests/suites/test_suite_psa_crypto_storage_format.v0.data] not found! make[2]: *** [tests/test_suite_psa_crypto_storage_format.v0.c] Error 1

System information
Mbed TLS version (number or commit id): 3.1.0
Operating system and version: macOS 12
Expected behavior
build successfully
Steps to reproduce

untar 3.1.0 tarball file
cmake -S . -B build -DUSE_SHARED_MBEDTLS_LIBRARY=On<EMAIL_ADDRESS><EMAIL_ADDRESS>-DCMAKE_INSTALL_PREFIX=/opt/homebrew/Cellar/mbedtls/3.1.0 -DCMAKE_INSTALL_LIBDIR=lib -DCMAKE_BUILD_TYPE=Release -DCMAKE_FIND_FRAMEWORK=LAST -DCMAKE_VERBOSE_MAKEFILE=ON -Wno-dev -DBUILD_TESTING=OFF -DCMAKE_OSX_SYSROOT=/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk
cmake --build build

Additional information
full build log, https://github.com/Homebrew/homebrew-core/runs/4571515113
relates to Homebrew/homebrew-core#91501
relates to Homebrew/homebrew-core#92136

I can't reproduce this: I tried (also on an M1 Mac with Homebrew installed) and cmake --build build completed successfully.
test_suite_psa_crypto_generate_key.generated.data is present in the release, so it doesn't need to be generated. This is a generated file that only depends on other source files, not on the library configuration or the platform. We no longer keep such files in the git tree in the development branch, but we add them to releases.
Looking at the release content, it seems that we aren't changing the build scripts to not attempt to rebuild those files. The file timestamps in the official archive are the time the archive was generated, so if they're preserved on extraction, they should match and make shouldn't attempt to re-generate the file. But if the timestamps don't match for some reason, the build may attempt to re-generate those files. That's not the behavior you intended. However, regenerating those files should still work if not cross-compiling (the generation of test_suite_psa_crypto_generate_key.generated.data needs to compile a C program that runs on the host).
Looking at the logs, I see another problem, or maybe two problems.
2021-12-18T22:37:37.9204050Z [ 95%] Generating test_suite_psa_crypto_storage_format.v0.c
2021-12-18T22:37:37.9207770Z cd /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests &&<EMAIL_ADDRESS>/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/scripts/generate_test_code.py -f /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/suites/test_suite_psa_crypto_storage_format.function -d /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests/suites/test_suite_psa_crypto_storage_format.v0.data -t /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/suites/main_test.function -p /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/suites/host_test.function -s /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/suites --helpers-file /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/suites/helpers.function -o .
2021-12-18T22:37:37.9212570Z Deleting primary custom command output "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests/suites/test_suite_psa_crypto_generate_key.generated.data" because another output "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests/suites/test_suite_psa_crypto_storage_format.v0.data" does not exist.
2021-12-18T22:37:37.9214930Z /Applications/Xcode.app/Contents/Developer/usr/bin/make  -f tests/CMakeFiles/test_suite_psa_crypto_storage_format.current.dir/build.make tests/CMakeFiles/test_suite_psa_crypto_storage_format.current.dir/build
2021-12-18T22:37:37.9216780Z [ 95%] Generating suites/test_suite_psa_crypto_generate_key.generated.data, suites/test_suite_psa_crypto_not_supported.generated.data, suites/test_suite_psa_crypto_storage_format.current.data, suites/test_suite_psa_crypto_storage_format.v0.data
2021-12-18T22:37:37.9219220Z cd /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0 &&<EMAIL_ADDRESS>/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/../tests/scripts/generate_psa_tests.py --directory /tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests/suites
2021-12-18T22:37:37.9220640Z Traceback (most recent call last):
2021-12-18T22:37:37.9221570Z   File "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/scripts/generate_test_code.py", line 1142, in <module>
2021-12-18T22:37:37.9222270Z     main()
2021-12-18T22:37:37.9223090Z   File "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/scripts/generate_test_code.py", line 1133, in main
2021-12-18T22:37:37.9223920Z     generate_code(funcs_file=args.funcs_file, data_file=args.data_file,
2021-12-18T22:37:37.9224970Z   File "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/tests/scripts/generate_test_code.py", line 1055, in generate_code
2021-12-18T22:37:37.9225770Z     raise IOError("ERROR: %s [%s] not found!" % (name, path))
2021-12-18T22:37:37.9226890Z OSError: ERROR: Data file [/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests/suites/test_suite_psa_crypto_storage_format.v0.data] not found!
2021-12-18T22:37:37.9227850Z make[2]: *** [tests/test_suite_psa_crypto_storage_format.v0.c] Error 1

So generate_test_code.py can't find test_suite_psa_crypto_storage_format.v0.data even though it has been successfully re-generated above. With the mixture of absolute and relative paths in the logs, it's not clear to me at this time whether the file was generated in the same directory where the build later expects it.
I also see Deleting primary custom command output "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests/suites/test_suite_psa_crypto_generate_key.generated.data" because another output "/tmp/mbedtls-20211218-25035-1043085/mbedtls-mbedtls-3.1.0/build/tests/suites/test_suite_psa_crypto_storage_format.v0.data" does not exist., which doesn't seem to be a problem here but is not something I'd expect to see. Those two files are generated by the same command, so either both should exist or neither, unless it's a race condition while the generation script is running.
Can you please try one of the following workarounds?

Do a non-parallel build. We've had bugs with parallel builds before due to accidentally missing dependencies (and also apparently due to a bug in older cmake versions, but that shouldn't be an issue with Homebrew).
Pass -DGEN_FILES=OFF to cmake. This should use the generated files from the archive. (And I think it should be the default in the release, both with make and with cmake.)

Please try if #5429 can fix this problem.

Pass -DGEN_FILES=OFF to cmake. This should use the generated files from the archive. (And I think it should be the default in the release, both with make and with cmake.)

This fixed our build issue and we have merged the PR. Thanks @gilles-peskine-arm!
Closing the issue for now.

I'm reopening this issue because there's a workaround for releases (and it won't need to be applied explicitly once we fix #5432), but that workaround doesn't apply to the development branch. We need to fix that (https://github.com/ARMmbed/mbedtls/pull/5429).

I see, make sense.