Streaming support?

Does this library support streaming of the audio data to the APIs? I can't find it in the documentation but since some APIs support it it would make the process of capturing audio -> text transcription faster.

Hi @edevil,
Support for this is planned for the next major version. However, it will require significant backward compatibility breaks to do properly. I don't really have time to work on that at the moment, but it's definitely on the roadmap.

I would also be very interested in this. Could you point me in the right direction so I could take a look?

The current work for that is in the streaming branch of this repository. Haven't worked on that for a while, though.

It would be awesome if you guys figure out a easy way to implement this. For me, this is a must on any speech recognition lib. I wish I was pro on python to help you guys out. :p

Hey I know it's been a few years, but is there any updates on the topic?
I was looking for ways to get real time results from google on long recordings, some basic speech feedback you know..
I believe it's called streaming.


Only list vendors in the data map as vendors_disclosed in the FE

Bug Description
After another reread of the spec, we think it makes sense to only list the vendors in both the datamap and the GVL in the vendors_disclosed section of the TC string. See the discussion here: https://github.com/ethyca/fides/pull/4160#discussion_r1337694296
The backend has gone ahead and made this change, so we should do something similar for the FE!
Steps to Reproduce

Set up your TCF environment
Opt in or opt out of all
Check your TC string—it'll have a huge vendors disclosed section since it lists every vendor in the GVL when it should really only list the vendors we are showing in the vendor tab.

Expected behavior
The vendors disclosed section should only show the vendors in the vendor tab.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

Version:
OS:
Python Version:
Docker Version:

Additional context
Add any other context about the problem here.

Actually, it looks like we should not be including this string at all when the CMP API surfaces it
🤔 https://ethyca.slack.com/archives/C05E74TR0BB/p1696341554803559

Okay we no longer surface the vendors_disclosed string as part of the CMP API: https://github.com/ethyca/fides/pull/4244/files
However, I am still confused about how to actually properly set the vendors_disclosed string, as the library seems to insist that we set all the GVL vendors. more investigation needed!


crypto/tls: TLS 1.3 unable to disable non-NIST approved ChaCha20 Cipher Suite

What version of Go are you using (go version)?
go version go1.18.4 linux/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
golang:1.18:4 docker image

What did you do?

Attempted to disable the ChaCha20 TLS 1.3 suite as it is not approved by NIST yet by removing it from cipher list:
package main

import (
	"crypto/tls"
	"log"
	"net/http"
)

func main() {
	server := http.Server{
		Addr: "localhost:2443",
		TLSConfig: &tls.Config{
			CipherSuites: []uint16{tls.TLS_AES_256_GCM_SHA384,tls.TLS_AES_128_GCM_SHA256},
			MinVersion:   tls.VersionTLS13,
		},
	}
	log.Fatal(server.ListenAndServeTLS("localhost.pem", "localhost-key.pem"))
}

I then tried to force a client to choose the ChaCha20 suite:
openssl s_client -connect localhost:2443 -ciphersuites TLS_CHACHA20_POLY1305_SHA256

What did you expect to see?
To error when a client tries to force the ChaCha20 cipher suite to be used
What did you see instead?
---
New, TLSv1.3, Cipher is TLS_CHACHA20_POLY1305_SHA256
Server public key is 4096 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 18 (self signed certificate)
---

Background
FIPS 140-3 seems to be approving all the components of TLS 1.3 except the ChaCha20 suite. This has ruffled many feather as this Public Response on the NIST website points out:

Limiting the label to only NIST approved cryptography seems overly restrictive. For example,
software may include support for TLS 1.3, which can include ChaCha20/Poly1305 and neither of
those are NIST approved as of today.

The response doesn't point out that there is a CAVP for TLS 1.3 Key Derivation Function so that looks like it is going to be accepted/tolerated, but there seems to be active silence regarding ChaCha20.  There is seemingly no way currently to get it approved.
Regarding issue ##29349, it basically left off with:

what would work here would be to open a new one about a use case (not about a specific solution) with supporting information to show what the requirements are like and how common they are

So that is what I am trying to do. NIST can very well change its mind and approve ChaCha20, but it right now there is no real indicator that they will and many indicators that TLS 1.3 will be approved in FIPS environments without it.

cc @golang/security

Disabling ChaCha20Poly1305 is a solution, not a use case. The implicit use case seems to be FIPS 140-3 compliance, but just disabling a couple cipher suites does not get you within any compliance framework that I'm aware of. Can you tell us more about what requirements you are trying to comply with?

Without getting into the specifics, I am aiming at the very least for the non-technical designation of "FIPS 140-3 compliant" (IE: A threat scanner would show the same ciphers being advertised as valid FIPS 140-3) with the idea that there is still a valid path to lower class, Hardware/Hybrid module validation using Go code.

I have tracked down a more explicit 'snub' of ChaCha20 from NIST.
Per the latest NIST Guidance on TLS, NIST 800-52r2 Appendix B.2 "Interpreting Cipher Suites Names in TLS 1.3":

As shown in Section 3.3.1, these cipher suites have the following form:
TLS_AEAD_HASH
AEAD indicates the AEAD algorithm that is used for confidentiality, integrity, and message authentication. The NIST-approved TLS 1.3 AEAD algorithms comprise a NIST-recommended block cipher and NIST-recommended AEAD mode.
HASH indicates the hashing algorithm that is used with the HKDF during key derivation.
The following examples illustrate how to interpret TLS 1.3 cipher suite names:
• TLS_AES_256_GCM_SHA384: Messages are encrypted and authenticated with AES256 in GCM mode, and SHA-384 is used with the HKDF.
• TLS_AES_128_CCM_SHA256: Messages are encrypted and authenticated with AES128 in CCM mode, and SHA-256 is used with the HKDF.
The negotiation of the key exchange method is handled elsewhere in the TLS handshake.

The ChaCha20 Suite is the only TLS 1.3 suite omitted from this section and there is no mention of it in the entire document.

@FiloSottile, FIPS aside, I believe that "we only allow explicitly NIST approved ciphers or functions within our security boundary" is a valid use case.
Right now there is no evidence that ChaCha20 is NIST approved so it seems reasonable to just allow it to be disabled.
I also understand that there may be some other tweaks in order to satisfy this use case such as potentially also disabling 'x25519'; however, I will need to look at that more and in another ticket.

ChaCha20Poly1305 is not part of any NIST framework, that's for sure.
However, "the non-official designation of FIPS 140-3 compliant" is, as far as I can tell, a made up target. crypto/tls is built to minimize complexity and configuration options, and to do that we need to minimize the targets we support. FIPS 140 is a popular one, so although it isn't officially supported, you can look into the BoringCrypto branch or Red Hat's solutions to find a way to satisfy that compliance requirement.
Part of the goal of the BoringCrypto branch is to bottle up the compliance-driven requirements so they don't affect other users. Satisfying a request like "I want some of the configurability to meet some sort of FIPS-like target but without the other negative side-effects" would require leaking the side-effect (like extra complexity due to configurability) into the code that everyone unconstrained by compliance uses.
I suggest you look into the existing FIPS compliance options. This is not official advice, but it sounds like simply building the BoringCrypto experiment would make your threat scanners happy.

"we only allow explicitly NIST approved ciphers or functions within our security boundary" is a valid, non-made up target. Guides for satisfyingly this target are pretty easy to find; here is the one for OpenShift .
As for the general compliance vs complexity argument. TLSConfig has non-uniform behavior when setting the ciphers for TLS12 vs TLS13. I would argue that most users would expect the TLSConfig to actual configure the cipher suite as directed and not just ignore it silently. Keeping the behavior the same between TLS12 and TLS13 would make usage less complex.
As for the boring branch being the defacto compliance branch. last i experimented with it, it was not suited for ARM targets, (huge performance hit and arch macros prevented the FIPS parts to compile) .
Finally the CHACHA20 suite is not mandatory even by the RFC specification (it gets a SHOULD not a MUST):

A TLS-compliant application MUST implement the TLS_AES_128_GCM_SHA256
[GCM] cipher suite and SHOULD implement the TLS_AES_256_GCM_SHA384
[GCM] and TLS_CHACHA20_POLY1305_SHA256 [RFC8439] cipher suites (see
Appendix B.4).


Fix build on macOS

Current zlib-ng defines _POSIX_C_SOURCE, which causes macOS sys/types.h
to not define types like u_char and u_int, which leads to compilation
errors when including other headers that use those types.
Define _DARWIN_C_SOURCE to work around this, which causes macOS
sys/types.h to define these types again.

Test fix, to evaluate on CI.
Thanks to @Byron for further investigation on a macOS system.

This passes CI on macOS, but the previous version did as well. @Byron, does this fix the issue you observed in https://github.com/rust-lang/libz-sys/commit/5c4704efa6ae73a95c3c6e1ccf4bd212f927be7a#commitcomment-68180284 ?

Unfortunately it doesn't quite work yet, even though the new define did indeed show up:
running: "cmake" "/Users/byron/dev/github.com/rust-lang/libz-sys/src/zlib-ng" "-DBUILD_SHARED_LIBS=OFF" "-DZLIB_COMPAT=ON" "-DWITH_GZFILEOP=ON" "-D_DARWIN_C_SOURCE=1" "-DCMAKE_INSTALL_PREFIX=/Users/byron/dev/github.com/rust-lang/libz-sys/target/debug/build/libz-sys-ffb81820f742554e/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -arch arm64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -arch arm64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_ASM_FLAGS= -ffunction-sections -fdata-sections -fPIC -arch arm64" "-DCMAKE_ASM_COMPILER=/usr/bin/cc" "-DCMAKE_BUILD_TYPE=Debug"

How could I forget fighting odd defines 10 years ago, this definitely brings back some memories 😅.

