hide live photo download

to hide live photo on download modal when not present

Code wise it looks sane, but I don't have pictures to test it with.

There are sample photos here:https://github.com/LycheeOrg/Lychee/issues/378 i
test with them. And you can test with any photo to see that download modal
has "Video part of live-photo" option in every photo that are not
live-photo.
Benoît Viguier<EMAIL_ADDRESS>3 Tem 2020 Cum, 17:06 tarihinde
şunu yazdı:

Code wise it looks sane, but I don't have pictures to test it with.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LycheeOrg/Lychee-front/pull/204#issuecomment-653564888,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJE6E626DRCDDOKGZ4ZXAODRZXQXVANCNFSM4OKOY5BA
.


API always returns empty errors

No matter what mjml was passed - errors will be empty all the time
try render via API "" without any closing tag - no any errors in response.

Without any details it's hard to help your here.
Please open a proper issue with sample requests at least.
Non-parsable content might not output a JSON in the output and report a HTTP error code instead.

Ok. Can you provide any mjml that should return errors? I will try to reproduce on my environment.


The word "activated" in NoClip in danish is spelled wrong / mistypo

txAdmin/FXServer versions:
You can see that at the bottom of the txAdmin page, or in the terminal as soon as you start fxserver.
Describe the bug
The Danish language for the noclip activated is spelled wrong.
It should be spelled: NoClip aktiveret please see the Screenshot.
To Reproduce
Steps to reproduce the behavior:
Just have the danish language and then join the server at do /tx and activate noclip.
Screenshots

Thank you.
I suppose the line "God Mode aktiveretr" is also wrong?
I'll change it and if that was correct please let me know and I can revert it.

Thank you. I suppose the line "God Mode aktiveretr" is also wrong? I'll change it and if that was correct please let me know and I can revert it.

You are correct that was also spelled wrong :) thanks again.

This change has been made but will only be available when the next txAdmin update (v7) is released in a month or so.

This change has been made but will only be available when the next txAdmin update (v7) is released in a month or so.

Ahh okey perfect


Update docker api deprecated types

We are using some deprecated types of the docker API package that we need to update to the suggested types. Follow reference links for more details.
Changes:

Replace these types:

ContainerCreateCreatedBody -> CreateResponse (reference)
ContainerWaitOKBody -> WaitResponse (reference)

Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[x] Update dependencies

Testing
Requires testing

[x] No

Codecov Report
Patch coverage: 50.00% and no project coverage change

Comparison is base (90c0e23) 90.83% compared to head (2831d21) 90.83%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #258   +/-   ##
========================================
  Coverage    90.83%   90.83%
========================================
  Files           71       71
  Lines         4112     4112
========================================
  Hits          3735     3735
  Misses         282      282
  Partials        95       95

Flag
Coverage Δ

unittests
90.83% <50.00%> (ø)

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

Impacted Files
Coverage Δ

cli/cli.go
56.03% <0.00%> (ø)

internal/pkg/services/services.go
100.00% <ø> (ø)

internal/pkg/services/wait.go
100.00% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Race conditions / dependencies between CFE core apps

The "core" applications have significant dependencies between them that need to be more pro-actively satisfied.  There are some race conditions during the startup phase that can pose some serious problems if things are not executed in the right order.
The summary of what happened is below, but here is a list of the basic problems:

Start up code should synchronize at least the "core" applications and ensure that each one has reached it's respective "RunLoop" before starting the next one, regardless of what the platform config sets the priority to (likely depends on #71).
EVS_IsFiltered should range check before doing the table lookups based on passed-in values
CFE SB and EVS (at least) populate different values into their own "AppID" global variable before initialization.  SB does nothing (0 by default, which is in fact a valid AppID for a different app) but EVS initializes this to 0xFFFFFFFFF, which has very ill-effects if actually used for something, and nothing really checks for this.

For those interested, here are the details of the specific sequence of events discovered when debugging application startup on the Microblaze processor used by the EVA team at GRC:

As dictated by the table within "cfe_es_objtab.c", the CFE core applications are started (Tasks Created) in the order of EVS, SB, ES, TIME, BL.
In the default/example platform configuration, these have respective priorities of 61(EVS), 64(SB), 68(ES), 60(TIME), and 70(TBL).
TIME task will run it's TaskMain first even though it is 4th in the start sequence.
As part of this init sequence, it calls CFE_SB_CreatePipe() which in turn calls CFE_EVS_SendEventWithAppID() in several places (for errors as well as an unconditional "debug event" at the end).  The AppId supplied is "CFE_SB.AppId" which is uninitialized since SB has not executed yet.  In this case the value used is actually 0.
In turn this eventually calls EVS_NotRegistered() (since CFE_EVS_TaskInit has not run) and then EVS_SendEvent() as part of that.
EVS_SendEvent() calls EVS_IsFiltered() with the contents of CFE_EVS_GlobalData.EVS_AppId, which is also uninitialized but set to "0xFFFFFFFF", not zero like CFE_SB.AppId.
This appID value is not range-checked by EVS_IsFiltered and ultimately segfaults and crashes CFE core.

Trac comment by jphickey on 2015-05-07 10:41:17:
Working on a fix for this.  There are two possible approaches to solving this, some CCB discussion might be good to decide which is best:

Move more of the critical initialization bits into the "EarlyInit" calls.  Some of this initialization work might be in the task itself due to the fact that it is dependent on the AppId (e.g. CFE_ES_GetAppID() needs to work).  However, for the core applications, they are always present and always get the same AppIDs, these could be changed to a fixed enumeration for Early Init purposes so it would not depend on CFE_ES_GetAppId.

Keep the initialization as part of the task itself, but use something like the existing startup sync semaphore (after fixing it) to wait for each CORE task to reach the run loop before starting the next task.  This would only need to be done for the core tasks -- the other tasks already call WaitForStartupSync if they depend on another task already being initialized for part of their initialization.

Trac comment by jphickey on 2015-05-08 16:58:43:
Related PSP ticket: [https://babelfish.arc.nasa.gov/trac/cfs_psp/ticket/23]
I created this ticket in the PSP trac to capture the issue brought up by Chris Monaco during today's CCB meeting while discussing this ticket.  In this case the PSP is possibly calling into the Timer 1Hz function before CFE TIME has been initialized.
This issue can be tracked/resolved separately. If any changes are necessary for this one, they will likely be done in the PSP.

Trac comment by jphickey on 2015-05-08 13:39:51:
DEPENDENCY NOTE: Trac #71 implements the first part of this fix, which is to synchronize the start up of the core applications.

Trac comment by jphickey on 2015-05-11 09:54:07:
Pushed commit [changeset:0c00114] for remainder of this fix
This commit makes two additional minor modifications to EVS:

During EVS_SendEvent, confirm that the global "EVS_AppID" value is within range before calling EVS_IsFiltered.  Otherwise do nothing.
Set the EVS_AppID value as the last thing in CFE_EVS_TaskInit, so it can be assured that once the AppID is valid that all other initialization is also done.

Associated branch name is "trac-42-rangecheck-evs-appid"

Trac comment by sstrege on 2015-05-15 16:47:47:
Approve

Trac comment by acudmore on 2015-05-18 15:40:11:
Approve

Trac comment by sduran on 2015-05-19 13:46:30:
approve

Trac comment by jwilmot on 2015-05-19 10:15:17:
Approve

Trac comment by glimes on 2015-05-19 13:47:46:
approve

Trac comment by glimes on 2015-05-19 13:52:53:
Note that you can use ![cfs_psp:23] to link to [cfs_psp:23] -- yay InterTrac ;)

Trac comment by glimes on 2015-05-22 10:51:16:
Commit [changeset:e08eada] has this fix, backported to master.

Trac comment by wmoleski on 2015-06-16 13:37:12:
cFE <IP_ADDRESS> was tested using an MCP750 running vxworks 6.4. All build verification tests normally executed on a cFE release were successfully executed. An additional test was performed in an attempt to verify that the race conditions identified did not appear. The UART (minicom) output for the test is attached to trac #81.

Trac comment by sstrege on 2016-08-11 15:39:18:
Merged to development on  Wed May 20 09:39:24 2015 -0400


qv2ray: Add version 2.1.2

Yet another v2ray client. Qv2ray is a Qt based cross-platform GUI client using v2ray core.
More detail: https://github.com/Qv2ray/Qv2ray

@Ash258

What is difference between gRPC and libqvb?

There will be only gRPC version in the future releases.

This cannot work with default configuration

I will think about to specify the default v2ray core path installed by scoop
I have removed the auto update section, because the developer will change release filename

There will be only gRPC version in the future releases.

What does it mean??

Source?
From the discussion with developers, they will only provide gRPC build for Windows from the next release.

Submitted an issue to Qv2ray asking for removing Qt version number from release files (linked above👆), which if accepted, should make autoupdate work even Qt version updates.

Nowhere is specified -or-later license

https://github.com/Qv2ray/Qv2ray#licences

Noone care if it is cross platform or in what it is written

This is a brief description from their wiki, which best describes what it is. There are many "Graphical frontend for v2ray", someone may care about consistent experience across different platforms, not "noone".

Source of vcredist requirement??

v2.1.1 Release notes.

BREAKING: Windows 版本现在使用 MSVC 编译
Windows 用户如果启动失败的话，请尝试安装 Qv2ray 安装包内的 MSVC 运行库

TL:

BREAKING: Windows version is now compiled with MSVC
Should Windows users fail to launch the program, please try installing MSVC runtime in Qv2ray's installation package.

* Do not use unneeded custom symlinks when you can edit one file ...

What's the disadvantage to go with symlinks?

* Source of vcredist requirement??

The developer has bundled a vcredist2019 installer in their package. The vcredist2019 runtime library is a real dependency not suggestion.

Hello guys, I wonder if this is ready to go.

@DuckSoft Will be updated automatically after merge. Or i will update it before merging next week.

@DuckSoft Will be updated automatically after merge. Or i will update it before merging next week.

An automatic update shall be fine. Thanks for your efforts btw!


Update Byte Array Interop Breaking Change

Summary

We backed out part of this breaking change via https://github.com/dotnet/aspnetcore/pull/33768

Does line 10 need to be updated at all?

Nope, I think that's fine as-is.


Build with bazel

The targets.mk seems to be generated from BUILD files. Now that bazel is open source, can you guys just open source the bazel BUILD files too? Thanks!

