Documentation feedback on /docs/install/redhat.rst (SUSE support)

Hi again. Coming from GH-71, we wanted to report that installation on SUSE and derivates fails with an error about signing.
Problem
zypper --plus-content=cratedb-ce-stable install -y crate

Temporarily enabling repository 'CrateDB RPM package repository - x86_64 - Stable'. [--plus-content]
Warning: File 'repomd.xml' from repository 'CrateDB RPM package repository - x86_64 - Stable' is unsigned.

    Note: Signing data enables the recipient to verify that no modifications occurred after the data
    were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
    and in extreme cases even to a system compromise.

    Note: File 'repomd.xml' is the repositories master index file. It ensures the integrity of the
    whole repo.

    Warning: We can't verify that no one meddled with this file, so it might not be trustworthy
    anymore! You should not continue unless you know it's safe.

Repository 'CrateDB RPM package repository - x86_64 - Stable' is invalid.
[cratedb-ce-stable|https://cdn.crate.io/downloads/yum/7/x86_64] Valid metadata not found at specified URL
History:
 - Signature verification failed for repomd.xml

@matriv suggested:

Isn't there a way for Suse to skip this verification, and only verify the package itself?
The signing of the repo data is optional (at least for Centos and Redhat).

There is a corresponding setting, right. It is called repo_gpgcheck=0, or, alternatively, use the zypper parameter --gpgcheck-allow-unsigned-repo.

https://github.com/ansible-collections/community.general/issues/2519

Problem
When adding repo_gpgcheck=0 to /etc/zypp/repos.d/cratedb.repo, there is an error:
Signature verification failed [4-Signatures public key is not available]

Details
zypper --plus-content=cratedb-ce-stable install -y crate

Temporarily enabling repository 'CrateDB RPM package repository - x86_64 - Stable'. [--plus-content]
Retrieving repository 'CrateDB RPM package repository - x86_64 - Stable' metadata ........................................................................................................[done]
Building repository 'CrateDB RPM package repository - x86_64 - Stable' cache .............................................................................................................[done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
  crate

1 new package to install.
Overall download size: 127.0 MiB. Already cached: 0 B. After the operation, additional 235.1 MiB will be used.

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: crate-5.7.0-1.x86_64 (CrateDB RPM package repository - x86_64 - Stable)                                                                                (1/1), 127.0 MiB
Retrieving: crate-5.7.0-1.x86_64.rpm .........................................................................................................................................[done (6.0 MiB/s)]
crate-5.7.0-1.x86_64.rpm:
    Header V4 RSA/SHA256 Signature, key ID 7faae51a06f6eaeb: NOKEY
    V4 RSA/SHA256 Signature, key ID 7faae51a06f6eaeb: NOKEY

warning: /var/tmp/AP_0xML3p6q/crate-5.7.0-1.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 06f6eaeb: NOKEY
Looking for gpg key ID 06F6EAEB in cache /var/cache/zypp/pubkeys.
Looking for gpg key ID 06F6EAEB in repository CrateDB RPM package repository - x86_64 - Stable.
  gpgkey=https://cdn.crate.io/downloads/yum/RPM-GPG-KEY-crate
Retrieving: RPM-GPG-KEY-crate ...........................................................................................................................................................[error]
crate-5.7.0-1.x86_64 (CrateDB RPM package repository - x86_64 - Stable): Signature verification failed [4-Signatures public key is not available]
Abort, retry, ignore? [a/r/i] (a): a
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.

CrateDB on SUSE in a nutshell.
Use that config in /etc/zypp/repos.d/cratedb.repo.
[cratedb-ce-stable]
name=CrateDB RPM package repository - $basearch - Stable
baseurl=https://cdn.crate.io/downloads/yum/7/$basearch
enabled=0
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://cdn.crate.io/downloads/yum/RPM-GPG-KEY-crate
autorefresh=1
type=rpm-md

[cratedb-ce-testing]
name=CrateDB RPM package repository - $basearch - Testing
baseurl=https://cdn.crate.io/downloads/yum/testing/7/$basearch
enabled=0
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://cdn.crate.io/downloads/yum/RPM-GPG-KEY-crate
autorefresh=1
type=rpm-md

Use that command to import the public GPG key, in order to make signature validation work.
rpm --import https://cdn.crate.io/downloads/yum/RPM-GPG-KEY-crate

Finally, use those commands to install and start CrateDB.
zypper --plus-content=cratedb-ce-stable install -y crate
systemctl start crate

Thx a lot @amotl, see: https://github.com/crate/distribute/pull/680


Split improvement-branch into PRs for review

For the last few days, I've been exclusively developing on the https://github.com/cancerDHC/ccdhmodel/tree/improvement-batch branch, which therefore has a number of unrelated changes all smushed into a single branch. This issue covers dividing that branch into separate PRs for easier review, and then deleting it once that has been done.

This is complete as of PR #56, closing.


CF_MODPACK_MANIFEST not using overrides

Describe the problem
CF_MODPACK_MANIFEST is not adding the override files into the data config folder.
Container definition
version: "3"

services:
  mc:
    image: itzg/minecraft-server:java8-multiarch

    # needed with autostop
    restart: no
    tty: true
    stdin_open: true
    ports:
      - "25565:25565"
    environment:
      EULA: "true"
      TYPE: AUTO_CURSEFORGE
      CF_API_KEY: ${CF_API_KEY}
      FORGE_VERSION: "<IP_ADDRESS>60"
      VERSION: 1.12.2

      # wait for https://github.com/itzg/docker-minecraft-server/issues/2530
      # REMOVE_OLD_MODS: "true"
      ENABLE_ROLLING_LOGS:  "true"

      ENABLE_AUTOSTOP: "true"
      OVERRIDE_SERVER_PROPERTIES: "true"

      # resource constraints
      MAX_PLAYERS: "10"
      MAX_MEMORY: "8G"
      VIEW_DISTANCE: "8"

      # game preference
      CF_MODPACK_MANIFEST: /manifest.json
      CF_SLUG: "custom"
      DIFFICULTY: "hard"
      LEVEL: "word-data"
      ENABLE_WHITELIST: "true"

    volumes:
      - ./data:/data
      - ./modpack-client/manifest.json:/manifest.json:ro

    env_file:
      - .env

Container logs
No response

Overrides only exist in the modpack zip file and doesn't logically make sense when supplying a manifest file. Perhaps you missed the option for CF_MODPACK_ZIP where you can supply a zip that contains the manifest and overrides:
https://docker-minecraft-server.readthedocs.io/en/latest/types-and-platforms/mod-platforms/auto-curseforge/#unpublished-modpacks


Don't set nu and rnu, don't toggle unless &nu

Closes #19. Checks if number is enabled when before toggling
relativenumber, to disable numbertoggle automatically for buffers
without line numbers enabled (like the ones opened by Goyo and
NERDTree).
Please try it out (you'll have to set number and relativenumber yourself from this patch on), and let me know if it works with your plugins that open numberless buffers. ❤

From 2.1.0 on, numbertoggle won't :set number relative number anymore, and it's disabled automatically when number is not set.
Thanks for reviewing, @Leandros!

Thanks for the fix! 🎉


Introduce build/reload request

The reload request instructs the build server to reload the build configuration.
This request should be supported by build tools that keep their state in memory.
If the reload request returns with an error, it's expected that other requests
respond with the previously known "good" state.
This request is motivated by tools such as sbt, which maintain an in-memory state of the build, where reloading the build on-demand is not considered practical.
Prompted by discussion in https://github.com/sbt/sbt/issues/5783
Solves #134
cc @adpi2

Discussion point: should this be build/reload or workspace/reload?
build/reload may be better than workspace/reload because it is part of the server lifetime category with:

build/initialize
build/shutdown
builld/exit

You are right @jvican. It makes sense since we have the uri field in workspace/buildTargets.
So I guess we should rename it workspace/reload and have an uri field in the params.
Sorry @jastice for misleading you on this.

So I guess we should rename it workspace/reload and have an uri field in the params.

True, though the workspace is implicitly provided via the working directory of the build server, so we probably don't need a uri field

I think we do because some build server does not "live" in the same "working directory". Bloop, for instance, can manage many workspaces and he wants to know which one to reload.

I think we do because some build server does not "live" in the same working directory. Bloop, for instance, can manage many workspaces and he wants to know which one to reload.

Yes, but the server that the clients speaks to is always started in the workspace root directory. Note we don't have any root uri parameter for workspace/buildTargets either.

Oh yes you are right. Thank you for the clarification.

I am ready to submit the implementation of workspace/reload in sbt as soon as this one is merged!
See https://github.com/sbt/sbt/pull/5838

updated to workspace/reload


Update Helm

Latest helm version has some super important (10x) speed improvements for rendering.
Please update to latest version of helm.

More info why this is needed.
https://github.com/helm-unittest/helm-unittest/pull/277#issuecomment-1902630682
I should add that its 1200 tests that pass with this, which should give good indicators that it shouldn't break anything

@stavros-k With this not getting much attention at all and even code being merged that fails its own test, forking might become an option.


timeplus configuration

add configuration entry for timeplus workspace and apikey

(Jove Github Bot) added it to the current sprint.


Improving Trend Trove: Expanding Clothing Options, Design Variety, and Feature Page Functionality

Include traditional styles alongside western ethnic on the home page.
Add more unique designs to the trending clothes section.
Develop the missing "Feature" page for better product promotion.
Introduce more collections to enhance user choice.
@Tejashri-Taral plz assign this project to me.

@devki412 Product page already updated. Is there anything you would like to add?

Expanding clothing options and also show feature traditional cloth options
on home page and redesign navbar
On Thu, 10 Oct, 2024, 1:26 am Tejashri Taral, @.***>
wrote:

@devki412 https://github.com/devki412 Product page already updated. Is
there anything you would like to add?
—
Reply to this email directly, view it on GitHub
https://github.com/Tejashri-Taral/TrendTrove-Ecommerce/issues/150#issuecomment-2403318774,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BLWMCRXVXQ675PYN75LB75LZ2WC5VAVCNFSM6AAAAABPNOJHQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBTGMYTQNZXGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Longest consecutive subsequence in python

🚀 Feature
Given an array of positive integers. Find the length of the longest sub-sequence such that elements in the subsequence are consecutive integers, the consecutive numbers can be in any order
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
To contributing Gssoc'21
Pitch
Input:{2,6,1,9,4,5,3}
Output:
6
Explanation:
The consecutive numbers here
are 1, 2, 3, 4, 5, 6. These 6
numbers form the longest consecutive
subsquence.

/assign


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3816

Questions ?
Please refer to the Backport tool documentation


Programmatic way of updating JSON summary instances

Since you can fetch a JSON summary, you should be able to modify some of its values, and either call .save() which creates a new result, or call .update() which modifies the result. Probably also a good idea to have .delete() for removal of results.

I am not sure if this is really a good idea in the end. It feels like once results are saved, they should never be modified since they are the most representative of the "raw" data. Instead, it might be more useful to clone/copy them into another experiment's directory.


Gateway server is failing Evaluate/Endorsement when non-endorsement org peers are bad

Channel default Endorsement Policy - Specific Org -  PeerOrg1
2 Peer Orgs (PeerOrg1, PeerOrg2) are joined as writers on the channel
Collection configuration includes both orgs
Chaincode A - does not use collection - is installed/approved on PeerOrg1 only.
Chaincode B - uses collection, is installed and approved on both PeerOrg1 and PeerOrg2.
Invocations (grpc.Method=Endorse) to Chaincode B and Chaincode A go to PeerOrg2 peers (as first endorser) even though its not part of endorsement policy.

@bviswana101 Is your client targeting PeerOrg2 specifically? I believe gateway will attempt the first endorsement on the target peer, so it is up to the client to target at least one 'good' peer that it trusts, and then that peer can collect other endorsements as needed.
@bestbeforetoday keep me honest...

@denyeart No, infact we introduced a ProposalOptions.endorsingOrg to explicitly set it to PeerOrg1.
Evaluate always fails when any peer in PeerOrg2 is not reachable.
Endorse intermittently fails when any peer in PeerOrg2 is not reachable.
I believe the Proposal is not sent to PeerOrg2 peers itself, However, it is not reasonable to expect that all peers are available at all times.

@bviswana101  So you target PeerOrg1, the endorsement policy is PeerOrg1, and yet endorsement requests can fail if PeerOrg2 is not reachable by PeerOrg1?
If that is what you are saying, I agree that doesn't sound correct.

I tried to reproduce bad peer/org targeting in isolation as follows:

Modified the deployCC.sh script in the Fabric test-network so that chaincode is installed to only the Org1 peer.
Brought up the test-network and deployed chaincode:./network.sh up createChannel -c mychannel -ca
./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go/ -ccl go -ccep 'OR("Org1MSP.member","Org2MSP.member")'

Ran the asset-transfer-basic/application-gateway-typescript sample application, which submits and evaluates transactions using the Org1 Gateway peer and without any specific org targeting.

This worked fine.
I then repeated the test but this time installing the chaincode to only Org2 peer, while the application continues to use the Org1 Gateway peer. This also worked fine.
Perhaps the failures you are seeing are a special case of the behaviour reported in #556, where the Gateway is trying to establish connections to unreachable peers as part of its network discovery, not an issue of selecting incorrect endorsers.

I have also come across a similar issue while using fabric-gateway go client v1.3.0 but it got solved if I downgrade my client version to fabric-gateway go client v1.2.2. Please find my findings below.
Organizations: Org1, Org2, Org3
Peers: each organization has 3 peers among that 2 peers will be anchor peers.
Chaincode: Same version installed, approved, and committed in all organization's peers
Happy path:
Scenario 1: When all organization's anchor peers are up if org2 app invokes a smart contract on peer1Org2 that mutates state on private collection shared by Org1 and Org2 with endorsers as org1 and org2. Endorsement is successful and Block got committed.
Scenario 2: When all organization's anchor peers are up but org3's anchor peer is down(providing default TLS which is resulting in TLS Handshake error on other active peers). If the org2 app invokes a smart contract on peer1Org2 that mutates state on private collection shared by Org1 and Org2 with endorsers as org1 and org2. Endorsement is successful and Block got committed.
Failure Scenario:
When all organization's anchor peers are up but Org3's anchor peer is down(providing default TLS which is resulting in TLS Handshake error on other active peers) and while Org3's peer was down if org2 peers got restarted. If the org2 app invokes a smart contract on peer1Org2 that mutates state on private collection shared by Org1 and Org2 with endorsers as org1 and org2, in this case, the endorsement is not successful. Even though the gateway client config timeout (as mentioned below). The application still waiting for Org3's peer to be up, once endorsement is successful and Block got committed.
gateway, err := client.Connect(
  id,
  client.WithSign(sign),
  client.WithClientConnection(grpcConn),
  client.WithEvaluateTimeout(5*time.Second),
  client.WithEndorseTimeout(15*time.Second),
  client.WithSubmitTimeout(5*time.Second),
  client.WithCommitStatusTimeout(1*time.Minute),
)

Issues:

Should not expect other Org's peers to be up and running as long as the Org is not endorsing the entity.
Gateway clients should honor the timeouts.

@krishnanmano The first of the issues you report - Gateway peer waiting for org peers not required for endorsement - seems similar to the server-side mis-behaviour that this issue is addresses. This should not be affected by the version of the client API used. A fix went into Fabric v2.4.9 (and v2.5) that was supposed to address this server-side behaviour. More details in issue #556. Can you confirm which Fabric peer version you are using?
The Gateway client timeout behaviour seems to be something separate. The Fabric Gateway client API configures the default client-side timeout on the Context used for the underlying gRPC calls. There are unit tests that (should) confirm this happens, and I don't believe there has been any change to the code or behaviour in that area between v1.2.2 and v1.3.0 of the client. What has changed is the version of the google.golang.org/grpc dependency. It is possible there was a bug or regression in behaviour of the gRPC version used by fabric-gateway v1.3.0. This dependency was updated again for the v1.3.1 release, so it might be that moving forward to that version also solves issues for you.
Which problem was solved for you by moving from fabric-gateway v1.3.0 back to v1.2.2?

Thanks @bestbeforetoday for your reply.

I am using the fabric peer version 2.4 now.
By reverting gateway client from version 1.3.0 to 1.2.2, smart contact execution going through fine even though non endorsing org peers are down (returns tls handshake error), same is not working on 1.3.0.

As you suggested i will try the same scenarios with fabric peer version 2.4.9 or above and gateway client version 1.3.1.

@bestbeforetoday, I have tried the same scenario with the latest version of gateway client 1.3.1 and Fabric peer version 2.4.9. Still, if Org3 peers are down and at the same time Org2 peers get restarted then the smart contract invoked on Org2 is failing, where Org3 is not endorser. Smart contract invokes working fine only after Org3 Peers come back online.

Thanks for trying. I am still confused by the different behaviour you report depending on the client API version. All the client API does is send an endorse request to the peer Gateway service, and this has not changed at the client end. The peer Gateway service handles the endorsement (identifying the endorsement requirements, selecting endorsing peers, fail-over between peers, etc.).
Are you still seeing the problem that the client API is not timing out after the configured endorse timeout?
Looking back at your initial problem description, I have some questions to make sure I understand the scenario correctly:

You say, "with endorsers as org1 and org2". Are you specifying the endorsing orgs explicitly at the client end, or letting the Gateway determine the required endorsers?

In the failure case:

An org2 Gateway peer is used.
Org 3 anchor peer is down.
And, "while Org3's peer was down if org2 peers got restarted"

Could you clarify the exact sequence of events for org2 and org3 peers that triggers the failure?

You say both, "the endorsement is not successful", and, "the application still waiting for Org3's peer to be up". Do you observe and endorsement failure, or do you just observe the endorsement process blocking until org3 peers are up?

Do you see evidence (perhaps from the Gateway peer logs) that it is waiting longer for peers to become available than the timeouts in the Gateway peer configuration?

Fabric v2.4 has been superseded by Fabric v2.5 LTS so investigation and any fixes will probably need to target that version. Is it possible to provide an absolutely minimal sample and scripts (or specific steps) than can be used to reproduce the failure?

Closing due to inactivity - assuming resolved.


Question: what is the ETA of the 3.2.0 release?

Hello team!
Thanks a lot for your great work on this plugin <3
I'm having a question: what is the ETA of the 3.2.0 release? It contains really important bugfix (#2572).
Regards,
Albert

This November.
Unfortunately we cannot back-port it since it is a bit of breaking change in the behavior.
Please, use Discussions next time for this kind of questions.


[Refactoring] Fix a crash that occurred when converting if/else of enum with raw value to switch statement

If the enum has a raw value, E passed in to BinaryExpr is a DeclRefExpr, not a DotSyntaxCallExpr, so we crashed on dyn_cast<DotSyntaxCallExpr>(E->getFn())->getFn().
Only look through DotSyntaxCallExpr if E is indeed a DotSyntaxCallExpr. While at it, fix a few other potential sources of nullptr crashes.
rdar://84707973
CC @Regno

@swift-ci Please smoke test


Solutions include (slightly) incorrect solutions for specific joint angles

After multiple reports, I've finally been able to reproduce this problem.
There is a test to check the correctness of all the returned IK solutions i.e. test_correctness(), which tests:
FK(random_joints) == FK(IK(FK(random_joints)))

for 10000 random_joints. I have also never noticed any problems when doing IK with the TCP poses from the real robots. However a problem occurs when users use specific, nice, round joint angles such as:
joints = np.deg2rad([0, -45, -90, -90, 90, 0])

This triggers an incorrectly handled edge case in the IK calculations. This seems to manifest (only?) as additional incorrect joint solutions being included. What is striking however is that these solutions are only slighty incorrect, i.e. the TCP pose is translated a few cm or rotated a few degrees.
There are two fixes possible:

Easy fix: run FK on all IK solutions and remove incorrect ones, this won't increase runtime significantly as IK is cheap.
Best fix: correctly handle the edge cases, but this required some digging.

For now, I'll implement the easy fix and add a test case for these specific angles.

Easy fix implementen in: https://github.com/Victorlouisdg/ur-analytic-ik/commit/0c7a8cc7a16e8aef03bdc8c5683954be724a2dc8

@adverley, I think this one solves all your problems?

Let's close it for now, I won't have any opportunities to test this the
next two months.
Thanks for the update!
On Fri, 6 Dec 2024 at 15:08, Thomas Lips @.***> wrote:

@adverley https://github.com/adverley, I think this one solves all your
problems?
—
Reply to this email directly, view it on GitHub
https://github.com/Victorlouisdg/ur-analytic-ik/issues/5#issuecomment-2523330260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLT5VHGZ3NR3JY6NTA6ZT32EGVWLAVCNFSM6AAAAABTEXRBBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRTGMZTAMRWGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


⚠ Bofrost.be has degraded performance

In 41c6425, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1494 ms

Resolved: Bofrost.be performance has improved in 918344a after 35 minutes.


Volume resets when application refreshes/video changes.

OS: PopOS 22.04
Gnome: 42.5
Application Volume Mixer: 11
When a new YouTube video or song on YouTube music plays the slider is reset to the default value.

This is due to the OS/Firefox after further investigation.


Add time it and major refactor

Checklist:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you successfully run tests with your changes locally?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

Issues Solved
Fixes #35

Hi! Thanks for PR.
Make sure you have checked points in PR Template correctly.
(Powered by GitMate.io)


Not receiving messages with ManagedMqttClient

Which project is your question related to?

ManagedClient

Development environment

Visual Studio 2019 on Windows 10.
Xamarin Forms project, developing for Android and iOS. Currently doing all my testing on a Nexus 5X running Android 8.1.
Nuget packages installed: MQTTnet and MQTTnet.Extensions.ManagedClient (version 3.0.14).

Description of the issue
I have a microcontroller that is sending out messages to an MQTT server, and then an Android device that is subscribed to receive those messages. The microcontroller is sending the messages properly, and the server is receiving them properly. The server, by the way, is PubNub's MQTT server (https://www.pubnub.com/docs/sdks/mqtt-pubnub-bridge/).
I am using MQTTnet to subscribe to the topic and receive the messages. I am using the ManagedMqttClient, and it works....sometimes....?
It will seem like it is working perfectly for a bit, but then sometimes it will just inexplicably stop receiving the messages. At the same time, however, the server is definitely still receiving the messages from the microcontroller, because I am logged on to PubNub and using their debug console I can see the messages arriving on the server.
I have noticed that sometimes it will get fixed if I change the "uuid" in my Android code and re-build my solution, but it doesn't always work like that.
Here is my code. It is pretty simple. Setting up the MQTT connection:
//Setup and start a managed MQTT client.
mqtt_options = new ManagedMqttClientOptionsBuilder()
    .WithAutoReconnectDelay(TimeSpan.FromSeconds(5))
    .WithClientOptions(new MqttClientOptionsBuilder()
        .WithClientId(publish_key + "/" + subscribe_key + "/" + client_id)
        .WithTcpServer(server_address, server_port)
        .Build())
    .Build();

mqtt_client = new MqttFactory().CreateManagedMqttClient();
mqtt_client.UseApplicationMessageReceivedHandler(HandleReceivedMessage);
mqtt_client.UseConnectedHandler(HandleConnectedEvent);
mqtt_client.UseDisconnectedHandler(HandleDisconnectedEvent);
mqtt_client.StartAsync(mqtt_options);

My code to subscribe to a topic is also fairly simple:
await mqtt_client.SubscribeAsync(new MqttTopicFilterBuilder()
    .WithTopic(topic_name)
    .Build());

No exceptions are being thrown, and the "connected" event occurs successfully (the HandleConnectedEvent event handler that I defined is getting called). But the messages just simply aren't arriving... any thoughts?

Can you share what was the solution here?


editors - do not report as readonly based on file service handling

fix #91833

This PR fixes #

@isidorn this pretty much restores how it used to be:
https://github.com/Microsoft/vscode/blob/ae08d5460b5a45169385ff3fd44208f431992451/src/vs/workbench/contrib/files/common/editors/fileEditorInput.ts#L231

Fix looks good, verifying it fixes the issue...

I have verified this fixes the issue -> approved


Fix bug with loading default schema

Replace relative path with an absolute to avoid errors while using plugin with loctool.

Okay, it is published to npm now


Refactor ObjectStorage and StorageContext

Summary

Merge the ObjectStorage and StorageContext, and provide object_storage functions in the storage_context module.
Make the Table and TypeTable dependent on StorageContext, change table::new(TxContext) to table::new(StorageContext).
Make all TxContext functions as friend. Developers should call these functions through StorageContext.

partial of  #912

How about your 'Context' solution?


BodyParam() knows no "name" variable but is using one

I just tried to start the disco-node server after upgrading to the last commit of irony, encountering the following error:
[...]/irony/build/lib/system/router/decorators/decorators.js:102
        processDecoratedParameter(target, propertyKey, parameterIndex, enums_1.ParamType.body, name);
                                                                                ^

ReferenceError: name is not defined
    at [...]/irony/build/lib/system/router/decorators/decorators.js:102:96

This seems logical to me, reviewing this snippet from the decorators.ts:
export function BodyParam() {
  return function (target: Object, propertyKey: string, parameterIndex: number) {
    processDecoratedParameter(target, propertyKey, parameterIndex, ParamType.body, name);
  };
}

In contrast to the other *Param decorators, BodyParam does not expect the "name" parameter but is passing one to processDecoratedParameter. TypeScript does not fail because the name property was defined in some DOM specific typing file...
Should we simply add a name parameter?

I think I just forgot to push the latest changes, sorry - please pull and try again...

ok, sorry again - another issue - I need to investigate more... please be patient...

No problem :o)


NEW^^Viral@clip) ! Indian Teen School Girl XXX Porn video Orginal Full Hot sex videos

12 seconds ago
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter Telegram
[-𝗟𝗘𝗔𝗞𝗘𝗗-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
Indian Teen School Girl Original Video video took the internet by storm and amazed viewers on various social media platforms. Indian Teen School Girl, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter
Indian Teen School Girl Original Video video oficial twitter
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter..
,
,
,
,
,
,
,
,
,
,
,,
,
,
,
,,
,
,
,
,,
,
,
,
,
,
,
,
,
,
,
,,
,
,
,
,
,,
,
,
,
,
,
,,
,
,
,,
,
,,
,
,
,
,
,
,
,
,,
,
,
,
,
,
,
,
,
,
,
,
,
12 seconds ago
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter Telegram
[-𝗟𝗘𝗔𝗞𝗘𝗗-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
Indian Teen School Girl Original Video video took the internet by storm and amazed viewers on various social media platforms. Indian Teen School Girl, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter
Indian Teen School Girl Original Video video oficial twitter
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter..
,
,
,
,
,
,
,
,
,
,
,,
,
,
,
,,
,
,
,
,,
,
,
,
,
,
,
,
,
,
,
,,
,
,
,
,
,,
,
,
,
,
,
,,
,
,
,,
,
,,
,
,
,
,
,
,
,
,,
,
,
,
,
,
,
,
,
,
,
,
,
12 seconds ago
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter Telegram
[-𝗟𝗘𝗔𝗞𝗘𝗗-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
Indian Teen School Girl Original Video video took the internet by storm and amazed viewers on various social media platforms. Indian Teen School Girl, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter
Indian Teen School Girl Original Video video oficial twitter
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter..
,
,
,
,
,
,
,
,
,
,
,,
,
,
,
,,
,
,
,
,,
,
,
,
,
,
,
,
,
,
,
,,
,
,
,
,
,,
,
,
,
,
,
,,
,
,
,,
,
,,
,
,
,
,
,
,
,
,,
,
,
,
,
,
,
,
,
,
,
,
,
12 seconds ago
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter Telegram
[-𝗟𝗘𝗔𝗞𝗘𝗗-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
Indian Teen School Girl Original Video video took the internet by storm and amazed viewers on various social media platforms. Indian Teen School Girl, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter
Indian Teen School Girl Original Video video oficial twitter
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter..
,
,
,
,
,
,
,
,
,
,
,,
,
,
,
,,
,
,
,
,,
,
,
,
,
,
,
,
,
,
,
,,
,
,
,
,
,,
,
,
,
,
,
,,
,
,
,,
,
,,
,
,
,
,
,
,
,
,,
,
,
,
,
,
,
,
,
,
,
,
,
12 seconds ago
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
Watch 🟢 ➤ ➤ ➤ 🌐 Click Here To link (Full Viral Video Link)
🔴 ➤►DOWNLOAD👉👉 (Full Viral Video Link)
L𝚎aked Video Indian Teen School Girl Original Video Viral Video L𝚎aked on X Twitter Telegram
[-𝗟𝗘𝗔𝗞𝗘𝗗-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Indian Teen School Girl Video Original Video Link Indian Teen School Girl Video Viral On Social Media X Trending Now
Indian Teen School Girl Original Video video took the internet by storm and amazed viewers on various social media platforms. Indian Teen School Girl, a young and talented digital creator, recently became famous thanks to this interesting video.


Configure JVM metaspace for Gradle builds

This PR increases amount of memory for JVM metaspace used for Gradle builds.
The library version is bumped to 2.0.0-SNAPSHOT.92.

@armiol Please take a look.


Doc new g:AutoPairsCompatibleMaps default value 0

8fd8d1e Doc new g:AutoPairsCompatibleMaps default value 0
This was changed in [1].
[1] https://github.com/LunarWatcher/auto-pairs/commit/0fcb708a122d02697b760a7ef52b7ba181bc1f30

I could've sworn I did that already. Thank you!


[Microsoft][ODBC Driver 13 for SQL Server]Login timeout expired

HI,
Trying to create HANA remote source connection using SDA(Smart data access. ODBC MSSQL server connection created using remote source and connected successfully.
while doing test connection we are getting error SAP DBTech JDBC: [403] error.
Error message: SAP DBTech JDBC: [403]: internal error: Cannot get remote source objects: [Microsoft][ODBC Driver 13 for SQL Server]Login timeout expired
SDA Error.docx
)

Please suggest to resolve the issue.
Regards,

Hi, this looks like a connectivity issue. It is sometimes caused by firewall blocking access to the port you're connecting to. Try to connect outside of this application use sqlcmd and ODBC driver, see if it's possible to make the connection.

Hi @ataur2  I am getting the same error, do you mind sharing how you resolved this issue?


Add create-react-context to README

Because create-react-context is a peer deps, it will no be installed. Right now I didn't expect to get any error following the simple example but I had to install the deps first.

Thanks for the contribution!

I feel like we should just add it as a normal dependency

@thejameskyle I wouldn't, this is something that somebody could be using in their application and it is better to avoid any conflicts on the deps.
It doesn't hurt just to add it as a dep in the projects 😄

Yeah, was thinking about it later and came to the same conclusion.

There's probably never going to be a 2.0 of create-react-context and it's small enough that it shouldn't ever really matter. I'm gonna move it


Migrating Todo completed and skipped_datetime to status field

QA:

[x] Add a todo
[x] Add a todo from template
[x] Remove a todo and todolist
[x] Mark as completed/pending -- both flat and nested todo (reload and make sure changes persist)
[x] Mark as relevant/not relevant -- both flat and nested todo (reload and make sure changes persist)
[x] In the QA box, approve of one checklist item and disapprove of another. Add a comment to the disapproved item.
[x] Reload the task. The approved/disapproved checklist items should persist, as should the comment.
[x] Click Copy QA summary and paste it in a text editor. The list should reflect your approval/disapproval/comment.

Coverage decreased (-0.3%) to 94.119% when pulling a0597254151c63d167479c91e21cb9f794549621 on migrate_todo_status into 8f3bfb9aec2f19e8775edb9ce7d7c572f6f2e10d on main.


Android Mobile App Authenticates, but Doesn't Show Rooms

Description
When using the Android Mobile App, I can authenticate, but I cannot see the contents of any rooms. I can search users and rooms, but when selecting I get nothing. Web and desktop clients work.
Latest snap version hosted with Caddy serving it on 3000 on a private IP. Hosted on vcloud where snat and dnat is setup to translate 80 to 3000 on a routable IP. Additional the organization I'm hosting with offers a Web Application Firewall that serves the application on a secured URL with a different IP.
Devices and Versions
Server version: 0.71.1 (Snap)
Android App: 3.1.1
Device: Google Pixel with Android 9
Merge pull request #12499 from RocketChat/release-0.71.1
Steps to reproduce
Install Android app, login.
Clear app cache and storage, open app again, login.
All attempts authenticate user, can hit admin panel, but cannot access rooms. Just shows connecting.
Logs
Can't appear to bring up on my phone. Can provide later when I go into work.

Sorry for my ignorance, is that a server setting under the admin panel or a config entry for caddy?

For privacy purposes, I'd like to not share. Can you provide a simple request you would do to test it?
I can browse to https://REDACTED/websocket and I get an error, "Not a valid websocket request".

@jasonsumner Yes, so your server is not supporting WebSockets. It needs to support in order to use the mobile apps, more info here: https://github.com/RocketChat/Rocket.Chat.Android/issues/1116

I can use a websocket client and connect, I immediately get a server id back. Client reports it is open.

@jasonsumner Do you have any more information? Screenshots, logs?

I have additional information, and this may not be the section for this, but hoping you can send me in the right direction.
Again I have rocket chat listening on 80. My organization offers a reverse proxy that adds ssl from their ca. I have added the certs to Android and the website is trusted, but when connecting from a websocket client I get the following error.
"""Error: Failed to connect to WEBSITE URL port 80 from Port 4851"""
That leads me to believe that there is something wrong with my caddy config, and the server is responding with the URL at 80 and not 443.

I believe there's something wrong in your setup as well... not sure how I can help you here. On the web it works fine?

Yes, web and desktop app works.

It appears to be a certificate issue. Using a websocket client connecting to wss://website/websocket with the connect message documentee I get an error stating ”java.security.cert.CertPathValidationException: Trust anchor for certofication path not found."
I am using a certificate issued to me by our corporate enterprise CA. I have the root CA, intermediate CA, and website certificate installed on my device. Chrome authenticates properly.

@jasonsumner If the root CA is installed and trusted on your device, it should work (I saw other people doing that). Can you double-check?


Unconnected PDN node on net vccd1

INFO PSM-0064] Number of voltage sources = 88.
[WARNING PSM-0038] Unconnected PDN node on net vccd1 at location (367.200um, 1910.580um), layer: 6.
[WARNING PSM-0038] Unconnected PDN node on net vccd1 at location (367.200um, 1910.000um), layer: 5.
[ERROR]: during executing openroad script /openlane/scripts/openroad/pdn.tcl
[ERROR]: Exit code: 1

repo here: https://github.com/mattvenn/zero_to_asic_mpw5
run make user_project_wrapper should fail
might need to run make install to get caravel/openlane scripts first
reproducible.tar.gz

Given that there are no rails (FP_PDN_ENABLE_RAILS='0'), then there are no transistors being supplied off these segments of metal.
If rails are enabled, there is a connection to these stripes through the stdcell rails - when I set FP_PDN_ENABLE_RAILS='1' I get the following result:
[INFO PSM-0031] Number of PDN nodes on net vccd1 = 378519.
[INFO PSM-0064] Number of voltage sources = 88.
[INFO PSM-0040] All PDN stripes on net vccd1 are connected.
########## IR report #################
Worstcase voltage: 1.80e+00 V
Average IR drop  : 8.66e-15 V
Worstcase IR drop: 8.58e-13 V
######################################

So, whilst I agree that the report sections of the grid are disjoint, the fact that there are no connections to transistors mean that the power grid fully connects to all the transistors in the deisgn. The presence of this additional metal is fundamentally benign.

@Colin-Holehouse @maliberty  Is this something that check_power_grid should not be reporting as an error? Let me know if it needs a change.

@mattvenn
Is that resolved?

Sorry, way to late for me to confirm / deny. Feel free to close this issue.


Make a meta label so lists are easier to find

You're making lists to group issues together. This is nice. But can we please have a meta tag for meta-issues?

:+1:

@onbjerg, created.

Thanks!


Unable to run Windows Server ltsc2019 container in hyper-v mode (with Kubernetes CRI)

Description
I am trying to run Windows Server ltsc2019 container on a Windows Server 2022 host as a Kubernetes node

Containerd Version - 1.7.0 (running with default config)

Kubernetes Version - 1.25.7

WIndows Host - Windows server 2022

CNI - Calico

Runtime class - 'runhcs-wcow-hypervisor' has been defined and applied on the container:
The cluster has been provisioned using Cluster-API using the Azure Provider: https://cluster-api.sigs.k8s.io/user/quick-start.html

I get the error that container OS build does not match the host OS. I can see that Shim has provisioned a Virtual Machine for running the hyper-v container, however, I still get the error for build mismatch.

I am able to launch the ltsc2019 container with the ctr tool. However, it does not work when the container is launched via Kubernetes.

Steps to reproduce the issue

Describe the results you received and expected
I was expecting the ltsc2019-amd64 windows container to run seamlessly with hyper-v isolation on Windows Server 2022 Host
What version of containerd are you using?
1.7.0
Any other relevant information
No response
Show configuration if it is related to CRI plugin.
containerd.exe config default | Out-File config.toml -Encosing ascii

@rahulgupta999 Can you paste your containerd config file? It's likely because the SandboxImage defined/being used for your pod is different than ltsc2019. https://github.com/containerd/containerd/blob/7cd72cce99c8d3b938c1b763c2744a0b699028ab/pkg/cri/config/config.go#L256
For Hyper-V, the containers run in the VM it launches still need to match whatever the VMs build is. So if you launched a WS2022 Hyper-V pod, you can only run containers based off a ws2022 image inside.

@dcantah  Thanks for the follow-up. Attached is the toml file
config.toml.txt

@rahulgupta999 Oh, there might be a bigger problem here that I'm remembering for this support at the current moment. Your sandbox image (registry.k8s.io/pause:3.8) is more than fine, and even has a mapping for ws2019 inside:
[6]     Type: application/vnd.docker.distribution.manifest.v2+json
[6]   Digest: sha256:78bfb9d8999c190fca79871c4b2f8d69d94a0605266f0bbb2dbaa1b6dfd03720
[6]   Length: 1969
[6] Platform:
[6]    -      OS: windows
[6]    - OS Vers: 10.0.17763.2928
[6]    -    Arch: amd64

but because your host is ws2022 containerds pull logic determines that the 2022 variant for this image is the correct one to pull. There isn't logic today in the CRI layer for containerd to be able to pull an image that doesn't match the host, so even if we explicitly changed your sandbox_image field in your config file to some 2019 image you'll get an error when going to pull it iirc. Support for this scenario was punted to a future release for the initial hyper-v support for kubernetes here. How important is this scenario to you?
cc The Windows brigade as this is a fun problem 😆@kevpar @kiashok @gabriel-samfira @TBBle

There isn't logic today in the CRI layer for containerd to be able to pull an image that doesn't match the host, so even if we explicitly changed your sandbox_image field in your config file to some 2019 image you'll get an error when going to pull it iirc.

I don't think this is the case? I might be misremembering, but if you pull an image directly (rather than an image index like registry.k8s.io/pause:3.8), there's nothing that validates the relevant OS version flags, and it'll happily run it or fail at the HCS level.
So if I'm not misremembering, then directly referencing the desired sandbox image should work; from 30 seconds of Google search, the relevant tag will be registry.k8s.io/pause:3.8-windows-amd64-1809. It'd be nice if registry.k8s.io had a Web UI, but I'm not aware of one. At worst, you could docker buildx imagetools inspect registry.k8s.io/pause:3.8 and get the relevant image hash for LTSC2019 AMD64 from the output.
Still a bit of a workaround though; this is an interesting use-case that the existing Hyper-V discussions haven't raised (that I'm aware of): When you actually want the older image when a newer image exists, because it's for a sandbox and other images in the sandbox don't have the newer image. I don't think we have a channel to communicate that from k8s via CRI at all.
We'd need a way to defer pulling any images until all images for the sandbox are known, and hence we can solve for an image platform version that is both host-compatible and available in all desired images.
In the meantime, perhaps creating a new runtime class runhcs-wcow-hypervisor-ltsc2019 which references the LTSC 2019 image explicitly (and then referencing that in your pod) is the stablest workaround? Although I can't promise that sandbox_image is actually overridable per-runtime class... If not, that's an annoying oversight. Hopefully it is.

This is from my win 11 host, but I remember this is what you'd get on ws2022 when trying to explicitly pull a ws2019 image (I can't test ws2022 currently but maybe sometime this week).
PS C:\Users\danny\containerd> .\crictl.exe -i npipe:/\\\\.\\pipe\\containerd-containerd pull mcr.microsoft.com/windows/nanoserver:1809
E0410 06:40:56.698418   21296 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = NotFound desc = failed to pull and unpack image \"mcr.microsoft.com/windows/nanoserver:1809\": no match for platform in manifest: not found" image="mcr.microsoft.com/windows/nanoserver:1809"
time="2023-04-10T06:40:56-07:00" level=fatal msg="pulling image: rpc error: code = NotFound desc = failed to pull and unpack image \"mcr.microsoft.com/windows/nanoserver:1809\": no match for platform in manifest: not found"

mcr.microsoft.com/windows/nanoserver:1809 is an image index, albeit containing only one image. Try mcr.microsoft.com/windows/nanoserver@sha256:534e38583dfa4ab78b76d5b8dd31da8db589d981cf1c0eb3c7b34fd6b69b1bbe.

I suspect this is a policy of "immutable tags for images, with floating tags always being image indexes", which I actually 100% agree with, now I think of it.

I quite like this, and yes pulling by sha or version works fine btw. @rahulgupta999 Can you try registry.k8s.io/pause@sha256:78bfb9d8999c190fca79871c4b2f8d69d94a0605266f0bbb2dbaa1b6dfd03720 as the sandbox_image field in your containerd config then, but you'll need to supply the full sha for whatever 2019 image you want to run for your containers in the pod

Thanks, Windows brigade for chipping and sharing your viewpoint.
I will try out the suggestion for updating the sandbox image. However, this won't work for us as my original requirement would require us to run lts2022, ltsc2019, and 2004 based containers on the same node. I could potentially create separate node groups.
Given the issue, I had enforced my clients to upgrade their container images to ltsc2022. For now, this is not a blocker for me. Thanks for sharing more insights on this.

Another problem I faced with hyper-v containers is that they were not reachable from any other pod. This was a problem with Calico CNI. For now, I have worked around in my custom calico build. I am sharing this in case there is some more awareness around this.
https://github.com/projectcalico/calico/issues/7490

@rahulgupta999  .. Just wondering how you worked around this issue and what is in your custom Calico build.


Fix an issue with loading ssl_verify setting for SIP2 integration.

Description
The existing code had an idiotic problem that the type checker was unable to catch. Essentially, calling .value on a configuration setting that contains a value true or false (or really any string), will result in that value being returned as a string. If the code was expecting a bool... Tough luck, it's getting a str.
Using .json_value on the configuration setting instead forces the code to actually interpret the setting's value, and will correctly result in a bool being returned.
Motivation and Context
TLS verification was still being performed, even though the configuration setting stated that it shouldn't be.
How Has This Been Tested?
I ran the existing test suite, and I tested this locally in a debugger. I was not impressed.
Checklist

[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

Going to merge this one, so we can roll out fix to impacted library


bad result detected

I got bad result using layout-parser
here is the image I am used:

here is the code run in python :
image = cv2.imread("1.png")
# Convert the image from BGR (cv2 default loading style)
# to RGB
image = image[..., ::-1]
origin_image = image.copy()

model = lp.Detectron2LayoutModel('lp://PubLayNet/mask_rcnn_R_50_FPN_3x/config',
                             extra_config=["MODEL.ROI_HEADS.SCORE_THRESH_TEST", 0.8],
                             label_map={0: "Text", 1: "Title", 2: "List", 3:"Table", 4:"Figure"})
# Load the deep layout model from the layoutparser API
# For all the supported model, please check the Model
# Zoo Page: https://layout-parser.readthedocs.io/en/latest/notes/modelzoo.html

layout = model.detect(image)
# print("layout : ", layout)
# Detect the layout of the input image
text_blocks = lp.Layout([b for b in layout if b.type=='Text'])
drawRectangleInImage(origin_image, text_blocks, (36,255,12))

titles_blocks = lp.Layout([b for b in layout if b.type=='Title'])
drawRectangleInImage(origin_image, titles_blocks, (76, 155, 175))

figure_blocks = lp.Layout([b for b in layout if b.type=='Figure'])
drawRectangleInImage(origin_image, figure_blocks, (122, 96, 216))

lists_blocks = lp.Layout([b for b in layout if b.type=='List'])
drawRectangleInImage(origin_image, lists_blocks, (176, 155, 175))

tables_blocks = lp.Layout([b for b in layout if b.type=='Table'])
drawRectangleInImage(origin_image, tables_blocks, (76, 255, 75))

cv2.imshow('image', origin_image)
cv2.waitKey()

here is the result:

by the way ：
there is some warning generated ：
/usr/local/lib/python3.9/site-packages/detectron2/structures/image_list.py:99: UserWarning: floordiv is deprecated, and its behavior will change in a future version of pytorch. It currently rounds toward 0 (like the 'trunc' function NOT 'floor'). This results in incorrect rounding for negative values. To keep the current behavior, use torch.div(a, b, rounding_mode='trunc'), or for actual floor division, use torch.div(a, b, rounding_mode='floor').
max_size = (max_size + (stride - 1)) // stride * stride
/usr/local/lib/python3.9/site-packages/torch/functional.py:445: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at  ../aten/src/ATen/native/TensorShape.cpp:2157.)
return _VF.meshgrid(tensors, **kwargs)  # type: ignore[attr-defined]

Thank you for reporting this -- it can be easily resolved by reconfiguring the models hyperparameters, and one example is:  https://github.com/allenai/VILA/blob/96cafe591ae6ee8a70f941a52dd37bbe0a60b243/datasets/s2-vl-utils/vision_model_loader.py#L140 .

Thank you for reporting this -- it can be easily resolved by reconfiguring the models hyperparameters, and one example is: https://github.com/allenai/VILA/blob/96cafe591ae6ee8a70f941a52dd37bbe0a60b243/datasets/s2-vl-utils/vision_model_loader.py#L140 .

Hi, thanks very much for replying
I just want to recognize text, figure and table from published document.
how should I  adjust the parameters?
when I use the extra config in :https://github.com/allenai/VILA/blob/96cafe591ae6ee8a70f941a52dd37bbe0a60b243/datasets/s2-vl-utils/vision_model_loader.py#L140 .
I can recognize text , figure , but math equation can not be recognized.
Thanks!


Implement affinity groups

I am about to implement affinity groups thus opening a ticket to keep track of the progress.
Details about affinity groups can be found in RHEV Administration Guide as well as in RHEV Technical Guide

I have done an initial implementation of affinity groups feature.
I have tested this in RHEV 3.4 and seems to work ok.
Following are the features of this implementation

List affinity groups
List a given affinity group
List VMs assigned to this affinity group
Create new affinity group
Destroy an affinity froup
Assign a VM to an affinity group
Remove a VM from an affinity group

@abenari I have created a separate affinity_group_api.rb, however according to RHEV Technical Guide it is a sub collection of Clusters collection. Please let me know if you want me to move affinity_group_api.rb into cluster_api.rb.

@abenari Any updates here? Thanks.

@pdilung a separate file for the affinity group sounds good, once you'll send the pull request I'll be happy to review the code.
Thanks,
Amos.

@abenari, PR is ready #69.


Rename LayoutKitExampleLayouts to ExampleLayouts so it isn't pulled in by Carthage

These example layouts are not intended to be part of LayoutKit. They
are intended as documentation and proof of concept.

Current coverage is 91.92% (diff: 100%)

Merging #68 into master will not change coverage

@@             master        #68   diff @@
==========================================
  Files            52         52
  Lines          2924       2924
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2688       2688
  Misses          236        236
  Partials          0          0

Powered by Codecov. Last update fc7c907...c6dab29


Unresolved circular dependencies

Do you want to request a feature or report a bug?
Bug report.
What is the current behavior?
An exception gets thrown when trying to extend a class with circular dependencies:
tslib.es6.js:22 Uncaught TypeError: Object prototype may only be an Object or null: undefined
    at setPrototypeOf (<anonymous>)
    at Object.__extends [as a] (tslib.es6.js:22)
    at b.js:4
    at Object.__webpack_exports__.a (b.js:11)
    at __webpack_require__ (bootstrap 4672cf4…:19)
    at Object.defineProperty.value (bootstrap 4672cf4…:65)
    at __webpack_require__ (bootstrap 4672cf4…:19)
    at Object.<anonymous> (bundle.umd.js:108)
    at __webpack_require__ (bootstrap 4672cf4…:19)
    at Object.<anonymous> (bundle.umd.js:321)

If the current behavior is a bug, please provide the steps to reproduce.
Here's a repo to easily reproduce this: https://github.com/jsayol/typescript-issue-14734
$ git clone https://github.com/jsayol/typescript-issue-14734.git
$ cd typescript-issue-14734
$ npm install
$ npm run build

And load index.html in the browser.
This reproduction consists of 3 files:
a.ts:
import { B } from './b';

export class A {
  constructor(public prop: string) {
  }

  b(): B {
    return new B(this.prop, 123);
  }

  log() {
    console.log(`Prop: ${this.prop}`);
  }
}

b.ts
import { A } from './a';

export class B extends A {
  constructor(prop: string, public otherStuff: number) {
    super(`B ${prop}`);
  }
}

index.ts
import { A } from './a';
import { B } from './b';

const a = new A('hello');
const b: B = a.b();
b.log();

What is the expected behavior?
Seeing "B hello" logged in the console.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
OS: Linux
Webpack: 2.2.1
Node.js: 7.7.0

I initially reported this to TypeScript but someone pointed out this was probably a Webpack issue: https://github.com/Microsoft/TypeScript/issues/14734

related to #1788
maybe you find an answer there? Not sure if there is a satisfying solution

Hey @timse. I thought that issue was only about default exports but I took a better look and you might be right, it seems like the same underlying issue.
There's really no solution per se, but as a workaround for now I'm putting both classes A and B in the same file.
Let me know if I should close this issue in favor of the referenced one, or if I should add a comment there with the reproduction I provided here.

This is neither a webpack nor a typescript issue. The behavior is correct according to the spec.
Note that class declarations are not hoisted in ES6.
The execution order is: b.ts a.ts index.ts.
As "fix" switch import { A } from './a'; import { B } from './b'; to import { B } from './b'; import { A } from './a'; in index.ts
This changes the execution order to: a.ts b.ts index.ts.

Thanks for looking into it @sokra. Moving import { B } from './b'; in index.ts doesn't really make a difference since the TypeScript compiller actually drops that line from the generated index.js, as B is only being used as a type.
For reference, the index.js generated by TypeScript and used as an entry point with Webpack is this:
import { A } from './a';
var a = new A('hello');
var b = a.b();
b.log();
//# sourceMappingURL=index.js.map

Following your suggestion, if I manually add import { B } from './b'; at the top of the generated index.js before running Webpack then everything works as expected.
I think TypeScript is correct in dropping that import, so this still feels like something Webpack should be able to detect.
Any thoughts?

TypeScript is not correct in dropping import { B } from './b';. An import may have side-effects and can't be dropped easily. It may optimize it to import './b'; if it's only used for its types.
Your case is a good example for this behavior. Dropping the import breaks the build.
A simpler example:
// a.ts
export class A {}
console.log("test");

// index.ts
import { A } from "./a";
var a: A = null;

Your're absolutely right, @sokra. I just did some googling and it seems that by default TypeScript assumes imported modules imports have no side effects.
So in my initial example, the "correct" way to do it would be:
// index.ts
import './b';
import { B } from './b';
import { A } from './a';

const a = new A('hello!');
const b: B = a.b();
b.log();

Which, when transpiled, generates:
// index.js
import './b';
import { A } from './a';
var a = new A('hello!');
var b = a.b();
b.log();

A bit redundant, but that's what TypeScript expects. I'm just leaving all this here in case anyone else stumbles upon the same problem.
Thanks for your help, @sokra, and sorry for wasting your time :upside_down_face:

Im having the exact same error but in my electron react startup app
All I did was (index.tsx):
import * as React from 'react';
import * as ReactDom from 'react-dom';

export class Test extends React.Component() {
    render() {
        return
helloWorld

    }
}

ReactDom.render(
    <Test />,
    document.getElementById("main")
);

How can this be? did i forget to import something?

Ugh freaking obvious but took me ages -.-
 React.Component() {
should be without () ofcourse:
 React.Component {


Make a release

@chenxianyu2015 would be great to release all the changes made in the recent months.
That includes:

https://github.com/chenxianyu2015/liquid-lua/pull/7
https://github.com/chenxianyu2015/liquid-lua/pull/13

We are forced to use our fork from git: https://github.com/chenxianyu2015/liquid-lua/compare/master...3scale:master that has those changes.
We are using this library to template nginx config in http://github.com/3scale/apicast and it works just fine.

@chenxianyu2015 I'm going to make v0.1 release to https://luarocks.org/modules/3scale/liquid including changes mentioned above plus:

https://github.com/3scale/liquid-lua/pull/4
https://github.com/3scale/liquid-lua/pull/5

Any input from you is very welcome.


error in SQL Editor current connect

DBeaver 7.2.4
Postgresql 9
the task is:
to execute a query for db_m1 in sqlEditor1, open an object of another db_m2 and transfer something to sqlEditor1 and execute for db_m1.
CASE:

two database in objects tree

Open sqlEditor1 for db_m1

Open any object from db_m2. Open db_m2.table

DBeaver change current connect for  sqlEditor1(Script48) to db_m2 without my participation.

It is wrong because I'm sure I'm still working with db_m1 in sqlEditor1(Script48) and i am messed up the data in db_m2.
I'm sure I'm still working with db_m1 in sqlEditor1(Script48). But in fact DBeaver change current connect for  sqlEditor1(Script48) to db_m2.

on version 7.2.5 problem is actual

Hi @detkliff ,
probably you've got Auto-sync connection with navigator option enabled. Can you check?

OK. It is wor for me. Thank you!


Improve settings

[ ] Create an editor separately, instead of replacing existing slogans
[ ] Add a subscription to them
[ ] Add unsubscribe to them

... for ...

[x] Editing slogans
[ ] Changing current slogan

Live sync for editing slogans 2dafa266fbcc144834c73e743989fa4613a7c22e!

Live sync for changing current slogan added in e6fbf30f3010c55f9106159439bcc7e8e2f43d8b!


Add Dark Mode

There are several rules which we have to follow, for quicker implementation
I will try to describe it as much as I can.
Dove #727272 to Dusty #999999
Azure #007fed to Dodge #0c84ff
White #ffffff bg to Cod #141414
Green remains the same
Alabaster #fbfbfb to Venus #232323
Mercury #e9e9e9 to Venus #232323
Mine #2f2f2f to White #ffffff
Dark mode:
https://zpl.io/09kMrOm

I am going to post more comments, cues on Monday.

https://github.com/AlphaWallet/alpha-wallet-ios/issues/3483#issuecomment-980008604
I think you can follow cues from iOS. Apart from outdated buttons, they are all the same.

Nice!
@justindg We'll probably need to sift through and do a minor refactor for all instances where we've used colours directly instead of using theme colours (eg R.color.white instead of R.color.colorTheme for backgrounds etc), what do you think?
Once that's done it should be pretty easy to change this.

@justindg Let me know if you need more info from me. I tried to describe every thing in here

Hey @colourfreak , thank you for the detailed overview. I will be in touch once I start the work on this feature

Hi @colourfreak , what is the preferred color of these showcase/onboarding dialogs for dark mode?
https://app.zeplin.io/project/5d088205bff2d15de6a4397b/screen/5e21865083d02d7acbe394d9
My initial thought was that cod  lacked a bit of contrast with the background, but I'm no expert in this field. Let me know your thoughts.
This is the current iteration (will fix the corner radius soon):

@colourfreak Also what is the preferred color for bottom sheets? Below is the default theme:

Hi @colourfreak , what is the preferred color of these showcase/onboarding dialogs for dark mode?
https://app.zeplin.io/project/5d088205bff2d15de6a4397b/screen/5e21865083d02d7acbe394d9
My initial thought was that cod lacked a bit of contrast with the background, but I'm no expert in this field. Let me know your thoughts.
This is the current iteration (will fix the corner radius soon):

Set the background color of a bubble to Mine

@colourfreak Also what is the preferred color for bottom sheets? Below is the default theme:

Mine


Full SSR support

Description
The library still uses window in some places and thus SSR will fail.
Suggestion
Maybe we can add a getLocation option to the config that will return window.location by default. Having that one could easily pass a static location to Ziggy while using SSR and thus it wouldn't fail.
Alternatives
n/a

I don't think it requires window.
I've got a full Inertia + SSR demo working with no changes to Ziggy. Basically you need Inertia to pass all the Ziggy config to the SSR function, and then redefine your route function to use it.
In PHP, add your routes to the page.
$page['ziggy'] = (new Ziggy)->toArray();

In your SSR, pull ziggy off the payload:
import route from 'ziggy';

return await createInertiaApp({
        page: event,
        render: renderToString,
        resolve: (name) => require(`./Pages/${name}`),
        setup({app, props, plugin}) {
            return createSSRApp({
                render: () => h(app, props),
            }).use(plugin).mixin({
                methods: {
                    // Pull the ziggy config off of the event.
                    route: (name, params, absolute, config = event.ziggy) => route(name, params, absolute, config),
                },
            })
        },
    });

You'll also need to alias ziggy in your webpack config:
const path = require('path')
const mix = require('laravel-mix')

require('laravel-mix-merge-manifest')

mix.webpackConfig({
    resolve: {
        alias: {
            ziggy: path.resolve('vendor/tightenco/ziggy/dist'),
        },
    }
})

Yep, thanks but that's more or less clear. However, you cannot use current() for example. See https://github.com/tighten/ziggy/blob/147804d5f3e98b897fc1ed15efc2807f1099cf83/src/js/Router.js#L72-L74
So that's why I think a configuration possibility would be fine.

Yeah thats true, current doesnt work at the moment

If one of the maintainers agrees, I could raise a PR but without their agreement on the approach I'm reluctant 😉

Yeah ideally the location would come from the config or the window, in that order.

@jaulz here's a workaround for now:
import {createSSRApp, h} from 'vue'
import {renderToString} from '@vue/server-renderer'
import {createInertiaApp} from '@inertiajs/inertia-vue3'
import Router from 'ziggy/Router';

exports.handler = async function (event) {
    return await createInertiaApp({
        page: event,
        render: renderToString,
        resolve: (name) => require(`./Pages/${name}`),
        setup({app, props, plugin}) {
            return createSSRApp({
                render: () => h(app, props),
            }).use(plugin).mixin({
                methods: {
                    // Pull the ziggy config off of the event.
                    route: (name, params, absolute, config = event.ziggy) => {
                        const router = new Router(name, params, absolute, config);

                        let original = router.current;

                        router.current = function (name, params) {
                            global.window = {
                                location: new URL(event.ziggy.url)
                            }

                            let result = original.call(this, name, params);

                            global.window = undefined;

                            return result;
                        }

                        return name ? router.toString() : router;
                    },
                },
            })
        },
    });
}

I'm definitely open to a PR that addresses this! Is it basically just replacing window with some kind of getLocation() function or is there more to it?

@bakerkretzmar reading it off of the config and then falling back to the window would be great for me!


StreamName.For<T>() is prepending type name

Why is StreamName.For<T>() prepending the type name? Why is it depending on T at all?
I have at least two problems with this:

My event store already have established stream ids. Eventuous is unable to read these without me implementing an adapter and hack the incoming stream name.
Renaming an aggregate will disconnect it from existing streams.

What your stream ids look like?

About "Why is it depending on T at all?" - it's because Eventuous is built on the opinion that since a stream is also a transaction boundary, one stream should match one aggregate. Therefore, the stream name is built from the aggregate type and its identity. It's a good default, but it has a limitation about separating, for example, different bounded contexts that have the same aggregate names (and, probably, the same ids) by the bounded context namespace. I had a discussion about it with colleagues just this week.
If you have some samples of what you have in your event store or any suggestion about how to figure out the stream name given the aggregate type and id, I would love to hear that.
And yes, I agree that renaming the aggregate type will break things, and it's not good.

In my opinion stream names shares the same problem as event names. Which you solved with explicit mapping.
One approach is to not tie stream name to aggregate. Another one is to map aggregate types the same way as event types.
But why do you need this at all? We have to provide the stream name/aggregate id in the application service anyway.
Our stream ids look like:
/inventory/customer-id/ad/members
A third option would be to provide us a hook where we can define our own conventions.

I think the default behaviour of the command service is okay. You just need to extract the id, otherwise, you'd need to interpolate the string for the stream id all the time. Also, making it work in a way that you will return the full stream id would make this https://github.com/Eventuous/eventuous/issues/39 impossible.
Detaching stream name from aggregate type is a good idea, I fully agree. If we all agree on that, I can make it work.

Agreed 🙂. Most important to me is to use Eventuous on top of my existing streams. Right now I hacked the stream name in my own adapter for SqlStreamStore. But it’s ugly.

Btw concerning SqlStreamStore, how do you feel using it as it's no longer maintained?

@thomaseyde have a look at #78, I think it will solve the issue you have. Not all overloads of the app service command handler registrations are in place, but it should give you the idea.

@thomaseyde I think specifying the stream name calculation function for each command is an overkill.
My idea is that the identity record can have more properties, then the getId function can populate these properties for each command, and then you need only one id -> stream name function defined per identity type.
https://github.com/Eventuous/eventuous/blob/93cbb3b1f62432052793f8ba63fdf3df8f925393/src/Core/test/Eventuous.Tests/StoringEventsWithCustomStream.cs#L10-L15

Thinking more about this: StreamName and AggregateId are different concerns.
I should be able to identify my aggregate however I like without having to think about persistence. The aggregate should be persistence agnostic.
The stream name, however, is all about persistence and need to contain all information needed.
The ApplicationService then should provide a strategy to map AggregateId to StreamName. This could be a function T -> StreamName.
If I have a common command interface for my aggregate, I could:
StreamName name = StreamNameFrom<IMyCommand>(c => /**/)
If I don't, I could use an object overload and pattern matching:
StreamName name = StreamNameFrom(c => c switch { /**/ }).
Which may be what is suggested earlier here or in a related issue?

The ApplicationService then should provide a strategy to map AggregateId to StreamName. This could be a function T -> StreamName.

It's right in the code I have shown in the previous comment. I merged my PR, so I want to close this now. If you get any feedback, please feel free to provide some.

Docs: https://eventuous.dev/docs/persistence/aggregate-stream/#stream-name


SipServer.sln is missing

Hi, I am compiling on windows system. As guided, firing msbuild SipServer.sln results into SipServer.sn not found.
Is there anything else that I am missing?
Can we use msys to compile the code?

Hi, I am compiling on windows system. As guided, firing msbuild SipServer.sln results into SipServer.sn not found. Is there anything else that I am missing? Can we use msys to compile the code?

Opening the Makefile directly in Visual Studio 2022 and compiling works!


[Vaults UI] Handle file limit upload

Should display a pop to block the document upload if plan restriction is met. Popup and check is already implemented in DocumentUploadOrEditModal , MultipleDocumentsUpload , TableUploadOrEditModal - just need to get the current number of files.
Need clarification on what's the max #documents in the plan : is it per data_source or per workspace ?

current restriction is per data_source.
need to have the pagination implemented  to get the total number of nodes in a dsv, depends on https://github.com/dust-tt/dust/issues/7053


Do not open login shell (-s & -a option)

Unify all the work logs about following features.
-s: option:  Speedy mode. Just execute command. Do not make panes interactive.
-a: keep alive option (do not close pane when the command finished when -s option)

-s option  is came from "speedy" or "sh" or something.
-a No reason but easy to type. 'a' key is by the 's' key.
I believe this feature solves both #89  #90 .

Memo: tmux behavior of split-window command.
https://github.com/tmux/tmux/blob/7448b38327f856dae6ce915eae63f7f6c3f036e0/window.c#L983

   * If given one argument, assume it should be passed to sh -c;
   * with more than one argument, use execvp(). If there is no
   * arguments, create a login shell.

https://github.com/tmux/tmux/blob/master/cmd-split-window.c#L122

I noticed terrible idea,
If you want "to execute commands as is, promptly, on the existing pane", then -sex option is required 🤣
Like this.
$ xpanes -sex 'echo '{01..15}

I am now working on this feature on develop-3.1.0 branch and touch upon the new options.
Finally, I am pretty sure that suppressing closing pane should be default.
I want to change the specification of this feature like this.
Abolish -a option. set -ss option instead.
Before:
-s: option:  Speedy mode. Just execute command. Do not make panes interactive.
-a: keep alive option (do not close pane when the command finished when -s option)-s: option:  Speedy mode. Just execute command. D

After:
  -s: Speedy mode: Run commands promptly. But panes are not interactive.
  -ss: Speedy mode and close windows automatically when process ends.

There are two reasons:

xpanes --help lines up all the options alphabetically.
If -a option is going to be placed upper part of the --help/man page.
In that case, uses may not notice the relationship between -s option.

It is common to use same letters sequentially in Unix commands.
i.e: ssh -vvv option.

This feature is released at v3.1.0


Deleting a post, which has been reported to moderator, give a PHP error

I attempted to delete a single post, which had been reported to moderators:
http://forum.arduino.cc/index.php?action=deletemsg;topic=339965.0;msg=2345326
This page appeared after I clicked on "Remove message":

Fatal error: Call to undefined function recountOpenReports() in /var/www/forum/Sources/RemoveTopic.php on line 1007

It appears that the function recountOpenReports is being called when you remove a message, and this does not exist.

This happened to me some times, I always thought it is some race condition
when multiple moderators are deleting spam at the same time.
If so, task accomplished
On Fri, Aug 7, 2015 at 2:10 AM, Nick Gammon<EMAIL_ADDRESS>wrote:

I attempted to delete a single post, which had been reported to moderators:
http://forum.arduino.cc/index.php?action=deletemsg;topic=339965.0;msg=2345326
This page appeared after I clicked on "Remove message":
Fatal error: Call to undefined function recountOpenReports() in
/var/www/forum/Sources/RemoveTopic.php on line 1007
It appears that the function recountOpenReports is being called when you
remove a message, and this does not exist.
—
Reply to this email directly or view it on GitHub
https://github.com/arduino/forum-issues/issues/191.

I think the message was deleted, but since this has happened twice now, and I already reported it once before directly to Luca, now I am raising a bug report.

Its should be fixed now in http://forumdev.arduino.cc/

Still happening in production a moment ago:
 Fatal error: Call to undefined function recountOpenReports() in /var/www/forum/Sources/RemoveTopic.php on line 1007

Hi nickgammon. Thanks so much for reporting this bug. Since the forum system has been completely changed by the switch to Discourse this week, I'm going to guess this issue is now obsolete. If I'm wrong about that, please comment here and I'll reopen the issue.


Add 2 themes: Classic Retro and Vintage Warm

Classic Retro

Vintage Warm

🎉 Perfect!
Love both themes 😄
Thanks for the additions!


Set git-clone tasks in examples to run as root

Changes
Similar to https://github.com/tektoncd/pipeline/commit/ba2e7f3655d57d3ba3921462f21ece7f86b31488 - with https://github.com/tektoncd/pipeline/pull/4758, git-init now uses ghcr.io/distroless/git as its base image, and that image needs to run as root. git-init by default does not run as root. So the two examples using copy-pasted old versions of the git-clone catalog task need to be changed to run as root, or the example tests will keep failing forever.
An equivalent change will be needed in the git-clone catalog task once it's bumped to using git-init:v0.35.0 or later - currently, it's using v0.29.0.
/kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Docs included if any changes are user facing
[x] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in
(if there are no user facing changes, use release note "NONE")

Release Notes
NONE

@mattmoor - I think this is what you fixed in test/yamls/v1beta1/pipelineruns/*.yaml in https://github.com/tektoncd/pipeline/commit/ba2e7f3655d57d3ba3921462f21ece7f86b31488, which we wouldn't see in the examples tests until after a release, since they're using image: gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init:latest, while the yamls are using image: ko://github.com/tektoncd/pipeline/cmd/git-init (which is why you hit this problem when you changed the base image for git-init in TestYamls but not in TestExamples).
I assume this means we'll need to update the git-clone task in the catalog as well, once it's updated to use gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init:v0.35.0 (or later) as the default (it's currently using gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init:v0.29.0).

/assign @mattmoor
/assign @vdemeester
/assign @lbernick

Thanks for fixing this!
I understand that this is to unblock current PRs from failing integration tests, but would it make sense to update our git init dockerfile to run as root? This would avoid breaking users of this image, which we currently list as part of the API (and we should probably backport it to the release we just did). We could have the examples run an earlier version of the image until the image is fixed.

@lbernick I'm going to defer to @mattmoor on that, since he opened/fixed #4711. =)

/hold

@mattmoor They run, but they used the latest release image of git-init, so won't surface issues there until post release.

/hold cancel
I was just trying to see if there was a non-root workaround, but there isn't one that's simple enough to merit going with it over runAsUser: 0 in the examples to unblock everything else. I've reopened #4711, because I think we need to somehow get rid of the run-as-root requirement, or at least the need to explicitly specify the user when running git-init in a step.

It will be awesome to fix task from Tekton Hub (https://hub.tekton.dev/tekton/task/git-clone) as well, as it based on pretty old image and if users just replace image to newer execution will fail.


add: Add some issue to the web app manually #178

What does this PR do?
Added some issues in the web app manually.

@CYBWEBALI Great work, I see youve made changes to the contributors.md as well. Quick advice , when working on an issue try to make changes related to that issue only. you could have raised a seperate PR to add your name. But, I appreciate your work, Really clean commit message and PR. Well done!

@CYBWEBALI Great work, I see youve made changes to the contributors.md as well. Quick advice , when working on an issue try to make changes related to that issue only. you could have raised a seperate PR to add your name. But, I appreciate your work, Really clean commit message and PR. Well done!

Thank you, Next time I will not make this mistake.


Planets_and_Moons_Dataset_AI_in_Space - Add New

Hello,
I added my Planets and Moons Dataset and AI in Space Software's second version.
Thanks!

Thanks for the PR! There are multiple files in this PR, so before we can review please remove all files except the .py file of the example you want to submit in this PR.

Yes i removed (Only Planet .py, .ipynb, .md and IMG folder remain)

Yes i removed (Only Planet .py, .ipynb, .md and IMG folder remain)

Please follow the instructions in the README and take a look at the .py file for other examples to get an idea of how to format the code.

Yes i removed (Only Planet .py, .ipynb, .md and IMG folder remain)

Please follow the instructions in the README and take a look at the .py file for other examples to get an idea of how to format the code.

Yes i followed after then this generated by automatic from jupyter library.


Tree sharding to process updates in parallel

At the moment, the tree can only safely handle one update at a time. It would be desirable to shard the tree into multiple subtrees and allow parallel updates to the subtrees.

Does this get rid of atomic writes?
Does this have overlap with https://github.com/cosmos/cosmos-sdk/issues/6370

It shouldn't do if implemented correctly! See https://github.com/google/trillian/blob/v1.4.0/merkle/smt/writer.go#L37 for a sharded SMT implementation.

The SDK is about to remove / reduce (?) the multistore because it is not easy to implement this correctly I think. See specifically this comment: https://github.com/cosmos/cosmos-sdk/issues/6370#issuecomment-643226398 (the problem is that the sub-trees are treated somewhat too independently and the abstractions did not make it easy that the writes were actually atomic).
IIUC, the code @musalbas posted is not about sharding into subtrees alá logical subtrees (like in the multistore) but rather about sharding into equal sized shards independent of any logical sub-trees (e.g. accounts, delegations, valsets etc would be logical sub-trees).
Either way, it is probably safe to say that this does not have the highest priority right now?

It's not high priority, but it would be important for execution environments like Solana that support parallel transaction execution.

Agree not high priority


remove s3 consistency check

resolves #

Description

recommended to remove extra validation overhead - https://hudi.apache.org/docs/configurations/#hoodieconsistencycheckenabled
Checklist

[ ] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt-glue next" section.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@menuetb can you validate and merge?

@zhangyuan can you review?


history & duration handling

is new_df a variable in this function or in zoe's branch? its undefined here

it's a variable name to define the df of the input JSON.


Vagrantfile: use KVM paravirt

@unclejack Change looks good to me.
Do you know if this works on MacOS?
LGTM otherwise..


Allow export default interface. Related to issue 3792.

Fixes #3792.

Has the CLA changed? I am pretty sure I signed it before...

@erikmcc, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

@andy-ms can you please review this change.

I pushed tests and fixed resolveName in https://github.com/Microsoft/TypeScript/pull/16040

closing in favor of https://github.com/Microsoft/TypeScript/pull/16040


Tsformer pretrain question

In the file tsformer_runner.py, it uses method "test" to do the test while training, however, I found that it only use the last batch of the test_dataloader. Is there something wrong with the for loop? I'm I wrong?
`    @torch.no_grad()
@master_only
def test(self):
"""Evaluate the model.
    Args:
        train_epoch (int, optional): current epoch if in training process.
    """

    for _, data in enumerate(self.test_data_loader):
        forward_return = self.forward(data=data, epoch=None, iter_num=None, train=False)
    # re-scale data
    prediction_rescaled = SCALER_REGISTRY.get(self.scaler["func"])(forward_return[0], **self.scaler["args"])
    real_value_rescaled = SCALER_REGISTRY.get(self.scaler["func"])(forward_return[1], **self.scaler["args"])
    # metrics
    for metric_name, metric_func in self.metrics.items():
        metric_item = metric_func(prediction_rescaled, real_value_rescaled, null_val=self.null_val)
        self.update_epoch_meter("test_"+metric_name, metric_item.item())`

Thanks for your question.
I have checked and this is a bug...
But this doesn't affect the final result because this metric is not used for anything.
Thanks again for reporting this bug, I'll fix it right away!

Thanks for your reply, so the right test method is the test method in the file "base_tsf_runner.py",`  def test(self):
"""Evaluate the model.
    Args:
        train_epoch (int, optional): current epoch if in training process.
    """

    # test loop
    prediction = []
    real_value = []
    for _, data in enumerate(self.test_data_loader):
        forward_return = self.forward(data, epoch=None, iter_num=None, train=False)
        prediction.append(forward_return[0])        # preds = forward_return[0]
        real_value.append(forward_return[1])        # testy = forward_return[1]
    prediction = torch.cat(prediction, dim=0)
    real_value = torch.cat(real_value, dim=0)
    # re-scale data
    prediction = SCALER_REGISTRY.get(self.scaler["func"])(
        prediction, **self.scaler["args"])
    real_value = SCALER_REGISTRY.get(self.scaler["func"])(
        real_value, **self.scaler["args"])
    # summarize the results.
    # test performance of different horizon
    for i in self.evaluation_horizons:
        # For horizon i, only calculate the metrics **at that time** slice here.
        pred = prediction[:, i, :]
        real = real_value[:, i, :]
        # metrics
        metric_results = {}
        for metric_name, metric_func in self.metrics.items():
            metric_item = self.metric_forward(metric_func, [pred, real])
            metric_results[metric_name] = metric_item.item()
        log = "Evaluate best model on test data for horizon " + \
            "{:d}, Test MAE: {:.4f}, Test RMSE: {:.4f}, Test MAPE: {:.4f}"
        log = log.format(
            i+1, metric_results["MAE"], metric_results["RMSE"], metric_results["MAPE"])
        self.logger.info(log)
    # test performance overall
    for metric_name, metric_func in self.metrics.items():
        metric_item = self.metric_forward(metric_func, [prediction, real_value])
        self.update_epoch_meter("test_"+metric_name, metric_item.item())
        metric_results[metric_name] = metric_item.item()

`
I'm I right?

No, the test function in the base_tsf_runner is designed for the Time Series Forecasting (TSF) problem, which is not compatible with the reconstruction task in the pre-training stage.
Actually, I think you can fix this by adding a Tab  for lines 84~90 like:
    @torch.no_grad()
    @master_only
    def test(self):
        """Evaluate the model.

        Args:
            train_epoch (int, optional): current epoch if in training process.
        """

        for _, data in enumerate(self.test_data_loader):
            forward_return = self.forward(data=data, epoch=None, iter_num=None, train=False)
            # re-scale data
            prediction_rescaled = SCALER_REGISTRY.get(self.scaler["func"])(forward_return[0], **self.scaler["args"])
            real_value_rescaled = SCALER_REGISTRY.get(self.scaler["func"])(forward_return[1], **self.scaler["args"])
            # metrics
            for metric_name, metric_func in self.metrics.items():
                metric_item = metric_func(prediction_rescaled, real_value_rescaled, null_val=self.null_val)
                self.update_epoch_meter("test_"+metric_name, metric_item.item())

Thanks for your answering, I got your idea. : )

This bug is now fixed. Thanks again for your report!


Parsing email list broken with python3

Imap-CLI use ast module to parse imap result and this method does not work with python3.

Peut-etre ici ?

Exactly :)
I think we need to write a real parser here

I can't fully test this solution right now. If you can, please take a look at PR #19

Solved \o/ 🎉


update and unify dependencies

This PR does a maintenance on the dependencies. Here is the full list of the things done:

centralize the immutables version and updates to latest
centralize the swagger-jersey2-jaxrs and update to latest
update all test frameworks to the latest (except mockito which is updated to the latest 3.x line)
organization of the dependencies in all projects in groups - stargate, C, 3rd party, test
removing the javax.validation-api and javax.annotation-api from the persistence-api as this makes no sense at all
javatuples version centralized, and defined correct scope for the projects that depend on it
setting the explicit maven compiler java version to 1.8
remove all <scope>compile</scope> from the poms, as this is default
updates dropwizard to latest version 2.0.27

Note that of course there is bunch of other dependencies to be updated. Here is my overview on the most important ones:

cassandra-all from 3.11.9 to 3.11.11
DS OSS java-driver-core from 4.9.0 to 4.13.0

Tasks:

[ ] Rebase before merge

@tatu-at-datastax @jeffreyscarpenter FYI: I am about to merge this and this could break your v2 branch.. Not sure how much you depend on the main pom..

@ivansenic thank you fro heads up. I hope it merges fine; our dependencies should use parent pom but there's just one new module at this point.