Unfortunately it doesn't quite work yet, even though the new define did indeed show up:
running: "cmake" "/Users/byron/dev/github.com/rust-lang/libz-sys/src/zlib-ng" "-DBUILD_SHARED_LIBS=OFF" "-DZLIB_COMPAT=ON" "-DWITH_GZFILEOP=ON" "-D_DARWIN_C_SOURCE=1" "-DCMAKE_INSTALL_PREFIX=/Users/byron/dev/github.com/rust-lang/libz-sys/target/debug/build/libz-sys-ffb81820f742554e/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -arch arm64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -arch arm64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_ASM_FLAGS= -ffunction-sections -fdata-sections -fPIC -arch arm64" "-DCMAKE_ASM_COMPILER=/usr/bin/cc" "-DCMAKE_BUILD_TYPE=Debug"

How could I forget fighting odd defines 10 years ago, this definitely brings back some memories 😅.

Now it works 🎉🎉🎉!
Thanks so much!

Excellent! Merging to fix macOS then.


Ci release

Similar to #189 to have a better build and release CI pipeline

I currently have exams. I'll come back to this in a week :)

I currently have exams. I'll come back to this in a week :)

All good
I was away for quite some time! I just added you so that you are informed if interested.


Automatically detect the make:command command option

This PR updates the make:command command to default the --command option to the colon separated class name without the Command suffix.
It's pretty common for Laravel apps to use the same name for the class and the command $name, i.e.

App\Console\Commands\Inspire -> inspire
App\Console\Commands\ImportCsv -> import:csv

Some developers prefer to use a Command suffix on the class, i.e. App\Commands\InspiringCommand -> inspiring.
Currently you have to specify the command option manually like this:
php artisan make:command Inspire --command inspire

This is pretty tiring if you are making a lot of commands. Since there isn't a default and it's up to the developer to decide on the name it's easy to end up with inconsistent names on larger projects.
This PR changes the make:command generator to default the --command to the colon separated class name of the command without the Command suffix.  For example:

SendCommand -> send
Send -> send
SendEmailCommand -> send:email
SendEmail -> send:email
SendEmailWelcomeCommand -> send:email:welcome

You can still manually specify the --command option if you don't want to use the defaults.
I tried to add a test but there aren't any existing tests for generator commands and it's really difficult to set the test up.

Hmm, having more than one colon probably isn't desirable. Maybe it should produce:
send:email-welcome

for the last case?

I was thinking of that example being a case where you have subcommands of a subcommand. I generally use a dash if it's a compound word noun and a colon if it's a subcommand, i.e. you might have:
send:email:welcome
send:email:password-reset
send:notification:welcome

The only example I really know of of a Laravel app nesting commands that far is Laravel Doctrine though.
Since we can't really tell if it's a compound word or a sub command and we probably shouldn't be encouraging sub commands > 2 levels deep I agree that using a dash for everything after the first one makes sense.

IMO this will have to be too opinionated to be in the framework. If you're creating so many commands that saving a few keystrokes is a big deal, have a custom command in your app that handles this. Then you can be as opinionated as you like.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Require min Istio version 1.11 to deploy Delta app

Having ISTIO_DELTA_XDS enabled prior to version 1.10 causes the Delta deployment to hang.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

is this because the delta API was not implemented 1.10 and back?

Yeah I believe so.


Improvements for adding events

Issue #, if available:
No existing issue
Description of changes:
This PR improves the code for creating new events. The main enhancement is a fix to avoid accessing UI APIs on a background thread when adding an event, which triggered the main thread checker.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I rebased the commits, but let me quickly check that I merged correctly. Will update this PR when I'm done

All good – ready for merging @rohandubal


v0.0.8 failing for internet explorer 9.

hi,
something in 0.0.8 is stopping the charts from rendering in ie 9 (9.0.8112.16421)...
i tried reverting to 0.0.7 and it works okay...
interesting to note though, w/ 0.0.8 and IE 9, it works if i open F12...
it continues to work even after i close the developer console... until i restart IE.

Interesting. Let me know fi you can find the specific error.

@bhtek Did you ever find out anything more about this particular issue?

I am afraid not. Sorry.
On 7 Sep 2015 02:33, "Matt Sidor"<EMAIL_ADDRESS>wrote:

@bhtek https://github.com/bhtek Did you ever find out anything more
about this particular issue?
—
Reply to this email directly or view it on GitHub
https://github.com/pablojim/highcharts-ng/issues/289#issuecomment-138109233
.


Setting GTK+ and KDE themes will be a necessary part of the Settings app I make so apps look correct, so I need to know the themes and config file locations.

There are a bunch of config files listed here that should help a lot when setting themes: https://github.com/shalva97/kde-configuration-files
My Settings app will have a page that covers the most-common theme settings for KDE/Maui, (most) non-KDE Qt, and GTK+ apps, but I may miss some things, so people will need to install the relevant config packages if they need those settings. If possible, all the theme-related settings for these major UI toolkits will be in their own pivots on one page. The entry in the Settings app's page list will probably be either "other theme settings" or "non-Retiled theme settings", with the text below it being "Theme configuration for KDE, GTK+, etc. apps". I don't think non-KDE Qt apps use different theme settings from KDE apps when running on KDE, which is what I'm trying to make them think they're doing when running on Retiled if they don't have support for Retiled-specific things.
There should be a link to this page from the bottom of the "start+theme" page of Settings, possibly with the text of "Configure themes for apps not designed for Retiled".

If I need to have a toggle switch for any theme configuration, then I can't use a pivot since it's not allowed on Windows Phone and I think that's because sliding a control while on a horizontal-sliding page is undefined behavior or something. That makes sense if the reason is due to it being too easy to mess with the toggle switch while swiping through the pivots.
I'd then have to probably use either an appbar with navigation buttons on it, or list buttons on a main subpage for the other theme settings page.

As described in a comment on #129, MauiProject apps have a global theme config file (mauiproject.conf) file as described here: https://mauikit.org/blog/maui-report-18/
An example as pasted from that page is available below for reference:
[GLOBAL]
CSD=true

CSDStyle=Nitrux

DARK_MODE=true

The page says the new feature is allowing dark mode to be set for all apps, but the entire file will be useful for setting the user's theme.


v15.2.3 fix mobile view

[Current coverage][cc-pull] is 100%

Merging [#372][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master   #372   diff @@
====================================
  Files          24     24
  Lines         365    365
  Methods        77     77
  Messages        0      0
  Branches        0      0
====================================
  Hits          365    365
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last updated by [d989ffd...ea922b8][cc-compare]
[cc-base-branch]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/compare/d989ffdb8547c7cd51336dbf781c06d358b2619c...ea922b87008dc0caed9860098b874461004d8cd7
[cc-pull]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/pull/372?src=pr


fix: default INVALID_TOOL_MSG_TEMPLATE

The default template in tool_executor is incorrect and has not properly replaced availableToolNamesString.

Thank you!


Fenix2GSX issue when boarding with deboarding only selected to stand

Hello,
Please see attached GSX profile for MK Studios Dublin,
To replicate load up a flight from any of the PBZ stands e.g. 417.
Context - On the PBZ gates pax walk to the aircraft, during de-boarding a bus is sent (as real life at these gates).
Replication:
Begin boarding.
Findings;
-> When using Fenix2GSX, a bus is sent in addition to pax walking to the aircraft, boarding will loop as a result.
-> When not using Fenix2GSX no bus is sent and the profile works correctly during boarding.
eidw-MKStudios.zip

Well, it is great that you put so much Effort in that Report (wished some Users would do half of that), but a Log would have been nice.
Seems more like the usual weird Behavior of GSX. From what I've seen in my Tests, it seems to evolve around Crew-Boarding. Depending on how that is skipped GSX will either send the Crew-Bus, the Passenger-Bus or no Bus (as it is intended by the Profile for that Spot).
When I recall correctly, the only way to workaround that is: Do not skip the Crew-Question with via Fenix2GSX or GSX and manually Answer it with "nobody" when the Question pops-up.
Will need to look into if there is a Way to implement (yet another) GSX-Workaround in Fenix2GSX.
Don't know if I have the Energy to report that to FSDT, I'm currently just too fed up for yet another Explanation why everything and everybody else is the Problem because GSX in its perfect Design works as intended 🤷♂

Have attached the logs for you here if it helps you, thank you for the detailed reply! And I understand completely your frustrations with GSX.
Fenix2GSX20241007.zip
Fenix2GSX20241010.zip
Fenix2GSX20241011.zip

Since it 3 Days of Logs: when was the Session with described Situation in Dublin? ;)

Both the 10th and 11th, many thanks :)

I give up.
Spend hours yesterday and tried different Workarounds. GSX will only not send a Bus when you keep the Menu enabled and operate it manually ... we just have to live with that I guess 🤷♂


NB2 parameters about the chat "input_crop_TSUM_parameters_maiz_sugar"

Hi, here are 2 questions about the "input_crop_TSUM_parameters_maiz_sugar" parameters:

We noticed that "min_cycle_len, max_cycle_len and height" are new parameters in pyAEZ 2.2, in  GAEZ appendix https://s3.eu-west-1.amazonaws.com/data.gaezdev.aws.fao.org/documentation/GAEZ4_Appendices.xlsx. There are no references to the three parameters; I wonder if we could get them from our own experience in our study area. I would be grateful if you provided some reference sources for me.
"Adaptability" has been shown in the PDF "PyAEZ: Crop Simulation" , but I didn't find the corresponding reference in the appendix.  I would be grateful if you provided some reference sources for me.
The high light below are issue parameters that have been mentioned.

Hi @WeirdCxychen,

For the cycle length settings, there are no standardizations, due to different regions, species and many reasons. However, there is a database named ECOCROP (source: https://gaez.fao.org/pages/ecocrop-find-plant) where more than 50 crop's characteristics, where cycle length's minimum and maximum extent can be referred.
In AEZ methodology, adaptability refers to the terminology "Crop Climatic Adaptability" depending on distinctive crop photosynthesis characteristics in relation of temperature and radiation for biomass productivity. I'm providing an online FAO document from AEZ study in Kenya (Source: https://www.fao.org/3/t0741e/T0741E06.htm#ch6.1). There is little concept regarding crop adaptability but they cited many FAO documents which you can refer to.

Height is named as plant height (in meters).

@WeirdCxychen 我也遇到了同样的问题，看了这个之后 我解决了我的问题

Hi @NokuzaSezo97,
Thank you so much for your advice!
Regards,
Xinyue Chang

i can't find the D1 & D2 paramater in GAEZ4_Appendices.xlsx, can you tell me where is it ?


Automated cherry pick of #2461: fix snapshot can't delete

Cherry pick of #2461 on release/2.11.
#2461: fix snapshot can't delete

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@b70c8a6). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.11   #2463   +/-   ##
==============================================
  Coverage                ?   7.07%
