[stable/prometheus-postgres-exporter] CrashLoopBackOf on fresh install

BUG REPORT

Version of Helm and Kubernetes:

Kubernetes: 1.9.4
Helm: v2.8.2

Which chart:

stable/prometheus-postgres-exporter

What happened:

Pod doesn't start.  Viewing the pod with kubectl get pods I see that the pod is getting into a CrashLoopBackOff state after several unsuccessful restarts.

What you expected to happen:

Would like to see the pod start up successfully without intvervention

How to reproduce it (as minimally and precisely as possible):

Spin up Kubernetes instance, I used Minikube
Install configure Helm
helm install stable/prometheus-postgres-exporter --name test

Anything else we need to know:

I don't see any logs for the pod itself but can see error using kubectl get events, which makes it seem like there is something wrong with the manifests getting deployed but haven't found what is causing the error yet.

44s         5m           25        test-prometheus-postgres-exporter-7b5f9c5b47-t4wmp.1525f89e4c392cdb   Pod          spec.containers{prometheus-postgres-exporter}   Warning   BackOff                        kubelet, minikube       Back-off restarting failed container
5m          5m           1         test-prometheus-postgres-exporter-7b5f9c5b47-t4wmp.1525f8a27713dc21   Pod          spec.containers{prometheus-postgres-exporter}   Warning   Failed                         kubelet, minikube       Error: failed to start container "prometheus-postgres-exporter": Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/13edcd8ee6d90110ce6fab64e90ad616961799416765166f844027b27820f478/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/209f3b964d2c905a9c516db94c0391994634ee90ee3697b303c12d6606809028/merged\\\" at \\\"/var/lib/docker/overlay2/209f3b964d2c905a9c516db94c0391994634ee90ee3697b303c12d6606809028/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/209f3b964d2c905a9c516db94c0391994634ee90ee3697b303c12d6606809028/merged/etc/resolv.conf: read-only file system\\\"\""
4m          4m           1         test-prometheus-postgres-exporter-7b5f9c5b47-t4wmp.1525f8a8bd69a717   Pod          spec.containers{prometheus-postgres-exporter}   Warning   Failed                         kubelet, minikube       Error: failed to start container "prometheus-postgres-exporter": Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/13edcd8ee6d90110ce6fab64e90ad616961799416765166f844027b27820f478/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/70e85fa1255be13f73ca343607c5399d9abcf034151a1388c1c4711fdfa1591c/merged\\\" at \\\"/var/lib/docker/overlay2/70e85fa1255be13f73ca343607c5399d9abcf034151a1388c1c4711fdfa1591c/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/70e85fa1255be13f73ca343607c5399d9abcf034151a1388c1c4711fdfa1591c/merged/etc/resolv.conf: read-only file system\\\"\""
5m          5m           1         test-prometheus-postgres-exporter-7b5f9c5b47.1525f89b8dd5ff71         ReplicaSet                                                   Normal    SuccessfulCreate               replicaset-controller   Created pod: test-prometheus-postgres-exporter-7b5f9c5b47-t4wmp
5m          5m           1         test-prometheus-postgres-exporter.1525f89b8caace61                    Deployment                                                   Normal    ScalingReplicaSet              deployment-controller   Scaled up replica set test-prometheus-postgres-exporter-7b5f9c5b47 to 1

Here's the output from kubectl describe pod <name>.
kubectl describe pod
Name:           test-prometheus-postgres-exporter-7b5f9c5b47-t4wmp
Namespace:      default
Node:           minikube/<IP_ADDRESS>
Start Time:     Mon, 16 Apr 2018 09:49:55 -0700
Labels:         app=prometheus-postgres-exporter
                pod-template-hash=3619571603
                release=test
Annotations:    checksum/config=3d937b08e2a6d955bc6987aa3db916cc1a5717b6be465cf5d4f4ae3b576bff4b
Status:         Running
IP:             <IP_ADDRESS>
Controlled By:  ReplicaSet/test-prometheus-postgres-exporter-7b5f9c5b47
Containers:
  prometheus-postgres-exporter:
    Container ID:  docker://b82e4e7b71094574771b4014e31cc923f4aa101aed61e0703b483a6932e96d3f
    Image:         wrouesnel/postgres_exporter:v0.4.4
    Image ID:      docker-pullable://wrouesnel/postgres_exporter@sha256:f9810bc64b2d30c624ee3efa51a6c17b20b4ace30b014a0b30f80177313b9b74
    Port:          9187/TCP
    State:         Waiting
      Reason:      CrashLoopBackOff
    Last State:    Terminated
      Reason:      ContainerCannotRun
      Message:     oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/8bb49f1f7d9a143f2e5d69f8dfa97276cd19d9f41b4f921be895ca471d935664/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/c40bd147c64db80cf4a731a7b11881dd043c5fc5b1e031d6d4fdbbf5e448591a/merged\\\" at \\\"/var/lib/docker/overlay2/c40bd147c64db80cf4a731a7b11881dd043c5fc5b1e031d6d4fdbbf5e448591a/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/c40bd147c64db80cf4a731a7b11881dd043c5fc5b1e031d6d4fdbbf5e448591a/merged/etc/resolv.conf: read-only file system\\\"\""

      Exit Code:    128
      Started:      Mon, 16 Apr 2018 11:51:49 -0700
      Finished:     Mon, 16 Apr 2018 11:51:49 -0700
    Ready:          False
    Restart Count:  8
    Liveness:       http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      DATA_SOURCE_NAME:  <set to the key 'data_source_name' in secret 'test-prometheus-postgres-exporter'>  Optional: false
    Mounts:
      /etc from queries (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from test-prometheus-postgres-exporter-token-b6t25 (ro)
Conditions:
  Type           Status
  Initialized    True
  Ready          False
  PodScheduled   True
Volumes:
  queries:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      test-prometheus-postgres-exporter
    Optional:  false
  test-prometheus-postgres-exporter-token-b6t25:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  test-prometheus-postgres-exporter-token-b6t25
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     <none>
Events:
  Type     Reason                 Age                      From               Message
  ----     ------                 ----                     ----               -------
  Normal   Scheduled              2h                       default-scheduler  Successfully assigned test-prometheus-postgres-exporter-7b5f9c5b47-t4wmp to minikube
  Normal   SuccessfulMountVolume  2h                       kubelet, minikube  MountVolume.SetUp succeeded for volume "queries"
  Normal   SuccessfulMountVolume  2h                       kubelet, minikube  MountVolume.SetUp succeeded for volume "test-prometheus-postgres-exporter-token-b6t25"
  Normal   Pulling                2h                       kubelet, minikube  pulling image "wrouesnel/postgres_exporter:v0.4.4"
  Normal   Pulled                 2h                       kubelet, minikube  Successfully pulled image "wrouesnel/postgres_exporter:v0.4.4"
  Warning  Failed                 2h                       kubelet, minikube  Error: failed to start container "prometheus-postgres-exporter": Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/13edcd8ee6d90110ce6fab64e90ad616961799416765166f844027b27820f478/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/a4949183051d21563ba37e7218fbee92b2200f095f1e8d8a29d77f8128bf9778/merged\\\" at \\\"/var/lib/docker/overlay2/a4949183051d21563ba37e7218fbee92b2200f095f1e8d8a29d77f8128bf9778/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/a4949183051d21563ba37e7218fbee92b2200f095f1e8d8a29d77f8128bf9778/merged/etc/resolv.conf: read-only file system\\\"\""
  Warning  Failed                 2h                       kubelet, minikube  Error: failed to start container "prometheus-postgres-exporter": Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/13edcd8ee6d90110ce6fab64e90ad616961799416765166f844027b27820f478/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/0d05a535e11fc2ce7969b826a03f33a8538455c4c79aad333da924c7bd379e40/merged\\\" at \\\"/var/lib/docker/overlay2/0d05a535e11fc2ce7969b826a03f33a8538455c4c79aad333da924c7bd379e40/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/0d05a535e11fc2ce7969b826a03f33a8538455c4c79aad333da924c7bd379e40/merged/etc/resolv.conf: read-only file system\\\"\""
  Warning  Failed                 2h                       kubelet, minikube  Error: failed to start container "prometheus-postgres-exporter": Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/13edcd8ee6d90110ce6fab64e90ad616961799416765166f844027b27820f478/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/209f3b964d2c905a9c516db94c0391994634ee90ee3697b303c12d6606809028/merged\\\" at \\\"/var/lib/docker/overlay2/209f3b964d2c905a9c516db94c0391994634ee90ee3697b303c12d6606809028/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/209f3b964d2c905a9c516db94c0391994634ee90ee3697b303c12d6606809028/merged/etc/resolv.conf: read-only file system\\\"\""
  Normal   Created                2h (x4 over 2h)          kubelet, minikube  Created container
  Warning  Failed                 2h                       kubelet, minikube  Error: failed to start container "prometheus-postgres-exporter": Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/13edcd8ee6d90110ce6fab64e90ad616961799416765166f844027b27820f478/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/70e85fa1255be13f73ca343607c5399d9abcf034151a1388c1c4711fdfa1591c/merged\\\" at \\\"/var/lib/docker/overlay2/70e85fa1255be13f73ca343607c5399d9abcf034151a1388c1c4711fdfa1591c/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/70e85fa1255be13f73ca343607c5399d9abcf034151a1388c1c4711fdfa1591c/merged/etc/resolv.conf: read-only file system\\\"\""
  Normal   Pulled                 2h (x4 over 2h)          kubelet, minikube  Container image "wrouesnel/postgres_exporter:v0.4.4" already present on machine
  Warning  BackOff                1h (x48 over 2h)         kubelet, minikube  Back-off restarting failed container
  Normal   SuccessfulMountVolume  46s                      kubelet, minikube  MountVolume.SetUp succeeded for volume "queries"
  Normal   SuccessfulMountVolume  46s                      kubelet, minikube  MountVolume.SetUp succeeded for volume "test-prometheus-postgres-exporter-token-b6t25"
  Normal   SandboxChanged         46s                      kubelet, minikube  Pod sandbox changed, it will be killed and re-created.
  Warning  Failed                 41s                      kubelet, minikube  Error: failed to start container "prometheus-postgres-exporter": Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/8bb49f1f7d9a143f2e5d69f8dfa97276cd19d9f41b4f921be895ca471d935664/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/aca862930677982ecba73c9e845e333194a247333abdfd9e01017bed6c8b54af/merged\\\" at \\\"/var/lib/docker/overlay2/aca862930677982ecba73c9e845e333194a247333abdfd9e01017bed6c8b54af/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/aca862930677982ecba73c9e845e333194a247333abdfd9e01017bed6c8b54af/merged/etc/resolv.conf: read-only file system\\\"\""
  Warning  Failed                 29s                      kubelet, minikube  Error: failed to start container "prometheus-postgres-exporter": Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/8bb49f1f7d9a143f2e5d69f8dfa97276cd19d9f41b4f921be895ca471d935664/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/c40bd147c64db80cf4a731a7b11881dd043c5fc5b1e031d6d4fdbbf5e448591a/merged\\\" at \\\"/var/lib/docker/overlay2/c40bd147c64db80cf4a731a7b11881dd043c5fc5b1e031d6d4fdbbf5e448591a/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/c40bd147c64db80cf4a731a7b11881dd043c5fc5b1e031d6d4fdbbf5e448591a/merged/etc/resolv.conf: read-only file system\\\"\""
  Warning  BackOff                9s (x4 over 35s)         kubelet, minikube  Back-off restarting failed container
  Normal   Pulled                 <invalid> (x3 over 43s)  kubelet, minikube  Container image "wrouesnel/postgres_exporter:v0.4.4" already present on machine
  Normal   Created                <invalid> (x3 over 43s)  kubelet, minikube  Created container
  Warning  Failed                 <invalid>                kubelet, minikube  Error: failed to start container "prometheus-postgres-exporter": Error response from daemon: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/var/lib/docker/containers/8bb49f1f7d9a143f2e5d69f8dfa97276cd19d9f41b4f921be895ca471d935664/resolv.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/37e7270405505d1de55724920c9c27c04504e1ac02d11228512bea9a63352d16/merged\\\" at \\\"/var/lib/docker/overlay2/37e7270405505d1de55724920c9c27c04504e1ac02d11228512bea9a63352d16/merged/etc/resolv.conf\\\" caused \\\"open /var/lib/docker/overlay2/37e7270405505d1de55724920c9c27c04504e1ac02d11228512bea9a63352d16/merged/etc/resolv.conf: read-only file system\\\"\""

I have been able to get the pod to start by removing the volumeMounts spec.
volumeMounts:
            - name: queries
              mountPath: /etc

If there is a quick fix for this I can do a PR.


Container labels are ignored

When launching a container to a non-clustered docker host thru port 2376, I can pass a label which I can then later filter on with 'docker ps':
$ docker run -d --label=roambee=true --name=busybox busybox sleep 120
$ docker ps  --filter "label=roambee=true"
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
f4273a4643fc        busybox:latest      "sleep 120"         13 seconds ago      Up 9 seconds                            busybox

I can 'docker inspect' the container and see the label metadata.
However, if I launch this container into a docker-swarm thru port 3376, the label is not present on the container.  The 'docker ps' command returns ALL CONTAINERS.  'docker inspect' shows an empty label structure.

@peebles this was fixed with https://github.com/docker/swarm/pull/738 are you using 0.2.0 or master ?

I am using "docker run --rm swarm create" (etc).  So which version are you talking about?
$ docker --version
Docker version 1.6.0, build 4749651
$ docker-machine --version
docker-machine version 0.2.0 (8b9eaf2)

I see.  I can install "swarm" binary itself and use it.  And master has the fix.  Then how do I do things like
eval $(docker-machine env --swarm cluster-master)
docker ps

Cool, it works with master.  I git-cloned, built the image with Dockerfile
and used that image when launching the swarm nodes and master.  ps
filtering appears to work fine now.
a
On Mon, May 11, 2015 at 5:18 PM, Victor Vieux<EMAIL_ADDRESS>wrote:

@peebles https://github.com/peebles this was fixed with #738
https://github.com/docker/swarm/pull/738 are you using 0.2.0 or master ?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/swarm/issues/764#issuecomment-101079861.

Perfect! :)


