Netopeer2-server process is blocked.

Hi,
version: https://github.com/CESNET/netopeer2/releases/tag/v1.1.76
callhome configuration:
root@OpenWrt:/# sysrepocfg --export --format xml --datastore running --xpath /ietf-netconf-server:netconf-server/call-home -v 3
[INF]: Scheduled changes not applied because of other existing connections.
[INF]: Connection 15 created.
[INF]: Session 840 (user "root", CID 15) created.
<netconf-server xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-server">
  <call-home>
    <netconf-client>
      <name>eth0</name>
      <endpoints>
        <endpoint>
          <name>default-ssh</name>
          <ssh>
            <tcp-client-parameters>
              <remote-address><IP_ADDRESS></remote-address>
              <keepalives>
                <idle-time>1</idle-time>
                <max-probes>10</max-probes>
                <probe-interval>3</probe-interval>
              </keepalives>
            </tcp-client-parameters>
            <ssh-server-parameters>
              <server-identity>
                <host-key>
                  <name>default-key</name>
                  <public-key>
                    <keystore-reference>genkey</keystore-reference>
                  </public-key>
                </host-key>
              </server-identity>
              <client-authentication>
                <supported-authentication-methods>
                  <publickey/>
                  <passsword/>
                  <other>interactive</other>
                </supported-authentication-methods>
                <users/>
              </client-authentication>
            </ssh-server-parameters>
          </ssh>
        </endpoint>
      </endpoints>
      <connection-type>
        <persistent/>
      </connection-type>
    </netconf-client>
  </call-home>
</netconf-server>
root@OpenWrt:/#

Netopeer2-server call home for a long time, Occasionally, the following error occurs and the state is blocked(No more log printing), The process is restored after being restarted.
root@OpenWrt:~# tail -f /tmp/log/netopeer2-server.log
[INF]: LN: Trying to connect the pending socket 35.
[INF]: LN: Timed out after 5s (Operation now in progress).
[ERR]: LN: Failed to connect socket 35 after 5 retries, closing.
[INF]: LN: Trying to connect via IPv4 to <IP_ADDRESS>:4334.
[INF]: LN: Timed out after 5s (Operation now in progress).
[INF]: LN: Trying to connect the pending socket 35.
[INF]: SR: Session 12410 (user "root", CID 16) created.
[ERR]: LN: SSH key exchange timeout.
[ERR]: LN: Call Home client "eth0" was not found.
[INF]: LN: Call Home client "eth0" thread exit.

What advice do you have?
thanks.

I would be curious about the output of the client, whatever you are using. But this should occur only if the client fails to respond to a new SSH connection in a timely manner (5 * 5s), which is definitely an error. I am also puzzled by
[ERR]: LN: Call Home client "eth0" was not found.

which seems like an error in libnetconf2 but it is hard to say.
So it is difficult to suggest anything and to determine whether there is anything for us to fix. You can try, for example, to enable SSH debug output (-c SSH) and compare the output on successful connect to a failure. I do not know what else to suggest.


Add description for all Stripe GraphQL Fields

fixes nhost/nhost#975

Codecov Report

Merging #1011 (3893195) into main (aa17767) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1011   +/-   ##
=======================================
  Coverage   96.52%   96.52%
=======================================
  Files          39       39
  Lines        6273     6273
  Branches      393      393
=======================================
  Hits         6055     6055
  Misses        218      218

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


How to do calibration on real camera data?

I have a webcam I would like to perform calibration on. Calibration on real data was mentioned in the paper, but there doesn't seem to be away to implement that using the code.
Thanks in advance!

The pursuit of calibration precision can be time-consuming.

You need to train a detector model with your own chessboard size and background using train_CornerDetect.py and DataGenerator.py;
If distortion exists, you need train a model to correct it using train_DistCorr.py and DataGenerator.py;
Perform calibration using  calibration.py -> calib_by_RANSAC_practical() and tune your parameters;

Thanks for this! What if I was only interested in getting the radial distortion coefficients (k1, k2, k3)? How would I do that using my own camera images?

This method directly corrects the distorted images which means it outputs the correction coefficients rather than radial distortion coefficients.
If you wanna correct you images, you only need to train a distortion correction model. But  before that, you need to generate some ground truth data including distorted images and original images using `DataGenerator.py'. Note for better performance, synthetic dataset should be closed to the real onem, i.e. chessboard size and background.

Understood. Though, would it be possible to reverse-engineer the correction coefficients to obtain the radial distortion coefficients?

Actually, it's hard to acquire exact accurate radial distortion coefficients as the radial model we used is not completely reversible.

Got it. Would you say that the radial distortion coefficients obtained from OpenCV's camera calibration are accurate/sufficient enough?

If your images only got slight distortion, then yes. And I recommend to use Matlab which is more stable than OpenCV.

Better not? As the sharpening may change the original corner locations, I think.

I see. I've used a combination of image super-sampling followed by image shrinking for the implementation I'm attempting. And based on my testing, there were minor improvements in the reprojection error - but improvements, nonetheless.

Would you recommend that I still continue my implementation?

That's pretty good. But the exact corner locations need to be kept during the processing. I recommend that you can do some test on ground truth data.

You can use the `DataGenerator.py' to generate chessboard image with GT corner coordinates(no need to use the simulator camera to project, but directly draw the image), and then perform your operation and achieve the processed image(img_0). If you have the GT corner coordinates after processing(like after image super-resolution, the GT coordinates is linearly changed), you can draw the chessboard image again(img_1), and compare these two image(img_0&1) to see the difference. If the corner location is significantly changed, the image difference will be  obvious.

Got it. Here's an example of 3 three corner locations from my testing (after sub-pix):
Regular Calibration: [746.4545  425.5057 ], [712.4864  425.4922 ], [678.32355 425.57083]
Regular + Processed Calibration: [746.4544  425.51306], [712.48346 425.4849 ], [678.3135  425.57437]
Are these corner location differences significant?

No, it's minor.

Minor for both the corner location differences and the reprojection error?
Would having an implementation that results in a 1% RPE improvement (such as this) have any merit if it were part of a research or study?

The corner is minor, and the rpe is hard to say. As the reprojection error does not directly reflect the accuracy of calibration, it's better to apply more metrics to show the improvement if possible, like some application accuracy improvement (SfM or SLAM). Or you can compare the intrinsic parameter error like our paper.

Got it. Thanks so much for your help!


Docker container run issue

On running the docker container on windows:

Replace %cd% with application absolute path


Refactor Controller/Syncer logic

Syncers are full of a lot of repeated code that could be pushed into the controller. Do that.

Pushed common logic down into controller at the expense of increasing the complexity of the interface.  It will make cleaning up logging and adding metrics easier, but I can't say it reduced complexity overall or increased clarity.


Update scopes.md

upstream packages fail when not scoping always-auth.

@RobinBreman Thank you for your contribution. I am assigning this to the article author for review. Thank you.

Hi @RobinBreman ! Thanks for this - going to add @alexmullans to take a quick look for correctness and then hopefully we can get this change live :)


feat: retries new blocks

What was wrong?
This closes #893
How was it fixed?
Instead of panic, we loop over each new block , and emit a warning instead
To-Do

[ ] Add entry to the release notes (may forgo for trivial changes)
[ ] Clean up commit history

Thanks for the review. I would like to clarify if it makes sense to move this logic to within the serve  function
i.e.
    async fn serve(
        &self,
        gossip_range: Range<u64>,
        epoch_acc: Option<Arc<EpochAccumulator>>,
        gossip_stats: Arc<Mutex<GossipStats>>,
    ) -> anyhow::Result<()> {
        let futures = futures::stream::iter(gossip_range.into_iter().map(|height| {
            let epoch_acc = epoch_acc.clone();
            let gossip_stats = gossip_stats.clone();
            async move {
                let mut retry_count = 0;
                while retry_count < 3 {
                    match self
                        .serve_full_block(height, epoch_acc, gossip_stats, self.portal_clients.clone())
                        .await
                    {
                        Ok(_) => break,
                        Err(e) => {
                            warn!(
                                "Error serving block in latest mode: {:?}. Retrying...",
                                e
                            );
                            retry_count += 1;
                            if retry_count >= 3 {
                                return Err(anyhow!("Failed to serve block after 3 retries")); // We dont panic here , just warn
                            }
                        }
                    }
                }
            }
        }))
        .buffer_unordered(FUTURES_BUFFER_SIZE)
        .collect::<Vec<()>>();
        futures.await;
        if let Ok(gossip_stats) = gossip_stats.lock() {
            gossip_stats.display_stats();
        } else {
            warn!("Error displaying gossip stats. Unable to acquire lock."); // We dont panic here , just warn
        }
        Ok(())
    }

that way , its passed on to both launch_latest and launch_backfill

Ahh, sorry, but I was a bit confused about the scope of this pr. It seems to me like I was over-complicating things. All the issue #893 is asking is to not panic in the case that we are unable to that we run into an error requesting/gossiping data. In which case, simply logging an warning in the error case is fine. We don't need to worry about retries. Something like...
if let Err(err) = self.serve(gossip_range.clone(), epoch_acc, gossip_stats.clone()).await {
    warn!("Error serving block range in latest mode: {err:?}");
}

Closing as this PR is no longer applicable


⚠ Cioos Pacific CKAN has degraded performance

