Could not find an inverse kinematics solution.

Hey Paul,
I ran into a problem when I downloaded this code for the second time, saying ' x0 is infeasible. Could not find an inverse kinematics solution. '
Could you please help me?

Hey Liukey,
please refer to issue #9

Hey Paul,
ok, thank you very much for your reply.


MapView with multiple ShapeSources has Exception in onDidFinishLoadingStyle

Environment

Mapbox (GL) implementation: MapboxGL ("RNMapboxMapsImpl": "mapbox-gl")
@rnmapbox/maps Version: #main
Platform: Android
React Native Version 0.64.3
Platform OS: Android 13
Device: Pixel 6

Standalone component to reproduce
Stripped down EarthQuakes example from https://github.com/rnmapbox/maps/blob/main/example/src/examples/SymbolCircleLayer/EarthQuakes.js. Added a single ShapeSource <MapboxGL.ShapeSource id="temp" />
import React from 'react';
import MapboxGL from '@rnmapbox/maps';

const earthQuakesJSON = {
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          -120.8033371,
          36.2426682,
          5.47
        ]
      },
      "id": "nc73694191"
    },
  ]
}

class EarthQuakes extends React.Component {
  render() {
    return (
      <>
          <MapboxGL.MapView
            style={{ flex: 1 }}
            styleURL={MapboxGL.StyleURL.Dark}
          >
            <MapboxGL.Camera
              zoomLevel={6}
              centerCoordinate={[-122.09034,37.3892038]}
            />

            <MapboxGL.ShapeSource
              id="earthquakes"
              shape={earthQuakesJSON}
            >
              <MapboxGL.SymbolLayer
                id="pointCount"
              />
            </MapboxGL.ShapeSource>
            <MapboxGL.ShapeSource id="temp" />
          </MapboxGL.MapView>
      </>
    );
  }
}

export default EarthQuakes;

Observed behavior and steps to reproduce
Running on managed Expo workflow, screen goes dark and app crashes.
Logs are
Mapbox error, Exception in onDidFinishLoadingStyle, Object {
  "level": "error",
  "message": "Exception in onDidFinishLoadingStyle",
  "tag": "Mbgl-MapChangeReceiver",
}
at node_modules/@rnmapbox/maps/javascript/utils/Logger.js:103:20 in onLog
at node_modules/@rnmapbox/maps/javascript/utils/Logger.js:74:9 in subscribe
at node_modules/react-native/Libraries/vendor/emitter/_EventEmitter.js:135:10 in EventEmitter#emit

Expected behavior
Have used multiple sources on Mapbox GL web previously, if this isn't expected behavior from rnmapbox we could note it in https://github.com/rnmapbox/maps/blob/main/docs/ShapeSource.md

Follow-up: Still not sure why this works, but adding a shape to the ShapeSource lets this work. shape isn't required in https://github.com/rnmapbox/maps/blob/main/docs/ShapeSource.md though, so I assume this is still a bug?
import React from 'react';
import MapboxGL from '@rnmapbox/maps';

const earthQuakesJSON = {
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          -120.8033371,
          36.2426682,
          5.47
        ]
      },
      "id": "nc73694191"
    },
  ]
}

class EarthQuakes extends React.Component {
  render() {
    return (
      <>
          <MapboxGL.MapView
            style={{ flex: 1 }}
            styleURL={MapboxGL.StyleURL.Dark}
          >
            <MapboxGL.Camera
              zoomLevel={6}
              centerCoordinate={[-122.09034,37.3892038]}
            />

            <MapboxGL.ShapeSource
              id="earthquakes"
              shape={earthQuakesJSON}
            >
              <MapboxGL.SymbolLayer
                id="pointCount"
              />
            </MapboxGL.ShapeSource>
            <MapboxGL.ShapeSource id="temp" shape={earthQuakesJSON} />
          </MapboxGL.MapView>
      </>
    );
  }
}

export default EarthQuakes;

@michaelshum on iOS I get a reasonable error message:
It seems a ShapeSource should either have a shape or url.
 ERROR  Mapbox error SyleSource.addToMap id: Optional("temp") GeoJSON source must have a data value {"level": "error", "message": "SyleSource.addToMap id: Optional(\"temp\") GeoJSON source must have a data value"}

What is the use case for adding a ShapeSource without url or shape?!
We could improve error message on android, and also improve documentation.

Ah, hadn't seen the corresponding issue on iOS. Yup, it'd be great to update the error message on Android and note in documentation that additional ShapeSources require a data source. Re: your question, I was just testing (what I thought was) the most barebones version to debug.
However if a MapView has only a single ShapeSource it seems to work fine without shape: is there a reason why shape is not required when there's just one source, but is if it's a second one?

However if a MapView has only a single ShapeSource it seems to work fine without shape: is there a reason why shape is not required when there's just one source, but is if it's a second one?

Can you post an example where a single ShapeSource works fine without shape/url?!


[Request] Publish to Chrome Extension store

Description
@nganphan123
This is a pretty neat tool. Is this available on Chrome store? I don't really want to build the extension myself.

Stay tuned! It'll be published to Chrome soon.

Looks like it's online now on Chrome Store. Thanks @nganphan123!


boundary event coordinates do not cover bottom of visible map

node-red 1.06
worldmap 2.30.1 (issues was in 2.29.1 too)
I was noticing that my map did not have any points at the bottom and so I drew the bbox on the map and there is a gap at the bottom.  But, I expect  the bounding box to cover the entire map extents.

This is my map configuration but enabling/disabling coordinates display does not change behavior

