How to launch application when HoloLens is on the rig

Hi,
Currently when I'm using spectator view, I have 2 hololens, both not on the rig. I launch both applications manually and then position the spectator view hololens on the camera (not very accurate but just for testing). I'm confused on how I could launch spectator view when one hololens is mounted rigidly on the rig and I am unable to launch the app manually.

This issue may be in the wrong repository.
MRtK's Spectator View does not require a rig.
You may want to reopen this issue in the https://github.com/Microsoft/MixedRealityCompanionKit

You can launch the app through the device portal.


[Bug] Relative paths in tailwind.config.js not always working

There are still some issues with using relative content in tailwind.config.js
The current workaround is using absolute paths
module.exports = {
  content: [
    `${__dirname}/code.{js,ts,jsx,tsx}`,
  ],
};

Keeping this open until deployed


⚠ Bofrost.es has degraded performance

In 707c12f, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1493 ms

Resolved: Bofrost.es performance has improved in 47b4dd6 after 6 minutes.


Fix multi-statment return

Fixes #297
Only thing that could changed it currently
Return, a := 1, b := 2
; Converted to ->
Return (AHKv1v2_Temp := a := 1, b := 2, AHKv1v2_Temp) ; V1toV2: Wrapped Multi-statement return with parentheses
; Instead of reusing a
Return (a := 1, b := 2, a) ; V1toV2: Wrapped Multi-statement return with parentheses

I'll do more testing later to see if this can be implemented without issues

Theoretical RegEx i)^(?:Return\s*,?\s*([^,\s]*)\s*)([^a-zA-Z0-9\s]?=|<>)


Consider updating dependencies for 3.0

System.Threading.Tasks.Extensions (4.5.2)
https://github.com/aspnet/EntityFrameworkCore/blob/release/3.0/src/EFCore/EFCore.csproj#L27

Castle.Core (4.2.1)
https://github.com/aspnet/EntityFrameworkCore/blob/release/3.0/src/EFCore.Proxies/EFCore.Proxies.csproj#L19

Microsoft.Azure.Cosmos (3.0.0)
https://github.com/aspnet/EntityFrameworkCore/blob/release/3.0/src/EFCore.Cosmos/EFCore.Cosmos.csproj#L25

/cc @AndriySvyryd for Cosmos
@bricelam Can you take a look at the other two?
/cc @JunTaoLuo

/cc @Pilchie FYI

Cosmos is already at 3.0.0 https://github.com/aspnet/EntityFrameworkCore/blob/release/3.0/eng/Versions.props#L15

@AndriySvyryd Right, but there is a 3.1.1 package now.

I'm not sure we should upgrade unless we need to, users can always bump it up manually.

@AndriySvyryd Can you try to find out what they fixed between 3.0 and 3.1.1? There might be critical issues that we should update for.

System.Threading.Tasks.Extensions is for downlevel ValueTask. We can dump it.

@bricelam Looks like our Castle.Core is quite old; given that it only impacts proxies and test coverage is pretty good I think we should update this for 3.0 as well. Thoughts?

Agreed, fine to leave. Release notes:
https://github.com/castleproject/Core/releases/tag/v4.3.0
https://github.com/castleproject/Core/releases/tag/v4.3.1
https://github.com/castleproject/Core/releases/tag/v4.4.0

@bricelam So you think we should or should not update our Castle reference?

Oh, lol. Either way--it's low risk and low value. 😉

@bricelam I read through the release notes in more detail. Let's leave as is for now, but we should update for 3.1 or at the latest 5.0.

Our analyzer depends on Microsoft.CodeAnalysis.CSharp.Workspaces. Is it safe to update this package? We really only need to work with the version of Roslyn that ships in VS2019 16.3 and the .NET Core 3.0 SDK, right?

Filed #17625


[NLU-4112] Currency resolving for EGP and SAR

Resolved the currency for Egyptian Pound EGP and Saudi Riyal SAR

https://jenkins.ininica.com/view/Dialog Engine/job/NLU/job/Recognizers-Text/473/ Tests passing

Spoke with Huessien and he gave me the correct translations

https://jenkins.ininica.com/view/Dialog Engine/job/NLU/job/Recognizers-Text/475/


increase memory limits on all service catalog pods

fighting issues with continuous restarts on pods, bumping up memory a bit, need to do a round of performance runs but need immediate relief for broker developers.

/test e2e-aws-olm

/approve
/lgtm


Search for plug-ins crashes

Go to https://verdaccio.org/dev/plugins-search

Type anything like "theme"

Crashes on the first keystroke

Thanks :) might be the library was upgraded and well website does not have test :)

Still an issue. Looks like https://github.com/oramasearch/orama/issues/446, fixed in https://github.com/oramasearch/orama/pull/471 which is part of 1.2.2.
You picked 1.2.1 but 1.2.10 is latest. Or is there some caching on the backend?


Add Availabile condition to status.conditions to indicate if Kepler is operational

The purpose of the Reconcile condition is to indicate whether the reconciliation of a resource by the operator/controller has been completed or is in progress. It helps to track the progress and status of the operator's actions on the resource but not if the result of the reconciliation has resulted in the operand in a working condition. This can be indicated by Available condition. Having the condition means, user don't have to rely on implementation details of the Operator to understand if the operand is in working condition.
Currently after kepler is created, users need to wait for MC to apply and pods to restart (leaking internal implementation detail). Instead with Available condition in status, they would only have to wait until Available: true

@husky-parul I have reopened this because we still don't have Available condition in kepler status.

closed by https://github.com/sustainable-computing-io/kepler-operator/pull/182


Document deployment and upgrade approach for ACK itself

Currently, we think that the ASO server implementation will be entirely stateless. There may be caches, of course, but the state that ASO considers will be stored in the Kubernetes etcd backend and the AWS services themselves.
So, the upgrade process for ASO itself should be relatively simple: just increment the image version/tag for the Deployment YAML that describes the ASO application in the user's Kubernetes cluster.
However, over time, as AWS services evolve, so will the CRD(s) that describe(s) the object(s) the service exposes. We should document how we will handle evolving the CRD schema over time, how we will approach rolling out new CRD versions and how we will ensure that an ASO controller can read and reconcile CRs with different CRD schema versions.
A variety of options:

Standardize on Helm and keep deployment artifacts only in the eks Helm charts repository
Use a Kustomize config directory in the aws/aws-service-operator-k8s source repository and have a script that automatically creates/updates a Helm chart for ASO in the eks-charts Git repo

Closing out in favor of #366


Update .csproj RepositoryUrl

Used the old link to Shimmy's repo, which still mentioned "LCAPI".

Thanks for this, I was waiting for this repo to be renamed before swapping out the repo link, but forgot.


Added sort asc by name to print commands

Codecov Report

Merging #6 (058474b) into main (2dc1d82) will decrease coverage by 0.21%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   91.92%   91.70%   -0.22%
==========================================
  Files          19       19
  Lines         421      422       +1
==========================================
  Hits          387      387
- Misses         34       35       +1

Impacted Files
Coverage Δ

src/Console/Command/AddScope.php
100.00% <ø> (ø)

src/Console/Command/DeactivateApiKey.php
100.00% <ø> (ø)

src/Console/Command/DeleteScope.php
100.00% <ø> (ø)

src/Console/Command/GenerateApiKey.php
100.00% <ø> (ø)

src/Console/Command/GenerateScope.php
100.00% <ø> (ø)

src/Console/Command/RemoveScope.php
100.00% <ø> (ø)

src/ServiceProvider.php
90.90% <75.00%> (-9.10%)
:arrow_down:

src/Console/Command/Command.php
100.00% <100.00%> (ø)

src/Console/Command/PrintApiKey.php
100.00% <100.00%> (ø)

src/Console/Command/PrintScope.php
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Jakarta-ize Enterprise Web Services Specification Document Chapter 9

This pull request will Jakarta-ize chapter 9 of the Jakarta Enterprise Web services spec.  This is part of implementing issue #118

Cancelling this PR, will open a new one later


FEATURE: Enhance embedding functionality with batch and image support.

What is the purpose of this change?
The purpose of this change is to enhance the LangChain embeddings component by adding support for batch processing of embeddings and extending its functionality to include image embeddings. This allows for more efficient handling of multiple embeddings in a single operation and broadens the use cases to include image data alongside text data.
How is this accomplished?
This is accomplished by modifying the input schema to accept a list of items instead of a single text input and introducing methods to handle different types of embeddings (document, query, and image). The invoke method has been refactored to process all item types consistently, delegating the actual embedding process to specialized methods for each type.
Anything reviews should focus on/be aware of?
Reviewers should focus on the changes to the input and output schemas and how the invoke method handles the embedding operations for different types of data. Ensure that the batch processing logic works as intended for all supported embedding types and that the new image embedding functionality is properly integrated.
Changes are backward incompatible, but no one is using this component yet

LG


Document .Site.RegularPages