==============================================
  Files                   ?     454
  Lines                   ?   71720
  Branches                ?       0
==============================================
  Hits                    ?    5073
  Misses                  ?   66228
  Partials                ?     419

Flag
Coverage Δ

#aFlag
7.07% <ø> (?)

Impacted Files
Coverage Δ

pkg/compute/models/regiondrivers.go
20% <ø> (ø)

Continue to review full report at Codecov.

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

/lgtm

/approve


Setup child parser

It would be really useful to setup a way to specify a child parser so that it's possible to use it for hugo templated js file as well as hugo templates HTML or templates json, yaml or xml.

This will be very difficult, as the current implementation kind of depends on the html formatter. In case this project gains enough traction I'll rewrite the parser with this in mind, but atleast for now this is out of scope.
I'll leave this open, because it is a very good suggestion. Could also be helpful with markdown.
Also I'm very sorry for answering this late, just missed this issue in my mail notifications👀

This will be very difficult, as the current implementation kind of depends on the html formatter. In case this project gains enough traction I'll rewrite the parser with this in mind, but atleast for now this is out of scope.
I'll leave this open, because it is a very good suggestion. Could also be helpful with markdown.
Also I'm very sorry for answering this late, just missed this issue in my mail notifications👀

I think this could be quite doable as a long term goal. With the new implementation from #49 I should be able to switch to a different child parser.
Once all the basic features are done I'll come back to this.

Support for YAML would be of great help for Helm Charts, for example.


Graphics.drawTriangles does not work without indices

Indices are an optional (default null) parameter, however drawTriangles immediately aborts if they are missing:
https://github.com/openfl/openfl/blob/c2d593029ee9bc43e82531c9b4d7f170d128dc16/openfl/display/Graphics.hx#L531
Despite generating them if they were missing, further down:
https://github.com/openfl/openfl/blob/c2d593029ee9bc43e82531c9b4d7f170d128dc16/openfl/display/Graphics.hx#L541-L557
The first null check should not be there.
Also it aborts if uvtData is null, which is also an optional (default null) parameter.
It's not clear if this is legal or not. If not, this parameter should not be optional with a default value of null. If it is legal then this null check should also not be at the head.

Thanks for the heads-up :smile:
This was an oversight. On my version, it worked after removing those parameters, but the fill did not work properly on our Cairo renderer. A few fixes and this basic sample works for me:
package;

import openfl.display.Sprite;
import openfl.Vector;

class Main extends Sprite {

	public function new () {

		super ();

		graphics.beginFill (0xFF8000);
		graphics.drawTriangles (Vector.ofArray([
			10,10,  100,10,  10,100,
			110,10, 110,100, 20,100.]));

	}

}


Display In-Stock Quantity in Order Card

What is the motivation for adding/enhancing this feature?
The Order card in our application does not display the in-stock quantity of the ordered item. This missing information makes it difficult for users to quickly assess the availability of the product in the store at the time of order processing.
What are the acceptance criteria?
The Order card should include the in-stock quantity of the ordered item. By displaying this information, users can easily determine if there is sufficient stock to fulfill the order or if additional actions need to be taken to manage inventory.
Can you complete this feature request by yourself?

[ ] YES
[ ] NO

Additional information

Thanks @Dhiraj1405 we will pick this after the first released version of this app.


add code to create in-memory hdu from a postage stamp

Coverage increased (+2.6%) to 34.943% when pulling ac4f44275495962f86b09f9aec5c25f64288e05c on u/jchiang/in_memory_hdus into 3370c9c75ba626b018057ece3258844f6ebeadcd on master.


(Post-Tutorial Question) Drawing an image with ImGUI.

Howdy,
It's been a little while since I finished this tutorial, and I was just wondering if you tried to draw an image into an ImGUI frame? I ran into some issues myself and I was just unsure if I was doing it wrong. In online forums, people have said that it's because it's designed for OpenGL when using LWJGL.
So I guess the question if you do run into ths is: would you recommend an alternative library or doing it without a libray?

Hi, it should be possible to do that. I do not understand why they mention OpenGL. In any case, I will try to check an example to see how it can be done, You are trying to display a texture?
Another alternative should be nuklear, which, if I recall corectly, LWJGL has bindings for it.

Yes, specifically displaying a Vulkan texture into an ImGui frame. This is a related bug ticket link. https://github.com/SpaiR/imgui-java/issues/185

Ok. This seems to be solved here. Now you can use longs as texture ids and use the descriptor set associated to the texture. Let's wait for a new release of imgui to be published.
In any case, I will leave this issue open to include a specific example. This will be done in the new version of the book, which uses Vulkan latest features (still in progress). Right now the GUI render class does not care about texture ids (and it should)

I just saw that Imgui java port just uploaded a new version which seems to support longs for texture ids: https://github.com/SpaiR/imgui-java

This is fixed in new version in the book. Right now is just code (no explanation text) in a private repo, I expect to set up a public branch soon (meaning weeks or a couple of months)


How To Add Pure CSS Waves To Your Website

