[QUESTION] How to send raw audio to kvssink?

Hi,
We are trying to publish raw audio from a USB microphone as part of our kvssink pipeline.
We've confirmed we're able to successfully source this raw audio over alsasrc and pulsesrc and send it to autoaudiosink (via tcpsink) and hear the microphone's captured audio on another computer on the network.
However, we get an assertion error on GST_AUDIO_FORMAT_UNKNOWN when we change our sink to kvssink.
Here is the command (also includes video):
gst-launch-1.0 v4l2src device=/dev/video2 ! video/x-h264,width=1280,height=720,framerate=30/1 ! h264parse ! kvssink name=sink stream-name="REDACTED" access-key="REDACTED" secret-key="REDACTED" aws-region="us-west-2" storage-size=100 pulsesrc device=alsa_input.usb-Generic_INSIGNIA_USB_MIC_Device_IM10000002-00.analog-stereo ! 'audio/x-alaw,channels=2,rate=44100' ! sink.
Below, I've included output from this command, along with output of  gst-device-monitor for the mic as well as from arecord when we record outside of GStreamer.
Any help is much appreciated!

Setting pipeline to PAUSED ...
log4cplus:ERROR could not open file ../kvs_log_configuration
INFO - createKinesisVideoClient(): Creating Kinesis Video Client
2022-09-15 19:21:41 [3070042736] INFO - heapInitialize(): Initializing native heap with limit size 104857600, spill ratio 0% and flags 0x00000001
2022-09-15 19:21:41 [3070042736] INFO - heapInitialize(): Creating AIV heap.
2022-09-15 19:21:41 [3070042736] INFO - heapInitialize(): Heap is initialized OK
2022-09-15 19:21:41 [3070042736] DEBUG - getSecurityTokenHandler invoked
2022-09-15 19:21:41 [3070042736] DEBUG - Refreshing credentials. Force refreshing: 0 Now time is:<PHONE_NUMBER>167088653 Expiration: 0
2022-09-15 19:21:41 [3070042736] INFO - createDeviceResultEvent(): Create device result event.
2022-09-15 19:21:41 [3070042736] DEBUG - clientReadyHandler invoked
2022-09-15 19:21:41 [3070042736] INFO - try creating stream
2022-09-15 19:21:41 [3070042736] INFO - Creating Kinesis Video Stream REDACTED
2022-09-15 19:21:41 [3070042736] INFO - createKinesisVideoStream(): Creating Kinesis Video Stream.
2022-09-15 19:21:41 [3070042736] INFO - logStreamInfo(): SDK version: 70f74f14cf27b09f71dc1889f36eb6e04cdd90a8
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Kinesis Video Stream Info
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Stream name: oclea-demo
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Streaming type: STREAMING_TYPE_REALTIME
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Content type: video/h264,audio/alaw
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Max latency (100ns): 600000000
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Fragment duration (100ns): 20000000
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Key frame fragmentation: Yes
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Use frame timecode: Yes
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Absolute frame timecode: Yes
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Nal adaptation flags: 0
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Average bandwith (bps): 4194304
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Framerate: 100
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Buffer duration (100ns):<PHONE_NUMBER>
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Replay duration (100ns): 400000000
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Connection Staleness duration (100ns): 600000000
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Store Pressure Policy: 1
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): View Overflow Policy: 1
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Segment UUID: NULL
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Frame ordering mode: 5
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Track list
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Track id: 1
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Track name: kinesis_video
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Codec id: V_MPEG4/ISO/AVC
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Track type: TRACK_INFO_TYPE_VIDEO
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Track cpd: NULL
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Track id: 2
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Track name: audio
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Codec id: A_MS/ACM
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Track type: TRACK_INFO_TYPE_AUDIO
2022-09-15 19:21:41 [3070042736] DEBUG - logStreamInfo(): Track cpd: NULL
2022-09-15 19:21:41 [3070042736] INFO - writeHeaderCallback(): RequestId: 86b15eaa-929c-4b3d-a3be-15fa18da8624
2022-09-15 19:21:41 [2927518816] DEBUG - describeStreamCurlHandler(): DescribeStream API response: {"StreamInfo":{"CreationTime":1.647642558129E9,"DataRetentionInHours":24,"DeviceName":null,"IngestionChannelARN":null,"IngestionConfiguration":null,"KmsKeyId":"arn:aws:kms:us-west-2:553910552099:alias/aws/kinesisvideo","MediaType":null,"Status":"ACTIVE","StreamARN":"REDACTED","StreamName":"oclea-demo","Version":"X70WXCuvQKFcQNM3uYjC"}}
2022-09-15 19:21:41 [2927518816] INFO - describeStreamResultEvent(): Describe stream result event.
2022-09-15 19:21:41 [2927518816] WARN - describeStreamResult(): Retention period returned from the DescribeStream call doesn't match the one specified in the StreamInfo
2022-09-15 19:21:41 [2927518816] WARN - describeStreamResult(): Content type returned from the DescribeStream call doesn't match the one specified in the StreamInfo
2022-09-15 19:21:41 [2927518816] INFO - writeHeaderCallback(): RequestId: 12b0b3f6-2f69-4629-b344-86747b237b61
2022-09-15 19:21:41 [2917135456] DEBUG - getStreamingEndpointCurlHandler(): GetStreamingEndpoint API response: {"DataEndpoint":"REDACTED"}
2022-09-15 19:21:41 [2917135456] INFO - getStreamingEndpointResultEvent(): Get streaming endpoint result event.
2022-09-15 19:21:41 [2917135456] DEBUG - getStreamingTokenHandler invoked
2022-09-15 19:21:41 [2917135456] DEBUG - Refreshing credentials. Force refreshing: 1 Now time is:<PHONE_NUMBER>779941563 Expiration:<PHONE_NUMBER>3709551615
2022-09-15 19:21:41 [2917135456] INFO - getStreamingTokenResultEvent(): Get streaming token result event.
2022-09-15 19:21:41 [2917135456] DEBUG - streamReadyHandler invoked
2022-09-15 19:21:41 [2917135456] Stream is ready
Pipeline is live and does not need PREROLL ...

(gst-launch-1.0:1961): GStreamer-CRITICAL **: 19:21:41.811: gst_structure_fixate_field_string: assertion 'gst_structure_has_field (structure, field_name)' failed

** (gst-launch-1.0:1961): CRITICAL **: 19:21:41.819: gst_audio_info_to_caps: assertion 'info->finfo->format != GST_AUDIO_FORMAT_UNKNOWN' failed

(gst-launch-1.0:1961): GStreamer-CRITICAL **: 19:21:41.822: gst_caps_get_structure: assertion 'GST_IS_CAPS (caps)' failed
Setting pipeline to PLAYING ...

(gst-launch-1.0:1961): GStreamer-CRITICAL **: 19:21:41.824: gst_structure_get_name: assertion 'structure != NULL' failed
Caught SIGSEGV

$ gst-device-monitor-1.0

name  : INSIGNIA USB MIC Device Analog Stereo
	class : Audio/Source
	caps  : audio/x-raw, format=(string){ S16LE, S16BE, F32LE, F32BE, S32LE, S32BE, S24LE, S24BE, S24_32LE, S24_32BE, U8 }, layout=(string)interleaved, rate=(int)[ 1,<PHONE_NUMBER> ], channels=(int)[ 1, 32 ];
	        audio/x-alaw, rate=(int)[ 1,<PHONE_NUMBER> ], channels=(int)[ 1, 32 ];
	        audio/x-mulaw, rate=(int)[ 1,<PHONE_NUMBER> ], channels=(int)[ 1, 32 ];
	properties:
		alsa.resolution_bits = 16
		device.api = alsa
		device.class = sound
		alsa.class = generic
		alsa.subclass = generic-mix
		alsa.name = "USB\ Audio"
		alsa.id = "USB\ Audio"
		alsa.subdevice = 0
		alsa.subdevice_name = "subdevice\ \#0"
		alsa.device = 0
		alsa.card = 1
		alsa.card_name = "INSIGNIA\ USB\ MIC\ Device"
		alsa.long_card_name = "Generic\ INSIGNIA\ USB\ MIC\ Device\ at\ usb-musb-hdrc.1-1.1\,\ full\ speed"
		alsa.driver_name = snd_usb_audio
		device.bus_path = platform-musb-hdrc.1-usb-0:1.1:1.0
		sysfs.path = /devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1/usb1/1-1/1-1.1/1-1.1:1.0/sound/card1
		udev.id = usb-Generic_INSIGNIA_USB_MIC_Device_IM10000002-00
		device.bus = usb
		device.vendor.id = 2034
		device.vendor.name = Generic
		device.product.id = 0105
		device.product.name = "INSIGNIA\ USB\ MIC\ Device"
		device.serial = Generic_INSIGNIA_USB_MIC_Device_IM10000002
		device.string = front:1
		device.buffering.buffer_size = 352800
		device.buffering.fragment_size = 176400
		device.access_mode = mmap+timer
		device.profile.name = analog-stereo
		device.profile.description = "Analog\ Stereo"
		device.description = "INSIGNIA\ USB\ MIC\ Device\ Analog\ Stereo"
		alsa.mixer_name = "USB\ Mixer"
		alsa.components = USB2034:0105
		module-udev-detect.discovered = 1
		device.icon_name = audio-card-usb
	gst-launch-1.0 pulsesrc device=alsa_input.usb-Generic_INSIGNIA_USB_MIC_Device_IM10000002-00.analog-stereo ! ...

$ arecord -f cd -r 44100 -D hw:CARD=Device  test.wav -v
Recording WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Hardware PCM card 1 'INSIGNIA USB MIC Device' device 0 subdevice 0
Its setup is:
  stream       : CAPTURE
  access       : RW_INTERLEAVED
  format       : S16_LE
  subformat    : STD
  channels     : 2
  rate         : 44100
  exact rate   : 44100 (44100/1)
  msbits       : 16
  buffer_size  : 22050
  period_size  : 5513
  period_time  : 125011
  tstamp_mode  : NONE
  tstamp_type  : MONOTONIC
  period_step  : 1
  avail_min    : 5513
  period_event : 0
  start_threshold  : 1
  stop_threshold   : 22050
  silence_threshold: 0
  silence_size : 0
  boundary     :<PHONE_NUMBER>
  appl_ptr     : 0
  hw_ptr       : 0

