password policy related states, are never reached in CAS v5.1.0

In CAS 5.1.0, when binding to an OpenLDAP server, even though ldaptive returns password policy related messages/errors, the relevant states/views are never reached.
The problem goes away when adding in login-webflow.xml the following (taken from the CAS 5.0.x login-webflow.xml):
<action-state id="handleAuthenticationFailure">
    <evaluate expression="authenticationExceptionHandler.handle(currentEvent.attributes.error, messageContext)"/>
    <transition on="AccountDisabledException" to="casAccountDisabledView"/>
    <transition on="AccountLockedException" to="casAccountLockedView"/>
    <transition on="CredentialExpiredException" to="casExpiredPassView"/>
    <transition on="AccountPasswordMustChangeException" to="casMustChangePassView"/>
    <transition on="InvalidLoginLocationException" to="casBadWorkstationView"/>
    <transition on="InvalidLoginTimeException" to="casBadHoursView"/>
    <transition on="FailedLoginException" to="initializeLoginForm"/>
    <transition on="AccountNotFoundException" to="initializeLoginForm"/>
    <transition on="UnauthorizedServiceForPrincipalException" to="initializeLoginForm" />
    <transition on="UnsatisfiedAuthenticationPolicyException" to="initializeLoginForm"/>
    <transition on="UnauthorizedAuthenticationException" to="casAuthenticationBlockedView"/>
    <transition to="initializeLoginForm"/>
</action-state>

<end-state id="casMustChangePassView" view="casMustChangePassView"/>

Server environment: Stand alone CAS server v5.1.0, Tomcat8 @ Debian/GNU Linux
cas.properties file contains:
cas.authn.ldap[0].type=AUTHENTICATED
cas.authn.ldap[0].ldapUrl=ldap://ldap.example.com
cas.authn.ldap[0].useSsl=false
cas.authn.ldap[0].useStartTls=false
cas.authn.ldap[0].baseDn=dc=example,dc=com
cas.authn.ldap[0].userFilter=uid={user}
cas.authn.ldap[0].bindDn=cn=admin,dc=example,dc=com
cas.authn.ldap[0].bindCredential=secretpass
cas.authn.ldap[0].passwordPolicy.type=GENERIC
cas.authn.ldap[0].passwordPolicy.enabled=true
Log entries:
2017-06-22 20:06:11,994 DEBUG [org.apereo.cas.authentication.LdapAuthenticationHandler] - <LDAP response: [[org.ldaptive.auth.AuthenticationResponse@1793423495::authenticationResultCode=AUTHENTICATI
ON_HANDLER_FAILURE, resolvedDn=uid=auser,ou=People,dc=example,dc=com, ldapEntry=[dn=uid=auser,ou=People,dc=example,dc=com[]], accountState=[org.ldaptive.auth.ext.PasswordPolicyAccountState@1202237630::accountWarnings=null, accountErrors=[PASSWORD_EXPIRED]], result=false, resultCode=INVALID_CREDENTIALS, message=javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials], controls=[[org.ldaptive.control.PasswordPolicyControl@1159820221::criticality=false, timeBeforeExpiration=0, graceAuthNsRemaining=0, error=PASSWORD_EXPIRED]]]]>
2017-06-22 20:06:11,995 DEBUG [org.apereo.cas.authentication.LdapAuthenticationHandler] - <Applying password policy to [[org.ldaptive.auth.AuthenticationResponse@1793423495::authenticationResultCode
=AUTHENTICATION_HANDLER_FAILURE, resolvedDn=uid=auser,ou=People,dc=example,dc=com, ldapEntry=[dn=uid=auser,ou=People,dc=example,dc=com[]], accountState=[org.ldaptive.auth.ext.PasswordPolicyAccountState@12
02237630::accountWarnings=null, accountErrors=[PASSWORD_EXPIRED]], result=false, resultCode=INVALID_CREDENTIALS, message=javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credenti
als], controls=[[org.ldaptive.control.PasswordPolicyControl@1159820221::criticality=false, timeBeforeExpiration=0, graceAuthNsRemaining=0, error=PASSWORD_EXPIRED]]]]>
2017-06-22 20:06:11,995 DEBUG [org.apereo.cas.authentication.support.DefaultAccountStateHandler] - <Handling error [PASSWORD_EXPIRED]>
2017-06-22 20:06:11,995 INFO [org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - <[LdapAuthenticationHandler] failed authenticating [auser]>
2017-06-22 20:06:11,996 DEBUG [org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - <[LdapAuthenticationHandler] exception details: [null]>
2017-06-22 20:06:11,996 WARN [org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - <Authentication has failed. Credentials may be incorrect or CAS cannot find authentication handler tha
t supports [auser] of type [UsernamePasswordCredential], which suggests a configuration problem.>
2017-06-22 20:06:12,029 DEBUG [org.apereo.cas.web.flow.resolver.impl.InitialAuthenticationAttemptWebflowEventResolver] - <1 errors, 0 successes>
org.apereo.cas.authentication.AuthenticationException: 1 errors, 0 successes
at org.apereo.cas.authentication.PolicyBasedAuthenticationManager.evaluateProducedAuthenticationContext(PolicyBasedAuthenticationManager.java:173) ~[cas-server-core-authentication-5.1.0.jar:5.1.0]
at org.apereo.cas.authentication.PolicyBasedAuthenticationManager.authenticateInternal(PolicyBasedAuthenticationManager.java:153) ~[cas-server-core-authentication-5.1.0.jar:5.1.0]
at org.apereo.cas.authentication.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:140) ~[cas-server-core-authentication-5.1.0.jar:5.1.0]
at org.apereo.cas.authentication.AbstractAuthenticationManager$$FastClassBySpringCGLIB$$12a86894.invoke() ~[cas-server-core-authentication-5.1.0.jar:5.1.0]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.3.8.RELEASE.jar:4.3.8.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:738) ~[spring-aop-4.3.8.RELEASE.jar:4.3.8.RELEASE]
...
...
...
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_121]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat-util.jar:8.0.41]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
2017-06-22 20:06:12,042 DEBUG [org.apereo.cas.web.flow.resolver.impl.AbstractCasWebflowEventResolver] - <Resolved single event [authenticationFailure] via [org.apereo.cas.web.flow.resolver.impl.InitialAuthenticationAttemptWebflowEventResolver] for this context>
2017-06-22 20:06:12,056 DEBUG [org.apereo.cas.web.flow.InitializeLoginAction] -

Thanks for the logging the issue report. Please investigate the problem, evaluate and analyze your logs at DEBUG level and whenever reasonable, file a pull request to address this case.
Note: If you have already identified an enhancement or a bug fix, it is STRONGLY recommended that you simply submit a pull request to address the issue. There is no need for special ceremony to create separate issues.
The pull request IS the issue and it will be tracked and tagged as such. Do NOT log issues hoping for the problem to get resolved in the future by someone else. Study the guide and learn the skills to submit contributions, or reach out to a commercial affiliate for assistance.
You can learn how to build and run CAS from here.
Thanks again!

DefaultWebflowConfigurer sets up the handleAuthenticationFailure action-state that login-webflow.xml used to.  However it doesn't seem to be recognizing the exception, ie

2017-06-23 08:56:54,990 DEBUG [org.apereo.cas.web.flow.resolver.impl.AbstractCasWebflowEventResolver] - <Resolved single event [authenticationFailure] via [org.apereo.cas.web.flow.resolver.impl.InitialAuthenticationAttemptWebflowEventResolver] for this context>
2017-06-23 08:56:54,991 DEBUG [org.springframework.webflow.engine.Transition] - <Executing [Transition@669b3fb9 on = authenticationFailure, to = handleAuthenticationFailure]>
2017-06-23 08:56:54,991 DEBUG [org.springframework.webflow.engine.Transition] - <Exiting state 'realSubmit'>
2017-06-23 08:56:54,991 DEBUG [org.springframework.webflow.engine.ActionState] - <Entering state 'handleAuthenticationFailure' of flow 'login'>
2017-06-23 08:56:55,003 DEBUG [org.apereo.cas.web.view.CasReloadableMessageBundle] - <Loading properties [messages.properties] with encoding 'UTF-8'>
2017-06-23 08:56:55,006 DEBUG [org.springframework.webflow.engine.Transition] - <Executing [Transition@541e1ec8 on = *, to = initializeLoginForm]>
2017-06-23 08:56:55,006 DEBUG [org.springframework.webflow.engine.Transition] - <Exiting state 'handleAuthenticationFailure'>
2017-06-23 08:56:55,006 DEBUG [org.springframework.webflow.engine.ActionState] - <Entering state 'initializeLoginForm' of flow 'login'>

initializeLoginForm is the default transition ie it's not recognising the expected credentials expired exception.

I think that I have found the problem and its solution. See pull request 2709 (https://github.com/apereo/cas/pull/2709)

Thanks so much for finding/sorting that :)  I was looking all over for it!
On 23 June 2017 at 10:34, pdrados<EMAIL_ADDRESS>wrote:

I think that I have found the problem and its solution. See pull request
2709 (#2709 https://github.com/apereo/cas/pull/2709)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apereo/cas/issues/2703#issuecomment-310620237, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AYi-1aV9erYscSSRo8N5EgxXOXamyCB-ks5sG4akgaJpZM4OCmK0
.

--
This email is sent on behalf of Northgate Public Services (UK) Limited and
its associated companies including Rave Technologies (India) Pvt Limited
(together "Northgate Public Services") and is strictly confidential and
intended solely for the addressee(s).
If you are not the intended recipient of this email you must: (i) not
disclose, copy or distribute its contents to any other person nor use its
contents in any way or you may be acting unlawfully;  (ii) contact
Northgate Public Services immediately on +44(0)1908 264500 quoting the name
of the sender and the addressee then delete it from your system.
Northgate Public Services has taken reasonable precautions to ensure that
no viruses are contained in this email, but does not accept any
responsibility once this email has been transmitted.  You should scan
attachments (if any) for viruses.
Northgate Public Services (UK) Limited, registered in England and Wales
under number 00968498 with a registered address of Peoplebuilding 2,
Peoplebuilding Estate, Maylands Avenue, Hemel Hempstead, Hertfordshire, HP2
4NN.  Rave Technologies (India) Pvt Limited, registered in India under
number 117068 with a registered address of 2nd Floor, Ballard House, Adi
Marzban Marg, Ballard Estate, Mumbai, Maharashtra, India, 400001.


[Question] int-8 bits for instruct tuning

Question
Many thanks to the authors for this very good work.
 The following is the loss curve:

But when I use the following command to make predictions using the trained model, the result is very bad:
    python llava/eval/run_llava.py \
    --model-path ./checkpoints/llava-vicuna-v1-3-7b-finetune-tmp \
    --image-file images/llava_logo.png \
    --query "describe the image"

It's the result:
chevlocchevchevchevlocchevlocchevchevlocchevchevlocchevlocchevlocchevloclocchevlocchevchevchevlocchevloclocchevlocchevchevchevlocchevlocchevloclocchevlocchevchevloclocchevlocch
evlocchevlocchevchevlocchevloclocloclocchevloclocchevloclocchevchevchevlocchevlocchevchevchevlocchevchevlocchevlocchevlocchevlocchevchevloclocchevchevchevchevchevlocchevloclocc
hevlocchevlocchevchevloclocchevchevchevchevlocloclocloclocchev Хронологијасняchevlocchevchevchevlocchevchevlocchevlocchevchevchevlocchevchevchevlocchevlocchevchevchevlocchevmer
kсняchevchevlocchev Хронологијаchevсняchevmerkchevchevchevchevchev Хронологијаchevmerkchevchevсняchevchevchevсняmerkmerklocchevchevchevchevchevchevchevmerklocmerkchev Хронологи
 ...

Does anyone know why? Is it because I'm using the model incorrectly? Or is this model less effective in int-8 mode?
Thanks much.

Hi, I have not tried or verified the full model finetuning using int8 training. Int8/Int4 are mainly designed for quantized LoRA training. Please check out the instructions here.

Hi, I have not tried or verified the full model finetuning using int8 training. Int8/Int4 are mainly designed for quantized LoRA training. Please check out the instructions here.

@haotian-liu Thanks for your suggestion. I know there were problems with the previous training, so I changed to lora+8-bits training as you suggested. Below is my instruct tuning loss curve:

The results generated from the model are not very satisfactory. For instance, I want the model to describe the llava logo image:
python llava/eval/run_llava.py \
--model-path ./checkpoints/llava-vicuna-v1-3-7b-finetune-lora \
--model-base lmsys/vicuna-7b-v1.3 \
    --load-8bit \
    --image-file images/llava_logo.png \
    --query "describe the image"

The following are generated responses：
The image is a close-up of a person's face, with a blurred background. The person's eyes are open, and their facial expression appears to be one of concentration or focus. The
blurred background adds a sense of depth and focus to the image, making the person's face the primary point of interest. The overall effect is a visually striking and engaging
portrait that captures the viewer's attention.

Would you mind providing your Lora instruct tuning logs? Thanks much.


feat(services/tikv): introduce new service backend tikv

blocked by https://github.com/tikv/client-rust/pull/395#issuecomment-1611837537

TiKV has migrated it's grpc client to tonic at https://github.com/tikv/client-rust/pull/399
We will need to wait for tikv 0.3

tikv_client v0.2 has been released, let's rock: https://docs.rs/tikv-client/latest/tikv_client/

I will add test action in another PR.

I submitted a PR https://github.com/tikv/client-rust/pull/411 to remove the need of PROTOC.

Hi, @oowl, I have added protoc in https://github.com/apache/incubator-opendal/pull/2674. Would you like to take another try?

I will add tikv integration test in next PR.

I will add tikv integration test in next PR.

LGTM.

Great, let's go!


Hooks.php bug crash site on delete things...

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the plugin and it is still present.

WordPress version
5.9.3
Cloudflare-WordPress version
4.9.1
PHP version
8.0
Expected result
Delete media
Actual result
An error of type E_ERROR was caused in line 172 of the file /www/wwwroot/DOMAIN/wp-content/plugins/cloudflare/src/WordPress/Hooks.php. Error message: Uncaught TypeError: array_merge(): Argument #2 must be of type array, null given in /www/wwwroot/DOMAIN/wp-content/plugins/cloudflare/src/WordPress/Hooks.php:172
Stack trace:
#0 /www/wwwroot/DOMAIN/wp-content/plugins/cloudflare/src/WordPress/Hooks.php(172): array_merge()
#1 /www/wwwroot/DOMAIN/wp-includes/class-wp-hook.php(309): CF\WordPress\Hooks->purgeCacheByRelevantURLs()
#2 /www/wwwroot/DOMAIN/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#3 /www/wwwroot/DOMAIN/wp-includes/plugin.php(474): WP_Hook->do_action()
#4 /www/wwwroot/DOMAIN/wp-includes/post.php(6390): do_action()
#5 /www/wwwroot/DOMAIN/wp-admin/upload.php(197): wp_delete_attachment()
#6 {main}
thrown
Steps to reproduce
Delete media
Additional factoids
No response
References
No response

By any chance are you using the hook 'cloudflare_purge_by_url'?  If so, can you verify it's not returning a null value?


Windows 10 Pro est_watson.py  error

On Windows 10 Pro I reinstalled td-watson package and from environment C:\Users\User\Watson\tests tested test_watson.py file. I get error explanation.

Traceback (most recent call last):
File "C:\Users\User\Watson\tests\test_watson.py", line 15, in
from . import mock_read, TEST_FIXTURE_DIR
ImportError: cannot import name 'mock_read'

How to fix it.

The problem was python 36-32 bit version installed. I reinstalled python  64-bit Python version and project has full funcionalities.   See explantation for Windows file system https://stackoverflow.com/a/60612077/7307843.


Relocated analysis

Updated dataorganization.py to handle the case where the filemap no longer points to the data because it has been moved (different dataHome). This update was crafted to maintain backward compatibility.

Hello @timblosser! Thanks for opening this PR.

In the file merlin/data/dataorganization.py:

Line 257:1: W293 blank line contains whitespace
Line 262:17: E231 missing whitespace after ','
Line 263:81: E501 line too long (88 > 80 characters)

I hadn't originally intended to carry over the google cloud into this PR, if you want me to get rid of it let me know, otherwise I think it's fine to merge with this one.

I believe I've addressed your comments now @emanuega


Test performance of the app with large event

Currently we are not aware of a performance of the app with large event which will be having large attendees.
So approximate workaround will be

Make a test event which will be having large attendees (1000+)
Check the performance for attendees page, qr scan
Create issues accordingly

This can be taken up by all devs on board.
@iamareebjamal please label it high-priority, open-for-all

While I'm working on DB. I'll give you a tip. No need to create so much hassle (well you can if you want to do real testing). We have created the application in a modular way so you can just create a new EventService and return mock JSON with 1000 attendees, and it will work!

This should be first principle and then we can test the actual server response, but the test is for the app, so the only think, that will not be emulated here will be the response time for getting all attendees (which is actually not our problem)

@mariobehling @niranjan94 @iamareebjamal
I tested the app for an event with 1089 attendees with average down speed of 120 KB/s.
Currently the app loads all the attendees at a time and it took 13 sec (average) to display 1089 attendees on the screen after opening event detail screen of the event. Although this will be one time that is for first time only. Once all the attendees are loaded and saved in database all the functions are handled efficiently. functions here means - toggling attendee check in direct and via qr scan, displaying attendees list.
So? do we need to decrease initial loading time or is it acceptable?

This initial loading time you are talking about, if I am correct, is because of the data loading from the network. In which case, we can't really do anything about it. Secondly, please try on the database version to see how it plays. There will be a difference in speed of retrieval from the in-memory cache that was being used till now

because of the data loading from the network. In which case, we can't really do anything about it

I didn't get the need of loading all the attendees locally.
We don't have to load all the attendees locally.
For attendees list

attendees can be loaded by stocks according to viewport requirement. And shall be stored in cache only
searching attendees by name should be implemented on api
toggling check in is already being called on api

For ticket and attendees stats

This also need to be shifted to server.
Server should have a stats endpoint which will provide stats accordingly.

So what exactly use of storing all the attendees locally?
Petrixdroid is also following same approach. Doing all the functions on server.
@niranjan94 @mariobehling @iamareebjamal  what is your opinion?

You can't scan by QR then, because you won't have the complete set of attendees. And we simply can't do everything on the server as it does not have API for everything
Besides, cache was to be removed once database is implemented, so it is not there anymore

And we simply can't do everything on the server as it does not have API for everything

new api is being created hence these endpoints can be added which is really necessary.

cache was to be removed once database is implemented, so it is not there anymore

I don't see point in storing attendees in database.

@mejariamol I'll repeat, you can't scan by QR then because you won't have the complete set of attendees.
Secondly, searching from server every time is the worst possible design pattern on native applications. Just imagine organizer waiting for the search to finish when you have all the data to perform search locally.
Thirdly, I never said, server should not implement it, just that we should not sit idle waiting for the implementation to happen. Furthermore, the new API is being created, that doesn't mean we can just add it in one go.
Lastly, our app should be offline ready. We'll use JobScheduler to queue the network requests and mark the models in the database transient, and once the network comes back online, we won't be able to do this if we don't save models in database

The app needs to be offline ready - Very important.

Just imagine a big a event with a lot of attendee (In the order of 1000s) and network fails or the network is slow (Happens all the time in public wifi). Imagine the mess at the entrance when each attendee is waiting for his ticket to be scanned and verified.
So, for this, I believe the best way is to cache the attendees locally in one go and sync it up with the server in the background so that even if there is a lack of network, it does not cause the organizer to go mad

Stats endpoint can be provided. No issues.

@mejariamol @iamareebjamal

Okay. So currently attendees are loaded only when the concerned event is open. I think we should start loading all data in background once user logs in. These can be made in steps. for example

All the events will be loaded and saved
All the attendees of events will be loaded and saved
Till then we can show the data from local storage only which is loaded with progressbar and can implement flag system for each event if its complete data is loaded. once it is done we can show all the data.

This is counter intuitive to the flow of the app. If there are past events with 1000s of attendees, we might be unnecessarily pulling data and filling up the database where the user never even opens the event. I don't think this should be done. Attendees should only be loaded on demand

All the events will be loaded and saved

The basic details of the event (name & dates for example) could be loaded and cached

All the attendees of events will be loaded and saved

Not for all events. Only when the attendee list is opened for the first time

That is what we currently do :+1:

@iamareebjamal Yeah. but currently the data load request is called every time when fragment is hosted. That is if user switches between event containing fragments then the request calls will be called repetitively.
This must be fixed to avoid repetitive calls.

Call to network is made only once, all other calls are to database.

@iamareebjamal true. Sending a PR for fragment persistance


Add coverage percentiles getColorValue prop to grid layer

To make grid layer consistent with hexagon layer, add coverage, lowerPercentile, upperPercentile and getColorValue to layer prop
Fix bug in hex _onGetSublayerColor, use bin.value instead of bin.points.length to calculate color

Changes Unknown when pulling 30b58582a678cddde1c69a196757c7833f557248 on grid-colorValue-percentile into ** on master**.

Changes Unknown when pulling 171edd5662449334a4b949a6a8098132b1bf7ab8 on grid-colorValue-percentile into ** on master**.


Save Button Doesn't Work

Does the "Save.." button work for anyone in the Calculator example? I looked at the main.cpp in the calculator subdirectory and it seems like FlowScene::save() should save the graph in some sort of .flow file. Does anyone know whether they are able to save their graphs?

Hi!
It should work. Give me 5 mins

It work on my Linux machine with the master branch build.
What is exactly your problem? You press 'save' and nothing happens?

{
    "connections": [
        {
            "in_id": "{581959fe-719d-4f40-9334-26fa4809c29b}",
            "in_index": 0,
            "out_id": "{f5230fbb-7a8d-4b11-993a-6f3621e90188}",
            "out_index": 0
        }
    ],
    "nodes": [
        {
            "id": "{f5230fbb-7a8d-4b11-993a-6f3621e90188}",
            "model": {
                "name": "NumberSource",
                "number": "3"
            },
            "position": {
                "x": -385,
                "y": 139
            }
        },
        {
            "id": "{581959fe-719d-4f40-9334-26fa4809c29b}",
            "model": {
                "name": "Result"
            },
            "position": {
                "x": 260,
                "y": 132
            }
        }
    ]
}

Yes I don't see the output you are getting above anywhere. I run the executable ./calculator and then I try creating and saving a graph (by pressing the "Save.." button and then "Activate"). After that it seems like nothing happens (aka no terminal output after pressing the button as well as no file saved anywhere that I can find. Do you know where I should be looking after clicking the save button?

Normally, after pressing the 'save' button you should see the standard system save file dialog. You give the filename and press save. The .flow file is located in the folder where you decided to save it.

Any updates? Can you make a video of your screen?

Please, reopen if there is still the issue


[Bypass] OpenBlocks, Block Breaker

Version: griefdefender-1.1.0-TEST13-DEBUG3
Placing a OpenBlocks Block Breaker on the edge of a claim and powering it with redstone will allow blocks in the claim to be broken
Also errors when this is performed
https://gist.github.com/clienthax/04e1836d64b2d6295c0f1a62a92938e4

Create new ticket if this issue persists with latest SpongeForge and is caused by GD


Appcenter don't update active device, download, install.

Hi, i have issue:
I released an update to appcenter. But when user update my release sometime get error:
Can't send request to: https://codepush.azurewebsites.net/updateChecked
When user can dowload and update my release have error  500: Internal Server Error and appcenter dont update active device:
2019-10-07 11:00:02.054746+0700 TCInvest[1290:686740] ERROR: [CodePush] An error occurred while reporting status: {"status":0,"appVersion":"0.0.4","deploymentKey":"4YjOqObytTcTsMsfeaCJSpMFyPo2754aad31-eac7-4547-9c64-fa4e8abb6485","previousLabelOrAppVersion":null,"previousDeploymentKey":null} 500: Internal Server Error. StackTrace: ionic://tcinvest.tcbs.com.vn/plugins/code-push/script/acquisition-sdk.js:129:39
onreadystatechange@ionic://tcinvest.tcbs.com.vn/plugins/cordova-plugin-code-push/bin/www/httpRequester.js:30:51
Pls help. Thank

Hi, we were experiencing some issues with CodePush earlier today. Everything should be back to normal now. If you are still experiencing issues, please contact support on appcenter.ms


Add Blender 3.1 tags and generate new Dockerfiles

I also adjusted the readme, to document how to do a basic local test (in my case it showed that the python version had to be updated).
I also adjusted the drone-ci pipeline (with a copy-paste ;)

Right, I blindly copy/pasted it!
I have just removed the old one.


why I get error when I run my code?

I write my code as follows:
autotrain.txt
but when I run my code on linux，I get this error as follows. Could you help me solve it?

Traceback (most recent call last):
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/distributed/protocol/pickle.py", line 38, in dumps
result = pickle.dumps(x, protocol=pickle.HIGHEST_PROTOCOL)
_pickle.PicklingError: Can't pickle <function ag_train_mnist at 0x7f582b8bb7a0>: it's not the same object as main.ag_train_mnist
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "autotrain.py", line 287, in
myscheduler.run()
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/autogluon/scheduler/fifo.py", line 146, in run
self.schedule_next()
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/autogluon/scheduler/fifo.py", line 177, in schedule_next
self.add_job(task, **extra_kwargs)
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/autogluon/scheduler/fifo.py", line 223, in add_job
job = cls._start_distributed_job(task, cls.RESOURCE_MANAGER, self.env_sem)
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/autogluon/scheduler/scheduler.py", line 102, in _start_distributed_job
env_sem)
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/distributed/client.py", line 1501, in submit
actors=actor,
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/distributed/client.py", line 2492, in _graph_to_futures
"tasks": valmap(dumps_task, dsk3),
File "cytoolz/dicttoolz.pyx", line 179, in cytoolz.dicttoolz.valmap
File "cytoolz/dicttoolz.pyx", line 204, in cytoolz.dicttoolz.valmap
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/distributed/worker.py", line 3282, in dumps_task
return {"function": dumps_function(task[0]), "args": warn_dumps(task[1:])}
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/distributed/worker.py", line 3291, in warn_dumps
b = dumps(obj)
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/distributed/protocol/pickle.py", line 51, in dumps
return cloudpickle.dumps(x, protocol=pickle.HIGHEST_PROTOCOL)
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/cloudpickle/cloudpickle.py", line 1125, in dumps
cp.dump(obj)
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/cloudpickle/cloudpickle.py", line 482, in dump
return Pickler.dump(self, obj)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 437, in dump
self.save(obj)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 789, in save_tuple
save(element)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 549, in save
self.save_reduce(obj=obj, *rv)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 662, in save_reduce
save(state)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 859, in save_dict
self._batch_setitems(obj.items())
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 885, in _batch_setitems
save(v)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/cloudpickle/cloudpickle.py", line 556, in save_function
return self.save_function_tuple(obj)
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/cloudpickle/cloudpickle.py", line 758, in save_function_tuple
save(state)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 859, in save_dict
self._batch_setitems(obj.items())
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 885, in _batch_setitems
save(v)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 859, in save_dict
self._batch_setitems(obj.items())
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 890, in _batch_setitems
save(v)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/cloudpickle/cloudpickle.py", line 556, in save_function
return self.save_function_tuple(obj)
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/cloudpickle/cloudpickle.py", line 758, in save_function_tuple
save(state)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 859, in save_dict
self._batch_setitems(obj.items())
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 885, in _batch_setitems
save(v)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 859, in save_dict
self._batch_setitems(obj.items())
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 890, in _batch_setitems
save(v)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/cloudpickle/cloudpickle.py", line 556, in save_function
return self.save_function_tuple(obj)
File "/home/yllgl/anaconda3/lib/python3.7/site-packages/cloudpickle/cloudpickle.py", line 758, in save_function_tuple
save(state)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 859, in save_dict
self._batch_setitems(obj.items())
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 885, in _batch_setitems
save(v)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 504, in save
f(self, obj) # Call unbound method with explicit self
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 819, in save_list
self._batch_appends(obj)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 843, in _batch_appends
save(x)
File "/home/yllgl/anaconda3/lib/python3.7/pickle.py", line 524, in save
rv = reduce(self.proto)
TypeError: can't pickle CudnnModule objects

