Reconsider editor.codeActionsOnSave change

Testing #194077
It seems that the editor.codeActionsOnSave setting has changed its value type. There are a couple of issues with this

no automatic migration happened, e.g. all existing usages are now flagged as errors (see below). This isn't user-friendly and if we stick with this we should make sure to use our auto-migration logic. Check IConfigurationMigrationRegistry for this
I fail to understand the added value of this, the new values are as expressive as the old ones
For editor.codeActionsOnSave there is no IntelliSense of the value set

intellisense issue related to https://github.com/microsoft/vscode/issues/161284

There is an unfortunate regression... It looks like the migration code that I have recommended isn't working great. I revert your changes and we need a path forward: either we get a fix for the migration or the setting is defined as boolean or string enum

resolved in https://github.com/microsoft/vscode/issues/194437. Migration to happen in next milestone with https://github.com/microsoft/vscode/issues/194427 👍


Update uri.cpp

Fix for uri::swap method

Thanks for the PR. But what does this fix? Can you add a test?

Without proposed changes uri::swap method worked in incorrect way: this method swapped uri_ and uri_view_, but uri_parts_ members were not swapped, this method used other.uri_parts_ for both uri objects. This method overwrote this->uri_parts_ by other.uri_parts_ and then wrote to this->uri_parts_ to other.uri_parts_,  so both uris had the same other.uri_parts_ value.

Sorry it has taken me a while to respond. Your changes look correct, but I'd still like to see a unit test before merging this PR.

@TheAquaMan I applied this fix in PR #99, including a test. Can you confirm if that works for you?

Fix was applied on master (see PR #99)


Any option to set the slider to InProgress state?

Scenario explained:

User slides the slide to the right
Now the slider turns into a progress dialog
Slider shrinks and changes icon to progress icon
If operation succeed, icon changes to tick
If operation fails, icon changes to cross

Wrong repo


WIP cli+api: consistent and intuitive CLI usage

Fixes https://github.com/textileio/docs/issues/89

When this is out of WIP, it would be awesome for downstream clients if the changelog included all the new REST API endpoints 🙏. Especially because all the nice aliases are slightly harder to groc in the source :)

When this is out of WIP, it would be awesome for downstream clients if the changelog included all the new REST API endpoints 🙏

No changes to the REST API in this besides removal of default thread, which shouldn't require any client updates, as no one is probably using it.


Thanks for your reply.

Hi,
You may use tools/test.py. And you can find a detailed tutorial here:https://github.com/open-mmlab/mmclassification/blob/master/docs/getting_started.md . Pls let me know if you have any further questions.

Thanks for your answer and it works~


Following the DF screen cannot be disabled.

On 0.19.1, when built for mac, the F key does not toggle whether the DF screen is followed, although the Help overlay indicates it should.

Pressing F only enables follow. Pressing any of wasd disables it.
On Mon 7 May, 2018, 5:02 AM Alex<EMAIL_ADDRESS>wrote:

On 0.19.1, when built for mac, the F key does not toggle whether the DF
screen is followed, although the Help overlay indicates it should.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/JapaMala/armok-vision/issues/66, or mute the thread
https://github.com/notifications/unsubscribe-auth/AARm3cXrsuFWY-2BIOJxnQS7q5uGWKmoks5tv4gjgaJpZM4T0PhI
.

Ah, it just launches in follow mode. Could it be made to toggle? For instance if one wants to drop into FPS mode directly where the DF screen is.
Also, since AV launches in follow mode, could you add a log message (similar to "Changing to First Person") when moving in and out of follow mode?

Sure, that's reasonably.

Also is it intended that the camera doesn't unfollow when switching to FPS mode & walking around, but only unfollows with wasd in god mode?

That's a bug.
It's great having detailed feedback like this. I'm often on my own with this kind of stuff.

Hah well there's more where that came from.
Also in Assets/Scripts/MapGen/GameMap.cs, near line 1542, is there any reason for the posZ != dfPos.z + 1 test? Why not just constitutively write to it and avoid the branch prediction failure?

Note that hitting F in FPS mode (i.e. enabling follow) moves the section of the map rendered to where the DF screen is showing, without moving the FPS camera. This often means that you immediately fall to -infinity.
One of two things should happen instead:

Either following the DF Screen should be disabled in FPS mode, or
The FPS camera should be moved to where the DF Screen is, but not be locked to it (i.e. it should be a one-shot move of the rendered area & FPS camera to where the DF screen is).

The second one is cooler.


Add a Gitter chat badge to README.md

mltsp/mltsp now has a Chat Room on Gitter
@stefanv has just created a chat room. You can visit it here: https://gitter.im/mltsp/mltsp.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

:+1:

Sneaky, gitter-bot!  But looks ok to me :)

One step closer to https://en.wikipedia.org/wiki/Grey_goo.


Image uploads as all black

Environment:

Mac
.NET Core 3.1

var imagekit = new Imagekit.Imagekit(publicKey, privateKey, urlEndpoint);
imagekit.options.Add("folder", "/test/");
imagekit.options.Add("fileName", "testios");
Uri apiEndpoint = new Uri(Imagekit.Util.Utils.GetUploadApi());
var data = imagekit.getUploadData();
var filePath = "/Users/Christi/Library/Photos/pic1.jpg";
var response = Imagekit.Util.Utils.PostUpload(apiEndpoint, data, filePath, privateKey);
var responseContent = await response.Content.ReadAsStringAsync();

The status code of response is a 200 but the uploaded image is entirely black.

Please share the original image which you are trying to upload. Ping us on support chat at Imagekit.io for quick response.

I'm using Imagekit.Util.Utils.PostUpload which uploads as base64.
I was uploading one of the default images from the iPhone simulator which is not black, but when I dig down into the temp file location it is saved as all black, so I guess it's an issue somewhere else. Closing this.


Include all post-WW2 aircraft in encyclopedia

Populate the data in the encyclopedia package with every postwar aircraft in DCS World.

Should be complete as of #149


Image Tag Requirement

My apologies if I've missed this in the documentation, but would it be worthwhile to mention that an image tag is necessary when specifying the codePackage's container image or the deployment will fail? I tried deploying without one and got the error:
{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "BadRequestWithReason",
"message": "Request is invalid. Reason 'helloworldapp.WebFrontEnd.WebFrontEnd': Image tag not specified..",
"details": []
}
]
}
}
Adding an image tag, even :latest, fixes the deployment.

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

ID: 2a11074a-9b44-cb3c-77a9-fba646a75d3b
Version Independent ID: c3fd5f8e-6043-6482-4153-c6d044ce10bc
Content: Tutorial- Deploy an app to Azure Service Fabric Mesh
Content Source: articles/service-fabric-mesh/service-fabric-mesh-tutorial-template-deploy-app.md
Service: service-fabric-mesh
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@damienestewart I tried to deploy a mesh app using that template.
Looks like image tag is mandatory for windows containers.
I will check again and post the updates.

#reassign @erikadoyle

Service Fabric Mesh is deprecated.
#please-close


improve CLI speed

Is your feature request related to a problem? Please describe.
every time I execute a command (e.g: amplify update api), it takes at least 6seconds of startup time before the command executes, same thing happens when you call amplify-cli via nodejs.
Describe the solution you'd like
Improve its CLI speed to be below 1 or 2s, I'm not an expert in the field but a few ideas would be to remove dependencies or create a single js file executable using ncc. or even better create binaries. I know it is a lot of work though but could be cool to have that!

Are you using the npm global installation?
If so, have you tried installing using the new smaller packaged available via curl? It's at least 3x faster from my experience.
https://docs.amplify.aws/cli/start/install
That being said, it would also be nice to have better performance in general.

Are you using the npm global installation?
If so, have you tried installing using the new smaller packaged available via curl? It's at least 3x faster from my experience.
https://docs.amplify.aws/cli/start/install
That being said, it would also be nice to have better performance in general.

Nice, I reinstalled via Curl, and indeed now it's faster! (takes 2 to 3 seconds to start) thanks 👍

Nice, I reinstalled via Curl, and indeed now it's faster! (takes 2 to 3 seconds to start) thanks 👍

@anisg thanks for reporting this issue, as @dabit3 pointed out we have a package CLI version which already has some performance gains, but as we going forward these pain points are considered and continuously improved, so closing it as a 'non-issue' for now.

@anisg thanks for reporting this issue, as @dabit3 pointed out we have a package CLI version which already has some performance gains, but as we going forward these pain points are considered and continuously improved, so closing it as a 'non-issue' for now.


SRT Streaming Issues with GStreamer

Which version are you using?
v1.8.4
Which operating system are you using?

[ ] Linux amd64 standard
[ ] Linux amd64 Docker
[ ] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[x] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
I want to receive and view the camera stream sent to the mediamtx server via RTMP using GStreamer with SRT. The readme only provides code related to RTSP for GStreamer, and I would like to know the command to pull the stream from the mediamtx server using SRT.
Describe how to replicate the issue

I am running the Linux binary for armv6 on Ubuntu 20.04 and using a Jetson Orin NX board. I am using GStreamer 1.16.3 for streaming.
The process of sending the camera stream to the mediamtx server via RTMP and then receiving and viewing it using GStreamer via RTSP works fine with the following steps:

RTMP -> mediamtx
gst-launch-1.0 -v -e v4l2src device=/dev/video0 ! 'video/x-raw, width=640, height=480, framerate=30/1, format=YUY2' ! nvvidconv ! 'video/x-raw(memory:NVMM), format=(string)NV12' ! nvv4l2h264enc bitrate=5000000 ! h264parse ! flvmux ! rtmpsink location='rtmp://localhost:1935/mystream live=1'

mediamtx -> RTSP
gst-launch-1.0 rtspsrc location=rtsp://<board_IP_address>:8554/mystream drop-on-latency=true use-pipeline-clock=true do-retransmission=false latency=0 ! rtph264depay ! avdec_h264 ! autovideosink sync=true

However, when I try to receive and view the stream using GStreamer via SRT, I keep encountering the following error:
$ gst-launch-1.0 -v -e srtsrc uri="srt://<board_IP_address>:8890?streamid=read:mystream" ! queue ! h264parse ! avdec_h264 ! autovideosink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
11:05:37 AM.549573/SRT:RcvQ:workerE:SRT.c: processAsyncConnectRequest: REJECT reported from HS processing, not processing further.
11:05:37 AM.549614/SRT:RcvQ:workerE:SRT.c: RendezvousQueue: processAsyncConnectRequest FAILED. Setting TTL as EXPIRED.
11:05:37 AM.806282/SRT:RcvQ:workerE:SRT.c: processAsyncConnectRequest: REJECT reported from HS processing, not processing further.
11:05:37 AM.806352/SRT:RcvQ:workerE:SRT.c: RendezvousQueue: processAsyncConnectRequest FAILED. Setting TTL as EXPIRED.
^Chandling interrupt.
Interrupt: Stopping pipeline ...
EOS on shutdown enabled -- Forcing EOS on the pipeline
Waiting for EOS...
Got EOS from element "pipeline0".
EOS received - stopping pipeline...
Execution ended after 0:00:01.159024029
Setting pipeline to NULL ...
Freeing pipeline ...
The stream is successfully received with VLC and ffmpeg, but not with GStreamer. Below are the successful VLC and ffmpeg commands, and I would like to know how to receive the stream with GStreamer.

