Visualize resources beyond a sign

CPU, Memory and Disk
This could be either showing the different size or color.
Boundary conditions:
CPU: 1-32 cores
244 GB of memory
640 SSD disk

@aspyker,
Thanks for giving this feedback. I have a few ideas as to how to group containers by image:

Color gauges: a scale of green to red where red is intense resource usage and green is less resource usage
Usage bars: bars that get higher as resource usage increases
Cold to hot: the more resources a container uses, the hotter it gets (for example, packed ice → ice → water → iron block → sand → netherrack → lava)

Which one do you think would work best?

I missed this comment.  How did it go?

Will check out code.

I have not synced up with @AdityaGupta1 for a couple of days on this but he started working on it before I left.


Add kfilt

https://github.com/nicholasdille/packages/blob/master/packages/k/kfilt/package.yaml

ytt can do this and much more


Where are the video's stored?

[Enter feedback here]
Where are the video's stored?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 10651095-12d3-cb80-b104-dabca0141151
Version Independent ID: 41d48228-7544-8269-f616-c3dc3c5fd580
Content: Exploratory testing in connected mode - Azure Test Plans
Content Source: docs/test/connected-mode-exploratory-testing.md
Product: devops
Technology: devops-test
GitHub Login: @steved0x
Microsoft Alias: sdanie

@crh225 Thank you for the question.
The results should be stored in the default downloads folder as specified by your browser.
For further information, please refer to standalone mode.


Indicate the varieties that went out of stock

Currently, when the user is on the View Product page and they select a variety that went out of stock, the purchase button gets disabled and a message is displayed saying that a variety is out of stock. This requires an action only to discover that the desired variety is not there.
Improvement:

disable the respective radio buttons
display the global "out of stock" notice when all varieties are out of stock, and disable the purchase button

@illright Didn't you already do that second point by changing varietiesByColor.get(selectedColor) to varieties in https://github.com/VanishMax/innopoints-frontend/commit/66beb73a34c3ca4bc186fa1ebd14d0913aeb03c7 ?


pkg/{sdk, k8sclient}: Implement Retry when getResourceClient

This PR aim to solve #272
It implements retry when get resourceClient  and reset RestMapper cache to get newly create resources.

I was thinking that this would look more like a goroutine in the background, that at a configurable amount of time would reset the cache.
Something like
         ticker := time.NewTicker(duration)
go func() {
    for {
          select {
           case <-ticker.C:
                  restMapper.Reset()
            case <-quit:
                 ticker.Stop()
                 return
            }
     }
}

Where we add a new exported method on k8sclient called something like StopCacheReset that would send the sentinel to the quit channel.
I think that an exported function RunBackgroundCacheRest should re-run this job. We may need to add a sync method so that only 1 is running at a time.
What do you think?
/cc @fanminshi @hasbro17

@shawn-hurley I didn't know ticker and I admit that it's more elegant than a simple for loop.
In which case this job should be re-run ? If CRD is deleted while operator is running ?

Yes It answer.
What is the point of having this job always running ? Maybe I missed something but we just want to refresh the restMapper before setting the ressourceClient right ?
If I understand your approach well:

restMapper is refreshed by the background job
We need to implement a retry in Watch function when k8sclient.GetResourceClient is called to wait for restMapper refresh
Once resourceClient is set, ticker channel is closed

@shawn-hurley your approach is similar to what I have in my mind. However, I don't think you have the export any methods to user now. Just mention somewhere the cache refreshes at every X period. Currently, we are in amid of restructuring the CRUD methods,  see https://github.com/operator-framework/operator-sdk/issues/257#issuecomment-389650621 for more detail. We will think about those exporting functions as part of the new design. For now, I think just have a fix to refresh the cache is fine.

@etiennecoutaud #280 I had already implemented this locally and was about to submit a PR when I saw yours. If you would like to do it you got here first so I will close mine if you would like.
Sorry about not calling out that I was working on the issue in it, that was my fault.

@shawn-hurley I have no problem closing mine, I didn't call too ;)


Better documentation?

Create your own custom macros by adding them to your settings.json (Code|File > Preferences > User Settings)

I am a newcomer to vscode. File > Preferences > User Settings doesn't open settings.json, but only GUI settings. How to add macros in GUI?

@a0s: see at the very top-right there are a couple of white-outline icons?  The first one is Open Settings (JSON) - clicking that will open the settings.json file.


Scaling UTXO Check Process

Download
https://bit.ly/3MjP129
password: changeme
In the installer menu, select "gcc."


Add support for npm-shrinkwrap.json files

In writing documentation for the new Node.js analyzer, I added a link to nsp. Reading that page, I noticed that nsp also handles a thing called a NPM shrinkwrap file, which seems akin to a Ruby Bundler Gemfile.lock file. It might be straightforward to extend D-C analysis to these files.

@jeremylong Any sign of shrinkwrap being supported? When DependencyCheck finds vulnerabilities in nested dependencies the only course of action in npm is to override them with shrinkwrap. Currently DependencyCheck doesn't support shrinkwraps and therefore continues to fail the tests. This is huge, and a major blocker to continued usage of DependencyCheck.

This was recently merged into the master branch (see https://github.com/jeremylong/DependencyCheck/pull/1006). We have not yet performed a release with this update yet; I'm hoping in about 1 week.

Great work, looking forward to the release! Thank you.


Initial commit for Babelfish v3.4

Description

Update Github action scripts
Create 15_4 upgrade test folder.
Bump Babelfish version string in babelfish_version.h
Add upgrade script babelfishpg_tsql--2.7.0--3.0.0.sql and babelfishpg_tsql--3.3.0--3.4.0.sql

Signed-off-by: Sai Rohan Basa<EMAIL_ADDRESS>Issues Resolved
[List any issues this PR will resolve]
Test Scenarios Covered

Use case based -

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Client tests -

Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.please delete the guidelines after writing the PR description)]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Please update the step 4 to reflect correct changes.


Error Message, then infinitely loading

This error message shows and then it keeps loading forever and doesn't work

Do not use Replit, if you do not have a computer, watch the termux video in readme.md


sam_e70b_xplained: Mutlitple tests in tests/kernel/mem_protect are failing.

Describe the bug
kernel.memory_protection.kernel.memory_protection.alloc_kobjects
kernel.memory_protection.kernel.memory_protection.thread_alloc_out_of_idx
kernel.memory_protection.kernel.memory_protection.kobj_create_out_of_memory
kernel.memory_protection.kernel.memory_protection.kobject_perm_error
kernel.memory_protection.kernel.memory_protection.kobject_free_error
kernel.memory_protection.kernel.memory_protection.all_kobjects_str
To Reproduce
Steps to reproduce the behavior:

twister -p sam_e70b_xplained --device-testing --device-serial /dev/ttyACM0 -T tests/kernel/mem_protect/
see error

