Send email notification to support staff and user when submitting a form

This PR introduces the logic to send an email to:

our internal support address
the user who submitted the form

The email message contains a link to the submission for reference along with a helpful message.

[x] email uses a text template we can read and change the copy
[x] email uses an html template we can read and change the copy
[x] email links back to to the provider, and includes relevant details
[x] an email is sent to the submission author and the support staff
[x] we have fail gracefully when email is not working, with a intelligible error message

 Send an email when a new verification request is submitted

hey @tortila it looks like you're reviewing this PR - can you please tag me when you're done? I'll make the requested changes once you have.


Tut not found

README recommends this:
scalacOptions.in(Tut) ~= filterConsoleScalacOptions

please use some actual configuration? Also, I'd suggest switching to the / syntax.

Immediately above this the README says
f necessary you can filter out scalac options that are unhelpful in the REPL from user-defined tasks or scopes.

I can't posslbly predict what plugins and configurations the user will have. The code sample is just an example of such a user-defined scope.
I don't use SBT anymore and haven't regularly done so for about 3 years. If you'd like to keep this plugin up to date I am happy to give you maintainer access. Failing that, PRs are welcome.


Can not call existing function

Godot version
v4.1.2.stable.official [399c9dc39]
System information
Godot v4.1.2.stable - Windows 10.0.22621 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3050 Laptop GPU (NVIDIA; <IP_ADDRESS>9) - 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 Threads)
Issue description
When my custon plugin call the the node's function of edit scene, it throws the error nonexistent function 'generate_tile' in base 'TileMap'.But the node has the function.With or without the tool keyword.
Steps to reproduce

create a plugin
create a script inherit from EditorPlugin
write a new dock and bind a function to button like this

@tool
extends EditorPlugin

const editorAddon = preload("res://addons/MapGenerateEditor/MapEditor.tscn")

var dockedscene
@export var num: int = 1

func _enter_tree():
	dockedscene = editorAddon.instantiate()
	add_control_to_dock(DOCK_SLOT_RIGHT_UL, dockedscene)
	dockedscene.get_node("./Button1").pressed.connect(self.test)

func _exit_tree():
	remove_control_from_docks(dockedscene)
	dockedscene.free()

func test():
	var t = get_editor_interface().get_edited_scene_root()
	print(t.get_node("./TileMaps").has_method("generate_tile"))
	t.get_node("./TileMaps").generate_tile()
	# t.get_node("./TileMaps").set_cell(0, Vector2i(1, 0), 0, Vector2i(0, 0), 0) the code execute normally

create a new scene and add a tilemap node.
create a script to it and add any function.
click the button that just creates.

Minimal reproduction project
project.zip

You cannot call a non-@tool method from a @tool method, the fact that has_method returns true doesn't really depend on that I'd say, and not sure it should

You cannot call a non-@tool method from a @tool method, the fact that has_method returns true doesn't really depend on that I'd say, and not sure it should

In Issue description, I write with or without the tool keyword.It still happens.

The attached project works correctly for me, so not sure what's the problem?
As for the error, it's expected if you don't use @tool: #43853

The attached project works correctly for me, so not sure what's the problem? As for the error, it's expected if you don't use @tool: #43853

After I test many times, I find if the project's script itself has the tool keyword, then the plugin can access the method whether you remove it or keep it. If the open project doesn't have the tool keyword, then it won't help if you add it. Unless you reload the project.
@tool
extends TileMap

func _enter_tree():
	print(randi())
	# set_cell(get_layer_id_by_name("ground"), Vector2i(0, 0), 0, Vector2i(0, 0), 0)
	# set_cell(get_layer_id_by_name("ground"), Vector2i(0, 1), 0, Vector2i(0, 0), 0)
	# set_cell(get_layer_id_by_name("ground"), Vector2i(0, 2), 0, Vector2i(0, 0), 0)

func get_layer_id_by_name(name_to_find: String) -> int:
	var layer_id = -1
	for i in range(get_layers_count()):
		if get_layer_name(i) == name_to_find:
			layer_id = i
			break
	return layer_id

func generate_tile():
	print("generate_tile")
	set_cell(get_layer_id_by_name("ground"), Vector2i(0, 0), 0, Vector2i(0, 0), 0)

Tool scripts are colored differently in the script editor (regular scripts have white icon). Normally you don't need to restart the editor for them to get enabled, though reloading the scene might be necessary.

Tool scripts are colored differently in the script editor (regular scripts have white icon). Normally you don't need to restart the editor for them to get enabled, though reloading the scene might be necessary.

yes, you are right.When I click reload saved scene menu, it runs normally.

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/36592.


libassuan bottle issue

Bug reports:
I'm on El Capitan
The binary build for libassuan seems to be broken
dylanetaft-imac:gpgme-1.6.0 dylanetaft$ libassuan-config --libs
-L/usr/local/Cellar/libassuan/2.4.2/lib -lassuan -L/usr/local/Cellar/libgpg-error/1.20_1/lib -lgpg-error
dylanetaft-imac:gpgme-1.6.0 dylanetaft$ ls usr/local/Cellar/libgpg-error/1.20_1/lib
ls: usr/local/Cellar/libgpg-error/1.20_1/lib: No such file or directory
dylanetaft-imac:gpgme-1.6.0 dylanetaft$ ls usr/local/Cellar/libgpg-error/1.20_1
ls: usr/local/Cellar/libgpg-error/1.20_1: No such file or directory
brew install --build-from-source libassuan fixes the issue
dylanetaft-imac:libassuan-2.4.2 dylanetaft$ libassuan-config --libs
-L/usr/local/Cellar/libassuan/2.4.2/lib -lassuan -L/usr/local/Cellar/libgpg-error/1.21/lib -lgpg-error
The binary version installs to a 1.21 folder, but the build seems to be 1.20.

It looks like you're missing a / before usr here:
ls usr/local/Cellar/libgpg-error/1.20_1

Sorry but you have not followed the requested steps on the Troubleshooting page: https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting
Please follow (all of) these steps and post the information here so we can help you with your problem.
Thanks!

Bad paste on the ls command, still, libassuan-config --libs if not installed from source shows a directory that doesn't exist on El Capitain.
I ended up forgoing brew for gpgme, gpg2, libgpg-err, and libassuan and for now because I want to develop against 2.1.11
If you can't reproduce it, I'll just close this.

Compiled GPGME and related packages of homebrew due to unrelated issues\version, can't easily test further because that will conflict with homebrew links in /usr/local, closing, thanks!


ERM - Create derived table 'openaccess_charges' for Metadb

The purpose of this derived table is to show informations about the records in the table "folio_oa.charges" and their linked tables and reference data.
Attributes: https://wiki.folio.org/pages/viewpage.action?pageId=118272744

The connection between charges in the FOLIO app Open Access and the invoices in the FOLIO app Invoices still needs to be clarified. The ERM working group will discuss this.

Report is required, but SME still need to consider what the report should look like.


add coro_file

Why
Add coro_file to support cross-platform file async read and write.

linux 5.1 above: using io_uring to do async file read/write;
linux (5.1 bellow): using libaio to do async file read/write;
win: using iocp to do async file read/write;
mac: using threadpool to do async file read/write;

work items:

[ ] deal with unaligned buffer for libaio;
[ ] add get_aligned_buffer for user to reuse the buffer;
[ ] support mac async file read/write;
[ ] add ut make sure 100% line coverage;
[ ] add more examples for libaio;
[ ] add more examples for io_uring;
[ ] add more examples for win;
[ ] add more examples for mac;
[ ] add benchmark;
[ ] add doc;

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: qicosmos:x: zhengjian526You have signed the CLA already but the status is still pending? Let us recheck it.


AUTO_INCREMENT support for MySQL

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

The annotation as implemented below does not result in auto-increment functionality in MySQL.
field.Uint32("something").
			Annotations(
				entsql.Annotation{
					Incremental: &increment,
				},
			),

Result:
`something` int unsigned,

Expected:
`something` int unsigned AUTO_INCREMENT,

Motivation 🔦

It should be possible to have auto-incrementing fields that are not the id field as I use strings for id.

Hey @ClayMav! If you don't use AUTO_INCREMENT IDs in your Ent schemas, it should be possible. I'll give it a look and will update you.

Any update on this? In my application ids are strings (nanoids). I do not use auto increment for the id field

Could confirm, Adding following field results in column def which is missing Increment struct member
field.Int("int_id").Annotations(entsql.Annotation{
			Incremental: &t,
		}).Unique(),

The schema column def in migration
		{Name: "int_id", Type: field.TypeInt, Unique: true},  // <<<--- missing Increment: true

@a8m

attempt: https://github.com/ent/ent/pull/3398/files

@a8m
What is the current status of this issue?
https://github.com/ent/ent/pull/3398
Why hasn't this PR been either closed or merged yet?


nixos/virtualisation.podman: Init module

