feat(gasless): add gasless module

Description
This PR has following changes:

Adding Gasless Module to the RDK
Adding Wasmd dependency and app wiring

Closes #XXX
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.
For Author:

[ ]  Targeted PR against correct branch
[ ]  included the correct type prefix in the PR title
[ ]  Linked to Github issue with discussion and accepted design
[ ]  Targets only one github issue
[ ]  Wrote unit and integration tests
[ ]  All CI checks have passed
[ ]  Added relevant godoc comments

For Reviewer:

[ ]  confirmed the correct type prefix in the PR title
[ ]  Reviewers assigned
[ ]  confirmed all author checklist items have been addressed

After reviewer approval:

[ ]  In case targets main branch, PR should be squashed and merged.
[ ]  In case PR targets a release branch, PR should be rebased.

Hey @zale144,
Thanks for the suggestions and improvements, we will get relevant changes resolved by EOD.

@zale144 ^

@zale144 , requested changes done

hey @omritoptix, testcase has been fixed which was causing the workflow check failure.

Architecture

Why have bespoke logic for authorisation of management, why not use authz?

Fixed, removed authorisation of management

What is the purpose of max num transactions per user? Why is max amt gas not enough for all use cases?

Make sense, Removed max num transactions per user

Why did you replace the sdk DeductFeeDecorator instead of using it and wrapping it in another decorator which makes use of the FeeTx interface? https://github.com/dymensionxyz/cosmos-sdk/blob/72f89234841ebd392981c4939bd1ff4dec8b7943/types/tx_msg.go#L57-L58