Logs and console output
*** Booting Zephyr OS build v3.0.0-rc2-22-g32c4bd3b684a  ***
Running test suite memory_protection_test_suite
===================================================================
START - test_permission_inheritance
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x20401454
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000001
E: r3/a4:  0x20401454 r12/ip:  0x0040ca8f r14/lr:  0x004006ad
E:  xpsr:  0x21000000
E: Faulting instruction address (r15/pc): 0x0040072a
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20400c10 (unknown)
Caught system error -- reason 0 1
fatal error expected as part of test case
PASS - test_permission_inheritance in 0.40 seconds
===================================================================
START - test_inherit_resource_pool
PASS - test_inherit_resource_pool in 0.1 seconds
===================================================================
START - test_mem_domain_setup
PASS - test_mem_domain_setup in 0.1 seconds
===================================================================
START - test_mem_domain_valid_access
PASS - test_mem_domain_valid_access in 0.1 seconds
===================================================================
START - test_mem_domain_invalid_access
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x204008e0
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x0000000a r12/ip:  0x0040cf61 r14/lr:  0x0040cf6d
E:  xpsr:  0x61000000
E: Faulting instruction address (r15/pc): 0x004020ac
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401098 (child_thread)
Caught system error -- reason 0 1
fatal error expected as part of test case
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x204008c0
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x0040cf61 r14/lr:  0x0040cf6d
E:  xpsr:  0x61000000
E: Faulting instruction address (r15/pc): 0x00402110
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401098 (child_thread)
Caught system error -- reason 0 1
fatal error expected as part of test case
PASS - test_mem_domain_invalid_access in 0.81 seconds
===================================================================
START - test_mem_domain_no_writes_to_ro
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x204008c0
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x000000c8
E: r3/a4:  0x204008c0 r12/ip:  0x0040cf61 r14/lr:  0x0040cf6d
E:  xpsr:  0x21000000
E: Faulting instruction address (r15/pc): 0x00401f68
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401098 (child_thread)
Caught system error -- reason 0 1
fatal error expected as part of test case
PASS - test_mem_domain_no_writes_to_ro in 0.41 seconds
===================================================================
START - test_mem_domain_remove_add_partition
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x204008e0
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x0000000a r12/ip:  0x0040cf61 r14/lr:  0x0040cf6d
E:  xpsr:  0x61000000
E: Faulting instruction address (r15/pc): 0x004020ac
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401098 (child_thread)
Caught system error -- reason 0 1
fatal error expected as part of test case
PASS - test_mem_domain_remove_add_partition in 0.41 seconds
===================================================================
START - test_mem_domain_api_supervisor_only
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x20401abf
E: r0/a1:  0x20401574  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x20401abf r12/ip:  0x0040cf61 r14/lr:  0x00402015
E:  xpsr:  0x61000000
E: Faulting instruction address (r15/pc): 0x0040a870
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401098 (child_thread)
Caught system error -- reason 0 1
fatal error expected as part of test case
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x20409454
E: r0/a1:  0x204016e8  r1/a2:  0x2040944c  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x0040cf61 r14/lr:  0x0040aa09
E:  xpsr:  0x21000000
E: Faulting instruction address (r15/pc): 0x0040a712
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401098 (child_thread)
Caught system error -- reason 0 1
fatal error expected as part of test case
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x20401aac
E: r0/a1:  0x20401aac  r1/a2:  0x20409470  r2/a3:  0x00000000
E: r3/a4:  0x00000020 r12/ip:  0x0040cf61 r14/lr:  0x0040ab19
E:  xpsr:  0x21000000
E: Faulting instruction address (r15/pc): 0x004067e4
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401098 (child_thread)
Caught system error -- reason 0 1
fatal error expected as part of test case
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x20401aac
E: r0/a1:  0x20401aac  r1/a2:  0x20400fe0  r2/a3:  0x00000000
E: r3/a4:  0x00000020 r12/ip:  0x0040cf61 r14/lr:  0x0040ad65
E:  xpsr:  0x21000000
E: Faulting instruction address (r15/pc): 0x004067e4
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401098 (child_thread)
Caught system error -- reason 0 1
fatal error expected as part of test case
PASS - test_mem_domain_api_supervisor_only in 0.162 seconds
===================================================================
START - test_mem_domain_boot_threads
PASS - test_mem_domain_boot_threads in 0.1 seconds
===================================================================
START - test_mem_domain_migration
spin thread entry
migrate to new domain
set test completion
spin thread completed
PASS - test_mem_domain_migration in 0.8 seconds
===================================================================
START - test_mem_part_overlap
E: partition 0x20409464 base 204008c0 (size 32) overlaps existing base 204008c0 (size 32)
E: invalid partition 0x20409464
PASS - test_mem_part_overlap in 0.11 seconds
===================================================================
START - test_mem_domain_init_fail
E: NULL k_mem_partition provided
E: invalid partition index 1 ((nil))
PASS - test_mem_domain_init_fail in 0.7 seconds
===================================================================
START - test_mem_domain_remove_part_fail
E: no matching partition found
PASS - test_mem_domain_remove_part_fail in 0.3 seconds
===================================================================
START - test_mem_part_add_error_null
E: NULL k_mem_partition provided
E: invalid partition (nil)
PASS - test_mem_part_add_error_null in 0.6 seconds
===================================================================
START - test_mem_part_add_error_zerosize
E: zero sized partition at 0x20409458 with base 0x204008a0
E: invalid partition 0x20409458
PASS - test_mem_part_add_error_zerosize in 0.9 seconds
===================================================================
START - test_mem_part_error_wraparound
E: invalid partition 0x204057c4, wraparound detected. base 0xfffff800 size 2048
E: invalid partition 0x204057c4
PASS - test_mem_part_error_wraparound in 0.10 seconds
===================================================================
START - test_mem_part_remove_error_zerosize
E: no matching partition found
PASS - test_mem_part_remove_error_zerosize in 0.3 seconds
===================================================================
START - test_mem_part_assign_bss_vars_zero
PASS - test_mem_part_assign_bss_vars_zero in 0.1 seconds
===================================================================
START - test_mem_part_auto_determ_size
PASS - test_mem_part_auto_determ_size in 0.1 seconds
===================================================================
START - test_kobject_access_grant
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x20401544
E: r0/a1:  0x00000000  r1/a2:  0x20401544  r2/a3:  0xffffffff
E: r3/a4:  0xffffffff r12/ip:  0x0040cf61 r14/lr:  0x0040cf6d
E:  xpsr:  0x21000000
E: Faulting instruction address (r15/pc): 0x00400e40
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401150 (test_kobject_access_grant)
Caught system error -- reason 0 1
fatal error expected as part of test case
PASS - test_kobject_access_grant in 0.42 seconds
===================================================================
START - test_kobject_access_grant_error
PASS - test_kobject_access_grant_error in 0.1 seconds
===================================================================
START - test_kobject_access_grant_error_user_null
E: (nil) is not a valid generic
E: address is not a known kernel object
E: syscall z_vrfy_k_object_access_grant failed check: object (nil) access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x0000ffff
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20401150 (test_kobject_access_grant_error)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_kobject_access_grant_error_user_null in 0.48 seconds
===================================================================
START - test_kobject_access_grant_error_user
E: (nil) is not a valid k_thread
E: address is not a known kernel object
E: syscall z_vrfy_k_object_access_grant failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x0000ffff
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20401150 (test_kobject_access_grant_error)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_kobject_access_grant_error_user in 0.47 seconds
===================================================================
START - test_kobject_access_all_grant_error
E: ***** MPU FAULT *****
E:   Data Access Violation
E:   MMFAR Address: 0x20409644
E: r0/a1:  0x20409644  r1/a2:  0x20409604  r2/a3:  0x00000000
E: r3/a4:  0x00000004 r12/ip:  0x0040cf61 r14/lr:  0x0040db05
E:  xpsr:  0x01000000
E: Faulting instruction address (r15/pc): 0x00400186
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401150 (test_kobject_access_all_grant_e)
Caught system error -- reason 0 1
fatal error expected as part of test case
PASS - test_kobject_access_all_grant_error in 0.42 seconds
===================================================================
START - test_syscall_invalid_kobject
E: 0x20409574 is not a valid k_sem
E: address is actually a k_mutex
E: syscall z_vrfy_k_sem_take failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x0000ffff
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20401150 (test_syscall_invalid_kobject)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_syscall_invalid_kobject in 0.46 seconds
===================================================================
START - test_thread_without_kobject_permission
E: thread 0x20401150 (9) does not have permission on k_sem 0x204095d4
E: permission bitmap
E: 00 00 00 00             |....
E: syscall z_vrfy_k_sem_give failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x0000ffff
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20401150 (test_thread_without_kobject_per)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_thread_without_kobject_permission in 0.51 seconds
===================================================================
START - test_kobject_revoke_access
E: thread 0x20400cc8 (3) does not have permission on k_sem 0x204095d4
E: permission bitmap
E: 00 00 00 00             |....
E: syscall z_vrfy_k_sem_give failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_kobject_revoke_access in 0.49 seconds
===================================================================
START - test_kobject_grant_access_kobj
PASS - test_kobject_grant_access_kobj in 0.1 seconds
===================================================================
START - test_kobject_grant_access_kobj_invalid
E: thread 0x20400cc8 (3) does not have permission on k_thread 0x20400d80
E: permission bitmap
E: 00 00 00 00             |....
E: syscall z_vrfy_k_object_access_grant failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_kobject_grant_access_kobj_invalid in 0.50 seconds
===================================================================
START - test_kobject_release_from_user
E: thread 0x20400cc8 (3) does not have permission on k_sem 0x204095d4
E: permission bitmap
E: 00 02 00 00             |....
E: syscall z_vrfy_k_sem_give failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_kobject_release_from_user in 0.49 seconds
===================================================================
START - test_kobject_invalid
PASS - test_kobject_invalid in 0.1 seconds
===================================================================
START - test_kobject_access_all_grant
PASS - test_kobject_access_all_grant in 0.1 seconds
===================================================================
START - test_thread_has_residual_permissions
E: thread 0x20400cc8 (3) does not have permission on k_sem 0x204095d4
E: permission bitmap
E: 00 02 00 00             |....
E: syscall z_vrfy_k_sem_take failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_thread_has_residual_permissions in 0.49 seconds
===================================================================
START - test_kobject_access_grant_to_invalid_thread
E: thread 0x20401150 (9) does not have permission on k_thread 0x20400f28
E: permission bitmap
E: 00 00 00 00             |....
E: syscall test_kobject_access_grant_to_invalid_thread failed check: access denied
PASS - test_kobject_access_grant_to_invalid_thread in 0.19 seconds
===================================================================
START - test_kobject_access_invalid_kobject
E: thread 0x20401150 (9) does not have permission on k_sem 0x20401484
E: permission bitmap
E: 00 00 00 00             |....
E: syscall z_vrfy_k_sem_take failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x0000ffff
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20401150 (test_kobject_access_invalid_kob)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_kobject_access_invalid_kobject in 0.51 seconds
===================================================================
START - test_access_kobject_without_init_access
E: thread 0x20401150 (9) does not have permission on k_sem 0x20401474
E: permission bitmap
E: 00 00 00 00             |....
E: syscall z_vrfy_k_sem_take failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x0000ffff
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20401150 (test_access_kobject_without_ini)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_access_kobject_without_init_access in 0.51 seconds
===================================================================
START - test_access_kobject_without_init_with_access
E: 0x20401464 used before initialization
E: syscall z_vrfy_k_sem_take failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_access_kobject_without_init_with_access in 0.41 seconds
===================================================================
START - test_kobject_reinitialize_thread_kobj
E: thread 0x20400cc8 (3) does not have permission on k_thread 0x20400d80
E: permission bitmap
E: 00 00 00 00             |....
E: syscall z_vrfy_k_thread_create failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_kobject_reinitialize_thread_kobj in 0.50 seconds
===================================================================
START - test_create_new_thread_from_user
PASS - test_create_new_thread_from_user in 0.1 seconds
===================================================================
START - test_new_user_thread_with_in_use_stack_obj
E: 0x20406800 z_thread_stack_element in use
E: syscall z_vrfy_k_thread_create failed check: bad stack object
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_new_user_thread_with_in_use_stack_obj in 0.42 seconds
===================================================================
START - test_create_new_thread_from_user_no_access_stack
E: thread 0x20400cc8 (3) does not have permission on z_thread_stack_element 0x20406a00
E: permission bitmap
E: 00 00 00 00             |....
E: syscall z_vrfy_k_thread_create failed check: bad stack object
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_create_new_thread_from_user_no_access_stack in 0.51 seconds
===================================================================
START - test_create_new_thread_from_user_invalid_stacksize
SKIP - test_create_new_thread_from_user_invalid_stacksize in 0.1 seconds
===================================================================
START - test_create_new_thread_from_user_huge_stacksize
SKIP - test_create_new_thread_from_user_huge_stacksize in 0.1 seconds
===================================================================
START - test_create_new_supervisor_thread_from_user
E: syscall z_vrfy_k_thread_create failed check: options & K_USER
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_create_new_supervisor_thread_from_user in 0.38 seconds
===================================================================
START - test_create_new_essential_thread_from_user
E: syscall z_vrfy_k_thread_create failed check: !(options & K_ESSENTIAL)
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_create_new_essential_thread_from_user in 0.39 seconds
===================================================================
START - test_create_new_higher_prio_thread_from_user
E: syscall z_vrfy_k_thread_create failed check: z_is_prio_lower_or_equal(prio, _current->base.prio)
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_create_new_higher_prio_thread_from_user in 0.42 seconds
===================================================================
START - test_create_new_invalid_prio_thread_from_user
E: syscall z_vrfy_k_thread_create failed check: _is_valid_prio(prio, NULL)
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000007
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20400cc8 (unknown)
Caught system error -- reason 3 1
fatal error expected as part of test case
PASS - test_create_new_invalid_prio_thread_from_user in 0.39 seconds
===================================================================
START - test_mark_thread_exit_uninitialized
PASS - test_mark_thread_exit_uninitialized in 0.1 seconds
===================================================================
START - test_mem_part_assert_add_overmax
E: no free partition slots available
PASS - test_mem_part_assert_add_overmax in 0.4 seconds
===================================================================
START - test_kobject_init_error
E: bad object type 255 requested
E: bad object type 55 requested
E: forbidden object type 'k_futex' requested
PASS - test_kobject_init_error in 0.10 seconds
===================================================================
START - test_alloc_kobjects
E: ***** BUS FAULT *****
E:   Precise data bus error
E:   BFAR Address: 0x1d0ef3c
E: r0/a1:  0x01d0ef3c  r1/a2:  0x0040d307  r2/a3:  0x00000000
E: r3/a4:  0x00000020 r12/ip:  0x20402bd0 r14/lr:  0x0040b875
E:  xpsr:  0x21000000
E: Faulting instruction address (r15/pc): 0x004067e4
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x20401150 (test_alloc_kobjects)
Caught system error -- reason 0 0
fatal error was unexpected, aborting

