Missing Features

I really like where Blogifier is going, and I realize that it's still a relatively new codebase, but there are a few features I wasn't really seeing mentioned here, but would really like:

Custom Pages - most blogs generally also have some custom pages. These could be an "About Me", a "Resume", etc.
Contact Page - again many websites generally want to enable users to contact the site owner. Certainly a v1 could be a simple contact form, but it would be awesome to have a form builder so that forms could be used across one or more pages.

Also not sure if it's a limitation of the default template or framework limitation, but I was noticing there's no way to set the url or enable/disable the social links

We've just added widgets framework and now working on themes framework, which will allow theme customization, external loading and so on. Form builder is something we can look into later, but its not high on priority list to be honest, at least right now.

Totally understandable. Also forgot to mention Blog Comments. I know that there is a wiki entry for Disqus but having it as a built in feature would be nicer.

Also I want to change post's date because I imported posts, they are all incorrect.

Have the ability to display the full post in a post list, instead of just the excerpt. The data isn't even accessible in the view as it is right now so I can't get away with a theme.

I am going to be slapping on a jquery datepicker to the date published field in admin. I really like the simple look & feel of this one: https://www.jqueryscript.net/time-clock/Super-Tiny-jQuery-HTML5-Date-Picker-Plugin.html  I think it matches blogifier's UI aesthetic.
Would you like me to push my changeset after I implement?

I am going to be slapping on a jquery datepicker to the date published field in admin. I really like the simple look & feel of this one: https://www.jqueryscript.net/time-clock/Super-Tiny-jQuery-HTML5-Date-Picker-Plugin.html I think it matches blogifier's UI aesthetic.
Would you like me to push my changeset after I implement?

I think you would need datetime picker. Anyway, if you do something that can be useful to others, just submit pull request for review.

Would be nice to include also custom code to header and some trackers too!

I would definitely vote for "comments" module, should relatively easy to add.
I think custom forms and other pages can be handled with static files easily.

Closing to avoid confusion, most of this pretty old and no longer relevant.


Increase Members per Tag Limit

Number of members per tag has been increased from 100 to 200

#sign-off


unable to add externalReferralProgram

I am not  able to externalReferralProgram as an option

I've pushed a fix - try the latest version & let me know: npm install ftx-api@latest

@tiagosiebler  please update the example for using it it doesn't display in autocorrect it needs to be submitted as an optional params


Updated background color index.html

your pr is conflicted, star the repo this is mandatory and you can also follow me.


Tiny Tapeout 6 Submission Issues [Action required]

Hi, congrats on submitting to Tiny Tapeout 6!
Unfortunately, there are some issues with the submission that prevent it from being integrated into the shuttle:

VPWR and VGND rails on metal4 are are not exported as pin under their whole length
Some of the INPUTS are shorted to VGND (e.g. ena, rst_n, clk, and the uin_in ports)

In addition, @smunaut did a quick review of the design, and found some potential issues:

Power seems to have been routed as a normal signal wire, using a thin wires, and with one via connecting the power rail. With that configuration, that module might have issues if it tries to consume more than ~ 300 uA
There is also a massive amount of routing on li (which has pretty high resistance)

We suggest to fix the issues and resubmit through https://app.tinytapeout.com/projects/586 before the shuttle's deadline (about 11 hours from now). Otherwise, we won't be able to include the project in Tiny Tapeout 6 (and it looks like a cool project, so we'd love to have it in).

cc @cavelcu

Thank you very much Uri, we are revising and evaluating our options.

First two issues are easily fixed

I just submitted a new revision for this project. Please let us know if everything is under control

Thanks! I ran a special test to see if it integrates with the chip in isolation, so instead of waiting for ~2 hours to know, we'll know in about 20 minutes. You can follow it here:
https://github.com/TinyTapeout/tinytapeout-06-staging/actions/runs/8756963308

Looks like it passed

Awesome!

Awesome. Thank you very much for your help Uri

When submitting the combined chip to efabless, we encountered fom density (nwell/tap) issues. We tracked them down to where this design is placed:

Unfortunately, this means we'll have to remove this design from TT06 in order to make it for the efabless tape out deadline. I'm sorry.

Good news!
Efabless had some issues with their submission system, so I took advantage of the delay it caused and tried to reposition your project in attempt to find a spot where the fom density meet the requirements. And I finally found such spot!
This means that your design will be fabricated on Tiny Tapeout 6. Congratulations!
p.s. you can find the final combined TT chip file we submitted to the fab here: https://github.com/TinyTapeout/tinytapeout-06/releases/tag/tapeout-ci2404

Thank you so much!


teslaCtrlSendCommand; Failed to execute command: car could not execute command: SetChargingAmps failed

Hello!
Since 2024.26.7 I have no way to get under 5 Amps (from car, from tesla app and from ble)....
Anyone with same problem?
Chris

Still works ok for me. What do the logs say? Here's mine when setting to 1 amp:
2024-08-19T12:45:05.844906497Z Command charging-set-amps 5 was successfully delivered to vin:LRXXXXXXXXX
2024-08-19T12:45:14.282956788Z Received MQTT message; topic:tesla_ble/LRXXXXXXXXX/charging-set-amps msg:1 vin:LRXXXXXXXXXcmd:charging-set-amps
2024-08-19T12:45:14.287278892Z Attempt 1/5 sending Set charging Amps to 1 (#1/2) to vin:LRXXXXXXXXXcommand:charging-set-amps 1
2024-08-19T12:45:17.597807879Z Command charging-set-amps 1 was successfully delivered to vin:LRXXXXXXXXX
2024-08-19T12:45:19.606899653Z Attempt 1/5 sending Set charging Amps to 1 (#2/2) to vin:LRXXXXXXXXXcommand:charging-set-amps 1
2024-08-19T12:45:22.876516988Z Command charging-set-amps 1 was successfully delivered to vin:LRXXXXXXXXX

Only this for every retry it does:
Received MQTT message; topic:tesla_ble/XXXXXXXXXXXXX/charging-set-amps msg:1 vin:XXXXXXXXXXXXX cmd:charging-set-amps
Attempt 1/5 sending Set charging Amps to 5A then to 1 to vin:XXXXXXXXXXXXXXXXXX command:charging-set-amps 1
teslaCtrlSendCommand; Failed to execute command: car could not execute command: SetChargingAmps failed
Skipping command charging-set-amps 1 to vin:XXXXXXXXXXXXXXXXX

Maybe Tesla have changed something which would be very annoying. I'm on 2024.20.9

I tried also with debug enabled but the message is the same.
However I noticed sometimes various
teslaCtrlSendCommand; Error: ble: failed to enumerate device services: ATT request failed: input channel closed: io: read/write on closed pipe

How far away is your device from the car? The error message you report is more frequent if the distance is further

Yes, I was suspecting the same....it is not so near the car... :)

Any way you can try it closer? At least to rule out or otherwise whether Tesla have changed anything

Not able, the raspberry I am using is mounted inside an electrical box....
However it was working good before last tesla update.... Let's hope is not a Tesla limit.

OK. I'll see if I can upgrade my car's software to see what happens

teslaCtrlSendCommand; Error: ble: failed to enumerate device services: ATT request failed: input channel closed: io: read/write on closed pipe
That error tells us Linux probably can't communicate with the BLE adapter. Please reboot your device and see if it starts working again.

Working fine for me with latest car update. @chrispazz do you still have the issue?

Resolved today. I was a Tesla side issue.
Resolved using this solution:
https://github.com/teslamotors/vehicle-command/issues/287#issuecomment-2306575740

Thanks for the update, glad it got resolved


Fixed compilation on windows (with exception)

@stuartarchibald
I fixed the 2015 studio build for everything and fixed 2008 build for omppool and workqueue. But I did nothing w.r.t. tbbpool with old 2008 compiler, it requires extensive reworking. Once again, the options we discussed are:

compile it separately with new compiler and then link with everything else using old compiler.. perhaps.. though I'm still now sure how to accomplish that. probably make a separate setup.py which creates static lib which then reused for main compilation and linkage of tbbpool extension... but I'm not sure about all the details and think that complexity of this solution exceeds complexity of rewritting the module to C++98
use Intel composer XE 2013 which is still compatible with vs2008 but supports c++11 already - that is what we do in our distro now
use MSVS2017 which supports linking with old runtimes https://blogs.msdn.microsoft.com/vcblog/2016/02/24/stuck-on-an-older-toolset-version-move-to-visual-studio-2015-without-upgrading-your-toolset/
do not build tbbpool for this config (e.g. remove dependence on tbb-devel for this case in recipe)

Though I like the idea to make tbb default everywhere, you said workqueue will rather stay anyway.. thus, why not to use workqueue or omppool for this config by default at least until e.g. (3) is implemented in your infrastructure..
So, my suggestion is to go with (4) for now and you can see whether other options are feasible.

@anton-malakhov Thanks for making these changes, they look good on inspection, I think we can just merge and put it through the build farm to see what it thinks. As discussed over IRC:

Think this is similar to how llvmlite is built, it may well work.
Will speak to the build team etc.
Didn't know that, thanks for sharing. As 2, will speak to build team.
This may be the cheapest option for now :)

Merging!