text input display on another page

Description of the Feature
Hello everyone
I have a question please... I'm making an app for my project using Kivymd, is there anyway I can view the text input from one screen (the one on the left) to another one (on the right), where one screen I put the information and  the other screen displays it after its saved.
can someone help me with the code please. Thanks

Screenshots
Add images to explain us this feature. Paste urls here.
Remove this section if no images here
Versions

OS:
Python:
Kivy:
KivyMD:

greetings
This is not a bug, but rather a support request, for this kind of questions use the appropiate discord channels.
you can find the server on the repo README.MD
this is not a kivymd related issue, rather a kivy framework issue.
yes it is possible.
you can use the ID of the label between screen or use the app method to share the data between screens.


Application run fail when using @JobWorker annotation

Running the code as-is (save for updated application.properties values) is failing with the error:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'customerOnboardingGlueCode'
Caused by:
java.lang.NoClassDefFoundError: org/springframework/core/LocalVariableTableParameterNameDiscoverer
with several mentions of io.camunda.zeebe.spring.client.annotation.processor.ZeebeWorkerAnnotationProcessor.
The error disappears when the code is refactored to eliminate the use of the @JobWorker annotation by manually creating the JobWorkers using client.newWorker().jobType(...).handler(...).open();.

Some further investigation revealed that the root cause was a version mismatch between the Zeebe client and the cluster. Updating the zeebe.version property in the pom.xml to match the cluster (8.3.4 at the time of writing) solved the problem.


Remove explicit server stop

Stopping the remote-processor in the stop command has two side effect:

stopping the remote-processor thread will fail as it is not possible
to join a thread to itself. This leads to the leak of all the thread
object (destructor not called).
the server will not return the exit command status as it has been
stopped during it's execution.

Remove the remote-processor stop as it will be called during it's
destruction.

Rebased to trigger a build from travis.

Anyone ? It is very easy to reproduce:
Without the patch
$ test-platform config.xml &
$ remote-process localhost 5001 exit
Unable to received answer from target: Size read failed: Connection reset by peer

# $? == 1; 2 valgrind leak

With the patch
$ test-platform config.xml &
$ remote-process localhost 5001 exit

# $? == 0; 0 valgrind leak


Correct capability and Route information. Add link to more docs.

cc @cdonthini

@hpsin,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Thanks Lauren!


07/01/2018 21:46 : Create Pull Request for branch prTesting_2018070121 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

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


added runtime component generation

Signed-off-by: ashish<EMAIL_ADDRESS>Description
This PR added runtime component generation
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@leecalcote  when I commit any requested changes in the commit, the DCO fails in the subsequent workflow run.(Like in this case)
Any way to get around this?

@leecalcote I think we can extract out a common function from here. I would propose to take the configuration via a struct so that we can make changes to the function without changing the function signature. We would want the function to have the following configurations:

timeouts
url
probably consume the generation method via a string => "manifest" | "helm"
filters

A future item to add here will be a callback function which is invoked on each definition. This will minimize the code duplication while ensuring that the adapters get full control of the generated components which would be needed for converting workloads to traits (maybe for envoyfilter, virtual service, etc) or for attaching additional metadata.

@leecalcote  when I commit any requested changes in the commit, the DCO fails in the subsequent workflow run.(Like in this case)
Any way to get around this?

Good question, @Revolyssup. The DCO issue is probably from one of my web-based commits. We're safe to ignore this warning and will manually override it. Thanks for double checking.

@Revolyssup @leecalcote I think we can extract out a common function from here. I would propose to take the configuration via a struct so that we can make changes to the function without changing the function signature. We would want the function to have the following configurations:

timeouts
url
probably consume the generation method via a string => "manifest" | "helm"
filters

A future item to add here will be a callback function which is invoked on each definition. This will minimize the code duplication while ensuring that the adapters get full control of the generated components which would be needed for converting workloads to traits (maybe for envoyfilter, virtual service, etc) or for attaching additional metadata.

@utkarsh-pro  About making the URL configurable:
The version is fetched on runtime and added to the URL. Hence user doesn't know the exact URL beforehand.
Every adaptor has its own way of finding versions.So we will have to leave the version calculation to each adapter. And the config can have a version field. Also the url can be configured now that we have version

@Revolyssup @leecalcote I think we can extract out a common function from here. I would propose to take the configuration via a struct so that we can make changes to the function without changing the function signature. We would want the function to have the following configurations:

timeouts
url
probably consume the generation method via a string => "manifest" | "helm"
filters

A future item to add here will be a callback function which is invoked on each definition. This will minimize the code duplication while ensuring that the adapters get full control of the generated components which would be needed for converting workloads to traits (maybe for envoyfilter, virtual service, etc) or for attaching additional metadata.

@utkarsh-pro About making the URL configurable:
The version is fetched on runtime and added to the URL. Hence user doesn't know the exact URL beforehand.
Every adaptor has its own way of finding versions.So we will have to leave the version calculation to each adapter. And the config can have a version field. Also the url can be configured now that we have version

@utkarsh-pro  Are you proposing to add these functions as method on those structs.
Or pass the struct as config to those functions?

@leecalcote  The filter configuration i.e. manifests.Config need to be also configurable in that case.
Although all adaptors currently have same exact json paths in their CRD's, there is not spec and any adaptor in future can change the way their manifests look like. So eventhough now the json paths for all adaptors looks exactly the same, they still should be configurable by individual adaptors instead of being hardcoded in adaptor library

@leecalcote  Also , the OAMRegistrantData struct also exists in each adpators individually,which is also being used. So we will also have to centralize that struct. So first we will have to start from taking that struct out from each adaptor and centralizing it. That would require a lot of refactoring. Lets discuss on today's call.

I missed your comments until just now, @Revolyssup.
Catching up here, how much refactoring does #115 address? More than likely, we’ll want to refactor in order to centralize. Quality, consistency, sustainability - all reasons to refactor and DRY.

I missed your comments until just now, @Revolyssup.
Catching up here, how much refactoring does #115 address? More than likely, we’ll want to refactor in order to centralize. Quality, consistency, sustainability - all reasons to refactor and DRY.

yups these changes are old, have refactored changes here. Making the new PR

Very good, @Revolyssup. Thank you for confirming.


Issue

this doesn't work on android 11 and above
Doesn't work on all devices

Hello, @kwesiamartey can you provide error logs in here?

Hello, I am a developer from China. I can only use Google Translate to communicate with you. I am very sorry for this.
I seem to have encountered this problem too. I currently only have two devices in my hand, one is Android 9 and the other is Android 13. On Android 9, I can successfully wake up the permission application and open the camera smoothly, but my other Android 13 has no response and no error prompts. I'm not sure if this is a problem I'm using

Hello there, I encountered same problem. I think the issue here is due to permission handling - when I manually enable Camera permission in application settings, everything works fine.
Without manual grant of Camera permission for the application, the code below just prints a message to the console and no camera view is displayed, nor is the user prompted to grant the permission.
Tested on: Emulator with Android API 34
Code:

@Composable
@Preview
fun App() {
    MaterialTheme {
        Column(modifier = Modifier.fillMaxSize()) {
            Text("Some text")
            MyScreen()
        }
    }
}

@Composable
fun MyScreen() {
    val state = rememberPeekabooCameraState(
        onCapture = { /* Handle captured images */ },
    )

    PeekabooCamera(
        state = state,
        modifier = Modifier.fillMaxSize(),
        permissionDeniedContent = {
            println("\uD83C\uDF44 Permission failed")
        },
    )
}

Logs:

