Add iOS Support

Add conditionals for compile-time iOS Support.
We need float output (not signed integer) for
ofSoundBuffer (not SInt as specified by libaudiodecoder).
ping @kylemcdonald

thanks!
this would be better to add to the original library at https://github.com/asantoni/libaudiodecoder and then merge here, but i will merge it anyway since it doesn't look like iOS is one of their target platforms.

@kylemcdonald thanks... I held back on that because I believe the audio-callback on iOS/OSX indeed expects SInt (like they specified) while oFX\s SoundBuffer takes in floats


Re-write PDFHistory from scratch

Please refer to the individual commit messages.
Supersedes PRs #6272 and #8753; hopefully third time's the charm :-)
Edit: Based on this PR, we should also be able to finally address issue #5927 properly; see WIP patches available here.
Edit2: Rebased to fix merge conflicts, no code changes were made.

/botio-linux preview

/botio-linux preview

/botio unittest

Phew, that was quite a bit of code to review :)

Thank you for having the persistence, despite the size[1], to wade through all of it!!!

As is to be expected with such a large pull request, I have some questions and suggestions for improvement, but most of them are minor.

There's a number of good questions asked and I've tried my best to answer them[2], so please check if you're satisfied with the responses or if you think further clarifications are necessary!
In general, did you find that the existing comments helped, or were they to verbose?

I'll do more testing (initial testing did not yield any unexpected behavior yet)

That's very reassuring to hear, since the whole point of this re-write was to make the code more robust (and of course more maintainable too).
Again, thanks for taking the time to do such a thorough review :-)

[1] I really tried to break this up into somewhat smaller commits, but unfortunately that didn't work as well as I would have liked :-(
[2] It's sometimes quite difficult to know what parts will be confusing or difficult to understand for someone else, considering that you've got a lot of context that the reviewer might not have.

Thank you for the clear responses! In general the comments really helped to understand the code, in particular the edge cases you're addressing, so I'm really glad that it's documented so well! You're right that having the context is key here, so a review is a good way to find out which parts may need further clarification.
The responses look good so far. For some of them I'll need some more time to compare them with the code and to really understand, which I'll do this week including the testing, so we can hopefully merge it at the end of the week if all goes well. Feel free to amend the commits in the meantime if you want; I'll check each comment above in the amended version after that.

/botio-linux preview

/botio unittest

Nice work! Looks really good and it's a massive improvement over the old implementation.

Nice work! Looks really good and it's a massive improvement over the old implementation.

Thanks so much for helping getting this reviewed (with lots of good points/questions) and landed! :-D

Nice work! Looks really good and it's a massive improvement over the old implementation.

Thanks so much for helping with getting this reviewed (with lots of good points/questions) and landed! :-D


Remove flakey test label from mirroring_with_http integration test

#1627

Looks like this exact test is flaking out?

yup, so turns out @meowjesty's pr didn't do it. now I wondering if it has to do with posix_spawn


Change text extractor to use InputStream

Change method arguments to use InputStream vice DataInputStream. This will prevent unnecessary wrapping to DataInputStream in methods that call this Class.

The method argument was changed.


New version: Unity.Unity.6000.Android version 6000.0.9f1

Created by 🥟 Dumplings in workflow run #6342.

Log
Updated: 6000.0.8f1 → 6000.0.9f1
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request
Pull request created: New version: Unity.Unity.6000 version 6000.0.9f1 - https://github.com/microsoft/winget-pkgs/pull/161485
Handling Unity.Unity.6000.Android...
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Depends on https://github.com/microsoft/winget-pkgs/pull/161485

/azp run

/azp run


Cannot do async validation onChange - only onBlur

I have a need to fire async validation onChange of field. I could not find this feature so I posted about it on Stackoverflow and an awesome awesome member shared a deep hack: https://stackoverflow.com/a/47292974/1828637 - Here is a CodeSandbox thanks to this user - https://codesandbox.io/s/8r9qwnnxl
It would be awesome to have this built-in as this is common thing to need (ie: password strength, etc). (with debouce option would be awesome).
Are you submitting a bug report or a feature request?
Feature request
What is the current behavior?
Async validation only fires onBlur
What is the expected behavior?
Async validation should fire on change, and cancel previous check if it was in progress with asyncChangeFields:
@reduxForm({
  form: 'login',
  asyncValidate: validator,
  //asyncBlurFields: ['username','password'],
  asyncChangeFields: ['username','password'], /* add this new option */
})

Sandbox Link
Demo of hack - https://codesandbox.io/s/8r9qwnnxl
What's your environment?
redux-form: 7.1.2
OS: all
Browser: all
Node: all
Other information
none

FWIW there is already a way to do this that is documented here:
https://github.com/erikras/redux-form/blob/79677759d40e6cf9840dfece094cc5eb3d1b9d6e/examples/asyncChangeValidation/src/AsyncValidation.md

Way interesting thanks @kylesuss - does it automatically cancel the fired event if the user is typing fast and the value has changed by the time it triggers the event. (sort of like debouncing)?

No idea! I didn't write it or anything. Just found these related issues when searching for something myself.

Ohh thanks so much for being such a great citizen and informing me! :)

Related to #3521.


User/anusa/user id helper  user process id helper

Description
Describe the purpose of and changes within this Pull Request.
Testing
Do any existing tests cover this change? Are new tests needed?
Documentation
Is there any documentation impact for this change?

Codecov Report

Merging #181 (8c977c5) into master (971f19b) will increase coverage by 1.22%.
The diff coverage is 47.82%.

@@            Coverage Diff             @@
##           master     #181      +/-   ##
==========================================
+ Coverage   84.39%   85.62%   +1.22%
==========================================
  Files         136      123      -13
  Lines       22561    19935    -2626
==========================================
- Hits        19041    17069    -1972
+ Misses       3520     2866     -654

Impacted Files
Coverage Δ

netebpfext/net_ebpf_ext_sock_addr.c
10.57% <10.86%> (-0.66%)
:arrow_down:

libs/execution_context/ebpf_core.c
90.73% <66.66%> (-0.23%)
:arrow_down:

libs/platform/user/kernel_um.cpp
83.70% <70.00%> (+5.84%)
:arrow_up:

libs/platform/user/ebpf_platform_user.cpp
83.02% <74.07%> (-0.89%)
:arrow_down:

libs/api/libbpf_program.cpp
77.13% <100.00%> (+0.21%)
:arrow_up:

libs/ubpf/endian.h
33.33% <0.00%> (-66.67%)
:arrow_down:

netebpfext/net_ebpf_ext_bind.c
18.98% <0.00%> (-4.64%)
:arrow_down:

netebpfext/net_ebpf_ext_hook_provider.c
71.77% <0.00%> (-1.63%)
:arrow_down:

netebpfext/user/ndis_um.cpp
82.05% <0.00%> (-1.63%)
:arrow_down:

... and 29 more

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


deltachat-desktop: 1.46.8 -> 1.48.0

Diff: https://github.com/deltachat/deltachat-desktop/compare/v1.46.8...v1.48.0
Changelog: https://github.com/deltachat/deltachat-desktop/blob/v1.48.0/CHANGELOG.md

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

The Darwin build fails with
  • electron-builder  version=24.13.3 os=23.6.0
  • loaded configuration  file=/private/tmp/nix-build-deltachat-desktop-1.48.0.drv-0/source/packages/target-electron/electron-builder.json5
  • writing effective config  file=dist/builder-effective-config.yaml
  • packaging       platform=darwin arch=arm64 electron=32.2.2 appOutDir=dist/mac-arm64
  • copying Electron  source=/nix/store/6l7mmzg75dfz6hr581b0ygchaiwp6pjw-electron-32.2.2/Applications/Electron.app destination=/private/tmp/nix-build-deltachat-desktop-1.48.0.drv-0/source/packages/target-electron/dist/mac-arm64/Electron.app
  ⨯ open /private/tmp/nix-build-deltachat-desktop-1.48.0.drv-0/source/packages/target-electron/dist/mac-arm64/Electron.app/Contents/Frameworks/Electron Helper (GPU).app/Contents/Info.plist: permission denied
  ⨯<EMAIL_ADDRESS>process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1  failedTask=build stackTrace=Error<EMAIL_ADDRESS>process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1
    at ChildProcess.<anonymous> (/private/tmp/nix-build-deltachat-desktop-1.48.0.drv-0/source/node_modules/.pnpm/builder-util@24.13.1/node_modules/builder-util/src/util.ts:252:14)
    at Object.onceWrapper (node:events:634:26)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:305:5)
/private/tmp/nix-build-deltachat-desktop-1.48.0.drv-0/source/packages/target-electron:
 ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command failed with exit code 1: electron-builder --config ./electron-builder.json5 --dir -c.electronDist=/nix/store/6l7mmzg75dfz6hr581b0ygchaiwp6pjw-electron-32.2.2/Applications -c.electronVersion=32.2.2

Since I don't want to invest too much time into that I'll probably just mark it broken.


