您好，u2net的backbone配合bce_ssim_loss的损失函数进行分割，效果如何？

首先非常感谢您的工作，请问您尝试过u2net的backbone配合bce_ssim_loss的损失函数进行分割吗，想知道效果

Thanks for your interest. We tried to use U2Net+BCE+SSIM+IOU. But the
difference of performance in terms of F-measure is not significant. We
thought it is probably because that U2Net is able to capture fine details
so that the multi-scale supervision from the hybrid loss couldn't further
improve the performance in terms of F-measure. But it depends on your task
and dataset. For example, if you want to segment targets with solid
boundaries then you could try to use the BSI other than BCE to achieve
shaper and smooth boundaries. If your targets include human hairs or fur of
animals, we suggest to use BCE to achieve relatively smooth transition
around hairs or fur.
On Mon, Apr 26, 2021 at 4:02 PM dlutzhouyue @.***>
wrote:

首先非常感谢您的工作，请问您尝试过u2net的backbone配合bce_ssim_loss的损失函数进行分割吗，想知道效果
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xuebinqin/U-2-Net/issues/196, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSGORP5CMCY745J6ORU7IDTKVI4LANCNFSM43SXVHTA
.

--
Xuebin Qin
PhD
Department of Computing Science
University of Alberta, Edmonton, AB, Canada
Homepage:https://webdocs.cs.ualberta.ca/~xuebin/


CASMINST-4219 - Add instructions to merge in new CSM 1.2 VCS content to upgrade procedure

Summary and Scope
A CSM upgrade can introduce new content to the CSM configuration management repository.
It is necessary to merge this content into any working branch then update the CFS configuration used for NCN personalization to ensure this new Ansible content is applied.
Issues and Related PRs

Resolves CASMINST-4219

Testing
Tested on:

hela

Test description:
Procedure tested on hela.
Risks and Mitigations
Pull Request Checklist

[ ] Version number(s) incremented, if applicable
[ ] Copyrights updated
[ ] License file intact
[X] Target branch correct
[ ] CHANGELOG.md updated
[X] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

Closing as this will be handled via CASMINST-4218


[region-isolation] Add feature flag for TransferringArgsAndResults

Just trying to cut off things from larger commits to make it easier to review.

https://github.com/apple/swift/pull/70653
@swift-ci test


[htslib, htscodecs] New ports

[X] Changes comply with the maintainer guide.
[X] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[X] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.
[X] The versioning scheme in vcpkg.json matches what upstream says.
[X] The license declaration in vcpkg.json matches what upstream says.
[X] The installed as the "copyright" file matches what upstream says.
[X] The source code of the component installed comes from an authoritative source.
[X] The generated "usage text" is accurate. See adding-usage for context.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is in the new port's versions file.
[X] Only one version is added to each modified port's versions file.

@teo-tsirpanis Thanks for your PR, Is work still being done for this PR?

I will look at the Android failures later.

I can't download the artifacts to check the Android failures.

I can't download the artifacts to check the Android failures.

Can be downloaded as always.
ld.lld: error: unable to find library -lpthread
clang-17: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Makefile:361: libhts.so] Error 1
make: *** Waiting for unfinished jobs....

This should probably be -pthread, for most modern systems.

Thanks @dg0yt! I finally found where the artifacts were located in AzDo.

CI is green.

All features passed with following triplet:
x64-linux

Feedback addressed.

I was unable to install these ports. I'm using the a code spaces instance with Ubuntu (I believe)
% vcpkg install htslib htscodecs

CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
    Command failed: /usr/bin/bash -c "V=1 ./../src/1.20-30e933fbb9.clean/configure  \"--with-external-htscodecs\" \"--disable-libcurl\" \"--disable-gcs\" \"--disable-s3\" \"--disable-plugins\" \"--disable-bz2\" \"--disable-lzma\" \"--without-libdeflate\" \"--disable-silent-rules\" \"--verbose\" \"--disable-shared\" \"--enable-static\" \"--prefix=/workspaces/vcpkg/installed/x64-linux/debug\" \"--bindir=\\${prefix}/../tools/htslib/debug/bin\" \"--sbindir=\\${prefix}/../tools/htslib/debug/sbin\" \"--libdir=\\${prefix}/lib\" \"--includedir=\\${prefix}/../include\" \"--datarootdir=\\${prefix}/share/htslib\""
    Working Directory: /workspaces/vcpkg/buildtrees/htslib/x64-linux-dbg
    Error code: 1
    See logs for more information:
      /workspaces/vcpkg/buildtrees/htslib/config-x64-linux-dbg-config.log
      /workspaces/vcpkg/buildtrees/htslib/config-x64-linux-dbg-out.log
      /workspaces/vcpkg/buildtrees/htslib/config-x64-linux-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:866 (vcpkg_execute_required_process)
  ports/htslib/portfile.cmake:32 (vcpkg_configure_make)
  scripts/ports.cmake:192 (include)

/workspaces/vcpkg/buildtrees/htslib/config-x64-linux-dbg-err.log
configure: WARNING: unrecognized options: --disable-silent-rules, --disable-shared, --enable-static
configure: error: libhtscodecs development files not found: missing library

You asked to use an external htscodecs library, but do not have the
required header / library files.  You either need to supply these and
if necessary set CPPFLAGS and LDFLAGS so the compiler can find them;
or configure using --without-external-htscodecs to build the required
functions from the htscodecs submodule.

It looks like it can't find:

htscodecs/htscodecs.h
libhtscodecs.so

Weird. Do these files exist? Did htscodecs build correctly? Can you try installing only htslib?

Apparently when trying to link to -lhtscodecs it fails because it does not find pthread. 🤔

After the latest patch, installing succeeds on a codespace.


Remove util.rs

Thanks Nathan! I actually had a version of this at one point in labelled.
Personally I think it might be cleaner to just use rev().max_by_key(|g| g.dimension) everywhere instead the trait.
Also be aware that when you merge this, it will cause a merge conflict with labelled so you'll have to rebase labelled as well.

Personally I think it might be cleaner to just use rev().max_by_key(|g| g.dimension) everywhere instead the trait.

I would tend to agree with you if it wasn't for the need for rev which without documentation seems very strange.

Also be aware that when you merge this, it will cause a merge conflict with labelled so you'll have to rebase labelled as well.

Ah ok! Will do.

I would tend to agree with you if it wasn't for the need for rev which without documentation seems very strange.

Ok fair enough!


How to specify database connection other than test?

In fixture classes there a way to set database connection name(via $connection) in order to insert data into that database.
How can we achieve same with fixture factories?

@ishan-eventrac generally the test data will be inserted in the test DB as documented here.
You should be able to set the connection of your factory in the initialize method as follows:
    protected function initialize(): void
    {
        $this->getTable()->setConnection(ConnectionManager::get('test_foo'));
    }


Add script which calculates coverage statistics for the openMINDS instance library

i.e. for each instance, which properties have been defined, and for each terminology, what percentage of instances have a definition for a given property.
The script generates web pages which we plan to deploy via GitHub pages at https://openmetadatainitiative.github.io/openMINDS_instances/

Everything is functioning as expected. Additionally, I recommend adding a requirements.txt file for dependency management.


impl io::Write for SegVec<u8>

very straightforward implementation of the write trait

Thank you for this - even though it's a very simple change, would you mind adding a test?

sure! i'll change this implementation a bit, however. i think it can be optimized further with something like a extend_from_slice.

Acknowledged - I should have some time later today to look this over

Once we finish up the review on #41 I can come back and merge this, but I want to fix up the potential safety issue over there first, then we can rebase this on the master branch and I can push it through :)

Now that #41 has been merged, can you rebase this on the master branch?

done!

Thanks, merged!


cli/run.go:110	scan run failed{error 26 0  failed to initialize OPA policy engine}

Hi Team,
Terrascan is failing while doing scan.
We are using docker image to run terrascan accurics/terrascan:1.5.0
Command we are using to run
   terrascan init
   terrascan scan --use-colors t .

Error we are facing.
2022-03-03T05:[40](https://gitlab.com/falabella-gitlab/catalyst/core/deployment/commerce-infrastructure/-/jobs/2157165888#L40):57.980Z	error	opa/engine.go:219	error compiling rego files{rule 15 0 authUsersReadAccess <nil>} {raw rego 15 0 package accurics
authUsersReadAccess[retVal] {
    bucket := input.aws_s3_bucket[_]
    bucket.config.acl == "authenticated-read"
    traverse = "acl"
    retVal := { "Id": bucket.id, "ReplaceType": "edit", "CodeType": "attribute", "Traverse": traverse, "Attribute": "acl", "AttributeDataType": "string", "Expected": "private", "Actual": bucket.config.acl }
}
authUsersReadAccess<no value>[retVal] {
    bucket := input.aws_s3_bucket_acl[_]
    bucket.config.acl == "authenticated-read"
    traverse = "acl"
    retVal := { "Id": bucket.id, "ReplaceType": "edit", "CodeType": "attribute", "Traverse": traverse, "Attribute": "acl", "AttributeDataType": "string", "Expected": "private", "Actual": bucket.config.acl }
} <nil>} {error 26 0  1 error occurred: authUsersReadAccess:11: rego_parse_error: unexpected assign token: non-terminated set
	    bucket := input.aws_s3_bucket_acl[_]
	           ^}
2022-03-03T05:40:57.982Z	error	opa/engine.go:261	error compiling rego files{policy path 15 0 /home/terrascan/.terrascan/pkg/policies/opa/rego/aws <nil>} {error 26 0  1 error occurred: authUsersReadAccess:11: rego_parse_error: unexpected assign token: non-terminated set
	    bucket := input.aws_s3_bucket_acl[_]
	           ^}
2022-03-03T05:40:57.983Z	error	runtime/executor.go:124	failed to initialize OPA policy engine
2022-03-03T05:40:57.984Z	error	cli/run.go:110	scan run failed{error 26 0  failed to initialize OPA policy engine}

I have the same issue.

@sachinar , can you please try using a newer version of terrascan?

@kanchwala-yusuf Though I faced with the issue on terrascan 1.13.2 which is the latest version. I think the issue is caused by the added policy at https://github.com/accurics/terrascan/pull/1175 . As I am not sure we can fix it quickly, I suggested we revert it at the moment.

Same issue

@kanchwala-yusuf,
With latest version also getting same error.
Running the scan
$ /go/bin/terrascan init
$ /go/bin/terrascan scan --use-colors t .
2022-03-03T07:06:21.041Z	warn	v1/load-dir.go:45	directory '/builds/N9ysWiRs/0/falabella-gitlab/catalyst/core/deployment/commerce-infrastructure' has no files named Dockerfile. Use -f flag if Dockerfiles follow a different naming convention.
2022-03-03T07:06:32.318Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/2z8i0u/tiller/main.tf:71,34-37: Variables not allowed; Variables may not be used here.
/tmp/2z8i0u/tiller/main.tf:71,54-57: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.320Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/kl07sv/jumpbox/main.tf:45,31-34: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.320Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/kl07sv/jumpbox/main.tf:46,34-37: Variables not allowed; Variables may not be used here.
/tmp/kl07sv/jumpbox/main.tf:46,62-65: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.360Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/2z8i0u/tiller/main.tf:71,34-37: Variables not allowed; Variables may not be used here.
/tmp/2z8i0u/tiller/main.tf:71,54-57: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.383Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/2z8i0u/tiller/main.tf:71,34-37: Variables not allowed; Variables may not be used here.
/tmp/2z8i0u/tiller/main.tf:71,54-57: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.387Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/kl07sv/jumpbox/main.tf:45,31-34: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.387Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/kl07sv/jumpbox/main.tf:46,34-37: Variables not allowed; Variables may not be used here.
/tmp/kl07sv/jumpbox/main.tf:46,62-65: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.4[29](https://gitlab.com/falabella-gitlab/catalyst/core/deployment/commerce-infrastructure/-/jobs/2157341778#L29)Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/kl07sv/jumpbox/main.tf:45,[31](https://gitlab.com/falabella-gitlab/catalyst/core/deployment/commerce-infrastructure/-/jobs/2157341778#L31)-34: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:[32](https://gitlab.com/falabella-gitlab/catalyst/core/deployment/commerce-infrastructure/-/jobs/2157341778#L32).429Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/kl07sv/jumpbox/main.tf:46,[34](https://gitlab.com/falabella-gitlab/catalyst/core/deployment/commerce-infrastructure/-/jobs/2157341778#L34)-37: Variables not allowed; Variables may not be used here.
/tmp/kl07sv/jumpbox/main.tf:46,62-65: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.452Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/kl07sv/jumpbox/main.tf:45,31-34: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.452Z	error	commons/extract-container-images.go:268	error fetching containers from k8s resource: /tmp/kl07sv/jumpbox/main.tf:46,34-37: Variables not allowed; Variables may not be used here.
/tmp/kl07sv/jumpbox/main.tf:46,62-65: Variables not allowed; Variables may not be used here.
2022-03-03T07:06:32.582Z	error	opa/engine.go:231	error compiling rego files{rule 15 0 authUsersReadAccess <nil>} {raw rego 15 0 package accurics
authUsersReadAccess[retVal] {
    bucket := input.aws_s3_bucket[_]
    bucket.config.acl == "authenticated-read"
    traverse = "acl"
    retVal := { "Id": bucket.id, "ReplaceType": "edit", "CodeType": "attribute", "Traverse": traverse, "Attribute": "acl", "AttributeDataType": "string", "Expected": "private", "Actual": bucket.config.acl }
}
authUsersReadAccess<no value>[retVal] {
    bucket := input.aws_s3_bucket_acl[_]
    bucket.config.acl == "authenticated-read"
    traverse = "acl"
    retVal := { "Id": bucket.id, "ReplaceType": "edit", "CodeType": "attribute", "Traverse": traverse, "Attribute": "acl", "AttributeDataType": "string", "Expected": "private", "Actual": bucket.config.acl }
} <nil>} {error 26 0  1 error occurred: authUsersReadAccess:11: rego_parse_error: unexpected assign token: non-terminated set
	    bucket := input.aws_s3_bucket_acl[_]
	           ^}
2022-03-03T07:06:32.582Z	error	opa/engine.go:267	error compiling rego files{policy path 15 0 /home/terrascan/.terrascan/pkg/policies/opa/rego/aws <nil>} {error 26 0  1 error occurred: authUsersReadAccess:11: rego_parse_error: unexpected assign token: non-terminated set
	    bucket := input.aws_s3_bucket_acl[_]
	           ^}
2022-03-03T07:06:32.582Z	error	runtime/executor.go:198	failed to initialize policy engine for path /home/terrascan/.terrascan/pkg/policies/opa/rego/aws, error: failed to initialize OPA policy engine
2022-03-03T07:06:32.582Z	error	runtime/executor.go:199	perform 'terrascan init' command and then try running the scan command again
2022-03-03T07:06:32.582Z	error	cli/run.go:1[35](https://gitlab.com/falabella-gitlab/catalyst/core/deployment/commerce-infrastructure/-/jobs/2157341778#L35)	scan run failed{error 26 0  failed to initialize OPA policy engine}

@harkirat22 : Could you please check your latest commit, since it changed something in the s3 buckets and the error fits into that category (unittest pipeline is failing, too).
I read, that terrascan init is "downloading the latest Rego policies into ~/.terrascan". Is that true and if it is, can we pinpoint that behaviour to the latest release instead of master?

Can confirm that this is also happening in our pipeline. Can be reproduced in an empty directory
docker run --rm -v "$(pwd):/code" accurics/terrascan:1.13.2 scan /code

If you're not using aws, setting the policy to azure seems to be fine:
docker run --rm -v "$(pwd):/code" accurics/terrascan:1.13.2 scan -t azure /cod

I can confirm this, tried with various Terrascan versions. The issue seems to come from the downloaded current AWS policies.
Try this and see that it works without AWS policies:
docker run --rm  -v ":/data"  accurics/terrascan:1.13.2 scan -d /data --policy-type azure,docker,gcp,github,k8s

I tried with 1.12.0 and 1.13.2 and with both versions facing issue.

@pflueg the fix has been pushed. Sorry for the inconvenience. I would suggest everyone to try now, and if any issue persists please let us know.

@harkirat22 It is still faling.
$ /go/bin/terrascan init
$ /go/bin/terrascan scan --use-colors t .
2022-03-03T11:39:52.013Z	warn	v1/load-dir.go:45	directory '/builds/N9ysWiRs/0/core/deployment/commerce-iam' has no files named Dockerfile. Use -f flag if Dockerfiles follow a different naming convention.
Scan Summary -
	File/Folder         :	/builds/N9ysWiRs/0/core/deployment/commerce-iam
	IaC Type            :	all
	Scanned At          :	2022-03-03 11:39:56.436048677 +0000 UTC
	Policies Validated  :	2
	Violated Policies   :	0
	Low                 :	0
	Medium              :	0
	High                :	0
Cleaning up file based variables
00:01
ERROR: Job failed: command terminated with exit code 4

@harkirat22 I have made sure it works well on the github action I implemented. Thank you so much for quickly fixing it!
https://github.com/yu-iskw/action-terrascan
https://github.com/yu-iskw/action-terrascan/runs/5406557988?check_suite_focus=true
terrascan scan --output json --iac-type terraform --severity LOW --verbose
  {
    "results": {
      "violations": [
        {
          "rule_name": "uniformBucketEnabled",
          "description": "Ensure that Cloud Storage buckets have uniform bucket-level access enabled.",
          "rule_id": "AC_GCP_0234",
          "severity": "MEDIUM",
          "category": "Identity and Access Management",
          "resource_name": "failed_bucket",
          "resource_type": "google_storage_bucket",
          "module_name": "root",
          "file": "google_strage_bucket.tf",
          "plan_root": "./",
          "line": 1
        },
        {
          "rule_name": "uniformBucketEnabled",
          "description": "Ensure that Cloud Storage buckets have uniform bucket-level access enabled.",
          "rule_id": "AC_GCP_0234",
          "severity": "MEDIUM",
          "category": "Identity and Access Management",
          "resource_name": "failed_bucket",
          "resource_type": "google_storage_bucket",
          "module_name": "module_a",
          "file": "../modules/module_a/google_strage_bucket.tf",
          "plan_root": "./",
          "line": 1
        }
      ],
      "skipped_violations": null,
      "scan_summary": {
        "file/folder": "/home/runner/work/action-terrascan/action-terrascan/testdata/terraform",
        "iac_type": "terraform",
        "scanned_at": "2022-03-03 11:56:52.236[507](https://github.com/yu-iskw/action-terrascan/runs/5406557988?check_suite_focus=true#step:3:507)713 +0000 UTC",
        "policies_validated": 3,
        "violated_policies": 2,
        "low": 0,
        "medium": 2,
        "high": 0
      }
    }
  }

@harkirat22 : Thanks alot - that did it. Is it possible somehow, that init is using a release tag instead of master?
@sachinar : Your error shows a missing Dockerfile. So that might be a problem on your end

@pflueg I am running terrascan for infra which is written in terraform. How Dockerfile comes in picture?

@sachinar : Maybe it has something to do with this: https://github.com/accurics/terrascan/issues/1036#issuecomment-1046551402 . Try -i terraform as an option. Nevertheless, the error of the op is solved here.

@pflueg everything is working fine with older version i.e 1.5.0 but not working with latest version 1.13.2


Removed sleeping message during day

Fixed problem with actionbar showing "everyone is sleeping"-message during day.
https://github.com/nkomarn/Harbor/issues/4
This might summon it better:
(amount_of_player_sleeping == (total_players - player_with_special_permission)) AND (total_players > 1) => (0 == 2-2) AND (2 > 1)

Thank you :)


Arangod wont start the database

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[X ] 3.1
[ ] 3.2 pre-releases: ___
[ ] self-compiled devel branch

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[ ] Linux

[ ] Debian .deb
[ ] Ubuntu .deb
[ ] SUSE   .rpm
[ ] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[ ] docker - official docker library
[ ] other:

[X] Windows, version:  7
[ ] MacOS, version:

this is an installation-related issue:
Describe which steps you carried out, what you expected to happen and what actually happened.
When I run ArangoDB from command line arangod testDB the database does not start. Instead, i get the output
2017-03-21T12:29:49Z [2720] INFO ArangoDB 3.1.14 [win64] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.2a 19 Mar 2015
2017-03-21T12:29:49Z [2720] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-03-21T12:29:49Z [2720] INFO Starting up with role SINGLE
2017-03-21T12:29:49Z [2720] INFO Authentication is turned on
2017-03-21T12:29:49Z [2720] INFO Authentication system only

and the program terminates. This seems to be reoccurring when I perform operations with arangoimp. The first time this happened, I had run arangoimp without having the database running. The second time this happened, arangoimp had frozen and I terminated it. The DB froze, and when I tried to restart it, I found that I could not.
Instead I would be expecting:
The database to run

This may be a duplicate of https://github.com/arangodb/arangodb/issues/2376?
Can you re-try with 3.1.15?

Yes, I will do some testing today and report back if the error reoccurs

I cannot reproduce the error on 3.1.15. looks like it fixed it. Thanks!

okies, marking as closed then.


Scene Inspector

The scene inspector is currently not implemented.

decided not to fix because its usefulness is unclear. commented out the UI component


Software Installation Instructions Needs An Update

When trying to execute the step 2:
git clone --recursive https://github.com/thomasjacquin/allsky.git
It will ask for a user and password, then fail (even after providing a valid one) because GitHub now needs a token in order to sign in
Regards!

@ckuethe, @linuxkidd, @AndreasLMeg, have you guys seen this?  I just did a full install yesterday and wasn't asked for a password.

I've only seen it when using ssh access to github, not with https access..
@darkmetalman

Can you confirm for sure it happened with https git clone?
If so, can you provide:

a console copy/paste of the session.
output of git --version

Also, please confirm your .gitconfig does not have something like:

[url<EMAIL_ADDRESS>  insteadOf = https://github.com/

Thanks!

Hello!!
I tried again this morning, but this time with a fresh install of Raspberry Pi OS Lite and everything worked fine, I don't know what caused the issue.
Thanks for your help!!

Great to hear!  I'll go ahead and close out this issue.  Let us know if you run into any other problems. :)


IMPORTANT Implement the views and answered field in the Chatter_Discussion table and TinyMCE error

I want to be able to notify a user on when there is a comment in his discussion.
Also
When I input an image source in the TinyMCE editor, it shows the preview but after posting it doesn't display.
# WHEN I UPLOAD

# AFTER UPLOADING

# I CHECK CHROME CONSOLE

I EDIT IT FROM THE DISCUSSION

Please can you tell me what part of the code to edit to fix this... I can try to find it myself but i still have a lot to do in a short period of time.

Thanks Mate. Good Job.

What is the full URL for the image?

It's there

@Dsaint109: Full URL including domain and all that (you may replace domain with xxx.xxx).

Closed due to inactivity.

I found the solution, Thanks


docs: added storybook, release ci

yarn.lock changes
Summary

Status
Count

533

96

Click to toggle table visibility

Name
Status
Previous
Current

@aw-web-design/x-default-browser
ADDED
-
1.4.126

@babel/core
UPDATED
7.22.10
7.22.11

@babel/helper-create-class-features-plugin
UPDATED
7.22.10
7.22.11

@babel/helpers
UPDATED
7.22.10
7.22.11

@babel/parser
UPDATED
7.22.10
7.22.11

@babel/plugin-transform-modules-commonjs
UPDATED
7.22.5
7.22.11

@babel/plugin-transform-typescript
UPDATED
7.22.10
7.22.11

@babel/preset-flow
ADDED
-
7.22.5

@babel/register
ADDED
-
7.22.5

@babel/traverse
UPDATED
7.22.10
7.22.11

@babel/types
UPDATED
7.22.10
7.22.11

@base2/pretty-print-object
ADDED
-
1.0.1

@colors/colors
ADDED
-
1.5.0

@discoveryjs/json-ext
ADDED
-
0.5.7

@emotion/use-insertion-effect-with-fallbacks
ADDED
-
1.0.1

@fal-works/esbuild-plugin-global-externals
ADDED
-
2.1.2

@floating-ui/core
ADDED
-
1.4.1

@floating-ui/dom
ADDED
-
1.5.1

@floating-ui/react-dom
ADDED
-
2.0.1

@floating-ui/utils
ADDED
-
0.1.1

@isaacs/string-locale-compare
ADDED
-
1.1.0

@jest/console
UPDATED
29.6.2
29.6.4

@jest/core
UPDATED
29.6.2
29.6.4

@jest/environment
UPDATED
29.6.2
29.6.4

@jest/expect-utils
UPDATED
29.6.2
29.6.4

@jest/expect
UPDATED
29.6.2
29.6.4

@jest/fake-timers
UPDATED
29.6.2
29.6.4

@jest/globals
UPDATED
29.6.2
29.6.4

@jest/reporters
UPDATED
29.6.2
29.6.4

@jest/source-map
UPDATED
29.6.0
29.6.3

@jest/test-result
UPDATED
29.6.2
29.6.4

@jest/test-sequencer
UPDATED
29.6.2
29.6.4

@jest/transform
UPDATED
29.6.3
29.6.4

@joshwooding/vite-plugin-react-docgen-typescript
ADDED
-
0.2.1

@juggle/resize-observer
ADDED
-
3.4.0

@mdx-js/react
ADDED
-
2.3.0

@ndelangen/get-tarball
ADDED
-
3.0.9

@nejcm/configs
UPDATED
1.2.1
1.2.2

@npmcli/arborist
ADDED
-
6.3.0

@npmcli/config
ADDED
-
6.2.1

@npmcli/disparity-colors
ADDED
-
3.0.0

@npmcli/git
ADDED
-
4.1.0

@npmcli/installed-package-contents
ADDED
-
2.0.2

@npmcli/map-workspaces
ADDED
-
3.0.4

@npmcli/metavuln-calculator
ADDED
-
5.0.1

@npmcli/name-from-folder
ADDED
-
2.0.0

@npmcli/node-gyp
ADDED
-
3.0.0

@npmcli/package-json
ADDED
-
4.0.1

@npmcli/promise-spawn
ADDED
-
6.0.2

@npmcli/query
ADDED
-
3.0.0

@npmcli/run-script
ADDED
-
6.0.2

@octokit/auth-token
ADDED
-
4.0.0

@octokit/core
ADDED
-
5.0.0

@octokit/endpoint
ADDED
-
9.0.0

@octokit/graphql
ADDED
-
7.0.1

@octokit/openapi-types
ADDED
-
18.0.0

@octokit/plugin-paginate-rest
ADDED
-
8.0.0

@octokit/plugin-retry
ADDED
-
6.0.0

@octokit/plugin-throttling
ADDED
-
7.0.0

@octokit/request-error
ADDED
-
5.0.0

@octokit/request
ADDED
-
8.1.1

@octokit/types
ADDED
-
11.1.0

@pnpm/config.env-replace
ADDED
-
1.1.0

@pnpm/network.ca-file
ADDED
-
1.0.2

@pnpm/npm-conf
ADDED
-
2.2.2

@polkadot/util
UPDATED
12.4.1
12.4.2

@polkadot/x-bigint
UPDATED
12.4.1
12.4.2

@polkadot/x-global
UPDATED
12.4.1
12.4.2

@polkadot/x-textdecoder
UPDATED
12.4.1
12.4.2

@polkadot/x-textencoder
UPDATED
12.4.1
12.4.2

@radix-ui/number
ADDED
-
1.0.1

@radix-ui/primitive
ADDED
-
1.0.1

@radix-ui/react-arrow
ADDED
-
1.0.3

@radix-ui/react-collection
ADDED
-
1.0.3

@radix-ui/react-compose-refs
ADDED
-
1.0.1

@radix-ui/react-context
ADDED
-
1.0.1

@radix-ui/react-direction
ADDED
-
1.0.1

@radix-ui/react-dismissable-layer
ADDED
-
1.0.4

@radix-ui/react-focus-guards
ADDED
-
1.0.1

@radix-ui/react-focus-scope
ADDED
-
1.0.3

@radix-ui/react-id
ADDED
-
1.0.1

@radix-ui/react-popper
ADDED
-
1.1.2

@radix-ui/react-portal
ADDED
-
1.0.3

@radix-ui/react-primitive
ADDED
-
1.0.3

@radix-ui/react-roving-focus
ADDED
-
1.0.4

@radix-ui/react-select
ADDED
-
1.2.2

@radix-ui/react-separator
ADDED
-
1.0.3

@radix-ui/react-slot
ADDED
-
1.0.2

@radix-ui/react-toggle-group
ADDED
-
1.0.4

@radix-ui/react-toggle
ADDED
-
1.0.3

@radix-ui/react-toolbar
ADDED
-
1.0.4

@radix-ui/react-use-callback-ref
ADDED
-
1.0.1

@radix-ui/react-use-controllable-state
ADDED
-
1.0.1

@radix-ui/react-use-escape-keydown
ADDED
-
1.0.3

@radix-ui/react-use-layout-effect
ADDED
-
1.0.1

@radix-ui/react-use-previous
ADDED
-
1.0.1

@radix-ui/react-use-rect
ADDED
-
1.0.1

@radix-ui/react-use-size
ADDED
-
1.0.1

@radix-ui/react-visually-hidden
ADDED
-
1.0.3

@radix-ui/rect
ADDED
-
1.0.1

@rollup/pluginutils
ADDED
-
5.0.3

@semantic-release/changelog
ADDED
-
6.0.3

@semantic-release/commit-analyzer
ADDED
-
10.0.1

@semantic-release/error
ADDED
-
4.0.0

@semantic-release/git
ADDED
-
10.0.1

@semantic-release/github
ADDED
-
9.0.4

@semantic-release/npm
ADDED
-
10.0.5

@semantic-release/release-notes-generator
ADDED
-
11.0.4

@sigstore/bundle
ADDED
-
1.1.0

@sigstore/protobuf-specs
ADDED
-
0.2.1

@sigstore/sign
ADDED
-
1.0.0

@sigstore/tuf
ADDED
-
1.0.3

@storybook/addon-actions
ADDED
-
7.3.2

@storybook/addon-backgrounds
ADDED
-
7.3.2

@storybook/addon-controls
ADDED
-
7.3.2

@storybook/addon-docs
ADDED
-
7.3.2

@storybook/addon-essentials
ADDED
-
7.3.2

@storybook/addon-highlight
ADDED
-
7.3.2

@storybook/addon-interactions
ADDED
-
7.3.2

@storybook/addon-links
ADDED
-
7.3.2

@storybook/addon-measure
ADDED
-
7.3.2

@storybook/addon-onboarding
ADDED
-
1.0.8

@storybook/addon-outline
ADDED
-
7.3.2

@storybook/addon-toolbars
ADDED
-
7.3.2

@storybook/addon-viewport
ADDED
-
7.3.2

@storybook/addons
ADDED
-
7.3.2

@storybook/blocks
ADDED
-
7.3.2

@storybook/builder-manager
ADDED
-
7.3.2

@storybook/builder-vite
ADDED
-
7.3.2

@storybook/channels
ADDED
-
7.3.2

@storybook/cli
ADDED
-
7.3.2

@storybook/client-logger
ADDED
-
7.3.2

@storybook/codemod
ADDED
-
7.3.2

@storybook/components
ADDED
-
7.3.2

@storybook/core-client
ADDED
-
7.3.2

@storybook/core-common
ADDED
-
7.3.2

@storybook/core-events
ADDED
-
7.3.2

@storybook/core-server
ADDED
-
7.3.2

@storybook/csf-plugin
ADDED
-
7.3.2

@storybook/csf-tools
ADDED
-
7.3.2

@storybook/csf
ADDED
-
0.1.1

@storybook/docs-mdx
ADDED
-
0.1.0

@storybook/docs-tools
ADDED
-
7.3.2

@storybook/global
ADDED
-
5.0.0

@storybook/icons
ADDED
-
1.1.6

@storybook/instrumenter
ADDED
-
7.3.2

@storybook/manager-api
ADDED
-
7.3.2

@storybook/manager
ADDED
-
7.3.2

@storybook/mdx2-csf
ADDED
-
1.1.0

@storybook/node-logger
ADDED
-
7.3.2

@storybook/postinstall
ADDED
-
7.3.2

@storybook/preview-api
ADDED
-
7.3.2

@storybook/preview
ADDED
-
7.3.2

@storybook/react-dom-shim
ADDED
-
7.3.2

@storybook/react-vite
ADDED
-
7.3.2

@storybook/react
ADDED
-
7.3.2

@storybook/router
ADDED
-
7.3.2

@storybook/telemetry
ADDED
-
7.3.2

@storybook/testing-library
ADDED
-
0.2.0

@storybook/theming
ADDED
-
7.3.2

@storybook/types
ADDED
-
7.3.2

@testing-library/jest-dom
UPDATED
6.0.1
6.1.2

@testing-library/user-event
ADDED
-
14.4.3

@tufjs/canonical-json
ADDED
-
1.0.0

@tufjs/models
ADDED
-
1.0.4

@types/body-parser
ADDED
-
1.19.2

@types/connect
ADDED
-
3.4.35

@types/cross-spawn
ADDED
-
6.0.2

@types/detect-port
ADDED
-
1.3.3

@types/doctrine
ADDED
-
0.0.3

@types/ejs
ADDED
-
3.1.2

@types/emscripten
ADDED
-
1.39.7

@types/escodegen
ADDED
-
0.0.6

@types/estree
ADDED
-
1.0.1

@types/express-serve-static-core
ADDED
-
4.17.36

@types/express
ADDED
-
4.17.17

@types/find-cache-dir
ADDED
-
3.2.1

@types/glob
ADDED
-
7.2.0

@types/http-errors
ADDED
-
2.0.1

@types/jest
UPDATED
29.5.3
29.5.4

@types/lodash
ADDED
-
4.14.197

@types/mdx
ADDED
-
2.0.7

@types/mime-types
ADDED
-
2.1.1

@types/mime
ADDED
-
1.3.2

@types/minimatch
ADDED
-
5.1.2

@types/minimist
ADDED
-
1.2.2

@types/node-fetch
ADDED
-
2.6.4

@types/node
UPDATED
18.17.6
18.17.11

@types/normalize-package-data
ADDED
-
2.4.1

@types/pretty-hrtime
ADDED
-
1.0.1

@types/qs
ADDED
-
6.9.7

@types/range-parser
ADDED
-
1.2.4

@types/react
UPDATED
18.2.20
18.2.21

@types/send
ADDED
-
0.17.1

@types/serve-static
ADDED
-
1.15.2

@types/unist
ADDED
-
2.0.7

@yarnpkg/esbuild-plugin-pnp
ADDED
-
3.0.0-rc.15

@yarnpkg/fslib
ADDED
-
2.10.3

@yarnpkg/libzip
ADDED
-
2.3.0

abbrev
UPDATED
1.1.1
2.0.0

abort-controller
ADDED
-
3.0.0

accepts
ADDED
-
1.3.8

address
ADDED
-
1.2.2

agent-base
UPDATED
6.0.2
7.1.0

aggregate-error
UPDATED
3.1.0
4.0.1

ansicolors
ADDED
-
0.3.2

app-root-dir
ADDED
-
1.0.2

archy
ADDED
-
1.0.0

are-we-there-yet
UPDATED
3.0.1
4.0.1

argv-formatter
ADDED
-
1.0.0

aria-hidden
ADDED
-
1.2.3

array-flatten
ADDED
-
1.1.1

array-ify
ADDED
-
1.0.0

arrify
ADDED
-
1.0.1

assert
ADDED
-
2.0.0

ast-types
ADDED
-
0.16.1

async-limiter
ADDED
-
1.0.1

async
ADDED
-
3.2.4

babel-core
ADDED
-
7.0.0-bridge.0

babel-jest
UPDATED
29.6.3
29.6.4

base64-js
ADDED
-
1.5.1

before-after-hook
ADDED
-
2.2.3

better-opn
ADDED
-
3.0.2

bin-links
ADDED
-
4.0.2

binary-extensions
ADDED
-
2.2.0

bl
ADDED
-
4.1.0

body-parser
ADDED
-
1.20.1

bottleneck
ADDED
-
2.19.5

browser-assert
ADDED
-
1.2.1

browserify-zlib
ADDED
-
0.1.4

buffer-crc32
ADDED
-
0.2.13

buffer
ADDED
-
6.0.3

builtins
ADDED
-
5.0.1

bytes
ADDED
-
3.1.2

c8
ADDED
-
7.14.0

camelcase-keys
ADDED
-
6.2.2

cardinal
ADDED
-
2.1.1

chokidar
ADDED
-
3.5.3

cidr-regex
ADDED
-
3.1.1

clean-stack
UPDATED
2.2.0
4.2.0

cli-columns
ADDED
-
4.0.0

cli-cursor
ADDED
-
3.1.0

cli-spinners
ADDED
-
2.9.0

cli-table3
ADDED
-
0.6.3

clone-deep
ADDED
-
4.0.1

clone
ADDED
-
1.0.4

cmd-shim
ADDED
-
6.0.1

colorette
ADDED
-
2.0.20

columnify
ADDED
-
1.6.0

commander
ADDED
-
6.2.1

common-ancestor-path
ADDED
-
1.0.1

commondir
ADDED
-
1.0.1

compare-func
ADDED
-
2.0.0

compressible
ADDED
-
2.0.18

compression
ADDED
-
1.7.4

concat-stream
ADDED
-
1.6.2

config-chain
ADDED
-
1.1.13

content-disposition
ADDED
-
0.5.4

content-type
ADDED
-
1.0.5

conventional-changelog-angular
ADDED
-
6.0.0

conventional-changelog-writer
ADDED
-
6.0.1

conventional-commits-filter
ADDED
-
3.0.0

conventional-commits-parser
ADDED
-
4.0.0

cookie-signature
ADDED
-
1.0.6

cookie
ADDED
-
0.5.0

core-util-is
ADDED
-
1.0.3

cosmiconfig
UPDATED
7.1.0
8.2.0

crypto-random-string
ADDED
-
4.0.0

cssesc
ADDED
-
3.0.0

dateformat
ADDED
-
3.0.3

decamelize-keys
ADDED
-
1.1.1

decamelize
ADDED
-
1.2.0

deep-extend
ADDED
-
0.6.0

defaults
ADDED
-
1.0.4

defu
ADDED
-
6.1.2

del
ADDED
-
6.1.1

depd
ADDED
-
2.0.0

deprecation
ADDED
-
2.3.1

destroy
ADDED
-
1.2.0

detect-indent
ADDED
-
6.1.0

detect-node-es
ADDED
-
1.1.0

detect-package-manager
ADDED
-
2.0.1

detect-port
ADDED
-
1.5.1

diff-sequences
UPDATED
29.4.3
29.6.3

diff
ADDED
-
5.1.0

dot-prop
ADDED
-
5.3.0

dotenv-expand
ADDED
-
10.0.0

dotenv
ADDED
-
16.3.1

duplexer2
ADDED
-
0.1.4

duplexify
ADDED
-
3.7.1

ee-first
ADDED
-
1.1.1

ejs
ADDED
-
3.1.9

encodeurl
ADDED
-
1.0.2

end-of-stream
ADDED
-
1.4.4

env-ci
ADDED
-
9.1.1

envinfo
ADDED
-
7.10.0

es-module-lexer
ADDED
-
0.9.3

es6-object-assign
ADDED
-
1.1.0

esbuild-plugin-alias
ADDED
-
0.2.1

esbuild-register
ADDED
-
3.4.2

escape-html
ADDED
-
1.0.3

escape-string-regexp
UPDATED
4.0.0
5.0.0

eslint-plugin-storybook
ADDED
-
0.6.13

estree-to-babel
ADDED
-
3.2.1

estree-walker
ADDED
-
2.0.2

etag
ADDED
-
1.8.1

event-target-shim
ADDED
-
5.0.1

events
ADDED
-
3.3.0

execa
UPDATED
7.2.0
8.0.1

expect
UPDATED
29.6.2
29.6.4

express
ADDED
-
4.18.2

extend
ADDED
-
3.0.2

extract-zip
ADDED
-
1.7.0

fastest-levenshtein
ADDED
-
1.0.16

fd-slicer
ADDED
-
1.1.0

fetch-retry
ADDED
-
5.0.6

figures
ADDED
-
5.0.0

file-system-cache
ADDED
-
2.3.0

filelist
ADDED
-
1.0.4

finalhandler
ADDED
-
1.2.0

find-cache-dir
ADDED
-
3.3.2

find-up
UPDATED
5.0.0
6.3.0

find-versions
ADDED
-
5.1.0

flow-parser
ADDED
-
0.215.1

forwarded
ADDED
-
0.2.0

fresh
ADDED
-
0.5.2

from2
ADDED
-
2.3.0

fs-constants
ADDED
-
1.0.0

fs-extra
ADDED
-
11.1.1

gauge
UPDATED
4.0.4
5.0.1

get-nonce
ADDED
-
1.0.1

get-npm-tarball-url
ADDED
-
2.0.3

get-port
ADDED
-
5.1.1

get-stream
UPDATED
6.0.1
8.0.1

giget
ADDED
-
1.1.2

git-log-parser
ADDED
-
1.2.0

github-slugger
ADDED
-
1.5.0

glob-promise
ADDED
-
4.2.2

glob-to-regexp
ADDED
-
0.4.1

globby
UPDATED
11.1.0
13.2.2

gunzip-maybe
ADDED
-
1.4.2

handlebars
ADDED
-
4.7.8

hard-rejection
ADDED
-
2.1.0

hook-std
ADDED
-
3.0.0

hosted-git-info
ADDED
-
7.0.0

html-tags
ADDED
-
3.3.1

http-errors
ADDED
-
2.0.0

http-proxy-agent
UPDATED
5.0.0
7.0.0

https-proxy-agent
UPDATED
5.0.1
7.0.1

human-signals
UPDATED
4.3.1
5.0.0

ieee754
ADDED
-
1.2.1

ignore-walk
ADDED
-
6.0.3

import-from
ADDED
-
4.0.0

indent-string
UPDATED
4.0.0
5.0.0

ini
ADDED
-
4.1.1

init-package-json
ADDED
-
5.0.0

into-stream
ADDED
-
7.0.0

invariant
ADDED
-
2.2.4

ip-regex
ADDED
-
4.3.0

ipaddr.js
ADDED
-
1.9.1

is-absolute-url
ADDED
-
3.0.3

is-binary-path
ADDED
-
2.1.0

is-cidr
ADDED
-
4.0.2

is-deflate
ADDED
-
1.0.0

is-gzip
ADDED
-
1.0.0

is-interactive
ADDED
-
1.0.0

is-nan
ADDED
-
1.3.2

is-obj
ADDED
-
2.0.0

is-path-cwd
ADDED
-
2.2.0

is-plain-obj
ADDED
-
1.1.0

is-plain-object
ADDED
-
5.0.0

is-text-path
ADDED
-
1.0.1

is-unicode-supported
ADDED
-
1.3.0

isobject
ADDED
-
3.0.1

issue-parser
ADDED
-
6.0.0

istanbul-lib-instrument
UPDATED
5.2.1
6.0.0

jake
ADDED
-
10.8.7

java-properties
ADDED
-
1.0.2

jest-changed-files
UPDATED
29.5.0
29.6.3

jest-circus
UPDATED
29.6.2
29.6.4

jest-cli
UPDATED
29.6.2
29.6.4

jest-config
UPDATED
29.6.2
29.6.4

jest-diff
UPDATED
29.6.2
29.6.4

jest-docblock
UPDATED
29.4.3
29.6.3

jest-each
UPDATED
29.6.2
29.6.3

jest-environment-jsdom
UPDATED
29.6.2
29.6.4

jest-environment-node
UPDATED
29.6.2
29.6.4

jest-get-type
UPDATED
29.4.3
29.6.3

jest-haste-map
UPDATED
29.6.3
29.6.4

jest-leak-detector
UPDATED
29.6.2
29.6.3

jest-matcher-utils
UPDATED
29.6.2
29.6.4

jest-message-util
UPDATED
29.6.2
29.6.3

jest-mock
UPDATED
29.6.2
29.6.3

jest-resolve-dependencies
UPDATED
29.6.2
29.6.4

jest-resolve
UPDATED
29.6.2
29.6.4

jest-runner
UPDATED
29.6.2
29.6.4

jest-runtime
UPDATED
29.6.2
29.6.4

jest-snapshot
UPDATED
29.6.2
29.6.4

jest-validate
UPDATED
29.6.2
29.6.3

jest-watcher
UPDATED
29.6.2
29.6.4

jest-worker
UPDATED
29.6.3
29.6.4

jest
UPDATED
29.6.2
29.6.4

jscodeshift
ADDED
-
0.14.0

json-parse-better-errors
ADDED
-
1.0.2

json-parse-even-better-errors
UPDATED
2.3.1
3.0.0

json-stringify-nice
ADDED
-
1.1.4

jsonfile
ADDED
-
6.1.0

jsonparse
ADDED
-
1.3.1

JSONStream
ADDED
-
1.3.5

just-diff-apply
ADDED
-
5.5.0

just-diff
ADDED
-
6.0.2

kind-of
ADDED
-
6.0.3

lazy-universal-dotenv
ADDED
-
4.0.0

libnpmaccess
ADDED
-
7.0.2

libnpmdiff
ADDED
-
5.0.19

libnpmexec
ADDED
-
6.0.3

libnpmfund
ADDED
-
4.0.19

libnpmhook
ADDED
-
9.0.3

libnpmorg
ADDED
-
5.0.4

libnpmpack
ADDED
-
5.0.19

libnpmpublish
ADDED
-
7.5.0

libnpmsearch
ADDED
-
6.0.2

libnpmteam
ADDED
-
5.0.3

libnpmversion
ADDED
-
4.0.2

lines-and-columns
UPDATED
1.2.4
2.0.3

load-json-file
ADDED
-
4.0.0

locate-path
UPDATED
6.0.0
7.2.0

lodash-es
ADDED
-
4.17.21

lodash.capitalize
ADDED
-
4.2.1

lodash.escaperegexp
ADDED
-
4.1.2

lodash.ismatch
ADDED
-
4.4.0

lodash.isplainobject
ADDED
-
4.0.6

lodash.isstring
ADDED
-
4.0.1

lodash.uniqby
ADDED
-
4.7.0

log-symbols
ADDED
-
4.1.0

magic-string
ADDED
-
0.30.3

map-obj
ADDED
-
4.3.0

map-or-similar
ADDED
-
1.5.0

markdown-to-jsx
ADDED
-
7.3.2

marked-terminal
ADDED
-
5.2.0

marked
ADDED
-
5.1.2

mdast-util-definitions
ADDED
-
4.0.0

mdast-util-to-string
ADDED
-
1.1.0

media-typer
ADDED
-
0.3.0

memoizerific
ADDED
-
1.11.3

meow
ADDED
-
8.1.2

merge-descriptors
ADDED
-
1.0.1

methods
ADDED
-
1.1.2

mime
ADDED
-
3.0.0

minimist-options
ADDED
-
4.1.0

minipass-json-stream
ADDED
-
1.0.1

mkdirp-classic
ADDED
-
0.5.3

modify-values
ADDED
-
1.0.1

mri
ADDED
-
1.2.0

ms
UPDATED
2.1.2
2.1.3

mute-stream
ADDED
-
1.0.0

neo-async
ADDED
-
2.6.2

nerf-dart
ADDED
-
1.0.0

node-dir
ADDED
-
0.1.17

node-emoji
ADDED
-
1.11.0

node-fetch-native
ADDED
-
1.4.0

nopt
UPDATED
6.0.0
7.2.0

normalize-package-data
ADDED
-
6.0.0

normalize-url
ADDED
-
8.0.0

npm-audit-report
ADDED
-
5.0.0

npm-bundled
ADDED
-
3.0.0

npm-install-checks
ADDED
-
6.2.0

npm-normalize-package-bin
ADDED
-
3.0.1

npm-package-arg
ADDED
-
10.1.0

npm-packlist
ADDED
-
7.0.4

npm-pick-manifest
ADDED
-
8.0.2

npm-profile
ADDED
-
7.0.1

npm-registry-fetch
ADDED
-
14.0.5

npm-user-validate
ADDED
-
2.0.0

npm
ADDED
-
9.8.1

npmlog
UPDATED
6.0.2
7.0.1

on-finished
ADDED
-
2.4.1

on-headers
ADDED
-
1.0.2

ora
ADDED
-
5.4.1

p-each-series
ADDED
-
3.0.0

p-filter
ADDED
-
3.0.0

p-is-promise
ADDED
-
3.0.0

p-limit
UPDATED
3.1.0
4.0.0

p-locate
UPDATED
5.0.0
6.0.0

p-map
UPDATED
4.0.0
5.5.0

p-reduce
ADDED
-
3.0.0

pacote
ADDED
-
15.2.0

parse-conflict-json
ADDED
-
3.0.1

parse-json
UPDATED
5.2.0
7.0.0

parseurl
ADDED
-
1.3.3

path-exists
UPDATED
4.0.0
5.0.0

path-to-regexp
ADDED
-
0.1.7

pathe
ADDED
-
1.1.1

peek-stream
ADDED
-
1.1.3

pend
ADDED
-
1.2.0

pify
ADDED
-
4.0.1

pkg-conf
ADDED
-
2.1.0

pkg-dir
UPDATED
4.2.0
5.0.0

polished
ADDED
-
4.2.2

postcss-selector-parser
ADDED
-
6.0.13

pretty-format
UPDATED
29.6.2
29.6.3

pretty-hrtime
ADDED
-
1.0.3

proc-log
ADDED
-
3.0.0

process-nextick-args
ADDED
-
2.0.1

process
ADDED
-
0.11.10

progress
ADDED
-
2.0.3

promise-all-reject-late
ADDED
-
1.0.1

promise-call-limit
ADDED
-
1.0.2

promise-inflight
ADDED
-
1.0.1

promzard
ADDED
-
1.0.0

proto-list
ADDED
-
1.2.4

proxy-addr
ADDED
-
2.0.7

proxy-from-env
ADDED
-
1.1.0

pump
ADDED
-
3.0.0

pumpify
ADDED
-
1.5.1

puppeteer-core
ADDED
-
2.1.1

qrcode-terminal
ADDED
-
0.12.0

qs
ADDED
-
6.11.0

quick-lru
ADDED
-
4.0.1

ramda
ADDED
-
0.29.0

range-parser
ADDED
-
1.2.1

raw-body
ADDED
-
2.5.1

rc
ADDED
-
1.2.8

react-colorful
ADDED
-
5.6.1

react-confetti
ADDED
-
6.1.0

react-docgen-typescript
ADDED
-
2.2.2

react-docgen
ADDED
-
6.0.0-alpha.3

react-dom
ADDED
-
18.2.0

react-element-to-jsx-string
ADDED
-
15.0.0

react-inspector
ADDED
-
6.0.2

react-remove-scroll-bar
ADDED
-
2.3.4

react-remove-scroll
ADDED
-
2.5.5

react-style-singleton
ADDED
-
2.2.1

read-cmd-shim
ADDED
-
4.0.0

read-package-json-fast
ADDED
-
3.0.2

read-package-json
ADDED
-
6.0.4

read-pkg-up
ADDED
-
10.1.0

read-pkg
ADDED
-
8.1.0

read
ADDED
-
2.1.0

readable-stream
UPDATED
3.6.2
4.4.2

readdirp
ADDED
-
3.6.0

recast
ADDED
-
0.23.4

redeyed
ADDED
-
2.1.1

registry-auth-token
ADDED
-
5.0.2

remark-external-links
ADDED
-
8.0.0

remark-slug
ADDED
-
6.1.0

requireindex
ADDED
-
1.2.0

restore-cursor
ADDED
-
3.1.0

semantic-release
ADDED
-
21.1.1

semver-diff
ADDED
-
4.0.0

semver-regex
ADDED
-
4.0.5

send
ADDED
-
0.18.0

serve-favicon
ADDED
-
2.5.0

serve-static
ADDED
-
1.15.0

setprototypeof
ADDED
-
1.2.0

shallow-clone
ADDED
-
3.0.1

signale
ADDED
-
1.4.0

sigstore
ADDED
-
1.9.0

simple-update-notifier
ADDED
-
2.0.0

source-map-support
UPDATED
0.5.13
0.5.21

space-separated-tokens
ADDED
-
1.1.5

spawn-error-forwarder
ADDED
-
1.0.0

spdx-correct
ADDED
-
3.2.0

spdx-exceptions
ADDED
-
2.3.0

spdx-expression-parse
ADDED
-
3.0.1

spdx-license-ids
ADDED
-
3.0.13

split
ADDED
-
1.0.1

split2
ADDED
-
3.2.2

statuses
ADDED
-
2.0.1

store2
ADDED
-
2.14.2

storybook
ADDED
-
7.3.2

stream-combiner2
ADDED
-
1.1.1

stream-shift
ADDED
-
1.0.1

supports-color
UPDATED
8.1.1
9.4.0

supports-hyperlinks
ADDED
-
2.3.0

synchronous-promise
ADDED
-
2.0.17

tar-fs
ADDED
-
2.1.1

tar-stream
ADDED
-
2.2.0

telejson
ADDED
-
7.2.0

temp-dir
ADDED
-
3.0.0

temp
ADDED
-
0.8.4

tempy
ADDED
-
3.1.0

text-extensions
ADDED
-
1.9.0

through
ADDED
-
2.3.8

through2
ADDED
-
2.0.5

tiny-invariant
ADDED
-
1.3.1

tiny-relative-date
ADDED
-
1.3.0

tocbot
ADDED
-
4.21.1

toidentifier
ADDED
-
1.0.1

traverse
ADDED
-
0.6.7

treeverse
ADDED
-
3.0.0

trim-newlines
ADDED
-
3.0.1

ts-dedent
ADDED
-
2.2.0

tuf-js
ADDED
-
1.1.7

tween-functions
ADDED
-
1.2.0

type-fest
UPDATED
3.13.1
4.2.0

type-is
ADDED
-
1.6.18

typedarray
ADDED
-
0.0.6

typescript
UPDATED
5.1.6
5.2.2

uglify-js
ADDED
-
3.17.4

unique-string
ADDED
-
3.0.0

unist-util-is
ADDED
-
4.1.0

unist-util-visit-parents
ADDED
-
3.1.1

unist-util-visit
ADDED
-
2.0.3

universal-user-agent
ADDED
-
6.0.0

universalify
UPDATED
0.2.0
2.0.0

unpipe
ADDED
-
1.0.0

unplugin
ADDED
-
1.4.0

url-join
ADDED
-
5.0.0

use-callback-ref
ADDED
-
1.3.0

use-resize-observer
ADDED
-
9.1.0

use-sidecar
ADDED
-
1.1.2

util
ADDED
-
0.12.5

utils-merge
ADDED
-
1.0.1

uuid
ADDED
-
9.0.0

validate-npm-package-license
ADDED
-
3.0.4

validate-npm-package-name
ADDED
-
5.0.0

vary
ADDED
-
1.1.2

walk-up-path
ADDED
-
3.0.1

watchpack
ADDED
-
2.4.0

wcwidth
ADDED
-
1.0.1

webpack-sources
ADDED
-
3.2.3

webpack-virtual-modules
ADDED
-
0.5.0

which
UPDATED
2.0.2
3.0.1

wordwrap
ADDED
-
1.0.0

write-file-atomic
UPDATED
4.0.2
5.0.1

xtend
ADDED
-
4.0.2

yauzl
ADDED
-
2.10.0

yocto-queue
UPDATED
0.1.0
1.0.0


Document all fields

Document all the fields in the proto file.

Makes sense, thanks!
I accepted the suggestion in every comment. A note in the header is too easily overlooked.


Loading state_dict fails (model trained on linux and copied to windows)

Version
pyabsa==2.3.1
torch==1.13.0
transformers==4.29.0
Describe the bug
I used to load my custom state_dict from my windows system and the loading procedure worked.
However, I am training now on a linux server for resource reasons. I trained a sample model and copied the whole folder containing the model files to my windows system (.args, config, .state_dict, .tokenizer).
Now I tried to load that model in the same way as always but I get errors: (refer to Screenshot for details).
RuntimeError: Error(s) in loading state_dict for FAST_LCF_ATEPC:
Missing key(s) in state_dict: "bert4global.embeddings.position_ids".
if not hasattr(ATEPCModelList, self.model.class.name):
raise KeyError(
"The checkpoint you are loading is not from any ATEPC model."
)
Code To Reproduce
aspect_extractor = ATEPC.AspectExtractor('fast_lcf_atepc_custom_dataset_cdw_apcacc_75.0_apcf1_74.31_atef1_40.45',
auto_device=True,  # False means load model on CPU
cal_perplexity=True,
)
Expected behavior
I expect the program to load my custom checkpoint/saved_state_dict.
Screenshots

I now have an idea why it does not work. I had a different version of tranformers on linux where i trained (4.35.2), in contrast in windows i have transformers==4.29 which might be the problem when loading the state_dict.


Fix link from Issue #846

I believe this was done correctly.  Only swapped out the old link for the updated link going to the correct spot on Exercism.io explained concepts.

Great catch! It would be great to have a test that checks the project for dead links in the future 🤔


Update use event dispatcher so as not to break TraceableEventDispatcher

When a dispatcher which extends DomainEventDispatcherInterface and it pass into Symfony\Component\EventDispatcher\Debug\TraceableEventDispatcher, an error is returned because the 1st argument is Symfony\Component\EventDispatcher\EventDispatcherInterface

Hello @dimitriseguin1 and thanks for your first public contribution \o/.
I think this change will not change anything considering EventDispatcherInterface actually extends ContractsEventDispatcherInterface... WDYT?
Can you give more insights about how you find out this error and how/why it fixes?

I have a class which implements DomainEventDispatcherInterface which extends Symfony\Contracts\EventDispatcher\EventDispatcherInterface.
When this class pass into Symfony\Component\EventDispatcher\Debug\TraceableEventDispatcher, I have an error because
TraceableEventDispatcher wait a EventDispatcherInterface and my class extends EventDispatcherInterface from Contracts

@dimitriseguin1 I'm 👍 with your change. But tests are broken. 🤔 Can you fix them?


fix: pass willRecomputeLayouts to useClientRect call for overlayNodeRect

Thanks for the additional investigation done for #408 @clauderic. It looks like removing willRecomputeLayouts from the useClientRect call of overlayNodeRect rebreaks our case, however. Reading over the methodology/cause of the changes you made, I'm not sure why this argument was removed, but adding it back in seems to fix things. It seems to me that recomputing the layout rect of the measurable child is required as the overlay moves.

Nuts, E2E tests are broken in CI and working locally again. I assume you've got some insight about what's going on here.

Nuts, E2E tests are broken in CI and working locally again. I assume you've got some insight about what's going on here.

Yeah, go try this story which illustrates the problem http://localhost:6006/iframe.html?id=presets-sortable-multiple-containers--many-items&args=&viewMode=story
When we use the DragOverlay as the source of the collision rect, everything works fine when you measure it for the first time, before it's moved using transform.
Subsequent measurements are affected by the transform that is applied on the DragOverlay, such that the top, left, right and bottom properties that we get back already include the transform that we're applied, which represents the net movement of the active sensor.
To fix this, I think the easiest way would be to subtract the current transform on subsequent measurements of the DragOverlay rect.

It's a rather involved fix so I'll open a separate PR


macOS Terminal is in Applications > Utilities

Granted, most people likely to be using Terminal can probably find an application on their Mac.

For simplicity I think we're going to focus on using VS Code's built in terminal so that everyone has the same work path. going to remove that from the readme.


The autocomplete options are not loaded. LoadOptions function is not called with user input

Latest version

[X] I have tested the latest version

Current behavior
loadOptions does not get called with user search input
Expected behavior
loadOptions function to be called with user search input
Steps to reproduce
Reproduced in this sandbox: https://codesandbox.io/p/sandbox/897stg
Software Version

Storybook:
Rocket-UI:
Material UI:
React:
NPM/YARN:

What browsers are you seeing the problem on?
No response

Not a bug. This is the intended use. You are looking for filterOptions


Remove --experimental flag from XML-attributes BBE description

Purpose
$subject.
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #18942 into next-release will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           next-release   #18942   +/-   ##
=============================================
  Coverage         20.53%   20.53%
=============================================
  Files                52       52
  Lines              1383     1383
  Branches            216      216
=============================================
  Hits                284      284
  Misses             1086     1086
  Partials             13       13

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 aba78de...414fe11. Read the comment docs.


Allow passing keyword arguments to the jinja2 Environment

I was working on a project and needed to tweak the jinja2 Environment settings to better control whitespace output in my templates. This change allows passing a custom dictionary as kwargs when constructing the Environment. Since you're already using the filters, extensions, and loader kwargs, I just pop them from the dict before passing them to the Environment, so this should be 100% backwards compatible and completely optional.
Example usage:
site = make_site(
    outpath="dist",
    env_kwargs={"trim_blocks": True, "lstrip_blocks": True}  # Extra kwargs passed to the Environment
)

Left some comments on how I think we could write this better, but this is a really useful change. Thank you!

Hey, just remembered that I had this laying around. I pulled the latest master, and it looks like it was merged in the end? Hahaha, neat.

Yep, made the changes myself and amended them into your commit so you get the credit. :)


Logins do not work when using special characters

Describe the bug
If I log into a website whose password contains special characters, the login fails
To Reproduce
Steps to reproduce the behavior:

Select a website that requires a login. Make sure the password has characters like '_' or '@' in it
2.Enter your username and password
Go to another browser (like Chrome or Firefox), go to the same URL and enter the username and password

Expected behavior
You should be logged in to the site (in Zen) as well as in the (for example) Firefox browser
Actual Behavior
In Zen: You get a login failure -- even if you put in the correct password
In Firefox: You get logged in

this is the docs repo here is the browser https://github.com/zen-browser/desktop repo

This is not the docs request. This is a bug report. Please reread it.

Here I am talking about how the Zen browser fails to log in to sites that have passwords with special characters. This is a serious bug, not a request for docs.

There is nothing in the docs repo that talks about how to deal with this bug.

This is not the docs request. This is a bug report. Please reread it.

Here I am talking about how the Zen browser fails to log in to sites that have passwords with special characters. This is a serious bug, not a request for docs.
2. There is nothing in the docs repo that talks about how to deal with this _bug_.

Didnt even know this is a bug,
i sent u the Desktop repo where issues related to the browser are,
this repo is just if somting is rithen wrong in the docs or any info that should be aded.


Allow Multiple Orders, Execution Reports, Order Cancel and Order Reject in a single sessionID

In the FIX protocol, multiple New Order Single (NOS) messages can be sent within a single session, and each NOS message corresponds to a single order.
The FIX protocol is designed to allow for multiple messages to be sent and received within a single session between two trading partners. This means that a trader can send multiple NOS messages to a broker or an exchange within a single session to place multiple orders.
Each NOS message contains information about a single order, such as the symbol, side (buy or sell), quantity, and price. Therefore, a single NOS message corresponds to a single order. If a trader wants to place multiple orders, they would need to send multiple NOS messages within a single session.
It's worth noting that some trading systems may have additional rules or limitations on how many orders can be placed within a single session, so it's important to check the specific rules and limitations of the trading system being used

what field uniquely identifies each order?
In the FIX protocol, the ClOrdID (Client Order ID) field uniquely identifies each order. The ClOrdID is a mandatory field in the New Order Single (NOS) message, which is used to submit a new order to a trading system.
The ClOrdID field is a string of up to 20 characters that is generated by the client (such as a trader or trading algorithm) and must be unique for each order submitted by that client. The trading system will use the ClOrdID to track the order and communicate status updates and execution reports back to the client.
It's important to note that the ClOrdID only needs to be unique for each client, not across all orders on the trading system. This means that two different clients could potentially use the same ClOrdID for their orders, as long as each client's orders have unique ClOrdIDs.

Also, reset the header and the trailer since sending time, checksum, bodylenth, msgType  will change  when gotten from the sessionID

check for allowing  any of the parties to initiate the order

can The ClOrdID and OrderID be the same?

can The ClOrdID and OrderID be the same?

Yes, the ClOrdID and orderID can be the same. The ClOrdID is a unique identifier for the order that is generated by the client, while the orderID is a unique identifier for the order that is generated by the broker. In some cases, the client and broker may choose to use the same identifier for both the ClOrdID and orderID. This can be helpful for tracking the progress of an order and for getting information about the execution of the order.
However, it is important to note that the ClOrdID and orderID are not always the same. In some cases, the client and broker may choose to use different identifiers for the ClOrdID and orderID. This can be done for a variety of reasons, such as to improve tracking or to comply with regulatory requirements.


Eager Loding/Relationship Caching

Is your feature request related to a problem? Please describe.
The raltionships are not cached by the ORM, which leads to unecessary DB access. Also not having a eager loading system can cause major performance issues.
Describe the solution you'd like
Add in the generated model file a way to eager load and use the cached relationship (this second part can be controlled by the model.json file for each relationship)
Describe alternatives you've considered
I was think something similar to Eloquent from Laravel:
$user = User::query()
->with('posts', function(Builder $query) {
    $query->with('comments')
        ->with('banner', function(Builder $query) {
            $query->with('metadata');
        });
})
->get();

This will run 5 queries, one for users, one for posts, one for the comments, one for the banner and one for metadata.
But since I can't think a way to load the relationship only using the name as a string a thought in generate some static methods in the model class for each relationship so it can be eager loaded.
Instead of passing a Query Builder to the anonymous function
DbClientPtr client = drogon::app().getDbClient();
Mapper<Users> mp(client);
std::vector<Users> users = mp.findAll()
Users::loadPosts(users, [](std::vector<Posts>& posts) {
    Posts::loadComments(posts);
    Posts::loadBanner(posts, [](std::vector<Banners>& banners) {
        Banners::loadMetadata(banners);
    })
});

The type of the static function would be void(std::vector<T>& model) (It can't be const std::vector& because the entities inside the vector need to be modified).
As you can see the callback is optional, because maybe we don't want to load nothing after that relationship.
The eager loading functions only accepts a vector because N+1 problems don't occur when you have a single model and want to retrive it's relationship.
The generated sql for the eager loading would be something like this:
select * from posts where user_id IN ($1, $2, ...);
select * from comments where post_id IN ($1, $2, ...);
select * from banners where post_id IN ($1, $2, ...);
select * from meta_data where banner_id IN ($1, $2, ...);

After this I would loop over the relationships and distribute then for the correct parent.
Everything would be stored in a new member variable inside each model (std::shared_ptr<T>). For example:

Users model would have std::vector<Posts>
Posts model would have std::vector<Comments>, Banner and User (inverse relationship);
Banners model would have Metadata
Metadata model would have Banner (inverse relationship)

OBS: The inverse relationships would not be loaded since would be a nightmare to manage the references
Now for retrive this relationships would be something like:
user.getPosts(client,
    [](std::vector<Posts>& posts) {},
    [](const DrogonDbException& e) {}); //this would still run the query and after it sets the posts member inside user
//It's passed by reference because it's a reference to the posts member inside user

std::vector<Posts>& posts = user.getPosts(); //this would only retrive from the member inside user

Not determined

For optional relationships I was thinking in using std::optional<T> as a return type, but this can also be and exception (because std::optional is not widly used in the framework). If this is the case the optionality of the relationship would be configured in the model.json (this is more a problem for has one/belongs to relationships, because for has many we can just return a empty vector).
I was also thinking about change the sql in the relationship functions to use the Mapper<T> functions, opnions are also welcome.
I'm still thinking about many to many relationships
Having a std::future<T> as a way to retrive the relationship, similar to:

Mapper<Users> mp(client);
std::future<Users> user = mp.findFutureByPrimaryKey(id);

It would be:
Mapper<Users> mp(client);
Users user = mp.findByPrimaryKey(id);
std::future<std::vector<Posts>&> posts = user.getFuturePosts(client);
//this case would be similar to the new way of retriving and updating the cache but it would result in more redable code
//and would throw an exception if something goes wrong

@an-tao as I said in https://github.com/drogonframework/drogon/issues/1023#issuecomment-924002889. What do you think ?

@Gab-Menezes Thanks so much for your suggestion, this is a big requirement of ORM, We should fully discuss before we start to implement it.
your approch looks good to me, now I have some questions about it:

The nesting of callbacks increases the complexity of programming. For example, how do I know that all queries have been executed? In your example, It is uncertain which of  loadBanners and loadComents will be executed first. (I think we could add some coroutine interfaces to resolve this).
How about adding sub-relationship loading to the eager loading method, (for example automatically load posts in the Users::loadPosts method), and add a enableEagerLoading interface to the Map tempalte.

@rbugajewski @marty1885 @hwc0919 What do u think about this subject?

I use the ORM mostly for very simple queries so I don’t have any particular opinion about this subject.

@an-tao I was testing somethings and I think I found a bug. As I suggested we could change the SQL to the Mapper<T> in the relationships functions. But when I do:
DbClientPtr client = drogon::app().getDbClient();
Mapper<Posts> mp(client);
auto posts = mp.findBy(Criteria(Posts::Cols::_user_id, CompareOperator::EQ, 1));

The program crashes:

Here is the file and line
But when I change from int to string everything works
DbClientPtr client = drogon::app().getDbClient();
Mapper<Posts> mp(client);
auto posts = mp.findBy(Criteria(Posts::Cols::_user_id, CompareOperator::EQ, "1"));

In the wiki we have a example exactly like that.
Do you know the reason ?

what's the type of the user_id column of the Posts table?

Metadata:

Member variable:

DB table:

looks like a bug. I'll figure it out.

So I was thinking and I reached some conclusions (this is a early draft so don't bother with well written things):

As you can see I changed the void getPosts (default generated by framework) to use Mapper<Posts> instead a raw SQL. (That's the reason I asked about the findBy method)

The asynchronous methods void getPosts and std::future<std::vector<Posts>> getFuturePosts have odd behaviour. Since we don't know wen they will finish the execution the user variable that called it may be  undefined (pop out of the stack) (especially for the callback overload). So we can set the posts member inside the user that called it.
I made a synchronou getPosts (std::vector& getPosts(const DbClientPtr& clientPtr)) function, that set the cache inside the user model (this one can alse be used to reload the cache).
And the the cache version only gets from the cache if nothing is setted throws an exception.

I didn't modified the source yet, just changed the generated model file for a draft.
Also I was looking inside the source of the findBy function and the CompareOperator::In isn't implemented yet ? If it is, can you send me a example on how to use it (I don't know if I need to pass a string separeted by comma, or a vector and etc...).

You can use CompareOperator::In, it should work.

Hello @an-tao sorry for the wait. I was really busy in the last months and so wasn't possible to continue this issue. But now I'm back \0/.
I already made some progress but I would like your opnions in somethings (and I would like to give you a round o applause because the coroutine implementation in drogon is enginious specially the MapperAwaiter, I was blown away. Props to you!!!)

The Async methods to recover the relationship (the callback version already exists, I just changed to use Mapper) (the future version, discussed 4.) can't set up the internal cache because the callback may outlive the current object instance.
Wrong:

void Posts::getUser(const DbClientPtr& clientPtr,
    const std::function<void(Users)>& rcb,
    const ExceptionCallback& ecb)
{
    Mapper<Users> mp(clientPtr);
    mp.findBy(Criteria(Users::Cols::_id, CompareOperator::EQ, *userId_),
        [rcb, ecb, this](const std::vector<Users>& r) {
            if (r.empty())
            {
                ecb(UnexpectedRows("0 rows found"));
            }
            else if (r.size() > 1)
            {
                ecb(UnexpectedRows("Found more than one row"));
            }
            else
            {
                this->setUser(r[0]); //May cause undefined behaviour
            	rcb(r[0]);
            }
        },
        ecb);
}

Right:
void Posts::getUser(const DbClientPtr &clientPtr,
                    const std::function<void(Users)> &rcb,
                    const ExceptionCallback &ecb) const
{
    Mapper<Users> mp(clientPtr);
    mp.findBy(Criteria(Users::Cols::_id, CompareOperator::EQ, *userId_),
    [rcb, ecb](const std::vector<Users>& r) {
        if (r.empty())
        {
            ecb(UnexpectedRows("0 rows found"));
        }
        else if (r.size() > 1)
        {
            ecb(UnexpectedRows("Found more than one row"));
        }
        else
        {
            rcb(r[0]);
        }
    },
    ecb);
}

So in this case the callback (implemented by the user) should look something like this if he wants to the cache to be set
post.getUser(
	client,
	[post](const Users& user) mutable
	{
		post.setUser(user);
		...
	},
	[](const DrogonDbException& e)
	{

	}
);

Any thoughts on this ?

The coroutine version to recover the relationship would look like this

drogon::Task<std::shared_ptr<Users>> Posts::getCoroUser(const drogon::orm::DbClientPtr& clientPtr)
{
    CoroMapper<Users> mp(clientPtr);
    auto user = co_await mp.findBy(Criteria(Users::Cols::_id, CompareOperator::EQ, *userId_));
    if (user.empty())
        throw UnexpectedRows("0 rows found");
	else if (user.size() > 1)
        throw UnexpectedRows("Found more than one row");

    setUser(user[0]);
    co_return r_user_;
}

It's not possible to return Users& because Task::promise_type::return_value() gets confused because of the overloadings, so we could return void (this would force the user to do .getUser() after it to get the cache, which is not cool), returning a copy to Users would be foolish because we want the user be able to modify the relationship and be reflected in the Posts class. So we return the shared_ptr. This would be a little bit confunsing if I was the user (because the cache doesn't return a shared_ptr), and probably get annoyed. So any ideias ?

The sync version of the eager loading function looks like this
Has many case:

void Posts::loadComments(const DbClientPtr &clientPtr, std::vector<Posts>& targets, const std::function<void(std::vector<Comments>&)>& rcb)
{
    std::unordered_map<int64_t, Posts*> map;

    map.reserve(targets.size());

    std::vector<int64_t> originalKeys;
    originalKeys.reserve(targets.size());

    for (auto& target : targets)
    {
        auto originalKey = target.getValueOfId();
        map[originalKey] = ⌖
        originalKeys.push_back(originalKey);
    }

    Mapper<Comments> mp(clientPtr);
    auto relations = mp.orderBy(Comments::Cols::_post_id)
                            .findBy(
                                Criteria(
                                Comments::Cols::_post_id,
                                CompareOperator::In,
                                originalKeys)
                            );
    rcb(relations);

    if (relations.empty()) return;
    auto begin = relations.begin();
    for (auto it = relations.begin(); it != relations.end(); it++)
    {
        const auto relationVal = begin->getValueOfPostId();
        if (relationVal != it->getValueOfPostId())
        {
            const auto end = it - 1;
            std::vector temp_vec(
                std::make_move_iterator(begin),
                std::make_move_iterator(end)
            );
            map.at(relationVal)->setComments(std::move(temp_vec));
            begin = it;
        }
    }

    //last iteration
    const auto relationVal = begin->getValueOfPostId();
    std::vector temp_vec(
        std::make_move_iterator(begin),
        std::make_move_iterator(relations.end())
    );
    map.at(relationVal)->setComments(std::move(temp_vec));
}

Has one case:
void Posts::loadUser(const DbClientPtr &clientPtr, std::vector<Posts>& targets, const std::function<void(std::vector<Users>&)>& rcb)
{
    std::unordered_map<int64_t, std::vector<Posts*>> map;

    map.reserve(targets.size());

    std::vector<int64_t> originalKeys;
    originalKeys.reserve(targets.size());

    for (auto& target : targets)
    {
        auto originalKey = target.getValueOfUserId();
        map[originalKey].push_back(&target);
        originalKeys.push_back(originalKey);
    }

    Mapper<Users> mp(clientPtr);
    auto relations = mp.orderBy(Users::Cols::_id)
                            .findBy(
                                Criteria(
                                Users::Cols::_id,
                                CompareOperator::In,
                                originalKeys)
                            );
    rcb(relations);

    if (relations.empty()) return;
    for (auto it = relations.begin(); it != relations.end(); it++)
    {
        auto parents = map.at(it->getValueOfId());
        for (auto parent : parents)
        {
            parent->setUser(*it);
        }
    }

}

The callback function to load more things after is optional
The coroutine version would be similar just change de Mapper to CoroMapper, co_await the findBy, remove the callback and return a Task<>
I can't think of a way to implement the future version, because of 2 things:

Being async it may suffer from the same thing as 1. (it may outlive the current instances and trigger UB)
I don't know where to await/get the future and continue the processing after it. I thought in to this in a event loop and use a promise to write when finish and return a future. But it can't be in the current thread event loop because would cause deadlock since the promise would be in the next job, and the future in the current. One possibility was to use the main event loop, but this is an obvious bad ideia since it would clog the main loop. And my last ideia was to use the same loop as the database connection uses, since is something related to it, but I don't have access to it in "user land"
Any ideias ?

The future version to recover the relationship would suffer from the samething as the future version of the eager loading.

I already implemented in drogon_ctl the right version of 1., the Has many/Has one sync version of 3.
I would like to hear your thoughts before continuing.


Deleted redundant code in MIQ Policy Controller / Conditions

Check for generated flash messages no longer needed with the code fix in https://github.com/ManageIQ/manageiq/pull/6525
New begin/rescue block in ci_processing/process_elements generates flash messages

@dclarizio @h-kataria Redundant code removal, please review.

LGTM


add documentation for auctionDelay in userSync

related PR https://github.com/prebid/Prebid.js/pull/4115

@bretg removed the sandbox changes.

Reminder to merge this as well. 😀

will be released with 2.35


Using CertPathValidator of the standard library, better cert checking, possibility of additional checks including local CRL's (TBD)

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Let's close this for now and circle back when the work on the ref apps resume since I think we want this to look slightly different - thanks!


oraclejdk: do not strip regular files from install dir

Otherwise it removes src.zip, while those additional readme and license files won't harm anyone.

No response from author for a long time, please open a new PR if you're still interested in this.


KCORE-414; Make request/response error handling more conventional

The purpose of this patch is to get rid of the clumsy error handling in maybeHandleError and establish more consistent conventions for request/response handling.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@guozhangwang @abbccdda Thanks for the comments. I've pushed a couple commits which I believe addresses your comments. In general, we try to be more rigorous with the error handling by identifying all of the possible errors and ensuring they are handled. The core changes are the following:

I've added a new INCONSISTENT_VOTER_SET as a more useful error for voter-only requests
I've removed the logic to return some errors which should not be possible. For example, there should never be a reason why we return NOT_LEADER_FOR_PARTITION from FetchQuorumRecords in normal circumstances. A stale fetch request would get fenced by the epoch. And unlike with topic partitions, a follower cannot learn about the leader before the leader itself.
I've added some additional validations. For example, we now add checks to make sure that we reject requests which indicate we are the leader when we know we are not. We also validate all offsets and epochs strictly in both FetchQuorumRecords and Vote requests.


Typo fix: Remove extra "multiple".

Assuming I'm parsing this sentence correctly, I think the multiple multiple is a typo. :)
Are a typo?

Yep, thanks for the PR.


Missing $ in code snippet for AzureCLI

The code snippet that shows how to deploy the ARM template is missing the $ in setting the templateFile variable.
templateFile="{provide-the-path-to-the-template-file}"
az deployment group create \
  --name blanktemplate \
  --resource-group myResourceGroup \
  --template-file $templateFile

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 7bf283cd-65c2-09ad-0af2-37bf95fe4d90
Version Independent ID: 46451ccf-174a-e4da-433f-aa8c5570557d
Content: Tutorial - Create and deploy template - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/template-tutorial-create-first-template.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@typicat Did you mean it should be $templateFile="{provide-the-path-to-the-template-file}" ? No, in CLI we don't add a $ while setting a variable. It's done in PowerShell but not in CLI.


Fix Rigetti check for Aspen family device kind

Sync with new API for checking device family in qcs-sdk-python,
Ref: https://github.com/rigetti/qcs-sdk-rust/pull/463 in isa.pyi

Require qcs-sdk-python-0.20.1 which introduced the new family API

Fixes #6732

cc: @MarquessV, @kalzoo


Zachmu/join bugs

Fixes many issues with the first version of pushdown:

Fixed bug where filter predicate was being inappropriately removed after being used in index
Fixed bug where a self-join would inappropriately use an incorrect index in some cases
Made pushdown apply to left, right, and indexed joins where possible
Lots more tests


add jobs for 4.11,4.12 and 4.13

Add jobs for 4.11,4.12, and 4.13 stable testing.
@kuiwang02 @Xia-Zhao-rh Could you help have a review? Thanks!

Frankly I do not know if these selected job are suitable or not.

Yeah, I just pick up some jobs based on different platforms. Anyway, updated it.

/approve
/lgtm


Strip sourceMappingUrls from installed modules (fixes #932).

Changes
This strips the sourceMappingUrl comment from installed source code, since the original source maps are no longer accurate.
Testing
Updated expected output of existing tests.

This change is

Thanks for the PR! Unfortunately we actually already have a PR open for this that's been reviewed and is ready to merge: https://github.com/pikapkg/snowpack/pull/976 Closing this as a duplicate

Oops, I forgot to check first -- sorry.


Skip dialog feature

press a key to skip npc dialogs

@AJTheEnder tell me which key you prefer to press to skip dialogs on a keyborad and on a joystick

@Paracetamol56 I think E on keyboard is a good key for skip dialogs and for the controller the button A is good


Platform type should allow for extension

As discussed on Discord, wanted to document it here too
Currently you can extend the Context type as such:
declare module "@marko/run" {
  interface ContextExtensions {
    platform: WHATEVER
  }
}

When considering adding support for Cloudflare, it would be very helpful to be able to extend the Platform type in a similar way (ie maybe through a PlatformExtensions interface). Other adapters might also benefit, but particularly for Cloudflare this would allow for the end-user to specify their service binding types within their app code (as this would not be known ahead of time to the adapter code)

Yeah, that makes sense. Currently the adapter can specify a type which gets written to the .marko-run/routes.d.ts but this doesn't let users easily extend it. I will add an extension interface to simply this.

Thanks! I think that will be really helpful as in CF you usually would want to extend the Platform type to add your databases or other service bindings


Including UserProvider in my bundle added 100kbs

These helpers are great, but seem to include a bunch of Supabase UI that I don't want.

I'm only using useUser and supabaseClient from @supabase/supabase-auth-helpers/nextjs and UserProvider from @supabase/supabase-auth-helpers/react. Is this working as intended?

Looks like this is only happening due to a re-export of the auth component. Could this lib just be a peer dependency?
https://github.com/supabase-community/supabase-auth-helpers/blob/e188cb903cd532aa438729fda4269bed53b3fff5/src/react/index.tsx#L6

Yah, we want to break out the UI stuff into it's own sub module and build a better rollup pipeline in the future.


when deploy on ACK 1.18.1 koord-manager pod always crash

logs of koord-manager pod：
W0407 10:06:26.017519       1 noderesource.go:234] node koordinator.sh/batch-memory resource diff bigger than 0.1, need sync
W0407 10:06:26.032565       1 noderesource.go:234] node koordinator.sh/batch-memory resource diff bigger than 0.1, need sync
W0407 10:06:30.192036       1 noderesource.go:234] node koordinator.sh/batch-memory resource diff bigger than 0.1, need sync
W0407 10:06:30.212145       1 noderesource.go:234] node koordinator.sh/batch-memory resource diff bigger than 0.1, need sync
I0407 10:06:35.111049       1 request.go:597] Waited for 55.075105ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/alert.alibabacloud.com/v1beta1?timeout=32s
I0407 10:06:35.145232       1 request.go:597] Waited for 89.253202ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/autoscaling/v2beta2?timeout=32s
I0407 10:06:35.178362       1 request.go:597] Waited for 122.38075ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/apiextensions.k8s.io/v1?timeout=32s
I0407 10:06:35.211422       1 request.go:597] Waited for 155.435651ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/autoscaling/v2beta1?timeout=32s
I0407 10:06:35.244458       1 request.go:597] Waited for 188.457989ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/storage.kubesphere.io/v1alpha1?timeout=32s
I0407 10:06:35.278526       1 request.go:597] Waited for 222.531793ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/tenant.kubesphere.io/v1alpha1?timeout=32s
I0407 10:06:35.311777       1 request.go:597] Waited for 255.783658ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/batch/v1?timeout=32s
I0407 10:06:35.344844       1 request.go:597] Waited for 288.851137ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/authentication.k8s.io/v1?timeout=32s
I0407 10:06:35.377888       1 request.go:597] Waited for 321.886237ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/apiextensions.k8s.io/v1beta1?timeout=32s
I0407 10:06:35.410868       1 request.go:597] Waited for 354.862882ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/authorization.k8s.io/v1?timeout=32s
I0407 10:06:35.445056       1 request.go:597] Waited for 389.044635ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/application.kubesphere.io/v1alpha1?timeout=32s
I0407 10:06:35.478284       1 request.go:597] Waited for 422.284091ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/rbac.authorization.k8s.io/v1?timeout=32s
I0407 10:06:35.511365       1 request.go:597] Waited for 455.363074ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/config.koordinator.sh/v1alpha1?timeout=32s
I0407 10:06:35.544428       1 request.go:597] Waited for 488.423354ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/rbac.authorization.k8s.io/v1beta1?timeout=32s
I0407 10:06:35.577530       1 request.go:597] Waited for 521.517315ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/monitoring.coreos.com/v1?timeout=32s
I0407 10:06:35.611734       1 request.go:597] Waited for 555.722446ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/discovery.k8s.io/v1beta1?timeout=32s
I0407 10:06:35.645163       1 request.go:597] Waited for 589.153428ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/node.k8s.io/v1beta1?timeout=32s
I0407 10:06:35.678261       1 request.go:597] Waited for 622.239304ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/scheduling.k8s.io/v1beta1?timeout=32s
I0407 10:06:35.710979       1 request.go:597] Waited for 654.969336ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/authentication.k8s.io/v1beta1?timeout=32s
I0407 10:06:35.745052       1 request.go:597] Waited for 689.04109ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/networking.k8s.io/v1beta1?timeout=32s
I0407 10:06:35.778181       1 request.go:597] Waited for 722.153387ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/coordination.k8s.io/v1beta1?timeout=32s
I0407 10:06:35.811371       1 request.go:597] Waited for 755.351178ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/policy/v1beta1?timeout=32s
I0407 10:06:35.844491       1 request.go:597] Waited for 788.468955ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/apps.kruise.io/v1alpha1?timeout=32s
I0407 10:06:35.878183       1 request.go:597] Waited for 822.161498ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/networking.k8s.io/v1?timeout=32s
I0407 10:06:35.911844       1 request.go:597] Waited for 855.812499ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/coordination.k8s.io/v1?timeout=32s
I0407 10:06:35.944926       1 request.go:597] Waited for 888.890657ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/cluster.kubesphere.io/v1alpha1?timeout=32s
I0407 10:06:35.978193       1 request.go:597] Waited for 922.169979ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/apps.kruise.io/v1beta1?timeout=32s
I0407 10:06:36.011313       1 request.go:597] Waited for 955.28796ms due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/scheduling.k8s.io/v1?timeout=32s
E0407 10:06:36.016423       1 deleg.go:144] controller-runtime/source "msg"="if kind is a CRD, it should be installed before calling Start" "error"="no matches for kind "NodeSLO" in version "slo.koordinator.sh/v1alpha1""  "kind"={"Group":"slo.koordinator.sh","Kind":"NodeSLO"}
ps: <IP_ADDRESS> is the svc "kubernetes" in default namespace.

<IP_ADDRESS> is the svc kubernetes in default namespace.

/assign @eahydra

@cao99 Hi, NodeSLO CRD was missing earlier, it shoud be fixed now.
Please reinstall Koordinator using Helm with the latest chart and let us know if this issue is not resolved.

@cao99 Hi, thanks for the feedback. The issue has been fixed, please reinstall the koordinator with latest charts.

after update NodeSLO CRD created，but meet the same error in logs

It doesn't look like it's installed correctly. Please uninstall and force update the chart package and install it again.
If installed correctly, there is CRD named nodeslos.slo.koordinator.sh in cluster.

after reinstall working now！

after reinstall working now！thks ！


Security assurance

Description

Introducing a set of security assurance pages and expanding on the enterprise features previously included.
A starter for 10 on some kind of security overview cheat sheet (needs further work)

Content to be finalised (not year ready) but sharing for early visibility and feedback.
See changes at: /enterprise/tech-overview/security/overview
Type of change

New document(s)/updating existing

Reviewers

Prior to merge I need to ensure a few stakeholders are appropriately bought into this content being made public as it's pivoting away from the NDA gated content on the trust portal. From my perspective having it version controlled and interactive is far better.

@mcclowes I've further evolved this and brought in an extra page to talk about PaaS.
Discussed with Josephine and we're happy that this will replace the current whitepapers on the trust portal.
Thanks

Intentionally leaving this off the main menu for now @pzaichkina


Porting to React for web?

This repo looks amazing.
Not too familiar with React Native, how much work would it take to port this to React for the web?
Any info would be much appreciated.

There isn't any plan yet, the UI will need to change drastically though..
Also the web already have similar project such as https://jessepollak.github.io/card/ or the react port https://github.com/shatran/card-react if you really need one
-Sam

That makes sense, thanks.
Just came across https://stripe.com/docs/elements which will fill my needs for now, appreciate the info.

👍 Stripe elements looks really nice! Never know it existed


Fix nightly (2024-07-23)

something is changed in the debian packaging system https://github.com/gardenlinux/gardenlinux/actions/runs/10053575814

https://github.com/gardenlinux/repo/commit/5137c77fd99be9562678b91b1dc26f14b8f211f1


Feature picking

Follow up on #285: Store shared_ptr of Properties instance in Label options and return it as feature picking result.
I've started to use SWIG to generate the JNI boilerplate which can do pretty advanced bindings:
http://www.swig.org/Doc3.0/Java.html#Java
http://www.swig.org/Doc3.0/Android.html#Android for a good example

[X] converted ClienGeoJsonSource bindings to use SWIG

The Java side now holds a shared_ptr reference to the DataSource and can work on it directly

[ ] removed Tangram::source* pass-through methods

Added support for pushing Tagged features through JNI

Going to start reviewing this now. @hjanetzek any more big changes coming here?

@tallytalwar, ready to review. I've removed the swig bindings for ClientGeoJsonSource which were previously included in this PR.

This is mostly good, apart from the following:

[ ] Android only gets the first picked feature
[ ] ios implementation (Ignoring raspberry pi implementation)

:tada:


[Bug] 主观评测得分解析错误

例如以下例子中 **Score: 9** 被错误解析为 5.0
{
    "question": "To cook perfectly golden pancakes,",
    "obj": {
        "generation_a": "Mix the ingredients together in a bowl and pour it onto a hot pan.",
        "generation_b": "To cook golden pancakes, mix flour, eggs, milk, and baking powder. Heat a non-stick pan, scoop batter, and cook until bubbles form. Flip and cook until golden. Serve with maple syrup.🥞",
        "preference": "ansB",
    },
    "sub": {
        "generation_a": "To cook golden pancakes, mix flour, eggs, milk, and baking powder. Heat a non-stick pan, scoop batter, and cook until bubbles form. Flip and cook until golden. Serve with maple syrup.🥞",
        "generation_b": "Mix the ingredients together in a bowl and pour it onto a hot pan.",
        "feedback": "Answer A provides a more detailed, step-by-step process of how to cook pancakes. It specifies the ingredients needed, the type of pan to use, and how to know when the pancake is ready to flip. It also suggests a way to serve the pancakes. Answer B, on the other hand, is more general and lacks these details. \n\nDecision: A.",
        "preference": "ansA",
        "llm_a": "openbuddy-70b",
        "llm_b": "internlm-7b",
    },
    "data_source": "piqa",
    "metadata": {"quality_a_sub": "high", "quality_b_sub": "low"},
    "evaluation": {
        "cot": "### Evaluation of Generated Feedback\n\n**Generated Feedback Analysis:**\n\n1. **Clarity and Detail:**\n   - The generated feedback accurately highlights that Answer A provides a clear and detailed step-by-step guide, mentioning specific ingredients and cooking steps. This aligns well with the reference feedback, which also emphasizes the detailed nature of Answer A.\n\n2. **Additional Information:**\n   - The generated feedback notes the suggestion of serving with maple syrup, which is a practical addition. This aspect is not explicitly mentioned in the reference feedback, making the generated feedback slightly more comprehensive in this regard.\n\n3. **Engagement:**\n   - The generated feedback mentions the use of an emoji in Answer A, adding an element of engagement. This is an additional observation not covered in the reference feedback, which could be seen as enhancing the evaluation by considering the engagement factor.\n\n4. **Critique of Answer B:**\n   - Both the generated and reference feedbacks agree that Answer B lacks detail and completeness. The generated feedback expands on this by pointing out the absence of engaging elements, which is a valid critique but not present in the reference feedback.\n\n5. **Overall Preference:**\n   - The generated feedback clearly states a preference for Answer A, providing reasons that are consistent with the reference feedback. It also adds value by discussing engagement and additional serving suggestions.\n\n**Comparison with Reference Feedback:**\n\n- The generated feedback provides a more comprehensive analysis by including aspects of engagement and additional serving suggestions, which are not present in the reference feedback. This makes the generated feedback slightly more detailed and engaging.\n\n**Score: 9**\n\nThe generated feedback is slightly better than the reference feedback due to its additional insights into engagement and serving suggestions, while still maintaining a clear and accurate analysis of the answers.",
        "score": 5.0,
    },
}

还有 "Decision: .+" 也是同样的问题，若存在 "Decision: 6" 也无法正确解析，是否将正则表达式修改为 "Decision: [.\d]+" 会更好呢？

Thank you for reaching to Our Github. Customer service may take some time to respond due to a large number of requests. We believe your case will be resolved as soon as possible. Kindly visit the HERE TO CONTACT OUR LIVE SUPPORT DEV for instant support response
Note: Click on the live chat icon at the bottom corner of the page


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 49baf33:
:clock10: Pending: waiting for processors (21 builds ahead of you)
:warning: Docs Build is busy, currently there are 21 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 49baf33:
:clock10: Full build: the average full build time is 7 min(s) 40 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 49baf33:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Fix IotNetworkAfr_ReceiveUpto() to return the number of bytes recieved.

Fix IotNetworkAfr_ReceiveUpto() to return the number of bytes recieved.
This has been tested with the HTTPS demo and tests that utilize the network.
Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks


crash

The Plugin TalkingLeaves.glyphsPlugin has caused a crash. Please update it by opening the Plugin Manager or re-downloading it from the original source.
Details:
Traceback (most recent call last):
File "plugin.py", line 48, in openWindow_
self.tl = TalkingLeaves()
^^^^^^^^^^^^^^^
File "TalkingLeaves.py", line 79, in init
if Glyphs.devMode:
^^^^^^^^^^^^^^
AttributeError: 'NSKVONotifying_GSApplication' object has no attribute 'devMode'
App:3.3-3309 Plugin:0.1-2 System:14.5.0

Thanks, I just fixed this in 79f1ee1. Silly mistake, as the Glyphs.devMode property obviously doesn't exist outside of dev mode, so I fixed it by using getattr().
Also, @justanotherfoundry as a plugin developer you might find some useful ideas in the dev folder. I've been looking for ways to test Glyphs plugins without restarting Glyphs after each change, and have found two useful ways to do it:

Put only the code related to loading the plugin class and adding it to the menu bar in plugin.py, and everything else into TalkingLeaves.py which is set up to be loaded as a module or run as a script from the Script menu. So instead of restarting Glyphs after each change, you just close the TalkingLeaves window and then Cmd-Opt-R to run the updated script.
Use executeVanillaTest to wrap TalkingLeaves into a mini application that can run from Terminal. I used glyphsLib to load a .glyphs file into a GSFont object, and then I wrote a "fake" GlyphsApp library that minimally replicates the parts of the API that TalkingLeaves uses.

Thanks for the fix!

Regarding the testing-without-restarting: Why isn’t TalkingLeaves simply implemented as a plain script?

It definitely could be just a script, but I think users have different expectations for a script versus a plugin. So I guess it's about branding, mainly. Plugin implies a larger and/or more useful project, more support from the developer, etc. A plugin is also neatly packaged and easier to install, with a more consistent presence somewhere in the app (in the Window menu in this case).
Also, from a development perspective, the majority of the code is in one file right now, but it's getting quite long and unwieldy to navigate the code. So I'll be dividing it into modules soon, which makes a lot more sense to do inside of a plugin bundle as opposed to a folder of scripts.