zef: 0.16.0 -> 0.17.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ugexe/zef/releases.
meta.description for zef is: Raku / Perl6 Module Management
meta.homepage for zef is: https://github.com/ugexe/zef
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.17.0 with grep in /nix/store/8fldlxdpv8clanj189il8n0gvnxxwii6-zef-0.17.0
found 0.17.0 in filename of file in /nix/store/8fldlxdpv8clanj189il8n0gvnxxwii6-zef-0.17.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
zef

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8fldlxdpv8clanj189il8n0gvnxxwii6-zef-0.17.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A zef https://github.com/r-ryantm/nixpkgs/archive/eb3fc41f913087e80026c3401b828e6e4f61a083.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8fldlxdpv8clanj189il8n0gvnxxwii6-zef-0.17.0
ls -la /nix/store/8fldlxdpv8clanj189il8n0gvnxxwii6-zef-0.17.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

zef

Maintainer pings
cc @stigtsp for testing.

Result of nixpkgs-review pr 217388 run on aarch64-darwin 1

1 package built:

zef


Rsheldon/ch5194/fork jr and get rid of serializer shortcut

we're doing some funky business in JR with nonprimary keys being the identifier for resources. JR didn't really plan for this in the past, and assumed that underlying DB keys would be the keys of the resources. We've gotten by with monkey patches for the most part now, and this could also be a monkey patch if we wanted, but so far we've monkey patched extension classes and not underlying classes. I figured it'd be better to have this in a fork, since the function no longer exists on master of JR, and if we were to upgrade without a fork we may lose this functionality.

should we make a PR to JR directly, as well?

we're disabling functionality for most people so probably not :x if you are passing around database ids you save a database call by doing it the way we are disabling

gonna merge this to move the story along


Support for together.ai OpenAPI endpoints

Describe the need of your request
Thank you for working on this awesome plugin.
together.ai provides an openai compatible endpoint that could work, except they have a wide range of models with different names.
Proposed solution
allow to use custom model name
or
load all available models from the api instead of hardcoding them.
(openai api provides a list of available models)
Additional context
awesome plugin, love it

Hey,
Version 2.4.0 is now publicly available, providing the option to configure custom OpenAI-compatible services.
Please let me know if it helps.


home section HTML code with CSS code

fixes #1 : i included a navigation menu linked to jump into the specific parts of our website such as home, about, services, team, and section. For the design, I accept the suggestion of @camille-vrx to make the image as bg and welcoming message above it

Good design for welcoming visitors. Navigation menus are also responsive. Btw, thanks for accepting my suggestion!

I'm also ok with this!


Building package curl:x86-windows failed with: BUILD_FAILED

C:\Users\test\Desktop\vcpkg>vcpkg.exe install CPR
The following packages will be built and installed:
cpr:x86-windows

curl:x86-windows
Additional packages (*) will be installed to complete this operation.
Building package curl:x86-windows...
-- CURRENT_INSTALLED_DIR=C:/Users/test/Desktop/vcpkg/installed/x86-windows
-- DOWNLOADS=C:/Users/test/Desktop/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/Users/test/Desktop/vcpkg/packages/curl_x86-windows
-- CURRENT_BUILDTREES_DIR=C:/Users/test/Desktop/vcpkg/buildtrees/curl
-- CURRENT_PORT_DIR=C:/Users/test/Desktop/vcpkg/ports/curl/.
-- Using cached C:/Users/test/Desktop/vcpkg/downloads/curl-curl-curl-7_55_1.tar.
gz
-- Testing integrity of cached file...
-- Testing integrity of cached file... OK
-- Extracting done
-- Applying patch C:/Users/test/Desktop/vcpkg/ports/curl/0001_cmake.patch
-- Applying patch failed. This is expected if this patch was previously applied.

-- Applying patch C:/Users/test/Desktop/vcpkg/ports/curl/0001_cmake.patch done
-- Applying patch C:/Users/test/Desktop/vcpkg/ports/curl/0002_fix_uwp.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Applying patch C:/Users/test/Desktop/vcpkg/ports/curl/0002_fix_uwp.patch done
-- Configuring x86-windows-rel
-- Configuring x86-windows-rel done
-- Configuring x86-windows-dbg
-- Configuring x86-windows-dbg done
-- Package x86-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:43 (message):
Command failed: C:/Users/test/Desktop/cmake-3.9.1-win64-x64/bin/cmake.exe;--
build;.;--config;Release;--target;install;--;-v
Working Directory: C:/Users/test/Desktop/vcpkg/buildtrees/curl/x86-windows-r
el
See logs for more information:
C:\Users\test\Desktop\vcpkg\buildtrees\curl\package-x86-windows-rel-out.lo
g
C:\Users\test\Desktop\vcpkg\buildtrees\curl\package-x86-windows-rel-err.lo
g
Call Stack (most recent call first):
scripts/cmake/vcpkg_install_cmake.cmake:49 (vcpkg_execute_required_process)
ports/curl/portfile.cmake:51 (vcpkg_install_cmake)
scripts/ports.cmake:72 (include)
Error: Building package curl:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: curl:x86-windows
Vcpkg version: 0.0.85-2017-08-28-28e581599e263e3f0b021ad5b6914d80fa9640f8
Additionally, attach any relevant sections from the log files above.
C:\Users\test\Desktop\vcpkg>
package-x86-windows-rel-out.log.zip

Hi @k3v1n1990s, this may be fixed in the latest master.
Could you try updating and let us know if the problem still repro's?

C:\vcpkg>vcpkg install curl
The following packages will be built and installed:
curl:x86-windows

libssh2:x86-windows
openssl:x86-windows
zlib:x86-windows
Additional packages (*) will be installed to complete this operation.
Starting package 1/4: zlib:x86-windows
Building package zlib:x86-windows...
-- CURRENT_INSTALLED_DIR=C:/vcpkg/installed/x86-windows
-- DOWNLOADS=C:/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/vcpkg/packages/zlib_x86-windows
-- CURRENT_BUILDTREES_DIR=C:/vcpkg/buildtrees/zlib
-- CURRENT_PORT_DIR=C:/vcpkg/ports/zlib/.
-- Using cached C:/vcpkg/downloads/zlib1211.tar.gz
-- Testing integrity of cached file...
-- Testing integrity of cached file... OK
-- Extracting done
-- Configuring x86-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:43 (message):
Command failed: C:/vcpkg/downloads/cmake-3.9.3-win32-x86/bin/cmake.exe;C:/vcpkg/buildtrees/zlib/src/zlib-1.2.11;-DSKIP_INSTALL_FILES=ON;-DBUILD_SHARED_LIBS=ON;-DVCPKG_TARGET_TRIPLET=x86-windows;-DCMAKE_CXX_FLAGS= /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP ;-DCMAKE_C_FLAGS= /DWIN32 /D_WINDOWS /W3 /utf-8 /MP ;-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON;-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON;-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON;-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE;-DCMAKE_VERBOSE_MAKEFILE=ON;-DVCPKG_APPLOCAL_DEPS=OFF;-DCMAKE_TOOLCHAIN_FILE=C:/vcpkg/scripts/buildsystems/vcpkg.cmake;-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON;-DCMAKE_CXX_FLAGS_RELEASE=/MD /O2 /Oi /Gy /DNDEBUG /Z7 ;-DCMAKE_C_FLAGS_RELEASE=/MD /O2 /Oi /Gy /DNDEBUG /Z7 ;-DCMAKE_SHARED_LINKER_FLAGS_RELEASE=/DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF ;-DCMAKE_EXE_LINKER_FLAGS_RELEASE=/DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF ;-G;Ninja;-DCMAKE_BUILD_TYPE=Release;-DCMAKE_INSTALL_PREFIX=C:/vcpkg/packages/zlib_x86-windows
Working Directory: C:/vcpkg/buildtrees/zlib/x86-windows-rel
See logs for more information:
C:\vcpkg\buildtrees\zlib\config-x86-windows-rel-out.log
C:\vcpkg\buildtrees\zlib\config-x86-windows-rel-err.log

Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:170 (vcpkg_execute_required_process)
ports/zlib/portfile.cmake:10 (vcpkg_configure_cmake)
scripts/ports.cmake:72 (include)
Error: Building package zlib:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: zlib:x86-windows
Vcpkg version: 0.0.89-2017-09-23-67e876c76555c466e4faf49d6cd80a88b835f972
Additionally, attach any relevant sections from the log files above.

Still failing.