VLC
srt://<board_IP_address>:8890?streamid=read:mystream

ffmpeg
ffplay srt://<board_IP_address>:8890?streamid=read:mystream

Can you help me with the command to receive the stream using GStreamer?
Did you attach the server logs?

2024/07/25 16:03:38 INF MediaMTX v1.8.4
2024/07/25 16:03:38 INF configuration loaded from /home/k/Downloads/mediamtx_v1.8.4_linux_armv6/mediamtx.yml
2024/07/25 16:03:38 INF [RTSP] listener opened on :8554 (TCP), :8000 (UDP/RTP), :8001 (UDP/RTCP)
2024/07/25 16:03:38 INF [RTMP] listener opened on :1935
2024/07/25 16:03:38 INF [HLS] listener opened on :8888
2024/07/25 16:03:38 INF [WebRTC] listener opened on :8889 (HTTP), :8189 (ICE/UDP)
2024/07/25 16:03:38 INF [SRT] listener opened on :8890 (UDP)
2024/07/25 16:03:43 INF [RTMP] [conn <IP_ADDRESS>:48590] opened
2024/07/25 16:03:43 INF [RTMP] [conn <IP_ADDRESS>:48590] is publishing to path 'mystream', 1 track (H264)
Did you attach a network dump?

no

I'm having the same issue but sending via SRT using gstreamer (srtclientsink or srtsink)
gst-launch-1.0 videotestsrc is-live=true ! videoconvert ! x264enc bitrate=500 ! h264parse ! mpegtsmux ! srtclientsink uri=srt://XXX.XXX.XXX.XXX:8890
09:52:02.066637/SRT:RcvQ:workerE:SRT.c: processAsyncConnectRequest: REJECT reported from HS processing, not processing further.
09:52:02.066793/SRT:RcvQ:workerE:SRT.c: RendezvousQueue: processAsyncConnectRequest FAILED. Setting TTL as EXPIRED.

Answer was provided by @moschopsuk . Make sure that you are using a recent GStreamer version, or alternatively compile it from source.


Centos 8 Stream

Any plans to upgrade this to Stream in the future?

No; I've moved my own infrastructure that was using CentOS 8 for prod/testing over to Rocky Linux.

Gotchya....thanks


Add keti alias

kcexec and kexec aliases have the problem that they cant autocomplete the pod name because they are hidden inside a function. In addition in case the pod contains multiple containers, its impressible to specify the container.

Thank you for the PR @konstantinos-angelo ! That's awesome.
@patmessina what do you think of keti vs keit or some other alias alternative?

keit seems more appropriate to me.

Thank you @konstantinos-angelo for your contribution! We appreciate it :)
Please feel welcome to add any other functionality that you wish this plugin had

Second. Appreciate it!


[DPE-2983] HA network cut

NOTE to Reviewers:
Plese take a look at "Usage Instructions" in this comment before reviewing this PR
Shotrly:
When reviewing changs, in the Files (left-hand side) tab

close the libs tab (nothig to review there)
close the tests/integration/opensearch-operator tab (nothing to review here)

Furthemore, you may find review by commit handy.

@phvalguima Evaluating your comment

Pretty big PR

kaboca@pegasus:~/repos/duplicated/opensearch-dashboards-operator$ git log --oneline -10
6762835 (HEAD -> DPE-2983_ha_network_cut, origin/DPE-2983_ha_network_cut) TLS operator v136
9cf625d HA tests
8a5d2fe Removing unnecessary unittest
e213a06 Certificate refresh on IP change (+ small adjustments)
946e85e Generic tests cleanup from local Opensearch charm copy
519e6cf Removing local copy of Opensearch
2450340 Updating libs
ef6cbbc (origin/main, origin/HEAD, main) Merge pull request #19 from canonical/4033_tls_workflow_cleanup
6ea9bb7 (origin/4033_tls_workflow_cleanup) fixup! Changes on PR request
6a228ab Changes on PR request
kaboca@pegasus:~/repos/duplicated/opensearch-dashboards-operator$ git log ef6cbbc..519e6cf --numstat --pretty="%H" | awk 'NF==3 {added+=$1; deleted+=$2} NF==1 {commit++} END {printf("total lines added: +%d\ntotal lines deleted: -%d\ntotal commits: %d\n", added, deleted, commit)}'
total lines added: +154
total lines deleted: -26017
total commits: 2

While I agree that the PR "seems" big, on a closer look what you find is:

25 000+ lines were removed -- no reveiw needed

local copy of the Opensearch charm is not needed in test space anymore, since https://github.com/canonical/opensearch-operator/pull/216 got merged
easy to ignore in review space by closing the opensearch-operator file pull-down list, since no review needed on this
added in isolation as a separate commit

outdated charm libs got updated -- no reveiw needed

added in isolation as a separate commit (two actually, as I consider TLS libs v13 "experimental" :-) )
easy to ignore by closing the libs/charms file pull-down listt, as o review is needed on this
note: the charm has no libs on it's own so far

the core add-on in this PR is the HA testing, which indeed is a big, very repetititve module (as I guess it's normal for such test modules)

Overall, defending my case: I don't think the PR is really "big" once taking a closer look.
While I DO agree that I should have made all these details clear for reviewers in the Description. I'll do that next time.
But the level of "complexity" involved in this PR I think is kinda normal given the weight of pipeline executions, that additional gradening (libs, or removing garbage) is handiest to be added alongside normal tasks...

@phvalguima I don't think blocking using a test helper or not may be necessary :-)
As explained above: I would not like to use the Opensearch wait_until() method/module.
I used it before on Opensearch, and I found it particularly difficult to use when debugging a particular issue.
Instead of status output, I have added particularly strict checks on the PR with blocking and parsing status output making sure that expected behavior is carried out -- while aiming to keep it all simple. I payed special attantion to the unknown/lost status that you've highlighted earlier.
Given the already existing complexity, the Juju bug discovered (in particularly time-consuming ways -- since only appeared on the pipeline) I would like to avoid introducing any additional layer of complexity whenever avoidable.

@Mehdi-Bendriss

Could you remove references to ZooKeeper from the helpers?

Primarily if any garbage left here is to be cleaned up in here: https://warthogs.atlassian.net/browse/DPE-3954
I would rather suggest to concentrate on the HA network tests making sure that further develoment (cleanup) can think of it as solid. Typically when requesting reveiws -- that casually become possible earlier than 1.5h pipelines verification each time.
Given that we can assume HA tests being solid, i.e reveiws CAN be requested while HA tests sitll running -- speeding up feedback cycles of 80+ comments (as on this PR).
This PR is partcularly heavy, and speidng 4-5 days on hunting down the related bug https://bugs.launchpad.net/juju/+bug/2064876 (only appearing on heavy pipelines) doubled the already significant weight. I see little value in helper function names or docstring cosmetics added on the top of the above -- especially from a moral perspective.


Clean install fails to start replicas

Hi,
problem
new 3 node cluster starts primary which seems fine and can query with psql - but no replica pods get created.
environment

a bare metal cluster (ubuntu hosts) running kubernetes v1.26
cluster is in namespace ext
controller is installed in cnpg-system using the helm chart
cluster doesn't have a csi / automated pv provisioning so pvs are created manually
only the pv from the first host gets claimed

cluster configuration
  apiVersion: postgresql.cnpg.io/v1
  kind: Cluster
  metadata:
    name: pg
  spec:
    instances: 3
    imageName: ghcr.io/cloudnative-pg/postgresql:15.3

    # Persistent storage configuration
    storage:
      size: 50Gi
      pvcTemplate:
        accessModes:
          - ReadWriteOnce
        resources:
          requests:
            storage: 50Gi
        storageClassName: local-storage
        volumeMode: Filesystem

    affinity:
      enablePodAntiAffinity: true
      topologyKey: kubernetes.io/hostname
      podAntiAffinityType: preferred

when cluster comes up we have the following
NAME                       READY   STATUS      RESTARTS   AGE
pod/pg-1                   1/1     Running     0          31m
pod/pg-1-initdb--1-86nhj   0/1     Completed   0          137m
pod/ubuntu                 1/1     Running     0          14h

NAME            TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
service/pg-r    ClusterIP   <IP_ADDRESS>    <none>        5432/TCP   137m
service/pg-ro   ClusterIP   <IP_ADDRESS>    <none>        5432/TCP   137m
service/pg-rw   ClusterIP   <IP_ADDRESS>   <none>        5432/TCP   137m

NAME                    COMPLETIONS   DURATION   AGE
job.batch/pg-1-initdb   1/1           41s        137m

controller logs show
{"level":"info","ts":"2023-06-24T11:29:51Z","msg":"Cannot extract Pod status","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg","namespace":"ext"},"namespace":"ext","name":"pg","reconcileID":"fc802273-9673-4094-89a2-a2868762260c","uuid":"6e026de8-1282-11ee-bd18-8e70f882700f","name":"pg-1","error":"Get \"http://<IP_ADDRESS>:8000/pg/status\": dial tcp <IP_ADDRESS>:8000: i/o timeout"}
{"level":"info","ts":"2023-06-24T11:29:51Z","msg":"Failed to extract instance status from ready instances. Attempting to requeue...","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg","namespace":"ext"},"namespace":"ext","name":"pg","reconcileID":"fc802273-9673-4094-89a2-a2868762260c","uuid":"6e026de8-1282-11ee-bd18-8e70f882700f"}
{"level":"info","ts":"2023-06-24T11:30:03Z","msg":"Cannot extract Pod status","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg","namespace":"ext"},"namespace":"ext","name":"pg","reconcileID":"7ca102e3-14f8-4daf-8e29-47301e855bc2","uuid":"75354488-1282-11ee-bd18-8e70f882700f","name":"pg-1","error":"Get \"http://<IP_ADDRESS>:8000/pg/status\": dial tcp <IP_ADDRESS>:8000: i/o timeout"}
{"level":"info","ts":"2023-06-24T11:30:03Z","msg":"Failed to extract instance status from ready instances. Attempting to requeue...","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg","namespace":"ext"},"namespace":"ext","name":"pg","reconcileID":"7ca102e3-14f8-4daf-8e29-47301e855bc2","uuid":"75354488-1282-11ee-bd18-8e70f882700f"}
{"level":"info","ts":"2023-06-24T11:30:15Z","msg":"Cannot extract Pod status","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg","namespace":"ext"},"namespace":"ext","name":"pg","reconcileID":"0215cbf1-f55c-4d44-bd09-9893055394ef","uuid":"7c61f7d9-1282-11ee-bd18-8e70f882700f","name":"pg-1","error":"Get \"http://<IP_ADDRESS>:8000/pg/status\": dial tcp <IP_ADDRESS>:8000: i/o timeout"}
{"level":"info","ts":"2023-06-24T11:30:15Z","msg":"Failed to extract instance status from ready instances. Attempting to requeue...","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg","namespace":"ext"},"namespace":"ext","name":"pg","reconcileID":"0215cbf1-f55c-4d44-bd09-9893055394ef","uuid":"7c61f7d9-1282-11ee-bd18-8e70f882700f"}

