Ensure balance formatting in most used pages

Tasks to complete Fix balance components:

[x] Add balance formatting util; https://github.com/cennznet/ui/pull/60 ;
[x] Implement balance formatting in Storage page as a trial; https://github.com/cennznet/ui/pull/61
This pull request: Ensure balance formatting being implemented in most used pages (No actual code changes, but only rebased https://github.com/cennznet/ui/pull/60 and https://github.com/cennznet/ui/pull/61 into this feature branch); https://github.com/cennznet/ui/pull/62

http://localhost:3000/#/chainstate
Before

After

http://localhost:3000/#/extrinsics
Before

After

http://localhost:3000/#/toolbox
No need to be done for cennzx balance at this stage, and ensured no errors occur related to this change

@holygits The newly created balanceFormatting util is effective in pages with chain state and extrinsic queries.
We also have similar formatting utils are effective in generic-asset page, as well as in Input components, more refactoring and testing may need to consider if we want to uniform balance formatting across the app.
Further actions could be considered:

Refactor FormatBalance in Generic asset page if needed - https://github.com/cennznet/ui/blob/develop/packages/app-generic-asset/src/FormatBalance.tsx#L22
Uniform getFormatBalance.js which is applied on InputBalance components and toFormattedBalance which is created in this PR, if needed; https://github.com/cennznet/ui/blob/develop/packages/react-components/src/util/getFormatedBalance.ts
Apply 4dp balance formatting on toolbox/cennzx/rpc/**;


Fresh ftl serve execution fails to wait to connect to pg

Fresh clone of the repo, ftl docker containers stopped + deleted, docker image deleted -- basically a fresh start from the beginning -- ftl serve fails to connect to postgres. Then I can run ftl serve again and it connects no problem.
(Assuming running source bin/activate-hermit first and foremost)
ftl on  main via 🐹 v1.21.3 via ☕ v17.0.6 on 🐳 v24.0.6
➜ ftl serve
info: Creating docker container 'ftl-db' for postgres db
info: Unable to find image 'postgres:latest' locally
info: latest: Pulling from library/postgres
info: 31ce7ceb6d44: Pulling fs layer
info: 28caef79f6ed: Pulling fs layer
info: be24e278ddaa: Pulling fs layer
info: dfdbb4d6f9a3: Pulling fs layer
info: ebb06cfd45ec: Pulling fs layer
info: 9738a56db3f9: Pulling fs layer
info: 87cb08d2765c: Pulling fs layer
info: d99960ffd545: Pulling fs layer
info: 5b7988269916: Pulling fs layer
info: e5a82de43af8: Pulling fs layer
info: af2aa815fc4c: Pulling fs layer
info: 66c1f54848f0: Pulling fs layer
info: 2d2755afc3bb: Pulling fs layer
info: d99960ffd545: Waiting
info: 5b7988269916: Waiting
info: e5a82de43af8: Waiting
info: af2aa815fc4c: Waiting
info: 66c1f54848f0: Waiting
info: 2d2755afc3bb: Waiting
info: dfdbb4d6f9a3: Waiting
info: ebb06cfd45ec: Waiting
info: 9738a56db3f9: Waiting
info: 87cb08d2765c: Waiting
info: 28caef79f6ed: Verifying Checksum
info: 28caef79f6ed: Download complete
info: be24e278ddaa: Download complete
info: dfdbb4d6f9a3: Verifying Checksum
info: dfdbb4d6f9a3: Download complete
info: 9738a56db3f9: Verifying Checksum
info: 9738a56db3f9: Download complete
info: 31ce7ceb6d44: Verifying Checksum
info: 31ce7ceb6d44: Download complete
info: ebb06cfd45ec: Verifying Checksum
info: ebb06cfd45ec: Download complete
info: 87cb08d2765c: Verifying Checksum
info: 87cb08d2765c: Download complete
info: d99960ffd545: Verifying Checksum
info: d99960ffd545: Download complete
info: e5a82de43af8: Download complete
info: af2aa815fc4c: Verifying Checksum
info: af2aa815fc4c: Download complete
info: 66c1f54848f0: Verifying Checksum
info: 66c1f54848f0: Download complete
info: 2d2755afc3bb: Verifying Checksum
info: 2d2755afc3bb: Download complete
info: 31ce7ceb6d44: Pull complete
info: 28caef79f6ed: Pull complete
info: be24e278ddaa: Pull complete
info: dfdbb4d6f9a3: Pull complete
info: ebb06cfd45ec: Pull complete
info: 9738a56db3f9: Pull complete
info: 87cb08d2765c: Pull complete
info: d99960ffd545: Pull complete
info: 5b7988269916: Verifying Checksum
info: 5b7988269916: Download complete
info: 5b7988269916: Pull complete
info: e5a82de43af8: Pull complete
info: af2aa815fc4c: Pull complete
info: 66c1f54848f0: Pull complete
info: 2d2755afc3bb: Pull complete
info: Digest: sha256:a80d0c1b119cf3d6bab27f72782f16e47ab8534ced937fa813ec2ab26e1fd81e
info: Status: Downloaded newer image for postgres:latest
info: 63301db4c892cbc0566070fb298f01ddeb1ecd02d457efd31945cbfc2da0e189
info: Waiting for ftl-db to be healthy
info: Postgres DSN: postgres://postgres:secret@localhost:/ftl-db?sslmode=disable
ftl: error: failed to connect to `host=localhost user=postgres database=`: dial error (dial tcp <IP_ADDRESS>:5432: connect: connection refused)

ftl on  main via 🐹 v1.21.3 via ☕ v17.0.6 on 🐳 v24.0.6 took 29.8s
➜ ftl serve
info: Using docker container 'ftl-db' for postgres db
info: Postgres DSN: postgres://postgres:secret@localhost:5433/ftl-db?sslmode=disable
info: Starting 1 controller(s) and 0 runner(s)
info:controller0: Starting FTL controller
info:controller0: Building console...
info:controller0: Console started
info:controller0: Starting DB listener
info:controller0: Listening on http://localhost:8892

I understand the command ftl-initdb --recreate is now replaced with ftl serve --recreate but running the former prints a similar error, so it may be in the same area of interest:
ftl on  main via 🐹 v1.21.3 via ☕ v17.0.6 on 🐳 v24.0.6
➜ ftl-initdb --recreate
ftl-initdb: error: failed to connect to `host=localhost user=postgres database=`: dial error (dial tcp <IP_ADDRESS>:5432: connect: connection refused)

It looks like in the first attempt we failed to get the port back from docker since the connection string has localhost: without the port:
info: Postgres DSN: postgres://postgres:secret@localhost:/ftl-db?sslmode=disable

The second issue is likely related to the fact that ftl-initdb and ftl serve use different database ports.
ftl-initdb: 5432
ftl serve: 5433

The best way to get a db for ftl-initdb is to do docker compose up -d in ftl


fix reputation check

Dominant / Submissive reputation got changed a long time ago.
I believe long time ago the value went from 0 to 100.
Anyone with a stat below 50 was considered submissive and anyone with over 50 was dominant.
The current club uses a value from -100 to +100.
Starting at 0, anyone below 0 is submissive and anyone with more than 0 is dominant.
This fixes it and for gameplay purposes, consider anyone with a 0 stat to be submissive. For all the new players joining the room.

added more info in the issue page

fair enough for the rep check.. was thinking about it from a math point of vue.. but it makes sense to have the threshold at 50


NH-80074 Otelcol: Add lambda distro version to resource attribute

Added sw.apm.otelcol.version in resource attributes processor to indicating current opentelemetry-lambda distro.

NH-80243

LGTM! One ask--you mentioned the pitfall of forgetting update this. Can it be checked for in the publish workflow, or mentioned in the release process?

The check won't have much benefit as I still need to do the following manual action.

Remove the tag
Bump the version in config.yaml
Tag again to release

Not prefer to pollute the workflow because of inspecting the content of config.yaml.

How about adding a RELEASE markdown to our branch under the collector directory with some info then?

How about adding a RELEASE markdown to our branch under the collector directory with some info then?

I wonder how does a RELEASE markdown file help.

How about adding a RELEASE markdown to our branch under the collector directory with some info then?

I wonder how does a RELEASE markdown file help. Sound like I have to maintain config.yaml and RELEASE together.

it would help someone new to this know what the steps are for releasing our otelcol extension layers.

How about adding a RELEASE markdown to our branch under the collector directory with some info then?

I wonder how does a RELEASE markdown file help. Sound like I have to maintain config.yaml and RELEASE together.

it would help someone new to this know what the steps are for releasing our otelcol extension layers.

I changed to do it in another way.

Extracting the version from the tags
Replace the placeholder string by the version in config.yaml
build and publish the lambda

As the version is set to config.yaml only, I think it is okay not to commit that file to the tag. That sw.apm.otelcol.version field doesn't hurt to investigate issue in the future.


Undefined symbol zungqr_

Traceback (most recent call last):
File "real_time_object_detection.py", line 2, in
from imutils.video import VideoStream
File "/var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/imutils/init.py", line 8, in
from .convenience import translate
File "/var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/imutils/convenience.py", line 5, in
import numpy as np
File "/var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/numpy/init.py", line 148, in
from . import lib
File "/var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/numpy/lib/init.py", line 25, in
from .index_tricks import *
File "/var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/numpy/lib/index_tricks.py", line 12, in
import numpy.matrixlib as matrixlib
File "/var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/numpy/matrixlib/init.py", line 4, in
from .defmatrix import *
File "/var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/numpy/matrixlib/defmatrix.py", line 11, in
from numpy.linalg import matrix_power
File "/var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/numpy/linalg/init.py", line 73, in
from .linalg import *
File "/var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/numpy/linalg/linalg.py", line 33, in
from numpy.linalg import lapack_lite, umath_linalg
ImportError: /var/rootdirs/home/root/tflite/tflite-env/lib/python3.8/site-packages/numpy/linalg/lapack_lite.cpython-38-arm-linux-gnueabi.so: undefined symbol: zungqr

@Nytish,
We see that the issue template has not been filled, could you please do so as it helps us analyse the issue [tf version, steps followed before you ran into this error or stand alone code to reproduce the issue faced] or if possible share a colab gist with the issue reported.
Thanks!

Steps
1.Installed lapack on system
2. Try to run my Python code
3. Got this error as shown above

@Nytish,
We see that you are using tf version 1.0, 1.x is not actively supported, please update to 2.x and let us know if you are using same issue.
Also looks like your numpy installation is broken. Numpy appears installed by linked incorrectly to lapack.
Thanks!

How to upgrade tf to 2.x
Numpy version 1.17.4 i installed
On Fri, May 21, 2021, 2:58 PM tilakrayal @.***> wrote:

@Nytish https://github.com/Nytish,
We see that you are using tf version 1.0, 1.x is not actively supported,
please update to 2.x and let us know if you are using same issue.
Also looks like your numpy installation is broken. Numpy appears installed
by linked incorrectly to lapack.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/49366#issuecomment-845818198,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARVZUDHYPT2DQBH42OGIPZDTOYRT5ANCNFSM45F6VVUQ
.

@Nytish ,
Can you please refer to this link for installing tensorflow latest version.
Thanks!


Normalize buttons

Normalize all landing buttons to be like the "Meet the team" one. We should also create a component to render a button.

This was solved in #571


backend beautification

Brother, I think the back-end permission setting page can be considered to beautify it. At present, I feel that this part affects the use a bit 😄 Thanks for updating and sharing！

Thank you for your feedback and encouragement ❤
Due to limited energy,  I can only focus on optimizing the client for now. I will consider optimizing the management panel when I have more time.


Remove dependency with non-existent docker image hyperledger/sawtooth…

docker image hyperledger/sawtooth-shell:1.0 not exists. I have repaced it for ubuntu:xenial base image.

The shell image contains a few extra dependencies for interacting with the sawtooth blockchain, and can be found here:
https://hub.docker.com/r/hyperledger/sawtooth-shell/


account for empty lines in receive-hook message (#10773)

Backport #10773
Co-authored-by: Lunny Xiao<EMAIL_ADDRESS>Co-authored-by: John Olheiser<EMAIL_ADDRESS>

make L-G-T-M work


Added tokenizeTopN

Added a method to provide top n tokenization results for each chunk.
PTAL @juneng603, @MechanicKim

I saw this change now. Sorry for late.
I will update open-korean-text-api.
Thanks @nlpenguin


[INLONG-691] update properties and scripts for inlong-manager

Codecov Report

Merging #529 (6b65a0d) into master (17f6e08) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #529      +/-   ##
===========================================
- Coverage      7.72%   7.71%   -0.01%
+ Complexity      563     562       -1
===========================================
  Files           355     355
  Lines         31077   31077
  Branches       4970    4970
===========================================
- Hits           2400    2399       -1
- Misses        28187   28190       +3
+ Partials        490     488       -2

Impacted Files
Coverage Δ

.../producer/qltystats/DefaultBrokerRcvQltyStats.java
45.31% <0.00%> (-0.40%)
:arrow_down:

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 17f6e08...6b65a0d. Read the comment docs.


Support testing internal classes with and without internal interfaces

The current implementation only provides a Test<T> class which forces the scope of T to be public to satisfy the compiler. The workaround for private types with a public interface is to use TargetType. This however does not support the scenario where both the interface and type are internal.
This could be supported by providing an alternative as Test with a SUT<T>() method instead.

This idea would result is an abstract class with something like
public abstract class Test
{
    private object? _sut;

    public T SUT<T>() {

        if (_sut == null || _sut is T == false)
        {
            // Build the SUT
        }

        return _sut;
    }
}


Next release

Hi!
Is there any way to know when the last release is scheduled for ? Last release is not very convenient to use with Webpack/Browserify/... And this PR fixed the problem: https://github.com/pablojim/highcharts-ng/pull/428 but I have to depend on master to use it right now.
Thanks !

@pablojim any chance of a release soon?

@gaelduplessix I've released<EMAIL_ADDRESS>

@pablojim hey, it would be great to get a new release

Planning to get a release it next week. Thanks for chasing!
On 29 Jul 2016 9:58 a.m., "Thomas Grainger"<EMAIL_ADDRESS>wrote:

@pablojim https://github.com/pablojim hey, it would be great to get a
new release
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pablojim/highcharts-ng/issues/452#issuecomment-236129897,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AApu0z0Q0_R5koR2zUCyqkgc1-b5BkSFks5qacC5gaJpZM4Htnic
.

0.0.12 released

Sweet
On 7 Aug 2016 21:05, "Barry Fitzgerald"<EMAIL_ADDRESS>wrote:

0.0.12 released
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pablojim/highcharts-ng/issues/452#issuecomment-238105053,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZQTF1yW-SxvPkhEvyq4f9GozvNQSuiks5qdjqdgaJpZM4Htnic
.

@graingert Thanks for all the work on this!


Add kernel 6.1.3 to Microsoft Surface profile

Description of changes
Things done

Updates the kernel version + upstream patches from linux-surface to 6.1.3

[ ] Tested the changes in your own NixOS Configuration
[ ] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

Hmm, seems like it's failing similarly to https://github.com/NixOS/nixos-hardware/pull/533#issuecomment-1376497418, @Mic92.
Not sure if you want me to raise an issue against some of the RasbPi commiters?

If this version builds + runs as expected, I intend to drop the 6.0.* kernel.
cc @damianoognissanti, @tmnvanderberg, @Yeshey

bors merge

bors cancel

Kernel 6.1.6 patches have been released.
A new PR for that is here: #545


Linking in task execution schema

This is a draft proposal for the workflow execution schema that uses protobuf and extends on the task execution schema.

@kellrott Do you think it'd be worth discussing this on a call or not really?

Probably only after @tetron has looked at it

I started playing with this in the protobuf-pa branch.

Take a look at PR #8


Update to Django 1.10 when Django 1.10 is released.

https://docs.djangoproject.com/en/dev/releases/1.10/

Closed in favor of #392


record_transformer: remove_keys processing should be last

Currently, remove_keys doesn't work with renew_time_key parameter, so
user needs one more filter to remove renew_time_key field from the record.
<filter pattern>
  @type record_transformer
  renew_time_key event_time
  auto_typecast true
  <record>
    event_time ${Convert record["time_str"] into unixtime or float type}
  </record>
</filter>

<filter pattern>
  @type record_transformer
  remove_keys event_time
</filter>

This is verbose and not good performance. remove_keys should remove renew_time_key.
<filter pattern>
  @type record_transformer
  renew_time_key event_time
  remove_keys event_time
  auto_typecast true
  <record>
    event_time ${Convert record["time_str"] into unixtime or float type}
  </record>
</filter>

@sonots Could you check this patch?

LGTM


missing pipes folder?

pipes folder is missing?

In this example project, I don't add a folder because nothing is implemented as a pipe.
Pipe folders are described in the folder structure.

In this example project, I don't add a folder because nothing is implemented as a pipe.
Pipe folders are described in the folder structure.


Incorrect (false positive) floating point recognizing

Any lexeme that starts with e (or with a regexp \d*e) is recognized as a floating point number. Thus, any missed word that starts with e does not cause an error (as expected), but is unexpectedly translated as 0e.
A testcase of the expected behavior:
t{ s" 0 0 efoobar-undefined-word" ' evaluate catch nip nip -> 13 }t

1efoobar-undefined-word is still incorrectly recognized as a floating point number.
See the format in 12.3.7 Text interpreter input number conversion.

I really shouldn't fix bugs before bed.


fwlink is broken

The link https://go.microsoft.com/fwlink/?LinkID=187810 in the Description results in a 404

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

ID: 2d922a32-981c-8e08-9359-b7f5e21b1aa4
Version Independent ID: a0f9af58-42af-202c-10f3-dbb09b17595e
Content: Install-SPSolution (sharepoint-server)
Content Source: sharepoint/sharepoint-ps/sharepoint-server/Install-SPSolution.md
Product: sharepoint-powershell
GitHub Login: @techwriter40
Microsoft Alias: kirks

@officedocsbot assign @yogkumgit

Hello @John-Hart
Thanks for noticing and reporting, created a PR to fix this.

@get-itips  Thank you very much for the contribution and updating the documentation with PR. @John-Hart Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


[Bug?]: clientOnly doesn't work on Cloudflare Pages

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
clientOnly doesn't render when on Cloudflare Pages and a "real" domain. What's a "real" domain? https://pentive.com/ is "real", and https://hub-b6m.pages.dev/ is "fake".
Yeah, this is gonna be a weird one.
Expected behavior 🤔
clientOnly should render.
Steps to reproduce 🕹
Steps:

Clone this minimal repo https://github.com/AlexErrant/solid-start-cf-basic
pnpm i && pnpm build && pnpm run deploy
Observe that it works on the whatever-name.pages.dev domain
Observe that a Cloudflare Site doesn't work (for me, DNS is setup like CNAME, pentive.com, hub-b6m.pages.dev)

Context 🔦
From Cloudflare's Dashboard, Caching/Configuration, I've hit the "Purge Everything" button to clear the cache.
Strangely, enabling "Development Mode" makes clientOnly render as expected. But it only works for 3hrs before Cloudflare turns it off again.

It was Cloudflare's auto-minify, which I had to disable via curl because, in their infinite wisdom, Cloudflare deprecated the UI before the setting itself.
https://discord.com/channels/595317990191398933/1273376820221313045/1273441598604181654
https://community.cloudflare.com/t/deprecating-auto-minify/655677/18


[BUG] change group introduction,but the message return is group name changed

OpenIM Server Version
3.5.1
Operating System and CPU Architecture
macOS (ARM)
Deployment Method
Source Code Deployment
Bug Description and Steps to Reproduce
1、use api setGroupInfo,set introduction property
2、return a message，but the message contentType is groupSetName
Screenshots Link
No response

Hi, updated to 3.8.

It has not responded for a long time. Close it first and reopen it when there is a problem.


Answering callback query?

Hello.
It is still not clear how to handle callbacks from inline buttons.
In each callback I'm using
callback: cb => {
  $.api.answerCallbackQuery(cb.id)
}

so the button in Telegram will stop 'spinning'.
Are there any solution out the box to not write that answerCallbackQuery each time?

#63 This issue has already been discussed and sorted out.

Is this a solution - each time I should write it? Really? For each button?


Hangfire dashboard authorization

I would like to add support for authorization in Hangfire Dashboard. Specifically, I propose to modify the entry URL query by adding an access_token, which will then be verified for validity in the IDashboardAsyncAuthorizationFilter. However, due to the length of the JWT token generated by this project, it is not possible to pass it through the URL. Therefore, I have implemented a workaround that only takes the first part of the token before the dot. Although I acknowledge that this approach may not be ideal, it is currently the best solution I have found.
@Bram1903
If you have any suggestions on how to shorten the length of the JWT token, please let me know. Thank you.

Isn't it possible to send the authentication cookie within the request header, which doesn't have to be shortened?

Isn't it possible to send the authentication (JWT) cookie with the request itself, rather than defining the token within the URL itself?
Currently, you are actually parsing in the token in the request URL, but I believe it's also possible to send it with the same request, but within a cookie.
I might have missed something, which makes this impossible, but it is the only solution I can think of.

Thanks for your message. It seems that the issue at hand is that the JWT token is too long because it contains all the permissions for the current user. As a result, the generated token string exceeds the URL and Cookie limitations of browsers, making it impossible to save the complete token string to a Cookie.

I solved the merge conflicts that occured after recent commits. Is this already completly functional, or does it still need improvements?

@Bram1903
Thank you for letting me know how to change the status of a PR from Draft.


fix #80

May not have closely read the original pull request enough💀, but this should work.
It passes all of the test suite, and it works on my test file as well.

Hey @SuperStormer, thanks for sending the PR. I'll merge it and add a test case on top of it.


Display result of code in codemirror textarea

#41 issue is must be precede first, but implemented

Implemented in #63


Entity hider but for pets only.

Basically just an extension to entity hider to only hide pets and nothing else.

Duplicate #2794


fkdl0048's mentoring meeting 9, 2023-01-23

google meet, 오후 11시

https://github.com/fkdl0048/Mentoring-Project/discussions/39


PackageSelector>>#uninstall: endless loop

Describe the bug
When uninstalling a user-defined package, the uninstaller gets into a loop and does not return. Dolphin must then be shutdown using the Task Manager.
The problem does not happen for standard Dolphin image packages. The packages where this does happen are in a a subfolder of the 'Desktop' folder.
To Reproduce
Steps to reproduce the behavior:

Create and install a package.
Uninstall the package.
The spinning cursor is show and Dolphin must be shut down with the Task Manager.

Expected behavior
The package is uninstalled.
Screenshots
If applicable, add screenshots to help explain your problem.
Please complete the following information):

OS: Windows 10, Dolphin release/7.1

Additional context
PackageSelector>>#uninstall:
At the bottom the check for currentFolder notNil is always true and the loop does not exit.
[currentFolder notNil and: [(self filterPresenter selection: currentFolder ifAbsent: []) isNil]]
		whileTrue: [currentFolder := currentFolder parent]

On my setup, it seems the call currentFolder parent always returns 'C:' if the current folder is 'C:'

File class>>#removePathDelimiter returns 'C:' if the argument is 'C:'


Page for https://storybook.js.org/examples/ not available

Describe the bug
Before version 5, this page was available to our team, is it now lost?
To Reproduce
Go to https://storybook.js.org/examples/
and you will see redirect to https://storybook.js.org/use-cases/
Expected behavior
Page must be available

Closing this as a duplicate of https://github.com/storybooks/frontpage/issues/31


Add a switch to disable synthesizer collapsing functions

Motivation
Sometimes users who are interested in the readability of generated SystemVerilog or ROHD developers are curious about how in-line modules and assignment collapsing are performed to create the final output.  A flag to disable this would be useful in these situations.
Desired solution
A flag (maybe per-module, maybe per-synthesizer) that disables collapsing like _collapseAssignments and _collapseChainableModules.

Sometimes it is desirable to prevent collapse on only specific signals (for either debug or production).


Exception handling

Hug provides @exception to add error handlers. This is great, but I'd like to propose an improvement - there should be a way to exclude Falcon's error classes - these are raised by Falcon itself, or by your own code to handle expected problems.
Right now, I can do something like this:
@exception()
def handle_exception(exception):
    if not isinstance(exception, falcon.HTTPError):
        log.exception('Unexpected error while handling API request.')

    raise falcon.HTTPInternalServerError('Something broke', 'Something broke')

This works, but it would be nice to do something a bit cleaner:
@exception(exclude_falcon=True)    # proposed
def handle_exception(exception):
    raise falcon.HTTPInternalServerError('Something broke', 'Something broke')

In other words, a falcon exception isn't "really" an exception, and it would be useful to have a convenience function or argument to capture non-Falcon errors.

Found another issue with exception handler. I'll park this here for now, let me know if you'd prefer a separate issue.
If a middleware throws an exception, it's handled by falcon and never hits hug's exception handlers.

Hi @ariscn,
Thanks for the ideas! I think the way I will implement the first will be an exclude=(Exception, ) tuple that can be used to define any number of class of exceptions that you would like to be handled externally. The second is known, with the assumption that middleware exceptions are different that other classes of exceptions - and should generally handle the exceptions internally in their own unique way - but I think I'm getting swayed to the other way of thinking.
Thanks!
~Timothy

Similar comment to the other thread - if this is a known issue (or considered a feature at the moment), it's worth documenting.

An exclude argument would also prevent KeyboardInterruption exceptions being handled while developing and hitting CTRL+C constantly.

Found another issue with Exception handling.
My API has an exception handler, and uses LogMiddleware. The error handler re-raises Falcon exceptions and raises HTTPInternalServerError(...) otherwise.
When an exception occurs, this returns a 500 as expected. But, the middleware logs a 200! Roughly:
@middleware_class()
class DummyLogMiddleware(LogMiddleware):
    pass

@exception()
def handle_exception(exception):
    raise HTTPInternalServerError('Something broke', 'Something broke')

@get('/foo')
def foo():
    raise Exception('foo')

This has been officially implemented and merged into develop in preparation for the next release here: https://github.com/timothycrosley/hug/pull/382/files
Thanks!
~Timothy

2.2.0 has now been officially pushed to PYPI with this issue resolved
Thanks!
~Timothy

Quick followup question - does 2.2.0 also change handling for exceptions thrown by middleware (handled by Falcon per earlier comment), and will middleware now see the correct status code?


Update version from 0.0.80 to 0.0.81

This is an automated update of version in pyproject.toml. This action is performed by publish.yml.

updated version from 0.0.80 to 0.0.81, @SuleyNL pls review


Multilingual tabular to schema

For a given Google Sheets driven schema in /web/templates/[schema folder]/[LinkML schema files], if schema has an "in_language" parameter with list of languages such as "en, fr", then running

cd web/templates/[template folder]/
python ../../../script/tabular_to_schema.py

will create /web/templates/[schema folder]/schema.yaml and schema.json as well as creating locales/[locale e.g. fr]/schema.yaml and schema.json.
to also add entries in /web/templates/menu.js, include the -m or --menu parameter:

python ../../../script/tabular_to_schema.py -m

This depends on Google Sheets setup of fields like so, see CanCoGeN-slots and  CanCoGeN-enums tabs of this sheet.

To clarify, those fields annotated to _fr do not become a <field>_fr: <french field> mapping in the schema? But instead only as <field>: <french field> for the schema in /web/templates/locales/fr/?


Add sudo to Dockerfile

I could not build this Docker image. So I added sudo to Dockerfile.

Thanks :)


Add a secret GM notes field on items

Add a GM notes field to the common item template, which is shown only to GM users in the description tab of all item sheets.
The specific use-case right now is for forged documents that need a secret DC to discover the forgery for passive observers, but the field itself should be usable in many situations.

How big is it when it's empty?

Same size. I found it to be a little hard to adjust the size properly. Maybe it can be collapsed a bit using :has() or by converting the description tab to a grid?
I picked the current size by looking at this:

With the default item sheet window size, the editor buttons take up two rows making it a super tight fit 😐

Another option is to add a GM tab. Not my preferred option due to the reduced visibility. But it does give room for more GM-y things.

Maybe it can default to null and have minimal profile until the GM clicks +?

Let me try that.

For some reason the :has(...) selector doesn't work properly with descendant classes 🤷 This is the most compact I could make it, since the editor has to be present in the DOM for Sheet#activeEditor(...) to work.

You could check hazards to see how to make them compact. I had to do some shenaniganry there.

After taking a look at the hazard sheet, I decided to go in a slightly different direction and put the GM notes at the top and let the entire description panel flow normally, instead of having an always-visible, height-adapting block at the bottom.

Can you please change the "GM Notes" header to look different while it's empty?  I imagine that 99% of items will not have any GM notes, and for all of those cases the extra text and separating line take up a lot of space, along with drawing the eye.
I would prefer it if the GM Notes element didn't take any lines at all, as long as it's empty;  and the GM would need to click some button in order to add GM notes, with that button being unobtrusive and somewhere on the side or the top of the dialog window.

Compacted the description tab further when there are no GM notes:


Vulnerability scan the ko image and attach as attestation

See https://github.com/distroless/actions/blob/main/apko-snapshot/action.yaml#L98-L105 for example -- this runs trivy on a newly built container image, which produces a SARIF file. Then the next step cosign attests that scan result onto the image in the correct form: https://github.com/distroless/actions/blob/main/apko-snapshot/action.yaml#L145-L146
cc @vaikas

/assign


New device type Dyson purifier cool formaldehyde

I have two Dyson Purifier+Cool Formaldehyde. One with device type 358E and one with device type 358K.
I could connect the device type 358E in Home Assistant, but for the device type 358K I''m getting the error "Failed to connect".

Hi @mtjweb! Unfortunately this integration is no longer maintained, but I've created a new fork and am actively working on the new Humidifier and Formaldehyde models. Have a look at #185 for more information, and let me know if you have any questions.

Hi @mtjweb! Unfortunately this integration is no longer maintained, but I've created a new fork and am actively working on the new Humidifier and Formaldehyde models. Have a look at #185 for more information, and let me know if you have any questions.

Thanks for your reply. Are you going to add the device type 358K?

Yes, definitely. It's the next thing on my list after getting the forks detached from the original repos. I've got some requests to github support for that now, and that will allow me to have dedicated issue trackers on the new repos.

Support for all Formaldehyde devices has been implemented on https://github.com/libdyson-wg/ha-dyson and https://github.com/libdyson-wg/libdyson-neon!


Use ReplayLog data to create KML files of both traffic and ownship

Changes to the Settings page allows the user to dump the ReplayLog (traffic+ownship) SQLite file or in the new "GPS Track File" panel to just dump the ownship  mySituation GPS data. The new 'Write GPS to file' setting only writes the mySituation portion of ReplayLog to limit the growth of the stratux.sqlite file size.
The ReplayLog KML file can be created with animations based on time, or altitude. The altitude filter is useful to remove cruise traffic and view traffic below. Demo: https://zippy.gfycat.com/OfficialFirstChinesecrocodilelizard.webm
The KML files have folders based on the following criteria:

ownship
ADS-B Traffic w/min alt < FL180
ADS-B Traffic w/min alt > FL180
UAT Traffic (TARGET_TYPE>1)

Clicking on traffic trails will display minimum and maximum altitude and provide links to Flightaware.
The only thing I think I am missing is a way to clear the SQLite file from the web UI to either free up space or when starting a new flight.

WOW! Nice

Looks pretty good. The biggest issue I have with this is that it opens and runs from the gen_gdl90 daemon. File locking issues.
Breaking out some of the replay log features is a good idea.
How are most people handling .kml files?

Does the Write-Ahead Logging in SQLite3 prevent the file lock issues you are concerned with? In my testing I haven't been able to create a file lock error. It looks like there is no issue with concurrent writes from datalog.go and reads from export-datalog.go.
Here is a Gist of lsof output showing multiple locks on the SQLite, -wal and -shm files while testing concurrent reads and writes.
Is there any part of the code base that doesn't run under gen_gdl90 that I can look at as an example for breaking out these functions?

Any chance there can be future movement on this?  How about saving the files to another partition on the microSD?  I have a 32GB one that I put Stratux on.  It is still however only using the standard 2GB partition.  Another 28GB (after formatting) still kicking around I'm sure.

Stale PR

Hi, can the work of @alexberryman be merged please ?  In developer mode maybe?  This would make stratux the only adsb device with flight logging....


Pls pls don’t archive this repo

Is there any chance to fork your fork ?
I like Cercube much more then uYouplus but unfortunately the repo of QN got taken down but no one knows why

Is there any chance to fork your fork ?
yes of course! And if you need help go here. https://github.com/arichorn/CercubePlusExtra/wiki/Building

I like Cercube much more then uYouplus but unfortunately the repo of QN got taken down but no one knows why
I think the reason it got taken down was probably because it got requested for take down by the Cercube Developer or Google sent qn a letter to take it down. Honestly don’t know but this is probably why I’m Archiving to prevent the same fate as the original CercubePlus Repo

also when this gets archived you can still download the cercubeplus ipa.

I like Cercube much more then uYouplus but unfortunately the repo of QN got taken down but no one knows why
I think the reason it got taken down was probably because it got requested for take down by the Cercube Developer or Google sent qn a letter to take it down. Honestly don’t know but this is probably why I’m Archiving to prevent the same fate as the original CercubePlus Repo

hm okay i really wish that you maintain it as long as possible, i have not enough knowledge to do it by myself :(.
i think not that he does it because of the Cercube Dev want it too, QN never cracked it, he just combined it with other tweaks like on jailbreak.
The take down is really really mysterious

I would highly recommend to not mention "Cercube" anywhere, I think it's developer is continuously searching the web for unauthorised projects from people using his tweak and is sending out injunctions... So many Cercube Mods were taken down in the past...

I would highly recommend to not mention "Cercube" anywhere, I think it's developer is continuously searching the web for unauthorised projects from people using his tweak and is sending out injunctions... So many Cercube Mods were taken down in the past...

Really?  It’s really hard for me to imagine that the dev of Cercube would do something like that because his tweak is not modified/ cracked in the CercubePlus ipa

Sadly for me I have no knowledge I know a bit though when it comes to changing a bit of stuff in the code. but overall it’s not bad.

okay, same for me

Yep I can combine tweaks like qn too. Like for example the New YT Shorts remover Tweak I added in 17.49.4-5.3.12. Combining tweaks is pretty simple if you find some tutorials about it.

Ok maybe you can teach me some of your knowledge ;)
Or give a link for good video

I would highly recommend to not mention "Cercube" anywhere, I think it's developer is continuously searching the web for unauthorised projects from people using his tweak and is sending out injunctions... So many Cercube Mods were taken down in the past...

Yeah. It’s been sad to see them go.

Really? It’s really hard for me to imagine that the dev of Cercube would do something like that because his tweak is not modified/ cracked in the CercubePlus ipa

Cercube itself wasn’t modified in this. It’s just sad to see the dev take them down.

I think I will ask him

watch out. Don’t let this get taken down, because I got a bit more versions to go before I stop maintaining it.

B


no output file specified

happens every time i use picasso -h vshader_shbin.h vshader.v.pica

As the error message indicates, you have not specified an output file. Please read the documentation: https://github.com/fincs/picasso/blob/master/Manual.md#command-line-usage


Class 'WP2StaticAdvancedCrawling\Controller' not found in wp-content/plugins/wp2static-addon-advanced-crawling-master/wp2static-addon-advanced-crawling.php:27

With wp2static 7.1.6, when activating this addon, I get:
Fatal error: Uncaught Error: Class 'WP2StaticAdvancedCrawling\Controller' not found in wp-content/plugins/wp2static-addon-advanced-crawling-master/wp2static-addon-advanced-crawling.php:27 Stack trace: #0 wp-content/plugins/wp2static-addon-advanced-crawling-master/wp2static-addon-advanced-crawling.php(41): run_wp2static_addon_advanced_crawling() #1 wp-admin/includes/plugin.php(2286): include_once('') #2 wp-admin/plugins.php(191): plugin_sandbox_scrape('wp2static-addon...') #3 {main} thrown in wp-content/plugins/wp2static-addon-advanced-crawling-master/wp2static-addon-advanced-crawling.php on line 27

Hi @twardoch, these GitHub repos require running composer install to use.
For easily installable zips, you can grab from https://wp2static.com/thanks-for-supporting

Yep, I realized they require compiling just short time ago :) I think I got "advanced crawling" working. Is the "advanced discovery" add-on abandoned? I’d love to be also able to specify some additional URLs to crawl and turn into static pages.

BTW, in the install.sh, it’d be safer to wrap all paths in quotes. I had a space in the path and the install failed. Sure, developers don’t use spaces, but... :)

@twardoch the build zip script? Yep, agree! I usually add shellcheck test to my projects, haven't added that into this, it seems, else I think it would warn about unquoted paths. I can add it to the GitHub Actions in this repo.
I bleieve there's crawling within this addon, but this is mostly @john-shaffer's code and I'm not up to speed with it yet.
The older style WP2Static has crawling built in, you can grab latest source from https://github.com/leonstafford/static-html-output (recently patched some PHP8 errors)


Using generic function inside of generic class can produce unexpected type typing.

Dart SDK Version: 2.2.0-dev 2.1, 2.1.1-dev.3.2
OS: Windows 10 64 bit
The following code sample declares a generic class with generic function:
class Test<X extends num> {
  void printX() {
    print("X: " + X.toString());
  }
  void printT<T extends X>() {
    print("T: " + T.toString());
  }
}

main() {
  Test<int> t1 = new Test<int>();
  t1.printX();
  t1.printT();

  Test<num> t2 = t1;
  t2.printX();
  t2.printT();
}

I expect that T should extend X (i.e. it should be int for t1 and t2), however this is not so here - t2.printX() prints int and t2.printT() throws an exception here:
X: int
T: int
X: int
Unhandled exception:
type 'num' is not a subtype of type 'int' of 'T'
#0      Test.printT (file:///D:/DART/sdk/tests/co19/src/Language/Generics/test.dart)
#1      main (file:///D:/DART/sdk/tests/co19/src/Language/Generics/test.dart:17:6)
#2      _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:300:19)
#3      _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

As far as I understand, this issue should be fixed when inference specification is ready.

@iarkh wrote:

this issue should be fixed when inference specification is ready

Agreed, but let me mention the expectations: The only outcomes which are affected by inference are the printouts during t1.printT() and during t2.printT().
The actual type argument of t1 and t2 at Test cannot be denoted (in the given scope, there is no syntax derived from <type> whose value is that type argument), and hence there is no way type inference could provide such a type argument to the invocations of printT.
So it's not plausible that inference will be specified to provide any other value than the statically known value of the type argument of t1 respectively t2, that is int for the first invocation of printT and num for the second. I'd say that the only plausible alternative would be to make it an error to invoke printT outside class Test at all, but that is of course a breaking change, and hence not so likely.
This actually means that the behavior that you have observed (that would be when running the test program using dart, maybe with some options?) is exactly what a specification of type inference is likely to require, which means that the test ought to be adjusted to have //# 00: compile-time error in line 17.
With that, the example program would simply be a test that targets type inference, and it would have exactly the same status as any other test targeting type inference ("this is how we think it should work, but we'll need to double-check when the type inference specification has been landed").
Isn't there a suitable place to put such tests, and a suitable status to give them? Presumably, we'll have a lot of co19 tests targeting type inference, and if this is the first one then it could just be put into a new directory (or directory subtree) on that topic.

Initially I was going to put such tests into Language/Generics folder, with the following assertion:

A generic class is a mapping that accepts a list of actual type argu-
ments and maps them to a class. Consider a generic class declaration G named C
with formal type parameter declarations X1 extends B1, . . . , Xm extends Bm,
and a parameterized type T of the form C<T1, . . . , Tl>.
It is a compile-time error if m != l. It is a compile-time error if T is not
well-bounded (14.2).
Otherwise, said parameterized type C<T1, . . . , Tm> denotes an application
of the generic class declared by G to the type arguments T1, . . . , Tm. This yields
a class C0 whose members are equivalent to those of a class declaration which
is obtained from the declaration G by replacing each occurrence of Xj by Tj.

Regarding the suitable status - I was going just to mark the tests with corresponding $Issue tag - is it enough or not?

I think there is a need for a separate Language/Inference or Language/TypeInference folder, because some inferred types are not type arguments (e.g., they can be the type of a variable or parameter). Also, some inferred type arguments are not class type arguments but function invocation type arguments (e.g., myList.map((x) => 42)), and that's also true for the particular example that we have discussed. So we'd need text about inference, and in particular about inference in the setting where the bound is not statically known.
We could then consider everything in the type inference folder (or folder hierarchy, if needed) to have status "please double-check this when we have landed a specification of inference", and that double-check operation will then (hopefully) only cause a small number of adjustments.


Suggestions on the current UI

Add more instructions for the code exercise

Scrolling doesn't work when the user is focusing on a code editor

Action buttons for assertion code

The action buttons with assertion code are currently placed outside of the assertion code box. Users may misunderstand them with actions on the exercise --- e.g., deleting an exercise instead of deleting an assertion

For MCQs, the button to add options should be more obvious.

An example fix:

Rendering doesn't work after switching to the learners' view?

Thanks for the suggestions. I hadn't seen them until now. I'll consider them after today's lab meeting.
The point 5: not rendering after switching back, should already be fixed.


supported more css units

Support more CSS units without native update.
Three updates together:

css-units branch in weexteam/weex-styler
weex-next branch in weexteam/weex-vue-loader
jsfm-feature-css-units in jinjiang/weex

How it works: CSS value 100rem in <style> will be transformed into "100rem" by weex-styler and then 100 * CSS_UNIT.REM by weex-vue-loader. At the same time define global variable CSS_UNIT in JS Framework. So it works.

https://github.com/alibaba/weex/pull/1894 related

Just
this.width = 32 * CSS_UNIT.REM
this.height = this.getHeight() / 25 * CSS_UNIT.VH

is OK. The variable CSS_UNIT could be exposed to frontend developers

Another thing is at least we can make it happen before native render support these units. And maybe that's enough already.


DE28906: Fix for nested drop zones with rejected inner drop

What does this PR do?
Allows an outer nested drop element to receive a drop if an inner nested drop has rejected it.  In a nested configuration, an outer nest may receive a drop notification if an inner one doesn't handle it.  Once a drop is handled, the outward event propagation is stopped.
Any background context you want to provide?
When testing an upgrade in Churro, bumping react-dnd to the current version (0.9.6-rally.9), the team planning page broke in alm-guitests for workspaces that are configured with manual ranking.  If you drag something form the backlong onto the iteration's stories, the drop isn't allowed -- you must pass over the header row area, which is a functional regression.
Where should the reviewer start?
NOTE: The only two files that really changed here are: modules/backends/Mouse.js and modules/utils/createDragDropMixin.js.
The rest of the files are built based on that.
How should this be manually tested?
There are no tests for this package.
What are the relevant tickets?
DE28906
Screenshots, if appropriate. :link:
n/a
Definition of Done

[X] Story acceptance criteria updated if changed
[X] Does not negatively impacting perceived performance
[ ] Does not degrade performance and meets feature performance requirements
[ ] Renders properly in all supported browsers
[X] Sufficiently rich data used during development to expose important data relationships
[ ] Code reviewed by someone who didn't write it
[ ] Automated tests written and passing at appropriate levels. (unit, integration, end-to-end, etc.)
[ ] No functional regressions have been introduced

How does this PR make you feel? :link:

Though there are no tests in this package, there is a demo that contains some different use cases.  It is useful to ensure that all of the examples still operate properly.

If this will cause a regression to the sombrero-demo, then it should be addressed as part of this story.

@brentertz , I see the Sombrero demos, but it's not always well documented, what the exact expected behaviors are.
We do want a drop on a nested drop target to trigger a drop on the parent drop target; there is a test in alm-guitests which is this scenario.  The linked defect goes into some more detail.

Perhaps I should say... for the purposes of the team planning page in manual ranking mode, which shows a defect when using react-dnd 0.9.6-rally.9, we want the drop to trickle through to the outer nested drop.  When we are in manual ranking, the Sombrero DataTable that renders the stories in the iteration view disables drag & drop.  In 0.9.6-rally.6, the logic somehow got the drop event to the outer drop, so we could drop to the table as a whole.  With the current version, the drop goes to the inner target, and halts there -- the only way to recognize the table as a drop target was to drag over the header row first.
If this behavior is bad for other parts of our app, I haven't seen a test yet which breaks it.

Do not merge yet: we are not correctly handling sort order for nested drop targets.

Only thing I'm still a bit concerned about is adding more logic to these handlers that get called on every mouse mouse event. Might want to double check that it hasn't introduced any extra lag on crappy hardware. Other than that it looks good.

I will check on it.  I feel that it shouldn't be too much worse -- thankfully this is only applied during a drag, and the number of drop targets was already reduced (in the original code) to just what's under the mouse.  In the most heinous situations that I've seen... that's 2.  Will update after doing some comparisons.

I used the Team Plan page to test dnd from the backlog to an iteration.  The Chrome tools are extremely helpful, in that they tell me what part of the timeline is spent dragging.  (Thanks, Chrome!)
react-dnd 0.9.6-rally.9: almost entirely in the 50-60fps range, with occasional dipping to 40-45fps.
react-dnd 0.9.6-rally.next: almost entirely in the 50-60fls range, with occasional dipping into 30-45fps.

@object88 looks good.
One small thing: the .sort could use a static function instead of a closure.

Will get that in.  Thanks again, @limscoder!


CVE 2023 39325 5.1

Removal of unnecessary image Pull Secrets.
Added retry in case of unreachability to IAM endpoint
Golang update to 1.20.10

/ok-to-test

coverage: 83.302%. remained the same when pulling 71d9cfdb0c67160458826d2dcba3b4d5a70e6903 on GunaKKIBM:CVE-2023-39325-5.1 into 48da04b0d3f20de0b5388563a2f7e8645571a34a on kubernetes-sigs:v5.1.

/lgtm


Quiz moodle joneice clean

This is my course list UI

I have updated the UI to reflect the suggestion.

Closed due to contributing element of this branch (the course list UI) having been added in another pull request.


[Nox.Ui] Create Initial skeleton Cryptocash.Api Phase1 based on existing sampleWebApi project

Have attached Seed sql script for now to populate database for testing - whilst awaiting ETL process from config to seed data see: https://github.com/NoxOrg/Nox.Generator/issues/588
Seed_Cryptocash_SQLSERVER.zip


Fix additionalAttributeNames in UpdateItemCodableInput by mapping key array

#671 has introduced a new method to initialize UpdateItemCodableInput, but it has introduced an issue.
Consider the following code:
private struct AdditionalAttributes: Encodable {
        let keyName: String
        let oldUpdatedAt: String
}

func updateItem<T: BreezeCodable>(item: T) async throws -> T {
        var item = item
        let oldUpdatedAt = item.updatedAt ?? ""
        let date = Date()
        item.updatedAt = date.iso8601
        let attributes = AdditionalAttributes(keyName: keyName, oldUpdatedAt: oldUpdatedAt)
        let input = try DynamoDB.UpdateItemCodableInput(
            additionalAttributes: attributes,
            conditionExpression: "attribute_exists(#keyName) AND #updatedAt = :oldUpdatedAt AND #createdAt = :createdAt",
            key: [keyName],
            tableName: tableName,
            updateItem: item
        )
        let _ = try await db.updateItem(input)
        return try await readItem(key: item.key)
}

The intention of the previous code is to update the item only when the key exists and when the record to update has the same createdAt and updatedAt data stored in DynamoDB. The update will change updatedAt with a new timestamp. In this way a client that doesn't have the same item cannot update the DynamoDB table and is forced to read the item before an update. (Optimistic locking)
But it leads to the following exception:
test_updateItem(): failed: caught error: "ValidationException: Value provided in ExpressionAttributeNames unused in expressions: keys: {#oldUpdatedAt}"

To fix the issue the code has be changed to include only the key in additionalAttributeNames and avoiding to add attributes that are not used.
The client code can be fixed by using:
private struct AdditionalAttributes: Encodable {
        let oldUpdatedAt: String
}

func updateItem<T: BreezeCodable>(item: T) async throws -> T {
        var item = item
        let oldUpdatedAt = item.updatedAt ?? ""
        let date = Date()
        item.updatedAt = date.iso8601
        let attributes = AdditionalAttributes(oldUpdatedAt: oldUpdatedAt)
        let input = try DynamoDB.UpdateItemCodableInput(
            additionalAttributes: attributes,
            conditionExpression: "attribute_exists(#\(keyName)) AND #updatedAt = :oldUpdatedAt AND #createdAt = :createdAt",
            key: [keyName],
            tableName: tableName,
            updateItem: item
        )
        let _ = try await db.updateItem(input)
        return try await readItem(key: item.key)
}

In the Unit Tests, the optimistic locking has been tested using id as key and age as condition to validate the record.
An alternative solution could be to add an explicit parameter to additionalAttributeNames.

Swift 5.8 failed https://github.com/soto-project/soto/actions/runs/5275592595/jobs/9541238015?pr=673#step:5:8784
Maybe localstack getting it wrong though

The age in the example was updated to 33 to prove that conditional update works when executed against the last update.
All seems ok.
Still in doubt if It's better to have explicit parameter for additionalAttributeNames.
For implementing optimistic locking this seems enough.

Just re-running the tests. I can't get them to fail locally with local stack.


chrom fetch sizes has issues reading yeast chromosomes (latin numbering?)

Check output of bioframe.fetch_chromsizes('sacCer3') in screenshot. It seems like only chrX and chrM are fetched, possibly because chromosomes of yeast are labelled with latin numbering (?).
Thank you!

good guess! did you try a chrom.sizes file with renamed chrms?
On Fri, May 24, 2019 at 11:32 AM Marlies Oomen<EMAIL_ADDRESS>wrote:

Check output of bioframe.fetch_chromsizes('sacCer3') in screenshot. It
seems like only chrX and chrM are fetched, possibly because chromosomes of
yeast are labelled with latin numbering (?).
Thank you!
[image: image]
https://user-images.githubusercontent.com/16121171/58349056-46a10b00-7e30-11e9-9072-16bc7779dc34.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mirnylab/bioframe/issues/12?email_source=notifications&email_token=AEV7GZMXKPLEBAIBTTCFQXDPXAYC3A5CNFSM4HPRZMK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GVYRTRQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEV7GZLPSDNSVJPIR7BCOYLPXAYC3ANCNFSM4HPRZMKQ
.

Never mind, we just found the solution in the code! You can add a parameter. Running it likes this works:
chromsizes = bioframe.fetch_chromsizes('sacCer3',all_names=True)

nice!
On Fri, May 24, 2019 at 11:36 AM Marlies Oomen<EMAIL_ADDRESS>wrote:

Never mind, we just found the solution in the code! You can add a
parameter. Running it likes this works:
chromsizes = bioframe.fetch_chromsizes('sacCer3',all_names=True)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mirnylab/bioframe/issues/12?email_source=notifications&email_token=AEV7GZKJA6LEKMD5Z7NRLETPXAYTFA5CNFSM4HPRZMK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWGIC5Y#issuecomment-495747447,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEV7GZIAN53MMRPO4G5JMT3PXAYTFANCNFSM4HPRZMKQ
.

Nezar, this is not the first time people are running into this issue
(myself included, twice). Maybe we should set all_names to True by default?
Anton.
(typed on a phone, sorry for brevity and typos)
On Fri, May 24, 2019, 14:39 Marlies Oomen<EMAIL_ADDRESS>wrote:

Closed #12 https://github.com/mirnylab/bioframe/issues/12.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mirnylab/bioframe/issues/12?email_source=notifications&email_token=AAG64CQEKNBADULCX62HGMLPXAY6ZA5CNFSM4HPRZMK2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORUGFR7A#event-2366396668,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAG64CVYADTIYNUPPNGEZCLPXAY6ZANCNFSM4HPRZMKQ
.


circumflex: 2.6 -> 2.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bensadeh/circumflex/releases.
meta.description for circumflex is: A command line tool for browsing Hacker News in your terminal
meta.homepage for circumflex is: https://github.com/bensadeh/circumflex
Updates performed

Golang 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 2.8 with grep in /nix/store/czzc59pvs6p856qhpja9d07p6idf30jj-circumflex-2.8
found 2.8 in filename of file in /nix/store/czzc59pvs6p856qhpja9d07p6idf30jj-circumflex-2.8

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
circumflex

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/czzc59pvs6p856qhpja9d07p6idf30jj-circumflex-2.8 \
  --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 circumflex https://github.com/r-ryantm/nixpkgs/archive/99639b329f0ef67dc531f8858c34006da2cae8ed.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/czzc59pvs6p856qhpja9d07p6idf30jj-circumflex-2.8
ls -la /nix/store/czzc59pvs6p856qhpja9d07p6idf30jj-circumflex-2.8/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:

circumflex

Maintainer pings
cc @mktip for testing.

@ofborg build circumflex circumflex.passthru.tests


Missing bool from Data.Bool

raycast.hs:6:19: Module ‘Data.Bool’ does not export ‘bool’

Easy to implement:
bool :: a -> a -> Bool -> a
bool f _ False = f
bool _ t True  = t

This is caused by Haste using a patched base from GHC 7.6, where bool wasn't implemented yet. Will be fixed when 7.10 support arrives, since all of base will be getting upgraded to the latest version this time around.

Ah, I see. I didn't realise bool was a recent addition. :)

Fixed on master with GHC 7.10.


Error verifying, FirebaseError: internal

Describe the bug
Error verifying, FirebaseError: internal displayed after some time after resuming the contribution
To Reproduce
Start a contribution - get a timeout - reopen the page and start the contribution again. In my case I did that twice after getting a timeout twice (and also switching between ceremonies). Cannot specify the exact sequence, but if I remember correctly, first started the RLN ceremony, it timed out, then retried it, it timed out again, then switched to MACI, later it timed out, then switched to RLN again and got the error.
Expected behavior
Not showing the error.
Screenshots

Desktop (please complete the following information):

OSX 13.5
Firefox 116.0.2

Thanks for reporting this, I fixed it here https://github.com/privacy-scaling-explorations/DefinitelySetup/pull/87 - please try again when you get a chance.


Laravel 5.3 upgrade

Coverage decreased (-3.3%) to 44.292% when pulling 3d536de8d11a0c55e95b03bea1ca428a37fe2b56 on laravel_53_upgrade into<PHONE_NUMBER>96ef5609057f37083f244cd4659924 on master.

Coverage increased (+8.003%) to 55.55% when pulling ca4c7841af129faa0ce2ab80f20aa9861522a358 on laravel_53_upgrade into<PHONE_NUMBER>96ef5609057f37083f244cd4659924 on master.

@GrupaZero/developers It's ready for review

Coverage increased (+8.1%) to 55.669% when pulling 850110c167c0ac2749c87cb8efaf11d43c33a3b7 on laravel_53_upgrade into<PHONE_NUMBER>96ef5609057f37083f244cd4659924 on master.

Coverage increased (+7.9%) to 55.49% when pulling 6216a5694887439cef74ea483594426dd094aede on laravel_53_upgrade into<PHONE_NUMBER>96ef5609057f37083f244cd4659924 on master.


Blog post links directly to mac dmg only (twice) instead of GH releases

https://medium.com/@graphcool/f1e0a018f05d

We're linking two times to the GitHub repo, in the first and in the last paragraph. And two times to the direct download, once in the caption of the header image and another time two paragraphs after that image.
Which links would you expect to be different?

I meant the two direct download links. The Github repo readme points to the releases on Github, which is also still empty, but I think it makes sense they link to a place where you can find the executables for all platforms, right?

I see, thanks for the hint! I think you're right and we should link to the GitHub releases. I updated the links in the blog post accordingly.


ParameterExpression throws an error for gradients with complex coefficients.

Information

Qiskit Terra version: 0.18
Python version: 3.8
Operating system: MacOS

What is the current behavior?
When having a ParameterExpression with an imaginary unit, taking a gradient w.r.t. a parameter existing in a ParameterExpression results in an error.
Steps to reproduce the problem
p = Parameter("theta")
p2 = 1j*p
p2
Out[27]: ParameterExpression(1.0*I*theta)
p2.gradient(p)
Traceback (most recent call last):
  File "/qiskit-terra/venv/lib/python3.8/site-packages/IPython/core/interactiveshell.py", line 3437, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-28-058190e5d73e>", line 1, in <module>
    p2.gradient(p)
  File "/qiskit-terra/qiskit/circuit/parameterexpression.py", line 303, in gradient
    return float(expr_grad)
  File "symengine_wrapper.pyx", line 1133, in symengine.lib.symengine_wrapper.Basic.__float__
  File "symengine_wrapper.pyx", line 958, in symengine.lib.symengine_wrapper.Basic.n
  File "symengine_wrapper.pyx", line 4194, in symengine.lib.symengine_wrapper.evalf
RuntimeError: Not Implemented

What is the expected behavior?
Calculating a gradient with a complex coefficient.
Suggested solutions
Perhaps
  File "/qiskit-terra/qiskit/circuit/parameterexpression.py", line 303, in gradient
    return float(expr_grad)

should be changed to
  File "/qiskit-terra/qiskit/circuit/parameterexpression.py", line 303, in gradient
    return complex(expr_grad)

?

Perhaps it is. Seems to fix the problem. I can take this one.


Minor: Switch LastValue SQL workflow to UDAF version

Which issue does this PR close?

Closes #.
Part of https://github.com/apache/arrow-datafusion/issues/8708
Rationale for this change
After this change, LAST_VALUE goes to the registered UDAF instead of builtin one.

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Then I think we need to support ordering for the window function before this

To support replacing window first/last, there are many issues to be solved.
Including replacing first/last in convert_firsts_last rule, and support sliding accumulator for udaf, and support list instead of NUMERIC signature.

To support replacing window first/last, there are many issues to be solved.

I wonder if starting with simpler aggregates (like approx_distinct) might be a good idea. They are probably simpler to port and would let us work through some of the details before breaking off the larger more complex ones
first_value / last_value are likely the most complex as they are order aware and can be used as aggregates and window functions

To support replacing window first/last, there are many issues to be solved.

I wonder if starting with simpler aggregates (like approx_distinct) might be a good idea. They are probably simpler to port and would let us work through some of the details before breaking off the larger more complex ones
first_value / last_value are likely the most complex as they are order aware and can be used as aggregates and window functions

While I try to deprecate first/last, I found that window function can works with UDAF without additional change.

Including replacing first/last in convert_firsts_last rule, and support sliding accumulator for udaf, and support list instead of NUMERIC signature.

The issue I mentioned is part of a need for deprecating first/last, not for window function.


Vim window display issues when resizing on Hyprland with xterm-kitty

When running Vim on Hyprland with the xterm-kitty terminal emulator, resizing the terminal window causes the Vim window to break.
https://github.com/hyprwm/Hyprland/assets/50273941/8483379f-1235-4be6-b237-21124cfa491d

Hyprland version
Hyprland, built from branch main at commit 7f0738bcb3647f766427706b28a1f72677de9b1b dirty (varlist: allow using s for std::isspace).
Tag: v0.25.0-13-g7f0738bc

Kitty
kitty 0.28.1 created by Kovid Goyal

Vim version
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Apr 06 2023 14:24:38)
Included patches: 1-1420
Compiled by Arch Linux

Solution
set TERM xterm-256color
https://github.com/hyprwm/Hyprland/assets/50273941/5fada948-d409-4bf5-80ff-95c0d53a4cd4

well, i just install sudo pacman -S vim kitty and this happen, i never faced this issue before only in hyprland, this is a hyprland issue, but you can close because the solution is really simple, i open this issue just to help others.

kitty issue then.

kitty issue then.

yes you right, i tested in xfce4 and the same issue happen

@maxmx03 Have you resolved this issue now? It still persists when I use kitty.

@maxmx03 Have you resolved this issue now? It still persists when I use kitty.

Yes, here the solution:
# term xterm-kitty
term xterm-256color

@maxmx03 Have you resolved this issue now? It still persists when I use kitty.

Yes, here the solution:
# term xterm-kitty
term xterm-256color

thx,that works fine :)


update markdown-it dependency

Currently this package is using an outdated and vulnerable version of markdown-it.
See https://snyk.io/test/npm/markdown-it-multimd-table
Can you please bump the dependencies to markdown-it@^11 ?

Sorry for late reply.
Dependency got updated to markdown-it^11.0.0. Thanks for the report!

@RedBug312 Thanks for updating. Could you please publish the updated version on npm?

Sure. Just published as version 4.0.3. :smiley:


NEP-5 withdrawals are not secured

Runtime.Verification only secures System Asset withdrawals.

Closed by https://github.com/ConjurTech/switcheo/commit/a6314e17e7c1e704612df7c80bdd393e7fe2dfbc


go/internal/gcimporter: detect and gracefully fail on old versions

gcimporter does not fail gracefully when it encounters old versions. This trips up a lot of people--they think it's a bug, and do not think to re-install the relevant packages (why would they?). Related bugs: #16879 and #16859 and #16112 and #15728 and #16826 and #16781 and lots more. I think at this point some kind of fix, even a kludgy one, is called for.
The best case scenario, to my mind, is that importers just work (#10276). Failing that, gcimporter should treat the input package as potentially hostile (i.e. as user input) and on error, suggest a package re-install. Failing that, gcimporter should explicitly check for and recognize known prior versions and suggest a package re-install.

The new export format does recognize old versions and does try to work gracefully around them.
Many of the prior issues had to do with the transition from textual to binary format. The textual format had no versioning, and the binary format was in development, with people using mixes of the two, and sometimes even mixes of two different binary formats.
The "gracefully working around issues" was done only partially (in x/tools/gcimporter) as I (wrongly) assumed that people would always re-build when working at tip (we don't guarantee anything across different compilers). That's obviously not the case.
The trivial solution is to bail with an explicit error requesting recompiles - at least when working at tip. It's a bit more complicated than that because x/tools/gcimporter15 also needs to work on tip but also legacy installed packages.
On it.

This issue (and how to fix it: what must be rebuilt/reinstalled) should be mentionned in Go 1.7 release notes.


Search boosts

Fix for #1929
Add some config options to enhance search behavior (mainly for large projects that produce a large result set when searching):

add search config to typedoc.json (todo: I don't know where to edit the schema definition)
add boost logic to Search.ts, so that user can increase relevance based on exactMatch, kind, or category
add numResults (I don't really need this one, I just thought it would be a good first exercise, but it is useful for troubleshooting)

Notes:

category boosts don't currently work in the example app, as I couldn't figure out how to switch on the category plugin... please advise
the search config is a big crazy object, whereas all the config options tend to be scalar or array types, presumably so that they can also be set via command line; not sure what to do about that
I think @Gerrit0 wants some or possibly all of this to be on by default, which would certainly simplify above problems.

Great library, thanks so much.

todo: I don't know where to edit the schema definition

This gets automatically generated by scripts/generate_options_schema.js when a new version is published.

category boosts don't currently work in the example app, as I couldn't figure out how to switch on the category plugin... please advise

The category plugin only does things if the @category tag is used in the project, it looks like the example project doesn't use it right now.

@Gerrit0 ready for another look when you have time.

Very good Now get in there and make it happen I'm counting on you and thanks

I'm liking the look of this! Things I want to look at when I have more than a few minutes:

Can we pre-compute the group boost too, and just ship a "boost" field in the frontend?
Option validation functions for both searchCategoryBoosts and searchGroupBoosts to prevent someone doing something dumb like { asdf: [] }

Can we pre-compute the group boost too, and just ship a "boost" field in the frontend?
Option validation functions for both searchCategoryBoosts and searchGroupBoosts to prevent someone doing something dumb like { asdf: [] }

3601b26e
Added validation for searchGroupBoosts, but I'm not sure how to validate the category names, as they're not known until the reflection is complete.

@Gerrit0 Sorry for being a pest, but is there any way we can get this merged? My team and I are sort of waiting on this, and if any problems arise I'm around to fix them--just say the word.

I should be able to get this in on Monday -- life has been really busy the past couple weeks

Hey, thanks for merging. 👍
I see you added tests and some extra bits of business; much obliged, I'll take it out for a spin tomorrow.


Fix typo

@roj1512 does CI fail because the commit on main does not have the correct labels? Does this mean we should add a check for the branch?

No wait, it succeeds on main … what's going on here

No idea.

I think we should debug it.


Random classification baseline does not work when using accuracy in constraint strings

When constraint strings include ACC, such as min((ACC | [democrat])/(ACC | [republican]),(ACC | [republican])/(ACC | [democrat])) >= 0.8, running the random classification baseline will cause an error below:
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 239, in _process_worker
    r = call_item.fn(*call_item.args, **call_item.kwargs)
  File<EMAIL_ADDRESS>line 198, in _process_chunk
    return [fn(*args) for args in chunk]
  File<EMAIL_ADDRESS>line 198, in <listcomp>
    return [fn(*args) for args in chunk]
  File<EMAIL_ADDRESS>line 285, in run_baseline_trial
    parse_tree.evaluate_constraint(theta=solution,
  File<EMAIL_ADDRESS>line 727, in evaluate_constraint
    self._evaluator_helper(self.root,
  File<EMAIL_ADDRESS>line 779, in _evaluator_helper
    self._evaluator_helper(node.right,
  File<EMAIL_ADDRESS>line 777, in _evaluator_helper
    self._evaluator_helper(node.left,
  File<EMAIL_ADDRESS>line 777, in _evaluator_helper
    self._evaluator_helper(node.left,
  File<EMAIL_ADDRESS>line 768, in _evaluator_helper
    value = node.calculate_value(
  File<EMAIL_ADDRESS>line 140, in calculate_value
    value = evaluate_statistic(model,
...
--> 388         raise self._exception
    389     else:
    390         return self._result

AttributeError: 'NoneType' object has no attribute 'ndim'

This is a bug in the Engine. I addressed the problem in this commit: https://github.com/seldonian-toolkit/Engine/commit/e2e6932977f0cca6d59133f2ba974157e70b7d00
It is resolved in v0.7.4 of the seldonian-engine PyPI package


Add shifuctl to Makefile

What this PR does / why we need it:
This PR adds shifuctl to Makefile.
Will this PR make the community happier?
Yes. People can now build the powerful tool with ease.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
How is this PR tested

[ ] unit test
[ ] e2e test
[ ] other (please specify)

Special notes for your reviewer:
Release note:

Do we still need this PR with https://github.com/Edgenesis/shifu/pull/442?

Do we still need this PR with #442?

No. I'll close this one.


Code does not display nicely

Expected Behavior
Show text in {code} tags nicely formatted.
Actual Behavior
Text runs off the page.
Steps to Reproduce the Problem

Create a Jira issue with {code} tags
View in Jira and then notice the difference in Chronos

Specifications

Chronos-timetracker version: 3.0.0
OS: macOS 10.4.3

It displays a little bit different, without highlight, but description return from api in html format, so we display what jira returns, if they fix it, it will work,


(pouchdb/pouchdb#4798) - use git master for tests

After pouchdb/pouchdb#4798, it's no longer safe to
use the npm version of pouchdb to test itself, because
the test files won't be in there.

Does that mean the 'npm install' line in test-pouchdb.sh can go?
Otherwise looks good, :+1: when green.

No, the npm install is still necessary in order to install the dependencies of pouchdb itself.

Right, forgot about the dev dependencies.

Tracking this in https://github.com/pouchdb/express-pouchdb/issues/276

OK, this is working correctly. It's just a known bug in pouchdb-server/express-pouchdb that is causing Firefox to fail. This has been known for forever and we should fix it; maybe the red "broken" badge will motivate us.

Good point.


Update FreeRTOS to 10.4.5 or newer (IDFGH-5391)

Is your feature request related to a problem? Please describe.
Hello, I would like to request an update for FreeRTOS. The current release/4.3 apears to be working on version 10.2.1, which is quite outdated at this point. In the current version of FreeRTOS they have some interesting features that I would like to use in my project.
The one that I'm really looking forward to use is ulTaskNotifyTakeIndexed function, because they claim, that this function is 45% faster than standard ISR handling by using semaphore.
https://www.freertos.org/RTOS_Task_Notification_As_Counting_Semaphore.html
Describe the solution you'd like
I would like to have an updated version of FreeRTOS in the closest release. I'm not sure at this moment if ESP-IDF is using just the kernel of FreeRTOS, or the whole FreeRTOS subsystem, but when I look a those releases, they look juicy as hell!
https://github.com/FreeRTOS/FreeRTOS/releases
https://github.com/FreeRTOS/FreeRTOS-Kernel/releases
So updating FreeRTOS to version 10.4.4, or 202104.00 seems to have the most sense for now.
Describe alternatives you've considered
For now I'm sticking with ulTaskNotifyTake, which is fine, but if I can provide a better way to utilize my ESP, then I want to do this.
I've also considered to update freertos by my self, but my lack of experience with embeded systems may result in more problems than benefits. That's why I would like that this component got updated by experienced team. Especialy it looks like the freertos required some porting for it to work with esp.

Hi @DawidDiaco,
Thanks for bringing this up. Agree there are some nice features in these newer FreeRTOS releases.
ESP-IDF uses the FreeRTOS kernel, with modifications for SMP (dual core) support. Because of the kernel modifications, updating is more risky than just using the new kernel source - new features may need modifications to work correctly and careful testing to make sure they work in the SMP configuration and don't introduce subtle bugs or regressions. It's quite a lot of work to update.
That said, we will consider updating to pick up these new features. I can't give you any ETA on this, sorry.
Long term, FreeRTOS team has recently created a development branch with an official SMP kernel and we're looking to move ESP-IDF to this, but such a change will require a major version update as the behaviour is different and some APIs will break. If/when we use the official upstream SMP kernel then updating to new upstream versions will become much simpler!
Angus

Thank you for your explanation. I think I can live with the current version of FreeRTOS, but I will be patiently waiting for updates.
For now you can close this ticket, or mark it as whatever is appropriate in this case.

Hi @projectgus
I notice below issues was fixed in upstream FreeRTOS.
Would you mind take a look if the esp-idf needs the fix.
https://github.com/FreeRTOS/FreeRTOS-Kernel/pull/117
https://github.com/FreeRTOS/FreeRTOS-Kernel/commit/82df39764a813970ba1071ac064063ea010ebed8
https://github.com/FreeRTOS/FreeRTOS-Kernel/pull/118
https://github.com/FreeRTOS/FreeRTOS-Kernel/commit/b9748e50eaafdb20a0c2438c0286a255c3f59e4c
I create a gist to make it easier to check the diff (without whilte space change) for above fixes:
https://gist.github.com/AxelLin/500cdc3414fac7ba291d2df54239fd6c

@DawidDiaco Current IDF master (20847eeb96c486629a678d6ffbe73670013fb771) should already have updated FreeRTOS to v10.4.3. Closing this issue, please feel free to reopen.

@DawidDiaco
@Dazza0
Can please reopen this issue.
The ability to change ulRunTimeCounter to uint64_t is a very valuable feature for us since it will enable far longer periods of per task processor utilization trending.
Currently we have to run a routine is an idle task to detect and handle wrapping of the runtime counter, an unnecessary kludge.

@ammaree Could you specific exactly which FreeRTOS version you want?

10.4.5 or newer
Sent from my iPhone
On 15 Feb 2022, at 08:00, Darian @.***> wrote:

@ammareehttps://github.com/ammaree Could you specific exactly which FreeRTOS version you want?
—
Reply to this email directly, view it on GitHubhttps://github.com/espressif/esp-idf/issues/7137#issuecomment-1039889464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYT7GH5NORULHICSAVTQEDU3HTWVANCNFSM46RDH3XQ.
You are receiving this because you were mentioned.Message ID: @.***>

@ammaree Could you specific exactly which FreeRTOS version you want?

I think @ammaree want this feature:
https://github.com/FreeRTOS/FreeRTOS-Kernel/blob/main/History.txt#L31-L34

Absolutely correct
Sent from my iPhone
On 15 Feb 2022, at 09:04, Axel Lin @.***> wrote:

@ammareehttps://github.com/ammaree Could you specific exactly which FreeRTOS version you want?
I think @ammareehttps://github.com/ammaree want this feature:
https://github.com/FreeRTOS/FreeRTOS-Kernel/blob/main/History.txt#L31-L34
—
Reply to this email directly, view it on GitHubhttps://github.com/espressif/esp-idf/issues/7137#issuecomment-1039925769, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYT7GBTE3P34TWSQHYIKB3U3H3JFANCNFSM46RDH3XQ.
You are receiving this because you were mentioned.Message ID: @.***>

@Dazza0
Any chance of on update on this functionality?

@ammaree We're still discussing whether to upgrade to v10.4.3. Our main concern right now is that v10.4.3 is an LTS version. Given that we are going to move over to the SMP Kernel, preferably want to leave the legacy kernel on an LTS version.
If this ends up being the case, then will backport specific functionality from later versions (such as the configRUN_TIME_COUNTER_TYPE feature in this case). However, if there are numerous functions required from v10.4.5, then we may also consider upgrading.
@ammaree do you have any preference w.r.t the two approaches mentioned above?

Our only requirement is for the 64bit runtime counters so you welcome to choose the option that would be the least effort and quickest.
Other users might requirement additional 10.4.5 functionality but cannot speak for them.

@ammaree We're still discussing whether to upgrade to v10.4.3. Our main concern right now is that v10.4.3 is an LTS version. Given that we are going to move over to the SMP Kernel in the future, we preferably want to leave the legacy kernel on an LTS version.

According to the FAQ https://www.freertos.org/faq-lts.html#question2 , the support period for FreeRTOS LTS libraries is two years.
V10.4.3 was released on 15 Dec 2020, so it will reach the end of TLS support period by the end of this year.
Given such timing it's probably fine to move to newer version (or next TLS version).

FYI, V10.5.0 released.
https://github.com/FreeRTOS/FreeRTOS-Kernel/releases/tag/V10.5.0

@ammaree We're still discussing whether to upgrade to v10.4.3. Our main concern right now is that v10.4.3 is an LTS version.

@Dazza0
FYI, New FreeRTOS Long Term Support version released
https://freertos.org/2022/10/new-freertos-long-term-support-version-released.html

@Dazza0 as per @AxelLin post above
+99999 for for leaving legacy kernel on the just released new FreeRTOS LTS version.
That will leave those that are remaining on v4.x.x on a version with a long lifetime ahead...
AND
It will allow those of us on v5.x to continue with the same latest version until you have completed the move to SMP kernel

@Dazza0
Just remind that the FreeRTOS LTS 202012 will be EOL by end of next month.
I think you should prepare upgrading to new LTS version ASAP to avoid using an EOL version of FreeRTOS for esp-idf-4.4+.
Cc @igrr (in case if no response from @Dazza0 )

We will evaluate this, but since IDF 4.4.x service period is ending soon, we might end up keeping the existing version of FreeRTOS in release/v4.4, to avoid regressions or app behavior changes due to an upgrade.
Even though it will be EOL for support from upstream, we will still provide support in terms of fixes for security issues and critical issues, by backporting relevant fixes from the newer upstream releases.

We will evaluate this, but since IDF 4.4.x service period is ending soon, we might end up keeping the existing version of FreeRTOS in release/v4.4, to avoid regressions or app behavior changes due to an upgrade.

FYI: There is no API change (compared to previous LTS version)  for the FreeRTOS Kernel part.
https://freertos.org/2022/10/new-freertos-long-term-support-version-released.html

We will evaluate this,

AFAICT, the espressif's response is too slow.
4 Months ago I already pointed out new FreeRTOS LTS version is available by https://github.com/espressif/esp-idf/issues/7137#issuecomment-1340461360 .
The esp-idf is using a EOL version of FreeRTOS now.

@Dazza0  @igrr
I notice in master repo that we have 'FreeRTOS-Kernel-V10.5.1' there. this OK to use?
Any instructions on selecting and using this new kernel?

Not yet, it is in progress at the moment:
https://github.com/espressif/esp-idf/blob/903af13e847cd301e476d8b16b4ee1c21b30b5c6/components/freertos/Kconfig#L6-L11
https://github.com/espressif/esp-idf/blob/903af13e847cd301e476d8b16b4ee1c21b30b5c6/components/freertos/CMakeLists.txt#L34-L35

Thanks @igrr
Any estimated timeframe for having a "testable" version in master?

Not yet, it is in progress at the moment:

I'm wondering if FreeRTOS-10.5.1 fixes this issue: https://github.com/espressif/esp-idf/issues/8849

@AxelLin I will check
@ammaree we are actively working on this at the moment, at the end of Q3 we should have version for RISC-V chips

Thanks for the feedback but an estimate of Q3 for the RISC-V is of no value to us.
The requirement is for the ESP32[S2/S3] not for RISC-V.
Leaving customer still supporting the original ESP32 out for this long on 10.4.3 is very painful and sad.
On 23/07/14, 05:25, "Zim Kalinowski"<EMAIL_ADDRESS>wrote:
@AxelLinhttps://github.com/AxelLin I will check
@ammareehttps://github.com/ammaree we are actively working on this at the moment, at the end of Q3 we should have version for RISC-V chips
—
Reply to this email directly, view it on GitHubhttps://github.com/espressif/esp-idf/issues/7137#issuecomment-1635213181, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYT7GGLO4MSWLMQB37APK3XQC32BANCNFSM46RDH3XQ.
You are receiving this because you were mentioned.Message ID: @.***>

@AxelLin I will check

So how is the status? Any update?

@AxelLin I will check

However, I don't get further response at all. @zikalino

@igrr
@Dazza0
@zikalino
This issue is almost 20 months old, from the date of it being reopened at my request. We are STILL, 20 months later, on an LTS version of FreeRTOS that is EOL.
We accept the argument of the older version being retained with the IDF 4.4.x releases/updates, but to still be using the EOL RTOS with IDF v5.2, that is a serious problem.
Also not sure why the "focus" on upgrading the RTOS for C3 series, surely ESP32/S2/S3 should receive same if not higher priority?

@AxelLin @ammaree The FreeRTOS upgrade has already been merged internally and is waiting sync to GitHub.

@AxelLin @ammaree The FreeRTOS upgrade has already been merged internally and is waiting sync to GitHub.

@Dazza0
But that is not the question I asked, see https://github.com/espressif/esp-idf/issues/7137#issuecomment-1627668795
What I asked is if the fixes in newer FreeRTOS release fixes the bug in current FreeRTOS in esp-idf.
What I care is if current release branches are stable because the reported issue is still open.

@AxelLin

For issue #8849, no this has not been fixed in v10.5.1 (and there is no easy way to fix this as I've described in the issue comments)
For the other v10.6.0 fixes, we'll need to selectively backport them to v10.6.0 depending on severity.

@AxelLin @ammaree The FreeRTOS upgrade has already been merged internally and is waiting sync to GitHub.

Any idea how long the delay to finally get to GitHub?
We are already another 3 days later and still nothing...

FYI, FreeRTOS-v11.0.0 released. (SMP merged into the mainline)
https://github.com/FreeRTOS/FreeRTOS-Kernel/releases/tag/V11.0.0

FYI, FreeRTOS 202406.00-LTS
https://github.com/FreeRTOS/FreeRTOS-LTS/releases/tag/202406.00-LTS


[config] change default (<IP_ADDRESS> -> localhost) for debug interface

This might be a breaking change for validators, depending on their configuration and how they are deployed.

Correct me if I'm wrong, but if we want to do this, we would need to update all of our deployment configurations, tutorials, and documentation. And also as far as I understand, no one is running this software on bare metal?
@mimoo perhaps the better approach is to document in the deployment process that if you do deploy this on bare metal, here are the risks.
cc: @mgorven

btw this PR is not here to drive this work, I just wanted to point out that we were exposing these publicly :) a volunteer needs to drive a change to secure default configurations :D

Then why submit this :P


Gs/code improvement

Add category file in the config of the examples
Change the crs for the original image path in the detection attributes
Remove the control that there are the same number of class in every coco file, all categories are always saved to the "categories" part of the COCO files.
Add possibility to assess results with a predefined confidences score.

This PR is part of the conclusion of the project on border points.


[Enhancement] Add function serialize/deserialize/serializeToString to BitmapValue

Why I'm doing:
User will use hive udf to serialize/deserialize or display BitmapValue, so i add three function, this function will be used by later hive udf framework.
What I'm doing:
Add serialize/deserialize/serializeToString to BitmapValue
TODO: BitmapValue that supports set will be modified uniformly in next pr.
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[x] 3.0
[x] 2.5

backport branch-2.5

https://github.com/Mergifyio backport branch-2.5


Make the Dark Theme properly again.

Description of the new feature / enhancement
With update 45 the previous Dark Theme was replaced by a far worse Grey Theme.
It's not only far uglier, it also makes it more difficult to read and white text on grey backgrounds easily gets blurred for anyone without perfect eyesight.
Scenario when this would be used?
I need to be able to read properly the text on my screen. And Grey Themes make that very very hard. So if the Dark Theme isn't done properly (using black), my only option is to use the Light Theme which causes a lot more strain in the eyes.
In other words, I either have to put strain in my eyes with the Light Theme or put strain in my eyes with a Grey Theme that makes text hard to read.
I've reverted to update 43 and I will NOT install Windows 11 for the same reason (even though Microsoft has been made aware of the serious health problems Grey Themes represent time and again).
If this isn't addressed in a future update, I'm afraid I'll have to simply stop using PowerToys which is a shame since it's a tremendously useful productivity tool.
Supporting information
No response

It seems, with WinUI 2.6 and Windows 11, Microsoft is moving away from pure-black to a more grey theme. The reason why these were adopted for PT is that WinUI provides these out-of-the-box.

It seems, with WinUI 2.6 and Windows 11, Microsoft is moving away from pure-black to a more grey theme. The reason why these were adopted for PT is that WinUI provides these out-of-the-box.

Indeed they are. Even though they've been made aware of it being a health issue for many of us. Microsoft willfully disregarded it. Which is why I'm not allowing Windows 11 to be installed on any of my computers.
The question is: can PT provide a proper Dark Theme going forward, or will it only use whatever misguided decisions Microsoft makes by letting the OS indicate the colours for the UI?
'cause depending on that, we the users need to make a choice of either not update PT anymore or completely uninstall it :|

Personally, I prefer the greyer color pallette that WinUI 2.6 and W11 introduce. The contrast between the text on the background colors is a bit less harsh and a bit smoother which I like.
From a developer perspective supporting an additional dark theme means defining a whole new color palette for ALL controls and implementing it. That's quite the effort (while making sure accesibility guidelines are met in terms of contrast).

Fair enough.
In that case, I will not be updating PowerToys anymore as the newer versions will be detrimental to my eyesight. I can't read white text on grey backgrounds.
If it stops working, I'll look for an alternative program.

Fair enough.
In that case, I will not be updating PowerToys anymore (nor recommending it to anyone) as the newer versions will be detrimental to my eyesight. I can't read white text on grey backgrounds.
If it stops working, I'll look for an alternative program. But I hope it doesn't. There's no reason it should stop working I think.

Fair enough.
In that case, I will not be updating PowerToys anymore (nor recommending it to anyone) as the newer versions will be detrimental to my eyesight. I can't read white text on grey backgrounds.
If it stops working, I'll look for an alternative program. But I hope it doesn't. There's no reason it should stop working I think.

You can take 2 things into consideration:

I think this is valud feedback. I'd open an issue in the WinUI repository so the team there can collect your feedback.
We are using solid background colors as the moment. This will however change once we move to WinUI 3. If you'd run the Settings app then it will take the colors from your wallpaper with a "frosted ice" look and feel. This effect is called Mica. If you have a dark wallpaper, I can imagine it will turn the background darker so it might suit your needs better! You can try this effect now already by running the default OS Settings app on Windows 11.

You can try the high contrast mode.
https://support.microsoft.com/en-us/windows/turn-high-contrast-mode-on-or-off-in-windows-909e9d89-a0f9-a3a9-b993-7a6dcee85025

You can try the high contrast mode.
https://support.microsoft.com/en-us/windows/turn-high-contrast-mode-on-or-off-in-windows-909e9d89-a0f9-a3a9-b993-7a6dcee85025

Microsoft's High Contrast Theme is designed for people with very severe visual impairments. It's far too extreme. Most of us who can't read white text on grey backgrounds don't actually need something as extreme as the High Contrast Theme.
I've tried to bring the issue to Microsoft's attention but I doubt they'll do anything. They don't actually listen to external feedback. Never have. Going forward, for now at least, my option will be to not install Windows 11 at all, and not install updates to PowerToys beyond version .43.

Thank you for the feedback @DJCBS, we'll do our best to investigate alternatives and follow up on suitable paths to address this.

We leverage system resources / theming.  I don't see us doing a custom implementation past what it build into the OS

In that case, I won't bother updating and if it stops working, I'll just ditch the product.

This is very typical of Microsoft lately, though: arrogant and lazy.

If you want to help implement something, happy to talk about implementation across the 10+ utilities, how long term support is maintained as well as hot to provide support inside future utilities. It is a lot of work and we are a very small team. I am being honest and open. I do not see the team itself prioritizing this work versus fixing bugs and building out new utilities like we did in 0.55.