2024-05-30 16:45:07.619  8330-8330  ziparchive              cz.procyon.kmp                       W  Unable to open '/data/app/~~SDxJRZhIeCcJD6Dyhkuf0Q==/cz.procyon.kmp-d8jdsrz5V2CUvCgPptHrYw==/base.dm': No such file or directory
2024-05-30 16:45:07.619  8330-8330  ziparchive              cz.procyon.kmp                       W  Unable to open '/data/app/~~SDxJRZhIeCcJD6Dyhkuf0Q==/cz.procyon.kmp-d8jdsrz5V2CUvCgPptHrYw==/base.dm': No such file or directory
2024-05-30 16:45:08.160  8330-8330  nativeloader            cz.procyon.kmp                       D  Configuring clns-6 for other apk /data/app/~~SDxJRZhIeCcJD6Dyhkuf0Q==/cz.procyon.kmp-d8jdsrz5V2CUvCgPptHrYw==/base.apk. target_sdk_version=34, uses_libraries=, library_path=/data/app/~~SDxJRZhIeCcJD6Dyhkuf0Q==/cz.procyon.kmp-d8jdsrz5V2CUvCgPptHrYw==/lib/x86_64:/data/app/~~SDxJRZhIeCcJD6Dyhkuf0Q==/cz.procyon.kmp-d8jdsrz5V2CUvCgPptHrYw==/base.apk!/lib/x86_64, permitted_path=/data:/mnt/expand:/data/user/0/cz.procyon.kmp
2024-05-30 16:45:08.182  8330-8330  GraphicsEnvironment     cz.procyon.kmp                       V  Currently set values for:
2024-05-30 16:45:08.182  8330-8330  GraphicsEnvironment     cz.procyon.kmp                       V    angle_gl_driver_selection_pkgs=[]
2024-05-30 16:45:08.182  8330-8330  GraphicsEnvironment     cz.procyon.kmp                       V    angle_gl_driver_selection_values=[]
2024-05-30 16:45:08.186  8330-8330  GraphicsEnvironment     cz.procyon.kmp                       V  ANGLE GameManagerService for cz.procyon.kmp: false
2024-05-30 16:45:08.186  8330-8330  GraphicsEnvironment     cz.procyon.kmp                       V  cz.procyon.kmp is not listed in per-application setting
2024-05-30 16:45:08.186  8330-8330  GraphicsEnvironment     cz.procyon.kmp                       V  Neither updatable production driver nor prerelease driver is supported.
2024-05-30 16:45:08.233  8330-8351  libEGL                  cz.procyon.kmp                       D  loaded /vendor/lib64/egl/libEGL_emulation.so
2024-05-30 16:45:08.236  8330-8351  libEGL                  cz.procyon.kmp                       D  loaded /vendor/lib64/egl/libGLESv1_CM_emulation.so
2024-05-30 16:45:08.247  8330-8351  libEGL                  cz.procyon.kmp                       D  loaded /vendor/lib64/egl/libGLESv2_emulation.so
2024-05-30 16:45:08.333  8330-8330  Compatibil...geReporter cz.procyon.kmp                       D  Compat change id reported: 237531167; UID 10187; state: DISABLED
2024-05-30 16:45:08.343  8330-8330  OpenGLRenderer          cz.procyon.kmp                       W  Unknown dataspace 0
2024-05-30 16:45:08.658  8330-8330  System.out              cz.procyon.kmp                       I  🍄 Permission failed
2024-05-30 16:45:08.766  8330-8349  OpenGLRenderer          cz.procyon.kmp                       W  Failed to initialize 101010-2 format, error = EGL_SUCCESS
2024-05-30 16:45:08.795  8330-8349  Gralloc4                cz.procyon.kmp                       I  mapper 4.x is not supported
2024-05-30 16:45:09.248  8330-8345  OpenGLRenderer          cz.procyon.kmp                       I  Davey! duration=982ms; Flags=1, FrameTimelineVsyncId=96529, IntendedVsync=5686048911655, Vsync=5686165578317, InputEventId=0, HandleInputStart=5686177177359, AnimationStart=5686177183710, PerformTraversalsStart=5686178370408, DrawStart=5686667056478, FrameDeadline=5686065578321, FrameInterval=5686173312767, FrameStartTime=16666666, SyncQueued=5686676904907, SyncStart=5686682970359, IssueDrawCommandsStart=5686683708793, SwapBuffers=5686859062983, FrameCompleted=5687037730169, DequeueBufferDuration=3487, QueueBufferDuration=757463, GpuCompleted=5686859062983, SwapBuffersCompleted=5687037730169, DisplayPresentTime=0, CommandSubmissionCompleted=5686859062983,
2024-05-30 16:45:09.257  8330-8330  Choreographer           cz.procyon.kmp                       I  Skipped 49 frames!  The application may be doing too much work on its main thread.
2024-05-30 16:45:13.410  8330-8360  ProfileInstaller        cz.procyon.kmp                       D  Installing profile for cz.procyon.kmp


Costs: allow user to switch year

Description
User (NH) would like to be able to select which year to show costs for (currently just defaults to the latest available).
Resourcing
We intend to contribute this feature


RUSTSEC-2022-0046 - Out-of-bounds read when opening multiple column families with TTL

Affects rocksdb < 0.19.0
See https://rustsec.org/advisories/RUSTSEC-2022-0046

We have been periodically updating the rocksdb crate and now use RocksDB 8.3.2.


Firebase Sign In with KMM Is Taking Forever On Emulator

I'm trying to build a PoC using your library but the Firebase sign in request is taking 4 minutes to complete on my end. Anyone else having these issues when building a KMM project?
I've used the following code:
commonMain/CoroutineViewModel.kt
expect abstract class CoroutineViewModel() {

    val coroutineScope: CoroutineScope

    fun dispose()

    protected open fun onCleared()
}

commonMain/LoginViewModel.kt
class LoginViewModel : CoroutineViewModel() {

    private val _loginState: MutableStateFlow<LoginState> = MutableStateFlow(LoginState.Initial)
    val loginState = _loginState.asStateFlow()

    private var firebaseAuth: FirebaseAuth = Firebase.auth

    fun login(
        email: String,
        password: String
    ) {
        _loginState.value = LoginState.Loading

        coroutineScope.launch {
            _loginState.value = try {
                val authResult = firebaseAuth.signInWithEmailAndPassword(
                    email = email,
                    password = password
                )
                when (authResult.user) {
                    null -> LoginState.Error("No user with these credentials")
                    else -> LoginState.Success(authResult)
                }
            } catch (e: Exception) {
                LoginState.Error(e.message.orEmpty())
            }
        }
    }
}

sealed class LoginState {
    object Initial : LoginState()
    object Loading : LoginState()
    data class Success(val authResult: AuthResult?) : LoginState()
    data class Error(val message: String) : LoginState()
}

Could somebody please help point me in the right direction regarding how to solve this issue? Thanks :)
Note -- This is only happening for the first time I'm trying to sign in. The other requests finish in 1ms

@rand0md3v1 I've had the same Problem, as well as others. Here they seem to have solved it by downgrading the emulator. I've recently updated the emulator to 32.1.2, which has resolved this issue for me.
I think this issue can be closed, as it does not seem to be an issue with this library.


Updated versions of some gems

First of all thank you for your gem, it works perfect and has helped me a lot to integrate Typekit in a couple of hours.
I made this fork due to a conflict in the version number of HTTParty with another gem that I have installed in my project.
I have changed to version 0.8.0 and everything seems to work fine.
Well I have also updated the version of bundler. 1.1.rc is pretty fast!

Thanks for the patch, and I'm glad that this Gem helped you out!


I made changes to README file

sup, i made a change to the read me file to add further instructions.

LGTM!


Fix chunk length when creating new ID3 for AIFF files

Hello, if you have an AIFF file, which doesn't have an ID3 chunk, creating new one affects the stream_position() of writer inside src/chunk.rs:115. If the ID3 tag is already present, the writer is empty, but if new tag is created, it will have the 8 bytes of chunk header + length, which causes the ID3 chunk to have invalid length. I've added a simple fix, which subtracts that value. Tested in foobar2000.
Thanks

Thanks!


Don't show notification if app is in focus

If app is open and in focus, a notification should not be displayed.

Why do you think so? I think current behavior follows that of web browsers.

I think the behavior should follow that of desktop applications ;) Skype won't show notifications if you're on the app (it does show the username in bold, with unread messages).

Can this be reconsidered? I am not a fan of this behaviour either. Notifications are intrusive/distracting and are meant to draw your attention to them. If you have the window focused, what's the point? This is how the HipChat app behaves for example, no notification when the window has focus.

First, I want notifications always even if the window is focused. At least this behavior should be optional.
By the way, in this case, I can understand the reason for the active tab. But how should unfocused tabs work?

Optional is always good.
In skype, you get the new message sound (configurable), the person name changes font (bold a different color), but the notification popup does not show up. I think it's good like that.

Maybe show notifications for other channels?

Also, maybe part of this issue, you get thousand of notifications on your mobile device, if you having a private chat with someone on desktop. Also the mobile notifications won't be cleared when the messages are read on any other device, causing your notification area on mobile to be filled with already read notifications.

Likely mobile app specific.

Thanks @timroes! Mattermost provides an option to configure which types of messages should send a push notification on mobile. You can find this setting in Main Menu > Account Settings > Notifications > Mobile push notifications.
As for your second piece of feedback, Mattermost currently doesn't support clearing push notifications on mobile notification area after they've been read on web or the desktop app.
If you'd like to suggest it as a feature idea, I encourage you to submit your idea to the Feature Idea forums so it can be discussed, upvoted and prioritized by the Mattermost team.

A pull request has been submitted on the server side, which will disable notifications when actively viewing a channel https://github.com/mattermost/platform/pull/4216 - I believe this will partially cover the suggested improvement.
If there are further suggestions, I encourage you to submit the idea to the Feature Idea forums so it can be discussed, upvoted and prioritized by the community.


Edge: session storage not persisting during localhost redirect login

Description
Hi, I encountered a very specific issue trying to do a redirect login in Edge running on localhost. It appears Edge isn't persisting the session storage on localhost. I know Edge does some stuff to localhost for the sake of security (i.e. Allow localhost loopback). Not sure if there's an Edge configuration to address this. This is working perfectly fine on a deployed server.
I traced this issue back to 2.10.2 #236 fd0a995. The localhost redirect login in Edge works in 2.10.1.
Some of the salte-auth storage properties always get set to 'session' even if 'local' is passed as the storageType. If I manually change all properties to store to 'local', the login works and local storage looks fine.
Expected outcome
salte.auth session storage properties should be persisted following a redirect login on localhost
Actual outcome
salte.auth session storage properties are missing following a redirect login on localhost
Steps to reproduce

Use salte-auth version greater than 2.10.1
Run app on localhost using MS Edge browser
ws02 provider, 'id_token token' response type, redirect login, storageType 'local' or 'session'

Note: have not tested IE. The app I'm running currently doesn't run in IE
Browsers Affected

[ ] Chrome
[ ] Firefox
[ ] Safari 11
[ ] Safari 10
[ ] Safari 9
[ ] Safari 8
[ ] Safari 7
[x] Edge
[ ] IE 11
[ ] IE 10