@mikewadhera ,
Your pipeline seems fine. But, can you try adding audioconvert before audio/x-alaw to see what happens? Can you also attach logs in a file with GST_DEBUG=5"? Would like to see what GST api is actually causing the error.

Thanks!
Below is the output of the original command with GST_DEBUG=5 so you can see the error closer.
alaw_log_no_secret_no_access.txt
Also, if we add audioconvert before audio/x-alaw we get:
WARNING: erroneous pipeline: could not link audioconvert0 to sink, audioconvert0 can't handle caps audio/x-alaw, channels=(int)2, rate=(int)44100

@mikewadhera indeed this is expected, if you use gst-inspect-1.0 kvssink you'll find what kvssink accepts.  Today it does not accept audio/x-raw, here is what is accepted:
https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-cpp/blob/master/src/gstreamer/gstkvssink.cpp#L189-L193
audioconvert will actually not give you this hence the error you see is telling you exact that, audioconvert cannot handle caps audio/x-alaw.  If you look at the sink/src pads (https://gstreamer.freedesktop.org/documentation/audioconvert/index.html?gi-language=c) it only gives audio/x-raw.  Ok so if you need to convert this to try it out just use alawenc for example:  https://gstreamer.freedesktop.org/documentation/alaw/alawenc.html?gi-language=c#alawenc
If you you look at the src pad of audioconvert you'll find it can do audio/x-raw with S16LE which is alaw.  You do not need to specify a capsfilter.  After your audio source you just need audioconvert ! alawenc ! sink and that should work.  alawenc doesn't support 44100 rate the options are 8000 and 192000 so you'll have to pick one of them just to try it out.


How to set up the browser automatically when the installation is complete

How to set up the browser automatically when the installation is complete

The hooks command "start http://www.baidu.com" can't be installed.

Have you tried something like cmd /c start /b http://baidu.com?

thanks ,it's worked


Close Compass subscriptions when IPad goes to sleep

Describe the bug
Compass subscriptions remain open after IPad screen goes to sleep which may result from excessive battery drain.
Expected behavior
When the AppState is 'inactive' the subscription listener stops and then can restart when AppState is 'active'
https://reactnative.dev/docs/appstate
Could also help solve issue #193

fixed with commit e65d41b82adb1ba4e502884839d7c7461d148153

fixed with commit e65d41b82adb1ba4e502884839d7c7461d148153


Intake Take2 is about to release

Please consider pinning intake<2 to keep this package working, if it breaks with the new code.

It should be possible to port existing users to intake.readers.catalogs.THREDDSCatalogReader

Any plan to make this intake-thredds compatible with the newer intake 2?
If we want intake-xarray 2, we need intake 2, but then this intake-thredds is not compatible with intake 2.

Good point - I'll look into it. Intake 2 does have a THREDDSCatalogReader internally, so it should not be much work (hopes).


Allow session_path to be configured with wildcards (e.g. ~/projects/project-* or ~/projects/*)

What would you like sesh to do?
I would like session_path to allow wildcards so I can use the same script_path for similar projects.
I have several projects where I typically like to open a few windows (code, server, tests, zsh). What I do now, is define a startup script per project pointing to the same script_path.
[[startup_scripts]]
script_path = "~/.config/sesh/scripts/project"
session_path = "~/projects/project-1"

[[startup_scripts]]
script_path = "~/.config/sesh/scripts/project"
session_path = "~/projects/project-2"

With a wildcard this could be reduced to something like this:
[[startup_scripts]]
script_path = "~/.config/sesh/scripts/project"
session_path = "~/projects/project-*"

Or something like this?
[[startup_scripts]]
script_path = "~/.config/sesh/scripts/project"
session_path = "~/projects/*"

Apologies if this is already possible and I missed something in the docs.
For reference, this is what my startup script contains:
#!/usr/bin/env bash
# vi: ft=sh

tmux rename-window "code"
tmux new-window -n "server"
tmux new-window -n "tests"
tmux new-window
tmux select-window -t 1
nvim -c "Telescope find_files"

Great idea! It was a quick update, download v0.15.0 and let me know how it works for you.

Awesome, works exactly as advertised. I wasn't sure if foo* would also match just foo but it does.
E.g. I have these projects:
~/projects/project
~/projects/project-foo

Both are matched nicely with the config below:
[[startup_scripts]]
script_path = "~/.config/sesh/scripts/project"
session_path = "~/projects/project*"

Cheers for the change!


gh-pages branches

Now, we can configure an arbitrary branch for gh-pages (part of the slow process of renaming default branch...)
should we rename "master" to "gh-pages", and "source" to "master", and set gh-pages as the branch to publish?  Would that work?

Yes, good idea. I will do that. (main instead of master since that's the new default on GH).

Done. Seems to work.


Remove more deprecations

Takes out the deprecation in getComponents, and removes some old deprecated docs

Lots of red. I like it!


Blog: OT Democratization Journey

Checklist

[ ] tile
[ ] East West vs North South Graphic

[ ] I have read the contribution guidelines
[ ] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

@Yndira-E Do you know if it okay if I used this image or will we need to recreate it?
https://www.ciscopress.com/articles/article.asp?p=3004581&seqNum=2

@gdziuba

@Yndira-E Do you know if it okay if I used this image or will we need to recreate it?

I've just updated the image 😉


Portable application executable is renamed despite absence of rename argument

Brief description of your issue
The Portable/Standalone applications documentation states:

If a command value is specified in the manifest, then the symlink filename will be renamed to match the command value. If the rename argument is provided, then both the symlink filename and the portable exe filename will be renamed to match the rename argument value.

However, the portable exe is renamed even if the rename argument is absent.
In case the behavior is intended and only the documentation is misleading, I still request changing this behavior. Renaming the exe is confusing and seems unnecessary.
Steps to reproduce
Run winget install --exact --id Microsoft.Sysinternals.ProcessExplorer --version 17.05
Note that the manifest includes:
Commands:
- process-explorer

Expected behavior
C:\Users\<username>\AppData\Local\Microsoft\WinGet\Links contains symlink process-explorer.exe.
C:\Users\<username>\AppData\Local\Microsoft\WinGet\Packages\Microsoft.Sysinternals.ProcessExplorer_Microsoft.Winget.Source_8wekyb3d8bbwe\ contains procexp64.exe.
Actual behavior
C:\Users\<username>\AppData\Local\Microsoft\WinGet\Links contains symlink process-explorer.exe.
C:\Users\<username>\AppData\Local\Microsoft\WinGet\Packages\Microsoft.Sysinternals.ProcessExplorer_Microsoft.Winget.Source_8wekyb3d8bbwe\ contains process-explorer.exe.
Environment
Windows-Paket-Manager v1.6.3482
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

Windows: Windows.Desktop v10.0.19045.3803
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.21.3482.0

Related to https://github.com/microsoft/winget-cli/issues/3437


chg: [template] conditionally list IR phases in RP body

Empty phases should not be included in the markdown RP.

Hello @VVX7 !
Looks great. The only things that is left is the list of stages for AMITT here:
https://github.com/atc-project/atomic-threat-coverage/blob/c492c501daa5d420a330683a168f258b4eb8e408/scripts/responseplaybook.py#L191-L195
The same way you did it here:
https://github.com/atc-project/atomic-threat-coverage/blob/c492c501daa5d420a330683a168f258b4eb8e408/scripts/responseplaybook.py#L98-L109
Yes, it's kinda repeating the code... But we will optimise it in ATC API, that we will release RealSoon™ (: So it's some sort of temporary solution.
PS
You actually can modify amitt branch of ATC Project, we've provided you with the permissions (:

You actually can modify amitt branch of ATC Project, we've provided you with the permissions (:
Thanks.  I've changed the phases in each part of esponseplaybook.py where it's required.


ImportError: DLL load failed: The specified procedure could not be found.  Import win32api

import win32api
ImportError: DLL load failed: The specified procedure could not be found.
It throws the exception , Exception: pywin32 library required. but i already installed pywin32, pip install pywin32, it satisfies the error but still giving me above error.


Add get framework route

This is required for a lot of the DOS pages.

But I liked biscuits-for-gov...
:+1:

@TheDoubleK ok then


Update bootstrap to v5.3.1

https://github.com/twbs/bootstrap/releases/tag/v5.3.1
Related to: https://github.com/test-network-function/cnf-certification-test/pull/1284

Let's merge #2 first.


Feature/cypress 3.8

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Exam mode: Validate that exam exercises do not have dates

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server

Server

[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I implemented the changes with a good performance and prevented too many database calls.
[ ] I documented the Java code using JavaDoc style.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context

Description

Steps for Testing

1 Editor or higher
The bugfix is validated by introduced tests, only adaptions for the Resource should be tested
Create and Update a Modeling Exercise, first in a Course, then in an Exam
Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Test Coverage

Screenshots

I integrated the changes in the other branch that handled the same issue, therefore we close this PR.


Draft contribution guidelines for platform-app repo

As discussed in today's sprint catch-up meeting, it would be a good idea to have a set of contribution guidelines for the platform-app repo.

@javfg as you did such a great job with the documentation for the table component, could you start drafting contribution guidelines for the platform-app repo?
Topics could include:

Do PRs need to be connected to an issue?
Opening up a PR and tagging me or David O.
When merging a PR, do we squash commits or keep the history?

Indeed, this is in my to-do list. I'll open a discussion about it everyone involved to get you input!

New docs are up: https://github.com/opentargets/platform-app/tree/jf-docs
@andrewhercules @d0choa can you take a look and see if I missed something? Thanks!
PS: We now have a working badge! :D

Looks good in my opinion. We need @mkarmona view on this as well

@andrewhercules up to you to close this ticket

@andrewhercules up to you to close this ticket

Guidelines reviewed and will be included in our release comms plan

Guidelines reviewed and will be included in our release comms plan


Release workflow failed

I found the release workflow was failed

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of URL. Received undefined

https://github.com/unocss/unocss/blob/cb61f2a6326133c96ff364a64c03a7833f114fed/packages/vscode/scripts/publish.ts#L7
I have debugged locally, maybe import.meta.url was the wrong reason.

Now, Interactive(0.33.1) 、Playground(0.33.1) and Vscode extension(0.33.2) version is different from the latest veison.
Please update it to be consistent.
p.s.
I personally use playground a lot, but now, there is no drak mode in it. It's so terriable. hhhh😂

Nuxt was broken so I locked to previous version for the site before I can take time to loolk into it.


Product Definition

What exactly goes into a product

We are starting with this basic definition:
{
    "retailer_item_number": 3945,
    "name": "kingston 64GB FLASDRIVE",
    "description": null,
    "size": null,
    "price": 180.0,
    "UPC":<PHONE_NUMBER>51.0,
    "item_type": "Inventory",
    "main_category": "Storage",
    "manufacturer": null,
    "weight": 0,
    "quantity": 0
  }

We will update the category to a category + sub category like this:
{ main_category: "computers", sub_category: "storage" }

Then

size value
size unit
retailer reference


Add getValue to index.d.ts

adds getValue declaration to index.d.ts otherwise TS app which tries to import complains that the getValue export does not exist

@jeswanke build is failing on unrelated change, same fail as https://github.com/open-cluster-management/temptifly/pull/130

did this in my pr


GDScript 2.0: Lambda capturing issues with default parameter values

Godot version
4.0.dev (99b46a261)
System information
5.15.12-1-MANJARO
Issue description
Lambdas seem to fail capturing locals that are used in parameter defaults:
func _ready():
	var x = "local"
	var lambda = func(param=x): print(param)
	lambda.call()

Parse Error: Identifier "x" not declared in the current scope.

But magically, if we simply add a member with the same identifier, it works (and correctly uses the local):
var x = "member" # having this lets it compile
func _ready():
	var x = "local" # this is the one that gets used (as expected)
	var lambda = func(param=x): print(param)
	lambda.call()

local

Very messed up case:
var x = "member" # this is still required
func _ready():
	#var x = "local" # does not affect anything
	var lambda = func(x=x): print(x)
	lambda.call()

null

Steps to reproduce
Reproducible code in the description above.
Minimal reproduction project
No response

Very messed up case:
var x = "member" # this is still required
func _ready():
	#var x = "local" # does not affect anything
	var lambda = func(x=x): print(x)
	lambda.call()

null

This is actually a general issue with default parameters, not only with lambdas. The problem is that the default value is gathered later so it uses the local value instead (which is empty), since it's in a closer scope. If you try to do func any(x=x) you'll get a parser error if x isn't previously declared (note that func any(a, b=a) is valid and works as intended).
For the first issue I'm about to post a fix.


vagrant-completion 1.7.3

Update since there's new completion functionality in this version.
https://github.com/mitchellh/vagrant/commits/364db17e3d87c766e696f088d6aeb9e5d9cb330c/contrib/bash/completion.sh
Also provided a sha256 hash to the new formula.

Sorry for the delay, could you please rebase your branch on top of master?

@bfontaine This can be closed. It was already updated to 1.7.4.

Right, thank you @vitorgalvao!


feat(AlgebraicGeometry/ProjectiveSpectrum/Scheme): calculate stalk of toSpec map

In this PR, we show the newly defined map of locally ringed spacetoSpec agree with the ProjIsoSpecTopComponent.toSpec and calculate the stalk map.
Co-authored-by: Andrew Yang<EMAIL_ADDRESS>

Thanks!
LGTM but I did a significant portion of these so I'll wait for someone else to review.

Thanks!
bors d+

bors r+


Ported Primer and Lang Guide to mkdocs

I had this sitting in my computer for some time :)

While having a wiki is great in my opinion some documentation is better served by having it sit besides the actual project source code. This makes it trivial to keep it versioned and simplifies updating it when implementing new features.
The idea then is to have the more official documentation as part of the repository, reviewed and improved via pull requests, while the Wiki would remain a place for user generated and frequently changed contents (ie: Faq, usage examples, links, ...).
This PR uses mkdocs to generate the Primer and Language Guide contents (copied from the wiki) as a static site with search support, which can be easily deployed in GitHub pages. Simply run mkdocs gh-deploy on the project root, which can be easily automated on TravisCI even supporting versioned docs with a bit of effort.
You can see the current output in my fork: http://drslump.github.io/boo/

@masonwheeler thanks for reviewing it! note though that these are the contents from the wiki, I haven't edited them except for styling issues.
I'll fix the issues you raised up though :)

Also fixed the Travis CI build spec (SourceForge project for Mono no longer exists)


iOS 14+ support added for changes related to application tracking permission.

For iOS 14+ apple changes regarding Application tracking, you need to ask the user for permission to track Application.
"isAdvertisingTrackingEnabled" is deprecated and always return NO/false for iOS 14+
https://developer.apple.com/documentation/adsupport/asidentifiermanager/1614148-isadvertisingtrackingenabled

I can confirm what problem is solved with that pull request. @FlorianBergmann any chance that can be merged and released?

Yep, this is very important for ios 14, data will be null without it

But the api was deprecated, we need to use https://developer.apple.com/documentation/apptrackingtransparency instead @ijunaid

@FlorianBergmann  any chance that can be merged and released

@FlorianBergmann  any chance that can be merged and released

Would it be possible to merge this PR and make a new release?

Hello! no one here to merge, please?? :(


Unable to Install via aur helper

:: Proceed with installation? [Y/n]
:: Retrieving packages...
zenity-4.0.2-1.1-x86_64.pkg.tar.zst failed to download
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from cdn-1.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from at.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from nl-ams.soulharsh007.dev : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from aur.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mirror.lesviallon.fr : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from no.mirror.cx : The requested URL :: Proceed with installation? [Y/n]
:: Retrieving packages...
zenity-4.0.2-1.1-x86_64.pkg.tar.zst failed to download
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from cdn-1.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from at.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from nl-ams.soulharsh007.dev : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from aur.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mirror.lesviallon.fr : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from no.mirror.cx : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mirror.truenetwork.ru : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mirror.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from cdn77.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mirrors.tuna.tsinghua.edu.cn : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from us.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from cdn.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mir.cachyos.fr : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mirror.truenetwork.ru : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mirror.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from cdn77.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mirrors.tuna.tsinghua.edu.cn : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from us.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from cdn.cachyos.org : The requested URL returned error: 404
error: failed retrieving file 'zenity-4.0.2-1.1-x86_64.pkg.tar.zst' from mir.cachyos.fr : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

Thanks for repporting.
I can't reproduce.
I just fresh installed CachyOS on a VM and it's working fine.
There's something wrong with your repositories.
Try to update your system with sudo pacman -Syyu.

fixed now somehow


add uberon code to v2g data

create a tissue label <=> uberon code LUT to use in the v2g pipeline

Moved to https://github.com/opentargets/genetics/issues/222


Getting 429 errors (Too Many Requests)

Hi,
I'm getting 429 Too Many Requests errors back from the API. I'm getting this a lot because of the way the To Watch and sync is implemented in our apps and because we never thought they would be a quota or something like that in place.
Should we update our app to take this into account? Do we have more info on the number of requests we can do in what time? Do we have a Retry-After header we can use?
Thanks for the info!

Was going to create the same issue. Even after several requests to API, getting errors:
429 API rate limit exceeded. Please wait 11 seconds then retry your request.
Never happened before, is this some temporary or permanent limitations?

We were testing out API limits last week to gather some stats, but we reverted the change which stopped the 429 errors. We'll be testing out some update rate limiting this week. The goal is to prevent poorly coded apps from spamming the API, but while not affecting correctly coded apps from using the API as normal.
We recommend handling the 429 errors and the API docs have an example of the info that is sent back. We've had the 429 documented, but need to start enforcing more strict rate limits to deal with the recent performance issues.
https://trakt.docs.apiary.io/#introduction/rate-limiting

I see in the documentation it says to wait to the time until returns in the X-Ratelimit header. But this is problematic because of timezones and regular changes of them. For example a change of DST date which happens quite often would then result in the App waiting potentially an extra hour.
The App would have to convert local time to Zulu which can be wrong when the timezone changed (DST changes or others). It would be more useful and less problematic if a field seconds or similar would be returned with the value how many seconds to wait. This would be then timezone convert error independent.

@rectifyer will you also support the standard Retry-After header (indicating how long to wait before making a new request in seconds)? During my tests last week I was it and have started an implementation based on that header. Would be awesome if you could.
I understand you'll do more tests this week. Does that mean that we should already update our apps for this?
Another question is if this rate limit is linked to our app-id or to the user's ip or to something else?
Thanks for the info!

@kevincador yes, there will be a Retry-After header returned as well, I'll update the API docs. I would recommend updating your apps to handle the header yes, we're still in the testing phase but it's good to handle it. It is linked to the user's IP currently.
@Prinz23 the until is in UTC like all other timestamps we return. That should be fine to use in your app and I don't believe there should be any conversion issues with it.

Hello @rectifyer
You may be aware that the library called Requests is the defacto HTTP library for Python applications cross platform. A dependency of it is urllib3 and only yesterday did they push a commit where the message in the changes.rst file reads...
Fix retry backoff time parsed from ``Retry-After`` header when given
  in the HTTP date format. The HTTP date was parsed as the local timezone
  rather than accounting for the timezone in the HTTP date (typically
  UTC) (Pull #1932, Pull #1935, Pull #1938, Pull #1949)

This fix will not propagate to many peoples machine for months at the best case.
As you can see, there are clearly issues converting and using any full date system, locales, bugs in libraries, systems not set correctly, and other issues.
Can you please make it easier for application developers by simply having some kind of SecondsUntil:Integer header, where no conversion is required and where it would not matter if an enduser machine has correct locale, correct date/time, or whatever, because the number of seconds to wait, is simply that.
Please reconsider to make your goal of getting apps to easily adopt and back off from hammering your server easier. It takes near zero developer effort, and is far less issue prone, to simply pop a response number of seconds into a wait until next request function, don't you agree ?
Thanks.
Jack

Hello @rectifyer
You may be aware that the library called Requests is the defacto HTTP library for Python applications cross platform. A dependency of it is urllib3 and only yesterday did they push a commit where the message in the changes.rst file reads...
Fix retry backoff time parsed from ``Retry-After`` header when given
  in the HTTP date format. The HTTP date was parsed as the local timezone
  rather than accounting for the timezone in the HTTP date (typically
  UTC) (Pull #1932, Pull #1935, Pull #1938, Pull #1949)

This fix will not make it to many peoples machines for months at the best case.
As you can see, there are clearly issues converting and using any full date system, bugs in libraries, systems not set correctly (e.g. locales), and surprisingly many others.
Your response text in messages is like 429 API rate limit exceeded. Please wait 30 seconds then retry your request - this text may vary or change, so can you place that number into a response header field so that it is always explicit.
Please reconsider to make your goal of getting apps to easily adopt and back off from hammering your server easier. It takes near zero developer effort, and is far less issue prone, to simply pop that response number of seconds into a wait until next request function, don't you agree ?
Thanks.
Jack

The Retry-After is the number of seconds, not a timestamp.

@rectifyer I would like to test my implementation regarding this. Would it be possible to enable this on staging or to communicate when you enable it next for your tests on production?
Also, do you have an ETA for when this will be live?
Thanks!

Closing this topic since I just posted an official announcement which can be a more global place to discuss.
@kevincador this will be live today with the limit mentioned in the API docs. I'm also in the process of rebuilding the staging server since it died recently.


Add csrf token support

What's this PR do/fix?
Try to find csrf token and add it to the header of all requests by patching the requestInterceptor. The behavior is based on the configuration described in the spring security reference. The following order is the order of finding the csrf token.
P.S. This implementation will always use the csrf token obtained the first time.
P.S. If necessary, Maybe someone in the future can add the ability to configure these behaviors, I don’t know how to add options. 😢

CSRF token within your meta tags [1]
The meta name must be _csrf and _csrf_header. / is the page used to query meta data.
<html>
<head>
  <meta name="_csrf" content="${_csrf.token}"/>
  <!-- default header name is X-CSRF-TOKEN -->
  <meta name="_csrf_header" content="${_csrf.headerName}"/>
</head>

Define an endpoint used to fetch csrf token [2]
The @RequestMapping value must be /csrf.
@RestController
public class CsrfController {

  @RequestMapping("/csrf")
  public CsrfToken csrf(CsrfToken token) {
    return token;
  }
}

It is important to keep the CsrfToken a secret from other domains.
This means if you are using Cross Origin Sharing (CORS), you should NOT expose the CsrfToken to any external domains.

CSRF token within your cookie [3]
The default cookie name is XSRF-TOKEN, and the default header name is X-XSRF-TOKEN.
@EnableWebSecurity
public class WebSecurityConfig extends WebSecurityConfigurerAdapter {

	@Override
	protected void configure(HttpSecurity http) throws Exception {
		http.csrf().csrfTokenRepository(CookieCsrfTokenRepository.withHttpOnlyFalse());
	}
}

Are there unit tests? If not how should this be manually tested?

File
% Stmts
% Branch
% Funcs
% Lines
Uncovered Line #s

csrf.js
82.86
87.5
87.5
81.82
10,11,13,17,19,21

Any background context you want to provide?

Parameter Name
Description

requestInterceptor
Function=(a => a). MUST be a function.  Function to intercept remote definition, Try-It-Out, and OAuth2 requests.  Accepts one argument requestInterceptor(request) and must return the modified request, or a Promise that resolves to the modified request.

What are the relevant issues?
#1450

Hi @dilipkrish , any suggestion?

@olOwOlo didnt mean for u to change it, was just asking if that has an impact on what browsers are supported. Thank you for doing that tho'.
Also one last question. Does the swagger-ui.html need to change? Seems like it should have the meta tags as u suggested?
<!-- The meta name must be _csrf and _csrf_header. / is the page used to query meta data. -->

<html>
<head>
  <meta name="_csrf" content="${_csrf.token}"/>
  <!-- default header name is X-CSRF-TOKEN -->
  <meta name="_csrf_header" content="${_csrf.headerName}"/>
</head>

@dilipkrish No, swagger-ui.html is a fully static file. Meta tags should be included in templates, such as JSP, freemarker, thymeleaf, etc.

CSRF

where is CsrfToken class ??

Hello guys, sorry but I have to ask :) Is there somewhere a "complete" example how to get rid of "404 for csrf" in spring boot 2.X?

This is a terrible pr.

If CSRF token in a cookie, how can swagger UI pick it up?  The token is changing per ANY POST/PUT/DELETE/PATCH operation.  So, is there any logic to pick up the value from the cookie?

If CSRF token in a cookie, how can swagger UI pick it up?  The token is changing per ANY POST/PUT/DELETE/PATCH operation.  So, is there any logic to pick up the value from the cookie?


dragging a file in the editor cause black screen

When you drag-and-drop a file in the editor, this cause a "crash": the screen is black and the only thing you can do is to cmd+q (not forcing).
The file in question is a c file, "norminette.c".
Atom is in full screen with just one pane.
autocomplete-clang, linter, linter-clang, tab-control are installed (and others, ...)
After this closing, Atom doesn't save my panes and my tree-view...
The file in question is from another desktop on my mac.
Macbook pro retina end 2013, 2,6 GHz Intel Core i5, 8Go of ram

@Kerosene2000 Strange, I'm having trouble reproducing that problem. Can you clarify which version of Atom you're using and if you can reproduce the problem in safe mode? Also, can you reproduce the problem for any file or only just that one file?
You also said this:

The file in question is from another desktop on my mac.

Can you clarify what this means and how it affects the report? If the file is not from a different desktop -- can you still reproduce the issue?

I was able to reproduce the same problem consistently, and it's only related to the full screen mode. If I open a fresh window (untitled), maximize it, and then close it directly from it's maximized state, I will get a crash notice from Apple "Atom quit unexpectedly." This results in your previously opened trees not reappearing upon reopening Atom (if I have more than 'untitled' open, it will not reopen with Atom).
The maximization on my laptop creates a new 'desktop' for my Mac (and hides the main Apple toolbar), meaning I can still swipe to swap my view back to the location I originally opened Atom. This is different than a typical 'maximize' that simply stretches the app across the current desktop with the Apple toolbar in view.
I believe this new desktop maximize that crashes Atom is set by default on all new Apple computers.
Atom 1.3.1
Mac OS X 10.11.1

@jnelken The full screen crashing issue is something separate (that I believe has been fixed in the recent beta versions).
Since there hasn't been a response to the request for more information, I'm going to close this. Please let us know if you can still reproduce the issue @Kerosene2000!


Wrong distance calculation

Your formula for calculating distance is incorrect. You need to use the bytes [6, 7, 12, 13, 18, 19, 24, 25, 30, 31, 36, 37] instead of [4, 5, 8, 9, 12, 13, 16, 17, 20, 21, 24, 25].
You can check again in the datasheet.

So the final corrected code will be
for i in range(6):     distance = (bytes_data[6 + (i*6) + 1] << 8) | (bytes_data[6 + (i*6)])


Add OOB permutation importance for xgbTree

It would be great if OOB permutation based feature importance is avaliable in xgboost.
The implementation of this method I have seen is in the R gbm package. But for now, the gbm::permutation.test.gbm can only compute importance using entire training dataset (not OOB).
I guess its result should not be that different from the current information gain based feature importance in xgboost.
Also, I guess the feature importance result may be highly related to the subsample parameter, I'm not sure if this have to be done in a bootstrap way. If so, then this may be related to #374
I hope the team can add this feature, It will be a great tool for feature selection.

The OOB feature importance option would only make sense for the random forest setting with num_parallel_tree, but I doubt it would make much sense for boosting. See also #1070. Overall, it seems like the xgboost random forest might need some specialized set of functionality to be fully useful.
What's more necessary for boosting, I think, is an ability to perform feature importance evaluation in a dataset separate from training. It could be done either by updating split gains for new data or it could also be a permutation-based approach. I had some brute force attempts in R for the latter, but a significantly faster implementation should in principle be possible for repeated prediction in data with single permuted (or some other way modified) columns. I'm still thinking over good ways to do it.

That's truly keen insight of RF and boosting. I agree with you. I mentioned because I saw this OOB permutation feature importance in the R gbm document. I thought I might miss some papers.
For the "feature importance on validation dataset" idea, I think it's valuable for finding features that has negative impact for performance. I think both of them can be done in R, though it will be slow especially the later one. A C++ level implementation would be great.


Issues with redis' get_client method

Those should be added:

socket_timeout
socket_connect_timeout
socket_keepalive
health_check_interval

ssl parameters should be set like this:
ssl=cacert is not None or cert is not None or key is not None,
ssl_ciphers=SSL_CIPHERS,  # Customize TLS ciphers (Python 3.10+)

This should be removed:
ssl_cert_reqs=ssl.CERT_REQUIRED if cacert else ssl.CERT_NONE,

Also, new redis and hiredis should be used.

And client.json() should not be part of the get_client method as this module is not a must.

Also password shouldn't be required if user is specified.


[React][Toast] Can't pass ReactNode to title or description

Description
When I try to add a ReactNode to title or description of a toast, the app crashes and I get the error

proxy set handler returned false for property '"validated"'

on the browser console.
Link to Reproduction (or Detailed Explanation)
https://github.com/lebretont/ark/tree/bug/toast
Steps to Reproduce
Clone the reproduction
Navigate to the packages/react folder
Execute bun vitest ./src/components/toast/tests/toast.test.tsx
Test fails
Ark UI Version
3.10.0
Framework

[X] React
[ ] Solid
[ ] Vue

Browser
Firefox, Arc
Additional Information
At first sight the error comes from the jsxFactory method inside factory.ts but I have not been able to correctly identify the cause or correct the problem.

This has been fixed in Zag.js. We'll release an update shortly.


Npm run test command not working as expected

In node 4.0, running npm test is no longer printing test results to console. Seems to just hang there.
Probably related to mocha-phantom moving core to a different module after 4.0.
This would be a good reason to upgrade the node version we're pegging this to.

Hi there @dereklieu
I was looking at how things are with regards to testing in Prose given that you mentioned needing more tests to do regression testing on some cool PRs (like the ProseMirror integration #935 )
I came by this issue and couldn't reproduce it locally switching with nvm to node 4.0, 4.1 or 4.2. I thought I'd give a shot at building with travis across all know node_js version to see if it caught something but it seems sane and passes and displays test results to the console except on 0.6 and 0.8.
Cheers,
Jun

@jmatsushita you're right, I just did a fresh npm install on 4.2.4 and it worked fine. Closing this.


fix(ui): add missing modal component to display login feedback

Added modal component to show login success message on form submission
Updated modal content to provide relevant feedback for login action
Adjusted login button to trigger modal display

This fix addresses the missing modal, ensuring users receive feedback after logging in.

Hey @ddoemonn, Thanks for your contributions. All of our examples are well crafted by designers. I will assign this task to designer for review.


Private organization repos don't work

My setup:

Gogs v0.9.46
Sqlite3
Ubuntu Linux 16.04

I want to be able to keep my department's organizations separate from each other. It would be great if the 'blue_widget_devel' organization and the 'red_widget_devel' organization couldn't see each other's repositories by default.
Right now, an organization's repos can be seen by everybody. If an org's repo is public, it shows up on the Explore page and can been seen by anybody. If I mark an org's repo as private, Gogs will block everybody from seeing it (including members of the organization).
Could we get a patch that will change the behaviour so that:

Repo Type
Behavior

Private individual user repo
Invisible to everybody except collaborators

Public individual user repo
Visible to everybody

Private organization repo
Invisible to everybody except organization members

Public organization repo
Visible to everybody

Never mind - I just didn't understand how the 'teams' work. :)


Update to zio 2

Closes #1161

Hi @adamw can I help with this?

zio-nio now has a 2.0-RC1 release! 🎉


ipconfig built with clang fails to complete dhcp process

Expected behavior
Build ipconfig with clang, boot, and clang properly finishes dhcp process.
Actual behavior
It hangs -- is it dropping packets, seeing corrupted packets, not handling a lock correctly? it's not clear.
Steps to reproduce

build everything with clang.
boot and see a hang.
build sys/src/cmd/ip/ipconfig/ipconfig.json
CC=clang build sys/src/9/amd64
hang goes away.

I interpret this as being only an ipconfig issue, and purely from the source in sys/src/cmd/ip/ipconfig, i.e. 3 files. I think we should drop ppp, by the way. I doubt anyone cares about ppp any more -- you can't find serial ports on most hardware, and PPPoE was never a big deal.

We always can do a Go program for PPP like any other abandoned old server.

@rminnich this is resolved right?

The odd part here is that anything ever worked at all. Ah well.
Fixed.


speech/captionasync: fix vet warnings

Seconds are int64, not a float. Format them with "%d".

/cc @adams-sarah


Only TriggerBot

Hello, I wanted to select from your cheat only the trigger bot and only the dependencies necessary for it. I tried to do this, but everything was mixed in one object and there were vars and funcs for all cheat funcs, so I got confused and didn’t succeed. Because of this, I want to ask you for a favor. You can select from your cheat only a triggerbot and a team check with only the necessary parameters in the objects (which will relate to the triggerbot, and not to the aim, wh, ... which will not be) and only the necessary dependencies. I only need a trigger for personal use and don’t want to use all the other functionality. I would be very grateful. As a thank you, I can tell you about your project on my discord server, which has over 100 participants
my discord: nick_vinesmoke

You can check out this, it uses dependency injection instead of global variables, and i think it's cleaner in general.

Is it external software?

is it undetected?

Can you select from your cheat only a triggerbot and a team check with only the necessary parameters in the objects (which will relate to the triggerbot, and not to the aim, wh, ... which will not be) and only the necessary dependencies. I only need a trigger for personal use and don’t want to use all the other functionality.

pls

ok

If your issue has been solved can you close the issue?


[SPARK-48089][SS][CONNECT][FOLLOWUP][3.5] Disable Server Listener failed 3.5 <> 4.0 test

What changes were proposed in this pull request?

Disable the listener test. This test would fail after https://github.com/apache/spark/pull/46921, which is now reverted. The reason was because with #46921, the server starts a server side python process which serializes the StreamingQueryProgress object with the new StreamingQueryProgress change. But in the client, the client tries to deserialize StreamingQueryProgress use the old StreamingQueryProgress without the change, which caused serde error.
However, as the change is going to spark 4.0, and is considered a generally good improvement and does more good than harm, we would like to disable this test to bring back #46921.
Why are the changes needed?

Unblock bringing back #46921
Does this PR introduce any user-facing change?

No
How was this patch tested?

No need
Was this patch authored or co-authored using generative AI tooling?

No

Merged to branch-3.5


Identity-Based Signatures

Hello,
How would I go about implementing identity-based signatures? I noticed that you have added Hess Identity Based Signatures to cryptiid-native. What needs to be done to implement this in the Java version?
Thank you!

Hi @bobomate!
We are not planning to implement any more protocols in the java version of CryptID, but we would be more than happy if we would receive pull requests.
If you want to implement the Hess signature protocol yourself, just fork the repository and make it happen. :)
As I believe the Hess protocol is highly based on the Boneh-Franklin scheme, so all the required arithmetics are implemented already, all you need to do is to use the right function calls. If you start working based on our Identity-based Encryption implementation and the native Hess implementation, it shouldn't be difficult to get it done.
If you plan to implement it, please add some tests to your code and open a pull request, so I or @battila7 can review it and merge it to CryptID-java if it is correct.


🚀 Feature: Upload Speed and Percentage Stats

🔖 Feature description
It would be great to see the upload speed, percentage of file upload completed, and possibly an estimate of the time left to upload each file.
🎤 Pitch
When uploading small files that take a couple seconds I know seeing the stats don't really matter. But when uploading larger files it would really help to see how fast they are uploading and how much time is left.

This is an interesting idea, it would be easy to calculate the progression using a chunk counter

It would be nice!!!!

@McFex mentioned in the issue #243 that the color of the progress indicator in dark mode is poor. This will be fixed too when I have the time to work on this.

I think this is a great idea too!


[BEAM-7418] Add google-cloud-storage to base image

This adds google-cloud-storage to the base python worker image. This is another useful package required by some libs that do not work with Beam's FileSystems.

Thank you for your contribution!

This file is generally meant to match setup.py. For loading additional dependencies there are alternatives, also it is possible to build more specific containers.
The reason I am worried about expanding here beyond the bare minimum is to reduce the dependency conflicts.
That said, what other libs needs this dependency?


Game crashing when breaking trees

I just downloaded the 1.18.2 version for forge. The game crashes immediately after breaking a log with the chop setting (normal breaking works normally)
Heres the crash message:
The game crashed whilst exception in server tick loop
Error: java.lang.NoSuchMethodError: 'net.minecraftforge.registries.tags.ITagManager net.minecraftforge.registries.IForgeRegistry.tags()'
Exit-Code: -1
And the log:
crash-2022-03-25_15.37.54-server.txt
Thank you in advance.
Best egards,
Daniel

Hi man, updating to Forge 40.0.18 or later should fix the crash

Updating to forge 40.0.32 and n ow its working, thank you.

Sweet! Any time big guy.


tests: reduce timeouts and iterations

This reduces the time it takes to run the test. Shorter timeouts on
clients to avoid awaiting for the detault timeouts.
It's also reduces the iterations in some test functions, this doesn't
seem to impact the tests indicating those numbers where random to begin
with.
Stop using Google Public DNS in tests as well: it's faster, keeps things
local and avoids spilling info to Google.
This brings the test duration down from ~8s to ~3s on my machine.
PASS
ok  	github.com/miekg/dns	2.751s

Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
PASS
ok  	github.com/miekg/dns	7.915s

Codecov Report

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

@@            Coverage Diff             @@
##           master    #1175      +/-   ##
==========================================
+ Coverage   55.11%   55.19%   +0.07%
==========================================
  Files          42       42
  Lines        9581     9581
==========================================
+ Hits         5281     5288       +7
+ Misses       3275     3270       -5
+ Partials     1025     1023       -2

Impacted Files
Coverage Δ

server.go
68.88% <0.00%> (+0.30%)
:arrow_up:

msg.go
74.56% <0.00%> (+0.76%)
:arrow_up:

client.go
70.05% <0.00%> (+1.12%)
:arrow_up:

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 10e0aee...08eab3b. Read the comment docs.

move the contentious bit out of this PR, all comments addressed, so I'm merging.


Lt.matrix() still not working for some case (brombo/galgebra#18)

@chaowenGUO commented on May 29, 2016

import ga,sympy
base=ga.Ga('b_1|2|3',g=[1]_3,coords=sympy.symbols('x1:4',real=True))
transformation=base.lt([[1,-2,3],[4,0,3],[7,8,-9]])
print transformation
print transformation.lt_dict
print transformation.matrix()
the final answer still wrong, it print out:
Matrix([
[ 1, -2, 3],
[ 3,  4, 0],
[-9,  7, 8]])
the correct answer is just:
Matrix([[1,-2,3],
[4,0,3],
[7,8,-9]])
By the way, there is some thought about the definition about Lt.matrix().
From the definition right now:
list M
If M is a list of vectors equal in length to the dimension of the vector space then the linear transformation is L(ei)=M [i]. If M is a list of lists of scalars where all lists are equal in length to the dimension of the vector space then the linear transformation is L(ei)=\sum_j M [i] [j]ej.
It is a good definition, because it follows the row major routine of python about how to access list of list. As a result, in Ga.lt(M), the first row of M is the image of e1, the second row of M is the image of e2 and so on.
Then, in the definition of Lt.matrix():
Returns the matrix representation (sympy Matrix) of the linear transformation, L, defined by L(ei)=\sum_j Lijej where Lij is the matrix representation.
That means Lt.matrix() return a sympy matrix A. The first row of such matrix A is the image of e1, the second row is the image of e2 and so on. However, such definition does not follow the routine of linear algebra. In linear algebra, L(ei)=\sum_j ejLji. So the first column of matrix L is the image of e1, the second column of matrix L is the image of e2 and so on. As a consequence, L_v is the image of v, in order to get the same result in Lt.matrix(), one needs to write Lt.matrix().T_v, to get the transpose first. So it is recommended to change the definition of Lt.matrix() to:
Returns the matrix representation (sympy Matrix) of the linear transformation, L, defined by L(ei)=\sum_j ejLji where Lji is the matrix representation.
So that Lt.matrix() should return the transpose of the matrix M that used in Ga.lt(M). In the new definition, galgebra both respects the routine in python and linear algebra.
Full example:
preamble(the same for Now and New)
import ga,sympy
base=ga.Ga('b_1|2',g=[1]_2,coords=sympy.symbols('x1:3',real=True))
matrix=sympy.Matrix([[1,2],[3,4]])
vector=base.mv('v','vector')
transformation=base.lt(matrix)
image=transformation(vector)
vectorSympy=sympy.Matrix(vector.blade_coefs(base.mv()))#to construct sympy matrix from galgebra vector
Now:
imageSympy=transformation.matrix().T_vectorSympy#regular matrix multiplication
str(image)==str(imageSympy[0]_base.mv()[0]+imageSympy[1]*base.mv()[1])#is true
New:
imageSympy=transformation.matrix()_vectorSympy#no transpose
str(image)==str(imageSympy[0]_base.mv()[0]+imageSympy[1]*base.mv()[1])#is true
what is your opinion?

@brombo commented on May 30, 2016

Fixed error in Dictionary_to_Matrix(dict_rep, ga) function and pushed to
github. I will think about you comments on matrix representations.

@brombo commented on May 30, 2016

Implemented you suggestion (pushed to github).  The matrix of a linear
transformation now agrees with the mathematical definition for the
multiplication of matrices and column vectors.

@brombo commented on May 30, 2016

Attached is a description of the latest thing I am trying to implement
in galgebra.  You might find it interesting.

@chaowenGUO commented on May 30, 2016

Thank you. But where is the attachment?

@chaowenGUO commented on May 30, 2016

Well, there is still several issue.
First galgebra.tex:
line 2440 should be changed to: $\f{L}{\ebf_{i}} = \ebf_{j}L_{ji}$ where $L_{ji}$ is the matrix representation.
to represent the new definition
Second lt.py
line 94 should be changed to: basis=sorted(dict_rep.keys(),key=lambda x:x.sort_key())
Because the keys method in dict can not guarantee the order. I encounter several cases, the order of dict_rep.keys() is b2,b1,b4,b3. So to sorted it first can guarantee the order.

@utensil commented on Jun 9, 2016

Thank you. But where is the attachment?

@brombo , it seems that you tend to reply to Github issues via only emails and attached an attachment along with the email but it's dropped by Github.

From http://webcache.googleusercontent.com/search?q=cache:https://github.com/brombo/galgebra/issues/18

Output on master:
In [50]: base=ga.Ga('b*1|2|3',g=[1]*3,coords=sympy.symbols('x1:4',real=True))
    ...: transformation=base.lt([[1,-2,3],[4,0,3],[7,8,-9]])
    ...: print(transformation)
    ...: print(transformation.lt_dict)
    ...: print(transformation.matrix())
Lt(b_1) = b_1 - 2*b_2 + 3*b_3
Lt(b_2) = 4*b_1 + 3*b_3
Lt(b_3) = 7*b_1 + 8*b_2 - 9*b_3
{b_3: 7*b_1 + 8*b_2 - 9*b_3, b_2: 4*b_1 + 3*b_3, b_1: b_1 - 2*b_2 + 3*b_3}
Matrix([[1, 4, 7], [-2, 0, 8], [3, 3, -9]])

This is the transpose of what is claimed to be expected here, but I think that's maybe covered by #104.
This looks a little wrong still, opening gh-158 to track what's left.


Rename clock_systime[r|spec] to clock_systime_[ticks|timespec]

Summary
Follow the consistent naming patter of https://cwiki.apache.org/confluence/display/NUTTX/Naming+of+OS+Internal+Functions
Impact
Name change only. No impact is expected
Testing

nxstyle error can be ignored:
arch/arm/src/lc823450/lc823450_sddrv_dep.c:98:35: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:147:29: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:178:29: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:212:29: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:229:29: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:271:33: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:286:28: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:303:28: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:312:26: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:326:35: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:360:32: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:391:25: error: Mixed case identifier found
arch/arm/src/lc823450/lc823450_sddrv_dep.c:479:26: error: Mixed case identifier found
drivers/wireless/nrf24l01.c:1905:11: error: Mixed case identifier found
drivers/wireless/nrf24l01.c:1908:11: error: Mixed case identifier found
drivers/wireless/nrf24l01.c:1912:11: error: Mixed case identifier found

I wonder if internal clock interfaces should be nxclock_ vs. clock_?  The are several other internal clock interfaces, we don't need to change this PR for that.

This is failing and holding up the merge:
libmetal/lib/system/nuttx/time.c:21:6: error: implicit declaration of function 'clock_systimespec'; did you mean 'clock_systime_timespec'? [-Werror=implicit-function-declaration]
  r = clock_systimespec(&tp);
      ^~~~~~~~~~~~~~~~~
      clock_systime_timespec

Now it looks like it is failing with in lc823450_sddrv_dep.c:
chip/lc823450_sddrv_dep.c: In function 'sddep_read':
chip/lc823450_sddrv_dep.c:402:32: error: suggest parentheses around comparison in operand of '|' [-Werror=parentheses]
  402 |                           type == SDDR_RW_INC_WORD ? LC823450_DMA_DSTINC : 0,
chip/lc823450_sddrv_dep.c:411:31: error: suggest parentheses around comparison in operand of '|' [-Werror=parentheses]
  411 |                          type == SDDR_RW_INC_HWORD ? LC823450_DMA_DSTINC : 0,
chip/lc823450_sddrv_dep.c:420:32: error: suggest parentheses around comparison in operand of '|' [-Werror=parentheses]
  420 |                           type == SDDR_RW_INC_BYTE ? LC823450_DMA_DSTINC : 0,
chip/lc823450_sddrv_dep.c: In function 'sddep_write':
chip/lc823450_sddrv_dep.c:490:32: error: suggest parentheses around comparison in operand of '|' [-Werror=parentheses]
  490 |                           type == SDDR_RW_INC_WORD ? LC823450_DMA_SRCINC : 0,
chip/lc823450_sddrv_dep.c:499:31: error: suggest parentheses around comparison in operand of '|' [-Werror=parentheses]
  499 |                          type == SDDR_RW_INC_HWORD ? LC823450_DMA_SRCINC : 0,
chip/lc823450_sddrv_dep.c:508:32: error: suggest parentheses around comparison in operand of '|' [-Werror=parentheses]
  508 |                           type == SDDR_RW_INC_BYTE ? LC823450_DMA_SRCINC : 0,
cc1: all warnings being treated as errors

I don't see how that is related to your change.

You did not modify c823450_sddrv_dep.c and it appears to me that master does have the missing parentheses.  For example at lone 409 on master (NOT line 402), I see the first:
 (type == SDDR_RW_INC_HWORD ? LC823450_DMA_DSTINC : 0),

Do you need to rebase your branch?

No, I was mistaken.  You did modify the tests.  Your PR removes the parentheses and introduces the errors.  You need to back out all of the changes like:
@@ -485,7 +487,7 @@ SINT_T sddep_write(void *src, void *dst, UI_32 size, SINT_T type,
        lc823450_dmasetup(_hwdma[ch],
        lc823450_dmasetup(_hwdma[ch],
                          LC823450_DMA_SRCWIDTH_WORD |
                          LC823450_DMA_SRCWIDTH_WORD |
                          LC823450_DMA_DSTWIDTH_WORD |
                          LC823450_DMA_DSTWIDTH_WORD |
    -                     (type == SDDR_RW_INC_WORD ? LC823450_DMA_SRCINC : 0),
    +                     type == SDDR_RW_INC_WORD ? LC823450_DMA_SRCINC : 0,
                          (uint32_t)src, (uint32_t)dst, size / 4);
                          (uint32_t)src, (uint32_t)dst, size / 4);
        break;

You modified the tests in this PR. Your PR removes the parentheses and introduces the errors. You need to back out all of the changes like:

I fixed them with a forced push to your branch


where is the code for the data augmentation?

The specific code for the data-augmentation was not packaged here, but can be reproduced by using an off-the-shelf NER classifier and collecting entities under some per-type grouping, then swapping.
We however release the augmented data used in the paper in this repository.
Hope this helps. If any extra pointers are needed for adapting TypeSwaps to your problem, happy to answer questions :)


fix co2_year

This PR addresses issue #50

successfully 0-diff tested for Intel (incl debug) by @gmao-rreichle


jax2tf does not preserve argument names

When converting a function from JAX to TensorFlow using experimental jax2tf.convert, the function arguments are not preserved, thus it is not possible to call the code with named instead of positional arguments.
For example, the following snippet will break:
    def f_jax(x):
        return jnp.sum(x)

    f_tf = jax2tf.convert(f_jax)

    x = jnp.zeros(3)
    print(f_tf(x=x))

Traceback (most recent call last):
  File "test.py", line 8, in <module>
    print(f_tf(x=x))
TypeError: converted_fun() got an unexpected keyword argument 'x'

My workaround so far has been to wrap the converted function around another function, and then proceed to export the saved model.
    def f_jax(x):
        return jnp.sum(x)

    f_tf = jax2tf.convert(f_jax)
    f_wrap = lambda x: f_tf(x)

    x = jnp.zeros(3)
    print(f_wrap(x=x))

Since jax2tf is experimental, I expected to find some issues. However, this one is not listed as a known issue. An important use case for this is to allow models with multiple inputs to be called via Tensorflow Serving.

@saeta Thank you for the quick solution :)


REST access via token and session

I've encountered a case where I have to give access for a REST method via oauth and session. It works if only one access rule is on this method, but if both are assigned it doesn't work anymore. The problem is described in #4575, but it isn't solved for me, because it must be accessed from both and not only one.
My current approach looks like this:
public function behaviors()
{
    return ArrayHelper::merge(parent::behaviors(), [
        'authenticator' => [
            'class' => CompositeAuth::className(),
            'authMethods' => [
                ['class' => HttpBearerAuth::className()],
                ['class' => QueryParamAuth::className(), 'tokenParam' => 'access_token'],
            ],
            'except' => ['generate-password'],
        ],
        'access' => [
            'class' => AccessControl::className(),
            'rules' => [
                [
                    'allow' => true,
                    'roles' => ['@'],
                    'actions' => ['generate-password'],
                ],
            ],
            'only' => ['generate-password'],
        ],
    ]);
}

With this method the generate-password action is accessible via a normal logged in user, but isn't via oauth.
Currently I see two options:

Make the method public.
Copy the method and use it with another name.

Make the method public.
Copy the method and use it with another name.

which method?

@cebe Sorry, that are just options which I could do, so make the generate-password method public to all users. I've not done any research, why this is not possible with this two behaviors.

if u want auth users in all actions except generate-password why u write role for guest as
'roles' => ['@'],
need ?

@lynicidn auth users should also have access to generate-password.

also or only ?

For what it's worth I agree with @thejahweh
if in his example he sets authentication to ? all users can access BUT he can not access Yii::$app->user for logging or other purposes because of the 'except' on the authenticator. This is a problem I've run into on many apps I've done in Yii. This limitation frequently causes duplication of actions just so I can have both a public and "authenticated" version.
If he removes the authenticator then any role type access rules defined by AccessControl are useless (except for actual RBAC, which still works just fine) since it won't allow unauthenticated users to access it even when the rule allows anonymous users.
And allowing only '@' but having the 'except' condition makes the action completely inaccessible as the AccessControl doesn't check for the types of authentication he needs.
I dislike that the Authentication Filters deny access in direct opposition to any AccessControl rules that have been set. @kirill-konshin said something very similar at the end of #4575 more than a year ago. However I understand that implementing such behavior would very likely break backwards compatibility unless you released a whole new set of authorization filters that only set the user if the AccessControl filter is used and maybe follow the existing behavior IFF AccessControl is not being used. And likely since filters wouldn't easily be made aware of each other you'd probably just make an AccessControl compatible version that defers all authorization to the access control.
I accept that my knowledge in security matters is lacking and if there is some solid reason why this isn't as safe I'm willing to learn. But I think the TLDR of his point would boil down to "the authenticator is currently performing authorization tasks, why?"

On second look I think I misread the thread. but I think what I propose would still fix the issue.
I have the problem of wanting the user object in an action that doesn't need it to be accessible.
From my latest reading of the problem whatever authenticator is getting the user object from session is doing it's job just as I suggest the other filters should. but because the user is logged in by session and not one of the other methods from the CompositeAuth filter they are rejected by the CompositeAuth filter doing authorization tasks and not letting the AccessControl handle it.
Correct me if I'm wrong

@kyrandita I think the 'optional' parameter will solve the issue you mentioned.


[Feature Request] enhanced email marketing

Is your feature request related to a problem? Please describe.
There is Mass Mail Tool extension at FOSSBilling, but capabilities of the Recipients filter are incredibly low - there is even no possibility for filtering clients that opted into email marketing.
Describe the solution you'd like
I think two things could be done:

add possibility to change custom field type (currently it is string)
add optional filter for Mass Mail Tool which checks selected custom field for true/false

Describe alternatives you've considered
Currently the only alternative I am aware of is usage of external means, for example something like public read-only mailing list
Additional context
null

You're right, there needs to be changes, also to comply with GDPR. I'll look into it and update the module.

Related to #254


Application problem due to UI change of Korean server

Before opening an issue:

[ check ] I tested the latest release
[ check ] I looked at other issues (even the closed ones)
[ check ] I read the Troubleshooting Guide
[ check ] I'll fill this template properly

Your issue will get closed/locked by the bot in case proper info isn't provided
If you open unnecessary/dumb issues, you'll be rewarded with appropriate tags.

Describe the bug
First, I apologize for my poor English.
The application does not work properly as the Korean server's user interface becomes the same as the Japanese server.
There are problems such as the location of the touch and the inability to recognize it.
Device Info (please fill at-least 'Device model'):

Device model: [Most devices (Author is using Galaxy 21)]
Screen size: [Most display sizes (Author's device display is 2400x1080)]
Android Version: [Most Android versions (Author is using Android 11)]
RAM: [Most Capacity (Author is using 8GB)]
Most Korean server users are experiencing this problem.

Korean server's user interface becomes the same as the Japanese server.

There might be differences. I don't play on KR server, so please provide some screenshots so we can see what changed.

I'm attaching a video.
Please understand that I am forced to post a link to the Korean community.
https://gall.dcinside.com/mgallery/board/view/?id=mfgo&no=3315267&page=1
If you can't see two videos, I can send you the video myself.
The first video shows that the application does not come into the dungeon.
The second image shows that the macro originally woven with a double scadi system is not working properly.

Patches such as speed/UI applied on the 5th anniversary of the Japanese server have been applied to the Korean server.
In this process, the application seems to be a bug caused by mistake for UI of the existing Korean server.

FGA build 1402
Galaxy Note20 Ultra 5G
Android 11
Accessibility Enabled
Set as Fullscreen mode app
https://user-images.githubusercontent.com/559952/126946944-3fd82b38-b4c0-4512-980b-d16fc6484e87.mp4
https://user-images.githubusercontent.com/559952/126946955-6b3c3ac1-8b33-4240-beb6-021a48a4237c.mp4
https://user-images.githubusercontent.com/559952/126946957-304efbe7-da1c-493a-af7d-ee6f6e623e0e.mp4

FGA build 1402
Galaxy Note20 Ultra 5G
Android 11
Accessibility Enabled
Set as Fullscreen mode app
Flag on for ignore camera hole -> no effect
Set as JP server
https://user-images.githubusercontent.com/559952/126954505-dd5d366d-0cc3-45ee-b35b-cd58689b414b.mp4
I guess we might set flag on for KR server to NewUI (wide)

@MathewSachin Can you check #787 ?

Btw as a temporary solution until this issue is fixed, setting stage counter similarity to 100% helps at least executing the script but it won't do auto-battle and only stick to the script. Also it doesn't know that the battle has finished so you kinda have to press on the 'Next' Button on the item-drop screen yourself to loop the script. This mostly helps EXP/QP farming scripts.

@Yoshinyong that only applies to 16:9 devices. Things are different for other resolutions.

@MathewSachin Just in case since some ppl also run it on app-players which are mostly 16:9

@Yoshinyong Ah, then that should be mentioned or others who're not using 16:9 would get confused.

@MathewSachin Ye you are right. Updated the context.


[themes][semantic] default themes: new constant color

Dark+ / Light +
Use the default color for constant variables.

as done in the VS 2019: See #92965
take advantage of constants info from semantic highlighting

Hey @aeschli just saw this in today's insiders.
For JS/TS, the new color for constants does change the character of the dark theme. One specific nit I have is that constants now use the same color as punctuation which makes code less legible:

Trying to match VS is a good goal but I find the impact of this little change to be quite drastic (more drastic than enabling semantic highlighting in the first place). And honestly, we have a whole lot of users who are using the default VS Code theme and don't care what Visual Studio is doing
Maybe there's a compromise that won't be quite as jarring when users upgrade but still lets us convey if something is a constant or not?

I thought it was a bug and was about to report it. It feels like the color that should be there just disappeared.

I fully understand. It also took me a while to like it. Theme changes are always very controversial.
Still, I wanted to put it out to see the general reaction. I'm fine to revert it for stable if there are many negative reactions.

I first tried to find another color, but it's hard and equally controversial. Also there has been many requests for more colors in the default themes and we always resisted with the argument to keep it simple and clean
we define a new Default theme that we only give as default to new users. If we do that, it should be more than just a single color change, but a a new, fresh design.
@misolori Your thoughts?

@aeschli: Would it be possible to use something in between cyan and white? Or go darker.
The reason I got the feeling something was wrong with the theme was because nothing else in the dark theme is white. Everything is different colors. So it felt like something was "missing". Personally I don't care if let/const have the same color, but since they are still very similar from a semantic POV maybe a more subtle color change would suffice?

The change of color for consts in a test run in Insiders. Please give it a chance and please add a thumbs up/down on that issue.
From https://github.com/microsoft/vscode/issues/95434#issuecomment-615086755

It's a bit strange to close opened issue as duplicate of this and expect feedback on closed issue. Could you have an open one for feedback?
I don't have any preference for color, however default "white" doesn't have any as with plain text and would be nice to have something else.

take advantage of constants info from semantic highlighting

I don't think that knowledge that some variable/property is constant is more useful to discard type of data in variable as was implemented for JS/TS.
In JS some teams (our too) use const for everything except that we need reassignments let (counts are const 10k+ vs let ~1.5k) so almost every variable in our app is white.
It's also (almost ?) impossible to create readonly object properties in plain JS - no changes here.
Previous behavior with value type should have greater priority than generic constant.

Reopened for feedback

I'm not finding this particularly useful, especially on properties. You have to know something about the kind of immutability being used in order to determine if/when a property can be written to.
Unfortunately, some extensions/grammars do not respect the subtle distinctions. For example, in TypeScript, while the readonly modifier is correct semantically, it's not the same as a const modifier, and yet that is the scope being used on read-only properties. If you switch to a language with properly scoped read-only fields, then you now have two colors for the same thing.
This is also made worse if a language server is inconsistent in its semantic highlighting. Again, from TypeScript:
class A {

  public readonly roField = 1;

  // Without a setter, this should be read-only too, especially since it
  // could also implement an abstract readonly field from an interface.
  public get roProperty(): number { return 1; }

  public foo(): number {
    return this.roField /* white */ + this.roProperty /* light blue */;
  }

}