It seems to build it fine in current master (https://github.com/Microsoft/vcpkg/commit/05edef92233854e944baa3cbde4d5b004f717bdd) to build curl:x64-windows on Windows 10 Evaluation image( https://developer.microsoft.com/en-us/windows/downloads/virtual-machines) .
Still reproduce?

Please open a new issue if this is still a problem for you.


Not working if aircondition are on a different subnet

Hi it works great but if the ac units are moved to a different subnet (other VLAN) and although I can ping the ACs from home assistant the plugin does not connect to any AC.
Is there a limitation if the ACs are on a different VLAN?

Hi, there is no any limitation

I see but why is not working? I see is using port 80 but is it tcp or udp? Does it using broadcast because I am trying to access it from another VLAN?


New parser

Closes #13.

[x] Comments are ignored everywhere
[x] Enums and function arguments are parsed, if not supported
[x] AST contains metadata like spans
[ ] Parser creates AST from a list of tokens, not the raw string

Closing for now


Deleting a menu causes a global delete for all menu items in all other menus

Hi everyone,
I'm using:
Strapi v4.21.0
Navigation v2.4.0
Node v18.19.1
NPN v10.2.4
I deleted an useless menu (on my project) from the "Manage All Navigations" pop-up dialog and after that I noticed the all items in all other menus have been deleted, all plugin database tables are empty.
I tested a couple of time and the issue persist.
Thanks.

Confirm.

Released as part of v2.5.0.
Note that was last major release containing features for Strapi v4.


refactor: event 系统

目前存在两个个问题，大家看一下
1、老接口是否保留
2、点击/消息元素 是挂在 Player 上还是挂在各自的 合成上，现在为了方便操作，用户直接使用元素的事件emit更简单一些，不需要进行名称的筛选
@yiiqii  @wumaolinmaoan  @RGCHN  @liuxi150
确定后更新 threejs的变动 及 单测

Summary by CodeRabbit

New Features

Introduced event emission for player activities, such as state changes and errors.
Enabled user interactions within the player component with dedicated event listeners.
Added new properties and methods to enhance composition interactivity and state management.
Newly defined types for robust event handling related to user interactions.

Improvements

Enhanced event handling across the Player, Composition, and related classes, promoting an event-driven architecture.
Deprecated outdated callback functions to streamline event management.

User Experience

Improved responsiveness and interactivity in visual effects handling.
Enhanced logging for user actions, providing better feedback and debugging capabilities.
Updated resource loading to better manage composition events and state transitions.

元素监听事件和合成监听事件应该都支持比较合理？


BDOG-21 Catalogue doesn't understand -play-25 versions

I'm not sure if this is part of services-dependencies or rather catalogue-frontend but do we want to show play-26 dependencies on a play 2.6 microservice and play-25 ones on play 2.5 microservices? Only returning major,minor,patch may not enable this.

Sounds like returning the version's suffix would be the right thing to do. Doesn't really make sense for the service to be discarding this data.
I'll look at adding it in.

We could also return major,minor,patch and one more field e.g. playCrossCompiled = true/false. Then the Catalogue could infer the version of play from a plugin that is used and add a correct suffix of -play-25 or -play-26. Just a thought, maybe not a good one.

Not sure how easily we can identify if a given library version is cross compiled.
It looks like the service finds latest/alternative library versions by looking at the libraries repo's tags, which only have the version (e.g. v1.2.3). Might be possible to parse it from the release name or look it up in the artefact repository?

I've raised a new ticket (BDOG-44) to implement this.


revert: do not create the index policies from the gateway

Issue
https://gravitee.atlassian.net/browse/APIM-7236
Description
In this PR I revert what I did in the previous one as we won't create the index policies for the customers but just reference it in the templates
Additional context

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 5.1.2-apim-7236-revert-policy-creation-SNAPSHOT
download it from Artifactory here

:tada: This PR is included in version 5.1.2 :tada:
The release is available on:

5.1.2
GitHub release

Your semantic-release bot :package::rocket:


Can't install latest release

Hello,
i can't install latest release (0.3.1) on A6000. Error code:100.
The release 0.3 installed w/o problem.
Regards,
Istvan

I had a problem with the signature, now it works again.

Thanks for the info


have tuned on error checking for tariffs, but relaxed for older accounting tariffs which I want to deprecate

Merged into aws-eb-test branch for review


chore: refactor docs prepare for open source

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


how  to use set, get or push for child and nested data?  I want to make tree in database.

You must find the answer and question on another topic in recent. I got the same question and I found the topic that nearly means of your question. https://github.com/FirebaseExtended/firebase-arduino/issues/325
Firebase.setFloat("/data/VAL1", 50.0);

You must find the answer and question on another topic in recent. I got the same question and I found the topic that nearly means of your question. #325
Firebase.setFloat("/data/VAL1", 50.0);

Yeah that doesn't really get into it for me. Im just trying to push to a nested array. Have tried to use @ViewChildren decorator to import the HTML  data into the typescript file. I get a bunch of html that Im not sure how to work with over there though, I just want objects and arrays and the same as I put in to work with the same way! Is this not a thing?


Inconsistent with the naming after change

https://github.com/OTRF/OSSEM-CDM/blob/dacbc880b04e9b8ca0ae07b42614c1e0f9bcc8bf/schemas/entities/registry.yml#L48
The original registry fields are appended with "_modified" to reflect the value before change. However the fields "registry_value_name_modified" and "registry_value" do not keep this convention.

Please review the changes in the following commit. Let us know if you have any questions. We can discuss it in our next community meeting.


Add repobeats to README.md

Motivation for this change
Add some extra eye candy with insights for repo from repobeats.axiom.co
This is how it would look like

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 wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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

[ ] Fits CONTRIBUTING.md.

Hm, I don’t think we want to add advertising for products to our repository.

Sorry, this is just a copy+paste advertising pr going through the top repos on github, closing
https://github.com/microsoft/vscode/pull/136496
https://github.com/hashicorp/terraform/pull/29886

We can remove the footers if that is a problem


Options to roll empty logs and log trimming

Added 2 options:

proxy.config.log.rolling_allow_empty - ability to roll empty logs
(i.e. rolling logs without traffic)
proxy.config.log.rolling_max_count - trimming logs to a certain
number of rolled files on each rolling
More info and use-cases in records.config.en.rst and rotation.en.rst.

[approve ci Clang-Analyzer]

[approve ci clang-analyzer]

[approve ci autest]

[approve ci autest]

[approve ci autest]

@bryancall, @dyrock, @mlibbey is there anything else I could address ?

Thank you Bryan! Merging...
@mlibbey, @dyrock thank you for your reviews as well!

This has merge conflicts, and we'll need a new 8.1.x PR. Also, feel free to recommend / suggest other PRs that this depends on, such that it makes the back porting easier.

Created PR #6553 to resolve the cherry-pick/merge conflicts.

This was back ported and merged into 8.1.0 release.


Partial regional results

This PR makes it possible to fetch regional analysis results when the analysis is not finished yet. In discussion with @trevorgerhardt we came to the conclusion that this would be useful.
The existing endpoint for complete results at "/api/regional/:_id/grid/:format" will detect whether the analysis is complete or incomplete, and will return the grid directly if it's incomplete, otherwise it returns a "wrapped URL" redirect to s3.
This will require changes to the UI since unfinished results are streamed back from a file immediately, not as a redirect. It would also be possible to just have two different HTTP endpoints, one for finished and one for unfinished results.
I am pushing this branch for preliminary review and feedback from @trevorgerhardt, so the branch is not forgotten. I can update the description with more detail once we get a chance to talk about it. It probably needs a little more work before it's really usable.
This PR also moves GridResultAssembler and SelectingGridReducer into the backend from R5 since they are never used directly in R5, and are essentially part of backend operation.
It also removes the ResultAssembler objects when a job is complete - previously it seems they were left in memory forever.

Codecov Report

Merging #181 into dev will decrease coverage by 0.33%.
The diff coverage is 1.66%.

@@             Coverage Diff              @@
##                dev     #181      +/-   ##
============================================
- Coverage     18.88%   18.55%   -0.34%
- Complexity       72       88      +16
============================================
  Files            58       60       +2
  Lines          2160     2555     +395
  Branches        195      258      +63
============================================
+ Hits            408      474      +66
- Misses         1733     2062     +329
  Partials         19       19

Impacted Files
Coverage Δ
Complexity Δ

...c/main/java/com/conveyal/taui/util/WrappedURL.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...conveyal/taui/analysis/RegionalAnalysisStatus.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...java/com/conveyal/taui/analysis/broker/Broker.java
12.57% <0%> (-0.41%)
4 <0> (ø)

...n/java/com/conveyal/taui/SelectingGridReducer.java
0% <0%> (ø)
0 <0> (?)

...in/java/com/conveyal/taui/GridResultAssembler.java
0% <0%> (ø)
0 <0> (?)

...l/taui/controllers/RegionalAnalysisController.java
8.75% <6%> (-1.66%)
2 <0> (ø)

...m/conveyal/taui/controllers/GraphQLController.java
57.89% <0%> (-2.11%)
3% <0%> (+1%)

...va/com/conveyal/taui/models/AbstractTimetable.java
2.94% <0%> (-0.77%)
1% <0%> (ø)

...ava/com/conveyal/taui/models/ModificationStop.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...java/com/conveyal/taui/models/AnalysisRequest.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

... and 9 more

Continue to review full report at Codecov.

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

Based on recent discussion with @trevorgerhardt and @ansoncfit this works the way we want it to - a single endpoint that returns a redirect code with application/json (if the job is finished) or a 202 with application/octet-stream if the job is still running, with partial results. Ready for review and merge.

Currently you'll get a 302 redirect with type text/plain for completed jobs, and a 200 OK with type application/octet-stream for incomplete jobs. This does allow distinguishing between them but it's kind of weird to give the "normal" OK status code when the job isn't finished. We could change it to 206 but that's kind of abuse of notation. Practically speaking, it should work in current form.

The partial results fetching works in local testing. I get an ACCESSGR file while the analysis is running, and I get a 404 once I've deleted the job. I can't test S3 redirects because my completed local analyses are not uploading to S3 (region weirdness), but it appears to work exactly like before so should be good.
One thing I notice is that we're always sending URLs ending with /grid?redirect=false then returning redirects anyway. Does anyone know what this boolean redirect parameter is for? It's ignored in the backend code.

This PR's branch is now caught up with dev, so now includes proxy-content-type. We should test this branch on staging.


serve web-console even if router management proxy is not enabled

This PR modifies the router to always serve the web-console, regardless of whether or not the management proxy is enabled (@vogievetsky is planning on adding a graceful degradation mode to the Druid web-console).

https://github.com/apache/incubator-druid/pull/8796 should me merged first

This is great! With our powers combined the web console will be unstoppable! 👍


⚠ Bofrost.at has degraded performance

In d3439c2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2099 ms

Resolved: Bofrost.at performance has improved in f642057.


Changed WIN32 to _WIN32

Changed WIN32 to _WIN32 because MSVC doesn't define WIN32 or WIN64.

@googlebot I signed it!


Getting 'Failed to parse source map from ...' warnings on CRA 5.0.1

Thanks for the great library!
This is not a breaking issue for me but I had to post this as an issue since there is no discussions tab in the repo.
Using stdnum-js latest version with CRA v5.0.1 by importing import { stdnum } from 'stdnum'; and getting a bunch of warnings, for ex.:
WARNING in ./node_modules/stdnum/lib/esm/ro/cnp.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '.../node_modules/stdnum/src/ro/cnp.ts' file: Error: ENOENT: no such file or directory, open '/Users/buraktilek/projects/application-frontend/node_modules/stdnum/src/ro/cnp.ts'

Is this due to CRA or due to the library I wonder 🤔, much appreciated if you can provide some answer, cheers!

Thanks for the report. It'll be a little bit until I can dig into this in some detail but is very weird.
Can you provide your tsconfig.json file for reference since I'm assuming that that might be part of the source of the "error".  Or if you have any other babel settings of note.

Hey @koblas, thanks for checking! Here is my tsconfig: (There is no custom babel config)
{
  "compilerOptions": {
    "target": "es6",
    "module": "esnext",
    "outDir": "build",
    "rootDir": "src",
    "strict": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "allowSyntheticDefaultImports": true,
    "useUnknownInCatchVariables": false,
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react",
  },
  "include": [
    "src"
  ],
  "exclude": [
    "node_modules"
  ]
}

This might be relevant -> https://github.com/facebook/create-react-app/pull/11752
**Also if you don't have time and this happens to be a fault on lib side I'd like to contribute if I can, thanks!


Add Ability to edit unkown nodes

Maybe basic Hex editor or at least import export of node data

maybe use https://www.nuget.org/packages/Be.Windows.Forms.HexBox/


PR#7 Fix - Added Support for Auth URL Params + Test Fixes

Contributions from Serhii Holovashchuk
https://github.com/kinde-oss/kinde-flutter-generator/pull/7
Explain your changes
Fixed config.yaml -- Added reference for auth_url_params.dart
Fixed failing tests on flutter test in generated kinde-flutter-sdk:

Added test value test_org_name to test createOrganization
Added test value to test_user_id to test updateUser

Checklist

[X] I have read the “Pull requests” section in the contributing guidelines.
[X] I agree to the terms within the code of conduct.

Here's the documentation for Auth URL Params for the Flutter Integration docs at https://docs.kinde.com/developer-tools/sdks/native/flutter-sdk/
https://towering-dumpling-aa8.notion.site/Kinde-Auth-Params-URL-Docs-c9e6097c1f9d41b78194cfee842327a2?pvs=4


Support cloud regions with multiple clusters in the docs

This PR updates the existing InfluxDB Cloud URL functionality to support regions with multiple clusters.
(Don't merge until the new AWS us-west-2-2 region is live)
Updated modal

Updated Cloud regions page

[x] Rebased/mergeable

Looks good to me.  Thanks.


[DRAFT] Adds test for RadioButton

This PR adds tests mentioned in this issue Tests #957
NOTE: This is still a work in progress.
Test Completed Checklist

[ ] Flyouts
[ ] ComboBox
[ ] NumberBox
[ ] PasswordBox
[ ] TextBox
[ ] DatePicker
[ ] TimePicker
[ ] Card
[ ] CommandBar
[ ] ContentDialog
[ ] ListTile
[ ] ProgressRing
[ ] ProgressBar
[ ] Tooltip
[ ] TabView
[x] RadioButton
[ ] SplitButton
[ ] InfoBadge

Pre-launch Checklist

[ ] I have updated CHANGELOG.md with my changes
[x] I have run "dart format ." on the project
[ ] I have added/updated relevant documentation

Wow! Thank you for your efforts, I really appreciate it. Looking forward to it

Wow! Thank you for your efforts, I really appreciate it. Looking forward to it

Thanks @bdlukaa I will keep on adding more test cases.

Hey @foxtrotravi, any news about this?

Hi @bdlukaa I have stopped working on this. Can you please take over this or assign someone else.


Laravel Install

Hey guys, and thanks in advance.
I did the composer install.. No issue there.. But Laravel only allows classes to run in a provider/facade method, in their own namespace.
Do you have any laravel instructions?

Hey Bobby,
I'm afraid we don't have instructions specific to Laravel! Having said that, the ActiveCampaign class (and others here) are not in any declared namespace, so you should be able to reference them like new \ActiveCampaign(...) from within Laravel.
Let us know if you're still running into problems!

But Laravel only allows classes to run in a provider/facade method, in their own namespace.

That's incorrect.
Here's an example of how to create a service provider for this class...
php artisan make:provider ActiveCampaignProvider

namespace App\Providers;

use App\Contact;
use Illuminate\Support\ServiceProvider;

class ActiveCampaignProvider extends ServiceProvider
{
    /**
     * Indicates if loading of the provider is deferred.
     *
     * @var bool
     */
    protected $defer = true;

    /**
     * Bootstrap the application services.
     *
     * @return void
     */
    public function boot()
    {
        // --
    }

    /**
     * Register the application services.
     *
     * @return void
     */
    public function register()
    {
        $this->app->singleton('ActiveCampaign',  function($app) {
            $config = $app['config']['services']['activecampaign'];
            return new \ActiveCampaign($config['url'], $config['key']);
        });
    }

    /**
     * Get the services provided by the provider.
     *
     * @return array
     */
    public function provides()
    {
        return [\ActiveCampaign::class];
    }
}

Add this to config/services.php
    'activecampaign' => [
        'url' => env('ACTIVECAMPAIGN_URL'),
        'key' => env('ACTIVECAMPAIGN_API_KEY')
    ],

Then add those values to your .env file.
Now you can reference the singleton elsewhere in your code with something like this...
$ac = app('ActiveCampaign');

Simple example for adding a new contact
public function addContact(array $newContactData, \ActiveCampaign $ac)
{
    return $ac->api('contact/add', $newContactData)->success;
}

$ac will automatically be injected by Laravel's IOC container; it will be the singleton that you created in the ActiveCampaignProvider.
This is all Laravel 101. You might consider perusing the docs a bit and familiarizing yourself with Laravel a bit more.

Thanks @QWp6t . One other step I needed to take to get this to work was to add this line to the 'providers' array in config/app.php: App\Providers\ActiveCampaignProvider::class,

Thanks @ryancwalsh  and @QWp6t. This works well!


Better Error Handling after 1.5 node release

So in 1.5 the error logs will be lot more descriptive:
{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32008,
    "message": "Invalid Deploy",
    "data": "deploy parameter failure: account b05e28fd7d00c2de89ce00b4ded5dad29076e7e020b2086af02dc7703eb216c5 does not exist at prestate_hash: 63cf..eff9"
  }
}

And currently SDK is only showing message when in fact data should be also visible to user.
This will probably mean less questions from the community :)

