Selecting columns

Since '*' is not allowed in query interface  a selection of multiple columns, preferably with separating ',' when put into query box,  should be possible.

'*' query is working now


docusaurus start command shows DeprecationWarning: The punycode module is deprecated.

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
When starting a dev server of the latest version of Node (v22.1.0) and Docusaurus (v3.3.2) with npm start (docusaurus start) I'll get the following warning:
DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.

This is due to the fact that docusaurus/core has serve-handler as a dependency.
And serve-handler itself depends on fast-url-parser which seems to be the root cause of this warning.
Is there anything Docusaurus can do to fix this or does the serve-handler project have to refactor its code from fast-url-parser to Node's native url module instead?
Reproducible demo
No response
Steps to reproduce
npx create-docusaurus@latest my-website classic
cd my-website
npm run start

Expected behavior
Don't show any warnings in the console.
Actual behavior
When starting a dev server of the latest version of Node (v22.1.0) and Docusaurus (v3.3.2) with npm start (docusaurus start) I'll get the following warning:
DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.

Your environment
No response
Self-service

[ ] I'd be willing to fix this bug myself.

Thanks
Normally we'd wait for serve-handler to update and fix the problem. Unfortunately, I doubt serve-handler is well-maintained these days, and not sure a fix will be published. We'd probably have to patch it ourselves.

It's a bit risky to change server implementation in a minor release, but we might drop serve-handler in a major if we find a good alternative. I don't know the current landscape of alternatives to serve a static deployment.
There's Nitro, but its primary use-case does not look like to be static deployments, although it could be interesting in the future if we want to add support for Docusaurus server-side features (do we?).

@slorber I agree that serve-handler is not well-maintained anymore. But also don't know of any good alternatives.

[...] if we want to add support for Docusaurus server-side features (do we?).

I would absolutely love to see Docusaurus moving into this direction (as long as they stay optional).
With server-side features there would be endless possibilities to make Docusaurus way better than it already is.

Is this anything to worry about or can I just ignore this warning for my docusaurus site?

Encounter the same problem too. If you are using pnpm as the package manager, simply run pnpm patch<EMAIL_ADDRESS>and update the require('punycode') to require('punycode/'), then run pnpm patch-commit ... to solve it temporarily.
More details: https://github.com/petkaantonov/urlparser/issues/20.


TextModelPart is disposed!: Error: TextModelPart is disposed!

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.85.2
OS Version: Linux garg10may 6.5.0-14-generic 14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Steps to Reproduce:

When I press CTRL + J in the editor window
I have vim extension and various manual key binding like \t to open terminal. When I press CTRL + J being in terminal it hides it, but when in editor it does nothing. Using \t key binding I transfer myself to terminal.