I use pytorch as backend. I also meet the same problem. If the problem occurs, how i can deal with it? Or how i can know which variable cause the problem.  My train script seems the same as the code provided in 'MNIST Training in PyTorch' tutorial.

@yllgl Sorry for the delay. Didn't notice that you have attached the code.
The dataset/dataloader should be created inside the training function or being created through @ag.obj() or @ag.func() https://autogluon.mxnet.io/api/autogluon.core.html?highlight=func#autogluon.func  then pass through the @ag.args().

@yaojunr Please see my reply to @yllgl . Let me know if you have resolved that.

Resolving, please re-open if issues still persist.


feat: warn on pypi conda clobbering

pixi will print a warning, if for some reason a conda package was mapped wrong
and we reinstall it again but as a pypi package.
Example:
using this custom mapping https://gist.githubusercontent.com/nichmor/6e0b8965e948536ed278f03aac31feb0/raw/635b0b849b88530a70889c4ef2f861bcb2ecc88e/wrong_mapping.json
and having both mdurl in dependencies and pypi-dependencies
user will see following warning

it's missing a warning for the usecase when we first install pypi and later conda which don't remove the pypi one and we end up with two .dist-info in site-packages

Conflict it seems!

Nice that you've included benchmarks! Just wondering what the cost is of doing the check as opposed to not doing it :), for these large environments?

Nice that you've included benchmarks! Just wondering what the cost is of doing the check as opposed to not doing it :), for these large environments?

added benchmark in the description!
but tl;dr - we add overhead of 0.100 seconds for large env


Resources representations with POST/PUT/PATCH and embedded resources