In 09c97e6, Cioos Pacific CKAN (https://catalogue.cioospacific.ca) experienced degraded performance:

HTTP code: 200
Response time: 13546 ms

Resolved: Cioos Pacific CKAN performance has improved in a103db3 after 18 minutes.


Remove security for /auth route in OpenAPI generator

The /auth route is always public, so we can disabled the security part in OpenAPI.

I don't understand the CI Tests error, I don't think this is related to the PR.


DOC: Only dunders we have created will appear in the documentation

Some hacky things are happening, but it beats redistributing numpydoc!

:+1: this is way better than the .. shownumpydoc hack we used to have!

Ready for merge when tests pass


Added environment collection class

Codecov Report

Merging #13434 into master will decrease coverage by 0.02%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master   #13434      +/-   ##
==========================================
- Coverage   59.92%   59.90%   -0.03%
==========================================
  Files         670      671       +1
  Lines       37211    37221      +10
  Branches     5311     5311
==========================================
- Hits        22300    22297       -3
- Misses      13774    13784      +10
- Partials     1137     1140       +3

Impacted Files
Coverage Δ

src/client/interpreter/contracts.ts
100.00% <ø> (ø)

src/client/pythonEnvironments/info/index.ts
68.96% <ø> (ø)

.../pythonEnvironments/common/externalDependencies.ts
50.00% <50.00%> (ø)

...ent/pythonEnvironments/discovery/locators/index.ts
85.71% <100.00%> (ø)

src/client/pythonEnvironments/legacyIOC.ts
100.00% <100.00%> (ø)

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/datascience/crossProcessLock.ts
79.41% <0.00%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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


[fix] Fix map type mapping to doris type error

Proposed changes

When you map the flink Map<date, date> type to map<date, date> or map<string, string> in Doris, this will cause the key to be null and the result to be incorrect respectively. Therefore, it can be solved by converting the key  in Map into Date.

second, it solves the problem of converting Map<TIMESTAMP_LTZ,TIMESTAMP_LTZ> into MAP<STRING,STRING> without time zone information.

We add a unit test for map type.
Issue Number: close #xxx

Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

It is recommended to add map type coverage in DorisRowConverterTest

It is recommended to add map type coverage in DorisRowConverterTest

Ok !!!


Support metadata annotations in ScaledJob template's volume claims

Report
Applying metadata annotations on a volume claim template, inside ScaledJob templates returns an error.
Here's the definition of the metadata annotations:
apiVersion: keda.sh/v1alpha1
kind: ScaledJob
metadata:
  labels:
    argocd.argoproj.io/instance: xxx
  name: yyy
  namespace: zzz
spec:
(...)
        volumes:
(...)
          - ephemeral:
              volumeClaimTemplate:
                metadata:
                  annotations:
                    resize.topolvm.io/increase: 15Gi
                    resize.topolvm.io/inodes-threshold: 20%
                    resize.topolvm.io/storage_limit: 1024Gi
                    resize.topolvm.io/threshold: 30%
                    volume-type: ephemeral

Expected Behavior
This should create a volume claim with the appropriate metadata annotations
Actual Behavior
It returns the following error: ScaledJob in version "v1alpha1" cannot be handled as a ScaledJob: strict decoding error: unknown field "spec.jobTargetRef.template.spec.volumes[5].ephemeral.volumeClaimTemplate.metadata.annotations"
Steps to Reproduce the Problem

Create a ScaledJobs based on the definition given above
Run kubectl apply -f using this definition
This returns the error

KEDA Version
2.15.1
Kubernetes Version
1.30
Platform
Google Cloud
Scaler Details
No response
Anything else?
No response

Interesting, could this be related with this other issue that we solved some years ago? https://github.com/kedacore/keda/issues/1311
If yes, are you willing to apply the same patch to the new path to keep the current annotations :)

Hey @JorTurFer,
Thanks for pointing me this related error. I applied a patch based on the fix in this issue and it solves the problem
I have proposed a PR based on this solution https://github.com/kedacore/keda/pull/6259

Thanks for the fix! He have merged https://github.com/kedacore/keda/pull/5939, and I'd say that it will fix the current issue too. Could you double check it?


nixos/pantheon: add docs

Motivation for this change
I finally translated the docs I wrote for Pantheon in markdown months ago :confetti_ball:
https://gist.github.com/worldofpeace/27fcdcb111ddf58ba1227bf63501a5fe
There's one thing I couldn't translate and it's the cool citation/reference [^1], which in markdown would give you a nice hover text and citation at the end of the section (clickable link).
Things done
Manual was built.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@jtojnar I wasn't sure how to link into the nixpkgs manual for the overrides.

I also wasn't sure about plugins vs plug-ins. I see a lot of docs with plugins and I almost always use this spelling.


usefulness of dev/xcode directory

as cmake is used and as cmake can create xcode project files, is dev/xcode directory useful ?

Hi!
Yes, it is useful. XCode project in the directory is not for building a library. It is exclusively for development. The project builds an executable file. Simply put, I'm developing in XCode :)


(pre-1107 2) Refactors and tidy ups

Changes in this PR
A few small refactors and tidy ups before #352
Release checklist
Release process documentation
As part of our continuous deployment strategy we must ensure that this work is
ready to be released once merged.
Pre-merge

[ ] There are changes required to the Accredited Programmes API for this change to work...

[ ] ... and they have been released to production already

Post-merge

[ ] This adds, extends or meaningfully modifies a feature...

[ ] ... and I have written or updated an end-to-end test for the happy path in the Accredited Programmes E2E repo

[ ] This makes new expectations of the API...

[ ] ... and I have notified the API developer(s) of changes to the contract tests (Pact), or the API is already compliant

[ ] Manually approve release to preprod
[ ] Manually approve release to prod

 Show message if there are no sentence details (S)


NetworkPolicy based on PodSelector and NamespaceSelector doesn't work.

NetworkPolicy based on PodSelector and NamespaceSelector doesn't work.
Expected Behavior

policy:

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  namespace: network-policy
  creationTimestamp: null
  name: allow-client-b-in-ns-b-via-ns-selector-and-pod-selector
spec:
  ingress:
  - from:
    - namespaceSelector:
        matchLabels:
          ns-name: network-policy-c
      podSelector:
        matchLabels:
          pod-name: client-b
  podSelector:
    matchLabels:
      pod-name: network-policy-server

namespace:

apiVersion: v1
kind: Namespace
metadata:
  creationTimestamp: "2019-11-15T05:52:09Z"
  labels:
    ns-name: network-policy-b
  name: network-policy-b

pod

apiVersion: v1
kind: Pod
metadata:
  namespace: network-policy-b
  generateName: client-a-

  labels:
    pod-name: client-b
spec:
  containers:
  - args:
    - /bin/sh
    - -c
    - for i in $(seq 1 5); do nc -vz -w 8 svc-network-policy-server.network-policy
      80 && exit 0 || sleep 1; done; exit 1
    image: beyond.io:5000/busybox:1.29
    name: client-a-container
    resources: {}
  restartPolicy: Never
status: {}

this pod was expected to connect to server，but can not.

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Calico version : v3.1.0
Orchestrator version (e.g. kubernetes, mesos, rkt):kubernetes-v1.15.1
Operating System and version: Centos 7 1804
Link to your project (optional):

You listed Calico version v3.1.0, was that a typo? If not please try again with the latest 3.10 release as support for namespace selectors was added in v3.10.0.

@tmjd Thank you for your answer. I will have a try,if it works ,I will closed this issue.

You listed Calico version v3.1.0, was that a typo? If not please try again with the latest 3.10 release as support for namespace selectors was added in v3.10.0.

@tmjd Hi! May I ask if it is supported in version 3.10.0 and above. I meet same issue in calico 3.8.0. I thought calico had already supported it.
This is my issue: https://github.com/kubernetes/kubernetes/issues/85539

@xieyanker I have already check it,v3.10.0 works. calico v3.10 release note

@TomatoAres Thanks, I will upgrade calico to 3.10.1

@TomatoAres @tmjd @fasaxc
I have upgraded calico to v3.10.1. However, not works for me still!
root@inspurtest14-wxhqn85ukg-master-1:~# kubectl get ns -A -owide --show-labels|grep test
test1             Active   11d   ns=test1
test2             Active   11d   <none>
root@inspurtest14-wxhqn85ukg-master-1:~# kubectl get pod -A -owide --show-labels|grep test-nginx
test1             test-nginx1                                         1/1     Running             0          10m     <IP_ADDRESS>     master1   <none>           <none>            app=test-nginx1
test2             test-nginx2                                         1/1     Running             0          10m     <IP_ADDRESS>     master2   <none>           <none>            app=test-nginx2
root@inspurtest14-wxhqn85ukg-master-1:~# kubectl get networkpolicy --all-namespaces -oyaml
apiVersion: v1
items:
- apiVersion: extensions/v1beta1
  kind: NetworkPolicy
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"extensions/v1beta1","kind":"NetworkPolicy","metadata":{"annotations":{},"name":"test-nginx-policy","namespace":"test2"},"spec":{"ingress":[{"from":[{"namespaceSelector":{"matchLabels":{"ns":"test1"}},"podSelector":{"matchLabels":{"app":"test-nginx1"}}}]}],"podSelector":{"matchLabels":{"app":"test-nginx2"}}}}
    creationTimestamp: "2019-12-03T12:32:07Z"
    generation: 1
    name: test-nginx-policy
    namespace: test2
    resourceVersion: "8690440"
    selfLink: /apis/extensions/v1beta1/namespaces/test2/networkpolicies/test-nginx-policy
    uid: eb68fa16-15c8-11ea-b1d2-fa163e59946d
  spec:
    ingress:
    - from:
      - namespaceSelector:
          matchLabels:
            ns: test1
        podSelector:
          matchLabels:
            app: test-nginx1
    podSelector:
      matchLabels:
        app: test-nginx2
    policyTypes:
    - Ingress
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""
root@inspurtest14-wxhqn85ukg-master-1:~# calicoctl get networkpolicy --all-namespaces -oyaml
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
apiVersion: projectcalico.org/v3
items:
- apiVersion: projectcalico.org/v3
  kind: NetworkPolicy
  metadata:
    creationTimestamp: 2019-12-03T12:32:07Z
    name: knp.default.test-nginx-policy
    namespace: test2
    resourceVersion: "8690442"
    uid: 5506ca0a-a85f-483e-912e-b0e20b8d215e
  spec:
    ingress:
    - action: Allow
      destination: {}
      source:
        namespaceSelector: ns == 'test1'
        selector: projectcalico.org/orchestrator == 'k8s' && app == 'test-nginx1'
    order: 1000
    selector: projectcalico.org/orchestrator == 'k8s' && app == 'test-nginx2'
    types:
    - Ingress