the detailed error message can be logged like this
try {
      const roothash = await client.getStateRootHash();
      const toPublicKey = Keys.Ed25519.new().publicKey;
      await client.getBlockState(roothash, toPublicKey.toAccountHashStr(), []);
    } catch (error) {
      if (error instanceof JSONRPCError) {
        console.log(error.name);
        // Error

        console.log(error.data);
        // ValueNotFound("Failed to find base key at path: Key::Account(6c5fc23f3cb18c877d743e6d50f7c660bdfca947da2abaca4cfe778dbf104b17)")
      }
    }


ProjectConf: support files/directories/etc... based run

cont #47
With #47, reviewdog behavior can be configured by reviewdog.yml.
However, we cannot specify changed files, directories, or whatever with reviewdog.yml.
Example without reviewdog.yml:
$ vint $(git diff --name-only master | grep '.vim') | reviewdog -diff="git diff master" -efm="%f:%l:%c: %m"
autoload/vital/__vital__/Data/String.vim:9:11: Prefer single quoted strings (see Google VimScript Style Guide (Strings))

Supporting to pass changed files as an environment variable is simple and useful.
FILES="file1\nfile2\nfile3"

cmd: <lint cmd> $(echo $FILES | grep '.go')


NoneType' object has no attribute 'inference_sft

I get this error: NoneType' object has no attribute 'inference_sft
Also there was a message about 'no lightning' ... as if not everything needed was installed.
Best regards, Ruud.

try to reinstall torch2.3+cuda11.8


Digitalocean DNS01 Challenge Provider - Could not find the start of authority

Describe the bug:
While trying to get a wildcard certificate from letsencrypt using the dns challenge with the digital ocean provider, I get:
I0222 21:38:32.618977       1 dns.go:89] Presenting DNS01 challenge for domain "fakedomain.com" E0222 21:38:32.621899       1 controller.go:207] challenges controller: Re-queuing item "default/wildcard-certificate-2142438036-0" due to error processing: Could not find the start of authority
Expected behaviour:
Certificate is issued correctly.
Steps to reproduce the bug:
Apply digital ocean acces token secret:
apiVersion: v1
kind: Secret
metadata:
  name: digitalocean-dns
  namespace: cert-manager
data:
  access-token: *****************************

Apply cluster issuer:
apiVersion: certmanager.k8s.io/v1alpha1
kind: ClusterIssuer
metadata:
  name: letsencrypt-staging
spec:
  acme:
    server: https://acme-staging-v02.api.letsencrypt.org/directory
    email<EMAIL_ADDRESS>
    # Name of a secret used to store the ACME account private key
    privateKeySecretRef:
      name: letsencrypt-staging

    # ACME DNS-01 provider configurations
    dns01:

      # Here we define a list of DNS-01 providers that can solve DNS challenges
      providers:

        - name: prod-dns
          digitalocean:
            tokenSecretRef:
              name: digitalocean-dns
              key: access-token