Another problem is that enum members aren't easily distinguishable in code anymore. This is mainly because the light green color was replaced and isn't being used on them or the enum identifier. It would be a lot better if the enum identifier got that color by default now, which would also be consistent with VS2019 as well.
That said, I would like to see the default theme be a little closer to VS2019. Another alternative could be to reduce the change to just local constants (if possible, pending other issues) and enum members (which are never ambiguous because all members are always const).

I also thought this was a bug when I saw it.  I agree with @IllusionMH, my JS team also uses const for everything and now I have a lot of white text in my dark theme.  It just feels like part of the highlighting isn't working or that the variable i'm using doesn't exist.

We will give an new color a try that is closer to the variable color. Please try it out a while and let me know whether the new color is better or if we should go back to the original theme.

Version: 1.45.0-insider
Commit: a250df703de955a38aed427a917bce8278ab3331
Date: 2020-04-24T20:46:59.782Z
Electron: 7.2.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 17.7.0
I am a user of Default Light+. The current  color of constant variables,  variable.other.constant,variable.other.enummember { "foreground": "#328267" }, is too light when the background color is white.
It is difficult to distinguish it from the color of comments.
1.44.2:

Insiders:

There's not a lot of contrast with existing colors in the dark theme either. It's kind of in no man's land between this, type names, and unused variables/parameters.