Indeed this was set up to look like a BUILD file (but wasn't actually generated from a real BUILD file). I don't have time to do this, but would love to see it happen if someone volunteers.


fix: wraps DropdownList with styled

PR checklist

[X] I have followed the "Committing and publishing" guidelines;
[X] I have added unit tests to cover my changes;
[X] I updated the documentation and examples accordingly;

Changes description
Fixes missing styled component in DropdownList
Affected packages

@quid/react-dropdown

Please may you add a test to make sure the component can be styled?

Please remember to tag test commits with test:


[NOT FOR MERGE] Adjust prompt to use view command

Give a summary of what the PR does, explaining any non-trivial design decisions
This is the prompt adjustment I used, with the purpose that the LLM uses more the view tool for directories, which is part of its file_editor tool, than other options (ls -R /workspace or ls -la /workspace).
This is used for the initial exploration of the repository a lot.
I think it would be interesting to eval this after Ryan's fix is merged in main.
Edited to add: in the event stream of CodeAct 2.2 swe-bench run, the agent uses ls -R /workspace a lot, and ls -la sometimes.

To run this PR locally, use the following command:
docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:12be7fc-nikolaik   --name openhands-app-12be7fc   docker.all-hands.dev/all-hands-ai/openhands:12be7fc

There we go:
THOUGHT: I'll help you implement the necessary changes to fix the issue with `django.utils.http.parse_http_date`. Let's follow the steps you outlined.

1. First, let's explore the repository structure:
CODE:
print(file_editor(**{'command': 'view', 'path': '/workspace/django__django__3.1'}))

OBSERVATION
[Agent Controller default] **IPythonRunCellObservation**
Here's the files and directories up to 2 levels deep in /workspace/django__django__3.1, excluding hidden items:
/workspace/django__django__3.1
/workspace/django__django__3.1/AUTHORS
/workspace/django__django__3.1/CONTRIBUTING.rst
/workspace/django__django__3.1/FUNDING.yml
/workspace/django__django__3.1/Gruntfile.js
/workspace/django__django__3.1/INSTALL
/workspace/django__django__3.1/LICENSE
/workspace/django__django__3.1/LICENSE.python
...

I ran 13 instances that are unresolved (0/13) in the CodeAct 2.2 results. They're all on django, and all part of the intersection of Lite with Verified.
CodeAct2.2: 0/13
Branch: 1/13.
Too little to matter, but FWIW! @xingyaoww

I'm thinking about whether we should make this change in the prompt, as encouraging the agent to use view over ls -R can save us on tokens, hence allow the agent to execute more steps before reaching context limit 🤔

Evaluation results: ## Summary

submitted instances: 30
empty patch instances: 12
resolved instances: 8
unresolved instances: 22
error instances: 0

Haven't automated this part yet so here ya go:
evaluation.zip


AVT 3 - Content Switcher Component: State and correct role are not announced by VoiceOver

Environment
macOS Mojave version 10.14.2
Chrome version 72.0.3626.96 (Official Build) (64-bit)
Detailed Description
VO announces does not announce the correct role for each button and does not announce when it is selected.
Expected Result
VO should announce each button as a tab using role="tab" and indicate when it is selected using aria-selected="true".
The Right and Left Arrow keys should move focus forward and backward through the tabs.
See ARIA Authoring Practices 1.1 - Tabs  for additional ARIA requirements.
It is also recommended that the example include the tabpanel to ensure the ARIA roles and states, as well as focus are implemented correctly.

This issue should remain open until it is fixed and retested.


Misleading exception message due to incorrectly named handler methods on Save

When authoring an aggregate root with event application if the handler methods (by convention named Handle) are incorrectly named (eg. Consume) then no events will be recorded for persistence.
In the case that the handler methods are incorrectly named Apply then the aggregate root will appear to function correctly up until it is persisted. This is due to the base method invocation which triggers the handler methods also being named Apply.
There are really two issues here:

It should not be possible to instantiate an aggregate root with event application without any events stored for persistence (the error message the we get).
It should be more apparent to the author that the handler method is incorrect.

These issues may manifest in the following ways:

If Apply is mis-used then there will be no events (error on save)
If Consume is used then there will be events but not -application- of events (error on initial Apply)

Thinking about it, for the Consume case the fact that the Apply mehod is being called should be sufficient reason to believe that event application is the desired approach.

I think Serkan might look at this.


Auto-generate Rust program structures / client from IDL

Hi!
Some projects do only provide an IDL or js client. Rust users have to manually create struct's based on the IDL in order to interact with the program. It would be very neat to generate such clients automatically from an IDL json file.
Thanks

https://github.com/saber-hq/anchor-gen

https://github.com/igneous-labs/solores

for offchain clients based on anchor-gen: https://github.com/jordy25519/drift-account-indexer/tree/main/src/idl-gen

Added in https://github.com/coral-xyz/anchor/pull/2857

Are there any examples of how to use this #2857 @acheroncrypto ? It's really not documented at all and I can't find a simple standalone example of how to parse some instruction data in minimal project anywhere?


Avoid repeated searching for positioning ATX in 1:N

Motivation
It avoids duplicated work to look up a positioning ATX and verify its chain.
Description
Looking up a positioning ATX is serialized with a mutex and the result is cached (keyed by the publish epoch that the pos ATX is about to be used for). Only one pos ATX is cached.
Test Plan
Added tests to verify caching.
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[ ] Update documentation as needed
[ ] Update changelog as needed

bors merge


Readmes

Coverage remained the same at 100.0% when pulling e63bf89d293f91d9ff7889b982bb902f3bb63e6e on rstegg:readmes into 68de04589e6d783e917aa954dfb3133abaa9a608 on evilsoft:master.

Coverage remained the same at 100.0% when pulling e63bf89d293f91d9ff7889b982bb902f3bb63e6e on rstegg:readmes into 68de04589e6d783e917aa954dfb3133abaa9a608 on evilsoft:master.

Coverage remained the same at 100.0% when pulling d3faf10ef220cfae607caf9a690597892f6b6a91 on rstegg:readmes into 68de04589e6d783e917aa954dfb3133abaa9a608 on evilsoft:master.

Coverage remained the same at 100.0% when pulling 082184ebd2ea5b7956c5947ebc6ab06f9ec200c8 on rstegg:readmes into 68de04589e6d783e917aa954dfb3133abaa9a608 on evilsoft:master.

Coverage remained the same at 100.0% when pulling 082184ebd2ea5b7956c5947ebc6ab06f9ec200c8 on rstegg:readmes into 68de04589e6d783e917aa954dfb3133abaa9a608 on evilsoft:master.

Coverage remained the same at 100.0% when pulling 4eb69861b545d1811eab07c39048ce86ee693926 on rstegg:readmes into 68de04589e6d783e917aa954dfb3133abaa9a608 on evilsoft:master.

@rstegg This PR was merged!
So if you rebase off master (do not forget to rm -rf node_modules && npm i to get the latest eslint) you the READMEs in src/ will have their code blocks linted.


Set up auto-assignment bot

PRs often get stuck for a while waiting for someone to review. To help mitigate this, we introduced a list of reviewers who can be directly assigned PRs to review. The idea is once someone is made responsible for reviewing a PR, it's more likely to be done quickly. The reviewer has the option of reviewing the PR or passing it on to someone else on the list.
The next problem is actually assigning PRs to those people to review, for a while we have tried to do this manually but it seems to get forgotten about.
Our proposed solution to this, is to insert these names into an Airtable database and write a bot that automatically assigns PRs to someone on that list.

It seems we haven’t acted upon this despite it feeling like a good idea in 2021, so I’ll close this now. If we still want to have that kind of bot I’d recommend bringing this to core team discussions again.


[typo] their -> they

Fix a small typo in the Ecto main module documentation

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


Rendering is layered on top of itself

Not working with my 1.5 series k8s cluster. Installed/running using the instructions from the README. Using Chrome 56.
Empty page flash:

When it does render (briefly):

@xrl did you figure the issue out?
I'm experiencing the same problem

No, I didn't figure it out. I just abandoned the work. Good luck!


Implement UniqueId type

UniqueId is a property type that is currently present only in place files. It has distinct formats for both rbxl and rbxlx.
Sample property chunk for rbxl format, in hexadecimal format:
| 00 00 00 00 08 00 00 00  55 6e 69 71 75 65 49 64 |........UniqueId|
| 1f 00 01 b7 86 02 4e 93  e1 e1 1e 4c 04 09 cf 82 |......N....L....|
| 88                                               |.|

Sample of equivalent value for rbxlx:
<UniqueId name="UniqueId">708f260204e7c144024e93e10001b786</UniqueId>

The first bytes describe the property as usual:
00 00 00 00              Class ID (0)
08 00 00 00              Length of property name (8)
55 6e 69 71 75 65 49 64  Property name ("UniqueId")
1f                       Property type

The type ID for UniqueId is 0x1F.
As usual, the remaining bytes represent an array of values. For this type, the array is interlaced by 16 bytes.
The sample contains one value:
00 01 b7 86 02 4e 93 e1 e1 1e 4c 04 09 cf 82 88

For proper conversion between rbxlx, this must be interpreted as a struct:
{
	Index:  u32
	Time:   u32
	Random: i64
}

The Index and Time fields are interpreted as unsigned 32-bit integers, encoded in big-endian. The Random field is similar to the encoding of the int64 type: a signed 64-bit integer in big-endian and with rotated encoding.
In the rbxlx format, this value is encoded by converting each field to bytes in big-endian, then encoding to hexadecimal. In relation to the binary format, the fields are written in reverse order:
    Index    Time     Random
bin 0001b786 024e93e1 e11e4c0409cf8288

    Random           Time     Index
xml 708f260204e7c144 024e93e1 0001b786

Decoding is simply applying this process in reverse.
Note: The Random field looks different between formats because rbxl uses rotated encoding:
    Random (hex)     Random (binary)
bin e11e4c0409cf8288<PHONE_NUMBER>011110010011000000010000001001110011111000001010001000
xml 708f260204e7c144<PHONE_NUMBER>001111001001100000001000000100111001111100000101000100

The following archive contains rbxl and rbxlx files with instances that have equivalent UniqueId values. These can be used to verify the correctness of implementations:
Baseplate.zip

After a brief discussion with a Roblox engineer on this, it's been made clear that these are meant to be just GUIDs for Instances (it will be used to make packages usable, among other things). I'm not sure if it's meaningful to separate them internally beyond splitting the number to correct the differences between file formats.
I'd love some additional feedback on this, but my current plan is to instead implement this as a simple wrapper for u128 and have functions to convert from the xml format to the binary format and vice versa. I don't see a reason why someone would want to access the individual fields that make up the number (the time field is unfortunately not a timestamp).

I think it's a lot easier to reason about as a struct. Had the binary format of UIDs matched the XML format, then the type could easily have been represented as a u128 or constant-length sequence of bytes. But because of the seemingly complicated conversion between binary and XML, it's pretty clear that Roblox uses a struct internally. We all want the UID to be an opaque hunk, but that isn't how it played out, and it's too late to change things. Any attempts to hide what it actually is now will only make things more difficult down the line.
Some extra bits:

Time is a timestamp! It just has an epoch set at 2021-01-01 00:00:00.
The Random field is almost certainly a 64-bit signed integer, due to how its encoded in the binary format. The sign bit is always 0, suggesting that random 63-bit positive integers generated.
This comment has more information, particularly how UIDs are generated.

Wow, I really don't like that epoch even though it makes perfect sense to use it. I'd not sure what I'd assumed the time field was if not a real timestamp (in hindsight I think I've just been willfully ignoring its significance in hopes of ignoring the struct entirely), but confirming that it's a real one does change things somewhat because now we have to treat UniqueId as a struct.
The hope was to obscure the implementation details on Roblox's end since it seemed superfluous to the whole thing but with a timestamp embedded it really doesn't make sense to ignore, it especially when the time comes for us to make our own. I suppose complexity is the price we pay for correctness in the end...

