OIDC login to Gitea 500 error UserSignIn: oauth2: server response missing access_token despite it exists

Description
Hi, I'm trying to use kanidm as OIDC authentication source for Gitea, it used to work for the previous version of Gitea (I forgot the version), I've upgraded Gitea to the latest v1.20.2 since, and now after redirecting back to /usr/oauth2/Kanidm/callback, the page shows 500 and Gitea's error log says:
2023/08/09 07:56:50 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/oauth2/Kanidm for <IP_ADDRESS>:57572, 307 Temporary Redirect in 1.5ms @ auth/oauth.go:849(auth.SignInOAuth)

2023/08/09 07:37:27 ...rs/web/auth/oauth.go:923:SignInOAuthCallback() [E] UserSignIn: oauth2: server response missing access_token

2023/08/09 07:37:27 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/oauth2/Kanidm/callback?state=69fbc6a2-6e08-40e4-aa33-67e9ef226803&code=gAAAAABk00I2HwG8QH_0P40nva3-sqyXzled4Dres5sj1gYXTI5G1U0ToEpWRFRp2a5s8Z9BdGN07skh_4ix0NOZ8hv58nvhlFyRZ58zS_Sb7B31jNG_Cv1rv8ixzr9yKS2ozDQr1864XnniWJMo_TMwTwxTHzoA1cUNvN7DC9Y6Z56_5ay527AslKZwH5qMkCIS1Kac_sagGhK5CpMcDnvJAl0QDoLf8SdkF6D30SrclN6VleDww5aierC3dgUE0Z7-wLiIhiC2NhK8uhWWcTUrbx3LyruC6_XPVjGuDkr2e0O0ueLQkk_ypIf7WCCZ3TVaqJ4GE50l_Sv6bU2all6G-rpaz1NmlsVmYF8bH1w4C99xkdCWcXyTC1AC8cQ4Vgh7J3y5_1_5aeeiviUK3wE6Bto3CJMZBEXfKarY4w1jQf1QIYh1qeUr4Os4Rvidp8_iaDqxvdrRCmV2-XVex_qAXdF0ADrGj7nYkONPYshgilUE5ybRXclSPCAptdcwOVq5IxWRxGt5Tw36LSRr_vg3W592ptlh-JKD9V9Lte9GDC2VZk0gD5zPH6FVpCGgNKqbuEmMpp8z4t3kXEEcshZ7nZO0-YWJZRlTN8f756cdrzOxeb-MvDcu0ylrHw9c0TQwYmgiEL-754Y9xKAZjoZJQBxwRCRNdBGQPCxYcYY8chXHiROMEc1A8ZxyEIlVaTDb3J9m0qVwIJdQsUnH_Nj_xt8-R0P5gZVN6Nuw8PHGxkRWhzwbqag%3D for <IP_ADDRESS>:35320, 500 Internal Server Error in 354.9ms @ auth/oauth.go:886(auth.SignInOAuthCallback)