@misolori see above, comment on the contrast of the new color.

@tamuratak thanks for the feedback, our accessibility color contrast goals are to meet WCAG AA so you will find this throughout all of our themes. The new const color meets WCAG AA at 4.6:1, see below.

cc @isidorn

To verify:
Open the Dark+/Light+ themes on a TypeScript file and look at the coloring of const variables, enum members and read-only properties . They should have a different color than regular variables.
Verify that the color is not to be confused from the keyword and commend color.

Can you please remove it? Or at least make it toggleable. I thought this was a bug because it was so ugly lol

Default Dark Theme:

x - variable is not used
y - variable is used
a - variable is used
b - variable is not used

This color creates more problems than benefits

I loved my yellow enums! Bring them back! 😢

Declaration and usage of the same variable have different colors. Looks a bit strange:

@gnaeus Did you disable semantic highlighting?

@aeschli, why console.log changes color, when this option is enabled?

@aeschli no I didn't disable semantic highlighting. My combination of flags:
    "editor.semanticHighlighting.enabled": true,
    "editor.semanticTokenColorCustomizations": {
        "enabled": false,
    },

Also here is the settings for all who loves the old behavior:
"editor.semanticTokenColorCustomizations": {
  "rules": {
    // different color for all constants
    "*.readonly": "#9cdcfe",
  }
}