Motivation for this change
This is another stab at making a module for podman, a drop-in replacement for Docker.
Unlike previous attempts ( https://github.com/NixOS/nixpkgs/pull/68343 & https://github.com/NixOS/nixpkgs/pull/54925 ) this tries to stay very close to upstream defaults and introduce minimal configuration.
I also have tests and release notes.
I have been running a very similar module in my own configuration for quite some time without issues.
It works just fine rootless too with the following configuration in configuration.nix:
virtualisation.podman.enable = true;
virtualisation.podman.dockerCompat = true;
virtualisation.containers.users = [ "adisbladis" "aoeu" ];

~Should we add a config option to set up subuid/subgid ranges for users in the podman module maybe?~ - done
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @vdemeester @peterhoeg @nlewo
Closes https://github.com/NixOS/nixpkgs/issues/65202

This is nice and much nicer than mine (a lot less code which is great!).

Should we add a config option to set up subuid/subgid ranges for users in the podman module maybe?

Yes please.

Should we add a config option to set up subuid/subgid ranges for users in the podman module maybe?
Yes please.

Can you think of a nice interface for this?

I've opted to make subuid/subgid users a simple list:
    virtualisation.podman.users = [
      "adisbladis"
    ];

podman and related packages have a team if you want to add it as a a maintainer for the module.
cc @saschagrunert

I've also moved declarative docker containers to podman in https://github.com/adisbladis/nixpkgs/tree/podman-declarative-containers. This will be a follow-up PR.

podman and related packages have a team if you want to add it as a maintainer for the module.

Done! also added myself to the podman team.

@GrahamcOfBorg eval
@GrahamcOfBorg test podman

@GrahamcOfBorg eval
@GrahamcOfBorg test podman

Unless I get some very strong objections my plan is to move fast on this and merge soon.

Is it a good idea to map all podman users to the same 100000+65536 range?

Is it a good idea to map all podman users to the same 100000+65536 range?

No that was an oversight. I've fixed this.

I have created a new virtualisation.containers module.
The cri-o module was also creating /etc/containers/policy.json so these modules would be mutually exclusive.
With this change things composes much better with multiple container runtimes.
This leads to a much smaller podman module with a better defined scope.

@GrahamcOfBorg test podman

@talyz That looks to be https://github.com/containers/libpod/issues/5873.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/podman-and-docker-fail-to-mount/11709/3


testing, formatting and updated examples

needs to be tested further

I'll test it but it looks good to me.

@mhsjlw the branch has conflict, can't merge, can you rebase ?

would be useful to rebase this @mhsjlw

yup, I'll do it when I get a chance and set up circle ci too

It seems that this PR is really broken, I'll just open a new one.


Add backend services launch type

@jmandel wrote:

Feature note: I think we do want a "Backend Services Launch" option. Now that we've folded Backed Services into the core SMART spec (e.g. in overview at https://hl7.org/fhir/smart-app-launch/) it'll be important to support testing of this functionality. Basic workflow would be: choose "launch type" of "Backend Services", and get a "FHIR base URL" at the bottom of the launcher, just like in a standalone launch. Now apps can  POST directly to the /token endpoint with a client authn JWT + scopes to obtain an access token. It's the same workflow that the bulk data tool already supports, but will allow developers to try out a flow where they get scopes like system/Patient.read and then can make API calls like GET /Patient?name=... which will be important for folks developing headless EHR-integrated services. Does this make sense?

OK, I have deployed  some changes, adding support for BS launch as well as separate sample app for that.

This is looking great!
One issue on validation: if I set "JWKS Inline" via the "App Registration Options" tab, and then launch the sample app, it proceeds with a different public key (e.g., its default value from https://www.hl7.org/fhir/smart-app-launch/RS384.public.json). I'd expect this token request to fail because the app-supplied JKU is only a "hint"; the server can't trust it or treat it as authoritative, if it's inconsistent with the registration-time JWKS or JWKS URI. Does this make sense?

I am trying to figure out the proper behavior (applies to both backend service launch and asymmetric auth). Is this correct and what should be done if we have jwks + jku (case 6)?
# | jwks | jwks_url | jku |
--+------+----------+-----+-----------------------------------------
1 |  N   |    N     |  N  |  Not OK
2 |  N   |    N     |  Y  |  OK if jku works
3 |  N   |    Y     |  N  |  OK if jwks_url works
4 |  Y   |    N     |  N  |  OK if jwks works
5 |  N   |    Y     |  Y  |  OK if jwks_url works and matches jku
6 |  Y   |    N     |  Y  |  ?
7 |  Y   |    Y     |  N  |  OK if jwks_url works; Ignore jwks
8 |  Y   |    Y     |  Y  |  OK if jwks_url works and matches jku; Ignore jwks

Thanks for laying this out in a logical grid!
Let me try to build up from a processing model. When a token request arrives...

If neither jwks nor jwks_uri is set in "App Registration Options", disable client authn checks. Just make sure a well-formed JWS is present in the client assertion, and consider it "valid" if so. (This is similar to how we disable client authn checks for symmetric authn, if no client secret is set in app registration.)

Otherwise, enable client authn checks.

Build a set of "allowed keys" as the union of:

All keys in jwks
All keys in jwks_uri

Check whether the JWS is valid and signed with one of the allowed keys
If jku is present as a JWS header, check that an idential jwks_uri was included in "App Registration" options, because https://hl7.org/fhir/smart-app-launch/client-confidential-asymmetric.html says: "When present, this SHALL match the JWKS URL value that the client supplied to the FHIR authorization server at client registration time."

It says here that "If no keys match, or more than one key matches, the verification fails.". There is an edge case where the user enters a jwks and a jwks_url that provides the same JWKS. In this case we will have duplicate keys. What is the correct behavior then?

a. Ignore duplicates (if so, how can we have more than one match?)
b. Prefer keys from jwks_uri as they may be more recent
c. Produce an error

Is it even valid to use jwks and jwks_uri together?

an edge case where the user enters a jwks and a jwks_url that provides the same JWKS.

Just to be clear, you're saying the JWKS and the JWKS URL are both provided and both have a key with the same kid? Sure, in that case we should produce an error (not sure it's the "best" behavior but it's what the spec says, so seems good enough). Note that this issues doesn't arise when the JWKS and JWKS URL have content with distinct kids.

That sounds great, thanks @vlad-ignatov !


Upgrade redux-persist-transform-immutable

redux-persist-transform-immutable v4 uses transit-js, which takes up 18kb of the bundle size, gzipped and minified. It would be nice to use v5 which uses a much lighter library. I could open a PR for this but wanted to know if it would break anything :)

Very interested in this as well

@chrisgbaker I have already upgraded it in a fork on my account. After upgrading redux-persist-transform-immutable, there was a bug in the new library it used instead of transit-js where it tried to instantiate classes without new, this caused a runtime error with Babel-compiled projects. I also upgraded that and added everything to this branch:
https://github.com/aghoneim92/redux-persist-immutable/tree/upgrade-remotedev-serialize

@aghoneim92 thoughts on that PR?

What needs to be done to get @aghoneim92's changes merged and a new release cut? Still very interested in having the dependency updated so I can drop transit-js from my bundle.

@chrisgbaker #37 and #41 are both open, but the library doesn't seem to be active or maintained anymore. If we couldn't get this merged, I suggest you link to my fork or your own fork of that one with a github value in your package.json

Hey in case anyone comes across this you can use this package


[SPARK-31305][SQL][DOCS] Add a page to list all commands in SQL Reference

What changes were proposed in this pull request?
Add a page to list all commands in SQL Reference...
Why are the changes needed?
so it's easier for user to find a specific command.
Does this PR introduce any user-facing change?
before:

after:

Also move use database from query category to ddl category.
How was this patch tested?
Manually build and check

Test build #120602 has started for PR 28074 at commit 083d479.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25306/
Test PASSed.

Test build #120602 has finished for PR 28074 at commit 083d479.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120602/
Test PASSed.

Test build #120605 has started for PR 28074 at commit 571765a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25309/
Test PASSed.

Test build #120605 has finished for PR 28074 at commit 571765a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120605/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/25326/
Test PASSed.

Test build #120624 has started for PR 28074 at commit c8c9f17.

Test build #120624 has finished for PR 28074 at commit c8c9f17.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/120624/
Test PASSed.

@srowen This is for 3.0. Thank you!

Thanks, @huaxingao ! Merged to master/3.0. btw, have we done all the works about the SQL references? It seems the RC1 for 3.0 will be started in a few days.

Thanks! @maropu @srowen
@gatorsmile wants a few more. I am working on functions right now, will probably submit a PR for UDF later today.

ok, thanks for the work! cc: @dongjoon-hyun


Roll engine 740f9160a256..6a0ca8dc7890 (1 commits)

git@github.com:flutter/engine.git/compare/740f9160a256...6a0ca8dc7890
git log 740f9160a256..6a0ca8dc7890 --no-merges --oneline
2019-08-31<EMAIL_ADDRESS>Let java unit tests build with autoninja (flutter/engine#11799)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Auto-roller completed checks. About to merge.


per-account 3/n: Sort out remaining selectors

This is the next PR in the series after #5016, #5017, and #5023, produced from the branch described at #5006 (comment).
From the foreshadowing last time:

After this PR, the conversion of tryGetAuth is still incomplete, so that's next up. Then we handle a few remaining selectors elsewhere, in particular those for state.settings and state.session.

That's this PR.
Next, continuing what we mentioned last time:

After that, we'll convert thunk actions and React components so that they get a PerAccountState rather than a GlobalState.

Thanks, LGTM! Please merge at will.
One nit is that "remaining selectors" doesn't quite cover it, I think—remember this bit, from your 59d8813889c69083e66902b140a742e93fd80d66:

A more boring class of exceptions is the many small anonymous
selectors (mostly as callbacks to useSelector) that get bits of
the settings and session data. Many of those are really
per-account, but for now we leave them all marked as global.

Thanks for the review! Merged.

One nit is that "remaining selectors" isn't quite accurate, I think—remember this bit, from your 59d8813:

A more boring class of exceptions is the many small anonymous
selectors (mostly as callbacks to useSelector) that get bits of
the settings and session data. Many of those are really
per-account, but for now we leave them all marked as global.

True. I guess what I really meant is more like "remaining named selectors", or "remaining selectors in *Selectors.js files".
Those small anonymous selectors, we'll get to as part of migrating the React components that they're part of.


Update flatbuffers version and fixed incompatibilities

Codecov Report

Merging #191 (57a060a) into master (f9f162d) will decrease coverage by 0.38%.
The diff coverage is 0.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #191      +/-   ##
==========================================
- Coverage   64.45%   64.07%   -0.38%
==========================================
  Files          71       71
  Lines        4324     4326       +2
  Branches      543      545       +2
==========================================
- Hits         2787     2772      -15
- Misses       1297     1311      +14
- Partials      240      243       +3

Components
Coverage Δ

AuthManager
77.77% <ø> (ø)

Cache
28.24% <ø> (-1.51%)
:arrow_down:

FDS
70.68% <ø> (ø)

FileWatcher
55.90% <ø> (ø)

Flip
65.67% <ø> (ø)

gRPC
77.66% <ø> (ø)

Logging
29.33% <ø> (ø)

Metrics
80.54% <ø> (ø)

Options
100.00% <ø> (ø)

Setting
56.79% <0.00%> (-1.20%)
:arrow_down:

StatusObject
73.83% <ø> (ø)

Utility
83.66% <0.00%> (-1.26%)
:arrow_down:

Version
95.83% <ø> (ø)


[PE-D][Tester B] Sortcus function not working as intended

sortcus d/- does not work, when inputting into the command line and pressing enter, there is no action even though the logbook logs the command being executed. Attached are the photos of the logbook and how the GUI looks after inputting the command and pressing enter. The sortcus command works well for all other iterations of the prefix and suffix. Only seems to not work for sortcus d/-.

Labels: type.FunctionalityBug severity.High
original: Neethesh26/ped#1

The issue with this is the latest commission date for all customers in the sample file is the same, so sorting by customer seems like it does nothing. Perhaps we can include the time (idk if this is a feature flaw or bug) or change the dates in the sample data so it looks like it's doing something

Duplicate of #178


[py38] Python 3.8 is no longer dev

Python 3.8 is no longer dev

Coverage decreased (-0.004%) to 95.59% when pulling 52e13cbee4e5a49f86aace5c371b29cd62852a48 on Djailla:py38 into 4589d4c40bd5b8ecb1b34e69e5f5e6632217de2c on django-import-export:master.

Coverage decreased (-0.004%) to 95.59% when pulling 52e13cbee4e5a49f86aace5c371b29cd62852a48 on Djailla:py38 into 4589d4c40bd5b8ecb1b34e69e5f5e6632217de2c on django-import-export:master.

Thanks


Consider using a tool such as Bakefile

Currently, all the build files are hand-written.  You should consider using Bakefile, which is based on the idea of pre-generating the build files. You run Bakefile on your computer, upload the generated files, and the user doesn't even know it exists.
It supports VS 2013 and GNU make. I can look into opening a PR for Code Blocks if desired.
Also, I'd be happy to contribute the build files if it's decided that this would be a good idea.

Looking forward your contribution


Get notified/alerted when there's a high number of rollbacks in Codepush

Context on issue
I realised after a few days that our last React Native CodePush build had an issue and was being rolled back. An important feature blocked users as they needed to be on the latest version.
Describe the solution you'd like
Would be good to be notified if a high number of rollbacks are happening and nobody is activating the last version of the app. Maybe if the number of rollbacks is almost the same number of active devices. Or a % of them.

Thanks for the suggestion. Will add this to the list of future improvements.


Resetting default focus

When my app that uses Sunbeam starts, it's setting an item to focused by default. This is great.
When I change screens in my app using react-navigation, I'd like the first element on the new screen to be focused by default. However, the old item remains focused even though it's no longer visible, and maybe not even in the component tree anymore.
Is there a way to re-run the startup behavior to determine a new default focused element? I found focusManager.revalidateFocusPath(), but that didn't seem to do it.

Hi, are you sure that the old Focusable is not in the tree anymore, because it will stay focused if it's still there. If your use case requires the Focusable to stay in the tree but say invisible you could use focusable: {false} (https://github.com/vovaguguiev/react-sunbeam/blob/dc16272f336133baa7fedda7bb0f77ec919fe424/packages/react-sunbeam/src/focus/components/Focusable.tsx#L15) prop on it to make Sunbeam ignore it when it's not visible. Once changed to false it will trigger the re-selection of the new Focusable

Here is a practical example of how that prop can be used: https://github.com/vovaguguiev/react-sunbeam/blob/dc16272f336133baa7fedda7bb0f77ec919fe424/packages/demo/src/apps/SettingsMenu/Picker.tsx#L20

Thanks for the reply, and apologies for not seeing it sooner.
The old Focusable remains in the tree, but hidden, so it retains focus.
I hadn't noticed the focusable property, I'm guessing that will solve the problem. I'll explore and report back if that doesn't work.


thirdpseron

the thirdperson local player keeps blinking anyone else got this problem?

Yes, will get fixed in the next update.

alright great thank you


3.1.0 Erases most Typescript definitions

Description
As of 3.1.0, almost all valuable TS definitions are gone. I believe that this function just needs some generic type variables and it'd resolve the issue:
https://github.com/handsontable/react-handsontable/blob/3331959cd0ddc887c867f8839cb342f8313ab7f2/src/helpers.tsx#L153-L166
See generated TS definitions:
https://unpkg.com/<EMAIL_ADDRESS>https://unpkg.com/<EMAIL_ADDRESS>

@dboskovic You're right, it definitely needs fixing. Thanks for reporting!

+1 hope this will be fixed soon, busy setting up a presentation for my team to compare handsontable and ag-grid, without the typescript support handsontable will never get accepted for our production.

Hey @PaulPCIO we're already doing the Code Review.
It shouldn't take us long to push a fix.

@PaulPCIO, @dboskovic<EMAIL_ADDRESS>was just released, so this issue should no longer be a problem.


feat(prow-jobs): add presubmit job for pingcap/tiflow

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


Thanks Jenkins.sh...

Really thanks. Jenkins.sh is broken my server.
Apache, MySQL,and all server apps broken because script use rm -rf
Thanks.

we don't support old branch. it's on the plan for removal.

But you send me here from faq.

Why you even had an idea to touch jenkins? Also, take risk if you ran it as root.

because it wrote in README.md

Again, if you ran it as root, it's up to your responsibility. Inspect the content before you run a file. These script are provided by best effort basis.

But you need check your script.

This is not for your use. You don't read the words. This is used for previous Jenkins only and put there for a reference.


The wordlist contains a non-alphabetical character in "BLING!"

Describe the bug
The wordlist contains a non-alphabetical character in "BLING!". Users can not enter the exclamation point in the user interface.
To Reproduce
Steps to reproduce the behavior:

Search the repo for BLING!

Expected behavior
The user would only expect solutions that contain the letters A-Z.
Screenshots
No screenshots at this time.
Desktop (please complete the following information):

OS: all
Browser all
Version all

Smartphone (please complete the following information):

Device: all
OS: all
Browser all
Version all

Additional context
BLING! was the marvle word of the day today. :/

Fixed! Thanks for reporting. :)


FREQ: Set local SID via LDAP parameter

Hello MutonUfoAI,
I have a feature request.  In the authentication configuration for LDAP, there is the ability to map parameters from LDAP to the user.  It would be nice if the local created user SID could be mapped from the LDAP "sambaSID" parameter.
Thank you.

That will not work.
You need to join this samba domain to use those sid's.

Ah, Ok.  Sorry to hear that.
Thank you.


Fix rapid-fire rejuvs edge case

Ran into a mana burn champ and had all 8 full rejuvs drained within 2 seconds.
[2021-11-30 22:02:25,394] DEBUG      Waiting for Template ['ELDRITCH_0', 'ELDRITCH_START']
[2021-11-30 22:02:38,542] DEBUG      Drink rejuv potion in slot 2. HP: 97.9%, Mana: 0.0%
[2021-11-30 22:02:38,676] DEBUG      Drink rejuv potion in slot 2. HP: 97.9%, Mana: 0.0%
[2021-11-30 22:02:38,816] DEBUG      Drink rejuv potion in slot 2. HP: 97.9%, Mana: 0.0%
[2021-11-30 22:02:39,106] DEBUG      Took a screenshot of current loot
[2021-11-30 22:02:39,457] DEBUG      Drink rejuv potion in slot 2. HP: 96.7%, Mana: 0.0%
[2021-11-30 22:02:39,600] DEBUG      Drink rejuv potion in slot 4. HP: 96.7%, Mana: 0.0%
[2021-11-30 22:02:39,735] DEBUG      Drink rejuv potion in slot 4. HP: 96.7%, Mana: 0.0%
[2021-11-30 22:02:40,244] DEBUG      Drink rejuv potion in slot 4. HP: 98.9%, Mana: 0.0%
[2021-11-30 22:02:40,386] DEBUG      Drink rejuv potion in slot 4. HP: 98.9%, Mana: 0.0%
[2021-11-30 22:02:40,388] DEBUG      Stop health monitoring

https://user-images.githubusercontent.com/9866239/144169056-f22c5003-feb0-46d9-bb63-6dbeff704825.mp4
This PR utilizes the initialized _last_rejuv variable for HP and mana to avoid edge cases like this, allowing a small delay in HP and MP rejuvs. Feel free to adjust the delay as you think is appropriate.

Has been on my list. You were quicker :P


SD OLED Installation Black Screen

Not sure how to capture a log for this but during install on Steam Deck OLED (2tb ssd upgrade) I can get to select Basic Graphics mode to begin installation but then it just goes to a black screen and sits there indefinitely.  The touchpads sound like they're working but there's nothing on the screen.  If I press power I can see it start to get to a prompt but then that too disappears.
If I try to install normally I can get to the first install screen but of course on OLED it's the wrong resolution and I only see the top left area of the screen.
Any ideas?
Edit: using deck-gnome
Edit: also just tried the kde image, same result

I had to reinstall SteamOS after my screen goes black after an update on BazziteOS (KDE).
And now, same behaviour: black screen after the installer loaded. Installer appears when using the default installer entry not the basic graphic mode entry.
Using SD OLED 512Go.

I held off installing Bazzite until it was a little more stable for SDOLED but for more context I also tried various hardware configurations: official dock, aftermarket dock, different keyboards and cables, with and without a mouse, and various flash drives.  I did notice that I was able to drop to different terminals (cmd+alt+f1 f2 etc) and then get back to the install screen with cmd+alt+f6 but after getting back to the install screen this way, the keyboard and mouse were not visible.  Such that even hitting tab did not show me which section of the install screen I was highlighting until I dropped to the terminal then got back to the install screen.  Very strange... I could probably get through the install this way but it would be difficult and risky.  I also noticed, when giving up on the Bazzite install and booting back into SteamOS, when going into desktop mode the screen displayed a bunch of random vertical lines, filling up the screen, until I put the deck into sleep mode and then bring it back up.  After that I've had no issues using SteamOS.

I'm having this issue, too. Fresh 2TB SSD, SD OLED. Like said above, I can drop into a terminal from the black screen, then get to the installer. But, there's no recognized mouse or keyboard input unless I hope back into a terminal.
Booted from Ventoy in grub2 mode, then Basic Graphics Mode. I'll try a USB on its own, but I'm not hopeful.

I am seeing the same behavior. Steam deck oled, 512gb. I was able to install on the regular graphics mode, and therefore only seeing the top left of the screen, and using tab to select off-screen buttons. Plugging in an external screen lets you see a little more.

Fixed in newest ISO, also has Bazzite branding and a default username and password, eliminating the need for a keyboard (Though still highly recommended)

I'm having this problem with fresh BazziteOS installer on the OLED.
Basic graphics mode just goes to completely black screen, and regular installer has wrong resolution


Known Issue: Firefox Windows: Filter row misaligned with empty result in horizontally scrolled FilterTable

When

a Filtertable is wider than its container
and is scrolled to the right
and you enter a filter expression that leads to an empty result

then

the Filtertable is scrolled back all the way to the left
but the Filter row stays in the scrolled-to-the-right position; so the columns are misaligned

Only reproduced on Windows 7 with FF 25 & 28.
Not reproduced with Chrome on Windows or Safari 7.0.3 and Firefox 28 on Mac OS X 10.9.2.
Example code to reproduce is here:  https://github.com/jey-avono/columntrouble
Just run mvn package jetty:run and open http://localhost:8080
Start:

Scroll to right:

Enter Filter String:

After Pressing RETURN

Is this issue resolved? Any update please?


Adjusting the Margin of the ContentLoader in a TabList

I'm fairly new to WPF, and am having a bit of trouble getting access to the margin (Margin=32,0,0,0) on the content side of the TabList. Everything looks awesome in general, but that one's kind of hurting my design. Is that something that can be changed with a custom theme, or is it too deep, and if it can, can someone possibly give me a pointer as to how to achieve this. I don't really understand the theme setup to begin with. I've created and loaded a custom theme, but from there, I don't really know what it is that I need to do to style (or if that's even something that can be styled).