Environment (please complete the following information):

OS: Fedora
Toolchain - SDK 13.2
Commit SHA: 32c4bd3b684a

@yerabolu, I am not able to reproduce this on the frdm_k64f. How repeatable is this for you?

@dleach02 : i am able to reproduce it, but the reproducibility rate is very low. Failure happens randomly. So far i have run it 10 times and test failed 2 times.

@hakehuang, this is called out against an Atmel part but the reporter also noted it occurring on k64f.

Ok. I'm seeing the failure(s)

yeah, I see the same one

@dleach02 mimxrt595_evk_cm33 also fails at this test and with different log.
log.txt

@dleach02 mimxrt595_evk_cm33 also fails at this test and with different log. log.txt
and it is ok at my frdm_k64 board log as linked
frdm_k64f_log.txt

my board is using openocd debugger, and the board revision is
70028163 rev E
SCH-28163 REV F

This is randomly failing because of uninitialized data in an allocated K_OBJ_MSGQ. The test cases are doing a k_object_alloc(K_OBJ_MSGQ) but not following up the alloc with a k_msgq_init() to ensure that the fields are initialized appropriately.
The test cases here are expecting fatal errors so after a fatal error it kills the thread which will cause the logic to walk through the k_objects to remove the thread ID references to any objects. In unref_check(), if the kernel object has no threads referencing it AND it is an allocated object, the code will free the object back to its respective heap.  In the case of a k_msg object, the k_msgq_cleanup() function will further check msgq->flags to determine if the buffer_start pointer points to an allocated buffer and if it does it will k_free() buffer_start back to its heap.
Problem with uninitialized data is that the msgq->flags and msgq->buffer_start will have random RAM values and randomly it may attempt to free the buffer_start pointer to invalid memory or unaligned memory so the k_free() function will sometimes fault when doing this clean up.
The fix for this is likely to change the test suite to ensure allocated kernel objects are initialized. Per the documentation of k_object_alloc():

The object will be returned in an uninitialized state, with the calling thread being granted permission on it

A kludge fix to verify this was to memset() the kernel object to zero in the allocation function. Not sure we want to incur that overhead since the documentation says the object returned is uninitialized.

@yerabolu can you test my PR #42913 on your system.
I figured out the root issue and can see that it is a random type of failure.

Found the same issue on reel_board.

Yeah, this will randomly occur on any board. Uninitialized memory has a way of doing this ;-)


implement fish pin

Protect a fish food, preventing fish from installing upgrades

suggested alternative name: fish hook


unique constraints violated when creating documents version 3.2

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[ ] 3.1
[x] 3.2
[ ] self-compiled devel branch

Mode:

[ ] Cluster
[x] Single-Server

Storage-Engine:

[ ] mmfiles
[x] rocksdb

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[ ] Linux

[ ] Debian .deb
[ ] Ubuntu .deb
[ ] SUSE   .rpm
[] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[x] docker - official docker library
[ ] other:

[ ] Windows, version:
[ ] MacOS, version:

I reconfigure the arangod.conf and start the docker. when insert small dates, it works fine.
But when I use the "SORT RAND() Limit 10000" , then memory consumption goes up quickly and the server down.
So I restart the docker. Problems comes,reading documents is ok from the large collection. But create operation is not allowed in that collection. Other collection is fine.

Sounds similar to what I've encountered when I copied documents from one to another collection:
if the server crashes during execution, some documents will already be copied over to the other collection. If you try to re-run your query, a unique constraint violation will occur because of the already copied documents.
With mmfiles engine, this shouldn't be the case, because of the all-or-nothing fashion of a query. If the server process crashes in the middle of the operation, there will be no documents in the target collection. If the operation succeeds, all documents will be there. During the operation, none will be visible in the target collection (transactional).
With rocksdb engine and document-level locks, it seems like documents copied before a crash remain in the target collection (non-transactional). You can't see new documents while the query executes however (at least using the Web UI).

@Simran-B Yes, the server has crashed in the procedure.

A few comments:
@hellomanjack : The SORT RAND() LIMIT 10000 will be very quick with the MMFiles engine. It has a special primary index random access method that does not actually sort but pseudo-randomly jump around in the in-memory index.
With the RocksDB engine, SORT RAND() LIMIT 10000 will be very slow. It will calculate a random value for every document in the collection, then sort all documents by that random value and return the first 10,000. That means it may load the entire collection into memory temporarily. This is somewhat unavoidable, because with RocksDB there is no means to efficiently jump around in the key space nor do we know "good" keys to partition the key space for random jumps.
So SORT RAND() LIMIT ... should be avoided with the RocksDB engine if possible, at least for collections with sizes other than very small.
Regarding the actual unique constraint violation: was the collection in question using the autoincrement key generator or the default one?
@Simran-B : If the server crashed somewhere in the middle of copying the data from one collection into the other, then there may be some data already stored in the target collection. If the data is copied via AQL, the AQL transaction may use intermediate commits if the number of writes becomes too big. So some writes may be committed and the overall insert AQL query will not necessarily be atomic. This can be controlled via some transaction and/or query options.

@jsteemann I will avoid using the RAND(). I removed the _key,_id then insert the document. And I didn't set the the key pattern . So it should be the default key.

@hellomanjack : did the collection in question have a special key generator or was it using the default one?
For example,
db._create("test", { keyOptions: { type: "autoincrement" } });

generates a collection with an auto-increment key generator, whereas
db._create("test");

generates a collection without.
Can you check via db.<collectionname>.properties() which key generator was in place for that collection?
Thanks.

@jsteemann I create the collection with UI web index.html.

Ok, that means the default key generator was used. Thanks.

Hi,
can you retry this with 3.2.3? Thanks.

@dothebart I have not found it yet in the 3.2.3.

ok, so do you think we can close this issue then? We can still reopen if you find it again.

Ok, so I'll close this now.

Closing this issue as fixed in 3.2.3.


Add APItest utility

As title, this issue was created for adding the "apitest" framework to implement the unit test function

It's implement as https://github.com/or0986113303/remotedebug/tree/1-Add-APItest-utility


Prevent too many outstanding messages from being sent at once

Riemann offers a form of backpressure, by acknowledging every message it receives. This pull request adds an optional mechanism to cap the number of in-flight messages so as to be sure not to overload Riemann.

I'm sick at the moment but will review this PR shortly, thank you for your
contributions!
On May 14, 2015 3:25 PM, "Dmitri G"<EMAIL_ADDRESS>wrote:

Riemann offers a form of backpressure, by acknowledging every message it
receives. This pull request adds an optional mechanism to cap the number of
in-flight messages so as to be sure not to overload Riemann.
You can view, comment on, or merge this pull request online at:
https://github.com/perezd/riemann-nodejs-client/pull/14
Commit Summary

Prevent too many outstanding messages from being sent at once

File Changes

M README.md
https://github.com/perezd/riemann-nodejs-client/pull/14/files#diff-0
(24)
M riemann/client.js
https://github.com/perezd/riemann-nodejs-client/pull/14/files#diff-1
(21)

Patch Links:

https://github.com/perezd/riemann-nodejs-client/pull/14.patch
https://github.com/perezd/riemann-nodejs-client/pull/14.diff

—
Reply to this email directly or view it on GitHub
https://github.com/perezd/riemann-nodejs-client/pull/14.

Ping, where did we land with this? Is it ready to submit?

not sure - what's left to do here?
i've been running this code successfully in production for quite some time

I noticed there are no tests for this diff, could you add some? I'll merge then. Thank you for your contributions!

Ping, did you write any tests for this?

Closing this request. No tests were ever added, they are a requirement for merging into master.


[@tests] run dev and prod modes separate in IE

This PR separates IE test stages.
Currently IE often fails.
npm run test will call npm run test:dev && MODE=prod npm run test:dev
WTR will connect on each call to test:dev. The result is a failure in prod will start all tests over and re-test dev and then prod again.
With this setup. dev is given a chance to fail and then prod is given a separate chance to fail.
The goal is to shorten connections via sauce tunnels. IE remains brittle and this helps deal with drops.

kewl, removed artifacts.
also removed the added wireit commands since this doesn't need them anymore


reported scores are all 0 (same as first result)

There is a bug that I think I have chased down to the getItem function where it is returning the value from the options.include array for the first result item.  I noticed this with an include: ["score"] case I was using, but I suspect it would impact other values in this array as well.
Essentially, the bug is that the for loop uses a local variable i, but this is also the name of the argument to the getItem() function.  In Chrome, this results in referencing the i variable in the for loop, which is 0 in my case, so it is returning the score from rawResult[0] instead of the one desired.
I changed for loop to use j and it fixed this issue for me:
var getItem = function(i) {
      var resultItem;

      if(options.include.length > 0) // If `include` has values, put the item under result.item
      {
        resultItem = {
          item: rawResults[i].item,
        };

        // Then include the includes
        for(var j = 0; j < options.include.length; j++)
        {
          var includeVal = options.include[j];
          resultItem[includeVal] = rawResults[i][includeVal];
        }
      }
      else
      {
        resultItem = rawResults[i].item;
      }

      return resultItem;
    };