From the 0.18 Release Notes (#2769):

.Site.RegularPages is a shortcut to the page collection you have been used to getting.

.Site.Pages now contains more than just regular pages.

Why is this labeled "discussion"?

Errant mouse click.  Fixed.


Kill the besu service when we deploy the smart contract by below function call

Please suggest us how to deal with a issue , when our developer who write a smart contract included below function call , when it deploy it will kill the besu service
result := delegatecall(gas(), _impl, ptr, calldatasize(), 0, 0)
size := returndatasize()
returndatacopy(ptr, 0, size)
.....
emit TopUpPaymentWalletFailed(paymentWalletAddr, gasUsed, currBalance, ptr);
Versions (Add all that apply)

Software version: [besu --21.10.2]
OS Name & Version: [ubuntu 20.04 lts x64]
Kernel Version: [Linux ip-172-31-24-141 5.11.0-1021-aws #22~20.04.2-Ubuntu SMP Wed Oct 27 21:27:13 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux]
Docker Version: [ Version:  20.10.5]
Cloud VM, type, size: [Amazon Web Services t3.2xlarge]

Genesis file
{
"config" : {
"chainId" : 2021,
"constantinoplefixblock" : 0,
"istanbulBlock" : 9702190,
"muirglacierBlock" : 9702195,
"berlinBlock" : 9702200,
"contractSizeLimit": 245760,
"ibft2" : {
"blockperiodseconds" : 2,
"epochlength" : 30000,
"requesttimeoutseconds" : 10,
"blockreward": "5000000000000000",
"miningbeneficiary": "0xe0275e0cf831d5a74089e1a66c810b57891c2d85"
}
},
"nonce" : "0x0",
"timestamp" : "0x58ee40ba",
"gasLimit" : "0x1fffffffffffff",
"difficulty" : "0x1",
"mixHash" : "0x63746963616c2062797a616e74696e65206661756c7420746f6c6572616e6365",
"coinbase" : "0x0000000000000000000000000000000000000000",

We can reproduce the issue by these 2 contracts (note that comment in the 2nd contract is intended)
contract Contract {
    function callMe(address) external {
        revert("Revert anyway");
    }
}

contract OOM {
    event Reverted(address indexed addr, bytes revertReason);

    function callMe(address addr) external {
        bytes memory ptr;
        uint256 offset;
        uint256 size;
        uint256 result;

        assembly {
            ptr := mload(0x40)
            calldatacopy(ptr, 0, calldatasize())
            result := delegatecall(gas(), addr, ptr, calldatasize(), 0, 0)
            size := returndatasize()
            returndatacopy(ptr, 0, size)

            switch result
            case 0 {
                if gt(size, 0) {
                    offset := add(ptr, 0x120)
                    mstore(0x40, offset)
                    // ptr := add(ptr, 4)
                    // let lengthFieldLength := mload(ptr)
                    // ptr := add(ptr, lengthFieldLength)
                }
            }
        }

        if (result == 0) {
            emit Reverted(addr, ptr);
        }
    }
}

Make a transaction to OOM and delegatecall to Contract, CPU and memory usage rise, the node becomes unresponsive until we restart and produce below error message
"class":"PeerDiscoveryAgent","message":"P2P peer discovery agent started and listening on /<IP_ADDRESS>:30303","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:30,397","container":"15590c1d9d97","level":"INFO","thread":"vert.x-eventloop-thread-4","class":"PeerDiscoveryAgent","message":"Writing node record to disk. NodeRecord{seq=55, publicKey=0x02579bab37e54dc4dcb996bc6bc80594e915062352584d3428e302de1981fdd66e, udpAddress=Optional[/<IP_ADDRESS>:30303], tcpAddress=Optional[/<IP_ADDRESS>:30303], asBase64=-Je4QBqVfk4CCun01TZMrbNKRzXDxaOQZL1ApB127RlL3MU3Iy2wKyZdtAVAtawaJWp0WF2Xo-l2zkXFXHrdug3p2Ho3g2V0aMfGhEV_Vf-AgmlkgnY0gmlwhKwQ7w6Jc2VjcDI1NmsxoQJXm6s35U3E3LmWvGvIBZTpFQYjUlhNNCjjAt4Zgf3WboN0Y3CCdl-DdWRwgnZf, nodeId=0x8550c1493dab8574daf645d0fc638101f646aef1fc921478bce1f35e9071bf7b, customFields={tcp=30303, udp=30303, ip=0xac10ef0e, eth=[[0x457f55ff, 0x]], id=V4, secp256k1=0x02579bab37e54dc4dcb996bc6bc80594e915062352584d3428e302de1981fdd66e}}","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:30,470","container":"15590c1d9d97","level":"INFO","thread":"main","class":"DefaultP2PNetwork","message":"Enode URL enode://579bab37e54dc4dcb996bc6bc80594e915062352584d3428e302de1981fdd66ec991c82a594cd9279bed6da800d57ce2129e40efd1128074d10cebe83046ea6c@<IP_ADDRESS>:30303","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:30,471","container":"15590c1d9d97","level":"INFO","thread":"main","class":"DefaultP2PNetwork","message":"Node address 0xfc638101f646aef1fc921478bce1f35e9071bf7b","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:30,473","container":"15590c1d9d97","level":"INFO","thread":"main","class":"DefaultSynchronizer","message":"Starting synchronizer.","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:30,475","container":"15590c1d9d97","level":"INFO","thread":"main","class":"FullSyncDownloader","message":"Starting full sync.","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:30,475","container":"15590c1d9d97","level":"INFO","thread":"main","class":"FullSyncTargetManager","message":"No sync target, waiting for peers: 0","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:30,791","container":"15590c1d9d97","level":"INFO","thread":"nioEventLoopGroup-3-9","class":"FullSyncTargetManager","message":"No sync target, waiting for peers: 9","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:59,846","container":"15590c1d9d97","level":"INFO","thread":"main","class":"JsonRpcHttpService","message":"Starting JSON-RPC service on <IP_ADDRESS>:8545","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:59,877","container":"15590c1d9d97","level":"INFO","thread":"main","class":"GraphQLHttpService","message":"Starting GraphQL HTTP service on <IP_ADDRESS>:8547","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:59,876","container":"15590c1d9d97","level":"INFO","thread":"vert.x-eventloop-thread-8","class":"JsonRpcHttpService","message":"JSON-RPC service started and listening on <IP_ADDRESS>:8545","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:59,881","container":"15590c1d9d97","level":"INFO","thread":"main","class":"WebSocketService","message":"Starting Websocket service on <IP_ADDRESS>:8546","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:59,881","container":"15590c1d9d97","level":"INFO","thread":"vert.x-eventloop-thread-10","class":"GraphQLHttpService","message":"GraphQL HTTP service started and listening on <IP_ADDRESS>:8547","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:59,893","container":"15590c1d9d97","level":"INFO","thread":"vert.x-eventloop-thread-12","class":"WebSocketService","message":"Websocket service started and listening on <IP_ADDRESS>:8546","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:59,895","container":"15590c1d9d97","level":"INFO","thread":"main","class":"Runner","message":"Ethereum main loop is up.","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:59,909","container":"15590c1d9d97","level":"INFO","thread":"main","class":"AutoTransactionLogBloomCachingService","message":"Starting auto transaction log bloom caching service.","throwable":""}
today at 16:14  {"timestamp":"2021-11-19T08:14:59,911","container":"15590c1d9d97","level":"INFO","thread":"main","class":"LogBloomCacheMetadata","message":"Lookup cache metadata file in data directory: /opt/besu/data/caches","throwable":""}
today at 16:17  {"timestamp":"2021-11-19T08:17:46,656","container":"15590c1d9d97","level":"INFO","thread":"pool-9-thread-1","class":"IbftRound","message":"Importing block to chain. round=ConsensusRoundIdentifier{Sequence=9702015, Round=4}, hash=0xa91b22545f94a67c23d7c1d6a3353584b4129a58453fe53360909dc246f40403","throwable":""}
today at 16:18  {"timestamp":"2021-11-19T08:18:16,237","container":"15590c1d9d97","level":"WARN","thread":"vertx-blocked-thread-checker","class":"BlockedThreadChecker","message":"Thread Thread[vert.x-eventloop-thread-4,5,main]=Thread[vert.x-eventloop-thread-4,5,main] has been blocked for 2485 ms, time limit is 2000 ms","throwable":""}
today at 16:18  {"timestamp":"2021-11-19T08:18:16,263","container":"15590c1d9d97","level":"WARN","thread":"vertx-blocked-thread-checker","class":"BlockedThreadChecker","message":"Thread Thread[vert.x-eventloop-thread-4,5,main]=Thread[vert.x-eventloop-thread-4,5,main] has been blocked for 7515 ms, time limit is 2000 ms","throwable":" io.vertx.core.VertxException: Thread blocked\n\tat java.base@11.0.13/jdk.internal.misc.VM.getNanoTimeAdjustment(Native Method)\n\tat java.base@11.0.13/java.time.Clock$SystemClock.instant(Unknown Source)\n\tat java.base@11.0.13/java.time.Instant.now(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PacketData.defaultExpiration(PacketData.java:37)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.FindNeighborsPacketData.create(FindNeighborsPacketData.java:42)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController.lambda$findNodes$14(PeerDiscoveryController.java:536)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController$$Lambda$1226/0x000000084066d440.accept(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController$PeerInteractionState.execute(PeerDiscoveryController.java:702)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController.dispatchInteraction(PeerDiscoveryController.java:558)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController.findNodes(PeerDiscoveryController.java:541)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController$$Lambda$1130/0x0000000840637c40.findNeighbours(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.neighboursInitiateRound(RecursivePeerRefreshState.java:165)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.bondingInitiateRound(RecursivePeerRefreshState.java:110)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.neighboursCancelOutstandingRequests(RecursivePeerRefreshState.java:179)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState$$Lambda$1229/0x000000084066c040.run(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.performIfNotCancelled(RecursivePeerRefreshState.java:132)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.lambda$scheduleTimeout$0(RecursivePeerRefreshState.java:126)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState$$Lambda$1159/0x0000000840642c40.handle(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.VertxTimerUtil.lambda$setTimer$1(VertxTimerUtil.java:34)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.VertxTimerUtil$$Lambda$1156/0x0000000840642040.handle(Unknown Source)\n\tat app//io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:942)\n\tat app//io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:906)\n\tat app//io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:366)\n\tat app//io.vertx.core.impl.EventLoopContext.execute(EventLoopContext.java:43)\n\tat app//io.vertx.core.impl.ContextImpl.executeFromIO(ContextImpl.java:229)\n\tat app//io.vertx.core.impl.ContextImpl.executeFromIO(ContextImpl.java:221)\n\tat app//io.vertx.core.impl.VertxImpl$InternalTimerHandler.run(VertxImpl.java:932)\n\tat app//io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)\n\tat app//io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)\n\tat app//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)\n\tat app//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)\n\tat app//io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:497)\n\tat app//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)\n\tat app//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)\n\tat app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.base@11.0.13/java.lang.Thread.run(Unknown Source)\n"}
today at 16:18  {"timestamp":"2021-11-19T08:18:22,869","container":"15590c1d9d97","level":"INFO","thread":"pool-9-thread-1","class":"IbftBesuControllerBuilder","message":"Imported #9,702,015 / 2 tx / 0 pending / 9,875,025 (0.0%) gas / (0xa91b22545f94a67c23d7c1d6a3353584b4129a58453fe53360909dc246f40403)","throwable":""}
today at 16:18  {"timestamp":"2021-11-19T08:18:22,869","container":"15590c1d9d97","level":"INFO","thread":"EthScheduler-Workers-0","class":"PersistBlockTask","message":"Imported #9,702,015 / 2 tx / 0 om / 9,875,025 (0.0%) gas / (0xa91b22545f94a67c23d7c1d6a3353584b4129a58453fe53360909dc246f40403) in 0.661s. Peers: 5","throwable":""}
today at 16:19  {"timestamp":"2021-11-19T08:18:57,578","container":"15590c1d9d97","level":"WARN","thread":"vertx-blocked-thread-checker","class":"BlockedThreadChecker","message":"Thread Thread[vert.x-eventloop-thread-4,5,main]=Thread[vert.x-eventloop-thread-4,5,main] has been blocked for 2249 ms, time limit is 2000 ms","throwable":""}
today at 16:21  {"timestamp":"2021-11-19T08:21:22,802","container":"15590c1d9d97","level":"WARN","thread":"vertx-blocked-thread-checker","class":"BlockedThreadChecker","message":"Thread Thread[vert.x-eventloop-thread-4,5,main]=Thread[vert.x-eventloop-thread-4,5,main] has been blocked for 5416 ms, time limit is 2000 ms","throwable":" io.vertx.core.VertxException: Thread blocked\n\tat java.base@11.0.13/java.util.stream.ReferencePipeline.limit(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.neighboursRoundCandidates(RecursivePeerRefreshState.java:258)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.neighboursInitiateRound(RecursivePeerRefreshState.java:150)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.bondingInitiateRound(RecursivePeerRefreshState.java:110)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.neighboursCancelOutstandingRequests(RecursivePeerRefreshState.java:179)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState$$Lambda$1229/0x000000084066c040.run(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.performIfNotCancelled(RecursivePeerRefreshState.java:132)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState.lambda$scheduleTimeout$0(RecursivePeerRefreshState.java:126)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.RecursivePeerRefreshState$$Lambda$1159/0x0000000840642c40.handle(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.VertxTimerUtil.lambda$setTimer$1(VertxTimerUtil.java:34)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.VertxTimerUtil$$Lambda$1156/0x0000000840642040.handle(Unknown Source)\n\tat app//io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:942)\n\tat app//io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:906)\n\tat app//io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:366)\n\tat app//io.vertx.core.impl.EventLoopContext.execute(EventLoopContext.java:43)\n\tat app//io.vertx.core.impl.ContextImpl.executeFromIO(ContextImpl.java:229)\n\tat app//io.vertx.core.impl.ContextImpl.executeFromIO(ContextImpl.java:221)\n\tat app//io.vertx.core.impl.VertxImpl$InternalTimerHandler.run(VertxImpl.java:932)\n\tat app//io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)\n\tat app//io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)\n\tat app//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)\n\tat app//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)\n\tat app//io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)\n\tat app//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)\n\tat app//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)\n\tat app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.base@11.0.13/java.lang.Thread.run(Unknown Source)\n"}
today at 16:21  {"timestamp":"2021-11-19T08:21:22,873","container":"15590c1d9d97","level":"WARN","thread":"vertx-blocked-thread-checker","class":"BlockedThreadChecker","message":"Thread Thread[vert.x-worker-thread-16,5,main]=Thread[vert.x-worker-thread-16,5,main] has been blocked for 126543 ms, time limit is 60000 ms","throwable":" io.vertx.core.VertxException: Thread blocked\n\tat app//org.hyperledger.besu.nativelib.secp256k1.LibSecp256k1.secp256k1_ecdsa_recover(Native Method)\n\tat app//org.hyperledger.besu.crypto.SECP256K1.recoverFromSignatureNative(SECP256K1.java:223)\n\tat app//org.hyperledger.besu.crypto.SECP256K1.recoverFromSignature(SECP256K1.java:197)\n\tat app//org.hyperledger.besu.crypto.AbstractSECP256.normaliseSignature(AbstractSECP256.java:109)\n\tat app//org.hyperledger.besu.crypto.NodeKey.sign(NodeKey.java:34)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.Packet.(Packet.java:64)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.Packet.create(Packet.java:99)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController.lambda$createPacket$12(PeerDiscoveryController.java:518)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController$$Lambda$1147/0x0000000840633440.get(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.VertxPeerDiscoveryAgent$VertxAsyncExecutor.lambda$execute$0(VertxPeerDiscoveryAgent.java:254)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.VertxPeerDiscoveryAgent$VertxAsyncExecutor$$Lambda$1148/0x0000000840632840.handle(Unknown Source)\n\tat app//io.vertx.core.impl.ContextImpl.lambda$executeBlocking$2(ContextImpl.java:313)\n\tat app//io.vertx.core.impl.ContextImpl$$Lambda$1150/0x0000000840632040.run(Unknown Source)\n\tat java.base@11.0.13/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base@11.0.13/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.base@11.0.13/java.lang.Thread.run(Unknown Source)\n"}
today at 16:21  {"timestamp":"2021-11-19T08:21:22,880","container":"15590c1d9d97","level":"WARN","thread":"vertx-blocked-thread-checker","class":"BlockedThreadChecker","message":"Thread Thread[vert.x-worker-thread-9,5,main]=Thread[vert.x-worker-thread-9,5,main] has been blocked for 120552 ms, time limit is 60000 ms","throwable":" io.vertx.core.VertxException: Thread blocked\n\tat app//org.hyperledger.besu.nativelib.secp256k1.LibSecp256k1.secp256k1_ecdsa_sign_recoverable(Native Method)\n\tat app//org.hyperledger.besu.crypto.SECP256K1.signNative(SECP256K1.java:141)\n\tat app//org.hyperledger.besu.crypto.SECP256K1.sign(SECP256K1.java:91)\n\tat app//org.hyperledger.besu.crypto.KeyPairSecurityModule.sign(KeyPairSecurityModule.java:57)\n\tat app//org.hyperledger.besu.crypto.NodeKey.sign(NodeKey.java:32)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.Packet.(Packet.java:64)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.Packet.create(Packet.java:99)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController.lambda$createPacket$12(PeerDiscoveryController.java:518)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.internal.PeerDiscoveryController$$Lambda$1147/0x0000000840633440.get(Unknown Source)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.VertxPeerDiscoveryAgent$VertxAsyncExecutor.lambda$execute$0(VertxPeerDiscoveryAgent.java:254)\n\tat app//org.hyperledger.besu.ethereum.p2p.discovery.VertxPeerDiscoveryAgent$VertxAsyncExecutor$$Lambda$1148/0x0000000840632840.handle(Unknown Source)\n\tat app//io.vertx.core.impl.ContextImpl.lambda$executeBlocking$2(ContextImpl.java:313)\n\tat app//io.vertx.core.impl.ContextImpl$$Lambda$1150/0x0000000840632040.run(Unknown Source)\n\tat java.base@11.0.13/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base@11.0.13/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.base@11.0.13/java.lang.Thread.run(Unknown Source)\n"}

Hi @eu09 I am working on reproducing this. So far I can't reproduce it locally (the call gets status 0x0 but I don't see the CPU/memory problems you describe) locally (ethash network, running on my local machine, and I've tried latest main branch and 21.10.2). I've only tried as a public contract - confirming you are not deploying this as a private contract? I haven't had too much to do with solidity assembly so may need to do some more research into that.

I have also tried with the quickstart using besu version (21.7.4 and) 21.10.2 using QBFT/IBFT2 and I don't see any issues with memory/CPU when I deploy or call these contracts.
Can you describe how you are deploying the contracts and sending the transactions? Wondering if there is something different about the way the transactions are being constructed. (eg calldatasize may be large)
Also what version of solidity compiler are you using? Actually it might help if you send the contract binary code, so we can see if they are different?

We use truffle to compile and deploy the contracts, then just simply send the transaction by web3.js . oomContract.methods.callMe("0x...").send(...)
Our normal development also uses the same settings and works fine so far, so it should have little relation to the issue.
Tools version:
Truffle v5.4.16 (core: 5.4.16)
Solidity - 0.6.6 (solc-js)
Node v14.17.2
Web3.js v1.5.3
The  Besu Service located in Docker Container. Each Service is limited in Min 2GB Max 4GB on JVM options
Here below is config of the docker-composer
x-besu-bootnode-def:
&besu-bootnode-def
restart: "on-failure"
image: hyperledger/besu:21.10.2
environment:
- BESU_OPTS=-Xms4g -Xmx8g
- LOG4J_CONFIGURATION_FILE=/config/log-config.xml
x-besu-def:
&besu-def
restart: "on-failure"
image: hyperledger/besu:21.10.2
environment:
- LOG4J_CONFIGURATION_FILE=/config/log-config.xml
- BESU_OPTS=-Xms4g -Xmx8g

@eu09 this is what I get for the binaries of those contracts - are yours different?
cat Contract.bin
608060405234801561001057600080fd5b506101ca806100206000396000f3fe608060405234801561001057600080fd5b506004361061002b5760003560e01c8063b27b880414610030575b600080fd5b61004a6004803603810190610045919061009c565b61004c565b005b6040517f08c379a000000000000000000000000000000000000000000000000000000000815260040161007e906100ec565b60405180910390fd5b6000813590506100968161017d565b92915050565b6000602082840312156100b2576100b161014f565b5b60006100c084828501610087565b91505092915050565b60006100d6600d8361010c565b91506100e182610154565b602082019050919050565b60006020820190508181036000830152610105816100c9565b9050919050565b600082825260208201905092915050565b60006101288261012f565b9050919050565b600073ffffffffffffffffffffffffffffffffffffffff82169050919050565b600080fd5b7f52657665727420616e7977617900000000000000000000000000000000000000600082015250565b6101868161011d565b811461019157600080fd5b5056fea2646970667358221220f98aead7839d4b5cb2fa52561c9b1720603885870f500dc934de148dcdea6e8164736f6c63430008060033
cat OOM.bin
608060405234801561001057600080fd5b50610274806100206000396000f3fe608060405234801561001057600080fd5b506004361061002b5760003560e01c8063b27b880414610030575b600080fd5b61004a60048036038101906100459190610108565b61004c565b005b60606000806000604051935036600085376000803686885af490503d9150816000853e806000811461007d57610093565b60008311156100925761012085019350836040525b5b5060008114156100ec578473ffffffffffffffffffffffffffffffffffffffff167f410d96db3f80b0f89b36888c4d8a94004268f8d42309ac39b7bcba706293e099856040516100e3919061016e565b60405180910390a25b5050505050565b60008135905061010281610227565b92915050565b60006020828403121561011e5761011d610211565b5b600061012c848285016100f3565b91505092915050565b600061014082610190565b61014a818561019b565b935061015a8185602086016101de565b61016381610216565b840191505092915050565b600060208201905081810360008301526101888184610135565b905092915050565b600081519050919050565b600082825260208201905092915050565b60006101b7826101be565b9050919050565b600073ffffffffffffffffffffffffffffffffffffffff82169050919050565b60005b838110156101fc5780820151818401526020810190506101e1565b8381111561020b576000848401525b50505050565b600080fd5b6000601f19601f8301169050919050565b610230816101ac565b811461023b57600080fd5b5056fea2646970667358221220fdfb5c371055342507b8fb9ca7b0c234f79819bd5cb05c0d467fb605de979eb564736f6c63430008060033

We have custom solc settings in truffle-config.js, so the compiled bytecode are different.
{
optimizer: {
enabled: true,
runs: 200
},
evmVersion: "istanbul"
}
Contract
6080604052348015600f57600080fd5b5060c58061001e6000396000f3fe6080604052348015600f57600080fd5b506004361060285760003560e01c8063b27b880414602d575b600080fd5b605060048036036020811015604157600080fd5b50356001600160a01b03166052565b005b6040805162461bcd60e51b815260206004820152600d60248201526c52657665727420616e7977617960981b604482015290519081900360640190fdfea2646970667358221220ab0ae18364d8bc77816c4403af0321b94d8c64bfcf78de34c1ac975a38df507a64736f6c63430006060033
OOM
608060405234801561001057600080fd5b5061017a806100206000396000f3fe608060405234801561001057600080fd5b506004361061002b5760003560e01c8063b27b880414610030575b600080fd5b6100566004803603602081101561004657600080fd5b50356001600160a01b0316610058565b005b60405160008080368185376000803686885af490503d9150816000853e80801561008157610093565b82156100935761012085019350836040525b508061013d57846001600160a01b03167f410d96db3f80b0f89b36888c4d8a94004268f8d42309ac39b7bcba706293e099856040518080602001828103825283818151815260200191508051906020019080838360005b838110156101025781810151838201526020016100ea565b50505050905090810190601f16801561012f5780820380516001836020036101000a031916815260200191505b509250505060405180910390a25b505050505056fea2646970667358221220e205eab0fed611629d6d7c1c6b0f1236988e82ccf408bd002b46112baf2990b764736f6c63430006060033

Using this version of solc: 0.6.6+commit.6c089d02.Emscripten.clang

We weren't able to reproduce this issue after deploying the contract with the binary values we got locally from our machines, nor the binary values you have provided.
Can you confirm the memory allocation for the Docker container? Is it min 2, max 4 or min 4, max 8?

@RP27
Let me provide some more info and context in the hope it can help. We did some internal tests and observed as follows.
The main concern here is the high resource usage when executing that call.
The node can hang/crash or not depends on the hardware (vm/container) type/resources and also on the block size (gas limit).
For instance testing in one small instance (local machine) we observed the following cpu/mem bumps while executing the call to rpcnode:
                   CPU %     MEM USAGE
validator1_1       6.40%     679.5MiB
validator2_1       2.76%     471.4MiB
validator3_1       5.89%     488.2MiB
validator4_1       6.35%     472.1MiB
rpcnode          207.70%      1.51GiB

during that high usage the logs report several times (log cleaned)
{
  "timestamp": "2021-12-02T19:47:45,365",
  "container": "70a0f942ae46",
  "level": "WARN",
  "thread": "vertx-blocked-thread-checker",
  "class": "BlockedThreadChecker",
  "message": "Thread Thread[vert.x-worker-thread-0,5,main]=Thread[vert.x-worker-thread-0,5,main] has been blocked for 124379 ms, time limit is 60000 ms",
  "throwable": " io.vertx.core.VertxException: Thread blocked "
               " at app//org.hyperledger.besu.evm.frame.MessageFrame.writeMemoryRightAligned(MessageFrame.java:648) "
               " at app//org.hyperledger.besu.evm.operation.MStoreOperation.execute(MStoreOperation.java:46) "
               " at app//org.hyperledger.besu.evm.EVM.lambda$executeNextOperation$0(EVM.java:86) "
               " at app//org.hyperledger.besu.evm.EVM$$Lambda$1530/0x0000000840746440.execute(Unknown Source) "
               " at app//org.hyperledger.besu.evm.tracing.EstimateGasOperationTracer.traceExecution(EstimateGasOperationTracer.java:31) "
               " at app//org.hyperledger.besu.evm.EVM.executeNextOperation(EVM.java:80) "
               " at app//org.hyperledger.besu.evm.EVM.runToHalt(EVM.java:73) "
               " at app//org.hyperledger.besu.evm.processor.AbstractMessageProcessor.codeExecute(AbstractMessageProcessor.java:157) "
               " at app//org.hyperledger.besu.evm.processor.AbstractMessageProcessor.process(AbstractMessageProcessor.java:169) "
               " at app//org.hyperledger.besu.ethereum.mainnet.MainnetTransactionProcessor.process(MainnetTransactionProcessor.java:489) "
               " at app//org.hyperledger.besu.ethereum.mainnet.MainnetTransactionProcessor.processTransaction(MainnetTransactionProcessor.java:397) "
               " at app//org.hyperledger.besu.ethereum.mainnet.MainnetTransactionProcessor.processTransaction(MainnetTransactionProcessor.java:148) "
               " at app//org.hyperledger.besu.ethereum.transaction.TransactionSimulator.process(TransactionSimulator.java:222) "
               " at app//org.hyperledger.besu.ethereum.transaction.TransactionSimulator.process(TransactionSimulator.java:107) "
               " at app//org.hyperledger.besu.ethereum.api.jsonrpc.internal.methods.EthEstimateGas.response(EthEstimateGas.java:81) "
               " at app//org.hyperledger.besu.ethereum.api.jsonrpc.JsonRpcHttpService.process(JsonRpcHttpService.java:725) "
               " at app//org.hyperledger.besu.ethereum.api.jsonrpc.JsonRpcHttpService.lambda$handleJsonSingleRequest$13(JsonRpcHttpService.java:579) "
               " at app//org.hyperledger.besu.ethereum.api.jsonrpc.JsonRpcHttpService$$Lambda$1494/0x0000000840726040.handle(Unknown Source) "
               " at app//io.vertx.core.impl.ContextImpl.lambda$executeBlocking$2(ContextImpl.java:313) "
               " at app//io.vertx.core.impl.ContextImpl$$Lambda$1006/0x0000000840580c40.run(Unknown Source) "
               " at java.base@11.0.13/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) "
               " at java.base@11.0.13/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) "
               " at app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) "
               " at java.base@11.0.13/java.lang.Thread.run(Unknown Source)"
}

this shows 3 calls "high" cpu usage duration example:
gasLimit -> 60_000_000

After a wile (in the example ~2 minutes) the node recovers and back to normal.
Doing the same in the same setup but just lowering the block size (gas limits) results in much lower "high" resources usage duration and faster recovery times as shown:
gasLimit -> 16_000_000

Now doing the same tests on more powerful machines the high usage (due to available resources the cpu usage was about 400%) is about 3-5 seconds (instead of ~2 minutes) and no warning logs reported (since the thread lock time < time limit ).
We didn't test with the highest gasLimit value (as the op reports) since that's not an option for us and the spike was worrying enough for us to investigate further.

We have made attempts to reproduce the high CPU usage issue when making that call, but we have been unsuccessful so far in doing so, despite having a Besu node running in a docker container with min 1/max 2, min 2/max 4 and min 4/ max 8gb of memory. We have also attempted to run the container with just 1 CPU core.
Are you able to provide the web3js code you are using to construct the calls to the contracts?
Also might be useful if you can provide a standalone repository that we can checkout and work with.

In conducting further tests, there appears to be something similar to the issue reported, with a spike in the CPU usage occurring when calling the callMe function in OOM via truffle migrate. Though, this is slightly different as the spike remains constant and does not recover back to normal usage. This test was conducted with Besu running in a docker container with min 2/max 4 memory and 1 CPU core.
As mentioned in my previous reply, it would be very useful for us if you could provide us with a repository that can reproduce this issue, along with your web3js code.

I was able to help @RP27  replicate this (deploying the contracts twice and Besu starts creating threads until it reaches the limit and start throwing exceptions)

Looking at the code: contract OOM {
event Reverted(address indexed addr, bytes revertReason);
function callMe(address addr) external {
    bytes memory ptr;
    uint256 offset;
    uint256 size;
    uint256 result;

    assembly {
        ptr := mload(0x40)
        calldatacopy(ptr, 0, calldatasize())
        result := delegatecall(gas(), addr, ptr, calldatasize(), 0, 0)
        size := returndatasize()
        returndatacopy(ptr, 0, size)

Apologies for the delay.
We've done some more testing, and it seems like Besu's behaviour handling the contract call is inline with other clients we've tested, in a 0 gas environment there's an issue with the contract that freaks the EVM out.
What's the use case for manually assigning an offset with add(ptr, 0x120) and storing it at 0x40? This is probably not done correctly.
contract OOM {
    event Reverted(address indexed addr, bytes ptr);

    function callMe(address addr) external {
        bytes memory ptr;
        // uint256 offset;
        uint256 size;
        uint256 result;

        assembly {
            ptr := mload(0x40)
            calldatacopy(ptr, 0, calldatasize())
            result := delegatecall(gas(), addr, ptr, calldatasize(), 0, 0)
            size := returndatasize()
            returndatacopy(ptr, 0, size)

            // switch result
            // case 0 {
            //     if gt(size, 0) {
            //         let newPtr := mload(0x40)
            //         mstore(0x40, add(newPtr, and(add(add(size, 0x20), 0x1f), not(0x1f))))
            //     }
            // }
            switch result
            case 0 { revert(ptr, size) }
            default { return(ptr, size) }
        }
        // if (result == 0) {
        //     emit Reverted(addr, ptr);
        // }
    }
}

Something like this works quite well (ignore the comments)
cc @elohffa  @eu09

the contract that freaks the EVM out

See the code in question below. Is the issue that the following code causes ptr to not point to a valid bytes object. When the emit is called, the bytes that ptr points to is copied for the purposes of emitting an event.
My guess is that the location ptr points to is interpreted as the bytes object having a very large length (think 2**256). Because the length field of ptr is very large, the EVM spends a lot of time copying bytes (it could keep trying to copy until the computer runs out of memory). In a configuration where gas wasn't zero, the transaction would run out of gas quickly and stop.
offset := add(ptr, 0x120)
mstore(0x40, offset)
emit Reverted(addr, ptr);

hi @eu09 - we've reproduced the memory spike on other clients so are closing this one.  Please reopen if you have any further questions.


fix issues #1185 and #1166

took action to fix issues #1185  and #1166

Thanks for the fixes but please revert back the sidecar changes. There is a good reason why both Monsters and Multiclass are sidecars. As soon as the monsters fixes are in the next nexus update will have the monsters DLL in the zip. If not enabled, like multiclass, it'll be fully isolated from the rest of CE. Monsters as it's own project will also give you the freedom to work on it independently as I do with Multiclass.

Sidecar is too unstable and unreliable , it was accidentally forgotten from the last three releases. Nobody else uses them and I have heard of no good or valid reasons to put this code in a sidecar. This code is finished and complete and does not require constant tweaking like multiclass does. It's not comparable to multiclass, is comparable to feats or spells which remain pay of the primary dll

I’m not aware about any instabilities in sidecar code. Nexus releases and builds are separate topics. It wasn’t on Nexus waiting for these fixes. I’ll merge and have the DLL back on next Nexus release once sidecar changes get reversed.

I’m not aware about any instabilities in sidecar code. Nexus releases and builds are separate topics. It wasn’t on Nexus waiting for these fixes. I’ll merge and have the DLL back on next Nexus release once sidecar changes get reversed.

I assumed it was a mistake because I didn't think anyone would remove content without notice. That's a very poor way to handle a community mod.  You mean you purposely removed content without informing any other contributors or users or including the change in the change log?
Why was this the only content removed when a bug was reported, when there have been dozens of other bug reports for other features/codes that have not been removed?
If content is removed when waiting on fix, warlock should be removed. This does not look like fair treatment.

this code throws lots of warnings reason why. merged your files under the sidecar.


How to make a sprite move in pause menu?

Describe your problem here.
I want to do something like Hypno's Lullaby v2.0 where art of the characters show up in the pause menu. I made a script that basically does that, but, the only problem is that the tweens do not function. (Well, they do function, but are frozen in the menu.)
My code:
local paused = false
local tweenSpeed = 0.45

function onUpdate()
    if songName == "songname" then
        if keyJustPressed("pause") then
            if paused == false then
                paused = true
                makeLuaSprite("pauseSprite","pausecharacters/slime",screenWidth,(screenHeight/2)-((600*0.75)/2))
                addLuaSprite("pauseSprite")
                scaleObject("pauseSprite", 0.75, 0.75)
                doTweenX("pauseSpriteMove", "pauseSprite", screenWidth-((600*0.75)-50), tweenSpeed, "circularInOut")
                setScrollFactor("pauseSprite",0,0)
                setObjectCamera("pauseSprite","other")
                debugPrint("the f")
            elseif paused == true then
                paused = false
                doTweenX("pauseSpriteMove", "pauseSprite", screenWidth, tweenSpeed, "circularInOut")
            end
        end
    end
end

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No, i didn't.

it’s not possible in lua

sad

Im pretty sure it is, this guy made a video of making a custom pause screen in lua, so maybe download the script in the disc, and edit it a bit? https://youtu.be/AgS4gzhIjBs

Help. the image is not appearing


Running the exercises seems to be broken?

e.g. filling in the blanks in the first exercise on https://www.scala-exercises.org/cats/semigroup and clicking 'Run' results in an error:
Evaluation failed : Compilation Error ; ERROR -> not found: value catslib at [213, 213, 213]

I tried one of the stdlib exercises and got a similar error.

It should be back now @cb372, thanks for reporting it!


docs: add more description for max_connection_duration in timeout faqs

This PR adds some more description around max_connection_duration in the Timeout FAQs.
Commit Message: add more description for max_connection_duration in timeout faqs.
Additional Description: -
Risk Level: N/A
Testing: N/A
Docs Changes: Added some more description around max_connection_duration in the Timeout FAQs.
Release Notes: N/A
Platform Specific Features: N/A
Signed-off-by: Rohit Agrawal<EMAIL_ADDRESS>

/assign @mattklein123

@markdroth latest version LGTY?

/lgtm api


Update InstallingAndServicing.md

paragraph needs to be seperated from note by white space

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/commercialize-your-device/InstallingAndServicing.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Getting "You must run VS code with admin privileges in order to use Raining in." When Clicking On "Toggle Downpour"

I even tried to run vs code as administrator, but it didn't work

im closing this issue. thanks for fixing!


Fix #1675 - Console User Interface (work by @raygervais, with fix for regression to UI.js)

Fixes to https://github.com/mozilla/brackets/pull/752 to deal with what I had to revert in https://github.com/mozilla/brackets/commit/896adeb1668da2986621cac1b24f2c73f3c840f8.
@raygervais please sign-off on this before I try and merge again.

@raygervais let's move discussion here.  What are you seeing with respect to dist/config.json?  This is working fine for me locally.

When running the local version, the terminal (backend get requests) show it stopped at dist/config.json. I had @flukeout look at it earlier in the week, but we saw nothing wrong with it. If it's running on your computer, along with everyone's except mine, then perhaps my machines are the issue?

But it'll stay there until you try to reload again. And so forth.

I'd say your dev env is busted.  Take a look at the code and make sure you're OK with what I've done, and I'll try to land it again.  Then we can both test it on staging in the next few days.  We're shipping on the 17th, so we can fix small things we find.

I agree, I say we follow through with your idea & I'll test / setup the development environment again.

I agree, I say we follow through with your idea & I'll test / setup the development environment again.

@raygervais so you're going to test this, or you want me to land it and we test on staging?  I'm unclear what you mean above.  I want to get this in today or tomorrow.

Testing now.

@humphd just one small change and I think we're good to go.

OK, let's try this again and see if it will stick.  @raygervais, please test for us on staging at http://bramble.mofostaging.net/ and file new bugs on anything you notice.

First regression found! https://github.com/mozilla/thimble.mozilla.org/issues/2057


Can Truvari read out query coordinates of duplications from .vcf file?

Hello,
I am a master student in the area of genomics and I am using Truvari in my automated SV calling pipeline. I think it is a great tool, however, I was wondering how Truvari handles the coordinates of the query genome for duplications, since for example the duplicated sequence can be on some distant location, and only on the query. Is there some tag in the INFO field of the .vcf file, which can contain this info for Truvari?
And as a secondary question, if it is not the case that Truvari considers that: What is your estimate how difficult it is to change the source code myself and introduce such a functionality? Additionally, I would also like that Truvari benchmarks translocations, and for them the same problem exists, that the coordinates of the query genome are essential to benchmark this SV correctly.
Thank you very much for your time and effort!
Best,
Thomas

Hello,
If your DUP has start/end information in its VCF entry, Truvari will compare that information to events at that same location. Generally, DUPs aren't a sequence-resolved variant and should therefore be compared without sequence similarity (e.g. --pctseq 0 docs). Translocations (BNDs) are not recommended for comparison by Truvari.
Have a great day,
~/Adam English


format test_meas_data.c and .h files to some default format

a script should before testing the c code generate measurements and fill the arrays with those values. After test runned it should set back the default format.
The idea is to reduce the large diff that test_meas_data.c and .h files produce and to eliminate any changes to those files

done https://github.com/IvanVnucec/Optimal-REQUEST/commit/b8db8ef65da3404200e5176c5f6bf36f490e1c7e


⚠ Palworld Tunnel (Connection URL) has degraded performance

In cb2e486, Palworld Tunnel (Connection URL) ($PG_PANEL/tstat.txt) experienced degraded performance:

HTTP code: 523
Response time: 95 ms

Resolved: Palworld Tunnel (Connection URL) performance has improved in 7ea1925 after 21 minutes.


can not open developer menu , iOS

cannot open developer menu in anyway，react-native: 0.59.8，i have use_frameworks! in Podfile, hardware keyboard is already connected, happens either in iOS simulator or device.( in android everything is fine )
React Native version:

react native info

  React Native Environment Info:
    System:
      OS: macOS 10.14.5
      CPU: (6) x64 Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
      Memory: 47.24 MB / 8.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 12.3.1 - /usr/local/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.9.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 23, 28
        Build Tools: 28.0.3
    IDEs:
      Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.8 => 0.59.8
    npmGlobalPackages:
      react-native-cli: 2.0.1

Podfile

# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'ReactNativeAppDemo' do
  # Pods for ReactNativeAppDemo
  pod 'React', :path => '../node_modules/react-native', :subspecs => [
  'Core',
  'CxxBridge',
  'DevSupport',
  'RCTText',
  'RCTNetwork',
  'RCTWebSocket',
  'RCTAnimation'
  ]
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

  pod 'react-native-baidu-map', :podspec => '../node_modules/react-native-baidu-map/ios/react-native-baidu-map.podspec'

  pod 'AppCenter/Crashes', '~> 2.0.1'
  pod 'AppCenter/Analytics', '~> 2.0.1'
  pod 'AppCenterReactNativeShared', '~> 2.0.0'
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!

  platform :ios, '9.0'
  target 'ReactNativeAppDemoTests' do
    inherit! :search_paths
    # Pods for testing
  end

end

target 'ReactNativeAppDemo-tvOS' do
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!

  # Pods for ReactNativeAppDemo-tvOS

  target 'ReactNativeAppDemo-tvOSTests' do
    inherit! :search_paths
    # Pods for testing
  end

end

Steps To Reproduce

install app in iOS simulator or device
command + d or command + r or shake device or hardware -- shake gesture

Describe what you expected to happen:

the developer menu show up

Can you check you're scheme is running in Debug mode, if you're in Release mode you won't be able to access the dev menu

@CatapultJesse yes, I am sure it is in debug mode

I have the same issue, developer menu is not showing in iOS.
I can only fix it by removing use_frameworks in pods

I have the same issue, developer menu is not showing in iOS.
I can only fix it by removing use_frameworks in pods

me too, i finally removed  use_frameworks! and the library that need use_frameworks!, then the developer menu come back

@KingAmo
and others!
Guys, its not good to fix dev menu accessibility this hardcore and unreliable way!
I anyway need to use_frameworks as so other ones need as! So please anyone help to decide how to fix this WITHOUT removing use_frameworks keyword from pods

Hi, same issue here
This is my Podfile, I'm sure app is running in Debug mode
platform :ios, '9.0'

target 'easypol' do
  use_frameworks!

  pod 'React', :path => '../node_modules/react-native', :subspecs => [
    'Core',
    'CxxBridge', # Include this for RN >= 0.47
    'DevSupport', # Include this to enable In-App Devmenu if RN >= 0.43
    'RCTText',
    'RCTNetwork',
    'RCTWebSocket', # needed for debugging
    'RCTImage',
    'RCTWebSocket', # Needed for debugging
    'RCTAnimation', # Needed for FlatList and animations running on native UI thread
    # Add any other subspecs you want to use in your project
  ]

  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

  # My dependencies
  pod 'Nexi_XPay', '1.1.6'
end

same problem here. podfile:
`# Uncomment the next line to define a global platform for your project
platform :ios, '9.0'
target 'glimpsy' do
Comment the next line if you don't want to use dynamic frameworks
use_frameworks!
Pods for glimpsy
Your 'node_modules' directory is probably in the root of your project,
but if not, adjust the :path accordingly
pod 'React', :path => '../node_modules/react-native', :subspecs => [
'Core',
'CxxBridge', # Include this for RN >= 0.47
'DevSupport', # Include this to enable In-App Devmenu if RN >= 0.43
'RCTText',
'RCTNetwork',
# 'RCTWebSocket', # Needed for debugging
'RCTAnimation', # Needed for FlatList and animations running on native UI thread
# Add any other subspecs you want to use in your project
'RCTImage',
]
pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
pod 'react-native-fast-image', :path => '../node_modules/react-native-fast-image'
Third party deps podspec link
pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons'
pod 'RNGestureHandler', :path => '../node_modules/react-native-gesture-handler'
pod 'react-native-image-picker', :path => '../node_modules/react-native-image-picker'
pod 'react-native-fast-image', :path => '../node_modules/react-native-fast-image'
end
post_install do |installer|
installer.pods_project.targets.each do |target|
if target.name == "React"
target.remove_from_project
end
end
end`

sam problem here. code:
platform :ios, '9.0'

target 'testapp' do
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!

  # Pods for testapp
  pod 'React', :path => '../node_modules/react-native', :subspecs => [
    'Core',
    'CxxBridge', # Include this for RN >= 0.47
    'DevSupport', # Include this to enable In-App Devmenu if RN >= 0.43
    'RCTText',
    'RCTNetwork',
    # 'RCTWebSocket', # Needed for debugging
    'RCTAnimation', # Needed for FlatList and animations running on native UI thread
    # Add any other subspecs you want to use in your project
    'RCTImage',
  ]

  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
  pod 'react-native-fast-image', :path => '../node_modules/react-native-fast-image'
  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

  pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons'
  pod 'RNGestureHandler', :path => '../node_modules/react-native-gesture-handler'
  pod 'react-native-image-picker', :path => '../node_modules/react-native-image-picker'
  pod 'react-native-fast-image', :path => '../node_modules/react-native-fast-image'

end

I have similar issue, sometimes the menu won't open (on real device) when debugger is running. So I have no way to disable the debugger.

I had a similar issue though the shake gesture worked for me. Not sure this is the reason but it happened after upgrading xcode. And the reason seemed to be that the hardware keyboard was disconnected. When pressing SHIFT + COMMAND + K to connect the hardware keyboard the developer menu was reachable with COMMAND + D again.
or in menu:

Hi any update on this issue?

How to reproduce:

react-native init Example --version 0.59.8
cd Example/ios
pod init
Change Podfile to the following:

platform :ios, '9.0'

target 'Example' do
  # I can't run with the following uncommented, get "ld: symbol(s) not found for architecture x86_64" error
  # use_frameworks!

  # Pods for Example
  pod 'React', :path => '../node_modules/react-native', :subspecs => [
    'Core',
    'CxxBridge',
    'DevSupport',
    'RCTActionSheet',
    'RCTAnimation',
    'RCTBlob',
    'RCTImage',
    'RCTLinkingIOS',
    'RCTNetwork',
    'RCTSettings',
    'RCTText',
    'RCTVibration',
    'RCTWebSocket',
  ]
  # Explicitly include Yoga if you are using RN >= 0.42.0
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'

  # Third party deps podspec link
  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

end

pod install
cd ../ && react-native run-ios

Dev menu shows with shake gesture but not with keyboard shortcut.

react-native info

  React Native Environment Info:
    System:
      OS: macOS 10.14.6
      CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
      Memory: 869.09 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
      Yarn: 1.17.3 - ~/.nvm/versions/node/v10.15.3/bin/yarn
      npm: 6.11.2 - ~/.nvm/versions/node/v10.15.3/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
      Android SDK:
        API Levels: 25, 26, 27, 28
        Build Tools: 25.0.3, 26.0.3, 27.0.3, 28.0.3, 29.0.0
        System Images: android-25 | Google Play Intel x86 Atom, android-26 | Google Play Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.4 AI-183.6<IP_ADDRESS>92245
      Xcode: 10.3/10G8 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.8 => 0.59.8
    npmGlobalPackages:
      react-native-cli: 2.0.1

Selecting Hardware > Keyboard > Send Keyboard Shortcuts to Device fixed this issue for me

Control + Cmd + Z (Menu: Device | Shake ^⌘Z)

I fixed mine by clicking in I/O > input and Send Keyboard input to Device

Control + Cmd + Z (Menu: Device | Shake ^⌘Z)

Jesus effing christ this took me way too long to find. It used to me Cmd+D on IOS was it not?! The devil in this whole thing is that Cmd+D still works sometimes and it's just so incredibly frustrating but Ctrl+Cmd+Z works every time. Thank you!

I had a similar issue though the shake gesture worked for me. Not sure this is the reason but it happened after upgrading xcode. And the reason seemed to be that the hardware keyboard was disconnected. When pressing SHIFT + COMMAND + K to connect the hardware keyboard the developer menu was reachable with COMMAND + D again.
or in menu:

This resolved my issue.

Can you check your scheme is running in Debug mode, if you're in Release mode you won't be able to access the dev menu

For anyone not sure how to check this: see https://stackoverflow.com/a/28059831 - as of xcode 12.4 go to Product > Scheme > Edit Scheme, then in the Run vertical tab, Info horizontal tab, check Build configuration

Control + Cmd + Z (Menu: Device | Shake ^⌘Z)

This worked, I was trying to do Cmd + D before. Although weirdly enough I noticed that if I do a screenshot first using Cmd + S  then I can do Cmd + D after that to open the dev menu

Simulator => Device => Restart


Featuring:

Updated swiper package
Edited client review slider and added an auto-swipe animation

npm install to update your local packages


Documenting Array.cr

Thank you! Overall really good changes, talking about "self and other" vs. "the two arrays" or "ary" (which doesn't exist in the code) is much better in my opinion.

@asterite thanks for the feedback!  I made some adjustments, let me know what you think.  Also I noticed a discrepancy in calling out argument names:  Sometimes they're written with * and others with (i.e. *random* vsrandom).  I feel the backticks  are more commonly understand as code.  Thoughts?

Also, are we abiding by an 80-char column limit or something like that?

@arktisklada We have the convention to use *arg* for arguments. If you use backticks and the name is a method, the doc generator will create a link to that method. So please change all arguments to use stars instead of backticks (it's OK to use backticks with self).
The 80-char column limit is something from the past, nowadays monitors are bigger, editors have word-wrap, etc.

@asterite (or whomever appropriate) is this PR too big?  If I were to add more code-level documentation, would it be best broken into smaller pieces?

@arktisklada Oh, it's just that I didn't realize you made the changes above. I'll take a look into this in these days.

@arktisklada Looks really good :-)
Just two things:

There are a couple of nil between starts (*nil*) that should be between backticks (`nil`).
Instead of "This expression returns" use "This method returns".

@asterite awesome, thanks!  Made those updates: nil => nil and expression => method

......and rebased

Thank you!! :smile_cat:


update smk to 1.1.8

link to demo deployment of your smk based app is
https://smk-mrdt-rt-b16795-dev.apps.silver.devops.gov.bc.ca
Verify that it looks good, if so merge the pull request which will trigger a prod deployment, otherwise close the pull request without merging
mentions / notifications: @michaelpnelson, @rustyjux

The Vanity URL for the dev deploy is https://smk-mrdt-api-gov-bc-ca.test.api.gov.bc.ca
If this is a dev deploy,  verify that it looks good, then merge the pull request to trigger prod deployment.
If this is a prod deployment, view your prod deploy at the url above :)
mentions / notifications: @michaelpnelson, @rustyjux


Project will not build after doing NPM install.

After another team member cloned the repo and attempted to build the project we ran into issues.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
What do I have to do to get resolve these dependency issues?

These are all warnings, can you post the full command you ran and traceback from trying to run the application? You should give it another shot with Angular bumped to 4 (latest commits in this repository) as well.

Thanks. I had done that after posting this. Update was the obvious choice. Should not have wasted your time. My bad.

Sounds like this is handled via an update, feel free to comment if you need any additional help, but I'm going to close this.

could you please explain the steps?

@vinaymorkar what issues are you having? these were all warnings and what fixed it was cloning a fresh copy of the latest code and re-running everything

I actually just diffed the files and made the changes manually so I understood what had changed. If I remember correctly there were some changes with tslint and something in the web pack config. I also added yarn wrapping npm to prevent this from happening again.

@mcescalante ya but after doing npm start it was throwing errors and most of them were related to missing/incorrect dependencies in package.json file. But installing latest angular-cli globally and  then updating latest packages locally resolved my issue.
Global package:
npm uninstall -g @angular/cli
npm cache clean
npm install -g @angular/cli@latest
Local project package:
rm -rf node_modules dist # use rmdir /S/Q node_modules dist in Windows Command Prompt; use rm -r -fo node_modules,dist in Windows PowerShell
npm install --save-dev @angular/cli@latest
npm install

Note
#use rmdir /S/Q node_modules dist in Windows Command Prompt; use rm -r -fo node_modules,dist in Windows PowerShell
Above is commented part.

Interesting - this repo doesn't use angular-cli so I'm not sure why that was part of the solution, but glad to hear that some node_modules work  and updating fixed it :)

Lol, maybe Angular CLI has super powers we don't know about. :)


idris2: 0.6.0 -> 0.7.0

Description of changes
Just packaging the release of Idris2 from today.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 276071 run on x86_64-darwin 1

1 package built:

idris2


Create project in current directory

So I want to upgrade my current git project with preact. This app is just html and JS. So how can I create a new project in the current directory instead of creating a new folder? Thanks
I tried this:
preact create lcac --type root --dest .

It will say the directory already exists.
I don't think we have an option to bypass that right now (maybe a generic --force -f? ) but this works:
preact create lcac -type root && move lcac/* . && rm -rf lcac

Ah, took me a second to realize what the issue was there - you're right @framp. A --force option sounds good.


Automate shell completion function generation

The cli/lib/scripts/completer is difficult to keep in sync, also it's a bit slow and not very sophisticated.
We should have a gem after install hook to automatically create real proper completion functions
See https://github.com/Homebrew/brew/blob/master/completions/bash/brew and https://github.com/Homebrew/brew/blob/master/completions/zsh/_brew for fine examples.

work in progress, also fixes #2270


added my name to guestbook.md

Hi!!!!
It has been pleasant to learn from you about Bash and Git.
Thank you so much for putting everything that is easy to understand and follow

I'm so happy you enjoyed it! Thank you for the pull request!


make location-list window height based on number of entries

I was wondering if the height of the location-list that shows the results can be configured. I think the default height is 10 lines, but if I have only 3 lines of results, having a location list of 10 lines consumes screen space. Would it be possible to change the height of location list based on number of results? It might also be useful to provide a way for user to configure the height of location list for showing the results.

@rajukv, I think this doable. lopen takes an optional parameter which defines its height. I'll add both, max height configuration and handling the case you describe.

Added parameter controls the height of the window. Parameter is common for both location list and quickfix list. At this point don't see a use case for them to have different heights.

@lyuts thank you. I am closing this issue


Hp gatekeeper test

Checks for a path parameter and applies it to the path
Adds additional logging
Fixes Rubocop warnings

Further work captured here #156


dbt Selection Analysis Utilities

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3304
Originally created by @pnadolny13 on 2022-03-02 21:22:58

Related to a discussion in slack https://meltano.slack.com/archives/C01UTUSP34M/p1646174917907139 where we laid out common dbt orchestration strategies.
A common strategy as your dbt project grows past the point of being able to just dbt run the whole thing is to target certain subsets of models based on their business need. Some need to be refreshed intraday vs once a week. A challenge with this strategy is that the selection criteria gets hard to manage and scary to change. Maybe we should allow dbt pipelines to be defined in Meltano in a way where we can provide useful information about this. Things like: what models are not selected by my whole list of complex selection criteria? Given the cron schedule of these model selections, are there any that are at risk of causing timing issues or collisions (i.e. if one DAG relies on a model but doesnt directly refresh it and the model is scheduled to refresh after the DAG that depends on it, indicating a stale data situation)?
These wouldnt be things in dbt itself because it requires an understanding of how/when you are scheduling models to run.

Interesting idea but a discussion would likely be better.


Analytics Data Service

how can i add new dimension or  new metric, help me please
const metric = AnalyticsData.newMetric();
metric.name = 'activeUsers';

const dimension = AnalyticsData.newDimension();
dimension.name = ('platform');

Hello,
Please check out the following example script.

Hello @ikuleshov
The script example from google you shared does not explain how to add multiple metrics/dimensions. Obviously the OP known about this example script otherwise he wouldn't be able to talk about the AnalyticsData. method...


An incorrect module name is enough to "prove" false

@catalin-hritcu stumbled upon this

Create a file; write the wrong module name in it.

$ printf "module BBB\n" > AAA.fst

Fix it in the UI, but forget to save; thus Emacs sends module AAA. Then send an incorrect definition: let f () : Lemma False = ()

$ cat incorrect-module-name.fst.in
{"query-id":"1","query":"push","args":{"kind":"full","code":"module AAA\n","line":1,"column":0}}
{"query-id":"2","query":"push","args":{"kind":"full","code":"\nlet f () : Lemma False = ()\n","line":2,"column":0}}

…profit? F* accepts the push without complaints.

$ /build/fstar/master/bin/fstar.exe --ide AAA.fst < incorrect-module-name.fst.in
{"kind":"protocol-info","version":1,"features":["autocomplete","compute","describe-protocol","describe-repl","exit","lookup","lookup/documentation","lookup/definition","pop","peek","push","search"]}
{"kind":"message","level":"warning","contents":"Warning: the module declaration \"module BBB\" found in file AAA.fst does not match its filename. Dependencies will be incorrect.\n"}
{"kind":"message","level":"warning","contents":"Warning: the module declaration \"module BBB\" found in file AAA.fst does not match its filename. Dependencies will be incorrect.\n"}
{"kind":"response","query-id":"1","status":"success","response":[]}
{"kind":"response","query-id":"2","status":"success","response":[]}

The core trick here is that the name of the module that F* detected and the name that actually gets sent by Emacs must be different.

I expect the latest refactorings in FStar.Ide.fs will make this trickier to reproduce in practice, but it should be easier now to craft a repro using vfs-add

Indeed, here's a repro:
{"query-id":"0","query":"vfs-add","args":{"contents": "module IncorrectModuleName\n\nlet f () : Lemma False = ()\n"}}
{"query-id":"1","query":"push","args":{"kind":"full","code":"module AAA\n","line":1,"column":0}}
{"query-id":"2","query":"push","args":{"kind":"full","code":"\nlet f () : Lemma False = ()\n","line":2,"column":0}}


New package: LaserFields v0.1.0

Registering package: LaserFields
Repository: https://github.com/jfeist/LaserFields.jl
Created by: @github-actions[bot]
Version: v0.1.0
Commit: 95188eebcff83a2346bcd58464ad7001a50c5a69
Reviewed by: @github-actions[bot]
Reference: https://github.com/jfeist/LaserFields.jl/commit/95188eebcff83a2346bcd58464ad7001a50c5a69#commitcomment-95532455

Is it appropriate that the general registry include packages that have no description or documentation?
[no block]

I've added a short description clarifying that this is a reimplementation in Julia of an existing Fortran library, and added an example notebook to show how to use it.

Excellent.  Thank you.
On Jan 13, 2023 10:39 AM, Johannes Feist @.***> wrote:
I've added a short description clarifying that this is a reimplementation in Julia of an existing Fortran library, and added an example notebook to show how to use it.
—
Reply to this email directly, view it on GitHubhttps://github.com/JuliaRegistries/General/pull/75379#issuecomment-1382030342, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIBY3E5OJRGR4EP7HNKY2C3WSFZKDANCNFSM6AAAAAATVN4I3A.
You are receiving this because you commented.Message ID: @.***>

This has been superseded by a new pull request (#75767), I understood from the documentation of JuliaRegistrator that this pull request would be closed, but this hasn't happened yet. Do I need to do anything else?


Update outbound-rules-control-egress.md

Copy text from release note about set-kube-service-host-fqdn into main public-facing docs. Release note is https://github.com/Azure/AKS/releases/tag/2022-07-17

@asudbring
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Ck editor text area not allowing contents after & sign

I have integrated Django-ckeditor in my application and when i enter the text which contains & sign, all the text and sentences after & sign is removed when saving the content. Please see the image below

Please note that the content after & sign got removed when saved. please see the image below

I haven't done any server side script to remove that sign. still it got removed.
Please help me to fix this issue.
I am using django-ckeditor==5.4.0

Maybe you found a real issue, but if that's the case then this is a bug in CKEditor proper, not in django-ckeditor. You should report this in their issue tracker. Thanks!


Simplify F.tile test

Simplifies test_tile using testing.FunctionTestCase
Solves part of issue #6071

LGTM. Jenkins, test this please.

Jenkins CI test (for commit 814f08d4b530b65bb72063b154b929837079418f, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)


switch to React

It's not sustainable to develop long-term without a proper UI framework, so switch to https://github.com/Jonghakseo/chrome-extension-boilerplate-react-vite

May be worth using https://github.com/fregante/webext-options-sync


NaN boxing issue for floating point

While D extension is enabled, according to the Unprivileged ISA V20191213, if for some instruction source register is a single-precision floating value, then a check must be made to see if the upper 32 bits of float register are all 1. This check is not there in the whisper.
These are the exact words from '12.2 NaN Boxing of Narrower Values' in spec:

Apart from transfer operations described in the previous paragraph, all other floating-point operations on narrower n-bit operations, n < FLEN, check if the input operands are correctly NaN-boxed, i.e., all upper FLEN−n bits are 1. If so, the n least-significant bits of the input are used as the input value, otherwise the input value is treated as an n-bit canonical NaN.

Hi Urvish,
The check you mention is supposed to be there.  If it does not always get
applied then that is a bug.  Please share the test case exhibiting the bug
and I will fix it.
Joe
Here's the code that does the check (file FpRegs.hpp line 356):
template<>
inline
float
FpRegs::readSingle(unsigned i) const
{
FpUnion u;
u.dp = regs_.at(i);
// Check for proper nan-boxing. If not properly boxed, replace with NaN.
if (~u.sp.pad != 0)
return std::numeric_limits::quiet_NaN();
return u.sp.sp;
}
On Wed, Feb 24, 2021 at 11:20 PM Urvish Patel<EMAIL_ADDRESS>wrote:

While D extension is enabled, according to the Unprivileged ISA
V20191213, if for some instruction source register is a single-precision
floating value, then a check must be made to see if the upper 32 bits of
float register are all 1. This check is not there in the whisper.
These are the exact words from '12.2 NaN Boxing of Narrower Values' in
spec:
Apart from transfer operations described in the previous paragraph, all
other floating-point operations on narrower n-bit operations, n < FLEN,
check if the input operands are correctly NaN-boxed, i.e., all upper FLEN−n
bits are 1. If so, the n least-significant bits of the input are used as
the input value, otherwise the input value is treated as an n-bit canonical
NaN.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/chipsalliance/SweRV-ISS/issues/7, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASHQXYHF5HCRGW637SHLDTTAXMYDANCNFSM4YF2LBLQ
.

Hi Joe,
Thanks for the response. Actually, I was using an older version, which was not having this fix (Also, does the latest commit take into account that NaN-boxing is not checked for instructions like fsw and fcvt.x.w. These instructions must ignore the upper FLEN-n bits).
But when I compiled the latest commit and ran this, it showed an unexpected behaviour:
$ ./build-Linux/whisper --isa imafdc --interactive
whisper> poke m 0 0x53
whisper> s
#1 0 00000000 00000053 c 0300       00001800  fadd.s   f0, f0, f0, rne  +
#1 0 00000000 00000053 c 0341       00000000  fadd.s   f0, f0, f0, rne  +
#1 0 00000000 00000053 c 0342       00000002  fadd.s   f0, f0, f0, rne  +
#1 0 00000000 00000053 c 0343       00000053  fadd.s   f0, f0, f0, rne
whisper>

Hi Urvish,
We implemented the FS bits of mstatus.  The default value for those bits is
00 (off).  To enable floating point you need to set them to 01:
poke c mstatus 0x3800
poke m 0 0x53
s
Alternatively you change the reset value of mstatus by creating a config
file, say whisper.json and putting the following in it:
{
"csr" : {
"mstatus" : {
"reset" : "0x3800",
"exists" : "true",
"mask" : "0x6088"
}
}
}
Then you can run like this:
whisper --configfile whisper.json --isa imacfd -i
poke m 0 0x53
s
Or you can enable newlib emulation (which enables extensions a,f, and d and
turns on floating point in mstatus):
whisper --newlib -i
poke m 0 0x53
s
Joe
Joe
On Fri, Feb 26, 2021 at 2:33 AM Urvish Patel<EMAIL_ADDRESS>wrote:

Hi Joe,
Thanks for the response. Actually, I was using an older version, which was
not having this fix (Also, does the latest commit take into account that
NaN-boxing is not checked for instructions like fsw and fcvt.x.w.
These instructions must ignore the upper FLEN-n bits).
But when I compiled the latest commit and ran this, it showed an
unexpected behaviour:
$ ./build-Linux/whisper --isa imafdc --interactive
whisper> poke m 0 0x53
whisper> s
#1 0 00000000 00000053 c 0300       00001800  fadd.s   f0, f0, f0, rne  +
#1 0 00000000 00000053 c 0341       00000000  fadd.s   f0, f0, f0, rne  +
#1 0 00000000 00000053 c 0342       00000002  fadd.s   f0, f0, f0, rne  +
#1 0 00000000 00000053 c 0343       00000053  fadd.s   f0, f0, f0, rne
whisper>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chipsalliance/SweRV-ISS/issues/7#issuecomment-786494771,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASHQXYKYF7GNCZDQQZMO5DTA5MGDANCNFSM4YF2LBLQ
.

Hi Joe,
Are 's' and 'u' (supervisor and user mode) supported by newlib emulation?
Urvish

They should be
On Mon, Jul 12, 2021, 8:08 AM Urvish Patel @.***> wrote:

Hi Joe,
Are 's' and 'u' (supervisor and user mode) supported by newlib emulation?
Urvish
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chipsalliance/SweRV-ISS/issues/7#issuecomment-878264346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASHQXYNBIAAQQ5CPCWJSOLTXLSLZANCNFSM4YF2LBLQ
.


Codegen proto_utils fix

This should go into the pending dgquintas/codegen_lib branch for the time being. Removing PR.


Rethrow the exception from the underlying method. This fixes #21.

Is there any release planned to get this out?

On it.

A new release is now planned for next week. Apologies for the delay.

Thanks a lot. Great tool and good support.

Did that release happen? I could not find it on mvnrepository yet.

This is on the radar, but hasn't happened yet. I've created https://github.com/GoogleCloudPlatform/cloud-trace-java-instrumentation/issues/28.


Substitute internal/custom error in place of context deadline exceeded error

It's probably worth substituting a context deadline exceeded error with an internal error value that clearly indicates to a sysadmin that the problem is timeout related. Seeing a "context deadline" error message likely doesn't mean a whole lot.
Example from a failing snapshots age service check:
Error occurred while destroying view
CRITICAL: Error retrieving list of VMs from resource pools list

**ERRORS**

* failed to retrieve VirtualMachines from object: Resources: context deadline exceeded

Also note: the Error occurred while destroying view text shouldn't have been emitted to stdout, but rather set as debug output or wrapped with the other error message chain. #462 will track that specific problem.

It's probably worth substituting a context deadline exceeded error with an internal error value that clearly indicates to a sysadmin that the problem is timeout related.

Not sure yet where in the process that the cause of plugin exit is related to a timeout would be emitted as a log message.

I've got an implementation that will go into the v0.25.0 release, but is likely not the final form.


Improves README.

Part of https://github.com/maliput/maliput_documentation/issues/100
Summary
This PR improves the README file:

Providing information about installation via binaries.
Providing information about installation via sources.
Linking to online documentation

The idea of this PR is to define a README format that can be replicated for the rest of the repositories as part of https://github.com/maliput/maliput_documentation/issues/100

Thanks for initiating this process @francocipollone
I have some maintenance concerns related to the repetition of installation steps for all packages/repositories. From the top of my head I can only identify delphyne repositories with a different requirement (drake_vendor) from the standard rules. Then, why would we repeat it everywhere when we have a repository that concentrates all that information?
Unsolicited opinion of how it should be: https://docs.ros.org/en/rolling/The-ROS2-Project/Contributing/Developer-Guide.html#documentation :

All packages should have these documentation elements present in their README or linked to from their README:

Description and purpose

I think we could be more descriptive here.

Definition and description of the public API

We could link to the doxygen documentation that extensively explains this.

Examples

We could reference to maliput_integration and maliput_integration_tests if required. Also delphyne_demos.

How to build and install (should reference external tools/workflows)

We could link to the readthedocs documentation.

How to build and run tests

We could link to the readthedocs documentation.

How to build documentation

We could link to the readthedocs documentation.

How to develop (useful for describing things like python setup.py develop)

We could link to the readthedocs documentation.

License and copyright statements

We could add the badges for the license as other projects do (pointing to maliput_infrastructure nightly builds for example).
What do you think?

Agree overall, following ROS2 suggestion seems the way to go.

I have some maintenance concerns related to the repetition of installation steps for all packages/repositories.

I had the same concern however I decided to proceed that way to give each package certain "autonomy" instead of directly pointing to the main documentation, which explains, in a general manner, how to install maliput packages.
Even though I don't expect the installation process to change in time, as we are compatible with ros index, It may need rewording once we support other ros version, so I could agree on leveraging the online docs directly.

Description and purpose

I think we could be more descriptive here.

Note that for maliput we have the maliput_overview page which I find quite complete regarding maliput package. For the other packages we could be quite descriptive as we don't have docs in other places about their general description, unless we decide to add general descriptions for the backends in the online docs.

Definition and description of the public API

We could link to the doxygen documentation that extensively explains this.

Yes agree, as a API reference.

Examples
We could reference to maliput_integration and maliput_integration_tests if required. Also delphyne_demos.

In the particular case of maliput, for examples we have to rely on an implementation, so agree on pointing to maliput_integration. Also the backends are "examples" of an implemented maliput. I am working on a "getting started" page for the online docs, maybe we could point to that also.

How to build and install (should reference external tools/workflows)

We could link to the readthedocs documentation.

I think that doing so for the binary installation make total sense, that's why I pointed to that and then just indicate which is the package of the moment. However, I am not totally sure about the source installation given that readthedocs docs in this matter, are particularly oriented to source installing the entire ecosystem. When in fact, just cloning one repo, installing deps via rosdep (even maliput-related deps) is way easier than setting up everything(using repos files and waiting too much time for building all the maliput repos when you are interested in only one)

How to build and run tests

We could link to the readthedocs documentation.

sure

How to build documentation

We could link to the readthedocs documentation.

Sure

How to develop (useful for describing things like python setup.py develop)

We could link to the readthedocs documentation.

Sure

License and copyright statements
We could add the badges for the license as other projects do (pointing to maliput_infrastructure nightly builds for example).

Agree with the badges for this but I am not sure how it is related to the nightly builds.

@agalbachicar, Labeling @tfoote as he probably has a wise opinion here.

Let me know what you guys think @agalbachicar @tfoote

@liangfok It is ready for another pass


Bugfix using CHIP_CONFIG_SECURITY_TEST_MODE will not allow to build.

Issue : When enabled the CHIP_CONFIG_SECURITY_TEST_MODE created a call for otThreadGetNetworkKey API. The API call fails due to wrong number of arguments
Modified the API call otThreadGetNetworkKey() to return the otKey as an argument out. Following the declaration
void otThreadGetNetworkKey(otInstance *aInstance, otNetworkKey *aNetworkKey);

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

In view of this https://github.com/project-chip/connectedhomeip/pull/28058 there's probably no need for the API version check?

@selissia Yes we can ignore that. I didn't realize that it has been broken for so long. The other comment needs to be addressed still.