text:
Add register & profile performance profiling, disable jobs and allow dismissing loader view

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #[issue number] or Closes #[issue number]
Engineer Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app

Code Reviewer Checklist

[ ] I have verified Unit tests have been written for any new feature(s) and edge cases
[ ] I have verified any strings visible on UI components are in the strings.xml file
[ ] I have verifed the CHANGELOG.md file has any notable changes to the codebase
[ ] I have verified the solution has been implemented in a configurable and generic way for reuseable components
[ ] I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

@ellykits Here is the code for profiling
Attached is the data set that should be loaded with app/debug since this allows the app to load resources from local configs
resources.zip
Make sure to run
CREATE INDEX IF NOT EXISTS `index_DateTimeIndexEntity_index_from` ON `DateTimeIndexEntity` (`index_from`)

on the database before copying it onto the device to replace the current one

can we make this configurable with a debug or a new profile flag and get this merged in?

the commented jobs that is

@pld We are considering writing benchmarks for specific areas of code using Jetpack Microbenchmark library. After the kotlin DSL migration PR is merged and dependencies upgraded. Closing this PR (was used while measuring register/profile) data load performance - currently being undertaken by the QA team.
cc: @ekigamba

authors: ekigamba ellykits pld

repo: opensrp/fhircore


text:
why openssl use ecb mode for CTR-Drbg?

Hi,
I am reading the DRBG code and I found drbg use ecb mode  for CTR-DRBG, why didn't use CTR mode or CBC mode for this?
https://github.com/openssl/openssl/blob/a47dd08d6cacc64536c2f57e0f0aee03dcfaab3d/crypto/rand/drbg_ctr.c#L429

Google Sp800-90

Closing since this has been answered.

source: gharchive/issue

authors: joymcg paulidale slontis

repo: openssl/openssl

license_type: permissive

license_source: github-api


text:
OpenSSL 3.0 hangs on exit with FIPS and badly formatted config file

If the FIPS provider is loaded manually and the providers section of the config file contains any lines with name=value where no [value] section exists, OpenSSL hangs on exit().
Section 7.1 of https://wiki.openssl.org/index.php/OpenSSL_3.0 says to put these lines "near the beginning" of the config file:
openssl_conf = openssl_init

.include /usr/local/ssl/fipsmodule.cnf

[openssl_init]
providers = provider_sect

[provider_sect]
fips = fips_sect

If these lines are placed at the very beginning of the config file, the existing default section becomes part of the [provider_sect] section and the existing HOME = . line causes OpenSSL to hang on exit() because there is no [.] section. Likewise, if you were to add foo = bar under [provider_sect] without creating a [bar] section, OpenSSL will hang on exit().
The problem only occurs under certain specific circumstances:

A bad config file exists as described above
The FIPS provider is loaded manually via OSSL_PROVIDER_load()
A digest algorithm is fetched via EVP_get_digestbyname()
The algorithm is actually used (e.g. by EVP_DigestInit_ex())

OR

A bad config file exists as described above
The FIPS provider is loaded manually via OSSL_PROVIDER_load()
A digest algorithm is fetched via EVP_MD_fetch() (whether or not it is actually used later)

OR

A bad config file exists as described above
The FIPS provider is loaded manually via OSSL_PROVIDER_load()
The FIPS provider is not unloaded via OSSL_PROVIDER_unload() prior to exit().

The first two scenarios above cause OpenSSL to hang whether or not the FIPS provider is manually unloaded prior to exit().

Note: this issue is a spinoff from thread OpenSSL 3.0 hangs at exit with FIPS provider on openssl-users.

i believe the Wiki docs are outdated, and that https://www.openssl.org/docs/manmaster/man5/config.html and https://www.openssl.org/docs/manmaster/man5/fips_config.html are more accurate.  In particular, there is really no reason for the FIPS config part to be "near the beginning" of the file.

This issue now seems to be fixed. I was able to reproduce this problem on a checkout from around the time that this issue was raised. However I am unable to do so on latest master. Therefore I'm closing this.

authors: mattcaswell mspncp richsalz tomiii00


text:
X509_ATTRIBUTE_create  core dumped

OpenSSL> version
OpenSSL 1.1.1k  25 Mar 2021

file stack_overflow.c :
  1 #include "openssl/x509.h"
  2
  3 int main(void)
  4 {
  5     int value = 0;
  6     X509_ATTRIBUTE *attr = NULL;
  7
  8     attr = X509_ATTRIBUTE_create(1, 0, &value);
  9     X509_ATTRIBUTE_free(attr);
 10
 11     return 0;
 12 }