Hi, we are creating a Backbone project to easily manage HAL in our SPA apps.
On one of our project we need to POST/PUT/PATCH resources which embed other resources. After reading some posts on the net (mainly https://groups.google.com/forum/#!topic/hal-discuss/0-CYh0oFUUo and https://groups.google.com/forum/#!topic/hal-discuss/SLAchdbd8E0/discussion) it seems HAL does not defines how we should send the payloads.
As an exemple if we have a User with an embedded Address we could POST it using 2 different representations.
application/hal+json (is refused by Apigility)
PATCH /api/users/1 HTTP/1.1
Accept: application/hal+json
Content-Type: application/hal+json
{
    "firstName": "John",
    "lastName": "Doe",
    "_embedded" : {
        "address": {}
    }
}

application/json (works with Apigility)
PATCH /api/users/1 HTTP/1.1
Accept: application/json
Content-Type: application/json
{
    "firstName": "John",
    "lastName": "Doe",
    "address": {}
}

By default the first payload seems to be refused by Apigility which returns the following error :
{
    "type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html",
    "title":"Bad Request",
    "status":400,
    "detail":"Unrecognized field \"_embedded\""
}

In my opinion the 2 payloads should be authorized because the first one uses an application/hal+json content type and the second one an application/json content type, is this valid ?
But if we use HAL representations for GET requests why forbid the same representation for POST/PUT/PATCH requests by default ?
Perhaps Apigility should be able to manage both HAL serialization and deserialization ? Would it be a good or bad idea ?
What are best practices about this ?
Thanks,
Baptiste

Currently, HAL is used as the response format only within Apigility. I'm open to allowing it on incoming requests, and would welcome a pull request that would enable it. :)

I added a pull request here which should be enough to add this enhancement

This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at https://github.com/laminas-api-tools/api-tools/issues/51.


Repeated spam blocking on the same comment

Ignore my name. So, there was this spam reply on a normal comment, so I restored the comment, and then restored the spam reply, and the spam blocking started repeating itself on the normal comment.

@sussyamongussussy  Thanks for your feedback. I'll try to fix it

Fix in version 1.2.1
Released for Chrome: 2022-06-22
Released for Firefox: 2022-06-21


Feature request: Allow changing log level at runtime

Use case
If I have an issue in production, I want to set the debug log level to DEBUG right away. The fastest way for me to do that is through the AWS console. However, if I set the environment variable in the AWS console, the new log level doesn't seem to get picked up in existing execution environments, so the logger doesn't log any subsequent debug logs.
Solution/User Experience
I'm not sure if changing the environment variable in the AWS console updates environment variables within existing execution environments. If it does, then perhaps the logger could poll the environment variable every minute or so to make sure it's logging at the most recently configured level. Maybe there's a better way to handle this that I'm not considering.
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Lambda Powertools Tenets
[X] Should this be considered in other Lambda Powertools languages? i.e. Python, Java

However, if I set the environment variable in the AWS console, the new log level doesn't seem to get picked up in existing execution environments, so the logger doesn't log any subsequent debug logs.

This is not the expected behaviour and I'd like us to investigate about that's happening here. Can you please share with us the code you use to reproduce this issue?

Note: potentially a bug, needs investigation.

Nothing special:
export default new PowertoolsLogger({
  serviceName: 'ciam',
  sampleRateValue: 0.3,
});

and then calling logger.debug with messages throughout our app.
FWIW, I'm not really sure how/when AWS gets updated environment variables into the runtime. If changing the log level at runtime is intended to be working as it is, I can play around with it more and see if I find anything new.

I tried to reproduce the issue with a simple sam app template:

create sam-app with powertools ts (log level set to INFO)
invoke the http API
the log output in CW is INFO, log level set to INFO
change the env var in lambda console LOG_LEVEL to DEBUG
invoke the http API
the log output in CW is INFO and DEBUG, log level set to DEBUG.

It seems like you create and export your own wrapper around the logger, can you provide more details how you define and use it?

I'm going to leave the feature request open to give a chance to discover other use cases and hear other customers as well.
From this discussion it appears that there might be other use cases in which changing the log level at runtime might be useful.

I have another use case for this: dynamically setting the logging level based on a value in the event or context in a multi-tenant environment. Lambda authorizer may set a "debug" level that appears in the event.requestContext.authorizer.lambda.logLevel (for example). I can then "set" the log level for the execution based on that. This way if a specific user is having an issue I can increase logging to troubleshoot just that user without capturing data from all users (who havent authorized us to capture data in logs for example)


BUG: My Coingecko momentum bot exited, but I see no Telegram bot alerts that the bot was successful.

What is happening?

Section description
Provide as much context as you can. Give as much context as you can to make it easier for the developers to figure what is happening.

BUG: My Coingecko momentum bot exited, but I see no Telegram bot alerts that the bot was successful.
Position 1: https://etherscan.io/tx/0x4a834af98fe2aca5bf935fb9c0686b8ba4b93a89b524d898d175ea8e30b8c055
(Aug-18-2023 01:01:47 AM +UTC)
Exit position: https://etherscan.io/tx/0x2088b966c4b05fab3fa8b805676c7cb37432563e29d71ccbb1b3fd9ad26e281e
(Aug-18-2023 01:19:11 AM +UTC)
Telegram: We already have your address. We will notify you when any of your swaps are complete.
No Telegram alerts that bot exited.
What is the expected behaviour?

Section description
If you know, please write down what is the expected behaviour. If you don't know, that's ok. We can have a discussion in comments.

Telegram bot provides history of bot transaction with post. We need this.

@jamie088 closing as fixed.


start adding a little custom completion framework

This is kinda my vision for a little extensible completion framework. But of course, also open for discussion :)

@wolfv Should we close this?


Tag BoneScript v0.2.5

It would be nice if there was a tag for BoneScript v0.2.5. This would make it easier to find things in the future.

I can't use it on Beaglebone Green, right?

It's not support kernel 4.x.x for Beaglebone Green.

Use OctalBoneScript.

It is tagged.

Yes, it looks like it was tagged on Sep 17 2015 shortly after this issues was created. I hadn't spotted that.


hack: boilerplate: fix copyright year positioning

The copytight year should actually sit on top
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

/cherry-pick release-4.12


float accuracy on math functions

CrateDB version:1.1.2
JVM version:1.8
OS version / environment description:redhat 7.3
Problem description:datatype 'float' accuracy

Steps to reproduce:

create table cash(date string, spend float);
insert into cash(date, spend) values ('2017-05-03', 55.55);
insert into cash(date, spend) values ('2017-05-03', 34.55);
insert into cash(date, spend) values ('2017-05-03', 87.55);
select (0 - spend) sp,* from cash limit 100;

select (spend + 1.34) sp,* from cash limit 100;
Use case:

