Bug: no-missing-import does not find index.js in import folder

Environment
Node version: 20.18.0
npm version: 10.8.2
ESLint version: 8
eslint-plugin-n version: 17.3.1
Operating System: MacOS
What rule do you want to report?
no-missing-import
Link to Minimal Reproducible Example
https://eslint-online-playground.netlify.app/#eNp1kDFvwyAQhf+Ky5JWcuzdWTt061J1KR0QXC1auEOAK1eR/3sPo0SOpWxw3+O9e5xFirqHWfngoPtOYhDWB4q5OXT9FzkDsbdoYD6cJO5JmYl2ddhKq40mTMSejsZHKV7AOXqQ4unEDzpIzmKOmpWErD1LbBopYM6AJkkxNB98W0VDBE3e8xyMFC2rgptGiwP2N+SzrR6VXjxwA1RMEF9DtrxYwWvoGqu9eoeYGJS5FE5lSJnTLopEU9Tw9hegCjyZyfG58EXiwp2C0j9qLF+4bWTg9xlCWRG1hV3s2u9OYoXH2ua42+sau/wDnveUww==
What did you expect to happen?
The index.js is the default when importing a folder
Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
import './folder/index';
import './folder';
The 2nd import shows the error, it is doing the same as the 1st

Hi, thank you for the report.
This is actually not a bug:
https://nodejs.org/api/esm.html#mandatory-file-extensions
Node requires both the full file path, and the file extension in esm mode.

Then lets close the issue. I'll added '/index.js' None the less I used it inside code which is afterwards converted to vanilla script


Use vue-meta to manage pages titles

https://www.npmjs.com/package/vue-meta
This refactoring is needed for SSR. To don't refer to document explicitly in the router.
https://github.com/aeternity/superhero-ui/blob/3b07c6deb19a60eddcca173baad7365936a51d0f/src/router.js#L194

implemented in #915


Chapter 7. Network Virtualization

Learning Objectives
By the end of this chapter, you should be able to:
        Discuss about the role of orchestration and management in open networking and NFV.
        Analyze integration touch points of modern networks and cloud environments.
        Discover open source orchestration platforms that can be integrated with business applications, OSS and BSS.

Fully Integrated Systems
In this chapter, we will start looking at the orchestration and virtual management layer on top of the network control layer. Virtual management refers to an orchestration platform which deals with tasks such as provisioning and spinning up virtual machines or containers to perform specific network and security tasks.
Orchestration and virtual management platforms interact with the network control layer to create and provision networking requirements such as policies, traffic redirection, and service insertion for the virtual workloads that they create.
The virtual management layer which we are referring to here is mainly intended to create workloads related to networking and security. It is not for general workloads and spinning up virtual servers to perform other enterprise applications (i.e. a database for a human resource management system).
In this chapter, we will also review the ONAP (Open Network Automation Platform) orchestration platform, as well as some other open source orchestration projects that interact with ONAP, such as CORD, Trellis and OSC (Open Security Controller). In addition, we will take a look at OPNFV, MANO, and Akraino.

Open Network Automation Platform (ONAP)
According to its ONAP's website,
"ONAP provides a comprehensive platform for real-time, policy-driven orchestration and automation of physical and virtual network functions that will enable software, network, IT and cloud providers and developers to rapidly automate new services and support complete lifecycle management".
Hosted by The Linux Foundation, ONAP is an open source project that started in March of 2017 as a response to the need of telcos and service providers to deliver on-demand network services leveraging the existing infrastructure. It is in fact a merger of two other projects: Open-O (China Telecom and ZTE) and Open ECOMP (AT&T).
ONAP - Quick Summary

Name
Open Network Automation Platform (ONAP)

By
The Linux Foundation

Where it runs
On separate hosts, recommended to run on Kubernetes or OpenStack

What it does
ONAP is a platform that orchestrates the lifecycle of virtual network services in a software defined networking environment

Features
Open source; creates services that consist of VNFs and policies. Runs and executes the services. Has a closed-loop.

What it can do out-of-the-box
ONAP relies on many other components and platforms; it will not be  able to deliver the real functions without the other components  out-of-the-box. There are multiple use cases for ONAP, such as uCPE, edge networking  services, Voice-over-LTE, virtual firewall, virtual DHCP server, etc. You can deploy a full or minimum ONAP environment using OpenStack. A  full ONAP environment requires numerous virtual machines and gigabytes  of RAM.

ONAP can be deployed with Kubernetes, OpenStack, or manually on your Linux flavor.
Key things to remember about ONAP:
It's a platform to orchestrate the lifecycle of VNFs in a software defined environment
It consists of multiple applications that integrate with each other
It is divided into two main functional frameworks: design time and run time.
ONAP Architecture
ONAP has a complex architecture with multiple applications and components that are integrated with each other.

ONAP is an orchestration platform for automation, service orchestration, network orchestration, and has  capabilities to orchestrate other services, such as security, physical network, and network function virtualization.
ONAP’s main target market is telco and service providers. However, cloud and datacenter providers and enterprises can leverage the benefits of ONAP for complete lifecycle automation of services that they would automate.
ONAP can help the acceleration of 5G for service providers by creating a dynamic, open standard environment for new 5G software services, such as network slicing, network function virtualization, edge computing and service function chaining.
ONAP Design Time Environment
The Design Time environment is a development framework with all the tools and repositories that administrators can use to create a service. A service consists of multiple elements and artifacts; the most important one is the VNF (Virtual Network Function), which should be packaged to run on different virtual environments and hypervisors.
Administrators create services and products using the Design Time environment; once they are validated, they will be transferred to the Service Catalog database of the Run Time. Run Time components will invoke the service details from Service Catalog when required in order to deploy the VNF in the virtual infrastructure.
The Design Time framework includes:
        Service Design and Creation (SDC)
        To define system assets and their policies.
        VNF Software Development Kit (VNFSDK) and VNF Validation Program (VVP)
        For VNF packaging and validation of VNFs.
        Policy Creation (POLICY)
        To define policies that need to be maintained or enforced.
        Closed Loop Automation Management Platform (CLAMP)
        To design and manage closed control loops.
        Optimization Framework (OOF)
        To optimize the application and services.

ONAP Run Time Environment
ONAP’s Run Time environment executes the service catalog and policies that were created and distributed by the Design Time framework. The Run Time invokes the services when they are requested by external parties (via the ONAP CLI, WEB GUI or API call), or it may get triggered by an internal process within the Run Time environment.
Following are the main components of the Run Time environment in ONAP:
        Service Orchestrator (SO)
        The Service Orchestrator is an automation engine in the ONAP Run Time environment. It processes and executes a list of tasks (i.e. a runbook) related to applying a service policy during the creation of the service, as well as altering and changing the service parameters. SO is also able to communicate with OpenStack.
        SO processes a runbook that may include tasks such as creating a virtual machine in OpenStack, creating virtual networks and assigning IP addresses from IPAM, applying security groups, creating service insertion or service chaining, etc.
        SO processing is very high level; it uses multiple components, drivers and southbound protocols to execute the work. SO has a full end-to-end view of the virtual infrastructure, network and applications.
        Software Defined Network Controller (SDNC)
        It is responsible for executing the network configuration.
        Application Controller (APPC)
        It is responsible for executing and configuring the Virtual Network Functions (VNF).
        Virtual Function Controller (VF-C)
        It is responsible for the lifecycle management of the Virtual Network Functions (VNF) which are run by the VNF manager.
        Active and Available Inventory (A&AI)
        It is responsible for the real-time view of system resources, products and their relationships.

ONAP: Closed Loop Automation
The Closed Loop Automation is one of the features of ONAP. This module proactively responds to network and service conditions without any human interaction. Closed Loop Automation components use the other components and plugins to detect problems in the network, and identify the appropriate remediation. For actions, the Closed Loop Automation will notify the Service Orchestrator or one of its controllers to take action and execute the change. The Closed Loop Automation can also generate alerts for operators, instead of automatically fixing the issues.

ONAP CLI
ONAP includes a command line interface, a web GUI, as well as APIs. The CLI can be used by the operator, as well as by automation tools to automate communication with ONAP. ONAP CLI provides the commands for the following features:
        ONAP microservice discovery
        ONAP external system and VNF cloud onboarding
        ONAP customer and subscription management
        ONAP product and service onboarding
        ONAP network service lifecycle management.

        An administrator creates a firewall service in the ONAP Design Time environment. The service will include the virtual firewall VM files that needs to run in the uCPE hypervisor (lets say uCPE is a compute node, part of OpenStack of ISP), as well as network parameters (the LAN/Trust and WAN/Untrust interfaces), IP addresses, firewall policies, NAT, DHCP server, DNS proxy configuration, and the network configuration that should dictate what packets from the subscriber must go to the firewall before going out.
        The ONAP Design Time environment validates the service and it will get transferred to the service catalog.
        A request comes from the ONAP CLI to deploy the virtual firewall for Subscriber-1.
        The ONAP Run Time environment starts fetching the service recipe from the service catalog and starts executing the process.
        ONAP Run Time uses different applications and plugins to create the virtual machine on Subscriber-1 uCPE, and create its network. After creating the firewall VM, it calls the API to the VNF manager (firewall manager software, in our example) to apply policies on the firewall to allow traffic out from the subscriber and perform source NAT.
        The ONAP Run Time uses its SDN manager to communicate with the underlay network to apply policies to route the return traffic from the underlay network to the virtual firewall.

As a super orchestrator, ONAP integrates with multiple virtual infrastructure management platforms, network management platforms, and control environments. Next, we will explore several such platforms used by ONAP to perform full orchestration: OpenStack, CORD, Trellis.

ONAP and OpenStack
OpenStack is a cloud orchestration platform. OpenStack is a virtual infrastructure management platform to manage compute, storage and virtual networking. You can compare OpenStack with the VMware suite of products, such as vSphere, NSX, and other components. OpenStack orchestrates compute, storage and networking to allow users to create virtual machines, create templates, migrate them between hosts, apply security groups, etc.
ONAP and OpenStack

The main components of OpenStack are:
        Heat (Orchestration)
        Nova (Manages hosts and hypervisors)
        Neutron (Virtual networking)
        Cinder and Swift (Manage object and block level storage)
        Horizon (Dashboard).