Apply certificate:
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: wildcard-certificate
  namespace: default
spec:
  secretName: wildcard-tls
  issuerRef:
    name: letsencrypt-staging
    kind: ClusterIssuer
  commonName: '*.fakedomain.com'
  dnsNames:
  - fakedomain.com
  acme:
    config:
    - dns01:
        provider: prod-dns
      domains:
      - '*.fakedomain.com'
      - fakedomain.com

Anything else we need to know?: Im using minikube, It has been 48 hours since I changed the nameservers to point to digital ocean dns service.
Environment details::

Kubernetes version: v1.13.3
Cloud-provider/provisioner: minikube
cert-manager version: v0.6.6
Install method: static manifests

/kind bug

I am having a similair issue with minikube 1.0.0  I get
I0426 20:21:35.366903       1 dns.go:89] Presenting DNS01 challenge for domain "xxxxx.xxx"
E0426 20:21:35.375082       1 controller.go:207] challenges controller: Re-queuing item "cert-manager/xxxxx-xxx-certificate-3478766445-0" due to error processing: Could not find the start of authority

Any ideas on how to debug?

Raised https://github.com/kubernetes/minikube/issues/4167 to help resolve my issue, it may help others too.
After applying the change I was able to get my Windows Minikube to issue certificates.


HTTP/3 switch to HTTP/2 after refresh

Hello and thank you for this tutorial.
After installation and configure nginx, HTTP/3 work fine. But after refresh, HTTP/3 switch to HTTP/2.
/et/nginx/nginx.conf
user www-data;
worker_processes auto;

error_log /var/log/nginx/error.log notice;
pid /var/run/nginx.pid;

events {
    multi_accept       on;
    worker_connections  65535;
}