investigation
have created a bare pod in the cnpg-system namespace to test the call being made using curl
curl 'http://<IP_ADDRESS>:8000/pg/status'
{"currentLsn":"0/6000000","systemID":"7248177365388468245","isPrimary":true,"replayPaused":false,"pendingRestart":false,"pendingRestartForDecrease":false,"isWalReceiverActive":false,"node":"","pod":{"metadata":{"name":"pg-1","creationTimestamp":null},"spec":{"containers":null},"status":{}},"isPgRewindRunning":false,"totalInstanceSize":"29 MB","mightBeUnavailable":false,"lastArchivedWAL":"000000010000000000000005","lastArchivedWALTime":"2023-06-24T11:05:23.61393Z","lastFailedWALTime":"-infinity","isArchivingWAL":true,"currentWAL":"000000010000000000000005","timeLineID":1,"isPodReady":false,"executableHash":"76ceae159df15258568e3c48687e90c35aecda372e23e4ab1ef2a7eb6a2fe950","isInstanceManagerUpgrading":false,"instanceManagerVersion":"1.20.1","instanceArch":"amd64"}

Looks like maybe the controller can't get past not getting the status from the first pod? and is stuck retrying every 10s or so, but as far as i can tell the call it is trying to use should succeed.
Any pointers on where to look next?
Thanks

Looks like a networking issue, can you try the curl from a pod in the same cnpg-system namespace, but making sure it's scheduled on the same node?

Thanks @phisco, you're right - we seem to have a pod network issue and have some connectivity issues with one node.
The cluster controller had scheduled itself onto the one with a problem.
I think I could get around this by putting a taint on the node for now to stop things scheduling onto it - but doing a bit of digging first to see if I can work out what is wrong with it.


Android. Error: Text strings must be rendered within a  component

Hi
I am having problems with Chart Guage on android.
I run this code and it works fine in web browser.
import * as React from 'react';
import {Chart} from 'react-google-charts';

export default class GaugeChartController extends React.Component {

  render() {
    return (
      <Chart
        width={250}
        height={120}
        chartType="Gauge"
        loader={
Loading Chart
}
        data={[
          ['Label', "value"],
          ['Oil', 35],
          ['Water', 36],
        ]}
        options={{
          redFrom: 110,
          redTo: 130,
          yellowFrom: 100,
          yellowTo: 110,
          minorTicks: 5,
          max: 130,
          min: 30
        }}
      />
    );
  }
}

But when I try it on android, I get this error
Error: Text strings must be rendered within a <Text> component.

This error is located at:
    in div (at LoRuouController.tsx:18)
    in ContextProvider (created by Chart)
    in Chart (at LoRuouController.tsx:14)
    in LoRuouController (at SceneView.tsx:130)
    in StaticContainer
    in StaticContainer (at SceneView.tsx:123)
    in EnsureSingleNavigator (at SceneView.tsx:122)
    in SceneView (at useDescriptors.tsx:181)
    in RCTView (at View.js:34)
    in View (at CardContainer.tsx:245)
    in RCTView (at View.js:34)
    in View (at CardContainer.tsx:244)
    in RCTView (at View.js:34)
    in View (at CardSheet.tsx:33)
    in ForwardRef(CardSheet) (at Card.tsx:573)
    in RCTView (at View.js:34)
    in View (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:555)
    in PanGestureHandler (at GestureHandlerNative.tsx:13)
    in PanGestureHandler (at Card.tsx:549)
    in RCTView (at View.js:34)
    in View (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:544)
    in RCTView (at View.js:34)
    in View (at Card.tsx:538)
    in Card (at CardContainer.tsx:206)
    in CardContainer (at CardStack.tsx:619)
    in RNSScreen (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at src/index.native.tsx:147)
    in Screen (at Screens.tsx:74)
    in MaybeScreen (at CardStack.tsx:612)
    in RNSScreenContainer (at src/index.native.tsx:186)
    in ScreenContainer (at Screens.tsx:50)
    in MaybeScreenContainer (at CardStack.tsx:494)
    in CardStack (at StackView.tsx:462)
    in KeyboardManager (at StackView.tsx:458)
    in SafeAreaProviderCompat (at StackView.tsx:455)
    in RCTView (at View.js:34)
    in View (at GestureHandlerRootView.android.tsx:21)
    in GestureHandlerRootView (at StackView.tsx:454)
    in StackView (at createStackNavigator.tsx:87)
    in StackNavigator (at BottomTabNavigator.tsx:124)
    in LoRuouNavigator (at SceneView.tsx:130)
    in StaticContainer
    in StaticContainer (at SceneView.tsx:123)
    in EnsureSingleNavigator (at SceneView.tsx:122)
    in SceneView (at useDescriptors.tsx:181)
    in RCTView (at View.js:34)
    in View (at CardContainer.tsx:245)
    in RCTView (at View.js:34)
    in View (at CardContainer.tsx:244)
    in RCTView (at View.js:34)
    in View (at CardSheet.tsx:33)
    in ForwardRef(CardSheet) (at Card.tsx:573)
    in RCTView (at View.js:34)
    in View (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:555)
    in PanGestureHandler (at GestureHandlerNative.tsx:13)
    in PanGestureHandler (at Card.tsx:549)
    in RCTView (at View.js:34)
    in View (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:544)
    in RCTView (at View.js:34)
    in View (at Card.tsx:538)
    in Card (at CardContainer.tsx:206)
    in CardContainer (at CardStack.tsx:619)
    in RNSScreen (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at src/index.native.tsx:147)
    in Screen (at Screens.tsx:74)
    in MaybeScreen (at CardStack.tsx:612)
    in RNSScreenContainer (at src/index.native.tsx:186)
    in ScreenContainer (at Screens.tsx:50)
    in MaybeScreenContainer (at CardStack.tsx:494)
    in CardStack (at StackView.tsx:462)
    in KeyboardManager (at StackView.tsx:458)
    in SafeAreaProviderCompat (at StackView.tsx:455)
    in RCTView (at View.js:34)
    in View (at GestureHandlerRootView.android.tsx:21)
    in GestureHandlerRootView (at StackView.tsx:454)
    in StackView (at createStackNavigator.tsx:87)
    in StackNavigator (at BottomTabNavigator.tsx:63)
    in TabOneNavigator (at SceneView.tsx:130)
    in StaticContainer
    in StaticContainer (at SceneView.tsx:123)
    in EnsureSingleNavigator (at SceneView.tsx:122)
    in SceneView (at useDescriptors.tsx:181)
    in RCTView (at View.js:34)
    in View (at BottomTabView.tsx:55)
    in SceneContent (at BottomTabView.tsx:172)
    in RNSScreen (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at src/index.native.tsx:147)
    in Screen (at ResourceSavingScene.tsx:28)
    in ResourceSavingScene (at BottomTabView.tsx:166)
    in RNSScreenContainer (at src/index.native.tsx:186)
    in ScreenContainer (at BottomTabView.tsx:146)
    in RCTView (at View.js:34)
    in View (at BottomTabView.tsx:145)
    in SafeAreaProviderCompat (at BottomTabView.tsx:144)
    in BottomTabView (at createBottomTabNavigator.tsx:45)
    in BottomTabNavigator (at BottomTabNavigator.tsx:29)
    in BottomTabNavigator (at SceneView.tsx:130)
    in StaticContainer
    in StaticContainer (at SceneView.tsx:123)
    in EnsureSingleNavigator (at SceneView.tsx:122)
    in SceneView (at useDescriptors.tsx:181)
    in RCTView (at View.js:34)
    in View (at CardContainer.tsx:245)
    in RCTView (at View.js:34)
    in View (at CardContainer.tsx:244)
    in RCTView (at View.js:34)
    in View (at CardSheet.tsx:33)
    in ForwardRef(CardSheet) (at Card.tsx:573)
    in RCTView (at View.js:34)
    in View (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:555)
    in PanGestureHandler (at GestureHandlerNative.tsx:13)
    in PanGestureHandler (at Card.tsx:549)
    in RCTView (at View.js:34)
    in View (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at Card.tsx:544)
    in RCTView (at View.js:34)
    in View (at Card.tsx:538)
    in Card (at CardContainer.tsx:206)
    in CardContainer (at CardStack.tsx:619)
    in RNSScreen (at createAnimatedComponent.js:165)
    in AnimatedComponent (at createAnimatedComponent.js:215)
    in ForwardRef(AnimatedComponentWrapper) (at src/index.native.tsx:147)
    in Screen (at Screens.tsx:74)
    in MaybeScreen (at CardStack.tsx:612)
    in RNSScreenContainer (at src/index.native.tsx:186)
    in ScreenContainer (at Screens.tsx:50)
    in MaybeScreenContainer (at CardStack.tsx:494)
    in CardStack (at StackView.tsx:462)
    in KeyboardManager (at StackView.tsx:458)
    in SafeAreaProviderCompat (at StackView.tsx:455)
    in GestureHandlerRootView (at GestureHandlerRootView.android.tsx:26)
    in GestureHandlerRootView (at StackView.tsx:454)
    in StackView (at createStackNavigator.tsx:87)
    in StackNavigator (at navigation/index.tsx:34)
    in RootNavigator (at navigation/index.tsx:23)
    in EnsureSingleNavigator (at BaseNavigationContainer.tsx:411)
    in ForwardRef(BaseNavigationContainer) (at NavigationContainer.tsx:91)
    in ThemeProvider (at NavigationContainer.tsx:90)
    in ForwardRef(NavigationContainer) (at navigation/index.tsx:20)
    in Navigation (at App.tsx:63)
    in RNCSafeAreaProvider (at SafeAreaContext.tsx:76)
    in SafeAreaProvider (at App.tsx:61)
    in SSRProvider (at NativeBaseProvider.tsx:93)
    in ToastProvider (at NativeBaseProvider.tsx:91)
    in PortalProvider (at NativeBaseProvider.tsx:90)
    in HybridProvider (at NativeBaseProvider.tsx:86)
    in RNCSafeAreaProvider (at SafeAreaContext.tsx:76)
    in SafeAreaProvider (at NativeBaseProvider.tsx:81)
    in NativeBaseConfigProviderProvider (at NativeBaseProvider.tsx:76)
    in ThemeProvider (at NativeBaseProvider.tsx:75)
    in NativeBaseProvider (at App.tsx:60)
    in App (created by ExpoRoot)
    in ExpoRoot (at renderApplication.js:45)
    in RCTView (at View.js:34)
    in View (at AppContainer.js:106)
    in RCTView (at View.js:34)
    in View (at AppContainer.js:132)
    in AppContainer (at renderApplication.js:39)
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:104:6 in reportException
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:171:19 in handleException
at node_modules/react-native/Libraries/Core/setUpErrorHandling.js:24:6 in handleError
at node_modules/expo-error-recovery/build/ErrorRecovery.fx.js:12:21 in ErrorUtils.setGlobalHandler$argument_0