OpenStack Neutron is the networking component of OpenStack. Neutron is a network virtualization component that creates virtual networks between virtual workloads in the OpenStack environment. Neutron uses VXLAN as the default encapsulation mechanism to send traffic between the tenants (projects). Neutron can integrate with other SDN network controllers using a plugin.
In order to create and start Virtual Network Functions (VNFs), as well as to apply the virtual network settings (to connect the new VNF to the virtual networks within the OpenStack), ONAP has plugins and drivers to communicate with OpenStack. This will help users such as service providers to reuse their existing investments and infrastructure for OpenStack to deploy and manage the new VNFs. In addition, we need to remember that ONAP itself sets up and gets installed using OpenStack (or Kubernetes).

ONAP and CORD
CORD (Central Office Re-architected as a Datacenter) is a bundled platform of a virtualization platform (currently, OpenStack) and a network control layer (ONOS) that are orchestrated by CORD XOS. CORD has multiple other integrated components as well. CORD's aim is to transform the service providers' and telco's edge network into an agile model, flexible and ready to provide next generation services. The edge network normally refers to the location in the service provider network which connects to consumers and subscribers. The edge of the operator network (such as the central office for telcos and the head-end for cable operators) is where operators connect to their customers.
CORD is based on a completely integrated bundle of multiple open source projects. It aims to deliver an open, cloud-native, programmable and agile platform for service providers to leverage the SDN and NFV technologies and use this platform to build and deliver virtual network services to their consumers. CORD is built on commodity hardware and the latest designs of OCP (Open Compute Project) and cloud initiatives.

M-CORD (Mobile CORD)
Mobile CORD (M-CORD) targets mobile radio access and mobile core platforms. M-CORD provides a framework for carriers deploying 5G mobile networks. It includes virtualization of Radio Access Network (RAN), as well as Evolved Packet Core (EPC), the mobile core. By virtualizing the RAN and EPC, service providers can leverage the SDN and NFV technologies to create and build mobile edge applications and services.
M-CORD disaggregates the legacy RAN and EPC, allows service providers to use virtualized infrastructure to build an agile, software defined platform supporting the new initiatives of cloud and 5G.
The Role of M-CORD in a Mobile Service Provider Infrastructure

R-CORD (Residential CORD)
Residential CORD, or R-CORD, aims to leverage the SDN and NFV technologies to evolve the broadband services in the residential market. R-CORD doesn’t change the physical access method for subscribers. Instead, it utilizes the existing invested infrastructure based on different access technologies such as GPON, EPON, DOCSIS, etc.
Using its agile platform, R-CORD virtualizes the network services for subscribers, allows service providers to implement distributed network edge services as a virtual machine or a container such as CDN, DHCP, DNS, AAA (Authentication, Authorization, Accounting), VOD (Video On Demand), etc. R-CORD uses open source technologies such as OpenStack and ONOS to deliver services.
VOLTHA (Virtual OLT Hardware Abstraction), another open source project, abstracts the specialized concentrator access equipment (such as OLT, GPON, DOCSIS, head-end units) to make it OpenFlow-capable and be managed via OpenFlow and standard SDN controllers. This allows R-CORD to control this special purpose equipment.
R-CORD Architecture

E-CORD (Enterprise CORD)
Enterprise CORD, or E-CORD, aims to evolve the legacy WAN services that service providers are delivering to enterprise customers. E-CORD uses commodity hardware to create an infrastructure to run virtual network functions at different layers, such as customer premises (as a universal CPE), service provider central offices, etc. Using E-CORD, service providers will be able to provide agile and on demand services, such as:
        VPN
        Internet Access
        Firewall and border protection
        CDN (Content Delivery Network)
        Network core functions such as DNS, DHCP, etc.
        SD-WAN
        Traffic optimization and enhanced QoS
        Zero Touch Provisioning of commodity hardware at customer premises and sites
        Correctly measured monitoring services to deliver an outcome-based SLAs and KPIs
        A platform that enables creation and delivery of innovative services.

E-CORD Touch Points in a Service Provider Network

ONAP Communication with CORD
ONAP can use CORD as an underlay orchestrator component. ONAP and CORD both have open APIs that can be used for integration. Using CORD as an underlay for ONAP will reduce the workload on ONAP and its Service Orchestrator (SO), as the SO will be able to request CORD to build a whole infrastructure and service policies with a minimum number of tasks to be executed by ONAP’s SO.
The following diagram illustrates a high-level relationship between ONAP, CORD and other cloud platforms such as OpenStack.
High-Level Relationship between ONAP and Cloud Platforms

Trellis
Trellis is another open source project created and managed by ONF. Trellis is a networking project designed to deliver a standard L2/L3 leaf-spine switching fabric for datacenters leveraging the ONOS Controller. Trellis uses white box bare metal switches and open source software to create the underlying switching and packet forwarding hardware for a datacenter. Trellis uses the ONOS SDN controller to control the switches in the fabric. Trellis runs an agent software on white box switches to allow ONOS to manage the switches. There is no routing protocol or any networking software stack running on white box switches in the fabric. Trellis also includes multiple applications that run on ONOS and are used to manage the fabric, as well as provide monitoring, giving a detailed view of the datacenter network.
Leaf-Spine Design in a Datacenter

Apart from managing the physical underlay switches, Trellis also has capabilities to create and manage overlay networks in order to connect the isolated tenant networks on top of the underlay network. For external connectivity, Trellis provides a virtual router solution which makes the whole fabric act as a data plane for its distributed virtual router.
Trellis is also used as a component in the CORD platform, as a network infrastructure to provide connectivity to the CORD POD. However, Trellis can be used independently from CORD as a network platform for a datacenter.
High-Level Architecture of Trellis in a Datacenter

Trellis Architecture
The main components of Trellis are:
        ONOS SDN controller.
        A set of Trellis applications that run on ONOS.
        Trellis agent software that runs on top of ONL on a white box switch. This agent is actually an Indigo OpenFlow agent that communicates with the switch silicon SDK or the driver.
        Trellis management UI and northbound APIs.

Trellis Components on a White Box Switch

ONAP Integration with Trellis
In order to execute the processes required in networking to redirect traffic for Virtual Network Functions (VNFs) it manages and automates, ONAP can control Trellis using plugins and APIs.

Open Source MANO
OSM or Open Source MANO (Management And Orchestration) is an open source project hosted by ETSI for development of NFV Management and Orchestration, aligned with the ETSI NFV architecture. It has an operator-led community and offers production-ready an open source MANO stack that meets the requirements of commercial VNFs.
OSM didn’t start from scratch, but as an integration of:
        OpenMANO as the seed Resource Orchestrator
        Riftware as the seed Service Orchestrator
        Juju as an external reference for VNF configuration and management.

OSM is a tight integration of existing open source modules from Telefonica’s OpenMANO project, Rift.io orchestrator and Canonical’s Juju Charms as VNFM. OSM works with virtualization platforms such as AWS EC2, VMware vCloud Director, etc.
The OSM project consists of three basic components:
Service Orchestrator (SO)
SO is responsible for the end-to-end service orchestration and provisioning of VNFs and service chaining. SO manages the automation workflow for service deployment. OSM uses RIFT.io as orchestration engine.
Resource Orchestrator (RO)
RO is responsible to communicate with virtualization platforms such as OpenStack and VMware. RO provisions the NFV virtual workloads on virtualization platforms.
VNF Configuration and Abstraction (VCA)
VCA is responsible for the configuration of VNFs that are provisioned by the Resource Orchestrator. OSM uses Canonical’s Juju Charms as an automation engine to apply the required configuration to the provisioned VNFs.

OSM vs ONAP
OSM and ONAP are similar. Initial versions of OSM had limited capabilities. However, there are new features being introduced in recent releases of OSM. ONAP’s scope is bigger than OSM. ONAP is a comprehensive service management orchestration platform, but OSM is mainly a Virtual Network Function Orchestrator (VNFO).

Open Platform for NFV (OPNFV)
According to OPNFV's website,
"Open Platform for NFV (OPNFV) facilitates the development and evolution of NFV components across various open source ecosystems. Through system level integration, deployment and testing, OPNFV creates a reference NFV platform to accelerate the transformation of enterprise and service provider networks".
OPNFV is hosted by The Linux Foundation and aims to create a standard-grade NFV platform. Its current objective is to create a standard open source platform for Virtual Network Functions in order to run on different platforms. For example, if OpenStack and VMware vSphere are both OPNFV-certified, we can load an OPNFV-certified VNF (such as a virtual load balancer) on any of these certified platforms and expect a similar functional behavior.
Current Scope of OPNFV

The initial phase of OPNFV is limited to building standards for the NFV infrastructure (NFVI) and Virtualized Infrastructure Management (VIM).

Open Security Controller (OSC)
Open Security Controller (OSC) is an open source software defined security orchestration solution hosted by The Linux Foundation. OSC automates the deployment and provisioning of Virtualized Network Security Functions (VNSC), which can provide on-demand protection between workloads (East-West) as well as filtering traffic to and from outside networks (North-South). The foundation of OSC is based on Network Function Virtualization, which allows distributed and flexible provisioning of virtual security appliances such as IPS, IDS, WAF and Firewalls within the network.
Unlike traditional network security physical appliances, where a very limited number of large firewalls are used to protect the resources, the new distributed security systems utilize virtual network functions, which can be distributed anywhere in a cloud environment, rather than on a whole site or datacenter POD.
In order to create and provision virtual machines or containers that can provide a network function, OSC has tight integration with virtual management platforms such as OpenStack, Kubernetes, etc. This is called Virtual Network Function (VNF), and the technology is referred to as Network Function Virtualization (NFV) in industry terms.
Open Security Controller - Quick Summary

Name
Open Security Controller (OSC)

By
The Linux Foundation

Where it runs
On a Linux host

What it does
Provision  virtual firewall, IPS, and other components. Communicate with SDN  controllers to create service chaining and ensure traffic is routed via  the provisioned security functions.

What it can do out-of-the-box
OSC  has built-in capabilities to integrate with OpenStack and Kubernetes to  provision firewalls and other virtual security services.

For example, if OSC receives a policy to enforce all traffic going from Virtual Machine A to Virtual Machine B to pass via a firewall, the OSC will perform the following high-level actions:
        Call an API on virtual machine management platform (i.e. OpenStack) to provision a virtual machine using the base image of virtual firewall, along with the networks that it needs to connect to.
        Virtual machine management platform (i.e. OpenStack) provisions the virtual machine, reports back the Virtual Machine details, such as IP address, MAC address allocated for this VNF, etc.
        OSC calls the API to the network control layer (i.e OpenDaylight or Tungsten Fabric) to create a service chain that sends all traffic from VM A to this newly created VNF.