doc how to configure etcd for high heartbeat-interval and election-timeout

doc how to configure etcd for high heartbeat-interval and election-timeout, considering we support it now.

The issue doesn't describe clearly. It wants to document how to configure etcd on heartbeat-interval and election-timeout in the case of high RTT. The general guide has been added here: https://github.com/coreos/etcd/commit/7082d3a76598365a9e41988c14e10530b16911ea


upgraded akka version to 2.4.0

Hi, the only problem i couldn't solve for now is SocketIOClusterSpec. Its tests do not pass now. I suppose there could be potential bug with sharding.
Coould you please take a look on my changes and suggest how to fix this problem.


Stable docs 404 in README

https://fluxml.ai/GeometricFlux.jl/stable

Opened: https://github.com/JuliaDocs/Documenter.jl/issues/1674

@yuehhua can we try tagging a new release ?

Let me check current state and then I will tag new release.

Great! Thank you. Just trying to do some cleanup this weekend :)

Thank you so much. I just fire a new release. Let's see if stable doc works.

Fixed! Thank you.


if the port of my oracle and it is not 1521,  it will throw TNS not lisen

if the port of my oracle and it is not 1521,  it will throw TNS not listen.
and I found the reason .... the port param have not transfer into the oracledb ....

This is how oracledb test setup creates connection:
https://github.com/knex/knex/blob/master/test/knexfile.js#L81
DB driver's connection parameters are not handled by knex. Is there something that knex should do differently here?


Fixed: Cannot correctly clone Error instance.

#68

Thank you for your contribution.
I'd like to add you as a contributor to the package.json before publishing to npm. How do you want to be referenced? (See https://docs.npmjs.com/files/package.json#people-fields-author-contributors)

: ) It sounds great!
Just reference like this:
name: Misery Lee      (I‘m a Chinese, this is my English name 😝)
email<EMAIL_ADDRESS>url: https://github.com/miserylee
Thank you!


added app-switcher.svg

Changelog
New

created a 20x20 app-switcher.svg that will look great @ 2x and not awful @ 1x.

existing Asset @2x:

existing asset @1x:

new asset @2x:

new asset@1x:

the scaled dimension of each block was 2.5px. 2 px is too small, but 4 is too big. the new asset the blocks are 3px, but that means centered will be anti aliased in some dimensions, with the center square (5) the worst.
this is probably as good as you are going to get and certainly an improvement over every edge anti aliased everywhere at every resolution
cc @conradennis


add support for unix domain sockets

with my "anysocket" crate
Implements #172

I would personally be against this type of change, as it strongly looks like a feature creep to me.
 They're important for hosting via reverse proxies

Hi. Thank you for the PR.
While I'm myself on the fence on the value of http-servers on unix sockets, it's importance is demonstrated by the fact that two PR:s have been devised for this.
However of the two approaches, considering anysocket seems to be a one-man effort, at 0.1 release, and with no other dependent crates, I'd strongly avoid adding that as a dependency for tiny-http. I'm therefore going to close this PR.
If you still want to contribute, since you're obviously knowledgeable in the field, I'd value your input on https://github.com/tiny-http/tiny-http/pull/187.

Hi. Thank you for the PR.
While I'm myself on the fence on the value of http-servers on unix sockets, it's importance is demonstrated by the fact that two PR:s have been devised for this.
However of the two approaches, considering anysocket seems to be a one-man effort, at 0.1 release, and with no other dependent crates, I'd strongly avoid adding that as a dependency for tiny-http. I'm therefore going to close this PR.
If you still want to contribute, since you're obviously knowledgeable in the field, I'd value your input on https://github.com/tiny-http/tiny-http/pull/187.


Support of feature local-binding-supported

Hello,
Does Netopeer2 supports feature local-binding-supported from ietf-tcp-client for call-home :
leaf local-address {
if-feature "local-binding-supported";
type inet:ip-address;
description
"The local IP address/interface (VRF?) to bind to for when
connecting to the remote peer.  INADDR_ANY ('<IP_ADDRESS>') or
INADDR6_ANY ('0:0:0:0:0:0:0:0' a.k.a. '::') MAY be used to
explicitly indicate the implicit default, that the server
can bind to any IPv4 or IPv6 addresses, respectively.";
}

No, this feature is not supported.


Fixed FA 5 dependencies for the new font awesome picker

My last pull request was only for the font-awesome picker
Your font-awesome is still the old one and caused a lot of font missing
I updated the menu.blade.php without the prefix of fa every time adding item['icon'] because it breaks in FA 5, with the fontawesome picker it includes all of the prefix of the new FA 5 (fas, fab, etc).
I also updated each default font with the correct classes
Checked and test, love your work btw
Thanks!

Great!! Waiting for the release

This should be alright, I have this updated on my local too

Thanks！

Laravel admin using admin lte 2.3. its rely on font awesome 4.  Some font will missing instead you change all font awesome class style

@muhlisabdi Yes, you'r right，some font styles are missing, and all extensions using font-awesome 4 need to be updated, which brings more problems, I will revert this pull request

@z-song reverting is not solution, you should not depend on old stuff, they should just update what they want as they want, here's nothing was missed, just renamed some icos and separated to another packs.

True.. I think we're just missing a bit here and there! We can help fix, such as the toggle icon and some missing stuff


Fix DOM render when cacheAsBitmap

The __cacheBitmap does not have a stage reference, but DOMBitmap.render expects it.

Do you think it would work to set __cacheBitmap.stage = stage immediately before DOMBitmap? That might also fix the issue.
Thanks :smile:

Yes, but keep the if (__worldVisible) {

There we go. DOMBitmap.render checks for both stage != null and __worldVisible, so I think my last commit should work. However, if we need to copy additional properties from the parent object to __cacheBitmap for it to work, let me know. We may be missing a cleanup step for DOM to work perfectly

You'll still need the if (__worldVisible) {, because cacheBitmap's __worldVisible is always true, even if the DisplayObject's is false.


correct one keyword

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
correct one keyword in japanese.
Fixes #(issue)
Type of change
Please delete any options that are not relevant.

Other

Checklist

[x] My code follows the style guidelines of this project
[ ] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[ ] I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
[x] My changes generates no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)
Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

Language files cannot be touched in any pull requests, because they easily create merge conflicts with Weblate.
Please update it on https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/ instead


Network folder name not displayed in folder browser