This was closed by #271!


"Ticket: Adding Dynamic Theme to the App"

Request to add a dynamic theme to the app.

Summarized feedback from<EMAIL_ADDRESS>
Request to add a dynamic theme to the app.

Related to #601


Use quickpick with search and toggles to toggle the setting value per language

The current Modified Elsewhere hover doesn't make it easy to quickly identify what value per language is set to, is it possible to instead use a quickpick with toggles per language showing the value for the setting. In this example, global formatOnSave is enabled, with some languages having default or user-set overrides to false. The dialog then shows the languages with the overrides and you can toggle from the quickpick or search for a language.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I just realized your idea only applies to boolean settings for language overrides only.
Is that intentional, or does the idea also extend to other types of settings?

My suggestion was mostly concerned with boolean settings as you've described. I haven't considered or experimented with multiple value settings which will not be as clear to modify in a quickpick.


python310Packages.pyunifiprotect: 4.6.1 -> 4.6.2

Diff: https://github.com/briis/pyunifiprotect/compare/refs/tags/v4.6.1...v4.6.2
Changelog: https://github.com/AngellusMortis/pyunifiprotect/releases/tag/v4.6.2
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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

1 package failed to build:

python311Packages.pyunifiprotect

3 packages built:

home-assistant-component-tests.unifiprotect
python310Packages.pyunifiprotect
unifi-protect-backup

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

1 package failed to build:

python311Packages.pyunifiprotect

3 packages built:

home-assistant-component-tests.unifiprotect
python310Packages.pyunifiprotect
unifi-protect-backup


Fix padded code (text) in mdast

Strip one space from the beginning and end of InlineCode if (a) the value starts and ends with a space and (b) is not all spaces.
From CommonMark spec section 6.1:

If the resulting string both begins and ends with a space character, but does not consist entirely of space characters, a single space character is removed from the front and back.

Resolves #122

whether this should apply to all inline code text, or just `

How do you mean? Isn’t all “inline code” / “code (text)” with `?

whether I should adjust the position fields (and if so, which? all of them, or just the *_offsets?) to account for the stripping the spaces

I don’t think that’s needed. Positional info represents the whole, which includes the backticks too. So the spaces have no effect on it.

apologies if this PR is not the appropriate way to do that!

This is great! Thank you!

whether this should apply to all inline code text, or just `

How do you mean? Isn’t all “inline code” / “code (text)” with `?

I think this the raw_text also covers $$, but I'm not 100% — I haven't tested it out yet. And I'm also not sure whether $$ also requires stripping the space.

whether I should adjust the position fields (and if so, which? all of them, or just the *_offsets?) to account for the stripping the spaces

I don’t think that’s needed. Positional info represents the whole, which includes the backticks too. So the spaces have no effect on it.

Awesome, thanks! That makes it easy.

apologies if this PR is not the appropriate way to do that!

This is great! Thank you!

Glad to hear it! 😁
Unfortunately, I won't be able to get to it until later tonight (US east coast), but I'm guessing there's no urgency on this from your end. :-)

$, as in math, has no standard. I intentionally here use the exact same working of ` for $. So :+1: to same workings for both.
No urgency from me! I really appreciate you helping!

Ah, if they intentionally work the same, then perhaps this PR is ready to go? I'll go ahead and mark it as "ready for review" and subject it to full critique! :-)

Thanks Yuval! Released!!

Awesome, thanks so much!


Support for React v0.14

Updates for React v0.14.
Note that these changes are not backwards compatible.

Can you update this to work with the final release?

Already implemented in #20. Thanks for contributing though.


Make a Lambda to add users.

sys_user_management

Use SAM
Receive list of names in event
Create users in IAM with these names and random passwords. DO NOT require users to set new passwords.
Attach to them Administrator AWS managed policy
Output a JSON user: pass

Solved in #3

Solved in PR #3


Stub implementation of stale-state hover and codeAction

This adds a stubbed implementation of stale-state textDocument/hover and textDocument/codeAction queries.
Why those two queries? Because it seems that this is the minimal set we need to stub in order to get interesting behavior out of vscode.
Motivation
Would be nice to review the basic design around locking/multithreading separately from logic tweaks.
Test plan
No unit tests for the moment (open to ideas on how to improve that situation!) but everything should be hidden behind the --enable-experimental-lsp-stale-state flag.
For a basic smoke test, I've set up a sandbox project in vscode with --sleep-in-slow-path and --enable-experimental-lsp-stale-state and verified that we get stub answers for hover while a slowpath is running:

[ ] TODO: Test by hand against Stripe's codebase to make sure that the --enable-experimental-lsp-stale-state flag is indeed properly gating this feature.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_LIT9mHdKg3DWsD
→ https://go/builds/bui_LIT9Z09YUDpbXX


Getting error when running gatsby build!

Running gatsby build throws following error:
ERROR #11328

A page component must export a React component for it to be valid. Please make sure this file exports a React component:

undefined

not finished createPagesStatefully - 0.079s

Could be due to one of the plugins versions, tried solving locally but couldn't get it!
gatsby develop gives below errors in browser:

Not enough data to understand what went wrong. Can you create a repository where this error is reproduced?
I can assume that this is due to the fact that there is no content on the site, you need at least some content, for this there is content/links/frontmatter-placeholder in each starter.

I started with gatsby-starter-chronoblog,
gatsby new chronoblog-starter-site https://github.com/Chronoblog/gatsby-starter-chronoblog
cd chronoblog-starter-site/
gatsby build

the forked repository, where I encountered this error is as below:
https://github.com/itzsrv/gatsby-starter-chronoblog.git

Thanks for the info!

Wanted to take the hacker starter for a spin, but unfortunately I got the same error. This is what the console says btw.:
The above error occurred in the <Context.Provider> component:
    in MDXProvider (at wrap-root-element.js:65)
    in MDXScopeProvider (at wrap-root-element.js:64)
    in Unknown
    in Unknown (at wrap-root-element.js:72)
    in StaticQueryStore (at root.js:138)
    in _default (at app.js:94)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries. index.js:2177
    __stack_frame_overlay_proxy_console__ index.js:2177
    React 22
        logCapturedError
        logError
        callback
        callCallback
        commitUpdateQueue
        commitLifeCycles
        commitLayoutEffects
        callCallback
        invokeGuardedCallbackDev
        invokeGuardedCallback
        commitRootImpl
        unstable_runWithPriority
        runWithPriority$1
        commitRoot
        finishSyncRender
        performSyncWorkOnRoot
        scheduleUpdateOnFiber
        updateContainer
        legacyRenderSubtreeIntoContainer
        unbatchedUpdates
        legacyRenderSubtreeIntoContainer
        render
    js app.js:94

And this is my gatsby info:
❯ gatsby info

  System:
    OS: macOS 10.15.5 # i tried on a debian system too, but to no avail
    CPU: # not relevant
    Shell: # not relevant
  Binaries:
    Node: 12.18.0 - ~/.nodenv/versions/12.18.0/bin/node
    npm: 6.14.4 - ~/.nodenv/versions/12.18.0/bin/npm
  Languages:
    Python: 2.7.16 - /Users/stefan.prietl/.pyenv/shims/python
  Browsers:
    Chrome: 83.0.4103.97
    Firefox: 77.0.1
    Safari: 13.1.1
  npmPackages:
    gatsby: ^2.18.7 => 2.23.3
    gatsby-plugin-google-analytics: ^2.1.23 => 2.3.4
    gatsby-plugin-manifest: ^2.2.27 => 2.4.11
    gatsby-plugin-sitemap: ^2.2.21 => 2.4.5
    gatsby-theme-chronoblog: ^0.22.0 => 0.22.0
  npmGlobalPackages:
    gatsby-cli: 2.12.45

The version of mdx-js/reactI get:
│ │ │ ├──<EMAIL_ADDRESS>deduped
│ │ │ │ └──<EMAIL_ADDRESS>deduped
│ │ │ ├──<EMAIL_ADDRESS>deduped
│ │ │ │ ├──<EMAIL_ADDRESS>deduped
│ ├──<EMAIL_ADDRESS>
So I guess it has something to do with the @mdx-js/react module which got recently updated to 1.6.5, which was after the last deployment of your chronoblogs (around 2020-04-27 I think?).
I already played around trying to get an earlier mdx-js version, but I was not able to do this (I am new to this so the dependency management of npm is a bit of a blackbox to me right now).
HTH somehow.

It may also be worth noting that the starters seem to work when checking out gatsby-theme-chronoblog and running for example ´yarn start:hacker`.