http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

    access_log  /var/log/nginx/access.log  main;
    error_log /var/log/nginx/error.log warn;
    client_header_buffer_size 8k;
    large_client_header_buffers 8 64k;

    aio threads;
    aio_write on;

    brotli on;
    brotli_comp_level 11;
    brotli_types application/atom+xml application/javascript application/json application/rss+xml application/vnd.ms-fontobject application/x-font-opentype application/x-font-truetype application/x-font-ttf application>

    gzip on;
    gzip_vary on;
    gzip_proxied any;
    gzip_comp_level 6;
    gzip_types application/atom+xml application/javascript application/json application/rss+xml application/vnd.ms-fontobject application/x-font-opentype application/x-font-truetype application/x-font-ttf application/x>

    more_clear_headers server;

    quic_gso on;
    quic_retry on;

    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    server_tokens off;

    ssl_protocols TLSv1.3;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DH>
    ssl_early_data on;
    ssl_ecdh_curve X25519:P-256:P-384;
    ssl_session_timeout 1d;
    ssl_session_cache shared:SSL:10m;
    ssl_stapling on;
    ssl_stapling_verify on;
    ssl_session_tickets on;

    resolver <IP_ADDRESS> <IP_ADDRESS> [2606:4700:4700::1111] [2606:4700:4700::1001] <IP_ADDRESS> <IP_ADDRESS> [2001:4860:4860::8888] [2001:4860:4860::8844] <IP_ADDRESS> <IP_ADDRESS> [2620:119:35::35] [2620:119:53::53] valid=60s;
    resolver_timeout 2s;

    include /etc/nginx/conf.d/*.conf;
}

/etc/nginx/conf.d/default.conf
server {
    listen 80;
    server_name server.exemple.com;
    location / {
        return 301 https://server.exemple.com$request_uri;
    }
}

server {
    listen              443 ssl http2;
    listen              443 http3;
    listen              [::]:443 ssl http2;
    listen              [::]:443 http3;

    server_name server.exemple.com;

    root /usr/share/nginx/html;

    add_header Alt-Svc 'h3=":443"; ma=3600' always;

    ssl_certificate /etc/letsencrypt/live/server.exemple.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/server.exemple.com/privkey.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/server.exemple.com/chain.pem;
    ssl_stapling_file /etc/letsencrypt/live/server.exemple.com/ocsp.resp;

    access_log /var/log/nginx/server.exemple.com-access.log main;
    error_log /var/log/nginx/server.exemple.com-error.log warn;
}

Others informations :

OS : Debian 11
Same issue with an other site + Cloudflare (HTTP/3 Quic activate) on the same server
Browser support HTTP/3

Best regards

Same issue with an other site + Cloudflare (HTTP/3 Quic activate) on the same server

If the same issue also occurs on sites with Cloudflare, it should be your client's problem.

Thank you for the feedback.
I try to reproduce all installation with add_header Alt-Svc 'h3=":443"; ma=3600, h3-24":443"; ma=3600, h3-23=":443"; ma=3600, h3-29=":443"; ma=3600' always; on other server. The result :

1st load, the protocol HTTP/3 work fine
2nd refresh with CTRL + F5, the protocol switch to HTTP/2
2nd refresh, normal refresh with CTRL + R, the protocol switch randomly HTTP/2 and HTTP/3 or Only CSS and JS use HTTP/3
3rd refresh, normal refresh with CTRL + R, the protocol HTTP/3 work fine

I admit that I'm lost on the source of the problem. Do you have an explanation ?

Can you reproduce that on my site (https://ononoki.org)? If not, I'm sure the issue comes from your client.

Can you reproduce that on my site (https://ononoki.org)? If not, I'm sure the issue comes from your client.

I reproduce the same step on https://ononoki.org and the result is the same. If the problem comes from the client, can you give me the version of your client so that I can test? Thanks.

I'm using Firefox Developer Edition 103.0b9 and Chromium 103.0.5060.68, and I do not encounter the issue.

I'm using Firefox Developer Edition 103.0b9 and Chromium 103.0.5060.68 on Windows 10 x64, and I do not encounter the issue.

Thank you for this information and after try, I confirm, the issue comes from the client.

Thank you for the feedback.
I try to reproduce all installation with add_header Alt-Svc 'h3=":443"; ma=3600, h3-24":443"; ma=3600, h3-23=":443"; ma=3600, h3-29=":443"; ma=3600' always; on other server. The result :

1st load, the protocol HTTP/3 work fine
2nd refresh with CTRL + F5, the protocol switch to HTTP/2
2nd refresh, normal refresh with CTRL + R, the protocol switch randomly HTTP/2 and HTTP/3 or Only CSS and JS use HTTP/3
3rd refresh, normal refresh with CTRL + R, the protocol HTTP/3 work fine

I admit that I'm lost on the source of the problem. Do you have an explanation ?

i resolve same problem with this:
listen 443 http3 reuseport;
listen 443 ssl;
also add to location:
add_header Alt-Svc 'h3=":443"; ma=3600';


Fix various bugs in modf, add

First commit is identical to the existing PR.

I just had some tea and took a healthy dose of nyquil, so apologies if my comment(s) were wrong.
thanks for the changes. very thankful to have another set of eyes going over the code!

First commit is identical to the existing PR.

does this mean I can close the other one?


[ZEPPELIN-5857] Bump gRPC and protobuf to support build on macOS M1 chips

What is this PR for?
I suppose this upgrade will not introduce compatibility issue, see details discussion about version requirements and compatibility https://github.com/apache/incubator-uniffle/pull/13
What type of PR is it?
Improvement
Todos

[ ] - Task

What is the Jira issue?
ZEPPELIN-5857
How should this be tested?
Build on my M1 mac.
Screenshots (if appropriate)
before

after

Questions:

Does the licenses files need to update? Yes, and updated.
Is there breaking changes for older versions? No.
Does this needs documentation? No.

I've checked the link you added but it's a bit different because we are using another maven plugin so I cannot reproduce the error like you. Could you please check it? BTW, I like the approach you suggested but we'd better change more to make them the same. Could you please check and modify them?

@jongyoul are you using x86 JDK w/ Rosetta? the native aarch64 JDK should fail.
➜  apache-zeppelin git:(ZEPPELIN-5857) java -version
openjdk version "1.8.0_332"
OpenJDK Runtime Environment (Zulu <IP_ADDRESS>-CA-macos-aarch64) (build 1.8.0_332-b09)
OpenJDK 64-Bit Server VM (Zulu <IP_ADDRESS>-CA-macos-aarch64) (build 25.332-b09, mixed mode)

typically, the native aarch64 JDK is 2x faster than x86 JDK w/ Rosetta (testing by compiling Apache Spark and Apache Kyuubi)

I tested it failed with aarch64 jdk. Thank you for letting me know.

@jongyoul this is ready for review, I believe the CI failure is irrelevant.
I can success build the project(except to frontend modules) using Java8 aarch64 on M1 mac now.


Refactor for reuse

The only user-visible change here is fixing some error messages.
Otherwise, this just makes a few members public in a way that allows experimenting with reuse from other code.
Eventually, the code may end up in source_gen – but we'll take our time.

@natebosch – fixed copyright year...


[fluidsynth] no absolute paths

For #20469

arm64 fails with
CMake Error at CMakeLists.txt:13 (project):
  Generator

    Ninja

  does not support platform specification, but platform

    Win32

  was specified.

I have no clue ...


Update rails to <IP_ADDRESS> due to vuln

Description
Dependabot flagged a high severity vulnerability: https://github.com/SaraAlert/SaraAlert/security/dependabot
Update Rails to 6.1.4: https://github.com/rails/rails/releases/tag/v6.1.4

if you remove test/system/roles/enroller/enrollment/form_validator.rb:133 the test seems to work according to the new page flow. Would like someone else to confirm that is the correct thing to do.


Composite bar charts should be supported

Description
Composite bar charts (sometimes also call stacked bar charts) are charts where each bar displays multiple data points stacked in a single row or column.
There are situations where no other diagram type can be used to express the intended conclusion. Also the use of 2 diagrams with identical X Axis but different Y axis would not be appropriate. Therefore composite bar charts are rellay needed!
Refer to https://www.goteachmaths.co.uk/composite-bar-charts/
To me it is not quite clear if Mermaid supports this type of diagram at the moment: https://github.com/mermaid-js/mermaid/issues/4269#issuecomment-1868982956

Thanks @camueller how would you expect to define the payloads in the msg for such a chart?

This doesn't really matter to me since I can use a Javascript node for any kind of data transformation.
BTW: Since mermaidcurrently has no support for composite charts I implemented it yesterday and today and created a PR for it: https://github.com/mermaid-js/mermaid/pull/5167
Looking at the other PRs I don't expect an response soon althought I would like it.
If you look at this PR you can see the syntax I used for dataset of composite charts: https://github.com/mermaid-js/mermaid/pull/5167/files#diff-15b2d25f41bde2a210201a02bcfd09ba323c9e85136ae309d684aa6c4bcd4dea
I watched your Video about Dashboard 2.0 ( https://www.youtube.com/watch?v=7GTHYzRpQ9M ) and was surprised about your switch to Vue.js. Since 2018 I'm working as developer for one of (or the?) largested Vue.js projects in Europe :-)

Requested again here: https://discourse.nodered.org/t/stacked-bar-graph/89164


bug(button): Icon Button Focusing Inconsistent

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
This bug can be seen on the documentation page of Menu component. If you go to https://material.angular.io/components/menu/examples and scroll down to "Menu with icons" section, the icon button will sometimes be left focused after opening and closing the menu. See below:
https://github.com/angular/components/assets/4698762/8261e82f-a51d-481d-a45b-467f3571429e
One thing to note, I'm seeing this issue only with trackpad taps, not with trackpad clicks. See below:
https://github.com/angular/components/assets/4698762/d818e059-1e3f-4b05-80ea-e70e12e06e36
Reproduction
StackBlitz link: https://stackblitz.com/edit/stackblitz-starters-fntbkn?file=src%2Fmain.ts

Steps to reproduce:

Click on the icon button to open the menu
Click again on the icon button to close the menu
Move the cursor away from the button
Repeat

Expected Behavior
The focus on the icon button should be gone on hovering away from the button.
Actual Behavior
The focus stays on the button.
Environment

Angular: 17.2.1
CDK/Material: 17.2.0
Browser(s): Chrome, Firefox and Safari latest
Operating System (e.g. Windows, macOS, Ubuntu): macOS 12.7.3

@karmasakshi I believe for accessibility reasons, the correct behavior is for focus to return to the button after closing the menu.
The unexpected behavior here would be that closing the menu does not return focus to the button

Hello folks, this may be a systemic issue with Overlay and maybe not only an issue with button and menu components. I noticed in chrome debugger that document.activeelement is the menu trigger when closing popup, but it doesn't display the focus state. I also noticed that when closing with mouse, activeElement changed to body before changing to trigger.
-Zach


Adopting JSON API v1 spec

Are there any plans for improved support for the JSON API spec? It would be awesome if I could simply specify a resource by its attributes and then get a generated JSONAPI v1 compliant schema for the common REST operations from Apiary.

@jonnedeprez Yes! There is a plan for it. However this is more in the jurisdiction of API Blueprint itself as it needs the information about available affordances (links in JSON API). See https://github.com/apiaryio/api-blueprint/issues/291
Please feel free to comment, bump or suggest improvements to the idea! (Or even implement it :smile: )


always use ChunkHeaderFormat::Empty on non-first chunks

Thanks for the great library!
Streaming into Twitch was breaking when a payload exceeded the max chunk size. Changing this chunk format logic seemed to fix it.

Thanks for this!  Glad someone's getting use out of the library :D
Merged your fix in and published 0.3.4 to crates.io with the fix.

Awesome thanks for the quick publish :)


MAISTRA-2060 Point to Red Hat Jira for issues

Those fixes are better going in another PR

Oops. That wasn't intended. Reverting

Those fixes are better going in another PR

Oops. That wasn't intended. Reverting


better logos

Nice! The project logos should also be white in dark mode, I think:

Nice! The project logos should also be white in dark mode, I think:

That's a good point, we should have white version of them at some point.
But my PR was mainly about having actual SVG logos instead of a vectorization ;-)


exiv2: enabling tests for real

Motivation for this change
Fixes #67453, which disabled all tests by mistake, given I have assumed doCheck defaults to true if tests are found.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nix-review --run "nix-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.

Looks like darwin is stuck.
@GrahamcOfBorg build exiv2

@worldofpeace now, the tests are failing on darwin instead of aarch64.

@GrahamcOfBorg build exiv2

@GrahamcOfBorg build exiv2

@GrahamcOfBorg build exiv2

@GrahamcOfBorg build exiv2

Ok, last try and I disable the tests of darwin :)

@GrahamcOfBorg build exiv2
Ok, last try and I disable the tests of darwin :)

@GrahamcOfBorg build exiv2


Cannot open nbformat 2 or 3 notebooks

Bug: Notebook Editor
Note: this is reopening #7731 which is locked.
Steps to cause the bug to occur
Try opening a Jupyter notebook in NBFormat v2 or v3.
Actual behavior
File is closed immediately and an error notification is shown:
test2.ipynb is not a valid notebook file. Check the file for correct json.
Expected behavior
Either open the file in the notebook editor (preferred) or offer the option of opening the file as JSON. As is, there is no way to open this file in VSCode at all if the Python extension is installed.
Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running: N/A
Extension version: 2020.6.90262
VS Code version: 1.45.1
Setting python.jediEnabled: false
Setting python.languageServer: Jedi
Python and/or Anaconda version: 3.6.10
OS: Linux (Debian):
Virtual environment: conda

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

@kynan, thanks for bringing it back up. We'll discuss it in our next triage.

Thanks for the feedback! However, we don't have plans on adding this functionality at this time.


add class for dropdown menus

like the menu itself

they're already marked with blocklyDropDownDiv. What we need is category classes.

pshh, you can't expect the user to know that blocklyDropDownDiv is a dropdown.
Also, make sure t works with the horizontal broadcast dropdown


Add Grafana dashboard for Embedded Infinispan

Closes #330
There are three types of rows on the dashboard:
Global statistics - showing info about all caches globally:

Local cache stats - local caches are used for caching objects from the database or LDAP, therefore contain hit ratio:

Distributed cache stats - distributed caches are used for storing data like sessions or login failures:

@mhajas we might have fix the dashboard for the openshift deployment, do you want to try and take this up as a separate ticket ?

and on minikube I can see the metrics coming through, except for this widget, do you observe the same @mhajas ?

@kami619 I just realized that what I mentioned previously about not the work cache is not correct, it is used even without remote caches. Why it was not visible is that I forgot to enable statistics for that cache :see_no_evil:
@ahus1 I looked into how we configure metrics in Keycloak and we need some changes in dist to create some env variable from metrics-enabled option so we can consume it in the cache config file. I am wondering whether we need to do it in this version or if we can create a follow-up issue in Keycloak and then adjust kcb for that. WDYT?


Looking forwards to RestEase 2

At some point, I'd like to move to RestEase 2. There are two main things want to achieve:

Make use of source generators
Make Json.NET optional

This issue is a brain dump, and a place to record my thoughts as they evolve.
Source Generators
Source generators are coming. They will essentially let NuGet packages hook into the build system, and insert their own code. This is a perfect fit for something like RestEase, where we can generate the implementation of a user's interface at compile-time instead of at runtime.
However, I don't want to remove support for the current IL emission approach.
As I understand it, the options available are:

Let the user define partial classes with partial methods instead of interfaces, and generate the other part of the partial class.
Keep the current approach of letting the user define an interface, and generate an implementation for that.

Partial classes have some appeal: they would let users write:
partial class MyApi
{
    [Get("foo")]
    partial Task FooAsync();
}

var api = new MyApi("https://api.example.com");

which avoids needing to use reflection. It also means the user can add their own concrete helper methods. However, there are some downsides: users like being able to define interfaces from an abstraction standpoint, and it would make the README significantly more complex (each code sample needs duplicating).
Continuing to use interfaces shouldn't be too bad: we can emit an assembly-level attribute saying which generated type implements which interface, which we can pick up on at runtime.
Another consideration is what will happen if the source generator isn't working. With a partial class, the compilation will fail. With interfaces, we simply won't get an implementation generated, and we won't know until runtime. I don't know whether this might be an issue in practice.
We'd also want to keep the RestClient.For syntax for interfaces, presumably. However, I'd want both source generation and runtime IL generation to be opt-in, and allow both to run side-by-side, so RestClient would need to be defined in a central place, and do nasty things to make sure that it did runtime generation if necessary, and if possible. That could cause problems.
Identifying which partial classes / interfaces need implementations generated could be tricky: we don't currently have a guaranteed type-level attribute, so we'd have to go looking through all methods of all types.
Json.NET
Json.NET is currently a mandatory dependency. That makes the simple case simpler, but means people who don't want to use it still have to take a pointless dependency.
This never used to be much of a problem: most REST APIs are json, and everyone used Json.NET. However System.Text.Json is now a thing, and forcing people who want to use System.Text.Json to take a dependency on Json.NET is wrong.
However, we still need to support people who want to use Json.NET.
Backwards compatibility
Major version bumps are a good excuse to make breaking changes. I'm OK with breaking changes in principle, but they must be compile-time breakages (I don't want things failing only at runtime), and there should ideally be guidance on how to solve it (e.g. use of Obsolete attributes).
Changes
I want to move all common types (attributes, RequestInfo, Requester, etc) to a RestEase.Core assembly. This is necessary to let source generation and runtime IL generation work side-by-side. These would stay in their current namespaces. It's unclear what would happen to RestClient.
Currently the various serializers and deserializers are separate properties on RestClient. In order to let the user opt into the Json.NET (de)serializers easily, these would have to be grouped on a new object. Then the user could do new RestClient() { Serializers = new JsonNetSerializers() } or similar. The JsonSerializerSettings would have to be removed from RestClient as well.
We'd need a RestEase.Json.NET NuGet package which contains the Json.NET (de)serializers.
Presumably we'd want two more NuGet packages, one for the source generators and one for the runtime IL emission (they can't be the same package, because the source generators shouldn't have a dependency on ILBuilder).
It's unclear what should happen to the current RestEase NuGet package. Maybe this should continue to contain the IL emission code, or maybe it should be a backwards-compatibility meta-package which references the IL emission NuGet package, as well as the RestEase.Json.NET NuGet package.
Other Changes
It's also a chance to tackle #19, and not assume that responses are always strings. This needs more thought.

They've introduced preview of Source Generators

I've been mulling over this further, and I'm leaning in favour of keeping things as a single package. This would include the source analyzer and the S.R.E implementation. The S.R.E would be used as a fallback in case the source generator fails, or isn't available (on platforms which support it).
This makes life a lot simpler: people don't have to make informed decisions at the point of installing the library (which is a hurdle). They install the RestEase package, and if their toolchain supports source generators, they get nice compile-time error messages; if it doesn't, things work as before (except on Xamarin.iOS, where they'll get a nice exception message pointing them at the docs for source generatosr).
This does mean we'll ship a S.R.E implementation to platforms which don't support it, but that's probably OK. .NET Standard 2.1 includes S.R.E (and the latest Xamarin versions target .NET Standard 2.1), so we won't have an extraneous dependency on the S.R.E NuGet package
There is the thorny issue of what to do about the Newtonsoft.Json dependency, though. Intuitively, we should target System.Text.Json by default, but 1) that's only supported on some platforms, so we'll get different behaviour depending on the platform, and 2) that ends up going down the route of silently switching people from Newtonsoft.Json to System.Text.Json, which is going to break things for some people. Therefore I think we have the following options:

Deprecate RestEase (NuGet supports this now) and switch to RestEase2. The migration notes tell people what to do in order to keep using Newtonsoft.Json (whatever that may be).
Detect whether Newtonsoft.Json is loaded and automatically switch to it. I don't like this at all: installing an unrelated package will silently change the behaviour of RestEase.
Don't target any json library by default, and force the user to explicitly opt into one. We'd want a nice way to opt into a library, such as an attribute on the interface (which is something I've been thinking of anyway: the current approach of putting that config on the RestClient removes it from the code which actually uses it). We would need logic to detect when the user is trying to use an interface which needs serializer support (check for method return types which need deserializing; SerializationMethod, etc), and throw a suitably informative error message. We will break some users this way, however.
Something similar to what I was thinking of before: RestEase becomes some sort of compatibility package which references the "main" RestEase NuGet package, and also the Newtonsoft.Json RestEase package. It needs some way to tell the main RestEase package that the Newtonsoft.Json package is available however, and this gets ugly.

A slight evolution: the SourceAnalyzer will be in its own package -- you can't bundle a library and source generator in the same package. The rest will stay the same: I'm planning to ship the S.R.E implementation in the RestEase package, then people can install the RestEase.SourceGenerator package to get the source generator. RestClient will try to get a source generator generated implementation first, then fall back to S.R.E on platforms that support it.
This means that I don't need to cut RestEase 2.0 in order to release the source generator. I do need to add more types to support the soruce generator, so there'll be a minor version bump, but that's it.
I'll open a new issue when the source generator is testing. It's getting there -- ironing out the edge cases. Obviously it won't be released at final until the design of source generators is released, probably with C# 9.

The source generator preview is now out, see #158

The source generator has shipped, as a separate package. This means that it's opt-in (and if there are teething problems, noone's forced to use it). In the future, I'm tempted to have a RestEase meta-package which references a bunch of things, including the source generator.
#170 is probably something that should also be addressed for 2.0.

The SG also means that there's little point in a separate RestEase.Core library: the SG'd code needs to reference lots of RestEase types, and so these need to be available in all assemblies.
The main thing I'd currently like to see in v2 is a nice way of opting into json.net, Polly, etc. Ideally this means some way of adding extension methods into the RestClient.For call, naively something like:
T api = new RestClient(...).UseNewtonsoft(settings).UsePolly(policy).For<T>();

That's nice, but it's a bit wordy, especially if the user's primary way of getting instances of T is calling into RestClient.For directly (i.e. they haven't wrapped it into their own factory). There are two possible approaches I can think of here:

Make the user create and configure a factory which is used to generate instances of T. This raises the barrier to entry a bit though, and requires that the user has a central place to set these sorts of things up, and a way of distributing said factory to all of the places which need RestEase, which isn't necessarily a given.
Do something with attributes

The attributes approach feels nice: an interface which reference models which are inherently either json.net or S.T.J, so configuring this at the interface level makes sense. However it then gets harder for the user to set their own json.net-related options, or pass their own Polly policy, or...
So something like this is unlikely to be flexible enough:
[UseNewtonsoft]
public interface ISomeApi
{
}

Something like this might fly:
[RestEaseFactory(typeof(Factory))]
public interface ISomeApi
{
}

public class Factory : IRestEaseFactory
{
    public RestClient GetClient() => new RestClient(...).UseNewtonsoft(...);
}

That's a bit more headache though, and I don't want newbies to have to add that much boilerplate just to get up and running. I also don't know whether the complexity is worth the effort: maybe everyone who uses RestEase in a complex enough scenario that they need to be configuring it already has DI set up, or is wrapping it up in some sort of factory method.
A hybrid approach, where both are allowed, might make sense (so e.g. public void ConfigureClient(RestClient client) => client.UseNewtonsoft(...) above), with the options from one overriding the options from the other.

I'd also like the use the opportunity to make some breaking changes:

Get rid of [Obsolete] members
string return types are no longer special, and get passed to deserializers. Maybe add an attribute to get a raw string return.

Personally, I'm not a fan of the use of attributes in this way. I prefer to see exactly what's happening at the point of use. For this scenario I like the fluid api style, T api = new RestClient(...).UseNewtonsoft(settings).UsePolly(policy).For<T>();
So long as you have sensible defaults to fallback to then the user can just use RestClient.For as normal unless they require specific non-default behaviour, in which case I think its perfectly reasonable that you need to do a little extra setup work.

Agreed -- the idea with the attributes was to still configure RestClient using that style, but put those method calls in a central place rather than forcing the user to repeat them every time they create a new instance.
So RestEaseFactory (or whatever it's called) would refer to some type, and that type would define a method which contains calls to exactly that same fluid API. A lot like the Startup class in asp.net

There's also the matter that people are publishing libraries containing RestEase interfaces. It might be nice to let them specify what serialization to use with those, rather than making them add documentation telling the user what configuration they need to do.

But on the flip side, as a consumer I would want to choose which JSON library I was going to use.

If you're using models which someone else has written, you'll need to use the same json library as the models are intended for. If they're decorated with json.net attributes, they won't work with S.T.J!

This might also be a good time to drop .NET 5 support and move to .NET 6, since .NET 5 is EOL. Although, I don't even think you'd need a major version to do this.

I don't think there's any need to drop support for older TFMs, unless we need some API which isn't available there? And since we're supporting Framework for the forseeable future that seems unlikely.
Supporting a TFM as a library just means that we don't need any of the APIs from newer TFMs. We'll of course run on whatever runtime the main application is running on.

Is there a way to use RestEase with STJ yet?
I'm trying to implement WebAuthn in a Blazor application using the passwordless Fido2 lib's models, which use STJ attributes and can therefore not use Json.NET as it seems, so I can't communicate the models with the server via RestEase yet.

You can write your own serializer which uses STJ - the only side is you'll bring in json.net as a dependency, even though it's unused.
There's also a third party fork of RestEase on nuget, although I can't vouch for it

Why make a whole new nuget package instead of just increasing the major version? A migration guide will be needed either way, and breaking changes are expected in a major update.

So this topic is 4yr old at this point... is 2.0 in progress? I saw that source generator poc is there, but is that something that is ready to be used in production code?
Finally, is there currently a way to utilize System Text Json with restease? Is that just a matter of somehow implementing a custom serializer or something? Should we expect an update that will allow us to more easily use system.text.json more directly?

You can currently use STJ with RestEase by building your own serializer like this and then telling RestEase to use it like this


Use In-memory SQLite Database for Testing

In order to test our database, I can as a developer create an in memory database using SQLite.
See week 7, 1a)


Delete account v1

Change Log
Extended @studna's work to delete content (note: this is an initial v but we want to later do proper shut downs and clearing of data dirs across the board but that's going to require some refactoring at very core levels).
Todo

Add mocked unit tests

@dmerrill6 @maurycy @perfectmak can you kindly review this again? The change most impactful change is here https://github.com/FleekHQ/space-daemon/pull/219/commits/68e8f40edb32e38d1f3ce9a037d445a89165cb28 and spoke with @dmerrill6 that moving the sync init to where it is now is not the best, so we can decide if that's okay for now or we should tweak it in this PR.


Bower

Hey @jaredreich ,
Anychance you could put this on bower / npm for people to use?
I think it will increase the usage of notie.js
Thanks

Definitely, will do this soon. Thanks for the suggestion!

Little update - someone else just took the npm name 'notie' about a week ago for a different, more obscure module.  We'll see what I can come up with. I can either ask them to change the name or just use notie-js


database: drop the mutex

Without a critical section, we naturally hit a few unimplemented paths when handling concurrent transactions, which is great news! Visiting previously impossible paths already proves that lock-free is able to handle concurrency > 1.
Now, the easy part - fixing all the unimplemented paths and making the Hekaton implementation 100% foolproof.

note: this PR also temporarily drops garbage collection - the previous, naive implementation piggy-backed on the fact that we were under a mutex, and now it makes no sense to keep it

Update: it turned out that we don't hit the todo!() parts of the code, which is worrying. I'm yet to discover why, and my prime suspect is the fact that we still use SkipMap<key, RwLock<value>> under the hood rather than SkipMap<key, value>, since it's enforced by the compiler. Perhaps we still lock, but in a more granular way. If that's the case, replacing all locks with try-locking should work as proof - I'll try that

https://github.com/penberg/mvcc-rs/pull/17 added garbage-collecting mutations assuming that everything happens under a mutex, but in our case it does not anymore! Now the next thing to do is figure out a test case that triggers the bug, and then fix it


Booster vaccination certificate is not combined with the other certificates if the second name is missing

Hi,
I came across some unexpected behavior in the Android app and also saw it in the IOS app: The first two vaccination certificates are combined into one tab, the third certificate is not included in this tab. The only difference between the two 'persons' is the missing second name.
The issue probably originates from the fact that I had to use my passport ('amtlich', with the 2nd name) for the first two vaccinations and only had to show my electronic health card (without the 2nd name, you do not have to state it there) or even only a registration form for the 3rd dose.
I would propose that only the first and last name and the date of birth are checked for determining whether the certificate is from the same person.

Internal Tracking ID: EXPOSUREAPP-10871

Hi @MagnusOstertag,
Thanks for the suggestion. Transferred to wishlist repository. Internal Tracking ID: EXPOSUREAPP-10871
Best wishes, DS

Corona-Warn-App Open Source Team

Same here. Maybe it's possible to implement a manuel merge function for certificates.

@kroerig
I suggest you read thorough #705.

It's solved, nice!

Hi @MagnusOstertag,
thanks for reporting here and your feedback. Best wishes, DS

Corona-Warn-App Open Source Team


Estimate the glass transition temperature

Using the fit of the Vogel-Fulcher-Tamman function, it is possible to get an estimate on when the dynamics reach the point of slowing down enough. This would allow a comparison with other values using the glass transition temperature.

This estimation will be based on the fit in #17, there will also need to be a results file with the resulting estimation.


Added aggregate metrics for timed functions

Changes:

Added NATS-based metric aggregation for each function timed with @timer
Removed CoreWorkflow @timer in favor of support/timer.py @timer
Added 'metrics' object to /status that shows the total time, msg count and average time for each function being timed

Example trace logging output shows elapsed time for each timed function:
2021-05-13 14:33:44,776 - connect.workflows.core - TRACE - Running FhirWorkflow
2021-05-13 14:33:44,776 - connect.workflows.fhir - TRACE - FhirWorkflow.validate: resource type = Patient
2021-05-13 14:33:44,778 - connect.workflows.core - TRACE - FhirWorkflow: incoming message type = <class 'fhir.resources.patient.Patient'>
2021-05-13 14:33:44,785 - connect.clients.nats - TRACE - nats_timing_event_handler: validate() average elapsed time = 0.02258973s
2021-05-13 14:33:44,787 - connect.clients.nats - TRACE - nats_timing_event_handler: transform() average elapsed time = 0.00001578s
2021-05-13 14:33:44,792 - connect.clients.kafka - TRACE - Produced record to topic FHIR-R4_PATIENT partition [0] @ offset 68
2021-05-13 14:33:44,792 - connect.workflows.core - TRACE -  FhirWorkflow persist: stored resource location = FHIR-R4_PATIENT:0:68
2021-05-13 14:33:44,795 - uvicorn.access - INFO - <IP_ADDRESS>:60346 - "POST /fhir/Patient HTTP/1.1" 200
2021-05-13 14:33:44,804 - connect.clients.nats - TRACE - nats_timing_event_handler: persist() average elapsed time = 0.07418847s
2021-05-13 14:33:44,804 - connect.clients.nats - TRACE - nats_timing_event_handler: transmit() average elapsed time = 0.00002680s
2021-05-13 14:33:44,805 - connect.clients.nats - TRACE - nats_sync_event_handler: received a message on EVENTS.sync
2021-05-13 14:33:44,805 - connect.clients.nats - TRACE - nats_sync_event_handler: detected local LFH message, not storing in kafka
2021-05-13 14:33:44,805 - connect.clients.nats - TRACE - nats_timing_event_handler: synchronize() average elapsed time = 0.00015202s
2021-05-13 14:33:44,806 - connect.clients.nats - TRACE - nats_timing_event_handler: run() average elapsed time = 0.09844871s

With the addition of display formatting with format_metrics(), we get the /status output:
{
    "application": "connect.asgi:app",
    "application_version": "0.42.0",
    "is_reload_enabled": true,
    "nats_client_status": "CONNECTED",
    "kafka_broker_status": "AVAILABLE",
    "status_response_time": 0.00172129,
    "metrics": {
        "validate": {
            "total": 0.15420198,
            "count": 10,
            "average": 0.0154202
        },
        "transform": {
            "total": 0.00016522,
            "count": 10,
            "average": 1.652e-05
        },
        "persist": {
            "total": 1.09643579,
            "count": 10,
            "average": 0.10964358
        },
        "transmit": {
            "total": 0.00019121,
            "count": 10,
            "average": 1.912e-05
        },
        "synchronize": {
            "total": 0.00142241,
            "count": 10,
            "average": 0.00014224
        },
        "run": {
            "total": 1.26608157,
            "count": 10,
            "average": 0.12660816
        }
    }
}


Request change in "piper" TAR file naming

REQUEST:
You've recently changed the naming convention of the piper tar files.
From: piper_<amd64/arm64/armv7>.tar.gz
To: piper_linux_<x64/aarch64/armv7>.tar.gz
To be consistent with the linux system variable "$HOSTTYPE", "x64" should be "x86_64".
Instead of: piper_linux_<x64/aarch64/armv7>.tar.gz
Please use: piper_linux_<x86_64/aarch64/armv7>.tar.gz
Following the linux system variable "$HOSTTYPE" convention simplifies writing download scripts for the user.
Example:
wget https://github.com/rhasspy/piper/releases/download/"$PIPER_VERSION"/piper_linux_"$HOSTTYPE".tar.gz
Thank you.

Microsoft is using x64 for linux, instead of x86_64.

Microsoft is dominant in widows, not linux.
In most linux systems, x86_64 is the value of the system variable.
I'm requesting a linux name (x86_64) in a linux tar file (example:  piper_linux_x86_64.tar.gz) .
(It would also make sense to use a windows name in a windows tar file.  I'm requesting consistency.)

Changed in the latest release: https://github.com/rhasspy/piper/releases/tag/2023.11.14-2


[SUGGESTION] List of songs related to emotes

Is it possible to make a list, either in the README or part of the emote's description? There's a few songs we like and do not know such as Quick Style!

I'd also like a list, there are several songs I'd like to know the name of

I do not have a list of the actual song names. Your best bet it so look up the emote online, and try to find it yourself. Most of these are from fortnite emotes, so you should be able to find something online

Such a list would be just wonderful to have! I also in a search of some songs, and, of course, I want to find some not when I am in a game (I'm currently sitting in a train and don't have any possibilities to shazam..). As I see, there are plenty of people like me... Thanks a lot in advance!

Sorry, I don't have a list of song names. The songs are all named to match the emote name, which isn't always the name of the song, but sometimes it is. If you're looking for a specific song, chances are you can google the emote name, and you might be able to find it yourself.
Maybe when I have more free time, I could compile a list.


feat: Add organiser to persistence layer

Fixes #168

Add organizer in persistence layer
Create tests, and fix old ones
Change and add API in correspondence to asynchronous code
Update dbflow to include bug fixes

@mejariamol @arp95 @Shailesh351 @rohanagarwal94 @mahikaw Please review

@niranjan94 Please merge


Bluetooth: Host: Add public way of getting bonding state of a connection

Some used the internal function (bt_addr_le_is_bonded) from hci_core to get bonding information.

This may not be necessary if https://github.com/zephyrproject-rtos/zephyr/pull/43540 get merged, as we can obtain the bonded state via the callback from that.

We already have an internal function bt_addr_le_is_bonded which does exactly what you suggest, and we can simply make that public as an alternative.

Can we do that @Thalley ? Thanks!

This may not be necessary if #43540 get merged, as we can obtain the bonded state via the callback from that.

can you close this one then, since #43540 got merged?

This may not be necessary if #43540 get merged, as we can obtain the bonded state via the callback from that.

can you close this one then, since #43540 got merged?

I think so, yes. The problem that this PR was supposed to help fix, has been fixed by the other PR.