🐛 Enabling video causes black flash freeze issue

What were you trying to do?
When I enable video on the Camera component the screen freezes for a moment and turns dark
Is this expected?
Thanks
Reproduceable Code
    <ReanimatedCamera
	ref={camera}
	style={StyleSheet.absoluteFill}
	device={device}
	isActive={true}
	photo={true}
	video={true}
	audio={hasMicrophonePermission}

What happened instead?
I expect the video to continue smoothly instead of freezing and turning black
Relevant log output
No response
Device
iPhone 12 Mini
VisionCamera Version
^2.10.0
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Uploading RPReplay_Final1640221860.mov…
Here is a video recording of it happening

why did you not fill out the "Relevant Log Output" field?

Hold on, do you mean it freezes for a second and works again afterwards, or does it not work anymore? Not clear to me

@mrousavy it works afterwards fine ! It's just freezes momentarily. It's not a huge issue but doesn't seem ideal. Does this happen to you? It's pretty easy repo on mine. I just set video = true. It's a little laggy when switching front / back cameras as well. I just wanted to check if this was expected I assumed others have seen this ?
I can post additional logs if that helps but didn't notice any output.

lol no that's how cameras work

just leave video on if it's an issue for you 🤷♂
you can see the same behaviour in any Camera app if you switch from photo to video

@mrousavy what are you talking about? Look at the video I posted, that is not how "every camera works" are you serious? Launch the default camera app it does not freeze for a second and turn black

@mrousavy I think you are confused. Video is left on. I'm not toggling video on/off. This is with 'video=true' always. On launch the video freezes and turns black. Look at the video I posted, this is not normal camera behaviour at all.

https://user-images.githubusercontent.com/775808/147415343-10f1af76-8f90-48b2-a517-dbd5adb1c0b4.mov
Here is a video of launching the app with 'video=true' no switching anything. Notice how it freezes and turns black momentarily?

are you serious? why did you not explain it better then?
in all seriousness - share me the logs (like I already said three comments ago) and I can take a look.
But I am sure you are changing the formats or enabling/disabling a field that reconfigures the camera on the fly - otherwise this would not happen.

and share the full component without leaving anything out.

@mrousavy thanks, and sorry I wasn't very clear. Here is a full example with logs
Example:
/**
 * Sample React Native App
 * https://github.com/facebook/react-native
 *
 * Generated with the TypeScript template
 * https://github.com/react-native-community/react-native-template-typescript
 *
 * @format
 */
import React from 'react';
import { StyleSheet, View } from 'react-native';
import { Camera, useCameraDevices } from 'react-native-vision-camera';

const App = () => {
	const devices = useCameraDevices();

	const device = devices.back;

	if (device == null) return null;

	return (
		<View style={styles.container}>
			<Camera
				style={StyleSheet.absoluteFill}
				device={device}
				isActive={true}
				enableZoomGesture={false}
				photo={true}
				video={true}
			/>
		</View>
	);
};

const styles = StyleSheet.create({
	container: {
		flex: 1,
		// backgroundColor: 'blue',
	},
});

export default App;

Logs:
flipper: FlipperClient::addPlugin Inspector
flipper: FlipperClient::addPlugin Preferences
flipper: FlipperClient::addPlugin React
flipper: FlipperClient::addPlugin Network
2021-12-27 09:27:05.416424-0700 CameraVisionTest[456:15649] [native] Running application CameraVisionTest ({
    initialProps =     {
    };
    rootTag = 1;
})
2021-12-27 09:27:05.444661-0700 CameraVisionTest[456:15886] FrameProcessorBindings: Creating Runtime Manager...
2021-12-27 09:27:05.445489-0700 CameraVisionTest[456:15886] FrameProcessorBindings: Runtime Manager created!
2021-12-27 09:27:05.445510-0700 CameraVisionTest[456:15886] FrameProcessorBindings: Installing Frame Processor plugins...
2021-12-27 09:27:05.445524-0700 CameraVisionTest[456:15886] FrameProcessorBindings: Frame Processor plugins installed!
2021-12-27 09:27:05.445606-0700 CameraVisionTest[456:15907] FrameProcessorBindings: Installing Frame Processor Bindings for Bridge...
2021-12-27 09:27:05.445779-0700 CameraVisionTest[456:15907] FrameProcessorBindings: Installing global functions...
2021-12-27 09:27:05.445840-0700 CameraVisionTest[456:15907] FrameProcessorBindings: Finished installing bindings.
2021-12-27 09:27:09.108403-0700 CameraVisionTest[456:15907] [javascript] Running "CameraVisionTest" with {"rootTag":1,"initialProps":{}}
2021-12-27 09:27:09.170417-0700 CameraVisionTest[456:15649] [native] VisionCamera.didSetProps(_:): Updating 15 prop(s)...
2021-12-27 09:27:09.170507-0700 CameraVisionTest[456:15882] [native] VisionCamera.configureCaptureSession(): Configuring Session...
2021-12-27 09:27:09.170573-0700 CameraVisionTest[456:15882] [native] VisionCamera.configureCaptureSession(): Initializing Camera with device com.apple.avfoundation.avcapturedevice.built-in_video:6...
2021-12-27 09:27:09.170589-0700 CameraVisionTest[456:15882] [native] VisionCamera.configureCaptureSession(): Adding Video input...
2021-12-27 09:27:09.215747-0700 CameraVisionTest[456:15886] [connection] nw_socket_handle_socket_event [C5:1] Socket SO_ERROR [61: Connection refused]
2021-12-27 09:27:09.215926-0700 CameraVisionTest[456:15881] [connection] nw_connection_get_connected_socket [C5] Client called nw_connection_get_connected_socket on unconnected nw_connection
2021-12-27 09:27:09.215955-0700 CameraVisionTest[456:15881] TCP Conn 0x2814fcdc0 Failed : error 0:61 [61]
2021-12-27 09:27:09.223079-0700 CameraVisionTest[456:15882] [native] VisionCamera.configureCaptureSession(): Adding Photo output...
2021-12-27 09:27:09.226491-0700 CameraVisionTest[456:15882] [native] VisionCamera.configureCaptureSession(): Adding Video Data output...
2021-12-27 09:27:09.226927-0700 CameraVisionTest[456:15882] [native] VisionCamera.invokeOnInitialized(): Camera initialized!
2021-12-27 09:27:09.226995-0700 CameraVisionTest[456:15882] [native] VisionCamera.configureCaptureSession(): Session successfully configured!
2021-12-27 09:27:09.227586-0700 CameraVisionTest[456:15882] [native] VisionCamera.configureFormat(): Configuring Format...
2021-12-27 09:27:09.227592-0700 CameraVisionTest[456:15882] [native] VisionCamera.configureDevice(): Configuring Device...
2021-12-27 09:27:09.227623-0700 CameraVisionTest[456:15882] [native] VisionCamera.configureDevice(): Device successfully configured!
2021-12-27 09:27:09.227738-0700 CameraVisionTest[456:15882] [native] VisionCamera.didSetProps(_:): Starting Session...
2021-12-27 09:27:09.901664-0700 CameraVisionTest[456:15882] [native] VisionCamera.didSetProps(_:): Started Session!

Recording:
https://user-images.githubusercontent.com/775808/147490213-3c7c3207-0361-496d-9e66-b3d8606a7e80.mov
Notice how when it launches the video feed is dark and freezes momentarily. I'm really just curious if this is expected. If in the component I set video = false it works as expected (no freeze, or dark) but in the example both are set to true so I assume that should be fine to do?
This happens on a release build for me as well
Again, thanks for your help, love all your work and repos :)

Okay from your logs it looks like it is correctly only starting the session once, not sure why there is a flicker here then. Maybe that's really just the behaviour of the Triple-Camera you are using here because it has to initialize in serial and the queue is blocked by the other 2 cameras then?

@mrousavy ah that could be, I have a few other devices laying around. I'll test around on them a bit.
Can you think of any workaround I could do or something I could look into?

You can use a single camera device instead of the triple camera, that should definitely initialize faster. (useCameraDevices('wide-angle'))

@mrousavy oh got it, amazing thanks so much for your help. Working very smooth now :)


The app ID "com.example.myapp" cannot be registered to your development team. Change your bundle identifier to a unique string to try again.

I am not able to connect my apple ID with Xcode. Any ideas on how to solve this issue ??
Also in my iPhone, I am not able to locate General > Device Management. Did anyone have the same problem ?
Thanks
Kumuda

Enter a different bundle identifier.

I tried different bundle identifier but it does not work.

Which one? It must be unique. E.g. com.kumuda123.example or something like that.
What error do you get?

My phone is connected to my laptop.

Can you run it on an emulator?
Btw this is in no way an error of the flutter project. You might want to find solutions over at stackoverflow.com.

Yes i can run it on the Simulator. Also how should I open main.dart ? Whenever i open, it gives me this error.

There are several tutorial videos over at youtube that can help you setup a flutter project.

I don't think there's a bug to track here.  The error is coming from Xcode, and the error message is pretty clear about what to do.  Seems like a setup issue covered on stackoverflow.

what is unique ID
Give me an example
tsk

@huyvuro Flutter didn't generate this error.  Feel free to file an issue with Apple https://feedbackassistant.apple.com


Strange undefined logging in Output

My output for GHPRI has these log messages:

I'm on today's insiders with Pre-release GitHub Pull Requests and Issues and I still see these:

Versions:


AWS EC2 Executor Planning

Acceptance Criteria
A design document that should outline:

Proposal of how new & existing [cloud] executors should change in order to support new hooks during the workflow lifecycle in order to provision cloud resources programatically via Terraform CDK
How this affects the plugin ecosystem (organization of plugins within Git and pip deployments)
How automated testing should be performed on executors

Additional requirements:

All terraform infrastructure code should live in the AgnostiqHQ/terraform repo, and in a seperate mono repo AgnostiqHQ/cloud-executors. Therefore there should be a mapping from a cloud executor and a folder under AgnostiqHQ/terraform

The related discussion for this issue is #893


resolving a conflict due to reformatting

Thanks @DaanHoogland
FYI this was the conflict after fwd-merge:
rbergsma[~/git/apache/cloudstack](master)$ git diff
diff --cc engine/orchestration/src/org/apache/cloudstack/engine/orchestration/NetworkOrchestrator.java
index fa6cd82,5f442b3..0000000
--- a/engine/orchestration/src/org/apache/cloudstack/engine/orchestration/NetworkOrchestrator.java
+++ b/engine/orchestration/src/org/apache/cloudstack/engine/orchestration/NetworkOrchestrator.java
@@@ -168,8 -167,8 +168,9 @@@ import com.cloud.user.Account
  import com.cloud.user.ResourceLimitService;
  import com.cloud.user.User;
  import com.cloud.user.dao.AccountDao;
+ import com.cloud.utils.NumbersUtil;
  import com.cloud.utils.Pair;
 +import com.cloud.utils.UuidUtils;
  import com.cloud.utils.component.AdapterBase;
  import com.cloud.utils.component.ManagerBase;
  import com.cloud.utils.concurrency.NamedThreadFactory;