Hey Phil,
The level of information you've provided is absolutely stellar.
I believe the reason we always save the validation parameters to sessionStorage is due to IE 11. https://github.com/salte-auth/salte-auth/issues/168
I'll have to look at this later tonight when I get the chance.

I'm unable to reproduce this using Edge 18, 17, or 16.
What version of Edge are you using?

Edge: 41.16299.492.0
EdgeHTML: 16.16299
If I manually add a property to session storage (i.e. test: 'value'), the value persists if I reload the page (no redirect). The property is lost when I do a login redirect.
I wonder if this issue relates to this: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/13861050/

Possibly, at the very least it would explain why I can't reproduce in Sauce Labs with Auth0.
Sauce Labs Manual Test (skip to 3:22)

I confirmed IE11 works in the same scenario where Edge isn't using the latest version

@nick-woodward The ADAL (another oauth library) posts an article about this known issue about session storage lost. Known issues in Edge.
If the redirection happens between 2 "security zones", then the session storage will be lost. As the article mentioned, one prerequisite to repro this issue is that the the provider URL and the redirectUrl needs to be in 2 different security zones. You can achieve that by removing these URLs from the trusted site (see herefor details).

Hey @zhenchaoni thanks for the extra information!
I'll try to reproduce this tonight and get back to everyone here.


Switch version in version.go to 'dev'

Signed-off-by: Nathan LeClaire<EMAIL_ADDRESS>

this should be sufficient since the release script will always replace this with the proper version
LGTM


Problems with assets

How should I use svg files or images in my components when i store them in client/assets/images/?
If I use path like this /assets/some-image.png in development env it works. But in production env this image has e-tag postfix /assets/some-image-5dd021956efcd611492a65f2a05fb24a2c304d98ec00ecae3a7f17e48da10652.png and it doesn't work because i have /assets/some-image.png path in my component .
How can I solve this problem without rails helpers = assets_path() and .jsx.erb?
I'm using react_on_rails v.4.

@justin808 could you help me?

@evgenTraytyak are you trying to use webpack to build your CSS or Rails.
It's much simpler to just let Rails handle your CSS.
Otherwise, you can use CSS modules and follow the recipe here: https://github.com/shakacode/react-webpack-rails-tutorial/.
The reason you're seeing the problem with fingerprinting is that you're not using only the rails asset pipeline.
Please keep in mind that ReactOnRails has no direct connection with CSS assets, other than we support webpack and you can use webpack to build your CSS assets for Rails.
We should probably close this issue.

@evgenTraytyak @justin808 I faced with the same problem. I need to use right images paths from jsx in <img src="..." />  and in javascript for src dynamic changing on the page.
I used tutorial https://github.com/shakacode/react-webpack-rails-tutorial/ and everything works perfect in development until I deployed the code to heroku. We are using rails asset pipelines and all images was collected in public/assets/image-5dd0219..........52.jpg. I found it's required to convert original image name to the hashed name on production and added script
// app/assets/javascripts/assets_images.js.erb
<%
imgs = {}
Dir.chdir("#{Rails.root}/app/assets/images/") do
  imgs = Dir.glob("**/*").inject({}) {|h,f| h.merge! f => asset_path(f)}
end
%>

window.imagePath = function(name) {
  return <%= imgs.to_json %>[name]
}

and required it in app/assets/javascripts/application_non_webpack.js
//= require assets_images

Then I start to use wrapper imagePath('image.jpg') everywhere and it make things works better: client rendering starts working as expected, but server rendering shows me error:
[Error] [SERVER] Exception in rendering!
	global code (xxx.herokuapp.com:117)
[Error] [SERVER] message: imagePath is not defined
	global code (xxx.herokuapp.com:118)
[Error] [SERVER] stack: ReferenceError: imagePath is not defined
    at RadiumEnhancer.render (<eval>:40131:58)
    at RadiumEnhancer.render (<eval>:36793:66)
    at ReactCompositeComponentMixin._renderValidatedComponentWithoutOwnerOrContext (<eval>:16344:35)
    at ReactCompositeComponentMixin._renderValidatedComponent (<eval>:16364:33)
    at ReactCompositeComponentMixin.mountComponent (<eval>:15977:31)
    at Object.ReactReconciler.mountComponent (<eval>:14295:36)
    at ReactDOMComponent.ReactMultiChild.Mixin.mountChildren (<eval>:22839:45)
    at ReactDOMComponent.Mixin._createContentMarkup (<eval>:20022:33)
    at ReactDOMComponent.Mixin.mountComponent (<eval>:19910:30)
    at Object.ReactReconciler.mountComponent (<eval>:14295:36)
	global code (xxx.herokuapp.com:119)

I'm still searching solution how to make function imagePath accessible during server rendering. Perhaps register it somehow in serverRegistration.jsx? I tried, but without success, @justin808 do you have any suggestions?

Solved this issue very simple - just put images to public folder and fingerprinting is not worrying me for assets images

@evgenTraytyak @ramusus Have a look at PR#413 we're about to merge. I think it will solve your problems.

@justin808 suggest we close as @alleycat-at-git fixed this in #413


[Question] timestamps in different zones

During a talk at Devoxx 2016 in Poland by Marcin Grzejszczak a question was asked if the timestamps are derived from the server time or a global time because there would be some problems if it is done with the server time and the servers are located in different time zones.
It was suggested to use a tool for synchronizing the time from which the timestamps are derived and it was also said that such a feature would be implemented.
I couldn´t find an issue relating to that topic so I´d like to know if something like this is already implemented or if it is still on the todo list or if there is a workaround.

An issue is still there - https://github.com/spring-cloud/spring-cloud-sleuth/issues/275 . The workaround (or actually good practice) is to use NTP (https://en.wikipedia.org/wiki/Network_Time_Protocol) but I'm no expert on this topic. Maybe @wybczu can elaborate more on this?

UNIX timestamp is defined as the number of seconds (or milliseconds) that have passed since the beginning of 1 January 1970, 00:00:00 UTC so it is timezone independent. However I would recommend using one timezone across your fleet, e.g. UTC. It will save you a lot of hassle with time calculations :)
As @marcingrzejszczak wrote, clock synchronization across your servers is a good practice or even a requirement in this case (not timezone specific) as you need to order events based on timestamps.

thank you for that information

No problem. Thanks @wybczu !


Not saving form collection

Status
READY
JIRA Ticket
SPACON-592
Description
Fixed bug and added form submission tests using server endpoint
Todos

[ ] Tests
[ ] Documentation
[ ] License

Steps to Test or Reproduce
Outline the steps to test or reproduce the PR here.
git fetch --all
git checkout <feature_branch>
./gradlew connectedCheck

@boundlessgeo/spatial-connect

👍


Adding example programs

Codecov Report

Merging #16 (c8dfdee) into main (72b6d45) will decrease coverage by 0.99%.
The diff coverage is 86.04%.

@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
- Coverage   86.35%   85.37%   -0.99%
==========================================
  Files           4        4
  Lines         425      417       -8
  Branches      116      117       +1
==========================================
- Hits          367      356      -11
- Misses          7        9       +2
- Partials       51       52       +1

Flag
Coverage Δ

unittests
85.37% <86.04%> (-0.99%)
:arrow_down:

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

Impacted Files
Coverage Δ

lib/public/task_pool/traits.h
86.95% <0.00%> (-8.29%)
:arrow_down:

lib/task_pool.cpp
100.00% <ø> (ø)

lib/public/task_pool/pool.h
84.61% <87.34%> (-0.66%)
:arrow_down:

lib/public/task_pool/pipes.h
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Write-permission warning when everything is ok

When i run script i got write-permission warning even everything is ok and:

i run it as administrator
in folder when everyting have permission to write

I do test from UI and got that result

Could you restart the script and then, when the error appears, double click the L icon in the system-tray and take a screenshot of the bottom of the AHK-log?

Apparently, it cannot create img\Recognition (XXXXp). Could you double-check if that folder is really missing inside the img-folder? XXXX is your screen resolution, e.g. 1080

There is only GUI folder.
Also download las release instead of copy github repository and same situationm here is folder tree

There seem to be issues with creating folders deeper inside the folder structure. It had no problems creating the cheat-sheets, exports, ini, and update folders. But the write-test also creates files and folders inside data\write-test, so I don't really know why it cannot create the recognition folder.
You could try creating the recognition (XXXXp) folder inside img manually and see if it then can create folders inside it. Otherwise, you'll have to also manually create a GUI and Betrayal folder inside there. Another thing you could try is moving the folder outside of your C-drive.

Maybe script cannot recognise my screen resolution because i have two monitor setup, and didnt make correct folder?

No, you can't get that far into the tool if it can't recognize your resolution (there are certain unsupported ones, so the check has to pass). The folder check happens basically at the very end. Maybe Windows doesn't like the folder name or sees a specific pattern and then blocks it.
Glad it worked out in the end. For the next version, I'll also include in the error-message which folders cannot be accessed/created so it'll be easier to report and get support.

:) this is not the end of problems, i try to use Betrayal info i can open menu using mButton but it cannot recognise members when mouse over, like in wiki


GSM8K few-shot sampling from test set?

Excellent work! However, in your paper page 19, Appendix D, you show automatically constructed demonstrations for GSM8K. However, I  find that these 8 cases are from test.jsonl but not train.jsonl. Is there a data leak problem?

Hi, there would not be a data leak problem because no gold label is used. We only collect questions for automatic rationale generation.


How to do units.NumberMultiplier * float operator?

General Question

When users want to use 2048Mi memory, for example, and we set resources.memroy.limits = 2048Mi, but set resources.memroy.requests = 2048Mi * (a float ratio).
import units
import base.pkg.kusion_models.kube.frontend.resource

a: units.NumberMultiplier = 2048Mi
ratio: float = 0.01

res: resource.Resource = {
    cpu = 1
    memory = a * ratio  # error: unsupport
    #memory = units.to_Mi(float(int(a)) * ratio) # error: type == str
}

@Peefy @chai2010

@LeoLiuYan
In KCL, numeric units exist as a special type, which does not allow four arithmetic operations, because str(1024Mi) == "1024Mi" can be written directly, but when they are calculated and then use the str function, KCL compiles I don't know what unit to take.
Therefore, If you really want to support resource assignment as a string type, you can directly extend the definition of Resource as follows:
import units

type Unit = units.NumberMultiplier

schema Resource:
    cpu?: int | Unit = 1
    memory?: str | Unit = 1024Mi
    disk?: str | Unit = 10Gi

Where, the type of memory is str | Unit

@Peefy
OK.  But this is a common operation when set the value of resources.limits and resources.requests,  will the KCL to support a easy way to do this operation.

OK. But this is a common operation when set the value of resources.limits and resources.requests, will the KCL to support a easy way to do this operation.

Got it. We'll consider an easier way to deal with resource.

However, we can convert the numeric unit literal value into an integer through the int() function, and then call the functions in the units package or spliced into the corresponding unit string.

import units
import math

a: units.NumberMultiplier = 2048Mi
ratio: float = 0.3
cpu: int | str = 1