Feature description:
as you can see, math operation such as + - * /  would produce many decimal points, I cant find any function in scalar (https://crate.io/docs/reference/sql/scalar.html) can help me with this, is there any suggestions?
thanks

this looks like a bug, we'll have a look into it, thx for reporting.

@liujie20087349 fixed and released with Crate 1.1.3. Thanks for reporting.


CanCan Ability class does not mock

CanCan requires Ability.rb. Typically, this file is in app/models. This gives the rake task...
desc 'Build mockeries'
task :mock => :environment do
  Mockumentary.introspect
  Mockumentary.dump
end

... fits :
$ rake mock
undefined method `columns' for Ability:Class

A workaround is to move ability.rb to lib.

Actually I think the library should be smart enough to not try to introspect on non-AR models. It is really a good practice to create models that are not AR to encapsulate business logic.
I will write some tests and try to make this work over the weekend.
On a related note, Mockumentary should probably be smart enough to introspect on models in plugins, but I won't be implementing that until someone runs into the problem and requests it!
Thanks for alerting me to this

I ran into an issue today with acts_as_taggable_on. I also ran into issues with concerned_with, which I know is not used widely. So I have had to punt on using Mockumentary.
On Nov 17, 2011, at 11:47 AM, Kane Baccigalupi wrote:

Actually I think the library should be smart enough to not try to introspect on non-AR models. It is really a good practice to create models that are not AR to encapsulate business logic.
I will write some tests and try to make this work over the weekend.
On a related note, Mockumentary should probably be smart enough to introspect on models in plugins, but I won't be implementing that until someone runs into the problem and requests it!
Thanks for alerting me to this

Reply to this email directly or view it on GitHub:
https://github.com/baccigalupi/mockumentary/issues/1#issuecomment-2778405

I just released v 0.2.1 which will try to mock each model it finds, but fails gracefully if that isn't possible. It should address this and similar problems.


Deploy v0.1.0-rc-1 fixes to prod

Pull Request Test Coverage Report for Build 996788908

6 of 7 (85.71%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 84.906%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

accounts/views.py
1
2
50.0%

Totals

Change from base Build 996415879:
0.2%

Covered Lines:
810

Relevant Lines:
954

💛  - Coveralls


Deployment Group Create vs. Group Deployment Create

What is the difference between "deployment group create" and "group deployment create"
https://docs.microsoft.com/en-us/cli/azure/group/deployment?view=azure-cli-latest#az_group_deployment_create

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

ID: 649a07bb-0fa2-6c51-2820-88b1bafa80ba
Version Independent ID: ace434b7-7549-8e6d-cab0-1612f422a0cf
Content: az deployment group
Content Source: latest/docs-ref-autogen/deployment/group.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

ARM

They are both Azure resource manager
On Fri, Sep 3, 2021, 20:59 yonzhan @.***> wrote:

ARM
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/19451#issuecomment-912902339,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANWTTK63GO2NWFZDCGKNSTUAGKSDANCNFSM5DM3HZ6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@jenellea At present, we can deploy resources at different scopes: tenant, subscription, resource group, management group.
Therefore, the commands corresponding to the four scopes are az deployment tenant create, az deployment sub create, az deployment group create,  az deployment mg create
As the difference between az deployment group create and az group deployment create is that az group deployment create is an old command to be deprecated and will be replaced by az deployment group create. Therefore, it is recommended to use az deployment group create to deploy resources under the resource group scope.
You can execute az group deployment create -h to see the relevant deprecation information:
Command
    az group deployment create : Start a deployment.
        This command is implicitly deprecated because command group 'group deployment' is
        deprecated and will be removed in a future release. Use 'deployment group' instead.

Thank you.
On Sat, Sep 4, 2021, 21:04 Xing Zhou @.***> wrote:

@jenellea https://github.com/jenellea At present, we can deploy
resources at different scopes: tenant, subscription, resource group,
management group.
Therefore, the commands corresponding to the four scopes are az
deployment tenant create, az deployment sub create, az deployment group
create, az deployment mg create
As the difference between az deployment group create and az group
deployment create is that az group deployment create is an old command to
be deprecated and will be replaced by az deployment group create.
Therefore, it is recommended to use az deployment group create to deploy
resources under the resource group scope.
You can execute az group deployment create -h to see the relevant
deprecation information:
Command
az group deployment create : Start a deployment.
This command is implicitly deprecated because command group 'group deployment' is
deprecated and will be removed in a future release. Use 'deployment group' instead.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/19451#issuecomment-913082200,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANWTTMIBX5SLCDKWOT2PGLUALT5FANCNFSM5DM3HZ6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Suggestion: Terminal UI

What are the chances of having the ability to create terminal UIs in TTY::Box (or somewhere else in the TTY toolkit)?
I think with what TTY brings to the table, having a minimum viable solution - one that allows creating panels that can a) be refreshed on interval and b) always contain their own content - is not too far out of reach, is it?
So we can do UIs like this, without relying on the complex ncurses related projects?

Ideally (but I know highly unlikely), I wish Ruby would have something similar to Go's termui:

I really like your suggestion and think that's the ultimate future for TTY. Provide the ability to build rich terminal interfaces. However, before this dream is realised many things have to happen.
The most important of them is to make components work with absolutely positioned content like tty-pie. Components like tty-progressbar, tty-spinner or tty-tree could be made to work this way or alternatively they could inherit parent box size to determine their own display width etc...
The second thing that needs to happen. There are still a few components missing like plot lines or sparklines to help with graphical interfaces. I think adding more components would get TTY much closer to rich UIs.
As for tty-box, for me, its sole purpose is drawing terminal boxes. I wouldn't want to expand it to start handling complex terminal layouts/dashboards. I feel this belongs into another gem such as tty-ui which would further build on the concept with an easy and declarative way to build layouts out of boxes. This could mimic the concept of CCS grids where user would specify how many panels they want and assign proportional values to each of them. They could also specify the type of a box, for example, a progress bar box would have already preconfigured formatting and display. But this requires some thought as to how it would work. I may create a repository so we can collect thoughts/ideas.
As for working on the idea. Finding time for OSS is a constant challenge. I have already many plans for things I'm going to do in the next few months. One of them is rewritting tty gem to remove direct dependency on bundler.

Sounds great. I agree it is a separate gem, only TTY Box was the place that made most sense to post an issue :).

Any progress on this thinking? Would love to be able to have CLI dashboards like this. And also, the ability to have auto-scrolling content inside of a box (following content output).

@kevinelliott Thank you for expressing support for this. I'm all for the idea and have plans for many new components that will make this possible. However, as you probably imagine to get to such a place requires plenty of work in my limited spare time. I maintain many Ruby projects including 25 TTY gems. My priorities currently include updating strings components like strings-case and making a new release of tty toolkit. I enabled discussions in the TTY project where you can share your ideas for new components. I had been thinking about the viewport scrolling component but it will need to wait for some unspecified time before I get around to implementing it. I wish I had a better answer but that's how things are at the moment.


text improvement

replaced 'contributing' to 'contributings'

replaced 'contributing' to 'contributings'

It should be contributions actually


[RFC] add tox.ini / support for pytest

This is rudimentary, but makes it a lot easier to run the tests.
Please consider adopting it and mention it in the docs.
It could also be used on Travis.

Coverage remained the same at 99.63% when pulling 730edf784a6c9c52361229ef2e594eca86342f5a on blueyed:tox into 7c9253656cb6bd23d0889dc87ecc92c11922d507 on djangonauts:master.

@blueyed excellent suggestion. I have always been lazy on this subject. I would like to go ahead on this, could you rewrite the Test section of the README and .travis.yml too?

I've hoped that you would pick it up from here.
I can do it, of course - but not soonish.. ;)

"Now is better than never, although never is probably better than right now" (cit.)

never is probably better than right now

I am taking this.  Feel free to adopt it, of course.

I don't understand why you closed it. Can it stay open as a reminder for when me or other contributors will have time to look into it?

Coverage remained the same at 99.63% when pulling 730edf784a6c9c52361229ef2e594eca86342f5a on blueyed:tox into 7c9253656cb6bd23d0889dc87ecc92c11922d507 on djangonauts:master.

Coverage remained the same at 99.63% when pulling 730edf784a6c9c52361229ef2e594eca86342f5a on blueyed:tox into 7c9253656cb6bd23d0889dc87ecc92c11922d507 on djangonauts:master.

Can it stay open as a reminder for when me or other contributors will have time to look into it?

Sure.  I understood it wrongly then in the beginning - and came across it when going through my open PRs.  Sorry.

I've updated it: it now allows you to use pytest/pytest-django through tox (used in one matrix entry on Travis).
I'll need to revisit myself, but would appreciate any comments/review on it already.

@blueyed great!
Could you squash the commits?
One question, why adding pytest to the build? Wouldn't that slow down the build with no practical advantage?

Could you squash the commits?

Sure, please never merge fixup! commits.. :)

One question, why adding pytest to the build? Wouldn't that slow down the build with no practical advantage?

Only for demo.. we could use pytest for only one / a few in the end.

@blueyed can we keep it simple and avoid adding unneeded dependencies to the build please?

What's the problem with having one build also pip-install pytest/pytest-django?
It is more comfortable to have pytest as a test runner, therefore I added it to tox / config for it, but then I think it should also get tested/used on CI to catch any problems with it.

I don't want to use more resources than needed and I don't want to slow down the build unnecessarily. We are using a free service after all.
Developers can use pytest offline in their own dev environment.

Do you really think an additional pip install pytest pytest-django about once per month is a problem for Travis?! (https://travis-ci.org/djangonauts/django-rest-framework-gis/pull_requests)
But given that, please comment on the build matrix I came up with otherwise - there are probably things to strip there then?!

Old (9 builds): https://travis-ci.org/djangonauts/django-rest-framework-gis/builds/229053544
New  (11, but 10 with -pytest (re)moved): https://travis-ci.org/djangonauts/django-rest-framework-gis/builds/232514268; but covers Django 1.11.
To be clear: my idea was to use py36-dj110-pytest instead of py36-dj110 - which would result in 10 builds.

Squashed, and removed pytest from Travis.  Also the config for it - still works through Tox.

@blueyed thanks a lot :+1:!

@nemesisdesign
Thanks for merging it! :)


Error while updating property 'accessibilityState' of a view managed by : RCTView , null ,   Value of disabled cannot be cast from ReadableNativeMap to Boolean

New Version
0.70.4
Old Version
0.68.2
Build Target(s)
platform :ios, '12.4'
Output of react-native info

npx react-native info<<<<<<<<<<

info Fetching system and libraries information...
System:
OS: macOS 11.4
CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz
Memory: 104.48 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.13.2 - ~/node_modules/.bin/node
Yarn: 1.22.19 - ~/.yarn/bin/yarn
npm: 8.17.0 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
Android SDK:
API Levels: 28, 29, 30, 31, 33
Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0
System Images: android-28 | Google APIs Intel x86 Atom_64, android-29 | Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom, android-32 | Google APIs Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8139111
Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
Languages:
Java: <IP_ADDRESS> - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.4 => 0.70.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Issue and Reproduction Steps
we faced this while upgrading react native version from 0.68.2 to 0.70.4
we also tested by creating a new project with the latest version it also shows the same error
This happens when we pass an object to disabled property in TouchableOpacity
<TouchableOpacity
onPress={onPress}
disabled={ {} }                           //it will show error
disabled={ {} ? false : true }    //it won't show error

Now the problem is that we are using this type of condition on the whole app  (disabled={item?.address}) and we have to change it everywhere

Something very similar started happening to me after I updated to 0.70:

The problem was that my button looked like this:
    <Button
       label={'Next'}
       disabled={!phone || !country || error} // <--- error was an empty string
     />

I switched it to:
    <Button
       label={'Next'}
       disabled={!phone || !country || !!error} // <--- "!!error" is now a boolean
     />

So, Button, TouchableOpacity, Pressable which uses disabled.It takes a Boolean or Falsey / Truthy values. We can convert the value using !! operator

Something very similar started happening to me after I updated to 0.70:

The problem was that my button looked like this:
    <Button
       label={'Next'}
       disabled={!phone || !country || error} // <--- error was an empty string
     />

I switched it to:
    <Button
       label={'Next'}
       disabled={!phone || !country || !!error} // <--- "!!error" is now a boolean
     />

that was the same issue for me , solved by setting disabled field with a boolean value

i was having the same issue, was not explicitly checking if value is null.
<TouchableOpacity     disabled={registeredDevices[module${index + 1}`]}
onPress={() => handleModuleClick(index + 1)}

<Text>{index + 1}</Text>

`
so i made it
<TouchableOpacity     disabled={registeredDevices[module${index + 1}`] !== null}
onPress={() => handleModuleClick(index + 1)}

<Text>{index + 1}</Text>

