Mouse wheel scrolling not working

Description
Mouse wheel will not scroll folders in this app.   Windows file explorer scrolls with mouse wheel as it should.
Windows 10 Pro 22H2
Steps To Reproduce
Open app
Select folder in left window using right click
move mouse wheel
Requirements
Expected behavior is to scroll through folders in left pane of the app
Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.3448
Log File
debug.log

Thanks for the report,

Can you see if this is an issue in the preview version. https://files.community/download

If so and you have software called XMouse control? if so you can try creating a separate profile for Files.exe > Options > enable Disable Scroll Window Under Cursor

You can also try going to Windows Settings > Bluetooth & devices > Mouse > Enable Scroll inactive windows when hovering over them

Hi,
Changing the mouse setting to Scroll inactive windows when hovering over them   allows scroll to work.
But that setting shouldn’t be necessary. So, I tried installing an older revision.    https://files.community/download    sends me to the Microsoft store, where I could not find prior revs of the software
Thanks,
David
From: Josh65-2201 @.>
Sent: Tuesday, September 19, 2023 08:36 AM
To: files-community/Files @.>
Cc: Gitme76269 @.>; Author @.>
Subject: Re: [files-community/Files] Mouse wheel scrolling not working (Issue #13395)
Thanks for the report,

Can you see if this is an issue in the preview version. https://files.community/download
If so and you have software called XMouse control? if so you can try creating a separate profile for Files.exe > Options > enable Disable Scroll Window Under Cursor
You can also try going to Windows Settings > Bluetooth & devices > Mouse > Enable Scroll inactive windows when hovering over them

—
Reply to this email directly, view it on GitHub https://github.com/files-community/Files/issues/13395#issuecomment-1725427190 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQGEEAXHNZI2AEPHRK2F5RDX3GGRHANCNFSM6AAAAAA46B7AYA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AQGEEAWTFOSPL72L2Z7R5F3X3GGRHA5CNFSM6AAAAAA46B7AYCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTG27W7M.gif Message ID: @.*** @.***> >

Please check the preview version for the issue (Second button on the website), older ones are not available.

Thanks Josh
Insider Preview fixed it.
From: Josh65-2201 @.>
Sent: Tuesday, September 19, 2023 11:45 AM
To: files-community/Files @.>
Cc: Gitme76269 @.>; Author @.>
Subject: Re: [files-community/Files] Mouse wheel scrolling not working (Issue #13395)
Please check the preview version for the issue (Second button on the website), older ones are not available.
—
Reply to this email directly, view it on GitHub https://github.com/files-community/Files/issues/13395#issuecomment-1725921034 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AQGEEAS3I2WOP54UESICNZDX3G4WRANCNFSM6AAAAAA46B7AYA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AQGEEAS56COUXUJMSSSK4H3X3G4WRA5CNFSM6AAAAAA46B7AYCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTG353QU.gif Message ID: @.*** @.***> >


Install on MacOS build failed

Hi,
So I was trying to install pyre2 on my Mac following the steps described in the Installation.
And I encountered the following error when I tried to do the install.
The same error message occurs if I do pip3 install re2
Could you please help me with this?
Thank you for your time.
$ python3 setup.py install
running install
running build
running build_ext
building 're2' extension
creating build
creating build/temp.macosx-10.9-x86_64-3.8
creating build/temp.macosx-10.9-x86_64-3.8/src
gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/<HomePath>/opt/miniconda3/envs/ipa/include -arch x86_64 -I/<HomePath>/opt/miniconda3/envs/ipa/include -arch x86_64 -I/usr/local/include -I/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8 -c src/re2.cpp -o build/temp.macosx-10.9-x86_64-3.8/src/re2.o -std=c++11

(I removed all the warnings for unreachable code and explicit value assignment for simplity)

src/re2.cpp:14764:24: error: no member named 'exc_type' in '_ts'
    tmp_type = tstate->exc_type;
               ~~~~~~  ^
src/re2.cpp:14765:25: error: no member named 'exc_value' in '_ts'; did you mean 'curexc_value'?
    tmp_value = tstate->exc_value;
                        ^~~~~~~~~
                        curexc_value
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:79:15: note: 'curexc_value' declared here
    PyObject *curexc_value;
              ^
src/re2.cpp:14766:22: error: no member named 'exc_traceback' in '_ts'; did you mean 'curexc_traceback'?
    tmp_tb = tstate->exc_traceback;
                     ^~~~~~~~~~~~~
                     curexc_traceback
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:80:15: note: 'curexc_traceback' declared
      here
    PyObject *curexc_traceback;
              ^
src/re2.cpp:14767:13: error: no member named 'exc_type' in '_ts'
    tstate->exc_type = local_type;
    ~~~~~~  ^
src/re2.cpp:14768:13: error: no member named 'exc_value' in '_ts'; did you mean 'curexc_value'?
    tstate->exc_value = local_value;
            ^~~~~~~~~
            curexc_value
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:79:15: note: 'curexc_value' declared here
    PyObject *curexc_value;
              ^
src/re2.cpp:14769:13: error: no member named 'exc_traceback' in '_ts'; did you mean 'curexc_traceback'?
    tstate->exc_traceback = local_tb;
            ^~~~~~~~~~~~~
            curexc_traceback
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:80:15: note: 'curexc_traceback' declared
      here
    PyObject *curexc_traceback;
              ^
src/re2.cpp:14790:21: error: no member named 'exc_type' in '_ts'
    *type = tstate->exc_type;
            ~~~~~~  ^
src/re2.cpp:14791:22: error: no member named 'exc_value' in '_ts'; did you mean 'curexc_value'?
    *value = tstate->exc_value;
                     ^~~~~~~~~
                     curexc_value
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:79:15: note: 'curexc_value' declared here
    PyObject *curexc_value;
              ^
src/re2.cpp:14792:19: error: no member named 'exc_traceback' in '_ts'; did you mean 'curexc_traceback'?
    *tb = tstate->exc_traceback;
                  ^~~~~~~~~~~~~
                  curexc_traceback
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:80:15: note: 'curexc_traceback' declared
      here
    PyObject *curexc_traceback;
              ^
src/re2.cpp:14801:24: error: no member named 'exc_type' in '_ts'
    tmp_type = tstate->exc_type;
               ~~~~~~  ^
src/re2.cpp:14802:25: error: no member named 'exc_value' in '_ts'; did you mean 'curexc_value'?
    tmp_value = tstate->exc_value;
                        ^~~~~~~~~
                        curexc_value
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:79:15: note: 'curexc_value' declared here
    PyObject *curexc_value;
              ^
src/re2.cpp:14803:22: error: no member named 'exc_traceback' in '_ts'; did you mean 'curexc_traceback'?
    tmp_tb = tstate->exc_traceback;
                     ^~~~~~~~~~~~~
                     curexc_traceback
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:80:15: note: 'curexc_traceback' declared
      here
    PyObject *curexc_traceback;
              ^
src/re2.cpp:14804:13: error: no member named 'exc_type' in '_ts'
    tstate->exc_type = type;
    ~~~~~~  ^
src/re2.cpp:14805:13: error: no member named 'exc_value' in '_ts'; did you mean 'curexc_value'?
    tstate->exc_value = value;
            ^~~~~~~~~
            curexc_value
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:79:15: note: 'curexc_value' declared here
    PyObject *curexc_value;
              ^
src/re2.cpp:14806:13: error: no member named 'exc_traceback' in '_ts'; did you mean 'curexc_traceback'?
    tstate->exc_traceback = tb;
            ^~~~~~~~~~~~~
            curexc_traceback
/<HomePath>/opt/miniconda3/envs/ipa/include/python3.8/cpython/pystate.h:80:15: note: 'curexc_traceback' declared
      here
    PyObject *curexc_traceback;
              ^
75 warnings and 15 errors generated.
error: command 'gcc' failed with exit status 1

There's an active (and updated) fork available here:  https://github.com/andreasvc/pyre2 that builds fine on the CI macos runners.  take a look at the files in.github/workflows but essentially all you should need is brew to install re2 and then build away...


[KeyVault] - test out matrix-based multi-version-tests

Going to compare with the in-code based approach

/azp run js - keyvault-certificates - tests

/azp run js - keyvault-certificates - tests


Avatar in list duplicate

Reproduction link
https://wyquff.run.stackblitz.io/
Steps to reproduce
Add the following nz-list-item-meta to the nz-list-item
<nz-list-item-meta [nzAvatar]="nzAvatar" [nzTitle]="nzTitle" [nzDescription]="nzDescription">
<ng-template #nzTitle>
{{item.title}}

<ng-template #nzDescription>
{{item.description}}

<ng-template #nzAvatar>

What is expected?
Avatar should not be duplicated
What is actually happening?
Avatar is duplicated

Environment
Info

ng-zorro-antd
9.0.0-beta.1

Browser
Chrome latest

Could not get beta1 stackblitz examples to work so put in the default link


NoneType exception occured on payment

As i try to paste a payment invoice into my LNBits interface and click pay, red notification is displayed with "500"
Some logs from service found:

The invoice was created by a BTCPay Server behind TOR. The payment is displayed as pending in LNBits.
Another payment to an eclair invoice was recently successful. Lntxbot gets payed too via my lnbits wallet. So my node seems basically work.
// My BTCPay Server does not have a working channel open, so no route to host seems legit?

Can you help us debug by adding a line specifically before that preimage = base64.b64decode(...) line?
Just add print('DATA', data) there, then restart LNbits and try again. View the logs again and tell us what the new logs show.

added as line 103 and restarted lnbits service. i cant find your print here even the line is now 104. Maybe its not part of journal logging?
-- Logs begin at Mon 2021-04-05 21:17:59 BST. --
Apr 06 07:49:21 raspberrypi systemd[1]: Stopping lnbits...
Apr 06 07:49:21 raspberrypi systemd[1]: lnbits.service: Main process exited, code=killed, status=15/TERM
Apr 06 07:49:21 raspberrypi systemd[1]: lnbits.service: Succeeded.
Apr 06 07:49:21 raspberrypi systemd[1]: Stopped lnbits.
Apr 06 07:49:21 raspberrypi systemd[1]: Started lnbits.
Apr 06 07:49:25 raspberrypi sh[18959]: [2021-04-06 07:49:25 +0100] [18961] [INFO] Running on http://<IP_ADDRESS>:5000 (CTRL + C to quit)
Apr 06 07:51:02 raspberrypi sh[18959]: [2021-04-06 07:51:02,687] ERROR in app: Exception on request POST /api/v1/payments
Apr 06 07:51:02 raspberrypi sh[18959]: Traceback (most recent call last):
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart_trio/app.py", line 143, in handle_request
Apr 06 07:51:02 raspberrypi sh[18959]:     return await self.full_dispatch_request(request_context)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart_trio/app.py", line 165, in full_dispatch_request
Apr 06 07:51:02 raspberrypi sh[18959]:     result = await self.handle_user_exception(error)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart_trio/app.py", line 178, in handle_user_exception
Apr 06 07:51:02 raspberrypi sh[18959]:     return await super().handle_user_exception(error)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart/app.py", line 1076, in handle_user_exception
Apr 06 07:51:02 raspberrypi sh[18959]:     raise error
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart_trio/app.py", line 163, in full_dispatch_request
Apr 06 07:51:02 raspberrypi sh[18959]:     result = await self.dispatch_request(request_context)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart/app.py", line 1882, in dispatch_request
Apr 06 07:51:02 raspberrypi sh[18959]:     return await handler(**request_.view_args)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/lnbits/decorators.py", line 55, in wrapped_view
Apr 06 07:51:02 raspberrypi sh[18959]:     return await view(**kwargs)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/lnbits/core/views/api.py", line 139, in api_payments_create
Apr 06 07:51:02 raspberrypi sh[18959]:     return await api_payments_pay_invoice()
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/lnbits/decorators.py", line 28, in wrapped_view
Apr 06 07:51:02 raspberrypi sh[18959]:     return await view(**kwargs)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/lnbits/decorators.py", line 55, in wrapped_view
Apr 06 07:51:02 raspberrypi sh[18959]:     return await view(**kwargs)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/lnbits/core/views/api.py", line 121, in api_payments_pay_invoice
Apr 06 07:51:02 raspberrypi sh[18959]:     raise exc
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/lnbits/core/views/api.py", line 114, in api_payments_pay_invoice
Apr 06 07:51:02 raspberrypi sh[18959]:     payment_hash = await pay_invoice(wallet_id=g.wallet.id, payment_request=g.data["bolt11"])
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/lnbits/core/services.py", line 131, in pay_invoice
Apr 06 07:51:02 raspberrypi sh[18959]:     payment: PaymentResponse = WALLET.pay_invoice(payment_request)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/home/lnbits/lnbits/lnbits/wallets/lndrest.py", line 104, in pay_invoice
Apr 06 07:51:02 raspberrypi sh[18959]:     preimage = base64.b64decode(data["payment_preimage"]).hex()
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/usr/lib/python3.7/base64.py", line 80, in b64decode
Apr 06 07:51:02 raspberrypi sh[18959]:     s = _bytes_from_decode_data(s)
Apr 06 07:51:02 raspberrypi sh[18959]:   File "/usr/lib/python3.7/base64.py", line 46, in _bytes_from_decode_data
Apr 06 07:51:02 raspberrypi sh[18959]:     "string, not %r" % s.__class__.__name__) from None
Apr 06 07:51:02 raspberrypi sh[18959]: TypeError: argument should be a bytes-like object or ASCII string, not 'NoneType'

Ok, since you said that I think the issue is that we're not capturing the error properly.

Can you upgrade to master or apply this change manually and see what happens?

Can you upgrade to master or apply this change manually and see what happens?

here we go :+1:
Apr 06 14:27:02 raspberrypi sh[11994]: [2021-04-06 14:27:02 +0100] [11998] [INFO] Running on http://<IP_ADDRESS>:5000 (CTRL + C to quit)
Apr 06 14:28:48 raspberrypi sh[11994]: [2021-04-06 14:28:48,575] ERROR in app: Exception on request POST /api/v1/payments
Apr 06 14:28:48 raspberrypi sh[11994]: Traceback (most recent call last):
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart_trio/app.py", line 143, in handle_request
Apr 06 14:28:48 raspberrypi sh[11994]:     return await self.full_dispatch_request(request_context)
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart_trio/app.py", line 165, in full_dispatch_request
Apr 06 14:28:48 raspberrypi sh[11994]:     result = await self.handle_user_exception(error)
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart_trio/app.py", line 178, in handle_user_exception
Apr 06 14:28:48 raspberrypi sh[11994]:     return await super().handle_user_exception(error)
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart/app.py", line 1076, in handle_user_exception
Apr 06 14:28:48 raspberrypi sh[11994]:     raise error
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart_trio/app.py", line 163, in full_dispatch_request
Apr 06 14:28:48 raspberrypi sh[11994]:     result = await self.dispatch_request(request_context)
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/venv/lib/python3.7/site-packages/quart/app.py", line 1882, in dispatch_request
Apr 06 14:28:48 raspberrypi sh[11994]:     return await handler(**request_.view_args)
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/lnbits/decorators.py", line 55, in wrapped_view
Apr 06 14:28:48 raspberrypi sh[11994]:     return await view(**kwargs)
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/lnbits/core/views/api.py", line 139, in api_payments_create
Apr 06 14:28:48 raspberrypi sh[11994]:     return await api_payments_pay_invoice()
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/lnbits/decorators.py", line 28, in wrapped_view
Apr 06 14:28:48 raspberrypi sh[11994]:     return await view(**kwargs)
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/lnbits/decorators.py", line 55, in wrapped_view
Apr 06 14:28:48 raspberrypi sh[11994]:     return await view(**kwargs)
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/lnbits/core/views/api.py", line 121, in api_payments_pay_invoice
Apr 06 14:28:48 raspberrypi sh[11994]:     raise exc
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/lnbits/core/views/api.py", line 114, in api_payments_pay_invoice
Apr 06 14:28:48 raspberrypi sh[11994]:     payment_hash = await pay_invoice(wallet_id=g.wallet.id, payment_request=g.data["bolt11"])
Apr 06 14:28:48 raspberrypi sh[11994]:   File "/home/lnbits/lnbits/lnbits/core/services.py", line 141, in pay_invoice
Apr 06 14:28:48 raspberrypi sh[11994]:     raise Exception(payment.error_message or "Failed to pay_invoice on backend.")
Apr 06 14:28:48 raspberrypi sh[11994]: Exception: no_route

Ok, got rid of that. Now it should fail more cleanly.

I would like to reopen this issue basically. After a long time i tried to use my lnbits on clearnet to pay a coingate lightning invoice. I received some funds via lightning from an eclair wallet successful but as i want to pay my coingate invoice it stucks. Second try ends on 500.
 I think i can easy reproduce this issue here


Flow AbortSignal from IDE

Description
#2935 had some AbortControllers with no way to call abort() on it. This PR fixes that and only adds AbortSignal where it makes sense. For future proofing, AbortSignal is also passed down to core/llm/stream.ts functions.
The abort error that shows up in debug console is also removed.
Testing

Tested with ollama serve. No requests are left open. Cached completions still work. No regressions are detected so far with manual testing.

Binding the http requests to the IDE cancellation token was the 1st approach I used in #2935. But as @sestinj requested, and as https://github.com/continuedev/continue/pull/2935#issuecomment-2488927707 explains, the abort signal has to be controlled by the generator, so you can still reuse pending streaming if the prefix is compatible with previous completion requests, as to minimize requests. This is irrelevant to response caching, that you observed.

Right! I apologize I missed that comment. Will fix in a moment.

Done. I think AbortSignal is outside the scope of ListenableGenerator's tee-ing function and should be managed by the GeneratorReuseManager instead. It makes more sense this way for me.

Because of the other PR we had to similarly address this, I'm going to close this PR. We seem to have abort signals passed through everywhere, and it's actually purposeful that they are different ones from VSCode's token passed through the InlineCompletionProvider
I think just an awkward bit of timing with a few people jumping to solve the problem all at once (which I appreciate!), but if I'm missing something here let me know


update "media partners" to general partners and add this

Madhesi Youth

Janakpur Youth Network - JYN
(This doesn't have logo yet - so instead of coming soon can you just have text that says "Janakpur Youth Network - JYN"

Done @ravinepal. Please review and close the issue.

Thanks, @studenton! One more under general partners:


add --extra-info flag

this will add line info to test lists, and test descriptions to the long
form of the test list
Related to issue #930

I tested this quickly and I am willing to merge it*, but I found what I would consider a bug in the implementation of --extra-info:
If I pass only --extra-info option to Catch binary, it behaves as if no arguments were passed (all tests are run). This is different from all other list X commands, and even though it isn't named list-*, I think user would expect it to behave like one (especially since its description says "list more info").

I didn't have time to look through the code yet, so standard disclaimers apply.

I decided to make some changes, it is now --list-extra-info and behaves like other --list-* flags, meaning that it lists tests on its own and prevents execution of tests.
Also improved the CLI description a bit.

Sorry, I saw your comment but hadn't had a chance to fix it myself.
I am wondering if I am going about this the wrong way. My intention was to make more info available for external runners to use, but for that maybe instead of adding more info to the existing lists, would it make more sense to create a new list command --list-parseable or something similar, which will list tests in a documented, parser-friendly format instead of a screen-friendly one? The format would probably include all the info available on a test (name, description, line info, tags, etc.) on a single line, with the different fields separated by some delimiter.
Would that be a better idea than the current one? Or maybe leave this already and add also the parser-friendly list command?

It is quite likely the wrong solution, but we had a discussion with Phil and we are willing to merge this in at least temporarily. Routing list outputs through reporters, so they can format the output accordingly, and introducing verbosity levels would be preferred, but I have no idea when that would make it in.

Routing list outputs through reporters, so they can format the output accordingly, and introducing verbosity levels would be preferred, but I have no idea when that would make it in.

I would like to try working on this, but am unsure where to do this. It would probably involve some slight breaking changes, at least to the command line. Should I base this on the master branch or on dev-modernize? I am assuming that the later is the work on a Catch v2? How close is that to becoming stable?

@BMBurstein A preview of Catch v2 should be released relatively soon, but it being preview means that breaking changes might still get in afterwards.
If you want to try your hand at making this change, I think you should base your work on dev-modernize.


add standard environments exclusion to the gitignore file

Its better to make gitignore file more standard, I check it out and add standard environments folder exclusion to the gitignore file

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


README.md file within docs is updated

README.md file within docs is updated

@souka Squash your commits into one :+1:

@souka1 Squash your commits into one :+1:


enable opengl in samples

Description
added the line to each main.cpp file to enable opengl for each sample; I think this change is pretty straightforward since this line is needed to enable opengl but I have had some difficulties running some of the samples in general on my machine so I haven't tested it yet, but I wasn't sure we need to?
Type of change

[x] Bug fix
[ ] New sample implementation
[ ] Sample viewer enhancement
[ ] Other enhancement

Platforms tested on:

[ ] Windows
[ ] Android
[ ] Linux
[ ] macOS
[ ] iOS

Checklist

[ ] Runs and compiles on all active platforms as a standalone sample
[ ] Runs and compiles in the sample viewer(s)
[x] Branch is up to date with the latest main/v.next
[x] All merge conflicts have been resolved
[ ] Self-review of changes
[ ] There are no warnings related to changes
[ ] No unrelated changes have been made to any other code or project files
[ ] Code is commented with correct formatting (CTRL+i)
[ ] All variable and method names are camel case
[ ] There is no leftover commented code
[ ] Screenshots are correct size and display in description tab (500px by 500px, platform agnostic)
[ ] If adding a new sample, it is added to the sample viewer
[ ] Cherry-picked to Main branch (if applicable)

@annika-oeth should we close this?

oh yeah sorry I forgot to close this one!


Provide write permissions to container FS to golang app running in a distroless container

Hello,
We have a golang app for which we use skaffold and ko to build an image. KO by default uses a distroless base image. Upon inspecting that image it seems that nonroot user does not have write permissions to anything except /tmp directory which is a problem. The application in question writes a configuration file to /etc and for obvious reasons it used to work when using non-distroless containers. When using docker to build the image we could use chown along with copy command (https://docs.docker.com/engine/reference/builder/#copy) but i do not find any such command/configuration in KO.
The following works with a Dockerfile:
FROM golang:1.20 as builder
WORKDIR /go/src/github.com/org/myapp
COPY . .

RUN mkdir -p /var/myapp/config

# Build
RUN make build

FROM gcr.io/distroless/static-debian11:nonroot AS myapp
WORKDIR /

COPY --from=builder --chown=nonroot:nonroot /var/myapp/config /var/myapp/config
COPY --from=builder /go/src/github.com/org/myapp/bin/myapp /myapp
ENTRYPOINT ["/myapp"]

Any help would be appreciated.

I have already tried to use gcr.io/distroless/static-debian11:nonroot with KO but even with this image by default you do not have permissions and that is the reason i had to explicitly create an empty dir in the builder step and  change the ownership while copying that folder from the builder to the final image. Same problem for all distroless images with nonroot users.

This isn't really a ko issue. If you choose a base image that runs as a user that has permission to write to /etc, things should work fine. Neither the default base image or gcr.io/distroless/static-debian11:nonroot do that, but you can choose or build a base image that does allow that.


Error on resolve

We'll be able to validate the below map without issues but trying to resolve the errors will yield an error:

new_file.sbgn.txt

Same for this file:
new_file_4.nwt.txt
We can then try to catch any errors so it can continue working.

@ugurdogrusoz @hasanbalci the reason of problem is undefined types, like array[0].property for empty array. Fixed by necessary if statements.


interactive input

Hi when I tried your "create minimalistic Todo app' I got this error for previewing the result. It seems like the environment couldn't have interactive input. However your example has a nice output. How can I 'upgrade' my environment?
StdinNotImplementedError: raw_input was called, but this frontend does not support input requests.

I believe there was a bug with the application a while ago.
Could you pull the latest version of the repo and try running it again?
Feel free to reopen if you experience any issues.

ok i'll try it again!. thank you for the reply


feat:configloader ut #661

UT BBD.yaml
given:
  - name: "Config"
    modules:
      - name: "LoadConfig"                    # 对于configloader.LoadConfig函数测试
        behavior:
          - when: "Yaml Parses Success"
              - specify: "should state filed correctly"   # 是否应正确存档状态
               - should: "state.backend equal s3 or local"  # 应该是s3 or local
               - should: "state.options.statefile equal devstream.state"  # 应该是devstream.state

              - specify: "Tools Options cannot be empty"
               - should: "Array Tools not nil"
               - should: "Tools.Name not empty"
               - should: "Tools.InstanceID not empty"
               - should: "Tools.Options not empty"
               - should: "Tools.DependsOn not empty"
          - when: "Yaml Parses Fails"
             - specify: "Yaml parses fails"
               - should: "err not nil"

Description
Add configloader Loadconfig some ut test cases
Related Issues
🍀 Proposal: Add More ut to the configloader Package #661
New Behavior (screenshots if needed)

Correct configuration screenshots

Error configuration screenshots

Now that we are part of CNCF, per CNCF's requirement, we kindly require that contributors sign off on commits submitted to our project's repositories. Thanks!

Please sign off these four commits:

git rebase HEAD~4 --signoff
git push --force-with-lease origin feat-configloader-ut-661

@himku Thanks for the contribution! Please resolve the conflicts locally and push again.

@himku Thanks for the contribution! Please resolve the conflicts locally and push again.
ok


Initial fork always shows test cases failed

The original solutions which have been forked will always show test case failure. Seems like a bug as it's been encountered in most forks that I have clicked onto. Here's a screenshot ~~

It is also unable for users to view the run output of the original fork, but it's available in the latest fork! (See screenshot below

When a user saves a kumite, the output and a flag indicating if the test passed are stored. The original doesn't have them because it's automatically created when someone attempts to fork a solution, using test cases at the time.
The Failed badge was shown because the flag is null, and the frontend was checking for falsey value. This was fixed.

It is also unable for users to view the run output of the original fork, but it's available in the latest fork!

The original one doesn't have the output recorded, so there's nothing to show. I'm thinking of adding a button to run it instead of showing a stored output.


Add u32 type and use it for get_local

It's a first step to fix #126 but we should add all the different method signatures.
#104 could be the way to go however some method signatures seems to be wrong too (see https://github.com/WebAssembly/wabt/blob/master/src/opcode.def#L62 it's declared as i32,i32 instead of u32,u32). It might be cleaner to use our own data structure?

LGTM 👍

@johnsudaar do you mind fixing the linting warnings (which will be considered as error soon):
/home/travis/build/xtuc/js-webassembly-interpreter/test/interpreter/kernel/exec/conversion-instructions.js
  177:50  warning  property `nan`: Property not found in 'object literal'. See line 23   flowtype-errors/show-errors
  177:50  warning  property `nan`: Property not found in 'object literal'. See line 36   flowtype-errors/show-errors
  177:50  warning  property `nan`: Property not found in 'object literal'. See line 49   flowtype-errors/show-errors
  177:50  warning  property `nan`: Property not found in 'object literal'. See line 124  flowtype-errors/show-errors
  177:50  warning  property `nan`: Property not found in 'object literal'. See line 137  flowtype-errors/show-errors
  177:50  warning  property `nan`: Property not found in 'object literal'. See line 150  flowtype-errors/show-errors
  177:50  warning  property `nan`: Property not found in 'object literal'. See line 163  flowtype-errors/show-errors

/home/travis/build/xtuc/js-webassembly-interpreter/src/compiler/AST/index.js
  213:40  warning  FloatLiteral: Could not resolve name                                                                                flowtype-errors/show-errors

/home/travis/build/xtuc/js-webassembly-interpreter/src/compiler/parsing/watf/grammar.js
  719:50  warning  Incorrect number of type parameters (expected 1). See line 719                                                                                flowtype-errors/show-errors


Release authentication

Hi,
I haven't found any way to authenticate rainloop release tarballs, since all data and metadata is served over clear HTTP.
Would it be possible that you provide a GPG signature along each release ?
Or maybe have a mirror of either tarballs or the http://repository.rainloop.net/v2/core.stable.json file somewhere trustworthy (github releases ?)

I have added signatures (GPG) for each release file.
Check the new download page: http://www.rainloop.net/downloads/

Nice, thank you! It is just what I needed to enable automated updates from tarballs.
For other uses, do you plan to add signature checking in installer and updater ?

Yes, but not right now.

Fine, thanks again.


Failed to load the sound - resource not found. - Android

I'm getting an error message:
"'failed to load the sound', { message: 'resource not found', code: -1 }"
the code I am using is a direct copypaste from the example with some variable names changed:
var Sound = require('react-native-sound');
var bell = new Sound('./doorbell_1.mp3', Sound.MAIN_BUNDLE, (error) => {
  if (error) {
    console.log('failed to load the sound', error);
    return;
  }
  // loaded successfully
  console.log('duration in seconds: ' + bell.getDuration() + 'number of channels: ' + bell.getNumberOfChannels());
});

the location of my mp3 file is in the raw directory as the instructions state. I can't figure out what I'm doing wrong.
I have attached a screenshot of the doorbell_1.mp3 location in my directory.

Fixed by restarting the packager.
All I had to do was look through the closed issues to find out.
Thanks.


What is the current version of osmdroid?

Issue Type
[x] Question
Description and/or steps/code to reproduce the problem
@spyhunter99
What is the current version of osmdroid?
https://github.com/osmdroid/osmdroid/releases says 6.1.17
That is also the version, which I use in build.gradle.
dependencies {
   ...
    implementation group: 'org.osmdroid', name: 'osmdroid-android', version: '6.1.17'
   ...
}

However, OsmdroidBuildInfo.java says 6.1.15:
package org.osmdroid;

//this file is automatically generated during the build
//when making changes, only edit ./src/main/filtered/...
//https://github.com/osmdroid/osmdroid/issues/1500
public class OsmdroidBuildInfo {

    private OsmdroidBuildInfo() {
    }

    public static final String VERSION = "6.1.15";
    public static final String BUILD_DATE = "Tue Mar 28 20:46:50 EDT 2023";
}

What is correct?
Version of osmdroid the issue relates to:
6.1.15 ... 6.1.17 (?)

that's unexpected. i'll look into it. latest version published to central
should be 6.1.17
On Tue, Oct 17, 2023 at 10:05 AM Michael L. Braun @.***>
wrote:

Issue Type
[x] Question
Description and/or steps/code to reproduce the problem
@spyhunter99 https://github.com/spyhunter99
What is the current version of osmdroid?
https://github.com/osmdroid/osmdroid/releases says 6.1.17
That is also the version, which I use in build.gradle.
dependencies {
...
implementation group: 'org.osmdroid', name: 'osmdroid-android', version: '6.1.17'
...
}
However, OsmdroidBuildInfo.java says 6.1.15:
package org.osmdroid;
//this file is automatically generated during the build
//when making changes, only edit ./src/main/filtered/...
//https://github.com/osmdroid/osmdroid/issues/1500
public class OsmdroidBuildInfo {
private OsmdroidBuildInfo() {
}

public static final String VERSION = "6.1.15";
public static final String BUILD_DATE = "Tue Mar 28 20:46:50 EDT 2023";

}
What is correct?
Version of osmdroid the issue relates to:
6.1.15 ... 6.1.17 (?)
—
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/1946, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPCIGMTU55F4YNN3BUEADLX72GCBAVCNFSM6AAAAAA6D5GSEWVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2DONJRHAYDIOI
.
You are receiving this because you were mentioned.Message ID:
@.***>

@spyhunter99
I just saw, that you have published the osmdroid version 6.1.18, good!
However, OsmdroidBuildInfo.java still says 6.1.15 (see above).

sorry about that, forgot about this issue. it looks like it's a bug in gradle. It will only do the copy/filter if the destination does not exist, Which is contrary to the documentation and all the examples. It's entirely possible this started happening when we upgraded gradle after 6.1.15
looking at it now


Look for default parameters that are more closely related to linguistic trees

Or, at least, to the Indo-European one

Not necessary anymore, and should be delegated to abzu (if at all).


Changes to Chronic Heat test example.

Changes to Chronic Heat test example to make it compatible with actual S3 data.
Modelling impact as truncated gaussian, introducing uncertainty in hazard and vulnerability.

Fixed conflicts and push in separate PR.


Module Issue and Project Clarifcation

Hi Professor,
I have an issue with one of my modules breaking, and I'm not sure what the problem is since it only affects one of the modules in the middle of my Pokedex.
I also have I question about the idea I have come up with for my to-do list. My idea is to have a Pokedex, where you can check off the pokemon you caught and it shows the number at the top of the screen as to how many you have caught out of 72. They can click and unclick the caught buttons to add or remove the pokemon from their caught number. I was wondering if that met the assignment requirements or if I had to do something that actually adds or removes something in a more literal sense instead of just detracting from the number at the top.
Thanks

@ChristianLAPB
Sorry - can you describe the problem in a bit more detail, or include a screenshot of the error that you are experiencing. Happy to help - just need a bit more details so I can better troubleshoot.
Thank you

I have an issue with one of my modules breaking, and I'm not sure what the problem is since it only affects one of the modules in the middle of my Pokedex.

Hi @ChristianLAPB
THIS IS AWESOME 🎉
Your "Pokedex" idea 100% meets the functionality requirements of the assignment and I am beyond excited to see it in action.
If you need a list of Pokemon: https://github.com/fanzeyi/pokemon.json/blob/master/pokedex.json
Or if you need images: https://github.com/fanzeyi/pokemon.json/tree/master/images
(just remember to put a reference in your code as a comment if you end up using the above two items)

I also have I question about the idea I have come up with for my to-do list. My idea is to have a Pokedex, where you can check off the pokemon you caught and it shows the number at the top of the screen as to how many you have caught out of 72. They can click and unclick the caught buttons to add or remove the pokemon from their caught number. I was wondering if that met the assignment requirements or if I had to do something that actually adds or removes something in a more literal sense instead of just detracting from the number at the top.

Hi Professor!
I hope your vacation is going well! I was able to fix the issue, so all is good there! Would you be able to look at my site and let me know if it looks fine on your side? Some people seem to have issues viewing it properly while others don't and it doesn't seem to be browser dependent. Thanks for your help!

Hi @ChristianLAPB
Just had a quick look! Looking really great so far.
Unfortunately the following error is being thrown:

The issue seems to be with this line of code
// The ul for the list of pokemon
const pokeList = document.querySelector(".poke-entries");

pokeList is coming up as null.
Can you double check to see if there is an element on your page with the class "poke-entries".

Hi @ChristianLAPB
I'm also going to challenge you on a couple of things:
In mobile mode, the design could really be enhanced by using the full width of the mobile device as opposed to a smaller fraction of the width. I tried to do a quick drawing but admittedly it's pretty rough.

Also, though not required, it would be super cool if you could generate all of the Pokemon entries from a Javascript array of data as opposed to manually creating them in your HTML!
pokemons = [
  {
     name: "Pikachu",
     imgSrc: "\images\004.png",
     isCaught: false,
  },
  {
     name: "Chesnaught",
     imgSrc: "\images\005.png",
     isCaught: false,
  },
  ...
];

for (let I=0; I < pokemons.length ; I++) {
  ... code that adds all of the pokemons to the parent list item...
}

Hi Professor!
Thank you for all the suggestions! I am working on fixing the mobile layout, and I have run into an issue. There is a 30px padding or margin on the left side, and I can't find out what is causing it. I looked in inspect and my best guess would be it's due to the grid I'm using, but I'm unsure how to target that grid portion. I want to have the mobile version have 2 boxes show up side by side.

Hi @ChristianLAPB
This one was tricky!
Forcing a margin and padding of zero on the main ul.pokemon list seems to clear out that space.
The reason for this is browsers add margin and padding to ul by default. Setting the margin and padding to 0px clears out this default spacing.
main ul.pokemon {
  border: 1px solid red;
  background-color: red;
  list-style-type: none;

  margin: 0px;
  padding: 0px;

  display: grid;
  grid-template-columns: repeat(1, 1fr);
  grid-template-rows: repeat(72, 1fr);
}


Feature: Display WebUI version on homepage

Motivation for changes:
It was a request and it was low hanging fruit 🥝 🍎 🍌
Detailed changes:

Passed npm_package_version variable to webpack
Display npm_package_version  in Version component
Update Snapshot that failed

Addressed issues:

Fixes #94

Not really sure if passing the npm package version to webpack is the correct way. Also not sure if this will work for a "production" build as I'm not familiar with webpack or how you bundle the webui with the flexget binary.

Thanks. I'll take a look in a bit.

Actually we might have to change this for production. We don't bump the version currently until after doing a production build. I can point you in the direction of all that stuff, are you in the flexget chat?

@kristenmills busy week at work. I'll be free all weekend. Ping me on gitter and we can talk about this feature.

Sorry that i haven't gotten to this yet @shadycuz I've been really busy myself

@kristenmills No problems. I have tried DMing you on gitter, but maybe I should try slack?

Yeah message me on slack.


missing YIPs from all-yip

Important YIPs are missing again from https://yips.yearn.finance/all-yip
for example, YIP-57 (mint more YFI) is a really big one that is missing
edit: Apparently the up to date info is here: https://docs.yearn.finance/governance/proposal-repository
Maybe delete https://yips.yearn.finance/all-yip or have it redirect to https://docs.yearn.finance/governance/proposal-repository ?

this can be closed per https://github.com/yearn/YIPS/pull/83


[Bug] Support for generic entry functions

We revisit this in stage#2 or later so keeping this task to track support of generic entry functions.
@nvjle suggested that one approach would be to have the compiler generate one generic function and use some form of type-descriptor at runtime. The type descriptor could be the same as our hidden rtty desc, or instead the language_storage::TypeTag
We probably need to put checks:

preventing users from abusing the generic entry points.
limiting the kind of type descriptors allowed for entry functions

This is part of #161.

Many Move smart contracts are parameterized by the type of an asset they're handling, e.g. Coin, where Coin can be any particular token type. That is to say, generic structs and functions in Move binary packages are quite a common thing, not an exotic feature.  Move bytecode supports type parameterization, with instantiation being performed at run-time by the VM.  I'm not sure how we can generate generic LLVM code and determine struct layout at compile time, if the actual type parameters can be other structs possibly defined in other modules or even packages.

Many Move smart contracts are parameterized by the type of an asset they're handling, e.g. Coin, where Coin can be any particular token type. That is to say, generic structs and functions in Move binary packages are quite a common thing, not an exotic feature. Move bytecode supports type parameterization, with instantiation being performed at run-time by the VM. I'm not sure how we can generate generic LLVM code and determine struct layout at compile time, if the actual type parameters can be other structs possibly defined in other modules or even packages.

We already handle generics (i.e., where function signatures or structs are parameterized by type) in all cases with the exception of Move entry functions. Currently these implemented as follows:

In the case of ordinary Move function generic signatures, we expand ("monomorphize"/concretize) each function into a concrete instantiation. This is essentially the same as is done by C++ template expansion or Rust generics. See
In the case of native Move functions, we leave them generic and pass an implicit MoveType parameter for each generic type parameter. The move-native library routines must interpret these types at runtime. This interpretation is what accounts for much of the complexity in what is otherwise a simple library.

Similarly, Move entry functions could be implemented as either #1 or #2 above-- or a combination. If all (or many) of the expected type parameters for a given entry point happened to be known (e.g., we know a function typically takes SOL, or u32), then #1 applies. We'd concretize/expand the function as usual. If, on the other hand, we have the case where we do not necessarily know the expected types (or there are "too many")[*], the we could do something similar (if not identical to) #2. We also concretize generic structs, which is a considerably more tricky than functions.
The Coin example is a place where #2 would make sense. Note, however, that Coin is part of the vendor/chain-specific framework library. We do not have to do tokens (or anything else) the same way (i.e, generic). I don't seem to remember most Solana functions being generic like this (but I do need to go back and review, e.g., a Solana token "transfer" API). This is why in the meeting on Friday I opined that this functionality seems not high priority. But I do agree that it adds expressiveness to the language/interface and is very nice and convenient. In either case, if someone is interested in implementing it, the "simplest" way to do it is to follow what we already do for #2.
[*] As is done in some systems, the expected or likely types can be annotated in comments or language-specific annotation mechanisms. In some cases, a set of expected/possible types are obvious (often from type inference itself)-- e.g., type T is an integer primitive-- which is a very small number of types in the Move Language).

Sounds good to me. We definitely can postpone support of generic entry functions. I added a small example using a generic entry function in #355.  It seems currently this function is not included in function declarations that declare_functions_walk creates. I'll probably debug this a bit, just to understand what we do.

Sounds good to me. We definitely can postpone support of generic entry functions. I added a small example using a generic entry function in #355. It seems currently this function is not included in function declarations that declare_functions_walk creates. I'll probably debug this a bit, just to understand what we do.

One reason it is not included in declare_functions_walk is because in your example, it (public entry fun bar<T: store>(coin: &Coin<T>): u64) is never instantiated (that is, it is never called). Please see the rbpf test examples I wrote for this sort of thing in tests/rbpf-tests/rgeneric-func* and tests/rbpf-tests/generic_struct*. A simple example follows:
module 0x100::MX {
    public fun generic_id<T>(v: T): T {
        v
    }
}

module 0x200::MX {
    use 0x100::MX::generic_id;

    public fun square32(n: u32): u32 {
        generic_id<u32>(n) * generic_id<u32>(n)
    }

    public fun square8(n: u8): u8 {
        generic_id<u8>(n) * generic_id<u8>(n)
    }
}

script {
    fun main() {
        let x2 = 0x200::MX::square8(8);
        assert!(x2 == 64, 0xf00);

        let y2 = 0x200::MX::square32(32);
        assert!(y2 == 1024, 0xf01);

        // Second instantiation of generic_id<u8>.
        let z = 0x100::MX::generic_id<u8>(33);
        assert!(z == 33, 0xf02);
    }
}

I did try to copiously document what I implemented in declare_functions_walk (and related), and likewise for generic structs (declare_structs and related) in the comments in the source code.

Makes sense. My mistake, not paying due attention.

An aside (splitting out from above):
Regarding Coin specifically-- this does not seem to be the killer app for generics in the Solana context. That is, as near as I can tell, SPL Token APIs are all concrete (see, e.g.,  transfer above).
If I understand correctly, we will need to interoperate with existing Solana programs (including system programs). At least for token creation and transfers, I think we'd have to adhere to SPL Token APIs-- and likewise for any other standard Solana framework items. On the other hand, if we are free to design our own framework along the lines of Aptos or Sui, then we could support generic APIs, such as Aptos' legacy Coin, etc.
I certainly think redoing them generically would be better long term from the expressiveness and modernity point of view, but we may not have that option just now.


cont use the library while coding in android with (CodeAssist) app

Hello brother. I salute you for your project (Mongol Library). I practice programming on the phone, specifically on the (CodeAssist) application. When I add your library in a project, it is not recognized, especially when importing it in an activity. I do not know the reason, and I have tried a lot, even copying all the contents of the library into a new project and extracting the (aar) file and it works with me, but the problem remains. When adding any part of the library in the (main_xml) file and running the application, it happens The application is closing, I am creating a Keyboard application and I just want to add the navigation view, to control the writing cursor, copy and paste, I searched a lot for these codes that control the writing cursor in the directions (up, down, right, left), is it possible to change the line for adding the library implementation 'net.studymongolian:mongol-library:1.17.3' to anything else, or you can download the CodeAssist application, and try , and see the mistakes yourself....Thank you

Sorry, I'm no longer maintaining this library since I've started using Flutter. The mongol package for Flutter is what I use now.


Added Logging Capabilities

Summary of the Pull Request
Added Logging Capabilities for Data Factory and SQL that can be optionally disabled.

References
No references.

PR Checklist

[x] Code of Conduct signed. If not, go to Code of Conduct.

Validation Steps Performed
See checks below.

Preview Link


Copying and pasting dist folder's contents from Classifai_FrontEnd to classifai's webroot

This is an automatically created PR :robot::robot:

It will triggered once codes in dist folder from repo Classifai_FrontEnd has been pushed.
Files & sub-folder in dist folder of repo Classifai_FrontEnd will be copied into classifai's webroot
Committed frontend PR's URL can be found in the commit history below.

Don't know if this is caused by this change, but the import window doesn't pop up.
In v2_alpha, import works.

@devenyantis hmmm maybe can verify by doing a fresh build from classifai_frontend and see if the same scenario persists.

@devenyantis It's because the PR #441 does not merged yet

@amalsyahmi-certifai @codenamewei
Okay. In that case, should we rebase to #441 ?
And. Is there any backend dependencies for the sorting?
I tested this pr yesterday, it shows July 4 for both created and modified. Today it shows July 5. Haven't open any project.
In alpha1, the created dates are correctly shown.

thanks for the clarification , ill rebase this frontend to #441
and let deven review and possibly merge #441
then we'll come back to delete feature
ill do it now.


Documentation: JavaScript sample code in Prompting Users page needs improvements and should use modern JS language features and be more readable for novice JS developers

The  sample code should be readable and obvious to novice JavaScript developers.   For example; you should be using language features like the in-operator   instead of checking for undefined keys. You can see this throughout the sample code base but it starts in the Prompting Users page. For example you can change if (state.prompt  === undefined) to if (!('prompt' in state)).

I updated the prompt samples to use in. Do you have other specific suggestions?

Made the changes suggested


fix(dbm-services): 转移业务权限规格克隆参数问题

关联研发信息
dev_branch: fix/clone_priv_rules/#8509
target_branch: v1.5.0


ilab model download reports confusing error when downloading non-GGUF repo without .safetensors file

Describe the bug
Note that currently,  ilab model download errors out on not finding a file merlinite-7b-lab-Q4_K_M.gguf when trying to download a non-GGUF repo that does not have a .safetensors file. This might be confusing to the user, who expects the whole repo to be downloaded in such cases, not InstructLab looking for a specific file.
To Reproduce
Steps to reproduce the behavior:

Run ilab model download --repository=UnicomLLM/Unichat-llama3-Chinese-8B-28K. (This is a repo containing the model in .bin format).
ilab model download errors out with Entry Not Found for url: https://huggingface.co/UnicomLLM/Unichat-llama3-Chinese-8B-28K/resolve/main/merlinite-7b-lab-Q4_K_M.gguf., confusing the user because this is not a GGUF repo, and InstructLab can download other non-GGUF repos, like instructlab/granite-7b-lab.

Expected behavior
Error that the repo does not contain a .safetensors file nor a GGUF file, and thus the download is not supported.
Screenshots

Device Info (please complete the following information):

Hardware Specs: ThinkPad T14s Gen 2i
OS Version: ThinkPad T14s Gen 2i
Python Version: Python 3.12.4
InstructLab Version: ilab, version 0.17.1

Additional context
It is unclear from the interface that there are two code paths: one when there is a .safetensors file, then, the repo is considered a non-GGUF one and the whole repo is downloaded, and the other one where there is no such file where the repo is considered a GGUF repo and InstructLab automatically tries to download a GGUF file.

Fixed. Sorry, I was a bit too quick in filing the issue.

Thank you! I see you're using 0.17.1 - looking at the issue I think this may be fixed in current main - we are planning to cut a 0.18.0 soon, but if you want to you can try this on the current main branch to see if it's an issue there.

We need to expand ilab model download to understand .bin models, this is a pretty trivial fix and I can make a PR for it


Changed class evaluation from type to isinstance

Description
This PR closes issue #1176.
It changes the create_qt_controls and create_vispy_visual to evaluate the layer's class with isinstance and not type.
Type of change

[X] Bug-fix (non-breaking change which fixes an issue)

References
Issue #1176 and image.sc forum post.
How has this been tested?

[X] Using the standard pytest command as described here.

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

Comments
The create_qt_controls need to respect a certain ordering because Labels inherits Image and they have different QtControls. The sequence is of if and else is not very elegant but I think it is less error-prone than using a list in place of the dictionary.

I like what you did with the vispy layer:
    for layer_type, visual in layer_to_visual.items():
        if isinstance(layer, layer_type):
            return visual(layer)

I would do it with the qt controls as well... but use an OrderedDict to make sure that Labels comes before image.
also... You can get rid of Labels in the vispy layer_to_visual dict now.

I like what you did with the vispy layer:
    for layer_type, visual in layer_to_visual.items():
        if isinstance(layer, layer_type):
            return visual(layer)

I would do it with the qt controls as well... but use an OrderedDict to make sure that Labels comes before image.
also... You can get rid of Labels in the vispy layer_to_visual dict now.

I appreciate your feedback.
It seems that from Python 3.6 the standard dictionary is sorted and from 3.7+ this behavior is part of the Python specs.
Sources:

Python 3.6
Python 3.7+

yeah, you can use the standard dict too.  we'll also be dropping 3.6 in the near future.

@tlambert03 do we want to add a test for the typeerror?


Make default ClusterInputs optional and configurable

What this PR does / why we need it:
Make default ClusterInputs optional and configurable as already done for ClusterFilter objects.
Which issue(s) this PR fixes:
Fixes #594
Does this PR introduced a user-facing change?
Make default ClusterInputs optional and configurable

Additional documentation, usage docs, etc.:

That's a good tuning of the chart, thanks @AndreaVida !

@benjaminhuo glad to have been of help. Just to know, are you planning to make a new release anytime soon?


Dice game fix

Title and Issue number
Title : JS: Dice Game - Replace images with HTML and CSS
Issue No. : #451
Code Stack : HTML, CSS and JS
Close #451
Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have updated the Index.html file for my contribution

conflict @amanraina1

@sadanandpai please verify now


rust bug repro

not crashed( gather pgo data step passed
Finished `release` profile [optimized] target(s) in 3m 11s

Results (0.37s):
       157 passed

guess: too small benches? profdata fits into 1 file?


Release Hugo extended binary for Linux arm64 platform

Hi Team,
I have explored and it looks like you are not releasing Hugo extended binary for Linux arm64 platform.
It will be really helpful if the binary is released for Linux arm64 platform.
If required I will be willing to contribute.

How well have you explored?

Hi @bep
Apologies for the trouble I have caused and thanks for sharing the details, I missed the new release and hence raised the issue.

@odidev no problems, it's only been there for a few days :-)


Applying environment variables to istio-operator deployment

Bug description
Hi
I install istio through IstioOperator resource. This deploys me several components including a istio-operator deployment resource (=The operator controller deployment)
I do want to add environment variables to this deployment, however I’m afraid that this deployment is controlled by the istioOperator resource. That’s why I would like to add environment variables to the istioOperator resource instead of the deployment.
Am I correct? Or can I add environment variables to the istio-operator deployment resource without worrying that it will be overriden at some point?
How could I apply environment variables to this deployment through the istioOperator resource? I could already add environment variables to the egressgateway,ingressgateway & pilot through following config
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  namespace: {{ .Values.namespace }}
  name: istiocontrolplane
spec:
  profile: demo
  meshConfig:
    accessLogFile: "/dev/stdout"

  components:
    pilot:
      k8s:
        env:
        - name: **KUBERNETES_SERVICE_HOST**
          value: {{ .Values.KUBERNETES_SERVICE_HOST }}
        - name: **KUBERNETES_SERVICE_PORT**
          value: "443"
        replicaCount: {{ .Values.pilotReplicaCount }}
        resources:
          requests:
            cpu: 1000m #parameter to tweak
          limits:
            cpu: 2000m #parameter to tweak
    egressGateways:
    - name: istio-egressgateway
      enabled: true
      k8s:
        env:
        - name: **KUBERNETES_SERVICE_HOST**
          value: {{ .Values.KUBERNETES_SERVICE_HOST }}
        - name: **KUBERNETES_SERVICE_PORT**
          value: "443"
        replicaCount: {{ .Values.egressGatewayReplicaCount }}
        resources:
          requests:
            cpu: 200m #parameter to tweak
          limits:
            cpu: 500m #parameter to tweak
    ingressGateways:
    - name: istio-ingressgateway
      enabled: true
      k8s:
        env:
        - name: **KUBERNETES_SERVICE_HOST**
          value: {{ .Values.KUBERNETES_SERVICE_HOST }}
        - name: **KUBERNETES_SERVICE_PORT**
          value: "443"
        serviceAnnotations:
          service.beta.kubernetes.io/azure-load-balancer-internal: "true"
          service.beta.kubernetes.io/azure-load-balancer-internal-subnet: "{{ .Values.loadBalancerSubnet }}"
        replicaCount: {{ .Values.ingressGatewayReplicaCount }}
        #hpaSpec:
        #  minReplicas: 1
        #  maxReplicas: 5
        resources:
          requests:
            cpu: 200m #parameter to tweak
          limits:
            cpu: 500m #parameter to tweak
        service:
          type: LoadBalancer
          loadBalancerIP: {{ .Values.loadBalancerIP }}
          ports:
            - name: status-port
              port: 15020
              targetPort: 15020
              protocol: TCP
            - name: http2
              port: 80
              targetPort: 8080
              protocol: TCP
            - name: https
              port: 443
              targetPort: 8443
              protocol: TCP
            - name: tls
              port: 15443
              targetPort: 15443
              protocol: TCP
            - name: tcp
              port: 31400
              targetPort: 31400
              protocol: TCP

[ ] Docs
[ X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
Istio 1.7
How was Istio installed?
IstioOperator
Environment where bug was observed (cloud vendor, OS, etc)
Azure Kubernetes Service

I do want to add environment variables to this deployment, however I’m afraid that this deployment is controlled by the istioOperator resource.

istio-operator deployment is not controlled by the istioOperator resource. On the contrary, istioOperator is reconciled by the istio-operator deployment.
Why do you want to add environment variables to the istio-operator deployment?

@morvencao thats good news, thanks for the reply.
I'm running istio on AKS, and I'm limiting egress traffic through an Azure Firewall. I'm coming across following two issues
https://github.com/Azure/kubernetes-keyvault-flexvol/issues/137#issuecomment-583612338
https://stackoverflow.com/questions/62423868/can-anyone-clarify-where-you-can-specify-kubernetes-service-host-in-azure-aks-fo
KUBERNETES_SERVICE_HOST & KUBERNETES_SERVICE_PORT variables are not defined in other namespaces than kube-system in AKS. If I apply these variables to all deployments that communicates with the k8s API then my deployments succeeds. Thats why i needed to apply it as well to pilot, egressgateway & ingressgateway deployment resources.

Currently there are no configurations available for you to add environment variables to istio-operator deployment, you can add it manually by generating the istio-operator resources with helm firstly:
helm template manifests/charts/istio-operator/ \
  --set hub=docker.io/istio \
  --set tag=1.8.0 \
  --set operatorNamespace=istio-operator \
  --set watchedNamespaces=istio-system > istio-operator.yaml

then rdit istio-operator.yaml to add required environment variables and then deploy the istio operator:
kubectl apply -f istio-operator.yaml


Implement Login and Sign Up Page for Application

Let's move to implement the login and signup page of the application.

@calistatan03 Thank you! I will merge main into this branch and integrate the Header component with the login/signup pages!

@KatyayaniPande I moved the Header component from the app/ directory to the /components directory for better management of custom components!

heyy actually, i realised that having donor login and beneficiary login in the header may be abit unnecessary since we can simply show the login page that you have created and users can just toggle to whichever profile login suits them? i was thinking maybe instead of having login for all 3 profiles in the header, can just do one 'login' button and also include a 'signup' button?

That makes sense, we don't have to repeat ourselves and we can showcase the signup feature as well!

Ok I'll just let Katy know first! Also wanted to clarify w u, will you be implementing user authentication? I realised w/o authentication it may be difficult for us to merge downstream tasks w the database w/o knowing the logged-in user's details? For example when a donor submits a donation or when a beneficiary submits a request for food, we don't know their profile...or do you have a workaround for this such that we don't need to implement user auth?

I'm not very sure how to implement auth at the moment, but I assume we can store the user's token/username in the session state and use it to retrieve data from the database once the user logs in with valid credentials.
Do let me know if there are better ways of doing this!

Actually, was wondering if you've used Firebase before as they have very easy login and sign up methods...and I think its easier to use than MongoDB...

@calistatan03 Auth is implemented (its quite shaky at the moment, there's a lot of hoops to jump through to get it to work) but it is largely working(?)
The current user can be obtained by using next-auth's useSession() provider, which should be useful for the downstream workflows that require the current user.
AI was used to troubleshoot and generate some of the code pieces; I'm not sure if it is up to standards or otherwise. Would really appreciate it if you are able to take a look to see if there are any areas for optimisation/fixing!

got it! thanks :) sorry im out so not able to look through in detail yet, but just to check the user object being stored in session storage will have all the user info (basically the info they key in during sign-up)? not just email and role ?

Oh so far its only the role and email, but we can expand it to store the other details as well!

I have expanded the data to the other fields of the user as well.

The deployment to Vercel is currently failing due to the presence of a duplicate tailwind.config.js file. This PR will remove the file, which should solve the issue.


SCP-2370: let minting policies take redeemers

This is really only the beginning of this: it completely punts on
handling actually passing the redeemers around properly, instead just
conjuring () in all cases. The main point of this is so that
downstream can use our libraries to make minting policies that will work
with the real ledger, which will pass the extra argument (and does
already handle the redeemers).
I will make a follow-up PR for actually doing things properly, but it's
a bit of a rabbit-hole, so I thought I should get this one done first.

Pre-submit checklist:

Branch

[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages
[x] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

I'm being pushy on this but do take a look later.


More realistic simulation of zingers and stripes

add a random blurring effect to zinger pixels or stripes in sinogram/projection domain

#63 delivers more realistic 3D simulation. 2D WIP

improving synthetic flat-field generator.


Breaking Change regarding the usage of keytar

Hi,
I'm working on VSCode and I am trying to enable the usage of ASAR for VSCode. This can improve the startup time of VSCode by up to 5%. We are at a point where we are pursuing even such small gains...
I have found that your extension makes an assumption about the disk layout of VSCode's node_modules:
ms-azuretools.vscode-cosmosdb/out/src/tree/AttachedAccountsTreeItem.js:35
  this._keytar = require(`${vscode.env.appRoot}/node_modules/keytar`);

To make your extension entirely compatible with a distribution of VSCode that uses ASAR, and to make your extension work with both VSCode stable and VSCode insiders, you will need to try to load from two paths... Something like the following:
function getNodeModule(moduleName) {
  try {
    return require(`${vscode.env.appRoot}/node_modules.asar/${moduleName}`);
  } catch(err) { }
  try {
    return require(`${vscode.env.appRoot}/node_modules/${moduleName}`);
  } catch(err) {}
  return null;
}

I plan to release the changes to Insiders this week, such that the Insiders build on Friday, 23.02.2018, will contain the ASAR packing of node modules. In the meantime, I have created custom builds that include this change if you wish to test your extension against a VSCode version which contains these changes:

Win 64
Win 32
macOS
Linux 64
Linux 32

@chrisdias @chrmarti why are we referencing VS Code's node_modules? Why don't we follow the normal pattern where we add it to our package.json and reference it from our extension's node_modules directly? I'm asking you guys since it was added in this PR: https://github.com/Microsoft/vscode-cosmosdb/pull/41
cc: @StephenWeatherford

Ah, I assumed we were referencing our own.  Good question.

Keytar is a native module, so you'd have to ship one version per architecture and bitness (currently 5) and these would need to be rebuilt when we update to a new V8 with a new version of Electron. Having keytar built as part of VS Code does that for us.

I have submitted a PR to make the adoption - https://github.com/Microsoft/vscode-cosmosdb/pull/369

@alexandrudima when will this be going into stable?

@EricJizbaMSFT With the February release - https://github.com/Microsoft/vscode/issues/43361

Thank you!


Does pdf-lib has a method for extracting embedded images from a PDF file?

I want to extract an image from a PDF file but I can't see a way to do that in the documentation. How can this be done?
P.S. I see PDFIMage but it seems it is limited to embedding images into a PDF and not extraction.

Hello @adetoola! Please see https://github.com/Hopding/pdf-lib/issues/83#issuecomment-487383843.


Fix a few broken links and malformed markdown

This should fix the 3 megalinter errors that it's currently reporting
For the Piwigo face/object recognition, I removed the link to the piwigo extensions of type "Tag" as the one users seem to be using, Mugshot, is linked in the GitHub issue

Thanks! I noticed the litter errors, but just have not even had a few minutes to look at it!


[PE-D] "updt" command has incorrect format in UG

For the updt command, both fields are listed as optional even though at least 1 is mandatory.

Labels: severity.Medium type.DocumentationBug
original: medajet/ped#12

Fixed


Added licensing information about the data used

Not all of the files contained in the git repo are under the MIT license; some of them are under other licenses, such as CC BY-SA 3.0. This pull request gives information on the licenses for the data used to generate frequency_lists.json.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Riley Baird seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


merge overloads of std.algorithm.mutation.swap()

The two overloads are widely separated. This puts them together for easier study. The changes are mostly indenting.
Also has its own error message rather than the compiler generated one.

Gave up on the own message and the merge. Just co-located them.

dstyle fails with no message.