res = {
    cpu = str(int(int(cpu) * ratio * 1000)) + "m"
    memory = units.to_Mi(int(int(a) * ratio))
}

@LeoLiuYan

@LeoLiuYan In KCL, numeric units exist as a special type, which does not allow arithmetic operations, because str(1024Mi) == "1024Mi" can be written directly, but when they are calculated and then use the str function, KCL compiler don't know what unit to take.
Therefore, If you really want to support resource assignment as a string type, you can directly extend the definition of Resource as follows:
import units

type Unit = units.NumberMultiplier

schema Resource:
    cpu?: int | Unit = 1
    memory?: str | Unit = 1024Mi
    disk?: str | Unit = 10Gi

Where, the type of memory is str | Unit

In addition, it is not complete to only support the operation of numerical unit types and integers. For addition, 1Mi + 1Ki is ambiguous, and the calculation result unit is uncertain.


Add support for setting hyperlink display & tooltip

PR Details
Description
Adds a new struct, HyperlinkOpts, that can be optionally passed to SetCellHyperlink to set the display or tooltip value of the hyperlink. This adds tooltip functionality, and adds the ability to set the display value for a hyperlink in Google Sheets.
Related Issue
#790
Motivation and Context
Excel uses the cell value as the display value of a hyperlink, but Google Sheets relies on display being set correctly to set the display text. While Excel doesn't care about this value, it does correctly set it in the XML on save. Exposing the display attribute allows us to import excelize-generated spreadsheets into Google Sheets without breaking the link text of hyperlinks.
For completeness, I also added support for setting a Tooltip using the same HyperlinkOpts struct.
How Has This Been Tested
I tested a simple case in Excel & Google Sheets:
locText := "location"
f.SetCellStr("Sheet1", "A1", "Location link text")
f.SetCellHyperLink(
	"Sheet1",
	"A1",
	"Sheet1!A5",
	"Location",
	excelize.HyperlinkOpts{Display: &locText, Tooltip: &locText},
)

In Excel, the current display behaviour remains (cell value is Location link text) and the tooltip text is location.
In Google Sheets, the cell value appears as location instead of falling back to the link location (e.g. #gid=2039701591&range=A5) and the tooltip is ignored (not supported in Sheets).
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

LGTM, thanks @jrdallen97.


kibana IndexPattern disable project uid

The tribes feature allows a tribe node to act as a federated client across multiple clusters.
The general network topology is as follows:

We have Multiple openshift-elasticsearch clusters.
We want to query app logger in any one kibana. The network topology is as follows.

We have the same project on multiple clusters,but the same project don't have the same uid.
kibana IndexPattern format is as the project.project_name.project_UID.*
Project X on cluster Y the kibana IndexPattern look like this project.X.87654321-4f9f-11e9-91cd-000c29052923.* .
Project X on cluster Z the kibana IndexPattern look like this project.X.12345678-1234-1234-1234-000c29052923.* .
If we use project.X.* as the IndexPattern, we can query project X's logs in all cluster through tribenode. So, I think we need a configuration to decide whether to disable the project UID on kibana IndexPattern .We have do some work for this
If we don't do this, we should sync all project info from one openshift cluster to other cluster in this plugin. we don’t think is a good idea.
Any Suggestions?  Thank you

If we use project.X.* as the IndexPattern, we can query project X's logs in all cluster through tribenode.

How do you know that all users in project X in cluster A can view all of the logs in project X in cluster B?

We built the above system architecture.
The system information is as follows:
OpenShift Master:v3.11.0+cca69c5-73
Kubernetes Master:v1.11.0+d4cacc0
OpenShift Web Console:v3.11.0+ea42280
elasticsearch:origin-logging-elasticsearch5:v3.11.0
Kibana:origin-logging-kibana5:v3.11.0

The tribe node also use origin-logging-elasticsearch5:v3.11.0.
We sync the Secrets "logging-curator"、"logging-elasticsearch"、"logging-fluentd"、"logging-kibana" from Cluster A to Cluster B.
We create the same project X and the same user A1 in Cluster A and Cluster B.
After that，Our user can query app logs on kibana through tribenode.

result from cluster A

result from cluster B
The kibana Indexpattern is auto create by openshift-elasticsearch-plugin.
So,  we want to kibana Indexpattern can disable the project UID in openshift-elasticsearch-plugin.
@richm  we have post a patch on our branch. please review.

This UUID was introduced into the index pattern because there were cases where searches would match both a live project and deleted project as represented in ES.  There is no way to guarantee a user had access to the logs from the deleted namespace and the query result would return 403 leaving a confused user.  One way you could resolve your particular issue is to introduce configuration and a strategy to control the index pattern creation behavior.  Ref: https://github.com/fabric8io/openshift-elasticsearch-plugin/blob/master/src/main/java/io/fabric8/elasticsearch/plugin/kibana/KibanaUtils.java#L110

@richm @jcantrill
I have post a pr #178
I do some test on our cluster.

First Step:
The user has permissions for project X and project Y.
Show on the kibana like as follows:

Second Step:
If we remove the user's permissions for  project Y  through openshift.
Show on the kibana like as follows:

We also make a strategy to control RolesSync into seachguard :ProjectRolesSyncStrategy and UserRolesSyncStrategy

I think the path you are going down is making it more complicated by adding conditionals where not needed.  This https://github.com/fabric8io/openshift-elasticsearch-plugin/blob/master/src/main/java/io/fabric8/elasticsearch/plugin/kibana/KibanaUtils.java#L110 file controls the formatting.  Why not inject a strategy for formatting the pattern into the util which is already used else where?  Our default scenario is unlikely to use this feature so I would propose to seed the patterns as project.logan.* and skip the ones with UID all together


Istio proxy blocks traffic for stateful application with headless service

Bug Description
Hi, I am running two stateful applications in my cluster: zookeeper and solr. Solr service is a headless service with a selector. Traffic for Zookeeper works fine. However, request for solr fails with a 404 and NR. The request from solr is as pod.service. For testing requests, exec into solr-0 container then make request http://solr-1.solr-svc:8983/<some_path>.
Version
client version: 1.11.3
control plane version: 1.11.3
data plane version: 1.11.3

Additional Information
No response

@howardjohn this is the config_dump for solr-0 config_dump.json.zip

That seems ... odd? There is nothing about solr-1 or zookeeper there at all. A full istioctl bug-report may be useful to capture more info about your config

Ok this is interesting. I see a lot of Info [IST0118], could this issue be related to https://github.com/istio/istio/issues/35429?
bug-report.zip

Hi @linsun, we just tested by naming it as  [-], and it does fix the issue. Headless services faces a similar issue as ExternalNames


Undertow 1.2.6.Final

Windows Build 1367 is now running using a merge of 5d03406c39b9c95032aebd4778aa32239ab44096

Core - Full Integration Build 962 is now running using a merge of 5d03406c39b9c95032aebd4778aa32239ab44096

Linux Build 1813 is now running using a merge of 5d03406c39b9c95032aebd4778aa32239ab44096

Windows Build 1367 outcome was SUCCESS using a merge of 5d03406c39b9c95032aebd4778aa32239ab44096
Summary: Tests passed: 3105, ignored: 69 Build time: 0:21:38

Linux Build 1813 outcome was SUCCESS using a merge of 5d03406c39b9c95032aebd4778aa32239ab44096
Summary: Tests passed: 3105, ignored: 69 Build time: 0:23:53

Core - Full Integration Build 962 outcome was FAILURE using a merge of 5d03406c39b9c95032aebd4778aa32239ab44096
Summary: Tests failed: 1 (1 new), passed: 2843, ignored: 375, muted: 1 Build time: 0:52:00
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).failoverOnStop: <no details avaliable>


Tidied tests and grunt file

Thanks for this, but I would prefer not to change all of the code to conform to your own, personal preferred convention. Sorry :cry:


[Vitss JDBC] Changes to create context object while executing query

This change is

Reviewed 1 of 4 files at r1.
Review status: 1 of 4 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

java/jdbc/src/main/java/com/flipkart/vitess/jdbc/VitessConnection.java, line 875 [r1] (raw file):
Move this method out of context and place in Utility class as this is required by other classes to create context.

java/jdbc/src/main/java/com/flipkart/vitess/jdbc/VitessStatement.java, line 305 [r1] (raw file):
integer limit can exceed. Change back queryTimeoutInMillis to long type

Comments from the review on Reviewable.io

Review status: 1 of 4 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

java/jdbc/src/main/java/com/flipkart/vitess/jdbc/VitessConnection.java, line 875 [r1] (raw file):
Planning to modify this method with callerID, which will going access vitessConnection  properties.

java/jdbc/src/main/java/com/flipkart/vitess/jdbc/VitessStatement.java, line 305 [r1] (raw file):
Incorporated comment and pushed with commit :  https://github.com/youtube/vitess/commit/90789d60515eef6d619510e7af1de16b79c0df85

Comments from the review on Reviewable.io

Reviewed 3 of 4 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from the review on Reviewable.io


Multiple Constraint Violations in Time-Series Data Submodel

I encountered several constraint violations when attempting to open the Time-Series Data Submodel template:

The dataSpecification mandatory attribute is missing in multiple embeddedDataSpecifications.
Several shortNames of dataSpecificationIec61360 exceed the length limit of 18 characters.
Some mandatory shortNames of dataSpecificationIec61360 are not set.

@zrgt Please use the latest JSON file of the respective SMT which as been uploaded yesterday

@Rudra-sandeep the JSON has still problems:

Properties with different valueTypes have a value='' which is not None, it is string. In cases where valueType is not string it causes errors.
Now:

                {
                  "category": "VARIABLE",
                  "idShort": "RecordCount",
                  "semanticId": {
                    "type": "ExternalReference",
                    "keys": [
                      {
                        "type": "GlobalReference",
                        "value": "https://admin-shell.io/idta/TimeSeries/Segment/RecordCount/1/1"
                      }
                    ]
                  },
                  "qualifiers": [
                    {
                      "type": "Cardinality",
                      "valueType": "xs:string",
                      "value": "ZeroToOne"
                    }
                  ],
                  "valueType": "xs:long",
                  "value": "",
                  "modelType": "Property"
                }

Should be:
                {
                  "category": "VARIABLE",
                  "idShort": "RecordCount",
                  "semanticId": {
                    "type": "ExternalReference",
                    "keys": [
                      {
                        "type": "GlobalReference",
                        "value": "https://admin-shell.io/idta/TimeSeries/Segment/RecordCount/1/1"
                      }
                    ]
                  },
                  "qualifiers": [
                    {
                      "type": "Cardinality",
                      "valueType": "xs:string",
                      "value": "ZeroToOne"
                    }
                  ],
                  "valueType": "xs:long",
                  "modelType": "Property"
                }

Also in cases where valueType is string and value is not set the value key should be just removed from property object.
File object also has an empty string as a value: "value": "". This also should be removed.

Tested with https://github.com/rwth-iat/aas-compliance-tool