`

Yes! TouchableOpacity's disabled prop accept a bool value. If you need to calculate this bool value with a function, you should invoke the function in the disabled prop like the example below.
<TouchableOpacity **_disabled={isDisabled()}_**
<Text >Hamid Ali</Text>
</TouchableOpacity>

I hope, it might help someone.


Support for "SSESpecification" Schema option

DynamoDB recently announced server-side encryption, and it would be great if we could enable it when creating a table via the Dynamoose Schema options.. or at the very least, supply a way for users to pass-through additional options that aren't parsed by the Dynamoose API.

+1 I'm also very interested in this feature.

If anyone would like to create a PR for this I would be happy to review it and try to get it merged in.

@chaleCB and @RobertNorthard, I created a PR #306 for this feature. Just tested it and it seems to be working pretty well. You can either take my branch on my fork until we get this into a Dynamoose version or just wait until we get it added.
Would love to hear any input you have on it as well.
I will be keeping the PR open for a little bit just so I can try to figure out why that one test case isn't working and how I can fix it.


Add billing_address and shipping_address array parameters to the crea…

…teOrder description

Add billing_address and shipping_address array parameters to the createOrder description

At the moment you can only pass a billing or shipping ID to the API using this integration as it's missing the 'shipping_address' and 'billing_address' array parameters. Please see example number two here in the TradeGecko API docs, where you can create an order with a shipping or billing address with only one request, rather than having to create the addresses first.
Not sure why this is, but it would make sense to implement everything that's within the API docs.
https://developer.tradegecko.com/docs.html#2-order-with-existing-customer-but-new-address

Hi,
Thanks for adding this. I'm unfortunately not maintaining this anymore so it may be possible that new features may not be supported. I have merged this one though and tagged a new version ;).


python3Packages.ihatemoney: 4.1 -> 4.2

Update.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

What is the package name? I'm not finding it as "ihatemoney".

I fixed the title of the PR. The commit messages are correct.

I updated ihatemoney to 4.2 but haven't tested enough yet.

@GrahamcOfBorg build python3.pkgs.ihatemoney.tests

@GrahamcOfBorg build python3.pkgs.ihatemoney.tests.ihatemoney.ihatemoney-postgresql  python3.pkgs.ihatemoney.tests.ihatemoney.ihatemoney-sqlite

Looks like the PR is ready.

/marvin opt-in

/status needs_review

/status needs_work
That should work in review comments too.

Also the testsuite fails for me in nix-review.

Ah I can reproduce the test failure when I rebase on master.
A git bisect indicates that it's caused by 86990d60071a3be8ea25d2ad2f79a0ba096331b6     pythonPackages.wtforms: 2.1 -> 2.3.1
and apparently ihatemoney only supports 2.2.1: https://github.com/spiral-project/ihatemoney/commit/53dae96bdbfcf09f4cef56afda8a7ad567458eeb
I wonder what is the way to go from there.

upstream knows about the problem https://github.com/spiral-project/ihatemoney/issues/567

Pinning dependencies in python is generally messy. For a python application we could get away with it, for a library we can't.
Probably should have caught this in the initial review: Is this really a library? Looks more like an application to me. Search https://nixos.org/nixpkgs/manual/ for "Building packages and applications" for more info.
Since upstream knows about it we could also

wait for a fix there and apply the patch
fix it for them, create a PR and then apply the patch.

Depending on how much work you want to invest.

Probably should have caught this in the initial review: Is this really a library?

It is a wsgi application. That is, uwsgi starts a special python interpreter, and then imports ihatemoney. So for all intents and purposes, it is a library.
Regarding patching, I had a quick look, and have no idea what happens.
And regarding waiting, current version of ihatemoney is also affected.
I'll try and see if it still works if I disable this test in the coming days.

Result of nixpkgs-review pr 85023 1

2 packages failed to build:
- python37Packages.ihatemoney
- python38Packages.ihatemoney

8 packages built:
- python27Packages.sqlalchemy-continuum
- python27Packages.sqlalchemy-i18n
- python37Packages.debts
- python37Packages.sqlalchemy-continuum
- python37Packages.sqlalchemy-i18n
- python38Packages.debts
- python38Packages.sqlalchemy-continuum
- python38Packages.sqlalchemy-i18n

@GrahamcOfBorg build python37Packages.ihatemoney python38Packages.ihatemoney

Mic92: There is a known problem with a too-new dependency.

I thought a bit about this, and came to the conclusion that I can override the dependencies of ihatemoney locally because ihatemoney will never be the dependency of something else. It is only a library because it must be imported by uswgi, but it will not be depended upon by some other python module.
I also updated uswgi and removed the now-unneeded workaround. I tested this in a vm, and csv downloading works :)
/status needs_review

I agree with your reasoning, since this is a de-facto python application. Still, since we kind of have an (unwritten?) policy against dependency overrides within python-module I'd like @FRidh's okay on this.
@FRidh do you agree that its fine to override the dependencies here, since the module will only ever be used as an application (but through uswgi)?

@jonringer do you maybe have an opinion on this? See my last comment.
/status needs_work
(work = feedback to get it out of the needs_review queue, will be improved by https://github.com/timokau/marvin-mk2/issues/29)

Well, lacking any feedback I will just assume its fine. Please add the python.pkgs prefix to https://github.com/NixOS/nixpkgs/pull/85023/commits/ebc28de6a9001052abdc6bd6141ce0c228275d41, then this should be good to go.
I would still prefer to avoid hardcoding the debts rev to enable automatic updates, but If you as the maintainer want to stay on top of updates manually, that is your call.

done. The nixos tests still pass locally.

Thanks, and thank you for your patience!


Fixes #748

Improved the policy example to include the needed permissions as described in issue #748

/ok-to-test

Thanks for fixing this， would you help add ec2:DescribeAddresses as it specified in https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/elb-api-permissions.html

Of course, added a commit to add ec2:DescribeAddresses.

/lgtm

/approve


Expand the potential class

Right now the potential from LAMMPS supports inputs such as eam, tersoff, lenard-jones and reaxff. Each of these potentials is in principle a distinct data-type. The question is on whether one should condense this as much as possible, so that there is only one potential data type.
If well the LAMMPS potentials can look very different depending on how they were generated, from the data perspective this should not matter, the user should be able to store whatever potential they want, and then use it in their calculations with minimal issues for the plugin, as the large majority of potentials are files which are read by LAMMPS at run time (exception being the lenard-jones potentials)
Hence, what could be done, is to have the potentials being an instance of orm.SingleFileData where the potential is read, from the file. The user would have to indicate which kind of pair_style is being stored, so that the attributes are properly set, similarly to what is done now. This would allow the user the capability of using any kind of potential without having to develop a new plugin for that specific type of potential. Of course  a check would have to be done to ensure that the potential lines where LAMMPS knows how to read the potential data are accurate for all (or at least many) of the potential types. If a pair_style has not been checked this could raise a warning letting the user know that this can be an issue. Of course this is a bit more complicated for hybrid potentials.
One issue that also needs to be addressed is how to tag the potentials, in DFT codes one usually has the potential family concept, allowing one to group all the potentials belonging to a given exchange correlation potential or pseudopotential family. This makes reusing and querying for potentials quite simple. However, this is not so for LAMMPS potentials, where tagging is mostly an issue of using the extras provided by the user.
Hence, it might be good to provide a way for the user to set certain variables at the potential creation time to allows for a consistent potential storage and tagging. This could be done by the user passing a dictionary at creation time that will check for certain keys and attach them to the appropriate attributes. I think that a good idea would be to use a similar system than what is used in OpenKIM, where could pass the authors of the potential, the year, references, etc. Of this way one could have a consistent way of querying and storing the potentials. Of course, one should not be prevented from creating the potential node if these variables are not passed, but then it would be up to the user to find the "correct" potential using some sort of convention.
What do you think about this @chrisjsewell ?

Taking inspiration from the aiida-pseudo the potential class has been expanded so that the md5 checksum is calculated and of that way one can avoid creating a potential in the database if it already exists, instead it will be taken from the db and used.
To standardize the tagging of the potentials a series of required attributes species, pair_style and the filename have been added as attributes. Other optional attributes have been added which are in line with those in the OpenKIM schema, these are content_origin,  content_other_locations,  data_method, description, developer, disclaimer, generation_method, properties, publication_year, source_citations, title. These attributes will allow for an easier identification of the potentials from the database for later usage.

Closed via #35


[math] Big-endian buffer not supported on little-endian compiler

Relative to https://github.com/silx-kit/silx/pull/1140
Numpy support operations on little and big endian arrays
In [9]: numpy.array([0, 1, 2, 3], dtype=">f") + numpy.array([0, 1, 2, 3], dtype="<f")
Out[9]: array([ 0.,  2.,  4.,  6.], dtype=float32)

Our math function should support different endianness
In [6]: silx.math.combo.min_max(numpy.array([0, 1, 2, 3], dtype="<f"))
Out[6]: <silx.math.combo._MinMaxResult at 0x57bf7b8>

In [7]: silx.math.combo.min_max(numpy.array([0, 1, 2, 3], dtype=">f"))
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
E:\valls\silx\bootstrap.py in <module>()
----> 1 silx.math.combo.min_max(numpy.array([0, 1, 2, 3], dtype=">f"))

E:\valls\silx\silx\math\combo.pyx in silx.math.combo.min_max (silx\math\combo.c:14149)()
    316         return _finite_min_max(data, min_positive)
    317     else:
--> 318         return _min_max(data, min_positive)

E:\valls\silx\silx\math\combo.pyx in silx.math.combo._min_max (silx\math\combo.c:3652)()
    115 @cython.boundscheck(False)
    116 @cython.wraparound(False)
--> 117 def _min_max(_number[::1] data, bint min_positive=False):
    118     """:func:`min_max` implementation including infinite values
    119

ValueError: Big-endian buffer not supported on little-endian compiler

As we anyway make sure it is a contiguous array before going to C/C++/Cython, it should not be too much effort to make sure the data have a native endianness.

I reopen this issue.
All Cython modules are subject to this issue, so if we have to support endianness, let's do it everywhere...

I had a look on it.
Histogramnd and HistogramndLut had the same issue.
I haven't see other peace of code which can bring this issue. In most of case we are directly setting the type requested which will be native.
A second look would be better.


sdba - Optimizations for DQM and others

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #455

[x] Tests for the changes have been added (for bug fixes / features)
[x] Documentation has been added / updated (for bug fixes / features)
[x] HISTORY.rst has been updated (with summary of main changes)
[ ] bumpversion (minor / major / patch) has been called on this branch
[ ] Tags have been pushed (git push --tags)

What kind of change does this PR introduce?

Added norm_group to DetrendedQuantileMapping so that a different grouping can be used in the normalization steps. DQM.adjust also has a new  normalize_sim arg. When True, sim is normalized along norm_group before being detrended along group. When False (default), sim is only detrended along norm_group. This is quite useful as the detrending process has poor performance compared to simple normalization, but only detrending by month creates artefacts at the month boundaries.  Optimal performance is obtained with: norm_group='time.dayofyear', group='time.group', normalize_sim=True.

Added BaseAdjustment.save_training() and  BaseDetrending.save_fit() to save the training/fit datasets. This can help dask as adjustment processes create an enormous amount of small operations, especially with "time.dayofyear" grouping. Default is to save to a temporary file that is deleted when the adjustment object is garbage-collected. A persistent file can be created by passing filename or the temporary file's directory can be given with tempdir.

Does this PR introduce a breaking change?

No

Pull Request Test Coverage Report for Build 1994

0 of 70 (0.0%)  changed or added relevant lines in 4 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-1.2%) to 75.677%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

xclim/sdba/base.py
0
3
0.0%

xclim/sdba/processing.py
0
6
0.0%

xclim/sdba/detrending.py
0
25
0.0%

xclim/sdba/adjustment.py
0
36
0.0%

Files with Coverage Reduction
New Missed Lines
%

xclim/sdba/adjustment.py
1
0%

xclim/sdba/detrending.py
2
0%

Totals

Change from base Build 1983:
-1.2%

Covered Lines:
2654

Relevant Lines:
3507

💛  - Coveralls

I agree with the spirit of your comments. I believe one strength of xclim.sdba is the use of xarray/dask and the tremendous performance improvement it can provide when compared to other options. For large workloads, dask does have its limits and the save_training/fit function is an example of optimization we can add to help dask while staying in kinda-high-level programming.
For the norm_group/normalize_sim duo, I am ambivalent. As @RondeauG  and I came to realize is that QM with monthly grouping is not quite as robust as we thought. However, this 'dayofyear' pre-normalization really helps. We could suggest to the user to build its own process, that is in fact what I do in the notebook of #478.
D'ailleurs, I think that notebook adds explanations where the docstrings could be still unclear.

Just to give my opinion on this matter:
As @aulemahal mentioned, we discovered that grouping per month is not reliable enough, especially for months that exhibit large variations (i.e. several degrees of warming between 1st and 30th of June). Therefore, for an adequate adjustment, it is essential to normalize the data using a smaller window (time.dayofyear does the job adequately, especially if using a window).
The issue is that for large datasets, dask is overloaded by those smaller groups (as @aulemahal mentioned in another comment).
These are the conclusions of my tests:

norm_group=Grouper(group='time.dayofyear') is essential. Any other option (except maybe weekofyear?) will simply create bad results whenever there are strong variations within the groupings decided by the user. Therefore, I don't think that norm_group/normalize_sim are good arguments to provide the user, as anything other than norm_group=Grouper(group='time.dayofyear') is wrong. A better parameter, if we want one, could be norm_window. The difference in results between window=1 vs. window=31 seemed rather small, while window=31 was much more costly to run.

In any case, using norm_group=Grouper(group='time.dayofyear') is costly. There's no way around that. We should warn users that if this is too much for dask, the domain should be cut in smaller pieces, or the user should use the more optimized (but complex) code provided in @aulemahal 's Notebook. Using his Notebook, I have roughly the same performance as before (~25 minutes to bias correct 15 000 grid cells).

I'm :-1: on asking users to cut the domain. I think it's our job to solve this problem.
Is this relevant: https://docs.dask.org/en/latest/array-creation.html#intermediate-storage ?

If we can solve the problem, I'm all for it. The link you provided mentions "It can be useful as a checkpoint for long running or error-prone computations.", so... maybe?
The main problem that we have is that with the time.dayofyear groups, dask gets overloaded while building its task tree ("arborescence de tâches") : the process never gets parallelised, the RAM usage just grows and grows until you either stop the code or it reaches the limit of the computer. This is why our solution was to write more often on disk, as this reduces the number of tasks that dask has to perform at once.

After discussion with the whole user base, I followed the comments here and removed save_training and save_fit. Loading the datasets in memory is now the recommended way of dividing the workload in two, the notebook in the other PR has been update as well.


asyncio.timeout() is missing documentation in Python 3.6

I see in What’s New In Python 3.6 that asyncio.timeout will be reintroduced in Python 3.6, but I don't see docs for it in 3.6.0b1 version in official docs.
/cc: @asvetlov

It was ripped out after inclusion.
But you can use async_timeout which is a clone of ripped version.

Oh, I see... Then this issue is resolved, thanks for pointing on async_timeout!

FWIW I removed it from the what's new. (If we end up adding something like
this back we'll update it again.)


feat: support ClusterIP service

This PR allow generation of a ClusterIP service. By doing so, we give user the freedom to choose how they want to expose their wireguard instance. For example, if they are using the Gateway CRD, they could use UDPRoutes to expose the wireguard instance

:tada: This issue has been resolved in version 2.6.0 :tada:
The release is available on:

v2.6.0
GitHub release

Your semantic-release bot :package::rocket:


Adding Volume Control either digitally or using analog input

I am attempting to use a potentiometer to add analog volume control to the i2s play back by modifying the play function like below however this is causing the esp32 to panic do you have a better idea of how this could be implemented digitally?:
void play(Output *output, const char *fname)
{
  int16_t *samples = (int16_t *)malloc(sizeof(int16_t) * 1024);
  // open the file on the sdcard
  FILE *fp = fopen(fname, "rb");
  // create a new wave file writer
  WAVFileReader *reader = new WAVFileReader(fp);
  ESP_LOGI(TAG, "Start playing");
  output->start(reader->sample_rate());
  ESP_LOGI(TAG, "Opened wav file");
  // read until theres no more samples
  int16_t samples_read_signed;
  uint16_t i;

  while (true)
  {
    int16_t samples_read = reader->read(samples, 1024);
    if (samples_read == 0)
    {
      break;
    }

    Volume = float(analogRead(PIN_VOL_ADC)) / 2047;

    for(i=0;i<samples_read;i+=2)  // We step 2 bytes at a time as we're using 16bits per channel
   {
     samples_read_signed=*((int16_t *)(samples_read+i));   // Get the Byte address, convert to an int pointer, then get contents of that address as an int
     samples_read_signed=samples_read_signed*Volume;         // multiply by the volume - a value that will be between 0 and 1, 1 would be full vol
      *((int16_t *)(samples_read+i))=samples_read_signed;   // Store back in the memory location we got the sample from

    }

    ESP_LOGI(TAG, "Read %d samples", samples_read);
    output->write(samples, samples_read);
    ESP_LOGI(TAG, "Played samples");
  }
  // stop the input
  output->stop();
  fclose(fp);
  delete reader;
  free(samples);
  ESP_LOGI(TAG, "Finished playing");
}

Try adding this line to your platformio.ini it will switch on exception decoding and should give you a better idea of what's going wrong with the code:
monitor_filters = esp32_exception_decoder

But, you will kick yourself. You are currently trying to use samples_read as if it were the buffer of samples - it's the count of how many samples were read. You shouldn't need to do any casting as the samples buffer is already a pointer int16_t
for(int i = 0; i<samples_read; i++) {
    samples[i] = samples[i] * volume;
}


No such file or directory: '../../data/mot17/train'

*/CenterTrack/src/tools$ bash get_mot_17.sh
Traceback (most recent call last):
  File "convert_mot_to_coco.py", line 22, in <module>
    seqs = os.listdir(data_path)
FileNotFoundError: [Errno 2] No such file or directory: '../../data/mot17/train'
Traceback (most recent call last):
  File "convert_mot_det_to_results.py", line 14, in <module>
    os.mkdir(OUT_DIR)
FileNotFoundError: [Errno 2] No such file or directory: '../../data/mot17/results/'

Fixed by
https://github.com/xingyizhou/CenterTrack/pull/290
https://github.com/xingyizhou/CenterTrack/pull/290/commits/a5543cfc9f9fadf9bf4d27cb4f7816982c2b289a
https://github.com/bryanbocao/CenterTrack/blob/master/src/tools/get_mot_17.sh


Feat/fetch single user api

Description
Develop API endpoint to fetch a single user
Acceptance Criteria

The endpoint should be accessible at api/v1/users/:userId
The endpoint should accept HTTP GET requests.
The endpoint should be secured to ensure that only authenticated users can fetch all users
The endpoint should check that the user has the appropriate permissions
Requests to the endpoint must include a valid authentication token in the Authorization header. Authorization: Bearer
Given a request with a valid user ID, when the user is authenticated and authorized, the system should retrieve the user's information with a status code of 200.
Given a request with an invalid or non-existent user ID, when the user is authenticated and authorized, the system should return a 404 Not Found status.

Request
Endpoint: GET /api/v1/users/:userId
Parameters:
userId: string
Expected Outcome
Successful Response
{
  "status": "success",
  "message": "User retrieved successfully",
  "user": {
    "id": "String",
    "name": "String",
    "email": "String",
    "phoneNumber": "String"
  }
}

Error Response:
{
  "status":string,
  "message": string,
  "status_code":int
}

Purpose
Provides a backend service which allows users to fetch a single user
Requirements

Develop server-side logic to fetch a single user
Ensure compliance with security standards for handling user information.

Tasks
Create User Fetching Logic

[x]  Implement the GET /api/users/:userId endpoint.
[x]  Query the database to retrieve user details by user ID.
[x]  Handle errors and return appropriate responses when the user is not found.
Authorization Checks
[x]  Ensure that only authorized users (e.g., the user themselves or administrators) can access this endpoint.
[x]  Implement middleware to check if the requester is authorized to fetch user details.
Database Operations:
[x]  Create a schema for storing user details if not already existing.
[x]  Securely retrieve user details from the database.
[x]  Ensure compliance with data protection standards.
Error Handling and Logging:
[x]  Implement comprehensive error handling for different failure scenarios (e.g., user not found, unauthorized access).
[x]  Log errors and access attempts for monitoring and troubleshooting.
Tests
[x] Write unit tests for the GET /api/users/:userId endpoint.
[x] Write unit tests for validation and error handling logic.
[ ] Write integration tests for the end-to-end user fetching process.
[ ] Test the full flow from requesting user details to receiving the response.
[x] Ensure the system handles successful and failed requests appropriately.

Kindly pull changes from the dev branch


WIP: (refactor) Update todo example to Polymer 2.

Work in progress:

[ ] The bower_components directory needs to be updated using a clean bower install.
[x] The polymer-2 branch in the dolphin-platform-polymer repository needs bugfixes to be merged.

This change is

Coverage remained the same at 60.156% when pulling 397f62cabb95cd7819c79638d47a904535bf47a8 on feat/todo-example-poly2 into 5ab95dbf84ceeaca773f13806a389b4d2c8f1ec7 on master.

Coverage increased (+0.05%) to 60.202% when pulling ad75e1eaa3769a9cc187112110abf7d963f5f70f on feat/todo-example-poly2 into 5ab95dbf84ceeaca773f13806a389b4d2c8f1ec7 on master.

Coverage increased (+0.05%) to 60.202% when pulling ad75e1eaa3769a9cc187112110abf7d963f5f70f on feat/todo-example-poly2 into 5ab95dbf84ceeaca773f13806a389b4d2c8f1ec7 on master.

Coverage increased (+0.05%) to 60.202% when pulling 4c0bf7c4a0e2f03d8db4b3b05276baba48afb66f on feat/todo-example-poly2 into 5ab95dbf84ceeaca773f13806a389b4d2c8f1ec7 on master.

@hendrikebbers The latest commits change the font-roboto dependency to font-roboto-local to prevent requests to fonts.googleapis.com being send in the examples.

Coverage increased (+0.05%) to 60.202% when pulling 25ef9a6e3e02d75b6c9eef642760d6425eb7519b on feat/todo-example-poly2 into 5ab95dbf84ceeaca773f13806a389b4d2c8f1ec7 on master.


fix stackdriver adapter getting shutdown (#15612)

Manual cherry pick of #15612. action/merge-to-release-1.2-branch label does not seem to function.
@fpesce Could you please help to merge this? This is a bug in Stackdriver adapter that is found and fixed by community contributor. Without this fix, stackdriver adapter will stop after the first push. Thank you!
cc @kyessenov @canthefason

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: bianpengyuan
To complete the pull request process, please assign kyessenov
You can assign the PR to them by writing /assign @kyessenov in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

mixer/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm
/approve
CLA verified (two author PR)

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bianpengyuan, kyessenov
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS [kyessenov]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@bianpengyuan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
774de8795480dc796adcec91fe09c888ff0a2a8b
link
/test integ-mixer-k8s-presubmit-tests-release-1.2

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-mixer-k8s-presubmit-tests-release-1.2

@fpesce gentle ping. Could you please help to merge this? thanks!

@fpesce This is a critical for stackdriver adapter. PTAL.


obtaining the stream state

HTTP Datagrams (#3522) require us to track the state of the underlying QUIC stream:

It is not permitted to send DATAGRAMs for a stream whose send side is closed. We should reject calls to SendDatagram in our API.
Conversely, when DATAGRAMs are received for a stream whose receive side is closed, they MUST be discarded.

My first idea how to implement this was tracking the state transitions by wrapping a quic.Stream. For example, we know that the send side is closed when Closed and CancelWrite are called. So far, so good. However, the send side can also be closed by receiving a STOP_SENDING frame. As a consumer of a quic.Stream, we'll only learn about this on the next call to Write.
But here's the problem: What if the application never writes again. Sure - it should not just walk away from the stream without either calling Close or CancelWrite, but there's no guarantee for that. At the QUIC layer, we'd garbage collect the stream, whereas on the HTTP/3 layer this stream would remain open indefinitely.
The same happens on the read side, if the application never calls Read after the RESET_STREAM has been received. Again, the application shouldn't do that (and risks leaking the stream if it does and no RESET_STREAM is received), but we also don't have a guarantee for that.
It would be nice if there was an API that could be used to obtain the stream state, avoid any synchronization issues. It would be even nicer if no quic.Config entry was required, since our HTTP/3 API allows using a QUIC connection.

Here's an API proposal:
We add a new method to the SendStream, ReceiveStream and Stream:
type StreamState int

// TODO: define constants for all stream states defined in RFC 9000

type {Send,Receive}Stream interface {
     StateTransition() <-chan StreamState
}

The channel returned here is a buffered channel, with a capacity sufficient to hold all possible state transitions. I haven't done the math yet, but 8 should be sufficient, maybe even smaller.
The nice property of this channel API is that it doesn't matter when the application calls it: For example, the stream might already be closed when it is called. The channel will then contain all state transitions that happened to reach this state.

On the other hand, it requires a Go routine to block on this channel. Maybe it's better to set a callback:
type {Send,Receive}Stream interface {
     OnStateTransition(func(StreamState))
}

This callback would be called multiple times if multiple state transitions had already happened.

Note that the callback allows us to have multiple layers set a callback. We'd just wrap the existing callback. It's not terribly efficient, but should be fine for a limited number of callbacks. I don't see how this would work with the channel-based API.

Alternatively, we could consider changing how the QUIC layers reports streams as completed: We could only do that once the STOP_SENDING error (for send streams) or RESET_STREAM error (for receive streams) has been read by the application.
This would enforce "correct" usage of the stream API, and allow applications to more easily track the stream state by just wrapping a quic.Stream. The downside is that this change is pretty subtle, and we really need to make sure that we get it right, otherwise we risk deadlocks if streams don't get garbage collected.

Another downside is that the stream actually needs to be used (read from and written to). It's possible to just open the HTTP stream, and send and receive datagrams, but that means you'll never observe the state transition.


Parse envars in middleware

Codecov Report

Merging #15 into master will decrease coverage by 2.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
- Coverage     100%   97.87%   -2.13%
==========================================
  Files           2        2
  Lines          34       47      +13
==========================================
+ Hits           34       46      +12
- Misses          0        1       +1

Impacted Files
Coverage Δ

middleware.py
97.77% <0%> (-2.23%)
:arrow_down:

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 427db20...81280ec. Read the comment docs.


Figure out an easy way to run the test suite locally for all combos of ORM, Ruby, and Rails

Probably using commands involved with the appraisal gem that we already use https://github.com/thoughtbot/appraisal

I've tried using https://github.com/nektos/act with not a whole lot of luck. It doesn't seem to play well with build matrices.

Tried out that tool and I had the same issue with the build matrices. The output was also super verbose. I think the best bet is going to be for users to push their code to their own forked repos and check out the build results there.


JAVA-3456: Make ClassModel immutable

Evergreen patch: https://evergreen.mongodb.com/version/5da8bc5b9ccd4e627b13dd4b

Online research shows that unit testing immutability is either not possible or very expensive. There are a couple of tools available that claim to detect immutability, but they do not fully guarantee immutability. Closing PR.


Updated data JSON; added some MC

Updated 2015B & 2015C with latest Golden JSONs (re-reco & 2015D with almost 0.5 fb-1 will not be long now I guess?)
Added some ttbar MC (TTV, high-mass ttbar, and "the" official ttbar MC sample)
Scaled down number of units/job to more practical values for some samples

I didn't add more since re-miniAOD in 7412 will come soon anyway.

Thanks! Can you also update Run2015B to use the rereco (see #15 ) instead of prompt?

There's even a newer rereco than the one mentioned in #15, see https://cmsweb.cern.ch/das/request?view=list&limit=50&instance=prod%2Fglobal&input=dataset%3D%2F*%2FRun2015B-*%2FMINIAOD
Do you maybe have a link with details about the re-recos? I cannot find anything on the PPD twikis beside this where they only mention the prompt recos: https://twiki.cern.ch/twiki/bin/view/CMS/PdmV2015Analysis#DATA...

Yeah I saw it but it is not documented anywhere. Documentation for miniaod is here: https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookMiniAOD#Run2015B_17Jul2015_re_miniAOD_Da
As you can see, only 17Jul is mentioned so I don't think we should use the august one.

Ok, thanks for the link.
How come the re-reco covers much fewer runs than what is included in the corresponding Golden JSON? Ie compare
https://cms-service-dqm.web.cern.ch/cms-service-dqm/CAF/certification/Collisions15/13TeV/Cert_246908-255031_13TeV_PromptReco_Collisions15_50ns_JSON_v2.txt
with
https://cmsweb.cern.ch/das/request?instance=prod%2Fglobal&input=run+dataset%3D%2FDoubleEG%2FRun2015B-17Jul2015-v1%2FMINIAOD&idx=0&limit=10
and
https://cmsweb.cern.ch/das/request?instance=prod%2Fglobal&input=run+dataset%3D%2FDisplacedJet%2FRun2015B-PromptReco-v1%2FMINIAOD&idx=0&limit=10

Covers the run range<PHONE_NUMBER>62 for which MET filters were missing in PromptReco.
Ok so it seems like it's supposed to be used with prompt reco. How convenient...

But I guess it does not really matter since we agreed on not using 2015B, so you can leave it like this, sorry for the noise :)

Indeed! So ok to merge?

Yep, thanks :)

Just for completeness, the 5Aug rereco of 2015B is for the validation of 7.5.1.


Make TableDataWriteChannel expose Job when upload completed

This fixes #1392

Coverage increased (+0.02%) to 84.248% when pulling 10afcef7ac7fe5b24938cc549b95f82bc03ee383 on mziccard:bigquery-streaming-job into 57738da1b95ddef21e32f0b2037a1780ad7cc154 on GoogleCloudPlatform:master.

/cc @tswast

Can we tell codacy-bot to ignore unused locals in snippets?

It is doable but configuration is not exactly easy.

@garrettjonesgoogle do you want to have a look?

@lesv PTAL

So the argument for not using @Deprecated and creating a new API is that no one could actually have used the earlier API.  Since that's the case, and presuming everyone agrees, LGTM.


floating point literals don't implicitly convert to float

I should be able to pass 2.0 to a float parameter.

It only happened for -2.0. Fixed now.


Setup Next

Please fix stickler pipeline

solicito revisión QA

emanuel por fabor sube el enlacepara verlo

Why do it again next when you only had to modify it on plain javascript? Isn't it like working double or triple? @e-azocar

Why do it again using next when you only had to modify it on plain javascript? Isn't it like working double or triple? @e-azocar

I decided to use React because has advantages in managing the state and components are easier to use, without template strings. And I decided to use Next.js because It's React with seo improvements


SAA-559 - Wire in prisoner allocated audit event

Codecov Report
Patch coverage: 69.56% and project coverage change: +0.14 :tada:

Comparison is base (5222d4f) 81.20% compared to head (da3d3f1) 81.35%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #254      +/-   ##
============================================
+ Coverage     81.20%   81.35%   +0.14%
- Complexity     1411     1427      +16
============================================
  Files           236      236
  Lines          6067     6083      +16
  Branches        204      208       +4
============================================
+ Hits           4927     4949      +22
+ Misses         1030     1019      -11
- Partials        110      115       +5

Impacted Files
Coverage Δ

.../hmppsactivitiesmanagementapi/entity/Allocation.kt
89.58% <ø> (ø)

...ctivitiesmanagementapi/entity/AuditableListener.kt
48.14% <41.66%> (+14.81%)
:arrow_up:

...anagementapi/model/audit/PrisonerAllocatedEvent.kt
100.00% <100.00%> (ø)

...activitiesmanagementapi/util/TransformFunctions.kt
83.84% <100.00%> (+4.29%)
:arrow_up:

... and 1 file with indirect coverage changes
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 in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Looks good.  Just a few comments to think about.