[JBEAP-922] - [Migration operation] [Web to Undertow] truststore - ke…

…ystore-password does it really needs to be mandatory?
WFLY: https://issues.jboss.org/browse/WFLY-9155

Please correct the commit message and the PR title to reflect the WFCORE issue. Thanks.

I'm not clear on what this has to do with Web to Undertow migration.

Core - Full Integration Build 5586 outcome was FAILURE using a merge of 06bdf5df57ddd5f4a7008bbe43033c3a0c8e91ca
Summary: Tests failed: 1 (1 new), passed: 4116, ignored: 110 Build time: 01:18:34
Failed tests
org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.testSingleMethodAnnotationsUser1Template: java.lang.AssertionError: Login record has not been written into audit log! (time expired). Checked regex=(TRACE.+org.jboss.security.audit.+Success.+user1|SecurityAuthenticationSuccessfulEvent.*"name":"user1")
	at org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.checkAuditLog(SecurityAuditingTestCase.java:229)
	at org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.testSingleMethodAnnotationsUser1Template(SecurityAuditingTestCase.java:183)
------- Stdout: -------
 [0m00:00:35,885 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0022: Unregistered web context: '/CustomAuditProviderModuleTest' from server 'default-server'
 [0m [0m00:00:35,887 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment CustomAuditProviderModuleTest.war (runtime-name: CustomAuditProviderModuleTest.war) in 2ms
 [0m [0m00:00:35,891 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0002: Content removed from location /store/work/tc-work/5768cf3a0bee5b47/full/testsuite/integration/basic/target/jbossas/standalone/data/content/91/dbc5ac638f1a60b29e139148836d8a42f94b9f/content
 [0m [0m00:00:35,891 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0009: Undeployed "CustomAuditProviderModuleTest.war" (runtime-name: "CustomAuditProviderModuleTest.war")
 [0m [0m00:00:35,936 INFO  [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /store/work/tc-work/5768cf3a0bee5b47/full/testsuite/integration/basic/target/jbossas/standalone/data/content/7a/4c14b3e8470f42e7da1531b04c7dd8b6cfcf05/content
 [0m [0m00:00:35,937 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "form-auth.war" (runtime-name: "form-auth.war")
 [0m [33m00:00:35,961 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.form-auth.war" is using a private module ("org.wildfly.security.manager") which may be changed or removed in future versions without notice.
 [0m [0m00:00:35,976 INFO  [org.jboss.as.arquillian] (MSC service thread 1-4) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."form-auth.war",unit=form-auth.war,tests=[org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase]]
 [0m [0m00:00:35,988 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 30) WFLYUT0021: Registered web context: '/form-auth' for server 'default-server'
 [0m [0m00:00:35,994 INFO  [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "form-auth.war" (runtime-name : "form-auth.war")
 [0m [0m00:00:36,019 INFO  [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /store/work/tc-work/5768cf3a0bee5b47/full/testsuite/integration/basic/target/jbossas/standalone/data/content/7c/87744568dab4e56190856f3a8438a91185169d/content
 [0m [0m00:00:36,020 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "singleMethodsAnnOnlySFSB.jar" (runtime-name: "singleMethodsAnnOnlySFSB.jar")
 [0m [0m00:00:36,033 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment singleMethodsAnnOnlySFSB.jar
 [0m [0m00:00:36,035 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'SingleMethodsAnnOnlyCheckSFSB' in deployment unit 'deployment "singleMethodsAnnOnlySFSB.jar"' are as follows:

	java:global/singleMethodsAnnOnlySFSB/SingleMethodsAnnOnlyCheckSFSB!org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote
	java:app/singleMethodsAnnOnlySFSB/SingleMethodsAnnOnlyCheckSFSB!org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote
	java:module/SingleMethodsAnnOnlyCheckSFSB!org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote
	java:jboss/exported/singleMethodsAnnOnlySFSB/SingleMethodsAnnOnlyCheckSFSB!org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote
	java:global/singleMethodsAnnOnlySFSB/SingleMethodsAnnOnlyCheckSFSB
	java:app/singleMethodsAnnOnlySFSB/SingleMethodsAnnOnlyCheckSFSB
	java:module/SingleMethodsAnnOnlyCheckSFSB

 [0m [0m00:00:36,036 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'AnnOnlyCheckSLSBForInjection' in deployment unit 'deployment "singleMethodsAnnOnlySFSB.jar"' are as follows:

	java:global/singleMethodsAnnOnlySFSB/AnnOnlyCheckSLSBForInjection!org.jboss.as.test.integration.ejb.security.authorization.AnnOnlyCheckSLSBForInjection
	java:app/singleMethodsAnnOnlySFSB/AnnOnlyCheckSLSBForInjection!org.jboss.as.test.integration.ejb.security.authorization.AnnOnlyCheckSLSBForInjection
	java:module/AnnOnlyCheckSLSBForInjection!org.jboss.as.test.integration.ejb.security.authorization.AnnOnlyCheckSLSBForInjection
	java:global/singleMethodsAnnOnlySFSB/AnnOnlyCheckSLSBForInjection
	java:app/singleMethodsAnnOnlySFSB/AnnOnlyCheckSLSBForInjection
	java:module/AnnOnlyCheckSLSBForInjection

 [0m [0m00:00:36,036 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'AnnOnlyCheckSFSBForInjection' in deployment unit 'deployment "singleMethodsAnnOnlySFSB.jar"' are as follows:

	java:global/singleMethodsAnnOnlySFSB/AnnOnlyCheckSFSBForInjection!org.jboss.as.test.integration.ejb.security.authorization.AnnOnlyCheckSFSBForInjection
	java:app/singleMethodsAnnOnlySFSB/AnnOnlyCheckSFSBForInjection!org.jboss.as.test.integration.ejb.security.authorization.AnnOnlyCheckSFSBForInjection
	java:module/AnnOnlyCheckSFSBForInjection!org.jboss.as.test.integration.ejb.security.authorization.AnnOnlyCheckSFSBForInjection
	java:global/singleMethodsAnnOnlySFSB/AnnOnlyCheckSFSBForInjection
	java:app/singleMethodsAnnOnlySFSB/AnnOnlyCheckSFSBForInjection
	java:module/AnnOnlyCheckSFSBForInjection

 [0m [0m00:00:36,083 INFO  [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "singleMethodsAnnOnlySFSB.jar" (runtime-name : "singleMethodsAnnOnlySFSB.jar")
 [0m [31m00:00:36,200 ERROR [org.jboss.as.ejb3.invocation] (default task-23) WFLYEJB0034: EJB Invocation failed on component SingleMethodsAnnOnlyCheckSFSB for method public abstract java.lang.String org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote.roleBasedAccessMore(java.lang.String): javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract java.lang.String org.jboss.as.test.integration.ejb.security.authorization.SimpleAuthorizationRemote.roleBasedAccessMore(java.lang.String) of bean: SingleMethodsAnnOnlyCheckSFSB is not allowed
	at org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:134)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
	at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
	at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

@bstansberry @darranl I'm sorry for the delay (I've missed notifications), I'll look into it.

@darranl May I ask for clarification of you change request?
I have tried migration without trusstore password and it works (with the wildfly from master with changes from this PR and linked one) -> password for trusstore is optional.
For the keystore it behaves in the same way, although I haven't found a way of creation keystore with key without password. I was able simulate it with keystore with entry only (in that case there was a problem that there are no keys in store) - but as a prove that it can be defined without password it is enough.

AIUI the issues are as follows:

The xsd for the version that is current when this change is made needs to be updated to reflect the fact the password is not required.

The xsd version this applies to is not wildfly_config_5_0.xsd, as 5 had shipped and we don't change it. It would have been 6, which is the version for WF Core 4 / WF 12. But this likely isn't going to make WF Core 4. So it will be wildfly_config_7_0.xsd.

It's ok that even though the  5 and 6 xsds say the attribute isn't optional that the parser for those versions (ManagementXml_5) is lenient and doesn't require it. IOW we shouldn't need a ManagementXml_7 that doesn't require the attribute while ManagementXml_5 would continue to.

@bstansberry
I've checked definition of password, and it is optional - https://github.com/wildfly/wildfly-core/blob/master/server/src/main/resources/schema/wildfly-config_6_0.xsd#L652
(I've validate it also as xml against xsd)
So I don't think there is need to ass anything.

retest this please
@jmesnil Assuming no relevant CI issues this is good to go.


how's the speed of resize compare with opencv?

Hi, simd seems pretty good. just wonder does there any benchmarks on specific resizing compare with opencv?

Simd is specialized in single thread performance. In multi thread performance of OpenCV will be greater. Unfortunately there are no benchmark to test its performance to compare with OpenCV now.


Update README.md

Add the QEMU error in README.md

@satyajitghana Thank you for your contribution! Now, the configure_qemu.sh is executed with docker run. Did described error occur?
https://github.com/atinfinity/sdk_manager_docker/blob/62428020d8b3a0b6cf065fef2fc59d68d212660d/Dockerfile#L68

Yes, for some reason it still did, I had to rerun the commands again on a running container to get it to work.

CMD is executed when no command is specified in docker run. In this repo container is launched as docker run <args> bash, so bash overrides CMD <command>.
To solve this, you need to launch container with something like docker run <args> bash -c "sudo /home/${USERNAME}/configure_qemu.sh; bash".

@satyajitghana @MiroPsota  Thank you for your comment. I'll consider measures to resolve this problem. So, please wait a little.

LGTM!

👍


Add Person.notes

Solves #323.
One bug was discovered and fixed, see commits in this PR.

@gvwilson amended that commit. Green light to merge?

:+1: to merge and deploy.


Reverse an integer using stack | Python3

Reverse an integer using stack -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] Python3

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

Please assign this to me


convolution with non-contiguous arrays

I noticed that the results of convolution with non-contiguous arrays are incorrect. For example if the output is non-contiguous:
import numpy as np
from neon.backends import gen_backend
ng = gen_backend(backend='gpu', device_id=0)

cl = ng.conv_layer(ng.default_dtype, N=32, C=4, K=8, D=1, H=1, W=3, T=1, R=1, S=2)
I = ng.ones(cl.dimI)
F = ng.ones(cl.dimF)
O = ng.zeros((8, 1, 1, 3, 32))
O2 = O[:, :, :, 1:, :]
ng.fprop_conv(cl, I, F, O2)
print O.get()[:, :, :, 1:, :] # O2 contents : prints 0s and 8s instead of just 8s

I'm guessing it's just not supported, but the code also doesn't check that O2 is contiguous.
I wonder how difficult it would be to support arbitrary strides?
It's of course possible to work around this limitation by copying data to and from contiguous arrays, but that's more complicated, less efficient, and may need significantly more memory.
Personally, I care about the first 4 axes of the output array, i.e. the strides that are greater than 1 anyway.
By the way, cuDNN supports setting arbitrary strides with cudnnSetTensor4dDescriptorEx, so I must not be the only one who finds it useful.

Adding arbitrary slicing support for input/output tensors would be pretty easy.  Just a few more kernel params and some additional pointer arithmetic.   I think the common use case there is merging the feature map output of two branches.  But K for us is an outer dimension and so merges are just simple contiguous concatenations.  I haven't had any requests for this and was unaware it was a desired feature.   I'll check out cudnn and see if I can at least match their support.

Thanks!


Is there an interface or a way to set up an interface between BookStack and Other Systems?

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
Hello,
I'm looking for a way to integrate BookStack with a Ticket System. Specifically, I want to receive suggestions on keywords for entries in the ticketing system from BookStack articles.
I'm wondering if there is an interface or a way to set up such an interface between the two applications to exchange data and achieve this integration. I've searched the internet for information on this topic but couldn't find any clear guidance.
Therefore, I'm reaching out to the community to see if anyone has experience with integrating BookStack and Ticketsystems or has any suggestions on how I can achieve this integration. Any help or suggestions on this matter would be greatly appreciated.
Thank you in advance for your assistance.
Best regards
Exact BookStack Version
does not matter
Log Content
No response
PHP Version
does not matter
Hosting Environment
does not matter

Hi @KxvinG,
BookStack has a built-in REST API, including an endpoint for general search which would likely be useful for this use-case. I use this endpoint in this api-scripts example.

Rest API details

I can't provide any details in regards to SAP C4C, I have never used it.

Since the original question has been answered, and there's been no further conversation, I'll therefore close this off.


Update README

Add instructions to include the libraries also from the CDN, instead that only from the local folder.

Done it @ComputerWolf
https://github.com/ComputerWolf/SlickNav/pull/192

Done it @ComputerWolf
https://github.com/ComputerWolf/SlickNav/pull/192

No longer needed

No longer needed


Finish removing 'kubectl get all'

As has been extensively discussed on prior occasions (see https://github.com/kubernetes/kubectl/issues/151), kubectl get all is not recommended, has been removed from documentation, and should be removed.
It appears that the primary reason this has not yet been completed is because the issue was filed against the kubernetes/kubectl issue tracker instead of kubernetes/kubernetes. At the request of the kubectl maintainers in https://github.com/kubernetes/kubectl/issues/1584#issuecomment-2077738119, the issue is being copied over to here.
The requested change is that kubectl get all is formally deprecated and eventually removed - or, fixed so that it does what it says it does.

Oops, I didn't see that the kubectl maintainers requested tracking it elsewhere.
/transfer kubernetes


B 17842 New Department Indicators on Orders View/Edit Page

Agility Ticket: B-17842
Summary
This adds "57 Air Force and Space Force", "96 Army Corps of Engineers", and "97 Office of Secretary of Defense and all Defense Agencies" to the list of options in the "Department Indicators" dropdown menu in the "View/Edit Orders" page that the TOO and SC have access to.
How to test

(If needed) Create a move and upload orders
Login as a SC/TOO and access the move page
Click "Edit Order" in the "Orders" module
In the department indicators dropdown, the above options should now be available as options.
Change to one of the new options and click "Save", the TOO/SC summary screen should now show the new Dept. in the "Orders" module.

Backend

[x] Code follows the guidelines for Logging.
[x] The requirements listed in Querying the Database Safely have been satisfied.

Screenshots

Note: This PR is a draft until our team receives clarification regarding the naming of the 97 Dept. name.

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 2fae08ff56193c39a1de347822cdfdef2764aa53

You may also have to add to internal.yaml and support.yaml to allow those new values.

You may also have to add to internal.yaml and support.yaml to allow those new values.

@taeJungCaci Good catch, just pushed the changes to those yaml files as well.

Test coverage on client failed.
Last run: Thu 16 Nov 2023 08:46:25 PM UTC
Refer to this report to see coverage details for the client app.
Documentation for test coverage can be found at this link.

heads up to please include team name tags under the labels of the PR

Tested and looks good!

Commit: db3dc54 -> Reverted since this was changing affiliations and not department indicators.
Commit de8148c -> Reverted more that was affiliation related.
Commit 9c924a0 - > Was causing issues because Department Indicator consts were never created and was using BoS instead.
Commit a399aea -> Test was using Department Indicator instead of Affiliation. Default affiliation is also Army in test build.
@brooklyn-welsh @JamesHawks224 Please review the changes. I don't think I have any additional changes.

Thanks Tae! I think that one test and invoice file using dept. indicators instead of affiliation was what led me down the path of changing all that other unrelated stuff, thanks for catching that and reverting all my unnecessary changes. All of the changes look good to me.

Commit: db3dc54 -> Reverted since this was changing affiliations and not department indicators.
Commit de8148c -> Reverted more that was affiliation related.
Commit 9c924a0 - > Was causing issues because Department Indicator consts were never created and was using BoS instead.
Commit a399aea -> Test was using Department Indicator instead of Affiliation. Default affiliation is also Army in test build.
@brooklyn-welsh @JamesHawks224 Please review the changes. I don't think I have any additional changes.

Thanks Tae! I think that one test and invoice file using dept. indicators instead of affiliation was what led me down the path of changing all that other unrelated stuff, thanks for catching that and reverting all my unnecessary changes. All of the changes look good to me.

No prob! Yeah, they were using affiliation conts for dept. indicators in move history as well which was causing a bug too. I guess there are still a lot of uncaught bugs in the code and it's causing issues for our work. Can't trust the existing code either lol.


Customize Workspaces

Two related questions for customizing workspaces:

I am currently using Workspaces with Sketchybar which runs aerospace list-workspaces --all. Is there a way I can customize to have fewer workspaces? Or start with fewer workspaces and dynamically increase to more similar to Mission Control? I don't love having the menu bar full of 0-9 + A-Z if I am only using the first few. If that's not possible maybe I can create an indicator to color if a workspace has any windows attached to it.

Is there a way to start the workspaces from 1 instead of 0? I am frequently using the keyboard shortcuts of alt+0 and alt+1 to switch between workspaces and it would be easier to switch between 1 and 2 compared to 0 and 1. If possible, I would like to make the default workspace be 1 and increment from there. Alternatively I can likely change the keybindings to make alt+1 go to workspace 0.

Or start with fewer workspaces and dynamically increase to more similar to Mission Control?

You can call aerospace move-node-to-workspace name-that-didnt-exist-before and it will create workspace name-that-didnt-exist-before and move the window to the newly created workspace. Workspaces are created on the fly

If that's not possible maybe I can create an indicator to color if a workspace has any windows attached to it.

aerospace list-workspaces --on-monitor focused --empty no

I don't love having the menu bar full of 0-9 + A-Z

Is there a way to start the workspaces from 1 instead of 0?

#100
#32

I can't believe it was that simple, thanks @nikitabobko!


Hangs on the SpongeMain project

Submitting this project on Atelier, won't return any comments and the logs only show
Received new webhook request.
Handling submission eT_cwTKjRpiPZyaZRraHEg

Indicating that this hangs before even starting the Atelier commenting renderer.
Locally, with only the 'Smell of Processing' rules enabled and not reporting to Atelier, this project returns 170 violations. 168 of these are 'drawing method outside the draw stack' violations and they, on first glance, look to be incorrect. The other two are 'use of global event variable', and these do look to be correct.
Attachement: SpongeMain.zip

Looks like this was also fixed by 0c3a40e


Turtlebot 4 lite raspberry pi wifi network not showing up. Unable to ssh into it.

Please provide the following information:

OS: Ubuntu 18.04
ROS Distro: Dashing
Built from source or installed: Installed
Package version:

Expected behaviour
I'm expecting to see the Wi-Fi network "Turtlebot4" to appear when the TurtleBot 4 lite powers on.
Actual behaviour
I am not seeing the Wi-Fi network appear, and am not able to connect and SSH into the raspberry pi.
To Reproduce
Provide the steps to reproduce:

Place TurtleBot 4 lite onto charging dock to turn on.
Wait 30 seconds for a noise to chime.
Look in available internet connections on host computer for TurtleBot 4.

Other notes
Add anything else you thing is important.

The RPi creates a 5GHz network. Can you make sure that your WiFi adapter supports that?
If not, you can try to connect to it using an ethernet cable. See https://turtlebot.github.io/turtlebot4-user-manual/troubleshooting/faq.html#access-the-rpi-over-ethernet

My WiFi adapter does support 5 GHz. I am using the TP-Link Nano AC600 USB WiFi adapter.
I decided to use the ethernet cable and I was able to SSH into it and configure the WiFi, but I do not know if it is connecting successfully or not. Does the raspberry pi only support connecting to a 5 GHz network?
Additionally, may I ask what is the difference between the Create 3 and the Raspberry Pi, and why we need to configure the WiFi for both of them?

Additionally, while I was configuring the Turtlebot 4 standard, when it rebooted the display screen was off and none of the LEDs were working. Is it because it did not connect to a network successfully?

The RPi supports both 2.4 and 5GHz networks but it is recommended to use 5GHz to improve performance for things like streaming camera data.
To check if the RPi has connected to WiFi, try to SSH in and run ip a. You should see an entry for wlan0 with an IP address if it is connected like so:
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether e4:5f:01:89:bc:59 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic noprefixroute wlan0
       valid_lft 6476sec preferred_lft 6476sec
    inet6 fe80::e65f:1ff:fe89:bc59/64 scope link
       valid_lft forever preferred_lft forever

If the interface is down, you can manually edit the network configuration located at /etc/netplan/50-cloud-init.yaml. Make sure that your SSID and password are correct. If you make any changes there, you can apply them by calling sudo netplan apply.

Also, while I was configuring the Turtlebot 4 standard, when it rebooted the display screen was off and none of the LEDs were working. Is it because it did not connect to a network successfully?

We are working on a solution to allow the TurtleBot 4 to only use the RPi WiFi but it requires some IP routing that we do not yet support. See #26 for details. You are able to run the robot without connecting the Create 3 currently, but the ROS2 topics will only appear on the RPi4, and not an external PC.

Also, while I was configuring the Turtlebot 4 standard, when it rebooted the display screen was off and none of the LEDs were working. Is it because it did not connect to a network successfully?

By default CycloneDDS is configured to use both usb0 and wlan0, and will fail if one of the interfaces is down. If you check the logs on the RPi with sudo journalctl -u turtlebot4 -r you will likely see a bunch of errors from CycloneDDS.

If it shows:
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether e4:5f:01:bb:8f:2b brd ff:ff:ff:ff:ff:ff
that means it did not connect successfully, right?

I've modified the 50-cloud-init.yaml file and rebooted. I am no longer able to ssh into the raspberry pi using the ethernet cable.

If it shows:
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether e4:5f:01:bb:8f:2b brd ff:ff:ff:ff:ff:ff
that means it did not connect successfully, right?

Yes, it did not connect.

I've modified the 50-cloud-init.yaml file and rebooted. I am no longer able to ssh into the raspberry pi using the ethernet cable.

What did you change? The ethernet and usb0 should not be modified.

I uncommented the “# ap” line to see if it would reboot in ap mode and deleted my ssid and password fields

The AP mode still requires a SSID and password so this is likely an invalid configuration. Netplan probably can't run properly which is why the ethernet stopped working. For future reference, you can call sudo wifi.sh -a to set the RPi back to AP mode.
If you have a micro HDMI cable you can connect that to the HDMI0 port of the RPi. You can then use a monitor and keyboard to recover. Your other option is to just reflash the SD card by following the instructions here. The RPi should be back in AP mode with a fresh install.
Once you have recovered the RPi I would recommend creating a WiFi hotspot from your phone and trying to connect the RPi4 to it. If that works then the issue may be with your WiFi network.

I have been using a hotspot with my phone. I will try to recover the 50-cloud-init-yaml file. What’s the proper format?

See wifi.sh. I would recommend running sudo wifi.sh -a first before modifying so that the formatting is correct. You can also try to comment out the band: 5GHz line when in AP mode so that the AP is 2.4GHz.

I was able to connect it to a router that had a 5 GHz network but I am still unable to connect it to a 2.4 GHz network. I am also trying to connect it to my campus Wi-Fi. Is there any encryption that I should be aware of on the Turtlebot?


Enable VGNC xrefs for callithrix_jacchus and papio_anubis [master]

Description
Enable production of VGNC xrefs for additional two species: marmoset, olive baboon. For consistency with #426.
Use case
VGNC has recently begun to provide data for these species and have requested Ensembl to enable production of corresponding xrefs.
Benefits
More VGNC xrefs in Ensembl.
Possible Drawbacks
Increased run time of the xref pipeline. That said, a single run of VGNCParser takes in the order of seconds so it will not be a large increase.
Testing
Have you added/modified unit tests to test the changes?
No.
If so, do the tests pass/fail?
N/A
Have you run the entire test suite and no regression was detected?
Yes, no regression detected.

Coverage remained the same at 81.472% when pulling f182933592980abb0595f20f78c862c53150128a on feature/vgnc_xrefs_master into ca396c5ea453fe498b1344341c90388c68645d7a on master.


Add automatic restore functionality

We should create a session file on each run that is named repeatably for the task and, if it is detected, it should be used to restore a run. Hashcat will automatically delete it if the run is successful, so that should make it easier to stop tasks and have them start again.

Added with 8165e1229dda97a0f30526588ce7c19a403e106a


Add dispose() into the xRayViewer so that it clears out the THREE scene.

Also ran yarn format.

Can we use the same prettier config that we are using in internal code? Your formatting changes here make this different than our internal style. (Which isn't necessarily a problem, because it's third party code, but if the style config here is arbitrary, I'd rather have things be the same.)

@pdubroy I have no strong feelings about the style used here. But for now this is what is checked in.

We should definitely look into the correct way to free the memory of the objects that we are removing from the scene. See here for some info about this.

@wally-the-cartographer merge

Merge requested by authorized user SirVer. Merge queue now has a length of 1.


Add Windows support.

This is the first step towards having Torus working on Windows, as per #123.
This patch splits up some unix specific behaviour and adds build tags so we can
use a Windows specific implementation:

use Named Pipes on Windows (only) as a net connection.
disable the prompt styler on Windows
we don't set Setsid: true on the daemon command for Windows
we set torusRoot according to HomePath and prepend HOMDERIVE on Windows
per OS rootPathLength to decide if we're on a root path or not
set the transport address per OS, encapsulate it's behaviour and rename SocketPath to TransportAddress

Needs attention:

disabled prompt for Windows

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

@ianlivingstone @jbowes I've implemented npipes, which was surprisingly easy. I'm going to read up on the documentation a little bit more for named pipes in general to dig through all the security implementations, but from an initial look, this seems like the perfect solution (also, Keybase are using this).
One suggestion about this, it might be worth it implementing the DialTimeout setup, this way we ensure we don't hang forever and close connections when they take too long. I haven't done this here to mimic the same behaviour as the regular setup, but we could do this in a separate PR.
I'll also have a look if we can get around the setsid for Windows in a way.

One suggestion about this, it might be worth it implementing the DialTimeout setup, this way we ensure we don't hang forever and close connections when they take too long. I haven't done this here to mimic the same behaviour as the regular setup, but we could do this in a separate PR.

Makes tons of sense, want to split off another issue to set this up?

So regarding Setsid, apparently this is the default on Windows and we don't need to set it.
(taken from the Keybase documentation)

So regarding Setsid, apparently this is the default on Windows and we don't need to set it.

Nice!

What's the installation process look like for someone on Windows? Should we split off another issue for setting that up?
Do they just put the torus.exe somewheres in their path? I suppose we need some documentation surrounding that as well.

We're just waiting on:

promptui changes
creating a .zip of torus.exe
Installation instructions
Creation of an issue to make an .msi installer

Before this can be merged.

With regards to the UTF8 characters, I've used simple latin fallbacks on Windows. By default, Windows doesn't support UTF8 in the prompt.
When we use a .msi installer, we could potentially look at turning this on by default?
http://superuser.com/questions/269818/change-default-code-page-of-windows-console-to-utf-8/269857#269857


KAFKA-2478: Fix manual committing example in javadoc

Committing before inserting all records into the database
might lead to some records being lost.
I've changed the example to commit only after all records
returned by poll are inserted into the database.

Alternative implementation makes sure that buffer size
does not grow over commitInterval, but it's more verbose:
        Properties props = new Properties();
        props.put("bootstrap.servers", "localhost:9092");
        props.put("group.id", "test");
        props.put("enable.auto.commit", "false");
        props.put("auto.commit.interval.ms", "1000");
        props.put("session.timeout.ms", "30000");
        props.put("key.deserializer", "org.apache.kafka.common.serialization.StringDeserializer");
        props.put("value.deserializer", "org.apache.kafka.common.serialization.StringDeserializer");
        KafkaConsumer<String, String> consumer = new KafkaConsumer<>(props);
        consumer.subscribe(Arrays.asList("foo", "bar"));
        int commitInterval = 200;
        List<ConsumerRecord<String, String>> buffer = new ArrayList<>();
        Map<TopicPartition, Long> consumedOffsets = new HashMap<>();
        while (true) {
            ConsumerRecords<String, String> records = consumer.poll(100);
            for (ConsumerRecord<String, String> record : records) {
                buffer.add(record);
                consumedOffsets.put(new TopicPartition(record.topic(), record.partition()), record.offset());
                if (buffer.size() >= commitInterval) {
                    insertIntoDb(buffer);
                    consumer.commitSync(consumedOffsets);
                    buffer.clear();
                    consumedOffsets.clear();
                }
            }
        }

Here we commit every 200 records as in original example, but we have to maintain
the consumed offsets manually, so we don't commit records that haven't been inserted
into the database yet.

@shtratos I think the example still needs fixed in trunk, but the code has diverged. Can you rebase?

@hachikuji rebased, please review

LGTM

@hachikuji thank you. Will you merge this? Do you need any other help with this PR?

LGTM. Merged to both trunk and 0.9.0.

Thanks!


Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed

After update 10.1.12 I am getting:

Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self'".

I reverted the changes from this PR #1117 locally and now things work fine.

You're using a custom typescript version and not the one that came with atom-typescript. If you update to a recent nightly, it should work fine. The current stable (2.0.6?) still has the issue, but you can work around it by creating a wrapper package that's using loophole to require Typescript.
var loophole = require("loophole")
module.exports = loophole.allowUnsafeNewFunction(function() {
  return require("typescript")
})

Then specify a full path to this module.

@guncha I'm getting the issue with typescript 2.1.0-dev.20161109

I'm still seeing this.

My workaround was doing:

Update makeTypeScriptGlobal.js to:

var loophole = require("loophole");
// ...
global.ts = loophole.allowUnsafeNewFunction(() => require(typescriptPath));

Update package.json to:

"dependencies": {
  // ...
  "loophole": "1.1.0"
}

Install loophole

# Not sure if this is the correct way of doing it as I know nothing about node.
$ cd ~/.atom/packages/atom-typescript/node_modules
$ npm i loophole

Is there any legit fix for this in the pipeline? Is atom-typescript deprecated?

This workaround doesn't work for me... Just to clarify, this is the new makeTypeScriptGlobal.js that I have, in case I made csome mistake:
import {isAbsolute} from "path"

// Debugging helper
global.stack = function() {
    console.error((<any>new Error()).stack);
}

// Export Typescript as a global. Takes an optional full path to typescriptServices.js
export function makeTsGlobal(typescriptPath?: string) {
  if (typescriptPath) {
    if (!isAbsolute(typescriptPath)) {
      throw new Error(`Path to Typescript "${typescriptPath}" is not absolute`)
    }

    typescriptPath = typescriptPath.trim()
  } else {
    typescriptPath = "typescript"
  }
  // I added this:
  var loophole = require("loophole");
  global.ts = loophole.allowUnsafeNewFunction(() => require(typescriptPath));
  // global.ts = require(typescriptPath);
}

@conan747, it seems like you are updating makeTypeScriptGlobal.ts instead of makeTypeScriptGlobal.js

Yeah, that was it. Thanks man!

After version 11.x I believe this issue is now fixed.


Darwin: Bug fixes in BleConnectionDelegateImpl

Avoid clearing the ble global if it points to a different instance.

Also read characteristic value before dispatching and improve logging.

Fast-tracking platform-specific fix with platform owner review.


export nimbleFunctionList?

This is a curious case. It only makes sense to use it in setup code, and in that case it runs ok, found in nimble namespace.  But if a user wants to look at it as a standalone call from R, it isn't found.  I think it would make sense to export and document it.

Agreed, however obscure, I think this should work.  Especially since we advertise that the setup code is "regular R code", and anything that works in one should work in the other.

also modelValues and modelValuesConf

ok, I will add those
On Mon, Sep 26, 2016 at 3:52 PM, perrydv<EMAIL_ADDRESS>wrote:

also modelValues and modelValuesConf
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nimble-dev/nimble/issues/231#issuecomment-249720801,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYr3n6mLfV3xwifg6riSFYUjCZreXE1ks5quEyTgaJpZM4J8V51
.

added nimbleFunctionList to exports with a minimal roxygen entry.
modelValues and modelValuesConf were already exported...


TypeScript support

Find typescript module in current working directory and use it to compile ts or typescript code blocks.

Whoah... How much :+1: ...
What is the use case? Tasks are pretty simple in most cases. What, you will define types in the task, why? Uh. Definitely don't seeing sense for typescript, but it would be just easy to add.

Yeah seems needless, I'll close it for now. Also I guess no editor has intellisense support for typescript in markdown code

It might be a good idea to consume or create a separate NPM module which can be responsible for spawning code snippets from multiple programming languages ( including languages like TypeScript, Lua, PHP, etc )
This way maid itself could focus itself on orchestrating tasks and this separate module would focus on spawning and executing tasks.

the separate module for spawning is a good idea and it would handle the problems of #22 and #40


Edge detection

Description
Implements Canny Edge Detection to filter an image into only edges, in grayscale.
Testing

Be in the sketchy/ml/edge_detection folder and run model.py.
Should return a filtered donut.

Notes

Takes as input a binary byte string and returns as output a binary byte string in the jpg format

Test with
if __name__ == "__main__":
    with open("../../public/Glazed-Donut.jpg", 'rb') as f:
        r = f.read()

    res = edge_detection(r)
    image = np.array(Image.open(io.BytesIO(res)))

    plt.imshow(image, cmap="gray")
    plt.show()


stably sort contig link counts

We noticed an issue whereby the order of a fasta impacted the plasmid assignment. I.e. moving a contig from the start of a fasta to the end moved it from plasmid to chromosome.
The cause was a lack of stable sorting for contig link counts.
When assigning clusters based on low-linkage contigs, the contig link counts are sorted ascending based on number of links. This means that contigs with less links come first:
OrderedDict([('93_8c4ba764a297754de0bcf081764fadef_circular=false', 1),
             ('142_494caf9c7c04ae64d92f9c52294a8928_circular=false', 1),
             ('141_114a1e3e2d432957a53f2f55b3976d00_circular=false', 1),
             ('161_07c8c980bc4cb398f48683b1c1ebddff_circular=false', 1),
...

This makes sense. However, given that many contigs share a link count, the sorting was dependent on the order of the sequences in the input fasta. contig_clust_assoc was already defined in the sorting/ordering function, so I assume it was meant to be used as a tie-breaker for sorting. However, it didn't appear to be used for anything.
By incorporating the cluster scores, we can sort the contigs first by link count, and secondarily by score (with highest scores coming first). This brings stable sort ordering regardless of the order of the fasta file.

I had submitted similar PR #164 with addresses this issue by first ordering input contigs based on length from longest to shortest and then by md5 checksum, in addition for contigs with identical number of links to plasmid primary clusters, I order by contig length. Since md5cheksum is unique, this double ordering both brings consistency to contig_report.txt and mob_typer.txt and is biologically and practically sound as longer contigs usually are more information rich. Ordering by primary plasmid cluster score seems to me a bit less stable as is done anyways later in the code where those highly covered plasmid clusters are assigned contigs first anyways. James will review the PR and will then probably push a new release and conda recipe


CodeAi fixes: Remove dead code

CodeAi suggests the removal of 3 lines of dead code in log_reader.cc.
Issue #517
CLA: QbitLogic

This was landed in 3da4d8b9899257386aeb5ffa345a6477c62ff7bf. Thank you very much for your contribution!


Error: long_description_content_type

Error: /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'long_description_content_type'

Was fixed in some past commit (can not remember in which, and missed to mention it in the commit message).


Add metadata, improve SEO

I would like to learn and work on it.

Has Hemant been assigned this issue or is it still open? I too wanted to learn and work on SEO

Since @ORKO06 is working on another issue, @Swatishree-Mahapatra you can take this up! 🚀

@Swatishree-Mahapatra you can find the basic meta tags here ⬇
https://github.com/CIPHERTron/kaagaz/blob/main/components/layout.tsx
and their config from the SiteConfig object in config/index.json
Apart from this, refer to some articles on the internet regarding SEO in Next.js. You'll get some more idea 💪🏻


removeListener

Hi,
Hi, would I remove a particular listener, please?
Thanks
Stephen

Hi guys,
Just noticed my error in my question!
How would I remove a particular listener, please?
I have a number of listeners that needs to stay on but have a particular one which needs to be either stopped or reset.
Thanks

Hello!
I think you can use removeListener on the context manager. Note, that if you want to use it, you have to keep a reference to the event listener in a variable.
So instead of doing this:
mgr.addListener(new EvtPinListener(...);
you will write
EvtPinListener * myEvtPinListener = new EvtPinListener(...); mgr.addListener(myEvtPinListener);
and when you want to remove it, you just write mgr.removeListener(myEvtPinListener)


Code smell: changing return true; to true in check_access causes a test failure

This is supposed to not affect any actual execution result. There might be an underlying issue.

Hi jane could you please be more specific about this issue?

stall issue, open again if still relevant


add to CI server to run unit tests automatically

it would be nice to add this to one of the CI services that allow free unit test running for open source projects, so we can make sure all tests always pass.

done

done


Test if invited user can decrypt message when nine users are invited

For https://github.com/vector-im/hydrogen-internal/issues/24
Branch from support-hydrogen-adapter

Not sure how to fix the typing issue here, any ideas @michaelkaye?

@MidhunSureshR ^^ maybe this last commit is a way to skip around the typing; i'm not sure whether there's a way to annotate the lambda itself; but this seems to work.


[api] Refactor drawMask() for instance segmentation

Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 8.16327% with 45 lines in your changes missing coverage. Please review.

Project coverage is 57.91%. Comparing base (725851b) to head (eeab075).
Report is 3 commits behind head on master.

Files
Patch %
Lines

...pencv/src/main/java/ai/djl/opencv/OpenCVImage.java
0.00%
20 Missing :warning:

.../java/ai/djl/modality/cv/BufferedImageFactory.java
0.00%
19 Missing :warning:

.../cv/translator/InstanceSegmentationTranslator.java
0.00%
6 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##             master    #3304       +/-   ##
=============================================
- Coverage     72.71%   57.91%   -14.81%
+ Complexity     7361     5757     -1604
=============================================
  Files           677      677
  Lines         32561    32594       +33
  Branches       3433     3441        +8
=============================================
- Hits          23677    18877     -4800
- Misses         7258    12261     +5003
+ Partials       1626     1456      -170

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


test-cluster-failover is flaky

Description
https://grabl.io/flyingsilverfin/client-python/989e727c8ef6c8e0ac1de8247b868d21a2515157/build/2/correctness/1/test-cluster-failover/1
Environment

OS (where Grakn server runs): Ubuntu 20
Grakn version (and platform): the artifact that's included in the repository
Grakn client-python version: flyingsilverfin/client-python@989e727c8ef6c8e0ac1de8247b868d21a2515157

fixed in https://github.com/graknlabs/client-python/pull/198


Use Debouncer for update calls on stats sensors

A fresh restart of #32088, using helpers/debounce (suggested by @balloob)
to limit activity when incoming bursts of samples are received.
For the debouncer: set cooldown=10ms and immediate=False (we want to wait for the sampling burst to end before calling the sensor update)
cc @exxamalte @MartinHjelmare @fabaff

Breaking change

Proposed change

Instead of call await self.async_update_ha_state(True) after each sample and also inside the purge callback, we call a debounced wrap of that: self.hass.async_create_task(self._debounced_updater.async_call())
That way we ensure that multiple simultaneous calls are processed just once, and the number of cancelling+setting the purge callback is minimized, thus decreasing the stress on the event bus.
As the issue (#31997) is hard to catch, this fix may need a test in real conditions to be sure that it is valid, and the unknown listener core warnings completely disappear. I will put it in my production HA to check it this week, and I'll feedback with the results.
Notes: Debouncer usage and tests
cc @balloob
When debouncer is set to immediate=False, and the call is not done until cooldown is expired, the common hass.block_till_done() does not wait for the debouncer (there are no tasks registered), so async_update is never called.
To quickfix that I introduced a silly task (a call to await asyncio.sleep(cooldown)) to prevent the block from finishing before the delayed update is called.
That may require a deeper review to solve it with a more elegant hack :)
The issue only affects tests, as in real time things happen when they need to.
Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

This PR fixes or closes issue: fixes  #31997
This PR is related to issue:  #31576
This PR is another approach of #32088, so at least one of the 2 should be closed.
Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

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

[ ] Documentation added/updated for www.home-assistant.io

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

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

[ ] No score or internal
[ ] 🥈 Silver
[ ] 🥇 Gold
[ ] 🏆 Platinum

As the issue (#31997) is hard to catch, this fix may need a test in real conditions to be sure that it is valid, and the unknown listener core warnings completely disappear. I will put it in my production HA to check it this week, and I'll feedback with the results.

---> This patch does not solve the problem :(
2020-02-25 02:11:11 WARNING (MainThread) [homeassistant.core] Unable to remove unknown listener <function async_track_point_in_utc_time.<locals>.point_in_time_listener at 0xe98bb198>
2020-02-25 02:12:10 WARNING (MainThread) [homeassistant.core] Unable to remove unknown listener <function async_track_point_in_utc_time.<locals>.point_in_time_listener at 0xe9a27660>
2020-02-25 02:13:11 WARNING (MainThread) [homeassistant.core] Unable to remove unknown listener <function async_track_point_in_utc_time.<locals>.point_in_time_listener at 0xe98ae8a0>
2020-02-25 03:14:42 WARNING (MainThread) [homeassistant.core] Unable to remove unknown listener <function async_track_point_in_utc_time.<locals>.point_in_time_listener at 0xe9840f60>
2020-02-25 03:16:42 WARNING (MainThread) [homeassistant.core] Unable to remove unknown listener <function async_track_point_in_utc_time.<locals>.point_in_time_listener at 0xe7ac5ae0>
2020-02-25 03:18:12 WARNING (MainThread) [homeassistant.core] Unable to remove unknown listener <function async_track_point_in_utc_time.<locals>.point_in_time_listener at 0xeb0908a0>
2020-02-25 05:56:15 WARNING (MainThread) [homeassistant.core] Unable to remove unknown listener <function async_track_point_in_utc_time.<locals>.point_in_time_listener at 0xeb0dbd20>
2020-02-25 06:27:09 WARNING (MainThread) [homeassistant.core] Unable to remove unknown listener <function async_track_point_in_utc_time.<locals>.point_in_time_listener at 0xe9861780>
2020-02-25 06:28:41 WARNING (MainThread) [homeassistant.core] Unable to remove unknown listener <function async_track_point_in_utc_time.<locals>.point_in_time_listener at 0xe793fe40>

They are there AGAIN :(
It could be because of the short cooldown (just 10ms), or because the lack of lock (#32161), but I'm not sure right now :(
The patch in #32088, with the naive approach of filter some purge schedule, did the trick. I will test some more, as I see more interesting to work with the debouncer

Maybe this is the key to, at least, remove the core warnings:
if self._update_listener:
    if not hasattr(self._update_listener, "run"):
        self._update_listener()
    else:
        _LOGGER.warning("%s: Gotcha, this was going to generate a core warning :)", self.entity_id)
    self._update_listener = None

(print is always the debugger best-friend)

cc @ballob, @exxamalte

And the thing is that with 3 lines of code to wrap the update and call the debouncer instead,
the issue disappears completely, as now the update calls are grouped when these bursts come in.

Sadly, that is not true, only reduces the frequency of warnings raising :(
But I think I've got it, finally.
What is happening?
After a lot of approaches,  I've identified multiple causes for the extra stress that, apparently, the stats sensor is creating in the event bus with the max age purge scheduling.

Burst incoming: sometimes a burst of new samples is received, and for each one the cycle of purge + update + cancel old listener + create new one is repeated.
Schedule repeat: Most times the new schedule matches the last one, or it is very near it, but this is not checked, and instead we cancel + reprogram it.
Periodic overlapping: Most input signals for the stats sensor will have a constant frequency, with period T, and with a max_age = n * T, the scheduled purge of the oldest sample will be called ~almost at the same time than the next incoming sample

All of these are happening in sub-second intervals, while the event bus fires EVENT_TIME_CHANGED only once each second, and only fires EVENT_TIMER_OUT_OF_SYNC if the event is > 1 sec late, so there is a window of max 1 sec where a tick can be a little late and we don't know.
So, this is the only thing I can imagine that it is happening for the issue to appear:

current purge schedule is waiting in 'listener X' set to t=-.7, so tick in t=-1 does not activate it,
a tick with t=0 is fired, and matched 'listener X' gets added for evaluation
'listener X' is called with tick t=0, gets "run" tag, does the unsub, and adds the 'purge job X' to queue,
new sample comes in t=0.5, calling update. As _update_listener is not None, it is canceled, but because it is not there, the warning is generated.
'purge job X' callback is finally called, setting _update_listener to None too late.

This is only my hypothesis, as I've been incapable of reproducing the issue upon request, and every approach worked ok in the dev machine. The 'good thing' is that I'm suffering of this core warning in the home machine, with different frequencies for each approach, so I've been real testing all approaches in that environment (a RPI4_4GB+USB_SSD running hassio 105.5 on docker, editing the files inside the HA container and restarting it)
Along the way I've discovered/validated some things:

All warnings are coming from the stats sensors with max age, for sure.
All unknown listeners have the "run" tag added, so they've been called (or just added the job to queue) in the past, and because of async_unsub(), they have removed the listener.
The timestamp of the lost listeners has ~always a datetime of <1s near the core warning

And I've also made a lot of small changes to try to remove the issue. Finally, I have a working version running for > 14 h without the issue, so I hope it is fixed, with these:
Changes / Optimizations

Debounced call to async_update to handle bursts of incoming samples.
Abort call to update from an incoming sample if a scheduled purge is coming in near future.
Store the last scheduled purge and compare times with new one, to abort re-scheduling to the same (or very similar) future timestamp. Most important optimization by far.
Access to self._update_listener with a lock around (I'm almost sure that this is unnecessary, but current working version has it)
Do not operate in sub-second times: as the HA ticking is of 1 second, (scheduling listeners to HH:MM:SS.6 makes the listener run the callback in 1.0 anyway).
Instead, admit up to 1 second error in the max_age of the sensor (which is very reasonable IMHO), by ceiling the purge scheduled timestamps. This one is where the magic happens :)

Results
To put some numbers on these, here is the evolution of the RPI machine for the last hours:

It shows that ~1/3 of the updates are scheduled purge operations and 2/3 are incoming samples
Yellow area is the number of aborted cancel + re-schedule actions (before the fix those where happening)
Small in comparison, but also important, green area shows the aborted calls to update from incoming samples
The debouncing doesn't appear here, but it's also happening (I did not introduce logging messages in debouncer, so I have no data, but in dev machine I've seen it working with groups of 2 and 3 calls)

Plot notes:

Data comes from /api/error_log after setting stats at debug level, parsing the generated log messages. So far no warnings.
There are 4 stats sensors with max_age from 5 to 15 min, all of them filtering template sensors dependant of 2 to 6 entities each one.
It plots a resample(2min).count(), so a value of 120 means one event per sec.

Logging notes:

I introduced a small hack in async_track_point_in_utc_time to tag the listeners, with:
# Set variable to identify origin (for error logging purposes).
setattr(
    point_in_time_listener,
    "__name__",
    f"{action.__name__}_{point_in_time:%H_%M_%S_%f}",
)

That way I could see the issues like that:
2020-02-26 12:49:41.000 ERROR (MainThread) [homeassistant.core] Unable to remove unknown 'time_changed' listener (there are 113) named '_scheduled_update_11_49_40_000000' (run True)
2020-02-26 13:19:03.025 ERROR (MainThread) [homeassistant.core] Unable to remove unknown 'time_changed' listener (there are 118) named '_scheduled_update_12_19_02_648276' (run True)
2020-02-26 14:03:41.069 ERROR (MainThread) [homeassistant.core] Unable to remove unknown 'time_changed' listener (there are 114) named '_scheduled_update_13_03_40_422252' (run True)
2020-02-26 14:05:41.047 ERROR (MainThread) [homeassistant.core] Unable to remove unknown 'time_changed' listener (there are 116) named '_scheduled_update_13_05_40_342420' (run True)
2020-02-26 14:09:04.028 ERROR (MainThread) [homeassistant.core] Unable to remove unknown 'time_changed' listener (there are 114) named '_scheduled_update_13_09_03_581080' (run True)
2020-02-26 14:12:04.112 ERROR (MainThread) [homeassistant.core] Unable to remove unknown 'time_changed' listener (there are 115) named '_scheduled_update_13_12_03_613611' (run True)
2020-02-26 14:14:34.025 ERROR (MainThread) [homeassistant.core] Unable to remove unknown 'time_changed' listener (there are 116) named '_scheduled_update_13_14_33_059348' (run True)

I'll be pushing the last changes here for review, after rebasing with last changes in debouncer,
and I will update the RPI to 106 to check the original issue is there, and then again with the described patch (maybe without the extra lock, to check that it is not necessary).

I'll be pushing the last changes here for review, after rebasing with last changes in debouncer,

Done

and I will update the RPI to 106 to check the original issue is there, and then again with the described patch (maybe without the extra lock, to check that it is not necessary).

Also done.

Original issue still happens in 106.0 (no surprises)
This fix also works on 106, without extra locks, so I removed it.

@balloob please check https://github.com/home-assistant/home-assistant/pull/32155/commits/476a165bfadbec571f09cb39feae77cd0631f3b6, about the delayed debouncer + tests using hass.block_til_done()


How to use icons dynamically

How can I use dynamic icons in v3?
In my database I have 2 values iconType which holds something like 'Ionicons' or 'MaterialIcons' and iconName which holds the name if the icon.
This is how I did it in v2.
 <Icon
        name={props.iconName}
        type={props.iconType}
/>

Is there any way to also define the as property inside v3 icon with dynamic string values containing the icon type?

Hi @manufunk In v3, you can do something like this. It's a bit verbose but we decided to decouple vector or expo icons in v3. We might add a more simple way so that above syntax is possible. In the meantime, you can do below.
const getComponent = (iconType, iconName) => {
  switch(iconType) {
    case "MaterialIcons":
      return <MaterialIcons name={iconName} />
    case "Ionicons":
      return <Ionicons  name={iconName} />
    default:
      return <MaterialIcons  name={iconName} />
    }
  }

export const Example = ({iconName, iconType}) => {
  const iconComponent = getComponent(iconName, iconType);
  return (
      <Icon as={iconComponent} />
  )
}

Thank you for the hint. I thought maybe there is a nicer solution for this because it could be any type of icon which is a very long list. But I guess for now I will follow your suggestion until there is a more dynamic way. Should I create a feature request for it to have it in the backlog?

A solution similar to above solution works in v3 now. Check third party icons documentation here


Merge master to milestone/4.0.0

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update README.md

I modified the original entry to point to sysdig's monitoring system (versus our open source troubleshooting tool). This seemed to more closely match the other systems in the section (eg prometheus and datadog).

[Insert the URL to be listed]
[Explain what the project is about and why it should be listed]
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines

The project submitted conforms to the quality standards outlined in the contribution guidelines

Go to the contribution guidelines and read it again.

RULES (because you probably didn't read the guidelines):
Links will be tested with awesome_bot. Please make sure your URL to be listed is unique (do some search queries), otherwise put a link at the end of README.md file.

FORMAT

Use the following format: [Name](Link) - Description.
[Name] should be the title of the project
(Link) should be pointing to a GitHub repository, not to a website
Description. should end with a full stop/period
For GitHub repositories, add the name of the author with a link to its GitHub account after the description, like By [@author](GitHub account)

ORDER: The entries are in lexical order (English letter order)
LABEL (Optional): Add one of the following icons next to the project name like [Name](Link) :icon: - Description.

:heavy_dollar_sign: indicates if one needs a paying subscription to use the project.
:construction: indicates that the project is a work in progress/beta release.
:skull: indicates that the project is obsolete, but still worth mentioning it.

Hi @Moshe-Immerman thanks for the comment.
No the open source version of sysdig is still available. I couldn't quite figure out where to put it - it's not a monitoring tool but rather a troubleshooting tool so doesn't fit in the current category. I planned to do a separate PR to bring it in. Any suggestions where to put it?
Also - regarding the heavy $ I noticed none of the other vendors have it in the monitoring section (assuming because it's called out up top) - more fuel to the fire that the open source sysdig tool belongs elsewhere.
I'll tone down the language on the commercial tool and we can at least get that merged.

@apurvadave If you see any entry that is missing the 💲 , we would be grateful for a quick PR!
Highly appreciated

Waiting too long

Apologies I missed this entirely. I'll reopen and resolve it in a timely fashion
Sent from my iPhone

On Feb 22, 2018, at 1:17 AM, Julien Bisconti<EMAIL_ADDRESS>wrote:
Waiting too long
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@apurvadave ping

@veggiemonk just submitted for Sysdig URL. I'll do another PR to bring open source sysdig back.


Remove Istio ambient compatibility blurb

Currently the Istio integration page states the following:

The new experimental ambient mesh data plane is not supported, as it interferes with the Cilium data plane.

As of Istio release 1.21, this is no longer accurate, so removed that  blurb and lightly reworked other bits of the doc.

@bleggett CI is failing due to:
ERROR:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Daniel Hawton<EMAIL_ADDRESS>
@dhawton will need to sign off. Since all the changes are related to docs, maintainers may also want you to squash into a single commit.

@bleggett CI is failing due to:
ERROR:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Daniel Hawton<EMAIL_ADDRESS>
@dhawton will need to sign off. Since all the changes are related to docs, maintainers may also want you to squash into a single commit.

Fair enough, forgot cilium doesn't autosquash on merge.
Manually squashed, should fix the signoff lint too, I think?

Change LGTM but I think that the commit message for 4a783d3 is long enough that it's making the BPF Checks CI entry fail. I'd recommend truncating to just Add a separate section for the Istio + Cilium demo for ambient.

Change LGTM but I think that the commit message for 4a783d3 is long enough that it's making the BPF Checks CI entry fail. I'd recommend truncating to just Add a separate section for the Istio + Cilium demo for ambient.

resquashed, ty!

/test

/test

ty!


Added tests for VesselStatusMessageParams.ts

Description

Added VesselStatusMessageParams.test.ts file in src/vessel-charging/messages.
Fixes Issue #30
Related Issue

#31
Motivation and Context

The test file checks whether the serialize and deserialize methods work as it should.
How Has This Been Tested?

I executed npm run jest and made sure my code was not breaking.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Closes #30
Thank you once more @sark01
Looks great 👍


Move the main module to the one we plan to name as core in order to continue evolving the project in the future.

Remove headers from the original source code files as well


Template DisableEmailUserNameValidation property to carbon.xml.j2

Resolves partially https://github.com/wso2/product-is/issues/10760
Purpose
$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/981695859

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/981695859
Status: failure


TypeError: 'Serialize' object is not subscriptable when reading parquet dataset with Client(processes=False).

What happened*:
When computing on a Parquet dataset (e.g. .get_partition(0).compute()) with a scheduler created with Client(processes=False), I see a an exception
distributed.worker - WARNING - Compute Failed
Function:  subgraph_callable-5a6fa5b8-3068-4bcd-be9e-0c62ca98
args:      (<Serialize: {'piece': ('/mnt/c/Users/taugspurger/timeseries.parquet/part.0.parquet', [0], [])}>)
kwargs:    {}
Exception: TypeError("'Serialize' object is not subscriptable")

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-8-ef0b428efc40> in <module>
----> 1 df.get_partition(0).compute()

~/src/dask/dask/dask/base.py in compute(self, **kwargs)
    284         dask.base.compute
    285         """
--> 286         (result,) = compute(self, traverse=False, **kwargs)
    287         return result
    288

~/src/dask/dask/dask/base.py in compute(*args, **kwargs)
    566         postcomputes.append(x.__dask_postcompute__())
    567
--> 568     results = schedule(dsk, keys, **kwargs)
    569     return repack([f(r, *a) for r, (f, a) in zip(results, postcomputes)])
    570

~/src/dask/distributed/distributed/client.py in get(self, dsk, keys, workers, allow_other_workers, resources, sync, asynchronous, direct, retries, priority, fifo_timeout, actors, **kwargs)
   2754                     should_rejoin = False
   2755             try:
-> 2756                 results = self.gather(packed, asynchronous=asynchronous, direct=direct)
   2757             finally:
   2758                 for f in futures.values():

~/src/dask/distributed/distributed/client.py in gather(self, futures, errors, direct, asynchronous)
   2031             else:
   2032                 local_worker = None
-> 2033             return self.sync(
   2034                 self._gather,
   2035                 futures,

~/src/dask/distributed/distributed/client.py in sync(self, func, asynchronous, callback_timeout, *args, **kwargs)
    864             return future
    865         else:
--> 866             return sync(
    867                 self.loop, func, *args, callback_timeout=callback_timeout, **kwargs
    868             )

~/src/dask/distributed/distributed/utils.py in sync(loop, func, callback_timeout, *args, **kwargs)
    324     if error[0]:
    325         typ, exc, tb = error[0]
--> 326         raise exc.with_traceback(tb)
    327     else:
    328         return result[0]

~/src/dask/distributed/distributed/utils.py in f()
    307             if callback_timeout is not None:
    308                 future = asyncio.wait_for(future, callback_timeout)
--> 309             result[0] = yield future
    310         except Exception:
    311             error[0] = sys.exc_info()

~/miniconda3/envs/dask-dev/lib/python3.8/site-packages/tornado/gen.py in run(self)
    760
    761                     try:
--> 762                         value = future.result()
    763                     except Exception:
    764                         exc_info = sys.exc_info()

~/src/dask/distributed/distributed/client.py in _gather(self, futures, errors, direct, local_worker)
   1896                             exc = CancelledError(key)
   1897                         else:
-> 1898                             raise exception.with_traceback(traceback)
   1899                         raise exc
   1900                     if errors == "skip":

~/src/dask/dask/dask/optimization.py in __call__(self, *args)
    967         if not len(args) == len(self.inkeys):
    968             raise ValueError("Expected %d args, got %d" % (len(self.inkeys), len(args)))
--> 969         return core.get(self.dsk, self.outkey, dict(zip(self.inkeys, args)))
    970
    971     def __reduce__(self):

~/src/dask/dask/dask/core.py in get(dsk, out, cache)
    149     for key in toposort(dsk):
    150         task = dsk[key]
--> 151         result = _execute_task(task, cache)
    152         cache[key] = result
    153     result = _execute_task(out, cache)

~/src/dask/dask/dask/core.py in _execute_task(arg, cache, dsk)
    119         # temporaries by their reference count and can execute certain
    120         # operations in-place.
--> 121         return func(*(_execute_task(a, cache) for a in args))
    122     elif not ishashable(arg):
    123         return arg

~/src/dask/dask/dask/dataframe/io/parquet/core.py in __call__(self, part)
     89             self.engine,
     90             self.meta,
---> 91             [(p["piece"], p.get("kwargs", {})) for p in part],
     92             self.columns,
     93             self.index,

~/src/dask/dask/dask/dataframe/io/parquet/core.py in <listcomp>(.0)
     89             self.engine,
     90             self.meta,
---> 91             [(p["piece"], p.get("kwargs", {})) for p in part],
     92             self.columns,
     93             self.index,

TypeError: 'Serialize' object is not subscriptable

Minimal Complete Verifiable Example:
In [1]: import dask.datasets

In [2]: import dask.dataframe as dd

In [3]: from distributed import Client
In [4]: dask.datasets.timeseries().to_parquet("timeseries.parquet")

In [5]: from distributed import Client

In [6]: client = Client(processes=False)

In [7]: df = dd.read_parquet("timeseries.parquet")

In [8]: df.get_partition(0).compute()

Anything else we need to know?:
It only occurs with processes=False. With the default of processes=True, things are fine.
Environment:
I've tried with dask / distributed 2021.7.2 and main. I've reproduced this with pyarrow 4.0.0 and 5.0.0.
cc @rjzamora if you have any immediate thoughts.

You are exactly right that the culprit is processes=False - This is a known issue that has proven difficult to resolve.  Note that the fine-grained seriealization work from @madsbk would fix this, but I'm not sure what the status is on that front.

Thanks. I'll close this then, if it's a know issue.


ref(docs): update to run/deploy via OCI

Updates the deployment mechanism of this website (GH workflow and nomad job) to use OCI
Updates the docs spin.toml manifest with minimal naming updates necessary for using Spin v2 (see https://github.com/fermyon/spin/pull/2118 for a follow-up to fully convert to v2 manifest syntax)

TODO:

[x] Test run from this branch -> https://github.com/fermyon/spin/actions/runs/7039475395

Ready for review (identical pattern to refactor in https://github.com/fermyon/bartholomew/pull/185).
I'll remove the testing lines in deploy.yml prior to merge.


Multi-file: Runtime error spans are incorrectly mapped to source files

The bug exists in run() in the wasm layer. When the runtime error contains a span, and the span is coming from a file in the program that's not the first one, the wrong span is reported.
I don't think this span is used in the UX anywhere but since it's such a general function it may bite us in the future if we decide to surface these spans.

I need to see if this is still happening after all of the multi-file changes. Assigning myself.


CLI Needs A list option

As far as I can tell, there is no way to see which ignite packages are currently installed. Now that my app is gearing up for release, I would like to remove the ignite packages that I didn't end up using, but I don't know what they are.
Should there be an ignite list command added?

I agree @johndanek . Thanks!

In the meantime, a good way to see all installed Ignite packages is yarn list | grep 'ignite-'.

There is already a ignite list command though. Any idea what word to use instead? @jamesgeorge007

@adrianhartanto0 We could show which ones are currently installed by highlighting them and adding [installed], or put them in a separate section of the output.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Handle 404 errors in Router

We can move 404 errors handling to the Router class in order to gain in code readability as 404 errors handling can be the responsability of the Router.

So, we can move some code from outside class X to inside it, because we can ... Sure, we can, but why should we?

I propose this change for three reasons :
Increase the readability of the CodeIgniter.php file :
CodeIgniter.php is pretty easy to read and allow a quick understanding of the application flow, however 404 errors handling take an important part the class.
Here is a quick pastebin ( https://pastebin.com/LhUi4eUK ), 404 errors handling is from line 100 to 175 so we have (75 / 191) * 100 = 39.2% of the code.
Decrease in code complexity :
The current code handling 404 errors can be divided in two parts : the first one check if a controller for the request exists, then the second one check if a custom 404 controller exists.
I propose to divide these two parts in two separate functions in the Router component to get shorter units of code, respectively controller_exists() and handle_404_override().
Also I noticed a strange behaviour with the sharing of the '$e404' boolean variable between these two parts.
In the current code we have $e404 = FALSE when a custom 404 controller is loaded which can be confusing since we are still loading a 404 error page.
I replaced this $e404 boolean respectively with '$controller_exists' and '$overriden_404' boolean variables in controller_exists() and handle_404_override() functions.
Gain in encapsulation and cohesion :
All the routing responsibilities are grouped in the Router component.
Let me know what you think regarding this proposal

Eh ... Sorry, but really you're just moving stuff around.


[System] Add a raspberry pi howto

Update the document at here:
https://github.com/BUPT/cad-board/wiki/Raspberry-Pi-Howto

@linyimin-bupt You are fast!
But please leave a reply with comments before you close an issue in the future, thanks.

OK.


Files set to open with Visual Studio code have no Icon in File Explorer when in Details view

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: Version: 1.59.1
OS Version: Windows_NT x64 10.0.19043

Steps to Reproduce:

Install Visual Studio Code
Set a file type to be opened with VS Code
Set view type in File Explorer to Details

Doing a fresh install of VS code seems to have removed this issue. I believe it could be caused by not selecting the install option to register common file types with VS code, although I haven't bothered to test if that was the case.
I guess the expected behavior would be to have a generic icon for files to open with VS code (I.E. the VS Code logo) if a file type is added manually (open with dialog) and not via the installer option

Was this fixed or did you just close it because?


Add TempoWorld API to Control Actors

Adds actor control API to TempoWorld, which can spawn, move, and destroy actors, as well as set their properties with a generic reflection-based mechanism.

Closing temporarily to add:

Set component transform
Add/Remove component

And investigate issues:

Spawned actor name is not always correct
Segfault when actor or component does not exist


added test case for dashboardConfig

Closes: https://issues.redhat.com/browse/RHOAIENG-2118
Description
Added test case for frontend/api/k8s/dashboardConfig file

How Has This Been Tested?
npm run test

Test Impact
test coverage :

Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/lgtm
/approve


Types missing from v1.9.0

Hey! The types are broken in the new 1.9.0, because now that tests exists, TypeScript is generating the types at build/types/src/* instead of build/types/*:
https://unpkg.com/browse/<EMAIL_ADDRESS>

<EMAIL_ADDRESS>has been published. Please try it.

It works! 🎉 Thanks for the fast turnaround


clarification about output

Hii @p-ranav
thank so much for sharing your amazing work
i wanted to know what output image represents, is it representing absolute depth or anything proportional to absolute depth?
what are the values in average_depth in infer.py represent?
if i want to get the absolute depth how can i get that
Thank you

It is intended to be absolute depth in meters. Some of the depth predictions (e.g., MiDaS) are not absolute but instead relative depth (https://github.com/intel-isl/MiDaS/issues/37).


Add option to save workspace

From #161: "yeah, i think we should add a cli option, maybe --save-workspace, and include the .viv file generation in hardcore mode."

closed in #176


[SDP-702]: Add the privacy_policy_link to the organization database and serve it in a model

What
Add a column in the organization database called privacy_policy_link, and support it in the organization’s payloads (GET, PATCH)
Why
Each tenant org will have a different privacy policy.
Known limitations
N/A
Checklist
PR Structure

[x] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR title and description are clear enough for anyone to review it.
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[ ] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr247.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr247.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr247.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr247.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr247.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr247.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr247.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr247.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr247.previews.kube001.services.stellar-ops.com


separate out electrumx settings into json config file (to facilitate overwriting this file in docker)

solved in different way.


Cache type inference details in a .nixi file

Once #105 is done, we'd like to cache type information learned about the contents of file, so the symbolic evaluator can load this information when it encounters an import statement (this will require introducing at least the file reading effect into that evaluator).

This is waiting on #105


I want to add free courses from Coursera , can I add it?

https://www.coursera.org/courses?query=free

only technical courses


Unable to run hello_world example

Describe the Bug
Hi! I am new and unable to run the hello_world example. I wonder if I have set up something with the rust devtools incorrectly.
Steps to Reproduce

Clone this repo
Open the hello_world example dir
Run npm i
Run npm run serve
See error

Expected Behavior
The hello world example served via local HTTP server
Actual Behavior
it looks like the Rust project used to create this wasm file was linked against
version of wasm-bindgen that uses a different bindgen format than this binary:

  rust wasm file schema version: 0.2.84 (b41de3f22)
     this binary schema version: 0.2.84

Currently the bindgen format is unstable enough that these two schema versions
must exactly match. You can accomplish this by either updating the wasm-bindgen
dependency or this binary.

You should be able to update the wasm-bindgen dependency with:

    cargo update -p wasm-bindgen

or you can update the binary with

    cargo install -f wasm-bindgen-cli

if this warning fails to go away though and you're not sure what to do feel free
to open an issue at https://github.com/rustwasm/wasm-bindgen/issues!

running either cargo update -p wasm-bindgen or cargo install -f wasm-bindgen-cli --version 0.2.84 did not help
Additional Context
$ wasm-pack -V
wasm-pack 0.11.0
$ rustc -V
rustc 1.68.0 (2c8cc3432 2023-03-06)
$ wasm-bindgen -V
wasm-bindgen 0.2.84

This is a known issue. It's happening because wasm-pack is attempting to use the released v0.2.84 version of the wasm-bindgen CLI with the git version of the #[wasm_bindgen] macro, and there have been breaking changes to the internal protocol between them since v0.2.84 was released, making them incompatible.
To work around it, you can either switch to the state of this repo as of when v0.2.84 was released with git checkout v0.2.84, so that both the CLI and macro are at version 0.2.84, or you can build a git version of the CLI and add it to PATH so that wasm-pack can use it:
cargo build --release -p wasm-bindgen-cli
export PATH="$PWD/target/release:$PATH"

Thank you! Running git checkout 0.2.84 and rebuilding did get rid of the error. Although, now I am running into a separate issue I can open another thread for.


无法获取

flutter_resource_generator any which doesn't exist (could not find package flutter_resource_generator at https://pub.flutter-io.cn), version solving failed.

https://pub.flutter-io.cn/packages/flutter_asset_generator
I don't know your means.

This is the code I wrote when I first used flutter.
Later I will rewrite this in the form of pub global instead of build_runner.

国内的镜像有时会出现问题, 请使用官方镜像源下载.
Domestic mirrors sometimes have problems, please use the official mirror source to download.
mac or linux:
unset FLUTTER_STORAGE_BASE_URL
unset PUB_HOSTED_URL
windows:
System=>environment variables

Update version to 0.4.0.
Try to use it with pub global.


Test Resource scripts set environment-specific service version variables

Some cloud environments may have service versions which are different from that of the public cloud. Since these configurations exist at the level of the environment (not subscription) we should make use of an environment configuration which enables us to set service version environment variables.

Solved.  We have cases where people are already doing this.


rerun notebook, to make output correct

The pushed notebook had a mixed up cell execution order, such that an error occured.
This PR fixes the displaying of all cells.

bors merge


Expand default props to include canvas props

I was having an issue because I wanted to pass props like className and style into the canvas that's inside the default component.  It can technically be done from a code level because of the use of ...rest from the props, but Typescript complains because BabylonjsProps doesn't include them.
Rather than including them explicitly, I thought it would be easier and more accessible for other people's use cases to include all the the valid props for a typical canvas element.
The first commit (67d47f8) just removes extra whitespace.  My editor did that.
The second commit (b6980c1) removes some assertions that ts-lint was complaining about.  According to the types, scene.getEngine() can only return an instance of Engine.  It doesn't appear to be Nullable, so I think this is okay.
The third commit (00a36f1) adds the extra props to the default component.
Please let me know if there's anything more I should do to get this ready for merging.  Thank you!

I am a little concerned about https://github.com/brianzinn/babylonjs-hook/commit/b6980c18acb70457cb77559c90dace016331b4fd.  I think it's either valid for those assertions to be there and there should be an exception there for the linter, or they should be replaced with scene.getEngine()?.getRenderingCanvas()!; to handle the undefined case.  I've tested it with scene.getEngine()?.getRenderingCanvas()!; and the linter is okay with it.  What do you think, @brianzinn?

Thanks @JayAndCatchFire - that is a great addition that improves typings support and makes it much better to discover the available props.  Should be available in 0.0.11!  I didn't test it out myself, but it looks perfect.  Cheers.

I'll try to switch the project over to eslint and see what kind of warnings are shown.  Thanks also for bringing that up :)


Property setters are not included in sphinx autodoc

The docstrings of property setters are ignored by sphinx autodoc, only possible 'solution' I've found is:
https://stackoverflow.com/questions/71713284/types-of-setter-arguments-not-showing-in-sphinx-documentation

Only getters are documented - so probably should include the docstring info for setting in the getters


Docs: Providing docs for opening a new modal and closing the current one

{{ Bootstrap 4: Docs }} , Path => /components/modal/
Please add documentation on opening an another modal and closing the current one when a link is clicked as its done without any extra code efforts, via
  Next >
JS Fiddle: http://jsbin.com/hujipi/edit?html,output
This is happening as i am calling both data toggle and data dismiss at the same time, so i felt it should be in the documentation too. As always, rest on you guys to decide :smile_cat:

Awaiting reply @mdo

Such solution has a bug with modal-open body class. But it would be nice it working)

Still love you guys but passing on this and closing!


shovel: bugfix. negative int256 values

It might be possible to not wrap uint256.Int with the negInt struct: https://github.com/holiman/uint256/issues/175