kind: NetworkPolicyList
metadata:
  resourceVersion: "8692292"
root@inspurtest14-wxhqn85ukg-master-1:~# kubectl exec -it test-nginx1 sh -ntest1
# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 22ms

#
root@inspurtest14-wxhqn85ukg-master-1:~# calicoctl version
Client Version:    v3.10.1-2-gb82f07ab
Git commit:        b82f07ab
Cluster Version:   v3.10.1-5-g2826afa
Cluster Type:      kubespray,bgp,k8s

Is there any configuration that needs attention？ Maybe I use some wrong configs.

Did you ensure that your test pods have the appropriate app labels?
Have you verified without the policy (or any other) that the traffic you are attempting does work?

@tmjd  Yeah, my pods have the appropriate app labels
root@inspurtest14-wxhqn85ukg-master-1:~# kubectl get ns -A -owide --show-labels|grep test
test1             Active   11d   ns=test1
test2             Active   11d   <none>
root@inspurtest14-wxhqn85ukg-master-1:~# kubectl get pod -A -owide --show-labels|grep test-nginx
test1             test-nginx1                                         1/1     Running             0          10m     <IP_ADDRESS>     master1   <none>           <none>            app=test-nginx1
test2             test-nginx2                                         1/1     Running             0          10m     <IP_ADDRESS>     master2   <none>           <none>            app=test-nginx2

And if I delete the networkpolicy, I can connect success.

Sorry I should have scrolled over in your first post and seen the labels.
Actually I realized that I was incorrect in suggesting the upgrade, the upgrade would only be required if you were using a Calico GlobalNetworkPolicy and you were using namespaceSelector as the 'top' level selector like here https://docs.projectcalico.org/v3.10/security/namespace-policy#use-kubernetes-rbac-to-control-namespace-label-assignment.
I'm not sure what to say, your setup looks correct. Would you please open another issue since the original issue here was resolved. Please include info about your setup and reference this issue.
I think we might need you to set debug for node/felix and collect logs from the host where nginx2 is running.

@tmjd Thanks for your reply! I have resolved it!
My cni-plugin‘s configuration didn't start policy, it works when I add follows
      "policy": {
        "type": "k8s"
      },

on /etc/cni/net.d/calico.conflist.template, refer to cni-plugin configuration.
By the way, I got some error about authority when I run new pod after I update this config. It works util I exec kubectl edit clusterrole system:node and add namespaces's  authority. Is there exists any good idea to resolve it?

@xieyanker Please open a new issue for your latest error.

@tmjd I resolve the authority's issue. This is because of my cni-plugin configuration's kubeconfig is wrong, and I should use /etc/cni/net.d/calico-kubeconfig.


Add precipitation metric collection

KCRHA expects this alert to be able to collect information on precipitation (measurements in inches) for both predicted rainfall and snowfall forecasts.

Potential Data Sources
Rain
Liquid precipitation (this is their language, not mine) data may be derived from the Weather Prediction Center (WPC) in the form of Quantitative Precipitation Forecasts (QPF) and Probabilistic Quantitative Precipitation Forecasts (PQPF) products.
Documentation on both can be found here:

QPF
PQPF

Furthermore, there is additional rain-related dashboards and forecasts, such as the Excessive Rainfall Forecast and Significant River Flood Outlook products.
Snow
Winter weather precipitation may be derived from the WPC's Winter Weather Forecast (WWF) product (Documentation for the WWF product). The WWF breaks down it's precipitation forecasts into 2 categories:

Snowfall
Freezing rain

Data Formats & Availability
Rain
Formats
The QPF's are available as GRIB2, Shapefile, and KML formats (seen here), while PQPF's seem to only be available via the GRIB2 format (seen here).
Availability
For brevity's sake, I will cover only the GRIB2 type of forecast format offered for QPF, to give context to the type of forecast breakdowns offered. QPF's seem to be available for a 7-day period with differences between the first 3 days of forecasts and the last 4 days of forecasts. For the first 3 days, each forecast covers 6 hour spans (eg, 00-06 hour forecast, 06-12 hour forecast, ..., 30-36 hour forecast, etc.). However, there also exists longer span reports for the first three days, as well, offering 24/120/168 hour span forecasts, such as 24/48/72 hours. Lastly, the 5-day and 7-day forecasts are only available via 120 hour and 168 hour forecasts.
While PQPF's only seem to project out 3 days or 72 hours, providing a 6 hour, 12 hour, 24 hour and 72 hour forecast.
Snow
Formats
The WWF seems to also offer GRIB2, Shapefile and KML formatted files (seen here for Shapefile/KML links and individual forecast links offer GRIB2 format download links).
Availability
The WWF seems to only predict precipitation amounts out by 3 days or 72 hours, but offer 1 day, 2 day, and 3 day forecasts.
Collecting the data
All data seems to be hosted as individual files, each containing some or all of the specific forecast, which are hosted via an FTP server.
To collect the 7-day forecast of each of these would require fetching between 1-7 forecast files (depending on the granularity of the forecast data within each file) per data point (ie, 1-7 QPF or PQPF forecast files, 1-7 snowfall forecast files, and/or 1-7 freezing rain forecast files).
Below are the FTP server locations of the aforementioned forecast files:

QPF

GRIB2
Shapefile

PQPF

GRIB2

WWF

GRIB2
Shapefile

KML (all types)

Finding the forecast files on the FTP
While I'm not certain the exact naming strategy for all forecast files, the strategy for most files on the FTP server seem to follow a pattern as such:
p{$length_of_forecast}m_{$date_of_forecast}{$hour_of_forecast}f{$end_time_of_forecast}

Where:

$length_of_forecast pertains to the span of hours covered (ex, p06m_... likely covers a 6 hour window)
$date_of_forecast pertains to the day for when the forecast begins (ex, if the forecast was calculated on 2024 Jan 7, this would read 20240107
$hour_of_forecast pertains to the hour for when the forecast begins (ex, if the forecast was calculated at 05:18, this would read 06, as the forecasts are calculated every 6 hours, rounding the up to the nearest hour of when the forecast was generated)
$end_time_of_forecast is the end time of the forecast. So if this reads 54 and the $length_of_forecast was p06m, then this report covers hours 48 through 54 from when the forecast was calculated. So if the forecasts $date_of_forecast and $hour_of_forecast reads<PHONE_NUMBER>, this forecast was calculated to start at noon (timezone unknown) for 2024 Jan 7, and provides forecasted conditions for for the hours of 2024 Jan 9 @ noon to 2024 Jan 9 @ 6p.

Parsing the data
At present, I'm not sure how to use any of these data types (GRIB2, Shapefile, or KML) to collect the necessary data about predicted rainfall.

Hoorah! It seems like it's not a well-documented feature, but after reviewing the NWS endpoints again (for what feels like the 100th time), it turns out that there is a RAW forecast endpoint for individual gridpoints, which will provide a 7-day forecast with quantitative precipitation estimates!
https://api.weather.gov/gridpoints/SEW/125,69

Added with #4


Generate emulation training data v4

v3 of the emulation data was generated in November and lacked some important information like cloud after the condensation scheme. The training data also showed some initial condition dependence due to using surface forcings from the initial condtions rather than GRIB files.

Generate v4 of this training set addressing these issues
Add  emulation.ModelConfig.output_start_sec

cc @frodre
Probably easiest to review commit-by-commit.

At some point it might be interesting for us to look at the difference between the relevant fields in the sfc_data files of the initial conditions and their counterparts in the GRIB files.

Indeed. I can't tell if this is a sensitivity we want to present in the paper. If it ends up being relevant for ML it probably is though.


checking vm version error " check internet connection " how to fix

when i run vm_main.py  , i get error saying " Checking vm main version..." and then it keep repeating line after line with the same error : " recheck internet connection " , how can I fix this error ?

this is the error please if anyone knows how to fix it, leave a comment, thanks


Img src and link mismatch

There is a mismatch between the zoom/open in new tab hyperlink for the image regarding "Regulatory Compliance Dashboard" (currently, the wrapper  element is pointing to an image for "Audit Reports List"  instead and displays it when user goes to click to Zoom.

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

ID: a9fbe6ca-1f70-657b-fc1a-c488335bdef6
Version Independent ID: 4962534a-ec5a-bc9a-f0ec-2074cf446807
Content: The regulatory compliance dashboard in Microsoft Defender for Cloud
Content Source: articles/defender-for-cloud/update-regulatory-compliance-packages.md
Service: defender-for-cloud
GitHub Login: @ElazarK
Microsoft Alias: elkrieger

@minh-pham1
Thanks for your feedback! We will investigate and update as appropriate.

#please-close


[WIP] Feature/issue 758 add dot product covariance function

Submission Checklist

[ ] Run unit tests: ./runTests.py test/unit
[ ] Run cpplint: make cpplint
[ ] Declare copyright holder and open-source license: see below

Summary:
Add a dot product covariance function. The dot product covariance function is equivalent to Bayesian Regression with N(0, 1) priors on regression coefficients. Adding this will extend the Gaussian Process Library in Stan, and enable users to use HMC for fast computation.
How to Verify:
Test cases.
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Copyright <2018>
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

I added a WIP marker to the title to indicate it's not ready for review.  Every push kicks off our integration testing, so please don't hammer our servers with lots of little updates.

closing pull request until ready for review.


Automatic version updates for v1.32.4 release

Description
Prepare to release v1.32.4
For PR author

[x] Tests for change.
[x] If changing pkg/apis/, run make gen-files
[x] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

/merge-when-ready delete-branch squash-commits release-note-not-required docs-not-required

OK, I will merge the pull request when it's ready, squash the commits when I merge it, and delete the branch after I've merged it.

closing this as it is incorrect


[master] Weird borders

For some reason that I have yet to identify, there will be borders drawn when inbetween a space transition. After a transition ends, these borders disappear and only the focused border remains (as expected).
These borders also persist after the focused and marked border has been disabled.
This causes huge lag when trying to perform space transitions using gestures.

I think the cause of this is that borders aren't getting reused, i.e. each time we change space a new borders is created.

I'm happy to look into this (it might be my code causing the problem!) - I'm a bit confused by the report though.
When I do a space transition (e.g. go to space left) with keystroke, I see the active border disappear from the old space, and re-appear in the same position on the new space at the beginning of the transition. At the end of the transition, the border resizes to the active window on the new space. No other borders are visible throughout this.
This doesn't seem much like what you are describing. Is it easy to upload a screencast or something?

You appear to be using a keystroke

When I do a space transition (e.g. go to space left) with keystroke

The ticket describes the issue is with gestures

This causes huge lag when trying to perform space transitions using gestures.

Could that be the reason you have trouble repoing the issue @akdor1154?

just tested with a gesture (three finger swipe on mbp trackpad) and behaviour is the same as I described before.

So I can reproduce this by transitioning to an empty space and going back to some other space. There will now be 1 additional border.

Unable to reproduce in version 4.0.4


Added core GIT to list of GUIs

and linked to the https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools page that includes dozens of options.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@tjsullivan1 thanx for your contribution


Add a new instructlab.sdg.taxonomy_to_samples API

Take a first pass at separating out the data preprocessing steps from generation by adding a new top-level API (and temporary CLI) to invoke preprocessing but not generation.
This adds a simple CLI usable within SDG itself to do all taxonomy preprocessing via:
python -m instructlab.sdg.cli.taxonomy_to_samples --taxonomy-path /path/to/my/taxonomy/ --output-dir /path/to/my/output/samples --log-level DEBUG
Alternatively, the same thing can be accomplished via a Python API call such as:
from instructlab.sdg.taxonomy import taxonomy_to_samples

output_files = taxonomy_to_samples(
    "/path/to/my/taxonomy",
    "/path/to/my/output/samples",
)
# Do something with the jsonl output files in code
# Loop through each one and read its contents into a Dataset or whatever you need

See the code comments in src/instructlab/sdg/taxonomy.py for more usage details.

@jwm4 Does something like this help with some of your needs? A top-level API to only do the preprocessing steps but not any data generation?


adding changes in the nav bar and the header image

Star the repo

Already starred &
I have added the changes


SelectFilter formatter is not working properly

By using multiselectFilter or selectFilter like below, the content of column 'Category' isn't displayed and with selecting an option, no row is displayed.

Here is my code:
render() {
  const selectOptions = {
    0: 'A',
    1: 'B',
    2: 'C'
  };
  const columns = [
    {
      dataField: 'id',
      text: 'ID'
    },
    {
      dataField: 'category',
      text: 'Category',
      formatter: cell => selectOptions[cell],
      filter: multiSelectFilter({
        options: selectOptions,
      })
    }
  ];
  return (
    <BootstrapTable
      keyField='id'
      data={data}
      columns={columns}
      filter={filterFactory()}
    />
  );
}

Here is my source of how to use multiSelectFilter.
If I modify selectOptions to
const selectOptions = {
  "A": "A",
  "B": "B",
  "C": "C"
}

the filter works fine.

So I think the formatter is not working as expected and searches for the key instead of the value in the table.
This is what my json data looks like:
[{
  "id": 1,
  "category": "A"
}, {...}, {...}]

Do you have any idea how to fix this?
Thanks!

@NadineSch that is wired, I will check this out.

@NadineSch if you raw data is
{
  id: 1,
  category: "A"
}

I mean without double quotes

@AllenFang no I receive my data in json format, therefore with double quotes. You think this could be an issue?

@NadineSch lol
I probably got the problem....
ok, https://react-bootstrap-table.github.io/react-bootstrap-table2/storybook/index.html?selectedKind=Column Filter&selectedStory=MultiSelect Filter&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel
that is example you reference and the selectOptions is like below
const selectOptions = {
  0: 'good',
  1: 'Bad',
  2: 'unknown'
};

Actually, 0, 1 and 2 is just the column value of Product Quailty but I use column.formatter to show it as good, bad or unknow.
so if your raw data is not like above example, you probably don't need the column.formatter. I think your data is already A, B, C.
Please do let me know if you still have any question and reopen this issue again, thanks

@AllenFang
thanks for your fast reply.
So you're right with the formatter, my raw data is A, B or C and not 0, 1 or 2.
Does that mean it's necessary that the value i'm filtering for (A, B or C) is the key-attribute of the selectOptions-Object? Like:
const selectOptions = {
  A: 'Filter by A',
  B: 'Filter by B',
  C: 'Filter by C'
}

[key]: what I'm looking for in my raw Data
[value]: how to name it in my filter-menu (?)
If I'm getting this right I'm clear now, thanks!

@NadineSch yes, you are right!


[runix/pgadmin4] custom command doesn't accept arguments

When you want to use a custom command you cannot use any arguments.
I.e. the following does not work:
command: ["sh","-c","sleep infinity"]

But a command without arguments is fine:
command: ["top"]

The reason is that it's threaten as a string so cannot find an executable with spaces.

You can try the following then instead:
command: ["sh"]
args: ["-c", "sleep", "infinity"]

hm, I should try this. I just don't see how it would be handled in the template in this case and nothing in the docs, so I didn't try


Redirect tensorflow/tensorflow/examples to examples repo in examples/README

This template is for miscellaneous issues not covered by the other issue categories.
For questions on how to work with TensorFlow, or support for problems that are not verified bugs in TensorFlow, please go to StackOverflow.
If you are reporting a vulnerability, please use the dedicated reporting process.
For high-level discussions about TensorFlow, please post to<EMAIL_ADDRESS>for questions about the development or internal workings of TensorFlow, or if you would like to know how to contribute to TensorFlow, please post to<EMAIL_ADDRESS>

Here's a brief about the issue...
In this repo (tensorflow/tensorflow/examples) the README is enough with examples and all other things, but still it has a statement "This directory is not actively maintained" which is fine, but I feel a statement must be included along with it... "Refer this repo for more examples as this folder is not actively maintained" so that newcomers will know and refer to that link

And TF community, please assign me this issue, I want to work on it! :)

@alphaX86
Please feel free to submit a PR.Thanks!


Fix fragility issues in all.sh

Fix some issues that don't break all.sh on a pristine checkout, but make it fragile in a tree where you've been doing development.

Fix make WINDOWS_BUILD=1 clean on non-Windows hosts.
In keep-going mode, don't hard-fail on some auxiliary script or test.
Fix #1691 #1713: check-files.py complaining about files in .git or in third-party subtrees.
Fix make apidoc looking for files in unintended subdirectories.
Don't fail on a spurious error if ASLR can't be disabled (not an issue on developer machines, but this would let us remove the don't-enforce-ASLR configuration from some CI jobs).

Backports: #2032 for 2.7, #2033 for 2.1.

all.sh run on CI: https://jenkins-internal.mbed.com/job/mbedtls-release/716/

@Patater The WINDOWS_BUILD fix is for an issue introduced by #930. The others are unrelated, but “don't hard-fail on some auxiliary script” modifies one line that was introduced in #930.

I made another commit that will allow us to run the CI with ASLR enforced.

@Patater @sbutcher-arm I rewrote the commit that modifies check-files.py to exclude other directories, including a fix for #1691. The original history is in https://github.com/gilles-peskine-arm/mbedtls/tree/all.sh-fragility-201809-1. Please re-review.

New run of all.sh at https://jenkins-internal.mbed.com/job/mbedtls-release/727/

I took the liberty of editing the PR description by adding "fix" in front of an issue number so that github picks it up as fixed by this PR.

@sbutcher-arm Thanks for reviewing. I removed the yotta line from check-files.py.

retest

Jenkins failed on the BSD timing test, which is a known issue and as good as a pass. Therefore marking as 'ready for merge'.


SHA in user agent

I want the version string to include the git commit that built it:
$ git lfs version
git-lfs/0.5.3 (GitHub; darwin amd64; go 1.3; git 0cf7c47)

This PR gets it working with script/run version, but not script/bootstrap.
$ script/bootstrap
# github.com/github/git-lfs
/opt/boxen/chgo/versions/1.3/pkg/tool/darwin_amd64/6l: unknown flag -X github.com/github/git-lfs/lfs.GitCommit 22bb4ab

2015/07/28 16:04:56 exit status 2
exit status 1

I'm really not sure why it fails here when it works in script/run or running go build manually.
A workaround is to create a file like lfs/aaaaa_version.go:
package lfs

func init() {
  GitCommit = "22bb4ab"
}

Such a file could be created and then trashed during every script/bootstrap run.

Excellent :+1:


Initial changes to the CMake and make session

Typos and missing words in the make session, but do commit to get the start of Wednesday according to planned schedule

Thanks! I will also submit my changes as PR tonight so that you can review my stuff.


Adding Changes to support smoke test on Datahub deployed on kubernetes Cluster

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Changes made in https://github.com/datahub-project/datahub/pull/5287. For any more work required we will have a new PR


Fix #7572 and Moving sitemap_search_selector from tools to new route

This PR fixes the issue with #7572 and also moves sitemap_search_selector to the CCM route system
I have kept the old sitemap_search_selector in tools incase of any packages using it (unlikely but don't want to BC break)

Ping.


install-plugins.sh fails due to timeout

Hi,
I'm trying to use install-plugins.sh from China. I understand this may not be a common location but due to poor internet I see the connection timeout.
In the current script, I can see a timeout of 5 seconds.
Is it a valid idea to increase this or make it configurable at least? Or instead do people with poor connections need to manage their own version of this script?
Thanks!

see #361


Fixed onChanged for events

Based on documentation (http://fullcalendar.io/docs/event_data/updateEvent/)

event must be the original Event Object for an event, not merely a reconstructed object. The original Event Object can obtained by callbacks such as eventClick, or by the clientEvents method.

I changed eventsWatcher.onChanged to work with original Event Object obtained by clientEvents method based on _id
This should fix #186

+1 for merging this! Spend the whole afternoon understanding looking after this bug :/ Thanks for fixing it!

It still has yet to catch a collaborator or owner's attention... This is a major feature which is broken. Anyone out there?

hey sorry about the delay on this guys. The PR looks like a good addition, but could you help out and rebase this up for me? And just to make sure, but you guys are still seeing this issue with the latest master correct?
Thanks

Rebased at #257


add volto-subsites

@nileshgulia1 I don't know about this dependency. As you can use volto-eea-kitkat independently, without EEA Design System / EEA Website Theme I don't this volto-subsites belong here.

@nileshgulia1 He he, not that simple as you used the develop branch. You'll have to revert al the changes :smile:


There is a need to import object variations for specific endpoint

Basicaly it means there is a need to support relations for any document. I'm not so sure if that is reasonable to support it natively in API bundle. It's too complex to be tied to a products or some other domain. Curently we are trying to make it more universal version where we can provide an easy way to use Restful API for elasticsearch.

Related to https://github.com/ongr-io/Demo/issues/157

Blocks https://github.com/ongr-io/FilterManagerBundle/issues/129

After some investigation looks like the ApiBundle is not the right place to do that. Most likely we need to create some custom controller for it, or as a plan B some helper.

Closed with #113


Pointer casts in CTFE: fixes 6792 and 6800

Disallow pointer casts which involve reinterpret casts. These commits allow as many other casts as possible: const casts and changes of signedness (int* to uint*). Also casts to void*, and allow casts back from void*, but only back to the original type.
6792 [CTFE] ICE with pointer cast of indexed array
6800 [CTFE] dangerous pointer casts should be rejected

Obsoleted by pull 488.
https://github.com/D-Programming-Language/dmd/pull/488


Add aromaticity model support as per 125

This adds aromaticity model support as per #125 . Also adds a version attribute at the same time.
C Bayly needs this ASAP so I'm trying to get something rough up immediately for him to use. I'll revisit it likely early next week to polish.

We've verified that this works. On c12c(cccc1)occ2 the bond 6-7 (among others) ends up different with and without the MDL aromaticity model in Chris's "super preliminary draft parm@frosst-y SMIRFF for bonds".
But, I have to run off for the weekend, so Bayly will be working/testing.

Please add nosetests! "we've verified that this works" is not future proof!

@jchodera - yes, will add nosetests. That's why this is still [WIP]. I've just been focused on getting things done which must be done now before implementing tests. :)

Added tests verifying not just that it runs but also that the choice of aromaticity model has the desired effect. Should be ready to merge once it passes tests.


move to dev, and update batch_processing

Done ! The result is not perfect but really nice. If it's OK for you we can close this.
In blue: automatic GM segmentation, in Red-Yellow: template GM registered on mt1

nice!  so, did you update the batch_processing accordingly? (i started to modify it but it was incomplete). Also, did you see the info on issue #536?
Another thing to investigate is the scaling of the probabilistic map. We need to make sure that the registered WM + GM equals 1 in the spinal cord (it should). Maybe play with interpolation methods.

Yes I did (modify the batch_processing and see the info)
I just check : the sum of the registered WM + GM gives 1 in the SC.  Sometimes the visualization is a bit tricky because the threshold on the color map exclude the value 0.5 on both WM and GM so if a voxel is exactly at 0.5 you don't see it but the sum is correct.

I also changed the doc on sourceforge for sct_register_graymatter :
https://sourceforge.net/p/spinalcordtoolbox/wiki/register_to_metric/
and added a section tips & tricks to the list of tools : we could add other information about registration  on that section (like what to do when register multimodal fails).

awesome :+1:


Github API Rate Limit Exception Notification Queue Renders VSCode unusable

I'm trying to migrate a large project to my online github repo but I rack up modal API rate limit notifications, which are subsequently queued, and must be individually dismissed, rendering vcode unusable, requiring a Windows taskkill operation. Reinstalling vscode has no effect since the issue is with github and the remote repository extension; the extension cannot be uninstalled due to the UI being locked by the modal notification queue; and deleting the .vscode extensions folder, leaves the notifications queued on the repo, reviving the issue upon reinstalling the extension and or vscode.

Note: Worldwide cartel malware is rendering Humanity unusable. Recommend Mother Nature marking blight as won't fix to be queued up for subsequent bio-wipe and permanent deletion without reset. Good riddance to DNA Earth trash.

Thanks for your patience--can you please provide steps to repro, or a screen recording of the issue you're encountering?

Thanks for the reply. It's good to know parts of the world are still functional.
This Youtube video explains my issue and the way they (temporarily) patch it.
https://youtu.be/7qFHjlUi2iI?si=8DqYSYo6CWRx6EA3


Compatibility with Pod Identity?

Is this mechanism also compatible with passing credentials through Pod Identity?
I am testing switching from IRSA to Pod Identity in a K8s cluster and pods which have IRSA configured on them can successfully connect to MSK using this module, whereas each time I try to do it via pod with Pod Identity role, it fails, although I can connect to other services allowed by the IAM role so the mechanism itself works fine.
Is there some specific configuration required for this to work here?
I am a bit at a loss if this is this library problem or kafka's client, but I tried using the newest 3.6.1 from here
https://archive.apache.org/dist/kafka/3.6.1/ alongside with version 2.0.2 of this library and it still throws same errors:
WARN Exception loading credentials. Retry Attempts: 0 (software.amazon.msk.auth.iam.internals.MSKCredentialProvider)
aws_msk_iam_auth_shadow.com.amazonaws.SdkClientException: Unable to load AWS credentials from any provider in the chain: [aws_msk_iam_auth_shadow.com.amazonaws.auth.AWSCredentialsProviderChain@36877a4d: Unable to load AWS credentials from any provider in the chain: [EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY)), SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey), WebIdentityTokenCredentialsProvider: You must specify a value for roleArn and roleSessionName, software.amazon.msk.auth.iam.internals.EnhancedProfileCredentialsProvider@3bdccd22: Profile file contained no credentials for profile 'default': ProfileFile(profilesAndSectionsMap=[]), aws_msk_iam_auth_shadow.com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper@6f468d40: The full URI (http://<IP_ADDRESS>/v1/credentials) contained withing environment variable AWS_CONTAINER_CREDENTIALS_FULL_URI has an invalid host. Host should resolve to a loopback address or have the full URI be HTTPS.]]
	at aws_msk_iam_auth_shadow.com.amazonaws.auth.AWSCredentialsProviderChain.getCredentials(AWSCredentialsProviderChain.java:142)
	at software.amazon.msk.auth.iam.internals.MSKCredentialProvider.loadCredentialsWithRetry(MSKCredentialProvider.java:158)
	at software.amazon.msk.auth.iam.internals.MSKCredentialProvider.getCredentials(MSKCredentialProvider.java:145)
	at software.amazon.msk.auth.iam.IAMClientCallbackHandler.handleCallback(IAMClientCallbackHandler.java:100)
	at software.amazon.msk.auth.iam.IAMClientCallbackHandler.handle(IAMClientCallbackHandler.java:77)
	at software.amazon.msk.auth.iam.internals.IAMSaslClient.generateClientMessage(IAMSaslClient.java:139)
	at software.amazon.msk.auth.iam.internals.IAMSaslClient.evaluateChallenge(IAMSaslClient.java:96)
	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.lambda$createSaslToken$1(SaslClientAuthenticator.java:534)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.base/javax.security.auth.Subject.doAs(Subject.java:423)
	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.createSaslToken(SaslClientAuthenticator.java:534)
	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.sendSaslClientToken(SaslClientAuthenticator.java:433)
	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.sendInitialToken(SaslClientAuthenticator.java:332)
	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.authenticate(SaslClientAuthenticator.java:273)
	at org.apache.kafka.common.network.KafkaChannel.prepare(KafkaChannel.java:181)
	at org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:543)
	at org.apache.kafka.common.network.Selector.poll(Selector.java:481)
	at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:571)
	at org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.processRequests(KafkaAdminClient.java:1381)
	at org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.run(KafkaAdminClient.java:1312)
	at java.base/java.lang.Thread.run(Thread.java:829)

AWS Docs are saying here https://docs.aws.amazon.com/eks/latest/userguide/pod-id-minimum-sdk.html:
"EKS Pod Identities have been added to the Container credential provider which is searched in a step in the default credential chain. If your workloads currently use credentials that are earlier in the chain of credentials, those credentials will continue to be used even if you configure an EKS Pod Identity association for the same workload."
I am wondering if the problem is in:

library itself
kafka client
client properties (do they need to be adjusted?)

Would appreciate any hints here.
Thanks

Hi. Did you find any fix for this?

nope, but was not looking too hard really

The issue appears to be with the version of the sdk used in this project -- v1 is not supported
https://docs.aws.amazon.com/eks/latest/userguide/pod-id-minimum-sdk.html
https://github.com/aws/aws-sdk-java/issues/3062#issuecomment-1861905542
I'm not very familiar with this space, but based on this commit it looks like the project uses v1.12.638 on the latest release
https://github.com/aws/aws-msk-iam-auth/commit/ee55c0ffdf98f6cef45f25ee5179155ca9515d77
It looks like to support PodIdentity, this project would need to update that version. I have no idea what that entails however.

Can you try this with the PR: https://github.com/aws/aws-msk-iam-auth/pull/157
This updates all the internal usages of Java sdk v1 to v2.

Hello,
can this be fixed and release asap ? this is impacting out implementation and we are stuck because of this issue.

Can you try this with the PR: #157
This updates all the internal usages of Java sdk v1 to v2.

Hi @rajarshp , sorry for long radio silence,
I'll try to see if I can test it soon, although have not done it before without a release I can point my terraform automation to so will have to research how to do it.

I've noticed that it was merged and see there is version 2.0.3 available now with "Upgrade AWS SKD version" comment (probably should be SDK?) so I gave it a spin today but unfortunately still see the error:
WARN Exception loading credentials. Retry Attempts: 0 (software.amazon.msk.auth.iam.internals.MSKCredentialProvider) aws_msk_iam_auth_shadow.com.amazonaws.SdkClientException: Unable to load AWS credentials from any provider in the chain: [aws_msk_iam_auth_shadow.com.amazonaws.auth.AWSCredentialsProviderChain@17ead63f: Unable to load AWS credentials from any provider in the chain: [EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY)), SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey), WebIdentityTokenCredentialsProvider: You must specify a value for roleArn and roleSessionName, software.amazon.msk.auth.iam.internals.EnhancedProfileCredentialsProvider@f94bdf7: Profile file contained no credentials for profile 'default': ProfileFile(sections=[]), aws_msk_iam_auth_shadow.com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper@6815eca9: The full URI (http://<IP_ADDRESS>/v1/credentials) contained withing environment variable AWS_CONTAINER_CREDENTIALS_FULL_URI has an invalid host. Host should resolve to a loopback address or have the full URI be HTTPS.]] 	at aws_msk_iam_auth_shadow.com.amazonaws.auth.AWSCredentialsProviderChain.getCredentials(AWSCredentialsProviderChain.java:142) 	at software.amazon.msk.auth.iam.internals.MSKCredentialProvider.loadCredentialsWithRetry(MSKCredentialProvider.java:158) 	at software.amazon.msk.auth.iam.internals.MSKCredentialProvider.getCredentials(MSKCredentialProvider.java:145) 	at software.amazon.msk.auth.iam.IAMClientCallbackHandler.handleCallback(IAMClientCallbackHandler.java:100) 	at software.amazon.msk.auth.iam.IAMClientCallbackHandler.handle(IAMClientCallbackHandler.java:77) 	at software.amazon.msk.auth.iam.internals.IAMSaslClient.generateClientMessage(IAMSaslClient.java:139) 	at software.amazon.msk.auth.iam.internals.IAMSaslClient.evaluateChallenge(IAMSaslClient.java:96) 	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.lambda$createSaslToken$1(SaslClientAuthenticator.java:534) 	at java.base/java.security.AccessController.doPrivileged(Native Method) 	at java.base/javax.security.auth.Subject.doAs(Subject.java:423) 	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.createSaslToken(SaslClientAuthenticator.java:534) 	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.sendSaslClientToken(SaslClientAuthenticator.java:433) 	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.sendInitialToken(SaslClientAuthenticator.java:332) 	at org.apache.kafka.common.security.authenticator.SaslClientAuthenticator.authenticate(SaslClientAuthenticator.java:273) 	at org.apache.kafka.common.network.KafkaChannel.prepare(KafkaChannel.java:181) 	at org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:543) 	at org.apache.kafka.common.network.Selector.poll(Selector.java:481) 	at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:571) 	at org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.processRequests(KafkaAdminClient.java:1381) 	at org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.run(KafkaAdminClient.java:1312) 	at java.base/java.lang.Thread.run(Thread.java:829)
although I am definitely using the new library
# ls ../libs/aws* ../libs/aws-msk-iam-auth-2.0.3-all.jar
Do I need to change client.properties in any way (or something else) to use it?

ok, got gradle set up and tried to build the newest version cloned but regardless of version used (8.7 or 7.6.4) it fails:
8.7
# gradle clean build
Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
org/gradle/api/plugins/MavenPlugin
> org.gradle.api.plugins.MavenPlugin

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.7/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 19s

7.6.4
# gradle clean build

Welcome to Gradle 7.6.4!

Here are the highlights of this release:
 - Added support for Java 19.
 - Introduced `--rerun` flag for individual task rerun.
 - Improved dependency block for test suites to be strongly typed.
 - Added a pluggable system for Java toolchains provisioning.

For more details see https://docs.gradle.org/7.6.4/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)

> Task :compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :javadoc FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':javadoc'.
> Javadoc generation failed. Generated Javadoc options file (useful for troubleshooting): '/aws-msk-iam-auth/build/tmp/javadoc/javadoc.options'

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.6.4/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 36s

Not sure about build fail, as it is passing for me. I am working on running tests, and release.

ok, got it working (installing java-devel helps....)
and the jar generated with gradle clean shadowJar works fine now! :1st_place_medal:

Hello,
when can we expect this fix to be released?

The PRs have been released as part of 2.1.0 Could you try and see if that resolves the issue.

Yes, I can confirm it works fine with 2.1.0!
Thank you, closing :)


