Feature: RESTIC_DRY_RUN environment variable

Output of restic version
restic 0.13.1 (v0.13.1-0-g594f155e) compiled with go1.18 on linux/amd64

What should restic do differently? Which functionality do you think we should add?
It might be helpful to have an environment variable which enables/disables the dry-run mode, similar to the RESTIC_REPOSITORY or RESTIC_PASSWORD variables, to complement the --dry-run/-n flag.

What are you trying to do? What problem would this solve?
This would be useful, for example, in a multi-stage Bash script where Restic is invoked multiple times. Instead of adding/removing the --dry-run flag in multiple places, one could just add/remove export RESTIC_DRY_RUN=true (or at least, I think that's right).

Did restic help you today? Did it make you happy in any way?
 :)

I see two problems with that:

not all command implement a dry-run mode. Now, if you specify the --dry-run option for a command that doesn't support it, this will result in an error. With an environment variable, the variable would just be ignored and restic would unexpectedly modify the repository.
With an environment variable it would be much harder to see whether a command runs in dry-run mode. But for most dry-run use cases, I really want to be sure that the mode is active.

Now, if you specify the --dry-run option for a command that doesn't support it, this will result in an error

Granted I don't know anything about the internals of Restic and how it works, but couldn't the environment variable being set cause the same reaction? Is it possible to have a command fail in the same way as it would if --dry-run was specified if RESTIC_DRY_RUN specified?

I really want to be sure that the mode is active.

Could a big warning as soon as the command starts be useful for this? WARNING: Restic is running in dry run mode because RESTIC_DRY_RUN is set. No changes will be made to the repository, etc, etc, etc Colours could even be added to it to give it some extra emphasis.

It could be useful to extend the dry run feature to any action that would cause data change. I am (and have been for some months now) writing a centrally-controlled and monitored secure site backup solution based on restic, and the ability to test using dry run on all potentially modifying commands would be a plus.

While I agree, that's outside the scope of this issue.

True, but it lends credence to the idea of a globally-scoped RESTIC_DRY_RUN flag 😉

Let's all take a step back here :) @codemicro What is your actual use case? What are you trying to or need to do?
I read what you wrote initially and I don't really see the/a need for this flag in that description:

This would be useful, for example, in a multi-stage Bash script where restic is invoked multiple times. Instead of adding/removing the --dry-run flag in multiple places, one could just add/remove export RESTIC_DRY_RUN=true (or at least, I think that's right).

You can simply make a variable in your script, e.g. BACKUP_ARGS="" and make all the invocations to restic backup have $BACKUP_ARGS in the command line, e.g. restic -r foo backup $BACKUP_ARGS /my/stuff. When the variable has an empty value (which it would normally do) the final command that's invoked would be restic -r foo backup  /my/stuff, and if you modify the value of the variable in that script of yours to be --dry-run, then the final invoked command would be restic -r foo backup --dry-run /my/stuff.
In other words, there's no need for an actual environment variable to reach the goal of not having to modify multiple lines every time you want to turn on/off the dry run.

The actual use case was testing a Bash script containing calls to backup and prune. Though, it hadn't crossed my mind that it's possible to do the variable interpolation like that. I'll most likely end up doing that, so thanks for the heads up!
That said, I'd still argue that it's worth having a RESTIC_DRY_RUN variable of some sort. It might not be strictly neccessary, but I think it'd be helpful (though I have had a quick look through the code and appreciate it's not as simple as it might otherwise sound to add).

Could a big warning as soon as the command starts be useful for this? WARNING: Restic is running in dry run mode because RESTIC_DRY_RUN is set. No changes will be made to the repository, etc, etc, etc Colours could even be added to it to give it some extra emphasis.

That direction is not the problem i was worried about. If restic accidentally runs in dry-run mode the worst outcome is wasting time (unless that prevents the backup from ever succeeding, but you want monitoring for that anyways). What I'm more worried about is that someone runs RESTIC_DRY_RUN=true in their terminal, starts messing around with e.g. forget and afterwards wonders why most snapshots have been delete. What went wrong? The environment variable was not exported. We've seen quite a few bug reports with users messing that up...

Yeah, that is an issue, and not one I'd considered.

@MichaelEischer the argument about having BACKUP_ARGS is a valid one.
the argument about people having set an environment variable by accident and now having it forgotten … is a bit shaky: RESTIC_REPOSITORY etc … why do they exist then in the first place if people could get confused about the environment variable and the "-r" flag for example.
i'll now switch to BACKUP_ARGS in my script and dump https://github.com/restic/restic/pull/4072


Cilium Operator does not retrieve lock if kube-apiserver is down

I'm not sure if this only happens in the development machine.
Steps to reproduce the issue:

start Cilium & Cilium-operator in the dev VM.
sudo service kube-apiserver stop
wait ~10 seconds
sudo service kube-apiserver restart
journalctl -fu cilium-operator

The operator never "restarted" its operations.
Sep 15 07:50:37 k8s1 cilium-operator[5814]: level=debug msg="Controller func execution time: 218.122µs" name=restart-unmanaged-kube-dns subsys=controller uuid=d87cab03-f6a4-11ea-8208-080027b966a1
Sep 15 07:50:43 k8s1 cilium-operator[5814]: error retrieving resource lock default/cilium-operator-resource-lock: Get "https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/cilium-operator-resource-lock": context deadline exceeded
Sep 15 07:50:43 k8s1 cilium-operator[5814]: level=error msg="error retrieving resource lock default/cilium-operator-resource-lock: Get \"https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/cilium-operator-resource-lock\": context deadline exceeded" subsys=klog
Sep 15 07:50:43 k8s1 cilium-operator[5814]: level=warning msg="error retrieving resource lock default/cilium-operator-resource-lock: Get \"https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/cilium-operator-resource-lock\": context deadline exceeded" subsys=klog
Sep 15 07:50:43 k8s1 cilium-operator[5814]: level=info msg="error retrieving resource lock default/cilium-operator-resource-lock: Get \"https://<IP_ADDRESS>:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/cilium-operator-resource-lock\": context deadline exceeded" subsys=klog
Sep 15 07:50:43 k8s1 cilium-operator[5814]: level=info msg="failed to renew lease default/cilium-operator-resource-lock: timed out waiting for the condition" subsys=klog
Sep 15 07:50:43 k8s1 cilium-operator[5814]: Failed to release lock: resource name may not be empty
Sep 15 07:50:43 k8s1 cilium-operator[5814]: level=error msg="Failed to release lock: resource name may not be empty" subsys=klog
Sep 15 07:50:43 k8s1 cilium-operator[5814]: level=warning msg="Failed to release lock: resource name may not be empty" subsys=klog
Sep 15 07:50:43 k8s1 cilium-operator[5814]: level=info msg="Failed to release lock: resource name may not be empty" subsys=klog
Sep 15 07:50:43 k8s1 cilium-operator[5814]: level=info msg="Leader election lost" operator-id=k8s1-sJIQbbPYPS subsys=cilium-operator

same here

Same issue!

This issue was closed and has been considered as addressed for nearly four years. If you observed a recent regression, can you please open a new, dedicated issue?


dev to master

Codecov Report

Merging #45 into master will increase coverage by 0.27%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
+ Coverage   38.12%   38.39%   +0.27%
==========================================
  Files         120      120
  Lines       10311    10311
==========================================
+ Hits         3931     3959      +28
+ Misses       5980     5954      -26
+ Partials      400      398       -2

Impacted Files
Coverage Δ

gemmill/blockchain/pool.go
69.92% <0%> (+10.52%)
:arrow_up:


[improvement] Implement panning

When dealing with huge sized photos (e.g. Historic maps), it would be great to be able to pan and zoom the image without having to go back to its reduced display, and double click.
I would recommend OpenSeaDragon as the best open source library to achieve the result.

That is a nice feature. Since it targets not exactly my vision it could be awesome for me for some panorama views or sphere images of my DJI drone.
Currently there are many other issues to fix before supporting such feature. Anyway PRs are welcome ;-)
Also here a defined plugin API would might help to easy extend HomeGallery for such needs and the plugin API needs to be implemented first, too. What a pity.

Closing it due inactivity. Please do not hesitate to reopen it if required.


WFLY-15724: Bump gson version

https://issues.redhat.com/browse/WFLY-15724

Hello, trixpan. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

@jasondlee can you please review this PR.


Add initial rust download to setup target.

Also:

Adjust README.md accordingly.

Signed-off-by: Dan Nussbaum<EMAIL_ADDRESS>Remember to run make prtest and paste the output here (replace this line)

This failed because the automated build is a non-interactive environment, and the command that I folded into make setup is interactive.  We could take steps to make it non-interactive, but that would lose useful flexibility, and the complexity that doing so only for the automated build would not be warranted.  Furthermore, such a change would buy us nothing -- the whole point of the change is to get rid of the gesture associated with the curl command -- leaving it interactive would mean that the gesture is still there.


No such module ARCL

After following the steps mentioned in the setup using cocoapods, I get the following error.

What could be wrong?

Make sure you're opening the the project via .xcworkspace and not the .xcodeproj

Ah. Thank you very much


Circular reference breaks loading in home assistant