@ederst @itzsrv
I published a new version of Chronoblog - v0.23.0 (https://www.npmjs.com/package/gatsby-theme-chronoblog).
It would be great if you tested the new version. The problems listed here, I hope, have been resolved, but I'm not 100% sure.

hi @Ganevru,
Its working great for me! Thanks a lot!

@Ganevru can confirm that it's working now wit npm too; tested with git clone;  npm i, and with gatsby new
thanks!

@itzsrv @ederst thank you, guys 🤝


LORE of head

Hello, when I want to change the color of the head there is no change all the time the same, I restart the server but still nothing changes
why?

Hey, thanks for reporting an issue.  I apologize for the late response.
Are you sure that you are saving the file?  If so, what version is your server running and are you getting any errors in your console?

Closed due to inactivity.  Feel free to re-open if you are still experiencing issues.


Phaser renders incorrect color

Version

Phaser Version: 3.16.2

Operating system: Ubuntu 16.04.1

Browser: Chrome Version 72.0.3626.109 (Official Build) (64-bit)

Description

If you check the test code, you will notice that background color of the canvas doesn't obey the color defined in config object, we have #2d2d2d in config object but what gets rendered is #313131.
Example Test Code

https://codepen.io/anon/pen/wNRjvr
Additional Information

I doubt if this is only about background color or the whole game like images and etc, also I've tested using both Chrome and Firefox.

I'm getting the correct color on my end

For me, it is always wrong.

After chatting on the discord server and it works for everything but them, Antriel hopped in and said it seemed like an HDR issue he's had before, unsure how to fix. conversation started here

It seems this is an old Chrome issue. (maybe happened cause of new update again?)
It effects both CSS and canvas.
http://www.html5gamedevs.com/topic/25294-color-problem-with-chrome-osx-desktop-browser/
https://bugs.chromium.org/p/chromium/issues/detail?id=637801&desc=2


DID Key Identifiers for NIST Curves are Wrong

See https://github.com/w3c-ccg/did-method-key/commit/f72be388f1c10e76f7785bb02ea2cd7828b47359

Fixed in https://github.com/transmute-industries/did-key.js/pull/97


Exception when using sensor manager to record video and output generated by sensor manager are multiple images in place of video file

Camera sensor throwing exception every time, when starting sensor manager for VideoRequest.
Also output generated by sensor manager for video recording contain multiple images. But expected output is a single video file in place of images.
Exception logs:
FATAL EXCEPTION: main
Process: com.abc.xyz, PID: 783
java.io.FileNotFoundException: /data/user/0/com.abc.xyz/files/tbapp/recordings_2024-09-06T10:56:44.406777Z/1_1725620204772.video/mp4v-es: open failed: ENOENT (No such file or directory)
at libcore.io.IoBridge.open(IoBridge.java:574)
at java.io.FileOutputStream.<init>(FileOutputStream.java:236)
at java.io.FileOutputStream.<init>(FileOutputStream.java:186)
at com.google.android.sensing.capture.sensors.CameraSensor$saveImage$2.invokeSuspend(CameraSensor.kt:285)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:111)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:99)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:811)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:715)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:702)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@44ef58f, Dispatchers.Main.immediate]
Caused by: android.system.ErrnoException: open failed: ENOENT (No such file or directory)

Initialisation code:
sensorManager.start(
                    InternalSensorType.CAMERA,
                    CameraCaptureRequest.VideoRequest(
                        externalIdentifier = "Patient1",
                        outputFolder = "outputFolderName",
                        outputTitle = "Video",
                        outputFormat = "video/mp4v-es",
                        bufferCapacity = Int.MAX_VALUE
                    )
                )

Thanks for pointing this out.
The current CameraSensor implementation does not support VideoRequests right now so I'll add code to properly handle this exception. However this CameraSensor implementation is just a sample implementation and we encourage you to set up your own Sensor interface's implementation for whichever Sensor you want to work with. More details in the Sensor interface kdoc.
You can write your own CameraSensor implementation and register it with the Sensing library using api registerSensorFactory.
Then use generic apis of SensorManager to capture using your sensor implementation.


fix: default file/uploads location for Silverstripe

The Issue
ddev import-files on Silverstripe does not have a default import location set.
How This PR Solves The Issue
Adds a default UploadDirs method to Silverstripe, so the default (public/assets) is properly detected.
Manual Testing Instructions
Run an import of assets.
Automated Testing Overview
To be completed
Related Issue Link(s)
Depends on

#5234

Release/Deployment Notes

Seems so far the Colima tests just crashed. No big deal though, it's a 3-liner.
I'll make it fully working, and hopefully also, while at it, a few tiny fixes?
@rfay I noticed that the ddev list command works but since "Silverstripe" is longer than the currently allocated 9 characters, it gets a break.
Do you want a separate PR for that (Changing the limit from 9 to 13), or are you okay with putting it all in one PR?
I don't mind either way, but multiple PRs for just Silverstripe minor fixes feels a tad overkill?

Rebased and the requisite PR is now pulled, so please check it over and take a look at the silverstripe files tarball. Thanks!

I'll try to make some time free for it! But no promises... Life is surely getting in the way at the moment :)

I've added a very basic test that checks if the upload dir is at least not empty.
I'm a tad short on time right now, but I'm trying to get the tests to match an actual expectation instead of only "not empty"

Please edit the OP to add a complete description of how to test import-files, thanks!
Note that colima on amd64 has been broken for the last couple of weeks, so don't worry about that.

Mildly unsure why the no-bind-mounts=false test keeps failing... It succeeds locally

Not sure which test you're referring to, a link would be good.

It's this one, the Colima test indeed :) :
https://github.com/ddev/ddev/actions/runs/6019812935/job/16330172143?pr=5241

Rebased. I hope things have calmed down now @Firesphere and that the new life is great! Let me know if you want to go forward with this one.

I'll close this about Oct 1 if it doesn't get attention, thanks @Firesphere . After that it can be reopened when you are ready to return to it.

Apologies, both work and personal life are very stressful and busy at the moment.
I'll get back to tidying this up probably not before mid October

Update, got some spare time.
I think this is what I completely intended to achieve.
Set the upload dir, and test for the known project types that have an upload dir, that it is what is expected from default settings.

Thanks. I know what it's like to have too much else to do. Wasn't trying to pressure you, just try to keep things moving so it doesn't get too messy around here.

Sorry, this got lost in the older PRs and now I'm less available next few weeks. Will try to get it reviewed.

Hm, okay, I did not expect that :D . I'll have a look. Cheers!

It was a tad dumb of me, the upload dir is relative to the public dir, it was indeed creating public/public/assets constantly.
A "simple" matter of not including public in the upload dir should solve it.

Thanks for the followup!

As far as I'm concerned/aware, it's good to go. It has all the tests and solves the original problem mentioned in #5234

@stasadev can take a look tomorrow and in it goes!


x/playground: Deploy Playground Automatically

We want to reduce toil and ensure that we’re running the latest Playground version for play.golang.org. The current process involves manual steps, which can be error-prone, forgotten, or interruptive. After this work, changes to Playground or a new Go release should be available on play.golang.org shortly after they’re made.
In either scenario below, we need to ensure that we're always deploying playground built on the latest stable release of Go. It's possible to get this information from maintner.
We have a number of other services that could benefit from CI/CD, but we should focus on solving this issue for playground for the moment, and see what we learn.
Deploying the latest Playground:
It’s possible to configure this flow entirely within Cloud Console and a cloudbuild.yaml file.

Grant App Engine access to Cloud Build
Create a cloudbuild.yaml file in the playground repo

Add step for gcloud app deploy
Configure build timeout to avoid currently documented issue

Create a Cloud Build trigger, and link to github.com/golang/playground

The user authorizing this trigger needs to be in the golang github org, and an admin of the playground repo on github.

Convert GO_VERSION in the playground Dockerfile to an ARG with a default value

Our docker build step must populate the latest GO_VERSION when it builds.
There are other options available for pushing directly from gerrit, but would involve additional manual configuration, as well as figuring out where to store it and document it.
Deploying Playground with the latest Go release
This update flow requires determining the latest stable Go release after it happens, then building deploying Playground with the new release. This workflow more involved, as Cloud Build doesn't  provide a way to add the business logic that we want out of the box: mainly that we want to trigger based on the latest stable tagged release of a different repository, and not accidentally downgrade (say, if 1.11.x is tagged after 1.12.x)
If either of these workflows feels too difficult to configure, or feels fragile, we should try a gerrit based flow instead.
cloudbuild.yaml reference: https://cloud.google.com/cloud-build/docs/build-config
App Engine automation quickstart: https://cloud.google.com/source-repositories/docs/quickstart-triggering-builds-with-source-repositories
Cloud Build API for manual (or programmatic) triggers: https://cloud.google.com/cloud-build/docs/running-builds/start-build-manually

After some experimentation, a GitHub Cloud Build Trigger seems to support our requirements.
When a new version of Go is released, we push tags, then build and push releases (see x/build: cmd/releasebot/main.go). We can configure a trigger on Cloud Build for new tags being pushed to GitHub for the golang/go repository. The trigger can whitelist to tags matching a regex (for example /^go[0-9](\.[0-9]+)+$/). Cloud Build can then run arbitrary steps to build and release Playground.
The Cloud Build steps would look something like:

Clone the latest master branch of Playground
Determine the latest, stable release of Go
Build Playground docker image
Deploy Playground to AppEngine

It is possible that this trigger would fire before the Go binaries have been released. The Playground Dockerfile may need to be updated to build Go from source instead of fetching the release. As Playground already modifies and rebuilds Go, this should be a minor increase in complexity.
Determining the latest, stable release of Go could be done a number of ways. One option is to use git ls-remote --tags, filtering and sorting by version, such as by sort -Vr. Another option is to create a new command in x/build/cmd that either lists releases from Maintner, or acts as a Maintner API CLI.
Gerrit Cloud Build triggers do not support the same level of filtering as the GitHub triggers. Filtering is important, as deploying Playground on every single push to Go would be excessive.
Another option entirely would be to run a daemon to poll for new releases of Go, triggering releases manually. I would prefer to use Could Build if we can to reduce maintenance overhead.

Another thought: we could build and release Playground daily as well, using whatever the latest release of Go is. This would avoid the issue of triggers entirely. Building and deploying daily (on working weekdays) is a good continuous delivery practice, so it is a solid fallback option.

@dmitshur Initial testing for tag-based triggers works great.
If we're using a tag based trigger to start the Cloud Build, and rely on maintner to tell us what the latest release is, what is the delay between the tag being pushed to github and being able to query it from maintner?

A tag pushed to Gerrit should be available in maintner within a few seconds or so.

Great, so we'll be able to move forward with a command to fetch the latest go tag from maintner, and use that to build the playground in a GCB triggered build.

A new Playground is now deployed automatically, built with the latest supported Go release, by Google Cloud Build Triggers under two scenarios: a new tag matching goX.Y.Z is pushed to github.com/golang/go, or a new commit is pushed to github.com/golang/playground's master branch.

This appears to have stopped working
https://play.golang.org/p/Ztyu2FJaajl
1.13.7 is run at the moment

@amnonbc Thanks for reporting. Issue #37632 is tracking the work needed to resolve this.


Doc Feedback: Too much left and right Margin

Location : https://apim.docs.wso2.com/en/latest/Learn/DesignAPI/CreateAPIProduct/api-product-overview/

@erangatl , could you please comment on the Git issue from a UX point of view.

This is a fixed layout and margins are set according to the device with.
Primary content area has an optimum line length (100 cpl) for better readability.

For those who prefers longer lines, we have given the capability of collapsing the TOC and expand the content.