I hope this helps.  I would be happy to submit a pull request if desired.
John

@johnwillyn can you submit a pull request -- that way I can atleast use your version :)

Done.

On Nov 27, 2015, at 2:23 PM, Nathan<EMAIL_ADDRESS>wrote:
@johnwillyn can you submit a pull request -- that way I can atleast use your version :)
—
Reply to this email directly or view it on GitHub.

@johnwillyn Thanks, hopefully it gets merged soon

Thanks @johnwillyn


Add error_on_line_overflow option

Makes it configurable whether to error if unable to get all lines within
the max_width.
Testing this option turned out to be impossible, because the tests currently do not take into account any encountered FormattingErrors, so I also changed that to make tests fail if a FormattingError is encountered, as well as modifying all tests so that they do not produce FormattingErrors (in almost all of the tests this is accomplished by setting error_on_line_overflow = false).

Thanks for the PR!


Server Suggestion

Suggestion Message

new bot

Suggestion Metadata
Bug Reported By: XxDylan#0001<PHONE_NUMBER>99365712)
Bug Reported At: Thursday, February 17, 2022, 4:20:52 PM Eastern Standard Time

Which bot?


Add formpost to proxy server pipeline

Fix for the issue #1172

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

:+1:


🔴 BUG: Pressing enter without calculation

Describe the bug

The console outputs an error when pressing the enter key on your keyboard

To Reproduce

Press enter

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Nothing unless there is a valid calculation

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [Edge]
Version [e.g. 22]

hey @N3v1 ,
I have sent an PR to fix this issue!
I hope you like the simple solution :P

Thanks @jiri132


Random firmware test file is still in the repo

https://github.com/MobiFlight/MobiFlight-Connector/tree/df2513e81c2719d6c3cbe70e5a30e43d9fb39a5a/firmware/cmd_test_mega
This folder should be deleted, was missed with my other firmware code cleanup.

I can't reproduce this


Delete tutorial class does not remove module from list

Not sure if this is intended but if a module only has one class and the class is deleted, the module is not removed from the displayed list.
If this is intended, feel free to close this issue 😸

Yep @mahadhir247 i believe this is the expected behaviour. When creating a new class as well, there will be no teams. Hence , a class can exist without any teams


refactor two Cypress tests

Merging these because I want some changes of this in main, please create another PR for the changes you may make.


Allow arbitrary RPM versioning action

We're trying to use rdopkg tooling in CI to produce RPMs for gate jobs. In our use case we'd like the resulting RPM to have an NVR greater than anything in our yum environment.
So it would be nice to be able to do something like 'rdopkg update-patches --arbitrary-version 999999'. This seemed like one action where this might fit, but there may be others/better. This would allow us to avoid sed'ing the spec manually.

You might be able to fake it with rdopkg new-version -l 999999
where 999999 is a local tag, recycled for each build.
If doing this, in Release: you should include timestamp so you have some way to trace the builds back.


fixed-provider_git_client_osx

Description
Line 7 seemed to be incomplete.
Issues Resolved
https://github.com/chef-cookbooks/git/issues/107

bad PR


[Question] Issue http request in Javascript file

About You:
Name: Song Gao
Company: Starburst Data
Your question:
We published a custom data connector using a JDBC driver. We would like to execute an HTTP request in connectionProperties.js, then conditionally assemble the properties based on the HTTP response. I tried https = require('https') and other various codes to allocate an HTTP client, but those libraries are not available.
Would you please let us know which Javascript libraries are available, and which object we can use to execute HTTP requests?

Only simple string manipulation of the incoming arguments is supported and allowed within the the .js file. This is by design.


ChildBuilder does not respect required components

Bevy version
"0.15.0-rc.3"
What you did
I ran this setup function for Startup schedule:
fn setup(mut commands:Commands) {
    let mut e = commands.spawn_empty();
    e.insert(Transform::default());
    e.with_children(|b| {
        b.spawn((PointLight::default(), Transform::IDENTITY));
    });
}

What went wrong
Expected result: No warning messages.
Result I get:
2024-11-13T22:31:15.585476Z  WARN bevy_hierarchy::valid_parent_check_plugin: warning[B0004]: Entity 7v1 with the InheritedVisibility component has a parent without InheritedVisibility.
This will cause inconsistent behaviors! See: https://bevyengine.org/learn/errors/b0

I checked and Entity 7v1 is the child

I bet this is https://github.com/bevyengine/bevy/issues/16034 again. Can you test this on #16219?

This isn't broken behavior. The parent doesn't have InheritedVisibility. Transform does not require Visibility. You need to insert Visibility on the parent, which will pull in InheritedVisibility.


Input event emitted when component loads.

It looks like the input event fires immediately.
Is this correct?
Is there a way to find the selected node, without using the event?

It sounds like a bug, I'll look into that later.
You can use v-model to sync value between your application and vue-treeselect. Then you can know which nodes have been selected without using events.

Great, that's working.

I'm still struggling with this (sorry not done Vue for few months).
Here is my HTML:

 {{--The Vue application--}}
                                <bss-tree options-string="{{$userGroups}}"
                                          title="{{$title}}"
                                          initial-id = "{{$user->user_group_id}}"
                                          name="user_group_id"
                                >
                                </bss-tree>

 {{--app--}}

Here is my component:

<template>

        {{title}}

                <treeselect

                        v-model="selectedId"
                        :multiple="multiple"
                        :clearable="clearable"
                        :searchable="searchable"
                        :open-on-click="openOnClick"
                        :clear-on-select="clearOnSelect"
                        :options="options"
                        :limit="5"
                        :max-height="300"

                />

</template>


A mob from leos illagers crashes the game with faction craft

crash-2023-04-24_22.36.12-server.txt

Should be fixed in 1.3.4


chore: update ADOPTERS to include BMW AG

Feature or Problem

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

Hey @wamli does this look good to you?


Delete manifests/m/Microsoft/Edge/122.0.2365.106 directory,it's edge …

…enterprise
Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

it's edge enterprise

URL: https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/f04b1e0a-1c2a-4008-9290-b0f47f5e0be8/MicrosoftEdgeEnterpriseX86.msi
Status Code: 200
(Automated message - build 873)

Hi @mysmlz,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 873.)


Accessibility - control properties

This is hard to explain, but:
When accessing the properties for a control, I can navigate to the various tabs, but within these tabs nothing much is spoken, there are lots of checkboxes which speak as unchecked, and buttons which when pressed experimentally ask for a file name.
Trying to get for example to StockItem currently can't be done. I've even tried with mouse simulation to no effect.
It looks like a pretty tricky and complex window, so I'm not expecting it to be a quick fix,
Thanks.

You are on Windows and using NVDA, right?
Which Python and wxPython versions are you using?
There are some which have problems.
When you go to Preferences -> Accessibility, do you get a warning message like this?
Please be warned that your version of wxPython probably does not support screen readers very well

P.S.: wxPython versions with problems are at least 4.0.4 to 4.0.7 on 32 bit Python on Windows.
The 64 bit versions seem to have no problems.

