Time format issue

The time format changes depending on the language of the pc and prevents the playlist from downloading. For the software to work you need the time format "yyyy-MM-dd" but other people can have the time format "dd / MM / yyyy" (this is the case in France). The format can be changed in the settings but this could cause problems for those who do not know this feature.

I'm not using time formats when downloading playlists, did you mean the 'Subscriptions' tab?
I'm using the dd/MM/yyyy format myself and I don't have any issues with downloading playlists

Thats very strange, I'm able to download it, my system time format is dd/MM/yyyy.
Do you get an error or is it just not downloading? could you share the Errors.txt file? it is located at %appdata%\Youtube Playlist Downloader

"Le format de la chaîne d'entrée est incorrect." means "The format of the input string is incorrect." and "La clé donnée était absente du dictionnaire." means "The given key was missing from the dictionary." Idk why it's not in english in the file.
Errors.txt

I tried again and the download worked.

It could be something on YouTube's end, if it works now that's the only hypothesis I have


added name and thanks

This doesn't seem to print out "Aku Cinta Kamu", please take a look in your .py file 😄


dns and container repos support for gcp

@xpositivityx note the cloud field isn't consistent. Not sure if this matters or now. Following the naming from AWS.

@WillBeebe thsi will need to be released before container repo support will work for gcp


Treat failure to collect metric as fatal

Exit on any failure to collect metrics.  This will give
stackdriver_exporter a chance to start over and perhaps recover from
transient errors.  For example: if it's Google credentials have expired
and have been replaced, it can restart to try to load up new ones.
 That should fix up the tests.
Also, if you wouldn't mind adding an entry to the CHANGELOG
* [BUGFIX] Treat failure to collect metric as fatal #83

Done and done.


Unable to build ogre on OS X 10.9.2

This is a freetype error that is arising when trying to install ogre.
See the gist here: https://gist.github.com/skotturi/108f6e149b0e38424e7f

I have ogre installed via homebrew:
$ brew info ogre
osrf/simulation/ogre: stable 1.7.4 (bottled), HEAD
Object-Oriented Graphics Rendering Engine
http://www.ogre3d.org/
/usr/local/Cellar/ogre/1.7.4 (487 files, 16.3M) *
  Poured from bottle
From: https://github.com/osrf/homebrew-simulation/blob/master/ogre.rb
==> Dependencies
Build: cmake ✔
Required: boost ✔, doxygen ✔, freeimage ✔, freetype ✔, libzzip ✔, tbb ✔
==> Options
--with-cg

--HEAD
	Install HEAD version


dummy file

https://tools.hmcts.net/jira/browse/RWA-201

I close it because I need to raise a new one. @lewis150193, FYI.


Crash in zrepl daemon

Using zrepl 0.7.6 on Void linux, I'm getting a crash in the daemon while executing a job.  The configuration was working with one of the first releases tagged in this repo, 0.6.6.  Attached is a debug log and the zrepl.yaml that was used. I'm happy to provide additional details as needed.
zrepl.debug.txt
zrepl.yml.txt

Hi,
Sorry, I didn't get a notification about this issue. Could you try to reproduce this crash using latest 0.8.0 version?

Feedback timeout.

I built 0.8.2 locally on Void and I can confirm that it's working as expected now. Lots of nice improvements in there, thanks for continuing to drive this project forward!

Glad to see it, thank you.


[Rhino] NGon Mesh Faces are broken

Explanation
Imported a sketchup model into Rhino and sent it into Speckleverse. This is the Rhino model sent:

This is how it looks like in the viewer👇:

Its not a viewer issue. When received back in Rhino, they come with broken meshes:

Commits Used
https://latest.speckle.dev/streams/28dd9ad7ba/commits/38e7fbd2b0
Files
chair.zip

Closing after confirming with Bilal this is no longer an issue.


Bug: Soft vs hard minimum for power capping

We've been working with Shilpa and Vaidy on an issue that we'd like to see addressed in a future release of OPAL for IBM witherspoon. I'm documenting our issue, Shilpa's fix and some additional notes here. I was hoping to see this change in hw/occ.c in 6.0.8 but looks like it didn't make it in there.
Minimum power cap in OPAL was based on the "hard" minimum power cap and was assuming that GPUs are in peak power use of 250W, resulting in a minimum node power of 1700 W. Ideally, this minimum should be the "soft" minimum power cap, which is 500 W. This is captured in the figure below (courtesy: Todd Rosedahl).
Ideally, it'd be great if the hard and soft power minimums were exposed separately through the /sys/firmware/opal/powercap/system-powercap/ interface. This would let advanced users as well as system admins determine how they would like to configure their node when needed.
There are several scenarios where a workload running on a node may use no GPUs or fewer than 4 GPUs, and in these cases, being able to set the power cap to be low enough gives us the ability to redirect extra power to CPUs, other jobs on the cluster, or just save power. Thanks!

Shilpa's fix was as follows. It'd be ideal if both hard and soft min power caps were exposed through OPAL.
diff --git a/hw/occ.c b/hw/occ.c
index a55bf8e..7e6e02e 100644
--- a/hw/occ.c
+++ b/hw/occ.c
@@ -246,7 +246,8 @@ struct occ_dynamic_data {
        u16 min_pwr_cap;
        u16 max_pwr_cap;
        u16 cur_pwr_cap;
-       u8 pad[112];
+       u16 soft_min_pwr_cap;
+       u8 pad[110];
        struct opal_command_buffer cmd;
        struct occ_response_buffer rsp;
 } __packed;
@@ -1362,7 +1363,7 @@ int occ_get_powercap(u32 handle, u32 *pcap)

        switch (powercap_get_attr(handle)) {
        case POWERCAP_OCC_MIN:
-               *pcap = ddata->min_pwr_cap;
+               *pcap = ddata->soft_min_pwr_cap;
                break;
        case POWERCAP_OCC_MAX:
                *pcap = ddata->max_pwr_cap;
@@ -1410,7 +1411,7 @@ int occ_set_powercap(u32 handle, int token, u32 pcap)
                return OPAL_SUCCESS;

        if (pcap && (pcap > ddata->max_pwr_cap ||
-           pcap < ddata->min_pwr_cap))
+           pcap < ddata->soft_min_pwr_cap))
                return OPAL_PARAMETER;

        pcap_cdata = pcap;

Thanks for the bug report. This is an area where I've been a bit suspicious there's bugs hiding around the place, and indeed, our op-test tests were showing some failures in the powercap tests (at least with op-build master on some platforms).
I'm trying to chase down why that is, but https://github.com/open-power/op-test-framework/blob/adeaa20/testcases/OpalSysfsTests.py#L107 is my new and improved test case for it, and this should be enough to at least start to ask questions of the OCC team. I'll try and incorporate pulling some debug data from the OCC on test failure too, as that may help get to the bottom of it.
As for the issue of hard vs soft minimum, hrm... it looks like the device tree bindings and kernel driver completely don't take into account the concept of a soft minimum power cap.
The patch you mention there, which is https://patchwork.ozlabs.org/patch/958105/ is one I don't think I want to take as-is, as then there's no way to work out what the hard minimum is.
I think the correct solution here is going to be twofold:

add a soft min powercap to the device tree bindings.
add support for this to the kernel.

FWIW this is what I'm getting as a current failure on a DD2.1 witherspoon running op-build master and the testcase mentioned above:
======================================================================
FAIL [114.099s]: test_opal_powercap (testcases.OpalSysfsTests.Skiroot)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/stewart/op-test-framework/testcases/OpalSysfsTests.py", line 120, in test_opal_powe
rcap
    self.set_power_cap(min_powercap)
  File "/home/stewart/op-test-framework/testcases/OpalSysfsTests.py", line 98, in set_power_cap
    repr(valid_powercap_values)))
AssertionError: Retrieved powercap was not either the previous one (3050) or the one we're trying
 to set (1700). Got 1550, expected in [3050, 1700]

----------------------------------------------------------------------
Ran 1 test in 114.099s

and then, if you run it again without an IPL:
======================================================================                           FAIL [58.049s]: test_opal_powercap (testcases.OpalSysfsTests.Skiroot)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/stewart/op-test-framework/testcases/OpalSysfsTests.py", line 119, in test_opal_powe
rcap
    self.set_power_cap(max_powercap)
  File "/home/stewart/op-test-framework/testcases/OpalSysfsTests.py", line 105, in set_power_cap
    cur_powercap, value))
AssertionError: OPAL failed to set power cap value. Got 1550 when trying to set 3050.
                                                                                ----------------------------------------------------------------------
Ran 1 test in 58.049s

@stewart-ibm: Thanks for looking into this!
Shilpa's patch is a temporary fix. I agree that adding soft power min to devicetree and adding support for it in the kernel is the right way to go. Both the hard and soft power caps should be exposed through OPAL, along with explanation/documentation about what guarantees to expect in each case. As in, when you set a soft power cap, you may go over the limit temporarily, and more experimentation is needed to understand the time window and maximum range for exceeding the power cap would be.
Another important knob that's not currently exposed is that of Turbo frequencies/ultrascale, I'll circle around to that once I have a better understanding for it.

https://github.com/open-power/op-test-framework/blob/master/testcases/OpTestEM.py has a bunch of tests for turbo / ultraturbo and how that is mapped out in sysfs.
https://open-power.github.io/skiboot/doc/device-tree/ibm,opal/power-mgt.html has some bare bones documentation on the device tree entries too. (and wow, the documentation there really needs expanding upon. Patches would be much appreciated :)

Hi Tapasya,
Sorry for taking a long time to resolve this. I have posted a new version of the skiboot patch to fix the issue which requires minimal changes to the kernel to export the full powercap range.
https://lists.ozlabs.org/pipermail/skiboot/2019-February/013165.html
This skiboot patch changes the "powercap-min" property to point to soft powercap minimum limit instead of hard powercap minimum. It also adds DT property "powercap-hard-min" to export the hard powercap minimum.
The kernel changes with this DT updates are minimal to adding a new sysfs file to export the hard min powercap limit.

Thank you, Shilpa!

The fix for this issue is available in skiboot
https://github.com/open-power/skiboot/commit/a96739c6c1cdf02521cab703733cef8cb54debbf
This patch is queued for stable and should subsequently be available in the next service-pack
The kernel patch to export hard-min powercap is also posted
<EMAIL_ADDRESS>

Excellent! Thank you, Shilpa! Looking forward to the next service pack being available.

The fix is now in the 6.0.18 stable branch https://github.com/open-power/skiboot/commit/a3c88493956190b5079139f4b1aef0a3cbb2dd42

The skiboot image with the fix  is available in PNOR level OP910_1913D
IBM-witherspoon-OP9_v2.0.14_1.2
op-build-v2.0.14-420-gb32daa2
buildroot-2018.05.1-9-gc99f2ee
skiboot-v6.0.18
hostboot-14fd85c-p80ac538
occ-394de99
linux-4.17.12-openpower1-p2f43189
petitboot-v1.7.5-p6a40ae5
machine-xml-94a137f
hostboot-binaries-5c5adec
capp-ucode-p9-dd2-v4
sbe-4aa6703