Improve jvm codegen to generate classes parallely

Description:
current jvm codegen generate classes sequentially, can improve that to process them parallelly

This is implemented, however there is no significant perf improvement, so we need to investigate more why parallelly processing doesn't improve performance.


Support uploading sourcemaps when bundling from stdin

Currently, when bundling with esbuild and the entrypoint is from stdin, no sourcemaps are uploaded to Sentry. Digging into the source, it happens because debug IDs (needed to resolve source maps) are only injected for actual module entrypoints (not stdin entrypoints).
We can see this with the following esbuild config (taken from my SST project where I noticed the issue) that SST generates to deploy my functions.
// worker.ts
export default {
  fetch(request: Request) {
    return new Response(null, { status: 204 })
  }
}

import { build } from "esbuild";
import { sentryEsbuildPlugin } from "@sentry/esbuild-plugin";

build({
	stdin: {
		contents: `
        import handler from "./worker.ts"
        import { wrapCloudflareHandler } from "sst"
        export default wrapCloudflareHandler(handler)
        `,
		loader: "ts",
		resolveDir: "./",
	},
	plugins: [
		sentryEsbuildPlugin({
			org: "OMITTED",
			project: "OMITTED",
			authToken: "OMITTED",
			debug: true,
		}),
	],
	sourcemap: true,
	bundle: true,
	metafile: true,
	outfile: "./dist/index.mjs",
	external: ["node:process"],
}).then(() => process.exit(0))

Running a build produces the following logs:
[sentry-esbuild-plugin] Debug: Could not determine debug ID from bundle. This can happen if you did not clean your output folder before installing the Sentry plugin. File will not be source mapped: /Users/ernest/Downloads/esbuild-sentry/dist/index.mjs
> Found 0 files
> Adding source map references
> Nothing to upload
[sentry-esbuild-plugin] Info: Successfully uploaded source maps to Sentry

As you can see, the build script SST uses wraps my handler with some functions to define stuff it needs at runtime. I could get around this issue by:

Bundling the function before passing it to SST but I'd rather not have to maintain my own build steps when SST supports this (with customisation) already.
Using the uploadLegacySourcemaps options to manually upload the sourcemaps, but I had difficulty with actually getting Sentry to map errors to the source code

However, I feel like this is a valid use-case, even outside of SST, hence why I'm opening this PR (and not an issue in SST). I don't feel too strongly about having this built in and will happily accept an explanation on why this is not a good idea.
Now, the check for modules required by stdin may not be correct, but I think this is along the lines of what's needed to support the feature.

Hi! Thanks for the PR! :) I'd be generally happy to add this as soon as we add some tests. Would you be up for adding them? If not I can also get to it at some point but it might take a while.

No problem, but I can't seem to find much in the way of (esbuild) tests apart from packages/e2e-tests/utils/create-cjs-bundles.ts which doesn't seem to be testing multiple use cases?

I've tried again uploading these to Sentry - it works but the actual source mapping doesn't point to my source files. I'm now not so sure this is a valid use case?


Allow timestamp parameter in ProcessorTopologyTestDriver.process

All current implementations process records using the same timestamp. This makes it difficult to test operations that require time windows, like KStream-KStream joins.
This change would allow tests to simulate records created at different times, thus making it possible to test operations like the above mentioned joins.

@sebigavril thanks for the patch! I've left some minor comments.

@bbejeck have a look at the refactor.
I have also change the default timestamp in CustomTimestampExtractor as it was causing tests that were using 0 as timestamp to fail. Anyway, I think 0 is more appropriate for a default than 1000.

@sebigavril just one minor additional comment, but otherwise LGTM.
\cc @dguy @guozhangwang @mjsax  for second review.

@bbejeck - done!

LGTM! Merged to trunk.