OLDNEW

@gnaeus enums should be yellow :)

Can someone return back the original color for constants? It's clashing with the green color. Not sure why this was done
I tried using this to return to old behavior and it doesn't work
"editor.semanticTokenColorCustomizations": {
  "rules": {
    // different color for all constants
    "*.readonly": "#9cdcfe",
  }
}

To get the old colors back you need to add the following to the settings:
    "editor.tokenColorCustomizations": {
        "[Default Dark+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#9CDCFE"
                    }
                }
            ]
        },
        "[Default Light+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#001080"
                    }
                }
            ]
        },
    },

To get the old colors back you need to add the following to the settings:
    "editor.tokenColorCustomizations": {
        "[Default Dark+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#9CDCFE"
                    }
                }
            ]
        },
        "[Default Light+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#001080"
                    }
                }
            ]
        },
    },

Thank you for a quick response. It worked

Just spend 30 minutes trying to fix this bug by reopening VSC then reinstalling it because I was sure that my coloring is broken.
Now I read that, this is a "feature".

To get the old colors back you need to add the following to the settings:
    "editor.tokenColorCustomizations": {
        "[Default Dark+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#9CDCFE"
                    }
                }
            ]
        },
        "[Default Light+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#001080"
                    }
                }
            ]
        },
    },