Never mind. So sorry for jumping the gun. I figured out how to use the custom theme to adjust the margin. Sorry to have bothered.


Add Livestream possibility

To livestream from the camera a second camera device is necessary.
Adding a v4l2 loopback module is a way to add a virtual camera device that mimicks the original one. This is the device to be used by the streaming platform. Adding just one will limit overhead on the mini-pc.
Then we need a way for an arbitrary number of users to be able to stream the frames coming in. For that we will create a shared memory object that will host the current video frame. This frame will be updated then a new camera frames comes and a counter will be incremented. The counter is used to acoid serving the same frame multiple times.
When a user connects to the stream, the server side route will build a generator that on every call of next() will:

wait until the counter is changed from its current value (maybe use a condition variable with wait() in the generator and notify_all() in the sharted mem object. It could replace the counter and make it more reliable)
read and yield the frame

That will enable any number of users to stream the same video stream. Frames missed due to slow network wll simply not be seen by the generatoor and thus immediately dropped. No tearing will be present because each frame will be it's own object and won't be GC before all generators have released it. However that will place strain on the GC! (problem for another time)

NB: A second video device is necessary! cf v4l2 loopback module
You can stream to any number of people simultaniously by setting the device in the .env file STREAM_VID_DEVICE (for example /dev/video2)
Then going to /livestream will start reading from the device (usually a camera) and regularly update the current frame. Note: frame drops may happen but you will never fall behind. Missed frames are nust never shown.
NB: depending on the resolution, it may require a lot of bandwidth! (every frame is currently a jpeg)