And how do you suggest on doing this ?
Justification for the way it is implemented -
Field Promotion and Field Visibility
When you embed a struct within another struct, the fields of the embedded struct are promoted, meaning they are accessible as if they were fields of the outer struct. However, this promotion only works within the same package.
The issue occurs when accessing struct field like txFeeChecker and others, since these fields are unexported (private) field in the DeductFeeDecorator of ante package.
Maybe my knowledge limitation but Unexported fields or methods are only accessible within the package they are defined in.
Only possible solution I see around Is exporting the struct fields from DeductFeeDecorator of ante package in Cosmos SDK so that those are accessible from other packege. (Now I'm not sure about the security aspects of doing so)

What is the purpose of the fee burn percentage?

Was irrelevant, removed it

What is the purpose of the tank creation limit? Why is it not trivial to circumvent?

Was irrelevant, removed it

Need to justify the following two hardcoded values please
MaximumTankCreationLimit = uint64(10)
MaximumAuthorizedActorsLimit = 5

Removed it, since these values made no sense after refactor

It should be generic over other VMs but only supports wasm contract execution. That's fine for an MVP but it needs to be specced out how it can be expanded to other VMS, and 'contract' terminology that is specific to wasm should be clearly demarcated.

Made generic so far, moved all the supporting identifier types to - x/gasless/keeper/usage_identifiers.go, any new transaction identifiers can be integrated within this.
Existing usage identifiers includes - MessageTypeURLs, Contract Addresses

Only 'reserved' is used, not 'provider'. Sorry if I missed it.

reserve address - holds all the funds of the gas tank, also act as a fee source
provider - is the one who creates the gas tank,

How do you add funds to a tank after creating it?

Gas tank can be funded via simple bank.MsgSend to the gas tank reserve address
x/gasless/spec/01_concepts.md > Funding a GasTank

What is the deposit for? Can we remove the deposit concept? It seems like useless extra surface area

Nope, it helps in initialising the gas tank while creating it, also it helps countering spam gas tank creation.
Docs

Please have a contrast/comparison section with feegrant in the spec

Added in x/gasless/spec/01_concepts.md,
More improvements and suggestions are welcomed

Need to explain priority and cross interaction with feegrant in spec

Added in x/gasless/spec/03_ante.md
More improvements and suggestions are welcomed

All proto fields need a docstring

Done
Code

Do not embed data in error strings, put it at the end k:v

Not sure about this, could you please give example

TxGTIDs and all references needs to be something more readable

Refactored

Utils should go in their own packeges. e.g slice utils in sliceutils

Refactored

Thanks for the PR! I've a couple questions and requests please
Architecture
Why have bespoke logic for authorisation of management, why not use authz? What is the purpose of max num transactions per user? Why is max amt gas not enough for all use cases? Why did you replace the sdk DeductFeeDecorator instead of using it and wrapping it in another decorator which makes use of the FeeTx interface? https://github.com/dymensionxyz/cosmos-sdk/blob/72f89234841ebd392981c4939bd1ff4dec8b7943/types/tx_msg.go#L57-L58 What is the purpose of the fee burn percentage?
What is the purpose of the tank creation limit? Why is it not trivial to circumvent?
Need to justify the following two hardcoded values please MaximumTankCreationLimit = uint64(10) MaximumAuthorizedActorsLimit = 5
It should be generic over other VMs but only supports wasm contract execution. That's fine for an MVP but it needs to be specced out how it can be expanded to other VMS, and 'contract' terminology that is specific to wasm should be clearly demarcated.
Only 'reserved' is used, not 'provider'. Sorry if I missed it.
How do you add funds to a tank after creating it? What is the deposit for? Can we remove the deposit concept? It seems like useless extra surface area
Docs
Please have a contrast/comparison section with feegrant in the spec Need to explain priority and cross interaction with feegrant in spec All proto fields need a docstring
Code
Do not embed data in error strings, put it at the end k:v TxGTIDs and all references needs to be something more readable Utils should go in their own packeges. e.g slice utils in sliceutils

https://github.com/dymensionxyz/dymension-rdk/pull/427#issuecomment-2143490236

Thanks @hunter1269 for the responses and changes I will review ASAP

Thanks for the recent round of changes @hunter1269
Looks pretty good to me
Please fix conflicts, I will enable CICD
Should be able to get it merged soon
Someone from our team might take one last look just to double check

@danwt @omritoptix,
could you please approve and rerun the workflow,
Latest commit includes -

conflicts resolution
synced with upstream repo

@hunter1269 there is still a markdown lint fail

@hunter1269 there is still a markdown lint fail

Looking into it,
would be great if you could provide me the reference to command or tool to be used

@hunter1269 there is still a markdown lint fail

Fixed, could you please rerun

@hunter1269 there is still a markdown lint fail

Resolved, @danwt


[jgraph/drawio] Pdf exports - only blank page appears

Describe the bug
When exporting .pdf, any page exports totally blank.
To Reproduce
Steps to reproduce the behavior:
Go to 'File'
Click on 'Export as'
Select 'Pdf'
Select 'Current page' unselect other options
Click 'Export'.
Select 'Download'.
Open downloaded file with any pdf reader
Expected behavior
Pdf opens with exported flowchart.
draw.io version (In the Help->About menu of the draw.io editor):
draw.io version: 13.6.2
Organigrammes.zip
Desktop (please complete the following information):
OS: iOS
Browser: chrome
Version: 83

Here's the results when exporting one of the file attached to my last comments.
Reseults.pdf

Hi,

if you repeat all the steps in Incognito mode, is it working? If yes, then clear cache and temporarily disable all browser extensions in Chrome and check the result.

another suggestion would be to try File > Print > click "Print" > choose Print to PDF or/and Save as PDF

P.S I tested this at my place and all is working well but I use Win 10. Sometimes only first page shows as blank so check all pages down
Regards,

Hi,
I have tried that on the web version and it works perfectly fine.
When I tried it using the Desktop version of Draw.io/Diagram, it stills displays as blank file.
Can you take a look with my graph up above?
Thanks

Fixed, will be available in the next release


Formatting messes up cursor position

Sometimes on format the cursor will move to the top of the file.
I have not been able to properly reproduce this.
Used config:
    {
        "nvimdev/guard.nvim",
        event = { 'BufReadPost', 'BufNewFile' },
        config = function()
            local ft = require('guard.filetype')

            ft('typescript,javascript,typescriptreact,vue'):fmt('prettierd')
            --     :lint({
            --     cmd = 'eslint',
            --     args = { '--fix' },
            --     stdin = true
            -- })

            -- Call setup() LAST!
            require('guard').setup({
                -- the only options for the setup function
                fmt_on_save = true,
                -- Use lsp if no formatter was defined for this filetype
                lsp_as_default_formatter = false,
            })
        end
    },

Possibly related: #67

Should involve handling exit code of uv.spawn() process for formatters
I suggest we also create a config option check_exit_code like null-ls. Otherwise check if exit code is 0.

Can you provide an example, try to reproduce it, or provide any helpful info?
Also BTW, that lint config with eslint (which may actually be the problem - are you sure it's the formatte) will not work.
We need to manually parse the output of linters and haven't implemented eslint nor eslint_d yet (those should be coming very soon, though).

Can you provide an example, try to reproduce it, or provide any helpful info?

I will update once I am able to reproduce the issue but so far it seems to happen on random occasions.
The current workaround has always been to completely restart nvim because if it happens once, it keeps happening.

if you got something wrong. I'd suggest you try a min config avoid some things conflict.

if you got something wrong. I'd suggest you try a min config avoid some things conflict.

Config is posted above. It is already very minimal.

I mean just include guard . something like  this not a Config
vim.opt.rtp:append(path/to/guard)
local ft = require('guard.filetype')
ft:('xxx'):fmt

@DrunkenToast also are you on latest version of guard, pretty sure this was fixed in #48

@DrunkenToast also are you on latest version of guard, pretty sure this was fixed in #48

I regularly update plugins, it did happen again recently in a vue3 project. But again, I don't really understand what causes it.

The issue has not occurred anymore since the exit code fix. The only thing that annoys me currently is that undoing makes my cursor jump to the bottom and with prettier it fails very very often even if there is no reason to (which I assume means it sends the wrong buffer as input), but these are separate issues so I'll consider this closer for now.


Issues observed in Delete Account command

Environment info
NooBaa Version: 5.15
Platform: Linux
1. config_root is mandatory for each account deletion
Actual Behaviour:
Command:
node src/cmd/manage_nsfs account delete --config_root /ibm/fs1/ces/s3-config --name noobaa --email<EMAIL_ADDRESS>--new_buckets_path /ibm/fs2 --access_key a-abcdefghijklmn123456 --secret_key s-abcdefghijklmn123456 --uid test --gid test
Oct-25 22:35:57.649 [/2815112]   [LOG] CONSOLE:: Resource deleted :  a-abcdefghijklmn123456
[root@ramya-sc-worker noobaa-core]# node src/cmd/manage_nsfs account list --config_root /ibm/fs1/ces/s3-config
Oct-25 22:36:00.737 [/2815218]   [LOG] CONSOLE::  []
Expected Behaviour: config_root should be optional
Command:
node src/cmd/manage_nsfs account delete  --name noobaa --email<EMAIL_ADDRESS>--new_buckets_path /ibm/fs2 --access_key a-abcdefghijklmn123456 --secret_key s-abcdefghijklmn123456 --uid test --gid test
Oct-25 22:35:57.649 [/2815112]   [LOG] CONSOLE:: Resource deleted :  a-abcdefghijklmn123456
[root@ramya-sc-worker noobaa-core]# node src/cmd/manage_nsfs account list --config_root /ibm/fs1/ces/s3-config
Oct-25 22:36:00.737 [/2815218]   [LOG] CONSOLE::  []
2. Account should get deleted with name
Actual Behaviour:
Command:
node src/cmd/manage_nsfs account delete --config_root /ibm/fs1/ces/s3-config
--access_key a-abcdefghijklmn123456
Oct-25 22:35:57.649 [/2815112]   [LOG] CONSOLE:: Resource deleted :  a-abcdefghijklmn123456
[root@ramya-sc-worker noobaa-core]# node src/cmd/manage_nsfs account list --config_root /ibm/fs1/ces/s3-config
Oct-25 22:36:00.737 [/2815218]   [LOG] CONSOLE::  []
Expected Behaviour: name should be used for deletion
Command :
node src/cmd/manage_nsfs account delete  --name noobaa
Oct-25 22:35:57.649 [/2815112]   [LOG] CONSOLE:: Resource deleted :  a-abcdefghijklmn123456
[root@ramya-sc-worker noobaa-core]# node src/cmd/manage_nsfs account list --config_root /ibm/fs1/ces/s3-config
Oct-25 22:36:00.737 [/2815218]   [LOG] CONSOLE::  []
3. Account should get deleted with uid:gid combination instead of accesskey
Actual Behaviour:
Command :
node src/cmd/manage_nsfs account delete --config_root /ibm/fs1/ces/s3-config
--access_key a-abcdefghijklmn123456
Oct-25 22:35:57.649 [/2815112]   [LOG] CONSOLE:: Resource deleted :  a-abcdefghijklmn123456
[root@ramya-sc-worker noobaa-core]# node src/cmd/manage_nsfs account list --config_root /ibm/fs1/ces/s3-config
Oct-25 22:36:00.737 [/2815218]   [LOG] CONSOLE::  []
Expected Behaviour: uid:gid should be used for deletion
Command :
node src/cmd/manage_nsfs account delete  —uid:gid 1092:1093
Oct-25 22:35:57.649 [/2815112]   [LOG] CONSOLE:: Resource deleted :  a-abcdefghijklmn123456
[root@ramya-sc-worker noobaa-core]# node src/cmd/manage_nsfs account list --config_root /ibm/fs1/ces/s3-config
Oct-25 22:36:00.737 [/2815218]   [LOG] CONSOLE::  []
4. Account should get deleted / should throw the error if wrong config root provided.  Please take a look of this issue. Thank you.

the following are apis exposed for ocp for deleting account which either accepts uid/gid or name So the delete functionality should work similar to the below api
Api: "account_api", Method: "delete_account",
			Params: getAccountParamsNoobaaRequest{
				Email: name,
				Uid:   int32(uid),
				Gid:   int32(gid),
			},

Api: "account_api", Method: "delete_account_by_property",
			Params: deleteAccountNoobaaRequestParams{
				Nsfs_account_config: deleteAccountNsfsAccountConfig{
					Uid: int(uid),
					Gid: int(gid),
				},
			},

@ramya-c3 Please break all those 4 observations into separate Issues, and please give the proper subject to each.
The fixes are different and we should evaluate/discuss each separately.

Closing in favor of #7583 #7584 #7585 #7586


Fix grammar of grouped description

In the Iterables section, under grouped the word "an" makes this sentence confusing

LGTM, thanks for your contribution!


Only send PrivateClusterConfig for private clusters

GKE rolled out a change that denies setting PrivateClusterConfig on
Cluster objects if they are not using private nodes, so update the
controller to conform with this.
https://github.com/rancher/rancher/issues/33241

@rmweir

Should we instead validate this in a rancher validator and let the controller here get an error from GKE?

It's not a user error. We still need the user to set PrivateClusterConfig to non-nil on the CR because of syncing.

Otherwise the user may set private cluster config and not understand why the change isn't taking place.

The operator still reads the PrivateClusterConfig on the CR and decides whether to create a private cluster or non-private cluster. PrivateClusterConfig cannot be updated so there is no risk of the user making a change to the CR and not seeing it changed in the cluster.

We could even leave it how it is since an error should be propagated up.

There's nothing a user could do to fix this, it's an API error caused by the Cluster object that the operator is sending in the request.

Added validation to make sure EnablePrivateEndpoint makes sense.


exportToJson and importFromJson not working with REAL type

Tried using exportToJson and importFromJson its working fine with INTEGER and TEXT type but not working with REAL Type,
I also checked vue-sqlite-app-startar, REAL type is never used in the demo as well.
Steps:

Prepare any SQLite DB with Real Type
Try to use exportToJSON or importFromJson.
It will give an error ( Note: In Export It won't give an error but the values will be emitted from the exported JSON )

example JSON:
    database : "db-from-json",
    version: 1,
    encrypted : false,
    mode : "full",
    tables :[
        {
            name: "users",
            schema: [
                {column:"id", value: "INTEGER PRIMARY KEY NOT NULL"},
                {column:"email", value:"TEXT UNIQUE NOT NULL"},
                {column:"name", value:"TEXT"},
                {column:"age", value:"REAL"},
                {column:"last_modified", value:"INTEGER"}
            ],
            indexes: [
                {name: "index_user_on_name",column: "name"},
                {name: "index_user_on_last_modified",column: "last_modified"}
            ],
            values: [
                [1,"Whiteley.com","Whiteley",30.1,1582536810],
                [2,"Jones.com","Jones",44,1582812800],
                [3,"Simpson@example.com","Simpson",69,1583570630],
                [4,"Brown@example.com","Brown",15,1590383895]
            ]
        },
        {
          name: "messages",
          schema: [
            {column:"id", value: "INTEGER PRIMARY KEY NOT NULL"},
            {column:"title", value:"TEXT NOT NULL"},
            {column:"body", value:"TEXT NOT NULL"},
            {column:"last_modified", value:"INTEGER"}
          ],
          values: [
              [1,"test post 1","content test post 1",1587310030],
              [2,"test post 2","content test post 2",1590388125]
          ]
        },
        {
          name: "images",
          schema: [
            {column:"id", value: "INTEGER PRIMARY KEY NOT NULL"},
            {column:"name", value:"TEXT UNIQUE NOT NULL"},
            {column:"type", value:"TEXT NOT NULL"},
            {column:"size", value:"INTEGER"},
            {column:"img", value:"BLOB"},
            {column:"last_modified", value:"INTEGER"}
          ],
          values: [
            [1,"feather","png","NULL",Images[1],1582536810],
            [2,"meowth","png","NULL",Images[0],1590151132]
          ]
        }

    ]
}```

@mouse9 Are you using the refactor 2.9.4 or the original 2.4.5 of @capacitor-community/sqlite? On which platform it happens iOS, Android, Electron ?

@mouse9 Are you using the refactor 2.9.4 or the original 2.4.5 of @capacitor-community/sqlite? On which platform it happens iOS, Android, Electron ?

@jepiqueau I am using this "@capacitor-community/sqlite": "^2.4.5-3",
and I have checked in Android, haven't checked with other two.
In Fact it's reproducible with the same import JSON with REAL type in this Repository.
https://github.com/jepiqueau/vue-sqlite-app-starter
I have shared the above JSON from this repository only.

@jepiqueau I am using this "@capacitor-community/sqlite": "^2.4.5-3",
and I have checked in Android, haven't checked with other two.
In Fact it's reproducible with the same import JSON with REAL type in this Repository.
https://github.com/jepiqueau/vue-sqlite-app-starter
I have shared the above JSON from this repository only.

@mouse9 i solve it in the coming refactor 2.9.5 release, i will invite you to start looking at migrating to the refactor release and test it on https://github.com/jepiqueau/vue-sqlite-app-starter refactor branch. The plugin interface has changed but it will be the one to use when upgrading to capacitor3. It is well documented, but if you need some help do not hesitate to contact me

@mouse9 i solve it in the coming refactor 2.9.5 release, i will invite you to start looking at migrating to the refactor release and test it on https://github.com/jepiqueau/vue-sqlite-app-starter refactor branch. The plugin interface has changed but it will be the one to use when upgrading to capacitor3. It is well documented, but if you need some help do not hesitate to contact me


hello-world mongoose dependency is necessary, but currently is only a peer dependency

Node.js version: v10.11.0
npm version: 6.4.1
Strapi version: 3.0.0-alpha.14.2
Operating system: Mac OS High Sierra 10.13.4
Which example is causing problem?
hello-world
Do you want to request a feature or report a bug?
bug
What is the current behavior?
npm install does not automatically install<EMAIL_ADDRESS>It is only suggested as a peer dependency. If the user does not manually install this dependency, then npm start fails to boot the server. See the following gist for the log: https://gist.github.com/gwpantazes/8711bf0cf15165fb04e374aa4659f11c
If the current behavior is a bug, please provide the steps to reproduce the problem
Follow the instructions in the README.
npm install
npm start

As of running npm start, observe that the server fails to start because it cannot find the mongoose module.
At this point, manually installing with npm install<EMAIL_ADDRESS>fixes the issue.
What is the expected behavior?
mongoose would be included not as a peer dependency, but as an actual dependency, if it was actually necessary to run the example. Running npm install would be sufficient to successfully run npm start.

Hello @gwpantazes.
Are you able to submit a PR to fix it ?

I'll look into it. I am not super experienced with NPM but from what I've found out since then I think I can fix it by running npm install<EMAIL_ADDRESS>--save or something like that. I'll see if that fixes it and submit a PR soon!

Submitted PR #55, which fixes this issue for me.

Hello @gwpantazes
I'm not able to reproduce your issue.
mongoose is a deps of strapi-hook-mongoose so the dep is installed ...


Feature/remove token param

Remove the token param if it is set after retrieving token

Question @Schparky:
Some lines have return p.ManagementAPI, nil, should that be return p.ManagementAPI + p.TokenPath, nil instead?

General question @Schparky (not changed in this PR, but might need to be changed): Some lines have return p.ManagementAPI, nil, should that be return p.ManagementAPI + p.TokenPath, nil instead?

I believe you're right. Might explain why sometimes I end up on a CAM page when I expect to be on a proxy/static page.


Fix "warning: circular argument reference - filters" on Ruby 2.2

See: http://stackoverflow.com/questions/27669855/warnings-after-upgrading-to-ruby-2-2-0
Fixes #286

It would be really great to get this merged and knife-ec2 released.  This causes huge warnings that makes using knife-ec2 difficult.

@ryancragun can I get a :+1: on this so I can merge it?

LGTM.  :+1:


add Adil Sheikh

I'm happy to add my name to the list ✌🤗

Thanks! 🎉

Very Welcome and Thank you for merging😊


Unifi verify_ssl configuration to certificate path not accepted

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.46.0
Python release (python3 --version):
3.4.2
Component/platform:
device_tracker.unifi
Description of problem:
Documentation says the following on https://home-assistant.io/components/device_tracker.unifi/
verify_ssl (Optional): Controls if the SSL certificate running on your Unifi webserver must be trusted by a known Certificate Authority on the server running Home Assistant. Defaults to ‘True’ but can also be a value that points to your custom cert “path/to/custom_cert.pem”.
I've added the following in my configuration:
verify_ssl: "/home/homeassistant/.homeassistant/certs/unifi.pem"
I got an error that a boolean value is expected.
Expected:
Accepted configuration
Problem-relevant configuration.yaml entries and steps to reproduce:
device_tracker:
  - platform: owntracks
  - platform: unifi
    host: <IP_ADDRESS>
    username: !secret unifi_user
    password: !secret unifi_pw
    verify_ssl: "/home/homeassistant/.homeassistant/certs/unifi.pem"

Traceback (if applicable):
2017-06-04 12:51:23 ERROR (MainThread) [homeassistant.config] Invalid config for [device_tracker.unifi]: invalid boolean value /home/homeassistant/.homeassistant/certs/unifi.pem for dictionary value @ data['verify_ssl']. Got '/home/homeassistant/.homeassistant/certs/unifi.pem'. (See ?, line ?). Please check the docs at https://home-assistant.io/components/device_tracker.unifi/

Additional info:
Found the following on reddit: https://www.reddit.com/r/homeassistant/comments/6a2t7a/device_trackerunifi/

I'm also encountering this issue.
Home Assistant release (hass --version):
0.49.0
Python release (python3 --version):
3.5.2

I stumbled into this, too. Fresh Hass.io setup (HA 0.49.1). According to the code at https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/device_tracker/unifi.py#L35 the docs are just wrong and it has to be a boolean?

In urllib, it can be a boolean or a string to the cert file.

I've been looking at this and it seems to be an issue with the config validation expecting a boolean but the underlying libraries (pyunifi / urllib3 / requests) can all take either a boolean (True => Use OS CA certificate store for validation, False => Don't do any validation) or a string for the absolute path to a CA bundle file that is responsible for validating the encountered certificate.
I'll make a PR to resolve the config expectation.
One thing to bear in mind is that the default certificate used on my Unifi Cloud Key had no commonName or SubjectAltName which lead to: requests.packages.urllib3.exceptions.SSLError: no appropriate commonName or subjectAltName fields were found and it bailing out as expected.
Not sure if this is applicable to the standalone java instances.
The only solution I can see is to either self sign your own certificate in place or have your own CA generate one for it (this was my use case and what lead me here).


HHH-15598 Removal of enhancer helpers

As proposed in https://hibernate.atlassian.net/browse/HHH-15598.
The org.hibernate.bytecode.spi.InstrumentedClassLoader is a little utility we don't use ourselves anymore. It's simple enough that anyone needing such a thing could re-implement it themselves so I suggest we remove it; in fact I know of other platforms having a similar utility - but it's never quite implemented exactly like this, so I'd question the general usefulness; it feels more like it's a useful example.
Same for org.hibernate.bytecode.spi.ByteCodeHelper: it has no use within our own runtime code, but it's used by tests - so I'd move it to the testing utilities.
Since these are SPIs I’m proposing the change for 6.2, without need for a deprecation cycle.
I’ll send a draft to check if this is agreeable.
Would this be OK @sebersole , @scottmarlow , @yrodiere  ? I'd like to clean this up soon as it limits the use of ByteBuddy to a specific couple of packages, makes some further cleanup easier.

Good point about EnhancingClassLoader, but it's in testing already so it doesn't bother me - and it's actually useful :)

Seems fine to me.  Should https://docs.jboss.org/hibernate/orm/6.0/internals/internal.txt be updated to include org.hibernate.bytecode.spi as well?

Seems fine to me. Should https://docs.jboss.org/hibernate/orm/6.0/internals/internal.txt be updated to include org.hibernate.bytecode.spi as well?

No objections but I'm not sure - it's literally an SPI, do we consider those internal?


How to open same thread between 2 users programatically

@bensmiley Please help me on this.

@myeduapp You could use this guide: https://github.com/chat-sdk/docs#creating-a-private-thread. I hope that helps.

@bensmiley The link only shows how to create a thread. I want to open chat between 2 users. If there is already communication between 2 users then it should open the particular chat otherwise create new chat. It seems that fetchuserswithentityid method is having some issues as it is returning null value even if user is present in firebase console
Please help me on these issues.

@bensmiley Could you please explain it in detail?


Add pages for 3 Project

Issue Type:
[  ] Bug Report
[ x]  Feature Request
[  ] Documentaion
Describe the bug
Add Pages for Our 3 Projects
Possible solution
For now we can add the same data on Wordpress website so we can get an idea for improvement !

@himanshu007-creator  Can we start for this ?

@rohank2502 Go ahead and work on this.
@himanshu007-creator kindly assign him.

ead and work on this.

Cool ! I will start work on this tomorrow and update you with all three pages within 3 days will it be ok !

Yeah, 1st update by Sunday would be fine.

Yeah, 1st update by Sunday would be fine.

Cool @himanshu007-creator  Please assign

@himanshu007-creator  We have created all three pages for projects !!

done


about train/test result

Thank you very much for sharing the code. I have been training less than 95.3% when I use your script to do training. I can only train about 94.5%. The environment I use is pytorch1.0.1, 4 v100, can you help me analysis? Thanks!

I modified your learning rate strategy and now reach around ~95%.

Hello, Validation dataset are need ?


PT Run alternative functionality

PT Run seems to serve the same functionality as the start menu meaning that I rarely use it.

For my workflow I often find myself wanting to switch windows instead of open applications with the menu and usually do it with Alt + Tab but that can become cumbersome with large numbers of windows. Another option for this workflow would be to use the Task View screen, but that means I lose focus on the window I was already using and have to use the mouse.
What I want to propose is a feature similar to the Command Palette in many code editors, a menu where you can type to execute common actions or switch files.
The ideal features of this would be:

The ability to bring a specific window into focus.
The ability to switch virtual desktops.
Context specific actions.

ex: Typing "minimize" will minimize the focused window.

Being able to execute common windows actions.

ex: Lock, show desktop, open action center, etc.

Making this and the current functionality both optional.

The ability to bring a specific window into focus.

This is something that is already there in PT Run but may not be at the top of the search results. This is already addressed in #6129 (Not released)
You can also shutdown your computer from PT Run:
Type "> shutdown /p /f" in PT Run and press enter

you can now do system level commands and we can do text based running app searches.

You can do this already with the window walker built in plugin.
i think system keystrokes are better.  Virtual desktops is win+ctrl+arrows already is there and does this
i think system keystrokes are better than PT run.
https://github.com/microsoft/PowerToys/issues/129


more permissive jdcal version

See #3
Possibly this line should be removed altogether if it's just a dependency, but...

I agree, this line should be removed. It's a dependency of csvkit. Resolved in 343ea47ad8d09fe195e8742d51f73b8c60ed017e


wil::com_ptr typedef is silently omitted if WI_ENABLE_EXCEPTIONS isn't defined

If exceptions aren't enabled using wil::com_ptr results in an error that isn't immediately clear without digging through the source.
error C2039: 'com_ptr': is not a member of 'wil'
It should be pretty easy to add a struct that takes a compile time message and static_assert(false, message) if that class is instantiated to produce a clearer error message when using throwing types in binaries that don't support exceptions.

There's wil::com_ptr_nothrow

Yeah, I switched over to the _nothrow variant once I figured out what the error was. I made this change in a header that is included into a bunch of different binaries one of which happened to have exceptions turned off and it took me a bit to figure out that that binary didn't have exceptions and that was causing the compiler error since the typedef isn't defined at all in that case. Adding some sort of InvalidInstantiation struct to static_assert in cases like this would be pretty helpful in making the error immediately apparent. This is a little tricky since string literals can't be passed as template arguments but maybe something like this:
enum class BadInstantiation : int { com_ptr } template<BadInstantiation> struct InvalidInstantiation {     static_assert(false, "Must be overloaded") }; template<> struct InvalidInstantiation<BadInstantiation::com_ptr> {     static_assert(false, "wil::com_ptr must not be instantiated when exceptions are disabled.") }
although admittedly that is still pretty ugly.

What error was it giving you that was confusing? I'd expect it to give some form of "undefined symbol" error, which should be relatively clear as to what's wrong. Albeit perhaps not super clear of why the symbol is undefined, however looking up the definition should give a pretty quick answer:
#ifdef WIL_ENABLE_EXCEPTIONS
    //! COM pointer, errors throw exceptions (see @ref com_ptr_t for details)
    template <typename T>
    using com_ptr = com_ptr_t<T, err_exception_policy>;
#endif

But if we were to try and do something here, we can probably piggy-back off the definition of err_exception_policy which we already have to stub out for other reasons. E.g. providing functions of the form:
struct err_exception_policy
{
    template <typename T = void> static result HResult(HRESULT hr) { static_assert(details::false_v<T>, "Exceptions not enabled etc. etc."); }
    // ...
};

It's probably best to do that anyway since the experience of err_exception_policy accidentally being used is currently pretty sub-optimal (although it should be somewhat difficult to find yourself in that situation).
But again, I'm not all that sold on this being necessary. Additionally a lot of people are generally unhappy if a symbol shows up in intellisense/editor suggestions that they can't use

Yeah, the what is fairly clear in error C2039: 'com_ptr': is not a member of 'wil' but tracking down the why is a bit more effort. If the error output was just "instantiating com_ptr with exceptions disabled, use com_ptr_nothrow instead" it would be super clear and easy to fix the issue without doing any digging. Not a super big issue but seems like it would be a nice to have and potentially save people a few minutes of digging to fix this issue.

I don't feel strongly about this, though better errors are always good.
One key to keep in mind if this is pursued is that the solution cannot cause ODR issues when linking a LIB built with exceptions enabled with a LIB built without exceptions enabled into the same binary.  This is commonplace in some binaries.
I suspect that the simple fact that this class is template-based would avoid it in this case, but it could be applicable in others.

The problem with the proposal is that it would create ODR violations if one *.cpp file used exceptions and another didn't. This is a common situation for static libraries.
``cpp
// library1.cpp - compiled with exceptions disabled
#include <wil\com.h> // defines err_exception_policy::HResult to raise a static assert

``cpp
// library2.cpp - compiled with exceptions enabled
#include <wil\com.h> // defines err_exception_policy::HResult without the static assert

If your project uses both libraries, you have an ODR violation if the definition of err_exception_polcy or com_ptr varied depending on whether exceptions are enabled.
The current mechanism has the important property that you can link together libraries with different exception policies.


Feature/maplibre express

closes #29

[ ] Handle Multi-Geometry objects
[ ] Handle multiple dataset/frames at once
[ ] Automatically create color bins based on a given property

Need to br re-worked
mx.Map(layers = [], controls=[], ...)

mx.layer(..., map, map_class)

mx.fill_layer(color, ...)

mx.line_layer(color, ...)

mx.extrusion_layer(color, extrusion, ...)

mx.circle_layer(color, ...)


LIVY-776 - Update Maven Shade Plugin to 3.2.1

In order to apply the PR to update Jackson to 2.10.1 (https://github.com/apache/incubator-livy/pull/258/files), it is also necessary to update the Maven Shade Plugin to avoid an ASM IllegalArgumentException error in the client-http module.

Hi @coheigea  I faced the same issue (shaded plugin and jackson version) on https://github.com/apache/incubator-livy/pull/289 for scala 2.12 and spark 3 support. I need also to change this. I do not know how deal with multiple PR.

@tprelle It's up to the maintainers of the project, either it could all be done in one go (as in your PR), or maybe they might prefer to just update Jackson separately. If your PR is merged first, then I'll just close this PR. Either way it would be good from my POV to get us updated to Jackson 2.10.x ;-)

Fixed in #300


WIP: deconz: allow setting both entity and field in deconz.configure

Description:
This is a work in progress. I'm submitting it now to gather feedback before doing the remaining work (tests, documentation, etc.)
Problem:
Currently the deconz.configure service allows either specifying a field or an entity, but not both. This makes it impossible to set states in deCONZ when all you have is an entity id (think AppDaemon or other automations), since an entity will resolve to a device path such as /lights/1 (that you can use to change configuration attributes such as the device name) and in order to change states you need to do a PUT to /lights/1/state.
Motivation:
Why setting states via deconz.configure instead of (for example) light.turn_on? Because right now the feature of increasing/decreasing a light's current brightness (or color temperature) which is exposed by deCONZ (which is actually from the Hue bridge API so it applies to the Hue bridge as well) via the bri_inc (and ct_inc) attributes is not accessible via the light platform.
Two examples of why it's necessary to use this:

This is essential to implement a remote control that can smoothly control the lights in HASS, because for example when you hold a "increase brightness" button you want to tell the light to increase its brightness to the max with a transition of (let's say) 5 seconds (bri_inc: 254, transitiontime: 50)  and when the button is released you send bri_inc: 0 (also defined by Hue API) to tell the light to stop the fade (this gets translated to a Zigbee "stop" command). Right now via the light platform you can only set explicit brightness targets, and you have to do that in a loop, however this tends to overload the Zigbee network and it's not smooth. The algorithm I describe is how remote controls manage to implement smooth fades with just two Zigbee commands (one to start, one to stop).

Some lights such as IKEA trådfri have firmware bugs in which they fail to respond to commands in case they're in the middle of a long transition (https://github.com/dresden-elektronik/deconz-rest-plugin/issues/894). Sending bri_inc: 0 (which gets translated into a "stop" command in the Zigbee layer) can "ressurect" the lamp. Right now you can't send such a command from HASS, which is useful when you need to work around these kinds of firmware bugs.

However, I'm going to submit a separate WIP PR to introduce that feature (fading brightness/temperature) on the light platform. This PR is about offering a way to set state attributes that exist in the Hue/deCONZ API that for whatever reason are not (yet) exposed in "higher-level" platforms, and all you have is the entity id and do not know the device path. I believe that is even the original intent, since the documentation explicitly refers to /lights/1/state and the fact you can't do that by specifying an entity was probably an oversight.
Solution:
Allow both entity and field to be set simultaneously. This won't break any existing setups because they're currently mutually exclusive. If you set them both, entity is used to resolve the device path and field is added as a subpath. In this way you can set state attributes by setting:
{ "entity": "light.name", "field": "/state", "data": { ... } }

I also considered introducing a new service such as deconz.put_state but I deemed it not to be necessary and probably redundant, given the above. Personally I have no strong preference to one way or another, so I can do that if you believe it's a superior alternative.
Related issue (if applicable): N/A
Pull request in home-assistant.io with documentation (if applicable): None yet. Will do it once the approach is settled.
Example entry for configuration.yaml (if applicable):
N/A
Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] ~New dependencies have been added to the REQUIREMENTS variable~ N/A
[ ] ~New dependencies are only imported inside functions that use them~ N/A
[ ] ~New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py~ N/A
[ ] ~New files were added to .coveragerc~ N/A

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Commit amended and comments addressed. services.yaml updated.
I'll need some guidance for introducing unit tests. I'm new to this codebase.
Regarding documentation, I would appreciate suggestions for the wording to be used. I'm not a native English speaker.

Amended again. New comments addressed.

Looks good! I'd like a test or two now that it is a bit more complex

I'll need some guidance for introducing unit tests. I'm new to this codebase.

Could you help me out with this, please? Maybe pointing to some unit tests that are similar enough that I could draw inspiration from?

You need to find a test that calls a service. You can base the test on https://github.com/home-assistant/home-assistant/blob/7be7a8de309fdfc39cd409f24fa9503afd11695e/tests/components/deconz/test_init.py#L100
You can probably remove most asserts
Then just a couple of tests that runs the different paths in the service
Give it a couple of hours. I'll be at the computer tonight I think

OK, thanks. It's getting late in my time zone, so I'm probably only going to give it a go tomorrow.

Pushed tentative unit tests.
I have to be honest and say I they are completely based on cargo cult. I know exactly what needs to be done in abstract terms, but I'm not a Python developer and I have no previous exposure to (Python) async, testing and the HASS codebase (and how much of HASS gets mocked during testing). I do not really know if those tests are actually technically correct (for example, free of race conditions), or they only happen to pass due to luck. I made them after lots of trial and error, bashing my head against the wall, fighting with await et al.
Usually I prefer to have small test methods, so each test would be in its own, but in order to cut down the amount of setup boilerplate I ended up testing all cases within the same method.
To improve these tests beyond the state they're in, I really need to be spoon fed and told exactly what needs to be done and where. I'm afraid we reached the limit of what I can currently do unassisted.

I'm not sure why the Travis CI build failed. It does not seem that it was due to the tests.

Got a green build, @Kane610. Tests were passing previously, but I had to change one docstring to please the linter.

I'd just like a quick second opinion by @MartinHjelmare or @balloob to top this off.


[ZEPPELIN-2749] Use scalable file structure for zeppelin web

What is this PR for?
We have improved zeppelin-web, but some parts are still messy. As part of keeping zeppelin-web module healthy (ZEPPELIN-2725), I suggest having these file structure. (Refer the screenshot section)
Here are few reasons.

unified directory, file name helps us to recognize, find which part we should modify / fix

Let's say we need to modify the resize feature of paragraph, where the developer can find it? currently, it's under component/resizable not under paragraph/resizeable and also it's not the shareable component. There is no reason to keep that files in component/**

this structure is what the angularjs community has verified for few years. so newly joined developers can feel more comfortable.
this is necessary for Modular archiecture and it eventually helps us to make a smooth transition toward next technologies (even whatever we will use)

Additionally,

This is not the meaningless refactoring PR and doesn't block developing new features / fixes (Please refer the Some Details section)
I will handle conflicts for few days would be brought by other WIPs

For your information,

https://github.com/toddmotto/angularjs-styleguide#file-naming-conventions
https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#naming

How to Review This PR?
Please follow the commits. I modified submodules by splitting commits. Thus commit message includes what has been done in that PR. For example,

Some Details

Didn't change the widely used variable names not to make many conflicts. For example, websocketMsgSrv, arrayOrderingSrv
Since there are helium packages already published, didn't change the HTML file names like pivot_setting.html (it's better to use pivot-setting.html if we following the rule)

What type of PR is it?
[Improvement | Refactoring]
Todos
Please refer the commit message.
What is the Jira issue?
ZEPPELIN-2749
How should this be tested?
All functionalities must work as like before, CI will test it.
Screenshots (if appropriate)
Before: messy, mixed directory structure

After: only the shared components will be placed under components/

Questions:

Does the licenses files need update? - NO
Is there breaking changes for older versions? - NO
Does this needs documentation? - NO

Cool, I also experienced as like what your describing at especially filename and messy folders.
And Tested and LGTM. Everything is working.

@soralee Thanks for the review. We need to keep the zeppelin-web module clean. :)
Merge if no more discussion.

rebased to fix some commit message which can't be handled in the merge script. (*)

Rebased to clean commit messages.

Left a comment for history.
I tried to merge this one before 11 hours ago and at that time it looks merged. (no error on the script) But ASF git didn't reflect the commit. That's the reason why I rebased twice. (I thought long commit message or some invalid chars are the problem).


How to build from source now?

I would still love to build from source instead of docker but the documentation on this seems deprecated (no longer a 'build_all' in bin)

See file BUILD.md in the root directory for instructions.

Fixed with  https://github.com/danintel/sawtooth-faq/commit/40f2c0


[TEMPLATE] Movies Panel

Description
This app is a dashboard for searching, filtering and analyzing movies.
Integrations and features

Built-in Sample Movies Database in MongoDB
Gmail SMTP Integration
Carbone API Integration for Report Generation
Attach and send PDF files via Email
Loading Animation that hides individually loading widgets until all APIs have run.
Side Menu where the selected item is highlighted.
A Filter widget where the user can change the data shown in the dashboard.

Attachments

[x] Link to App

[x] Screenshots

[x] JSON Export
Movies Panel.zip

Congratulations! You won a gold prize for this submission and 10 coins for use in the swag store!


Fall back on default type parameter when inference does not yield a more suitable type

TypeScript Version:  2.3.2
Code
class O<T=any> {
    constructor(public array: T[]) { }
}

declare let val: O<number> | O<string>;
declare function f<T=any>(x: O<T>): T;
// Inference fails here.
f(val);

Actual behavior:
An inference error is produced on the f(val) invocation.
The type argument for type parameter 'T' cannot be inferred from the usage. Consider specifying the type arguments explicitly.
Type argument candidate 'number' is not a valid type argument because it is not a supertype of candidate 'string'.

Expected behavior:
TypeScript should be able to accept this program.
There are two possible paths by which this program could be accepted.

TypeScript could infer T = number | string.

In essence, the f(val) call requires TypeScript solve O<number> | O<string> = O<T>. This is solvable if TypeScript can prove that O<number> | O<string> is a subtype of O<number | string> which depends on the variance of O.
It's possible that TypeScript is already doing the right thing here and failing to infer a type for T given what it knows.

TypeScript could fall back on the default type T = any when inference for T fails.

I believe this would be a valid improvement to the existing logic. Given the presence of the default type for T and the fact that val satisfies it, the given default of any should be used as inference has failed to identify a narrower type.
It is unexpected that the compiler ignores the provided default for T which would allow the program to be accepted in favor of rejecting the program because inference is unable to solve for T.
Real world example:
Angular is attempting to add generics to our Forms API in a backwards-compatible manner, using any as a default generic type for the values of composed form structures.
Here is the basic class structure:
class AbstractControl<T=any> {
    value: T;
}
class FormGroup<T=any> extends AbstractControl<T> {
    constructor(
        public controls: {[key in keyof T]: AbstractControl<T[key]>}
    ) {
        super()
    }
}
class FormArray<T=any> extends AbstractControl<T>{
    constructor(
        public controls: AbstractControl<T>[]
    ) {
        super()
    }
}
class FormControl<T=any> extends AbstractControl<T>{
    constructor(value: T) {
        super()
        this.value = value
    }
}

We have been unable to deploy this solution as it breaks the following existing example:
let a = new FormArray([
  new FormGroup({'c2': new FormControl('v2'), 'c3': new FormControl('v3')}),
  new FormArray([new FormControl('v4'), new FormControl('v5')])
]);

Here, the array passed to the FormArray constructor has a union type (similar to val in the theoretical example above), and inference for FormArray's generic T parameter fails. In this case, the default parameter type of any could be correctly applied and would ensure this code is still accepted (as it was before the addition of generics).
Thanks to @rkirov for his insight and the simplified theoretical example, and @Toxicable for the initial report.

Ah this would be great if it got fixed!

Any plans to fix this one soon? Cheers

Here is a working example:
class AbstractControl<T = any> {
  value: T;
}

class FormGroup<T = any> extends AbstractControl<T> {
  constructor(public controls: { [key in keyof T]: AbstractControl<T[key]> }) {
    super();
  }
}

class FormControl<T = any> extends AbstractControl<T> {
  constructor(value: T) {
    super();
    this.value = value;
  }
}

class FormArray<T = any> extends AbstractControl<T> {
  constructor(public controls: ControlType<T, keyof T>[]) {
    super();
  }
}

let a = new FormArray([
  new FormGroup({ c2: new FormControl('v2'), c3: new FormControl('v3') }),
  new FormArray([new FormControl('v4'), new FormControl('v5')]),
]);

type ControlType<T, K extends keyof T> =
  T[K] extends any[] ? FormArray<T[K]> :
  T[K] extends object ? FormGroup<T[K]> :
  FormControl<T[K]>;

Hey, this issue opened 2 years ago  :-1: . Nobody doesn't fix this(

So 3 years and still nothing?!

TypeScript could fall back on the default type T = any when inference for T fails.

This is just not what type parameter defaults are for—they very intentionally play no part in inference. I argue that you want to know when inference “fails.” Let me modify the original example very slightly:
interface Box<T> {
    get: () => T;
    set: (x: T) => void;
}

declare function doSomethingWithBox<T = any>(box: Box<T>): T;

declare let box: Box<number> | Box<string>;

doSomethingWithBox(box);

The difference here is that Box, unlike Array (which is the salient feature of O), is written to be invariant on T, as Array ought to be if we were aiming for strict soundness. Because of this change, there now exists no sound instantiation of T at doSomethingWithBox(box). In other words, if I were to explicitly provide the type argument, the only type I could write that would type check is doSomethingWithBox<any>(box). Is this an argument for falling back to any? I see it as the opposite. My call is inherently unsafe, so I should be alerted to that fact. I would be unhappy if my error were silently suppressed, potentially by a type definition I got from an @types package. If I truly want to silence the error, I can always supply the any type argument myself.

Thank you for even asking that 😄 I was looking for fallbacking generics and your f<T=any> helped me :)


update 6.0 cannot be used

Describe the bug
Installed dependencies according to the documentation and updated the plugin to version 6.0, but encountering an error in the Windows environment: Error: Cannot find package 'prettier-plugin-organize-imports' imported from D:\Microsoft VS Code\noop.js. How can this issue be resolved?

To Reproduce
Steps to reproduce the behavior:
yarn add -D<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Expected behavior
success
Versions (please complete the following information):

VS Code Prettier ESLint extension 6.0
Visual Studio Code: [v1.87.2]
Node: [v16.14.2]
Package Manager [ npm 8.5.0, yarn 1.22.18, pnpm 8.10.3]
prettier: [3.2.5]
eslint: [8.52.0]

System Specifications (please complete the following information):

OS: [Windows 10]
Processor: [Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz   2.90 GHz]
RAM Size: [16 GB]

Error: Cannot find package 'prettier-plugin-organize-imports' imported from C:\Program Files\Microsoft VS Code Insiders\noop.js     at __node_internal_ (file:///d:/repos/qlab/ms-frontend/node_modules/prettier/index.mjs:16460:11)


[ICE: 27] Balances not showing on Mode - RPC Issues

Describe the bug
We have had a few reports of users not being able to see their balance when starting a bridge from Mode.
After checking with them and trying to reproduce the issue, I have found a CORS block on my console (and also on the users'). We have tried changing our RPC (in the attached image I am using https://mode.drpc.org/ but it is https://1rpc.io/mode in the console error).
The error is intermittent, sometimes I get the balance and sometimes it disappears. As example, right now i just did a CONTROL+F5 refresh and ezETH its there, but after a while, it disappears

Ticket:
https://app.intercom.com/a/inbox/qge2vd8z/inbox/shared/all/conversation/769?view=List
@oncall

It's a rate limit on the public RPC. Unfortunately we don't have better options atm.

Is there no possible fix for this? (other than users waiting)
Some reported trying throughout several hours and still getting the error

Are RPCs on the frontend automatically rotated between a set of public ones? If not, we should probably rotate based on user reports

can try Blast https://blastapi.io/chains/mode

https://app.intercom.com/a/inbox/qge2vd8z/inbox/shared/all/conversation/777?view=List
https://app.intercom.com/a/inbox/qge2vd8z/inbox/search/conversation/775?query=RPC Mode&sort=newest
https://app.intercom.com/a/inbox/qge2vd8z/inbox/conversation/705?view=List
https://app.intercom.com/a/inbox/qge2vd8z/inbox/conversation/779?view=List
https://app.intercom.com/a/inbox/qge2vd8z/inbox/conversation/804?view=List
https://app.intercom.com/a/inbox/qge2vd8z/inbox/search/conversation/809?query=RPC Mode&sort=newest
https://app.intercom.com/a/inbox/qge2vd8z/inbox/search/conversation/772?query=RPC Mode&sort=newest
https://app.intercom.com/a/inbox/qge2vd8z/inbox/search/conversation/769?query=RPC Mode&sort=newest
https://app.intercom.com/a/inbox/qge2vd8z/inbox/search/conversation/768?query=RPC Mode&sort=newest
https://app.intercom.com/a/inbox/qge2vd8z/inbox/search/conversation/786?query=RPC Mode&sort=newest
https://app.intercom.com/a/inbox/qge2vd8z/inbox/search/conversation/763?query=RPC Mode&sort=newest

Looking at replacement options

@just-a-node Returned to QA and code review

https://github.com/connext/frontend/pull/70
Created a PR for this

Added private blast rpcs.


Remove usage of xargo and switch to cargo build-std

This should simplify quite some stuffs while building.

already done, should be closed

True, forgot about this PR


Replaces invalid HTML code with valid markdown

Invalid HTML code was used as a try to embed a YouTube video. As HTML is not supported, this code was replaced with valid markdown instead.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.


Sporadic ERR_ABORTED request error

Steps to reproduce
Tell us about your environment:

Puppeteer version: v1.5.0
Platform / OS version: macOS v10.13.5
Node.js version: v9.5.0

What steps will reproduce the problem?
Unfortunately, I can't provide access to the code as it's closed off, so this ticket will be useful only to the extent that others have a similar problem and chime in with a reproducible demo.
This error only occurs sporadically in headless mode and by sporadically I mean 50% of the time. It also seems to occur after puppeteer has been launched (and closed) twice before in the same script.
The same request that causes an "ERR_ABORTED" error works fine before it does not.
A breakpoint right at the entrance of my server code shows that no connection is made with my REST API when the "ERR_ABORTED" error occurs.
The same task is executed every time the puppeteer script runs, which is what confuses me the most.
The only other ticket that I see could be related to mine is: https://github.com/GoogleChrome/puppeteer/issues/2701, although my issue has nothing to do with serving a video file.

@maximedupre it's hard to say exactly what's going on. In general, requests can be aborted in many cases, e.g. if one attaches an iframe to DOM and then detaches it. In this case the request for the frame's main resource will be initiated and then aborted. The same happens to media resources and probably some other website assets.
I'm not sure how else I can help here; let me know if you have any further questions.


AttributeError: 'module' object has no attribute 'logamplitude'

Excuse me,the Error above confused me for a long time when I using feature-converter.py. I tried to google it, but there're nothing helpful. Can you tell me how to solve it? And another question is that did you develop this system on Mac OS?  :)

I used Mac Os for this! This error is from librosa?

I used Mac Os for this! This error is from librosa?
Yes,it was from librosa.


Breaking API changes in satori/go.uuid

The changes outlined in https://github.com/satori/go.uuid/issues/66 break the btree/immutable package. I guess the changes may or may not be reverted, based on the comments, but a fix might be in order.

I just hit this as well. I don't need btree yet so its not urgent, but this has been opened for 22 days.

I sent a PR removing go.uuid entirely. It was not contributing much.


On-run-end hook fails if model fails

We recently updated to 1.0 and it appeared that another package's  on-run-end hooks do not work.
It appeared that dbt_constraints on-run-end hook fails if any model with tests fails. Unfortunately DBT stops execution in case of on-run-end hook error.
on-run-end-hook-error 1.zip
How to reproduce:

Add debug DBT profile (Snowflake in our case)
dbt deps
dbt build
Check logs and check log message: on-run-end failed, error:

Full log:
12:38:21  Running with dbt=1.8.3
12:38:22  Registered adapter: snowflake=1.8.3
12:38:22  Unable to do partial parsing because saved manifest not found. Starting full parse.
12:38:24  [WARNING]: Deprecated functionality
The `tests` config has been renamed to `data_tests`. Please see
https://docs.getdbt.com/docs/build/data-tests#new-data_tests-syntax for more
information.
12:38:24  [WARNING]: Configuration paths exist in your dbt_project.yml file which do not apply to any resources.
There are 1 unused configuration paths:
- models.TFS_Debug.staging
12:38:25  Found 2 models, 1 operation, 2 data tests, 650 macros
12:38:25
12:38:27  Concurrency: 10 threads (target='denis')
12:38:27
12:38:27  1 of 4 START sql view model denis.stg_constraints .............................. [RUN]
12:38:27  2 of 4 START sql view model denis.stg_pass ..................................... [RUN]
12:38:29  1 of 4 OK created sql view model denis.stg_constraints ......................... [SUCCESS 1 in 1.36s]
12:38:29  2 of 4 OK created sql view model denis.stg_pass ................................ [SUCCESS 1 in 1.35s]
12:38:29  3 of 4 START test dbt_constraints_primary_key_stg_constraints_id ............... [RUN]
12:38:29  4 of 4 START test not_null_stg_pass_id ......................................... [RUN]
12:38:30  4 of 4 PASS not_null_stg_pass_id ............................................... [PASS in 1.50s]
12:38:30  3 of 4 ERROR dbt_constraints_primary_key_stg_constraints_id .................... [ERROR in 1.58s]
12:38:30
12:38:30  Running 1 on-run-end hook
12:38:30  Running dbt Constraints
12:38:30  Database error while running on-run-end
12:38:31
12:38:31  Finished running 2 view models, 2 data tests in 0 hours 0 minutes and 6.67 seconds (6.67s).
12:38:31
12:38:31  Completed with 2 errors and 0 warnings:
12:38:31
12:38:31    Database Error in test dbt_constraints_primary_key_stg_constraints_id (models\staging\stg_constraints.yml)
  100051 (22012): Division by zero
  compiled Code at target\run\Debug\models\staging\stg_constraints.yml\dbt_constraints_primary_key_stg_constraints_id.sql
12:38:31
12:38:31    on-run-end failed, error:
 '>' not supported between instances of 'NoneType' and 'int'
12:38:31
12:38:31  Done. PASS=3 WARN=0 ERROR=2 SKIP=0 TOTAL=5

The problem is in lookup_should_rely macro: it expects res.failures to be numeric.
{#- This macro that checks if a test has results and whether there were errors -#}
{%- macro lookup_should_rely(test_model) -%}
    {%- if test_model.config.where
            or test_model.config.warn_if != "!= 0"
            or test_model.config.fail_calc != "count(*)" -%}
        {#- Set NORELY if there is a condition on the test -#}
        {{ return('NORELY') }}
    {%- endif -%}

    {%- for res in results
        if res.node.config.materialized == "test"
        and res.node.unique_id == test_model.unique_id -%}
        {%- if res.failures > 0 -%}
            {#- Set NORELY if there is a test failure -#}
            {{ return('NORELY') }}
        {%- elif res.failures == 0 -%}
            {#- Set RELY if there are 0 failures -#}
            {{ return('RELY') }}
        {%- endif -%}
    {%- endfor -%}
    {{ return('') }}
{%- endmacro -%}

This has been resolved in the latest release. Thanks for reporting it!


Bluetooth: controller: Fix ll_cig_remove not cleaning up

When removing a CIG, the instance and associated CIS instances were not always released. This causes repeated Create_CIG/Remove_CIG operations to fail assertion with resource error.
Fixes issue #53301.
Signed-off-by: Morten Priess<EMAIL_ADDRESS>

Is this needed in addition to a consolidated list of changes to support Broadcast and Connected ISO in this PR: https://github.com/zephyrproject-rtos/zephyr/pull/52955?

Is this needed in addition to a consolidated list of changes to support Broadcast and Connected ISO in this PR: #52955?

In my opinion, the smaller the PRs we can submit to fix specific problems, the better traceability. Also, PR#52955 may take some time to get in, as we need to verify that it will still pass all CIS EBQ tests.

Is this needed in addition to a consolidated list of changes to support Broadcast and Connected ISO in this PR: #52955?

In my opinion, the smaller the PRs we can submit to fix specific problems, the better traceability. Also, PR #52955 may take some time to get in, as we need to verify that it will still pass all CIS EBQ tests.

#52955 is big as it is covered by upstream broadcast and unicast babblesim test.
I am not blocking this PR, just a comment that this PR change has no coverage upstream. Can a unit test be added?

I am not blocking this PR, just a comment that this PR change has no coverage upstream. Can a unit test be added?

Actually, there is a bsim test tests/bluetooth/bsim_bt/bsim_test_audio/src/unicast_client_test.c that can use it.
@mtpr-ot You could just add another change in this PR that enables CONFIG_BT_CTLR_CENTRAL_ISO in bsim_test_audio.
diff --git a/tests/bluetooth/bsim_bt/bsim_test_audio/prj.conf b/tests/bluetooth/bsim_bt/bsim_test_audio/prj.conf
index a7305b25cc..1c9830ea1e 100644
--- a/tests/bluetooth/bsim_bt/bsim_test_audio/prj.conf
+++ b/tests/bluetooth/bsim_bt/bsim_test_audio/prj.conf
@@ -166,3 +166,4 @@ CONFIG_BT_CTLR_ADV_ISO_STREAM_COUNT=1
 # Only 1 stream support by controller at this point
 CONFIG_BT_CTLR_SYNC_ISO_STREAM_MAX=1
 CONFIG_BT_CTLR_ISO_TX_BUFFERS=3
+CONFIG_BT_CTLR_CENTRAL_ISO=y


[MM-28216] Billing History View (UX Only)

Summary
Billing History table demo. UX only.
Includes a button so you can see what no billing history looks like.
Will merge this PR and submit a follow-up PR once the backend is complete.
Ticket Link
https://mattermost.atlassian.net/browse/MM-28216

Solid work @devinbinnie. Will we include pagination in another PR?

Thanks @matthewbirtch. The functionality will, but I think i'll add the UI for it now. Thanks for the reminder!

@matthewbirtch I added the paging section, can you have a quick glance?


Change "In depth guide" to "In-depth guide"

"In depth" should be changed to "In-depth".

It needs to be updated in a couple places:
https://github.com/donejs/donejs/search?utf8=✓&q="In+depth"&type=

Fixed by #913


Failed to build wheel for uninstallable depthai when setting up arducam on NVIDIA Jetson

Hi, I am working on arducam with NVIDIA Jetson.  During initial setup stage we are building the requriments by following the
arducam_imx283 branch of  depthai-experiments repos.
 depthai-experiments.
@jakaskerl  @Erol444
Help me to resolve the following error when running requirments.py file under  arducam_imx283 file gen2-color-isp-raw.
ERROR : Failed to build wheel for uninstallable depthai

@autonomy-123 that branch/library version is 4 years old. Could you try just on main branch, with latest depthai? AFAIK we have support for IMX283 already.

@autonomy-123 that branch/library version is 4 years old. Could you try just on main branch, with latest depthai? AFAIK we have support for IMX283 already.

@Erol444  thanks for your quick response. I will definitely try to build it on main branch. Can you just list me any additional changes needed along with latest depthai library?
I will connect back for further issues.

Likely zero changes, but let me know if there are issues and we'll try locally.

Likely zero changes, but let me know if there are issues and we'll try locally.

Likely zero changes, but let me know if there are issues and we'll try locally.

Hey, I tried running requirements.txt file under  depthai-experiments/gen2-color-isp-raw , not able to build properly
Tried running it on make, shows disutils module no found, on jetson its having issues with numpy==1.22
also tried updating the tools as shwon in errors for both environments didn't work.

@autonomy-123 just use latest depthai (2.28), and numpy anything below 2.0 (whatever works with your jetson).
I am now doing it in virtual environment. When I install depthai using

python3 -m pip install depthai  , it fials at building wheel & further erros comiingon terminal.
So how to do it? I m not getting any idea.

@autonomy-123 could you copy paste full log when trying to install depthai?

``

@autonomy-123 could you copy paste full log when trying to install depthai? Perhaps try python3 -m pip install depthai -U? We should have prebuilt wheels for all platforms. What python version are you using?

Yes with python3 -m pip install depthai -U , its not working. Followimg is the error
error: [Errno 2] No such file or directory: '/private/var/folders/9d/jpxxknzx3kj0l9nw_czwdnn40000gn/T/pip-install-uhuhh119/depthai_e727266910654248a8987ead8fb34fa1/utilities/cam_test.py'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for depthai
Failed to build depthai
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: pip install --upgrade pip

@autonomy-123 could you try with anything below 3.13? As it was released a month ago, we don't have wheels for it yet

@autonomy-123 could you try with anything below 3.13? As it was released a month ago, we don't have wheels for it yet

Yes earlier tried with 3.10 but was not working

@autonomy-123 what was output from 3.10?

@autonomy-123 what was output from 3.10?

It was disutils mdoule not found, installed setuptools didn't worked, then updated python even then not .

@autonomy-123 I don't think that's needed, code works for me even without it. Please also provide full log

@autonomy-123 I don't think that's needed, code works for me even without it. Please also provide full log

I will try once fresh , then will check & get back to you

@autonomy-123 I don't think that's needed, code works for me even without it. Please also provide full log

Hi @Erol444 ,
I started with fresh virutal environment, build with python 3.11 & updated the pip & setuptools depenedencies.
this time i was able to run requirments.txt in main barnch itself under gen2-color-isp-raw as you suggested above.
Now when i try to run main.py under same folder I am not able to see my camera feed for arducam imx283.
How to check it & fix it?
When running mai.py , following is the logs in terminal :
depthai version: <IP_ADDRESS> [2024-11-07 11:42:45.543] [depthai] [warning] [194430104185E61200] [0.1] Flashed bootloader version 0.0.19, less than 0.0.28 is susceptible to bootup/restart failure. Upgrading is advised, flashing main/factory (not user) bootloader. Available: 0.0.28 [194430104185E61200] [0.1] [9.004] [ColorCamera(0)] [error] Camera not detected on socket: 0
& its freeze here.

Do you have the IMX283 connected to CAM_A socket? Photos would be helpful @autonomy-123

Do you have the IMX283 connected to CAM_A socket? Photos would be helpful @autonomy-123

Yes sure, this is how we have connected it.

@autonomy-123 you have it connected to CAM_D, not CAM_A, could you move it?

@autonomy-123 you have it connected to CAM_D, not CAM_A, could you move it?

To which one, can you point ?

@autonomy-123 this one

@autonomy-123 you have it connected to CAM_D, not CAM_A, could you move it?

Yes i will try again, but before it was connected to the CAM_A itslef but same issue was there

@autonomy-123 this one

Yes tried switching but it still won't fix the issue. Below is the error.
I also updated depthai from 2.26 to 2.28
depthai version: <IP_ADDRESS> [2024-11-07 16:10:11.261] [depthai] [warning] [194430104185E61200] [0.1] Flashed bootloader version 0.0.19, less than 0.0.28 is susceptible to bootup/restart failure. Upgrading is advised, flashing main/factory (not user) bootloader. Available: 0.0.28 [194430104185E61200] [0.1] [7.611] [ColorCamera(0)] [error] Camera not detected on socket: 0

@autonomy-123 this one

Yes tried switching but it still won't fix the issue. Below is the error. I also updated depthai from 2.26 to 2.28
depthai version: <IP_ADDRESS> [2024-11-07 16:10:11.261] [depthai] [warning] [194430104185E61200] [0.1] Flashed bootloader version 0.0.19, less than 0.0.28 is susceptible to bootup/restart failure. Upgrading is advised, flashing main/factory (not user) bootloader. Available: 0.0.28 [194430104185E61200] [0.1] [7.611] [ColorCamera(0)] [error] Camera not detected on socket: 0

Hey @Erol444 ,
I solved the issue, it was with cable connecting arducam & FFC-4P ic .
thanks for your help.

Great to hear, thanks for the update!


Fix test/integration/feed_test.rb

This test does not operate properly under rake.  Running the command rake results in the following error.
Error:
FeedTest#test_feed_matches_fixture_file:
ActiveRecord::EnvironmentMismatchError: You are attempting to modify a database that was last run in development environment.
You are running in test environment. If you are sure you want to continue, first set the environment using:
    bin/rails db:environment:set RAILS_ENV=test

test/integration/feed_test.rb:16:in `block (2 levels) in <class:FeedTest>'
test/integration/feed_test.rb:13:in `block in <class:FeedTest>'

bin/rails test test/integration/feed_test.rb:22

We could easily add this command to the "rake test" command.  Then it'd automagically set up the test environment.

Unfortunately when adding it to the rake test command, if we want to run an individual test with
rails t test/integration/feed_test.rb
The command doesn't get carried out.  I am creating a pull request now with my proposed change.

That makes sense - the patch forces the environment to be correct just before running feed_test.


Clean-up Tasks for Merging WG GitOps with OpenGitOps Project

GitOps Working Group Leads to work with OpenGitOps project maintainers to:
[ ] update the WG meeting documents, and any other outstanding items, to point to open gitops
[ ] make a decision on the #wg-gitops slack channel (e.g. point to opengitops or vice versa and rename)
[ ] update the OpenGitOps project home page with current information/status
[ ] schedule a time to present to TAG App Delivery in a general meeting in May/June with an update on OpenGitOps project status

@scottrigby can we close this out? have all items been completed?

imho the wg cleaned up the repo and progresses further as OpenGitOps project. Therefore, this issue will be closed.


Make windows draggable

Capturing here from TODO.md to make sure it doesn't get lost.

Windows are draggable. There are some bugs, but it works. We should open Issues specific to those bugs. Closing this Issue.


Allow : in Author name.

Suport for names such as :Barry-Thomas-Paul: Moss
See: FOR THE CLAIM OF THE LIFE.
Resolves: python-poetry#

[ ] Added tests for changed code.
[ ] Updated documentation for changed code.

I'm really unclear on the purpose or value of this (and the linked site seems to be a combo of a sovereign citizen/world citizen/law of attraction sort of thing) -- but setuptools allows it, so I suppose we might as well.
It looks like we don't have any test coverage here -- could you please write a test with good and bad names?

I'm really unclear on the purpose or value of this (and the linked site seems to be a combo of a sovereign citizen/world citizen/law of attraction sort of thing) -- but setuptools allows it, so I suppose we might as well.
It looks like we don't have any test coverage here -- could you please write a test with good and bad names?

Short version Poetry is blocking my Lawful name.

Requires tests.

All current test are passing. I will add specific test and update PR.


[Storage] Add description for the attributes

Add description/documentation above abortSignal
https://github.com/Azure/azure-sdk-for-js/blob/05ee0fbe7639378744177bcaaed08e2edfa575c3/sdk/storage/storage-file/src/DirectoryClient.ts#L10-L20
Need to add some description for all the attributes(interfaces) in storage-blob.
https://github.com/Azure/azure-sdk-for-js/blob/feature/storage/sdk/storage/storage-blob/src/ContainerClient.ts

I have a PR up to improve documentation.

Closing as the work is already tracked by #2915.


[Migration] Deprecating common introspection data provider enabling configuration

Upto IS 5.11, all the registered OAuth introspection data providers can be enabled/disabled with the following config.
[oauth.grant_type.uma_ticket]
retrieve_uma_permission_info_through_introspection="true"

From 5.12.0-M18 onward, above configuration has been deprecated and IntrospectionDataProviders are registered as event listeners. Existing introspection data providers can be enabled using following configurations.
[event.default_listener.is_introspection_data_provider]
enable=true

[event.default_listener.uma_introspection_data_provider]
enable=true

Related product issue : https://github.com/wso2/product-is/issues/11351
Doc improvement : https://github.com/wso2/docs-is/pull/2562

Added to docs with https://github.com/wso2/docs-is/pull/2991, https://github.com/wso2/docs-is/pull/2997


Update upgrade.md

Container name uses dashes instead of underscores by default when using https://raw.githubusercontent.com/chatwoot/chatwoot/develop/docker-compose.production.yaml

@JosephDeFazio I don't follow. Could you please re-check?
root@ip-172-31-17-103:/home/ubuntu# docker ps
CONTAINER ID   IMAGE                       COMMAND                  CREATED      STATUS          PORTS                      NAMES
27969489e123   chatwoot/chatwoot:v2.12.1   "bundle exec sidekiq…"   4 days ago   Up 34 seconds   3000/tcp                   ubuntu_sidekiq_1
ad074ed30e26   chatwoot/chatwoot:v2.12.1   "docker/entrypoints/…"   4 days ago   Up 34 seconds   <IP_ADDRESS>:3000->3000/tcp   ubuntu_rails_1
175a90b2fd89   redis:alpine                "docker-entrypoint.s…"   4 days ago   Up 35 seconds   <IP_ADDRESS>:6379->6379/tcp   ubuntu_redis_1
d2cf105bad7d   postgres:12                 "docker-entrypoint.s…"   4 days ago   Up 34 seconds   <IP_ADDRESS>:5432->5432/tcp   ubuntu_postgres_1

root@ip-172-31-17-103:/home/ubuntu# docker exec -it $(basename $(pwd))_rails_1 sh -c 'RAILS_ENV=production bundle exec rails c'
I, [2023-01-30T13:00:42.657292 #32]  INFO -- : Skipping because: Rails console. Start manually with `ElasticAPM.start'
W, [2023-01-30T13:00:43.672602 #32]  WARN -- : Creating scope :open. Overwriting existing method Conversation.open.
W, [2023-01-30T13:00:43.736581 #32]  WARN -- : Creating scope :latest. Overwriting existing method Mention.latest.
Loading production environment (Rails <IP_ADDRESS>)
irb(main):001:0>

@vishnu-narayanan I'm not sure why ours are different, but you can see mine below has dashes in the container name. For reference, I'm on Docker version 20.10.17, build 100c701 and Docker Compose version v2.6.0.


fix(bun): :bug: Change bun invocation to bunx

Script should be invocated with bunx instead of bun, otherwise it throws an error regarding missing script.
It is a simple typo that may happen also with npm and npx.

Thanks @mjaroszek


Spec still references max_db_per_node (in an example)

It is the only use of the max_db_per_node field name in the spec. I assume it was recently removed but not from the last example.

Closing this as #151 fixes it


fail starting containers

I've program starting the containers with the plugin
mvn docker:start-containers
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building search-svc 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- docker-maven-plugin:3.0:start-containers (default-cli) @ search-svc ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.327 s
[INFO] Finished at: 2015-03-19T22:41:36-07:00
[INFO] Final Memory: 9M/238M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal net.wouterdanes.docker:docker-maven-plugin:3.0:start-containers (default-cli) on project search-svc: The parameters 'containers' for goal net.wouterdanes.docker:docker-maven-plugin:3.0:start-containers are missing or invalid -> [Help 1]
here's the config
<execution>
                        <id>start</id>
                        <goals>
                            <goal>start-containers</goal>
                        </goals>
                        <configuration>
                            <containers>
                                <container>
                                    <image>${project.name}:${project.version}</image>
                                </container>
                            </containers>
                        </configuration>
                    </execution>

maven version
mvn --version
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T06:51:42-07:00)
Maven home: /opt/apache-maven-3.2.2
Java version: 1.8.0_40, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.16.0-31-generic", arch: "amd64", family: "unix"
however, it can start & stop the container through the verify goal.
mvn verify
[INFO] --- docker-maven-plugin:3.0:build-images (build) @ search-svc ---
[INFO] Using docker provider: remote
[INFO] Building image 'search', with name and tag 'search-svc:1.0-SNAPSHOT'..
[INFO] Image 'search' has Id 'cf3e355fc5ce'
[INFO]
[INFO] --- docker-maven-plugin:3.0:start-containers (start) @ search-svc ---
[INFO] Using docker provider: remote
[INFO] Starting container 'search-svc:1.0-SNAPSHOT'..
[INFO] Setting property 'docker.containers.search-svc:1.0-SNAPSHOT.ports.8080/tcp.host' to '<IP_ADDRESS>'
[INFO] Setting property 'docker.containers.search-svc:1.0-SNAPSHOT.ports.8080/tcp.port' to '49155'
[INFO] Started container with id '77103f93ef186e6bb5b1812979176bdac57b66f7c263cc6483a1262d2dd2dc07'
[INFO]
[INFO] --- docker-maven-plugin:3.0:stop-containers (stop) @ search-svc ---
[INFO] Using docker provider: remote
[INFO] Stopping container '77103f93ef186e6bb5b1812979176bdac57b66f7c263cc6483a1262d2dd2dc07'..
[INFO] Deleting container '77103f93ef186e6bb5b1812979176bdac57b66f7c263cc6483a1262d2dd2dc07'..
[INFO] Keeping image cf3e355fc5ce
[INFO]
[INFO] --- docker-maven-plugin:3.0:verify (verify) @ search-svc ---
[INFO] Using docker provider: remote

Hmm, try moving the configuration outside the execution block, but in the root of the plugin definition. Does that help? I think the configuration in the execution block is only visible in the phase where that goal is registeren, which is "pre-integration-test" by default.

yes, it  works!  thanks


ci: reimpl release workflow

The former release workflow relied on rust-build/rust-build.action@latest which uses docker to setup the building environment. It's perfect if we do not rely externally on other system dependencies (which is why kafka-rust is preferable). But actually, macos build depends on openssl. rust-build.action does not provide the customizability to install openssl inside docker. So we have to rewrite the workflow (btw, it's based on ripgrep's workflow).
Eventually, maybe we can totally replace rdkakfa with kakfa-rust.

I had plan to implement with both kakfa-rust and rdkafka. But Kafka-rust is far from mature last year.


add new interface option for skipping interfaces and expand interface option to take multiple regexes

Description
Added an option to skip network interfaces specified by regexes so that users can have first-found logic without having to manually specify system/setup specific interfaces to skip by changing the code.
Requires/is required by projectcalico/calicoctl#1675
Addresses projectcalico/calicoctl#1555
Builds off of https://github.com/projectcalico/calico/pull/878
Testing

Added unit tests
Ran modified calicoctl commands against an image of these changes to verify that if regexes were specified, they would not be picked up to be used.

LGTM.  Should be good to go as soon as the calicoctl change has been merged.
Also, will need to be rebased off the latest master before we merge.

Tests require https://github.com/projectcalico/calico/pull/904 in order to pass


Replacing paragraph with heading for error summary (DAC audit) A

This was flagged in the DAC audit (p. 18):

The text of ‘There is a problem’ contained within the error summary is not marked up as a heading. As this text is used to introduce the same page skip link, this should be marked up as a heading to ensure screen reader users are given the same context as a sighted user gets from visual cues.

This PR implements the recommended fix.

Might be one to confirm with DAC as part of the current report, or in the next drop-in.
AFAIK a h2 before a h1 is OK e.g. to introduce navigation or other secondary content https://www.w3.org/WAI/tutorials/page-structure/headings/#main-heading-after-navigation. I think the main requirement is for heading to not skip around levels.
I'd expect it to be worse for the error summary title to be the h1 in this case, but I could easily be wrong.

I'd expect it to be worse for the error summary title to be the h1 in this case, but I could easily be wrong.

I think you're definitely right!
The gov.uk example has the h2 at the top before an h1, which is the opposite of what I thought was OK on reading mdn's docs.  https://design-system.service.gov.uk/components/error-summary/full-page-example/index.html. But it has convinced me so I'm fine.  I might ask at the next drop in anyway 👍🏻

Yeah we definitely should check 👍 WCAG is really fuzzy on this. Sounds like we're happy to ship this as is based on the recommendation in the report and that it matches GOV.UK here.

Thanks both! Now that I think about this more, I wonder if we should go back to David S' original suggestion and allow users to specify what element the title to be rendered as. This is not so much for the instances when the error summary is before h1 (because after reading the documentation I think it's fine but I'll pop a note in the ability net drop in doc). It's for  'Email this advice to yourself':

'Email this advice to yourself' is h2 and if 'There is a problem' is part of that section, should it not be h3?


Is it possible to choose default auth source?

Gitea version (or commit ref): 1.10.0+dev-60-gc5f9c0418
Git version:
Operating system: linux
Database (use [x]):

[ x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x ] Not relevant

How do you mean default? They all work at the same time

Thanks for answering
More like if its possible to disable some of the auth sources. E.g so that users can just interact with the oidc auth, and not the default gitea one.

@andloh Gitea support LDAP/mail/OAuth2 and etc. Is that what you mean?

No. The auth support is great. But i would like to disable some of them. So that users only have one auth source to interact with on the login page

Once role mapping is possible option to force OAuth2 auth source would be nice.

In addition to what @army1349 said, OIDC/OAuth2 Autoregistration (worked on in https://github.com/go-gitea/gitea/pull/5123) would also be useful to make login for existing OIDC accounts seamless.

I support this issue.

I worked around this by adding a redirect to Gitea's oauth URL in my webserver (nginx) in order to directly forward users to our OIDC/SSO logon page upon clicking "Sign in" in Gitea - maybe it helps others:
location                /user/login {
return                  302 https://git.com.de/user/oauth2/LibertaCasaSSO;
}

The last bit is the name of the authentication provider that was set in Gitea - best to just visit the Gitea sign-in page regularly, right-clicking on the SSO/OIDC button, and selecting the browsers "Copy Link" option.

Thanks for answering More like if its possible to disable some of the auth sources. E.g so that users can just interact with the oidc auth, and not the default gitea one.

The same request as #13606, will be implemented by #32687


Fatal error: Undefined class constant 'PARSE_EXCEPTION_ON_INVALID_TYPE' caused by adding YAML front matter

I'm getting the following error when attempting to compile a new Sculpin site:
Fatal error: Uncaught Error: Undefined class constant 'PARSE_EXCEPTION_ON_INVALID_TYPE' in /Users/opdavies/Code/freelance-clients/vendor/dflydev/dot-access-configuration/src/Dflydev/DotAccessConfiguration/YamlConfigurationBuilder.php:43
Stack trace:
#0 /Users/opdavies/Code/freelance-clients/vendor/dflydev/dot-access-configuration/src/Dflydev/DotAccessConfiguration/AbstractConfigurationBuilder.php(59): Dflydev\DotAccessConfiguration\YamlConfigurationBuilder->internalBuild(Object(Dflydev\DotAccessConfiguration\Configuration))
#1 /Users/opdavies/Code/freelance-clients/vendor/sculpin/sculpin/src/Sculpin/Core/Source/FileSource.php(96): Dflydev\DotAccessConfiguration\AbstractConfigurationBuilder->build()
#2 /Users/opdavies/Code/freelance-clients/vendor/sculpin/sculpin/src/Sculpin/Core/Source/FileSource.php(53): Sculpin\Core\Source\FileSource->init()
#3 /Users/opdavies/Code/freelance-clients/vendor/sculpin/sculpin/src/Sculpin/Core/Source/FilesystemDataSource.php(207): Sculpin\Core\Source\FileSource->__construct(Object(Dflydev\Ca in /Users/opdavies/Code/freelance-clients/vendor/dflydev/dot-access-configuration/src/Dflydev/DotAccessConfiguration/YamlConfigurationBuilder.php on line 43

It's an issue that I first noticed on my https://github.com/opdavies/sculpin-skeleton project, but I've replicated it using a brand new installation following the instructions on https://sculpin.io/download/#download-via-composer, though I've tried it with ^2.1 as there is a public release rather than the dev version.
The site will compile until I enter any values into the YAML front matter section. If the front matter is empty, it will compile, but throws the error as soon as soon as an arbitrary value is entered.
Here are the files that I've added:
composer.json:
{
  "require": {
    "sculpin/sculpin": "^2.1@dev",
    "dflydev/embedded-composer": "@dev"
  }
}

app/config/sculpin_site.yml:
---
sculpin_content_types:
  posts:
    enabled: false

Working index.md:
---
---
test

Failing index.md:
---
foo: bar
---
test

The same error occurs when using the .html.twig extension rather than .md.
I've tested with both 5.6.38 and 7.1.22 locally.

This is an issue with sculpin’s usage of the symfony yaml component - passing a Boolean was deprecated in a version of the component, so Sculpin was upgraded to use the constant, but the constant doesn’t exist in the earlier versions of the component.
In other words, composer.json and composer.lock are applying the wrong lower bound to the symfony/yaml package, IIRC. I’d like to get it fixed in all the places it’s currently wrong, but in the short term I think you can fix it by directly requiring the newer yaml component (probably '^3.4' would solve it)

Well, I think I was quite wrong with that suggestion. Still investigating.

Ah, here's a working workaround:
composer require "dflydev/dot-access-configuration v1.0.2"
I think I'll do a 2.1.2 release tonight to fix this.

And thanks for highlighting this issue! I had heard something was acting up but wasn't able to isolate it.

OK, I think it is fixed now (with the release of Sculpin 2.1.2). A local test seems to confirm. Thanks again for filing the issue!

Yep, is working after a composer update. Thanks @beryllium!


Add scalafmt check to Travis build

Adding a separate linting task that should prevent people from
accidentally pushing non-formatted code.

Can't that be in the same line so sbt doesn't have to be started twice?


Implement brainwallet

Title says it all really. Allow us to use the btc address as the hash.

Thanks for your interest in the project, however I'm not sure why seedcat would need a brain wallet implementation when using vanilla hashcat is probably sufficient.
The purpose of seedcat is to provide the fastest solution for BIP39 bitcoin wallets which is the modern standard.  I didn't want to get sidetracked by alternative standards or altcoins.

Hashcat itself doesn't have brainwallet support.

Sorry for the late reply.  I've been trying to find information about brain wallet specs and it seems like the term "brain wallet" is generic and could encompass several different kinds of hash functions.
Do you know if there is a brainwallet spec?


Undefined subroutine &CGI::link called

Test suite of 0.01 fails:
# $VAR1 = bless( {
#                  'lon' => '-0.09',
#                  'lat' => '51.5',
#                  'popup' => 'marker'
#                }, 'Geo::Leaflet::marker' );
# $VAR1 = [
#           bless( {
#                    'lon' => '-0.09',
#                    'lat' => '51.5',
#                    'popup' => 'marker'
#                  }, 'Geo::Leaflet::marker' ),
#           bless( {
#                    'lon' => '-0.11',
#                    'radius' => 500,
#                    'popup' => 'circle',
#                    'properties' => {
#                                      'fillColor' => '#f03',
#                                      'color' => 'red',
#                                      'fillOpacity' => '0.5'
#                                    },
#                    'lat' => '51.508'
#                  }, 'Geo::Leaflet::circle' ),
#           bless( {
#                    'coordinates' => [
#                                       [
#                                         '51.509',
#                                         '-0.08'
#                                       ],
#                                       [
#                                         '51.503',
#                                         '-0.06'
#                                       ],
#                                       [
#                                         '51.51',
#                                         '-0.047'
#                                       ]
#                                     ],
#                    'properties' => {},
#                    'popup' => 'polygon'
#                  }, 'Geo::Leaflet::polygon' )
#         ];
Undefined subroutine &CGI::link called at /home/cpansand/.cpan/build/2024110902/Geo-Leaflet-0.01-0/blib/lib/Geo/Leaflet.pm line 278.
# Looks like your test exited with 255 just after 9.
t/002_html.t ..
Dubious, test returned 255 (wstat 65280, 0xff00)
All 9 subtests passed

Unfortunately, I could not reproduce this issue on my platform (RPM: perl-CGI-3.63-4).  I assume that your CGI.pm does not understand use CGI qw{link}; but, I have no idea what versions of CGI.pm do or do not support that syntax.  I am working on porting from CGI.pm to HTML::Tiny 1.08 based on the recommendation at CGI::Alternatives.

Fixed in v0.02 commit 50bac07 by moving from CGI.pm to HTTP::Tiny.


git LFS issue when cloning

I am getting git-lfs smudge errors when I try to clone.  Does the error message look like a file you would expect to be cloned?
git clone https://github.com/aadhithya14/Open-Teach.git
Cloning into 'Open-Teach'...
remote: Enumerating objects: 6951, done.
remote: Counting objects: 100% (143/143), done.
remote: Compressing objects: 100% (65/65), done.
remote: Total 6951 (delta 87), reused 126 (delta 78), pack-reused 6808
Receiving objects: 100% (6951/6951), 511.87 MiB | 9.54 MiB/s, done.
Resolving deltas: 100% (3617/3617), done.
Updating files: 100% (12041/12041), done.
Downloading VR/Bimanual-Robot-Unity/Assets/Oculus/SampleFramework/Usage/Firebase/README.md (1.3 KB)
Error downloading object: VR/Bimanual-Robot-Unity/Assets/Oculus/SampleFramework/Usage/Firebase/README.md (28b6429): Smudge error: Error downloading VR/Bimanual-Robot-Unity/Assets/Oculus/SampleFramework/Usage/Firebase/README.md (28b6429da3cdbba903ab35ca4bdc6d3621ffcb8224a36564d17593bcf8b3ab9d): [28b6429da3cdbba903ab35ca4bdc6d3621ffcb8224a36564d17593bcf8b3ab9d] Object does not exist on the server: [404] Object does not exist on the server

Errors logged to /home/xxxxxx/projects/Open-Teach/.git/lfs/logs/20240501T123943.0248752.log
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: VR/Bimanual-Robot-Unity/Assets/Oculus/SampleFramework/Usage/Firebase/README.md: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

my git-lfs version.
git-lfs -v
git-lfs/3.0.2 (GitHub; linux amd64; go 1.18.1)

Thanks.  That is an improvement as the repo is now checked out and in a clean state, but i think the underlying issue is still there.
git clone https://github.com/aadhithya14/Open-Teach.git
Cloning into 'Open-Teach'...
remote: Enumerating objects: 6951, done.
remote: Counting objects: 100% (143/143), done.
remote: Compressing objects: 100% (65/65), done.
remote: Total 6951 (delta 87), reused 126 (delta 78), pack-reused 6808
Receiving objects: 100% (6951/6951), 511.87 MiB | 19.30 MiB/s, done.
Resolving deltas: 100% (3617/3617), done.
Updating files: 100% (12041/12041), done.
Encountered 2 file(s) that should have been pointers, but weren't:
	VR/Bimanual-Robot-Unity/README.md
	VR/Franka-Bot-Unity/README.md

But when I try to pull the lfs files they still can't be found
cd Open-Teach/; git lfs pull
[ffb934fc9f094ef320fc8d38eb141d8d962abdf92c8d4a2175011f94ac59fa18] Object does not exist on the server: [404] Object does not exist on the server
[033c03a7178a6763f9a8c644f8c2c8f7ddb167cd53d084ee1ff655b2d1b92634] Object does not exist on the server: [404] Object does not exist on the server
[e6c0777c2c08befdb34ebd130ef874a4a4d086667b658d782c1b218316b7ecf3] Object does not exist on the server: [404] Object does not exist on the server
[28b6429da3cdbba903ab35ca4bdc6d3621ffcb8224a36564d17593bcf8b3ab9d] Object does not exist on the server: [404] Object does not exist on the server
error: failed to fetch some objects from 'https://github.com/aadhithya14/Open-Teach.git/info/lfs'

Yes you can take those readme's out. Those readme's come together with the unity files. I will stash those. Apart from that you should be able to use the APK without the need of the unity codefiles. The unity codefiles are needed in case you want to make any changes to the source code of APK.