The problem also occures in Range object, as it has min and max values which should be removed or set to valid XSD datetime string
{
                "idShort": "Timespan",
                "description": [
                  {
                    "language": "en",
                    "text": "The valueType of the given timespan must match the valueType of the time properties of the segments."
                  }
                ],
                "semanticId": {
                  "type": "ExternalReference",
                  "keys": [
                    {
                      "type": "GlobalReference",
                      "value": "https://admin-shell.io/idta/TimeSeries/Timespan/1/1"
                    }
                  ]
                },
                "valueType": "xs:dateTime",
                "min": "",
                "max": "",
                "modelType": "Range"
              }
´´´

Also a problem in ExternalReference in semantiid of segments. According to Constraint AASd-122 the type of the first key of an ExternalReference must be a GenericGloballyIdentifiable, but "Property" was set:
            {
              "value": {
                "idShort": "Segments",
                "semanticId": {
                  "type": "ExternalReference",
                  "keys": [
                    {
                      "type": "Property",
                      "value": "https://admin-shell.io/idta/TimeSeries/AggregationMethod/1/1"
                    }
                  ]
                },
                "modelType": "SubmodelElementCollection"
              }
            }

@zrgt Thank you for your feedback I will look into this issues.

@Rudra-sandeep the same problems mentioned in the original issue report also appear in JSON.

@zrgt Thank you for your feedback, I will look into this issue.

@Rudra-sandeep Please consider that probably all issues mentioned in this problem also exist in all JSON files that have been uploaded recently.

@zrgt Thank you for your feedback, I will look into this issue.

@Rudra-sandeep Please consider that probably all issues mentioned in this problem also exist in all JSON files that have been uploaded recently and the Serializer/SDK you are using is not compliant with the AAS Spec.

@zrgt Yes regarding to compliant with the Spec we have already started discussions in the WG's

@zrgt Thank you for raising the issue and the issue is been solved you can find the Bugfixed SMT at below link
[https://github.com/admin-shell-io/submodel-templates]


Update CherryPy SSL to use latest API and work on Py3

On Py2, the ssl_certificate and ssl_private_key attributes are deprecated, and on Py3 they don't exist at all!
This PR just updates the code to use BottlePy's recommended ssl_adapter method, fixing it for Python3.
That said, I haven't actually been able to get this to work with Py2. Neither this nor the previous version work on Python2 for me, and they both result in a non-ssl server, but I suspect that's a CherryPy issue with my particular environment. Mind trying this out with a Py2 server on your own box before pulling it? I've got some test server code here

I've been able to get ssl with CherryPy and bottle on Python 2.7.x. I'm not sure why, but I've needed to use CherryPy's BuiltinSSLAdapter (meaning Python's builtin ssl module as opposed to PyOpenSSL [which I don't mind since the Python 2.7.9 update]). The following code creates an ssl server using bottle and CherryPy:
import bottle

app = bottle.Bottle(__name__)

@app.route("/")
def index():
    return "You are seeing this over https."

if __name__ == "__main__":
    from cherrypy.wsgiserver import CherryPyWSGIServer
    from cherrypy.wsgiserver.ssl_builtin import BuiltinSSLAdapter

    CherryPyWSGIServer.ssl_adapter = BuiltinSSLAdapter(
        'cert.pem',
        'privkey.pem',
        None)

    app.run(server="cherrypy")