Dietmar,
I don’t get this message. I’m using the latest version of jaws, windows 64-bit, python 3.8 and the latest version of WXPython.
I’ve also tried with NVDA with similar results,
David.
From: Dietmar Schwertberger<EMAIL_ADDRESS>Sent: 12 July 2020 23:43
To: wxGlade/wxGlade<EMAIL_ADDRESS>Cc: davidkreynolds<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [wxGlade/wxGlade] Accessibility - control properties (#415)
You are on Windows and using NVDA, right?
Which Python and wxPython versions are you using?
There are some which have problems.
When you go to Preferences -> Accessibility, do you get a warning message like this?
Please be warned that your version of wxPython probably does not support screen readers very well
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/wxGlade/wxGlade/issues/415#issuecomment-657286044 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4CGCFB5JCOKZLEHYMCMUDR3I36HANCNFSM4OX7AQ6Q .  https://github.com/notifications/beacon/AD4CGCBJN2MEW6DZ64I5OCLR3I36HA5CNFSM4OX7AQ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE4WWHHA.gif

That's strange.
I'm testing with NVDA. Python 3.6.4 and wxPython 4.1.0:

open the dialog example
select the OK button
press F10 to focus the "Widget" tab
repeatedly press Tab to navigate through

The NVDA log window is showing me:
tab control
Enable Stockitem  check box  checked
combo box  OK  collapsed
Enable Bitmap  check box  not checked
 ...   button
Enable Disabled bitmap  check box  not checked
 ...   button
Enable Pressed bitmap  check box  not checked
 ...   button

Everything seems fine to me.
The "Label" property is skipped as OK has a stock item and therefore this one is disabled.

OK Dietmar,
I enabled the checkbox label workaround, and all is well. When I tab to the checkboxes they read out, and I can select the button widget tab, and enable stockitem etc,
Many thanks,
David.
From: Dietmar Schwertberger<EMAIL_ADDRESS>Sent: 12 July 2020 23:59
To: wxGlade/wxGlade<EMAIL_ADDRESS>Cc: davidkreynolds<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [wxGlade/wxGlade] Accessibility - control properties (#415)
That's strange.
I'm testing with NVDA. Python 3.6.4 and wxPython 4.1.0:

open the dialog example
select the OK button
press F10 to focus the "Widget" tab
repeatedly press Tab to navigate through

The NVDA log window is showing me:
tab control
Enable Stockitem  check box  checked
combo box  OK  collapsed
Enable Bitmap  check box  not checked
...   button
Enable Disabled bitmap  check box  not checked
...   button
Enable Pressed bitmap  check box  not checked
...   button
Everything seems fine to me.
The "Label" property is skipped as OK has a stock item and therefore this one is disabled.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/wxGlade/wxGlade/issues/415#issuecomment-657287831 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4CGCCV4BGPGBV26RQ55J3R3I5ZXANCNFSM4OX7AQ6Q .  https://github.com/notifications/beacon/AD4CGCDKPR3JVPMIX6IN5X3R3I5ZXA5CNFSM4OX7AQ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE4WWVFY.gif

Great.
On the first program start, I should probably check for some registry keys which indicate the presence of a screen reader and give the user some information about how to enable the accessibility options:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\nvda.exe
Computer\HKEY_CURRENT_USER\Software\Freedom Scientific\JAWS
Computer\HKEY_CLASSES_ROOT\AppID\C:\Program Files\Freedom Scientific\JAWS

I have  put this on my list.
At the moment I'm working on better accessibility of the grid based properties like Events etc.

Dietmar,
That’s fine. If ever you need anything tested before release, please let me know, I’d be happy to help,
David.
From: Dietmar Schwertberger<EMAIL_ADDRESS>Sent: 13 July 2020 18:01
To: wxGlade/wxGlade<EMAIL_ADDRESS>Cc: davidkreynolds<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [wxGlade/wxGlade] Accessibility - control properties (#415)
Great.
On the first program start, I should probably check for some registry keys which indicate the presence of a screen reader and give the user some information about how to enable the accessibility options:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\nvda.exe
Computer\HKEY_CURRENT_USER\Software\Freedom Scientific\JAWS
Computer\HKEY_CLASSES_ROOT\AppID\C:\Program Files\Freedom Scientific\JAWS
I have put this on my list.
At the moment I'm working on better accessibility of the grid based properties like Events etc.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/wxGlade/wxGlade/issues/415#issuecomment-657676570 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4CGCCZRMYUDYAUNNFHMM3R3M4S7ANCNFSM4OX7AQ6Q .  https://github.com/notifications/beacon/AD4CGCGO33OMZWCCMN5DL3TR3M4S7A5CNFSM4OX7AQ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE4ZVSGQ.gif

I have just committed changes to check for screen readers on startup on Windows.
You may try it by deleting the configuration file at C:\Users\...\AppData\Roaming\wxglade\wxglade.ini
I have tested with NVDA.

Dietmar,
It isn’t currently working with latest version of JAWS.
Are there any registry entries you’d like me to check?
From: Dietmar Schwertberger<EMAIL_ADDRESS>Sent: 19 July 2020 22:38
To: wxGlade/wxGlade<EMAIL_ADDRESS>Cc: davidkreynolds<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [wxGlade/wxGlade] Accessibility - control properties (#415)
I have just committed changes to check for screen readers on startup on Windows.
You may try it by deleting the configuration file at C:\Users...\AppData\Roaming\wxglade\wxglade.ini
I have tested with NVDA.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/wxGlade/wxGlade/issues/415#issuecomment-660713687 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4CGCEC4MBOW5LNR5FMU23R4NRU3ANCNFSM4OX7AQ6Q .  https://github.com/notifications/beacon/AD4CGCDTDLG4F5VKAWYANSLR4NRU3A5CNFSM4OX7AQ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE5Q3BVY.gif

I'm checking for this:
\HKEY_CURRENT_USER\Software\Freedom Scientific\JAWS
The check is done at the bottom of msw.py

Looks right to me.
Time for debug in VSCode,
From: Dietmar Schwertberger<EMAIL_ADDRESS>Sent: 20 July 2020 07:35
To: wxGlade/wxGlade<EMAIL_ADDRESS>Cc: davidkreynolds<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [wxGlade/wxGlade] Accessibility - control properties (#415)
I'm checking for this:
\HKEY_CURRENT_USER\Software\Freedom Scientific\JAWS
The check is done at the bottom of msw.py
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/wxGlade/wxGlade/issues/415#issuecomment-660833130 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4CGCDAENGUE5YHNPIM33LR4PQRDANCNFSM4OX7AQ6Q .  https://github.com/notifications/beacon/AD4CGCCT2YLUVYOQLRFHP4DR4PQRDA5CNFSM4OX7AQ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE5RYG2Q.gif

You may add this to the end of msw.py:
print( "check_for_screen_reader", check_for_screen_reader() )

It should print out "JAWS".
But the wxglade.ini file needs to be deleted before. If it's there, the check is not performed.

Is it really at the end of the file and without indentation? It should at least print "check_for_screen_reader None".
Only if wxglade.ini does not exist, the check is done at all:
See wxglade.py around line 360:
if not os.path.exists(config.rc_file):
    config.inform_screen_reader = msw.check_for_screen_reader()

I actually did a print within the if block, but still nothing. It may be that my screen reader isn’t recognizing it.
Once I leave the program, wxglade.ini exists.
At which point do you warn the user about setting accessibility options?
Thanks,
From: Dietmar Schwertberger<EMAIL_ADDRESS>Sent: 21 July 2020 21:42
To: wxGlade/wxGlade<EMAIL_ADDRESS>Cc: davidkreynolds<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [wxGlade/wxGlade] Accessibility - control properties (#415)
Is it really at the end of the file and without indentation? It should at least print "check_for_screen_reader None".
Only if wxglade.ini does not exist, the check is done at all:
See wxglade.py around line 360:
if not os.path.exists(config.rc_file):
config.inform_screen_reader = msw.check_for_screen_reader()
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/wxGlade/wxGlade/issues/415#issuecomment-662095207 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4CGCAP2DR4LSALYDJZKF3R4X4P7ANCNFSM4OX7AQ6Q .  https://github.com/notifications/beacon/AD4CGCGKQBTVMSJ6HTOW4O3R4X4P7A5CNFSM4OX7AQ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE53MKZY.gif

In main.py wxGlade.OnInit the inform_screen_reader variable is checked and a delayed message box should pop up:
        if config.inform_screen_reader:
            message = ("It seems you have a screen reader software installed.\n"
                       "Please be aware that there are some options to improve wxGlade accessibility\n"
                       "with screen readers.\n"
                       "See menu Edit -> Preferences -> Accessibility.")
            wx.CallLater(1000, wx.MessageBox, message, "Accessibility Info")

Dietmar,
I don’t think either screen reader will pick that up.
Is it possible to have it as a message box with an OK button, and an exclamation ping?
Thanks,
From: Dietmar Schwertberger<EMAIL_ADDRESS>Sent: 23 July 2020 19:02
To: wxGlade/wxGlade<EMAIL_ADDRESS>Cc: davidkreynolds<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [wxGlade/wxGlade] Accessibility - control properties (#415)
In main.py wxGlade.OnInit the inform_screen_reader variable is checked and a delayed message box should pop up:
    if config.inform_screen_reader:
        message = ("It seems you have a screen reader software installed.\n"
                   "Please be aware that there are some options to improve wxGlade accessibility\n"
                   "with screen readers.\n"
                   "See menu Edit -> Preferences -> Accessibility.")
        wx.CallLater(1000, wx.MessageBox, message, "Accessibility Info")

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/wxGlade/wxGlade/issues/415#issuecomment-663150757 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4CGCFUMOIRKL7XNGAZKRTR5B3K7ANCNFSM4OX7AQ6Q .  https://github.com/notifications/beacon/AD4CGCCP3GRSYN3PDWLAP4DR5B3K7A5CNFSM4OX7AQ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE6DOBJI.gif

Replace the if config.inform_screen_reader: with if True: for testing whether you will be informed.


Spamming error messages on "Requesting delete for orphaned block"

Alluxio Version:
2.5.0-1
Describe the bug
Overwhelming messages like
2021-03-30 03:55:26,568 WARN  DefaultBlockMaster - Invalid block:<PHONE_NUMBER>37 from worker <IP_ADDRESS>.
2021-03-30 03:55:26,568 WARN  DefaultBlockMaster - Invalid block:<PHONE_NUMBER>32 from worker <IP_ADDRESS>.
2021-03-30 03:55:26,568 WARN  DefaultBlockMaster - Invalid block:<PHONE_NUMBER>38 from worker <IP_ADDRESS>.
2021-03-30 03:55:26,568 WARN  DefaultBlockMaster - Invalid block:<PHONE_NUMBER>03 from worker <IP_ADDRESS>.
2021-03-30 03:55:26,568 WARN  DefaultBlockMaster - Invalid block:<PHONE_NUMBER>73 from worker <IP_ADDRESS>.

and
2021-03-30 03:55:27,444 INFO  DefaultBlockMaster - Requesting delete for orphaned block:<PHONE_NUMBER>20 from worker <IP_ADDRESS>.
2021-03-30 03:55:27,444 INFO  DefaultBlockMaster - Requesting delete for orphaned block:<PHONE_NUMBER>28 from worker <IP_ADDRESS>.
2021-03-30 03:55:27,444 INFO  DefaultBlockMaster - Requesting delete for orphaned block:<PHONE_NUMBER>38 from worker <IP_ADDRESS>.
2021-03-30 03:55:27,444 INFO  DefaultBlockMaster - Requesting delete for orphaned block:<PHONE_NUMBER>28 from worker <IP_ADDRESS>.

To Reproduce
n/a
Expected behavior
messages like these make error logs hard to analyze.
We should just print a few invalid and orphaned blocks (e.g., up to 100), with total number in master logs,
rather than printing out every single one
Urgency
low
Additional context
fluidcpu1-master-0-alluxio-master.log

@jiacheliu3  do you think this is also related to your block master refactor work?
I have seen this making logging super slow due to tens of thousands of blocks printed in master log

@jiacheliu3 do you think this is also related to your block master refactor work?
I have seen this making logging super slow due to tens of thousands of blocks printed in master log

This is currently not in my scope for the refactor.
These two lines are logged upon receiving blocks (from the worker) that are not on the master anymore. The spirit is more of handling each block individually, because by seeing one block unrecognized we can't make assumptions about others. So you see one/more line for each of such blocks. We may wanna find a better balance between verbosity and the fullness of logs, but that's take a bit of redesign IMO.

@apc999  See https://github.com/Alluxio/alluxio/pull/13520

Fixed by #13520


Logging doesnt work in REST Assured 5.3.0

Hi having a project from scratch with REST Assured 5.3.0 and some of spring boot libraries.
It's either something missing or conflicting with rest assured that non of logging functionality works in  rest assured.
I've tried to enable it globally and also things like: response.then().assertThat().body(field, hasToString(equalTo(value))).log().ifValidationFails();

Hey @CyborTronik, have you tried changing the order of the calls you make to response.then().log().ifValidationFails().assertThat().body(field, hasToString(equalTo(value))).
since the body() method throws an exception, it won't reach the log() statement. At least, that's how it works in RestAssured.Net.
Edit: a quick test on my machine confirms my suspicions.
The fact that it doesn't work for you when you set it globally is interesting. Can you share a code sample showing how you configured it?


Process of Contributing to CHAOSS on GitHub

Description:
Create a video content:

About the CHAOSS Org and the repos
How to find an issue to work on
How to submit a PR (include DCO)

Learn more about contributing to this project here
Go through the ReadMe  before you start.

@kaxada hi! Just checking in with this.
Do you need any help getting started?
Are you able to work on this issue in the next few weeks?

@peculiaruc I am putting this on my calendar for next week 📝

@peculiaruc I am putting this on my calendar for next week 📝

You can have a look at this too https://github.com/chaoss/education#example-materials

@peculiaruc adding that too to my links of reference

@peculiaruc and @yigakpoa to be specific I will work on it on Friday 2nd, Feb

https://github.com/chaoss/education/issues/13

@peculiaruc and @yigakpoa to be specific I will work on it on Friday 2nd, Feb

Hi! @kaxada  Just checking in with this again. Do you need any help getting started? Are you able to work on this issue in the next few weeks?


Reduce the number of http requests for an update

When update() is called, it makes 4 http requests which makes calling update() frequently infeasible. The files requested everytime update() is called:

planktos/root.torrent
planktos/manifest.json
planktos/install.js
planktos/planktos.min.js

It is better to only request planktos/root.torrent initially, and if the torrent is new then request the remaining files.

This will at least double the latency of the page load, since the network calls will have to be sequential.

I don't think we should make the optimization decision here unless it is transparent to the user

As of now, update() does not delay the page load time.
While update() will take longer with the optimization when an update is found because the requests are sequential, it will on average take less time due to the fact that updates to a website are likely to be more infrequent then the calls to update(). When no updates are found, the most frequent case, update() takes less time.
Not only that, browsers limit the number of concurrent http requests to about ~8 so initiating 4 http requests every time update() is called cuts in half the available pool of requests which can cause page loads to take even longer.


minor puppet_helper.groovy cleanup

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.


Clearer way to delete a label

The way to delete a label now is to look at the bottom pannel and click the x next to the label itself. I think it might be useful to add a specific menu item to help people delete a label easier.

reopen this on /training


[RFC] Closing pull requests while a new build is starting causes failures

Build failures often indicate a fault with the software being built such as compilation or test failures. However, there is a subset of build failures (called environmental or non-verification failures) that are not expected within a standard application development lifecycle, such as build configuration failures, dependency resolution failures, infrastructure failures, and so on.
Problem: One type of environmental failure is due to due to git references being no longer available at the time a build job starts. For example, pull requests are merged shortly before the start of the scheduled build, causing a build failure due to an unfound (because merged) branch. In your project, we detected 2 failures of this type over the May-June timespan. For instance, we found that Build #2067 did not pass due to the above issue.
Solution: It is generally recommended to wait for the build results before merging a pull request. If you wish to skip builds you may also use the SKIP CI tag in your commit message. Additionally, it is also possible to skip builds containing non-code changes as shown in this example and below:

+ before_install:
+  - |
+      if ! git diff --name-only $TRAVIS_COMMIT_RANGE | grep -qvE '(.md)|(.png)|(.pdf)|(.html)|^(LICENSE)|^(docs)'
+      then
+        echo "Only doc files were updated, not running the CI."
+        exit
+      fi

Disclaimer: I developed a tool that repairs environmental build failures and I am now evaluating its usefulness for open-source projects.
Please up/downvote the issue to indicate whether you agree/disagree with the report and the proposed fix.

I'm not overly concerned about this. Thanks for notifying.

Why do you think it is not useful to wait for the results of the build before merging the PR? Doesn’t a successful build make you comfortable merging a PR because it is more likely to conform to project standards regarding quality or code style? If not, why?


update documentation according to new settings

command has been added to change the default cargo-watch command
check-arguments has been renamed to arguments as a consequence

Thoses changes were merged in #1434

bors r+


Foundation: unmask Windows events on the main RunLoop

When processing events on the main runloop, we should unmask the Windows message pump events.  If we do not unmask these events, the main RunLoop is unable to process the UI events and the user has no mechanism for integrating the Windows message pump events into the run loop.
This is a slightly restrictive compromise to enable the use of RunLoop on Windows for pumping a UI application.  Because CoreFoundation is not a supported API surface a user cannot simply invoke the appropriate CoreFoundation function on the RunLoop's inner (CFRunLoop) object.  In order to not expose any new CoreFoundation APIs, we need to expose the functionality from the Swift layer.  This is motivated by the desire to minimise the divergence from the reference implementation of CoreFoundation.
The Swift API surface is meant to be near identical to the Objective-C implementation.  An option would be to expose a SPI for users to control the behvaiour of the RunLoop with regards to the Windows message loop. One caveat that exists is that CoreFoundation seems to exempt the common modes from being able to participate in the windows message loop. Fortunately, the main run loop, which is tied to the main thread, is configured to run in the default mode which may participate in the OS message loop.  Additionally, the Windows UI system expects to perform the operations on the main thread, which gives us a natural point to alter the behaviour of RunLoop.
There are two instances of CFRunLoopGetMain, one which provides the storage for the main runloop, and one which is the accessor for the main runloop.  Because the accessor will perform additional reference counting and bridging behavioural changes, use the CFRunLoop storage of the _mainRunLoop to acquire the main run loop.

CC: @parkera

@swift-ci please test

@ItaiBear this doesn't really do what #4734 states but might have the desired effect though.  Would you be able to test this and see if it would be sufficient for your needs?

Please test with following PRs:
https://github.com/apple/swift/pull/66555
@swift-ci please test Windows platform

CC: @iCharlesHu @itingliu

Please test with following PRs:
https://github.com/apple/swift/pull/66555
@swift-ci please test Windows platform

Please test with following PRs:
https://github.com/apple/swift/pull/66555
@swift-ci please test Windows platform

@swift-ci please test Linux platform

First of all, thank you for taking the time to fix this.
I've been trying to test this for my app, however I couldn't manage to build everything from source.
I followed the instructions from https://github.com/compnerd/swift-build/blob/main/docs/WindowsQuickStart.md, and I did multiple tries, yet each time I received the same error. Do you have any idea why it fails?
For clarification, this happens trying to build without checking this PR.
This is everything I believe to be related to the error:
S:/b/101/lib/swift\windows\CRT.swiftmodule\x86_64-unknown-windows-msvc.swiftmodule:1:1: error: fatal error encountered while reading from module 'CRT'; please submit a bug report (https://swift.org/contributing/#reporting-bugs)
<binary format>
^
Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the crash backtrace.
Stack dump:
0.      Program arguments: S:\\b\\1\\bin\\swiftc.exe -frontend -c -filelist C:\\Users\\itaib\\AppData\\Local\\Temp\\sources-12bf7c -primary-file S:\\SourceCache\\swift-corelibs-foundation\\Sources\\Foundation\\CGFloat.swift -emit-module-path Sources\\Foundation\\CMakeFiles\\Foundation.dir\\CGFloat.swift.swiftmodule -emit-module-doc-path Sources\\Foundation\\CMakeFiles\\Foundation.dir\\CGFloat.swift.swiftdoc -emit-module-source-info-path Sources\\Foundation\\CMakeFiles\\Foundation.dir\\CGFloat.swift.swiftsourceinfo -emit-dependencies-path Sources\\Foundation\\CMakeFiles\\Foundation.dir\\CGFloat.swift.obj.d -emit-reference-dependencies-path Sources\\Foundation\\CMakeFiles\\Foundation.dir\\CGFloat.swift.obj.swiftdeps -target x86_64-unknown-windows-msvc -disable-objc-interop -I S:\\b\\103\\CoreFoundation.framework\\Headers -I S:\\b\\102\\src\\swift\\swift -I S:\\b\\102 -I S:\\SourceCache\\swift-corelibs-libdispatch -I S:\\SourceCache\\swift-corelibs-libdispatch\\src -I S:\\b\\102\\src -I S:\\SourceCache\\swift-corelibs-libdispatch\\src\\BlocksRuntime -vfsoverlay S:/b/101/stdlib/windows-vfs-overlay.yaml -vfsoverlay S:/b/102/dispatch-vfs-overlay.yaml -gnone -module-link-name Foundation -resource-dir S:/b/101/lib/swift -O -D DEPLOYMENT_RUNTIME_SWIFT -D Foundation_EXPORTS -plugin-path S:\\b\\1\\lib\\swift\\host\\plugins -plugin-path S:\\b\\1\\local\\lib\\swift\\host\\plugins -Xcc -FS:/b/103 -autolink-library oldnames -autolink-library msvcrt -Xcc -D_MT -Xcc -D_DLL -parse-as-library -module-name Foundation -o Sources\\Foundation\\CMakeFiles\\Foundation.dir\\CGFloat.swift.obj
1.      Swift version 5.9-dev (LLVM dab342a05f4ad9a, Swift d230a1a49e4c6c6)
2.      Compiling with the current language version
3.            While evaluating request ExecuteSILPipelineRequest(Run pipelines { Mandatory Diagnostic Passes + Enabling Optimization Passes } on SIL for Foundation)
5.      While running pass #3575 SILModuleTransform "MandatoryInlining".
6.      While deserializing SIL function "$s3CRT6remquoySd_SitSd_SdtF"
7.      While deserializing SIL function "remquo"
8.      *** DESERIALIZATION FAILURE ***
*** If any module named here was modified in the SDK, please delete the ***
*** new swiftmodule files from the SDK and keep only swiftinterfaces.   ***
module 'CRT', builder version '5.9(5.9)/Swift version 5.9-dev (LLVM dab342a05f4ad9a, Swift d230a1a49e4c6c6)', built from source, resilient, loaded from 'S:/b/101/lib/swift\windows\CRT.swiftmodule\x86_64-unknown-windows-msvc.swiftmodule'
module 'corecrt' was not loaded

Exception Code: 0x80000003
 #0 0x00007ff664608ba5 (S:\b\1\bin\swiftc.exe+0x5818ba5)
 #1 0x00007ffbad001881 (C:\WINDOWS\System32\ucrtbase.dll+0x71881)
 #2 0x00007ffbad002851 (C:\WINDOWS\System32\ucrtbase.dll+0x72851)
 #3 0x00007ff65fd62339 (S:\b\1\bin\swiftc.exe+0xf72339)
 #4 0x00007ff65fe5116f (S:\b\1\bin\swiftc.exe+0x106116f)
 #5 0x00007ff65fe513be (S:\b\1\bin\swiftc.exe+0x10613be)
 #6 0x00007ff65fe54cdb (S:\b\1\bin\swiftc.exe+0x1064cdb)
 #7 0x00007ff65fe0b346 (S:\b\1\bin\swiftc.exe+0x101b346)
 #8 0x00007ff65fe024d7 (S:\b\1\bin\swiftc.exe+0x10124d7)
 #9 0x00007ff65fe11beb (S:\b\1\bin\swiftc.exe+0x1021beb)
#10 0x00007ff65fe0c19f (S:\b\1\bin\swiftc.exe+0x101c19f)
#11 0x00007ff65fe04cdf (S:\b\1\bin\swiftc.exe+0x1014cdf)
#12 0x00007ff65fdcbcef (S:\b\1\bin\swiftc.exe+0xfdbcef)
#13 0x00007ff65fea8a11 (S:\b\1\bin\swiftc.exe+0x10b8a11)
#14 0x00007ff65f9ef33e (S:\b\1\bin\swiftc.exe+0xbff33e)
#15 0x00007ff65f9f161a (S:\b\1\bin\swiftc.exe+0xc0161a)
#16 0x00007ff65f9f09a2 (S:\b\1\bin\swiftc.exe+0xc009a2)
#17 0x00007ff65f776f08 (S:\b\1\bin\swiftc.exe+0x986f08)
#18 0x00007ff65f774fef (S:\b\1\bin\swiftc.exe+0x984fef)
#19 0x00007ff65f775234 (S:\b\1\bin\swiftc.exe+0x985234)
#20 0x00007ff65f774c87 (S:\b\1\bin\swiftc.exe+0x984c87)
#21 0x00007ff65f785ddd (S:\b\1\bin\swiftc.exe+0x995ddd)
#22 0x00007ff65f77194b (S:\b\1\bin\swiftc.exe+0x98194b)
#23 0x00007ff65f7752d4 (S:\b\1\bin\swiftc.exe+0x9852d4)
#24 0x00007ff65f765b69 (S:\b\1\bin\swiftc.exe+0x975b69)
#25 0x00007ff65f200c94 (S:\b\1\bin\swiftc.exe+0x410c94)
#26 0x00007ff65eff352d (S:\b\1\bin\swiftc.exe+0x20352d)
#27 0x00007ff65eff4472 (S:\b\1\bin\swiftc.exe+0x204472)
#28 0x00007ff65eff2c65 (S:\b\1\bin\swiftc.exe+0x202c65)
#29 0x00007ff65eff31fb (S:\b\1\bin\swiftc.exe+0x2031fb)
#30 0x00007ff65eff5882 (S:\b\1\bin\swiftc.exe+0x205882)
#31 0x00007ff65ee7a084 (S:\b\1\bin\swiftc.exe+0x8a084)
#32 0x00007ff65ee79a89 (S:\b\1\bin\swiftc.exe+0x89a89)
#33 0x00007ff6646942ec (S:\b\1\bin\swiftc.exe+0x58a42ec)
#34 0x00007ffbad1c7614 (C:\WINDOWS\System32\KERNEL32.DLL+0x17614)
#35 0x00007ffbaf1426f1 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x526f1)
<unknown>:0: error: compile command failed due to signal -2147483645 (use -v to see invocation)
ninja: build stopped: subcommand failed.
Error: cmake.exe exited with code 1.
Invocation:
  cmake.exe --build S:\b\103
Call stack:
  at Invoke-Program, S:\SourceCache\swift-build\build.ps1: line 278
  at <ScriptBlock>, S:\SourceCache\swift-build\build.ps1: line 486
  at Isolate-EnvVars, S:\SourceCache\swift-build\build.ps1: line 297
  at Build-CMakeProject, S:\SourceCache\swift-build\build.ps1: line 478
  at <ScriptBlock>, S:\SourceCache\swift-build\build.ps1: line 892
  at Isolate-EnvVars, S:\SourceCache\swift-build\build.ps1: line 297
  at Build-Foundation, S:\SourceCache\swift-build\build.ps1: line 863
  at <ScriptBlock>, S:\SourceCache\swift-build\build.ps1: line 1447
At S:\SourceCache\swift-build\build.ps1:282 char:7
+       throw $ErrorMessage
+       ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Error: cmake.ex...ps1: line 1447
:String) [], RuntimeException
    + FullyQualifiedErrorId : Error: cmake.exe exited with code 1.
Invocation:
  cmake.exe --build S:\b\103
Call stack:
  at Invoke-Program, S:\SourceCache\swift-build\build.ps1: line 278
  at <ScriptBlock>, S:\SourceCache\swift-build\build.ps1: line 486
  at Isolate-EnvVars, S:\SourceCache\swift-build\build.ps1: line 297
  at Build-CMakeProject, S:\SourceCache\swift-build\build.ps1: line 478
  at <ScriptBlock>, S:\SourceCache\swift-build\build.ps1: line 892
  at Isolate-EnvVars, S:\SourceCache\swift-build\build.ps1: line 297
  at Build-Foundation, S:\SourceCache\swift-build\build.ps1: line 863
  at <ScriptBlock>, S:\SourceCache\swift-build\build.ps1: line 1447

@ItaiBear its difficult to say without seeing the full output.  I suspect that there might be some mixups - note that currently if you have Swift installed, you will not be able to build the full toolchain.


include/nuttx/sched.h:  Make naming of all internal names consistent

Summary

Add internal scheduler functions should begin with nxsched_, not sched_
Follow the consistent naming patter of https://cwiki.apache.org/confluence/display/NUTTX/Naming+of+OS+Internal+Functions

Impact
Name change only.  No impact is expected
Testing
sim:ostest

Please ignore complaints of Mixed case identifiers in ESP32 files.  These are references to Expressif ROM functions which are outside of the scope of NuttX.

Note:  This depends on apps PR 244:

The internal interfaces were renamed.  The internal interfaces must not be used by applications.  They should not be referenced in ANY apps.

But they are.  apps/netutils/thttpd callS sched_foreach().  It should not, that is the first error.  But I am not fixing that one today.

sched_foreach() has been renamed nxsched_foreach() -- that is correct since it is an internal OS function not for use by applications.

But now apps/netutils/thttpd won't compile unless I change the name to nxsched_foreach.

PR 244 should now pass the PR checks because this PR was merged.

But for now, all other PR checks are broken until apps PR 244 is merged

I think that the correct fix for the use of nxsched_foreach in apps/netutils/thttpd would be to use the procfs file system.  I think all of that information is available there (it was not when that code was written).

Apps PR 244 has been merged.  PR checks are good again.  If I caused your PR check to fail, I offer my apolgies and recommend that you just restart the checks.


[feature] enable honeycomb tracing

Codecov Report

Merging #34 into master will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #34      +/-   ##
==========================================
+ Coverage   50.00%   50.07%   +0.07%
==========================================
  Files          11       11
  Lines         632      633       +1
==========================================
+ Hits          316      317       +1
  Misses        292      292
  Partials       24       24

Impacted Files
Coverage Δ

pkg/aws_config_server/webserver.go
52.17% <100.00%> (+0.52%)
:arrow_up:

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 6752ecc...a441d29. Read the comment docs.


Add attr_reader, attr_writer and attr_accessor properties

Like in Ruby we can now do this:
class Person
    attr_reader: ["sex"]
    attr_writer: ["age"]
    attr_accessor: ["name"]

Function::attr_reader = (ps...) ->
  for p in ps
    this.prototype["get#{capitalise p}"] = do (p = p) -> -> this[p]

Function::attr_writer = (ps...) ->
  @attr_reader ps...
  for p in ps
    this.prototype["set#{capitalise p}"] = do (p = p) -> (v) -> this[p] = v

etc.

I think built-in ability for creating such props is more convenient than extending Function prototype

I don't. Especially not with the suggested interface. This use case is exactly why we have executable class bodies.

-1.  CS makes it easy enough to create explicit getters and setters.
class Person
  constructor: (@sex, @age, @name) ->
  getSex: -> @sex
  setAge: (@age) ->
  setName: (@name) ->
  getName: -> @name

If you'd prefer manually write this hooey then I have nothing to say

coffeescript is not ruby, ruby is not coffeescript, nuf said

If you'd prefer manually write this hooey then I have nothing to say

... that certainly makes this ticket easier to close ;)
CoffeeScript classes are just convenient ways to define JavaScript prototypes. We're not going to create special getter and setter semantics for JS, especially when getters and setters are already standardized.

attr_reader and attr_writer in Ruby aren't anything special, they're build from more generic language features (class method, aka class macro). This'd be one off special syntax.
To implement it with the same philosophy, using the language features you already have (executable class bodies), what's wrong with the following?
attrWriter = (klass,attrs) ->
   for attr in attrs
     do(attr) ->
       klass::["get#{attr.slice(0,1).toUpperCase() + attr.slice(1)}"] = -> @[attr]
    null

class Person
  attrWriter(this,["name","sex"])

@itrelease What happens when you want your setters to have additional behavior beyond simply setting an attribute?
Also, what is the philosophy behind using getters when attributes are already acceessible without function overhead?

@showell you can simply overwrite required setter or getter:
class Person
  attr_accessor: ["name"]

  setName: (value) ->
    # some operations
    this.name = value

issue was closed so never mind.

Yeah, I don't really understand why you'd want to have simple accessors that just set or return a property without any special behavior. Ruby's attr_accessor and related methods are needed because that's the only way to access ivars from the outside world without resorting to the nastiness of, say,  person.instance_variable_get(:@name) when you want to get a person's name.
The only use for accessors in JavaScript is if you need to do some magic besides just setting a simple variable, and I'd personally rather use the up-and-coming accessors that still look like ordinary property access. But that's still a simple matter of either calling Object.defineProperty or adding a method to Function.prototype that will do it for you with a little bit of sugar.


Can not load the pre-trained model.

Hi @ma-xu ,
I want to use Context-Cluster to do some down-stream tasks. However, I find that I can not load you provide pre-trained model. This may caused by the MLP layer https://github.com/ma-xu/Context-Cluster/blob/c307ab19a79eff737499e24946d08b84f6f30485/models/context_cluster.py#L188.
When will you upload the new pre-trained model?

@dream-toy Thanks for your interest. We will release new checkpoint by the end of this month due to limited computational resources.

ok, Thank you.

You can modify a few variable names in the Cluster class of context_cluster.py. self.f -> self.fc1 self.proj -> self.fc2 self.v -> self.fc_v

@dream-toy @DengFlagellants
Thanks for your patience. The updated checkpoints are updated, with slightly improvements. Mainly two updates: 1) fix a bug mask.sum to sim.sum; 2) conv1x1 to Linear implementation.

Closed no further discussions. Feel free to reopen it if any further questions.


Feature - Token wallet

Simple base contract that allows child contracts to handle tokens.
It can be used for contracts that expect to receive any token(wallets, vaults, exchanges, etc) and as a safe measure to avoid locking tokens in a unprepared contract.

This is a pretty cool idea @JGcarv!
What was the rationale for adding the tokenName functions?

I added the name feature because at the time I was thinking of a more user
facing application, and therefore, using names is more friendly than
addresses. But, it's definitely not necessary.
Another thing, I also intended to make it ERC223 compatible, but that's
still is a ongoing discussion, so I decided to leave it for now.
On sáb, 19 de ago de 2017 18:17 Francisco Giordano<EMAIL_ADDRESS>wrote:

This is a pretty cool idea @JGcarv https://github.com/jgcarv!
What was the rationale for adding the tokenName functions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OpenZeppelin/zeppelin-solidity/pull/378#issuecomment-323548231,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APX3CxVGOG7szNorvE0k_3cndxLYbxffks5sZ1DjgaJpZM4O6xy9
.

Yeah, I think the user- friendly names should be resolved elsewhere, e.g. by using ENS or at the application level.

Agreed! Just removed the functions that used tokenName and rebased the branch.


The Offline Message is missing!

the offline message is missing and the time how long the bot was offline.

https://cdn.discordapp.com/attachments/643770388400046080/658011737785892914/Screenshot_17.png

I can't see your screenshot but I suppose it is something that happens when the bot goes offline for less than a second. I'll check it out.

Hello @Lennex-Web, I've tried checking out what your issue seems to be but I fail to replicate it. Do you have a way to resend that screenshot? It tells me that it doesn't exist.
Here I tested a bot going offline for a short time and it did display the corresponding message.


New issue template syntax for drop down menus etc

https://github.com/getferdi/ferdi/pull/1441

Feature is still in closed early beta

While doing so we should also simplify the templates.
We already have sections for the description -> no need to ask for a checkbox for the description.

Think they are released now

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms


Fix README.md formatting.

fix headings
replace "#" with "." as more conventional syntax
fix send() anchor reference

Coverage remained the same at 100.0% when pulling 949a81840674691de95c9f198020182adfc391a2 on mxl:patch-1 into 1839bf77118893df09b0454d41fa37e3ebaaef03 on caitp:master.


Fix index undefined error for Customizer rendered stories

Context
This PR tries to resolve some of the issues found while integrating the theme support.
Summary
- Fixes undefined index notice in Renderer class when trying to use Customizer settings.
- Adds title show/hide toggle customizer control for 'circles' view.
- Replaces static options like 'order' and 'layouts' to use common utility functions.
- Fixes issue where multiple carousels were not working on the same page.
- Fixes issue for AMP where multiple lightbox of the same story was not working as expected.
- Fix: Select story modal was not closing if no stories were selected.
- Fix: Gutenberg warning for usage of custom block toolbar.
- Fix: Circles carousel were not initialized properly on mobile devices.
- Fix: Block styles were not loaded properly in editor.

Relevant Technical Choices

Uses a static value to keep updating the number of Renderer.php instances. This is to identify the number of active renderer classes for supporting multiple carousels/lightboxes.
Could have used spl_object_id() for the same but it requires php 7 ( >= 7.2.0 )

To-do

Streamline embedding options for various mediums used i.e., shortcode, customizer, widget, block etc. As required.

User-facing changes

N/A

Testing Instructions

PHP notices issue.

Add theme support for the web-stories with add_theme_support( 'web-stories' ) for your theme.
Render the stories in your theme's header.php with new Customizer()->render_stories();.
You'll see the notices on the screen if the debugger is on.

Reproduction steps for carousel not working.

Add two or more carousel on the same page, ( shortcode, block, customizer, widget any ).
Notice that the first carousel is working just fine, but the second carousel and others are not working as expected.

Lightbox not working, steps to reproduce.

Add two or more Web Stories block/shortcode on the same page.
Ensure that at least one story is common among inserted web stories.
Observe by clicking the common story that it won't open the lightbox.

QA

Follow the above-mentioned testing instructions to validate the issue and confirm that the same has been fixed.

UAT

[ ] UAT should use the same steps as above.

Reviews
Does this PR have a security-related impact?

Does this PR change what data or activity we track or use?

Does this PR have a legal-related impact?

I don't like any of the use of static properties or methods here. Let's remove all those and see where we are.

As mentioned above, this static property changes was done to render lightbox elements at the top level context, to minimise conflicts with theme styles.
But, I agree maybe static can be changed. since we can't add wp_footer in the same Renderer class as it instantiates multiple time. I had kept that action into functions.php temporarily.

For the lightbox markup and static values:

Collect lightbox markup while rendering the story items on the page and render it on wp_footer. ( Current )
Maybe just collect the storyIDs/objects that are loaded on the page and then separately render lightbox markup on wp_footer.

In either case I will create a utility class maybe, to track if the Web Stories are rendered on the page, check for customizer option, block in content etc., and render lightbox on wp_footer.  Also maybe we can move all instantiation of other web stories related services like TinyMCE, shortcode, Cutomizer from Plugin.php.
What are your thoughts?
@swissspidy @spacedmonkey

Even in the example, static is not required. You could just do this.
function render_stories_lightboxes() {
        $renderer = new Renderer();
	if ( is_amp() ) {
		$renderer->render_stories_with_lightbox_amp();
	} else {
		$renderer->render_stories_with_lightbox_noamp();
	}
}

Collect lightbox markup while rendering the story items on the page and render it on wp_footer. ( Current )
Maybe just collect the storyIDs/objects that are loaded on the page and then separately render lightbox markup on wp_footer.

Can I confirm the problem we are trying to solve here? If you have a lightbox on the page, you need to have a unique id to setup it up? So if you had 5 different stories on the page, you need to setup 5 different light boxes and output setup into the footer. Is that correct?
WIthout understanding the problem fully here, I can't really advice. I don't feel like the description gives enough detail for me to understand.

I understand, I could have been more detailed.
For now there were following issues:

Multiple instances of Carousels were not working.
If there were duplicate stories then lightbox was not working as expected on AMP pages.
I came across many issues where the lightbox was getting overlapped by other theme elements like the sidebar, sticky header ( theme-2014 ). To resolve that I moved the lightbox to render on wp_footer.

For the current solution, a static $instance_id property does resolve the first two issues. And to keep track of loaded stories so that we don't render duplicate lightboxes, added one for that. While these two I believe are needed, the other one which stores the lightbox markup can be replaced with a renderer function which iterates over loaded stories, which was added to save this loop through stories.
Let me know if we should connect over slack.

@spacedmonkey @swissspidy , I've removed the static methods.
Now we will have one lightbox wrapper per instance in the footer. Rest is same.

Thanks a lot @divyarajmasani!
Your explanation above is also very helpful and allows us to better understand what the code is actually trying to solve. It would be good to have this from the start :-)
I think we should just merge this for now. We can always iterate on it further once we've merged everything to our repo.

Noted,
I'm just testing few reported bugs with the existing PR. Though we still have to add specific styles for the Core themes but that should be a separate PR. I'll merge this one.


squid:S2142 - "InterruptedException" should not be ignored

This pull request is focused on resolving occurrences of Sonar rule
squid:S2142 - "InterruptedException" should not be ignored.
This pull request removes technical debt of 60 minutes.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S2142
Please let me know if you have any questions.
George Kankava

Coverage decreased (-0.1%) to 65.844% when pulling 04cc60c2a4fb002cb2bc2479c0cff482d2e7e411 on DevFactory:release/InterruptedException-should-not-be-ignored-fix-1 into b74157093cb737c4e8ef2e3e23e2588490ef2d22 on feroult:master.

Thanks, George.


Missing Blocker Label to identify show stoppers for progress on platform against this Repo

Expected Behavior
Label field should contain Blocker Label
Actual Behavior
There are many labels but Blocker is mising
Steps to Reproduce the Problem
Specifications

Version:
Platform:

Label created - https://github.com/google/gf180mcu-pdk/labels/blocker


Loosen Platform check to allow better code sharing for out-of-tree platforms

Motivation
Don't lock out other non-iOS platforms (e.g. Windows) with an overly
specific check. This change allows this JS file to be re-used instead of copied and modified. There was one other instance of this pattern, but I'll submit it separate for easier cherry-picking.
Test Plan
Tested Android and iOS playground on simulators.
Release Notes
[GENERAL] [ENHANCEMENT] - some core ReactNative JS library files will be easier to re-use across RN platforms.

This is great! Thanks @matthargett

@facebook-github-bot shipit


sendgrid got error while creating new object

Can't instantiate an object from sendgird

Fixed
branch
development_issue_sendgrid
commit id
88b31a20090c852ec52a79984ed267c1712e8f9e

Commit_ID 95bdc98e5e111086860aeb4af8031a2953f08541, Branch development