Package for patching kubernetes resources

This code contains the guts of kustomize style overlays for the generated manifest.
Please see code and tests for documentation and examples.

General comment, if this is supposed to represent "kustomize" type capabilities, would it be better to try to use the actual kustomize code, e.g. like we do with helm?
For example, use functionality from any of these packages: https://github.com/kubernetes-sigs/kustomize/tree/master/pkg

Okay, I don't think I understood what was going on here initially.  Are you creating a schema for defining patches in the CR?  If so, I think that has real potential to bloat the CR, with all of this patching.
If that is the case, then maybe, instead of defining your own schema for patching, it might be better to utilize json merge patch or strategic merge patch descriptions, as these are standard and supported by things like kubectl patch.  Users would at least have a head start in understanding the format.

The problem is neither json merge nor strategic patch support value based path selection.
What this means in practice is that you cannot modify just a flag in one of the containers (since this is a list item) as shown in the unit tests here. You have to re-specify the entire container. I started off thinking I could just use json merging but I just don't think it's workable, since customizing container flags is going to be a very common use case for this overlay mechanism.

I believe strategic merge patch supports ordering and removal.  Here's a link to the docs:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/strategic-merge-patch.md

It does, but what I'm saying is list entry selection through key is not supported, so you have to replace/remove the entire list item. For example, how would you remove the following line with json/strategic merge?
https://gist.github.com/chanwit/4e1e4f951cf3357c1c3d7804f8162312#file-istio-demo-yaml-L2815
(say you want to remove --webhook-config-file).

According to the jsonpatch doc, while accessing a list item by key is not supported (what key would you use?), you can access them by index.  For example, from http://jsonpatch.com/
{
  "op": "replace",
  "path": "/biscuits/0/name",
  "value": "Chocolate Digestive"
}

You can find more k8s specific examples if you look (e.g. changing the image name on specific container within a deployment).

Right, jsonpatch only supports indexing which is too brittle to use in practice, since we cannot depend on item index in lists remaining constant over time.

The base functionality looks fine to me to move forward with it for now, but we should remove the dependencies to the github.com/ostromart/operator repo before merging this in.

Removed the dependencies (these were just left over from testing in my local ws) and added some minor fix. If there are no comments this can be approved, anyway it can not go in until the dependencies are merged.


Support import script in Global block

Is your feature request related to a problem? Please describe.
We don't have javascript highlighting in YAML files. one way is to break out the javascript into a separate file and import it via yaml. This is already supported in executeCode function.
Describe the solution you'd like
Update the global block to also support scriptName and import file from app context
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@evshi, if we update the global block to support the script name, and then during runtime, import that script from the app context, the current implementation of the global scope, which accepts the code block in the form of a string, may break.
Global: |
  function callMeAsYouSee(){
    console.log("See ya, it works");
  }

  function manipulateData(dataArr){
    let newData = dataArr;
    console.log(dataArr);
  }

As per the evaluate function, it simply compiles the string of the global scope as code.

@sagardspeed2 it shouldn't break. This ticket is only about adding support for how the script is loaded into memory, not how it's evaluated.

@evshi, currently, the definition of the global block is like:
Global: |
  function callMeAsYouSee(){
    console.log("See ya, it works");
  }

  function manipulateData(dataArr){
    let newData = dataArr;
    console.log(dataArr);
  }

which holds this code in memory. Now, for the support of importing a script inside the global block, the definition of the global block will be:
Global:
  scriptName: test.js

So, during parsing of the ensemble app, we will import the script from the app context and store the script body inside the global block. Am I correct?

Yes correct

So, when I change the global block definition from string to scriptName, the previously defined global block will not have a scriptName, so previously defined YAML with the global block will not work.

No, it should support both, prefer the script name property if it exists, otherwise fallback to the plain string definition

@evshi Yup, I got it and I am doing this way only


Design Suggestion

I've been thinking about the overall design of this project and there appears to be a lot of duplication. In each of the different configurations, are the scripts like Run-Lab identical? If so, I'd suggest creating a folder like Library or Tools and centralize the scripts. Perhaps even better would  be to turn the scripts into functions and create a module. The functions could have a Path parameter that defaults to the current location. The end result is that you can still run the commands from each configuration directory but overall management of the code base could be simplified.  Thoughts?

Totally agree!  Originally, the control scripts were unique to the configurations. As it stands today, they are not -- they are the same across configs and I would love to do this.  Do you have any ideas on how you think it best to proceed?  And if so, this would greatly improve maintenance for me -- as I've screwed up a few commits already.  Question is, since this would be a breaking change from the current design -- it would be another major point release.  Is this something we might be able to do in this release?  The only Dev work in progress on this release is @majst32 finishing ADCS in the POC-MultiRole config --- so the system is static enough to work on at the moment. @jdhitsolutions

@jdhitsolutions @majst32 - so - philosophical question -- Jeff, whats the community feeling of having control scripts turned into function in a module --- in other words -- All the test formatting, write-host and colorization......that pretty much all violates best practice and triggers everything in the script analyzer --- I think the module is a great approach, just trying to justify the approach.
  Anyway -- will put together a test module

I see this project as something that can eventually be modular easy to re-use. I don't see an issue with the control scripts as functions. They can be parameterized to make them easy to re-use.  Someday I'd love for an author or trainer to be able to easily generate a configuration. For example, I can foresee helper functions to export user information to a json file for example.
Of course, if you think what you have now is all you ever intend to do, then don't bother and call it a day.

ok -- almost done -- let me master this in the Dev-Modules branch -- I will let you know and you can test ...and clean my crappy module ;)

@jdhitsolutions @majst32  Jeff -- After I send this to master today - I will ping you --- it would be great if you could add the helper function to export AD users groups and OU's --- no rush -- it can be added as a point release later -- but I'm leaving this open for further discussion and issue reference.

This was resolved in a later release. Closing issue


Limit Number of Displayed Selected Facets

Currently we're showing all of the selected facets which can make the UI very cluttered. We should limit this list to 25 rows.

Since the redesign of the UI last fall, this issue doesn't seem relevant anymore.
Can you look at this @hongsudt  and see if you have the same problem still?


Fix refreshing page after deleting miq server

Configure->Configuration->Diagnostics->lead to any zone in tree
then in Roles by Servers tab click any server and click on Configured button and delete server and it caused error

LGTM :+1:


command: create new content

this requires some form of editor support, should support at least vim to start.


Getting an error

After following your instructions and then doing:
php artisan config:publish ceesvanegmond/minify

I'm getting the error:
PHP Fatal error:  Class 'CeesVanEgmond\Minify\MinifyServiceProvider' not found in /var/www/laravel/bootstrap/compiled.php on line 4485

{"error":{"type":"Symfony\Component\Debug\Exception\FatalErrorException","message":"Class 'CeesVanEgmond\Minify\MinifyServiceProvider' not found","file":"/var/www/laravel/bootstrap/compiled.php","line":4485}}
What do I have to do to solve this issue?

I had to do:
composer update

before publishing the config file.

Yes ofc, otherwise the package are not downloaded.


Fix outdated target_group naming in error message

The target_groups config has been renamed to static_configs, the error
message for overflow attributes should reflect that.
Fixes #1801.

:+1:


ci: init

closes #5
depends on #28

Let's use the standard CI flow here, the rest of us are not Nix-savvy enough to start using this as the main CI

Let's use the standard CI flow here, the rest of us are not Nix-savvy enough to start using this as the main CI

reworked to use asdf instead


Fix issue 15334 - OS X core.time ticksPerSecond calculation is incorrect

Fix for https://issues.dlang.org/show_bug.cgi?id=15334
The _d_initMonoTime() version(OSX) calculation for ticksPerSecond is using a flipped mach_timebase_info ratio numer/denom when it should be denom/numer.
This is a redo of #1430 on stable per @schveiguy with some of his suggestions.

I swear that this code becomes weirder and uglier ever time I look at it. The number of hoops that we've had to jump through to support multiple clock types is ludicrous. :|
In any case, I don't see anything obviously wrong with this change. I wish that we could have a unit test to verify this bug, but I can't think of one at the moment.

@jmdavis if you read the previous PR that @smolt made, when we merged the big change to generic MonoTime, we accidentally undid a previous fix of his for this that occurred between when you opened the PR and when it was merged. We just didn't notice the ordering of the numer/denom change. See this:
https://github.com/D-Programming-Language/druntime/pull/990/files#diff-b1d9cd2f54f89877fa85992be121dd6cL2304

I wish that we could have a unit test to verify this bug