Info

expo 42.0
<EMAIL_ADDRESS>node v16.13.0
react-google-charts: "^3.0.15"

Did you solve this issue?

this problem is because the library running is reactjs not react native. problem is not resolved.

react-google-charts is indeed not supposed to be used with React Native. You might want to look at other solutions.

yes i found another workaround for react native. The problem may be closed.

@xdien would you be willing to share your workaround? I'm also looking for a way to use Google Charts in react native.

@xdien would you be willing to share your workaround? I'm also looking for a way to use Google Charts in react native.

My solution is not very good. i use another library for reatjs native,

Correct, Google Charts is not meant for React Native, you will need to either render a webpage and use Google Charts inside of it or use another charting library.


Please install your Cordova CLI to version  >=4.2.0 npm install -g cordova

Hi There,
I am getting this error when trying to use your example.
I however have the latest version of Cordova installed (globally) - 6.5.0
Any way I can fix this?

Hello,
Try re-installing cordova and ionic, maybe that'll fix it
Other than that the issue is most probably related with your Cordova installation


version number in the readme

Is it possible to put the version number of the release in the readme for future versions.
Optionally, in the plugin dialogue in Paint.NET you could also put the version there.

The version number is already listed on the GitHub releases page and the DLL file properties.
I will not be putting it in the readme,
The Paint.NET diagnostic information in Settings > Diagnostics shows the version for all installed Effect and FileType plugins.
I do not plan on putting it in the plugin dialog.

I added the plugin and libwebp versions to the save UI.


libsidplayfp: 2.2.1 -> 2.2.2

Motivation for this change
Bugfix release.

songlengthdb: fix possible corrupted data

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 137216 at e53e9660 run on aarch64-linux 1

5 packages built successfully:

audacious (audaciousQt5)
gjay
libsidplayfp
qmplay2
sidplayfp


Respect gson.serializeNulls()

The API I'm working with requires null attributes to be sent and the generated type adapter never writes attributes which are null.

I'd be happy to make the change if you approve.

Sorry, this is a dupe of #67


HttpClient sends invalid extension during TLS Client Hello causing failed connection to server

Steps to Reproduce

Execute dart run example.dart on the code sample
Press Button
See error in debug output

Expected results:
Request successfully goes through
Actual results:
Error fails with error
I/flutter (29677): Error HandshakeException: Handshake error in client (OS Error:
I/flutter (29677): 	TLSV1_ALERT_DECODE_ERROR(tls_record.cc:594))

Code sample

import 'dart:io';

void main() async {
  HttpClient client = HttpClient();
  Uri url = Uri.parse("https://<IP_ADDRESS>:8888/");
  try {
    await client.postUrl(url);
  } catch (error) {
    print("Error $error");
  }
}

Logs

Error HandshakeException: Handshake error in client (OS Error:
	TLSV1_ALERT_DECODE_ERROR(tls_record.cc:594))

[✓] Flutter (Channel master, 3.1.0-0.0.pre.1099, on Arch Linux
    5.18.1-arch1-1, locale en_US.UTF-8)
    • Flutter version 3.1.0-0.0.pre.1099 at /opt/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0895130e51 (28 hours ago), 2022-06-03
      16:43:11 -0700
    • Engine revision 76a1567841
    • Dart version 2.18.0 (build 2.18.0-165.0.dev)
    • DevTools version 2.14.0

[✓] Android toolchain - develop for Android devices (Android SDK
    version 32.1.0-rc1)
    • Android SDK at /home/ford/Android/Sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.3+7)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at
    google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome
      executable.

[✓] Linux toolchain - develop for Linux desktop
    • clang version 13.0.1
    • cmake version 3.23.2
    • ninja version 1.11.0
    • pkg-config version 1.8.0

[!] Android Studio (not installed)
    • Android Studio not found; download from
      https://developer.android.com/studio/index.html
      (or visit
      https://flutter.dev/docs/get-started/install/linux#android-setu
      p for detailed instructions).

[✓] Connected device (2 available)
    • SM G975U (mobile) • R38M30FGMGE • android-arm64 • Android 12
      (API 31)
    • Linux (desktop)   • linux       • linux-x64     • Arch Linux
      5.18.1-arch1-1

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 2 categories.

Currently, my server is using axum-server with rustls in order to create a backend for my application. In doing so, I only have an ip to connect with. However, using wireshark we can decode the TLSv1.2 Client Hello packet that the flutter application is sending.

Specifically what we see here is that the HttpClient is sending a server_name extension. While this traditionally would serve to increase security, the way it is represented with the uri is a bug. <IP_ADDRESS> is clearly not a hostname, but instead an ip. Furthermore, according to the ietf rfc, an ip is a distinct thing from a hostname and "Literal IPv4 and IPv6 addresses are not permitted in 'HostName'.". As a result, when the server goes to decode the host name, it fails to get a DnsNameRef. If we reply this packet with only the hostname changed to the hext of a string, such as 'google.com', then the connection succeeds.
EDIT: Changed quote from RFC to more proper RFC as well as simplifying code. Thanks simolus3!

@Programatic
Looking at the error TLSV1_ALERT_DECODE_ERROR, it could be related to your server using the latest TLSV version which Flutter may not be supporting.
Also, I suggest you to file this issue in dedicated repo : https://github.com/dart-lang/io/issues
Closing from here. If you get redirected here mentioning this could be specific to flutter itself, write in comments and I'll reopen it.


Custom path matching

When I try to build js-files, I got strings like this:
this.replaceOn({icon:'i/setting.svg'})

and sometimes like this:
this.css({'background-image': 'url('+ this.param('src') +')'})

So in the first case I will not get what I want and the second case logs an error. Of course I can use only url(...) format and ignore errors in the log, but I think, It would be better to make a custom path refexp issue. Or maybe some kind of flag to match any url ends on *.svg, *.png, etc. Not sure which is better.

You probably should not be running your javascript files through this gulp task.  Use a CSS class on the element instead, and specify the image URL inside a CSS file.


faster dictation dance

I optimized the fixes made in #902 to involve fewer keypresses, which will help when these are expensive (eg. on Linux :P). Mainly:

I removed the clobber argument to dictation_peek_left, we only ever call it with clobber=True and inserting space will already clobber the selection, so this gets rid of a space-backspace pair.

I used edit.extend_line_end in dictation_peek_right instead of edit.extend_right multiple times.

Yeah, I think I accidentally duplicated key(" ") in dictation_peek_left when I cherry-picked this from my local changes. Good catch.


Organise Stakeholder workshop with Met Office

[ ] Identify key stakeholders to invite
[ ] Choose date/time/location (perhaps better later in the year, e.g. early Dec?)
[ ] Set agenda and circulate invites

Rough stakeholder groups (per convo with Sophie):

Climate Scientists
Scientists from other domains (e.g. Health, KCL folks)
Non-technical users from Climate Orgs
Climate data standards bodies/orgs

Feedback from James:
From our end, we are certainly interested and probably a discussion in September would be wise, but it would be good beforehand to flesh out what we want to achieve with such a workshop.  Fai and I were wondering if this is about demonstrating the impact of the work from Clim-Recal or if it is about looking towards funding to build a more user focused tool? We obviously have a very diverse set of skills amongst our users from those who use very high-level information (such as key results spreadsheets, a version of which will use data from Clim-Recal on Extreme Indices) down to those who get stuck into the code, with everything in-between.

Made some holds for rooms at Turing

30 Nov, 10am-4pm (David Blackwell)
6 Dec, 10am-3pm (Margaret Hamilton)
12 Dec, 9am-4pm (Ada)
14 Dec, 9am-3pm (David Blackwell)

Working HackMD for event: https://hackmd.io/@jending12/SkCfCMJ1T


file exchange: added download all functionality

Since the Hub aids in collaborating within a pentesting team, we thought it would be great if we can download a zip of all the files uploaded within the file exchange functionality. In the end, this can be used to make sure everyone has all the raw data.
So I implemented a "download all" functionality. This is what it looks like

Makes sense and the diff looks good.
Just one thing: What do you think about preventing dead space by placing the button on the same row as the Upload button,  flushed to the right? I don't know which bootstrap class we need to assign the button to without doing some research, but maybe you do.

Also, what are the permissions of the temporary file? We should avoid leaving this data somewhere in /tmp for everyone to read. Maybe we should even consider creating a zipped stream (example)

Just one thing: What do you think about preventing dead space by placing the button on the same row as the Upload button, flushed to the right? I don't know which bootstrap class we need to assign the button to without doing some research, but maybe you do.

I also thought about this, after I submitted the PR. I think this should be comparably easy. However, BS4 changed a few things compared to BS3 and I also need to dive into the docs. Maybe I find time this evening. Maybe I can also fix the alignment of the Upload button then ^^

Done. Styling the 'browse' button is not straight forward though, and I don't care enough right now


Add c unity package

Simple Unit Testing for C: https://github.com/ThrowTheSwitch/Unity

please push to dev branch next