Which is strange, because on the Kanidm side there's no error and I've log the HTTP response with a debug reverse proxy in the middle, and access_token clearly exists:
kanidm-debug-proxy-1  | POST /oauth2/token HTTP/1.1                                                                                [34/1939]
kanidm-debug-proxy-1  | Host: idm.fusiongalaxy.cn
kanidm-debug-proxy-1  | Accept-Encoding: gzip
kanidm-debug-proxy-1  | Authorization: Basic Z2l0ZWE6ZHJDZzBmSFV4VDlVMlRadVlTYTRBRWNIazVnMzhTV2YzZXlydHAzYnFGSE5razRn
kanidm-debug-proxy-1  | Content-Length: 881
kanidm-debug-proxy-1  | Content-Type: application/x-www-form-urlencoded
kanidm-debug-proxy-1  | User-Agent: Go-http-client/2.0
kanidm-debug-proxy-1  | X-Forwarded-For: <IP_ADDRESS>
kanidm-debug-proxy-1  | X-Forwarded-Host: idm.fusiongalaxy.cn
kanidm-debug-proxy-1  | X-Forwarded-Proto: https
kanidm-debug-proxy-1  |
kanidm                | 41560c8a-9343-4d4f-96d9-1564a01c2d96 INFO     request [ 4.67ms | 2.80% / 100.00% ]
kanidm                | 41560c8a-9343-4d4f-96d9-1564a01c2d96 INFO     ┕━ handle_oauth2_token_exchange [ 4.54ms | 50.67% / 97.20% ]
kanidm                | 41560c8a-9343-4d4f-96d9-1564a01c2d96 INFO        ┕━ commit [ 2.17ms | 46.53% ]
kanidm-debug-proxy-1  | code=gAAAAABk0z6nnSEaZSB5z0ZWOH5KN1mlpb2tj8CZiBKYdr4geDQ18P0Ql-HMXX7VA0nMOb5RRQe1agJo6Mvz9j35nuTvjB8SzakMi5nztBmPi8O3veY
vI14BnoJ0_LNqvkMntdpFgsOIHFcLZZ2nP0myLkmI3EqQeZQPiCoA7eOxAjV0AxF6g7OR1iUHeO50C7kqwvKl3E8vzhHbTNteu3eafJA3-YfClr07FbUuXab2JLOXxUEgkDxj_BkIrr2p3QD
d38U6aa2HQq7V-i_UfVstjKd51dZhCS08AecWdZaU5cif9bNzsLUEIbOOE-n6BBioq1w8xcozwif91xhjuFDW-Y612907jHrj4tb_PUjErz32SKl-G3IWN3fyF9dHi7I8KsP2n3Kc7ew9lN3
c3PWseSni_A1f402bI_5IxAmeyAz-QNq-BKpyWkBIQ0ZjrxbGuqh1WqrocZU4I2eeKb3ynvVA-G5_U4wanCbHVOsB3N6R5M0fQEzkP7pNGQDWXBiaes1dOqVl_y8OQI3ZXSJITlbwYQjrli1
h44pvykkiQsJYXYXdleFhkxRpNIqA5WaM_sJXt37ZfDv0pdckW5aFnyR1BfUBBsqgZDwCjCiSvB93NvCXFpjP7g5wDjhp9wOZrMb98GOQzoTCruv_lEpfm-2dhw55lkSTZeZek0SPZSJrO0c
hXOj036fzyJfvrJMnzLB9Ts-7N5fsqREYaKvmuomBBNOLPXJIlBKKYXVnCcVzNg_Qzco%3D&grant_type=authorization_code&redirect_uri=https%3A%2F%2Fgitea.redacted.com%2Fuser%2Foauth2%2FKanidm%2FcallbackHTTP/1.1 200 OK
kanidm-debug-proxy-1  | Content-Length: 2150
kanidm-debug-proxy-1  | Access-Control-Allow-Origin: *
kanidm-debug-proxy-1  | Cache-Control: no-store no-cache max-age=0
kanidm-debug-proxy-1  | Content-Security-Policy: base-uri 'self' https:; default-src 'self'; form-action 'self' https:; frame-ancestors 'none';
img-src 'self' data:; script-src 'self' 'unsafe-eval' 'sha384-MrcW6ZMFYlzcLA8Nl+NtUVF0sA7MsXsP1UyJoMp4YLEuNSfAP+JcXn/tWtIaxVXM' 'sha384-Zao7ExRX
VZOJobzS/uMp0P1jtJz3TTqJU4nYXkdmsjpiVD+/wcwCyX7FGqRIqvIz'; worker-src 'none';
kanidm-debug-proxy-1  | Date: Wed, 09 Aug 2023 07:22:17 GMT
kanidm-debug-proxy-1  | Permissions-Policy: fullscreen=(), geolocation=()
kanidm-debug-proxy-1  | Pragma: no-cache
kanidm-debug-proxy-1  | Referrer-Policy: no-referrer-when-downgrade
kanidm-debug-proxy-1  | Strict-Transport-Security: max-age=86400
kanidm-debug-proxy-1  | X-Content-Type-Options: nosniff
kanidm-debug-proxy-1  | X-Kanidm-Opid: 41560c8a-9343-4d4f-96d9-1564a01c2d96
kanidm-debug-proxy-1  | X-Kanidm-Version: 1.1.0-beta.13
kanidm-debug-proxy-1  |
kanidm-debug-proxy-1  | {"access_token":"gAAAAABk0z6pmCVYFLfRWBaYqMNkzJYoiQYasCiPi6EKxjVpDKPfww0HWS45irMQlrh3byAJC-QldnyGeSX-vnMl4tEKHEGMHGefNcM
2mhtuoYgCEES4Kcmz2iZE6TdkZEP9azgE3tRe8IJ1ZZy12h-Ag7mVdMGkuovgm4i8JtMsROtZD_UDk5kFrSCie8YIGb1BYBu_dQmLyK153zy3rRv1YpQ4J2nfBw9YEosWdcnmMqPIotm9LnK
Zdr35sBD9cAoMawVrCYeDwODvwtc0NhxXK4t6Lz6GNGQXEWDTD1wwbq0GKQYd-92uO5jexI1QmA2RtUrm2U8y-5gGt-yYL-cvRuSFNqUUIBOSjGcQnrC_jM2j79V0P4-HPQuv_DPBEDcxk3V
b6XOp0cSvmYSbq7523DneVnu9NsyltsMVRdmAY1yn1iBYor_Z3YV037pBha3T8tHVWzl4X6gvYj62a7W_kDdoHeW9zQ==","token_type":"bearer","expires_in":900,"refresh_t
oken":"gAAAAABk0z6pYsD_2ZHgBXD1OYKHqE-JHAJ1jhEatlKKuXel351UHaIYR4RbO-cn4TzXF82jX1zKFnQgl3Rb-_w5tX6jvAvXhi_gkpDFyriSR2xCq4fdsDsuea5AEfTctqGO_8Q2G
kn3l7MnqFaNISxemv3YjvvyLsFvYVCzaSn8z2ahwI13Php4iL5vqHBL10NhTNHWk9RkQCsI3wdBumlNJzV8kHdUzxey7bPjzq-A8KZYoTd_HsAun5_0WGrCcTlhon07y2UAIQmLxs5S95Lql
DzPytn3Z8WkuQkK8mq8SvBhHgWoV2KOTF77zAaA2k5z60Nn8cfM-tDan0-vW2a8CuMhxXDKVX00xCTqJTXaYUL3KpOyXLeajH_Ip7lLhHsVCYeLh6kfBNJ_ktvy6fOgADWNcC5DP48zfaNhb
efH0i6_lkmzdv35-ArgdGsp2xVSSOrPtiI6","scope":"email groups openid profile","id_token":"eyJhbGciOiJFUzI1NiIsImtpZCI6IjlhZTQ1OGI1NGQyYTQ1YjY1NDY3Y
zY4YzkxYjVjZjdkNzA4MDBlOWMwMTJhY2M3NTQxYjY0NmY0OGEyODA1N2EiLCJ0eXAiOiJKV1QifQ.eyJpc3MiOiJodHRwczovL2lkbS5mdXNpb25nYWxheHkuY24vb2F1dGgyL29wZW5pZC
9naXRlYSIsInN1YiI6IjM0MzdlNWExLWRiMGUtNGVlYy1hZTg3LWRjNGE2NzdjOWMzMiIsImF1ZCI6ImdpdGVhIiwiZXhwIjoxNjkxNTY2NjM3LCJuYmYiOjE2OTE1NjU3MzcsImlhdCI6MT
Y5MTU2NTczNywiYXV0aF90aW1lIjpudWxsLCJhenAiOiJnaXRlYSIsIm5hbWUiOiLmnLHmmZPml7siLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJ6aHV4aWFvbWluIiwiZW1haWwiOiJ6aHV4aW
FvbWluQGZ1c2lvbmdhbGF4eS5jbiIsImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJzY29wZXMiOlsiZW1haWwiLCJncm91cHMiLCJvcGVuaWQiLCJwcm9maWxlIl0sImdyb3VwcyI6WyIwMDAwMD
AwMC0wMDAwLTAwMDAtMDAwMC0wMDAwMDAwMDAwMzUiLCIwMDAwMDAwMC0wMDAwLTAwMDAtMDAwMC0wMDAwMDAwMDAwMzYiLCI0NGU2MDEwOC0yZjcxLTRmZDEtYTkzZS03YTY1N2MyNmI0NW
UiLCI4MWZhNzIxOS00MmFjLTQyZDktOWM1NS03YjVkY2VjYzQ2YzgiLCJhYTEyNTA5NC1iZGZlLTRhYTUtOWZiZS0xZjc0Y2RjMWExNzYiLCI2M2I5NjRmYi00ZDQ5LTQ4NDItOTIxZS1jNz
VkNTA5ODkxZDAiLCIzNDM3ZTVhMS1kYjBlLTRlZWMtYWU4Ny1kYzRhNjc3YzljMzIiXX0.FPlruBHtRMXL1ikI90UX8HigIJxcr4Ad5axhPmzXTgtQ1pl4soAkdwbyvYfpGF5HZxQIOBOhHH
Nk6kZeSq1wpw"}

I have not renamed the OAuth2 application. It used to work with older version of Gitea, so I think the OIDC provider is fine, could this be a bug in the latest version?

Gitea Version
1.20.2
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
K8s
How are you running Gitea?
K8s with the official Helm chart
Database
PostgreSQL

Which provider did you use in fact?

@lunny https://kanidm.com/

Yes, with Kanidm it had worked once, but I've upgraded Gitea version since. I also logged the response from Authelia which is working, and compare with the Kanidm one, which has one more field refresh_token, don't think it could be the cause.

I can reproduce that (found this issue by googling for the very same problem). Following...

According to this writeup, it rather seems to be an issue with kanidm...
https://ashhhleyyy.dev/blog/2023-02-05-from-keycloak-to-kanidm

@pfalzsocial According to the blog post you posted, it should work with the latest Kanidm, however it's failing for me with the latest Kanidm 1.1.0-beta.13

@lunny @techknowlogick Any advice how I can debug further?

@NexZhu See the discussion here, this seems to be a fixed issue on Kanidm's side: https://github.com/kanidm/kanidm/discussions/2058
Though I do agree that Gitea's error message could do with refinement to indicate the actual problem.

The issue is that Kanidm was incorrectly returning a response without a correct content type header (for anyone who wants to know the answer without having to dig through all the issues/code). This is resolved in our devel images aka  rc.14. Sorry about the issues you had here @NexZhu :(

I have the same issue, on my first run to connect with GitHub I have web/auth/oauth.go:937:SignInOAuthCallback() [E] UserSignIn: could not find a matching session for this request. Then I go back to login and try once more, and it works.
Reproduced on different users.

@wxiaoguang should I open a new issue for GitHub ?
I also have DISABLE_REGISTRATION: true

I have the same issue, on my first run to connect with GitHub I have web/auth/oauth.go:937:SignInOAuthCallback() [E] UserSignIn: could not find a matching session for this request. Then I go back to login and try once more, and it works. Reproduced on different users.
This bug has been there for years, I only report it now

If it is a different problem, feel free to open a new issue with a reproducible setup (ideally by a docker compose with detailed steps), then if some people have time, they would take a look.

I believe we are running into the same issue with OIDC on Gitea 1.21.7.  In our case, we are authenticating against an Azure B2C tenant with a custom user flow. After we authenticate in the tenant, it redirects to the GItea callback and gives us error 500.
I stood up a dummy authentik docker to test this Gitea OIDC with and it works fine in the same instance. Something specific to the Azure B2C is causing the problem.
2024/03/06 02:46:35 ...rs/web/auth/oauth.go:937:SignInOAuthCallback() [E] UserSignIn: oauth2: server response missing access_token

2024/03/06 02:46:35 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/oauth2/azureb2c/callback?state=767d0f86-c4ef-4012-a7f3-8049791c792f&code=eyJraWQiOiJjcGltY29yZV8wOTI1MjAxNSIsInZlciI6IjEuMCIsInppcCI6IkRlZmxhdGUiLCJzZXIiOiIxLjAifQ..OUaJNMESA7glOvJ3.g_59tvq-jd_9dW-O5YEtm5lcD-K4Pne6BETJMd7cXVB0_uSLYVAEsgAr7e-CmJ0ImfS2hkTVf_sGqyj2WunK2CugpZGNgWG2WZcjkrAi2G8dVy-rOrRgO3UKwN35uI-LZTJ8F0SX8xdmv6ML_iPzD50bZzDxLtMFDU3u5Uo4BVLXqFxHyvYf4kZ2hNkT1Fs1YgitHUhGbmhN9HMEsA2cEplKYVrsAWl6KpH0-mDbIL6ENuir78Cg1-0ya23DXZpTO9vbBtOGhcHWUIBbXOrgBUaQQM0kdRo0voOqBVRY6uSZMLkDKLkBAHijffBkH4eA6TjnxBuJCvMiExpLniJriiTkHjE2wyjzG0KNNEosBZhxzdiw5P1ve3XaLyJTjj3__6viD6TJmXt3XPL1-k4_vXabsvfolXHwvL77Ra15nx0OS9I8Ibxjl9EjmI1a4rlh04lEG0PbxglhXj9w0C1MKAq46XEN.f4nXicml_eHJ8BKwMOYp6w for <IP_ADDRESS>:47874, 500 Internal Server Error in 642.6ms @ auth/oauth.go:886(auth.SignInOAuthCallback)

Setup in Gitea authentication:


Update pcluster architecture guidance

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

You have also some docs on IAM identity center setup here -> https://github.com/aws/amazon-vpc-cni-k8s/pull/3047

Thanks for the info! however, it would be a bit hard for user to jump around the repository and identify the right guidance, so I would prefer to have it in the same doc.


[DO NOT TOUCH] Comment on PR test

Test!

Compat issues with assembly Microsoft.Bot.Builder
Compat issues with assembly Microsoft.Bot.Builder


Make low level client use System.text.json

re-targeting #4211 to master
This introduces an IElasticsearchSerializer implementation for System.Text.Json.
TODO:

[ ] Remove LowLevelRequestResponseSerializer
[ ] Move Utf8Json to Nest
[ ] Make sure formatters the lowlevel client relies on are ported over

[ ] DynamicDictionaryFormatter

Long term plan is for Nest to move over to System.Text.Json as well but this will require significant investment in porting formatters over.

Kick this off again to see why clients-ci was failing.

rebased against master

canary packages are currently failing to be built for this because ILRepack cannot resolve the netstandard20 System.Text.Json assembly when running the "merge" for netstandard21. I've opened https://github.com/nullean/assembly-rewriter/pull/7 to allow AssemblyRewriter to sign the rewritten versioned canary packages, which would allow ILRepack to be removed, since it is only being used to sign the assembly in the master and 7.x branches.

@russcam this is starting to look good to me! Some updated on this on my end

clients-ci was silently failing open #5024 to remedy this on all integration branches.
Rebased this PR, clients-ci started failing because YamlMap is Dict<object, object> which System.Text.Json does not support. Added an additional converter for it.
clients-ci is now failing on 1 test where the its asserting { value: 5.0 } where { value: 5 } is returned. We have some leniency if numbers are compared directly but we do not (and should not) recursively patch assertion values. This is related to the yaml test failures you identified in the rust client. We don't need to solve this on this PR IMO.
Noticed some assertions in PostData.doc.cs were commented out (pretty sure I did that), uncommented them again and everthing was still green.

If you have time to:

ignore that test for now
run the docs generator to fix the stale docs check

I'm happy if we merge this to master 🎉

ResponseBuilder was asking the Utf8Json serializer to deserialize to DynamicDictionary.
I added a new System.Text.Json converter to handle this now.
This also updates DynamicValue to deal with the fact that deserializing to Dictionary<string, object> does not materialize object these remain JsonElement.

The failing integration tests relate to boost being available on some properties.
Merging this in!

Will follow up with a PR to:

Remove LowLevelRequestResponseSerializer
Move Utf8Json to Nest


minor updates

added some minor updates for easier use and responsiveness

added html and body 100% height to support height:100% for elements
added full-width and full-height helper classes
changed .mid_center's width attribute to max-width:320px in order to support smaller devices like iphone4 and iphone4s (screen size 320px )

I will try to update as much as I have time.

for the full height, I did this:
html {
  height:100%;
}

body, .full-height, .body, .main_container, .right_col {
  min-height: 100%;
}

When I locked the height to 100%, the background of the container (grey) stopped at 100% of viewport.

#275 - added.


Log - Enable the Charging Station filter in addtion to the "Smart Charging" filter

The charging station filters only the Source column

Correct but here Smart Charging source is always "Central Server" which is not helpful if you work on a specific charging station. Could we specify the charging station ID instead of "Central Server" which has no value in fact?

Smart Charging work at Site Area level.

As discussed we cannot filter inside the detailed area in MongoDB


Ideas on Screensaver within Channels

When the screensaver takes over while we are within a channel, it starts the Roku name screensaver even though I have chosen the PhotoView screensaver.  When I am on the menu screen, it starts the PhotoView screensaver like it is supposed to do.  Any ideas?

@Marvelguy -- I tested this and was not able to reproduce. Can you set your screensaver to 1 min, take a video and send to me showing this?  Email<EMAIL_ADDRESS>

Ok, here is a link to the video I made showing the issue.
https://photos.app.goo.gl/jCC7bABCKDgweajQA
Thanks!
Sam
On Thu, Jan 2, 2020 at 3:47 PM Chris Taylor<EMAIL_ADDRESS>wrote:

@Marvelguy https://github.com/Marvelguy -- I tested this and was not
able to reproduce. Can you set your screensaver to 1 min, take a video and
send to me showing this? Email<EMAIL_ADDRESS>—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chtaylo2/Roku-GooglePhotos/issues/288?email_source=notifications&email_token=AOFS5ESZM4SQLMELZXOIMWLQ3ZOHBA5CNFSM4KCGAN22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH7Q5EQ#issuecomment-570363538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFS5ES2WMM66BMEEC6OLP3Q3ZOHBANCNFSM4KCGAN2Q
.


chore: removed dead usePrepareContractWrite link

Description
removed dead usePrepareContractWrite link from TypeScript docs page
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Added in https://github.com/wagmi-dev/wagmi/commit/0b4d7ee5e37b61967b44c4dd1f8ab5cebf00d959 since I wasn't able to update the branch.


SDO upload / download - no timeout status return

Hello,
In the new version of can node (2.0) there is error in CO_SDOclientDownload / CO_SDOclientUpload functions: no return status
CO_SDOcli_endedWithTimeout, so using it like here:
		uint16_t timer1msDiff; 		do{ 			 /* Calculate time difference */ 			 timer1msDiff = timer1ms - timer1msPrev; 			 timer1msPrev = timer1ms; 			 ret = CO_SDOclientDownload(SDO_C, timer1msDiff*1000, 0, (CO_SDO_abortCode_t*)SDOabortCode,0,0); 		}while(ret > 0); 		CO_SDOclientClose(SDO_C);
it make infinity loop.

There was the problem inside SDO client. Not return value, but something else. However, SDO client has been recently heavily tested, some fixes were made in several places in both: master and newOD branch. So this makes problems no more.


ISPN-10866 Force Infinispan Wildfly extension to use jboss marshalling

https://issues.jboss.org/browse/ISPN-10866
This is necessary as the wildfly InfinispanExtension does not allow serialization to be configured via the DMR or XML. Therefore, we default to the old behaviour of using jboss-marshalling.

I guess we're keeping the protobuf changes for later @ryanemerson ?

@danberindei I don't think we're adding new features to the wildfly subsystem.

Then maybe we should also remove the protobuf-specific stuff we added in the tests earlier?

@danberindei that was for embedded usage in the contexts of wildfly. This is for utilising the InfinispanExtension on wildfly

I see. I'm not familiar with InfinispanExtension and I assumed it's always in use when an application depends on the Infinispan feature pack.

I see. I'm not familiar with InfinispanExtension and I assumed it's always in use when an application depends on the Infinispan feature pack.

No the InfinispanExtension is only loaded if the following are in the Wildfly extensions section of the xml:
<extensions>
        <extension module="org.infinispan.extension:${infinispan.module.slot}"/>
        <extension module="org.jgroups.extension:${infinispan.module.slot}"/>
        ....
</extensions>


disfetch: 1.21 -> 1.22

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/llathasa-veleth/disfetch/releases.
meta.description for disfetch is: "Yet another *nix distro fetching program, but less complex"
meta.homepage for disfetch is: "https://github.com/llathasa-veleth/disfetch"
meta.changelog for disfetch is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/r2bw6wxqzp7cbrr325rhy6rh3syq53ps-disfetch-1.22/bin/disfetch passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 1.22 in filename of file in /nix/store/r2bw6wxqzp7cbrr325rhy6rh3syq53ps-disfetch-1.22

directory tree listing: https://gist.github.com/ed5676d46a0b9f51f661c021d87b1711

du listing: https://gist.github.com/4ba528e6e0ccb425c7c3b8f1638b9489

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
disfetch

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r2bw6wxqzp7cbrr325rhy6rh3syq53ps-disfetch-1.22 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A disfetch https://github.com/r-ryantm/nixpkgs/archive/775cb72c891e65cd18a6a6039c5dcf41832641f1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r2bw6wxqzp7cbrr325rhy6rh3syq53ps-disfetch-1.22
ls -la /nix/store/r2bw6wxqzp7cbrr325rhy6rh3syq53ps-disfetch-1.22/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

disfetch

Maintainer pings
cc @llathasa-veleth for testing.

Result of nixpkgs-review pr 118982 run on x86_64-linux 1

1 package built:

disfetch


Is this you

https://www.codester.com/eduardofiorini
If it’s you can you make this available again
https://www.codester.com/items/10159/emoji-keyboard-in-c-net

Hello, it is already available again for purchase. Thank you!
Em qua., 28 de out. de 2020 às 11:30, Daszbin<EMAIL_ADDRESS>escreveu:

https://www.codester.com/eduardofiorini
If it’s you can you make this available again
https://www.codester.com/items/10159/emoji-keyboard-in-c-net
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/eduardofiorini/ci4cli/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIX7PTIK4RAO2USX7U5BA3SNA2JRANCNFSM4TCPPWJA
.


Update Test Unit

Description of the Change
Update Test Unit

Coverage increased (+1.0%) to 89.499% when pulling 42dae0f981338371995c391b72bec7ec3ab5f58d on ahdbk:master into 305571f11d22b0af4bca8cdd60c0eb09adc8557a on JsonSchema-JavaUI:master.


Migrate from AppVeyor to GitHub action

Useful link:
https://alessio.franceschelli.me/posts/dotnet/build-a-dotnet-library-with-github-actions/
Closes #28
Still to do:

[ ] Patch version before building

Current: AppVeyor patch
Option: AutoSemVerLib (fork to work as GitHub Action?)
Option: just add a custom patch step to use the GitHub Run Number on master builds?

[ ] Update README badge

GitHub Action build badge markdown:
![Build status](https://github.com/pi-top/pi-top-4-.NET-SDK/workflows/Publish%20to%20NuGet/badge.svg)

AppVeyor patching output:
Patching .NET Core project files
Patching PackageVersion in src\PiTop.Camera.nuget\PiTop.Camera.nuget.csproj...OK
Patching PackageVersion in src\PiTop.Camera.Psi.nuget\PiTop.Camera.Psi.nuget.csproj...OK
Patching PackageVersion in src\PiTop.MakerArchitecture.Expansion.nuget\PiTop.MakerArchitecture.Expansion.nuget.csproj...OK
Patching PackageVersion in src\PiTop.MakerArchitecture.Foundation.nuget\PiTop.MakerArchitecture.Foundation.nuget.csproj...OK
Patching PackageVersion in src\PiTop.MakerArchitecture.Foundation.Psi.nuget\PiTop.MakerArchitecture.Foundation.Psi.nuget.csproj...OK
Patching PackageVersion in src\PiTop.nuget\PiTop.nuget.csproj...OK

Do you want to migrate to actions?


Duplicated record with query

Hi there!
I have a problem with a query. The key of my table is compost of tree field: IdXYZ, IdDateFrom, IdCounter. My entity is:
    // ...
    public sealed class XYZRow : Row, IIdRow
    {
        [DisplayName("IdXYZ"), Column("IDXYZ"), PrimaryKey, ForeignKey("[dbo].[XYZTable]", "IDXYZ"), LeftJoin("jXXX"), TextualField("jXXXDescrizione")]
        public Int32? IdXYZ
        {
            get { return Fields.IdXYZ[this]; }
            set { Fields.IdXYZ[this] = value; }
        }

        [DisplayName("Date From"), Column("IDDateFrom"), PrimaryKey]
        public DateTime? IdDateFrom
        {
            get { return Fields.IdDateFrom[this]; }
            set { Fields.IdDateFrom[this] = value; }
        }

		// This value is 1 or 2
        [DisplayName("Id Counter"), Column("IdCounter"), PrimaryKey]
        public Int32? IdCounter
        {
            get { return Fields.IdCounter[this]; }
            set { Fields.IdCounter[this] = value; }
        }

        [DisplayName("Id"), Column("ID"), Identity]
        public Int32? Id
        {
            get { return Fields.Id[this]; }
            set { Fields.Id[this] = value; }
        }

        [DisplayName("Amount"), Size(16), Scale(2)]
        public Decimal? Amount
        {
            get { return Fields.Amount[this]; }
            set { Fields.Amount[this] = value; }
        }
       //...

When I have executed a query from SQL Management Studio, the result I get is,  correctly, two record:
SELECT * FROM [dbo].[XYZTable] as XYZ
 WHERE XYZ.IDXYZ = 10 AND XYZ.IDDateFrom = '2015-01-01'

Record 1: 10, '2015-01-01', 1
Record 2: 10, '2015-01-01', 2

When I execute this request in Serenity, I get eight entities:
    // ...
    var repos = new XYZRepository ();
    var lr = new ListRequest();

    lr.EqualityFilter = new Dictionary<string, object>
    {
          {  XYZRow.Fields.IdXYZ.PropertyName, IDValue },
          {  XYZRow.Fields.IdDateFrom.PropertyName, DateFromValue }
    };

    lr.ColumnSelection = ColumnSelection.Details;
    public List<XYZRow> test = (repos.List(RequestParams.Connection, lr)).Entities;

    // test.Count = 8
    // with the first four record duplicated, with key: 10, '2015-01-01', 1
    // with the second four record duplicated, with key 10, '2015-01-01', 2

I tried also in this manner:
       lr.Criteria = new Criteria(XYZRow.Fields.IdXYZ.PropertyName) == IDValue
                    & new Criteria(XYZRow.Fields.IdDateFrom.PropertyName) == IDDateFromValue;

but the resul is the same.
Can help me?
Thank you

Your LeftJoins probably returns duplicate records, in sql you dont have them, debug and see which

You are right.
In fact my LeftJoin(jXXX) in the entity is incomplet. The table jXXX has a key compost of two field IDXXX and IDDateFromXXX, but in the entity only one is tested. Is possibile specify more key of the LeftJoin int the row entity? eg:
SELECT *, *
FROM [dbo].[XYZTable] as XYZ
LEFT JOIN [dbo].[JXXXTable] as TWO
       ON XYZ.IDXYZ = TWO.IDXXX AND XYZ.IDDateFrom = TWO.IDDateFrom
WHERE ZYZ.IDXYZ = 10 AND XYZ.IDDateFrom = '2015-01-01'

There is the possibility of define an attribute ForeignKey with two or more fields?
[ForeignKey("[dbo].[XYZTable]", one: "IDXYZ", two: "IDDateFrom"), or repeat the attribute?
    // ...
    public sealed class XYZRow : Row, IIdRow
    {
        [DisplayName("IdXYZ"), Column("IDXYZ"), PrimaryKey]
        [ForeignKey("[dbo].[XYZTable]", "IDXYZ"), LeftJoin("jXXX")]
        [TextualField("jXXXDescrizione")]
        public Int32? IdXYZ
        {
            get { return Fields.IdXYZ[this]; }
            set { Fields.IdXYZ[this] = value; }
        }

        [DisplayName("Date From"), Column("IDDateFrom"), PrimaryKey]
        [ForeignKey("[dbo].[XYZTable]", "IDDateFrom"), LeftJoin("jXXX")]
        public DateTime? IdDateFrom
        {
            get { return Fields.IdDateFrom[this]; }
            set { Fields.IdDateFrom[this] = value; }
        }

Put LeftJoin on top of row, not field, than specify full join condition, e.g. t0.A = t1.X and t0.B = t1.Y

Perfect, you are my hero.
I had read this in the manual, but I forgot - sorry.
I will write in the Wiki.
Thank you very much.


windows defender

hi man thanks for this great project but the issue is when compiling runboo.exe windows defender delete it ans stop the exploit ; any idea how to bypass defender or just don't use runboo.exe !

don't use runboo.exe


Handle resolving a null field with @http

Discussed in https://github.com/tailcallhq/tailcall/discussions/2466

Originally posted by angristan July 19, 2024
With this example:
schema @server(port: 8000) @upstream(baseURL: "http://jsonplaceholder.typicode.com") {
  query: Query
}

type Query {
  users: [User] @http(path: "/users")
}

type User {
  id: Int!
  name: String!
  username: String!
  email: String!
  authorID: String

  posts: [Post]
    @http(
      path: "/posts"
      query: [{ key: "author_ids[]", value: "{{.value.authorID}}" }]
      batchKey: ["author_ids[]"]
    )
}

type Post {
  id: Int!
  title: String!
  body: String!
}

If authorID is not nil, it works as expected, however if it is nil, it calls /posts without any query param, thus returning unrelated posts.
Expected url
https://jsonplaceholder.typicode.com/posts?userId=
Actual url
https://jsonplaceholder.typicode.com/posts
By default this should be the behaviour

@angristan
Do we need the = in the end? Can we drop that like below?
- https://jsonplaceholder.typicode.com/posts?userId=
+ https://jsonplaceholder.typicode.com/posts?userId

/bounty 100$

/attempt #2467

Looks like we can drop the equal sign: https://stackoverflow.com/questions/4557387/is-a-url-query-parameter-valid-if-it-has-no-value
In the API I'm querying, providing posts?userId or posts?userId= yields the same result (nothing). I feel like posts?userId= might be safer, but that's just a gut feeling

Btw I don't know the codebase, but I got this working:
diff --git a/src/core/http/query_encoder.rs b/src/core/http/query_encoder.rs
index c978988f..c68d3356 100644
--- a/src/core/http/query_encoder.rs
+++ b/src/core/http/query_encoder.rs
@@ -51,7 +51,7 @@ pub fn convert_value(value: &async_graphql::Value) -> Option<String> {
         async_graphql::Value::String(s) => Some(s.to_string()),
         async_graphql::Value::Number(n) => Some(n.to_string()),
         async_graphql::Value::Boolean(b) => Some(b.to_string()),
-        _ => None,
+        _ => Some("".to_string()),
     }
 }

@@ -95,6 +95,18 @@ mod tests {
         assert_eq!(actual, expected);
     }

+    #[test]
+    fn test_encode_key_with_null_value() {
+        let encoder = QueryEncoder::RepeatedKey;
+        let values = Value::List(vec![]);
+        let arg_raw_value = Some(ValueString::Value(Cow::Borrowed(&values)));
+
+        let actual = encoder.encode("key", arg_raw_value);
+        let expected = Some("key=".to_string());
+
+        assert_eq!(actual, expected);
+    }
+
     #[test]
     fn test_encode_env_var() {
         let encoder = QueryEncoder::default();

Btw I don't know the codebase, but I got this working:

ye that's the problem I think

thanks @ssddOnTop :)


Navigation?

Hi, wondering if this component has keyboard navigation?
e.g. arrow up to move up a node,
arrow down to move down
arrow left to collapse node
arrow right to expand node.
moving nodes with ctrl arrow key.
etc.

good ideas, for the time being do not support this feature, I will consider adding these features in a later version, or you can contribute code


Added tests for complex types in ArgminL2Norm impl of primitive types

Codecov Report
Base: 92.24% // Head: 92.26% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (32032fb) compared to base (43a4846).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #289      +/-   ##
==========================================
+ Coverage   92.24%   92.26%   +0.02%
==========================================
  Files         119      119
  Lines       18004    18018      +14
==========================================
+ Hits        16607    16624      +17
+ Misses       1397     1394       -3

Impacted Files
Coverage Δ

argmin-math/src/primitives/l2norm.rs
100.00% <100.00%> (+7.89%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


🐛 V3 runAsync doesn't work

What's happening?
On docs is described:

But I think it needs update, cause request frame as first parameter and func (callback) as second parameter.

The callback function is never called. I saw that code reach the func on runOnAsyncContext function, but I think enter always on finally cause I can't see my log ok 2.

Reproduceable Code
No response
Relevant log output
No response
Camera Device
No response
Device
iPhone 14 Pro
VisionCamera Version
3.0.0
Can you reproduce this issue in the VisionCamera Example app?

[ ] I can reproduce the issue in the VisionCamera Example app.

Additional information

[ ] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

@manolo-battista did you find any solution for this ?

@manolo-battista did you find any solution for this ?

no, unfortunately I still didn't find any solution. For my projects at the moment I'm using runAtTargetFps to run lower FPS rate.
const frameProcessor = useFrameProcessor((frame) => {
  'worklet'
  console.log("I'm running synchronously at 60 FPS!")
  runAtTargetFps(2, () => {
    'worklet'
    console.log("I'm running synchronously at 2 FPS!")
  })
}, [])

Hi. Would've been great if you could've sent a PR for that to fix it in docs.
But in my tests, runAsync works - can you put a console.log in there to double check that it does not get called?
Can you reproduce it in the example app?

hey @mrousavy  i think we should keep this issue open, i'm facing the same issue since this function was released, can you provide a minimal example that's working for you?

UseCase1:
on background throws JSI rethrowing JS exception: Regular javascript function cannot be shared. Try decorating the function with the 'worklet' keyword to allow the javascript function to be used as a worklet."
  const myFn = (frameContext) => {
    "worklet";
    console.log("Here", frameContext);
  };

  const frameProcessor = useFrameProcessor(
    (frame) => {
      "worklet";
      runAsync(frame, () => {
        "worklet";
        console.log("my awesome log");
      });
    },
    []
  );

UseCase2:
do not throws anything onlogcat but frameContext is always undefined, the callback is not being triggered for some reason
  const myFn = (frameContext) => {
    "worklet";
    console.log("Here", frameContext);
  };

  const frameProcessor = useFrameProcessor(
    (frame) => {
      "worklet";
      runAsync(frame, myFn);
    },
    [myFn]
  );

oh wait
it seems that by design the frame it's not being passed to myFn as a callback prop, this forces us to uses arrow functions to hook the frame scope, also internal.decrementRefCount() is being called before my long running function finishes the execution, which causes a java.lang.IllegalStateException: Image is already closed,
https://github.com/mrousavy/react-native-vision-camera/blob/764897dcf119e26668b9fb6c6eb78f0e2993ffd1/package/src/FrameProcessorPlugins.ts#L50-L55

Wait what? not sure if I follow -

it seems that by design the frame it's not being passed to myFn as a callback prop

no you're right, you can just use the Frame inside your lambda directly, the lambda has no parameters.

there's no guarantees that internal.decrementRefCount() is being called after my long running function finishes the execution

Why not? It runs in finally, no?

@mrousavy yep you are totally right, i was very drunk that day sorry
found a pattern that doesn't make sense for me, example app works my app doesn't work, tried different combination of libs and now i'm using same version that's on example but it always end up with

i have a serie of frame processors at this moment running in sequence
something like this
const frameProcessor = (frame) => {
    'worklet';

     // processors
     const faces = faceDetectorProcessor(frame)
     const luminanceResults = luminanceDetectionProcessor(frame, faces)
     const spoofResults = antiSpoofingProcessor(frame);

    // callbacks
    handleSpoofingDetection(spoofResults)
    handleLuminanceDetection(luminanceResults)

},[handleSpoofingDetection, handleLuminanceDetection])

the problem is that at this point the frame are being deallocated when i finish my operations,
so i'm thinking to implement something like this, to drop some frames while my processors still running
const frameProcessor = (frame) => {
    'worklet';

    // just drop the frame
    if(!jsiUtil.finishedOperations) return;

    const frameCopy = jsiUtil.copyFrame(frame);

     // processors
     const faces = faceDetectorProcessor(frameCopy)
     const luminanceResults = luminanceDetectionProcessor(frameCopy, faces)
     const spoofResults = antiSpoofingProcessor(frameCopy);

    // cleanup frame copy
    jsiUtil.ReleaseFrameCopy()

    // callbacks
    handleSpoofingDetection(spoofResults)
    handleLuminanceDetection(luminanceResults)

},[handleSpoofingDetection, handleLuminanceDetection])

would be nice to hear your opinion on this temporary solution to make sure i'm not missing anything
some final notes:
i'm linking my lib with visionCamera.so and unwraping the frame, i've tried increment refcount before my operations and decrement on the last one, but it seems to be ignored need further investigation

Woah, that's a weird error. Can you add console.log statements to your code (begin and end of sync calls, and begin and end of async calls) and then also to the native Frame's release method?
This is weird and you shouldn't need such workarounds - it should just work magically with ref counting.

Haaa I found out, i have a monorepo with this structure
-- packages
---- playground
---- mylib
if i have reanimated in my lib i face this issue, removed reanimated from mylib and now i'm using it only in the playground, working like a charm

@mrousavy fyi it's reproducible on example app now

Wait so Reanimated makes it break? Yea it's a bit weird that Worklets and reanimated do the same thing... Maybe we can fix this compatibility for now and think about a better solution in the future.

Wait so Reanimated makes it break?

that's what i though because after removing reanimated i can do a console.log inside the runAsync,  however if i call any function inside it i got the same error

Similar issue here. Using @ismaelmoreiraa/vision-camera-ocr, any call to scanOCR using runAsync throws:
JSI rethrowing JS exception: Exception in HostFunction: java.lang.ClassNotFoundException: Didn't find class "com.facebook.jni.MapIteratorHelper" on path: DexPathList[[directory "."],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/lib64, /system/system_ext/lib64]]

Error: Exception in HostFunction: java.lang.ClassNotFoundException: Didn't find class "com.facebook.jni.MapIteratorHelper" on path: DexPathList[[directory "."],nativeLibraryDirectories=[/system/lib64, /system/system_ext/lib64, /system/lib64, /system/system_ext/lib64]]
    at call (native)
    at scanOCR (/Users/username/dev/app/node_modules/@ismaelmoreiraa/vision-camera-ocr/src/index.tsx:8:21)
    at fn (native)
    at anonymous (/Users/username/dev/app/packages/app/src/features/foo.tsx:18:27)
    at fn (native)
    at anonymous (/Users/username/dev/app/node_modules/react-native-vision-camera/src/FrameProcessorPlugins.ts:6:9)

runAtTargetFps works fine. Not using Reanimated at all in my project.

Btw.; here's an explanation and a fix: https://github.com/margelo/react-native-worklets-core/issues/136

This is not related to VisionCamera, but rather about Reanimated.
If you do not use Reanimated, runAsync works fine. If you do use Reanimated, you need to enable processNestedWorklets in the Reanimated's babel plugin. See https://github.com/software-mansion/react-native-reanimated/issues/5576 for more info

Enabling processNestedWorklets solved the error for me, but now this error pops up: Frame Processor Error: Value is undefined, expected an Object, js engine: VisionCamera
This is my code (from react-native-fast-tflite), note that the model is printed out, but then it shows the error, I'm trying to make the model not interfere with how the camera output is displayed in my app (it interferes on Android but not iOS):
  const frameProcessor = useFrameProcessor((frame) => {
    'worklet'

    const data = resize(frame, {
      size: {
        // center-crop
        x: (frame.width / 2) - (320 / 2),
        y: (frame.height / 2) - (320 / 2),
        width: 320,
        height: 320,
      },
      pixelFormat: 'rgb',
      dataType: 'uint8'
    })

    runAsync(frame, () => {
      'worklet'
      console.log(model)

      const output = model.runSync([data])

      const numDetections = output[0]
    })
  }, [model])

If I pass the frame into runAsync, I get this error:  ERROR  Frame Processor Error: Exception in HostFunction: no ArrayBuffer attached, js engine: VisionCamera
Not sure if I'm misunderstanding some fundamentals here.
"react-native-vision-camera": "^3.8.2",
"react-native-worklets-core": "^0.2.4",
"react-native-reanimated": "^3.6.1",

ArrayBuffers can't be shared (right @chrfalch?), do the resize also in runAsynx.

Correct.

Sorry, I meant that I passed the resize into runAsync and then I got this error, if that was what you were asking for: ERROR  Frame Processor Error: Exception in HostFunction: no ArrayBuffer attached, js engine: VisionCamera

Yeah - try to move the resize call also into runAsync.

I did that, and I get this error:
 ERROR  Frame Processor Error: Exception in HostFunction: java.lang.ClassNotFoundException: Didn't find class "com.mrousavy.camera.frameprocessor.Frame" on path: DexPathList[[directory "."],nativeLibraryDirectories=[/system/lib64, /system/product/lib64, /system/lib64, /system/product/lib64]], js engine: VisionCamera
When I use this code:
  const frameProcessor = useFrameProcessor((frame) => {
    'worklet'

    runAsync(frame, () => {
      'worklet'

      const data = resize(frame, {
        size: {
          // center-crop
          x: (frame.width / 2) - (320 / 2),
          y: (frame.height / 2) - (320 / 2),
          width: 320,
          height: 320,
        },
        pixelFormat: 'rgb',
        dataType: 'uint8'
      })
    })
  }, [])

I did that, and I get this error:  ERROR Frame Processor Error: Exception in HostFunction: java.lang.ClassNotFoundException: Didn't find class "com.mrousavy.camera.frameprocessor.Frame" on path: DexPathList[[directory "."],nativeLibraryDirectories=[/system/lib64, /system/product/lib64, /system/lib64, /system/product/lib64]], js engine: VisionCamera

that so weird, same problem here

From reading the error message, it looks like the reason the JNI class cannot be found in runAsync is because there is no JNI Environment set up on that specific Thread - which is weird, because we set it up here: https://github.com/margelo/react-native-worklets-core/blob/d8dae58ffac6b7050bb0b410b69acc621dcf74d8/cpp/WKTJsiWorkletContext.cpp#L147-L149
Is that not called when invoking a worklet from JS, @chrfalch ?

Hey @rodgomesc and @Cosmorider - a discord user posted a SIGABRT stacktrace with symbols attached so I was able to figure out that this came from JVisionCameraScheduler - can you guys maybe try if this PR fixes the issue for you? https://github.com/mrousavy/react-native-vision-camera/pull/2457

I'm not seeing the same error. I have this one when using runAsync:
Frame Processor Error: Exception in HostFunction: java.lang.ClassNotFoundException: Didn't find class "com.facebook.jni.MapIteratorHelper" on path: DexPathList[[directory "."],nativeLibraryDirectories=[/system/lib64, /system_ext/lib64, /system/lib64, /system_ext/lib64]], js engine: VisionCamera

The new PR does not fix this particular one.

@MSchmidt can you try to add a
facebook::jni::ThreadScope scope;

right at the top of this method: https://github.com/mrousavy/react-native-vision-camera/blob/02bc8a979c192707efc5d6e1f424812e36f6369f/package/android/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp#L35-L45
? Let me know if that works for you

@MSchmidt in any way to find a fix myself I would need you to also get me a symbolicated stacktrace/crash log just like the one I have posted in PR #2457.

A second idea would be that I am using JMap's iterator function here: https://github.com/mrousavy/react-native-vision-camera/blob/02bc8a979c192707efc5d6e1f424812e36f6369f/package/android/src/main/cpp/frameprocessor/JSIJNIConversion.cpp#L155-L166
..maybe you are using an older version of fbjni where the map iterator part doesn't exist yet, hence it cannot find com.facebook.jni.MapIteratorHelper?

facebook::jni::ThreadScope scope; added to package/android/src/main/cpp/frameprocessor/java-bindings/JFrameProcessor.cpp is not working.
It's the same as this one: https://github.com/mrousavy/react-native-vision-camera/issues/1791#issuecomment-1843543328
It's somehow related to reanimated still. Their plugin does something different from vision camera's. It works when reanimated is thrown out of the project. Which isn't an option though.

It's the same as this one: https://github.com/mrousavy/react-native-vision-camera/issues/1791#issuecomment-1843543328

Yea I still need a symbolicated stacktrace. The error linked above just tells me that something inside the Frame Processor crashed, but I need the native C++ stacktrace.
Also the guy (@gbark) said he is not using Reanimated in his project, which makes me doubt that this is something coming from reanimated.

Okay nevermind - I was able to reproduce this 💪 - this fixes the issue: https://github.com/margelo/react-native-worklets-core/pull/141 🎉

Fixed in react-native-worklets-core 0.3.0 🎉🥳

@mrousavy do you think it would be a good idea to include the worklet config param processNestedWorklets into the docs?

I'm unable ti resolve this error even after enabling processNestedWorklets in babel config


Fix previous bugfix which doesn't really solve the problem

As it turn's out sensorEnables are intentended to be part of settings.
we just did not realize when we set sensor enabled, it modify the settings
but not guarding it.

@jorishjanssen could you merge this ?


train sample 0022.jpg mislabeled

It is annotated with 0 humans but there is one in the middle of the image.

is there a place, where labelling issues are discussed? I am thinking of running cleanlab at some point to possibly find other issues.
Best,
Fabian

I would run object detection on the data to find the issues. See for instance cleanlab tutorial on finding detection issues and paper ObjectLab: Automated Diagnosis of Mislabeled Images in Object Detection Data


add global options css for query

like babel-loader :  https://github.com/babel/babel-loader/blob/master/index.js#L36

Sorry, already have lessLoader for global.


AttributeError: 'SparkContext' object has no attribute 'install_packages'

[Enter feedback here]
sc.install_packages("numpy==1.11.0")
import numpy as np
result:
Traceback (most recent call last):
File "/script.py", line 14, in
sc.install_packages("numpy==1.11.0")
AttributeError: 'SparkContext' object has no attribute 'install_packages'
so is this incorrect or have you not been precise enough?

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

ID: 95966e39-532d-fcb7-7f2a-d7386dc53862
Version Independent ID: da6bc455-2357-046a-63d8-145335f2945d
Content: Spark Library Management - SQL Server Big Data Clusters
Content Source: docs/big-data-cluster/spark-install-packages.md
Product: sql
Technology: big-data-cluster
GitHub Login: @WilliamDAssafMSFT
Microsoft Alias: wiassaf

Cannot reproduce. @yetanotherlogonfail do you have any more scenario/setup information to provide?
CC @DaniBunny


Add back a 'SecurityTokenDescriptor' like class for creating tokens.

SecurityTokenDescriptor was used as a simple mechanism create tokens. We should add back an updated version that makes sense with todays OM.  For example, Lifetime should not be in the class.
see #80

RC1 fixes. #300


Add accumulate to index_put_

Issue 758 is closed.
It says:
it you need the 'accumulate' argument on index_put, please open a new issue specifically calling for that.
I need "accumulate" in index_put_
My use-case: list of 2D indices with duplicates, which need to be rasterized over 2D canvas, summing up the duplicates.
I needed it for 2 projects already (physics & microbiology).
So far I have being using a trick with sparse-dense tensor conversion (for some reason, it adds values during the conversion instead of overriding them), but that is an undocumented feature and a questionable long-term solution.
Thank you!

This has not been forgotten. I'm onboarding additional engineering resources at Microsoft, and I'm going to use fixing this bug as a part of that process.


[Feature] Tracking mass and character's current ship

The new EIS API supports pulling a character's current ship (yay).
By the looks of it, this is can work alongside the other SSO scopes. Exact mass won't be possible because we can't pull down the fit, but it's a start.
Link to endpoint.

Looking more closely, it should be possible to match the ship's unique ID to the XML API. Caching might present a problem with the assets list having a 2 hour cache, but it's better than nothing.

doing anything with the xml api is kinda bad. it will get phased out with the current plan being 18 months from now. looking at long term use i wouldnt rely on APIs with counted days you can also make educated guesses about the mass of a ship given you know the hull and maybe assume one plate on an armor ship. not the exact science but good enough to not accidentally collapse a hole from non reduction

Sure, it might get phased out (CCP FoxFour said there was no plans at the
time before she left the company, so it may have changed).
But at present there is no other way to work this, so we have to make do.
And an exact calculation is better than an educated guess.
On Nov 8, 2016 6:21 PM, "ZarosTenjin"<EMAIL_ADDRESS>wrote:

doing anything with the xml api is kinda bad. it will get phased out with
the current plan being 18 months from now. looking at long term use i
wouldnt rely on APIs with counted days you can also make educated guesses
about the mass of a ship given you know the hull and maybe assume one plate
on an armor ship. not the exact science but good enough to not accidentally
collapse a hole from non reduction
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/exodus4d/pathfinder/issues/382#issuecomment-259291140,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMl_LlSKtDBKpM2v7LBahb8pOMmgbnyuks5q8QP2gaJpZM4KtAmq
.

be sure that it'll get phased out pretty quickly if feature parity is archieved in the 18 months the dev blog eluded to in the subsection "What about XML API and CREST?"
I'm not questioning that exact calculation is better but i'm questioning if it is worth the effort and dev time to dedicate to a feature requiring an API thats on a death timer

I heard talks about getting the assets endpoints in ESI. So maybe talk with the CCPers in the ESI channel and ask for an ETA on that.

Got an ETA of Soon(TM) so who knows. Ultimately, 18 months IS a decent chunk of time for it to be around and reliable. Though the time commitment is always up for debate.

Duplicate #313, guys , pls before you open any issue, try to look on current issues. Thanks.

Thought it closed, so I didn't check. My bad I guess.


change the way to build maro

Description
Use generated raw_backend.pyx file instead realtime generating from template, as backend code not always change.
Linked issue(s)/Pull request(s)

issue_number

Type of Change

[x] Non-breaking bug fix
[ ] Breaking bug fix
[ ] New feature
[ ] Test
[ ] Doc update
[ ] Docker update

Related Component

[x] Simulation toolkit
[ ] RL toolkit
[ ] Distributed toolkit

Has Been Tested

OS:

[ ] Windows
[ ] Mac OS
[ ] Linux

Python version:

[ ] 3.6
[ ] 3.7

Key information snapshot(s):

Needs Follow Up Actions

[ ] New release package
[ ] New docker image

Checklist

[ ] Add/update the related comments
[ ] Add/update the related tests
[ ] Add/update the related documentations
[ ] Update the dependent downstream modules usage

Codecov Report

Merging #268 (10ccfdc) into master (ab290a4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #268   +/-   ##
=======================================
  Coverage   64.37%   64.37%
=======================================
  Files         113      113
  Lines        5553     5553
=======================================
  Hits         3575     3575
  Misses       1978     1978

Flag
Coverage Δ

unittests
64.37% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

Codecov Report

Merging #268 (10ccfdc) into master (ab290a4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #268   +/-   ##
=======================================
  Coverage   64.37%   64.37%
=======================================
  Files         113      113
  Lines        5553     5553
=======================================
  Hits         3575     3575
  Misses       1978     1978

Flag
Coverage Δ

unittests
64.37% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


add http-json-query exporter into exporters list

https://github.com/coliquio/http-json-query-exporter

Hmm, there's also https://github.com/kawamuray/prometheus-json-exporter out there which is more popular and we do try to avoid duplication in this list.

@bsingr Thanks for the contribution, but I think more people are using the existing https://github.com/kawamuray/prometheus-json-exporter right now. However it doesn't seem to be currently maintained.
Plus, the prometheus-json-exporter is written in Go, so it should be a bit more efficient than a javascript service.

No problem @brian-brazil  @SuperQ. Did not know about the https://github.com/kawamuray/prometheus-json-exporter.
Compares to me sth. like so:
Pro https://github.com/coliquio/http-json-query-exporter

The transformation with http://jsonata.org/ are far more flexible that just jsonpath
It supports basically any kind of http request (not just GET) including headers etc.
Allows querying different http endpoints from a single process

Pro https://github.com/kawamuray/prometheus-json-exporter

I assume you are right with the superior effiency of using go
More people using it seems also like big plus


feat(dosbatch): change dosbatch delimiters

Change left and leftAlt delimiters to nestable REM  (extra space character is required) for security and compatibility reasons. Here is two (the shortest) of the many justifications:

tldr
generalized

Is the extra space actually required for the syntax to be valid? Including the space here is problematic since it might get doubled or not properly removed when uncommenting based on user settings. If it is actually part of the language spec (and not just a recommended style) then we can go ahead, just know that it doesn't cleanly solve the problem and forces some people to change their configurations to work around the other issues with this plugin not supporting spaces as part of delimiters.

@alerque

Is the extra space actually required for the syntax to be valid?

Yes, otherwise there will be an error when executing the command (see example below).
Input:
@echo off
REM echo commented
REMecho comment error
echo printed

Output:
"REMecho" is not recognized as an internal or external command,
operable program or batch file.
printed

Including the space here is problematic since it might get doubled or not properly removed when uncommenting based on user settings.

However, without the extra space and with the plugin's default settings, uncommenting the line will leave the space at the beginning.

If it is actually part of the language spec (and not just a recommended style)

The REM command is the only part of the language dedicated directly to commenting.

just know that it doesn't cleanly solve the problem and forces some people to change their configurations

Yes, may be. However, REM is better than :: because due to :: there is a chance to get a subtle, but possibly fatal, error during script execution.


Add BossBar Support

I would like to add various BossBar functionality, only available when running on versions of Spigot that have the BossBar API.

Ability for magic mobs to use boss bars for health
BossBar spell action
Spell cooldowns?
Mana display?
Active spells?

This is all done


Adds feature select depending on sum method required

Adds feature select depending on sum method required

Looks good, thanks!

Absolutely no problem!


[5.0.26] FixElementSize behavior errors when getting elements in the collapsed combo

Describe the bug / 问题描述
Using fix-element-size behavior, then collapse the group which has "fixed" element, it will get the error below

And I found it will get each element from the ElementController in the fixNodeLike()
When the group is collapsed, even though the nodeId is correct, but it still return undefined, see the code below
https://github.com/antvis/G6/blob/0ab5f8d1a3c14cd9037841f766b687d5c0bf3217/packages/g6/src/behaviors/fix-element-size.ts#L218C25-L218C35
Reproduction link / 重现链接
No response
Steps to Reproduce the Bug or Issue / 重现步骤
No response
G6 Version / G6 版本
🆕 5.x
Operating System / 操作系统
macOS
Browser / 浏览器
Chrome, Edge
Additional context / 补充说明
No response

@yvonneyx The issue is still exist.


Adhoc interop tests are running out of space

I've poked at it a bit, but without too much happy result. #22967 is currently failing due to running out of space when downloading the new docker image files: https://source.cloud.google.com/results/invocations/dc61bd22-6253-48e8-b99c-e5cab1831f27/log (the failure is far up the log, one needs to download the full log to see it properly)

Basically the issue is that we already have too many versions that are being tested and the way the test script works is to download all the images for a language first and after that we run all the tests for that language:
https://github.com/grpc/grpc/blob/a43082112f5a2e4ef475c8b9c364ca08349e201b/tools/interop_matrix/run_interop_matrix_tests.py#L302
https://github.com/grpc/grpc/blob/a43082112f5a2e4ef475c8b9c364ca08349e201b/tools/interop_matrix/run_interop_matrix_tests.py#L206
We'd need to modify the script to only download a bunch of releases for a given language at a time

@gnossen  can you take a look?

#23285 should resolve this.


RHOARDOC-1645: [cherry-pick] remove references to specific maven an JDK versions

[ ] Have you followed the guidelines in our Contributing document?
[ ] [v2] Have you created a JIRA and used it in the commit message?
[ ] [v4] Have you created a GitHub Issue and used it in the commit message?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[ ] Have you built the project locally prior to submission with mvn clean install?

Can one of the admins verify this patch?

ok to test

ok to test

So, frankly, I'm not sure what to think about this. The difference between Thorntail docs and the RHOAR Thorntail release notes is minor, and the suggestion to just leave out versions from Thorntail docs doesn't really remove the difference. It just muddies the water. I added suggestions that would IMHO make it better and consistent with the release notes.

The rationale was to reduce the maintenance burden by moving the version requirement only to the Release Notes, but if you believe this reduction goes too far, we'll keep it.

I understand the desire, but I don't want to treat the community project as a second-class citizen ;-)

@Ladicek I totally understand and agree, I'm probably just over-eager in adapting to the low staffing and high turnover.


Build sync fail - Why? and how to solve?

Failed to resolve: recyclerview-v7
Open File
Failed to resolve: espresso-idling-resource
Open File
Failed to resolve: espresso-contrib
Open File
Failed to resolve: espresso-core
Open File

@DharitParmar I was running on the same issue. In the below implementation, just swap the position of repository.
repositories {
        jcenter()
        google()
    }

allprojects {
    repositories {
        jcenter()
        google()
    }
}

Worked when i put google() in first place and then jcenter(). @dino9

@dino9 @pramodit Same here worked with google() first and then jcenter().
Why is it so? What is the reason?

are you Chinese or English?Cause i think ther're Chinese who use the github,so problem is coming ,why do you use English to discuss with others otherwise we're Chinese


[SPARK-49877][SQL] Change classifyException function signature: add isRuntime argument

What changes were proposed in this pull request?
The proposal is to update the classifyException function so that it can return either AnalysisException or SparkRuntimeException. This is achieved by adding a new parameter, isRuntime, and modifying the return type to be Throwable with SparkThrowable for compatibility with both types.

Why are the changes needed?
The changes are needed to allow the classifyException function to be used in execution part of the code.

Does this PR introduce any user-facing change?
No.

How was this patch tested?
Not needed.

Was this patch authored or co-authored using generative AI tooling?
No.

The tests are now passing. Could you make a review @MaxGekk? Thanks.

+1, LGTM. Merging to master.
Thank you, @ivanjevtic-db.


Missing jitpack release

This repo is not in line with other projects of yours. Those have been provided as jitpack packages.
Maybe intended, maybe an oversight.

This repo is available as initial version 1.0.0


Alt doesn't correctly accumulate errors

Rust version: N/A
nom version: 5.0.1
compilation features: N/A

The documentation for ParseError::or reads:

This function is used to compare errors generated in various branches of alt

And indeed, we can see that the implementation of alt correctly uses or to compose errors, on lines 126 and 139 of this snippet:
https://github.com/Geal/nom/blob/092df74d3565590f0cd414c1ec2e60b55535d0be/src/branch/mod.rs#L119-L145
However, the default implementation of ParseError::or is to discard the left-hand error in favor of the right hand error, and none of the error types (not even VerboseError) actually override this default:
https://github.com/Geal/nom/blob/851706460a9311f7bbae8e9b7ee497c7188df0a3/src/error.rs#L94-L116
This means that there's no way to recover parse failure information from alt branches, besides the last branch.

this has always been the behaviour in nom, and the point of exposing the ParseError trait was to let people decide how they want to implement it if it does not match. From my point of view, which is heavily influenced by serialization formats, error accumulation in alt is not useful: either the next char or byte was not the one we wanted and none of the errors will give more information, or we went into the right branch and got an error later, and fr those cases you can use cut to transform the Error in a Failure, to prevent alt from trying other branches

This is mostly about error reporting. From the ParseError docs:

It provides methods to create an error from some combinators, and combine existing errors in combinators like alt

`fn or(...): combines two existing error. This function is used to compare errors generated in various branches of alt

This would seem to imply that alt uses the methods in the ParseError trait to report errors in the branches. It currently does not do this.

As a follow up to this, the default implementation of or completely throws away one of the two branches, and every existing implementation of ParseError doesn't specialize it. I understand if VerboseError is supposed to be a single stack, but I'd expect some kind of error type that does retain that stuff.
For instance, the char combinator reports an error like "expected character '{' ". I'd expect a really verbose error to respond to a failure in this part of a string parser with "expected 'u' or 'n' or 'r' or 't'"
https://github.com/Geal/nom/blob/b889d7c7e1879e3ff0a79bde61972f6662ed9ea7/examples/string.rs#L69-L83

Quick follow-up: I've implemented the proposed error behavior in ErrorTree, part of my nom enhancements library nom-supreme https://docs.rs/nom-supreme/0.4.4/nom_supreme/error/index.html


fix: send votes to the immediate next leader

Problem
Votes are always sent to the "forward leader" which is defined as the leader of the slot which is 2 slots beyond our latest poh clock slot. This means that a vote for the third slot of a given leader's slot span will always be sent to the following leader for inclusion in the first slot of that leader's slot span. This adds an unnecessary slot of latency to votes because the vote could potentially land in current leader's fourth slot.
Summary of Changes

Send votes to the leaders of the next two slots to decrease vote latency

Fixes #

would be nice to have a better source of truth for the next leader

Yeah I was thinking we could use blockstore to find in-progress or potential descendants of the last voted slot. This change felt like a good quick fix though.

Problem
Votes are always sent to the "forward leader" which is defined as the leader of the slot which is 2 slots beyond our latest poh clock slot. This means that a vote for the third slot of a given leader's slot span will always be sent to the following leader for inclusion in the first slot of that leader's slot span. This adds an unnecessary slot of latency to votes because the vote could potentially land in current leader's fourth slot.
Summary of Changes

Send votes to the leaders of the next two slots to decrease vote latency

Fixes #

Hi @jstarry,
Is this not also applicable for all the transactions? I was assuming the next leader offset logic was the same for all of them.
[ pub const FORWARD_TRANSACTIONS_TO_LEADER_AT_SLOT_OFFSET: u64 =
https://github.com/anza-xyz/agave/blob/5263c9d61f3af060ac995956120bef11c1bbf182/sdk/program/src/clock.rs#L141](https://github.com/anza-xyz/agave/blob/5263c9d61f3af060ac995956120bef11c1bbf182/sdk/program/src/clock.rs#L141)
Regards and thanks,

Is this not also applicable for all the transactions? I was assuming the next leader offset logic was the same for all of them so this improvement would apply for everyone.

@StaRkeSolanaValidator yes the offset logic is also the same for general tx forwarding and could benefit from a similar fix. Keeping this PR scoped to votes right now because improving vote latency is a priority given TVC will be enabled soon.


Login fails after fixture:load. Appears to be related to 'Auto' vs 'Bcrypt' in config.

Here is what I have found when installing the demo app. (Symfony Version 4.3.5 / PHP 7.1.23)
Upon initial install, everything works great. I can login and I can log out without issue.
If I run doctrine:fixtures:load, I can no longer login afterwards.
I have found that running doctrine:query:sql before the doctrine:fixture:load shows Bcrypt encrypted passwords, and after doctrine:fixtures:load the passwords are Argon2 encrypted.
For a workaround, I have changed the config in the security.yaml from auto to bcrypt. If I rerun the doctrine:fixtures:load again after changing to bcrypt, I can then login again.
I noticed that bcrypt was showing up in the debugger as deprecated, so i figured I should submit an issue here.

Hello @icircletech , i just installed the Symfony Demo and the version is 4.3.3. The authentication works fine.
I just run a composer update and Symfony is now in 4.3.5. And i still don't have any authentication problem.
When you installed Symfony, you ran the symfony new --demo my_project command ?
Cheers 😉

Hello @abdounikarim, thank you for the reply 😉.  I installed using the symfony new my_project_name --demo in CLI.
Did you run ./bin/console doctrine:fixtures:load in CLI?   This command is what breaks my authentication.

@icircletech yes and i don't have any problem.

Let's close this old issue because we haven't received any similar feedback about this and authentication seem to be working as expected. Thanks.


Clean up SearchFor

I didn't really understand fluent interfaces when I made this, so I kinda made it up as I went along.  I need to refactor it so that is implemented with a better pattern.
Important need to ensure backward compatibility.
Specifically, I don't like how the fluent functionality is duplicated between static methods and extension methods.

Looking at it again, this is a correct fluent builder pattern.  I must have been thinking of something else...

If I ignore backward compatibility, I can make this a breaking change and just do it right.  I already have a breaking change in the queue...


Dialogs reappear on Orientation Change

With the new Version <IP_ADDRESS> Dialogs in DIalogFragments reappear on OrientationChanges. It doesn't happen on Version <IP_ADDRESS>.

That's the main purpose of using a dialog fragment. That's expected and intended Android framework behavior.

Okay, thank you. How can I prevent the DIalog from reopening if it was explicit closed by the user?
This is a Dialog I use in my App: https://github.com/RubenGees/Vocabletrainer/blob/master/app/src/main/java/com/rubengees/vocables/dialog/EvaluationDialog.java

Oh, it re-opens? I might have an idea of why.

Fixed

https://github.com/afollestad/material-dialogs/releases/tag/v<IP_ADDRESS>


In-depth integration with Github

Integrating with Github which covers SP, IDP and provisioning requirements. This also includes enhancing existing integrations points with Github.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Document project

Try to document the project as most as possible on Github ReadMe in order to make easy to any user level to run/understand the project

This is one issue that have to be opened for the live time of the project.


HTTP 429 Too Many Requests

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS:Windows 11
- Continue:0.8.52
- IDE:VS Code 1.92.1
- Model:llama-3.1-8b-instant
- config.json:

  "tabAutocompleteModel": {
    "title": "llama-3.1-8b-instant",
    "model": "llama3.1-8b",
    "contextLength": 131072,
    "apiKey": "********",
    "completionOptions": {},
    "provider": "groq"

Description
This occurred right after I opened a txt file to edit a couple of things. I wasn't using Continue or attempting any tab completions. As a matter of fact, I didn't even have the side tab with Continue open.
Looking at the 'Continue: LLM...' it appears that Continue sent* (see below) the contents of the TXT file I was reading over and over again until Groq's request limit prevented it from sending anymore. I received 5 of the HTTP 429 error messages (see screenshot below) all at once, so my guess is that it was sending the requests back to back without stopping.

Continue sent to Groq the following on repeat:
"==========================================================================
==========================================================================
Settings:
contextLength: 131072
model: llama3.1-8b
maxTokens: 2048
temperature: 0.01
stop: <fim_prefix>,<fim_suffix>,<fim_middle>,<file_sep>,<|endoftext|>,</fim_middle>,,

,
,/src/,#- coding: utf-8,```,
function,
class,
module,
export,
import
raw: true
log: undefined
############################################
<fim_prefix>
"The content of my txt..."
<fim_suffix><fim_middle>
...then it would repeat from the beginning..."

To reproduce
No response
Log output
console.ts:137 [Extension Host] Error generating autocompletion:  Error: HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions

{"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 1.969s. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}

    at customFetch (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104571:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at withExponentialBackoff (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104258:26)
    at _Groq._streamChat (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483821:26)
    at _Groq._streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483778:26)
    at _Groq.streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104668:26)
    at ListenableGenerator._start (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:96495:28)
C @ console.ts:137
notificationsAlerts.ts:42 HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions  {"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 1.969s. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}
c @ notificationsAlerts.ts:42
console.ts:137 [Extension Host] Error generating autocompletion:  Error: HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions

{"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 1.287s. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}

    at customFetch (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104571:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at withExponentialBackoff (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104258:26)
    at _Groq._streamChat (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483821:26)
    at _Groq._streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483778:26)
    at _Groq.streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104668:26)
    at ListenableGenerator._start (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:96495:28)
C @ console.ts:137
notificationsAlerts.ts:42 HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions  {"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 1.287s. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}
c @ notificationsAlerts.ts:42
console.ts:137 [Extension Host] Error generating autocompletion:  Error: HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions

{"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 399ms. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}

    at customFetch (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104571:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at withExponentialBackoff (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104258:26)
    at _Groq._streamChat (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483821:26)
    at _Groq._streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483778:26)
    at _Groq.streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104668:26)
    at ListenableGenerator._start (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:96495:28)
C @ console.ts:137
notificationsAlerts.ts:42 HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions  {"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 399ms. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}
c @ notificationsAlerts.ts:42
console.ts:137 [Extension Host] Error generating autocompletion:  Error: HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions

{"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 1.042s. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}

    at customFetch (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104571:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at withExponentialBackoff (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104258:26)
    at _Groq._streamChat (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483821:26)
    at _Groq._streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483778:26)
    at _Groq.streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104668:26)
    at ListenableGenerator._start (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:96495:28)
C @ console.ts:137
notificationsAlerts.ts:42 HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions  {"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 1.042s. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}
c @ notificationsAlerts.ts:42
console.ts:137 [Extension Host] Error generating autocompletion:  Error: HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions

{"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 1.006s. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}

    at customFetch (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104571:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at withExponentialBackoff (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104258:26)
    at _Groq._streamChat (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483821:26)
    at _Groq._streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483778:26)
    at _Groq.streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104668:26)
    at ListenableGenerator._start (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:96495:28)
C @ console.ts:137
notificationsAlerts.ts:42 HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions  {"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 1.006s. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}
c @ notificationsAlerts.ts:42
console.ts:137 [Extension Host] Error generating autocompletion:  Error: HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions

{"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 526ms. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}

    at customFetch (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104571:19)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at withExponentialBackoff (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104258:26)
    at _Groq._streamChat (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483821:26)
    at _Groq._streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:483778:26)
    at _Groq.streamComplete (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:104668:26)
    at ListenableGenerator._start (c:\Users\AlexJ\.vscode\extensions\continue.continue-0.9.211-win32-x64\out\extension.js:96495:28)
C @ console.ts:137
notificationsAlerts.ts:42 HTTP 429 Too Many Requests from https://api.groq.com/openai/v1/chat/completions  {"error":{"message":"Rate limit reached for model `llama-3.1-8b-instant` in organization `org_01ht7j91w5fjx8yabp2xh9hq37` on requests per minute (RPM): Limit 30, Used 30, Requested 1. Please try again in 526ms. Visit https://console.groq.com/docs/rate-limits for more information.","type":"requests","code":"rate_limit_exceeded"}}

facing same issue is this been resolved ?

facing same issue is this been resolved ?

Nope. This is the first response that I have gotten. As for me I just shut off tab completion so I could continue working.

bump

facing same issue is this been resolved ?

The closest thing to an answer that I have at the moment is located in this thread: https://github.com/continuedev/continue/issues/2457#issuecomment-2402693231

Amplifying.  I don't have this issue yet, but reading #2457 and #2343, I think commenters mistakenly think this (#2343) is a problem with the rate-limit, while the reporter makes a good case it's Continue stuck in a loop:

it appears that Continue sent* ... the contents of the TXT file ... over and over again until Groq's request limit prevented it from sending anymore. I received 5 of the HTTP 429 error messages ... all at once, so my guess is that it was sending the requests back to back without stopping.

There is a suggestion on the other thread that upgrading solves #2457. Maybe this too?

Amplifying. I don't have this issue yet, but reading #2457 and #2343, I think commenters mistakenly attribute this (#2343) to a problem with the rate-limit, while the reporter makes a good case it's Continue stuck in a loop:

it appears that Continue sent* ... the contents of the TXT file ... over and over again until Groq's request limit prevented it from sending anymore. I received 5 of the HTTP 429 error messages ... all at once, so my guess is that it was sending the requests back to back without stopping.

There is a suggestion on the other thread that upgrading solves #2457. Maybe this too?

Thank you for commenting! I'll look into the potential remedy.
To be honest, I've been working on some other things and haven't earnestly attempted to find a solution.

I received this error upon sending a message in chat. I reproduced it three times. The message and context was small. Disabling autocomplete (credit) allowed my next attempt to succeed.

I received this error upon sending a message in chat, without receiving a response. I reproduced it three times. The message and context was small. Disabling autocomplete (as mentioned) allowed my next attempt to succeed.
Update: Some requests later in the same chat (autocomplete still disabled), the error occurred again consistently. Restarting VS code did not help. Starting a new chat seemed to have resolved the error, but I instead just got the error after a response (instead of before).
Is this error making me lose credits faster?
I've been watching my credit usage in Anthropic since before the errors and after. It jumped up by $1 of usage after only a few messages (with errors). Previous interaction (of a similar scope) was taking only small fractions of cents at a time.
Update: This may be because I had one chat that became very long, and I read (somewhere) that with each message in a long chat, Claude re-reads the entire chat.

I'm sorry to hear that you are having the same issue as I am. Perhaps you should open another issue thread because I think that at this point this one is going to remain open. We all may have better luck if there are multiple threads active. Just mention this one in that thread and it will link our threads together.
To answer your last question specifically... Yes, this will increase your usage. If you are using a paid service I would suggest, like you have been, keeping a close watch because it will likely send things multiple times. If the context is long....well... then it will be a lot.
Since this has been unresolved I have become very proficient with Aider and Cline (formerly ClaudeDev). That has kind of become my "AI Tool Stack" of sorts. For refactoring, feature addition, and other edit focused tasks I use Aider from CLI and to get an idea out of my head, planned out, and at least a MVP I have been using Cline. I will be lost if they ever pay wall those tools....
Hope this helps.
Cheers.


node: Separate out construction of CacheAvailability into separate function that accepts an Availability

Separate out construction of CacheAvailability, have it accept a general availability.
Here and here

Hey renaynay, could I get a bit more context here? Would services.FullAvailability and services.LightAvailability even need to exist then, or could we just use share.NewFullAvailability and share.NewLightAvailability instead?
Or alternatively, is this more like what you meant?
// LightAvailability constructs light share availability wrapped in cache availability.
func LightAvailability(
	lc fx.Lifecycle,
	bServ blockservice.BlockService,
	ds datastore.Batching,
) share.Availability {
	la := share.NewLightAvailability(bServ)
	ca := share.NewCacheAvailability(la, ds)
	return ca
}

// FullAvailability constructs full share availability wrapped in cache availability.
func FullAvailability(lc fx.Lifecycle, bServ blockservice.BlockService, ds datastore.Batching) share.Availability {
	fa := share.NewFullAvailability(bServ)
	ca := share.NewCacheAvailability(fa, ds)
	return ca
}

func CacheAvailability(lc fx.Lifecycle, ds datastore.Batching, avail share.Availability) *share.CacheAvailability {
	ca := share.NewCacheAvailability(avail, ds)
	lc.Append(fx.Hook{
		OnStop: ca.Close,
	})
	return ca
}

Yes you're right regarding the fx package. The issue is that fx does not accept two instances of the same type, in this case, share.Availability.

ok thanks sounds fun will report back


feat: app-database-form update with new fields

Add new fields to the UI and allow updating. This stuff currently publishes directly which replicates the unverified app flow. Next feature will be the verification flow. These values are not displayed anywhere currently so it shouldn't present any risks.

Also removed some individual mutators in use
Uploading Screen Recording 2024-01-10 at 6.54.55 PM.mov…
app that are no longer needed like updatedescription and name

@paolodamico


contact form not working

error on sending

Failed to load resource:
https://api-v2.ecrin-rms.org/app/send-email
the server responded with a status of 404 ()

with the new BE the fields for the contact form are subject, message, recipients, sender. But in the UI we have more fields than this. So a decision should be made about the required fields and for the instance i have not made any functionality integration for the contact form.


Improve Workspaces docs page

Problem
https://doc.rust-lang.org/cargo/reference/workspaces.html is comprehensive, but could benefit from some clarifications and examples of how to create a workspace
Anyone trying to create a workspace would have to piece together multiple code snippets and go by trial and error.
Most people probably get it right the first time, but making it clearer in the docs will help.
Proposed Solution

explain the behavior of a root package (root mainfest, it has different names even in the source code 😓).
explain the resolver part where it is first mentioned
add examples of creating a workspace step-by-step, manual and/or using cargo commands
consider https://matklad.github.io/2021/08/22/large-rust-workspaces.html

Copied from and earlier discussion (https://github.com/rust-lang/cargo/issues/13579#issuecomment-1996186120)
Notes
Related:

Stems from #13579
#8365
#5151
#11234

We can deal with each proposed solution per pull request.

explain the behavior of a root package (or primary package or root mainfest, it has different names even in the source code 😓).

This might be the easiest one, by expanding this Root package section, though not sure what needs to be captured. I can think of one: root package becomes the default workspace member when no other specified.

explain the resolver part where it is first mentioned

This could be as simple as a link to Resolver versions section, if I understand correctly.

add examples of creating a workspace step-by-step, manual and/or using cargo commands
consider https://matklad.github.io/2021/08/22/large-rust-workspaces.html

These are covered by #11234 I believe.
While I am going to mark this as S-accepted, documenting Cargo's behavior often requires a deep understanding of Cargo. It implies more back-and-forth between contributors and maintainers in discussion if there are gaps between their familiarities in Cargo.

I may not have understood it accurately in this regard, but I'd like to try to address it. @rustbot claim

explain the resolver part where it is first mentioned

Cargo book workspace The chapters are already given a link when they first appear, so it seems like there's no need for extra explanation?

[workspace] — Defines a workspace.

resolver — Sets the dependency resolver to use.
...

From the comment.
Cargo Guide:

This guide will give you all that you need to know about how to use Cargo to develop Rust packages.

Cargo Reference:

The reference covers the details of various areas of Cargo.

Maybe Cargo Reference is more appropriate?
But I seem to have found something else.I looked at the previous chapters and realized that in 3.1 Specifying Dependencies mentions a lot of workspaces and may need to reorder the chapters. For example, put the 3.3 Workspaces section in front.

add examples of creating a workspace step-by-step, manual and/or using cargo commands
consider https://matklad.github.io/2021/08/22/large-rust-workspaces.html

In addition, it occurred to me that I could add a sub-section Creating a Workspace Example to Workspaces, as in 3.4.1 Features Examples and 3.8.1 Build Script Examples。

@epage @weihanglo , I've written a rough post to show my plan and would like your advice.

Creating a New Workspace
In this chapter we implement the creation of a workspace new_workspace from scratch, in which two members foo-bin and bar-lib are included.
As mentioned in  [workspace] section, the workspace must have at least one member, either the root package or a virtual manifest. Here we recommend setting the root of the workspace to be a virtual manifest. The reason is as follows:

The crate namespace at the Cargo level is flat. The tree layout creates another hierarchy and increases the possibility of inconsistencies.
With a flat structure, adding or splitting crates is very easy.
Even larger flattened lists are easier to see at a glance and easier to maintain than smaller tree structures.

Let's look at how a workspace containing a virtual inventory should be created.
Currently Cargo does not provide automatic creation of workspaces using the command line. You need to create the Cargo.toml file under the folder new_workspace:
# [new_workspace]/Cargo.toml
[workspace]

If using a virtual workspace, then the version of resolver needs to be specified in the table (if not, the default version of resolver for a workspace is 1, even if the default resolver version for workspace members is 2), for example:
[workspace]
resolver = "2"

You can then proceed to create workspace members. As mentioned above, if you have a lot of workspace members, we recommend designing the workspace with a flat structure. So add all the workspace members in the directory new_workspace/crates.
There are several ways to add members to the workspace, we recommend using the command cargo new/init. For example, add the members foo-bin and bar-lib to the workspace:
$ cargo new crates/foo-bin
$ cargo new crates/bar-lib

Cargo will automatically add members to Cargo.toml:
# [new_workspace]/Cargo.toml
[workspace]
resolver = "2"
members = [ "bar-lib","foo-bin"]

[package]
...

The project at this point contains the following files:
$ cd new_workspace
$ tree .
.
├── Cargo.toml
└── crates
    ├── bar-lib
    │   ├── Cargo.toml
    │   └── src
    │       └── main.rs
    └── foo-bin
        ├── Cargo.toml
        └── src
            └── main.rs

5 directories, 5 files

Up to this point, we have achieved creating a workspace that contains multiple crate members through a step-by-step process.

Maybe Cargo Reference is more appropriate?
In addition, it occurred to me that I could add a sub-section Creating a Workspace Example to Workspaces, as in 3.4.1 Features Examples and 3.8.1 Build Script Examples。

If we're adding a how-to to the reference, that feels backwards and out of place.
The existing "examples" sections are showing practices related to the reference, not tutorial-level documentation.  We could likely add one of those for workspaces but that is different than "Creating a workspace".  If we add a section hanging off of the reference, it would more likely be related to #11234.  This would also accomplish the high level goal set out in this issue (showing a cohesive picture of workspaces).

But I seem to have found something else.I looked at the previous chapters and realized that in 3.1 Specifying Dependencies mentions a lot of workspaces and may need to reorder the chapters. For example, put the 3.3 Workspaces section in front.

Personally, I'm not too worried about the exact ordering of the reference as it is reference level material and cross-references itself all over the place.  There isn't really a clear "start with this"

So, is it possible to reach a consensus on the following.
The location of the new section is 2.3 Creating a New Workspace. And, if it involves something that's ahead of its time, use a link to refer to it. The general content of the addition is the content of my earlier first draft.
Are there any other suggestions to discuss? If not can I proceed to the next step and submit a PR?