The bug is straightforward to see, I don't know if there is a way to test it without mocking mach_timebase_info. Putting all the ticksPerSecond calculations in one place is probably best (although TickDuration is going away eventually).
One thing we could do is put a unit test that sleeps for 1 second, then verifies the ticks change roughly ticksPerSecond, or at least that the mach time corresponds to gettimeofday, but even with this, you would only see the bug on a system where the ratio is not 1:1 (e.g. iOS).
Dan, can you fix the comment typo and I will merge.

Oh, the bug is easy enough to see when you look carefully, but it always sucks when a unit test doesn't catch a bug, so ideally, we'd add a test that would. But in this case, I don't think we have a reasonable test that we can run. I certainly don't want to be adding sleeps to tests if we can avoid it.

I fix spelling and added a period to end of new abort message to match other aborts in this module.

I don't think we have a reasonable test that we can run.

Thinking outside the box, what about this:
version(Linux) version(unittest) version = hasMachTimeStuff;
version(OSX) version = hasMachTimeStuff;
...

version(hasMachTimeStuff)
{
   version(Linux) version(unittest)
   {
       struct mach_timebase_info_data_t {...}
       bool mach_timebase_info(mach_timebase_info_data_t *info)
       {
              /* return 125 / 3 */
              ...
       }
       unittest { assert(machTicksPerSecond() == 24_000_000);}
   }

   long machTicksPerSecond() { ... }
}

Ugly hack, yes :)

Auto-merge toggled on

Do I need a separate PR to get this into master or does that happen without me doing anything?

Martin will merge the branch into master every once in a while.


Using - inside the ip of the server

So, i'm a developer for a little server me and my friends own and they don't know how to get the numeric ip for the server (goofy ahh hosting) so we want to use the domain of the server which looks something like this: xxxx.xxxx-xxxxxxxx.xx
There is a - in there which makes the program crash, any ideas on how i could implement myself that or just wait for an update?

Hello,
I don't think a dash in the address could cause an error.
Please provide the log.
You can get the server's IP and port from a site like this: https://mcsrvstat.us/
and then try it.


lora二次訓練

參考了pretrain config, 使用lora設置use_speaker: false和較高learning rate合併lora能夠初步說其他語言，但不夠標準。
用其作為基底，繼續用lora以較細緻的設定finetune就失敗了。卡在了完成資料準備，Found 650 groups的字句，沒有任何報錯。

2024-06-19 13:51:40.341 | INFO     | __main__:main:174 | RANK: 0 / 1 - Starting worker
Found 99868 files
2024-06-19 13:51:50.988 | INFO     | __main__:main:185 | RANK: 0 / 1 - Processing 0/0 files
2024-06-19 13:51:54.878 | INFO     | __main__:get_model:62 | RANK: 0 / 1 - Loaded model
2024-06-19 13:51:54.879 | INFO     | __main__:main:211 | RANK: 0 / 1 - Finished processing 0 files, 0.00 hours of audio
Loading C:\Users\Naozumi0512\Desktop\AI\fish-speech\1.1.1\data: 99868it [00:01, 52269.95it/s]
Grouping C:\Users\Naozumi0512\Desktop\AI\fish-speech\1.1.1\data: 100%|████████| 99868/99868 [00:06<00:00, 16128.54it/s]
2024-06-19 13:52:06.934 | INFO     | __main__:task_generator_folder:46 - Found 650 groups in C:\Users\Naozumi0512\Desktop\AI\fish-speech\1.1.1\data, ['C:\\Users\\Naozumi0512\\Desktop\\AI\\fish-speech\\1.1.1\\data\\SPK100', 'C:\\Users\\Naozumi0512\\Desktop\\AI\\fish-speech\\1.1.1\\data\\SPK101', 'C:\\Users\\Naozumi0512\\Desktop\\AI\\fish-speech\\1.1.1\\data\\SPK102', 'C:\\Users\\Naozumi0512\\Desktop\\AI\\fish-speech\\1.1.1\\data\\SPK103', 'C:\\Users\\Naozumi0512\\Desktop\\AI\\fish-speech\\1.1.1\\data\\SPK104']...
556it [00:20, 113.19it/s]