shilpasri<EMAIL_ADDRESS>writes:

The skiboot image with the fix  is available in PNOR level OP910_1913D
IBM-witherspoon-OP9_v2.0.14_1.2

IBM builds aren't too relevant for the public project though, the real
bit that is relevant is the skiboot version:

skiboot-v6.0.18

as this op-build version number isn't an upstream commit:

op-build-v2.0.14-420-gb32daa2

--
Stewart Smith
OPAL Architect, IBM.


Shibboleth - principalType group not present in principals on first login. After a second login the group principalType is added.

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Setup a new Rancher 2.4 install. I used commit id: e11d47814
Configure Shibboleth with OpenLDAP
Create a cluster and add group1 as owner.
logout from the Shibboleth admin and login as testuser2 or other member of group1

This would be the first time testuser2 logs into Rancher

Result:

At this point you won't be able to see the cluster even though testuser2 belongs to group1
checking /v3/principals there's no principalType group for the user.
Log out and login as testuser2 again.
The cluster will be visible this time
/v3/principals for the user will show the group principalType

Other details that may be helpful:
First login /v3/principals
{

    "type": "collection",
    "links": {
        "self": "…/v3/principals"
    },
    "actions": {
        "search": "…/v3/principals?action=search"
    },
    "pagination": {
        "limit": 1000
    },
    "sort": {
        "order": "asc",
        "reverse": "…/v3/principals?order=desc",
        "links": {
            "loginName": "…/v3/principals?sort=loginName",
            "name": "…/v3/principals?sort=name",
            "principalType": "…/v3/principals?sort=principalType",
            "profilePicture": "…/v3/principals?sort=profilePicture",
            "profileURL": "…/v3/principals?sort=profileURL",
            "provider": "…/v3/principals?sort=provider",
            "uuid": "…/v3/principals?sort=uuid"
        }
    },
    "filters": {
        "created": null,
        "creatorId": null,
        "id": null,
        "loginName": null,
        "me": null,
        "memberOf": null,
        "name": null,
        "principalType": null,
        "profilePicture": null,
        "profileURL": null,
        "provider": null,
        "removed": null,
        "uuid": null
    },
    "resourceType": "principal",
    "data": [
        {
            "baseType": "principal",
            "created": null,
            "creatorId": null,
            "id": "shibboleth_user://testuser2",
            "links": {
                "self": "…/v3/principals/shibboleth_user:%2F%2Ftestuser2"
            },
            "loginName": "testuser2",
            "me": true,
            "memberOf": false,
            "name": "testuser2",
            "principalType": "user",
            "provider": "shibboleth",
            "type": "principal"
        }
    ]

}

Second login:
{

    "type": "collection",
    "links": {
        "self": "…/v3/principals"
    },
    "actions": {
        "search": "…/v3/principals?action=search"
    },
    "pagination": {
        "limit": 1000
    },
    "sort": {
        "order": "asc",
        "reverse": "…/v3/principals?order=desc",
        "links": {
            "loginName": "…/v3/principals?sort=loginName",
            "name": "…/v3/principals?sort=name",
            "principalType": "…/v3/principals?sort=principalType",
            "profilePicture": "…/v3/principals?sort=profilePicture",
            "profileURL": "…/v3/principals?sort=profileURL",
            "provider": "…/v3/principals?sort=provider",
            "uuid": "…/v3/principals?sort=uuid"
        }
    },
    "filters": {
        "created": null,
        "creatorId": null,
        "id": null,
        "loginName": null,
        "me": null,
        "memberOf": null,
        "name": null,
        "principalType": null,
        "profilePicture": null,
        "profileURL": null,
        "provider": null,
        "removed": null,
        "uuid": null
    },
    "resourceType": "principal",
    "data": [
        {
            "baseType": "principal",
            "created": null,
            "creatorId": null,
            "id": "shibboleth_user://testuser2",
            "links": {
                "self": "…/v3/principals/shibboleth_user:%2F%2Ftestuser2"
            },
            "loginName": "testuser2",
            "me": true,
            "memberOf": false,
            "name": "testuser2",
            "principalType": "user",
            "provider": "shibboleth",
            "type": "principal"
        },
        {
            "baseType": "principal",
            "created": null,
            "creatorId": null,
            "id": "shibboleth_group://cn=group1,ou=groups,dc=example,dc=org",
            "links": {
                "self": "…/v3/principals/shibboleth_group:%2F%2Fcn=group1%2Cou=groups%2Cdc=example%2Cdc=org"
            },
            "me": false,
            "memberOf": true,
            "name": "cn=group1,ou=groups,dc=example,dc=org",
            "principalType": "group",
            "provider": "shibboleth",
            "type": "principal"
        }
    ]

}

Environment information

Rancher version: 2.4 master-head (02/19/2020) commit id: e11d47814
Installation option (single install/HA): single

This is still reproducible in Rancher version 2.4 master-head (02/22/2020) commit id: 26d38e1dd

Rancher version: v2.4.0-rc1 (ca71db485)

Validated the principalType: group are retrieved as expected on users first login in Shibboleth Only Auth setup.
Validated the principalType: group are retrieved as expected on users first login in Shibboleth+OpenLDAP Auth setup.

Validated the RBAC use cases for Site, Cluster and Project access. I didn't have to re-login to check the access when a group was added as member and a user of that group login for the first time.


Helm 3: Registry blob storage to follow OCI Image Layout Spec

Currently the charts are stored in custom fashion in ${HELM_HOME}/registry:
$ tree ~/.helm/registry
/Users/me/.helm/registry
├── blobs
│   └── sha256
│       ├── 3344059bb81c49cc6f2599a379da0a6c14313cf969f7b821aca18e489ba3991b
│       └── 84059d7403f496a1c63caf97fdc5e939ea39e561adbd98d0aa864d1b9fc9653f
├── charts
│   └── mychart
│       └── versions
│           └── 2.7.1
└── refs
    └── localhost_5000
        └── myrepo
            └── mychart
                └── tags
                    └── latest
                        ├── chart -> /Users/me/.helm/registry/charts/mychart/versions/2.7.1
                        ├── content -> /Users/me/.helm/registry/blobs/sha256/3344059bb81c49cc6f2599a379da0a6c14313cf969f7b821aca18e489ba3991b
                        └── meta -> /Users/me/.helm/registry/blobs/sha256/84059d7403f496a1c63caf97fdc5e939ea39e561adbd98d0aa864d1b9fc9653f

Instead, Helm should adhere to the OCI Image Layout Specification:
$ find . -type f
./index.json
./oci-layout
./blobs/sha256/3588d02542238316759cbf24502f4344ffcc8a60c803870022f335d1390c13b4
./blobs/sha256/4b0bc1c4050b03c95ef2a8e36e25feac42fd31283e8c30b3ee5df6b043155d3c
./blobs/sha256/7968321274dc6b6171697c33df7815310468e694ac5be0ec03ff053bb135e768

cc @jzelinskie @bacongobbler

Hye @jdolitsky where are we with this?

IIRC @stevvooe mentioned that there is a library in containerd that abstracts this away. I have no idea if it'll work alongside your XDG_HOME/CONFIG PR, though.

upstream ticket: https://github.com/deislabs/oras/issues/107

Thanks for the heads up @jzelinskie! I'll do some digging in containerd and see what comes up.

Hi, hoping to have this land upstream in ORAS early next week.
On Wed, Jul 31, 2019 at 1:44 PM Matthew Fisher<EMAIL_ADDRESS>wrote:

Thanks for the heads up @jzelinskie https://github.com/jzelinskie! I'll
do some digging in containerd and see what comes up.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/helm/helm/issues/6068?email_source=notifications&email_token=AADACFXPFNJEX5WFZ3WMIR3QCHMRZA5CNFSM4IGHQJG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3IGAIQ#issuecomment-516972578,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADACFXYUFIVT5HMWR7ZMQ3QCHMRZANCNFSM4IGHQJGQ
.

removing from the beta milestone as #6185 has been PR'd, which means this discussion can move forward without blocking the release.

closed via https://github.com/helm/helm/pull/6205


Diable empty messages

Describe the bug
Currently anyone can send empty messages in the chat box
To Reproduce
Clear steps describing how to reproduce the issue.

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected result
What should happen?
Actual result
It should not send any empty messages
Screenshots

Are you willing to contribute to this issue? [Yes]
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hi @garvitgupta13, First of all, thank you so much for taking out the time to create this issue.
Definitely 🙌, Please go forward to work on this issue. I am assigning this Issue to you 👍
And last but not least,
Keep Contributing 🙏🔥

Hey @Akash-Salvi can you please let me know where can I get me REACT_APP_ONLINE_JUDGE_API key

Hey @Akash-Salvi can you please let me know where can I get REACT_APP_ONLINE_JUDGE_API key

It's a Rapid Api online Judge. Here is the API Ref. You can register and get your credentials.
happy Contributing !

Hey @Akash-Salvi can you please let me know where can I get REACT_APP_ONLINE_JUDGE_API key

It's a Rapid Api online Judge. Here is the API Ref. You can register and get your credentials.
happy Contributing !

Please review my PR


Add geoparquet.js

Add link to hyparam/geoparquet which is a new library for converting geoparquet into geojson. It's written in 100% javascript, and is only 9.2kb compressed including parquet parsing.

FYI your demo doesn't work for me

The demo works on all my browsers, and works for the friends I sent it to? Is your adblock interfering?

@kylebarron I switched to google maps loading=async does that fix anything for you? (I'm unable to repro)

Indeed now it works for me


c library

There is a C API, is there a C library to link to? What is the plan for running gluon in c/c++ (if any)?

Hi an-kumar,
Thank you for your question!
There is currently no C library - only the API specification - but the C library will be added to this repository at a future point.
This project is a community-driven effort, so there is not specific timeline around roadmap items. Your recommendation for a Gluon implementation in C/C++ is a great request, and we welcome the community to contribute.


Do not install pulumi automatically

Pulumi is marked as a requirement, but I do not expect a Makefile to install it for me using curl | bash. I would prefer to get an error and figure out myself how to install Pulumi. Notably, if I have an environment with Pulumi but I forgot to switch to it, I don't expect to have another copy installed this way.

hi! We apologize for having neglected this pull request.
Our current approach is actually installing Pulumi for each provider build in the provider repository and overriding your local Pulumi.
I've filed https://github.com/pulumi/pulumi-tf-provider-boilerplate/issues/114 to track that here and am closing this pull request.


Spec says that dimensions on a thumbnail are optional, but does not define the expected behaviour if they are omitted

https://matrix.org/docs/spec/client_server/r0.4.0.html#get-matrix-media-r0-thumbnail-servername-mediaid.
Personally I'm of the opinion that these should be mandatory, but if they are not we should define the expected behaviour. Note that synapse currently 500s if they are omitted: https://github.com/matrix-org/synapse/issues/2748

Worth also noting that matrix-media-repo handles this nicely. I'm all for making them required though.

what is matrix-media-repo's behaviour, ooi?

picks the first configured thumbnail size in the config:
https://github.com/turt2live/matrix-media-repo/blob/master/src/github.com/turt2live/matrix-media-repo/api/r0/thumbnail.go#L42-L44

I made an executive decision.


Remote control callbacks

I propose an easy and clean way to register simple callbacks which are triggered as a remote control button is switched.
IT can be used as follows:
remote_callback_register(remote, my_cb_function, my_structure, remote_channel);
As the value of remote_channel changes, the function my_cb_function(my_structure, new_value); is called.
This allows to register callback without modifying the MAVRIC_Library. Furthermore, it is structured and clean. Furthermore, is "synchronized" with remote_update function, which avoids polling to often or not often enough

Sounds good !
Can we have a parameter to register the callback only for rising event or falling event or both ?

Good idea to allow specification of rising/falling/both!
We could also add the remote_channel to the parameters given to the callback function, this would allow to have the same function on different buttons and to know which button has trigger the callback, but I don't no if it is really useful.

I added rising/falling edge to the latest commit. However, at the moment the edge direction is not given to the function. Should it be given or should we leave that to the "user" ? (since the new value is transmitted, he could store the old value in the struct and compare)
There is an issue with the 11bit protocol: there is a tiny jitter on the button values (I have never seen the raw value to vary more than +/-1). If it really varies only between +/-1, than I will add that the change should be larger than 1. If it can be more, we could either define a common epsilon for all callbacks or let the "user" define an epsilon for each callback.

Closing this issue in favour of issue #106.


[only test] sink filter fin  only RUNNABLE

Proposed changes
Issue Number: close #xxx

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

run buildall

run buildall


flex: [number] not work in ScrollView

I have some jsx below
<View>
  <ScrollableTabView>
    <ScrollView>
      <CustomView></CustomView>
    </ScrollView>
  </ScrollableTabView>
</View>

all above jsx tag have style flex: 1, and I want to use flexbox layout in CustomView tag, but I find that flex: [number] can't work.
however, when I specify height css property of CustomView component, all things back to normal.
if I don't know height, how could I use flex: [number] in my CustomView?
thanks for your time.

I'm not sure that you can use flex for elements inside ScrollView maybe someone will give better answer.

I'm having this same problem

Same here.  I notice that if I put a ListView in a team it nicely uses up all the available space.  But if I put a view in there with flex: 1 it does nothing.  Anyone got a solution?

I've "solved" it wrapping the scrollview with a view and put flex on it (view).

Closing as this issue is very old, feel free to open a new issue if its still happening in the latest release


avtSiloFileFormat::GetGlobalNodeIds does not work for POINT meshes

          @markcmiller86 I just noticed another interesting thing. When avtGenericDatabase fails to get the global node ids from the cache, it allows the interface to attempt retrieval by calling `GetGlobalNodeIds`.

 avtSiloFormat::GetGlobalNodeIds only considers UCD meshes, not Point meshes.
Originally posted by @biagas in https://github.com/visit-dav/visit/issues/19130#issuecomment-1885129155

resolved in #19302 (3.4RC) and #19315 (develop)

@biagas...thanks for pointing this out. Its a subtle difference that should be corrected. One is pre-caching global node ids for a point mesh in case they are ever asked for. The other issue (the one your are describing here) is if for some reason global node ids are not pre-cached for a point mesh (I can't imagine why that might happen), then they are never obtained via this more explicit route. I have reopened and moved to 3.4.3. The right action for 3.4.3 may be to just close this again after confirming that the path you describe cannot happen.


[FEATURE REQUEST]use @hapi/joi for schema description and data validation

Is your feature request related to a problem? Please describe.
It is important to do validation of data from a user before persisting it in the db.Data validation can get very complex especially when dealing with multiple schemas like we are.
Describe the solution you'd like
@hapi/joi is a module that is used to define a schema or blueprint of Javascript objects. Once the schema is defined, you then can use Joi's handy methods that come bundled with it, to validate any other objects against the schema. In our case the req.body will be compared with a schema we describe using @hapi/joi. @hapi/joi will also create detailed error messages for us so we don't have to write error messages again and again for every case.
Describe alternatives you've considered
I've considered writing all the validation from scatch for all the schemas but this can get long and clutter our code.
Additional context
With @hapi/joi we can just describe a schema and compare it with data sent by a user every time a POST request is made.Joi will validate the data and create a detailed error message if any errors are found.
I'd like to work on this so please assign this to me if this issue is accepted.

Can I work on this?


ENH: report the issue back on the status page

would be nice to have a way for a hover over or else to see the actual issue with the changelog, without needing to click to the full log.

Next time you see this again, can you please post a screenshot for clarity? Thanks!

Here you are, this is what I see on https://github.com/astropy/pyvo/pull/465 without the proper label. Then of course the log tells me what its problem actually is:
 PYTHON=/usr/bin/python3.8
WARNING: Invalid version string: 0.7rc1 (2018-02-18)
Changelog entry not present, (or PR number missing) and neither the **Affects-dev** nor the **no-changelog-entry-needed** label is set.

I think it was implemented to some degree (using REST API) in baldrick but we do not use that here:
https://github.com/OpenAstronomy/baldrick/blob/f06badcdb817e66124408aa24c0119e28bc4b109/baldrick/github/github_api.py#L181

Ah, since we use PyGithub, maybe this is more relevant though we need to pass in some SHA from the pull request object:
https://pygithub.readthedocs.io/en/latest/examples/Commit.html

I looked at the script again and to properly support this, might as well refactor from simple Python script to a proper Actions calls but I don't have time to do it.


Questions about using tiles

Hello,
I have a few questions about using the tiles:

what is exactly the difference between analog tile and inference tile? I thought that analog tile is an abstract object and we can't really use it, but as I seen in some of your examples you use it explicitly (as seen in example 01 where you use SingleRPUConfig() which uses AnalogTiles).

How can I specify the size of the tile after defining an rpu configuration? from looking at you documentation, I saw that when creating a tile, the user can specify it's size, as following tile = InferenceTile(32, 32). but when creating a model or when using an existing one and converting it to analog counterpart, we use rpu_config = InferenceRPUConfig(). I'd appreciate if you could explain to me:

What is the difference between the configuration and the tile itself? the configuration just allows the user to specify more parameters for a specific tile right?
When defining configuration as follows rpu_config = InferenceRPUConfig() Suppose now I want to change the tile to be 32x32. how can I do it? by viewing you documentation I saw the functions rpu_config.forward.inp_res and rpu_config.forward.out_res which quantise the ADC and DAC. so should I specify rpu_config.forward.inp_res = 1/32 and rpu_config.forward.out_res = 1/32 or did I misinterpreted the meaning of the last two functions? I saw this example also:

from aihwkit.simulator.tiles import AnalogTile
from aihwkit.simulator.configs import SingleRPUConfig
from aihwkit.simulator.configs.devices import ConstantStepDevice

config = SingleRPUConfig(device=ConstantStepDevice())
tile = AnalogTile(32, 32, rpu_config=config)

how can I make sure this tile will be used in the configuration which is sent to the model as seen in example 03:
def create_analog_network(input_size, hidden_sizes, output_size):
   ...
    model = AnalogSequential(
        AnalogLinear(input_size, hidden_sizes[0], True,
                     rpu_config=SingleRPUConfig(device=ConstantStepDevice())),
        ...

When using InferenceRPUConfig I saw that the default Tile type is InferenceTile but of what size (out_size and in_size)? and I also saw that you're using ConstantStepDevice as defult, but of what precision?

Is there any way to create our own configuration? this is, specify explicitly the tile with it's parameters, and the device and create an rpu configuration from it to send to the model?

Thank you very much for your help.

Hi @ElinorG11 ,
thanks for your questions !
to 1: The InferenceRPUConfig (which generates an InferenceTile) has a number of features that are useful for hardware that only support inference, whereas the other AnalogTile implement some realistic way of investigating analog training directly on the crossbar array.   The difference is that for hardware that only support analog inference,  backward and update is not supported on the chip itself. For these chip designs, InferenceRPUConfig is used. Note that one can still train a network with the InferenceTile with AIHWKIT which in this case however uses a perfect backward and update step and thus does "hardware-aware" (software) training, in that only the forward pass is non-ideal. It also provides a mechanism to use realstic PCM calibrated programming noise and drift during the inference.  Please consult the documentation for more details
to 2: The rpu configuration sets all the meta-parameter that essentially define the hardware design, such as noise strengths, device-to-device variations etc.  The size of the tile is currently determined solely be the DNN layer. So it will be as big as needed for a layer. If one wants to restrict the tile size, currently one needs to change the DNN accordingly so that it has smaller weight matrices (e.g. by simply splitting a linear layer into multiple parts and adding/concatenating the outputs). We will however soon a new layer where the maximal physical tile size can be defined.    Note that only the maximal tile size is of concern. If you have a DNN where all layers are smaller than the max tile size, the current simulation is accurate with the assumption that non-used devices do not contribute to the non-idealities, which should be true in first approximation.
Note that the inp_res and out_res are just the DAC/ADC converter resolutions, it has nothing to do with the tile size. Weights are not sliced across multiple crossbar arrays. If you want to investigate this, you can simple generate multiple tiles for each slice.
Note again that SingleRPUConfig and ConstantStepDevice define a hardware that is capable of doing analog training (in contrast to hardware designs that support only inference).
to 3:  Sure that is the idea. You can just define the setting of your hardware by specifying your own rpu_config

Thank you very much for the detailed answer. I just want to make sure I understood correctly: the number of cross-points at the crossbar array (i.e. the size of the tile) is determined by the layer with the maximal input*output size (thus making sure that the crossbar will contain enough devices to store all the weight for every layer)? what confused me was the fact that I can create a tile of a specific size such as: tile = InferenceTile(10,20,config) but I suppose that the user has no use of it, and it is only used internally by InferenceRPUConfig() ?

Oh, I see what you mean. Typically, the rpu_config will specify the Tile class that is constructed. Typically you just construct say a linear layer, e.g. AnalogLinear(5, 6, rpu_config) and then it will use a tile that is specified by the rpu_config. You don't need to call InferenceTile directly. Working on the tile level is more low-level and only useful if one wanted to implement new layers that for instance would use multiple tiles under the hood.

Thank you for your guidance!


DEV-36849; fix: trigger input event before and after replacement

Make replacements work in Quip Editor
Quip is a state based editor, it triggers changes to state when it encounters events.
Example: When you press a key on keyboard, beforeInput and input events are triggered on the text node, which then bubble up in the DOM
Our current workflow does not trigger input events on text node, the text appears to change on DOM but the state inside editor doesn't update, resulting loss of changes when browser is reloaded.
Solution:

Trigger input events simulating real world scenario, which helps the editor to understand that it needs to update its state
The input events are specifically triggered on text node as text nodes are the leaf nodes and events can then bubble up in DOM
The solution implemented is a generic solution, rather than limiting only to Quip
Config option added to disable input event simulation if not necessary

Tests:

Added test on ContentEditable and StateBasedAdapter to verify if simulated events are triggered
Existing 500+ tests continue to work as expected

@pcdeshmukh
Addressed the following:

check parent node is null before triggering event - @loaiabdelhalim suggestion
renamed fakeInput to simulateInput
simulated event in pairs wherever used
async state based adapter test check for both input events


Transformers branch: BIDSEventsCollection expects "trial_type" column

Although the doc string says trial_type is optional, the default value is not None. Thus, when it is not found (because it is not required per BIDS spec), an error is thrown. I wrote the original code, so I can fix it soon!

The pattern has changed; see the init docstring. Right now the condition_column argument specifies where to look for conditions, and it defaults to 'trial_type'. If set to None, this should work fine for event files without 'trial_type'.
We could set the default to None, but my guess is that the (vast?) majority of inputs will have a trial_type column, so it's probably better to make the exceptions change the argument rather than the other way around. Can you set condition_column to None and see if it works for you?

Also, please add "in transformers branch" to the issue title, as this hasn't been merged yet, so other people don't need to worry about it.

Alright actually I think that's fine. Probably what would be better is if trial_type is not found, it doesn't throw and error but just a warning. This makes it easier to generic code using the event collection without knowing if that task has a trial_type column or not.

Closing because the internal model has changed to not treat trial_type differently from other columns.


fix<EMAIL_ADDRESS>Android compatibility

Updated CMakeLists.txt to comply with new<EMAIL_ADDRESS>specs

Hi @numandev1, this is good to go.
For those who can't wait:
react-native-keys+0.7.10.patch
diff --git a/node_modules/react-native-keys/android/CMakeLists.txt b/node_modules/react-native-keys/android/CMakeLists.txt
index f453363..8f262ec 100644
--- a/node_modules/react-native-keys/android/CMakeLists.txt
+++ b/node_modules/react-native-keys/android/CMakeLists.txt
@@ -9,6 +9,7 @@ set(BUILD_DIR ${CMAKE_SOURCE_DIR}/build)
 if(${REACT_NATIVE_MINOR_VERSION} GREATER_EQUAL 71)
     # Consume shared libraries and headers from prefabs
     find_package(ReactAndroid REQUIRED CONFIG)
+    find_package(fbjni REQUIRED CONFIG)  # Add this line to find fbjni

     include_directories(
         ${PACKAGE_NAME}
@@ -49,7 +50,17 @@ if(${REACT_NATIVE_MINOR_VERSION} GREATER_EQUAL 71)

     find_package(openssl REQUIRED CONFIG)

-    target_link_libraries(
+    if (REACTNATIVE_MERGED_SO OR ReactAndroid_VERSION_MINOR GREATER_EQUAL 76)
+     target_link_libraries(
+        ${PACKAGE_NAME}
+        ${LOG_LIB}
+        ReactAndroid::reactnative
+        ReactAndroid::jsi
+        fbjni::fbjni
+        openssl::crypto
+      )
+    else()
+      target_link_libraries(
         ${PACKAGE_NAME}
         ${LOG_LIB}
         ReactAndroid::jsi
@@ -57,7 +68,8 @@ if(${REACT_NATIVE_MINOR_VERSION} GREATER_EQUAL 71)
         ReactAndroid::react_nativemodule_core
         android
         openssl::crypto
-    )
+     )
+    endif()
 else()
     add_library(
         ${PACKAGE_NAME}


Questions regarding eager loading, paginating and resulting responses

So this is my first time using laravel and dingo and I have some question about whether I'm doing things right or not and if I'm understanding things right or not. So I wanted to return a collection of resources and figured I would eager load relations if they were requested via the includes query string parameter. So in my controller, I have the following:
$input = Request::input();
$includes = isset($input['include']) ? $input['include'] : null;
$paginationSize = 25;
if ($includes) {
    $products = Product::with(explode(',', $includes))->paginate($paginationSize);
} else {
    $products = Product::paginate($paginationSize);
}

return $this->paginator($products, new ProductTransformer());

Seems to work well but then I realized that Dingo\Api\Transformer\Adapter\Fractal does it's own eager loading as well by default. Does that mean that I didn't have to manually eager load on my controller?
Second question: is it normal that responses get built out twice? Having my eager loaded controller code actually made things slower as I was doing some random endpoint testing with large amounts of data being returned. I noticed that it was because the Factory::paginator() method creates a new Response class (and thus applies the morphToJson() method on my large content), then later calls Router::prepareResponse() which again recreates the Response object using Response::makeFromExisting() (and again calls morphToJson()). Didn't have time to look into it further but why would the Dingo Response need to rebuild itself if Response::makeFromExisting and/or Response::makeFromJson already have a working copy of the current response passed to them?

Must have missed the wiki block about eager loading being a feature, so I guess that answers my first question.

@georaldc For you're first question, yea looks like you found that the package automatically handles eager loading for you. As for the second one, thats something I need to dig into more and see if I can resolve that.


Images not properly loaded in Neume Notation Documentation

Most images are not loaded in the Documentation of Neume Notation, like this:

We think the problem is due to the images in the guidelines repo are not fully uploaded to the main MEI-encoding repo.

The images are available in the Guidelines, they're just not showing up in the documentation:
https://music-encoding.org/guidelines/v4/images/modules/neumes/NEUME-con.png
The guidelines have the image URL as this (you can right click on the image that is not loading and say "Copy image address")
src="/guidelines/images/v4/modules/neumes/NEUME-con.png"
It looks like the correct address should be v4/images, not images/v4

Ahh I see. Yes you're right. Thanks for looking into this @ahankinson !

I believe this has been addressed now.


False positive: aws_compliance.control.foundational_security_ssm_2 if Patch is not applicable

Describe the bug
False Positive Results for Control aws_compliance.control.foundational_security_ssm_2. All Patches that are not applicable raises alarm.
Especially for windows instances, this result into thousands of false positives in our environment.
Steampipe version (steampipe -v)
v0.21.4
Plugin version (steampipe plugin list)
aws 0.130.0
To reproduce
Lets check patches for an instance with AWS CLI:
aws ssm describe-instance-patches --instance-id i-03cdb --region eu-central-1
Result (stripped to KB2305420)
{
"Patches": [
{
"Title": "",
"KBId": "KB2305420",
"Classification": "",
"Severity": "",
"State": "NotApplicable",
"InstalledTime": 0.0
}
]
}
Please note the State "NotApplicable"
Now let's start the control:
steampipe check aws_compliance.control.foundational_security_ssm_2

2 All EC2 instances managed by Systems Manager should be compliant with patching requ… HIGH 2,321 / 5,266 [==========]
ALARM: i-03cdb patch KB2305420 is non-compliant. ............................... eu-central-1 123456789

Expected behavior
Instead of raising an ALARM please consider the NotApplicable as SKIP.
Please see the AWS documentation regarding this status as well here:
https://docs.aws.amazon.com/systems-manager/latest/userguide/patch-manager-compliance-states.html
Not-Applicable means really: The related vulnerable software package is not even installed on that specific instance, therefore the patch is not required and skipped.
thanks in advance
Markus

Thanks, @the-cloud-ninja, for catching this bug. I have raised a PR with a fix. Could you please test it and let us know if it works for you?

Very nice job indeed! Review succesful, false positive gone! Thank you so much!


Date format for first date and first day of month differ from others

Having config:
views: [
{
mode: "week",
position: "middle_center",
dateFormat: "D",
},
],
Result:

Expecting:
Having the same dateformat on every date header.

set slotAltTitleFormat: "D",.


remove all the old tlog and batch referenches from the code

No more old data path. hooray!!!
The monitor of BG has not been refactored yet.

Covered by our tests, and installation (not upgrade) environment without old files.
Moving the issue to Done.


does not correctly pull up to day module manager

sooo.. i had module manager installed via ckan, so i could update it, but cka won't update it, and it's quite behid... soo i removed it, and now i'ds "autodetected"... but that's supposedly causing problems with realfuels.,...
and now, afdter deleting the dll, it wants to remove about 40 or 50 mods. so... what i'm kinda asking, is if we can get an override for "autodetected" mods, to avoid this cluster****

I have a plan in my head for a better way to handle installations outside CKAN, but it's very theoretical at this stage. Currently, the only method is to use File->"Export Installed Mods" , save as type CKAN favourites list, then delete the AD mod, let CKAN delete all the others, then use File->"Install from .ckan", selecting the favourites list you created. CKAN will pull all the removed mods back in from the cache, so it should be pretty quick.

well, i ended up just handling modulemanager manually for now.
any idea as to why it wasn't updating in the first place?

Without knowing what error message you were getting, I couldn't say.


Add missing FromTimeSpan method on Duration type

Oh wait, there is one error

Ok, now it is ready for review.

Merged in #11.


Deployment crazyness.

I am not really sure how to explain this.
Sometime when we update a service that is already running in service fabric it will stop the service on one node and then start it up again (maybe on the same node, maybe on another).  Which is all very expected and at this point you would have thought SF had done all the work it needed to do.  But sometimes (maybe 1 in 2) it decides to do this again!  It stops the service it has just started up and starts it again (maybe on the same node, maybe on another).
We really struggling to work out why it is doing this and how to stop it.  Any advice would be much appreciated.
<?xml version="1.0" encoding="utf-8"?>
<ServiceManifest Name="RedisEntityDispatcherCasinoPkg"
                 Version="${FileHash}"
                 xmlns="http://schemas.microsoft.com/2011/01/fabric"
                 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <ServiceTypes>
    <StatelessServiceType ServiceTypeName="RedisEntityDispatcherCasinoType" UseImplicitHost="true">
      <LoadMetrics>
        <LoadMetric Name="CPU" DefaultLoad="100" />
      </LoadMetrics>
      <PlacementConstraints>#{RedisEntityDispatcherCasino-PlacementConstraints}</PlacementConstraints>
    </StatelessServiceType>
  </ServiceTypes>

  <CodePackage Name="Code" Version="#{RedisEntityDispatcherCasino-Version}">
    <SetupEntryPoint>
      <ExeHost>
        <Program>SpreadexServiceManager/Spreadex.ServiceManager.exe</Program>
        <Arguments>-consulonly</Arguments>
        <WorkingFolder>CodePackage</WorkingFolder>
      </ExeHost>
    </SetupEntryPoint>
    <EntryPoint>
      <ExeHost>
        <Program>Spreadex.Redis.EntityDispatcher.exe</Program>
      </ExeHost>
    </EntryPoint>
    <EnvironmentVariables>
      <EnvironmentVariable Name="SX_ENDPOINT" Value="Casino"/>
    </EnvironmentVariables>
  </CodePackage>

</ServiceManifest>

So, this, seems sort of minor and explainable to me. It was probably evacuating an update domain for an upgrade, determined that the shortest path was to move stuff to another specific node. But that maybe triggered some other condition (like memory usage), and so it decided it would be better served somewhere else.

Thanks for the feed back.
For most of our services this isn't really an issue, but we do have some that provide updates and content to our sites, are expensive to start up and we can only run one instance.  If these services are shut down and started up once we get about 10-15 seconds of laggy/hanging service which although isn't ideal has been a price worth paying for in hours deployments.  However when one of these services gets shut down and started twice it causes issues on the site for over a minute.
In your example why would it then decide to stop it and start it on the same node again though?
eg.
stop service A on node 1
start service A on node 2
stop service A on node 2
start service A on node 2
we don't set any memory metrics for our services, so I don't think this would be having any effect.

Name
Node Capacity
Node Load
Node Remaining Capacity
Is Capacity Violation
Node Buffered Capacity
Node Remaining Buffered Capacity
Current Node Load
Node Capacity Remaining
Buffered Node Capacity Remaining
Planned Node Load Removal

servicefabric:/_MemoryInMB
26213
0
26213
false
26213
26213
0
26213
26213
0

In the latest example of this happening node 2 was running at about 15% actual memory usage.
We do use the cpu metric to try to spread the services sensibly though.  But the metrics for the target nodes were all < 50% so it shouldn't feel the need to juggle things around too much.
Do you know of any settings that we could look at to prevent this from happening?

@AlexisColes I'm not an expert by any means, but I do believe you can setup a MovementCost with each service, to give Service Fabric some hints when deciding whether or not to move services.

Setting movement cost as mentioned by @JustinKaffenberger should reduce the rate of service placement changes which should improve overall service quality. These services will still be moved during static config or code upgrades so you may want to manually trigger upgrades during a self-designated maintenance period.


I have a bot with a single dialog and I can't seem to set "AutoEndDialog" property

Describe the bug
There is no way for controlling the behavior of the root dialog?
Version
1.0.1
To Reproduce

create a dialog, try and set AutoEndDialog property.

Expected behavior
To be able to set AutoEndDialog property to true or false.,

@tdurnford let's bring back autoEndDialog into the forms for an Adaptive Dialog as a boolean affordance

autoEndDialog is set to true by default.
However, it does not appear that the root dialog ends properly as expected. For example, properties in the dialog scope do not expire between executions.

This appears to be part of the problem:
https://github.com/microsoft/BotFramework-Composer/blob/master/runtime/dotnet/core/ComposerBot.cs#L57

Per @tomlm @Stevenic @benbrown, we should

Expose ability to manage autoEndDialog property of adaptive dialog in form editor
remove the code in bot runtime that automatically sets autoEndDialog to false.


Remove system time dependencies from tests

AlarmClock constructor optionally takes a function pointer. This can be used to override the Sleep() function in the tests so that they don't actually call std::this_thread::sleep_for()

Tests updated with new constructor usage

Existing syntax works properly, nothing in Research should break

:+1:

:+1: I like the approach. If you can check the values used in the calls to FakeSleep, you will have better tests.

:+1: Consider making kFakeSleepUs an atomic.

Looks good now


Fix incompatibility with neovim 0.4.4

Hi @ojroques, I occur a problem after update this plugin to this commit

and the pr fix this

Thanks !


Add grpcwebproxy plugin

1. What does this change do, exactly?
New directive for the http server type called grpcwebproxy
2. Please link to the relevant issues.
N/A
3. Which documentation changes (if any) need to be made because of this PR?
No document changes needed. Link to plugin's documentation --> here

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.pieterlouw seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Wow this is awesome. 👏

What if it was just called grpc? Would there be anything other than a GRPC web proxy?

Hi Matt,
That's a good question.
My initial idea was to have it as a grpc-web client to normal grpc server
proxy,but it could just as well serve as a transparent grpc client
(mobile,IoT, etc) to grpc server proxy as well.
The other implementation in the grpc ecosystem is grpc-gateway (REST to
grpc proxy),but I'm not exactly sure how and if that could be dynamically
implemented in the plugin
Pieter
On 24 May 2017 4:51 PM, "Matt Holt"<EMAIL_ADDRESS>wrote:

What if it was just called grpc? Would there be anything other than a
GRPC web proxy?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mholt/caddy/pull/1686#issuecomment-303748353, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AETJrbmj30TavmOhl1GjPoaFiKrUCo1xks5r9EP9gaJpZM4NlGWH
.

In general, Caddy plugins should be as cohesive as possible (meaning that a grpc plugin would handle all things GRPC related), unless there are some crazy dependency reasons or some other extenuating circumstance that requires they be split into different plugins/directives. (Remember a plugin can also register more than one directive. But I dunno if you'd want to do that if configuring a GRPC proxy and gateway are similar.)
Simpler directive names are usually better as well.
Once you choose the name, it's not easily changed, so choose wisely. I think I might lean more toward grpc than grpcwebproxy personally.

Naming it grpc makes more and more sense to me.

Closing this PR as I created a new one here with plugin name as grpc instead


Update Hello example

Update to SSE-300 pack version 1.4.0
Update to CMSIS-Compiler I/O-Retargeting
Add GCC and Clang compiler support
Add build.py for CI test on Corstone

Superseded by other PRs in the meanwhile.


K8 spxc 370 test

Test name
Status

scheduled-backup
failed

Test name
Status

scheduled-backup
failed

Test name
Status

scheduled-backup
failed

Test name
Status

scheduled-backup
failed

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-562-badd0401

Test name
Status

scheduled-backup
passed

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-562-465465da

Test name
Status

scheduled-backup
passed


UTC Logger.check error: failed to get caller

looks like with v1.15.1 of the aws vpc cni the output for the aws-eks-nodeagent just says
k logs aws-node-jpg2r -c aws-eks-nodeagent
{"level":"info","ts":"2023-10-19T09:55:41.395Z","caller":"runtime/asm_amd64.s:1598","msg":"version","GitVersion":"","GitCommit":"","BuildDate":""}
2023-10-19 09:55:41.481551956 +0000 UTC Logger.check error: failed to get caller
2023-10-19 09:55:41.481656868 +0000 UTC Logger.check error: failed to get caller

It shouldn't cause any functionality impact but we will clean it up.

Hey!
Using VPC CNI v1.16.0 I'm still facing this Issue.
This makes enable-policy-event-logs pretty useless and the logging feature pretty useless.
Cluster uses EKS (1.27) with managed node groups (1.27.9-20240117): any chance to get a pointer on how to fix that and get  hands on policy event logs ?

@Jufik - Are you checking pod logs for policy logs when you enable - enable-policy-event-logs ? The decision/access logs will be redirected to /var/log/aws-routed-eni/network-policy-agent.log when the knob is enabled. The same log file will also contain node agent logs..

Am i doing something wrong, because I am using 1.16.3 and still see Logger.check error: failed to get caller logged constantly when policy event logs are enabled. I'd rather not log redundant, unimportant lines on every since pod on each node. Is is possible to change the log level so I don't have to log these to disk at all?

The problem persists, and I'm encountering it with aws-network-policy-agent:v1.0.8-eksbuild.1 and eks 1.27. Can we consider reopening the issue? @jayanthvn @jdn5126
Additionally, when I enable both the enable-cloudwatch-logs and enable-policy-event-logs parameters, the pods get stuck in a crashloopbackoff state with exit code 1, and no logs are generated.

I can confirm that this issue still persists with EKS 1.28 / aws-network-policy-agent:v1.1.0-eksbuild.1
Can this issue be /reopen 'ed?

I'm seeing a similar issue with EKS 1.29 and CNI : v1.16.2-eksbuild.1. Looks the issue needs to be reopened unless we missing something ?
{"level":"info","ts":"2024-03-26T18:30:07.320Z","caller":"runtime/asm_amd64.s:1650","msg":"version","GitVersion":"","GitCommit":"","BuildDate":""} 2024-03-26 18:30:07.336116596 +0000 UTC Logger.check error: failed to get caller

I was getting this error with EKS 1.29 and VPC CNI v1.17.1, but it went away after commenting serviceAccountArn property in my CDK resource
    new eks.CfnAddon(this, "VpcCniAddon", {
      clusterName: cluster.clusterName,
      addonName: "vpc-cni",
      addonVersion: "v1.17.1-eksbuild.1",
      resolveConflicts: "PRESERVE",
      // serviceAccountRoleArn: cluster.role.roleArn,
      configurationValues: JSON.stringify({
        env: {
          ENABLE_PREFIX_DELEGATION: "true",
          WARM_PREFIX_TARGET: "1",
        },
      }),
    });

I was getting this error with EKS 1.29 and VPC CNI v1.17.1, but it went away after commenting serviceAccountArn property in my CDK resource
    new eks.CfnAddon(this, "VpcCniAddon", {
      clusterName: cluster.clusterName,
      addonName: "vpc-cni",
      addonVersion: "v1.17.1-eksbuild.1",
      resolveConflicts: "PRESERVE",
      // serviceAccountRoleArn: cluster.role.roleArn,
      configurationValues: JSON.stringify({
        env: {
          ENABLE_PREFIX_DELEGATION: "true",
          WARM_PREFIX_TARGET: "1",
        },
      }),
    });

That potentially indicate that role missing some permissions which are present on nodegroup's role

Using VPC CNI addon 1.17.1, based on observing log data, this error seems to occur only when a policy verdict is being made. So the more verdicts you have, the more spammy this log is.
If it helps anything, our settings are:
{
  "enableNetworkPolicy": "true",
  "env": {
    "AWS_VPC_ENI_MTU": "1480",
    "AWS_VPC_K8S_CNI_LOG_FILE": "stdout",
    "AWS_VPC_K8S_PLUGIN_LOG_FILE": "stderr",
    "AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG": "true"
  },
  "nodeAgent": {
    "enablePolicyEventLogs": "true",
    "enableCloudWatchLogs": "true",
  }
}

We also have some IRSA policy attached to deliver the cloudwatch logs (which are working, by the way -- we see policy verdicts in CW)

Fix is released with network policy agent v1.1.2 for the original issue of logs having failed to get caller... - https://github.com/aws/amazon-vpc-cni-k8s/releases/tag/v1.18.2. Please test and let us know if there are any issues.


Compatibility certification request for Hibernate Validator for Validation 3.1.0

[x] Organization Name ("Organization") and, if applicable, URL:
Red Hat, https://www.jboss.org/

[x] Product Name, Version and download URL (if applicable):
Hibernate Validator, 8.0.1.Final, http://hibernate.org/validator/releases/8.0/

[x] Specification Name, Version and download URL:
Jakarta Bean Validation 3.1, https://jakarta.ee/specifications/bean-validation/3.1/

[x] TCK Version, digital SHA-256 fingerprint and download URL:
3.1.0, ed25281dad4ce0f04b040ff910f7cdbf6758bc20609d7d185bb9d8e720cddb17
https://download.eclipse.org/ee4j/bean-validation/3.1/beanvalidation-tck-dist-3.1.0.zip

[x] Public URL of TCK Results Summary:
https://github.com/jakartaredhat/beanvalidation-tck/wiki/Jakarta-Bean-Validation-3.1-TCK-Results
Includes both Java SE 17 and 21 runs

[x] Java runtime used to run the implementation:
openjdk version "21.0.1" 2023-10-17 LTS
OpenJDK Runtime Environment Temurin-21.0.1+12 (build 21.0.1+12-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.1+12 (build 21.0.1+12-LTS, mixed mode, sharing)
openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment Temurin-17.0.9+9 (build 17.0.9+9)
OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (build 17.0.9+9, mixed mode, sharing)

[x] Summary of the information for the certification environment, operating system, cloud, ...:
EF CI environment
Linux basic-2vd69 6.2.9-300.fc38.x86_64 SMP PREEMPT_DYNAMIC Thu Mar 30 22:32:58 UTC 2023 x86_64 GNU/Linux

[x] By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.

[x] By checking this box I attest that all TCK requirements have been met, including any compatibility rules.

Link to TCK should be https://download.eclipse.org/ee4j/bean-validation/3.1/validation-tck-dist-3.1.0.zip

Link to TCK should be https://download.eclipse.org/ee4j/bean-validation/3.1/validation-tck-dist-3.1.0.zip

Also applies to the TCK Results page

Links have been updated


Refactor ServiceBuilder

Remove extra alias indirection ServiceTypeAlias - all its usage (2 places) fits on one screen

Remove add_service_types in favor of add_service_type. The removed function was only used once and easily replacable by its "singular" version

Remove ServiceBuilderWithServiceType - ServiceType is in fact optional, as https://sovrin-foundation.github.io/sovrin/spec/did-method-spec-template.html says:

If the types field is present

So requiring user to call one of the (originally 2 methods) is just not right. If we were to be just "opinionated" to require users of our builder to do so, it should follow same pattern as other required attributes such as id, service_endpoint, extra.

If add_service_type is called with the same value as been provided before, throw InvalidInput instead of quietly doing nothing

If add_service_type is called with empty string, throw InvalidInput error

Note:
Probably stating obvious, but I take it that ServiceBuilder was somewhat of a shortcut as we didn't intend to use builder macro libraries at the time, and building full blown state pattern builder by hand is cumbersome (hence why required attributes are part of ServiceBuilder<E>::new(....) constructor directly. Perhaps down the line we can adopt the same builder library as in messages crate.

Codecov Report

Merging #1021 (f902e5f) into main (1a414f0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1021   +/-   ##
=======================================
  Coverage   36.31%   36.31%
=======================================
  Files         386      386
  Lines       22040    22040
  Branches     4062     4062
=======================================
  Hits         8003     8003
  Misses      11877    11877
  Partials     2160     2160

Flag
Coverage Δ

unittests-aries-vcx
36.31% <ø> (ø)

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


☂✅ Green CI: Re-enabling disabled tests

We have a handful of tests that have been disabled on Circle CI over the years. It's time to get these back up and running so we can merge PRs and cut new releases with confidence.
This is an umbrella task intended to track all the work necessary to re-enable these tests. This issue is being kept up to date so new items will be added and completed ones will be (re)moved. Some of the items will spawn separate issues to track work. If you don't see a name assigned to any of the below items and you would like to help out, please volunteer in the comments and reach out to me to get started!
What needs to be re-enabled?
These tests are configured as aliases in the Circle CI config. I'm happy to help with the Circle CI side of things, but for now you can focus on making sure the command/script (e.g. ./scripts/run-ci-e2e-tests.js --ios) succeeds locally.

Circle CI Job
Test Name
Test Script
Fix?

test_android
Android e2e
node ./scripts/run-ci-e2e-tests.js --android

test_ios
iOS e2e
node ./scripts/run-ci-e2e-tests.js --ios

test_js
JS e2e
node ./scripts/run-ci-e2e-tests.js --js
https://github.com/facebook/react-native/pull/28392

test_ios
Podspecs
./scripts/process-podspecs.sh

CocoaPods Podspecs tests

@hramos is there more detail on what this should do?

I haven’t looked into it recently. There’s a PR out right now that reworks how CocoaPods is supported in this repo, so it’s an open question whether this test is still necessary or sufficient.
Sent with GitHawk

@hramos I'd like to help with this  ./scripts/run-ci-e2e-tests.js --js

@gregoryfm it looks like @ericlewis is already taking a stab at this, through https://github.com/facebook/react-native/pull/23571.

Any help with android e2e would be much appreciated tho!

@hramos I think the iOS portion is complete too, it’s e2e test consists of setting up a project via react-native init and confirming that we are indeed using the master branch template & that the snapshot lines up. This should indicate a successful react native init on iOS.

The js e2e tests consist of us being able to bundle the js successfully, and has been completed as well, as marked. But wanted to note how it works for transparency purposes.

Working on fixing the android e2e tests! Once I've made some progress, I'll give an update :)

@casperboone @ericlewis thanks so much for your help on this.
@hramos do you think you could give an update about what we still would like to do? I think there is probably a bunch more integration work for Facebook to keep things green but I'm not entirely up-to-date on what that work may be.

Thanks for all your help getting these tests fixed.
I'm posting an update to clarify what needs to be done before this issue can be closed. The podspec tests and Android end-to-end tests remain disabled, and we could use some help getting them green again.
iOS: Podspec tests
These are failing because the yoga pod cannot be built (expand to see logs):

  While building module 'yoga' imported from /var/folders/82/w8hcc_tj7yq80482srkc1r2x0bj21j/T/CocoaPods-Lint-20190530-11880-m4ez3b-yoga/App/main.m:3:
    In file included from :1:
    In file included from /Users/hramos/Library/Developer/Xcode/DerivedData/App-fcnbolkgqgfrrdcvttlgzjkxdyvg/Build/Products/Release-iphonesimulator/yoga/yoga.framework/Headers/yoga-umbrella.h:13:
    /Users/hramos/Library/Developer/Xcode/DerivedData/App-fcnbolkgqgfrrdcvttlgzjkxdyvg/Build/Products/Release-iphonesimulator/yoga/yoga.framework/Headers/CompactValue.h:11:10: fatal error: 'cmath' file not found
    #include
             ^~~~~~~
    1 error generated.
    /var/folders/82/w8hcc_tj7yq80482srkc1r2x0bj21j/T/CocoaPods-Lint-20190530-11880-m4ez3b-yoga/App/main.m:3:9: fatal error: could not build module 'yoga'
    @import yoga;
     ~~~~~~~^~~~
    2 errors generated.
WriteAuxiliaryFile /Users/hramos/Library/Developer/Xcode/DerivedData/App-fcnbolkgqgfrrdcvttlgzjkxdyvg/Build/Intermediates.noindex/App.build/Release-iphonesimulator/App.build/Objects-normal/i386/App.LinkFileList (in target: App)
    cd /var/folders/82/w8hcc_tj7yq80482srkc1r2x0bj21j/T/CocoaPods-Lint-20190530-11880-m4ez3b-yoga
    write-file /Users/hramos/Library/Developer/Xcode/DerivedData/App-fcnbolkgqgfrrdcvttlgzjkxdyvg/Build/Intermediates.noindex/App.build/Release-iphonesimulator/App.build/Objects-normal/i386/App.LinkFileList

** BUILD FAILED **

The following build commands failed:
    CompileC /Users/hramos/Library/Developer/Xcode/DerivedData/App-fcnbolkgqgfrrdcvttlgzjkxdyvg/Build/Intermediates.noindex/App.build/Release-iphonesimulator/App.build/Objects-normal/i386/main.o /var/folders/82/w8hcc_tj7yq80482srkc1r2x0bj21j/T/CocoaPods-Lint-20190530-11880-m4ez3b-yoga/App/main.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
    CompileC /Users/hramos/Library/Developer/Xcode/DerivedData/App-fcnbolkgqgfrrdcvttlgzjkxdyvg/Build/Intermediates.noindex/App.build/Release-iphonesimulator/App.build/Objects-normal/x86_64/main.o /var/folders/82/w8hcc_tj7yq80482srkc1r2x0bj21j/T/CocoaPods-Lint-20190530-11880-m4ez3b-yoga/App/main.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(2 failures)

Testing with xcodebuild.
-> yoga (1000.0.0.React)
- WARN  | source: Git sources should specify a tag.
- WARN  | [iOS] license: Unable to find a license file
- ERROR | [iOS] xcodebuild: Returned an unsuccessful exit code.
- NOTE  | xcodebuild:  note: Using new build system
- NOTE  | [iOS] xcodebuild:  note: Planning build
- NOTE  | [iOS] xcodebuild:  note: Constructing build description
- NOTE  | [iOS] xcodebuild:  warning: Capabilities for App may not function correctly because its entitlements use a placeholder team ID. To resolve this, select a development team in the build settings editor. (in target 'App')
- NOTE  | xcodebuild:  /Users/hramos/Library/Developer/Xcode/DerivedData/App-fcnbolkgqgfrrdcvttlgzjkxdyvg/Build/Products/Release-iphonesimulator/yoga/yoga.framework/Headers/CompactValue.h:11:10: fatal error: 'cmath' file not found
- NOTE  | xcodebuild:  /var/folders/82/w8hcc_tj7yq80482srkc1r2x0bj21j/T/CocoaPods-Lint-20190530-11880-m4ez3b-yoga/App/main.m:3:9: fatal error: could not build module 'yoga'
[!] yoga did not pass validation, due to 1 error.
You can use the --no-clean option to inspect any issue.
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.6.1/lib/cocoapods/command/lib/lint.rb:92:in block in run' /Library/Ruby/Gems/2.3.0/gems/cocoapods-1.6.1/lib/cocoapods/command/lib/lint.rb:60:in each'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.6.1/lib/cocoapods/command/lib/lint.rb:60:in run' /Library/Ruby/Gems/2.3.0/gems/claide-1.0.2/lib/claide/command.rb:334:in run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.6.1/lib/cocoapods/command.rb:52:in run' /Library/Ruby/Gems/2.3.0/gems/cocoapods-1.6.1/bin/pod:55:in <top (required)>'

The failure can be reproduced by running ./scripts/process-podspecs.sh on macOS.

I've updated the root issue with the latest list of disabled tests. I have opened https://github.com/facebook/react-native/pull/28392 to make it easier to re-enable tests and iterate on them on your PRs.

JavaScript end-to-end tests
These run as part of the test_js job, and are disabled by default. To run them, edit .circleci/config.yml and set run_disabled_tests to true under the test_js workflow at the end of the file (pending #28392 getting merged):
workflows:
  version: 2

  tests:
    jobs:
...
      - test_js:
          run_disabled_tests: true
          requires:
            - setup_js

Why it's failing
react-native $ node ./scripts/run-ci-e2e-tests.js --js
...
error Cannot find module './Libraries/polyfills/console.js'

iOS end-to-end tests
These run as part of the test_ios job, and are disabled by default. To run them, edit .circleci/config.yml and set run_disabled_tests to true under the test_ios workflow at the end of the file (pending #28392 getting merged):
workflows:
  version: 2

  tests:
    jobs:
...
      - test_ios:
          run_disabled_tests: true
          requires:
            - setup_ios

Why it's failing
react-native $ node ./scripts/run-ci-e2e-tests.js --ios
...
▸ Building Pods/Flipper [Debug]
▸ Check Dependencies
▸ Building Pods/FlipperKit [Debug]
▸ Check Dependencies
▸ Building Pods/Pods-HelloWorld [Debug]
▸ Check Dependencies
▸ Building Pods/Pods-HelloWorld-HelloWorldTests [Debug]
▸ Check Dependencies
▸ Building HelloWorld/HelloWorld [Debug]
▸ Check Dependencies
▸ Running script 'Start Packager'
▸ Linking HelloWorld
⚠  ld: directory not found for option '-L-L/Users/distiller/Library/Developer/Xcode/DerivedData/HelloWorld-ddyeadlplgsjokalhojpfxozuuyp/Build/Products/Debug-iphonesimulator/CocoaAsyncSocket'

❌  ld: library not found for -lCocoaAsyncSocket

❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

Testing failed:
	HelloWorld:
		Linker command failed with exit code 1 (use -v to see invocation)
	Testing cancelled because the build failed.

CocoaPods Podspecs tests
These run as part of the test_ios job, and are disabled by default. To run them, edit .circleci/config.yml and set run_disabled_tests to true under the test_ios workflow at the end of the file (pending #28392 getting merged):
workflows:
  version: 2

  tests:
    jobs:
...
      - test_ios:
          run_disabled_tests: true
          requires:
            - setup_ios

Why it's failing
react-native $ ./scripts/process-podspecs.sh
+ pod lib lint --subspec=_ignore_me_subspec_for_linting_ --verbose --allow-warnings --fail-fast --private --swift-version=3.0 --sources=https://example.com/react-test.git,https://github.com/CocoaPods/Specs.git

  CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only perfomed in repo update
[!] Unable to find a specification named `React/_ignore_me_subspec_for_linting_` in `React (1000.0.0)`.

/Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.8.4/lib/cocoapods-core/specification.rb:339:in `subspec_by_name'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/validator.rb:120:in `validate'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/command/lib/lint.rb:87:in `block in run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/command/lib/lint.rb:69:in `each'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/command/lib/lint.rb:69:in `run'
/Library/Ruby/Gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'

Exited with code exit status 1
CircleCI received exit code 1```

Android end-to-end tests
These run as part of the test_android job, and are disabled by default. To run them, edit .circleci/config.yml and set run_disabled_tests to true under the test_android workflow at the end of the file (pending #28392 getting merged):
workflows:
  version: 2

  tests:
    jobs:
...
      - test_android:
          run_disabled_tests: true
          requires:
            - setup_android

Why it's failing
react-native $ node ./scripts/run-ci-e2e-tests.js --android
...
>>>>> Install end-to-end framework

Command failed, 2 retries left
Command failed, 1 retries left
Command failed, 0 retries left
Failed to install appium

https://github.com/facebook/react-native/pull/28392 fixes the JavaScript e2e tests.

Great stuff @hramos, I’ll dive into these soon too 👍

iOS end-to-end tests
These run as part of the test_ios job, and are disabled by default. To run them, edit .circleci/config.yml and set run_disabled_tests to true under the test_ios workflow at the end of the file (pending #28392 getting merged):
workflows:
  version: 2

  tests:
    jobs:
...
      - test_ios:
          run_disabled_tests: true
          requires:
            - setup_ios

Why it's failing
react-native $ node ./scripts/run-ci-e2e-tests.js --ios
...
▸ Building Pods/Flipper [Debug]
▸ Check Dependencies
▸ Building Pods/FlipperKit [Debug]
▸ Check Dependencies
▸ Building Pods/Pods-HelloWorld [Debug]
▸ Check Dependencies
▸ Building Pods/Pods-HelloWorld-HelloWorldTests [Debug]
▸ Check Dependencies
▸ Building HelloWorld/HelloWorld [Debug]
▸ Check Dependencies
▸ Running script 'Start Packager'
▸ Linking HelloWorld
⚠  ld: directory not found for option '-L-L/Users/distiller/Library/Developer/Xcode/DerivedData/HelloWorld-ddyeadlplgsjokalhojpfxozuuyp/Build/Products/Debug-iphonesimulator/CocoaAsyncSocket'

❌  ld: library not found for -lCocoaAsyncSocket

❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

Testing failed:
	HelloWorld:
		Linker command failed with exit code 1 (use -v to see invocation)
	Testing cancelled because the build failed.

After upgrading a project with version 0.61.2 to 0.62.0 building the app fails with the same error.

That's right, @timkuilman, these tests are broken on master.

I'm sorry I wasn't very clear. After doing the upgrade as explained in the React Native Upgrade tool my app was no longer building. I'm not referring to the test.
In my case, the error was fixed by enforcing the new build system of XCode. I had these lines from ios/appName.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings
	<key>BuildSystemType</key>
	<string>Original</string>

Hi, I have the same issue here: "ld: library not found for -lCocoaAsyncSocket",  " 0.62.2".

For me it only worked when I added:
$(TOOLCHAIN_DIR)/usr/lib/swift5.0/$(PLATFORM_NAME) to the Library Search Paths.
https://github.com/react-native-community/lottie-react-native/issues/575#issuecomment-542049943

@hramos is it still worth keeping this issue open? Is it still relevant?

@hramos is it still worth keeping this issue open? Is it still relevant?

@hramos pinging just in case you missed ☝ :)

I'm not sure why GH gave me a notification for this issue given that there's no activity (?)
but this is a stale issue that we can close so I'll do just that :D


Linuxkit integration

Integration of linuxkit
Sub-commands to work with GCP via linuxkit

Haven't had a chance to review in details yet, but if any code was taken from linuxkit project -- that needs to be very explicitly mentioned before this can be merged.

Hey @mydatascience -- just please update LICENSE and NOTICE as it is done in EVE itself re: Linuxkit

Hey @mydatascience -- just please update LICENSE and NOTICE as it is done in EVE itself re: Linuxkit

Is it ok now @rvs ?


just wondering why new seed after snapshot

shouldn't be  an old seed  still be secure after a snapshot?
or is it just  to  be extra safe you create new seed..?

It’s so that you don’t need to generate a ton of addresses in the wallet

@rajivshah3 is right. The idea is that you don't want a seed that needs to generated like 1000 addresses, because that is what this tool is doing. The new seed gives you quick access to a post-snapshot wallet without any delay.


Added optional remote logging to kedge.

PTAL @kdima, @devnev
Signed-off-by: Bartek Plotka<EMAIL_ADDRESS>

Codecov Report

Merging #31 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #31   +/-   ##
=======================================
  Coverage   49.75%   49.75%
=======================================
  Files          22       22
  Lines        1039     1039
=======================================
  Hits          517      517
  Misses        481      481
  Partials       41       41

Continue to review full report at Codecov.

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

LGTM


questions on fixed-buf variations other than read_fixed and write_fixed

sendmsg variations: prep_sendmsg_zc and prep_sendmsg_zc_fixed

[ ] Missing man page info: the kernel supports a prep_sendmsg_zc but there is no man page for it and the op is not in the io_uring_enter.2 man page.
There is support for it in the liburing API: io_uring_prep_sendmsg_zc is defined and there appears to be a path in test/send-zerocopy.c for testing it. Perhaps this should be added to the prep_sendmsg.3 and the io_uring_enter.2 man pages.

[ ] Missing liburing API: it appears the kernel is already supporting a fixed-buffer option to sendmsg_zc, but the liburing API does not include such a variation. Based on the names chosen for the prep_send options, I guess the name would be io_uring_prep_sendmsg_zc_fixed.

uring_cmd operation

[ ] Missing man page info. No liburing support for this. That's not a problem, per se, but the io_uring_enter.2 man page doesn't give even a mention to the IORING_OP_URING_CMD op but the io_uring_setup.2 man page does mention it when explaining the need for the larger sized SQE and CQE structures.
[x] It does get tested via test/io_uring_passthrough.c.
[ ] The kernel appears to support a fixed-buffer variation of this, using the sqe->buf_index field when the IORING_URING_CMD_FIXED ioprio bit is set. But it is not tested in the io_uring_passthrough.c.
[ ] Additional man page info: and the io_uring_enter.2 man page would then cover this ioprio bit.

IORING_RECVSEND_FIXED_BUF flag

Was this name chosen to future proof the symbol even though there is no recv or recvmsg op that accepts a fixed buf or is it considered a misnomer by now? While designing the fixed-buf option for a Rust library, am wondering if it should be made general enough to cover some receive operations which may come in the future or if it will always just be for the zero-copy forms of send and sendmsg.
And if it is just going to be used for the zero-copy forms, a question purely out of curiosity: why is the fixed-buf well suited for zero-copy send and sendmsg but not as well suited for the normal send and sendmsg?

IORING_RECVSEND_FIXED_BUF flag
1. Was this name chosen to future proof the symbol even though there is no recv or recvmsg op that accepts a fixed buf or is it considered a misnomer by now? While designing the fixed-buf option for a Rust library, am wondering if it should be made general enough to cover some receive operations which may come in the future or if it will always just be for the zero-copy forms of send and sendmsg.
   And if it is just going to be used for the zero-copy forms, a question purely out of curiosity: why is the fixed-buf well suited for zero-copy send and sendmsg but not as well suited for the normal send and sendmsg?

For zerocopy it saves some cycles on page pinning and so, but there should be almost no performance difference when we already memcpy the payload. Even though it can be implemented for generality, it would be useless performance wise. I didn't put much meaning into the RECV part of the name, the support might appear at some moment but I don't expect anyone being much interested in it.


ADE20K Dataset changed

I also retrain deeplabV3 plus on ADE20K and the link to this dataset changed http://groups.csail.mit.edu/vision/datasets/ADE20K/
And the structrue of this is different old ade20k dataset.
How I should change code to train or could you share to me the old dataset(ADEChallengeData2016.zip)

Excuse me, do you save dataset folder of ADE20K?
would you mind share for me the dataset folder of ADE20K which from the old link( I will download this)


[RESOLVED] System Board Inlet Temp: Temperature is above warning threshold: >30

Problem started at 18:39:27 on 2023.07.12
Problem name: System Board Inlet Temp: Temperature is above warning threshold: >30
Host: IDRAC_83
Severity: Warning
Operational data: Current value: 31 °C
Original problem ID: 32144
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23218&eventid=32144

Problem has been resolved in 4h 30m 1s at 23:09:28 on 2023.07.12
Problem name: System Board Inlet Temp: Temperature is above warning threshold: >30
Host: IDRAC_83
Severity: Warning
Original problem ID: 32144


Feature request

Thank you for this integration! No idea if it is possible, but I have two ideas:

sensor with my actual credit value. It would be great to use it to notify me in case of low value.
sensor that show if SMS were delivered. For example last ten SMS (like in journal on web) are listed in sensor attributes.

Thank you

Hi @GegoSK ,
thanks for your suggestions.
Your first point is easy. We can add a sensor for that.
Point 2 however, seems much more tricky because from what I know, home assistant has no API for storing any kind of data which would be needed in order to get the SMS IDs.
We will discuss this further internally and get back to you soon.
Hope this helps for now!


How to clear the screen?

I don't find a way to clear the screen in the API. It should work multi-platform...

Currently clear_screen is not exposed in the API.

Version 12.0.0 released


Add node list param to GraphEdit::delete_nodes_request signal

A small enhancement which should be useful for users which using custom GraphEdit's - Added a nodes parameter (typed array of StringName of the deleted nodes names) to the GraphEdit::delete_nodes_request call + updates existed engine calls of it to use that parameter (visual shader & animation editor).
Closes https://github.com/godotengine/godot/issues/30240

Thanks!

Y'all reaction time is insane. Thank you so much !

We maybe could backport it to 3.5 actually, since it shouldn't be ground-breacking
Issues to backport : #61112 , #30240

Was there a particular reason to provide only node names and not just the nodes themselves? To access/delete them they need to be gotten again :|

Was there a particular reason to provide only node names and not just the nodes themselves? To access/delete them they need to be gotten again with proper path from wherever the signal is being handled :|
Also I see changes in shader graph and animation tree, but did Visual Script use that signal?
Finally I realized if I use the node_names they are always empty even though I do have selected nodes and requested delete. And that's because... my nodes have no close button. I never saw the need to show one particularly. That sounds very arbitrary...

I did it for consistency with other methods which accept StringName's as a node id, at the end you only need to convert it to integer value.


Check in vendor directory

Over the last 8 or so days, I've been working with @jpeeler on getting roundtripping of API objects to work.  This involved a ton of deep dives in k8s code and adding debugging statements to upstream code.  Doing this was prohibitively difficult due to the fact that we do not let git track the vendor directory.  I think we have reached the point where we need to change that.
Arguments for:

Easy to manage changing code for dependencies in order to debug
Easy to collaborate on (1) by using a shared branch in git
Much easier to create patches and feed back changes into upstream from these debugging runs (which is something I have done numerous times when debugging problems in OpenShift, which also vendors the k8s repo)

I will never not boo the concept of committing 4.8 million lines of code.

For the record, I've removed the glide install invocation from the Makefile, since we should now be building based on the state of the vendor directory.

I would like to understand the problems you encountered. If you both checked out the same commit, what was getting out of sync?

@MHBauer

I would like to understand the problems you encountered. If you both checked out the same commit, what was getting out of sync?

There's no easy way to share the debugging changes you've made to files that aren't tracked by git.

So there were changes being made to stuff in vendor?

Correct - not functional, debugging only. Not intended to be checked in.
On Thu, Jan 12, 2017 at 9:47 PM Morgan Bauer<EMAIL_ADDRESS>wrote:

So there were changes being made to stuff in vendor?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/pull/257#issuecomment-272347115,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWXmOUoCHIoZAd0M_HZJZiSRV5AioKhks5rRuWtgaJpZM4Lidch
.

Couldn't we check vendor into a branch to debug, do the debug, and then remove the vendor commit at the end? Help me understand the steps to doing vendor check in temporarily vs permanently. I'm going to go poke at it now.

We could do that, but it's a process that involves hacking up the makefiles
and dockerfiles.  I feel like you shouldn't have to hack up the repo to do
this type of basic debugging.  I expect that we are going to be doing thus
A LOT as we begin using k8s code, and think that trying to repeat some
manual process each time is going to be burdensome and error prone.
Let me be honest here: I really do not understand what the objections to
this approach are based on except personal subjective taste. You literally
have to download the same bits if you let glide manage the directory.
On Thu, Jan 12, 2017 at 10:02 PM Morgan Bauer<EMAIL_ADDRESS>wrote:

Couldn't we check vendor into a branch to debug, do the debug, and then
remove the vendor commit at the end? Help me understand the steps to doing
vendor check in temporarily vs permanently. I'm going to go poke at it now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/pull/257#issuecomment-272349094,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWXmIlyEE1LZgiYCJs2U4ij2RTYPB4bks5rRulFgaJpZM4Lidch
.

maybe its in here and I missed it, but what's the process for updating the vendor dir since you erased glide from scbuildimage?

Is it correct to flatten the kubernetes vendor/ into our own?

What is the makefile hacking?

Ah, I see, the glide steps. I don't think we should automatically call glide for exactly that reason, but that's my fault.

You have to remove all glide installs frothe makefile and dockerfiles,
remove the line from gitignore, check in the vendored code.  This also
means you have to push the vendored code every time you have to debug an
issue like this.
Like I said, I do not personally understand objections to this as anything
but a style thing.  I'm willing to listen if someone can make the argument.
On Thu, Jan 12, 2017 at 10:25 PM Morgan Bauer<EMAIL_ADDRESS>wrote:

What is the makefile hacking?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/pull/257#issuecomment-272351782,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWXmA_Riu8OzHrYF1bYud4TEXvw0zySks5rRu6_gaJpZM4Lidch
.

This is so that we can more easily share modifications to dependencies? The upstream repos should be the book of record for each dependency; not our tainted copies of them. There's just way too much that can go wrong here. When you submit a PR that upgrades any dependencies, there could be thousands of lines of changes added as a result-- changes that are for all practical purposes unreviewable-- unreviewable, but not unimportant because we build against them. This just sounds awful to me.

It's both for collaborative debugging and creating patches to dependencies
to feed back debugging enhancements into them.
We can add a verify script that checks the integrity of the vendor
directory based on the glide yaml and lock - that should work to mitigate
risks you are concerned about.
I'm perfectly happy not to do this if someone can show me a better way.
On Thu, Jan 12, 2017 at 10:31 PM Kent Rancourt<EMAIL_ADDRESS>wrote:

This is so that we can more easily share modifications to dependencies?
The upstream repos should be the book of record for each dependency; not
our tainted copies of them. There's just way too much that can go wrong
here. When you submit a PR that upgrades any dependencies, there could be
thousands of lines of changes added as a result-- changes that are for all
practical purposes unreviewable-- unreviewable, but not unimportant
because we build against them. This just sounds awful to me.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/pull/257#issuecomment-272352392,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWXmFhRF3Fq-yjtdR3r0VuRB5dH8gP1ks5rRu_8gaJpZM4Lidch
.

@MHBauer @krancour All of the go projects that I personally work on commit their vendored dependencies, so I'm extremely curious how you two handle this situation:

I need to debug some problem
Hey, it looks like it goes into dependency X, which is missing meaningful debugging code in this area or missing the kind of debugging code I need
I add some debugging code and get closer, but dang, I just cannot figure it out; let me see if trusted work pal and colleague can help
I want to pass the exact same state easily in git to my trusted pal so they don't have to hunt around like I just did
Sweet, we finally figured out the problem, and I want to push changes into dependency X to make this easier for the next person to debug

For me, this happens almost every time I need to debug something, and I find committing the vendored code is a great facilitator of working through these problems.
As I said, if someone can show me a way which is objectively better, I'm happy to go that way.

I think one of the points of accepting glide initially was that glide could handle this scenario. Is it possible to create a customized k8s branch with debug info and temporarily point at it?

I think one of the points of accepting glide initially was that glide could handle this scenario. Is it possible to create a customized k8s branch with debug info and temporarily point at it?

This would be an acceptable solution for me, I think. I'll look into this tomorrow, but if someone wants to chime in with a link I wouldn't mind.

Hrm, looks like this might be what I am looking for:
https://glide.readthedocs.io/en/latest/commands/#glide-mirror

I was going to suggest the same.

I'd be interested to know if mirror does what you want.
I used the a modification of glide.yaml
  version: customized-k8s
  repo: https://github.com/MHBauer/kubernetes.git

then a glide update -v
then build the apiserver go build -i -v cmd/apiserver/apiserver.go
then run and we should see an upstream change
./apiserver --etcd-servers http://localhost:2379
W0112 21:49:36.497262   66237 authorization.go:33] Authorization is disabled
W0112 21:49:36.497336   66237 handlers.go:50] Authentication is disabled
E0112 21:49:36.497407   66237 genericapiserver.go:264] INSTALLING APIS UPSTREAM
I0112 21:49:36.499832   66237 apiserver.go:127] Finished installing API groups
[restful] 2017/01/12 21:49:36 log.go:30: [restful/swagger] listing is available at https://<IP_ADDRESS>:6443/swaggerapi/
[restful] 2017/01/12 21:49:36 log.go:30: [restful/swagger] https://<IP_ADDRESS>:6443/swaggerui/ is mapped to folder /swagger-ui/
I0112 21:49:36.500948   66237 server.go:201] Running the API server
I0112 21:49:36.500954   66237 serve.go:79] Serving securely on <IP_ADDRESS>:6443

The line E0112 21:49:36.497407   66237 genericapiserver.go:264] INSTALLING APIS UPSTREAM comes from a change in my fork of k8s upstream.
Can checkout this branch on my fork https://github.com/MHBauer/service-catalog/tree/my-upstream

I think I am convinced, just going futz around with this for a bit, closing this PR for now.


Unchecked add of instant + duration is causing a panic.

Current and expected behavior
https://github.com/kube-rs/kube/blob/0.91.0/kube-runtime/src/controller/mod.rs#L475
I'm getting a panic here.  I'm sure it's because we've accidentally queued up some long retry duration, but it shouldn't panic even if you do that.  Digging through the code, there's actually quite a few unchecked additions of times in the code.
Possible solution
use checked adds.
Additional context
No response
Environment
We're using the latest version of EKS 1.29, but i don't think it's relevant.
Configuration and features
No response
Affected crates
kube-runtime
Would you like to work on fixing this bug?
None

oh, wow. i wasn't aware that could panic. thanks for the report.
guess we need to move to https://doc.rust-lang.org/std/time/struct.Instant.html#method.checked_add everywhere as you say, but that does imply injecting a default instant if it fails. maybe a lower number, defaulting to now?

as an aside, i am curious about why this actually panics in practice. like, is this from bad monotonicity conditions with low numbers, or is there a problem with user requeue / debounce numbers that causes them to grow beyond the bounds of systemtime?

Are you running a debug build? Overflow checks are not enabled by default in release builds.

We found and fixed our bug that triggered this.. we had some code that sometimes generated a negative retry time, which we were casting to an unsigned int, which created a very large number.

as an aside, i am curious about why this actually panics in practice. like, is this from bad monotonicity conditions with low numbers, or is there a problem with user requeue / debounce numbers that causes them to grow beyond the bounds of systemtime?

isn't this just an integer overflow of the system monotonic counter?
I think it is reasonable to panic in that case, since passing such a large value is practically a bug. If this duration originated from user input, it is the input component that should have validated this.

We found and fixed our bug that triggered this.. we had some code that sometimes generated a negative retry time

Thanks for confirming this.

isn't this just an integer overflow

yeah, i was reading too much into all the scary notes in the instant docs about monotonicity. confirmed above as near-max int overflow, so just merging the fix in #1489.