This is the template node to make the bbox on change of boundary.
[{"id":"9b2015b6.65a058","type":"worldmap in","z":"e02f29e1.67d3d8","name":"worldmap boundary","path":"/worldmap","events":"bounds","x":110,"y":180,"wires":[["7c761ea0.1480d","9470a517.f4e368","aa3569bc.33e3a8"]]},{"id":"aa3569bc.33e3a8","type":"trigger","z":"e02f29e1.67d3d8","op1":"","op2":"","op1type":"nul","op2type":"pay","duration":"250","extend":true,"units":"ms","reset":"","bytopic":"all","name":"","x":420,"y":180,"wires":[["3a7daa20.4a5456"]]},{"id":"3a7daa20.4a5456","type":"change","z":"e02f29e1.67d3d8","name":"set center","rules":[{"t":"set","p":"payload.center","pt":"msg","to":"{}","tot":"json"},{"t":"set","p":"payload.center.lat","pt":"msg","to":"$average([payload.north, payload.south])\t","tot":"jsonata"},{"t":"set","p":"payload.center.lon","pt":"msg","to":"$average([payload.east, payload.west])\t","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":580,"y":180,"wires":[["495f29b2.e5e508","9ed54ec.ce141b","c28055e3.2c3cf8"]]},{"id":"c28055e3.2c3cf8","type":"template","z":"e02f29e1.67d3d8","name":"","field":"payload","fieldType":"msg","format":"handlebars","syntax":"mustache","template":"{\n  \"name\": \"bounds\", \n  \"area\": [\n            [{{payload.south}}, {{payload.west}}], \n            [{{payload.north}}, {{payload.west}}], \n            [{{payload.north}}, {{payload.east}}],\n            [{{payload.south}}, {{payload.east}}],\n            [{{payload.south}}, {{payload.west}}]\n    ]}","output":"json","x":1060,"y":400,"wires":[["c5157a30.bbb588","4c9dc44a.908fdc"]]},{"id":"4c9dc44a.908fdc","type":"ui_worldmap","z":"e02f29e1.67d3d8","group":"b216f4f.7d69c08","order":1,"width":"20","height":"10","name":"","lat":"38.2","lon":"-97.2","zoom":"4.5","layer":"","cluster":"","maxage":"","usermenu":"hide","layers":"show","panit":"false","panlock":"false","zoomlock":"false","hiderightclick":"true","coords":"none","showgrid":"false","allowFileDrop":"false","path":"/worldmap","overlist":"","maplist":"OSMG,OSMC,EsriC,EsriS,EsriT,EsriDG","mapname":"","mapurl":"","mapopt":"","mapwms":false,"x":1680,"y":200,"wires":[]},{"id":"b216f4f.7d69c08","type":"ui_group","z":"","name":"World Map","tab":"a4e26d94.4446","order":1,"disp":true,"width":"20","collapse":false},{"id":"a4e26d94.4446","type":"ui_tab","z":"","name":"World Map","icon":"dashboard","order":6,"disabled":false,"hidden":false}]

The bounds event is reported after a moveend or zoomend event within leaflet. The co-ordinates are those given by map.getBounds()... so not sure why they would be wrong - but likewise not sure if it's worldmap or the underlying leaflet.

not sure if it's worldmap or the underlying leaflet.

I added this leaflet example to this same node implementation and it reports the south/west corner correctly.  In this example the click event is registered to send a message with the click coordinates and the bbox.
[{"id":"5c525d5a.2d40a4","type":"ui_template","z":"89b966af.00ed98","group":"63fc21fa.6e84e","name":"Leaflet","order":1,"width":"20","height":"10","format":"<link rel=\"stylesheet\"<EMAIL_ADDRESS>integrity=\"sha512-hoalWLoI8r4UszCkZ5kL8vayOGVae1oxXe/2A4AO6J9+580uKHDO3JdHb7NzwwzK5xr/Fs0W40kiNHxM9vyTtQ==\" crossorigin=\"\"/>\n\n\n\n\n

","storeOutMessages":true,"fwdInMessages":true,"resendOnRefresh":false,"templateScope":"local","x":90,"y":140,"wires":[["9bc1fa57.e63918","1f38776f.36a619","3626ac11.e223e4"]]},{"id":"3626ac11.e223e4","type":"debug","z":"89b966af.00ed98","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":790,"y":140,"wires":[]},{"id":"63fc21fa.6e84e","type":"ui_group","z":"","name":"OpenStreetMap Leaflet","tab":"61be5b66.568104","order":2,"disp":true,"width":"20","collapse":false},{"id":"61be5b66.568104","type":"ui_tab","z":"","name":"Map Example","icon":"dashboard","order":7,"disabled":false,"hidden":false}]

If I use your original example it works fine...
[{"id":"c9828117.f463","type":"worldmap","z":"27d4cd61f8c2d5ed","name":"worldmap-/test","lat":"","lon":"","zoom":"","layer":"","cluster":"","maxage":"","usermenu":"show","layers":"show","panit":"false","panlock":"false","zoomlock":"false","hiderightclick":"false","coords":"none","showgrid":"false","allowFileDrop":"false","path":"/worldmap","overlist":"DR,CO,RA,DN,HM","maplist":"OSMG","mapname":"","mapurl":"","mapopt":"","mapwms":false,"x":455,"y":450,"wires":[]},{"id":"73c8a005.6a324","type":"worldmap in","z":"27d4cd61f8c2d5ed","name":"worldmap-/test","path":"/worldmap","events":"bounds","x":235,"y":510,"wires":[["d8b66827.f4d188","61b068dd229b63ee"]]},{"id":"8a82b6f9.b0c6c8","type":"inject","z":"27d4cd61f8c2d5ed","name":"add point to layer","repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"{\"lat\":38.1,\"lon\":-77.1,\"name\":\"myname\",\"layer\":\"mylayer\"}","payloadType":"json","x":255,"y":430,"wires":[["c9828117.f463"]]},{"id":"d8b66827.f4d188","type":"debug","z":"27d4cd61f8c2d5ed","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":425,"y":510,"wires":[]},{"id":"a7059aab.b14288","type":"inject","z":"27d4cd61f8c2d5ed","name":"clear","repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"{\"command\":{\"clear\":\"mylayer\"}}","payloadType":"json","x":225,"y":470,"wires":[["c9828117.f463"]]},{"id":"61b068dd229b63ee","type":"function","z":"27d4cd61f8c2d5ed","name":"function 2","func":"//{ \"action\": \"bounds\", \"south\": 50.68427770577119, \"west\": -2.4678039550781254, \"north\": 51.41291212935532, \"east\": -0.29113769531250006, \"zoom\": 10 }\nvar p = msg.payload;\n\nmsg.payload = { \"name\": \"zone1\", \"area\": [[p.south,p.west], [p.north,p.east]] }\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":390,"y":585,"wires":[["a6c23236311ec26b"]]},{"id":"a6c23236311ec26b","type":"delay","z":"27d4cd61f8c2d5ed","name":"","pauseType":"delay","timeout":"5","timeoutUnits":"seconds","rate":"1","nbRateUnits":"1","rateUnits":"second","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":false,"allowrate":false,"outputs":1,"x":555,"y":585,"wires":[["c9828117.f463"]]}]

Fixed in v2.30.3

Testing passed on 2.30.3


add exam type

hi @dileep-gadiraju .....   I have checked navin's changes it is working fine . you can accept above pr .

Done
On Wed, 10 Nov 2021, 6:34 pm apurvabisht97, @.***>
wrote:

hi @dileep-gadiraju https://github.com/dileep-gadiraju ..... I have
checked navin's changes it is working fine . you can accept above pr .
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Sunbird-Saral/Project-Saral/pull/13#issuecomment-965111635,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVL45SHNYGJJF3HD4RQGPMTULJUVVANCNFSM5HXIS6TQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


[Question]: Should there be a Scan Frequency?

Checklist

[X] I've searched for similar issues and couldn't find anything matching
[X] I've included steps to reproduce the behavior

Affected Components

[ ] K8sGPT (CLI)
[X] K8sGPT Operator

K8sGPT Version
v0.3.14
Kubernetes Version
v1.26
Host OS and its Version
No response
Steps to reproduce

Deploy k8s operator using helm
Add K8sGPT CRD with openai backend (for v0.3.14)

After deployment we hit a couple hundred API calls / hour
Expected behaviour
I can see many teams appreciating the constant scan, especially those with monitors in Prom/Grafana; however, this can likely increase costs for some.
Possibly the introduction of a cron like scan frequency to allow the user to choose how frequently they need an AI assisted audit.
Or notes in the docs where the expectation would be for the user to install/uninstall the application when they needed scans.
Actual behaviour
Appears to be constant scanning
Additional Information
Searched around docs, GIT, reddit, YT, and Slack - apologies if this was already discussed somewhere

We could potentially enable users control the intervals between reconciliation loops without touching the k8sgpt deployment.
Another alternative may be checking if we get any new errors from analysers and only then enable the explain in k8sgpt to go and fetch the ai backend response. This approach could be enabled by  bidirectional grpc streams..
Any more ideas @AlexsJones ?

@theblinkingusb what you can do as an alternative is switching off the explain attribute which will prevent making calls to AI backends. Obviously you will not get any possible solutions in your Result Custom Resources

Thanks @arbreezy - I just made that change. This is nice too because it keeps the grafana dashboards populated for forensics (vs doing the helm uninstall/reinstall as I was before). Perhaps I can throw a simple patch script on a cron every week or two.
I'll close this out for now!

@theblinkingusb no worries.
We can expose to the user (helm chart's values.yaml -- overriding  a value) the interval time between reconciliation loops of the operator. It's a rather small change to make but I am not sure how much it would make sense, eager to get your thoughts :)


upgrade(installer): Forward tags to binary

What does this PR do?
Forward config host tags from installer daemon to installer binary
Motivation
Describe how to test/QA your changes
Tested manually on a VM, tags are indeed used in the CDN
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Don't comment them out

I figured out how <os/feature_private.h> was, and those dyld magic values.
https://github.com/Torrekie/apple_internal_sdk
I started working on this while compiling latest objc4 for porting it to older iOS. Commenting out featureflag and OS detection codes was really a bad idea since it ACTUALLY affecting how libobjc works. The reason I am doing this is, I can't find any useful information except bunch copies of articles telling me to comment these undefined values out, no, don't do that.
These undefined values and undeclared functions can be easily figured out by simple searching or reversing. For that non-open feature_private.h, I have done that here.
And for those dyld version check constants, they should originally be in <mach-o/dyld_priv.h> but stripped out by Apple. They are simple structs containing two uint32_t values referring to platforms and versions.
typedef uint32_t dyld_platform_t;

typedef struct {
    dyld_platform_t platform;
    uint32_t        version;
} dyld_build_version_t;

These are actual values of those dyld_fall_20*_os_versions stuff
// Sat Mar 26 18:48:53 CST 2022
// reversed from /usr/lib/libobjc.A.dylib and /usr/lib/system/libcommonCrypto.dylib
// Also tested
#define dyld_fall_2017_os_versions		(dyld_build_version_t) { 0xFFFFFFFF, 0x07E10901 }
#define dyld_fall_2018_os_versions		(dyld_build_version_t) { 0xFFFFFFFF, 0x07E20901 }
#define dyld_fall_2019_os_versions		(dyld_build_version_t) { 0xFFFFFFFF, 0x07E30901 }
#define dyld_fall_2020_os_versions		(dyld_build_version_t) { 0xFFFFFFFF, 0x07E40901 }
#define dyld_fall_2021_os_versions		(dyld_build_version_t) { 0xFFFFFFFF, 0x07E50901 }

#define dyld_platform_version_macOS_10_11       (dyld_build_version_t) { PLATFORM_MACOS, 0x000A0B00 }
#define dyld_platform_version_macOS_10_12       (dyld_build_version_t) { PLATFORM_MACOS, 0x000A0C00 }
#define dyld_platform_version_macOS_10_13	(dyld_build_version_t) { PLATFORM_MACOS, 0x000A0D00 }
#define dyld_platform_version_macOS_10_14	(dyld_build_version_t) { PLATFORM_MACOS, 0x000A0E00 }
#define dyld_platform_version_macOS_10_15	(dyld_build_version_t) { PLATFORM_MACOS, 0x000A0F00 }
#define dyld_platform_version_macOS_10_16	(dyld_build_version_t) { PLATFORM_MACOS, 0x000A1000 }
#define dyld_platform_version_macOS_12_00	(dyld_build_version_t) { PLATFORM_MACOS, 0x000C0000 }

#define dyld_platform_version_tvOS_10_0         (dyld_build_version_t) { PLATFORM_TVOS, 0x000A0000 }
#define dyld_platform_version_tvOS_11_0         (dyld_build_version_t) { PLATFORM_TVOS, 0x000B0000 }
#define dyld_platform_version_tvOS_12_0		(dyld_build_version_t) { PLATFORM_TVOS, 0x000C0000 }
#define dyld_platform_version_tvOS_13_0		(dyld_build_version_t) { PLATFORM_TVOS, 0x000D0000 }
#define dyld_platform_version_tvOS_14_0		(dyld_build_version_t) { PLATFORM_TVOS, 0x000E0000 }
#define dyld_platform_version_tvOS_15_0		(dyld_build_version_t) { PLATFORM_TVOS, 0x000F0000 }

#define dyld_platform_version_iOS_10_0          (dyld_build_version_t) { PLATFORM_IOS, 0x000A0000 }
#define dyld_platform_version_iOS_11_0          (dyld_build_version_t) { PLATFORM_IOS, 0x000B0000 }
#define dyld_platform_version_iOS_12_0		(dyld_build_version_t) { PLATFORM_IOS, 0x000C0000 }
#define dyld_platform_version_iOS_13_0		(dyld_build_version_t) { PLATFORM_IOS, 0x000D0000 }
#define dyld_platform_version_iOS_14_0		(dyld_build_version_t) { PLATFORM_IOS, 0x000E0000 }
#define dyld_platform_version_iOS_15_0		(dyld_build_version_t) { PLATFORM_IOS, 0x000F0000 }

#define dyld_platform_version_watchOS_3_0       (dyld_build_version_t) { PLATFORM_WATCHOS, 0x00030000 }
#define dyld_platform_version_watchOS_4_0       (dyld_build_version_t) { PLATFORM_WATCHOS, 0x00040000 }
#define dyld_platform_version_watchOS_5_0	(dyld_build_version_t) { PLATFORM_WATCHOS, 0x00050000 }
#define dyld_platform_version_watchOS_6_0	(dyld_build_version_t) { PLATFORM_WATCHOS, 0x00060000 }
#define dyld_platform_version_watchOS_7_0	(dyld_build_version_t) { PLATFORM_WATCHOS, 0x00070000 }
#define dyld_platform_version_watchOS_8_0	(dyld_build_version_t) { PLATFORM_WATCHOS, 0x00080000 }

#define dyld_platform_version_bridgeOS_2_0      (dyld_build_version_t) { PLATFORM_BRIDGEOS, 0x00020000 }
#define dyld_platform_version_bridgeOS_3_0      (dyld_build_version_t) { PLATFORM_BRIDGEOS, 0x00030000 }
#define dyld_platform_version_bridgeOS_4_0      (dyld_build_version_t) { PLATFORM_BRIDGEOS, 0x00040000 }
#define dyld_platform_version_bridgeOS_5_0      (dyld_build_version_t) { PLATFORM_BRIDGEOS, 0x00050000 }
#define dyld_platform_version_bridgeOS_6_0      (dyld_build_version_t) { PLATFORM_BRIDGEOS, 0x00060000 }

Using that CrashReporterClient.h stub which appears in older Libc was not quite a good idea, since linking libCrashReporterClient would insert a load command section to Mach-O files (that also indicates libCrashReporterClient was a static library)

Section
  sectname __crash_info
   segname __DATA
      addr 0x00000001d97f8ad8
      size 0x0000000000000040
    offset 246296
     align 2^3 (8)
    reloff 0
    nreloc 0
     flags 0x00000000
 reserved1 0
 reserved2 0

We can find CrashReporterClient implementation under WTF/wtf/spi/cocoa/CrashReporterClientSPI.h and WTF/wtf/cocoa/CrashReporter.cpp, these codes also appears in many other Apple OSSes.
Now we have <CrashReporterClient.h> and libCrashReporterClient.a
For those Cambria APIs, we can see objc-cache.mm was calling two of them
#if TARGET_OS_OSX
        if (oah_is_current_process_translated()) {
            kern_return_t ret = objc_thread_get_rip(threads[count], (uint64_t*)&pc);
            if (ret != KERN_SUCCESS) {
                pc = PC_SENTINEL;
            }
        } else {
            pc = _get_pc_for_thread (threads[count]);
        }
#else
        pc = _get_pc_for_thread (threads[count]);
#endif

It was really easy to figure out that oah_is_current_process_translated() was returning bool, with no arguments, then we have its prototype
bool oah_is_current_process_translated(void);

objc_thread_get_rip() was kinda tricky but still easy to find out how to correctly call it, the definition of thread was
thread_act_port_array_t threads;, and the actual type of thread_act_port_array_t was
// <arm/_types.h> or <i386/_types.h>
typedef unsigned int            __darwin_natural_t;
// <sys/_types.h>
typedef __darwin_natural_t __darwin_mach_port_name_t; /* Used by mach */
typedef __darwin_mach_port_name_t __darwin_mach_port_t; /* Used by mach */
// <sys/_types/_mach_port_t.h>
typedef __darwin_mach_port_t mach_port_t;
// <mach/mach-types.h>
typedef mach_port_t             thread_act_t;
typedef thread_act_t            *thread_act_array_t;
typedef thread_act_array_t      thread_act_port_array_t;

We can see the 1st arg of objc_thread_get_rip() was a member of thread_act_port_array_t, then the type is thread_act_t but not thread_act_port_array_t, then we get prototype
kern_return_t objc_thread_get_rip(thread_act_t thread, uint64_t** buf);

These codes cannot successfully compile without linking liboah, which was not presenting in MacOSX.sdk, we can extract dyld shared cache, get /usr/lib/liboah.dylib, generate liboah.tbd from it. I have done Cambria headers also

WOHO!


[Request for help] Pods can't reach hosts outside cluster

Is this a request for help?:
Request for help
Is this an ISSUE or FEATURE REQUEST? (choose one):

What version of acs-engine?:

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.10.3
What happened:
I am trying to replicate the environment built via acs-engine using  ansible. I use CoreOS as a host OS with updated containerd (1.1), the latest version of the azure-cni plugin and conntrack. Kubernetes cluster works fine, pods get the correct ips from azure-vnet range and are able to communicate within cluster. But when I try to connect to resources outside of the cluster, the pod can't get a response. I've duplicated the kubernetes and azure-cni configuration using acs-engine cluster as an example. Iptables look the same. Can anybody help?
What you expected to happen:
Pods can connect to the world-wide
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

@ivanovoleg Can you please check if you have the masquerade rule to snat traffic that is destined for outside Vnet?

@sharmasushant
Here is the iptables and routes configuration:

ACS cluster (Ubuntu)
1.1 . ACS cluster (master):

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0d:3a:2c:7f:69 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/12 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20d:3aff:fe2c:7f69/64 scope link
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:89:42:c1:38 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:89ff:fe42:c138/64 scope link
       valid_lft forever preferred_lft forever

default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/12 dev eth0  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS> via <IP_ADDRESS> dev eth0
<IP_ADDRESS> via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/16 dev docker0  proto kernel  scope link  src <IP_ADDRESS> linkdown

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-EXTERNAL-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes externally-visible service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
KUBE-FORWARD  all  --  anywhere             anywhere             /* kubernetes forwarding rules */
DOCKER-ISOLATION  all  --  anywhere             anywhere
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain DOCKER (1 references)
target     prot opt source               destination

Chain DOCKER-ISOLATION (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Chain KUBE-EXTERNAL-SERVICES (1 references)
target     prot opt source               destination

Chain KUBE-FIREWALL (2 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere             /* kubernetes firewall for dropping marked packets */ mark match 0x8000/0x8000

Chain KUBE-FORWARD (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* kubernetes forwarding rules */ mark match 0x4000/0x4000
ACCEPT     all  --  <IP_ADDRESS>/12        anywhere             /* kubernetes forwarding conntrack pod source rule */ ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             <IP_ADDRESS>/12        /* kubernetes forwarding conntrack pod destination rule */ ctstate RELATED,ESTABLISHED

Chain KUBE-SERVICES (1 references)
target     prot opt source               destination

1.2 ACS cluster (agent)
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc mq master azure0 state UP group default qlen 1000
    link/ether 00:0d:3a:2c:7b:f1 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::20d:3aff:fe2c:7bf1/64 scope link
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:1e:7d:ac:c3 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:1eff:fe7d:acc3/64 scope link
       valid_lft forever preferred_lft forever
6: azure0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:0d:3a:2c:7b:f1 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/12 scope global azure0
       valid_lft forever preferred_lft forever
    inet6 fe80::20d:3aff:fe2c:7bf1/64 scope link
       valid_lft forever preferred_lft forever
7: azveth78072a3@if8: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether fa:1b:a1:7d:43:07 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::f81b:a1ff:fe7d:4307/64 scope link
       valid_lft forever preferred_lft forever
9: azvethc1b1f0b@if10: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether 22:20:8a:4d:e6:ef brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::2020:8aff:fe4d:e6ef/64 scope link
       valid_lft forever preferred_lft forever
11: azveth446cf7f@if12: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether 56:fb:a1:97:ef:b2 brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet6 fe80::54fb:a1ff:fe97:efb2/64 scope link
       valid_lft forever preferred_lft forever
13: azvethf562385@if14: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether 6e:f1:54:db:3b:ce brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet6 fe80::6cf1:54ff:fedb:3bce/64 scope link
       valid_lft forever preferred_lft forever
15: azveth9e9e1eb@if16: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether fa:2b:d2:75:56:82 brd ff:ff:ff:ff:ff:ff link-netnsid 4
    inet6 fe80::f82b:d2ff:fe75:5682/64 scope link
       valid_lft forever preferred_lft forever
17: azveth0ad1cc1@if18: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether d6:31:a6:ba:16:bd brd ff:ff:ff:ff:ff:ff link-netnsid 5
    inet6 fe80::d431:a6ff:feba:16bd/64 scope link
       valid_lft forever preferred_lft forever

default via <IP_ADDRESS> dev azure0
<IP_ADDRESS>/12 dev azure0  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/16 dev docker0  proto kernel  scope link  src <IP_ADDRESS> linkdown

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-EXTERNAL-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes externally-visible service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
KUBE-FORWARD  all  --  anywhere             anywhere             /* kubernetes forwarding rules */
DOCKER-ISOLATION  all  --  anywhere             anywhere
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain DOCKER (1 references)
target     prot opt source               destination

Chain DOCKER-ISOLATION (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Chain KUBE-EXTERNAL-SERVICES (1 references)
target     prot opt source               destination

Chain KUBE-FIREWALL (2 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere             /* kubernetes firewall for dropping marked packets */ mark match 0x8000/0x8000

Chain KUBE-FORWARD (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* kubernetes forwarding rules */ mark match 0x4000/0x4000
ACCEPT     all  --  <IP_ADDRESS>/12        anywhere             /* kubernetes forwarding conntrack pod source rule */ ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             <IP_ADDRESS>/12        /* kubernetes forwarding conntrack pod destination rule */ ctstate RELATED,ESTABLISHED

Chain KUBE-SERVICES (1 references)
target     prot opt source               destination

1.3. ACS cluster (DNS pod)
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
12: eth0@if11: <BROADCAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 86:cf:1c:e0:df:54 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/12 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::84cf:1cff:fee0:df54/64 scope link
       valid_lft forever preferred_lft forever

default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/12 dev eth0 scope link  src <IP_ADDRESS>

Kubernetes cluster (CoreOS)
2.1 Kubernetes cluster (master)

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0d:3a:39:5a:11 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/12 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::20d:3aff:fe39:5a11/64 scope link
       valid_lft forever preferred_lft forever
3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:e4:cf:0e:82 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:e4ff:fecf:e82/64 scope link
       valid_lft forever preferred_lft forever
5: veth47697d9@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether 3e:9b:4c:87:cf:8b brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::3c9b:4cff:fe87:cf8b/64 scope link
       valid_lft forever preferred_lft forever

default via <IP_ADDRESS> dev eth0 proto dhcp metric 1024
<IP_ADDRESS>/12 dev eth0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS> via <IP_ADDRESS> dev eth0 proto dhcp metric 1024
<IP_ADDRESS> via <IP_ADDRESS> dev eth0 proto dhcp metric 1024
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS>

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-EXTERNAL-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes externally-visible service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
KUBE-FORWARD  all  --  anywhere             anywhere             /* kubernetes forwarding rules */
DOCKER-USER  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain DOCKER (1 references)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             <IP_ADDRESS>           tcp dpt:http

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-USER (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Chain KUBE-EXTERNAL-SERVICES (1 references)
target     prot opt source               destination

Chain KUBE-FIREWALL (2 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere             /* kubernetes firewall for dropping marked packets */ mark match 0x8000/0x8000

Chain KUBE-FORWARD (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* kubernetes forwarding rules */ mark match 0x4000/0x4000
ACCEPT     all  --  <IP_ADDRESS>/12        anywhere             /* kubernetes forwarding conntrack pod source rule */ ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             <IP_ADDRESS>/12        /* kubernetes forwarding conntrack pod destination rule */ ctstate RELATED,ESTABLISHED

Chain KUBE-SERVICES (1 references)
target     prot opt source               destination

2.2 Kubenetes cluster (agent)
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc mq master azure0 state UP group default qlen 1000
    link/ether 00:0d:3a:39:54:78 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::20d:3aff:fe39:5478/64 scope link
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:57:09:ca:aa brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global docker0
       valid_lft forever preferred_lft forever
4: azure0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:0d:3a:39:54:78 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/12 scope global azure0
       valid_lft forever preferred_lft forever
    inet6 fe80::d006:1dff:fe80:9920/64 scope link
       valid_lft forever preferred_lft forever
5: azv2010ddf0ba5@if6: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether 4e:e4:3b:81:bf:0c brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::4ce4:3bff:fe81:bf0c/64 scope link
       valid_lft forever preferred_lft forever
7: azvb693453cda4@if8: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether da:73:f6:24:e2:5b brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::d873:f6ff:fe24:e25b/64 scope link
       valid_lft forever preferred_lft forever
9: azve6844c3d520@if10: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether 76:bb:dc:75:55:c7 brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet6 fe80::74bb:dcff:fe75:55c7/64 scope link
       valid_lft forever preferred_lft forever
11: azvfee51350d48@if12: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether 5e:45:a9:2e:1e:25 brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet6 fe80::5c45:a9ff:fe2e:1e25/64 scope link
       valid_lft forever preferred_lft forever
13: azv561f374d784@if14: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether aa:e6:cb:78:c9:e5 brd ff:ff:ff:ff:ff:ff link-netnsid 4
    inet6 fe80::a8e6:cbff:fe78:c9e5/64 scope link
       valid_lft forever preferred_lft forever
17: azva09e9d53bff@if18: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether 1a:bc:00:38:25:42 brd ff:ff:ff:ff:ff:ff link-netnsid 6
    inet6 fe80::18bc:ff:fe38:2542/64 scope link
       valid_lft forever preferred_lft forever
19: azv77902ee09aa@if20: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master azure0 state UP group default qlen 1000
    link/ether 36:40:4a:e9:74:21 brd ff:ff:ff:ff:ff:ff link-netnsid 5
    inet6 fe80::3440:4aff:fee9:7421/64 scope link
       valid_lft forever preferred_lft forever

default via <IP_ADDRESS> dev azure0 proto dhcp metric 1024
<IP_ADDRESS>/12 dev azure0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS> via <IP_ADDRESS> dev azure0 proto dhcp metric 1024
<IP_ADDRESS> via <IP_ADDRESS> dev azure0 proto dhcp metric 1024
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS> linkdown

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-EXTERNAL-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes externally-visible service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
KUBE-FORWARD  all  --  anywhere             anywhere             /* kubernetes forwarding rules */
DOCKER-USER  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain DOCKER (1 references)
target     prot opt source               destination

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-USER (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Chain KUBE-EXTERNAL-SERVICES (1 references)
target     prot opt source               destination

Chain KUBE-FIREWALL (2 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere             /* kubernetes firewall for dropping marked packets */ mark match 0x8000/0x8000

Chain KUBE-FORWARD (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             /* kubernetes forwarding rules */ mark match 0x4000/0x4000
ACCEPT     all  --  <IP_ADDRESS>/12        anywhere             /* kubernetes forwarding conntrack pod source rule */ ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             <IP_ADDRESS>/12        /* kubernetes forwarding conntrack pod destination rule */ ctstate RELATED,ESTABLISHED

Chain KUBE-SERVICES (1 references)
target     prot opt source               destination

2.3 Kubernetes cluster (DNS pod)
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
6: eth0@if5: <BROADCAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether 6a:b0:ea:c1:fc:e8 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/12 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::68b0:eaff:fec1:fce8/64 scope link
       valid_lft forever preferred_lft forever

default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/12 dev eth0 scope link  src <IP_ADDRESS>

@IvanovOleg This is because not every ip-address in the Vnet get a default snat IP for internet bound traffic. Only the primary ip of the VM interface gets it.

@sharmasushant I don't see this kind of rule in the acs-engine cluster I use as an example. Or maybe I look in the wrong place...

@IvanovOleg I am not sure why your cluster does not have the rule. Are you using Azure CNI when you deployed via acs-engine?
The rule appears in the POSTROUTING chain of nat table on the cluster that I created
MASQUERADE  all  --  anywhere            !<IP_ADDRESS>/8           destination IP range ! <IP_ADDRESS>-<IP_ADDRESS> ADDRTYPE match dst-type !LOCAL
<IP_ADDRESS>/8 is my Vnet address space
Here is the command to add the rule
iptables -t nat -A POSTROUTING -m iprange ! --dst-range <IP_ADDRESS> -m addrtype ! --dst-type local ! -d '<vnet-address-space>' -j MASQUERADE

@sharmasushant Yes, I've deployed that cluster using acs-engine 0.17.1 with the next config:
{
  "apiVersion": "vlabs",
  "properties": {
    "orchestratorProfile": {
      "orchestratorType": "Kubernetes",
      "orchestratorVersion": "1.10.3",
      "kubernetesConfig": {
        "networkPolicy": "azure",
        "enableRbac": true,
        "apiServerConfig": {
          "--admission-control": "NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,ResourceQuota,DenyEscalatingExec,AlwaysPullImages"
        }
      }
    },
    "masterProfile": {
      "count": 1,
      "dnsPrefix": "xxxxxxx",
      "vmSize": "Standard_D2_v2",
      "storageProfile" : "ManagedDisks"
    },
    "agentPoolProfiles": [
      {
        "name": "agentpool1",
        "count": 1,
        "vmSize": "Standard_DS2_v2",
        "availabilityProfile": "AvailabilitySet",
        "storageProfile" : "ManagedDisks"
      }
    ],
    "linuxProfile": {
      "adminUsername": "xxxxx",
      "ssh": {
        "publicKeys": [
          {
            "keyData": ""
          }
        ]
      }
    },
    "servicePrincipalProfile": {
      "clientId": "",
      "secret": ""
    }
  }
}

@sharmasushant Yes, this rule helps. Thanks!


Port 5633 Datadog Ocean integration

Description
Add Datadog to Ocean

Type of change

[x] New feature (non-breaking change which adds functionality)

@Tankilevitch, I have removed the contacts property after reviewing the datadog  service schema and API docs to see that there are 3 possible contact types: email, slack and microsoft-teams. I now have them as properties on the service blueprint.


Cors auto generated when no are an action route with options

The Cors annotation need send options request with the http verb allowed to the route when the option  path is not defined
I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[X] feature request

featured ready. The next pull request include this.


Explore Mosh as the transport

From personal experience, mosh is the best feature that happens for me in years since i use terminals on mobile devices (blink app is the best example)


Setting up eslint and linting the code

I want to make the code prettier by setting up eslint in the project and linting the code

@ravikr126 please assign this issue to me

Go ahead @subhangi2731

@harikesh409 thanku can u please provide the gssoc and level tags

Reopening as it is not resolved.

Moved to #518


Automatic iteration through all entities

Explanation
Iterate through all entities on each frame and call a specific function, if available

Iteration through entities was added in 0.0.1-dev


Integration of Foreman and the inclusion of a Procfile for dev. environments

Currently, the Vite asset pipeline does not support the Hot Module Replacement when only rails server is invoked within the local development environment. In order to ensure that HMR is enabled and that modifications made to the SCSS files are dynamically updated in one's web browser, one must open a separate, new terminal and invoke bundle exec ./bin/vite dev. One alternative to this might be to please include https://github.com/ddollar/foreman as a dependency. Using a Procfile structured as the following:
vite: bin/vite dev
web: bin/rails s

...one can then simply invoke bundle exec foreman start.
Please see https://github.com/pulibrary/orcid_princeton/issues/199 for reference

Let's discuss this as a team before scheduling into a sprint.

Following the discussion during the check-in meeting for this morning, it was determined that the preferred approach for this is to please invoke rake assets:clobber should issues arise with SCSS or JavaScript assets not being updated within the development environment


Background "OpenStreetMap (Standard)" should fetch fresh tiles after each save

Seems to make sense that background "OpenStreetMap (Standard)" should fetch fresh tiles (if "possible").
I mean we are tying to build upon our edits in an area... so maybe get fresh tiles exactly once after each save... not too wasteful indeed, just the tiles for the area we are looking at when we made the save.

OK, I see it currently gets the tiles the same way as when not editing OSM.ORG. So the user will probably see a mix of old and new tiles as he zooms in and out. Hmm, well maybe make sure they all get refreshed...

The tiles are rendered and cached on external servers. iD has no control over when any of the tiles are refreshed.


Settings Refresh

Why?
In the future we may need more categories (for example Tweet Card Customisation) and currently the UI doesn't allow that to happen. Please let me know of any changes you would make to it as this is a major change.
Settings UI

BottomNavigationBar -> Categories List
Future Proof

General Settings

Sub-category: Media
Sub-category: Feed

Theme Settings

Moved: Font Size

Thank you for this PR.
I agree with the general idea of restructuring the settings to allow extending it.
I don't agree with the simplified list of color selection. or instance I'm using right now a color that is not even in the list.
I will accept this PR if you roll back the color list selection.

Thank you for the feedback, I'll revert the colour options as soon as I'm
able to.
On Tue, 12 Dec 2023, 20:17 Jean-Francois Briere, @.***>
wrote:

Thank you for this PR.
I agree with the general idea of restructuring the settings to allow
extending it.
I don't agree with the simplified list of color selection. or instance I'm
using right now a color that is not even in the list.
I will accept this PR if you roll back the color list selection.
—
Reply to this email directly, view it on GitHub
https://github.com/j-fbriere/squawker/pull/130#issuecomment-1852740624,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BD45TZ7UD7IP4QMUM5A24QTYJC3WZAVCNFSM6AAAAABAOXQ4IOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSG42DANRSGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

@j-fbriere I have reverted the colour selection, any more feedback before you merge?

You removed Experiments?

Yes, it is intentional as I feel there is no need for it

Thank you, for the quick response. I hope to be working more on Squawker in
the future 😃
On Tue, 12 Dec 2023, 23:09 Jean-Francois Briere, @.***>
wrote:

Merged #130 https://github.com/j-fbriere/squawker/pull/130 into master.
—
Reply to this email directly, view it on GitHub
https://github.com/j-fbriere/squawker/pull/130#event-11229500384, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BD45TZ6KP57YIFZWR2BVOGLYJDPZRAVCNFSM6AAAAABAOXQ4IOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGIZDSNJQGAZTQNA
.
You are receiving this because you were mentioned.Message ID:
@.***>


User suggestion to improve transaction docs

https://github.com/prisma/prisma/discussions/21550#discussioncomment-7332212

👋 Hi there,
We're reviewing and tidying up our backlog to focus on the most relevant and impactful issues. After careful consideration, we're closing issues that haven't had any recent activity or align with our current priorities.
If you believe this issue is still important or unresolved, you're welcome to reopen it or create a new one with updated details. Your feedback is always valued and we're here to help ensure our docs continue to improve.
Thank you for your understand and contributions!


Error connecting to CertStream: SSLV3_ALERT_HANDSHAKE_FAILURE

I have the following error:
[ERROR:root] 2018-07-19 18:56:49,459 - Error connecting to CertStream - [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:579) - Sleeping for a few seconds and trying again...
Any ideas?

Looks to be an issue with my OpenSSL implementation - Works fine on Windows / PyCharm. Will check further....

Hey there,
Let me know if there's anything actionable here and I'm happy to take a look!
Thanks,
Ryan


Add German Bible translation

Hello everyone, first of all thanks for the plugin @tim-hub, its really helpfull. It would be even nicer if we could add a german bible translation. Is this possible?

Hi @daribock
Thanks for the feedback the only issue is I don't know whether there is a free online German bible API

Hi @daribock
Thanks for the feedback the only issue is I don't know whether there is a free online German bible API

I think I found one but you need to register for this API. https://scripture.api.bible/
I am not that experienced with API's thats why I why I can't tell you if we could easily implement the API in the obsidian plugin. 🤔

Also one other question @tim-hub. How did you build you portfolio page? (https://techtim42.com/) I think it looks really nice and I would love to know how you build it. 🤓

Also one other question @tim-hub. How did you build you portfolio page? (https://techtim42.com/) I think it looks really nice and I would love to know how you build it. 🤓

Thanks, Glad to hear you like it.
It is a very simple Nextjs project.
I haven't make the source code public yet, but if you are familiar with React/Nextjs, I don't mind sharing you with the access to the private repo, so you can have a look and build your own :)
Just let me know

I am familiar with React and Nextjs is on my todo list.
So yeah I would love to have a sneak peak in your portfolio repo. :D

I am familiar with React and Nextjs is on my todo list. So yeah I would love to have a sneak peak in your portfolio repo. :D

I just added you.
https://github.com/tim-hub/techtim42


[DOCUMENTATION] v3 getProps and shouldGetProps removed from the pages

Summary
I see that these events are removed from the pages (product-detail and page-not-found). These are not mentioned in the v3 migration guide, maybe we can add a mention about this?

@alimonculOSF thanks for pointing this out, we'll update the docs


NPM fails to start : s6-rc fatal error

Hi there, since the first timeI installed NPM it never started well. After a reboot of my server the container does start but there’s still this weird error :
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service prepare: starting s6-rc: fatal: timed out s6-sudoc: fatal: unable to get exit status from server: Operation timed out /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
I have to go to portainer and recreate the container at each of my server reboot so it starts well.
Here’s the steps to reproduce :
use this docker compose and just reboot your device where NPM is installed.
version: '3.8'services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
volumes:
- /home/louise/docker/NGINX/data:/data
-  /home/louise/docker/NGINX/letsencrypt:/etc/letsencrypt
If anyone has any idea about how to fix s6-rc not working (I don’t even know what it is tbh), I take !

I have same issue
❯ Configuring npmuser ...
id: 'npmuser': no such user
s6-rc: fatal: timed out
s6-sudoc: fatal: unable to get exit status from server: Operation timed out
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

I have this instance running for many years, after rebooting the host. The host started.
Note: using this tag fixed the issue for me for now # 2.9.22

Since NPM works well when it's first created but not after a reboot I created a script that recreates the container at every startup. Here's the script if anyone's interested (it could definitely need improvements but it works).
NPM.txt

I also have this problem, docker deployment, please let me know if it is solved
❯ Setting ownership ...
s6-rc: fatal: timed out
s6-sudoc: fatal: unable to get exit status from server: Operation timed out
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

same problem here. had to roll back to 2.9.22

I'm not entirely sure, but it may be linked to a problem I'm experiencing on TrueNAS Scale, where NPM works on SSDs based pools, and not on HDDs pools. May be a clue to what the problem is coming from.

This has been an ongoing issue for months, even on 2.9.22 I have to occasionally restart the container manually.
Can we just roll back whatever change caused these constant permissions issues?

I had to pull jc21/nginx-proxy-manager:2.10.3 specifically, latest seemed to still pull 2.10.2 which still had the error reported here

export: fatal: unable to exec /etc/s6/init/init-stage1: No such file or directory

Throwing my name into the hat. I get this after rolling back to 2.9.20. Been running for years, and this just started the other day.
  nginxpm:
    image: jc21/nginx-proxy-manager:2.9.20
    container_name: nginx-proxy-manager
    #security_opt: #an attempt to fix, didn't work.
    #  - seccomp:unconfined
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    ports:
      - 80:80
      - 81:81
      - 443:443
    labels:
      - docker.group=monitor
    volumes:
      - ${LOCALTIME}:${LOCALTIME}:ro
      - ${NGINX_CONF}:/config:rw
      - ${NGINX_CONF}/letsencrypt:/etc/letsencrypt
      - ${NGINX_CONF}/data:/data
      - ${NGINX_CONF}/etc:/etc
    healthcheck:
      test:
        - CMD
        - /bin/check-health
      interval: 10s
      timeout: 3s
    restart: always

New discovery.
s6-rc-compile: fatal: during resolution of bundle top: undefined service name user2

hello.
I faced similar problem when reboot my device and now it works fine after add this environment variable.
S6_CMD_WAIT_FOR_SERVICES_MAXTIME
default value is 5000 (5 seconds). I set it to 60000.

I faced similar problem when reboot my device and now it works fine after add this environment variable.
S6_CMD_WAIT_FOR_SERVICES_MAXTIME
default value is 5000 (5 seconds). I set it to 60000.

        environment:
            - S6_CMD_WAIT_FOR_SERVICES_MAXTIME=60000

That doesnt work for me sadly. Same exact error in logs.

Still a problem.


calculate nearest region distance

iterate all other region blocks
determine which is nearest
calc the distance from origin + size of current region block

https://github.com/cracked-machine/mmdiagram/commit/4127f75327ed172fd5175acacb1376949b53afa7

Needs proper set of unit tests

5d2ee10145341d3404ffbf946acef80143e36ee3


What is the point of this repository?

What the title says, really. This repo doesn't help much with true app-local (portable xcopy-deploy) deployment of the CRT, as this repo contains no actual code, only export forwarders. When I need to do true portable CRT deployment, I copy the applicable DLLs out of the VC\Redist folder in my VS install.
Besides, IIRC the *_app.dll files contain only UWP-compatible APIs. This would make the stubs in this repository and the real implementations being forwarded to incompatible, potentially causing Store submission failure if used. Some clarification on how this code is useful would be appreciated. Thanks!

This component is meant to be used by unpackaged Win32 projects that use components that depend on the CRT. As such this should never be used in a Store package project.

Have a look at this blog post for more details on usage: https://blogs.windows.com/buildingapps/2019/04/30/enhancing-non-packaged-desktop-apps-using-windows-runtime-components/


Make conversion from hex to bin

Signed-off-by: Federico Bruzzone<EMAIL_ADDRESS>

Reference to issue #35

I commented cartridge_header.rs with the binary conversion.
I don't know if it's better to keep it in hex, let me know.

I opened a new PR.
Do you want to keep this open to fix the error? (From 0xAAA to 0xAAAAAAAA)?


feature request: control output format of source location

Currently, in HRF format, the source location is printed as file.ext(lineno):.
For example
./.././detail/test.cpp(764): error in "test_name": check a == b has failed [3 != 6]

It would be good for automated tools to have the alternative to print the source location in format more similar to source locations printed in clang and gcc (also Catch2), i.e. file.ext:lineno.
For example the modified format out would print:
./.././detail/test.cpp:764: error in "test_name": check a == b has failed [3 != 6]

Would it be possible to add this options to the format output?
(I tried editing the strings in /usr/include/boost/test/minimal.hpp and in test/impl/compiler_log_formatter.ipp:print_prefix but that didn't do it.)

I found this in the sources. It seems that the format is controlled by the compiler in the case of Xcode, based on an idea of https://richarddingwall.name/2008/06/01/using-the-boost-unit-test-framework-with-xcode-3
#ifdef __APPLE_CC__
        // Xcode-compatible logging format, idea by Richard Dingwall at
        // <http://richarddingwall.name/2008/06/01/using-the-boost-unit-test-framework-with-xcode-3/>.
        output << file_name << ':' << line_num << ": ";
#else
        output << file_name << '(' << line_num << "): ";
#endif

Very good, with the same criteria the (default) format can be deduced from the compiler used to compile Boost.Test in linux as well (e.g. GCC, clang --same format incidentally--, intel, etc)
That is I propose:
#if defined(__APPLE_CC__) or defined(__GNUC__) or defined(__clang__)
        // Xcode-compatible logging format, idea by Richard Dingwall at
        // <http://richarddingwall.name/2008/06/01/using-the-boost-unit-test-framework-with-xcode-3/>.
       // also for gcc and clang
        output << file_name << ':' << line_num << ": ";
#else
        output << file_name << '(' << line_num << "): ";
#endif

I found a solution using the facilities of Boost.Test, but it is really and overkill just to change this detail (parenthesis for colon).
https://stackoverflow.com/a/64619245/225186


Review Branch Folder restrictions

Assuming I had implemented restrictions such as those described, how can I inspect a repository to review these restrictions?

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

ID: 330532da-d568-b010-a154-62afb1844e4a
Version Independent ID: 4efad37d-4ec2-033e-51b1-b9f588e675c6
Content: Require branches to be created in folders
Content Source: docs/git/how-to/require-branch-folders.md
Service: unspecified
Product: devops
GitHub Login: @steved0x
Microsoft Alias: sdanie

@davidsk You can use the tf git permission command to view the permissions, from that page, here is an example of viewing permissions for a repo. Maybe I should update that topic and include an example of reviewing the permissions once you have set them, would that be helpful?

That would be very helpful, thanks!

Maybe I'm missing something but how can I see the branch folders that I've specified?  I can see that [TeamProject]\Contributors has the CreateBranch permission but not that I've restricted it to features/ and users/.

Please accept our apology for the significant delay in addressing this issue.
It looks like you're working through an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot

@davidsk, @steved0x
Did you ever figure out a way to view what restrictions are set?  All I'm seeing is the generic CreateBranch permission, not actual folder restrictions.

I didn't, no, and I don't have access to the repository that I was working with when I raised the issue.  The docs, however, seem to have been updated - did you try using the tf git permission command


Default to restoring CPU affinity

Otherwise commands spawned by pcm end up being bound to one thread.
Tested on FreeBSD and Linux.
Closes #378, #380

thanks a lot!


Memory support (Issue #42)

Addresses #42.

@ddtm Some tests are now failing. Also have you actually tested it?

Coverage decreased (-0.1%) to 94.266% when pulling 9aa6ba6b132f55ca130c7429ce9e098ff03e42ec on ddtm:memory into da978d6de8f0b9c596d2496ccc8239aebc41a4e4 on SMART-Lab:master.

Coverage decreased (-0.08%) to 94.31% when pulling 257e7fe9718760b5b29435822eb43f1e1906a555 on ddtm:memory into da978d6de8f0b9c596d2496ccc8239aebc41a4e4 on SMART-Lab:master.

Coverage increased (+0.1%) to 94.515% when pulling abc79ee1fc5ea6687a21d0af90459bd95fc83418 on ddtm:memory into da978d6de8f0b9c596d2496ccc8239aebc41a4e4 on SMART-Lab:master.

Coverage increased (+0.1%) to 94.648% when pulling 110beed20fb931d9f955e0cd260bf0562bdc1d3e on ddtm:memory into c94f08e828d6deec453c054fd340e694ec0e0b9a on SMART-Lab:master.


Visual Studio Image Not Showing

🐞 Problem

The Visual Studio image is not showing in Chrome.

@SeanBarber, this works for me. Could you please check again and give more details?

@Roshanjossey I just updated my post with the picture of Chrome

@SeanBarber, still loading for me

Could you check network tab in dev tools to find why it's not loading?

I found the link it is supposed to load and it says it is not found on my Chrome

Cleared my cache and it loaded properly. Interesting.

@SeanBarber, This is the image we're using there https://www.microsoft.com/net/images/vslogo.png
It gives me a 404. Still, the image is loaded from
https://camo.githubusercontent.com/3860efdf8f5c7f13181764ff963ef6cad2a28ac9/68747470733a2f2f7777772e6d6963726f736f66742e636f6d2f6e65742f696d616765732f76736c6f676f2e706e67
We might have to look in to this problem in the future


Jedis cluster

@bstout @pixelthekid Requesting this PR in order to resolve https://cccnext.jira.com/browse/CONDUCTOR-330
This code is in PR to netflix dev currently, but we'd like it sooner.
Original Issue: https://github.com/Netflix/conductor/issues/1431
PR to Netflix Dev: https://github.com/Netflix/conductor/pull/1422/files
Is there a version bump we need to make here in order to distinguish this from current? Or would that be secondary from this PR and done when we release this as new version?

followup in PR: https://github.com/bstout/conductor/pull/18


TypescriptBug. IParticlesParams Type has an error.

mode: ['grab', 'repulse'], can be an array not only a single string
sample:
import Particles, { IParticlesParams } from 'react-particles-js'

const ParticleSett = {
...
interactivity: {
		detect_on: 'canvas',
		events: {
			onhover: {
				enable: true,
				mode: ['grab', 'repulse']
			},
...
}

<Background params={ParticleSett} />

Thanks for the feedback. v2.7.1 should fix the issue


python312Packages.import-expression: 1.1.5 -> 2.0.0; python312Packages.jishaku: 2.5.2 -> 2.5.1-unstable-2024-05-29

Description of changes

python312Packages.import-expression: 1.1.5 -> 2.0.0
python312Packages.jishaku: 2.5.2 -> 2.5.1-unstable-2024-05-29

Alternative to #315235

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

@ofborg build python311Packages.import-expression python311Packages.jishaku

Result of nixpkgs-review run on x86_64-linux 1

8 packages built:

python311Packages.import-expression
python311Packages.import-expression.dist
python311Packages.jishaku
python311Packages.jishaku.dist
python312Packages.import-expression
python312Packages.import-expression.dist
python312Packages.jishaku
python312Packages.jishaku.dist

I don't know if the API is a breaking change and if it's eligible for backport in the first place

Result of nixpkgs-review run on x86_64-linux 1

8 packages built:

python311Packages.import-expression
python311Packages.import-expression.dist
python311Packages.jishaku
python311Packages.jishaku.dist
python312Packages.import-expression
python312Packages.import-expression.dist
python312Packages.jishaku
python312Packages.jishaku.dist

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

8 packages built:

python311Packages.import-expression
python311Packages.import-expression.dist
python311Packages.jishaku
python311Packages.jishaku.dist
python312Packages.import-expression
python312Packages.import-expression.dist
python312Packages.jishaku
python312Packages.jishaku.dist

Why's there hidden whitespace characters at the beginning of the title

Why are we downgrading jishaku here? 2.5.2 is a bugfix release afaik

It's not a downgrade, upstream messed up tags

Tags seem to be fine though?

Okay seems like an intentional backport, but in any case all the commits are present on the main branch, but the 2.5.2 tag itself is not on that branch

Weirdly managed tagging indeed, but 2.5.2 -> 2.5.1-unstable-2024-05-29 sends a wrong message that it is being downgraded. Changing it to 2.5.2-unstable... would be better in my opinion

I disagree :shrug:

If a package is a commit from a repository without a version assigned, then the version attribute should be the latest upstream version preceding that commit

https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#package-naming

The changes and tag is present, it's just not obvious.


Answer for 'Functional Programming: Sort an Array Alphabetically using the sort Method' doesn't work in Chrome

Describe your problem and how to reproduce it:
I was doing the Functional Programming: Sort an Array Alphabetically using the sort Method challenge, in which you're supposed to sort an array of letters alphabetically. So I tried what I thought was the correct answer. It didn't work. I looked at the answer and it was exactly the same but with a longer syntax:
return arr.sort((a,b)=> a>b));

I was very confused, I was so confident about that answer! So I started trying different things in codepen and jsfiddle, but that method wasn't working at all:
// Chrome output
const arr = ["c", "a", "b"];
console.log(arr.sort((a,b)=>a>b)); //["c", "a", "b"]
console.log(arr.sort((a, b) => a.localeCompare(b))); //["a", "b", "c"]
console.log(arr.sort()); //["a", "b", "c"]

Still very confused I opened Firefox and did the same thing. But this time, all methods worked.
// Firefox output
const arr = ["c", "a", "b"];
console.log(arr.sort((a,b)=>a>b)); //["a", "b", "c"]
console.log(arr.sort((a, b) => a.localeCompare(b))); //["a", "b", "c"]
console.log(arr.sort()); //["a", "b", "c"]

It appears that the latest versions of Chrome won't let you sort arrays alphabetically that way anymore. But I don't know what would be the right way to tackle that problem.
Probably a good first step is to add a disclaimer to the solution guide explaining the issue.
What do you guys think?
-- EDIT:
It may be obvious, but I should mention that this is a problem for all the people using later versions of Chrome, because in both the challenge explanation and the solution, the method that is used to sort the array won't work. So even if you copy and paste the solution, the tests will fail.
Add a Link to the page with the problem:
https://learn.freecodecamp.org/javascript-algorithms-and-data-structures/functional-programming/sort-an-array-alphabetically-using-the-sort-method
Tell us about your browser and operating system:

Browser Name: Chrome
Browser Version: 73.0.3683.86 (Official Build) (64-bit)
--
Browser Name: Firefox
Browser Version: 67.0b8 (64-bit)
--
Operating System: macOS Mojave 10.14.3

What's going on here is that Chrome is being strict about the spec while Firefox is more relaxed.  From here:

If comparefn is not undefined, it should be a function that accepts two arguments x and y and returns a negative value if x < y, zero if x = y, or a positive value if x > y.

The instructions are a bit different on rocks, as the misleading example has been replaced with correct code.  Do you think the new instructions do a good enough job conveying how to use sort?

What's going on here is that Chrome is being strict about the spec while Firefox is more relaxed.  From here:

If comparefn is not undefined, it should be a function that accepts two arguments x and y and returns a negative value if x < y, zero if x = y, or a positive value if x > y.

The instructions are a bit different on rocks, as the misleading example has been replaced with correct code.  Do you think the new instructions do a good enough job conveying how to use sort?

Thank you for the explanation! Now I understand what the problem is.
I think that the instructions are very good at explaining how sort() works.
But the problem remains. In chrome, you won't be able to sort alphabetically an array of letters by using arr.sort((a,b)=>a>b)., as the example shows.
Actually, if you copy and paste the second example from the instructions, you will get a different result. I think that would be confusing for people that is using chrome and is just learning js.
Maybe it would be good to have 2 different challenges? One to sort numbers and one alphabetically. And in the one for alphabetical sorting, explain this issue and show another method?

@guayom Ah, my bad, I linked to the wrong page!  I should have pointed you to here.  I've edited my original comment, but I thought I'd best add this so you know what happened.
I think it's okay to keep one challenge, but it might be worth modifying this one a little.  For example, the first line could read something like

The sort method sorts the elements of an array and returns it.  sort can be called with an optional callback function that takes two arguments and returns -1, 0 or 1 if they are in order, equal or out of order.

I think it's best to avoid boolean comparisons entirely.  As you've noticed, they are not reliable!

@guayom Though not reflected in the beta, the challenge was update`d on PR #35756.  Also, on PR #35746, I have corrected the suggested solution and improved the hint example.  I am just waiting for it to get merged.

@ojeytonwilliams @RandellDawson  Oh I see now! That's perfect! Thanks for your help!
With all that said, I'll close the issue since the changes will eventually get merged :)


Add json output to pedump

It would be great if the pedump tool would have a cli flag to dump all of the data as a Json document. This way it would become a safe alternative to the widely used python pefile tool:
https://github.com/erocarrera/pefile

This is interesting and has been on my mind but I couldn't get the code right to my satisfaction.
In the meantime I did work on a JS API (powered by wasm) which begs the question: is it important that this tool is an exe? Could it also work as a library in eg. JS or or python? I ask because I'm much more comfortable making bindings than writing CLI applications...


Canvascast: Filter favorite courses

This allows only the favorite courses to be shown, but still preserves the order from the original /courses endpoint.
Description
Filters courses to only allow favorites. Suggested by @eliotbehr after #209 was merged

Type of change
Adds a feature to improve the user experience of the extension.
In canvas, users can set their favorite courses so that inactive courses are not shown. This change allows the extension to follow those settings.

Bug fix / improvement for my extension

Screencast
No visible change, other than the data shown. See #209 for what the extension does.
Checklist

[ x ] I read the extension guidelines
[ x ] I read the documentation about publishing

Hi @YodaLightsabr 👋
Everything is still working as expected, does it make sense to have it as a preference, so it's still possible to use the old “way” or even make another command?
I'm just curious, and I know nothing about it 😄

I had only ever intended it to show favorite courses, because those are the only ones you can easily access from the Canvas dashboard itself, but I hadn't tested to make sure only favorite courses were displayed. Many instructors forget to close old courses, and the old courses can really add up and prevent you from accessing the important assignments and courses. It would be possible to make it a preference, but I'm not sure that anyone would get much value out of it, as they could just change their favorite courses within Canvas to show the ones they're actively using.


Accessing a zustand store outside of the UI?

Hi :)
Zustand react seems to allow access outside of the UI https://github.com/pmndrs/zustand?tab=readme-ov-file#using-zustand-without-react but the solid plugin doesnt seem to allow for that. It would be nice to be able to do that that.
The reason I am asking is since I essentially am trying to use it as a backend for an application that requires a long polling setup (its a chat app). Meaning I would need to update the client despite the UI state I am currently at. Basically a background job. It would be nice to be able to do this without having to use another store system :D
I hope the explanation of why I am asking makes sense. But feel free to make suggestions or ask further questions. I am new to solidjs so I may also just have missed something obvious here.

Ok turns out due to https://github.com/wobsoriano/solid-zustand/blob/main/src/createWithSignal.ts#L47 I can just not call the function which createWithSignal gives me and then access the original store. Allowing to use the api as described in the url above. :)


Session access token encoding error for Facebook callback

I'm using Facebook provider for authentication in my Vapor 4 app. Everything works fine on localhost, but I get the following error for callback URL for the app deployed on Heroku: invalidValue("long_fb_code_here", Swift.EncodingError.Context(codingPath: [], debugDescription: "Top-level String encoded as string JSON fragment.", underlyingError: nil)). I've found out this happens when setting a session access token in FacebookRouter.swift:52. For some reason the encoder has troubles with encoding the received access token as a string in Sessions+Imperial.swift:62.
As I noted it works fine on localhost which is really strange and I have no clue why. 😅  I have everything set up fine on Facebook side. As a temporary workaround I forked this repo and replaced try session.setAccessToken(accessToken) with session.data["access_token"] = accessToken. That works fine. I really wonder why this is an issue only in the deployed app.
If it is relevant, I use fluent as storage for sessions.

Hmm that's weird. I wonder if it's a Fluent issue 🤔
The only way that line could fail would be if it's trying to set invalid data to JSON. Is this still reproducible?


[PROPOSAL] Supported Ruby versions: 2.1 or later

I propose that we should be going to define Supported Ruby Versions explicitly, and to decide it for v0.14 as Ruby 2.1 or later.
Pros:

Ruby 2.0 requires default value for method keyword arguments

This specification requires programmers to check method values are specified or not in all methods
This requirements brings many terrible code and bugs
Ruby 2.1 allows to use keyword arguments without default values (and raises ArgumentError if not specified)

At Ruby 2.1, def returns symbol

This allows to write private def private_method_name(), and this method signature makes code clear

Ruby 2.1 String has #scrub

Invalid bytes of UTF-8 brings tons of clashes

Ruby 2.1 Socket#getifaddrs

Networking is very important for fluentd, and this method make it better

Cons:

Supported versions of ruby is Ruby2.0 in both of RHEL/CentOS7 and Ubuntu LTS

But these ruby packages has dead-lock bug of require
Many fluentd users don't use system ruby for fluentd now

Today (March 2015), Ruby 1.9.x is not maintained. So we don't support Fluentd on ruby 1.9.x even in Fluentd v0.12.

+1

From td-agent view, td-agent 2 already uses Ruby 2.1.
Older td-agent 1 uses Ruby 1.9 and td-agent 1 never update Ruby and Fluentd major versions.
So dropping Ruby 2.0 is no impact in td-agent world.

:+1:

I found one more reason:
Ruby 2.1 or later have OpenSSL::SSL::SSLErrorWaitReadable and others.
This means that errors on non-blocking I/O for SSLSocket are different on ruby 2.1 from 2.0.

Close this issue.
Let's go with Ruby 2.1!

:+1:


Bare bones installation guide?

Hey guys!
So I found out about Swagger a few days ago - but as I am in *.rc1-final of the MVC tooling it looks like Ahoy is my only real option for Swagger integration (outside of doing it by hand, of course).
I looked at the pull request with partial install instructions, but that is targeted as RC8, and I know there were some changes that mattered from there to rc1.
If we could get any sort of guidance, I will be happy to get it running and write a more significant bit of text on the process and contribute that back into the codebase.
Thanks for all your work in any case.

+1
I've tried using the guide at https://www.myget.org/feed/swashbuckle/package/nuget/Swashbuckle.Swagger
I've tried using the Startup.cs and project.json in the Ahoy Test projects
I've tried using this feed: https://www.myget.org/gallery/swashbuckle
Nothing works. At all.

I eventually did a whole bunch of refactoring and built my own nupkg for it. A bit of a pain, but will tide me over for now.

@shederman Any chance you could share that nupkg? The lack of documentation is rather frustrating...

This is all in pre-release at the mo - just don't got the time to build the docs yet.
I would say check out the examples in the test/Websites folder. Look at the Startup files - it's pretty straightforward.
Feel free to submit a PR with the docs

@shederman have you tried using the official nuget package? https://www.nuget.org/packages/Swashbuckle/6.0.0-rc1-final

@domaindrivendev @shederman Issue was between the chair and keyboard. Should have been more aware of how it was configured. Default url is /swagger/ui. Not /swagger as the documentation for Swagger shows. Thanks!

Sorry for lack of reply, was away on holiday. I found that the tests/Websites didn't even compile.

They compile and work for me. Which version of dnx do you have installed?

rc1. Will try again and check.

Tried again, deleted the repository, fetches everything again, and it built fine. Going to go with "gremlins" :-)


Add missing files to project.

This commit adds missing files from the project. Without this change if
you build the framework from source using Xcode and without Cocoapods,
the build fails.
Background
Implementation
Testing steps
Is this change backwards-compatible?

Build the framework from source without using Cocoapods or SPM, so every missing file causes our projects not to build.
If it's possible it'll be very useful to add to the CI here a step that will build the example project without Cocoapods.


Fix: use model dialect as fallback for audits

Fixes a regression caused by the recent audit refactor. Additional context can be found in this thread.

CI failures are unrelated and have been documented in https://github.com/TobikoData/sqlmesh/pull/3446.


Zero values in imported results are not used

When I import results, values of zero end up as "Not available" in AidStream, and completing an activity is not possible with the error message:
Multiple Baseline Code are missing from the ‘Baseline’ element. of Description element.
The error message is not very clear, but in the XML output it says: Error 1868:Element 'baseline': The attribute 'value' is required but missing.in line no. ..
If I edit the results one by one, the zero values are present, and simply clicking save without any changes then saves it as zero value. After doing that for each result with a zero, it is possible to mark the activity as completed.

Sample results CSV file:
Type,Aggregation Status,Title,Title Language,Description,Description Language,Measure,Ascending,Indicator Title,Indicator Title Language,Indicator Description,Indicator Description Language,Reference Vocabulary,Reference Code,Reference URI,Baseline Year,Baseline Value,Baseline Comment,Baseline Comment Language,Period Start,Period End,Target Value,Target Location Ref,Target Dimension Name,Target Dimension Value,Target Comment,Target Comment Language,Actual Value,Actual Location Ref,Actual Dimension Name,Actual Dimension Value,Actual Comment,Actual Comment Language 1,true,Result zero test,en,,,1,true,Indicator zero test,en,,,99,123,,2016,0,,en,2016-01-01,2016-12-31,0,,,,,,0,,,,, 1,true,Zero point zero,en,,,1,true,Indicator zero point zero test,en,,,99,123,,2016,0.0,,en,2016-01-01,2016-12-31,0.0,,,,,,0.0,,,,,

Hi.
The target and actual value are shown as 'Not Available' whereas the baseline value is shown as 0 if it is a 0 value. However, if the baseline value is missing, i.e., when there is validation error in the file, the above error is shown.
As long as it passes all the schema and AidStream's Validation rules, there should be no problem.
We tested this with the sample data you have provided, and it is working.
Here is the sample file but in xlsx format, as github did not allow me to upload a csv file.
Would you please confirm and let us know.
Thank you.

Hello @rolfkleef
This issue has been solved. Could you please verify from your side.
Thank you.


Test support for RHEL 9 (and derivatives)

Triggered by NLnetLabs/ploutos#64.

Test run here succeeded: https://github.com/NLnetLabs/ploutos-testing/actions/runs/4297888042/jobs/7491436986
Now running a test with Routinator here: https://github.com/NLnetLabs/routinator/actions/runs/4297956163


stdin for sam local doesn't have correct encoding

stdin for sam local doesn't have correct encoding
When piping data to sam local invoke you will get UnicodeEncodeError when presented with non-ASCII Unicode streams.
Steps to reproduce the issue:

Make sure you're using the python2.7 SAM
Create a test file like :  { "city": "Tromsø" }  -- the 'o' character is non-ASCII character
cat test.json | sam local invoke

Note: this only reproduces when it's piped in (via stdin) rather than provided as a '-e file'
Observed result:
Traceback (most recent call last):
  File "/Users/koblas/.virtualenvs/aws-sam/bin/sam", line 11, in <module>
    sys.exit(cli())
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/click/decorators.py", line 64, in new_func
    return ctx.invoke(f, obj, *args[1:], **kwargs)
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/samcli/commands/local/invoke/cli.py", line 44, in cli
    docker_network, log_file, skip_pull_image, profile)  # pragma: no cover
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/samcli/commands/local/invoke/cli.py", line 76, in do_cli
    stderr=context.stderr)
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/samcli/commands/local/lib/local_lambda.py", line 80, in invoke
    stdout=stdout, stderr=stderr)
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/samcli/local/lambdafn/runtime.py", line 68, in invoke
    env_vars = environ.resolve()
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/samcli/local/lambdafn/env_vars.py", line 100, in resolve
    result[name] = self._stringify_value(value)
  File "/Users/koblas/.virtualenvs/aws-sam/lib/python2.7/site-packages/samcli/local/lambdafn/env_vars.py", line 195, in _stringify_value
    result = str(value)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf8' in position 16: ordinal not in range(128)

Expected result:
Lambda function should run in the sam way as if invoked as sam local invoke -e test.jsonAdditional environment details (Ex: Windows, Mac, Amazon Linux etc)
Output of sam --version:
SAM CLI, version 0.4.0
Optional Debug logs:
Add --debug flag to command you are running

Actually, it is not the stdin. It is stringifying the environment variables that are passed.
It is easy to fix: At this line, update the condition to do str(value)  only if string is not unicode. You also need to do this only for Python2.
Will you be interested in sending a Pull Request? I can help you out with it if you are stuck

Truthfully, dealing with these encoding issues in python is not something that I enjoy.  As you probably know, dealing with the Python 2 vs 3 and the file encoding vs the locale encoding always leaves edge cases around.
Since what happens if the file is in UTF-8 and the locale is in ISO-8859-5 so you have environment variables in a different encoding than the file input.  Maybe you do have an easy fix that I'm over thinking.

Closing this as it was released in 0.6.0


Alert: TargetDown in kube-system

Alert TargetDown firing in kube-system namespace
This is an automated issue created by the monitoring system. Please do not edit this message.
Alertmanager URL: https://alertmanager.ankhmorpork.thaum.xyz
Issue was last updated at 2023-03-07 15:35:54.361497113 +0000 UTC m=+5306.197458924.
Common Labels

alertname
TargetDown

cluster
ankhmorpork

job
kubelet

namespace
kube-system

prometheus
monitoring/k8s

severity
warning

Common Annotations

description
16.67% of the kubelet/ targets in kube-system namespace are down.

runbook_url
https://runbooks.prometheus-operator.dev/runbooks/general/targetdown

summary
One or more targets are unreachable.

Alerts

StartsAt
Links

2023-03-07 15:28:48.612 +0000 UTC
GeneratorURL

(DO NOT MODIFY: 94dfa839b818df033c2fd5c399524e220141b7e1b739d2805273cb0d3a25758e )

Fixed with #201


Added a "object storage" description about Ceph

Hi guys,
I know, this is pretty simple, maybe don't do any difference but is good to tell about this. Sometimes people think that only with Noobaa they can create ObjectBucketClaims and forget about the ocs-external-storagecluster-ceph-rgw StorageClass.
From time to time I got someone thinking in this way.
Thanks!

Hello @hector-vido Thanks for the PR, Can you pls follow our Contribution guide [1] to write a commit message as per our requirements. Also pls sign off the commit.
[1]. https://github.com/red-hat-storage/odf-operator/blob/main/CONTRIBUTING.md#commit-structure

/ok-to-test