設定了較低的workers number後可以正常工作，但無法合併模型:
RuntimeError: Error(s) in loading state_dict for DualARTransformer:
        Missing key(s) in state_dict: "embeddings.weight", "layers.0.attention.wqkv.weight", "layers.0.attention.wo.weight", "layers.0.feed_forward.w1.weight", "layers.0.feed_forward.w3.weight", "layers.0.feed_forward.w2.weight", "layers.0.ffn_norm.weight", "layers.0.attention_norm.weight", "layers.1.attention.wqkv.weight", "layers.1.attention.wo.weight", "layers.1.feed_forward.w1.weight", "layers.1.feed_forward.w3.weight", "layers.1.feed_forward.w2.weight", "layers.1.ffn_norm.weight", "layers.1.attention_norm.weight", "layers.2.attention.wqkv.weight", "layers.2.attention.wo.weight", "layers.2.feed_forward.w1.weight", "layers.2.feed_forward.w3.weight", "layers.2.feed_forward.w2.weight", "layers.2.ffn_norm.weight", "layers.2.attention_norm.weight", "layers.3.attention.wqkv.weight", "layers.3.attention.wo.weight", "layers.3.feed_forward.w1.weight", "layers.3.feed_forward.w3.weight", "layers.3.feed_forward.w2.weight", "layers.3.ffn_norm.weight", "layers.3.attention_norm.weight", "layers.4.attention.wqkv.weight", "layers.4.attention.wo.weight", "layers.4.feed_forward.w1.weight", "layers.4.feed_forward.w3.weight", "layers.4.feed_forward.w2.weight", "layers.4.ffn_norm.weight", "layers.4.attention_norm.weight", "layers.5.attention.wqkv.weight", "layers.5.attention.wo.weight", "layers.5.feed_forward.w1.weight", "layers.5.feed_forward.w3.weight", "layers.5.feed_forward.w2.weight", "layers.5.ffn_norm.weight", "layers.5.attention_norm.weight", "layers.6.attention.wqkv.weight", "layers.6.attention.wo.weight", "layers.6.feed_forward.w1.weight", "layers.6.feed_forward.w3.weight", "layers.6.feed_forward.w2.weight", "layers.6.ffn_norm.weight", "layers.6.attention_norm.weight", "layers.7.attention.wqkv.weight", "layers.7.attention.wo.weight", "layers.7.feed_forward.w1.weight", "layers.7.feed_forward.w3.weight", "layers.7.feed_forward.w2.weight", "layers.7.ffn_norm.weight", "layers.7.attention_norm.weight", "layers.8.attention.wqkv.weight", "layers.8.attention.wo.weight", "layers.8.feed_forward.w1.weight", "layers.8.feed_forward.w3.weight", "layers.8.feed_forward.w2.weight", "layers.8.ffn_norm.weight", "layers.8.attention_norm.weight", "layers.9.attention.wqkv.weight", "layers.9.attention.wo.weight", "layers.9.feed_forward.w1.weight", "layers.9.feed_forward.w3.weight", "layers.9.feed_forward.w2.weight", "layers.9.ffn_norm.weight", "layers.9.attention_norm.weight", "layers.10.attention.wqkv.weight", "layers.10.attention.wo.weight", "layers.10.feed_forward.w1.weight", "layers.10.feed_forward.w3.weight", "layers.10.feed_forward.w2.weight", "layers.10.ffn_norm.weight", "layers.10.attention_norm.weight", "layers.11.attention.wqkv.weight", "layers.11.attention.wo.weight", "layers.11.feed_forward.w1.weight", "layers.11.feed_forward.w3.weight", "layers.11.feed_forward.w2.weight", "layers.11.ffn_norm.weight", "layers.11.attention_norm.weight", "layers.12.attention.wqkv.weight", "layers.12.attention.wo.weight", "layers.12.feed_forward.w1.weight", "layers.12.feed_forward.w3.weight", "layers.12.feed_forward.w2.weight", "layers.12.ffn_norm.weight", "layers.12.attention_norm.weight", "layers.13.attention.wqkv.weight", "layers.13.attention.wo.weight", "layers.13.feed_forward.w1.weight", "layers.13.feed_forward.w3.weight", "layers.13.feed_forward.w2.weight", "layers.13.ffn_norm.weight", "layers.13.attention_norm.weight", "layers.14.attention.wqkv.weight", "layers.14.attention.wo.weight", "layers.14.feed_forward.w1.weight", "layers.14.feed_forward.w3.weight", "layers.14.feed_forward.w2.weight", "layers.14.ffn_norm.weight", "layers.14.attention_norm.weight", "layers.15.attention.wqkv.weight", "layers.15.attention.wo.weight", "layers.15.feed_forward.w1.weight", "layers.15.feed_forward.w3.weight", "layers.15.feed_forward.w2.weight", "layers.15.ffn_norm.weight", "layers.15.attention_norm.weight", "layers.16.attention.wqkv.weight", "layers.16.attention.wo.weight", "layers.16.feed_forward.w1.weight", "layers.16.feed_forward.w3.weight", "layers.16.feed_forward.w2.weight", "layers.16.ffn_norm.weight", "layers.16.attention_norm.weight", "layers.17.attention.wqkv.weight", "layers.17.attention.wo.weight", "layers.17.feed_forward.w1.weight", "layers.17.feed_forward.w3.weight", "layers.17.feed_forward.w2.weight", "layers.17.ffn_norm.weight", "layers.17.attention_norm.weight", "layers.18.attention.wqkv.weight", "layers.18.attention.wo.weight", "layers.18.feed_forward.w1.weight", "layers.18.feed_forward.w3.weight", "layers.18.feed_forward.w2.weight", "layers.18.ffn_norm.weight", "layers.18.attention_norm.weight", "layers.19.attention.wqkv.weight", "layers.19.attention.wo.weight", "layers.19.feed_forward.w1.weight", "layers.19.feed_forward.w3.weight", "layers.19.feed_forward.w2.weight", "layers.19.ffn_norm.weight", "layers.19.attention_norm.weight", "layers.20.attention.wqkv.weight", "layers.20.attention.wo.weight", "layers.20.feed_forward.w1.weight", "layers.20.feed_forward.w3.weight", "layers.20.feed_forward.w2.weight", "layers.20.ffn_norm.weight", "layers.20.attention_norm.weight", "layers.21.attention.wqkv.weight", "layers.21.attention.wo.weight", "layers.21.feed_forward.w1.weight", "layers.21.feed_forward.w3.weight", "layers.21.feed_forward.w2.weight", "layers.21.ffn_norm.weight", "layers.21.attention_norm.weight", "layers.22.attention.wqkv.weight", "layers.22.attention.wo.weight", "layers.22.feed_forward.w1.weight", "layers.22.feed_forward.w3.weight", "layers.22.feed_forward.w2.weight", "layers.22.ffn_norm.weight", "layers.22.attention_norm.weight", "layers.23.attention.wqkv.weight", "layers.23.attention.wo.weight", "layers.23.feed_forward.w1.weight", "layers.23.feed_forward.w3.weight", "layers.23.feed_forward.w2.weight", "layers.23.ffn_norm.weight", "layers.23.attention_norm.weight", "layers.24.attention.wqkv.weight", "layers.24.attention.wo.weight", "layers.24.feed_forward.w1.weight", "layers.24.feed_forward.w3.weight", "layers.24.feed_forward.w2.weight", "layers.24.ffn_norm.weight", "layers.24.attention_norm.weight", "layers.25.attention.wqkv.weight", "layers.25.attention.wo.weight", "layers.25.feed_forward.w1.weight", "layers.25.feed_forward.w3.weight", "layers.25.feed_forward.w2.weight", "layers.25.ffn_norm.weight", "layers.25.attention_norm.weight", "layers.26.attention.wqkv.weight", "layers.26.attention.wo.weight", "layers.26.feed_forward.w1.weight", "layers.26.feed_forward.w3.weight", "layers.26.feed_forward.w2.weight", "layers.26.ffn_norm.weight", "layers.26.attention_norm.weight", "layers.27.attention.wqkv.weight", "layers.27.attention.wo.weight", "layers.27.feed_forward.w1.weight", "layers.27.feed_forward.w3.weight", "layers.27.feed_forward.w2.weight", "layers.27.ffn_norm.weight", "layers.27.attention_norm.weight", "layers.28.attention.wqkv.weight", "layers.28.attention.wo.weight", "layers.28.feed_forward.w1.weight", "layers.28.feed_forward.w3.weight", "layers.28.feed_forward.w2.weight", "layers.28.ffn_norm.weight", "layers.28.attention_norm.weight", "layers.29.attention.wqkv.weight", "layers.29.attention.wo.weight", "layers.29.feed_forward.w1.weight", "layers.29.feed_forward.w3.weight", "layers.29.feed_forward.w2.weight", "layers.29.ffn_norm.weight", "layers.29.attention_norm.weight", "norm.weight", "output.weight", "fast_embeddings.weight", "fast_layers.0.attention.wqkv.weight", "fast_layers.0.attention.wo.weight", "fast_layers.0.feed_forward.w1.weight", "fast_layers.0.feed_forward.w3.weight", "fast_layers.0.feed_forward.w2.weight", "fast_layers.0.ffn_norm.weight", "fast_layers.0.attention_norm.weight", "fast_layers.1.attention.wqkv.weight", "fast_layers.1.attention.wo.weight", "fast_layers.1.feed_forward.w1.weight", "fast_layers.1.feed_forward.w3.weight", "fast_layers.1.feed_forward.w2.weight", "fast_layers.1.ffn_norm.weight", "fast_layers.1.attention_norm.weight", "fast_layers.2.attention.wqkv.weight", "fast_layers.2.attention.wo.weight", "fast_layers.2.feed_forward.w1.weight", "fast_layers.2.feed_forward.w3.weight", "fast_layers.2.feed_forward.w2.weight", "fast_layers.2.ffn_norm.weight", "fast_layers.2.attention_norm.weight", "fast_layers.3.attention.wqkv.weight", "fast_layers.3.attention.wo.weight", "fast_layers.3.feed_forward.w1.weight", "fast_layers.3.feed_forward.w3.weight", "fast_layers.3.feed_forward.w2.weight", "fast_layers.3.ffn_norm.weight", "fast_layers.3.attention_norm.weight", "fast_layers.4.attention.wqkv.weight", "fast_layers.4.attention.wo.weight", "fast_layers.4.feed_forward.w1.weight", "fast_layers.4.feed_forward.w3.weight", "fast_layers.4.feed_forward.w2.weight", "fast_layers.4.ffn_norm.weight", "fast_layers.4.attention_norm.weight", "fast_layers.5.attention.wqkv.weight", "fast_layers.5.attention.wo.weight", "fast_layers.5.feed_forward.w1.weight", "fast_layers.5.feed_forward.w3.weight", "fast_layers.5.feed_forward.w2.weight", "fast_layers.5.ffn_norm.weight", "fast_layers.5.attention_norm.weight", "fast_norm.weight", "fast_output.weight".
        ```

@leng-yue  ( 求救救 🥺

小数据多 worker 卡死我可能还得试试能不能复现，感谢您的 PR #284 修复了合并问题。


https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details
On
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp

search for
can more results

I believe you are missing a verb. And I am not sure that 'results' is the right word. I suggest
can match a wider range of strings

But I will be happy with any wording that is accurate and clear

Thank you for pointing that out to us. I have updated the text to:
"Patterns can include special characters so they can match a wider range of values than would a literal string."

Good change. In this context, 'values' is a better word than 'strings'. And probably would be even if there were not a conflicting use of 'string' later in the sentence.
I had a feeling there was a reason that Mozilla has you 🧠✍ writing the documentation instead of me!

Thanks! Compliments always appreciated.


[#4888] [Slack Adapter] Make messages with attachments into message activities

Fixes #4888
Description
Updates the Slack Adapter to resolve received messages with attachments as ActivityTypes.Message, allowing users to access the text and attachment properties from the root activity.
THIS IS A BREAKING CHANGE
Messages with attachments will be received "on message" activities instead of "on event" activities.
The change makes attachment messages more akin to ABS, which also interprets them as message activities but lacks the text property, using the attachment name instead.

Specific Changes

Adds received messages with attachments to the filter to resolve them as message activities.

Obtains each file's properties manually to parse them into Attachments

Testing
The changes were tested in unit and functional tests with no issues, since there are no message with attachment tests affected.

@denscollo, could you please see the request above?

@carlosscastro @mrivera-ms sure! We are currently working on it, as soon as we have it ready we'll let you know. Thanks!

@carlosscastro @mrivera-ms We just pushed the changes with the new test.


Allow clients to define the padding for Input and DropdownButton

Complex forms contain many types of input elements (checkboxes, dropdowns, pickers). It is difficult to use a consistent input labeling mechanism approved by Material. Take a look at this for instance:

The dropdown input labels "From" and "To" would match perfectly to what the input label will look like for "Location" once a value is entered. In reality, this would be a hack in the client app's code because Location's style and size is provided by the input widget while the "From"/"To" labels of the dropdowns are explicitly drawn by the app.
Leafy chose to fix this by disabling material labeling for all form elements and instead providing a consistent labeling mechanism. Unfortunately, this breaks when intrinsic padding is introduced. Examples:

Top and bottom padding on Input
Top and bottom padding on DropdownButton
Start and end padding on Slider

It would be great if clients could specify the padding (if any) for these elements.

@mpcomplete is mr. forms.

Another way to solve this is to standardize labeling across all form elements. That would be very neat and it would not require any workaround on the app side. That way, Input would require no change but things like Slider, Checkbox, DropdownButton would optionally take a "label" argument which would create a label similar to Input's label with the same font/padding/size.

https://github.com/flutter/flutter/issues/254 is another (long standing) issue about making associating a label with a control much easier.

The dropdown input labels "From" and "To" would match perfectly to what the input label will look like for "Location" once a value is entered. ...

I'm not entirely sure what you're getting at here.  I'm guessing that you want to be able to line up the baselines of the label and the dropdown's value?

Fixing #6421 would automatically fix this for the From and To fields here, right?

I spoke with @mehmetf and he clarified that this bug is basically about making sure all the existing input controls (checkboxes, radio buttons, sliders, dropdowns, etc) can be used with the widget we create for #6421 in such a way that they all line up (i.e. removing any default padding in that case).
We could do this by having #6421's widget set some sort of inherited widget that controls whether or not to show default padding, or we could make it simpler and just remove the padding on existing widgets (slider in particular), or make it configurable.


Submit jNeuroML 0.8.5

id: jneuroml
version: 0.8.5
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_pyNeuroML/27c2c97bc9192984e719880a96c1c3d1b4611b72/biosimulators-jneuroml.json
specificationsPatch:
version: 0.8.5
validateImage: false
commitSimulator: true

Changelog

restarted because API was down

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, and committing your simulator to the BioSimulators registry. You have chosen not to have the Docker image for your simulator validated.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job will be available for 90 days here.

The validation/submission of your simulator failed.
- HTTPSConnectionPool(host='api.biosimulators.org', port=443): Max retries exceeded with url: /simulators/validate (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7ff19d23cdf0>: Failed to establish a new connection: [Errno 110] Connection timed out'))

The complete log of your validation/submission job, including further information about the failure, is available for 90 days here.
If you chose to validate your Docker image, the results of the validation of your image will be available shortly as a JSON file. A link to this file will be available for 90 days from the "Artifacts" section at the bottom of this page.
Once you have fixed the problem, edit the first block of this issue to re-initiate this validation.
The BioSimulators Team is happy to help. Questions and feedback can be directed to the BioSimulators Team by posting comments to this issues that reference the GitHub team @biosimulators/biosimulators (without the backticks).

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, and committing your simulator to the BioSimulators registry. You have chosen not to have the Docker image for your simulator validated.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job will be available for 90 days here.

The specifications of your simulator is valid!

Your submission was committed to the BioSimulators registry. Thank you!
Future submissions of subsequent versions of jneuroml to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, and committing your simulator to the BioSimulators registry. You have chosen not to have the Docker image for your simulator validated.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job will be available for 90 days here.

The specifications of your simulator is valid!

Your submission was committed to the BioSimulators registry. Thank you!
Future submissions of subsequent versions of jneuroml to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.


Add to model a list of models in one call

<model>.add(List<Model> list)

@yanchevsky suggests to insert all records in one SQL statement. Examples:
SQLServer
2008 and >
INSERT INTO MyTable (id, name) VALUES (1, 'Bob'), (2, 'Peter'), (3, 'Joe');
MySQL
INSERT INTO tbl_name
(a,b,c)
VALUES
(1,2,3),
(4,5,6),
(7,8,9);
Oracle
INSERT ALL
INTO t (col1, col2, col3) VALUES ('val1_1', 'val1_2', 'val1_3')
INTO t (col1, col2, col3) VALUES ('val2_1', 'val2_2', 'val2_3')
INTO t (col1, col2, col3) VALUES ('val3_1', 'val3_2', 'val3_3')
PostgreSQL
INSERT INTO films (code, title, did, date_prod, kind) VALUES
('B6717', 'Tampopo', 110, '1985-02-10', 'Comedy'),
('HG120', 'The Dinner Game', 140, DEFAULT, 'Comedy');
H2
INSERT INTO table VALUES (.., .., ...), (.., .., ...), ... (.., .., ...);
SQLite3
INSERT INTO table1 (
column1,
column2 ,..)
VALUES
(
value1,
value2 ,...),
(
value1,
value2 ,...),
...
(
value1,
value2 ,...);
http://www.sqlitetutorial.net/sqlite-insert/
Additionally, the following checks need to be performed:

All models in list need to be the same type
Models in list need to be real dependencies of current model

Implementation:

For One to Many and Polymorphic this means adding records into a child table.
For Many to Many it means adding records  into a join table.


fix up a typo in extraEnvs

@jufa2401 This should be published now as 2023.4.2. Thanks again for pointing that out!


changed way of generating temporary file path

Hi,
Path.GetTempFileName() generates predictable file names and is inherently unreliable and insecure. Additionally, the method will raise an IOException if it is used to create more than 65535 files without deleting previous temporary files.
https://rules.sonarsource.com/csharp/RSPEC-5445

@microsoft-github-policy-service agree

/azp run


Result of JavaTemplate inserting statements in before coordinates of first method decl statement fails to render

borne out of https://github.com/openrewrite/rewrite/pull/244 specifically https://github.com/openrewrite/rewrite/pull/244#discussion_r573141959
We should be able to use the following template in CovariantEquals inserted before the first Statement of a MethodDeclaration using Coordinates, e.g.

                "if (#{} == this) return true;\n" +
                "if (#{} == null || getClass() != #{}.getClass()) return false;\n" +
                "#{} #{} = (#{}) #{};"

with the insertion point being m.getbody().getStatements().get(0).getCoordinates().before()
However the resultant template is not inserted back into the method body, e.g.
----Template After Substitutions----
if (obj == this) return true;
if (obj == null || getClass() != obj.getClass()) return false;
A other = (A) obj;
------Generated Synthetic Class-----
class A {
    String id;
    @SuppressWarnings("all")
    public boolean equals(A other) {
    }
}

After adding that, you can see the template is correctly populated with parameters...but not being inserted into the synthetic class.

This issue is fixed with this commit : 19b99faaa5a0055375cc563a659e5c2b044e79e8


department select list and data

@PFwhite there is a CI failure on this branch

@PFWhite As I was worried about, changing the column does not remove the data. So, the migration ends up failing due to foreign key constraints. We may need to dump the column first before applying the migration. On a side note, removing the expertise migration in 0006...1603.py seems to fix the other issue where it failed.


Fix namespace collision deprecation warnings

Fixes the namespace collision deprecation warnings in recent Chef versions.
Description
Using the short form of property_name inside resources is deprecated and will be removed in favour of new_resource.property_name to avoid collisions between properties in different scopes.
This fixes a large list of deprecation warnings produced by the current version.
Issues Resolved
#400 may be relevant although that actually appears to be referring to other properties that have already been removed.
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[x] (NA) New functionality includes testing.
[x] (NA) New functionality has been documented in the README if applicable
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

the tests for this are actually all passing, but a different one has suffered a network-related failure on each of the last couple of runs. As I'm not a collaborator, I can't restart just the failed test on travis.
This actually fixes all the failing tests from the current master AFAICS

@tas50 it's slightly concerning to see new releases going out when the travis build is still red (and has been for some time...). This PR fixes all the current deprecation warnings / failing travis tests - any chance it could be reviewed and merged?

That release was a bit of a yak shave. I needed that release out the door to cleanup client installation deprecation warnings. I knew we still had quite a few warnings in place, thus the red builds, but the actual cookbook was functional. Thanks for getting this put together. I'll run it through and see if I can get this shipped today.

@tas50 thanks very much.


I can't deplay on vercel

I got the error as below

Please tell me how to fix it?

Thank you so much for raising this issue. It has been resolved now.
Just need to deploy the master branch once more in vercel

It works. Thank you

Do you have online document?


feat(#24): Add OptimizationTest

Add OptimizationTest class.

feat(#24): Add OptimizationTest
feat(#24): Remove the old puzzle and add one more new puzzle

Closes: #24.

PR-Codex overview
This PR focuses on adding unit tests and implementing back transformation to bytecode in the Optimization class.
Detailed summary

Added unit tests for the Optimization class.
Implemented back transformation to bytecode in the Optimization class.
Added a new Mock boost class.
Added a new test case for the Optimization class.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here


Build Error After Upgrading to targetSDK 34

I am getting following build error in android after upgrading to targetSDK 34
Failed to transform billing-ktx-7.0.0.aar (com.android.billingclient:billing-ktx:7.0.0) to match attributes {artifactType=android-dex, asm-transformed-variant=NONE, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=21, org.gradle.category=library, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-runtime}.

Could you try updating your build.gradle file like below?
// In your root build.gradle file
buildscript {
    dependencies {
        classpath 'com.android.tools.build:gradle:7.0.0' // or a compatible version
    }
}

// In your gradle-wrapper.properties file
distributionUrl=https\://services.gradle.org/distributions/gradle-7.0-bin.zip // or a compatible version

Also try to clean and rebuild
./gradlew clean
./gradlew build

If the issue persists, we need additional information to accurately diagnose the cause. Please provide the following details:

PC environment (operating system, version, etc.)
Information about the Android device you are using
React Native version
List of other dependencies in the project

Providing this information will help us diagnose and resolve the issue more precisely.

@Girum upgrade minSdkVersion to 24

@Girum upgrade minSdkVersion to 24

This worked for me where nothing else would, thank you.

I encountered this problem too, and I'd like to keep my minSdkVersion at 21 so I looked a little further and found this:
https://stackoverflow.com/questions/78113826/failed-to-transform-firebase-auth-22-3-1-aar/78149818#78149818
I added the following two lines to my debug build type in /android/app/build.gradle:
...
buildTypes {
        debug {
            minifyEnabled true
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
...

but I found that I was getting crashes on startup due to the obfuscation.  I was able to fix it by adding the following line to /android/app/proguard-rules.pro:
-keep class com.facebook.** {*;}
I'm still not happy with the solution since I don't really want obfuscated code in debug builds and also there must be some react-native proguard rules that are getting picked up in release builds but not debug builds that I should be tapping into rather than the blanket keep I'm using here, but I thought I'd post this in case anyone else is having issues.

I have face same issue when I have installed
"@react-native-google-signin/google-signin": "^13.1.0", in react-native
need to update the config as below
open android/build.gradle
buildscript {  ext {     minSdkVersion = 24     compileSdkVersion = 34     targetSdkVersion = 34  } }


Close all others

Close all others with command+option+w

Great idea! I would love a keybinding to do that.
The only problem is that I think this functionality escapes our initial proposal of preventing unintentional workspace shutdowns. This idea is more related to tabs organization.
Also, you can achieve that without adding any plugins. You can go to Settings > Keybindings > your keymap fileand add the desired keybindings.

Nice :-)

Nice :-)


Implement multi account module

Multi Account Module
A module with multisig functionality with a static AccountId and a dynamic threshold and set of signatories.
Overview
This module contains functionality to create, update and remove multi accounts, identified by a deterministicallygenerated account ID, as well as (potentially) stateful multisig dispatches.
This module is closely implemented after the multisig functionality of the utility pallet. The main difference is that this module stores static account ids on chain which are not changing when the threshold or signatories are updated.
This module allows multiple signed origins (accounts) to coordinate and dispatch calls from a previously created multi account origin. When dispatching calls, the threshold defined in the multi account defines the number of accounts from the multi account signatory set that must approve it. In the case that the threshold is just one then this is a stateless operation. This is useful for multisig wallets where cryptographic threshold signatures are not available or desired or where a dynamic set of signatories with a static account ID is desired.
The motivation for this module is that a deterministically created account ID from threshold and a set of
signatories as in the utility pallet has certain downsides:

When using multisigs for token holdings and changing signatories or the threshold, the tokens need to be transferred to a new account ID, which might be a taxable event, depending on jurisdiction. Even if it's not, it complicates communication with accountants/tax advisors.
When using multisigs for staking and changing signatories or the threshold, the account needs to unbond, transfer tokens and re-stake again. That can lead to months of lost staking rewards, depending on the unbonding time.
When using multisigs for voting and changing signatories or the threshold, the accounts needs to unvotes, transfer tokens and vote again, which is cumbersome.

The downside of using this multi account module is that it is slightly more complex than the utility multisigs and that it introduces additional state and the requirement of creating multi accounts before using multisigs.
Interface
Dispatchable Functions
For multi account management

create - Create a new multi account with a threshold and given signatories.
update - Update an existing multi account with a new threshold and new signatories.
remove - Remove an existing multi account.

For multisig dispatch

call - Approve and if possible dispatch a call from a multi account origin.
approve - Approve a call from a multi account origin.
cancel - Cancel a call from a multi account origin.

Edge Cases
Update:
Multi account thresholds and signatories can only be updated and removed if all active/ongoing multisig operations have been cancelled. That eliminates all of the previous edge cases outlined below. To prevent an outgoing multi account member to block updates/removals, the multi account itself can cancel any active multisig.

Approve/dispatch multisig
Cancel multisig

1. Multisig owner no longer in signatories
Only current signatories should count for approvals
Owner should still be able to cancel

2. Multisig approver no longer in signatories
Only current signatories should count for approvals
Owner should be able to cancel

3. Multi account removed
Approvals/dispatch should not be possible anymore
Owner should still be able to cancel

Multi account changed: Multisig owner no longer in signatories

[x] The owner should still be able to cancel the multisig, even after he left the signatories of the multi account, to get back their deposit.
[x] The multisig can still be approved and dispatched, even if the owner is no longer one of the signatories, as long as the number of approvals through the current signatories is >= the threshold. The original owner should get back their deposit.

Multi account changed: Multisig approver no longer in signatories

[x] At the time of dispatch, only approvals from current signatories should be counted, not from signatories that are no longer part of the multi account. (Can be done either by filtering the approval list immediately before the dispatch, or by updating all the approvals of all multisigs when updating the multi account's signatories. The former is prefrrable, since that search is bounded by the signatory size, while updating all multisigs is unbounded.).
[x] ~~The multisig can still be approved and dispatched, even if one of the approvers is no longer in the signatory set, as long as the number of approvals through the current signatories is >= the threshold. ~~

Multi account removed

[x] Multisigs should not be allowed to be approved and/or dispatched after a multi account has been approved.
[x] Multisigs should still be allowed to be cancelled by the owner, even if a multi account has been removed.

Questions

[ ] Are there any security implications of using just a string and a nonce for multi account id generation? If yes, how can this be improved?
[x] Is a PR to https://github.com/polkadot-js/api necessary (cc @jacogr)?

Misc
Closes #4834.

No PR there needed. But if accepted, there will be some work to add the required types for proper support. (Help there will be appreciated, although not required)

Added a few notes on missing tests/edge cases above.

Added tests and handling of all the edge cases described above.

IIUC this would no longer be breaking at all if you don't increment spec version. as it exists atm, this PR doesn't touch the runtime at all so incrementing the runtime spec version is not necessary.
I would put the integration into the substrate runtime into a separate PR if you find it necessary. otherwise I would remove the change to lib.rs

Thanks, I just removed the spec version increase. This makes a check fail though.

We have created a dedicated repository for this pallet: https://github.com/centrifuge/substrate-pallet-multi-account
I keep this PR open though in the hope that it will still be merged – to be audited and reviewed as a part of Substrate.
Thanks for all the feedback so far, that helped a lot!

@philipstanislaus Thanks for your PR.
As we discussed offline, this PR will not get merged into Substrate. Unfortunately, every pallet in our repository adds additional overhead to the Parity team in terms of maintenance and support. Especially given the fact we will not use this pallet in any of our core projects (Substrate Node, Polkadot/Kusama Node), it is even more likely that some breaking change/bug is introduced and we miss it. This would be bad for everyone involved.
We encourage all Substrate developers to create new and useful pallets, but contribute them to the community just like any open-source project. Parity does not intend to be the only place where pallets are found. We hope in the long term, we our pallets are just one choice in pool of many options for different runtime developers.
I hope the review I gave was sufficient for your needs, and I hope that you will include this pallet into your runtime and as a part of an open source repository so others can use it.
Thanks, and feel free to follow up with me about any concerns you might have!

@shawntabrizi understood, thanks for the context and especially your valuable feedback in the process.
We improved a few things with the multi account pallet and performed an internal audit as well (3 other engineers were involved in it). It is used in our chain right now.
Here is the link again for anyone that would like to use it: https://github.com/centrifuge/substrate-pallet-multi-account


Error loading the key.pem cert. into the docker container

While running this image, it keeps bringing an exception about loading the key.pem certificate file. I tried to edit the docker-compose.yml "SOLID_SSL_KEY" from key.pem to privkey.pem "like certbot generated one" but it didn't work.
here is the exception stack
server_1_bcc3baf06840 | Generating a RSA private key server_1_bcc3baf06840 | ..........................................................................................+++++ server_1_bcc3baf06840 | ........................................................................................................+++++ server_1_bcc3baf06840 | writing new private key to './solid-temporary.key' server_1_bcc3baf06840 | ----- server_1_bcc3baf06840 | Finished: SUCCESS server_1_bcc3baf06840 | TIP create a config.json: $ solid initserver_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Server URI: https://mohamedsaidhamed.org server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Auth method: oidc server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Strict origins: true server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Allowed origins: server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Db path: ./.db server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Config path: ./config server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Suffix Acl: undefined server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Suffix Meta: undefined server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Filesystem Root: none server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Allow WebID authentication: true server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Live-updates: true server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Multi-user: false server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Suppress default data browser app: undefined server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Default data browser app file path: default server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings Base URL (--mount): / server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings SSL Private Key path: /opt/solid/certs/key.pem server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:settings SSL Certificate path: /opt/solid/certs/fullchain.pem server_1_bcc3baf06840 | ERROR Can't find SSL key in /opt/solid/certs/key.pem server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:authentication Provider keys loaded from config server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:authentication Provider keychain initialized server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:authentication Not sleeping before client registration... server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:authentication Client not present for issuer https://mohamedsaidhamed.org, initializing new client server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:authentication Registering new client for issuer  https://mohamedsaidhamed.org server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:authentication Error registering a new client:  { FetchError: request to https://mohamedsaidhamed.org/.well-known/openid-configuration failed, reason: read ECONNRESET server_1_bcc3baf06840 |     at ClientRequest.<anonymous> (/usr/local/lib/node_modules/solid-server/node_modules/node-fetch/lib/index.js:1444:11) server_1_bcc3baf06840 |     at ClientRequest.emit (events.js:189:13) server_1_bcc3baf06840 |     at TLSSocket.socketErrorListener (_http_client.js:392:9) server_1_bcc3baf06840 |     at TLSSocket.emit (events.js:189:13) server_1_bcc3baf06840 |     at emitErrorNT (internal/streams/destroy.js:82:8) server_1_bcc3baf06840 |     at emitErrorAndCloseNT (internal/streams/destroy.js:50:3) server_1_bcc3baf06840 |     at process._tickCallback (internal/process/next_tick.js:63:19) server_1_bcc3baf06840 |   message: server_1_bcc3baf06840 |    'request to https://mohamedsaidhamed.org/.well-known/openid-configuration failed, reason: read ECONNRESET', server_1_bcc3baf06840 |   type: 'system', server_1_bcc3baf06840 |   errno: 'ECONNRESET', server_1_bcc3baf06840 |   code: 'ECONNRESET' } server_1_bcc3baf06840 | Thu, 11 Apr 2019 03:35:19 GMT solid:authentication Error initializing local RP client:  { FetchError: request to https://mohamedsaidhamed.org/.well-known/openid-configuration failed, reason: read ECONNRESET server_1_bcc3baf06840 |     at ClientRequest.<anonymous> (/usr/local/lib/node_modules/solid-server/node_modules/node-fetch/lib/index.js:1444:11) server_1_bcc3baf06840 |     at ClientRequest.emit (events.js:189:13) server_1_bcc3baf06840 |     at TLSSocket.socketErrorListener (_http_client.js:392:9) server_1_bcc3baf06840 |     at TLSSocket.emit (events.js:189:13) server_1_bcc3baf06840 |     at emitErrorNT (internal/streams/destroy.js:82:8) server_1_bcc3baf06840 |     at emitErrorAndCloseNT (internal/streams/destroy.js:50:3) server_1_bcc3baf06840 |     at process._tickCallback (internal/process/next_tick.js:63:19) server_1_bcc3baf06840 |   message: server_1_bcc3baf06840 |    'request to https://mohamedsaidhamed.org/.well-known/openid-configuration failed, reason: read ECONNRESET', server_1_bcc3baf06840 |   type: 'system', server_1_bcc3baf06840 |   errno: 'ECONNRESET', server_1_bcc3baf06840 |   code: 'ECONNRESET' }

Hi Mohamed, thanks for your report.
To be able to help you, I need some additional information:

What operation system is your host running on?
Are you mounting the certificate files from your host file system or another docker volume?
Are the files accessible by UID 1000? (key.pem as SOLID_SSL_KEY and fullchain.pem as SOLID_SSL_CERT should be the correct ones)
Do you have any security mechanism like SELinux running?

You could try executing into the container with docker exec ... or open a shell in a new container with docker run -it --entrypoint sh ... and try to read the files from perspective of the container.  Does this work?

The message comes from this code section in NSS, so something goes wrong accessing the file:
https://github.com/solid/node-solid-server/search?q=Can't+find+SSL+key+in&unscoped_q=Can't+find+SSL+key+in
Unfortunately the original error message is swallowed by NSS...

I'm running Ubuntu server 18.04
I'm mounting them from my host file system
Yes they are accessible by UID:1000
SELinux is disabled

Please run openssl rsa -in key.pem -check to check if your keyfile is ok. It should say "RSA key ok"  and print the private key.
Have you tried the docker exec command to see from perspective of the container?

The problem seams to be caused by only mounting the letsencrypt folder containing the symlinks, but not the actual cert / key files. https://superuser.com/questions/1357862/how-to-mount-certificates-from-certbot-to-use-inside-docker-container

Thank to @angelo-v, The problem was resolved by loading the whole letsencrypt folder into the docker container and making sure that it has the right permissions.


Size of the single cell dataset

Hey, thanks a lot for this wonderful package. I've been experimenting with it, and the results have been very accurate according to the pathologists.
I have a question about the size of the single-cell dataset. I guess that the bigger the dataset, the more data and the better would be the results. However, I'm unsure about the optimal number of cells I should aim for when generating a single-cell dataset. I'm trying to find the right balance between performance and cost-effectiveness. Of course there is not correct answer, but if you could provide some insights I will appreciate it
For instance, would a dataset with 4k cells be sufficient, or should I aim for a larger number? Are there any research papers or methods that explore this correlation?
Jaime

You need to aim for sufficient representation of your populations of interest. In some rare cases, very few cells can suffice to define informative reference gene expression signatures (eg 10 cells). However, I would generally recommend 100s of cells per population of interest (at least 40-50 rarer cells). For an atlas of one tissue, you can get a decent reference with 40k cells (eg. mouse brain data in our paper).


Handle Sense pin in an open-collector fashion

The Sense pin on the original Datassette is a physical switch that only grounds the line when pressed, it's left floating when no keys are pressed. This means that the pin should be driven in an open-collector fashion, otherwise it can create problems, in particular on the Plus/4 where the Sense line is shared with data pin 2 of the User Port.
This could be compensated in hardware (put a diode in series, cathode to Arduino side) or in software, by taking advantage of the way ATmega pins are configured, which is what we do here:

To set sense "high" we set the pin to input mode, pin will go Hi-Z and basically float (it will be pulled up on the computer side)
To set it low, we switch to output mode which will implicitly be low (PORTD defaults to 0 and we never touch it)

This change is tested and working on Plus/4.

Hi and thanks for the PR, I didn't realise this and that there were issues with the Plus4.
Have you tested this on a C64 as well? I'm happy to merge on confirmation of that.

Well, maybe no one realized so far because there's not that much hardware for the userport on the +4 :). But I'm working on porting the WiC64 interface and this hit me immediately.
I was planning on doing the C64 test yesterday but got stuck into preparations for my holidays. I will test once I'm back and will report accordingly, but it would be very surprised if it doesn't work as I have checked the schematics and the Sense line pull-up resistor is right there.

Ok great. I'll try and give it a test myself, but all my kit is packed away, so might take some time. Let me know and if I get to it first and it's all good, I'll merge. Enjoy your holidays! :)

Tested and working fine on C64!

Merged! Thank you!