Hey.
I think this commit broke the loading into home assistant
Cant load the custom component due to a circular reference which I think is from the below commit, I tested the commit before it and it loads however this commit does not
https://github.com/scottyphillips/echonetlite_homeassistant/commit/9223f8fc916deb66bcd65e1653004040ce509447#diff-fcfdfd9773401069af4737299de4b85f09172755d33da1710560f4a6c2c39cb1R51
Pretty sure this is the offending import as its importing from the fan which also requires the const file
from custom_components.echonetlite.fan import (

@josh-shaw-dev Thanks! 👍


Generate Style Guide from .rubocop.yml

As our team is customizing rubocop to our tastes, we're essentially creating our own fork of the style guide. Wouldn't it be cool if we could generate a custom style guide document from the rules we've defined in .rubocop.yml?
This would probably require the MSGs in cops to be more verbose, with the relevant section of https://github.com/bbatsov/ruby-style-guide

I'd love to see this happen + help start building this out. @bbatsov - if I start working on this, would you consider accepting the feature once it is ready?


Prometheus exporter: omit empty otel_scope_info and otel_target_info metrics

Description
otel_scope_info and target_info should now only be generated when scope attributes and resource attributes are non-empty.
From https://github.com/open-telemetry/opentelemetry-specification/pull/3660:

Prometheus exporters SHOULD generate an Info-typed
metric named otel_scope_info for each Instrumentation Scope with non-empty
scope attributes.

In SDK Prometheus (pull) exporters, resource attributes SHOULD be converted to
a single target_info metric
if the resource is not empty;

@dashpole id like to work on this issue

Picking this up

It seems this change doesn't need to be done in this repo @dashpole

I believe we emit target_info even if there are no resource attributes: https://github.com/open-telemetry/opentelemetry-js/blob/f665499096189390e691cf1a772e677fa67812d7/experimental/packages/opentelemetry-exporter-prometheus/src/PrometheusSerializer.ts#L343-L350

I've updated the description to be more accurate, as otel_scope_info changes are not needed here.

I believe we emit target_info even if there are no resource attributes:

From the code below, the default resource is always used if no resource is specified (or an empty one is passed in) so we'd never have an empty resource. https://github.com/open-telemetry/opentelemetry-js/blob/f5ef8de1cc92ad22d7d95df6a5f585f9d64ddef1/packages/sdk-metrics/src/MeterProvider.ts#L47-L57
If we choose not to emit target_info when the default resource is used, it could break the existing API, and I cannot predict the extent of the impact.

Thanks for clarifying!


installion error

I am getting this error on make install
[+] Building 2.7s (8/8)
=> [rasa-actions internal] load build definition from Dockerfile          0.0s
=> => transferring dockerfile: 32B                                        0.0s
=> [rasa-actions internal] load .dockerignore                             0.0s
=> => transferring context: 34B                                           0.0s
=> [rasa-actions internal] load metadata for docker.io/khalosa/rasa-aarc  0.3s
=> [rasa-actions internal] load build context                             0.0s
=> => transferring context: 555B                                          0.0s
=> [rasa-actions 1/4] FROM docker.io/khalosa/rasa-aarch64:3.5.2@sha256:4  0.0s
=> CACHED [rasa-actions 2/4] COPY . /app                                  0.0s
=> CACHED [rasa-actions 3/4] WORKDIR /app                                 0.0s
=> ERROR [rasa-actions 4/4] RUN pip install python-dotenv rasa-sdk reque  0.4s
^Z

I have changed
sudo chmod +x app/rasa/wait-for-it.sh

FROM khalosa/rasa-aarch64:3.5.2 to FROM rasa/rasa:latest in app/rasa/actions/Dockerfile

rasa-core:
#image: khalosa/rasa-aarch64:3.5.2
image: rasa/rasa:latest
in docker-compose.yml

Even added user: 1000:1000 in docker-compose.yml as below

Rasa credentials helper service
rasa-credentials:
user: 1000:1000
and
Postgres database service
db:
user: 1000:1000
restarted the service but still getting the error as below in ubuntu machine

=> ERROR [rasa-actions 4/4] RUN pip install python-dotenv rasa-sdk requests

Same error! Any fix? @babasahebpinjar

No. I guess it works only on MACos.

i have same error, install in linux.
can resovle add root user .
modify app/rasa/actions/Dockerfile:
#FROM khalosa/rasa-aarch64:3.5.2
FROM rasa/rasa:latest
COPY . /app
WORKDIR /app
USER root
because current user is rasa
#RUN whoami
RUN pip3 install python-dotenv &&
pip3 install --no-cache-dir rasa-sdk requests -i https://pypi.douban.com/simple
USER rasa

Thanks fjcondy.
it is working only with
USER root

@babasahebpinjar, @fjcondy : Are you able to successfully install it?

Hey @nitishymtpl I was able to solve it with USER as root.

@babasahebpinjar : Oh, It works, thanks! that error got fixed.
But there seem issue with DB. Do we need to make changes?
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context
self.dialect.do_execute(
File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute
cursor.execute(statement, parameters)
psycopg2.errors.UndefinedFunction: operator does not exist: entity_status = integer
LINE 3: ...splay_name = 'project-pepetamine.md' AND document.status = 2
^
HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.

I got it up and did a POC which didnt move forward so I am not working on that anymore.
I didn't get this DB error back then.

oh, I see. It doesn't seems to work. Need to check it :).


ADD: ERS-HM

www.ers-hameln.de
https://www.ers-hameln.de/bildungsgaenge/index.htm

@36shpP Would you please:

Check if<EMAIL_ADDRESS>is a valid address in your school mail system (if yes, you may wish to tell this user to change their school inbox password asap, or at least ensure they did it recently)

Provide us with a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

You can provide us with any of the following:

A copy of instruction (a hard-copy or electronic one) given to you by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that students use this email domain
A reference to a recognized journal where an article was published by someone from the school, with explicit affiliation to the school, and e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be verified independently.

@36shpP You might miss my previous comment. Please react.

@36shpP I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


refactor garden-debian-sources-list script

What would you like to be added:
While integrating a new native Debian mirror support for Garden Linux, we encountered several things that should be adjusted within the garden-debian-sources-list script. However, we probably should completely refactor this one after #1426 got merged.
There shouldn't be any --gardenlinux-only param anymore since this is our default. Next, we probably can remove older references of squeeze etc. With #1426 the orchestrating scripts are already adjusted and the handling of a non existent --gardenlinux-only param integrated. Therefore, we only may call it with an additional --debian-mirror param which adds the native Debian repository.

#1426 is currently blocked by the broken Github tests. However, if #1426 is still not merged until the 1st of December, I may include a fix for this issue within #1426. If anyone else may start with this earlier - go ahead!

DEP task #1426 is fixed, now. In review by @Vincinator and ready for merge.

Quick update to this issue. We had a discussion with @gehoern about this and the following things should be kept in mind while refactoring this script:

This script shouldn't be part of the build pipeline anymore but rather be included in the artifact itself.

Keep in mind, that we will still need it for bootstrapping Garden Linux, but it should also be included in a running instead in order to modify sources.

It should be more intuitive, so that it's easy to modify the sources of the Garden Linux image during runtime.
Maybe, there is already such a script in Debian. If so, we should re-use it and adjust it for Garden Linux then. Needs to be verified.
It should be possible to add and define the following sources:

Only Garden Linux
Only Debian

Just Debian testing
Just Debian unstable

It should be possible to remove sources easily without modifying the APT sources by ourselves.
We may should keep the /etc/apt/source.list empty and just use the drop in directory /etc/apt/source.list.d

There could be files in the drop in directory like: gardenlinux.list, debian-testing.list, ...
Via a flag, one can also add source packages sources instead of just binary sources.

This tool should also consider priorities (take a look how it is already done in the current script).

It may be useful to define Garden Linux to priority 990+ to ensure hot fixes are applied no matter what the target version ist.
Take a look into here: https://linux.die.net/man/5/apt_preferences

We should check, if the script should use the Deb822-style format instead of the One-Line-Style Format for better machine-parsability.


[FRONTEND] Add error messages for arange

Fix issue https://github.com/openai/triton/issues/244
Check end is greater than start.
Check if the range can fit in int32.
Check the number of elements less than or equal to TRITON_MAX_TENSOR_NUMEL = 131072.

Please run autopep8 -a -r -i ./python


Cannot change the notification tone

It would be great to be able to change the notification tone for the app instead of using the default.

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

ID: 2033900c-d18a-cdd3-313c-7efed2ceb4ec
Version Independent ID: 87b1f4a4-abb8-f3f6-241e-ca8b9b3d5015
Content: Kaizala regional availability
Content Source: Office365-Kaizala/regional-availability.md
Service: kaizala
GitHub Login: @chuckedmonson
Microsoft Alias: chucked

@CarikeBL Thank you for this suggestion.
I know the product teams are always looking for user feedback and how to make software  better. They keep a close tab on the Kaizala app<EMAIL_ADDRESS>Thank you for your contribution to make the docs better! Much appreciated!


Doesn't work for snapped apps

The extension doesn't work with snapped apps. Does this extension uses the .desktop file names to map or something?

After a bit of research and finding this issue, which is also linked by this proposal that apparently you have found already, it seems that the mpris service that this extension uses, does somehow use the .desktop file names.

To be honest, I thought it doesn't work, because most my work revolved around firefox and firefox didn't work. But with some recent testings, I found that it just works! So, awesome! Thanks a lot! Keep up the good work.


telegram-desktop: 4.16.8 -> 5.0.0

Diff: https://github.com/telegramdesktop/tdesktop/compare/v4.16.8...v5.0.0
Changelog: https://github.com/telegramdesktop/tdesktop/releases/tag/v5.0.0
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

Telegram 5.0.0 works for me.
But it outputs a ton of logs, such as:

qt.svg: Error while inflating gzip file: SVG format check failed

Telegram 5.0.0 works for me. But it outputs a ton of logs, such as:

qt.svg: Error while inflating gzip file: SVG format check failed

This particular log has been around for long. Anything else?


Per-component borrow checking

Currently, runtime borrow checking is performed in order to allow the user to access two different components at the same time (which rust's static borrow checking would not allow), but disallow the same component from being incorrecttly borrowed multiple times.
The runtime state of a component's borrow is stored as an atomic integer along with each component's slice in each chunk. This is efficient and allows us to include borrow checking in release builds (although this is currently not the case) without significant performance penalty.
However, it is overly strict. It will not allow two components of the same type to be accessed at the same time when they each belong to different entities - even though this should be safe. This makes random component access very difficult in many situations.
We could relax these borrowing restrictions by tracking borrow state for every component, rather than each component slice. However, it is unlikely that this would provide acceptable performance, so we almost certainly would have to disable runtime borrow checking in release builds (perhaps with an opt-in).

However, it is unlikely that this would provide acceptable performance, so we almost certainly would have to disable runtime borrow checking in release builds (perhaps with an opt-in).

Would this not potentially cause undefined behavior in release mode, though? Even if users check that their borrows are correct in debug mode, untested edge cases could cause illegal borrow patterns, leading to UB in safe code. This might be tolerable, but there should definitely be a warning of such cases in the docs (and, technically, any component access functions should be marked unsafe, but that's not very ergonomic.)

Yes, that is expressly insta-UB. It sounds like this is in fact already a present problem:

This is efficient and allows us to include borrow checking in release builds (although this is currently not the case)

The implementation is therefore unsound, and the proposed change would further entrench that unsoundness.

I have created an issue for this: #21
I was undecided on an opt-out vs opt-in for release mode checks. I do not think an opt-out of these checks by itself is an issue. Such an opt-out serves much the same function of requiring the user to aknowledge their responsibility as the unsafe keyword does. However, these APIs do indeed need to be marked as unsafe regardless, and I do agree that the library should not allow the user to write code that breaks borrowing rules without the user's responsibilities being clearly communicated (ideally via unsafe, or very clear documentation if there is no single entrypoint responsible for the potential issue).
The safety checks proposed in this issue will require some way to disable them for performance reasons. Without that, either the borrow checking remains too loosely defined for these APIs to be truely functional, or the library as a while becomes too slow to be usable. If it is ever a decision between being able to solve a problem at the risk of the user being able to write code with certain classes of bugs, or not being able to solve the problem at all, I will choose the former. However, I cannot think of a situation where this cannot be clearly communicated; that is the purpose of unsafe and it is applicable here. The argument for ergonomics is much weaker with the introduction of systems (which ensure safety via the scheduler) and the query random access APIs proposed in #19 (which can perform cheap runtime checks).

I do not think an opt-out of these checks by itself is an issue.

I think this is sound so long as the opt-out is itself marked unsafe. Of course, care should be taken to ensure that most users do not need to write unsafe code to make effective use of the library, if at all possible.

If it is ever a decision between being able to solve a problem at the risk of the user being able to write code with certain classes of bugs, or not being able to solve the problem at all, I will choose the former.

To be clear, undefined behavior is not "certain classes of bugs," it's permission for the compiler and run-time environment to do literally anything, including revealing private data or remote code execution. We can't always wall it off completely

through the use of cfg-if and a private unsafe function that gets exposed as either a safe or unsafe public function, it's fairly easy to setup that release mode makes things become unsafe.
also please don't actually do any of this, it's a very bad look for the future core of Rust's only major game engine project to have even potential soundness issues.

A flag like that would either introduce compile errors that only exist in one build target (essentially forcing you to aknowledge the unsafe in both cases anyway), or it would cause people to disable runtime checks in debug builds (which I don't think is ever justified).
By marking these functions as unsafe in either case, there are no soundness issues beyond what you might find in any unsafe Rust code, and they are unsafe due to the nessesity of their nature. If anything, the fact that the library can perform runtime sanity checks for this unsafe code and provide stack traces pointing at the origin of the problem is a significant advantage over most unsafe code.

How about instead of changing the current implementation, allow the user to get a "ComponentStorage" wrapper that allows for borrowing the entire storage instead of a single component, and let that storage wrapper expose the decision of unsafety vs safe ref-counting per entity?


Trouble sending payment

recurring error message:
Error: Couldn't send user_command: (Transaction_pool.apply "Ledger was detatched") (in ["sendPayment"])

i was running the previous version!


Better grooming of created queryset content for search results is needed.

Right now, if you type "dkim" into the main page searchbox, you are redirected to a search result page that has this URL:
https://datatracker.ietf.org/doc/search?csrfmiddlewaretoken=<actual token elided>&name=dkim&sort=&rfcs=on&activedrafts=on&by=group&group=
This is silly. The issue is that the view is blindly copying things from the submitted form into the queryset.
It should, instead, only copy the things that make sense. The csrfmiddlewaretoken should never be copied. Any thing that would result in key= with no value should be elided.

The csrf_token tag should not be used in forms that don't use POST. (We can tell that this does GET because the form element has action="{% url 'ietf.doc.views_search.search' %}" and not method="post".) Apparently if you GET such a form, it adds a csrfmiddlewaretoken to the URL. Now we know.
Separately from that, the group parameter is empty because by is pre-selected as group, i.e. the radio button is pre-checked for "WG", but nothing is entered in the text field. If I remove the initial='group' argument from SearchForm.by, that empty field goes away (as well as by=group), but the user who wants to search by WG would first have to check the radio button, so that's a UI change.
The empty sort parameter is similar - we haven't chosen a sort (which we can only do from the search results page).
From what I've been able to find, a URL with empy parameters is pretty benign, and I haven't found a way to suppress it in the Form or Field classes. If there is a way, I'd love to be enlightened. @jennifer-richards
Separately from that as well, you say "The issue is that the view is blindly copying things from the submitted form into the queryset."  But that all happens after the generated URL is received. For purposes of filtering the search results in retrieve_search_results, it may be slightly more efficient to skip filtering on empty criteria, but not so as I'd notice.
So I think we're good with removing the csrf_token tag, and letting the other stuff slide.

Don't know offhand of a way to suppress it, but that doesn't mean there isn't one. Is there a reason not to change this to a POST?

It's just a search form, it's not changing anything on the server. So I don't see why it shouldn't be GET?

It should be GET in those terms, but since GET can't have a body it forces the unwieldy URL. I'm not terribly bothered by the bending of the convention. It does mean that the search URL cannot be shared which is a potentially useful feature.
After poking around a bit, your observation that this "happens after the generated URL is received" is the rub here. The only solutions I know of that leave a shareable, minimal URL are using javascript to disable the unneeded fields or to POST the search to an endpoint that redirects to a GET with the non-empty params.
I think using JS or living with the poor aesthetics are the better options.

The search form, in its current state, is used by many other pages essentially as an internal api (almost all pages that list documents use it). A shift to POST will cause quite a bit more change than one would expect. We should make that change anyhow, but I don't think this particular issue is the tipping point that pushes us into that investment.


Math: Find K Closest Points to Origin in Python

https://leetcode.com/problems/k-closest-points-to-origin/

i can do this


feature request: let lncli stop wait until there are no HTLCs pending

Background
Describe your issue here.
imagine i stoppen lnd with lncli stop but there was a pending HTLC in one of the channels, when the remote party wants to fulfill it, it cant so force closes the channel.
Your environment

version of lnd lnd version 0.14.2-beta commit=v0.14.2-beta
which operating system (uname -a on *Nix) Linux 5600g 5.17.2-arch3-1 #1 SMP PREEMPT Sun, 10 Apr 2022 11:18:32 +0000 x86_64 GNU/Linux
version of btcd, bitcoind, or other backend
any other relevant environment details

Steps to reproduce
Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.
not really a bug, but lncli stop when a channel has a pending HTLC the other can fulfill and it will force close to fulfill it on chain
Feature request:
an rpc and lncli argument to lncli stop to let it wait until all channels are 'clean'

you can use the HtlcInterceptor API to start refusing HTLCs before shutdown. Another mitigation here could be to increase your CLTV delta if you are simply restarting and don't have enough time to complete a restart. If you are bringing your node down for more extended periods of time, you can minimize HTLC attachment by making private channels. A normal lncli stop wouldn't result in force closed channels even with attached HTLCs, so long as you are able to restart within a reasonable amount of time.


PDF Rendering Issue in all versions after 2024.1.3 on Linux

PDF Rendering Issue in all versions 2024.1.10, 2024.2.0, and 2024.2.1 on Linux (some of the report content is not rendered)
To Reproduce
when I use version 2024.1.3 everything works fine but when I change to version 2024.1.10, 2024.2.0 or 2024.2.1 some parts of the reports disappear without any change in other code
Expected behavior
It is supposed to work properly on all versions.
Screenshots
with version 2024.1.3

with versions 2024.1.10, 2024.2.0 and 2024.2.1

Device (please complete the following information):

OS: Rocky Linux 9.4
Browser Chrome and Edge
Version; all

Hello!
Could you please send us your test report for testing and also the font used in your report, if you can also upgrade to the current version of FastReport and let us know the results
Also, to get a faster response you can create a ticket for our support department: https://www.fast-report.com/support.
Best regards,
Bogdan

Hi Bogdan
Oh! you remembered to reply now! It has been about 6 months since we
suffered from the problem and we waited with no response.
So, we did our own solution.
Anyway, thanks for the response.
Regards.
Assis. Prof. Dr. Mohamed A. Alrshah.IEEE Senior Member.Senior Lecturer at
the Department of Networks,Faculty of Computer Science and Information
Technology,
AL Asmarya Islamic University, Zliten, Libya
@.***<EMAIL_ADDRESS>@.**>
+218-91-320-6229
On Tue, Dec 17, 2024 at 12:21 PM Bogdan Stegachev @.***>
wrote:

Hello!
Could you please send us your test report for testing and also the font
used in your report, if you can also upgrade to the current version of
FastReport and let us know the results
Also, to get a faster response you can create a ticket for our support
department: https://www.fast-report.com/support.
Best regards,
Bogdan
—
Reply to this email directly, view it on GitHub
https://github.com/FastReports/FastReport/issues/703#issuecomment-2548067100,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF6XE4TGMOWFBC3AJJTE2Z32F73MLAVCNFSM6AAAAABJEISON6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBYGA3DOMJQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Repeat validation message not displaying

Question
Trying to validate repeating value in my app sample app. User can select a column and a new name in each repeat , but the  new name should not be duplicated in other repeat  fields. The validation is defined in the root field (repeat type) and it works as the form is set to invalid when validation fails, but the message is not displayed. What am I missing? How should I define the validation message so it'll display either under "new name" or for the repeat group. Thanks in advance.

To show the message error in repeat type, use formly-validation-message:
<div *ngIf="showError">
  <formly-validation-message [field]="field"></formly-validation-message>
</div>

Thanks, Where should this be added to? I don't find any documentation for this. added it to the repeate-section.types and still not working.

Inside repeate-section.types, I've checked the above provided stackblitz example and it seems working:

I made a little adjustment to the above solution see https://github.com/ngx-formly/ngx-formly/issues/3170#issuecomment-1029762431


Remove ellipsis from block hash logs

Description
As an operator, I want full block hashes so that I can grep for them in logs and display them in Splunk dashboards.
Steps to Reproduce (Bug)

Run a sync
Grep for FullImportBlockStep
See that log lines look like "Import reached block 3787200 (0xa147..ad3d), 29.996 Mg/s, Peers: 25"

Expected behavior:
Should see full block hash in parens
Actual behavior:
Only see the beginning and end of the hash, making it useless to match block hashes.
Versions (Add all that apply)

Software version: 20.10.1

Hi!
I've added a pull request, https://github.com/hyperledger/besu/pull/2105 .


build  update dependencies

Description
Update dependencies:

build(dependencies): 🧱 update crates
ci: 🐝 update pre-commit hooks

Type of change

[x] Dependency update

How Has This Been Tested?

[x] update dependencies

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 34.79%. Comparing base (257234f) to head (e22aa30).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #298   +/-   ##
=======================================
  Coverage   34.79%   34.79%
=======================================
  Files          13       13
  Lines        5858     5858
=======================================
  Hits         2038     2038
  Misses       3820     3820

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Intent as optional field in nlu.json

Hey guys,
I'm trying to create an nlu.json file without define the "intent" field, only entities.
The documentation https://rasa.com/docs/nlu/dataformat/ says that intent is an optional field:

The intent is the intent that should be associated with the text [optional]

so it should work - however , i've tried that in multiple ways (with empty field, none, null) but none of them work.
Any ideas how to solve that ?
Many thanks

Thanks for the question, our Github issue board is for bugs and feature requests only, though 😕
Please ask this question in the forum✨
If you were describing a bug, please create a report and fill out the template


Qbo fix

A couple fixes for QBO Diags:
-Add function to unify plevs.
-Inverse plev axes.
-Updates default cfg files.
-Bug fix
Example output:
Model vs obs:https://acme-viewer.llnl.gov/zhang40/qbo_diags_acme1/viewer/
Model vs model: https://acme-viewer.llnl.gov/zhang40/qbo_diags_acme1_m2m/viewer/

@forsyth2 This PR included the change in https://github.com/E3SM-Project/e3sm_diags/pull/309 Please let me know if you catch any problems. I will make a new release after merging this PR. Thank you.


Mac keeps going to sleep please help

I used to have homebridge running for 3 years just fine.
But 2 weeks ago, homebridge seems to sleep when idle. The devices goes "updating" until I wake up the mac.
So to troubleshoot this, I have a brand new homebridge installation, brand new home in Homekit, brand new config file. Brand new macOS. But the problem won't go away.
I already did sudo systemsetup -setcomputersleep Never
Doesn't help.
How to fix this?

It's not the mac per se thats sleeping.
If I use the 'home' app on macOS, it will wake homebridge
If I go to the computer and load a browser, it will wake homebridge
If I access the homebridge-config-ui-x webpage, it wakes homebridge
I don't understand whats going on

Could it be that the latest macOS version is now applying "App Nap" also to command line tools like nodejs? Have you updated macOS over these two weeks, maybe to the latest 10.14.6? Want to try to disable App Nap on your system to see if it solves the issue (search on google), and then maybe consider some way to disable app nap just for the nodejs command?

I've since (for testing) moved homebridge to linux in a vm inside the mac. Maybe the "app nap" is also napping the vm?

Why don’t you buy one cheap Raspberry pi

But I already run homebridge from linux, what would be the difference?

I've since (for testing) moved homebridge to linux in a vm inside the mac. Maybe the "app nap" is also napping the vm?

That would make sense. Lookup for the application that runs your VM, open the info of the app, and check the "Prevent App Nap". See e.g. https://www.lifewire.com/control-how-mac-applications-use-app-nap-2260788
Full mac Apps can be controlled one by one, with this on the GUI, or via command line.
What was confusing me was if macOS could also app nap terminal apps like nodejs… it's not unexpected, but as a beta tester, I can't confirm or deny if that will happen (translation: it's broken to the point that I'm pretty sure it won't happen, and it would make no sense to push that into a stable version of Mojave)

Have you tried with an app like: https://apps.apple.com/us/app/amphetamine/id937984704?mt=12
This will allow you to control if you don't want your mac to go to sleep. Or you allow the screen to go off, but the mac to keep running, etc.


Crud controller for custom pivot model

I'm using a custom intermediate table model for pivoting, as documented in https://laravel.com/docs/5.4/eloquent-relationships#many-to-many "Defining Custom Intermediate Table Models". So my model extends Illuminate\Database\Eloquent\Relations\Pivot class:
use Illuminate\Database\Eloquent\Relations\Pivot;
use Backpack\CRUD\CrudTrait;

class ClubSport extends Pivot
{
    use CrudTrait;
    protected $table = 'club_sport';
    ...

I want to make a CrudController for it, but I get this error:
ErrorException in Pivot.php line 47: Argument 1 passed to Illuminate\Database\Eloquent\Relations\Pivot::__construct() must be an instance of Illuminate\Database\Eloquent\Model, none given, called in C:\wamp\www\sportsconnect\vendor\backpack\crud\src\CrudPanel.php on line 90 and defined
If I make my Model extend Illuminate\Database\Eloquent\Model instead of Pivot, it works perfectly. Is it possible to make this work?

I'm not sure how you'd avoid the requirement from upstream Laravel to make the first argument to Pivot's constructor a Model:
https://laravel.com/api/5.4/Illuminate/Database/Eloquent/Relations/Pivot.html#method___construct
It looks like you're falling over here:
 77
 78     /**
 79      * This function binds the CRUD to its corresponding Model (which extends Eloquent).
 80      * All Create-Read-Update-Delete operations are done using that Eloquent Collection.
 81      *
 82      * @param [string] Full model namespace. Ex: App\Models\Article
 83      */
 84     public function setModel($model_namespace)
 85     {
 86         if (! class_exists($model_namespace)) {
 87             throw new \Exception('This model does not exist.', 404);
 88         }
 89
 90         $this->model = new $model_namespace();
 91         $this->query = $this->model->select('*');
 92     }

You could attempt to extend the CrudPanel itself and replace line 90 somehow when you see a Pivot relation but at the moment I'm not sure how else you might do that (although @tabacitu might know how as he's more familiar with this than me).

You could also use the model as a regular model, and have two belongsto relationships with both of the related models.
Dont know if the pivot model provides other  functionality that you mis out on by not extending from Pivot though.

@mariavilaro I'm having the same exact problem. If I use extend the Model class instead of the Pivot class, it works. However, the attach() and detach() functions don't work when trying to update the pivot table, because it's looking for the table with the tableA_tableB naming convention (even though the pivot table Model hast the $table property to a custom name).

Hmm... please check out https://github.com/Laravel-Backpack/CRUD/issues/393, might be a solution. A broken one (they say) but yeah :-)

#393 got fixed; closing this due to inactivity.


Dart: Skip final getCounters, postFinish to idle historicals.

In a Dart query, all Historicals are given worker IDs, but not all of them are going to actually be started or receive work orders.
Attempting to send a getCounters or postFinish command to a worker that never received a work order is not only wasteful, but it causes errors due to the workers not knowing about that query ID.

TY for having a look @LakshSingla


Cluster receiver crashes after helm update when file_storage extension is enabled

What happened?
Description
While working on these PRs #675 and #753 I discovered that when file_storage was enabled for the cluster receiver, then making any update in the values.yaml file under clusterReceiver section and running helm update caused crash of the cluster receiver pod. Using file_storage in agent works fine.
Steps to Reproduce

Set up cluster receiver config as described in the configuration and start the otel collector.
Make any change in the values.yaml under clusterReceiver section and run helm update.

Expected Result
Cluster Receiver pod working correctly.
Actual Result
Cluster Receiver pod crashes.
Chart version
0.71.0
Environment information
Environment
Chart configuration
Name:         sck-otel-splunk-otel-collector-otel-k8s-cluster-receiver
Namespace:    default
Labels:       app=splunk-otel-collector
              app.kubernetes.io/instance=sck-otel
              app.kubernetes.io/managed-by=Helm
              app.kubernetes.io/name=splunk-otel-collector
              app.kubernetes.io/version=0.71.0
              chart=splunk-otel-collector-0.71.0
              helm.sh/chart=splunk-otel-collector-0.71.0
              heritage=Helm
              release=sck-otel
Annotations:  meta.helm.sh/release-name: sck-otel
              meta.helm.sh/release-namespace: default

Data
====
relay:
----
exporters:
  splunk_hec/platform_metrics:
    disable_compression: true
    endpoint: <MY_ENDPOINT>
    index: metric
    max_connections: 200
    retry_on_failure:
      enabled: true
      initial_interval: 5s
      max_elapsed_time: 300s
      max_interval: 30s
    sending_queue:
      enabled: true
      num_consumers: 10
      queue_size: 5000
      storage: file_storage/persistent_queue
    source: kubernetes
    splunk_app_name: splunk-otel-collector
    splunk_app_version: 0.71.0
    timeout: 10s
    tls:
      insecure_skip_verify: true
    token: ${SPLUNK_PLATFORM_HEC_TOKEN}
extensions:
  file_storage/persistent_queue:
    directory: /var/addon/splunk/persist/clusterReceiver
  health_check: null
  memory_ballast:
    size_mib: ${SPLUNK_BALLAST_SIZE_MIB}
processors:
  batch: null
  memory_limiter:
    check_interval: 2s
    limit_mib: ${SPLUNK_MEMORY_LIMIT_MIB}
  resource:
    attributes:
    - action: insert
      key: metric_source
      value: kubernetes
    - action: upsert
      key: k8s.cluster.name
      value: sck-otel
  resource/add_collector_k8s:
    attributes:
    - action: insert
      key: k8s.node.name
      value: ${K8S_NODE_NAME}
    - action: insert
      key: k8s.pod.name
      value: ${K8S_POD_NAME}
    - action: insert
      key: k8s.pod.uid
      value: ${K8S_POD_UID}
    - action: insert
      key: k8s.namespace.name
      value: ${K8S_NAMESPACE}
  resource/k8s_cluster:
    attributes:
    - action: insert
      key: receiver
      value: k8scluster
  resourcedetection:
    detectors:
    - env
    - system
    override: true
    timeout: 10s
receivers:
  k8s_cluster:
    auth_type: serviceAccount
  prometheus/k8s_cluster_receiver:
    config:
      scrape_configs:
      - job_name: otel-k8s-cluster-receiver
        scrape_interval: 10s
        static_configs:
        - targets:
          - ${K8S_POD_IP}:8889
service:
  extensions:
  - health_check
  - memory_ballast
  - file_storage/persistent_queue
  pipelines:
    metrics:
      exporters:
      - splunk_hec/platform_metrics
      processors:
      - memory_limiter
      - batch
      - resource
      - resource/k8s_cluster
      receivers:
      - k8s_cluster
    metrics/collector:
      exporters:
      - splunk_hec/platform_metrics
      processors:
      - memory_limiter
      - batch
      - resource/add_collector_k8s
      - resourcedetection
      - resource
      receivers:
      - prometheus/k8s_cluster_receiver
  telemetry:
    logs:
      level: "debug"
    metrics:
      address: <IP_ADDRESS>:8889

Events:  <none>

Log output
2023/04/07 15:44:07 settings.go:331: Set config to [/conf/relay.yaml]
2023/04/07 15:44:07 settings.go:384: Set ballast to 297 MiB
2023/04/07 15:44:07 settings.go:400: Set memory limit to 810 MiB
2023-04-07T15:44:07.429Z	info	service/telemetry.go:90	Setting up own telemetry...
2023-04-07T15:44:07.429Z	info	service/telemetry.go:116	Serving Prometheus metrics	{"address": "<IP_ADDRESS>:8889", "level": "Basic"}
2023-04-07T15:44:07.429Z	debug	extension/extension.go:146	Beta component. May change in the future.	{"kind": "extension", "name": "health_check"}
2023-04-07T15:44:07.429Z	debug	extension/extension.go:146	Beta component. May change in the future.	{"kind": "extension", "name": "memory_ballast"}
2023-04-07T15:44:07.429Z	debug	extension/extension.go:146	Beta component. May change in the future.	{"kind": "extension", "name": "file_storage/persistent_queue"}
2023-04-07T15:44:07.429Z	debug	exporter/exporter.go:284	Beta component. May change in the future.	{"kind": "exporter", "data_type": "metrics", "name": "splunk_hec/platform_metrics"}
2023-04-07T15:44:07.429Z	debug	processor/processor.go:298	Beta component. May change in the future.	{"kind": "processor", "name": "resource/k8s_cluster", "pipeline": "metrics"}
2023-04-07T15:44:07.429Z	debug	processor/processor.go:298	Beta component. May change in the future.	{"kind": "processor", "name": "resource", "pipeline": "metrics"}
2023-04-07T15:44:07.429Z	debug	processor/processor.go:298	Beta component. May change in the future.	{"kind": "processor", "name": "resource", "pipeline": "metrics/collector"}
2023-04-07T15:44:07.429Z	debug	processor/processor.go:298	Beta component. May change in the future.	{"kind": "processor", "name": "resourcedetection", "pipeline": "metrics/collector"}
2023-04-07T15:44:07.429Z	debug	processor/processor.go:298	Beta component. May change in the future.	{"kind": "processor", "name": "resource/add_collector_k8s", "pipeline": "metrics/collector"}
2023-04-07T15:44:07.430Z	debug	processor/processor.go:298	Stable component.	{"kind": "processor", "name": "batch", "pipeline": "metrics"}
2023-04-07T15:44:07.430Z	debug	processor/processor.go:298	Stable component.	{"kind": "processor", "name": "batch", "pipeline": "metrics/collector"}
2023-04-07T15:44:07.430Z	debug	processor/processor.go:298	Beta component. May change in the future.	{"kind": "processor", "name": "memory_limiter", "pipeline": "metrics"}
2023-04-07T15:44:07.430Z	info	memorylimiterprocessor@v0.71.0/memorylimiter.go:113	Memory limiter configured	{"kind": "processor", "name": "memory_limiter", "pipeline": "metrics", "limit_mib": 810, "spike_limit_mib": 162, "check_interval": 2}
2023-04-07T15:44:07.430Z	debug	receiver/receiver.go:305	Beta component. May change in the future.	{"kind": "receiver", "name": "k8s_cluster", "data_type": "metrics"}
2023-04-07T15:44:07.430Z	debug	processor/processor.go:298	Beta component. May change in the future.	{"kind": "processor", "name": "memory_limiter", "pipeline": "metrics/collector"}
2023-04-07T15:44:07.430Z	debug	receiver/receiver.go:305	Beta component. May change in the future.	{"kind": "receiver", "name": "prometheus/k8s_cluster_receiver", "data_type": "metrics"}
2023-04-07T15:44:07.449Z	info	service/service.go:140	Starting otelcol...	{"Version": "v0.71.0", "NumCPU": 4}
2023-04-07T15:44:07.449Z	info	extensions/extensions.go:41	Starting extensions...
2023-04-07T15:44:07.449Z	info	extensions/extensions.go:44	Extension is starting...	{"kind": "extension", "name": "health_check"}
2023-04-07T15:44:07.449Z	info	healthcheckextension@v0.71.0/healthcheckextension.go:45	Starting health_check extension	{"kind": "extension", "name": "health_check", "config": {"Endpoint":"<IP_ADDRESS>:13133","TLSSetting":null,"CORS":null,"Auth":null,"MaxRequestBodySize":0,"IncludeMetadata":false,"Path":"/","CheckCollectorPipeline":{"Enabled":false,"Interval":"5m","ExporterFailureThreshold":5}}}
2023-04-07T15:44:07.449Z	warn	internal/warning.go:51	Using the <IP_ADDRESS> address exposes this server to every network interface, which may facilitate Denial of Service attacks	{"kind": "extension", "name": "health_check", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2023-04-07T15:44:07.449Z	info	extensions/extensions.go:48	Extension started.	{"kind": "extension", "name": "health_check"}
2023-04-07T15:44:07.449Z	info	extensions/extensions.go:44	Extension is starting...	{"kind": "extension", "name": "memory_ballast"}
2023-04-07T15:44:07.520Z	info	ballastextension@v0.71.0/memory_ballast.go:52	Setting memory ballast	{"kind": "extension", "name": "memory_ballast", "MiBs": 297}
2023-04-07T15:44:07.520Z	info	extensions/extensions.go:48	Extension started.	{"kind": "extension", "name": "memory_ballast"}
2023-04-07T15:44:07.520Z	info	extensions/extensions.go:44	Extension is starting...	{"kind": "extension", "name": "file_storage/persistent_queue"}
2023-04-07T15:44:07.520Z	info	extensions/extensions.go:48	Extension started.	{"kind": "extension", "name": "file_storage/persistent_queue"}
2023-04-07T15:44:08.473Z	info	service/service.go:166	Starting shutdown...
2023-04-07T15:44:08.474Z	info	healthcheck/handler.go:129	Health Check state change	{"kind": "extension", "name": "health_check", "status": "unavailable"}
2023-04-07T15:44:08.474Z	info	extensions/extensions.go:55	Stopping extensions...
2023-04-07T15:44:08.474Z	info	service/service.go:180	Shutdown complete.
Error: cannot start pipelines: timeout; failed to shutdown pipelines: no existing monitoring routine is running; no existing monitoring routine is running
2023/04/07 15:44:08 main.go:115: application run finished with error: cannot start pipelines: timeout; failed to shutdown pipelines: no existing monitoring routine is running; no existing monitoring routine is running

Additional context
No response

@wojtekzyla did you try adding a new volume and volume mount to the deployment-cluster-receiver.yaml for where the persistent queue data would be stored?

so, what happens when we update the cluster receiver deployment:
1). The old pod is running and has acquired the lock for the file-storage path for persistent queue.
2). New pod is created and it tries to acquire the lock, but gives up after 1s (default timeout value) as the old one is still up, because of the default strategy setting in deployment.
To solve this issue we need to:
1). Update the deployment pod replacement strategy and set .spec.strategy.rollingUpdate.maxUnavailable to 1, so we can terminate the old pod and create a new pod simultaneously. This would work the same way as the agent pods.
2). Set timeout to 0 i.e. wait indefinitely to acquire the lock. It would succeed once the previous pod is terminated successfully.

The old pod isn't terminating because we haven't yet successfully started the new pod. The new pod is trying to acquire a lock that can only be released when we terminate the old pod.
A deadlock ;(
and that's why we need to pod replacement strategy for the deployment to fix this issue

I think we can close this one as the behavior is as designed


Ammo.js Dependency

Should Ammo.js be considered a dependency in the package.json?
"dependencies": {
    "ammo.js": "https://github.com/kripken/ammo.js"
  }

No, I don't feel like it's a hard dependency really. From the looks of things, the ammo.js node package is no longer updated:
https://www.npmjs.com/package/ammo.js
And the package.json is not regularly updated with a meaningful version.
The only dependency on ammo is the link to the version of the library that we recommend. For example:
https://github.com/playcanvas/engine/blob/master/examples/physics/falling_shapes/index.html#L5
I don't think the library is required anywhere else in the codebase. Now, as an end user, sure, you're likely to want to use ammo.js, and if so, either grab the latest build from kripken's repo, or use the latest on https://code.playcanvas.com
I think I'll add a comment in the engine's top-level readme to explain all this.


Bug in ./example/

In /example/ssd/evaluate_net.py, Line84 DetRecordIter using the default RGB means, not the params set in /example/ssd/evaluate.py.
In /example/rcnn/rcnn/symbol/symbol_vgg.py and symbol_resnet.py, all mx.symbol.contrib.Proposal need to update to mx.contrib.symbol.Proposal.

Thanks for reporting.

see fix #8352
mx.symbol.contrib == mx.contrib.symbol so it's not a problem now.


⚡Cool App deserves a cool icon

Describe the feature
@thewh1teagle Hi!
Let's keep it simple, Vibe helped me a lot to learn more in what I'm doing.
So, here's an all-NEW cool app icon from myside.
Of Course, It's up-to you, to accept it as the default app icon, though I kept the app theming in mind while designing it, the icon clearly reflects the aura of Vibe.
An overview of the first phase of design

I've made some variations also, let me know which one feels right, and if you need any changes in design or color, just mention me in this thread.
More Variants

The app is for sure very good on the inside, so why not let that be shown on the outside.
Below is Scale: 100% view of 96 by 96 px icons.

These fluent design-based icons look kind of good to me.
My taskbar will be waiting for this icon update ;)

I'm quite opinionated when it comes to design! :)
I appreciate fluent design and agree that the logo could use some improvement. However, I’d like to emphasize the importance of preserving the overall shape of the main concept (the microphone). The document element in the new logo feels overly dominant compared to the core concept.

Yes, I appreciate your points, I'm using Figma.
The icons are 96px by 96 px in size though.

I felt putting a document appearance could emphasize the type of output i.e. the transcript that the app generates.

So, can you please list out the changes needed as in points?
Like this,

1
2 ...

Since, you haven't replied, I suppose, I should at least just drop here what's looking good on mine.

(Vibe is right next to GitHub Desktop App in the screenshot)
Here's the asset archive which contains ...

4 SVGs for sizes 16x16, 32x32, 64x64, 128x128 (px).
Windows Ico file exported using GIMP.
GIMP Workspace (.xcf)

At last, that's how what vibe appears on my windows system.


Strong button affordance, or add a cursor pointer

This is a minor issue, but the Next/Previous track buttons should either be more clearly buttons, or the cursor should change into a pointer when hovering over them.
See: https://medium.com/simple-human/buttons-shouldnt-have-a-hand-cursor-b11e99ca374b#.s47d20e3t

That's been bothering me as well, just haven't had the time to fix it. I'll get into it later.

@kmikiy Thanks! I can take a crack at it after work today -- which option are you leaning towards (better affordance vs cursor pointer)?

With the latest version of SpotMenu (1.3) almost the whole surface is clickable, so just simply using a cursor pointer might not help that much. Better affordance might be a better option, although I don't have any ideas on how to make the buttons look more like buttons and keep a minimal design at the same time.

I disagree re: not using a cursor pointer, I think that adding one and maybe changing the arrow to a light grey on hover would help significantly.
I completely agree re: better affordance, though. That's a tough problem, especially if you're trying to be consistent with macOS styling. Which is why I think that the cursor pointer is better than nothing. :)

@camdenb I'm confused, the article you linked strongly disagrees with using cursor: pointer over buttons like the prev/next affordances in the menulet. And yet you seem to be advocating for their use. I think a hover state for the affordances would be sufficient.

@trevorsayre Yeah, a hover state or better button affordance would be ideal, but as a bare minimum a pointer is better than nothing.

👋 Hey, thanks for the project @kmikiy!
I was playing with this today and wanted to suggest a few small changes that might help here. Let me know if you agree, and I'll PR it!

button alpha change on hover state
more recognisable next/previous icons (hopefully without spoiling the clean/minimal look)
smaller target areas to make it harder to hit the wrong button

e.g.

@jacobpgn nice, looks great🙌🏻 it would be awesome if you made a PR!

Yeah, looks amazing!! Maybe the next/previous buttons could have some extra clickable space around them to make them a little easier to click?


$ wrangler dev --env local randomly returns 502 Bad Gateway

Hi, the title pretty much says it all.
I'm trying to build a worker but whenever I try to start it locally with $ wrangler dev --env local a 502 is randomly returned.
Not every time, not never.
Just randomly.
Frustrating.
I'm passing  the --env option in order to bind a KV namespace I've set in the wrangler.toml file.
I'm also using the itty-router package to handle incoming requests.
When the 502 doesn't happen, everything works just fine.
Node version: 16.13.2
Wrangler version: 1.19.7
I've tried with wrangler@beta, too.
Same issue.
Any help anyone?
Thanks!

I have the same problem, maybe it is the cloudflare tunnel's problem

I am having the same issue

This sounds frustrating, sorry about that. Could you share a some more details? I'd like to see what the logs say when this is happening. If you can make a sample project that reproduces that issues that would be extremely helpful.

I have the same problem too. I'm using router starter project. Just changed a little bit.
After getting 502, I changed my internet connection to another network, and it worked just fine.

Hey all, sorry about the issues! We've identified the issue and are rolling out a fix. Let us know if you continue to have any issues!


Why 2.0?

What change to xhr caused the major version bump?

Two main things:

xhr was supposed to be a replacement for request and 1.x would return HTTP responses of 400+ as errors, while request did not. We changed that and now the callback is only called with first argument not null when there is an error making the request
xhr used to extend the XMLHttpRequest object and return it as a second argument, but for old IEs it couldn't be done, so turning on IE support changed the response format, which was hard to maintain for developers using it. We changed the format of the response object to be much simpler and IE compatible.

As a result it's not going to 'just work' if you replace xhr 1.x with 2.0 in your dependencies.

:+1: Changelog please! :)

Yeah a changelog would be nice.
xhr@2 landed in nets@3: https://www.npmjs.com/package/nets


top_p

why doesn't generation use top_p?

why doesn't generation use top_p?

no particular reason, we just haven't implemented it yet. We'd be happy to get a PR, or otherwise might add it eventually.


Missing feature - handling XML processing instructions

Hi
I wonder if there's a possibility to add this little feature available in xmlbuilder - https://github.com/oozcitak/xmlbuilder-js/wiki#processing-instructions? Currently I need to do rather hacky-way, by string comparision and then insert/replace.

+1

If we just wanted to support collecting processing instructions we could allow the calling code to do this pretty easily - something like this:
diff --git a/src/parser.coffee b/src/parser.coffee
index eb19c5b..03d8f47 100644
--- a/src/parser.coffee
+++ b/src/parser.coffee
@@ -87,6 +87,9 @@ class exports.Parser extends events
         @saxParser.ended = true
         @emit "end", @resultObject

+    @saxParser.onprocessinginstruction = (instruction) =>
+      @emit "processinginstruction", instruction
+
     # another hack to avoid throwing exceptions when the parsing has ended
     # but the user-supplied callback throws an error
     @saxParser.ended = false

i.e. just add a callback to the underlying sax parser for onprocessinginstruction and just emit the event verbatim.
and then in the calling code
const parser = new xmljs.Parser();
parser.addListener('processinginstruction', (instr) => {
  // do something with instr
});
await parser.parseStringPromise(xml);


[Bug]: Reporting broken

What happened?
Reporting is broken
Unable to send report
Invalid `prisma.commentReport.create()` invocation: An operation failed because it depends on one or more records that were required but not found. No 'Comment' record(s) (needed to inline the relation on 'CommentReport' record(s)) was found for a nested connect on one-to-many relation 'CommentToCommentReport'.

Steps to reproduce the problem

Go to comment/model/etc (specifically image comment)
Report it

What should have happened?
Report content
What platforms do you use to access the site?
Windows
What browsers do you use to access the site?
Mozilla Firefox
Additional information, context and logs
No response

I'm having trouble reproducing this.
I was able to successfully report the following:

Model
Image
Comment on Model
Comment on Image.

Do you have a specific comment I should try to report?

Ok, we found this issue and fixed this.
Thanks for the bug report @WASasquatch!


When I press the import button I get an error

I  was trying to add a movement to a character but when importing I got an error saying non-negative number required

Sorry for the trouble i already resolved the issue


Question: What kind of HTTPS ceritificate do I need to apply as my BOT is on AWS?

HI,
I want to host my bot on AWS.
I tried third-party HTTPS certs from StartSSL.com & LetsEncrypt.com
But on 'Test connection to bot' they give an error.
Sometimes it's 'Trust cannot be established' and on other occasions it's 'Error in BotControllerManager.cs'
Please help as its urgent for me to fix soon as my bot is to launch this week.
My questions:

What kind of HTTPS ceritificate do I need to apply as my BOT is on AWS and not on Azure?
Do I need to configure anything else as well besides the HTTPS certificate apply on my endpoint??

Hi @afficionaddo, the Error in BotControllerManager will be fixed in our next deployment.
The Bot Framework requires that the x.509v3 certificate exposed by your endpoint be current and valid. Most of the checks for "current and valid" are standard checks for server certs: the CN must match the hostname, it must not be expired, it must not be listed in a CRL, it must have the correct set of EKUs, etc.
Most importantly, your cert must chain to a root certificate authority trusted by Microsoft. The latest list of these CAs is available here: http://social.technet.microsoft.com/wiki/contents/articles/31634.microsoft-trusted-root-certificate-program-participants-v-2016-april.aspx


Updated ReadMe

I just changed some stuff for you in the ReadMe to help make things a little more clear.

This repo is now diseased, in favor of esp8266ws2812i2s.


⚠ Bofrost.lu has degraded performance

In 0038aad, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1757 ms

Resolved: Bofrost.lu performance has improved in daa68ef after 10 minutes.


Fix UUID regexp again?!

I have no idea why my UUID regexp fix got reverted...
I've also added myself to the list of contributors. Thanks for pulling :)

I've specified the commit-range in #15 so i can continue to push to my master...


⚠ TADA Wallet Web has degraded performance

In 7a85265, TADA Wallet Web ($WALLET_WEB_URL) experienced degraded performance:

HTTP code: 200
Response time: 7163 ms

Resolved: TADA Wallet Web performance has improved in 5dcb608.


FEATURE REQUEST: Local LLM endpoint integration (like Ollama and OpenAI API compatible) and Docker Container

This project seems awesome. Thanks for building this.
Would it be possible to:

Expose a variable for the LLM Endpoint address so systems like Ollama could be used as OpenAI API compatible endpoints?
Would you be able to offer the tool / UI as a Docker container or Docker Compose stack?

Thanks!

For 1, you can change the LLM configuration according to https://github.com/stanford-oval/storm?tab=readme-ov-file#customize-the-storm-configurations.
For 2, having a Docker release sounds like a good idea. We will consider this.

Hi @shuther , thanks for the info! Are you willing to help with ollama integration to see whether it's feasible? We develop STORM using dspy and I just found they support ollama in their codebase. New LM integration can be added in src/lm.py.

Hi @shuther , thank you so much!
I feel we can leverage the effort in https://github.com/stanfordnlp/dspy/blob/main/dsp/modules/ollama.py, though some testing is needed and we may need to create a wrapper instead of directly using it (you can check out examples in src/lm.py).
When testing Mistral 7B, I found although it's worth than GPT (which is as expected), it can do a pretty good job in the knowledge curation part (i.e., finding and organizing information). That's why I think ollama integration is interesting.

It could make sense to focus on this one or you have a concern?

No concern, this is good. I think https://github.com/stanfordnlp/dspy/blob/main/dsp/modules/ollama.py is also implemented based on it. You may check whether their implementation can directly work or not. If not, we also hope to inherit dspy.LM. In this way, we can pass the model object into STORMWikiLMConfigs without changing anything else. For example, people may use Ollama to run STORM in this way:
lm_configs = STORMWikiLMConfigs()

conv_simulator_lm = OllamaModel(...)
question_asker_lm = OllamaModel(...)
outline_gen_lm = OllamaModel(...)
article_gen_lm = OllamaModel(...)
article_polish_lm = OllamaModel(...)

# LM setup.
lm_configs.set_conv_simulator_lm(conv_simulator_lm)
lm_configs.set_question_asker_lm(question_asker_lm)
lm_configs.set_outline_gen_lm(outline_gen_lm)
lm_configs.set_article_gen_lm(article_gen_lm)
lm_configs.set_article_polish_lm(article_polish_lm)

# STORM pipeline setup (independent with LM setup).
engine_args = STORMWikiRunnerArguments(...)

# User / Other functions only need to call runner, and do not need to think about Ollama after they are set up.
runner = STORMWikiRunner(engine_args, lm_configs)

llama3 may worth a try.

Totally. I only provide an example with Mistral because I haven't got time to configure llama3 yet - but it's really worth a try.

@shuther  The error root : ERROR    : Error occurs when searching query : 'hits' you see is most likely due to rate limit exceeds from You.com search engine API. (check if you have some error log looks like this #28)

@shuther Also, note that the argument --remove-duplicate should go with --do-polish-article as the argument controls over whether remove duplicate content after final article generation. It does nothing when you don't specify --do-polish-article.

@shuther Would you mind provide full log of running the command? Also please confirm that you are on the head of main branch.

seems like storm/./src/lm.py, line 191, should be self.history.append(json_serializable_history) instead of (RateLimitError,),. Could you confirm you are at head of main branch?

is it possible to change the model from paraphrase-MiniLM-L6-v2 to ollama/all-minilm (using openai/litellm compatible endpoint)

This is possible, though you need to check its performance. This model is used to retrieve collected information to write each section. Here is an example for how to use ollama/all-minilm

Create OllamaStormInformationTable inheriting StormInformationTable but using ollama for retrieving information from the information table.

import numpy as np
import ollama  # Assume ollama is already installed on the PC and you have already run `ollama pull all-minilm`

class OllamaStormInformationTable(InformationTable):
    """Manage StormInformation with ollama embedding model."""

    def prepare_table_for_retrieval(self):
        self.encoder = SentenceTransformer('paraphrase-MiniLM-L6-v2')
        self.collected_urls = []
        self.collected_snippets = []
        for url, information in self.url_to_info.items():
            for snippet in information.snippets:
                self.collected_urls.append(url)
                self.collected_snippets.append(snippet)
                # This part is new.
                self.encoded_snippets.append(ollama.embeddings(model='all-minilm', prompt=snippet)['embeddings'])
        self.encoded_snippets = np.array(self.encoded_snippets)

    def retrieve_information(self, queries: Union[List[str], str], search_top_k) -> List[StormInformation]:
        selected_urls = []
        selected_snippets = []
        if type(queries) is str:
            queries = [queries]
        for query in queries:
            # This line is new.
            encoded_query = np.array(ollama.embeddings(model='all-minilm', prompt=query)['embeddings'])
            sim = cosine_similarity([encoded_query], self.encoded_snippets)[0]
            sorted_indices = np.argsort(sim)
            for i in sorted_indices[-search_top_k:][::-1]:
                selected_urls.append(self.collected_urls[i])
                selected_snippets.append(self.collected_snippets[i])

        url_to_snippets = {}
        for url, snippet in zip(selected_urls, selected_snippets):
            if url not in url_to_snippets:
                url_to_snippets[url] = set()
            url_to_snippets[url].add(snippet)

        selected_url_to_info = {}
        for url in url_to_snippets:
            selected_url_to_info[url] = copy.deepcopy(self.url_to_info[url])
            selected_url_to_info[url].snippets = list(url_to_snippets[url])

        return list(selected_url_to_info.values())

Customize STORMWikiRunner to use OllamaStormInformationTable.

class MySTORMWikiRunner(STORMWikiRunner):

    """Customize STORMWikiRunner to use OllamaStormInformationTable."""
    def run(self,
        topic: str,
        ground_truth_url: str = '',
        do_research: bool = True,
        do_generate_outline: bool = True,
        do_generate_article: bool = True,
        do_polish_article: bool = True,
        remove_duplicate: bool = False,
        callback_handler: BaseCallbackHandler = BaseCallbackHandler()):
    self.topic = topic
    self.article_dir_name = topic.replace(' ', '_').replace('/', '_')
    self.article_output_dir = os.path.join(self.args.output_dir, self.article_dir_name)
    os.makedirs(self.article_output_dir, exist_ok=True)

    # research module
    information_table: OllamaStormInformationTable = None  # StormInformationTable -> OllamaStormInformationTable
    if do_research:
        information_table = self.run_knowledge_curation_module(ground_truth_url=ground_truth_url,
                                                               callback_handler=callback_handler)
    else:
        information_table = OllamaStormInformationTable.from_conversation_log_file(
            os.path.join(self.article_output_dir, 'conversation_log.json'))  # StormInformationTable -> OllamaStormInformationTable

    # outline generation module
    outline: StormArticle = None
    if do_generate_outline:
        outline = self.run_outline_generation_module(information_table=information_table,
                                                     callback_handler=callback_handler)
    else:
        outline = StormArticle.from_outline_file(topic=topic, file_path=os.path.join(self.article_output_dir,
                                                                                'storm_gen_outline.txt'))

    # article generation module
    draft_article: StormArticle = None
    if do_generate_article:
        draft_article = self.run_article_generation_module(outline=outline,
                                                           information_table=information_table,
                                                           callback_handler=callback_handler)

    # article polishing module
    if do_polish_article:
        polished_article = self.run_article_polishing_module(draft_article=draft_article,
                                                             remove_duplicate=remove_duplicate)

If you want to use https://docs.litellm.ai/docs/providers/ollama instead of https://github.com/ollama/ollama-python, you just need to change the ollama.embeddings(...) to corresponding call to litellm API.

root : ERROR    : Error occurs when searching query : 'hits'
root : ERROR    : Error occurs when searching query : 'hits'
root : ERROR    : Error occurs when searching query : 'hits'
interface : INFO     : run_knowledge_curation_module executed in 1.4256 seconds
interface : INFO     : run_outline_generation_module executed in 3.9669 seconds

Based on the log, it seems like the do_research part is not correctly executed, i.e., no information is collected. Could you check whether YouRM is working? It may be exceeding the search API limit, so no information is returned when calling the retriever. To check this, you can do the following
from rm import YouRM

you_rm = YouRM(ydc_api_key="you_com_api_key")
output = you_rm(query_or_queries="Differences between capitalism and liberalism", exclude_urls=[])
print(output)

Ollama is supported now by #81. For other bug report, please open a new issue with bug report template.

Fantastic work! Thanks @Yucheng-Jiang


refactor nimbleMCMC to pull out model creation

This will refactoring be helpful for future nimbleHMC function.

@paciorek Here is one example of the mcem testing failure (which is the first commit in this PR):
https://github.com/nimble-dev/nimble/runs/6576403030?check_suite_focus=true
I just merged the "patch" (PR #1224 ) into this PR, so testing should pass on this PR now.


Enhance expo template with expo router, expo auth session and eslint

This provides an enhanced out-of-the-box experience when running the template.
I also added the default scripts to run a local FHIR Server.
Enhance #146

@nickvallee I built on your previous PR to add a bit more to the experience, as I believe people implementing an expo app will need to have solutions for routing and authentication.


Use typing_extensions.Self

Roadmap
Taken from the output of grep -lE "(self|cls): " -d recurse gd | uniq | sort.

Merging that in. Not gonna squash right now. Reverting is always an option if something. Please review this PR anyway.


Troubleshooting / FAQ

We have a FAQ/SETUP docs here on github, but we want to:

Expand the troubleshooting portions ... especially around deployment as thats where we see a lot of stumbling atm
Make sure wherever the deployment/troubleshooting docs live its in a place people can find and use

(going to start listing questions we've seen more than once here so we remember what to add to these docs)
We've fielded a few questions for PullPolicy settings for custom manifests. Lets ID the symptoms for when this is set wrong (e.g. when you have old features bcz the new default is Always when you're trying to use newly compiled versions so you should set it to IfNotPresent)

We get questions about timeout errors during cluster deployment such as
pachd starting up before rethinkdb is ready. Would be good to document that
this is normal.
Same for fuse throwing benign errors
On Fri, Jul 1, 2016 at 12:16 PM, Sean Jezewski<EMAIL_ADDRESS>wrote:

(going to start listing questions we've seen more than once here so we
remember what to add to these docs)
We've fielded a few questions for PullPolicy settings for custom
manifests. Lets ID the symptoms for when this is set wrong (e.g. when you
have old features bcz the new default is Always when you're trying to use
newly compiled versions so you should set it to IfNotPresent)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pachyderm/pachyderm/issues/543#issuecomment-230027167,
or mute the thread
https://github.com/notifications/unsubscribe/ABtjwHjMSj_drg9gPl_i7vKuR6nBulp1ks5qRWeTgaJpZM4I25Y-
.

The fixes from the error-cleanup branch silence the fuse errors, so we don't have to document that one anymore ;-)


Gulp pack should not run on dataplane packages

The gulp-pack step in the management plane pipelines were running on data plane packages too, aometimes causing our PRs to fail. So we want to update the gulp-packstep to not include the data plane packages - they should run only on management plane packages

@KarishmaGhiya Is this PR still applicable? Can you add more details in the PR description?

@KarishmaGhiya  I think you might forget to change https://github.com/Azure/azure-sdk-for-js/blob/master/package.json#L31 here. such as add a "prebuild": "your data-plane list generation script". In this way,  when you run npm build it will automatically run prebuild first.

@KarishmaGhiya I think you might forget to change https://github.com/Azure/azure-sdk-for-js/blob/master/package.json#L31 here. such as add a "prebuild": "your data-plane list generation script". In this way, when you run npm build it will automatically run prebuild first.

That sounds good! Thanks!!

@qiaozha There are 2 places where I added the step back in the yaml files, since we don't run build before the gulp pack step in the ci yaml file and before the npm run build step in the pr yaml file. Can you check these?

@qiaozha There are 2 places where I added the step back in the yaml files, since we don't run build before the gulp pack step in the ci yaml file and before the npm run build step in the pr yaml file. Can you check these?

Should we change ci.yaml or pr yaml gulp pack step into npm run build? that would be more consistent.

@qiaozha  @weshaggard I changed the solution from generating a file to call a TS script which has a function return both the list of package names and list of package's folder names. That way I can even skip the paths to the samples of the dataplane packages.
Also, I removed the pre-build step from the package.json as this solution doesn't require it anymore. @qiaozha  for your credScan tool PR, you can write reuse the variables from common.ts script to skip the "packagesToIgnore" and "foldersToIgnore"


Logout does a navigate (GET), would be more secure with a POST

As it is now, when you do a logout oauth-service.ts:1769 it simply sets 'location.href'.
While all communication should happen over HTTPS, when (and if) logs get leaked/exposed, one could use information from the URL. Since a POST would also be an option, this would be preferred.

Interesting suggestion. I'm not sure how sensitive logout info would be, but I do suppose it wouldn't hurt to try and hide it from said logs.
As far as I can tell, the relevant spec says nothing explicitly about the http methods that should be supported by the ID Server for the log out endpoint. Still, even though a cursory check at IdentityServer4's code suggest that ID solutions do support it, I wouldn't dare assume that all of them do. So I'd suggest this would have to be an opt-in feature (or otherwise at least part of a major update, possibly with an opt-out toggle).

The current method has a boolean that if true, skips the logout redirect/GET
a second boolean, or a config obj, ... something would indeed make sense
I would however, in documentation, push people into using it (POST), since I would consider it a best practice if supported.

Hello ,
From the OIDC spec  (https://openid.net/specs/openid-connect-rpinitiated-1_0.html ):

OpenID Providers MUST support the use of the HTTP GET and POST methods defined in RFC 7231 [RFC7231] at the Logout Endpoint. RPs MAY use the HTTP GET or POST methods to send the logout request to the OP. If using the HTTP GET method, the request parameters are serialized using URI Query String Serialization. If using the HTTP POST method, the request parameters are serialized using Form Serialization.

Enabling a logout through POST method would not only make sense security wise , but also technically.
In our case some of our logout requests exceed the HTTP url limit of 2048 characters because in some cases the base64 encoded 'id_token_hint' param is too large and the total url exceeds 2048 characters. This results in logout requests being blocked by our WAF (Web Application Firewall).

Technically speaking, your URL should never be longer than 2,048 characters. Any longer than this and Internet Explorer won’t be able to load your page.

The 'id_token_hint' doesn't even have to be that big for the url to exceed the limit ...

@lbuyse Why not just use client_id instead of id_token_hint?

client_id : The most common use case for this parameter is to specify the Client Identifier when post_logout_redirect_uri is used but id_token_hint is not. Another use is for symmetrically encrypted ID Tokens used as id_token_hint values that require the Client Identifier to be specified by other means, so that the ID Tokens can be decrypted by the OP.


Update w2grid.js

The "textSearch" default value shall be "contains" and not "begins" in order to maintain compatibility with previous versions.

Well, I feel it is better to have "begins" as default search operator for text. However, when you define search field, you can pass operator, so this should not cause problems.
searches: [
 { type: 'text', caption: 'Text', field: 'fname', operator: 'contains' }
...
]
``


Completed the cluster generator and added visualization

This still need some refactoring and some clean up. But it works and should be sufficient to move forward.

Seeing a small decrease in coverage. Overriding it for now because next refactoring sprint will increase it again.


Packed resizeBilinear op

Packed resizeBilinear op.
Introduced WEBGL_PACK_ARRAY_OPERATIONS

The logic is copied from non-packed resize_bilinear_gpu.ts, with a change that it is parallelized for all values in 2x2 packed texel. This brings performance improvement as measured by benchmark on integrated GPU Intel® Iris™ Pro 5200 on MacBook Pro (Retina, 15-inch, Mid 2014):
         |  [1,33,33,21]->[1,257,257,21]  |  [1,65,65,21]->[1,513,513,21]
---------------------------------------------------------------------------
master:  |            53.32ms             |            237.33ms
patch:   |            26.87ms             |             86.69ms

resizeBilinear of tensor of shape [1,65,65,21] to tensor of shape [1,513,513,21] (alignCorners = true) is part of DeepLabV3+ MobileNetV2 model.

This change is

@annxingyuan, PTAL.


[occm] Disable openlab jobs and create new jobs in GCP infra

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
The reason we keep the occm openlab jobs is to make sure we build new jobs to replace them, however, keeping those jobs doesn't help anything and only cause confusion for contributors.
Let's remove all those openlab jobs and using this issue to track the job migration task.
What you expected to happen:
How to reproduce it:
Anything else we need to know?:
Environment:

openstack-cloud-controller-manager(or other related binary) version:
OpenStack version:
Others:

+1, we can start by removing zuul jobs in the repo, causing lot of failures on PR creating confusion for new contributors.

@lingxiankong we already have tracking issue open here , https://github.com/kubernetes/cloud-provider-openstack/issues/1613 ,
as openlab jobs are removed now, we can close this issue?

Yes, thanks for finding that one. Let's close this and use #1613 to track the migration.


Tasks if KPI is not reached

When a KPI is not reached it should be possible to create one or more tasks, with starting and end date, cost and responsible, with activities to bring the KPI index back to goal.

This issues request will be into when the "0.6.3" development plan, so need wait some time.

Please provide a detailed description of the process, help to understand development needs.

issues merge to Plan for 0.6.3

Sorry for the delay.
The idea is use PDCA: https://en.wikipedia.org/wiki/PDCA
Here in my organization, when a target is not reached, we create a FCA - Fact, cause, action. I mean, if a target is no reached, we registrer what, why and how we can correct this.
My sugestion is when a target is not reached can create a FCA.
The FCA must contain:
Fact - description of the fact
Cause - root cause analysis
Action - the action taken to resolve the problem
It is necessary a person resposable, dates to start and finishe and cost.

This part will be the reference PDCA/FCA, adding the plan 0.6.3
issues move to : https://github.com/billchen198318/bamboobsc/issues/14


Parca continous exporting profiles even when relabel config explicitly disallows it

Describe the bug
When parca-agent is configured to only keep profiles with a certain label, it still doesn't prevent ingesting mismatched profiles that lack that label. In our case we have a kubernetes cluster where parca-agent is deployed, and the agent is configured to only keep app=$X through a  relabel_configs entry. But I can still see profiling traces this being ingested in PolarSignals UI when I query app!=$X.
To Reproduce
This is our ConfigMap:
Name:         parca-config

Data
====
parca-agent.yaml:
----
relabel_configs:
- source_labels: [app]
  regex: fal-isolate-controller
  action: keep

And this is the Pod information:
[...]
    Mounts:
      /config from config (ro)
[...]
Volumes:
  config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      parca-config
    Optional:  false

Expected behavior
Not seeing any app!=$X on the UI.
Screenshots or Profiles (using https://pprof.me)

Logs

Don't see any errors/unusual warnings in the logs.
Software (please complete the following information):

Parca Agent Version: ghcr.io/parca-dev/parca-agent:v0.26.0
Parca Server Version (if applicable): PolarSignals

Workload (please complete the following information):

Runtime (if applicable): Python
Compiler (if applicable): -

Environment (please complete the following information):

Linux Distribution: Same as the parca-agent docker image
Linux Version: 5.15.107+
Arch: x86_64
Kubernetes Version (if applicable): v1.25.10-gke.2700
Container Runtime (if applicable): COS

Additional context
Context from discord: https://discord.com/channels/813669360513056790/913454681878048868/1170356803712843946

@isidentical Could you please share the label set on your target workload?
Hovering over a sample should do the trick. e.g.

This is a positive match (app="fal-isolate-controller")

And this is a negative one (app!="fal-isolate-controller") that shouldn't have been ingested (?)

With the suggestion of @kakkoyun, we noticed --config-path was missing from the set of arguments which means anything that I put was ignored 🤦🏻 There is no real issue with parca on that front, it was entirely on my side.


migrate to cobra

When I run nerdctl build . -t a:b, it success but without producing image a:b. And I read the code of nerdctl, noticed that nerdctl is using github.com/urfave/cli/v2. It doesn't support parse flag after args. i.e. nerdctl build . -t a:b vs nerdctl build -t a:b ..
And, I noticed that helm use github.com/spf13/cobra, so I compare those.
cobra support parser flag after args, and support bash/fish/powershell/zsh completion, completion function is simple, just have to process argument's completion.
So, I think it's time to migrate to github.com/spf13/cobra. Any ideas?

SGTM as long as it does not cause any regression

SGTM as long as it does not cause any regression

I just noticed that cobra doesn't allow child command to override parent command's flag by shorthand.
logs command use -n as --tail, and it conflicts with -n for --namespace in root command.
https://github.com/spf13/cobra/issues/1486

The Docker CLI seems to use spf13/cobra, for instance: https://github.com/docker/cli/blob/e3023ca3e363f04ecec2e50f43307b6b171f9698/cli/command/container/cmd.go#L6 ... somehow they must have been able to get that working in the first place?

Doesn't look like an issue if I'm hopefully not mistaken, here's Docker's implementation: https://github.com/docker/cli/blob/154ce5e58d672d3c45313a1a61cb2a7a5900f52a/cli/command/container/logs.go#L46


AMD module

Fixes #50.
If AMD loader is present (basically when (typeof define === 'function' && define.amd !== undefined) is truthy) the script registers itself as anonymous AMD module without polluting global window-object or extending jQuery.
This means that one can use the script by:
require(['http://example.com/url.min.js'], function(privateJsUrl) {
  console.log(typeof window.url); // -> undefined
  console.log(typeof $.url); // -> undefined
  console.log(typeof privateJsUrl); // -> function
  console.log(privateJsUrl('domain', 'http://foo.bar.example.com')); // -> example.com
});

Thx, will take a look at this shortly.
On Feb 9, 2017 02:00, "Ari Palo"<EMAIL_ADDRESS>wrote:

Fixes #50 https://github.com/websanova/js-url/issues/50.
If AMD loader is present (basically when (typeof define === 'function' &&
define.amd !== undefined) is truthy) the script registers itself as
anonymous AMD module without polluting global window-object or
extending jQuery.
This means that one can use the script by:
require(['http://example.com/url.min.js'], function(privateJsUrl) {
console.log(typeof window.url); // -> undefined
console.log(typeof $.url); // -> undefined
console.log(typeof privateJsUrl); // -> function
console.log(privateJsUrl('domain', 'http://foo.bar.example.com')); // -> example.com
});

You can view, comment on, or merge this pull request online at:
https://github.com/websanova/js-url/pull/54
Commit Summary

add .editorconfig
format url.js with editorconfig
wrap to IIFE and explicitly assign to window
define as AMD module
update minified version
fix AMD definition
describe AMD functionality
some text adjustment on README
some text adjustment on README
some text adjustment on README

File Changes

A .editorconfig
https://github.com/websanova/js-url/pull/54/files#diff-0 (12)
M README.md
https://github.com/websanova/js-url/pull/54/files#diff-1 (4)
M url.js https://github.com/websanova/js-url/pull/54/files#diff-2
(291)
M url.min.js
https://github.com/websanova/js-url/pull/54/files#diff-3 (2)

Patch Links:

https://github.com/websanova/js-url/pull/54.patch
https://github.com/websanova/js-url/pull/54.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/websanova/js-url/pull/54, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABkcyySDunH01-Hd8wpNxgX8bjmnE41sks5rahC0gaJpZM4L7OJO
.

Ok, this has been pushed up as v2.4.0

Thx, for adding this :-)

Can't see v2.4: https://github.com/websanova/js-url/releases
Thus bower installs 2.3.1

Whoops, sorry. Pushed now.
https://github.com/websanova/js-url/releases/tag/v2.4.0
On Thu, Feb 16, 2017 at 5:11 AM, Oytun Tez<EMAIL_ADDRESS>wrote:

Can't see v2.4: https://github.com/websanova/js-url/releases
Thus bower installs 2.3.1
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/websanova/js-url/pull/54#issuecomment-280156740, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABkcy2GCaYUeU9g4kiIxB-QoprXXDzNWks5rc3gRgaJpZM4L7OJO
.

Perfect! Pulling it right away. Fresh release, mmmmmm...


chore(master): release 0.43.2

:robot: I have created a release beep boop
0.43.2 (2024-10-24)
Bug Fixes

remove unused properties from first time created config.yaml (#439) (#440) (3e9c0b7)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/swarm-desktop/releases/tag/untagged-a0a9860f05756bed7ef9 :sunflower: