text:
Unhandled exception. System.EntryPointNotFoundException: Unable to find an entry point named 'objdetect_CascadeClassifier_newFromFile' in shared library 'OpenCvSharpExtern'.

Hey, @sdcb I know your library only includes some modules. My question is - how could I expand it?
I'm having trouble running OpenCVSharp4 on Debian 12, and your runtime is closest thing I could find.

Hey, @sdcb , I think this issue is a duplicate of #2 . Chances are that both projects are running .Net 8, and that is where the issue comes from.
You can see the description of the related warning here: https://learn.microsoft.com/en-us/dotnet/core/tools/sdk-errors/netsdk1206
You might want to move to portable RIDs.

OpenCVSharp4 on Debian 12 you can try the ubuntu 22.04 version

authors: lukardvn sdcb skolumban-ex

repo: sdcb/opencvsharp-mini-runtime


text:
Fix inverted --no-root cmd option

Fixes #973

Can confirm this fixes the behavior to be sane again.

source: gharchive/pull-request

repo: sdispater/poetry

license: MIT

license_type: permissive

license_source: github-api


text:
Add sdk env install subcommand

Fixes #784.

Needs some more testing love 😆 .

Looks great! Left one small comment regarding the test.

@marc0der Ready to merge?

Great, glad to see this merged, it's a welcome addition - thanks!
@marc0der - do you have any plans to do a new release of SDKMAN soon? Looking at the releases, 5.9.0 was in early Aug and 5.9.1 a couple of months later in early-ish Oct, so maybe a good time for 5.9.2 (he says hopefully! 😆 )?

authors: helpermethod joehorsnell marc0der

repo: sdkman/sdkman-cli


text:
Added validation for not nullable edm parameters, and added null check when setting parameters for primitive types.

Added validation for not nullable edm parameters, and added null check when setting parameters for primitive types.

Looks good.

Looks Okay!

authors: agelenler lozenko vinayknl

repo: sdl/odata

license_source: bigquery


text:
docs: fix the typo in code example of next-mdx-static-import

Hi there, thanks for the awesome library!
I noticed a typo in the next-mdx-static-import README, so I created a fix for it. If I missed something obvious, feel free to close this.
By the way, this feature looks great! Will it be released in the next version?

Thanks 🙏

Will it be released in the next version?

Yes.

repo: sdorra/content-collections


text:
ListElementPointer(List): Update code to tally with comments

The constructor’s header comments state that this object is backed by
a defensive copy of the list that is passed in as parameter. However,
the code does not reflect this behaviour.

The constructor should use create a defensive copy of the list to
prevent unintentional modifications to the backing list whenever the
list passed in as parameter is modified.

Let’s update ListElementPointer(List<String>) to create a defensive copy
of the list.

@Zhiyuan-Amos btw why does getHistorySnapshot() return a ListElementPointer? It assumes that callers would use it as a ListElementPointer, and its even more strange when you see that ListElementPointer takes a List<String> in its constructor...
If history is an ordered collection of items, then expose it as a list?

@damithc Approve?

Changes Unknown when pulling 3f112c97d31efaf8dc10be1dd871992ca123ecd6 on Zhiyuan-Amos:list-element-pointer-bug into ** on se-edu:master**.

@Zhiyuan-Amos btw why does getHistorySnapshot() return a ListElementPointer? It assumes that callers would use it as a ListElementPointer, and its even more strange when you see that ListElementPointer takes a List in its constructor...
If history is an ordered collection of items, then expose it as a list?

@pyokagan Yup, what you said sounds right. I'm wondering whether we should actually shift the storing of the history of user input in CommandBox instead of Logic, since CommandBox functions as a View-Controller.
That way, does it make better sense to use a ListElementPointer since CommandBox will only use its history in the context of a ListElementPointer?

If we think of history as simply filling the command box with some text when the up/down key is pressed, then it is fine to store that data in the command box itself. i.e. history is local to the command box. Rest of the code doesn't need to know about it. But if we think of history as representing the history of user actions (i.e. it goes beyond just the command box), then it should be in a more central location.

I think the initial reason why we decided to leave history at a more central location is that it should capture both commands and user input.
However, since we have decided not to do it that way and that we have separate histories (user input history & command history), then should the user input history be placed in the command box instead of logic?

I'm of two minds about it. Our current architecture style follows an n-tier approach where the model is a tier that sits behind the logic tier. Attaching micro-models to various parts of the GUI is a different architecture style altogether. While there is no rule that we have to follow one architecture style exclusively, mixing of styles should be a deliberate and justifiable decision. There is value in giving examples of multiple architecture styles given that this is used for teaching, as long as it is done carefully and not at the expense of simplicity of the design.

@Zhiyuan-Amos

since CommandBox functions as a View-Controller and user input is somewhat like its model,

Ah yes, this makes me notice something. If we are modeling the user's input history as part of the domain, then why isn't the input history stored in the model layer?
It seems like a code smell to me when we have to, in addition to the Model object, pass separate CommandHistory and UndoRedoStack objects to the command, which indicates to me that we are storing user state in too many different locations which is unwieldy.

As an aside, regarding the "history" feature:
imo, I think the feature should be removed. It was sold to me as a "nice to have" feature that would have a negligible impact on code base size since it was thought that it could piggy back on the undo/redo architecture. But now it turns out that it's not the case, and now it's yet another feature in addressbook-level4, which already has the problem of feature/scope creep.

authors: Zhiyuan-Amos coveralls damithc pyokagan


text:
Add periodic encounter summary feature

Description
It would be useful for users to get a periodic summary of their encounters and interactions with people. This summary could be delivered on a weekly/monthly/yearly basis to the user. The summary should contain how many new people they have met, which people have the most new encounters added (most improved), who they have the most encounters and least encounters with. This should be delivered in a fun and engaging way that encourages users to keep connecting with new and existing people.
By having a periodic encounter summary provided to users, they can receive a reminder on who they should contact soon, and keep track of their progress and how close they are to achieving their networking/socialisation goals.
Acceptance Criteria

[ ] Summary is sent to users on a periodic basis
[ ] Summary provides information on how many new people they have met
[ ] Summary provides information on people the user has met that has the most new encounters (most improved)
[ ] Summary provides information on people who the user has the most encounters with
[ ] Summary provides information on people who the user has the least encounters with
[ ] Summary is delivered to users in a fun and engaging manner

Implementation details
Consider UI design of summary for an engaging user experience. Database may be required to store statistical data.
Testing notes
Tests should ensure that functionality works as intended. Take care when testing the periodic functionality.

LGTM!

source: gharchive/issue


text:
Incorrect catalog status when synchronizing templates timeout

Describe the bug

The catalog status is incorrect when synchronizing templates timeout.
To Reproduce
Steps to reproduce the behavior:

Add a catalog.

Wait to synchronize template.

The timeout is too short, and it remains in Initializing state after timeout.

2023-08-11T06:34:45.564Z	E	catalog	failed to update sync info: context deadline exceeded
github.com/seal-io/seal/pkg/catalog.Sync.func1
	github.com/seal-io/seal/pkg/catalog/catalog.go:110
github.com/alitto/pond.(*WorkerPool).executeTask
	github.com/alitto/pond@v1.8.3/pond.go:454
github.com/alitto/pond.worker
	github.com/alitto/pond@v1.8.3/worker.go:32
2023-08-11T06:34:45.574Z	E	catalog	failed to update catalog cloudposse status: context deadline exceeded
github.com/seal-io/seal/pkg/catalog.Sync.func1
	github.com/seal-io/seal/pkg/catalog/catalog.go:119
github.com/alitto/pond.(*WorkerPool).executeTask
	github.com/alitto/pond@v1.8.3/pond.go:454
github.com/alitto/pond.worker
	github.com/alitto/pond@v1.8.3/worker.go:32

Expected behavior

Environment

Seal version: 0265239705f6f6ba511c842b466ae843cc94e775

Additional context
Add any other context about the problem here.

Currently not reproducible, need to keep watching

Environment

Walrus version: main 7dddda0f4b8d278b4731528af87dbf93f8a17d97
UI version: dev-42d12aa

Trigger catalog synchronization via CatalogTemplateSync task. Sometimes it may time out and the catalog stuck in Initializing state.

2023-09-07T07:14:00.043Z	E	catalog	failed to sync catalog terraform-alicloud-modules templates: Get "https://api.github.com/orgs/terraform-alicloud-modules/repos?per_page=100&visibility=public": context deadline exceeded
github.com/seal-io/walrus/pkg/catalog.UpdateStatusWithSyncErr
	github.com/seal-io/walrus/pkg/catalog/catalog.go:197
github.com/seal-io/walrus/pkg/scheduler/catalog.(*TemplateSyncTask).Process
	github.com/seal-io/walrus/pkg/scheduler/catalog/template_sync_task.go:79
github.com/seal-io/walrus/utils/cron.timeoutTask.Process
	github.com/seal-io/walrus/utils@v0.0.0-00010101000000-000000000000/cron/cron.go:156
reflect.Value.call
	reflect/value.go:584
reflect.Value.Call
	reflect/value.go:368
github.com/go-co-op/gocron.callJobFuncWithParams
	github.com/go-co-op/gocron@v1.29.0/gocron.go:116
github.com/go-co-op/gocron.runJob
	github.com/go-co-op/gocron@v1.29.0/executor.go:76
github.com/go-co-op/gocron.(*executor).runJob
	github.com/go-co-op/gocron@v1.29.0/executor.go:173
github.com/go-co-op/gocron.(*executor).run.func1
	github.com/go-co-op/gocron@v1.29.0/executor.go:239
2023-09-07T07:14:00.046Z	W	task	error executing: error syncing templates of catalog 477357966266204162: failed to update sync info: context deadline exceeded	{"createBy": "CatalogTemplateSyncCronExpr"}

Template synchronization completed, but context deadline exceeded reported.

2023-09-07T10:43:00.597Z	D	catalog	synced catalog terraform-alicloud-modules, total 208, processed: 15, failed: 193
2023-09-07T10:43:00.597Z	W	catalog	failed to sync catalog terraform-alicloud-modules templates: error syncing template terraform-alicloud-ram: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ram': error running /usr/bin/git: ; error syncing template terraform-alicloud-alikafka: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-alikafka': error running /usr/bin/git: ; error syncing template terraform-alicloud-redis: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-redis': error running /usr/bin/git: ; error syncing template terraform-alicloud-wordpress: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-wordpress': error running /usr/bin/git: ; error syncing template terraform-alicloud-market-tensorflow: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-market-tensorflow': error running /usr/bin/git: ; error syncing template terraform-alicloud-slb-http: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-slb-http': error running /usr/bin/git: ; error syncing template terraform-alicloud-kms: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-kms': error running /usr/bin/git: ; error syncing template terraform-alicloud-ons: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ons': error running /usr/bin/git: ; error syncing template terraform-alicloud-rabbitmq: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-rabbitmq': error running /usr/bin/git: ; error syncing template terraform-alicloud-dms-rds: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-dms-rds': error running /usr/bin/git: ; error syncing template terraform-alicloud-ga-slb-ecs-cdn-oss: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ga-slb-ecs-cdn-oss': error running /usr/bin/git: ; error syncing template terraform-alicloud-fc-oss-trigger: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-fc-oss-trigger': error running /usr/bin/git: ; error syncing template terraform-alicloud-fcs-nas: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-fcs-nas': error running /usr/bin/git: ; error syncing template terraform-alicloud-alb-http: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-alb-http': error running /usr/bin/git: ; error syncing template terraform-alicloud-cloud-storage-gateway: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cloud-storage-gateway': error running /usr/bin/git: ; error syncing template terraform-alicloud-sae: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-sae': error running /usr/bin/git: ; error syncing template terraform-alicloud-eais: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eais': error running /usr/bin/git: ; error syncing template terraform-alicloud-direct-mail: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-direct-mail': error running /usr/bin/git: ; error syncing template terraform-alicloud-landing-zone-cen-with-dmz-vpc: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-landing-zone-cen-with-dmz-vpc': error running /usr/bin/git: ; error syncing template terraform-alicloud-slb-acl: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-slb-acl': /usr/bin/git exited with -1: Cloning into '/tmp/seal-template-QckpPpfJ6Y'...
; error syncing template terraform-alicloud-ddoscoo-instance: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ddoscoo-instance': error running /usr/bin/git: ; error syncing template terraform-alicloud-serverless-webapp: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-serverless-webapp': error running /usr/bin/git: ; error syncing template terraform-alicloud-sls-logtail: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-sls-logtail': error running /usr/bin/git: ; error syncing template terraform-alicloud-market-wordpress: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-market-wordpress': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecs-image: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecs-image': error running /usr/bin/git: ; error syncing template terraform-alicloud-multi-zone-infrastructure-with-ots: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-multi-zone-infrastructure-with-ots': error running /usr/bin/git: ; error syncing template terraform-alicloud-kubernetes-nodes-supplement: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-kubernetes-nodes-supplement': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecs-rds: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecs-rds': error running /usr/bin/git: ; error syncing template terraform-alicloud-eip-slb-ecs-polardb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eip-slb-ecs-polardb': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-slb-ecs-ga-dns: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-slb-ecs-ga-dns': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-ecs-rds-slb-redis: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-ecs-rds-slb-redis': error running /usr/bin/git: ; error syncing template terraform-alicloud-quota-application: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-quota-application': error running /usr/bin/git: ; error syncing template terraform-alicloud-alb-https: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-alb-https': error running /usr/bin/git: ; error syncing template terraform-alicloud-cen-transit-router: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cen-transit-router': error running /usr/bin/git: ; error syncing template terraform-alicloud-polardb-postgresql: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-polardb-postgresql': error running /usr/bin/git: ; error syncing template terraform-alicloud-vbr: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vbr': error running /usr/bin/git: ; error syncing template terraform-alicloud-dbfs: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-dbfs': error running /usr/bin/git: ; error syncing template terraform-alicloud-landing-zone-account-factory-role-based-sso: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-landing-zone-account-factory-role-based-sso': error running /usr/bin/git: ; error syncing template terraform-alicloud-elasticsearch-instance: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-elasticsearch-instance': /usr/bin/git exited with -1: Cloning into '/tmp/seal-template-3OLC4ZUb9E'...
; error syncing template terraform-alicloud-ecs-cluster: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecs-cluster': error running /usr/bin/git: ; error syncing template terraform-alicloud-eip: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eip': error running /usr/bin/git: ; error syncing template terraform-alicloud-ram-policy: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ram-policy': error running /usr/bin/git: ; error syncing template terraform-alicloud-lnmp: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-lnmp': error running /usr/bin/git: ; error syncing template terraform-alicloud-slb-tcp: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-slb-tcp': error running /usr/bin/git: ; error syncing template terraform-alicloud-key-pair: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-key-pair': error running /usr/bin/git: ; error syncing template terraform-alicloud-emr-dataflow: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-emr-dataflow': error running /usr/bin/git: ; error syncing template terraform-alicloud-dcdn: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-dcdn': error running /usr/bin/git: ; error syncing template terraform-alicloud-waf: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-waf': error running /usr/bin/git: ; error syncing template terraform-alicloud-rds-to-polardb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-rds-to-polardb': error running /usr/bin/git: ; error syncing template terraform-alicloud-ram-vpc-ecs-cloudmonitor: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ram-vpc-ecs-cloudmonitor': error running /usr/bin/git: ; error syncing template terraform-alicloud-fc-function: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-fc-function': error running /usr/bin/git: ; error syncing template terraform-alicloud-alb-quic: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-alb-quic': error running /usr/bin/git: ; error syncing template terraform-alicloud-hpc-cluster: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-hpc-cluster': error running /usr/bin/git: ; error syncing template terraform-alicloud-serverless-workflow: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-serverless-workflow': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecp: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecp': error running /usr/bin/git: ; error syncing template terraform-alicloud-acr-enterprise: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-acr-enterprise': error running /usr/bin/git: ; error syncing template terraform-alicloud-gitlab: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-gitlab': error running /usr/bin/git: ; error syncing template terraform-alicloud-slb-listener: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-slb-listener': /usr/bin/git exited with -1: Cloning into '/tmp/seal-template-A9GewbVEtF'...
; error syncing template terraform-alicloud-fc: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-fc': error running /usr/bin/git: ; error syncing template terraform-alicloud-nas: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-nas': error running /usr/bin/git: ; error syncing template terraform-alicloud-managed-kubernetes: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-managed-kubernetes': error running /usr/bin/git: ; error syncing template terraform-alicloud-emr-zookeeper: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-emr-zookeeper': error running /usr/bin/git: ; error syncing template terraform-alicloud-rds-postgres: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-rds-postgres': error running /usr/bin/git: ; error syncing template terraform-alicloud-jenkins: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-jenkins': error running /usr/bin/git: ; error syncing template terraform-alicloud-market-app-with-ecs-image: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-market-app-with-ecs-image': error running /usr/bin/git: ; error syncing template terraform-alicloud-analyticdb-mysql: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-analyticdb-mysql': error running /usr/bin/git: ; error syncing template terraform-alicloud-automation-elastic-landing: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-automation-elastic-landing': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecs-redis-mongodb-polardb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecs-redis-mongodb-polardb': error running /usr/bin/git: ; error syncing template rocketmq-redis: error downloading 'https://github.com/terraform-alicloud-modules/rocketmq-redis': error running /usr/bin/git: ; error syncing template terraform-alicloud-rds-to-gpdb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-rds-to-gpdb': error running /usr/bin/git: ; error syncing template terraform-alicloud-logstore-alb-listener: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-logstore-alb-listener': error running /usr/bin/git: ; error syncing template terraform-alicloud-cloud-sso-group: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cloud-sso-group': error running /usr/bin/git: ; error syncing template terraform-alicloud-prometheus: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-prometheus': error running /usr/bin/git: ; error syncing template terraform-alicloud-eventbridge: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eventbridge': error running /usr/bin/git: ; error syncing template terraform-alicloud-dts: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-dts': error running /usr/bin/git: ; error syncing template terraform-alicloud-cloud-firewall: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cloud-firewall': error running /usr/bin/git: ; error syncing template terraform-alicloud-imp: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-imp': error running /usr/bin/git: ; error syncing template terraform-alicloud-private-zone: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-private-zone': /usr/bin/git exited with -1: Cloning into '/tmp/seal-template-5i3KhStVSJ'...
; error syncing template terraform-alicloud-api-gateway: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-api-gateway': error running /usr/bin/git: ; error syncing template terraform-alicloud-gpdb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-gpdb': error running /usr/bin/git: ; error syncing template terraform-alicloud-tensorflow: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-tensorflow': error running /usr/bin/git: ; error syncing template terraform-alicloud-sls: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-sls': error running /usr/bin/git: ; error syncing template terraform-alicloud-hbase-cluster: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-hbase-cluster': error running /usr/bin/git: ; error syncing template terraform-alicloud-bootstrap: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-bootstrap': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecs-gpu-instance: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecs-gpu-instance': error running /usr/bin/git: ; error syncing template terraform-alicloud-resource-manager: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-resource-manager': error running /usr/bin/git: ; error syncing template terraform-alicloud-influxdb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-influxdb': error running /usr/bin/git: ; error syncing template terraform-alicloud-eip-slb-ecs-redis-polardb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eip-slb-ecs-redis-polardb': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecommerce-elasticsearch: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecommerce-elasticsearch': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-privatelink-connection: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-privatelink-connection': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecs-snapshot-oss: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecs-snapshot-oss': error running /usr/bin/git: ; error syncing template terraform-alicloud-alb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-alb': error running /usr/bin/git: ; error syncing template terraform-alicloud-cloud-config: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cloud-config': error running /usr/bin/git: ; error syncing template terraform-alicloud-polardb-mysql: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-polardb-mysql': error running /usr/bin/git: ; error syncing template terraform-alicloud-hbr-nas: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-hbr-nas': error running /usr/bin/git: ; error syncing template terraform-alicloud-data-security-center: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-data-security-center': error running /usr/bin/git: ; error syncing template terraform-alicloud-landing-zone-role-based-sso: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-landing-zone-role-based-sso': error running /usr/bin/git: ; error syncing template terraform-alicloud-cen-bandwidth: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cen-bandwidth': /usr/bin/git exited with -1: Cloning into '/tmp/seal-template-T9iafycD0k'...
; error syncing template terraform-alicloud-serverless-kubernetes: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-serverless-kubernetes': error running /usr/bin/git: ; error syncing template terraform-alicloud-emr-kafka: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-emr-kafka': error running /usr/bin/git: ; error syncing template terraform-alicloud-rds-mysql: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-rds-mysql': error running /usr/bin/git: ; error syncing template terraform-alicloud-network-with-nat: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-network-with-nat': error running /usr/bin/git: ; error syncing template terraform-alicloud-cloud-monitor: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cloud-monitor': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-peering-multi-region: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-peering-multi-region': error running /usr/bin/git: ; error syncing template terraform-alicloud-ram-group: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ram-group': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecs-rds-redis: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecs-rds-redis': error running /usr/bin/git: ; error syncing template terraform-alicloud-kafka-cloudmonitor: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-kafka-cloudmonitor': error running /usr/bin/git: ; error syncing template terraform-alicloud-ons-redis: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ons-redis': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-bastionhost: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-bastionhost': error running /usr/bin/git: ; error syncing template terraform-alicloud-cloud-sso: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cloud-sso': error running /usr/bin/git: ; error syncing template terraform-alicloud-arms: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-arms': error running /usr/bin/git: ; error syncing template terraform-alicloud-eds: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eds': error running /usr/bin/git: ; error syncing template terraform-alicloud-sag: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-sag': error running /usr/bin/git: ; error syncing template terraform-alicloud-service-linked-role: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-service-linked-role': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpn-pbr-route-entry: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpn-pbr-route-entry': error running /usr/bin/git: ; error syncing template terraform-alicloud-oss-object: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-oss-object': /usr/bin/git exited with -1: Cloning into '/tmp/seal-template-boXMsQBcVD'...
; error syncing template terraform-alicloud-mongodb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-mongodb': error running /usr/bin/git: ; error syncing template terraform-alicloud-autoscaling-rule: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-autoscaling-rule': error running /usr/bin/git: ; error syncing template terraform-alicloud-mongodb-sharding: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-mongodb-sharding': error running /usr/bin/git: ; error syncing template terraform-alicloud-ram-user: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ram-user': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecs-bare-metal-instance: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecs-bare-metal-instance': error running /usr/bin/git: ; error syncing template terraform-alicloud-dnat: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-dnat': error running /usr/bin/git: ; error syncing template terraform-alicloud-edas: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-edas': error running /usr/bin/git: ; error syncing template terraform-alicloud-ess-scaling-rule: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ess-scaling-rule': error running /usr/bin/git: ; error syncing template terraform-alicloud-eip-slb-ecs-rds: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eip-slb-ecs-rds': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-ecs-rds-slb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-ecs-rds-slb': error running /usr/bin/git: ; error syncing template terraform-alicloud-ram-fc: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ram-fc': error running /usr/bin/git: ; error syncing template terraform-alicloud-msc-subscription: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-msc-subscription': error running /usr/bin/git: ; error syncing template terraform-alicloud-landing-zone-cloud-sso-multi-account-policy: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-landing-zone-cloud-sso-multi-account-policy': error running /usr/bin/git: ; error syncing template terraform-alicloud-mybase: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-mybase': error running /usr/bin/git: ; error syncing template terraform-alicloud-mse: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-mse': error running /usr/bin/git: ; error syncing template terraform-alicloud-hbr-ecs: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-hbr-ecs': error running /usr/bin/git: ; error syncing template terraform-alicloud-ess-alb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ess-alb': error running /usr/bin/git: ; error syncing template terraform-alicloud-landing-zone-guardrails: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-landing-zone-guardrails': error running /usr/bin/git: ; error syncing template terraform-alicloud-dns: context deadline exceeded; error syncing template terraform-alicloud-mns-topic: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-mns-topic': error running /usr/bin/git: ; error syncing template terraform-alicloud-drds: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-drds': error running /usr/bin/git: ; error syncing template terraform-alicloud-best-practice-084: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-best-practice-084': error running /usr/bin/git: ; error syncing template terraform-alicloud-kubernetes-networking: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-kubernetes-networking': error running /usr/bin/git: ; error syncing template terraform-alicloud-memcache: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-memcache': error running /usr/bin/git: ; error syncing template terraform-alicloud-ecs-spot-instance: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ecs-spot-instance': error running /usr/bin/git: ; error syncing template terraform-alicloud-market-app-on-autoscaling: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-market-app-on-autoscaling': error running /usr/bin/git: ; error syncing template terraform-alicloud-cassandra: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cassandra': error running /usr/bin/git: ; error syncing template terraform-alicloud-adb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-adb': error running /usr/bin/git: ; error syncing template terraform-alicloud-eip-slb-ecs-redis-rds: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eip-slb-ecs-redis-rds': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-slb-ecs-rds-drds: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-slb-ecs-rds-drds': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-ecs-eip: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-ecs-eip': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-click-house-cluster-account: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-click-house-cluster-account': error running /usr/bin/git: ; error syncing template terraform-alicloud-eip-anycast: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eip-anycast': error running /usr/bin/git: ; error syncing template terraform-alicloud-clickhouse: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-clickhouse': error running /usr/bin/git: ; error syncing template terraform-alicloud-oos: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-oos': error running /usr/bin/git: ; error syncing template terraform-alicloud-hbr-oss: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-hbr-oss': error running /usr/bin/git: ; error syncing template terraform-alicloud-bastionhost: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-bastionhost': error running /usr/bin/git: ; error syncing template terraform-alicloud-landing-zone-log-archive: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-landing-zone-log-archive': error running /usr/bin/git: ; error syncing template terraform-alicloud-disk: context deadline exceeded; error syncing template terraform-alicloud-oss-bucket: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-oss-bucket': error running /usr/bin/git: ; error syncing template terraform-alicloud-actiontrail: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-actiontrail': error running /usr/bin/git: ; error syncing template terraform-alicloud-remote-backend: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-remote-backend': error running /usr/bin/git: ; error syncing template terraform-alicloud-emr-druid: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-emr-druid': error running /usr/bin/git: ; error syncing template terraform-alicloud-hbase: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-hbase': error running /usr/bin/git: ; error syncing template terraform-alicloud-market-jenkins: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-market-jenkins': error running /usr/bin/git: ; error syncing template terraform-alicloud-snat: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-snat': error running /usr/bin/git: ; error syncing template terraform-alicloud-maxcompute-project: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-maxcompute-project': error running /usr/bin/git: ; error syncing template terraform-alicloud-slb-rule: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-slb-rule': error running /usr/bin/git: ; error syncing template terraform-alicloud-mongodb-multi: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-mongodb-multi': error running /usr/bin/git: ; error syncing template terraform-alicloud-rocketmq-redis: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-rocketmq-redis': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-ecs: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-ecs': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-log-flows: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-log-flows': error running /usr/bin/git: ; error syncing template terraform-alicloud-cloud-sso-user: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cloud-sso-user': error running /usr/bin/git: ; error syncing template terraform-alicloud-hdfs: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-hdfs': error running /usr/bin/git: ; error syncing template terraform-alicloud-global-accelerator: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-global-accelerator': error running /usr/bin/git: ; error syncing template terraform-alicloud-service-mesh: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-service-mesh': error running /usr/bin/git: ; error syncing template terraform-alicloud-ess-clb: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ess-clb': error running /usr/bin/git: ; error syncing template terraform-alicloud-landing-zone-resource-structure: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-landing-zone-resource-structure': error running /usr/bin/git: ; error syncing template terraform-alicloud-mns-queue: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-mns-queue': /usr/bin/git exited with -1: Cloning into '/tmp/seal-template-Fwo3sXVnnE'...
; error syncing template terraform-alicloud-cen-instance: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-cen-instance': error running /usr/bin/git: ; error syncing template terraform-alicloud-demo: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-demo': error running /usr/bin/git: ; error syncing template terraform-alicloud-emr-hadoop: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-emr-hadoop': error running /usr/bin/git: ; error syncing template terraform-alicloud-ram-role: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-ram-role': error running /usr/bin/git: ; error syncing template terraform-alicloud-network-with-security-group: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-network-with-security-group': error running /usr/bin/git: ; error syncing template terraform-alicloud-slb-udp: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-slb-udp': error running /usr/bin/git: ; error syncing template terraform-alicloud-vpc-peering: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-vpc-peering': error running /usr/bin/git: ; error syncing template terraform-alicloud-demo-test: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-demo-test': error running /usr/bin/git: ; error syncing template terraform-alicloud-scdn: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-scdn': error running /usr/bin/git: ; error syncing template terraform-alicloud-amqp-ram-cloudmonitor: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-amqp-ram-cloudmonitor': error running /usr/bin/git: ; error syncing template terraform-alicloud-control-policy: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-control-policy': error running /usr/bin/git: ; error syncing template terraform-alicloud-kafka: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-kafka': error running /usr/bin/git: ; error syncing template terraform-alicloud-kms-alias: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-kms-alias': error running /usr/bin/git: ; error syncing template terraform-alicloud-alb-server-group: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-alb-server-group': error running /usr/bin/git: ; error syncing template terraform-alicloud-eci: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-eci': error running /usr/bin/git: ; error syncing template terraform-alicloud-simple-application-server: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-simple-application-server': error running /usr/bin/git: ; error syncing template terraform-alicloud-enable: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-enable': error running /usr/bin/git: ; error syncing template terraform-alicloud-acr-personal: error downloading 'https://github.com/terraform-alicloud-modules/terraform-alicloud-acr-personal': error running /usr/bin/git:
2023-09-07T10:43:00.597Z	W	task	error executing: error syncing templates of catalog 477242801281627906: failed to update sync info: context deadline exceeded	{"createBy": "CatalogTemplateSyncCronExpr"}

Just started synchronizing templates, but immediately reported context deadline exceeded.

2023-09-07T11:13:01.665Z	D	task	syncing templates of catalog "477058412413248514"	{"createdBy": "CatalogTemplateSyncCronExpr"}
2023-09-07T11:13:01.665Z	W	task	error executing: error syncing templates of catalog 477399475380344322: failed to update sync info: context deadline exceeded; context deadline exceeded	{"createBy": "CatalogTemplateSyncCronExpr"}

Environment

Walrus version: main ed21adcc5770196dc4a5654502d4a98a0987a631

Test Result: Cannot reproduce in latest version.

authors: Finenyaco alexcodelf

repo: seal-io/walrus


text:
The value of map(string) variable is not shown on service detail page

Describe the bug

The value of map(spring) variable is not shown on service detail page
Steps to reproduce

Using kubernetes-containerservice template to create a service with the configuration as shown below:

Go to the service details page and check the template configuration.

Result

The value of map(string) is not displayed. Checked the api response that has returned the value.

Expected behavior

Display the complete configuration
Environment

Walrus version: v0.4.0

Additional context
Add any other context about the problem here.

Environment

Walrus version: v0.4.0
UI version: dev-43aa2a1

Test Result:  Failed
It didn't show the basic configuration.


text:
Failed to deploy resource using docker tempaltes

Describe the bug

Steps to reproduce

Setup walrus using docker mode.
Create a resource using docker-contianerservice template v0.2.1.

Result

Expected behavior

Failed to deploy: invalid variables: violate ui schema: not found required values [infrastructure]

Environment

Walrus version: dev-38bbd2a
UI version: dev-d90cfe2

Additional context
Add any other context about the problem here.
Other docker templates with the latest version also have this issue.

Environment

Template version: v0.2.2

Test Result:

containerservice: blocked by https://github.com/seal-io/walrus/issues/1833

mysql: pass

postgresql: pass

redis: pass

Environment

Walrus version: main 1e59b4feaae335bfa20cbfa170908396806ca7b5
UI version: dev-437b352

Test Result:

containerservice: pass


text:
Update build configuration

The build configuration of this project is outdated and may no longer work.
This pull request will be merged automatically if there are no conflicts.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: sealsystems/node-assert-mongo-error


text:
chore: update connect-service

Details
https://sealsystems.atlassian.net/browse/PLS-1771
Breaking Changes
References
Introduction to Pull Requests

Please read before submitting your first pull request!

Thank you for creating a pull request. We really appreciate your effort!
Here is some information to help you integrate your changes as easily as possible into the next release.
Title Field
The title is one of the most important parts of a pull request. The content is shown in CHANGELOG.md and release notes. Therefore, be sure to summarize your changes in a short but catchy sentence. Others should be able to easily get an idea of your changes.
By adding keywords at the beginning of the title, you can control the process of merging and releasing your pull request. Here is the list of all available keywords:

WIP:
It is highly recommended to open a pull request as soon as possible. This allows discussions during code development and not just criticism after work is done.
Please start a new pull request with the prefix WIP:. This signals to others that is is not yet ready to be merged into the master branch. It also prevents our bot from merging. (See section "Merging into Master" below)
After the changes and the pull request description have been completed, remove this prefix. In this case, review requests may be automatically generated to ensure, e.g., the compatibility of your description with our release notes format.

feat:
A pull request with this prefix in its title is marked as a new feature. In general this creates a minor release when merging the pull request into the master branch. A label with the expected release type is added to the pull request.

fix:
A pull request with this prefix in its title is marked as a bugfix. In general this creates a patch release when merging the pull request into the master branch. A label with the expected release type is added to the pull request.

chore:
A pull request with this prefix in its title is marked as a maintenance change. In general this creates a patch release when merging the pull request into the master branch. A label with the expected release type is added to the pull request. Only CHANGELOG.md, but not our release notes, will be updated with information about the pull request.

You can specify the kind of pull request when you create a new one. But do not forget to prefix it with WIP:. Here is an example title for such a pull request:
WIP: feat: My super cool new feature

After finishing the work, you can simply remove WIP:.
Please do not format the Title field with Markdown.
Description Field
Besides this introduction, the description field also contains sections with the following headings which contribute to CHANGELOG.md and release notes:

Details
Sometimes it is not possible to explain a change with a single short line in the Title field. In this case, you can add a more detailed description in the Details section.
You may add several paragraphs if needed and unlike the Title field, you can format the content with Markdown.

Breaking Changes
Please fill out this section if and only if your changes affect the public Interface. This creates a major release when merging the pull request into the master branch. Breaking changes are shown in an additional section of CHANGELOG.md and release notes. So two headings will be created: One for the bugfix/feature itself and one for the breaking changes.
All information for the Details section also applies here, with one important exception:
In contrast to the Details section, the first line is used as a title for the breaking change. Therefore, please add a short description first and append paragraphs for more information if needed. Do not start with a large paragraph and do not format the first line.
Here is an example of a longer text for a breaking change:

This is a brief description of the breaking change (without a punctuation mark and formatting)
In another paragraph, I add detailed information of steps needed to adapt to the new interface. I can also format this paragraph using Markdown.
I can add as many paragraphs as needed.

The first line is shown as a heading and the following paragraphs as normal text.
Use this section only to describe changes to the interface and how to adapt to the new version. Use the Details section to provide information about the bugfix/feature itself.

References
Here you can enter links to Jira oder Github. This allows you to provide more information about the background of your code changes.
Add one link per line without any other text.

Please make sure that you leave a blank line between the headings and the beginning and end of your text.
Merging into Master
After all reviews have been successfully completed, you are ready to merge your pull request into the master branch. This is only possible if all required automated tests pass.
You cannot use the green "Merge" button. Instead you must add a special comment containing only the following command:
/merge

This causes our merge bot to merge the pull request using a commit message consisting of the various pieces of information in the Title and Description fields.
Only users with admin or write permissions are allowed to merge a pull request. The branch is automatically deleted after a successful merge.

/merge

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: comgit seal-rr

repo: sealsystems/node-request-service


text:
Error preparing statement.  Cause: io.seata.common.loader.EnhancedServiceNotFoundException: not found service provider for : io.seata.sqlparser.druid.SQLOperateRecognizerHolder

在mybatis查询数据时出现这个错误：
Error preparing statement.  Cause: io.seata.common.loader.EnhancedServiceNotFoundException: not found service provider for : io.seata.sqlparser.druid.SQLOperateRecognizerHolder