[release-v1.12] Test Keda Kafka Source Scaling (#3491)

Cherry pick of https://github.com/knative-extensions/eventing-kafka-broker/pull/3491

/retest

/retest

/close
We are not using 1.12_old, hence closing.


OIDC auth and token enpoints to support enironments like servers section does

Servers section allows for multiple urls's however oidc only allows a single oidc server

The security section assumes I have one IAM I want to be able to have one
per environment
servers:

url: https://{environment}.api.server.test/v1
variables:
environment:
default: api.sit # SIT server
enum:
- api.dev # Development server
- api.sit # SIT server
- api.uat # UAT server
- api.ppe # PPE server
url: https://api.server.test/v1 # Production server

So something like this
securitySchemes:
mutualTLS:
description: Mutual TLS
type: mutualTLS
scheme: mutual
oauthAuthCode:
  description: Auth Code
  type: oauth2
  flows:
    authorizationCode:
      authorizationUrl: 'https://

{environment}.secure.server.test/authorization'
tokenUrl: 'https://{environment}.secure.server.test/token'
variables:
environment:
default: api.sit # SIT server
enum:
- dev # Development server
- sit # SIT server
- uat # UAT server
- ppe # PPE server
scopes:
admin: Admin scope
user: User scope
media: Media scope
On Fri, 24 May 2024 at 19:25, Henry Andrews @.***>
wrote:

@mcrobbj https://github.com/mcrobbj – It's not entirely clear what you
want to have happen here, could you please elaborate? (most of the
maintainers are not security experts, so you'll need to explain your use
case and any relevant standards of which we should be aware)
—
Reply to this email directly, view it on GitHub
https://github.com/OAI/OpenAPI-Specification/issues/3101#issuecomment-2130128494,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACQL2EGUFFIP6XMTLYAUNGLZD6AY5AVCNFSM6AAAAAATBTTVNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZQGEZDQNBZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


fix: update samples snippet to write to BYTES instead of ARRAY

Update samples snippet InsertingDataTypes.java

Change datatype for school column from REPEATED BYTES to BYTES
Convert byte array to base64 string when writing into BYTES column (school)

Fixes #2875 ☕

LGTM, manually tested and after the change a correct base64 encoded string is being uploaded to BQ


[WEB Improvement] : Add Dynamic GitHub Stars Section ⭐

Quick Description 🛠
Currently all the Github Starts that shown in The Website is Static, make it Dynamic Github Stars

Select the open-source program you're contributing to
Other
Adherence to Code of Conduct

[X] I adhere to the CONTRIBUTING GUIDELINES of this project.

Hey @Puskar-Roy👋! Thanks for raising this issue and demonstrating your interest in contributing to our project!🚀
We value your engagement and eagerly anticipate your contributions. Should you wish to get involved, please use the /assignme command to self-assign the issue.
This issue provides an excellent opportunity for us to enhance our project, and we're excited to have you join us! Please take a moment to review our CONTRIBUTING GUIDELINES before getting started.
If you have any questions or need assistance, feel free to reach out to us on LinkedIn.❤

Hey! puskar can i work on this issue ?

@South-IN Sure!

Hey puskar  i needed some help where should i write the issue number in the PR?

@South-IN So You Can Add Issue Number In Title Of The PR,
You can follow this format and Replace Issue Number and <issue_no> with Your Issue Number.

ok thank you and where can i find the "rules of when pr will get merged"?

@South-IN push the code in dev branch, it's just a recommendation that if you want to contribute in some repo at first read the contributing.md.

@Puskar-Roy  i am sorry but i read the contributing.md and couldn't find any mention of merging code to the dev branch that's why I asked where can I find the "rules of when pr will be merged".

@South-IN are no issues 😃

Hello @Puskar-Roy! We'd like to inform you that the issue has been resolved and is now closed. We appreciate your understanding and look forward to your continued involvement with our repository!🤗
If you encounter any further issues, please don't hesitate to reach out to us on LinkedIn. Thank you for your support!❣
Happy coding!✨ We hope to see you again soon!❣


Unable to use the package in react when installing using npm

Hi,
I tried installing the package in my react project using npm.
I used ES6 import. When I tried to console the imageCompression object, the output is displayed as a function.
Code is
"import imageCompression from 'browser-image-compression';
console.log(imageCompression)"
output is
"/static/media/browser-image-compression.9d2e921a.mjs"
the error I am getting is
"TypeError: __WEBPACK_IMPORTED_MODULE_1_browser_image_compression___default(...) is not a function"

@vinayedadan There may be some issues in your webpack setup.
To demonstrate the functionality of the package with React, I have created a demo on CodeSandbox, you may have a look at it here:
https://codesandbox.io/s/dq1j2

closed because of inactivity

@vinayedadan There may be some issues in your webpack setup.
To demonstrate the functionality of the package with React, I have created a demo on CodeSandbox, you may have a look at it here:
https://codesandbox.io/s/dq1j2

I have seen this link of yours but in my system still getting "TypeError: __WEBPACK_IMPORTED_MODULE_1_browser_image_compression___default(...) is not a function" this issue


clarify location of client_id and client_secret in token request semantics of ITI-71

This issue applies to IUA Rev 2.1 Trial Implementation, published March 19. 2021
CLIENT CREDENTIALS GRANT TYPE:
—> ITI-71 Message Semantics for Client Credentials Grant type token request (https://profiles.ihe.net/ITI/IUA/index.html#3714121-client-credential-grant-type) specifies that the client_id and client_secret goes in the HTTP header of the POST to request the token
—> And Figure <IP_ADDRESS>.2.1-2 also indicates that client_id and client_secret go in the HTTP header.
CODE AUTHORIZATION GRANT TYPE:
—>ITI-71 Message Semantics for the Code Authorization Grant type request (https://profiles.ihe.net/ITI/IUA/index.html#3714122-authorization-code-grant-type)  indicates that the client_id goes in the HTTP request body of the HTTP POST to request the token.
—> the text prior to Figure <IP_ADDRESS>.2.2-3 seems to be a copy/paste error from client_credentials above, indicating that both client_secret and client_id belong in the header… (client_secret is not specified for code authorization).   The example in the figure shows client_id in the header and not in the body.
QUESTION:  Is it intentional that client_id goes in the HTTP header for the client credentials grant type, but it goes in the body for the code authorization grant type?

It looks to me that the question compares two very different things:
In the authorization code grant flow retrieving the token is a two step process. First the authorization request is performed to get the authorization code sending the client_id in the http header. In the second step the authorization code is used to retrieve the access token sending the client_id with the body of the POST request.
The client credential flow only uses one step with one http transaction sending the client_id in the http header, just like the first step in the authorization code flow.

Yes, I understand that the client-credential flow is one step and the code-authorization is two step.
The screen shot below is ITI-71 text describing step 2 of the authorization code step.  I believe the text underlined in red contradicts what is marked in green.   Am I misunderstanding????

Dear Lynn
sorry I misunderstood the question.
Yes you are right. In the second http call of the authorization code flow the client authentication via the client_id and client_secret is not required anymore in the latest version of the OAuth specification, Section 4.1.
Now it reads:
When making the request, the client authenticates with the authorization server if it can.
Thus client authentication using the client_id and client_secret in the http authorization header is optional.
Formally the example is still correct for those using this way for client authorization but may be misleading.
Kind regards
Martin

On 28 Apr 2021, at 16:21, lynnfel @.***> wrote:
Yes, I understand that the client-credential flow is one step and the code-authorization is two step.
The screen shot below is ITI-71 text describing step 2 of the authorization code step. I believe the text underlined in red contradicts what is marked in green. Am I misunderstanding????
https://user-images.githubusercontent.com/47753616/116419487-b8dfae80-a802-11eb-9279-7650d1147bf6.jpg
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/IHE/ITI.IUA/issues/77#issuecomment-828496079, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEC6MVB4MN2262PUACW33DTLAKVVANCNFSM424BF4NQ.

This change is tracked as CP-ITI-1256:  https://docs.google.com/spreadsheets/d/1gdr_Y8xZBvbb326J4z67cqprxOexFgtkPj_VlD3rB9E/edit#gid=0


Error

Describe the bug A clear and concise description of what the bug is.
Hello, I did the setup according to the instructions, but I get an error when I start it.
Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Windows 10
node v18.9.0
npm 9.7.1

https://github.com/jooy2/vitepress-sidebar/issues/49#issuecomment-1532310510


Consider getting rid of RegProxy

It was added to work around some perceived shortcomings in svd2rust (see https://github.com/rust-embedded/svd2rust/issues/213), and while I still think it would be worthwhile to make the proposed improvements in svd2rust, RegProxy causes a lot of complexity in this crate, and its utility is dubious at best.

Some more thoughts: https://github.com/lpc-rs/lpc8xx-hal/pull/210#issuecomment-587406534

I think in it's current incarnation (ignoring the safety issues), RegProxy is of limited use. In syscon.rs it makes what's happening more clear, whilst in #210 it makes the code more complex & confusing.
Getting rid of  RegProxy & replacing it with the unsafe equivalent, when it's used for shared registers (in ctimer, #210 and parts of dma) makes sense, but for the syscon it's seems fine if we just declare the constructor as unsafe.

Sounds like a good compromise actually. I've added a task to my list to do just that (at the current pace, I think it'll be a few weeks).
It would be great to make RegProxy completely redundant by improving svd2rust, but there's so much to do... maybe some day.


normalizedRequestAttrs stopped working for dasherized paths

Hi there.
There's a bug with normalizedRequestAttrs in 0.4.10 version of mirage that I believe was caused by this commit: https://github.com/samselikoff/ember-cli-mirage/commit/4606c11ab8480698a6ed42e819b645967e3562f3
Previously having app/models/foo-bar.js defined I could do something like this in my mirage/config.js
export default function () {
  this.patch('foo-bars/:id', function () {
    const attrs = this.normalizedRequestAttrs();
  });
}

Now this doesn't work because of added assertion this.schema.modelFor(modelName) in normalizedRequestAttrs. See https://github.com/samselikoff/ember-cli-mirage/commit/4606c11ab8480698a6ed42e819b645967e3562f3#diff-9ff4e2a84eb4c76ed9a4d8c6d117fda4R48
Also it looks like this assertion is not necessary, because the _getAttrsForRequest function actually uses this.schema.modelClassFor(modelName) which camelizes model name.
So the solution seems to either assert for this.schema.modelClassFor(modelName) instead of this.schema.modelFor(modelName) in BaseRouteHandler, or to modify modelFor method in schema so that it also camelizes its argument to be consistent with modelClassFor.

fyi, I was able to "fix" this by manually specifying the model name in camel-cased, singular form, e.g.
this.normalizedRequestAttrs('fooBar');

I noticed this today too after upgrading. I would have though that the modelName for normalizedRequestAttrs would be expecting a dasherized name like we do when calling server.create, etc.


Try to get Gentoo to provide needed files on the distmirrors

This is

gentoo kernel
gentoo.igz original initrd
image.squashfs
boot.ipxe the iPXE script - once it is well tested for all platforms

This is a discussion with an already existing Bug, probably not to hard to get fix once we have good documentation here on how it could be used. https://bugs.gentoo.org/494300

From chat using https://web.libera.chat/#gentoo-releng

jpds
NiKiZe: [as a user]: I'd like that, debian has the stuff under http://ftp.uk.debian.org/debian/dists/stable/main/installer-amd64/current/images/netboot/debian-installer/amd64/

NiKiZe
jpds yes, the current iso works as it is, so I have not found any reason to make it netboot specific? But I guess this somewhat boils down to maintenance and automation. If anyone could point me in the right direction for where minimal iso is created and copied, then maybe I could provide a patch to move forward?

iamben
look in releng.git repo, tools/catalyst-auto calls catalyst, uploading happens via the arch-specific catalyst-auto-*.conf files
im not sure if it would be best implemented in catalyst-auto, or as a separate build target in catalyst itself

NiKiZe
Thanks! Since the artifacts should already exist from building the iso I'm assuming it's best to reuse that if possible? Could you explain just a little more where I should look for "separate build target in catalyst"?

iamben
https://github.com/gentoo/catalyst/tree/master/targets

Notes for trying to use catalyst
mkdir -p /etc/portage/package.accept_keywords
echo dev-util/catalyst > /etc/portage/package.accept_keywords/catalyst
emerge -uv pixz catalyst genlop reptyr -j16
# python mount needed (maybe)
USE=python emerge -v util-linux

# grep -v ^# /etc/catalyst/catalyst.conf
# remove autoresume
# add preserve_libs
# add keepwork
# remove snapcache - first build fails with this enabled ?
options="bindist kerncache pkgcache preserve_libs keepwork seedcache"
snapshot_cache="/release/tmp/snapshots"
storedir="/release/buildroot/amd64-dev"
source_matching="loose"
# add log
port_logdir="/var/tmp/catalyst/tmp"
var_tmpfs_portage=16

# cat /etc/catalyst/catalystrc
export MAKEOPTS="-j8"
export EMERGE_DEFAULT_OPTS="--jobs 20 --load-average 9"

cd
git clone https://github.com/gentoo/releng.git
cd releng

# TODO parse /etc/catalyst/catalyst.conf to get below paths

mkdir -p /release/buildroot/amd64-dev/builds/default/
mkdir -p /release/buildroot/amd64-dev/builds/hardened/
mkdir -p /release/buildroot/amd64-dev/builds/musl
mkdir -p /release/buildroot/amd64-dev/builds/musl-hardened
mkdir -p /release/tmp/snapshots/
pushd /release/buildroot/amd64-dev/builds/default/
FILE=$(wget -q http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64/ -O - | grep -o -E 'stage3-amd64-20\w*\.tar\.(bz2|xz)' | uniq)
wget http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64/$FILE
ln -s $FILE stage3-amd64-openrc-latest.tar.xz
popd

# check expected times:
genlop -t gcc

mkdir -p /release/buildroot/amd64-dev/tmp/
rm -rf /release/buildroot/amd64-dev/tmp/*; mount none -t tmpfs /release/buildroot/amd64-dev/tmp/ -o size=16G,nr_inodes=1M
sh tools/catalyst-auto -c tools/catalyst-auto-amd64-demeter.conf -v -v -X
umount /release/buildroot/amd64-dev/tmp/

Building with snapcache enabled gives this:
*** Running command: catalyst -a -c /etc/catalyst/catalyst.conf -f /tmp/catalyst-auto.20210723T062037Z.zsSPDX/specs/stage1-openrc.spec
23 Jul 2021 08:20:44 CEST: NOTICE  : Loading configuration file: /etc/catalyst/catalyst.conf
23 Jul 2021 08:20:44 CEST: NOTICE  : conf_values[options] = {'preserve_libs', 'pkgcache', 'clear-autoresume', 'keepwork', 'seedcache', 'snapcache', 'bindist', 'kerncache'}
23 Jul 2021 08:20:44 CEST: NOTICE  : Processing spec file: /tmp/catalyst-auto.20210723T062037Z.zsSPDX/specs/stage1-openrc.spec
23 Jul 2021 08:20:44 CEST: NOTICE  : Using target: stage1
23 Jul 2021 08:20:44 CEST: NOTICE  : Source file specification matching setting is: loose
23 Jul 2021 08:20:44 CEST: NOTICE  : Accepted source file extensions search order: ['tar.xz', 'tpxz', 'xz', 'tar.bz2', 'bz2', 'tbz2', 'squashfs', 'sfs', 'tar.gz', 'gz', 'tar']
23 Jul 2021 08:20:44 CEST: NOTICE  : Source path set to /release/buildroot/amd64-dev/builds/default/stage3-amd64-openrc-latest.tar.xz
23 Jul 2021 08:20:44 CEST: NOTICE  : stage1 stage path is /release/buildroot/amd64-dev/tmp/default/stage1-amd64-openrc-20210723T062037Z/tmp/stage1root
23 Jul 2021 08:20:44 CEST: NOTICE  : --- Running action sequence: unpack
23 Jul 2021 08:20:44 CEST: NOTICE  : Referenced SEEDCACHE does not appear to be a directory, trying to untar...
23 Jul 2021 08:20:44 CEST: NOTICE  : Clearing the chroot path ...
23 Jul 2021 08:20:44 CEST: NOTICE  : Emptying directory: /release/buildroot/amd64-dev/tmp/default/stage1-amd64-openrc-20210723T062037Z
23 Jul 2021 08:20:44 CEST: NOTICE  : Starting auto from /release/buildroot/amd64-dev/builds/default/stage3-amd64-openrc-latest.tar.xz
23 Jul 2021 08:20:44 CEST: NOTICE  : to /release/buildroot/amd64-dev/tmp/default/stage1-amd64-openrc-20210723T062037Z (this may take some     time) ..
23 Jul 2021 08:20:47 CEST: NOTICE  : --- Running action sequence: unpack_snapshot
23 Jul 2021 08:20:47 CEST: NOTICE  : Unpacking portage tree (this can take a long time) ...
tar: /release/tmp/snapshots/20210723T062037Z: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
23 Jul 2021 08:20:47 CEST: ERROR   : Error unpacking snapshot using mode lbzip2
23 Jul 2021 08:20:47 CEST: ERROR   : Exception running action sequence unpack_snapshot
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/catalyst/base/stagebase.py", line 1499, in _run
    getattr(self, x)()
  File "/usr/lib/python3.9/site-packages/catalyst/base/stagebase.py", line 891, in unpack_snapshot
    with open(snapshot_cache_hash_path, 'w') as myf:
FileNotFoundError: [Errno 2] No such file or directory: '/release/tmp/snapshots/20210723T062037Z/catalyst-hash'
23 Jul 2021 08:20:47 CEST: NOTICE  : Cleaning up... Running unbind()

bootstrap stage2 fails, it was ok first time, but even after clearing all binpkgs still getting this.
Copying stage2-chroot.sh to /tmp
copying stage2-chroot.sh to /release/buildroot/amd64-dev/tmp/default/stage2-amd64-openrc-20210724T051742Z/tmp
copying chroot-functions.sh to /release/buildroot/amd64-dev/tmp/default/stage2-amd64-openrc-20210724T051742Z/tmp
Ensure the file has the executable bit set
Running stage2-chroot.sh in chroot:
    chroot /release/buildroot/amd64-dev/tmp/default/stage2-amd64-openrc-20210724T051742Z /tmp/stage2-chroot.sh
>>> Regenerating /etc/ld.so.cache...

Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2020 Gentoo Authors; Distributed under the GPLv2
-------------------------------------------------------------------------------
  [[ (0/3) Locating packages ]]
 * Using baselayout : >=sys-apps/baselayout-2
 * Using portage    : sys-apps/portage
 * Using os-headers : >=sys-kernel/linux-headers-5.10
 * Using binutils   : sys-devel/binutils
 * Using gcc        : sys-devel/gcc
 * Using gettext    : sys-devel/gettext
 * Using libc       : sys-libs/glibc:2.2
 * Using texinfo    : sys-apps/texinfo
 * Using zlib       : sys-libs/zlib
 * Using ncurses    : sys-libs/ncurses
-------------------------------------------------------------------------------
  [[ (1/3) Configuring environment ]]
-------------------------------------------------------------------------------
  [[ (2/3) Updating portage ]]
>>> Running pre-merge checks for sys-apps/portage-3.0.20-r6
 * Checking for suitable kernel configuration options...
 [ ok ]
>>> Emerging binary (1 of 1) sys-apps/portage-3.0.20-r6::gentoo
>>> Installing (1 of 1) sys-apps/portage-3.0.20-r6::gentoo
-------------------------------------------------------------------------------
  [[ (3/3) Emerging packages ]]
[ebuild   R   ] sys-apps/baselayout-2.7
[ebuild   R   ] sys-libs/zlib-1.2.11-r4
[ebuild   R   ] sys-kernel/linux-headers-5.10
[ebuild   R   ] sys-devel/gettext-0.21-r1
[ebuild   R   ] sys-devel/binutils-2.35.2
[ebuild   R   ] sys-devel/gcc-10.3.0-r2
[ebuild   R   ] sys-libs/glibc-2.33-r1
[ebuild  N    ] virtual/perl-IO-1.460.0
[ebuild  N    ] dev-perl/Unicode-EastAsianWidth-1.330.0-r1
[ebuild  N    ] dev-perl/Text-Unidecode-1.300.0
[ebuild  N    ] dev-perl/Params-Util-1.70.0
[ebuild  N    ] dev-perl/Class-Inspector-1.360.0
[ebuild  N    ] dev-perl/File-ShareDir-Install-0.130.0
[ebuild  N    ] dev-perl/Exporter-Tiny-1.2.2
[ebuild  N    ] dev-perl/List-MoreUtils-0.428.0
[ebuild  N    ] dev-perl/File-ShareDir-1.116.0
[ebuild  N    ] dev-perl/libintl-perl-1.310.0
[ebuild   R   ] sys-apps/texinfo-6.7

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

sys-devel/gcc:10

  (sys-devel/gcc-10.3.0-r2:10/10::gentoo, ebuild scheduled for merge) USE="(cxx) (multilib) nls nptl (pie) (-ada) -d -debug -doc (-fixed-point) -fortran -go -graphite (-hardened) -jit (-libssp) -lto -objc -objc++ -objc-gc -openmp -pch -pgo -sanitize -ssp -systemtap -test -vanilla -vtv -zstd" ABI_X86="(64)" pulled in by
    sys-devel/gcc (Argument)

  (sys-devel/gcc-10.3.0-r2-1:10/10::gentoo, installed) USE="(cxx) fortran (multilib) nls nptl openmp pch (pie) sanitize ssp (-ada) -d -debug -doc (-fixed-point) -go -graphite (-hardened) -jit (-libssp) -lto -objc -objc++ -objc-gc -pgo -systemtap -test -vanilla -vtv -zstd" ABI_X86="(64)" pulled in by
    >=sys-devel/gcc-4.2:*[openmp] required by (app-crypt/libb2-0.98.1-r2-1:0/0::gentoo, installed) USE="openmp -native-cflags -static-libs" ABI_X86="(64) -32 (-x32)"
                          ^^^^^^
    >=sys-devel/gcc-4.2:*[openmp] required by (app-portage/portage-utils-0.90-1:0/0::gentoo, installed) USE="nls openmp qmanifest qtegrity -static" ABI_X86="(64)"
                          ^^^^^^

It might be possible to solve this slot collision
by applying all of the following changes:
   - sys-devel/gcc-10.3.0-r2 (Change USE: +openmp)

24 Jul 2021 07:22:22 CEST: ERROR   : CatalystError: cmd(['/usr/share/catalyst/targets/stage2/stage2-controller.sh', 'run']) exited 1
ERROR:catalyst:CatalystError: cmd(['/usr/share/catalyst/targets/stage2/stage2-controller.sh', 'run']) exited 1
24 Jul 2021 07:22:22 CEST: ERROR   : CatalystError: Stage build aborting due to error.
ERROR:catalyst:CatalystError: Stage build aborting due to error.
24 Jul 2021 07:22:22 CEST: ERROR   : Exception running action sequence run_local

Testing if using this stage3 works around the openmp issue ...
FILE=$(wget -q http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64/ -O - | grep -o -E 'stage3-amd64-20\w*\.tar\.(bz2|xz)' | uniq)
wget http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64/$FILE
ln -s $FILE stage3-amd64-openrc-latest.tar.xz

catalyst only generates one file?
The cleanest way would be to split installcd-stage2-minimal.spec up into 2 files to get a stage2 and 3

installcd-stage2.spec would build squashfs, kernel, initrd.
installcd-stage3-minimal.spec would need to add bootloaders (current grub, syslinux), and generate iso.
installpxe-stage3-minimal.spec Would just repackage initrd+squashfs and possibly generate config files/scripts, but this still needs to generate multiple outputs?

However this probably makes to much of a disconnect between settings in the stage2 spec files and what would be needed for stage3.
In the end maybe the best, or at least the first solution, would be to simply extract the iso in the upload step instead?

More issues when building livecd stage1
[blocks B     ] <sys-apps/man-pages-5.11-r1 ("<sys-apps/man-pages-5.11-r1" is blocking sys-apps/shadow-4.8.1-r4)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (sys-apps/man-pages-5.11-1:0/0::gentoo, installed) pulled in by
    sys-apps/man-pages required by @system

  (sys-apps/shadow-4.8.1-r4:0/0::gentoo, ebuild scheduled for merge) pulled in by
    sys-apps/shadow required by (net-proxy/dante-1.4.1-r6:0/0::gentoo, ebuild scheduled for merge) USE="pam static-libs tcpd -debug -kerberos (-selinux) -upnp"
    sys-apps/shadow required by (net-misc/openssh-8.6_p1-r2:0/0::gentoo, ebuild scheduled for merge) USE="bindist livecd pam pie scp ssl -X -X509 -audit (-debug) -hpn -kerberos -ldns -libedit -sctp -security-key (-selinux) -static -test -xmss"
    sys-apps/shadow required by @system

Have tried to create PoCs to generate PXE files for minimal livecd (amd64), feedback appreciated https://bugs.gentoo.org/494300#c4
One variant modifies upload step https://github.com/NiKiZe/releng/commit/8408f98
Another variant modifies ISO creation https://github.com/NiKiZe/catalyst/commit/33c9405

robbat2:

mattst88: proj/releng.git scripts/copy_buildsync.sh creates latest-*.txt
plus catalyst-auto in some cases


Scorpio not fully resolving JSON-LD context

{
"@context": "https://industryfusion.github.io/contexts/staging/example/v0.1/context.jsonld",
"id": "urn:cutter:1",
"type": "iffBaseEntities:Machine",
"iffBaseEntities:hasState": [
{
"type": "Property",
"value": {
"@id": "base:state_ON"
}}]
}
Scorpio v3 does not resolve "base:state_ON" but JSON-LD playground does resolve it (according to JSON-LD specification). Q. How about Scorpio v4? If it is not resolving correctly we need to file an issue.

Tested on the upstream development branch and inserted the given object. Afterwards queried it through a GET request:
{
  "id":"urn:cutter:1",
  "type":"https://industryfusion.github.io/contexts/example/v0/base_entities/Machine",
  "https://industryfusion.github.io/contexts/example/v0/base_entities/hasState":{
    "type":"Property",
    "value":{
      "type":"Property",
      "value":{
        "id":"base:state_ON"
      }
    }
  },
  "@context":[
    "https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.7.jsonld"
  ]
}

The context in the @id has not been resolved. It is also the same way in the dataset, only with more metadata:
{
  "@id":"urn:cutter:1",
  "@type":[
    "https://industryfusion.github.io/contexts/example/v0/base_entities/Machine"
  ],
  "https://uri.etsi.org/ngsi-ld/createdAt":[
    {
      "@type":"https://uri.etsi.org/ngsi-ld/DateTime",
      "@value":"2024-04-19T12:49:49.223000Z"
    }
  ],
  "https://uri.etsi.org/ngsi-ld/modifiedAt":[
    {
      "@type":"https://uri.etsi.org/ngsi-ld/DateTime",
      "@value":"2024-04-19T12:49:49.223000Z"
    }
  ],
  "https://industryfusion.github.io/contexts/example/v0/base_entities/hasState":[
    {
      "@type":[
        "https://uri.etsi.org/ngsi-ld/Property"
      ],
      "https://uri.etsi.org/ngsi-ld/hasValue":[
        {
          "@type":[
            "https://uri.etsi.org/ngsi-ld/Property"
          ],
          "https://uri.etsi.org/ngsi-ld/hasValue":[
            {
              "@id":"base:state_ON"
            }
          ],
          "https://uri.etsi.org/ngsi-ld/createdAt":[
            {
              "@type":"https://uri.etsi.org/ngsi-ld/DateTime",
              "@value":"2024-04-19T12:49:49.223000Z"
            }
          ],
          "https://uri.etsi.org/ngsi-ld/modifiedAt":[
            {
              "@type":"https://uri.etsi.org/ngsi-ld/DateTime",
              "@value":"2024-04-19T12:49:49.223000Z"
            }
          ]
        }
      ],
      "https://uri.etsi.org/ngsi-ld/createdAt":[
        {
          "@type":"https://uri.etsi.org/ngsi-ld/DateTime",
          "@value":"2024-04-19T12:49:49.223000Z"
        }
      ],
      "https://uri.etsi.org/ngsi-ld/modifiedAt":[
        {
          "@type":"https://uri.etsi.org/ngsi-ld/DateTime",
          "@value":"2024-04-19T12:49:49.223000Z"
        }
      ]
    }
  ]
}

Fixed with https://github.com/ScorpioBroker/ScorpioBroker/pull/552


Remove ConfigFetchIntervalSec from mixer args

Fix #9320

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kyessenov
If they are not already assigned, you can assign the PR to them by writing /assign @kyessenov in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @supereagle. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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

/cc @kyessenov  @douglas-reid   PTAL

@supereagle: GitHub didn't allow me to request PR reviews from the following users: PTAL.
Note that only istio members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @kyessenov  @douglas-reid   PTAL

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

/ok-to-test

/lgtm
cc: @bianpengyuan (who i think has looked at this recently)

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: douglas-reid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS [douglas-reid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@supereagle: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
37ab535306c7ff2818d721489da330f53210bfa3
link
/test e2e-mixer-no_auth-mcp

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

@supereagle: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
37ab535306c7ff2818d721489da330f53210bfa3
link
/test e2e-mixer-no_auth-mcp

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

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

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
37ab535306c7ff2818d721489da330f53210bfa3
link
/test e2e-mixer-no_auth-mcp

prow/istio-unit-tests.sh
37ab535306c7ff2818d721489da330f53210bfa3
link
/test istio-unit-tests

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

/retest

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
37ab535306c7ff2818d721489da330f53210bfa3
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
37ab535306c7ff2818d721489da330f53210bfa3
link
/test istio-integ-local-tests

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

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

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
37ab535306c7ff2818d721489da330f53210bfa3
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
37ab535306c7ff2818d721489da330f53210bfa3
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
37ab535306c7ff2818d721489da330f53210bfa3
link
/test istio-integ-k8s-tests

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

/test istio-unit-tests

@bianpengyuan  PTAL
/assign @bianpengyuan

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bianpengyuan, douglas-reid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS [douglas-reid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@bianpengyuan  The lint failure is not related with this PR, how can we merge this?

/approve
/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bianpengyuan, douglas-reid, geeknoid, supereagle
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS [douglas-reid,geeknoid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[Bug] on Safari most severe accidents widgets is empty with error text

Describe the bug
The most severe accidents widgets is empty and has error text "Invalid Component widget"
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Scroll down to the most severe accidents widgets (the third one)
See error

Expected behavior
Should appear as it does on chrome.
Screenshots

Environment
Browser: Safari
Environment: Local and Production

https://github.com/hasadna/anyway-newsflash-infographics/pull/451

solved


Landscape . If an existing application is selected, an error is reported if the environment cluster is empty

选择已有应用，环境集群为空时点击提交，报错

resolved


Redshift: fix object types with empty properties getting ignored

If we process following schema with igluctl static generate:
{
  "$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
  "self": {
    "vendor": "com.acme",
    "name": "site_search",
    "format": "jsonschema",
    "version": "1-0-0"
  },
  "description": "Schema for search interaction events with filters as arrays",
  "properties": {
    "filters": {
      "description": "Active site search filters",
      "type": [ "object", "null" ],
      "properties": {},
      "additionalProperties": true
    },
    "sorting": {
      "description": "Active site search sorting",
      "type": [ "object", "null" ],
      "properties": {},
      "additionalProperties": true
    }
  },
  "additionalProperties": false,
  "type": "object"
}

In resulting DDL there will be no filters nor sorting columns. If we remove properties from both fields - they're getting added.

As mentioned in https://github.com/snowplow/iglu-central/issues/1137 the behavior is slightly different if we have additionalProperties with object in it.


Support: Decide on which license you want to use and publish Purple Tools under it

At the moment, the Purple Tools project doesn't use any license. I want it to be as close to public domain as possible.
Most probable candidates at the moment are the MIT license and the BSD 0-clause license.

[WEIGHT: 1.324 U @ 00:33:06]


[#3988] Correctly count acquired channels in FixedChannelPool

Motivation:
We missed to correctly count acquired channels in FixedChannelPool which could produce an assert error.
Modifications:
Only try to decrement acquired count if the channel was really acuired.
Result:
No more assert error possible.

Cherry-picked into 4.0 (467a07aa30088e58e76cea8ea861603c580941c7), 4.1 (bd42987143958b4a5232f76229b914249a51cddf) and master (1a34427a51ba822e104d4aa46f1359dee92e9bb3)


Add CHANGELOG.md entry about @objc(Name) on enums and enum cases

#797 should be merged before this.

We actually had a Radar for this too, rdar://problem/21930334. Can you add that in the same style as the other Radar references?

Sure thing.

PR updated.

Thanks!


fn: add ContextGuard from tapd repo

This adds the ContextGuard struct from the taproot-assets repository that has been in use there for a while.
The context guard allows for easy creation of contexts that depend on a central wait group and quit channel.
A context can either be created with a timeout and quit, meaning it will cancel either on reaching the timeout or when the central quit channel is closed.
Or a context can be created to block and use a timeout, meaning it will not cancel on quit but rather block the shutdown until it is completed (or times out).
The third way is to create a context that just cancels on quit with no timeout.
Usage example: https://github.com/lightninglabs/taproot-assets/blob/7a6ee2ebaf26f0bed1041a4e4ea163f4371853c7/tapfreighter/chain_porter.go#L166

cc @jharveyb

LGTM! Nicer than the bare context


random seed

How to set random seeds for the  gat layer?

It is sufficient to call np.random.seed(seed)so that the initial weights of the layer will always be the same.

I am using tensorflow 1.13.1 and keras 2.2.4. When I was using the GraphAttention layer, I got this error when batch size > 1:

tensorflow.python.framework.errors_impl.InvalidArgumentError: Incompatible shapes: [200,500,200] vs. [200,500,500]
[[{{node graph_attention_1/mul}}]]
[[{{node loss/mul}}]]

(200 is my batch size and 500x500 is the graph shape)
Changing line 121 from
dense = attn_for_self + K.transpose(attn_for_neighs)
into
dense = attn_for_self + K.permute_dimensions(attn_for_neighs, (0, 2, 1))
solved the problem.
Hope it can help someone!


Support for servers other than http-kit?

I am trying to run ripley in a kit-clj project which uses undertow web server through reitit router. I investigated a lot and found out that the implementation of connection handler is coupled with http-kit server and it's websocket support.
Would you confirm that I am on the right path? I feel I need to implement connection handler for other servers. If it makes sense and might get some help, I would like to try a generic connection handler to integrate with various web servers.

Yes, that is correct. It currently only supports http-kit, as that is what I use for everything.
I would gladly take a PR for a generic one and possibly moving server specific parts to separate impl namespaces.
It would be good to not have direct dependency to a particular serve lib in that case, so we don't need all of them.

Good to hear that. How would you look to use https://github.com/taoensso/sente as a dependency here to offload a lot of websocket related details to the library? I am not into too much of websocket details already but with the help of this library I might come up with a generic solution. Just poking for ideas, thanks!

Some implementation could use that, if it helps.
I would rather keep the current simple http-kit implementation as is without any new dependencies.

I'll make do some preliminary work for this by moving the particulars of the connection to protocols. Hopefully that will make it easier to implement other servers.

PR #17  is now merged, with example implementation using pedestal+jetty for WebSockets.
Hopefully this should make it possible to support undertow as well.
PRs welcome for additional server libraries.


WIP

The type of this PR is: TYPE

This PR resolves [MX-]
Description

Test Plan

Screenshots

Fails

:no_entry_sign:
Missing Test Files:

src/lib/Scenes/ArtistSeries/__tests__/ArtistSeriesMoreSeries-tests.tsx

If these files are supposed to not exist, please update your PR body to include "#skip_new_tests".

  Generated by :no_entry_sign: dangerJS


Automate the setup process

Same like ROS1 https://docs.neobotix.de/display/ROSSim/Installation+on+Ubuntu

Updated here: https://docs.neobotix.de/display/R2/Installation+on+Ubuntu


DP Factory Method in Java

Need to make a readme file which should have the
Definition
Explanation in simple terms
Code related explanation.

Can you assign to me

ok


chore: follow-up on MyCollection artworks grid comments

The type of this PR is: Enhancement

Description
This PR solves some small comments I left on https://github.com/artsy/eigen/pull/6151

I renamed the files + removed the unnecessary Flex + Added a test for the migration

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

#nochangelog

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against 2cab8e630a3aa6c3220939ffe23ba2281c7802f7

Sorry, I thought I answered here. Going with the plural name is a personal preference for me, I of course don't mind not going with it for consistency. I will close this PR then. thanks for the follow up PR 🙇♂


Add ALLOW_EMPTY_PASSWORD env var support to Redis image

Since bitnami/redis:3.2.9-r2 image, Redis image accepts the ALLOW_EMPTY_PASSWORD environment variable.
If this env var is set to "yes", Redis could be configured without a password, otherwise, a password must be specified.

closing in favour of #1061


Add shelley package to nightly windows tests

Overview

Github actions steps need to be coded in yaml.
Shelley tests were not in the list of steps.

Ouch... they fail immediately. :(

Hopefully they will work better when cardano-cli.exe is added to the testing bundle.

bors r+


Converter

What kind of change does this PR introduce?
Fixes #47
What is the current behavior?
N/A
What is the new behavior?
final res = await postgrest
      .from('users')
      .select()
      .withConverter<List>((data) => [data])
      .execute();

Thanks for working on this! I've been meaning to do it myself but just hadn't gotten to it. Definitely a useful feature. A couple of thoughts on this current proposal:

The PostrgestResponse body will still show as dynamic even though it's been converted, right? So the user would have to cast it back into whatever type they passed to withConverter
This only handles deserialization and not serialization (since that would require making all the builders generic) so this doesn't do the same thing as firebase's withConverter method

I think this is a useful contribution regardless, just trying to clarify the intended operation. Thanks

@dshukertjr Added type annotations, but I'm not sure the way it's done is correct. I think it may throw cast errors

@bdlukaa At a quick glance, it looked amazing! Will do a through review later!

I still don't get how this converter works? It doesn't do any kind of parsing.
Could you please answer @point-source points?