Thank you! It is unbelievable that WE as users have to make our own fixes around this new "feature". Though you guys at Microsoft would listen to us... :unamused:

Holy moly, I have color blindness, and after recent update, I thought it some kind of bug. You should  change color schemes with care. Reverting to old style

Holy moly, I have color blindness, and after recent update, I thought it some kind of bug. You should change color schemes with care. Reverting to old style

Exactly. I'm color blind too, so that's why I have major problem with this. I guess this feature hasn't been consulted with UX and hasn't been tested.
Second major bad feature for me in VSC in 2020. I wonder if it's beggining of downfall of VSC and some new "light, fresh" player should appear on market.

Leaving a comment here just for feedback. I feel a little too picky about this, but I spent more than an hour trying to figure out what was wrong with the const coloring. I thought it was a bug or some intrusive extension messing up my settings. Thanks for the "solution"!

Spent couple hours today reinstalling vscode, was sure its a bug. Had to go with color customization fix mentioned above to revert it back to normal colors.
Why would you add such "features" that break normal workflow for so many people? I'm wondering how many hours collectively developers who use vscode have wasted trying to work it around back to normal.

See #97373 for the discussion about improving the color.

To get the old colors back you need to add the following to the settings:
    "editor.tokenColorCustomizations": {
        "[Default Dark+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#9CDCFE"
                    }
                }
            ]
        },
        "[Default Light+]": {
            "textMateRules": [
                {
                    "scope": ["variable.other.constant", "variable.other.enummember"],
                    "settings": {
                        "foreground": "#001080"
                    }
                }
            ]
        },
    },