Article checklist
Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes
`This closes #4825

Add author details!

Add author details!

Got it!

added the needed details. @jumamiller

What's wrong? @jumamiller

What's wrong? @jumamiller

Kindly be a little patient. I have seen the updates!

What's wrong? @jumamiller

Kindly be a little patient. I have seen the updates!

I'll review your work as soon as possible!

thank you for the affirmation @jumamiller

Hallo. I believe they are. However, you can list the areas where you feel i
should expound on more. Thanks
On Tue, Nov 30, 2021, 20:55 jumamiller @.***> wrote:

@.**** requested changes on this pull request.
Hi, kindly ensure all code snippets are explained!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/section-engineering-education/engineering-education/pull/5193#pullrequestreview-819375062,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUORJKAR4FWJVUAL7MQXCATUOUF25ANCNFSM5IUSHKEA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@jumamiller
If needed lets consider pinging our team for help - we have more than enough pull request.
No need to assign yourself more than needed 👀

@jumamiller
Thank you for the great feedback - lets take a look at the recent changes provided.
IF any other revisions are needed - lets provide some guidance on how to get the article up to par - and CLOSE the PR. To allow the author the proper time to make any and all needed corrections.
This is a duplicate PR - if any more changes were needed (in general) we should close the PR immediately especially if its a duplicate PR (generally there are always exceptions).

@jumamiller
If any more major revisions are needed - we will be closing this PR asap. 👀
@lin-chez
Please be sure you are going over the entire article for any other mistakes or errors, as our peer reviewers are not responsible to point out every mistake - that is the authors responsibility to properly review and proofread their work.

Hi, work on the minor edits suggested!

@jumamiller Hallo! I believe all requested changes were met, kindly approve them or point out other sections that need my attention. Thanks.

@lin-chez, I'm testing your codes currently. Could you kindly add a github repo for the complete site and provide a link?

@lin-chez, I'm testing your codes currently. Could you kindly add a GitHub repo for the complete site and provide a link?

@jumamiller kindly clarify the need for a GitHub repo when the complete code is featured on the last segments of the article.

@lin-chez, I'm testing your codes currently. Could you kindly add a GitHub repo for the complete site and provide a link?

@jumamiller kindly clarify the need for a GitHub repo when the complete code is featured on the last segments of the article.

Cloning a project is easier than copy pasting?

I had to fork the repo for this article to act as my reference in the future. I really loved the animation!

Hope it helps other devs out there!

@jumamiller Thank you for the wonderful remarks. I also thank you for your patience, I gained some tips on how to better my services. For that am grateful.😊

jumping on this one


Using Meteor.js methods with saga

Can anybody suggest how can I use server side methods with saga in Meteor.js?
With redux thunk I have something like this in action:
import {saveTicket} from '/lib/methods/methods';

export const USER_SAVED_TICKET = 'USER_SAVED_TICKET';
export function userSavedTicket(content) {
  return (dispatch, getState) => {
    saveTicket.call(content, (error, result) => {
      if (error) {
        dispatch(ticketSaveFailed(error.reason));
      } else {
        dispatch(ticketSaveSucceeded());
      }
    });
  }
}

export const TICKET_SAVE_SUCCEEDED = 'TICKET_SAVE_SUCCEEDED';
export function ticketSaveSucceeded() {
  return {
    type: TICKET_SAVE_SUCCEEDED,
  }
}

export const TICKET_SAVE_FAILED = 'TICKET_SAVE_FAILED';
export function ticketSaveFailed(errorReason) {
  return {
    type: TICKET_SAVE_FAILED,
    errorReason,
  }
}

my saga is:
import { take, put, call, fork, select } from 'redux-saga/effects';
import {saveTicket} from '/lib/methods/methods';

export default function *ticketSaved() {
  const { ticket } = yield take({ type: 'USER_SAVED_TICKET_SAGA' });
  const { err, res } = yield call(saveTicket.call, ticket);

  if (err) {
    yield put({ type: 'TICKET_SAVE_SUCCEEDED' }, err)
  } else {
    yield put({ type: 'TICKET_SAVE_FAILED' }, res)
  }
}

but it doesn't work... I can't figure out how to call this method :worried:
and action:
export const USER_SAVED_TICKET_SAGA = 'USER_SAVED_TICKET_SAGA';
export function userSavedTicketSaga(content) {
  console.log("#userSavedTicketSaga action runned");
  return {
    type: USER_SAVED_TICKET_SAGA,
    content,
  }
}

@kefirchik We recommend you to ask on StackOverflow with redux-saga tag.
In this line, call effect won't wait for a callback of saveTicket function.
const { err, res } = yield call(saveTicket.call, ticket);

Please consider using eventChannel to handle a callback of saveTicket function properly.
eventChannel is often used integrating saga with external services that have a callback/event-based API.
For example, the following code is an example of using Page Visibility API of web browsers with redux-saga.
https://github.com/kuy/redux-saga-examples/blob/master/startstop/sagas.js#L49
Demo: http://kuy.github.io/redux-saga-examples/startstop.html
GitHub: https://github.com/kuy/redux-saga-examples/tree/master/startstop


eCl@ss was renamed to ECLASS

eCl@ss was renamed to ECLASS: update eCl@ss in all questions and answers

was accepted on 31.05.

closed in c1696bd49b34daca118f9b2b56ec5681aa015f97


router guard error causes SSR request to never complete

Versions

nuxt: v2.14.0
node: v14.5.0

Reproduction
https://codesandbox.io/s/inspiring-nash-hknkc?file=/plugins/router-error.js
According to vue-router navigation guards documentation, the next() function can be called with an error.
However, calling next() with either an error or false during SSR will cause the server never to respond.
Here are the attempts I made:

Using `next(err)`
export default function plugin({ app, error }, inject) {
  app.router.beforeEach(async (to, from, next) => {
    try {
      await someAsyncTask()
      next()
    } catch (err) {
      next(err) // Will cause the server to hang indefinitely
    }
  })
}

Using `onError`
export default function plugin({ app, error }, inject) {
  app.router.onError(error) // Will cause the server to hang indefinitely
}

Using `next(false)`
export default function plugin({ app, error }, inject) {
  app.router.beforeEach(async (to, from, next) => {
    try {
      await someAsyncTask()
      next()
    } catch (err) {
      next(false) // Will cause the server to hang indefinitely
      error(err) // Does nothing
    }
  })
}

Workaround
export default function plugin({ app, error }, inject) {
  app.router.beforeEach(async (to, from, next) => {
    try {
      await someAsyncTask()
    } catch (err) {
      error(err)
    } finally {
      next() // The route will still be loaded, but never shown...
    }
  })
}

Steps to reproduce
export default function plugin({ app, error }, inject) {
  app.router.beforeEach(async (to, from, next) => {
    next(new Error("Some async error"));
  });
}

What is Expected?
Nuxt should handle vue-router navigation errors (esp. during SSR)
What is actually happening?
Nuxt does not handle router errors, causing the requests to hang indefinitely

Should be fixed with v2.14.1


Fixing Ignite issue regarding serial creation

Hi @networkop
in case you have time would you be able to have a look at that PR?
For some reason, the cache that ignite consults with seems to be invalid as shown here - https://github.com/srl-labs/containerlab/issues/1039#issue-1388913471
What is even more funny is that it worked prior to 0.31.0, where in 0.31.0 we didn't have a sequential order of ignite containers start. It is reintroduced in this PR, but issues are still seen.

Done a little debugging:
(dlv) print strictErrs
[]error len: 2, cap: 2, [
        *errors.errorString {
                s: "unknown field \"spec\"",},
        *errors.errorString {
                s: "unknown field \"status\"",},
]

Those errors come from k8s.io's apimachinery. The issue is that ignite and libgitops are built against apimachinery v0.18 or smth and clab now depends on 0.25. So as you see from this diff, it seems like the decoder is now a lot stricter and bails out when it sees unexpected fields.
https://github.com/kubernetes/apimachinery/compare/v0.25.0..v0.22.0#diff-620d6f1202d998ffe5b21e700ec1599b12a7364ef2b705b5be8496f1233a9781L163-L187
TBH, I'm not sure what the right way forward from here is. I can raise this issue in ignite repo but it may require a substantial re-work and time investment, which I doubt weave are prepared to make. Also clab may be one of the few projects that uses ignite via API, not via CLI, so don't know if they will even be willing to entertain such idea.

I think there's an indirect dependency by other modules. e.g. github.com/hairyhenderson/gomplate/v3 depends on client-go  v0.25.2, which, in turn, depends on apimachinery 0.25.1

there are a few others like containerd

sadly, these things are pretty common for k8s.io packages, e.g. https://github.com/kubernetes/kubernetes/issues/88472

Ah, indeed. Well, then let me mark ignite support as "broken" for now in the docs and make it non default for cvx nodes in the next release. Then over time if ignite lives they will probably have a chance to fix it

Yep, probably worth mentioning that older version of clab would still work.

What do we do about this PR, which already handles the ignite nodes and creates dependencies that make them start one after the other?!
Do we close it for now? Or do we want to merge is, since we feel that this is only temporarely broken and will probably be fixed somewhen soon?

What do we do about this PR, which already handles the ignite nodes and creates dependencies that make them start one after the other?! Do we close it for now? Or do we want to merge is, since we feel that this is only temporarely broken and will probably be fixed somewhen soon?

Let's merge this, as the slight chance that this gets fixed upstream still exists =)

there's a bit of cleanup you can do before merging this. In deploy.go and clab.go remove serialNodes variable as it's no longer used.

@steiler in #1051 I have changed default runtime to docker for cvx nodes

I've removed the serialNodes, thanks for pointing that out @networkop
So I think this can be merged now.
I recognized that destroy also contains serialNodes. Question is, if we want to use DM there as well (we should open a new issue for that) or if we leave that part as is.

Done a little debugging:
(dlv) print strictErrs
[]error len: 2, cap: 2, [
        *errors.errorString {
                s: "unknown field \"spec\"",},
        *errors.errorString {
                s: "unknown field \"status\"",},
]

Those errors come from k8s.io's apimachinery. The issue is that ignite and libgitops are built against apimachinery v0.18 or smth and clab now depends on 0.25. So as you see from this diff, it seems like the decoder is now a lot stricter and bails out when it sees unexpected fields (search for func (s *Serializer) Decode) https://github.com/kubernetes/apimachinery/compare/v0.25.0..v0.22.0#diff-620d6f1202d998ffe5b21e700ec1599b12a7364ef2b705b5be8496f1233a9781L163-L187
TBH, I'm not sure what the right way forward from here is. I can raise this issue in ignite repo but it may require a substantial re-work and time investment, which I doubt weave are prepared to make. Also clab may be one of the few projects that uses ignite via API, not via CLI, so don't know if they will even be willing to entertain such idea.

The issue is, that the apimachinery functions are used, but the object handed into the decodeInto function is this
https://github.com/weaveworks/libgitops/blob/v0.0.2/pkg/runtime/meta.go#L16-L19
instead of the runtime.Object as defined in the apimachinery. And obviously the spec and status definitions are missing with this APIType struct.
Here it is created and handed over to the decodeInto function.
https://github.com/weaveworks/libgitops/blob/v0.0.2/pkg/storage/storage.go#L244-L257
Well nothing that will help much now, but the issue seems with weaveworks packages rather then apimachinery.

thanks @steiler , @networkop
I am merging this and hope ignite will get their assessment if this can be fixed


Bitvm bitcoin 0.32.5

Related to https://github.com/rust-bitcoin/rust-bitcoin/pull/3729.
Keeping this as a draft since I am planning to do PRs in more BitVM org crates to bump rust-bitcoin to 0.32.5 (latest).

I need to update in light of https://github.com/BitVM/rust-bitcoin-script/pull/4, https://github.com/BitVM/rust-bitcoin-scriptexec/pull/9, and https://github.com/BitVM/rust-bitcoin-script/pull/5.

This is good to go @lucidLuckylee


Bug: Steps 排序与 Github Jobs 网页顺序不一致

https://github.com/Byte-OS/polyhal/actions/runs/10975443878/workflow

修复后：


Add credits page

Add a credits page to the website, which automatically fetches names of contributors on this repository and displays their names and ids.

can you assign me?


No auth token in 3.3 rc3?

I noticed a change while trying the new RC3.
I didn't change the SPA that is using the login manager, but with the last version of Flask-Security-Too the login suddenly doesn't work anymore.
Not sure if I needed to change something on my backend?
https://travis-ci.com/acidjunk/improviser/jobs/239315478
New, commit sha: 71f409774f3666bc16c60c9bbab6db44c55437db
{
  "meta": {
    "code": 200
  },
  "response": {
    "csrf_token": "IjAzNTIyMTllY6FkMDM1MmRhZmUyZmZmNDU0NDM1OGY5NDYzNWVkODIi.XYxryQ.1Pt4cDMwujN6uUpDFoWN5Uty0UY",
    "user": {
      "id": "4af1f7f6-4781-4607-bf6c-f0388f7f4527"
    }
  }
}

Older response, sha: 560a401545006cf43b7047a16e944cf78ea75070
{
  "meta": {
    "code": 200
  },
  "response": {
    "csrf_token": "ImNmMjM4ODVkYjRlOTY0ODk4NzQ0MjNlOWE2OGE0NWJiZWVjM2M1NGMi.XYx3ow.lnThUkbuOz59ZhFF_BGFTSKPaGI",
    "user": {
      "authentication_token": "WyI0YWYxZjdmNS90NzgxLTQ2MDctYmY2Yy1mMDM4OGY3ZjQ1MjciLCIkNSRyb3VuZHM9NTM1MDAwJGIveHN2NjdyYjZrM1B3Zi4kdFkzTXpMMDBkcnVqd21ramxkb3JrYzNPNFBYNGJROEk1QW1Jdk5TT2RLMyJd.XYx3ow.s82HkXwm9_pIs_85-6H7eu6Qehg",
      "id": "4af1f7f6-4781-4607-bf6c-f0388f7f4527"
    }
  }
}

As noted in the CHANGES - the default behavior has changed - you must now either:

explicitly request the auth token (add ?include_auth_token) OR
set the SECURITY_BACKWARDS_COMPAT_AUTH_TOKEN=True

Always sending back the auth token is a security issue for those application that aren't using it (such as normal session based apps).

Thanks, fixed indeed. :)


Expose mentions verified property

refs https://github.com/TryGhost/Team/issues/2551 https://github.com/TryGhost/Team/issues/2549

exposed the verified property to the mentions browse endpoint.
updated the bookshelf repo.

closed by https://github.com/TryGhost/Ghost/commit/c6b90b6ac7c6490104b5b64cc6a7518680201007


implement the MkDir#45 and DeleteDir#44 interface.

Instead of using a slice to store child nodes in the DirTree structure, consider using a map. This change eliminates the need to traverse each layer when searching for a specific node. Additionally, by adding a nodeMap field to the DirTree structure, you can quickly locate a desired node, avoiding recursive search operations when performing deletions.
After performing a test by inserting 10,000 folders into the directory tree, I observed a significant improvement in performance when switching from a slice to a map. The execution time decreased from 20 seconds to just 250 milliseconds.

I apologize for the mistake in my previous response. Upon retesting with 100,000 folders, I found that using slice storage for nodes took more than 20 seconds. However, when utilizing a map, the storage time was significantly reduced to approximately 3 seconds.

The version I tested using map before only inserted 10,000 folders.


⚠ ClamAV has degraded performance

In 77281a2, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 212 ms

Resolved: ClamAV performance has improved in feb32ff after 5 minutes.


Fix grading editor not resetting on question change

Description
Fix the grading editor not resetting when clicking next/previous.
Bug introduced by https://github.com/source-academy/cadet-frontend/commit/802a24b8ccdda4c23fb270dacc72c314ca885b04. The grading editor has been fundamentally broken though, and only worked because of the bug that was fixed in that commit.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

How to test
Open the grading workspace and go between questions. See that the grading editor resets to show the comment of the question navigated to upon each navigation.
Checklist

[x] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build 7549

0 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 33.155%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/pages/academy/grading/subcomponents/GradingEditor.tsx
0
4
0.0%

Totals

Change from base Build 7547:
-0.03%

Covered Lines:
2293

Relevant Lines:
6409

💛  - Coveralls


default_factory's result doesn't get deepcopy'd - bug or feature?

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.5.1
            pydantic compiled: False
                 install path: /home/johnc/.virtualenvs/myproject/lib/python3.7/site-packages/pydantic
               python version: 3.7.5 (default, Apr 19 2020, 20:18:17)  [GCC 9.2.1 20191008]
                     platform: Linux-5.3.0-51-generic-x86_64-with-Ubuntu-19.10-eoan
     optional deps. installed: []

Currently the result of default_factory isn't deepcopy'd, is this a bug or a feature?
In my use case it's actually useful, since my factory is intentionally returning a singleton, but I'm wondering if it's safe to rely on this?
If it's intended to stay this way I can add a unit test to avoid regression?
Or is this something you'd rather not lock down?
The relevant lines:https://github.com/samuelcolvin/pydantic/blob/5067508eca6222b9315b1e38a30ddc975dee05e7/pydantic/fields.py#L274-L282
Example code:
from typing import Union

import pydantic

class Sentinel:
  pass

MY_SENTINEL = Sentinel()

class Foo(pydantic.BaseModel):
  myfield: Union[str, Sentinel] = pydantic.Field(default_factory=lambda : MY_SENTINEL)

  class Config:
    arbitrary_types_allowed = True

assert Foo().myfield is Foo().myfield

this is almost certainly intentional; having a customizable default_factory allows the user to provide unique copies if needed anyway

Hi @therefromhere!
It is indeed intentional ! This is the exact same behaviour as dataclasses from the standard library:
from dataclasses import dataclass, field
from typing import Union

class Sentinel:
  pass

MY_SENTINEL = Sentinel()

@dataclass
class Bar:
    myfield: Union[str, Sentinel] = field(default_factory=lambda: MY_SENTINEL)

assert Bar().myfield is Bar().myfield


Request for new feature

Request for drag and drop images into markdown docs.

VSCode Version:
OS Version:

Steps to Reproduce:

Reproduces without extensions: Yes/No

Duplicate of #19632


Add safe exposure of sqlite3_wal_hook

I'd like to propose adding support for the sqlite3_wal_hook in rusqlite, inspired by the existing commit_hook and rollback_hook etc. This would allow users to monitor Write-Ahead Logging (WAL) events via a safe Rust interface.
Proposed Changes:

Feature Flag:

Introduce a feature flag (e.g., "wal_hook" or added with the "hooks" feature ) to keep this functionality optional.

Safe Callback Interface:

Similar to commit_hook, provide a safe Rust closure interface for the WAL hook, ensuring it adheres to Rust's borrowing and ownership rules.
Avoid direct exposure of raw pointers, offering a safe abstraction instead.

You should be able to reuse the existing hooks feature because sqlite3_wal_hook was introduced before 3.14 (https://github.com/rusqlite/rusqlite/blob/95680270eca6f405fb51f5fbe6a214aac5fdce58/libsqlite3-sys/sqlite3/sqlite3ext.h#L233).

http://sqlite.org/c3ref/wal_hook.html

Note that the sqlite3_wal_autocheckpoint() interface and the wal_autocheckpoint pragma both invoke sqlite3_wal_hook() and will overwrite any prior sqlite3_wal_hook() settings.

So it seems not possible to use a closure / Fn but only a fn (like busy_handler).


Password only for write

when I use
 CONFIG SET requirepass mypass

the password is for read and write? exist a way to require password only for write?

Yes. This is for all commands. You must also call config rewrite to save the change.

thanks

thanks


[Core] Fix named imports across the entire codebase

Objective
Follow best Golang practices w.r.t named imports
Origin Document

Goals

Follow best practices in Go
Stay consistent w.r.t imports throughout the codebase

Deliverable

[ ] Identify and update all named imports in Go that are CamelCase and change them to snake_case

Non-goals / Non-deliverables

Any business logic changes

General issue deliverables

[ ] Update the appropriate CHANGELOG(s)
[ ] Update any relevant local/global README(s)
[ ] Update relevant source code tree explanations
[ ] Add or update any relevant or supporting mermaid diagrams

Testing Methodology

[ ] Task specific tests or benchmarks: make ...
[ ] New tests or benchmarks: make ...
[ ] All tests: make test_all
[ ] LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md
[ ] k8s LocalNet: verify a k8s LocalNet is still functioning correctly by following the instructions here

Creator: @Olshansk

@kutoft We discussed you trying out a core starter task issue to get "hands on" with the codebase. Wdyt of this one?

@kutoft Do you want to try and tackle this in the upcoming iteration?

tl;dr Goal is to make all named imports snake_case
(2) is what we DON'T WANT and (1) is what we DO WANT

If we do a regex search all camelCase imports (e.g. ^\s*([a-z]+(?:[A-Z][a-z]*)*)\s), we find the following:

If we do a regex search all snake_case imports (e.g. ^\s*([a-z]+_[a-z_]+)\s+"github\.com(.*?)"), we find the following:

@Olshansk Your message seems a little contradictory. So I just want to confirm which casing structure you want here, camelCase or snake_case.
Additionally, I was reading up on GO language patterns, and it appears the common practice is to name packages as all lowercase. Would you rather stick with this convention?
https://go.dev/blog/package-names

Response to the question is below but please hold off on implementation until further notice while our team reevaluated priorities.

Additionally, I was reading up on GO language patterns, and it appears the common practice is to name packages as all lowercase. Would you rather stick with this convention?

Yes. Attaching the GPT screenshot from our offline conversation for reference.

Tl;dr

Replace snake_case with lowercase
Replace PascalCase with lowercase
Replace camelCase with lowercast


RC Spot-Check Test: Vector Addition: Equations 1.1.0-rc.2

RC Spot-Check Test
Mentions: @arouinfar @KatieWoe @kathy-phet
Simulation links

github repository for issues <= Yes, this is vector-addition.
phet top-level directory
sim: all_phet.html

Test Matrices
General Test:

[x] Tester = NS , Platform = mac +safari, Time = .25
[x] Tester = KW, Platform = Win 11 Chrome, Time = .25

Features included

PhET-iO
Dynamic Locale
Alternative Input
UI Sound
Sonification
Description
Voicing

Focus and Special Instructions
This sim is the Equations screen from the Vector Addition sim, and was built from the identical code.   So please do https://github.com/phetsims/qa/issues/1168 first, and then you can do an RC-lite test on this sim.
Issues to Verify
It is sufficient to test these issues on 1 platform.
These issues have the "status:ready-for-review" label. Unless an issue says to close after verifying, assign the
issue back to the developer.

[x] https://github.com/phetsims/vector-addition/issues/287
[x] https://github.com/phetsims/vector-addition/issues/289
[x] https://github.com/phetsims/vector-addition/issues/284

For QA...

General features

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test some query parameters. (See QA Book for a
list of query parameters.)
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there
is a problem.
As the RC ends, notify the developer of any new QA credits that need to be added.

PhET-iO features

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
sure the simulation loads without crashing or throwing errors.
Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:/wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER

Further instructions in QA Book
Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other
random platform.
Conduct a memory test on the stand alone sim wrapper (rc.1).
Test one platform combination with ?phetioDebug=true on the Studio and State wrapper.
If Pan/Zoom is supported, make sure that it works when set with PhET-iO State.
Test that the sim works offline:

Click the link to the phet-io zip file (at top of issue) to download the zip file.
Unzip it to a spot locally.
Open index.html by double clicking it on your desktop or in a Finder-view.
It should look like the standalone version of the sim in PhET-iO brand.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please
assign to @terracoda and @emily-phet.

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
here. If you find a screen reader bug,
please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel
controls. Please test magnfication and make sure it is working as intended and well with the use cases of the
simulation. Due to the way screen readers handle user input, magnification is NOT expected to work while using a screen
reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

QA is done

Thanks QA! Onward to publishing 1.1.


[Feature request] Firefox ESR

Idea
Is there any chance you could provide Firefox ESR versions as well?
The reason for this request is that the normal Firefox version doesn't allow custom add-ons to be installed permanently. The debug option will remove the add-on on the next program start.
There is the option xpinstall.signatures.required in about:config that allows installing unsigned (custom/modified) add-ons permanently, but this setting is only used in the ESR, nightly and developer builds, but not in the normal release.
Sadly, there seems to be no docker hub project with either of those alternative versions.
Is there any chance you could add an ESR version branch to your project?

Thanks for the suggestion.  Yes, I can provide the ESR version!

Firefox ESR image is now available: https://hub.docker.com/r/jlesage/firefox-esr


How to Update Password

I have had to update the pasword for access to my Dahu system. Where is the password stored in the Dahua integration to allow me update it?

Same issue here - does someone knows ?

As the configuration is done in the UI you need to delete the entity and reconfigure. Its the same if you change the IP address see this forum post the integration needs to be updated to allow modification of the username / password / ip of the camera
I changed my camera's subnet and i had to delete them from ha and reconnect them.


Enable libbsd for test compilation and cleanup misc. warnings

Make changes in Makefile.am to pass BSD_OVERLAY_CFLAGS
through to test case compilations (excluding dispatch_c99
because header files are not c99 compliant).
Remove stubbed out functions/defines that are now provided
by libbsd.
Include string.h to in bsdtests.h for strrchr.

Thanks for the comment on #18; it helped us realize what the right approach to fixing it was.  (Hubertus and I sitting next to each other and hacking away today...).

lgtm


Hello. Thanks for your wonderful work. Question about detection model

Hello .Thanks for your wonderful work.
I noticed that you trained an additional object detection model  in SAM-det. Have you ever considered embed an detection head after the SAM's image encoder ? Because (1) we could use the information from SAM's image encoder instead of training an image encoder from scratch (2) save some computational resources.
Best regards,
Bizhe

It also works. SAM-seg is what you mean to some extent. But SAM-seg is an implement of instance detection. It can also be replaced with a detection head to perform as an absolute object detection method. In addition, your analysis is also very correct. We also discussed the resource consumption of SAM decoder in the discussion section. To some extent, replacing the head is also an effective alternative.

Hope that other researchers can investigate a foundation model similar to SAM by replacing the head and combining adapter technology.

Thank you!

I think it would like the architecture of  RSPromter-anchor

Yes! Thanks for your help .


timeline summary should include information about refresh rates.

The timeline summary should include refresh rate information.
The things to include should be:

The percentage of the frames running on 30hz.
The percentage of the frames running on 60hz.
The percentage of the frames running on 90hz.
The percentage of the frames running on 80hz.
The percentage of the frames running on 120hz.
The number of the frames running on an illegal refresh rate.

Since there would be rounding errors calculating refresh rates. We should consider add an error margin when determine refresh rate.
5Hz could be a value we try. (e.g. we consider a frame with 35hz as a valid 30hz frame)

There are some other lower refresh rate that iOS promotion display supports, see: https://developer.apple.com/documentation/quartzcore/optimizing_promotion_refresh_rates_for_iphone_13_pro_and_ipad_pro?language=objc
We should add them later.

Closing as https://github.com/flutter/flutter/pull/99854 has landed.


SwiftAudioPlayer without pods?

Your SwiftAudioPlayer is exactly what I need for a player of complex sound files. They are very large (>1GB) wav files, and streaming with AVPlayer or AVAudioPlayer don't cut it.
I am a novice in Swift but a programmer for many years. My problem is that I use a framework (Solar2d) and I cannot get the integration with pods to work. Someone in a forum wrote that it can work, but he forgot how he did it. Always
The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.
And then /Users/Shared/Mobile/SScapeN2/ios/SwSound.swift:10:8 No such module 'SwiftAudioPlayer'
I have tried everything I have seen on in other forums (updates, clean, etc), nothing fixes these. I do get a 'warning' that seems fixable, but I haven't figured it out. pod install says  "include the Target Support Files/Pods-SoundScape/Pods-SoundScape.release.xcconfig in your build configuration (CoronaApp.xcconfig)."
I was just wondering if it is possible to just add the SwiftAudioPlayer swift files into the project, make it simpler. But then, which files?
Sorry I am so ignorant in this, just running in circles.

The sync problem went away, but still several issues integrating Solar2d and pods, so bypassing pod would be helpful,


SSL Error

You could try fetching the URL that it is complaining about with curl and see if that shows the same SSL error.

I get this.


Some questions about Backdoor Bench

hello！
Recently，I found some issues when trying to reproduce the experiment in Revisiting Personalized Federated Learning: Robustness Against Backdoor Attacks.
The output is a complex number result, and the evaluator assesses the test_acc and poison_acc for each client. However, in the paper's charts, it appears that only one model was evaluated. Did you select specific clients or perform some kind of processing?
Thanks

@Alan-Qin zeyu, you can have a look when you are available.

Hi,
In our paper and experiments, we take the evaluation on all client and compute the average value of all client's clean acc and poisoning acc.
Could you please show all details about your issues?
Bests,
Zeyu


Use Traefik as router

Traefik is a very small, build for cloud, reverse proxy. If can handle docker backends out of the box.
Even Let's encrypt is build in.
https://traefik.io/

We aren't unhappy with our router solution. Are you? Lets Encrypt is not useful since we are not dealing with something that letsencrypt can work with (for Lets Encrypt you have to have a reachable site). Could you please say why you'd make this change, make a stronger case for it?

Mostly because it’s official, you just need to pass in a config (or parameters). It would reduce the code you need to maintain. In case of docker, it handles the routing with labels and don’t mess up the environment of the container. I’m very happy with it in local dev (not ddev) and on production.
The issue was for discussion and point you to Traefik if you don’t know it already.

Thanks, we are familiar with traefik, but ddev-router, which is a fork of https://github.com/jwilder/nginx-proxy, has served us well. It also is native to docker, listens to docker etc.
It's always wonderful to be pointed to something useful like this, and thanks for bringing it to our attention!


feat(guild): support for membership screening feature

Please describe the changes this PR makes and why it should be merged:

[x] Added pending property to the GuildMemberUpdatePayload interface. (79a6190)
[ ] Added Membership Screening endpoints.

Reference: https://github.com/discord/discord-api-docs/pull/2396
Closes #271
Status

[ ] Code changes have been tested against the Discord API, or there are no code changes

Semantic versioning classification:

[x] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Could you draft this PR? Also there are still types missing

Could you draft this PR? Also there are still types missing

1 more nice thing imo would be a special event like memberVerified or something like that which is run when a member completes this

1 more nice thing imo would be a special event like memberVerified or something like that which is run when a member completes this


72 feature implement vehicle controller

Description
Added a node that collects all data needed for the vehicle_control_cmd and sending it.
The node also designed to decide weather to use the stanley or pure pursuit controller, but at the moment only the stanley controller is used.
If the node receives an emergency msg, it will bring the vehicle to a stop and send an emergency msg with data = False back, after the velocity of the vehicle has reached 0.
Closes #72
Time invested
Julian: 10h
Type of change

New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)

Does this PR introduce a breaking change?
This PR deletes the acting node which was used in the minimal viable vehicle (#57). The acting node is replaced by the vehicle controller node.
Most important changes
Replacement of acting
Implementing emergency breaking
Test
You can see this node working by merging this branch with 69-feature-implement-pid-for-velocity-control and enabling the VelocityPublisherDummy in the launch file.
You can also manually send emergency msgs to trigger an emergency stop.
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 (might be obsolete with CI later on)
[x] New and existing unit tests pass locally with my changes (might be obsolete with CI later on)

I think this is a very good basis to build the controller upon. Mainly I think the handling of emergencies might need to be adjusted a little bit, apart from that it, I think it looks great. If you would like to handle emergencies in another way, could maybe explain your idea at the next meeting?
112 h by @schwalga

I would handle the emergencies the way I implemented it. Emergency = True triggers the emergency, emergency = False indicates the end of the emergency. What would you do differently?

TODO: add qos ledge

Github didn't recognize my rebase, so I had to change the base branch to sth other than main and back, as suggested here.


Publicize assertInlineSnapshot

The one caveat we've found to this API is that it breaks undo. I think we consider the advantages far outweigh this negative, though, and hopefully Xcode will get better undo support for writes that happen outside of Xcode in the future!

Let's revisit this in the future after SwiftSyntax.


JavaScript capstone project  API-based webapp

created webpack application
Used TVmaze API to fetch movies data
implemented likes functionality from an API
wrote tests to test for counter function and comments
implemented  ES6 syntax

You can also consider:

[ ] You did well pitching your project in the video and also showing some parts of the code which is great. However, I will suggest you get other members of your team to also present some features of your project. I didn't see any of them in the video. Please reach out to them and do the video together.

[ ] I noticed three contributors to this project. Was your group made up of 3 students?  If that's is true, you were supposed to work on the reservations pop part as well.

@mmsesay  we are two my partner has two GitHub accounts that's why it's showing three members  but we are only two

Good to know @Bria222. Please work on the other change.

@mmsesay the video right

@mmsesay Just like Brian say, it is only two...unfortunately, I have one separate GitHub account linked to the local repo which is different from my remote repo. I have tried solving this, but the issue persist. Apologise

@mmsesay thanks for the review we have fixed the issue and recorded a video

@CollinsTatang thanks for the feedback I have implemented the requested changes


Create Figma model for Teacher Dashboard

As the title states.

Link to the free model can be found here.

Done


npm run build errored

~/src/js/enoki-starterkit 🐈  git diff
diff --git a/content/projects/04-transatlantic-editions/project.txt b/content/projects/04-transatlantic-editions/project.txt
index 863e3e7..544fe58 100644
--- a/content/projects/04-transatlantic-editions/project.txt
+++ b/content/projects/04-transatlantic-editions/project.txt
@@ -1,10 +1,17 @@
 title: Masterpieces of Photography
+
 ----
+
 tags:
   - book
   - 1952
   - photography
   - ernst heiniger
   - composition
+
+
 ----
-text: New York City: Transatlantic Editions, 1952.
\ No newline at end of file
+
+text: New York City: Transatlantic Editions, 1952.
+
+hello
\ No newline at end of file
~/src/js/enoki-starterkit 🐈  node -v
v6.11.0

~/src/js/enoki-starterkit 🐈  npm run build

><EMAIL_ADDRESS>build /Users/max/src/js/enoki-starterkit
> enoki build -o public/ && browserify site/ -o public/bundle.js -t require-globify -t enoki/transform -t yo-yoify -t es2040

/Users/max/src/js/enoki-starterkit/node_modules/yargs/yargs.js:1079
      else throw err
           ^

TypeError: Object.values is not a function
    at copyFiles (/Users/max/src/js/enoki-starterkit/node_modules/enoki/bin/build.js:48:14)
    at route (/Users/max/src/js/enoki-starterkit/node_modules/enoki/bin/build.js:29:41)
    at Object.build [as handler] (/Users/max/src/js/enoki-starterkit/node_modules/enoki/bin/build.js:20:3)
    at Object.self.runCommand (/Users/max/src/js/enoki-starterkit/node_modules/yargs/lib/command.js:233:22)
    at Object.Yargs.self._parseArgs (/Users/max/src/js/enoki-starterkit/node_modules/yargs/yargs.js:990:30)
    at Object.get [as argv] (/Users/max/src/js/enoki-starterkit/node_modules/yargs/yargs.js:927:19)
    at Object.<anonymous> (/Users/max/src/js/enoki-starterkit/node_modules/enoki/bin/index.js:39:3)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)

Thanks @max, patched that one up real quick! Writing some testing is one of the big items on the more immediate list :)


504 (Outdated Optimize Dep) (vue.js, line 0) on Safari

Environment
npx nuxi info

Operating System: Darwin
Node Version:     v20.10.0
Nuxt Version:     3.8.2
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools
Runtime Modules:  -
Build Modules:    -

 "devDependencies": {
    "@nuxt/devtools": "latest",
    "nuxt": "^3.8.2",
    "vue": "^3.3.10",
    "vue-router": "^4.2.5"
  }

The browser is Safari 17.1.2
Reproduction
The issue is present with only the default scaffolding.
The following are exhaustive steps to reproduce the issue.
Note that this is most likely highly dependent on the environment.

npx nuxi@latest init <project-name>
cd <project-name>
yarn install
yarn dev
Visit the page and keep it open
control + c to shut down the server
yarn dev
Before the server has booted up, bring focus back to the website

Describe the bug
Expected behaviour:
There is a short wait while the server finishes booting up. Then everything works normally
Actual behaviour:
http://localhost:3000/_nuxt/node_modules/.cache/vite/client/deps/vue.js?v=b5b0d026 fails to load with the following error message in the console: "Failed to load resource: the server responded with a status of 504 (Outdated Optimize Dep)". As a result no client-side scripts work.
Additional context
I did not manage to reproduce the problem using the Vue SSR starter.
Tested solutions:

Disabling the browser cache & refreshing the page has no effect.
Deleting node_modules and doing a full reinstall has no effect.
Yarn complained that some packages were missing vite as a peer dependency, installing that does not resolve this issue.
Googling yielded few results

Some mention the solutions above
Running vite with --force, not applicable?
Adding the dependency ("vue") to vite.optimizeDeps.exclude does not solve this issue.

Disabling anti-tracking/ad-block plugins had no effect.

Two methods to temporarily clear the issue:

Method 1

Shut down the server
Refresh the page to bring up the Safari's "Safari cannot connect ..." page
Start the server
Refresh the page

Method 2

"Empty Buffers" in the Safari developer menu. and refresh the page

Logs
[Error] Failed to load resource: the server responded with a status of 504 (Outdated Optimize Dep) (vue.js, line 0)
[Debug] [vite] connecting... (client, line 229)
[Debug] [vite] connected. (client, line 324)

I have this error every time I restart the server.
For me it fixes when I reload page using Option+Command+R.

This is a Vite issue. It may be resolved in Vite 5 - would you try manually adding npm i vite@5 and seeing if that makes a difference? 🙏

This is a Vite issue. It may be resolved in Vite 5 - would you try manually adding npm i vite@5 and seeing if that makes a difference? 🙏

That fixed it for me!

This is a Vite issue. It may be resolved in Vite 5 - would you try manually adding npm i vite@5 and seeing if that makes a difference? 🙏

Unfortunately, no difference.

After updating to Nuxt 2.9 / Vite 5, I still had to perform a full reload once using Option + Command + R to resolve the issue.
On subsequent server restarts the issue no longer occured with the latest nuxt version.

nuxt3.9.0 problem still exists

@whcxxb Provide a reproduction then please ☺

@whcxxb Provide a reproduction then please ☺

Getting this in a completely fresh install, just as OP describes, using npx nuxi@latest init <project-name>, following exact steps explained to reproduce.
Error isn't present after running yarn dev for first time. But after restarting server and returning to page, error is perpetual.
Error only present in Safari (v 17.2.1). Chrome has no issue.
Tried reproducing in StackBlitz but there's currently a different issue with webcontainers and Safari compatibility, that's completely breaking Nuxt installs on their platform.

I still can't reproduce following those exact steps.
However, it seems likely that this is a vite issue. You could try removing node_modules/.cache to remove the vite cache.

I still can't reproduce following those exact steps.
However, it seems likely that this is a vite issue. You could try removing node_modules/.cache to remove the vite cache.

Try yarn dev --host. Still getting with a fresh install after updating Safari, but not with --host omitted. Also tried forcing Vite to v5

Hope we have tracking issue in Vite

I still can't reproduce following those exact steps.
However, it seems likely that this is a vite issue. You could try removing node_modules/.cache to remove the vite cache.

I still same problem, Is there not another option?


[BUG] HEATFS incorrect penetration readout/shell underperformance/improper jet spawning

Description:
HEATFS (only HEATFS, HEAT, and GLATGM perform fine) has incorrect penetration readout in the menu and on the crates on the dev branch after the menu update- its performance seems to have deteriorated from the pre-menu dev branch (105mm HEATFS can't penetrate 200mm), and the shaped charge seems to spawn behind the gun, leading to vehicles damaging themselves as well.
Reproducing:
Creating any HEATFS round with the new menu will yield interesting results for the round penetration, with the 105mm smoothbore readout easily reaching thousands of millimeters of penetration.
Using an existing vehicle with HEATFS or setting up a test stand with a prop directly behind a gun will lead to the jet spawning seemingly behind the gun after hitting a target, leading to its target and the prop behind it taking damage.
Screenshots/Videos:
105mm Smoothbore HEATFS:

140mm Smoothbore HEATFS:

HEAT/HEATFS performance demonstration:
https://youtu.be/ZZo-E4aQ4qo
Jet spawning behind breech demonstration:
https://youtu.be/q7sUPtbA020
https://youtu.be/QwsLoRS5j-w
Dupe file for test stand:
heat test_002.txt

HEATFS, and all other HEAT-based munitions since they all shared the affected bit of code, firing back and being unable to penetrate anything has been fixed on ac7b08b, it was a fault on the ballistic code that, for whatever reason, decided to send the projectile in the opposite direction.
HEATFS showing insane penetration values has been fixed on 464f2be and b72688a (my bad on the second one). It was faulty code from a moment when I decided to switch the bullet's calibers from centimeters to millimeters, which was eventually scrapped and reverted.


⚠ main has degraded performance

In ebd2e18, main ($MAIN_API_URL) experienced degraded performance:

HTTP code: 200
Response time: 26200 ms

Resolved: main performance has improved in 179c9f6.


fix: in memory html fails if it gets a future

Fixes / Enhancements
Currently the star wars example is broken when using flutter web, this fixes it.
I'm not able to get the star wars server running because the angle graphql server is trying to access the message of a typeerror. But I tested it with a javascript version. Don't know if it functions completely but at least it doesn't break as badly.

outdated by 4.0.0-beta.1 – please try there and if there's still an issue we'll go from there

This was for #717 I believe


Use fuzzing run setup to investigate data-node database size with different margin settings

Run the fuzzing run on a sufficiently long running market (at least 24h null-chain time and a good number orders / second on average) under two identical scenarios except:

margin scaling levels are (search, initial, release) = (1.050, 1.100, 1.150)
margin scaling levels are (search, initial, release) = (1.001, 2.000, 4.000).

The aim would be to run this, settle the markets, make sure that data node is caught up and then compare the size of the Postgres database in each case.

We should use the same price sequence (same random seed when generating) in both cases.


Add Typescript user-defined Type Guards

Right now I have some code that looks like this:
const b = {
    s: Term
    p: Term
    o: Term
}
if (
    b.s.termType != "NamedNode" &&
    b.s.termType != "BlankNode"
) {
    return
}
if (b.p.termType != "NamedNode") {
    return
}

if (
    b.p.termType != "NamedNode" ||
    b.p.termType != "BlankNode" ||
    b.p.termType != "Literal"
) {
    return
}
quad(b.s, b.p, b.o, defaultGraph)

It's getting pretty hairy and I doubt I'm doing everything correctly. DeMorgans laws!! It would be awesome if I could write things like:
if (!(isBlankNode(b.s) || isNamedNode(b.s))) {
    return
}

and have Typescript infer the proper type of b.s (BlankNode | NamedNode) in subsequent accesses.
See: https://www.typescriptlang.org/docs/handbook/advanced-types.html#user-defined-type-guards.
This repo might not be the right place to raise this issue as it's not written in TS, in which case I'll open an issue in @types.
See https://github.com/DefinitelyTyped/DefinitelyTyped/pull/29836 for more background.
I also wonder if there's a specific reason if this library isn't written directly in Typescript. No particular benefits come to mind, so I'd appreciate if someone could give some insight.
Thanks all for a nice RDF/JS ecosystem!

This implementation just covers the spec and the spec says:

We don't define any validation of given values (e.g. IRI, URI, CURIE).

The spec is not explicitly about your use case, but we had two reasons to add it:

Performance: If another part of your code does already the validation there is no need to check it again in the data model.
Flexibility: The RDF spec may set constraints on the data, but maybe there are some cases like intermediate data or algorithms, where you don't want to follow it very strictly.

The spec also says:

Implementations that apply validation should make this fact clear in their documentation.

So you are always free to wrap the data model and validation to it.

This repo might not be the right place to raise this issue as it's not written in TS, in which case I'll open an issue in @types.

Yes, for TS related stuff, that is the better place to discuss it. You could also check the RDF/JS Gitter channel.

I also wonder if there's a specific reason if this library isn't written directly in Typescript.

Being as close as possible to the spec (as far as I know TS still doesn't support WebIDL)
Every TS developer should know JS, but it's not the other way round, so using JS lowers the barrier and doesn't require additional tools

@alexkreidler Please close the issue, if I covered all of your questions and there are no follow up questions.


Uploading CS2030S latex file

Hi, any chance you could upload your latex file for the cs2030s finals? Thanks!

unfortunately I don't have a source tex file for cs2030s because it wasn't typeset using latex - sorry to disappoint!


Update incoming items area to track items being loaded from buffer and failed items

it doesnt work with foundation i was trying to request foundation from all the hub but nothing fill my inv . i was trying to request from 5 to fill but nothing happened

it doesnt work with foundation i was trying to request foundation from all the hub but nothing fill my inv . i was trying to request from 5 to fill but nothing happened

Are you talking about the version in this PR or latest from thunderstore? Can you show a screenshot of the item tooltip that pops up when you mouseover foundation?


How to connect firebase-admin to the firebase emulators?

There is a related issue (https://github.com/firebase/firebase-admin-node/issues/575) but it seems that it's still unresolved.
We would like to connect the admin SDK to firebase emulators when running tests. Our setup code looks like this:
import * as admin from 'firebase-admin'
admin.initializeApp({ credential: ... })
export default admin

Then in every file that needs access to firestore, we use:
import firebase from `./firebase`
firebase.firestore().doSomething()

How can we modify this setup so that is connects to the firebase emulators instead?
This is what we've tried so far:

Have the setup code return the @firebase/testing namespace depending on the node environment. However this library doesn't setup a default firebase app so calling firebase.firestore() fails.
Have firebase-admin connect to the emulators directly, by providing an explicit databaseURL and firestore URLs, and overriding credential.getAccessToken() to return owner. Now the issue is that the admin's implementation of firestore expects a service account and throws on the credentials override: https://github.com/firebase/firebase-admin-node/blob/master/src/firestore/firestore.ts#L95-L100
Return the firebase app as part of the setup code, so that app.firestore() always works. This requires refactoring the whole codebase to use an app instance instead of a firebase workspace.

Is there a recommended way to connect the admin sdk to emulators?

The Admin SDKs support the FIRESTORE_EMULATOR_HOST environment variable. You can simply set it to localhost:8080 to connect directly to the emulator.
Let us know if you have any other questions, but for now I hope you are unblocked.

For those in the future, please note this is an environment variable and not a parameter to the admin SDK.
To elaborate this, if you are running a NodeJS backend/script:
const useEmulator = true;

if (useEmulator){
    process.env['FIRESTORE_EMULATOR_HOST'] = 'localhost:8080';
}

admin.initializeApp({ ... });

This will set the environment variable from within code (not recommend for production environments), you can read more in this S.O Article for other ways of setting Environment Variables for NodeJS.
Do not try to do it this way:
admin.initializeApp({
    ...
    FIRESTORE_EMULATOR_HOST: 'localhost:8080'
});

It will have no effect locally, only remotely.

Side note, setting process.env['FIRESTORE_EMULATOR_HOST'] = 'localhost:8085'; only affects Firestore. Admin calls made to firebase auth WILL go to remote NOT emulator.
Also, if you don't know what port to set, check firebase.json & look for Firestore port there.

Yeah, I'm also looking for how to connect the auth utility of firebase-admin?

ℹ  If you're using Firebase Cloud Storage rather than Firestore, you may need to set FIREBASE_STORAGE_EMULATOR_HOST rather than FIRESTORE_EMULATOR_HOST.

I managed to get this working after a bit of debugging.  FIREBASE_AUTH_EMULATOR_HOST does work. You should not include the protocol part of the url (http/https)
e.g:  localhost:9099
not http://localhost:9099
export FIREBASE_AUTH_EMULATOR_HOST=localhost:9099

Can we connect to the emulator without relying on an environment variable? The reason why I ask is that I'd like to create 2 instances of the Firesbase Admin app: 1 for Cloud Firestore and 1 for Emulator Firestore so that I can copy data between the 2. For example:
const cloudAdmin = admin.initializeApp(
  {
    credential: admin.credential.cert(cloudServiceAccount),
  },
  'app-name-1',
);

const cloudFirestore = cloudAdmin.firestore();

const emulatorAdmin = admin.initializeApp(
  {
    // Connect to Emulator?
  },
  'app-name-2',
);

const emulatorFirestore = emulatorAdmin.firestore();

(async function () {
  // Copy data from Cloud Firestore to Emulator Firestore
  const data = await cloudFirestore
    .doc('widgets/1')
    .get();

  await emulatorFirestore
    .doc('widgets/1')
    .set(data.data());
})();

The only way I can connect to both the emulator and cloud Firestore in the same script is to use @firebase/testing for the emulator connection and firebase-admin for the cloud connection.
const firebaseAdmin = require('firebase-admin');
const testAdmin = require('@firebase/testing');

const cloudFirestore = firebaseAdmin.initializeApp(
  {
    credential: admin.credential.cert(cloudServiceAccount),
  },
  'app-name-1',
).firestore();

const emulatorFirestore = testAdmin
  .initializeAdminApp({ projectId: 'demo-project' })
  .firestore();

For anyone else who wants to connect to both the emulator and cloud Firestore at the same time, you can do this. It turns out that  process.env.FIREBASE_AUTH_EMULATOR_HOST and process.env.FIRESTORE_EMULATOR_HOST are only referenced when initializing the app.
const admin = require('firebase-admin');

// Cloud Firestore
const cloudAdmin = admin.initializeApp(
  { projectId: 'my-cloud-project-id' },
  'cloud-app',
);
const cloudDb = cloudAdmin.firestore();

// Emulator
process.env.FIREBASE_AUTH_EMULATOR_HOST = 'localhost:9099';
process.env.FIRESTORE_EMULATOR_HOST = 'localhost:8080';
const emulatorAdmin = admin.initializeApp(
  {
    projectId: 'demo-project',
  },
  'emulator-app',
);
const emulatorDb = emulatorAdmin.firestore();

(async () => {
  const cloudDoc = await cloudDb.doc('/documents/one').get();
  const emuCourse = await emulatorDb.doc('/documents/two').get();

  console.log('cloudDoc', cloudDoc.data());
  console.log('emuCourse', emuCourse.data());
})();

Where are all those variables documented ?
FIREBASE_AUTH_EMULATOR_HOST,  FIRESTORE_EMULATOR_HOST
for app check and so fort ?

@cedvdb they are documented in both GCP and Firestore docs. I've personally found GCP docs to be more technical, while the Firestore docs are more often what you are looking for/will use. Below I linked to the Firestore docs.

FIREBASE_AUTH_EMULATOR_HOST

FIRESTORE_EMULATOR_HOST

These are both sub-sections of the larger documentation for the entire Emulator Suite, I recommend reading everything in the section to strengthen your understanding of the whole Emulators Suite - even when you are confident with the technology, since the docs are often updated with new features.

Firestore Emulators Suite

The solution posted by @johnnyoshika (for using both an emulated admin SDK and a non-emulated SDK at the same time) does not work for Firebase Auth, because the admin SDK for auth does not only reference the env var when initializing the app. (And you'll notice they only show Firestore in their example code)
For example, the AuthResourceUrlBuilder calls useEmulator(), which checks FIREBASE_AUTH_EMULATOR_HOST. It does this on almost any SDK method.

this worked for me for  BOTH auth and firestore!:

// firebaseAdmin.js

import * as admin from 'firebase-admin';

if (!admin.apps.length) {
  // Connect to Firestore emulator if in development environment
  if (process.env.NODE_ENV === 'development' || process.env.NODE_ENV === 'test') {
    //for firestore
    process.env['FIRESTORE_EMULATOR_HOST'] = '<IP_ADDRESS>:1956';
    //for auth
    process.env['FIREBASE_AUTH_EMULATOR_HOST'] =  '<IP_ADDRESS>:9099';
    }

    admin.initializeApp({
        credential: admin.credential.cert({
            projectId: process.env.FIREBASE_PROJECT_ID,
            clientEmail: process.env.FIREBASE_CLIENT_EMAIL,
            privateKey: process.env.FIREBASE_PRIVATE_KEY.replace(/\\n/g, '\n'),
        }),
        databaseURL: process.env.FIREBASE_DATABASE_URL,
    });
}

export default admin;

This emulator should be its own npm package - having to add a global package just to test database is not ideal.

How can I verify that the emulator is actually being used?
I am sending a JWT token from my web client (it's using the Firebase Auth Emulator) to my backend.
However, whily calling verifyIdToken(), I am getting the following error:
{
  errorInfo: {
    code: 'auth/invalid-credential',
    message: 'Must initialize app with a cert credential or set your Firebase project ID as the GOOGLE_CLOUD_PROJECT environment variable to call verifyIdToken().'
  },
  codePrefix: 'auth'
}

Does this imply, that firebase-admin is not using the emulator?
I am running the server with
FIREBASE_AUTH_EMULATOR_HOST=<IP_ADDRESS>:9099
FIRESTORE_EMULATOR_HOST=<IP_ADDRESS>:9199


Feature request: enable toggle input

Could it be possible to implement a feature that toggles the "input broadcasting" on (⌘⇧I) in all panes when creating a new session?

If you create a script like this, and save it as something link broadcast.scpt:
tell application "iTerm"
	tell application "System Events" to keystroke "i" using {command down, shift down}
end tell

Then you can just run osascript broadcast.scpt as a command in one of the panes you open and it would do exactly what you are looking for.
Let me know!


feat(client) toip returns the last hostname resolved

client.toip() gets a new return value that will hold the last name resolved in a chain of records.

Closing this due to lack of activity. Please re-open if needed.