This is the main duty of OSC: to build an infrastructure for provisioning security components. In addition, OSC also has some capabilities to perform other security-related tasks, such as applying security policies.
OSC can also be used directly by cloud tenants. Tenants can choose their required controls from a catalog of security service functions and create a logical service policy to add a virtual security function such as a virtual firewall, virtual IPS, virtual WAF or virtual load balancer, and define how the traffic should route towards the virtual security services.
OSC Architecture
OSC interacts with multiple systems within a cloud environment. For example, it interacts with the SDN controller, virtual machine management and security function managers.
Open Security Controller Conceptual Architecture

OSC Interactions
OSC provides a web GUI, as well as northbound APIs for management. In order to create a new network security function (i.e. IPS/Firewall) and redirect the network traffic to that specific service, security administrators can use the web interface to define security policies and interact with OSC. OSC’s northbound APIs allow other systems to interact with OSC to provision network security functions. For example, cloud platforms can be integrated with OSC, to allow a tenant to create and manage security services.
As far as southbound communications are concerned, OSC communicates with three different systems:
        Virtualization management systems
        OSC includes a connector to communicate with virtualization management systems such as OpenStack and Kubernetes. This connector directly calls the Virtual Infrastructure Manager (VIM) APIs in order to provision virtual network security functions. OSC Virtualization Management plugin also subscribes to notification events from the VIM system in order to receive information and status related to provisioned virtual network security workloads (virtual machines or containers).
        SDN controllers
        OSC supports communication with multiple networking and SDN controllers. OSC has a built-in connector that works with multiple SDN controllers. OSC uses the SDN controller plugin to implement traffic redirection or Service Function Chaining (SFC) to send specific traffic to the newly created network security function.
        Security Function Managers
        OSC uses this connector to communicate with security function systems such as IPS manager, firewall manager, security policy manager, etc. Using this plugin, OSC will be able to call the Security Function Manager APIs to apply specific policy updates, device group membership settings, etc., to the newly created virtual network function.

OSC Use Case: Microsegmentation
OSC can be used to implement microsegmentation in OpenStack. With OSC, the logical group of workloads can be protected via a dedicated Virtual Network Security Function.
Open Security Controller - Microsegmentation

In addition, OSC can place the VNSF on different physical hosts to ensure high availability and efficiency.
Microsegmentation will help the datacenter and enterprise infrastructure team to not make any changes on their existing physical firewalls or deploy any new firewalls. Microsegmentation and the use of VNSF will eliminate any changes on physical security devices and OSC will automate the provisioning workloads of VNSF.
OSC Use Case: Segmentation within a Multi-Tenant Environment
Another use case of microsegmentation is the traffic isolation between tenants in a multi-tenant environment. Cloud service providers will be able to use OSC to inject a virtual security function between tenants if they need to establish communication with each other.
OSC can provision simple IPS/IDS for traffic traversing between the two tenants to ensure the tenants are protected from attacks and malware that may come from another tenant.
OSC Multi-Tenancy Use Case

Microsegmentation is designed to provide isolation and service insertion using the shared infrastructure. It does not require new infrastructure.

Akraino Edge Stack
Akraino Edge Stack is a new open source project hosted by The Linux Foundation (as of February 2018). It is still in its early stages, and the source code and wiki are not yet publicized (as of July 2018). The project:
"will create an open source software stack to improve the state of edge cloud infrastructure for carrier, provider and IoT networks".
The Akraino Edge Stack code is contributed by AT&T and Intel Corporation:
        AT&T contributed a software stack designed for carrier scale edge computing applications running in virtual machines and containers.
        Intel has committed to open source key components of its Wind River Titanium Cloud portfolio, as well as Intel's Network Edge Virtualization Software Development Kit (NEV SDK).

Akraino's goal is to develop a fully virtualized edge platform based on OpenStack, Kubernetes and ONAP.
Akraino's Proposed Architecture

Learning Objectives (Review)
You should now be able to:
        Discuss about the role of orchestration and management in open networking and NFV.
        Analyze integration touch points of modern networks and cloud environments.
        Discover open source orchestration platforms that can be integrated with business applications, OSS and BSS.

Summary
In this chapter, we reviewed ONAP, the super orchestrator for open source networking. ONAP has many capabilities and use cases due to its design; it can integrate with multiple external OSS (Operational Support System) and BSS (Business Support System) in service providers, as well as other applications. We also talked about CORD and Trellis and how they are accelerating the evolution in service provider networks, in order to simplify the service deployment and reduce the time to market. Then, we looked at OSC (Open Security Controller), a software defined security platform for applying security profiles as virtual network functions in different locations in a network.
These are all possible thanks to a programmable and software defined network that is able to re-route and send specific traffic to a VNF whenever it is activated, or re-route the traffic once the VNF is obsolete or removed.


Add support for .NET 4.6.1 for clip V2 libraries

PR for https://github.com/michielpost/Q42.HueApi/issues/271

Thanks!


Cargo multiple bin linting

Hello,
When you use the default way to build multiple binaries with cargo, this SublimeLinter doesn't handle this correctly and throw me this error:
extra arguments to `rustc` can only be passed to one target, consider filtering
the package by passing e.g. `--lib` or `--bin NAME` to specify a single target

I tried to add custom args in the sublimeLinter Config User file but, it seems they are given to rustc and not handled by cargo...
My file tree:

src/

bin/

server.rs
client.rs

Thanks !

Does this still occur if you use the new cargo check option?

I didn't try... Sorry

Seems not to work for me, or I don't know how to pass options to cargo or rust via the 'custom args' settings in the sublimeLinter Config User file

Cargo check needs to fix this :disappointed:
https://github.com/rsolomo/cargo-check/issues/4


How to debug queries?

I get some errors on prepareData
{ [Error: fetchWithRetries(): Still no successful response after 1 retries, giving up.]
  response:
   Body {
     url: 'http://localhost:4000/graph',
     status: 400,
     statusText: 'Bad Request',
     headers: Headers { _headers: [Object] },
     ok: false,
     body:
      PassThrough {
        _readableState: [Object],
        readable: true,
        domain: null,
        _events: [Object],
        _eventsCount: 7,
        _maxListeners: undefined,
        _writableState: [Object],
        writable: true,
        allowHalfOpen: true,
        _transformState: [Object] },
     bodyUsed: false,
     size: 0,
     timeout: 0,
     _raw: [],
     _abort: false } }

I guess that is because 400 is returned from graphql endpoint. How I can get string representing query?
How you could debug this ?

For example you can write a query logger on the GraphQL server or in a custom relay network layer. Or place a request logging proxy before GraphQL server.


Chapter 6 example does not behave as described in the book.

On docker-compose up and a curl -I http://{DOCKER_HOST}/holdings as suggested on page 141, the curl-call bails out with a AttributeError: module 'holdings.queries_cached' has no attribute 'Holdings'.
I would expect it to trace the 3 calls tried.

Actually it tries to import it from wrong file, it had to be holdings.queries


[E2E]Not able to see access rights for default vmgroup

Steps mentioned in  #1396