@@@ -1025,12 -1021,9 +1029,12 @@@ public class NetworkOrchestrator extend
              _networksDao.update(network.getId(), network);
              implemented.set(guru, network);
              return implemented;
-         } catch (NoTransitionException e) {
+         } catch (final NoTransitionException e) {
              s_logger.error(e.getMessage());
              return null;
 +        } catch (CloudRuntimeException e) {
 +            s_logger.error("Caught exception: " + e.getMessage());
 +            return null;
          } finally {
              if (implemented.first() == null) {
                  s_logger.debug("Cleaning up because we're unable to implement the network " + network);
@@@ -1922,35 -1915,33 +1926,65 @@@
                  throw new InvalidParameterValueException("The VLAN tag " + vlanId + " is already being used for dynamic vlan allocation for the guest network in zone "
                          + zone.getName());
              }
++<<<<<<< HEAD
 +            if (! UuidUtils.validateUUID(vlanId)){
 +                String uri = BroadcastDomainType.fromString(vlanId).toString();
 +                // For Isolated networks, don't allow to create network with vlan that already exists in the zone
 +                if (ntwkOff.getGuestType() == GuestType.Isolated) {
 +                    if (_networksDao.countByZoneAndUri(zoneId, uri) > 0) {
 +                        throw new InvalidParameterValueException("Network with vlan " + vlanId + " already exists in zone " + zoneId);
 +                    } else {
 +                        List<DataCenterVnetVO> dcVnets = _datacenterVnetDao.findVnet(zoneId, vlanId.toString());
 +                        //for the network that is created as part of private gateway,
 +                        //the vnet is not coming from the data center vnet table, so the list can be empty
 +                        if (!dcVnets.isEmpty()) {
 +                            DataCenterVnetVO dcVnet = dcVnets.get(0);
 +                            // Fail network creation if specified vlan is dedicated to a different account
 +                            if (dcVnet.getAccountGuestVlanMapId() != null) {
 +                                Long accountGuestVlanMapId = dcVnet.getAccountGuestVlanMapId();
 +                                AccountGuestVlanMapVO map = _accountGuestVlanMapDao.findById(accountGuestVlanMapId);
 +                                if (map.getAccountId() != owner.getAccountId()) {
 +                                    throw new InvalidParameterValueException("Vlan " + vlanId + " is dedicated to a different account");
 +                                }
 +                                // Fail network creation if owner has a dedicated range of vlans but the specified vlan belongs to the system pool
 +                            } else {
 +                                List<AccountGuestVlanMapVO> maps = _accountGuestVlanMapDao.listAccountGuestVlanMapsByAccount(owner.getAccountId());
 +                                if (maps != null && !maps.isEmpty()) {
 +                                    int vnetsAllocatedToAccount = _datacenterVnetDao.countVnetsAllocatedToAccount(zoneId, owner.getAccountId());
 +                                    int vnetsDedicatedToAccount = _datacenterVnetDao.countVnetsDedicatedToAccount(zoneId, owner.getAccountId());
 +                                    if (vnetsAllocatedToAccount < vnetsDedicatedToAccount) {
 +                                        throw new InvalidParameterValueException("Specified vlan " + vlanId + " doesn't belong" + " to the vlan range dedicated to the owner "
 +                                                + owner.getAccountName());
 +                                    }
++=======
+             final String uri = BroadcastDomainType.fromString(vlanId).toString();
+             // For Isolated networks, don't allow to create network with vlan that already exists in the zone
+             if (ntwkOff.getGuestType() == GuestType.Isolated) {
+                 if (_networksDao.countByZoneAndUri(zoneId, uri) > 0) {
+                     throw new InvalidParameterValueException("Network with vlan " + vlanId + " already exists in zone " + zoneId);
+                 } else {
+                     final List<DataCenterVnetVO> dcVnets = _datacenterVnetDao.findVnet(zoneId, vlanId.toString());
+                     //for the network that is created as part of private gateway,
+                     //the vnet is not coming from the data center vnet table, so the list can be empty
+                     if (!dcVnets.isEmpty()) {
+                         final DataCenterVnetVO dcVnet = dcVnets.get(0);
+                         // Fail network creation if specified vlan is dedicated to a different account
+                         if (dcVnet.getAccountGuestVlanMapId() != null) {
+                             final Long accountGuestVlanMapId = dcVnet.getAccountGuestVlanMapId();
+                             final AccountGuestVlanMapVO map = _accountGuestVlanMapDao.findById(accountGuestVlanMapId);
+                             if (map.getAccountId() != owner.getAccountId()) {
+                                 throw new InvalidParameterValueException("Vlan " + vlanId + " is dedicated to a different account");
+                             }
+                             // Fail network creation if owner has a dedicated range of vlans but the specified vlan belongs to the system pool
+                         } else {
+                             final List<AccountGuestVlanMapVO> maps = _accountGuestVlanMapDao.listAccountGuestVlanMapsByAccount(owner.getAccountId());
+                             if (maps != null && !maps.isEmpty()) {
+                                 final int vnetsAllocatedToAccount = _datacenterVnetDao.countVnetsAllocatedToAccount(zoneId, owner.getAccountId());
+                                 final int vnetsDedicatedToAccount = _datacenterVnetDao.countVnetsDedicatedToAccount(zoneId, owner.getAccountId());
+                                 if (vnetsAllocatedToAccount < vnetsDedicatedToAccount) {
+                                     throw new InvalidParameterValueException("Specified vlan " + vlanId + " doesn't belong" + " to the vlan range dedicated to the owner "
+                                             + owner.getAccountName());
++>>>>>>> 4.7
                                  }
                              }
                          }
@@@ -2051,14 -2042,7 +2085,18 @@@

                  if (vlanIdFinal != null) {
                      if (isolatedPvlan == null) {
++<<<<<<< HEAD
 +                        URI uri = null;
 +                        if (UuidUtils.validateUUID(vlanIdFinal)){
 +                            //Logical router's UUID provided as VLAN_ID
 +                            userNetwork.setVlanIdAsUUID(vlanIdFinal); //Set transient field
 +                        }
 +                        else {
 +                            uri = BroadcastDomainType.fromString(vlanIdFinal);
 +                        }
++=======
+                         final URI uri = BroadcastDomainType.fromString(vlanIdFinal);
++>>>>>>> 4.7
                          userNetwork.setBroadcastUri(uri);
                          if (!vlanIdFinal.equalsIgnoreCase(Vlan.UNTAGGED)) {
                              userNetwork.setBroadcastDomainType(BroadcastDomainType.Vlan);
rbergsma[~/git/apache/cloudstack](master)$

I'll run a test suite on this PR.

for what it's worth: LGTM

LGTM Run the tests to be sure, all fine.
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a tags=advanced,required_hardware=true \
component/test_vpc_redundant.py \
component/test_routers_iptables_default_policy.py \
component/test_routers_network_ops.py \
component/test_vpc_router_nics.py \
smoke/test_loadbalance.py \
smoke/test_internal_lb.py \
smoke/test_ssvm.py \
smoke/test_network.py

Result:
Check the password file in the Router VM ... === TestName: test_isolate_network_password_server | Status : SUCCESS ===
ok
Create a redundant VPC with two networks with two VMs in each network ... === TestName: test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Status : SUCCESS ===
ok
Create a redundant VPC with two networks with two VMs in each network and check default routes ... === TestName: test_02_redundant_VPC_default_routes | Status : SUCCESS ===
ok
Create a redundant VPC with two networks with two VMs in each network ... === TestName: test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Status : SUCCESS ===
ok
Create a redundant VPC with 1 Tier, 1 VM, 1 ACL, 1 PF and test Network GC Nics ... === TestName: test_04_rvpc_network_garbage_collector_nics | Status : SUCCESS ===
ok
Create a redundant VPC with 1 Tier, 1 VM, 1 ACL, 1 PF and test Network GC Nics ... === TestName: test_05_rvpc_multi_tiers | Status : SUCCESS ===
ok
Test iptables default INPUT/FORWARD policy on RouterVM ... === TestName: test_02_routervm_iptables_policies | Status : SUCCESS ===
ok
Test iptables default INPUT/FORWARD policies on VPC router ... === TestName: test_01_single_VPC_iptables_policies | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_03_RVR_Network_check_router_state | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test nics after destroy ... === TestName: test_01_VPC_nics_after_destroy | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test default routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
ok
Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... === TestName: test_router_dhcphosts | Status : SUCCESS ===
ok
Test to create Load balancing rule with source NAT ... === TestName: test_01_create_lb_rule_src_nat | Status : SUCCESS ===
ok
Test to create Load balancing rule with non source NAT ... === TestName: test_02_create_lb_rule_non_nat | Status : SUCCESS ===
ok
Test for assign & removing load balancing rule ... === TestName: test_assign_and_removal_lb | Status : SUCCESS ===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic to 3 vm's in a Single VPC ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 | Status : SUCCESS ===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic to 3 vm's in a Redundant VPC ... === TestName: test_02_internallb_roundrobin_1RVPC_3VM_HTTP_port80 | Status : SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... === TestName: test_03_vpc_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... === TestName: test_04_rvpc_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS ===
ok
Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status : SUCCESS ===
ok
Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status : SUCCESS ===
ok
Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
ok
Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
ok
Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS ===
ok
Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS ===
ok
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS ===
ok
Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS ===
ok
Test Site 2 Site VPN Across redundant VPCs ... === TestName: test_01_redundant_vpc_site2site_vpn | Status : SUCCESS ===
ok
Test Remote Access VPN in VPC ... === TestName: test_01_vpc_remote_access_vpn | Status : SUCCESS ===
ok
Test Site 2 Site VPN Across VPCs ... === TestName: test_01_vpc_site2site_vpn | Status : SUCCESS ===
ok
test_01_vpc_privategw_acl (integration.smoke.test_privategw_acl.TestPrivateGwACL) ... === TestName: test_01_vpc_privategw_acl | Status : SUCCESS ===
ok
test_02_vpc_privategw_static_routes (integration.smoke.test_privategw_acl.TestPrivateGwACL) ... === TestName: test_02_vpc_privategw_static_routes | Status : SUCCESS ===
ok
test_03_vpc_privategw_restart_vpc_cleanup (integration.smoke.test_privategw_acl.TestPrivateGwACL) ... === TestName: test_03_vpc_privategw_restart_vpc_cleanup | Status : SUCCESS ===
ok
test_04_rvpc_privategw_static_routes (integration.smoke.test_privategw_acl.TestPrivateGwACL) ... === TestName: test_04_rvpc_privategw_static_routes | Status : SUCCESS ===
ok
Test for port forwarding on source NAT ... === TestName: test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_3_Load_Balancer_Rule | Status : SUCCESS ===
ok

Ran 44 tests in 27761.483s

OK

And:
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a tags=advanced,required_hardware=false \
smoke/test_routers.py \
smoke/test_network_acl.py \
smoke/test_privategw_acl.py \
smoke/test_reset_vm_on_reboot.py \
smoke/test_vm_life_cycle.py \
smoke/test_vpc_vpn.py \
smoke/test_service_offerings.py \
component/test_vpc_offerings.py \
component/test_vpc_routers.py

Result:
Test router internal advanced zone ... === TestName: test_02_router_internal_adv | Status : SUCCESS ===
ok
Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS ===
ok
Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS ===
ok
Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS ===
ok
Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS ===
ok
Test start router ... === TestName: test_08_start_router | Status : SUCCESS ===
ok
Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS ===
ok
Test reset virtual machine on reboot ... === TestName: test_01_reset_vm_on_reboot | Status : SUCCESS ===
ok
Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status : SUCCESS ===
ok
Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS ===
ok
Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status : SUCCESS ===
ok
Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS ===
ok
Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS ===
ok
Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS ===
ok
Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS ===
ok
Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS ===
ok
Test migrate VM ... === TestName: test_08_migrate_vm | Status : SUCCESS ===
ok
Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status : SUCCESS ===
ok
Test to create service offering ... === TestName: test_01_create_service_offering | Status : SUCCESS ===
ok
Test to update existing service offering ... === TestName: test_02_edit_service_offering | Status : SUCCESS ===
ok
Test to delete service offering ... === TestName: test_03_delete_service_offering | Status : SUCCESS ===
ok
Test for delete account ... === TestName: test_delete_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for admin account ... === TestName: test_public_ip_admin_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for user account ... === TestName: test_public_ip_user_account | Status : SUCCESS ===
ok
Test for release public IP address ... === TestName: test_releaseIP | Status : SUCCESS ===
ok
Test create VPC offering ... === TestName: test_01_create_vpc_offering | Status : SUCCESS ===
ok
Test VPC offering without load balancing service ... === TestName: test_03_vpc_off_without_lb | Status : SUCCESS ===
ok
Test VPC offering without static NAT service ... === TestName: test_04_vpc_off_without_static_nat | Status : SUCCESS ===
ok
Test VPC offering without port forwarding service ... === TestName: test_05_vpc_off_without_pf | Status : SUCCESS ===
ok
Test VPC offering with invalid services ... === TestName: test_06_vpc_off_invalid_services | Status : SUCCESS ===
ok
Test update VPC offering ... === TestName: test_07_update_vpc_off | Status : SUCCESS ===
ok
Test list VPC offering ... === TestName: test_08_list_vpc_off | Status : SUCCESS ===
ok
test_09_create_redundant_vpc_offering (integration.component.test_vpc_offerings.TestVPCOffering) ... === TestName: test_09_create_redundant_vpc_offering | Status : SUCCESS ===
ok
Test start/stop of router after addition of one guest network ... === TestName: test_01_start_stop_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test reboot of router after addition of one guest network ... === TestName: test_02_reboot_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to change service offering of router after addition of one guest network ... === TestName: test_04_chg_srv_off_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test destroy of router after addition of one guest network ... === TestName: test_05_destroy_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to stop and start router after creation of VPC ... === TestName: test_01_stop_start_router_after_creating_vpc | Status : SUCCESS ===
ok
Test to reboot the router after creating a VPC ... === TestName: test_02_reboot_router_after_creating_vpc | Status : SUCCESS ===
ok
Tests to change service offering of the Router after ... === TestName: test_04_change_service_offerring_vpc | Status : SUCCESS ===
ok
Test to destroy the router after creating a VPC ... === TestName: test_05_destroy_router_after_creating_vpc | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 41 tests in 8829.718s

OK

After merging this PR shows much more commits and changed files than before merge.
For the record, this what I saw at the moment of merging:

This is the log of my commands:

Everything seems OK. @DaanHoogland can you please validate it went well? Thanks.

This due to the PR being for a merge commit. You could have just pushed it upstream
The extra merge does nothing
the extra file (s?) is only in the conflict resolving. It should be only one and it is also in one of the commits before.


[gdal] update port to 2.3.2 and mysql support as port feature

This PR updates gdal port from 2.3.0 to 2.3.2.
It also removes libmysql from GDAL core dependencies and makes mysql support a port feature (related issue: #3793).
Two features are created:

mysql-libmysql to add mysql support using libmysql
mysql-libmariadb to add mysql support using libmariadb

mysql-libmysql is placed in Default-Features to keep previous compatibility.
However, one can choose between libmariadb or libmysql implementation or even no mysql support using feature selection:
vcpkg install gdal[core]
vcpkg install gdal[core,mysql-libmysql]
vcpkg install gdal[core,mysql-libmariadb]

Finally, this PR fixes build issue of libmariadb if VCPKG_BUILD_TYPE is set to release or debug

Awesome, thanks for the PR!


Support tailable cursors in find

What should be done?
https://www.mongodb.com/docs/manual/core/tailable-cursors/
Tailable cursors do not close when it exhausted results, the cursor is kept open waiting for more documents to be added. It's available for find cursor. Not available for aggregate cursor.
issue number added in PR https://github.com/FerretDB/FerretDB/pull/2953
Where?
https://github.com/FerretDB/FerretDB/blob/cbd9e06a3361e0b88ee81d4323f93e62c3635106/internal/handlers/pg/msg_find.go#L161
Definition of Done

all handlers updated;
integration/compatibility tests added/updated;
spot refactorings done;
user documentation updated or an issue to create documentation created;

Duplicate of #2283


Append _async to Whitehall::PublishingApi methods

across WH code wherever Whitehall::PublishingApi is referenced, it is not apparent that methods on it perform operations async'ly. this rename makes it explicit that we're sending an edition to a queue to be processed async.

This seems to be missing the changes to Whitehall::PublishingApi itself :-)

@danielroseman, who does that? fixed. :smile:

:+1:


Implement slog Logging in Postgres

Description
The objective is to enhance our logging mechanism within the internal/storage/postgres directory of our codebase. We plan to use slog, a feature in the new version of Go, for detailed and efficient logging. This will significantly improve our debugging and monitoring capabilities for our Postgres datastore.
Suggested Implementation

Integrate slog for Advanced Logging: Adopt slog for logging in the internal/storage/postgres directory, capturing detailed log information at different levels (debug, info, warning, error).
Ensure Compatibility with Postgres: Validate that slog is compatible and works efficiently with our Postgres implementation.
Consistent Logging Standards: Develop and maintain consistent logging formats and practices.

Example Code with slog Integration
Below is an example showing how slog can be implemented in the internal/storage/postgres directory:
package postgres

// ... Other imports ...
import "path/to/slog"

// ... Existing code ...

// Begin a new read-only transaction with the specified isolation level.
var tx *sql.Tx
tx, err = r.database.DB.BeginTx(ctx, &r.txOptions)
if err != nil {
    slog.Error("Error starting transaction: ", err)
    // ... other error handling ...
    return nil, nil, err
}

slog.Debug("Transaction started")

// Rollback the transaction in case of any error.
defer utils.Rollback(tx)

// Build relationships query
// ... building query ...
slog.Info("Building relationships query")
// ... applying filters ...
slog.Debug("Applied tuples filter to query builder")
// ... more query modifications ...
slog.Debug("Applied snapshot query to query builder")

// ... Rest of your code ...

Goals
Contextual Logging: Implement detailed logging within the internal/storage/postgres directory.
Enhanced Debugging: Enable better debugging and error tracing with clear, contextual log messages.
Monitor Logging Impact: Assess the impact of logging on system performance and database interactions.

Please assign to me!


Display of movie items is not correct when remove it after download movie.

The Issue
Display of movie items is not correct when remove it after download movie.
Steps to Reproduce

Go to any movie and remember it (ex MOVIE_03)
Click DOWNLOAD
Wait until there is some download progress (10%, 20%... COMPLETE)
Click REMOVE button
Tick on check box: Delete this file from my computer
Click REMOVE button to confirm remove

Expected Behaviour
Go back to home page, and confirm the MOVIE_03. It should keep as same as original, there no icon of folder (mean You have a copy of this file), and when go to the MOVIE_03, you will need to click download or play again to have a copy of it.
And the movie is deleted.
Actual Behaviour
Go back to home page, and confirm the MOVIE_03: You will see the icon of Folder (mean You have a copy of this file).
When click on it, it display xx% COMPLETE and REMOVE button.
But the movie is deleted.
Suggested Solutions
N/A
System Configuration

LBRY Daemon version: 0.19.3
LBRY App version: 0.21.4
LBRY Installation ID: N/A
Operating system: Windows 10

Anything Else
N/A
Screenshots
N/A

@namujan78 thanks for filing, this is most likely a timing issue related to https://github.com/lbryio/lbry/issues/1199 . Not much we can do about it on the app side for now, but will keep this issue open for tracking.

@namujan78 can you check to see if you can still reproduce this on the latest version? The new daemon should handle deletions better. Also, give it a few seconds after deleting before going back into the claim.

@tzarebczan It is not fixed, still same problem.
App | 0.22.2
Daemon (lbrynet) | 0.20.3
Wallet (lbryum) | 3.2.3

Happen with lbry://aggretsuko-a-cartoon-for-children-ages#66070156e7c93df52122b4359361e3424818b4c4
Frequency: 1/5
It’s quite hard to happen. Thanks.

Closing because it's a small timing issue between the app and daemon. Don't think it's a typical use case to delete the file and quickly go back to the file page.  As the daemon performance improves we should see less of this.


feat(website): add tools page to website

It does not work after building the website
cd docusaurus/website
yarn install
yarn run build
mv build lumos
yarn global add http-server
http-server
# open http://localhost:8080/lumos/tools/address-conversion

tools use API like helper.encodeToAddress only implement on branch ckb2021,So I create a new PR https://github.com/nervosnetwork/lumos/pull/241  and change merge target to ckb2021. this pr will be close


Fix render system

This should fix #1100
@Kukanani can you give this a try and see if it fixes it for you?

Works for me, thanks!

Backported in https://github.com/ros-visualization/rviz/pull/1110

Actually strike that, this will not be back ported, since #1093 was not back ported.


Eliminate LazyRefs before comparing seen types in collectCompanions

Closes #21521
I don't have a minimized test case for this yet. Perhaps someone more knowledgeable can figure out a good way to construct types with LazyRefs.
Also, I'm not sure if this is the best fix, as something else seems to have caused this in 3.5.0 (not many changes in Implicits.scala recently, that I could see, that would have caused this issue).
Still, I think the logic of eliminating LazyRefs before comparing with previously seen types is sound, as that's what TypeComparer does.
With this change, the sample (correctly) fails to compile with the same error messages as on Scala 3.4.2:
 7 |  Box.builder()
 8 |    .setOrientation(Orientation.VERTICAL)
 9 |    .setHalign(Align.START)
10 |    .setValign(Align.BASELINE)
11 |    .se
   |  ^
   |value se is not a member of org.gnome.gtk.Box#Builder[? <: org.gnome.gtk.Box#Builder[?]]#B#B² - did you mean B.ne?
   |
   |where:    B  is a type in trait Builder² with bounds <: io.github.jwharm.javagi.gobject.Builder³[B]
   |          B² is a type in class Builder⁴ with bounds <: org.gnome.gtk.Widget#Builder⁴[B²]

Yeah, this might not be the right fix, see https://github.com/scala/scala3/issues/21521#issuecomment-2336101928

Closed in favor of https://github.com/scala/scala3/pull/21566


Follow serverless

This PR updates deps to follow the promotion of serverless tooling out of trillian-examples and into its own repo.

This can be merged. Why leaves_pr fails unknown and will still be investigated.


Usage question about plugin.cfg

I'm new to this plugin and godot so I have some question about usage.
Assume I installed plugin A on project A, plugin B on project B, ...
And now I want to enable all plugins among all projects.
Then, I should add paths like /..../projectA/addons/pluginA/plugin.cfg, /..../projectB/addons/pluginB/plugin.cfg, ...
I wonder In this case, what should I do if I want to remove project B in my disk. Should I move plugin B to other project?

If you want to keep plugin b then yeah. And also update the path in EditorSettings
Though I think I see the issue you're bringing up. I'm assuming you're downloading a plugin from the asset store, and you don't want the "globalization" to be tied to a specific project
For now, it might be a good idea to have a single project specifically for containing plugins that should be global

But I might be able to add another editor property, where instead of file paths, you have a list of URLs. The URLs could point to plugins in the asset store, and synced into the project from there. I'll have to experiment a bit

If you want to keep plugin b then yeah. And also update the path in EditorSettings
Though I think I see the issue you're bringing up. I'm assuming you're downloading a plugin from the asset store, and you don't want the "globalization" to be tied to a specific project
For now, it might be a good idea to have a single project specifically for containing plugins that should be global

Well understood.

But I might be able to add another editor property, where instead of file paths, you have a list of URLs. The URLs could point to plugins in the asset store, and synced into the project from there. I'll have to experiment a bit
Edit: nvm, the asset library doesn't have a public api

Have you check this api document?
Looks like this can be used.
$ curl --request GET \
       --url https://godotengine.org/asset-library/api/asset/2681

{
	"asset_id": "2681",
	"type": "addon",
	"title": "Globalize Plugins",
	"author": "dugramen",
	"author_id": "13830",
	"version": "1",
	"version_string": "1.0",
	"category": "Tools",
	"category_id": "5",
	"godot_version": "4.2",
	"rating": "0",
	"cost": "MIT",
	"description": "This plugin lets you globalize other plugins. Globalized plugins get copied into the current project when loaded, keeping them up to date and adding any new plugins you've globalized since.\r\n\r\nTo globalize plugins, go to Editor > EditorSettings > Global Plugins > Paths, and add the plugin.cfg of your plugin.\r\n\r\nTo enable global plugins in a project, just download and enable this plugin, and all your globalized plugins will be added automatically (You only have to do this once per project).",
	"support_level": "community",
	"download_provider": "GitHub",
	"download_commit": "6da8eb783547c4fd6b2c02edc3b8e2d5a4f61af3",
	"browse_url": "https:\/\/github.com\/dugramen\/godot-globalize-plugins",
	"issues_url": "https:\/\/github.com\/dugramen\/godot-globalize-plugins\/issues",
	"icon_url": "https:\/\/raw.githubusercontent.com\/dugramen\/godot-globalize-plugins\/master\/globalize-plugin.png",
	"searchable": "1",
	"modify_date": "2024-03-14 19:39:19",
	"download_url": "https:\/\/github.com\/dugramen\/godot-globalize-plugins\/archive\/6da8eb783547c4fd6b2c02edc3b8e2d5a4f61af3.zip",
	"previews": [],
	"download_hash": ""
}

Thanks! Don't know how I missed that
I was experimenting with parsing the Asset Library's node tree and grabbing the repository link from there. I might be able to inject a "Globalize" button directly into the download prompt that way. But if that gets too complicated I'll just settle for a simple search UI with their api


WIP don't merge yet!

Hello @pbugni! Thanks for submitting the PR.

In the file portal/models/assessment_status.py, following                are the PEP8 issues :

Line 36:80: E501 line too long (80 > 79 characters)
Line 228:80: E501 line too long (81 > 79 characters)
Line 464:5: E722 do not use bare 'except'

There are no PEP8 issues in the file portal/models/clinical_constants.py !

There are no PEP8 issues in the file portal/models/coredata.py !

There are no PEP8 issues in the file portal/models/encounter.py !

In the file portal/models/fhir.py, following                are the PEP8 issues :

Line 71:1: W391 blank line at end of file

In the file portal/models/intervention_strategies.py, following                are the PEP8 issues :

Line 295:80: E501 line too long (82 > 79 characters)

In the file portal/models/observation.py, following                are the PEP8 issues :

Line 18:80: E501 line too long (80 > 79 characters)

In the file portal/models/organization.py, following                are the PEP8 issues :

Line 99:80: E501 line too long (81 > 79 characters)
Line 101:80: E501 line too long (82 > 79 characters)
Line 152:80: E501 line too long (80 > 79 characters)
Line 380:80: E501 line too long (80 > 79 characters)
Line 539:80: E501 line too long (84 > 79 characters)
Line 540:80: E501 line too long (85 > 79 characters)
Line 839:9: E266 too many leading '#' for block comment

In the file portal/models/questionnaire_bank.py, following                are the PEP8 issues :

Line 302:80: E501 line too long (84 > 79 characters)
Line 326:80: E501 line too long (87 > 79 characters)

In the file portal/models/questionnaire_response.py, following                are the PEP8 issues :

Line 364:1: W391 blank line at end of file

There are no PEP8 issues in the file portal/models/reporting.py !

In the file portal/models/user.py, following                are the PEP8 issues :

Line 4:36: E261 at least two spaces before inline comment
Line 492:80: E501 line too long (80 > 79 characters)
Line 496:80: E501 line too long (80 > 79 characters)
Line 521:80: E501 line too long (80 > 79 characters)
Line 681:80: E501 line too long (83 > 79 characters)
Line 1731:80: E501 line too long (85 > 79 characters)
Line 1921:13: E128 continuation line under-indented for visual indent

There are no PEP8 issues in the file portal/models/value_quantity.py !

In the file portal/views/assessment_engine.py, following                are the PEP8 issues :

Line 125:80: E501 line too long (110 > 79 characters)
Line 163:80: E501 line too long (87 > 79 characters)
Line 171:80: E501 line too long (87 > 79 characters)
Line 179:80: E501 line too long (87 > 79 characters)
Line 187:80: E501 line too long (87 > 79 characters)
Line 195:80: E501 line too long (87 > 79 characters)
Line 203:80: E501 line too long (87 > 79 characters)
Line 211:80: E501 line too long (87 > 79 characters)
Line 219:80: E501 line too long (87 > 79 characters)
Line 227:80: E501 line too long (87 > 79 characters)
Line 235:80: E501 line too long (87 > 79 characters)
Line 243:80: E501 line too long (87 > 79 characters)
Line 251:80: E501 line too long (87 > 79 characters)
Line 259:80: E501 line too long (87 > 79 characters)
Line 267:80: E501 line too long (87 > 79 characters)
Line 275:80: E501 line too long (87 > 79 characters)
Line 283:80: E501 line too long (87 > 79 characters)
Line 291:80: E501 line too long (87 > 79 characters)
Line 299:80: E501 line too long (87 > 79 characters)
Line 307:80: E501 line too long (87 > 79 characters)
Line 315:80: E501 line too long (87 > 79 characters)
Line 323:80: E501 line too long (87 > 79 characters)
Line 331:80: E501 line too long (87 > 79 characters)
Line 339:80: E501 line too long (87 > 79 characters)
Line 347:80: E501 line too long (87 > 79 characters)
Line 355:80: E501 line too long (87 > 79 characters)
Line 363:80: E501 line too long (87 > 79 characters)
Line 392:80: E501 line too long (87 > 79 characters)
Line 400:80: E501 line too long (87 > 79 characters)
Line 408:80: E501 line too long (87 > 79 characters)
Line 418:80: E501 line too long (87 > 79 characters)
Line 426:80: E501 line too long (87 > 79 characters)
Line 434:80: E501 line too long (87 > 79 characters)
Line 444:80: E501 line too long (87 > 79 characters)
Line 452:80: E501 line too long (87 > 79 characters)
Line 460:80: E501 line too long (87 > 79 characters)
Line 468:80: E501 line too long (87 > 79 characters)
Line 476:80: E501 line too long (87 > 79 characters)
Line 484:80: E501 line too long (87 > 79 characters)
Line 492:80: E501 line too long (87 > 79 characters)
Line 500:80: E501 line too long (87 > 79 characters)
Line 508:80: E501 line too long (87 > 79 characters)
Line 516:80: E501 line too long (87 > 79 characters)
Line 524:80: E501 line too long (87 > 79 characters)
Line 532:80: E501 line too long (87 > 79 characters)
Line 540:80: E501 line too long (87 > 79 characters)
Line 548:80: E501 line too long (87 > 79 characters)
Line 556:80: E501 line too long (87 > 79 characters)
Line 564:80: E501 line too long (87 > 79 characters)
Line 572:80: E501 line too long (87 > 79 characters)
Line 580:80: E501 line too long (87 > 79 characters)
Line 587:80: E501 line too long (82 > 79 characters)
Line 617:80: E501 line too long (80 > 79 characters)
Line 728:80: E501 line too long (110 > 79 characters)
Line 783:80: E501 line too long (82 > 79 characters)
Line 884:80: E501 line too long (82 > 79 characters)
Line 917:80: E501 line too long (134 > 79 characters)
Line 933:80: E501 line too long (120 > 79 characters)
Line 937:80: E501 line too long (118 > 79 characters)
Line 942:80: E501 line too long (136 > 79 characters)
Line 961:80: E501 line too long (145 > 79 characters)
Line 966:80: E501 line too long (144 > 79 characters)
Line 973:80: E501 line too long (148 > 79 characters)
Line 975:80: E501 line too long (80 > 79 characters)
Line 986:80: E501 line too long (161 > 79 characters)
Line 994:80: E501 line too long (172 > 79 characters)
Line 1012:80: E501 line too long (80 > 79 characters)
Line 1106:80: E501 line too long (85 > 79 characters)
Line 1114:80: E501 line too long (85 > 79 characters)
Line 1122:80: E501 line too long (85 > 79 characters)
Line 1132:80: E501 line too long (85 > 79 characters)
Line 1140:80: E501 line too long (85 > 79 characters)
Line 1148:80: E501 line too long (85 > 79 characters)
Line 1158:80: E501 line too long (85 > 79 characters)
Line 1166:80: E501 line too long (85 > 79 characters)
Line 1174:80: E501 line too long (85 > 79 characters)
Line 1182:80: E501 line too long (85 > 79 characters)
Line 1190:80: E501 line too long (85 > 79 characters)
Line 1198:80: E501 line too long (85 > 79 characters)
Line 1206:80: E501 line too long (85 > 79 characters)
Line 1214:80: E501 line too long (85 > 79 characters)
Line 1222:80: E501 line too long (85 > 79 characters)
Line 1230:80: E501 line too long (85 > 79 characters)
Line 1238:80: E501 line too long (85 > 79 characters)
Line 1246:80: E501 line too long (85 > 79 characters)
Line 1254:80: E501 line too long (85 > 79 characters)
Line 1262:80: E501 line too long (85 > 79 characters)
Line 1270:80: E501 line too long (85 > 79 characters)
Line 1278:80: E501 line too long (85 > 79 characters)
Line 1286:80: E501 line too long (85 > 79 characters)
Line 1294:80: E501 line too long (85 > 79 characters)
Line 1507:80: E501 line too long (80 > 79 characters)
Line 1548:80: E501 line too long (80 > 79 characters)
Line 1597:80: E501 line too long (80 > 79 characters)
Line 1763:80: E501 line too long (95 > 79 characters)
Line 1776:80: E501 line too long (84 > 79 characters)

There are no PEP8 issues in the file portal/views/clinical.py !

In the file portal/views/patient.py, following                are the PEP8 issues :

Line 38:80: E501 line too long (83 > 79 characters)
Line 166:80: E501 line too long (81 > 79 characters)
Line 189:80: E501 line too long (80 > 79 characters)
Line 190:80: E501 line too long (80 > 79 characters)
Line 195:80: E501 line too long (83 > 79 characters)

In the file portal/views/portal.py, following                are the PEP8 issues :

Line 246:80: E501 line too long (86 > 79 characters)
Line 373:80: E501 line too long (80 > 79 characters)
Line 502:80: E501 line too long (90 > 79 characters)
Line 505:80: E501 line too long (88 > 79 characters)
Line 962:80: E501 line too long (101 > 79 characters)
Line 973:80: E501 line too long (89 > 79 characters)
Line 1137:80: E501 line too long (86 > 79 characters)
Line 1146:80: E501 line too long (84 > 79 characters)
Line 1155:80: E501 line too long (83 > 79 characters)
Line 1164:80: E501 line too long (84 > 79 characters)
Line 1173:80: E501 line too long (83 > 79 characters)

In the file tests/__init__.py, following                are the PEP8 issues :

Line 65:1: E402 module level import not at top of file
Line 263:12: E713 test for membership should be 'not in'

There are no PEP8 issues in the file tests/test_assessment_status.py !

There are no PEP8 issues in the file tests/test_clinical.py !

There are no PEP8 issues in the file tests/test_communication.py !

There are no PEP8 issues in the file tests/test_fhir.py !

There are no PEP8 issues in the file tests/test_questionnaire_bank.py !

There are no PEP8 issues in the file tests/test_site_persistence.py !

In the file tests/test_user.py, following                are the PEP8 issues :

Line 176:80: E501 line too long (80 > 79 characters)
Line 222:80: E501 line too long (80 > 79 characters)
Line 378:5: E303 too many blank lines (2)


Share this on Hacker News?

hey ykdojo

?

I think you absolutely should! This an awesome tool and I'm sure it would get a lot of traction. I would suggest creating a setup tutorial first to reduce the number of future issues like the "have you tried writing documentation" from the influx it will probably bring and save yourself the potential headache. Like I mentioned in discord, I'm happy to contribute to the win setup portion with a PR to the readme when I have some time :)

Sounds good! That's basically where I was, too. And thank you! Looking forward to your PR.


Add Ruby 3.0.1, 3.0.0, 2.7.3, 2.6.7 and 2.5.9

Ruby 3.0.0 was released two months ago.  This PR adds 3.0.0 to the list of rubies.

New teeny releases have been added.  /ping @dazuma 🙏

This project seems to be on hiatus, but fortunately, the Dockerfile template is so simple and you can easily build prebuilt ruby images on your own.
 This looks fine. The changes to CI won't pass until we actually build the new versions, and we need them in master in order to do that, so I'll go ahead and merge this for now.

@dazumu Thank you for coming back and taking the time.  I really appreciate it!


[Service Bus] Batching Receiver Batch Receiver failing in nightly runs

Service Bus nightly test runs are failing with:

Error message:
The session lock has expired on the session with id my-session
Stack trace:
ServiceBusError: The session lock has expired on the session with id my-session
at translateServiceBusError (/Users/runner/work/1/s/sdk/servicebus/service-bus/src/serviceBusError.ts:86:63)
at ServiceBusSessionReceiverImpl._throwIfReceiverOrConnectionClosed (/Users/runner/work/1/s/sdk/servicebus/service-bus/src/receivers/sessionReceiver.ts:110:1)
at ServiceBusSessionReceiverImpl.completeMessage (/Users/runner/work/1/s/sdk/servicebus/service-bus/dist-esm/src/receivers/sessionReceiver.js:73:1367)
at completeDeadLetteredMessage (/Users/runner/work/1/s/sdk/servicebus/service-bus/test/internal/batchReceiver.spec.ts:473:22)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at testDeadletter (/Users/runner/work/1/s/sdk/servicebus/service-bus/test/internal/batchReceiver.spec.ts:491:7)
at Context. (/Users/runner/work/1/s/sdk/servicebus/service-bus/test/internal/batchReceiver.spec.ts:498:9)

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1390812&view=results

Recent runs are green


Cannot build with go modules

My actions before raising this issue

[x] Followed the troubleshooting guide
[x] Read/searched the docs
[x] Searched past issues

I would like to use go modules in my openfaas function.
Expected Behaviour

I whould be able to build my function by enabling GO111MODULE.
Current Behaviour

Building fail with this error:
handler.go:8:2: no required module provides package golang.org/x/example/stringutil; to add it:
        go get golang.org/x/example/stringutil

Steps to Reproduce (for bugs)

We are going to build a function with "golang.org/x/example/stringutil" module

faas new --lang=golang-middleware test-module
Edit test-module/handler.go

package function

import (
	"fmt"
	"io/ioutil"
	"net/http"

	"golang.org/x/example/stringutil"
)

func Handle(w http.ResponseWriter, r *http.Request) {
	var input []byte

	if r.Body != nil {
		defer r.Body.Close()

		body, _ := ioutil.ReadAll(r.Body)

		input = body
	}

	w.WriteHeader(http.StatusOK)
	w.Write([]byte(stringutil.Reverse("!selpmaxe oG ,olleH")))
}

faas-cli build -f test-module.yml

Step 21/36 : RUN GOOS=${TARGETOS} GOARCH=${TARGETARCH} go test ./... -cover
 ---> Running in e673616d5614
handler.go:8:2: no required module provides package golang.org/x/example/stringutil; to add it:
        go get golang.org/x/example/stringutil
The command '/bin/sh -c GOOS=${TARGETOS} GOARCH=${TARGETARCH} go test ./... -cover' returned a non-zero code: 1

Context

Pulled latest golang-middleware template.
GO111MODULE is now enabled by default.
I tried with build-args option on the cli and in test-module.yml without success.
Your Environment

FaaS-CLI version ( Full output from: faas-cli version ):

CLI:
commit:  72816d486cf76c3089b915dfb0b66b85cf096634
version: 0.13.13

Docker version docker version (e.g. Docker 17.0.05 ): 20.10.12

Are you using Docker Swarm or Kubernetes (FaaS-netes)? Irrelevant

Operating System and version (e.g. Linux, Windows, MacOS): Linux

Code example or link to GitHub repo or gist to reproduce problem: Irrelevant

Other diagnostic information / logs from troubleshooting guide

Next steps
You may join Slack for community support.

@LucasRoesler could you take a look please?

@lapwat my guess is that you haven't read the docs for this, you should be setting --build-arg GO111MODULE=on
https://docs.openfaas.com/cli/templates/
We also cover this extensively in my eBook on OpenFaaS and Go -> https://gumroad.com/l/everyday-golang

/add label: support,question

I guess that this option is now enabled by default: https://github.com/openfaas/golang-http-template/pull/63
I also said in the context that I have tried both options:

faas-cli build -f test-module.yml --build-arg GO111MODULE=on
setting GO111MODULE=one in the yml file

What did I miss ?

Can we reopen the issue ?

Judging by the error you get, your function is not a go module.
As mentioned in the docs you should run go mod init function to initialize your function and than use go get to manage your dependencies.

I think that this process of 'go getting' packages is handled by the Dockerfile.
Note that I don't have this error when using the original go template.

I have succeeded to build the image in this issue.
I do not have to type those commands when working with the go template which was misleading.


v: class implementation

Suspect that big v footprint is due to creating scoped functions instead of using prototype. channel can safely be turned into a class - it has no special signatures.

Done. Can't notice significant memory usage drop though, need to test on benchmark


Multi-pipelines for mono-repo

Although the default name of configuration file is "azure-pipelineS.yaml" it looks like this file allows to define only a single pipeline.
The docs don't mention this limitation explicitly. They also don't seem to provide a guide on how one supposes to maintain a set of pipelines for multiple microservices in a mono-repo.
Ideally I would like to have a single azure-pipelines.yaml in the root which references other pipeline definitions in sub-folders. When a new definition is added there, a corresponding pipeline is created in DevOps.

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

ID: 7458d5b2-1bb7-7d87-7ce6-2b0c430b0155
Version Independent ID: edf5bbd3-a3f0-5426-e985-31290f8afd05
Content: YAML schema - Azure Pipelines
Content Source: docs/pipelines/yaml-schema.md
Product: devops
Technology: devops-cicd
GitHub Login: @vtbassmatt
Microsoft Alias: macoope

The name of the product is "Azure Pipelines", hence the name of the YAML file.
You can have multiple pipelines pointing to one YAML file. And for example, you could make that pipeline expect a variable telling it which directory to build, and then each of your definitions could set the variable differently. Alternatively, you can have as many pipeline YAMLs as you want in the repo.
Auto-creation is something we've considered, but it hasn't bubbled up the backlog yet. To make sure your voice is heard, you should file a feature request on Developer Community. (And interestingly, not everyone wants us to do the auto-creating thing at all.)

Thanks Matt, done: https://developercommunity.visualstudio.com/idea/820717/allow-defining-multiple-pipelines-in-one-yaml-conf.html


feat: integrate with Codecov

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@ddfb30d). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #50   +/-   ##
=======================================
  Coverage        ?   95.09%
  Complexity      ?      416
=======================================
  Files           ?       88
  Lines           ?     1571
  Branches        ?        0
=======================================
  Hits            ?     1494
  Misses          ?       77
  Partials        ?        0

Flag
Coverage Δ

phpunit
95.09% <0.00%> (?)

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

Continue to review full report at Codecov.

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


Fix request cancelling bugs (GPC header injection)

Task/Issue URL: https://app.asana.com/0/inbox/392891325557408/1199370790017886/1198740529455819
Tech Design URL:
CC:
Description:
Use a subclass to inject gpc header without having to cancel and re-issue the request
Steps to test this PR:

Visit https://global-privacy-control.glitch.me/ and enable/disable the GPC setting.  Ensure the website reflects the setting correctly.
Visit https://github.com/globalprivacycontrol/gpc-spec/issues/11#issuecomment-732504580 ensure the page loads as expected (no reload cycle)
Visit https://twitter.com/CodeClanScot/status/1332275491726831616?s=20 (or any other tweet with a link to a URL)

Ensure page loads.
Tap link ensure page loads (in a new tab)
Tap back, should close tab and show Twitter

Smoke test by browsing the web hitting up other big sites like Facebook and Google amongst others.

OS Testing:

[ ] iOS 11
[ ] iOS 12
[ ] iOS 13
[ ] iOS 14

Internal references:
Software Engineering Expectations
Technical Design Template

Doesn't work for navigation.


Position sticks around for quite some time although dlc has already been closed

Happens when opening and closing the position.

Same is when opening a position: it takes ages for the open position to appear.

https://github.com/get10101/10101/assets/382048/afbe72c1-20f5-4557-ae99-27f258f1db7c


Fixed documentation for Query struct

This has already been changed in current main:
https://github.com/bevyengine/bevy/blob/3e285d5c0bd49cf1aff11cf3848270bafdd48646/crates/bevy_ecs/src/system/query.rs#L13-L14


Tweet $5000 for NC Datapalooza top prize

@ChrisTheDBA Please send over more information so that I can promote more effectively


fix neofetch not recognizing brew package count on M1 macs

Description
changes /usr/local/Cellar to "$(brew --cellar)" as used on line 1550
Features
Issues
#1746
TODO
Someone with a non-M1 mac should verify this has no issues for them (done)

also fixed an issue where the package count would show every available package for apt rather than just the installed one.


fix: Intermediate solution for 429 Too Many Requests error

Hey, I just made a Pull Request!
This PR attempts to address the issue of Bitbucket Server API call rate limit and the '429 Too Many Requests' error, considering that RFC #13531 is not yet ready.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

I understand that amount of entities in your catalog might be too large for this to have any meaningful effect.
I feel that the best investment is to transitioning over to webhooks for Bitbucket which should drastically reduce the amount of requests as requests are only made when needed. Adding retries to the stable integrations API require more thought and it does not feel like a good intermediate solution for already sending to many requests. It might be that specific operations within the scaffolder should be retry-able but I think that those are probably best decided on a case by case basis and something that we might want to surface in the task execution log to clearly surface to the user that operation X failed but we're trying x more times before giving up. More so I think the default cases for retries are probably cases where the API returns a 500. If you want to explore retries further I suggest to make an RFC covering this in a bit more details with some of the concerns raised here. Solving for BitBucket specifically the best way forward is to implement webhooks similarly as the community has done for GitHub.


Cannot read property 'style' of undefined

I keep getting this when I open the terminal. It seems to have something to do with task terminals because I see it when I am using them.
TypeError: Cannot read property 'style' of undefined
    at e.layout (terminalInstance.ts:1313)
    at p.layout (terminalTab.ts:204)
    at v.layout (splitview.ts:130)
    at S.layoutViews (splitview.ts:855)
    at S.layout (splitview.ts:423)
    at g.layout (terminalTab.ts:136)
    at m.layout (terminalTab.ts:404)
    at terminalPanel.ts:123
    at Array.forEach (<anonymous>)
    at x.layout (terminalPanel.ts:123)
    at e.showComposite (compositePart.ts:278)
    at e.doOpenComposite (compositePart.ts:147)
    at e.openComposite (compositePart.ts:111)
    at e.openPanel (panelPart.ts:236)
    at terminalService.ts:419
    at new Promise (<anonymous>)
    at D.showPanel (terminalService.ts:416)
    at ne.run (terminalActions.ts:583)
    at Object.triggerAndDisposeAction (actions.ts:116)
    at /Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/async file:/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2586

Caused by https://github.com/xtermjs/xterm.js/issues/2471 in a backgrounded task


BotBuilder and BotConnector architecture

Investigate Microsoft BotBuilder and BotConnector architecture

[ ] Create MarkupBuilder
[ ] Escaping message

Define replyTo. If message.to contains @thread.skype or @p2p.thread.skype then need to use mesage.to otherwise message.from

Create TextBuilder instead of Markupbuilder where each part of text should be represented as TextPart.
Create Smilies as one of implementation of available smilies in skype.
Bold as TextPart which will wrap text into bold
Italic as TextPart which will wrap text into italic

Link as TextPart which will print a link

Also need to create a TextParser which will be parse text of message Andrey create TextBuilder

Send typing request before each message activity

Implement a sending and receiving quotes
<quote author=\"LOGIN\" authorname=\"LOGIN\" conversation=\"ID\" guid=\"xdedd1401e88ff300ec7303 6b9661085b15c683021741a32a042178c230debd97\" timestamp=\"1475750831\"><legacyquote>[13:47:11] LOGIN: </legacyquote>на их исправление много времени уйдет?<legacyquote>\r\n\r\n<<< </legacyquote></quote>"

https://docs.oracle.com/javase/tutorial/i18n/text/boundaryintro.html

<URIObject type="Video.1/Flik.1" uri="https://static.asm.skype.com/pes/v1/items/c8d2e2ae0da64a4d8e3bf4fc854c8d25\" url_thumbnail="https://static.asm.skyp
e.com/pes/v1/items/c8d2e2ae0da64a4d8e3bf4fc854c8d25/views/thumbnail"> Moji <a href="https://login.skype.com/login/sso?go=xmmfallback&c8d2e2ae0da64a4d8e3bf4fc854c8d25
">https://login.skype.com/login/sso?go=xmmfallback&c8d2e2ae0da64a4d8e3bf4fc854c8d25<OriginalName v="The Secret Life of Pets" />

Implement sending and receiving {code}


fix/2896 Fix saving pivot values in CreateAction

This uses the create function to directly save the pivot values on the relations. See issue 2896 & https://github.com/filamentphp/filament/issues/2896#issuecomment-1176066942

Thanks!


Update of api/1/energy_sites/{site_id}/tariff_rate

using the SITE_TARIFF endpoint.
Maybe a bit long for inclusion here, so I may need to simplify but keep the structure.

Thanks as well!


Creating Databases

As a service provider
I need an SQL databases to store user's ID, first name, last name, address 1 and address 2 (optional), isActive.
So that I can retrieve them anytime using REST APIs.
Details and Assumptions

We will be using SQL Database.

Acceptance Criteria
Given query is called
When database receives the request query and is executed
Then database is successfully created

Hey team! Please add your planning poker estimate with Zenhub @kovidiament @omb244 @SamSloboda

I have moved this issue to the "Done" section as it was covered with #17.


what is the difference between hostport and localredirectpolicy?

in hostport mode external traffic from any other not kubernetes node can connect to the hostport node，but in localredirectpolicy addressMatcher mode it seems only allow the node which has the addressMatcher‘s ip to connect ,maybe the other kubernetes node also can connect but i don't make a test .  so I have this question as I asked. Or this function is designd for the external workloads, make it convinent for no needs to change the application config

LRPs enable users to specify configurations to redirect application pod traffic to a backend pod running on the same node as the application pod. For example, the addressMatcher LRP that you mentioned lets user specify <ip address/port/protocol> tuple as a frontend configuration and backend pod configuration where application pod traffic destined to this frontend is redirected to. On the other hand, the serviceMatcher LRP lets user specify a Kubernetes clusterIP service for which traffic from pods need to be redirected to only node-local backend pods.
LRPs only apply to East-West traffic and not for North-South external workloads.
You can also read about the use cases that LRPs enable in order to understand this better - https://docs.cilium.io/en/latest/gettingstarted/local-redirect-policy/#use-cases.
Let us know if you need additional clarification.


fix(utils): recognize content types with valid whitespace

The RFC for content-type header format allows optional whitespace before the semicolon. Our regular expressions for recognizing various mime types do not account for this, so valid mime types may not be recognized. This commit adjusts the expression to close that gap.
PR summary

PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] Dependencies have been updated as needed
[ ] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:

[ ] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)
[ ] If necessary, added new validation rule implementation (packages/ruleset/src/functions/*.js, updated index.js)
[ ] Added new rule to default configuration (packages/ruleset/src/ibm-oas.js)
[ ] Added tests for new rule (packages/ruleset/test/*.test.js)
[ ] Added docs for new rule (docs/ibm-cloud-rules.md)

:tada: This PR is included in version 0.45.5 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.97.5 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.0.2-rc.1 :tada:
The release is available on npm package (@v1-rc dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


make integration fails with missing entry error in go.sum

Description
After go version was updated to 1.16.6, i am seeing this test failure with my commit that i am trying to test and send upstream.
[ec2-user@fc-dev:containerd 15:05:14]$ go mod tidy
warning: ignoring symlink /home/ec2-user/containerd/cluster/gce
warning: ignoring symlink /home/ec2-user/containerd/test/e2e
[ec2-user@fc-dev:containerd 15:05:16]$ go mod vendor
warning: ignoring symlink /home/ec2-user/containerd/cluster/gce
warning: ignoring symlink /home/ec2-user/containerd/test/e2e
[ec2-user@fc-dev:containerd 15:05:19]$ make
+ bin/ctr
+ bin/containerd
+ bin/containerd-stress
+ bin/containerd-shim
+ bin/containerd-shim-runc-v1
+ bin/containerd-shim-runc-v2
+ binaries
[ec2-user@fc-dev:containerd 15:05:29]$ make integration
+ integration
# github.com/containerd/containerd/integration/client
../../../go/pkg/mod/google.golang.org/grpc@v1.38.0/credentials/credentials.go:31:2: missing go.sum entry for module providing package github.com/golang/protobuf/proto (imported by google.golang.org/grpc/health/grpc_health_v1); to add:
	go get<EMAIL_ADDRESS>FAIL	github.com/containerd/containerd/integration/client [setup failed]
make: *** [integration] Error 1
[ec2-user@fc-dev:containerd 15:05:36]$ go version
go version go1.16.6 linux/amd64
[ec2-user@fc-dev:containerd 15:05:42]$ go get<EMAIL_ADDRESS>[ec2-user@fc-dev:containerd 15:06:04]$ make integration
+ integration
# github.com/containerd/containerd/integration/client
../../../go/pkg/mod/google.golang.org/grpc@v1.38.0/credentials/credentials.go:31:2: missing go.sum entry for module providing package github.com/golang/protobuf/proto (imported by google.golang.org/grpc/health/grpc_health_v1); to add:
	go get<EMAIL_ADDRESS>FAIL	github.com/containerd/containerd/integration/client [setup failed]
make: *** [integration] Error 1
[ec2-user@fc-dev:containerd 15:06:08]$ go mod tidy
warning: ignoring symlink /home/ec2-user/containerd/cluster/gce
warning: ignoring symlink /home/ec2-user/containerd/test/e2e
[ec2-user@fc-dev:containerd 15:06:27]$ go mod vendor
warning: ignoring symlink /home/ec2-user/containerd/cluster/gce
warning: ignoring symlink /home/ec2-user/containerd/test/e2e
[ec2-user@fc-dev:containerd 15:06:30]$ make integration
+ integration
# github.com/containerd/containerd/integration/client
../../../go/pkg/mod/google.golang.org/grpc@v1.38.0/credentials/credentials.go:31:2: missing go.sum entry for module providing package github.com/golang/protobuf/proto (imported by google.golang.org/grpc/health/grpc_health_v1); to add:
	go get<EMAIL_ADDRESS>FAIL	github.com/containerd/containerd/integration/client [setup failed]
make: *** [integration] Error 1

Steps to reproduce the issue:
Can be reproduced by trying to do make integration in following branch for example
https://github.com/alakesh/containerd/tree/opentelemetry-basic
Describe the results you received:
[ec2-user@fc-dev:containerd 15:06:30]$ make integration
+ integration
# github.com/containerd/containerd/integration/client
../../../go/pkg/mod/google.golang.org/grpc@v1.38.0/credentials/credentials.go:31:2: missing go.sum entry for module providing package github.com/golang/protobuf/proto (imported by google.golang.org/grpc/health/grpc_health_v1); to add:
	go get<EMAIL_ADDRESS>FAIL	github.com/containerd/containerd/integration/client [setup failed]
make: *** [integration] Error 1

[ec2-user@fc-dev:containerd 15:06:32]$ containerd --version
containerd github.com/containerd/containerd v1.5.0-199-g7eceeb950.m 7eceeb950b84396c165d972efb35116a113966fd.m
Any other relevant information (runC version, CRI configuration, OS/Kernel version, etc.):
[ec2-user@fc-dev:containerd 15:11:45]$ uname -a
Linux ip-172-31-40-125.us-west-2.compute.internal 4.14.238-182.422.amzn2.x86_64 #1 SMP Tue Jul 20 20:35:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
[ec2-user@fc-dev:containerd 15:12:03]$ runc --version
runc version 1.0.0
commit: %runc_commit
spec: 1.0.2-dev
go: go1.15.12
libseccomp: 2.4.1

The issue got resolved by doing this
[ec2-user@fc-dev:containerd 15:29:27]$ cd integration/client/
[ec2-user@fc-dev:client 15:29:33]$ go get -t .
go build github.com/containerd/containerd/integration/client: build constraints exclude all Go files in /home/ec2-user/containerd/integration/client
[ec2-user@fc-dev:client 15:29:38]$ go mod tidy
[ec2-user@fc-dev:client 15:29:48]$ go mod vendor
[ec2-user@fc-dev:client 15:29:52]$ go get -t .
go build github.com/containerd/containerd/integration/client: build constraints exclude all Go files in /home/ec2-user/containerd/integration/client


Could not find com.github.yhaolpz:FloatWindow:1.0.9

Could not find com.github.yhaolpz:FloatWindow:1.0.9. 按照引导接入，提示如前，FloatWindow指定的maven地址不可访问，求解，谢谢哈~

maven { url 'https://jitpack.io' } 这个地址没法访问，有啥其他办法吗？

maven { url 'https://jitpack.io' } 这个地址没法访问，有啥其他办法吗？

是不是网络问题呀？我这边可以访问。

same issue here

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find com.github.yhaolpz:FloatWindow:1.0.4.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/github/yhaolpz/FloatWindow/1.0.4/FloatWindow-1.0.4.pom
       - https://repo.maven.apache.org/maven2/com/github/yhaolpz/FloatWindow/1.0.4/FloatWindow-1.0.4.pom
       - https://storage.googleapis.com/download.flutter.io/com/github/yhaolpz/FloatWindow/1.0.4/FloatWindow-1.0.4.pom
     Required by:
         project :app

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 3s
Error: Gradle task assembleDebug failed with exit code 1

I put maven { url 'https://jitpack.io' } in my build.gradle and work as well.


vue-components: Update npm dependencies

added 564 packages from 447 contributors, removed 462 packages, updated 255 packages, moved 54 packages and audited 3238 packages in 86.312s
Note: dependabot probably doesn't look for nested package.json files.

TEST FAILURE: 28 errors during execution; 24 assertions failed, 21 passed (6m 42s)

That's a lot of Browser test errors :thinking:
I'll start the tests again, but if that is flakyness, then it reached a new quality.

TEST FAILURE: 28 errors during execution; 24 assertions failed, 21 passed (6m 42s)

That's a lot of Browser test errors thinking

Yes, something's off. Will have a look tomorrow.

Yes, something's off. Will have a look tomorrow.

There is a ticket for it, I was going to look into it on Monday... If you pick it up, please assign it to yourself and move it to the doing column https://phabricator.wikimedia.org/T268107

It looks like the test failures here are different, saucelabs can't find __Lookup-menu on any of the browsers.

Could you update the storybook dependencies to 6.1.6? Otherwise it will keep bugging us^^

Could you update the storybook dependencies to 6.1.6? Otherwise it will keep bugging us^^

Unfortunately the new version of Storybook does not seem to work on IE11.
I'm seeing a Syntax error in vendors~main.0b8843e11b5751b64f8c.bundle.js which is in /storybook-static.
The error is related to /node_modules/prettier/parser-html.js

Thank you for checking in on the IE errors :pray:
There seems to a couple of problems with IE11 and the new storybook, e.g. storybookjs/storybook#12399. Apparently, they were fine releasing the new storybook version without supporting it :shrug:
How do we move forward from here? I'm not sure we have already officially abandoned IE11, so we could move forward with this PR without the storybook updates?
The alternative would be to drop the IE11 tests entirely from our CI. I wouldn't be terribly sad with this solution either.

How do we move forward from here?

I think that for now we should refrain from updating storybook, as we made a conscious decision to support IE11, and I don't think that the fact that storybook doesn't support it should cause us to follow suite.

There seems to a couple of problems with IE11 and the new storybook, e.g. storybookjs/storybook#12399. Apparently, they were fine releasing the new storybook version without supporting it shrug

Yes, but they claimed the bugs are fixed and it works on IE11 now, so I'm inclined to think it's our setup that's at fault :thinking:

How do we move forward from here? I'm not sure we have already officially abandoned IE11, so we could move forward with this PR without the storybook updates?

I downgraded Storybook back to 6.0.28 which is the last version that worked in wikit, so we can move forward with the original idea behind this patch - update dependencies. I'll open a ticket for the storybook update because it seems to be an adventure on its own.

The alternative would be to drop the IE11 tests entirely from our CI. I wouldn't be terribly sad with this solution either.

Supporting IE11 was a decision taken by the whole team back at the start of the DS, so I think it's more of a product question than a dev one.
The whole "using nightwatch and saucelabs" was because of IE11. So I'd be suprised if a few month later we are ready to drop support.


Small changes in API

New function get_problem(problem, name) to fetch a problem from the analysis.
Update docstrings.
Connectivity can be given with tuple when creating new element.
Be more information (@info) when calling functions to be more responsible.
Preparations to separate topology and basis.
Remove function to update properties with string pairs, it's quite an unpractical approach (we still should implement something like update_properties!(...) ).
add_elements!, add_problems!, takes also varargs, so can also call add_elements!(p, e1, e2) instead of creating first iterable.
update! can take list of elements as tuple.
SparseMatrixCOO and SparseVectorCOO can be converted to full matrices / vectors using Matrix and Vector.
Comparison of SparseMatrixCOO with matrix / vector using isapprox.
add! returns nothing.

Coverage increased (+0.2%) to 99.258% when pulling 5d5fdb007c43ddff844473d6c13828d7da3cd8c6 on release-0.2.1 into 5201c70c23eee966406c86548ff25ff8e5a35dd8 on master.


Fix filtered out qualities on 'Myself' tab not being processed when added back.

Closes #20.

@alanhuang122 Please review when you have time.


Adding property to 'import Vue from 'vue'' import makes 'Vue' no longer constructible

TS Template added by @mjbvz
TypeScript Version: 3.9.0-dev.20200427
Search Terms

Vue
constructor
javascript

VSCode Version: 1.44.2
OS Version: Win10

Does this issue occur when all extensions are disabled?: Yes
Intellisense broken after added property.
Steps to Reproduce:
In a test directory :
yarn init -y
yarn add vue

Create a javascript file index.js :
import Vue from 'vue';
Vue.config.productionTip = true;
const vm = new Vue("");

Intellisense work :

Intellisense broken :

A second test with another module (dayjs)
Intellisense work :

Intellisense broken :

A third test with a function constructor in index.js
It always works, test property exists.

The error here is:


[Question]: How to run RAGFLOW locally on a Mac M3 machine

Describe your problem
is there any documentation on how to bring the ragflow service up and running on a Mac M3 machine? I want to run it via docker and docker-compose.

You could follow the guide build the RAGFlow docker image on ARM platform by yourself.


Detail about an objects allways shows "furnished" yes and not the value from DB

DoR:

[] The software is in a stable conditions to reproduce the error

ACA (Acceptance criteria:):

[] AC1: The error get analysed why it always show "furnised yes" and don't take the value from the Database
[] AC2: The error gets fixed and the real values from the Database is in use and shown correctli
[] AC3: There is a suggetion from Brice, that also the field "temporary" got the same problem. Check it out and fixe it too
[] AC4: The software was checked, reviewed and installed on INT

DoD:

[] Dod1: The software on INT can be used and the value is shown correct

Example of the error:

Infos meeting 01.11.2022:
Filipe nows a part of the error to get fixed:

reproducing the error with my own data :

The Bug doesn't appear anymore (See screenshot above)


Add more options to python nexmark launcher

Add some useful flags to control the behavior of nexmark_launcher.
This is the first step to enable nexmark python suite with the java nexmark synthetic source

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @angoenka

Run Python PreCommit

Run PythonDocker PreCommit

Run Python PreCommit

cc: @leiyiz


added Close Poll Button

Added close poll button with implementation in addAnswer:

Pull Request Test Coverage Report for Build 885083106

0 of 28 (0.0%)  changed or added relevant lines in 6 files are covered.
66 unchanged lines in 12 files lost coverage.
Overall coverage decreased (-7.4%) to 11.347%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/Liquid-Core.package/LiquidHostMenu.class/instance/buildWith..st
0
1
0.0%

packages/Liquid-Core.package/LiquidHostMenu.class/instance/closePoll.st
0
3
0.0%

packages/Liquid-Core.package/LiquidPoll.class/instance/open..st
0
3
0.0%

packages/Liquid-Core.package/LiquidPoll.class/instance/open.st
0
3
0.0%

packages/Liquid-Core.package/LiquidHostMenu.class/instance/startPoll.st
0
4
0.0%

packages/Liquid-Core.package/LiquidHostMenu.class/instance/buildClosePollButtonWith..st
0
14
0.0%

Files with Coverage Reduction
New Missed Lines
%

packages/Liquid-Core.package/LiquidHostMenu.class/instance/startPoll.st
1
0%

packages/Liquid-Core.package/LiquidQuestion.class/instance/printOn..st
3
0%

packages/Liquid-Core.package/LiquidResultsView.class/instance/poll.st
3
0%

packages/Liquid-Core.package/LiquidAnswerSet.class/instance/answers.st
4
0%

packages/Liquid-Core.package/LiquidPoll.class/instance/answerSets.st
4
0%

packages/Liquid-Core.package/LiquidQuestion.class/instance/title.st
4
0%

packages/Liquid-Core.package/LiquidResultsView.class/instance/poll..st
4
0%

packages/Liquid-Core.package/LiquidSingleChoiceAnswer.class/instance/votedChoice.st
4
0%

packages/Liquid-Core.package/LiquidResultsView.class/instance/getResults.st
6
0%

packages/Liquid-Core.package/LiquidSingleChoiceAnswer.class/instance/printDataOn..st
6
0%

Totals

Change from base Build 883099357:
-7.4%

Covered Lines:
107

Relevant Lines:
943

💛  - Coveralls


Duplicate to all artboards not working

I have just downloaded this plugin and tried running for the same example you have.
Created an shape in the 1024x1024 icon then selected that layer and run duplicate to all artboards. It duplicates the layer to the first (bottom) artboard, does not resize it or move it onto the canvas then stops and that is all that happens.

@buscarini  It was working fine few weeks ago but I tried running it today and it didn't work. It's duplicating the artwork  but not duplicating to the other artworks.

I want this plugin to work so badly! … but it isn't. No duplication at all, not even on the same art-board.
I'm on Sketch Version 3.3 (11970).
Here is a before and after screenshot:

Let me know if there is any other helpful information I can provide.

Still not working for me.

not working.

It doesn't work for me either :(
Same experience as @m0rourke

I'm so sorry about this, but I have been extremely busy for a long time. I tried to check this but I didn't have the time. I hope to be able to fix it in the future, but I can't say when.


ENG-11522: Deprecate log integration input variables

For sidecars v4.6+, these inputs will do nothing. They will be removed in the next major release.

@VictorGFM that's correct.


Unable to connect when $eth->eth_protocolVersion

`try {
// Connect to Ganache
$eth = new Ethereum('http://<IP_ADDRESS>:8545');
$eth->eth_getBalance()
        $result = $eth->eth_getBalance(["0xc94770007dda54cF92009BFF0dE90c06F603a09f","latest"]);
        var_dump($result);
    }
    catch (\Exception $exception) {
        die ("Unable to connect.");
    }`

return: syntax error, unexpected '$result' (T_VARIABLE)

Very good support for this library XDDDDDDDDDDDDDDDD

Payed support is available for this opensource project if you want.
JTorres @.***> schrieb am So., 24. März 2024, 20:13:

Very good support for this library XDDDDDDDDDDDDDDDD
—
Reply to this email directly, view it on GitHub
https://github.com/digitaldonkey/ethereum-php/issues/47#issuecomment-2016911085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADMSLVVDEXKT3SIXZEYHUTYZ4QU7AVCNFSM4KZOICGKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBRGY4TCMJQHA2Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


The helmrelease reconcillation is failed for ww-gitops and unable to access the UI with ingress set up

I am facing the below issue with the dashboard setup.
flux reconcile helmrelease ww-gitops ► annotating HelmRelease ww-gitops in flux-system namespace ✔ HelmRelease annotated ◎ waiting for HelmRelease reconciliation ✗ HelmRelease reconciliation failed: install retries exhausted
Using the below Kustomization
`apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
name: ww-gitops
namespace: flux-system
spec:
chart:
spec:
chart: weave-gitops
sourceRef:
kind: HelmRepository
name: ww-gitops
interval: 1h0m0s
values:
ingress:
enabled: true
hosts:
- host: xxx-xx.xxxx.io
ingressClassName: nginx-internal
annotations:
cert-manager.io/cluster-issuer: letsencrypt
path: /
pathType: Prefix
tls:
- secretName: xxx-xx.xxxx.io-tls
hosts:
- xxx-xx.xxxx.io
adminUser:
create: true
username: xxx
passwordHash: xxxx
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
name: ww-gitops
namespace: flux-system
spec:
interval: 1h0m0s
type: oci
url: oci://ghcr.io/weaveworks/charts `
`k describe po ww-gitops-weave-gitops-7db7c787df-b4fdt -n flux-system

kubectl describe po ww-gitops-weave-gitops-7db7c787df-b4fdt -n flux-system
Name:         ww-gitops-weave-gitops-7db7c787df-b4fdt
Namespace:    flux-system
Priority:     0
Node:         gke-ecom-dev-uc1-main-d8e1d673-gj5v/<IP_ADDRESS>
Start Time:   Mon, 26 Sep 2022 15:01:05 +0000
Labels:       app.kubernetes.io/instance=ww-gitops
app.kubernetes.io/name=weave-gitops
pod-template-hash=7db7c787df
Annotations:
Status:       Running
IP:           <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/ww-gitops-weave-gitops-7db7c787df
Containers:
weave-gitops:
Container ID:  docker://7a04e96a20095a7dc283b14784bebe34c7afdb5954dfd53429a3ec42073e35ed
Image:         ghcr.io/weaveworks/wego-app:v0.9.5
Image ID:      docker-pullable://ghcr.io/weaveworks/wego-app@sha256:a4bcb924074ddedfd4dedae35937734cc71b36e8ad39ff0c558b026c1ce26c43
Port:          9001/TCP
Host Port:     0/TCP
Args:
--log-level
info
--insecure
State:          Running
Started:      Mon, 26 Sep 2022 15:01:10 +0000
Ready:          True
Restart Count:  0
Liveness:       http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
Readiness:      http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:
WEAVE_GITOPS_FEATURE_TENANCY:  true
WEAVE_GITOPS_FEATURE_CLUSTER:  false
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-g8gmb (ro)
Conditions:
Type              Status
Initialized       True
Ready             True
ContainersReady   True
PodScheduled      True
Volumes:
kube-api-access-g8gmb:
Type:                    Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds:  3607
ConfigMapName:           kube-root-ca.crt
ConfigMapOptional:
DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type     Reason     Age                From               Message

Normal   Scheduled  19m                default-scheduler  Successfully assigned flux-system/ww-gitops-weave-gitops-7db7c787df-b4fdt to gke-ecom-dev-uc1-main-d8e1d673-gj5v
Normal   Pulling    19m                kubelet            Pulling image "ghcr.io/weaveworks/wego-app:v0.9.5"
Normal   Pulled     19m                kubelet            Successfully pulled image "ghcr.io/weaveworks/wego-app:v0.9.5" in 2.848372971s
Normal   Created    19m                kubelet            Created container weave-gitops
Normal   Started    19m                kubelet            Started container weave-gitops
Warning  Unhealthy  19m (x2 over 19m)  kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:9001/": dial tcp <IP_ADDRESS>:9001: connect: connection refused`

I wouldn't mark this as a bug, as it's not proved to be an issue with the helm-chart itself. I answered you on Slack, but I'll re-post it here. Even though your markdown doesn't render properly I recall this issue from the error-messages.
From the Helm chart's values-file, you need to indent the other ingress-related properties under that key. You also need to rename ingressClassName. Like so:
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: ww-gitops
  namespace: flux-system
spec:
  chart:
    spec:
      chart: weave-gitops
      sourceRef:
        kind: HelmRepository
        name: ww-gitops
  interval: 1h0m0s
  values:
    ingress:
      enabled: true
      hosts:
      - host: xxx-xxx-xxx.xxxx.io
      className: nginx-internal
      annotations:
        cert-manager.io/cluster-issuer: letsencrypt
      path: /
      pathType: Prefix
      tls:
      - secretName: xxx-xxx-xxx.xxxx.io-tls
        hosts:
        - xxx-xxx-xxx.xxxx.io
    adminUser:
      create: true
      username: xxxx
      passwordHash: xxx

---
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
  name: ww-gitops
  namespace: flux-system
spec:
  interval: 1h0m0s
  type: oci
  url: oci://ghcr.io/weaveworks/charts

If that doesn't work, I suggest you remove the ingress-stuff and try without it. Try using the gitops CLI to generate the most basic one. Follow instructions here
If it still doesn't work, please post the resulting resources generated from the HelmRelease (remove any sensitive data) here and I'll see if I can help you further.

Yes, it works with ingress now and all looks good.
Thank you.

Issue resolved.


Fix Array out of bounds error

Problem:
In the test.chpl file would go to Collapse Vertices, it would be looking for duplicates.
    writeln("Marking and Deleting Vertices...");
            var vertexSetDomain : domain(ArrayWrapper);
            var vertexSet : [vertexSetDomain] int;
            var l$ : sync bool;
            var numUnique : int;
            forall v in _verticesDomain with (+ reduce numUnique, ref vertexSetDomain, ref vertexSet) {
              var tmp = [e in _vertices[v].incident[0..#_vertices[v].degree]] e.id;
              var vertexArr = new ArrayWrapper();
              vertexArr.dom = {0..#_vertices[v].degree};
              **vertexArr.arr = tmp;**

When it would try to set the vertexArr.arr to tmp it would get an error chgl/src/modules/AdjListHyperGraph.chpl:521: error: halt reached - array index out of bounds: (3)
To solve this issue, we added a check  to see if the a.arr.size was >= than the b.arr.size to remove the error.
   proc ==(a: ArrayWrapper, b: ArrayWrapper) {
   +    if a.arr.size >= b.arr.size {
   +       return || reduce (b.arr == a.arr) ;
   +    }
        return && reduce (a.arr == b.arr);
   }

Thanks for the patch!


RFM - pencil

Current Maintainer

[ ] I am the maintainer of the package and wish to pass it to someone else;

Checklist

[x] Issue title starts with 'RFM - '

Existing Package Details
Package URL: https://chocolatey.org/packages/pencil
Package source URL: https://github.com/chocolatey-community/chocolatey-coreteampackages/tree/master/automatic/pencil

/confirm a.bejenaru

/confirm a.bejenaru

@abejenaru just a note, you only needed to add the /confirm command ones. For the rest it is enough to just check the box that you are the maintainer again, and the bot will be re-run (I think it will just fail when you are already confirmed).

New maintainer notes

This package is hosted in the GitHub chocolatey-coreteampackages repository, when picking up this request please do one of the following

After being added as a new maintainer, please open a PR to remove the package and icon from the repository if you want to host the package in your own repository.
After being added as a new maintainer, please open a PR to add yourself as a maintainer to the nuspec and CODEOWNERS files, if you want the package to still be hosted in that repository.