Thank you! It is unbelievable that WE as users have to make our own fixes around this new "feature". Though you guys at Microsoft would listen to us... 😒

This is awesome. I love you man. I was going nuts with the new coloring

The issues with this:

It provides very little value. I don't really care whether a variable is a const or not. In the cases where I do, I will get feedback that it's a const very quickly anyway.
It's hard to parse and is confusing. By making every little thing have a different color, it ends up being very hard to remember that color X stands for Y thing. As a result, it just confuses you because you're looking at rainbow-colored text. Different colors should stand for very significant differences where it makes it easier to read text than harder. (See how I used italics for specific words to enhance my point? If the whole text was a mixture of bold and italics, it would be very hard to read.)
The color does not fit into the theme. The contrast against the dark background is not good enough in my opinion, even though you claim that it satisfies some standard. The usual (mutable) variable color works really well against the dark background, I prefer it highly over this color. Most of my variables are constants, so this is a serious eyesore.


Automatically deploy a docker image

see https://dev.to/cloudx/multi-arch-docker-images-the-easy-way-with-github-actions-4k54


laststatus + redraw! causes external command output to be highlighted with StatusLine group

Steps to reproduce

Create reproduce.vim:set laststatus=2
redraw!
!echo output

Run vim --clean -u reproduce.vim /tmp/blah