32024-01-26 18:20:10.174 [error] TextModelPart is disposed!: Error: TextModelPart is disposed!
    at f.g (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:121:22521)
    at f.getWordAtPosition (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:629:119736)
    at q.getWordAtPosition (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:736:9052)
    at L.h (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:68579)
    at new l (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:68454)
    at new L (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:69323)
    at P (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:69855)
    at T.F (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:74429)
    at T.E (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:74226)
    at new T (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:70825)
    at q (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:75301)
    at o.value (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:75446)
    at u.y (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at u.z (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at u.fire (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at x.setModel (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:744:400)
    at y.setInput (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:2148:11654)
    at async y.setInput (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:2152:6719)
2024-01-26 18:20:37.550 [error] TextModelPart is disposed!: Error: TextModelPart is disposed!
    at f.g (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:121:22521)
    at f.getWordAtPosition (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:629:119736)
    at q.getWordAtPosition (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:736:9052)
    at L.h (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:68579)
    at new l (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:68454)
    at new L (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:69323)
    at P (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:69855)
    at T.F (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:74429)
    at T.E (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:74164)
    at o.value (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:760:70608)
    at u.y (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at u.z (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at u.fire (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at x.setModel (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:744:400)
    at y.setInput (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:2148:11654)
    at async y.setInput (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:2152:6719)

You can run Developer: Toggle Keyboard Shortcuts Troubleshooting to figure out what keybindings are happening for you.

2024-01-27 14:43:19.975 [error] Cannot read properties of undefined (reading 'data'): TypeError: Cannot read properties of undefined (reading 'data')
    at /home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:139734
    at _0x1be708 (/home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:152918)
    at ve.provideCompletionItems (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:143:53055)
2024-01-27 17:18:16.836 [error] Cannot read properties of undefined (reading 'data'): TypeError: Cannot read properties of undefined (reading 'data')
    at /home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:139734
    at _0x1be708 (/home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:152918)
    at ve.provideCompletionItems (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:143:53055)
2024-01-27 17:56:47.051 [error] Cannot read properties of undefined (reading 'data'): TypeError: Cannot read properties of undefined (reading 'data')
    at /home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:139734
    at _0x1be708 (/home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:152918)
    at ve.provideCompletionItems (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:143:53055)
2024-01-27 17:56:52.742 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.python' wants API proposal 'registerIssueDataProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2024-01-27 17:56:53.142 [info] Started local extension host with pid 1416552.
2024-01-27 17:56:56.802 [info] [perf] Render performance baseline is 27ms
2024-01-27 18:45:12.581 [error] Cannot read properties of undefined (reading 'data'): TypeError: Cannot read properties of undefined (reading 'data')
    at /home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:139734
    at _0x1be708 (/home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:152918)
    at ve.provideCompletionItems (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:143:53055)
2024-01-27 18:51:46.059 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.python' wants API proposal 'registerIssueDataProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2024-01-27 18:51:46.433 [info] Started local extension host with pid 1511824.
2024-01-27 18:51:50.269 [info] [perf] Render performance baseline is 30ms
2024-01-27 18:52:32.097 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.python' wants API proposal 'registerIssueDataProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2024-01-27 18:52:32.507 [info] Started local extension host with pid 1513196.
2024-01-27 18:52:36.268 [info] [perf] Render performance baseline is 31ms
2024-01-27 19:03:27.201 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.python' wants API proposal 'registerIssueDataProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2024-01-27 19:03:27.581 [info] Started local extension host with pid 1532264.
2024-01-27 19:03:31.431 [info] [perf] Render performance baseline is 28ms
2024-01-27 19:20:10.073 [error] Cannot read properties of undefined (reading 'data'): TypeError: Cannot read properties of undefined (reading 'data')
    at /home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:139734
    at _0x1be708 (/home/garg10may/.vscode/extensions/ms-python.vscode-pylance-2023.12.1/dist/extension.bundle.js:1:152918)
    at ve.provideCompletionItems (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:143:53055)
2024-01-27 22:08:53.537 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-python.python' wants API proposal 'registerIssueDataProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2024-01-27 22:08:53.862 [info] Started local extension host with pid 1851618.
2024-01-27 22:08:57.575 [info] [perf] Render performance baseline is 32ms
2024-01-27 22:13:36.202 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-01-27 22:13:36.203 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-01-27 22:13:36.203 [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control
2024-01-27 22:13:36.203 [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl')
2024-01-27 22:13:36.204 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-01-27 22:13:36.330 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-01-27 22:13:36.330 [info] [KeybindingService]: | Resolving ctrl+[KeyC]
2024-01-27 22:13:36.331 [info] [KeybindingService]: \ From 7 keybinding entries, matched extension.vim_ctrl+c, when: editorTextFocus && vim.active && vim.overrideCtrlC && vim.use<C-c> && !inDebugRepl, source: user extension vscodevim.vim.


Gossip custom message data

We can add a field to the message format that can be used to gossip custom data. We can have an extra field that can be a hashmap. Users can serialize anything into the map.

This is will be a good idea. Similar Akka is doing this.

Yes thinking through this though I am not sure if the gossiper is the right place to exchange data. Where does the gossiper and the database/service using the gossiper begin?

Agreed that gossip is not the right protocol to exchange data. This would put additional constraints on the protocol to deal with things like consistency etc. However, there might be a good to provide additional node meta data that a client wants to exchange.
Akka adds version to do some optimization for version https://gist.github.com/jboner/7692270

One of the reasons I found/put together this library was I was building my own no-sql https://github.com/edwardcapriolo/nibiru. So I was thinking the place to do things like this would be in there.

Are you thinking about continuing this library, i.e. gossip?

Yes. We can go on with the library. But I think a eventually consistent CRDT structure is something closer to a NoSQL database than a gossip library.

for sure and that would not make sense to add to this library.


Multi-regional not required

Hi team - great work with this repo, the amount of work is truly extraordinary. I was just wondering, we are not in need of multi-region support. Is there a way that this repo can support that without just resorting to activating only one region that permanently has a /cc/ in the URL structure? Conscious that there are many files dependent on region and countryCode props etc.
Thanks

@GXM245, do you also only intend to have a single country in that region?
If you want to have a single region with a single country and not have that reflected in the URL structure, you would need to modify the code.


Portal is overriding the lazy loaded sibling after hydration under specific conditions

Describe the bug
If I use a component like below inside a For,  after hydration it renders the Portal but not the lazy component.   See the reproduction to see it happen.
<>
  <Lazy />
  <Portal>Portal</Portal>
</>

The workaround is to use a div instead a fragment, or wrap either the portal or the lazy component in a div.

Screenshots or Videos
No response
Platform

Browser: Chrome
Version: solid-js 1.6.4

Additional context
No response

Thanks for reporting. This is an issue with how Portal works. It doesn't really hydrate properly. Which I figured was fine since it doesn't really work during SSR. Like you can't portal into nothing. There is a mechanism to make it delay client render immediately after hydration but it doesn't take into account the havoc the marker (we use to lookup the parent for event delegation) causes on hydration. I need a new approach.


Let people unassign themselves from shifts

Also let people unassign themselves.

Originally posted by @simonw in https://github.com/natbat/pillarpointstewards/issues/8#issuecomment-1069542630

Re-opening until I have added tests.


Store locally referenced templates properly

Locally referenced templates cannot be executed successfully because the reference is not found in stored templates but found local templates still need to be resolved. Here's an example that reproduces the issue besides examples/workflow-template/local-ref.yaml.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: argo-dag-
spec:
  entrypoint: dag
  templates:
  - dag:
      tasks:
      - name: task1
        template: container1-proxy
    name: dag
  - name: container1-proxy
    template: container1
  - container:
      image: python:alpine3.6
      command: [python, -c]
      args: ["import sys; sys.exit(0)"]
    name: container1

This PR will fix #1672


When initializing a response it should throw if status is not in the range 200 to 599

From the spec https://fetch.spec.whatwg.org/#response-class

To initialize a response, given a Response object response, ResponseInit init, and an optional body with type body, run these steps:
 1. If init["status"] is not in the range 200 to 599, inclusive, then throw a RangeError.
 2. If init["statusText"] does not match the reason-phrase token production, then throw a TypeError.
 [...]
 6. If body was given, then:
      1. If response’s status is a null body status, then throw a TypeError.
      [...]

Reproduction
new Response('body', { status: 204 }); // KO Not throwing
new Response(undefined, { status: 204 }); // Not throwing is correct here
new Response(undefined, { status: 0 }); // KO Not throwing

Expected behavior
Under Chrome 107:
new Response('body', { status: 204 });
// TypeError: Failed to construct 'Response': Response with null body status cannot have body

new Response(undefined, { status: 204 });
// No throwing

new Response(undefined, { status: 0 });
// RangeError: Failed to construct 'Response': The status provided (0) is outside the range [200, 599].

Your Environment

software
version

node-fetch
3.3.0

node
18.12.1

npm
8.19.2

Operating System
macOS Monterey

If this issue is open and no one is working on it, i would like to work on it

@asingh04 PR welcome! 🙌


Revert "feat(rule): add secrets rule"

Reverts camunda/bpmnlint-plugin-camunda-compat#116
reason : https://github.com/camunda/bpmnlint-plugin-camunda-compat/pull/116#issuecomment-1678758361

Done on main. Thanks.


Add new method hasNot() to Collection.

Add same convenience as is provided by isNotEmpty() for isEmpty() to has().

Collections aren't entirely meant to encase single objects so will hold off for now.

@taylorotwell I don't understand what this has to do with encasing objects. The added method in this PR is just the negation of the already available has() method.

For me has() and isEmpty() dont have the same logic, so no need to be consistent with it.


Using "get_theme_X" methods fail to retrieve theme property when type variation is set on Godot v4.2.x

Tested versions

Reproducible in v4.2 starting with commit 58126e479cd7341ec2ae306131e14868bcff06ca @YuriSizov
Not reproducible in v4.1.3 and versions prior to commit listed above after using git bisect

System information
Godot v4.2.1.stable (b09f793f5) - Fedora Linux 39 (Workstation Edition) - Wayland - GLES3 (Compatibility) - AMD Radeon Graphics (radeonsi, gfx1103_r1, LLVM 17.0.6, DRM 3.54, 6.6.13-200.fc39.x86_64) () - AMD Ryzen 7 7840U w/ Radeon  780M Graphics (16 Threads)
Issue description
Using any get_theme_X method (e.g. get_theme_icon) on a Control node with a theme variation returns an empty/invalid value. This issue goes away if you remove the theme variation property on the Control node.
For example, from the MRP, this scene has two Texture2D nodes with the same script below:
@tool
extends TextureRect

func _ready() -> void:
	theme_changed.connect(_on_theme_changed)
	_on_theme_changed()

func _on_theme_changed() -> void:
	var icon := get_theme_icon("highlight", "CustomType") as Texture2D
	if not icon:
		return
	texture = icon

One has its theme variation property set, while the other does not, which creates this result:

This issue does not appear in Godot v4.1.3 or versions prior to commit 58126e479cd7341ec2ae306131e14868bcff06ca.
Steps to reproduce
You can run the provided MRP project to reproduce the issue.
The gist is:

Create a theme with a custom type and theme item on that custom type
Set the root Control node to use the theme
Create a child Control node and set the theme variation property to use the created custom theme type
Call any get_theme_X method (e.g. get_theme_icon) to get the theme property

Minimal reproduction project (MRP)
ThemeIssue-MRP.zip

You don't have this type defined as a type variation in your theme resource. It needs to have a base type configured, and that type must be compatible with the control node's type which you use it on.
Around the commit that you link to the bug was fixed where this was not checked properly.

Thanks for your response! I did confirm that configuring the base type does indeed resolve this particular issue:

This change did break theming in my project, but it shouldn't be too difficult for me to add the base types to all type variations. Maybe as a feature the editor should display a warning if there is a type variation defined without a base type configured? This issue could effect others upgrading to v4.2 from v4.1.


Provide user-input validation

As per a discussion with @jugonzal07, Copper should provide some degree of user-input validation.
Examples:

Do not attempt to run if the input reference capacity of a chiller is 0 or negative
Do not attempt to run if the input targeted full load efficiency or part load efficiency of a chiller is 0 or negative

I added a json schema so I'll make it it's own branch and submit a pull request with that in the next week or so.
Schemas are so nice for input validation.

Addressed in #72.


Most subcommands depend on configuration file

headscale command currently need a configuration file for all subcommands. It's useless now, since clients talk to server through a socket. Only the headscale serve should need the full configuration file.

We are going there, but have not had time to sort it out yet.
You should probably be able to set the Unix socket path via env var and not have to have a config.


Article link broken on readme.md page

This link is broken on the readme:
Introducing an Accessible HTML5 Video Player
https://www.paypal-engineering.com/2014/09/05/introducing-an-accessible-html5-video-player/
Is the PayPal Engineering blog its articles gone? Tried searching and couldn't find a new location.
If gone, suggest marking as such and adding this post:
https://paulschantz.com/2015/03/06/7-lessons-from-developing-an-accessible-html-5-video-player/

Sure. you want to send a PR with it?
@deque-dennis is this a new profile for you?

So it's gone then, too bad.
I'll submit a PR soon.
Yes, it's me (dennis/weboverhauls); I created this from my other account by mistake :-)

It appears that the PayPal Engineering blog is back online.


added google analytics tracking to the theme and github

@idmontie and @bryanbarker checkout https://github.com/igrigorik/ga-beacon


Projects deprecated

Current projects are deprecated. The due dates have passed and there is no update in the achieved goals.
I think that the benefits of having a project for each discrete goal is a bit overkill for a team of three persons, who communicate in a daily basis. The time needed to create them, explain them and keep them updated could be used efficiently for coding.
I propose we abandon the idea of having them. If we need something for internal tasks management, we could use one single project, containing smaller tasks that could be frequently passed among the cards (TODO, Done, In progress).

The flat pages can be cancelled, I think we've settled on independent applications.
Internationalization can stay, at least to outline Stage 3.
I wasn't planning on writing any more projects so :+1: in general.


Migrations and existing databases

Something like https://msdn.microsoft.com/en-us/data/dn579398

https://docs.microsoft.com/en-us/ef/core/get-started/full-dotnet/new-db
Hello, I created an SQLite database following these tutorials for a console .net core app and works like a charm with child classes and I really love all these coding advances.
I have a doubt trying to upgrade the SQLite database based on models:
1.- I create my models
2.- I use Add-Migration MyFirstMigration
3.- db.Database.Migrate(); add all the data and save changes
4.- I update the model with more properties.
5.- What exactly do I have to do now to update the SQLite database? delete migrations folder? add-migration again? Update-Database? and in code what do I have to call to create new columns?
I have tried to understand and try several ways keeping the current data but I cannot make it work.
Really thank you, it is a real advance for my apps. (A really cool new one for UWP soon :)).
(meanwhile it is effortless to upgrade it in an SQLite editor, but would be great to understand for more complex scenarios).

Consolidating with #204

Reopening since I'm closing #204 without this.


[Feature] HttpClient Listener rewritten for performance

HttpClient Listener rewritten for performance
For HttpClient, we built a new from-the-ground-up managed HttpClientHandler called SocketHttpHandler. As you can likely guess, it’s a C# implementation of HttpClient based on .NET sockets and Span.
The biggest win of SocketHttpHandler is performance. It is a lot faster than the existing implementation. There are other benefits:
Elimination of platform dependencies on libcurl (for linux) and WinHTTP (for Windows) – simplifies both development, deployment and servicing
Consistent behavior across platforms and platform/dependency versions.
You can opt-in to using the SocketHTTPHandler in one the following ways with Preview 1:
Environment variable: COMPlus_UseManagedHttpClientHandler=true
AppContext: System.Net.Http.UseManagedHttpClientHandler=true
Still Needed:

[ ] Content Types
[ ] Table of Contents
[ ] Prioritization

If you know someone who can provide feedback, use '@' to ask them to review.

Let's just add this to the what's new topic: https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-2-1


⚠ Bofrost.es has degraded performance

In 73bc6d6, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1414 ms

Resolved: Bofrost.es performance has improved in c98bef7.


lmp: 1.0 -> 1.1

Motivation for this change
https://github.com/0xInfection/LogMePwn/releases/tag/v1.1
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 151236 run on x86_64-linux 1

1 package built:

lmp


FAQ: Updates for changed exposure check strategy

Where to find the issue
FAQ Link
-- |
https://www.coronawarn.app/en/faq/#multiple_exposure_checks
https://www.coronawarn.app/en/faq/#exposure_check
https://www.coronawarn.app/en/faq/#risk_update_24
and corresponding https://www.coronawarn.app/de/faq/ German language articles.
Describe the issue
According to the blog article Corona-Warn-App Version 1.7 can perform the exposure check several times a day the exposure check strategy has changed with the release of CWA V1.7. This makes the text of several FAQ articles out of date.
The article says:
"With Corona-Warn-App Version 1.7, the exposure check can be run several times a day so that users are informed about possible risk encounters sooner. This repeated daily check is performed automatically. However, it requires a Wi-Fi connection. The standard daily exposure check is still performed once a day, no matter if the smartphone is connected to a Wi-Fi network or not."

FAQ Link
Current text (partial extract)

https://www.coronawarn.app/en/faq/#multiple_exposure_checks
It is therefore not an error   that multiple, seemingly simultaneous entries are visible in the exposure   check history. (See also https://github.com/corona-warn-app/cwa-website/issues/578.)

https://www.coronawarn.app/en/faq/#exposure_check
When the app was running   constantly during the last two weeks, you should see 14 checks within the   last 24 hours.

https://www.coronawarn.app/en/faq/#risk_update_24
Updating only around every 24   hours is due to API restrictions and to ensure consistency between the   Corona-Warn-App versions for iOS and Android.

Suggested change

Review each of the articles and modify the text so that it agrees with the blog.
Check that the detailed behavior of the app is described correctly for the currently released version.

See also: #628

@Ein-Tim

See also: #628

Whoops! Somehow I missed this new issue. I will close my issue and add the information to the existing issue.


Feature request - silent errors

Whenever trackers are having downtime, an intrusive dialog box pops up with the appropriate error message. If multiple trackers are down then there's multiple alerts per IMDB tab. With multiple IMDB tabs, this can get pretty annoying. I'd like to request a feature that could be enabled in the options, where instead of displaying an alert with the error, the tracker abbreviation would just show up differently. For example strikethrough+italics, or strikethrough+red, or something else like that.
That's all that would be needed for the feature, but an extra-smooth way of implementing this would be to display the error in a tooltip when the user mouses over the tracker abbreviation.
As a "workaround" to stop the annoyance during longer downtimes (recently AHD for a few days, or TehC intermittently throughout the day) I just removed this section from the userscript:
		onerror: function(response) {
			alert('Call to ' + search_url + ' for ' + link_text + ' failed with status ' + response.statusText + '.\n' +
			'Please go to the URL in your browser and make sure it is valid.');
		},

I definitely see what you mean, I threw that in there mostly to catch sites with self-signed HTTPS certificates that would otherwise just not show up. I'll probably go with the strike-through+red, to be eye-catching but ignorable.

Finally had an opportunity to test it - works great! Much less annoying than before.


Added installation steps via helm charts.

Fixed https://github.com/istio/istio.github.io/issues/412

I signed it!

Jenkins job istio.github.io/presubmit passed

Thanks @ldemailly , how about make this on top of the installation page, so  that if people want a simple installation steps, they can just goto helm without reading the whole manual installation steps.

The page you want to link https://github.com/kubernetes/charts/tree/master/incubator/istio
says:

with "here" being https://istio.io/docs/tasks/installing-istio.html#installation-steps which is this page, thus we would create a loop with your change
Can you first change https://github.com/kubernetes/charts/tree/master/incubator/istio to be self contained (and reference this page as "manual steps" if you want) ?
or again we can add a new section but not at the top - it'll show up in table of content box:

Posted a PR in to fix istio helm chart https://github.com/kubernetes/charts/pull/1496 @ldemailly

Please remove the separate header and instead add the single paragraph:
You can use the [istio helm chart](https://github.com/kubernetes/charts/tree/master/incubator/istio) to install, or follow the steps below:

ping @gyliu513

Jenkins job istio.github.io/presubmit passed

@gyliu513 thanks for make some of the changes, though I'm not exactly in love with the "manual install" part (should probably be "manual installation", install is a verb (or a colloquial noun/abbrev)
I'll defer to @geeknoid to PTAL

ps: avoid doing force pushes as it erases the history in github

Jenkins job istio.github.io/presubmit passed

Removed the update to istio auth, thanks @ldemailly


New image: auth utils

Related Issues
Related: https://jira-hq.paloaltonetworks.local/browse/CIAC-861
Description
New image based on the demisto/crypto, grouping the following auth-related images:
azure-kusto-data
winrm
ssl-analyze
akamai
pyjwt3
pydantic
uptycs
oauthlib

121.64 mb size

should be used in the following yml files:
Packs/Akamai_SIEM/Integrations/Akamai_SIEM/Akamai_SIEM.yml
Packs/Akamai_WAF/Integrations/Akamai_WAF/Akamai_WAF.yml
Packs/ApiModules/Scripts/ZoomApiModule/ZoomApiModule.yml
Packs/AzureDataExplorer/Integrations/AzureDataExplorer/AzureDataExplorer.yml
Packs/Box/Integrations/BoxEventsCollector/BoxEventsCollector.yml
Packs/Box/Integrations/BoxV2/BoxV2.yml
Packs/Cylance_Protect/Integrations/Cylance_Protect_v2/Cylance_Protect_v2.yml
Packs/GitHub/Integrations/GitHub/GitHub.yml
Packs/Infinipoint/Integrations/Infinipoint/Infinipoint.yml
Packs/JWT/Integrations/JWT/JWT.yml
Packs/Jira/Integrations/JiraV2/JiraV2.yml
Packs/Keyfactor/Integrations/Keyfactor/Keyfactor.yml
Packs/Malwarebytes/Integrations/Malwarebytes/Malwarebytes.yml
Packs/MicrosoftCloudAppSecurity/Integrations/MicrosoftDefenderEventCollector/MicrosoftDefenderEventCollector.yml
Packs/MicrosoftDefenderAdvancedThreatProtection/Integrations/Microsoft365DefenderEventCollector/Microsoft365DefenderEventCollector.yml
Packs/MicrosoftManagementActivity/Integrations/MicrosoftManagementActivity/MicrosoftManagementActivity.yml
Packs/Pcysys/Integrations/Pcysys/Pcysys.yml
Packs/Silverfort/Integrations/Silverfort/Silverfort.yml
Packs/Troubleshoot/Scripts/CertificatesTroubleshoot/CertificatesTroubleshoot.yml
Packs/Uptycs/Integrations/Uptycs/Uptycs.yml
Packs/WinRM/Integrations/WindowsRemoteManagement/WindowsRemoteManagement.yml
Packs/Zoom/Integrations/Zoom/Zoom.yml
Packs/Zoom/Integrations/ZoomEventCollector/ZoomEventCollector.yml
Packs/Zoom/Integrations/Zoom_IAM/Zoom_IAM.yml

@ilappe lets try to add the new images to native image support


Regular Update for Dependencies

User Story - Business Need
We wish to keep dependencies up to date so we do not need such massive overhauls of our system. This is a recurring task to update all dependencies we are able to update. Any conflicts shall get a dedicated ticket. This task should be a day of work at most because it only updates non-breaking changes.

[ ] Ticket is understood and QA has been contacted

User Story
As VA Notify,
I want to keep our service up to date
So that we are secure and as free of bugs as possible.
Additional Info and Resources

Relevant section of README.md
Troubleshooting tips:

When looking at changes in poetry.lock, revert major changes, then minor, then patch/security

Engineering Checklist

[ ] Open "Tech Debt" issues reviewed to identify packages already known to have breaking changes (don't try to upgrade these)
[ ] Review open Dependabot PRs to determine where the changes will take place. You may need to rebase older PRs.  The PRs explain how to do this.
[ ] Update performed per the README.md
[ ] Dependabot PRs updated.  (They should automatically close if a given dependency was upgrade at least to the version given by the PR.)
[ ] Passes all tests locally
[ ] Passes QA Suite regression testing against Dev
[ ] If there are any failures, compare the poetry.lock in master against your local poetry.lock.

[ ] Identify the descrepancies and lock those versions in pyproject.toml, create a ticket, and label it "tech debt"
[ ] Any non-top level dependencies that have to be locked should have a comment added to pyproject.toml and have a checkbox to remove that dependency from pyproject.toml in the acceptance criteria
[ ] Created ticket has the package name in the title

Acceptance Criteria
Repo dependencies are updated and we have no broken functionality. Issues opened by Dependabot are resolved. Tickets with the "tech debt" label created for any updates we could, or should, not do.
QA Considerations

[ ] Check to see if these updates cancel out any Twistlock issues
[ ] QA Regression tests pass after deploying this code.

@cris-oddball just noting you wanted to update this ticket and template

The upgrade to protobuf failed, I've added a ticket.

PR approved and merged. Deploying to Perf.

Everything deployed to Perf just fine, dependabot issues closed, twistlock exceptions removed, sending to Staging.


Location hierarchy formatting issues

The source-data/location_hierarchy.tsv file contains some issues where

some rows only have 3 columns instead of 4 (which GitHub currently points out when you view this file in the browser), i.e. a missing final tab
some rows have 5 columns instead of 4, i.e. a surplus final tab

This bug was discovered when seemingly duplicate location hierarchies were appearing in Slack notifications describing them as new region-country-division-location combinations.
To prevent future formatting issues with the manually updated location hierarchy file, I suggest adding a script like bin/clean-location-hierachy that either

does some bash magic (something like cut -f1-4 source-data/location-hierarchy.tsv to grab only the first four columns, then something else I haven't quite figured out to add a trailing tab to rows missing the 4th column -- awk and gsub()?), or
loads it into pandas and print it back out again with only 4 columns, tab-delimited.

I also suggest sorting the file on region, country, division, and location in case a row is misplaced.
This cleaning script should be added to the ingest scripts.

Just had a thought maybe we should make this a new workflow to run whenever there's a push to source-data/location_hierarchy.tsv instead of within the ingest scripts.

Just had a thought maybe we should make this a new workflow to run whenever there's a push to source-data/location_hierarchy.tsv instead of within the ingest scripts.

That's a great idea!

We could also add an option to the script to add in the the output from the slack location hierarchy additions file so that you could run it locally to add those new location hierarchies and then manually remove the wrong ones or duplicates (there will be fewer duplicates with this clean up script included in automation) instead of manually adding the correct new ones.
Sorry if this belongs better in https://github.com/nextstrain/ncov/pull/455

We could also add an option to the script to add in the the output from the slack location hierarchy additions file so that you could run it locally to add those new location hierarchies and then manually remove the wrong ones or duplicates (there will be fewer duplicates with this clean up script included in automation) instead of manually adding the correct new ones.
Sorry if this belongs better in nextstrain/ncov#455

So if I understand correctly, you're suggesting an automated way of appending the new location hierarchies to source-data/location_hierarchy.tsv? Thus saving copy/pasting by build maintainers?
In general, I'm very interested in learning of more ways to improve the nCoV build maintenance workflow. IMO such a feature doesn't thematically fit within a "cleaning" script, but it could influence the overall solution that resolves this issue since sorting would have to occur after appending to the location hierarchy. So, thanks for bringing it up here! I haven't looked at nextstrain/ncov#455, but I think this repo, perhaps under a new issue, is a fine place for this discussion.

So if I understand correctly, you're suggesting an automated way of appending the new location hierarchies to source-data/location_hierarchy.tsv? Thus saving copy/pasting by build maintainers?

@kairstenfay exactly, and perhaps this is not top on the list in terms of potential time saved by automating things currently achieved by copy/pasting. I'll open a new issue anyway. Thanks!

@kairstenfay exactly, and perhaps this is not top on the list in terms of potential time saved by automating things currently achieved by copy/pasting. I'll open a new issue anyway. Thanks!

Thanks for taking the initiative on that. Perhaps the feature you described could fit in the new location hierarchy workflow @joverlee521 proposed.

@kairstenfay exactly, and perhaps this is not top on the list in terms of potential time saved by automating things currently achieved by copy/pasting. I'll open a new issue anyway. Thanks!

Thanks for taking the initiative on that. Perhaps the feature you described could fit in the new location hierarchy workflow @joverlee521 proposed.

I think naming the new script and/or workflow "adjust location hierarchy" instead of "clean location hierarchy" would create a logical place for @eharkins's suggested feature to live.

My only concern with the automation is that it's important to be checking these new locations are reasonable - that the division is a division and the location is a location (it's not uncommon to get cities as divisions, for example). It makes things harder down the line when we end up with too much inconsistency in how we're dividing things  and what things are called.... I'm all for making things easier, but I would want to be sure we keep doing these checks rather than allowing everything to be added automatically!

I agree @emmahodcroft; I think it would make sense to clean tabs and sort location hierarchies in an automated workflow, but adding new ones should still be a manual process. Here's what I propose for adding new locations manually/locally:

Run cat location_hierarchy_additions.tsv >> location_hierarchy.tsv using the new location hierarchies from slack (this achieves what I was hoping for assuming you correct errors in the steps below)
Run the sorting and tab clean up script being discussed here on location_hierarchy.tsv
Manually check that no bad hierarchies were added to location_hierarchy.tsv, removing duplicates, mispellings, and ensure

division is a division and the location is a location

Follow the normal protocol for adding the valid new locations to ncov/defaults/{color_ordering.tsv, lat_longs.tsv} and annotating invalid locations in ncov-ingest/source-data/gistad_annotations.tsv

I'd agree with this except I'd reverse the order - check the locations first in location_hierarchy_additions.tsv to ensure they're 'legit' and remove any that shouldn't be there - then cat, sort, and check the remaining 'good' ones. Otherwise it can be difficult to remember what's new, and to be sure you scrolled around, found it, and removed it.
Also important to remember do to this with the 'final' version of the file - after any changes to gisaid_annotations.tsv! Certainly for me yesterday this was key as the additions shrunk when I'd fixed up the sequences. This does reinforce being able to generate new location_hierarchy_additions.tsv files without necessarily re-running a build though!

While we are autosorting things, are there other files, e.g. gisaid_annotations.tsv that would be good to run basic sorting (and perhaps tab cleanup) on as well on push?

While we are autosorting things, are there other files, e.g. gisaid_annotations.tsv that would be good to run basic sorting (and perhaps tab cleanup) on as well on push?

Excellent point! I am happy to also adjust the annotations files if that is desirable among our build maintainers. We may want to do a one-time cleanup of duplicates in annotations files, though, before sorting them. I would guess we would keep the entry listed lower in the file in the event of a duplicate.

Would also be happy to do this!
One point is that we've kept the title and paper_url at the bottom half of the file just to make it easier for shepherds to add the other stuff at the top (Paul is exclusively working on adding papers, so this just keeps all that separate). So when sorting we would want to maintain that if possible.
Alternatively we could split the paper stuff out to an entirely separate file - I suggested this a while ago and meant to do it, but it hasn't come to pass yet. Would be happy for either solution! (The two files could then essentially be cat together before being passed to the scripts that ingest them, as there's no real difference between the two except for humans!)

We may want to do a one-time cleanup of duplicates in annotations files, though, before sorting them. I would guess we would keep the entry listed lower in the file in the event of a duplicate.

@kairstenfay removing duplicates sounds good, just in case they cause confusion or take up space. If we are removing exact duplicate annotations (all columns exactly the same), does it matter which one we keep?

One point is that we've kept the title and paper_url at the bottom half of the file just to make it easier for shepherds to add the other stuff at the top

@emmahodcroft if we were auto sorting them using a script on pushing to this repo, we could just stick any new annotations on the end of the file and they would get sorted into place by the script when we push, right? It still might be useful to be able to look for existing annotations in the file in addition to / in the process of appending new ones, but searching the file would be easier if it had been autosorted.
But if having the paper annotations potentially interleaved with the rest due to autosorting made life harder in a way I'm not getting, this seems like a good solution:

Alternatively we could split the paper stuff out to an entirely separate file - I suggested this a while ago and meant to do it, but it hasn't come to pass yet. Would be happy for either solution! (The two files could then essentially be cat together before being passed to the scripts that ingest them, as there's no real difference between the two except for humans!)

It's not a huge deal, except that the paper_url and title info is about 2/3 of the file right now. And generally, it's info we wouldn't ever be interested in browsing or looking into. So, it's just that if it was mixed in, then it would just be most of the lines, which makes general browsing or looking for 'actually interesting' information harder. As I said, probably not a huge deal, but probably also not a big deal to either separate these out and sort them then just print one after another, or split into two files :)

@kairstenfay would cleaning up and sorting annotations belong as an (optional) feature of this script https://github.com/nextstrain/ncov-ingest/blob/master/bin/check-annotations ?
As for location hierarchies it seems to make more sense to (as discussed above) create bin/adjust-location-hierarchy which runs upon pushing changes to source-data/location_hierarchy.tsv. Since https://github.com/nextstrain/ncov-ingest/blob/master/bin/check-locations seems like it creates the location-hierarchies-additions.tsv and is more geared toward the ingest workflow so it wouldn't be as good of a place for sorting and cleaning newly added locations. Sorry if that is obvious, just checking my interpretation makes sense as I orient myself more with the scripts in the repo.


[1.18.2] Electrum sword seems to have incorrect attack speed

While the vanilla swords all have a speed of 1.6, the electrum sword has a speed of 1.4, ever so slightly slower.

I could see a world where this is intentional, considering that electrum is considerably easier to obtain than netherite. However, if it is, it at least doesn't seem to fit with the theme of electrum being "fast" like the armor set.


 design

Shall we go for <section title> - Chrome Dev Summit?
So, Community Guidelines - Chrome Dev Summit, and the homepage is just Chrome Dev Summit.
Any objections @argyleink @surma @kosamari?

Wfm

Taking this as it has overlap with the calendar stuff.


fix issue #329

this commit to fix issue #329

Hi @yaanhyy! Thank you for your help :pray:! Our team has looked into the issue and indeed there is a way to optimize the load_account_tree for the witness_generator, but the provided solution is unfortunately not fully correct, our team will soon release the fix


$SkipToken and $Count to current sensitivity labels API [DO NOT MERGE]

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java

Can one of the admins verify this patch?

@igsiroti I haven't heard on this PR for a while, I'll close it for now and feel free to comment when you're ready to reopen for merging. Thanks!


Rework date selection

Unifiy SelectedDate into SelectedDates.
Separate how the user selects a date from what happens when the user selects a date. For example:

Separating SelectionMode.Single into SelectionType.Single and SelectionMode.Replace
Separating SelectionMode.Multiple into SelectionType.Single and SelectionMode.Modify
Separating SelectionMode.Range into SelectionType.Range and SelectionMode.Replace

The DateSelectionChanged event no longer works correctly due to an issue that could be fixed by jamesmontemagno/mvvm-helpers#83.


Access to parent field through __ does not work

In One to Many relations I was accessing Parent fields with __.
For example if Child had Parent then I can have:
list_display =['Parent__ParentField']
This does not seem to be working with django-material ModelViewSet

Yep, looks like it's requires to fix lookup procedure. I hope i would add this ti 2.0 only.
Currently this can be overcome by using custom method
    def parentfield(self, obj):
        return obj.parent.parentfield


Paraphrase ?...

Hi William
Is it possible to paraphrase some texts with your wrapper ?
I understood all functions you've implemented (it's great !) and it's possible I use it in next weeks for my personal use.
Great job !

Hey. You sure can. There's a few examples on the OpenAI site and one of them is in the examples folder. On the OpenAI playground I made this setup:

And it produced:

Elon Reeve Musk is a business magnate and entrepreneur who founded SpaceX, Tesla, Inc., The Boring Company, Neuralink, and OpenAI. He is also the co-founder of SolarCity and X.com. With an estimated net worth of around US$243 billion as of February 2022

So you can just replicate that setup with the wrapper.
Summarize for a 2nd grader example: https://beta.openai.com/examples/default-summarize
Notes to summary example: https://beta.openai.com/examples/default-notes-summary
The notes to summary example is available in the examples folder here: https://github.com/WilliamWelsh/OpenAI.Net/blob/main/samples/NotesToSummary/Program.cs

I'm gonna go ahead and close this after a month of no response, but like I said it's easily possible with the wrapper. Feel free to re-open if you need help.


typeof-like thing for functions, but change return-type to void

hi,
if i use typeof on a function, then it copies both the function-arguments-types and the return-type. is there a way to only copy the function-arguments-types, but make the return-type void?
example:
function a(x:string, y:number):number { ... }

type B = magicmagic a;
// at this point B is (string,number)=>void

the reason is Redux. it wraps functions and the wrapped-function has the same arguments as the original function, but the return-type gets changed to void.

i'm not sure how to do it with arbitrary number of params, but here's a somewhat buggy version:
type _VoidRet2<A, B, F: (A, B) => any> = (A, B) => void;
type VoidRet2<F> = _VoidRet2<*, *, F>;

declare var action: (string, number) => string;

(((a: string, b: number) => a): VoidRet2<typeof action>);
(((a: string, b: number) => undefined): VoidRet2<typeof action>);
(((a: string, b: string) => undefined): VoidRet2<typeof action>); // should be an error

it works, but is it recommended way?

@gabor Did you find a solution? I have the exact same problem with Redux.

It's possible
// @flow

function a(x: string, y: number): number { return 0 }

type $Arguments<F> = $Call<<A>(f: [(...args: A) => any]) => A, [typeof a]>

type F = (...args: $Arguments<typeof a>) => void

const hey: F = (a: number, y: string) => { // error
  return 1 // error
}


Allow reputation +'s and -'s to be logged like kicks and mutes.

So I am playing around with what I can use from discord bots and the rep thing is a good idea.
But without the proper logging I can't see who may or may not be spamming rep. Can we get a logging feature like moderation powers do like how you can have warnings and mutes and stuff auto log the action to a channel "for the record" a way to do that for rep would be nice too.

Good idea, for now you can always use a custom command to send a message to a channel though.

I actually do log them all already, i just haven't made any way to access those logs

done with https://github.com/jonas747/yagpdb/commit/0f06cb7046a62dea25d5846f9badf8cc0aa0a6d1 and https://github.com/jonas747/yagpdb/commit/52a5867534caa30b95f963051bca3d5155e0c8a2


dotfiles v1.2.x

📜 Software Release Plan 📜
Purpose

To maintain the dotfiles repository.
Quality Criteria

[x] > 80% of identified bugs fixed.

Personnel and Resources

Lead: @cmbengue-ec-intl
Reviewers: @javhaan
Delivery Approach & Schedule

Release Date: 2024-06-27

CC

@cmbengue-ec-intl
@Azendae-Popo

Key Results and Deliverables

### v1.2.0 QuAC
- [ ] https://github.com/ec-intl/dotfiles/issues/55
- [x] update Readme.md directory structure

### v1.2.1 QuAC
- [ ] https://github.com/ec-intl/dotfiles/issues/54
- [ ] https://github.com/ec-intl/dotfiles/issues/57
- [ ] https://github.com/ec-intl/dotfiles/pull/67

🌵 Complete


Fix CI: 🟢 mac-os specific ghostscript install

Let's make CI 🟢 again.
Thanks to this source: https://jonathansoma.com/everything/pdfs/camelot-ghostscript/

EAFP,
We can always revert. 😉


Unreal Engine 5.1 Released

Need to compile the plugin for 5.1 and deprecate previous version

This was resolved as part of #26
Release can be found here: https://github.com/JaydenMaalouf/JoystickPlugin/releases/tag/1.1.0


Bonfire: cash register leads to waypoint build a cash register

The link Bonfire:cash register leads to the waypoint: build a cash register. The bonfire shows as incomplete, I have completed the cash register waypoint, which shows as complete. I'm not sure if they are meant to be different things?

Nice catch! I've fixed this and it will be live soon. Thanks!


generic baseline

Generic baseline for developing different types of examples

Thinking now with the chat-gpt API released benchmarks for this template against specialized templates become a bit less important, I was going to make it ready for review afterward benchmarks but it feels like there is no harm in merging it this way and maybe making changes later on.