I discussed it with Sam, since the product behavior  regarding the default vmgroup is still under discussion and we have not reached the conclusion yet (see #1397 ), so move this issue to future.

Not sure why the original issue was closed. At any rate, the original one says
Tried to see access rights for _DEFAULT vmgroup
Failed with error:
Please init configuration with 'vmdkops_admin.py config init' before changing it.

The behavior is correct. When config is not inited, there is no concept of vmgroups and no access control.
We should change a message to something like the one below. No other code changes IMO
Configuration is not initialized.
No vmgroups  are defined, no quotas or access control is supported.
If you are trying to change it, first initialized configuration with  'vmdkops_admin.py config init'

At least we should have consistent behavior for showing vmgroup and access rights. Marking as mustfix.

as discussed during the meeting, the workflow would be verified manually and during flash sprint automation will be added.
@ashahi1 Let's verify manually and add automation test during Flash sprint


Ci publish: Add release workflow/job, publish-latest job

The new release workflow uses action "pipe-cd/actions-gh-release". This action uses file RELEASE in the root. When that file is modified in a PR, and contains a new release tag, it will trigger a release upon the PR being merged. The action will create a git tag in the repo and the corresponding GitHub release, containing auto-generated release notes, that can be later edited by a committer.
The new release will in turn trigger the new "publish-latest" job (ci-cd workflow), which will publish the new version of the package to npm.
Also made little improvements to package.json

I successfully tested locally, publishing to a npm registry, using verdaccio.

I have tested yarn publish:latest:ci locally using verdaccio and it seems to work.

Thanks for the review!


Translate courses

Add courses to the db translation system, so that their names and descriptions can be translated. This includes a new patch posting system using middleware instead of the old Handler system, which changes how patches are submitted. Currently for other collections, their I18N Views try to figure out whether to save changes or create a patch. But the I18NEditCourseView always submits patches, and then the server endpoint decides if it should accept the changes immediately. This should guard against lost diplomat translations, where if the server can't accept changes for whatever reason, the changes at least get saved to the db where they can be analyzed and recovered later.

Need to copy styling from article editor to course editor. Mainly have the save button float right.


Attributes without whitespace between them is not valid html

https://github.com/ErikHen/PictureRenderer/blob/5b2f95d9708a0421e7684f29b5f7c609b3dad4a7/PictureRenderer/Picture.cs#L88
could you please add white space between the attributes!

I tried to find information if it was valid or not when I built it. Now I have taken a look in the W3C XML (=XHTML) specification, and it seems that you are correct. Will change it asap.
Thanks


recieving updates but not posting on CurseForge/Modrinth? Why

Just wondering as i just found this mod, it would be nice if there was more of a wiki on what to do in this mod

I will be volunteering answering questions if you want. Just reply to this!

Ok. Why are there being github release published, but not cf/modrinth updates

I'm not the creator, so I can't answer that... I thought you wanted to ask questions on the "wiki" that is not present. I can help better on that.

4.x hasn't been uploaded anywhere because it's broken.


No Redirect on IOS

I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
its just do nothing after i logged in succesfull in keycloak, i can click done but nothing happens.
i created in the app an listener
   App.addListener('appUrlOpen', (url) => {       console.log('appUrlOpen', url);     });
and i get following in the app console
⚡  TO JS {"iosSourceApplication":"com.apple.SafariViewService","iosOpenInPlace":"","url":"myapp:\/\/app\/capacitor:\/localhost\/properties?pathAfterAuth=properties&socialLogin=false&isSearching=null#state=*SOME_STATE*&session_state=9... ⚡  [log] - appUrlOpen
Expected behavior:
that the IOS BrowserTab close and that the AuthToken obj is in localstorage to get me logged in in my app
BrowserTab is not reacting on this.browsertab.close i think or cause the app is call via "appUrlOpen"

i have tested something in the appUrlOpen listener i added this.browserTab.close and it worked
sooo something is not working with this framework on IOS


Thread 'main' panicked at 'Trick: if you are running on a vm' when machine is not a VM

Bug description
Running scaphandre on bare metal (no VM) produces the following error, even though the machine is not a virtual machine:
Scaphandre stdout exporter
Sending ⚡ metrics
thread 'main' panicked at 'Trick: if you are running on a vm, do not forget to use --vm parameter invoking scaphandre at the command line', src/sensors/mod.rs:263:18
stack backtrace:
   0: rust_begin_unwind
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/std/src/panicking.rs:493:5
   1: core::panicking::panic_fmt
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/core/src/panicking.rs:92:14
   2: core::option::expect_failed
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/core/src/option.rs:1292:5
   3: core::option::Option<T>::expect
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/core/src/option.rs:349:21
   4: scaphandre::sensors::Topology::add_cpu_cores
             at ./src/sensors/mod.rs:259:26
   5: <scaphandre::sensors::powercap_rapl::PowercapRAPLSensor as scaphandre::sensors::Sensor>::generate_topology
             at ./src/sensors/powercap_rapl.rs:106:9
   6: <scaphandre::sensors::powercap_rapl::PowercapRAPLSensor as scaphandre::sensors::Sensor>::get_topology
             at ./src/sensors/powercap_rapl.rs:112:24
   7: scaphandre::exporters::stdout::StdoutExporter::runner
             at ./src/exporters/stdout.rs:122:24
   8: <scaphandre::exporters::stdout::StdoutExporter as scaphandre::exporters::Exporter>::run
             at ./src/exporters/stdout.rs:19:9
   9: scaphandre::run
             at ./src/lib.rs:74:9
  10: scaphandre::main
             at ./src/main.rs:81:5
  11: core::ops::function::FnOnce::call_once
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Adding the "--vm" argument gives (and still does not work):
scaphandre::sensors::powercap_rapl: Powercap_rapl path is: /var/scaphandre
Scaphandre stdout exporter
Sending ⚡ metrics
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/sensors/powercap_rapl.rs:76:53
stack backtrace:
   0: rust_begin_unwind
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/std/src/panicking.rs:493:5
   1: core::panicking::panic_fmt
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/core/src/panicking.rs:92:14
   2: core::result::unwrap_failed
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/core/src/result.rs:1284:5
   3: core::result::Result<T,E>::unwrap
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/core/src/result.rs:1037:23
   4: <scaphandre::sensors::powercap_rapl::PowercapRAPLSensor as scaphandre::sensors::Sensor>::generate_topology
             at ./src/sensors/powercap_rapl.rs:76:23
   5: <scaphandre::sensors::powercap_rapl::PowercapRAPLSensor as scaphandre::sensors::Sensor>::get_topology
             at ./src/sensors/powercap_rapl.rs:112:24
   6: scaphandre::exporters::stdout::StdoutExporter::runner
             at ./src/exporters/stdout.rs:122:24
   7: <scaphandre::exporters::stdout::StdoutExporter as scaphandre::exporters::Exporter>::run
             at ./src/exporters/stdout.rs:19:9
   8: scaphandre::run
             at ./src/lib.rs:74:9
   9: scaphandre::main
             at ./src/main.rs:81:5
  10: core::ops::function::FnOnce::call_once
             at /build/rustc-h1hlaa/rustc-1.51.0+dfsg1+llvm/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Reloading the rapl kernel modules, and restarting the machine does not seem to change anything.
To Reproduce
cargo build
./target/debug/scaphandre stdout

Expected behavior
Something should happen :)
Environment
Linux Distribution: Ubuntu 18.04.5 LTS
Linux Kernel: 5.14.15-051415-generic (Also had issues with 5.04)
>> lsmod | grep rapl

intel_rapl_msr         20480  0
intel_rapl_common      24576  1 intel_rapl_msr
rapl                   20480  0

>> ls /sys/class/powercap
dtpm  intel-rapl  intel-rapl:0

>> lshw -short

H/W path             Device          Class          Description
===============================================================
                                     system         System Product Name
/0                                   bus            WS X299 SAGE
/0/1                                 memory         64KiB BIOS
/0/4a                                memory         System Memory
/0/4a/0                              memory         16GiB DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/4a/1                              memory         16GiB DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/4a/2                              memory         16GiB DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/4a/3                              memory         16GiB DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/54                                memory         System Memory
/0/54/0                              memory         16GiB DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/54/1                              memory         16GiB DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/54/2                              memory         16GiB DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/54/3                              memory         16GiB DIMM DDR4 Synchronous 2667 MHz (0.4 ns)
/0/5e                                memory         896KiB L1 cache
/0/5f                                memory         14MiB L2 cache
/0/60                                memory         19MiB L3 cache
/0/61                                processor      Intel(R) Core(TM) i9-9940X CPU @ 3.30GHz
/0/2                                 memory
/0/3                                 memory
/0/100                               bridge         Sky Lake-E DMI3 Registers
/0/100/4                             generic        Sky Lake-E CBDMA Registers
/0/100/4.1                           generic        Sky Lake-E CBDMA Registers
/0/100/4.2                           generic        Sky Lake-E CBDMA Registers
/0/100/4.3                           generic        Sky Lake-E CBDMA Registers
/0/100/4.4                           generic        Sky Lake-E CBDMA Registers
/0/100/4.5                           generic        Sky Lake-E CBDMA Registers
/0/100/4.6                           generic        Sky Lake-E CBDMA Registers
/0/100/4.7                           generic        Sky Lake-E CBDMA Registers
/0/100/5                             generic        Sky Lake-E MM/Vt-d Configuration Registers
/0/100/5.2                           generic        Intel Corporation
/0/100/5.4                           generic        Intel Corporation
/0/100/8                             generic        Sky Lake-E Ubox Registers
/0/100/8.1                           generic        Sky Lake-E Ubox Registers
/0/100/8.2                           generic        Sky Lake-E Ubox Registers
/0/100/14                            bus            200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
/0/100/14/0          usb1            bus            xHCI Host Controller
/0/100/14/0/e                        input          AURA Custom Human interface
/0/100/14/1          usb2            bus            xHCI Host Controller
/0/100/14.2                          generic        200 Series PCH Thermal Subsystem
/0/100/16                            communication  200 Series PCH CSME HECI #1
/0/100/17                            storage        200 Series PCH SATA controller [AHCI mode]
/0/100/1b                            bridge         200 Series PCH PCI Express Root Port #17
/0/100/1b.4                          bridge         200 Series PCH PCI Express Root Port #21
/0/100/1b.4/0                        storage        NVMe SSD Controller SM981/PM981
/0/100/1b.4/0/0      /dev/nvme0      storage        Samsung SSD 970 EVO Plus 2TB
/0/100/1b.4/0/0/1    /dev/nvme0n1    disk           2TB NVMe namespace
/0/100/1b.4/0/0/1/1                  volume         511MiB Windows FAT volume
/0/100/1b.4/0/0/1/2  /dev/nvme0n1p2  volume         1862GiB EXT4 volume
/0/100/1c                            bridge         200 Series PCH PCI Express Root Port #1
/0/100/1c.2                          bridge         200 Series PCH PCI Express Root Port #3
/0/100/1c.2/0        enp4s0          network        I210 Gigabit Network Connection
/0/100/1d                            bridge         200 Series PCH PCI Express Root Port #9
/0/100/1d/0                          bus            ASMedia Technology Inc.
/0/100/1d/0/0        usb3            bus            xHCI Host Controller
/0/100/1d/0/1        usb4            bus            xHCI Host Controller
/0/100/1d.2                          bridge         200 Series PCH PCI Express Root Port #11
/0/100/1d.2/0                        bus            ASMedia Technology Inc.
/0/100/1d.2/0/0      usb5            bus            xHCI Host Controller
/0/100/1d.2/0/1      usb6            bus            xHCI Host Controller
/0/100/1f                            bridge         X299 Chipset LPC/eSPI Controller
/0/100/1f.2                          memory         Memory controller
/0/100/1f.3                          multimedia     200 Series PCH HD Audio
/0/100/1f.4                          bus            200 Series/Z370 Chipset Family SMBus Controller
/0/100/1f.6          eno1            network        Ethernet Connection (2) I219-LM
/0/101                               bridge         Sky Lake-E PCI Express Root Port A
/0/101/0                             bridge         PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
/0/101/0/8                           bridge         PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
/0/101/0/10                          bridge         PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
/0/4                                 generic        Intel Corporation
/0/6                                 generic        Sky Lake-E RAS Configuration Registers
/0/7                                 generic        Intel Corporation
/0/8                                 generic        Sky Lake-E CHA Registers
/0/8.1                               generic        Sky Lake-E CHA Registers
/0/8.2                               generic        Sky Lake-E CHA Registers
/0/8.3                               generic        Sky Lake-E CHA Registers
/0/8.4                               generic        Sky Lake-E CHA Registers
/0/8.5                               generic        Sky Lake-E CHA Registers
/0/8.6                               generic        Sky Lake-E CHA Registers
/0/8.7                               generic        Sky Lake-E CHA Registers
/0/9                                 generic        Sky Lake-E CHA Registers
/0/9.1                               generic        Sky Lake-E CHA Registers
/0/9.2                               generic        Sky Lake-E CHA Registers
/0/9.3                               generic        Sky Lake-E CHA Registers
/0/9.4                               generic        Sky Lake-E CHA Registers
/0/9.5                               generic        Sky Lake-E CHA Registers
/0/9.6                               generic        Sky Lake-E CHA Registers
/0/9.7                               generic        Sky Lake-E CHA Registers
/0/a                                 generic        Sky Lake-E CHA Registers
/0/11                                generic        Sky Lake-E CHA Registers
/0/e                                 generic        Sky Lake-E CHA Registers
/0/e.1                               generic        Sky Lake-E CHA Registers
/0/e.2                               generic        Sky Lake-E CHA Registers
/0/e.3                               generic        Sky Lake-E CHA Registers
/0/e.4                               generic        Sky Lake-E CHA Registers
/0/e.5                               generic        Sky Lake-E CHA Registers
/0/e.6                               generic        Sky Lake-E CHA Registers
/0/e.7                               generic        Sky Lake-E CHA Registers
/0/f                                 generic        Sky Lake-E CHA Registers
/0/f.1                               generic        Sky Lake-E CHA Registers
/0/f.2                               generic        Sky Lake-E CHA Registers
/0/f.3                               generic        Sky Lake-E CHA Registers
/0/f.4                               generic        Sky Lake-E CHA Registers
/0/f.5                               generic        Sky Lake-E CHA Registers
/0/f.6                               generic        Sky Lake-E CHA Registers
/0/f.7                               generic        Sky Lake-E CHA Registers
/0/10                                generic        Sky Lake-E CHA Registers
/0/10.1                              generic        Sky Lake-E CHA Registers
/0/1d                                generic        Sky Lake-E CHA Registers
/0/1d.1                              generic        Sky Lake-E CHA Registers
/0/1d.2                              generic        Sky Lake-E CHA Registers
/0/1d.3                              generic        Sky Lake-E CHA Registers
/0/1e                                generic        Sky Lake-E PCU Registers
/0/1e.1                              generic        Sky Lake-E PCU Registers
/0/1e.2                              generic        Sky Lake-E PCU Registers
/0/1e.3                              generic        Sky Lake-E PCU Registers
/0/1e.4                              generic        Sky Lake-E PCU Registers
/0/1e.5                              generic        Sky Lake-E PCU Registers
/0/1e.6                              generic        Sky Lake-E PCU Registers
/0/0                                 bridge         Sky Lake-E PCI Express Root Port A
/0/0/0                               bridge         PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
/0/0/0/8                             bridge         PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
/0/0/0/8/0                           display        NVIDIA Corporation
/0/0/0/8/0.1                         multimedia     NVIDIA Corporation
/0/0/0/8/0.2                         bus            NVIDIA Corporation
/0/0/0/8/0.2/0       usb7            bus            xHCI Host Controller
/0/0/0/8/0.2/1       usb8            bus            xHCI Host Controller
/0/0/0/8/0.3                         bus            NVIDIA Corporation
/0/0/0/10                            bridge         PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch
/0/0/0/10/0                          display        NVIDIA Corporation
/0/0/0/10/0.1                        multimedia     NVIDIA Corporation
/0/0/0/10/0.2                        bus            NVIDIA Corporation
/0/0/0/10/0.2/0      usb9            bus            xHCI Host Controller
/0/0/0/10/0.2/1      usb10           bus            xHCI Host Controller
/0/0/0/10/0.3                        bus            NVIDIA Corporation
/0/13                                generic        Intel Corporation
/0/14                                generic        Sky Lake-E RAS Configuration Registers
/0/18                                generic        Intel Corporation
/0/19                                generic        Intel Corporation
/0/1a                                generic        Intel Corporation
/0/1b                                generic        Intel Corporation
/0/1c                                generic        Intel Corporation
/0/a.2                               generic        Intel Corporation
/0/a.3                               generic        Intel Corporation
/0/a.4                               generic        Intel Corporation
/0/a.5                               generic        Intel Corporation
/0/a.6                               generic        Intel Corporation
/0/a.7                               generic        Intel Corporation
/0/b                                 generic        Intel Corporation
/0/b.1                               generic        Intel Corporation
/0/b.2                               generic        Intel Corporation
/0/b.3                               generic        Intel Corporation
/0/c                                 generic        Intel Corporation
/0/c.1                               generic        Intel Corporation
/0/c.2                               generic        Intel Corporation
/0/c.3                               generic        Intel Corporation
/0/c.4                               generic        Intel Corporation
/0/c.5                               generic        Intel Corporation
/0/c.6                               generic        Intel Corporation
/0/c.7                               generic        Intel Corporation
/0/d                                 generic        Intel Corporation
/0/d.1                               generic        Intel Corporation
/0/d.2                               generic        Intel Corporation
/0/d.3                               generic        Intel Corporation
/0/5                                 generic        Intel Corporation
/0/5.2                               generic        Sky Lake-E RAS Configuration Registers
/0/5.4                               generic        Intel Corporation
/0/12                                generic        Sky Lake-E M3KTI Registers
/0/12.1                              generic        Sky Lake-E M3KTI Registers
/0/12.2                              generic        Sky Lake-E M3KTI Registers
/0/15                                generic        Sky Lake-E M2PCI Registers
/0/16                                generic        Sky Lake-E M2PCI Registers
/0/16.4                              generic        Sky Lake-E M2PCI Registers
/0/17                                generic        Sky Lake-E M2PCI Registers
/0/1f                scsi3           storage
/0/1f/0.0.0          /dev/sda        disk           8001GB ST8000DM004-2CX1
/0/20                scsi5           storage
/0/20/0.0.0          /dev/sdb        disk           8001GB ST8000DM004-2CX1
/0/21                scsi7           storage
/0/21/0.0.0          /dev/sdc        disk           8001GB ST8000DM004-2CX1
/1                                   power          To Be Filled By O.E.M.

Hi ! Thanks for noticing this bug.
What I see in the details you provided makes me think you are running kind or a "new" version of powercap: https://docs.kernel.org/power/powercap/dtpm.html
You have an extra "dtpm" forlder but no RAPL domain-specific folder under intel-rapl:0 (in mainstream cases you get 0:0, :0:1 :0:2 for example).
We need to investigate this, as we have never seen this mode running on other machines. I guess this is related to your pretty recent cpu (i9) too.

Thanks for the reply! Let me know if we can do anything to help. I've also linked a gist of the full folder structure for /sys/class/powercap - which may be helpful in debugging.
https://gist.github.com/DavidMChan/21037f7a126f0e6a112ab691785f0e51

Hey
I got the same issue with Intel Xeon Gold proc and Fedora CoreOS sys (working on OKD4 with OVH Cloud)
CPU family:                      6
Model:                           85
Model name:                      Intel(R) Xeon(R) Gold 6226R CPU @ 2.90GHz

[root@worker-0 5.12.7-300.fc34.x86_64]# podman run -v /sys/class/powercap:/sys/class/powercap -v /proc:/proc -ti hubblo/scaphandre --vm stdout -t 15
scaphandre::sensors::powercap_rapl: Powercap_rapl path is: /var/scaphandre
Scaphandre stdout exporter
Sending ⚡ metrics
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/sensors/powercap_rapl.rs:76:53`

[root@worker-0 powercap]# pwd
/sys/class/powercap
[root@worker-0 powercap]# ls
dtpm

[root@worker-0 powercap]# lsmod | grep intel_rapl
intel_rapl_msr         20480  0
intel_rapl_common      28672  1 intel_rapl_msr

Thanks for noticing, I'll push info on this thread when there is something new.

Hey, did you manage for this issue ? I can provide you more infos or we can program a workshop in order to investigate

Hi @DavidMChan, @jules-delecour-dav.
I should be able to work on this issue in february. The issue I'll quickly run into is that I don't have access to any machine with an i9 or equivalent cpu. Would you be able to share a remote access to a server or desktop with those caracteristics to help troubleshoot ? (so, probably for february, then)
Thanks

Hi @bpetit  - do you have time to add a quick outline of what needs to be done? (i.e. where I should start looking to adjust the ingestion of the data, and what needs to be updated...) If so, I can take a look at creating a PR for this issue which might be a bit easier than trying to get you access to one of our machines.

Hi ! Of course. The first thing to do would surely be to :

find if the intel_rapl and intel_rapl_msr modules are available on recent kernels
(seems to be appropriate to test on 5.12 and above)
if they are working properly on i9
if they are still providing data in /sys/class/powercap folder
if one of those 3 conditions are not met, document it, so that we find another way to make scaphandre work on i9 or equivalent cpus (maybe #78 or #

A great extra would be to provide some docs for #137 in the mean time, as you will propably go through the steps required to be documented.
Just as a reference #140 seems related, in some way.

Hi @bpetit, i can create a vm and give you access to it
I'll send you connexion access when it will be created

Hi, hitting the same issue (Ubuntu 20.04.3 LTS, GNU/Linux 5.13.0-28-generic x86_64).
Intel(R) Core(TM) i9-10900X CPU @ 3.70GHz

root@node:~$ lsmod | grep rapl
intel_rapl_msr         20480  0
intel_rapl_common      24576  1 intel_rapl_msr
rapl                   20480  0

root@node:~$ ll /sys/class/powercap
total 0
drwxr-xr-x  2 root root 0 feb  9 10:47 ./
drwxr-xr-x 85 root root 0 feb  9 10:47 ../
lrwxrwxrwx  1 root root 0 feb  9 10:47 dtpm -> ../../devices/virtual/powercap/dtpm/
lrwxrwxrwx  1 root root 0 feb  9 10:47 intel-rapl -> ../../devices/virtual/powercap/intel-rapl/
lrwxrwxrwx  1 root root 0 feb  9 14:14 intel-rapl:0 -> ../../devices/virtual/powercap/intel-rapl/intel-rapl:0/

Can read from /sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj (but do not see subzone directories)
root@node:~$ cat /sys/class/powercap/intel-rapl/intel-rapl\:0/energy_uj
174924188972

Hi !
Thanks for those informations. @pingenglj
@jules-delecour-dav if need access to a physical machine with an i9 cpu to reproduce this error. A vm wouldn't do it. But thanks !

Hello @bpetit ,
I am trying to propagate metrics from my host machine (ubuntu 22.04) to my vm (also ubuntu 22.04). But when making ./scaphandre --vm prometheus, i obtain that :
scaphandre::sensors::powercap_rapl: Powercap_rapl path is: /var/scaphandre
Scaphandre prometheus exporter
Sending \u26a1 metrics
Press CTRL-C to stop scaphandre
thread 'main' panicked at 'Trick: if you are running on a vm, do not forget to use --vm parameter invoking scaphandre at the command line', src/sensors/mod.rs:263:18
stack backtrace:
0:     0x5579f1858a36 - std::backtrace_rs::backtrace::libunwind::trace::h610d887740cf1987
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
1:     0x5579f1858a36 - std::backtrace_rs::backtrace::trace_unsynchronized::h5247907892598408
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
2:     0x5579f1858a36 - std::sys_common::backtrace::_print_fmt::h163eb591d48f053c
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/sys_common/backtrace.rs:67:5
3:     0x5579f1858a36 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hd5f6fdeadc182c0b
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/sys_common/backtrace.rs:46:22
4:     0x5579f188b4ac - core::fmt::write::hab5e32ad139dc64f
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/core/src/fmt/mod.rs:1149:17
5:     0x5579f184a725 - std::io::Write::write_fmt::hda56003ffc07f403
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/io/mod.rs:1697:15
6:     0x5579f184cc60 - std::sys_common::backtrace::_print::hcad41b2400bee496
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/sys_common/backtrace.rs:49:5
7:     0x5579f184cc60 - std::sys_common::backtrace::print::h2782dac9fb8841ed
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/sys_common/backtrace.rs:36:9
8:     0x5579f184cc60 - std::panicking::default_hook::{{closure}}::heb06a17e9362a548
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panicking.rs:211:50
9:     0x5579f184c7ee - std::panicking::default_hook::h3d84794a36de0246
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panicking.rs:228:9
10:     0x5579f184d213 - std::panicking::rust_panic_with_hook::h6c9f137ff9fef51a
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panicking.rs:606:17
11:     0x5579f18593a0 - std::panicking::begin_panic_handler::{{closure}}::h2877cd4e6462e1cb
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panicking.rs:502:13
12:     0x5579f1858b84 - std::sys_common::backtrace::__rust_end_short_backtrace::h6f8a54cfa7a7d4a3
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/sys_common/backtrace.rs:139:18
13:     0x5579f184cd52 - rust_begin_unwind
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panicking.rs:498:5
14:     0x5579f12a54e1 - core::panicking::panic_fmt::he8875066124331b8
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/core/src/panicking.rs:107:14
15:     0x5579f1885ee1 - core::panicking::panic_display::hcc6252ba93313e49
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/core/src/panicking.rs:63:5
16:     0x5579f12a55db - core::option::expect_failed::h92d1dc3d07d26094
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/core/src/option.rs:1637:5
17:     0x5579f12b37bf - scaphandre::sensors::Topology::add_cpu_cores::h292edf12ceacb0dc
18:     0x5579f12ef23d - <scaphandre::sensors::powercap_rapl::PowercapRAPLSensor as scaphandre::sensors::Sensor>::generate_topology::ha40f60e38f4f0dd7
19:     0x5579f12ef62d - <scaphandre::sensors::powercap_rapl::PowercapRAPLSensor as scaphandre::sensors::Sensor>::get_topology::hd1f10b9842a4494a
20:     0x5579f12fdfba - <scaphandre::exporters::prometheus::PrometheusExporter as scaphandre::exporters::Exporter>::run::h4f4fa4bdb9a727cb
21:     0x5579f12b7c6c - scaphandre::run::hfd14dfaef5c665f1
22:     0x5579f12a7667 - scaphandre::main::h44c89ca42efb3fb8
23:     0x5579f12a5f43 - std::sys_common::backtrace::__rust_begin_short_backtrace::hff0c6ad7bcf5e558
24:     0x5579f12a5f19 - std::rt::lang_start::{{closure}}::h8f69d29914e3e657
25:     0x5579f1847c71 - core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once::hd220f9373558aca3
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/core/src/ops/function.rs:259:13
26:     0x5579f1847c71 - std::panicking::try::do_call::hce771ab8e2469e1b
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panicking.rs:406:40
27:     0x5579f1847c71 - std::panicking::try::hdcd46bc7121f05a6
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panicking.rs:370:19
28:     0x5579f1847c71 - std::panic::catch_unwind::h220bff361500ce4b
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panic.rs:133:14
29:     0x5579f1847c71 - std::rt::lang_start_internal::{{closure}}::h9c7d2a04b3782841
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/rt.rs:128:48
30:     0x5579f1847c71 - std::panicking::try::do_call::hf862adda5d81a53e
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panicking.rs:406:40
31:     0x5579f1847c71 - std::panicking::try::hef41490d9308414a
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panicking.rs:370:19
32:     0x5579f1847c71 - std::panic::catch_unwind::h351e79fc6ca7598f
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/panic.rs:133:14
33:     0x5579f1847c71 - std::rt::lang_start_internal::h039e34ac72710a33
at /build/rustc-oOlesr/rustc-1.58.1+dfsg1~ubuntu1/library/std/src/rt.rs:128:20
34:     0x5579f12a7832 - main
35:     0x7fede17d1d90 - __libc_start_call_main
at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
36:     0x7fede17d1e40 - __libc_start_main_impl
at ./csu/../csu/libc-start.c:392:3
37:     0x5579f12a5ac5 - _start
38:                0x0 -

@DavidMChan would it be, by any chance, possible to access your machine for the tests (or another with the same cpu) ?

Sure! Can you send me an email/DM, and I can work out how to get you ssh access to a machine.

Hi @bpetit , unfortunately Im still getting an exception (on branch #131), let me know if I can check/verify anything for you:
user@node:~/git/scaphandre$ sudo RUST_BACKTRACE=1 ./target/debug/scaphandre stdout -t 15
Scaphandre stdout exporter
Sending ⚡ metrics
thread 'main' panicked at 'Trick: if you are running on a vm, do not forget to use --vm parameter invoking scaphandre at the command line', src/sensors/mod.rs:263:18
stack backtrace:
   0: rust_begin_unwind
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/std/src/panicking.rs:498:5
   1: core::panicking::panic_fmt
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/panicking.rs:107:14
   2: core::panicking::panic_display
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/panicking.rs:63:5
   3: core::option::expect_failed
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/option.rs:1637:5
   4: core::option::Option<T>::expect
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/option.rs:709:21
   5: scaphandre::sensors::Topology::add_cpu_cores
             at ./src/sensors/mod.rs:259:26
   6: <scaphandre::sensors::powercap_rapl::PowercapRAPLSensor as scaphandre::sensors::Sensor>::generate_topology
             at ./src/sensors/powercap_rapl.rs:106:9
   7: <scaphandre::sensors::powercap_rapl::PowercapRAPLSensor as scaphandre::sensors::Sensor>::get_topology
             at ./src/sensors/powercap_rapl.rs:112:24
   8: scaphandre::exporters::stdout::StdoutExporter::runner
             at ./src/exporters/stdout.rs:121:24
   9: <scaphandre::exporters::stdout::StdoutExporter as scaphandre::exporters::Exporter>::run
             at ./src/exporters/stdout.rs:19:9
  10: scaphandre::run
             at ./src/lib.rs:74:9
  11: scaphandre::main
             at ./src/main.rs:81:5
  12: core::ops::function::FnOnce::call_once
             at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

@geertpingen Hi, thanks for the feedback.
Are you running on a physical machine ? and built https://github.com/hubblo-org/scaphandre/pull/198 ?
Thanks

Hi @bpetit, you are too fast :smile:  I was too quick and pulled the wrong branch, it seems to work on first observation!
user@node:~/git/scaphandre$ sudo RUST_BACKTRACE=1 ./target/debug/scaphandre stdout -t 15
Scaphandre stdout exporter
Sending ⚡ metrics
scaphandre::sensors::powercap_rapl: Couldn't find domain folders from powercap. Fallback on socket folders.
scaphandre::sensors::powercap_rapl: Scaphandre will not be able to provide per-domain data.
Measurement step is: 2s
Host:   0 W
Top 5 consumers:
Power           PID     Exe
No processes found yet or filter returns no value.
------------------------------------------------------------

Host:   29.331151 W
Socket0 29.331152 W |

Top 5 consumers:
Power           PID     Exe
1.676065 W      918     "gitlab-runner"
0.838032 W      14      "rcu_sched"
0.838032 W      780     "systemd-resolve"
0 W     1       "systemd"
0 W     2       "kthreadd"

Great, thanks for the feedback ! Happy testing !

A new fresh test of #198 on @DavidMChan's machine seems to work properly with stdout and prometheus exporters.

Thanks @bpetit  - This seems to be working on our other machines as well! (Sorry for the delayed test!)

Thank you for the feedback !


Add support for rgw loadbalancer based on haproxy & keepalived

This is a basic version of a loadbalancer solution for multiple rgw instances.
It includes:

An infrastructure playbook for haproxy & keepalived setup -- rgw-loadbalancer.yml
An infrastructure playbook for purging -- purge-rgw-loadbalancer.yml
Roles definition for haproxy & keepalived

Any comment(s) would be highly appreciated :)

hi @leseb, any comments on this one?

@guihecheng interesting! adding a couple of reviewers

@mattbenjamin oh, nice to see you here, matt, thanks for your help!
Actually, I've tried haproxy & keepalived in our production environment, but we are not experts on haproxy & keepalived,we really need all variable suggestions from all the reviewers :)

hi all, I've updated a version with some changes:

merge the extra playbook into site.yml, this mainly intends to let the option configure_firewalld to control the behavior of haproxy and keepalived firewall settings.
add haproxy and keepalived firewall settings.
merge haproxy and keepalived role into rgw-loadbalancer role

@leseb hi, any interest to review the new version ?
There's quite a lot of changes~

ping @leseb ?

maybe @guits  or @dsavineau  can have a look at the updated version ?

@guits merged the lb purging stuff into existing purge-cluster.yml, thanks.

ping @guits @leseb

@guihecheng we're almost there.
I know it's been a while, thanks for your patience!

@guits thanks for your comments, I've adopted the changes, hopt it works this time :)

@guihecheng If I run ./generate_group_vars_sample.sh in your branch I get this diff:
diff --git a/group_vars/rgwloadbalancers.yml.sample b/group_vars/rgwloadbalancers.yml.sample
index 76fab9f7..0784a2d8 100644
--- a/group_vars/rgwloadbalancers.yml.sample
+++ b/group_vars/rgwloadbalancers.yml.sample
@@ -14,10 +14,4 @@ dummy:
 ###########

 #haproxy_frontend_port: 80
-#
-#virtual_ips:
-#   - <IP_ADDRESS>
-#   - <IP_ADDRESS>
-#
-#virtual_ip_netmask: 24
-#virtual_ip_interface: ens33
+

@guits yes, I added these samples by hand, because it is impossible to pick defaults values for these virtual ip information, users could only arrange their virtual ips by themselfs.
But here, I still want to give examples as a hint, so I added these.

@guihecheng so you can leave them commented out in roles/ceph-rgw-loadbalancer/defaults/main.yml
we must keep each sample file synced with its corresponding defaults/main.yml

@guits updated, thanks~

not sure what's wrong with mergify, merging anyway.

How do you handle ssl with haproxy deployed by this ansible role?

@secret104278  look at https://github.com/ceph/ceph-ansible/blob/master/group_vars/rgwloadbalancers.yml.sample#L18


Fixed issue where pressing form button on sub-list view was blowing up.

Fixed to not show toolbars when pressing Manage Policies button, there shouldnt be toolbar buttons on forms.
Fixed code to build @view when user pressed save/cancel buttons on forms performain tasks such as Editing Tags or Managing Policies from sub-list view screens. Moved show_association, show_details methods to a common module and removed individual methods from other controllers.

https://bugzilla.redhat.com/show_bug.cgi?id=1193847
@dclarizio please review/test.

Verified fix.


fix(scripts): noEmit appears to no longer be supported with references

In typescript, if there are multiple references we cannot use noEmit (see here and here) so this needs to be turned off in those situations. Also enabling incremental mode to help speed up build/check times.
Found this issue again in tablekit-next branch which didn't seem to be fixed last time.

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in<EMAIL_ADDRESS>:rocket:


Some systems failed to build for Quicklisp dist

Building with SBCL 2.0.5 / ASDF 3.3.1 for quicklisp dist creation.
Trying to build commit id b0429e8cb4565365f90d3e30b7d964d02e115c95
with-c-syntax-test fails to build with the following error:
Unhandled UNDEFINED-FUNCTION in thread #<SB-THREAD:THREAD "main thread" RUNNING {1000A18083}>: The function WITH-C-SYNTAX.LIBC:|ilogb| is undefined.

with-c-syntax fails to build with the following error:
Unhandled UNDEFINED-FUNCTION in thread #<SB-THREAD:THREAD "main thread" RUNNING {1000A18083}>: The function WITH-C-SYNTAX.LIBC:|ilogb| is undefined.

Full log here

Confirmed. I will fix it soon.


Update must gather image workflow

Let's fix the action for must gather, and add multi arch build to it.

/lgtm

Excellent


Adding travis config

Fixes #343

If anyone connects this repository to Travis. I can see if this configuration is working fine or not?

@therewasaguy can you review this?

thank you, @iFlameing, this'll be great!
I don't have owner permissions for Processing or for this repo, so I can't add it to travis-ci.org. @lmccart are you able to grant me permission or help with this?

this is great. I need to do some work to look into our travis status, right now it's spread across https://travis-ci.com and https://travis-ci.org and I need to sort and consolidate that. so it may be a while, but once I've got that set I will add in p5.js-sound and see if I can also give you access @therewasaguy. thanks for your patience :)

sounds good, thanks @lmccart ! This'll be good to set up when you get a chance, no rush.

closed with https://github.com/processing/p5.js-sound/pull/355


Add context parameter to some database functions

To avoid deadlock problem, almost database related functions should be have ctx as the first parameter.
This PR do a refactor for some of these functions.

How many functions are missing?

How many functions are missing?

What did you mean?

I've already reviewed quite a few PRs that only added ctx params.
How many more will there be?

I've already reviewed quite a few PRs that only added ctx params. How many more will there be?

I can just say there are still over 500 db.DeaultContext are using except test files.


Fix enqueue_lazy_method_definition! on Ruby <2.5

The enqueue_lazy_method_definition! method in HasLazilySpecializedMethods calls define_method directly, rather than using send to call it.
This means that the method doesn't work on any Ruby version prior to 2.5, which consequently breaks T::Struct.
Motivation
Fixes #2743
Test plan
As this is specific to a particular Ruby version, this could be tested by extending the Buildkite sorbet-runtime tests to run on 2.4 as well as 2.6.3.

Great. I was about to look into this issue 🏃


Wheels validation is broken

This URL used in the wheel validation process doesn't work:
https://raw.githubusercontent.com/home-assistant/wheels-custom-integrations/master/components/$domain.json

https://github.com/hacs/action/runs/1338680521?check_suite_focus=true#step:3:252 ?

https://github.com/nielsfaber/scheduler-component/pull/46/checks?check_run_id=1353523897#step:3:328 ...

scheduler.json does not exist https://github.com/home-assistant/wheels-custom-integrations/tree/master/components
https://raw.githubusercontent.com/home-assistant/wheels-custom-integrations/master/components/scheduler.json

Well it looks like it forgot to template it.

Ooops, sorry, I was confused.

Well this repository has no dependencies, so it shouldn't need to be added.

Any updates on this? The previous one only failed if it needed to be in there and it wasn't in there.


DCOS-14692: split up external volumes

Checklist

[x] Did you add a JIRA issue in a commit message or as part of the branch name?
[ ] Did you add new unit tests?
[ ] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

Can one of the admins verify this patch?

There are conflicts, but this is working well! :ship:

Thanks John, I rebased this branch against the base.


Lighten up regexp to allow other shells than bash

Allows the extension to work with shells like zsh and sh as the
previous regexp was specifically targetting bash.

I found that this solved the problem in many shells. It's definitely possible to create a more powerful regex to handle even more shells in one regex but I figured you might want to see if there's any demand for that before making the code way harder to reader.

Thanks! Applied it in a single regexp

Thanks @rauchg!


Add support for Cinder volumes

Please add support for Cinder volumes in templates.
I would suggest two different behaviors:

Cinder volume would be created with slave and deleted with slave. User will specify cinder volume size.
User manually creates cinder volume and this volume would be specified in slave template and volume would be connected to provisioned slave.

Makes sense to me. #2 would share the volume with all slaves provisioned this way, right?

#2 would share the volume with 1 slave, so in this case template should be limited to just 1 slave.
I do not think, that cinder volume could be linked with more than 1 slave.

@jkopriva, what would be the use-case for an exclusively used persistent drive?

@olivergondza It could be for example when you have one slave used for nexus repository - you do not have to delete this drive, but sometimes you want to restart slave, but anyway, this is a special case, first approach would be used much more often.

I have a related use case that could use #2 but since I also use the shared volume for file caching, it would be better to allow #3.
3.  Multiple provisioned slave VMs, are sharing a long lived disk volume, for a combination of read + write access.
My main use case, is that I launch around 80 Jenkins jobs from a buildflow (will migrate to pipeline later), in parallel.  Each launched Jenkins job, saves the test result files.  After the buildflow completes the parallel job execution, a report job is started that reads the test results from each completed job and writes them to the shared disk volume test result files and generates a web report and sends email.  The test result files are proprietary format.
As @jkopriva mentioned, cinder volume can not be linked with more than 1 slave,which I think is mentioned in this proposal for changing that.  Or, perhaps Cinder has already addressed multi-attach-volume, as mentioned here..
In summary, I really need #2 but could make use of #3, if that became an option, which is why I am invading this issue with my additional (optional #3) request (if that makes sense to also include).

+1.
It would be useful when a Jenkins slave requires a large storage.

I have got this change in progress though it was postponed weeks ago due to other work coincidentally in the same plugin.

How are we doing?

I have pushed a simple patch allowing boot from volume with images at #194.

Support fo booting from volume (https://github.com/jenkinsci/openstack-cloud-plugin/pull/195) was released in 2.32.

Support fo booting from volume (https://github.com/jenkinsci/openstack-cloud-plugin/pull/195) was released in 2.32.

Will anything more happen on this topic? The #195 addressed only the first use-case in which the volume is created by the plugin but does not address the second use-case in which the user specifies the volume by himself and it's just attached to the instance.

@Ziomalon, the fact only a half of this was addressed is the reason I am keeping this open. Personally, I do not have the motivation to address that part. Any takers?

I would also like to have this 2. feature. It would be a really nice way to speed up building as non-persistent volumes cause a build from scratch while this would allow incremental builds. Or is there another good workaround for getting incremental builds?


Add support for Page Up / Page down (channel buttons) on iOS remote control

Summary
This adds support for the Channel Up/Down buttons on the iOS control center remote control.
Changelog
[TVOS] [Added] - Add support for Channel Up/Down buttons on iOS control center remote control.
Test Plan
Add a TV event handler that logs eventType, open the Apple TV remote on an iPhone and press channel up/down to see the new pageUp/Down events

Thanks a lot @BryanRolfe !!! I'll test this out and get it merged soon.

Thanks @douglowder - I was going to take care of these changes this weekend but you beat me to it!

NP @BryanRolfe and thanks again for adding this!


Clarification in SignInManager.signIn method

It would be really helpful to clarify something in the information about the signIn method here:
https://ucwa.skype.com/reference/WebSDK/interfaces/_s4b_sdk_d_.jcafe.signinmanager.html#signin
The text gives a set of examples of how to use signIn with different auth types (OAuth, IWA, login/password, etc.).  What it doesn't talk about is which of these auth types are actually supported with the different Skype for Business products.
For example, it is our understanding from some of the other help topics (like this one: https://msdn.microsoft.com/en-us/skype/websdk/developwebsdkappsforsfbonline) that for Skype for Business Online, OAuth is the preferred login type, and IWA is not supported with that product.
Would be great to clarify or link to another topic that explains which auth types makes sense based on the product type, and possibly which types are recommended.
Thanks!

Great feedback. I'll bring that to the developers who are responsible for the reference docs.

For Skype for Business Online OAuth is the only supported login type right now. That is why the article at https://msdn.microsoft.com/en-us/skype/websdk/developwebsdkappsforsfbonline uses only OAuth based sign in.
For Skype for Business On Premises there are a few auth types supported. These are explained in the documentation at https://msdn.microsoft.com/en-us/skype/websdk/developforskypeforbusiness
I'll update the second article to reflect that it is for Skype for Business onprem.


Desktop wallet product improvement2: Top account switch

Top account switch， content of modification：

Displays more detailed account information and profile information more detailed
Migrate the exit program here
Migrate profile password changes here
Add deletion of profile
Add account deletion
Add Mnemonic backup
Import the seed account or private key account

Refer to the model（please ignore other parts of product)

pending mockup review


Make Cloudfront auth more configurable

For continuous delivery reasons and improved security it would be better the secrets and other variables could be externalized.
The variables could be passed in as environment variables for example.

This is an important point to bring up. Externalizing would be a good addition to the project.
Unfortunately, Lambda@Edge has some limitations in that it does not support environment variables. With that said, the next best thing may be to support AWS Parameter Store. This will require a bit more conversation on how to best implement it into the build process. Always open to suggestions on implementation and externalization methods.

#38


Hindi Readme for multilinguals

New Readme can be written in Hindi to help multilinguals.

Please assign me this issue under iwoc and easy/medium/hard.

@A91y In this case , create a separate file for it and in the actual readme file of the project, mention a special link to that file


Global/default values for all tooltips

It'd be really great if in the ember-cli-build.js file we an specify global defaults for all tooltips in the application, something like this
var EmberApp = require('ember-cli/lib/broccoli/ember-app');

module.exports = function(defaults) {
  var app = new EmberApp(defaults, {
    'ember-cli-tooltipster': {
      importTooltipsterPunk: true,
      defaults: {
        animationDuration: 100,
        theme: 'tooltipster-light'
      }
    }
  });

  return app.toTree();
};

I'm open to putting the configuration in other places, but I just want a way to set all tooltips a specific setting without having to go to every single tooltip.
Thanks!

I just published version 0.5.0 that allows global values through ENV config.
In your config/environment.js try to add e.g
 ENV['ember-cli-tooltipster'] = {
    animation: 'swing',
    theme: 'tooltipster-light'
  };

This should set the options. However if options are set in the component they will override these ones.
Try this and let me know if it solves your case or if you find any issues.

@altrim oh my that was quick. Great work! And I just tested it; works like a charm!! Much appreciated!


query result table: "save as markdown table"

Is your feature request related to a problem? Please describe.
I write documentations in a WIKI using markdown. And I need to insert results from sql queries into the documentation. I want to insert them not as screenshot but as markdown table.
Describe the solution or feature you'd like
I want to request a "save as markdown" (additional to the existing "save as csv", "save as json", ...) to the result windows (in queries and in notebooks)
Describe alternatives you've considered
My current solution:

I save the result as JSON
I use the online converter https://tableconvert.com/ to convert from JSON into markdown

Shouldn't this issue be closed? It's already possible to save as markdown


DataFusion HashJoin LeftAnti doesn't support null aware anti join

Describe the bug
During working on https://github.com/apache/datafusion-comet/pull/437, a few Spark join tests are failed when delegating to DataFusion HashJoin.
It is because that DataFusion HashJoin LeftAnti Join returns incorrect results when it is a null aware anti join.
To Reproduce
Added a test to join.slt:
statement ok
CREATE TABLE IF NOT EXISTS test_table(c1 INT, c2 INT) AS VALUES
(1, 1),
(2, 2),
(3, 3),
(4, null),
(null, 0);

query II
SELECT * FROM test_table t1 WHERE (c1 NOT IN (SELECT c2 FROM test_table)) = true
----
4 NULL
NULL 0

Expected behavior
Above query should return empty relation.
Additional context
No response

I'll just add one more example here in order to show that the problem is related not only to non-correlated subqueries
CREATE TABLE IF NOT EXISTS test_table(c1 INT, c2 INT) AS VALUES
(1, 1),
(2, 2),
(3, 3),
(4, null),
(4, 7),
(null, 0);

SELECT * FROM test_table t1 WHERE c1 NOT IN (SELECT c2 FROM test_table t2 where t1.c1 = t2.c1);
+----+----+
| c1 | c2 |
+----+----+
| 4  |    |
| 4  | 7  |
|    | 0  |
+----+----+

while PG returns
CREATE TABLE
INSERT 0 6
 c1 | c2
----+----
    |  0
(1 row)


Web configurator pin restriction due to Boards.json

On PCB with Flatbox pinout certain used pins are restricted from being set within the web configurator. This corresponds with www/src/Data/Boards.json. Removal of said restrictions or override possibility (for validation errors) could help.

I also experienced some issues with the web configurator because of this. My DIY board uses the Adafruit KB2040 as its microcontroller and it uses pin 29,


corrected the validations.py

Fixes #6528 6528

It's a good idea to open an issue first for discussion.

@Xplod4432 can you merge?

Closes: #1
Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.


Generate complete 3d point cloud of indoor room

Required Info

Camera Model
L515&D455

Firmware Version
v2.50

Operating System & Version
win10

Kernel Version (Linux Only)

Platform
PC

SDK Version
v2.50

Language
python

Segment
{Robot/Smartphone/VR/AR/others }

Generate complete point cloud of indoor room
Hi,
i really want to generate a 3d point cloud of the indoor room. I have looked through many issues but i cannot find the answer of my question.
I only want to use one camera (L515 or D455) and take a scan of the whole room, then I want to get the point cloud. Is that possible with the sdk? Please give me some advices if you have ideas.
Thank you so much!

Hi @Yiiii19  A whole-room scan could be achieved with the RealSense SDK's C++ example program rs-kinfu, which builds upa point cloud as a single camera is moved around the scene by "fusing" frames together.  When you are satisifed with the level of detail on the pointcloud then you can export it to a .ply format pointcloud data file.
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/opencv/kinfu
There is not an equivalent frame-fusion script for Python, unfortunately.
If you are able to use a commercial pre-made software solution then DotProduct Dot3D for Windows and Android is compatible with D455 and L515 and can generate room scans with a single camera.  It has a free trial version and a Pro version for scanning larger scenes.
https://www.dotproduct3d.com/
The YouTube link below has an Intel video demonstration of room scanning with an L515 and Dot3D Pro.
https://www.youtube.com/watch?v=41Yu2H9_z3w


{appservice} Replace fabric/invoke w/parallel-ssh

Related command
az appservice
Description
The parallel-ssh module is backed by the libssh/libssh2 libraries. This increases speed, reduces overhead, and allows for FIPS compliance. Fabric/invoke require paramiko and it makes FIPS compliance difficult.
In addition, parallel-ssh could be used for ssh tunnels (in the batchai command module) in a separate PR. Currently, batchai uses the sshtunnel package (which also requires paramiko) to make those connections.
Testing Guide
The testing process is unchanged.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

appservice

Small typo in that last push. Fixed it up.

Nevermind on this one for now.


Function "implicitAccountId" referenced but not defined

At ln. 37 in near.js there is the following assignment:
    const id = accountId || implicitAccountId(publicKey)

However, implicitAccountId is declared nowhere.
If this is what you have intended, I can change this part as below, and open a PR for that:
const id = accountId

ah, i must have removed at one point -- good catch. Feel free to open PR


Remove header paths from CMakeLists.txt.

Codecov Report
Base: 23.34% // Head: 23.34% // No change to project coverage :thumbsup:

Coverage data is based on head (8958881) compared to base (4ad9535).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           stable     #477   +/-   ##
=======================================
  Coverage   23.34%   23.34%
=======================================
  Files          63       63
  Lines        5731     5731
  Branches      311      311
=======================================
  Hits         1338     1338
  Misses       4345     4345
  Partials       48       48

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


drawing lines in map view where long. < -180 or long. > 180 puts the_geom data in longitude range [-540,-180], [180,540], etc., so they don't display on map

@namessanti noticed this bug
Should there be an float mod(long,360) call somewhere to correct this?
Procedure to recreate bug:

Make an empty table
Switch to map view
Create a new point, line, or polygon
Go ±360° to the left or right (that is, go to the next Africa to the left/right :), create a new point, line, or polygon and it will seem to not appear
Check out Data View to see that they were created but shifted by ±360°, so it doesn't display on map view. If you go ±360° more, it continues to shift but not remain in view.

Example map data here

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Doc Feedback: The below documentation is not relevant to the API Manager

Location : https://apim.docs.wso2.com/en/latest/use-cases/streaming-usecase/use-cases/

@nadeesha5814 , can you be more specific please.

@sajithshn , please clarify.

Hi Mariangela, This issue is no longer relevant, hence u can close it.


[WHIS-63] Add s3 read/write permissions to eks worker node

[WHIS-63] Add s3 read/write permissions to eks worker node

We can externalize the policy document from module eks-cluster to the main tf file.

Hi Duan,
Please review updated terraform code. It seems to do the right thing, but I didn't aspplied it to the cluster before your confirmation.
Note that I left cdn bucket creation inside cloudfornt-s3. And s3 module will manage creation of all other buckets , except of cdn. Cause I found no way to pass cdn bucket details from s3 module to cloudfront-s3.


Plugin ID Mismatch

I keep getting "Plugin ID Mismatch" when i try to install this plugin. My obsidian version is v0.9.11

This seems to come from Obsidian's internals but I can't figure out why. As a shot in the dark, maybe I used something in the plugin that is incompatible with Obsidian 0.9.11 (I used 0.9.12). I'll try to investigate more thoroughly early next week, but hopefully 0.9.12 will be formally released by then and maybe it will solve the issue.

P.S: just in case, please try to delete the directory VAULT_ROOT/.obsidian/obsidian-rtl if you have it, then restart Obsidian and retry to install.

@esm7 thanks for this plugin.
I also use v0.9.11 and had same issue. I also tried to download the plugin zip and decompress it into VAULT_ROOT/.obsidian/obsidian-rtl but it's not working.
Appreciate if this issue can be resolved soon.

Ok, I believe the issue that the released file is not for "Obsidian RTL". It is for "Obsidian Vimrc Support".
Here is what I found in manifest.json file:
{
  "id": "obsidian-vimrc-support",
  "name": "Obsidian Vimrc Support",
  "version": "0.1.0",
  "description": "Auto-load a startup file with Obsidian Vim commands.",
  "author": "esm",
  "authorUrl": "",
  "isDesktopOnly": false
}

Great catch, sorry for the confusion! I fixed the release, please let me know if it works now.

Installed, activated and switching LTR<>RTL successfully.
Thanks for your fast support.


outdated versions of dat should give nice error messages

It'd be cool if outdated dats could be detected and give a nice message to say 'Hey, update your dat' with a link to instructions on how to do that. And then if you want the stack trace you can add --verbose or --debug or something.
Connecting to dat network...
/Users/karissa/node_modules/dat/node_modules/append-tree/index.js:636
      if (offset >= buf.length) throw new Error('Invalid index')
                                ^

Error: Invalid index
    at Tree._inflate (/Users/karissa/node_modules/dat/node_modules/append-tree/index.js:636:39)
    at Tree._list (/Users/karissa/node_modules/dat/node_modules/append-tree/index.js:132:24)
    at /Users/karissa/node_modules/dat/node_modules/append-tree/index.js:112:10
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

What version was the dat created with? I thought we had a nice message for the last breaking change, but haven't seen it for awhile so maybe could have regressed.

@joehand I realized that this is actually a hyperdb dat..

@joehand I realized that this is actually a hyperdb dat..

ah cool! We will definitely have nice messages for that down the road. In the meantime we can use https://github.com/joehand/dat-next