Pulling Issues [The Compendium]

I will be keeping this checklist updated, so never fear someone having to make another one of these in a couple days time. Just comment underneath this thread with new issues.

[x] You can pull multiple items at the same time.
[x] Pulling currently doesn't take up a free hand
[x] Humans collide with each other when pulling them
[x] When pulling multiple items, clicking the "pull" icon only stops pulling the first object pulled and goes away. You need to control-click on the rest of the objects to stop pulling them.
[x] Pulling collidables is very jerky and can even kill you when pulled diagonally.
[x] When pulling something that is anchored, walking out of range of it will not stop pulling it and will stick you with the slowdown till you stop pulling.
[x] Pulling speed can be inconsistent with pushing speed on the same object.
[x] Pulling doesn't change the sprite direction of the pulled entity based on the direction it's being pulled.

metalgearsloth's comment from a previous issue about pulling letting you transcend space and time...
Closing #2306, #1557, #2304, #1971, #1799 in favor of this thread.

[ ]  Pulling currently doesn't take up a free hand
PJB asked about this on the original pulling PR (https://github.com/space-wizards/space-station-14/pull/850#issuecomment-628290617), I'm not sure if a decision has been made about it.

I have made the decision that yes it should be done.

All issues fixed! Good job team!


fetch/getEntry returns null if the entry is free

fixes incorrect document outline object reference in pdf from #1041
the existing 'reading an XRef stream not implemented yet' error is incorrect

@pdfjsbot test


Build failed

I'm using https://jitpack.io for cmpile project, and it's failed:
(https://jitpack.io/com/github/timmolter/XChange/7c3ca254fd/build.log)
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/jitpack/build/xchange-yobit/src/main/java/org/knowm/xchange/yobit/YoBitAdapters.java:[134,18] cannot find symbol
symbol:   method join(java.lang.String,java.util.List<java.lang.String>)
location: class java.lang.String
As i undestad problem with  String.join("-", pairs)
What should i do? Wait while some one fixed it or create pull request for fix or change java compile version?

What JVM are you using?

As i say, i build it with jitpack io. And as i undestand, it using maven-compiler-plugin 1.7, cose this version set in pom.xml

Is String.join() Java 8? If so that should be replaced.

Yes, it's java 8. Should i create a pull request for it, or better wait while some one fix it, coze i'm not good in java :-)

That was probably me.  I'd accidentally commit some java 8 stuff but thought i'd removed it.  The build went green I'm sure.

https://github.com/timmolter/XChange/pull/1736

It's strange to me that Travis CI and my IDEs (Eclipse and Intellij) didn't catch this issue because the JRE is defined as 1.7 in the pom.xml. I'm using JDK 8, but it used to work fine and catch these issues.


Question: Calling Sentry from Long Running Process

I have a function that is called both by a short-lived phoenix process and by a other longer running process that are not invoked via a web request.
This function adds extra context (with unique key values) every time it is called.
My question is... when this is called from a long-running process... is the process dictionary just going to grow and grow since it will never be purged?
Thanks!

@ryan-mahoney From what it sounds like, yep.  The long-running process will continue adding to its process dictionary.  It's difficult to say if it will grow to the point of being problematic though.

Thanks for your answer -- that is what I saw in the code, but I just wanted to be sure.
What I've decided to do is count the number of messages that I've put into the process table for sentry. When the count get's above a certain threshold, I purge the table.
I expect that this approach will have low overhead and it will prevent the possibility of a slow memory leak from becoming a problem.

Glad to help clarify!
Your solution sounds good to me, but if there's ever something Sentry can do to make it easier going forward, I'd be happy to make it happen.  For now though, I'll close this issue 🙂


hash key is not correct when some returned parameters are missing

Hello there,
When some request.args.get() is missing (in my case, no "photo_url") and None is returned as the default value, key + '=' + data[key] would result in error since data[key] is None. I have tried checking for None value, to skip the whole key + '=' + data[key] line, or make it to be key + '=' + '', both give a wrong hash.
May you please help take a look on this?
Thanks.

I am probably too late, but here is what I've done to fix this:
if telegram_data['photo_url'] == None:
         telegram_data.pop('photo_url', None)

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!


[Feature]: Support internet throttling

What is your Test Scenario?

I have a PWA application and scenario is simple: turn off internet and launch this application. As a result, I want to see that service worker cached some data and this data is loading from cache.
What are you suggesting?

Create a syntax just like in protractor:
test('no internet', async t =>{
t.setNetworkConnection() // just like in protractor
})

What alternatives have you considered?
LightHouse can emulate throttling but only for chrome and chromium-based browsers

Any update on this please.

@AndreyBelym, any update?

In the example provided, No Network was specifically called out, but the headline suggests implementing Network Throttling. Supporting throttling such as controlling upload and download speed and latency is needed as well, to be able to emulate slow/poor network conditions in the test.

Hi @TomRodano,
Thank you for the additional information. We will consider it when we take this enhancement into work.


Error when loading multiple instances at the same time: NameError: name 'config' is not defined

In our setup, we initialize multiple instances (6-8) of django-summernote's SummernoteTextFormField at the same time. Often this crashes, unfortunately not in a predictable or reproducable manner with the error: NameError: name 'config' is not defined at this line: https://github.com/summernote/django-summernote/blob/master/django_summernote/views.py#L34
Since my debugger would not stop at this code segment, I put print statements in there and saw that they were called in a non-sequential way. This means that the execution of the __init__ method is done concurrently and so I assume that there is some kind of race condition somewhere responsible for ovewriting or deleting the config reference, which then results in the error I see.
I could however circumvent this, by putting one line into the beginning of the __init__ method where I load the global reference to config into a temporary variable config_tmp right away, and then replaced all other occurences of config with this config_tmp. Then the NameError did not occur anymore.
So I assume that the temporary variable stores whatever the 'global' variable config is referencing, and by this keeps it from being deleted or overwritten.
My modified __init__ method looks like this:
    @using_config
    def __init__(self):
        config_tmp = config # <- Insertion of temporary variable

        super(SummernoteEditor, self).__init__()

        static_default_css = tuple(static(x) for x in config_tmp['default_css'])
        static_default_js = tuple(static(x) for x in config_tmp['default_js'])
        self.css = \
            config_tmp['base_css'] \
            + (config_tmp['codemirror_css'] if has_codemirror_config() else ()) \
            + static_default_css \
            + config_tmp['css']

        self.js = \
            config_tmp['base_js'] \
            + (config_tmp['codemirror_js'] if has_codemirror_config() else ()) \
            + static_default_js \
            + config_tmp['js']

Whatever the deeper lying cause of this I can not tell, not even if it might be actually due to our setup and not due to django-summernot itself. For this our setup involves:

Django 2.1.9
django-crispy-forms==1.7.2 (where the django-summernot widgets are integrated into)
django_summernote.fields.SummernoteTextFormField

Just thought I'd document it here, in case it might be due to django-summernote or someone else encounters the same problem with a similiar setup.

@steffres I also see this error from time to time

I have this error after deploying to AWS


Fixes Falkon looking in the wrong directory for Qt resources.

modified:   build
modified:   checksums
new file:   files/qt.conf
modified:   sources
modified:   version

Please fill out the template.
Read: https://k1ss.org/style
Read: https://k1ss.org/guidestones

Installed manifest of package
(cat /var/db/kiss/installed/<pkg_name>/manifest)
http://ix.io/2i1o

Existing package

[x] I am the maintainer of this package.

Nice. /usr/bin seems like an odd place for this file to live but this can always be changed later on. :+1:


reference community docs in readme

I was having issues getting started on MacOS M1. After consulting the Plutus community docs, everything worked in all its glory. I believe this PR can save future MacOS users quite a bit of time (I wasted several hours trying to nix-build without the correct  configuration).
Related: https://github.com/input-output-hk/plutus-community/pull/15
This closes #632 .
Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[X] Commit sequence broadly makes sense
[X] Key commits have useful messages
[ ] Formatting, PNG optimization, etc. are updated

PR

[X] Self-reviewed the diff
[X] Useful pull request description
[ ] Reference the ADR in the PR and reference the PR in the ADR (if revelant)
[ ] Reviewer requested

@erichulburd just a quick nudge if you're still interested in completing this Pull Request, please see @ak3n  comment
You may transition the PR to Draft mode if you require more time.
Thank you for your contributions, -k


Roadmap to v0.3-alpha

Spider v0.3 will be the first usable, thought not production ready release.
Features:

A DriverInterface Contract and abstract for creating drivers
A basic, fluent CommandBuilder that performs CRUD operations, but does not handle traversals or relationships (those come in 0.4)
Predictable and versatile response formats.
Fully documented, both at code-level and in guides at http://spider-ogm.readthedocs.org/

Will not include, yet

Traversal query builder
Models
Schema
Unified Spider

To be completed:

[x] Merge new Driver and Responses PR #20
[x] Integrate data-manager, Base\Collection, and Base\Object throughout the system. See #12
[x] Add return formatting methods to  CommandBuilder set(), tree(), path(), scalar(). Default to set.
[x] Add exceptions from #17
[x] Refactor the OrientCommandProcessor See #18
[x] Remove the LanguageProcessor Convention that couples them to Drivers
[ ] Complete GremlinCommandProcessor and NeoCommandProcessor
[x] Refactor system to use consistent terms (e.g. properties, not fields) See #15
[x] Update and build documentation

A solid draft of documentation is up at http://spider-ogm.readthedocs.org/en/develop, including some internals notes and a rough roadmap.

ok Cool!!
I've made changes to the builder (the ones we spoke of) locally, but it's made the test suite fail and while I was going in and correcting the tests I figured I would try and fix some of the spaghetti stub issues we had (because one of them was leading to some of the errors I was having). So it might be a heavier PR than originally expected. I'll try and get that in today (hopefully I find the time).
It then shouldn't be too long before I get a CypherProcessor up and running. GremlinProcessor is a bit of another issue it might need more thinking. I'll create an issue once I get there.

Sounds great. I'd like to do a prerelease for after CypherProcessor is up. We can leave GremlinProcessor unsupported for now. At least until we work out how the CommandBag will hold traversals.

Oh yeah, be sure to pull or look at a few recent commits. I switched the constructor arguments in Connection so you can pass a config connection up front. That should be the only change that matters to the rest of the code.
I am done committing to the develop branch for a while. I won't have as much time next week, so I'm going to create a branch and start working on the top-level Spider and a way to integrate Events, Caching, and Logging into the loop, even if no implementations.
After that: Traversals in full force.

Added a couple housekeeping tasks

ok what's left here? do you want to set up a scrutinizer for style consistency and such?

I could configure the account if you can give me rights for it (It would probably be best if you created it since you own the organization)

I am updating docs and scrutinizing now. How do I give you rights? Do you need admin rights? You should have those anyway. The bus factor and all that.

You are now an admin. I don't what other rights to give you. I think coveralls requires you to be public, but I see you made yourself public already.

Thanks. I'm trying to figure this one out. Scrutinizer is complaining about something I'll see if I can sort it out

I am scrutinizing for style now. I've also updated the docs. Pushing in a minute.

Ok it looks like I don't have administrative rights to the repo for some reason. (only push & pull rights). The admin group must be just shy in terms of rights.

Weird. I have a ticket open with coveralls, but no matter how hard I try, I can't get the repos to sync. I also created another user, spider-ogm, in hopes it would sync, but that was to no avail. Is there another code coverage system you like? I'm not married to coveralls.

We seem to be good here.


Trafficserver has more read bytes than Nginx

I plan to replace my existing Nginx with Trafficserver (with range plugin)。And in a comparison test, I found that Trafficserver reads significantly more bytes than Nginx for the same HTTP Range request, basically a 2-3x difference. However, the number of write bytes is equal.
I didn't change much in my configuration file, I turned on "Read While Writer" and turned on RamCache.
There is also enough hard drive space, 12*8TB.
Here is my remap configuration:
map http://<IP_ADDRESS>/ http://x.x.x.x/ \
    @plugin=slice.so  @pparam=--blockbytes=2m @pparam=--remap-host=loopback

map http://loopback/ http://x.x.x.x/ \
    @plugin=cachekey.so @pparam=--include-headers=Range @pparam=--remove-prefix=true @pparam=--remove-all-params=true \
    @plugin=cache_range_requests.so @pparam=--no-modify-cachekey @pparam=--consider-ims

I can't find a reason for this, any suggestions for troubleshooting?
trafficserver：

Nginx：

I have a guess, is it because the slice plugin sets two rules that cause the read byte count to double?

When using slice with loopback into the same remap rule we use a 'php != 0' filter on our logs to remove the loopback served bytes.  I hope this helps.

When using slice with loopback into the same remap rule we use a 'php != 0' filter on our logs to remove the loopback served bytes. I hope this helps. The loopback part might also qualify as an internal transaction as well for code purposes (needs verification).

Unfortunately, it doesn't help, the IO is actual disk IO.


User account display UI

Note: this is just UI -- on the preferences page the user would be able to see a 'tap to login' button and their name if they are already logged in.  Those changes would persist in the new 'user' Redux store.  Also there is an appSettings USER_LOGIN.ENABLED which is set to false, so until we turn that to true nothing new will happen.
I wanted to get this merged as a start / proof of concept before I started making changes to actually implement auth.  Let me know what you think

Looks good.


Include syntax-dynamic-import in stage-2 docs

@lourd thanks for the fix! made a slight tweak and alpha sorted the plugins

You're quite welcome, thanks for the quick responses and action!


Eagerly emit reflection metadata as decls are emitted

Rather than collection nominal type and extension decls and emit
reflection metadata records in one go, we can emit them as they
are encountered and instead collection builtin types referenced
by those at the end.

@swift-ci Please smoke test

Looks like some minor ordering changes in IRGen, which is expected. Updating the tests.

Merged manually.


Code workflow

This pipeline configuration builds the application and produces a build for the release configuration.

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


Improve OS X installation instructions

Follow up from https://github.com/sparklemotion/nokogiri/issues/1504
Nokogiri installation instructions here:
http://www.nokogiri.org/tutorials/installing_nokogiri.html#mac_os_x
Should assume that you're on a fresh OS X installation.
Suggestions:

If Xcode and Xcode command line tools are not installed, then instruct downloading it from Mac App Store and then $ xcode-select --install
if RVM is required, instruct to install it.
Instructions should work for new OS X El Capitan (v10.11.x) installations (currently they're supported for up till OS X Yosemite (v10.10.x))

Are you aware that the installation instructions are open-source and open to pull requests? https://github.com/sparklemotion/nokogiri.org-tutorials
I got a PR merged a while ago, and it was really fun! Well, not really fun. But maybe good for my karma.

Shouldn't this stay open till https://github.com/sparklemotion/nokogiri.org-tutorials/pull/48 is resolved?


chore(main): release 0.0.7

:robot: I have created a release beep boop
0.0.7 (2024-07-28)
Bug Fixes

update bump actions/setup-node from 3 to 4 (#19) (8eae436)
update bump url from 0.11.3 to 0.11.4 (#20) (891a358)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.0.7
:sunflower:


DOCS link provided not working for failed CIS controls

Describe the bug
The DOCS link provided after scanning is not working for CIS controls.
Steps To Reproduce
Steps to reproduce the behavior:

Scan Resources/Cluster with verbose flag
Click on the DOCS link provided for failed CIS controls

Expected behavior
Should take user to the documentation page of CIS control.
Actual Behavior
404 page not found.

Reason:

For cis-5.7.3 control, the link provided is https://hub.armosec.io/docs/cis-5.7.3. But the actual address is https://hub.armosec.io/docs/cis-573. This is the case with other CIS controls too.

Hi, Thank you for reporting.
@YiscahLevySilas1 What is the link convention for the CIS controls?
We need to update the output. This issue might occur in the Kubescape cloud as well.
@yuleib

Hi, thanks for bringing to our attention.
We're currently changing the URL convention and will fix them both in Kubescape CLI and cloud.

solved by PR #909


Plugin text and example do not match

In https://github.com/lumeland/lume.land/blame/main/plugins/markdown.md#L64-L77 the text refers to the markdown-it-emoji plugin, but the example uses the markdown-it-anchor plugin.

good catch. It's fixed. Thanks!


[wiki][typo] ACSII -> ASCII

At page https://github.com/Microsoft/vscode/wiki/How-to-Contribute line 26, there is a typo:
Make sure your profile path only contains ACSII letters

my PR would be: https://github.com/isghe/vscode.wiki-doc/compare/fix-typo-ascii

Please create a PR

Please create a PR

It's not possible to create a PR on a wiki page.

@isghe You can make a PR on the wiki's repo, see: https://github.com/Microsoft/vscode-wiki

done https://github.com/Microsoft/vscode-wiki/pull/59


Release 1.21/1.21.1 on Modrinth/GitHub

Hey, would you like to release latest version to Modrinth/GitHub?

There's still some parts that I want to clean up before release, and I'm quite tied up with school and other projects at the moment, but I'll definitely release the new version soon!


Investigate high block processor time

Describe the bug
This is on a mainnet node, after capella block processor time is high for some blocks

is this due to high withdrawals on these blocks?
Expected behavior

Track withdrawals per block in a metric
If it's not due to withdrawals per block, add more metrics/debugs to figure out the reason
Make sure block processor time is <100ms consistently

@tuyennhv for this type of issues switch to heatmap and render the % of samples above a certain threshold. The timeline chart of average does not accurately signal the relevance of this issue

@dapplion I get what you mean but this is 1m chart and since we have 12s between blocks and a scrape duration of 10s this chart shows good result to some degree in a very short time :). More over bucket for this metric jump from 0.1s to 1s so you'll see no issue there
on each node it shows high block process time on random slots, number of withdrawals are 16 most of the time it's not likely a performance issue in state transition code, could be gc runs during state transition

this is not an issue in current unstable since network thread is in

and we have way better gc metric

should be fixed in v1.9


[Tag Manager] Error during creation of hierarchical Tags at level 4

After a sub tag is assigned at hierarchy level 4. An error pop-up appears and the view is no longer able to load any data

The error occurs in class ZCL_ABAPTAGS_TAG_UTIL in method BUILD_HIERARCHICAL_TAGS and occurs because of an unassigned field symbol:

Fixed with Commit fix: fixes issue for deep hierarchical tags


Shewit: UI/UX Design, 2 weeks

My UI/UX trial repository

Learning Objectives
1. Design Thinking

[ ] 🥚 User Empathy: You understand what user empathy is, and can use it
to understand a classmate's needs and help them plan a home page.
[ ] 🥚 Design Cycle: You will be able to describe the design cycle and
what steps you will take in each state (Empathize, define, ideate,
prototype, testing and implement).
[ ] 🥚 Double Diamond: You can separate the design and deliver phases of a
project. Design and delivery are a never-ending cycle, but it helps to be
clear when you are focusing one or the other.
[ ] 🥚 Stakeholder Interviews: You can interview another student to learn
their motivations, needs, and blocks
[ ] 🥚 Rapid Prototyping: You can use rapid prototyping techniques (such
as paper prototyping) to test initial design hypotheses and receive user
feedback.
[ ] 🥚 User Journeys: You can write user journeys for websites that you
use.

Week 1
What went well?

Understood the basic of ui/ux design.
Sketched my first prototype.
Figma account set up.

What went less well?
Lessons Learned

I followed UI design Fundamentals by scrimba and the resources provided by the coaches.
I watched some videos of how to use Figma and its functionalities.

Sunday Prep Work
I am prepping on Learn to use Figma for planning your websites.


drivers: uart: esp32: use config from device tree

The parity, stop bits and data bits config was hard-coded instead of taken from the device tree.

@marcowidmer thank you for your contribution!


Added DB connect for MongoDB

merging  feature/update_chassis_library_GDEV-236 into dev

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@c2b3b4d). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage        ?   46.40%
=======================================
  Files           ?        6
  Lines           ?      153
  Branches        ?        0
=======================================
  Hits            ?       71
  Misses          ?       82
  Partials        ?        0

Continue to review full report at Codecov.

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


Split pandas/core/window.py into pandas/core/window/*.py

Ideally we can do this in pandas master.
We can possible split into multiple files:

groupby.py
ewm.py
utils.py

Closed by https://github.com/pandas-dev/pandas/pull/27736


After updating the xcode to 16, i am not able to build the app

Steps to reproduce

Updated the xcode.
trying to build the app but i am getting error.

Expected results
The app should build in ios
Actual results
The app is not build
Code sample
Code sample
[4]: Mac Designed for iPad (mac-designed-for-ipad)
Please choose one (or "q" to quit): 2
Launching lib/main.dart on Abhinav’s iPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: 22LR5PHG5J
Running Xcode build...
Xcode build done.                                           16.5s
Failed to build iOS app
Could not build the precompiled application for the device.
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    Writing result bundle at path:
        /var/folders/wp/czy2ky5553vgdmg6s67j0w_c0000gn/T/flutter_tools.oDn0XW/flutter_ios_build_temp_dirlcd5Vh/temporary_xcresult_bundle

    /Users/abhinav/.pub-cache/hosted/pub.dev/url_launcher_ios-6.3.0/ios/url_launcher_ios/Sources/url_launcher_ios/Launcher.swift:22:1: error: type 'UIApplication' does not conform to protocol 'Launcher'
    extension UIApplication: Launcher {}
    ^
    UIKit.UIApplication:24:15: note: candidate has non-matching type '(URL, [UIApplication.OpenExternalURLOptionsKey : Any], (@MainActor @Sendable (Bool) -> Void)?) -> Void'
        open func open(_ url: URL, options: [UIApplication.OpenExternalURLOptionsKey : Any] = [:], completionHandler completion: (@MainActor @Sendable (Bool) -> Void)? = nil)
                  ^
    /Users/abhinav/.pub-cache/hosted/pub.dev/url_launcher_ios-6.3.0/ios/url_launcher_ios/Sources/url_launcher_ios/Launcher.swift:22:1: note: add stubs for conformance
    extension UIApplication: Launcher {}
    ^
    /Users/abhinav/Documents/Flutter Project/pmg-app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 18.0.99.
    (in target 'permission_handler_apple-permission_handler_apple_privacy' from project 'Pods')
    /Users/abhinav/Documents/Flutter Project/pmg-app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 18.0.99.
    (in target 'flutter_local_notifications-flutter_local_notifications_privacy' from project 'Pods')
    /Users/abhinav/Documents/Flutter Project/pmg-app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 18.0.99.
    (in target 'SwiftyGif-SwiftyGif' from project 'Pods')
    /Users/abhinav/Documents/Flutter Project/pmg-app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 18.0.99.
    (in target 'SDWebImage-SDWebImage' from project 'Pods')
    /Users/abhinav/Documents/Flutter Project/pmg-app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 18.0.99.
    (in target 'PromisesObjC-FBLPromises_Privacy' from project 'Pods')
    /Users/abhinav/Documents/Flutter Project/pmg-app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 18.0.99.
    (in target 'GTMSessionFetcher-GTMSessionFetcher_Full_Privacy' from project 'Pods')
    /Users/abhinav/Documents/Flutter Project/pmg-app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 10.0, but the range of supported deployment target versions is 12.0 to 18.0.99.
    (in target 'GTMSessionFetcher-GTMSessionFetcher_Core_Privacy' from project 'Pods')
    /Users/abhinav/Documents/Flutter Project/pmg-app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 18.0.99.
    (in target 'AppAuth-AppAuthCore_Privacy' from project 'Pods')```

</details>

### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>

### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.2, on macOS 15.0 24A335 darwin-arm64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.92.2)
[✓] Connected device (4 available)
    ! Error: Browsing on the local area network for Mohit’s iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources

Hi @rajatsingh0406, this has been fixed in url_launcher_ios: 6.3.1. Kindly run flutter pub upgrade to upgrade your dependency to 6.3.1.
Closing this as a duplicate of https://github.com/flutter/flutter/issues/155306

Running Xcode build...
Xcode build done.                                           37.5s
Failed to build iOS app
Could not build the precompiled application for the device.
Swift Compiler Error (Xcode): Method does not override any method from its superclass
/Users/abhinav/.pub-cache/hosted/pub.dev/flutter_inappwebview-5.8.0/ios/Classes/InAppWebView/InAppWebView.swift:1225:25
now getting this issues

Kindly report that on the flutter_inappwebview plugin repo

What worked for me:

flutter pub upgrade
upgraded url_launcher to 6.3.1 from 6.2.5

My solution

Flutter pub upgrade
Upgrade url_launcher to 6.3.1
If you run into the issue @rajatsingh0406 experienced update flutter_inappwebview to its latest version (6.1.5)
If you experience a firebase_database error go to Xcode => Runner => Build Settings and put "Allow Non-modular Includes In Framework Modules" to "yes"