Expected behaviour
Highlighting of the command output should not be highlighted with StatusLine group:

Version of Vim
Vim 8.2.4324 (Latest MacPorts package) and Vim 8.2.4701 (git HEAD)
Environment
OS: macOS 11.6.5
Terminal: tested on iTerm, Terminal.app, xterm
$TERM: xterm-256color
Shell: Bash 3.2.57
Logs and stack traces
No response

A little more background: I was creating a cabbrev to call sudo and encountered this issue, only in non-GUI vim.  To clear the abbreviation before the password prompt, I executed redraw!, but this resulted in the command output being highlighted with StatusLine group. With my full vimrc, sudo tee is the only external command I have found that triggers this.
" With full vimrc, this has highlight issue
redraw! | execute 'w !sudo tee /dev/null > /dev/null'
" Executing `syntax enable` is a simple workaround, but doesn't work for the minimal vimrc above:
redraw! | syntax enable | execute 'w !sudo tee /dev/null > /dev/null'


Update cassandra, clickhouse, cockroachdb, ... to 1.20.3

About this PR
📦 Updates

org.testcontainers:cassandra
org.testcontainers:clickhouse
org.testcontainers:cockroachdb
org.testcontainers:couchbase
org.testcontainers:db2
org.testcontainers:dynalite
org.testcontainers:elasticsearch
org.testcontainers:gcloud
org.testcontainers:influxdb
org.testcontainers:jdbc
org.testcontainers:kafka
org.testcontainers:localstack
org.testcontainers:mariadb
org.testcontainers:milvus
org.testcontainers:minio
org.testcontainers:mockserver
org.testcontainers:mongodb
org.testcontainers:mssqlserver
org.testcontainers:mysql
org.testcontainers:neo4j
org.testcontainers:nginx
org.testcontainers:oracle-xe
org.testcontainers:orientdb
org.testcontainers:postgresql
org.testcontainers:presto
org.testcontainers:pulsar
org.testcontainers:rabbitmq
org.testcontainers:redpanda
org.testcontainers:selenium
org.testcontainers:solr
org.testcontainers:testcontainers
org.testcontainers:toxiproxy
org.testcontainers:trino
org.testcontainers:vault

from 1.20.2 to 1.20.3
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.testcontainers" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.testcontainers" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #384.


msalInstance.getAccountByHomeId is deprecated.ts

Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.3.0
Wrapper Library
MSAL Node Extensions (@azure/msal-node-extensions)
Wrapper Library Version
None
Public or Confidential Client?
Public
Description
Getting The signature '(homeAccountId: string): AccountInfo | null' of 'msalInstance.getAccountByHomeId' is deprecated.ts(6387), in "@azure/msal-browser": "^3.3.0". There is no issue with "@azure/msal-browser": "^3.1.0".
Error Message
The signature '(homeAccountId: string): AccountInfo | null' of 'msalInstance.getAccountByHomeId' is deprecated.ts(6387)
PublicClientApplication.d.ts(131, 8): The declaration was marked as deprecated here.
(method) PublicClientApplication.getAccountByHomeId(homeAccountId: string): AccountInfo | null
Returns the signed in account matching homeAccountId. (the account object is created at the time of successful login) or null when no matching account is found
@param homeAccountId
@returns — The account object stored in MSAL
@deprecated — - Use getAccount instead
Msal Logs
No response
MSAL Configuration
CLIENTID=****
AUTHORITY=https://login.microsoftonline.com/****

Relevant Code Snippets
// Sign out user
  function signOut(accountId: string) {
    const account = accountId
      ? msalInstance.getAccountByHomeId(accountId)
      : null;
    if (account) {
      msalInstance.logoutRedirect({
        account,
      });
      localStorage.clear();
    } else {
      console.error("Account not found");
    }

Reproduction Steps
While adding plugins in Nuxt 3
Expected Behavior
It should get logout.
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Edge
Regression
@azure/msal-browser 3.3.0
Source
Internal (Microsoft)

@ashkumarverma the getAccountByHomeId() API was marked for deprecation as of v3.3.0, but it is still available so it should work unless your project configuration doesn't allow using deprecated functions. MSAL doesn't actually throw an error for this.
You have two options to fix this:

(Recommended): Migrate to the new getAccount() API:

// Sign out user
  function signOut(accountId: string) {
    const account = accountId
      // New getAccount API allows you to pass in a filter
      ? msalInstance.getAccount({ homeAccountId: accountId })
      : null;
    if (account) {
      msalInstance.logoutRedirect({
        account,
      });
      localStorage.clear();
    } else {
      console.error("Account not found");
    }

Configure your application to ignore the deprecation warning.