I'm not sure if this will help with your PR and I don't know if this works in Python 3, but I thought I would provide it anyway.
Please Note that there is a bug in CherryPy (I'm not sure about the affected versions) that reports "http" on the CLI when starting the server, but it does serve over https.

I just had this problem, and had to work out if it was a CherryPy or Bottle problem or both. It seems that the latest CherryPy (3.8.0) will happily ignore the ssl_certificate and ssl_private_key members (I don't know if using CPWSGIServer instead of CherryPyWSGIServer would help?). I fixed it in a similar way to iLoveTux.
As a more general question, is SSL actually supported by Bottle? This has been an open pull request  with no comments from the bottle maintainers for over 7 months. If it's not supported why not remove the cherrypy SSL arguments?


HWKALERTS-182 Update swagger doc

HKWALERTS-184 Wrap deleted number response in a json
A necessary update on the swagger doc.
Now data types are covered and API operations reviewed.
Unified some style as readers of swaggers are REST API users (non Java users).
Fixing minor non-json types for consistency.
Several tricks on the asciidoc templates as swagger has some limitations for Java types or free text.

Thanks for the review.


Add menu to deploy.md

Signed-off-by: Hang Yan<EMAIL_ADDRESS>

cc @moxiegirl

@hangyan Thank you for the contribution.  This menu displays to the left of the page already tho. Are you not seeing it in your browser?

@hangyan Thank you for the contribution! Unfortunately, we already have a TOC system.


[Breaking Change]: Replace babel-istanbul-plugin and replace it by a webpack loader

Closes https://github.com/storybookjs/addon-coverage/issues/29
Closes https://github.com/storybookjs/addon-coverage/issues/17
Closes https://github.com/storybookjs/addon-coverage/issues/21
Closes https://github.com/storybookjs/addon-coverage/issues/25
What Changed
The babel-istanbul-plugin was replaced by a custom webpack loader to enable support for all Webpack5 projects, independently, whether they are using Babel as a compiler or another solution, like SWC
Release Notes

[BREAKING CHANGE]: Dropping Storybook < 7 support
Replaced babel-istanbul-plugin with a custom Webpack loader to support coverage independently of the compiler used for Webpack5 projects. Before, the coverage addon only worked if Babel was used with Webpack5. Now, users might use other compilers like, for example, SWC.

📦 Published PR as canary version: 1.0.0-canary.27.12a4851.0

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

@kasperpeulen @yannbf I tested it with pnpm create vite (React -> TypeScript + SWC) and I´m not able to get the coverage correctly (#28)

how do I expect to run the coverage on the webpack5 example folder ?
I am getting following errors:

Test Suites: 3 failed, 3 total
Tests:       8 failed, 8 total
Snapshots:   0 total
Time:        1.416 s
Ran all test suites.
Coverage file (2 bytes) written to .nyc_output/coverage.json
----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------|---------|----------|---------|---------|-------------------
All files |       0 |        0 |       0 |       0 |
----------|---------|----------|---------|---------|-------------------

while yarn test-storybook works just fine
 PASS   browser: chromium  stories/Page.stories.tsx
 PASS   browser: chromium  stories/Button.stories.tsx
 PASS   browser: chromium  stories/Header.stories.tsx

Test Suites: 3 passed, 3 total
Tests:       8 passed, 8 total
Snapshots:   0 total
Time:        1.318 s


DataStore-like ORM

Which Category is your question related to?
DataStore / Lambdas
Amplify CLI Version
4.13.1
What AWS Services are you utilizing?
AppSync, DynamoDB, Lambda
Provide additional details e.g. code snippets
Is there any implementation or workaround to make the DataStore ORM API available on the backend (That would be without the actual data store and sync, using the API to talk directly to the DynamoDB)
If not, is it something to be considered or it's just out of the project scope?
Thanks.

Any interest?

@andrestone This is an interesting idea. It's a feature request that we'll look at in the future and measure community interest. If you want to work on it, you can maybe open up an RFC with ideas before starting implementation.


📕【认领】Solibrary 翻译任务认领说明

翻译任务认领说明

2024年9月10日新的翻译工程来了，https://8bit-1.gitbook.io/solibrary 是一个学习Solana的资料库，从不同的角度总结了Solana开发与使用的技术资料

注意：
一次尽量只认领一篇，给其他小伙伴留些机会~
认领开始前，请务必阅读翻译流程说明

从 Todo List 中选取未被人领取过的文章：
未被领取过：

[ ] Solana Documentation

领取过：

[ ] Solana Documentation(@Fankouzu)

领取过，已完成：

[x] Solana Documentation(@PigGoose ) #11

领取方式，在本 issues 下评论即可。
认领任务格式：
Section | Title | 译者 | 完成时间 | PR
-- | -- | -- | -- | --
Solana Clients| Rust | @PigGoose | 2021.08.06 - 2021.08.10 | -

示例效果：

Section
Title
译者
完成时间
PR

Solana Clients
Rust
@PigGoose
2021.08.06 - 2021.08.10
-

当完成时，请修改自己的认领评论，添加 PR 信息：

Section
Title
译者
完成时间
PR

Solana Clients
Rust
@PigGoose
2021.08.06 - 2021.08.10
#11

任务认领列表

注意：翻译后的文档文件名和官网文件名一致，文件放到https://github.com/Fankouzu/solana-basic-ui/tree/main/docs/SoLibrary 目录中

[ ] Solana @XingqiWang
[ ] The Meme Coin Problem and Solution
[ ] Developing on Solana
[ ] From Rust To Deployment
[ ] Solana Blockchain Explorer
[ ] Building a Solana dAPP
[ ] Deploying a Solana dApp
[ ] Deploying a Solana Memecoin using CLI
[ ] Solana Smart Contracts
[ ] Send Solana via javascript functions
[ ] Candy Machine
[ ] Pump fun APIs
[ ] Metaplex
[ ] Metaplex Program Library
[ ] Solana Program Library
[ ] UMI Framework
[ ] Umi and Web3js Differences
[ ] Fetching Accounts
[ ] UMI Helpers
[ ] HTTP Requests
[ ] Umi's Interfaces
[ ] Interface implementations
[ ] Kinobi
[ ] UMI Plugins
[ ] Registering Programs
[ ] Public keys and Signers
[ ] Connecting RPCS
[ ] Serializer
[ ] Storage
[ ] Transactions
[ ] Web 3.JS Adapters
[ ] Metaplex Umi Plugins
[ ] Core JS SDK v1.0
[ ] Local Validator
[ ] SolScriptions
[ ] FAQ
[ ] Initialize
[ ] Write Inscription Data
[ ] Fetch
[ ] Clear
[ ] Close
[ ] Authority
[ ] Sharding
[ ] Getting Started using JavaScript
[ ] Getting started using the Inscriptions CLI
[ ] Core Candy Machine
[ ] Getting Started using JavaScript
[ ] Candy Guard
[ ] Assets
[ ] Creating a Core Candy Machine
[ ] Inserting Items
[ ] Updating The Core Candy Machine
[ ] Guard Groups
[ ] Special Guard Instructions
[ ] Fetching a Core Candy Machine
[ ] Minting
[ ] Withdrawing a Core Candy Machine
[ ] Address Gate Guard
[ ] Allocation
[ ] Allowlist Guard
[ ] Asset Burn Guard
[ ] Asset Burn Multi
[ ] Asset Payment Guard
[ ] Asset Payment Multi
[ ] Asset Mint Limit
[ ] Bot Tax Guard
[ ] End Date Guard
[ ] Edition
[ ] Freeze Sol Payment guard
[ ] Freeze Token Payment Guard
[ ] Gatekeeper Guard
[ ] Mint Limit Guard
[ ] NFT Burn Guard
[ ] NFT Gate Guard
[ ] NFT Mint Limit Guard
[ ] NFT Payment Guard
[ ] Program Gate Guard
[ ] Redeemed Amount Guard
[ ] Sol Fixed Fee Guard
[ ] Sol Payment Guard
[ ] Start Date Guard
[ ] Third Party Signer Guard
[ ] Token Burn Guard
[ ] Token Gate Guard
[ ] Token Payment Guard
[ ] Token2022 Payment Guard
[ ] Generating Custom Guard Client for Core Candy Machine

Section
Title
译者
完成时间
PR

SoLibrary
Solana
@XingqiWang
2021.09.10 - 2021.09.15
-

Section
Title
译者
完成时间
PR

SoLibrary
Developing on Solana
@JustinMaDev
2024.11.15-2024.11.22
-


upgrade libunwind to 1.5

Scope & Purpose
Upgrade libunwind to 1.5.

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[x] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[x] No backports required

Testing & Verification

[x] This change is a trivial rework / code cleanup without any test coverage.

Link to Jenkins PR run:
http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13747/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13749/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/13749/

Tests blue

Tests blue


Redirect default vhost to simple index.html

Hi!
Let's say I run the nginx-proxy on main.domain.com.
I have enabled https for it also, using letsencrypt-nginx-proxy-companion.
How can I configure it so that when someone goes to http://main.domain.com it will just redirect to:
https://main.domain.com/index.html.
Currently I'm ending up in a loop.
When I manually edited conf.d/default.conf, removed lines below, then it worked perfectly:
       location / {
                proxy_pass http://fb7dgrdgdga733e074a1ab9ec0584acb155bb476c;
        }

Such a feature is usually not under the responsibility of the reverse-proxy (which nginx-proxy is) but under the responsibility of the web server that serves the files for that website.
If your webserver is apache, look at the DirectoryIndex directive. If your webserver is nginx, use the index directive.

That being said, if you really want to add rewrite rules into your reverse-proxy config, you still can do it by customizing the location {...} section of its config as explained at § Per-VIRTUAL_HOST location configuration of the README.md file:
On your docker host, create a file named main.domain.com_location:
rewrite ^/$ /index.html last;

and then add a the main.domain.com_location file as a volume on your nginx-proxy container:
docker run -d -p 80:80 -p 433:433 \
    -v /var/run/docker.sock:/tmp/docker.sock:ro \
    -v /somewhere/main.domain.com_location:/etc/nginx/vhost.d/main.domain.com_location:ro \
    jwilder/nginx-proxy

In the nextcloud example (https://github.com/nextcloud/docker/blob/master/.examples/docker-compose/with-nginx-proxy/mariadb-cron-redis/apache/docker-compose.yml) they bind the directory /usr/share/html to a volume html and by your reasoning, this is incorrect, do I understand correctly?


tools/old/mdflush.bt: fix BPFTRACE_HAVE_BTF macro

The correct macro to use is called BPFTRACE_HAVE_BTF, not __BPFTRACE_HAVE_BTF.

Checklist

[ ] Language changes are updated in man/adoc/bpftrace.adoc and if needed in docs/reference_guide.md
[x] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

wanted to merge it, figured I'd use the 'resolve conflict' button github gives me but I seem to have made it worse 😢 .

wanted to merge it, figured I'd use the 'resolve conflict' button github gives me but I seem to have made it worse cry .

Fixed, that button seems dangerous :worried:


previous link to Office compat matrix outdated

included the latest link. Please #signoff asap, to avoid confusion at customers and potentially wrong investment decisions in regard of EOS and support of Office 365 on Windows Server 2022 @v-dihans
Your link does not even include Windows Server 2022. TYVM Diana!

@Karl-WE   We're aware of this issue and a resolution is being worked on. Depending on how long that takes, we'll decide whether we need to temporarily update all URL references for the matrix to point to the English version (of Sept 2021) until the resolution is in place.

@DHB-MSFT Thanks for your reply and triage. Why do you think it is not a good idea to update this link to this one? It is often published. The only thing that is different there is no aka.ms or fwlink for this yet (as of I know).
As a Microsoft Partner It is important that this gets an update so we can plan and budget for changes with our customers for 2025. Thank you very much for elaborating the close.

@Karl-WE  We've gone ahead and temporarily changed the URL for the matrix in our articles from https://go.microsoft.com/fwlink/p/?linkid=2111390 to https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE2OqRI. But that means for the time being, everyone will only see the English version of the matrix, but at least it will be the most current version of the matrix.
(It might take a few days for our localization process to pick up and implement this change to the URL in the articles.)
Once we get the issue resolved with the localized versions of the matrix, we'll revert back to using https://go.microsoft.com/fwlink/p/?linkid=2111390 in our articles so that customers will once again be taken to the appropriate localized version of the matrix, where available.

Thank you for your understanding.
Due to the nature of localization most of the time the non en-us content on docs.microsoft.com or KB articles are either outdated or has wrong links or outdated downloads.
I am thankful so many contribute to and spent precious time on a human translation of articles
Appreciate your action and decision to merge this for the moment as primarily the en-us content is prefered by professionals anyway for said reason.
If you need help with a de-de localization I am happy to help.

PS @DHB-MSFT this one appear unmerged, means there was an internal PR?

@Karl-WE  We did an internal PR because there were several articles where we needed to make this change.

Ah I see thank you very much once again. 👍🏻


Controllers middleware @UseBefore is executed before passport middleware that was attached to app before importing controllers.

Is there any way to fix it? I'm using middleware to check for authentication status of user, but my check "if !request.user throw HttpUnautherizedError" is executed before user is event placed inside of request by passport-jwt.

can you show a short peace of code?

@pleerock
this is my Authenticated middleware which I user with controllers (UseBefore for the whole class)

This is my main startup code in main server file:

Controllers middleware @UseBefore is executed before passport middleware that was attached to app before importing controllers.

It is not possible, routing-controllers can't change somehow things you have already configure before using it. So debug and try to find real problem.


Feature request: Don't remove search results when text is changed?

Currently, if I do a find in files, the results are listed on the left. As I then click each result to make a change I can edit the file. If this is something like a rename, it means that as soon as I edit the text, the result on the left dissappears. This makes it hard to work out how far down the list of search results I've got to.
Would it be possible to grey out the result (as it is no longer valid) instead of removing it completely?

// CC @sandy081


add timing information to show how long it takes to build a wheel

It would be useful if the wheel building step of bootstrap, build, and build-sequence reported how long the wheel build takes. We can use that information to split up test jobs that are rebuilding a sequence of items, for example.

Should this information be logged out as info using logger.info()?

Maybe there is an existing log message where we could add the info? Like when we say that we've finished building a wheel, we could include the duration in that message?

Okay, will check!

I have the following questions / clarifications:

The bootstrap command uses handle_requirement() which in turn gives call to wheels.build_wheel(). Should we add timing information only for the wheels.build_wheel() call or the entire function handle_requirement() or entire function build_wheel() present in wheels.py. Also, the log message for "finishing building a wheel" exists in handle_requirement() where I plan to add timing information.

The build and build-sequence command uses a private method _build() which in turn gives call to wheels.build_wheel(). So do we time the wheels.build_wheel() call or entire _build() private method? Also, there are no log messages in _build() indicating completion of wheel building process and neither does build_wheel() in wheels.py. I plan to add a log message which will show the time required to build the wheel.

Should the time be displayed in seconds or in a specific format like hh:mm:ss?

I have the following questions / clarifications:

The bootstrap command uses handle_requirement() which in turn gives call to wheels.build_wheel(). Should we add timing information only for the wheels.build_wheel() call or the entire function handle_requirement() or entire function build_wheel() present in wheels.py. Also, the log message for "finishing building a wheel" exists in handle_requirement() where I plan to add timing information.

I'm most interested in the wheel build time, since that takes the longest of any operation.
Would it make sense to move that log message into build_wheel()?

The build and build-sequence command uses a private method _build() which in turn gives call to wheels.build_wheel(). So do we time the wheels.build_wheel() call or entire _build() private method? Also, there are no log messages in _build() indicating completion of wheel building process and neither does build_wheel() in wheels.py. I plan to add a log message which will show the time required to build the wheel.

Same answer, I think.

Should the time be displayed in seconds or in a specific format like hh:mm:ss?

Some of these builds take a lot of seconds. Pick something that would be easy to understand for a build that takes 30-45 minutes as well as one that takes less than 1 minute.

okay! will do
Thanks


Impact Shaders

HI @filipppavlov,
I've made a webgl 2.0 compatible version of ccpwgl to get 3d texture support so that I could try out the hull/armour/shield impact shaders.
In the SOF there is racial data for these effects but they're in arrays and don't have parameter names so while I could guess at most of the textures, the parameters are a different story (although I can obviously use the shader defaults).
I'm not 100% sure how these shaders are supposed to work, but it looks like they need a particle or emitter system to go with them. Could you confirm if this is the case and if they should be able to work in any manner without this system?
    "ArmorHardeningGradientMap": "res:/texture/fx/gradients/gradientbeat_02d.dds.0.png",
    "CutOffsetMap": "res:/fisfx/impact/3dfx_cutoffsetmap_01a.dds.0.png",
    "GradientMap": "res:/fisfx/impact/gradientmap_01a.dds.0.png",
    "HullRepairGradientMap": "res:/fisfx/impact/hullrepairgradient_smips_01a.dds.0.png",
    "HullRepairLayerAllMap": "res:/fisfx/impact/insidemap_03a_nrm.dds.0.png",
    "ImpactShieldDataMap": "res:/texture/fx/3d/3dfx_shield_concord.dds.0.png",
    "InsideMap": "res:/fisfx/impact/insidemap_03a.dds.0.png",
    "InsideNormalMap": "res:/fisfx/impact/insidemap_03a_nrm.dds.0.png",
    "LayerAllMap": "res:/fisfx/impact/3dfx_layerallmap_01a.dds.0.png"

Found the issue by combing through the shader: the i0.x variable in the for loop statement was causing the shader to fail compiling. This should have thrown an error, so not sure why it didn't... 📦

Armor/ Shield
 "damage": {
        "flickerPerlinAlpha": 0.199951171875,
        "armorParticleVelocityStretchRotation": 1,
        "shieldShaderHull": "fx/impact/fxshieldhullimpactv5.fx",
        "armorParticleTurbulenceFrequency": 7,
        "armorShader": "fx/impact/fxarmorimpactv5.fx",
        "armorParticleAngle": 1.3291015625,
        "armorParticleTurbulenceAmplitude": 999,
        "shieldShaderEllipsoid": "fx/impact/fxshieldimpactv5.fx",
        "armorParticleMinMaxLifeTime": {
            "0": 0.419921875,
            "1": 0.75
        },
        "armorParticleDrag": 0.074951171875,
        "armorParticleColor3": {
            "0": 1,
            "1": 0,
            "2": 0,
            "3": 0.501953125
        },
        "shieldGeometryResFilePath": "res:/graphics/generic/unitsphere/unitsphere_shieldgeo_01a.wbg",
        "armorParticleRate": 1000,
        "flickerPerlinSpeed": 0.96044921875,
        "flickerPerlinN": 2,
        "armorParticleColor2": {
            "0": 16,
            "1": 3.44921875,
            "2": 0,
            "3": 1
        },
        "flickerPerlinBeta": 4.19921875,
        "armorParticleSizes": {
            "0": 0.25,
            "1": 3,
            "2": 0,
            "3": 4
        },
        "armorParticleColor0": {
            "0": 32,
            "1": 12.546875,
            "2": 5.01953125,
            "3": 1
        },
        "armorParticleMinMaxSpeed": {
            "0": 120,
            "1": 150
        },
        "armorParticleColor1": {
            "0": 32,
            "1": 12.546875,
            "2": 5.01953125,
            "3": 1
        },
        "armorParticleTextureIndex": 3
    }

Hull
 "hullDamage": {
        "hullParticleMinMaxSpeed": {
            "0": 75,
            "1": 142
        },
        "hullParticleRate": 6,
        "hullParticleSizes": {
            "0": 77,
            "1": 222,
            "2": 333,
            "3": 1.19921875
        },
        "hullParticleAngle": 0.7998046875,
        "hullParticleTurbulenceAmplitude": 80,
        "hullParticleTextureIndex": 1,
        "hullParticleTurbulenceFrequency": 3,
        "hullParticleColorMidpoint": 0.199951171875,
        "hullParticleMinMaxLifeTime": {
            "0": 6,
            "1": 12
        },
        "hullParticleColor2": {
            "0": 0.0039215087890625,
            "1": 0.0039215087890625,
            "2": 0.0039215087890625,
            "3": 0.1058349609375
        },
        "hullParticleDrag": 0.419921875,
        "hullParticleColor0": {
            "0": 333,
            "1": 148.75,
            "2": 57.4375,
            "3": 0.0980224609375
        },
        "hullParticleColor1": {
            "0": 0.0274505615234375,
            "1": 0.0274505615234375,
            "2": 0.0274505615234375,
            "3": 0.1646728515625
        }
    },

Generic Race damage data
{
    "armorImpactTextures": [
        "res:/fisfx/impact/insidemap_03a.dds.0.png",
        "res:/fisfx/impact/3dfx_cutoffsetmap_01a.dds.0.png",
        "res:/fisfx/impact/3dfx_layerallmap_01a.dds.0.png",
        "res:/fisfx/impact/gradientmap_01a.dds.0.png",
        "res:/fisfx/impact/insidemap_03a_nrm.dds.0.png",
        "res:/texture/fx/gradients/gradientbeat_02d.dds.0.png",
        "res:/fisfx/impact/hullrepairgradient_smips_01a.dds.0.png",
        "res:/texture/fx/3d/3dfx_shield_concord.dds.0.png"
    ],
    "shieldImpactTextures": [
        "res:/texture/fx/gradients/whitesharp_bw_01a.dds.0.png",
        "res:/fisfx/impact/temporalfadeout_01a.dds.0.png",
        "res:/texture/fx/3d/3dfx_shield_01a.dds.0.png",
        "res:/texture/fx/gradients/gradientbeat_02c.dds.0.png"
    ],
    "armorImpactParameters": [
        {
            "0": 3,
            "1": 32,
            "2": 3.142578125,
            "3": 1.2275390625
        },
        {
            "0": 1.2998046875,
            "1": 11.75,
            "2": 9.1875,
            "3": 2
        },
        {
            "0": 10.5,
            "1": 0.004199981689453125,
            "2": 1.33203125,
            "3": 128
        },
        {
            "0": 0.06475830078125,
            "1": 0.06475830078125,
            "2": 0.06475830078125,
            "3": 1
        },
        {
            "0": 0.0231475830078125,
            "1": 0.0231475830078125,
            "2": 0.0231475830078125,
            "3": 1
        },
        {
            "0": 1,
            "1": 0.1129150390625,
            "2": 0.00920867919921875,
            "3": 1
        },
        {
            "0": 0.0030345916748046875,
            "1": 0.0030345916748046875,
            "2": 0.0030345916748046875,
            "3": 1
        },
        {
            "0": 11.75,
            "1": 1.5,
            "2": 0.25,
            "3": 0
        },
        {
            "0": 48.1875,
            "1": 64,
            "2": 48.1875,
            "3": 1
        },
        {
            "0": 1.8916015625,
            "1": 2.4921875,
            "2": 3,
            "3": 1
        },
        {
            "0": 0,
            "1": 0,
            "2": 0,
            "3": 0
        },
        {
            "0": -17,
            "1": 6,
            "2": 0.412353515625,
            "3": 0.109375
        },
        {
            "0": 8,
            "1": 9,
            "2": 0.14990234375,
            "3": 0.0999755859375
        },
        {
            "0": 3,
            "1": 2,
            "2": 0.14990234375,
            "3": 0.199951171875
        },
        {
            "0": 0.12298583984375,
            "1": -4.19921875,
            "2": 0.00099945068359375,
            "3": 0
        },
        {
            "0": 3,
            "1": 6,
            "2": 0.00299835205078125,
            "3": -0.005496978759765625
        },
        {
            "0": 1.5,
            "1": 2.66015625,
            "2": 3.298828125,
            "3": 1
        },
        {
            "0": 12,
            "1": 0.25,
            "2": -0.419921875,
            "3": 0
        }
    ],
    "shieldImpactParameters": [
        {
            "0": 3.61328125,
            "1": 11,
            "2": 4,
            "3": 0.5
        },
        {
            "0": 0.25,
            "1": 0.0999755859375,
            "2": 0.300537109375,
            "3": 1.7431640625
        },
        {
            "0": 0.01329803466796875,
            "1": 0.14990234375,
            "2": 0.103271484375,
            "3": -0.9814453125
        },
        {
            "0": 0,
            "1": -0.0099945068359375,
            "2": -0.0099945068359375,
            "3": 0
        },
        {
            "0": -1,
            "1": -3,
            "2": 0.349853515625,
            "3": 0.64990234375
        },
        {
            "0": 0,
            "1": -5,
            "2": 0,
            "3": 0
        },
        {
            "0": -1.5,
            "1": -1.5,
            "2": 0.262451171875,
            "3": 0.375
        },
        {
            "0": 0.69970703125,
            "1": -0.39990234375,
            "2": -0.69970703125,
            "3": 5
        },
        {
            "0": 1.25,
            "1": 0,
            "2": 0,
            "3": 0
        },
        {
            "0": 0.587890625,
            "1": 0.2822265625,
            "2": 0.11761474609375,
            "3": 1
        },
        {
            "0": 0.367919921875,
            "1": 0.5546875,
            "2": 0.74609375,
            "3": 1
        },
        {
            "0": 1.330078125,
            "1": 21.28125,
            "2": 86.375,
            "3": 86.375
        }
    ]
}

I was going to take a look at webgl 2.0 some time this summer. One of the requirements there is a different export phase for our shaders to be compatible with GLSL 3. I wanted to do this along with some larger changes to the project.
Hopefully I'll have some time to look into this in July-August.
If I remember correctly the shield impact effect contains an ellipsoid around the ship (that's the part that needs 3d textures) and some particle emitters. It should look OK without particles though. The trick there is recording hit directions in a texture. So there is quite a bit of code missing for this. I never bothered porting it to javascript as I knew that the whole thing wouldn't work without 3d textures.
The hull damage effect is kind of similar, but instead of being an ellipse, it's an overlay effect on ship geometry.

Which texture records the hit directions? And is there specific value/ shape they need to be?

Managed to get it kinda working, although I can't seem to place the damage anywhere other than the middle of an object using a pure white texture :(


Support for react 18

I have been using this npm in all my projects but now we have planned to move to react 18 will we have support for react 18 ?

@chunming-c

@chunming-c Any help here in upgrading the package to support React18?
Much appreciated

+1

Any plans to upgrade this npm package to support React 18?

This issue duplicates #1797.
FYI, the package hasn't been updated for 4 years.
So I don't think it would have any more update or maintenance.


Different color for

The color for \cnote and \mnote highlighting are the same, and with the new behavior that \cnote simply generates a bit of text if you provide an argument, it might be worthwhile seeing if a different color would help for either one.

While you're at it, the current highlighter color is pretty awful in my opinion :grimacing:

which one? the yellow for pnote? or the grey for mnote?

The \pnote.


Ircv3 capabilities?

Would be useful to use SASL, account-notify and the like

I added PLAIN SASL support , see PR #77


use map() on Collection throw a parenthesis of PHPDoc type

Larastan Version: 9.5.19
--level 8 used:

Description
Parameter #1 $callback of method Illuminate\Database\Eloquent\Collection<(int|string),Illuminate\Database\Eloquent\Model>::map() expects
  callable(Illuminate\Database\Eloquent\Model, (int|string)): array<string, mixed>,
  Closure(App\Models\SocialSecurity, int|string): array<string, mixed> given.

Laravel code where the issue was found
    protected static function processListedCollection(Collection $collection, ListRequest $request): Collection
    {
        /** @var array<int,string> $relations */
        $relations = self::getEagerLoadRelations();

        return Collection::make($collection->map(fn (SocialSecurity $social_security, int|string $key): array => self::loadRelatives($social_security, $relations)));
    }

If this is a BUG, I am willing to fix it.

Hello Kay! 👋
Thank you for your report.
Could you try with a "long" function?

Hi,
You need to add a type with @param for the $collection parameter. To describe the collection generic types.
Try this:
/** @param Collection<array-key, App\Models\SocialSecurity> $collection */
protected static function processListedCollection(Collection $collection, ListRequest $request): Collection
{
	...
}

Also consider adding something similar for the return type.


Replace Basic Progress Bar with Functional Slider, Revamp Podcast Player, and Implement Accurate View Tracking with Internal Timer

This pull request overhauls the podcast player by adding a functional slider for enhanced playback control, a redesigned user interface for the player, and a YouTube-style method to track and measure accurate podcast views based on actual playback time. These improvements aim to boost user experience, engagement, and view-tracking accuracy.
Key Changes:

Interactive Slider for Playback Control:

Replaced the static progress bar with a functional, draggable slider.
Allows users to adjust playback position precisely, offering a smoother and more responsive experience.
Improved accessibility, making playback control easier across all devices.

Podcast Player Redesign:

Modernized the player interface with an updated layout and responsive design adjustments.
Added volume control and enhanced playback features like forward and rewind buttons.
Optimized styling for seamless appearance across different screen sizes.

Accurate View Tracking with Internal Timer:

Implemented a timer-based system to track actual podcast listening duration per user.
Like YouTube’s methodology, this system measures and logs user engagement based on playback activity, ensuring a view is counted only if a user listens for a specified time.
Reduces false or inaccurate view counts by differentiating between brief interactions and meaningful engagement.

Testing & Validation:

Tested slider functionality and new view-tracking system across multiple devices and browsers.
Validated view count accuracy by simulating various playback scenarios (partial, pauses, and full listens).

This update provides a richer podcast experience by giving users more control over playback and offering precise, meaningful view metrics for content creators.

LGTM 👍