@waruqi Ohhh, it always failed when I run test specifying the windows platform. (:
xmake l scripts/test.lua --shallow -vD -k shared -p windows unity_test

I just finished building with the ninja, so haven't commited. And these action tests also haven't windows platform?

@waruqi Ohhh, it always failed when I run test specifying the windows platform. (:
xmake l scripts/test.lua --shallow -vD -k shared -p windows unity_test

I just finished building with the ninja, so haven't commited.

it works now on windows ci

it works now on windows ci

Yeah, yeah, but no successed on my linux

I have to try your code, I don't know why, 😢

it works now on windows ci

Yeah, yeah, but no successed on my linux

but it works on linux ci

error: @programdir/modules/package/tools/cmake.lua:89: vs not found!
stack traceback:
    [C]: in function 'error'
    [@programdir/core/base/os.lua:913]: in function 'raiselevel'
    [@programdir/core/sandbox/modules/utils.lua:149]: in function 'assert'
    [@programdir/modules/package/tools/cmake.lua:89]: in function '_get_msvc'
    [@programdir/modules/package/tools/cmake.lua:621]: in function '_get_cmake_generator_for_msvc'
    [@programdir/modules/package/tools/cmake.lua:654]: in function '_get_configs_for_generator'
    [@programdir/modules/package/tools/cmake.lua:687]: in function '_get_configs'
    [@programdir/modules/package/tools/cmake.lua:980]: in function 'install'
    [...feiwu/Project/xmake-repo/packages/u/unity_test/xmake.lua:20]: in function 'script'
    [...dir/modules/private/action/require/impl/utils/filter.lua:125]: in function 'call'
    [.../modules/private/action/require/impl/actions/install.lua:364]:

  => install unity_test v2.5.2 .. failed
error: @programdir/modules/private/async/runjobs.lua:256: .../modules/private/action/require/impl/actions/install.lua:469: install failed!
stack traceback:
    [C]: in function 'error'
    [@programdir/core/base/os.lua:913]:
    [.../modules/private/action/require/impl/actions/install.lua:469]: in function 'catch'
    [@programdir/core/sandbox/modules/try.lua:123]: in function 'try'
    [.../modules/private/action/require/impl/actions/install.lua:328]:
    [...modules/private/action/require/impl/install_packages.lua:479]: in function 'jobfunc'
    [@programdir/modules/private/async/runjobs.lua:232]:

stack traceback:
        [C]: in function 'error'
        @programdir/core/base/os.lua:913: in function 'base/os.raiselevel'
        (...tail calls...)
        @programdir/modules/private/async/runjobs.lua:256: in field 'catch'
        @programdir/core/sandbox/modules/try.lua:123: in global 'try'
        @programdir/modules/private/async/runjobs.lua:218: in upvalue 'cotask'
        @programdir/core/base/scheduler.lua:404: in function <@programdir/core/base/scheduler.lua:397>
error: execv(xmake require -f -y --build -v -D --shallow --extra={configs={shared=true}} unity_test) failed(255)

But I ran into this issue that vs not found, I used your code as well.

error: @programdir/modules/package/tools/cmake.lua:89: vs not found!
stack traceback:
    [C]: in function 'error'
    [@programdir/core/base/os.lua:913]: in function 'raiselevel'
    [@programdir/core/sandbox/modules/utils.lua:149]: in function 'assert'
    [@programdir/modules/package/tools/cmake.lua:89]: in function '_get_msvc'
    [@programdir/modules/package/tools/cmake.lua:621]: in function '_get_cmake_generator_for_msvc'
    [@programdir/modules/package/tools/cmake.lua:654]: in function '_get_configs_for_generator'
    [@programdir/modules/package/tools/cmake.lua:687]: in function '_get_configs'
    [@programdir/modules/package/tools/cmake.lua:980]: in function 'install'
    [...feiwu/Project/xmake-repo/packages/u/unity_test/xmake.lua:20]: in function 'script'
    [...dir/modules/private/action/require/impl/utils/filter.lua:125]: in function 'call'
    [.../modules/private/action/require/impl/actions/install.lua:364]:

  => install unity_test v2.5.2 .. failed
error: @programdir/modules/private/async/runjobs.lua:256: .../modules/private/action/require/impl/actions/install.lua:469: install failed!
stack traceback:
    [C]: in function 'error'
    [@programdir/core/base/os.lua:913]:
    [.../modules/private/action/require/impl/actions/install.lua:469]: in function 'catch'
    [@programdir/core/sandbox/modules/try.lua:123]: in function 'try'
    [.../modules/private/action/require/impl/actions/install.lua:328]:
    [...modules/private/action/require/impl/install_packages.lua:479]: in function 'jobfunc'
    [@programdir/modules/private/async/runjobs.lua:232]:

stack traceback:
        [C]: in function 'error'
        @programdir/core/base/os.lua:913: in function 'base/os.raiselevel'
        (...tail calls...)
        @programdir/modules/private/async/runjobs.lua:256: in field 'catch'
        @programdir/core/sandbox/modules/try.lua:123: in global 'try'
        @programdir/modules/private/async/runjobs.lua:218: in upvalue 'cotask'
        @programdir/core/base/scheduler.lua:404: in function <@programdir/core/base/scheduler.lua:397>
error: execv(xmake require -f -y --build -v -D --shallow --extra={configs={shared=true}} unity_test) failed(255)

But I ran into this issue that vs not found, I used your code as well.

vs? windows? did you install vs?

vs? windows? did you install vs?

Debian, bro!
 uname -a
Linux feiwu 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-1 (2023-07-14) x86_64 GNU/Linux

error: @programdir/modules/package/tools/cmake.lua:89: vs not found!
stack traceback:
    [C]: in function 'error'
    [@programdir/core/base/os.lua:913]: in function 'raiselevel'
    [@programdir/core/sandbox/modules/utils.lua:149]: in function 'assert'
    [@programdir/modules/package/tools/cmake.lua:89]: in function '_get_msvc'
    [@programdir/modules/package/tools/cmake.lua:621]: in function '_get_cmake_generator_for_msvc'
    [@programdir/modules/package/tools/cmake.lua:654]: in function '_get_configs_for_generator'
    [@programdir/modules/package/tools/cmake.lua:687]: in function '_get_configs'
    [@programdir/modules/package/tools/cmake.lua:980]: in function 'install'
    [...feiwu/Project/xmake-repo/packages/u/unity_test/xmake.lua:20]: in function 'script'
    [...dir/modules/private/action/require/impl/utils/filter.lua:125]: in function 'call'
    [.../modules/private/action/require/impl/actions/install.lua:364]:

  => install unity_test v2.5.2 .. failed
error: @programdir/modules/private/async/runjobs.lua:256: .../modules/private/action/require/impl/actions/install.lua:469: install failed!
stack traceback:
    [C]: in function 'error'
    [@programdir/core/base/os.lua:913]:
    [.../modules/private/action/require/impl/actions/install.lua:469]: in function 'catch'
    [@programdir/core/sandbox/modules/try.lua:123]: in function 'try'
    [.../modules/private/action/require/impl/actions/install.lua:328]:
    [...modules/private/action/require/impl/install_packages.lua:479]: in function 'jobfunc'
    [@programdir/modules/private/async/runjobs.lua:232]:

stack traceback:
        [C]: in function 'error'
        @programdir/core/base/os.lua:913: in function 'base/os.raiselevel'
        (...tail calls...)
        @programdir/modules/private/async/runjobs.lua:256: in field 'catch'
        @programdir/core/sandbox/modules/try.lua:123: in global 'try'
        @programdir/modules/private/async/runjobs.lua:218: in upvalue 'cotask'
        @programdir/core/base/scheduler.lua:404: in function <@programdir/core/base/scheduler.lua:397>
error: execv(xmake require -f -y --build -v -D --shallow --extra={configs={shared=true}} unity_test) failed(255)

But I ran into this issue that vs not found, I used your code as well.

vs? windows? did you install vs?

what's you xmake version? did you modify xmake source code?

what's your xmake version? did you modify xmake source code?

xmake --version
xmake v2.8.1+20230723, A cross-platform build utility based on Lua

no modified

 -p windows

did you pass -p windows to test.lua? it's only for windows platform.

did you pass -p windows to test.lua? it's only for windows platform.

Is it like that? But successed when I used ninja to build -p macosx. Or only -p windows is like that?

did you pass -p windows to test.lua? it's only for windows platform.

Is it like that? But successed when I used ninja to build -p macosx.

Oh I see, I thought that this is a cross platroms test before. So Only using xmake l scripts/test.lua --shallow unity_test is Ok?

? if you run test.lua on linux, you cannot pass -p windows.

Oh I see, I thought that this is a cross platroms test before. So Only using xmake l scripts/test.lua --shallow unity_test is Ok?

right, msvc has no cross-platform toolchain. you should use mingw.


Added Scala (Community) definition.

This has been here for some weeks now, anything missing to have it merged?

Thank you for your contribution @heksesang! Upon initial review, the definition looks good, with a lot of great documentation.
We are working on how to best support current and future contributions to this repo. As this poses a delay in accepting some new definitions, we want to emphasize we really appreciate your work, and we're working on how to best support community contributions in a scalable way moving forward. There are additional details in this issue: https://github.com/microsoft/vscode-dev-containers/issues/1291.

Does this mean that this PR won't be merged into this repo now?

We may restructure how we hold and publish definitions, so it may get accepted into a new/newly structured repo once we're able to sort that out in the next few weeks. We won't be ignoring or rejecting new PRs, just at the moment we're only accepting critical fixes until we can make the repo readjustments.

Thanks again for opening this!
As mentioned above, our team has been actively focused on an updated plan for community contributions and this repo moving forward, which we've now outlined in this issue: https://github.com/microsoft/vscode-dev-containers/issues/1589. This includes moving to a couple new repos for images (https://github.com/devcontainers/images) and Features (https://github.com/devcontainers/features).
We anticipate to have a similar repo and distribution process for templates/definitions. We'll keep everyone updated (likely via another issue in this repo or comment on https://github.com/microsoft/vscode-dev-containers/issues/1589) when our new templates repo is available and the process is defined.
Please let me know if you have any questions, thank you!


webpack plugin

I looked into webpack plugin development the last days, but compared to rollup it's rather complicated...

I want to support webpack 4 and 5, so the current idea is three packages:

plugin-webpack
plugin-webpack4
plugin-webpack5

So plugin-webpack simply picks the right one by checking webpack.version - which hopefully reduces version conflicts or at least reducing version-switching pains.


Use a pool of rand.Source to reduce lock contention

when creating span ids
Signed-off-by: Gary Brown<EMAIL_ADDRESS>Which problem is this PR solving?
Resolves #353 - possibly :)
Short description of the changes
Instead of using a lock around the random number generation, a pool of rand.Sources is maintained.

Running a test creating 5 million spans, using the existing and new approach, shows that generally they take the same time (8 to 9 seconds) - however on occasions the existing approach resulted in runs of 18 seconds.
Checking the mutex profiling showed far less time spent - on the pool, rather than the mutex around random number generation.
@yurishkuro If the implementation looks ok, is it worth asking the Istio team to try it out before we consider merging?

sorry, already merged - def. worth asking them to try, but overall seems like a worthy improvement.


qmplay2: rename libgme to game-music-emu

qmplay2: rename libgme to game-music-emu
error: Function called without required argument "libgme" at /home/intj/.cache/nixpkgs-review/pr-189290-2/nixpkgs/pkgs/applications/video/qmplay2/default.nix:11, did you mean "libgee", "libime" or "lib3mf"?
(use '--show-trace' to show detailed location information)

~/nixpkgs/pkgs/top-level (master) $ rg libgme
aliases.nix
720:  libgme = game-music-emu; # Added 2022-07-20

Result of nixpkgs-review pr 189319 run on x86_64-linux 1

1 package built:

qmplay2


Setting array type for a variable explicitly does not work the same way as inferred type

Hi. I was able to track down my issue to this pretty straightforward example.
// @flow

function takesAListOfStringNumberUnion(list: (string | number)[]) {}

const inferred = [123]
takesAListOfStringNumberUnion(inferred)
const explicit: number[] = [123]
takesAListOfStringNumberUnion([...explicit]) // workaround
takesAListOfStringNumberUnion(explicit) // errors

It looks like a bug in flow, because it works fine when the type is inferred, but not when it's set explicitly.
Here is a link to flow try snippet https://flow.org/try/#0PTAEAEDMBsHsHcBQjIFcB2BjALgS1uqNgIYDWApgM4CCAMrpdgPKQDK2ATrugOYByqALYAjchwCq6fOgAU0BtgBcoGYy69QAH1DohojgEoA2gF0DoAN4BfZJgKNQ3SGI7kAJqAC8oIwEYATADMJogkFDT0jCzs6vx6YpLSMk4u7gaIdugO5AAeAA7ymLhKOvEcpl4+AcGhZFR0CtGc3HEiCVIEMkYAdL25BbhF2GagIKDwsBykxBywGG614Q1RbM28Am0SHbL9hcXmYy6TlIhAA

Not a bug. Here the fix.
See https://github.com/facebook/flow/issues/6045 and other issues like this.

Well, the error is the same from my point of view: you can't call a function with some argument of incompatible type.
I agree, it could be better, of course.

@apsavin I think you're right, the error message is essentially the same, but could be improved. So shall I open another issue or just update this one? I guess the latter will be confusing.


Add option to disable ambiguous unicode characters detection

Close #24483
Close #28123
Close #23682
Close #23149

(maybe more)

Maybe it should even be disabled by default because as I see it, the current detection is almost pure false-positives for the "warnings", only the "errors" are real problems.

Maybe it should even be disabled by default because as I see it, the current detection is almost pure false-positives for the "warnings", only the "errors" are real problems.

Then we need a break label.

Maybe it should even be disabled by default because as I see it, the current detection is almost pure false-positives for the "warnings", only the "errors" are real problems.

Then we need a break label.

It wouldn't break anyone's workflow I assume. Not a fan of unnecessary breaking labels.

Maybe it should even be disabled by default because as I see it, the current detection is almost pure false-positives for the "warnings", only the "errors" are real problems.

I won't do so at the moment, because otherwise some extremists would catch this point and criticize that "Gitea doesn't take security seriously“

I think ideally we just remove the warning category (which warns on any irregular whitespace), and just keep the error category (which are the real bidi exploits). Doesn't have to be in this PR.

That's why I used AMBIGUOUS_UNICODE_DETECTION = true, in the future it could be improved to : AMBIGUOUS_UNICODE_DETECTION = error or AMBIGUOUS_UNICODE_DETECTION = bidi, etc

I think ideally we just remove the warning category

Sounds like a good idea. Currently this feature is kinda useless. If you have almost only false positives, Users do not care about the Warning and will ignore it, even when there's a real threat.
You should also add a User setting. Not everyone is Admin.

I think ideally we just remove the warning category

Sounds like a good idea. Currently this feature is kinda useless. If you have almost only false positives, Users do not care about the Warning and will ignore it, even when there's a real threat.
You should also add a User setting. Not everyone is Admin.

It doesn't work that way at the moment, every detected problem is rendered as "warning".
Any improvement could be done later.

Does this hide the "Escape" button in diffs? I think it should when the feature is disabled.

Does this hide the "Escape" button in file view and diffs? I think it should when the feature is disabled as the button is only useful for that feature.

Yes. There won't be "escape" button if there is no detected ambiguous unicode character.

I was unable to create a backport for 1.21. @wxiaoguang, please send one manually. :tea:
go run ./contrib/backport 28454
...  // fix git conflicts if any
go run ./contrib/backport --continue

Does this hide the "Escape" button in file view and diffs? I think it should when the feature is disabled as the button is only useful for that feature.

Yes. There won't be "escape" button if there is no detected ambiguous unicode character.

Just realized that some "escape" buttons are hidden correctly, while some are not, because some of the old code doesn't respect EscapeStatus.Escaped .... so some buttons are always there.

Does this hide the "Escape" button in file view and diffs? I think it should when the feature is disabled as the button is only useful for that feature.

Yes. There won't be "escape" button if there is no detected ambiguous unicode character.

Just realized that some "escape" buttons are hidden correctly, while some are not, because some of the old code doesn't respect EscapeStatus.Escaped .... so some buttons are always there.

We should get rid of all those unneccesary and confusing escape buttons, e.g. only show if there is actually escapable content.


Update to Python3

I've updated pykevoplus to work with python3 and have been testing it for a few months in a python3.6 venv without any noticeable issues. There are still error500 returned from time to time, but I think this is more an issue on Unikey's side than mine.

Great work guys! Hopefully there’ll be Siri support some day.


Upgrade to MudBlazor 7.0.0-rc.2 and Latest Blazor Project Templates

Description
Fixes: https://github.com/MudBlazor/Templates/issues/451
Fixes: https://github.com/MudBlazor/Templates/issues/466
Fixes: https://github.com/MudBlazor/Templates/issues/467
Fixes: https://github.com/MudBlazor/Templates/issues/458
Fixes: https://github.com/MudBlazor/Templates/issues/450
Fixes: https://github.com/MudBlazor/Templates/issues/455
Replaces PR: https://github.com/MudBlazor/Templates/pull/452
Replaces PR: https://github.com/MudBlazor/Templates/pull/459
This update upgrades the MudBlazor templates to use the latest Blazor .NET 8 templates and MudBlazor 7 RC 2.  This update also uses the MudBlazor.Static library by @Anu6is to upgrade Account pages (which use Static rendering).
Interactive Auto (Dark Mode)

Interactive Auto (Light Mode)

Register

Login

Profile

Change Email

Change Password

Two-factor authentication

Personal Data

How Has This Been Tested?
This was tested by:

Running .\InstallAndBuildAllTemplates.ps1 PowerShell script
Observing that all builds succeeded
Opening each solution and testing all links

Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

@ScarletKuro @henon @danielchalmers @mikes-gh Here's a PR for the .NET 8 MudBlazor 7.0.0-preview.4 templates.  (I had to start over.)  Currently, the template has the basic pages updated and the test PS script works, but I had some questions about what else you'd like to see:

Do you want all of the auth pages (about 20 of them) upgraded to MudBlazor components?
The template has something which may feel like a bug to end users.  The Microsoft Identity code has options.SignIn.RequireConfirmedAccount = true in it, which means nobody who registers an account can immediately log in until they connect to the database and manually modify their record.  I would like to change this flag to false to fix this (and it works), but it's less secure.  Are you okay with this change?
The Home.razor page in the template has one set of instructions for all project types.  Shall we make this more dynamic to show different messages per project type?   (I would vote yes)

Global Mode without Auth:

Mode
Status

Auto
Working

Wasm
Working

Server
Working

Per page without Auth:

Mode
Status
Description

Auto
Not working
When I open weather page gives exception: Error: One or more errors occurred. (Root component type '[MudBlazorApp1.Components.Pages.Weather](http://MudBlazorApp1.Components.Pages.Weather)' could not be found in the assembly 'MudBlazorApp1'.)

Wasm
Not working
When I open weather page gives exception: Error: One or more errors occurred. (Root component type '[MudBlazorApp1.Components.Pages.Weather](http://MudBlazorApp1.Components.Pages.Weather)' could not be found in the assembly 'MudBlazorApp1'.)

Server
Working
-

I didn't check the static SSR yet (auth). I think we need to fix the per page first to move on the next step.

Can we control the default selection mode?
I would want it to be global -> wasm.
That would eliminate a lot of complaints, as many newbie people just hit the next button.

Can we control the default selection mode? I would want it to be global -> wasm. That would eliminate a lot of complaints/issues, as many newbie people just hit the next button.

Yes, I was able to change the defaults in template.json, in the InteractivityPlatform and InteractivityLocation sections.

Per page without Auth:  Auto/Wasm Not Working

Thanks @ScarletKuro , I have fixed these issues and have retested all templates.  Also:

The Dark/Light Mode button only appears for apps without Auth
The default template is now WebAssembly/Global
The bootstrap.css and app.css are now only included by App.razor while viewing Auth pages.

... the only issue I couldn't figure out is regarding app.css and Auth pages.  The CSS shows underlines for links in the Nav Panel, but the non-Auth pages look okay:

Thanks @ScarletKuro , I have fixed these issues and have retested all templates

Great work.

... the only issue I couldn't figure out is regarding app.css and Auth pages. The CSS shows underlines for links in the Nav Panel, but the non-Auth pages look okay:

My offer would be both drop the app.css and bootstrap.css and use:
https://github.com/0phois/MudBlazor.StaticInput
https://www.nuget.org/packages/Extensions.MudBlazor.StaticInput
by @Anu6is
for the login/register pages, there is sample on the repo.

Ah, I just noticed it's for v6 :( I don't think it's compatible with v7

Pushed a pre-release for v7.
Think I thought v7 was getting released early June so I intended to wait.

Pushed a pre-release for v7. Think I thought v7 was getting released early June so I intended to wait.

Ok, thanks @Anu6is! I'm excited to check out your library and will work on the Auth pages tonight.

@Anu6is your library worked beautifully for upgrading the Account pages.  Thanks so much for your work on the static form components!

Everything seems to work. It's a very great work.

Is anyone willing to double check the templates itself? @henon @mikes-gh @xC0dex @Anu6is @danielchalmers
Otherwise I want to merge this ASAP.

Is anyone willing to double check the templates itself? @henon @mikes-gh @xC0dex @Anu6is @danielchalmers Otherwise I want to merge this ASAP.

I could try it out this evening, so in about 2–3 hours 👍

Thank you very much

Just a quick note:  When MudBlazor 7.0.0 is released, a small PR will be needed to change the Package Reference version to 7.* for templates.

Just a quick note: When MudBlazor 7.0.0 is released, a small PR will be needed to change the Package Reference version to 7.* for templates.

Yes


Gitlab returns just "Bad Request"

ERRO[2023-11-06T09:51:36+01:00] cannot update feedback retriever: cannot update commit status: Bad Request  name=sample-cicd/sample-springboot11-preview-bwxx8 request=b0cda7b6-7c81-11ee-95bc-902e16dea917

It seems it may be related with commit status, some statuses are passing, some are not.
For example - a failed pipeline is not reported.

It seems Gitlab returns 400 everytime a "Pending" or "Running" status is sent at least twice. Resolved by improving caching and by handling 400 when git-kind == gitlab

https://github.com/kube-cicd/pipelines-feedback-core/commit/6786d1fe367855bb2f747198dc287ddfd80bde01
https://github.com/kube-cicd/pipelines-feedback-core/commit/f4ab1a8c1eef6154d558c36caeb6630d0b95cd10


Need of Full example with all options (optional options also)

Can you provide Full examples with all options (optional options also)? because its needed.

The majority of the options are just what Omnipay generically supports across its various drivers. This especially applies to the card parameter, or creditCard object, which is fixed across all drivers.
The authentication and debug parameters are generally all in the API gateway classes here https://github.com/thephpleague/omnipay-authorizenet/tree/master/src These normally need to be looked at in conjunction with the gateway documentation, so you kind of need to know what the gateway is expecting anyway.
The remaining parameters that are not standard Omnipay options are then scattered over the request messages. They are unfortunately not all documented in detail, and I think with the APIs behind this driver having been deprecated by Authorize.Net some time ago, it will probably remain that way.


SassPlugin & RawPlugin both caching

This configuration:
[
  '*.scss',
  SassPlugin(),
  RawPlugin()
]

doesn't work because both the SassPlugin and RawPlugin support caching.  SassPlugin sets the cache and RawPlugin reads the sass output without doing it's normal work.  Need to find a way for multiple plugins in a row to support caching.
in 2.2.3-beta.12

Please check<EMAIL_ADDRESS>


Could you add a requirements file?

It would help speed some setup stuff up if you could.

Thanks!

Double checking but the Images for toptee, shirt, and dress shouldn't be separate right?
Also if some of the links don't work will that cause problems or will the data just be less accurate? (Trying to get it to run first before trying to worry about accuracy).


De-linearize synchronization if behind by >100 blocks

The RPC is the limiting factor,  we could trivially de-linearize the 1st order connect calls,  provided tip doesn't get confused.
tip is the only data that is "UPDATE"d.

Blocked by https://github.com/bitcoinjs/indexd/issues/26


Use CassandraContainer in Cassandra IT

Current test execution depends on a running cassandra instance,
which depends on a manual execution on the compose file. This commit
introduces testcontainers as in other modules to run such instance
along with tests.
Run test, no containers.
Clone and run experience.

I think we might have work on the same thing. My PR is also opened
https://github.com/langchain4j/langchain4j/pull/306

I didn't notice the PR. I'll leave it up to the maintainer on how to proceed. Great to see Testcontainers used as part of the PR 👍🏽

@eddumelendez thank you a lot! If you don't mind, I will leave it to @clun as his PR was first :)


Refactor Column Pruning and support where case: like and not like, is not null

What is changed and how it works?

Refactor ColumnPruning RBO Rule

refer from: https://github.com/duckdb/duckdb/blob/main/src/optimizer/remove_unused_columns.cpp

support where case

like
not like
is not null

Code changes

[x] Has Rust code change
[ ] Has CI related scripts change

Check List
Tests

[x] Unit test
[x] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Note for reviewer

This pr contains like/null expr, ColumnCatalog refactoring, constant calculation, column pruning, etc, not friendly to reviewer. You could split pr into smaller pieces next time.


Inquiry about Computational Resources

Hello,
I'm planning a project that requires approximately 10,000 single point and gradient calculations, and I found Chemcloud that supports Terachem. This seems like a great fit for my needs, but I have some questions about the available computational resources:

Are there paid plans available for users with large-scale computation needs?
What's the maximum number of batched calculations that can be run simultaneously?
Are there any limitations on computational resources (e.g., time limits, job rate restrictions)?

Thank you for your help!

Hi @kangmg. Currently you'd need to run your own BigChem/ChemCloud instances on your own hardware (or on the cloud)--the software is available open source but we are not running a paid service anywhere for other people to use.
In the future it's possible we run an open ChemCloud server that other can use (and pay for), but for now it is up to each research to run their own.
If you like the interface and user experience you may want to consider qcop which will structure and execute your calculations for you on a single node. If you have multiple nodes and want to use them collectively BigChem is the easiest way to do this and I can help you setup a cluster, if you'd like :)


Feature/exempt tags

Coverage decreased (-1.2%) to 86.923% when pulling c6fe249a265dfb52d35a2a54eed879d46c733a97 on feature/exempt_tags into 27773169a8827905fcf09aed85e0545c1534b179 on master.

Coverage decreased (-1.2%) to 86.923% when pulling a4f3ef90235de3590af8e7becf27b4f6560f68fc on feature/exempt_tags into 27773169a8827905fcf09aed85e0545c1534b179 on master.

Coverage decreased (-1.2%) to 86.923% when pulling 6dcaf64897e96f04288d15ee1570498b7de92f2e on feature/exempt_tags into 27773169a8827905fcf09aed85e0545c1534b179 on master.

Coverage decreased (-1.2%) to 86.923% when pulling 17f3625bf9b5e333bb9530e70c5ff0fe11eb0a1d on feature/exempt_tags into 27773169a8827905fcf09aed85e0545c1534b179 on master.

Coverage increased (+2.03%) to 90.181% when pulling<PHONE_NUMBER>4dadc37780acb5ee1e2c3de80e3bdf on feature/exempt_tags into 27773169a8827905fcf09aed85e0545c1534b179 on master.

Coverage increased (+2.03%) to 90.181% when pulling 240eec8b81d964da145ece85a4c05e4114241b18 on feature/exempt_tags into 27773169a8827905fcf09aed85e0545c1534b179 on master.

Coverage increased (+2.03%) to 90.181% when pulling 8f0dfc72cb1b1a36871347f2ae6488a67ecfe89c on feature/exempt_tags into 27773169a8827905fcf09aed85e0545c1534b179 on master.

Coverage increased (+2.03%) to 90.181% when pulling 5c8d7c666417877d80f1af4172685c96fd772222 on feature/exempt_tags into 27773169a8827905fcf09aed85e0545c1534b179 on master.

Coverage increased (+2.03%) to 90.181% when pulling 5c8d7c666417877d80f1af4172685c96fd772222 on feature/exempt_tags into 27773169a8827905fcf09aed85e0545c1534b179 on master.


Typo in require path

Short description of the problem:
Webpack build fails with this error: build dev failed: Cannot find module '../util/Logger'
What behavior are you expecting?
In dist/webpack/ionic-environment-plugin.js
var Logger_1 = require('../util/Logger');

should be:
var Logger_1 = require('../util/logger');

(notice the lowercase l)
Steps to reproduce:

Start new project
Run ionic serve

Which @ionic/app-scripts version are you using?
0.0.41

This is an especially mean typo because it breaks builds on case-sensitive file systems (e.g. most Linux), but works on case-insensitive systems (e.g. some macOS). My workaround is to symlink Logger.js to logger.js but obviously this should be fixed upstream.

Ops, didn't see this issue. Closing https://github.com/driftyco/ionic-app-scripts/issues/332

@marcoturi had a PR merged for this. This must have been a VSCode autocorrect or something. Not sure. Sorry!
Thanks,
Dan

Hello guys! Sorry about this question but I am new in this world! How can I update ionic to fix this issue? I tried with npm install -g ionic, ionic lib update (ups, lot of warning related to use a deprecated command).
Thanks in advance.

@fedesardo,
We haven't published a fix yet but probably will today (Thursday).
Thanks,
Dan

@fedesardo If you need to get it fixed right now before a new version is published, go to the root of your project and edit the file at<EMAIL_ADDRESS>Change line number 2 from
var Logger_1 = require('../util/Logger');
to
var Logger_1 = require('../util/logger');
Don't forget to update @ionic/app-scripts to the latest version as soon as it's published!

Thanks, @jsayol !!!

Thanks for your answer and workaround ideas!

This is resolved. Please install npm install @ionic/app-scripts@latest.
Thanks,
Dan

In Linux Mint, I need change local variable "logger" yet, even updating lasted script.

@guibson91, I'm not following what you mean. Can you explain what you changed?
Thanks,
Dan

I deleted the node_modules folder, ran the "npm install @ ionic / app-scripts @ latest" command, but I kept getting error messages because of "Util / Logger".
When I renamed the variable:
Var Logger_1 = require ( '../ util / Logger');
to
Var Logger_1 = require ( '../ util / logger');
In file<EMAIL_ADDRESS>solved the problem.
My OS is Linux Mint 17, which the terminal is case sensitive.


npm run test:integration command not working on M1

I noticed that in workspaces-rs there was a fix implemented for this error message:
Error: Action #0: CompilationError(WasmerCompileError { msg: "The target x86_64 without AVX is not yet supported (see https://docs.wasmer.io/ecosystem/wasmer/wasmer-features)" })
However when setting up a default project with create-near-app when I run npm test I'm still seeing this error message. Is there something I can do in my project configuration to pull in the M1 fix for the tests?

here is my cargo.toml in the integration-tests folder:
`[package]
name = "integration-tests"
version = "1.0.0"
publish = false
edition = "2018"
[dev-dependencies]
anyhow = "1.0"
borsh = "0.9"
maplit = "1.0"
near-units = "0.2.0"
arbitrary_precision enabled for u128 types that workspaces requires for Balance types
serde_json = { version = "1.0", features = ["arbitrary_precision"] }
tokio = { version = "1.18.1", features = ["full"] }
tracing = "0.1"
tracing-subscriber = { version = "0.3.11", features = ["env-filter"] }
workspaces = "0.4.0"
pkg-config = "0.3.1"
[[example]]
name = "integration-tests"
path = "src/tests.rs"
`
So it seems I have the version with the fix: 0.4.0 but still getting this error

fixed by installing rust again without using Rosetta 2


load rules_swift 1.3.0

load rules_swift 1.3.0, and run the build bazelisk build //iOSApp/Test/SwiftUnitTests:iOSAppSwiftUnitTests to get below error
~/tinder/rules_xcodeproj/examples/integration/ [issue-933/duplicate_symbol_linker_error+*] bazelisk build //iOSApp/Test/SwiftUnitTests:iOSAppSwiftUnitTests
INFO: Analyzed target //iOSApp/Test/SwiftUnitTests:iOSAppSwiftUnitTests (101 packages loaded, 3393 targets configured).
INFO: Found 1 target...
INFO: From AssetCatalogCompile iOSApp/Source/iOSApp-intermediates/xcassets:
/* com.apple.actool.document.notices */
/Users/kaijing/tinder/rules_xcodeproj/examples/integration/iOSApp/Source/Assets.xcassets:./AppIcon.appiconset/[][iphone][57x57][][][2x][][][]: notice: 57x57@2x app icons only apply to iPhone apps targeting releases of iOS prior to 7.0
INFO: From MomCompile iOSApp/Source/iOSApp-intermediates/Model.momd:
/Users/kaijing/tinder/rules_xcodeproj/examples/integration/bazel-output-base/sandbox/darwin-sandbox/87/execroot/main/iOSApp/Source/Model.xcdatamodeld/Model2.xcdatamodel:Entity2.parent: warning: Entity2.parent should have an inverse [2]
ERROR: /Users/kaijing/tinder/rules_xcodeproj/examples/integration/iOSApp/Test/TestingUtils/BUILD:3:14: Compiling Swift module //iOSApp/Test/TestingUtils:TestingUtils failed: (Exit 1): worker failed: error executing command bazel-out/darwin_x86_64-opt-exec-BDE7E609-ST-53df4e45311b/bin/external/build_bazel_rules_swift/tools/worker/worker swiftc ... (remaining 1 argument skipped)
swift_worker: Could not copy bazel-out/ios-sim_arm64-min15.0-applebin_ios-ios_sim_arm64-fastbuild-ST-25e246568c54/bin/iOSApp/Test/TestingUtils/SwiftAPI/TestingUtils-Swift.h to bazel-out/ios-sim_arm64-min15.0-applebin_ios-ios_sim_arm64-fastbuild-ST-25e246568c54/bin/_swift_incremental/iOSApp/Test/TestingUtils/SwiftAPI/TestingUtils-Swift.h (No such file or directory)
Target //iOSApp/Test/SwiftUnitTests:iOSAppSwiftUnitTests failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /Users/kaijing/tinder/rules_xcodeproj/examples/integration/iOSApp/Test/SwiftUnitTests/BUILD:17:14 Compiling Swift module //iOSApp/Test/SwiftUnitTests:iOSAppSwiftUnitTests.library failed: (Exit 1): worker failed: error executing command bazel-out/darwin_x86_64-opt-exec-BDE7E609-ST-53df4e45311b/bin/external/build_bazel_rules_swift/tools/worker/worker swiftc ... (remaining 1 argument skipped)
INFO: Elapsed time: 18.991s, Critical Path: 7.56s
INFO: 299 processes: 199 internal, 86 darwin-sandbox, 12 local, 2 worker.
FAILED: Build did NOT complete successfully

I'm tracking this in the update PR. rules_swift has broken objc header generation. We should have a fix for it soon, probably a 1.3.1.

I'm tracking this in the update PR. rules_swift has broken objc header generation. We should have a fix for it soon, probably a 1.3.1.

@brentleyjones  Thanks very much to look at the issue. Actually, I try to use this example to reproduce the issue of https://github.com/bazelbuild/rules_swift/issues/933
I expect to see the duplicate symbol and linker error, but see the above -swift.h error.


freetype: add some key reverse dependencies to passthru.tests

Description of changes
Packages that have a large reverse dependency set are hard to test because a full rebuild is infeasible. But on the other hand, it's tricky for reviewers to remember which reverse dependencies of a particular package are particularly important to ensure are working or are known to be particularly sensitive to changes in the depended package.
Therefore it makes sense to add a small selection of such packages to passthru.tests. Done here for freetype.
See also #167079 in the same vein
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I created a new label ^


numaresourcesscheduler: configmap hash annotation

We're adding an annotation with the ConfigMap's hash which is used by the scheduler, under the deployment .spec.template filed.
This way, for every change/update done to the ConfigMap, a new hash will get calculated which in turn causes the deployment to restart the scheduler pod and read the updated ConfigMap.
This change is important in order to make sure that we're not running the scheduler pod with a stale ConfigMap configuration.

/cc @fromanirh

we will need a similar change for RTE - and to disable the exit-on-config-change flag as well.

we will need a similar change for RTE - and to disable the exit-on-config-change flag as well.

This solution will work only when RTE is deployed with the controller.
Is that good enough to justify the removal of the current solution which works (although not perfectly) with the deployer as well?

/hold verify the solution by running the serial tests locally

we will need a similar change for RTE - and to disable the exit-on-config-change flag as well.

This solution will work only when RTE is deployed with the controller. Is that good enough to justify the removal of the current solution which works (although not perfectly) with the deployer as well?

we will not remove the fix from the deployer, but we should use the same approach for the RTE in the numaresourcesoperator_controller, and we should stop enabling the exit-on-config-changes flag (https://github.com/openshift-kni/numaresources-operator/blob/v4.10.0-rc0/pkg/objectstate/rte/rte.go#L345)

let's retarget this PR and add the similar change also for the numaresourcesoperator controller

OK i'll start working on it

/appove
/cherry-pick release-4.10

/approve

we're almost ready. Let's solve the BinaryData thingy, let's add some unit tests for the newly added hash package and we're good.

BinaryData can be postponed, but we need some unit test coverage for the hash package

BinaryData can be postponed, but we need some unit test coverage for the hash package

On the grill

/hold cancel

/hold

the lint failures need attention but the lint lane is non-blocking, so let me re-add the hold

PTAL to the lint failures the gh actions E2E flow error is non-blocking

Fixed the lint issue

/lgtm
/approve

/hold cancel

@Tal-or could you please take care of the cherry-pick to the release-4.10 branch? we don't need 1:1 commit fidelity so a manual backport is ok (we avoid because automatick cherry-picks are more convenient)

@Tal-or could you please take care of the cherry-pick to the release-4.10 branch? we don't need 1:1 commit fidelity so a manual backport is ok (we avoid because automatick cherry-picks are more convenient)

Sure I'll handle it


dbeaver/pro#2309 Column alias visibility

Solves both https://github.com/dbeaver/dbeaver/issues/22374 and https://github.com/dbeaver/pro/issues/2309
Column aliases has restricted visibility:
https://stackoverflow.com/questions/13031013/how-do-i-use-alias-in-where-clause
Currently we made them visible by default for all databases everywhere.
And specified some concrete visibility scopes for several databases (see below). Please test specified databases. If column alias is not visible in some scope, it should be highlighted with red. If it should be visible in some scope, no red highlighting should appear. Note: it should be tested with active connection and Read database tables/columns for semantic analysis on.
Column alias is visible in:

[x]  SQLite: everywhere
[x] PostgreSQL: GROUP BY, ORDER BY https://dba.stackexchange.com/a/225883
[x] DB2:  ORDER BY https://www.ibm.com/docs/en/ias?topic=nps-using-column-aliases-in-where-clause
[x] MySQL: GROUP BY, HAVING, ORDER BY https://dev.mysql.com/doc/refman/8.0/en/problems-with-alias.html
[x] SQL Server: ORDER BY https://learn.microsoft.com/en-us/previous-versions/sql/compact/sql-server-compact-4.0/ms173451(v=sql.110)?redirectedfrom=MSDN
[x] Snowflake: everywhere
[x] Oracle: ORDER BY
[x] Clickhouse: everywhere
[x] Exasol: ORDER BY

You can test it on the following query:
SELECT
1 AS TEST_ALIAS
FROM
TPCH_SF1.CUSTOMER  a
WHERE TEST_ALIAS IS not NULL AND 1 > TEST_ALIAS
GROUP BY TEST_ALIAS
HAVING TEST_ALIAS > 0 AND 8 > TEST_ALIAS
ORDER BY TEST_ALIAS;

Main idea
If nothing is highlighted with red, then query should be executed without errors. If something is highlighted with red, then query should NOT be executed without errors.
Also you can investigate visibility scopes by trying to execute such query and reading database response.

verified


Show average unit price in calculations PDF.

This makes it easier to understand how the pool unit cost evolves, and makes it easier to understand the capital gain or losses.

Makes sense, thanks!


PatternFly milestone update

PatternFly milestone update
https://issues.redhat.com/browse/COST-3339

Codecov Report

Merging #2778 (c710d66) into main (7e9b53d) will decrease coverage by 0.00%.
The diff coverage is n/a.

:exclamation: Current head c710d66 differs from pull request most recent head 1e3f482. Consider uploading reports for the commit 1e3f482 to get more accurate results

@@            Coverage Diff             @@
##             main    #2778      +/-   ##
==========================================
- Coverage   65.90%   65.89%   -0.01%
==========================================
  Files         486      485       -1
  Lines        9323     9319       -4
  Branches     2150     2000     -150
==========================================
- Hits         6144     6141       -3
+ Misses       3176     3175       -1
  Partials        3        3

Impacted Files
Coverage Δ

...c/routes/views/components/dataToolbar/tagValue.tsx
27.77% <0.00%> (-0.99%)
:arrow_down:

src/store/featureFlags/featureFlagsActions.ts
100.00% <0.00%> (ø)

src/store/featureFlags/featureFlagsReducer.ts
100.00% <0.00%> (ø)

src/store/featureFlags/featureFlagsSelectors.ts
100.00% <0.00%> (ø)

...tes/costModels/costModelsDetails/utils/filters.tsx
74.13% <0.00%> (ø)

...Overview/ociCostOverview/ociCostOverviewWidgets.ts
100.00% <0.00%> (ø)

...Overview/ocpCostOverview/ocpCostOverviewWidgets.ts
100.00% <0.00%> (ø)

...erview/rhelCostOverview/rhelCostOverviewWidgets.ts
100.00% <0.00%> (ø)

...view/azureCostOverview/azureCostOverviewWidgets.ts
100.00% <0.00%> (ø)

src/utils/props.ts

... and 2 more

Continue to review full report at Codecov.

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


Fixing smattering of issues regarding updating projects for cross-plat

Fixes #22569
Fixes #22570
Fixes #22567

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 19 (52.63%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+8.0e**-05%**) to 41.708%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-database-projects/src/controllers/projectController.ts
0
4
0.0%

extensions/sql-database-projects/src/models/project.ts
7
12
58.33%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

extensions/sql-bindings/src/common/azureFunctionsUtils.ts
1
80.65%

Totals

Change from base Build<PHONE_NUMBER>:
8.0e-05%

Covered Lines:
30340

Relevant Lines:
67346

💛  - Coveralls