你好，楼主，请问问题解决了吗？我遇到和你一样的问题

切换成 最新版本的 seata server 就能搞定了

切换成 最新版本的 seata server 就能搞定了

我用的1.4.2，也报这个错，而且捕捉不到异常堆栈信息。
io.seata.common.loader.EnhancedServiceNotFoundException: not found service provider for : io.seata.sqlparser.druid.SQLOperateRecognizerHolder

authors: niaoshuai shanjia-sdu srg1556 wwkin

repo: seata/seata-samples


text:
consul1.4.1 has no class com.ecwid.consul.v1.health.HealthServicesRequest，but seata is used at ConsulRegistryServiceImpl.java

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

Ⅰ. Issue Description
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [io.seata.rm.datasource.DataSourceProxy]: Factory method 'dataSourceProxy' threw exception; nested exception is java.lang.NoClassDefFoundError: com/ecwid/consul/v1/health/HealthServicesRequest
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185) ~[spring-beans-5.1.5.RELEASE.jar:5.1.5.RELEASE]
at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:622) ~[spring-beans-5.1.5.RELEASE.jar:5.1.5.RELEASE]
... 146 common frames omitted
Caused by: java.lang.NoClassDefFoundError: com/ecwid/consul/v1/health/HealthServicesRequest
at io.seata.discovery.registry.consul.ConsulRegistryServiceImpl.getHealthyServices(ConsulRegistryServiceImpl.java:241) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.discovery.registry.consul.ConsulRegistryServiceImpl.refreshCluster(ConsulRegistryServiceImpl.java:268) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.discovery.registry.consul.ConsulRegistryServiceImpl.lookup(ConsulRegistryServiceImpl.java:156) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.core.rpc.netty.NettyClientChannelManager.getAvailServerList(NettyClientChannelManager.java:214) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.core.rpc.netty.NettyClientChannelManager.reconnect(NettyClientChannelManager.java:161) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.core.rpc.netty.RmRpcClient.registerResource(RmRpcClient.java:226) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.rm.AbstractResourceManager.registerResource(AbstractResourceManager.java:119) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.rm.datasource.DataSourceManager.registerResource(DataSourceManager.java:149) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.rm.DefaultResourceManager.registerResource(DefaultResourceManager.java:114) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.rm.datasource.DataSourceProxy.init(DataSourceProxy.java:87) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.rm.datasource.DataSourceProxy.(DataSourceProxy.java:76) ~[seata-all-0.8.0.jar:0.8.0]
at io.seata.rm.datasource.DataSourceProxy.(DataSourceProxy.java:65) ~[seata-all-0.8.0.jar:0.8.0]
at com.turtle.shop.service.store.service.SeataAutoConfig.dataSourceProxy(SeataAutoConfig.java:78) ~[classes/:na]
at com.turtle.shop.service.store.service.SeataAutoConfig$$EnhancerBySpringCGLIB$$a8f9cafa.CGLIB$dataSourceProxy$1() ~[classes/:na]
at com.turtle.shop.service.store.service.SeataAutoConfig$$EnhancerBySpringCGLIB$$a8f9cafa$$FastClassBySpringCGLIB$$a76afa21.invoke() ~[classes/:na]
at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244) ~[spring-core-5.1.5.RELEASE.jar:5.1.5.RELEASE]
at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:363) ~[spring-context-5.1.5.RELEASE.jar:5.1.5.RELEASE]
at com.turtle.shop.service.store.service.SeataAutoConfig$$EnhancerBySpringCGLIB$$a8f9cafa.dataSourceProxy() ~[classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_172]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_172]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_172]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_172]
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154) ~[spring-beans-5.1.5.RELEASE.jar:5.1.5.RELEASE]
... 147 common frames omitted
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version :1.8
OS :win10
seata:0.8.0
consul 1.4.1

Thank you

repo: seata/seata


text:
bugfix: fix the other of column type cause rollback fail

Ⅰ. Describe what this PR did
Oracle Driver dose not support the other type of column
Ⅱ. Does this pull request fix one issue?
#1831
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1863 into develop will increase coverage by 0.01%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             develop    #1863      +/-   ##
=============================================
+ Coverage      55.04%   55.05%   +0.01%
  Complexity      2353     2353
=============================================
  Files            422      422
  Lines          14273    14274       +1
  Branches        1712     1713       +1
=============================================
+ Hits            7856     7859       +3
+ Misses          5686     5684       -2
  Partials         731      731

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/io/seata/common/util/LambdaUtils.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...seata/rm/datasource/undo/AbstractUndoExecutor.java
74.33% <0%> (-0.67%)
21 <0> (ø)

...server/store/file/FileTransactionStoreManager.java
60.19% <0%> (+0.98%)
29% <0%> (ø)
:arrow_down:


text:
Implement path validation when inserting new questions

Describe the solution you'd like
The QuestionService states that create "will fail if he path provided already resolves to a QuestionDefinition or Scalar." We need to implement this logic in the service implementation
Done when
A new question insertion fails when the path already exists

M1 Review - Not worked on

authors: carolinedanzi lianne-oy

repo: seattle-uat/universal-application-tool


text:
Use bin/fmt instead of third party action

Description
Third party action suddenly broke on us - use our own.
Checklist