output:
./stack_overflow.bin
*** Error in `./stack_overflow.bin': free(): invalid pointer: 0x00007fff529997a4 ***
Aborted (core dumped)

statck frame:
#0  0x00007f6355e86c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007f6355e8a028 in __GI_abort () at abort.c:89
#2  0x00007f6355ec32a4 in __libc_message (do_abort=do_abort@entry=1,
    fmt=fmt@entry=0x7f6355fd5350 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#3  0x00007f6355ecf82e in malloc_printerr (ptr=<optimized out>, str=0x7f6355fd149e "free(): invalid pointer", action=1)
    at malloc.c:4998
#4  _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3842
#5  0x00007f63565ec97d in CRYPTO_free (str=0x7ffe85d69744, file=0x7f63566b0cf8 "crypto/asn1/asn1_lib.c", line=343)
    at crypto/mem.c:312
#6  0x00007f63564cca4a in asn1_string_embed_free (a=0x7ffe85d69744, embed=0) at crypto/asn1/asn1_lib.c:343
#7  0x00007f63564d93a3 in asn1_primitive_free (pval=0x1e6f068, it=0x0, embed=0) at crypto/asn1/tasn_fre.c:204
#8  0x00007f63564d9372 in asn1_primitive_free (pval=0x7ffe85d69670, it=0x7f6356941800 <ASN1_ANY_it>, embed=0)
    at crypto/asn1/tasn_fre.c:199
#9  0x00007f63564d8e7e in asn1_item_embed_free (pval=0x7ffe85d69670, it=0x7f6356941800 <ASN1_ANY_it>, embed=0)
    at crypto/asn1/tasn_fre.c:51
#10 0x00007f63564d91ad in asn1_template_free (pval=0x1e6f018, tt=0x7f6356967208 <X509_ATTRIBUTE_seq_tt+40>)
    at crypto/asn1/tasn_fre.c:137
#11 0x00007f63564d90c1 in asn1_item_embed_free (pval=0x7ffe85d69708, it=0x7f635695e2a0 <X509_ATTRIBUTE_it>, embed=0)
    at crypto/asn1/tasn_fre.c:110
#12 0x00007f63564d8d64 in ASN1_item_free (val=0x1e6f010, it=0x7f635695e2a0 <X509_ATTRIBUTE_it>)
    at crypto/asn1/tasn_fre.c:20
#13 0x00007f635668cb10 in X509_ATTRIBUTE_free (a=0x1e6f010) at crypto/x509/x_attrib.c:33
#14 0x00000000004006ca in main () at stack_overflow.c:9

1.Core dump occurs in the above code.
2.I did not find the manpage document for X509_ATTRIBUTE_create.

1.Core dump occurs in the above code.

This appears to be due to misuse of the X509_ATTRIBUTE_create function. The first parameter is supposed to be the NID for some well known X509_ATTRIBUTE (e.g. NID_surname). The second parameter is supposed to be the ASN1 type associated with this value (e.g. V_ASN1_UTF8STRING), and the third parameter is supposed to be an ASN1_VALUE that corresponds to that type. The ownership of the value is passed to the X509_ATTRIBUTE as part of the call - so the X509_ATTRIBUTE will attempt to free it when X509_ATTRIBUTE_free is called. Passing an incorrect value during the create (e.g. a value that doesn't correspond to the type, or a non-malloced value that can't be freed) will result in a subsequent crash. This is considered an error in the application not in OpenSSL.
For example the following works correctly:
#include <string.h>
#include "openssl/x509.h"

int main(void)
{
    X509_ATTRIBUTE *attr = NULL;
    ASN1_UTF8STRING *value = NULL;

    value = ASN1_UTF8STRING_new();
    ASN1_STRING_set(value, "hello", strlen("hello"));

    attr = X509_ATTRIBUTE_create(NID_surname, V_ASN1_UTF8STRING, value);
    X509_ATTRIBUTE_free(attr);

    return 0;
}

2.I did not find the manpage document for X509_ATTRIBUTE_create.

There are many functions that do not have documentation. We are slowly improving the situation but contributions of documentation are always welcome.

I will try to contribute some functional documentation, and I may have a lot of questions in the process, which will also be a challenge to my English level.

authors: mattcaswell yangyangtiantianlonglong


text:
PEM_write_PrivateKey failed(app exit) on windows

OS: Windows 10 x64

Env: Visual Studio 2015

OpenSSL version: 1.1.0c

behavior
I'm trying to use PEM_write_PrivateKey() function to write the private keys into the file. It fails. The Win32 console screen closed automatically after this function called. And the key.pem file contains nothing.
Same problem already occurred, here and here. But nothing helpful.
Actually, PEM_write_X509() acts same way as PEM_write_PrivateKey().
How to reproduce
use this code on windows.

Right about here, you might want to add this line:
ERR_print_errors_fp(stderr);

Actually, there are a number of places where you might want to do that.  That will help you diagnose what goes wrong.
This being said, this is hardly an issue with OpenSSL itself.  The better place for this kind of question is the mailing list openssl-users@openssl.org.  See here for information on our mailing lists.
Closing this.

@levitte Thank you.

@spartucus I came across this today. For windows, we should set /MD  (Use Run-Time Library). In both debug and release configuration. It worked for me.

authors: guptachetan levitte spartucus


text:
Native Windows absolute paths are treated as URIs.

Discussed in https://github.com/openssl/openssl/discussions/21969

Originally posted by njbelf September  5, 2023
I'm sure I'm missing something.    Following is the error, the public key itself and pertinent config file entry.     What am I missing?
./openssl dgst -sha3-384 -verify C:\SampleKeys\key-a_public_key_secp384r1.pem -signature  H:\SHATestVectors\SHA3_384\SHA3_384_384_in.bin
Could not open file or uri for loading public key from C:\SampleKeys\key-a_publi
c_key_secp384r1.pem
78B80000:error:16000069:STORE routines:ossl_store_get0_loader_int:unregistered s
cheme:crypto\store\store_register.c:237:scheme=file
78B80000:error:1608010C:STORE routines:inner_loader_fetch:unsupported:crypto\sto
re\store_meth.c:383:No store loader found. For standard store loaders you need a
t least one of the default or base providers available. Did you forget to load t
hem? Info: Global default library context, Scheme (file : 0), Properties (
)
78B80000:error:16000069:STORE routines:ossl_store_get0_loader_int:unregistered s
cheme:crypto\store\store_register.c:237:scheme=C
78B80000:error:1608010C:STORE routines:inner_loader_fetch:unsupported:crypto\sto
re\store_meth.c:383:No store loader found. For standard store loaders you need a
t least one of the default or base providers available. Did you forget to load t
hem? Info: Global default library context, Scheme (C : 0), Properties ()
This public key PEM file is readable by everything else on my Windows 10 machine and looks like this:
-----BEGIN PUBLIC KEY-----
MHYwEAYHKoZIzj0CAQYFK4EEACIDYgAECK3Ptkmy1euJ0DNogEgMnSFzsCKh+gx0
peZQCWIexEgNipGisfyHv1Tb2wa5p26Rq1mGnYZwDrxdTlpDJjuSFbOszCjufhXF
4biHkt2HmjTH0d3vNUILhqdZrdyH+wc+
-----END PUBLIC KEY-----
I'm automatically loading providers in my config file with this line:
openssl_conf = openssl_init

The backslashes get interpreted I assume. I do not think this is a real bug - the discussion topic was closed by the reporter.

The reporter found a workaround - quoting a filename. But file name interpretation on Windows seems deserving a separate treatment.

The reporter found a workaround - quoting a filename. But file name interpretation on Windows seems deserving a separate treatment.

What? This was not a workaround. The path as it got to OpenSSL was not the real path anymore. And yeah, there is a fallback that treats the path as URI if there is a colon : inside. But I do not think this is a problem.

@t8m if you have a Windows machine (I don't), could you please check the behavior on 1.1.1 and 3.x with absolute paths?

@beldmit I have tested OpenSSL 3.0.10 on Windows 10.
.\openssl.exe genrsa -out D:\ossl30_key.pem 4096
.\openssl.exe rsa -in D:\ossl30_key.pem -pubout > D:\ossl30_pubkey.pem
.\openssl.exe dgst -sign D:\ossl30_key.pem -keyform PEM -sha256 -out D:\ossl30.sign C:\vars.bat
.\openssl.exe dgst -verify D:\ossl30_pubkey.pem -keyform PEM -sha256 -signature D:\ossl30.sign C:\vars.bat
Verified OK

OK, if it doesn't reproduce as is, let's close.


text:
Fix overflow check in BN_bn2dec()

Fix an off by one error in the overflow check added by 07bed46f332fc ("Check for errors in BN_bn2dec()").
This causes, for example BN_bn2dec(BN_value_one()) to fail.

+1 from me and +1 from Steve Henson

Pushed.

source: gharchive/pull-request

authors: mattcaswell rhenium


text:
Use build.info not file-wide ifndef

If configured with no-cms, handle it in build.info like the other options.
I guess I missed doing this file in PR #11250

This pull request is ready to merge

Merged to master. Thank you for the contribution!

authors: openssl-machine richsalz t8m


text:
Simplify and fix usage of char buf[3][BSIZE]

Simplify and remove an useless array of 3 string

please update the commit to say something like "replace an array of three strings with two local variables" ?

+1, needs another reviewer.

merged, thanks.

authors: FdaSilvaYY richsalz


text:
Fix version detection of clang on Apple OSes

Added missing fix from the master branch.
Fixes #20518

Only the second patch is applicable to master branch as well.

This pull request is ready to merge

Merge to 3.1 and master (only the two applicable commits) branches. Thank you for the reviews.


text:
Do not build P10-specific AES-GCM assembler on macOS

Legacy PowerPC machines running Mac OS X 10.5 and earlier are unable to build OpenSSL 3.1 due to the inclusion of new PPC assembler code that is incompatible with the OS X assembler. Exclude the P10-specific AES-GCM and ChaCha assembler code from being built on OS X systems.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

FYI @dannytsen

To accept the contribution we will need a regular CLA. Could you please follow the process described here: https://www.openssl.org/policies/cla.html

To accept the contribution we will need a regular CLA. Could you please follow the process described here: https://www.openssl.org/policies/cla.html

Done

ping for second review

A bit surprising that the code is broken even for AIX, which supports the latest ISA, I believe.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged to master and 3.1 branches. Thank you for your contribution.


text:
Add NNTP support (RFC 4642) to s_client ("-starttls nntp")

Checklist

[x] documentation is added or updated
[ ] tests are added or updated
[x] CLA is signed

Description of change

Add NNTP support (RFC 4642) to s_client ("-starttls nntp").

merged thanks!

authors: richsalz robert-scheck


text:
Fix typo in mk-fipsmodule-cnf.pl

I think I made them broken when editing multiple lines at the same time.
Checklist

[x] documentation is added or updated
[x] tests are added or updated

Agree its urgent to fix other PR's.

Merged, thanks for the fix.

Why couldn't this repository's CI find this issue?

Why couldn't this repository's CI find this issue?

It would have been found very quickly with use strict;, hence my question. But yes, there's also the issue that testing in the CI didn't spot this, but then no CI covers 100%

Why couldn't this repository's CI find this issue?

It would have been found very quickly with use strict;, hence my question. But yes, there's also the issue that testing in the CI didn't spot this, but then no CI covers 100%

I see. With this issue, the broken fipsmodule.cnf, OpenSSL even couldn't load the fips provider, and I reported the issue at https://github.com/openssl/openssl/discussions/24991. So, I thought some test cases were missing in the CI.

authors: 0140454 junaruga paulidale slontis tom-cosgrove-arm


text:
Fix some params which should be const in the API

Fixes #1526

can we change the API of pre-master functions?

Why not? I thought we'd gone around that circle a hundred times already. We've done it before, it doesn't break source or binary compatibility and it fixes real problems. Why would we not do it?

For function parameters, constifying is trivial and backward compatible, it only enforces us to keep a social promise.  For function return types, it's a different story altogether.

I thought I remember @dot-asm and/or @kroeckx arguing const'ifying params...  Maybe they can comment and correct me or re-argue their position?

I thought I remember @dot-asm and/or @kroeckx arguing const'ifying params... Maybe they can comment and correct me or re-argue their position?

Not had any reply to this last comment. I will leave for another day or so and otherwise take @levitte's approval.

I thought I remember @dot-asm and/or @kroeckx arguing const'ifying params... Maybe they can comment and correct me or re-argue their position?

Not had any reply to this last comment. I will leave for another day or so and otherwise take @levitte's approval.

Still got no reply, so I took @levitte's approval and pushed.

Ok, so it looks like this did actually cause an unexpected breakage. Specifically the adding of "const" to the arguments of ASN1_TIME_to_generalizedtime() has broken the pyca tests with this error:
ccache gcc-5 -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -I/home/travis/build/openssl/openssl/test/../include -I/home/travis/build/openssl/openssl/test/../include -L/home/travis/build/openssl/openssl/test/.. -fPIC -I/usr/include/python2.7 -c build/temp.linux-x86_64-2.7/_openssl.c -o build/temp.linux-x86_64-2.7/build/temp.linux-x86_64-2.7/_openssl.o
build/temp.linux-x86_64-2.7/_openssl.c:756:23: error: conflicting types for 'ASN1_TIME_to_generalizedtime'
 ASN1_GENERALIZEDTIME *ASN1_TIME_to_generalizedtime(ASN1_TIME *,
                       ^
In file included from build/temp.linux-x86_64-2.7/_openssl.c:468:0:
/home/travis/build/openssl/openssl/test/../include/openssl/asn1.h:628:23: note: previous declaration of 'ASN1_TIME_to_generalizedtime' was here
 ASN1_GENERALIZEDTIME *ASN1_TIME_to_generalizedtime(const ASN1_TIME *t,

The pyca file src/_cffi_src/openssl/asn1.py has this line in it:
ASN1_GENERALIZEDTIME *ASN1_TIME_to_generalizedtime(ASN1_TIME *,
ASN1_GENERALIZEDTIME **);
i.e. a copy of the ASN1_TIME_to_generalizedtime() declaration but without the added const. I'm not sure how exactly this is used but I assume it is auto-generating some C code and ending up with mis-matched function declarations.
Not sure what to do about it though? Revert this PR and ban all future addition of "const" until 1.2.0? Or is it a pyca problem?
Ping @levitte, @dot-asm, @kroeckx, @alex, @jon-oracle

I believe the general consensus is that having ones own declarations for functions provided by a third-party library (instead of using that library's headers) is considered Wrong, i.e., that pyca is at fault.  (I expect they have some technical reason in their build process that prevents them from easily just using our headers, but that means they need to be prepared to cope if our stuff changes.)

@mattcaswell addition of const breaks cryptography because we (perhaps unwisely) decided to try to ensure that function signatures we declare and the ones that OpenSSL declares are identical. We originally took this path because we wanted to avoid scenarios where we declared a type as int when in reality it was size_t or other potentially dangerous mismatches, but a consequence of our approach is that it also breaks on constification.
We can resolve this in our own tree by moving the declaration to a different section.

Thanks @reaperhulk. So it seems the consensus is that this is an issue for the python cryptography project an not us. I have created #3569 to update our external tests to pull in the fix for this.

authors: kaduk levitte mattcaswell reaperhulk richsalz


text:
Cleanup RAND_load_file,RAND_write_file

Document an internal assumption that these are only for use with files,
and return an error if not. That made the code much simpler.
Also only write 256 bytes, we don't need more than that from a security
perspective.
This was pulled out from #3862.

Okay, additional commit pushed that does your suggestions, @levitte

Cool. I'll do a double check on VMS tomorrow (way too tired to do it now)

so, @levitte did I break VMS or did it work? :)

[ahem] I was distracted...  trying it now

You’re not allowed to have a life ☺

Stop scaring me ;-)

Thanks!  commit 9ee344f

Good point.  New PR coming up.

authors: levitte richsalz


text:
Fix a gcc fallthru warning

GCC warns here because the previous switch statement has no default label,
so technically the control flow can fall thru into the next block.

Merged.  Thanks!


text:
[install_openstack_ca] Refactor main.yml

This patch cleans up the main.yml file of the install_openstack_ca role by:

Making task names more clear
Adding rescue blocks to print debug info when needed
Adding a new default to ease reading cifmw_install_openstack_ca_file_full_path
prepend internal vars with _

This patch is a result of a review on https://github.com/openstack-k8s-operators/ci-framework/pull/2155
Depends-On: https://github.com/openstack-k8s-operators/ci-framework/pull/2155

/approve

/lgtm

authors: cescgina lewisdenny raukadah


text:
Ensure we're running the hook against localhost only

the involved playbook runs against localhost. Though, in this case, it
may not properly be passed down - so let's just pass a static string as
inventory.
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

With the new ability to set the connection type, we can properly ensure where the hook is running

/approve
It now properly works and we shouldn't see any issue with the #361 change. We may depends-on in order to double-check that.
https://review.rdoproject.org/zuul/build/ef73c8f154994ac89a671f1bbfa1c713/log/ci-framework-data/logs/ansible.log-2023-07-22-06:51#805


text:
Set deploymentSSHSecret: osp-controlplane-ssh-keys

This key is automatically generated by the controlplane AppLabel
name. Lets make them match.

this change needs also be done in the kuttl test files

interesting. I would not have expected it to work correctly as the kuttle tests are currently coded as that secret won't even exist. I guess it just checks the API though so it makes sense


text:
set enable-chassis-as-gw on controllers by default

As part of [1] the enable-chassis-as-gw flag has been removed by default from the computes. Now this patch changes the default on the controllers to have it enabled so that the gw ports as hosted on the controllers instead of the computes by default.
[1] https://github.com/openstack-k8s-operators/edpm-ansible/pull/178

Would also need to validate if this works as expected before we merge it.

Would also need to validate if this works as expected before we merge it.

Yep, lets wait until we see the controllers are configure properly to enable N/S traffic, so that configuring the gw ports on the controllers does not break it

We should also add a default (true) to CRD definition, no?

Isn't that handled on the init.sh? if no value is passed it will take true (which made me realize that it should be "true" instead of true)

/ok-to-test


text:
Google sheets integration

plus other improvements for #46 #37 #38

@Ancymonek zrobiłem merge żeby na dev trafiło, ale jak widać trzeba to sporo poprawić jeszcze

repo: openstreetmap-polska/aed-mapa

license: MIT


text:
Untranslatable String 'Show the keyboard shortcuts screen'

Just checked with transifex, all translated there:

It's there now!
I was playing around with the Transifex client (#4101) and now I can manually push new source files anytime 👍

authors: bhousel manfredbrandl

repo: openstreetmap/iD

license: ISC


text:
Doesn't recognize vending machine tagging as "Parcel Pickup/Dropoff Locker" when order of values in vending tag is different

When an object is tagged with amenity=vending_machine and vending=parcel_mail_in;parcel_pickup instead of vending=parcel_pickup;parcel_mail_in (note the different order of values), it is displayed as only a generalVending Machine in the title/type (instead of Parcel Pickup/Dropoff Locker) which is a bit confusing for a parcel pickup and drop-off station.
If you rearrange the values, it is correctly recognized.
The order of values in vending (or in most tags, except destination, etc) shouldn't matter for the interpretation as far as I can see.
If this is not a huge thing to fix, I could implement it? But I'm not familiar with the project, so I'm asking here first.

If this is not a huge thing to fix, I could implement it?

Maybe it should be implemented as validator proposing to change vending=parcel_mail_in;parcel_pickup into more common form?
Current usage is 211 items ( https://overpass-turbo.eu/s/Y81 ) so support for such rare tag may be rejected - I would wait for decision from maintainers.

Hi and welcome, @xuiqzy. I agree the order of these values shouldn't really matter, but it's really helpful if they're consistent for tagging presets.
Since 4800 features use iD's order and only 200 use the other, a validation rule as proposed by @matkoniecz sounds okay. If the uses were closer to even then we'd look at a more advanced solution.

authors: matkoniecz quincylvania xuiqzy


text:
fix: optimize filetree view perf

变动类型

[x] 代码风格优化

需求背景和解决方案
changelog

优化文件树渲染性能

Codecov Report

Merging #149 (b8a39d1) into main (58b0f50) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #149      +/-   ##
==========================================
- Coverage   59.43%   59.43%   -0.01%
==========================================
  Files        1180     1180
  Lines       72315    72315
  Branches    14956    14956
==========================================
- Hits        42979    42977       -2
- Misses      26734    26736       +2
  Partials     2602     2602

Impacted Files
Coverage Δ

packages/core-common/src/node/port.ts
43.93% <0.00%> (-3.04%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: Aaaaash codecov-commenter

repo: opensumi/core


text:
Added tests for readme examples

Added a few tests for the examples in the readme and corrected the readme accordingly.  I also added some tests demonstrating how the loose option affects results.

It would be nice to merge this as it fixes the broken README.md!

authors: bamapookie simlmx

repo: opentable/accept-language-parser

license: mit

license_source: bigquery


text:
server: /single-deployment deployspec validation

No longer validates the partial deploy spec from the request
since we expect that to be incomplete information.
Validation is still done after round-tripping the new DeploySpec
to the GDM so that default values are added.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

  Generated by :no_entry_sign: Danger

authors: samsalisbury sous-machine-account

repo: opentable/sous


text:
[mle] API to provide MLE Parent Response information

Need to provide a way for clients of openthread(most likely vendor specific upper layers) to get parent request scan response data for SED. The plan is to implement it via a callback which needs to be installed by upper layer. The callback will be used to deliver following stats about a parent when a Parent Response is handled in Mle.

RSSI (1 byte)
rlock16 (2 byte)
extAddr (8 byte)
priority
Link count - LQ3 (1 byte)
Link count - LQ2 (1 byte)
Link count - LQ1 (1 byte)

Resolved by #3027.

authors: bisdash jwhui

repo: openthread/openthread


text:
[github-actions] macOS builds are currently failing

The error:

The runner did not connect within the allotted time of 45 minute(s).

I have created a GitHub support ticket. Will update this issue as I receive updates.

From GitHub Support:

Thank you for bringing this issue to our attention. Our Actions service is currently experiencing a degradation related to macos runners that our engineers are actively working on resolving.

GitHub has resolved the macOS runner issue.


text:
🛑 Search Tool is down

In a5cc4a1, Search Tool (https://search.opentorc.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Search Tool is back up in 26eab47.

repo: opentorc/upptime


text:
🛑 [CN] OpenUPM API /packages/extra is down

In 846e69b, [CN] OpenUPM API /packages/extra (https://api.openupm.cn/packages/extra) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM API /packages/extra is back up in b742aa3 after 8 minutes.

repo: openupm/upptime-openupmcn


text:
🛑 [CN] OpenUPM Website Docs is down

In 655b7e8, [CN] OpenUPM Website Docs (https://openupm.cn/docs/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM Website Docs is back up in 2849dd8.


text:
🛑 [CN] OpenUPM Website is down

In f1a74fa, [CN] OpenUPM Website (https://openupm.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM Website is back up in a3579d2 after 9 minutes.


text:
Add common characters for names

This PR adds common characters frequently used in people's names to the list.
重編國語辭典修訂本

啓 https://dict.revised.moe.edu.tw/dictView.jsp?ID=99047
伃 https://dict.revised.moe.edu.tw/dictView.jsp?ID=163122
峯 https://dict.revised.moe.edu.tw/dictView.jsp?ID=37377
咏 https://dict.revised.moe.edu.tw/dictView.jsp?ID=165985

全字庫（教育部辭典皆未收錄）

瀞 https://www.cns11643.gov.tw/wordView.jsp?ID=219730
彣 https://www.cns11643.gov.tw/wordView.jsp?ID=206194
瑠 https://www.cns11643.gov.tw/wordView.jsp?ID=215077
凃 https://www.cns11643.gov.tw/wordView.jsp?ID=207678

凃姓 https://zh.wikipedia.org/zh-tw/凃姓

This PR adds common characters frequently used in people's names to the list.

感謝製發 PR。好奇想問的是，製作這份 PR，是否有根據什麼語料或新聞時事等，來決定增加當前這些字呢？
換句話說我好奇的是「為什麼要增加這些字」或者「怎麼知道要增加這些字」。

這些字起源於兩個階段：

剛開始是我想打某位朋友的名字打不出來
想到可拿常用字的字集來參考，於是找了以下兩個字集

教育部次常用國字標準字體表

取差集後的結果為皆為罕用字，未採用

jf 7000 當務字集

基本包的 6373 字
Justfont 是一間字型設計公司，選出的字應該具代表性

如果您認為不需要加入，或是回歸到個人需求讓使用者要用的話自行加入即可，都可以關閉此沒關係 PR～

edu_secondary.txt
万丌丏冇与丮丰丱乂乜亍亓亢亳亶亹仂仉仨仜仩仡仝伎优伬仵伔伋仱伀价佖伻佢佉体佤伾佈佧佒佚佟佁佘侘佼侅佽侀侇佶佴侉侑侄佷佌侗佪侚佹侁佸侐侜佺侔侞俍俅俓侲俉侷俋俁俔俜俙侻侳俛俇倞倅倇倓倢倰倛俵俴倳倷倬俶俷倗倜倠偯偰偪偡偞偠偭偓偋偝偲偈偍偁偛偊偢倕偅偟偩偫傛傚傕傔傞傋傣傃傌傎傝偨傜傒傂傽傿僆傮僄僊傴僇僈僂傰僁傺傱僋僉僦僔僗僨僳僛僪僎僝僤僓僩僬僰僿儃儰僸儆儇僶僾儋儌僽儜儕儓儗儚儑儦儥儢儤儠儱儴儵儳儺儸儹儻儽党冏冔冓冘冞冪冱冼凊凄凅凔凘刌刉刓刖刜刞刵刲刳剆刱剄剉剡剚剒剞剟剕剫剭剬剺剸剻剼劂劀劁劋劌劊劓劖劘劗劙劦劭劼勍勖勣勩勰勱勴勺匊匜匢匭匰匴匷匼匽卌卍卣卬卼厂厎厒厗厖厞厜厤厬厹叄叡叻吰吷吪呔听咇呿咁咑咂咈呫呺呾呥呬呴呦咍咩咺咡咭咥咧哏哃茍咷咮哖咶哅哆咿咠呰咼咢唦唇哢唗唒哧哳哽哤唚哿唄唈哫唏唑唅啵啶唼啍啐唴唪啑啢唶唵唰啒啅啁啗唌唲啥啎喑喨喥喭啷噅喢喫喓喈喏喵喁喙喣喒喤啽喌喦嗃嗛嗌嗐嗉嗋嗊嗝嗀嗔嗄嗩喿嗒喍嗏嗕嗢嗖嗈嗲嘧嘕嘌嘒嗼嘏嘜嘁嘐嘓嗶嘂嗺嘝嘄嗿噈噂噌嘵噁噊噉噆噘噚噀嘳嘽嘬嘾嘸噍噰噠噶噮噳噦噣噭噲噞嚓嚌嚍嚆嚄嚃嚘嚜嚗嚚嚫嚭嚦嚧嚪嚬嚲嚵嚳囃嚽嚾囆囅囋囓囍囔囗囝囡囟囫囮囧囷囹囿圁圄圂圊圉圇圌圜圞圠圩圮坁圻坅坌坯坲坭坫坱坰坶垀坵坻坳坴垵垞垓垟垤垌垗垝垛垔垘埌堲埕埒垺埆垽垼埻埢埶埜埴堀埭埽堈埸堋埳埏堇堩堷堙堞堧堝堣堨埵堠塈堥塓塨塤塒塏塍塉塯塕塋墉塼墐墘墆墁塿塴墋塺墩墫墝墱墠墣墦墯墬壈墽壖壎壚壝壛壴壼壾壿夃夆夌复夎夒夗夬夯奅奓奊奡奫奭奰奲妀奼妦妘妠妗妎妢妐妵妺姏姎妲姌姁㚷姡姞姮娀姱姝姺姽姼姶姤娙娖娉娭婠婘婕婧婞娸娵婭婐婟婥婬婓婤婗媯媔媟婺媢媞婸媦媧婼媥媬媕媮娷嫇嫄嫋媺媸媱媵媰媿嫈媻嫜嫮嫥嫕嫪嫚嫭嫫嫳嫢嫠嫛嫿嬈嫴嫽嫷嫶嬃嬗嬙嬛嬡嬎嬓嬐嬖嬭嬥嬲嬽嬾嬿孃孅孈孋孌孛孢孥孬屘孲孷宁宄宎宓宕宨宧寁寀寪寍寋寔寑寖寘寙寠寰寱尃尌尐尔尒尟尨尪尰尳尻屄屌屖屔屙屝屣屧屨屩屭屮屴屼屺岍岏岈岋岉岒岊岮岤岠岵岯岨岬岟岣岭岢岪岧岝峐峘峌峒峗峋峛峞峚峉峇峊峬峴峿峮峱峷崞崋崝崚崠崌崨崍崦崤崥崏崰崒崧崗崣崟崷嵃嵫嵁嵋崿崵嵑嵎嵕崳崺崴嵒崽崱嵙嵇嵂嵯嵱嵣嵊嵥嵲嵬嵞嶂嶀嵽嶆嵺嶁嵷嶊嶉嶈嵾嶙嶗嶟嶒嶢嶓嶕嶠嶜嶡嶚嶞嶔嶬嶱嶩嶧嶵嶰嶮嶪嶨嶲嶭嶸嶷巀巃巆巇巉巏巋巕巑巘巟巰巹巿帊帗帔帙帡帢帟帣帠帤帩帨帾帴幄幃幏幎幘幙幓幩幝幡幠幧幨幦幬幪幭幰幵庀庂庋庉庌庈庰庤庢庛庣庥庨庮庪庬庱庴庹庲庳廄廅廌廆廋廇廘廑廗廎廜廕廙緳廛廞廡廩廧廦廨廥廮廯廱蠯廾异弅弇弋弚弝弨弢弣弤弮弳弶弸彀彄彃彉彊彋彏彔彖彘彧彯彳彴彸徂彾徉徠徛徜徦徥徯徭徲徼徾徿忀忁忉忔忕忒忑忐忭忨忮忳忸忡忤忣忺忯忪忷忻忞忥怭怦怙怲怋怴怩怫怊怗怳怛怚怞怬怢怍怐怮怓怷怹恔恲恞恅恓恇恉恛恌恀恂恟恝恚恧恁悢悈悀悒悁悝悃悕悛悗悇悊悐悆惇悾悰悺惓惔惏惤惙惝惈悱惛悷惉悹惌惢惎惄愔惲愊愖愅惵愓愒惸惼惾惷愍愆慉慊愫慅愶愲愷愮慆愯愬愨慁慞慵慱慳慒慓慲慬憀慴慔慺慛慥憋憃慹憱憰憢憉憛憓憯憭憟憒憪憡憍憮憝憨憖懅憴懆懁懌憺憿憸懃懋憵憼懧懠懥懤懨懞懘懟懭懮懱懪懰懫懻懽戁戃戄戇戉戔戠酨戣戥戩戧戭戺戽扂扃扆扊扑扐扜扞扤扡扦扢抃抆抌抎抏抔抇扱扻扺抭抴拑抾抪抶拊抮拏挍挂挋拵挎挃拫拹挏挌拸拶挀拲挐捖挬捄捅挶捃揤捍捌挹捋捊挼挩捁挴捘捔挲捥掊掂捽掽掞掭掝掗掫捺掎捯掇掐据掯捵掜捭掮捼掤挻掰掔掱揎揥揨揯揃撝揳揊揠揶揕揲揵摡揟揹掾揝揜揄揘揅揱揫搐搒搉搠搤搳搆摃搟搕搘搹搷搢搣搌搦搰搨摁搵搯搊搚摀搥搧搋搴搫摍摛摭摝摴摶摲摳摽摵摦撦摎撂摞摜摋摻摓摠摐摿摮摰撙撢撖撠撅撗撜撏撋撊撌撣撳撟擗擖擐擏擉撾撽擯擩擣擫擢擭擤擨擿擷攄擽擸攇攐攍攉攌攗攖攕攓攛攡攠攦攢攩攭攮攲攳攷攸攽敁敉敊敆敕敔敓敧敪敤敜敯敳敶敺敹敻敿斁斀斄斌斒斔斕斖斛斝斞斠斨斪斮斲斶斻斿旆旃旄旂旍旐旒旓旚旛旞旝旟旯旮旰旴旳昉旼昄昒昕昈旻昊昃昇昶昡昲昵昜昦昢昳昫昱昺昝昴晅晊晟晇晁晥晡晛晙晞晜晢晼晾晬晻暀晷暄暆暌暕暐暘暍暋暝暡暠暵暱暰暩曈暾曀曊曄曋曇曏曒曜曚曛曨曣曩曭曮曶朁朅朄朏朐朒朓朘朢朣朾朹朸朻机朿朼杆杅杇杠杙杕杌杈杝杓杗枓枅杬枎枒杶杼杻杪枘枆构杴枍枌杲柁柲柈枰枺柜枻柸柘柀枷柅柫柤柟枵柙柍枳柷柶柮柣柂枹柎柢柝柧柒柰枲栟栚桉栲栳栻桋桏栖栱栜栵栫栭栯桎桄栴栝栘栒桁栔梡桹梂梇梐梜桭桮梮梫楖桯梣梬梩桵桴梲梏桷梒桼椌棓椄棜椪棬棪棱楮椏棖棷棫棤棶椓椐棳棡椇棌椈楰梴椑棯棆椔棸棐棽棼棻棨楦楟椸楎楢楱椿楅楝楪椹楂楗楣楙楺楈楛楉椵楬椳椽楥棰楸椴楩楀楯楄楶㮣楘榱榶槉榠槎榖榰榬榼榑榙榎榧榍榩榾榯榿槄榽榤槔榦榹槊槃樀樆樗槥槸樕槱槤樠槿槬槭槢樛樝槾樧槲槮樔槷槧橀樴橦橉橧樲橈橨樾橝橭橶橛橑樨橚樻樿橁橪橤橐檍檖檁檥檉檟檣橾檗檛檡檞檐檇檓檎檕檃檠櫅檹檽檮檯櫡櫆櫧櫠櫌櫑櫙櫋櫟櫜櫐櫫櫳櫬櫰櫪櫨櫹櫱櫺欂櫸櫼欃欋欈欐欑欒欘欥欨欴欬欯欭欱欶欳欷欸欹欻欿歆歅歃歂歈歊歍歋歎歕歔歜歛歠歭殀歾殂殄肂殈殑殏殍殔殗殙殛殞殟殠殥殣殢殦殧殪殫殭殰殳殶殽毃毄毈毇毉毊毌毐毖毘毚毞毦毤毨毣毬毰毲毳毻毼毹毾氁氀毿氂氄氅氈氍气氕氘氙氚氠氪氰氬氶汃氿汆汒污汜汏汊汛汍汔汎汋汴沆汸汶汧汫沄沍沋沏沔沘汱汯汩沚汭沇沕沜汦沂汳沓泬泫泮泙沶沬泔沭泧沷泯泐泂沺泃泆泭泜泲泒泖泝泠沴泵洨洴洭洟洹洼洿洒洧洊泚洸洳洩洄洮洙洺洵洚洎洫洑洀浺浣浤浶洍涌浡涒浘浢浭浯涑涍涊淯浹涅浿涆浥浞浧涔浠涗浰浼浟涂涘淀涫涴涳涪淬湴涬淩淢涷淶淔涿渀淈淠淟淖涾淥淜淝淛淴淊涽淭淰淦淼湆湇渟湉溈渼渽湅湢渫渿湁湝湳湎渜渳湣湄湋湀湑渻渃渮湞湨湜湡渱渨湠湲湱湩湫渹渢湟渰湓溛滖滈溏滀溟溓溔溠溱溹滆滒溧溽滁溞滉溷溰滍溦滏溲溴溾滃滜滎滕滵滱漃漥滸漷滻漮漉潎漙漚漧漘漻漒滭漊漶潳滹滮漭滷潀漰漼漵滫漇漎潃漅漦潁潾澇濆澒澍澉澌潢潏澅潯潚潠澖潶潬澂潕潲潒潐潗潟澔澓潝澶澭濋澣濇澦澼濎濈澠潞濄澽澞濊澴澨瀄澥澮濌澩濴濔濣濜濭濩濕濧濦濞濮濰瀇瀌瀍瀁瀅瀔瀎濿瀀濻瀦濼瀙瀧瀠瀖瀫瀡瀢瀘瀣瀩瀼瀵瀯瀷瀴瀱灂瀸瀿瀺瀲瀹灃灄灊灈灉灕灖灗灛灞灟灡灝灨灩灪炔炘炅炷炤炟炾炱炰烜烓烑烝烋缹烺焍烷焗烴焌烯烰焄焠焞焯焜烻焮焱焣煇煔煒煆煣煠煁煝煨煖煢煲熇熐熉熀熅熂熒熏熲熯熛熰熠熚燅燂熿熸燖燀燁燋燔燊燡燠燼爁燿燾燹爌爊爇爂爓爝爚爞爟爢爣牁牂牄牉牋牏牓牚牣牬牰牸牷牾牻牼牿犈犉犆犅犍犌犑犐犎犗犕犓犘犚犝犞犥犦犤犣犨犩犪犮犰犴犵犿犽狃狆狁狖狋狘狉狜狒狔狚狌狑狊狤狨狫狟狪狦狣猀狺狴狾狶狳狻猝猗猇猑猘猊猈狿猏猋猒猰猢猱猳猧猲猭猦猣猵猼獂猻猺獀獊獃獍獑獌獘獒獞獟獠獝獛獡獩獦獧獬獥獫獪獳獮獯獶獽獼獾獿玂玁玃玅玆玈玊玎玕玗玓玔玤玡玭玦玢玠珌珂珈珅珓珪珙珥珖玼珧珣珞珩珶珸珵琄琁珽琇琀琮琯琬琛琰琫琖琦琚琡琨琭琱琤瑄瑊瑋瑒瑑瑗瑀瑢瑳瑱瑵瑲璇璉璊瑾璆璀璁瑽璅瑿璘璚璟璞璠璗璲璫璨璐璪璸瓀璵璿瓁瓋瓅璺瓖瓔瓘瓚瓛瓝瓞瓟瓡瓤瓥瓨瓬瓮瓴瓵瓿瓾瓽甀甂甃甈甋甍甐甑甒甔甓甖甗甝甡甪甮甯町甹甿畀甾畎畋畇畛畟畤畣畯畬畹畷畽畿疀疌疐疔疕疢疣疧疰痂痁疻疸痄痀痎痒痍痏痋痌痑痧痚痡痦痝痟痤痗痠痯瘏痳瘃痷痾痼痹痸瘐痻瘖瘈瘌瘕瘑瘊瘥瘞瘙瘝瘢瘜瘣瘯瘭瘱瘽瘳瘺瘼瘵瘲癃癈癉癇癜癤癙癐癓癠癟癪癭癰癵癹皁皊皋皏皕皙皜皝皞皛皤皦皫皭皯皵皸皻皽皾盄盅盉盓盝盦盩盬盭盳盱眈眃眄眅眇眊盷盻眝眛眐眓眒眣眑眕眙眚眢眹眯眭眱眲眴眳眽眥睆睇睄睍睅睊睎睋睌睕睟睠睒睖睚睩睢睧睔瞁睼瞅瞂睮瞀睯睾瞋瞍瞏瞉瞚瞝瞡瞜瞛瞢瞵瞫瞲瞷瞶瞴矂瞼矉矊矌矎矏矍矐矔矕矘矙矞矠矧矬矰矱矲矸矼矹矻矺砆砑砒砅砐砏砎砉砣砬砢砵砠砯砟砲砨砮硎硈硒硉硍硊硌砦硠硤硥硜硭硱硪确硰硩碇碚碔碏碄碕碅碓碆碲碪碴碭碣碨硾碫碞磍碻磏磌磑磎磔磈磃磝磧磩磥磪磞磣磛磳磽磻磼磿礌礓礔礉礐礝礛礴礜礥礣礧礨礭礱礵礽祂礿祊祌祋祅祔祛祏祜祓祒祑祤祧祩祪祣祫祡祴祳祲祼禂禘禊禋禖禕禔禓禗禚禡禠禜禫禨禭禬禰禴禳禷禸禺离歶秈秅秕种秏秖秎秘秫秬秠秮秭秪秺秸秶稂稊稃稌稑稘稙稞稒稗稫穊稰稯稹穋穄穈穜穛穖穟穠穧穨穮穬穭穰穱穸窀穾窆窉窅窋窌窊窏窔窐窙窣窢窞窨窫窬窲窴窳窶窸窵窱窾竀窿竁竑竘竦竫竷笐笄笓笅笏笈笊笵笻笴笥笰笢笤笳笘笪笝笮笱笫笭笯笲筊筇筑筄筈筌筦筤筭筴筮筩筲筥筧筳筱筰筡箈箜箊箑箐箸箖箍箌箛箎箅箇箘劄箙箄箷篋箾箬篎箠箯篌箹篞篣篧篝篕篥篚篨篹篔篦篪簅簏篲簀篿篻簌簎篴簋篳簂簉簃篠簁篸篽簜簩簙簠簟簭簝簦簨簢簥簳簼籀簹簬簻籉籈籊籔籗籜籙籛籧籣籥籦籩籯籽籺籸籹粄粑粊粔粘粕粢粲粻粿粼粺糅糈糌糒糔糗糝糬糪糰糲糴糱糶糷紆紃紈紞紝紑紎紘紖紓紟紒紵紽紸紶紲紺紱絅紬紩絁絇紾紿絘絯絣絓絰絖絧絪絏絳絭絜絫綈綆綀綍絿綅絺綎絻綃絼綌絛綔綧綷緂綣綪緁緀緅綝緎緄緆緋綬緌綯綹綖綼綟綦綮緷緛緪緧緗緙緡縃緺緦緲緹緶緱緰縒縡縞縗縌縟縠縝縓縉縎縜縕縚縢縐縋縏縭縼繂縴縳縹顈繈縸縵縪繉繀繇縩緵縰縿縻縶繄繒繜繐繖繣繘繢繟繙繑繠繶繵繸繰繷繯繺繳繲繴繻繾纁纀纊纇纈纋纆纍纑纕纔纗纚纘纛缾缿罃罅罋罊罌罍罏网罘罜罡罞罠罝罛罣罥罦罭罫罧罨罬罳罶罻罼罺罿罾罽羃羆羇羉羑羍羖羒羜羝羕羛羢羠羡羦羥羧羬羰羭羱羵羳羷羺羼羾翃翂翊翋翍翐翑翇翏翛翜翢翣翥翭翫翪翬翦翨翮翯翴翲翽翾翿耄耇耋耎耑耏耔耖耟耞耡耤耦耪耨耬耰耴耵耷耾耹聇聃聈聑聏聒聝聵聹肏肕肙肐肒肜肮肣肸肵胘胇胠胑胈胂胐胅胣胙胜胊胕胉胝胏胗胺胲胼胹胯胵脁胻脀胾胔脘脰脥脤脙脛脭脟脬脞脡脕脧腃腊腌腒腏腄腓腇脽腴腍腤腠腷腜腩腛腢腲朡腞腶腧腯膉膆膃膇膍膌膂膋膣膟膘膞膕膢膱膦膮膹膵膫膰膬膴膲臇膷膻臄臌臊臅臑臒臐臗臕臛臙臝臞臢臠臡臦臩臮臲臷臸臿舁舄舋舑舕舝舠舡舯舸舳舺舴舲舼舽艉艄艀艂艅艋艏艓艒艐艎艑艕艛艟艤艨艫艴艵艸艼芀艽芐芏芅芎芑芓芊芃芄芔芠苀芯芫芸芚芘芣芰芾芛芵芧芮芷芼芞芺芴芨芡芩苙苾苹苯茇苨茀苕茺苫苖苴苬苡苲苵茌苻茆苶茳茨茭荄茙荑茥荖茿荁茦茜茢荂荎茛茪茈茼荍茖茤茠茷茯茩荇荃荅茻莐莣莨莍荺荳莆莤荴莏莁莕莙荵莧莔莩荽莃莌莝莛莪莋荾莥菏菹萣菀菨萒菧菤菼菶萐萇菆菈菫菣莿萁菝菥菘菿菡菋菎菖菵菉萉菔菟萏菞萑萆菂菳菕菺菇菑蓱萿葖葶葹蒍葥葑葀葧萰葍葽葚葙葴葳葝蔇葞萷葭萺萴葺葃葸萲葅萩菙葋萯葂萭葟葆葰萹葎葌葒葯蒗蒤蒡蒟蓑蒺蓎蓂蒬蒮蒫蒹蒴蓁蓍蒪蒚蒱蓐蒝蒧蒻蒢蒔蓇蓌蒛蒩蒯蒨蓖蒘蒶蓊蓏蒠蔆蔤蔻蔏蔀蔩蔎蔉蔍蔟蔊蔧蔜蓻蔫蓺蔈蔌蓴蔪蓲蔕蓷蓫蓳蓼蔒蓪蓩蔖蓾蔨蔝蔮蔂蓽蔞蓶蔱蔦蓧蓨蓰蓯蓹蔘蔠蔰蕖蕅蕫蕍蕓蕡蕘蕀蕆蕤蕁蕞蕢蕄蕑蕇蕣蔾蕛蕱蕎蕵蕮蕕蕧蕠薌蕦蕝薃薀薏薧薕薠薋薣蕻薤薚薞蕷蕼薉薡蕺蕸蕗薎薖薨薆薍薙薝薊薁薢薂薈薅薴藆藀薺藃藂薹薳薵薽藇藄薿藋藎藈藅薱薶藒蘤藫藱藭藙藡藨藷藚藗藲藬藸藘藟藣藜藑藰蘢藿蘁藾蘛蘀藶蘄蘉蘅蘌蘘蘪蘦蘟蘣蘜蘙蘧蘮蘡蘠蘩蘞蘥蘴蘵蘳蘬蘺虀蘹蘼蘱蘻蘾虃虆虇虈虌虋虓虒虙虖虡虢虣虩虪虰虯虭虮虻虷虺虴蚢蚨蚖蚍蚑蚞蚜蚇蚗蚆蚋蚚蚅蚥蚙蚡蚧蚕蚿蚷蛂蛁蛅蚺蚰蛈蚹蚳蛉蚸蛌蚴蚻蚼蛘蛢蛦蛓蛣蛚蛪蛝蛐蛞蛫蛜蛬蛩蛗蜋蜄蛷蜌蛺蛖蛵蝍蛸蜆蜎蜉蜁蜊蛶蜍蜳蜷蜣蜨蝫蝀蜮蜞蜡蜙蜛蝃蜬蝁蜾蝆蜠蜲蜩蜪蜭蜼蜒蜺蜱蜵蝂蜦蜧蜸蜤蜚蜰蜑蝖蝣蝤蝷蟡蝳蝘蝔蝛蝒蝡蝚蝑蝞蝭蝪蝐蝎蝟蝝蝯蝬蝓蝺蝮蝜蝥螛螏螗螓螒螈螁螖螘蝹螇螣螅螐螑螝螄螔螜螚螾螪螭蟅螰螬螹螵螼螮蟉蟃蟂蟌螷螯蟄蟊螴螶螿螸螽蟞蟧蟦蟢蟛蟫蟪蟥蟟蟳蟤蟔蟠蟜蟓蟭蟘蟣螤蟗蟙蠁蟴蟨蠀蟺蠃蟶蟷蠉蠌蠋蟾蠆蟼蠈蟿蠙蠐蠑蠗蠓蠖蠩蠝蠛蠠蠤蠜蠫蠬蠨蠦蠪蠥蠰蠲蠮蠳蠸蠷蠵蠼蠾蠽蠿衁衃衄衈衊衋衎衒衖衕衚衧衪衩衭衽衵衶衲袀衱衹衿衯袃衾袉袕袨袢袪袚袑袡袟袘袧袙袛袗袤袬袌袺裗袹袸裀袾袶袼袷袽袲裖裋裍裎裞裛裒裚裷裧裱裲裺裾裮裼裶裯裻褁褅褌褔褋褗褘褙褆褖褑褕褊褎褡褞褦褰褭褮褧褱褢褩褵褳褼褾襁襒褷襂褽襓襋襏襌襆襐襢襚襛襗襡襜襘襝襞襣襦襭襩襮襬襶襴襳襹襺襾覂覅覈覕覘覜覛覝覡覢覤覣覭覯覮覷覶覿觔觓觖觙觕觝觚觟觥觤觡觠觢觜觩觫觭觰觬觱觲觳觶觷觺觻觼觾觿訄訇訏訒訑訰訧訬訞訢詎詍訶訹詙詖詀詗詘詄詅詒詈詶誆詿詡訿詷誂誄詵詻誃訾誫誙誋誚誒誶諏諆誸諓諑諔諕誻誹諗誾諛諀諅諠諳諢諲諶諴諵諝謔諤諟諰諼諈諞諡謞謐謘謖謑謅謋謏謒謕謇謍謈謫謪謧謣謳謰謵譇謯謼謾謱謥謷謦譐譈譊譆譀譓譖譔譋譕譑譙譠譪譝譨譟譣譥譹譸譅譺譻譾讄讂讆讌讎讋讔讕讘讙讜讞讟谹谻谼谽谾豃豇豋豍豏豗豜豝豟豥豤豦豨豭豰豲豳豱豯豵豷豶豸豻豽貁貀貆貄貅貏貑貒貕貔貙貘貗貜貤貣貺貾貰賌賕賥賟賙賨賡賚賵賮賸賻賾贄贆贇贐贔贕贙赨赩赬赮赶赸趄趀趑趌趎趏趍趓趠趜趡趥趧趬趪趭趫趮趯趲趵趷趼趺跂趹趿跘跓跍跇跖跜跏跕跙跈跗跅跤跰跠跬跱跮跐跩跦跣跢跧跲跫踉踂跿踍跽踊踃踇踆踅跾踠踣踥踤踮踡踕踛踖踑踙踦踞踧踔踒踘踓踳踾踸蹀蹅踶踼踽蹁踰蹎蹍蹓蹐蹌蹇蹜蹢蹠蹗蹟蹖蹞蹥蹧蹛蹚蹕蹡蹝蹩蹔蹴蹭蹸蹳蹪蹯蹻躆躈躄躋躕躔躚躒躓躐躖躗躞躟躠躥躤躣躦躩躨躽軏軑軓軘軞軝軯軷軺軹軦軮軥軵軧軨軶軫軱軬輆軿輁輀輅輇輈輂輋輐輑輬輤輘輚輞輠輥輣輖輗輶輳輮輵輲輹輷輴轃轀轆轇轈轒轑轏轐轓轙轖轗轕轘轚轞轛轝轠轢轤辴迉迒迋迓迍迖迕迣迡迤迮迨迸迾迵适迿迻逄逤逋逑逜逌逡逭逴逯逶遒逿遄遢遝遛遳遰遯遶遹遻邆邅遾邃邈邋邍邙邗邘邛邔邟邡邥邞邧邠邲邴邶邯邳邰郱邽邿郕郅邾郇郋郃郈郖郠郙郚郣郝郟郥郢郘郛郗郜郤郯郪郰郴郲郳郔郫鄆鄬鄄郾郿郼鄈郹郻鄁鄀鄇鄅鄃郺鄗鄐鄍鄏鄑鄖鄔鄋鄎鄣鄘鄜鄠鄢鄟鄞鄝鄚鄤鄡鄛鄨鄯鄫鄩鄪鄲鄦鄮鄳鄵鄴鄶鄸鄺鄻鄾酀酃酁酆酄酅酈酇酐酎酏酖酘酚酓酡酤酟酢酮酯酺酲酹酴酳醅醆醊醁醓醐醑醍醚醢醛醙醟醨醥醧醯醪醰醱醭醮醷醵醴醲醳醹醼醾醽釂釃釅釆釔釕釙釢釬釭釴釱釳釩釸釤釹鈁鈊鈥鈇鈃鈚鈦鈏鈌鈀鈒釿鈑釽鈆鉈鉒鈰鉉鉍鈺鉦鉅鈳鉥鉞銃鈮鉊鈹鉆鉭鉬鉏鈿鉠鉧鉯鉚鈶銨銥鉼銤鉶銛鉺銠銔銪銍銦銚銑銫鉹銗鉿銣鋮銎鋐鋃鋄鋀鋙銶鋏鋱鋟鋘鋩鋇鋰銲鋗鋝鋌鋯鋂鋨鋊鋈錧錞錈錟錆錏鍺錡錸錼錛錣錒錕錮錁鍆錭錎錍鋋錙鎡鎃鎯鍤鍖鍇鍼鍘鍜鍶鍉鍚鍔鍐鍑鍠鍭鎏鍌鍪鎵鎬鎰鎌鎒鎷鎘鎛鎝鎉鎧鎎鎪鎚鎞鎦鎗鏞鏇鏏鏂鏚鏐鏹鏬鏌鏙鎩鏦鏊鏨鐋鐓鏻鐠鐏鐔鏾鐕鐐鐨鐙鐍鏵鐀鏷鐇鐎鐫鐖鐿鐻鐶鑌鑐鑊鑋鑢鑕鑪鑫鑮鑭鑯鑱鑷鑴钂钀钁钃镺镻镼镽閆閈閍閌閎閟閜閞閬閫閼闍閾閹閺閶閿閵閽闇闀闉闃闅閷闕闒闓闑闚闛闞闠闟闥闤阞阢阤阠阬阰阨阯阹陂阽阼阸阺陔陏陑陓陊陜陘陟陞陬陼陭陫隇陾隄隈隉隃隒隓隑隗隞隤隩隮隰隳隹隼隿雂雈雎雊雒雓雔雗雚巂雟雘雝雩雱雰雺雽雿霅霈霂霋霒霐霠霣霢霤霩霫霬霮霰霵霿靆靃靉靚靪靬靰靮靳靷靸靲靽靺靾鞃鞀鞂靻鞄鞊鞎鞈鞙鞗鞔鞚鞡鞜鞞鞬鞮鞨鞫鞤鞪鞳鞷鞶鞹鞻鞿韄韅韇韉韎韍韐韏韕韔韗韙韝韞韟韡韣韥韰韱韹韽頄頇頏頍頎頖頞頝頦頩頨頫頠頜頵頯頲顁顄顊顉顅顐顑顒顜顙顝顗顠顢顣顟顤顥顪顩顲顳顴颬颭颮颲颸颿颽颻颾飁飂飉飆飋飌飣飫飶餂餀餈飺餑餔餖餗餕餤餟餚餧餥餫餬餪餳餲餯餭餱餰餮饁餼饈饇饉饃饐饎饙饌饋饗饘饔饕饛饟饡馗馘馝馣馦馯馲馰馵駃馹馻馺駂馽駜駍駏駓駔駎駉駖駘駮駬駥駤駰駣駪駩騂駺駴駷駹駸駶駻駽駾駼騃騏騋騉騍騄騑騊騅騇騚騕騥騝騤騛騢騠騧騣騞騜騵騲騴騱騬騪騶騩騮騸騭騹騽驆驄驂驁騺驎驓驍驔驌驏驈驊驉驒驖驞驠驤驦驩驨驫骭骫骹骿骴骾髁髀髂髇髊髆髍髐髑髕髖髟髡髣髧髬髫髳髲髶髺髹髾髽鬁髼鬈鬄鬅鬋鬊鬎鬌鬐鬒鬕鬗鬘鬖鬙鬞鬟鬠鬣鬤鬩鬫鬮鬯鬳鬵鬷鬺鬻鬾鬿魆魃魈魊魎魌魍魋魑魖魠魡魧魴魱魦魶魵鮀鮅鮇魼魾魻鮂鮓鮒鮐鮚鮭鮨鮞鮛鮦鮡鮥鮤鮆鯇鯆鯃鮿鯁鮵鮸鯈鯓鯀鯖鯪鯫鯠鯞鯤鯛鯦鯢鯰鯔鯗鯬鰌鰋鰈鯷鰅鰒鯸鱀鰫鰝鰜鰬鰣鰨鰩鱆鱈鰿鱄鰹鰳鱁鰼鰷鰴鰲鱒鱘鱐鱊鱍鱋鱕鱣鱧鱦鱢鱞鱠鱟鱨鱮鱴鱳鱹鱺鳦鳪鳭鳧鳱鳲鳵鳼鳺鳽鳿鳷鴇鴀鳹鳻鴈鴅鴃鴥鴗鴠鴞鴔鴩鴝鴘鴢鴐鴳鵁鵧鴶鴮鴯鴱鴸鴰鵅鵂鵃鴾鴷鵀鴽鵜鵓鵏鵊鵛鵋鵙鵖鵌鵗鵒鵔鵟鵷鶁鶊鶄鶈鵱鶀鵸鶆鶋鶌鵽鵫鵴鵵鵰鵩鶅鵳鵻鶂鵯鵹鶟鶙鶤鶝鶒鶘鶐鶛鶠鶔鶜鶪鶗鶡鶚鶢鶨鶞鶣鶿鶩鶖鶷鶶鶼鷁鷇鷊鷏鶾鷅鷃鶻鶵鷎鶹鶺鶬鷈鶱鶭鷛鷒鷞鷚鷋鷐鷜鷑鷟鷩鷙鷘鷖鷵鷕鷻鷷鷯鷣鷫鷸鷤鷶鷡鷮鷦鷲鷰鷢鸂鷾鸇鸃鸆鸅鸀鸁鸉鷿鷽鸄鸋鸍鸐鸏鸒鸑鸔鸓鸕鸗鸙鸛鸝鹵鹺麀麃麈麆麇麊麉麎麌麔麑麙麛麚麜麠麡麤麧麮麰麶麷黀黂黈黌黐黓黕黖黚黟黥黤黧黫黮黭黰黲黳黵黶黹黺黻黼黽黿鼁鼀鼆鼉鼊鼏鼐鼒鼖鼛鼘鼜鼤鼣鼢鼥鼫鼪鼩鼨鼭鼯鼰鼮鼱鼵鼳鼲鼸鼷鼶鼽齀齁齂齃齇齉齌齍齎齏齔齕齖齗齘齛齠齞齝齥齤齧齫齱齰齮齯齴齵齶齸齻齺齹齾龒龕龠龢龤堔礂蒏蒆謢

jf_basic.txt
㹴一丁七万丈三上下不与丐丑且丕世丘丙丞丟並丫中丰串丸丹主丼乂乃久么之乍乎乏乒乓乖乘乙乜九乞也乩乳乾亂了予事二于云互亓五井亘亙些亞亟亡亢交亥亦亨享京亭亮亳人什仁仃仄仆仇今介仍仔仕他仗付仙仝仞仟代令以仨仰仲仳仵件价任份仿企伃伉伊伋伍伎伏伐休伕优伙伝伯估伴伶伸伺似伽佃但佇佈位低住佐佑体佔何佗佘余佚佛作佝佞佟你佢佣佩佬佯佰佳併佶佺佻佼佾使侃侄來侈例侍侏侑侔侖侗侘供依侮侯侵侶侷便係促俄俊俋俎俏俐俑俗俘俚保俞俟俠信俣俥俬修俯俱俳俵俶俸俺俾倀倆倉個倌倍倏們倒倔倖倘候倚倜借倡倢倣倥倦倨倩倪倫倬倭值偃假偈偉偌偎偏偕做停健偭偲側偵偶偷偺偽傀傅傌傍傑傖傘備傚傜傢傣催傭傯傲傳傴債傷傻傾僂僅僇僉僎像僑僕僖僚僥僧僩僭僮僱僵價僻儀儂億儆儈儉儐儒儔儕儘償儡優儲儳儷儸儺儻儼儿兀允元兄充兆兇先光克兌免兒兔兕兗党兜兢入內全兩八公六兮共兵其具典兼冀円冇冉冊再冏冑冒冕冗冠冢冤冥冪冬冰冶冷冼冽凃凄准凋凌凍凜凝几凡凭凰凱凳凶凸凹出函刀刁刃分切刈刊刎刑划刖列初判別刨利刪刮到制刷券刺刻剁剃則剉削剋剌前剎剔剖剛剜剝剩剪剮副割剴創剷剽剿劃劄劇劈劉劊劍劑劓力功加劣助努劫劬劭劻劼劾勁勃勇勉勒動勗勘務勛勝勞募勢勣勤勦勰勳勵勸勺勻勾勿包匆匈匍匏匐匕化北匙匝匠匡匣匪匭匯匱匹匾匿區十千卅升午卉半卍卑卒卓協南博卜卞占卡卦卮卯印危即卵卷卸卹卻卿厂厄厘厚厝原厥厭厲去叁參又叉及友双反叔取受叛叟叡叢口古句另叨叩只叫召叭叮可台叱史右叵叶司叻叼吁吃各吆合吉吊吋同名后吏吐向吒吔君吝吞吟吠否吧吩含听吭吮吱吳吵吶吸吹吻吼吽吾呀呂呃呆呈告呎呔呢呣呤呦周呯呱味呵呶呷呸呻呼命呿咀咁咂咄咆咈咋和咎咏咐咒咔咕咖咚咥咦咧咨咩咪咫咬咭咯咱咲咳咸咻咽咾咿哀品哂哄哆哇哈哉哎哏哖哞員哢哥哦哧哨哩哪哭哮哲哺哼哽唁唄唆唇唉唎唏唐唑唔唚唧唬唭售唯唰唱唳唵唷唸唾啁啃啄啅商啊問啐啓啕啖啗啜啞啟啡啣啤啥啦啪啵啶啷啻啼啾喀喂喃善喆喇喉喊喋喎喏喔喘喙喚喜喝喟喧喨喪喫喬單喱喲喳喵喻嗄嗅嗆嗇嗉嗎嗑嗒嗓嗔嗖嗚嗜嗝嗟嗡嗣嗤嗥嗦嗨嗩嗯嗲嗶嗷嗽嗾嘀嘆嘈嘉嘌嘍嘎嘐嘓嘔嘖嘗嘛嘜嘞嘟嘧嘩嘮嘯嘰嘲嘴嘶嘸嘹嘻嘿噁噌噍噎噓噗噘噙噠噢噤噥器噩噪噫噬噯噱噴噶噸噹嚀嚅嚆嚇嚎嚏嚐嚓嚕嚥嚦嚨嚮嚴嚶嚷嚼囀囁囂囈囉囊囌囍囑囓囔囗囚四囝回囟因囡囤囧囪囫囮困囹固囿圃圄圇圈圉國圍園圓圖團圜土圣在圬圭圮圯地圳圻圾址坂均坊坋坌坍坎坏坐坑坔坡坤坦坨坩坪坯坳坵坷坼垂垃型垓垛垠垢垣垮垵埂埃埆埋城埒埔埕埗埜域埠埡埤埭埴埵執培基埼堀堂堃堅堆堇堉堊堝堠堡堤堪堯堰報場堵塊塋塌塑塒塔塗塘塚塞塢填塭塱塵塹塽塾墀境墅墉墊墓墘墜增墟墦墨墩墮墳墻墾壁壅壇壎壑壓壕壘壙壞壟壢壤壩士壬壯壹壺壼壽夏夔夕外夙多夜夠夢夤夥大天太夫夬夭央夯失夷夸夾奀奄奇奈奉奎奏奐契奔奕套奘奚奠奢奧奩奪奭奮女奴奶奸她好妁如妃妄妊妍妏妒妓妖妘妙妝妞妣妤妥妨妮妯妲妳妹妻妾姆姊始姍姐姑姒姓委姘姚姜姝姣姥姦姨姪姬姮姵姻姿威娃娉娌娑娓娘娛娜娟娠娣娥娩娶娼婀婁婆婉婊婕婚婢婦婪婬婭婷婿媒媗媚媛媜媞媧媲媳媼媽媾嫁嫂嫉嫋嫌嫖嫗嫘嫚嫡嫣嫦嫩嫵嫺嫻嬈嬉嬋嬌嬖嬗嬛嬝嬡嬤嬪嬬嬰嬲嬴嬸嬿孀孃孅孌子孑孓孔孕孖字存孚孛孜孝孟孢季孤孥孩孫孬孰孱孳孵學孺孽孿它宅宇守安宋完宏宓宕宗官宙定宛宜客宣室宥宦宮宰害宴宵家宸容宿寂寄寅密寇富寐寒寓寔寞察寡寢寤寥實寧寨審寫寬寮寰寵寶寸寺封射將專尉尊尋對導小少尖尚尢尤尪尬就尷尸尹尺尻尼尾尿局屁屄居屆屈屋屌屍屎屏屐屑展屘屙屜屠屢屣層履屨屬屭屯山屹岈岌岐岑岔岡岩岫岬岭岱岳岷岸峇峋峒峙峨峪峭峯峰峴島峻峽崁崆崇崎崑崔崖崗崙崚崛崢崤崧崩崴崽嵇嵋嵌嵐嵙嵩嵯嶂嶄嶇嶔嶙嶝嶠嶸嶺嶼嶽巉巍巒巔巖川州巡巢工左巧巨巫差己已巳巴巷巽巾巿市布帆希帑帔帕帖帘帙帚帛帝帥師席帳帶帷常帽幀幃幄幅幌幔幕幗幛幟幡幢幣幫干平年并幸幹幻幼幽幾庄庇床序底庖店庚府庠度座庫庭庵庶康庸庹庾廁廂廄廈廉廊廍廓廖廚廝廟廠廡廢廣廨廬廳延廷廸建廾廿弁弄弈弊弋式弒弓弔引弗弘弛弟弦弧弩弭弱弳張強弼彆彈彊彌彎彗彘彙彝彞形彣彤彥彧彩彪彫彬彭彰影彷役彼彿往征待徇很徉徊律後徐徑徒得徘徙徜從徠御徨復循徬徭微徵德徹徼徽心必忌忍忐忑忒忖志忘忙忝忠忡忤忪快忮忱念忸忻忽忿怎怏怒怔怕怖怙怛怜思怠怡急怦性怨怩怪怫怯怵恁恂恃恆恍恐恒恕恙恢恣恤恥恨恩恪恫恬恭息恰恿悄悅悉悌悍悔悖悚悛悟悠患您悱悲悴悵悶悸悻悼悽情惆惇惊惋惑惕惘惚惜惟惠惡惦惰惱想惴惶惹惺惻愀愁愆愈愉愍愎意愕愚愛愜感愣愧愫愴愷愾愿慄慇慈態慌慍慎慓慕慘慚慝慟慢慣慧慨慫慮慰慳慵慶慷慼慾憂憊憋憎憐憑憔憚憤憧憨憩憫憬憮憲憶憾懂懃懇懈應懊懋懌懍懟懣懦懨懲懵懶懷懸懺懼懾懿戀戇戈戊戌戍戎成我戒戕或戚戛戟戡戢截戮戰戲戳戴戶戽戾房所扁扇扈扉手才扎扑扒打扔托扛扞扣扦扭扮扯扱扳扶批扼找承技抄抉把抑抒抓抔投抖抗折抨披抬抱抵抹押抽抿拂拄拆拇拈拉拊拋拌拍拎拏拐拒拓拔拖拗拘拙拚招拜括拭拮拯拱拳拴拷拼拽拾拿持挂指挈按挑挖挨挪挫振挲挹挺挽挾捂捅捆捉捋捌捍捎捏捐捕捧捨捩捫据捱捲捶捷捺捻捽掀掂掃掄授掉掌掏掐排掖掘掙掛掠採探掣接控推掩措掬掮掯掰揀揄揆揉揍描提插揖揚換揠握揣揩揪揭揮援揶揹搆損搏搐搓搔搖搗搜搞搥搧搪搬搭搴搵搶搽搾摀摁摃摑摒摔摘摜摟摧摩摭摯摳摶摸摹摺摻撂撇撈撐撒撓撕撙撚撞撢撣撤撥撩撫撬播撮撰撲撳撻撼撾撿擀擁擂擄擅擇擊擋操擎擒擔擘據擠擢擣擤擦擬擯擰擱擲擴擷擺擻擼擾攀攆攏攔攖攘攙攜攝攢攣攤攥攪攫攬支收攸改攻放政故效敉敏救敔敕敖敗敘教敝敞敢散敦敬敲整敵敷數斂斃文斌斐斑斕斗料斛斜斟斡斤斥斧斫斬斯新斷方於施旁旂旅旋旌旎族旒旖旗既日旦旨早旬旭旱旺旻旼昀昂昃昆昇昉昊昌明昏易昔昕星映昤春昧昨昭是昱昴昵昶晁時晃晉晌晏晒晚晝晞晟晢晤晦晨晬普景晰晴晶晷智晾暄暇暈暉暌暍暐暑暖暗暘暝暢暨暫暮暱暴暸暹曄曆曇曉曖曙曜曝曠曦曩曬曰曲曳更曷書曹曼曾替最會月有朋服朔朕朗望朝期朦朧木未末本札朮朱朴朵机朽杆杈杉杌李杏材村杓杖杙杜杞束杠杪杭杯杰東杲杳杵杷杼松板极枇枉枋析枒枓枕林枚果枝枯枳枴枵架枷枸柁柄柊柏某柑柒染柔柘柙柚柝柞柢查柩柬柯柱柳柴柵柺柿栓栖栗校栢栩株核根格栽桀桁桂桃桄桅框案桉桌桎桐桑桓桔桶桿梁梃梅梆梏梓梔梗梘條梟梠梡梢梧梨梭梯械梱梳梵棄棉棋棍棒棕棗棘棚棟棠棣棧棨森棱棲棵棹棺棻椅椋椌植椎椏椒椪椰椹椽椿楂楊楓楔楚楝楞楠楢楣楨楫業楮極楷楸楹概榆榎榔榕榖榛榜榧榨榫榭榮榴榷榻槁槃構槌槍槐槓槙槤槨槭槲槳槻槽槿樁樂樅樊樑樓標樞樟模樣樨樵樸樹樺樽橄橇橈橋橘橙機橡橢橫橾檀檄檎檐檔檗檜檠檢檣檬檮檯檳檸檻櫂櫃櫓櫚櫛櫝櫞櫟櫥櫨櫪櫫櫬櫸櫺櫻欄欉權欏欒欖欠次欣欲欷欸欺欽款歃歆歇歉歌歎歐歙歛歟歡止正此步武歧歪歲歷歸歹死歿殂殃殄殆殉殊殍殖殘殛殞殤殫殭殮殯殲段殷殺殼殿毀毅毆毋母每毒毓比毗毘毛毫毬毯毽氂氅氈氏氐民氓气氕氖氘氙氚氛氟氡氣氤氦氧氨氪氫氬氮氯氰氳水永氾汀汁求汆汎汐汕汗汙汛汝汞江池污汨汩汪汰汲汴汶決汽汾沁沂沃沅沆沈沉沌沍沏沐沒沓沔沖沙沛沫沬沮沱河沸油治沼沽沾沿況泄泅泉泊泌泓法泖泗泛泠泡波泣泥注泫泮泯泰泱泳泵洁洄洋洌洎洒洗洙洛洞津洨洩洪洫洮洱洲洳洵洶洸活洽派流浙浚浣浥浦浩浪浬浮浯浴海浸浹涂涅涇消涉涌涎涓涔涕涮涯液涵涸涼涿淀淄淅淆淇淋淌淑淒淖淘淙淚淝淞淡淤淦淨淩淪淫淬淮深淳淵混淹淺添淼清渙渚減渝渟渠渡渣渤渥渦温測渭港渲渴游渺渼渾湃湄湊湍湎湔湖湘湛湟湣湧湮湯湲湳溉溏源準溘溚溜溝溟溢溥溪溫溯溱溴溶溺溼滂滄滅滇滉滋滌滎滑滓滔滕滬滯滲滴滷滸滾滿漁漂漆漉漏漓演漕漚漠漢漣漩漪漫漬漯漱漲漳漸漾漿潁潑潔潘潛潟潢潤潦潭潮潯潰潲潸潺潼澀澂澄澆澇澈澍澎澔澗澡澤澦澧澪澱澳澶澹激濁濂濃濕濘濛濟濠濡濤濫濬濮濯濰濱濺濾瀅瀆瀉瀋瀏瀑瀕瀘瀚瀛瀝瀞瀟瀣瀧瀨瀰瀲瀾灌灑灘灝灞灣灤灩火灰灶灸灼災炅炆炊炎炒炔炕炙炤炫炬炭炮炯炳炷炸為烈烊烏烔烘烙烟烤烯烴烷烹烽焉焊焓焗焙焚焜焠無焢焦焯焰焱然焿煆煇煉煊煌煎煒煖煙煜煞煤煥煦照煨煩煬煮煲煸煽熄熊熏熒熔熗熙熟熠熨熬熱熵熹熾燁燃燄燈燉燎燐燒燔燕燙燜營燠燥燦燧燬燭燮燴燻燼燾燿爆爌爍爐爛爨爪爬爭爰爵父爸爹爺爻爽爾爿牆片版牌牒牖牘牙牛牝牟牠牡牢牧物牯牲牴特牽犀犁犄犇犒犖犛犢犧犬犯犰犽狀狂狄狎狐狒狗狙狠狡狩狳狷狸狹狻狼狽猁猊猓猖猙猛猜猝猞猢猥猩猴猶猷猻猾猿獄獅獎獐獒獗獠獨獪獰獲獴獵獷獸獺獻獼獾玀玄玆率玉王玖玟玠玥玦玨玩玫玲玳玷玻珀珂珅珈珉珊珍珞珠珣珥珩珪班珮珺珽現球琅理琇琉琊琍琚琛琢琥琦琨琪琬琮琯琰琲琳琴琵琶琺琿瑀瑁瑄瑋瑕瑗瑙瑚瑛瑜瑞瑟瑠瑢瑣瑤瑩瑪瑭瑯瑰瑱瑳瑾璀璁璃璇璉璋璐璘璜璞璟璣璦璧璨璩環璽璿瓊瓏瓔瓖瓚瓜瓞瓠瓢瓣瓤瓦瓮瓶瓷甄甌甍甕甘甚甜生產甥甦用甩甫甬甭甯田由甲申男甸町甽甾畀畋界畎畏畑畔留畚畜畝畢略畦番畫畯異當畸畿疆疇疊疋疏疑疔疙疚疝疣疤疥疫疱疲疳疵疸疹疼疽疾痀痂病症痊痍痒痔痕痘痙痛痞痠痢痣痤痧痰痱痲痳痴痹痺痼痾痿瘀瘁瘉瘋瘍瘓瘖瘜瘝瘟瘠瘡瘢瘤瘦瘧瘩瘴瘸瘺瘻療癆癇癈癌癒癖癘癟癡癢癤癥癩癬癭癮癰癱癲癸登發白百皂的皆皇皈皋皎皓皖皙皚皤皮皰皴皸皺皿盂盃盅盆盈益盍盎盒盔盛盜盞盟盡監盤盥盧盪目盯盲直相盹盼盾省眇眈眉看眛真眠眥眨眩眯眶眷眸眺眼眾着睇睏睚睛睜睞睡睢督睥睦睨睪睫睬睹睽睿瞄瞅瞇瞋瞌瞎瞑瞞瞟瞠瞥瞧瞪瞬瞭瞰瞳瞻瞼瞽瞿矇矓矗矚矛矜矢矣知矧矩矬短矮矯石矸矽砂砌砍砒研砝砠砥砦砧砭砰砲破砵砷砸硃硅硍硎硐硒硝硫硬确硯硼硿碁碇碉碌碎碑碓碗碘碟碣碧碩碰碳碴確碼碾磁磅磊磋磐磔磕磚磡磧磨磬磯磴磷磺礁礎礑礙礡礦礪礫礬礴示礽社祀祁祂祆祇祈祉祐祓祕祖祗祚祛祝神祟祠祢祥票祭祺祿禁禍禎福禕禚禛禦禧禪禮禰禱禳禹禺禽禾禿秀私秈秉秋科秒秘租秣秤秦秧秩秭移稀稅稈程稍稔稗稚稜稞稟稠種稱稷稹稻稼稽稿穀穆穌積穎穗穠穡穢穩穫穴究穹空穿突窄窈窒窕窖窗窘窟窠窣窩窪窮窯窳窸窺窿竄竅竇竈竊立竑站竟章竣童竦竭端競竹竺竽竿笆笈笏笑笙笛笞笠符笨笪笫第筆等筊筋筌筍筏筐筑筒答策筠筧筮筱筴筵筷箇箋箍箏箔箕算箝箠管箬箭箱箴箸節篁範篆篇築篋篌篙篛篝篠篡篤篦篩篳篷篾簇簋簌簍簑簞簡簣簧簪簫簷簸簽簾簿籀籃籌籍籐籟籠籣籤籥籬籮籲米籽粄粉粑粒粕粗粘粟粥粧粨粩粱粲粳粵粹粼粽精粿糅糊糌糕糖糗糙糜糞糟糠糢糧糬糯糰糴糶糸系糾紀紂約紅紆紇紈紉紊紋納紐紓純紕紗紘紙級紛紜素紡索紫紬紮累細紲紳紹紺紼絀終絃組絆結絕絛絜絝絞絡絢絣給絨絮統絲絳絹綁綉綏綑經綜綞綠綢綣綫綬維綰綱網綴綵綸綹綺綻綽綾綿緇緊緋緒緘緙線緝緞締緡緣編緩緬緯緲練緹緻縈縉縊縐縑縛縝縞縟縣縫縮縱縲縴縵縷縹總績繁繃繅繆繇繈繒織繕繖繙繚繞繡繩繪繫繭繰繳繹繻繼繽繾纂纈續纍纏纓纔纖纘纛纜缶缸缺缽罄罅罈罌罍罐网罔罕罟罡罣罩罪罫置罰署罵罷罹羅羆羈羊羋羌美羔羚羞羡群羥羧羨義羯羰羲羶羸羹羽羿翁翅翊翌翎習翔翕翟翠翡翦翩翫翬翮翰翱翳翹翻翼耀老考耄者耆耋而耍耐耑耒耕耗耘耙耜耦耨耳耶耽耿聆聊聒聖聘聚聞聯聰聱聲聳聵聶職聽聾聿肄肅肆肇肉肋肌肏肓肖肘肚肛肝股肢肥肩肪肫肯肱育肴肺肽胃胄胇背胎胖胗胚胛胜胝胞胡胤胥胭胯胰胱胳胴胸胺胼能脂脅脆脈脊脖脘脛脣脩脫脯脰脹脾腆腈腊腋腌腎腐腑腓腔腕腥腦腩腫腮腰腱腳腴腸腹腺腿膀膂膈膊膏膕膘膚膛膜膝膠膨膩膳膺膻膽膾膿臀臂臃臆臉臊臍臏臘臚臟臠臢臣臥臧臨自臬臭至致臺臻臼臾舀舂舅與興舉舊舌舍舐舒舔舖舘舛舜舞舟舢舨航舫般舵舶舷船舺艇艉艋艏艘艙艦艮良艱色艷艸艾芃芊芋芍芎芒芘芙芛芝芟芡芣芥芩芫芬芭芮芯芰花芳芷芸芹芻芽芾苑苒苓苔苗苙苛苜苞苟苡苣若苦苧苫苯英苳苷苹苺茁茂范茄茅茆茉茗茜茨茫茬茭茯茱茲茴茵茶茸茹茼荀荃荇草荊荏荐荒荔荖荳荷荸荻荼荽莆莉莊莎莒莓莖莘莞莠莢莧莨莩莪莫莽莿菀菁菅菇菈菊菌菓菔菖菘菜菟菠菡菩菫華菰菱菲菴菸菽萁萃萄萇萊萋萌萍萎萘萣萩萬萱萵萸萼落葆葉著葚葛葡董葦葩葫葬葭葯葱葳葵葶葷葺蒂蒐蒔蒙蒜蒞蒟蒡蒨蒯蒲蒴蒸蒹蒺蒻蒼蒽蒿蓀蓁蓄蓆蓉蓊蓋蓍蓑蓓蓖蓪蓬蓮蓴蓼蓽蓿蔆蔑蔓蔔蔗蔘蔚蔡蔣蔥蔦蔫蔬蔭蔻蔽蕁蕃蕈蕉蕊蕎蕙蕞蕤蕨蕩蕪蕭蕾薄薇薈薊薏薑薔薙薛薜薤薦薨薩薪薯薰薹薺藉藍藏藐藕藜藝藤藥藩藪藷藹藺藻藿蘅蘆蘇蘊蘋蘑蘗蘚蘢蘭蘸蘿虎虐虔處虛虜虞號虧虫虯虱虹虺虻蚊蚋蚌蚓蚕蚜蚣蚤蚩蚪蚯蚰蚱蚵蚶蚺蛀蛄蛆蛇蛉蛋蛐蛔蛙蛛蛞蛟蛤蛭蛸蛹蛻蛾蜀蜂蜃蜆蜇蜈蜉蜊蜍蜒蜓蜘蜚蜜蜡蜢蜥蜩蜴蜷蜻蜿蝌蝎蝓蝕蝗蝙蝟蝠蝣蝦蝨蝮蝴蝶蝸螂螃螅螈融螞螟螢螫螭螯螳螺螻螽蟀蟄蟆蟈蟋蟎蟑蟒蟠蟥蟬蟯蟲蟳蟹蟻蟾蠅蠆蠊蠍蠑蠓蠔蠕蠖蠟蠡蠢蠣蠱蠵蠶蠹蠻血衊行衍術衖街衙衛衝衡衢衣表衩衫衰衲衷衹衽衾衿袁袂袈袋袍袒袓袖袞袤袪被袱裁裂裊裎裏裒裔裕裘裙補裝裟裡裨裱裳裴裸裹製褂複褊褐褒褓褔褕褙褚褡褥褪褫褲褶褸褻襁襄襖襞襟襠襤襪襬襯襲西要覃覆覈見規覓視覡覦親覬覲覷覺覽覿觀角觔觚解觥触觴觸言訂訃訇計訊訌討訏訐訓訕訖託記訛訝訟訢訣訥訪設許訴訶診註証訾詁詆詈詎詐詒詔評詛詞詠詡詢詣試詨詩詫詬詭詮詰話該詳詹詼誅誆誇誌認誑誒誓誕誘誚語誠誡誣誤誥誦誧誨說誰課誹誼調諂諄談諉請諍諏諒論諗諛諜諡諢諤諦諧諫諭諮諱諳諶諷諸諺諼諾謀謁謂謄謅謊謎謐謔謖謗謙講謝謠謨謫謬謳謹謾譁證譎譏識譙譚譜譟警譫譬譭譯議譴護譽讀變讎讒讓讖讚讜讞谷谿豁豆豈豉豊豌豎豐豔豕豚象豢豪豫豬豳豸豹豺貂貅貉貊貌貍貓貔貘貝貞負財貢貧貨販貪貫責貯貲貳貴貶買貸費貼貽貿賀賁賂賃賄賅資賈賊賑賒賓賜賞賠賡賢賣賤賦質賬賭賴賸賺賻購賽贅贈贊贍贏贓贔贖贗贛赤赦赧赫赭走赳赴赶起趁超越趕趖趙趟趣趨趯足趴趺趾跆跋跌跎跑跖跚跛距跟跡跤跨跩跪跫路跳跺跼踉踊踏踐踝踞踟踢踩踪踫踭踮踰踱踴踵踹踽蹂蹄蹇蹈蹉蹊蹋蹌蹓蹕蹙蹚蹟蹠蹣蹤蹦蹧蹩蹬蹭蹲蹴蹶蹺蹼躁躂躅躇躉躊躋躍躑躓躕躡躥躪身躬躲躺軀車軋軌軍軏軒軔軛軟軫軸軻軼軾較載輊輒輓輔輕輛輜輝輟輦輩輪輯輳輸輻輾輿轂轄轅轆轉轍轎轔轟轡轤辛辜辟辣辦辨辭辮辯辰辱農辵迂迄迅迆迎近迓返迢迤迥迦迨迪迫迭述迴迷迸迺追退送逃逅逆逍透逐逑途逕逖逗這通逛逝逞速造逡逢連逭逮週進逵逶逸逼逾遁遂遇遊運遍過遏遐遑道達違遘遙遛遜遝遞遠遢遣遨適遭遮遯遲遴遵遶遷選遺遼遽避邀邁邂邃還邇邈邊邋邏邐邑邕邢那邦邨邪邯邰邱邵邶邸郁郃郊郎郗郝郡郢郤部郭郵都郾鄂鄉鄒鄔鄙鄞鄢鄧鄭鄰鄱鄲鄴鄹鄺酆酈酉酊酋酌配酎酐酒酗酚酞酢酣酥酩酪酬酮酯酵酶酷酸酹醂醃醇醉醋醍醐醒醚醛醜醞醣醫醬醮醯醱醴醺釀釁釆采釉釋里重野量釐金釗釘釙釜針釣釦釧釩釭釵釷釹鈇鈉鈍鈎鈐鈑鈔鈕鈞鈣鈦鈴鈷鈸鈹鈺鈽鈾鈿鉀鉅鉈鉉鉋鉍鉑鉗鉚鉛鉞鉤鉦鉬鉸鉻鉼銀銃銅銑銓銖銘銚銜銣銥銦銨銫銬銲銳銷銹銻銼鋁鋃鋅鋇鋌鋏鋐鋒鋤鋦鋪鋯鋰鋸鋼錄錐錒錕錘錙錚錞錠錡錢錦錨錫錮錯錳錵錶錸鍊鍋鍍鍔鍘鍛鍥鍬鍰鍵鍶鍺鍼鍾鎂鎊鎌鎏鎔鎖鎗鎘鎚鎢鎧鎩鎬鎮鎰鎳鎵鏃鏈鏍鏑鏖鏗鏘鏜鏝鏞鏟鏡鏢鏤鏨鏽鐃鐐鐘鐙鐧鐫鐮鐲鐳鐵鐶鐸鐺鑄鑊鑑鑒鑠鑣鑪鑫鑭鑰鑲鑷鑼鑽鑾鑿長門閂閃閉開閎閏閑閒間閔閘閡閣閤閥閨閩閭閱閹閻閾闆闇闈闊闋闌闍闐闔闕闖關闡闢阜阡阨阪阮阱防阻阿陀陂附陋陌降限陘陛陜陝陞陟陡院陣除陪陬陰陲陳陴陵陶陷陸陽隄隅隆隈隊隋隍階隔隕隘隙際障隧隨險隰隱隴隸隹隻隼雀雁雄雅集雇雉雋雌雍雎雒雕雖雙雛雜雞離難雨雩雪雯雰雲零雷雹電需霄霆震霈霉霍霎霏霑霓霖霙霜霞霤霧霪霰露霸霹霽霾靂靄靈青靖靚靛靜非靠靡面靦靨革靳靴靶靼鞅鞋鞍鞏鞘鞠鞣鞦鞭韁韃韆韉韋韌韓韜韭音韶韻響頁頂頃項順頇須頊頌預頑頒頓頗領頜頡頤頫頭頰頷頸頹頻顆題額顎顏顓願顛類顢顥顧顫顯顰顱顳顴風颯颱颳颶颺颼飄飆飛食飢飧飩飪飭飯飲飴飼飽飾餃餅餉養餌餐餒餓餘餚餛餞餡館餬餮餵餽餾餿饃饅饈饉饋饌饑饒饕饗饜饞首馗香馥馨馬馭馮馱馳馴駁駐駑駒駕駙駛駝駟駢駭駱駿騁騎騏騖騙騫騮騰騵騷騾驀驁驃驅驊驍驕驗驚驛驟驢驤驥驪骨骯骰骷骸骼骾髀髁髂髏髑髒髓體髕髖高髡髣髦髫髭髮髯髻鬃鬆鬍鬚鬟鬢鬣鬥鬧鬨鬩鬱鬲鬻鬼魁魂魄魅魍魎魏魑魔魘魚魟魠魩魯魴魷魽鮑鮒鮕鮘鮟鮨鮪鮫鮭鮮鯀鯁鯈鯉鯊鯓鯔鯖鯛鯝鯡鯤鯧鯨鯪鯰鯷鯽鰂鰆鰈鰍鰓鰕鰤鰥鰭鰱鰲鰹鰻鰾鱇鱈鱉鱒鱔鱖鱗鱘鱟鱧鱲鱷鱸鱺鳥鳧鳩鳳鳴鳶鴃鴆鴇鴉鴒鴕鴛鴞鴟鴣鴦鴨鴴鴻鴿鵑鵜鵝鵠鵡鵪鵬鵯鵰鵲鶇鶉鶘鶚鶩鶯鶴鶸鶺鶼鷂鷓鷗鷥鷲鷳鷴鷸鷹鷺鸚鸛鸝鸞鹵鹹鹼鹽鹿麂麋麒麓麗麝麟麥麩麴麵麻麼麾黃黌黍黎黏黐黑黔默黛黜黝點黠黥黨黯黴黷黹黽鼇鼎鼐鼓鼕鼙鼠鼬鼯鼴鼻鼾齁齊齋齒齜齟齡齣齦齧齪齬齲齷龍龐龔龕龜

check.py
with open("edu_secondary.txt", "r", encoding="UTF-8") as f:
    edu_sec = set(f.readline().strip())

with open("jf_basic.txt", "r", encoding="UTF-8") as f:
    jf_basic = set(f.readline().strip())

with open("BPMFBase.txt", "r", encoding="UTF-8") as f:
    lines = f.readlines()
    BPMFBase = set()
    for line in lines:
        BPMFBase.add(line.split()[0])

print(edu_sec.difference(BPMFBase))

print(jf_basic.difference(BPMFBase))

結果
{'㮣', '尔', '緵', '鰌', '阸', '㚷', '嬎'}

{'伃', '瀞', '鐧', '咏', '獴', '㹴', '凃', '邨', '咲', '凭', '廍', '粩', '彝', '吔', '啓', '峯', '叶', '踭', '鯝', '腈', '瘻', '円', '鰂', '俥', '瑠', '亘', '舘', '踪', '綫', '栢', '鮘', '擀', '葱', '梘', '嘞', '溚', '酞', '廸', '祢', '蒽', '埗', '辵', '彣', '鈎', '烟', '菓', '鰕', '俣'}

@ChiahongHong thank you!

authors: ChiahongHong lukhnos xatier

repo: openvanilla/McBopomofo


text:
Assign course email template

Email templates for letting user know about the assigned course and inform the manager once the user starts the course

Used Base64 encoding to embed the logo image directly in the email HTML.

Fixes #100

@sadrisya  Can you add a screenshot of the completed UI ?

authors: deepakkumarnd sadrisya

repo: openvitae-tech/blackboard-lms


text:
:wrench: set default fixture scope for pytest-asyncio

Resolves PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset

I was going to change this with an upcoming PR. But we can change it here. I was going to change it to session scope as default. Not sure if there's a reason you chose module or not? I don't think it will really matter.

I was going to change this with an upcoming PR. But we can change it here. I was going to change it to session scope as default. Not sure if there's a reason you chose module or not? I don't think it will really matter.

Ah, the only reason for setting it to module level is because it's the lowest available scope.
I think the default in the next pytest-asyncio release will be "function" scope, so I first tried that. But then there are module-scope fixtures that depend on function-scope fixtures, which isn't allowed. So, module scope is a default that works. I guess that was the only reason.
The main difference will be in the lifecycle of the test fixtures. I think session-scope fixtures should be explicitly marked as such, since they have the longest lifecycle (created once and destroyed at end of test run). And those should probably be few and far between. Probably much of a muchness. But it makes sense that since the tests are highly modular (each module has its own tests folder), most test fixtures that don't have an explicitly defined scope should probably be function or module level.
I think function-level would make most sense, but that entails a review of all the fixtures that don't have a defined scope, and then setting only the ones that need it to module scope.

repo: openwallet-foundation/acapy


text:
ui: fix visual and bug on removing contact

Summary of Changes
This PR changes the visual of the default ContactCredentialListItem in the ContactDetails Screen and the look of the contact name + logo.
Contact without Image:

Contact with image:

This PR also fixes a problem with the removal of the contact when it has issued credentials.
Related Issues
N/A
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[x] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[x] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[x] Updated documentation as needed for changed code and new or modified features;
[x] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

@fc-santos what part of this PR addresses this:

This PR also fixes a problem with the removal of the contact when it has issued credentials.

Just curious, it's not super obvious to me

@bryce-mcmath The new hook useBranding(params) was being used in the ContactCredentialListItem and the params being passed was not being memoized and it was causing an infinite re-render.

authors: bryce-mcmath fc-santos

repo: openwallet-foundation/bifold-wallet


text:
Prepare data dictionary for skips and poi data resources

Hi @n-raspi, thanks for sharing the data. I have prepared the structure for the data package to be updated. Currently working on a dev branch.
Could you please:

Add a concise one sentence description to each variable, staring with captial letter and ending with a period. No commas.

Option 1
-Download: https://github.com/openwashdata/wasteskipsblantyre/blob/dev/data-raw/dictionary.xlsx

Fill out locally
Upload and overwrite: https://github.com/openwashdata/wasteskipsblantyre/blob/dev/data-raw/dictionary.xlsx

Option 2

Clone the repo and and on dev branch, edit the XLSX

Done

authors: larnsce n-raspi

repo: openwashdata/wasteskipsblantyre


text:
Set your OpenWhisk Namespace and Authorization Key

I had ever connected via CLI successfully. After I build my local OpenWhisk development environment, the CLI does not work.
I input the same command "wsk property set --auth " in my terminal, it returns

error: The supplied authentication is invalid (code 599)

wsk property set --auth xxx:yyy for some xxx:yyy as the auth key does not make an API call. It just write to the wsk property file. Are you saying that after you set the auth key to an appropriate value, a subsequent API call fails?
If so,

are you using cloudant or couchdb and did you run the script createImmortalDbs?
are you using one of the built in keys or a new key?
if using a new key, did you add the key to the db using wskadmin create user ...?

I figure out what is wrong. After setting up the local development environment; I run wsk property set --apihost  pointing to Vagrant. I forget to change the apihost back to openwhisk.ng.bluemix.net. Be better, you may add documentation mentioning the proper --apihost

repo: openwhisk/openwhisk


text:
allow defaulting to snapshots builds if no stable builds are found for a device

when using the fw selector, you can remove the version=<x.x.x> url parameter to create a link to the latest available build for a device.
for example, this link will pre-select the latest build for WHW03 V2:

https://firmware-selector.openwrt.org/?target=ipq40xx%2Fgeneric&id=linksys_whw03v2

however, if there are no stable builds for a device yet (still on snapshot), the same type of link will fail:

https://firmware-selector.openwrt.org/?target=ipq40xx%2Fgeneric&id=linksys_whw03

these links are useful and are sometimes used in devices wikis (and i think they should be auto-generated in the ToH now). however, currently they can't be used for devices still on snapshot (whose wikis tend to be more actively maintained, paradoxically).
please consider fixing this by defaulting to snapshots if stable builds are not found.

A missing version in the link is undefined behavior. I like to keep selector simple and not added any logic behind it.

that's too bad... it's reasonable to have a link to the latest release software for each device.
such functionality i baked in many platforms, eg: https://github.com/openwrt/openwrt/releases/latest
in any case, because links missing the version currently resolve to latest version instead of faulting, people reasonably thought that that was feature and started using it. so now there are a bunch of links from device pages to the firmware selector that work but are technically undefined.
for example, this page includes this line:

Official firmware: https://firmware-selector.openwrt.org/?target=ipq806x%2Fgeneric&id=arris_tr4400-v2

yes, that's a page i built myself for a port that i did, but i took inspiration/copied from other wiki entries.
besides that case, i know i added those types of links a couple of times in the wiki, for devices i ported and also others i helped document. i always thought that having to use a special form for devices not yet with a stable (to point to snapshot) release was a nuisance.

I had the same idea actually and added it in 4.0.0 (https://github.com/openwrt/firmware-selector-openwrt-org/blob/master/CHANGELOG.md?plain=1#L40)
But the translation layer was removed in favor of simplicity and reducing local state. That makes it very hard for the OFS to implement this. The OFS would need to load all release information at once, that would multiply the OFS load traffic by 30x).

authors: Lanchon mwarning

repo: openwrt/firmware-selector-openwrt-org


text:
Language and style error.

When you install a theme, it would add an option in Stlye.But it does not remove the option while you uninstall the theme.

I have remove the theme of Material and OpenWrt, but it still can choose here. Is there something wrong?

I think we have to update the theme Makefile in https://github.com/openwrt/luci/blob/master/themes/ with a postrm section to remove on remove the string from the config
config internal 'themes'
option Material
option OpenWrt
option Bootstrap

You can use ssh and type these;
uci -q delete luci.themes.Material
uci commit luci

authors: Holinc19 esershnr feckert

repo: openwrt/luci


text:
luci-proto-wireguard: Remove confirmation dialogue to generate keys

Quality of life improvements. Reduce click amounts. LuCI batches all changes for user-review anyway.
Tested on 23.05.0

I don't know. A lot of people simply smash save & apply without ever reviewing changes. Also that crypto material is a bit more important than generic settings which can be reverted to defaults or restored from remembered settings...
I tend to NAK this one.

OK, I understand your concern. Although the private key can be reverted just like any other setting.

authors: jow- systemcrash


text:
Reenable -Wc++20-extensions?

I have to disable -Wc++20-extensions with Clang because my local Clang-19 has just started rejecting multiple points in IREE code with:
error: passing no argument for the '...' parameter of a variadic macro is a C++20 extension [-Werror,-Wc++20-extensions]

Basically, we like to think we are not relying on C++20 extensions, but we are actually relying on that one, and Clang started warning on that when we ask it to.

Where exactly?
It's a C++ extension, but not a C one, so I suspect it's only triggering in cc files?

authors: benvanik bjacob

repo: openxla/iree


text:
Make default distribution logic divide work evenly.

Also fix a bug in tile size adjustment, which reduce the number of workgroups in cases where we are dividing the work too much. The numWorkgroupsPerDim[index] was not updated after adjusting it to a new tile size.

The regressions and improvements are noise. Good to have dispatch size improvements!

For future reference, Diego and I had an offline discussion. It's ok if there is a bit of load imbalance. We just have to make sure that the gap between the first N-1 and the last one is not huge. I added hints to make distribution tile sizes be multiple of the vector length. It makes sure that we are not penalizing all the threads.

@dcaballe I think this is the root cause that regresses some benchmarks. We can't simply revert it because one of landed commit depends on it. I will prepare a PR that reverts it properly later today.

I checked that the regression only happens on MobileBert_int8 case, and filed an issue. I think we should fix that after we have better int8 codegen. The configuration was tuned by me and it just unrolls a lot. We don't get a chance to fix it. I'd defer the multi-threading issue after fixing codegen. Otherwise, we will sit in the sub-optimal configurations for a long time. And it will be much harder to contribute.


text:
[Question] Does OpenYurt have a formal code style requirement?

What happened:
I am not sure whether OpenYurt has a formal code style requirement, which may include:

function name definition rule
limitation of max characters every line
code comments format
patch comments format
...
What you expected to happen:
If no clear requirement for OpenYurt by now, I think it's better to clarify it so that different contributors can follow the unified code style rule. Forming the consistent code style may be beneficial to the code readability and maintainability of the whole project.
How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:
Environment:

OpenYurt version:
Kubernetes version (use kubectl version):
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

others
/kind question

@zzguang Very appreciate for your issue.
OpenYurt community does not have a detailed code style at present, but code of pull request will be verified by golang native rule(golangci-lint run --out-format=github-actions --disable-all  -E deadcode -E gofmt -E goimports -E ineffassign -E misspell -E vet --timeout=15m in github action)
and If you have a good code style to contribute to OpenYurt, we will be more than happy to do so.

Okay, let's follow the golang native rule firstly, if we find it's not enough yet, we can discuss it in future to figure out an unified code style, thanks!

authors: rambohe-ch zzguang

repo: openyurtio/openyurt


text:
fix(yurt-manager): raven controller can't list calico blockaffinity

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

/kind bug
What this PR does / why we need it:
The CR blockaffinity is defined as projectcalico.org/v3 in the new calico api package, but in fact calico use crd.projectcalico.org/v1 version.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/assign @rambohe-ch

hi @luckymrwang , thanks for your work! I met the same issue, has this PR completely fixed this problem?

hi @luckymrwang , thanks for your work! I met the same issue, has this PR completely fixed this problem?

Yes.

Hi @luckymrwang , I use your branch but yurt-manager report another error.
E0915 08:02:30.248561       1 deleg.go:144] setup "msg"="unable to setup controllers" "error"="no matches for raven.openyurt.io/v1beta1, Resource=gateways"

Hi @luckymrwang , I use your branch but yurt-manager report another error.
E0915 08:02:30.248561       1 deleg.go:144] setup "msg"="unable to setup controllers" "error"="no matches for raven.openyurt.io/v1beta1, Resource=gateways"

Because I fix it on the lastest main branch which is not stable version. If you want use it immediately, you can replace the yurt-manager image by luckymrwang/yurt-manager:hotfix-v1.3.4 which I fixed it on the stable version v1.3.4.

/lgtm

authors: fighterhit luckymrwang rambohe-ch


text:
add yurtingress controller unit test

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

@Rudolf1998 , the current unit test coverage is only about 18.8% basing on your PR, which can not meet the 70% target, could you please optimize it to improve the ratio? thanks!
$go test ./pkg/yurtappmanager/controller/yurtingress/... --covermode=count
ok  	github.com/openyurtio/yurt-app-manager/pkg/yurtappmanager/controller/yurtingress	(cached)	coverage: 18.8% of statements

@Rudolf1998 , the current unit test coverage is only about 18.8% basing on your PR, which can not meet the 70% target, could you please optimize it to improve the ratio? thanks! $go test ./pkg/yurtappmanager/controller/yurtingress/... --covermode=count ok github.com/openyurtio/yurt-app-manager/pkg/yurtappmanager/controller/yurtingress (cached) coverage: 18.8% of statements

@zzguang I think 70% test coverage for the entire yurt-app-manager repo is enough, and some unit tests will need mock tests, which we can implement uniformly later.

@Rudolf1998 , the current unit test coverage is only about 18.8% basing on your PR, which can not meet the 70% target, could you please optimize it to improve the ratio? thanks! $go test ./pkg/yurtappmanager/controller/yurtingress/... --covermode=count ok github.com/openyurtio/yurt-app-manager/pkg/yurtappmanager/controller/yurtingress (cached) coverage: 18.8% of statements

@zzguang I think 70% test coverage for the entire yurt-app-manager repo is enough, and some unit tests will need mock tests, which we can implement uniformly later.

Okay, agree with you to implement the mock test in future.

/approve

/lgtm

/lgtm

/lgtm
/approve

@Rudolf1998 please check ci/golangci-lint error info .

/approve

Fixes #76

/approve

authors: Congrool Rudolf1998 kadisi zzguang

repo: openyurtio/yurt-app-manager


text:
only trace valid requests

Realized while looking at the traces that we had bunch of traces for weird URLs.
Turns out is people trying to find security holes in our apps.
We do not want to send those all traces to our zipkin. This PR solves the problem for Rails apps.
@jamescway @jfeltesse-mdsol

:+1:

released 0.6.2

authors: jamescway jcarres-mdsol

repo: openzipkin/zipkin-tracer


text:
When gateway kind is CLIENT, http.path: is "/", Why is that?

This is the version I am currently using.
Spring Cloud Greenwich SR2
Spring Cloud Gateway 2.1.2
Spring boot2.1.6
Spring Cloud Zipkin 2.1.2
Show-how
Spring Cloud Gateway Configuration

Request url

zipkin ui

[
{
"traceId": "f86c4c36d0718024",
"parentId": "f86c4c36d0718024",
"id": "3d95b7b0c8fdde88",
"kind": "SERVER",
"name": "get /demo1/test/auto/refresh/names",
"timestamp": 1566366796911115,
"duration": 2681,
"localEndpoint": {
"serviceName": "msa-demo1",
"ipv4": "172.17.101.50"
},
"remoteEndpoint": {
"ipv4": "172.17.101.50"
},
"tags": {
"http.method": "GET",
"http.path": "/demo1/test/auto/refresh/names",
"mvc.controller.class": "AutoRefreshController",
"mvc.controller.method": "autoRefreshNames"
},
"shared": true
},
{
"traceId": "f86c4c36d0718024",
"parentId": "f86c4c36d0718024",
"id": "3d95b7b0c8fdde88",
"kind": "CLIENT",
"name": "get",
"timestamp": 1566366796904700,
"duration": 9697,
"localEndpoint": {
"serviceName": "msa-gateway",
"ipv4": "172.17.101.50"
},
"tags": {
"http.method": "GET",
"http.path": "/demo1/test/auto/refresh/names"
}
},
{
"traceId": "f86c4c36d0718024",
"id": "f86c4c36d0718024",
"kind": "CLIENT",
"name": "get",
"timestamp": 1566366796908788,
"duration": 7110,
"localEndpoint": {
"serviceName": "msa-gateway",
"ipv4": "172.17.101.50"
},
"tags": {
"http.method": "GET",
"http.path": "/"
}
}
]
End
I hope to answer my questions. Thank you.

Hi, can you either as on sleuth's gitter or open an issue against sleuth please? This repo is for the zipkin server code https://gitter.im/spring-cloud/spring-cloud-sleuth

authors: adriancole songwenh

repo: openzipkin/zipkin


text:
Add Hacker News

@premii's Hacker News mobile app
Site: https://hn.premii.com/
Github: https://github.com/premii/hn

I haven't investigated this thoroughly, but the web app install banner isn't triggered on this site... Any idea why?

AFAICT, it doesn't use a service worker, so won't show up an install banner. Doesn't work offline too.
I would vote a 'no' on this one in the current form.

I agree. @zcdunn happy to include it once these issues are fixed :) Closing PR for now.

authors: andreasbovens shwetank zcdunn

repo: operasoftware/pwa-list


text:
fix example json string in jenkins-operator

Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/ok-to-test

/lgtm

authors: jkhelil mvalarh

repo: operator-framework/community-operators


text:
Add AkkaClusterOperator - Community

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?
[x] Have you tested your Operator with all Custom Resource Definitions?
[x] Have you tested your Operator in all supported installation modes?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Have you tested an update to your Operator when deployed via OLM?

Your submission should not

[x] Modify more than one operator
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Basic Tests:
    Spec Block Exists: 1/1
    Status Block Exists: 1/1
    Writing into CRs has an effect: 0/1
OLM Tests:
    Provided APIs have validation: 1/1
    Owned CRDs have resources listed: 1/1
    CRs have at least 1 example: 1/1
    Spec fields with descriptors: 2/2
    Status fields with descriptors: 4/4

Total Score: 86%

/ok-to-test


text:
[community] Add Dynatrace OneAgent operator bundle

Add a Dynatrace OneAgent operator bundle file containing CRD, CSV and package yaml.

Pushed oneagent operator to community-operators repo in quay

authors: SamiSousa jeremylinlin


text:
Spinnaker operator 1.17.2

Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[x] Has you operator nested directory structure?
[x] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?
[x] Have you tested your Operator with all Custom Resource Definitions?
[x] Have you tested your Operator in all supported installation modes?
[x] Is your submission signed?

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

@aswath2saru, please sign it by @j-sandy as an author. Thank you.

is there any way i can be a co-author ?

@aswath2saru, you will be co-author. But modifications needs to be approved by original author.

@aswath2saru, try to make as few commits as possible by squashing them.

I've Rebased and Merged the Code. Kindly review it.

@dmesser Can you please Review and approve  ?


text:
doc: add proposal for Image scaffold feature

Description of the change:
Proposal for new operator-SDK future to allow users to inform images in order to scaffold the code required for them to get running in the cluster.
Motivation for the change:
Many operators will at the end have CRD's which will represent a deployment/pod/service of an image:tag. So, I am as oper user I'd like to have a feature to make this process easier.
Ref: Proposal made in the PR: https://github.com/operator-framework/operator-sdk/pull/2158

Hi @zachncst,
I really like your idea proposed in #2158 which was closed by you. So, I am adding this one with the suggestions made. Feel free to collab with and let's see what the others think about. really thank you for your collab with.

@camilamacedo86 This looks amazing! Thanks for consolidating down my original request into the scaffold idea you proposed in our discussions. I definitely like this for getting operator-sdk a little closer to rails generators. Happy to help with it as well.

Hi @zachncst,
After discussing with @joelanford over it was decided to track the need in https://github.com/operator-framework/operator-sdk/issues/2529 and close this one since currently, we are working to integrate the project with Kubebuiler and it would be impacted. For further info see the comment https://github.com/operator-framework/operator-sdk/issues/2467#issuecomment-580053554. Please, feel free to follow up.

repo: operator-framework/operator-sdk


text:
execution of "squid -z" missing on web cache activation

Hello,
Maybe I'm wrong, but it looks like execution of squid -z on cache activation is missing.
Thanks for your work.
Regards,
Renoow.

Hi Renoow,
It should be pulled in via setup.sh
https://github.com/opnsense/core/blob/master/src/opnsense/scripts/proxy/setup.sh
What issue are you seeing?
Cheers,
Franco

Hmm, it’s not run on restart/reconfigure, maybe that is your issue. Initial setup ok, cache add and not working?

Hi Franco,
When I check " Enable local cache (requires service restart) " squid restart hang.
/var/log/squid.syslog.log
OPNsense (squid-1): Failed to verify one of the swap directories, Check cache.log for details. Run 'squid -z' to create swap directories if needed, or if running Squid for the first time.
/var/log/squid/cache.log
2017/12/20 19:13:47 kid1| Squid Cache (Version 3.5.27): Exiting normally.
2017/12/20 19:13:48 kid1| Set Current Directory to /var/squid/cache
2017/12/20 19:13:48 kid1| Starting Squid Cache version 3.5.27 for amd64-portbld-freebsd11.0...
2017/12/20 19:13:48 kid1| Service Name: squid
2017/12/20 19:13:48 kid1| Process ID 46668
2017/12/20 19:13:48 kid1| Process Roles: worker
2017/12/20 19:13:48 kid1| With 57960 file descriptors available
2017/12/20 19:13:48 kid1| Initializing IP Cache...
2017/12/20 19:13:48 kid1| DNS Socket created at [::], FD 6
2017/12/20 19:13:48 kid1| DNS Socket created at 0.0.0.0, FD 8
2017/12/20 19:13:48 kid1| Adding domain localdomain from /etc/resolv.conf
2017/12/20 19:13:48 kid1| Adding nameserver 127.0.0.1 from /etc/resolv.conf
2017/12/20 19:13:48 kid1| Adding nameserver 192.168.122.1 from /etc/resolv.conf
2017/12/20 19:13:48 kid1| Logfile: opening log stdio:/var/log/squid/access.log
2017/12/20 19:13:48 kid1| Unlinkd pipe opened on FD 13
2017/12/20 19:13:48 kid1| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec
2017/12/20 19:13:48 kid1| Logfile: opening log stdio:/var/log/squid/store.log
2017/12/20 19:13:48 kid1| Swap maxSize 102400 + 262144 KB, estimated 28041 objects
2017/12/20 19:13:48 kid1| Target number of buckets: 1402
2017/12/20 19:13:48 kid1| Using 8192 Store buckets
2017/12/20 19:13:48 kid1| Max Mem size: 262144 KB
2017/12/20 19:13:48 kid1| Max Swap size: 102400 KB
2017/12/20 19:13:48 kid1| ERROR: /var/squid/cache/00: (2) No such file or directory
FATAL: Failed to verify one of the swap directories, Check cache.log
for details. Run 'squid -z' to create swap directories
if needed, or if running Squid for the first time.
Squid Cache (Version 3.5.27): Terminated abnormally.
Running "squid -z" manually and restarting squid solve the problem.
I've tried on two fresh installs and obtain same result each time.
Cordialement,
Renaud MEDICI
Inform'Ethic
8, Route de Saint Julien - 07200 Ucel
Tél. : +33 7 86 47 60 21
Fax : +33 9 55 24 01 54
De: "Franco Fichtner" notifications@github.com
À: "opnsense/core" core@noreply.github.com
Cc: "Renaud MEDICI" rmedici@inform-ethic.fr, "Author" author@noreply.github.com
Envoyé: Mercredi 20 Décembre 2017 20:57:10
Objet: Re: [opnsense/core] execution of "squid -z" missing on web cache activation (#2008)
Hi Renoow,
It should be pulled in via setup.sh
[ https://github.com/opnsense/core/blob/master/src/opnsense/scripts/proxy/setup.sh | https://github.com/opnsense/core/blob/master/src/opnsense/scripts/proxy/setup.sh ]
What issue are you seeing?
Cheers,
Franco
—
You are receiving this because you authored the thread.
Reply to this email directly, [ https://github.com/opnsense/core/issues/2008#issuecomment-353165405 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AXGwXZMFo0_86a3ty7NIndDX7F-FpIm1ks5tCWVNgaJpZM4RI1Wv | mute the thread ] .

Yes, local cache activation activated when web cache already activated.
Cordialement,
Renaud MEDICI
Inform'Ethic
8, Route de Saint Julien - 07200 Ucel
Tél. : +33 7 86 47 60 21
Fax : +33 9 55 24 01 54
De: "Franco Fichtner" notifications@github.com
À: "opnsense/core" core@noreply.github.com
Cc: "Renaud MEDICI" rmedici@inform-ethic.fr, "Author" author@noreply.github.com
Envoyé: Mercredi 20 Décembre 2017 20:54:57
Objet: Re: [opnsense/core] execution of "squid -z" missing on web cache activation (#2008)
Hmm, it’s not run on restart/reconfigure, maybe that is your issue. Initial setup ok, cache add and not working?
—
You are receiving this because you authored the thread.
Reply to this email directly, [ https://github.com/opnsense/core/issues/2008#issuecomment-353166168 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AXGwXVBZqw6VDdbLKME-ocpd75nTW-F2ks5tCWYRgaJpZM4RI1Wv | mute the thread ] .

Aha, should be an easy fix. Will ping you tomorrow morning :)

It looks like this is a problem in squid itself. If the service is running, squid -z -N says:
2017/12/21 06:49:36| Squid is already running!  Process ID 79343

and refuses to do the cache creation.

@renoow you can try this prior to starting to configure squid:
# opnsense-patch 25ca2ad 85c1e0a

However, the restart will always be necessary and I think manual stop + start already works.

There is more issues here, I'm circling around to fix this for 18.1.

This works now, but will not hit 17.7.x anymore.

authors: fichtner renoow

repo: opnsense/core


text:
Labels for interfaces.php

fix #5725

Using the left column item names as input for label is problematic for touch usage due to inadvertent toggling of settings as the left is commonly used for touch scrolling with the left thumb.  Example is block bogons and private networks.
The inadvertent changes get save along with intended changes and a wild goose chase for what broke the system ensues.
If for label to the right of the checkbox in these cases creates undesirable display clutter.  Perhaps make it screen reader only content.

@NOYB reading your comment many times and with many "eyses" we are not sure to understand it correctly.
Attach a left or a right label with the for attribute, put the focus on the check-boxe on a tap.
We haven't notice a negative mobile experience, with many tries.
Could you please illustrate the problem you encountered

On touch devices vertical scrolling is frequently done with the left thumb along the left part of the display where the item names such as "Block private networks" are located.

When those are used and "labels" for input elements (such as checkboxes) it is very easy to inadvertently toggle the setting while scrolling with noticing.  Tapping the label doesn't simple focus the checkbox.  It toggles the checkbox.
The inadvertent and unnoticed changed setting is then saved along with the intended settings.  Breaking the intended system behavior.
This is why I attached a separate label to the checkboxes.  But I'm unsure how well that seemingly duplication works out with screen readers.  Visually we can ignore some things like that much easier than a phrase repeated auditorily.  That could be very annoying.
One possibility may be to prevent the name in the left column from screen reading and make the checkbox attached label to be screen reader only content.  But that takes away the displayed "active label" which is beneficial for dexterity impaired.
I've not come up with a way to address both that I like.

@NOYB we have tried with several users, and no one succeeded to toggle a checkbox without explicitly made a "tap" on the label.
So we suspect, you' re a very quick with your phone :)
First question : is to be "quick" a good behavior when updating a firewall ? And second question : how many times did you update a firewall with your phone along a year ?
From a point of view of semantic, and accessibility the tag <label for"id_of_control"> is the right way.
the way with a second label on right, is not a good option, as you said the repetitions are not confortable for anyone.
However an option is to remove the <label for=""> and set an aria-label attribute on the control. But we miss the semantic way and it's more intrusive along existant pages, (not only adding html).
<label for="blockpriv"><?=gettext("Block private networks"); ?></label>

 <input name="blockpriv" type="checkbox" id="blockpriv" value="yes" <?=!empty($pconfig['blockpriv']) ? "checked=\"checked\"" : ""; ?> />

became
<?=gettext("Block private networks"); ?>

 <input name="blockpriv" type="checkbox" id="blockpriv"  aria-label="<?=gettext("Block private networks"); ?>" value="yes" <?=!empty($pconfig['blockpriv']) ? "checked=\"checked\"" : ""; ?> />

As you can see it's more intrusive.
We really prefer the implementation with labels, but we can make exceptions for checkboxes on commits with aria-labels if opnsense core-devs choose our way is not the right.
@AdSchellevis or other, we need your opinion here.
Thanks

Smartphones are not the only touch devices and testing deliberately is unlikely to result in an inadvertent action.  My purpose is to point out the potential, not squash the use.  Unless a good or better alternative exists.
I would like to make a suggestion though.  If the left column item names/titles are used for input labels then do this with all of them for consistency.  For example even though the enable item has a label, still make the left column item name/title a label also.

After internal discussion this approach through individual static PHP pages doesn't really work for us:
It's hundreds of changes and if the style doesn't match expectation we possibly change hundreds of lines again and rinse and repeat for over 100 such pages.
Instead, please improve the MVC templates which instantly translate to a large number of core and plugins pages and are easily deployed and reviewed. With this we can work on an agreeable style to go forward and maybe then start going through static pages to consolidate the UI style.
Cheers,
Franco

authors: NOYB fichtner jpcw


text:
security/acme-client: Add ALPN Challenge Type

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[X] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[X] I have searched the existing issues and I'm convinced that mine is new.
[X] When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
Many businesses I am aware of have performed some odd choices in blocking TCP/80 HTTP traffic on their edge firewalls in order to discourage the use of any incoming unencrypted HTTP traffic internally. Residential ISPs are also starting to enforce this as well under the guise of security for end users.
This creates an issue where the built in ACME client for OPNSense is unable to issue certificates using the HTTP-01 challenge type, and not all users may have the ability to use the DNS-01 challenge type due to lack of access or the registrar not supporting dynamic functionality.
Because of this issue, I am unable to use the built in haproxy and acme-client on my OPNSense firewall, and instead rely on a separate container for this service.
Describe the solution you'd like
This issue is requesting to add TLS-ALPN-01 as an additional challenge type to the acme-client plugin. acme.sh provides an alternate challenge type for these use cases with tls-alpn-01. This acts similar to a standalone HTTP challenge, but will utilize TCP/443 as the transport as opposed to the more commonly blocked TCP/80.
Reference documentation: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert#3-standalone-tls-alpn-mode
I have this working on my haproxy container as well using the below command to initiate a certificate issue using the alpn challenge:
acme.sh --issue --alpn [ -d {{ web-domain }} ]

I've implemented this in https://github.com/opnsense/plugins/pull/2688/commits/7f0ec9b47e495d51e76d45eade211672db5e421f. However, this is based on the implemention of the HTTP-01 challenge type, so it's prone to the same failures and instability (because it tries to guess the correct settings and needs to use a dynamic port forward).
Besides that I can't test it, but the generated acme.sh command looks good to me:
Dec  8 00:21:14 opnsense.example.com opnsense[38935]: AcmeClient: running acme.sh command: /usr/local/sbin/acme.sh --issue --syslog 7 --debug --server 'letsencrypt_test' --alpn [...] --tlsport '43581' [...]

And the acme.sh log seems to confirm that TLS-ALPN-01 is being used:
Dec  8 00:21:16 opnsense.example.com acme.sh[9535]: [Wed Dec  8 00:21:16 CET 2021] Standalone alpn mode.
Dec  8 00:21:16 opnsense.example.com acme.sh[10419]: [Wed Dec  8 00:21:16 CET 2021] _checkport='43581'

Confirmed this is working in 3.6 using the test server.
Thank you for the fast turnaround!

repo: opnsense/plugins


text:
[COOK-4555] #127 Adding db user fails and replication support

*In PostgresSQL 9.1, the REPLICATION and NOREPLICATION keywords
were added.
*Adding replication support causes earlier clients to see see a syntax
error causing failure for users to add. This was evident in #127
as well as the jira cookbook on centos6.
*This fix uses a pgsql function to check for the existence of
the replication keyword. If it does not exist, the options will
not be used, avoiding the syntax error and restoring proper operation.

Hi thanks for the patch, I like the approach and intend to merge this, but I have a few comments.
I will be making the comments inline

@kisoku I agree with your idea. I've made the change requested and added a test case for it.

Hi thanks for the changes. I'm not super keen on the test you added, I feel monkey patching libraries from a recipe is not a very good pattern to encourage.
As it is the existing test suite fails to converge on platforms with an older postgres (centos-510, and centos-64), and I can confirm that the new code fixes the breakage.

@kisoku Ya, I wasn't too big a fan of making the method public either as it doesn't "do" anything so doesn't qualify as public. Test removed.

Merging this now.

Bad news guys, it looks like at least in PostgreSQL server 9.3.6, the REPLICATION and NOREPLICATION don't appear in the select* from pg_get_keywords() query, meaning this commit eliminates the 'replication' attribute from user creation entirely.  Since this commit, my cookbooks cannot use the replication LWRP to create users that are allowed to replicate.
Pull request https://github.com/opscode-cookbooks/database/pull/139 introduces a more reliable way of determining whether the postgres server is greater than 9.1 and thus capable of receiving the REPLICATION attribute.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@dtsosie

Please sign the CLA here.

Yeah, I can attest to this not working either. On postgres 9.2 a select * from pg_get_keywords() does not return any 'replication' word thus the ROLE does not get assigned.  Does the if keyword?('REPLICATION') piece even need to be there?  Just have it set REPLICATION role if true..

@ericwingate From the sound of this bug report, older versions of Postgres (prior to 9.01) error out on that line without the check because they don't recognize the REPLICATION role keyword.
Pull request https://github.com/opscode-cookbooks/database/pull/139 explicitly checks that the Postgres version via a SHOW server_version_num; query before allowing the newly introduced REPLICATION keyword.

authors: SimonKaluza chef-supermarket dtsosie ericwingate kisoku

repo: opscode-cookbooks/database


text:
Create global.json

added global json for net6 targeting

added global json for net6 targeting

repo: opsgilitybrian/GitHubDevopsSimpleWeb


text:
Creating a MenuPolicy

Hi there,
I am trying to create a menu policy since according to this PR it should be available: https://github.com/optimistdigital/nova-menu-builder/pull/21
I created a MenuPolicy with php artisan make:policy MenuPolicy --model=Menu then changed the actual model to
use OptimistDigital\MenuBuilder\Models\Menu; but it does not seem to have any effect.. Am I missing something obvious here? :D
I would love to PR the actual documentation of this feature in case you could explain to me how it actually works?
Thanks!

Bump

Hi!
Please check out Laravel's documentation on policies: https://laravel.com/docs/8.x/authorization#creating-policies
Policies aren't autoloaded, you must apply them manually to classes. Ie:
class AuthServiceProvider extends ServiceProvider
{
    /**
     * The policy mappings for the application.
     *
     * @var array
     */
    protected $policies = [
        Menu::class => MenuPolicy::class,
    ];

    // ....

}

Thank you @Tarpsvo !

authors: Reached Tarpsvo

repo: optimistdigital/nova-menu-builder


text:
Strange behaviour when using the helper in web.php

I can't quite work out what's happening here.
Locally, this works fine without any issues.
Package is installed and I can update via Nova no problem.
I have the following conditional in web.php
if (nova_get_setting('site_is_live')) {
    Route::get('/', SplashPageController::class);
} else {
    Route::get('/', function () {
        return view('index');
    });
}

However, when I attempt to deploy to Vapor environment
build:
      - 'composer install --no-dev'
      - 'php artisan event:cache'
      - 'npm ci && npm run prod && rm -rf node_modules'

I run into a db access error.
If I remove that conditional in web.php - it deploys just fine.
Can't figure out why.
Any ideas?

Hi! The issue is that web.php is fully executed when running artisan commands and nova_get_setting() tries to query the value from the database, which is not there during the build process. You should:
a) Run php artisan event:cache during startup of the web application
b) Change how the routes are made to:
Route::get('/', function () {
        return nova_get_setting('site_is_live') ? (new SplashPageController)->index() :  view('index');
});

repo: optimistdigital/nova-settings


text:
Crash Report null

Crash Report
What happened
(The user did not submit additional information)
Context information

Plugin: Apache Avro IDL Schema Support 213.3.1
IDE: IntelliJ IDEA 2022.3.1
JVM: OpenJDK 64-Bit Server VM (JetBrains s.r.o.) 17.0.5+1-b653.23
OS: Mac OS X (aarch64) 13.1

Exception
com.intellij.diagnostic.PluginException: Cannot create extension (class=opwvhk.intellij.avro_idl.editor.AvroIdlAngleBracketTypedHandler) [Plugin: net.sf.opk.avro-schema-support]
	at com.intellij.serviceContainer.ComponentManagerImpl.createError(ComponentManagerImpl.kt:1051)
	at com.intellij.openapi.extensions.impl.XmlExtensionAdapter.doCreateInstance(XmlExtensionAdapter.kt:70)
	at com.intellij.openapi.extensions.impl.XmlExtensionAdapter.createInstance(XmlExtensionAdapter.kt:31)
	at com.intellij.openapi.extensions.impl.ExtensionPointImpl.processAdapter(ExtensionPointImpl.java:473)
	at com.intellij.openapi.extensions.impl.ExtensionPointImpl.processAdapters(ExtensionPointImpl.java:421)
	at com.intellij.openapi.extensions.impl.ExtensionPointImpl.computeExtensionList(ExtensionPointImpl.java:249)
	at com.intellij.openapi.extensions.impl.ExtensionPointImpl.getExtensionList(ExtensionPointImpl.java:243)
	at com.intellij.openapi.extensions.ExtensionPointName.getExtensionList(ExtensionPointName.java:39)
	at com.intellij.codeInsight.editorActions.TypedHandler.beforeExecute(TypedHandler.java:119)
	at com.intellij.codeInsight.template.impl.editorActions.TypedActionHandlerBase.beforeExecute(TypedActionHandlerBase.java:37)
	at com.intellij.codeInsight.template.impl.editorActions.TypedActionHandlerBase.beforeExecute(TypedActionHandlerBase.java:37)
	at com.intellij.codeInsight.template.impl.editorActions.TypedActionHandlerBase.beforeExecute(TypedActionHandlerBase.java:37)
	at com.intellij.openapi.editor.impl.DefaultRawTypedHandler.beforeExecute(DefaultRawTypedHandler.java:32)
	at com.intellij.openapi.editor.impl.EditorFactoryImpl$MyRawTypedHandler.beforeExecute(EditorFactoryImpl.java:305)
	at com.maddyhome.idea.vim.VimTypedActionHandler.beforeExecute(VimTypedActionHandler.kt:60)
	at com.intellij.openapi.editor.actionSystem.TypedAction.beforeActionPerformed(TypedAction.java:193)
	at com.intellij.openapi.editor.impl.EditorImpl.processKeyTypedImmediately(EditorImpl.java:1324)
	at com.intellij.openapi.editor.impl.EditorImpl.processKeyTyped(EditorImpl.java:1309)
	at com.intellij.openapi.editor.impl.EditorImpl.processKeyTyped(EditorImpl.java:3492)
	at com.intellij.openapi.editor.impl.EditorImpl$7.keyTyped(EditorImpl.java:1148)
	at java.desktop/java.awt.AWTEventMulticaster.keyTyped(AWTEventMulticaster.java:247)
	at java.desktop/java.awt.AWTEventMulticaster.keyTyped(AWTEventMulticaster.java:247)
	at java.desktop/java.awt.Component.processKeyEvent(Component.java:6603)
	at java.desktop/javax.swing.JComponent.processKeyEvent(JComponent.java:2899)
	at java.desktop/java.awt.Component.processEvent(Component.java:6425)
	at java.desktop/java.awt.Container.processEvent(Container.java:2266)
	at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5022)
	at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2324)
	at java.desktop/java.awt.Component.dispatchEvent(Component.java:4854)
	at java.desktop/java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1953)
	at java.desktop/java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:886)
	at java.desktop/java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:1166)
	at java.desktop/java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:1023)
	at java.desktop/java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:849)
	at com.intellij.ide.IdeKeyboardFocusManager.lambda$dispatchEvent$0(IdeKeyboardFocusManager.java:32)
	at com.intellij.openapi.application.TransactionGuardImpl.performActivity(TransactionGuardImpl.java:105)
	at com.intellij.ide.IdeEventQueue.performActivity(IdeEventQueue.java:615)
	at com.intellij.ide.IdeKeyboardFocusManager.dispatchEvent(IdeKeyboardFocusManager.java:32)
	at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4903)
	at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2324)
	at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2802)
	at java.desktop/java.awt.Component.dispatchEvent(Component.java:4854)
	at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:781)
	at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:730)
	at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:724)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:97)
	at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:754)
	at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:752)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
	at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:751)
	at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:909)
	at com.intellij.ide.IdeEventQueue.dispatchKeyEvent(IdeEventQueue.java:818)
	at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:750)
	at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$5(IdeEventQueue.java:437)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:772)
	at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$6(IdeEventQueue.java:436)
	at com.intellij.openapi.application.TransactionGuardImpl.performActivity(TransactionGuardImpl.java:113)
	at com.intellij.ide.IdeEventQueue.performActivity(IdeEventQueue.java:615)
	at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$7(IdeEventQueue.java:434)
	at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:813)
	at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:480)
	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:207)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128)
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)
	at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:92)
Caused by: com.intellij.diagnostic.PluginException: Cannot create class opwvhk.intellij.avro_idl.editor.AvroIdlAngleBracketTypedHandler (classloader=PluginClassLoader(plugin=PluginDescriptor(name=Apache Avro IDL Schema Support, id=net.sf.opk.avro-schema-support, descriptorPath=plugin.xml, path=~/Library/Application Support/JetBrains/Toolbox/apps/IDEA-U/ch-0/223.8214.52/IntelliJ IDEA.app.plugins/avro-schema-support, version=213.3.1, package=null, isBundled=false), packagePrefix=null, instanceId=401, state=active))
	at com.intellij.serviceContainer.ComponentManagerImpl.instantiateClass(ComponentManagerImpl.kt:989)
	at com.intellij.openapi.extensions.impl.XmlExtensionAdapter.instantiateClass(XmlExtensionAdapter.kt:79)
	at com.intellij.openapi.extensions.impl.XmlExtensionAdapter$SimpleConstructorInjectionAdapter.instantiateClass(XmlExtensionAdapter.kt:90)
	at com.intellij.openapi.extensions.impl.XmlExtensionAdapter.doCreateInstance(XmlExtensionAdapter.kt:50)
	... 68 more
Caused by: java.lang.NoClassDefFoundError: Could not initialize class opwvhk.intellij.avro_idl.AvroIdlLanguage
	at opwvhk.intellij.avro_idl.psi.AvroIdlElementType.<init>(AvroIdlElementType.java:8)
	at opwvhk.intellij.avro_idl.psi.AvroIdlTypes.<clinit>(AvroIdlTypes.java:11)
	at opwvhk.intellij.avro_idl.editor.AvroIdlAngleBracketTypedHandler.<clinit>(AvroIdlAngleBracketTypedHandler.java:18)
	at java.base/java.lang.invoke.DirectMethodHandle.allocateInstance(DirectMethodHandle.java:520)
	at com.intellij.serviceContainer.ComponentManagerImpl.instantiateClass(ComponentManagerImpl.kt:950)
	... 71 more

Duplicate of #39

repo: opwvhk/avro-schema-support