What version of Music Assistant has the issue?
2.2.9
What version of the Home Assistant Integration have you got installed?
2024.9.1
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
After newly adding a remote file share (and changing it's name in a second step), the folder browser shows some generated names for the remote file shares:

How to reproduce

Create a new filesystem provider for remote shares.
Change its name to something like "Music"
Open the browse tab to browse the file systems

==> wrong name shown
Music Providers
filesystem provider for remote shares.
Player Providers
not relevant for browsing, but I do have Chromecast players
Full log output
music-assistant.log
Additional information
No response
What version of Home Assistant Core are your running
2024.10.3
What type of installation are you running?
Home Assistant Supervised
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

Both folders show the correct content and are indexed correctly as far as I can tell, so it seems just to be an issue with renaming the provider

The browse view has limited functionality. No provider gets renamed there. I’ll ask Marcel if he wants to change this.

This will be fixed in due course

This has been fixed

Confirmed!
Thank you!


Connection pooling support

Hi,
I am sorry about not using your template. It is just question. Do you have any vision on support connections pooling here? Any plans? Any interest to contribution?

Pooling support will likely be handled in the same way as in diesel itself. This means diesel_async wont implement pooling by itself. It will just support existing solutions. I do not have any concrete planes to add this yet, so this will likely happen after the initial release.
One thing I would be interested to know is which external pooling crates are used in the async world and which of them would need explicit support in diesel_async.

One thing I would be interested to know is which external pooling crates are used in the async world and which of them would need explicit support in diesel_async.

I would suggest to check https://crates.io/crates/deadpool

Here https://github.com/weiznich/diesel_async/pull/3 is PoC of connection pooling with https://crates.io/crates/deadpool

Is there any reference material on how to use this?


webterm: intermittent weird text rendering

Sometimes, the webterm displays output where glyphs appear in inconsistent typefaces or styles. I'm not sure if these glyphs are being drawn from different fonts or different code planes of the same font.

Note that the mangled rendering only pertains to some messages. Particularly, the group-store spam renders normally.
This weirdness seems to come and go. I only see this sort of mangling in Urbit webterm.
To Reproduce

Go to webterm
Wait. If you are lucky you may see this strange yet charming phenomenon.

Expected behavior
The webterm renders everything in more or less the same glyph style unless there is a functional reason.
Additional context:

Ship type: planet
Instance type: self-hosted with CLI
OS/browser: Vivaldi on Linux

@arthyn o7 I haven't seen this bug in months, so it may have spontaneously resolved and/or have been unrelated to Urbit.


refactor(api): merge OT3Axis into Axis

Closes RLAB-356
Overview
This is a follow-up PR to #12671 and merges the two different axis types- Axis and OT3Axis into one.
Please don't be daunted by the large diff. Most of it is just changing the names from 'OT3Axis' to 'Axis'. I'm pointing out the critical stuff in changelog below.
Test Plan
Test a couple of protocol flows- including running attach/detach flows and LPC on both OT2 & OT3 to make sure nothing breaks.
Changelog

Made OT3Axis enum the new Axis with aliases for the old OT2 Axis members. So the true members of Axis are now: X, Y, Z_L, Z_R, Z_G, P_L, P_R, Q, G with aliases for OT2 axes of Z, A, B, C.
Any and all changes relating to making the above change and making sure OT2 code still works and the smoothie driver gets the correct 'translated' old Axis.
Most of the changes are just name updates following the merging of the OT3Axis.
The critical changes are:

replacing the .to_mount method on Axis (and OT3Axis) with separate .to_ot2_mount and .to_ot3_mount for each robot type
making sure the OT2's axes still translate to Z, A, B, C for the smoothie driver. For this I created an ot2_axis_to_string util function and replaced all calls to axis.name or str(axis) or any equivalent with that function.
removing almost all AxisType TypeVars that specified the type as combination of Axis & OT3Axis
removing all overloaded functions relating to the two different axis types in motion_utilities.py
changes to models and router for /motors

Review requests

Check if there's any silly auto-refactor changes like Union[OT3Axis, Axis] -> Union[Axis, Axis]
Any changes I've missed or made incorrectly? esp. in motion_utilities.py
Are there any pipette settings & related files that might get affected by this?
Look out for questions in comments
Test if the OT3 and OT2 still work correctly! (working on this)

Risk assessment
High. Changes very low level code for OT2.
Not much detrimental for OT3 other than making sure all scripts are updated correctly (ones in this repo and any testing/ factory scripts in use).

Tested simple transfer protocols on both OT2 & Flex to confirm I didn't break anything. Also tested calibration on OT-2 to make sure the pipette offset endpoints return expected responses.


Fix weak cipher check for OpenSSL 1.1

Fixes #569, though possibly not in the best way, since it doesn't appear any ciphers from OpenSSL 1.1.x would ever match the weak cipher list in the current code.

Whoops! It looks like #570 is an attempt to tackle this far more comprehensively. My bad for not looking earlier.

Thanks!


i can use xaml Designer with c++ winui3?

I hope to use the xaml designer to develop C + + winui3 applications,This will greatly improve efficiency。Do you intend to provide modification function?
Or provide a way to develop winui3 interactively with c# and C + +.

It's been a long discussion about the XAML designer of WinUI, see #5917 , the WinUI team suggest developers choose the hot reload over the XAML designer, however, IMO being unable to customize the built-in control is a great drawback of this approach

Unfortunately not, the team is failing to provide any good tooling for C++ at the same level as C++/CX, and the issue referred by @dylech30th doesn't cover the whole cluckly IDL development part.
For writing C++ Windows applications with a nice development experience you are better off going with Qt or C++ Builder, we are years away until C++/WinRT provides anything similar, and has been promised since C++/CX was deprecated in 2015.
Best of all, with Qt or C++ Builder, you can go on macOS and GNU/Linux as well.

@dylech30th
So is it a better way for Microsoft not to do XAML?If Microsoft has evaluated this and believes that hot overloading is the way of UI development in the future, I am happy to try it.

Well, I think it will be a significant improvement on developers' experience if Microsoft decided to add the XAML designer to cooperate with the hot reload, but at least for now (if you check the last community call on Jan 19) I don't see any tendencies from the Win UI team to do this. They incline to push the hot reload, quote in their own words, "IMO, Hot Reload and Live Visual Tree are fine", but from my point of view I think the hot reload is not enough

in their own words, "IMO, Hot Reload and Live Visual Tree are fine"

@dylech30th Why are you quoting me? I don't work for MS.
Also, as they stated in the community call the WPF & UWP designers were straightforward to implement due to their code living in the OS, whereas that isn't the case for WinUI 3 so it would take a substantial amount of work.
I'm not against a designer, I'm just trying to be pragmatic here as it is obvious the WinUI team is fairly small and they can only get so much done every quarter/year.

They should have thought of it before deprecating C++/CX in 2015.

in their own words, "IMO, Hot Reload and Live Visual Tree are fine"

@dylech30th Why are you quoting me? I don't work for MS.
Also, as they stated in the community call the WPF & UWP designers were straightforward to implement due to their code living in the OS, whereas that isn't the case for WinUI 3 so it would take a substantial amount of work.
I'm not against a designer, I'm just trying to be pragmatic here as it is obvious the WinUI team is fairly small and they can only get so much done every quarter/year.

sry for the misunderstanding, what I want to say is even the designer itself can be replaced by hot reload, we still need alternatives for those functionalities that are not for visual design purpose but still very vital (like the example I stated before, i.e., change the style of the built-in controls)

@llothar Reflection won't be part of ISO C++23, so there you have it, how great Microsoft decided to deal with C++ customers on WinRT.
Then they do all these public announcements how "modern" it is.
Any C++ developer should consider Qt and C++ Builder instead, or the new SixtyFPS startup that has been able to provide in two years the C++ tooling that seems so impossible to do in Redmond.

@pjmlp Yes it's a shame. It seems that Frontend needs to go C# and backend of your code is C++.
Now every toolkit/operating system has it's own GUI language:

Linux Gtk has Vala
Android has Java/Kotlin
macOS/iOS has Swift
Windows has C#

I know that the C++ object model is just not flexible enough for a lot of the GUI convenience and stability (fragile base class problem). But i wish they had picked an easy interoperation language like Objective-C.
Lets see how Slint is doing. But i'm pretty sure that you always have to go with the native toolkit on Android and macOS/iOS to be accepted and support the latest OS features. Cross Platform is not a thing anymore. What we need is finally a modern  Windows Gui Toolkit that is not sandboxing us.

@llothar Agree with the observation, although Qt, C++ Builder prove what is possible, for 25 years now.
So they can come up with excuses about reflection and such, yet the competition has no issues providing the tooling, which for a moment C++/CX almost nailed it.
Even if C# takes the role, that isn't my problem, as I am mainly doing C# on Windows anyway, the problem is that we are forced to adopt C++/WinRT for the features that we need to write bindings for, with tooling reminiscient from OLE 2.0 heyday.
I consider a big lack of respect to paying customers to have deprecated C++/CX without tooling that can match it, same applies to the whole story with WinUI 3.0 and lack of designers.
There isn't any hot reload that will save us to manually write endless XAML boilerplate for behaviors, story boards, styles,...
Whatever, I moved back to the Web, and don't consider advising anyone to adopt WinUI until it can match WPF/WinForms API surface level and designer tooling.

Bring C++/WinRT out of the stone age.
This is what C++/CX could have been, had it not been killed by internal politics, by a team that is now rather having fun with Rust/WinRT,  without any respect for Microsoft paying customers.
C++ Builder, released in 1997, 26 years of commercial use and still going.
Qt, released in1995, 28 years of commercial use and still going.
Not only they provide a proper developer experience with a designer tool, they are cross platform.

Please read and act accordingly!

The link again:
https://developercommunity.visualstudio.com/t/Feature-request-Visual-designer-for-Wi/1608476?q=WinUI+Designer
Oh! And SPREAD THE WORD!
PLEASE!


chore(idempotency): expiration timestamp rounded to the nearest second

Summary
For consistency, we need to align timestamp formats for expiration and in_progress_expiration in idempotency table. To achieve this we have to round off expiration attribute.
Changes

Round off the return value of getExpiryTimestamp function
Fix failing tests because of the rounding off

Issue number:  #2298

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Hi @arnabrahman - thank you for opening this PR!
While I review it and run tests, could I please ask you to leave a comment under the linked issue so that I can assign it to you? (GitHub doesn't let me do it unless you interact with it first).

Regarding the failing integration test, it's possible that the sorting order is being affected because we are rounding off the expiration value.
https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/packages/idempotency/tests/e2e/makeIdempotent.test.ts#L205-L207
For example, previously if this was the items array with expiryAttr:
const items = [
      { id: 1, foo: 'bar' , expiryAttr: 0.6},
      { id: 2, foo: 'baq' , expiryAttr: 0.7},
      { id: 3, foo: 'bar' , expiryAttr: 0.8},
],

After sorting, the items array would remain unchanged.
But now, if the value is rounded off, the items array would look like this for the same value:
const items = [
      { id: 1, foo: 'bar' , expiryAttr: 1},
      { id: 2, foo: 'baq' , expiryAttr: 1},
      { id: 3, foo: 'bar' , expiryAttr: 1,
],

And after sorting, the items array will look like this:
const items = [
      { id: 3, foo: 'bar' , expiryAttr: 1},
      { id: 2, foo: 'baq' , expiryAttr: 1},
      { id: 1, foo: 'bar' , expiryAttr: 1},
],

This is likely why we get id: 3 in the first position. (https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/9195366267/job/25291037147#step:8:538)
However, I'm not entirely certain. To validate this, need the actual values for expiryAttr in e2e.
@dreamorosi

Thank you for looking into it, you are exactly right.
I have tested this on my local branch and it works, I'd suggest to replace the sorting here with this:
const idempotencyRecordsItems = [
  idempotencyRecords.Items?.find(
    (record) =>
      record.customId ===
      `${functionNameCustomConfig}#${payloadHashes[0]}`
  ),
  idempotencyRecords.Items?.find(
    (record) =>
      record.customId ===
      `${functionNameCustomConfig}#${payloadHashes[1]}`
  ),
  idempotencyRecords.Items?.find(
    (record) =>
      record.customId ===
      `${functionNameCustomConfig}#${payloadHashes[2]}`
  ),
];

and the one here with this:
const idempotencyRecordsItems = [
  idempotencyRecords.Items?.find(
    (record) => record.id === `${functionNameDefault}#${payloadHashes[0]}`
  ),
  idempotencyRecords.Items?.find(
    (record) => record.id === `${functionNameDefault}#${payloadHashes[1]}`
  ),
];

Once replaced I'll run the tests again and if green, I think we should be able to merge!

I have updated the tests. You can try it now, @dreamorosi

Thank you - seems to work now, great job!


Problem compiling dsniff

When I move on to the step "make" it turned out that:
./ssh.c:398:26: error: incomplete definition of type 'struct rsa_st'
get_bn(ssh->ctx->hostkey->e, &p, &i);
~~~~~~~~~~~~~~~~~^
/usr/local/opt/openssl/include/openssl/ossl_typ.h:110:16: note: forward
declaration of 'struct rsa_st'
typedef struct rsa_st RSA;
And this error happens many times
What's wrong?
plz, reply soon.

I've got the same errors. Look around and guess it's a problem of openssl 1.1 installed by Homebrew for the newer version alters API.
Maybe downgrading openssl to 1.0 can solve this, but i have not tried and it seems not so convenient because this version of openssl is no longer available via Homebrew, and you need to build yourself. A ref page about install openssl 1.0.2: https://stackoverflow.com/questions/59337838/openssl-1-0-2m-on-macos
A better solution is to update dsniff itself. Wait for it...


Some metrics are lost

This happens when I have a few metrics that share the same prefix, but do not have the same level of namespaces. For example:
'counters.token': 100,
'counters.token.200': 80,
'counters.token.401': 15,
'counters.token.500': 5

The backend will return:
{
  "counters": {
    "tokens: 100
  }
}

Is there a generic solution to return all the metrics? I know I can rename the first metric to counters.token.total, but there are many metrics in our application, and they are being used in many other monitoring systems and dashboards.

I wonder how other backends might support this use case.  The original backend for statsd was Graphite and you can't have a stat name that is both a folder and a metric.  Also, how would you propose modelling this in JSON?


Crash with latest version of Forge

This happened with the latest version of Forge and the mod:

https://paste.ee/p/Tsz1c

See #419, there is a crash higher up in your latest.log, this is just a followup due to it not crashing correctly in an earlier loading stage.

Help me please


Add a description section in donate section .

Describe the bug
A clear and concise description of what the bug is.
The donate section does not have description of the pet page. The description of the pet is important as sometime pet can have same color, size and breed to bifurcate and differentiate between them. It is just optional section the owner to give specific details. The description includes pet age, what he eats, his unique feature and so on.

Expected behavior
Here is the sample UI/UX This section will be added just after pet breed to briefly describe the pet.

I am gssoc contributor kindly assign this issue to me.

@akshitagupta15june plz assign this me under gssoc'23. It will be better if description section is added for more info.

I am from GSSoC'23.
I would like to be assigned this task.

@akshitagupta15june kindly let me know about it

Hey there! I'm Ashutosh Kumar, a full-stack MERN web developer. With experience in numerous successful MERN stack  projects, I excel in  HTML, CSS,JavaScript,C, C++,jQuery, Node.js, React.js, Bootstrap, Tailwind, Express, MongoDB, API,GraphQL,WebRTC.
You can find me on LinkedIn : https://www.linkedin.com/in/ashutosh-kumar-60b262251/
GitHub : https://github.com/Ashutosh-0506.
Looking forward to contributing to GSSOC 2024!


[walla] Fixed extractor and added site-wide video extraction

The previous extractor allowed downloading videos only from the VOD section.
Now when there is a video in an article, you can download it as well, using the article's URL.
I had to add the strip() to the _download_xml method, since some XML coming from walla can contain spaces in the beginning. If this is not the correct place, please notify me and I will change it.

It might be better to use the transform_source parameter of _download_xml()?


PAINT data imported

We  are now importing PAINT data. Presumably this has come in via GOA.
The good news is that it doesn't look too bad so we can keep them.
I think at present IBA must be the last evidence code in the filtering pipeline because after filtering there are only 69 IBAs to check. I will check these today, then we can prioritise IBA over IEA.
BUT, I want to check, because I did not expect the number to be so low. So @kimrutherford  how many PAINT (IBA) annotations do we have pre-filtering? Maybe they are not all included in UniProt/GOA, or maybe UniProt  do some pre-filtering of their own.
It's odd that there seem to be less to check  than I  already know are problematic......

@pgaudet this will make you happy. PAINT import happened accidentally via GOA  an it looks good!

Great !!
I must say
I am not clear at all with the pipeline. I would also like to see some stats about how many annotations make it, compared to how many annotations we have in the PAINT database, for example, to make sure all is OK.
@huaiyumi

I'm going to do some checking.....

So @kimrutherford how many PAINT (IBA) annotations do we have pre-filtering?

So the number of IBA evidence codes from GOA?  Here are the counts for all the codes from GOA for pombe:
    1 IKR
    5 IRD
   28 IEP
  420 TAS
  573 EXP
  740 NAS
  836 IGI
 1239 ISM
 1257 IC
 1535 HMP
 1604 ISS
 2116 ND
 3437 IPI
 4519 IMP
 5254 ISO
 6933 HDA
 7034 IDA
 8196 IBA
37506 IEA

OK, I don't believe we filter down to 69. This would imply that all of these were covered by existing annotation. I doubt it. I wonder if some are not loading form other reasons. I started to check the logs to see if there was anything in there (there isn't) but I'm still sidetracked fixing things in here .........
How strange. I can check by looking at some of my  tickets on the annotation tracker
https://github.com/geneontology/go-annotation/issues?q=is%3Aopen+is%3Aissue+author%3AValWood+label%3A"PAINT+annotation"

OK, I don't believe we filter down to 69.

I think I understand this now.  When we load from the GOA GAF we only load annotation assigned by InterPro or UniProt.  It looks like all the IBA annotations in the GOA GAF are assigned by GO_Central.  Almost all the GO_Central annotations are IBA:
    5 IRD
 8196 IBA

I think the 69 IBA annotations we do have are from the inferred GAF file: pombase-prediction.gaf - there are 619 IBA annotation from that file before filtering.

OK that makes sense!
OK I will check these 69 today from the F-P inferred GAF today...
(I really think these should have a different evidence code!)
We will  still not load the GO_Central PAINT annotation quite yet. I want to make sure the problems I know about are filtered first. Not so much checking to do then!

We will still not load the GO_Central PAINT annotation quite yet.

OK.  Let me know when you'd like me to do a test load including the extra annotation.

nothing to do here, these as will go away.


Can't run oc-mirror on low spec VM

Version
$ oc-mirror version
Client Version: version.Info{Major:"", Minor:"", GitVersion:"v0.2.0-alpha.1-76-g159c539", GitCommit:"159c5394", GitTreeState:"clean", BuildDate:"2023-01-11T01:33:11Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}

What happened?
When attempting to list, or mirror any content on a machine that has limited memory (4GB) and limited SWAP (2GB) I receive the following error:
error: render reference "registry.redhat.io/redhat/redhat-operator-index:v4.10": write /tmp/render-unpack-1874233107/usr/lib64/python3.6/__pycache__/tracemalloc.cpython-36.opt-1.pyc: no space left on device

What did you expect to happen?
I expect the command to run successfully.
How to reproduce it (as minimally and precisely as possible)?

create a VM with 2GB of SWAP, 4GB of memory and 60GB+ of storage.
clone the oc-mirror repo
install all deps, then make build
use the resulting binary to run the following commands

oc-mirror list operators --catalog registry.redhat.io/redhat/redhat-operator-index:v4.10 --package devspaces
oc mirror -c ./operators.yml --dry-run file:///var/tmp/mirror

where operators.yml contains:

---
apiVersion: mirror.openshift.io/v1alpha2
kind: ImageSetConfiguration
storageConfig:
  local:
    path: /var/tmp/mirror
mirror:
  operators:
    - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.10
      packages:
        - name: devspaces
          channels:
            - name: stable
              minVersion: '3.3.0'

After running each of the above commands, I received the same error.

This might be because I was using /var/tmp. I changed to use /home/<user> and it seems to work fine now 🙂

Disabling tmpfs mount for /tmp resolved this issue for me:
systemctl mask tmp.mount
reboot
tmp will be mounted on root (/tmp) and did not return any errors when running the mirror.


SES not supported, aborting taming frame initialization in Chrome 45

How to reproduce:

Navigate to https://developers.google.com/caja/demos/gettingstarted/host.html
Expected result:

Caja host page
Static hello world
Dynamic hello world

Actual result:

Caja host page

Browser: Chrome Version 45.0.2454.85 m
OS: Windows 7 Pro x64
Error:

Needed to update the version deployed on caja.appspot.com. Done. Thanks for the report.

Thanks!


uORB multi pubsub depends on order of subscribing/publishing

Below is what I found, correct me if I'm just wrong :):
Basically, I think, in the current multi pubsub implementation, the publisher needs to be started before the subscriber, otherwise they won't talk to each other.
An example from #2297 would be:

Mavlink starts first and wants to subscribe to the distance_sensor topic. It gets the first instance here:
https://github.com/PX4/Firmware/blob/master/src/modules/uORB/uORB.cpp#L144
The the ll40ls wants to do a advertise_multi:
https://github.com/PX4/Firmware/blob/master/src/drivers/ll40ls/LidarLitePWM.cpp#L116
https://github.com/PX4/Firmware/blob/master/src/modules/uORB/uORB.cpp#L93
I believe this fails here:
https://github.com/PX4/Firmware/blob/master/src/modules/uORB/uORBManager_nuttx.cpp#L246
And gets +1 here probably:
https://github.com/PX4/Firmware/blob/master/src/modules/uORB/uORBDevices_nuttx.cpp#L471
This leads to mavlink subscribing on 0 and the ll40ls publishing on 1.

Instead of the check ...

Does the node exist already?

It should be something like:

Does the node exist already and has stuff been published yet?
Does the node exist already but is it only opened by a subscriber?

@LorenzMeier bump, is this intended or should I try to come up with a fix?

The analysis is correct and we need to fix it, a fix would be more than welcome. I think I just found another race because of this in the HIL setup.


Fix accounts permissions

Created permissions for Accounts tab and Users tab.
Users tab:

[x] Everyone can see users
[x] Only Admin can edit/add/delete all users
[x] Everyone can edit their own user

Accounts tab:

[x] Only Admin and Sales Manager can add new Accounts
[x] Admin, Sales Manager (if created or assigned to account) and Sales Representative (if assigned to account) can edit Accounts
[x] Admin, Sales Manager (if created or assigned to account) can delete Accounts
[x] basic Users cannot be assigned to accounts

Users Tab

[x]  Everyone can see users ✅
[x]  Only Admin can edit/add/delete all users✅
[x]  Everyone can edit their own user✅

Accounts tab

[x]  Only Admin and Sales Manager can add new Accounts✅
[x]  Admin, Sales Manager (if created or assigned to account) and Sales Representative (if assigned to account) can edit Accounts

Note:
When the Sales Representative edits, they should not be able to edit the "assigned to" tab.
Because if they change it or leave it empty then the permission will be taken away from them ,
therefore they won't see this Account anymore in the accounts lists tab.

[x]  Admin, Sales Manager (if created or assigned to account) can delete Accounts✅
[x]  basic Users cannot be assigned to account‼
 I could not test this feature, I will try again and will edit this comment

Basic users work, please try again. They can be added from frontend but they get excluded in backend.
Changes added:

[x]  Only Sales Managers who created the account and Admins can change the assigned_to list. If someone else tries to change it then response is 200 but values overwritten with the pervious values.


SDK uses deprecated Microsoft.Azure.DocumentDB.Core library

Version
4.16.1
Describe the bug
The SDK uses a deprecated version of Microsoft.Azure.DocumentDb.Core which is now causing security warnings due to the lack of support for this library. Migration to Cosmos Db.NET V3 is the recommended path forward: Migrate your application to use the Azure Cosmos DB .NET SDK v3.
Expected behavior
SDK uses supported underlying libraries.

There are currently two classes that work with Cosmos, the older is CosmosDBStorage and the newer is CosmosDbPartitionedStorage. The latter is compatible with the original, and CosmosDBStorage has been marked deprecated now for two years, so let's remove CosmosDbStorage.cs, CosmosDBCustomerClientOptions.cs, and CosmosDBStorageOptions.cs which will then allow us to remove the dependency on Microsoft.Azure.DocumentDb.Core. We can put in the release notes that anyone using the remove class will need to move to the newer CosmosDBPartitionedStorage class, which is compatible so is only a minor change.


About file output size

Hello, author, I like this plugin very much, but I want to try to understand the internal principle of the plugin, I tried to output FlutterError.onError stack into the log file, but why I output more than 10,000 characters, while catcher_2 is very few and accurate, How did you do that

If you want to take a look at the internals, I would suggest starting here:
https://github.com/ThexXTURBOXx/catcher_2/blob/master/lib/core/catcher_2.dart#L478
From, there a Report object is being built which then represents the current error state of the application.
That's most of the magic. However, most of that stuff is not by me, but by jhomlala: https://github.com/jhomlala/catcher
This project is just a fork of his project (since it is kind of abandoned, with only very few updates coming out here and then)


MAISTRA-682 - Fixing Kiali CR secrets

On the Kiali CR,
it doesn't need to be used name which is used on helm. Because the kiali-operator does pass the name after receiving the array.
kiali-kiali-fixed.yaml.log
kiali-kiali-wrong.yaml.log

cc @brian-avery

After not using the name,
kiali-operator deploys correctly with pull secret.
pod-kiali-5dcd79f95f-8z9xm.yaml.log

cc @rcernich


Added initial support for OCP-TV output format

This is to add initial support. Yet to add support for validators, pass/fail etc.
Sample OCP-TV output:
    {"schemaVersion": {"major": 2, "minor": 0}, "sequenceNumber": 0, "timestamp": "2024-08-19T00:30:31.094657Z"}
    {"testRunArtifact": {"testRunStart": {"name": "pci_lmt", "version": "1.3.1", "commandLine": "-o ocp -c lmt.cfg auto", "parameters": {}, "dutInfo": {"dutInfoId": "319706019", "name": "hostname", "platformInfos": [], "softwareInfos": [], "hardwareInfos": []}}}, "sequenceNumber": 1, "timestamp": "2024-08-19T00:30:31.094946Z"}
    {"testStepArtifact": {"testStepId": "0", "testStepStart": {"name": "Rcvr:6 Step:5 Ann:CPU Tx -> Retimer Rx (Timing left)"}}, "sequenceNumber": 2, "timestamp": "2024-08-19T00:30:31.095273Z"}
    {"testStepArtifact": {"testStepId": "0", "measurement": {"name": "BDF:0000:1a:00.0 Lane:0", "value": 0.0, "validators": []}}, "sequenceNumber": 3, "timestamp": "2024-08-19T00:30:36.691321Z"}
    {"testStepArtifact": {"testStepId": "0", "measurement": {"name": "BDF:0000:1a:00.0 Lane:1", "value": 0.0, "validators": []}}, "sequenceNumber": 4, "timestamp": "2024-08-19T00:30:36.691972Z"}
    {"testStepArtifact": {"testStepId": "0", "measurement": {"name": "BDF:0000:1a:00.0 Lane:2", "value": 0.0, "validators": []}}, "sequenceNumber": 5, "timestamp": "2024-08-19T00:30:36.692493Z"}
    {"testStepArtifact": {"testStepId": "0", "measurement": {"name": "BDF:0000:1a:00.0 Lane:3", "value": 0.0, "validators": []}}, "sequenceNumber": 6, "timestamp": "2024-08-19T00:30:36.692845Z"}
    {"testStepArtifact": {"testStepId": "0", "measurement": {"name": "BDF:0000:1a:00.0 Lane:4", "value": 0.0, "validators": []}}, "sequenceNumber": 7, "timestamp": "2024-08-19T00:30:36.693209Z"}
    {"testStepArtifact": {"testStepId": "0", "measurement": {"name": "BDF:0000:1a:00.0 Lane:5", "value": 0.0, "validators": []}}, "sequenceNumber": 8, "timestamp": "2024-08-19T00:30:36.693568Z"}
    {"testStepArtifact": {"testStepId": "0", "measurement": {"name": "BDF:0000:1a:00.0 Lane:6", "value": 0.0, "validators": []}}, "sequenceNumber": 9, "timestamp": "2024-08-19T00:30:36.693947Z"}
    {"testStepArtifact": {"testStepId": "0", "measurement": {"name": "BDF:0000:1a:00.0 Lane:7", "value": 0.0, "validators": []}}, "sequenceNumber": 10, "timestamp": "2024-08-19T00:30:36.694338Z"}
    {"testStepArtifact": {"testStepId": "0", "testStepEnd": {"status": "COMPLETE"}}, "sequenceNumber": 11, "timestamp": "2024-08-19T00:30:36.694586Z"}
    {"testStepArtifact": {"testStepId": "1", "testStepStart": {"name": "Rcvr:6 Step:6 Ann:CPU Tx -> Retimer Rx (Timing left)"}}, "sequenceNumber": 12, "timestamp": "2024-08-19T00:30:36.694755Z"}
    {"testStepArtifact": {"testStepId": "1", "measurement": {"name": "BDF:0000:1a:00.0 Lane:0", "value": 0.0, "validators": []}}, "sequenceNumber": 13, "timestamp": "2024-08-19T00:30:42.283159Z"}
    {"testStepArtifact": {"testStepId": "1", "measurement": {"name": "BDF:0000:1a:00.0 Lane:1", "value": 0.0, "validators": []}}, "sequenceNumber": 14, "timestamp": "2024-08-19T00:30:42.283600Z"}
    {"testStepArtifact": {"testStepId": "1", "measurement": {"name": "BDF:0000:1a:00.0 Lane:2", "value": 0.0, "validators": []}}, "sequenceNumber": 15, "timestamp": "2024-08-19T00:30:42.283974Z"}
    {"testStepArtifact": {"testStepId": "1", "measurement": {"name": "BDF:0000:1a:00.0 Lane:3", "value": 0.0, "validators": []}}, "sequenceNumber": 16, "timestamp": "2024-08-19T00:30:42.284312Z"}
    {"testStepArtifact": {"testStepId": "1", "measurement": {"name": "BDF:0000:1a:00.0 Lane:4", "value": 0.0, "validators": []}}, "sequenceNumber": 17, "timestamp": "2024-08-19T00:30:42.284669Z"}
    {"testStepArtifact": {"testStepId": "1", "measurement": {"name": "BDF:0000:1a:00.0 Lane:5", "value": 0.0, "validators": []}}, "sequenceNumber": 18, "timestamp": "2024-08-19T00:30:42.285002Z"}
    {"testStepArtifact": {"testStepId": "1", "measurement": {"name": "BDF:0000:1a:00.0 Lane:6", "value": 0.0, "validators": []}}, "sequenceNumber": 19, "timestamp": "2024-08-19T00:30:42.285358Z"}
    {"testStepArtifact": {"testStepId": "1", "measurement": {"name": "BDF:0000:1a:00.0 Lane:7", "value": 0.0, "validators": []}}, "sequenceNumber": 20, "timestamp": "2024-08-19T00:30:42.287100Z"}
    {"testStepArtifact": {"testStepId": "1", "testStepEnd": {"status": "COMPLETE"}}, "sequenceNumber": 21, "timestamp": "2024-08-19T00:30:42.287347Z"}
    {"testRunArtifact": {"testRunEnd": {"status": "COMPLETE", "result": "PASS"}}, "sequenceNumber": 22, "timestamp": "2024-08-19T00:30:42.287470Z"}

the design of the OctTvOutputReporter thin wrapper breaks fundamental properties coming from the ocptv api lib

I'm trying to add the OCPTV output format natively but with very minimal changes to the main code. The thin wrapper allows me to handle OCPTV related code in a single class with very little modification to the main code.

while this isnt mandatory to fix, i would advise to consider them since this introduces code failure modes and tech debt, which may explode later and you or another maintainer will have to address

Understood.  I would love to know if there is a way to retain the benefits of the OCPTV APIs (esp contextmanager) and still contain the implementation in it's own Reporter sub-class.

i left a link with api examples above; it would be sufficient to follow that (how the api use contextmanager) in your wrapper class, since you want to keep that reporter interface. At the end of the day, try to write some code and then do the mental exercise of seeing what you can do with it. It doesnt have to be perfect, but if there's easy ways to misuse it (as i demonstrated above), then it can likely be improved

Thank you so much @mimir-d. Appreciate your support (during the review) and quick turnaround (in fixing the APIs).


Remove xf86-video-intel Xorg driver

Mesa is phasing out Intel driver in favor of modesetting since v20.0. We should remove it. Using modesetting is compatible with Nvidia prime configurations and iris graphics hardware.

Do we need to do something to enable modesetting?

Do we need to do something to enable modesetting?

No. It comes with Xorg and is the fallback driver for anything that it detects.


[module] Uncompressed grayscale format updating broken on GLES2

WARNING: Please, read this note carefully before submitting a new issue:
It is important to realise that this is NOT A SUPPORT FORUM, this is for reproducible BUGS with raylib ONLY.
There are lots of generous and helpful people ready to help you out on raylib Discord forum or raylib reddit.
Remember that asking for support questions here actively takes developer time away from improving raylib.

Please, before submitting a new issue verify and check:

[ yes] I tested it on latest raylib version from master branch
[yes] I checked there is no similar issue already reported
[yes] My code has no errors or misuse of raylib

Issue description
Briefly describe the issue you are experiencing (or the feature you want to see added to raylib). Tell us what you were trying to do and what happened instead. Remember, this is not the best place to ask questions. For questions, go to raylib Discord server.
Environment
Provide your Platform, Operating System, OpenGL version, GPU details where you experienced the issue.
x86, Linux, GLES2, gtx 1060
Issue Screenshot

If possible, provide a screenshot that illustrates the issue. Usually an image is better than a thousand words.
Code Example
#include "raylib.h"

int main(void)
{
    // Initialization
    //--------------------------------------------------------------------------------------
    const int screenWidth = 512;
    const int screenHeight = 2048;

    InitWindow(screenWidth, screenHeight, "raylib [textures] example - texture loading and drawing");
    SetTargetFPS(60);

    Image image = LoadImage("Mountain.png");
    ImageFormat(&image, UNCOMPRESSED_GRAYSCALE);
    Color *image_data = GetImageData(image);

    // Loads image into GPU, needs GL context given by InitWindow
    Texture texture = LoadTextureFromImage(image);
    texture.format = UNCOMPRESSED_GRAYSCALE; // just to make sure

    // Main loop
    while (!WindowShouldClose()) // Detect window close button or ESC key
    {
        // Draw
        //----------------------------------------------------------------------------------
        BeginDrawing();

        ClearBackground(RAYWHITE);

        UpdateTexture(texture, image_data); // this is what's broken
        DrawTexture(texture, screenWidth / 2 - texture.width / 2, screenHeight / 2 - texture.height / 2, WHITE); // draw to the center
        EndDrawing();
        //----------------------------------------------------------------------------------
    }

    // De-Initialization
    //--------------------------------------------------------------------------------------
    UnloadTexture(texture); // Texture unloading
    UnloadImage(image);

    CloseWindow(); // Close window and OpenGL context
    //--------------------------------------------------------------------------------------

    return 0;
}

@creikey Actually, that's the expected behaviour.
GetImageData() always return data as Color (RGBA), independently of the Image format.
It's up to the user to provide valid data to UpdateTexture() with the same format as texture.format.
Also, note that:
texture.format = UNCOMPRESSED_GRAYSCALE; // just to make sure

shouldn't be done because texture.format just takes same format as image.format.


Made InsertManager#insert chainable

Hey Guys,
First time contributing here, I was looking for low hanging fruits and thought that this one https://github.com/rails/arel/issues/402 could be it.
Let me know what you think.
Thanks

Awesome contribution. Thanks


Printing Stars Patterns

Printing stars pattern in Java.

Could you kindly explain in detail a bit about what you want to contribute?

I can print upper and lower triangle star pattern using c language. if you are  looking for this, then please do assign me the work


Open source Apple Music plugin

Picking up from https://x.com/ElgatoSupport/status/1860025327025816031
I'd like to have dial support for the Apple Music plugin owned by Elgato at https://marketplace.elgato.com/product/apple-music-719b94df-ee43-47b3-a7c0-a3ea176ebbec. I noticed it's not open-sourced, making it difficult for anybody else to contribute dial support for Apple Music. Would you consider open sourcing that on here and adding a dial for music volume?

Hi @bradgessler, I'm afraid we don't have plans to open source the Apple Music plugins at this time.
If you were interested in creating a new plugin that has expanded Apple Music functionality, we would love to see it on Marketplace! For more information on creating plugins, you can refer to our SDK documentation, or if you have any questions, please feel free to join our Marketplace Makers community Discord.

I would if I had time, but I don't. Was hoping this could be open sourced and a dial could be quickly added.
Could you run up the propriety chain a request to add a volume dial for Apple Music? That's my objective—I don't actually care if it's OSS or not.

No problems — I've added your feature request to our plugin board. I appreciate you taking the time to provide us with feedback.


Enhancement design of footer

I just review your work and fill like nothing here so the design should be enhanced for a better footer.

@jsroyal Dear Jitendra Singh, The plugin has no design constraints and only provides functionality to stick an element to the bottom of a parental element. I was wondering what you were trying to say with "... the design should be enhanced for a better footer". Could you be more elaborate?


Exception thrown misleading when OAuth2 provider refuses to return an access token

I am currently playing with Silhouette 5.0.0-RC2, and I find the getAccessToken error handling a bit misleading. If the provider answers a BadRequest when an access token is requested, then the exception will say:
Cannot build OAuth2Info because of invalid response format: List((/access_token,List(JsonValidationError(List(error.path.missing),WrappedArray()))))".

Maybe I am missing something, but in the case the method returns something different than a HTTP OK (200), would it be clearer to put that in the exception message? In my case, I had to debug step-by-step or increase the logging verbosity to see that the provider was actually saying:
[Silhouette][google] Access token response: [{
  "error" : "redirect_uri_mismatch"
}]

What do you think?

I'm aware of this issue and we do this already for the case that the result is not a JSON object.
The other case is a bit trickier, because it could lead to issues where secure credentials could be written to log files. Maybe a provider changes the structure of the successful result, so that it cannot be parsed to a OAuth2Info instance. In this case the access token could be printed to a log file which might be bad if an attacker has access to the log files.

Ok, thanks for the clarification.
But in my current case, where the result is not successful, do you agree that trying to parse the json is not relevant?
I was thinking of something like this:
protected def buildInfo(response: WSResponse): Try[OAuth2Info] = {
  Try(response.json) match {
    case Success(json) if response.status == 200 => json.validate[OAuth2Info].asEither.fold(
      error => Failure(new UnexpectedResponseException(InvalidInfoFormat.format(id, error))),
      info => Success(info)
    )
    case Failure(error) => Failure(new UnexpectedResponseException(JsonParseError.format(id, response.body, error)))
  }
}

I'm not sure if every provider returns status code 200 for a successful response. It would make sense, but I'm not sure if every provider does this. Maybe we could check for 2xx status codes or better we define a global successful status code and let the concrete provider override the code if another is used.

Yes, sounds good :)


[shellenv] preserve original XDG_DATA_DIRS during shellenv-ception

Summary
shellenv-ception is when we run shellenv within an already enabled shellenv environment.
We would like to preserve idempotency of XDG_DATA_DIRS for shellenv-ception, so
that we don't recursively keep prepending to the shellenv-enabled XDG_DATA_DIRS
and instead we prepend to the original XDG_DATA_DIRS.
How was it tested?
same as #1041

Current dependencies on/for this PR:

main

PR #1072   👈

This comment was auto-generated by Graphite.

That won't be enough, no?
For example, i'm considering the following scenario:

originally in the shell: XDG_DATA_DIRS=my-path-0
first shellenv produces: XDG_DATA_DIRS=my-path-1:my-path-0 because some nix package specified that my-path-1 should be in XDG_DATA_DIRS.
second shellenv that runs due to some edits to that nix package which changes my-path-1 to my-path-2. So, then we'd want the final env-var to be XDG_DATA_DIRS=my-path-2:my-path-0.

Does that make sense?
If so, I believe we do need to preserve the original env-var and not just de-duplicate in JoinPathLists

Its similar to the motivation for introducing OG_PATH in https://github.com/jetpack-io/devbox/issues/687

@savil what I had in mind was a bit more involved:
original XDG_DATA_DIRS=x:y:z
nix XDG_DATA_DIRS=a:z
computed XDG_DATA_DIRS=a:z:x:y
This has the following properties:

nix XDG_DATA_DIRS take precedent.
No duplicates
idempotent (because of no-duplicates property)

I think this could be used for all path joining cases (including PATH and LD_LIB) but that would introduce risk to this PR, so maybe use a new MergePathLists that joins and dedups?

@mikeland86 I don't think that removing duplicates will achieve idempotency by itself.
Continuing on from your example:

now we have XDG_DATA_DIRS=a:z:x:y
some edit is made, and shellenv is called again, and nix now has XDG_DATA_DIRS=b:z

Without the OG_XDG_DATA_DIRS fix, it'll be XDG_DATA_DIRS=b:a:z:x:y instead of what we would want: b:z:x:y
The PR as is will produce XDG_DATA_DIRS=b:z:x:y:z, which is idempotent. Its not "clean" since we have the trailing :z at the end, but functionally it won't matter.

@mikeland86 turns out JoinPathLists does de-duplicate. So, it does take care of the scenario you are concerned about.
I still think we also need to preserve the OG_XDG_DATA_DIRS so that we drop any directories that are no longer needed due to any nix edits that are made.

The result doesn't need to be unchanging to any input, it needs to be unchanging to the same input.
Specifically, calling shellenv multiple times should produce the same result (which would keep the hash constant). If the input changes then we get a different result.
Using the OG approach makes sense in a single shell world, but not sure it does in a multi-project world. It's also less scalable, we now need to keep a back-up variable for every one of these. I know that's what we already have for PATH, but I think we may want to move towards a deduping with prepending approach eventually.

Chatted IRL. Gonna punt on this for now since its a theoretical concern (no reports yet), and the pattern could lead to some edge-cases with nested shellenvs.


pass current i18n language into tinymce language option

I want to translate the tinymce buttons, and if I modify osd-canvas and osd-region files to include
 tinymce.init({
                   language: "cy-GB",,
                   selector : 'form.annotation-tooltip textarea',

Then it works fine, but of course I want it to pull in the i18n currentlng variable.  When loading the page it says that currentLng is set to cy-GB and I noticed that a lot of tinymce internationalisation scripts are called but tinymce doesnt automatically pick up the current lang.
I have tried re init and loading the current lang into a var but I keep getting undefined issues. JS is not my strongpoint and im tearing my hair out on this one :-)

Worked this out, must have been having a bad day.
In osd-region-rect-tools.js I just added a global var above the tinymce init. Possibly not the best solution but it worked for me :-)
      var tinylang = window.i18n.lng();
            tinymce.init({
              selector : 'form.annotation-tooltip textarea',
              menubar: false,
              statusbar: false,
              language: tinylang,
              toolbar: "my | custom | buttons |",
              formats: {


Crash while breeaking leaves, BirdsNests compatibility

I'm not sure which mod is causing this but when I install BirdsNests and try to break the dynamic leaves the game will eventually crash.
Dynamic Trees: 0.6.5
MC: 1.11.2

You got a crash log for me?

crash-2017-10-22_04.44.39-server.txt

Looks like the birdsnests mod is expecting my leaves to have a "decayable" property which it does not.  Dynamic leaves are derived from vanilla leaves but do not decay in the same way as vanilla leaves.
The author of birdsnests might consider putting in a check for leaves in case a mod(such as mine) does the leaves a bit differently.
if (blockState.getProperties().containsKey(DECAYABLE)) {
// do leafy stuff here
}
For me to institute a fix on my end I would have to do a tremendous amount of work to implement a non-standard IBlockState interface to return a fake "decayable" value and I don't know if the mod would be happy with true or false.

This is on BirdsNests to fix.  I've given my suggestion on how to fix it.  Looks like BirdsNests hasn't been updated in a while so I don't foresee this being fixed.

This has been fixed by cleverpanda.


save transactions to, fetch transactions from indexed db

Fixes #295.
In order to speed up history load time and efficiently count total number of transactions in wallet, this PR applies the dcrlibwallet tx indexing feature to godcr, regardless of whether wallet connection is established via dcrlibwallet or dcrwalletrpc.
In addition to improving history load times due to indexing, the following improvements come with this PR:
Transaction Details

The information processed/indexed and returned per transaction is updated in this PR. Tx details now contain a complete list of inputs and outputs (previously only inputs/outputs relating to wallet were processed). This resolves #268.
Tx details now also return the account number and account name for each input in a transaction. Returning account name for inputs and address for outputs is necessary in resolving

#302 (wrt displaying account column in http history page) and
#250 (wrt showing account names for inputs in tx details page).

Currently, account names are not returned for outputs but a look at the tx details page implementation (in terminal for example) exposes how to get the account name for each output using the address (should probably fix this, have the core code return the account name rather than leaving interfaces to convert address to account name).

Transaction Count and Filtering

Necessary in resolving #302 (wrt displaying count of all transactions, getting count of transactions by type and/or direction; and filtering by transaction type and direction).

Part of #311 (regarding showing total tx count at the top of the terminal history page) is fixed in this PR.

This PR also resolves #312 relating to terminal tx detail page not showing block height.

Part of #280 (wrt showing total transaction count in cli history) is also fixed in this PR.

Part of #274 and #303 (re showing the full format for datetime in tx detail page in cli and http history).

Using the Filter
See the updated comments on wallet.TransactionCount and wallet.TransactionHistory for guide in

how to get tx count for each filter
knowing what filters to display (where tx count for that filter is > 0)
retrieving transactions for a particular filter
combining filters

Need to test properly to confirm that this PR does not cause breaking changes in history and tx detail pages across all interfaces when connecting via dcrlibwallet and dcrwalletrpc.

Overall looks good. Tx details views need to show timezone on the date time.


can not load scss file with storybook

i hava configed the webpack.config.js follow:
const path = require('path'); module.exports = {     module: {         loaders: [             {                 test: /\.scss$/,                 loader:'style!css!sass',                 include: __dirname             }         ]     } }
buy when i run storybook ,the error follow show:
@arunoda  can u help me.
ERROR in ./imports/ui/layouts/app.scss Module parse failed: /Users/ww/Desktop/dev/meteorPro/forum/imports/ui/layouts/app.scss Unexpected token (1:0) You may need an appropriate loader to handle this file type. SyntaxError: Unexpected token (1:0)

include should be path.resolve(__dirname, '../)


Cannot use LlamaGuardShield since not present in config

Trying to use Llama3.2-11B-Vision-Instruct with no PromptGuard / LlamaGuard, along with llama-stack-apps/app/main.py. Perhaps I can disable Safety with the Agents logic somehow?
Getting this error in my terminal:
INFO:     <IP_ADDRESS>:39656 - "POST /agents/create HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:39656 - "POST /agents/session/create HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:39656 - "POST /agents/turn/create HTTP/1.1" 200 OK
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/llama_stack/distribution/server/server.py", line 231, in sse_generator
    async for item in event_gen:
  File "/usr/local/lib/python3.10/site-packages/llama_stack/providers/impls/meta_reference/agents/agents.py", line 127, in create_agent_turn
    async for event in agent.create_and_execute_turn(request):
  File "/usr/local/lib/python3.10/site-packages/llama_stack/providers/impls/meta_reference/agents/agent_instance.py", line 174, in create_and_execute_turn
    async for chunk in self.run(
  File "/usr/local/lib/python3.10/site-packages/llama_stack/providers/impls/meta_reference/agents/agent_instance.py", line 239, in run
    async for res in self.run_multiple_shields_wrapper(
  File "/usr/local/lib/python3.10/site-packages/llama_stack/providers/impls/meta_reference/agents/agent_instance.py", line 294, in run_multiple_shields_wrapper
    await self.run_multiple_shields(messages, shields)
  File "/usr/local/lib/python3.10/site-packages/llama_stack/providers/impls/meta_reference/agents/safety.py", line 37, in run_multiple_shields
    responses = await asyncio.gather(
  File "/usr/local/lib/python3.10/site-packages/llama_stack/distribution/routers/routers.py", line 168, in run_shield
    return await self.routing_table.get_provider_impl(shield_type).run_shield(
  File "/usr/local/lib/python3.10/site-packages/llama_stack/providers/impls/meta_reference/safety/safety.py", line 62, in run_shield
    shield = self.get_shield_impl(MetaReferenceShieldType(shield_type))
  File "/usr/local/lib/python3.10/site-packages/llama_stack/providers/impls/meta_reference/safety/safety.py", line 93, in get_shield_impl
    cfg is not None
AssertionError: Cannot use LlamaGuardShield since not present in config

built_at: '2024-09-25T18:42:07.306715'
image_name: local-gpu
docker_image: local-gpu
conda_env: null
apis_to_serve:
- agents
- memory
- models
- safety
- memory_banks
- shields
- inference
api_providers:
  inference:
    providers:
    - meta-reference
  safety:
    providers:
    - meta-reference
  agents:
    provider_id: meta-reference
    config:
      persistence_store:
        namespace: null
        type: sqlite
        db_path: /root/.llama/runtime/kvstore.db
  memory:
    providers:
    - meta-reference
  telemetry:
    provider_id: meta-reference
    config: {}
routing_table:
  inference:
  - provider_id: meta-reference
    config:
      model: Llama3.2-11B-Vision-Instruct
      quantization: null
      torch_seed: null
      max_seq_len: 4096
      max_batch_size: 1
    routing_key: Llama3.2-11B-Vision-Instruct
  safety:
  - provider_id: meta-reference
    config:
      llama_guard_shield: null
      prompt_guard_shield: null
    routing_key: llama_guard
  - provider_id: meta-reference
    config:
      llama_guard_shield: null
      prompt_guard_shield: null
    routing_key: code_scanner_guard
  - provider_id: meta-reference
    config:
      llama_guard_shield: null
      prompt_guard_shield: null
    routing_key: injection_shield
  - provider_id: meta-reference
    config:
      llama_guard_shield: null
      prompt_guard_shield: null
    routing_key: jailbreak_shield
  memory:
  - provider_id: meta-reference
    config: {}
    routing_key: vector

My mistake- it's hardcoded in the agent example in the apps client_utils


Update Interrogate documentation for clarity to naive user

Currently documentation in readme surrounding features like interrogate, flake, black, etc are not documented with use or solutions. (ie, how to run from terminal and how to solve errors they throw)

I'm making a branch for this, which I will include the documentation updates I have been walked through today. Please feel free to add your own to the branch

branch: https://github.com/AllenNeuralDynamics/aind-data-schema/tree/docs-300-improve-readme

Let's break this down into smaller issues...


Shortcut Control  + Command + R not working for Sketch 49.3

Shortcut Control  + Command + R not working for Sketch 49.3

We used Mac Sierra 10.12.6

@dwinurhadia Sorry for the long wait on this. The issue is that you probably have another plugin overwriting the shortcut. I use this plugin, https://github.com/PeachScript/sketch-plugin-monster, to manage the shortcuts. It will also tell you if there is any duplicates

Dear Sir,
Thank you for informations


Update Jitpack builds to 1.16

There's a jar for 1.16, but builds on Jitpack are still on 1.15 and don't work on 1.16

jitpack is an automated thing, you just specify a release tag, and a release version for 1.16 exists.

But Jitpack builds what's on the branch, and there isn't a branch with 1.16 code here. I see there was a release tagged with a 1.16 build, but that tag exists on the 1.15 branch which is what gets built by Jitpack.

oh wow I can't believe I didn't push the commits, thanks for pointing this out, it's actually resolved now


Add ability to adjust slash position in bread crumb

Add ability to adjust slash position in bread crumb

I'm wondering the use case here. Does it have to do with changing text size? if so i'm wondering if we can try and do this better through sass math as opposed to a variable.

@zurbrandon hi there.. The use case here is when you use different font, for example google font, for my experience, the slash is not aligned with the text, its either up or down, that's the reason i create this PR. Also this helps when you use different separator other than slash. Its not for changing text sizes :)

Thanks man :D, i have the same problem, but, when i change the slash with &raquo.


[20.09] bitcoin: 0.20.1 -> 0.21.0

Motivation for this change
Repology treats it as outdated and dangerous/vulnerable.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Why is nomad part of this PR?

No reason at all. I just cherry-picked all related commits to this modification.

No reason at all. I just cherry-picked all related commits to this modification.

No reason at all. I just cherry-picked all related commits to this modification.

Repology treats it as outdated and dangerous/vulnerable.

Repology is wrong in that regard - 0.20.1 is perfectly fine. I suggest leaving it as it is. And maybe later update it to 0.20.2 if some serious bug fix needs to be backported.

Good to know!


fix status and server ready

Also, your distributes-tests should be public repo, but now it's private.


Ability to use ParcelPropertyConverter annotation with ParcelClass annotation

Hello, thanks for you library, very great job!!!
Could you please tell me, how can i use "@ParcelPropertyConverter" while using approach "@ParcelClass" for declaration parcel classes. My model classes are in the different library, and i can't to mark parcel annotations directly to models.
Example which i'm waiting for:
@ParcelClasses({
        @ParcelClass(value = ExternalModel.class, annotations = {@ParcelPropertyConverter(value = ExternalModelFieldConverter.class, field = "listOfFields")}) //listOfFields is a member (List<...>) in the ExternalModel class, also we can put multiple property converters
})
public class ParcelsDeclaration {}

Hmm, are you looking to specify a converter for ExternalModel or a non-global converter for the properties on ExternalModel?

I'm looking for specifying converter for some internal field with type List and generic of abstraction (interface or abstract class). This field is a member of some external library class.

You could tell Parceler the converter for that type globally:
@ParcelClasses({
        @ParcelClass(value = SomeType.class, annotation = @Parcel(converter = SomeTypeConveter.class)),
        @ParcelClass(value = AnotherType.class, annotation = @Parcel(converter = AnotherTypeConveter.class)),
})
public class ParcelsDeclaration {}

Thinking about it more, you could register the generic type directly or include a converter if necessary.  Parceler knows how to handle Lists and would also handle your generic type if registered:
class Exernal {
    List<SomethingElse> stuff;
}

@ParcelClasses({
    @ParcelClass(External.class),
    @ParcelClass(value = SomethingElse.class, annotation=@Parcel(converter = PossibleConverter.class))
})

Thanks, it even works with List property!


Add static search

Use or get inspired by
https://github.com/bridgetownrb/bridgetown-quick-search
possibly using lunr.js search system

we are going to use minisearch and we now have a CLI plugin for it.
Adding it to the frontend is still an open task (need to think about how to include plugins in the frontend... probably 11ty plugins / filters...)

this has been implemented