[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Closed in favor of #169.


text:
Can not upgrade from 2.xx to 3.xx

Describe the bug
I1227 07:33:51.513225 volume_grpc_client_to_master.go:43 checkWithMaster localhost:9333: get master localhost:9333 configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: context deadline exceeded"
I1227 07:34:13.307527 volume_grpc_client_to_master.go:43 checkWithMaster localhost:9333: get master localhost:9333 configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: context deadline exceeded"

I couldn't Seaweedfs upgrade from 2.xx to 3.xx
System Setup
This is my command:
sudo docker run --name weed_master11 --restart always -d \
--net=host \
-p 9333:9333 -p 19333:19333 \
-v /home/seaweedfs/certs/weed:/etc/seaweedfs/certs \
-v /home/seaweedfs/data/master:/data/seaweedfs/master \
-v /home/seaweedfs/security.toml:/etc/seaweedfs/security.toml \
chrislusf/seaweedfs master -mdir=/data/seaweedfs/master \
-ip=(curl -s https://ipinfo.io/ip) \
-defaultReplication=010

sudo docker run --name weed_volume11 --restart always -d \
--net=host \
-p 8080:8080 -p 18080:18080 \
-v /home/seaweedfs/data/volume:/data/seaweedfs/volume \
-v /home/seaweedfs/security.toml:/etc/seaweedfs/security.toml \
-v /home/seaweedfs/certs/weed:/etc/seaweedfs/certs \
chrislusf/seaweedfs volume -dataCenter=dc1 -rack=rack1 -dir=/data/seaweedfs/volume -max=0 \
-ip=(curl -s https://ipinfo.io/ip) \
-mserver=localhost:9333

sudo docker run --name weed_filer11 --restart always -d \
--net=host \
-p 8888:8888 -p 18888:18888 -p 8333:8333 \
-v /home/seaweedfs/s3config.json:/s3config.json \
-v /home/seaweedfs/filer.toml:/etc/seaweedfs/filer.toml \
-v /home/seaweedfs/filer.conf:/etc/seaweedfs/filer.conf \
-v /home/seaweedfs/data/filer:/data/ \
-v /home/seaweedfs/security.toml:/etc/seaweedfs/security.toml \
-v /home/seaweedfs/certs/weed:/etc/seaweedfs/certs \
chrislusf/seaweedfs filer -s3 -s3.config=/s3config.json \
-ip=(curl -s https://ipinfo.io/ip) \
-master=localhost:9333

ubuntu 20.04
Can not use command weed shell. It looks like we can't connect to weed master
It works fine when I downgraded to the old version (8 months ago).

I mounted the wrong certs directory, and it is weird when I could install it completely with version 2.xx.

repo: seaweedfs/seaweedfs


text:
Dropdown: Multiselect checkmark is not displaying properly

Bug already reported?

[X] I confirm that I have checked if the bug already has been reported

For which framework/library you are reporting the bug
Core
Component name
dropdown
Description
Can be reproduced in storybook:
https://storybook.seb.io/latest/core/?path=/story/components-dropdown--multiple
Steps To Reproduce
https://storybook.seb.io/latest/core/?path=/story/components-dropdown--multiple
Current Behaviour
When selecting an option checkmark icon is not displayed but just a black box that also makes the checkbox wider
Expected Behaviour
Checkbox icon showing

version 1.56.0

Seems to be working in version 1.58.0

Same behavior is back in 1.60.1

repo: seb-oss/green


text:
MISSING_GLOBAL_NAME when used with LitElement

When I try to use LitElement in a project i get the following error at build time:
- No name was provided for external module 'lit-element' in output.globals – guessing 'litElement' [MISSING_GLOBAL_NAME]
This result in my web components not intializing correctly
full output:
$ preppy --watch --entry-lib=src/test.ts --entry-browser=src/test.ts --verbose
Flags: { watch: true,
  exec: false,
  sourcemap: true,
  notify: false,
  verbose: true,
  quiet: false,
  entryLib: 'src/test.ts',
  entryBrowser: 'src/test.ts',
  entryNode: null,
  entryCli: null,
  root: '/Users/florian/Dev/perso/lib',
  output: null,
  limit: null }
Entries:
- library: src/test.ts
- browser: src/test.ts
- binaries: null
Watching lib-0.0.1...
★ Added: src/test.ts [LIB] ❯ lib/index.esm.js [ESM]
★ Added: src/test.ts [LIB] ❯ lib/index.cjs.js [CJS]
★ Added: src/test.ts [LIB] ❯ lib/index.umd.min.js [UMD]
Variables: {
  "process.env.BUNDLE_NAME": "lib",
  "process.env.BUNDLE_VERSION": "0.0.1",
  "process.env.BUNDLE_TARGET": "lib"
}
Variables: {
  "process.env.BUNDLE_NAME": "lib",
  "process.env.BUNDLE_VERSION": "0.0.1",
  "process.env.BUNDLE_TARGET": "lib"
}
Variables: {
  "process.env.BUNDLE_NAME": "lib",
  "process.env.BUNDLE_VERSION": "0.0.1",
  "process.env.BUNDLE_TARGET": "lib"
}
✔ Written: lib/index.esm.js in 561ms [4.9 kB]
✔ Written: lib/index.cjs.js in 117ms [5.14 kB]
  - No name was provided for external module 'lit-element' in output.globals – guessing 'litElement' [MISSING_GLOBAL_NAME]
✔ Written: lib/index.umd.min.js in 694ms [3.74 kB]

package json:
{
    "name"           : "lib",
    "version"        : "0.0.1",
    "description"    : "my lib",
    "main"           : "lib/index.cjs.js",
    "module"         : "lib/index.esm.js",
    "unpkg"          : "lib/index.umd.min.js",
    "types"          : "lib/index.d.ts",
    "scripts"        : {},
    "author"         : "",
    "license"        : "ISC",
    "devDependencies": {
        "@babel/core"                            : "^7.6.0",
        "@babel/plugin-proposal-class-properties": "^7.5.5",
        "@babel/plugin-proposal-decorators"      : "^7.6.0",
        "@babel/plugin-transform-runtime"        : "^7.6.0",
        "@babel/preset-env"                      : "^7.6.0",
        "@babel/preset-typescript"               : "^7.6.0",
        "@babel/runtime"                         : "^7.6.0",
        "corejs"                                 : "^1.0.0",
        "es-dev-server"                          : "^1.17.2",
        "es-module-shims"                        : "^0.4.2",
        "lit-element"                            : "^2.2.1",
        "preppy"                                 : "^8.3.1",
        "typescript"                             : "^3.6.2"
    }
}

Not sure what the issue is here. Preppy do not inline external libraries by default. There is a new "deep" mode in the last release which adds this. In other cases for UMD builds (this issue in only reported while building the UMD), you somehow have to make this component available. I am not a massive user of these UMD approaches myself. If you like to improve the implementation I am happy to work together on PRs.

authors: swernerx zenwork

repo: sebastian-software/preppy


text:
Open last file upon application startup

When user opens the application, the last file that was worked on could get automatically opened. If the file does not exist anymore or if it's the first run, simply do not display anything.

Will take this if it's not already taken.

@rbanna01 sure, feel free to take it

@sebbrudzinski Think it's ready for testing.

@rbanna01 - where is the commit/commits? I cannot see any new pull request.

@sebbrudzinski Sorry, should be up now.

@sebbrudzinski
Does this item still exist? If this has not been resolved, may I take to work?  :D

@WhiteHsu It still hasn't been implemented so you are free to take it

@sebbrudzinski
Sorry to reply late because being so busy recently. I'll study codes and plan to start my work on this item on these days. Thank you.  :-)

@sebbrudzinski
I'm investigating how to implement this feature and think there should be a place to keep information of the last opened file. After studying the class "OpenFile.java", I find we originally keep the "Last Dir" in the property file "settings.properties". So may I also keep the "Last Opened File" information here? Or do you recommend other ways to do this?

@WhiteHsu Sounds good to me

@sebbrudzinski
Please kindly help review my codes and provide your valuable feedback. Thank you very much.  :-)

@sebbrudzinski
I've updated codes again based on the latest project version. Please kindly help review. Thank you very much. :-)

Fixed by @WhiteHsu   Thanks!

authors: WhiteHsu rbanna01 sebbrudzinski

repo: sebbrudzinski/Open-LaTeX-Studio

license: mit


text:
Add remote connection detection

Is your feature request related to a problem? Please describe.
Sometimes people use our apps in a remote environment through a remote session (e.g. RDP). We would like to detect and warn users when they do.
Describe the solution you'd like
Simply a flag to detect if you are running the application in a remote session.
Describe alternatives you've considered
None
Additional context
Windows provides this flag using GetSystemMetric syscall with SM_REMOTESESSION.
https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getsystemmetrics
Flag: SM_REMOTESESSION

@DanielMcAssey as far as I have seen in my investigation, this is only possible by writing an C++ extension. I currently do not plan to do that, this would a more complex installing process for some users. Fo Linux machines I found an easy solution but not for windows. If you have further suggestions, please post it here.

Maybe a Powershell solution?
https://stackoverflow.com/a/28678312/1032384

@DanielMcAssey @AdrianoCahete ... just added this to osInfo(). Version 5.3.0 just released.

repo: sebhildebrandt/systeminformation


text:
use spawnSync instead of execSync

in Raspiberry pi with 32bit OS, there is no problem. This library works fine!
But with arm64 OS, i have Error: EFAULT write but the result is still displayed
I replaced execSync with spawnSync (part of child_process)  and now no errors are displayed and result works too.
Tested on ubuntu: ok
Tested on Raspberry pi 4 arm64: ok
npm run test: ok

related to https://github.com/sebhildebrandt/systeminformation/issues/873#issuecomment-1890948800

finaly not help really :/


text:
Getting Started with Image Preprocessing in python

Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.
[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
This fixes #3188

Hello @FREDERICO23. There are several grammatical errors and many paragraphs that are tough to comprehend. Kindly check and change them. Once done, ping me.

plagiarism check done

@lalith1403 Revisions done

Changes Done

Hello @FREDERICO23. I had made a lot of changes in the earlier commit. You have updated the changes without pulling my changes. Please can you consider pulling the changes made in my commit and then push your changes.

@lalith1403
Can we get a status on this PR

Nice article @FREDERICO23. Good review @lalith1403

Merged #3306


text:
feat: Enable E2E tests in RHTAP for rekor

Adds the tasks and changes needed to support E2E tests in RHTAP,
Comments
Marking this pr as draft until changes are in main

/test all

/retest

/retest

/retest

@JasonPowr is this still a WIP?

Needs a bit of work after the path updates

/retest

This is all goo now ran into some issues with paths, permissions and auth, but as you can see its running and passing now https://console.redhat.com/preview/application-pipeline/workspaces/rhtas/applications/rhtas-stack-1-0-beta/pipelineruns/rekor-server-on-pull-request-p8f5p

authors: JasonPowr lance

repo: securesign/rekor


text:
Auto reload of networks mapping file

It would make sense to trigger via:

SIGHUP
http request (needs #1)
automatically when file changes

SIGHUP is implemented


text:
test: :white_check_mark: test migrations

Description
This PR DESCRIBE CHANGES.
Closes #

This PR needs a quick/an in-depth review.
Checklist

[ ] Added or updated tests
[ ] Tests passed locally
[ ] Linted and formatted code
[ ] Build passed locally
[ ] Updated documentation

😿

repo: seedcase-project/seedcase-sprout


text:
Other Request Example

I am creating the both and oauth2 server side. From what I understand there is an intercepter which adds necessary headers for oauth2 request. The code is working fine when I do
OAuth.getAccessToken();
I get the access token and everything works as expected. but when I try to access resource I get error. This is the code
$http.get( SERVER_CONFIG.baseUrl +  '/api/resource/' ).success(function (data) {
                res(data);
            })

It says CORS error, CORS header 'Access-Control-Allow-Origin' missing. I think this not the error with the server CORS headers because when I change the grant url in the config or change the source course itself
return $http.post("" + config.baseUrl + "" + config.grantPath, data,    options).then(function(response) {
                            OAuthToken.token = response.data;
                            return response;
                        });

to the resource url, it works fine and I get the resource, the OAuth is working an there is no CORS request error
So my question is do I need to make any changes to make the resource urls to work?
I know this is out of the scpoe of this plugin but any help is appreciated. I have spent a lot of time on this and to no avail.

it seems that the issue is with $q when I removed that from the code the api is being hit and I am getting the request from the server. I am wondering not what was the issue with $q.

Not sure if I understand the issue. Closing for now but please reopen with sample code if needed.

authors: developernaren ruipenso


text:
Chainlink CCIP integration with QR code dapp and Decentralized platform for incident reporting and summarization by citizens.

Ticket Contents
Description
We need to Create a Dapp (qr-code scanner ) with CCIP incident NFT's.
###Steps involved are :
1.Deploy and test the CCIP smart contract.
2.create Frontend Dapp which involves
a. qr scanner functionality
b. incident reporting page
c. Ipfs integration to store ccip nft metadata
d. ccip nft minting (contract Integration)
Product Name
incident ccip qr-code Daap
Organisation Name
NSUT in collaboration with C4GT, SEETA and AIC
Domain
Healthcare
Tech Skills Needed
React, RESTful APIs, Solidity, Tailwind CSS
Mentor(s)
@manusheel
Category
development

https://github.com/seetadev/ParkGHO-Family/issues/1

#4
#6
#1

#6
#4
#1

repo: seetadev/ParkGHO-Family


text:
React 15.5+ deprecates PropTypes and createClass

As of React 15.5 React.PropTypes and React.createClass are deprecated. react-wufoo-embed should move to prop-types and ES6 classes. Also the examples are out of date with React and should now be updated to use ReactDOM to render the Wufoo example.

#5 Fixes this.

Thanks so much for doing this @cwardzala .  Really happy to update this on npm as well.

https://www.npmjs.com/package/react-wufoo-embed bumped to major release to start using semver.
Thanks again.

authors: cwardzala seethroughtrees

repo: seethroughtrees/react-wufoo-embed


text:
TimeoutException after 0:00:02.000000: Future not completed

Dear when i try to connect with server i am getting "TimeoutException after 0:00:02.000000: Future not completed" issue , please check it and if working with you then please advise how can i fix this.
Note: I am using emulator and due to that reason i am accessing the localhost with ip: 10.0.2.2

Hello!  I am experiencing the same issue, have you been able to resolve this?

Hello, I've been looking at the source code, and I actually found a default timeout of 2000ms in http_connection.dart
Maybe this value can be exposed in http_connection_options.dart so you can change this limit.

@RazMuhammadAfridi  Hi, I am facing the same issue, have you any solution for it?

Thanks Luke, pull request has been merged and published.
I am going to close this issue.


text:
support hide default launcher

for: https://segment.atlassian.net/browse/INT-529
docs: https://docs.intercom.io/configure-intercom-for-your-product-or-site/customize-the-intercom-messenger/customize-the-intercom-messenger-technical#show-the-intercom-messenger-to-selected-users-for-web-
basically lets you use Intercom's hide_default_launcher option anytime you update the user. This will let them hide the messenger using intercom's native features rather than our existing recommendation of straight up disable a given call via selective integration which is not as good as this since you can still update user/group traits without losing that data inside intercom.
docs pr to go along with it: https://github.com/segmentio/site-docs/pull/1784
@WesleyDRobinson @f2prateek

Not sure how this flag is typically used, but I think it might be better to have users call the intercom API directly in this case?
i..e instead of:
analytics.identify('prateek', {email: 'prateek@segment.com'}, { context: { Intercom: { hideDefaultLauncher: true }}});

do:
analytics.identify('prateek', {email: 'prateek@segment.com'});
window.Intercom.set(hideDefaultLauncher: true);

Is that feasible?

@f2prateek I'd rather not have them use outside of segment. They also don't have a dandy set api but you have to push to their queue with other properties like appId etc, so the flag approach is more optimal an consistent with how we've been supporting their other features like secure mode and unsubscribe from emails.

Ok sgtm!


text:
How to keep the schema field same order as struct?

Hello,
I have a table already in redshift, I need to keep the same schema (even the order of the fields) to load parquet to redshift.
However I found the library creates the schema based on the struct and sorts the key. what I need is to keep the schema field same order as we defined in struct.
In redshift I have:
Schema: message test {
  required binary b (STRING);
  required int32 a (INT(32, true));
  required binary c (STRING);
}

The defined struct:
	type Test struct {
		B string `parquet:"b,plain,gzip"`
		A string `parquet:"a,plain,gzip"`
		C string `parquet:"c,plain,gzip"`
	}

its generated schema:
Schema: message Test {
  required binary a (STRING);
  required binary b (STRING);
  required binary c (STRING);
}

Is there any way to do that?

I have found the problem, in schema.go
func structFieldsOf(t reflect.Type) []reflect.StructField {
  fields := appendStructFields(t, nil, nil)

  for i := range fields {
    f := &fields[i]

    if tag := f.Tag.Get("parquet"); tag != "" {
      name, _ := split(tag)
      if name != "" {
        f.Name = name
      }
    }
  }

  /*  sort.Slice(fields, func(i, j int) bool {
      return fields[i].Name < fields[j].Name
    })
  */
  return fields
}

func (s *structNode) indexOf(name string) int {
  for i, n := range s.names {
    if name == n {
      return i
    }
  }
  return -1

/*
  i := sort.Search(len(s.names), func(i int) bool {
    return s.names[i] >= name
  })
  if i == len(s.names) || s.names[i] != name {
    i = -1
  }
  return i
  */
}

the schema names has been ordered for binary search, however in some cases we need to keep the order as we defined in structure, thus we should not order it.
I comment the two section code, then I get the order that I wanted.

This is currently done this way "by design", and assumed in many places in the code.
Do you mind explaining what the use case is that requires fields to be in the same order as the Go struct?

@achille-roussel
we have already tables very big in redshift, and we changed the loaded data format from csv.gz to parquet, thus we need to keep the structure the same as defined in redshift.
I think in some cases we need to keep the order, it would be nice if we can choose not to sort the fields even that would lead some performance loss.

The design decision of sorting columns of the schema has been depended upon throughout the code, so it seems like a risky choice to change. That being said, I would be against reviewing and accepting a pull request which makes it possible to retain the order of columns, I just want to warn that it may be a complex change to get right.
Have you considered keeping a mapping externally within the application; I'm probably oversimplifying but I could imagine like having a map[string]int which dictates the relationship between the column name and its position in the database may allow the application to do the conversion? I don't have a lot of context on how parquet-go and Redshift interact in your case tho, so please disregard if this is not a good advise.

@achille-roussel
I just tried to read the parquet file that I wrote with keeping the order, it doesn't work and I come to realize that what you said here.
so the need of keeping struct fields order does exist,  the AWS Redshift load the parquet file based on the fields order not the column name, and what I did (comment sort code) broke the read.
instead of maintaining a map of orders outside the library, I prefer to specifying the order in the annotation, but I am not sure if would be possible, anyway we need a solution for keeping fields in order even if the solution is not perfect.

Thanks for the extra details, I see how that's more constraining if Reshift is the limiting factor here.
If we need to dictate the order of columns in the final file, maybe we can come up with a change which sets the column order at serialization time, even if in memory we continue to use schemas with columns sorted by name, do you think that could work?

yes, I think it should work.

Hello @seaguest,
I opened https://github.com/segmentio/parquet-go/pull/140 which relaxes the requirement to sort columns by name in the parquet schema. The column order of structs that the schema is derived from will now be respected, as well as the order of columns in memory when reading parquet files.
If you have time to test it, your feedback will be valuable to understand whether it addresses your original issue.
Let me know!

sorry for my late update.
I tested with the latest code, it does solve the order problem and doesn't need any code change on my side, excellent work!

authors: achille-roussel seaguest

repo: segmentio/parquet-go


text:
AWS Athena's = not working for string

Hello,
When I made a parquet file and uploaded to S3 and run in Athena with following query, Athena returns nothing even it exists in reality.
select id_str from dummy1 where id_str = '1064572a7aa5d023a0455b956668b179'

Is there any way to handle it?
Detail
I made a parquet file with below code.
func main() {
	type segmentio struct {
		Name  string `parquet:"name"`
		IDStr string `parquet:"id_str"`
	}
	ss := []segmentio{
		{Name: "segmentio", IDStr: "1064572a7aa5d023a0455b956668b179"},
	}

	if err := parquet.WriteFile("p_segmentio.bin", ss); err != nil {
		panic(err)
	}
}

And I made a table in AWS Athena (trino compatibl) and uploaded the made file to S3.
CREATE EXTERNAL TABLE `dummy1`(
  `name` string,
  `id_str` string)
ROW FORMAT SERDE
  'org.apache.hadoop.hive.ql.io.parquet.serde.ParquetHiveSerDe'
STORED AS INPUTFORMAT
  'org.apache.hadoop.hive.ql.io.parquet.MapredParquetInputFormat'
OUTPUTFORMAT
  'org.apache.hadoop.hive.ql.io.parquet.MapredParquetOutputFormat'
LOCATION
  's3://${BUCKET}/aaa'

Then, I wanted the where id_str = '1064572a7aa5d023a0455b956668b179' SQL matches one record but it didn't.
xitongsys/parquet-go works
For investigation, I did the same thing with https://github.com/xitongsys/parquet-go with below code,

func main() {
	type xitongsys struct {
		Name  string `parquet:"name=name, type=BYTE_ARRAY, convertedtype=UTF8"`
		IDStr string `parquet:"name=id_str, type=BYTE_ARRAY, convertedtype=UTF8"`
	}

	fw, err := local.NewLocalFileWriter("p_xitongsys.bin")
	if err != nil {
		panic(err)
	}
	pw, err := writer.NewParquetWriter(fw, new(xitongsys), 4)
	if err != nil {
		panic(err)
	}
	xx := xitongsys{Name: "xitongsys", IDStr: "1064572a7aa5d023a0455b956668b179"}
	if err = pw.Write(xx); err != nil {
		panic(err)
	}
	if err = pw.WriteStop(); err != nil {
		panic(err)
	}
	fw.Close()
}

After I uploaded it to the same directory and run the same query, I could get one record.
So, I think this is not the problem in Athena but in parquet file.
paquet-cli
I compared metadata of the two files with parquet-mr/parquet-cli and there is difference, I hope it helps you see my situation.
For segmentio/parquet-go,
File path:  p_segmentio.bin
Created by: github.com/segmentio/parquet-go version 0.0.0(build e1109e2f6a20)
Properties: (none)
Schema:
message segmentio {
  required binary name (STRING);
  required binary id_str (STRING);
}

Row group 0:  count: 1  107.00 B records  start: 4  total(compressed): 107 B total(uncompressed):107 B
--------------------------------------------------------------------------------
        type      encodings count     avg size   nulls   min / max
name    BINARY    _         1         42.00 B
id_str  BINARY    _         1         65.00 B

For xitongsys/parquet-go,
File path:  p_xitongsys.bin
Created by: parquet-go version latest
Properties: (none)
Schema:
message parquet_go_root {
  required binary name (STRING) = 0;
  required binary id_str (STRING) = 0;
}

Row group 0:  count: 1  275.00 B records  start: 4  total(compressed): 275 B total(uncompressed):271 B
--------------------------------------------------------------------------------
        type      encodings count     avg size   nulls   min / max
name    BINARY    S BB_     1         80.00 B    0       "xitongsys" / "xitongsys"
id_str  BINARY    S BB_     1         195.00 B   0       "1064572a7aa5d023a0455b956..." / "1064572a7aa5d023a0455b956..."

Thank you in advance.

@mrasu I tried to reproduce this with the latest commit (05ed5ed000b1) and the Athena query was successful for me. I see your file was written with version e1109e2f6a20 of parquet-go which is several versions behind. I recommend updating your go.mod to the latest version of parquet-go (05ed5ed000b1), rewriting and uploading the file to S3, recreating the table, and trying the query again.
I also did another experiment adding ,zstd" to the parquet struct tags, and queried that table fine with Athena too.
Here's the meta output of my file reproducing yours but with the latest build:
$ parquet meta p_segmentio.bin

File path:  p_segmentio.bin
Created by: github.com/segmentio/parquet-go version 0.0.0(build 05ed5ed000b1)
Properties: (none)
Schema:
message segmentio {
  required binary name (STRING);
  required binary id_str (STRING);
}

Row group 0:  count: 1  107.00 B records  start: 4  total(compressed): 107 B total(uncompressed):107 B
--------------------------------------------------------------------------------
        type      encodings count     avg size   nulls   min / max
name    BINARY    _         1         42.00 B            "segmentio" / "segmentio"
id_str  BINARY    _         1         65.00 B            "1064572a7aa5d023a0455b956..." / "1064572a7aa5d023a0455b956..."

@bartleyg
After upgrading to the latest version, it works. Thank you!

@mrasu awesome! 🎉

authors: bartleyg mrasu


text:
Rename immutable, mutable etc... to new names that are correct

UniqueIncremental Counter (Hyperloglog++)
Unique (CuckooFilter and possibly play with the idea of CuckooLogLog)
UniqueFrequency Counter (minCount)
UniqueExpiring (Sliding Hyperloglog)
Free (Just a plain +1 and -1 Counter)
Create enums for those to be used across the project

Proposal: dynamic and static?

Nope all are dynamic
Look at the readMe
—
Sent from Mailbox
On Mon, Aug 10, 2015 at 10:43 PM, Martin Pinto-Bazurco
notifications@github.com wrote:

Proposal: dynamic and static?
Reply to this email directly or view it on GitHub:
https://github.com/seiflotfy/counts/issues/6#issuecomment-129600912

flexible/inflexible?

authors: martinpinto seiflotfy

repo: seiflotfy/counts


text:
[Infrastructure] File Structure change

This PR contains a huge structure change to the repo. The project now has a packages route which contains the cli and core packages. The core package being the UI components and the CLI package being the CLI that can be used to add components to users projects.

Thanks for opening this PR. Here are some thoughts that we can discuss on how to move forward with this restructure :)
Icons
I would love to get rid of the icons.tsx file and rather use icons directly in the components. This would remove the necessity to have that file present and you'd only need to add another import in the package.json. I really love the Tabler Icons for this, since I had some issues with Lucide (didn't work with Kobalte the last time I tried).
We could either use solid-icons or @tabler/icons-solidjs directly.
Structure
I looked at all the other shadcn ui repos (Svelte, SolidJS, React) and I really love the idea of the monorepo using turbo (I'm open for suggestions since I haven't worked with monorepos before).
Then we could move all the solid-start stuff for the docs into apps/www and have the packages/cli as it is now.
I'd also like to move the components from packages/core to apps/www/registry where we could group them by style (default, new york) if we ever decide to offer those.
But as stated I'm completely open on this one I just thought it would be handy to have a similar structure to all the other projects to make it easier to contribute between each other (bug-fixes etc.)
CLI
I really love the use of the commander package for the cli commands. It keeps everything clear. I also like that you moved the commands into the index file and just kept the functionality in their own files.
But for the prompts I kinda like the chained version better especially with "prompts". It also feels similar to the builder style used by "commander".
clack group
import * as p from "@clack/prompts"

const options = await p.group({
  style: () =>
    p.select({
      message: `Which ${highlight("style")} would you like to use?`,
      // @ts-ignore
      options: styles.map((style) => ({
        label: style.label,
        value: style.name,
      })),
    }),
  tailwindBaseColor: () =>
    p.select({
      message: `Which color would you like to use as ${highlight(
        "base color"
      )}?`,
      // @ts-ignore
      options: baseColors.map((color) => ({
        label: color.label,
        value: color.name,
      })),
    }),
});

prompts
import prompts from "prompts"

const options = await prompts([
  {
    type: "select",
    name: "style",
    message: `Which ${highlight("style")} would you like to use?`,
    choices: styles.map((style) => ({
      title: style.label,
      value: style.name,
    })),
  },
  {
    type: "select",
    name: "tailwindBaseColor",
    message: `Which color would you like to use as ${highlight("base color")}?`,
    choices: baseColors.map((color) => ({
      title: color.label,
      value: color.name,
    })),
  },
]);

There might be more but this should be more than enough topics to discuss for the beginning :D
Thanks again for your effort :)

Validation
I would love to try valibot instead of zod. Mainly because of the smaller bundle size. But either of them is fine.
Package Name
Unfortunately all of those are already in use:

suc
solid-ui
solid-ui-components
shadcn-solid

But especially since we want to add the cli tool we need something recognizable that isn't already in use.

Structure
I'm also having the same thoughts about turning the project into a monorepo. I have created one or two monorepos myself but I wasn't really sure what the best practices are. So this could be a new opportunity to explore using turbo repo.
Having the same structure as other Shadcn-ui forks is a smart call.
CLI
I'm thinking of sticking with Clack for the CLI. It's pretty intuitive and is widely used and shipped. I used commander in the index.ts because the documentation on that offered more info on how to use it to read CLI command parameters, flags and other things.
So I think Commander top level to collect and parse parameters and flags, and Clack for the interactive interface is the way to go.
Validation / Naming
The name doesn't really matter right now, we can always add or remove a letter from the names that exist. Concerning Valibot and Zod, I haven't found a need to use them in anything that I've worked on in the past so I'll leave that up to you.

Sounds great.
I would say we should do the turborepo stuff in here, since it fits the overall theme auf "structure change".
Once it's set up on this branch I can merge all the new components and docs, so that everything is up to date.

Ok, I'll get the turbo repo setup today. I setup one earlier this week so it shouldn't take long

I started to switch all the icons used in the components to solid-icons/tb. This should make the install process easier, since the components are now standalone and we don't need the icons.tsx anymore.

Ok. I haven't had time recently so I haven't been all that active. Hopefully I'll have some time this weekend.

this is the errormessage from vercel:

Oh, I think you'll need to modify the build command now that we're using a monorepo. If you invite me to the vercel project I can set it up

I would love to get rid of the icons.tsx file and rather use icons directly in the components. This would remove the necessity to have that file present and you'd only need to add another import in the package.json. I really love the Tabler Icons for this, since I had some issues with Lucide (didn't work with Kobalte the last time I tried).
We could either use solid-icons or @tabler/icons-solidjs directly.
EDIT
Looks like @tabler/icons-solidjs causes the same issues as lucide. But solid-icons works fine. So that would be my suggestion for the future.

lucide-solid with kobalt works for me https://stackblitz.com/edit/solidjs-templates-zsw3mp?file=src%2FApp.tsx,src%2Findex.css

authors: jguddas michaelessiet sek-consulting

repo: sek-consulting/solid-ui-components


text:
Option to disable remove confirmation for tags

I am looking for a way to disable the remove confirmation for tags. Currently when I am using select2 with tags options set to true, I have to press the backspace key twice to remove a tag item, Is there a way instead of making the selection on first backspace press and remove on second, to simply remove the tag item on first backspace ?

Closing this off because of the lack of activity. If this is not fixed in 4.0, and you are interested in seeing it fixed, add a :+1: to the ticket to bring it to our attention.
If you can add additional details, that would also be useful.

authors: amyth kevin-brown